Hi Tony,

section 5.1 of the draft-ietf-lsr-flex-algo says:

Min Unidirectional Link Delay as defined in [I-D.ietf-isis-te-app].

We explicitly say "Min Unidirectional Link Delay", so this cannot be mixed with other delay values (max, average).


section 7.3. of ietf-isis-te-app says:

Type   Description                          Encoding
                                            Reference
---------------------------------------------------------
34      Min/Max Unidirectional Link Delay    RFC8570


So, IMHO what we have now is correct and sufficient, but I have no issue adding the text you proposed below.

BTW, before I posted 09 version of flex-algo draft, I asked if you were fine with just referencing ietf-isis-te-app in 5.1. I thought you were, as you did not indicate otherwise.

Anyway, I consider this as a pure editorial issue and hopefully not something that would cause you to object the WG LC of the flex-algo draft.

thanks,
Peter









On 18/08/2020 01:47, [email protected] wrote:


This begins a 2 week WG Last Call, ending after September 1st, 2020, for 
draft-ietf-lsr-flex-algo

  https://datatracker.ietf.org/doc/draft-ietf-lsr-flex-algo/



Hi,

I’d like to raise an objection.

Recently, I requested (and I thought that Peter agreed to) a clarification of 
the Min Unidirectional Link Delay.

As of version -08, the draft references RFC 7810 for the Metric-type in Section 
5.1.

That RFC defines both a “Unidirectional Link Delay” (section 4.1) and “Min/Max 
Unidirectional Link Delay” (section 4.2).

I requested that the reference be extended to specify the section.

Instead, as of -09, the reference has been changed to refer to 
ietf-isis-te-app.  This is somewhat helpful becuase it makes it clear that this 
should be found
in the Application Specific Link Attributes Sub-TLV, but it still does not 
resolve the ambiguity of which sub-sub-TLV should be used.

I would again request that this be clarified.  Proposed text:

        1: Min Unidirectional Link Delay as defined in [RFC 7810], section 4.2, 
encoded in the Application Specific Link Attributes Sub-TLV 
[I-D.ietf-isis-te-app].


Thank you.

Regards,
Tony




_______________________________________________
Lsr mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/lsr

Reply via email to