Supported MPLS Standards
The JUNOS Software substantially supports the following MPLS standards.
- RFC 2547, BGP/MPLS VPNs
- RFC 2702, Requirements for Traffic Engineering Over MPLS
- RFC 2858, Multiprotocol Extensions for BGP-4
- RFC 3031, Multiprotocol Label Switching Architecture
- RFC 3032, MPLS Label Stack Encoding
- RFC 3063, MPLS Loop Prevention Mechanism
- RFC 3140, Per Hop Behavior Identification Codes
- RFC 3208, PGM Reliable Transport Protocol Specification
Only the network element is supported.
- RFC 3270, Multi-Protocol Label Switching
(MPLS) Support of Differentiated Services
Only E-LSPs are supported.
- RFC 3443, Time To Live (TTL) Processing in Multi-Protocol Label Switching (MPLS) Networks
- RFC 3469, Framework for Multi-Protocol Label Switching (MPLS)-based Recovery
- RFC 3564, Requirements for Support of Differentiated Services-aware MPLS Traffic Engineering
- RFC 4124, Protocol Extensions for Support of Diffserv-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
- RFC 4379, Detecting Multi-Protocol 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-l3vpn-rfc2547bis-04.txt, BGP/MPLS IP VPNs
- Internet draft draft-ietf-mpls-label-encaps-07.txt, MPLS Label Stack Encoding
- Internet draft draft-ietf-mpls-rsvp-lsp-fastreroute-03.txt, Fast Reroute Extensions to RSVP-TE for LSP Tunnels
Node protection in facility backup is not supported.
- Internet draft draft-ietf-mpls-soft-preemption-00.txt, MPLS Traffic Engineering Soft preemption
- Internet draft draft-ietf-ppvpn-rfc2547bis-03.txt, BGP/MPLS VPNs
- Internet draft draft-martini-l2circuit-encap-mpls-07.txt, Encapsulation Methods for Transport of Layer 2 Frames Over IP
and MPLS Networks
The JUNOS Software 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)
