[125170] in North American Network Operators' Group

home help back first fref pref prev next nref lref last post

Re: ARIN IP6 policy for those with legacy IP4 Space

daemon@ATHENA.MIT.EDU (John Curran)
Fri Apr 9 13:55:32 2010

X-Report-Abuse-To: abuse@dyndns.com (see
	http://www.dyndns.com/services/mailhop/outbound_abuse.html for
	abuse reporting information)
From: John Curran <jcurran@istaff.org>
In-Reply-To: <3C21D416-1009-4F93-A6BF-D8995E91DD25@virtualized.org>
Date: Fri, 9 Apr 2010 13:55:17 -0400
To: David Conrad <drc@virtualized.org>
Cc: NANOG list <nanog@nanog.org>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org

On Apr 9, 2010, at 1:26 PM, David Conrad wrote:
> Doesn't end user PI assignment already do this?  Note I'm not arguing =
against end user PI assignment policy, rather just making the =
observation that given IPv6 did not address routing scalability, the =
path we're heading down is obvious, the only question is how fast.=20

David,

The ISPs participating in ARIN get to disusss the impact of various =
allocation=20
thresholds on their routing during the policy development process.

If you have a magic vendor machine issuing prefixes to all comers =
regardless
of need, then the routing scalability problem becomes much, much =
poignant,=20
and the ability of the community to course correct is zero.

/John



home help back first fref pref prev next nref lref last post