Re: Moving forward with the CCAMP charter

JP Vasseur <jvasseur@cisco.com> Tue, 16 August 2005 23:39 UTC

Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1E5B1f-0003hL-A5 for ccamp-archive@megatron.ietf.org; Tue, 16 Aug 2005 19:39:23 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA21026 for <ccamp-archive@ietf.org>; Tue, 16 Aug 2005 19:39:19 -0400 (EDT)
Received: from psg.com ([147.28.0.62] ident=mailnull) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1E5Bb5-0002SZ-6q for ccamp-archive@ietf.org; Tue, 16 Aug 2005 20:16:00 -0400
Received: from majordom by psg.com with local (Exim 4.50 (FreeBSD)) id 1E5Avr-000Eca-7W for ccamp-data@psg.com; Tue, 16 Aug 2005 23:33:23 +0000
Received: from [64.102.122.149] (helo=rtp-iport-2.cisco.com) by psg.com with esmtp (Exim 4.50 (FreeBSD)) id 1E5Avq-000EcN-IW for ccamp@ops.ietf.org; Tue, 16 Aug 2005 23:33:22 +0000
Received: from rtp-core-2.cisco.com (64.102.124.13) by rtp-iport-2.cisco.com with ESMTP; 16 Aug 2005 19:32:50 -0400
X-IronPort-AV: i="3.96,114,1122868800"; d="scan'208"; a="66738785:sNHT32453664"
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com [64.102.31.12]) by rtp-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id j7GNWkQl025445; Tue, 16 Aug 2005 19:32:47 -0400 (EDT)
Received: from xfe-rtp-202.amer.cisco.com ([64.102.31.21]) by xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211); Tue, 16 Aug 2005 19:32:46 -0400
Received: from [192.168.1.102] ([10.86.242.36]) by xfe-rtp-202.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211); Tue, 16 Aug 2005 19:32:46 -0400
In-Reply-To: <01d401c5a294$477581f0$4f849ed9@Puppy>
References: <00db01c5a256$6624ebb0$4f849ed9@Puppy> <6A0BF8B4-577A-4AFC-8132-B086AC914C64@cisco.com> <01d401c5a294$477581f0$4f849ed9@Puppy>
Mime-Version: 1.0 (Apple Message framework v733)
X-Priority: 3
Content-Type: text/plain; charset="US-ASCII"; delsp="yes"; format="flowed"
Message-Id: <690B6C56-60F8-4F1F-8349-F3931878A0CA@cisco.com>
Cc: ccamp@ops.ietf.org, zinin@psg.com, 'Kireeti Kompella' <kireeti@juniper.net>
Content-Transfer-Encoding: 7bit
From: JP Vasseur <jvasseur@cisco.com>
Subject: Re: Moving forward with the CCAMP charter
Date: Tue, 16 Aug 2005 19:33:13 -0400
To: Adrian Farrel <adrian@olddog.co.uk>
X-Mailer: Apple Mail (2.733)
X-OriginalArrivalTime: 16 Aug 2005 23:32:46.0454 (UTC) FILETIME=[CEA62960:01C5A2BA]
X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on psg.com
X-Spam-Status: No, score=-2.6 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=3.0.2
Sender: owner-ccamp@ops.ietf.org
Precedence: bulk
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0ddefe323dd869ab027dbfff7eff0465
Content-Transfer-Encoding: 7bit

Hi Adrian,

On Aug 16, 2005, at 2:53 PM, Adrian Farrel wrote:

>> (1) Analysis of inter-domain issues for disjoint and protected paths
>>        - Informational I-D to close off the topic and devolve to PCE
>>        * first version of WG draft
>>        * submit for IESG review
>>
>> Could you briefly elaborate on this item ?
>>
>
> I think we have the need for an informational I-D that is a bit  
> like the
> existing inter-domain framework I-D, but that examines the more  
> complex
> question of the provisioning of disjoint and protection paths across
> domain boundaries. I am aware that there a lot of ideas out there  
> and that
> there has been a lot of research. I think we need to capture an  
> overview.
>

ok fair enough ... I'll be happy to provide my input on the topic (as  
you can imagine ;-))

> It is my (personal - not WG chair) opinion that this I-D will point  
> firmly
> at the PCE WG. But just as for single paths we discovered that  
> there are
> some (limited) scenarios for single paths where signaling is  
> suitable on
> its own, we may find some solutions for diverse and protected paths.
>
>
>> (2) May be in the same bucket as draft-ali-ccamp-mpls-graceful-
>> shutdown, you may want to add draft-leroux-ccamp-ctrl-
>> saturation-01.txt ?
>>
>
> Yes. I am inclined to add a work item for "control plane robustness".
>

Thanks.

JP.

> Adrian
>