[154873] in North American Network Operators' Group
Re: using "reserved" IPv6 space
daemon@ATHENA.MIT.EDU (Owen DeLong)
Sun Jul 15 06:16:30 2012
From: Owen DeLong <owen@delong.com>
In-Reply-To: <1342338639.10346.1981.camel@pc2>
Date: Sun, 15 Jul 2012 03:13:59 -0700
To: Laurent GUERBY <laurent@guerby.net>
Cc: nanog@nanog.org
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
On Jul 15, 2012, at 12:50 AM, Laurent GUERBY wrote:
> Hi,
>=20
> On Sat, 2012-07-14 at 17:02 -0700, Owen DeLong wrote:
>>> Hi,
>>>=20
>>> We use LLA to "virtualize" interconnection to our users:
>>> their network configuration is always static default via fe80::nnnn
>>> and we route their /56 prefix to fe80::xxxx:yyyy where xxxx:yyyy is
>>> unique per user - if our user want to do some routing of course. =
Since
>>> we don't have GUA interconnections we don't have to manage them =
inside
>>> our AS and we can move user stuff around without having them =
changing
>>> anything to their static configuration.
>>>=20
>>> We give a /56 IPv6 per /32 IPv4 to our user which does /48 =3D /24 =3D=
256
>>> "IP", it's nice to have more than one /64 around for some uses.
>>>=20
>>> Is there any "mass" hoster around that does provide by default a =
pefix
>>> larger than /64 and that does route it to the user? It's quite =
simple to
>>> do in IPv6 and we have the address space for it.
>=20
>> Why not just give each end-site a /48?
>=20
> We give a /48 on request, a /56 by default (and we never give a /64).
>=20
>> An end-site with a /24 may only need a single or a few subnets while =
an end-site with a /32 may have a host of subnets behind their IPv4 NAT =
gateway. Making IPv6 topological assumptions for your end-users based on =
their IPv4 presentation makes little sense to me and is likely a =
disservice to your end users.
>=20
> The /56 subnets we give are for single machine in a rack, virtual
> machine in a cluster or home router.
>=20
> http://www.tunnelbroker.net/ gives by default /64 to a home router
> and /48 on request we just decided to give /56 by default
> and /48 on request.
>=20
> Sorry if I wasn't clear in my first message.
>=20
> Is there an agreed upon definition of "end site"?
>=20
Not exactly, but, there is now an ARIN definition for ARIN address =
policy.
An end site (IIRC since I wrote the ARIN definition) is a single =
building or structure or a single tenant in a multi-tenant building or =
structure.
So, if you have a university campus with 23 buildings, that might be 23 =
end sites. However, if one of them is a dormitory which has 100 rental =
units, that would up the end-site count to 122. If one of those =
buildings houses the math department, the physics department, and the =
science department, that might bring the total up as high as 124.
Make sense?
Owen
