Encapsulation for BIER in Non-MPLS IPv6 Networks

Slides:



Advertisements
Similar presentations
OLD DOG CONSULTING Challenges and Solutions for OAM in Point-to-Multipoint MPLS Adrian Farrel, Old Dog Consulting Ltd. Zafar Ali, Cisco Systems, Inc.
Advertisements

BIER Ping IETF 92 draft-kumarzheng-bier-ping-00
IPv6 Keith Wichman. History Based on IPv4 Based on IPv4 Development initiated in 1994 Development initiated in 1994.
1 Internet Protocol Version 6 (IPv6) What the caterpillar calls the end of the world, nature calls a butterfly. - Anonymous.
Network Layer IPv6 Slides were original prepared by Dr. Tatsuya Suda.
2: Comparing IPv4 and IPv6 Rick Graziani Cabrillo College
Network Layer: IPv6 IS250 Spring 2010
1Group 07 IPv6 2 1.ET/06/ ET/06/ ET/06/ EE/06/ EE/06/ EE/06/6473 Group 07 IPv6.
Brett Neely IP Next Generation. To boldly go where no network has gone before...
Exposing Source IP Address Type Requirements with DHCPv6 D. Moses, A. Yegin draft-moses-dmm-dhcp-ondemand-mobility-00.
IETF 81: V6OPS Working Group – Proxy Mobile IPv6 – Address Reservations 1 Reserved IPv6 Interface Identifier for Proxy Mobile IPv6 Sri Gundavelli (Cisco)
4: Network Layer4b-1 IPv6 r Initial motivation: 32-bit address space completely allocated by r Additional motivation: m header format helps speed.
Introduction to IPv6 ECE4110. Problems with IPv4 32-bit addresses give about 4,000,000 addresses IPv4 Addresses WILL run out at some point – Some predicted.
An end-to-end usage of the IPv6 flow label
Advertising Encapsulation Capability Using OSPF draft-xu-ospf-encapsulation-cap-01 Xiaohu Xu (Huawei) Robert Raszuk (Mirantis) Uma Chunduri.
IPv6. What is an IP address?  Each host on a TCP/IP network is uniquely identified at the IP layer with an address.  An Internet Protocol (IP) address.
Connecting IPv4 Islands over IPv6 MPLS Using IPv4 Provider Edge Routers(4PE) Zhenqiang Li China Mobile.
BIER Use Case in VXLAN draft-wang-bier-vxlan-use-case-00 Linda Wang (Presenting) Sandy. Zhang & F. Hu.
Requirements for LER Forwarding of IPv4 Option Packets
UDP Encapsulation for IP Tunneling
Connecting MPLS-SPRING Islands over IP Networks
Internet Protocol Version 6 Specifications
draft-xu-isis-nvo-cp-00 Xiaohu Xu (Huawei) Saumya Dikshit (Cisco)
Multicast VPN using BIER
Advertising Encapsulation Capability Using OSPF
Carrying IPSEC Authentication and ESP Headers Across SCPS-NP Networks
Fast Handover for Multicast in Proxy Mobile IPv6
IPv6 / IP Next Generation
IPv6 Router Alert Option for MPLS OAM
PLR Designation in RSVP-TE FRR
Guide to TCP/IP Fourth Edition
draft-chandra-mpls-rsvp-shared-labels-np-00
Multicast/BIER As A Service
N. Kumar, C. Pignataro, F. Iqbal, Z. Ali (Presenter) - Cisco Systems
Zhenbin Li, Shunwan Zhuang Huawei Technologies
A Unified Approach to IP Segment Routing
Greg Mirsky Jeff Tantsura Mach Chen Ilya Varlashkin
draft-ietf-detnet-dp-sol-00 Issues
Use of BIER Entropy for Data Center CLOS Networks
IETF 100, November 2017 Singapore
draft-barth-pce-association-bidir-01
Consideration of IPv6 Encapsulation for Path Services draft-li-6man-ipv6-sfc-ifit-00 Zhenbin Li, Shuping Peng.
IETF 103 Bangkok, Thailand - November 2018
draft-guichard-sfc-nsh-sr-02
IETF BIER, November 2017, Singapore
Use of p2mp BFD in PIM-SM (over shared-media segment) draft-mirsky-pim-bfd-p2mp-use-case Greg Mirsky Ji Xiaoli
IPv6 Encapsulation for IOAM - Enhancement of IPv6 Extension Headers draft-li-6man-ipv6-sfc-ifit-01 draft-li-6man-enhanced-extension-header-00 Zhenbin.
draft-liu-pim-mofrr-tilfa-00
BIER in IPv6 draft-zhang-bier-bierin6-03
OAM for Deterministic Networks with MPLS Data Plane draft-mirsky-detnet-mpls-oam Greg Mirsky Mach Chen IETF-105 July 2019, Montreal.
PW Control Word Stitching
Active OAM in Geneve draft-mmbb-nvo3-geneve-oam
How OAM Identified in Overlay Protocols draft-mirsky-rtgwg-oam-identify Greg Mirsky IETF-104 March 2019, Prague.
draft-xie-bier-ipv6-mvpn-01 Presenter: Jingrong Xie
Quan Xiong(ZTE) Gregory Mirsky(ZTE) Chang Liu(China Unicom)
draft-ietf-bier-ipv6-requirements-01
Inter-domain Multicast using BIERv6
BIER P2MP mLDP Signaling
OAM for Deterministic Networks draft-mirsky-detnet-oam
Data plane round-table Feedback
Editors: Bala’zs Varga, Jouni Korhonen
BGP VPN service for SRv6 Plus IETF 105, Montreal
Parag Jain, Samer Salam, Ali Sajassi (Cisco),
IETF BIER, November 2018, Bangkok
Supporting Flexible Algorithm Prefix SIDs in LSP Ping/Traceroute
BIER Prefix Redistribute draft-zwzw-bier-prefix-redistribute-01
IETF 103 Jeffrey Zhang, Juniper Nils Warnke, DT Ice Wijnands, Cisco
draft-venaas-bier-mtud-01
BIER Prefix Redistribute draft-zwzw-bier-prefix-redistribute-00
Inter-AS OAM for SR Networks IETF 105, Montreal
Presentation transcript:

