P2Mp Responder Identifier Tlv Operations; Table 53: Sub-Tlvs Supported For The P2Mp Responder Identifier Tlv - Juniper JUNOSE SOFTWARE FOR E SERIES 11.3.X - BGP AND MPLS CONFIGURATION GUIDE 2010-10-12 Configuration Manual

P2MP Responder Identifier TLV Operations

Copyright © 2010, Juniper Networks, Inc.
ingress (and nearby routers) node from being flooded with a number of responses, or
from discarding responses if any rate limits are applied on the incoming traffic.
In JunosE Software, the delay is set to a maximum of 30 seconds. The ingress node
informs the egresses of this time interval limitation by supplying a value in the Echo Jitter
TLV in the echo request message. If this TLV is present in the echo request packet, the
responding egress node delays sending a response for a random amount of time between
zero milliseconds and 30 seconds that is predefined for this TLV. If the TLV is not
contained in the echo request packet, the responding egress node does not create any
additional delay in responding to the echo request. The Echo Jitter TLV is valid only in an
echo request message. If this TLV is included in an echo response message, it is ignored.
The Echo Jitter TLV is assigned the TLV type value of 12.
You can select the egress node in a point-to-multipoint LSP for which you want to trace
the path from an ingress node and detect network failures by including a P2MP Responder
Identifier TLV in the echo request packet sent to the egress node. The initiator can
determine whether only the node identified in the TLV must respond or any node on the
path to the selected egress node in the TLV needs to respond. If you do not include the
P2MP Responder Identifier TLV in an echo request packet, all egress nodes in the path
to the ingress node respond to echo request packets.
If the node is an egress of the P2MP LSP, the node checks whether it has received a P2MP
Responder Identifier TLV in an echo request. If a P2MP Responder Identifier TLV is
contained in the received echo request, the node uses the sub-TLVs contained in this
TLV to determine whether it must respond to the request. If the P2MP Responder Identifier
TLV is not present (or does not contain any sub-TLVs), the egress node responds to the
echo request depending on the setting of the Response Type field in the echo message.
The P2MP Responder Identifier TLV is assigned a type number of 11. The P2MP Responder
Identifier TLV is valid only in an echo request message.
If this TLV is included in an echo response message, it is ignored.
If no sub-TLVs are present, this TLV is processed as though it were not included.
If more than one sub-TLV is present in this TLV, they are processed based on their
subtype numbers and subsequent sub-TLVs are ignored.
Four sub-TLVs are defined for inclusion in the P2MP Responder Identifier TLV in the echo
request message. Table 53 on page 249 lists the sub-TLVs supported for the P2MP
Responder Identifier TLV.

Table 53: Sub-TLVs Supported for the P2MP Responder Identifier TLV

Subtype Number Value
1 IPv4 Egress Address P2MP
Responder Identifier
Chapter 3: MPLS Overview
Comments
The IPv4 address in this sub-TLV
is the IPv4 address of the egress
node and does not specify the IPv4
address of a branch or
intermediate node.
249