Zhenbin Li, Li Zhang(Huawei Technologies)

Slides:



Advertisements
Similar presentations
RSVP-TE Extensions for SRLG Configuration of FA
Advertisements

OLD DOG CONSULTING Challenges and Solutions for OAM in Point-to-Multipoint MPLS Adrian Farrel, Old Dog Consulting Ltd. Zafar Ali, Cisco Systems, Inc.
Requirement and protocol for WSON and non-WSON interoperability CCAMP WG, IETF 81th, Quebec City, Canada draft-shimazaki-ccamp-wson-interoperability-00.
1 Reoptimization of Point-to-Multipoint Traffic Engineering Loosely Routed LSPs draft-tsaad-mpls-p2mp-loose-path-reopt-00 Author list: Tarek Saad
Draft-li-mpls-global-label-usecases-00IETF 88 SPRING WG1 Usecases of MPLS Global Label draft-li-mpls-global-label-usecases-00 Zhenbin Li, Quintin Zhao.
Draft-chen-i2rs-mpls-ldp-usecases-00/ draft-huang-i2rs-mpls-te-usecase-00 IETF 88 I2RS1 Use Cases for an Interface to MPLS Protocol draft-chen-i2rs-mpls-ldp-usecases-00/
MPLS H/W update Brief description of the lab What it is? Why do we need it? Mechanisms and Protocols.
MPLS and Traffic Engineering
Seamless MPLS for Mobile Backhaul draft-li-mpls-seamless-mpls-mbh-00
A Study of MPLS Department of Computing Science & Engineering DE MONTFORT UNIVERSITY, LEICESTER, U.K. By PARMINDER SINGH KANG
Draft-li-rtgwg-cc-igp-arch-00IETF 88 RTGWG1 An Architecture of Central Controlled Interior Gateway Protocol (IGP) draft-li-rtgwg-cc-igp-arch-00 Zhenbin.
Draft-li-ccamp-auto-mbb-te-path-00IETF 88 CCAMP1 IGP Extensions for Automatic Computation of MPLS Traffic Engineering Path Using Traffic Engineering Layers.
Draft-li-mpls-seamless-mpls-mbb-00IETF 87 MPLS1 Seamless MPLS for Mobile Backhaul draft-li-mpls-mbb-seamless-mpls-00 Zhenbin Li, Lei Li (Huawei) Manuel.
1 Multi Protocol Label Switching Presented by: Petros Ioannou Dept. of Electrical and Computer Engineering, UCY.
64th IETF Vancouver Nov Graceful Shutdown in MPLS Traffic Engineering Networks draft-ali-ccamp-mpls-graceful-shutdown-02.txt Zafar Ali
Draft-li-mpls-global-label-framework-02IETF 90 MPLS WG1 A Framework of MPLS Global Label draft-li-mpls-global-label-framework-02 Zhenbin Li, Quintin Zhao,
1 Reoptimization of Point-to-Multipoint Traffic Engineering Loosely Routed LSPs draft-tsaad-mpls-p2mp-loose-path-reopt-03 Author list: Tarek Saad
Draft-li-mpls-network-virtualization-framework-00IETF 88 SPRING WG1 Framework of Network Virtualization Based on MPLS Global Label draft-li-mpls-network-virtualization-framework-00.
Kireeti Kompella draft-kompella-mpls-rmr-01
1 Ping and Traceroute for GMPLS LSPs in Non-Packet Switched Networks draft-ali-ccamp-gmpls-lsp-ping-traceroute-01.txt Zafar Ali, Roberto Cassata (Cisco.
Draft-torvi-mpls-rsvp-ingress-protection-00IETF 84 MPLS: 30 July Ingress Protection for RSVP-TE p2p and p2mp LSPs draft-torvi-mpls-rsvp-ingress-protection-00.
IP Traffic Engineering RSP draft-shen-ip-te-rsp-01.txt Naiming Shen Albert Tian Jun Zhuang
1 68th IETF, Prague, March 2007 Address Resolution for GMPLS controlled PSC Ethernet Interfaces draft-ali-arp-over-gmpls-controlled-ethernet-psc-i-04.txt.
Draft-li-mpls-proxy-te-lsp-01IETF 90 MPLS1 Proxy MPLS Traffic Engineering Label Switched Path(LSP) draft-li-mpls-proxy-te-lsp-01 Zhenbin Li, Xinzong Zeng.
Draft-li-mpls-proxy-te-lsp-00IETF 87 MPLS1 Proxy MPLS Traffic Engineering Label Switched Path(LSP) draft-li-mpls-proxy-te-lsp-00 Zhenbin Li, Xinzong Zeng.
1 MPLS Source Label Mach Chen Xiaohu Xu Zhenbin Li Luyuan Fang IETF87 MPLS Aug Berlin draft-chen-mpls-source-label-00.
Draft-li-mpls-serv-driven-co-lsp-fmwk-03IETF 90 MPLS1 A Framework for Service-Driven Co-Routed MPLS Traffic Engineering LSPs draft-li-mpls-serv-driven-co-lsp-fmwk-03.
Draft-rkhd-mpls-tp-sd-03 IETF 81 Jul 2011 Rafi Ram Daniel Cohn Masahiro Daikoku.
BGP extensions for Path Computation Element (PCE) Discovery in a BGP/MPLS IP-VPN draft-kumaki-pce-bgp-disco-attribute-03.txt Kenji Kumaki KDDI R&D Labs,
draft-jounay-pwe3-dynamic-pw-update-00.txt IETF 70 PWE3 Working Group
Requirements for LER Forwarding of IPv4 Option Packets
Residence Time Measurement draft-mirsky-mpls-residence-time-02
Zhenbin Li, Kai Lu Huawei Technologies IETF 98, Chicago, USA
IETF 67, MPLS WG, San Diego 11/08/2006
Jean-Philippe Vasseur – Cisco Systems Raymond Zhang - Infonet
A Framework for Service-Driven Co-Routed MPLS Traffic Engineering LSPs draft-li-mpls-serv-driven-co-lsp-fmwk-01 Zhenbin Li, Shunwan Zhuan, Jie Dong Huawei.
MPLS-TP Fault Management Draft draft-boutros-mpls-tp-fault-01
draft-huang-detnet-xhaul-00
Presenter: Jeffrey Zhang
MPLS LSP Instant Install draft-saad-mpls-lsp-instant-install-00
RSVP Setup Protection draft-shen-mpls-rsvp-setup-protection-02
Multi Protocol Label Switching (MPLS)
An analysis of scaling issues in MPLS-TE backbone networks
IETF 96 (MPLS WG) Abhishek Deshmukh Kireeti Kompella (presenting)
A Scalable Multipath Algorithm in Hierarchical MPLS Networks
Explicitly advertising the TE protocols enabled on links in OSPF
Extensions to Resource Reservation Protocol For Fast Reroute of Traffic Engineering GMPLS LSPs draft-ietf-teas-gmpls-lsp-fastreroute-06 Authors: Mike Taillon.
CHAPTER 8 Network Management
Authors Mach Chen Andrew G. Malis
Greg Mirsky IETF-99 July 2017, Prague
Zhenbin Li, Shunwan Zhuang Huawei Technologies
Greg Mirsky Jeff Tantsura Mach Chen Ilya Varlashkin
IETF South Korea PCEP Link-State extensions for Segment Routing draft-li-pce-pcep-ls-sr-extension-01 Zhenbin Li (Huawei) Xia Chen (Huawei) Nan.
OSPF WG Status IETF 98, Chicago
draft-gandhi-pce-pm-07
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.
Technical Issues with draft-ietf-mpls-bfd-directed
Network-automatic-optimization
PW Control Word Stitching
IETF 102 (TEAS WG) Abhishek Deshmukh (presenting) Kireeti Kompella
PW Control Word Stitching
YANG Data Models for TE and RSVP draft-ietf-teas-yang-te-19 draft-ietf-teas-yang-rsvp-10 draft-ietf-teas-yang-rsvp-te-05 draft-ietf-teas-yang-te-mpls-01.
OAM for Deterministic Networks draft-mirsky-detnet-oam
Kapil Arora Shraddha Hegde IETF-103
Zhaohui (Jeffrey) Zhang
Spencer Giacalone, Alia Atlas, John Drake, Dave Ward
Supporting Flexible Algorithm Prefix SIDs in LSP Ping/Traceroute
Pseudo-Wire Protection
TICTOC WG Transporting PTP Messages (1588) over MPLS Networks
E. Bellagamba, Ericsson P. Sköldström, Acreo D. Ward, Juniper
Presentation transcript:

RSVP-TE Extensions for Bit Error Rate (BER) Measurement draft-zhang-ccamp-rsvpte-ber-measure-02 Zhenbin Li, Li Zhang(Huawei Technologies) Guangming Yang(China Telecom) IETF 90, Toronto, Canada

Introduction Bit Error Rate (BER) is a significant parameter for Mobile Backhaul Service In IP/MPLS Mobile Backhaul Network, MPLS TE LSP is used to carry the mobile service, which maybe encapsulated in PW or L3VPN end to end MPLS TE Hot-standby is always used for traffic protection. The protection switch is always triggered by the failure detection instead of quality degradation. BER measurement requirement should be advertised to all of the LSRs of the MPLS TE LSP, and the BER measurement result need to report to the ingress LSR. It can be used for protection switch. Here, we propose two extensions of RSVP-TE: 1. Advertise the BER measure requirement of the specific LSP to its transit LSRs and egress LSR 2. Report the BER measurement result from any transit or egress LSR towards the ingress LSR

LSP_ATTRIBUTES Class=197, C-Type=1 RSVP-TE extension (1) BER_REQUEST TLV LSP_ATTRIBUTES Class=197, C-Type=1 Type=TBD,BER_REQ TLV 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 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Type=BER_REQ TLV(TBD) | Length | | BER threshold | Procedure RSVP-TE Path Message SHOULD be sent with BER_REQUEST TLV to advertise the BER measurement requirement to the transit LSRs and egress LSR If a LSP dose not require BER measurement anymore, a Path Message without BRE_REQUEST TLV SHOULD be sent The LSR receiving the Path Message with BER_REQUEST TLV will start BER measurement for this LSP with the threshold value set in the TLV

RSVP-TE extension (2) Error code of BER measurement report Procedure Error code Error value Description --------------------------------------------------------------------------- TBD "BER 0 bit error elimination measurement report" 1 bit error indication Procedure when the BER measurement value exceeds the threshold, a PathErr Message MUST be sent towards the ingress LSR of the LSP with the BER Error Code with Error Value 1 for bit error indication When the BER measurement value is less than the threshold, the LSR MUST send a PathErr Message with BER Error Value 0 for bit error elimination

Comments Response (1) Question1: How to measure the BER in IP network? The bit error rate (BER) is the number of bit errors divided by the total number of transferred bits during a studied time interval. BER is a unitless metric for performance measurement and often expressed as a percentage. In IP network, the traffic stream is based on data packet which may be not get the accurate BER value like the optical network. But it can use multiple alternative ways for BER measurement depending on implementation. For example, the optical layer’s BER may be adopted as that of the IP layer for P2P link. The widely used CRC (Cyclic Redundancy Check) in the IP network is another possible way as the alternative of BER.

Comments Response (2) Question2: If this is a functionality always running, why not using IGP instead of RSVP-TE? Since the application scenarios proposed here is to trigger the protection service traffic switch based on the BER measurement, the requirement is service-specific and the decision is determined by the service end-point. RSVP-TE is an appropriate way to advertise the BER measurement to the service end-point which has BER measurement requirement instead of flooding the BER information to all nodes like IGP extensions. IGP is truly a possible way to flood BER information. It can be taken into account later for the enhanced traffic engineering path calculation application scenarios like other IGP TE extended metrics [I-D.ietf-isis-te-metric-extensions-03].

Comments Response (3) Question3:The error rate measurement is an OAM function. I wonder why you don't want to use already defined mechanisms of RSVP to turn on and off OAM functions and define a new one The mechanisms of RSVP to turn on and off OAM functions usually enabled only on the ingress and egress nodes. But for the BER measurement, all of the nodes along the LSP path should have knowledge of the BER measurement requirement to enable BER measurement function. So the new RSVP-TE protocol extensions are introduced.

Draft Updates One co-author is added: Guangming Yang from China Telecom. Redefine the requirement to cope with single-point BER measurement firstly. Correct text errors.

Next Steps Solicit comments and feedback. Request for WG acceptance.