Lu Huang, China Mobile Shujun Hu, China Mobile Michael Wang, Huawei

Slides:



Advertisements
Similar presentations
Introduction to IPv6 Presented by: Minal Mishra. Agenda IP Network Addressing IP Network Addressing Classful IP addressing Classful IP addressing Techniques.
Advertisements

CPSC Network Layer4-1 IP addresses: how to get one? Q: How does a host get IP address? r hard-coded by system admin in a file m Windows: control-panel->network->configuration-
Transitioning to IPv6 April 15,2005 Presented By: Richard Moore PBS Enterprise Technology.
S4C4 PPP. Protocols Point to Point Protocol Link Control Protocol Network Control Program Password Authentication Protocol Challenge Handshake Authentication.
SCSC 455 Computer Security Virtual Private Network (VPN)
5/31/05CS118/Spring051 twisted pair hub 10BaseT, 100BaseT, hub r T= Twisted pair (copper wire) r Nodes connected to a hub, 100m max distance r Hub: physical.
1 Interconnection ECS 152A. 2 Interconnecting with hubs r Backbone hub interconnects LAN segments r Extends max distance between nodes r But individual.
TELE202 Lecture 10 Internet Protocols (2) 1 Lecturer Dr Z. Huang Overview ¥Last Lecture »Internet Protocols (1) »Source: chapter 15 ¥This Lecture »Internet.
Use Cases and API Extension for Source IP Address Selection draft-sijeon-dmm-use-cases-api-source-00.txt Presenter: Alper Yegin Authors: Seil Jeon, Sergio.
Cisco S4C6 Frame Relay.
Mobile IP Overview and Discussion. 2 Spectrum of Mobility – from network perspective no mobility high mobility mobile user, using same access point mobile.
Dean Cheng Jouni Korhonen Mehamed Boucadair
Generic Network Virtualization Encapsulation draft-gross-geneve-00 Pankaj Garg Jesse Gross
Authentication Mechanism for Port Control Protocol (PCP) draft-wasserman-pcp-authentication-01.txt Margaret Wasserman Sam Hartman Painless Security Dacheng.
Real-time Flow Management 2 BOF: Remote Packet Capture Extensions Jürgen Quittek NEC Europe Ltd, Heidelberg, Germany Georg Carle GMD.
1 © OneCloud and/or its affiliates. All rights reserved. VXLAN Overview Module 4.
Chapter 19 Binding Protocol Addresses (ARP) A frame transmitted across a physical network must contain the hardware address of the destination. Before.
1 © NOKIA FILENAMs.PPT/ DATE / NN Requirements for Firewall Configuration Protocol March 10 th, 2005 Gabor Bajko Franck Le Michael Paddon Trevor Plestid.
Dean Cheng 81 st IETF Quebec City RADIUS Extensions for CGN Configurations draft-cheng-behave-cgn-cfg-radius-ext
5: DataLink Layer5-1 Hubs Hubs are essentially physical-layer repeaters: m bits coming from one link go out all other links m at the same rate m no frame.
User Application Control (Keypress Events) SIPPING WG - IETF 53 Robert Fairlie-Cuninghame, Bert Culpepper, Jean-François Mulé.
Active-active access in NVO3 network draft-hao-l2vpn-evpn-nvo3-active-active-00 July 20131Active-active access in NVO3 network Weiguo Hao(Huawei) Yizhou.
8 Byte BGP Communities Finding a practical way forward.
Network Models. 2.1 what is the Protocol? A protocol defines the rules that both the sender and receiver and all intermediate devices need to follow,
BIER Use Case in VXLAN draft-wang-bier-vxlan-use-case-00 Linda Wang (Presenting) Sandy. Zhang & F. Hu.
Gateway-Initiated 4over6 Deployment
A quick intro to networking
RSVP-TE Extensions for Associated Co-routed Bidirectional Label Switched Paths (LSPs) draft-gandhishah-teas-assoc-corouted-bidir-01 Author list: Rakesh.
draft-xu-isis-nvo-cp-00 Xiaohu Xu (Huawei) Saumya Dikshit (Cisco)
VDP extension for SR-IOV
EAP-GEE Lakshminath Dondeti Vidya Narayanan
OSPF (Open Shortest Path First)
PCEP Extensions For Transporting Traffic Engineering (TE) Data
Advertising Encapsulation Capability Using OSPF
Hubs Hubs are essentially physical-layer repeaters:
Zhenqiang Li Rong Gu China Mobile Jie Dong Huawei Technologies
Radius Attribute for MAP draft-jiang-softwire-map-radius-03
Hubs Hubs are essentially physical-layer repeaters:
CU separated BNG Protocol
Chapter 3: Open Systems Interconnection (OSI) Model
Guide to TCP/IP Fourth Edition
Zhenbin Li, Shunwan Zhuang Huawei Technologies
Yang Data Model for VxLAN Protocol
Encapsulation for BIER in Non-MPLS IPv6 Networks
Network Virtualization Overlays (NVO3) Working Group IETF 101, March 2018, London Chairs: Secretary: Sam Aldrin Matthew Bocci.
YANG data model of Control-Plane and User-Plane Separation BNG
Network Virtualization Overlays (NVO3) Working Group IETF 99, July 2017, Prague Chairs: Secretary: Sam Aldrin Matthew Bocci
Implementing an OpenFlow Switch on the NetFPGA platform
Lu Huang Shujun Hu China Mobile
Requirements for C&U separation BNG Protocol
BGP community based PCE in native IP network
Providing Faster GAS Response
DetNet Information Model Consideration
Aijun Wang China Telecom Nov 2017
draft-barth-pce-association-bidir-01
1 Multi-Protocol Label Switching (MPLS). 2 MPLS Overview A forwarding scheme designed to speed up IP packet forwarding (RFC 3031) Idea: use a fixed length.
Delivering the Data.
ExPLORE Complex Oceanographic Data
DHCP: Dynamic Host Configuration Protocol
IETF BIER, November 2017, Singapore
How OAM Identified in Overlay Protocols draft-mirsky-rtgwg-oam-identify Greg Mirsky IETF-104 March 2019, Prague.
Quan Xiong(ZTE) Gregory Mirsky(ZTE) Chang Liu(China Unicom)
PIM Assert Message Packing
BGP VPN service for SRv6 Plus IETF 105, Montreal
Internet Protocol version 6 (IPv6)
TRILL Header Extension Improvements
Enhanced Alternate Marking Method
draft-gandhi-spring-sr-mpls-pm-03
YANG Data Models for TE and RSVP draft-ietf-teas-yang-te-21 draft-ietf-teas-yang-rsvp-11 draft-ietf-teas-yang-rsvp-te-07 Tarek Saad, Juniper Networks Rakesh.
IESG LC: BFD for VXLAN draft-ietf-bfd-vxlan
Presentation transcript:

