draft-ietf-bier-bgp-ls-bier-ext-00.txt   draft-ietf-bier-bgp-ls-bier-ext-01.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: July 14, 2017 Vengada. Govindan Expires: January 31, 2018 Vengada. Govindan
IJsbrand. Wijnands IJsbrand. Wijnands
Cisco Cisco
January 10, 2017 July 30, 2017
BGP Link-State extensions for BIER BGP Link-State extensions for BIER
draft-ietf-bier-bgp-ls-bier-ext-00 draft-ietf-bier-bgp-ls-bier-ext-01
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 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 July 14, 2017. This Internet-Draft will expire on January 31, 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 3, line 39 skipping to change at page 3, line 39
is defined for distributing BIER information. The new TLV is called is defined for distributing BIER information. The new TLV is called
the BIER TLV. The BIER TLVs may appear multiple times. the BIER TLV. 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 | | reserved | subdomain-id | MT-ID | BSL |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| BFR-id | reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| BFR-id | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| Sub-TLVs (variable) | | Sub-TLVs (variable) |
+- -+ +- -+
| | | |
Figure 1 Figure 1
Type: TBD. Type:as indicated in IANA Considerations section.
Length: 2 octet. Length: 2 octet.
Reserved: MUST be 0 on transmission, ignored on reception. May be
used in future versions.
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 (BS Len): A 1 octet field encoding the supported
BitString length associated with this BFR-prefix.This field are BitString length associated with this BFR-prefix.This field are
specified in section 3 of [I-D.ietf-bier-architecture].Given that the specified in section 3 of [I-D.ietf-bier-mpls-encapsulation].Given
bier router can support BSL values set, this field encoding the BSL that the bier router can support BSL values set, this field encoding
values set that BIER routers supported. 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 [I-D.ietf-bier-architecture]. If the BFR-id is zero, it means, the
advertising router is not advertising any BIER-id. advertising router 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.
If multiple BIER Sub-TLVs are present, all having the same BS Length If multiple BIER Sub-TLVs are present, all having the same BS Length
and Subdomain-id values, first one MUST be used and subsequent ones and Subdomain-id values, first one MUST be used and subsequent ones
MUST be ignored. MUST be ignored.
3.1.1. The BIER MPLS Encapsulation Sub-TLV 3.1.1. 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
skipping to change at page 4, line 47 skipping to change at page 5, line 5
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length | | Type | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|Lbl Range Size | Label Range Base | |Lbl Range Size | Label Range Base |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| BS Length | Reserved | | BS Length | Reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 2 Figure 2
Type: TBD. 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 Label Range Size: A 1 octet field encoding the label range size of
the label range. It MUST be greater than 0, otherwise the TLV MUST the label range. It MUST be greater than 0, otherwise the TLV MUST
be ignored. be ignored.
Label Range Base: A 3 octet field, where the 20 rightmost bits Label Range Base: A 3 octet field, where the 20 rightmost bits
represent the first label in the label range. represent the first label in the label range.
skipping to change at page 6, line 29 skipping to change at page 6, line 37
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] [I-D.ietf-bier-architecture]
Wijnands, I., Rosen, E., Dolganow, A., Przygienda, T., and Wijnands, I., Rosen, E., Dolganow, A., Przygienda, T., and
S. Aldrin, "Multicast using Bit Index Explicit S. Aldrin, "Multicast using Bit Index Explicit
Replication", draft-ietf-bier-architecture-05 (work in Replication", draft-ietf-bier-architecture-07 (work in
progress), October 2016. progress), June 2017.
[I-D.ietf-bier-isis-extensions] [I-D.ietf-bier-isis-extensions]
Ginsberg, L., Przygienda, T., Aldrin, S., and Z. Zhang, Ginsberg, L., Przygienda, T., Aldrin, S., and Z. Zhang,
"BIER support via ISIS", draft-ietf-bier-isis- "BIER support via ISIS", draft-ietf-bier-isis-
extensions-03 (work in progress), September 2016. extensions-04 (work in progress), March 2017.
[I-D.ietf-bier-mpls-encapsulation] [I-D.ietf-bier-mpls-encapsulation]
Wijnands, I., Rosen, E., Dolganow, A., Tantsura, J., Wijnands, I., Rosen, E., Dolganow, A., Tantsura, J.,
Aldrin, S., and I. Meilik, "Encapsulation for Bit Index Aldrin, S., and I. Meilik, "Encapsulation for Bit Index
Explicit Replication in MPLS and non-MPLS Networks", Explicit Replication in MPLS and non-MPLS Networks",
draft-ietf-bier-mpls-encapsulation-06 (work in progress), draft-ietf-bier-mpls-encapsulation-07 (work in progress),
December 2016. June 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, "OSPF Extensions Przygienda, T., Zhang, Z., and S. Aldrin, "OSPF Extensions
for BIER", draft-ietf-bier-ospf-bier-extensions-04 (work for BIER", draft-ietf-bier-ospf-bier-extensions-07 (work
in progress), September 2016. in progress), July 2017.
[I-D.ietf-idr-ls-distribution] [I-D.ietf-idr-ls-distribution]
Gredler, H., Medved, J., Previdi, S., Farrel, A., and S. Gredler, H., Medved, J., Previdi, S., Farrel, A., and S.
Ray, "North-Bound Distribution of Link-State and TE Ray, "North-Bound Distribution of Link-State and TE
Information using BGP", draft-ietf-idr-ls-distribution-13 Information using BGP", draft-ietf-idr-ls-distribution-13
(work in progress), October 2015. (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,
 End of changes. 15 change blocks. 
20 lines changed or deleted 25 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/