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
- Previous message (by thread): [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 ]
Sander Steffann
s.steffann at computel.nl
Tue May 29 10:26:01 CEST 2007
Note: soryr for the previous message, I hit the wrong key and sent it by accident Hi Randy, > ok, i give. if ula address space is assigned/managed by > registries, how is it actually different from pi space? Basically ULA space has the same 'routability' as RFC1918 space, with the added benefit of less (or in case of ULA central: no) possibility for conflicting addresses when merging/connecting separate networks. PI space is expected to be routed globally (if the user of the space wants to). > if ipv6 space is effectively infinite (and we once thought ipv4 space > was), then what is the use of ula address space? why not just assign > vanilla ipv6 space? At this moment there is no IPv6 PI space (yet) in the RIPE region. When there is PI space, there will maybe be recurring costs for it (RIPE policy proposal 2007-01 is in discussion now). ULA space is free to use and has a low possibility of conflicts, and ULA Central will probably have one-time fee and is globally unique. So the main reason will probably be cost... - Sander
- Previous message (by thread): [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 ]