[186097] in North American Network Operators' Group
Re: DHCPv6 PD & Routing Questions
daemon@ATHENA.MIT.EDU (Mark Andrews)
Thu Nov 26 01:04:25 2015
X-Original-To: nanog@nanog.org
To: =?utf-8?B?SsOBS8OTIEFuZHLDoXM=?= <jako.andras@eik.bme.hu>
From: Mark Andrews <marka@isc.org>
In-reply-to: Your message of "Thu, 26 Nov 2015 06:34:49 +0100."
<20151126053449.GA22347@eik.bme.hu>
Date: Thu, 26 Nov 2015 17:04:12 +1100
Cc: nanog@nanog.org
Errors-To: nanog-bounces@nanog.org
In message <20151126053449.GA22347@eik.bme.hu>, =?utf-8?B?SsOBS8OTIEFuZHLDoXM=?= writes:
> > Well the requesting router could announce the route. ISC's client
> > has hooks that allow this to be done. That is, after all, how
> > routing is designed to work. The DHCP server usually is sitting
> > in a data center on the other side of the country with zero ability
> > to inject approptiate routes.
> >
> > The DHCP relay could also have injected routes but that is a second
> > class solution.
>
> A CPE announcing the route is fine as long as the ISP controls the CPE.
>
> If the CPE is controled by the customer, then the ISP's problems are
> similar. They need to find a way to filter the CPE's announcement so
> that it can announce only the prefixes delegated to it.
>
> András
Which is why I mentioned the DHCP relay.
Somewhere back towards the beginnings of this thread there was a
reference to a blog post that complained that they couldn't workout
how to send a git pull request to us. I've forwarded that to our
dhcp team. For future reference dhcp-bugs@isc.org or dhcp-suggest@isc.org
would have been fine places to send the request. So to the bug
reporting form on isc.org which lets you select if it is bug,
suggestion or a security issue. There also the general contact
form which would get to the dhcp team after being forwarded a couple
of times.
Mark
--
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742 INTERNET: marka@isc.org
