BIER IPv6 Encapsulation (BIERv6) Support via IS-IS
draft-xie-bier-ipv6-isis-extension-00
|
| Document |
Type |
|
Active Internet-Draft (individual)
|
|
Last updated |
|
2019-07-01
|
|
Stream |
|
(None)
|
|
Intended RFC status |
|
(None)
|
|
Formats |
|
plain text
xml
pdf
htmlized
bibtex
|
| Stream |
Stream state |
|
(No stream defined) |
|
Consensus Boilerplate |
|
Unknown
|
|
RFC Editor Note |
|
(None)
|
| IESG |
IESG state |
|
I-D Exists
|
|
Telechat date |
|
|
|
Responsible AD |
|
(None)
|
|
Send notices to |
|
(None)
|
Network Working Group J. Xie
Internet-Draft Huawei Technologies
Intended status: Standards Track A. Wang
Expires: January 2, 2020 China Telecom
G. Yan
S. Dhanaraj
Huawei Technologies
July 1, 2019
BIER IPv6 Encapsulation (BIERv6) Support via IS-IS
draft-xie-bier-ipv6-isis-extension-00
Abstract
This document defines IS-IS extensions to support multicast
forwarding using the Bit Index Explicit Replication (BIER) with IPv6
encapsulation (BIERv6).
Requirements Language
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [RFC2119] and
[RFC8174].
Status of This Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
This Internet-Draft will expire on January 2, 2020.
Copyright Notice
Copyright (c) 2019 IETF Trust and the persons identified as the
document authors. All rights reserved.
Xie, et al. Expires January 2, 2020 [Page 1]
Internet-Draft BIERv6 Via IS-IS July 2019
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. Specification . . . . . . . . . . . . . . . . . . . . . . . . 3
3.1. Function sub-TLV for BIERv6 . . . . . . . . . . . . . . . 3
3.2. Encapsulation sub-sub-TLV for BIERv6 . . . . . . . . . . 4
4. Security Considerations . . . . . . . . . . . . . . . . . . . 4
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 4
5.1. Function sub-TLV Type Code . . . . . . . . . . . . . . . 4
5.2. Encapsulation sub-sub-TLV Type Code . . . . . . . . . . . 5
6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 5
7. References . . . . . . . . . . . . . . . . . . . . . . . . . 5
7.1. Normative References . . . . . . . . . . . . . . . . . . 5
7.2. Informative References . . . . . . . . . . . . . . . . . 6
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 6
1. Introduction
This document defines IS-IS extensions to support multicast
forwarding using the Bit Index Explicit Replication (BIER) with IPv6
encapsulation (BIERv6).
Familiarity with the concept of "BIER specific" IPv6 address
introduced in [I-D.xie-bier-ipv6-encapsulation] is necessary to
understand the extensions specified in this document.
The [I-D.ietf-spring-srv6-network-programming] describes how a
function can be bound to a special "IPv6 Address" within a special
"IPv6 Address Block". The function bound to a special "IPv6 Address"
can be used to indicate a special forwarding process in data-plane.
The BIER IPv6 encapsulation [I-D.xie-bier-ipv6-encapsulation] uses a
"BIER specific" IPv6 unicast address configured locally on a BIER
Forwarding Router (BFR) to indicate a "BIER specific handling" in
Forwarding Information Base (FIB). This BIER specific IPv6 address
is also required to use as the BFR prefix as defined in [RFC8279].
Xie, et al. Expires January 2, 2020 [Page 2]
Internet-Draft BIERv6 Via IS-IS July 2019
The indication of BFR prefix is a BIER Sub-TLV within the extended IP
reachability TLV as specified by in [RFC8401].
Show full document text