[175128] in North American Network Operators' Group
Re: IPv6 Default Allocation - What size allocation are you giving out
daemon@ATHENA.MIT.EDU (Faisal Imtiaz)
Thu Oct 9 13:15:12 2014
X-Original-To: nanog@nanog.org
Date: Thu, 9 Oct 2014 17:15:01 +0000 (GMT)
From: Faisal Imtiaz <faisal@snappytelecom.net>
To: Owen DeLong <owen@delong.com>
In-Reply-To: <5E33293C-2094-4779-B1DF-5FC89B07B7E5@delong.com>
Cc: nanog@nanog.org
Errors-To: nanog-bounces@nanog.org
> > Question: Should we be asking ARIN for another /32 so that each networ=
k
> > has it's own /32 or should be break out the /32 into /36 and use these=
in
> > each of the geographies ?
>=20
> Depends on your needs=E2=80=A6 Either is a viable solution, depending on =
your
> circumstances. ARIN has an MDN policy which would facilitate your
> acquisition of a second /32.
>
Thank you Owen, just got off the phone with ARIN, it should be a fairly sim=
ple process for us, and we will follow the advice of using a /32 for each g=
eographical location.
The overall discussion has been a very interesting one, and it would appear=
that the majority of the forward looking opinion is to allocate /48 to cus=
tomers, and don't do any smaller subnet allocation.
We will take this advice and re-evaluate our policies.
Regards.
Faisal Imtiaz
Snappy Internet & Telecom
7266 SW 48 Street
Miami, FL 33155
Tel: 305 663 5518 x 232
Help-desk: (305)663-5518 Option 2 or Email: Support@Snappytelecom.net=20
----- Original Message -----
> From: "Owen DeLong" <owen@delong.com>
> To: "Faisal Imtiaz" <faisal@snappytelecom.net>
> Cc: "William Herrin" <bill@herrin.us>, nanog@nanog.org
> Sent: Thursday, October 9, 2014 12:20:14 PM
> Subject: Re: IPv6 Default Allocation - What size allocation are you givin=
g out
>=20
>=20
> On Oct 9, 2014, at 7:31 AM, Faisal Imtiaz <faisal@snappytelecom.net> wrot=
e:
>=20
> >>> Selection of a default prefix is easy. Here are the steps.
> >>>=20
> >>> 4. Keeping in mind
> >>>=20
> >>> 4.1 Prefixes longer than somewhere around /48 to /56 may be
> >>> excluded from the global routing table
> >>=20
> >> 4.1a Prefix cutouts of any size (including /48) from inside your /32
> >> or larger block may be excluded from the global routing table. Folks
> >> who are multihomed and thus need to advertise their own block with BGP
> >> should be referred to ARIN for a direct assignment. Folks who aren't
> >> multihomed, well, until given evidence otherwise I claim there are no
> >> single-homed entities who will use 65,000 LANs, let alone more.
> > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> >=20
> > This brings up another interesting question...
> >=20
> > We operate Two separate networks in two geographical locations (Two ASN=
),
> > we have a single /32 allocation from ARIN.
> >=20
> > Question: Should we be asking ARIN for another /32 so that each networ=
k
> > has it's own /32 or should be break out the /32 into /36 and use these=
in
> > each of the geographies ?
>=20
> Depends on your needs=E2=80=A6 Either is a viable solution, depending on =
your
> circumstances. ARIN has an MDN policy which would facilitate your
> acquisition of a second /32.
>=20
> Owen
>=20
>
