RFC 4950: ICMP Extensions for Multiprotocol Label Switching
In plain English — editorial summary, not part of the RFC
This memo defines an extension object that can be appended to selected multi-part ICMP messages. This extension permits Label Switching Routers to append MPLS information to ICMP messages, and has already been widely deployed. [STANDARDS-TRACK]
Document record
- Document ID
- RFC4950
- Published
- August 2007
- Authors
- R. Bonica; D. Gan; D. Tappan; C. Pignataro
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 8
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4884Extended ICMP to Support Multi-Part MessagesUpdated
April 2007
- RFC 5461TCP's Reaction to Soft ErrorsCurrent
February 2009
- RFC 5837Extending ICMP for Interface and Next-Hop IdentificationCurrent
April 2010
- RFC 2765Stateless IP/ICMP Translation Algorithm (SIIT)Obsoleted
February 2000
- RFC 2463Internet Control Message Protocol (ICMPv6) for the Internet Protocol Version 6 (IPv6) SpecificationObsoleted
December 1998
- RFC 4951Fail Over Extensions for Layer 2 Tunneling Protocol (L2TP) "failover"Current
August 2007
- RFC 4940IANA Considerations for OSPFCurrent
July 2007
- RFC 4970Extensions to OSPF for Advertising Optional Router CapabilitiesObsoleted
July 2007
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?