[175091] in North American Network Operators' Group
Re: IPv6 Default Allocation - What size allocation are you giving out
daemon@ATHENA.MIT.EDU (Owen DeLong)
Thu Oct 9 03:30:19 2014
X-Original-To: nanog@nanog.org
From: Owen DeLong <owen@delong.com>
In-Reply-To: <1627782497.131675.1412827629110.JavaMail.zimbra@snappytelecom.net>
Date: Thu, 9 Oct 2014 00:26:55 -0700
To: Faisal Imtiaz <faisal@snappytelecom.net>
Cc: NANOG <nanog@nanog.org>
Errors-To: nanog-bounces@nanog.org
I=92ll go a step further=85
If you give a residential customer the /48 that they should be getting, =
then as DHCP-PD and automatic topologies become more widespread, you =
have enabled flexibility in the breadth and depth of the bit patterns =
used to facilitate such hierarchies in the home network environment. If =
you limit them to 8 bits of subnetting, you are very limited in the =
constructs (1x8, 2x4, 4x2, or 8x1) which can be achieved.
Further, there=92s really no advantage to keeping so much extra IPv6 =
address space on the shelves long past the expiration of the protocol=92s =
useful life. I guarantee you that unless we start doing really stupid =
things (like using IPv6 /48s as serial numbers for cars), giving /48s to =
residential customers will not exhaust the current /3 (1/8th of the =
total IPv6 space) before we hit some other limitation of the protocol.
Owen
On Oct 8, 2014, at 9:07 PM, Faisal Imtiaz <faisal@snappytelecom.net> =
wrote:
> Like I said, this was my understanding.... I am glad that it is being =
pointed out to be in-correct....=20
>=20
> I don't have a reason for why a /64 as much as I also don't have any =
reason Why NOT....=20
>=20
> So, let me ask the question in a different manner...=20
> What is the wisdom / reasoning behind needing to give a /56 to a =
Residential customer (vs a /64).=20
>=20
> Regards.=20
>=20
> Faisal Imtiaz=20
> Snappy Internet & Telecom=20
> ----- Original Message -----
>=20
>> From: "Sam Silvester" <sam.silvester@gmail.com>
>> To: "Faisal Imtiaz" <faisal@snappytelecom.net>
>> Cc: "Erik Sundberg" <ESundberg@nitelusa.com>, "NANOG" =
<nanog@nanog.org>
>> Sent: Wednesday, October 8, 2014 11:47:01 PM
>> Subject: Re: IPv6 Default Allocation - What size allocation are you =
giving
>> out
>=20
>> Why would you only allocate a residential customer a single /64?
>=20
>> That's totally short sighted in my view.
>=20
>> On Thu, Oct 9, 2014 at 2:07 PM, Faisal Imtiaz < =
faisal@snappytelecom.net >
>> wrote:
>=20
>>> We are going thru a similar process.. from all of my reading, best =
practice
>>> discussions etc..
>>=20
>=20
>>> Here is what i have understood so far:-
>>=20
>=20
>>> Residential Customers: /64
>>=20
>=20
>>> Small & Medium size Business Customers: /56
>>=20
>=20
>>> Large Business size or a multi-location Business Customer: /48
>>=20
>=20
>>> Don't skimp on allocating the subnets like we do on IPv4
>>=20
>>> Better to be 'wasteful' than have to come back to re-number or =
re-allocate
>>> .
>>=20
>=20
>>> Regards
>>=20
>=20
>>> Faisal Imtiaz
>>=20
>>> Snappy Internet & Telecom
>>=20
>=20
>>> ----- Original Message -----
>>=20
>>>> From: "Erik Sundberg" < ESundberg@nitelusa.com >
>>=20
>>>> To: nanog@nanog.org
>>=20
>>>> Sent: Wednesday, October 8, 2014 9:18:16 PM
>>=20
>>>> Subject: IPv6 Default Allocation - What size allocation are you =
giving
>>>> out
>>=20
>>>>=20
>>=20
>>>> I am planning out our IPv6 deployment right now and I am trying to =
figure
>>>> out
>>=20
>>>> our default allocation for customer LAN blocks. So what is everyone
>>>> giving
>>=20
>>>> for a default LAN allocation for IPv6 Customers. I guess the idea =
of
>>=20
>>>> handing a customer /56 (256 /64s) or a /48 (65,536 /64s) just makes =
me
>>=20
>>>> cringe at the waste. Especially when you know 90% of customers will =
never
>>=20
>>>> have more than 2 or 3 subnets. As I see it the customer can always =
ask
>>>> for
>>=20
>>>> more IPv6 Space.
>>=20
>>>>=20
>>=20
>>>> /64
>>=20
>>>> /60
>>=20
>>>> /56
>>=20
>>>> /48
>>=20
>>>>=20
>>=20
>>>> Small Customer?
>>=20
>>>> Medium Customer?
>>=20
>>>> Large Customer?
>>=20
>>>>=20
>>=20
>>>> Thanks
>>=20
>>>>=20
>>=20
>>>> Erik
>>=20
>>>>=20
>>=20
>>>> ________________________________
>>=20
>>>>=20
>>=20
>>>> CONFIDENTIALITY NOTICE: This e-mail transmission, and any =
documents,
>>>> files
>>>> or
>>=20
>>>> previous e-mail messages attached to it may contain confidential
>>>> information
>>=20
>>>> that is legally privileged. If you are not the intended recipient, =
or a
>>=20
>>>> person responsible for delivering it to the intended recipient, you =
are
>>=20
>>>> hereby notified that any disclosure, copying, distribution or use =
of any
>>>> of
>>=20
>>>> the information contained in or attached to this transmission is =
STRICTLY
>>=20
>>>> PROHIBITED. If you have received this transmission in error please =
notify
>>=20
>>>> the sender immediately by replying to this e-mail. You must destroy =
the
>>=20
>>>> original transmission and its attachments without reading or saving =
in
>>>> any
>>=20
>>>> manner. Thank you.
>>=20
>>>>=20
>>=20
