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] 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] Re: 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:05:40 CEST 2005
>> classically, if they have no plan to be connected, they don't get >> address space. > ...and do you think this is how it should be? in ipv4, yes. in ipv6, i am ambivalent. i don't believe v6 space is effectively so vast it can be wasted, especially with magic boundaries at /64 and /48. i also don't believe in site-local routing. though it was called site local _addressing_. the ivtf keeps confusing addressing and routing and neglecting the interactions and the implications. but i have no problem with an rfc 1918 equivalent in ipv6. on the other hand, it's can be fun to ask the question this way. since you will never be connected to the internet, why not just use whatever address space comes to mind? oh, you're worried about collisions? with whom? you said you were not connecting to the internet. 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] Re: Policy Proposal #eta : IPv6 Address Allocation and Assignment Policy - definition for "End-Site
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]