[195928] in North American Network Operators' Group
RE: DHCPv6-PD -> Lack of route injection in RFC
daemon@ATHENA.MIT.EDU (Nicholas Warren)
Sat Sep 23 03:17:49 2017
X-Original-To: nanog@nanog.org
From: Nicholas Warren <nwarren@barryelectric.com>
To: Baldur Norddahl <baldur.norddahl@gmail.com>, "nanog@nanog.org"
<nanog@nanog.org>
Date: Fri, 22 Sep 2017 17:08:02 +0000
In-Reply-To: <CAPkb-7C3Dt2iv4zeCYh+78YziGot8RE+17tQctkb9LGbGqFvsA@mail.gmail.com>
Errors-To: nanog-bounces@nanog.org
Which method would you recommend as an alternative?
-----Original Message-----
From: NANOG [mailto:nanog-bounces@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 VRR=
P and the backup router will not learn anything from a relay on the primary=
.
Den 22. sep. 2017 14.02 skrev "Steve Teusch" <steve.teusch@rtr.guru>:
I am running into venders that do not support injection of a delegated rout=
e 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 important or return =
packets won't go to the client unless the route is manually added as a rout=
ing protocol is not an option. There should be a MUST activity for this so=
mewhere.
Anyone know what gives?
