[75171] in North American Network Operators' Group
Re: Important IPv6 Policy Issue -- Your Input Requested
daemon@ATHENA.MIT.EDU (Daniel Roesen)
Mon Nov 8 16:17:04 2004
Date: Mon, 8 Nov 2004 22:15:13 +0100
From: Daniel Roesen <dr@cluenet.de>
To: nanog@merit.edu
Mail-Followup-To: nanog@merit.edu
In-Reply-To: <6.1.2.0.2.20041108153505.069cc5c0@mail.amaranth.net>
Errors-To: owner-nanog-outgoing@merit.edu
On Mon, Nov 08, 2004 at 03:46:05PM -0500, Daniel Senie wrote:
> Reason #3: A separate set of blocks should be set aside for use ONLY in
> documentation.
inet6num: 2001:0DB8::/32
netname: IPV6-DOC-AP
descr: IPv6 prefix for documentation purpose
[...]
remarks: This address range is to be used for documentation
remarks: purpose only. For more information please see
remarks:
http://www.apnic.net/info/faq/ipv6-documentation-prefix-faq.html
> Reason #4: Initial configuration of equipment which lacks a console port. I
> know, you're going to suggest the use of autoconfiguration mechanisms or
> DHCP. That's sometimes hard, for example in the case of a broadband
> "router" (home gateway) box that's going to be the DHCP server, print
> servers, and other such equipment.
I don't see that this is "hard". The box will get a /48 from the ISP's
DHCPv6 server (or whatever is used for that) and re-use subnets for
that for inside routing. Like simply the first /64, and doing router
advertisements on the inside ethernet for this subnet to allow
autoconfig of the hosts of the home LAN.
Regards,
Daniel
--
CLUE-RIPE -- Jabber: dr@cluenet.de -- dr@IRCnet -- PGP: 0xA85C8AA0
