< draft-xie-6man-bier-encapsulation-00.txt   draft-xie-6man-bier-encapsulation-01.txt >
Network Working Group J. Xie Network Working Group J. Xie
Internet-Draft G. Yan Internet-Draft Huawei Technologies
Intended status: Standards Track M. McBride Intended status: Standards Track L. Geng
Expires: December 30, 2018 Y. Xia Expires: January 3, 2019 L. Wang
Huawei Technologies China Mobile
June 28, 2018 G. Yan
M. McBride
Y. Xia
Huawei
July 2, 2018
Encapsulation for BIER in Non-MPLS IPv6 Networks Encapsulation for BIER in Non-MPLS IPv6 Networks
draft-xie-6man-bier-encapsulation-00 draft-xie-6man-bier-encapsulation-01
Abstract Abstract
Bit Index Explicit Replication (BIER) introduces a new multicast- Bit Index Explicit Replication (BIER) introduces a new multicast-
specific BIER Header. Currently BIER has two types of encapsulation specific BIER Header. Currently BIER has two types of encapsulation
formats: one is MPLS encapsulation, the other is Ethernet formats: one is MPLS encapsulation, the other is Ethernet
encapsulation. This document proposes a BIER IPv6 encapsulation for encapsulation. This document proposes a BIER IPv6 encapsulation for
Non-MPLS IPv6 Networks using an IPv6 Destination Option extension Non-MPLS IPv6 Networks using an IPv6 Destination Option extension
header. header.
skipping to change at page 1, line 43 skipping to change at page 1, line 47
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/. Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on December 30, 2018. This Internet-Draft will expire on January 3, 2019.
Copyright Notice Copyright Notice
Copyright (c) 2018 IETF Trust and the persons identified as the Copyright (c) 2018 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of (https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 7, line 16 skipping to change at page 7, line 16
'proto' field of the BIER header in the Destination Option Header. 'proto' field of the BIER header in the Destination Option Header.
Thus the 'Next Header' in the Destination Option Header is not need Thus the 'Next Header' in the Destination Option Header is not need
to identify the 'Upper-layer header' any more, and is recommended to to identify the 'Upper-layer header' any more, and is recommended to
be set to 'No Next Header (value 59)'. be set to 'No Next Header (value 59)'.
5. BIER Forwarding in Non-MPLS IPv6 Networks 5. BIER Forwarding in Non-MPLS IPv6 Networks
In a Non-MPLS IPv6 Network, BIER may be deployed in a hop-by-hop In a Non-MPLS IPv6 Network, BIER may be deployed in a hop-by-hop
manner, or possibly be deployed through an SRH tunnel either for manner, or possibly be deployed through an SRH tunnel either for
"bypassing Non-capable BIER routers" or "fast rerouting". Here is an "bypassing Non-capable BIER routers" or "fast rerouting". Here is an
example where a packet is first forwarded through an SRH tunnel and example where a packet is firstly forwarded through an SRH tunnel and
then through a hop-by-hop manner. then through a hop-by-hop BIER domain.
When a router along the Segment Routing path receives an IPv6 BIER When a router along the Segment Routing path receives an IPv6 BIER
packet with an SRH header, and if the IPv6 destination address is not packet with an SRH header, and if the IPv6 destination address is not
one of the router's address, then the packet is forwarded by an IPv6 one of the router's address, then the packet is forwarded by an IPv6
FIB lookup of the destination address and none of the IPv6 extension FIB lookup of the destination address and none of the IPv6 extension
headers will be checked. If the IPv6 Destination Address is one of headers will be checked. If the IPv6 Destination Address is one of
the router's address, and also one of the router's Segment (or SID) the router's address, and also one of the router's Segment (or SID)
of some type, then the router will do a specific function indicated of some type, then the router will do a specific function indicated
by the Segment, as defined in by the Segment, as defined in
[I-D.filsfils-spring-srv6-network-programming]. If the IPv6 [I-D.filsfils-spring-srv6-network-programming]. If the IPv6
skipping to change at page 7, line 50 skipping to change at page 7, line 50
6. pop the SRH 6. pop the SRH
7. forward the updated packet 7. forward the updated packet
8. ELSE 8. ELSE
9. drop the packet 9. drop the packet
10. ELSE 10. ELSE
11. drop the packet 11. drop the packet
Figure 2: End.BF Function Figure 2: End.BF Function
The End.BF function is used for the SRH tunnel destination router to The End.BF function is used for the SRH tunnel destination router to
terminate the source-routing SRH forwarding while begining the hop- terminate the source-routing SRH forwarding and begin the hop-by-hop
by-hop BIER IPv6 forwarding. After the SRH header is popped, the BIER IPv6 forwarding. After the SRH header is popped, the multicast
multicast address in the updated IPv6 Destination Address indicates address in the updated IPv6 Destination Address indicates the BIER
the BIER information of this 'host', and the packet will be forwarded information of this 'host', and the packet will be forwarded
according to the BIER Header in the BIER Destination Option TLV in according to the BIER Header in the BIER Destination Option TLV in
the IPv6 Destination Option extension header. the IPv6 Destination Option extension header of this 'host'.
In the following hop-by-hop forwarding procedure, the IPv6 In the following hop-by-hop forwarding procedure, the IPv6
Destination Address in an incoming packet indicates the BIER Destination Address in an incoming packet indicates the BIER
information of this 'host', and the packet will be forwarded information of this 'host', and the packet will be forwarded
according to the BIER Header in the BIER Destination Option TLV in according to the BIER Header in the BIER Destination Option TLV in
the IPv6 Destination Option extension header. A router is required the IPv6 Destination Option extension header. A router is required
to ignore the IPv6 BIER Destination Option if the IPv6 Destination to ignore the IPv6 BIER Destination Option if the IPv6 Destination
Address of a packet is not a multicast address, or is a multicast Address of a packet is not a multicast address, or is a multicast
adddress without indicating the BIER information of this 'host'. adddress without indicating the BIER information of this 'host'.
skipping to change at page 10, line 4 skipping to change at page 10, line 4
Requirement Levels", BCP 14, RFC 2119, Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997, DOI 10.17487/RFC2119, March 1997,
<https://www.rfc-editor.org/info/rfc2119>. <https://www.rfc-editor.org/info/rfc2119>.
Authors' Addresses Authors' Addresses
Jingrong Xie Jingrong Xie
Huawei Technologies Huawei Technologies
Email: xiejingrong@huawei.com Email: xiejingrong@huawei.com
Liang Geng
China Mobile
Beijing 10053
Email: gengliang@chinamobile.com
Lei Wang
China Mobile
Beijing 10053
Email: wangleiyjy@chinamobile.com
Gang Yan Gang Yan
Huawei Technologies Huawei
Email: yangang@huawei.com Email: yangang@huawei.com
Mike McBride Mike McBride
Huawei Technologies Huawei
Email: mmcbride7@gmail.com Email: mmcbride7@gmail.com
Yang Xia Yang Xia
Huawei Technologies Huawei
Email: yolanda.xia@huawei.com Email: yolanda.xia@huawei.com
 End of changes. 10 change blocks. 
17 lines changed or deleted 33 lines changed or added

This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/