[183593] in North American Network Operators' Group
Re: IPv6 Subscriber Access Deployments
daemon@ATHENA.MIT.EDU (Owen DeLong)
Wed Sep 9 13:18:27 2015
X-Original-To: nanog@nanog.org
From: Owen DeLong <owen@delong.com>
In-Reply-To: <1441741576.143219.378115649.3634EE3A@webmail.messagingengine.com>
Date: Wed, 9 Sep 2015 10:15:21 -0700
To: Clinton Work <clinton@scripty.com>
Cc: nanog@nanog.org
Errors-To: nanog-bounces@nanog.org
Sure, but this is a useless savings that comes at the cost of awkward =
traceroute output
that will initially confuse your new employees and consistently confuse =
your customers.
Owen
> On Sep 8, 2015, at 12:46 , Clinton Work <clinton@scripty.com> wrote:
>=20
> If you use separate VLANs for each customer then the CPE router =
doesn't
> even require an external IPV6 address for DHCPv6-PD. IPV6 link-local
> addresses can be used between your BRAS and customer CPE router. Some
> CPEs can even allocate a WAN/mgmt IPV6 address out of the delegated
> subnet via DHCPv6-PD. =20
>=20
> On Tue, Sep 8, 2015, at 01:31 PM, Owen DeLong wrote:
>> Short answer to that is =E2=80=9CDHCPv6-PD=E2=80=9D
>>=20
>> Once the router has an external address communicating point to point =
with
>> the ISP router, it should then send an DHCPv6-PD request asking for a
>> prefix that it can manage. The ISPs DHCP server should then send back =
a
>> /48 (or if you want to be silly, a /56 or a /60, and if you want to =
be
>> insane, a /64).
