[irs-discuss] IP Connectivity Provisioning Profile (draft-boucadair-connectivity-provisioning-profile)

<mohamed.boucadair@orange.com> Fri, 19 October 2012 14:13 UTC

Return-Path: <mohamed.boucadair@orange.com>
X-Original-To: irs-discuss@ietfa.amsl.com
Delivered-To: irs-discuss@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id B884021F8200 for <irs-discuss@ietfa.amsl.com>; Fri, 19 Oct 2012 07:13:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.134
X-Spam-Status: No, score=-2.134 tagged_above=-999 required=5 tests=[AWL=0.114, BAYES_00=-2.599, HELO_EQ_FR=0.35, UNPARSEABLE_RELAY=0.001]
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id E0GyEjTJlqwg for <irs-discuss@ietfa.amsl.com>; Fri, 19 Oct 2012 07:13:35 -0700 (PDT)
Received: from relais-inet.francetelecom.com (relais-ias91.francetelecom.com []) by ietfa.amsl.com (Postfix) with ESMTP id 0C34A21F84F1 for <irs-discuss@ietf.org>; Fri, 19 Oct 2012 07:13:34 -0700 (PDT)
Received: from omfedm07.si.francetelecom.fr (unknown [xx.xx.xx.3]) by omfedm09.si.francetelecom.fr (ESMTP service) with ESMTP id 0E92F2DC448 for <irs-discuss@ietf.org>; Fri, 19 Oct 2012 16:13:34 +0200 (CEST)
Received: from PUEXCH71.nanterre.francetelecom.fr (unknown []) by omfedm07.si.francetelecom.fr (ESMTP service) with ESMTP id E90464C060 for <irs-discuss@ietf.org>; Fri, 19 Oct 2012 16:13:33 +0200 (CEST)
Received: from PUEXCB1B.nanterre.francetelecom.fr ([]) by PUEXCH71.nanterre.francetelecom.fr ([]) with mapi; Fri, 19 Oct 2012 16:13:30 +0200
From: <mohamed.boucadair@orange.com>
To: "irs-discuss@ietf.org" <irs-discuss@ietf.org>
Date: Fri, 19 Oct 2012 16:13:29 +0200
Thread-Topic: IP Connectivity Provisioning Profile (draft-boucadair-connectivity-provisioning-profile)
Thread-Index: Ac2uA+ne/ZisyYd7RFKHWY1NEq/W+Q==
Message-ID: <94C682931C08B048B7A8645303FDC9F36E6556BED6@PUEXCB1B.nanterre.francetelecom.fr>
Accept-Language: fr-FR
Content-Language: fr-FR
acceptlanguage: fr-FR
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-PMX-Version:, Antispam-Engine:, Antispam-Data: 2012.6.19.115414
Cc: JACQUENET Christian OLNC/OLN <christian.jacquenet@orange.com>
Subject: [irs-discuss] IP Connectivity Provisioning Profile (draft-boucadair-connectivity-provisioning-profile)
X-BeenThere: irs-discuss@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Interface to The Internet Routing System \(IRS\)" <irs-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/irs-discuss>, <mailto:irs-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/irs-discuss>
List-Post: <mailto:irs-discuss@ietf.org>
List-Help: <mailto:irs-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/irs-discuss>, <mailto:irs-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 19 Oct 2012 14:13:35 -0000

Dear all,
I'm sending this message to this list as I received several comments asking how to position this I-D vs. IRS. 

I thought it would be useful to have comments and feedback from this list.
   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.


Comments are welcome.