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/[email protected]/
[address-policy-wg] Policy Proposal #eta : IPv6 Address Allocation and Assignment Policy - definition for "End-Site
- Previous message (by thread): [address-policy-wg] Policy Proposal #eta : IPv6 Address Allocation and Assignment Policy - definition for "End-Site
- Next message (by thread): [address-policy-wg] Policy Proposal #eta : IPv6 Address Allocation and Assignment Policy - definition for "End-Site
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Randy Bush
randy at psg.com
Mon Jul 11 19:47:08 CEST 2005
> RFC3879 deprecates "site-local" addresses for IPv6. I'm told > that the thinking is that sites should fence off a part of their > globally-routable IPv6 assignment for any "enterprise-local" > requirements they may have. the thinking at the time of killing site-local addresses was that, as they were specified, they had very complex and ill-thought-out routing implications (somewhat typical of the ivtf's ipv6 effort). >> What should they do, use some random number? > 2002:0a00/24 anyone? if they are really not connecting, why do we or they care? if they might be connecting, then we have to make some decisions. randy
- Previous message (by thread): [address-policy-wg] Policy Proposal #eta : IPv6 Address Allocation and Assignment Policy - definition for "End-Site
- Next message (by thread): [address-policy-wg] Policy Proposal #eta : IPv6 Address Allocation and Assignment Policy - definition for "End-Site
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]