1 / 7

Zafar Ali George Swallow Clarence Filsfils Luyuan Fang Matt Hartley Kenji Kumaki Rüdiger Kunze Daniele Ceccarelli X

RSVP-TE extension for extension for signaling Objective Function and Metric Bound draft -ali-ccamp-rc-objective-function-metric-bound- 04.txt. Zafar Ali George Swallow Clarence Filsfils Luyuan Fang Matt Hartley Kenji Kumaki Rüdiger Kunze Daniele Ceccarelli Xian Zhang .

herman
Download Presentation

Zafar Ali George Swallow Clarence Filsfils Luyuan Fang Matt Hartley Kenji Kumaki Rüdiger Kunze Daniele Ceccarelli X

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. RSVP-TE extension for extension for signaling Objective Function and Metric Bounddraft-ali-ccamp-rc-objective-function-metric-bound-04.txt Zafar Ali • George Swallow Clarence Filsfils Luyuan Fang Matt Hartley Kenji Kumaki RüdigerKunze Daniele Ceccarelli Xian Zhang Cisco Systems Cisco Systems Cisco Systems • Cisco Systems • Cisco Systems KDDI Corporation Deutsche Telekom AG Ericsson Huawei Technologies 88th IETF, CCAMP WG, Vancouver, BC, Canada (November 2013)

  2. Large SP Transport Layer Environment • Mixed Vendor Environment; Possible Dual Cores • Several Vendors in access • No PCE is deployed • SDN not yet deployed • Multiple operations groups NNI NNI Signaling NMS “SDN”

  3. Large SP Transport Layer Environment • Mixed Vendor Environment; Possible Dual Cores • Several Vendors in access • No PCE is deployed • SDN not yet deployed • Multiple operations groups NNI NNI SDN Signaling NMS “SDN”

  4. Operational Culture • Good fences make good neighbors • UNI exists to solve a political problem • otherwise we’d just have GMPLS • Fewer protocols is better (whether or not true, it is perceived) • Less training • Less configuration • Simpler debugging • Above sums to less OpEx • Resistant to allowing devices outside their control to participate in their protocols

  5. The full picture SDN NNI NNI SDN Signaling NMS “SDN”

  6. Recovery Requirements • Restoration needs to be performed in fully distributed fashion. • The entity that provisioned the path options may not be accessible/active during a failure, e.g., SDN controller, planning tool, manual, etc. • That entity may be overloaded during failure scenarios • Involving that entity will slow down the restoration. • A centralized entity may provide more relaxed constraints to be used in the event of a hard failure • (i.e. the primary constraints or ERO cannot be met) • This approach offers the benefits of centralized planning, but gives network autonomy to find restoration paths • Note that centralized planning could be an off-line exercise

  7. Motivation behind in/exclude route & OF • RFC4208 restrictive in scope • Idea is to open it up to information that parties are willing to agree to share • Allow User to learn SRLGs and latency • Allow User to specify requirements in more abstract, but highly relevant terms • Diverse from another path • Follow another path • Meet a bound on latency • Meet some other objective

More Related