draft-ietf-bier-bgp-ls-bier-ext-03.txt   draft-ietf-bier-bgp-ls-bier-ext-04.txt 
Networking Working Group Ran. Chen Networking Working Group Ran. Chen
Internet-Draft Zheng. Zhang Internet-Draft Zheng. Zhang
Intended status: Standards Track ZTE Corporation Intended status: Standards Track ZTE Corporation
Expires: March 3, 2019 Vengada. Govindan Expires: April 11, 2019 Vengada. Govindan
IJsbrand. Wijnands IJsbrand. Wijnands
Cisco Cisco
August 30, 2018 October 8, 2018
BGP Link-State extensions for BIER BGP Link-State extensions for BIER
draft-ietf-bier-bgp-ls-bier-ext-03 draft-ietf-bier-bgp-ls-bier-ext-04
Abstract Abstract
Bit Index Explicit Replication (BIER) is an architecture that Bit Index Explicit Replication (BIER) is an architecture that
provides optimal multicast forwarding through a "BIER domain" without provides optimal multicast forwarding through a "BIER domain" without
requiring intermediate routers to maintain any multicast related per- requiring intermediate routers to maintain any multicast related per-
flow state. BIER also does not require any explicit tree-building flow state. BIER also does not require any explicit tree-building
protocol for its operation. A multicast data packet enters a BIER protocol for its operation. A multicast data packet enters a BIER
domain at a "Bit-Forwarding Ingress Router" (BFIR), and leaves the domain at a "Bit-Forwarding Ingress Router" (BFIR), and leaves the
BIER domain at one or more "Bit-Forwarding Egress Routers" (BFERs). BIER domain at one or more "Bit-Forwarding Egress Routers" (BFERs).
skipping to change at page 1, line 47 skipping to change at page 1, line 47
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 https://datatracker.ietf.org/drafts/current/. Drafts is at https://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 March 3, 2019. This Internet-Draft will expire on April 11, 2019.
Copyright Notice Copyright Notice
Copyright (c) 2018 IETF Trust and the persons identified as the Copyright (c) 2018 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
(https://trustee.ietf.org/license-info) in effect on the date of (https://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 26 skipping to change at page 2, line 26
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
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. Conventions used in this document . . . . . . . . . . . . . . 3 2. Conventions used in this document . . . . . . . . . . . . . . 3
3. BGP-LS Extensions for BIER . . . . . . . . . . . . . . . . . 3 3. BGP-LS Extensions for BIER . . . . . . . . . . . . . . . . . 3
3.1. The BIER TLV . . . . . . . . . . . . . . . . . . . . . . 3 3.1. The BIER TLV . . . . . . . . . . . . . . . . . . . . . . 3
3.1.1. The BIER MPLS Encapsulation Sub-TLV . . . . . . . . . 4 3.2. The BIER MPLS Encapsulation Sub-TLV . . . . . . . . . . . 4
3.2. The BIER-TE TLV . . . . . . . . . . . . . . . . . . . . . 5 3.3. The BIER-TE TLV . . . . . . . . . . . . . . . . . . . . . 5
4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 6 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5
5. Security Considerations . . . . . . . . . . . . . . . . . . . 6 5. Security Considerations . . . . . . . . . . . . . . . . . . . 6
6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 6 6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 6
7. Normative references . . . . . . . . . . . . . . . . . . . . 6 7. Normative references . . . . . . . . . . . . . . . . . . . . 6
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 7 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 7
1. Introduction 1. Introduction
Bit Index Explicit Replication (BIER) is an architecture that Bit Index Explicit Replication (BIER) is an architecture that
provides optimal multicast forwarding through a "BIER domain" without provides optimal multicast forwarding through a "BIER domain" without
requiring intermediate routers to maintain any multicast related per- requiring intermediate routers to maintain any multicast related per-
skipping to change at page 3, line 16 skipping to change at page 3, line 16
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC2119. document are to be interpreted as described in RFC2119.
3. BGP-LS Extensions for BIER 3. BGP-LS Extensions for BIER
Each BFR MUST be assigned a "BFR-Prefix". A BFR's BFR-Prefix MUST be Each BFR MUST be assigned a "BFR-Prefix". A BFR's BFR-Prefix MUST be
an IP address (either IPv4 or IPv6) of the BFR, and MUST be unique an IP address (either IPv4 or IPv6) of the BFR, and MUST be unique
and routable within the BIER domain as described in section 2 of and routable within the BIER domain as described in section 2 of
[I-D.ietf-bier-architecture], and then external component (e.g., a [RFC8279], and then external component (e.g., a controller) need to
controller) need to collect BIER information of BIER routers are collect BIER information of BIER routers are associated with the BFR-
associated with the BFR-Prefix in the "northbound" direction within Prefix in the "northbound" direction within the BIER domain.
the BIER domain.
Given that the BIER information is associated with the prefix, the Given that the BIER information is associated with the prefix, the
BGP-LS Prefix Attribute TLV [I-D.ietf-idr-ls-distribution] can be BGP-LS Prefix Attribute TLV [RFC7752] can be used to carry the BIER
used to carry the BIER information. A new Prefix Attribute TLV and information. A new Prefix Attribute TLV and Sub-TLV are defined for
Sub-TLV are defined for the encoding of BIER information. the encoding of BIER information.
3.1. The BIER TLV 3.1. The BIER TLV
A new Prefix Attribute TLV (defined in [I-D.ietf-idr-ls-distribution] A new Prefix Attribute TLV (defined in [RFC7752] is defined for
is defined for distributing BIER information. The new TLV is called distributing BIER information. The new TLV is called the BIER TLV.
the BIER TLV. The BIER TLVs may appear multiple times. The BIER TLVs may appear multiple times.
The following BIER TLV is defined: The following BIER TLV is defined:
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length | | Type | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| reserved | subdomain-id | MT-ID | BSL | | BAR | IPA | subdomain-id | MT-ID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| BFR-id | reserved | | BFR-id | BS Length | Reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Sub-TLVs (variable) | | Sub-TLVs (variable) |
+- -+ +- -+
| | | |
Figure 1 Figure 1
Type:as indicated in IANA Considerations section. Type:as indicated in IANA Considerations section.
Length: 2 octet. Length: 2 octet.
Reserved: MUST be 0 on transmission, ignored on reception. May be Reserved: MUST be 0 on transmission, ignored on reception. May be
used in future versions. used in future versions.
BAR: A 1 octet field encoding the BIER Algorithm, used to calculate
underlay paths to reach BFERs. Values are allocated from the "BIER
Algorithms" registry which is defined in [RFC8401].
IPA: A 1 octet field encoding the IGP Algorithm, used to either
modify,enhance, or replace the calculation of underlay paths to reach
BFERs as defined by the BAR value. Values are from the IGP Algorithm
registry.
Subdomain-id: Unique value identifying the BIER sub-domain, 1 octet. Subdomain-id: Unique value identifying the BIER sub-domain, 1 octet.
MT-ID: Multi-Topology ID that identifies the topology that is MT-ID: Multi-Topology ID that identifies the topology that is
associated with the BIER sub-domain.1 octet. associated with the BIER sub-domain.1 octet.
BitString Length (BS Len): A 1 octet field encoding the supported
BitString length associated with this BFR-prefix.This field are
specified in section 3 of [I-D.ietf-bier-mpls-encapsulation].Given
that the bier router can support BSL values set, this field encoding
the BSL values set that BIER routers supported.
BFR-id: A 2 octet field encoding the BFR-id, as documented in BFR-id: A 2 octet field encoding the BFR-id, as documented in
[I-D.ietf-bier-architecture]. If the BFR-id is zero, it means, the [RFC8279]. If the BFR-id is zero, it means, the advertising router
advertising router is not advertising any BIER-id.In some is not advertising any BIER-id.In some environment, BFR-id can be
environment, BFR-id can be configured by NMS, The BFR-id should be configured by NMS, The BFR-id should be sent to a controller.
sent to a controller.
If multiple BIER Sub-TLVs are present, all having the same BS Length BS Length: A 1 octet field encoding the Bitstring length as per
and Subdomain-id values, first one MUST be used and subsequent ones [[RFC8296]]
MUST be ignored.
3.1.1. The BIER MPLS Encapsulation Sub-TLV If the MT-ID value is outside of the values specified in [RFC4915],
the BIER Sub-TLV MUST be ignored.
3.2. The BIER MPLS Encapsulation Sub-TLV
The BIER MPLS Encapsulation Sub-TLV is a sub-TLV of the BIER TLV. The BIER MPLS Encapsulation Sub-TLV is a sub-TLV of the BIER TLV.
BIER MPLS Encapsulation Sub-TLV is used in order to advertise MPLS BIER MPLS Encapsulation Sub-TLV is used in order to advertise MPLS
specific information used for BIER. It MUST appear multiple times in specific information used for BIER. It MUST appear multiple times in
the BIER TLV as described in [I-D.ietf-bier-ospf-bier-extensions] the BIER TLV as described in [I-D.ietf-bier-ospf-bier-extensions]
In some environment, each router allocates its labels, and advertises In some environment, each router allocates its labels, and advertises
it to the controller.That solution is simpler as the controller does it to the controller.That solution is simpler as the controller does
not need to deal with label allocation. If the controller has to not need to deal with label allocation. If the controller has to
deal with Label allocation , there needs to be a (global) range deal with Label allocation , there needs to be a (global) range
skipping to change at page 5, line 10 skipping to change at page 5, line 10
having the router allocate the BIER Label range and advertise it to having the router allocate the BIER Label range and advertise it to
the controller. the controller.
The following the BIER MPLS Encapsulation Sub-TLV is defined: The following the BIER MPLS Encapsulation Sub-TLV is defined:
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length | | Type | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|Lbl Range Size | Label Range Base | | Max SI | Label |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| BS Length | Reserved | | BS Length | Reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 2 Figure 2
Type: as indicated in IANA Considerations section. Type: as indicated in IANA Considerations section.
Length: 2 octet. Length: 2 octet.
Label Range Size: A 1 octet field encoding the label range size of Max SI: A 1 octet field encoding the maximum Set Identifier(as
the label range. It MUST be greater than 0, otherwise the TLV MUST defined in [[RFC8279]]), used in the encapsulation for this BIER
be ignored. subdomain for this BitString length.
Label Range Base: A 3 octet field, where the 20 rightmost bits
represent the first label in the label range.
BS Length: Bitstring length for the label range that this router is Label: A 3 octet field, where the 20 rightmost bits represent the
advertising per [I-D.ietf-bier-mpls-encapsulation]. 1 octet.The first label in the label range.
values allowed in this field are specified in section 3 of
[I-D.ietf-bier-mpls-encapsulation].
The "label range" is the set of labels beginning with the label range BS Length: A 1 octet field encoding the Bitstring length as per
base and ending with (label range base)+(label range size)-1. A [[RFC8296]]
unique label range is allocated for each BitStream length and Sub-
domain-ID. These label is used for BIER forwarding as described in
[I-D.ietf-bier-architecture] and
[I-D.ietf-bier-mpls-encapsulation].Label ranges within the sub-TLV
MUST NOT overlap, otherwise the whole sub-TLV MUST be disregarded
BS length in multiple BIER MPLS Encapsulation Sub-TLV inside the same BS length in multiple BIER MPLS Encapsulation Sub-TLV inside the same
BIER Sub-TLV MUST NOT repeat, otherwise only the first BIER MPLS BIER Sub-TLV MUST NOT repeat, otherwise only the first BIER MPLS
Encapsulation Sub-TLV with such BS length MUST be used and any Encapsulation Sub-TLV with such BS length MUST be used and any
subsequent BIER MPLS Encapsulation Sub-TLVs with the same BS length subsequent BIER MPLS Encapsulation Sub-TLVs with the same BS length
MUST be ignored. MUST be ignored.
3.2. The BIER-TE TLV 3.3. The BIER-TE TLV
This TLV is used to collect BIER-TE information in the "northbound" This TLV is used to collect BIER-TE information in the "northbound"
direction within the BIER-TE domain. direction within the BIER-TE domain.
The section will be added in next version. The section will be added in next version.
4. IANA Considerations 4. IANA Considerations
This document requests assigning code-points from the registry for This document requests assigning code-points from the registry for
the new Prefix Attribute TLV and Sub-TLV. the new Prefix Attribute TLV and Sub-TLV.
skipping to change at page 6, line 39 skipping to change at page 6, line 34
Procedures and protocol extensions defined in this document do not Procedures and protocol extensions defined in this document do not
affect the BGP security model. See [RFC6952] for details. affect the BGP security model. See [RFC6952] for details.
6. Acknowledgements 6. Acknowledgements
We would like to thank Peter Psenak (Cisco) for his comments and We would like to thank Peter Psenak (Cisco) for his comments and
support of this work. support of this work.
7. Normative references 7. Normative references
[I-D.ietf-bier-architecture]
Wijnands, I., Rosen, E., Dolganow, A., Przygienda, T., and
S. Aldrin, "Multicast using Bit Index Explicit
Replication", draft-ietf-bier-architecture-08 (work in
progress), September 2017.
[I-D.ietf-bier-isis-extensions]
Ginsberg, L., Przygienda, T., Aldrin, S., and Z. Zhang,
"BIER support via ISIS", draft-ietf-bier-isis-
extensions-11 (work in progress), March 2018.
[I-D.ietf-bier-mpls-encapsulation]
Wijnands, I., Rosen, E., Dolganow, A., Tantsura, J.,
Aldrin, S., and I. Meilik, "Encapsulation for Bit Index
Explicit Replication in MPLS and non-MPLS Networks",
draft-ietf-bier-mpls-encapsulation-12 (work in progress),
October 2017.
[I-D.ietf-bier-ospf-bier-extensions] [I-D.ietf-bier-ospf-bier-extensions]
Psenak, P., Kumar, N., Wijnands, I., Dolganow, A., Psenak, P., Kumar, N., Wijnands, I., Dolganow, A.,
Przygienda, T., Zhang, Z., and S. Aldrin, "OSPFv2 Przygienda, T., Zhang, Z., and S. Aldrin, "OSPFv2
Extensions for BIER", draft-ietf-bier-ospf-bier- Extensions for BIER", draft-ietf-bier-ospf-bier-
extensions-18 (work in progress), June 2018. extensions-18 (work in progress), June 2018.
[I-D.ietf-idr-ls-distribution]
Gredler, H., Medved, J., Previdi, S., Farrel, A., and S.
Ray, "North-Bound Distribution of Link-State and TE
Information using BGP", draft-ietf-idr-ls-distribution-13
(work in progress), October 2015.
[RFC3630] Katz, D., Kompella, K., and D. Yeung, "Traffic Engineering [RFC3630] Katz, D., Kompella, K., and D. Yeung, "Traffic Engineering
(TE) Extensions to OSPF Version 2", RFC 3630, (TE) Extensions to OSPF Version 2", RFC 3630,
DOI 10.17487/RFC3630, September 2003, DOI 10.17487/RFC3630, September 2003,
<https://www.rfc-editor.org/info/rfc3630>. <https://www.rfc-editor.org/info/rfc3630>.
[RFC4915] Psenak, P., Mirtorabi, S., Roy, A., Nguyen, L., and P.
Pillay-Esnault, "Multi-Topology (MT) Routing in OSPF",
RFC 4915, DOI 10.17487/RFC4915, June 2007,
<https://www.rfc-editor.org/info/rfc4915>.
[RFC6952] Jethanandani, M., Patel, K., and L. Zheng, "Analysis of [RFC6952] Jethanandani, M., Patel, K., and L. Zheng, "Analysis of
BGP, LDP, PCEP, and MSDP Issues According to the Keying BGP, LDP, PCEP, and MSDP Issues According to the Keying
and Authentication for Routing Protocols (KARP) Design and Authentication for Routing Protocols (KARP) Design
Guide", RFC 6952, DOI 10.17487/RFC6952, May 2013, Guide", RFC 6952, DOI 10.17487/RFC6952, May 2013,
<https://www.rfc-editor.org/info/rfc6952>. <https://www.rfc-editor.org/info/rfc6952>.
[RFC7752] Gredler, H., Ed., Medved, J., Previdi, S., Farrel, A., and
S. Ray, "North-Bound Distribution of Link-State and
Traffic Engineering (TE) Information Using BGP", RFC 7752,
DOI 10.17487/RFC7752, March 2016,
<https://www.rfc-editor.org/info/rfc7752>.
[RFC8279] Wijnands, IJ., Ed., Rosen, E., Ed., Dolganow, A.,
Przygienda, T., and S. Aldrin, "Multicast Using Bit Index
Explicit Replication (BIER)", RFC 8279,
DOI 10.17487/RFC8279, November 2017,
<https://www.rfc-editor.org/info/rfc8279>.
[RFC8296] Wijnands, IJ., Ed., Rosen, E., Ed., Dolganow, A.,
Tantsura, J., Aldrin, S., and I. Meilik, "Encapsulation
for Bit Index Explicit Replication (BIER) in MPLS and Non-
MPLS Networks", RFC 8296, DOI 10.17487/RFC8296, January
2018, <https://www.rfc-editor.org/info/rfc8296>.
[RFC8401] Ginsberg, L., Ed., Przygienda, T., Aldrin, S., and Z.
Zhang, "Bit Index Explicit Replication (BIER) Support via
IS-IS", RFC 8401, DOI 10.17487/RFC8401, June 2018,
<https://www.rfc-editor.org/info/rfc8401>.
Authors' Addresses Authors' Addresses
Ran Chen Ran Chen
ZTE Corporation ZTE Corporation
No.50 Software Avenue,Yuhuatai District No.50 Software Avenue,Yuhuatai District
Nanjing, Jiangsu Province 210012 Nanjing, Jiangsu Province 210012
China China
Phone: +86 025 88014636 Phone: +86 025 88014636
Email: chen.ran@zte.com.cn Email: chen.ran@zte.com.cn
 End of changes. 24 change blocks. 
76 lines changed or deleted 73 lines changed or added

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