Unfortunately not too much help, but previous discussion on this turned up
fairly empty:
https://mailman.nanog.org/pipermail/nanog/2019-May/101016.html
https://mailman.nanog.org/pipermail/nanog/2017-September/092416.html

-- 
Hugo Slabbert       | email, xmpp/jabber: h...@slabnet.com
pgp key: B178313E   | also on Signal


On Wed, Jan 15, 2020 at 6:02 PM Brandon Price <pri...@sherwoodoregon.gov>
wrote:

> Hey Nanog,
>
>
>
> I am in the process of building out a FTTH proof of concept, and I would
> really like to offer each of my customers a /48 of IPv6.
>
> I’ve been able to announce my /32 to my upstreams, dual-stack all of my
> internal infrastructure no-problem, build v6 recursive name servers, etc.
>
> This was fairly straight-forward.
>
>
>
> Where I am struggling is the Prefix Delegation part. How are most folks
> getting the PD subnets into their IGPs? In my environment I don’t run the
> DHCP server process on the router that is directly connected to the
> clients. I have seen documentation that cisco and juniper DHCPv6 processes
> are smart enough to insert that prefix into the routing table when they
> hand it out, but how is this handled in an environment with a central DHCP
> server? I do not currently run any PPPOE in my environment and I don’t use
> RADIUS for the subscriber management. I would really just like to stick to
> DHCP ideally.
>
>
>
> If anyone has any pointers, I would appreciate it.
>
>
>
> Brandon Price
>
> Senior Network Engineer
>
> City of Sherwood, Sherwood Broadband
>
> Desk: 503.625.4258
>
> Cell: 971.979.2182
>
>
>
> This email may contain confidential information or privileged material and
> is intended for use solely by the above referenced recipient. Any review,
> copying, printing, disclosure, distribution, or other use by any other
> person or entity is strictly prohibited and may be illegal. If you are not
> the named recipient, or believe you have received this email in error,
> please immediately notify the City of Sherwood at (503) 625-5522 and delete
> the copy you received.
>

Reply via email to