--- 1/draft-ietf-mpls-arch-06.txt 2006-02-05 00:26:07.000000000 +0100 +++ 2/draft-ietf-mpls-arch-07.txt 2006-02-05 00:26:07.000000000 +0100 @@ -1,24 +1,25 @@ + Network Working Group Eric C. Rosen Internet Draft Cisco Systems, Inc. -Expiration Date: February 2000 +Expiration Date: January 2001 Arun Viswanathan - Lucent Technologies + Force10 Networks, Inc. Ross Callon - IronBridge Networks, Inc. + Juniper Networks, Inc. - August 1999 + July 2000 Multiprotocol Label Switching Architecture - draft-ietf-mpls-arch-06.txt + draft-ietf-mpls-arch-07.txt Status of this Memo This document is an Internet-Draft and is in full conformance with all provisions of Section 10 of RFC2026. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that other groups may also distribute working documents as Internet- Drafts. @@ -248,36 +249,33 @@ precedence or class of service. MPLS stands for "Multiprotocol" Label Switching, multiprotocol because its techniques are applicable to ANY network layer protocol. In this document, however, we focus on the use of IP as the network layer protocol. A router which supports MPLS is known as a "Label Switching Router", or LSR. - A general discussion of issues related to MPLS is presented in "A - Framework for Multiprotocol Label Switching" [MPLS-FRMWRK]. - 2.2. Terminology This section gives a general conceptual overview of the terms used in this document. Some of these terms are more precisely defined in later sections of the document. DLCI a label used in Frame Relay networks to identify frame relay circuits + forwarding equivalence class a group of IP packets which are forwarded in the same manner (e.g., over the same path, with the same forwarding treatment) - frame merge label merging, when it is applied to operation over frame based media, so that the potential problem of cell interleave is not an issue. label a short fixed length physically contiguous identifier which is used to identify a FEC, usually of local significance. @@ -530,23 +528,23 @@ set of bindings, but not with respect to some other set of bindings.) The label distribution protocol also encompasses any negotiations in which two label distribution peers need to engage in order to learn of each other's MPLS capabilities. THE ARCHITECTURE DOES NOT ASSUME THAT THERE IS ONLY A SINGLE LABEL DISTRIBUTION PROTOCOL. In fact, a number of different label distribution protocols are being standardized. Existing protocols have been extended so that label distribution can be piggybacked on - them (see, e.g., [MPLS-BGP], [MPLS-RSVP], [MPLS-RSVP-TUNNELS]). New - protocols have also been defined for the explicit purpose of - distributing labels (see, e.g., [MPLS-LDP], [MPLS-CR-LDP]. + them (see, e.g., [MPLS-BGP], [MPLS-RSVP-TUNNELS]). New protocols + have also been defined for the explicit purpose of distributing + labels (see, e.g., [MPLS-LDP], [MPLS-CR-LDP]. In this document, we try to use the acronym "LDP" to refer specifically to the protocol defined in [MPLS-LDP]; when speaking of label distribution protocols in general, we try to avoid the acronym. 3.7. Unsolicited Downstream vs. Downstream-on-Demand The MPLS architecture allows an LSR to explicitly request, from its next hop for a particular FEC, a label binding for that FEC. This is known as "downstream-on-demand" label distribution. @@ -2755,56 +2753,46 @@ 8. Authors' Addresses Eric C. Rosen Cisco Systems, Inc. 250 Apollo Drive Chelmsford, MA, 01824 E-mail: erosen@cisco.com Arun Viswanathan - Lucent Technologies - 101 Crawford Corner Rd., #4D-537 - Holmdel, NJ 07733 - 732-332-5163 - E-mail: arunv@dnrc.bell-labs.com + Force10 Networks, Inc. + 1440 McCarthy Blvd. + Milpitas, CA 95035-7438 + E-mail: arun@force10networks.com Ross Callon - IronBridge Networks - 55 Hayden Avenue, - Lexington, MA 02173 - +1-781-372-8117 - E-mail: rcallon@ironbridgenetworks.com + Juniper Networks, Inc. + 1194 North Mathilda Avenue + Sunnyvale, CA 94089 USA + E-mail: rcallon@juniper.net 9. References [MPLS-ATM] "MPLS using LDP and ATM VC Switching", Davie, Doolan, - Lawrence, McGloghrie, Rekhter, Rosen, Swallow, work in progress, - April 1999. + Lawrence, McGloghrie, Rekhter, Rosen, Swallow, work in progress, June + 2000. [MPLS-BGP] "Carrying Label Information in BGP-4", Rekhter, Rosen, - work in progress, February 1999. + work in progress, January 2000. [MPLS-CR-LDP] "Constraint-Based LSP Setup using LDP", Jamoussi, - editor, work in progress, March 1999. - - [MPLS-FRMWRK] "A Framework for Multiprotocol Label Switching", - Callon, Doolan, Feldman, Fredette, Swallow, Viswanathan, work in - progress, November 1997 + editor, work in progress, July 2000. [MPLS-FRMRLY] "Use of Label Switching on Frame Relay Networks", - Conta, Doolan, Malis, work in progress, November 1998 + Conta, Doolan, Malis, work in progress, June 2000. [MPLS-LDP], "LDP Specification", Andersson, Doolan, Feldman, - Fredette, Thomas, work in progress, April 1999. - - [MPLS-RSVP] "Use of Label Switching with RSVP", Davie, Rekhter, - Rosen, Viswanathan, Srinivasan, work in progress, March 1998. + Fredette, Thomas, work in progress, June 2000. [MPLS-RSVP-TUNNELS], "Extensions to RSVP for LSP Tunnels", Awduche, - Berger, Gan, Li, Swallow, Srinvasan, work in progress, March 1999. + Berger, Gan, Li, Swallow, Srinvasan, work in progress, February 2000. [MPLS-SHIM] "MPLS Label Stack Encodings", Rosen, Rekhter, Tappan, - Farinacci, Fedorkow, Li, Conta, work in progress, April 1999. + Farinacci, Fedorkow, Li, Conta, work in progress, July 2000. - [MPLS-TRFENG] "Requirements for Traffic Engineering Over MPLS", - Awduche, Malcolm, Agogbua, O'Dell, McManus, work in progress, August - 1998. + [MPLS-TRFENG] RFC 2702, "Requirements for Traffic Engineering Over + MPLS", Awduche, Malcolm, Agogbua, O'Dell, McManus, September 1999.