[117855] in North American Network Operators' Group
Re: ISP customer assignments
daemon@ATHENA.MIT.EDU (Jens Link)
Mon Oct 5 14:19:01 2009
To: <nanog@nanog.org>
From: Jens Link <lists@quux.de>
Date: Mon, 05 Oct 2009 20:18:23 +0200
In-Reply-To: <29A54911243620478FF59F00EBB12F4701A60AD3@ex01.drtel.lan> (Brian
Johnson's message of "Mon\, 5 Oct 2009 11\:08\:30 -0500")
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
"Brian Johnson" <bjohnson@drtel.com> writes:
> So a customer with a single PC hooked up to their broad-band connection
> would be given 2^64 addresses?
>
> I realize that this is future proofing, but OMG! That=92s the IPv4
> Internet^2 for a single device!
Most people will have more than one device. And there is no NAT as you
know it from IPv4 (and hopefully there never will be. I had to
troubleshoot a NAT related problem today and it wasn't fun.[1])
And I want more than one network I want to have a firewall between my
fridge and my file server.
> Am I still seeing/reading/understanding this correctly?
RFC 3177 suggest a /48.=20
Forget about IPv4 when assigning IPv6 Networks to customers. Think big an
take a one size fits all(most) customers approach. Assign a /48 or /56 to
your customers and they will never ask you about additional IPs
again. This make Documentation relay easy. ;-)
cheers=20
Jens
[1] Everybody who claims that NAT is easy should have his or her head
examined.
--=20
-------------------------------------------------------------------------
| Foelderichstr. 40 | 13595 Berlin, Germany | +49-151-18721264 |
| http://www.quux.de | http://blog.quux.de | jabber: jenslink@guug.de |
-------------------------------------------------------------------------
