Supported MPLS Standards

The Junos OS substantially supports the following RFCs and Internet drafts, which define standards for MPLS and traffic engineering.

• RFC 2858, Multiprotocol Extensions for BGP-4
• RFC 3031, Multiprotocol Label Switching Architecture
• RFC 3032, MPLS Label Stack Encoding
• RFC 3140, Per Hop Behavior Identification Codes
• RFC 3270, Multi-Protocol [sic] Label Switching (MPLS) Support of Differentiated Services

  Only E-LSPs are supported.

• RFC 3443, Time To Live (TTL) Processing in Multi-Protocol [sic] Label Switching (MPLS) Networks
• RFC 3478, Graceful Restart Mechanism for Label Distribution Protocol
• RFC 4090, Fast Reroute Extensions to RSVP-TE for LSP Tunnels

  Node protection in facility backup is not supported.

• RFC 4124, Protocol Extensions for Support of Diffserv-aware MPLS Traffic Engineering
• RFC 4364, BGP/MPLS IP Virtual Private Networks (VPNs)
• RFC 4379, Detecting Multi-Protocol [sic] Label Switched (MPLS) Data Plane Failures

  The traceroute functionality is supported only on transit routers.

• RFC 4950, ICMP Extensions for Multiprotocol Label Switching
• Internet draft draft-ietf-bfd-mpls-02.txt, BFD for MPLS LSPs
• Internet draft draft-ietf-mpls-rsvp-te-p2mp-01.txt, Extensions to RSVP-TE for Point to Multipoint TE LSPs (expires June 2005)
• Internet draft draft-ietf-mpls-soft-preemption-02.txt, MPLS Traffic Engineering Soft preemption

The following RFCs and Internet drafts do not define standards, but provide information about MPLS, traffic engineering, and related technologies. The IETF classifies them variously as “Experimental,” “Historic,” or “Informational.”

• RFC 2547, BGP/MPLS VPNs
• RFC 2702, Requirements for Traffic Engineering Over MPLS
• RFC 3063, MPLS Loop Prevention Mechanism
• RFC 3208, PGM Reliable Transport Protocol Specification

  Only the network element is supported.

• RFC 3469, Framework for Multi-Protocol [sic] Label Switching (MPLS)-based Recovery
• RFC 3564, Requirements for Support of Differentiated Services-aware MPLS Traffic Engineering
• RFC 4125, Maximum Allocation Bandwidth Constraints Model for Diffserv-aware MPLS Traffic Engineering
• RFC 4127, Russian Dolls Bandwidth Constraints Model for Diffserv-aware MPLS Traffic Engineering
• Internet draft draft-martini-l2circuit-encap-mpls-07.txt, Encapsulation Methods for Transport of Layer 2 Frames Over IP and MPLS Networks

  The Junos OS differs from the Internet draft in the following ways:

  • A packet with a sequence number of 0 is treated as out of sequence.
  • Any packet which does not have the next incremental sequence number is considered out of sequence.
  • When out-of-sequence packets arrive, the expected sequence number for the neighbor is set to the sequence number in the Layer 2 circuit control word.
• Internet draft draft-martini-l2circuit-trans-mpls-14.txt, Transport of Layer 2 Frames Over MPLS
• Internet draft draft-raggarwa-mpls-p2mp-te-02.txt, Establishing Point to Multipoint MPLS TE LSPs

  The features discussed in the indicated sections of the draft are not supported:

  • Nonadjacent signaling for branch LSPs (section 7.1)
  • Make-before-break and fast reroute (section 9)
  • LSP hierarchy using point-to-point LSPs (section 10)

Related Topics

• Supported GMPLS Standards
• Supported LDP Standards
• Supported RSVP Standards
• Accessing Standards Documents on the Internet