IP/MPLS Connectivity Provisioning Profile
draft-boucadair-connectivity-provisioning-profile-02
The information below is for an old version of the document | |||
---|---|---|---|
Document | Type | Expired Internet-Draft (individual) | |
Authors | Mohamed Boucadair , Christian Jacquenet , Ning Wang | ||
Last updated | 2014-03-03 (latest revision 2012-09-25) | ||
Stream | ISE | ||
Intended RFC status | Informational | ||
Formats |
Expired & archived
pdf
htmlized (tools)
htmlized
bibtex
|
||
IETF conflict review | conflict-review-boucadair-connectivity-provisioning-profile | ||
Stream | ISE state | Response to Review Needed | |
Consensus Boilerplate | Unknown | ||
Document shepherd | None | ||
IESG | IESG state | Expired | |
Telechat date | |||
Responsible AD | (None) | ||
Send notices to | rfc-ise@rfc-editor.org |
https://www.ietf.org/archive/id/draft-boucadair-connectivity-provisioning-profile-02.txt
Abstract
This document describes the Connectivity Provisioning Profile (CPP) and proposes a CPP Template to capture IP connectivity requirements to be met in the context of delivery of services (e.g. Voice over IP or IP TV) which are to be plugged upon an IP/MPLS infrastructure. The CPP defines the set of IP transfer parameters to be supported by the underlying IP/MPLS transport network together with a reachability scope and bandwidth/capacity needs. Appropriate performance metrics such as one-way delay, one-way delay variation are used to characterize an IP transfer service. Both global and restricted reachability scopes can be captured in the CPP. Having the generic CPP template allows for (1) automating the process of service negotiation and activation, thus accelerating service provisioning, (2) setting the (traffic) objectives of Traffic Engineering functions and service management functions and (3) enriching service and network management systems with 'decision- making' capabilities based on negotiated/offered CPPs.
Authors
Mohamed Boucadair
(mohamed.boucadair@orange.com)
Christian Jacquenet
(christian.jacquenet@orange.com)
Ning Wang
(n.wang@surrey.ac.uk)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)