Hi All As an co-author of this draft I support this draft.
Currently there is no answer for multicast in a segment routing domain, enabling traditional multicast protocols will create an overhead which is not acceptable. Clean/Lean network from control point of view is the key of future network deployments. This means simplifications of the control plane overlay and of course single IGP underlay. P2MP policy provides this. P2MP policy is a controller specific policy where the controller learns of the root and the leaves of the tree and calculates the Tree and downloads the appropriate replication segments on the path of the tree. To program the policy and its replication segments there are 2 technologies, PCEP and BGP. As we all know it comes down to the operator choice to implement one or the other or both in the network. In addition the strength of this draft is reusing the unicast BGP SR TE Policy infrastructure, objects and SUB-TLVs. This draft basically enhances BGP SR TE Policy to P2MP policy. >From NLRI point of view there are 2 NLRI one for P2MP policy and its candidate >paths, which is relevant to the root (head-end) and another for downloading >the replication segments which are the forwarding entities and sid-list. There >was no need to download the P2MP policy and the candidate paths on the transit >and the leaves hence why the separation creates a clean and optimised solution. Regards Hooman From: BESS <[email protected]> On Behalf Of Susan Hares Sent: Thursday, March 10, 2022 9:55 AM To: [email protected]; [email protected]; [email protected] Subject: [bess] 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
_______________________________________________ BESS mailing list [email protected] https://www.ietf.org/mailman/listinfo/bess
