[130944] in North American Network Operators' Group
Re: Definitive Guide to IPv6 adoption
daemon@ATHENA.MIT.EDU (Owen DeLong)
Mon Oct 18 14:11:32 2010
From: Owen DeLong <owen@delong.com>
In-Reply-To: <4CBC7B6E.6000409@bogus.com>
Date: Mon, 18 Oct 2010 11:05:26 -0700
To: Joel Jaeggli <joelja@bogus.com>
Cc: nanog@nanog.org
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
On Oct 18, 2010, at 9:53 AM, Joel Jaeggli wrote:
> On 10/18/10 9:33 AM, Tony Hain wrote:
>> This 'get a /32' BAD ADVICE has got to stop. There are way too many =
people
>> trying to force fit their customers into a block that is intended for =
a
>> start-up with ZERO customers.
>>=20
>> Develop a plan for /48 per customer, then go to ARIN and get that =
size
>> block.=20
>=20
> Develop a plan, consider the prior art, consider the possibly that you
> might deploy 6rd, consider what your peers are doing, consider the
> projections for your business. Go to arin with a request that meets =
your
> current and anticipated needs and that is defensible.
>=20
> don't decide without thinking it through that you're assigning a
> customer a /64 a /60 a /56 or even /48. this should be defensible as
> part of a business plan, otherwise what's the point?
>=20
A /48 is defensible. It's the architecturally intended end-site =
configuration,
it is allowed by policy, and, it is a reasonable starting point. There =
is no
real reason to assign less than a /48 to any end-site other than hyper-
conservatism due to IPv4-think.
Owen
>> Figure out exactly what you are going to assign to customers later,
>> but don't tie your hands by asking for a block that is way too small =
to
>> begin with. Any ISP with more than 30k customers SHOULD NOT have a =
/32, and
>> if they got one either trade it in or put it in a lab and get a REAL =
block.=20
>>=20
>> Tony
>>=20
>>=20
>>> -----Original Message-----
>>> From: Brandon Kim [mailto:brandon.kim@brandontek.com]
>>> Sent: Saturday, October 16, 2010 1:59 PM
>>> To: nanog@nanog.org
>>> Subject: RE: Definitive Guide to IPv6 adoption
>>>=20
>>>=20
>>> Thanks everyone who responded. This list is such a valuable wealth =
of
>>> information.
>>>=20
>>> Apparently I was wrong about the /64 as that should be /32 so thanks
>>> for that correction....
>>>=20
>>> Thanks again especially on a Saturday weekend!
>>>=20
>>>=20
>>>=20
>>>> From: rdobbins@arbor.net
>>>> To: nanog@nanog.org
>>>> Date: Sat, 16 Oct 2010 16:09:43 +0000
>>>> Subject: Re: Definitive Guide to IPv6 adoption
>>>>=20
>>>>=20
>>>> On Oct 16, 2010, at 10:56 PM, Joel Jaeggli wrote:
>>>>=20
>>>>> Then move on to the Internet which as with most things is where =
the
>>> most cuurent if not helpful information resides.
>>>>=20
>>>>=20
>>>> Eric Vyncke's IPv6 security book is definitely worthwhile, as well,
>>> in combination with Schudel & Smith's infrastructure security book =
(the
>>> latter isn't IPv6-specific, but is the best book out there on
>>> infrastructure security):
>>>>=20
>>>> <http://www.ciscopress.com/bookstore/product.asp?isbn=3D1587055945>
>>>>=20
>>>> <http://www.ciscopress.com/bookstore/product.asp?isbn=3D1587053365>
>>>>=20
>>>> =
---------------------------------------------------------------------
>>> --
>>>> Roland Dobbins <rdobbins@arbor.net> // =
<http://www.arbornetworks.com>
>>>>=20
>>>> Sell your computer and buy a guitar.
>>>>=20
>>>>=20
>>>>=20
>>>>=20
>>>>=20
>>> =3D
>>=20
>>=20
>=20
