[arin-ppml] ARIN-prop-127: Shared Transition Space for IPv4 Address Extension

Frank Bulk frnkblk at iname.com
Sat Jan 22 23:53:02 EST 2011

While new CPE gear could designed to support E space, what about all the
network devices between the CPE and the LSN?  On top of the CGN hardware,
network redesign, and extra support costs, service providers aren't looking
to force customers to use newer CPE gear.  Plus who says they can get the
CPE vendors to even go along with this E space change?  


-----Original Message-----
From: arin-ppml-bounces at arin.net [mailto:arin-ppml-bounces at arin.net] On
Behalf Of George Bonser
Sent: Saturday, January 22, 2011 6:27 PM
To: Jack Bates
Cc: arin-ppml at arin.net
Subject: Re: [arin-ppml] ARIN-prop-127: Shared Transition Space for IPv4
Address Extension

> I'm afraid E has been so polluted by code restraints, there is no
> proper
> recovery of it. You're asking for a support nightmare.
> Jack

I don't believe so.  So lets say Vendor C produces both a line of NAT
devices and a line of CPE that supports the use of E space.  Now lets
say other vendors in their newer gear (and software updates for their
older gear) also support E space.

Now you won't necessarily be able to renumber people out of their
current global space in all cases. But you can keep the problem from
getting worse by specifying the CPE for NEW connections that does
support it.  Anyone attempting to use such space internally will find
that their workstations and servers won't work with it.

More information about the ARIN-PPML mailing list