Re: [Idr] draft-hb-idr-sr-p2mp-policy (3/10 to 3/24/2022) - Adoption call

[Susan Hares <[e-mail]>]

Swadesh:

 

Thank you your clear responses to my questions. 

 

Sue 

 

From: Swadesh Agrawal (swaagraw) [mailto:[e-mail]] 
Sent: Monday, March 21, 2022 6:03 PM
To: Susan Hares; [e-mail]
Subject: Re: [Idr] draft-hb-idr-sr-p2mp-policy (3/10 to 3/24/2022) - Adoption call

 

Hi Sue,

 

I support adoption of the draft.  Below is the response for specific consideration asked for each point:

 

1.      On lines similar to SR policy advertisement in BGP, draft extends BGP procedures to download SR P2MP policy and reuses the concept of a candidate path. It supports P2MP policy route, replication segment route and OIFs route of replication segment to create multicast distribution tree.
2.      Yes its defined correctly with different route types advertising tree information. Below are the important aspects
a.      Procedures avoid downloading all OIFs in single BGP route, hence avoiding complex TEA attribute.

b.	Individual OIF can be added, modified and withdrawn. No complete tree download each time.

c.       BGP packing efficient allowing distinct trees replication segments and OIFs packed in single update.
3.      Route types provide 
a.      P2MP tree information to head end
b.      Replication segment information to replication node
c.       OIF information
4.      Any deployment which uses BGP advertisement for P2P SR policy should have similar procedures to download P2MP trees from controller. SO yes, such procedures are required.
5.      No, due to reasons stated in point 4.
 
Regards
Swadesh

 

 

From: Idr <[e-mail]> on behalf of Susan Hares <[e-mail]>
Date: Thursday, March 10, 2022 at 7:29 AM
To: "[e-mail]" <[e-mail]>
Subject: Re: [Idr] draft-hb-idr-sr-p2mp-policy (3/10 to 3/24/2022) - Adoption call

 

IDR WG: 

 

If you just wish to respond to the IDR list, 

you may respond to this email on the adoption call. 

 

Cheers, Sue 

 

From: Idr [mailto:[e-mail]] On Behalf Of Susan Hares
Sent: Thursday, March 10, 2022 9:55 AM
To: [e-mail]; [e-mail]; [e-mail]
Subject: [Idr] draft-hb-idr-sr-p2mp-policy (3/10 to 3/24/2022)

 

This begins a 2 week WG adoption call for: 

draft-hb-idr-sr-p2mp-policy from (3/10 to 3/24/2022) 

 

You can obtain the draft at: 

https://datatracker.ietf.org/doc/draft-hb-idr-sr-p2mp-policy/

 

In your comments for this call please consider: 

 

1)  Does this technology support the SR P2MP features 

that distributes candidate paths which connect 

a multicast distribution tree (tree to leaves). 

 

2) Is the technology correctly specified for the 

NLRI (AFI/SAFI) and the tunnel encapsulation attribute 

additions (sections 2 and 3)? 

 

3) Does the P2MP policy operation (section 4) 

provide enough information for those implementing this 

technology and those deploying the technology? 

 

4) Do you think this multicast technology is a good

Place to start for P2MP policy advertisement via BGP? 

 

5) Do you think this SR P2MP policies should not be advertised 

via BGP? 

 

Cheers, Susan Hares