Re: [Last-Call] [Lsr] Genart last call review of draft-ietf-ospf-mpls-elc-13

["Les Ginsberg \(ginsberg\)" <ginsberg=40cisco.com@xxxxxxxxxxxxxx>]

Elwyn’s comment was:

 

<snip>

I was trying to understand

why a router that satisfies the previous condition so that it is

legitimate for it to announce ELC with any IP address prefix might wish

to only announce it with some prefixes and not others. 

<end snip>

 

The answer to that is clearly stated in the draft (emphasis added):

 

“If the router supports ELs on all of its interfaces, it SHOULD

   advertise the ELC with every local host prefix it advertises in OSPF.”

 

 

What is needed is to know whether traffic routed via a particular node can depend upon that node supporting EL.  That info is communicated by advertising ELC for the local host prefixes only.

No need to do so for other prefixes.

 

HTH

 

   Les

 

 

From: Lsr <lsr-bounces@xxxxxxxx> On Behalf Of Alvaro Retana
Sent: Thursday, May 14, 2020 12:46 PM
To: Acee Lindem (acee) <acee@xxxxxxxxx>; Peter Psenak (ppsenak) <ppsenak@xxxxxxxxx>; Elwyn Davies <elwynd@xxxxxxxxxxxxxx>; gen-art@xxxxxxxx
Cc: lsr@xxxxxxxx; last-call@xxxxxxxx; draft-ietf-ospf-mpls-elc.all@xxxxxxxx
Subject: Re: [Lsr] Genart last call review of draft-ietf-ospf-mpls-elc-13

 

Hi!

 

Yes, we cannot specify something that routers unaware of this specification should or shouldn’t do.

 

I believe that Elwyn’s point is this: *if a router supports this specification* then when would it not advertise the ELC?  IOW, the specification only obviously applies to implementations that support it — in that case I would think that if a router supports ELs on all of its interfaces then it would always advertise the ELC, right?

 

 

Thanks!

 

Alvaro.

 

On May 11, 2020 at 3:18:34 PM, Acee Lindem (acee) (acee@xxxxxxxxx) wrote:

Note that the optionality of ERLD-MSD advertisements appears on 
reflection to be a more serious issue than just an editorial nit. 

So what would you suggest? There are existing implementations that support multipath forwarding entropy using MPLS entropy labels but do not signal that capability in OSPF. We can't have a document that retroactively mandates that they signal it. This wouldn't be backward compatible. How can you possibly see this as a serious issue? 

-- 
last-call mailing list
last-call@xxxxxxxx
https://www.ietf.org/mailman/listinfo/last-call