IP Connectivity Provisioning Profile (CPP)
RFC 7297
Document | Type |
RFC - Informational
(July 2014; No errata)
Was draft-boucadair-connectivity-provisioning-profile (individual)
|
|
---|---|---|---|
Last updated | 2018-12-20 | ||
Stream | ISE | ||
Formats | plain text pdf html bibtex | ||
IETF conflict review | conflict-review-boucadair-connectivity-provisioning-profile | ||
Stream | ISE state | Published RFC | |
Consensus Boilerplate | Unknown | ||
Document shepherd | Adrian Farrel | ||
Shepherd write-up | Show (last changed 2014-03-13) | ||
IESG | IESG state | RFC 7297 (Informational) | |
Telechat date | |||
Responsible AD | (None) | ||
Send notices to | (None) | ||
IANA | IANA review state | Version Changed - Review Needed | |
IANA action state | No IANA Actions |
Independent Submission M. Boucadair Request for Comments: 7297 C. Jacquenet Category: Informational France Telecom ISSN: 2070-1721 N. Wang University of Surrey July 2014 IP Connectivity Provisioning Profile (CPP) Abstract This document describes the Connectivity Provisioning Profile (CPP) and proposes a CPP template to capture IP/MPLS connectivity requirements to be met within a service delivery context (e.g., Voice over IP or IP TV). The CPP defines the set of IP transfer parameters to be supported by the underlying transport network together with a reachability scope and bandwidth/capacity needs. Appropriate performance metrics, such as one-way delay or one-way delay variation, are used to characterize an IP transfer service. Both global and restricted reachability scopes can be captured in the CPP. Such a generic CPP template is meant to (1) facilitate the automation of the service negotiation and activation procedures, thus accelerating service provisioning, (2) set (traffic) objectives of Traffic Engineering functions and service management functions, and (3) improve service and network management systems with 'decision- making' capabilities based upon negotiated/offered CPPs. Status of This Memo This document is not an Internet Standards Track specification; it is published for informational purposes. This is a contribution to the RFC Series, independently of any other RFC stream. The RFC Editor has chosen to publish this document at its discretion and makes no statement about its value for implementation or deployment. Documents approved for publication by the RFC Editor are not a candidate for any level of Internet Standard; see Section 2 of RFC 5741. Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at http://www.rfc-editor.org/info/rfc7297. Boucadair, et al. Informational [Page 1] RFC 7297 CPP July 2014 Copyright Notice Copyright (c) 2014 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 1.1. Connectivity Provisioning Interface (CPI) . . . . . . . . 3 1.2. Rationale . . . . . . . . . . . . . . . . . . . . . . . . 4 1.3. Reference Architecture . . . . . . . . . . . . . . . . . 7 2. Scope of This Document . . . . . . . . . . . . . . . . . . . 9 3. Connectivity Provisioning Profile (CPP) . . . . . . . . . . . 9 3.1. Customer Nodes Map . . . . . . . . . . . . . . . . . . . 9 3.2. Scope . . . . . . . . . . . . . . . . . . . . . . . . . . 10 3.3. QoS Guarantees . . . . . . . . . . . . . . . . . . . . . 11 3.4. Availability . . . . . . . . . . . . . . . . . . . . . . 11 3.5. Capacity . . . . . . . . . . . . . . . . . . . . . . . . 12 3.6. Conformance Traffic . . . . . . . . . . . . . . . . . . . 13 3.7. Overall Traffic Guarantees . . . . . . . . . . . . . . . 13 3.8. Traffic Isolation . . . . . . . . . . . . . . . . . . . . 13 3.9. Flow Identification . . . . . . . . . . . . . . . . . . . 13 3.10. Routing and Forwarding . . . . . . . . . . . . . . . . . 14 3.11. Activation Means . . . . . . . . . . . . . . . . . . . . 15 3.12. Invocation Means . . . . . . . . . . . . . . . . . . . . 15 3.13. Notifications . . . . . . . . . . . . . . . . . . . . . . 16 4. CPP Template . . . . . . . . . . . . . . . . . . . . . . . . 16 5. Security Considerations . . . . . . . . . . . . . . . . . . . 18 6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 18 7. Informative References . . . . . . . . . . . . . . . . . . . 18 Boucadair, et al. Informational [Page 2] RFC 7297 CPP July 2014 1. Introduction This document describes the Connectivity Provisioning Profile (CPP) and proposes a CPP template to capture IP/MPLS connectivity requirements to be met within a service delivery context (e.g., Voice over IP, IP TV, and VPN services). In this document, the IP connectivity service is the IP transferShow full document text