Hi Peter,
On 7/5/21, 4:05 AM, "Peter Psenak" <[email protected]> wrote:
Hi Shraddha,
On 05/07/2021 06:44, Shraddha Hegde wrote:
> I support progressing this draft.
>
> I have a minor comment on the Flags sub-TLV.
>
> In section “ISIS Flexible Algorithm Definition Flags Sub-TLV”
>
> And “OSPF Flexible Algorithm Definition Flags Sub-TLV”
>
> We should add an explicit statement that
>
> “ If any undefined flag is set and that flag is not
>
> Understood by the node it MUST stop participating in the flex-algorithm”
>
> While this information can be derived from previous sections, adding an
> explicit
>
> Statement in the flags section will help implementors to honor that
> statement.
will add that statement in the next version.
We will request publication on this version.
Thanks,
Acee
thanks,
Peter
>
> If implementations miss this, it would be difficult to deploy features
> that need new flags
>
> In future.
>
> Rgds
>
> Shraddha
>
> Juniper Business Use Only
>
> *From:*Les Ginsberg (ginsberg) <[email protected]>
> *Sent:* Thursday, June 24, 2021 10:56 AM
> *To:* Acee Lindem (acee) <[email protected]>; [email protected]
> *Cc:* [email protected]; Christian Hopps <[email protected]>;
> [email protected]
> *Subject:* RE: Second Working Last Call for draft-ietf-lsr-flex-algo
>
> *[External Email. Be cautious of content]*
>
> I support progressing this document.
>
> Flex-algo has already been demonstrated to be useful with a number of
> implementations/deployments.
>
> Les
>
> *From:*Lsr <[email protected] <mailto:[email protected]>> *On
> Behalf Of *Acee Lindem (acee)
> *Sent:* Wednesday, June 16, 2021 7:01 AM
> *To:* [email protected] <mailto:[email protected]>
> *Cc:* [email protected] <mailto:[email protected]>; Christian Hopps
> <[email protected] <mailto:[email protected]>>;
> [email protected]
> <mailto:[email protected]>
> *Subject:* [Lsr] Second Working Last Call for draft-ietf-lsr-flex-algo
>
> After the first successful WG last call, the authors discovered that
> some re-work was needed for OSPF AS External route calculation –
> specifically with respect to the Flex Algorithm ASBR metrics and
> calculation. This was fixed and there were clarifications in the IANA
> section (see versions -14 and -15). The draft has been stable since
> April and we are now ready to WG last call the updated version.
>
> Without further ado, this begins a 2 week WG Last Call, ending on July
> 1st, 2021, for draft-ietf-lsr-flex-algo
>
> https://datatracker.ietf.org/doc/draft-ietf-lsr-flex-algo/
>
<https://urldefense.com/v3/__https:/datatracker.ietf.org/doc/draft-ietf-lsr-flex-algo/__;!!NEt6yMaO-gk!S24A0VDoKfWQMUhBAT1294ruoAud7W0REDqMrKLfBu7v843mcXzJ6Eu7x3QAu8ny$>
>
> All authors, please indicate by sending an email to the list, whether
> you aware of any other IPR beyond what is already posted:
>
> [From
>
https://datatracker.ietf.org/ipr/search/?submit=draft&id=draft-ietf-lsr-flex-algo
>
<https://urldefense.com/v3/__https:/datatracker.ietf.org/ipr/search/?submit=draft&id=draft-ietf-lsr-flex-algo__;!!NEt6yMaO-gk!S24A0VDoKfWQMUhBAT1294ruoAud7W0REDqMrKLfBu7v843mcXzJ6Eu7x8TVfDmS$>]
>
> https://datatracker.ietf.org/ipr/3910/
>
<https://urldefense.com/v3/__https:/datatracker.ietf.org/ipr/3910/__;!!NEt6yMaO-gk!S24A0VDoKfWQMUhBAT1294ruoAud7W0REDqMrKLfBu7v843mcXzJ6Eu7xwIee-xG$>
>
> https://datatracker.ietf.org/ipr/3248/
>
<https://urldefense.com/v3/__https:/datatracker.ietf.org/ipr/3248/__;!!NEt6yMaO-gk!S24A0VDoKfWQMUhBAT1294ruoAud7W0REDqMrKLfBu7v843mcXzJ6Eu7xyrFkBLf$>
>
> Thanks,
>
> Chris & Acee.
>
_______________________________________________
Lsr mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/lsr
