BIER IPv6 Requirements
draft-ietf-bier-ipv6-requirements-09
Network Working Group M. McBride
Internet-Draft Futurewei
Intended status: Informational J. Xie
Expires: April 1, 2021 X. Geng
S. Dhanaraj
Huawei
R. Asati
Cisco
Y. Zhu
China Telecom
G. Mishra
Verizon Inc.
Z. Zhang
Juniper
September 28, 2020
BIER IPv6 Requirements
draft-ietf-bier-ipv6-requirements-09
Abstract
There have been several proposed solutions with BIER being used in
IPv6. But there hasn't been a document which describes the problem
and lists the requirements. The goal of this document is to describe
the general BIER IPv6 encapsulation problem and detail solution
requirements, thereby assisting the working group in the development
of acceptable solutions.
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 April 1, 2021.
McBride, et al. Expires April 1, 2021 [Page 1]
Internet-Draft BIER IPv6 Requirements September 2020
Copyright Notice
Copyright (c) 2020 IETF Trust and the persons identified as the
document authors. All rights reserved.
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
1.1. Requirements Language . . . . . . . . . . . . . . . . . . 3
1.2. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3
2. Problem Statement . . . . . . . . . . . . . . . . . . . . . . 3
3. Requirements . . . . . . . . . . . . . . . . . . . . . . . . 4
3.1. Mandatory Requirements . . . . . . . . . . . . . . . . . 4
3.1.1. Support various L2 link types . . . . . . . . . . . . 4
3.1.2. Support BIER architecture . . . . . . . . . . . . . . 4
3.1.3. Support deployment with Non-BFR routers . . . . . . . 4
3.1.4. Support OAM . . . . . . . . . . . . . . . . . . . . . 5
3.2. Optional Requirements . . . . . . . . . . . . . . . . . . 5
3.2.1. Support Fragmentation . . . . . . . . . . . . . . . . 5
3.2.2. Support IPSEC ESP . . . . . . . . . . . . . . . . . . 5
4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5
5. Security Considerations . . . . . . . . . . . . . . . . . . . 6
6. Acknowledgement . . . . . . . . . . . . . . . . . . . . . . . 6
7. Normative References . . . . . . . . . . . . . . . . . . . . 6
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 7
1. Introduction
Bit Index Explicit Replication (BIER) [RFC8279] is an architecture
that provides optimal multicast forwarding, without requiring
intermediate routers to maintain per-flow state, through the use of a
multicast-specific BIER header. [RFC8296] defines two types of BIER
encapsulation: one is BIER MPLS encapsulation for MPLS environments,
the other is non-MPLS BIER encapsulation to run without MPLS. This
document describes non-MPLS BIER encapsulation in IPv6 environments.
Show full document text