[154936] in North American Network Operators' Group
Re: using "reserved" IPv6 space
daemon@ATHENA.MIT.EDU (Karl Auer)
Tue Jul 17 03:16:07 2012
From: Karl Auer <kauer@biplane.com.au>
To: NANOG List <nanog@nanog.org>
In-Reply-To: <894EB7FC-A18C-41BA-A778-85564632FC8E@delong.com>
Date: Tue, 17 Jul 2012 17:15:00 +1000
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
--=-K+RwXOmBvmjKru/6V7SK
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
On Mon, 2012-07-16 at 23:36 -0700, Owen DeLong wrote:
> Reread the spec... [the subnet router anycast address] gets the packet
> to one or more of the routers and it may well lead to packet
> duplication. There may or may not be coordination between the
> routers. It isn't in the spec.
Which spec? Looking at RFC 4291, Section 2.6.1:
Packets sent to the Subnet-Router anycast address will be delivered
to one router on the subnet. All routers are required to support the
Subnet-Router anycast addresses for the subnets to which they have
interfaces.
The Subnet-Router anycast address is intended to be used for
applications where a node needs to communicate with any one of the
set of routers.
But I do not have an encylopaedic knowledge of all the RFCs, so perhaps
this has been superseded, obsoleted or updated...
Reading it with a squint: The phrase "packets [...] will be delivered to
one router on the subnet" does not specifically exclude the possibility
that packets will be delivered to more than one router on the subnet.
Still, I do think it would be a little unreasonable to interpret it
thus.
Regards, K.
--=20
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Karl Auer (kauer@biplane.com.au)
http://www.biplane.com.au/kauer
GPG fingerprint: AE1D 4868 6420 AD9A A698 5251 1699 7B78 4EEE 6017
Old fingerprint: DA41 51B1 1481 16E1 F7E2 B2E9 3007 14ED 5736 F687
--=-K+RwXOmBvmjKru/6V7SK
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: This is a digitally signed message part
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
iF4EABEIAAYFAlAFEPQACgkQFpl7eE7uYBdemgEAkKQceU7v6OJ36tGCIWpQpPHC
A/YdFtmEEll1yNm8yHgA/i090kNGEGRKjt8eMVywIieR5b6tysXJaXgXa2WbyHv+
=nu2P
-----END PGP SIGNATURE-----
--=-K+RwXOmBvmjKru/6V7SK--
