This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/address-policy-wg@ripe.net/
[address-policy-wg] IPv6 access to K-root
- Previous message (by thread): [address-policy-wg] IPv6 access to K-root
- Next message (by thread): [address-policy-wg] IPv6 access to K-root
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Kurt Erik Lindqvist
kurtis at kurtis.pp.se
Sat Feb 26 20:21:47 CET 2005
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Feb 25, 2005, at 20:03, Elmar K. Bins wrote: > Contrast this with eleven/fifteen v4 sets on five unicast (provider PA) > and one anycast v4 (PI) address. So what you are _really_ arguing (or should be) is that you can get PA IPv4 but does not qualify for PA IPv6. That is something completely different, and I think we more or less have agreed in the RIPE region that this difference needs to be fixed... - - kurtis - -----BEGIN PGP SIGNATURE----- Version: PGP 8.1 iQA/AwUBQiDMTaarNKXTPFCVEQKV3ACgrjygZtuNmsMEvmkKr3C5tBDI/AUAnjAc eiqoDFUmFetqUbcu3+mwMInk =DEFZ -----END PGP SIGNATURE-----
- Previous message (by thread): [address-policy-wg] IPv6 access to K-root
- Next message (by thread): [address-policy-wg] IPv6 access to K-root
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]