PCEP Extensions For Transporting Traffic Engineering (TE) Data

Slides:



Advertisements
Similar presentations
Page - 1 Stateful PCE Kexin Tang Xuerong Wang Yuanlin Bao ZTE Corporation draft-tang-pce-stateful-pce-01.txt.
Advertisements

RSVP-TE Extensions for SRLG Configuration of FA
71 th IETF – Philadelphia, USA March 2008 PCECP Requirements and Protocol Extensions in Support of Global Concurrent Optimization Young Lee (Huawei) J-L.
Extensions to the Path Computation Element Communication Protocol (PCEP) for Point-to-Multipoint Traffic Engineering Label Switched Paths draft-ietf-pce-pcep-p2mp-extensions-05.txt.
Problem Statement and Architecture for Information Exchange Between Interconnected Traffic Engineered Networks draft-farrel-interconnected-te-info-exchange-03.txt.
Page th IETF – Vancouver, December 2007 PCEP Requirements and Extensions for the support of Wavelength Switched Optical Networks (WSON) Young
PCEP Extensions for Segment Routing draft-ietf-pce-segment-routing-01
IETF 69, PCE WG, Chicago Encoding of Objective Functions in PCE Communication and Discovery Protocols draft-leroux-pce-of-01.txt J.L. Le Roux (France Telecom)
Institute of Computer and Communication Network Engineering OFC/NFOEC, 6-10 March 2011, Los Angeles, CA Lessons Learned From Implementing a Path Computation.
PCEP extensions for the computation of route offers with price draft-carrozzo-pce-pcep-route-price-00 G. Carrozzo, G. Bernini, G. Landi {g.carrozzo, g.bernini,
ZTE CORPORATION Extensions of BRPC and PCEP to Support Inter- AS Bidirectional LSP Path Computation draft-wang-pce-inter-as-extentions-00 Xuerong.
Page th IETF – San Francisco, CA, March 2009 A Framework for the Control and Measurement of Wavelength Switched Optical Networks (WSON) with Impairments.
82 nd IETF – Taipei, Taiwan, November 2011 Extensions to Path Computation Element Communication Protocol (PCEP) for Hierarchical Path Computation Elements.
Path Computation Element (PCE) Discovery using Domain Name System(DNS) draft-wu-pce-dns-pce-discovery-04 Qin Wu ) Dhruv Dhody
PCE Traffic Engineering Database Requirements draft-dugeon-pce-ted-reqs-01.txt O. Dugeon, J. Meuric (France Telecom / Orange) R. Douville (Alcatel-Lucent)
CCAMP WG, IETF 76th, Hiroshima, Japan draft-zhang-ccamp-gmpls-g709-lmp-discovery-02.txt LMP extensions for G.709 Optical Transport Networks Fatai Zhang.
PCE-based Computation for Inter-domain P2MP LSP draft-zhao-pce-pcep-inter-domain-p2mp-procedures-00.txt Quintin Zhao, Huawei Technology David Amzallag,
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.
Page th IETF – Chicago, July 2007 Applicability of GMPLS and PCE to Wavelength Switched Optical Networks Greg
Applicability of Existing Solutions to the Problem Space draft-takeda-l1vpn-applicability-03.txt.
1 OSPF Based L1VPN Auto-Discovery ( draft-bryskin-l1vpn-ospf-auto-discovery-00.txt ) Igor Bryskin (Movaz Networks) : Lou Berger (LabN.
66th IETF, Montreal, July 2006 PCE Working Group Meeting IETF-66, July 2006, Montreal A Backward Recursive PCE-based Computation (BRPC) procedure to compute.
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.
Extensions to PCEP for Hierarchical Path Computation Elements PCE draft-zhang-pcep-hierarchy-extensions-00 Fatai Zhang Quintin Zhao.
Draft-chen-rtgwg-resource-management-yang-00IETF 94 RTGWG1 PCE-initiated IP Tunnel draft-chen-pce-pce-initiated-ip-tunnel-00 Xia Chen, Zhenbin Li(Huawei)
Stateful PCE Extensions for Data Plane Switchover and Balancing draft-tanaka-pce-stateful-pce-data-ctrl-00 July, 2013 Yosuke Tanaka, Yuji Kamite NTT Communications,
Extensions to Path Computation Element Communication Protocol (PCEP) for Hierarchical Path Computation Elements (PCE) PCE WG, IETF 86th draft-zhang-pce-hierarchy-extensions-03.
PCEP extensions for GMPLS CCAMP WG, IETF 79th, Beijing, China draft-ietf-pce-gmpls-pcep-extensions-01 Cyril Margaria Nokia Siemens Networks Oscar González.
67th IETF - San Diego, CA, USA November 8, 2006 PCECP Requirements for support of Global Concurrent Optimization Y. Lee, Huawei, D. King, Aria Networks,
Path Computation Element (PCE) Discovery using Domain Name System(DNS) draft-wu-pce-dns-pce-discovery-07 Qin Wu ) Dhruv Dhody
BIER Use Case in VXLAN draft-wang-bier-vxlan-use-case-00 Linda Wang (Presenting) Sandy. Zhang & F. Hu.
Konstantin agouros Omkar deshpande
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,
Connecting MPLS-SPRING Islands over IP Networks
Advertising Generic Information in IS-IS
Multi-layer Multi-domain Inter-op Test based on ACTN Architecture
draft-patel-raszuk-bgp-vector-routing-01
Zhenbin Li, Li Zhang(Huawei Technologies)
draft-litkowski-pce-state-sync-00
Zhenbin Li, Kai Lu Huawei Technologies IETF 98, Chicago, USA
Path Computation Element Working Group
Jean-Philippe Vasseur – Cisco Systems Raymond Zhang - Infonet
Connections and Accesses for Hierarchical PCE
MPLS-TP Fault Management Draft draft-boutros-mpls-tp-fault-01
OSPF (Open Shortest Path First)
PCEP Extensions in Support of Transporting Traffic Engineering Data
Applicability of GMPLS and PCE to Wavelength Switched Optical Networks
Path Computation Element (PCE) Discovery using Domain Name System(DNS) draft-wu-pce-dns-pce-discovery-03 Qin Wu ) Dhruv Dhody
PCEP Extension for Native IP ietf
Guard Bands requirements for GMPLS controlled optical networks
Explicitly advertising the TE protocols enabled on links in OSPF
ACTN Information Model
ACTN Information Model
draft-lazzeri-pce-residual-bw-00
LDP Extensions for RMR draft-esale-mpls-ldp-rmr- extensions
PCE – Path Computation Element
CHAPTER 8 Network Management
Zhenbin Li, Shunwan Zhuang Huawei Technologies
Yang model for requesting
Abstraction and Control of TE Networks (ACTN) Abstraction Methods
Separating Routing Planes using Segment Routing draft-gulkohegde-spring-separating-routing-planes-using-sr-00 IETF 98 – Chicago, USA Shraddha Hegde
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.
An Update on BGP Support for 4-byte ASN
draft-barth-pce-association-bidir-01
draft-gandhi-pce-pm-07
draft-zhuang-pce-stateful-pce-lsp-scheduling-05
Extended BFD draft-mirmin-bfd-extended
draft-liu-pim-mofrr-tilfa-00
Standard Representation Of Domain Sequence
TRILL Header Extension Improvements
Presentation transcript:

