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/
[ppml] [address-policy-wg] Those pesky ULAs again
- Next message (by thread): [ppml] [address-policy-wg] Those pesky ULAs again
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Iljitsch van Beijnum
iljitsch at muada.com
Fri Jun 1 18:44:18 CEST 2007
On 30-mei-2007, at 18:22, Paul_Vixie at isc.org wrote: > first, ARIN does not currently consider routability when allocating > address space. Hm: http://www.arin.net/policy/nrpm.html 6.3.4. Aggregation Wherever possible, address space should be distributed in a hierarchical manner, according to the topology of network infrastructure. This is necessary to permit the aggregation of routing information by ISPs, and to limit the expansion of Internet routing tables. This goal is particularly important in IPv6 addressing, where the size of the total address pool creates significant implications for both internal and external routing. The whole "routing is not guaranteed" thing is obviously in there because of the lawyers since ARIN can't force ISPs to route any given block of address space, not because routability isn't a goal. > non-routable space comes from ietf/iana, not the RIRs. > so, for ARIN to start allocating nonroutable space is a big change. Keeping the RIRs out of the ULA business would nicely avoid any problems resulting from that. Just let the domain sell the ip6.arpa domains in question. > (heck, maybe the old site-local prefix is still available.) http://www.ietf.org/rfc/rfc3879.txt Existing implementations and deployments MAY continue to use this prefix.
- Next message (by thread): [ppml] [address-policy-wg] Those pesky ULAs again
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]