RFC 4379:Detecting Multi-Protocol Label Switched (...
RFC-Ref

Detecting Multi-Protocol Label Switched (MPLS) Data Plane Failures


1. Introduction
1.1. Conventions
1.2. Structure of This Document
1.3. Contributors
2. Motivation
2.1. Use of Address Range 127/8
3. Packet Format
3.1. Return Codes
3.2. Target FEC Stack
3.2.1. LDP IPv4 Prefix
3.2.2. LDP IPv6 Prefix
3.2.3. RSVP IPv4 LSP
3.2.4. RSVP IPv6 LSP
3.2.5. VPN IPv4 Prefix
3.2.6. VPN IPv6 Prefix
3.2.7. L2 VPN Endpoint
3.2.8. FEC 128 Pseudowire (Deprecated)
3.2.9. FEC 128 Pseudowire (Current)
3.2.10. FEC 129 Pseudowire
3.2.11. BGP Labeled IPv4 Prefix
3.2.12. BGP Labeled IPv6 Prefix
3.2.13. Generic IPv4 Prefix
3.2.14. Generic IPv6 Prefix
3.2.15. Nil FEC
3.3. Downstream Mapping
3.3.1. Multipath Information Encoding
3.3.2. Downstream Router and Interface
3.4. Pad TLV
3.5. Vendor Enterprise Number
3.6. Interface and Label Stack
3.7. Errored TLVs
3.8. Reply TOS Byte TLV
4. Theory of Operation
4.1. Dealing with Equal-Cost Multi-Path (ECMP)
4.2. Testing LSPs That Are Used to Carry MPLS Payloads
4.3. Sending an MPLS Echo Request
4.4. Receiving an MPLS Echo Request
4.4.1. FEC Validation
4.5. Sending an MPLS Echo Reply
4.6. Receiving an MPLS Echo Reply
4.7. Issue with VPN IPv4 and IPv6 Prefixes
4.8. Non-compliant Routers
5. References
5.1. Normative References
5.2. Informative References
6. Security Considerations
7. IANA Considerations
7.1. Message Types, Reply Modes, Return Codes
7.2. TLVs
8. Acknowledgements
9. Authors' Addresses
10. Full Copyright Statement
11. Intellectual Property
12. Acknowledgement

Google
Web
RFC-Ref
RFC-Ref.org
Frontpage
Global Index
RFC
Sister Sites
Chess-Ref.org
Law-Ref.org
InChI.info
Zvon.org