From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:48185) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VYZZV-000050-CS for qemu-devel@nongnu.org; Tue, 22 Oct 2013 06:52:26 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1VYZZQ-0008V8-Cf for qemu-devel@nongnu.org; Tue, 22 Oct 2013 06:52:21 -0400 Received: from mx1.redhat.com ([209.132.183.28]:19443) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VYZZQ-0008UV-5I for qemu-devel@nongnu.org; Tue, 22 Oct 2013 06:52:16 -0400 Message-ID: <526658DB.4030803@redhat.com> Date: Tue, 22 Oct 2013 11:52:11 +0100 From: Eric Blake MIME-Version: 1.0 References: <20131020145406.GA17618@type> <1382280980-21676-1-git-send-email-samuel.thibault@ens-lyon.org> <1382280980-21676-16-git-send-email-samuel.thibault@ens-lyon.org> <526596D7.6000909@redhat.com> <20131022102203.GQ5518@type.wlan.youpi.perso.aquilenet.fr> <5266530F.8030100@redhat.com> <20131022103136.GR5518@type.wlan.youpi.perso.aquilenet.fr> <52665490.3070804@redhat.com> <20131022104504.GS5518@type.wlan.youpi.perso.aquilenet.fr> <526657E9.9080208@redhat.com> In-Reply-To: <526657E9.9080208@redhat.com> Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="oIbVfTP1RghXfm9gwlIGEmn19N8gh2Kb0" Subject: Re: [Qemu-devel] [PATCH 16/16] qapi-schema, qemu-options & slirp: Adding Qemu options for IPv6 addresses List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Samuel Thibault Cc: Yann Bordenave , qemu-devel@nongnu.org, Guillaume Subiron This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --oIbVfTP1RghXfm9gwlIGEmn19N8gh2Kb0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On 10/22/2013 11:48 AM, Eric Blake wrote: > On 10/22/2013 11:45 AM, Samuel Thibault wrote: >=20 >>>> It makes sense, yes, the syntax would be [ip6-prefix=3Dnet[/netsize]= ] . I >>>> just don't know how to express that in qapi :) >>> >>> '*ip6_net':'str', '*ip6_netsize':'int' >>> >>> passed on the wire as: >>> >>> "ip6_net":"fc00::1", "ip6_netsize":64 >> >> Err, so that means that the user would have to pass >> "ip6-net=3Dfc00::1,ip6_netsize=3D64"? This would look awkward, compar= ed to >> the ipv4 situation, which is a mere "net=3D10.0.2.2/24". >=20 > Err, yes. QMP is machine-parseable. HMP can let the user abbreviate t= o > net=3D10.0.2.2/24, but QMP should not require reparsing. So what if it= 's > longer, it's easier for machines to manipulate if it's already broken > into parts. Trust me - I wouldn't be asking you to split it into two > fields unless I thought that libvirt would much rather send it to you a= s > two fields. The command line, just like HMP, can use shorthand for convenience. I guess you do have a point about consistency of ipv4's @net requiring post-processing, but that doesn't mean we have to repeat the mistake for IPv6. --=20 Eric Blake eblake redhat com +1-919-301-3266 Libvirt virtualization library http://libvirt.org --oIbVfTP1RghXfm9gwlIGEmn19N8gh2Kb0 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.15 (GNU/Linux) Comment: Public key at http://people.redhat.com/eblake/eblake.gpg Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBCAAGBQJSZljbAAoJEKeha0olJ0NqfM8H/3fo7AQpRZTyUjm3LbZD0MZ7 VggY52PZlHtMz2Do8xndEYOaBdiQwC0PP5R9ec96+mkZElxZwAMALPIU4frug4hz Z1EmalwoTuNhTka6e7NC4aLd1XGc78XzYj/Tp0ynxrd3Fj3lB3SD5y1qg4ScEGT6 /gtnkdA5l/AT5xR5V2MP0FvaNJpoy2bnTDQ2vm+cYpmv6xAxJP4+A+kaO5O944F6 76dvjj5MSo3FaJqsNDUzsE00nmyO8DrtbaJ0MQ5NYcPUgnTvwFCSkf7OUZGPfppX tOH9KDehnpKjucmUoHBHKIG8aKfmteu+imv6SXdi8rCqbs8Rif/IA2PDnnFL9F4= =Lx3u -----END PGP SIGNATURE----- --oIbVfTP1RghXfm9gwlIGEmn19N8gh2Kb0--