<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.ietf-bier-bierin6" target="https://datatracker.ietf.org/doc/html/draft-ietf-bier-bierin6-09">
   <front>
      <title>Supporting BIER in IPv6 Networks (BIERin6)</title>
      <author initials="Z." surname="Zhang" fullname="Zheng Zhang">
         <organization>ZTE Corporation</organization>
      </author>
      <author initials="Z. J." surname="Zhang" fullname="Zhaohui (Jeffrey) Zhang">
         <organization>Juniper Networks</organization>
      </author>
      <author initials="I." surname="Wijnands" fullname="IJsbrand Wijnands">
         <organization>Individual</organization>
      </author>
      <author initials="M. P." surname="Mishra" fullname="Mankamana Prasad Mishra">
         <organization>Cisco Systems</organization>
      </author>
      <author initials="H." surname="Bidgoli" fullname="Hooman Bidgoli">
         <organization>Nokia</organization>
      </author>
      <author initials="G. S." surname="Mishra" fullname="Gyan Mishra">
         <organization>Verizon</organization>
      </author>
      <date month="March" day="17" year="2024" />
      <abstract>
	 <t>   BIER is a multicast forwarding architecture that does not require
   per-flow state inside the network yet still provides optimal
   replication.  This document describes how the existing BIER
   encapsulation specified in RFC 8296 works in a non-MPLS IPv6 network,
   which is referred to as BIERin6.  Specifically, like in an IPv4
   network, BIER can work over L2 links directly or over tunnels.  In
   case of IPv6 tunneling, a new IP &quot;Next Header&quot; type is to be assigned
   for BIER.


	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-ietf-bier-bierin6-09" />
   
</reference>
