Skip to main content

Advertising p2mp policies in BGP
draft-hb-idr-sr-p2mp-policy-00

The information below is for an old version of the document.
Document Type
This is an older version of an Internet-Draft whose latest revision state is "Replaced".
Expired & archived
Authors Hooman Bidgoli , Daniel Voyer , Andrew Stone , Rishabh Parekh , Serge Krier , Arvind Venkateswaran
Last updated 2020-05-02 (Latest revision 2019-10-30)
Replaced by draft-ietf-idr-sr-p2mp-policy
RFC stream (None)
Formats
Stream Stream state (No stream defined)
Consensus boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date (None)
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:

Abstract

SR P2MP policies are set of policies that enable architecture for P2MP service delivery. A P2MP policy consists of candidate paths that connects the Root of the Tree to a set of Leaves. The P2MP policy is composed of replication segments. A replication segment is a forwarding instruction for a candidate path which is downloaded to the Root, transit nodes and the leaves. This document specifies a new BGP SAFI with a new NLRI in order to advertise P2MP policy from a controller to a set of nodes. This document introduces two new route types within this NLRI, one for P2MP policy and its candidate paths that need to be programmed on the Root node and another for the replication segment and forwarding instructions that needs to be programmed on the Root, and optionally on Transit and Leaf nodes. It should be noted that this document does not specify how the Root and the Leaves are discovered on the controller, it only describes how the P2MP Policy and Replication Segments are programmed from the controller to the nodes.

Authors

Hooman Bidgoli
Daniel Voyer
Andrew Stone
Rishabh Parekh
Serge Krier
Arvind Venkateswaran

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)