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] Re: IPv6 PI
- Previous message (by thread): [address-policy-wg] Re: IPv6 PI
- Next message (by thread): [address-policy-wg] Re: IPv6 PI
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Lea Roberts
lea.roberts at stanford.edu
Mon Nov 21 18:40:08 CET 2005
On Mon, 21 Nov 2005, Elmar K. Bins wrote: > lea.roberts at stanford.edu (Lea Roberts) wrote: > > > this was the original ARIN proposal 2005-1, which could not reach > > consensus. The last time around it was re-worked to add more restrictions > > and again failed because other folks felt it was too restrictive. There > > are actually two issues: > > > > 1) the high cost of renumbering in a large organization > > Why should they renumber, if it's their own block? the point is that current policy only allocates to organizations who commit to assigning space to other organizations and perhaps a case could be made for a limited number of large organizations to qualify for a PI block of IPv6 addresses. the trick is finding the criteria which can reach consensus as "fair" but not "too complicated". such a policy would encourage IPv6 adoption in these large organizations, many of whom are unwilling to deploy it using PA addresses. > > 2) multi-homing for network reliability and resiliency > > Where's the problem here? Someone who can afford and establish > a case for _real_ multihoming can get an ASN and thus an assignment. > > Like was already said - loosening the ASN handout rules needs changes > in assignment rules, too. But that's for years to come. see also my reply to Michael Dillon. there is a legitimate fairness argument about trying to find policies that work into the future rather than policies that need to be made more restrictive later. We've already done that and prefer to make different mistakes this time. it's harder! there is no question that the easy way out is just give everyone the equivalent (or more :-) than they currently have in IPv4. that will work for now and some time into the future. sure. but why not design a future that is built to scale reliably? it's really time to try to get rid of the IPv4 mindset!! there will have to be new and better ways of solving how to use multiple providers than everybody's route going into the global routing table. some work is being done now and it's good to keep pointing out the need for creative and scaleable solutions. let's encourage the right solutions rather than short term work-arounds... /Lea
- Previous message (by thread): [address-policy-wg] Re: IPv6 PI
- Next message (by thread): [address-policy-wg] Re: IPv6 PI
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]