PCEP Extensions For Transporting Traffic Engineering (TE) Data draft-lee-pce-transporting-te-data-01 (informational) draft-dhodylee-pce-pcep-te-data-extn-01 (standard) Dhruv Dhody, Huawei Young Lee, Huawei Daniele Ceccarelli, Ericcson IETF 91, Honolulu, November 2014

Architectural Context [RFC4655] Section 4.3 describes the potential load of the TED on a network node and proposes an architecture where the TED is maintained by the PCE rather than the network nodes. [RFC7399] pce-questions Section 3 touches upon this issue: “It has also been proposed that the PCE Communication Protocol (PCEP) [RFC5440] could be extended to serve as an information collection protocol to supply information from network devices to a PCE. The logic is that the network devices may already speak PCEP and so the protocol could easily be used to report details about the resources and state in the network, including the LSP state discussed in Sections 14 and 15.” IETF 91, Honolulu, November 2014

Options for nodes to share local TED info with PCEs Nodes send local info directly to all PCEs, Nodes send local info to a intermediary (publish/subscribe), Nodes send info to at least one PCE and have the PCEs share TED information. IETF 91, Honolulu, November 2014

IETF 91, Honolulu, November 2014 Applicability As per [I-D.lee-pce-transporting-te-data], the mechanism specified in this draft is applicable to: Where there is no IGP-TE or BGP-LS running at the PCE to learn TED. Where there is IGP-TE or BGP-LS running but with a need for a faster TED population and convergence at the PCE. A PCE may receive partial information (say basic TE) from IGP-TE and other information (optical and impairment) from PCEP. A PCE may receive full information from both IGP-TE and PCEP. A PCC may further choose to send only local TE information or both local and remote learned TED information. IETF 91, Honolulu, November 2014

IETF 91, Honolulu, November 2014 New Functions Capability Advertisement (PCE<->PCC): Both PCC and PCE MUST announce they support PCEP extensions for TED population during PCEP session establishment TED Synchronization (PCC->PCE): After initialization, the PCE MUST learn PCC’s TED before path computation. TE Report (PCC->PCE) A PCC sends a TE report to a PCE whenever the TED changes. IETF 91, Honolulu, November 2014

Capability Advertisement The OPEN object to include the TED Capability 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=[TBD5] | Length=4 | | Flags |R| R (Remote – 1 bit): If set by a PCC, it indicates that the PCC allows reporting of remote TED info learned via other means (e.g., IGP-TE or BGP-LS); If set by a PCE, it indicates the PCE is capable of receiving remote TED info. The advertisement of the TED capability implies support of local TE population (to be advertised via TE Report Message) 75th IETF, Stockholm, July 2009

TE Report A PCEP TE Report (TERpt) is a new message send by a PCC to PCE to report the TED state (via the TE object) <TERpt Message> ::= <Common Header> <te-report-list> Where: <te-report-list> ::= <TE> [<te-report-list>] The format of the TE object: 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 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Protocol-ID | Flag |R|S| | TE-ID | // TLVs // | | IETF 91, Honolulu, November 2014

TE-ID A PCEP-specific identifier for the TE node or link. A PCC creates a unique TE-ID for each TE node/link that is constant for the lifetime of a PCEP session. All subsequent PCEP messages then address the TE node/link by the TE-ID making incremental TED changes easier to encode. 75th IETF, Stockholm, July 2009

TED Synchronization When the SYNC Flag in the TE object is set to 1, each TE report is sent. The end of synchronization marker is a TERpt message with the SYNC Flag set to 0. 75th IETF, Stockholm, July 2009

Summary & Next Steps A reasonable level of interest expressed in this work in the mailing list. What do you think? 90th IETF, Toronto, July 2014