RFC 7297 on IP Connectivity Provisioning Profile (CPP)

rfc-editor@rfc-editor.org Fri, 04 July 2014 01:26 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 26C611B2A27 for <ietf-announce@ietfa.amsl.com>; Thu, 3 Jul 2014 18:26:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.853
X-Spam-Level:
X-Spam-Status: No, score=-104.853 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.651, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jMqJ2UXQdzJc for <ietf-announce@ietfa.amsl.com>; Thu, 3 Jul 2014 18:26:25 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) by ietfa.amsl.com (Postfix) with ESMTP id ABFAE1B2A2F for <ietf-announce@ietf.org>; Thu, 3 Jul 2014 18:26:25 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 7F6B0180095; Thu, 3 Jul 2014 18:26:12 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 7297 on IP Connectivity Provisioning Profile (CPP)
X-PHP-Originating-Script: 6000:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20140704012612.7F6B0180095@rfc-editor.org>
Date: Thu, 03 Jul 2014 18:26:12 -0700
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf-announce/_jytprlL4ljUm8BAiyi7RyH1qKc
Cc: drafts-update-ref@iana.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: ietf@ietf.org
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 04 Jul 2014 01:26:27 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 7297

        Title:      IP Connectivity Provisioning Profile (CPP) 
        Author:     M. Boucadair, C. Jacquenet, N. Wang
        Status:     Informational
        Stream:     Independent
        Date:       July 2014
        Mailbox:    mohamed.boucadair@orange.com, 
                    christian.jacquenet@orange.com, 
                    n.wang@surrey.ac.uk
        Pages:      22
        Characters: 48281
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-boucadair-connectivity-provisioning-profile-05.txt

        URL:        http://www.rfc-editor.org/rfc/rfc7297.txt

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.


INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution of
this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see http://www.rfc-editor.org/search
For downloading RFCs, see http://www.rfc-editor.org/rfc.html

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC