draft-ietf-bier-ospf-bier-extensions-11.txt   draft-ietf-bier-ospf-bier-extensions-12.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: August 16, 2018 Cisco Expires: August 18, 2018 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.
February 12, 2018 February 14, 2018
OSPF Extensions for BIER OSPF Extensions for BIER
draft-ietf-bier-ospf-bier-extensions-11.txt draft-ietf-bier-ospf-bier-extensions-12.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
skipping to change at page 2, line 7 skipping to change at page 2, line 7
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 August 16, 2018. This Internet-Draft will expire on August 18, 2018.
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 5, line 46 skipping to change at page 5, line 46
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 1 of [RFC8279]) that are used in the Identifiers (SI) (section 1 of [RFC8279]) that are used in the
network. Each SI maps to a single label in the label range. The network. Each SI maps to a single label in the label range. The
first label is for SI=0, the second label is for SI=1, etc. first label is for SI=0, the second label is for 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 BIER sub-TLV MUST be Sub-TLV inside the same BIER Sub-TLV, the BIER sub-TLV MUST be
ignored. ignored.
Label ranges within all BIER MPLS Encapsulation Sub-TLV inside the Label ranges within all BIER MPLS Encapsulation Sub-TLVs advertised
same BIER Sub-TLV MUST NOT overlap. If the overlap is detected, the by the same BFR 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 any
sub-TLV. BIER sub-TLVs.
All advertised labels MUST be valid, otherwise the BIER sub-TLV MUST All advertised labels MUST be valid, otherwise the BIER sub-TLV MUST
be ignored. be ignored.
2.3. Flooding scope of BIER Information 2.3. Flooding scope of BIER Information
The flooding scope of the OSPF Extended Prefix Opaque LSA [RFC7684] The flooding scope of the OSPF Extended Prefix Opaque LSA [RFC7684]
that is used for advertising the BIER Sub-TLV is set to area-local. that is used for advertising the BIER Sub-TLV is set to area-local.
To allow BIER deployment in a multi-area environment, OSPF must To allow BIER deployment in a multi-area environment, OSPF must
propagate BIER information between areas. propagate BIER information between areas.
 End of changes. 5 change blocks. 
8 lines changed or deleted 8 lines changed or added

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