OC - relay agent queries w.r.t gi-address

Summary:

for v4 relay - leaf-list helper-address (this is basically the dhcp server address) but for a relay to function on a L3 interface, we also need the gi-address (https://tools.ietf.org/html/rfc3046)

But, we do not see any provision to configure a gi-address to be configured using OC. does this mean, we assume we fallback to the interface IPV4 address as giaddr

Email Exchange

---------- Forwarded message ---------- From: Rob Shakir robshakir@gmail.com Date: Fri, Jun 1, 2018 at 5:22 PM Subject: Re: OC - relay agent queries To: Wakif Isfaque wakifisfaque@gmail.com Cc: Anees Shaikh aashaikh@google.com, Rob Shakir robjs@google.com, OpenConfig netopenconfig@googlegroups.com

Anees' advice was that you'll need to open a new issue relating to this. If you do this, then we can update it when the issue is resolved.

Thanks, r.

On Fri, 1 Jun 2018 at 00:54 Wakif Isfaque wakifisfaque@gmail.com wrote: Thanks. Can we even track internal issues with the link you sent? I could not find anything w.r.t relay-agent in the link - https://github.com/openconfig/public/issues?page=1&q=is%3Aissue+is%3Aopen

If there is no way we can know about this. Would appreciate if you guys could post a message when a decesion is taken w.r.t giaddr for relay-agent.

Thanks,

Wakif

On Thu, May 31, 2018 at 5:11 PM, 'Anees Shaikh' via OpenConfig netopenconfig@googlegroups.com wrote: hi Wakif, you can open an issue on the public Github repo (github.com/openconfig/public) to track.

thanks. -- Anees

On Thu, May 31, 2018 at 4:09 AM Wakif Isfaque wakifisfaque@gmail.com wrote: Thanks.

Is there anyway we can track the progress w.r.t this one please?

Regards,

Wakif

On Tue, May 29, 2018 at 7:45 PM, Rob Shakir robjs@google.com wrote: Hi Wakif,

1) The relay agent model is alive and kicking -- the definitive source of the published models is the public repository.

2) We can add the giaddr to the model. This was not something that was in the initial set of configurations for operators in the group. We should also clarify that the giaddr should be set to the IPv4 address of the interface. We'll discuss how this should be treated in the case of >1 IPv4 address being configured and clarify the model. I have opened an internal issue for this.

Thanks, r.

On Tue, May 29, 2018 at 6:58 AM Wakif Isfaque wakifisfaque@gmail.com wrote: Hello There,

I had 2 queries. And would appreciate any inputs on the same.

1) A couple of weeks back, I could see the relay-agent model also listed in - http://openconfig.net/projects/models/ But, now i notice the same is not visible anymore. Also, the relay-agent yangs do exists (https://github.com/openconfig/public/tree/master/release/models/relay-agent). But for some reason its not listed. Does this mean, the relay-agent model would no longer be supported?

2) Incase the relay agent model is supported, the yang lists

for v4 relay - leaf-list helper-address (this is basically the dhcp server address) but for a relay to function on a L3 interface, we also need the gi-address (https://tools.ietf.org/html/rfc3046)

But, we do not see any provision to configure a gi-address to be configured using OC. does this mean, we assume we fallback to the interface IPV4 address as giaddr. If yes, is there is a decision algo on which IP to pick (primary/secondany? etc.). If not is the vendor open to choose?

Do let me know if any info is needed from my end.

Thanks,

Wakif

openconfig / public

OC - relay agent queries w.r.t gi-address #176

Email Exchange