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] 200 customer requirements for IPv6
- Previous message (by thread): [address-policy-wg] 200 customer requirements for IPv6
- Next message (by thread): [address-policy-wg] 200 customer requirements for IPv6
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Thomas Narten
narten at us.ibm.com
Fri Nov 18 15:17:32 CET 2005
> To all the nay-sayers and ignorants in the die-hard IPv6 camp I can only > recommend that they put yourself into the shoes of a large coporation > with 10,000 employees for a day. How many 10K employee organizations exist in the world today (or in ten years)? How many routing prefixes would be required in the DFZ to support this? Can the routing infrastructure handle that? If there were consensus that the answer to the above questions was "yes, it's manageable", I'm sure folk would support a modified policy to that effect in a heartbeat. But in the absence of some real data showing the implication of loosening the policy to allow the above, many (myself include) will be very concerned about the consequences of doing this. Thomas
- Previous message (by thread): [address-policy-wg] 200 customer requirements for IPv6
- Next message (by thread): [address-policy-wg] 200 customer requirements for IPv6
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]