idnits 2.17.1 draft-ietf-mpls-ttl-04.txt: Skipping this file; it looks like a tombstone file to me. -------------------------------------------------------------------------------- 1 A new Request for Comments is now available in online RFC libraries. 3 RFC 3443 5 Title: Time To Live (TTL) Processing in Multi-Protocol 6 Label Switching (MPLS) Networks 7 Author(s): P. Agarwal, B. Akyol 8 Status: Standards Track 9 Date: January 2003 10 Mailbox: puneet@acm.org, bora@cisco.com 11 Pages: 10 12 Characters: 18749 13 Updates: 3032 15 I-D Tag: draft-ietf-mpls-ttl-04.txt 17 URL: ftp://ftp.rfc-editor.org/in-notes/rfc3443.txt 19 This document describes Time To Live (TTL) processing in hierarchical 20 Multi-Protocol Label Switching (MPLS) networks and is motivated by the 21 need to formalize a TTL-transparent mode of operation for an MPLS 22 label-switched path. It updates RFC 3032, "MPLS Label Stack 23 Encoding". TTL processing in both Pipe and Uniform Model hierarchical 24 tunnels are specified with examples for both "push" and "pop" cases. 25 The document also complements RFC 3270, "MPLS Support of 26 Differentiated Services" and ties together the terminology introduced 27 in that document with TTL processing in hierarchical MPLS networks. 29 This document is a product of the Multiprotocol Label Switching 30 Working Group of the IETF. 32 This is now a Proposed Standard Protocol. 34 This document specifies an Internet standards track protocol for 35 the Internet community, and requests discussion and suggestions 36 for improvements. Please refer to the current edition of the 37 "Internet Official Protocol Standards" (STD 1) for the 38 standardization state and status of this protocol. Distribution 39 of this memo is unlimited. 41 This announcement is sent to the IETF list and the RFC-DIST list. 42 Requests to be added to or deleted from the IETF distribution list 43 should be sent to IETF-REQUEST@IETF.ORG. Requests to be 44 added to or deleted from the RFC-DIST distribution list should 45 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. 47 Details on obtaining RFCs via FTP or EMAIL may be obtained by sending 48 an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 49 help: ways_to_get_rfcs. For example: 51 To: rfc-info@RFC-EDITOR.ORG 52 Subject: getting rfcs 54 help: ways_to_get_rfcs 56 Requests for special distribution should be addressed to either the 57 author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless 58 specifically noted otherwise on the RFC itself, all RFCs are for 59 unlimited distribution.echo 60 Submissions for Requests for Comments should be sent to 61 RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC 62 Authors, for further information.