BIER IPv6 Requirements
draft-mcbride-bier-ipv6-requirements-01

Document Type Replaced Internet-Draft (individual)
Last updated 2019-05-09
Replaces draft-mcbride-bier-ipv6-problem-statement
Replaced by draft-ietf-bier-ipv6-requirements
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Replaced by draft-ietf-bier-ipv6-requirements
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-mcbride-bier-ipv6-requirements-01.txt

Abstract

The BIER WG has a charter item to work on mechanisms which use BIER natively in IPv6. This document is intended to help the WG with this effort by specifying requirements for transporting packets, with Bit Index Explicit Replication (BIER) headers, in an IPv6 environment. There will be a need to send IPv6 payloads, to multiple IPv6 destinations, using BIER. There have been several proposed solutions in this area. But there hasn't been a document which describes the problem and lists the requirements. The goal of this document is to describe the BIER IPv6 requirements and summarize the pro's and con's of the proposed solutions.

Authors

Mike McBride (michael.mcbride@huawei.com)
Jingrong Xie (xiejingrong@huawei.com)
Senthil Dhanaraj (senthil.dhanaraj@huawei.com)
Rajiv Asati (rajiva@cisco.com)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)