Subject: [Idr] Re： Adoption call for draft-wang-idr-bgp-ifit-capabilities-04 (3/10 to 3/24)

From: Yisong Liu<[email-masked]>
Date: 18 Mar 2022 10:15:23 +0800

Hi All,

I support the adoption of this draft. I think it is useful for the deployment of IFIT.

Best Regards

Yisong

发件人: Susan Hares

时间: 2022/03/10(星期四)22:38

收件人: idr;

主题: [Idr] Adoption call for draft-wang-idr-bgp-ifit-capabilities-04 (3/10 to 3/24)

Greeting: 

This begins a 2 week WG Adoption call (3/10/2022 to 3/24/2022) 

for draft-wang-idr-bgp-ifit-capabilities-04

https://datatracker.ietf.org/doc/draft-wang-idr-bgp-ifit-capabilities/

In your comments please consider if: 

1) Do the additions to BGP (2 Communities and 

TLV for next-hop-capability attribute) 

help the distribute information regarding the  IFIT options 

from tail (egress) nodes to head nodes (ingress)?  

Are there any cases where these BGP 

Communities should be removed or ignored?  

2) Are the mechanisms (2 Communities and 

attribute TLV) correctly specified? 

3) How do these additions interaction with the 

  With SR technology for IFIT described in 

   draft-ietf-idr-sr-policy-ifit, and its 

   use of RFC9012 (tunnel attributes)? 

(Authors an example on how these

technologies work together or 

 operate separately would be helpful). 

4)  Will this addition help network operators 

deploying IFIT technology? 

Cheerily, Sue