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 Policy Clarification - Initial allocation criteria "d)"
- Previous message (by thread): [address-policy-wg] IPv6 Policy Clarification - Initial allocation criteria "d)"
- Next message (by thread): [address-policy-wg] IPv6 Policy Clarification - Initial allocation criteria "d)"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Kurt Erik Lindqvist
kurtis at kurtis.pp.se
Tue Jun 22 13:39:30 CEST 2004
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2004-06-22, at 09.59, Gert Doering wrote: > I can't see the connection. The whole point of the multi6 group is > to find multihoming solutions that do *not* need a global routing table > slot. Well, they will need a global routing table slot, but preferably not more than one :-) - - kurtis - -----BEGIN PGP SIGNATURE----- Version: PGP 8.0.3 iQA/AwUBQNgadaarNKXTPFCVEQKDlQCg45zioLuVEJ23LaLFbEuWh/2WeRQAoKQF 7W5N2tArVmQpzd9GIemhUZU7 =q+GO -----END PGP SIGNATURE-----
- Previous message (by thread): [address-policy-wg] IPv6 Policy Clarification - Initial allocation criteria "d)"
- Next message (by thread): [address-policy-wg] IPv6 Policy Clarification - Initial allocation criteria "d)"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]