idnits 2.17.1 draft-ietf-mpls-label-encaps-08.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 3032 5 Title: MPLS Label Stack Encoding 6 Author(s): E. Rosen, Y. Rekhter, D. Tappan, G. Fedorkow, 7 D. Farinacci, T. Li, A. Conta 8 Status: Standards Track 9 Date: January 2001 10 Mailbox: erosen@cisco.com, tappan@cisco.com, 11 yakov@juniper.net, fedorkow@cisco.com, 12 dino@procket.com, tli@procket.com, aconta@txc.com 13 Pages: 23 14 Characters: 48314 15 Updates/Obsoletes/SeeAlso: None 17 I-D Tag: draft-ietf-mpls-label-encaps-08.txt 19 URL: ftp://ftp.isi.edu/in-notes/rfc3032.txt 21 "Multi-Protocol Label Switching (MPLS)" [1] requires a set of 22 procedures for augmenting network layer packets with "label stacks", 23 thereby turning them into "labeled packets". Routers which support 24 MPLS are known as "Label Switching Routers", or "LSRs". In order to 25 transmit a labeled packet on a particular data link, an LSR must 26 support an encoding technique which, given a label stack and a 27 network layer packet, produces a labeled packet. This document 28 specifies the encoding to be used by an LSR in order to transmit 29 labeled packets on Point-to-Point Protocol (PPP) data links, on LAN 30 data links, and possibly on other data links as well. On some data 31 links, the label at the top of the stack may be encoded in a different 32 manner, but the techniques described here MUST be used to encode the 33 remainder of the label stack. This document also specifies rules and 34 procedures for processing the various fields of the label stack 35 encoding. 37 This document is a product of the Multiprotocol Label Switching 38 Working Group of the IETF. 40 This is now a Proposed Standard Protocol. 42 This document specifies an Internet standards track protocol for 43 the Internet community, and requests discussion and suggestions 44 for improvements. Please refer to the current edition of the 45 "Internet Official Protocol Standards" (STD 1) for the 46 standardization state and status of this protocol. Distribution 47 of this memo is unlimited. 49 This announcement is sent to the IETF list and the RFC-DIST list. 50 Requests to be added to or deleted from the IETF distribution list 51 should be sent to IETF-REQUEST@IETF.ORG. Requests to be 52 added to or deleted from the RFC-DIST distribution list should 53 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. 55 Details on obtaining RFCs via FTP or EMAIL may be obtained by sending 56 an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 57 help: ways_to_get_rfcs. For example: 59 To: rfc-info@RFC-EDITOR.ORG 60 Subject: getting rfcs 62 help: ways_to_get_rfcs 64 Requests for special distribution should be addressed to either the 65 author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless 66 specifically noted otherwise on the RFC itself, all RFCs are for 67 unlimited distribution.echo 68 Submissions for Requests for Comments should be sent to 69 RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC 70 Authors, for further information.