draft-ietf-mpls-rfc3107bis-03.txt   draft-ietf-mpls-rfc3107bis-04.txt 
Internet Engineering Task Force E. Rosen Internet Engineering Task Force E. Rosen
Internet-Draft Juniper Networks, Inc. Internet-Draft Juniper Networks, Inc.
Obsoletes: 3107 (if approved) August 3, 2017 Obsoletes: 3107 (if approved) August 17, 2017
Intended status: Standards Track Intended status: Standards Track
Expires: February 4, 2018 Expires: February 18, 2018
Using BGP to Bind MPLS Labels to Address Prefixes Using BGP to Bind MPLS Labels to Address Prefixes
draft-ietf-mpls-rfc3107bis-03 draft-ietf-mpls-rfc3107bis-04
Abstract Abstract
This document specifies a set of procedures for using BGP to This document specifies a set of procedures for using BGP to
advertise that a specified router has bound a specified MPLS label advertise that a specified router has bound a specified MPLS label
(or a specified sequence of MPLS labels, organized as a contiguous (or a specified sequence of MPLS labels, organized as a contiguous
part of a label stack) to a specified address prefix. This can be part of a label stack) to a specified address prefix. This can be
done by sending a BGP UPDATE message whose Network Layer Reachability done by sending a BGP UPDATE message whose Network Layer Reachability
Information field contains both the prefix and the MPLS label(s), and Information field contains both the prefix and the MPLS label(s), and
whose Next Hop field identifies the node at which said prefix is whose Next Hop field identifies the node at which said prefix is
skipping to change at page 1, line 38 skipping to change at page 1, line 38
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
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."
This Internet-Draft will expire on February 4, 2018. This Internet-Draft will expire on February 18, 2018.
Copyright Notice Copyright Notice
Copyright (c) 2017 IETF Trust and the persons identified as the Copyright (c) 2017 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 2, line 17 skipping to change at page 2, line 17
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Using BGP to Bind an Address Prefix to One or More MPLS 2. Using BGP to Bind an Address Prefix to One or More MPLS
Labels . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 Labels . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
2.1. Multiple Labels Capability . . . . . . . . . . . . . . . 5 2.1. Multiple Labels Capability . . . . . . . . . . . . . . . 5
2.2. NLRI Encoding when the Multiple Labels Capability is 2.2. NLRI Encoding when the Multiple Labels Capability is
Not Used . . . . . . . . . . . . . . . . . . . . . . . . 8 Not Used . . . . . . . . . . . . . . . . . . . . . . . . 8
2.3. NLRI Encoding when the Multiple Labels Capability is Used 9 2.3. NLRI Encoding when the Multiple Labels Capability is Used 10
2.4. How to Explicitly Withdraw the Binding of a Label to a 2.4. How to Explicitly Withdraw the Binding of a Label to a
Prefix . . . . . . . . . . . . . . . . . . . . . . . . . 11 Prefix . . . . . . . . . . . . . . . . . . . . . . . . . 11
2.5. Changing the Label that is Bound to a Prefix . . . . . . 12 2.5. Changing the Label that is Bound to a Prefix . . . . . . 12
3. Installing and/or Propagating SAFI-4 or SAFI-128 Routes . . . 13 3. Installing and/or Propagating SAFI-4 or SAFI-128 Routes . . . 13
3.1. Comparability of Routes . . . . . . . . . . . . . . . . . 13 3.1. Comparability of Routes . . . . . . . . . . . . . . . . . 13
3.2. Modification of Label(s) Field When Propagating . . . . . 14 3.2. Modification of Label(s) Field When Propagating . . . . . 14
3.2.1. When the Next Hop Field is Unchanged . . . . . . . . 14 3.2.1. When the Next Hop Field is Unchanged . . . . . . . . 14
3.2.2. When the Next Hop Field is Changed . . . . . . . . . 14 3.2.2. When the Next Hop Field is Changed . . . . . . . . . 14
4. Data Plane . . . . . . . . . . . . . . . . . . . . . . . . . 15 4. Data Plane . . . . . . . . . . . . . . . . . . . . . . . . . 15
5. Relationship Between SAFI-4 and SAFI-1 Routes . . . . . . . . 17 5. Relationship Between SAFI-4 and SAFI-1 Routes . . . . . . . . 17
skipping to change at page 6, line 26 skipping to change at page 6, line 26
The value field of the Multiple Labels Capability (shown in Figure 1) The value field of the Multiple Labels Capability (shown in Figure 1)
consists of one or more triples, where each triple consists of four consists of one or more triples, where each triple consists of four
octets. The first two octets of a triple specify an AFI value, the octets. The first two octets of a triple specify an AFI value, the
third octet specifies a SAFI value, and the fourth specifies a Count. third octet specifies a SAFI value, and the fourth specifies a Count.
If one of the triples is <AFI,SAFI,Count>, the Count is the maximum If one of the triples is <AFI,SAFI,Count>, the Count is the maximum
number of labels that the BGP speaker sending the Capability can number of labels that the BGP speaker sending the Capability can
process in a received UPDATE of the specified AFI/SAFI. If the count process in a received UPDATE of the specified AFI/SAFI. If the count
is 255, then no limit has been placed on the number of labels that is 255, then no limit has been placed on the number of labels that
can be processed in a received UPDATE of the specified AFI/SAFI. can be processed in a received UPDATE of the specified AFI/SAFI.
Any implementation that sends a Multiple Labels Capability MUST be
able to support at least two labels in the NLRI. However, there may
be deployment scenarios in which a larger number of labels is needed.
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AFI | SAFI | Count ~ | AFI | SAFI | Count ~
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
~ AFI | SAFI | Count | ~ AFI | SAFI | Count |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 1: Value Field of Multiple Labels Capability Figure 1: Value Field of Multiple Labels Capability
skipping to change at page 20, line 29 skipping to change at page 20, line 31
Jeff Haas, Jonathan Hardwick, Jakob Heitz, Alexander Okonnikov, Keyur Jeff Haas, Jonathan Hardwick, Jakob Heitz, Alexander Okonnikov, Keyur
Patel, Kevin Wang, and Lucy Yong for their review of and comments on Patel, Kevin Wang, and Lucy Yong for their review of and comments on
this document. this document.
9. References 9. References
9.1. Normative References 9.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997, DOI 10.17487/RFC2119, March 1997, <https://www.rfc-
<http://www.rfc-editor.org/info/rfc2119>. editor.org/info/rfc2119>.
[RFC3031] Rosen, E., Viswanathan, A., and R. Callon, "Multiprotocol [RFC3031] Rosen, E., Viswanathan, A., and R. Callon, "Multiprotocol
Label Switching Architecture", RFC 3031, Label Switching Architecture", RFC 3031,
DOI 10.17487/RFC3031, January 2001, DOI 10.17487/RFC3031, January 2001, <https://www.rfc-
<http://www.rfc-editor.org/info/rfc3031>. editor.org/info/rfc3031>.
[RFC3032] Rosen, E., Tappan, D., Fedorkow, G., Rekhter, Y., [RFC3032] Rosen, E., Tappan, D., Fedorkow, G., Rekhter, Y.,
Farinacci, D., Li, T., and A. Conta, "MPLS Label Stack Farinacci, D., Li, T., and A. Conta, "MPLS Label Stack
Encoding", RFC 3032, DOI 10.17487/RFC3032, January 2001, Encoding", RFC 3032, DOI 10.17487/RFC3032, January 2001,
<http://www.rfc-editor.org/info/rfc3032>. <https://www.rfc-editor.org/info/rfc3032>.
[RFC3107] Rekhter, Y. and E. Rosen, "Carrying Label Information in [RFC3107] Rekhter, Y. and E. Rosen, "Carrying Label Information in
BGP-4", RFC 3107, DOI 10.17487/RFC3107, May 2001, BGP-4", RFC 3107, DOI 10.17487/RFC3107, May 2001,
<http://www.rfc-editor.org/info/rfc3107>. <https://www.rfc-editor.org/info/rfc3107>.
[RFC3443] Agarwal, P. and B. Akyol, "Time To Live (TTL) Processing [RFC3443] Agarwal, P. and B. Akyol, "Time To Live (TTL) Processing
in Multi-Protocol Label Switching (MPLS) Networks", in Multi-Protocol Label Switching (MPLS) Networks",
RFC 3443, DOI 10.17487/RFC3443, January 2003, RFC 3443, DOI 10.17487/RFC3443, January 2003,
<http://www.rfc-editor.org/info/rfc3443>. <https://www.rfc-editor.org/info/rfc3443>.
[RFC4271] Rekhter, Y., Ed., Li, T., Ed., and S. Hares, Ed., "A [RFC4271] Rekhter, Y., Ed., Li, T., Ed., and S. Hares, Ed., "A
Border Gateway Protocol 4 (BGP-4)", RFC 4271, Border Gateway Protocol 4 (BGP-4)", RFC 4271,
DOI 10.17487/RFC4271, January 2006, DOI 10.17487/RFC4271, January 2006, <https://www.rfc-
<http://www.rfc-editor.org/info/rfc4271>. editor.org/info/rfc4271>.
[RFC4364] Rosen, E. and Y. Rekhter, "BGP/MPLS IP Virtual Private [RFC4364] Rosen, E. and Y. Rekhter, "BGP/MPLS IP Virtual Private
Networks (VPNs)", RFC 4364, DOI 10.17487/RFC4364, February Networks (VPNs)", RFC 4364, DOI 10.17487/RFC4364, February
2006, <http://www.rfc-editor.org/info/rfc4364>. 2006, <https://www.rfc-editor.org/info/rfc4364>.
[RFC4659] De Clercq, J., Ooms, D., Carugi, M., and F. Le Faucheur, [RFC4659] De Clercq, J., Ooms, D., Carugi, M., and F. Le Faucheur,
"BGP-MPLS IP Virtual Private Network (VPN) Extension for "BGP-MPLS IP Virtual Private Network (VPN) Extension for
IPv6 VPN", RFC 4659, DOI 10.17487/RFC4659, September 2006, IPv6 VPN", RFC 4659, DOI 10.17487/RFC4659, September 2006,
<http://www.rfc-editor.org/info/rfc4659>. <https://www.rfc-editor.org/info/rfc4659>.
[RFC4760] Bates, T., Chandra, R., Katz, D., and Y. Rekhter, [RFC4760] Bates, T., Chandra, R., Katz, D., and Y. Rekhter,
"Multiprotocol Extensions for BGP-4", RFC 4760, "Multiprotocol Extensions for BGP-4", RFC 4760,
DOI 10.17487/RFC4760, January 2007, DOI 10.17487/RFC4760, January 2007, <https://www.rfc-
<http://www.rfc-editor.org/info/rfc4760>. editor.org/info/rfc4760>.
[RFC4798] De Clercq, J., Ooms, D., Prevost, S., and F. Le Faucheur, [RFC4798] De Clercq, J., Ooms, D., Prevost, S., and F. Le Faucheur,
"Connecting IPv6 Islands over IPv4 MPLS Using IPv6 "Connecting IPv6 Islands over IPv4 MPLS Using IPv6
Provider Edge Routers (6PE)", RFC 4798, Provider Edge Routers (6PE)", RFC 4798,
DOI 10.17487/RFC4798, February 2007, DOI 10.17487/RFC4798, February 2007, <https://www.rfc-
<http://www.rfc-editor.org/info/rfc4798>. editor.org/info/rfc4798>.
[RFC5462] Andersson, L. and R. Asati, "Multiprotocol Label Switching [RFC5462] Andersson, L. and R. Asati, "Multiprotocol Label Switching
(MPLS) Label Stack Entry: "EXP" Field Renamed to "Traffic (MPLS) Label Stack Entry: "EXP" Field Renamed to "Traffic
Class" Field", RFC 5462, DOI 10.17487/RFC5462, February Class" Field", RFC 5462, DOI 10.17487/RFC5462, February
2009, <http://www.rfc-editor.org/info/rfc5462>. 2009, <https://www.rfc-editor.org/info/rfc5462>.
[RFC5492] Scudder, J. and R. Chandra, "Capabilities Advertisement [RFC5492] Scudder, J. and R. Chandra, "Capabilities Advertisement
with BGP-4", RFC 5492, DOI 10.17487/RFC5492, February with BGP-4", RFC 5492, DOI 10.17487/RFC5492, February
2009, <http://www.rfc-editor.org/info/rfc5492>. 2009, <https://www.rfc-editor.org/info/rfc5492>.
[RFC5549] Le Faucheur, F. and E. Rosen, "Advertising IPv4 Network [RFC5549] Le Faucheur, F. and E. Rosen, "Advertising IPv4 Network
Layer Reachability Information with an IPv6 Next Hop", Layer Reachability Information with an IPv6 Next Hop",
RFC 5549, DOI 10.17487/RFC5549, May 2009, RFC 5549, DOI 10.17487/RFC5549, May 2009,
<http://www.rfc-editor.org/info/rfc5549>. <https://www.rfc-editor.org/info/rfc5549>.
[RFC7606] Chen, E., Ed., Scudder, J., Ed., Mohapatra, P., and K. [RFC7606] Chen, E., Ed., Scudder, J., Ed., Mohapatra, P., and K.
Patel, "Revised Error Handling for BGP UPDATE Messages", Patel, "Revised Error Handling for BGP UPDATE Messages",
RFC 7606, DOI 10.17487/RFC7606, August 2015, RFC 7606, DOI 10.17487/RFC7606, August 2015,
<http://www.rfc-editor.org/info/rfc7606>. <https://www.rfc-editor.org/info/rfc7606>.
9.2. Informative References 9.2. Informative References
[Enhanced-GR] [Enhanced-GR]
Patel, K., Chen, E., Fernando, R., and J. Scudder, Patel, K., Chen, E., Fernando, R., and J. Scudder,
"Accelerated Routing Convergence for BGP Graceful "Accelerated Routing Convergence for BGP Graceful
Restart", internet-draft draft-ietf-idr-enhanced-gr-06, Restart", internet-draft draft-ietf-idr-enhanced-gr-06,
June 2016. June 2016.
[RFC4724] Sangli, S., Chen, E., Fernando, R., Scudder, J., and Y. [RFC4724] Sangli, S., Chen, E., Fernando, R., Scudder, J., and Y.
Rekhter, "Graceful Restart Mechanism for BGP", RFC 4724, Rekhter, "Graceful Restart Mechanism for BGP", RFC 4724,
DOI 10.17487/RFC4724, January 2007, DOI 10.17487/RFC4724, January 2007, <https://www.rfc-
<http://www.rfc-editor.org/info/rfc4724>. editor.org/info/rfc4724>.
[RFC5331] Aggarwal, R., Rekhter, Y., and E. Rosen, "MPLS Upstream [RFC5331] Aggarwal, R., Rekhter, Y., and E. Rosen, "MPLS Upstream
Label Assignment and Context-Specific Label Space", Label Assignment and Context-Specific Label Space",
RFC 5331, DOI 10.17487/RFC5331, August 2008, RFC 5331, DOI 10.17487/RFC5331, August 2008,
<http://www.rfc-editor.org/info/rfc5331>. <https://www.rfc-editor.org/info/rfc5331>.
[RFC6514] Aggarwal, R., Rosen, E., Morin, T., and Y. Rekhter, "BGP [RFC6514] Aggarwal, R., Rosen, E., Morin, T., and Y. Rekhter, "BGP
Encodings and Procedures for Multicast in MPLS/BGP IP Encodings and Procedures for Multicast in MPLS/BGP IP
VPNs", RFC 6514, DOI 10.17487/RFC6514, February 2012, VPNs", RFC 6514, DOI 10.17487/RFC6514, February 2012,
<http://www.rfc-editor.org/info/rfc6514>. <https://www.rfc-editor.org/info/rfc6514>.
[RFC7432] Sajassi, A., Ed., Aggarwal, R., Bitar, N., Isaac, A., [RFC7432] Sajassi, A., Ed., Aggarwal, R., Bitar, N., Isaac, A.,
Uttaro, J., Drake, J., and W. Henderickx, "BGP MPLS-Based Uttaro, J., Drake, J., and W. Henderickx, "BGP MPLS-Based
Ethernet VPN", RFC 7432, DOI 10.17487/RFC7432, February Ethernet VPN", RFC 7432, DOI 10.17487/RFC7432, February
2015, <http://www.rfc-editor.org/info/rfc7432>. 2015, <https://www.rfc-editor.org/info/rfc7432>.
[RFC7911] Walton, D., Retana, A., Chen, E., and J. Scudder, [RFC7911] Walton, D., Retana, A., Chen, E., and J. Scudder,
"Advertisement of Multiple Paths in BGP", RFC 7911, "Advertisement of Multiple Paths in BGP", RFC 7911,
DOI 10.17487/RFC7911, July 2016, DOI 10.17487/RFC7911, July 2016, <https://www.rfc-
<http://www.rfc-editor.org/info/rfc7911>. editor.org/info/rfc7911>.
[TUNNEL-ENCAPS] [TUNNEL-ENCAPS]
Rosen, E., Patel, K., and G. Vandevelde, "The BGP Tunnel Rosen, E., Patel, K., and G. Vandevelde, "The BGP Tunnel
Encapulation Attribute", internet-draft draft-ietf-idr- Encapulation Attribute", internet-draft draft-ietf-idr-
tunnel-encaps-07, July 2017. tunnel-encaps-07, July 2017.
Author's Address Author's Address
Eric C. Rosen Eric C. Rosen
Juniper Networks, Inc. Juniper Networks, Inc.
 End of changes. 25 change blocks. 
31 lines changed or deleted 35 lines changed or added

This html diff was produced by rfcdiff 1.45. The latest version is available from http://tools.ietf.org/tools/rfcdiff/