From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:47156) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VYZVc-00074Z-ID for qemu-devel@nongnu.org; Tue, 22 Oct 2013 06:48:25 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1VYZVX-00070d-Lo for qemu-devel@nongnu.org; Tue, 22 Oct 2013 06:48:20 -0400 Received: from mx1.redhat.com ([209.132.183.28]:61418) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VYZVX-00070M-CY for qemu-devel@nongnu.org; Tue, 22 Oct 2013 06:48:15 -0400 Message-ID: <526657E9.9080208@redhat.com> Date: Tue, 22 Oct 2013 11:48:09 +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> In-Reply-To: <20131022104504.GS5518@type.wlan.youpi.perso.aquilenet.fr> Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="skV2lTkMppKdjk7EjqUqIPjw61gCjd9hR" 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) --skV2lTkMppKdjk7EjqUqIPjw61gCjd9hR Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On 10/22/2013 11:45 AM, Samuel Thibault wrote: >>> 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 >=20 > Err, so that means that the user would have to pass > "ip6-net=3Dfc00::1,ip6_netsize=3D64"? This would look awkward, compare= d to > the ipv4 situation, which is a mere "net=3D10.0.2.2/24". Err, yes. QMP is machine-parseable. HMP can let the user abbreviate to 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 as two fields. --=20 Eric Blake eblake redhat com +1-919-301-3266 Libvirt virtualization library http://libvirt.org --skV2lTkMppKdjk7EjqUqIPjw61gCjd9hR 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/ iQEcBAEBCAAGBQJSZlfpAAoJEKeha0olJ0NqAXsH/jUCfgH66Fs2sjnoYIlRQYcU X+A6nFtnqEfzrt5Wh2wFTDlhH18kPtKVFBJYkwfF3BjM3y7aHuYSTq8NhUTLe0qk hYvktEiPKZWylG2jmgLZ+9jSZYzwoanh0YUqY4U1mT+hE607fo7lV2cQAzHXapjI UDRNxH3Drbbasaw0fhCoq7J2qb/jxX/ROZG9PlaGUBVKDAOWqBJeqvXPdNHvgAXq 7SfKp7gRta2P5aUjWeGYqzTW4TQJlVAFfvTMj7aARKB7LbZnly2LdzNCj/sFjB7A wnmeYE4fBcxayLdPW/BuoywqtsXeQedVFvKDlXUvYowtB3HygQiM4YbpxFn1Vzs= =TfiC -----END PGP SIGNATURE----- --skV2lTkMppKdjk7EjqUqIPjw61gCjd9hR--