[158790] in North American Network Operators' Group
Re: Why do some providers require IPv6 /64 PA space to have public
daemon@ATHENA.MIT.EDU (Owen DeLong)
Tue Dec 11 03:37:25 2012
From: Owen DeLong <owen@delong.com>
In-Reply-To: <20121211000758.A49922CE1084@drugs.dv.isc.org>
Date: Tue, 11 Dec 2012 00:31:50 -0800
To: Mark Andrews <marka@isc.org>
Cc: "Constantine A. Murenin" <mureninc@gmail.com>,
"nanog@nanog.org" <nanog@nanog.org>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
On Dec 10, 2012, at 4:07 PM, Mark Andrews <marka@isc.org> wrote:
>=20
> In message <272782D1-8DEA-4718-9429-8B0505DD30BD@delong.com>, Owen =
DeLong write
> s:
>>=20
>>=20
>> Sent from my iPad
>>=20
>> On Dec 10, 2012, at 3:02 PM, Mark Andrews <marka@isc.org> wrote:
>>=20
>>> =3D20
>>> In message <50C65C84.6080203@dougbarton.us>, Doug Barton writes:
>>>> On 12/10/2012 01:27 PM, Schiller, Heather A wrote:
>>>>> I think most folks would agree that, IPv4 /32 :: IPv6 /128 as IPv4 =
/29 :=3D
>> : I
>>>> Pv6 /64
>>>> =3D20
>>>> Quite the opposite in fact. In IPv6 a /64 is roughly equivalent to =
a /32
>>>> in IPv4. As in, it's the smallest possible assignment that will =
allow an
>>>> end-user host to function under normal circumstances.
>>>> =3D20
>>>> SWIP or rwhois for a /64 seems excessive to me, FWIW.
>>>> =3D20
>>>> Doug
>>> =3D20
>>> Even SWIP for a /48 for a residential assignment is excessive.
>>> SWIP for a /48 for a commercial assignment is reasonable
>>> =3D20
>>=20
>> I disagree. SWIP for a /48 with the appropriate notations under =
residential c
>> =3D
>> ustomer privacy policy provides a good balance between the need for =
public a=3D
>> ccountability of resource utilization and privacy concerns for =
residential c=3D
>> ustomer assignments.
>>=20
>> Owen
>=20
> You don't SWIP each residential customer with IPv4. You often SWIP =
blocks
> of residential customers down to the pop level.
> You often SWIP each commercial customer with IPv4.
>=20
You SWIP each one that gets a /29 or larger.
> To require a SWIP entry for each residential customer is bureaucracy
> gone mad. Additionally there is no technical need for this. It
> isn't needed for address accountability. Residential customers
> have historically been treated in bulk.
>=20
It really isn't. We can agree to disagree, as we usually do. It's
quite easily automated and it really is the equivalent to current IPv4
policy. The difference being only that in IPv6, we expect more customers
to get networks instead of host addresses.
Owen
