Flex-Algorithm TLV in PIM Join Attributes

Introduction Protocol Independent Multicast (PIM) get the upstream neighbor and incoming interface to multicast source or Rendezvous Point (RP) from the unicast routing protocol. As described in section 3 in , PIM relies on an underlying topology-gathering protocol to populate the MRIB (Multicast Routing Information Base). Usually the MRIB is the best paths over the network based on the IGP metric. In some case, PIM should choose a special path such as low latency path or constraint-based path. specifies a set of extensions to IS-IS, OSPFv2, and OSPFv3 to be used to compute the best paths along the constrained topology. In order to allow PIM build multicast distribution trees following Flex-Algorithm topology, a PIM extension is needed. This document defines a new join attributes to restrict the path of pim join.

Requirements Language The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in .

Flex-Algorithm Attribute defines a pim Join Attributes are encoded as TLVs into the Encoded-Source Address field of a PIM Join message. This document specifies the Flex-Algorithm Attribute that allows the receiver to select the Flex-Algorithm path.

Flex-Algorithm Attribute Format

F bit: The Transitive bit. Specifies whether the attribute is transitive or non-transitive. This bit RECOMMENDED set to 1 and the attribute will be transitived.
E bit: End-of-Attributes bit. Specifies whether this attribute is the last. Set to zero if there are more attributes. Set to 1 if this is the last attribute.
Type: TBD (To be assigned by IANA).
Length: 1-octet.
Flex-Algo: A 1-octet field Flex-Algorithm (see Section 4 of ) to special the topology.

Specification of the Flex-Algorithm Attribute The PIM router on the receiving side specifies the Flex-Algorithm of the unicast route to the multicast source or RP according to the local policy. It lookup unicast route in Flex-Algorithm topology, and fills the specified Flex-Algorithm into the Flex-Algorithm attribute when sending the join message to upstream neighbor. After receiving join message with Flex-Algorithm attribute, the upstream PIM router lookup unicast routes in the Flex-Algorithm topology and selects the incoming interface and upstream neighbor. And the continual join messages keep carrying the Flex-Algorithm Attribute. When unicast routing is unreachable in the specific Flex-Algorithm topology, there are two processing modes: Try-to-Forward and Strictly-Topology. In Try-to-Forward mode, pim router continues to search the unicast route without topology constrained, and the sent join message will no longer carry Flex-Algorithm Attribute; In Strictly-Topology mode, it is handled according to route unreachable. If the Flex-Algorithm attribute of the same source address(or RP address) and group address sent by multiple downstream PIM routers are different, the join message from the neighbor, which has the larger address, is selected. Flex-Algorithm attribute and RPF vector attribute() SHOULD NOT appear in the Encoded-Source Address when PIM build a join message, . And if PIM router receives a join message with both Flex-Algorithm attribute and RPF vector attribute in a Encoded-Source Address, the first attribute is RECOMMENDED to be used. There should be no more than one Flex-Algorithm attribute in a Encoded-Source Address when PIM build a join message. If the PIM router receives a join message with multiple Flex-Algorithm attributes in a Encoded-Source Address, the first one is RECOMMENDED be used.