On Oct 16, 2010, at 5:22 PM, Franck Martin wrote:

> You give a /64 to the end users (home/soho), and /48 to multi homed 
> organization (or bigger orgs that use more than one network internally) and 
> get a /32 if you are an ISP.
> 
Please DON'T do that. End users (home/soho) should get at least a /56 and 
ideally a /48. The standards and the RIR policies both allow for 
end-users/sites to get /48s.

If you are an ISP, you get AT LEAST a /32.

> See also the discussion about what to use in p2p links.
> 
Yep. Personally, I like the /64 per subnet including p2p link approach. Others 
have different opinions.

Owen

> ----- Original Message -----
> From: "Brandon Kim" <brandon....@brandontek.com>
> To: nanog@nanog.org
> Sent: Sunday, 17 October, 2010 8:58:57 AM
> Subject: RE: Definitive Guide to IPv6 adoption
> 
> 
> Thanks everyone who responded. This list is such a valuable wealth of 
> information.
> 
> Apparently I was wrong about the /64 as that should be /32 so thanks for that 
> correction....
> 
> Thanks again especially on a Saturday weekend!
> 
> 
> 
>> From: rdobb...@arbor.net
>> To: nanog@nanog.org
>> Date: Sat, 16 Oct 2010 16:09:43 +0000
>> Subject: Re: Definitive Guide to IPv6 adoption
>> 
>> 
>> On Oct 16, 2010, at 10:56 PM, Joel Jaeggli wrote:
>> 
>>> Then move on to the Internet which as with most things is where the most 
>>> cuurent if not helpful information resides.
>> 
>> 
>> 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):
>> 
>> <http://www.ciscopress.com/bookstore/product.asp?isbn=1587055945>
>> 
>> <http://www.ciscopress.com/bookstore/product.asp?isbn=1587053365>
>> 
>> -----------------------------------------------------------------------
>> Roland Dobbins <rdobb...@arbor.net> // <http://www.arbornetworks.com>
>> 
>>             Sell your computer and buy a guitar.
>> 
>> 
>> 
>> 
>> 
>                                         


Reply via email to