UNI Extensions for Diversity and Latency Support
draft-fedyk-ccamp-uni-extensions-04

Document Type Replaced Internet-Draft (individual)
Last updated 2014-08-11 (latest revision 2014-02-14)
Replaced by draft-ietf-ccamp-lsp-diversity
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
pdf htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Replaced by draft-ietf-ccamp-lsp-diversity
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-fedyk-ccamp-uni-extensions-04.txt

Abstract

This document builds on the GMPLS overlay model [RFC4208] and defines extensions to the GMPLS User-Network Interface (UNI) to support route diversity within the core network for sets of LSPs initiated by edge nodes. A particular example where route diversity within the core network is desired, are dual-homed edge nodes. The core network is typically composed of multiple network domains and those multi-domain diversity aspects that have an implication on the GMPLS UNI extensions are discussed. The document also defines GMPLS UNI extensions to deal with latency requirements for edge node initiated LSPs. This document uses a VPN model that is based on the same premise as L1VPN framework [RFC4847] but may also be applied to other technologies. The extensions are applicable both to VPN and non VPN environments. These extensions move the UNI from basic connectivity to enhanced mode connectivity by including additional constraints while minimizing the exchange of CE to PE information. These extensions are applicable to the overlay extension service model. Route Diversity for customer LSPs are a common requirement applicable to L1VPNs. The UNI mechanisms described in this document are L1VPN compatible and can be applied to achieve diversity for sets of customer LSPs. The UNI extensions in support of latency constraints can also be applied to the extended overlay service model in order for the customer LSPs to meet certain latency requirements.

Authors

Don Fedyk (don.fedyk@hp.com)
Dieter Beller (dieter.beller@alcatel-lucent.com)
Lieven Levrau (lieven.levrau@alcatel-lucent.com)
Daniele Ceccarelli (daniele.ceccarelli@ericsson.com)
Fatai Zhang (zhangfatai@huawei.com)
Yuji Tochio (tochio@jp.fujitsu.com)
Xihua Fu (fu.xihua@zte.com.cn)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)