Encapsulation for BIER in Non-MPLS IPv6 Networks 2018/12/9 Encapsulation for BIER in Non-MPLS IPv6 Networks draft-xie-bier-6man-encapsulation-02 IETF103 2018-11-07 Bangkok Jingrong Xie @Huawei Liang Geng @China Mobile Lei Wang @China Mobile Mike McBride @Huawei Gang Yan @Huawei Yang Xia@Huawei

Should bier start work on v6 encap? If there is interest let’s get going, perhaps problem statement draft with use cases and then solutions draft? Determine if we really have a need for an encapsulation that is IPv6-specific

Replicate bier packets from BFIR to BFERs across v6 ipv6 S3 bfer

Do we need an IPv6 encapsulation ? SR has simplified the IP transport. SR has SR-MPLS and SRv6. SRv6 works without MPLS labels: transport labels like LSP, Service labels like Vpn, etc. How does BIER run in SRv6 network ? Do we need a BIER IPv6 encapsulation ? Page 4

The existing proposals Embedded BitString in part of the 128bit IPv6 Destination. A new Hop-By-Hop Extension Header. A new Extension Header with unicast destination address. A new Extension Header with multicast destination address. A Destination Option Header with multicast destination address. Page 5

The past discussions In Sep 2016, there was a suggestion to provide a method of using IPv6 extension header: https://www.ietf.org/mail-archive/web/bier/current/msg00986.html Again there were some 'requirements' mentioned by this thread: https://www.ietf.org/mail-archive/web/bier/current/msg00991.html "it shouldn't require hop-by-hop modification of the IP destination address field, and it shouldn't require the BFRs to inspect layer 4, and it shouldn't require changes to layer 4, and it shouldn't allow a multicast address to be put in the IP source address field, and it shouldn't assume that bits never get set incorrectly, and it shouldn't require changes in source address filtering procedures. In addition, it should be possible to use it to support the entire BIER architecture" Page 6

bierv6 encap Could use new defined IPv6 extension to carry the BIER header. Could use existing Dest Option extension to carry the BIER header. Page 7

One proposed encapsulation IPv6 Header(DA=Multicast Addr) + Dest Opt Hdr(TLV<T=bier, L, V=BIER Hdr>) The IPv6 BIER Option is the only one TLV in the Destination Options, with a Option Type BIER [IANA]. The Destination Options that carry a BIER Header, has a recommended Next Header Value of 59. Only be checked when the Destination Address is a Multicast Address indicating BIER. [IANA] is expected to specify a Multicast Address for BIER. Page 8

Why Proposing the encapsulation ? [RFC8200] Defining new IPv6 extension headers is not recommended, unless there are no existing IPv6 extension headers that can be used by specifying a new option for that IPv6 extension header. [RFC8200] it is recommended that the Destination Options header is used to carry optional information that must be examined only by a packet's destination node(s), because they provide better handling and backward compatibility. [RFC8200] Extension headers are not processed until the packet reaches the node (or each of the set of nodes, in the case of multicast) identified in the Destination Address field of the IPv6 header. The reason why we select Using [Multicast Addr + Dest Opt Hdr] to pilot the hop- by-hop replication. Page 9

Open discussion Forget debating the different solutions right now… Does the WG think a BIER IPv6 encapsulation problem/requirement draft is good? If so let’s do that. Then solutions. Page 10

2018/12/9 Thank you ! Thank You