draft-ietf-mpls-bgp4-mpls-01.txt   draft-ietf-mpls-bgp4-mpls-02.txt 
Network Working Group Yakov Rekhter Network Working Group Yakov Rekhter
Internet Draft Cisco Systems Internet Draft Cisco Systems
Expiration Date: February 1999 Eric Rosen Expiration Date: August 1999 Eric Rosen
Cisco Systems Cisco Systems
Carrying Label Information in BGP-4 Carrying Label Information in BGP-4
draft-ietf-mpls-bgp4-mpls-01.txt draft-ietf-mpls-bgp4-mpls-02.txt
1. Status of this Memo 1. Status of this Memo
This document is an Internet-Draft. Internet-Drafts are working This document is an Internet-Draft and is in full conformance with
documents of the Internet Engineering Task Force (IETF), its areas, all provisions of Section 10 of RFC2026.
and its working groups. Note that other groups may also distribute
working documents as Internet-Drafts. 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.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as ``work in progress.'' material or to cite them other than as ``work in progress.''
To view the entire list of current Internet-Drafts, please check The list of current Internet-Drafts can be accessed at
the "1id-abstracts.txt" listing contained in the Internet-Drafts http://www.ietf.org/ietf/1id-abstracts.txt
Shadow Directories on ftp.is.co.za (Africa), ftp.nordu.net
(Northern Europe), ftp.nis.garr.it (Southern Europe), munnari.oz.au The list of Internet-Draft Shadow Directories can be accessed at
(Pacific Rim), ftp.ietf.org (US East Coast), or ftp.isi.edu http://www.ietf.org/shadow.html.
(US West Coast).
2. Abstract 2. Abstract
When a pair of Label Switch Routers (LSRs) that maintain BGP peering When a pair of Label Switch Routers (LSRs) that maintain BGP peering
with each other exchange routes, the LSRs also need to exchange label with each other exchange routes, the LSRs also need to exchange label
mapping information for these routes. The exchange is accomplished by mapping information for these routes. The exchange is accomplished by
piggybacking the label mapping information for a route in the same piggybacking the label mapping information for a route in the same
BGP Update message that is used to exchange the route. This document BGP Update message that is used to exchange the route. This document
specifies the way in which this is done. specifies the way in which this is done.
skipping to change at page 2, line 19 skipping to change at page 2, line 19
route must be distributed between BGP peers. This document specifies route must be distributed between BGP peers. This document specifies
how this label mapping information is distributed. The label mapping how this label mapping information is distributed. The label mapping
information is included in the BGP Update message that is used to information is included in the BGP Update message that is used to
distribute the route. This is done by utilizing BGP-4 Multiprotocol distribute the route. This is done by utilizing BGP-4 Multiprotocol
Extensions attribute [BGP-MP]. Extensions attribute [BGP-MP].
4. Carrying Label Mapping Information 4. Carrying Label Mapping Information
Label mapping information is carried as part of the Network Layer Label mapping information is carried as part of the Network Layer
Reachability Information (NLRI) in the Multiprotocol Extensions Reachability Information (NLRI) in the Multiprotocol Extensions
attributes. Such NLRI is identified by using Sub-AFI TBD. attributes. Such NLRI is identified by using SAFI TBD.
The Network Layer Reachability information is encoded as one or more The Network Layer Reachability information is encoded as one or more
triples of the form <label, length, prefix>, whose fields are triples of the form <label, length, prefix>, whose fields are
described below: described below:
+---------------------------+ +---------------------------+
| Length (1 octet) | | Length (1 octet) |
+---------------------------+ +---------------------------+
| Label (3 octets) | | Label (3 octets) |
+---------------------------+ +---------------------------+
skipping to change at page 4, line 37 skipping to change at page 4, line 37
To be supplied. To be supplied.
9. References 9. References
[BGP-4] "A Border Gateway Protocol 4 (BGP-4), Y. Rekhter, T. Li (RFC [BGP-4] "A Border Gateway Protocol 4 (BGP-4), Y. Rekhter, T. Li (RFC
1771) http://ds.internic.net/rfc/rfc1771.txt 1771) http://ds.internic.net/rfc/rfc1771.txt
[BGP-CAP] "Capabilities Negotiation with BGP-4", R. Chandra, et al, [BGP-CAP] "Capabilities Negotiation with BGP-4", R. Chandra, et al,
Work in progress, http://www.internic.net/internet-drafts/draft- Work in progress, http://www.internic.net/internet-drafts/draft-
ietf-idr-bgp4-cap-neg-00.txt ietf-idr-bgp4-cap-neg-03.txt
[BGP-MP] "Multiprotocol Extensions for BGP-4", T. Bates, et al (RFC [BGP-MP] "Multiprotocol Extensions for BGP-4", T. Bates, et al (RFC
2283) http://ds.internic.net/rfc/rfc2283.txt 2283) http://ds.internic.net/rfc/rfc2283.txt
[MPLS-ARCH], "A Proposed Architecture for MPLS", E. Rosen, et al, [MPLS-ARCH], "A Proposed Architecture for MPLS", E. Rosen, et al,
Work in progress, http://www.internic.net/internet-drafts/draft- Work in progress, http://www.internic.net/internet-drafts/draft-
ietf-mpls-arch-00.txt ietf-mpls-arch-00.txt
[MPLS-ENCAPS], "MPLS Label Stack Encoding", E. Rosen, et al, Work in [MPLS-ENCAPS], "MPLS Label Stack Encoding", E. Rosen, et al, Work in
progress, http://www.internic.net/internet-drafts/draft-ietf-mpls- progress, http://www.internic.net/internet-drafts/draft-ietf-mpls-
 End of changes. 

This html diff was produced by rfcdiff 1.23, available from http://www.levkowetz.com/ietf/tools/rfcdiff/