draft-ietf-bier-bgp-ls-bier-ext-04.txt   draft-ietf-bier-bgp-ls-bier-ext-05.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: April 11, 2019 Vengada. Govindan Expires: November 11, 2019 Vengada. Govindan
IJsbrand. Wijnands IJsbrand. Wijnands
Cisco Cisco
October 8, 2018 MAY 10, 2019
BGP Link-State extensions for BIER BGP Link-State extensions for BIER
draft-ietf-bier-bgp-ls-bier-ext-04 draft-ietf-bier-bgp-ls-bier-ext-05
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 April 11, 2019. This Internet-Draft will expire on November 11, 2019.
Copyright Notice Copyright Notice
Copyright (c) 2018 IETF Trust and the persons identified as the Copyright (c) 2019 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
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
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.2. The BIER MPLS Encapsulation Sub-TLV . . . . . . . . . . . 4 3.2. The BIER MPLS Encapsulation Sub-TLV . . . . . . . . . . . 4
3.3. The BIER-TE TLV . . . . . . . . . . . . . . . . . . . . . 5
4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5 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
skipping to change at page 4, line 28 skipping to change at page 4, line 28
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.
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
[RFC8279]. If the BFR-id is zero, it means, the advertising router [RFC8279]. If the BFR-id is zero, it means, the advertising router
is not advertising any BIER-id.In some environment, BFR-id can be is not advertising any BIER-id.In some environment, BFR-id can be
configured by NMS, The BFR-id should be sent to a controller. configured by NMS, The BFR-id should be sent to a controller.
BS Length: A 1 octet field encoding the Bitstring length as per BS Length: A 1 octet field encoding the Bitstring length as per
[[RFC8296]] [RFC8296].
If the MT-ID value is outside of the values specified in [RFC4915], If the MT-ID value is outside of the values specified in [RFC4915],
the BIER Sub-TLV MUST be ignored. the BIER Sub-TLV MUST be ignored.
3.2. The BIER MPLS Encapsulation Sub-TLV 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 [RFC8444]
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
carved out such there are no conflicts. We can avoid all that by carved out such there are no conflicts. We can avoid all that by
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:
skipping to change at page 5, line 22 skipping to change at page 5, line 22
| 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.
Max SI: A 1 octet field encoding the maximum Set Identifier(as Max SI: A 1 octet field encoding the maximum Set Identifier(as
defined in [[RFC8279]]), used in the encapsulation for this BIER defined in [RFC8279]), used in the encapsulation for this BIER
subdomain for this BitString length. subdomain for this BitString length.
Label: A 3 octet field, where the 20 rightmost bits represent the Label: A 3 octet field, where the 20 rightmost bits represent the
first label in the label range. first label in the label range.
BS Length: A 1 octet field encoding the Bitstring length as per BS Length: A 1 octet field encoding the Bitstring length as per
[[RFC8296]] [RFC8296]
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.3. The BIER-TE TLV
This TLV is used to collect BIER-TE information in the "northbound"
direction within the BIER-TE domain.
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.
+-------------------+---------------+-----------------+ +-------------------+---------------+-----------------+
| TLV Code Point | Description | Value defined | | TLV Code Point | Description | Value defined |
+-------------------+---------------+-----------------+ +-------------------+---------------+-----------------+
| 1158( recommend ) | BIER | this document | | 1174( recommend ) | BIER | this document |
+-------------------+---------------+-----------------+ +-------------------+---------------+-----------------+
Table 1: The new Prefix Attribute TLV Table 1: The new Prefix Attribute TLV
+-----------------+-------------------------------+-----------------+ +-----------------+-------------------------------+-----------------+
| Sub-TLV | Description | Value | | Sub-TLV | Description | Value |
| Code Point | | | | Code Point | | |
+-----------------+-------------------------------+-----------------+ +-----------------+-------------------------------+-----------------+
| 1 ( recommend) | BIER MPLS Encapsulation | this document | | 1 ( recommend) | BIER MPLS Encapsulation | this document |
+------------+-------------------------------+----------------------+ +------------+-------------------------------+----------------------+
skipping to change at page 6, line 34 skipping to change at page 6, line 26
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-ospf-bier-extensions]
Psenak, P., Kumar, N., Wijnands, I., Dolganow, A.,
Przygienda, T., Zhang, Z., and S. Aldrin, "OSPFv2
Extensions for BIER", draft-ietf-bier-ospf-bier-
extensions-18 (work in progress), June 2018.
[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. [RFC4915] Psenak, P., Mirtorabi, S., Roy, A., Nguyen, L., and P.
Pillay-Esnault, "Multi-Topology (MT) Routing in OSPF", Pillay-Esnault, "Multi-Topology (MT) Routing in OSPF",
RFC 4915, DOI 10.17487/RFC4915, June 2007, RFC 4915, DOI 10.17487/RFC4915, June 2007,
<https://www.rfc-editor.org/info/rfc4915>. <https://www.rfc-editor.org/info/rfc4915>.
skipping to change at page 7, line 34 skipping to change at page 7, line 22
Tantsura, J., Aldrin, S., and I. Meilik, "Encapsulation Tantsura, J., Aldrin, S., and I. Meilik, "Encapsulation
for Bit Index Explicit Replication (BIER) in MPLS and Non- for Bit Index Explicit Replication (BIER) in MPLS and Non-
MPLS Networks", RFC 8296, DOI 10.17487/RFC8296, January MPLS Networks", RFC 8296, DOI 10.17487/RFC8296, January
2018, <https://www.rfc-editor.org/info/rfc8296>. 2018, <https://www.rfc-editor.org/info/rfc8296>.
[RFC8401] Ginsberg, L., Ed., Przygienda, T., Aldrin, S., and Z. [RFC8401] Ginsberg, L., Ed., Przygienda, T., Aldrin, S., and Z.
Zhang, "Bit Index Explicit Replication (BIER) Support via Zhang, "Bit Index Explicit Replication (BIER) Support via
IS-IS", RFC 8401, DOI 10.17487/RFC8401, June 2018, IS-IS", RFC 8401, DOI 10.17487/RFC8401, June 2018,
<https://www.rfc-editor.org/info/rfc8401>. <https://www.rfc-editor.org/info/rfc8401>.
[RFC8444] Psenak, P., Ed., Kumar, N., Wijnands, IJ., Dolganow, A.,
Przygienda, T., Zhang, J., and S. Aldrin, "OSPFv2
Extensions for Bit Index Explicit Replication (BIER)",
RFC 8444, DOI 10.17487/RFC8444, November 2018,
<https://www.rfc-editor.org/info/rfc8444>.
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. 14 change blocks. 
24 lines changed or deleted 16 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/