Re: [Lsr] Second Working Last Call for draft-ietf-lsr-flex-algo

[Gyan Mishra]

I support publication of Flex Algo specification.

Flex Algo use with SR-TE policy provides added steering capabilities to SR
framework and is very useful tool to have in the operators toolbox.

Flex Algo has been implemented by multiple vendors as well as had
successfully deployed by operators.

Gyan
On Mon, Jul 5, 2021 at 12:45 AM 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.
>
> 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) 
> *Sent:* Thursday, June 24, 2021 10:56 AM
> *To:* Acee Lindem (acee) ; lsr@ietf.org
> *Cc:* lsr-...@ietf.org; Christian Hopps ;
> draft-ietf-lsr-flex-algo@ietf.org
> *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  *On Behalf Of *Acee Lindem (acee)
> *Sent:* Wednesday, June 16, 2021 7:01 AM
> *To:* lsr@ietf.org
> *Cc:* lsr-...@ietf.org; Christian Hopps ;
> draft-ietf-lsr-flex-algo@ietf.org
> *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/
> 
>
>
>
> 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://datatracker.ietf.org/ipr/3910/
> 
>
>   https://datatracker.ietf.org/ipr/3248/
> 
>
>
>
> Thanks,
>
> Chris & Acee.
>
>
>
>
> ___
> Lsr mailing list
> Lsr@ietf.org
> https://www.ietf.org/mailman/listinfo/lsr
>
-- 



*Gyan Mishra*

*Network Solutions A**rchitect *

*Email gyan.s.mis...@verizon.com *



*M 301 502-1347*
___
Lsr mailing list
Lsr@ietf.org
https://www.ietf.org/mailman/listinfo/lsr

Re: [Lsr] Second Working Last Call for draft-ietf-lsr-flex-algo

[Shraddha Hegde]

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.
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) 
Sent: Thursday, June 24, 2021 10:56 AM
To: Acee Lindem (acee) ; lsr@ietf.org
Cc: lsr-...@ietf.org; Christian Hopps ; 
draft-ietf-lsr-flex-algo@ietf.org
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 mailto:lsr-boun...@ietf.org>> On Behalf Of Acee 
Lindem (acee)
Sent: Wednesday, June 16, 2021 7:01 AM
To: lsr@ietf.org
Cc: lsr-...@ietf.org; Christian Hopps 
mailto:cho...@chopps.org>>; 
draft-ietf-lsr-flex-algo@ietf.org
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/

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://datatracker.ietf.org/ipr/3910/
  
https://datatracker.ietf.org/ipr/3248/

Thanks,
Chris & Acee.


___
Lsr mailing list
Lsr@ietf.org
https://www.ietf.org/mailman/listinfo/lsr