Multi-Protocol Label Switching (MPLS) Label Switched Paths (LSPs) Parameters - per [RFC4379] (last updated 2008-06-23) Registries included below: - Message Types - Reply Modes - Return Codes - TLVs Message Types - per [RFC4379] Registration Procedures: 0-191 - Standards Action 192-251 - Specification Required (Experimental RFC needed) 252-255 - Vendor Private Use and MUST NOT be allocated Value Meaning Reference ----- ---------------------------- --------- 1 MPLS Echo Request [RFC4379] 2 MPLS Echo Reply [RFC4379] Reply Modes - per [RFC4379] Registration Procedures: 0-191 - Standards Action 192-251 - Specification Required (Experimental RFC needed) 252-255 - Vendor Private Use and MUST NOT be allocated Value Meaning Reference ----- ---------------------------------------------------- --------- 1 Do not reply [RFC4379] 2 Reply via an IPv4/IPv6 UDP packet [RFC4379] 3 Reply via an IPv4/IPv6 UDP packet with Router Alert [RFC4379] 4 Reply via application level control channel [RFC4379] Return Codes - per [RFC4379] Registration Procedures: 0-191 - Standards Action 192-251 - Specification Required (Experimental RFC needed) 252-255 - Vendor Private Use and MUST NOT be allocated Value Meaning Reference ----- ---------------------------------------------------- --------- 0 No return code [RFC4379] 1 Malformed echo request received [RFC4379] 2 One or more of the TLVs was not understood [RFC4379] 3 Replying router is an egress for the FEC at stack [RFC4379] depth 4 Replying router has no mapping for the FEC at stack [RFC4379] depth 5 Downstream Mapping Mismatch (See [1]) [RFC4379] 6 Upstream Interface Index Unknown (See [1]) [RFC4379] 7 Reserved [RFC4379] 8 Label switched at stack-depth [RFC4379] 9 Label switched but no MPLS forwarding at stack-depth [RFC4379] 10 Mapping for this FEC is not the given label at stack [RFC4379] depth 11 No label entry at stack-depth [RFC4379] 12 Protocol not associated with interface at FEC stack [RFC4379] depth 13 Premature termination of ping due to label stack [RFC4379] shrinking to a single label Notes ----- [1] The Return Subcode contains the point in the label stack where pro- cessing was terminated. If the RSC is 0, no labels were processed. Otherwise the packet would have been label switched at depth RSC. TLVs and sub-TLVs - per [RFC4379] Registration Procedures: 0-16383 and 32768-49161 - Standards Action 16384-31743 and 49162-64511 - Specification Required (Experimental RFC needed) 31744-32767 and 64512-65535 - Vendor Private Use, and MUST NOT be allocated Type Sub-Type Value Field Reference ----- -------- --------------------------------- --------- 1 Target FEC Stack [RFC4379] 1 LDP IPv4 prefix [RFC4379] 2 LDP IPv6 prefix [RFC4379] 3 RSVP IPv4 LSP [RFC4379] 4 RSVP IPv6 LSP [RFC4379] 5 Not Assigned [RFC4379] 6 VPN IPv4 prefix [RFC4379] 7 VPN IPv6 prefix [RFC4379] 8 L2 VPN endpoint [RFC4379] 9 "FEC 128" Pseudowire (Deprecated) [RFC4379] 10 "FEC 128" Pseudowire [RFC4379] 11 "FEC 129" Pseudowire [RFC4379] 12 BGP labeled IPv4 prefix [RFC4379] 13 BGP labeled IPv6 prefix [RFC4379] 14 Generic IPv4 prefix [RFC4379] 15 Generic IPv6 prefix [RFC4379] 16 Nil FEC [RFC4379] 2 Downstream Mapping [RFC4379] 3 Pad [RFC4379] 4 Not Assigned [RFC4379] 5 Vendor Enterprise Number [RFC4379] 6 Not Assigned [RFC4379] 7 Interface and Label Stack [RFC4379] 8 Not Assigned [RFC4379] 9 Errored TLVs [RFC4379] Any value The TLV not understood [RFC4379] 10 Reply TOS Byte [RFC4379] 11-14 Unassigned 15 BFD Discriminator [RFC-ietf-bfd-mpls-07.txt] References ---------- [RFC4379] K. Kompella and G. Swallow, "Detecting MPLS Data Plane Failures", RFC 4379, February 2006. [RFC-ietf-bfd-mpls-07.txt] R. Aggarwal, K. Kompella, T. Nadeau, G. Swallow, "BFD For MPLS LSPs". RFC XXXX, Month Year. (Registry created 2006-01-12) []