draft-ietf-bier-ospf-bier-extensions-05.txt   draft-ietf-bier-ospf-bier-extensions-06.txt 
OSPF P. Psenak, Ed. OSPF P. Psenak, Ed.
Internet-Draft N. Kumar Internet-Draft N. Kumar
Intended status: Standards Track IJ. Wijnands Intended status: Standards Track IJ. Wijnands
Expires: September 14, 2017 Cisco Expires: December 22, 2017 Cisco
A. Dolganow A. Dolganow
Nokia Nokia
T. Przygienda T. Przygienda
J. Zhang J. Zhang
Juniper Networks, Inc. Juniper Networks, Inc.
S. Aldrin S. Aldrin
Google, Inc. Google, Inc.
March 13, 2017 June 20, 2017
OSPF Extensions for BIER OSPF Extensions for BIER
draft-ietf-bier-ospf-bier-extensions-05.txt draft-ietf-bier-ospf-bier-extensions-06.txt
Abstract Abstract
Bit Index Explicit Replication (BIER) is an architecture that Bit Index Explicit Replication (BIER) is an architecture that
provides multicast forwarding through a "BIER domain" without provides multicast forwarding through a "BIER domain" without
requiring intermediate routers to maintain multicast related per-flow requiring intermediate routers to maintain multicast related per-flow
state. Neither does BIER require an explicit tree-building protocol state. Neither does BIER require an explicit tree-building protocol
for its operation. A multicast data packet enters a BIER domain at a for its operation. A multicast data packet enters a BIER domain at a
"Bit-Forwarding Ingress Router" (BFIR), and leaves the BIER domain at "Bit-Forwarding Ingress Router" (BFIR), and leaves the BIER domain at
one or more "Bit-Forwarding Egress Routers" (BFERs). The BFIR router one or more "Bit-Forwarding Egress Routers" (BFERs). The BFIR router
adds a BIER header to the packet. Such header contains a bit-string adds a BIER header to the packet. Such header contains a bit-string
in which each bit represents exactly one BFER to forward the packet in which each bit represents exactly one BFER to forward the packet
to. The set of BFERs to which the multicast packet needs to be to. The set of BFERs to which the multicast packet needs to be
forwarded is expressed by the according set of bits switched on in forwarded is expressed by the according set of bits set in BIER
BIER packet header. packet header.
This document describes the OSPF protocol extension required for BIER This document describes the OSPF protocol extension required for BIER
with MPLS encapsulation. with MPLS encapsulation.
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
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 September 14, 2017. This Internet-Draft will expire on December 22, 2017.
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
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. Flooding of the BIER Information in OSPF . . . . . . . . . . 3 2. Flooding of the BIER Information in OSPF . . . . . . . . . . 3
2.1. The BIER Sub-TLV . . . . . . . . . . . . . . . . . . . . 3 2.1. BIER Sub-TLV . . . . . . . . . . . . . . . . . . . . . . 3
2.2. The BIER MPLS Encapsulation Sub-TLV . . . . . . . . . . . 4 2.2. BIER MPLS Encapsulation Sub-TLV . . . . . . . . . . . . . 4
2.3. Optional BIER Tree Type Sub-TLV . . . . . . . . . . . . . 5 2.3. Optional BIER Tree Type Sub-TLV . . . . . . . . . . . . . 5
2.4. Flooding scope of BIER Information . . . . . . . . . . . 6 2.4. Flooding scope of BIER Information . . . . . . . . . . . 6
3. Security Considerations . . . . . . . . . . . . . . . . . . . 7 3. Security Considerations . . . . . . . . . . . . . . . . . . . 7
4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7
5. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 7 5. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 7
6. Normative References . . . . . . . . . . . . . . . . . . . . 7 6. Normative References . . . . . . . . . . . . . . . . . . . . 7
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 8 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 8
1. Introduction 1. Introduction
skipping to change at page 3, line 9 skipping to change at page 3, line 9
The BFIR router adds a BIER header to the packet. The BIER header The BFIR router adds a BIER header to the packet. The BIER header
contains a bit-string in which each bit represents exactly one BFER contains a bit-string in which each bit represents exactly one BFER
to forward the packet to. The set of BFERs to which the multicast to forward the packet to. The set of BFERs to which the multicast
packet needs to be forwarded is expressed by setting the bits that packet needs to be forwarded is expressed by setting the bits that
correspond to those routers in the BIER header. correspond to those routers in the BIER header.
BIER architecture requires routers participating in BIER to exchange BIER architecture requires routers participating in BIER to exchange
BIER related information within a given domain. BIER architecture BIER related information within a given domain. BIER architecture
permits link-state routing protocols to perform distribution of such permits link-state routing protocols to perform distribution of such
information. This document describes extensions to OSPF necessary to information. This document describes extensions to OSPF necessary to
carry BIER specific information in the case where BIER uses MPLS advertise BIER specific information in the case where BIER uses MPLS
encapsulation as described in [I-D.wijnands-mpls-bier-encapsulation]. encapsulation as described in [I-D.ietf-bier-mpls-encapsulation].
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].
2. Flooding of the BIER Information in OSPF 2. Flooding of the BIER Information in OSPF
All BIER specific information that a BFR needs to advertise to other All BIER specific information that a Bit-Forwarding Router (BFR)
BFRs is associated with a BFR-Prefix. BFR prefix is a unique (within needs to advertise to other BFRs is associated with a BFR-Prefix. A
a given BIER domain), routable IP address that is assigned to each BFR prefix is a unique (within a given BIER domain) routable IP
BFR as described in more detail in section 2 of address that is assigned to each BFR as described in more detail in
[I-D.wijnands-bier-architecture]. section 2 of [I-D.ietf-bier-architecture].
Given that BIER information must be associated with a BFR prefix, the Given that BIER information must be associated with a BFR prefix, the
OSPF Extended Prefix Opaque LSA [I-D.ietf-ospf-prefix-link-attr] has OSPF Extended Prefix Opaque LSA [RFC7684] has been chosen for
been chosen to flood it. advertisement.
2.1. The BIER Sub-TLV 2.1. BIER Sub-TLV
A new Sub-TLV of the Extended Prefix TLV (defined in A Sub-TLV of the Extended Prefix TLV (defined in [RFC7684]) is
[I-D.ietf-ospf-prefix-link-attr]) is defined for distributing BIER defined for distributing BIER information. The Sub-TLV is called the
information. The new Sub-TLV is called BIER Sub-TLV. Multiple BIER BIER Sub-TLV. Multiple BIER Sub-TLVs may be included in the Extended
Sub-TLVs may be included in the Extended Prefix TLV. Prefix TLV.
BIER Sub-TLV has the following format: The BIER Sub-TLV has the following format:
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 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Sub-domain-ID | MT-ID | BFR-id | | Sub-domain-ID | MT-ID | BFR-id |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Sub-TLVs (variable) | | Sub-TLVs (variable) |
+- -+ +- -+
| | | |
Type: TBD Type: TBD1
Length: variable Length: variable
Sub-domain-ID: Unique value identifying the BIER sub-domain within Sub-domain-ID: Unique value identifying the BIER sub-domain within
the BIER domain, as described in section 1 of the BIER domain, as described in section 1 of
[I-D.wijnands-bier-architecture]. [I-D.ietf-bier-architecture].
MT-ID: Multi-Topology ID (as defined in [RFC4915]) that identifies MT-ID: Multi-Topology ID (as defined in [RFC4915]) that identifies
the topology that is associated with the BIER sub-domain. the topology that is associated with the BIER sub-domain.
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
section 2 [I-D.wijnands-bier-architecture]. If the BFR is not section 2 of [I-D.ietf-bier-architecture]. If the BFR is not
locally configured with a valid BFR-id, the value of this field is locally configured with a valid BFR-id, the value of this field is
set to invalid BFR-id per [I-D.wijnands-bier-architecture]. set to invalid BFR-id per [I-D.ietf-bier-architecture].
Each BFR sub-domain MUST be associated with one and only one OSPF Each BFR sub-domain MUST be associated with one and only one OSPF
topology that is identified by the MT-ID. If the association between topology that is identified by the MT-ID. If the association between
BIER sub-domain and OSPF topology advertised in the BIER sub-TLV by BIER sub-domain and OSPF topology advertised in the BIER sub-TLV by
other BFRs is in conflict with the association locally configured on other BFRs is in conflict with the association locally configured on
the receiving router, whole BIER sub-TLV of the advertising routers the receiving router, the BIER Sub-TLV MUST be ignored.
MUST be ignored.
If a BFR advertises the same Sub-domain-ID in multiple BIER sub-TLVs, If a BFR advertises the same Sub-domain-ID in multiple BIER sub-TLVs,
the BRF MUST be treated as if it did not advertise a BIER sub-TLV for the BRF MUST be treated as if it did not advertise a BIER sub-TLV for
such sub-domain. such sub-domain.
All BFRs MUST detect advertisement of duplicate valid BFR-IDs for a All BFRs MUST detect advertisement of duplicate valid BFR-IDs for a
given MT-ID and Sub-domain-ID. When such duplication is detected all given MT-ID and Sub-domain-ID. When such duplication is detected all
BFRs advertising duplicates MUST be treated as if they did not BFRs advertising duplicates MUST be treated as if they did not
advertise a valid BFR-id. advertise a valid BFR-id.
2.2. The BIER MPLS Encapsulation Sub-TLV 2.2. BIER MPLS Encapsulation Sub-TLV
BIER MPLS Encapsulation Sub-TLV is a sub-TLV of the BIER Sub-TLV. The BIER MPLS Encapsulation Sub-TLV is a Sub-TLV of the BIER Sub-TLV.
BIER MPLS Encapsulation Sub-TLV is used in order to advertise MPLS The BIER MPLS Encapsulation Sub-TLV is used in order to advertise
specific information used for BIER. It MAY appear multiple times in MPLS specific information used for BIER. It MAY appear multiple
the BIER Sub-TLV. times in the BIER Sub-TLV.
BIER MPLS Encapsulation Sub-TLV has the following format: The BIER MPLS Encapsulation Sub-TLV has the following format:
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 | |Lbl Range Size | Label Range Base |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| BS Length | Reserved | | BS Length | Reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Type: TBD Type: TBD2
Length: 4 bytes Length: 4 octets
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 then 0, otherwise the the label range. It MUST be greater then 0, otherwise the
advertising router MUST be treated as if it did not advertise a advertising router MUST be treated as if it did not advertise a
BIER sub-TLV. BIER sub-TLV.
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.
BS Length: A 1 octet field encoding the supported BitString length Bit String Length: A 1 octet field encoding the supported
associated with this BFR-prefix. The values allowed in this field BitString length associated with this BFR-prefix. The values
are specified in section 3 of allowed in this field are specified in section 2 of
[I-D.wijnands-mpls-bier-encapsulation]. [I-D.ietf-bier-mpls-encapsulation].
The "label range" is the set of labels beginning with the label The "label range" is the set of labels beginning with the label
range base and ending with (label range base)+(label range size)- range base and ending with ((label range base)+(label range size)-
1. A unique label range is allocated for each BitStream length 1). A unique label range is allocated for each BitStream length
and Sub-domain-ID. These labels are used for BIER forwarding as and Sub-domain-ID. These labels are used for BIER forwarding as
described in [I-D.wijnands-bier-architecture] and described in [I-D.ietf-bier-architecture] and
[I-D.wijnands-mpls-bier-encapsulation]. [I-D.ietf-bier-mpls-encapsulation].
The size of the label range is determined by the number of Set The size of the label range is determined by the number of Set
Identifiers (SI) (section 2 of [I-D.wijnands-bier-architecture]) Identifiers (SI) (section 1 of [I-D.ietf-bier-architecture]) that
that are used in the network. Each SI maps to a single label in are used in the network. Each SI maps to a single label in the
the label range. The first label is for SI=0, the second label is label range. The first label is for SI=0, the second label is for
for SI=1, etc. SI=1, etc.
If same BS length is repeated in multiple BIER MPLS Encapsulation If same BS length is repeated in multiple BIER MPLS Encapsulation
Sub-TLV inside the same BIER Sub-TLV, the advertising router MUST be Sub-TLV inside the same BIER Sub-TLV, the BIER sub-TLV MUST be
treated as if it did not advertise a BIER sub-TLV. ignored.
Label ranges within all BIER MPLS Encapsulation Sub-TLV inside the Label ranges within all BIER MPLS Encapsulation Sub-TLV inside the
same BIER Sub-TLV MUST NOT overlap. If the overlap is detected, the same BIER Sub-TLV MUST NOT overlap. If the overlap is detected, the
advertising router MUST be treated as if it did not advertise a BIER advertising router MUST be treated as if it did not advertise a BIER
sub-TLV. sub-TLV.
All advertised labels MUST be valid, otherwise the advertising router All advertised labels MUST be valid, otherwise the BIER sub-TLV MUST
MUST be treated as if it did not advertise a BIER sub-TLV. be ignored.
2.3. Optional BIER Tree Type Sub-TLV 2.3. Optional BIER Tree Type Sub-TLV
This Sub-TLV carries the information associated with the supported This Sub-TLV carries the information associated with the supported
BIER tree type for a subdomain. This Sub-TLV is optional and its BIER tree type for a sub-domain. This Sub-TLV is optional and its
absence has the same semantics as its presence with Tree Type value 0 absence has the same semantics as its presence with Tree Type value 0
(SPF). When Tree Type 0 is used it is recommended that this Sub-TLV (SPF). When Tree Type 0 is used, it is RECOMMENDED that this Sub-TLV
is omitted in order to reduce the space consumed in the parent TLV. is omitted in order to reduce the space consumed in the parent TLV.
This Sub-TLV MAY occur no more than once in a BIER sub-TLV. If This Sub-TLV MAY occur no more than once in a BIER sub-TLV. If
multiple occurences of this Sub-TLV are present in a single BIER Sub- multiple occurences of this Sub-TLV are present in a single BIER Sub-
TLV the advertising router MUST be treated as if it did not advertise TLV, the BIER sub-TLV MUST be ignored.
a BIER sub-TLV.
If the tree type (implied or explicitly advertised) does not match If the tree type (implied or explicitly advertised) does not match
the locally configured tree type associated with the matching the locally configured tree type associated with the matching sub-
subdomain the advertising router MUST be treated as if it did not domain, the BIER sub-TLV MUST be ignored.
advertise a BIER sub-TLV.
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 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tree Type | | Tree Type |
+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+
Type: value of 1 indicating BIER Tree Type. Type: TBD3.
Length: 1 octet. Length: 1 octet.
Tree Type: 1 octet Tree Type: 1 octet
2.4. Flooding scope of BIER Information 2.4. Flooding scope of BIER Information
Flooding scope of the OSPF Extended Prefix Opaque LSA The flooding scope of the OSPF Extended Prefix Opaque LSA [RFC7684]
[I-D.ietf-ospf-prefix-link-attr] that is used for advertising BIER that is used for advertising the BIER Sub-TLV is set to area-local.
Sub TLV is set to area. To allow BIER deployment in a multi-area To allow BIER deployment in a multi-area environment, OSPF must
environment, OSPF must propagate BIER information between areas. The propagate BIER information between areas. The following procedure is
following procedure is used in order to propagate BIER related used in order to propagate BIER related information between areas:
information between areas:
When an OSPF ABR advertises a Type-3 Summary LSA from an intra- When an OSPF Area Border Router (ABR) advertises a Type-3 Summary
area or inter-area prefix to all its connected areas, it will also LSA from an intra-area or inter-area prefix to all its attached
originate an Extended Prefix Opaque LSA, as described in areas, it will also originate an Extended Prefix Opaque LSA, as
[I-D.ietf-ospf-prefix-link-attr]. The flooding scope of the described in [RFC7684]. The flooding scope of the Extended Prefix
Extended Prefix Opaque LSA type will be set to area-scope. The Opaque LSA type will be set to area-local. The route-type in the
route-type in the OSPF Extended Prefix TLV is set to inter-area. OSPF Extended Prefix TLV is set to inter-area. When determining
When determining whether a BIER Sub-TLV should be included in this whether a BIER Sub-TLV should be included in this LSA, an OSPF ABR
LSA ABR will: will:
- look at its best path to the prefix in the source area and - Examine its best path to the prefix in the source area and
find the advertising router associated with the best path to find the advertising router associated with the best path to
that prefix. that prefix.
- determine if such advertising router advertised a BIER Sub- - Determine if such advertising router advertised a BIER Sub-
TLV for the prefix. If yes, ABR will copy the information from TLV for the prefix. If yes, the ABR will copy the information
such BIER MPLS Sub-TLV when advertising BIER MPLS Sub-TLV to from such BIER MPLS Sub-TLV when advertising BIER MPLS Sub-TLV
each connected area. to each attached area.
3. Security Considerations 3. Security Considerations
Implementations must assure that malformed TLV and Sub-TLV Implementations must assure that malformed TLV and Sub-TLV
permutations do not result in errors which cause hard OSPF failures. permutations do not result in errors which cause hard OSPF failures.
4. IANA Considerations 4. IANA Considerations
The document requests three new allocations from the OSPF Extended The document requests three new allocations from the OSPF Extended
Prefix sub-TLV registry as defined in Prefix sub-TLV registry as defined in [RFC7684].
[I-D.ietf-ospf-prefix-link-attr].
BIER Sub-TLV: TBD BIER Sub-TLV: TBD1
BIER MPLS Encapsulation Sub-TLV: TBD BIER MPLS Encapsulation Sub-TLV: TBD2
BIER Tree Type Sub-TLV: TBD BIER Tree Type Sub-TLV: TBD3
5. Acknowledgments 5. Acknowledgments
The authors would like to thank Rajiv Asati, Christian Martin, Greg The authors would like to thank Rajiv Asati, Christian Martin, Greg
Shepherd and Eric Rosen for their contribution. Shepherd and Eric Rosen for their contribution.
6. Normative References 6. Normative References
[I-D.ietf-ospf-prefix-link-attr] [I-D.ietf-bier-architecture]
Psenak, P., Gredler, H., rjs@rob.sh, r., Henderickx, W., Wijnands, I., Rosen, E., Dolganow, A., Przygienda, T., and
Tantsura, J., and A. Lindem, "OSPFv2 Prefix/Link Attribute S. Aldrin, "Multicast using Bit Index Explicit
Advertisement", draft-ietf-ospf-prefix-link-attr-13 (work Replication", draft-ietf-bier-architecture-06 (work in
in progress), August 2015. progress), April 2017.
[I-D.wijnands-bier-architecture]
Wijnands, I., Rosen, E., Dolganow, A., and T. Przygienda,
"Multicast using Bit Index Explicit Replication", draft-
wijnands-bier-architecture-00 (work in progress),
September 2014.
[I-D.wijnands-mpls-bier-encapsulation] [I-D.ietf-bier-mpls-encapsulation]
Wijnands, I., Rosen, E., Dolganow, A., and J. Tantsura, Wijnands, I., Rosen, E., Dolganow, A., Tantsura, J.,
"Encapsulation for Bit Index Explicit Replication in MPLS Aldrin, S., and I. Meilik, "Encapsulation for Bit Index
Networks", draft-wijnands-mpls-bier-encapsulation-00 (work Explicit Replication in MPLS and non-MPLS Networks",
in progress), September 2014. draft-ietf-bier-mpls-encapsulation-07 (work in progress),
June 2017.
[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,
<http://www.rfc-editor.org/info/rfc2119>. <http://www.rfc-editor.org/info/rfc2119>.
[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,
<http://www.rfc-editor.org/info/rfc4915>. <http://www.rfc-editor.org/info/rfc4915>.
[RFC7684] Psenak, P., Gredler, H., Shakir, R., Henderickx, W.,
Tantsura, J., and A. Lindem, "OSPFv2 Prefix/Link Attribute
Advertisement", RFC 7684, DOI 10.17487/RFC7684, November
2015, <http://www.rfc-editor.org/info/rfc7684>.
Authors' Addresses Authors' Addresses
Peter Psenak (editor) Peter Psenak (editor)
Cisco Cisco
Apollo Business Center Apollo Business Center
Mlynske nivy 43 Mlynske nivy 43
Bratislava 821 09 Bratislava 821 09
Slovakia Slovakia
Email: ppsenak@cisco.com Email: ppsenak@cisco.com
 End of changes. 44 change blocks. 
104 lines changed or deleted 99 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/