VXLAN GPE Extension for Packets Exchange Between Control and User Plane of vBNG Lu Huang, China Mobile Shujun Hu, China Mobile Michael Wang, Huawei Ting Ao, ZTE

Problem to be addressed For China Mobile’s metro network evolution, we choose to separate control plane and user plane of the traditional BNG ( Broadband Network Gateway, or called BRAS, Broadband Remote Access Server) BNG-CP BNG-UP Service Interface Traditional BNG Between BNG-CP and UP, service interface is used to transmit PPPoE/IPoE authentication packets from UP to CP. We prefer to use VxLAN to encapsulate user’s packets. Furthermore, user’s port information on BNG-UP should be reported to BRAS-CP For TE, TS, LB, we need the BGP community information of a specific flow. We usually design several communities for one AS. BRAS-CP VxLAN No standard way for carrying port information in VxLAN header PPPoE BRAS-UP PPPoE Port information includes: device ID, slot ID, subcard ID, port ID User

ifIndex ( 32bit, speified in [RFC2863]) Proposed solution Extend VxLAN-GPE header to meet the requirement because it seems leverage the flexibility and complexity. Flag Reserved New Next protocol = vBNG service header VNI Next protocol Node ID Slot ID Subcard ID Port ID Port type VXLAN GPE Header vBNG Service Header An optional format for port information For TE, TS, LB, we need the BGP community information of a specific flow. We usually design several communities for one AS. Flag Next protocol Reserved Node ID ifIndex ( 32bit, speified in [RFC2863]) It’s a standard way to indicate a port/interface. But it can’t explicitly show the port’s location. CP should maintain a mapping table between ifIndex and physical port exactly same as UP. Should define a way to generate this table, UP or CP make the decision? It’s relatively more complex than the explicit way

Example of PPPoE dialup process For TE, TS, LB, we need the BGP community information of a specific flow. We usually design several communities for one AS.

Next Steps Welcome your comments and suggestions Request for WG adoption For TE, TS, LB, we need the BGP community information of a specific flow. We usually design several communities for one AS.

Thanks