RFC 3443: Time To Live (TTL) Processing in Multi-Protocol Label Switching (MPLS) Networks
In plain English — editorial summary, not part of the RFC
This document describes Time To Live (TTL) processing in hierarchical Multi-Protocol Label Switching (MPLS) networks and is motivated by the need to formalize a TTL-transparent mode of operation for an MPLS label-switched path. It updates RFC 3032, "MPLS Label Stack Encoding". TTL processing in both Pipe and Uniform Model hierarchical tunnels are specified with examples for both "push" and "pop" cases. The document also complements RFC 3270, "MPLS Support of Differentiated Services" and ties together the terminology introduced in that document with TTL processing in hierarchical MPLS networks. [STANDARDS-TRACK]
Document record
- Document ID
- RFC3443
- Published
- January 2003
- Authors
- P. Agarwal; B. Akyol
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 10
- Also known as
- —
Topics
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3478Graceful Restart Mechanism for Label Distribution ProtocolCurrent
February 2003
- RFC 3270Multi-Protocol Label Switching (MPLS) Support of Differentiated ServicesUpdated
May 2002
- RFC 3035MPLS using LDP and ATM VC SwitchingCurrent
January 2001
- RFC 3034Use of Label Switching on Frame Relay Networks SpecificationCurrent
January 2001
- RFC 4558Node-ID Based Resource Reservation Protocol (RSVP) Hello: A Clarification StatementCurrent
June 2006
- RFC 7152Requirements for Metro Ethernet Forum (MEF) Ethernet-Tree (E-Tree) Support in Layer 2 Virtual Private Network (L2VPN)Current
March 2014
- RFC 3477Signalling Unnumbered Links in Resource ReSerVation Protocol - Traffic Engineering (RSVP-TE)Updated
February 2003
- RFC 3479Fault Tolerance for the Label Distribution Protocol (LDP)Current
February 2003
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?