One document matched: draft-xu-bier-encapsulation-03.xml
<?xml version="1.0" encoding="US-ASCII"?>
<!-- This template is for creating an Internet Draft using xml2rfc,
which is available here: http://xml.resource.org. -->
<!DOCTYPE rfc SYSTEM "rfc2629.dtd" [
<!-- One method to get references from the online citation libraries.
There has to be one entity for each item to be referenced.
An alternate method (rfc include) is described in the references. -->
<!ENTITY RFC2119 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.2119.xml">
<!ENTITY RFC2629 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.2629.xml">
<!ENTITY RFC3552 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.3552.xml">
<!ENTITY I-D.narten-iana-considerations-rfc2434bis SYSTEM "http://xml.resource.org/public/rfc/bibxml3/reference.I-D.narten-iana-considerations-rfc2434bis.xml">
]>
<?xml-stylesheet type='text/xsl' href='rfc2629.xslt' ?>
<!-- used by XSLT processors -->
<!-- For a complete list and description of processing instructions (PIs),
please see http://xml.resource.org/authoring/README.html. -->
<!-- Below are generally applicable Processing Instructions (PIs) that most I-Ds might want to use.
(Here they are set differently than their defaults in xml2rfc v1.32) -->
<?rfc strict="yes" ?>
<!-- give errors regarding ID-nits and DTD validation -->
<!-- control the table of contents (ToC) -->
<?rfc toc="yes"?>
<!-- generate a ToC -->
<?rfc tocdepth="4"?>
<!-- the number of levels of subsections in ToC. default: 3 -->
<!-- control references -->
<?rfc symrefs="yes"?>
<!-- use symbolic references tags, i.e, [RFC2119] instead of [1] -->
<?rfc sortrefs="yes" ?>
<!-- sort the reference entries alphabetically -->
<!-- control vertical white space
(using these PIs as follows is recommended by the RFC Editor) -->
<?rfc compact="yes" ?>
<!-- do not start each main section on a new page -->
<?rfc subcompact="no" ?>
<!-- keep one blank line between list items -->
<!-- end of list of popular I-D processing instructions -->
<rfc category="std" docName="draft-xu-bier-encapsulation-03" ipr="trust200902">
<front>
<title abbrev="BIER Encapsulation">BIER Encapsulation</title>
<author fullname="Xiaohu Xu" initials="X.X." surname="Xu">
<organization>Huawei</organization>
<address>
<!--
<postal>
<street></street>
-->
<!-- Reorder these if your country does things differently -->
<!--
<city>Beijing</city>
<region></region>
<code></code>
<country>China</country>
</postal>
<phone>+44 7889 488 335</phone>
-->
<email>xuxiaohu@huawei.com</email>
<!-- uri and facsimile elements may also be added -->
</address>
</author>
<author fullname="S Somasundaram" initials="S.S." surname="Somasundaram">
<organization>Alcatel-Lucent</organization>
<address>
<!--
<postal>
<street></street>
-->
<!-- Reorder these if your country does things differently -->
<!--
<city>Bangalore</city>
<region></region>
<code></code>
<country>India</country>
</postal>
<phone>+44 7889 488 335</phone>
-->
<email>somasundaram.s@alcatel-lucent.com</email>
<!-- uri and facsimile elements may also be added -->
</address>
</author>
<author fullname="Christian Jacquenet" initials="C.J." surname="Jacquenet">
<organization>France Telecom</organization>
<address>
<!--
<postal>
<street></street>
-->
<!-- Reorder these if your country does things differently -->
<!--
<city>Soham</city>
<region></region>
<code></code>
<country>UK</country>
</postal>
<phone>+44 7889 488 335</phone>
-->
<email>christian.jacquenet@orange.com</email>
<!-- uri and facsimile elements may also be added -->
</address>
</author>
<author fullname="Robert Raszuk" initials="R.R." surname="Raszuk">
<organization>Mirantis Inc.</organization>
<address>
<!--
<postal>
<street></street>
-->
<!-- Reorder these if your country does things differently -->
<!--
<city>Soham</city>
<region></region>
<code></code>
<country>UK</country>
</postal>
<phone>+44 7889 488 335</phone>
-->
<email>robert@raszuk.net</email>
<!-- uri and facsimile elements may also be added -->
</address>
</author>
<!--
-->
<date day="" month="" year="2015"/>
<abstract>
<t>Bit Index Explicit Replication (BIER) is a new multicast forwarding
paradigm which doesn't require an explicit tree-building protocol and
doesn't require intermediate routers to maintain any multicast state.
This document proposes a transport-independent BIER encapsulation header
which is applicable in any kind of transport networks.</t>
</abstract>
</front>
<middle>
<section title="Introduction">
<t>Bit Index Explicit Replication (BIER) <xref
target="I-D.ietf-bier-architecture"/> is a new multicast forwarding
paradigm which doesn't require an explicit tree-building protocol and
doesn't require intermediate routers to maintain any multicast state. As
described in <xref target="I-D.ietf-bier-architecture"/>, BIER requires
that a multicast data packet (e.g., an IP packet or an MPLS packet) to
be encapsulated with a BIER header that carries the information needed
for supporting the BIER forwarding procedures. This information at least
includes Subdomain-ID, Set-Identifier (SI), Multi-Topology Identifier
(MT-ID) and BitString. Subdomain-ID, SI and BitString are used together
to identify the set of egress BFRs (BFERs) to which the packet must be
delivered. In addition, to indicate what type of payload is following
the BIER header, a protocol type field is neccessary. This document
proposes a transport-independent BIER encapsulation header which is
applicable in any kind of transport networks.</t>
<section title="Requirements Language">
<t>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 <xref
target="RFC2119">RFC 2119</xref>.</t>
</section>
</section>
<section anchor="Abbreviations_Terminology" title="Terminology">
<t>This memo makes use of the terms defined in <xref
target="I-D.ietf-bier-architecture"/>.</t>
</section>
<section title="BIER Header">
<t>The BIER header is shown as follows:</t>
<t><figure>
<artwork align="center"><![CDATA[ 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Ver | BS Length |Res| SI | MT-ID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| BFIR-ID | Sub-domain | Protocol |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Entropy | DS | TTL |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| BitString (first 32 bits) ~
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
~ ~
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
~ BitString (last 32 bits) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
]]></artwork>
</figure></t>
<t><list style="empty">
<t>Ver(sion): a 4-bit field identifying the version of the BIER
header. This document specifies version 0 of the BIER header.</t>
<t>BS Length: a one-octet field indicating the length of the
BitString in 4-byte. Note that legal BS Length values are specified
in <xref target="I-D.ietf-bier-architecture"/>.</t>
<t>Res: a 2-bit reserved field.</t>
<t>SI: a 10-bit field encoding the Set-Identifier (SI) for this
packet.</t>
<t>MT-ID: a one-octet field indicating which routing topology <xref
target="RFC4915"/> <xref target="RFC5120"/> should be applied for
BIER forwarding.</t>
<t>BFIR-ID: a 2-octet field encoding the BFR-ID of the BFIR, in the
sub-domain to which the packet has been assigned.</t>
<t>Sub-domain: a one-octet field encoding the sub-domain to which
the packet has been assigned.</t>
<t>Protocol: a one-octet field indicating the protocol type of the
BIER payload as per IP protocol numbers used in the Protocol field
of the IPv4 header and the Next Header field of IPv6 header. The
valid BIER payload types include but not limited to IPv4, IPv6,
MPLS, VXLAN <xref target="RFC7348"/>,VXLAN-GPE <xref
target="I-D.ietf-nvo3-vxlan-gpe"/> , and etc. The corresponding IP
Protocol numbers for VXLAN and VXLAN-GPE are to be allocated by
IANA.</t>
<t>Entropy: a 2-octet field containing an "entropy" value that can
be used for load balancing purposes.</t>
<t>BitString: a variable-length BitString field that, together with
the SI field, identifies all the destination BFERs for this
packet.</t>
<t>DS: The usage of this field is no different from that of the
Differentiated Services (DS) field in the IPv4 or IPv6 headers <xref
target="RFC2474"/>.</t>
<t>TTL: The usage of this field is no different from that of the
Time to Live (TTL) field in the IPv4 header.</t>
</list></t>
</section>
<section anchor="Encaps" title="Transport Encapsulation for BIER Header">
<t>Since the BIER encapsulation format as specified in Section 3 is
transport-independent, it can be encapsulated with any type of transport
encapsulation headers, such as Ethernet header, PPP header, IP header,
MPLS header, GRE header, UDP header etc. It requires for each possible
transport encapsulation header to be able to indicate the payload is an
BIER header. For instance, In the BIER-in-MAC encapsulation case, the
EtherType field in the Ethernet header is used. In the BIER-in-IP
encapsulation case, the Protocol field in the IPv4 or or the Next-Header
field in the IPv6 header is used. In the BIER-in-MPLS encapsulation
case, either the Protocol Type field <xref
target="I-D.xu-mpls-payload-protocol-identifier"/> within the MPLS
packet or a to-be-assigned Extended Special Purpose label <xref
target="RFC7274"/> is used.</t>
</section>
<section anchor="Acknowledgements" title="Acknowledgements">
<t>TBD.</t>
<!---->
</section>
<section anchor="IANA" title="IANA Considerations">
<t>This document includes a request to IANA to allocate an EtherType
code,a PPP protocol code, an IPv4 protocol code (i.e., an IPv6
Next-Header code), a UDP destination port for carring the
BIER-encapsulated packet over the corresponding transport networks.
Furthermore, This document includes a request to IANA to allocate IP
Protocol numbers for VXLAN and VXLAN-GPE respectively.</t>
<!---->
</section>
<section anchor="Security" title="Security Considerations">
<t>TBD.</t>
<!---->
</section>
</middle>
<back>
<references title="Normative References">
&RFC2119;
<?rfc include="reference.I-D.ietf-bier-architecture"?>
<?rfc include="reference.I-D.xu-mpls-payload-protocol-identifier"?>
<?rfc include="reference.RFC.7274"?>
<reference anchor="ETYPES">
<front>
<title>IEEE 802 Numbers</title>
<author>
<organization>The IEEE Registration Authority</organization>
</author>
<date year="2012"/>
<note title="">
<t><http://www.iana.org/assignments/ieee-802-numbers/ieee-802-numbers.xml>.</t>
</note>
</front>
</reference>
<!---->
</references>
<references title="Informative References">
<?rfc include="reference.RFC.7348"?>
<?rfc include="reference.I-D.ietf-nvo3-vxlan-gpe"?>
<?rfc include="reference.RFC.4915"?>
<?rfc include="reference.RFC.5120"?>
<?rfc include="reference.RFC.2474"?>
<!---->
</references>
</back>
</rfc>
| PAFTECH AB 2003-2026 | 2026-04-23 18:35:02 |