On Tue, 26 Sep 2017 17:02:51 -0400, Lee Howard said:
> Right. How many residential market gateways support any routing protocol
> at all?
Depends on how flabby a definition you use. Does "ask for a default route"
count? :)
pgpWsKLXrG1sf.pgp
Description: PGP signature
On Tue, 26 Sep 2017, Blake Dunlap wrote:
Isn't this the topic area that the home networking working group was
supposed to resolve?
HOMENET was never looking into running a routing protocol between the ISP
and the HGW. It was all about running a routing protocol WITHIN the home,
not between
Isn't this the topic area that the home networking working group was
supposed to resolve?
On Tue, Sep 26, 2017 at 2:02 PM, Lee Howard wrote:
>
>
> On 9/23/17, 1:51 AM, "nanog-boun...@nanog.org on behalf of
> valdis.kletni...@vt.edu"
On 9/23/17, 1:51 AM, "nanog-boun...@nanog.org on behalf of
valdis.kletni...@vt.edu" wrote:
>On Sat, 23 Sep 2017 08:47:32 +1000, Mark Andrews said:
>> You know CPE devices are routers. They can tell you what routes
>> DHCP has given
Dear Steve,
We used to have this in the IETF:
https://tools.ietf.org/html/draft-ietf-dhc-dhcpv6-prefix-pool-opt-03 and
https://tools.ietf.org/html/draft-petrescu-relay-route-pd-problem-00.
We abandoned that effort because there wasn't sufficient support for it at that
time.
Cheers,
Med
>
I don't know about brocade, but here's what I see in Junos and IOS...
dhcpv6 relay binding seen...
{master:0}
agould@eng-lab-5048-2> show dhcpv6 relay binding routing-instance three
Prefix Session Id Expires StateInterfaceClient
DUID
2699:2699:0:7::100/128 199
On Sat, 23 Sep 2017 08:47:32 +1000, Mark Andrews said:
> You know CPE devices are routers. They can tell you what routes
> DHCP has given them. That annoucement could be cryptographically
> authenticated.
This is, of course, a lot easier if the CPE already has onboard the needed
software to do
You know CPE devices are routers. They can tell you what routes
DHCP has given them. That annoucement could be cryptographically
authenticated.
Send a CPE generated public key with the PD request. Generate a
CERT for the prefix delegation using those two pieces of information
and return it
I know of several methods all flawed in some ways. There seems to be no
progress in this obvious lack of a solid easy way to inject routes to match
DHCP-PD.
We use ExaBGP to inject routes via BGP that matches the configuration that
our DHCP server has. But this is non standard and clumsy to
to handle that.
Although V6 still needs a lot more attention to get to that point.
-Original Message-
From: NANOG [mailto:nanog-boun...@nanog.org] On Behalf Of Baldur Norddahl
Sent: Saturday, September 23, 2017 1:52 AM
To: nanog@nanog.org
Subject: Re: DHCPv6-PD -> Lack of route inject
Which method would you recommend as an alternative?
-Original Message-
From: NANOG [mailto:nanog-boun...@nanog.org] On Behalf Of Baldur Norddahl
Sent: Friday, September 22, 2017 11:52 AM
This method is lacking because you might have several routers eg. using VRRP
and the backup router
This method is lacking because you might have several routers eg. using
VRRP and the backup router will not learn anything from a relay on the
primary.
Den 22. sep. 2017 14.02 skrev "Steve Teusch" :
I am running into venders that do not support injection of a delegated
On 9/22/17, 3:12 AM, "NANOG on behalf of Steve Teusch"
wrote:
>I am running into venders that do not support injection of a delegated
>route when operating as a DHCPv6 relay (or server for that matter).
>Brocade
Steve Teusch wrote:
> I am running into venders that do not support injection of a
> delegated route when operating as a DHCPv6 relay (or server for that
> matter). Brocade supports this, but I am not finding this as part of
> any of the RFC's. This is to deliver home ISP service, so it is very
14 matches
Mail list logo