Re: Draft L1VPN Charter

Alex Zinin <zinin@psg.com> Thu, 05 May 2005 01:09 UTC

Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA04054 for <rtg-dir-archive@ietf.org>; Wed, 4 May 2005 21:09:02 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DTV5c-0000kC-LB for rtg-dir-archive@ietf.org; Wed, 04 May 2005 21:23:44 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DTUq4-0002IG-Oe; Wed, 04 May 2005 21:07:40 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DTUq3-0002IB-QC for rtg-dir@megatron.ietf.org; Wed, 04 May 2005 21:07:39 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA03974 for <rtg-dir@ietf.org>; Wed, 4 May 2005 21:07:37 -0400 (EDT)
Received: from psg.com ([147.28.0.62] ident=mailnull) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DTV4G-0000iV-2w for rtg-dir@ietf.org; Wed, 04 May 2005 21:22:20 -0400
Received: from psg.com ([147.28.0.62] helo=[127.0.0.1]) by psg.com with esmtp (Exim 4.50 (FreeBSD)) id 1DTUq1-000Bx5-4M; Thu, 05 May 2005 01:07:37 +0000
Date: Wed, 04 May 2005 18:07:30 -0700
From: Alex Zinin <zinin@psg.com>
X-Priority: 3 (Normal)
Message-ID: <811368769.20050504180730@psg.com>
To: Dimitri.Papadimitriou@alcatel.be
In-Reply-To: <OFEB359B58.8D1D3984-ONC1256FF7.00818EF9-C1256FF7.00818FDF@netfr.alcatel.fr>
References: <OFEB359B58.8D1D3984-ONC1256FF7.00818EF9-C1256FF7.00818FDF@netfr.alcatel.fr>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.8 (/)
X-Scan-Signature: 057ebe9b96adec30a7efb2aeda4c26a4
Content-Transfer-Encoding: 7bit
Cc: Igor Bryskin <i_bryskin@yahoo.com>, Adrian Farrel <adrian@olddog.co.uk>, takeda.tomonori@lab.ntt.co.jp, Kireeti Kompella <kireeti@juniper.net>, rtg-dir@ietf.org
Subject: Re: Draft L1VPN Charter
X-BeenThere: rtg-dir@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Alex Zinin <zinin@psg.com>
List-Id: Routing Area Directorate <rtg-dir.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rtg-dir>, <mailto:rtg-dir-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rtg-dir@ietf.org>
List-Help: <mailto:rtg-dir-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rtg-dir>, <mailto:rtg-dir-request@ietf.org?subject=subscribe>
Sender: rtg-dir-bounces@ietf.org
Errors-To: rtg-dir-bounces@ietf.org
X-Spam-Score: 0.8 (/)
X-Scan-Signature: 9a2be21919e71dc6faef12b370c4ecf5
Content-Transfer-Encoding: 7bit

Hmmm... endorsement? I thought it was about cooperation, whatever that
means, no?

-- 
Alex
http://www.psg.com/~zinin

Wednesday, May 4, 2005, 4:35:09 PM, Dimitri.Papadimitriou@alcatel.be wrote:
> alex, i understand ... the reason is to be clear in terms of protocol
> work endorsement (also CCAMP WG was triggered by SG13 during Seoul
> meeting) ... but indeed worth re-explaining the rules of the game

> Alex Zinin <zinin@psg.com>
> 05/04/2005 15:48 MST
> Please respond to Alex Zinin

> To:Igor Bryskin <i_bryskin@yahoo.com>
> cc:Dimitri PAPADIMITRIOU/BE/ALCATEL@ALCATEL, Adrian Farrel
> <adrian@olddog.co.uk>, rtg-dir@ietf.org, Kireeti Kompella
> <kireeti@juniper.net>, <takeda.tomonori@lab.ntt.co.jp>
> bcc:
> Subject:Re: Draft L1VPN Charter




> Makes my skin crawl after the ITU NGN workshop earlier this week, but I can
> add that. Will have to talk to the future WG chairs to clearly explain that
> this shouldn't become a DoS...

> --
> Alex
> http://www.psg.com/~zinin

> Wednesday, May 4, 2005, 10:23:32 AM, Igor Bryskin wrote:
>> Good idea.
>> Igor

>> Dimitri.Papadimitriou@alcatel.be wrote:

>> igor, all - now that i am thinking of it there is probably a need to
>> add a sentence like "The WG will also liaise with related ITU-T SGs"
>> after "... and other WGs where necessary."

>> Igor Bryskin <i_bryskin@yahoo.com>
>> Sent by: rtg-dir-bounces@ietf.org
>> 05/04/2005 07:18 MST

>> To: Alex Zinin <zinin@psg.com>, Adrian Farrel <adrian@olddog.co.uk>,
>> Dimitri PAPADIMITRIOU/BE/ALCATEL@ALCATEL, rtg-dir@ietf.org, Kireeti
>> Kompella <kireeti@juniper.net>, takeda.tomonori@lab.ntt.co.jp
>> cc:
>> bcc:
>> Subject: Re: Draft L1VPN Charter




>> Alex, All



>> 2. Enhanced mode: the CE-PE interface provides the signaling capabilities
>> as in the Basic mode, plus permits utilization of the provider's control
>> plane for distribution of user's routing information (e.g. similar to the
>> MPLS/BGP model).

>> I'd like to replace this with:



>> 2. Enhanced mode: the CE-PE interface provides the signaling capabilities
>> as in the Basic mode, plus permits utilization of the provider's control
>> plane for distribution of user's arbitrary control plane information
>> between the VPN sites including but not limited to routing information.



>> Provider network IHMO should make no assumptions on what protocols are
>> running within VPNs. Generally speaking, a L1VPN user is not necessarily
>> GMPLS controlled network. Furthermore, even in case it does use GMPLS it
>> needs L1VPN CE-CE connections to provide (TE) links within VPNs.
>> Specifically, the User should be capable to run LMP for such links, it
>> also should be possible to establish signaling (RSVP) adjacencies between
>> their ends, etc. The bottom line is that distribution of routing
>> information between CEs IHMO is not sufficient. I believe this is
>> consistent with the requirements stated in ITU-T SG13 L1VPN documents



>> Igor





>> Alex Zinin <zinin@psg.com> wrote:

>> Folks-

>> Before we bring it to the l1vpn mailing list, I'd like to run this draft
>> by you guys for comments.