Re: [Int-area] IP Connectivity Provisioning Profile (draft-boucadair-connectivity-provisioning-profile)

<mohamed.boucadair@orange.com> Thu, 11 April 2013 08:05 UTC

Return-Path: <mohamed.boucadair@orange.com>
X-Original-To: int-area@ietfa.amsl.com
Delivered-To: int-area@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7EE3A21F8EE8 for <int-area@ietfa.amsl.com>; Thu, 11 Apr 2013 01:05:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.139
X-Spam-Level:
X-Spam-Status: No, score=-2.139 tagged_above=-999 required=5 tests=[AWL=0.109, BAYES_00=-2.599, HELO_EQ_FR=0.35, UNPARSEABLE_RELAY=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ltjUiflxYNBW for <int-area@ietfa.amsl.com>; Thu, 11 Apr 2013 01:05:58 -0700 (PDT)
Received: from relais-inet.francetelecom.com (relais-ias92.francetelecom.com [193.251.215.92]) by ietfa.amsl.com (Postfix) with ESMTP id 882B921F8EB3 for <int-area@ietf.org>; Thu, 11 Apr 2013 01:05:58 -0700 (PDT)
Received: from omfedm08.si.francetelecom.fr (unknown [xx.xx.xx.4]) by omfedm11.si.francetelecom.fr (ESMTP service) with ESMTP id 4E2DF3B48A4 for <int-area@ietf.org>; Thu, 11 Apr 2013 10:05:57 +0200 (CEST)
Received: from PUEXCH71.nanterre.francetelecom.fr (unknown [10.101.44.33]) by omfedm08.si.francetelecom.fr (ESMTP service) with ESMTP id 319B423809E for <int-area@ietf.org>; Thu, 11 Apr 2013 10:05:57 +0200 (CEST)
Received: from PUEXCB1B.nanterre.francetelecom.fr ([10.101.44.7]) by PUEXCH71.nanterre.francetelecom.fr ([10.101.44.33]) with mapi; Thu, 11 Apr 2013 10:05:53 +0200
From: mohamed.boucadair@orange.com
To: Internet Area <int-area@ietf.org>
Date: Thu, 11 Apr 2013 10:05:46 +0200
Thread-Topic: [Int-area] IP Connectivity Provisioning Profile (draft-boucadair-connectivity-provisioning-profile)
Thread-Index: Ac42i15oPQuMEMooTFCk83TaffhfiQ==
Message-ID: <94C682931C08B048B7A8645303FDC9F36EC1AE7E30@PUEXCB1B.nanterre.francetelecom.fr>
Accept-Language: fr-FR
Content-Language: fr-FR
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: fr-FR
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-PMX-Version: 5.6.1.2065439, Antispam-Engine: 2.7.2.376379, Antispam-Data: 2013.4.11.61520
Subject: Re: [Int-area] IP Connectivity Provisioning Profile (draft-boucadair-connectivity-provisioning-profile)
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF Internet Area Mailing List <int-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/int-area>, <mailto:int-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/int-area>
List-Post: <mailto:int-area@ietf.org>
List-Help: <mailto:int-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/int-area>, <mailto:int-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Apr 2013 08:05:59 -0000

Dear all,

We edited an I-D which proposes a global framework making use of the Connectivity Provisioning Profile. The document is available here:
http://tools.ietf.org/html/draft-sin-sdnrg-sdn-approach-02 

I'm sharing this information as it may be of interest of this working group.

Comments are more than welcome on both I-Ds.

Cheers,
Med

>
>On 10/12/2012 05:20 AM, mohamed.boucadair@orange.com wrote:
>> Dear all,
>> 
>> We submitted this new I-D which may be of interest of this WG. 
>> 
>> This is an effort trying to capture and expose the IP 
>connectivity service provided by the network layer to upper 
>services, to adjacent networks, offered/delivered to 
>customers, etc. The document focuses on the definition of the 
>CPP itself and does not discuss for instance how this is 
>translated into configuration data/policies to be enforced in 
>underlying nodes.
>> 
>> 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.
>> 
>> 
>https://datatracker.ietf.org/doc/draft-boucadair-connectivity-p
>rovisioning-profile
>> 
>http://tools.ietf.org/html/draft-boucadair-connectivity-provisi
>oning-profile-02
>> 
>> 
>> Comments are welcome.
>> 
>> Cheers,
>> Med