Hi, > -----Original Message----- > From: ipv6-ops-bounces+fred.l.templin=boeing....@lists.cluenet.de > [mailto:ipv6-ops- > bounces+fred.l.templin=boeing....@lists.cluenet.de] On Behalf Of Erik Kline > Sent: Wednesday, June 08, 2016 11:37 AM > To: Ole Troan <o...@cisco.com> > Cc: IPv6 Ops list <ipv6-ops@lists.cluenet.de>; Mikael Abrahamsson > <swm...@swm.pp.se> > Subject: Re: DHCPv6 relay with PD > > On 9 June 2016 at 03:16, Ole Troan <o...@cisco.com> wrote: > > Mikael, > > > >>> We also tried (and failed) to come up with a secure mechanism for the > >>> requesting router to advertise it's delegated prefix to first- > hop routers. > >>> > >>> Less astonished? ;-) > >> > >> Well, I guess I shouldn't be astonished. I've even seen vendors implement > >> the DHCPv6-PD server on the router itself, and fail to > install route according to the delegated prefix. > >> > >> So basically, regarding how to actually implement PD in a network (from an > >> IETF point of view), everybody just gave up, declared > the problem unsolvable, and went back to sleep? > > > > It shouldn't be the IETF's job to tell people how to run their networks. > > The IETF provides the building blocks. > > But this sounds like what's missing is operational guidance on what > collections of blocks have been known to work.
AERO provides operational guidance on collections of blocks that work: https://datatracker.ietf.org/doc/draft-templin-aerolink/ Thanks - Fred
