From mpls-bounces@ietf.org  Wed Oct  1 08:47:02 2008
Return-Path: <mpls-bounces@ietf.org>
X-Original-To: mpls-archive@megatron.ietf.org
Delivered-To: ietfarch-mpls-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 649DC28C0FA;
	Wed,  1 Oct 2008 08:47:02 -0700 (PDT)
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 200F93A6768
	for <mpls@core3.amsl.com>; Wed,  1 Oct 2008 08:47:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.435
X-Spam-Level: 
X-Spam-Status: No, score=-2.435 tagged_above=-999 required=5 tests=[AWL=0.164, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id V+aIVEeCpusl for <mpls@core3.amsl.com>;
	Wed,  1 Oct 2008 08:47:00 -0700 (PDT)
Received: from fg-out-1718.google.com (fg-out-1718.google.com [72.14.220.155])
	by core3.amsl.com (Postfix) with ESMTP id 0AD573A67A2
	for <mpls@ietf.org>; Wed,  1 Oct 2008 08:46:58 -0700 (PDT)
Received: by fg-out-1718.google.com with SMTP id d23so422074fga.41
	for <mpls@ietf.org>; Wed, 01 Oct 2008 08:47:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
	h=domainkey-signature:received:received:message-id:date:from:to
	:subject:cc:in-reply-to:mime-version:content-type
	:content-transfer-encoding:content-disposition:references;
	bh=veyl+4w6f0QfrANOtVR8OE3vOz9/a08WMAamCBsq2JI=;
	b=AEAE8+d3ZBCEGOsvP0j3YPwdm0bIxJQHS3ODWbbsA5sWhJEBwUGUwpG4ezk6Fx3fWq
	PQqypmM6TaUmjOc+O/gqCl5ftZWDSwt1O2hT+SbNNNClhJEfXTwOGXsfWQRdfoN124ik
	akqUPmqZB2yWAREM/0JlqSDGZROndC917CVnQ=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=message-id:date:from:to:subject:cc:in-reply-to:mime-version
	:content-type:content-transfer-encoding:content-disposition
	:references;
	b=axvIFc80OKHvm+1SZQCcZAQPR+Br1CTMxV2Yn/O2YWQZva3TCPFADn1aKLeo3xRVPN
	fjREzy45rdbKt0y4k0nmReNW30puiif+tRZbNUl8fvCSbbSLxYH0/7O57R23JZuMgOg3
	ntO5NQ8eLL5qyrj3vG3pON8hFanSlVn1LFd64=
Received: by 10.180.231.20 with SMTP id d20mr4452369bkh.11.1222876042335;
	Wed, 01 Oct 2008 08:47:22 -0700 (PDT)
Received: by 10.180.226.2 with HTTP; Wed, 1 Oct 2008 08:47:22 -0700 (PDT)
Message-ID: <77ead0ec0810010847r10efb0f0ncb4e24f5d9b4c492@mail.gmail.com>
Date: Wed, 1 Oct 2008 21:17:22 +0530
From: "Vishwas Manral" <vishwas.ietf@gmail.com>
To: "Shahram Davari" <davari@tpack.com>
In-Reply-To: <ba6305ea8b6f7b41bae8dcbb49c37c7c@mail.cph.tpack.net>
MIME-Version: 1.0
Content-Disposition: inline
References: <0458D2EE0C36744BABB36BE37805C29A029C6251@FRVELSMBS11.ad2.ad.alcatel.com>
	<ba6305ea8b6f7b41bae8dcbb49c37c7c@mail.cph.tpack.net>
Cc: "l2vpn@ietf.org" <l2vpn@ietf.org>,
	BOCCI Matthew <Matthew.Bocci@alcatel-lucent.com>,
	"mpls@ietf.org" <mpls@ietf.org>, "ccamp@ietf.org" <ccamp@ietf.org>,
	"mpls-tp@ietf.org" <mpls-tp@ietf.org>, "pwe3@ietf.org" <pwe3@ietf.org>
Subject: Re: [mpls] [PWE3] FW: Changes to PW ACH Channel Type allocation
	policy
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mpls-bounces@ietf.org
Errors-To: mpls-bounces@ietf.org

Hi Matthew,

I would like to propose another option if it is for vendor proprietery
"Channel Type" values in the ACH header. With the number of values of
the channel type being limited and the number of vendors actually a
lot, I would think something in the lines of what the draft below
talks about may make sense:

http://tools.ietf.org/draft-ietf-isis-proprietary-tlv-00

The idea is give a channel type value, for vendor specific
implemntations and further define the structure of the next header
value for such a "channel type" to actually have a Vendor OUI value.

This will allow for unlimited innovation without affecting
interoperability, unlike the other options you have mentioned.

Thanks,
Vishwas


On 10/1/08, Shahram Davari <davari@tpack.com> wrote:
> Hi Mathew,
>
> I support option 2, since a terminating node that doesn't understand the
> VCCV channel type can always drop it. This would allow more innovation and
> faster time to market.
>
> Best regards,
> Shahram
>
>
> -----Original Message-----
> From: pwe3-bounces@ietf.org [mailto:pwe3-bounces@ietf.org] On Behalf Of
> BOCCI Matthew
> Sent: September-30-08 12:23 PM
> To: pwe3@ietf.org; mpls-tp@ietf.org; mpls@ietf.org; ccamp@ietf.org;
> l2vpn@ietf.org
> Subject: [PWE3] FW: Changes to PW ACH Channel Type allocation policy
>
> The PWE3 chairs would like feedback on proposed changes to the
> allocation policy for the PW ACH codepoint registry. Please see the
> email below, and provide any feedback copying the PWE3 list.
>
> Best regards
>
> Matthew
>
> -----Original Message-----
> From: pwe3-bounces@ietf.org [mailto:pwe3-bounces@ietf.org] On Behalf Of
> BOCCI Matthew
> Sent: 25 September 2008 16:36
> To: pwe3@ietf.org
> Subject: [PWE3] Changes to PW ACH Channel Type allocation policy
>
>
>
> The current IANA allocation policy for the PW associated channel type
> registry is by IETF consensus. This policy was chosen in RFC 4385 based
> on WG consensus that since the associated channel exists in the data
> path, and VCCV packets are typically processed by the control processor
> on many PEs, it was prudent for the IETF to maintain strict control over
> what types of channels were allocated and to ensure that they complied
> to the PWE3 architecture.
>
> However, a need has been identified to provide a more flexible approach
> to allocating code points for VCCV channel types. This has partly arisen
> from the MPLS-TP work, where MPLS would be deployed in a transport
> network and where a much wider range of applications for the PW
> associated channel is envisioned, and partialy from a desire to extend
> the OAM capabilities for regular MPLS. We can support MPLS-TP and
> general MPLS apps with the current policy which requires standards
> action.
>
> However we are receiving requests to allow proprietary OAM and signaling
> protocols to be used in transport applications, and need to decide on
> the best way forward. We considered providing extension mechanisms
> within the standards track protocols, but believe that the standards
> track protocols would be much cleaner if the proprietary protocols ran
> on their own ACH code points.
>
> Note that we are talking about vendor protocols here. Other SDOs would
> be required to publish an RFC and would only be allocated an ACH through
> Standards Action.
>
> There are two ways to address the requests for proprietary protocol ACH
> code points:
>
> 1) Allow a range of the associated channel type registry to be allocated
> through expert review. Guidelines would be provided for the expert
> reviewer to guide them in assessing the request, which would have to be
> made in the form of an internet draft, while making sure that the
> request is dealt with in a timely and fair manner. This policy would
> include hurdles with regard to security, congestion etc that would be
> derived from those specified in the VCCV design.
>
> 2) Allow a range of the associated channel type registry to be allocated
> on a first-come-first-served basis. This does not provide the level of
> control that expert review provides, but this is balanced to some degree
> by the fact that the VCCV channel type is indicated in the data path,
> and so a PE can choose to discard or rate limit VCCV packets on an
> unrecognised associated channel.
>
> Any change to the ACH allocation policy would be outlined in the GE-ACH
> draft, which would update RFC 4385.
>
> We would appreciate feedback on the list as to which approach the WG
> prefers.
>
> Regards,
>
> Stewart and Matthew
>
> _______________________________________________
> pwe3 mailing list
> pwe3@ietf.org
> https://www.ietf.org/mailman/listinfo/pwe3
> _______________________________________________
> pwe3 mailing list
> pwe3@ietf.org
> https://www.ietf.org/mailman/listinfo/pwe3
>
>
>
> _______________________________________________
> pwe3 mailing list
> pwe3@ietf.org
> https://www.ietf.org/mailman/listinfo/pwe3
>
_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls


From mpls-bounces@ietf.org  Wed Oct  1 09:15:18 2008
Return-Path: <mpls-bounces@ietf.org>
X-Original-To: mpls-archive@megatron.ietf.org
Delivered-To: ietfarch-mpls-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 921133A6C38;
	Wed,  1 Oct 2008 09:15:18 -0700 (PDT)
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id BB4263A689F;
	Wed,  1 Oct 2008 09:15:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.436
X-Spam-Level: 
X-Spam-Status: No, score=-6.436 tagged_above=-999 required=5 tests=[AWL=0.163, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id f9n2o7dDaqWC; Wed,  1 Oct 2008 09:15:17 -0700 (PDT)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140])
	by core3.amsl.com (Postfix) with ESMTP id EF8D03A6C38;
	Wed,  1 Oct 2008 09:15:14 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,344,1220227200"; d="scan'208";a="21362714"
Received: from ams-dkim-2.cisco.com ([144.254.224.139])
	by ams-iport-1.cisco.com with ESMTP; 01 Oct 2008 16:12:45 +0000
Received: from ams-core-1.cisco.com (ams-core-1.cisco.com [144.254.224.150])
	by ams-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id m91GCj3h004219; 
	Wed, 1 Oct 2008 18:12:45 +0200
Received: from stewart-bryants-computer.local (dhcp-10-61-106-227.cisco.com
	[10.61.106.227])
	by ams-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m91GCjE1024837;
	Wed, 1 Oct 2008 16:12:45 GMT
Message-ID: <48E3A183.80908@cisco.com>
Date: Wed, 01 Oct 2008 17:12:51 +0100
From: Stewart Bryant <stbryant@cisco.com>
User-Agent: Thunderbird 2.0.0.16 (Macintosh/20080707)
MIME-Version: 1.0
To: Vishwas Manral <vishwas.ietf@gmail.com>
References: <0458D2EE0C36744BABB36BE37805C29A029C6251@FRVELSMBS11.ad2.ad.alcatel.com>	<ba6305ea8b6f7b41bae8dcbb49c37c7c@mail.cph.tpack.net>
	<77ead0ec0810010847r10efb0f0ncb4e24f5d9b4c492@mail.gmail.com>
In-Reply-To: <77ead0ec0810010847r10efb0f0ncb4e24f5d9b4c492@mail.gmail.com>
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1630; t=1222877565;
	x=1223741565; c=relaxed/simple; s=amsdkim2001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=stbryant@cisco.com;
	z=From:=20Stewart=20Bryant=20<stbryant@cisco.com>
	|Subject:=20Re=3A=20[mpls-tp]=20[PWE3]=20FW=3A=20Changes=20
	to=20PW=20ACH=20Channel=20Type=20allocation=0A=20policy
	|Sender:=20; bh=g9mZym05EdHo/mOUCiESy9fTVWDZvXr2hD1of7pFFlE=;
	b=jWGxhP4bxVlX6dcrKIM7k9QQODskPzJOvjRkeWR425WtBTII91k8LzbAHS
	MDz3OW56ViPc9Jvb+c6ck3lDwnx3rUAAOqOkJOpGy+JYDI/0ri7Ro8t0/rc/
	xicErkc8r9;
Authentication-Results: ams-dkim-2; header.From=stbryant@cisco.com; dkim=pass (
	sig from cisco.com/amsdkim2001 verified; ); 
Cc: "l2vpn@ietf.org" <l2vpn@ietf.org>,
	BOCCI Matthew <Matthew.Bocci@alcatel-lucent.com>,
	"mpls@ietf.org" <mpls@ietf.org>, "ccamp@ietf.org" <ccamp@ietf.org>,
	"mpls-tp@ietf.org" <mpls-tp@ietf.org>, "pwe3@ietf.org" <pwe3@ietf.org>,
	Shahram Davari <davari@tpack.com>
Subject: Re: [mpls] [mpls-tp] [PWE3] FW: Changes to PW ACH Channel Type
 allocation policy
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: stbryant@cisco.com
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: mpls-bounces@ietf.org
Errors-To: mpls-bounces@ietf.org

Vishwas Manral wrote:
> Hi Matthew,
>
> I would like to propose another option if it is for vendor proprietery
> "Channel Type" values in the ACH header. With the number of values of
> the channel type being limited and the number of vendors actually a
> lot, I would think something in the lines of what the draft below
> talks about may make sense:
>
> http://tools.ietf.org/draft-ietf-isis-proprietary-tlv-00
>
> The idea is give a channel type value, for vendor specific
> implemntations and further define the structure of the next header
> value for such a "channel type" to actually have a Vendor OUI value.
>
> This will allow for unlimited innovation without affecting
> interoperability, unlike the other options you have mentioned.
>
> Thanks,
> Vishwas
>   

Vishwas

We have 65000 units of innovation, and that is without expanding into 
the next
octet which is currently reserved for expansion.

Given that we have not yet run out of UDP ports I don't think we need to 
be concerned
in that regard.

The reason that we have been very cautious in the past is because we don't
want anything that goes on in the ACH straying into the dataplane - for
example  no one using the ACH as a PID and requiring the forwarder to look
at it.

Then when we designed VCCV we had all sorts of concerns over traffic volume
and security of traffic delivered straight to the management processor.

We were very cautious when we standardized the ACH mechanism, there is a
good case for maintaining that caution until we see what people are going
to use it for.

Stewart (speaking as myself)




_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls


From mpls-bounces@ietf.org  Wed Oct  1 10:58:51 2008
Return-Path: <mpls-bounces@ietf.org>
X-Original-To: mpls-archive@megatron.ietf.org
Delivered-To: ietfarch-mpls-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id EB4BE3A6801;
	Wed,  1 Oct 2008 10:58:50 -0700 (PDT)
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 3B3AF3A6801
	for <mpls@core3.amsl.com>; Wed,  1 Oct 2008 10:58:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.485
X-Spam-Level: 
X-Spam-Status: No, score=-2.485 tagged_above=-999 required=5 tests=[AWL=0.114, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id p2SxsEwwF2NA for <mpls@core3.amsl.com>;
	Wed,  1 Oct 2008 10:58:50 -0700 (PDT)
Received: from mail-gx0-f16.google.com (mail-gx0-f16.google.com
	[209.85.217.16])
	by core3.amsl.com (Postfix) with ESMTP id D94B13A6405
	for <mpls@ietf.org>; Wed,  1 Oct 2008 10:58:49 -0700 (PDT)
Received: by gxk9 with SMTP id 9so499805gxk.13
	for <mpls@ietf.org>; Wed, 01 Oct 2008 10:58:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
	h=domainkey-signature:received:received:message-id:date:from:to
	:subject:cc:in-reply-to:mime-version:content-type
	:content-transfer-encoding:content-disposition:references;
	bh=3U62Nx11GZerbWpbug+LVf2A7GKl9sCbvzunwQuR/5Y=;
	b=RytRoRR1RJNeXJbmtILiM9R7GDLDEo4UshIza2/27v2KZFOsg1MlQKv9QSSX+qh3/Q
	jcgUvHzQTJQ0jKFRNe70oSNTY9+jFctr/0MXr3x1waCXjK1zCwaivA79mir/MEdLMHQk
	t5SpxTYgQDzp1N5vAHmdvMOwh0zjyqyOxNsIs=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=message-id:date:from:to:subject:cc:in-reply-to:mime-version
	:content-type:content-transfer-encoding:content-disposition
	:references;
	b=L/3o3CCa460JW9QvSYK7qBQQkSYeufVyMJmgB2InBQDbqTsezyDuiHMod+5fY8C7b/
	B4foPaXviB2wA24z/r9h/WCFsVqfu/u7T7VZXkYJTmfs4COdf4AlZKAXcFjFtCCwfUBy
	JMjc/T1H1GmMu6LRWrYdmeT1xmW+sxJ91yBYE=
Received: by 10.142.72.4 with SMTP id u4mr3475299wfa.269.1222883567042;
	Wed, 01 Oct 2008 10:52:47 -0700 (PDT)
Received: by 10.142.88.14 with HTTP; Wed, 1 Oct 2008 10:52:46 -0700 (PDT)
Message-ID: <b2d141720810011052m18181d04lee3b0084e4d4f46@mail.gmail.com>
Date: Wed, 1 Oct 2008 13:52:47 -0400
From: "Andrew G. Malis" <amalis@gmail.com>
To: "Shah, Himanshu" <hshah@ciena.com>
In-Reply-To: <6535C9CED6F87446B41D20EF170F2362137AFD@mamxm01.ciena.com>
MIME-Version: 1.0
Content-Disposition: inline
References: <0458D2EE0C36744BABB36BE37805C29A029C6251@FRVELSMBS11.ad2.ad.alcatel.com>
	<6535C9CED6F87446B41D20EF170F2362137AFD@mamxm01.ciena.com>
Cc: l2vpn@ietf.org, BOCCI Matthew <Matthew.Bocci@alcatel-lucent.com>,
	mpls@ietf.org, ccamp@ietf.org, mpls-tp@ietf.org, pwe3@ietf.org
Subject: Re: [mpls] [PWE3] [mpls-tp] FW: Changes to PW ACH Channel Type
	allocationpolicy
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mpls-bounces@ietf.org
Errors-To: mpls-bounces@ietf.org

I also agree on #1.

Cheers,
Andy

On Tue, Sep 30, 2008 at 3:19 PM, Shah, Himanshu <hshah@ciena.com> wrote:
> I support proposal one - funnelling through expert review of the draft
> proposal.
> And yes turnaround must be quick...
>
> /himanshu
>
> -----Original Message-----
> From: mpls-tp-bounces@ietf.org [mailto:mpls-tp-bounces@ietf.org] On
> Behalf Of BOCCI Matthew
> Sent: Tuesday, September 30, 2008 12:23 PM
> To: pwe3@ietf.org; mpls-tp@ietf.org; mpls@ietf.org; ccamp@ietf.org;
> l2vpn@ietf.org
> Subject: [mpls-tp] FW: [PWE3] Changes to PW ACH Channel Type
> allocationpolicy
>
> The PWE3 chairs would like feedback on proposed changes to the
> allocation policy for the PW ACH codepoint registry. Please see the
> email below, and provide any feedback copying the PWE3 list.
>
> Best regards
>
> Matthew
>
> -----Original Message-----
> From: pwe3-bounces@ietf.org [mailto:pwe3-bounces@ietf.org] On Behalf Of
> BOCCI Matthew
> Sent: 25 September 2008 16:36
> To: pwe3@ietf.org
> Subject: [PWE3] Changes to PW ACH Channel Type allocation policy
>
>
>
> The current IANA allocation policy for the PW associated channel type
> registry is by IETF consensus. This policy was chosen in RFC 4385 based
> on WG consensus that since the associated channel exists in the data
> path, and VCCV packets are typically processed by the control processor
> on many PEs, it was prudent for the IETF to maintain strict control over
> what types of channels were allocated and to ensure that they complied
> to the PWE3 architecture.
>
> However, a need has been identified to provide a more flexible approach
> to allocating code points for VCCV channel types. This has partly arisen
> from the MPLS-TP work, where MPLS would be deployed in a transport
> network and where a much wider range of applications for the PW
> associated channel is envisioned, and partialy from a desire to extend
> the OAM capabilities for regular MPLS. We can support MPLS-TP and
> general MPLS apps with the current policy which requires standards
> action.
>
> However we are receiving requests to allow proprietary OAM and signaling
> protocols to be used in transport applications, and need to decide on
> the best way forward. We considered providing extension mechanisms
> within the standards track protocols, but believe that the standards
> track protocols would be much cleaner if the proprietary protocols ran
> on their own ACH code points.
>
> Note that we are talking about vendor protocols here. Other SDOs would
> be required to publish an RFC and would only be allocated an ACH through
> Standards Action.
>
> There are two ways to address the requests for proprietary protocol ACH
> code points:
>
> 1) Allow a range of the associated channel type registry to be allocated
> through expert review. Guidelines would be provided for the expert
> reviewer to guide them in assessing the request, which would have to be
> made in the form of an internet draft, while making sure that the
> request is dealt with in a timely and fair manner. This policy would
> include hurdles with regard to security, congestion etc that would be
> derived from those specified in the VCCV design.
>
> 2) Allow a range of the associated channel type registry to be allocated
> on a first-come-first-served basis. This does not provide the level of
> control that expert review provides, but this is balanced to some degree
> by the fact that the VCCV channel type is indicated in the data path,
> and so a PE can choose to discard or rate limit VCCV packets on an
> unrecognised associated channel.
>
> Any change to the ACH allocation policy would be outlined in the GE-ACH
> draft, which would update RFC 4385.
>
> We would appreciate feedback on the list as to which approach the WG
> prefers.
>
> Regards,
>
> Stewart and Matthew
>
> _______________________________________________
> pwe3 mailing list
> pwe3@ietf.org
> https://www.ietf.org/mailman/listinfo/pwe3
> _______________________________________________
> mpls-tp mailing list
> mpls-tp@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls-tp
> _______________________________________________
> pwe3 mailing list
> pwe3@ietf.org
> https://www.ietf.org/mailman/listinfo/pwe3
>
_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls


From mpls-bounces@ietf.org  Wed Oct  1 21:02:08 2008
Return-Path: <mpls-bounces@ietf.org>
X-Original-To: mpls-archive@megatron.ietf.org
Delivered-To: ietfarch-mpls-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 45E0D3A67DF;
	Wed,  1 Oct 2008 21:02:08 -0700 (PDT)
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B69993A67AF;
	Wed,  1 Oct 2008 21:02:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.117
X-Spam-Level: 
X-Spam-Status: No, score=-1.117 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, DNS_FROM_RFC_BOGUSMX=1.482]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 2gEsL85x0FgC; Wed,  1 Oct 2008 21:02:06 -0700 (PDT)
Received: from dog.tcb.net (dog.tcb.net [64.78.150.133])
	by core3.amsl.com (Postfix) with ESMTP id BB3FD3A67DF;
	Wed,  1 Oct 2008 21:02:06 -0700 (PDT)
Received: by dog.tcb.net (Postfix, from userid 0)
	id 37D2D268681; Wed,  1 Oct 2008 22:02:05 -0600 (MDT)
Received: from pmac.castlepoint.net (71-215-65-30.hlrn.qwest.net
	[71.215.65.30]) (authenticated-user smtp)
	(TLSv1/SSLv3 AES128-SHA 128/128) by dog.tcb.net with SMTP;
	Wed, 01 Oct 2008 22:02:05 -0600 (MDT)
	(envelope-from shane@castlepoint.net)
X-Avenger: version=0.7.8; receiver=dog.tcb.net; client-ip=71.215.65.30;
	client-port=2263; syn-fingerprint=65535:55:1:64:M1460,N,W3,N,N,T,S MacOS
	10.4.8; data-bytes=0
Message-Id: <639AAB99-9B29-40B1-A57D-C3476D87696C@castlepoint.net>
From: Shane Amante <shane@castlepoint.net>
To: BOCCI Matthew <Matthew.Bocci@alcatel-lucent.com>
In-Reply-To: <0458D2EE0C36744BABB36BE37805C29A029C6251@FRVELSMBS11.ad2.ad.alcatel.com>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Wed, 1 Oct 2008 22:01:48 -0600
References: <0458D2EE0C36744BABB36BE37805C29A029C6251@FRVELSMBS11.ad2.ad.alcatel.com>
X-Mailer: Apple Mail (2.929.2)
Cc: l2vpn@ietf.org, mpls@ietf.org, ccamp@ietf.org, pwe3@ietf.org,
	mpls-tp@ietf.org
Subject: Re: [mpls] [PWE3] Changes to PW ACH Channel Type allocation policy
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: mpls-bounces@ietf.org
Errors-To: mpls-bounces@ietf.org

Matthew,

Speaking as an operator, (L2VPN WG co-chair hat off), I would also  
prefer the existing mechanism that's already in place: expert review  
and IETF consensus.  After all, there are significant benefits to  
standards-based OAM and signaling protocols.  On the other hand, some  
people may still have a legitimate need to do uncommon things that  
aren't considered mainstream.  In that case, I would rather see a  
(small) subset of codepoints allocated for expert review with no IETF  
consensus (Option #1 below).

-shane


On Sep 30, 2008, at 10:23 AM, BOCCI Matthew wrote:
> The PWE3 chairs would like feedback on proposed changes to the
> allocation policy for the PW ACH codepoint registry. Please see the
> email below, and provide any feedback copying the PWE3 list.
>
> Best regards
>
> Matthew
>
> -----Original Message-----
> From: pwe3-bounces@ietf.org [mailto:pwe3-bounces@ietf.org] On Behalf  
> Of
> BOCCI Matthew
> Sent: 25 September 2008 16:36
> To: pwe3@ietf.org
> Subject: [PWE3] Changes to PW ACH Channel Type allocation policy
>
>
>
> The current IANA allocation policy for the PW associated channel type
> registry is by IETF consensus. This policy was chosen in RFC 4385  
> based
> on WG consensus that since the associated channel exists in the data
> path, and VCCV packets are typically processed by the control  
> processor
> on many PEs, it was prudent for the IETF to maintain strict control  
> over
> what types of channels were allocated and to ensure that they complied
> to the PWE3 architecture.
>
> However, a need has been identified to provide a more flexible  
> approach
> to allocating code points for VCCV channel types. This has partly  
> arisen
> from the MPLS-TP work, where MPLS would be deployed in a transport
> network and where a much wider range of applications for the PW
> associated channel is envisioned, and partialy from a desire to extend
> the OAM capabilities for regular MPLS. We can support MPLS-TP and
> general MPLS apps with the current policy which requires standards
> action.
>
> However we are receiving requests to allow proprietary OAM and  
> signaling
> protocols to be used in transport applications, and need to decide on
> the best way forward. We considered providing extension mechanisms
> within the standards track protocols, but believe that the standards
> track protocols would be much cleaner if the proprietary protocols ran
> on their own ACH code points.
>
> Note that we are talking about vendor protocols here. Other SDOs would
> be required to publish an RFC and would only be allocated an ACH  
> through
> Standards Action.
>
> There are two ways to address the requests for proprietary protocol  
> ACH
> code points:
>
> 1) Allow a range of the associated channel type registry to be  
> allocated
> through expert review. Guidelines would be provided for the expert
> reviewer to guide them in assessing the request, which would have to  
> be
> made in the form of an internet draft, while making sure that the
> request is dealt with in a timely and fair manner. This policy would
> include hurdles with regard to security, congestion etc that would be
> derived from those specified in the VCCV design.
>
> 2) Allow a range of the associated channel type registry to be  
> allocated
> on a first-come-first-served basis. This does not provide the level of
> control that expert review provides, but this is balanced to some  
> degree
> by the fact that the VCCV channel type is indicated in the data path,
> and so a PE can choose to discard or rate limit VCCV packets on an
> unrecognised associated channel.
>
> Any change to the ACH allocation policy would be outlined in the GE- 
> ACH
> draft, which would update RFC 4385.
>
> We would appreciate feedback on the list as to which approach the WG
> prefers.
>
> Regards,
>
> Stewart and Matthew
>
> _______________________________________________
> pwe3 mailing list
> pwe3@ietf.org
> https://www.ietf.org/mailman/listinfo/pwe3

_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls


From mpls-bounces@ietf.org  Thu Oct  2 00:01:17 2008
Return-Path: <mpls-bounces@ietf.org>
X-Original-To: mpls-archive@megatron.ietf.org
Delivered-To: ietfarch-mpls-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 969883A691D;
	Thu,  2 Oct 2008 00:01:17 -0700 (PDT)
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 2017D3A67B6;
	Thu,  2 Oct 2008 00:01:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.249
X-Spam-Level: 
X-Spam-Status: No, score=-2.249 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, HELO_EQ_FR=0.35]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id wFliwu8WSVK9; Thu,  2 Oct 2008 00:01:15 -0700 (PDT)
Received: from smail6.alcatel.fr (colt-na5.alcatel.fr [62.23.212.5])
	by core3.amsl.com (Postfix) with ESMTP id D85273A691D;
	Thu,  2 Oct 2008 00:01:14 -0700 (PDT)
Received: from FRVELSBHS03.ad2.ad.alcatel.com (frvelsbhs03.ad2.ad.alcatel.com
	[155.132.6.75])
	by smail6.alcatel.fr (8.13.8/8.13.8/ICT) with ESMTP id m9270ldd005024; 
	Thu, 2 Oct 2008 09:00:47 +0200
Received: from FRVELSMBS21.ad2.ad.alcatel.com ([155.132.6.55]) by
	FRVELSBHS03.ad2.ad.alcatel.com with Microsoft
	SMTPSVC(6.0.3790.2499); Thu, 2 Oct 2008 09:00:48 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Thu, 2 Oct 2008 09:00:55 +0200
Message-ID: <6FD21B53861BF44AA90A288402036AB40193F72F@FRVELSMBS21.ad2.ad.alcatel.com>
In-Reply-To: <ba6305ea8b6f7b41bae8dcbb49c37c7c@mail.cph.tpack.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [PWE3] FW:  Changes to PW ACH Channel Type allocation policy
Thread-Index: AckeEgHxlvy9zCPET0WFoA5KKm0awgBET6egAP0oyGAALpdOcAAib8Rg
References: <0458D2EE0C36744BABB36BE37805C29A029C6251@FRVELSMBS11.ad2.ad.alcatel.com>
	<ba6305ea8b6f7b41bae8dcbb49c37c7c@mail.cph.tpack.net>
From: "BUSI ITALO" <Italo.Busi@alcatel-lucent.it>
To: "Shahram Davari" <davari@tpack.com>,
	"BOCCI Matthew" <Matthew.Bocci@alcatel-lucent.com>, <pwe3@ietf.org>,
	<mpls-tp@ietf.org>, <mpls@ietf.org>, <ccamp@ietf.org>, <l2vpn@ietf.org>
X-OriginalArrivalTime: 02 Oct 2008 07:00:48.0093 (UTC)
	FILETIME=[991940D0:01C9245C]
X-Scanned-By: MIMEDefang 2.57 on 155.132.188.84
Subject: Re: [mpls] [PWE3] FW: Changes to PW ACH Channel Type allocation
	policy
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mpls-bounces@ietf.org
Errors-To: mpls-bounces@ietf.org

I also support option 2

The requirement is to allow a vendor to implement proprietary innovative
features.

Italo

> -----Original Message-----
> From: pwe3-bounces@ietf.org [mailto:pwe3-bounces@ietf.org] On 
> Behalf Of Shahram Davari
> Sent: Wednesday, October 01, 2008 4:34 PM
> To: BOCCI Matthew; pwe3@ietf.org; mpls-tp@ietf.org; 
> mpls@ietf.org; ccamp@ietf.org; l2vpn@ietf.org
> Subject: Re: [PWE3] FW: Changes to PW ACH Channel Type 
> allocation policy
> 
> Hi Mathew,
> 
> I support option 2, since a terminating node that doesn't 
> understand the VCCV channel type can always drop it. This 
> would allow more innovation and faster time to market.
> 
> Best regards,
> Shahram
> 
> 
> -----Original Message-----
> From: pwe3-bounces@ietf.org [mailto:pwe3-bounces@ietf.org] On 
> Behalf Of BOCCI Matthew
> Sent: September-30-08 12:23 PM
> To: pwe3@ietf.org; mpls-tp@ietf.org; mpls@ietf.org; 
> ccamp@ietf.org; l2vpn@ietf.org
> Subject: [PWE3] FW: Changes to PW ACH Channel Type allocation policy
> 
> The PWE3 chairs would like feedback on proposed changes to the
> allocation policy for the PW ACH codepoint registry. Please see the
> email below, and provide any feedback copying the PWE3 list.
> 
> Best regards
> 
> Matthew
> 
> -----Original Message-----
> From: pwe3-bounces@ietf.org [mailto:pwe3-bounces@ietf.org] On 
> Behalf Of
> BOCCI Matthew
> Sent: 25 September 2008 16:36
> To: pwe3@ietf.org
> Subject: [PWE3] Changes to PW ACH Channel Type allocation policy
> 
> 
>  
> The current IANA allocation policy for the PW associated channel type
> registry is by IETF consensus. This policy was chosen in RFC 
> 4385 based
> on WG consensus that since the associated channel exists in the data
> path, and VCCV packets are typically processed by the control 
> processor
> on many PEs, it was prudent for the IETF to maintain strict 
> control over
> what types of channels were allocated and to ensure that they complied
> to the PWE3 architecture.
> 
> However, a need has been identified to provide a more 
> flexible approach
> to allocating code points for VCCV channel types. This has 
> partly arisen
> from the MPLS-TP work, where MPLS would be deployed in a transport
> network and where a much wider range of applications for the PW
> associated channel is envisioned, and partialy from a desire to extend
> the OAM capabilities for regular MPLS. We can support MPLS-TP and
> general MPLS apps with the current policy which requires standards
> action.
> 
> However we are receiving requests to allow proprietary OAM 
> and signaling
> protocols to be used in transport applications, and need to decide on
> the best way forward. We considered providing extension mechanisms
> within the standards track protocols, but believe that the standards
> track protocols would be much cleaner if the proprietary protocols ran
> on their own ACH code points.
> 
> Note that we are talking about vendor protocols here. Other SDOs would
> be required to publish an RFC and would only be allocated an 
> ACH through
> Standards Action.
> 
> There are two ways to address the requests for proprietary 
> protocol ACH
> code points:
> 
> 1) Allow a range of the associated channel type registry to 
> be allocated
> through expert review. Guidelines would be provided for the expert
> reviewer to guide them in assessing the request, which would 
> have to be
> made in the form of an internet draft, while making sure that the
> request is dealt with in a timely and fair manner. This policy would
> include hurdles with regard to security, congestion etc that would be
> derived from those specified in the VCCV design.
> 
> 2) Allow a range of the associated channel type registry to 
> be allocated
> on a first-come-first-served basis. This does not provide the level of
> control that expert review provides, but this is balanced to 
> some degree
> by the fact that the VCCV channel type is indicated in the data path,
> and so a PE can choose to discard or rate limit VCCV packets on an
> unrecognised associated channel.
> 
> Any change to the ACH allocation policy would be outlined in 
> the GE-ACH
> draft, which would update RFC 4385.
> 
> We would appreciate feedback on the list as to which approach the WG
> prefers.
> 
> Regards,
> 
> Stewart and Matthew
> 
> _______________________________________________
> pwe3 mailing list
> pwe3@ietf.org
> https://www.ietf.org/mailman/listinfo/pwe3
> _______________________________________________
> pwe3 mailing list
> pwe3@ietf.org
> https://www.ietf.org/mailman/listinfo/pwe3
> 
> 
> 
> _______________________________________________
> pwe3 mailing list
> pwe3@ietf.org
> https://www.ietf.org/mailman/listinfo/pwe3
> 
_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls


From mpls-bounces@ietf.org  Thu Oct  2 00:11:43 2008
Return-Path: <mpls-bounces@ietf.org>
X-Original-To: mpls-archive@megatron.ietf.org
Delivered-To: ietfarch-mpls-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 481C93A6B00;
	Thu,  2 Oct 2008 00:11:43 -0700 (PDT)
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 23EEF3A6ACE;
	Thu,  2 Oct 2008 00:11:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.249
X-Spam-Level: 
X-Spam-Status: No, score=-2.249 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, HELO_EQ_FR=0.35]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id n9-Juz6-6Xa5; Thu,  2 Oct 2008 00:11:41 -0700 (PDT)
Received: from smail5.alcatel.fr (smail5.alcatel.fr [64.208.49.27])
	by core3.amsl.com (Postfix) with ESMTP id A756F3A677D;
	Thu,  2 Oct 2008 00:11:40 -0700 (PDT)
Received: from FRVELSBHS06.ad2.ad.alcatel.com (frvelsbhs06.ad2.ad.alcatel.com
	[155.132.6.78])
	by smail5.alcatel.fr (8.13.8/8.13.8/ICT) with ESMTP id m927BJSn012753; 
	Thu, 2 Oct 2008 09:11:19 +0200
Received: from FRVELSMBS21.ad2.ad.alcatel.com ([155.132.6.55]) by
	FRVELSBHS06.ad2.ad.alcatel.com with Microsoft
	SMTPSVC(6.0.3790.2499); Thu, 2 Oct 2008 09:11:20 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Thu, 2 Oct 2008 09:11:27 +0200
Message-ID: <6FD21B53861BF44AA90A288402036AB40193F737@FRVELSMBS21.ad2.ad.alcatel.com>
In-Reply-To: <77ead0ec0810010847r10efb0f0ncb4e24f5d9b4c492@mail.gmail.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [mpls-tp] [PWE3] FW: Changes to PW ACH Channel Type
	allocationpolicy
Thread-Index: Ackj3Q1bqBGtuyWETZaWG4drFEnw4AAf+XvQ
References: <0458D2EE0C36744BABB36BE37805C29A029C6251@FRVELSMBS11.ad2.ad.alcatel.com><ba6305ea8b6f7b41bae8dcbb49c37c7c@mail.cph.tpack.net>
	<77ead0ec0810010847r10efb0f0ncb4e24f5d9b4c492@mail.gmail.com>
From: "BUSI ITALO" <Italo.Busi@alcatel-lucent.it>
To: "Vishwas Manral" <vishwas.ietf@gmail.com>,
	"Shahram Davari" <davari@tpack.com>
X-OriginalArrivalTime: 02 Oct 2008 07:11:20.0116 (UTC)
	FILETIME=[11D04F40:01C9245E]
X-Scanned-By: MIMEDefang 2.57 on 155.132.188.13
Cc: l2vpn@ietf.org, BOCCI Matthew <Matthew.Bocci@alcatel-lucent.com>,
	mpls@ietf.org, ccamp@ietf.org, mpls-tp@ietf.org, pwe3@ietf.org
Subject: Re: [mpls] [mpls-tp] [PWE3] FW: Changes to PW ACH Channel Type
	allocationpolicy
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mpls-bounces@ietf.org
Errors-To: mpls-bounces@ietf.org

Vishwas,

I think this is a good idea

Both this proposal and option 2 (fist-come-first-served) meet the
requirements to make the ACH mechanism extensible.

The advantage of this approach is that we do not have to worry about how
many codepoints we need to allocate for proprietary extensions: we just
need one codepoint.

Italo

> -----Original Message-----
> From: mpls-tp-bounces@ietf.org 
> [mailto:mpls-tp-bounces@ietf.org] On Behalf Of Vishwas Manral
> Sent: Wednesday, October 01, 2008 5:47 PM
> To: Shahram Davari
> Cc: l2vpn@ietf.org; BOCCI Matthew; mpls@ietf.org; 
> ccamp@ietf.org; mpls-tp@ietf.org; pwe3@ietf.org
> Subject: Re: [mpls-tp] [PWE3] FW: Changes to PW ACH Channel 
> Type allocationpolicy
> 
> Hi Matthew,
> 
> I would like to propose another option if it is for vendor proprietery
> "Channel Type" values in the ACH header. With the number of values of
> the channel type being limited and the number of vendors actually a
> lot, I would think something in the lines of what the draft below
> talks about may make sense:
> 
> http://tools.ietf.org/draft-ietf-isis-proprietary-tlv-00
> 
> The idea is give a channel type value, for vendor specific
> implemntations and further define the structure of the next header
> value for such a "channel type" to actually have a Vendor OUI value.
> 
> This will allow for unlimited innovation without affecting
> interoperability, unlike the other options you have mentioned.
> 
> Thanks,
> Vishwas
> 
> 
> On 10/1/08, Shahram Davari <davari@tpack.com> wrote:
> > Hi Mathew,
> >
> > I support option 2, since a terminating node that doesn't 
> understand the
> > VCCV channel type can always drop it. This would allow more 
> innovation and
> > faster time to market.
> >
> > Best regards,
> > Shahram
> >
> >
> > -----Original Message-----
> > From: pwe3-bounces@ietf.org [mailto:pwe3-bounces@ietf.org] 
> On Behalf Of
> > BOCCI Matthew
> > Sent: September-30-08 12:23 PM
> > To: pwe3@ietf.org; mpls-tp@ietf.org; mpls@ietf.org; ccamp@ietf.org;
> > l2vpn@ietf.org
> > Subject: [PWE3] FW: Changes to PW ACH Channel Type allocation policy
> >
> > The PWE3 chairs would like feedback on proposed changes to the
> > allocation policy for the PW ACH codepoint registry. Please see the
> > email below, and provide any feedback copying the PWE3 list.
> >
> > Best regards
> >
> > Matthew
> >
> > -----Original Message-----
> > From: pwe3-bounces@ietf.org [mailto:pwe3-bounces@ietf.org] 
> On Behalf Of
> > BOCCI Matthew
> > Sent: 25 September 2008 16:36
> > To: pwe3@ietf.org
> > Subject: [PWE3] Changes to PW ACH Channel Type allocation policy
> >
> >
> >
> > The current IANA allocation policy for the PW associated 
> channel type
> > registry is by IETF consensus. This policy was chosen in 
> RFC 4385 based
> > on WG consensus that since the associated channel exists in the data
> > path, and VCCV packets are typically processed by the 
> control processor
> > on many PEs, it was prudent for the IETF to maintain strict 
> control over
> > what types of channels were allocated and to ensure that 
> they complied
> > to the PWE3 architecture.
> >
> > However, a need has been identified to provide a more 
> flexible approach
> > to allocating code points for VCCV channel types. This has 
> partly arisen
> > from the MPLS-TP work, where MPLS would be deployed in a transport
> > network and where a much wider range of applications for the PW
> > associated channel is envisioned, and partialy from a 
> desire to extend
> > the OAM capabilities for regular MPLS. We can support MPLS-TP and
> > general MPLS apps with the current policy which requires standards
> > action.
> >
> > However we are receiving requests to allow proprietary OAM 
> and signaling
> > protocols to be used in transport applications, and need to 
> decide on
> > the best way forward. We considered providing extension mechanisms
> > within the standards track protocols, but believe that the standards
> > track protocols would be much cleaner if the proprietary 
> protocols ran
> > on their own ACH code points.
> >
> > Note that we are talking about vendor protocols here. Other 
> SDOs would
> > be required to publish an RFC and would only be allocated 
> an ACH through
> > Standards Action.
> >
> > There are two ways to address the requests for proprietary 
> protocol ACH
> > code points:
> >
> > 1) Allow a range of the associated channel type registry to 
> be allocated
> > through expert review. Guidelines would be provided for the expert
> > reviewer to guide them in assessing the request, which 
> would have to be
> > made in the form of an internet draft, while making sure that the
> > request is dealt with in a timely and fair manner. This policy would
> > include hurdles with regard to security, congestion etc 
> that would be
> > derived from those specified in the VCCV design.
> >
> > 2) Allow a range of the associated channel type registry to 
> be allocated
> > on a first-come-first-served basis. This does not provide 
> the level of
> > control that expert review provides, but this is balanced 
> to some degree
> > by the fact that the VCCV channel type is indicated in the 
> data path,
> > and so a PE can choose to discard or rate limit VCCV packets on an
> > unrecognised associated channel.
> >
> > Any change to the ACH allocation policy would be outlined 
> in the GE-ACH
> > draft, which would update RFC 4385.
> >
> > We would appreciate feedback on the list as to which approach the WG
> > prefers.
> >
> > Regards,
> >
> > Stewart and Matthew
> >
> > _______________________________________________
> > pwe3 mailing list
> > pwe3@ietf.org
> > https://www.ietf.org/mailman/listinfo/pwe3
> > _______________________________________________
> > pwe3 mailing list
> > pwe3@ietf.org
> > https://www.ietf.org/mailman/listinfo/pwe3
> >
> >
> >
> > _______________________________________________
> > pwe3 mailing list
> > pwe3@ietf.org
> > https://www.ietf.org/mailman/listinfo/pwe3
> >
> _______________________________________________
> mpls-tp mailing list
> mpls-tp@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls-tp
> 
_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls


From mpls-bounces@ietf.org  Thu Oct  2 00:11:47 2008
Return-Path: <mpls-bounces@ietf.org>
X-Original-To: mpls-archive@megatron.ietf.org
Delivered-To: ietfarch-mpls-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 64C3D3A6B1A;
	Thu,  2 Oct 2008 00:11:47 -0700 (PDT)
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E54FC3A6B2A;
	Thu,  2 Oct 2008 00:11:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 8dNN2qnxNwik; Thu,  2 Oct 2008 00:11:45 -0700 (PDT)
Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117])
	by core3.amsl.com (Postfix) with ESMTP id 7A1F73A6B18;
	Thu,  2 Oct 2008 00:11:44 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,348,1220227200"; d="scan'208";a="167184173"
Received: from sj-dkim-1.cisco.com ([171.71.179.21])
	by sj-iport-6.cisco.com with ESMTP; 02 Oct 2008 07:11:27 +0000
Received: from sj-core-1.cisco.com (sj-core-1.cisco.com [171.71.177.237])
	by sj-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id m927BRIR017176; 
	Thu, 2 Oct 2008 00:11:27 -0700
Received: from stewart-bryants-computer.local (ams3-vpn-dhcp5965.cisco.com
	[10.61.87.76])
	by sj-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m927BOCv014347;
	Thu, 2 Oct 2008 07:11:25 GMT
Message-ID: <48E47400.2090309@cisco.com>
Date: Thu, 02 Oct 2008 08:10:56 +0100
From: Stewart Bryant <stbryant@cisco.com>
User-Agent: Thunderbird 2.0.0.16 (Macintosh/20080707)
MIME-Version: 1.0
To: BUSI ITALO <Italo.Busi@alcatel-lucent.it>
References: <0458D2EE0C36744BABB36BE37805C29A029C6251@FRVELSMBS11.ad2.ad.alcatel.com>	<ba6305ea8b6f7b41bae8dcbb49c37c7c@mail.cph.tpack.net>
	<6FD21B53861BF44AA90A288402036AB40193F72F@FRVELSMBS21.ad2.ad.alcatel.com>
In-Reply-To: <6FD21B53861BF44AA90A288402036AB40193F72F@FRVELSMBS21.ad2.ad.alcatel.com>
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=263; t=1222931487; x=1223795487;
	c=relaxed/simple; s=sjdkim1004;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=stbryant@cisco.com;
	z=From:=20Stewart=20Bryant=20<stbryant@cisco.com>
	|Subject:=20Re=3A=20[mpls]=20[PWE3]=20FW=3A=20Changes=20to=
	20PW=20ACH=20Channel=20Type=20allocation=09policy |Sender:=20;
	bh=pvgeNd5aukm3ecI1qgRNzO1GlTWsLanwYWJiX/bLe9o=;
	b=RIzrQPifWl6X8/8KJOBBD1igoLiZWwa/FY4Oy3w4bmnMyVhOLn2YfTQlax
	t2nkLlU2TlAG9q11WM5B8kBhXt8W+ZVafoSlRIPFifWbZMRcncIzbZy0iL5D
	aTUd4kq9Zqr9pajZQe7trTY+KLIKO7uD8iirpUv1zdXz9U/0LkH40=;
Authentication-Results: sj-dkim-1; header.From=stbryant@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim1004 verified; ); 
Cc: l2vpn@ietf.org, BOCCI Matthew <Matthew.Bocci@alcatel-lucent.com>,
	mpls@ietf.org, ccamp@ietf.org, mpls-tp@ietf.org, pwe3@ietf.org,
	Shahram Davari <davari@tpack.com>
Subject: Re: [mpls] [PWE3] FW: Changes to PW ACH Channel Type
	allocation	policy
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: stbryant@cisco.com
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: mpls-bounces@ietf.org
Errors-To: mpls-bounces@ietf.org

BUSI ITALO wrote:
> I also support option 2
>
> The requirement is to allow a vendor to implement proprietary innovative
> features.
>
> Italo
>
>   
Italo

How does option 1 prevent a vendor implementing proprietary innovative 
features?

Stewart
_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls


From mpls-bounces@ietf.org  Thu Oct  2 00:21:14 2008
Return-Path: <mpls-bounces@ietf.org>
X-Original-To: mpls-archive@megatron.ietf.org
Delivered-To: ietfarch-mpls-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 417FD28C1B6;
	Thu,  2 Oct 2008 00:21:14 -0700 (PDT)
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 57FC028C152
	for <mpls@core3.amsl.com>; Thu,  2 Oct 2008 00:21:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.47
X-Spam-Level: 
X-Spam-Status: No, score=-2.47 tagged_above=-999 required=5 tests=[AWL=0.129, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id Pu0fFsjcvdwF for <mpls@core3.amsl.com>;
	Thu,  2 Oct 2008 00:21:12 -0700 (PDT)
Received: from fg-out-1718.google.com (fg-out-1718.google.com [72.14.220.159])
	by core3.amsl.com (Postfix) with ESMTP id B6B403A63EC
	for <mpls@ietf.org>; Thu,  2 Oct 2008 00:21:11 -0700 (PDT)
Received: by fg-out-1718.google.com with SMTP id d23so640244fga.41
	for <mpls@ietf.org>; Thu, 02 Oct 2008 00:21:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
	h=domainkey-signature:received:received:message-id:date:from:to
	:subject:cc:in-reply-to:mime-version:content-type
	:content-transfer-encoding:content-disposition:references;
	bh=+WJ0gBmd03TT1U+IGlTzkNGgUl1n35g81V/kPFXHbAc=;
	b=QNjruWVpkN6Nuz4So+2dXqDs8NwOsE/uPu+vO3aCq6L012GHp1Q2U0Dpy9AxFYLwOw
	ulI2Z6LoU7bmU8mF2jUBssBLtu7kHjJ2FSnt2PDc0bm2u65l/Vc8s7f2AhULcTC/m/t8
	YSfSbcVyCpe7RhlCC0lK1hCBRd2T8tyvSghBk=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=message-id:date:from:to:subject:cc:in-reply-to:mime-version
	:content-type:content-transfer-encoding:content-disposition
	:references;
	b=M0jH/j6mMZPZGqIP1VOp/0Z1zMkn2IcIdE1po2z0WLe/x4rKmR/6APPUQ9NzWDt36c
	K39ruwMeljK02jne64VMa2bCb6CKbjP1aeQhVCocXcj8BeRR64bvuR7koawFC8k+9+9y
	stMIbeQFDbJGAjxSjyUuPl+WNrlvVG7FFgwXM=
Received: by 10.180.249.4 with SMTP id w4mr5222096bkh.79.1222932087655;
	Thu, 02 Oct 2008 00:21:27 -0700 (PDT)
Received: by 10.180.226.2 with HTTP; Thu, 2 Oct 2008 00:21:27 -0700 (PDT)
Message-ID: <77ead0ec0810020021l47d220f7n3a42651d1a17a6b4@mail.gmail.com>
Date: Thu, 2 Oct 2008 12:51:27 +0530
From: "Vishwas Manral" <vishwas.ietf@gmail.com>
To: "BUSI ITALO" <Italo.Busi@alcatel-lucent.it>
In-Reply-To: <6FD21B53861BF44AA90A288402036AB40193F737@FRVELSMBS21.ad2.ad.alcatel.com>
MIME-Version: 1.0
Content-Disposition: inline
References: <0458D2EE0C36744BABB36BE37805C29A029C6251@FRVELSMBS11.ad2.ad.alcatel.com>
	<ba6305ea8b6f7b41bae8dcbb49c37c7c@mail.cph.tpack.net>
	<77ead0ec0810010847r10efb0f0ncb4e24f5d9b4c492@mail.gmail.com>
	<6FD21B53861BF44AA90A288402036AB40193F737@FRVELSMBS21.ad2.ad.alcatel.com>
Cc: l2vpn@ietf.org, BOCCI Matthew <Matthew.Bocci@alcatel-lucent.com>,
	mpls@ietf.org, ccamp@ietf.org, mpls-tp@ietf.org, pwe3@ietf.org,
	Shahram Davari <davari@tpack.com>
Subject: Re: [mpls] [mpls-tp] [PWE3] FW: Changes to PW ACH Channel Type
	allocationpolicy
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mpls-bounces@ietf.org
Errors-To: mpls-bounces@ietf.org

Hi Italo,

I agree and that was my exact aim.

The other added advantage is that there are no interoperability issues
and no bottlenecks of assignments for a particular type.

Thanks,
Vishwas

On 10/2/08, BUSI ITALO <Italo.Busi@alcatel-lucent.it> wrote:
> Vishwas,
>
> I think this is a good idea
>
> Both this proposal and option 2 (fist-come-first-served) meet the
> requirements to make the ACH mechanism extensible.
>
> The advantage of this approach is that we do not have to worry about how
> many codepoints we need to allocate for proprietary extensions: we just
> need one codepoint.
>
> Italo
>
>> -----Original Message-----
>> From: mpls-tp-bounces@ietf.org
>> [mailto:mpls-tp-bounces@ietf.org] On Behalf Of Vishwas Manral
>> Sent: Wednesday, October 01, 2008 5:47 PM
>> To: Shahram Davari
>> Cc: l2vpn@ietf.org; BOCCI Matthew; mpls@ietf.org;
>> ccamp@ietf.org; mpls-tp@ietf.org; pwe3@ietf.org
>> Subject: Re: [mpls-tp] [PWE3] FW: Changes to PW ACH Channel
>> Type allocationpolicy
>>
>> Hi Matthew,
>>
>> I would like to propose another option if it is for vendor proprietery
>> "Channel Type" values in the ACH header. With the number of values of
>> the channel type being limited and the number of vendors actually a
>> lot, I would think something in the lines of what the draft below
>> talks about may make sense:
>>
>> http://tools.ietf.org/draft-ietf-isis-proprietary-tlv-00
>>
>> The idea is give a channel type value, for vendor specific
>> implemntations and further define the structure of the next header
>> value for such a "channel type" to actually have a Vendor OUI value.
>>
>> This will allow for unlimited innovation without affecting
>> interoperability, unlike the other options you have mentioned.
>>
>> Thanks,
>> Vishwas
>>
>>
>> On 10/1/08, Shahram Davari <davari@tpack.com> wrote:
>> > Hi Mathew,
>> >
>> > I support option 2, since a terminating node that doesn't
>> understand the
>> > VCCV channel type can always drop it. This would allow more
>> innovation and
>> > faster time to market.
>> >
>> > Best regards,
>> > Shahram
>> >
>> >
>> > -----Original Message-----
>> > From: pwe3-bounces@ietf.org [mailto:pwe3-bounces@ietf.org]
>> On Behalf Of
>> > BOCCI Matthew
>> > Sent: September-30-08 12:23 PM
>> > To: pwe3@ietf.org; mpls-tp@ietf.org; mpls@ietf.org; ccamp@ietf.org;
>> > l2vpn@ietf.org
>> > Subject: [PWE3] FW: Changes to PW ACH Channel Type allocation policy
>> >
>> > The PWE3 chairs would like feedback on proposed changes to the
>> > allocation policy for the PW ACH codepoint registry. Please see the
>> > email below, and provide any feedback copying the PWE3 list.
>> >
>> > Best regards
>> >
>> > Matthew
>> >
>> > -----Original Message-----
>> > From: pwe3-bounces@ietf.org [mailto:pwe3-bounces@ietf.org]
>> On Behalf Of
>> > BOCCI Matthew
>> > Sent: 25 September 2008 16:36
>> > To: pwe3@ietf.org
>> > Subject: [PWE3] Changes to PW ACH Channel Type allocation policy
>> >
>> >
>> >
>> > The current IANA allocation policy for the PW associated
>> channel type
>> > registry is by IETF consensus. This policy was chosen in
>> RFC 4385 based
>> > on WG consensus that since the associated channel exists in the data
>> > path, and VCCV packets are typically processed by the
>> control processor
>> > on many PEs, it was prudent for the IETF to maintain strict
>> control over
>> > what types of channels were allocated and to ensure that
>> they complied
>> > to the PWE3 architecture.
>> >
>> > However, a need has been identified to provide a more
>> flexible approach
>> > to allocating code points for VCCV channel types. This has
>> partly arisen
>> > from the MPLS-TP work, where MPLS would be deployed in a transport
>> > network and where a much wider range of applications for the PW
>> > associated channel is envisioned, and partialy from a
>> desire to extend
>> > the OAM capabilities for regular MPLS. We can support MPLS-TP and
>> > general MPLS apps with the current policy which requires standards
>> > action.
>> >
>> > However we are receiving requests to allow proprietary OAM
>> and signaling
>> > protocols to be used in transport applications, and need to
>> decide on
>> > the best way forward. We considered providing extension mechanisms
>> > within the standards track protocols, but believe that the standards
>> > track protocols would be much cleaner if the proprietary
>> protocols ran
>> > on their own ACH code points.
>> >
>> > Note that we are talking about vendor protocols here. Other
>> SDOs would
>> > be required to publish an RFC and would only be allocated
>> an ACH through
>> > Standards Action.
>> >
>> > There are two ways to address the requests for proprietary
>> protocol ACH
>> > code points:
>> >
>> > 1) Allow a range of the associated channel type registry to
>> be allocated
>> > through expert review. Guidelines would be provided for the expert
>> > reviewer to guide them in assessing the request, which
>> would have to be
>> > made in the form of an internet draft, while making sure that the
>> > request is dealt with in a timely and fair manner. This policy would
>> > include hurdles with regard to security, congestion etc
>> that would be
>> > derived from those specified in the VCCV design.
>> >
>> > 2) Allow a range of the associated channel type registry to
>> be allocated
>> > on a first-come-first-served basis. This does not provide
>> the level of
>> > control that expert review provides, but this is balanced
>> to some degree
>> > by the fact that the VCCV channel type is indicated in the
>> data path,
>> > and so a PE can choose to discard or rate limit VCCV packets on an
>> > unrecognised associated channel.
>> >
>> > Any change to the ACH allocation policy would be outlined
>> in the GE-ACH
>> > draft, which would update RFC 4385.
>> >
>> > We would appreciate feedback on the list as to which approach the WG
>> > prefers.
>> >
>> > Regards,
>> >
>> > Stewart and Matthew
>> >
>> > _______________________________________________
>> > pwe3 mailing list
>> > pwe3@ietf.org
>> > https://www.ietf.org/mailman/listinfo/pwe3
>> > _______________________________________________
>> > pwe3 mailing list
>> > pwe3@ietf.org
>> > https://www.ietf.org/mailman/listinfo/pwe3
>> >
>> >
>> >
>> > _______________________________________________
>> > pwe3 mailing list
>> > pwe3@ietf.org
>> > https://www.ietf.org/mailman/listinfo/pwe3
>> >
>> _______________________________________________
>> mpls-tp mailing list
>> mpls-tp@ietf.org
>> https://www.ietf.org/mailman/listinfo/mpls-tp
>>
>
_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls


From mpls-bounces@ietf.org  Thu Oct  2 00:52:41 2008
Return-Path: <mpls-bounces@ietf.org>
X-Original-To: mpls-archive@megatron.ietf.org
Delivered-To: ietfarch-mpls-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 18D4D3A6AE2;
	Thu,  2 Oct 2008 00:52:41 -0700 (PDT)
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B33C83A6AE8;
	Thu,  2 Oct 2008 00:52:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.43
X-Spam-Level: 
X-Spam-Status: No, score=-1.43 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, HELO_EQ_AT=0.424, HOST_EQ_AT=0.745]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id M9URTP6bIroJ; Thu,  2 Oct 2008 00:52:37 -0700 (PDT)
Received: from viefep20-int.chello.at (viefep20-int.chello.at [62.179.121.40])
	by core3.amsl.com (Postfix) with ESMTP id C887A3A677D;
	Thu,  2 Oct 2008 00:52:35 -0700 (PDT)
Received: from edge05.upc.biz ([192.168.13.212]) by viefep20-int.chello.at
	(InterMail vM.7.08.02.02 201-2186-121-104-20070414) with ESMTP
	id <20081002075210.MXFS7113.viefep20-int.chello.at@edge05.upc.biz>;
	Thu, 2 Oct 2008 09:52:10 +0200
Received: from [192.168.17.2] ([24.132.228.153]) by edge05.upc.biz with edge
	id Mjs71a00W3KDBhC05js8mk; Thu, 02 Oct 2008 09:52:10 +0200
X-SourceIP: 24.132.228.153
Message-ID: <48E47DA7.9090803@chello.nl>
Date: Thu, 02 Oct 2008 09:52:07 +0200
From: Huub van Helvoort <hhelvoort@chello.nl>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
To: Vishwas Manral <vishwas.ietf@gmail.com>
References: <0458D2EE0C36744BABB36BE37805C29A029C6251@FRVELSMBS11.ad2.ad.alcatel.com>	<ba6305ea8b6f7b41bae8dcbb49c37c7c@mail.cph.tpack.net>	<77ead0ec0810010847r10efb0f0ncb4e24f5d9b4c492@mail.gmail.com>	<6FD21B53861BF44AA90A288402036AB40193F737@FRVELSMBS21.ad2.ad.alcatel.com>
	<77ead0ec0810020021l47d220f7n3a42651d1a17a6b4@mail.gmail.com>
In-Reply-To: <77ead0ec0810020021l47d220f7n3a42651d1a17a6b4@mail.gmail.com>
Cc: l2vpn@ietf.org, mpls@ietf.org,
	BOCCI Matthew <Matthew.Bocci@alcatel-lucent.com>, ccamp@ietf.org,
	mpls-tp@ietf.org, pwe3@ietf.org, BUSI ITALO <Italo.Busi@alcatel-lucent.it>
Subject: Re: [mpls] [mpls-tp] [PWE3] FW: Changes to PW ACH Channel
	Type	allocationpolicy
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: hhelvoort@chello.nl
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: mpls-bounces@ietf.org
Errors-To: mpls-bounces@ietf.org

Hi Vishwas,

I support your proposal as well.

Your proposal is in fact in line with the way the vendor
specific codepoint is used in ITU-T Y.1731.

One of the objectives of the MPLS-TP JWT is to align with Y.1731
so this perfectly matches the objective.

Cheers, Huub.

=================================================
> Hi Italo,
> 
> I agree and that was my exact aim.
> 
> The other added advantage is that there are no interoperability issues
> and no bottlenecks of assignments for a particular type.
> 
> Thanks,
> Vishwas
> 
> On 10/2/08, BUSI ITALO <Italo.Busi@alcatel-lucent.it> wrote:
>> Vishwas,
>>
>> I think this is a good idea
>>
>> Both this proposal and option 2 (fist-come-first-served) meet the
>> requirements to make the ACH mechanism extensible.
>>
>> The advantage of this approach is that we do not have to worry about how
>> many codepoints we need to allocate for proprietary extensions: we just
>> need one codepoint.
>>
>> Italo
>>
>>> -----Original Message-----
>>> From: mpls-tp-bounces@ietf.org
>>> [mailto:mpls-tp-bounces@ietf.org] On Behalf Of Vishwas Manral
>>> Sent: Wednesday, October 01, 2008 5:47 PM
>>> To: Shahram Davari
>>> Cc: l2vpn@ietf.org; BOCCI Matthew; mpls@ietf.org;
>>> ccamp@ietf.org; mpls-tp@ietf.org; pwe3@ietf.org
>>> Subject: Re: [mpls-tp] [PWE3] FW: Changes to PW ACH Channel
>>> Type allocationpolicy
>>>
>>> Hi Matthew,
>>>
>>> I would like to propose another option if it is for vendor proprietery
>>> "Channel Type" values in the ACH header. With the number of values of
>>> the channel type being limited and the number of vendors actually a
>>> lot, I would think something in the lines of what the draft below
>>> talks about may make sense:
>>>
>>> http://tools.ietf.org/draft-ietf-isis-proprietary-tlv-00
>>>
>>> The idea is give a channel type value, for vendor specific
>>> implemntations and further define the structure of the next header
>>> value for such a "channel type" to actually have a Vendor OUI value.
>>>
>>> This will allow for unlimited innovation without affecting
>>> interoperability, unlike the other options you have mentioned.
>>>
>>> Thanks,
>>> Vishwas
>>>
>>>
>>> On 10/1/08, Shahram Davari <davari@tpack.com> wrote:
>>>> Hi Mathew,
>>>>
>>>> I support option 2, since a terminating node that doesn't
>>> understand the
>>>> VCCV channel type can always drop it. This would allow more
>>> innovation and
>>>> faster time to market.
>>>>
>>>> Best regards,
>>>> Shahram
>>>>
>>>>
>>>> -----Original Message-----
>>>> From: pwe3-bounces@ietf.org [mailto:pwe3-bounces@ietf.org]
>>> On Behalf Of
>>>> BOCCI Matthew
>>>> Sent: September-30-08 12:23 PM
>>>> To: pwe3@ietf.org; mpls-tp@ietf.org; mpls@ietf.org; ccamp@ietf.org;
>>>> l2vpn@ietf.org
>>>> Subject: [PWE3] FW: Changes to PW ACH Channel Type allocation policy
>>>>
>>>> The PWE3 chairs would like feedback on proposed changes to the
>>>> allocation policy for the PW ACH codepoint registry. Please see the
>>>> email below, and provide any feedback copying the PWE3 list.
>>>>
>>>> Best regards
>>>>
>>>> Matthew
>>>>
>>>> -----Original Message-----
>>>> From: pwe3-bounces@ietf.org [mailto:pwe3-bounces@ietf.org]
>>> On Behalf Of
>>>> BOCCI Matthew
>>>> Sent: 25 September 2008 16:36
>>>> To: pwe3@ietf.org
>>>> Subject: [PWE3] Changes to PW ACH Channel Type allocation policy
>>>>
>>>>
>>>>
>>>> The current IANA allocation policy for the PW associated
>>> channel type
>>>> registry is by IETF consensus. This policy was chosen in
>>> RFC 4385 based
>>>> on WG consensus that since the associated channel exists in the data
>>>> path, and VCCV packets are typically processed by the
>>> control processor
>>>> on many PEs, it was prudent for the IETF to maintain strict
>>> control over
>>>> what types of channels were allocated and to ensure that
>>> they complied
>>>> to the PWE3 architecture.
>>>>
>>>> However, a need has been identified to provide a more
>>> flexible approach
>>>> to allocating code points for VCCV channel types. This has
>>> partly arisen
>>>> from the MPLS-TP work, where MPLS would be deployed in a transport
>>>> network and where a much wider range of applications for the PW
>>>> associated channel is envisioned, and partialy from a
>>> desire to extend
>>>> the OAM capabilities for regular MPLS. We can support MPLS-TP and
>>>> general MPLS apps with the current policy which requires standards
>>>> action.
>>>>
>>>> However we are receiving requests to allow proprietary OAM
>>> and signaling
>>>> protocols to be used in transport applications, and need to
>>> decide on
>>>> the best way forward. We considered providing extension mechanisms
>>>> within the standards track protocols, but believe that the standards
>>>> track protocols would be much cleaner if the proprietary
>>> protocols ran
>>>> on their own ACH code points.
>>>>
>>>> Note that we are talking about vendor protocols here. Other
>>> SDOs would
>>>> be required to publish an RFC and would only be allocated
>>> an ACH through
>>>> Standards Action.
>>>>
>>>> There are two ways to address the requests for proprietary
>>> protocol ACH
>>>> code points:
>>>>
>>>> 1) Allow a range of the associated channel type registry to
>>> be allocated
>>>> through expert review. Guidelines would be provided for the expert
>>>> reviewer to guide them in assessing the request, which
>>> would have to be
>>>> made in the form of an internet draft, while making sure that the
>>>> request is dealt with in a timely and fair manner. This policy would
>>>> include hurdles with regard to security, congestion etc
>>> that would be
>>>> derived from those specified in the VCCV design.
>>>>
>>>> 2) Allow a range of the associated channel type registry to
>>> be allocated
>>>> on a first-come-first-served basis. This does not provide
>>> the level of
>>>> control that expert review provides, but this is balanced
>>> to some degree
>>>> by the fact that the VCCV channel type is indicated in the
>>> data path,
>>>> and so a PE can choose to discard or rate limit VCCV packets on an
>>>> unrecognised associated channel.
>>>>
>>>> Any change to the ACH allocation policy would be outlined
>>> in the GE-ACH
>>>> draft, which would update RFC 4385.
>>>>
>>>> We would appreciate feedback on the list as to which approach the WG
>>>> prefers.
>>>>
>>>> Regards,
>>>>
>>>> Stewart and Matthew
>>>>
>>>> _______________________________________________
>>>> pwe3 mailing list
>>>> pwe3@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/pwe3
>>>> _______________________________________________
>>>> pwe3 mailing list
>>>> pwe3@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/pwe3
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> pwe3 mailing list
>>>> pwe3@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/pwe3
>>>>
>>> _______________________________________________
>>> mpls-tp mailing list
>>> mpls-tp@ietf.org
>>> https://www.ietf.org/mailman/listinfo/mpls-tp
>>>
> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls
> 

-- 
================================================================
                   http://www.van-helvoort.eu/
================================================================
Always remember that you are unique...just like everyone else...
_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls


From mpls-bounces@ietf.org  Thu Oct  2 01:36:25 2008
Return-Path: <mpls-bounces@ietf.org>
X-Original-To: mpls-archive@megatron.ietf.org
Delivered-To: ietfarch-mpls-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id EC96828C23B;
	Thu,  2 Oct 2008 01:36:24 -0700 (PDT)
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 60E3228C23B;
	Thu,  2 Oct 2008 01:36:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.65
X-Spam-Level: 
X-Spam-Status: No, score=-2.65 tagged_above=-999 required=5 tests=[AWL=-0.051, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id eko6zx7yzASD; Thu,  2 Oct 2008 01:36:22 -0700 (PDT)
Received: from neo.viciousnest.net (neo.viciousnest.net [192.71.80.124])
	by core3.amsl.com (Postfix) with ESMTP id 2932028C20F;
	Thu,  2 Oct 2008 01:36:21 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1])
	by neo.viciousnest.net (Postfix) with ESMTP id DF26143185;
	Thu,  2 Oct 2008 10:36:12 +0200 (CEST)
Received: from neo.viciousnest.net ([127.0.0.1])
	by localhost (neo [127.0.0.1]) (amavisd-new, port 10024) with ESMTP
	id 32496-02; Thu,  2 Oct 2008 10:36:10 +0200 (CEST)
Received: from [10.4.144.123] (pat.acreo.se [217.151.195.214])
	by neo.viciousnest.net (Postfix) with ESMTP id B8E2543181;
	Thu,  2 Oct 2008 10:36:10 +0200 (CEST)
Message-ID: <48E487F8.2020700@pi.nu>
Date: Thu, 02 Oct 2008 10:36:08 +0200
From: Loa Andersson <loa@pi.nu>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
To: BOCCI Matthew <Matthew.Bocci@alcatel-lucent.com>
References: <0458D2EE0C36744BABB36BE37805C29A029C6251@FRVELSMBS11.ad2.ad.alcatel.com>
In-Reply-To: <0458D2EE0C36744BABB36BE37805C29A029C6251@FRVELSMBS11.ad2.ad.alcatel.com>
X-Enigmail-Version: 0.95.7
X-Virus-Scanned: by amavisd-new at viciousnest.net
Cc: l2vpn@ietf.org, mpls@ietf.org, ccamp@ietf.org, pwe3@ietf.org,
	mpls-tp@ietf.org
Subject: Re: [mpls] FW: [PWE3] Changes to PW ACH Channel Type allocation
	policy
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mpls-bounces@ietf.org
Errors-To: mpls-bounces@ietf.org

All,

I support option 1.

/Loa

BOCCI Matthew wrote:
> The PWE3 chairs would like feedback on proposed changes to the
> allocation policy for the PW ACH codepoint registry. Please see the
> email below, and provide any feedback copying the PWE3 list.
> 
> Best regards
> 
> Matthew
> 
> -----Original Message-----
> From: pwe3-bounces@ietf.org [mailto:pwe3-bounces@ietf.org] On Behalf Of
> BOCCI Matthew
> Sent: 25 September 2008 16:36
> To: pwe3@ietf.org
> Subject: [PWE3] Changes to PW ACH Channel Type allocation policy
> 
> 
>  
> The current IANA allocation policy for the PW associated channel type
> registry is by IETF consensus. This policy was chosen in RFC 4385 based
> on WG consensus that since the associated channel exists in the data
> path, and VCCV packets are typically processed by the control processor
> on many PEs, it was prudent for the IETF to maintain strict control over
> what types of channels were allocated and to ensure that they complied
> to the PWE3 architecture.
> 
> However, a need has been identified to provide a more flexible approach
> to allocating code points for VCCV channel types. This has partly arisen
> from the MPLS-TP work, where MPLS would be deployed in a transport
> network and where a much wider range of applications for the PW
> associated channel is envisioned, and partialy from a desire to extend
> the OAM capabilities for regular MPLS. We can support MPLS-TP and
> general MPLS apps with the current policy which requires standards
> action.
> 
> However we are receiving requests to allow proprietary OAM and signaling
> protocols to be used in transport applications, and need to decide on
> the best way forward. We considered providing extension mechanisms
> within the standards track protocols, but believe that the standards
> track protocols would be much cleaner if the proprietary protocols ran
> on their own ACH code points.
> 
> Note that we are talking about vendor protocols here. Other SDOs would
> be required to publish an RFC and would only be allocated an ACH through
> Standards Action.
> 
> There are two ways to address the requests for proprietary protocol ACH
> code points:
> 
> 1) Allow a range of the associated channel type registry to be allocated
> through expert review. Guidelines would be provided for the expert
> reviewer to guide them in assessing the request, which would have to be
> made in the form of an internet draft, while making sure that the
> request is dealt with in a timely and fair manner. This policy would
> include hurdles with regard to security, congestion etc that would be
> derived from those specified in the VCCV design.
> 
> 2) Allow a range of the associated channel type registry to be allocated
> on a first-come-first-served basis. This does not provide the level of
> control that expert review provides, but this is balanced to some degree
> by the fact that the VCCV channel type is indicated in the data path,
> and so a PE can choose to discard or rate limit VCCV packets on an
> unrecognised associated channel.
> 
> Any change to the ACH allocation policy would be outlined in the GE-ACH
> draft, which would update RFC 4385.
> 
> We would appreciate feedback on the list as to which approach the WG
> prefers.
> 
> Regards,
> 
> Stewart and Matthew
> 
> _______________________________________________
> pwe3 mailing list
> pwe3@ietf.org
> https://www.ietf.org/mailman/listinfo/pwe3
> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls


-- 
Loa Andersson

Principal Networking Architect
Acreo AB                           phone:  +46 8 632 77 14
Isafjordsgatan 22                  mobile: +46 739 81 21 64
Kista, Sweden                      email:  loa.andersson@acreo.se
                                           loa@pi.nu
_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls


From mpls-bounces@ietf.org  Thu Oct  2 06:54:58 2008
Return-Path: <mpls-bounces@ietf.org>
X-Original-To: mpls-archive@megatron.ietf.org
Delivered-To: ietfarch-mpls-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B4A5428C212;
	Thu,  2 Oct 2008 06:54:58 -0700 (PDT)
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E067B3A6AE2;
	Thu,  2 Oct 2008 06:54:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.209
X-Spam-Level: 
X-Spam-Status: No, score=-106.209 tagged_above=-999 required=5
	tests=[AWL=0.391, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4,
	USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id PSIx6l7EOmAM; Thu,  2 Oct 2008 06:54:52 -0700 (PDT)
Received: from mail121.messagelabs.com (mail121.messagelabs.com
	[216.82.245.115])
	by core3.amsl.com (Postfix) with ESMTP id 1D3B728C13E;
	Thu,  2 Oct 2008 06:54:52 -0700 (PDT)
X-VirusChecked: Checked
X-Env-Sender: dbrungard@att.com
X-Msg-Ref: server-14.tower-121.messagelabs.com!1222955663!24373905!1
X-StarScan-Version: 5.5.12.14.2; banners=-,-,-
X-Originating-IP: [144.160.20.54]
Received: (qmail 24754 invoked from network); 2 Oct 2008 13:54:23 -0000
Received: from sbcsmtp7.sbc.com (HELO mlpi135.enaf.sfdc.sbc.com)
	(144.160.20.54)
	by server-14.tower-121.messagelabs.com with AES256-SHA encrypted SMTP;
	2 Oct 2008 13:54:23 -0000
Received: from enaf.sfdc.sbc.com (localhost.localdomain [127.0.0.1])
	by mlpi135.enaf.sfdc.sbc.com (8.14.0/8.14.0) with ESMTP id
	m92DsN53002414; Thu, 2 Oct 2008 09:54:23 -0400
Received: from gaalpa1msgusr7e.ugd.att.com (gaalpa1msgusr7e.ugd.att.com
	[135.53.26.19])
	by mlpi135.enaf.sfdc.sbc.com (8.14.0/8.14.0) with ESMTP id
	m92DsGLY002371; Thu, 2 Oct 2008 09:54:18 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Thu, 2 Oct 2008 09:53:30 -0400
Message-ID: <D6CB948F7AFD6F4881D4B4F80C8509AA01208045@gaalpa1msgusr7e.ugd.att.com>
In-Reply-To: <639AAB99-9B29-40B1-A57D-C3476D87696C@castlepoint.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [mpls] [PWE3] Changes to PW ACH Channel Type allocation policy
Thread-Index: AckkQ71IH8+xzlBPTXyZ2QuPfVC+nQAT4P0w
References: <0458D2EE0C36744BABB36BE37805C29A029C6251@FRVELSMBS11.ad2.ad.alcatel.com>
	<639AAB99-9B29-40B1-A57D-C3476D87696C@castlepoint.net>
From: "BRUNGARD, DEBORAH A, ATTLABS" <dbrungard@att.com>
To: "Shane Amante" <shane@castlepoint.net>,
	"BOCCI Matthew" <Matthew.Bocci@alcatel-lucent.com>
Cc: l2vpn@ietf.org, mpls@ietf.org, ccamp@ietf.org, pwe3@ietf.org,
	mpls-tp@ietf.org
Subject: Re: [mpls] [PWE3] Changes to PW ACH Channel Type allocation policy
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mpls-bounces@ietf.org
Errors-To: mpls-bounces@ietf.org

Agree- and with the strong wording that option #1 is not for
SDOs/Forums. Option 2 (or the 3rd option being discussed), may be viewed
as no bottleneck for vendors on development of proprietary options, but
for operators, it will be an interoperability nightmare.
Deborah  

-----Original Message-----
From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf Of
Shane Amante
Sent: Thursday, October 02, 2008 12:02 AM
To: BOCCI Matthew
Cc: l2vpn@ietf.org; mpls@ietf.org; ccamp@ietf.org; pwe3@ietf.org;
mpls-tp@ietf.org
Subject: Re: [mpls] [PWE3] Changes to PW ACH Channel Type allocation
policy

Matthew,

Speaking as an operator, (L2VPN WG co-chair hat off), I would also  
prefer the existing mechanism that's already in place: expert review  
and IETF consensus.  After all, there are significant benefits to  
standards-based OAM and signaling protocols.  On the other hand, some  
people may still have a legitimate need to do uncommon things that  
aren't considered mainstream.  In that case, I would rather see a  
(small) subset of codepoints allocated for expert review with no IETF  
consensus (Option #1 below).

-shane


On Sep 30, 2008, at 10:23 AM, BOCCI Matthew wrote:
> The PWE3 chairs would like feedback on proposed changes to the
> allocation policy for the PW ACH codepoint registry. Please see the
> email below, and provide any feedback copying the PWE3 list.
>
> Best regards
>
> Matthew
>
> -----Original Message-----
> From: pwe3-bounces@ietf.org [mailto:pwe3-bounces@ietf.org] On Behalf  
> Of
> BOCCI Matthew
> Sent: 25 September 2008 16:36
> To: pwe3@ietf.org
> Subject: [PWE3] Changes to PW ACH Channel Type allocation policy
>
>
>
> The current IANA allocation policy for the PW associated channel type
> registry is by IETF consensus. This policy was chosen in RFC 4385  
> based
> on WG consensus that since the associated channel exists in the data
> path, and VCCV packets are typically processed by the control  
> processor
> on many PEs, it was prudent for the IETF to maintain strict control  
> over
> what types of channels were allocated and to ensure that they complied
> to the PWE3 architecture.
>
> However, a need has been identified to provide a more flexible  
> approach
> to allocating code points for VCCV channel types. This has partly  
> arisen
> from the MPLS-TP work, where MPLS would be deployed in a transport
> network and where a much wider range of applications for the PW
> associated channel is envisioned, and partialy from a desire to extend
> the OAM capabilities for regular MPLS. We can support MPLS-TP and
> general MPLS apps with the current policy which requires standards
> action.
>
> However we are receiving requests to allow proprietary OAM and  
> signaling
> protocols to be used in transport applications, and need to decide on
> the best way forward. We considered providing extension mechanisms
> within the standards track protocols, but believe that the standards
> track protocols would be much cleaner if the proprietary protocols ran
> on their own ACH code points.
>
> Note that we are talking about vendor protocols here. Other SDOs would
> be required to publish an RFC and would only be allocated an ACH  
> through
> Standards Action.
>
> There are two ways to address the requests for proprietary protocol  
> ACH
> code points:
>
> 1) Allow a range of the associated channel type registry to be  
> allocated
> through expert review. Guidelines would be provided for the expert
> reviewer to guide them in assessing the request, which would have to  
> be
> made in the form of an internet draft, while making sure that the
> request is dealt with in a timely and fair manner. This policy would
> include hurdles with regard to security, congestion etc that would be
> derived from those specified in the VCCV design.
>
> 2) Allow a range of the associated channel type registry to be  
> allocated
> on a first-come-first-served basis. This does not provide the level of
> control that expert review provides, but this is balanced to some  
> degree
> by the fact that the VCCV channel type is indicated in the data path,
> and so a PE can choose to discard or rate limit VCCV packets on an
> unrecognised associated channel.
>
> Any change to the ACH allocation policy would be outlined in the GE- 
> ACH
> draft, which would update RFC 4385.
>
> We would appreciate feedback on the list as to which approach the WG
> prefers.
>
> Regards,
>
> Stewart and Matthew
>
> _______________________________________________
> pwe3 mailing list
> pwe3@ietf.org
> https://www.ietf.org/mailman/listinfo/pwe3

_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls
_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls


From mpls-bounces@ietf.org  Thu Oct  2 07:43:49 2008
Return-Path: <mpls-bounces@ietf.org>
X-Original-To: mpls-archive@megatron.ietf.org
Delivered-To: ietfarch-mpls-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E11EC28C107;
	Thu,  2 Oct 2008 07:43:48 -0700 (PDT)
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id DBC823A6881;
	Thu,  2 Oct 2008 07:43:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.117
X-Spam-Level: 
X-Spam-Status: No, score=-1.117 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, DNS_FROM_RFC_BOGUSMX=1.482]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id P1uclxd7ZCmH; Thu,  2 Oct 2008 07:43:47 -0700 (PDT)
Received: from dog.tcb.net (dog.tcb.net [64.78.150.133])
	by core3.amsl.com (Postfix) with ESMTP id EC2D13A67E4;
	Thu,  2 Oct 2008 07:43:46 -0700 (PDT)
Received: by dog.tcb.net (Postfix, from userid 0)
	id E862D268680; Thu,  2 Oct 2008 08:43:28 -0600 (MDT)
Received: from [127.0.0.1] (dog.tcb.net [64.78.150.133])
	(authenticated-user smtp) (TLSv1/SSLv3 DHE-RSA-AES256-SHA 256/256)
	by dog.tcb.net with SMTP; Thu, 02 Oct 2008 08:43:28 -0600 (MDT)
	(envelope-from shane@castlepoint.net)
X-Avenger: version=0.7.8; receiver=dog.tcb.net; client-ip=64.78.150.133;
	client-port=50577; data-bytes=0
Message-ID: <48E4DE0F.9020704@castlepoint.net>
Date: Thu, 02 Oct 2008 08:43:27 -0600
From: Shane Amante <shane@castlepoint.net>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
To: Shahram Davari <davari@tpack.com>
References: <57ab175fd1b5f945afa7bc60dde31075@mail.cph.tpack.net>
In-Reply-To: <57ab175fd1b5f945afa7bc60dde31075@mail.cph.tpack.net>
Cc: "l2vpn@ietf.org" <l2vpn@ietf.org>, "mpls@ietf.org" <mpls@ietf.org>,
	BOCCI Matthew <Matthew.Bocci@alcatel-lucent.com>,
	"ccamp@ietf.org" <ccamp@ietf.org>, "mpls-tp@ietf.org" <mpls-tp@ietf.org>,
	"pwe3@ietf.org" <pwe3@ietf.org>, BUSI ITALO <Italo.Busi@alcatel-lucent.it>
Subject: Re: [mpls] [mpls-tp] [PWE3] FW: Changes to PW ACH Channel
	Type	allocationpolicy
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: mpls-bounces@ietf.org
Errors-To: mpls-bounces@ietf.org

Shahram Davari wrote:
> Hi,
> 
> I also prefer the method that Wishwas proposed. This has many advantages:
> 
> 1) Allows vendors to not expose their proprietary techniques to their competitors. 

 From the POV of an operator, this is actually a substantial disadvantage.


> 2) reduces the load of reviewing by IETF and PWE3 

OTOH, the benefit of such reviews by the IETF and PWE3 is when 
"commonality" among similar applications are discovered they can be 
standardized, rather kept proprietary.


> 3) results a faster time to market, since no expert review will be needed

True, to some extent.  But, IMHO, I would much rather see a *slightly* 
slower process involving a careful expert review and/or IETF consensus 
to make sure we're not: a) unnecessarily duplicating work; and, b) at 
the same time, encouraging more standards-based approach.


> 4) provides more codepoint space that the ACH channel type

This is false.  There is no shortage on ACH channel types today.


> 5) only one VCCV ACH channel type needs to be configured in each box for vendor specific filtering
 >
> The 2nd method has the first 3 advantages only, and the first method has none of these advantages.


Also, let's take a step back here.  Wasn't the whole point with the 
joint ITU-T/IETF effort surrounding MPLS-TP to create an environment in 
which MPLS-TP could seamlessly interoperate within (existing) MPLS 
environments?  I thought a fundamental part of that work is striving 
towards creating a *standards-based* MPLS-TP data-plane, OAM, signaling, 
etc. mechanisms.  IMO, Vishwas' proposal and Matthew's proposal #2 seems 
to run contrary to that goal.

-shane (speaking only for himself, not as co-chair)
_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls


From mpls-bounces@ietf.org  Thu Oct  2 08:13:12 2008
Return-Path: <mpls-bounces@ietf.org>
X-Original-To: mpls-archive@megatron.ietf.org
Delivered-To: ietfarch-mpls-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 4E44228C1C8;
	Thu,  2 Oct 2008 08:13:12 -0700 (PDT)
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id A162B28C1CA
	for <mpls@core3.amsl.com>; Thu,  2 Oct 2008 08:13:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.265
X-Spam-Level: 
X-Spam-Status: No, score=-2.265 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id qv55hjvoI-sR for <mpls@core3.amsl.com>;
	Thu,  2 Oct 2008 08:13:09 -0700 (PDT)
Received: from outbound-mail-26.bluehost.com (outbound-mail-26.bluehost.com
	[69.89.17.191]) by core3.amsl.com (Postfix) with SMTP id D41403A69CD
	for <mpls@ietf.org>; Thu,  2 Oct 2008 08:13:09 -0700 (PDT)
Received: (qmail 16851 invoked by uid 0); 2 Oct 2008 15:13:06 -0000
Received: from unknown (HELO box474.bluehost.com) (74.220.219.74)
	by outboundproxy2.bluehost.com with SMTP; 2 Oct 2008 15:13:06 -0000
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=labn.net;
	h=Received:X-Mailer:Date:To:From:Subject:Cc:In-Reply-To:References:Mime-Version:Content-Type:X-Identified-User;
	b=hyEUrTWEuyrPq++fgB9a5qtEkm+vByP5zFTGNCTAmZp6jqpZtMKde702ZK3iR0AqLMVc89/QdvndsMFUCnikDq29bDQzZxyO31mJnvJRBQb3KdrROcjBQJhzUJdbZ+DH;
Received: from box474.bluehost.com ([74.220.219.74] helo=LC2.labn.net)
	by box474.bluehost.com with esmtpa (Exim 4.69)
	(envelope-from <lberger@labn.net>)
	id 1KlPrY-0002eK-AU; Thu, 02 Oct 2008 09:13:08 -0600
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Thu, 02 Oct 2008 11:13:02 -0400
To: Shane Amante <shane@castlepoint.net>
From: Lou Berger <lberger@labn.net>
In-Reply-To: <48E4DE0F.9020704@castlepoint.net>
References: <57ab175fd1b5f945afa7bc60dde31075@mail.cph.tpack.net>
	<48E4DE0F.9020704@castlepoint.net>
Mime-Version: 1.0
X-Identified-User: {2629:box474.bluehost.com:labnmobi:labn.net} {sentby:smtp
	auth 74.220.219.74 authed with lberger@labn.net}
Message-Id: <20081002151309.D41403A69CD@core3.amsl.com>
Cc: "l2vpn@ietf.org" <l2vpn@ietf.org>, "mpls@ietf.org" <mpls@ietf.org>,
	BOCCI Matthew <Matthew.Bocci@alcatel-lucent.com>,
	"ccamp@ietf.org" <ccamp@ietf.org>, "mpls-tp@ietf.org" <mpls-tp@ietf.org>,
	"pwe3@ietf.org" <pwe3@ietf.org>, Shahram Davari <davari@tpack.com>,
	BUSI ITALO <Italo.Busi@alcatel-lucent.it>
Subject: Re: [mpls] [mpls-tp] [PWE3] FW: Changes to PW ACH Channel
 Type	allocationpolicy
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: mpls-bounces@ietf.org
Errors-To: mpls-bounces@ietf.org

Shane,
         Your comments make a lot of sense to me.  Particularly your 
last point.

Lou

At 10:43 AM 10/2/2008, Shane Amante wrote:
>Shahram Davari wrote:
>>Hi,
>>I also prefer the method that Wishwas proposed. This has many advantages:
>>1) Allows vendors to not expose their proprietary techniques to 
>>their competitors.
>
> From the POV of an operator, this is actually a substantial disadvantage.
>
>
>>2) reduces the load of reviewing by IETF and PWE3
>
>OTOH, the benefit of such reviews by the IETF and PWE3 is when 
>"commonality" among similar applications are discovered they can be 
>standardized, rather kept proprietary.
>
>
>>3) results a faster time to market, since no expert review will be needed
>
>True, to some extent.  But, IMHO, I would much rather see a 
>*slightly* slower process involving a careful expert review and/or 
>IETF consensus to make sure we're not: a) unnecessarily duplicating 
>work; and, b) at the same time, encouraging more standards-based approach.
>
>
>>4) provides more codepoint space that the ACH channel type
>
>This is false.  There is no shortage on ACH channel types today.
>
>
>>5) only one VCCV ACH channel type needs to be configured in each 
>>box for vendor specific filtering
> >
>>The 2nd method has the first 3 advantages only, and the first 
>>method has none of these advantages.
>
>
>Also, let's take a step back here.  Wasn't the whole point with the 
>joint ITU-T/IETF effort surrounding MPLS-TP to create an environment 
>in which MPLS-TP could seamlessly interoperate within (existing) 
>MPLS environments?  I thought a fundamental part of that work is 
>striving towards creating a *standards-based* MPLS-TP data-plane, 
>OAM, signaling, etc. mechanisms.  IMO, Vishwas' proposal and 
>Matthew's proposal #2 seems to run contrary to that goal.
>
>-shane (speaking only for himself, not as co-chair)
>_______________________________________________
>mpls mailing list
>mpls@ietf.org
>https://www.ietf.org/mailman/listinfo/mpls
>

_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls


From mpls-bounces@ietf.org  Thu Oct  2 08:19:24 2008
Return-Path: <mpls-bounces@ietf.org>
X-Original-To: mpls-archive@megatron.ietf.org
Delivered-To: ietfarch-mpls-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 67CB13A6946;
	Thu,  2 Oct 2008 08:19:24 -0700 (PDT)
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 15F253A6946;
	Thu,  2 Oct 2008 08:19:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.249
X-Spam-Level: 
X-Spam-Status: No, score=-3.249 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, HELO_EQ_FR=0.35, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 6Sv1dXPq0v96; Thu,  2 Oct 2008 08:19:17 -0700 (PDT)
Received: from p-mail2.rd.francetelecom.com (p-mail2.rd.francetelecom.com
	[195.101.245.16])
	by core3.amsl.com (Postfix) with ESMTP id 573683A67E4;
	Thu,  2 Oct 2008 08:19:15 -0700 (PDT)
Received: from FTRDMEL2.rd.francetelecom.fr ([10.193.117.153]) by
	ftrdsmtp1.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 2 Oct 2008 17:18:17 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Thu, 2 Oct 2008 17:18:17 +0200
Message-ID: <7DBAFEC6A76F3E42817DF1EBE64CB02605E3E1D2@ftrdmel2>
In-Reply-To: <D6CB948F7AFD6F4881D4B4F80C8509AA01208045@gaalpa1msgusr7e.ugd.att.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [mpls-tp] [mpls] [PWE3] Changes to PW ACH Channel Typeallocation
	policy
Thread-Index: AckkQ71IH8+xzlBPTXyZ2QuPfVC+nQAT4P0wAAFwrKA=
References: <0458D2EE0C36744BABB36BE37805C29A029C6251@FRVELSMBS11.ad2.ad.alcatel.com><639AAB99-9B29-40B1-A57D-C3476D87696C@castlepoint.net>
	<D6CB948F7AFD6F4881D4B4F80C8509AA01208045@gaalpa1msgusr7e.ugd.att.com>
From: <julien.meuric@orange-ftgroup.com>
To: <dbrungard@att.com>, <shane@castlepoint.net>,
	<Matthew.Bocci@alcatel-lucent.com>
X-OriginalArrivalTime: 02 Oct 2008 15:18:17.0996 (UTC)
	FILETIME=[1906FCC0:01C924A2]
Cc: l2vpn@ietf.org, mpls@ietf.org, ccamp@ietf.org, pwe3@ietf.org,
	mpls-tp@ietf.org
Subject: Re: [mpls] [mpls-tp] [PWE3] Changes to PW ACH Channel
	Typeallocation policy
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mpls-bounces@ietf.org
Errors-To: mpls-bounces@ietf.org

Hi.

I must agree with Deborah and Shane.

Option #3 hides the complexity behind a (useless) hierarchy and is
clearly not desired. Option #2 would create an explicit non standard
range and is not what we expect from the IETF.
As a result, since changing the former process seems already committed,
option #1 remains the better compromise.

Regards,

Julien


-----Original Message-----
From: mpls-tp-bounces@ietf.org [mailto:mpls-tp-bounces@ietf.org] On
Behalf Of BRUNGARD, DEBORAH A, ATTLABS

Agree- and with the strong wording that option #1 is not for
SDOs/Forums. Option 2 (or the 3rd option being discussed), may be viewed
as no bottleneck for vendors on development of proprietary options, but
for operators, it will be an interoperability nightmare.
Deborah  

-----Original Message-----
From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf Of
Shane Amante

Matthew,

Speaking as an operator, (L2VPN WG co-chair hat off), I would also  
prefer the existing mechanism that's already in place: expert review  
and IETF consensus.  After all, there are significant benefits to  
standards-based OAM and signaling protocols.  On the other hand, some  
people may still have a legitimate need to do uncommon things that  
aren't considered mainstream.  In that case, I would rather see a  
(small) subset of codepoints allocated for expert review with no IETF  
consensus (Option #1 below).

-shane


On Sep 30, 2008, at 10:23 AM, BOCCI Matthew wrote:
> The PWE3 chairs would like feedback on proposed changes to the
> allocation policy for the PW ACH codepoint registry. Please see the
> email below, and provide any feedback copying the PWE3 list.
>
> Best regards
>
> Matthew
>
> -----Original Message-----
> From: pwe3-bounces@ietf.org [mailto:pwe3-bounces@ietf.org] On Behalf  
> Of
> BOCCI Matthew
>
> The current IANA allocation policy for the PW associated channel type
> registry is by IETF consensus. This policy was chosen in RFC 4385  
> based
> on WG consensus that since the associated channel exists in the data
> path, and VCCV packets are typically processed by the control  
> processor
> on many PEs, it was prudent for the IETF to maintain strict control  
> over
> what types of channels were allocated and to ensure that they complied
> to the PWE3 architecture.
>
> However, a need has been identified to provide a more flexible  
> approach
> to allocating code points for VCCV channel types. This has partly  
> arisen
> from the MPLS-TP work, where MPLS would be deployed in a transport
> network and where a much wider range of applications for the PW
> associated channel is envisioned, and partialy from a desire to extend
> the OAM capabilities for regular MPLS. We can support MPLS-TP and
> general MPLS apps with the current policy which requires standards
> action.
>
> However we are receiving requests to allow proprietary OAM and  
> signaling
> protocols to be used in transport applications, and need to decide on
> the best way forward. We considered providing extension mechanisms
> within the standards track protocols, but believe that the standards
> track protocols would be much cleaner if the proprietary protocols ran
> on their own ACH code points.
>
> Note that we are talking about vendor protocols here. Other SDOs would
> be required to publish an RFC and would only be allocated an ACH  
> through
> Standards Action.
>
> There are two ways to address the requests for proprietary protocol  
> ACH
> code points:
>
> 1) Allow a range of the associated channel type registry to be  
> allocated
> through expert review. Guidelines would be provided for the expert
> reviewer to guide them in assessing the request, which would have to  
> be
> made in the form of an internet draft, while making sure that the
> request is dealt with in a timely and fair manner. This policy would
> include hurdles with regard to security, congestion etc that would be
> derived from those specified in the VCCV design.
>
> 2) Allow a range of the associated channel type registry to be  
> allocated
> on a first-come-first-served basis. This does not provide the level of
> control that expert review provides, but this is balanced to some  
> degree
> by the fact that the VCCV channel type is indicated in the data path,
> and so a PE can choose to discard or rate limit VCCV packets on an
> unrecognised associated channel.
>
> Any change to the ACH allocation policy would be outlined in the GE- 
> ACH
> draft, which would update RFC 4385.
>
> We would appreciate feedback on the list as to which approach the WG
> prefers.
>
> Regards,
>
> Stewart and Matthew
>
> _______________________________________________
> pwe3 mailing list
> pwe3@ietf.org
> https://www.ietf.org/mailman/listinfo/pwe3

_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls
_______________________________________________
mpls-tp mailing list
mpls-tp@ietf.org
https://www.ietf.org/mailman/listinfo/mpls-tp
_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls


From mpls-bounces@ietf.org  Thu Oct  2 08:21:57 2008
Return-Path: <mpls-bounces@ietf.org>
X-Original-To: mpls-archive@megatron.ietf.org
Delivered-To: ietfarch-mpls-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 29CEA28C21A;
	Thu,  2 Oct 2008 08:21:57 -0700 (PDT)
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 6470C28C1E4;
	Thu,  2 Oct 2008 08:21:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.636
X-Spam-Level: 
X-Spam-Status: No, score=-2.636 tagged_above=-999 required=5
	tests=[AWL=-0.036, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id vjR+6iLl3wab; Thu,  2 Oct 2008 08:21:54 -0700 (PDT)
Received: from neo.viciousnest.net (neo.viciousnest.net [192.71.80.124])
	by core3.amsl.com (Postfix) with ESMTP id E3E653A6A27;
	Thu,  2 Oct 2008 08:21:53 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1])
	by neo.viciousnest.net (Postfix) with ESMTP id 52E0343189;
	Thu,  2 Oct 2008 17:21:33 +0200 (CEST)
Received: from neo.viciousnest.net ([127.0.0.1])
	by localhost (neo [127.0.0.1]) (amavisd-new, port 10024) with ESMTP
	id 03904-02; Thu,  2 Oct 2008 17:21:28 +0200 (CEST)
Received: from [10.4.144.123] (pat.acreo.se [217.151.195.214])
	by neo.viciousnest.net (Postfix) with ESMTP id 38F6243186;
	Thu,  2 Oct 2008 17:21:28 +0200 (CEST)
Message-ID: <48E4E6F4.7030203@pi.nu>
Date: Thu, 02 Oct 2008 17:21:24 +0200
From: Loa Andersson <loa@pi.nu>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
To: Shane Amante <shane@castlepoint.net>
References: <57ab175fd1b5f945afa7bc60dde31075@mail.cph.tpack.net>
	<48E4DE0F.9020704@castlepoint.net>
In-Reply-To: <48E4DE0F.9020704@castlepoint.net>
X-Enigmail-Version: 0.95.7
X-Virus-Scanned: by amavisd-new at viciousnest.net
Cc: "l2vpn@ietf.org" <l2vpn@ietf.org>, "mpls@ietf.org" <mpls@ietf.org>,
	BOCCI Matthew <Matthew.Bocci@alcatel-lucent.com>,
	"ccamp@ietf.org" <ccamp@ietf.org>, "mpls-tp@ietf.org" <mpls-tp@ietf.org>,
	"pwe3@ietf.org" <pwe3@ietf.org>, Shahram Davari <davari@tpack.com>,
	BUSI ITALO <Italo.Busi@alcatel-lucent.it>
Subject: Re: [mpls] [PWE3] [mpls-tp] FW: Changes to PW ACH
	Channel	Type	allocationpolicy
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mpls-bounces@ietf.org
Errors-To: mpls-bounces@ietf.org

<chair hat off>

makes great sense, thanks Shane!

</chair hat off>

/Loa

Shane Amante wrote:
> Shahram Davari wrote:
>> Hi,
>>
>> I also prefer the method that Wishwas proposed. This has many advantages:
>>
>> 1) Allows vendors to not expose their proprietary techniques to their
>> competitors. 
> 
> From the POV of an operator, this is actually a substantial disadvantage.
> 
> 
>> 2) reduces the load of reviewing by IETF and PWE3 
> 
> OTOH, the benefit of such reviews by the IETF and PWE3 is when
> "commonality" among similar applications are discovered they can be
> standardized, rather kept proprietary.
> 
> 
>> 3) results a faster time to market, since no expert review will be needed
> 
> True, to some extent.  But, IMHO, I would much rather see a *slightly*
> slower process involving a careful expert review and/or IETF consensus
> to make sure we're not: a) unnecessarily duplicating work; and, b) at
> the same time, encouraging more standards-based approach.
> 
> 
>> 4) provides more codepoint space that the ACH channel type
> 
> This is false.  There is no shortage on ACH channel types today.
> 
> 
>> 5) only one VCCV ACH channel type needs to be configured in each box
>> for vendor specific filtering
>>
>> The 2nd method has the first 3 advantages only, and the first method
>> has none of these advantages.
> 
> 
> Also, let's take a step back here.  Wasn't the whole point with the
> joint ITU-T/IETF effort surrounding MPLS-TP to create an environment in
> which MPLS-TP could seamlessly interoperate within (existing) MPLS
> environments?  I thought a fundamental part of that work is striving
> towards creating a *standards-based* MPLS-TP data-plane, OAM, signaling,
> etc. mechanisms.  IMO, Vishwas' proposal and Matthew's proposal #2 seems
> to run contrary to that goal.
> 
> -shane (speaking only for himself, not as co-chair)
> _______________________________________________
> pwe3 mailing list
> pwe3@ietf.org
> https://www.ietf.org/mailman/listinfo/pwe3


-- 
Loa Andersson

Principal Networking Architect
Acreo AB                           phone:  +46 8 632 77 14
Isafjordsgatan 22                  mobile: +46 739 81 21 64
Kista, Sweden                      email:  loa.andersson@acreo.se
                                           loa@pi.nu
_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls


From mpls-bounces@ietf.org  Thu Oct  2 08:42:05 2008
Return-Path: <mpls-bounces@ietf.org>
X-Original-To: mpls-archive@megatron.ietf.org
Delivered-To: ietfarch-mpls-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 99B5728C230;
	Thu,  2 Oct 2008 08:42:05 -0700 (PDT)
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 9C08428C236
	for <mpls@core3.amsl.com>; Thu,  2 Oct 2008 08:42:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.487
X-Spam-Level: 
X-Spam-Status: No, score=-2.487 tagged_above=-999 required=5 tests=[AWL=0.113, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id eiluNe4gUtpI for <mpls@core3.amsl.com>;
	Thu,  2 Oct 2008 08:42:00 -0700 (PDT)
Received: from fg-out-1718.google.com (fg-out-1718.google.com [72.14.220.153])
	by core3.amsl.com (Postfix) with ESMTP id 861503A68CE
	for <mpls@ietf.org>; Thu,  2 Oct 2008 08:41:59 -0700 (PDT)
Received: by fg-out-1718.google.com with SMTP id d23so772263fga.41
	for <mpls@ietf.org>; Thu, 02 Oct 2008 08:42:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
	h=domainkey-signature:received:received:message-id:date:from:to
	:subject:cc:in-reply-to:mime-version:content-type
	:content-transfer-encoding:content-disposition:references;
	bh=MUSj8i8U4EUtH/CYFgO/sC5myhzTS2ZgdozoUEgxhEw=;
	b=iAj4KK2iACDMu9iyomUZabNDVtEXttVy7Bsl7t+JkPm3Mkqn/xyi6rFjspLPcpj1Qb
	Q5tUyqzxWgSyY1L28jQk7SlZjJRLlnOMKQ++cAX7Hk19QPTwXGYkmeORW7sepg7rLrsY
	BKzWL/1rspfvrr4qLLLOCrWwFy+supBk4B5vY=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=message-id:date:from:to:subject:cc:in-reply-to:mime-version
	:content-type:content-transfer-encoding:content-disposition
	:references;
	b=vI3F81rsBhUldUZlP+lV9SFvpJVO7KwfxOeZQU/D+gikpZyW1aSic2C2AEfkJnUjyX
	tEG3AsF/UrzUFlhmymLYvCLBCj5UMZ+COobFPigyO3rJUjkzb2/3DL0I16RRCjD4nPpy
	77w6CogXw2onBQRqSyMl/5HvS8QjFvjAwVKzw=
Received: by 10.180.204.10 with SMTP id b10mr5812536bkg.45.1222962143357;
	Thu, 02 Oct 2008 08:42:23 -0700 (PDT)
Received: by 10.180.226.2 with HTTP; Thu, 2 Oct 2008 08:42:22 -0700 (PDT)
Message-ID: <77ead0ec0810020842w17adb110qcd29446deede6ca7@mail.gmail.com>
Date: Thu, 2 Oct 2008 21:12:22 +0530
From: "Vishwas Manral" <vishwas.ietf@gmail.com>
To: "Shane Amante" <shane@castlepoint.net>
In-Reply-To: <48E4DE0F.9020704@castlepoint.net>
MIME-Version: 1.0
Content-Disposition: inline
References: <57ab175fd1b5f945afa7bc60dde31075@mail.cph.tpack.net>
	<48E4DE0F.9020704@castlepoint.net>
Cc: "l2vpn@ietf.org" <l2vpn@ietf.org>, "mpls@ietf.org" <mpls@ietf.org>,
	BOCCI Matthew <Matthew.Bocci@alcatel-lucent.com>,
	"ccamp@ietf.org" <ccamp@ietf.org>, "mpls-tp@ietf.org" <mpls-tp@ietf.org>,
	"pwe3@ietf.org" <pwe3@ietf.org>, Shahram Davari <davari@tpack.com>,
	BUSI ITALO <Italo.Busi@alcatel-lucent.it>
Subject: Re: [mpls] [mpls-tp] [PWE3] FW: Changes to PW ACH Channel Type
	allocationpolicy
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mpls-bounces@ietf.org
Errors-To: mpls-bounces@ietf.org

Hi Shane,

> Also, let's take a step back here.  Wasn't the whole point with the
> joint ITU-T/IETF effort surrounding MPLS-TP to create an environment in
> which MPLS-TP could seamlessly interoperate within (existing) MPLS
> environments?  I thought a fundamental part of that work is striving
> towards creating a *standards-based* MPLS-TP data-plane, OAM, signaling,
> etc. mechanisms.  IMO, Vishwas' proposal and Matthew's proposal #2 seems
> to run contrary to that goal.

Thanks for the detailed mail regarding your point of view.

So if I got you right, your opposition to the idea I proposed is based
on the fact that you are against allowing any proprietary ACH code
points as they would not be *standard based*. The options mentionend
by Matthew are however to address the request for *proprietary
extensions*. Am I missing the point altogather?

Thanks,
Vishwas
_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls


From mpls-bounces@ietf.org  Thu Oct  2 09:04:43 2008
Return-Path: <mpls-bounces@ietf.org>
X-Original-To: mpls-archive@megatron.ietf.org
Delivered-To: ietfarch-mpls-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id CCA6828C24B;
	Thu,  2 Oct 2008 09:04:43 -0700 (PDT)
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E688F28C23B;
	Thu,  2 Oct 2008 09:04:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.117
X-Spam-Level: 
X-Spam-Status: No, score=-1.117 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, DNS_FROM_RFC_BOGUSMX=1.482]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id ehfnLMG45nza; Thu,  2 Oct 2008 09:04:36 -0700 (PDT)
Received: from dog.tcb.net (dog.tcb.net [64.78.150.133])
	by core3.amsl.com (Postfix) with ESMTP id 745B528C23D;
	Thu,  2 Oct 2008 09:04:36 -0700 (PDT)
Received: by dog.tcb.net (Postfix, from userid 0)
	id 767AA26867C; Thu,  2 Oct 2008 10:04:05 -0600 (MDT)
Received: from [127.0.0.1] (dog.tcb.net [64.78.150.133])
	(authenticated-user smtp) (TLSv1/SSLv3 DHE-RSA-AES256-SHA 256/256)
	by dog.tcb.net with SMTP; Thu, 02 Oct 2008 10:04:05 -0600 (MDT)
	(envelope-from shane@castlepoint.net)
X-Avenger: version=0.7.8; receiver=dog.tcb.net; client-ip=64.78.150.133;
	client-port=39838; data-bytes=0
Message-ID: <48E4F0F3.8000704@castlepoint.net>
Date: Thu, 02 Oct 2008 10:04:03 -0600
From: Shane Amante <shane@castlepoint.net>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
To: Vishwas Manral <vishwas.ietf@gmail.com>
References: <57ab175fd1b5f945afa7bc60dde31075@mail.cph.tpack.net>	
	<48E4DE0F.9020704@castlepoint.net>
	<77ead0ec0810020842w17adb110qcd29446deede6ca7@mail.gmail.com>
In-Reply-To: <77ead0ec0810020842w17adb110qcd29446deede6ca7@mail.gmail.com>
Cc: "l2vpn@ietf.org" <l2vpn@ietf.org>, "mpls@ietf.org" <mpls@ietf.org>,
	BOCCI Matthew <Matthew.Bocci@alcatel-lucent.com>,
	"ccamp@ietf.org" <ccamp@ietf.org>, "mpls-tp@ietf.org" <mpls-tp@ietf.org>,
	"pwe3@ietf.org" <pwe3@ietf.org>, Shahram Davari <davari@tpack.com>,
	BUSI ITALO <Italo.Busi@alcatel-lucent.it>
Subject: Re: [mpls] [mpls-tp] [PWE3] FW: Changes to PW ACH Channel Type
	allocationpolicy
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: mpls-bounces@ietf.org
Errors-To: mpls-bounces@ietf.org

Vishwas,

Vishwas Manral wrote:
> Hi Shane,
> 
>> Also, let's take a step back here.  Wasn't the whole point with the
>> joint ITU-T/IETF effort surrounding MPLS-TP to create an environment in
>> which MPLS-TP could seamlessly interoperate within (existing) MPLS
>> environments?  I thought a fundamental part of that work is striving
>> towards creating a *standards-based* MPLS-TP data-plane, OAM, signaling,
>> etc. mechanisms.  IMO, Vishwas' proposal and Matthew's proposal #2 seems
>> to run contrary to that goal.
> 
> Thanks for the detailed mail regarding your point of view.
> 
> So if I got you right, your opposition to the idea I proposed is based
> on the fact that you are against allowing any proprietary ACH code
> points as they would not be *standard based*. The options mentionend
> by Matthew are however to address the request for *proprietary
> extensions*. Am I missing the point altogather?

Please note that I did not exclude Matthew's proposal #1 in the response 
you quoted above.  However, I did recommend that if the consensus was to 
adopt Matthew's proposal #1 I would rather see it modified, so only a 
(small) subset of codepoints (not the whole range of ACH's) were 
designated for "proprietary use", (still with expert review).  Please 
refer back to my first e-mail on this subject, where my position should 
be more clear:
http://www.ietf.org/mail-archive/web/pwe3/current/msg09945.html

-shane
_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls


From mpls-bounces@ietf.org  Thu Oct  2 09:51:43 2008
Return-Path: <mpls-bounces@ietf.org>
X-Original-To: mpls-archive@megatron.ietf.org
Delivered-To: ietfarch-mpls-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 1735728C245;
	Thu,  2 Oct 2008 09:51:43 -0700 (PDT)
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E564D28C1D2;
	Thu,  2 Oct 2008 09:51:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.893
X-Spam-Level: 
X-Spam-Status: No, score=-1.893 tagged_above=-999 required=5 tests=[AWL=0.356, 
	BAYES_00=-2.599, HELO_EQ_FR=0.35]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id Pk-0gM4SSBnE; Thu,  2 Oct 2008 09:51:40 -0700 (PDT)
Received: from smail6.alcatel.fr (colt-na5.alcatel.fr [62.23.212.5])
	by core3.amsl.com (Postfix) with ESMTP id BD23828C111;
	Thu,  2 Oct 2008 09:51:38 -0700 (PDT)
Received: from FRVELSBHS03.ad2.ad.alcatel.com (frvelsbhs03.ad2.ad.alcatel.com
	[155.132.6.75])
	by smail6.alcatel.fr (8.13.8/8.13.8/ICT) with ESMTP id m92GoxEG003085; 
	Thu, 2 Oct 2008 18:50:59 +0200
Received: from FRVELSMBS11.ad2.ad.alcatel.com ([155.132.6.33]) by
	FRVELSBHS03.ad2.ad.alcatel.com with Microsoft
	SMTPSVC(6.0.3790.2499); Thu, 2 Oct 2008 18:50:59 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Thu, 2 Oct 2008 18:50:56 +0200
Message-ID: <0458D2EE0C36744BABB36BE37805C29A02A41B1D@FRVELSMBS11.ad2.ad.alcatel.com>
In-Reply-To: <48E4F0F3.8000704@castlepoint.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [mpls-tp] [PWE3] FW: Changes to PW ACH Channel Type
	allocationpolicy
Thread-Index: AckkqJKJFC0Er7mmTBm52DbBrkgOPgABkDBA
References: <57ab175fd1b5f945afa7bc60dde31075@mail.cph.tpack.net>	
	<48E4DE0F.9020704@castlepoint.net>
	<77ead0ec0810020842w17adb110qcd29446deede6ca7@mail.gmail.com>
	<48E4F0F3.8000704@castlepoint.net>
From: "BOCCI Matthew" <Matthew.Bocci@alcatel-lucent.com>
To: "Shane Amante" <shane@castlepoint.net>,
	"Vishwas Manral" <vishwas.ietf@gmail.com>
X-OriginalArrivalTime: 02 Oct 2008 16:50:59.0842 (UTC)
	FILETIME=[0C255620:01C924AF]
X-Scanned-By: MIMEDefang 2.57 on 155.132.188.84
Cc: l2vpn@ietf.org, mpls@ietf.org, ccamp@ietf.org, mpls-tp@ietf.org,
	pwe3@ietf.org, Shahram Davari <davari@tpack.com>,
	BUSI ITALO <Italo.Busi@alcatel-lucent.it>
Subject: Re: [mpls] [mpls-tp] [PWE3] FW: Changes to PW ACH Channel Type
	allocationpolicy
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mpls-bounces@ietf.org
Errors-To: mpls-bounces@ietf.org

Shane,

We are not proposing changing the allocation policy for the whole
registry here. We can allocate, say, 1024 channel types by the new
method, and leave the rest for IETF consensus.

Regards

Matthew 

> -----Original Message-----
> From: Shane Amante [mailto:shane@castlepoint.net] 
> Sent: 02 October 2008 17:04
> To: Vishwas Manral
> Cc: Shahram Davari; BUSI ITALO; l2vpn@ietf.org; BOCCI 
> Matthew; mpls@ietf.org; ccamp@ietf.org; mpls-tp@ietf.org; 
> pwe3@ietf.org
> Subject: Re: [mpls-tp] [PWE3] FW: Changes to PW ACH Channel 
> Type allocationpolicy
> 
> Vishwas,
> 
> Vishwas Manral wrote:
> > Hi Shane,
> > 
> >> Also, let's take a step back here.  Wasn't the whole point 
> with the 
> >> joint ITU-T/IETF effort surrounding MPLS-TP to create an 
> environment 
> >> in which MPLS-TP could seamlessly interoperate within 
> (existing) MPLS 
> >> environments?  I thought a fundamental part of that work 
> is striving 
> >> towards creating a *standards-based* MPLS-TP data-plane, OAM, 
> >> signaling, etc. mechanisms.  IMO, Vishwas' proposal and Matthew's 
> >> proposal #2 seems to run contrary to that goal.
> > 
> > Thanks for the detailed mail regarding your point of view.
> > 
> > So if I got you right, your opposition to the idea I 
> proposed is based 
> > on the fact that you are against allowing any proprietary ACH code 
> > points as they would not be *standard based*. The options 
> mentionend 
> > by Matthew are however to address the request for *proprietary 
> > extensions*. Am I missing the point altogather?
> 
> Please note that I did not exclude Matthew's proposal #1 in 
> the response you quoted above.  However, I did recommend that 
> if the consensus was to adopt Matthew's proposal #1 I would 
> rather see it modified, so only a
> (small) subset of codepoints (not the whole range of ACH's) 
> were designated for "proprietary use", (still with expert 
> review).  Please refer back to my first e-mail on this 
> subject, where my position should be more clear:
> http://www.ietf.org/mail-archive/web/pwe3/current/msg09945.html
> 
> -shane
> 
_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls


From mpls-bounces@ietf.org  Thu Oct  2 11:39:09 2008
Return-Path: <mpls-bounces@ietf.org>
X-Original-To: mpls-archive@megatron.ietf.org
Delivered-To: ietfarch-mpls-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 0307228C21E;
	Thu,  2 Oct 2008 11:39:09 -0700 (PDT)
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 6779F3A6AD0;
	Thu,  2 Oct 2008 11:39:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.598
X-Spam-Level: 
X-Spam-Status: No, score=-6.598 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id A6SevXXZ6n2t; Thu,  2 Oct 2008 11:39:07 -0700 (PDT)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140])
	by core3.amsl.com (Postfix) with ESMTP id 0562B3A69F0;
	Thu,  2 Oct 2008 11:39:05 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,352,1220227200"; 
	d="eml'208?scan'208,208,217";a="21485391"
Received: from ams-dkim-1.cisco.com ([144.254.224.138])
	by ams-iport-1.cisco.com with ESMTP; 02 Oct 2008 18:39:24 +0000
Received: from ams-core-1.cisco.com (ams-core-1.cisco.com [144.254.224.150])
	by ams-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id m92IdOOl012775; 
	Thu, 2 Oct 2008 20:39:24 +0200
Received: from dhcp-gpk02-vlan300-64-103-65-109.cisco.com
	(dhcp-gpk02-vlan300-64-103-65-109.cisco.com [64.103.65.109])
	by ams-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m92IdNuK014332;
	Thu, 2 Oct 2008 18:39:23 GMT
Message-ID: <48E51561.1070103@cisco.com>
Date: Thu, 02 Oct 2008 19:39:29 +0100
From: Stewart Bryant <stbryant@cisco.com>
User-Agent: Thunderbird 2.0.0.16 (Macintosh/20080707)
MIME-Version: 1.0
To: pwe3 <pwe3@ietf.org>, "ccamp@ietf.org" <ccamp@ietf.org>,
	"l2vpn@ietf.org" <l2vpn@ietf.org>, "mpls@ietf.org" <mpls@ietf.org>
Content-Type: multipart/mixed; boundary="------------010408070202020501030202"
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=13920; t=1222972764;
	x=1223836764; c=relaxed/simple; s=amsdkim1002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=stbryant@cisco.com;
	z=From:=20Stewart=20Bryant=20<stbryant@cisco.com>
	|Subject:=20Re=3A=20[mpls-tp]=20[PWE3]=20FW=3A=20Changes=20
	to=20PW=20ACH=20Channel=20Type=20allocation=0A=20policy]
	|Sender:=20; bh=Dv5J3vONJLVQ25Z2+UHWxj8KjakAvj18vkfpDbYxBM4=;
	b=KiQtw71g4R9JlJusKd1uofrnFGTsRX1zdiZD0C2IGRh8x/iw7mJPB8y5LM
	B4fq+XIHOoOCJ70uZLn/xPKx1JUUrRi3qd7UJt5xIBaZA6vPMDzDSMNGi9Yp
	PFlTQY3dFl;
Authentication-Results: ams-dkim-1; header.From=stbryant@cisco.com; dkim=pass (
	sig from cisco.com/amsdkim1002 verified; ); 
Cc: Mike Shand <mshand@cisco.com>
Subject: Re: [mpls] [mpls-tp] [PWE3] FW: Changes to PW ACH Channel Type
 allocation policy]
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: stbryant@cisco.com
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=subscribe>
Sender: mpls-bounces@ietf.org
Errors-To: mpls-bounces@ietf.org

This is a multi-part message in MIME format.
--------------010408070202020501030202
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Since a reference was made to extension mechanisms proposed to
the ISIS WG, and since there seemed to be some enthusiasm
for it, to the point where there was a suggestion that we
might follow the same model, I asked my college Mike Shand
for some history and background and what happened next.

Please see the attached email for his answer.

I guess I have to ask whether there are lessons to be learned
from ISIS that we need to take into account here: i.e.
is experimental the way to go, and should we place significant
restriction on what you can do on an experimental codepoint?

Stewart

--------------010408070202020501030202
Content-Type: message/rfc822;
 name="Re: [Fwd: Re: [mpls-tp] [PWE3] FW: Changes to PW ACH Channel Type allocationpolicy].eml"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline;
 filename*0="Re: [Fwd: Re: [mpls-tp] [PWE3] FW: Changes to PW ACH Channel";
 filename*1=" Type allocation policy].eml"

X-Account-Key: account3
X-Mozilla-Keys: 
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140])
	by cisco.com (8.11.7p3+Sun/8.8.8) with ESMTP id m92Fvjp26895
	for <stbryant@mrwint.cisco.com>; Thu, 2 Oct 2008 16:57:45 +0100 (BST)
X-IronPort-AV: E=Sophos;i="4.33,352,1220227200"; 
   d="scan'208,217";a="21471859"
Received: from ams-dkim-2.cisco.com ([144.254.224.139])
  by ams-iport-1.cisco.com with ESMTP; 02 Oct 2008 15:57:45 +0000
Received: from ams-core-1.cisco.com (ams-core-1.cisco.com [144.254.224.150])
	by ams-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id m92Fvj9h002059
	for <stbryant@mrwint.cisco.com>; Thu, 2 Oct 2008 17:57:45 +0200
Received: from [64.103.64.190] (dhcp-gpk02-vlan300-64-103-64-190.cisco.com [64.103.64.190])
	by ams-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m92FviRf007406
	for <stbryant@cisco.com>; Thu, 2 Oct 2008 15:57:45 GMT
Message-ID: <48E4EF77.20900@cisco.com>
Date: Thu, 02 Oct 2008 16:57:43 +0100
From: mike shand <mshand@cisco.com>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
To: stbryant@cisco.com
Subject: Re: [Fwd: Re: [mpls-tp] [PWE3] FW: Changes to PW ACH Channel Type
 allocation policy]
References: <48E4EC39.5040202@cisco.com>
In-Reply-To: <48E4EC39.5040202@cisco.com>
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=10573; t=1222963065; x=1223827065;
	c=relaxed/simple; s=amsdkim2001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=mshand@cisco.com;
	z=From:=20mike=20shand=20<mshand@cisco.com>
	|Subject:=20Re=3A=20[Fwd=3A=20Re=3A=20[mpls-tp]=20[PWE3]=20
	FW=3A=20Changes=20to=20PW=20ACH=20Channel=20Type=0A=20alloca
	tion=20policy]
	|Sender:=20;
	bh=VNhbelG8ga5uxxtXpeVR65pmnfTtTds5mCLG0+G+mFY=;
	b=NcLCzPZKzovdg0OMUX4WzkZ5mKhzoeDNN8vjiDejTYJZL9VRuDAH/NEnqK
	1aK5C6ggaVjhCwMHv35RsGjoa1pHZX0p09n5lsu0xNDrILS1ZN+AspBCHeBn
	LCc14TMSDw;
Authentication-Results: ams-dkim-2; header.From=mshand@cisco.com; dkim=pass (
	sig from cisco.com/amsdkim2001 verified; ); 

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
  <title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
Stewart Bryant wrote:
<blockquote cite="mid:48E4EC39.5040202@cisco.com" type="cite"><br>
  <br>
  <hr size="4" width="90%"><br>
  <table class="header-part1" border="0" cellpadding="0" cellspacing="0"
 width="100%">
    <tbody>
      <tr>
        <td>
        <div class="headerdisplayname" style="display: inline;">Subject:
        </div>
Re: [mpls-tp] [PWE3] FW: Changes to PW ACH Channel Type allocation
policy</td>
      </tr>
      <tr>
        <td>
        <div class="headerdisplayname" style="display: inline;">From: </div>
"Vishwas Manral" <a class="moz-txt-link-rfc2396E" href="mailto:vishwas.ietf@gmail.com">&lt;vishwas.ietf@gmail.com&gt;</a></td>
      </tr>
      <tr>
        <td>
        <div class="headerdisplayname" style="display: inline;">Date: </div>
Wed, 1 Oct 2008 21:17:22 +0530</td>
      </tr>
      <tr>
        <td>
        <div class="headerdisplayname" style="display: inline;">To: </div>
"Shahram Davari" <a class="moz-txt-link-rfc2396E" href="mailto:davari@tpack.com">&lt;davari@tpack.com&gt;</a></td>
      </tr>
    </tbody>
  </table>
  <table class="header-part2" border="0" cellpadding="0" cellspacing="0"
 width="100%">
    <tbody>
      <tr>
        <td>
        <div class="headerdisplayname" style="display: inline;">To: </div>
"Shahram Davari" <a class="moz-txt-link-rfc2396E" href="mailto:davari@tpack.com">&lt;davari@tpack.com&gt;</a></td>
      </tr>
      <tr>
        <td>
        <div class="headerdisplayname" style="display: inline;">CC: </div>
<a class="moz-txt-link-rfc2396E" href="mailto:l2vpn@ietf.org">"l2vpn@ietf.org"</a> <a class="moz-txt-link-rfc2396E" href="mailto:l2vpn@ietf.org">&lt;l2vpn@ietf.org&gt;</a>, BOCCI Matthew
<a class="moz-txt-link-rfc2396E" href="mailto:Matthew.Bocci@alcatel-lucent.com">&lt;Matthew.Bocci@alcatel-lucent.com&gt;</a>, <a class="moz-txt-link-rfc2396E" href="mailto:mpls@ietf.org">"mpls@ietf.org"</a>
<a class="moz-txt-link-rfc2396E" href="mailto:mpls@ietf.org">&lt;mpls@ietf.org&gt;</a>, <a class="moz-txt-link-rfc2396E" href="mailto:ccamp@ietf.org">"ccamp@ietf.org"</a> <a class="moz-txt-link-rfc2396E" href="mailto:ccamp@ietf.org">&lt;ccamp@ietf.org&gt;</a>,
<a class="moz-txt-link-rfc2396E" href="mailto:mpls-tp@ietf.org">"mpls-tp@ietf.org"</a> <a class="moz-txt-link-rfc2396E" href="mailto:mpls-tp@ietf.org">&lt;mpls-tp@ietf.org&gt;</a>, <a class="moz-txt-link-rfc2396E" href="mailto:pwe3@ietf.org">"pwe3@ietf.org"</a>
<a class="moz-txt-link-rfc2396E" href="mailto:pwe3@ietf.org">&lt;pwe3@ietf.org&gt;</a></td>
      </tr>
    </tbody>
  </table>
  <br>
  <pre wrap="">Hi Matthew,

I would like to propose another option if it is for vendor proprietery
"Channel Type" values in the ACH header. With the number of values of
the channel type being limited and the number of vendors actually a
lot, I would think something in the lines of what the draft below
talks about may make sense:

<a class="moz-txt-link-freetext" href="http://tools.ietf.org/draft-ietf-isis-proprietary-tlv-00">http://tools.ietf.org/draft-ietf-isis-proprietary-tlv-00</a>
  </pre>
</blockquote>
This draft was replaced by <br>
<pre wrap=""><a class="moz-txt-link-freetext" href="http://tools.ietf.org/html/draft-ietf-isis-experimental-tlv">http://tools.ietf.org/html/draft-ietf-isis-experimental-tlv</a>

because the working group did not want to sanction true vendor proprietary extensions, but wanted to limit them to those which could be described as experimental. A requirement was added that any such extension SHOULD be documented in an experimental RFC.

There were also strict limitations that the presence of an experimental TLV MUST NOT cause a router to calculate a different route.

It was also forbidden to use the TLV as a means for carrying general application data. GENAPP should be used for such purposes.

A particular constraint in IS-IS is that the number space available for TLVs is limited to 255.


However, despite all this, the draft expired in November 2005 and there has been no subsequent desire to resurrect it.

	Mike


</pre>
<blockquote cite="mid:48E4EC39.5040202@cisco.com" type="cite">
  <pre wrap="">
The idea is give a channel type value, for vendor specific
implemntations and further define the structure of the next header
value for such a "channel type" to actually have a Vendor OUI value.

This will allow for unlimited innovation without affecting
interoperability, unlike the other options you have mentioned.

Thanks,
Vishwas


On 10/1/08, Shahram Davari <a class="moz-txt-link-rfc2396E" href="mailto:davari@tpack.com">&lt;davari@tpack.com&gt;</a> wrote:
  </pre>
  <blockquote type="cite">
    <pre wrap="">Hi Mathew,

I support option 2, since a terminating node that doesn't understand the
VCCV channel type can always drop it. This would allow more innovation and
faster time to market.

Best regards,
Shahram


-----Original Message-----
From: <a class="moz-txt-link-abbreviated" href="mailto:pwe3-bounces@ietf.org">pwe3-bounces@ietf.org</a> [<a class="moz-txt-link-freetext" href="mailto:pwe3-bounces@ietf.org">mailto:pwe3-bounces@ietf.org</a>] On Behalf Of
BOCCI Matthew
Sent: September-30-08 12:23 PM
To: <a class="moz-txt-link-abbreviated" href="mailto:pwe3@ietf.org">pwe3@ietf.org</a>; <a class="moz-txt-link-abbreviated" href="mailto:mpls-tp@ietf.org">mpls-tp@ietf.org</a>; <a class="moz-txt-link-abbreviated" href="mailto:mpls@ietf.org">mpls@ietf.org</a>; <a class="moz-txt-link-abbreviated" href="mailto:ccamp@ietf.org">ccamp@ietf.org</a>;
<a class="moz-txt-link-abbreviated" href="mailto:l2vpn@ietf.org">l2vpn@ietf.org</a>
Subject: [PWE3] FW: Changes to PW ACH Channel Type allocation policy

The PWE3 chairs would like feedback on proposed changes to the
allocation policy for the PW ACH codepoint registry. Please see the
email below, and provide any feedback copying the PWE3 list.

Best regards

Matthew

-----Original Message-----
From: <a class="moz-txt-link-abbreviated" href="mailto:pwe3-bounces@ietf.org">pwe3-bounces@ietf.org</a> [<a class="moz-txt-link-freetext" href="mailto:pwe3-bounces@ietf.org">mailto:pwe3-bounces@ietf.org</a>] On Behalf Of
BOCCI Matthew
Sent: 25 September 2008 16:36
To: <a class="moz-txt-link-abbreviated" href="mailto:pwe3@ietf.org">pwe3@ietf.org</a>
Subject: [PWE3] Changes to PW ACH Channel Type allocation policy



The current IANA allocation policy for the PW associated channel type
registry is by IETF consensus. This policy was chosen in RFC 4385 based
on WG consensus that since the associated channel exists in the data
path, and VCCV packets are typically processed by the control processor
on many PEs, it was prudent for the IETF to maintain strict control over
what types of channels were allocated and to ensure that they complied
to the PWE3 architecture.

However, a need has been identified to provide a more flexible approach
to allocating code points for VCCV channel types. This has partly arisen
from the MPLS-TP work, where MPLS would be deployed in a transport
network and where a much wider range of applications for the PW
associated channel is envisioned, and partialy from a desire to extend
the OAM capabilities for regular MPLS. We can support MPLS-TP and
general MPLS apps with the current policy which requires standards
action.

However we are receiving requests to allow proprietary OAM and signaling
protocols to be used in transport applications, and need to decide on
the best way forward. We considered providing extension mechanisms
within the standards track protocols, but believe that the standards
track protocols would be much cleaner if the proprietary protocols ran
on their own ACH code points.

Note that we are talking about vendor protocols here. Other SDOs would
be required to publish an RFC and would only be allocated an ACH through
Standards Action.

There are two ways to address the requests for proprietary protocol ACH
code points:

1) Allow a range of the associated channel type registry to be allocated
through expert review. Guidelines would be provided for the expert
reviewer to guide them in assessing the request, which would have to be
made in the form of an internet draft, while making sure that the
request is dealt with in a timely and fair manner. This policy would
include hurdles with regard to security, congestion etc that would be
derived from those specified in the VCCV design.

2) Allow a range of the associated channel type registry to be allocated
on a first-come-first-served basis. This does not provide the level of
control that expert review provides, but this is balanced to some degree
by the fact that the VCCV channel type is indicated in the data path,
and so a PE can choose to discard or rate limit VCCV packets on an
unrecognised associated channel.

Any change to the ACH allocation policy would be outlined in the GE-ACH
draft, which would update RFC 4385.

We would appreciate feedback on the list as to which approach the WG
prefers.

Regards,

Stewart and Matthew

_______________________________________________
pwe3 mailing list
<a class="moz-txt-link-abbreviated" href="mailto:pwe3@ietf.org">pwe3@ietf.org</a>
<a class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/pwe3">https://www.ietf.org/mailman/listinfo/pwe3</a>
_______________________________________________
pwe3 mailing list
<a class="moz-txt-link-abbreviated" href="mailto:pwe3@ietf.org">pwe3@ietf.org</a>
<a class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/pwe3">https://www.ietf.org/mailman/listinfo/pwe3</a>



_______________________________________________
pwe3 mailing list
<a class="moz-txt-link-abbreviated" href="mailto:pwe3@ietf.org">pwe3@ietf.org</a>
<a class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/pwe3">https://www.ietf.org/mailman/listinfo/pwe3</a>

    </pre>
  </blockquote>
  <pre wrap=""><!---->_______________________________________________
mpls-tp mailing list
<a class="moz-txt-link-abbreviated" href="mailto:mpls-tp@ietf.org">mpls-tp@ietf.org</a>
<a class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/mpls-tp">https://www.ietf.org/mailman/listinfo/mpls-tp</a>

  </pre>
</blockquote>
<br>
</body>
</html>


--------------010408070202020501030202
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls

--------------010408070202020501030202--


From mpls-bounces@ietf.org  Thu Oct  2 12:34:23 2008
Return-Path: <mpls-bounces@ietf.org>
X-Original-To: mpls-archive@megatron.ietf.org
Delivered-To: ietfarch-mpls-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id DB91C28C269;
	Thu,  2 Oct 2008 12:34:23 -0700 (PDT)
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 330C928C16D;
	Thu,  2 Oct 2008 12:34:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.117
X-Spam-Level: 
X-Spam-Status: No, score=-1.117 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, DNS_FROM_RFC_BOGUSMX=1.482]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id ZAgOkwX2R-4F; Thu,  2 Oct 2008 12:34:21 -0700 (PDT)
Received: from dog.tcb.net (dog.tcb.net [64.78.150.133])
	by core3.amsl.com (Postfix) with ESMTP id 43A1F3A69A1;
	Thu,  2 Oct 2008 12:34:21 -0700 (PDT)
Received: by dog.tcb.net (Postfix, from userid 0)
	id DAD8626867C; Thu,  2 Oct 2008 13:34:27 -0600 (MDT)
Received: from [127.0.0.1] (dog.tcb.net [64.78.150.133])
	(authenticated-user smtp) (TLSv1/SSLv3 DHE-RSA-AES256-SHA 256/256)
	by dog.tcb.net with SMTP; Thu, 02 Oct 2008 13:34:27 -0600 (MDT)
	(envelope-from shane@castlepoint.net)
X-Avenger: version=0.7.8; receiver=dog.tcb.net; client-ip=64.78.150.133;
	client-port=38693; data-bytes=0
Message-ID: <48E52242.7050907@castlepoint.net>
Date: Thu, 02 Oct 2008 13:34:26 -0600
From: Shane Amante <shane@castlepoint.net>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
To: BOCCI Matthew <Matthew.Bocci@alcatel-lucent.com>
References: <57ab175fd1b5f945afa7bc60dde31075@mail.cph.tpack.net>	
	<48E4DE0F.9020704@castlepoint.net>
	<77ead0ec0810020842w17adb110qcd29446deede6ca7@mail.gmail.com>
	<48E4F0F3.8000704@castlepoint.net>
	<0458D2EE0C36744BABB36BE37805C29A02A41B1D@FRVELSMBS11.ad2.ad.alcatel.com>
In-Reply-To: <0458D2EE0C36744BABB36BE37805C29A02A41B1D@FRVELSMBS11.ad2.ad.alcatel.com>
Cc: l2vpn@ietf.org, mpls@ietf.org, ccamp@ietf.org, mpls-tp@ietf.org,
	pwe3@ietf.org, Shahram Davari <davari@tpack.com>,
	BUSI ITALO <Italo.Busi@alcatel-lucent.it>
Subject: Re: [mpls] [mpls-tp] [PWE3] FW: Changes to PW ACH Channel Type
	allocationpolicy
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: mpls-bounces@ietf.org
Errors-To: mpls-bounces@ietf.org

Matthew,

BOCCI Matthew wrote:
> Shane,
> 
> We are not proposing changing the allocation policy for the whole
> registry here. We can allocate, say, 1024 channel types by the new
> method, and leave the rest for IETF consensus.

OK, thanks for the clarification.  That makes sense.  Still, my 
preferences are unchanged from my original e-mail:
http://www.ietf.org/mail-archive/web/pwe3/current/msg09945.html
(In short, if there is wide consensus that we need to change the 
allocation process, then I'd prefer a small range of ACH's be allocated 
with Expert Review, only).

-shane (speaking only for himself)



> Regards
> 
> Matthew 
> 
>> -----Original Message-----
>> From: Shane Amante [mailto:shane@castlepoint.net] 
>> Sent: 02 October 2008 17:04
>> To: Vishwas Manral
>> Cc: Shahram Davari; BUSI ITALO; l2vpn@ietf.org; BOCCI 
>> Matthew; mpls@ietf.org; ccamp@ietf.org; mpls-tp@ietf.org; 
>> pwe3@ietf.org
>> Subject: Re: [mpls-tp] [PWE3] FW: Changes to PW ACH Channel 
>> Type allocationpolicy
>>
>> Vishwas,
>>
>> Vishwas Manral wrote:
>>> Hi Shane,
>>>
>>>> Also, let's take a step back here.  Wasn't the whole point 
>> with the 
>>>> joint ITU-T/IETF effort surrounding MPLS-TP to create an 
>> environment 
>>>> in which MPLS-TP could seamlessly interoperate within 
>> (existing) MPLS 
>>>> environments?  I thought a fundamental part of that work 
>> is striving 
>>>> towards creating a *standards-based* MPLS-TP data-plane, OAM, 
>>>> signaling, etc. mechanisms.  IMO, Vishwas' proposal and Matthew's 
>>>> proposal #2 seems to run contrary to that goal.
>>> Thanks for the detailed mail regarding your point of view.
>>>
>>> So if I got you right, your opposition to the idea I 
>> proposed is based 
>>> on the fact that you are against allowing any proprietary ACH code 
>>> points as they would not be *standard based*. The options 
>> mentionend 
>>> by Matthew are however to address the request for *proprietary 
>>> extensions*. Am I missing the point altogather?
>> Please note that I did not exclude Matthew's proposal #1 in 
>> the response you quoted above.  However, I did recommend that 
>> if the consensus was to adopt Matthew's proposal #1 I would 
>> rather see it modified, so only a
>> (small) subset of codepoints (not the whole range of ACH's) 
>> were designated for "proprietary use", (still with expert 
>> review).  Please refer back to my first e-mail on this 
>> subject, where my position should be more clear:
>> http://www.ietf.org/mail-archive/web/pwe3/current/msg09945.html
>>
>> -shane
>>

_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls


From mpls-bounces@ietf.org  Fri Oct  3 00:38:45 2008
Return-Path: <mpls-bounces@ietf.org>
X-Original-To: mpls-archive@megatron.ietf.org
Delivered-To: ietfarch-mpls-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 1520C3A6AEE;
	Fri,  3 Oct 2008 00:38:45 -0700 (PDT)
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 425ED3A69E0;
	Fri,  3 Oct 2008 00:38:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.249
X-Spam-Level: 
X-Spam-Status: No, score=-2.249 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, HELO_EQ_FR=0.35]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id bAsA1E4f-r4Y; Fri,  3 Oct 2008 00:38:42 -0700 (PDT)
Received: from smail5.alcatel.fr (smail5.alcatel.fr [62.23.212.27])
	by core3.amsl.com (Postfix) with ESMTP id C2F063A68EB;
	Fri,  3 Oct 2008 00:38:41 -0700 (PDT)
Received: from FRVELSBHS04.ad2.ad.alcatel.com (frvelsbhs04.ad2.ad.alcatel.com
	[155.132.6.76])
	by smail5.alcatel.fr (8.13.8/8.13.8/ICT) with ESMTP id m937cbsM007785; 
	Fri, 3 Oct 2008 09:38:37 +0200
Received: from FRVELSMBS21.ad2.ad.alcatel.com ([155.132.6.55]) by
	FRVELSBHS04.ad2.ad.alcatel.com with Microsoft
	SMTPSVC(6.0.3790.2499); Fri, 3 Oct 2008 09:38:37 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Fri, 3 Oct 2008 09:38:47 +0200
Message-ID: <6FD21B53861BF44AA90A288402036AB40193F9F1@FRVELSMBS21.ad2.ad.alcatel.com>
In-Reply-To: <7DBAFEC6A76F3E42817DF1EBE64CB02605E3E1D2@ftrdmel2>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [mpls-tp] [mpls] [PWE3] Changes to PW ACH Channel
	Typeallocationpolicy
Thread-Index: AckkQ71IH8+xzlBPTXyZ2QuPfVC+nQAT4P0wAAFwrKAAI6eCgA==
References: <0458D2EE0C36744BABB36BE37805C29A029C6251@FRVELSMBS11.ad2.ad.alcatel.com><639AAB99-9B29-40B1-A57D-C3476D87696C@castlepoint.net><D6CB948F7AFD6F4881D4B4F80C8509AA01208045@gaalpa1msgusr7e.ugd.att.com>
	<7DBAFEC6A76F3E42817DF1EBE64CB02605E3E1D2@ftrdmel2>
From: "BUSI ITALO" <Italo.Busi@alcatel-lucent.it>
To: <julien.meuric@orange-ftgroup.com>, <dbrungard@att.com>,
	<shane@castlepoint.net>, "BOCCI Matthew" <Matthew.Bocci@alcatel-lucent.com>
X-OriginalArrivalTime: 03 Oct 2008 07:38:37.0195 (UTC)
	FILETIME=[0C007DB0:01C9252B]
X-Scanned-By: MIMEDefang 2.57 on 155.132.188.13
Cc: l2vpn@ietf.org, mpls@ietf.org, ccamp@ietf.org, pwe3@ietf.org,
	mpls-tp@ietf.org
Subject: Re: [mpls] [mpls-tp] [PWE3] Changes to PW ACH Channel
	Typeallocationpolicy
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mpls-bounces@ietf.org
Errors-To: mpls-bounces@ietf.org

Julien, Tom, Shane and Deborah,

it looks like you have a common position regarding interoperability
issues of proprietary protocols.

I can understand your issues with proprietary protocols because, by
definition, they do not interoperate.

However please note that all proprietary protocols by default must be
disabled and enabled if and only if it is known that all the nodes that
need to process the proprietary packets are capable to support the
proprietary protocol. As such you can simply never enable any
proprietary protocol.

I fail to understand how the allocation policy of ACH codepoints for
proprietary use can change the management issues from your point of
view.

Italo

> -----Original Message-----
> From: l2vpn-bounces@ietf.org [mailto:l2vpn-bounces@ietf.org] 
> On Behalf Of julien.meuric@orange-ftgroup.com
> Sent: Thursday, October 02, 2008 5:18 PM
> To: dbrungard@att.com; shane@castlepoint.net; BOCCI Matthew
> Cc: l2vpn@ietf.org; mpls@ietf.org; ccamp@ietf.org; 
> pwe3@ietf.org; mpls-tp@ietf.org
> Subject: RE: [mpls-tp] [mpls] [PWE3] Changes to PW ACH 
> Channel Typeallocationpolicy
> 
> Hi.
> 
> I must agree with Deborah and Shane.
> 
> Option #3 hides the complexity behind a (useless) hierarchy and is
> clearly not desired. Option #2 would create an explicit non standard
> range and is not what we expect from the IETF.
> As a result, since changing the former process seems already 
> committed,
> option #1 remains the better compromise.
> 
> Regards,
> 
> Julien
> 
> 
> -----Original Message-----
> From: mpls-tp-bounces@ietf.org [mailto:mpls-tp-bounces@ietf.org] On
> Behalf Of BRUNGARD, DEBORAH A, ATTLABS
> 
> Agree- and with the strong wording that option #1 is not for
> SDOs/Forums. Option 2 (or the 3rd option being discussed), 
> may be viewed
> as no bottleneck for vendors on development of proprietary 
> options, but
> for operators, it will be an interoperability nightmare.
> Deborah  
> 
> -----Original Message-----
> From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On 
> Behalf Of
> Shane Amante
> 
> Matthew,
> 
> Speaking as an operator, (L2VPN WG co-chair hat off), I would also  
> prefer the existing mechanism that's already in place: expert review  
> and IETF consensus.  After all, there are significant benefits to  
> standards-based OAM and signaling protocols.  On the other 
> hand, some  
> people may still have a legitimate need to do uncommon things that  
> aren't considered mainstream.  In that case, I would rather see a  
> (small) subset of codepoints allocated for expert review with 
> no IETF  
> consensus (Option #1 below).
> 
> -shane
> 
> 
> On Sep 30, 2008, at 10:23 AM, BOCCI Matthew wrote:
> > The PWE3 chairs would like feedback on proposed changes to the
> > allocation policy for the PW ACH codepoint registry. Please see the
> > email below, and provide any feedback copying the PWE3 list.
> >
> > Best regards
> >
> > Matthew
> >
> > -----Original Message-----
> > From: pwe3-bounces@ietf.org [mailto:pwe3-bounces@ietf.org] 
> On Behalf  
> > Of
> > BOCCI Matthew
> >
> > The current IANA allocation policy for the PW associated 
> channel type
> > registry is by IETF consensus. This policy was chosen in RFC 4385  
> > based
> > on WG consensus that since the associated channel exists in the data
> > path, and VCCV packets are typically processed by the control  
> > processor
> > on many PEs, it was prudent for the IETF to maintain strict 
> control  
> > over
> > what types of channels were allocated and to ensure that 
> they complied
> > to the PWE3 architecture.
> >
> > However, a need has been identified to provide a more flexible  
> > approach
> > to allocating code points for VCCV channel types. This has partly  
> > arisen
> > from the MPLS-TP work, where MPLS would be deployed in a transport
> > network and where a much wider range of applications for the PW
> > associated channel is envisioned, and partialy from a 
> desire to extend
> > the OAM capabilities for regular MPLS. We can support MPLS-TP and
> > general MPLS apps with the current policy which requires standards
> > action.
> >
> > However we are receiving requests to allow proprietary OAM and  
> > signaling
> > protocols to be used in transport applications, and need to 
> decide on
> > the best way forward. We considered providing extension mechanisms
> > within the standards track protocols, but believe that the standards
> > track protocols would be much cleaner if the proprietary 
> protocols ran
> > on their own ACH code points.
> >
> > Note that we are talking about vendor protocols here. Other 
> SDOs would
> > be required to publish an RFC and would only be allocated an ACH  
> > through
> > Standards Action.
> >
> > There are two ways to address the requests for proprietary 
> protocol  
> > ACH
> > code points:
> >
> > 1) Allow a range of the associated channel type registry to be  
> > allocated
> > through expert review. Guidelines would be provided for the expert
> > reviewer to guide them in assessing the request, which 
> would have to  
> > be
> > made in the form of an internet draft, while making sure that the
> > request is dealt with in a timely and fair manner. This policy would
> > include hurdles with regard to security, congestion etc 
> that would be
> > derived from those specified in the VCCV design.
> >
> > 2) Allow a range of the associated channel type registry to be  
> > allocated
> > on a first-come-first-served basis. This does not provide 
> the level of
> > control that expert review provides, but this is balanced to some  
> > degree
> > by the fact that the VCCV channel type is indicated in the 
> data path,
> > and so a PE can choose to discard or rate limit VCCV packets on an
> > unrecognised associated channel.
> >
> > Any change to the ACH allocation policy would be outlined 
> in the GE- 
> > ACH
> > draft, which would update RFC 4385.
> >
> > We would appreciate feedback on the list as to which approach the WG
> > prefers.
> >
> > Regards,
> >
> > Stewart and Matthew
> >
> > _______________________________________________
> > pwe3 mailing list
> > pwe3@ietf.org
> > https://www.ietf.org/mailman/listinfo/pwe3
> 
> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls
> _______________________________________________
> mpls-tp mailing list
> mpls-tp@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls-tp
> 
_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls


From mpls-bounces@ietf.org  Fri Oct  3 00:55:56 2008
Return-Path: <mpls-bounces@ietf.org>
X-Original-To: mpls-archive@megatron.ietf.org
Delivered-To: ietfarch-mpls-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B6B963A6AF4;
	Fri,  3 Oct 2008 00:55:56 -0700 (PDT)
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 835A83A68EB;
	Fri,  3 Oct 2008 00:55:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.249
X-Spam-Level: 
X-Spam-Status: No, score=-2.249 tagged_above=-999 required=5 tests=[AWL=0.000, 
	BAYES_00=-2.599, HELO_EQ_FR=0.35]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id uspyXEEdZ0cP; Fri,  3 Oct 2008 00:55:53 -0700 (PDT)
Received: from smail6.alcatel.fr (gc-na5.alcatel.fr [64.208.49.5])
	by core3.amsl.com (Postfix) with ESMTP id 8CA193A686A;
	Fri,  3 Oct 2008 00:55:53 -0700 (PDT)
Received: from FRVELSBHS03.ad2.ad.alcatel.com (frvelsbhs03.ad2.ad.alcatel.com
	[155.132.6.75])
	by smail6.alcatel.fr (8.13.8/8.13.8/ICT) with ESMTP id m937uHul024758; 
	Fri, 3 Oct 2008 09:56:17 +0200
Received: from FRVELSMBS21.ad2.ad.alcatel.com ([155.132.6.55]) by
	FRVELSBHS03.ad2.ad.alcatel.com with Microsoft
	SMTPSVC(6.0.3790.2499); Fri, 3 Oct 2008 09:56:17 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Fri, 3 Oct 2008 09:56:27 +0200
Message-ID: <6FD21B53861BF44AA90A288402036AB40193FA17@FRVELSMBS21.ad2.ad.alcatel.com>
In-Reply-To: <48E47400.2090309@cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [mpls] [PWE3] FW: Changes to PW ACH Channel Type
	allocation	policy
Thread-Index: AckkXh4Ga2Tii12ZSWONys7Db+iwcwAzh8TQ
References: <0458D2EE0C36744BABB36BE37805C29A029C6251@FRVELSMBS11.ad2.ad.alcatel.com>	<ba6305ea8b6f7b41bae8dcbb49c37c7c@mail.cph.tpack.net>
	<6FD21B53861BF44AA90A288402036AB40193F72F@FRVELSMBS21.ad2.ad.alcatel.com>
	<48E47400.2090309@cisco.com>
From: "BUSI ITALO" <Italo.Busi@alcatel-lucent.it>
To: <stbryant@cisco.com>
X-OriginalArrivalTime: 03 Oct 2008 07:56:17.0454 (UTC)
	FILETIME=[83F72CE0:01C9252D]
X-Scanned-By: MIMEDefang 2.57 on 155.132.188.84
Cc: l2vpn@ietf.org, BOCCI Matthew <Matthew.Bocci@alcatel-lucent.com>,
	mpls@ietf.org, ccamp@ietf.org, mpls-tp@ietf.org, pwe3@ietf.org,
	Shahram Davari <davari@tpack.com>
Subject: Re: [mpls] [PWE3] FW: Changes to PW ACH Channel Type
	allocation	policy
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mpls-bounces@ietf.org
Errors-To: mpls-bounces@ietf.org

Stewart,

as far as I can understand from RFC 4446, a vendor can be prevented
implementing proprietary innovative features by simply disapproving its
codepoint request.

Italo

> -----Original Message-----
> From: Stewart Bryant [mailto:stbryant@cisco.com] 
> Sent: Thursday, October 02, 2008 9:11 AM
> To: BUSI ITALO
> Cc: Shahram Davari; BOCCI Matthew; pwe3@ietf.org; 
> mpls-tp@ietf.org; mpls@ietf.org; ccamp@ietf.org; l2vpn@ietf.org
> Subject: Re: [mpls] [PWE3] FW: Changes to PW ACH Channel Type 
> allocation policy
> 
> BUSI ITALO wrote:
> > I also support option 2
> >
> > The requirement is to allow a vendor to implement 
> proprietary innovative
> > features.
> >
> > Italo
> >
> >   
> Italo
> 
> How does option 1 prevent a vendor implementing proprietary 
> innovative 
> features?
> 
> Stewart
> 
_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls


From mpls-bounces@ietf.org  Fri Oct  3 00:57:19 2008
Return-Path: <mpls-bounces@ietf.org>
X-Original-To: mpls-archive@megatron.ietf.org
Delivered-To: ietfarch-mpls-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 295EB28C197;
	Fri,  3 Oct 2008 00:57:19 -0700 (PDT)
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 0339F3A68EB;
	Fri,  3 Oct 2008 00:57:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.249
X-Spam-Level: 
X-Spam-Status: No, score=-2.249 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, HELO_EQ_FR=0.35]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id Y5PbpdW2vdTc; Fri,  3 Oct 2008 00:57:17 -0700 (PDT)
Received: from smail5.alcatel.fr (smail5.alcatel.fr [64.208.49.27])
	by core3.amsl.com (Postfix) with ESMTP id 7E9103A686A;
	Fri,  3 Oct 2008 00:57:16 -0700 (PDT)
Received: from FRVELSBHS03.ad2.ad.alcatel.com (frvelsbhs03.ad2.ad.alcatel.com
	[155.132.6.75])
	by smail5.alcatel.fr (8.13.8/8.13.8/ICT) with ESMTP id m937vcAh023013; 
	Fri, 3 Oct 2008 09:57:38 +0200
Received: from FRVELSMBS21.ad2.ad.alcatel.com ([155.132.6.55]) by
	FRVELSBHS03.ad2.ad.alcatel.com with Microsoft
	SMTPSVC(6.0.3790.2499); Fri, 3 Oct 2008 09:57:38 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Fri, 3 Oct 2008 09:57:47 +0200
Message-ID: <6FD21B53861BF44AA90A288402036AB40193FA1C@FRVELSMBS21.ad2.ad.alcatel.com>
In-Reply-To: <C50A3312.E217%tom.nadeau@bt.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [mpls-tp] [PWE3] FW: Changes to PW ACH Channel Type
	allocationpolicy
Thread-Index: Ackj3Q1bqBGtuyWETZaWG4drFEnw4AAf+XvQAArRnjgAKVxUoA==
References: <6FD21B53861BF44AA90A288402036AB40193F737@FRVELSMBS21.ad2.ad.alcatel.com>
	<C50A3312.E217%tom.nadeau@bt.com>
From: "BUSI ITALO" <Italo.Busi@alcatel-lucent.it>
To: "Thomas D. Nadeau" <tom.nadeau@bt.com>,
	"Vishwas Manral" <vishwas.ietf@gmail.com>,
	"Shahram Davari" <davari@tpack.com>
X-OriginalArrivalTime: 03 Oct 2008 07:57:38.0831 (UTC)
	FILETIME=[B47851F0:01C9252D]
X-Scanned-By: MIMEDefang 2.57 on 155.132.188.13
Cc: l2vpn@ietf.org, BOCCI Matthew <Matthew.Bocci@alcatel-lucent.com>,
	mpls@ietf.org, ccamp@ietf.org, mpls-tp@ietf.org, pwe3@ietf.org
Subject: Re: [mpls] [mpls-tp] [PWE3] FW: Changes to PW ACH Channel Type
	allocationpolicy
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mpls-bounces@ietf.org
Errors-To: mpls-bounces@ietf.org

See my reply to the same question made by Stewart

Italo

> -----Original Message-----
> From: Thomas D. Nadeau [mailto:tom.nadeau@bt.com] 
> Sent: Thursday, October 02, 2008 2:13 PM
> To: BUSI ITALO; Vishwas Manral; Shahram Davari
> Cc: l2vpn@ietf.org; BOCCI Matthew; mpls@ietf.org; 
> ccamp@ietf.org; mpls-tp@ietf.org; pwe3@ietf.org
> Subject: Re: [mpls-tp] [PWE3] FW: Changes to PW ACH Channel 
> Type allocationpolicy
> 
> 
> 
> 
> On 10/2/08 3:11 AM, "BUSI ITALO" <Italo.Busi@alcatel-lucent.it> wrote:
> 
> > Vishwas,
> > 
> > I think this is a good idea
> > 
> > Both this proposal and option 2 (fist-come-first-served) meet the
> > requirements to make the ACH mechanism extensible.
> 
>     How does the existing mechanism not meet the requirement 
> to make an ACH
> mechanism extensible?
> 
>     --Tom
> 
>  
> > The advantage of this approach is that we do not have to 
> worry about how
> > many codepoints we need to allocate for proprietary 
> extensions: we just
> > need one codepoint.
> > 
> > Italo
> > 
> >> -----Original Message-----
> >> From: mpls-tp-bounces@ietf.org
> >> [mailto:mpls-tp-bounces@ietf.org] On Behalf Of Vishwas Manral
> >> Sent: Wednesday, October 01, 2008 5:47 PM
> >> To: Shahram Davari
> >> Cc: l2vpn@ietf.org; BOCCI Matthew; mpls@ietf.org;
> >> ccamp@ietf.org; mpls-tp@ietf.org; pwe3@ietf.org
> >> Subject: Re: [mpls-tp] [PWE3] FW: Changes to PW ACH Channel
> >> Type allocationpolicy
> >> 
> >> Hi Matthew,
> >> 
> >> I would like to propose another option if it is for vendor 
> proprietery
> >> "Channel Type" values in the ACH header. With the number 
> of values of
> >> the channel type being limited and the number of vendors actually a
> >> lot, I would think something in the lines of what the draft below
> >> talks about may make sense:
> >> 
> >> http://tools.ietf.org/draft-ietf-isis-proprietary-tlv-00
> >> 
> >> The idea is give a channel type value, for vendor specific
> >> implemntations and further define the structure of the next header
> >> value for such a "channel type" to actually have a Vendor 
> OUI value.
> >> 
> >> This will allow for unlimited innovation without affecting
> >> interoperability, unlike the other options you have mentioned.
> >> 
> >> Thanks,
> >> Vishwas
> >> 
> >> 
> >> On 10/1/08, Shahram Davari <davari@tpack.com> wrote:
> >>> Hi Mathew,
> >>> 
> >>> I support option 2, since a terminating node that doesn't
> >> understand the
> >>> VCCV channel type can always drop it. This would allow more
> >> innovation and
> >>> faster time to market.
> >>> 
> >>> Best regards,
> >>> Shahram
> >>> 
> >>> 
> >>> -----Original Message-----
> >>> From: pwe3-bounces@ietf.org [mailto:pwe3-bounces@ietf.org]
> >> On Behalf Of
> >>> BOCCI Matthew
> >>> Sent: September-30-08 12:23 PM
> >>> To: pwe3@ietf.org; mpls-tp@ietf.org; mpls@ietf.org; 
> ccamp@ietf.org;
> >>> l2vpn@ietf.org
> >>> Subject: [PWE3] FW: Changes to PW ACH Channel Type 
> allocation policy
> >>> 
> >>> The PWE3 chairs would like feedback on proposed changes to the
> >>> allocation policy for the PW ACH codepoint registry. 
> Please see the
> >>> email below, and provide any feedback copying the PWE3 list.
> >>> 
> >>> Best regards
> >>> 
> >>> Matthew
> >>> 
> >>> -----Original Message-----
> >>> From: pwe3-bounces@ietf.org [mailto:pwe3-bounces@ietf.org]
> >> On Behalf Of
> >>> BOCCI Matthew
> >>> Sent: 25 September 2008 16:36
> >>> To: pwe3@ietf.org
> >>> Subject: [PWE3] Changes to PW ACH Channel Type allocation policy
> >>> 
> >>> 
> >>> 
> >>> The current IANA allocation policy for the PW associated
> >> channel type
> >>> registry is by IETF consensus. This policy was chosen in
> >> RFC 4385 based
> >>> on WG consensus that since the associated channel exists 
> in the data
> >>> path, and VCCV packets are typically processed by the
> >> control processor
> >>> on many PEs, it was prudent for the IETF to maintain strict
> >> control over
> >>> what types of channels were allocated and to ensure that
> >> they complied
> >>> to the PWE3 architecture.
> >>> 
> >>> However, a need has been identified to provide a more
> >> flexible approach
> >>> to allocating code points for VCCV channel types. This has
> >> partly arisen
> >>> from the MPLS-TP work, where MPLS would be deployed in a transport
> >>> network and where a much wider range of applications for the PW
> >>> associated channel is envisioned, and partialy from a
> >> desire to extend
> >>> the OAM capabilities for regular MPLS. We can support MPLS-TP and
> >>> general MPLS apps with the current policy which requires standards
> >>> action.
> >>> 
> >>> However we are receiving requests to allow proprietary OAM
> >> and signaling
> >>> protocols to be used in transport applications, and need to
> >> decide on
> >>> the best way forward. We considered providing extension mechanisms
> >>> within the standards track protocols, but believe that 
> the standards
> >>> track protocols would be much cleaner if the proprietary
> >> protocols ran
> >>> on their own ACH code points.
> >>> 
> >>> Note that we are talking about vendor protocols here. Other
> >> SDOs would
> >>> be required to publish an RFC and would only be allocated
> >> an ACH through
> >>> Standards Action.
> >>> 
> >>> There are two ways to address the requests for proprietary
> >> protocol ACH
> >>> code points:
> >>> 
> >>> 1) Allow a range of the associated channel type registry to
> >> be allocated
> >>> through expert review. Guidelines would be provided for the expert
> >>> reviewer to guide them in assessing the request, which
> >> would have to be
> >>> made in the form of an internet draft, while making sure that the
> >>> request is dealt with in a timely and fair manner. This 
> policy would
> >>> include hurdles with regard to security, congestion etc
> >> that would be
> >>> derived from those specified in the VCCV design.
> >>> 
> >>> 2) Allow a range of the associated channel type registry to
> >> be allocated
> >>> on a first-come-first-served basis. This does not provide
> >> the level of
> >>> control that expert review provides, but this is balanced
> >> to some degree
> >>> by the fact that the VCCV channel type is indicated in the
> >> data path,
> >>> and so a PE can choose to discard or rate limit VCCV packets on an
> >>> unrecognised associated channel.
> >>> 
> >>> Any change to the ACH allocation policy would be outlined
> >> in the GE-ACH
> >>> draft, which would update RFC 4385.
> >>> 
> >>> We would appreciate feedback on the list as to which 
> approach the WG
> >>> prefers.
> >>> 
> >>> Regards,
> >>> 
> >>> Stewart and Matthew
> >>> 
> >>> _______________________________________________
> >>> pwe3 mailing list
> >>> pwe3@ietf.org
> >>> https://www.ietf.org/mailman/listinfo/pwe3
> >>> _______________________________________________
> >>> pwe3 mailing list
> >>> pwe3@ietf.org
> >>> https://www.ietf.org/mailman/listinfo/pwe3
> >>> 
> >>> 
> >>> 
> >>> _______________________________________________
> >>> pwe3 mailing list
> >>> pwe3@ietf.org
> >>> https://www.ietf.org/mailman/listinfo/pwe3
> >>> 
> >> _______________________________________________
> >> mpls-tp mailing list
> >> mpls-tp@ietf.org
> >> https://www.ietf.org/mailman/listinfo/mpls-tp
> >> 
> 
> 
_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls


From mpls-bounces@ietf.org  Fri Oct  3 01:08:26 2008
Return-Path: <mpls-bounces@ietf.org>
X-Original-To: mpls-archive@megatron.ietf.org
Delivered-To: ietfarch-mpls-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id DC85E28C1C6;
	Fri,  3 Oct 2008 01:08:26 -0700 (PDT)
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 6B92728C1E4;
	Fri,  3 Oct 2008 01:08:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.454
X-Spam-Level: 
X-Spam-Status: No, score=-6.454 tagged_above=-999 required=5 tests=[AWL=0.145, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id TBWcFox16SmB; Fri,  3 Oct 2008 01:08:24 -0700 (PDT)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140])
	by core3.amsl.com (Postfix) with ESMTP id 5FBE928C1C6;
	Fri,  3 Oct 2008 01:08:23 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,355,1220227200"; d="scan'208";a="21519479"
Received: from ams-dkim-1.cisco.com ([144.254.224.138])
	by ams-iport-1.cisco.com with ESMTP; 03 Oct 2008 08:08:36 +0000
Received: from ams-core-1.cisco.com (ams-core-1.cisco.com [144.254.224.150])
	by ams-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id m9388a8W012159; 
	Fri, 3 Oct 2008 10:08:36 +0200
Received: from stewart-bryants-computer.local (dhcp-10-61-106-140.cisco.com
	[10.61.106.140])
	by ams-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m9388ZGb012454;
	Fri, 3 Oct 2008 08:08:35 GMT
Message-ID: <48E5D307.4080706@cisco.com>
Date: Fri, 03 Oct 2008 09:08:39 +0100
From: Stewart Bryant <stbryant@cisco.com>
User-Agent: Thunderbird 2.0.0.16 (Macintosh/20080707)
MIME-Version: 1.0
To: BUSI ITALO <Italo.Busi@alcatel-lucent.it>
References: <0458D2EE0C36744BABB36BE37805C29A029C6251@FRVELSMBS11.ad2.ad.alcatel.com>	<ba6305ea8b6f7b41bae8dcbb49c37c7c@mail.cph.tpack.net>
	<6FD21B53861BF44AA90A288402036AB40193F72F@FRVELSMBS21.ad2.ad.alcatel.com>
	<48E47400.2090309@cisco.com>
	<6FD21B53861BF44AA90A288402036AB40193FA17@FRVELSMBS21.ad2.ad.alcatel.com>
In-Reply-To: <6FD21B53861BF44AA90A288402036AB40193FA17@FRVELSMBS21.ad2.ad.alcatel.com>
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1269; t=1223021316;
	x=1223885316; c=relaxed/simple; s=amsdkim1002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=stbryant@cisco.com;
	z=From:=20Stewart=20Bryant=20<stbryant@cisco.com>
	|Subject:=20Re=3A=20[mpls]=20[PWE3]=20FW=3A=20Changes=20to=
	20PW=20ACH=20Channel=20Type=20allocation=09policy |Sender:=20;
	bh=E8McJlA9P1VOW3261fZiydOx2hwDHBpmvcXR/UltbyQ=;
	b=My5ab5b8+c5u2+m9j6yghqAaV9diBb3rXUQm5q6fFatqPknR2PYBk6CBIb
	PWY1Uu4hE7gCzZmuU42mRpvvMlpRJlpfwTJJSxVXGbvppxzZtK30pMPFsVt7
	ZTV83coBR/;
Authentication-Results: ams-dkim-1; header.From=stbryant@cisco.com; dkim=pass (
	sig from cisco.com/amsdkim1002 verified; ); 
Cc: l2vpn@ietf.org, BOCCI Matthew <Matthew.Bocci@alcatel-lucent.com>,
	mpls@ietf.org, ccamp@ietf.org, mpls-tp@ietf.org, pwe3@ietf.org,
	Shahram Davari <davari@tpack.com>
Subject: Re: [mpls] [PWE3] FW: Changes to PW ACH Channel Type
	allocation	policy
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: stbryant@cisco.com
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: mpls-bounces@ietf.org
Errors-To: mpls-bounces@ietf.org

Clearly the expert can decline, otherwise there would be no point in then
bing in the process.

However it is expected that they behave reasonably and within the policy
guidelines stated in the RFC, and in the event that you disagree with their
decision, you can appeal to the IESG.

Stewart



BUSI ITALO wrote:
> Stewart,
>
> as far as I can understand from RFC 4446, a vendor can be prevented
> implementing proprietary innovative features by simply disapproving its
> codepoint request.
>
> Italo
>
>   
>> -----Original Message-----
>> From: Stewart Bryant [mailto:stbryant@cisco.com] 
>> Sent: Thursday, October 02, 2008 9:11 AM
>> To: BUSI ITALO
>> Cc: Shahram Davari; BOCCI Matthew; pwe3@ietf.org; 
>> mpls-tp@ietf.org; mpls@ietf.org; ccamp@ietf.org; l2vpn@ietf.org
>> Subject: Re: [mpls] [PWE3] FW: Changes to PW ACH Channel Type 
>> allocation policy
>>
>> BUSI ITALO wrote:
>>     
>>> I also support option 2
>>>
>>> The requirement is to allow a vendor to implement 
>>>       
>> proprietary innovative
>>     
>>> features.
>>>
>>> Italo
>>>
>>>   
>>>       
>> Italo
>>
>> How does option 1 prevent a vendor implementing proprietary 
>> innovative 
>> features?
>>
>> Stewart
>>
>>     
>
>
>   

_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls


From mpls-bounces@ietf.org  Fri Oct  3 01:11:05 2008
Return-Path: <mpls-bounces@ietf.org>
X-Original-To: mpls-archive@megatron.ietf.org
Delivered-To: ietfarch-mpls-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id CA8603A6B3D;
	Fri,  3 Oct 2008 01:11:05 -0700 (PDT)
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B3DF33A6AD8;
	Fri,  3 Oct 2008 01:11:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.249
X-Spam-Level: 
X-Spam-Status: No, score=-2.249 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, HELO_EQ_FR=0.35]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id zlcfeE3c8jme; Fri,  3 Oct 2008 01:11:02 -0700 (PDT)
Received: from smail5.alcatel.fr (smail5.alcatel.fr [64.208.49.27])
	by core3.amsl.com (Postfix) with ESMTP id 95E253A68DF;
	Fri,  3 Oct 2008 01:11:02 -0700 (PDT)
Received: from FRVELSBHS03.ad2.ad.alcatel.com (frvelsbhs03.ad2.ad.alcatel.com
	[155.132.6.75])
	by smail5.alcatel.fr (8.13.8/8.13.8/ICT) with ESMTP id m938B6wt000729; 
	Fri, 3 Oct 2008 10:11:06 +0200
Received: from FRVELSMBS21.ad2.ad.alcatel.com ([155.132.6.55]) by
	FRVELSBHS03.ad2.ad.alcatel.com with Microsoft
	SMTPSVC(6.0.3790.2499); Fri, 3 Oct 2008 10:11:06 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Fri, 3 Oct 2008 10:11:15 +0200
Message-ID: <6FD21B53861BF44AA90A288402036AB40193FA34@FRVELSMBS21.ad2.ad.alcatel.com>
In-Reply-To: <92a2396384f1f54f92005abb3728728f@mail.cph.tpack.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [mpls-tp] [PWE3] FW: Changes to PW ACH Channel
	Type	allocationpolicy
Thread-Index: AckkqLTHdNDdblepSIu2W52R3r7OPAAhRAtQ
References: <48E4DE0F.9020704@castlepoint.net>
	<92a2396384f1f54f92005abb3728728f@mail.cph.tpack.net>
From: "BUSI ITALO" <Italo.Busi@alcatel-lucent.it>
To: "Shahram Davari" <davari@tpack.com>, "Shane Amante" <shane@castlepoint.net>
X-OriginalArrivalTime: 03 Oct 2008 08:11:06.0805 (UTC)
	FILETIME=[960F5E50:01C9252F]
X-Scanned-By: MIMEDefang 2.57 on 155.132.188.13
Cc: l2vpn@ietf.org, mpls@ietf.org,
	BOCCI Matthew <Matthew.Bocci@alcatel-lucent.com>, ccamp@ietf.org,
	mpls-tp@ietf.org, pwe3@ietf.org
Subject: Re: [mpls] [mpls-tp] [PWE3] FW: Changes to PW ACH Channel
	Type	allocationpolicy
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mpls-bounces@ietf.org
Errors-To: mpls-bounces@ietf.org

See my comments in line marked with [ib] 

> -----Original Message-----
> From: Shahram Davari [mailto:davari@tpack.com] 
> Sent: Thursday, October 02, 2008 6:06 PM
> To: Shane Amante
> Cc: BUSI ITALO; Vishwas Manral; l2vpn@ietf.org; BOCCI 
> Matthew; mpls@ietf.org; ccamp@ietf.org; mpls-tp@ietf.org; 
> pwe3@ietf.org
> Subject: RE: [mpls-tp] [PWE3] FW: Changes to PW ACH Channel 
> Type allocationpolicy
> 
> Hi Shane,
> 
> Please see my response in-line. 
> 
> Best regards,
> Shahram
> 
> 
> -----Original Message-----
> From: Shane Amante [mailto:shane@castlepoint.net] 
> Sent: October-02-08 10:43 AM
> To: Shahram Davari
> Cc: BUSI ITALO; Vishwas Manral; l2vpn@ietf.org; BOCCI 
> Matthew; mpls@ietf.org; ccamp@ietf.org; mpls-tp@ietf.org; 
> pwe3@ietf.org
> Subject: Re: [mpls-tp] [PWE3] FW: Changes to PW ACH Channel 
> Type allocationpolicy
> 
> Shahram Davari wrote:
> > Hi,
> > 
> > I also prefer the method that Wishwas proposed. This has 
> many advantages:
> > 
> > 1) Allows vendors to not expose their proprietary 
> techniques to their competitors. 
> 
>  From the POV of an operator, this is actually a substantial 
> disadvantage.
> 
> [Shahram] OTOH it encourages more innovation and 
> differentiation by vendors.
> 

[ib] I fully agree with Shaharm. This is exactly the objective of the
requirement to allow vendor proprietary extensions.

> 
> > 2) reduces the load of reviewing by IETF and PWE3 
> 
> OTOH, the benefit of such reviews by the IETF and PWE3 is when 
> "commonality" among similar applications are discovered they can be 
> standardized, rather kept proprietary.
> 
> [Shahram] Not if the inventing vendor is not willing to do so.
> 
> 
> > 3) results a faster time to market, since no expert review 
> will be needed
> 
> True, to some extent.  But, IMHO, I would much rather see a 
> *slightly* 
> slower process involving a careful expert review and/or IETF 
> consensus 
> to make sure we're not: a) unnecessarily duplicating work; and, b) at 
> the same time, encouraging more standards-based approach.
> 
> 
> > 4) provides more codepoint space that the ACH channel type
> 
> This is false.  There is no shortage on ACH channel types today.
> [Shahram] You are correct. 16-bit is sufficient enough.
> 

[ib] I agree that the codepoint space is big enough and the codepoint
exhaustion is not a real issue.

However, with both option 1 and 2, we still have an open point to decide
how many codepoints we need to reserve for proprietary use and this is
not an easy task.

Option 3 has the advantage that we just need to allocate a single
codepoint.

> 
> > 5) only one VCCV ACH channel type needs to be configured in 
> each box for vendor specific filtering
>  >
> > The 2nd method has the first 3 advantages only, and the 
> first method has none of these advantages.
> 
> 
> Also, let's take a step back here.  Wasn't the whole point with the 
> joint ITU-T/IETF effort surrounding MPLS-TP to create an 
> environment in 
> which MPLS-TP could seamlessly interoperate within (existing) MPLS 
> environments?  I thought a fundamental part of that work is striving 
> towards creating a *standards-based* MPLS-TP data-plane, OAM, 
> signaling, 
> etc. mechanisms.  IMO, Vishwas' proposal and Matthew's 
> proposal #2 seems 
> to run contrary to that goal.
> 
> [Shahram] off course we should all encourage standards 
> methods. But we should provide a fast and reasonable 
> procedure for vendor specific protocols that don't affect 
> interoperability. I worry that in first method competitors 
> may vote down code point requests for commercial reasons.
> 

[ib] I agree. Standard actions is definitely the preferred approach to
enhance the technology and MUST be pursed as much as possible.
BTW this is why we are all spending huge efforts to progress standard
activities.
However there are cases where multi-vendor interoperability is not an
issue/requirement and fast time to market is a key requirement, where
standard action is not appropriate.

> -shane (speaking only for himself, not as co-chair)
> 
> 
> 
> 
_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls


From mpls-bounces@ietf.org  Fri Oct  3 01:22:37 2008
Return-Path: <mpls-bounces@ietf.org>
X-Original-To: mpls-archive@megatron.ietf.org
Delivered-To: ietfarch-mpls-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id AE8C128C1B7;
	Fri,  3 Oct 2008 01:22:37 -0700 (PDT)
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id D40C528B56A;
	Fri,  3 Oct 2008 01:22:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.249
X-Spam-Level: 
X-Spam-Status: No, score=-2.249 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, HELO_EQ_FR=0.35]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 7LpXvq-8QgM2; Fri,  3 Oct 2008 01:22:36 -0700 (PDT)
Received: from smail5.alcatel.fr (smail5.alcatel.fr [64.208.49.27])
	by core3.amsl.com (Postfix) with ESMTP id C90543A6B0E;
	Fri,  3 Oct 2008 01:22:35 -0700 (PDT)
Received: from FRVELSBHS03.ad2.ad.alcatel.com (frvelsbhs03.ad2.ad.alcatel.com
	[155.132.6.75])
	by smail5.alcatel.fr (8.13.8/8.13.8/ICT) with ESMTP id m938MwlM010221; 
	Fri, 3 Oct 2008 10:22:58 +0200
Received: from FRVELSMBS21.ad2.ad.alcatel.com ([155.132.6.55]) by
	FRVELSBHS03.ad2.ad.alcatel.com with Microsoft
	SMTPSVC(6.0.3790.2499); Fri, 3 Oct 2008 10:22:58 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Fri, 3 Oct 2008 10:23:08 +0200
Message-ID: <6FD21B53861BF44AA90A288402036AB40193FA3C@FRVELSMBS21.ad2.ad.alcatel.com>
In-Reply-To: <48E5D307.4080706@cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [mpls] [PWE3] FW: Changes to PW ACH Channel Type
	allocation	policy
Thread-Index: AcklL0WjA9uBcVgBQ0eUHDpTbHc5cQAATVSQ
References: <0458D2EE0C36744BABB36BE37805C29A029C6251@FRVELSMBS11.ad2.ad.alcatel.com>	<ba6305ea8b6f7b41bae8dcbb49c37c7c@mail.cph.tpack.net>
	<6FD21B53861BF44AA90A288402036AB40193F72F@FRVELSMBS21.ad2.ad.alcatel.com>
	<48E47400.2090309@cisco.com>
	<6FD21B53861BF44AA90A288402036AB40193FA17@FRVELSMBS21.ad2.ad.alcatel.com>
	<48E5D307.4080706@cisco.com>
From: "BUSI ITALO" <Italo.Busi@alcatel-lucent.it>
To: <stbryant@cisco.com>
X-OriginalArrivalTime: 03 Oct 2008 08:22:58.0838 (UTC)
	FILETIME=[3E76FB60:01C92531]
X-Scanned-By: MIMEDefang 2.57 on 155.132.188.13
Cc: l2vpn@ietf.org, BOCCI Matthew <Matthew.Bocci@alcatel-lucent.com>,
	mpls@ietf.org, ccamp@ietf.org, mpls-tp@ietf.org, pwe3@ietf.org,
	Shahram Davari <davari@tpack.com>
Subject: Re: [mpls] [PWE3] FW: Changes to PW ACH Channel Type
	allocation	policy
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mpls-bounces@ietf.org
Errors-To: mpls-bounces@ietf.org

I think that everybody has a different view about the meaning of "behave
reasonably".

Any guideline you can write to describe what is a reasonable behavior is
open to different interpreation.

I can appeal to the IESG and to whatever authority to enforce a
reasonable behavior but this will end up in an endless discussion.

Endless discussions are against fast time to market.

Italo

> -----Original Message-----
> From: Stewart Bryant [mailto:stbryant@cisco.com] 
> Sent: Friday, October 03, 2008 10:09 AM
> To: BUSI ITALO
> Cc: Shahram Davari; BOCCI Matthew; pwe3@ietf.org; 
> mpls-tp@ietf.org; mpls@ietf.org; ccamp@ietf.org; l2vpn@ietf.org
> Subject: Re: [mpls] [PWE3] FW: Changes to PW ACH Channel Type 
> allocation policy
> 
> Clearly the expert can decline, otherwise there would be no 
> point in then
> bing in the process.
> 
> However it is expected that they behave reasonably and within 
> the policy
> guidelines stated in the RFC, and in the event that you 
> disagree with their
> decision, you can appeal to the IESG.
> 
> Stewart
> 
> 
> 
> BUSI ITALO wrote:
> > Stewart,
> >
> > as far as I can understand from RFC 4446, a vendor can be prevented
> > implementing proprietary innovative features by simply 
> disapproving its
> > codepoint request.
> >
> > Italo
> >
> >   
> >> -----Original Message-----
> >> From: Stewart Bryant [mailto:stbryant@cisco.com] 
> >> Sent: Thursday, October 02, 2008 9:11 AM
> >> To: BUSI ITALO
> >> Cc: Shahram Davari; BOCCI Matthew; pwe3@ietf.org; 
> >> mpls-tp@ietf.org; mpls@ietf.org; ccamp@ietf.org; l2vpn@ietf.org
> >> Subject: Re: [mpls] [PWE3] FW: Changes to PW ACH Channel Type 
> >> allocation policy
> >>
> >> BUSI ITALO wrote:
> >>     
> >>> I also support option 2
> >>>
> >>> The requirement is to allow a vendor to implement 
> >>>       
> >> proprietary innovative
> >>     
> >>> features.
> >>>
> >>> Italo
> >>>
> >>>   
> >>>       
> >> Italo
> >>
> >> How does option 1 prevent a vendor implementing proprietary 
> >> innovative 
> >> features?
> >>
> >> Stewart
> >>
> >>     
> >
> >
> >   
> 
> 
_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls


From mpls-bounces@ietf.org  Fri Oct  3 01:45:49 2008
Return-Path: <mpls-bounces@ietf.org>
X-Original-To: mpls-archive@megatron.ietf.org
Delivered-To: ietfarch-mpls-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 642043A6AD8;
	Fri,  3 Oct 2008 01:45:49 -0700 (PDT)
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 35F123A6AE9;
	Fri,  3 Oct 2008 01:45:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.799
X-Spam-Level: 
X-Spam-Status: No, score=-3.799 tagged_above=-999 required=5 tests=[AWL=2.800, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id GDmMxSliKv0G; Fri,  3 Oct 2008 01:45:46 -0700 (PDT)
Received: from demumfd001.nsn-inter.net (demumfd001.nsn-inter.net
	[217.115.75.233])
	by core3.amsl.com (Postfix) with ESMTP id 78E853A67E3;
	Fri,  3 Oct 2008 01:45:46 -0700 (PDT)
Received: from demuprx017.emea.nsn-intra.net ([10.150.129.56])
	by demumfd001.nsn-inter.net (8.12.11.20060308/8.12.11) with ESMTP id
	m938jsQ9025137
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL);
	Fri, 3 Oct 2008 10:45:54 +0200
Received: from demuexc022.nsn-intra.net (webmail.nsn-intra.net [10.150.128.35])
	by demuprx017.emea.nsn-intra.net (8.12.11.20060308/8.12.11) with ESMTP
	id m938jsWx023871; Fri, 3 Oct 2008 10:45:54 +0200
Received: from DEMUEXC030.nsn-intra.net ([10.150.128.57]) by
	demuexc022.nsn-intra.net with Microsoft SMTPSVC(6.0.3790.3959); 
	Fri, 3 Oct 2008 10:45:55 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Fri, 3 Oct 2008 10:45:47 +0200
Message-ID: <43284B5A95E36B4AB4A91EBA4E0FC31ED75EAD@DEMUEXC030.nsn-intra.net>
In-Reply-To: <6FD21B53861BF44AA90A288402036AB40193FA34@FRVELSMBS21.ad2.ad.alcatel.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [PWE3] [mpls-tp] FW: Changes to PW ACH
	ChannelType	allocationpolicy
Thread-Index: AckkqLTHdNDdblepSIu2W52R3r7OPAAhRAtQAAGjQQA=
References: <48E4DE0F.9020704@castlepoint.net><92a2396384f1f54f92005abb3728728f@mail.cph.tpack.net>
	<6FD21B53861BF44AA90A288402036AB40193FA34@FRVELSMBS21.ad2.ad.alcatel.com>
From: "Sprecher, Nurit (NSN - IL/Hod HaSharon)" <nurit.sprecher@nsn.com>
To: "ext BUSI ITALO" <Italo.Busi@alcatel-lucent.it>,
	"Shahram Davari" <davari@tpack.com>, "Shane Amante" <shane@castlepoint.net>
X-OriginalArrivalTime: 03 Oct 2008 08:45:55.0068 (UTC)
	FILETIME=[72C303C0:01C92534]
X-purgate: clean
X-purgate: This mail is considered clean
X-purgate-type: clean
X-purgate-Ad: Checked for Spam by eleven - eXpurgate www.eXpurgate.net
X-purgate-ID: 151667::081003104554-224A4BB0-8C814B94/0-0/0-15
X-purgate-size: 5167/0
Cc: l2vpn@ietf.org, mpls@ietf.org,
	BOCCI Matthew <Matthew.Bocci@alcatel-lucent.com>, ccamp@ietf.org,
	mpls-tp@ietf.org, pwe3@ietf.org
Subject: Re: [mpls] [PWE3] [mpls-tp] FW: Changes to PW ACH
	ChannelType	allocationpolicy
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mpls-bounces@ietf.org
Errors-To: mpls-bounces@ietf.org

" it encourages more innovation and differentiation by vendors". 
If there are some innovations (which is of course encouraged), why not
pushing it to be a standard behavior? 
I am pretty sure SPs will be happier to see it working in multi vendor
environment than as a proprietary solution that is supported by one
vendor only.  

-----Original Message-----
From: pwe3-bounces@ietf.org [mailto:pwe3-bounces@ietf.org] On Behalf Of
ext BUSI ITALO
Sent: Friday, October 03, 2008 11:11
To: Shahram Davari; Shane Amante
Cc: l2vpn@ietf.org; mpls@ietf.org; BOCCI Matthew; ccamp@ietf.org;
mpls-tp@ietf.org; pwe3@ietf.org
Subject: Re: [PWE3] [mpls-tp] FW: Changes to PW ACH ChannelType
allocationpolicy

See my comments in line marked with [ib] 

> -----Original Message-----
> From: Shahram Davari [mailto:davari@tpack.com] 
> Sent: Thursday, October 02, 2008 6:06 PM
> To: Shane Amante
> Cc: BUSI ITALO; Vishwas Manral; l2vpn@ietf.org; BOCCI 
> Matthew; mpls@ietf.org; ccamp@ietf.org; mpls-tp@ietf.org; 
> pwe3@ietf.org
> Subject: RE: [mpls-tp] [PWE3] FW: Changes to PW ACH Channel 
> Type allocationpolicy
> 
> Hi Shane,
> 
> Please see my response in-line. 
> 
> Best regards,
> Shahram
> 
> 
> -----Original Message-----
> From: Shane Amante [mailto:shane@castlepoint.net] 
> Sent: October-02-08 10:43 AM
> To: Shahram Davari
> Cc: BUSI ITALO; Vishwas Manral; l2vpn@ietf.org; BOCCI 
> Matthew; mpls@ietf.org; ccamp@ietf.org; mpls-tp@ietf.org; 
> pwe3@ietf.org
> Subject: Re: [mpls-tp] [PWE3] FW: Changes to PW ACH Channel 
> Type allocationpolicy
> 
> Shahram Davari wrote:
> > Hi,
> > 
> > I also prefer the method that Wishwas proposed. This has 
> many advantages:
> > 
> > 1) Allows vendors to not expose their proprietary 
> techniques to their competitors. 
> 
>  From the POV of an operator, this is actually a substantial 
> disadvantage.
> 
> [Shahram] OTOH it encourages more innovation and 
> differentiation by vendors.
> 

[ib] I fully agree with Shaharm. This is exactly the objective of the
requirement to allow vendor proprietary extensions.

> 
> > 2) reduces the load of reviewing by IETF and PWE3 
> 
> OTOH, the benefit of such reviews by the IETF and PWE3 is when 
> "commonality" among similar applications are discovered they can be 
> standardized, rather kept proprietary.
> 
> [Shahram] Not if the inventing vendor is not willing to do so.
> 
> 
> > 3) results a faster time to market, since no expert review 
> will be needed
> 
> True, to some extent.  But, IMHO, I would much rather see a 
> *slightly* 
> slower process involving a careful expert review and/or IETF 
> consensus 
> to make sure we're not: a) unnecessarily duplicating work; and, b) at 
> the same time, encouraging more standards-based approach.
> 
> 
> > 4) provides more codepoint space that the ACH channel type
> 
> This is false.  There is no shortage on ACH channel types today.
> [Shahram] You are correct. 16-bit is sufficient enough.
> 

[ib] I agree that the codepoint space is big enough and the codepoint
exhaustion is not a real issue.

However, with both option 1 and 2, we still have an open point to decide
how many codepoints we need to reserve for proprietary use and this is
not an easy task.

Option 3 has the advantage that we just need to allocate a single
codepoint.

> 
> > 5) only one VCCV ACH channel type needs to be configured in 
> each box for vendor specific filtering
>  >
> > The 2nd method has the first 3 advantages only, and the 
> first method has none of these advantages.
> 
> 
> Also, let's take a step back here.  Wasn't the whole point with the 
> joint ITU-T/IETF effort surrounding MPLS-TP to create an 
> environment in 
> which MPLS-TP could seamlessly interoperate within (existing) MPLS 
> environments?  I thought a fundamental part of that work is striving 
> towards creating a *standards-based* MPLS-TP data-plane, OAM, 
> signaling, 
> etc. mechanisms.  IMO, Vishwas' proposal and Matthew's 
> proposal #2 seems 
> to run contrary to that goal.
> 
> [Shahram] off course we should all encourage standards 
> methods. But we should provide a fast and reasonable 
> procedure for vendor specific protocols that don't affect 
> interoperability. I worry that in first method competitors 
> may vote down code point requests for commercial reasons.
> 

[ib] I agree. Standard actions is definitely the preferred approach to
enhance the technology and MUST be pursed as much as possible.
BTW this is why we are all spending huge efforts to progress standard
activities.
However there are cases where multi-vendor interoperability is not an
issue/requirement and fast time to market is a key requirement, where
standard action is not appropriate.

> -shane (speaking only for himself, not as co-chair)
> 
> 
> 
> 
_______________________________________________
pwe3 mailing list
pwe3@ietf.org
https://www.ietf.org/mailman/listinfo/pwe3
_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls


From mpls-bounces@ietf.org  Fri Oct  3 01:54:47 2008
Return-Path: <mpls-bounces@ietf.org>
X-Original-To: mpls-archive@megatron.ietf.org
Delivered-To: ietfarch-mpls-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id D15773A6A59;
	Fri,  3 Oct 2008 01:54:47 -0700 (PDT)
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 793173A6AE9;
	Fri,  3 Oct 2008 01:54:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id YXcPU6UFx3VK; Fri,  3 Oct 2008 01:54:45 -0700 (PDT)
Received: from sj-iport-5.cisco.com (sj-iport-5.cisco.com [171.68.10.87])
	by core3.amsl.com (Postfix) with ESMTP id 794193A6966;
	Fri,  3 Oct 2008 01:54:45 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,355,1220227200"; d="scan'208";a="47653747"
Received: from sj-dkim-2.cisco.com ([171.71.179.186])
	by sj-iport-5.cisco.com with ESMTP; 03 Oct 2008 08:55:13 +0000
Received: from sj-core-1.cisco.com (sj-core-1.cisco.com [171.71.177.237])
	by sj-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id m938tDS5021618; 
	Fri, 3 Oct 2008 01:55:13 -0700
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com
	[128.107.191.63])
	by sj-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m938tDQt028843;
	Fri, 3 Oct 2008 08:55:13 GMT
Received: from xfe-sjc-211.amer.cisco.com ([171.70.151.174]) by
	xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 3 Oct 2008 01:55:13 -0700
Received: from [10.19.202.51] ([10.19.202.51]) by xfe-sjc-211.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 3 Oct 2008 01:55:13 -0700
In-Reply-To: <0458D2EE0C36744BABB36BE37805C29A029C6251@FRVELSMBS11.ad2.ad.alcatel.com>
References: <0458D2EE0C36744BABB36BE37805C29A029C6251@FRVELSMBS11.ad2.ad.alcatel.com>
Mime-Version: 1.0 (Apple Message framework v753.1)
Message-Id: <424031F9-4D82-43E7-AF0A-8EBD855EB8AC@cisco.com>
From: Sam Aldrin <aldrin@cisco.com>
Date: Fri, 3 Oct 2008 01:55:11 -0700
To: BOCCI Matthew <Matthew.Bocci@alcatel-lucent.com>
X-Mailer: Apple Mail (2.753.1)
X-OriginalArrivalTime: 03 Oct 2008 08:55:13.0380 (UTC)
	FILETIME=[BF8AAA40:01C92535]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=3709; t=1223024113;
	x=1223888113; c=relaxed/simple; s=sjdkim2002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=aldrin@cisco.com;
	z=From:=20Sam=20Aldrin=20<aldrin@cisco.com>
	|Subject:=20Re=3A=20[mpls]=20FW=3A=20[PWE3]=20Changes=20to=
	20PW=20ACH=20Channel=20Type=20allocation=20policy |Sender:=20;
	bh=ACl0Vapr6AqhqO7j4Jsr6iBBVREH9ok7mLsGWMS/7gI=;
	b=Fo4vBBSw/pd8M1TFNkm0LLbAF6L9BV2Fn6Sl5FRjJAt2UwuOJFQPJeBDDn
	RVdMFuY6/x44ozrKk8p+ZiC4tkgK/50XNL8UD10Vh9hkUPxc+Myzifhc5hB9
	zO39mKe06a;
Authentication-Results: sj-dkim-2; header.From=aldrin@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim2002 verified; ); 
Cc: l2vpn@ietf.org, mpls@ietf.org, ccamp@ietf.org, pwe3@ietf.org,
	mpls-tp@ietf.org
Subject: Re: [mpls] FW: [PWE3] Changes to PW ACH Channel Type allocation
	policy
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: mpls-bounces@ietf.org
Errors-To: mpls-bounces@ietf.org

Agree on #1.

-sam
On Sep 30, 2008, at 9:23 AM, BOCCI Matthew wrote:

> The PWE3 chairs would like feedback on proposed changes to the
> allocation policy for the PW ACH codepoint registry. Please see the
> email below, and provide any feedback copying the PWE3 list.
>
> Best regards
>
> Matthew
>
> -----Original Message-----
> From: pwe3-bounces@ietf.org [mailto:pwe3-bounces@ietf.org] On  
> Behalf Of
> BOCCI Matthew
> Sent: 25 September 2008 16:36
> To: pwe3@ietf.org
> Subject: [PWE3] Changes to PW ACH Channel Type allocation policy
>
>
>
> The current IANA allocation policy for the PW associated channel type
> registry is by IETF consensus. This policy was chosen in RFC 4385  
> based
> on WG consensus that since the associated channel exists in the data
> path, and VCCV packets are typically processed by the control  
> processor
> on many PEs, it was prudent for the IETF to maintain strict control  
> over
> what types of channels were allocated and to ensure that they complied
> to the PWE3 architecture.
>
> However, a need has been identified to provide a more flexible  
> approach
> to allocating code points for VCCV channel types. This has partly  
> arisen
> from the MPLS-TP work, where MPLS would be deployed in a transport
> network and where a much wider range of applications for the PW
> associated channel is envisioned, and partialy from a desire to extend
> the OAM capabilities for regular MPLS. We can support MPLS-TP and
> general MPLS apps with the current policy which requires standards
> action.
>
> However we are receiving requests to allow proprietary OAM and  
> signaling
> protocols to be used in transport applications, and need to decide on
> the best way forward. We considered providing extension mechanisms
> within the standards track protocols, but believe that the standards
> track protocols would be much cleaner if the proprietary protocols ran
> on their own ACH code points.
>
> Note that we are talking about vendor protocols here. Other SDOs would
> be required to publish an RFC and would only be allocated an ACH  
> through
> Standards Action.
>
> There are two ways to address the requests for proprietary protocol  
> ACH
> code points:
>
> 1) Allow a range of the associated channel type registry to be  
> allocated
> through expert review. Guidelines would be provided for the expert
> reviewer to guide them in assessing the request, which would have  
> to be
> made in the form of an internet draft, while making sure that the
> request is dealt with in a timely and fair manner. This policy would
> include hurdles with regard to security, congestion etc that would be
> derived from those specified in the VCCV design.
>
> 2) Allow a range of the associated channel type registry to be  
> allocated
> on a first-come-first-served basis. This does not provide the level of
> control that expert review provides, but this is balanced to some  
> degree
> by the fact that the VCCV channel type is indicated in the data path,
> and so a PE can choose to discard or rate limit VCCV packets on an
> unrecognised associated channel.
>
> Any change to the ACH allocation policy would be outlined in the GE- 
> ACH
> draft, which would update RFC 4385.
>
> We would appreciate feedback on the list as to which approach the WG
> prefers.
>
> Regards,
>
> Stewart and Matthew
>
> _______________________________________________
> pwe3 mailing list
> pwe3@ietf.org
> https://www.ietf.org/mailman/listinfo/pwe3
> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls

_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls


From mpls-bounces@ietf.org  Fri Oct  3 02:46:39 2008
Return-Path: <mpls-bounces@ietf.org>
X-Original-To: mpls-archive@megatron.ietf.org
Delivered-To: ietfarch-mpls-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 924713A68FA;
	Fri,  3 Oct 2008 02:46:39 -0700 (PDT)
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id F0E333A6AF4;
	Fri,  3 Oct 2008 02:46:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.392
X-Spam-Level: 
X-Spam-Status: No, score=-1.392 tagged_above=-999 required=5 tests=[AWL=1.207, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id HUP8LpsXu1Wu; Fri,  3 Oct 2008 02:46:37 -0700 (PDT)
Received: from mk-outboundfilter-5.mail.uk.tiscali.com
	(mk-outboundfilter-5.mail.uk.tiscali.com [212.74.114.1])
	by core3.amsl.com (Postfix) with ESMTP id 2541D3A68FA;
	Fri,  3 Oct 2008 02:46:35 -0700 (PDT)
X-Trace: 89108553/mk-outboundfilter-5.mail.uk.tiscali.com/PIPEX/$PIPEX-ACCEPTED/pipex-customers/62.188.122.214
X-SBRS: None
X-RemoteIP: 62.188.122.214
X-IP-MAIL-FROM: nwnetworks@dial.pipex.com
X-IP-BHB: Once
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvAEADqH5Ug+vHrW/2dsb2JhbACDUjqIZq8EA4Fl
X-IronPort-AV: E=Sophos;i="4.33,356,1220223600"; d="scan'208";a="89108553"
X-IP-Direction: IN
Received: from 1cust214.tnt30.lnd3.gbr.da.uu.net (HELO allison)
	([62.188.122.214])
	by smtp.pipex.tiscali.co.uk with SMTP; 03 Oct 2008 10:46:47 +0100
Message-ID: <008401c92533$862e2260$0601a8c0@allison>
From: "Tom Petch" <nwnetworks@dial.pipex.com>
To: "BOCCI Matthew" <Matthew.Bocci@alcatel-lucent.com>, <pwe3@ietf.org>,
	<mpls-tp@ietf.org>, <mpls@ietf.org>, <ccamp@ietf.org>, <l2vpn@ietf.org>
References: <0458D2EE0C36744BABB36BE37805C29A029C6251@FRVELSMBS11.ad2.ad.alcatel.com>
Date: Fri, 3 Oct 2008 09:33:56 +0200
MIME-Version: 1.0
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Subject: Re: [mpls] FW: [PWE3] Changes to PW ACH Channel Type allocation
	policy
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Tom Petch <nwnetworks@dial.pipex.com>
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mpls-bounces@ietf.org
Errors-To: mpls-bounces@ietf.org

Option 1

It is the simplest and does the job (as far as I can see into the future).

Tom Petch


----- Original Message -----
From: "BOCCI Matthew" <Matthew.Bocci@alcatel-lucent.com>
To: <pwe3@ietf.org>; <mpls-tp@ietf.org>; <mpls@ietf.org>; <ccamp@ietf.org>;
<l2vpn@ietf.org>
Sent: Tuesday, September 30, 2008 6:23 PM
Subject: [mpls] FW: [PWE3] Changes to PW ACH Channel Type allocation policy


> The PWE3 chairs would like feedback on proposed changes to the
> allocation policy for the PW ACH codepoint registry. Please see the
> email below, and provide any feedback copying the PWE3 list.
>
> Best regards
>
> Matthew
>
> -----Original Message-----
> From: pwe3-bounces@ietf.org [mailto:pwe3-bounces@ietf.org] On Behalf Of
> BOCCI Matthew
> Sent: 25 September 2008 16:36
> To: pwe3@ietf.org
> Subject: [PWE3] Changes to PW ACH Channel Type allocation policy
>
>
>
> The current IANA allocation policy for the PW associated channel type
> registry is by IETF consensus. This policy was chosen in RFC 4385 based
> on WG consensus that since the associated channel exists in the data
> path, and VCCV packets are typically processed by the control processor
> on many PEs, it was prudent for the IETF to maintain strict control over
> what types of channels were allocated and to ensure that they complied
> to the PWE3 architecture.
>
> However, a need has been identified to provide a more flexible approach
> to allocating code points for VCCV channel types. This has partly arisen
> from the MPLS-TP work, where MPLS would be deployed in a transport
> network and where a much wider range of applications for the PW
> associated channel is envisioned, and partialy from a desire to extend
> the OAM capabilities for regular MPLS. We can support MPLS-TP and
> general MPLS apps with the current policy which requires standards
> action.
>
> However we are receiving requests to allow proprietary OAM and signaling
> protocols to be used in transport applications, and need to decide on
> the best way forward. We considered providing extension mechanisms
> within the standards track protocols, but believe that the standards
> track protocols would be much cleaner if the proprietary protocols ran
> on their own ACH code points.
>
> Note that we are talking about vendor protocols here. Other SDOs would
> be required to publish an RFC and would only be allocated an ACH through
> Standards Action.
>
> There are two ways to address the requests for proprietary protocol ACH
> code points:
>
> 1) Allow a range of the associated channel type registry to be allocated
> through expert review. Guidelines would be provided for the expert
> reviewer to guide them in assessing the request, which would have to be
> made in the form of an internet draft, while making sure that the
> request is dealt with in a timely and fair manner. This policy would
> include hurdles with regard to security, congestion etc that would be
> derived from those specified in the VCCV design.
>
> 2) Allow a range of the associated channel type registry to be allocated
> on a first-come-first-served basis. This does not provide the level of
> control that expert review provides, but this is balanced to some degree
> by the fact that the VCCV channel type is indicated in the data path,
> and so a PE can choose to discard or rate limit VCCV packets on an
> unrecognised associated channel.
>
> Any change to the ACH allocation policy would be outlined in the GE-ACH
> draft, which would update RFC 4385.
>
> We would appreciate feedback on the list as to which approach the WG
> prefers.
>
> Regards,
>
> Stewart and Matthew
>
> _______________________________________________
> pwe3 mailing list
> pwe3@ietf.org
> https://www.ietf.org/mailman/listinfo/pwe3
> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls

_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls


From mpls-bounces@ietf.org  Fri Oct  3 06:19:22 2008
Return-Path: <mpls-bounces@ietf.org>
X-Original-To: mpls-archive@megatron.ietf.org
Delivered-To: ietfarch-mpls-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 0889B3A68AE;
	Fri,  3 Oct 2008 06:19:22 -0700 (PDT)
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id EFE6228C14C;
	Tue, 30 Sep 2008 09:34:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.099
X-Spam-Level: 
X-Spam-Status: No, score=-1.099 tagged_above=-999 required=5 tests=[AWL=0.433, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, RCVD_NUMERIC_HELO=2.067]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id vqBItw2Iw63o; Tue, 30 Sep 2008 09:33:59 -0700 (PDT)
Received: from smtp2.smtp.bt.com (smtp2.smtp.bt.com [217.32.164.150])
	by core3.amsl.com (Postfix) with ESMTP id 39D3B3A6B67;
	Tue, 30 Sep 2008 09:33:58 -0700 (PDT)
Received: from E03MVZ2-UKDY.domain1.systemhost.net ([193.113.30.65]) by
	smtp2.smtp.bt.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 30 Sep 2008 17:34:17 +0100
Received: from 217.32.164.172 ([217.32.164.172]) by
	E03MVZ2-UKDY.domain1.systemhost.net ([193.113.30.120]) via
	Exchange Front-End Server mail.bt.com ([193.113.197.26]) with
	Microsoft Exchange Server HTTP-DAV ; Tue, 30 Sep 2008 16:34:16 +0000
User-Agent: Microsoft-Entourage/12.12.0.080729
Date: Tue, 30 Sep 2008 12:34:16 -0400
From: "Thomas D. Nadeau" <tom.nadeau@bt.com>
To: BOCCI Matthew <Matthew.Bocci@alcatel-lucent.com>, <pwe3@ietf.org>,
	<mpls-tp@ietf.org>, <mpls@ietf.org>, <ccamp@ietf.org>, <l2vpn@ietf.org>
Message-ID: <C507CD48.E0F0%tom.nadeau@bt.com>
Thread-Topic: [mpls-tp] FW: [PWE3] Changes to PW ACH Channel Type allocation
	policy
Thread-Index: AckeEgHxlvy9zCPET0WFoA5KKm0awgBET6egAP0oyGAAAJ9TrA==
In-Reply-To: <0458D2EE0C36744BABB36BE37805C29A029C6251@FRVELSMBS11.ad2.ad.alcatel.com>
Mime-version: 1.0
X-OriginalArrivalTime: 30 Sep 2008 16:34:17.0745 (UTC)
	FILETIME=[6205F810:01C9231A]
X-Mailman-Approved-At: Fri, 03 Oct 2008 06:19:21 -0700
Subject: Re: [mpls] [mpls-tp] FW: [PWE3] Changes to PW ACH Channel Type
 allocation policy
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mpls-bounces@ietf.org
Errors-To: mpls-bounces@ietf.org


    While a bit slower than the newer approach proposed, I still prefer the
existing mechanism requiring expert review and IETF consensus.  I don't see
why having to justify the case for a new code point allocation is such a
cumbersome process. The only trouble point I see is where folks might want
to allocate proprietary extension points, in which case consensus may be
difficult to arrive at. In these cases, it might be useful to carve out some
sub-set of the space for such allocations and only require expert review
without IETF consensus for this allocation.

    --Tom



On 9/30/08 12:23 PM, "BOCCI Matthew" <Matthew.Bocci@alcatel-lucent.com>
wrote:

> The PWE3 chairs would like feedback on proposed changes to the
> allocation policy for the PW ACH codepoint registry. Please see the
> email below, and provide any feedback copying the PWE3 list.
> 
> Best regards
> 
> Matthew
> 
> -----Original Message-----
> From: pwe3-bounces@ietf.org [mailto:pwe3-bounces@ietf.org] On Behalf Of
> BOCCI Matthew
> Sent: 25 September 2008 16:36
> To: pwe3@ietf.org
> Subject: [PWE3] Changes to PW ACH Channel Type allocation policy
> 
> 
>  
> The current IANA allocation policy for the PW associated channel type
> registry is by IETF consensus. This policy was chosen in RFC 4385 based
> on WG consensus that since the associated channel exists in the data
> path, and VCCV packets are typically processed by the control processor
> on many PEs, it was prudent for the IETF to maintain strict control over
> what types of channels were allocated and to ensure that they complied
> to the PWE3 architecture.
> 
> However, a need has been identified to provide a more flexible approach
> to allocating code points for VCCV channel types. This has partly arisen
> from the MPLS-TP work, where MPLS would be deployed in a transport
> network and where a much wider range of applications for the PW
> associated channel is envisioned, and partialy from a desire to extend
> the OAM capabilities for regular MPLS. We can support MPLS-TP and
> general MPLS apps with the current policy which requires standards
> action.
> 
> However we are receiving requests to allow proprietary OAM and signaling
> protocols to be used in transport applications, and need to decide on
> the best way forward. We considered providing extension mechanisms
> within the standards track protocols, but believe that the standards
> track protocols would be much cleaner if the proprietary protocols ran
> on their own ACH code points.
> 
> Note that we are talking about vendor protocols here. Other SDOs would
> be required to publish an RFC and would only be allocated an ACH through
> Standards Action.
> 
> There are two ways to address the requests for proprietary protocol ACH
> code points:
> 
> 1) Allow a range of the associated channel type registry to be allocated
> through expert review. Guidelines would be provided for the expert
> reviewer to guide them in assessing the request, which would have to be
> made in the form of an internet draft, while making sure that the
> request is dealt with in a timely and fair manner. This policy would
> include hurdles with regard to security, congestion etc that would be
> derived from those specified in the VCCV design.
> 
> 2) Allow a range of the associated channel type registry to be allocated
> on a first-come-first-served basis. This does not provide the level of
> control that expert review provides, but this is balanced to some degree
> by the fact that the VCCV channel type is indicated in the data path,
> and so a PE can choose to discard or rate limit VCCV packets on an
> unrecognised associated channel.
> 
> Any change to the ACH allocation policy would be outlined in the GE-ACH
> draft, which would update RFC 4385.
> 
> We would appreciate feedback on the list as to which approach the WG
> prefers.
> 
> Regards,
> 
> Stewart and Matthew
> 
> _______________________________________________
> pwe3 mailing list
> pwe3@ietf.org
> https://www.ietf.org/mailman/listinfo/pwe3
> _______________________________________________
> mpls-tp mailing list
> mpls-tp@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls-tp

_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls


From mpls-bounces@ietf.org  Fri Oct  3 06:19:22 2008
Return-Path: <mpls-bounces@ietf.org>
X-Original-To: mpls-archive@megatron.ietf.org
Delivered-To: ietfarch-mpls-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id A66DE28C0DB;
	Fri,  3 Oct 2008 06:19:22 -0700 (PDT)
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id BA3193A6768;
	Wed,  1 Oct 2008 07:38:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, MISSING_MIMEOLE=0.001]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id KWzHKIjOVAhS; Wed,  1 Oct 2008 07:38:05 -0700 (PDT)
Received: from tpack.net (ip18.tpack.net [213.173.228.18])
	by core3.amsl.com (Postfix) with ESMTP id C39793A6405;
	Wed,  1 Oct 2008 07:38:03 -0700 (PDT)
Received: from [192.168.111.2] (account shd@tpack.net)
	by tpack.net (CommuniGate Pro IMAP 5.1.12)
	with XMIT id 817490; Wed, 01 Oct 2008 16:37:08 +0200
Date: Wed, 01 Oct 2008 10:34:29 -0400
Organization: Tpack A/S
Message-Id: <ba6305ea8b6f7b41bae8dcbb49c37c7c@mail.cph.tpack.net>
In-Reply-To: <0458D2EE0C36744BABB36BE37805C29A029C6251@FRVELSMBS11.ad2.ad.alcatel.com>
MIME-Version: 1.0
Thread-Topic: [PWE3] FW:  Changes to PW ACH Channel Type allocation policy
Priority: Normal
Importance: normal
X-MSMail-Priority: normal
X-Priority: 3
Sensitivity: Normal
Thread-Index: AckeEgHxlvy9zCPET0WFoA5KKm0awgBET6egAP0oyGAALpdOcA==
From: "Shahram Davari" <davari@tpack.com>
To: "BOCCI Matthew" <Matthew.Bocci@alcatel-lucent.com>, 
	"pwe3@ietf.org" <pwe3@ietf.org>, "mpls-tp@ietf.org" <mpls-tp@ietf.org>, 
	"mpls@ietf.org" <mpls@ietf.org>, "ccamp@ietf.org" <ccamp@ietf.org>, 
	"l2vpn@ietf.org" <l2vpn@ietf.org>
X-MAPI-LastModified: Wed, 01 Oct 2008 10:34:29 -0400
X-Mailer: CommuniGate Pro MAPI Connector 1.2.9/1.2.12
X-Mailman-Approved-At: Fri, 03 Oct 2008 06:19:21 -0700
Subject: Re: [mpls] [PWE3] FW: Changes to PW ACH Channel Type allocation
	policy
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mpls-bounces@ietf.org
Errors-To: mpls-bounces@ietf.org

Hi Mathew,

I support option 2, since a terminating node that doesn't understand the VCCV channel type can always drop it. This would allow more innovation and faster time to market.

Best regards,
Shahram


-----Original Message-----
From: pwe3-bounces@ietf.org [mailto:pwe3-bounces@ietf.org] On Behalf Of BOCCI Matthew
Sent: September-30-08 12:23 PM
To: pwe3@ietf.org; mpls-tp@ietf.org; mpls@ietf.org; ccamp@ietf.org; l2vpn@ietf.org
Subject: [PWE3] FW: Changes to PW ACH Channel Type allocation policy

The PWE3 chairs would like feedback on proposed changes to the
allocation policy for the PW ACH codepoint registry. Please see the
email below, and provide any feedback copying the PWE3 list.

Best regards

Matthew

-----Original Message-----
From: pwe3-bounces@ietf.org [mailto:pwe3-bounces@ietf.org] On Behalf Of
BOCCI Matthew
Sent: 25 September 2008 16:36
To: pwe3@ietf.org
Subject: [PWE3] Changes to PW ACH Channel Type allocation policy


 
The current IANA allocation policy for the PW associated channel type
registry is by IETF consensus. This policy was chosen in RFC 4385 based
on WG consensus that since the associated channel exists in the data
path, and VCCV packets are typically processed by the control processor
on many PEs, it was prudent for the IETF to maintain strict control over
what types of channels were allocated and to ensure that they complied
to the PWE3 architecture.

However, a need has been identified to provide a more flexible approach
to allocating code points for VCCV channel types. This has partly arisen
from the MPLS-TP work, where MPLS would be deployed in a transport
network and where a much wider range of applications for the PW
associated channel is envisioned, and partialy from a desire to extend
the OAM capabilities for regular MPLS. We can support MPLS-TP and
general MPLS apps with the current policy which requires standards
action.

However we are receiving requests to allow proprietary OAM and signaling
protocols to be used in transport applications, and need to decide on
the best way forward. We considered providing extension mechanisms
within the standards track protocols, but believe that the standards
track protocols would be much cleaner if the proprietary protocols ran
on their own ACH code points.

Note that we are talking about vendor protocols here. Other SDOs would
be required to publish an RFC and would only be allocated an ACH through
Standards Action.

There are two ways to address the requests for proprietary protocol ACH
code points:

1) Allow a range of the associated channel type registry to be allocated
through expert review. Guidelines would be provided for the expert
reviewer to guide them in assessing the request, which would have to be
made in the form of an internet draft, while making sure that the
request is dealt with in a timely and fair manner. This policy would
include hurdles with regard to security, congestion etc that would be
derived from those specified in the VCCV design.

2) Allow a range of the associated channel type registry to be allocated
on a first-come-first-served basis. This does not provide the level of
control that expert review provides, but this is balanced to some degree
by the fact that the VCCV channel type is indicated in the data path,
and so a PE can choose to discard or rate limit VCCV packets on an
unrecognised associated channel.

Any change to the ACH allocation policy would be outlined in the GE-ACH
draft, which would update RFC 4385.

We would appreciate feedback on the list as to which approach the WG
prefers.

Regards,

Stewart and Matthew

_______________________________________________
pwe3 mailing list
pwe3@ietf.org
https://www.ietf.org/mailman/listinfo/pwe3
_______________________________________________
pwe3 mailing list
pwe3@ietf.org
https://www.ietf.org/mailman/listinfo/pwe3



_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls


From mpls-bounces@ietf.org  Fri Oct  3 06:19:23 2008
Return-Path: <mpls-bounces@ietf.org>
X-Original-To: mpls-archive@megatron.ietf.org
Delivered-To: ietfarch-mpls-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 3BC6D28C10E;
	Fri,  3 Oct 2008 06:19:23 -0700 (PDT)
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 7E77E3A69DF;
	Wed,  1 Oct 2008 10:21:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.837
X-Spam-Level: 
X-Spam-Status: No, score=-0.837 tagged_above=-999 required=5 tests=[AWL=0.696, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, RCVD_NUMERIC_HELO=2.067]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id D3vUTKUwJvRz; Wed,  1 Oct 2008 10:21:32 -0700 (PDT)
Received: from smtp4.smtp.bt.com (smtp4.smtp.bt.com [217.32.164.151])
	by core3.amsl.com (Postfix) with ESMTP id 713AB3A6856;
	Wed,  1 Oct 2008 10:21:32 -0700 (PDT)
Received: from E03MVZ2-UKDY.domain1.systemhost.net ([193.113.30.65]) by
	smtp4.smtp.bt.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 1 Oct 2008 18:21:30 +0100
Received: from 217.32.164.172 ([217.32.164.172]) by
	E03MVZ2-UKDY.domain1.systemhost.net ([193.113.30.120]) via
	Exchange Front-End Server mail.bt.com ([193.113.197.26]) with
	Microsoft Exchange Server HTTP-DAV ; Wed,  1 Oct 2008 17:21:29 +0000
User-Agent: Microsoft-Entourage/12.12.0.080729
Date: Wed, 01 Oct 2008 13:21:28 -0400
From: "Thomas D. Nadeau" <tom.nadeau@bt.com>
To: Stewart Bryant <stbryant@cisco.com>,
	Vishwas Manral <vishwas.ietf@gmail.com>
Message-ID: <C50929D8.E196%tom.nadeau@bt.com>
Thread-Topic: [mpls-tp] [PWE3] FW: Changes to PW ACH Channel Type allocation
	policy
Thread-Index: Ackj6iNm8LEXesKg0EeCFfYVc0+nnA==
In-Reply-To: <48E3A183.80908@cisco.com>
Mime-version: 1.0
X-OriginalArrivalTime: 01 Oct 2008 17:21:30.0426 (UTC)
	FILETIME=[24D889A0:01C923EA]
X-Mailman-Approved-At: Fri, 03 Oct 2008 06:19:21 -0700
Cc: "l2vpn@ietf.org" <l2vpn@ietf.org>,
	BOCCI Matthew <Matthew.Bocci@alcatel-lucent.com>,
	"mpls@ietf.org" <mpls@ietf.org>, "ccamp@ietf.org" <ccamp@ietf.org>,
	"mpls-tp@ietf.org" <mpls-tp@ietf.org>, "pwe3@ietf.org" <pwe3@ietf.org>,
	Shahram Davari <davari@tpack.com>
Subject: Re: [mpls] [mpls-tp] [PWE3] FW: Changes to PW ACH Channel Type
 allocation policy
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mpls-bounces@ietf.org
Errors-To: mpls-bounces@ietf.org


    Stewart,

        I agree with you %100.  It is not the time of approval that will be
the issue in the long run -- I would think an expert review assignment could
be serviced in a couple of weeks to a month (max) anyway. IMHO the real
issue is in how the assignments get implemented later, and precisely as you
say, in the data plane.  The affects here unintentional or intentional, can
be disastrous.

    --Tom (Speaking as my British alter-ego)



On 10/1/08 12:12 PM, "Stewart Bryant" <stbryant@cisco.com> wrote:

> Vishwas Manral wrote:
>> Hi Matthew,
>> 
>> I would like to propose another option if it is for vendor proprietery
>> "Channel Type" values in the ACH header. With the number of values of
>> the channel type being limited and the number of vendors actually a
>> lot, I would think something in the lines of what the draft below
>> talks about may make sense:
>> 
>> http://tools.ietf.org/draft-ietf-isis-proprietary-tlv-00
>> 
>> The idea is give a channel type value, for vendor specific
>> implemntations and further define the structure of the next header
>> value for such a "channel type" to actually have a Vendor OUI value.
>> 
>> This will allow for unlimited innovation without affecting
>> interoperability, unlike the other options you have mentioned.
>> 
>> Thanks,
>> Vishwas
>>   
> 
> Vishwas
> 
> We have 65000 units of innovation, and that is without expanding into
> the next
> octet which is currently reserved for expansion.
> 
> Given that we have not yet run out of UDP ports I don't think we need to
> be concerned
> in that regard.
> 
> The reason that we have been very cautious in the past is because we don't
> want anything that goes on in the ACH straying into the dataplane - for
> example  no one using the ACH as a PID and requiring the forwarder to look
> at it.
> 
> Then when we designed VCCV we had all sorts of concerns over traffic volume
> and security of traffic delivered straight to the management processor.
> 
> We were very cautious when we standardized the ACH mechanism, there is a
> good case for maintaining that caution until we see what people are going
> to use it for.
> 
> Stewart (speaking as myself)
> 
> 
> 
> 

_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls


From mpls-bounces@ietf.org  Fri Oct  3 06:19:23 2008
Return-Path: <mpls-bounces@ietf.org>
X-Original-To: mpls-archive@megatron.ietf.org
Delivered-To: ietfarch-mpls-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id CF75128C123;
	Fri,  3 Oct 2008 06:19:23 -0700 (PDT)
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id C94F43A6CC3;
	Thu,  2 Oct 2008 05:13:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.952
X-Spam-Level: 
X-Spam-Status: No, score=-0.952 tagged_above=-999 required=5 tests=[AWL=0.580, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, RCVD_NUMERIC_HELO=2.067]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 8S5kOLTHZo4X; Thu,  2 Oct 2008 05:13:32 -0700 (PDT)
Received: from smtp1.smtp.bt.com (smtp1.smtp.bt.com [217.32.164.137])
	by core3.amsl.com (Postfix) with ESMTP id 59E9F3A6CB0;
	Thu,  2 Oct 2008 05:13:32 -0700 (PDT)
Received: from E03MVZ2-UKDY.domain1.systemhost.net ([193.113.30.65]) by
	smtp1.smtp.bt.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 2 Oct 2008 13:13:08 +0100
Received: from 217.32.164.172 ([217.32.164.172]) by
	E03MVZ2-UKDY.domain1.systemhost.net ([193.113.30.120]) via
	Exchange Front-End Server mail.bt.com ([193.113.197.26]) with
	Microsoft Exchange Server HTTP-DAV ; Thu,  2 Oct 2008 12:13:07 +0000
User-Agent: Microsoft-Entourage/12.12.0.080729
Date: Thu, 02 Oct 2008 08:13:06 -0400
From: "Thomas D. Nadeau" <tom.nadeau@bt.com>
To: BUSI ITALO <Italo.Busi@alcatel-lucent.it>,
	Vishwas Manral <vishwas.ietf@gmail.com>, Shahram Davari <davari@tpack.com>
Message-ID: <C50A3312.E217%tom.nadeau@bt.com>
Thread-Topic: [mpls-tp] [PWE3] FW: Changes to PW ACH Channel Type
	allocationpolicy
Thread-Index: Ackj3Q1bqBGtuyWETZaWG4drFEnw4AAf+XvQAArRnjg=
In-Reply-To: <6FD21B53861BF44AA90A288402036AB40193F737@FRVELSMBS21.ad2.ad.alcatel.com>
Mime-version: 1.0
X-OriginalArrivalTime: 02 Oct 2008 12:13:08.0615 (UTC)
	FILETIME=[3B51F970:01C92488]
X-Mailman-Approved-At: Fri, 03 Oct 2008 06:19:21 -0700
Cc: l2vpn@ietf.org, BOCCI Matthew <Matthew.Bocci@alcatel-lucent.com>,
	mpls@ietf.org, ccamp@ietf.org, mpls-tp@ietf.org, pwe3@ietf.org
Subject: Re: [mpls] [mpls-tp] [PWE3] FW: Changes to PW ACH Channel Type
 allocationpolicy
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mpls-bounces@ietf.org
Errors-To: mpls-bounces@ietf.org




On 10/2/08 3:11 AM, "BUSI ITALO" <Italo.Busi@alcatel-lucent.it> wrote:

> Vishwas,
> 
> I think this is a good idea
> 
> Both this proposal and option 2 (fist-come-first-served) meet the
> requirements to make the ACH mechanism extensible.

    How does the existing mechanism not meet the requirement to make an ACH
mechanism extensible?

    --Tom

 
> The advantage of this approach is that we do not have to worry about how
> many codepoints we need to allocate for proprietary extensions: we just
> need one codepoint.
> 
> Italo
> 
>> -----Original Message-----
>> From: mpls-tp-bounces@ietf.org
>> [mailto:mpls-tp-bounces@ietf.org] On Behalf Of Vishwas Manral
>> Sent: Wednesday, October 01, 2008 5:47 PM
>> To: Shahram Davari
>> Cc: l2vpn@ietf.org; BOCCI Matthew; mpls@ietf.org;
>> ccamp@ietf.org; mpls-tp@ietf.org; pwe3@ietf.org
>> Subject: Re: [mpls-tp] [PWE3] FW: Changes to PW ACH Channel
>> Type allocationpolicy
>> 
>> Hi Matthew,
>> 
>> I would like to propose another option if it is for vendor proprietery
>> "Channel Type" values in the ACH header. With the number of values of
>> the channel type being limited and the number of vendors actually a
>> lot, I would think something in the lines of what the draft below
>> talks about may make sense:
>> 
>> http://tools.ietf.org/draft-ietf-isis-proprietary-tlv-00
>> 
>> The idea is give a channel type value, for vendor specific
>> implemntations and further define the structure of the next header
>> value for such a "channel type" to actually have a Vendor OUI value.
>> 
>> This will allow for unlimited innovation without affecting
>> interoperability, unlike the other options you have mentioned.
>> 
>> Thanks,
>> Vishwas
>> 
>> 
>> On 10/1/08, Shahram Davari <davari@tpack.com> wrote:
>>> Hi Mathew,
>>> 
>>> I support option 2, since a terminating node that doesn't
>> understand the
>>> VCCV channel type can always drop it. This would allow more
>> innovation and
>>> faster time to market.
>>> 
>>> Best regards,
>>> Shahram
>>> 
>>> 
>>> -----Original Message-----
>>> From: pwe3-bounces@ietf.org [mailto:pwe3-bounces@ietf.org]
>> On Behalf Of
>>> BOCCI Matthew
>>> Sent: September-30-08 12:23 PM
>>> To: pwe3@ietf.org; mpls-tp@ietf.org; mpls@ietf.org; ccamp@ietf.org;
>>> l2vpn@ietf.org
>>> Subject: [PWE3] FW: Changes to PW ACH Channel Type allocation policy
>>> 
>>> The PWE3 chairs would like feedback on proposed changes to the
>>> allocation policy for the PW ACH codepoint registry. Please see the
>>> email below, and provide any feedback copying the PWE3 list.
>>> 
>>> Best regards
>>> 
>>> Matthew
>>> 
>>> -----Original Message-----
>>> From: pwe3-bounces@ietf.org [mailto:pwe3-bounces@ietf.org]
>> On Behalf Of
>>> BOCCI Matthew
>>> Sent: 25 September 2008 16:36
>>> To: pwe3@ietf.org
>>> Subject: [PWE3] Changes to PW ACH Channel Type allocation policy
>>> 
>>> 
>>> 
>>> The current IANA allocation policy for the PW associated
>> channel type
>>> registry is by IETF consensus. This policy was chosen in
>> RFC 4385 based
>>> on WG consensus that since the associated channel exists in the data
>>> path, and VCCV packets are typically processed by the
>> control processor
>>> on many PEs, it was prudent for the IETF to maintain strict
>> control over
>>> what types of channels were allocated and to ensure that
>> they complied
>>> to the PWE3 architecture.
>>> 
>>> However, a need has been identified to provide a more
>> flexible approach
>>> to allocating code points for VCCV channel types. This has
>> partly arisen
>>> from the MPLS-TP work, where MPLS would be deployed in a transport
>>> network and where a much wider range of applications for the PW
>>> associated channel is envisioned, and partialy from a
>> desire to extend
>>> the OAM capabilities for regular MPLS. We can support MPLS-TP and
>>> general MPLS apps with the current policy which requires standards
>>> action.
>>> 
>>> However we are receiving requests to allow proprietary OAM
>> and signaling
>>> protocols to be used in transport applications, and need to
>> decide on
>>> the best way forward. We considered providing extension mechanisms
>>> within the standards track protocols, but believe that the standards
>>> track protocols would be much cleaner if the proprietary
>> protocols ran
>>> on their own ACH code points.
>>> 
>>> Note that we are talking about vendor protocols here. Other
>> SDOs would
>>> be required to publish an RFC and would only be allocated
>> an ACH through
>>> Standards Action.
>>> 
>>> There are two ways to address the requests for proprietary
>> protocol ACH
>>> code points:
>>> 
>>> 1) Allow a range of the associated channel type registry to
>> be allocated
>>> through expert review. Guidelines would be provided for the expert
>>> reviewer to guide them in assessing the request, which
>> would have to be
>>> made in the form of an internet draft, while making sure that the
>>> request is dealt with in a timely and fair manner. This policy would
>>> include hurdles with regard to security, congestion etc
>> that would be
>>> derived from those specified in the VCCV design.
>>> 
>>> 2) Allow a range of the associated channel type registry to
>> be allocated
>>> on a first-come-first-served basis. This does not provide
>> the level of
>>> control that expert review provides, but this is balanced
>> to some degree
>>> by the fact that the VCCV channel type is indicated in the
>> data path,
>>> and so a PE can choose to discard or rate limit VCCV packets on an
>>> unrecognised associated channel.
>>> 
>>> Any change to the ACH allocation policy would be outlined
>> in the GE-ACH
>>> draft, which would update RFC 4385.
>>> 
>>> We would appreciate feedback on the list as to which approach the WG
>>> prefers.
>>> 
>>> Regards,
>>> 
>>> Stewart and Matthew
>>> 
>>> _______________________________________________
>>> pwe3 mailing list
>>> pwe3@ietf.org
>>> https://www.ietf.org/mailman/listinfo/pwe3
>>> _______________________________________________
>>> pwe3 mailing list
>>> pwe3@ietf.org
>>> https://www.ietf.org/mailman/listinfo/pwe3
>>> 
>>> 
>>> 
>>> _______________________________________________
>>> pwe3 mailing list
>>> pwe3@ietf.org
>>> https://www.ietf.org/mailman/listinfo/pwe3
>>> 
>> _______________________________________________
>> mpls-tp mailing list
>> mpls-tp@ietf.org
>> https://www.ietf.org/mailman/listinfo/mpls-tp
>> 

_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls


From mpls-bounces@ietf.org  Fri Oct  3 06:19:24 2008
Return-Path: <mpls-bounces@ietf.org>
X-Original-To: mpls-archive@megatron.ietf.org
Delivered-To: ietfarch-mpls-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 65ED628C12E;
	Fri,  3 Oct 2008 06:19:24 -0700 (PDT)
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 159A53A6AC5;
	Thu,  2 Oct 2008 05:59:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, MISSING_MIMEOLE=0.001]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id Cas2BH5UM1ZR; Thu,  2 Oct 2008 05:59:04 -0700 (PDT)
Received: from tpack.net (ip18.tpack.net [213.173.228.18])
	by core3.amsl.com (Postfix) with ESMTP id 9AAA23A6CA2;
	Thu,  2 Oct 2008 05:59:02 -0700 (PDT)
Received: from [192.168.111.1] (account shd@tpack.net)
	by tpack.net (CommuniGate Pro IMAP 5.1.12)
	with XMIT id 818304; Thu, 02 Oct 2008 14:59:17 +0200
Date: Thu, 02 Oct 2008 08:58:07 -0400
Organization: Tpack A/S
Message-Id: <57ab175fd1b5f945afa7bc60dde31075@mail.cph.tpack.net>
In-Reply-To: <C50A3312.E217%tom.nadeau@bt.com>
MIME-Version: 1.0
Thread-Topic: [mpls-tp] [PWE3] FW: Changes to PW ACH Channel Type
	allocationpolicy
Priority: Normal
Importance: normal
X-MSMail-Priority: normal
X-Priority: 3
Sensitivity: Normal
Thread-Index: Ackj3Q1bqBGtuyWETZaWG4drFEnw4AAf+XvQAArRnjgAAUDYMA==
From: "Shahram Davari" <davari@tpack.com>
To: "BUSI ITALO" <Italo.Busi@alcatel-lucent.it>, 
	"Vishwas Manral" <vishwas.ietf@gmail.com>
X-MAPI-LastModified: Thu, 02 Oct 2008 08:58:07 -0400
X-Mailer: CommuniGate Pro MAPI Connector 1.2.9/1.2.12
X-Mailman-Approved-At: Fri, 03 Oct 2008 06:19:21 -0700
Cc: "l2vpn@ietf.org" <l2vpn@ietf.org>,
	BOCCI Matthew <Matthew.Bocci@alcatel-lucent.com>,
	"mpls@ietf.org" <mpls@ietf.org>, "ccamp@ietf.org" <ccamp@ietf.org>,
	"mpls-tp@ietf.org" <mpls-tp@ietf.org>, "pwe3@ietf.org" <pwe3@ietf.org>
Subject: Re: [mpls] [mpls-tp] [PWE3] FW: Changes to PW ACH Channel Type
	allocationpolicy
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mpls-bounces@ietf.org
Errors-To: mpls-bounces@ietf.org

Hi,

I also prefer the method that Wishwas proposed. This has many advantages:

1) Allows vendors to not expose their proprietary techniques to their competitors. 
2) reduces the load of reviewing by IETF and PWE3 
3) results a faster time to market, since no expert review will be needed
4) provides more codepoint space that the ACH channel type
5) only one VCCV ACH channel type needs to be configured in each box for vendor specific filtering

The 2nd method has the first 3 advantages only, and the first method has none of these advantages.


Best regards,
Shahram

-----Original Message-----
From: Thomas D. Nadeau [mailto:tom.nadeau@bt.com] 
Sent: October-02-08 8:13 AM
To: BUSI ITALO; Vishwas Manral; Shahram Davari
Cc: l2vpn@ietf.org; BOCCI Matthew; mpls@ietf.org; ccamp@ietf.org; mpls-tp@ietf.org; pwe3@ietf.org
Subject: Re: [mpls-tp] [PWE3] FW: Changes to PW ACH Channel Type allocationpolicy




On 10/2/08 3:11 AM, "BUSI ITALO" <Italo.Busi@alcatel-lucent.it> wrote:

> Vishwas,
> 
> I think this is a good idea
> 
> Both this proposal and option 2 (fist-come-first-served) meet the
> requirements to make the ACH mechanism extensible.

    How does the existing mechanism not meet the requirement to make an ACH
mechanism extensible?

    --Tom

 
> The advantage of this approach is that we do not have to worry about how
> many codepoints we need to allocate for proprietary extensions: we just
> need one codepoint.
> 
> Italo
> 
>> -----Original Message-----
>> From: mpls-tp-bounces@ietf.org
>> [mailto:mpls-tp-bounces@ietf.org] On Behalf Of Vishwas Manral
>> Sent: Wednesday, October 01, 2008 5:47 PM
>> To: Shahram Davari
>> Cc: l2vpn@ietf.org; BOCCI Matthew; mpls@ietf.org;
>> ccamp@ietf.org; mpls-tp@ietf.org; pwe3@ietf.org
>> Subject: Re: [mpls-tp] [PWE3] FW: Changes to PW ACH Channel
>> Type allocationpolicy
>> 
>> Hi Matthew,
>> 
>> I would like to propose another option if it is for vendor proprietery
>> "Channel Type" values in the ACH header. With the number of values of
>> the channel type being limited and the number of vendors actually a
>> lot, I would think something in the lines of what the draft below
>> talks about may make sense:
>> 
>> http://tools.ietf.org/draft-ietf-isis-proprietary-tlv-00
>> 
>> The idea is give a channel type value, for vendor specific
>> implemntations and further define the structure of the next header
>> value for such a "channel type" to actually have a Vendor OUI value.
>> 
>> This will allow for unlimited innovation without affecting
>> interoperability, unlike the other options you have mentioned.
>> 
>> Thanks,
>> Vishwas
>> 
>> 
>> On 10/1/08, Shahram Davari <davari@tpack.com> wrote:
>>> Hi Mathew,
>>> 
>>> I support option 2, since a terminating node that doesn't
>> understand the
>>> VCCV channel type can always drop it. This would allow more
>> innovation and
>>> faster time to market.
>>> 
>>> Best regards,
>>> Shahram
>>> 
>>> 
>>> -----Original Message-----
>>> From: pwe3-bounces@ietf.org [mailto:pwe3-bounces@ietf.org]
>> On Behalf Of
>>> BOCCI Matthew
>>> Sent: September-30-08 12:23 PM
>>> To: pwe3@ietf.org; mpls-tp@ietf.org; mpls@ietf.org; ccamp@ietf.org;
>>> l2vpn@ietf.org
>>> Subject: [PWE3] FW: Changes to PW ACH Channel Type allocation policy
>>> 
>>> The PWE3 chairs would like feedback on proposed changes to the
>>> allocation policy for the PW ACH codepoint registry. Please see the
>>> email below, and provide any feedback copying the PWE3 list.
>>> 
>>> Best regards
>>> 
>>> Matthew
>>> 
>>> -----Original Message-----
>>> From: pwe3-bounces@ietf.org [mailto:pwe3-bounces@ietf.org]
>> On Behalf Of
>>> BOCCI Matthew
>>> Sent: 25 September 2008 16:36
>>> To: pwe3@ietf.org
>>> Subject: [PWE3] Changes to PW ACH Channel Type allocation policy
>>> 
>>> 
>>> 
>>> The current IANA allocation policy for the PW associated
>> channel type
>>> registry is by IETF consensus. This policy was chosen in
>> RFC 4385 based
>>> on WG consensus that since the associated channel exists in the data
>>> path, and VCCV packets are typically processed by the
>> control processor
>>> on many PEs, it was prudent for the IETF to maintain strict
>> control over
>>> what types of channels were allocated and to ensure that
>> they complied
>>> to the PWE3 architecture.
>>> 
>>> However, a need has been identified to provide a more
>> flexible approach
>>> to allocating code points for VCCV channel types. This has
>> partly arisen
>>> from the MPLS-TP work, where MPLS would be deployed in a transport
>>> network and where a much wider range of applications for the PW
>>> associated channel is envisioned, and partialy from a
>> desire to extend
>>> the OAM capabilities for regular MPLS. We can support MPLS-TP and
>>> general MPLS apps with the current policy which requires standards
>>> action.
>>> 
>>> However we are receiving requests to allow proprietary OAM
>> and signaling
>>> protocols to be used in transport applications, and need to
>> decide on
>>> the best way forward. We considered providing extension mechanisms
>>> within the standards track protocols, but believe that the standards
>>> track protocols would be much cleaner if the proprietary
>> protocols ran
>>> on their own ACH code points.
>>> 
>>> Note that we are talking about vendor protocols here. Other
>> SDOs would
>>> be required to publish an RFC and would only be allocated
>> an ACH through
>>> Standards Action.
>>> 
>>> There are two ways to address the requests for proprietary
>> protocol ACH
>>> code points:
>>> 
>>> 1) Allow a range of the associated channel type registry to
>> be allocated
>>> through expert review. Guidelines would be provided for the expert
>>> reviewer to guide them in assessing the request, which
>> would have to be
>>> made in the form of an internet draft, while making sure that the
>>> request is dealt with in a timely and fair manner. This policy would
>>> include hurdles with regard to security, congestion etc
>> that would be
>>> derived from those specified in the VCCV design.
>>> 
>>> 2) Allow a range of the associated channel type registry to
>> be allocated
>>> on a first-come-first-served basis. This does not provide
>> the level of
>>> control that expert review provides, but this is balanced
>> to some degree
>>> by the fact that the VCCV channel type is indicated in the
>> data path,
>>> and so a PE can choose to discard or rate limit VCCV packets on an
>>> unrecognised associated channel.
>>> 
>>> Any change to the ACH allocation policy would be outlined
>> in the GE-ACH
>>> draft, which would update RFC 4385.
>>> 
>>> We would appreciate feedback on the list as to which approach the WG
>>> prefers.
>>> 
>>> Regards,
>>> 
>>> Stewart and Matthew
>>> 
>>> _______________________________________________
>>> pwe3 mailing list
>>> pwe3@ietf.org
>>> https://www.ietf.org/mailman/listinfo/pwe3
>>> _______________________________________________
>>> pwe3 mailing list
>>> pwe3@ietf.org
>>> https://www.ietf.org/mailman/listinfo/pwe3
>>> 
>>> 
>>> 
>>> _______________________________________________
>>> pwe3 mailing list
>>> pwe3@ietf.org
>>> https://www.ietf.org/mailman/listinfo/pwe3
>>> 
>> _______________________________________________
>> mpls-tp mailing list
>> mpls-tp@ietf.org
>> https://www.ietf.org/mailman/listinfo/mpls-tp
>> 




_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls


From mpls-bounces@ietf.org  Fri Oct  3 06:19:25 2008
Return-Path: <mpls-bounces@ietf.org>
X-Original-To: mpls-archive@megatron.ietf.org
Delivered-To: ietfarch-mpls-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 0F49928C14F;
	Fri,  3 Oct 2008 06:19:25 -0700 (PDT)
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 9DD393A6ABD;
	Thu,  2 Oct 2008 09:08:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, MISSING_MIMEOLE=0.001]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id bfsX9wnEKaJD; Thu,  2 Oct 2008 09:08:54 -0700 (PDT)
Received: from tpack.net (ip18.tpack.net [213.173.228.18])
	by core3.amsl.com (Postfix) with ESMTP id 6FEF53A6A27;
	Thu,  2 Oct 2008 09:08:51 -0700 (PDT)
Received: from [192.168.111.1] (account shd@tpack.net)
	by tpack.net (CommuniGate Pro IMAP 5.1.12)
	with XMIT id 818523; Thu, 02 Oct 2008 18:07:00 +0200
Date: Thu, 02 Oct 2008 12:05:36 -0400
Organization: Tpack A/S
Message-Id: <92a2396384f1f54f92005abb3728728f@mail.cph.tpack.net>
In-Reply-To: <48E4DE0F.9020704@castlepoint.net>
MIME-Version: 1.0
Thread-Topic: =?us-ascii?B?W21wbHMtdHBdIFtQV0UzXSBGVzogQ2hhbmdlcyB0byBQVyBBQ0ggQ2hhbm5l?=
	=?us-ascii?B?bCBUeXBlCWFsbG9jYXRpb25wb2xpY3k=?=
Priority: Normal
Importance: normal
X-MSMail-Priority: normal
X-Priority: 3
Sensitivity: Normal
Thread-Index: AckkqLTHdNDdblepSIu2W52R3r7OPA==
From: "Shahram Davari" <davari@tpack.com>
To: "Shane Amante" <shane@castlepoint.net>
X-MAPI-LastModified: Thu, 02 Oct 2008 12:05:36 -0400
X-Mailer: CommuniGate Pro MAPI Connector 1.2.9/1.2.12
X-Mailman-Approved-At: Fri, 03 Oct 2008 06:19:21 -0700
Cc: "l2vpn@ietf.org" <l2vpn@ietf.org>, "mpls@ietf.org" <mpls@ietf.org>,
	BOCCI Matthew <Matthew.Bocci@alcatel-lucent.com>,
	"ccamp@ietf.org" <ccamp@ietf.org>, "mpls-tp@ietf.org" <mpls-tp@ietf.org>,
	"pwe3@ietf.org" <pwe3@ietf.org>, BUSI ITALO <Italo.Busi@alcatel-lucent.it>
Subject: Re: [mpls] [mpls-tp] [PWE3] FW: Changes to PW ACH Channel
	Type	allocationpolicy
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mpls-bounces@ietf.org
Errors-To: mpls-bounces@ietf.org

Hi Shane,

Please see my response in-line. 

Best regards,
Shahram


-----Original Message-----
From: Shane Amante [mailto:shane@castlepoint.net] 
Sent: October-02-08 10:43 AM
To: Shahram Davari
Cc: BUSI ITALO; Vishwas Manral; l2vpn@ietf.org; BOCCI Matthew; mpls@ietf.org; ccamp@ietf.org; mpls-tp@ietf.org; pwe3@ietf.org
Subject: Re: [mpls-tp] [PWE3] FW: Changes to PW ACH Channel Type allocationpolicy

Shahram Davari wrote:
> Hi,
> 
> I also prefer the method that Wishwas proposed. This has many advantages:
> 
> 1) Allows vendors to not expose their proprietary techniques to their competitors. 

 From the POV of an operator, this is actually a substantial disadvantage.

[Shahram] OTOH it encourages more innovation and differentiation by vendors.


> 2) reduces the load of reviewing by IETF and PWE3 

OTOH, the benefit of such reviews by the IETF and PWE3 is when 
"commonality" among similar applications are discovered they can be 
standardized, rather kept proprietary.

[Shahram] Not if the inventing vendor is not willing to do so.


> 3) results a faster time to market, since no expert review will be needed

True, to some extent.  But, IMHO, I would much rather see a *slightly* 
slower process involving a careful expert review and/or IETF consensus 
to make sure we're not: a) unnecessarily duplicating work; and, b) at 
the same time, encouraging more standards-based approach.


> 4) provides more codepoint space that the ACH channel type

This is false.  There is no shortage on ACH channel types today.
[Shahram] You are correct. 16-bit is sufficient enough.


> 5) only one VCCV ACH channel type needs to be configured in each box for vendor specific filtering
 >
> The 2nd method has the first 3 advantages only, and the first method has none of these advantages.


Also, let's take a step back here.  Wasn't the whole point with the 
joint ITU-T/IETF effort surrounding MPLS-TP to create an environment in 
which MPLS-TP could seamlessly interoperate within (existing) MPLS 
environments?  I thought a fundamental part of that work is striving 
towards creating a *standards-based* MPLS-TP data-plane, OAM, signaling, 
etc. mechanisms.  IMO, Vishwas' proposal and Matthew's proposal #2 seems 
to run contrary to that goal.

[Shahram] off course we should all encourage standards methods. But we should provide a fast and reasonable procedure for vendor specific protocols that don't affect interoperability. I worry that in first method competitors may vote down code point requests for commercial reasons.

-shane (speaking only for himself, not as co-chair)



_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls


From mpls-bounces@ietf.org  Fri Oct  3 06:19:25 2008
Return-Path: <mpls-bounces@ietf.org>
X-Original-To: mpls-archive@megatron.ietf.org
Delivered-To: ietfarch-mpls-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id A1B5B28C197;
	Fri,  3 Oct 2008 06:19:25 -0700 (PDT)
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 81D543A6816;
	Thu,  2 Oct 2008 09:45:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.035
X-Spam-Level: 
X-Spam-Status: No, score=-1.035 tagged_above=-999 required=5 tests=[AWL=0.497, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, RCVD_NUMERIC_HELO=2.067]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 7fqRrcgqth4O; Thu,  2 Oct 2008 09:45:31 -0700 (PDT)
Received: from smtp4.smtp.bt.com (smtp4.smtp.bt.com [217.32.164.151])
	by core3.amsl.com (Postfix) with ESMTP id 710323A6A8B;
	Thu,  2 Oct 2008 09:45:16 -0700 (PDT)
Received: from E03MVZ2-UKDY.domain1.systemhost.net ([193.113.30.65]) by
	smtp4.smtp.bt.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 2 Oct 2008 17:43:33 +0100
Received: from 217.32.164.172 ([217.32.164.172]) by
	E03MVZ2-UKDY.domain1.systemhost.net ([193.113.30.120]) via
	Exchange Front-End Server mail.bt.com ([193.113.197.26]) with
	Microsoft Exchange Server HTTP-DAV ; Thu,  2 Oct 2008 16:43:32 +0000
User-Agent: Microsoft-Entourage/12.12.0.080729
Date: Thu, 02 Oct 2008 12:43:31 -0400
From: "Thomas D. Nadeau" <tom.nadeau@bt.com>
To: Shahram Davari <davari@tpack.com>,
	Shane Amante <shane@castlepoint.net>
Message-ID: <C50A7273.E252%tom.nadeau@bt.com>
Thread-Topic: [mpls-tp] [PWE3] FW: Changes to PW ACH Channel Type
	allocationpolicy
Thread-Index: AckkqLTHdNDdblepSIu2W52R3r7OPAABUvW5
In-Reply-To: <92a2396384f1f54f92005abb3728728f@mail.cph.tpack.net>
Mime-version: 1.0
X-OriginalArrivalTime: 02 Oct 2008 16:43:33.0168 (UTC)
	FILETIME=[01E84B00:01C924AE]
X-Mailman-Approved-At: Fri, 03 Oct 2008 06:19:21 -0700
Cc: "l2vpn@ietf.org" <l2vpn@ietf.org>, "mpls@ietf.org" <mpls@ietf.org>,
	BOCCI Matthew <Matthew.Bocci@alcatel-lucent.com>,
	"ccamp@ietf.org" <ccamp@ietf.org>, "mpls-tp@ietf.org" <mpls-tp@ietf.org>,
	"pwe3@ietf.org" <pwe3@ietf.org>, BUSI ITALO <Italo.Busi@alcatel-lucent.it>
Subject: Re: [mpls] [mpls-tp] [PWE3] FW: Changes to PW ACH Channel Type
 allocationpolicy
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mpls-bounces@ietf.org
Errors-To: mpls-bounces@ietf.org



    I agree with %100 of Shane's comments. One bit to add below:

> Hi Shane,
> 
> Please see my response in-line.
> 
> Best regards,
> Shahram
> 
> 
> -----Original Message-----
> From: Shane Amante [mailto:shane@castlepoint.net]
> Sent: October-02-08 10:43 AM
> To: Shahram Davari
> Cc: BUSI ITALO; Vishwas Manral; l2vpn@ietf.org; BOCCI Matthew; mpls@ietf.org;
> ccamp@ietf.org; mpls-tp@ietf.org; pwe3@ietf.org
> Subject: Re: [mpls-tp] [PWE3] FW: Changes to PW ACH Channel Type
> allocationpolicy
> 
> Shahram Davari wrote:
>> Hi,
>> 
>> I also prefer the method that Wishwas proposed. This has many advantages:
>> 
>> 1) Allows vendors to not expose their proprietary techniques to their
>> competitors.
> 
>  From the POV of an operator, this is actually a substantial disadvantage.
> 
> [Shahram] OTOH it encourages more innovation and differentiation by vendors.

    That is hogwash. Customers encourage vendors to innovate not standards
bodies. Standards bodies help encourage and foster interoperability of a
common specification. The latter is the important point Shane is making (as
am I and others who are the customers in this equation). We don't want to
encourage proprietary implementations for the sake of proprietary
implementations; we want to encourage them to ultimately interoperate on a
common specification. However, if your goal as a vendor is to create
proprietary implementations you are free to do so, but you do not need the
IETF unless you are looking for some sort of rubber stamp of approval.

    --Tom


  
>> 2) reduces the load of reviewing by IETF and PWE3
> 
> OTOH, the benefit of such reviews by the IETF and PWE3 is when
> "commonality" among similar applications are discovered they can be
> standardized, rather kept proprietary.
> 
> [Shahram] Not if the inventing vendor is not willing to do so.
> 
> 
>> 3) results a faster time to market, since no expert review will be needed
> 
> True, to some extent.  But, IMHO, I would much rather see a *slightly*
> slower process involving a careful expert review and/or IETF consensus
> to make sure we're not: a) unnecessarily duplicating work; and, b) at
> the same time, encouraging more standards-based approach.
> 
> 
>> 4) provides more codepoint space that the ACH channel type
> 
> This is false.  There is no shortage on ACH channel types today.
> [Shahram] You are correct. 16-bit is sufficient enough.
> 
> 
>> 5) only one VCCV ACH channel type needs to be configured in each box for
>> vendor specific filtering
>> 
>> The 2nd method has the first 3 advantages only, and the first method has none
>> of these advantages.
> 
> 
> Also, let's take a step back here.  Wasn't the whole point with the
> joint ITU-T/IETF effort surrounding MPLS-TP to create an environment in
> which MPLS-TP could seamlessly interoperate within (existing) MPLS
> environments?  I thought a fundamental part of that work is striving
> towards creating a *standards-based* MPLS-TP data-plane, OAM, signaling,
> etc. mechanisms.  IMO, Vishwas' proposal and Matthew's proposal #2 seems
> to run contrary to that goal.
> 
> [Shahram] off course we should all encourage standards methods. But we should
> provide a fast and reasonable procedure for vendor specific protocols that
> don't affect interoperability. I worry that in first method competitors may
> vote down code point requests for commercial reasons.
> 
> -shane (speaking only for himself, not as co-chair)
> 
> 
> 

_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls


From mpls-bounces@ietf.org  Fri Oct  3 06:19:26 2008
Return-Path: <mpls-bounces@ietf.org>
X-Original-To: mpls-archive@megatron.ietf.org
Delivered-To: ietfarch-mpls-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 3DFF928C1DB;
	Fri,  3 Oct 2008 06:19:26 -0700 (PDT)
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 605ED3A6816;
	Thu,  2 Oct 2008 10:18:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, MISSING_MIMEOLE=0.001]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id P25rJYhSkAAq; Thu,  2 Oct 2008 10:18:41 -0700 (PDT)
Received: from tpack.net (ip18.tpack.net [213.173.228.18])
	by core3.amsl.com (Postfix) with ESMTP id 53C023A67E4;
	Thu,  2 Oct 2008 10:18:38 -0700 (PDT)
Received: from [192.168.111.1] (account shd@tpack.net)
	by tpack.net (CommuniGate Pro IMAP 5.1.12)
	with XMIT id 818550; Thu, 02 Oct 2008 19:18:30 +0200
Date: Thu, 02 Oct 2008 13:17:58 -0400
Organization: Tpack A/S
Message-Id: <16a42c48f46e6547a1c3ce65f8fee99a@mail.cph.tpack.net>
In-Reply-To: <C50A7273.E252%tom.nadeau@bt.com>
MIME-Version: 1.0
Thread-Topic: [mpls-tp] [PWE3] FW: Changes to PW ACH Channel Type
	allocationpolicy
Priority: Normal
Importance: normal
X-MSMail-Priority: normal
X-Priority: 3
Sensitivity: Normal
Thread-Index: AckkqLTHdNDdblepSIu2W52R3r7OPAABUvW5AADtmEA=
From: "Shahram Davari" <davari@tpack.com>
To: "Thomas D. Nadeau" <tom.nadeau@bt.com>, 
	"Shane Amante" <shane@castlepoint.net>
X-MAPI-LastModified: Thu, 02 Oct 2008 13:17:58 -0400
X-Mailer: CommuniGate Pro MAPI Connector 1.2.9/1.2.12
X-Mailman-Approved-At: Fri, 03 Oct 2008 06:19:21 -0700
Cc: "l2vpn@ietf.org" <l2vpn@ietf.org>, "mpls@ietf.org" <mpls@ietf.org>,
	BOCCI Matthew <Matthew.Bocci@alcatel-lucent.com>,
	"ccamp@ietf.org" <ccamp@ietf.org>, "mpls-tp@ietf.org" <mpls-tp@ietf.org>,
	"pwe3@ietf.org" <pwe3@ietf.org>, BUSI ITALO <Italo.Busi@alcatel-lucent.it>
Subject: Re: [mpls] [mpls-tp] [PWE3] FW: Changes to PW ACH Channel Type
	allocationpolicy
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mpls-bounces@ietf.org
Errors-To: mpls-bounces@ietf.org

No one asked for IETF rubber stamping. I asked for a mechanism (code point assignment) that easily implement vendor specific methods. I don't see any reason why IETF should review and approve a vendor specific method. If IETF doesn't want to see any vendor specific method, then it doesn't need to allocate any code points. However, if IETF wants to encourage vendor specific protocols then it must do so in a way that makes it easy for vendors to use it.

-Shahram


-----Original Message-----
From: Thomas D. Nadeau [mailto:tom.nadeau@bt.com] 
Sent: October-02-08 12:44 PM
To: Shahram Davari; Shane Amante
Cc: l2vpn@ietf.org; mpls@ietf.org; BOCCI Matthew; ccamp@ietf.org; mpls-tp@ietf.org; Vishwas Manral; pwe3@ietf.org; BUSI ITALO
Subject: Re: [mpls-tp] [PWE3] FW: Changes to PW ACH Channel Type allocationpolicy



    I agree with %100 of Shane's comments. One bit to add below:

> Hi Shane,
> 
> Please see my response in-line.
> 
> Best regards,
> Shahram
> 
> 
> -----Original Message-----
> From: Shane Amante [mailto:shane@castlepoint.net]
> Sent: October-02-08 10:43 AM
> To: Shahram Davari
> Cc: BUSI ITALO; Vishwas Manral; l2vpn@ietf.org; BOCCI Matthew; mpls@ietf.org;
> ccamp@ietf.org; mpls-tp@ietf.org; pwe3@ietf.org
> Subject: Re: [mpls-tp] [PWE3] FW: Changes to PW ACH Channel Type
> allocationpolicy
> 
> Shahram Davari wrote:
>> Hi,
>> 
>> I also prefer the method that Wishwas proposed. This has many advantages:
>> 
>> 1) Allows vendors to not expose their proprietary techniques to their
>> competitors.
> 
>  From the POV of an operator, this is actually a substantial disadvantage.
> 
> [Shahram] OTOH it encourages more innovation and differentiation by vendors.

    That is hogwash. Customers encourage vendors to innovate not standards
bodies. Standards bodies help encourage and foster interoperability of a
common specification. The latter is the important point Shane is making (as
am I and others who are the customers in this equation). We don't want to
encourage proprietary implementations for the sake of proprietary
implementations; we want to encourage them to ultimately interoperate on a
common specification. However, if your goal as a vendor is to create
proprietary implementations you are free to do so, but you do not need the
IETF unless you are looking for some sort of rubber stamp of approval.

    --Tom


  
>> 2) reduces the load of reviewing by IETF and PWE3
> 
> OTOH, the benefit of such reviews by the IETF and PWE3 is when
> "commonality" among similar applications are discovered they can be
> standardized, rather kept proprietary.
> 
> [Shahram] Not if the inventing vendor is not willing to do so.
> 
> 
>> 3) results a faster time to market, since no expert review will be needed
> 
> True, to some extent.  But, IMHO, I would much rather see a *slightly*
> slower process involving a careful expert review and/or IETF consensus
> to make sure we're not: a) unnecessarily duplicating work; and, b) at
> the same time, encouraging more standards-based approach.
> 
> 
>> 4) provides more codepoint space that the ACH channel type
> 
> This is false.  There is no shortage on ACH channel types today.
> [Shahram] You are correct. 16-bit is sufficient enough.
> 
> 
>> 5) only one VCCV ACH channel type needs to be configured in each box for
>> vendor specific filtering
>> 
>> The 2nd method has the first 3 advantages only, and the first method has none
>> of these advantages.
> 
> 
> Also, let's take a step back here.  Wasn't the whole point with the
> joint ITU-T/IETF effort surrounding MPLS-TP to create an environment in
> which MPLS-TP could seamlessly interoperate within (existing) MPLS
> environments?  I thought a fundamental part of that work is striving
> towards creating a *standards-based* MPLS-TP data-plane, OAM, signaling,
> etc. mechanisms.  IMO, Vishwas' proposal and Matthew's proposal #2 seems
> to run contrary to that goal.
> 
> [Shahram] off course we should all encourage standards methods. But we should
> provide a fast and reasonable procedure for vendor specific protocols that
> don't affect interoperability. I worry that in first method competitors may
> vote down code point requests for commercial reasons.
> 
> -shane (speaking only for himself, not as co-chair)
> 
> 
> 




_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls


From mpls-bounces@ietf.org  Fri Oct  3 06:19:26 2008
Return-Path: <mpls-bounces@ietf.org>
X-Original-To: mpls-archive@megatron.ietf.org
Delivered-To: ietfarch-mpls-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id C0F8528C20A;
	Fri,  3 Oct 2008 06:19:26 -0700 (PDT)
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 178343A6AE1;
	Thu,  2 Oct 2008 10:28:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id GVYhOOzsjaM0; Thu,  2 Oct 2008 10:28:32 -0700 (PDT)
Received: from smtp4.smtp.bt.com (smtp4.smtp.bt.com [217.32.164.151])
	by core3.amsl.com (Postfix) with ESMTP id 1F3C33A6A0C;
	Thu,  2 Oct 2008 10:28:31 -0700 (PDT)
Received: from E03MVB3-UKBR.domain1.systemhost.net ([193.113.197.109]) by
	smtp4.smtp.bt.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 2 Oct 2008 18:28:32 +0100
Received: from 10.215.40.109 ([10.215.40.109]) by
	E03MVB3-UKBR.domain1.systemhost.net ([193.113.197.60]) via
	Exchange Front-End Server mail.bt.com ([193.113.197.32]) with
	Microsoft Exchange Server HTTP-DAV ; Thu,  2 Oct 2008 17:28:31 +0000
User-Agent: Microsoft-Entourage/12.12.0.080729
Date: Thu, 02 Oct 2008 18:28:29 +0100
From: Ben Niven-Jenkins <benjamin.niven-jenkins@bt.com>
To: Thomas Nadeau <tom.nadeau@bt.com>, Stewart Bryant <stbryant@cisco.com>,
	Vishwas Manral <vishwas.ietf@gmail.com>
Message-ID: <C50AC34D.C5B8%benjamin.niven-jenkins@bt.com>
Thread-Topic: [mpls-tp] [PWE3] FW: Changes to PW ACH Channel Type allocation
	policy
Thread-Index: Ackj6iNm8LEXesKg0EeCFfYVc0+nnAAyiVbz
In-Reply-To: <C50929D8.E196%tom.nadeau@bt.com>
Mime-version: 1.0
X-OriginalArrivalTime: 02 Oct 2008 17:28:32.0561 (UTC)
	FILETIME=[4ADEFA10:01C924B4]
X-Mailman-Approved-At: Fri, 03 Oct 2008 06:19:21 -0700
Cc: "l2vpn@ietf.org" <l2vpn@ietf.org>,
	BOCCI Matthew <Matthew.Bocci@alcatel-lucent.com>,
	"mpls@ietf.org" <mpls@ietf.org>, "ccamp@ietf.org" <ccamp@ietf.org>,
	"mpls-tp@ietf.org" <mpls-tp@ietf.org>, "pwe3@ietf.org" <pwe3@ietf.org>,
	Shahram Davari <davari@tpack.com>
Subject: Re: [mpls] [mpls-tp] [PWE3] FW: Changes to PW ACH Channel Type
 allocation policy
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mpls-bounces@ietf.org
Errors-To: mpls-bounces@ietf.org

If the process is going to be changed I would vote for Option #1 (expert
review).

Ben

On 01/10/2008 18:21, "Thomas Nadeau" <tom.nadeau@bt.com> wrote:
>     --Tom (Speaking as my British alter-ego)

I hope that's not me ;-))


_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls


From mpls-bounces@ietf.org  Fri Oct  3 06:19:27 2008
Return-Path: <mpls-bounces@ietf.org>
X-Original-To: mpls-archive@megatron.ietf.org
Delivered-To: ietfarch-mpls-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 63E8028C223;
	Fri,  3 Oct 2008 06:19:27 -0700 (PDT)
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id D535C28C224;
	Thu,  2 Oct 2008 10:29:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 7s3497kuL2cn; Thu,  2 Oct 2008 10:29:40 -0700 (PDT)
Received: from smtp1.smtp.bt.com (smtp1.smtp.bt.com [217.32.164.137])
	by core3.amsl.com (Postfix) with ESMTP id 0B31F28C20B;
	Thu,  2 Oct 2008 10:29:38 -0700 (PDT)
Received: from E03MVB3-UKBR.domain1.systemhost.net ([193.113.197.109]) by
	smtp1.smtp.bt.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 2 Oct 2008 18:29:51 +0100
Received: from 10.215.40.109 ([10.215.40.109]) by
	E03MVB3-UKBR.domain1.systemhost.net ([193.113.197.60]) via
	Exchange Front-End Server mail.bt.com ([193.113.197.32]) with
	Microsoft Exchange Server HTTP-DAV ; Thu,  2 Oct 2008 17:29:50 +0000
User-Agent: Microsoft-Entourage/12.12.0.080729
Date: Thu, 02 Oct 2008 18:29:49 +0100
From: Ben Niven-Jenkins <benjamin.niven-jenkins@bt.com>
To: Shahram Davari <davari@tpack.com>,
	Shane Amante <shane@castlepoint.net>
Message-ID: <C50AC39D.C5BD%benjamin.niven-jenkins@bt.com>
Thread-Topic: [mpls-tp] [PWE3] FW: Changes to PW ACH Channel Type
	allocationpolicy
Thread-Index: AckkqLTHdNDdblepSIu2W52R3r7OPAAC8Omk
In-Reply-To: <92a2396384f1f54f92005abb3728728f@mail.cph.tpack.net>
Mime-version: 1.0
X-OriginalArrivalTime: 02 Oct 2008 17:29:51.0143 (UTC)
	FILETIME=[79B5A370:01C924B4]
X-Mailman-Approved-At: Fri, 03 Oct 2008 06:19:21 -0700
Cc: "l2vpn@ietf.org" <l2vpn@ietf.org>, "mpls@ietf.org" <mpls@ietf.org>,
	BOCCI Matthew <Matthew.Bocci@alcatel-lucent.com>,
	"ccamp@ietf.org" <ccamp@ietf.org>, "mpls-tp@ietf.org" <mpls-tp@ietf.org>,
	"pwe3@ietf.org" <pwe3@ietf.org>, BUSI ITALO <Italo.Busi@alcatel-lucent.it>
Subject: Re: [mpls] [mpls-tp] [PWE3] FW: Changes to PW ACH Channel Type
 allocationpolicy
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mpls-bounces@ietf.org
Errors-To: mpls-bounces@ietf.org

On 02/10/2008 17:05, "Shahram Davari" <davari@tpack.com> wrote:
> From: Shane Amante [mailto:shane@castlepoint.net]
> Shahram Davari wrote:
>> Hi,
>> 
>> I also prefer the method that Wishwas proposed. This has many advantages:
>> 
>> 1) Allows vendors to not expose their proprietary techniques to their
>> competitors.
> 
>  From the POV of an operator, this is actually a substantial disadvantage.
> 
> [Shahram] OTOH it encourages more innovation and differentiation by vendors.

Which is fine until you run a multi-vendor network.

Ben

_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls


From mpls-bounces@ietf.org  Fri Oct  3 06:19:28 2008
Return-Path: <mpls-bounces@ietf.org>
X-Original-To: mpls-archive@megatron.ietf.org
Delivered-To: ietfarch-mpls-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 0B30928C23C;
	Fri,  3 Oct 2008 06:19:28 -0700 (PDT)
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 3A62328C18E
	for <mpls@core3.amsl.com>; Thu,  2 Oct 2008 10:30:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id NrOySQJRSXoF for <mpls@core3.amsl.com>;
	Thu,  2 Oct 2008 10:30:54 -0700 (PDT)
Received: from smtp111.rog.mail.re2.yahoo.com (smtp111.rog.mail.re2.yahoo.com
	[206.190.37.1]) by core3.amsl.com (Postfix) with SMTP id 6A2D428C172
	for <mpls@ietf.org>; Thu,  2 Oct 2008 10:30:53 -0700 (PDT)
Received: (qmail 9838 invoked from network); 2 Oct 2008 17:24:25 -0000
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com;
	h=Received:X-YMail-OSG:X-Yahoo-Newman-Property:Reply-To:From:To:Cc:References:In-Reply-To:Subject:Date:Message-ID:MIME-Version:Content-Type:Content-Transfer-Encoding:X-Mailer:Thread-Index:Content-Language;
	b=E4XEhIsGXfxzStilCPdb++Zj57BridhdscKU8qgrO4v304hflwhizcbEO7EQJ4a3qt6TExl56597pr4Yw7gWANteYChv91JKnBXMlBnoxoCU6g79Q8sydhZN9FTURXttqSFHscYt62WI25JvP0WQwMah09d7SPCIHGusuWfCyao=
	; 
Received: from unknown (HELO ShahramPC) (davarish@99.238.119.231 with login)
	by smtp111.rog.mail.re2.yahoo.com with SMTP; 2 Oct 2008 17:24:25 -0000
X-YMail-OSG: Ay5uktUVM1mvXCpCaIETGOiEVuFqfLNwrdvddRAsxtsMzmRdYiUzgm.IDAQBF0WsJA--
X-Yahoo-Newman-Property: ymail-3
From: "Shahram Davari" <davarish@yahoo.com>
To: "'Thomas D. Nadeau'" <tom.nadeau@bt.com>,
	"'Shahram Davari'" <davari@tpack.com>,
	"'Shane Amante'" <shane@castlepoint.net>
References: <92a2396384f1f54f92005abb3728728f@mail.cph.tpack.net>
	<C50A7273.E252%tom.nadeau@bt.com>
In-Reply-To: <C50A7273.E252%tom.nadeau@bt.com>
Date: Thu, 2 Oct 2008 13:24:20 -0400
Message-ID: <005901c924b3$b570bc20$20523460$@com>
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AckkqLTHdNDdblepSIu2W52R3r7OPAABUvW5AAFN92A=
Content-Language: en-ca
X-Mailman-Approved-At: Fri, 03 Oct 2008 06:19:21 -0700
Cc: l2vpn@ietf.org, mpls@ietf.org,
	'BOCCI Matthew' <Matthew.Bocci@alcatel-lucent.com>,
	ccamp@ietf.org, mpls-tp@ietf.org, pwe3@ietf.org,
	'BUSI ITALO' <Italo.Busi@alcatel-lucent.it>
Subject: Re: [mpls] [Bulk] Re: [PWE3] [mpls-tp] FW: Changes to PW ACH
	Channel Type allocationpolicy
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: davarish@yahoo.com
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mpls-bounces@ietf.org
Errors-To: mpls-bounces@ietf.org

By the way I suggest using more polite language.

-shahram

-----Original Message-----
From: pwe3-bounces@ietf.org [mailto:pwe3-bounces@ietf.org] On Behalf Of
Thomas D. Nadeau
Sent: October-02-08 12:44 PM
To: Shahram Davari; Shane Amante
Cc: l2vpn@ietf.org; mpls@ietf.org; BOCCI Matthew; ccamp@ietf.org;
mpls-tp@ietf.org; pwe3@ietf.org; BUSI ITALO
Subject: [Bulk] Re: [PWE3] [mpls-tp] FW: Changes to PW ACH Channel Type
allocationpolicy



    I agree with %100 of Shane's comments. One bit to add below:

> Hi Shane,
> 
> Please see my response in-line.
> 
> Best regards,
> Shahram
> 
> 
> -----Original Message-----
> From: Shane Amante [mailto:shane@castlepoint.net]
> Sent: October-02-08 10:43 AM
> To: Shahram Davari
> Cc: BUSI ITALO; Vishwas Manral; l2vpn@ietf.org; BOCCI Matthew;
mpls@ietf.org;
> ccamp@ietf.org; mpls-tp@ietf.org; pwe3@ietf.org
> Subject: Re: [mpls-tp] [PWE3] FW: Changes to PW ACH Channel Type
> allocationpolicy
> 
> Shahram Davari wrote:
>> Hi,
>> 
>> I also prefer the method that Wishwas proposed. This has many advantages:
>> 
>> 1) Allows vendors to not expose their proprietary techniques to their
>> competitors.
> 
>  From the POV of an operator, this is actually a substantial disadvantage.
> 
> [Shahram] OTOH it encourages more innovation and differentiation by
vendors.

    That is hogwash. Customers encourage vendors to innovate not standards
bodies. Standards bodies help encourage and foster interoperability of a
common specification. The latter is the important point Shane is making (as
am I and others who are the customers in this equation). We don't want to
encourage proprietary implementations for the sake of proprietary
implementations; we want to encourage them to ultimately interoperate on a
common specification. However, if your goal as a vendor is to create
proprietary implementations you are free to do so, but you do not need the
IETF unless you are looking for some sort of rubber stamp of approval.

    --Tom


  
>> 2) reduces the load of reviewing by IETF and PWE3
> 
> OTOH, the benefit of such reviews by the IETF and PWE3 is when
> "commonality" among similar applications are discovered they can be
> standardized, rather kept proprietary.
> 
> [Shahram] Not if the inventing vendor is not willing to do so.
> 
> 
>> 3) results a faster time to market, since no expert review will be needed
> 
> True, to some extent.  But, IMHO, I would much rather see a *slightly*
> slower process involving a careful expert review and/or IETF consensus
> to make sure we're not: a) unnecessarily duplicating work; and, b) at
> the same time, encouraging more standards-based approach.
> 
> 
>> 4) provides more codepoint space that the ACH channel type
> 
> This is false.  There is no shortage on ACH channel types today.
> [Shahram] You are correct. 16-bit is sufficient enough.
> 
> 
>> 5) only one VCCV ACH channel type needs to be configured in each box for
>> vendor specific filtering
>> 
>> The 2nd method has the first 3 advantages only, and the first method has
none
>> of these advantages.
> 
> 
> Also, let's take a step back here.  Wasn't the whole point with the
> joint ITU-T/IETF effort surrounding MPLS-TP to create an environment in
> which MPLS-TP could seamlessly interoperate within (existing) MPLS
> environments?  I thought a fundamental part of that work is striving
> towards creating a *standards-based* MPLS-TP data-plane, OAM, signaling,
> etc. mechanisms.  IMO, Vishwas' proposal and Matthew's proposal #2 seems
> to run contrary to that goal.
> 
> [Shahram] off course we should all encourage standards methods. But we
should
> provide a fast and reasonable procedure for vendor specific protocols that
> don't affect interoperability. I worry that in first method competitors
may
> vote down code point requests for commercial reasons.
> 
> -shane (speaking only for himself, not as co-chair)
> 
> 
> 

_______________________________________________
pwe3 mailing list
pwe3@ietf.org
https://www.ietf.org/mailman/listinfo/pwe3

_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls


From mpls-bounces@ietf.org  Fri Oct  3 06:19:28 2008
Return-Path: <mpls-bounces@ietf.org>
X-Original-To: mpls-archive@megatron.ietf.org
Delivered-To: ietfarch-mpls-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 93EFD28C244;
	Fri,  3 Oct 2008 06:19:28 -0700 (PDT)
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 8C4133A68E1;
	Thu,  2 Oct 2008 11:05:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.097
X-Spam-Level: 
X-Spam-Status: No, score=-1.097 tagged_above=-999 required=5 tests=[AWL=0.435, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, RCVD_NUMERIC_HELO=2.067]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id ZergAiywSVqS; Thu,  2 Oct 2008 11:05:49 -0700 (PDT)
Received: from smtp1.smtp.bt.com (smtp1.smtp.bt.com [217.32.164.137])
	by core3.amsl.com (Postfix) with ESMTP id 476313A6816;
	Thu,  2 Oct 2008 11:05:49 -0700 (PDT)
Received: from E03MVZ2-UKDY.domain1.systemhost.net ([193.113.30.65]) by
	smtp1.smtp.bt.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 2 Oct 2008 19:06:14 +0100
Received: from 217.32.164.172 ([217.32.164.172]) by
	E03MVZ2-UKDY.domain1.systemhost.net ([193.113.30.120]) via
	Exchange Front-End Server mail.bt.com ([193.113.197.26]) with
	Microsoft Exchange Server HTTP-DAV ; Thu,  2 Oct 2008 18:06:13 +0000
User-Agent: Microsoft-Entourage/12.12.0.080729
Date: Thu, 02 Oct 2008 14:06:12 -0400
From: "Thomas D. Nadeau" <tom.nadeau@bt.com>
To: <davarish@yahoo.com>, 'Shahram Davari' <davari@tpack.com>,
	'Shane Amante' <shane@castlepoint.net>
Message-ID: <C50A85D4.E273%tom.nadeau@bt.com>
Thread-Topic: [Bulk] Re: [PWE3] [mpls-tp] FW: Changes to PW ACH Channel Type
	allocationpolicy
Thread-Index: AckkqLTHdNDdblepSIu2W52R3r7OPAABUvW5AAFN92AAAZVIgg==
In-Reply-To: <005901c924b3$b570bc20$20523460$@com>
Mime-version: 1.0
X-OriginalArrivalTime: 02 Oct 2008 18:06:14.0917 (UTC)
	FILETIME=[8F571B50:01C924B9]
X-Mailman-Approved-At: Fri, 03 Oct 2008 06:19:21 -0700
Cc: l2vpn@ietf.org, mpls@ietf.org,
	'BOCCI Matthew' <Matthew.Bocci@alcatel-lucent.com>,
	ccamp@ietf.org, mpls-tp@ietf.org, pwe3@ietf.org,
	'BUSI ITALO' <Italo.Busi@alcatel-lucent.it>
Subject: Re: [mpls] [Bulk] Re: [PWE3] [mpls-tp] FW: Changes to PW ACH
 Channel Type allocationpolicy
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mpls-bounces@ietf.org
Errors-To: mpls-bounces@ietf.org


    I suggest listening more closely to potential customers.

    --Tom


On 10/2/08 1:24 PM, "Shahram Davari" <davarish@yahoo.com> wrote:

> By the way I suggest using more polite language.
> 
> -shahram
> 
> -----Original Message-----
> From: pwe3-bounces@ietf.org [mailto:pwe3-bounces@ietf.org] On Behalf Of
> Thomas D. Nadeau
> Sent: October-02-08 12:44 PM
> To: Shahram Davari; Shane Amante
> Cc: l2vpn@ietf.org; mpls@ietf.org; BOCCI Matthew; ccamp@ietf.org;
> mpls-tp@ietf.org; pwe3@ietf.org; BUSI ITALO
> Subject: [Bulk] Re: [PWE3] [mpls-tp] FW: Changes to PW ACH Channel Type
> allocationpolicy
> 
> 
> 
>     I agree with %100 of Shane's comments. One bit to add below:
> 
>> Hi Shane,
>> 
>> Please see my response in-line.
>> 
>> Best regards,
>> Shahram
>> 
>> 
>> -----Original Message-----
>> From: Shane Amante [mailto:shane@castlepoint.net]
>> Sent: October-02-08 10:43 AM
>> To: Shahram Davari
>> Cc: BUSI ITALO; Vishwas Manral; l2vpn@ietf.org; BOCCI Matthew;
> mpls@ietf.org;
>> ccamp@ietf.org; mpls-tp@ietf.org; pwe3@ietf.org
>> Subject: Re: [mpls-tp] [PWE3] FW: Changes to PW ACH Channel Type
>> allocationpolicy
>> 
>> Shahram Davari wrote:
>>> Hi,
>>> 
>>> I also prefer the method that Wishwas proposed. This has many advantages:
>>> 
>>> 1) Allows vendors to not expose their proprietary techniques to their
>>> competitors.
>> 
>>  From the POV of an operator, this is actually a substantial disadvantage.
>> 
>> [Shahram] OTOH it encourages more innovation and differentiation by
> vendors.
> 
>     That is hogwash. Customers encourage vendors to innovate not standards
> bodies. Standards bodies help encourage and foster interoperability of a
> common specification. The latter is the important point Shane is making (as
> am I and others who are the customers in this equation). We don't want to
> encourage proprietary implementations for the sake of proprietary
> implementations; we want to encourage them to ultimately interoperate on a
> common specification. However, if your goal as a vendor is to create
> proprietary implementations you are free to do so, but you do not need the
> IETF unless you are looking for some sort of rubber stamp of approval.
> 
>     --Tom
> 
> 
>   
>>> 2) reduces the load of reviewing by IETF and PWE3
>> 
>> OTOH, the benefit of such reviews by the IETF and PWE3 is when
>> "commonality" among similar applications are discovered they can be
>> standardized, rather kept proprietary.
>> 
>> [Shahram] Not if the inventing vendor is not willing to do so.
>> 
>> 
>>> 3) results a faster time to market, since no expert review will be needed
>> 
>> True, to some extent.  But, IMHO, I would much rather see a *slightly*
>> slower process involving a careful expert review and/or IETF consensus
>> to make sure we're not: a) unnecessarily duplicating work; and, b) at
>> the same time, encouraging more standards-based approach.
>> 
>> 
>>> 4) provides more codepoint space that the ACH channel type
>> 
>> This is false.  There is no shortage on ACH channel types today.
>> [Shahram] You are correct. 16-bit is sufficient enough.
>> 
>> 
>>> 5) only one VCCV ACH channel type needs to be configured in each box for
>>> vendor specific filtering
>>> 
>>> The 2nd method has the first 3 advantages only, and the first method has
> none
>>> of these advantages.
>> 
>> 
>> Also, let's take a step back here.  Wasn't the whole point with the
>> joint ITU-T/IETF effort surrounding MPLS-TP to create an environment in
>> which MPLS-TP could seamlessly interoperate within (existing) MPLS
>> environments?  I thought a fundamental part of that work is striving
>> towards creating a *standards-based* MPLS-TP data-plane, OAM, signaling,
>> etc. mechanisms.  IMO, Vishwas' proposal and Matthew's proposal #2 seems
>> to run contrary to that goal.
>> 
>> [Shahram] off course we should all encourage standards methods. But we
> should
>> provide a fast and reasonable procedure for vendor specific protocols that
>> don't affect interoperability. I worry that in first method competitors
> may
>> vote down code point requests for commercial reasons.
>> 
>> -shane (speaking only for himself, not as co-chair)
>> 
>> 
>> 
> 
> _______________________________________________
> pwe3 mailing list
> pwe3@ietf.org
> https://www.ietf.org/mailman/listinfo/pwe3
> 

_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls


From mpls-bounces@ietf.org  Fri Oct  3 06:19:29 2008
Return-Path: <mpls-bounces@ietf.org>
X-Original-To: mpls-archive@megatron.ietf.org
Delivered-To: ietfarch-mpls-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 2C4F528C24A;
	Fri,  3 Oct 2008 06:19:29 -0700 (PDT)
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B07E728C18E;
	Thu,  2 Oct 2008 11:36:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id IqN4U725IZ5f; Thu,  2 Oct 2008 11:36:10 -0700 (PDT)
Received: from napoleon.monoski.com (black.monoski.com [63.227.123.238])
	by core3.amsl.com (Postfix) with ESMTP id 9AC033A68E1;
	Thu,  2 Oct 2008 11:36:09 -0700 (PDT)
Received: from confusion.monoski.com (confusion.monoski.com [209.245.27.2])
	(authenticated bits=0)
	by napoleon.monoski.com (8.13.8/8.13.8) with ESMTP id m92IHF0f012751
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Thu, 2 Oct 2008 12:17:15 -0600 (MDT)
Message-ID: <48E5102B.3050307@cisco.com>
Date: Thu, 02 Oct 2008 12:17:15 -0600
From: Luca Martini <lmartini@cisco.com>
User-Agent: Thunderbird 2.0.0.12 (X11/20080213)
MIME-Version: 1.0
To: Shahram Davari <davari@tpack.com>
References: <16a42c48f46e6547a1c3ce65f8fee99a@mail.cph.tpack.net>
In-Reply-To: <16a42c48f46e6547a1c3ce65f8fee99a@mail.cph.tpack.net>
X-Scanned-By: MIMEDefang 2.63 on 209.245.27.1
X-Mailman-Approved-At: Fri, 03 Oct 2008 06:19:21 -0700
Cc: "Thomas D. Nadeau" <tom.nadeau@bt.com>, "mpls@ietf.org" <mpls@ietf.org>,
	BOCCI Matthew <Matthew.Bocci@alcatel-lucent.com>,
	"ccamp@ietf.org" <ccamp@ietf.org>, "l2vpn@ietf.org" <l2vpn@ietf.org>,
	"pwe3@ietf.org" <pwe3@ietf.org>, BUSI ITALO <Italo.Busi@alcatel-lucent.it>,
	"mpls-tp@ietf.org" <mpls-tp@ietf.org>
Subject: Re: [mpls] [PWE3] [mpls-tp] FW: Changes to PW ACH Channel
	Type	allocationpolicy
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: mpls-bounces@ietf.org
Errors-To: mpls-bounces@ietf.org

Shahram,
the point of expert review is not to prevent vendor specific OAM 
methods. It is to prevent duplication, and guide implementors in the 
right direction.
For example , if somebody needs a new PW type , for a very vendor 
specific protocol , say Apollo DDS ( I was the last recorded user of 
that ;-) ), but asks for an ACH type instead , the expert can advise to 
use a new pw type. In the end there is no enforcement method, so any 
vendor can do anything they want. The only part we can do here , is have 
some sane documentation of the methods we put in the registry. ( 
documentation could be as short a a line , or as long as a draft )

Luca


Shahram Davari wrote:
> No one asked for IETF rubber stamping. I asked for a mechanism (code point assignment) that easily implement vendor specific methods. I don't see any reason why IETF should review and approve a vendor specific method. If IETF doesn't want to see any vendor specific method, then it doesn't need to allocate any code points. However, if IETF wants to encourage vendor specific protocols then it must do so in a way that makes it easy for vendors to use it.
>
> -Shahram
>
>
> -----Original Message-----
> From: Thomas D. Nadeau [mailto:tom.nadeau@bt.com] 
> Sent: October-02-08 12:44 PM
> To: Shahram Davari; Shane Amante
> Cc: l2vpn@ietf.org; mpls@ietf.org; BOCCI Matthew; ccamp@ietf.org; mpls-tp@ietf.org; Vishwas Manral; pwe3@ietf.org; BUSI ITALO
> Subject: Re: [mpls-tp] [PWE3] FW: Changes to PW ACH Channel Type allocationpolicy
>
>
>
>     I agree with %100 of Shane's comments. One bit to add below:
>
>   
>> Hi Shane,
>>
>> Please see my response in-line.
>>
>> Best regards,
>> Shahram
>>
>>
>> -----Original Message-----
>> From: Shane Amante [mailto:shane@castlepoint.net]
>> Sent: October-02-08 10:43 AM
>> To: Shahram Davari
>> Cc: BUSI ITALO; Vishwas Manral; l2vpn@ietf.org; BOCCI Matthew; mpls@ietf.org;
>> ccamp@ietf.org; mpls-tp@ietf.org; pwe3@ietf.org
>> Subject: Re: [mpls-tp] [PWE3] FW: Changes to PW ACH Channel Type
>> allocationpolicy
>>
>> Shahram Davari wrote:
>>     
>>> Hi,
>>>
>>> I also prefer the method that Wishwas proposed. This has many advantages:
>>>
>>> 1) Allows vendors to not expose their proprietary techniques to their
>>> competitors.
>>>       
>>  From the POV of an operator, this is actually a substantial disadvantage.
>>
>> [Shahram] OTOH it encourages more innovation and differentiation by vendors.
>>     
>
>     That is hogwash. Customers encourage vendors to innovate not standards
> bodies. Standards bodies help encourage and foster interoperability of a
> common specification. The latter is the important point Shane is making (as
> am I and others who are the customers in this equation). We don't want to
> encourage proprietary implementations for the sake of proprietary
> implementations; we want to encourage them to ultimately interoperate on a
> common specification. However, if your goal as a vendor is to create
> proprietary implementations you are free to do so, but you do not need the
> IETF unless you are looking for some sort of rubber stamp of approval.
>
>     --Tom
>
>
>   
>   
>>> 2) reduces the load of reviewing by IETF and PWE3
>>>       
>> OTOH, the benefit of such reviews by the IETF and PWE3 is when
>> "commonality" among similar applications are discovered they can be
>> standardized, rather kept proprietary.
>>
>> [Shahram] Not if the inventing vendor is not willing to do so.
>>
>>
>>     
>>> 3) results a faster time to market, since no expert review will be needed
>>>       
>> True, to some extent.  But, IMHO, I would much rather see a *slightly*
>> slower process involving a careful expert review and/or IETF consensus
>> to make sure we're not: a) unnecessarily duplicating work; and, b) at
>> the same time, encouraging more standards-based approach.
>>
>>
>>     
>>> 4) provides more codepoint space that the ACH channel type
>>>       
>> This is false.  There is no shortage on ACH channel types today.
>> [Shahram] You are correct. 16-bit is sufficient enough.
>>
>>
>>     
>>> 5) only one VCCV ACH channel type needs to be configured in each box for
>>> vendor specific filtering
>>>
>>> The 2nd method has the first 3 advantages only, and the first method has none
>>> of these advantages.
>>>       
>> Also, let's take a step back here.  Wasn't the whole point with the
>> joint ITU-T/IETF effort surrounding MPLS-TP to create an environment in
>> which MPLS-TP could seamlessly interoperate within (existing) MPLS
>> environments?  I thought a fundamental part of that work is striving
>> towards creating a *standards-based* MPLS-TP data-plane, OAM, signaling,
>> etc. mechanisms.  IMO, Vishwas' proposal and Matthew's proposal #2 seems
>> to run contrary to that goal.
>>
>> [Shahram] off course we should all encourage standards methods. But we should
>> provide a fast and reasonable procedure for vendor specific protocols that
>> don't affect interoperability. I worry that in first method competitors may
>> vote down code point requests for commercial reasons.
>>
>> -shane (speaking only for himself, not as co-chair)
>>
>>
>>
>>     
>
>
>
>
> _______________________________________________
> pwe3 mailing list
> pwe3@ietf.org
> https://www.ietf.org/mailman/listinfo/pwe3
>   

_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls


From mpls-bounces@ietf.org  Fri Oct  3 06:19:29 2008
Return-Path: <mpls-bounces@ietf.org>
X-Original-To: mpls-archive@megatron.ietf.org
Delivered-To: ietfarch-mpls-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B8A3728C24D;
	Fri,  3 Oct 2008 06:19:29 -0700 (PDT)
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E192F3A6A8A
	for <mpls@core3.amsl.com>; Thu,  2 Oct 2008 13:25:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id g5WIi5Hm4DMM for <mpls@core3.amsl.com>;
	Thu,  2 Oct 2008 13:25:36 -0700 (PDT)
Received: from smtp122.rog.mail.re2.yahoo.com (smtp122.rog.mail.re2.yahoo.com
	[206.190.53.27]) by core3.amsl.com (Postfix) with SMTP id 3BD1A3A6869
	for <mpls@ietf.org>; Thu,  2 Oct 2008 13:25:36 -0700 (PDT)
Received: (qmail 99038 invoked from network); 2 Oct 2008 20:25:06 -0000
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com;
	h=Received:X-YMail-OSG:X-Yahoo-Newman-Property:Reply-To:From:To:Cc:References:In-Reply-To:Subject:Date:Message-ID:MIME-Version:Content-Type:Content-Transfer-Encoding:X-Mailer:Thread-Index:Content-Language;
	b=Bkrgxx/lP0lpJjR1AyHo/RRAuK9elUpEU39yGjluDdh5tx+BKgIERGGjXM0rqUQ5s8BlQgjB3s4iOHk+lSPCA0F6H+W4gVQXCaQAiB9xj/wbTWgttOxJBJUwc5jTBf3uzmblgksqGmMeuoXyhtekH6WQhR/tqSWjQGCHiPTHcNA=
	; 
Received: from unknown (HELO ShahramPC) (davarish@99.238.119.231 with login)
	by smtp122.rog.mail.re2.yahoo.com with SMTP; 2 Oct 2008 20:25:06 -0000
X-YMail-OSG: RpJj4QsVM1m.TRc.duc4uCtVExQBKevDbrb4zBth9u5f9Q5D3BXqAfkdfaxrh7fOqA--
X-Yahoo-Newman-Property: ymail-3
From: "Shahram Davari" <davarish@yahoo.com>
To: "'Luca Martini'" <lmartini@cisco.com>,
	"'Shahram Davari'" <davari@tpack.com>
References: <16a42c48f46e6547a1c3ce65f8fee99a@mail.cph.tpack.net>
	<48E5102B.3050307@cisco.com>
In-Reply-To: <48E5102B.3050307@cisco.com>
Date: Thu, 2 Oct 2008 16:25:01 -0400
Message-ID: <007201c924cc$f33d50e0$d9b7f2a0$@com>
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AckkvdGPtz/Y6awOSfaI1w1hcyIcdQADVAkQ
Content-Language: en-ca
X-Mailman-Approved-At: Fri, 03 Oct 2008 06:19:21 -0700
Cc: l2vpn@ietf.org, mpls@ietf.org,
	'BOCCI Matthew' <Matthew.Bocci@alcatel-lucent.com>,
	ccamp@ietf.org, mpls-tp@ietf.org, pwe3@ietf.org,
	'BUSI ITALO' <Italo.Busi@alcatel-lucent.it>
Subject: Re: [mpls] [Bulk] Re: [PWE3] [mpls-tp] FW: Changes to PW ACH
	Channel	Type	allocation policy
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: davarish@yahoo.com
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mpls-bounces@ietf.org
Errors-To: mpls-bounces@ietf.org

Hi Luca,

Are you saying that method 1 does not require IETF consensus? If so then
method 1 and 2 are essentially the same except that in Method 1, applicants
are forced to file for patent before writing the drafts (since writing a
draft is a form of public disclosure) asking for code points. While in the
2nd method they can choose not to file any patents or file patents
afterwards. 

Regards,
Shahram

-----Original Message-----
From: pwe3-bounces@ietf.org [mailto:pwe3-bounces@ietf.org] On Behalf Of Luca
Martini
Sent: October-02-08 2:17 PM
To: Shahram Davari
Cc: mpls@ietf.org; BOCCI Matthew; ccamp@ietf.org; l2vpn@ietf.org;
pwe3@ietf.org; BUSI ITALO; Shane Amante; mpls-tp@ietf.org
Subject: [Bulk] Re: [PWE3] [mpls-tp] FW: Changes to PW ACH Channel Type
allocationpolicy

Shahram,
the point of expert review is not to prevent vendor specific OAM 
methods. It is to prevent duplication, and guide implementors in the 
right direction.
For example , if somebody needs a new PW type , for a very vendor 
specific protocol , say Apollo DDS ( I was the last recorded user of 
that ;-) ), but asks for an ACH type instead , the expert can advise to 
use a new pw type. In the end there is no enforcement method, so any 
vendor can do anything they want. The only part we can do here , is have 
some sane documentation of the methods we put in the registry. ( 
documentation could be as short a a line , or as long as a draft )

Luca


Shahram Davari wrote:
> No one asked for IETF rubber stamping. I asked for a mechanism (code point
assignment) that easily implement vendor specific methods. I don't see any
reason why IETF should review and approve a vendor specific method. If IETF
doesn't want to see any vendor specific method, then it doesn't need to
allocate any code points. However, if IETF wants to encourage vendor
specific protocols then it must do so in a way that makes it easy for
vendors to use it.
>
> -Shahram
>
>
> -----Original Message-----
> From: Thomas D. Nadeau [mailto:tom.nadeau@bt.com] 
> Sent: October-02-08 12:44 PM
> To: Shahram Davari; Shane Amante
> Cc: l2vpn@ietf.org; mpls@ietf.org; BOCCI Matthew; ccamp@ietf.org;
mpls-tp@ietf.org; Vishwas Manral; pwe3@ietf.org; BUSI ITALO
> Subject: Re: [mpls-tp] [PWE3] FW: Changes to PW ACH Channel Type
allocationpolicy
>
>
>
>     I agree with %100 of Shane's comments. One bit to add below:
>
>   
>> Hi Shane,
>>
>> Please see my response in-line.
>>
>> Best regards,
>> Shahram
>>
>>
>> -----Original Message-----
>> From: Shane Amante [mailto:shane@castlepoint.net]
>> Sent: October-02-08 10:43 AM
>> To: Shahram Davari
>> Cc: BUSI ITALO; Vishwas Manral; l2vpn@ietf.org; BOCCI Matthew;
mpls@ietf.org;
>> ccamp@ietf.org; mpls-tp@ietf.org; pwe3@ietf.org
>> Subject: Re: [mpls-tp] [PWE3] FW: Changes to PW ACH Channel Type
>> allocationpolicy
>>
>> Shahram Davari wrote:
>>     
>>> Hi,
>>>
>>> I also prefer the method that Wishwas proposed. This has many
advantages:
>>>
>>> 1) Allows vendors to not expose their proprietary techniques to their
>>> competitors.
>>>       
>>  From the POV of an operator, this is actually a substantial
disadvantage.
>>
>> [Shahram] OTOH it encourages more innovation and differentiation by
vendors.
>>     
>
>     That is hogwash. Customers encourage vendors to innovate not standards
> bodies. Standards bodies help encourage and foster interoperability of a
> common specification. The latter is the important point Shane is making
(as
> am I and others who are the customers in this equation). We don't want to
> encourage proprietary implementations for the sake of proprietary
> implementations; we want to encourage them to ultimately interoperate on a
> common specification. However, if your goal as a vendor is to create
> proprietary implementations you are free to do so, but you do not need the
> IETF unless you are looking for some sort of rubber stamp of approval.
>
>     --Tom
>
>
>   
>   
>>> 2) reduces the load of reviewing by IETF and PWE3
>>>       
>> OTOH, the benefit of such reviews by the IETF and PWE3 is when
>> "commonality" among similar applications are discovered they can be
>> standardized, rather kept proprietary.
>>
>> [Shahram] Not if the inventing vendor is not willing to do so.
>>
>>
>>     
>>> 3) results a faster time to market, since no expert review will be
needed
>>>       
>> True, to some extent.  But, IMHO, I would much rather see a *slightly*
>> slower process involving a careful expert review and/or IETF consensus
>> to make sure we're not: a) unnecessarily duplicating work; and, b) at
>> the same time, encouraging more standards-based approach.
>>
>>
>>     
>>> 4) provides more codepoint space that the ACH channel type
>>>       
>> This is false.  There is no shortage on ACH channel types today.
>> [Shahram] You are correct. 16-bit is sufficient enough.
>>
>>
>>     
>>> 5) only one VCCV ACH channel type needs to be configured in each box for
>>> vendor specific filtering
>>>
>>> The 2nd method has the first 3 advantages only, and the first method has
none
>>> of these advantages.
>>>       
>> Also, let's take a step back here.  Wasn't the whole point with the
>> joint ITU-T/IETF effort surrounding MPLS-TP to create an environment in
>> which MPLS-TP could seamlessly interoperate within (existing) MPLS
>> environments?  I thought a fundamental part of that work is striving
>> towards creating a *standards-based* MPLS-TP data-plane, OAM, signaling,
>> etc. mechanisms.  IMO, Vishwas' proposal and Matthew's proposal #2 seems
>> to run contrary to that goal.
>>
>> [Shahram] off course we should all encourage standards methods. But we
should
>> provide a fast and reasonable procedure for vendor specific protocols
that
>> don't affect interoperability. I worry that in first method competitors
may
>> vote down code point requests for commercial reasons.
>>
>> -shane (speaking only for himself, not as co-chair)
>>
>>
>>
>>     
>
>
>
>
> _______________________________________________
> pwe3 mailing list
> pwe3@ietf.org
> https://www.ietf.org/mailman/listinfo/pwe3
>   

_______________________________________________
pwe3 mailing list
pwe3@ietf.org
https://www.ietf.org/mailman/listinfo/pwe3

_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls


From mpls-bounces@ietf.org  Fri Oct  3 06:19:30 2008
Return-Path: <mpls-bounces@ietf.org>
X-Original-To: mpls-archive@megatron.ietf.org
Delivered-To: ietfarch-mpls-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 5576628C257;
	Fri,  3 Oct 2008 06:19:30 -0700 (PDT)
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 086B13A6AD6;
	Fri,  3 Oct 2008 00:08:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.249
X-Spam-Level: 
X-Spam-Status: No, score=-2.249 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, HELO_EQ_FR=0.35]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id RNiKtBhCuwVM; Fri,  3 Oct 2008 00:08:33 -0700 (PDT)
Received: from smail5.alcatel.fr (smail5.alcatel.fr [62.23.212.27])
	by core3.amsl.com (Postfix) with ESMTP id 7E5BB3A6AAC;
	Fri,  3 Oct 2008 00:08:32 -0700 (PDT)
Received: from FRVELSBHS04.ad2.ad.alcatel.com (frvelsbhs04.ad2.ad.alcatel.com
	[155.132.6.76])
	by smail5.alcatel.fr (8.13.8/8.13.8/ICT) with ESMTP id m9378NWJ018246; 
	Fri, 3 Oct 2008 09:08:23 +0200
Received: from FRVELSMBS21.ad2.ad.alcatel.com ([155.132.6.55]) by
	FRVELSBHS04.ad2.ad.alcatel.com with Microsoft
	SMTPSVC(6.0.3790.2499); Fri, 3 Oct 2008 09:08:22 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Fri, 3 Oct 2008 09:08:33 +0200
Message-ID: <6FD21B53861BF44AA90A288402036AB40193F9DB@FRVELSMBS21.ad2.ad.alcatel.com>
In-Reply-To: <48E5102B.3050307@cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [PWE3] [mpls-tp] FW: Changes to PW ACH Channel
	Type	allocationpolicy
Thread-Index: AckkuyRk9yMIazY1RJes0DDgekoCjwAapu8g
References: <16a42c48f46e6547a1c3ce65f8fee99a@mail.cph.tpack.net>
	<48E5102B.3050307@cisco.com>
From: "BUSI ITALO" <Italo.Busi@alcatel-lucent.it>
To: "Luca Martini" <lmartini@cisco.com>, "Shahram Davari" <davari@tpack.com>
X-OriginalArrivalTime: 03 Oct 2008 07:08:22.0917 (UTC)
	FILETIME=[D29BA350:01C92526]
X-Scanned-By: MIMEDefang 2.57 on 155.132.188.13
X-Mailman-Approved-At: Fri, 03 Oct 2008 06:19:21 -0700
Cc: "Thomas D. Nadeau" <tom.nadeau@bt.com>, mpls@ietf.org,
	BOCCI Matthew <Matthew.Bocci@alcatel-lucent.com>, ccamp@ietf.org,
	l2vpn@ietf.org, pwe3@ietf.org, mpls-tp@ietf.org
Subject: Re: [mpls] [PWE3] [mpls-tp] FW: Changes to PW ACH Channel
	Type	allocationpolicy
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mpls-bounces@ietf.org
Errors-To: mpls-bounces@ietf.org

Luca,

Reading your mail, I understand that Expert Review is just providing an
advice and cannot enforce the requestor.

However, this is in contradiction from what I can understand reading RFC
4446 and in particulare the statement saying that "The expert reviewing
the request MUST approve or disapprove ...".

My understanding of RFC 4446 is that the experts can disapprove the
request and avoid the requestor using the ACH for its own proprietary
protocol.

Could you please clarify whether I am misunderstanding you or RFC 4446?

Thanks, Italo

> -----Original Message-----
> From: Luca Martini [mailto:lmartini@cisco.com] 
> Sent: Thursday, October 02, 2008 8:17 PM
> To: Shahram Davari
> Cc: Thomas D. Nadeau; Shane Amante; l2vpn@ietf.org; 
> mpls@ietf.org; BOCCI Matthew; ccamp@ietf.org; 
> mpls-tp@ietf.org; pwe3@ietf.org; BUSI ITALO
> Subject: Re: [PWE3] [mpls-tp] FW: Changes to PW ACH Channel 
> Type allocationpolicy
> 
> Shahram,
> the point of expert review is not to prevent vendor specific OAM 
> methods. It is to prevent duplication, and guide implementors in the 
> right direction.
> For example , if somebody needs a new PW type , for a very vendor 
> specific protocol , say Apollo DDS ( I was the last recorded user of 
> that ;-) ), but asks for an ACH type instead , the expert can 
> advise to 
> use a new pw type. In the end there is no enforcement method, so any 
> vendor can do anything they want. The only part we can do 
> here , is have 
> some sane documentation of the methods we put in the registry. ( 
> documentation could be as short a a line , or as long as a draft )
> 
> Luca
> 
> 
> Shahram Davari wrote:
> > No one asked for IETF rubber stamping. I asked for a 
> mechanism (code point assignment) that easily implement 
> vendor specific methods. I don't see any reason why IETF 
> should review and approve a vendor specific method. If IETF 
> doesn't want to see any vendor specific method, then it 
> doesn't need to allocate any code points. However, if IETF 
> wants to encourage vendor specific protocols then it must do 
> so in a way that makes it easy for vendors to use it.
> >
> > -Shahram
> >
> >
> > -----Original Message-----
> > From: Thomas D. Nadeau [mailto:tom.nadeau@bt.com] 
> > Sent: October-02-08 12:44 PM
> > To: Shahram Davari; Shane Amante
> > Cc: l2vpn@ietf.org; mpls@ietf.org; BOCCI Matthew; 
> ccamp@ietf.org; mpls-tp@ietf.org; Vishwas Manral; 
> pwe3@ietf.org; BUSI ITALO
> > Subject: Re: [mpls-tp] [PWE3] FW: Changes to PW ACH Channel 
> Type allocationpolicy
> >
> >
> >
> >     I agree with %100 of Shane's comments. One bit to add below:
> >
> >   
> >> Hi Shane,
> >>
> >> Please see my response in-line.
> >>
> >> Best regards,
> >> Shahram
> >>
> >>
> >> -----Original Message-----
> >> From: Shane Amante [mailto:shane@castlepoint.net]
> >> Sent: October-02-08 10:43 AM
> >> To: Shahram Davari
> >> Cc: BUSI ITALO; Vishwas Manral; l2vpn@ietf.org; BOCCI 
> Matthew; mpls@ietf.org;
> >> ccamp@ietf.org; mpls-tp@ietf.org; pwe3@ietf.org
> >> Subject: Re: [mpls-tp] [PWE3] FW: Changes to PW ACH Channel Type
> >> allocationpolicy
> >>
> >> Shahram Davari wrote:
> >>     
> >>> Hi,
> >>>
> >>> I also prefer the method that Wishwas proposed. This has 
> many advantages:
> >>>
> >>> 1) Allows vendors to not expose their proprietary 
> techniques to their
> >>> competitors.
> >>>       
> >>  From the POV of an operator, this is actually a 
> substantial disadvantage.
> >>
> >> [Shahram] OTOH it encourages more innovation and 
> differentiation by vendors.
> >>     
> >
> >     That is hogwash. Customers encourage vendors to 
> innovate not standards
> > bodies. Standards bodies help encourage and foster 
> interoperability of a
> > common specification. The latter is the important point 
> Shane is making (as
> > am I and others who are the customers in this equation). We 
> don't want to
> > encourage proprietary implementations for the sake of proprietary
> > implementations; we want to encourage them to ultimately 
> interoperate on a
> > common specification. However, if your goal as a vendor is to create
> > proprietary implementations you are free to do so, but you 
> do not need the
> > IETF unless you are looking for some sort of rubber stamp 
> of approval.
> >
> >     --Tom
> >
> >
> >   
> >   
> >>> 2) reduces the load of reviewing by IETF and PWE3
> >>>       
> >> OTOH, the benefit of such reviews by the IETF and PWE3 is when
> >> "commonality" among similar applications are discovered they can be
> >> standardized, rather kept proprietary.
> >>
> >> [Shahram] Not if the inventing vendor is not willing to do so.
> >>
> >>
> >>     
> >>> 3) results a faster time to market, since no expert 
> review will be needed
> >>>       
> >> True, to some extent.  But, IMHO, I would much rather see 
> a *slightly*
> >> slower process involving a careful expert review and/or 
> IETF consensus
> >> to make sure we're not: a) unnecessarily duplicating work; 
> and, b) at
> >> the same time, encouraging more standards-based approach.
> >>
> >>
> >>     
> >>> 4) provides more codepoint space that the ACH channel type
> >>>       
> >> This is false.  There is no shortage on ACH channel types today.
> >> [Shahram] You are correct. 16-bit is sufficient enough.
> >>
> >>
> >>     
> >>> 5) only one VCCV ACH channel type needs to be configured 
> in each box for
> >>> vendor specific filtering
> >>>
> >>> The 2nd method has the first 3 advantages only, and the 
> first method has none
> >>> of these advantages.
> >>>       
> >> Also, let's take a step back here.  Wasn't the whole point with the
> >> joint ITU-T/IETF effort surrounding MPLS-TP to create an 
> environment in
> >> which MPLS-TP could seamlessly interoperate within (existing) MPLS
> >> environments?  I thought a fundamental part of that work 
> is striving
> >> towards creating a *standards-based* MPLS-TP data-plane, 
> OAM, signaling,
> >> etc. mechanisms.  IMO, Vishwas' proposal and Matthew's 
> proposal #2 seems
> >> to run contrary to that goal.
> >>
> >> [Shahram] off course we should all encourage standards 
> methods. But we should
> >> provide a fast and reasonable procedure for vendor 
> specific protocols that
> >> don't affect interoperability. I worry that in first 
> method competitors may
> >> vote down code point requests for commercial reasons.
> >>
> >> -shane (speaking only for himself, not as co-chair)
> >>
> >>
> >>
> >>     
> >
> >
> >
> >
> > _______________________________________________
> > pwe3 mailing list
> > pwe3@ietf.org
> > https://www.ietf.org/mailman/listinfo/pwe3
> >   
> 
> 
_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls


From mpls-bounces@ietf.org  Fri Oct  3 06:19:31 2008
Return-Path: <mpls-bounces@ietf.org>
X-Original-To: mpls-archive@megatron.ietf.org
Delivered-To: ietfarch-mpls-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id EED5C28C262;
	Fri,  3 Oct 2008 06:19:30 -0700 (PDT)
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 958EC3A6AD7;
	Fri,  3 Oct 2008 00:14:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.249
X-Spam-Level: 
X-Spam-Status: No, score=-2.249 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, HELO_EQ_FR=0.35]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id rCACpJdC2g2n; Fri,  3 Oct 2008 00:14:00 -0700 (PDT)
Received: from smail5.alcatel.fr (smail5.alcatel.fr [62.23.212.27])
	by core3.amsl.com (Postfix) with ESMTP id ED0DB3A6ACB;
	Fri,  3 Oct 2008 00:13:59 -0700 (PDT)
Received: from FRVELSBHS06.ad2.ad.alcatel.com (frvelsbhs06.ad2.ad.alcatel.com
	[155.132.6.78])
	by smail5.alcatel.fr (8.13.8/8.13.8/ICT) with ESMTP id m937DVUc021898; 
	Fri, 3 Oct 2008 09:13:31 +0200
Received: from FRVELSMBS21.ad2.ad.alcatel.com ([155.132.6.55]) by
	FRVELSBHS06.ad2.ad.alcatel.com with Microsoft
	SMTPSVC(6.0.3790.2499); Fri, 3 Oct 2008 09:13:31 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Fri, 3 Oct 2008 09:13:41 +0200
Message-ID: <6FD21B53861BF44AA90A288402036AB40193F9DC@FRVELSMBS21.ad2.ad.alcatel.com>
In-Reply-To: <48E5102B.3050307@cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [PWE3] [mpls-tp] FW: Changes to PW ACH Channel
	Type	allocationpolicy
Thread-Index: AckkuyRk9yMIazY1RJes0DDgekoCjwAa9C2w
References: <16a42c48f46e6547a1c3ce65f8fee99a@mail.cph.tpack.net>
	<48E5102B.3050307@cisco.com>
From: "BUSI ITALO" <Italo.Busi@alcatel-lucent.it>
To: "Luca Martini" <lmartini@cisco.com>, "Shahram Davari" <davari@tpack.com>
X-OriginalArrivalTime: 03 Oct 2008 07:13:31.0834 (UTC)
	FILETIME=[8ABCA1A0:01C92527]
X-Scanned-By: MIMEDefang 2.57 on 155.132.188.13
X-Mailman-Approved-At: Fri, 03 Oct 2008 06:19:21 -0700
Cc: "Thomas D. Nadeau" <tom.nadeau@bt.com>, mpls@ietf.org,
	BOCCI Matthew <Matthew.Bocci@alcatel-lucent.com>, ccamp@ietf.org,
	l2vpn@ietf.org, pwe3@ietf.org, mpls-tp@ietf.org
Subject: Re: [mpls] [PWE3] [mpls-tp] FW: Changes to PW ACH Channel
	Type	allocationpolicy
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mpls-bounces@ietf.org
Errors-To: mpls-bounces@ietf.org

Luca,

I fully agree with you that using an ACH for implementing a new PW type
for a very vendor specific protocol is a very bad idea.

However, I think that the best way to avoid people running proprietary
PW within a ACH is not to overload experts with these requests but to
clearly document that a vendor that wishes to implement a new PW type
for a very vendor specific protocol MUST define a new PW type.

Italo

> -----Original Message-----
> From: Luca Martini [mailto:lmartini@cisco.com] 
> Sent: Thursday, October 02, 2008 8:17 PM
> To: Shahram Davari
> Cc: Thomas D. Nadeau; Shane Amante; l2vpn@ietf.org; 
> mpls@ietf.org; BOCCI Matthew; ccamp@ietf.org; 
> mpls-tp@ietf.org; pwe3@ietf.org; BUSI ITALO
> Subject: Re: [PWE3] [mpls-tp] FW: Changes to PW ACH Channel 
> Type allocationpolicy
> 
> Shahram,
> the point of expert review is not to prevent vendor specific OAM 
> methods. It is to prevent duplication, and guide implementors in the 
> right direction.
> For example , if somebody needs a new PW type , for a very vendor 
> specific protocol , say Apollo DDS ( I was the last recorded user of 
> that ;-) ), but asks for an ACH type instead , the expert can 
> advise to 
> use a new pw type. In the end there is no enforcement method, so any 
> vendor can do anything they want. The only part we can do 
> here , is have 
> some sane documentation of the methods we put in the registry. ( 
> documentation could be as short a a line , or as long as a draft )
> 
> Luca
> 
> 
> Shahram Davari wrote:
> > No one asked for IETF rubber stamping. I asked for a 
> mechanism (code point assignment) that easily implement 
> vendor specific methods. I don't see any reason why IETF 
> should review and approve a vendor specific method. If IETF 
> doesn't want to see any vendor specific method, then it 
> doesn't need to allocate any code points. However, if IETF 
> wants to encourage vendor specific protocols then it must do 
> so in a way that makes it easy for vendors to use it.
> >
> > -Shahram
> >
> >
> > -----Original Message-----
> > From: Thomas D. Nadeau [mailto:tom.nadeau@bt.com] 
> > Sent: October-02-08 12:44 PM
> > To: Shahram Davari; Shane Amante
> > Cc: l2vpn@ietf.org; mpls@ietf.org; BOCCI Matthew; 
> ccamp@ietf.org; mpls-tp@ietf.org; Vishwas Manral; 
> pwe3@ietf.org; BUSI ITALO
> > Subject: Re: [mpls-tp] [PWE3] FW: Changes to PW ACH Channel 
> Type allocationpolicy
> >
> >
> >
> >     I agree with %100 of Shane's comments. One bit to add below:
> >
> >   
> >> Hi Shane,
> >>
> >> Please see my response in-line.
> >>
> >> Best regards,
> >> Shahram
> >>
> >>
> >> -----Original Message-----
> >> From: Shane Amante [mailto:shane@castlepoint.net]
> >> Sent: October-02-08 10:43 AM
> >> To: Shahram Davari
> >> Cc: BUSI ITALO; Vishwas Manral; l2vpn@ietf.org; BOCCI 
> Matthew; mpls@ietf.org;
> >> ccamp@ietf.org; mpls-tp@ietf.org; pwe3@ietf.org
> >> Subject: Re: [mpls-tp] [PWE3] FW: Changes to PW ACH Channel Type
> >> allocationpolicy
> >>
> >> Shahram Davari wrote:
> >>     
> >>> Hi,
> >>>
> >>> I also prefer the method that Wishwas proposed. This has 
> many advantages:
> >>>
> >>> 1) Allows vendors to not expose their proprietary 
> techniques to their
> >>> competitors.
> >>>       
> >>  From the POV of an operator, this is actually a 
> substantial disadvantage.
> >>
> >> [Shahram] OTOH it encourages more innovation and 
> differentiation by vendors.
> >>     
> >
> >     That is hogwash. Customers encourage vendors to 
> innovate not standards
> > bodies. Standards bodies help encourage and foster 
> interoperability of a
> > common specification. The latter is the important point 
> Shane is making (as
> > am I and others who are the customers in this equation). We 
> don't want to
> > encourage proprietary implementations for the sake of proprietary
> > implementations; we want to encourage them to ultimately 
> interoperate on a
> > common specification. However, if your goal as a vendor is to create
> > proprietary implementations you are free to do so, but you 
> do not need the
> > IETF unless you are looking for some sort of rubber stamp 
> of approval.
> >
> >     --Tom
> >
> >
> >   
> >   
> >>> 2) reduces the load of reviewing by IETF and PWE3
> >>>       
> >> OTOH, the benefit of such reviews by the IETF and PWE3 is when
> >> "commonality" among similar applications are discovered they can be
> >> standardized, rather kept proprietary.
> >>
> >> [Shahram] Not if the inventing vendor is not willing to do so.
> >>
> >>
> >>     
> >>> 3) results a faster time to market, since no expert 
> review will be needed
> >>>       
> >> True, to some extent.  But, IMHO, I would much rather see 
> a *slightly*
> >> slower process involving a careful expert review and/or 
> IETF consensus
> >> to make sure we're not: a) unnecessarily duplicating work; 
> and, b) at
> >> the same time, encouraging more standards-based approach.
> >>
> >>
> >>     
> >>> 4) provides more codepoint space that the ACH channel type
> >>>       
> >> This is false.  There is no shortage on ACH channel types today.
> >> [Shahram] You are correct. 16-bit is sufficient enough.
> >>
> >>
> >>     
> >>> 5) only one VCCV ACH channel type needs to be configured 
> in each box for
> >>> vendor specific filtering
> >>>
> >>> The 2nd method has the first 3 advantages only, and the 
> first method has none
> >>> of these advantages.
> >>>       
> >> Also, let's take a step back here.  Wasn't the whole point with the
> >> joint ITU-T/IETF effort surrounding MPLS-TP to create an 
> environment in
> >> which MPLS-TP could seamlessly interoperate within (existing) MPLS
> >> environments?  I thought a fundamental part of that work 
> is striving
> >> towards creating a *standards-based* MPLS-TP data-plane, 
> OAM, signaling,
> >> etc. mechanisms.  IMO, Vishwas' proposal and Matthew's 
> proposal #2 seems
> >> to run contrary to that goal.
> >>
> >> [Shahram] off course we should all encourage standards 
> methods. But we should
> >> provide a fast and reasonable procedure for vendor 
> specific protocols that
> >> don't affect interoperability. I worry that in first 
> method competitors may
> >> vote down code point requests for commercial reasons.
> >>
> >> -shane (speaking only for himself, not as co-chair)
> >>
> >>
> >>
> >>     
> >
> >
> >
> >
> > _______________________________________________
> > pwe3 mailing list
> > pwe3@ietf.org
> > https://www.ietf.org/mailman/listinfo/pwe3
> >   
> 
> 
_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls


From mpls-bounces@ietf.org  Fri Oct  3 06:31:50 2008
Return-Path: <mpls-bounces@ietf.org>
X-Original-To: mpls-archive@megatron.ietf.org
Delivered-To: ietfarch-mpls-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 874DA28C268;
	Fri,  3 Oct 2008 06:19:31 -0700 (PDT)
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id F36353A6923
	for <mpls@core3.amsl.com>; Fri,  3 Oct 2008 05:06:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id qPQwvN6mQW8u for <mpls@core3.amsl.com>;
	Fri,  3 Oct 2008 05:06:00 -0700 (PDT)
Received: from smtp115.rog.mail.re2.yahoo.com (smtp115.rog.mail.re2.yahoo.com
	[68.142.225.231])
	by core3.amsl.com (Postfix) with SMTP id 997653A67FC
	for <mpls@ietf.org>; Fri,  3 Oct 2008 05:05:59 -0700 (PDT)
Received: (qmail 21259 invoked from network); 3 Oct 2008 11:39:47 -0000
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com;
	h=Received:X-YMail-OSG:X-Yahoo-Newman-Property:Reply-To:From:To:Cc:References:In-Reply-To:Subject:Date:Message-ID:MIME-Version:Content-Type:Content-Transfer-Encoding:X-Mailer:Thread-Index:Content-Language;
	b=WFhw/b/T3OJEnSlQFohYMsT/1kPvrFGthGgm6tcn5oTTzpB6a76EXAbbbH6iP+Xvx2youbjrx8WH+RXkeqRRQ/hlDUKgfpx2HMh6NwRNyrJR8XkeG71oh0HTq36oeMKjYm+0GDeFYtqowuFygHRkvhriHB5EAc30qqaDPgW8ths=
	; 
Received: from unknown (HELO ShahramPC) (davarish@99.238.119.231 with login)
	by smtp115.rog.mail.re2.yahoo.com with SMTP; 3 Oct 2008 11:39:46 -0000
X-YMail-OSG: GiG9HlsVM1lXkjuDPPLsh1zFO.mU.D93yDZifh0_pthfyH3j3MxuLrIh5BaZPWGsGA--
X-Yahoo-Newman-Property: ymail-3
From: "Shahram Davari" <davarish@yahoo.com>
To: "'Sprecher, Nurit \(NSN - IL/Hod HaSharon\)'" <nurit.sprecher@nsn.com>,
	"'ext BUSI ITALO'" <Italo.Busi@alcatel-lucent.it>,
	"'Shahram Davari'" <davari@tpack.com>,
	"'Shane Amante'" <shane@castlepoint.net>
References: <48E4DE0F.9020704@castlepoint.net><92a2396384f1f54f92005abb3728728f@mail.cph.tpack.net>	<6FD21B53861BF44AA90A288402036AB40193FA34@FRVELSMBS21.ad2.ad.alcatel.com>
	<43284B5A95E36B4AB4A91EBA4E0FC31ED75EAD@DEMUEXC030.nsn-intra.net>
In-Reply-To: <43284B5A95E36B4AB4A91EBA4E0FC31ED75EAD@DEMUEXC030.nsn-intra.net>
Date: Fri, 3 Oct 2008 07:39:42 -0400
Message-ID: <00b501c9254c$bad67990$30836cb0$@com>
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AckkqLTHdNDdblepSIu2W52R3r7OPAAhRAtQAAGjQQAABetSsA==
Content-Language: en-ca
X-Mailman-Approved-At: Fri, 03 Oct 2008 06:19:21 -0700
Cc: l2vpn@ietf.org, mpls@ietf.org,
	'BOCCI Matthew' <Matthew.Bocci@alcatel-lucent.com>,
	ccamp@ietf.org, mpls-tp@ietf.org, pwe3@ietf.org
Subject: Re: [mpls] [PWE3] [mpls-tp] FW: Changes to PW
	ACH	ChannelType	allocationpolicy
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: davarish@yahoo.com
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mpls-bounces@ietf.org
Errors-To: mpls-bounces@ietf.org

Hi Nurit,

Good question. There are many reasons why a vendor may not want to
standardize its proprietary protocol. Including commercial benefits, product
differentiation, or simply trying a new unproven protocol for some time
before they are confident it works in various network situations.

In any case, I think your question is out of the scope here, since we are
clearly debating how to allocate code points for proprietary use. In other
words we have already accepted that people need proprietary extensions.

Regards,
Shahram

-----Original Message-----
From: pwe3-bounces@ietf.org [mailto:pwe3-bounces@ietf.org] On Behalf Of
Sprecher, Nurit (NSN - IL/Hod HaSharon)
Sent: October-03-08 4:46 AM
To: ext BUSI ITALO; Shahram Davari; Shane Amante
Cc: l2vpn@ietf.org; mpls@ietf.org; BOCCI Matthew; ccamp@ietf.org;
mpls-tp@ietf.org; pwe3@ietf.org
Subject: Re: [PWE3] [mpls-tp] FW: Changes to PW ACH ChannelType
allocationpolicy

" it encourages more innovation and differentiation by vendors". 
If there are some innovations (which is of course encouraged), why not
pushing it to be a standard behavior? 
I am pretty sure SPs will be happier to see it working in multi vendor
environment than as a proprietary solution that is supported by one
vendor only.  

-----Original Message-----
From: pwe3-bounces@ietf.org [mailto:pwe3-bounces@ietf.org] On Behalf Of
ext BUSI ITALO
Sent: Friday, October 03, 2008 11:11
To: Shahram Davari; Shane Amante
Cc: l2vpn@ietf.org; mpls@ietf.org; BOCCI Matthew; ccamp@ietf.org;
mpls-tp@ietf.org; pwe3@ietf.org
Subject: Re: [PWE3] [mpls-tp] FW: Changes to PW ACH ChannelType
allocationpolicy

See my comments in line marked with [ib] 

> -----Original Message-----
> From: Shahram Davari [mailto:davari@tpack.com] 
> Sent: Thursday, October 02, 2008 6:06 PM
> To: Shane Amante
> Cc: BUSI ITALO; Vishwas Manral; l2vpn@ietf.org; BOCCI 
> Matthew; mpls@ietf.org; ccamp@ietf.org; mpls-tp@ietf.org; 
> pwe3@ietf.org
> Subject: RE: [mpls-tp] [PWE3] FW: Changes to PW ACH Channel 
> Type allocationpolicy
> 
> Hi Shane,
> 
> Please see my response in-line. 
> 
> Best regards,
> Shahram
> 
> 
> -----Original Message-----
> From: Shane Amante [mailto:shane@castlepoint.net] 
> Sent: October-02-08 10:43 AM
> To: Shahram Davari
> Cc: BUSI ITALO; Vishwas Manral; l2vpn@ietf.org; BOCCI 
> Matthew; mpls@ietf.org; ccamp@ietf.org; mpls-tp@ietf.org; 
> pwe3@ietf.org
> Subject: Re: [mpls-tp] [PWE3] FW: Changes to PW ACH Channel 
> Type allocationpolicy
> 
> Shahram Davari wrote:
> > Hi,
> > 
> > I also prefer the method that Wishwas proposed. This has 
> many advantages:
> > 
> > 1) Allows vendors to not expose their proprietary 
> techniques to their competitors. 
> 
>  From the POV of an operator, this is actually a substantial 
> disadvantage.
> 
> [Shahram] OTOH it encourages more innovation and 
> differentiation by vendors.
> 

[ib] I fully agree with Shaharm. This is exactly the objective of the
requirement to allow vendor proprietary extensions.

> 
> > 2) reduces the load of reviewing by IETF and PWE3 
> 
> OTOH, the benefit of such reviews by the IETF and PWE3 is when 
> "commonality" among similar applications are discovered they can be 
> standardized, rather kept proprietary.
> 
> [Shahram] Not if the inventing vendor is not willing to do so.
> 
> 
> > 3) results a faster time to market, since no expert review 
> will be needed
> 
> True, to some extent.  But, IMHO, I would much rather see a 
> *slightly* 
> slower process involving a careful expert review and/or IETF 
> consensus 
> to make sure we're not: a) unnecessarily duplicating work; and, b) at 
> the same time, encouraging more standards-based approach.
> 
> 
> > 4) provides more codepoint space that the ACH channel type
> 
> This is false.  There is no shortage on ACH channel types today.
> [Shahram] You are correct. 16-bit is sufficient enough.
> 

[ib] I agree that the codepoint space is big enough and the codepoint
exhaustion is not a real issue.

However, with both option 1 and 2, we still have an open point to decide
how many codepoints we need to reserve for proprietary use and this is
not an easy task.

Option 3 has the advantage that we just need to allocate a single
codepoint.

> 
> > 5) only one VCCV ACH channel type needs to be configured in 
> each box for vendor specific filtering
>  >
> > The 2nd method has the first 3 advantages only, and the 
> first method has none of these advantages.
> 
> 
> Also, let's take a step back here.  Wasn't the whole point with the 
> joint ITU-T/IETF effort surrounding MPLS-TP to create an 
> environment in 
> which MPLS-TP could seamlessly interoperate within (existing) MPLS 
> environments?  I thought a fundamental part of that work is striving 
> towards creating a *standards-based* MPLS-TP data-plane, OAM, 
> signaling, 
> etc. mechanisms.  IMO, Vishwas' proposal and Matthew's 
> proposal #2 seems 
> to run contrary to that goal.
> 
> [Shahram] off course we should all encourage standards 
> methods. But we should provide a fast and reasonable 
> procedure for vendor specific protocols that don't affect 
> interoperability. I worry that in first method competitors 
> may vote down code point requests for commercial reasons.
> 

[ib] I agree. Standard actions is definitely the preferred approach to
enhance the technology and MUST be pursed as much as possible.
BTW this is why we are all spending huge efforts to progress standard
activities.
However there are cases where multi-vendor interoperability is not an
issue/requirement and fast time to market is a key requirement, where
standard action is not appropriate.

> -shane (speaking only for himself, not as co-chair)
> 
> 
> 
> 
_______________________________________________
pwe3 mailing list
pwe3@ietf.org
https://www.ietf.org/mailman/listinfo/pwe3
_______________________________________________
pwe3 mailing list
pwe3@ietf.org
https://www.ietf.org/mailman/listinfo/pwe3

_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls


From mpls-bounces@ietf.org  Fri Oct  3 06:46:12 2008
Return-Path: <mpls-bounces@ietf.org>
X-Original-To: mpls-archive@megatron.ietf.org
Delivered-To: ietfarch-mpls-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 3C4123A69DA;
	Fri,  3 Oct 2008 06:46:12 -0700 (PDT)
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 50F873A69DA;
	Fri,  3 Oct 2008 06:37:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 1Wk8QVf2Obk4; Fri,  3 Oct 2008 06:37:14 -0700 (PDT)
Received: from imr1.ericy.com (imr1.ericy.com [198.24.6.9])
	by core3.amsl.com (Postfix) with ESMTP id 827BA28C282;
	Fri,  3 Oct 2008 06:36:33 -0700 (PDT)
Received: from eusrcmw750.eamcs.ericsson.se (eusrcmw750.exu.ericsson.se
	[138.85.77.50])
	by imr1.ericy.com (8.13.1/8.13.1) with ESMTP id m93DbGVI027088;
	Fri, 3 Oct 2008 08:37:16 -0500
Received: from eusrcmw721.eamcs.ericsson.se ([138.85.77.21]) by
	eusrcmw750.eamcs.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 3 Oct 2008 08:36:47 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Fri, 3 Oct 2008 08:36:46 -0500
Message-ID: <941D5DCD8C42014FAF70FB7424686DCF03DFF8C0@eusrcmw721.eamcs.ericsson.se>
In-Reply-To: <48E5102B.3050307@cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [mpls] [PWE3] [mpls-tp] FW: Changes to PW ACH
	ChannelType	allocationpolicy
Thread-Index: AcklXAv556efa7W+QeuNmHjImswuWgAAGF1g
References: <16a42c48f46e6547a1c3ce65f8fee99a@mail.cph.tpack.net>
	<48E5102B.3050307@cisco.com>
From: "Eric Gray" <eric.gray@ericsson.com>
To: "Luca Martini" <lmartini@cisco.com>, "Shahram Davari" <davari@tpack.com>
X-OriginalArrivalTime: 03 Oct 2008 13:36:47.0580 (UTC)
	FILETIME=[154501C0:01C9255D]
X-Mailman-Approved-At: Fri, 03 Oct 2008 06:46:11 -0700
Cc: "Thomas D. Nadeau" <tom.nadeau@bt.com>, mpls@ietf.org,
	BOCCI Matthew <Matthew.Bocci@alcatel-lucent.com>, ccamp@ietf.org,
	l2vpn@ietf.org, pwe3@ietf.org,
	BUSI ITALO <Italo.Busi@alcatel-lucent.it>, mpls-tp@ietf.org
Subject: Re: [mpls] [PWE3] [mpls-tp] FW: Changes to PW ACH
	ChannelType	allocationpolicy
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mpls-bounces@ietf.org
Errors-To: mpls-bounces@ietf.org

Luca,

	The practical reality is that expert review gives the 
designated "expert" (or experts) the same level of control 
of assignment as IESG review gives ADs over RFC publication.
While it is possible to push something through against the
"wishes" of an expert (who does in fact have more than the
ability to "advise" the requesting individual/organization),
the process can be quite confrontational and tedious.

--
Eric Gray
Principal Engineer
Ericsson  

> -----Original Message-----
> From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On 
> Behalf Of Luca Martini
> Sent: Thursday, October 02, 2008 2:17 PM
> To: Shahram Davari
> Cc: Thomas D. Nadeau; mpls@ietf.org; BOCCI Matthew; 
> ccamp@ietf.org; l2vpn@ietf.org; pwe3@ietf.org; BUSI ITALO; 
> mpls-tp@ietf.org
> Subject: Re: [mpls] [PWE3] [mpls-tp] FW: Changes to PW ACH 
> ChannelType allocationpolicy
> 
> Shahram,
> the point of expert review is not to prevent vendor specific OAM 
> methods. It is to prevent duplication, and guide implementors in the 
> right direction.
> For example , if somebody needs a new PW type , for a very vendor 
> specific protocol , say Apollo DDS ( I was the last recorded user of 
> that ;-) ), but asks for an ACH type instead , the expert can 
> advise to 
> use a new pw type. In the end there is no enforcement method, so any 
> vendor can do anything they want. The only part we can do 
> here , is have 
> some sane documentation of the methods we put in the registry. ( 
> documentation could be as short a a line , or as long as a draft )
> 
> Luca
> 
> 
> Shahram Davari wrote:
> > No one asked for IETF rubber stamping. I asked for a 
> mechanism (code point assignment) that easily implement 
> vendor specific methods. I don't see any reason why IETF 
> should review and approve a vendor specific method. If IETF 
> doesn't want to see any vendor specific method, then it 
> doesn't need to allocate any code points. However, if IETF 
> wants to encourage vendor specific protocols then it must do 
> so in a way that makes it easy for vendors to use it.
> >
> > -Shahram
> >
> >
> > -----Original Message-----
> > From: Thomas D. Nadeau [mailto:tom.nadeau@bt.com] 
> > Sent: October-02-08 12:44 PM
> > To: Shahram Davari; Shane Amante
> > Cc: l2vpn@ietf.org; mpls@ietf.org; BOCCI Matthew; 
> ccamp@ietf.org; mpls-tp@ietf.org; Vishwas Manral; 
> pwe3@ietf.org; BUSI ITALO
> > Subject: Re: [mpls-tp] [PWE3] FW: Changes to PW ACH Channel 
> Type allocationpolicy
> >
> >
> >
> >     I agree with %100 of Shane's comments. One bit to add below:
> >
> >   
> >> Hi Shane,
> >>
> >> Please see my response in-line.
> >>
> >> Best regards,
> >> Shahram
> >>
> >>
> >> -----Original Message-----
> >> From: Shane Amante [mailto:shane@castlepoint.net]
> >> Sent: October-02-08 10:43 AM
> >> To: Shahram Davari
> >> Cc: BUSI ITALO; Vishwas Manral; l2vpn@ietf.org; BOCCI 
> Matthew; mpls@ietf.org;
> >> ccamp@ietf.org; mpls-tp@ietf.org; pwe3@ietf.org
> >> Subject: Re: [mpls-tp] [PWE3] FW: Changes to PW ACH Channel Type
> >> allocationpolicy
> >>
> >> Shahram Davari wrote:
> >>     
> >>> Hi,
> >>>
> >>> I also prefer the method that Wishwas proposed. This has 
> many advantages:
> >>>
> >>> 1) Allows vendors to not expose their proprietary 
> techniques to their
> >>> competitors.
> >>>       
> >>  From the POV of an operator, this is actually a 
> substantial disadvantage.
> >>
> >> [Shahram] OTOH it encourages more innovation and 
> differentiation by vendors.
> >>     
> >
> >     That is hogwash. Customers encourage vendors to 
> innovate not standards
> > bodies. Standards bodies help encourage and foster 
> interoperability of a
> > common specification. The latter is the important point 
> Shane is making (as
> > am I and others who are the customers in this equation). We 
> don't want to
> > encourage proprietary implementations for the sake of proprietary
> > implementations; we want to encourage them to ultimately 
> interoperate on a
> > common specification. However, if your goal as a vendor is to create
> > proprietary implementations you are free to do so, but you 
> do not need the
> > IETF unless you are looking for some sort of rubber stamp 
> of approval.
> >
> >     --Tom
> >
> >
> >   
> >   
> >>> 2) reduces the load of reviewing by IETF and PWE3
> >>>       
> >> OTOH, the benefit of such reviews by the IETF and PWE3 is when
> >> "commonality" among similar applications are discovered they can be
> >> standardized, rather kept proprietary.
> >>
> >> [Shahram] Not if the inventing vendor is not willing to do so.
> >>
> >>
> >>     
> >>> 3) results a faster time to market, since no expert 
> review will be needed
> >>>       
> >> True, to some extent.  But, IMHO, I would much rather see 
> a *slightly*
> >> slower process involving a careful expert review and/or 
> IETF consensus
> >> to make sure we're not: a) unnecessarily duplicating work; 
> and, b) at
> >> the same time, encouraging more standards-based approach.
> >>
> >>
> >>     
> >>> 4) provides more codepoint space that the ACH channel type
> >>>       
> >> This is false.  There is no shortage on ACH channel types today.
> >> [Shahram] You are correct. 16-bit is sufficient enough.
> >>
> >>
> >>     
> >>> 5) only one VCCV ACH channel type needs to be configured 
> in each box for
> >>> vendor specific filtering
> >>>
> >>> The 2nd method has the first 3 advantages only, and the 
> first method has none
> >>> of these advantages.
> >>>       
> >> Also, let's take a step back here.  Wasn't the whole point with the
> >> joint ITU-T/IETF effort surrounding MPLS-TP to create an 
> environment in
> >> which MPLS-TP could seamlessly interoperate within (existing) MPLS
> >> environments?  I thought a fundamental part of that work 
> is striving
> >> towards creating a *standards-based* MPLS-TP data-plane, 
> OAM, signaling,
> >> etc. mechanisms.  IMO, Vishwas' proposal and Matthew's 
> proposal #2 seems
> >> to run contrary to that goal.
> >>
> >> [Shahram] off course we should all encourage standards 
> methods. But we should
> >> provide a fast and reasonable procedure for vendor 
> specific protocols that
> >> don't affect interoperability. I worry that in first 
> method competitors may
> >> vote down code point requests for commercial reasons.
> >>
> >> -shane (speaking only for himself, not as co-chair)
> >>
> >>
> >>
> >>     
> >
> >
> >
> >
> > _______________________________________________
> > pwe3 mailing list
> > pwe3@ietf.org
> > https://www.ietf.org/mailman/listinfo/pwe3
> >   
> 
> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls
> 
_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls


From mpls-bounces@ietf.org  Fri Oct  3 07:53:07 2008
Return-Path: <mpls-bounces@ietf.org>
X-Original-To: mpls-archive@megatron.ietf.org
Delivered-To: ietfarch-mpls-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id DF81E3A6820;
	Fri,  3 Oct 2008 07:53:06 -0700 (PDT)
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id D880B3A6820;
	Fri,  3 Oct 2008 07:53:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.274
X-Spam-Level: 
X-Spam-Status: No, score=-106.274 tagged_above=-999 required=5
	tests=[AWL=0.325, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4,
	USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 27vhBdDKjTTQ; Fri,  3 Oct 2008 07:53:03 -0700 (PDT)
Received: from mail120.messagelabs.com (mail120.messagelabs.com
	[216.82.250.83])
	by core3.amsl.com (Postfix) with ESMTP id 6C7A33A6765;
	Fri,  3 Oct 2008 07:53:03 -0700 (PDT)
X-VirusChecked: Checked
X-Env-Sender: dbrungard@att.com
X-Msg-Ref: server-12.tower-120.messagelabs.com!1223045541!41660334!1
X-StarScan-Version: 5.5.12.14.2; banners=-,-,-
X-Originating-IP: [144.160.20.54]
Received: (qmail 20948 invoked from network); 3 Oct 2008 14:52:22 -0000
Received: from sbcsmtp7.sbc.com (HELO mlpi135.enaf.sfdc.sbc.com)
	(144.160.20.54)
	by server-12.tower-120.messagelabs.com with AES256-SHA encrypted SMTP;
	3 Oct 2008 14:52:22 -0000
Received: from enaf.sfdc.sbc.com (localhost.localdomain [127.0.0.1])
	by mlpi135.enaf.sfdc.sbc.com (8.14.0/8.14.0) with ESMTP id
	m93EqLd7012603; Fri, 3 Oct 2008 10:52:21 -0400
Received: from gaalpa1msgusr7e.ugd.att.com (gaalpa1msgusr7e.ugd.att.com
	[135.53.26.19])
	by mlpi135.enaf.sfdc.sbc.com (8.14.0/8.14.0) with ESMTP id
	m93EqGVS012542; Fri, 3 Oct 2008 10:52:16 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Fri, 3 Oct 2008 10:52:15 -0400
Message-ID: <D6CB948F7AFD6F4881D4B4F80C8509AA0124B2E4@gaalpa1msgusr7e.ugd.att.com>
In-Reply-To: <6FD21B53861BF44AA90A288402036AB40193F9F1@FRVELSMBS21.ad2.ad.alcatel.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [mpls-tp] [mpls] [PWE3] Changes to PW ACH Channel
	Typeallocationpolicy
Thread-Index: AckkQ71IH8+xzlBPTXyZ2QuPfVC+nQAT4P0wAAFwrKAAI6eCgAAPAbNQ
References: <0458D2EE0C36744BABB36BE37805C29A029C6251@FRVELSMBS11.ad2.ad.alcatel.com><639AAB99-9B29-40B1-A57D-C3476D87696C@castlepoint.net><D6CB948F7AFD6F4881D4B4F80C8509AA01208045@gaalpa1msgusr7e.ugd.att.com>
	<7DBAFEC6A76F3E42817DF1EBE64CB02605E3E1D2@ftrdmel2>
	<6FD21B53861BF44AA90A288402036AB40193F9F1@FRVELSMBS21.ad2.ad.alcatel.com>
From: "BRUNGARD, DEBORAH A, ATTLABS" <dbrungard@att.com>
To: "BUSI ITALO" <Italo.Busi@alcatel-lucent.it>
Cc: l2vpn@ietf.org, mpls@ietf.org, ccamp@ietf.org, pwe3@ietf.org,
	mpls-tp@ietf.org
Subject: Re: [mpls] [mpls-tp] [PWE3] Changes to PW ACH Channel
	Typeallocationpolicy
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mpls-bounces@ietf.org
Errors-To: mpls-bounces@ietf.org

Hi Italo,

It is much more than a codepoint and ensuring the nodes are provisioned
correctly - which is in itself difficult - especially in large networks.
Here's just a partial list of additional concerns from an operator:
- proprietary protocols perpetuate the use of vendor islands - good for
a vendor/bad for an operator;-(
- each protocol, proprietary or not, for an operator requires testing of
the protocol itself, not just if it works as it should, but also
development and testing of failure scenarios, and the negotiation with
the vendor for fixes. And if it's proprietary, an operator is on their
own for determining bugs, determining the correct fix, testing the fix,
etc, etc.
- OS development - this is probably the biggest hit on time for
deployment and most costly (and it's not just for deployment, it
continues for the lifetime).

Which is why we have standards. I'm sure the others can add many more
(still on my first coffee here) and take a look back over Shane's mails.
Deborah

-----Original Message-----
From: BUSI ITALO [mailto:Italo.Busi@alcatel-lucent.it] 
Sent: Friday, October 03, 2008 3:39 AM
To: julien.meuric@orange-ftgroup.com; BRUNGARD, DEBORAH A, ATTLABS;
shane@castlepoint.net; BOCCI Matthew
Cc: l2vpn@ietf.org; mpls@ietf.org; ccamp@ietf.org; pwe3@ietf.org;
mpls-tp@ietf.org
Subject: RE: [mpls-tp] [mpls] [PWE3] Changes to PW ACH Channel
Typeallocationpolicy

Julien, Tom, Shane and Deborah,

it looks like you have a common position regarding interoperability
issues of proprietary protocols.

I can understand your issues with proprietary protocols because, by
definition, they do not interoperate.

However please note that all proprietary protocols by default must be
disabled and enabled if and only if it is known that all the nodes that
need to process the proprietary packets are capable to support the
proprietary protocol. As such you can simply never enable any
proprietary protocol.

I fail to understand how the allocation policy of ACH codepoints for
proprietary use can change the management issues from your point of
view.

Italo

> -----Original Message-----
> From: l2vpn-bounces@ietf.org [mailto:l2vpn-bounces@ietf.org] 
> On Behalf Of julien.meuric@orange-ftgroup.com
> Sent: Thursday, October 02, 2008 5:18 PM
> To: dbrungard@att.com; shane@castlepoint.net; BOCCI Matthew
> Cc: l2vpn@ietf.org; mpls@ietf.org; ccamp@ietf.org; 
> pwe3@ietf.org; mpls-tp@ietf.org
> Subject: RE: [mpls-tp] [mpls] [PWE3] Changes to PW ACH 
> Channel Typeallocationpolicy
> 
> Hi.
> 
> I must agree with Deborah and Shane.
> 
> Option #3 hides the complexity behind a (useless) hierarchy and is
> clearly not desired. Option #2 would create an explicit non standard
> range and is not what we expect from the IETF.
> As a result, since changing the former process seems already 
> committed,
> option #1 remains the better compromise.
> 
> Regards,
> 
> Julien
> 
> 
> -----Original Message-----
> From: mpls-tp-bounces@ietf.org [mailto:mpls-tp-bounces@ietf.org] On
> Behalf Of BRUNGARD, DEBORAH A, ATTLABS
> 
> Agree- and with the strong wording that option #1 is not for
> SDOs/Forums. Option 2 (or the 3rd option being discussed), 
> may be viewed
> as no bottleneck for vendors on development of proprietary 
> options, but
> for operators, it will be an interoperability nightmare.
> Deborah  
> 
> -----Original Message-----
> From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On 
> Behalf Of
> Shane Amante
> 
> Matthew,
> 
> Speaking as an operator, (L2VPN WG co-chair hat off), I would also  
> prefer the existing mechanism that's already in place: expert review  
> and IETF consensus.  After all, there are significant benefits to  
> standards-based OAM and signaling protocols.  On the other 
> hand, some  
> people may still have a legitimate need to do uncommon things that  
> aren't considered mainstream.  In that case, I would rather see a  
> (small) subset of codepoints allocated for expert review with 
> no IETF  
> consensus (Option #1 below).
> 
> -shane
> 
> 
> On Sep 30, 2008, at 10:23 AM, BOCCI Matthew wrote:
> > The PWE3 chairs would like feedback on proposed changes to the
> > allocation policy for the PW ACH codepoint registry. Please see the
> > email below, and provide any feedback copying the PWE3 list.
> >
> > Best regards
> >
> > Matthew
> >
> > -----Original Message-----
> > From: pwe3-bounces@ietf.org [mailto:pwe3-bounces@ietf.org] 
> On Behalf  
> > Of
> > BOCCI Matthew
> >
> > The current IANA allocation policy for the PW associated 
> channel type
> > registry is by IETF consensus. This policy was chosen in RFC 4385  
> > based
> > on WG consensus that since the associated channel exists in the data
> > path, and VCCV packets are typically processed by the control  
> > processor
> > on many PEs, it was prudent for the IETF to maintain strict 
> control  
> > over
> > what types of channels were allocated and to ensure that 
> they complied
> > to the PWE3 architecture.
> >
> > However, a need has been identified to provide a more flexible  
> > approach
> > to allocating code points for VCCV channel types. This has partly  
> > arisen
> > from the MPLS-TP work, where MPLS would be deployed in a transport
> > network and where a much wider range of applications for the PW
> > associated channel is envisioned, and partialy from a 
> desire to extend
> > the OAM capabilities for regular MPLS. We can support MPLS-TP and
> > general MPLS apps with the current policy which requires standards
> > action.
> >
> > However we are receiving requests to allow proprietary OAM and  
> > signaling
> > protocols to be used in transport applications, and need to 
> decide on
> > the best way forward. We considered providing extension mechanisms
> > within the standards track protocols, but believe that the standards
> > track protocols would be much cleaner if the proprietary 
> protocols ran
> > on their own ACH code points.
> >
> > Note that we are talking about vendor protocols here. Other 
> SDOs would
> > be required to publish an RFC and would only be allocated an ACH  
> > through
> > Standards Action.
> >
> > There are two ways to address the requests for proprietary 
> protocol  
> > ACH
> > code points:
> >
> > 1) Allow a range of the associated channel type registry to be  
> > allocated
> > through expert review. Guidelines would be provided for the expert
> > reviewer to guide them in assessing the request, which 
> would have to  
> > be
> > made in the form of an internet draft, while making sure that the
> > request is dealt with in a timely and fair manner. This policy would
> > include hurdles with regard to security, congestion etc 
> that would be
> > derived from those specified in the VCCV design.
> >
> > 2) Allow a range of the associated channel type registry to be  
> > allocated
> > on a first-come-first-served basis. This does not provide 
> the level of
> > control that expert review provides, but this is balanced to some  
> > degree
> > by the fact that the VCCV channel type is indicated in the 
> data path,
> > and so a PE can choose to discard or rate limit VCCV packets on an
> > unrecognised associated channel.
> >
> > Any change to the ACH allocation policy would be outlined 
> in the GE- 
> > ACH
> > draft, which would update RFC 4385.
> >
> > We would appreciate feedback on the list as to which approach the WG
> > prefers.
> >
> > Regards,
> >
> > Stewart and Matthew
> >
> > _______________________________________________
> > pwe3 mailing list
> > pwe3@ietf.org
> > https://www.ietf.org/mailman/listinfo/pwe3
> 
> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls
> _______________________________________________
> mpls-tp mailing list
> mpls-tp@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls-tp
> 
_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls


From mpls-bounces@ietf.org  Fri Oct  3 08:04:05 2008
Return-Path: <mpls-bounces@ietf.org>
X-Original-To: mpls-archive@megatron.ietf.org
Delivered-To: ietfarch-mpls-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id EEDCA28C272;
	Fri,  3 Oct 2008 08:04:04 -0700 (PDT)
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 0B67E3A69B5;
	Fri,  3 Oct 2008 08:04:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.146
X-Spam-Level: 
X-Spam-Status: No, score=-1.146 tagged_above=-999 required=5 tests=[AWL=0.386, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, RCVD_NUMERIC_HELO=2.067]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id ohzMqohH6me2; Fri,  3 Oct 2008 08:04:01 -0700 (PDT)
Received: from smtp2.smtp.bt.com (smtp2.smtp.bt.com [217.32.164.150])
	by core3.amsl.com (Postfix) with ESMTP id 651BB3A68C6;
	Fri,  3 Oct 2008 08:04:01 -0700 (PDT)
Received: from E03MVZ2-UKDY.domain1.systemhost.net ([193.113.30.65]) by
	smtp2.smtp.bt.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 3 Oct 2008 16:02:40 +0100
Received: from 217.32.164.172 ([217.32.164.172]) by
	E03MVZ2-UKDY.domain1.systemhost.net ([193.113.30.120]) via
	Exchange Front-End Server mail.bt.com ([193.113.197.26]) with
	Microsoft Exchange Server HTTP-DAV ; Fri,  3 Oct 2008 15:02:39 +0000
User-Agent: Microsoft-Entourage/12.12.0.080729
Date: Fri, 03 Oct 2008 11:02:39 -0400
From: "Thomas D. Nadeau" <tom.nadeau@bt.com>
To: "BRUNGARD, DEBORAH A, ATTLABS" <dbrungard@att.com>,
	BUSI ITALO <Italo.Busi@alcatel-lucent.it>
Message-ID: <C50BAC4F.E2DD%tom.nadeau@bt.com>
Thread-Topic: [mpls-tp] [mpls] [PWE3] Changes to PW ACH Channel
	Typeallocationpolicy
Thread-Index: AckkQ71IH8+xzlBPTXyZ2QuPfVC+nQAT4P0wAAFwrKAAI6eCgAAPAbNQAAFawJc=
In-Reply-To: <D6CB948F7AFD6F4881D4B4F80C8509AA0124B2E4@gaalpa1msgusr7e.ugd.att.com>
Mime-version: 1.0
X-OriginalArrivalTime: 03 Oct 2008 15:02:40.0959 (UTC)
	FILETIME=[14EC3CF0:01C92569]
Cc: l2vpn@ietf.org, mpls@ietf.org, ccamp@ietf.org, pwe3@ietf.org,
	mpls-tp@ietf.org
Subject: Re: [mpls] [mpls-tp] [PWE3] Changes to PW ACH Channel
 Typeallocationpolicy
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mpls-bounces@ietf.org
Errors-To: mpls-bounces@ietf.org




On 10/3/08 10:52 AM, "BRUNGARD, DEBORAH A, ATTLABS" <dbrungard@att.com>
wrote:

> Hi Italo,
> 
> It is much more than a codepoint and ensuring the nodes are provisioned
> correctly - which is in itself difficult - especially in large networks.
> Here's just a partial list of additional concerns from an operator:
> - proprietary protocols perpetuate the use of vendor islands - good for
> a vendor/bad for an operator;-(
> - each protocol, proprietary or not, for an operator requires testing of
> the protocol itself, not just if it works as it should, but also
> development and testing of failure scenarios, and the negotiation with
> the vendor for fixes. And if it's proprietary, an operator is on their
> own for determining bugs, determining the correct fix, testing the fix,
> etc, etc.
> - OS development - this is probably the biggest hit on time for
> deployment and most costly (and it's not just for deployment, it
> continues for the lifetime).
> 
> Which is why we have standards. I'm sure the others can add many more
> (still on my first coffee here) and take a look back over Shane's mails.

    Nothing to add here; hits the nail right on the head.

    --Tom


> Deborah
> 
> -----Original Message-----
> From: BUSI ITALO [mailto:Italo.Busi@alcatel-lucent.it]
> Sent: Friday, October 03, 2008 3:39 AM
> To: julien.meuric@orange-ftgroup.com; BRUNGARD, DEBORAH A, ATTLABS;
> shane@castlepoint.net; BOCCI Matthew
> Cc: l2vpn@ietf.org; mpls@ietf.org; ccamp@ietf.org; pwe3@ietf.org;
> mpls-tp@ietf.org
> Subject: RE: [mpls-tp] [mpls] [PWE3] Changes to PW ACH Channel
> Typeallocationpolicy
> 
> Julien, Tom, Shane and Deborah,
> 
> it looks like you have a common position regarding interoperability
> issues of proprietary protocols.
> 
> I can understand your issues with proprietary protocols because, by
> definition, they do not interoperate.
> 
> However please note that all proprietary protocols by default must be
> disabled and enabled if and only if it is known that all the nodes that
> need to process the proprietary packets are capable to support the
> proprietary protocol. As such you can simply never enable any
> proprietary protocol.
> 
> I fail to understand how the allocation policy of ACH codepoints for
> proprietary use can change the management issues from your point of
> view.
> 
> Italo
> 
>> -----Original Message-----
>> From: l2vpn-bounces@ietf.org [mailto:l2vpn-bounces@ietf.org]
>> On Behalf Of julien.meuric@orange-ftgroup.com
>> Sent: Thursday, October 02, 2008 5:18 PM
>> To: dbrungard@att.com; shane@castlepoint.net; BOCCI Matthew
>> Cc: l2vpn@ietf.org; mpls@ietf.org; ccamp@ietf.org;
>> pwe3@ietf.org; mpls-tp@ietf.org
>> Subject: RE: [mpls-tp] [mpls] [PWE3] Changes to PW ACH
>> Channel Typeallocationpolicy
>> 
>> Hi.
>> 
>> I must agree with Deborah and Shane.
>> 
>> Option #3 hides the complexity behind a (useless) hierarchy and is
>> clearly not desired. Option #2 would create an explicit non standard
>> range and is not what we expect from the IETF.
>> As a result, since changing the former process seems already
>> committed,
>> option #1 remains the better compromise.
>> 
>> Regards,
>> 
>> Julien
>> 
>> 
>> -----Original Message-----
>> From: mpls-tp-bounces@ietf.org [mailto:mpls-tp-bounces@ietf.org] On
>> Behalf Of BRUNGARD, DEBORAH A, ATTLABS
>> 
>> Agree- and with the strong wording that option #1 is not for
>> SDOs/Forums. Option 2 (or the 3rd option being discussed),
>> may be viewed
>> as no bottleneck for vendors on development of proprietary
>> options, but
>> for operators, it will be an interoperability nightmare.
>> Deborah  
>> 
>> -----Original Message-----
>> From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On
>> Behalf Of
>> Shane Amante
>> 
>> Matthew,
>> 
>> Speaking as an operator, (L2VPN WG co-chair hat off), I would also
>> prefer the existing mechanism that's already in place: expert review
>> and IETF consensus.  After all, there are significant benefits to
>> standards-based OAM and signaling protocols.  On the other
>> hand, some  
>> people may still have a legitimate need to do uncommon things that
>> aren't considered mainstream.  In that case, I would rather see a
>> (small) subset of codepoints allocated for expert review with
>> no IETF  
>> consensus (Option #1 below).
>> 
>> -shane
>> 
>> 
>> On Sep 30, 2008, at 10:23 AM, BOCCI Matthew wrote:
>>> The PWE3 chairs would like feedback on proposed changes to the
>>> allocation policy for the PW ACH codepoint registry. Please see the
>>> email below, and provide any feedback copying the PWE3 list.
>>> 
>>> Best regards
>>> 
>>> Matthew
>>> 
>>> -----Original Message-----
>>> From: pwe3-bounces@ietf.org [mailto:pwe3-bounces@ietf.org]
>> On Behalf  
>>> Of
>>> BOCCI Matthew
>>> 
>>> The current IANA allocation policy for the PW associated
>> channel type
>>> registry is by IETF consensus. This policy was chosen in RFC 4385
>>> based
>>> on WG consensus that since the associated channel exists in the data
>>> path, and VCCV packets are typically processed by the control
>>> processor
>>> on many PEs, it was prudent for the IETF to maintain strict
>> control  
>>> over
>>> what types of channels were allocated and to ensure that
>> they complied
>>> to the PWE3 architecture.
>>> 
>>> However, a need has been identified to provide a more flexible
>>> approach
>>> to allocating code points for VCCV channel types. This has partly
>>> arisen
>>> from the MPLS-TP work, where MPLS would be deployed in a transport
>>> network and where a much wider range of applications for the PW
>>> associated channel is envisioned, and partialy from a
>> desire to extend
>>> the OAM capabilities for regular MPLS. We can support MPLS-TP and
>>> general MPLS apps with the current policy which requires standards
>>> action.
>>> 
>>> However we are receiving requests to allow proprietary OAM and
>>> signaling
>>> protocols to be used in transport applications, and need to
>> decide on
>>> the best way forward. We considered providing extension mechanisms
>>> within the standards track protocols, but believe that the standards
>>> track protocols would be much cleaner if the proprietary
>> protocols ran
>>> on their own ACH code points.
>>> 
>>> Note that we are talking about vendor protocols here. Other
>> SDOs would
>>> be required to publish an RFC and would only be allocated an ACH
>>> through
>>> Standards Action.
>>> 
>>> There are two ways to address the requests for proprietary
>> protocol  
>>> ACH
>>> code points:
>>> 
>>> 1) Allow a range of the associated channel type registry to be
>>> allocated
>>> through expert review. Guidelines would be provided for the expert
>>> reviewer to guide them in assessing the request, which
>> would have to  
>>> be
>>> made in the form of an internet draft, while making sure that the
>>> request is dealt with in a timely and fair manner. This policy would
>>> include hurdles with regard to security, congestion etc
>> that would be
>>> derived from those specified in the VCCV design.
>>> 
>>> 2) Allow a range of the associated channel type registry to be
>>> allocated
>>> on a first-come-first-served basis. This does not provide
>> the level of
>>> control that expert review provides, but this is balanced to some
>>> degree
>>> by the fact that the VCCV channel type is indicated in the
>> data path,
>>> and so a PE can choose to discard or rate limit VCCV packets on an
>>> unrecognised associated channel.
>>> 
>>> Any change to the ACH allocation policy would be outlined
>> in the GE- 
>>> ACH
>>> draft, which would update RFC 4385.
>>> 
>>> We would appreciate feedback on the list as to which approach the WG
>>> prefers.
>>> 
>>> Regards,
>>> 
>>> Stewart and Matthew
>>> 
>>> _______________________________________________
>>> pwe3 mailing list
>>> pwe3@ietf.org
>>> https://www.ietf.org/mailman/listinfo/pwe3
>> 
>> _______________________________________________
>> mpls mailing list
>> mpls@ietf.org
>> https://www.ietf.org/mailman/listinfo/mpls
>> _______________________________________________
>> mpls-tp mailing list
>> mpls-tp@ietf.org
>> https://www.ietf.org/mailman/listinfo/mpls-tp
>> 
> _______________________________________________
> mpls-tp mailing list
> mpls-tp@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls-tp

_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls


From mpls-bounces@ietf.org  Fri Oct  3 08:25:30 2008
Return-Path: <mpls-bounces@ietf.org>
X-Original-To: mpls-archive@megatron.ietf.org
Delivered-To: ietfarch-mpls-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id DFFE528C2A8;
	Fri,  3 Oct 2008 08:25:29 -0700 (PDT)
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 8A1A13A6A86;
	Fri,  3 Oct 2008 08:25:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, MISSING_MIMEOLE=0.001]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id F-EWdTtyfNi8; Fri,  3 Oct 2008 08:25:08 -0700 (PDT)
Received: from tpack.net (ip18.tpack.net [213.173.228.18])
	by core3.amsl.com (Postfix) with ESMTP id BACB13A6974;
	Fri,  3 Oct 2008 08:25:05 -0700 (PDT)
Received: from [192.168.111.1] (account shd@tpack.net)
	by tpack.net (CommuniGate Pro IMAP 5.1.12)
	with XMIT id 819237; Fri, 03 Oct 2008 17:25:32 +0200
Date: Fri, 03 Oct 2008 11:23:34 -0400
Organization: Tpack A/S
Message-Id: <6cfe3b6383dfa347ab739d67002d4ca9@mail.cph.tpack.net>
In-Reply-To: <D6CB948F7AFD6F4881D4B4F80C8509AA0124B2E4@gaalpa1msgusr7e.ugd.att.com>
MIME-Version: 1.0
Thread-Topic: [PWE3] [mpls-tp] [mpls] Changes to PW ACH Channel
	Typeallocationpolicy
Priority: Normal
Importance: normal
X-MSMail-Priority: normal
X-Priority: 3
Sensitivity: Normal
Thread-Index: AckkQ71IH8+xzlBPTXyZ2QuPfVC+nQAT4P0wAAFwrKAAI6eCgAAPAbNQAAHk2GA=
From: "Shahram Davari" <davari@tpack.com>
To: "BRUNGARD, DEBORAH A, ATTLABS" <dbrungard@att.com>, 
	"BUSI ITALO" <Italo.Busi@alcatel-lucent.it>
X-MAPI-LastModified: Fri, 03 Oct 2008 11:23:34 -0400
X-Mailer: CommuniGate Pro MAPI Connector 1.2.9/1.2.12
Cc: "l2vpn@ietf.org" <l2vpn@ietf.org>, "mpls@ietf.org" <mpls@ietf.org>,
	"ccamp@ietf.org" <ccamp@ietf.org>, "pwe3@ietf.org" <pwe3@ietf.org>,
	"mpls-tp@ietf.org" <mpls-tp@ietf.org>
Subject: Re: [mpls] [PWE3] [mpls-tp] Changes to PW ACH Channel
	Typeallocationpolicy
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mpls-bounces@ietf.org
Errors-To: mpls-bounces@ietf.org

Hi Deborah,

Your concerns are valid, but irrelevant to the discussion at hand. I think it is understood that IETF wants to allow Proprietary protocols and the issue is how to allocate the code points. So there debating whether proprietary protocols are good or bad is not going to make any difference here.  

But just to give you my opinion, lots of great innovations start as proprietary and eventually if they are good they would probably find their way to standard. Juts take a look at Cisco Tag Switching. It started as proprietary but later was standardized as MPLS.

Best regards,
Shahram


-----Original Message-----
From: pwe3-bounces@ietf.org [mailto:pwe3-bounces@ietf.org] On Behalf Of BRUNGARD, DEBORAH A, ATTLABS
Sent: October-03-08 10:52 AM
To: BUSI ITALO
Cc: l2vpn@ietf.org; mpls@ietf.org; ccamp@ietf.org; pwe3@ietf.org; mpls-tp@ietf.org
Subject: Re: [PWE3] [mpls-tp] [mpls] Changes to PW ACH Channel Typeallocationpolicy

Hi Italo,

It is much more than a codepoint and ensuring the nodes are provisioned
correctly - which is in itself difficult - especially in large networks.
Here's just a partial list of additional concerns from an operator:
- proprietary protocols perpetuate the use of vendor islands - good for
a vendor/bad for an operator;-(
- each protocol, proprietary or not, for an operator requires testing of
the protocol itself, not just if it works as it should, but also
development and testing of failure scenarios, and the negotiation with
the vendor for fixes. And if it's proprietary, an operator is on their
own for determining bugs, determining the correct fix, testing the fix,
etc, etc.
- OS development - this is probably the biggest hit on time for
deployment and most costly (and it's not just for deployment, it
continues for the lifetime).

Which is why we have standards. I'm sure the others can add many more
(still on my first coffee here) and take a look back over Shane's mails.
Deborah

-----Original Message-----
From: BUSI ITALO [mailto:Italo.Busi@alcatel-lucent.it] 
Sent: Friday, October 03, 2008 3:39 AM
To: julien.meuric@orange-ftgroup.com; BRUNGARD, DEBORAH A, ATTLABS;
shane@castlepoint.net; BOCCI Matthew
Cc: l2vpn@ietf.org; mpls@ietf.org; ccamp@ietf.org; pwe3@ietf.org;
mpls-tp@ietf.org
Subject: RE: [mpls-tp] [mpls] [PWE3] Changes to PW ACH Channel
Typeallocationpolicy

Julien, Tom, Shane and Deborah,

it looks like you have a common position regarding interoperability
issues of proprietary protocols.

I can understand your issues with proprietary protocols because, by
definition, they do not interoperate.

However please note that all proprietary protocols by default must be
disabled and enabled if and only if it is known that all the nodes that
need to process the proprietary packets are capable to support the
proprietary protocol. As such you can simply never enable any
proprietary protocol.

I fail to understand how the allocation policy of ACH codepoints for
proprietary use can change the management issues from your point of
view.

Italo

> -----Original Message-----
> From: l2vpn-bounces@ietf.org [mailto:l2vpn-bounces@ietf.org] 
> On Behalf Of julien.meuric@orange-ftgroup.com
> Sent: Thursday, October 02, 2008 5:18 PM
> To: dbrungard@att.com; shane@castlepoint.net; BOCCI Matthew
> Cc: l2vpn@ietf.org; mpls@ietf.org; ccamp@ietf.org; 
> pwe3@ietf.org; mpls-tp@ietf.org
> Subject: RE: [mpls-tp] [mpls] [PWE3] Changes to PW ACH 
> Channel Typeallocationpolicy
> 
> Hi.
> 
> I must agree with Deborah and Shane.
> 
> Option #3 hides the complexity behind a (useless) hierarchy and is
> clearly not desired. Option #2 would create an explicit non standard
> range and is not what we expect from the IETF.
> As a result, since changing the former process seems already 
> committed,
> option #1 remains the better compromise.
> 
> Regards,
> 
> Julien
> 
> 
> -----Original Message-----
> From: mpls-tp-bounces@ietf.org [mailto:mpls-tp-bounces@ietf.org] On
> Behalf Of BRUNGARD, DEBORAH A, ATTLABS
> 
> Agree- and with the strong wording that option #1 is not for
> SDOs/Forums. Option 2 (or the 3rd option being discussed), 
> may be viewed
> as no bottleneck for vendors on development of proprietary 
> options, but
> for operators, it will be an interoperability nightmare.
> Deborah  
> 
> -----Original Message-----
> From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On 
> Behalf Of
> Shane Amante
> 
> Matthew,
> 
> Speaking as an operator, (L2VPN WG co-chair hat off), I would also  
> prefer the existing mechanism that's already in place: expert review  
> and IETF consensus.  After all, there are significant benefits to  
> standards-based OAM and signaling protocols.  On the other 
> hand, some  
> people may still have a legitimate need to do uncommon things that  
> aren't considered mainstream.  In that case, I would rather see a  
> (small) subset of codepoints allocated for expert review with 
> no IETF  
> consensus (Option #1 below).
> 
> -shane
> 
> 
> On Sep 30, 2008, at 10:23 AM, BOCCI Matthew wrote:
> > The PWE3 chairs would like feedback on proposed changes to the
> > allocation policy for the PW ACH codepoint registry. Please see the
> > email below, and provide any feedback copying the PWE3 list.
> >
> > Best regards
> >
> > Matthew
> >
> > -----Original Message-----
> > From: pwe3-bounces@ietf.org [mailto:pwe3-bounces@ietf.org] 
> On Behalf  
> > Of
> > BOCCI Matthew
> >
> > The current IANA allocation policy for the PW associated 
> channel type
> > registry is by IETF consensus. This policy was chosen in RFC 4385  
> > based
> > on WG consensus that since the associated channel exists in the data
> > path, and VCCV packets are typically processed by the control  
> > processor
> > on many PEs, it was prudent for the IETF to maintain strict 
> control  
> > over
> > what types of channels were allocated and to ensure that 
> they complied
> > to the PWE3 architecture.
> >
> > However, a need has been identified to provide a more flexible  
> > approach
> > to allocating code points for VCCV channel types. This has partly  
> > arisen
> > from the MPLS-TP work, where MPLS would be deployed in a transport
> > network and where a much wider range of applications for the PW
> > associated channel is envisioned, and partialy from a 
> desire to extend
> > the OAM capabilities for regular MPLS. We can support MPLS-TP and
> > general MPLS apps with the current policy which requires standards
> > action.
> >
> > However we are receiving requests to allow proprietary OAM and  
> > signaling
> > protocols to be used in transport applications, and need to 
> decide on
> > the best way forward. We considered providing extension mechanisms
> > within the standards track protocols, but believe that the standards
> > track protocols would be much cleaner if the proprietary 
> protocols ran
> > on their own ACH code points.
> >
> > Note that we are talking about vendor protocols here. Other 
> SDOs would
> > be required to publish an RFC and would only be allocated an ACH  
> > through
> > Standards Action.
> >
> > There are two ways to address the requests for proprietary 
> protocol  
> > ACH
> > code points:
> >
> > 1) Allow a range of the associated channel type registry to be  
> > allocated
> > through expert review. Guidelines would be provided for the expert
> > reviewer to guide them in assessing the request, which 
> would have to  
> > be
> > made in the form of an internet draft, while making sure that the
> > request is dealt with in a timely and fair manner. This policy would
> > include hurdles with regard to security, congestion etc 
> that would be
> > derived from those specified in the VCCV design.
> >
> > 2) Allow a range of the associated channel type registry to be  
> > allocated
> > on a first-come-first-served basis. This does not provide 
> the level of
> > control that expert review provides, but this is balanced to some  
> > degree
> > by the fact that the VCCV channel type is indicated in the 
> data path,
> > and so a PE can choose to discard or rate limit VCCV packets on an
> > unrecognised associated channel.
> >
> > Any change to the ACH allocation policy would be outlined 
> in the GE- 
> > ACH
> > draft, which would update RFC 4385.
> >
> > We would appreciate feedback on the list as to which approach the WG
> > prefers.
> >
> > Regards,
> >
> > Stewart and Matthew
> >
> > _______________________________________________
> > pwe3 mailing list
> > pwe3@ietf.org
> > https://www.ietf.org/mailman/listinfo/pwe3
> 
> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls
> _______________________________________________
> mpls-tp mailing list
> mpls-tp@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls-tp
> 
_______________________________________________
pwe3 mailing list
pwe3@ietf.org
https://www.ietf.org/mailman/listinfo/pwe3



_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls


From mpls-bounces@ietf.org  Fri Oct  3 08:33:19 2008
Return-Path: <mpls-bounces@ietf.org>
X-Original-To: mpls-archive@megatron.ietf.org
Delivered-To: ietfarch-mpls-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id A547328C2B0;
	Fri,  3 Oct 2008 08:33:19 -0700 (PDT)
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 8899228C21D;
	Fri,  3 Oct 2008 07:53:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id FPrrr+GYBWv2; Fri,  3 Oct 2008 07:53:44 -0700 (PDT)
Received: from napoleon.monoski.com (black.monoski.com [63.227.123.238])
	by core3.amsl.com (Postfix) with ESMTP id 1024428C146;
	Fri,  3 Oct 2008 07:53:43 -0700 (PDT)
Received: from confusion.monoski.com (confusion.monoski.com [209.245.27.2])
	(authenticated bits=0)
	by napoleon.monoski.com (8.13.8/8.13.8) with ESMTP id m93ErTLT027700
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Fri, 3 Oct 2008 08:53:29 -0600 (MDT)
Message-ID: <48E631E9.8090607@cisco.com>
Date: Fri, 03 Oct 2008 08:53:29 -0600
From: Luca Martini <lmartini@cisco.com>
User-Agent: Thunderbird 2.0.0.12 (X11/20080213)
MIME-Version: 1.0
To: Eric Gray <eric.gray@ericsson.com>
References: <16a42c48f46e6547a1c3ce65f8fee99a@mail.cph.tpack.net>
	<48E5102B.3050307@cisco.com>
	<941D5DCD8C42014FAF70FB7424686DCF03DFF8C0@eusrcmw721.eamcs.ericsson.se>
In-Reply-To: <941D5DCD8C42014FAF70FB7424686DCF03DFF8C0@eusrcmw721.eamcs.ericsson.se>
X-Scanned-By: MIMEDefang 2.63 on 209.245.27.1
X-Mailman-Approved-At: Fri, 03 Oct 2008 08:33:18 -0700
Cc: "Thomas D. Nadeau" <tom.nadeau@bt.com>, mpls@ietf.org,
	BOCCI Matthew <Matthew.Bocci@alcatel-lucent.com>, ccamp@ietf.org,
	l2vpn@ietf.org, pwe3@ietf.org, Shahram Davari <davari@tpack.com>,
	BUSI ITALO <Italo.Busi@alcatel-lucent.it>, mpls-tp@ietf.org
Subject: Re: [mpls] [PWE3] [mpls-tp] FW: Changes to PW ACH
	ChannelType	allocationpolicy
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: mpls-bounces@ietf.org
Errors-To: mpls-bounces@ietf.org

Eric,

This is true, but it all depends on the Expert guidelines we setup.
We can easily put in place a rule that mitigates this problem.

Luca


Eric Gray wrote:
> Luca,
>
> 	The practical reality is that expert review gives the 
> designated "expert" (or experts) the same level of control 
> of assignment as IESG review gives ADs over RFC publication.
> While it is possible to push something through against the
> "wishes" of an expert (who does in fact have more than the
> ability to "advise" the requesting individual/organization),
> the process can be quite confrontational and tedious.
>
> --
> Eric Gray
> Principal Engineer
> Ericsson  
>
>   
>> -----Original Message-----
>> From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On 
>> Behalf Of Luca Martini
>> Sent: Thursday, October 02, 2008 2:17 PM
>> To: Shahram Davari
>> Cc: Thomas D. Nadeau; mpls@ietf.org; BOCCI Matthew; 
>> ccamp@ietf.org; l2vpn@ietf.org; pwe3@ietf.org; BUSI ITALO; 
>> mpls-tp@ietf.org
>> Subject: Re: [mpls] [PWE3] [mpls-tp] FW: Changes to PW ACH 
>> ChannelType allocationpolicy
>>
>> Shahram,
>> the point of expert review is not to prevent vendor specific OAM 
>> methods. It is to prevent duplication, and guide implementors in the 
>> right direction.
>> For example , if somebody needs a new PW type , for a very vendor 
>> specific protocol , say Apollo DDS ( I was the last recorded user of 
>> that ;-) ), but asks for an ACH type instead , the expert can 
>> advise to 
>> use a new pw type. In the end there is no enforcement method, so any 
>> vendor can do anything they want. The only part we can do 
>> here , is have 
>> some sane documentation of the methods we put in the registry. ( 
>> documentation could be as short a a line , or as long as a draft )
>>
>> Luca
>>
>>
>> Shahram Davari wrote:
>>     
>>> No one asked for IETF rubber stamping. I asked for a 
>>>       
>> mechanism (code point assignment) that easily implement 
>> vendor specific methods. I don't see any reason why IETF 
>> should review and approve a vendor specific method. If IETF 
>> doesn't want to see any vendor specific method, then it 
>> doesn't need to allocate any code points. However, if IETF 
>> wants to encourage vendor specific protocols then it must do 
>> so in a way that makes it easy for vendors to use it.
>>     
>>> -Shahram
>>>
>>>
>>> -----Original Message-----
>>> From: Thomas D. Nadeau [mailto:tom.nadeau@bt.com] 
>>> Sent: October-02-08 12:44 PM
>>> To: Shahram Davari; Shane Amante
>>> Cc: l2vpn@ietf.org; mpls@ietf.org; BOCCI Matthew; 
>>>       
>> ccamp@ietf.org; mpls-tp@ietf.org; Vishwas Manral; 
>> pwe3@ietf.org; BUSI ITALO
>>     
>>> Subject: Re: [mpls-tp] [PWE3] FW: Changes to PW ACH Channel 
>>>       
>> Type allocationpolicy
>>     
>>>
>>>     I agree with %100 of Shane's comments. One bit to add below:
>>>
>>>   
>>>       
>>>> Hi Shane,
>>>>
>>>> Please see my response in-line.
>>>>
>>>> Best regards,
>>>> Shahram
>>>>
>>>>
>>>> -----Original Message-----
>>>> From: Shane Amante [mailto:shane@castlepoint.net]
>>>> Sent: October-02-08 10:43 AM
>>>> To: Shahram Davari
>>>> Cc: BUSI ITALO; Vishwas Manral; l2vpn@ietf.org; BOCCI 
>>>>         
>> Matthew; mpls@ietf.org;
>>     
>>>> ccamp@ietf.org; mpls-tp@ietf.org; pwe3@ietf.org
>>>> Subject: Re: [mpls-tp] [PWE3] FW: Changes to PW ACH Channel Type
>>>> allocationpolicy
>>>>
>>>> Shahram Davari wrote:
>>>>     
>>>>         
>>>>> Hi,
>>>>>
>>>>> I also prefer the method that Wishwas proposed. This has 
>>>>>           
>> many advantages:
>>     
>>>>> 1) Allows vendors to not expose their proprietary 
>>>>>           
>> techniques to their
>>     
>>>>> competitors.
>>>>>       
>>>>>           
>>>>  From the POV of an operator, this is actually a 
>>>>         
>> substantial disadvantage.
>>     
>>>> [Shahram] OTOH it encourages more innovation and 
>>>>         
>> differentiation by vendors.
>>     
>>>>     
>>>>         
>>>     That is hogwash. Customers encourage vendors to 
>>>       
>> innovate not standards
>>     
>>> bodies. Standards bodies help encourage and foster 
>>>       
>> interoperability of a
>>     
>>> common specification. The latter is the important point 
>>>       
>> Shane is making (as
>>     
>>> am I and others who are the customers in this equation). We 
>>>       
>> don't want to
>>     
>>> encourage proprietary implementations for the sake of proprietary
>>> implementations; we want to encourage them to ultimately 
>>>       
>> interoperate on a
>>     
>>> common specification. However, if your goal as a vendor is to create
>>> proprietary implementations you are free to do so, but you 
>>>       
>> do not need the
>>     
>>> IETF unless you are looking for some sort of rubber stamp 
>>>       
>> of approval.
>>     
>>>     --Tom
>>>
>>>
>>>   
>>>   
>>>       
>>>>> 2) reduces the load of reviewing by IETF and PWE3
>>>>>       
>>>>>           
>>>> OTOH, the benefit of such reviews by the IETF and PWE3 is when
>>>> "commonality" among similar applications are discovered they can be
>>>> standardized, rather kept proprietary.
>>>>
>>>> [Shahram] Not if the inventing vendor is not willing to do so.
>>>>
>>>>
>>>>     
>>>>         
>>>>> 3) results a faster time to market, since no expert 
>>>>>           
>> review will be needed
>>     
>>>>>       
>>>>>           
>>>> True, to some extent.  But, IMHO, I would much rather see 
>>>>         
>> a *slightly*
>>     
>>>> slower process involving a careful expert review and/or 
>>>>         
>> IETF consensus
>>     
>>>> to make sure we're not: a) unnecessarily duplicating work; 
>>>>         
>> and, b) at
>>     
>>>> the same time, encouraging more standards-based approach.
>>>>
>>>>
>>>>     
>>>>         
>>>>> 4) provides more codepoint space that the ACH channel type
>>>>>       
>>>>>           
>>>> This is false.  There is no shortage on ACH channel types today.
>>>> [Shahram] You are correct. 16-bit is sufficient enough.
>>>>
>>>>
>>>>     
>>>>         
>>>>> 5) only one VCCV ACH channel type needs to be configured 
>>>>>           
>> in each box for
>>     
>>>>> vendor specific filtering
>>>>>
>>>>> The 2nd method has the first 3 advantages only, and the 
>>>>>           
>> first method has none
>>     
>>>>> of these advantages.
>>>>>       
>>>>>           
>>>> Also, let's take a step back here.  Wasn't the whole point with the
>>>> joint ITU-T/IETF effort surrounding MPLS-TP to create an 
>>>>         
>> environment in
>>     
>>>> which MPLS-TP could seamlessly interoperate within (existing) MPLS
>>>> environments?  I thought a fundamental part of that work 
>>>>         
>> is striving
>>     
>>>> towards creating a *standards-based* MPLS-TP data-plane, 
>>>>         
>> OAM, signaling,
>>     
>>>> etc. mechanisms.  IMO, Vishwas' proposal and Matthew's 
>>>>         
>> proposal #2 seems
>>     
>>>> to run contrary to that goal.
>>>>
>>>> [Shahram] off course we should all encourage standards 
>>>>         
>> methods. But we should
>>     
>>>> provide a fast and reasonable procedure for vendor 
>>>>         
>> specific protocols that
>>     
>>>> don't affect interoperability. I worry that in first 
>>>>         
>> method competitors may
>>     
>>>> vote down code point requests for commercial reasons.
>>>>
>>>> -shane (speaking only for himself, not as co-chair)
>>>>
>>>>
>>>>
>>>>     
>>>>         
>>>
>>>
>>> _______________________________________________
>>> pwe3 mailing list
>>> pwe3@ietf.org
>>> https://www.ietf.org/mailman/listinfo/pwe3
>>>   
>>>       
>> _______________________________________________
>> mpls mailing list
>> mpls@ietf.org
>> https://www.ietf.org/mailman/listinfo/mpls
>>
>>     
>
>   

_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls


From mpls-bounces@ietf.org  Fri Oct  3 08:47:32 2008
Return-Path: <mpls-bounces@ietf.org>
X-Original-To: mpls-archive@megatron.ietf.org
Delivered-To: ietfarch-mpls-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 467E63A6839;
	Fri,  3 Oct 2008 08:47:32 -0700 (PDT)
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id EA5E33A6765;
	Fri,  3 Oct 2008 08:47:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.117
X-Spam-Level: 
X-Spam-Status: No, score=-1.117 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, DNS_FROM_RFC_BOGUSMX=1.482]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id DtofRHE4x9vP; Fri,  3 Oct 2008 08:47:30 -0700 (PDT)
Received: from dog.tcb.net (dog.tcb.net [64.78.150.133])
	by core3.amsl.com (Postfix) with ESMTP id 3F5783A679F;
	Fri,  3 Oct 2008 08:47:30 -0700 (PDT)
Received: by dog.tcb.net (Postfix, from userid 0)
	id 3C181268675; Fri,  3 Oct 2008 09:47:52 -0600 (MDT)
Received: from [127.0.0.1] (dog.tcb.net [64.78.150.133])
	(authenticated-user smtp) (TLSv1/SSLv3 DHE-RSA-AES256-SHA 256/256)
	by dog.tcb.net with SMTP; Fri, 03 Oct 2008 09:47:52 -0600 (MDT)
	(envelope-from shane@castlepoint.net)
X-Avenger: version=0.7.8; receiver=dog.tcb.net; client-ip=64.78.150.133;
	client-port=45016; data-bytes=0
Message-ID: <48E63EA7.1080207@castlepoint.net>
Date: Fri, 03 Oct 2008 09:47:51 -0600
From: Shane Amante <shane@castlepoint.net>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
To: "Thomas D. Nadeau" <tom.nadeau@bt.com>
References: <C50BAC4F.E2DD%tom.nadeau@bt.com>
In-Reply-To: <C50BAC4F.E2DD%tom.nadeau@bt.com>
Cc: l2vpn@ietf.org, mpls@ietf.org, ccamp@ietf.org, mpls-tp@ietf.org,
	pwe3@ietf.org, BUSI ITALO <Italo.Busi@alcatel-lucent.it>
Subject: Re: [mpls] [mpls-tp] [PWE3] Changes to PW ACH
	Channel	Typeallocationpolicy
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: mpls-bounces@ietf.org
Errors-To: mpls-bounces@ietf.org

Thomas D. Nadeau wrote:
> 
> 
> On 10/3/08 10:52 AM, "BRUNGARD, DEBORAH A, ATTLABS" <dbrungard@att.com>
> wrote:
> 
>> Hi Italo,
>>
>> It is much more than a codepoint and ensuring the nodes are provisioned
>> correctly - which is in itself difficult - especially in large networks.
>> Here's just a partial list of additional concerns from an operator:
>> - proprietary protocols perpetuate the use of vendor islands - good for
>> a vendor/bad for an operator;-(
>> - each protocol, proprietary or not, for an operator requires testing of
>> the protocol itself, not just if it works as it should, but also
>> development and testing of failure scenarios, and the negotiation with
>> the vendor for fixes. And if it's proprietary, an operator is on their
>> own for determining bugs, determining the correct fix, testing the fix,
>> etc, etc.
>> - OS development - this is probably the biggest hit on time for
>> deployment and most costly (and it's not just for deployment, it
>> continues for the lifetime).
>>
>> Which is why we have standards. I'm sure the others can add many more
>> (still on my first coffee here) and take a look back over Shane's mails.
> 
>     Nothing to add here; hits the nail right on the head.
> 
>     --Tom

Ditto.

-shane
_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls


From mpls-bounces@ietf.org  Mon Oct  6 03:12:29 2008
Return-Path: <mpls-bounces@ietf.org>
X-Original-To: mpls-archive@megatron.ietf.org
Delivered-To: ietfarch-mpls-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 83A5028C157;
	Mon,  6 Oct 2008 03:12:29 -0700 (PDT)
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 1FF383A69E9;
	Mon,  6 Oct 2008 03:12:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.985
X-Spam-Level: 
X-Spam-Status: No, score=-1.985 tagged_above=-999 required=5
	tests=[AWL=-0.678, BAYES_00=-2.599, MISSING_HEADERS=1.292]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id Xis8s9oXsGuj; Mon,  6 Oct 2008 03:12:27 -0700 (PDT)
Received: from neo.viciousnest.net (neo.viciousnest.net [192.71.80.124])
	by core3.amsl.com (Postfix) with ESMTP id E2E483A689D;
	Mon,  6 Oct 2008 03:12:26 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1])
	by neo.viciousnest.net (Postfix) with ESMTP id 46343431E6;
	Mon,  6 Oct 2008 12:12:42 +0200 (CEST)
Received: from neo.viciousnest.net ([127.0.0.1])
	by localhost (neo [127.0.0.1]) (amavisd-new, port 10024) with ESMTP
	id 03199-03; Mon,  6 Oct 2008 12:12:40 +0200 (CEST)
Received: from [10.4.144.123] (pat.acreo.se [217.151.195.214])
	by neo.viciousnest.net (Postfix) with ESMTP id ECBA1431DB;
	Mon,  6 Oct 2008 12:12:39 +0200 (CEST)
Message-ID: <48E9E491.1050700@pi.nu>
Date: Mon, 06 Oct 2008 12:12:33 +0200
From: Loa Andersson <loa@pi.nu>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
References: <001601c92786$bfe979a0$6d02a8c0@china.huawei.com>
In-Reply-To: <001601c92786$bfe979a0$6d02a8c0@china.huawei.com>
X-Enigmail-Version: 0.95.7
X-Virus-Scanned: by amavisd-new at viciousnest.net
Cc: l2vpn@ietf.org, mpls@ietf.org, ccamp@ietf.org, pwe3@ietf.org,
	mpls-tp@ietf.org
Subject: Re: [mpls] Changes to PW ACH Channel Type allocation policy
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mpls-bounces@ietf.org
Errors-To: mpls-bounces@ietf.org

All,

most IETF lists has a limit to how many recipients they allow on a
single mail. If we just keep responding to the last mail with a
"reply to all" the recipients list keep building up and actions by
list administrators is needed to let your mail be forwarded to the
list(s).

I've three suggestions:

1. We keep *discussion* of this just to the pwe3-list, now we all know
   that is is going on and are able to follow it on that list
2. when the pwe3 wg chairs make the consensus call they send it to all
   the lists it was originally sent to
3. We all make it a habit to prune the recipients-list to what is
   necessary (please make the assumption that people sending mails to
  IETF-lists are subscribed to the lists).

/Loa

Maarten Vissers wrote:
> Ben,
> 
> Also in case of a multi-vendor network there should be no issue. The new
> functionality is present only in the UNI-N ports (i.e. where the service is
> mapped into the PW). When you deploy such new functionality in UNI-N ports
> contained in Network Termination devices you can deploy those NT devices
> from one vendor. The main network now only has to carry the MS-PW between
> the NT devices at the edge of the network. The main network is as such
> agnostic to the new functionality.
> 
> The use of NT devices to support new (non standard) services not only allows
> differentiation by vendors, but also differentiation by operators. Operators
> wanting to differentiate their service offerings can ask a NT device vendor
> to add their operator specific service to the NT device.
> 
> Regards,
> Maarten
> 
> -----Original Message-----
> From: pwe3-bounces@ietf.org [mailto:pwe3-bounces@ietf.org] On Behalf Of Ben
> Niven-Jenkins
> Sent: 02 October 2008 19:30
> To: Shahram Davari; Shane Amante
> Cc: l2vpn@ietf.org; mpls@ietf.org; BOCCI Matthew; ccamp@ietf.org;
> mpls-tp@ietf.org; pwe3@ietf.org; BUSI ITALO
> Subject: Re: [PWE3] [mpls-tp] FW: Changes to PW ACH Channel Type
> allocationpolicy
> 
> On 02/10/2008 17:05, "Shahram Davari" <davari@tpack.com> wrote:
>> From: Shane Amante [mailto:shane@castlepoint.net] Shahram Davari 
>> wrote:
>>> Hi,
>>>
>>> I also prefer the method that Wishwas proposed. This has many advantages:
>>>
>>> 1) Allows vendors to not expose their proprietary techniques to their 
>>> competitors.
>>  From the POV of an operator, this is actually a substantial disadvantage.
>>
>> [Shahram] OTOH it encourages more innovation and differentiation by
> vendors.
> 
> Which is fine until you run a multi-vendor network.
> 
> Ben
> 
> _______________________________________________
> pwe3 mailing list
> pwe3@ietf.org
> https://www.ietf.org/mailman/listinfo/pwe3
> 
> 
> _______________________________________________
> pwe3 mailing list
> pwe3@ietf.org
> https://www.ietf.org/mailman/listinfo/pwe3


-- 
Loa Andersson

Principal Networking Architect
Acreo AB                           phone:  +46 8 632 77 14
Isafjordsgatan 22                  mobile: +46 739 81 21 64
Kista, Sweden                      email:  loa.andersson@acreo.se
                                           loa@pi.nu
_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls


From mpls-bounces@ietf.org  Mon Oct  6 03:34:07 2008
Return-Path: <mpls-bounces@ietf.org>
X-Original-To: mpls-archive@megatron.ietf.org
Delivered-To: ietfarch-mpls-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E6DBD28C1E9;
	Mon,  6 Oct 2008 03:34:06 -0700 (PDT)
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B0B343A6AA4;
	Mon,  6 Oct 2008 03:34:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.382
X-Spam-Level: 
X-Spam-Status: No, score=-5.382 tagged_above=-999 required=5 tests=[AWL=0.867, 
	BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id oHhFivSwm8yE; Mon,  6 Oct 2008 03:34:02 -0700 (PDT)
Received: from mailgw4.ericsson.se (mailgw4.ericsson.se [193.180.251.62])
	by core3.amsl.com (Postfix) with ESMTP id 6FA083A6A9C;
	Mon,  6 Oct 2008 03:34:02 -0700 (PDT)
Received: from mailgw4.ericsson.se (unknown [127.0.0.1])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	6DB6320667; Mon,  6 Oct 2008 12:34:37 +0200 (CEST)
X-AuditID: c1b4fb3e-a6680bb000007a96-c2-48e9e9bda1ae
Received: from esealmw128.eemea.ericsson.se (unknown [153.88.254.121])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	3E31D2026F; Mon,  6 Oct 2008 12:34:37 +0200 (CEST)
Received: from esealmw118.eemea.ericsson.se ([153.88.200.77]) by
	esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 6 Oct 2008 12:34:36 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Mon, 6 Oct 2008 12:34:34 +0200
Message-ID: <93DFCD4B101EB440B5B72997456C5F9402AFCF0B@esealmw118.eemea.ericsson.se>
In-Reply-To: <0458D2EE0C36744BABB36BE37805C29A029C6251@FRVELSMBS11.ad2.ad.alcatel.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [mpls-tp] FW: [PWE3] Changes to PW ACH Channel Type
	allocationpolicy
thread-index: AckeEgHxlvy9zCPET0WFoA5KKm0awgBET6egAP0oyGABIcWK0A==
References: <0458D2EE0C36744BABB36BE37805C29A029C6251@FRVELSMBS11.ad2.ad.alcatel.com>
From: "Annamaria Fulignoli" <annamaria.fulignoli@ericsson.com>
To: "BOCCI Matthew" <Matthew.Bocci@alcatel-lucent.com>, <pwe3@ietf.org>,
	<mpls-tp@ietf.org>, <mpls@ietf.org>, <ccamp@ietf.org>, <l2vpn@ietf.org>
X-OriginalArrivalTime: 06 Oct 2008 10:34:36.0928 (UTC)
	FILETIME=[21552000:01C9279F]
X-Brightmail-Tracker: AAAAAA==
Subject: Re: [mpls] [mpls-tp] FW: [PWE3] Changes to PW ACH Channel Type
	allocationpolicy
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: mpls-bounces@ietf.org
Errors-To: mpls-bounces@ietf.org

Hi Matthew,
I support option 2.

Best Regards
Annamaria =


-----Original Message-----
From: mpls-tp-bounces@ietf.org [mailto:mpls-tp-bounces@ietf.org] On Behalf =
Of BOCCI Matthew
Sent: marted=EC 30 settembre 2008 18.23
To: pwe3@ietf.org; mpls-tp@ietf.org; mpls@ietf.org; ccamp@ietf.org; l2vpn@i=
etf.org
Subject: [mpls-tp] FW: [PWE3] Changes to PW ACH Channel Type allocationpoli=
cy

The PWE3 chairs would like feedback on proposed changes to the allocation p=
olicy for the PW ACH codepoint registry. Please see the email below, and pr=
ovide any feedback copying the PWE3 list.

Best regards

Matthew

-----Original Message-----
From: pwe3-bounces@ietf.org [mailto:pwe3-bounces@ietf.org] On Behalf Of BOC=
CI Matthew
Sent: 25 September 2008 16:36
To: pwe3@ietf.org
Subject: [PWE3] Changes to PW ACH Channel Type allocation policy


 =

The current IANA allocation policy for the PW associated channel type regis=
try is by IETF consensus. This policy was chosen in RFC 4385 based on WG co=
nsensus that since the associated channel exists in the data path, and VCCV=
 packets are typically processed by the control processor on many PEs, it w=
as prudent for the IETF to maintain strict control over what types of chann=
els were allocated and to ensure that they complied to the PWE3 architectur=
e.

However, a need has been identified to provide a more flexible approach to =
allocating code points for VCCV channel types. This has partly arisen from =
the MPLS-TP work, where MPLS would be deployed in a transport network and w=
here a much wider range of applications for the PW associated channel is en=
visioned, and partialy from a desire to extend the OAM capabilities for reg=
ular MPLS. We can support MPLS-TP and general MPLS apps with the current po=
licy which requires standards action.

However we are receiving requests to allow proprietary OAM and signaling pr=
otocols to be used in transport applications, and need to decide on the bes=
t way forward. We considered providing extension mechanisms within the stan=
dards track protocols, but believe that the standards track protocols would=
 be much cleaner if the proprietary protocols ran on their own ACH code poi=
nts.

Note that we are talking about vendor protocols here. Other SDOs would be r=
equired to publish an RFC and would only be allocated an ACH through Standa=
rds Action.

There are two ways to address the requests for proprietary protocol ACH cod=
e points:

1) Allow a range of the associated channel type registry to be allocated th=
rough expert review. Guidelines would be provided for the expert reviewer t=
o guide them in assessing the request, which would have to be made in the f=
orm of an internet draft, while making sure that the request is dealt with =
in a timely and fair manner. This policy would include hurdles with regard =
to security, congestion etc that would be derived from those specified in t=
he VCCV design.

2) Allow a range of the associated channel type registry to be allocated on=
 a first-come-first-served basis. This does not provide the level of contro=
l that expert review provides, but this is balanced to some degree by the f=
act that the VCCV channel type is indicated in the data path, and so a PE c=
an choose to discard or rate limit VCCV packets on an unrecognised associat=
ed channel.

Any change to the ACH allocation policy would be outlined in the GE-ACH dra=
ft, which would update RFC 4385.

We would appreciate feedback on the list as to which approach the WG prefer=
s.

Regards,

Stewart and Matthew

_______________________________________________
pwe3 mailing list
pwe3@ietf.org
https://www.ietf.org/mailman/listinfo/pwe3
_______________________________________________
mpls-tp mailing list
mpls-tp@ietf.org
https://www.ietf.org/mailman/listinfo/mpls-tp
_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls


From mpls-bounces@ietf.org  Mon Oct  6 08:25:27 2008
Return-Path: <mpls-bounces@ietf.org>
X-Original-To: mpls-archive@megatron.ietf.org
Delivered-To: ietfarch-mpls-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 7F4B03A6A65;
	Mon,  6 Oct 2008 08:25:27 -0700 (PDT)
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id DB9993A6A69;
	Mon,  6 Oct 2008 08:25:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.599
X-Spam-Level: 
X-Spam-Status: No, score=-5.599 tagged_above=-999 required=5 tests=[AWL=0.650, 
	BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id aPbXjL9ZVU+d; Mon,  6 Oct 2008 08:25:13 -0700 (PDT)
Received: from mailgw3.ericsson.se (mailgw3.ericsson.se [193.180.251.60])
	by core3.amsl.com (Postfix) with ESMTP id D550D3A68DF;
	Mon,  6 Oct 2008 08:25:12 -0700 (PDT)
Received: from mailgw3.ericsson.se (unknown [127.0.0.1])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	4751820BCB; Mon,  6 Oct 2008 17:25:48 +0200 (CEST)
X-AuditID: c1b4fb3c-ae0cebb0000015b5-9c-48ea2dfcc660
Received: from esealmw126.eemea.ericsson.se (unknown [153.88.254.123])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	0AF5120B8F; Mon,  6 Oct 2008 17:25:48 +0200 (CEST)
Received: from esealmw118.eemea.ericsson.se ([153.88.200.77]) by
	esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 6 Oct 2008 17:25:47 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Mon, 6 Oct 2008 17:25:46 +0200
Message-ID: <93DFCD4B101EB440B5B72997456C5F9402AFD4E9@esealmw118.eemea.ericsson.se>
In-Reply-To: <48E47DA7.9090803@chello.nl>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [mpls] [mpls-tp] [PWE3] FW: Changes to PW ACH
	ChannelType	allocationpolicy
thread-index: AckkunwGNjaNTeEoRkiUgbT0DtwQJQDCc+Eg
References: <0458D2EE0C36744BABB36BE37805C29A029C6251@FRVELSMBS11.ad2.ad.alcatel.com>	<ba6305ea8b6f7b41bae8dcbb49c37c7c@mail.cph.tpack.net>	<77ead0ec0810010847r10efb0f0ncb4e24f5d9b4c492@mail.gmail.com>	<6FD21B53861BF44AA90A288402036AB40193F737@FRVELSMBS21.ad2.ad.alcatel.com><77ead0ec0810020021l47d220f7n3a42651d1a17a6b4@mail.gmail.com>
	<48E47DA7.9090803@chello.nl>
From: "Annamaria Fulignoli" <annamaria.fulignoli@ericsson.com>
To: "BOCCI Matthew" <Matthew.Bocci@alcatel-lucent.com>, <hhelvoort@chello.nl>,
	"Vishwas Manral" <vishwas.ietf@gmail.com>,
	"BUSI ITALO" <Italo.Busi@alcatel-lucent.it>
X-OriginalArrivalTime: 06 Oct 2008 15:25:47.0435 (UTC)
	FILETIME=[CE90EFB0:01C927C7]
X-Brightmail-Tracker: AAAAAA==
Cc: l2vpn@ietf.org, mpls@ietf.org, ccamp@ietf.org, pwe3@ietf.org,
	mpls-tp@ietf.org
Subject: Re: [mpls] [mpls-tp] [PWE3] FW: Changes to PW ACH
	ChannelType	allocationpolicy
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: mpls-bounces@ietf.org
Errors-To: mpls-bounces@ietf.org

Hi Matthew,
I also prefer the method that Wishwas proposed;
that for the several reasons yet clearly exposed in the mails below.
Besides, is it possible to "recognize" it as a possible third solution =

and add it to the two ones you proposed in your first mail ?

Thanks,BR.

Annamaria  =


-----Original Message-----
From: l2vpn-bounces@ietf.org [mailto:l2vpn-bounces@ietf.org] On Behalf Of H=
uub van Helvoort
Sent: gioved=EC 2 ottobre 2008 9.52
To: Vishwas Manral
Cc: l2vpn@ietf.org; mpls@ietf.org; BOCCI Matthew; ccamp@ietf.org; mpls-tp@i=
etf.org; pwe3@ietf.org; BUSI ITALO
Subject: Re: [mpls] [mpls-tp] [PWE3] FW: Changes to PW ACH ChannelType allo=
cationpolicy

Hi Vishwas,

I support your proposal as well.

Your proposal is in fact in line with the way the vendor specific codepoint=
 is used in ITU-T Y.1731.

One of the objectives of the MPLS-TP JWT is to align with Y.1731 so this pe=
rfectly matches the objective.

Cheers, Huub.

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> Hi Italo,
> =

> I agree and that was my exact aim.
> =

> The other added advantage is that there are no interoperability issues =

> and no bottlenecks of assignments for a particular type.
> =

> Thanks,
> Vishwas
> =

> On 10/2/08, BUSI ITALO <Italo.Busi@alcatel-lucent.it> wrote:
>> Vishwas,
>>
>> I think this is a good idea
>>
>> Both this proposal and option 2 (fist-come-first-served) meet the =

>> requirements to make the ACH mechanism extensible.
>>
>> The advantage of this approach is that we do not have to worry about =

>> how many codepoints we need to allocate for proprietary extensions: =

>> we just need one codepoint.
>>
>> Italo
>>
>>> -----Original Message-----
>>> From: mpls-tp-bounces@ietf.org
>>> [mailto:mpls-tp-bounces@ietf.org] On Behalf Of Vishwas Manral
>>> Sent: Wednesday, October 01, 2008 5:47 PM
>>> To: Shahram Davari
>>> Cc: l2vpn@ietf.org; BOCCI Matthew; mpls@ietf.org; ccamp@ietf.org; =

>>> mpls-tp@ietf.org; pwe3@ietf.org
>>> Subject: Re: [mpls-tp] [PWE3] FW: Changes to PW ACH Channel Type =

>>> allocationpolicy
>>>
>>> Hi Matthew,
>>>
>>> I would like to propose another option if it is for vendor =

>>> proprietery "Channel Type" values in the ACH header. With the number =

>>> of values of the channel type being limited and the number of =

>>> vendors actually a lot, I would think something in the lines of what =

>>> the draft below talks about may make sense:
>>>
>>> http://tools.ietf.org/draft-ietf-isis-proprietary-tlv-00
>>>
>>> The idea is give a channel type value, for vendor specific =

>>> implemntations and further define the structure of the next header =

>>> value for such a "channel type" to actually have a Vendor OUI value.
>>>
>>> This will allow for unlimited innovation without affecting =

>>> interoperability, unlike the other options you have mentioned.
>>>
>>> Thanks,
>>> Vishwas
>>>
>>>
>>> On 10/1/08, Shahram Davari <davari@tpack.com> wrote:
>>>> Hi Mathew,
>>>>
>>>> I support option 2, since a terminating node that doesn't
>>> understand the
>>>> VCCV channel type can always drop it. This would allow more
>>> innovation and
>>>> faster time to market.
>>>>
>>>> Best regards,
>>>> Shahram
>>>>
>>>>
>>>> -----Original Message-----
>>>> From: pwe3-bounces@ietf.org [mailto:pwe3-bounces@ietf.org]
>>> On Behalf Of
>>>> BOCCI Matthew
>>>> Sent: September-30-08 12:23 PM
>>>> To: pwe3@ietf.org; mpls-tp@ietf.org; mpls@ietf.org; ccamp@ietf.org; =

>>>> l2vpn@ietf.org
>>>> Subject: [PWE3] FW: Changes to PW ACH Channel Type allocation =

>>>> policy
>>>>
>>>> The PWE3 chairs would like feedback on proposed changes to the =

>>>> allocation policy for the PW ACH codepoint registry. Please see the =

>>>> email below, and provide any feedback copying the PWE3 list.
>>>>
>>>> Best regards
>>>>
>>>> Matthew
>>>>
>>>> -----Original Message-----
>>>> From: pwe3-bounces@ietf.org [mailto:pwe3-bounces@ietf.org]
>>> On Behalf Of
>>>> BOCCI Matthew
>>>> Sent: 25 September 2008 16:36
>>>> To: pwe3@ietf.org
>>>> Subject: [PWE3] Changes to PW ACH Channel Type allocation policy
>>>>
>>>>
>>>>
>>>> The current IANA allocation policy for the PW associated
>>> channel type
>>>> registry is by IETF consensus. This policy was chosen in
>>> RFC 4385 based
>>>> on WG consensus that since the associated channel exists in the =

>>>> data path, and VCCV packets are typically processed by the
>>> control processor
>>>> on many PEs, it was prudent for the IETF to maintain strict
>>> control over
>>>> what types of channels were allocated and to ensure that
>>> they complied
>>>> to the PWE3 architecture.
>>>>
>>>> However, a need has been identified to provide a more
>>> flexible approach
>>>> to allocating code points for VCCV channel types. This has
>>> partly arisen
>>>> from the MPLS-TP work, where MPLS would be deployed in a transport =

>>>> network and where a much wider range of applications for the PW =

>>>> associated channel is envisioned, and partialy from a
>>> desire to extend
>>>> the OAM capabilities for regular MPLS. We can support MPLS-TP and =

>>>> general MPLS apps with the current policy which requires standards =

>>>> action.
>>>>
>>>> However we are receiving requests to allow proprietary OAM
>>> and signaling
>>>> protocols to be used in transport applications, and need to
>>> decide on
>>>> the best way forward. We considered providing extension mechanisms =

>>>> within the standards track protocols, but believe that the =

>>>> standards track protocols would be much cleaner if the proprietary
>>> protocols ran
>>>> on their own ACH code points.
>>>>
>>>> Note that we are talking about vendor protocols here. Other
>>> SDOs would
>>>> be required to publish an RFC and would only be allocated
>>> an ACH through
>>>> Standards Action.
>>>>
>>>> There are two ways to address the requests for proprietary
>>> protocol ACH
>>>> code points:
>>>>
>>>> 1) Allow a range of the associated channel type registry to
>>> be allocated
>>>> through expert review. Guidelines would be provided for the expert =

>>>> reviewer to guide them in assessing the request, which
>>> would have to be
>>>> made in the form of an internet draft, while making sure that the =

>>>> request is dealt with in a timely and fair manner. This policy =

>>>> would include hurdles with regard to security, congestion etc
>>> that would be
>>>> derived from those specified in the VCCV design.
>>>>
>>>> 2) Allow a range of the associated channel type registry to
>>> be allocated
>>>> on a first-come-first-served basis. This does not provide
>>> the level of
>>>> control that expert review provides, but this is balanced
>>> to some degree
>>>> by the fact that the VCCV channel type is indicated in the
>>> data path,
>>>> and so a PE can choose to discard or rate limit VCCV packets on an =

>>>> unrecognised associated channel.
>>>>
>>>> Any change to the ACH allocation policy would be outlined
>>> in the GE-ACH
>>>> draft, which would update RFC 4385.
>>>>
>>>> We would appreciate feedback on the list as to which approach the =

>>>> WG prefers.
>>>>
>>>> Regards,
>>>>
>>>> Stewart and Matthew
>>>>
>>>> _______________________________________________
>>>> pwe3 mailing list
>>>> pwe3@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/pwe3
>>>> _______________________________________________
>>>> pwe3 mailing list
>>>> pwe3@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/pwe3
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> pwe3 mailing list
>>>> pwe3@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/pwe3
>>>>
>>> _______________________________________________
>>> mpls-tp mailing list
>>> mpls-tp@ietf.org
>>> https://www.ietf.org/mailman/listinfo/mpls-tp
>>>
> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls
> =


--
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
                   http://www.van-helvoort.eu/ =3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D
Always remember that you are unique...just like everyone else...
_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls


From mpls-bounces@ietf.org  Mon Oct  6 09:33:48 2008
Return-Path: <mpls-bounces@ietf.org>
X-Original-To: mpls-archive@megatron.ietf.org
Delivered-To: ietfarch-mpls-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id CC2A63A6820;
	Mon,  6 Oct 2008 09:33:48 -0700 (PDT)
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 6FD903A67DD
	for <mpls@core3.amsl.com>; Mon,  6 Oct 2008 09:33:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.508
X-Spam-Level: *
X-Spam-Status: No, score=1.508 tagged_above=-999 required=5
	tests=[BAYES_05=-1.11, FH_HOST_EQ_D_D_D_D=0.765,
	FH_HOST_EQ_D_D_D_DB=0.888, HELO_MISMATCH_COM=0.553,
	HOST_MISMATCH_NET=0.311, HTML_MESSAGE=0.001, RDNS_DYNAMIC=0.1]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id YdRiTJDe3PfP for <mpls@core3.amsl.com>;
	Mon,  6 Oct 2008 09:33:46 -0700 (PDT)
Received: from ns1.cpanel.btnaccess.com (205-177-121-254.pccwglobal.net
	[205.177.121.254])
	by core3.amsl.com (Postfix) with ESMTP id 8B6AD3A6969
	for <mpls@ietf.org>; Mon,  6 Oct 2008 09:33:46 -0700 (PDT)
Received: from [65.213.193.43] (helo=[127.0.0.1])
	by ns1.cpanel.btnaccess.com with esmtpa (Exim 4.69)
	(envelope-from <mtylenda@isocore.com>) id 1Kmt1p-0002r2-ME
	for mpls@ietf.org; Mon, 06 Oct 2008 12:33:49 -0400
Message-ID: <48EA3DF1.9050303@isocore.com>
Date: Mon, 06 Oct 2008 12:33:53 -0400
From: Matt Tylenda <mtylenda@isocore.com>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
To: mpls@ietf.org
X-AntiAbuse: This header was added to track abuse,
	please include it with any abuse report
X-AntiAbuse: Primary Hostname - ns1.cpanel.btnaccess.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - isocore.com
Subject: [mpls] Two weeks to MPLS2008 in Washington DC
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0594540662=="
Sender: mpls-bounces@ietf.org
Errors-To: mpls-bounces@ietf.org

This is a multi-part message in MIME format.
--===============0594540662==
Content-Type: multipart/alternative;
 boundary="------------030003080909050506090107"

This is a multi-part message in MIME format.
--------------030003080909050506090107
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

MPLS 2008 is set to take place, October 19-22, 2008. The technical 
program details and sponsors list
is available at: www.mpls2008.com

Registration is still open and accessible at 
http://www.isocore.com/mpls2008/registration/attendees.htm

-- 
Matt Tylenda
mtylenda@isocore.com
ISOCORE


--------------030003080909050506090107
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
</head>
<body bgcolor="#ffffff" text="#000000">
<font face="Courier New" size="2"><span
 style="font-size: 10pt; font-family: &quot;Courier New&quot;;">MPLS 2008 is set
to take place, October 19-22, 2008.
The technical program details and sponsors list<br>
is available at: <a class="moz-txt-link-abbreviated" href="http://www.mpls2008.com">www.mpls2008.com</a> <br>
</span></font><font face="Courier New"><span
 style="font-family: &quot;Courier New&quot;;"><br>
</span></font><font face="Courier New" size="2"><span
 style="font-size: 10pt; font-family: &quot;Courier New&quot;;">Registration is
still open and accessible at <a
 href="http://www.isocore.com/mpls2008/registration/attendees.htm"
 title="http://www.isocore.com/mpls2008/registration/attendees.htm">http://www.isocore.com/mpls2008/registration/attendees.htm</a>
</span></font>
<pre class="moz-signature" cols="72">-- 
Matt Tylenda
<a class="moz-txt-link-abbreviated" href="mailto:mtylenda@isocore.com">mtylenda@isocore.com</a>
ISOCORE</pre>
</body>
</html>

--------------030003080909050506090107--


--===============0594540662==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls

--===============0594540662==--



From mpls-bounces@ietf.org  Mon Oct  6 15:26:54 2008
Return-Path: <mpls-bounces@ietf.org>
X-Original-To: mpls-archive@megatron.ietf.org
Delivered-To: ietfarch-mpls-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 9326D3A684F;
	Mon,  6 Oct 2008 15:26:54 -0700 (PDT)
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id AA5F128C133
	for <mpls@core3.amsl.com>; Mon,  6 Oct 2008 15:23:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.449
X-Spam-Level: 
X-Spam-Status: No, score=-6.449 tagged_above=-999 required=5 tests=[AWL=0.150, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id yI5Lx5QNWfuV for <mpls@core3.amsl.com>;
	Mon,  6 Oct 2008 15:23:44 -0700 (PDT)
Received: from sj-iport-5.cisco.com (sj-iport-5.cisco.com [171.68.10.87])
	by core3.amsl.com (Postfix) with ESMTP id D0C8028C205
	for <mpls@ietf.org>; Mon,  6 Oct 2008 15:23:44 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,369,1220227200"; d="scan'208";a="47935525"
Received: from sj-dkim-1.cisco.com ([171.71.179.21])
	by sj-iport-5.cisco.com with ESMTP; 06 Oct 2008 22:24:22 +0000
Received: from sj-core-2.cisco.com (sj-core-2.cisco.com [171.71.177.254])
	by sj-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id m96MOMIj016440; 
	Mon, 6 Oct 2008 15:24:22 -0700
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com
	[64.102.31.102])
	by sj-core-2.cisco.com (8.13.8/8.13.8) with ESMTP id m96MOLka028860;
	Mon, 6 Oct 2008 22:24:21 GMT
Received: from xmb-rtp-212.amer.cisco.com ([64.102.31.111]) by
	xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 6 Oct 2008 18:24:21 -0400
X-Mimeole: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Mon, 6 Oct 2008 18:24:00 -0400
Message-ID: <42591A81B59EA14BAA617596482F65CE05C59C83@xmb-rtp-212.amer.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Fwd: New Version Notification for
	draft-dasmith-mpls-ip-options-01 
Thread-Index: AckoAOfplaTS4LREQAqFmQEPgiQZ9gAAGFrQ
From: "David Smith (djsmith)" <djsmith@cisco.com>
To: <mpls@ietf.org>
X-OriginalArrivalTime: 06 Oct 2008 22:24:21.0063 (UTC)
	FILETIME=[47747570:01C92802]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1774; t=1223331862;
	x=1224195862; c=relaxed/simple; s=sjdkim1004;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=djsmith@cisco.com;
	z=From:=20=22David=20Smith=20(djsmith)=22=20<djsmith@cisco.c
	om> |Subject:=20Fwd=3A=20New=20Version=20Notification=20for=20d
	raft-dasmith-mpls-ip-options-01=20 |Sender:=20;
	bh=Q47kahvPgKqvVzhoyZFQj9XQhRyum6T+Pcrk5lCib0c=;
	b=TOe13MnW1pQLWVqW0E6uwD+ySOB2bXgAU8Du6Y0O0GAmmbH6za0IAYXMsu
	GZnZT3t3U4aODD80GimxN4W3y0olMQ8OYJGwqd4EapFBIGK5jLI/C4BlK+DU
	TQR0QbASy0NBXsmQN4I7hwURUxNWr99JbaS+acld12/IRWBZqLDXo=;
Authentication-Results: sj-dkim-1; header.From=djsmith@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim1004 verified; ); 
Cc: "SCHOLL, TOM \(ATTLABS\)" <ts3127@att.com>,
	"John Mullooly \(jmullool\)" <jmullool@cisco.com>, "JAEGER,
	WILLIAM \(ATTSI\)" <wjaeger@att.com>
Subject: [mpls] Fwd: New Version Notification for
	draft-dasmith-mpls-ip-options-01
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mpls-bounces@ietf.org
Errors-To: mpls-bounces@ietf.org

 
FYI.  This version incorporates feedback received from MPLS WG members.
We ask that this version (01) be adopted as a working group draft. 

/dave

-----Original Message-----
From: IETF I-D Submission Tool [mailto:idsubmission@ietf.org] 
Sent: Monday, October 06, 2008 6:14 PM
To: David Smith (djsmith)
Cc: wjaeger@att.com; John Mullooly (jmullool); ts3127@att.com;
ipr@ietf.org
Subject: New Version Notification for draft-dasmith-mpls-ip-options-01 


A new version of I-D, draft-dasmith-mpls-ip-options-01.txt has been
successfuly submitted by David Smith and posted to the IETF repository.

Filename:	 draft-dasmith-mpls-ip-options
Revision:	 01
Title:		 Requirements for Label Edge Router Forwarding of IPv4
Option Packets
Creation_date:	 2008-10-06
WG ID:		 Independent Submission
Number_of_pages: 10

Abstract:
This document imposes a new requirement on Label Edge Routers (LER)
specifying that when determining whether to MPLS encapsulate an IP
packet, the determination is made independent of any IP options that may
be carried in the IP packet header.  Lack of a formal standard may
result in a different forwarding behavior for different IP packets
associated with the same prefix-based Forwarding Equivalence Class
(FEC).  While an IP packet with either a specific option type or no
header option may follow the MPLS label switched path (LSP) associated
with a prefix-based FEC, an IP packet with a different option type but
associated with the same prefix-based FEC may bypass MPLS encapsulation
and instead be IP routed downstream.  IP option packets that fail to be
MPLS encapsulated simply due to their header options present a security
risk against the MPLS infrastructure.
 



The IETF Secretariat.


_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls


From mpls-bounces@ietf.org  Tue Oct  7 01:40:06 2008
Return-Path: <mpls-bounces@ietf.org>
X-Original-To: mpls-archive@megatron.ietf.org
Delivered-To: ietfarch-mpls-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id A538328C141;
	Tue,  7 Oct 2008 01:40:06 -0700 (PDT)
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 9479728C137
	for <mpls@core3.amsl.com>; Tue,  7 Oct 2008 01:40:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id O1nS1Bv7aEHx for <mpls@core3.amsl.com>;
	Tue,  7 Oct 2008 01:40:03 -0700 (PDT)
Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.230])
	by core3.amsl.com (Postfix) with ESMTP id 8B7F928C127
	for <mpls@ietf.org>; Tue,  7 Oct 2008 01:40:03 -0700 (PDT)
Received: by rv-out-0506.google.com with SMTP id b25so3052405rvf.49
	for <mpls@ietf.org>; Tue, 07 Oct 2008 01:40:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
	h=domainkey-signature:received:received:message-id:date:from:to
	:subject:cc:in-reply-to:mime-version:content-type
	:content-transfer-encoding:content-disposition:references;
	bh=L2CZvD8wXz4h4w7EWWac+aP5nzHgK3+Q0qR35t5N4xA=;
	b=wv2id3fbaS3cfft0WixadDU7HheZWnsebZb+1HXYVRxC98S6+Z7ODs0O5+JPlVXWvx
	rwyhBREbJ+j3wetvX9tifMyEJ4sKDtqRuUY8t9PhG+drS5lsAO2ImY1VGpsIOwcX0UL5
	9iEKORk2ln/rJBjg4ksDNpm1qdFshRJwWRvJ4=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=message-id:date:from:to:subject:cc:in-reply-to:mime-version
	:content-type:content-transfer-encoding:content-disposition
	:references;
	b=sBhz/KjzYRTfDNsslqbrYuhlO2AvpEtRY+jxAXqjbE59xJOqaouEC4u8IoRxeBTsk0
	yWr6iAeH+UYAze7rGWDNDK71b31nlELgEqHFHxfKbgkOARYp9Nj15FaKqkVwBVhe7Jtl
	8peoeFhlobyySXA+l9Fe7WTmCMftqJcHmxOxs=
Received: by 10.140.208.17 with SMTP id f17mr310686rvg.218.1223368825942;
	Tue, 07 Oct 2008 01:40:25 -0700 (PDT)
Received: by 10.140.252.15 with HTTP; Tue, 7 Oct 2008 01:40:25 -0700 (PDT)
Message-ID: <7c923b5e0810070140u4e27bb75qef7284ef91d0cbc9@mail.gmail.com>
Date: Tue, 7 Oct 2008 10:40:25 +0200
From: "Francesco Fondelli" <francesco.fondelli@gmail.com>
To: stbryant@cisco.com
In-Reply-To: <48E51561.1070103@cisco.com>
MIME-Version: 1.0
Content-Disposition: inline
References: <48E51561.1070103@cisco.com>
Cc: "l2vpn@ietf.org" <l2vpn@ietf.org>, "mpls@ietf.org" <mpls@ietf.org>,
	"ccamp@ietf.org" <ccamp@ietf.org>, pwe3 <pwe3@ietf.org>,
	Mike Shand <mshand@cisco.com>
Subject: Re: [mpls] [mpls-tp] [PWE3] FW: Changes to PW ACH Channel Type
	allocation policy]
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mpls-bounces@ietf.org
Errors-To: mpls-bounces@ietf.org

Hi Stewart,

On Thu, Oct 2, 2008 at 8:39 PM, Stewart Bryant <stbryant@cisco.com> wrote:
> Since a reference was made to extension mechanisms proposed to
> the ISIS WG, and since there seemed to be some enthusiasm
> for it, to the point where there was a suggestion that we
> might follow the same model, I asked my college Mike Shand
> for some history and background and what happened next.

[cut]

> However, despite all this, the draft expired in November 2005 and there has
> been no subsequent desire to resurrect it.
>
> 	Mike

Ok, let me talk about something that is not dead :-)

in RSVP context class numbers 124..127 and 188..191 and 252..255
are "reserved for Vendor Private Use".
(http://www.iana.org/assignments/rsvp-parameters)
Definition of "Organization/Vendor Private" is in RFC 3936:

---
"Organization/Vendor Private" ranges refer to values that are
enterprise-specific; these MUST NOT be registered with IANA.  For
Vendor Private values, the first 4-octet word of the data field
MUST be an enterprise code [ENT] as registered with the IANA
SMI Network Management Private Enterprise Codes, and the rest
of the data thereafter is for the private use of the
registered enterprise.  (For each RSVP entity that has a
Vendor Private range, it must be specified where exactly the
data field starts; see below for examples.)  In this way,
different enterprises, vendors, or Standards Development
Organizations (SDOs) can use the same code point
without fear of collision.
---

I did implement some vendor-private-application-specific extensions
to RSVP following rules above and rules of RFC 2205 Section 3.10
(obj with Class-Num 0bbbbbbb rejected, 10bbbbbb ignored, 11bbbbbb
opaquely forwarded).

Never had an interoperability problem.

Is such a policy/mechanism applicable to "PW ACH Channel Type"?

Dunno, I just wanted to compensate the IS-IS history :-))

What do you think?

Ciao
FF

ps
obviously IANA doesn't charge you for a Private Eterprise Number
(PEN) http://pen.iana.org/pen/PenApplication.page
_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls


From mpls-bounces@ietf.org  Thu Oct  9 09:09:36 2008
Return-Path: <mpls-bounces@ietf.org>
X-Original-To: mpls-archive@megatron.ietf.org
Delivered-To: ietfarch-mpls-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 067A93A6A4A;
	Thu,  9 Oct 2008 09:09:36 -0700 (PDT)
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E9D6428C0EA;
	Mon,  6 Oct 2008 00:39:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.495
X-Spam-Level: 
X-Spam-Status: No, score=-0.495 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, 
	RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id PYSe3CGw51a7; Mon,  6 Oct 2008 00:39:50 -0700 (PDT)
Received: from szxga01-in.huawei.com (unknown [119.145.14.64])
	by core3.amsl.com (Postfix) with ESMTP id EE83D28C0EF;
	Mon,  6 Oct 2008 00:39:49 -0700 (PDT)
Received: from huawei.com (szxga01-in [172.24.2.3])
	by szxga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14
	(built Aug
	8 2006)) with ESMTP id <0K8B002BE3Z0AI@szxga01-in.huawei.com>; Mon,
	06 Oct 2008 15:40:13 +0800 (CST)
Received: from huawei.com ([172.24.1.6])
	by szxga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14
	(built Aug
	8 2006)) with ESMTP id <0K8B00LPK3YXMC@szxga01-in.huawei.com>; Mon,
	06 Oct 2008 15:40:12 +0800 (CST)
Received: from M00900002 (vissersm.demon.nl [83.160.252.43])
	by szxml02-in.huawei.com
	(iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug  8 2006))
	with ESMTPA id <0K8B004CI3YNUS@szxml02-in.huawei.com>; Mon,
	06 Oct 2008 15:40:12 +0800 (CST)
Date: Mon, 06 Oct 2008 09:39:59 +0200
From: Maarten Vissers <maarten.vissers@huawei.com>
In-reply-to: <C50AC39D.C5BD%benjamin.niven-jenkins@bt.com>
To: 'Ben Niven-Jenkins' <benjamin.niven-jenkins@bt.com>,
	'Shahram Davari' <davari@tpack.com>, 'Shane Amante' <shane@castlepoint.net>
Message-id: <001601c92786$bfe979a0$6d02a8c0@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
X-Mailer: Microsoft Office Outlook 11
Thread-index: AckkqLTHdNDdblepSIu2W52R3r7OPAAC8OmkALQvDPA=
X-Mailman-Approved-At: Thu, 09 Oct 2008 09:09:34 -0700
Cc: l2vpn@ietf.org, mpls@ietf.org,
	'BOCCI Matthew' <Matthew.Bocci@alcatel-lucent.com>,
	ccamp@ietf.org, mpls-tp@ietf.org, pwe3@ietf.org,
	'BUSI ITALO' <Italo.Busi@alcatel-lucent.it>
Subject: Re: [mpls] [PWE3] [mpls-tp] FW: Changes to PW ACH Channel Type
 allocationpolicy
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mpls-bounces@ietf.org
Errors-To: mpls-bounces@ietf.org

Ben,

Also in case of a multi-vendor network there should be no issue. The new
functionality is present only in the UNI-N ports (i.e. where the service is
mapped into the PW). When you deploy such new functionality in UNI-N ports
contained in Network Termination devices you can deploy those NT devices
from one vendor. The main network now only has to carry the MS-PW between
the NT devices at the edge of the network. The main network is as such
agnostic to the new functionality.

The use of NT devices to support new (non standard) services not only allows
differentiation by vendors, but also differentiation by operators. Operators
wanting to differentiate their service offerings can ask a NT device vendor
to add their operator specific service to the NT device.

Regards,
Maarten

-----Original Message-----
From: pwe3-bounces@ietf.org [mailto:pwe3-bounces@ietf.org] On Behalf Of Ben
Niven-Jenkins
Sent: 02 October 2008 19:30
To: Shahram Davari; Shane Amante
Cc: l2vpn@ietf.org; mpls@ietf.org; BOCCI Matthew; ccamp@ietf.org;
mpls-tp@ietf.org; pwe3@ietf.org; BUSI ITALO
Subject: Re: [PWE3] [mpls-tp] FW: Changes to PW ACH Channel Type
allocationpolicy

On 02/10/2008 17:05, "Shahram Davari" <davari@tpack.com> wrote:
> From: Shane Amante [mailto:shane@castlepoint.net] Shahram Davari 
> wrote:
>> Hi,
>> 
>> I also prefer the method that Wishwas proposed. This has many advantages:
>> 
>> 1) Allows vendors to not expose their proprietary techniques to their 
>> competitors.
> 
>  From the POV of an operator, this is actually a substantial disadvantage.
> 
> [Shahram] OTOH it encourages more innovation and differentiation by
vendors.

Which is fine until you run a multi-vendor network.

Ben

_______________________________________________
pwe3 mailing list
pwe3@ietf.org
https://www.ietf.org/mailman/listinfo/pwe3


_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls


From mpls-bounces@ietf.org  Thu Oct  9 09:09:36 2008
Return-Path: <mpls-bounces@ietf.org>
X-Original-To: mpls-archive@megatron.ietf.org
Delivered-To: ietfarch-mpls-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 94EB73A6ACA;
	Thu,  9 Oct 2008 09:09:36 -0700 (PDT)
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 3791528C165;
	Mon,  6 Oct 2008 00:49:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.495
X-Spam-Level: 
X-Spam-Status: No, score=-0.495 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, 
	RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id IcLVJmZtkLMR; Mon,  6 Oct 2008 00:49:15 -0700 (PDT)
Received: from szxga01-in.huawei.com (unknown [119.145.14.64])
	by core3.amsl.com (Postfix) with ESMTP id 9F3B83A69F5;
	Mon,  6 Oct 2008 00:49:14 -0700 (PDT)
Received: from huawei.com (szxga01-in [172.24.2.3])
	by szxga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14
	(built Aug
	8 2006)) with ESMTP id <0K8B0028N4ERAI@szxga01-in.huawei.com>; Mon,
	06 Oct 2008 15:49:39 +0800 (CST)
Received: from huawei.com ([172.24.1.3])
	by szxga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14
	(built Aug
	8 2006)) with ESMTP id <0K8B00F0V4ERK5@szxga01-in.huawei.com>; Mon,
	06 Oct 2008 15:49:39 +0800 (CST)
Received: from M00900002 (vissersm.demon.nl [83.160.252.43])
	by szxml01-in.huawei.com
	(iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug  8 2006))
	with ESMTPA id <0K8B003VZ4EE4K@szxml01-in.huawei.com>; Mon,
	06 Oct 2008 15:49:39 +0800 (CST)
Date: Mon, 06 Oct 2008 09:49:26 +0200
From: Maarten Vissers <maarten.vissers@huawei.com>
In-reply-to: <16a42c48f46e6547a1c3ce65f8fee99a@mail.cph.tpack.net>
To: 'Shahram Davari' <davari@tpack.com>,
	"'Thomas D. Nadeau'" <tom.nadeau@bt.com>,
	'Shane Amante' <shane@castlepoint.net>
Message-id: <001701c92788$11a596b0$6d02a8c0@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
X-Mailer: Microsoft Office Outlook 11
Thread-index: AckkqLTHdNDdblepSIu2W52R3r7OPAABUvW5AADtmEAAtUWvEA==
X-Mailman-Approved-At: Thu, 09 Oct 2008 09:09:34 -0700
Cc: l2vpn@ietf.org, mpls@ietf.org,
	'BOCCI Matthew' <Matthew.Bocci@alcatel-lucent.com>,
	ccamp@ietf.org, mpls-tp@ietf.org, pwe3@ietf.org,
	'BUSI ITALO' <Italo.Busi@alcatel-lucent.it>
Subject: Re: [mpls] [PWE3] [mpls-tp] FW: Changes to PW ACH Channel
	Typeallocationpolicy
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mpls-bounces@ietf.org
Errors-To: mpls-bounces@ietf.org

Sharam,

I agree.

In my understanding the PW ACH Channel Type provides the same function as
the EtherType in Ethernet networks. IEEE provides a means to buy an
EtherType codepoint (http://standards.ieee.org/regauth/ethertype/eth.txt).
The requesting organisation can decide to keep their associated application
private ("Protocl unavailable.") or to make it public.

As far as I understand this EtherType allocation policy is an industry
standard and could be copied for PW ACH Channel Type allocation policy.

Regards,
Maarten

-----Original Message-----
From: pwe3-bounces@ietf.org [mailto:pwe3-bounces@ietf.org] On Behalf Of
Shahram Davari
Sent: 02 October 2008 19:18
To: Thomas D. Nadeau; Shane Amante
Cc: l2vpn@ietf.org; mpls@ietf.org; BOCCI Matthew; ccamp@ietf.org;
mpls-tp@ietf.org; pwe3@ietf.org; BUSI ITALO
Subject: Re: [PWE3] [mpls-tp] FW: Changes to PW ACH Channel
Typeallocationpolicy

No one asked for IETF rubber stamping. I asked for a mechanism (code point
assignment) that easily implement vendor specific methods. I don't see any
reason why IETF should review and approve a vendor specific method. If IETF
doesn't want to see any vendor specific method, then it doesn't need to
allocate any code points. However, if IETF wants to encourage vendor
specific protocols then it must do so in a way that makes it easy for
vendors to use it.

-Shahram


-----Original Message-----
From: Thomas D. Nadeau [mailto:tom.nadeau@bt.com]
Sent: October-02-08 12:44 PM
To: Shahram Davari; Shane Amante
Cc: l2vpn@ietf.org; mpls@ietf.org; BOCCI Matthew; ccamp@ietf.org;
mpls-tp@ietf.org; Vishwas Manral; pwe3@ietf.org; BUSI ITALO
Subject: Re: [mpls-tp] [PWE3] FW: Changes to PW ACH Channel Type
allocationpolicy



    I agree with %100 of Shane's comments. One bit to add below:

> Hi Shane,
> 
> Please see my response in-line.
> 
> Best regards,
> Shahram
> 
> 
> -----Original Message-----
> From: Shane Amante [mailto:shane@castlepoint.net]
> Sent: October-02-08 10:43 AM
> To: Shahram Davari
> Cc: BUSI ITALO; Vishwas Manral; l2vpn@ietf.org; BOCCI Matthew;
mpls@ietf.org;
> ccamp@ietf.org; mpls-tp@ietf.org; pwe3@ietf.org
> Subject: Re: [mpls-tp] [PWE3] FW: Changes to PW ACH Channel Type
> allocationpolicy
> 
> Shahram Davari wrote:
>> Hi,
>> 
>> I also prefer the method that Wishwas proposed. This has many advantages:
>> 
>> 1) Allows vendors to not expose their proprietary techniques to their
>> competitors.
> 
>  From the POV of an operator, this is actually a substantial disadvantage.
> 
> [Shahram] OTOH it encourages more innovation and differentiation by
vendors.

    That is hogwash. Customers encourage vendors to innovate not standards
bodies. Standards bodies help encourage and foster interoperability of a
common specification. The latter is the important point Shane is making (as
am I and others who are the customers in this equation). We don't want to
encourage proprietary implementations for the sake of proprietary
implementations; we want to encourage them to ultimately interoperate on a
common specification. However, if your goal as a vendor is to create
proprietary implementations you are free to do so, but you do not need the
IETF unless you are looking for some sort of rubber stamp of approval.

    --Tom


  
>> 2) reduces the load of reviewing by IETF and PWE3
> 
> OTOH, the benefit of such reviews by the IETF and PWE3 is when
> "commonality" among similar applications are discovered they can be
> standardized, rather kept proprietary.
> 
> [Shahram] Not if the inventing vendor is not willing to do so.
> 
> 
>> 3) results a faster time to market, since no expert review will be needed
> 
> True, to some extent.  But, IMHO, I would much rather see a *slightly*
> slower process involving a careful expert review and/or IETF consensus
> to make sure we're not: a) unnecessarily duplicating work; and, b) at
> the same time, encouraging more standards-based approach.
> 
> 
>> 4) provides more codepoint space that the ACH channel type
> 
> This is false.  There is no shortage on ACH channel types today.
> [Shahram] You are correct. 16-bit is sufficient enough.
> 
> 
>> 5) only one VCCV ACH channel type needs to be configured in each box for
>> vendor specific filtering
>> 
>> The 2nd method has the first 3 advantages only, and the first method has
none
>> of these advantages.
> 
> 
> Also, let's take a step back here.  Wasn't the whole point with the
> joint ITU-T/IETF effort surrounding MPLS-TP to create an environment in
> which MPLS-TP could seamlessly interoperate within (existing) MPLS
> environments?  I thought a fundamental part of that work is striving
> towards creating a *standards-based* MPLS-TP data-plane, OAM, signaling,
> etc. mechanisms.  IMO, Vishwas' proposal and Matthew's proposal #2 seems
> to run contrary to that goal.
> 
> [Shahram] off course we should all encourage standards methods. But we
should
> provide a fast and reasonable procedure for vendor specific protocols that
> don't affect interoperability. I worry that in first method competitors
may
> vote down code point requests for commercial reasons.
> 
> -shane (speaking only for himself, not as co-chair)
> 
> 
> 




_______________________________________________
pwe3 mailing list
pwe3@ietf.org
https://www.ietf.org/mailman/listinfo/pwe3


_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls


From mpls-bounces@ietf.org  Thu Oct  9 09:09:37 2008
Return-Path: <mpls-bounces@ietf.org>
X-Original-To: mpls-archive@megatron.ietf.org
Delivered-To: ietfarch-mpls-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 2C0C03A6C82;
	Thu,  9 Oct 2008 09:09:37 -0700 (PDT)
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 02ABD28C180;
	Mon,  6 Oct 2008 01:27:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.328
X-Spam-Level: 
X-Spam-Status: No, score=-2.328 tagged_above=-999 required=5 tests=[AWL=0.271, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id Iv67ztV7DnSe; Mon,  6 Oct 2008 01:27:21 -0700 (PDT)
Received: from eci-iron1.ecitele.com (eci-iron1.ecitele.com [147.234.242.117])
	by core3.amsl.com (Postfix) with ESMTP id 9D1E53A69BB;
	Mon,  6 Oct 2008 01:27:19 -0700 (PDT)
Received: from unknown (HELO ILPTAM01.ecitele.com) ([147.234.244.44])
	by eci-iron1.ecitele.com with ESMTP; 06 Oct 2008 10:43:35 +0200
Received: from ilptexch01.ecitele.com ([172.31.244.40]) by
	ILPTAM01.ecitele.com with Microsoft SMTPSVC(6.0.3790.3959); 
	Mon, 6 Oct 2008 10:27:09 +0200
Received: from ILPTMAIL02.ecitele.com ([147.234.244.212]) by
	ilptexch01.ecitele.com ([172.31.244.40]) with mapi;
	Mon, 6 Oct 2008 10:27:08 +0200
From: Alexander Vainshtein <Alexander.Vainshtein@ecitele.com>
To: Maarten Vissers <maarten.vissers@huawei.com>
Date: Mon, 6 Oct 2008 10:27:08 +0200
Thread-Topic: [PWE3] [mpls-tp] FW: Changes to PW ACH Channel
	Typeallocationpolicy
Thread-Index: AckkqLTHdNDdblepSIu2W52R3r7OPAABUvW5AADtmEAAtUWvEAAAXysA
Message-ID: <A3C5DF08D38B6049839A6F553B331C768E242E6565@ILPTMAIL02.ecitele.com>
References: <16a42c48f46e6547a1c3ce65f8fee99a@mail.cph.tpack.net>
	<001701c92788$11a596b0$6d02a8c0@china.huawei.com>
In-Reply-To: <001701c92788$11a596b0$6d02a8c0@china.huawei.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
MIME-Version: 1.0
X-OriginalArrivalTime: 06 Oct 2008 08:27:09.0582 (UTC)
	FILETIME=[5328BAE0:01C9278D]
X-Mailman-Approved-At: Thu, 09 Oct 2008 09:09:34 -0700
Cc: "l2vpn@ietf.org" <l2vpn@ietf.org>,
	"mpls@ietf.org" <mpls@ietf.org>,
	"'Thomas D. Nadeau'" <tom.nadeau@bt.com>,
	Matthew' <Matthew.Bocci@alcatel-lucent.com>,
	"ccamp@ietf.org" <ccamp@ietf.org>, 'Shahram@core3.amsl.com,
	"mpls-tp@ietf.org" <mpls-tp@ietf.org>, 'BOCCI@core3.amsl.com,
	"pwe3@ietf.org" <pwe3@ietf.org>, Davari' <davari@tpack.com>,
	'BUSI ITALO' <Italo.Busi@alcatel-lucent.it>, 'Shane@core3.amsl.com
Subject: Re: [mpls] [PWE3] [mpls-tp] FW: Changes to PW ACH
	Channel	Typeallocationpolicy
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mpls-bounces@ietf.org
Errors-To: mpls-bounces@ietf.org


Maarten and all,
Please see some comments inline below. The unrelated text has been snipped to improve readability.

Regards,
        Sasha
> -----Original Message-----
> From: pwe3-bounces@ietf.org [mailto:pwe3-bounces@ietf.org] On
> Behalf Of Maarten Vissers
> Sent: Monday, October 06, 2008 9:49 AM
> To: 'Shahram Davari'; 'Thomas D. Nadeau'; 'Shane Amante'
> Cc: l2vpn@ietf.org; mpls@ietf.org; 'BOCCI Matthew';
> ccamp@ietf.org; mpls-tp@ietf.org; pwe3@ietf.org; 'BUSI ITALO'
> Subject: Re: [PWE3] [mpls-tp] FW: Changes to PW ACH Channel Type allocation policy
>
> Sharam,
>
> I agree.
>
> In my understanding the PW ACH Channel Type provides the same
> function as the Ethertype in Ethernet networks. IEEE provides a means to buy an
> Ethertype codepoint (http://standards.ieee.org/regauth/ethertype/eth.txt).
> The requesting organization can decide to keep their associated application
> private ("Protocol unavailable.") or to make it public.
>
> As far as I understand this Ethertype allocation policy is an industry
> standard and could be copied for PW ACH Channel Type allocation policy.
>
[Sasha] IMHO and FWIW your description of the IEEE process is somewhat inaccurate.
I am not an expert in the field, and Shahram (and others) will probably provide a much more accurate description
of the process, but still:

1. As you've mentioned, IEEE *SELLS* its Ethertype codepoints - at USD $2,500 per a *PUBLIC* codepoint.
    AFAIK, the IETF does not charge anybody  for its codepoints (hopefully this will not result in any bright ideas:-)

2. There is no such thing as a *PRIVATE* Ethertype codepoint at IEEE  (at least, I did not find any references
    on their Web site). AFAIK, the only private values you can obtain from IEEE are OUIs,
    and you must pay USD $1,650/year per private OUI to maintain privacy (that on top of USD $2,000 per a public OUI)

3. IEEE still requires description of the protocol before it approves your registration request, and it takes at least 90
    days before a new code point is granted. (From my experience when dealing with other SDOs IEEE requires an approved
    protocol spec lacking just the new Ethertype value in order to grant a new Ethertype codepoint.)

On top of all that, the most important issue here is that ACH has never been intended to be a new multiprotocol network layer.
This point has been raised already by the others.

Unfortunately your analogy between the ACH type and Ethertype only strengthens the suspicions that this can easily happen with an over-relaxed codepoint allocation policy.

... snipped to the end...

_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls


From mpls-bounces@ietf.org  Thu Oct  9 09:35:50 2008
Return-Path: <mpls-bounces@ietf.org>
X-Original-To: mpls-archive@megatron.ietf.org
Delivered-To: ietfarch-mpls-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id AEF8B3A6C98;
	Thu,  9 Oct 2008 09:35:50 -0700 (PDT)
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id F340A3A6C6C;
	Thu,  9 Oct 2008 09:35:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.249
X-Spam-Level: 
X-Spam-Status: No, score=-3.249 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, HELO_EQ_FR=0.35, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id Qe1byLLsV36z; Thu,  9 Oct 2008 09:35:48 -0700 (PDT)
Received: from p-mail2.rd.francetelecom.com (p-mail2.rd.francetelecom.com
	[195.101.245.16])
	by core3.amsl.com (Postfix) with ESMTP id 3704A3A6AC0;
	Thu,  9 Oct 2008 09:35:47 -0700 (PDT)
Received: from FTRDMEL2.rd.francetelecom.fr ([10.193.117.153]) by
	ftrdsmtp2.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 9 Oct 2008 18:36:27 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Thu, 9 Oct 2008 18:36:26 +0200
Message-ID: <7DBAFEC6A76F3E42817DF1EBE64CB02605EA9DB9@ftrdmel2>
In-Reply-To: <001601c92786$bfe979a0$6d02a8c0@china.huawei.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [mpls] [PWE3] [mpls-tp] FW: Changes to PW ACH Channel
	Typeallocationpolicy
Thread-Index: AckkqLTHdNDdblepSIu2W52R3r7OPAAC8OmkALQvDPAAqc+IYA==
References: <C50AC39D.C5BD%benjamin.niven-jenkins@bt.com>
	<001601c92786$bfe979a0$6d02a8c0@china.huawei.com>
From: <julien.meuric@orange-ftgroup.com>
To: <maarten.vissers@huawei.com>
X-OriginalArrivalTime: 09 Oct 2008 16:36:27.0212 (UTC)
	FILETIME=[2CE8D0C0:01C92A2D]
Cc: l2vpn@ietf.org, mpls@ietf.org, ccamp@ietf.org, pwe3@ietf.org,
	mpls-tp@ietf.org
Subject: Re: [mpls] [PWE3] [mpls-tp] FW: Changes to PW ACH Channel
	Typeallocationpolicy
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mpls-bounces@ietf.org
Errors-To: mpls-bounces@ietf.org

Hi Maarten.

That might be true sometimes, but the IETF allocation policy is not the
limiting factor in that kind of processes... ;-)

Regards,

Julien


-----Original Message-----
From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf Of
Maarten Vissers

[...]

The use of NT devices to support new (non standard) services not only
allows
differentiation by vendors, but also differentiation by operators.
Operators
wanting to differentiate their service offerings can ask a NT device
vendor
to add their operator specific service to the NT device.

Regards,
Maarten
_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls


From mpls-bounces@ietf.org  Mon Oct 13 23:42:45 2008
Return-Path: <mpls-bounces@ietf.org>
X-Original-To: mpls-archive@megatron.ietf.org
Delivered-To: ietfarch-mpls-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id D49CA3A69B5;
	Mon, 13 Oct 2008 23:42:45 -0700 (PDT)
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 5B21B3A69B5
	for <mpls@core3.amsl.com>; Mon, 13 Oct 2008 23:42:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id OrLeW-Rr1Ijg for <mpls@core3.amsl.com>;
	Mon, 13 Oct 2008 23:42:44 -0700 (PDT)
Received: from neo.viciousnest.net (neo.viciousnest.net [192.71.80.124])
	by core3.amsl.com (Postfix) with ESMTP id 8C6C33A676A
	for <mpls@ietf.org>; Mon, 13 Oct 2008 23:42:44 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1])
	by neo.viciousnest.net (Postfix) with ESMTP id 5020B4326B
	for <mpls@ietf.org>; Tue, 14 Oct 2008 08:42:41 +0200 (CEST)
Received: from neo.viciousnest.net ([127.0.0.1])
	by localhost (neo [127.0.0.1]) (amavisd-new, port 10024) with ESMTP
	id 16676-02 for <mpls@ietf.org>; Tue, 14 Oct 2008 08:42:39 +0200 (CEST)
Received: from [10.130.0.119] (2.234.241.83.in-addr.dgcsystems.net
	[83.241.234.2])
	by neo.viciousnest.net (Postfix) with ESMTP id 46F4E43240
	for <mpls@ietf.org>; Tue, 14 Oct 2008 08:42:37 +0200 (CEST)
Message-ID: <48F43F55.3020403@pi.nu>
Date: Tue, 14 Oct 2008 08:42:29 +0200
From: Loa Andersson <loa@pi.nu>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
To: "mpls@ietf.org" <mpls@ietf.org>
References: <48DAC28F.9010308@pi.nu>
In-Reply-To: <48DAC28F.9010308@pi.nu>
X-Enigmail-Version: 0.95.7
X-Virus-Scanned: by amavisd-new at viciousnest.net
Subject: Re: [mpls] wg LC on draft-ietf-mpls-ldp-end-of-lib-01.txt
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mpls-bounces@ietf.org
Errors-To: mpls-bounces@ietf.org

All,

this would have been a message to close the wg last call.

However, we have not received any comments, not even a "this is
OK" message. Hence I talked to a few people to look at the draft
and as this will take a few days, we invite further comments
from the working group.

Please send your comments before eob Oct 24.

Loa and George


Loa Andersson wrote
> Working group,
> 
> this is to initiate a two week working group last call on
> 
> draft-ietf-mpls-ldp-end-of-lib-01.txt
> 
> Please send your comment to the mpls working group mailing list
> or to the working group co-chairs.
> 
> 
> Loa and George
> 


-- 
Loa Andersson

Principal Networking Architect
Acreo AB                           phone:  +46 8 632 77 14
Isafjordsgatan 22                  mobile: +46 739 81 21 64
Kista, Sweden                      email:  loa.andersson@acreo.se
                                           loa@pi.nu
_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls


From mpls-bounces@ietf.org  Fri Oct 17 07:15:02 2008
Return-Path: <mpls-bounces@ietf.org>
X-Original-To: mpls-archive@megatron.ietf.org
Delivered-To: ietfarch-mpls-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 93D223A683C;
	Fri, 17 Oct 2008 07:15:02 -0700 (PDT)
X-Original-To: mpls@lists.ietf.org
Delivered-To: mpls@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0)
	id 1FBF23A683C; Fri, 17 Oct 2008 07:15:01 -0700 (PDT)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20081017141502.1FBF23A683C@core3.amsl.com>
Date: Fri, 17 Oct 2008 07:15:02 -0700 (PDT)
Cc: mpls@lists.ietf.org
Subject: [mpls] I-D Action:draft-ietf-mpls-cosfield-def-05.txt
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=subscribe>
Sender: mpls-bounces@ietf.org
Errors-To: mpls-bounces@ietf.org


--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Multiprotocol Label Switching Working Group of the IETF.


	Title           : "EXP field" renamed to "Traffic Class field"
	Author(s)       : L. Andersson, R. Asati
	Filename        : draft-ietf-mpls-cosfield-def-05.txt
	Pages           : 18
	Date            : 2008-10-17

The early MPLS documents defined the form of the MPLS Label Stack
entry.  This include a three bit field called the "EXP field".  The
exact use of this field was not defined by these documents, except to
state that it was to be "reserved for experimental use".

Although the intended use of the EXP field was as a "Class of
Service" field, it was not named the "Class of Service" (CoS) field
by these early documents because the use of such a CoS field was not
considered to be sufficiently defined.  Today a number of standards
documents define its usage as a CoS field. .

To avoid misunderstanding about how this field may be used, it has
become increasingly necessary to rename this field.  This document
changes the name of the field to the "Traffic Class field" ("TC
field".)  In doing so it also updates documents that define the
current use of the EXP this field.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-mpls-cosfield-def-05.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Message/External-body;
	name="draft-ietf-mpls-cosfield-def-05.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2008-10-17071359.I-D@ietf.org>


--NextPart
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls

--NextPart--


From mpls-bounces@ietf.org  Fri Oct 17 15:23:01 2008
Return-Path: <mpls-bounces@ietf.org>
X-Original-To: mpls-archive@megatron.ietf.org
Delivered-To: ietfarch-mpls-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id AFBE128C139;
	Fri, 17 Oct 2008 15:23:01 -0700 (PDT)
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id F260A3A6B2F
	for <mpls@core3.amsl.com>; Fri, 17 Oct 2008 15:22:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.102
X-Spam-Level: 
X-Spam-Status: No, score=-17.102 tagged_above=-999 required=5
	tests=[AWL=-0.103, BAYES_00=-2.599, J_CHICKENPOX_93=0.6,
	USER_IN_DEF_WHITELIST=-15]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id ptEo+wAWnWo3 for <mpls@core3.amsl.com>;
	Fri, 17 Oct 2008 15:22:59 -0700 (PDT)
Received: from bosco.isi.edu (bosco.isi.edu [128.9.168.207])
	by core3.amsl.com (Postfix) with ESMTP id 1C6A328C0D6
	for <mpls@lists.ietf.org>; Fri, 17 Oct 2008 15:22:59 -0700 (PDT)
Received: by bosco.isi.edu (Postfix, from userid 70)
	id D814C168CAC; Fri, 17 Oct 2008 15:24:03 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Message-Id: <20081017222403.D814C168CAC@bosco.isi.edu>
Date: Fri, 17 Oct 2008 15:24:03 -0700 (PDT)
Cc: mpls@lists.ietf.org, rfc-editor@rfc-editor.org
Subject: [mpls] RFC 5330 on A Link-Type sub-TLV to Convey the Number of
	Traffic Engineering Label Switched Paths Signalled with Zero
	Reserved Bandwidth across a Link
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=subscribe>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mpls-bounces@ietf.org
Errors-To: mpls-bounces@ietf.org


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

        
        RFC 5330

        Title:      A Link-Type sub-TLV to Convey 
                    the Number of Traffic Engineering Label 
                    Switched Paths Signalled with Zero Reserved 
                    Bandwidth across a Link 
        Author:     JP. Vasseur, Ed.,
                    M. Meyer, K. Kumaki,
                    A. Bonda
        Status:     Standards Track
        Date:       October 2008
        Mailbox:    jpv@cisco.com, 
                    matthew.meyer@bt.com, 
                    ke-kumaki@kddi.com,
                    alberto.tempiabonda@telecomitalia.it
        Pages:      8
        Characters: 15730
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-mpls-number-0-bw-te-lsps-12.txt

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

Several Link-type sub-Type-Length-Values (sub-TLVs) have been defined
for Open Shortest Path First (OSPF) and Intermediate System to
Intermediate System (IS-IS) in the context of Multiprotocol Label
Switching (MPLS) Traffic Engineering (TE), in order to advertise some
link characteristics such as the available bandwidth, traffic
engineering metric, administrative group, and so on.  By making
statistical assumptions about the aggregated traffic carried onto a
set of TE Label Switched Paths (LSPs) signalled with zero bandwidth
(referred to as "unconstrained TE LSP" in this document), algorithms
can be designed to load balance (existing or newly configured)
unconstrained TE LSP across a set of equal cost paths.  This requires
knowledge of the number of unconstrained TE LSPs signalled across a link.
This document specifies a new Link-type
Traffic Engineering sub-TLV used to advertise the number of
unconstrained TE LSPs signalled across a link.  [STANDARDS TRACK]

This document is a product of the Multiprotocol Label Switching Working Group of the IETF.

This is now a Proposed Standard Protocol.

STANDARDS TRACK: This document specifies an Internet standards track
protocol for the Internet community,and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Internet
Official Protocol Standards (STD 1) for the standardization state and
status of this protocol.  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/rfcsearch.html.
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
USC/Information Sciences Institute


_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls


From mpls-bounces@ietf.org  Sun Oct 19 14:40:51 2008
Return-Path: <mpls-bounces@ietf.org>
X-Original-To: mpls-archive@megatron.ietf.org
Delivered-To: ietfarch-mpls-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 6C6233A6809;
	Sun, 19 Oct 2008 14:40:51 -0700 (PDT)
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 194F43A6809
	for <mpls@core3.amsl.com>; Sun, 19 Oct 2008 14:40:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id DUWlHOPlYuUZ for <mpls@core3.amsl.com>;
	Sun, 19 Oct 2008 14:40:49 -0700 (PDT)
Received: from neo.viciousnest.net (neo.viciousnest.net [192.71.80.124])
	by core3.amsl.com (Postfix) with ESMTP id 0326E3A67CC
	for <mpls@ietf.org>; Sun, 19 Oct 2008 14:40:46 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1])
	by neo.viciousnest.net (Postfix) with ESMTP id 722083CF2;
	Sun, 19 Oct 2008 23:41:56 +0200 (CEST)
Received: from neo.viciousnest.net ([127.0.0.1])
	by localhost (neo [127.0.0.1]) (amavisd-new, port 10024) with ESMTP
	id 12493-01; Sun, 19 Oct 2008 23:41:53 +0200 (CEST)
Received: from [207.226.254.130] (unknown [207.226.254.130])
	by neo.viciousnest.net (Postfix) with ESMTP id 666773C9C;
	Sun, 19 Oct 2008 23:41:52 +0200 (CEST)
Message-ID: <48FBA99C.5070706@pi.nu>
Date: Sun, 19 Oct 2008 23:41:48 +0200
From: Loa Andersson <loa@pi.nu>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
To: "mpls@ietf.org" <mpls@ietf.org>
References: <20081017141502.1FBF23A683C@core3.amsl.com>
In-Reply-To: <20081017141502.1FBF23A683C@core3.amsl.com>
X-Enigmail-Version: 0.95.7
X-Virus-Scanned: by amavisd-new at viciousnest.net
Subject: Re: [mpls] I-D Action:draft-ietf-mpls-cosfield-def-05.txt
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mpls-bounces@ietf.org
Errors-To: mpls-bounces@ietf.org

WG,

I've republished the the draft-ietf-mpls-cosfield-def after
wg last call.

The following changes has been made:

Rajiv has been added as an author, since that is how thins
are

the former EXP field are now call Traffic Class field as per
earlier consensus

we have reserved the name T-LSP, with the same meaning as E-LSP

a lot of smaller editorial changes made

We have not change name of the file, it is still
draft-ietf-mpls-cosfield-def.

To my co-chair, this should be ready to send to the IESG :)

/Loa

Internet-Drafts@ietf.org wrote:
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
> This draft is a work item of the Multiprotocol Label Switching Working Group of the IETF.
> 
> 
> 	Title           : "EXP field" renamed to "Traffic Class field"
> 	Author(s)       : L. Andersson, R. Asati
> 	Filename        : draft-ietf-mpls-cosfield-def-05.txt
> 	Pages           : 18
> 	Date            : 2008-10-17
> 
> The early MPLS documents defined the form of the MPLS Label Stack
> entry.  This include a three bit field called the "EXP field".  The
> exact use of this field was not defined by these documents, except to
> state that it was to be "reserved for experimental use".
> 
> Although the intended use of the EXP field was as a "Class of
> Service" field, it was not named the "Class of Service" (CoS) field
> by these early documents because the use of such a CoS field was not
> considered to be sufficiently defined.  Today a number of standards
> documents define its usage as a CoS field. .
> 
> To avoid misunderstanding about how this field may be used, it has
> become increasingly necessary to rename this field.  This document
> changes the name of the field to the "Traffic Class field" ("TC
> field".)  In doing so it also updates documents that define the
> current use of the EXP this field.
> 
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ietf-mpls-cosfield-def-05.txt
> 
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
> 
> Below is the data which will enable a MIME compliant mail reader
> implementation to automatically retrieve the ASCII version of the
> Internet-Draft.
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> I-D-Announce mailing list
> I-D-Announce@ietf.org
> https://www.ietf.org/mailman/listinfo/i-d-announce
> Internet-Draft directories: http://www.ietf.org/shadow.html
> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


-- 
Loa Andersson

Principal Networking Architect
Acreo AB                           phone:  +46 8 632 77 14
Isafjordsgatan 22                  mobile: +46 739 81 21 64
Kista, Sweden                      email:  loa.andersson@acreo.se
                                           loa@pi.nu

_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls


From mpls-bounces@ietf.org  Mon Oct 20 08:43:39 2008
Return-Path: <mpls-bounces@ietf.org>
X-Original-To: mpls-archive@megatron.ietf.org
Delivered-To: ietfarch-mpls-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id AF52D3A6AB4;
	Mon, 20 Oct 2008 08:43:39 -0700 (PDT)
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id DD98C3A67D7;
	Mon, 20 Oct 2008 08:43:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.038
X-Spam-Level: 
X-Spam-Status: No, score=-2.038 tagged_above=-999 required=5 tests=[AWL=0.211, 
	BAYES_00=-2.599, HELO_EQ_FR=0.35]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id zrXD9esMSIep; Mon, 20 Oct 2008 08:43:37 -0700 (PDT)
Received: from smail5.alcatel.fr (smail5.alcatel.fr [64.208.49.27])
	by core3.amsl.com (Postfix) with ESMTP id DCC533A67E4;
	Mon, 20 Oct 2008 08:43:35 -0700 (PDT)
Received: from FRVELSBHS02.ad2.ad.alcatel.com (frvelsbhs02.ad2.ad.alcatel.com
	[155.132.6.74])
	by smail5.alcatel.fr (8.13.8/8.13.8/ICT) with ESMTP id m9KFikQ1004076; 
	Mon, 20 Oct 2008 17:44:46 +0200
Received: from FRVELSMBS11.ad2.ad.alcatel.com ([155.132.6.33]) by
	FRVELSBHS02.ad2.ad.alcatel.com with Microsoft
	SMTPSVC(6.0.3790.2499); Mon, 20 Oct 2008 17:44:46 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Mon, 20 Oct 2008 17:44:42 +0200
Message-ID: <0458D2EE0C36744BABB36BE37805C29A02B9F5B6@FRVELSMBS11.ad2.ad.alcatel.com>
In-Reply-To: <7DBAFEC6A76F3E42817DF1EBE64CB02605EA9DB9@ftrdmel2>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [PWE3] [mpls] [mpls-tp] FW: Changes to PW ACH
	ChannelTypeallocationpolicy
Thread-Index: AckkqLTHdNDdblepSIu2W52R3r7OPAAC8OmkALQvDPAAqc+IYAInM/ww
References: <C50AC39D.C5BD%benjamin.niven-jenkins@bt.com><001601c92786$bfe979a0$6d02a8c0@china.huawei.com>
	<7DBAFEC6A76F3E42817DF1EBE64CB02605EA9DB9@ftrdmel2>
From: "BOCCI Matthew" <Matthew.Bocci@alcatel-lucent.com>
To: <pwe3@ietf.org>, <mpls@ietf.org>, <ccamp@ietf.org>, <mpls-tp@ietf.org>
X-OriginalArrivalTime: 20 Oct 2008 15:44:46.0431 (UTC)
	FILETIME=[C73E6EF0:01C932CA]
X-Scanned-By: MIMEDefang 2.57 on 155.132.188.13
Subject: Re: [mpls] [PWE3] [mpls-tp] FW: Changes to PW ACH
	ChannelTypeallocationpolicy
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: pwe3@ietf.org
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mpls-bounces@ietf.org
Errors-To: mpls-bounces@ietf.org

It is not clear that there is rough consensus for changing the
allocation policy for the ACH channel type to be either expert review or
first come first served or any of the other proposed options.
Nevertheless, there are a significant number of participants who would
like to be able to develop and test proprietary ACH protocols prior to
any proposal for a standardised function being made.

We would therefore like to propose the following way forward. This is to
allocate a small range (say 16) of Experimental code points. These would
follow the rules of RFC3692, should be disabled by default, and mapping
of a code point to any specific function must be configurable. The
remainder of the channel type registry would remain as IETF consensus.

Please reply with any comments to the PWE3 list only.

Regards

Matthew

> -----Original Message-----
> From: pwe3-bounces@ietf.org [mailto:pwe3-bounces@ietf.org] On 
> Behalf Of julien.meuric@orange-ftgroup.com
> Sent: 09 October 2008 17:36
> To: maarten.vissers@huawei.com
> Cc: l2vpn@ietf.org; mpls@ietf.org; ccamp@ietf.org; 
> pwe3@ietf.org; mpls-tp@ietf.org
> Subject: Re: [PWE3] [mpls] [mpls-tp] FW: Changes to PW ACH 
> ChannelTypeallocationpolicy
> 
> Hi Maarten.
> 
> That might be true sometimes, but the IETF allocation policy 
> is not the limiting factor in that kind of processes... ;-)
> 
> Regards,
> 
> Julien
> 
> 
> -----Original Message-----
> From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On 
> Behalf Of Maarten Vissers
> 
> [...]
> 
> The use of NT devices to support new (non standard) services 
> not only allows differentiation by vendors, but also 
> differentiation by operators.
> Operators
> wanting to differentiate their service offerings can ask a NT 
> device vendor to add their operator specific service to the NT device.
> 
> Regards,
> Maarten
> _______________________________________________
> pwe3 mailing list
> pwe3@ietf.org
> https://www.ietf.org/mailman/listinfo/pwe3
> 
_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls


From mpls-bounces@ietf.org  Mon Oct 20 13:52:01 2008
Return-Path: <mpls-bounces@ietf.org>
X-Original-To: mpls-archive@megatron.ietf.org
Delivered-To: ietfarch-mpls-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 4B7453A6924;
	Mon, 20 Oct 2008 13:52:01 -0700 (PDT)
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 33E603A6924
	for <mpls@core3.amsl.com>; Mon, 20 Oct 2008 13:52:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id dLVP3iqP0NYF for <mpls@core3.amsl.com>;
	Mon, 20 Oct 2008 13:51:59 -0700 (PDT)
Received: from neo.viciousnest.net (neo.viciousnest.net [192.71.80.124])
	by core3.amsl.com (Postfix) with ESMTP id 359133A6839
	for <mpls@ietf.org>; Mon, 20 Oct 2008 13:51:59 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1])
	by neo.viciousnest.net (Postfix) with ESMTP id C4B381B3F4;
	Mon, 20 Oct 2008 22:53:10 +0200 (CEST)
Received: from neo.viciousnest.net ([127.0.0.1])
	by localhost (neo [127.0.0.1]) (amavisd-new, port 10024) with ESMTP
	id 17299-08; Mon, 20 Oct 2008 22:53:09 +0200 (CEST)
Received: from [207.226.254.242] (unknown [207.226.254.242])
	by neo.viciousnest.net (Postfix) with ESMTP id 8DCD11B3F1;
	Mon, 20 Oct 2008 22:53:05 +0200 (CEST)
Message-ID: <48FCEFAE.5050400@pi.nu>
Date: Mon, 20 Oct 2008 22:53:02 +0200
From: Loa Andersson <loa@pi.nu>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
To: "mpls@ietf.org" <mpls@ietf.org>
X-Enigmail-Version: 0.95.7
X-Virus-Scanned: by amavisd-new at viciousnest.net
Cc: BOCCI Matthew <Matthew.Bocci@alcatel-lucent.co.uk>,
	David Ward <dward@cisco.com>, Ross Callon <rcallon@juniper.net>,
	"'W. Mark Townsley'" <townsley@cisco.com>,
	Stewart Bryant <stbryant@cisco.com>
Subject: [mpls] time to request slots on the MPLS wg agenda in Minneapolis
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mpls-bounces@ietf.org
Errors-To: mpls-bounces@ietf.org

Working group,

there will be two MPLS wg meetings in Minneapolis also

- first a "traditional" MPLS wg meeting:

   MPLS Session 1 (2.5 hours)
   Tuesday, Morning Session I 0900-1130
   Room Name: Meeting Room

- second a meeting (joint with PWE3) for the
  MPLS-TP work:

   MPLS Session 2 (2 hours)
   Wednesday, Afternoon Session I 1300-1500
   Room Name: Meeting Room


I've indicated to the secretariat that we are interested in,
but not requiring, the second slot to be 2.5 hours too.

If you need a slot on either of the agendas please send a
mail to the wg chairs, indicating what draft you want the
discuss and how much time you need.

Loa and George



-- 
Loa Andersson

Principal Networking Architect
Acreo AB                           phone:  +46 8 632 77 14
Isafjordsgatan 22                  mobile: +46 739 81 21 64
Kista, Sweden                      email:  loa.andersson@acreo.se
                                           loa@pi.nu
_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls


From mpls-bounces@ietf.org  Mon Oct 20 14:50:58 2008
Return-Path: <mpls-bounces@ietf.org>
X-Original-To: mpls-archive@megatron.ietf.org
Delivered-To: ietfarch-mpls-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id C36E53A6AA3;
	Mon, 20 Oct 2008 14:50:58 -0700 (PDT)
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 33FBF3A6A10
	for <mpls@core3.amsl.com>; Mon, 20 Oct 2008 14:50:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id FU1v-AA+xQbY for <mpls@core3.amsl.com>;
	Mon, 20 Oct 2008 14:50:56 -0700 (PDT)
Received: from neo.viciousnest.net (neo.viciousnest.net [192.71.80.124])
	by core3.amsl.com (Postfix) with ESMTP id 601203A6924
	for <mpls@ietf.org>; Mon, 20 Oct 2008 14:50:56 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1])
	by neo.viciousnest.net (Postfix) with ESMTP id 88C211B3FA;
	Mon, 20 Oct 2008 23:52:05 +0200 (CEST)
Received: from neo.viciousnest.net ([127.0.0.1])
	by localhost (neo [127.0.0.1]) (amavisd-new, port 10024) with ESMTP
	id 18828-07; Mon, 20 Oct 2008 23:52:05 +0200 (CEST)
Received: from [207.226.254.242] (unknown [207.226.254.242])
	by neo.viciousnest.net (Postfix) with ESMTP id B89101B3D9;
	Mon, 20 Oct 2008 23:52:03 +0200 (CEST)
Message-ID: <48FCFD7D.3080306@pi.nu>
Date: Mon, 20 Oct 2008 23:51:57 +0200
From: Loa Andersson <loa@pi.nu>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
To: "mpls@ietf.org" <mpls@ietf.org>
X-Enigmail-Version: 0.95.7
X-Virus-Scanned: by amavisd-new at viciousnest.net
Cc: Ross Callon <rcallon@juniper.net>, David Ward <dward@cisco.com>
Subject: [mpls] last call on three mpls wg documents
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mpls-bounces@ietf.org
Errors-To: mpls-bounces@ietf.org

Working group,

the authors of

draft-ietf-mpls-gmpls-lsp-reroute-02.txt
draft-ietf-mpls-soft-preemption-13.txt
draft-ietf-mpls-3209-patherr-03.txt

has asked that we issue a working group last call on these
document as a group. This mail starts the wg last call.

There has gone quite an effort to align the three document and
to create a coherent structure.

The working group last call will end on Nov 7.

Please send comments to the working group mailing-list or to the
working group co-chairs.

/Loa

-- 
Loa Andersson

Principal Networking Architect
Acreo AB                           phone:  +46 8 632 77 14
Isafjordsgatan 22                  mobile: +46 739 81 21 64
Kista, Sweden                      email:  loa.andersson@acreo.se
                                           loa@pi.nu
_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls


From mpls-bounces@ietf.org  Tue Oct 21 13:12:41 2008
Return-Path: <mpls-bounces@ietf.org>
X-Original-To: mpls-archive@megatron.ietf.org
Delivered-To: ietfarch-mpls-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 439523A6BA4;
	Tue, 21 Oct 2008 13:12:41 -0700 (PDT)
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 4ED493A6BA4
	for <mpls@core3.amsl.com>; Tue, 21 Oct 2008 13:12:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id tjc4HVvZe-HN for <mpls@core3.amsl.com>;
	Tue, 21 Oct 2008 13:12:38 -0700 (PDT)
Received: from neo.viciousnest.net (neo.viciousnest.net [192.71.80.124])
	by core3.amsl.com (Postfix) with ESMTP id 7DCCB3A6BA3
	for <mpls@ietf.org>; Tue, 21 Oct 2008 13:12:38 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1])
	by neo.viciousnest.net (Postfix) with ESMTP id 08CBF1B405;
	Tue, 21 Oct 2008 22:13:52 +0200 (CEST)
Received: from neo.viciousnest.net ([127.0.0.1])
	by localhost (neo [127.0.0.1]) (amavisd-new, port 10024) with ESMTP
	id 26420-05; Tue, 21 Oct 2008 22:13:50 +0200 (CEST)
Received: from [207.226.254.46] (unknown [207.226.254.46])
	by neo.viciousnest.net (Postfix) with ESMTP id E41F21B3F7;
	Tue, 21 Oct 2008 22:13:45 +0200 (CEST)
Message-ID: <48FE37F1.8050709@pi.nu>
Date: Tue, 21 Oct 2008 22:13:37 +0200
From: Loa Andersson <loa@pi.nu>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
To: "mpls@ietf.org" <mpls@ietf.org>
X-Enigmail-Version: 0.95.7
X-Virus-Scanned: by amavisd-new at viciousnest.net
Cc: Ross Callon <rcallon@juniper.net>, David Ward <dward@cisco.com>
Subject: [mpls] draft-dasmith-mpls-ip-options-01.txt as a WG doc?
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mpls-bounces@ietf.org
Errors-To: mpls-bounces@ietf.org

Working Group,

we have been asked to adopt draft-dasmith-mpls-ip-options-01.txt
as a WG doc.

This is to start a two week poll. Please send your comments on
whether you think this is ready to become a wg document.

George and Loa

-- 
Loa Andersson

Principal Networking Architect
Acreo AB                           phone:  +46 8 632 77 14
Isafjordsgatan 22                  mobile: +46 739 81 21 64
Kista, Sweden                      email:  loa.andersson@acreo.se
                                           loa@pi.nu
_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls


From mpls-bounces@ietf.org  Wed Oct 22 11:27:49 2008
Return-Path: <mpls-bounces@ietf.org>
X-Original-To: mpls-archive@megatron.ietf.org
Delivered-To: ietfarch-mpls-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 3F5F73A6952;
	Wed, 22 Oct 2008 11:27:49 -0700 (PDT)
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 90AA73A6952
	for <mpls@core3.amsl.com>; Wed, 22 Oct 2008 11:27:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id os-UwhAmwH3o for <mpls@core3.amsl.com>;
	Wed, 22 Oct 2008 11:27:46 -0700 (PDT)
Received: from sj-iport-1.cisco.com (sj-iport-1.cisco.com [171.71.176.70])
	by core3.amsl.com (Postfix) with ESMTP id C97AD3A68B6
	for <mpls@ietf.org>; Wed, 22 Oct 2008 11:27:46 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,465,1220227200"; d="scan'208";a="94701973"
Received: from sj-dkim-2.cisco.com ([171.71.179.186])
	by sj-iport-1.cisco.com with ESMTP; 22 Oct 2008 18:28:51 +0000
Received: from sj-core-1.cisco.com (sj-core-1.cisco.com [171.71.177.237])
	by sj-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id m9MISpFJ019880; 
	Wed, 22 Oct 2008 11:28:51 -0700
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com
	[128.107.191.63])
	by sj-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m9MISp8C023027;
	Wed, 22 Oct 2008 18:28:51 GMT
Received: from xmb-sjc-225.amer.cisco.com ([128.107.191.38]) by
	xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 22 Oct 2008 11:28:50 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Wed, 22 Oct 2008 11:28:48 -0700
Message-ID: <0079EA505DB7BF48BE3D565D16ED55F8077B797E@xmb-sjc-225.amer.cisco.com>
In-Reply-To: <48FE37F1.8050709@pi.nu>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [mpls] draft-dasmith-mpls-ip-options-01.txt as a WG doc?
Thread-Index: AckzubPpQW3DzzkMRuyWcxIiNfWNWwAukNPg
References: <48FE37F1.8050709@pi.nu>
From: "Kenny Hong (kehong)" <kehong@cisco.com>
To: "Loa Andersson" <loa@pi.nu>, <mpls@ietf.org>
X-OriginalArrivalTime: 22 Oct 2008 18:28:50.0788 (UTC)
	FILETIME=[07C39A40:01C93474]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=948; t=1224700131; x=1225564131;
	c=relaxed/simple; s=sjdkim2002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=kehong@cisco.com;
	z=From:=20=22Kenny=20Hong=20(kehong)=22=20<kehong@cisco.com>
	|Subject:=20RE=3A=20[mpls]=20draft-dasmith-mpls-ip-options-
	01.txt=20as=20a=20WG=20doc? |Sender:=20;
	bh=gkigqSNqgph6LwC/LA5uJfNPNEeijTDzFWXmQIr3h1M=;
	b=rhww6qSKi0j+Fu3Z630za8dxg52ll93932oTqaPSv47gG1XepXT666kyJm
	/kZWl22pMUrGrvT49tF5ueDLb3C39f57Xib9/CA3H+kGHkZCp/Zyqzo3oozS
	W4yOk6p3On;
Authentication-Results: sj-dkim-2; header.From=kehong@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim2002 verified; ); 
Cc: Ross Callon <rcallon@juniper.net>, David Ward <dward@cisco.com>
Subject: Re: [mpls] draft-dasmith-mpls-ip-options-01.txt as a WG doc?
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mpls-bounces@ietf.org
Errors-To: mpls-bounces@ietf.org

yes 

-----Original Message-----
From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf Of
Loa Andersson
Sent: Tuesday, October 21, 2008 3:14 PM
To: mpls@ietf.org
Cc: Ross Callon; David Ward
Subject: [mpls] draft-dasmith-mpls-ip-options-01.txt as a WG doc?

Working Group,

we have been asked to adopt draft-dasmith-mpls-ip-options-01.txt
as a WG doc.

This is to start a two week poll. Please send your comments on whether
you think this is ready to become a wg document.

George and Loa

--
Loa Andersson

Principal Networking Architect
Acreo AB                           phone:  +46 8 632 77 14
Isafjordsgatan 22                  mobile: +46 739 81 21 64
Kista, Sweden                      email:  loa.andersson@acreo.se
                                           loa@pi.nu
_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls
_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls


From mpls-bounces@ietf.org  Wed Oct 22 13:26:56 2008
Return-Path: <mpls-bounces@ietf.org>
X-Original-To: mpls-archive@megatron.ietf.org
Delivered-To: ietfarch-mpls-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 473F628C138;
	Wed, 22 Oct 2008 13:26:56 -0700 (PDT)
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id AE76028C142
	for <mpls@core3.amsl.com>; Wed, 22 Oct 2008 13:26:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[AWL=0.000, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id f1eefr-D4lyC for <mpls@core3.amsl.com>;
	Wed, 22 Oct 2008 13:26:54 -0700 (PDT)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140])
	by core3.amsl.com (Postfix) with ESMTP id 7FA9628C0FC
	for <mpls@ietf.org>; Wed, 22 Oct 2008 13:26:53 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,466,1220227200"; d="scan'208";a="23443379"
Received: from ams-dkim-2.cisco.com ([144.254.224.139])
	by ams-iport-1.cisco.com with ESMTP; 22 Oct 2008 20:28:05 +0000
Received: from ams-core-1.cisco.com (ams-core-1.cisco.com [144.254.224.150])
	by ams-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id m9MKS5Wv022750; 
	Wed, 22 Oct 2008 22:28:05 +0200
Received: from xbh-ams-332.emea.cisco.com (xbh-ams-332.cisco.com
	[144.254.231.87])
	by ams-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m9MKS5Cp002905;
	Wed, 22 Oct 2008 20:28:05 GMT
Received: from xfe-ams-332.cisco.com ([144.254.231.73]) by
	xbh-ams-332.emea.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 22 Oct 2008 22:28:05 +0200
Received: from ams-flefauch-8713.cisco.com ([10.55.161.196]) by
	xfe-ams-332.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 22 Oct 2008 22:28:05 +0200
Message-Id: <63B9609E-421C-4F91-BEE5-6ECCED539E71@cisco.com>
From: Francois Le Faucheur IMAP <flefauch@cisco.com>
To: Loa Andersson <loa@pi.nu>
In-Reply-To: <48FE37F1.8050709@pi.nu>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Wed, 22 Oct 2008 22:28:03 +0200
References: <48FE37F1.8050709@pi.nu>
X-Mailer: Apple Mail (2.929.2)
X-OriginalArrivalTime: 22 Oct 2008 20:28:05.0354 (UTC)
	FILETIME=[B037BCA0:01C93484]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=765; t=1224707285; x=1225571285;
	c=relaxed/simple; s=amsdkim2001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=flefauch@cisco.com;
	z=From:=20Francois=20Le=20Faucheur=20IMAP=20<flefauch@cisco.
	com>
	|Subject:=20Re=3A=20[mpls]=20draft-dasmith-mpls-ip-options-
	01.txt=20as=20a=20WG=20doc? |Sender:=20;
	bh=au6nvJ21l4rkc3DYB0cRc92B0OA0usLQz1N9ktXOnJk=;
	b=E5eN6LZfKf0bxmbm9XiZGXkU4DSPKkcCA/eTULXWcKuVf4GeKgR7BaXsj/
	om2Cu+JEoq1DGX7pyWC0BrrZnxWZaq0B/+0a7gYx2XOLhApxddTjVsra91un
	epMJtl7iRo;
Authentication-Results: ams-dkim-2; header.From=flefauch@cisco.com; dkim=pass (
	sig from cisco.com/amsdkim2001 verified; ); 
Cc: Ross Callon <rcallon@juniper.net>, "mpls@ietf.org" <mpls@ietf.org>,
	Francois Le Faucheur IMAP <flefauch@cisco.com>,
	David Ward <dward@cisco.com>
Subject: Re: [mpls] draft-dasmith-mpls-ip-options-01.txt as a WG doc?
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: mpls-bounces@ietf.org
Errors-To: mpls-bounces@ietf.org

support.

On 21 Oct 2008, at 22:13, Loa Andersson wrote:

> Working Group,
>
> we have been asked to adopt draft-dasmith-mpls-ip-options-01.txt
> as a WG doc.
>
> This is to start a two week poll. Please send your comments on
> whether you think this is ready to become a wg document.
>
> George and Loa
>
> -- 
> Loa Andersson
>
> Principal Networking Architect
> Acreo AB                           phone:  +46 8 632 77 14
> Isafjordsgatan 22                  mobile: +46 739 81 21 64
> Kista, Sweden                      email:  loa.andersson@acreo.se
>                                           loa@pi.nu
> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls

_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls


From mpls-bounces@ietf.org  Wed Oct 22 22:37:23 2008
Return-Path: <mpls-bounces@ietf.org>
X-Original-To: mpls-archive@megatron.ietf.org
Delivered-To: ietfarch-mpls-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 5F71F3A685B;
	Wed, 22 Oct 2008 22:37:23 -0700 (PDT)
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 164593A685B
	for <mpls@core3.amsl.com>; Wed, 22 Oct 2008 22:37:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.254
X-Spam-Level: 
X-Spam-Status: No, score=0.254 tagged_above=-999 required=5 tests=[AWL=0.749, 
	BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, 
	RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id buVWwLBtrx6U for <mpls@core3.amsl.com>;
	Wed, 22 Oct 2008 22:37:21 -0700 (PDT)
Received: from szxga04-in.huawei.com (unknown [119.145.14.67])
	by core3.amsl.com (Postfix) with ESMTP id 41EB63A6358
	for <mpls@ietf.org>; Wed, 22 Oct 2008 22:37:21 -0700 (PDT)
Received: from huawei.com (szxga04-in [172.24.2.12])
	by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14
	(built Aug
	8 2006)) with ESMTP id <0K9600601FNUGU@szxga04-in.huawei.com> for
	mpls@ietf.org; Thu, 23 Oct 2008 13:38:18 +0800 (CST)
Received: from huawei.com ([172.24.1.12])
	by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14
	(built Aug
	8 2006)) with ESMTP id <0K96005CBFNU9G@szxga04-in.huawei.com> for
	mpls@ietf.org; Thu, 23 Oct 2008 13:38:18 +0800 (CST)
Received: from R73802B ([10.51.0.16])
	by szxml05-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14
	(built Aug
	8 2006)) with ESMTPA id <0K9600GS6FNLVB@szxml05-in.huawei.com> for
	mpls@ietf.org; Thu, 23 Oct 2008 13:38:18 +0800 (CST)
Date: Wed, 22 Oct 2008 22:38:08 -0700
From: Renwei Li <renweili@huawei.com>
In-reply-to: <48FE37F1.8050709@pi.nu>
To: 'Loa Andersson' <loa@pi.nu>, mpls@ietf.org
Message-id: <006901c934d1$89a7e220$0301a8c0@china.huawei.com>
Organization: Huawei Technologies
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
X-Mailer: Microsoft Office Outlook 11
Thread-index: Ackzuem58kjuQddzRgqs/M+6rT5e0gBFdYlg
References: <48FE37F1.8050709@pi.nu>
Cc: 'Ross Callon' <rcallon@juniper.net>, 'David Ward' <dward@cisco.com>
Subject: Re: [mpls] draft-dasmith-mpls-ip-options-01.txt as a WG doc?
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: renweili@huawei.com
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mpls-bounces@ietf.org
Errors-To: mpls-bounces@ietf.org

Opposed.

This draft imposes a new requirement on LER. But the new requirement has
nothing to do with inter-op. Moreover, the new requirement is really a
matter of local implementation, and doesn't look really like a "MUST"
requirement. 

Regards,

Renwei


> -----Original Message-----
> From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf Of
> Loa Andersson
> Sent: Tuesday, October 21, 2008 1:14 PM
> To: mpls@ietf.org
> Cc: Ross Callon; David Ward
> Subject: [mpls] draft-dasmith-mpls-ip-options-01.txt as a WG doc?
> 
> Working Group,
> 
> we have been asked to adopt draft-dasmith-mpls-ip-options-01.txt
> as a WG doc.
> 
> This is to start a two week poll. Please send your comments on
> whether you think this is ready to become a wg document.
> 
> George and Loa
> 
> --
> Loa Andersson
> 
> Principal Networking Architect
> Acreo AB                           phone:  +46 8 632 77 14
> Isafjordsgatan 22                  mobile: +46 739 81 21 64
> Kista, Sweden                      email:  loa.andersson@acreo.se
>                                            loa@pi.nu
> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls


_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls


From mpls-bounces@ietf.org  Thu Oct 23 07:16:19 2008
Return-Path: <mpls-bounces@ietf.org>
X-Original-To: mpls-archive@megatron.ietf.org
Delivered-To: ietfarch-mpls-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 8D8083A6AD6;
	Thu, 23 Oct 2008 07:16:19 -0700 (PDT)
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 1380A3A6B7B
	for <mpls@core3.amsl.com>; Thu, 23 Oct 2008 07:16:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.496
X-Spam-Level: 
X-Spam-Status: No, score=-6.496 tagged_above=-999 required=5 tests=[AWL=0.103, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id GmJPlnJlAaLa for <mpls@core3.amsl.com>;
	Thu, 23 Oct 2008 07:16:08 -0700 (PDT)
Received: from rtp-iport-2.cisco.com (rtp-iport-2.cisco.com [64.102.122.149])
	by core3.amsl.com (Postfix) with ESMTP id 7647E3A6AD6
	for <mpls@ietf.org>; Thu, 23 Oct 2008 07:16:07 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,470,1220227200"; d="scan'208";a="25406530"
Received: from rtp-dkim-1.cisco.com ([64.102.121.158])
	by rtp-iport-2.cisco.com with ESMTP; 23 Oct 2008 14:17:24 +0000
Received: from rtp-core-1.cisco.com (rtp-core-1.cisco.com [64.102.124.12])
	by rtp-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id m9NEHOqn028263; 
	Thu, 23 Oct 2008 10:17:24 -0400
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com
	[64.102.31.102])
	by rtp-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m9NEHORZ009776;
	Thu, 23 Oct 2008 14:17:24 GMT
Received: from xmb-rtp-212.amer.cisco.com ([64.102.31.111]) by
	xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 23 Oct 2008 10:17:24 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Thu, 23 Oct 2008 10:17:23 -0400
Message-ID: <42591A81B59EA14BAA617596482F65CE05E47778@xmb-rtp-212.amer.cisco.com>
In-Reply-To: <006901c934d1$89a7e220$0301a8c0@china.huawei.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [mpls] draft-dasmith-mpls-ip-options-01.txt as a WG doc?
Thread-Index: Ackzuem58kjuQddzRgqs/M+6rT5e0gBFdYlgABE03NA=
From: "David Smith (djsmith)" <djsmith@cisco.com>
To: <renweili@huawei.com>, "Loa Andersson" <loa@pi.nu>, <mpls@ietf.org>
X-OriginalArrivalTime: 23 Oct 2008 14:17:24.0505 (UTC)
	FILETIME=[120D4090:01C9351A]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=2311; t=1224771444;
	x=1225635444; c=relaxed/simple; s=rtpdkim1001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=djsmith@cisco.com;
	z=From:=20=22David=20Smith=20(djsmith)=22=20<djsmith@cisco.c
	om> |Subject:=20RE=3A=20[mpls]=20draft-dasmith-mpls-ip-options-
	01.txt=20as=20a=20WG=20doc? |Sender:=20
	|To:=20<renweili@huawei.com>,=20=22Loa=20Andersson=22=20<lo
	a@pi.nu>,=20<mpls@ietf.org>;
	bh=6kCnZOhw6p/qrg97XXXd6oym+GNNDYBbFCOArXKyLFc=;
	b=nh99TUrb7g/H7uVkEBp/jW0E1Hb/etZYZsHNBDQF4IkZGCe+5yzxULRQwD
	OUtDTcb6RLIUoNAJN1w1MaV+5CiNLWvYvazGYmZaz/VypkxRN1ESapQkLzT4
	s8QqIsaVGV;
Authentication-Results: rtp-dkim-1; header.From=djsmith@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim1001 verified; ); 
Cc: Ross Callon <rcallon@juniper.net>, David Ward <dward@cisco.com>
Subject: Re: [mpls] draft-dasmith-mpls-ip-options-01.txt as a WG doc?
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mpls-bounces@ietf.org
Errors-To: mpls-bounces@ietf.org


Hi Renwei,

Yes, it's a local LER decision.....but the LER implementation has
consequences on downstream LSRs.

Do you agree that failing to MPLS encapsulate a IPv4 packet simply
because it has an IP option header may be a problem for the downstream
network?

If so, should we not promote a consistent implementation among vendor
LERs via an MPLS WG standard such that when an LER decides "whether to
push an MPLS label stack onto an IP packet, the determination is made
without considering any IP options that may be carried in the IP packet
header"??

Regards,

/dave


-----Original Message-----
From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf Of
Renwei Li
Sent: Thursday, October 23, 2008 1:38 AM
To: 'Loa Andersson'; mpls@ietf.org
Cc: 'Ross Callon'; 'David Ward'
Subject: Re: [mpls] draft-dasmith-mpls-ip-options-01.txt as a WG doc?

Opposed.

This draft imposes a new requirement on LER. But the new requirement has
nothing to do with inter-op. Moreover, the new requirement is really a
matter of local implementation, and doesn't look really like a "MUST"
requirement. 

Regards,

Renwei


> -----Original Message-----
> From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf 
> Of Loa Andersson
> Sent: Tuesday, October 21, 2008 1:14 PM
> To: mpls@ietf.org
> Cc: Ross Callon; David Ward
> Subject: [mpls] draft-dasmith-mpls-ip-options-01.txt as a WG doc?
> 
> Working Group,
> 
> we have been asked to adopt draft-dasmith-mpls-ip-options-01.txt
> as a WG doc.
> 
> This is to start a two week poll. Please send your comments on whether

> you think this is ready to become a wg document.
> 
> George and Loa
> 
> --
> Loa Andersson
> 
> Principal Networking Architect
> Acreo AB                           phone:  +46 8 632 77 14
> Isafjordsgatan 22                  mobile: +46 739 81 21 64
> Kista, Sweden                      email:  loa.andersson@acreo.se
>                                            loa@pi.nu 
> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls


_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls
_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls


From mpls-bounces@ietf.org  Thu Oct 23 19:09:33 2008
Return-Path: <mpls-bounces@ietf.org>
X-Original-To: mpls-archive@megatron.ietf.org
Delivered-To: ietfarch-mpls-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 365A13A63D3;
	Thu, 23 Oct 2008 19:09:33 -0700 (PDT)
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id ED7E33A67A3
	for <mpls@core3.amsl.com>; Thu, 23 Oct 2008 19:09:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.201
X-Spam-Level: 
X-Spam-Status: No, score=0.201 tagged_above=-999 required=5 tests=[AWL=0.696, 
	BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, 
	RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id kkGiDvNG-eBX for <mpls@core3.amsl.com>;
	Thu, 23 Oct 2008 19:09:31 -0700 (PDT)
Received: from szxga01-in.huawei.com (unknown [119.145.14.64])
	by core3.amsl.com (Postfix) with ESMTP id F14D43A6358
	for <mpls@ietf.org>; Thu, 23 Oct 2008 19:09:30 -0700 (PDT)
Received: from huawei.com (szxga01-in [172.24.2.3])
	by szxga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14
	(built Aug
	8 2006)) with ESMTP id <0K9800KK30PSF3@szxga01-in.huawei.com> for
	mpls@ietf.org; Fri, 24 Oct 2008 10:10:41 +0800 (CST)
Received: from huawei.com ([172.24.1.12])
	by szxga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14
	(built Aug
	8 2006)) with ESMTP id <0K9800LZW0PSLO@szxga01-in.huawei.com> for
	mpls@ietf.org; Fri, 24 Oct 2008 10:10:40 +0800 (CST)
Received: from R73802B ([10.51.0.16])
	by szxml05-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14
	(built Aug
	8 2006)) with ESMTPA id <0K9800ID70OP98@szxml05-in.huawei.com> for
	mpls@ietf.org; Fri, 24 Oct 2008 10:10:40 +0800 (CST)
Date: Thu, 23 Oct 2008 19:09:59 -0700
From: Renwei Li <renweili@huawei.com>
In-reply-to: <42591A81B59EA14BAA617596482F65CE05E47778@xmb-rtp-212.amer.cisco.com>
To: "'David Smith (djsmith)'" <djsmith@cisco.com>, 'Loa Andersson' <loa@pi.nu>,
	mpls@ietf.org
Message-id: <009801c9357d$aed57a60$0301a8c0@china.huawei.com>
Organization: Huawei Technologies
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
X-Mailer: Microsoft Office Outlook 11
Thread-index: Ackzuem58kjuQddzRgqs/M+6rT5e0gBFdYlgABE03NAAGUgRQA==
References: <006901c934d1$89a7e220$0301a8c0@china.huawei.com>
	<42591A81B59EA14BAA617596482F65CE05E47778@xmb-rtp-212.amer.cisco.com>
Cc: 'Ross Callon' <rcallon@juniper.net>, 'David Ward' <dward@cisco.com>
Subject: Re: [mpls] draft-dasmith-mpls-ip-options-01.txt as a WG doc?
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: renweili@huawei.com
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mpls-bounces@ietf.org
Errors-To: mpls-bounces@ietf.org

Hi Dave,

I do see your point. But it is really a local implementation issue. With or
without it, LER would still work. It could at most serve as a CLI knob which
can be turned on or off according to whatever someone wants, but it doesn't
look like a requirement for LER. 

> If so, should we not promote a consistent implementation among vendor
> LERs via

It depends on what you mean by "consistent implementation"? If it has an
effect on inter-op for LERs from different vendors, no doubt we should
promote it and I will fully support it. But if it doesn't have anything to
do with inter-op, I am afraid we should not promote it. There are so many
different LERs that have different local implementations inside, but they
are just fine provided they inter-op.

Moreover, when an IP packet has an option, it usually has a reason for
having such an option, and thus expects to be processed along the forwarding
path in the network. In this case, an ingress LER is essentially just one
hop away from the exit LER. The processing of such options on LER should be
no different from on other routers. 

Regards,

Renwei


> -----Original Message-----
> From: David Smith (djsmith) [mailto:djsmith@cisco.com]
> Sent: Thursday, October 23, 2008 7:17 AM
> To: renweili@huawei.com; Loa Andersson; mpls@ietf.org
> Cc: Ross Callon; David Ward
> Subject: RE: [mpls] draft-dasmith-mpls-ip-options-01.txt as a WG doc?
> 
> 
> Hi Renwei,
> 
> Yes, it's a local LER decision.....but the LER implementation has
> consequences on downstream LSRs.
> 
> Do you agree that failing to MPLS encapsulate a IPv4 packet simply
> because it has an IP option header may be a problem for the downstream
> network?
> 
> If so, should we not promote a consistent implementation among vendor
> LERs via an MPLS WG standard such that when an LER decides "whether to
> push an MPLS label stack onto an IP packet, the determination is made
> without considering any IP options that may be carried in the IP packet
> header"??
> 
> Regards,
> 
> /dave
> 
> 
> -----Original Message-----
> From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf Of
> Renwei Li
> Sent: Thursday, October 23, 2008 1:38 AM
> To: 'Loa Andersson'; mpls@ietf.org
> Cc: 'Ross Callon'; 'David Ward'
> Subject: Re: [mpls] draft-dasmith-mpls-ip-options-01.txt as a WG doc?
> 
> Opposed.
> 
> This draft imposes a new requirement on LER. But the new requirement has
> nothing to do with inter-op. Moreover, the new requirement is really a
> matter of local implementation, and doesn't look really like a "MUST"
> requirement.
> 
> Regards,
> 
> Renwei
> 
> 
> > -----Original Message-----
> > From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf
> > Of Loa Andersson
> > Sent: Tuesday, October 21, 2008 1:14 PM
> > To: mpls@ietf.org
> > Cc: Ross Callon; David Ward
> > Subject: [mpls] draft-dasmith-mpls-ip-options-01.txt as a WG doc?
> >
> > Working Group,
> >
> > we have been asked to adopt draft-dasmith-mpls-ip-options-01.txt
> > as a WG doc.
> >
> > This is to start a two week poll. Please send your comments on whether
> 
> > you think this is ready to become a wg document.
> >
> > George and Loa
> >
> > --
> > Loa Andersson
> >
> > Principal Networking Architect
> > Acreo AB                           phone:  +46 8 632 77 14
> > Isafjordsgatan 22                  mobile: +46 739 81 21 64
> > Kista, Sweden                      email:  loa.andersson@acreo.se
> >                                            loa@pi.nu
> > _______________________________________________
> > mpls mailing list
> > mpls@ietf.org
> > https://www.ietf.org/mailman/listinfo/mpls
> 
> 
> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls


_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls


From mpls-bounces@ietf.org  Fri Oct 24 06:30:04 2008
Return-Path: <mpls-bounces@ietf.org>
X-Original-To: mpls-archive@megatron.ietf.org
Delivered-To: ietfarch-mpls-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 2D0403A6B28;
	Fri, 24 Oct 2008 06:30:04 -0700 (PDT)
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 67B3D3A6B28;
	Fri, 24 Oct 2008 06:30:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.729
X-Spam-Level: 
X-Spam-Status: No, score=-5.729 tagged_above=-999 required=5 tests=[AWL=0.520, 
	BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id c-JNYIv58oFh; Fri, 24 Oct 2008 06:30:01 -0700 (PDT)
Received: from mailgw3.ericsson.se (mailgw3.ericsson.se [193.180.251.60])
	by core3.amsl.com (Postfix) with ESMTP id 546B53A6B26;
	Fri, 24 Oct 2008 06:30:01 -0700 (PDT)
Received: from mailgw3.ericsson.se (unknown [127.0.0.1])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	93F2A20F2D; Fri, 24 Oct 2008 15:31:21 +0200 (CEST)
X-AuditID: c1b4fb3c-ae8cfbb0000015b5-6b-4901ce253bc1
Received: from esealmw128.eemea.ericsson.se (unknown [153.88.254.121])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	28E54208E0; Fri, 24 Oct 2008 15:31:17 +0200 (CEST)
Received: from esealmw118.eemea.ericsson.se ([153.88.200.77]) by
	esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 24 Oct 2008 15:31:15 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Fri, 24 Oct 2008 15:31:15 +0200
Message-ID: <93DFCD4B101EB440B5B72997456C5F9402C9B08D@esealmw118.eemea.ericsson.se>
In-Reply-To: <0458D2EE0C36744BABB36BE37805C29A02B9F5B6@FRVELSMBS11.ad2.ad.alcatel.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [mpls-tp] [PWE3] [mpls] FW: Changes to PW
	ACHChannelTypeallocationpolicy
thread-index: AckkqLTHdNDdblepSIu2W52R3r7OPAAC8OmkALQvDPAAqc+IYAInM/wwAMTcVZA=
References: <C50AC39D.C5BD%benjamin.niven-jenkins@bt.com><001601c92786$bfe979a0$6d02a8c0@china.huawei.com><7DBAFEC6A76F3E42817DF1EBE64CB02605EA9DB9@ftrdmel2>
	<0458D2EE0C36744BABB36BE37805C29A02B9F5B6@FRVELSMBS11.ad2.ad.alcatel.com>
From: "Annamaria Fulignoli" <annamaria.fulignoli@ericsson.com>
To: <pwe3@ietf.org>,
	<mpls@ietf.org>,
	<ccamp@ietf.org>,
	<mpls-tp@ietf.org>
X-OriginalArrivalTime: 24 Oct 2008 13:31:15.0398 (UTC)
	FILETIME=[C9F2CE60:01C935DC]
X-Brightmail-Tracker: AAAAAA==
Subject: Re: [mpls] [mpls-tp] [PWE3] FW: Changes to PW
	ACHChannelTypeallocationpolicy
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: mpls-bounces@ietf.org
Errors-To: mpls-bounces@ietf.org

Hi Matthew,

I can support that.

Regards
Annamaria  =


-----Original Message-----
From: mpls-tp-bounces@ietf.org [mailto:mpls-tp-bounces@ietf.org] On Behalf =
Of BOCCI Matthew
Sent: luned=EC 20 ottobre 2008 17.45
To: pwe3@ietf.org; mpls@ietf.org; ccamp@ietf.org; mpls-tp@ietf.org
Subject: Re: [mpls-tp] [PWE3] [mpls] FW: Changes to PW ACHChannelTypealloca=
tionpolicy

It is not clear that there is rough consensus for changing the allocation p=
olicy for the ACH channel type to be either expert review or first come fir=
st served or any of the other proposed options.
Nevertheless, there are a significant number of participants who would like=
 to be able to develop and test proprietary ACH protocols prior to any prop=
osal for a standardised function being made.

We would therefore like to propose the following way forward. This is to al=
locate a small range (say 16) of Experimental code points. These would foll=
ow the rules of RFC3692, should be disabled by default, and mapping of a co=
de point to any specific function must be configurable. The remainder of th=
e channel type registry would remain as IETF consensus.

Please reply with any comments to the PWE3 list only.

Regards

Matthew

_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls


From mpls-bounces@ietf.org  Fri Oct 24 08:49:17 2008
Return-Path: <mpls-bounces@ietf.org>
X-Original-To: mpls-archive@megatron.ietf.org
Delivered-To: ietfarch-mpls-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 4D8D23A69B9;
	Fri, 24 Oct 2008 08:49:17 -0700 (PDT)
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 16CF83A69B9
	for <mpls@core3.amsl.com>; Fri, 24 Oct 2008 08:49:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.516
X-Spam-Level: 
X-Spam-Status: No, score=-6.516 tagged_above=-999 required=5 tests=[AWL=0.083, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id llosF-R1JPyH for <mpls@core3.amsl.com>;
	Fri, 24 Oct 2008 08:49:13 -0700 (PDT)
Received: from sj-iport-5.cisco.com (sj-iport-5.cisco.com [171.68.10.87])
	by core3.amsl.com (Postfix) with ESMTP id C46EA3A6836
	for <mpls@ietf.org>; Fri, 24 Oct 2008 08:49:13 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,479,1220227200"; d="scan'208";a="50322263"
Received: from rtp-dkim-2.cisco.com ([64.102.121.159])
	by sj-iport-5.cisco.com with ESMTP; 24 Oct 2008 15:50:33 +0000
Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13])
	by rtp-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id m9OFoXHW030273; 
	Fri, 24 Oct 2008 11:50:33 -0400
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com
	[64.102.31.102])
	by rtp-core-2.cisco.com (8.13.8/8.13.8) with ESMTP id m9OFoXwK025728;
	Fri, 24 Oct 2008 15:50:33 GMT
Received: from xmb-rtp-212.amer.cisco.com ([64.102.31.111]) by
	xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 24 Oct 2008 11:50:33 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Fri, 24 Oct 2008 11:49:41 -0400
Message-ID: <42591A81B59EA14BAA617596482F65CE05E9E0AF@xmb-rtp-212.amer.cisco.com>
In-Reply-To: <009801c9357d$aed57a60$0301a8c0@china.huawei.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [mpls] draft-dasmith-mpls-ip-options-01.txt as a WG doc?
Thread-Index: Ackzuem58kjuQddzRgqs/M+6rT5e0gBFdYlgABE03NAAGUgRQAAaQlJQ
From: "David Smith (djsmith)" <djsmith@cisco.com>
To: <renweili@huawei.com>, "Loa Andersson" <loa@pi.nu>, <mpls@ietf.org>
X-OriginalArrivalTime: 24 Oct 2008 15:50:33.0300 (UTC)
	FILETIME=[3FA57140:01C935F0]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=5894; t=1224863433;
	x=1225727433; c=relaxed/simple; s=rtpdkim2001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=djsmith@cisco.com;
	z=From:=20=22David=20Smith=20(djsmith)=22=20<djsmith@cisco.c
	om> |Subject:=20RE=3A=20[mpls]=20draft-dasmith-mpls-ip-options-
	01.txt=20as=20a=20WG=20doc? |Sender:=20
	|To:=20<renweili@huawei.com>,=20=22Loa=20Andersson=22=20<lo
	a@pi.nu>,=20<mpls@ietf.org>;
	bh=rg6pVsW6HZfJ5oILAB+c9Tq4i31aP7BqfVRA9/Ddk8k=;
	b=KJq2p1l4EtrfCpu4XUvcSYJtYx61uhGW7flZzKbExAY5CFslVkm3vMOqoi
	9F+F55pyTvGxfGpOwNbH0uIMItYhFm6Cjn5R9N6DpnVH5ClUAIwEGWiigtz9
	XHlrZMHMTc;
Authentication-Results: rtp-dkim-2; header.From=djsmith@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim2001 verified; ); 
Cc: Ross Callon <rcallon@juniper.net>, David Ward <dward@cisco.com>
Subject: Re: [mpls] draft-dasmith-mpls-ip-options-01.txt as a WG doc?
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mpls-bounces@ietf.org
Errors-To: mpls-bounces@ietf.org


Hi Renwei,

Rather than a local LER implementation issue, I'd say this is really a
LER "forwarding issue". And the MPLS WG has defined many standards on
"forwarding issues". Consider RFC3443 (TTL Processing in MPLS Networks)
and RFC3270 (MPLS Support of DiffServ). Our draft complements RFC3443
and RFC3270.

>Moreover, when an IP packet has an option, it usually has a 
>reason for having such an option, and thus expects to be 
>processed along the forwarding path in the network. 

Keep in mind one reason (used by an attacker) may simply be "DoS LSRs".
While the attacker hopes the packet is processed along the forwarding
path, the MPLS network operator expects it to be tunnelled via an LSP. 

>In this case, an ingress LER is essentially just one hop 
>away from the exit LER. The processing of such options on 
>LER should be no different from on other routers

This is not true for IP option packets. For packets w/o IP options this
is true because they are LSP tunnelled from ingress LER to egress LER.
However, for packets "with" IP options this MAY not be true (depending
upon the ingress LER implementation) because such option packets are IP
routed downstream and NOT LSP tunneled. 

I'll argue this is a LER & LSR inter-op issue because the LSRs may not
be carrying BGP routes and, if so, cannot route (unlabelled) transit
packets that were not MPLS encapsulated by the ingress LER. 

For these reasons, I think the MPLS WG needs a well-defined (ingress)
LER forwarding rule to mitigate the risk of IP option packets on MPLS
networks (ie, LSRs). 

Regards,

/dave


-----Original Message-----
From: Renwei Li [mailto:renweili@huawei.com] 
Sent: Thursday, October 23, 2008 10:10 PM
To: David Smith (djsmith); 'Loa Andersson'; mpls@ietf.org
Cc: 'Ross Callon'; 'David Ward'
Subject: RE: [mpls] draft-dasmith-mpls-ip-options-01.txt as a WG doc?

Hi Dave,

I do see your point. But it is really a local implementation issue. With
or without it, LER would still work. It could at most serve as a CLI
knob which can be turned on or off according to whatever someone wants,
but it doesn't look like a requirement for LER. 

> If so, should we not promote a consistent implementation among vendor 
> LERs via

It depends on what you mean by "consistent implementation"? If it has an
effect on inter-op for LERs from different vendors, no doubt we should
promote it and I will fully support it. But if it doesn't have anything
to do with inter-op, I am afraid we should not promote it. There are so
many different LERs that have different local implementations inside,
but they are just fine provided they inter-op.

Moreover, when an IP packet has an option, it usually has a reason for
having such an option, and thus expects to be processed along the
forwarding path in the network. In this case, an ingress LER is
essentially just one hop away from the exit LER. The processing of such
options on LER should be no different from on other routers. 

Regards,

Renwei


> -----Original Message-----
> From: David Smith (djsmith) [mailto:djsmith@cisco.com]
> Sent: Thursday, October 23, 2008 7:17 AM
> To: renweili@huawei.com; Loa Andersson; mpls@ietf.org
> Cc: Ross Callon; David Ward
> Subject: RE: [mpls] draft-dasmith-mpls-ip-options-01.txt as a WG doc?
> 
> 
> Hi Renwei,
> 
> Yes, it's a local LER decision.....but the LER implementation has 
> consequences on downstream LSRs.
> 
> Do you agree that failing to MPLS encapsulate a IPv4 packet simply 
> because it has an IP option header may be a problem for the downstream

> network?
> 
> If so, should we not promote a consistent implementation among vendor 
> LERs via an MPLS WG standard such that when an LER decides "whether to

> push an MPLS label stack onto an IP packet, the determination is made 
> without considering any IP options that may be carried in the IP 
> packet header"??
> 
> Regards,
> 
> /dave
> 
> 
> -----Original Message-----
> From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf 
> Of Renwei Li
> Sent: Thursday, October 23, 2008 1:38 AM
> To: 'Loa Andersson'; mpls@ietf.org
> Cc: 'Ross Callon'; 'David Ward'
> Subject: Re: [mpls] draft-dasmith-mpls-ip-options-01.txt as a WG doc?
> 
> Opposed.
> 
> This draft imposes a new requirement on LER. But the new requirement 
> has nothing to do with inter-op. Moreover, the new requirement is 
> really a matter of local implementation, and doesn't look really like
a "MUST"
> requirement.
> 
> Regards,
> 
> Renwei
> 
> 
> > -----Original Message-----
> > From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf

> > Of Loa Andersson
> > Sent: Tuesday, October 21, 2008 1:14 PM
> > To: mpls@ietf.org
> > Cc: Ross Callon; David Ward
> > Subject: [mpls] draft-dasmith-mpls-ip-options-01.txt as a WG doc?
> >
> > Working Group,
> >
> > we have been asked to adopt draft-dasmith-mpls-ip-options-01.txt
> > as a WG doc.
> >
> > This is to start a two week poll. Please send your comments on 
> > whether
> 
> > you think this is ready to become a wg document.
> >
> > George and Loa
> >
> > --
> > Loa Andersson
> >
> > Principal Networking Architect
> > Acreo AB                           phone:  +46 8 632 77 14
> > Isafjordsgatan 22                  mobile: +46 739 81 21 64
> > Kista, Sweden                      email:  loa.andersson@acreo.se
> >                                            loa@pi.nu 
> > _______________________________________________
> > mpls mailing list
> > mpls@ietf.org
> > https://www.ietf.org/mailman/listinfo/mpls
> 
> 
> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls


_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls


From mpls-bounces@ietf.org  Fri Oct 24 09:07:21 2008
Return-Path: <mpls-bounces@ietf.org>
X-Original-To: mpls-archive@megatron.ietf.org
Delivered-To: ietfarch-mpls-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 5CC183A6A76;
	Fri, 24 Oct 2008 09:07:21 -0700 (PDT)
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 26FF13A6A76
	for <mpls@core3.amsl.com>; Fri, 24 Oct 2008 09:07:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.903
X-Spam-Level: 
X-Spam-Status: No, score=-1.903 tagged_above=-999 required=5 tests=[AWL=0.695, 
	BAYES_00=-2.599, STOX_REPLY_TYPE=0.001]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id lT2ei1ZT59aN for <mpls@core3.amsl.com>;
	Fri, 24 Oct 2008 09:07:16 -0700 (PDT)
Received: from asmtp2.iomartmail.com (asmtp2.iomartmail.com [62.128.201.249])
	by core3.amsl.com (Postfix) with ESMTP id 019253A69B9
	for <mpls@ietf.org>; Fri, 24 Oct 2008 09:07:15 -0700 (PDT)
Received: from asmtp2.iomartmail.com (localhost.localdomain [127.0.0.1])
	by asmtp2.iomartmail.com (8.12.11.20060308/8.12.8) with ESMTP id
	m9OG7CLl007208 for <mpls@ietf.org>; Fri, 24 Oct 2008 17:07:12 +0100
Received: from your029b8cecfe (dsl-sp-81-140-15-32.in-addr.broadbandscope.com
	[81.140.15.32]) (authenticated bits=0)
	by asmtp2.iomartmail.com (8.12.11.20060308/8.12.11) with ESMTP id
	m9OG7AYK007185 for <mpls@ietf.org>; Fri, 24 Oct 2008 17:07:11 +0100
Message-ID: <002801c935f2$9229cae0$0200a8c0@your029b8cecfe>
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: <mpls@ietf.org>
Date: Fri, 24 Oct 2008 17:05:06 +0100
MIME-Version: 1.0
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.3138
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
Subject: [mpls] A BNF specification for RSVP-TE
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Adrian Farrel <adrian@olddog.co.uk>
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: mpls-bounces@ietf.org
Errors-To: mpls-bounces@ietf.org

Hi,

This draft provides a specification of the BNF we already use in RSVP-TE and 
makes it available for use in future RSVP-TE extensions.

I intend asking that this draft progress in the standards process relatively 
soon.

Please review and comment as soon as possible.

Thanks,
Adrian
----- Original Message ----- 
From: <Internet-Drafts@ietf.org>
To: <i-d-announce@ietf.org>
Sent: Friday, October 24, 2008 5:00 PM
Subject: I-D Action:draft-farrel-rtg-common-bnf-06.txt


>A New Internet-Draft is available from the on-line Internet-Drafts 
>directories.
>
> Title           : Reduced Backus-Naur Form (RBNF) A Syntax Used in Various 
> Protocol Specifications
> Author(s)       : A. Farrel
> Filename        : draft-farrel-rtg-common-bnf-06.txt
> Pages           : 12
> Date            : 2008-10-24
>
> Several protocols have been specified using a common variant of the
> Backus-Naur Form (BNF) of representing message syntax. However, there
> is no formal definition of this version of BNF.
>
> There is value in using the same variant of BNF for the set of
> protocols that are commonly used together. This reduces confusion and
> simplifies implementation.
>
> Updating existing documents to use some other variant of BNF that is
> already formally documented would be a substantial piece of work.
>
> This document provides a formal definition of the variant of BNF that
> has been used (that we call Reduced BNF), and makes it available for
> use by new protocols.
>
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-farrel-rtg-common-bnf-06.txt

_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls


From mpls-bounces@ietf.org  Mon Oct 27 15:46:27 2008
Return-Path: <mpls-bounces@ietf.org>
X-Original-To: mpls-archive@megatron.ietf.org
Delivered-To: ietfarch-mpls-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 4D2623A6B9A;
	Mon, 27 Oct 2008 15:46:27 -0700 (PDT)
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 521693A6BB4
	for <mpls@core3.amsl.com>; Mon, 27 Oct 2008 15:46:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.495
X-Spam-Level: 
X-Spam-Status: No, score=-0.495 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, 
	RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id UD5mSW9FIgPq for <mpls@core3.amsl.com>;
	Mon, 27 Oct 2008 15:46:25 -0700 (PDT)
Received: from szxga03-in.huawei.com (unknown [119.145.14.66])
	by core3.amsl.com (Postfix) with ESMTP id D9D683A6BA8
	for <mpls@ietf.org>; Mon, 27 Oct 2008 15:46:24 -0700 (PDT)
Received: from huawei.com (szxga03-in [172.24.2.9])
	by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14
	(built Aug
	8 2006)) with ESMTP id <0K9F00CU75X2E2@szxga03-in.huawei.com> for
	mpls@ietf.org; Tue, 28 Oct 2008 06:46:14 +0800 (CST)
Received: from huawei.com ([172.24.1.12])
	by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14
	(built Aug
	8 2006)) with ESMTP id <0K9F00AX65X1WU@szxga03-in.huawei.com> for
	mpls@ietf.org; Tue, 28 Oct 2008 06:46:13 +0800 (CST)
Received: from R73802B ([10.193.217.99])
	by szxml05-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14
	(built Aug
	8 2006)) with ESMTPA id <0K9F00GI95WUXD@szxml05-in.huawei.com> for
	mpls@ietf.org; Tue, 28 Oct 2008 06:46:13 +0800 (CST)
Date: Mon, 27 Oct 2008 15:46:05 -0700
From: Renwei Li <renweili@huawei.com>
In-reply-to: <42591A81B59EA14BAA617596482F65CE05E9E0AF@xmb-rtp-212.amer.cisco.com>
To: "'David Smith (djsmith)'" <djsmith@cisco.com>, 'Loa Andersson' <loa@pi.nu>,
	mpls@ietf.org
Message-id: <001601c93885$cd87e190$63d9c10a@china.huawei.com>
Organization: Huawei Technologies
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
X-Mailer: Microsoft Office Outlook 11
Thread-index: Ackzuem58kjuQddzRgqs/M+6rT5e0gBFdYlgABE03NAAGUgRQAAaQlJQAKac5SA=
References: <009801c9357d$aed57a60$0301a8c0@china.huawei.com>
	<42591A81B59EA14BAA617596482F65CE05E9E0AF@xmb-rtp-212.amer.cisco.com>
Cc: 'Ross Callon' <rcallon@juniper.net>, 'David Ward' <dward@cisco.com>
Subject: Re: [mpls] draft-dasmith-mpls-ip-options-01.txt as a WG doc?
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: renweili@huawei.com
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mpls-bounces@ietf.org
Errors-To: mpls-bounces@ietf.org

Hi Dave,

I understand that the crafted IP options may be exploited by malicious users
to launch attacks, but some software vendors also develop their software
tools based on the options. The Class 2 options can't be simply ignored.

If an LER makes an IP packet un-routable because LSR doesn't install BGP
routes, the particular LER has an implementation problem. 

As I said before, if an IP packet has options inside, there has to be some
reasons for the options. Sometimes, if LER doesn't look at the options, the
packet can't be correctly forwarded. For example, if the packet wants to be
selectively broadcast to multiple destinations, the options must be
examined.

Moreover, IP options are also used for research and experiment. In such
cases, such experimental options are sometimes expected to be processed at
each hop.

As suggested before, it could be a CLI knob to turn on/off the feature.

If you try to standardize the forwarding path in LER, you have to consider
all the possible IP options. 

Regards,

Renwei



> -----Original Message-----
> From: David Smith (djsmith) [mailto:djsmith@cisco.com]
> Sent: Friday, October 24, 2008 8:50 AM
> To: renweili@huawei.com; Loa Andersson; mpls@ietf.org
> Cc: Ross Callon; David Ward
> Subject: RE: [mpls] draft-dasmith-mpls-ip-options-01.txt as a WG doc?
> 
> 
> Hi Renwei,
> 
> Rather than a local LER implementation issue, I'd say this is really a
> LER "forwarding issue". And the MPLS WG has defined many standards on
> "forwarding issues". Consider RFC3443 (TTL Processing in MPLS Networks)
> and RFC3270 (MPLS Support of DiffServ). Our draft complements RFC3443
> and RFC3270.
> 
> >Moreover, when an IP packet has an option, it usually has a
> >reason for having such an option, and thus expects to be
> >processed along the forwarding path in the network.
> 
> Keep in mind one reason (used by an attacker) may simply be "DoS LSRs".
> While the attacker hopes the packet is processed along the forwarding
> path, the MPLS network operator expects it to be tunnelled via an LSP.
> 
> >In this case, an ingress LER is essentially just one hop
> >away from the exit LER. The processing of such options on
> >LER should be no different from on other routers
> 
> This is not true for IP option packets. For packets w/o IP options this
> is true because they are LSP tunnelled from ingress LER to egress LER.
> However, for packets "with" IP options this MAY not be true (depending
> upon the ingress LER implementation) because such option packets are IP
> routed downstream and NOT LSP tunneled.
> 
> I'll argue this is a LER & LSR inter-op issue because the LSRs may not
> be carrying BGP routes and, if so, cannot route (unlabelled) transit
> packets that were not MPLS encapsulated by the ingress LER.
> 
> For these reasons, I think the MPLS WG needs a well-defined (ingress)
> LER forwarding rule to mitigate the risk of IP option packets on MPLS
> networks (ie, LSRs).
> 
> Regards,
> 
> /dave
> 
> 
> -----Original Message-----
> From: Renwei Li [mailto:renweili@huawei.com]
> Sent: Thursday, October 23, 2008 10:10 PM
> To: David Smith (djsmith); 'Loa Andersson'; mpls@ietf.org
> Cc: 'Ross Callon'; 'David Ward'
> Subject: RE: [mpls] draft-dasmith-mpls-ip-options-01.txt as a WG doc?
> 
> Hi Dave,
> 
> I do see your point. But it is really a local implementation issue. With
> or without it, LER would still work. It could at most serve as a CLI
> knob which can be turned on or off according to whatever someone wants,
> but it doesn't look like a requirement for LER.
> 
> > If so, should we not promote a consistent implementation among vendor
> > LERs via
> 
> It depends on what you mean by "consistent implementation"? If it has an
> effect on inter-op for LERs from different vendors, no doubt we should
> promote it and I will fully support it. But if it doesn't have anything
> to do with inter-op, I am afraid we should not promote it. There are so
> many different LERs that have different local implementations inside,
> but they are just fine provided they inter-op.
> 
> Moreover, when an IP packet has an option, it usually has a reason for
> having such an option, and thus expects to be processed along the
> forwarding path in the network. In this case, an ingress LER is
> essentially just one hop away from the exit LER. The processing of such
> options on LER should be no different from on other routers.
> 
> Regards,
> 
> Renwei
> 
> 
> > -----Original Message-----
> > From: David Smith (djsmith) [mailto:djsmith@cisco.com]
> > Sent: Thursday, October 23, 2008 7:17 AM
> > To: renweili@huawei.com; Loa Andersson; mpls@ietf.org
> > Cc: Ross Callon; David Ward
> > Subject: RE: [mpls] draft-dasmith-mpls-ip-options-01.txt as a WG doc?
> >
> >
> > Hi Renwei,
> >
> > Yes, it's a local LER decision.....but the LER implementation has
> > consequences on downstream LSRs.
> >
> > Do you agree that failing to MPLS encapsulate a IPv4 packet simply
> > because it has an IP option header may be a problem for the downstream
> 
> > network?
> >
> > If so, should we not promote a consistent implementation among vendor
> > LERs via an MPLS WG standard such that when an LER decides "whether to
> 
> > push an MPLS label stack onto an IP packet, the determination is made
> > without considering any IP options that may be carried in the IP
> > packet header"??
> >
> > Regards,
> >
> > /dave
> >
> >
> > -----Original Message-----
> > From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf
> > Of Renwei Li
> > Sent: Thursday, October 23, 2008 1:38 AM
> > To: 'Loa Andersson'; mpls@ietf.org
> > Cc: 'Ross Callon'; 'David Ward'
> > Subject: Re: [mpls] draft-dasmith-mpls-ip-options-01.txt as a WG doc?
> >
> > Opposed.
> >
> > This draft imposes a new requirement on LER. But the new requirement
> > has nothing to do with inter-op. Moreover, the new requirement is
> > really a matter of local implementation, and doesn't look really like
> a "MUST"
> > requirement.
> >
> > Regards,
> >
> > Renwei
> >
> >
> > > -----Original Message-----
> > > From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf
> 
> > > Of Loa Andersson
> > > Sent: Tuesday, October 21, 2008 1:14 PM
> > > To: mpls@ietf.org
> > > Cc: Ross Callon; David Ward
> > > Subject: [mpls] draft-dasmith-mpls-ip-options-01.txt as a WG doc?
> > >
> > > Working Group,
> > >
> > > we have been asked to adopt draft-dasmith-mpls-ip-options-01.txt
> > > as a WG doc.
> > >
> > > This is to start a two week poll. Please send your comments on
> > > whether
> >
> > > you think this is ready to become a wg document.
> > >
> > > George and Loa
> > >
> > > --
> > > Loa Andersson
> > >
> > > Principal Networking Architect
> > > Acreo AB                           phone:  +46 8 632 77 14
> > > Isafjordsgatan 22                  mobile: +46 739 81 21 64
> > > Kista, Sweden                      email:  loa.andersson@acreo.se
> > >                                            loa@pi.nu
> > > _______________________________________________
> > > mpls mailing list
> > > mpls@ietf.org
> > > https://www.ietf.org/mailman/listinfo/mpls
> >
> >
> > _______________________________________________
> > mpls mailing list
> > mpls@ietf.org
> > https://www.ietf.org/mailman/listinfo/mpls
> 



_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls


From mpls-bounces@ietf.org  Mon Oct 27 16:57:19 2008
Return-Path: <mpls-bounces@ietf.org>
X-Original-To: mpls-archive@megatron.ietf.org
Delivered-To: ietfarch-mpls-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B0AEA28C172;
	Mon, 27 Oct 2008 16:57:19 -0700 (PDT)
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 889BA28C193
	for <mpls@core3.amsl.com>; Mon, 27 Oct 2008 16:57:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, STOX_REPLY_TYPE=0.001]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id fF6r1Xo5D-ki for <mpls@core3.amsl.com>;
	Mon, 27 Oct 2008 16:57:17 -0700 (PDT)
Received: from asmtp1.iomartmail.com (asmtp1.iomartmail.com [62.128.201.248])
	by core3.amsl.com (Postfix) with ESMTP id C086528C16C
	for <mpls@ietf.org>; Mon, 27 Oct 2008 16:57:16 -0700 (PDT)
Received: from asmtp1.iomartmail.com (localhost.localdomain [127.0.0.1])
	by asmtp1.iomartmail.com (8.12.11.20060308/8.12.8) with ESMTP id
	m9RNv9NJ031065 for <mpls@ietf.org>; Mon, 27 Oct 2008 23:57:09 GMT
Received: from your029b8cecfe (dsl-sp-81-140-15-32.in-addr.broadbandscope.com
	[81.140.15.32]) (authenticated bits=0)
	by asmtp1.iomartmail.com (8.12.11.20060308/8.12.11) with ESMTP id
	m9RNv8CG031059 for <mpls@ietf.org>; Mon, 27 Oct 2008 23:57:08 GMT
Message-ID: <C48632358EF74F6595B4090FF4B42A39@your029b8cecfe>
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: <mpls@ietf.org>
References: <009801c9357d$aed57a60$0301a8c0@china.huawei.com><42591A81B59EA14BAA617596482F65CE05E9E0AF@xmb-rtp-212.amer.cisco.com>
	<001601c93885$cd87e190$63d9c10a@china.huawei.com>
Date: Mon, 27 Oct 2008 23:57:04 -0000
MIME-Version: 1.0
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.5512
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579
Subject: Re: [mpls] draft-dasmith-mpls-ip-options-01.txt as a WG doc?
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Adrian Farrel <adrian@olddog.co.uk>
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: mpls-bounces@ietf.org
Errors-To: mpls-bounces@ietf.org

I too am a bit concerned about this draft.

Unlike Renwei, I'm not too worried about experimental options. I don't think 
these are supposed to escape into the wider network, so we should not let 
them drive our decision-making.

However, I do agree that it worrying to make this standards track. It really 
does seem to be trying to define as mandatory an implementation behavior 
that might reasonably be flexible for different reasons.

If the use of IP options in the core is sufficiently worrying, why not 
disable them on the core routers?
If two IP packets carry different explicit paths in their options, why 
should they not be directed to different (explicitly routed) LSPs to conform 
to those routes even though they carry the same FEC?

There are plenty of questions like these and I don't feel that requiring an 
LER to conform to some behavior is beneficial.

Additionally, will you also be specifying the correct behavior of an LSR 
that receives an IP packet that carries options but that is not carried by 
an LSP when the LSR believes the packet should be carried by an LSP?

Now, if you made the I-D advice with suitable warnings, I might take a 
different view. This would be an Informational I-D not a BCP.

I would prefer more time to be spent discussing these ideas before the 
working group decides to embrace this work.

Cheers,
Adrian

----- Original Message ----- 
From: "Renwei Li" <renweili@huawei.com>
To: "'David Smith (djsmith)'" djsmith@cisco.com; "'Loa Andersson'" 
<loa@pi.nu>; <mpls@ietf.org>
Cc: "'Ross Callon'" <rcallon@juniper.net>; "'David Ward'" <dward@cisco.com>
Sent: Monday, October 27, 2008 10:46 PM
Subject: Re: [mpls] draft-dasmith-mpls-ip-options-01.txt as a WG doc?


> Hi Dave,
>
> I understand that the crafted IP options may be exploited by malicious 
> users
> to launch attacks, but some software vendors also develop their software
> tools based on the options. The Class 2 options can't be simply ignored.
>
> If an LER makes an IP packet un-routable because LSR doesn't install BGP
> routes, the particular LER has an implementation problem.
>
> As I said before, if an IP packet has options inside, there has to be some
> reasons for the options. Sometimes, if LER doesn't look at the options, 
> the
> packet can't be correctly forwarded. For example, if the packet wants to 
> be
> selectively broadcast to multiple destinations, the options must be
> examined.
>
> Moreover, IP options are also used for research and experiment. In such
> cases, such experimental options are sometimes expected to be processed at
> each hop.
>
> As suggested before, it could be a CLI knob to turn on/off the feature.
>
> If you try to standardize the forwarding path in LER, you have to consider
> all the possible IP options.
>
> Regards,
>
> Renwei
>
>
>
>> -----Original Message-----
>> From: David Smith (djsmith) [mailto:djsmith@cisco.com]
>> Sent: Friday, October 24, 2008 8:50 AM
>> To: renweili@huawei.com; Loa Andersson; mpls@ietf.org
>> Cc: Ross Callon; David Ward
>> Subject: RE: [mpls] draft-dasmith-mpls-ip-options-01.txt as a WG doc?
>>
>>
>> Hi Renwei,
>>
>> Rather than a local LER implementation issue, I'd say this is really a
>> LER "forwarding issue". And the MPLS WG has defined many standards on
>> "forwarding issues". Consider RFC3443 (TTL Processing in MPLS Networks)
>> and RFC3270 (MPLS Support of DiffServ). Our draft complements RFC3443
>> and RFC3270.
>>
>> >Moreover, when an IP packet has an option, it usually has a
>> >reason for having such an option, and thus expects to be
>> >processed along the forwarding path in the network.
>>
>> Keep in mind one reason (used by an attacker) may simply be "DoS LSRs".
>> While the attacker hopes the packet is processed along the forwarding
>> path, the MPLS network operator expects it to be tunnelled via an LSP.
>>
>> >In this case, an ingress LER is essentially just one hop
>> >away from the exit LER. The processing of such options on
>> >LER should be no different from on other routers
>>
>> This is not true for IP option packets. For packets w/o IP options this
>> is true because they are LSP tunnelled from ingress LER to egress LER.
>> However, for packets "with" IP options this MAY not be true (depending
>> upon the ingress LER implementation) because such option packets are IP
>> routed downstream and NOT LSP tunneled.
>>
>> I'll argue this is a LER & LSR inter-op issue because the LSRs may not
>> be carrying BGP routes and, if so, cannot route (unlabelled) transit
>> packets that were not MPLS encapsulated by the ingress LER.
>>
>> For these reasons, I think the MPLS WG needs a well-defined (ingress)
>> LER forwarding rule to mitigate the risk of IP option packets on MPLS
>> networks (ie, LSRs).
>>
>> Regards,
>>
>> /dave
>>
>>
>> -----Original Message-----
>> From: Renwei Li [mailto:renweili@huawei.com]
>> Sent: Thursday, October 23, 2008 10:10 PM
>> To: David Smith (djsmith); 'Loa Andersson'; mpls@ietf.org
>> Cc: 'Ross Callon'; 'David Ward'
>> Subject: RE: [mpls] draft-dasmith-mpls-ip-options-01.txt as a WG doc?
>>
>> Hi Dave,
>>
>> I do see your point. But it is really a local implementation issue. With
>> or without it, LER would still work. It could at most serve as a CLI
>> knob which can be turned on or off according to whatever someone wants,
>> but it doesn't look like a requirement for LER.
>>
>> > If so, should we not promote a consistent implementation among vendor
>> > LERs via
>>
>> It depends on what you mean by "consistent implementation"? If it has an
>> effect on inter-op for LERs from different vendors, no doubt we should
>> promote it and I will fully support it. But if it doesn't have anything
>> to do with inter-op, I am afraid we should not promote it. There are so
>> many different LERs that have different local implementations inside,
>> but they are just fine provided they inter-op.
>>
>> Moreover, when an IP packet has an option, it usually has a reason for
>> having such an option, and thus expects to be processed along the
>> forwarding path in the network. In this case, an ingress LER is
>> essentially just one hop away from the exit LER. The processing of such
>> options on LER should be no different from on other routers.
>>
>> Regards,
>>
>> Renwei
>>
>>
>> > -----Original Message-----
>> > From: David Smith (djsmith) [mailto:djsmith@cisco.com]
>> > Sent: Thursday, October 23, 2008 7:17 AM
>> > To: renweili@huawei.com; Loa Andersson; mpls@ietf.org
>> > Cc: Ross Callon; David Ward
>> > Subject: RE: [mpls] draft-dasmith-mpls-ip-options-01.txt as a WG doc?
>> >
>> >
>> > Hi Renwei,
>> >
>> > Yes, it's a local LER decision.....but the LER implementation has
>> > consequences on downstream LSRs.
>> >
>> > Do you agree that failing to MPLS encapsulate a IPv4 packet simply
>> > because it has an IP option header may be a problem for the downstream
>>
>> > network?
>> >
>> > If so, should we not promote a consistent implementation among vendor
>> > LERs via an MPLS WG standard such that when an LER decides "whether to
>>
>> > push an MPLS label stack onto an IP packet, the determination is made
>> > without considering any IP options that may be carried in the IP
>> > packet header"??
>> >
>> > Regards,
>> >
>> > /dave
>> >
>> >
>> > -----Original Message-----
>> > From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf
>> > Of Renwei Li
>> > Sent: Thursday, October 23, 2008 1:38 AM
>> > To: 'Loa Andersson'; mpls@ietf.org
>> > Cc: 'Ross Callon'; 'David Ward'
>> > Subject: Re: [mpls] draft-dasmith-mpls-ip-options-01.txt as a WG doc?
>> >
>> > Opposed.
>> >
>> > This draft imposes a new requirement on LER. But the new requirement
>> > has nothing to do with inter-op. Moreover, the new requirement is
>> > really a matter of local implementation, and doesn't look really like
>> a "MUST"
>> > requirement.
>> >
>> > Regards,
>> >
>> > Renwei
>> >
>> >
>> > > -----Original Message-----
>> > > From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf
>>
>> > > Of Loa Andersson
>> > > Sent: Tuesday, October 21, 2008 1:14 PM
>> > > To: mpls@ietf.org
>> > > Cc: Ross Callon; David Ward
>> > > Subject: [mpls] draft-dasmith-mpls-ip-options-01.txt as a WG doc?
>> > >
>> > > Working Group,
>> > >
>> > > we have been asked to adopt draft-dasmith-mpls-ip-options-01.txt
>> > > as a WG doc.
>> > >
>> > > This is to start a two week poll. Please send your comments on
>> > > whether
>> >
>> > > you think this is ready to become a wg document.
>> > >
>> > > George and Loa
>> > >
>> > > --
>> > > Loa Andersson
>> > >
>> > > Principal Networking Architect
>> > > Acreo AB                           phone:  +46 8 632 77 14
>> > > Isafjordsgatan 22                  mobile: +46 739 81 21 64
>> > > Kista, Sweden                      email:  loa.andersson@acreo.se
>> > >                                            loa@pi.nu
>> > > _______________________________________________
>> > > mpls mailing list
>> > > mpls@ietf.org
>> > > https://www.ietf.org/mailman/listinfo/mpls
>> >
>> >
>> > _______________________________________________
>> > mpls mailing list
>> > mpls@ietf.org
>> > https://www.ietf.org/mailman/listinfo/mpls
>>
>
>
>
> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls
> 

_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls


From mpls-bounces@ietf.org  Tue Oct 28 03:12:24 2008
Return-Path: <mpls-bounces@ietf.org>
X-Original-To: mpls-archive@megatron.ietf.org
Delivered-To: ietfarch-mpls-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 4AF453A6BCD;
	Tue, 28 Oct 2008 03:12:24 -0700 (PDT)
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 2723A3A695D;
	Tue, 28 Oct 2008 03:12:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.799
X-Spam-Level: 
X-Spam-Status: No, score=-0.799 tagged_above=-999 required=5 tests=[AWL=1.800, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 9xfAjTMG7RIb; Tue, 28 Oct 2008 03:12:22 -0700 (PDT)
Received: from neo.viciousnest.net (neo.viciousnest.net [192.71.80.124])
	by core3.amsl.com (Postfix) with ESMTP id 50F2A3A682A;
	Tue, 28 Oct 2008 03:12:22 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1])
	by neo.viciousnest.net (Postfix) with ESMTP id F15B33D2E;
	Tue, 28 Oct 2008 11:12:20 +0100 (CET)
Received: from neo.viciousnest.net ([127.0.0.1])
	by localhost (neo [127.0.0.1]) (amavisd-new, port 10024) with ESMTP
	id 06060-09; Tue, 28 Oct 2008 11:12:19 +0100 (CET)
Received: from [192.36.157.201] (dhcp201.verkstad.net [192.36.157.201])
	by neo.viciousnest.net (Postfix) with ESMTP id DC5B93D28;
	Tue, 28 Oct 2008 11:12:19 +0100 (CET)
Message-ID: <4906E57E.4050105@pi.nu>
Date: Tue, 28 Oct 2008 11:12:14 +0100
From: Loa Andersson <loa@pi.nu>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
To: "mpls@ietf.org" <mpls@ietf.org>, pwe3 <pwe3@ietf.org>, 
	"ahtmpls@itu.int" <ahtmpls@itu.int>, ccamp <ccamp@ops.ietf.org>
X-Enigmail-Version: 0.95.7
X-Virus-Scanned: by amavisd-new at viciousnest.net
Subject: [mpls] draft-bocci-mpls-tp-gach-gal-00.txt for mpls wg doc
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mpls-bounces@ietf.org
Errors-To: mpls-bounces@ietf.org

Working group(s),

this is to initiate a two week poll to see if
draft-bocci-mpls-tp-gach-gal-00.txt is in shape to
become a mpls working group document.

The current draft is a merge of to earlier draft
one that defined the GAL and another that specified
the generic associated channel.

Please send your responses to the mpls working group
mailing list (needs a bit of discipline, "replay all"
won't do the trick ;) .

Please respond on Tuesday Oct 11 the latest.

/Loa

-- 
Loa Andersson

Principal Networking Architect
Acreo AB                           phone:  +46 8 632 77 14
Isafjordsgatan 22                  mobile: +46 739 81 21 64
Kista, Sweden                      email:  loa.andersson@acreo.se
                                           loa@pi.nu
_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls


From mpls-bounces@ietf.org  Tue Oct 28 03:42:04 2008
Return-Path: <mpls-bounces@ietf.org>
X-Original-To: mpls-archive@megatron.ietf.org
Delivered-To: ietfarch-mpls-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B58503A68B6;
	Tue, 28 Oct 2008 03:42:04 -0700 (PDT)
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 0D6753A68B6
	for <mpls@core3.amsl.com>; Tue, 28 Oct 2008 03:42:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.249
X-Spam-Level: 
X-Spam-Status: No, score=-2.249 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, HELO_EQ_FR=0.35]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 4ks4N9GeThV2 for <mpls@core3.amsl.com>;
	Tue, 28 Oct 2008 03:42:02 -0700 (PDT)
Received: from smail5.alcatel.fr (smail5.alcatel.fr [62.23.212.27])
	by core3.amsl.com (Postfix) with ESMTP id 6B4D43A67ED
	for <mpls@ietf.org>; Tue, 28 Oct 2008 03:42:01 -0700 (PDT)
Received: from FRVELSBHS03.ad2.ad.alcatel.com (frvelsbhs03.ad2.ad.alcatel.com
	[155.132.6.75])
	by smail5.alcatel.fr (8.13.8/8.13.8/ICT) with ESMTP id m9SAeUQG022360
	for <mpls@ietf.org>; Tue, 28 Oct 2008 11:41:56 +0100
Received: from FRVELSMBS21.ad2.ad.alcatel.com ([155.132.6.51]) by
	FRVELSBHS03.ad2.ad.alcatel.com with Microsoft
	SMTPSVC(6.0.3790.2499); Tue, 28 Oct 2008 11:41:23 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Tue, 28 Oct 2008 11:41:22 +0100
Message-ID: <6FD21B53861BF44AA90A288402036AB401A37374@FRVELSMBS21.ad2.ad.alcatel.com>
In-Reply-To: <4906E57E.4050105@pi.nu>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [PWE3] draft-bocci-mpls-tp-gach-gal-00.txt for mpls wg doc
Thread-Index: Ack45bw2vBaK+W3OQJmHEjHQN9XhTQAA/IHw
References: <4906E57E.4050105@pi.nu>
From: "BUSI ITALO" <Italo.Busi@alcatel-lucent.it>
To: <mpls@ietf.org>
X-OriginalArrivalTime: 28 Oct 2008 10:41:23.0746 (UTC)
	FILETIME=[B8E72020:01C938E9]
X-Scanned-By: MIMEDefang 2.57 on 155.132.188.13
Subject: Re: [mpls] [PWE3] draft-bocci-mpls-tp-gach-gal-00.txt for mpls wg
	doc
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mpls-bounces@ietf.org
Errors-To: mpls-bounces@ietf.org

Support

Italo 

> -----Original Message-----
> From: pwe3-bounces@ietf.org [mailto:pwe3-bounces@ietf.org] On 
> Behalf Of Loa Andersson
> Sent: Tuesday, October 28, 2008 11:12 AM
> To: mpls@ietf.org; pwe3; ahtmpls@itu.int; ccamp
> Subject: [PWE3] draft-bocci-mpls-tp-gach-gal-00.txt for mpls wg doc
> 
> Working group(s),
> 
> this is to initiate a two week poll to see if
> draft-bocci-mpls-tp-gach-gal-00.txt is in shape to
> become a mpls working group document.
> 
> The current draft is a merge of to earlier draft
> one that defined the GAL and another that specified
> the generic associated channel.
> 
> Please send your responses to the mpls working group
> mailing list (needs a bit of discipline, "replay all"
> won't do the trick ;) .
> 
> Please respond on Tuesday Oct 11 the latest.
> 
> /Loa
> 
> -- 
> Loa Andersson
> 
> Principal Networking Architect
> Acreo AB                           phone:  +46 8 632 77 14
> Isafjordsgatan 22                  mobile: +46 739 81 21 64
> Kista, Sweden                      email:  loa.andersson@acreo.se
>                                            loa@pi.nu
> _______________________________________________
> pwe3 mailing list
> pwe3@ietf.org
> https://www.ietf.org/mailman/listinfo/pwe3
> 
_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls


From mpls-bounces@ietf.org  Tue Oct 28 06:38:49 2008
Return-Path: <mpls-bounces@ietf.org>
X-Original-To: mpls-archive@megatron.ietf.org
Delivered-To: ietfarch-mpls-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 7452F28C265;
	Tue, 28 Oct 2008 06:38:49 -0700 (PDT)
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 6D9453A6BA4;
	Tue, 28 Oct 2008 06:38:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 8l1vaVLJI+64; Tue, 28 Oct 2008 06:38:42 -0700 (PDT)
Received: from demumfd001.nsn-inter.net (demumfd001.nsn-inter.net
	[217.115.75.233])
	by core3.amsl.com (Postfix) with ESMTP id BA91A3A6979;
	Tue, 28 Oct 2008 06:38:41 -0700 (PDT)
Received: from demuprx016.emea.nsn-intra.net ([10.150.129.55])
	by demumfd001.nsn-inter.net (8.12.11.20060308/8.12.11) with ESMTP id
	m9SDccUO014833
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL);
	Tue, 28 Oct 2008 14:38:38 +0100
Received: from demuexc022.nsn-intra.net (webmail.nsn-intra.net [10.150.128.35])
	by demuprx016.emea.nsn-intra.net (8.12.11.20060308/8.12.11) with ESMTP
	id m9SDcaJq005134; Tue, 28 Oct 2008 14:38:38 +0100
Received: from DEMUEXC030.nsn-intra.net ([10.150.128.57]) by
	demuexc022.nsn-intra.net with Microsoft SMTPSVC(6.0.3790.3959); 
	Tue, 28 Oct 2008 14:38:36 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Tue, 28 Oct 2008 14:38:30 +0100
Message-ID: <43284B5A95E36B4AB4A91EBA4E0FC31EE6B78B@DEMUEXC030.nsn-intra.net>
In-Reply-To: <4906E57E.4050105@pi.nu>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [PWE3] draft-bocci-mpls-tp-gach-gal-00.txt for mpls wg doc
Thread-Index: Ack45a9i7kRm6Nr9R/u0ZP5cd7068QAHK5Iw
References: <4906E57E.4050105@pi.nu>
From: "Sprecher, Nurit (NSN - IL/Hod HaSharon)" <nurit.sprecher@nsn.com>
To: "ext Loa Andersson" <loa@pi.nu>, <mpls@ietf.org>, "pwe3" <pwe3@ietf.org>, 
	<ahtmpls@itu.int>, "ccamp" <ccamp@ops.ietf.org>
X-OriginalArrivalTime: 28 Oct 2008 13:38:36.0332 (UTC)
	FILETIME=[7A6AFEC0:01C93902]
X-purgate: clean
X-purgate: This mail is considered clean
X-purgate-type: clean
X-purgate-Ad: Checked for Spam by eleven - eXpurgate www.eXpurgate.net
X-purgate-ID: 151667::081028143838-115F1BB0-41EA3429/0-0/0-15
X-purgate-size: 1216/0
Subject: Re: [mpls] [PWE3] draft-bocci-mpls-tp-gach-gal-00.txt for mpls wg
	doc
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mpls-bounces@ietf.org
Errors-To: mpls-bounces@ietf.org

I support.
Nurit

-----Original Message-----
From: pwe3-bounces@ietf.org [mailto:pwe3-bounces@ietf.org] On Behalf Of
ext Loa Andersson
Sent: Tuesday, October 28, 2008 12:12
To: mpls@ietf.org; pwe3; ahtmpls@itu.int; ccamp
Subject: [PWE3] draft-bocci-mpls-tp-gach-gal-00.txt for mpls wg doc

Working group(s),

this is to initiate a two week poll to see if
draft-bocci-mpls-tp-gach-gal-00.txt is in shape to
become a mpls working group document.

The current draft is a merge of to earlier draft
one that defined the GAL and another that specified
the generic associated channel.

Please send your responses to the mpls working group
mailing list (needs a bit of discipline, "replay all"
won't do the trick ;) .

Please respond on Tuesday Oct 11 the latest.

/Loa

-- 
Loa Andersson

Principal Networking Architect
Acreo AB                           phone:  +46 8 632 77 14
Isafjordsgatan 22                  mobile: +46 739 81 21 64
Kista, Sweden                      email:  loa.andersson@acreo.se
                                           loa@pi.nu
_______________________________________________
pwe3 mailing list
pwe3@ietf.org
https://www.ietf.org/mailman/listinfo/pwe3
_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls


From mpls-bounces@ietf.org  Tue Oct 28 09:43:11 2008
Return-Path: <mpls-bounces@ietf.org>
X-Original-To: mpls-archive@megatron.ietf.org
Delivered-To: ietfarch-mpls-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 7E80A3A6B4A;
	Tue, 28 Oct 2008 09:43:11 -0700 (PDT)
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 3DE833A67B0;
	Tue, 28 Oct 2008 09:43:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id Pp+zbpLLp8hm; Tue, 28 Oct 2008 09:43:09 -0700 (PDT)
Received: from audl953.usa.alcatel.com (audl953.usa.alcatel.com
	[143.209.238.162])
	by core3.amsl.com (Postfix) with ESMTP id 616DD3A6B4A;
	Tue, 28 Oct 2008 09:43:09 -0700 (PDT)
Received: from usdalsbhs01.ad3.ad.alcatel.com (usdalsbhs01.usa.alcatel.com
	[172.22.216.19])
	by audl953.usa.alcatel.com (ALCANET) with ESMTP id m9SGh3hL021647;
	Tue, 28 Oct 2008 10:43:03 -0600
Received: from USDALSMBS03.ad3.ad.alcatel.com ([172.22.216.6]) by
	usdalsbhs01.ad3.ad.alcatel.com with Microsoft
	SMTPSVC(6.0.3790.2499); Tue, 28 Oct 2008 11:43:03 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Tue, 28 Oct 2008 11:43:01 -0500
Message-ID: <4A5028372622294A99B8FFF6BD06EB7B04C95204@USDALSMBS03.ad3.ad.alcatel.com>
In-Reply-To: <4906E57E.4050105@pi.nu>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [mpls] draft-bocci-mpls-tp-gach-gal-00.txt for mpls wg doc
Thread-Index: Ack45byfagYrwvvLT9mCMeJee3MqKwANnugw
References: <4906E57E.4050105@pi.nu>
From: "AISSAOUI Mustapha" <Mustapha.Aissaoui@alcatel-lucent.com>
To: "Loa Andersson" <loa@pi.nu>, <mpls@ietf.org>, "pwe3" <pwe3@ietf.org>,
	<ahtmpls@itu.int>, "ccamp" <ccamp@ops.ietf.org>
X-OriginalArrivalTime: 28 Oct 2008 16:43:03.0411 (UTC)
	FILETIME=[3EE93C30:01C9391C]
X-Scanned-By: MIMEDefang 2.64 on 143.209.238.34
Subject: Re: [mpls] draft-bocci-mpls-tp-gach-gal-00.txt for mpls wg doc
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mpls-bounces@ietf.org
Errors-To: mpls-bounces@ietf.org

support.

Mustapha. 

> -----Original Message-----
> From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On 
> Behalf Of Loa Andersson
> Sent: Tuesday, October 28, 2008 6:12 AM
> To: mpls@ietf.org; pwe3; ahtmpls@itu.int; ccamp
> Subject: [mpls] draft-bocci-mpls-tp-gach-gal-00.txt for mpls wg doc
> 
> Working group(s),
> 
> this is to initiate a two week poll to see if 
> draft-bocci-mpls-tp-gach-gal-00.txt is in shape to become a 
> mpls working group document.
> 
> The current draft is a merge of to earlier draft one that 
> defined the GAL and another that specified the generic 
> associated channel.
> 
> Please send your responses to the mpls working group mailing 
> list (needs a bit of discipline, "replay all"
> won't do the trick ;) .
> 
> Please respond on Tuesday Oct 11 the latest.
> 
> /Loa
> 
> --
> Loa Andersson
> 
> Principal Networking Architect
> Acreo AB                           phone:  +46 8 632 77 14
> Isafjordsgatan 22                  mobile: +46 739 81 21 64
> Kista, Sweden                      email:  loa.andersson@acreo.se
>                                            loa@pi.nu 
> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls
> 
_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls


From mpls-bounces@ietf.org  Tue Oct 28 09:51:05 2008
Return-Path: <mpls-bounces@ietf.org>
X-Original-To: mpls-archive@megatron.ietf.org
Delivered-To: ietfarch-mpls-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id ABA9828C2C1;
	Tue, 28 Oct 2008 09:51:05 -0700 (PDT)
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id CDC9C3A6C5E
	for <mpls@core3.amsl.com>; Tue, 28 Oct 2008 09:51:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.249
X-Spam-Level: 
X-Spam-Status: No, score=-3.249 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, HELO_EQ_FR=0.35, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id nB9wWMDKRzPE for <mpls@core3.amsl.com>;
	Tue, 28 Oct 2008 09:51:03 -0700 (PDT)
Received: from p-mail2.rd.francetelecom.com (p-mail2.rd.francetelecom.com
	[195.101.245.16])
	by core3.amsl.com (Postfix) with ESMTP id 77B2B3A6BED
	for <mpls@ietf.org>; Tue, 28 Oct 2008 09:51:03 -0700 (PDT)
Received: from FTRDMEL2.rd.francetelecom.fr ([10.193.117.153]) by
	ftrdsmtp2.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 28 Oct 2008 17:50:59 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Tue, 28 Oct 2008 17:50:14 +0100
Message-ID: <7DBAFEC6A76F3E42817DF1EBE64CB02605F7FFED@ftrdmel2>
In-Reply-To: <002801c935f2$9229cae0$0200a8c0@your029b8cecfe>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [mpls] A BNF specification for RSVP-TE
Thread-Index: Ack18vFMWIEDwv5CSsGojIKzyzx24gDGSlgw
References: <002801c935f2$9229cae0$0200a8c0@your029b8cecfe>
From: <julien.meuric@orange-ftgroup.com>
To: <adrian@olddog.co.uk>
X-OriginalArrivalTime: 28 Oct 2008 16:50:59.0339 (UTC)
	FILETIME=[5A9615B0:01C9391D]
Cc: mpls@ietf.org
Subject: Re: [mpls] A BNF specification for RSVP-TE
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mpls-bounces@ietf.org
Errors-To: mpls-bounces@ietf.org

Hi Adrian.

Here are a few comments on your ID.

**********
There is no ToC. Adding one might help to understand why the "Operators"
section is numbered 2.2 and not 2.1.5 (I'm a bit lost here).
**********
Section 2.2.1: you define the assigment operator by saying both sides
are "equivalent". I feel this very notion of "equivalence" is not
specified enough in our context of grammar definition and the operation
described is "stronger" than a usual equivalence noted "~". However, as
a non native, I know my interpretation is biased. Wouldn't a definition
relying on terms such as "synonymous", "equal", "identical",
"substituable"... (sure you'll find better words than me) make it
sharper?
**********
Section 2.2.3: nesting appears only as an example. I would find it more
consistent if the sentence "The optional operator can be nested" were
moved into the paragraph "Meaning".
**********
Section 2.2.4: the encoding is defined by a full sentence (including
subject, verb...), thus creating an exception in the form of the
document. (Would I have raised this if the author was different? ;-) )
**********
Section 2.2.5: my 1st reaction when reading the example is what you say
right after about grouping using round braquets instead of square ones.
The direct consequence of your example is that the operator "..." is
also defined for nil, which was not obvious before.

Second reaction: why those outer square brackets? Grouping could have
been used (even if useless), but why this double level of optionality? I
find it rather confusing and would have prefered:
- either "[ <MESSAGE_ID_ACK> | <MESSAGE_ID_NACK> ] ..."
- or "[  ( <MESSAGE_ID_ACK> | <MESSAGE_ID_NACK> ) ... ]"

Side question: I'm sure you're correct on "more clear" at the end of the
section, but your humble servant definitely requires an English grammar
lesson to understand why you prefered it to "clearer".
**********
Section 2.2.6, note 1: "grouping [...] is RECOMMENDED as a solution for
multi-alternates" while section 2.2.4 says about multi-alternates:
"explicit grouping [...] or an intermediary MUST be used". OPTIONAL can
be considered, but I'd favor MANDATORY; anyway consistency MUST be
achieved whithin the ID.
**********
Section 2.4: to depict the possible misinterpretation due to line
breaks, you'd better add an example such as:
<flow descriptor list> ::=  <empty> | <flow descriptor list>
                            <flow descriptor>
where the reader is really tempted by formulation "b" because of the
line break, while precedence leaves only "a" as an option.
**********
Section 5: I'd have swapped "defective" and "incompatible" in the last
paragraph since security attacks applies to the (former) former, not to
the (former) latter.
**********

Cheers,

Julien


-----Original Message-----
From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf Of
Adrian Farrel

Hi,

This draft provides a specification of the BNF we already use in RSVP-TE
and 
makes it available for use in future RSVP-TE extensions.

I intend asking that this draft progress in the standards process
relatively 
soon.

Please review and comment as soon as possible.

Thanks,
Adrian
----- Original Message ----- 
From: <Internet-Drafts@ietf.org>

>A New Internet-Draft is available from the on-line Internet-Drafts 
>directories.
>
> Title           : Reduced Backus-Naur Form (RBNF) A Syntax Used in
Various 
> Protocol Specifications
> Author(s)       : A. Farrel
> Filename        : draft-farrel-rtg-common-bnf-06.txt
> Pages           : 12
> Date            : 2008-10-24
>
> Several protocols have been specified using a common variant of the
> Backus-Naur Form (BNF) of representing message syntax. However, there
> is no formal definition of this version of BNF.
>
> There is value in using the same variant of BNF for the set of
> protocols that are commonly used together. This reduces confusion and
> simplifies implementation.
>
> Updating existing documents to use some other variant of BNF that is
> already formally documented would be a substantial piece of work.
>
> This document provides a formal definition of the variant of BNF that
> has been used (that we call Reduced BNF), and makes it available for
> use by new protocols.
>
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-farrel-rtg-common-bnf-06.txt

_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls
_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls


From mpls-bounces@ietf.org  Tue Oct 28 10:01:57 2008
Return-Path: <mpls-bounces@ietf.org>
X-Original-To: mpls-archive@megatron.ietf.org
Delivered-To: ietfarch-mpls-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 1F33428C2FA;
	Tue, 28 Oct 2008 10:01:57 -0700 (PDT)
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id A2FDD3A6B90
	for <mpls@core3.amsl.com>; Tue, 28 Oct 2008 10:01:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.248
X-Spam-Level: 
X-Spam-Status: No, score=-2.248 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id j9HFLR+0KhOy for <mpls@core3.amsl.com>;
	Tue, 28 Oct 2008 10:01:55 -0700 (PDT)
Received: from mailrelay2.alcatel.de (mailrelay2.alcatel.de [194.113.59.96])
	by core3.amsl.com (Postfix) with ESMTP id A40FE28C31A
	for <mpls@ietf.org>; Tue, 28 Oct 2008 10:01:48 -0700 (PDT)
Received: from [149.204.106.220] (destgn0t02145.ad1.ad.alcatel.com
	[149.204.106.220])
	by mailrelay2.alcatel.de (8.13.8/8.13.8/ICT) with ESMTP id
	m9SH1khc022139 for <mpls@ietf.org>; Tue, 28 Oct 2008 18:01:46 +0100
Message-ID: <49074579.7010106@alcatel-lucent.de>
Date: Tue, 28 Oct 2008 18:01:45 +0100
From: Dieter Beller <D.Beller@alcatel-lucent.de>
Organization: Alcatel-Lucent
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
To: "mpls@ietf.org" <mpls@ietf.org>
References: <4906E57E.4050105@pi.nu>
In-Reply-To: <4906E57E.4050105@pi.nu>
Content-Type: multipart/mixed; boundary="------------050101030403030004020507"
X-Scanned-By: MIMEDefang 2.57 on 149.204.45.73
Subject: Re: [mpls] draft-bocci-mpls-tp-gach-gal-00.txt for mpls wg doc
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=subscribe>
Sender: mpls-bounces@ietf.org
Errors-To: mpls-bounces@ietf.org

This is a multi-part message in MIME format.
--------------050101030403030004020507
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
<font face="Trebuchet MS">I support that this I-D becomes a WG doc.<br>
<br>
Cheers,<br>
Dieter<br>
</font><br>
Loa Andersson wrote:
<blockquote cite="mid:4906E57E.4050105@pi.nu" type="cite">
  <pre wrap="">Working group(s),

this is to initiate a two week poll to see if
draft-bocci-mpls-tp-gach-gal-00.txt is in shape to
become a mpls working group document.

The current draft is a merge of to earlier draft
one that defined the GAL and another that specified
the generic associated channel.

Please send your responses to the mpls working group
mailing list (needs a bit of discipline, "replay all"
won't do the trick ;) .

Please respond on Tuesday Oct 11 the latest.

/Loa

  </pre>
</blockquote>
<br>
<div class="moz-signature">-- <br>
<meta content="text/html;" http-equiv="Content-Type">
<title></title>
<hr size="2" width="100%">
</div>
<br>
<div class="moz-signature">-- <br>
<meta content="text/html;" http-equiv="Content-Type">
<title></title>
<hr size="2" width="100%">
</div>
</body>
</html>

--------------050101030403030004020507
Content-Type: text/x-vcard; charset=utf-8;
 name="D_Beller.vcf"
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
 filename="D_Beller.vcf"

begin:vcard
fn:Dieter Beller
n:Beller;Dieter
org:Alcatel-Lucent, Carrier Business Group;Optics Division - Network & Product Strategy
adr:;;Lorenzstrasse 10;Stuttgart;;70435;Germany
email;internet:D.Beller@alcatel-lucent.de
tel;work:+49 711 821-43125
tel;cell:+49 175 7266874
note;quoted-printable:Alcatel-Lucent Deutschland AG:=0D=0A=
	=0D=0A=
	Sitz der Gesellschaft: Stuttgart - Amtsgericht Stuttgart HRB 4026=0D=0A=
	Vorsitzender des Aufsichtsrats: Michael Oppenhoff=0D=0A=
	Vorstand: Wolfgang Weik (Vors.), Dr. Rainer Fechner, Juergen Poesinger,Al=
	f Henryk Wulf
x-mozilla-html:TRUE
version:2.1
end:vcard


--------------050101030403030004020507
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls

--------------050101030403030004020507--


From mpls-bounces@ietf.org  Tue Oct 28 10:17:38 2008
Return-Path: <mpls-bounces@ietf.org>
X-Original-To: mpls-archive@megatron.ietf.org
Delivered-To: ietfarch-mpls-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id A96BA3A6C92;
	Tue, 28 Oct 2008 10:17:38 -0700 (PDT)
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 54EE03A6C64;
	Tue, 28 Oct 2008 10:17:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id FIbecs2xlKZR; Tue, 28 Oct 2008 10:17:36 -0700 (PDT)
Received: from ihemail1.lucent.com (ihemail1.lucent.com [135.245.0.33])
	by core3.amsl.com (Postfix) with ESMTP id 7E24F28C2EC;
	Tue, 28 Oct 2008 10:17:24 -0700 (PDT)
Received: from ilexp01.ndc.lucent.com (h135-3-39-1.lucent.com [135.3.39.1])
	by ihemail1.lucent.com (8.13.8/IER-o) with ESMTP id m9SHIIqD014070;
	Tue, 28 Oct 2008 12:18:21 -0500 (CDT)
Received: from DEEXP02.DE.lucent.com ([135.248.187.66]) by
	ilexp01.ndc.lucent.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 28 Oct 2008 12:17:11 -0500
Received: from DEEXC1U02.de.lucent.com ([135.248.187.27]) by
	DEEXP02.DE.lucent.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 28 Oct 2008 18:17:09 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Tue, 28 Oct 2008 18:17:13 +0100
Message-ID: <972138A9A2BE554A8710BB4F3E4B03A5DD8F0D@DEEXC1U02.de.lucent.com>
In-Reply-To: <4906E57E.4050105@pi.nu>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [PWE3] draft-bocci-mpls-tp-gach-gal-00.txt for mpls wg doc
Thread-Index: Ack45bOU1d4kJliPR/CqK2x2BiOJ5QAO0xfw
References: <4906E57E.4050105@pi.nu>
From: "LEVRAU, LIEVEN \(LIEVEN\)" <llevrau@alcatel-lucent.com>
To: "Loa Andersson" <loa@pi.nu>, <mpls@ietf.org>, "pwe3" <pwe3@ietf.org>,
	<ahtmpls@itu.int>, "ccamp" <ccamp@ops.ietf.org>
X-OriginalArrivalTime: 28 Oct 2008 17:17:09.0371 (UTC)
	FILETIME=[0265F4B0:01C93921]
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.33
Subject: Re: [mpls] [PWE3] draft-bocci-mpls-tp-gach-gal-00.txt for mpls wg
	doc
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mpls-bounces@ietf.org
Errors-To: mpls-bounces@ietf.org

Support
./
Lieven

-----Original Message-----
From: pwe3-bounces@ietf.org [mailto:pwe3-bounces@ietf.org] On Behalf Of
Loa Andersson
Sent: 28 October 2008 11:12
To: mpls@ietf.org; pwe3; ahtmpls@itu.int; ccamp
Subject: [PWE3] draft-bocci-mpls-tp-gach-gal-00.txt for mpls wg doc

Working group(s),

this is to initiate a two week poll to see if
draft-bocci-mpls-tp-gach-gal-00.txt is in shape to
become a mpls working group document.

The current draft is a merge of to earlier draft
one that defined the GAL and another that specified
the generic associated channel.

Please send your responses to the mpls working group
mailing list (needs a bit of discipline, "replay all"
won't do the trick ;) .

Please respond on Tuesday Oct 11 the latest.

/Loa

-- 
Loa Andersson

Principal Networking Architect
Acreo AB                           phone:  +46 8 632 77 14
Isafjordsgatan 22                  mobile: +46 739 81 21 64
Kista, Sweden                      email:  loa.andersson@acreo.se
                                           loa@pi.nu
_______________________________________________
pwe3 mailing list
pwe3@ietf.org
https://www.ietf.org/mailman/listinfo/pwe3
_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls


From mpls-bounces@ietf.org  Tue Oct 28 10:46:52 2008
Return-Path: <mpls-bounces@ietf.org>
X-Original-To: mpls-archive@megatron.ietf.org
Delivered-To: ietfarch-mpls-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 7BEF528C0E5;
	Tue, 28 Oct 2008 10:46:52 -0700 (PDT)
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id D4EDB28C333
	for <mpls@core3.amsl.com>; Tue, 28 Oct 2008 10:46:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id ZJoHl1c69qn3 for <mpls@core3.amsl.com>;
	Tue, 28 Oct 2008 10:46:50 -0700 (PDT)
Received: from ihemail4.lucent.com (ihemail4.lucent.com [135.245.0.39])
	by core3.amsl.com (Postfix) with ESMTP id BAE3528C33C
	for <mpls@ietf.org>; Tue, 28 Oct 2008 10:46:47 -0700 (PDT)
Received: from ilexp03.ndc.lucent.com (h135-3-39-50.lucent.com [135.3.39.50])
	by ihemail4.lucent.com (8.13.8/IER-o) with ESMTP id m9SHk3eX014588
	for <mpls@ietf.org>; Tue, 28 Oct 2008 12:46:35 -0500 (CDT)
Received: from ILEXC2U03.ndc.lucent.com ([135.3.39.9]) by
	ilexp03.ndc.lucent.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 28 Oct 2008 12:46:25 -0500
Content-class: urn:content-classes:message
MIME-Version: 1.0
X-MimeOLE: Produced By Microsoft Exchange V6.5
Date: Tue, 28 Oct 2008 12:46:24 -0500
Message-ID: <A37753B7B7A3134F9366EE6B4052F43B022237FA@ILEXC2U03.ndc.lucent.com>
In-Reply-To: <4906E57E.4050105@pi.nu>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: draft-bocci-mpls-tp-gach-gal-00.txt for mpls wg doc
Thread-Index: Ack46GVmnm5uxhkzTRKke4CwlQvoaQAPHj+A
References: <4906E57E.4050105@pi.nu>
From: "Lam, Hing-Kam \(Kam\)" <hklam@alcatel-lucent.com>
To: <mpls@ietf.org>
X-OriginalArrivalTime: 28 Oct 2008 17:46:25.0548 (UTC)
	FILETIME=[19294CC0:01C93925]
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.39
Subject: Re: [mpls] draft-bocci-mpls-tp-gach-gal-00.txt for mpls wg doc
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mpls-bounces@ietf.org
Errors-To: mpls-bounces@ietf.org

I support <draft-bocci-mpls-tp-gach-gal-00.txt> to become a mpls wg
document.

--Kam

-----Original Message-----
From: owner-ccamp@ops.ietf.org [mailto:owner-ccamp@ops.ietf.org] On
Behalf Of Loa Andersson
Sent: Tuesday, October 28, 2008 6:12 AM
To: mpls@ietf.org; pwe3; ahtmpls@itu.int; ccamp
Subject: draft-bocci-mpls-tp-gach-gal-00.txt for mpls wg doc

Working group(s),

this is to initiate a two week poll to see if
draft-bocci-mpls-tp-gach-gal-00.txt is in shape to
become a mpls working group document.

The current draft is a merge of to earlier draft
one that defined the GAL and another that specified
the generic associated channel.

Please send your responses to the mpls working group
mailing list (needs a bit of discipline, "replay all"
won't do the trick ;) .

Please respond on Tuesday Oct 11 the latest.

/Loa

-- 
Loa Andersson

Principal Networking Architect
Acreo AB                           phone:  +46 8 632 77 14
Isafjordsgatan 22                  mobile: +46 739 81 21 64
Kista, Sweden                      email:  loa.andersson@acreo.se
                                           loa@pi.nu

_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls


From mpls-bounces@ietf.org  Tue Oct 28 10:49:01 2008
Return-Path: <mpls-bounces@ietf.org>
X-Original-To: mpls-archive@megatron.ietf.org
Delivered-To: ietfarch-mpls-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 79CC528C2FB;
	Tue, 28 Oct 2008 10:49:01 -0700 (PDT)
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id A439828C2BA;
	Tue, 28 Oct 2008 10:48:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id BKtoP1T6tlLw; Tue, 28 Oct 2008 10:48:58 -0700 (PDT)
Received: from mail203.messagelabs.com (mail203.messagelabs.com
	[216.82.254.243])
	by core3.amsl.com (Postfix) with ESMTP id B1D7728C17C;
	Tue, 28 Oct 2008 10:48:58 -0700 (PDT)
X-VirusChecked: Checked
X-Env-Sender: arhussain@att.com
X-Msg-Ref: server-9.tower-203.messagelabs.com!1225216134!25167626!1
X-StarScan-Version: 5.5.12.14.2; banners=-,-,-
X-Originating-IP: [144.160.20.54]
Received: (qmail 20878 invoked from network); 28 Oct 2008 17:48:55 -0000
Received: from sbcsmtp7.sbc.com (HELO mlpi135.enaf.sfdc.sbc.com)
	(144.160.20.54)
	by server-9.tower-203.messagelabs.com with AES256-SHA encrypted SMTP;
	28 Oct 2008 17:48:55 -0000
Received: from enaf.sfdc.sbc.com (localhost.localdomain [127.0.0.1])
	by mlpi135.enaf.sfdc.sbc.com (8.14.0/8.14.0) with ESMTP id
	m9SHmrJM028984; Tue, 28 Oct 2008 13:48:54 -0400
Received: from misout7msgusr7e.ugd.att.com (misout7msgusr7e.ugd.att.com
	[144.155.43.107])
	by mlpi135.enaf.sfdc.sbc.com (8.14.0/8.14.0) with ESMTP id
	m9SHmn5L028916; Tue, 28 Oct 2008 13:48:49 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Tue, 28 Oct 2008 13:47:03 -0400
Message-ID: <C6829F7738978D4EAEA69C354B4BA34E0B427B@misout7msgusr7e.ugd.att.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [mpls] draft-bocci-mpls-tp-gach-gal-00.txt for mpls wg doc
Thread-Index: Ack45byfagYrwvvLT9mCMeJee3MqKwANnugwAAI972k=
References: <4906E57E.4050105@pi.nu>
	<4A5028372622294A99B8FFF6BD06EB7B04C95204@USDALSMBS03.ad3.ad.alcatel.com>
From: "HUSSAIN, ARSHAD, ATTLABS" <arhussain@att.com>
To: "Loa Andersson" <loa@pi.nu>, <mpls@ietf.org>, "pwe3" <pwe3@ietf.org>,
	<ahtmpls@itu.int>, "ccamp" <ccamp@ops.ietf.org>
Subject: Re: [mpls] draft-bocci-mpls-tp-gach-gal-00.txt for mpls wg doc
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mpls-bounces@ietf.org
Errors-To: mpls-bounces@ietf.org

I support the draft as a WG document.
 
Arshad Hussain
AT&T Labs.

________________________________

From: mpls-bounces@ietf.org on behalf of AISSAOUI Mustapha
Sent: Tue 10/28/2008 11:43 AM
To: Loa Andersson; mpls@ietf.org; pwe3; ahtmpls@itu.int; ccamp
Subject: Re: [mpls] draft-bocci-mpls-tp-gach-gal-00.txt for mpls wg doc



support.

Mustapha.

> -----Original Message-----
> From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On
> Behalf Of Loa Andersson
> Sent: Tuesday, October 28, 2008 6:12 AM
> To: mpls@ietf.org; pwe3; ahtmpls@itu.int; ccamp
> Subject: [mpls] draft-bocci-mpls-tp-gach-gal-00.txt for mpls wg doc
>
> Working group(s),
>
> this is to initiate a two week poll to see if
> draft-bocci-mpls-tp-gach-gal-00.txt is in shape to become a
> mpls working group document.
>
> The current draft is a merge of to earlier draft one that
> defined the GAL and another that specified the generic
> associated channel.
>
> Please send your responses to the mpls working group mailing
> list (needs a bit of discipline, "replay all"
> won't do the trick ;) .
>
> Please respond on Tuesday Oct 11 the latest.
>
> /Loa
>
> --
> Loa Andersson
>
> Principal Networking Architect
> Acreo AB                           phone:  +46 8 632 77 14
> Isafjordsgatan 22                  mobile: +46 739 81 21 64
> Kista, Sweden                      email:  loa.andersson@acreo.se
>                                            loa@pi.nu
> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls
>
_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls


_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls


From mpls-bounces@ietf.org  Tue Oct 28 10:53:19 2008
Return-Path: <mpls-bounces@ietf.org>
X-Original-To: mpls-archive@megatron.ietf.org
Delivered-To: ietfarch-mpls-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 5AD1928C335;
	Tue, 28 Oct 2008 10:53:19 -0700 (PDT)
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id CB7EA3A696C
	for <mpls@core3.amsl.com>; Tue, 28 Oct 2008 10:53:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.43
X-Spam-Level: 
X-Spam-Status: No, score=-1.43 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, HELO_EQ_AT=0.424, HOST_EQ_AT=0.745]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id RQYROW3-hXSt for <mpls@core3.amsl.com>;
	Tue, 28 Oct 2008 10:53:18 -0700 (PDT)
Received: from viefep11-int.chello.at (viefep11-int.chello.at [62.179.121.31])
	by core3.amsl.com (Postfix) with ESMTP id 716A128C335
	for <mpls@ietf.org>; Tue, 28 Oct 2008 10:53:17 -0700 (PDT)
Received: from edge05.upc.biz ([192.168.13.212]) by viefep11-int.chello.at
	(InterMail vM.7.08.02.02 201-2186-121-104-20070414) with ESMTP
	id <20081028175309.XVRR2884.viefep11-int.chello.at@edge05.upc.biz>;
	Tue, 28 Oct 2008 18:53:09 +0100
Received: from McAsterix.local ([24.132.228.153]) by edge05.upc.biz with edge
	id YHt61a0603KDBhC05Ht8UU; Tue, 28 Oct 2008 18:53:09 +0100
X-SourceIP: 24.132.228.153
Message-ID: <49075182.10201@chello.nl>
Date: Tue, 28 Oct 2008 18:53:06 +0100
From: Huub van Helvoort <hhelvoort@chello.nl>
User-Agent: Thunderbird 2.0.0.17 (Macintosh/20080914)
MIME-Version: 1.0
To: Loa Andersson <loa@pi.nu>
References: <4906E57E.4050105@pi.nu>
In-Reply-To: <4906E57E.4050105@pi.nu>
Cc: "mpls@ietf.org" <mpls@ietf.org>
Subject: Re: [mpls] draft-bocci-mpls-tp-gach-gal-00.txt for mpls wg doc
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: hhelvoort@chello.nl
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: mpls-bounces@ietf.org
Errors-To: mpls-bounces@ietf.org

Hi,

I support this draft to become WG draft.

Cheers, Huub.

> Working group(s),
> 
> this is to initiate a two week poll to see if
> draft-bocci-mpls-tp-gach-gal-00.txt is in shape to
> become a mpls working group document.
> 
> The current draft is a merge of to earlier draft
> one that defined the GAL and another that specified
> the generic associated channel.
> 
> Please send your responses to the mpls working group
> mailing list (needs a bit of discipline, "replay all"
> won't do the trick ;) .
> 
> Please respond on Tuesday Oct 11 the latest.
> 
> /Loa
> 

-- 
================================================================
                   http://www.van-helvoort.eu/
================================================================
Always remember that you are unique...just like everyone else...
_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls


From mpls-bounces@ietf.org  Tue Oct 28 11:23:07 2008
Return-Path: <mpls-bounces@ietf.org>
X-Original-To: mpls-archive@megatron.ietf.org
Delivered-To: ietfarch-mpls-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 417AF3A6C9B;
	Tue, 28 Oct 2008 11:23:07 -0700 (PDT)
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 1804328C268
	for <mpls@core3.amsl.com>; Tue, 28 Oct 2008 11:23:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, STOX_REPLY_TYPE=0.001]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id gCr-j8JDqUmS for <mpls@core3.amsl.com>;
	Tue, 28 Oct 2008 11:23:05 -0700 (PDT)
Received: from asmtp1.iomartmail.com (asmtp1.iomartmail.com [62.128.201.248])
	by core3.amsl.com (Postfix) with ESMTP id E5F493A69B0
	for <mpls@ietf.org>; Tue, 28 Oct 2008 11:23:04 -0700 (PDT)
Received: from asmtp1.iomartmail.com (localhost.localdomain [127.0.0.1])
	by asmtp1.iomartmail.com (8.12.11.20060308/8.12.8) with ESMTP id
	m9SIN0XC013699; Tue, 28 Oct 2008 18:23:02 GMT
Received: from your029b8cecfe (dsl-sp-81-140-15-32.in-addr.broadbandscope.com
	[81.140.15.32]) (authenticated bits=0)
	by asmtp1.iomartmail.com (8.12.11.20060308/8.12.11) with ESMTP id
	m9SIMxHC013652; Tue, 28 Oct 2008 18:22:59 GMT
Message-ID: <E2075D5931364C61A7D9DF7C24E1E367@your029b8cecfe>
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: <julien.meuric@orange-ftgroup.com>
References: <002801c935f2$9229cae0$0200a8c0@your029b8cecfe>
	<7DBAFEC6A76F3E42817DF1EBE64CB02605F7FFED@ftrdmel2>
Date: Tue, 28 Oct 2008 18:11:41 -0000
MIME-Version: 1.0
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.5512
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579
Cc: mpls@ietf.org
Subject: Re: [mpls] A BNF specification for RSVP-TE
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Adrian Farrel <adrian@olddog.co.uk>
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: mpls-bounces@ietf.org
Errors-To: mpls-bounces@ietf.org

Julien,

Thanks for reading.

> Here are a few comments on your ID.
>
> **********
> There is no ToC. Adding one might help to understand why the "Operators"
> section is numbered 2.2 and not 2.1.5 (I'm a bit lost here).

I can add a ToC.
One is not required in an I-D of this length, but if it would be helpful...

Operators is 2.2 so that section 2.2.1. does not need to be 2.1.5.1 :-)

> **********
> Section 2.2.1: you define the assigment operator by saying both sides
> are "equivalent". I feel this very notion of "equivalence" is not
> specified enough in our context of grammar definition and the operation
> described is "stronger" than a usual equivalence noted "~". However, as
> a non native, I know my interpretation is biased. Wouldn't a definition
> relying on terms such as "synonymous", "equal", "identical",
> "substituable"... (sure you'll find better words than me) make it
> sharper?

adjective
1. equal in value, measure, force, effect, significance, etc.

I shall use "is set equal to"

> **********
> Section 2.2.3: nesting appears only as an example. I would find it more
> consistent if the sentence "The optional operator can be nested" were
> moved into the paragraph "Meaning".

I can do that.

> **********
> Section 2.2.4: the encoding is defined by a full sentence (including
> subject, verb...), thus creating an exception in the form of the
> document. (Would I have raised this if the author was different? ;-) )

Sorry, I will try to use less complete sentences in future documents that I 
write.

> **********
> Section 2.2.5: my 1st reaction when reading the example is what you say
> right after about grouping using round braquets instead of square ones.
> The direct consequence of your example is that the operator "..." is
> also defined for nil, which was not obvious before.

Hmmm. I'm not sure what you are saying.

> Second reaction: why those outer square brackets? Grouping could have
> been used (even if useless), but why this double level of optionality? I
> find it rather confusing and would have prefered:
> - either "[ <MESSAGE_ID_ACK> | <MESSAGE_ID_NACK> ] ..."
> - or "[  ( <MESSAGE_ID_ACK> | <MESSAGE_ID_NACK> ) ... ]"

Nearly all examples are taken from existing documents. I will add the 
reference to RFC 3473 so that people don't think this is *my* mistake.

> Side question: I'm sure you're correct on "more clear" at the end of the
> section, but your humble servant definitely requires an English grammar
> lesson to understand why you prefered it to "clearer".

In general, monosylabic adjectives use -er for comparatives, while 
polysylabic adjectives use "more."
However, sometimes, for stress or the feel of the sentence, one uses "more".

> **********
> Section 2.2.6, note 1: "grouping [...] is RECOMMENDED as a solution for
> multi-alternates" while section 2.2.4 says about multi-alternates:
> "explicit grouping [...] or an intermediary MUST be used". OPTIONAL can
> be considered, but I'd favor MANDATORY; anyway consistency MUST be
> achieved whithin the ID.

You're right that RECOMMENDED has the same level as SHOULD.

I'll make the text in both say that

"explicit grouping [...] or an intermediary MUST be used"

> **********
> Section 2.4: to depict the possible misinterpretation due to line
> breaks, you'd better add an example such as:
> <flow descriptor list> ::=  <empty> | <flow descriptor list>
>                           <flow descriptor>
> where the reader is really tempted by formulation "b" because of the
> line break, while precedence leaves only "a" as an option.

I agree that this would tempt people to the wrong thing.
Turns out there are no real examples of this misue that I can find, so I 
think I will not try to make the examples comprehensive, and rely on the 
rules.

> **********
> Section 5: I'd have swapped "defective" and "incompatible" in the last
> paragraph since security attacks applies to the (former) former, not to
> the (former) latter.

OK

Thanks,
Adrian 

_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls


From mpls-bounces@ietf.org  Tue Oct 28 11:33:51 2008
Return-Path: <mpls-bounces@ietf.org>
X-Original-To: mpls-archive@megatron.ietf.org
Delivered-To: ietfarch-mpls-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id D792028C322;
	Tue, 28 Oct 2008 11:33:51 -0700 (PDT)
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id D69A03A6C9F;
	Tue, 28 Oct 2008 11:33:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, STOX_REPLY_TYPE=0.001]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id jNerKPDE5bgE; Tue, 28 Oct 2008 11:33:49 -0700 (PDT)
Received: from asmtp1.iomartmail.com (asmtp1.iomartmail.com [62.128.201.248])
	by core3.amsl.com (Postfix) with ESMTP id CC0833A6C6C;
	Tue, 28 Oct 2008 11:33:48 -0700 (PDT)
Received: from asmtp1.iomartmail.com (localhost.localdomain [127.0.0.1])
	by asmtp1.iomartmail.com (8.12.11.20060308/8.12.8) with ESMTP id
	m9SIXWW1015400; Tue, 28 Oct 2008 18:33:32 GMT
Received: from your029b8cecfe (dsl-sp-81-140-15-32.in-addr.broadbandscope.com
	[81.140.15.32]) (authenticated bits=0)
	by asmtp1.iomartmail.com (8.12.11.20060308/8.12.11) with ESMTP id
	m9SIXViZ015394; Tue, 28 Oct 2008 18:33:31 GMT
Message-ID: <E53AE93AB87440CA8018F03124A37C4F@your029b8cecfe>
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "Loa Andersson" <loa@pi.nu>, "ccamp" <ccamp@ops.ietf.org>
References: <4906E57E.4050105@pi.nu>
Date: Tue, 28 Oct 2008 18:33:28 -0000
MIME-Version: 1.0
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.5512
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579
Cc: mpls@ietf.org, pwe3 <pwe3@ietf.org>, ahtmpls@itu.int
Subject: Re: [mpls] [PWE3] draft-bocci-mpls-tp-gach-gal-00.txt for mpls wg
	doc
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Adrian Farrel <adrian@olddog.co.uk>
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: mpls-bounces@ietf.org
Errors-To: mpls-bounces@ietf.org

Support
----- Original Message ----- 
From: "Loa Andersson" <loa@pi.nu>
To: <mpls@ietf.org>; "pwe3" <pwe3@ietf.org>; <ahtmpls@itu.int>; "ccamp" 
<ccamp@ops.ietf.org>
Sent: Tuesday, October 28, 2008 10:12 AM
Subject: [PWE3] draft-bocci-mpls-tp-gach-gal-00.txt for mpls wg doc


> Working group(s),
>
> this is to initiate a two week poll to see if
> draft-bocci-mpls-tp-gach-gal-00.txt is in shape to
> become a mpls working group document.
>
> The current draft is a merge of to earlier draft
> one that defined the GAL and another that specified
> the generic associated channel.
>
> Please send your responses to the mpls working group
> mailing list (needs a bit of discipline, "replay all"
> won't do the trick ;) .
>
> Please respond on Tuesday Oct 11 the latest.
>
> /Loa
>
> -- 
> Loa Andersson
>
> Principal Networking Architect
> Acreo AB                           phone:  +46 8 632 77 14
> Isafjordsgatan 22                  mobile: +46 739 81 21 64
> Kista, Sweden                      email:  loa.andersson@acreo.se
>                                           loa@pi.nu
> _______________________________________________
> pwe3 mailing list
> pwe3@ietf.org
> https://www.ietf.org/mailman/listinfo/pwe3
> 

_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls


From mpls-bounces@ietf.org  Tue Oct 28 14:29:55 2008
Return-Path: <mpls-bounces@ietf.org>
X-Original-To: mpls-archive@megatron.ietf.org
Delivered-To: ietfarch-mpls-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E184F28C2C9;
	Tue, 28 Oct 2008 14:29:54 -0700 (PDT)
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 64CB83A6CB9
	for <mpls@core3.amsl.com>; Tue, 28 Oct 2008 14:29:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.299
X-Spam-Level: 
X-Spam-Status: No, score=-5.299 tagged_above=-999 required=5 tests=[AWL=1.300, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 8++hDVjrlwjI for <mpls@core3.amsl.com>;
	Tue, 28 Oct 2008 14:29:53 -0700 (PDT)
Received: from rtp-iport-2.cisco.com (rtp-iport-2.cisco.com [64.102.122.149])
	by core3.amsl.com (Postfix) with ESMTP id 5CCDC28C2DE
	for <mpls@ietf.org>; Tue, 28 Oct 2008 14:29:53 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,501,1220227200"; d="scan'208";a="25943055"
Received: from rtp-dkim-1.cisco.com ([64.102.121.158])
	by rtp-iport-2.cisco.com with ESMTP; 28 Oct 2008 21:29:51 +0000
Received: from rtp-core-1.cisco.com (rtp-core-1.cisco.com [64.102.124.12])
	by rtp-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id m9SLTpEk015673; 
	Tue, 28 Oct 2008 17:29:51 -0400
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com
	[64.102.31.12])
	by rtp-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m9SLTpgj019949;
	Tue, 28 Oct 2008 21:29:51 GMT
Received: from xmb-rtp-206.amer.cisco.com ([64.102.31.32]) by
	xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 28 Oct 2008 17:29:51 -0400
Received: from 10.98.32.163 ([10.98.32.163]) by xmb-rtp-206.amer.cisco.com
	([64.102.31.32]) with Microsoft Exchange Server HTTP-DAV ; 
	Tue, 28 Oct 2008 21:29:45 +0000
User-Agent: Microsoft-Entourage/12.13.0.080930
Date: Tue, 28 Oct 2008 17:29:44 -0400
From: George Swallow <swallow@cisco.com>
To: Loa Andersson <loa@pi.nu>, <mpls@ietf.org>
Message-ID: <C52CFC88.9CD1%swallow@cisco.com>
Thread-Topic: [mpls] draft-bocci-mpls-tp-gach-gal-00.txt for mpls wg doc
Thread-Index: Ack45byfagYrwvvLT9mCMeJee3MqKwANnugwAAoEwGI=
In-Reply-To: <4A5028372622294A99B8FFF6BD06EB7B04C95204@USDALSMBS03.ad3.ad.alcatel.com>
Mime-version: 1.0
X-OriginalArrivalTime: 28 Oct 2008 21:29:51.0229 (UTC)
	FILETIME=[4F91E2D0:01C93944]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=25; t=1225229392; x=1226093392;
	c=relaxed/simple; s=rtpdkim1001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=swallow@cisco.com;
	z=From:=20George=20Swallow=20<swallow@cisco.com>
	|Subject:=20Re=3A=20[mpls]=20draft-bocci-mpls-tp-gach-gal-0
	0.txt=20for=20mpls=20wg=20doc |Sender:=20
	|To:=20Loa=20Andersson=20<loa@pi.nu>,=20<mpls@ietf.org>;
	bh=FZOyoip35RPqIS3Q53l/DBhaIrxX0pL1W1qdk6s+ghI=;
	b=EEcfHvrn3q/PR03+jnn0iqiiDuI2jqmwrkKpv7ZY36qtTSsuQMaSn9cPf1
	IagowIsoxKvdWyZnFUARva3saP/AzVxKrG6hCZqpschanr1j4z451kW0iU2H
	l/jhFPC6K0;
Authentication-Results: rtp-dkim-1; header.From=swallow@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim1001 verified; ); 
Subject: Re: [mpls] draft-bocci-mpls-tp-gach-gal-00.txt for mpls wg doc
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mpls-bounces@ietf.org
Errors-To: mpls-bounces@ietf.org


Support.

...George


_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls


From mpls-bounces@ietf.org  Tue Oct 28 16:57:41 2008
Return-Path: <mpls-bounces@ietf.org>
X-Original-To: mpls-archive@megatron.ietf.org
Delivered-To: ietfarch-mpls-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 947CE28C2CF;
	Tue, 28 Oct 2008 16:57:41 -0700 (PDT)
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 70DFC3A6959;
	Tue, 28 Oct 2008 16:57:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id F-RgWvqHVIX8; Tue, 28 Oct 2008 16:57:39 -0700 (PDT)
Received: from ihemail2.lucent.com (ihemail2.lucent.com [135.245.0.35])
	by core3.amsl.com (Postfix) with ESMTP id 95B8E3A6953;
	Tue, 28 Oct 2008 16:57:38 -0700 (PDT)
Received: from ilexp03.ndc.lucent.com (h135-3-39-50.lucent.com [135.3.39.50])
	by ihemail2.lucent.com (8.13.8/IER-o) with ESMTP id m9SNvYaH029290; 
	Tue, 28 Oct 2008 18:57:35 -0500 (CDT)
Received: from inexp02.in.lucent.com ([135.254.223.66]) by
	ilexp03.ndc.lucent.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 28 Oct 2008 18:57:34 -0500
Received: from INEXC1U01.in.lucent.com ([135.254.223.25]) by
	inexp02.in.lucent.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 29 Oct 2008 05:27:28 +0530
Content-class: urn:content-classes:message
MIME-Version: 1.0
X-MimeOLE: Produced By Microsoft Exchange V6.5
Date: Wed, 29 Oct 2008 05:27:51 +0530
Message-ID: <6D26D1FE43A66F439F8109CDD4241965020E933C@INEXC1U01.in.lucent.com>
In-Reply-To: <4906E57E.4050105@pi.nu>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [PWE3] draft-bocci-mpls-tp-gach-gal-00.txt for mpls wg doc
Thread-Index: Ack45bUGrlNTVozhT3OOzOfxULkNngAc0CAQ
References: <4906E57E.4050105@pi.nu>
From: "Dutta, Pranjal K \(Pranjal\)" <pdutta@alcatel-lucent.com>
To: "Loa Andersson" <loa@pi.nu>, <mpls@ietf.org>, "pwe3" <pwe3@ietf.org>,
	<ahtmpls@itu.int>, "ccamp" <ccamp@ops.ietf.org>
X-OriginalArrivalTime: 28 Oct 2008 23:57:28.0609 (UTC)
	FILETIME=[EEFAD110:01C93958]
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.35
Subject: Re: [mpls] [PWE3] draft-bocci-mpls-tp-gach-gal-00.txt for mpls wg
	doc
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mpls-bounces@ietf.org
Errors-To: mpls-bounces@ietf.org

Support.

Thanks,
Pranjal 

-----Original Message-----
From: pwe3-bounces@ietf.org [mailto:pwe3-bounces@ietf.org] On Behalf Of
Loa Andersson
Sent: Tuesday, October 28, 2008 3:12 AM
To: mpls@ietf.org; pwe3; ahtmpls@itu.int; ccamp
Subject: [PWE3] draft-bocci-mpls-tp-gach-gal-00.txt for mpls wg doc

Working group(s),

this is to initiate a two week poll to see if
draft-bocci-mpls-tp-gach-gal-00.txt is in shape to become a mpls working
group document.

The current draft is a merge of to earlier draft one that defined the
GAL and another that specified the generic associated channel.

Please send your responses to the mpls working group mailing list (needs
a bit of discipline, "replay all"
won't do the trick ;) .

Please respond on Tuesday Oct 11 the latest.

/Loa

--
Loa Andersson

Principal Networking Architect
Acreo AB                           phone:  +46 8 632 77 14
Isafjordsgatan 22                  mobile: +46 739 81 21 64
Kista, Sweden                      email:  loa.andersson@acreo.se
                                           loa@pi.nu
_______________________________________________
pwe3 mailing list
pwe3@ietf.org
https://www.ietf.org/mailman/listinfo/pwe3
_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls


From mpls-bounces@ietf.org  Tue Oct 28 22:47:13 2008
Return-Path: <mpls-bounces@ietf.org>
X-Original-To: mpls-archive@megatron.ietf.org
Delivered-To: ietfarch-mpls-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 7EE953A687C;
	Tue, 28 Oct 2008 22:47:13 -0700 (PDT)
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id CB6813A687C;
	Tue, 28 Oct 2008 22:47:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.249
X-Spam-Level: 
X-Spam-Status: No, score=-2.249 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, HELO_EQ_FR=0.35]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id WLGjkAoYIMO8; Tue, 28 Oct 2008 22:47:11 -0700 (PDT)
Received: from smail6.alcatel.fr (gc-na5.alcatel.fr [64.208.49.5])
	by core3.amsl.com (Postfix) with ESMTP id D5C8E3A6801;
	Tue, 28 Oct 2008 22:47:10 -0700 (PDT)
Received: from FRVELSBHS05.ad2.ad.alcatel.com (frvelsbhs05.ad2.ad.alcatel.com
	[155.132.6.77])
	by smail6.alcatel.fr (8.13.8/8.13.8/ICT) with ESMTP id m9T5l6Us016263; 
	Wed, 29 Oct 2008 06:47:07 +0100
Received: from FRVELSMBS22.ad2.ad.alcatel.com ([155.132.6.56]) by
	FRVELSBHS05.ad2.ad.alcatel.com with Microsoft
	SMTPSVC(6.0.3790.2499); Wed, 29 Oct 2008 06:47:06 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Wed, 29 Oct 2008 06:47:06 +0100
Message-ID: <B128F666D4C8BD4FBF56CEAFB2DB66D70393B9CA@FRVELSMBS22.ad2.ad.alcatel.com>
In-Reply-To: <6D26D1FE43A66F439F8109CDD4241965020E933C@INEXC1U01.in.lucent.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [PWE3] draft-bocci-mpls-tp-gach-gal-00.txt for mpls wg doc
Thread-Index: Ack45bUGrlNTVozhT3OOzOfxULkNngAc0CAQAAwzqGA=
References: <4906E57E.4050105@pi.nu>
	<6D26D1FE43A66F439F8109CDD4241965020E933C@INEXC1U01.in.lucent.com>
From: "HENDERICKX Wim" <wim.henderickx@alcatel-lucent.be>
To: "DUTTA Pranjal" <pdutta@alcatel-lucent.com>, "Loa Andersson" <loa@pi.nu>, 
	<mpls@ietf.org>, "pwe3" <pwe3@ietf.org>, <ahtmpls@itu.int>,
	"ccamp" <ccamp@ops.ietf.org>
X-OriginalArrivalTime: 29 Oct 2008 05:47:06.0823 (UTC)
	FILETIME=[C6F83D70:01C93989]
X-Scanned-By: MIMEDefang 2.57 on 155.132.188.84
Subject: Re: [mpls] [PWE3] draft-bocci-mpls-tp-gach-gal-00.txt for mpls wg
	doc
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mpls-bounces@ietf.org
Errors-To: mpls-bounces@ietf.org

support 

-----Original Message-----
From: pwe3-bounces@ietf.org [mailto:pwe3-bounces@ietf.org] On Behalf Of
DUTTA Pranjal
Sent: woensdag 29 oktober 2008 0:58
To: Loa Andersson; mpls@ietf.org; pwe3; ahtmpls@itu.int; ccamp
Subject: Re: [PWE3] draft-bocci-mpls-tp-gach-gal-00.txt for mpls wg doc

Support.

Thanks,
Pranjal 

-----Original Message-----
From: pwe3-bounces@ietf.org [mailto:pwe3-bounces@ietf.org] On Behalf Of
Loa Andersson
Sent: Tuesday, October 28, 2008 3:12 AM
To: mpls@ietf.org; pwe3; ahtmpls@itu.int; ccamp
Subject: [PWE3] draft-bocci-mpls-tp-gach-gal-00.txt for mpls wg doc

Working group(s),

this is to initiate a two week poll to see if
draft-bocci-mpls-tp-gach-gal-00.txt is in shape to become a mpls working
group document.

The current draft is a merge of to earlier draft one that defined the
GAL and another that specified the generic associated channel.

Please send your responses to the mpls working group mailing list (needs
a bit of discipline, "replay all"
won't do the trick ;) .

Please respond on Tuesday Oct 11 the latest.

/Loa

--
Loa Andersson

Principal Networking Architect
Acreo AB                           phone:  +46 8 632 77 14
Isafjordsgatan 22                  mobile: +46 739 81 21 64
Kista, Sweden                      email:  loa.andersson@acreo.se
                                           loa@pi.nu
_______________________________________________
pwe3 mailing list
pwe3@ietf.org
https://www.ietf.org/mailman/listinfo/pwe3
_______________________________________________
pwe3 mailing list
pwe3@ietf.org
https://www.ietf.org/mailman/listinfo/pwe3
_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls


From mpls-bounces@ietf.org  Wed Oct 29 01:14:36 2008
Return-Path: <mpls-bounces@ietf.org>
X-Original-To: mpls-archive@megatron.ietf.org
Delivered-To: ietfarch-mpls-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B6EE13A6CDD;
	Wed, 29 Oct 2008 01:14:36 -0700 (PDT)
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 95BCB3A6CD3;
	Wed, 29 Oct 2008 01:14:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.249
X-Spam-Level: 
X-Spam-Status: No, score=-6.249 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id QZjqqAVemoJD; Wed, 29 Oct 2008 01:14:34 -0700 (PDT)
Received: from mailgw3.ericsson.se (mailgw3.ericsson.se [193.180.251.60])
	by core3.amsl.com (Postfix) with ESMTP id B5F8C3A6CDD;
	Wed, 29 Oct 2008 01:14:33 -0700 (PDT)
Received: from mailgw3.ericsson.se (unknown [127.0.0.1])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	DF02220E23; Wed, 29 Oct 2008 09:14:31 +0100 (CET)
X-AuditID: c1b4fb3c-ab8c9bb0000015b5-d2-49081b671961
Received: from esealmw126.eemea.ericsson.se (unknown [153.88.254.123])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	8579820E1C; Wed, 29 Oct 2008 09:14:31 +0100 (CET)
Received: from esealmw118.eemea.ericsson.se ([153.88.200.77]) by
	esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 29 Oct 2008 09:13:55 +0100
Content-class: urn:content-classes:message
MIME-Version: 1.0
X-MimeOLE: Produced By Microsoft Exchange V6.5
Date: Wed, 29 Oct 2008 09:13:48 +0100
Message-ID: <93DFCD4B101EB440B5B72997456C5F9402CE5698@esealmw118.eemea.ericsson.se>
In-Reply-To: <4906E57E.4050105@pi.nu>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [mpls] draft-bocci-mpls-tp-gach-gal-00.txt for mpls wg doc
Thread-Index: Ack5FN/J0MB3zRkHTdaQyMxPQWY0SgAiGJgg
References: <4906E57E.4050105@pi.nu>
From: "Annamaria Fulignoli" <annamaria.fulignoli@ericsson.com>
To: "Loa Andersson" <loa@pi.nu>, <mpls@ietf.org>, "pwe3" <pwe3@ietf.org>,
	<ahtmpls@itu.int>, "ccamp" <ccamp@ops.ietf.org>
X-OriginalArrivalTime: 29 Oct 2008 08:13:55.0779 (UTC)
	FILETIME=[49844130:01C9399E]
X-Brightmail-Tracker: AAAAAA==
Subject: Re: [mpls] draft-bocci-mpls-tp-gach-gal-00.txt for mpls wg doc
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: mpls-bounces@ietf.org
Errors-To: mpls-bounces@ietf.org

I support.

Best Regards, =

Annamaria =


-----Original Message-----
From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf Of Loa=
 Andersson
Sent: marted=EC 28 ottobre 2008 11.12
To: mpls@ietf.org; pwe3; ahtmpls@itu.int; ccamp
Subject: [mpls] draft-bocci-mpls-tp-gach-gal-00.txt for mpls wg doc

Working group(s),

this is to initiate a two week poll to see if draft-bocci-mpls-tp-gach-gal-=
00.txt is in shape to become a mpls working group document.

The current draft is a merge of to earlier draft one that defined the GAL a=
nd another that specified the generic associated channel.

Please send your responses to the mpls working group mailing list (needs a =
bit of discipline, "replay all"
won't do the trick ;) .

Please respond on Tuesday Oct 11 the latest.

/Loa

--
Loa Andersson

Principal Networking Architect
Acreo AB                           phone:  +46 8 632 77 14
Isafjordsgatan 22                  mobile: +46 739 81 21 64
Kista, Sweden                      email:  loa.andersson@acreo.se
                                           loa@pi.nu ______________________=
_________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls
_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls


From mpls-bounces@ietf.org  Wed Oct 29 02:43:48 2008
Return-Path: <mpls-bounces@ietf.org>
X-Original-To: mpls-archive@megatron.ietf.org
Delivered-To: ietfarch-mpls-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B48393A6CF2;
	Wed, 29 Oct 2008 02:43:48 -0700 (PDT)
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B3C843A6CEF
	for <mpls@core3.amsl.com>; Wed, 29 Oct 2008 02:43:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.249
X-Spam-Level: 
X-Spam-Status: No, score=-3.249 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, HELO_EQ_FR=0.35, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id R32yf7IClZmU for <mpls@core3.amsl.com>;
	Wed, 29 Oct 2008 02:43:46 -0700 (PDT)
Received: from p-mail2.rd.francetelecom.com (p-mail2.rd.francetelecom.com
	[195.101.245.16])
	by core3.amsl.com (Postfix) with ESMTP id 702B83A6CEA
	for <mpls@ietf.org>; Wed, 29 Oct 2008 02:43:46 -0700 (PDT)
Received: from FTRDMEL2.rd.francetelecom.fr ([10.193.117.153]) by
	ftrdsmtp1.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 29 Oct 2008 10:43:42 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Wed, 29 Oct 2008 10:43:11 +0100
Message-ID: <7DBAFEC6A76F3E42817DF1EBE64CB02605F800EF@ftrdmel2>
In-Reply-To: <E2075D5931364C61A7D9DF7C24E1E367@your029b8cecfe>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [mpls] A BNF specification for RSVP-TE
Thread-Index: Ack5KkrdKel+0rBaSC2pSDYyUvRILwAe3pyw
References: <002801c935f2$9229cae0$0200a8c0@your029b8cecfe>
	<7DBAFEC6A76F3E42817DF1EBE64CB02605F7FFED@ftrdmel2>
	<E2075D5931364C61A7D9DF7C24E1E367@your029b8cecfe>
From: <julien.meuric@orange-ftgroup.com>
To: <adrian@olddog.co.uk>
X-OriginalArrivalTime: 29 Oct 2008 09:43:42.0622 (UTC)
	FILETIME=[D45343E0:01C939AA]
Cc: mpls@ietf.org
Subject: Re: [mpls] A BNF specification for RSVP-TE
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mpls-bounces@ietf.org
Errors-To: mpls-bounces@ietf.org

Hello Adrian.

I snipped to remaining issues only and prefixed my comments with "[JM]".


-----Original Message-----
From: Adrian Farrel [mailto:adrian@olddog.co.uk] 

<snip>

> **********
> There is no ToC. Adding one might help to understand why the "Operators"
> section is numbered 2.2 and not 2.1.5 (I'm a bit lost here).

I can add a ToC.
One is not required in an I-D of this length, but if it would be helpful...

Operators is 2.2 so that section 2.2.1. does not need to be 2.1.5.1 :-)

[JM] Coming from you, that kind of reason is rather weird... but you're the author. ;-)

<snip>

> **********
> Section 2.2.4: the encoding is defined by a full sentence (including
> subject, verb...), thus creating an exception in the form of the
> document. (Would I have raised this if the author was different? ;-) )

Sorry, I will try to use less complete sentences in future documents that I 
write.

[JM] Sounds great! :-)  (Note that the exception I mentioned only applied among the "Encoding" sections, not the whole of the document.)

> **********
> Section 2.2.5: my 1st reaction when reading the example is what you say
> right after about grouping using round braquets instead of square ones.
> The direct consequence of your example is that the operator "..." is
> also defined for nil, which was not obvious before.

Hmmm. I'm not sure what you are saying.

[JM] Sorry if my writing was confusing. I was refering to the last note of 2.2.5. Let me try to rephrase.
You're defining the operator "...". It applies to an object or a construct, but I first wondered on what set/domain (that word again?!) the function was defined. Indeed, the early specification doesn't state if this operator/function is defined for the empty construct or not. A piece of answer if provided in the last example: "[ <MESSAGE_ID_ACK> | <MESSAGE_ID_NACK> ] ..." reveals that "..." can be applied to an empty construct as the optional part, marked by the square braquets, could be equal to the empty set.
Am I more clear now?

<snip>

Best regards,

Julien
_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls


From mpls-bounces@ietf.org  Wed Oct 29 04:22:14 2008
Return-Path: <mpls-bounces@ietf.org>
X-Original-To: mpls-archive@megatron.ietf.org
Delivered-To: ietfarch-mpls-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 54B413A6CD3;
	Wed, 29 Oct 2008 04:22:14 -0700 (PDT)
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 4897B3A6CD3
	for <mpls@core3.amsl.com>; Wed, 29 Oct 2008 04:22:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.745
X-Spam-Level: 
X-Spam-Status: No, score=-4.745 tagged_above=-999 required=5 tests=[AWL=1.854, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id aH8olQuBoF1o for <mpls@core3.amsl.com>;
	Wed, 29 Oct 2008 04:22:12 -0700 (PDT)
Received: from imr1.ericy.com (imr1.ericy.com [198.24.6.9])
	by core3.amsl.com (Postfix) with ESMTP id 7F7133A6AEA
	for <mpls@ietf.org>; Wed, 29 Oct 2008 04:22:12 -0700 (PDT)
Received: from eusrcmw750.eamcs.ericsson.se (eusrcmw750.exu.ericsson.se
	[138.85.77.50])
	by imr1.ericy.com (8.13.1/8.13.1) with ESMTP id m9TBNlOU027266;
	Wed, 29 Oct 2008 06:23:47 -0500
Received: from eusrcmw721.eamcs.ericsson.se ([138.85.77.21]) by
	eusrcmw750.eamcs.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 29 Oct 2008 06:22:09 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Wed, 29 Oct 2008 06:22:09 -0500
Message-ID: <941D5DCD8C42014FAF70FB7424686DCF0405AC40@eusrcmw721.eamcs.ericsson.se>
In-Reply-To: <4906E57E.4050105@pi.nu>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [mpls] draft-bocci-mpls-tp-gach-gal-00.txt for mpls wg doc
Thread-Index: Ack5FO1/7uicLo+AS2KdsDTRVAL51wAlteHw
References: <4906E57E.4050105@pi.nu>
From: "Eric Gray" <eric.gray@ericsson.com>
To: <mpls@ietf.org>
X-OriginalArrivalTime: 29 Oct 2008 11:22:09.0922 (UTC)
	FILETIME=[9559B620:01C939B8]
Subject: Re: [mpls] draft-bocci-mpls-tp-gach-gal-00.txt for mpls wg doc
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mpls-bounces@ietf.org
Errors-To: mpls-bounces@ietf.org

I support making draft-bocci-mpls-tp-gach-gal-* a WG draft.

(I also recommend not including any WG other than the MPLS WG
 in the list of addressees...)

--
Eric Gray
Principal Engineer
Ericsson  

> -----Original Message-----
> From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On 
> Behalf Of Loa Andersson
> Sent: Tuesday, October 28, 2008 6:12 AM
> To: mpls@ietf.org; pwe3; ahtmpls@itu.int; ccamp
> Subject: [mpls] draft-bocci-mpls-tp-gach-gal-00.txt for mpls wg doc
> 
> Working group(s),
> 
> this is to initiate a two week poll to see if
> draft-bocci-mpls-tp-gach-gal-00.txt is in shape to
> become a mpls working group document.
> 
> The current draft is a merge of to earlier draft
> one that defined the GAL and another that specified
> the generic associated channel.
> 
> Please send your responses to the mpls working group
> mailing list (needs a bit of discipline, "replay all"
> won't do the trick ;) .
> 
> Please respond on Tuesday Oct 11 the latest.
> 
> /Loa
> 
> -- 
> Loa Andersson
> 
> Principal Networking Architect
> Acreo AB                           phone:  +46 8 632 77 14
> Isafjordsgatan 22                  mobile: +46 739 81 21 64
> Kista, Sweden                      email:  loa.andersson@acreo.se
>                                            loa@pi.nu
> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls
> 
_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls


From mpls-bounces@ietf.org  Wed Oct 29 06:36:58 2008
Return-Path: <mpls-bounces@ietf.org>
X-Original-To: mpls-archive@megatron.ietf.org
Delivered-To: ietfarch-mpls-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E9D723A6AF5;
	Wed, 29 Oct 2008 06:36:57 -0700 (PDT)
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 578D83A6C84
	for <mpls@core3.amsl.com>; Wed, 29 Oct 2008 06:36:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.639
X-Spam-Level: 
X-Spam-Status: No, score=-0.639 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, RCVD_IN_BL_SPAMCOP_NET=1.96]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id WjS9ALDuTcZ6 for <mpls@core3.amsl.com>;
	Wed, 29 Oct 2008 06:36:55 -0700 (PDT)
Received: from rn-out-0910.google.com (rn-out-0910.google.com [64.233.170.188])
	by core3.amsl.com (Postfix) with ESMTP id 648023A6AF5
	for <mpls@ietf.org>; Wed, 29 Oct 2008 06:36:54 -0700 (PDT)
Received: by rn-out-0910.google.com with SMTP id m7so1516889rnd.18
	for <mpls@ietf.org>; Wed, 29 Oct 2008 06:36:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
	h=domainkey-signature:received:received:cc:message-id:from:to
	:in-reply-to:content-type:content-transfer-encoding:mime-version
	:subject:date:references:x-mailer;
	bh=5YPSazi4FAbA2kvV6EwWoZD/XFK++bmRnoUoFHMxbCU=;
	b=uvE/Y+CKJjqnasXbWcWTZpY0Fb1EcaiRudpkWuzofKfnAM6ALtjLRyg/L5issfzzgN
	3FCk8SU7nSCFCV85wpTeUY+7gt6MVo2sY5Er1GX1CweOo7+W26MJAjLvYKF7dNc0B+Kh
	2xKwr5sxxsWYGfVEtnGnn4FG9B0ZU51Qz6fbg=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=cc:message-id:from:to:in-reply-to:content-type
	:content-transfer-encoding:mime-version:subject:date:references
	:x-mailer;
	b=Dl9o0kqqDf9eiPIpj3J58Covb77tlJp4ajhbZ/IUFKfu9XZs7dfAGuvzHq4LLH9O/N
	TuT8IQBJRlKEfoMg2C1Q5HQdMH6T8D57hWpkR77B5U1L4aEOnGa647unh7it9Qjm4mHx
	QYpLnbGstEqRwurHqKxyvRCMEYjEzS9aPiy/Y=
Received: by 10.100.154.9 with SMTP id b9mr8637412ane.73.1225287413264;
	Wed, 29 Oct 2008 06:36:53 -0700 (PDT)
Received: from ?10.64.29.112? (gw1.cox.com [24.248.74.254])
	by mx.google.com with ESMTPS id d35sm8592995and.8.2008.10.29.06.36.50
	(version=TLSv1/SSLv3 cipher=RC4-MD5);
	Wed, 29 Oct 2008 06:36:51 -0700 (PDT)
Message-Id: <6D849FFC-E67D-4F0A-A088-4631E31250D9@gmail.com>
From: Phil Bedard <bedard.phil@gmail.com>
To: Loa Andersson <loa@pi.nu>
In-Reply-To: <4906E57E.4050105@pi.nu>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Wed, 29 Oct 2008 09:36:49 -0400
References: <4906E57E.4050105@pi.nu>
X-Mailer: Apple Mail (2.929.2)
Cc: mpls@ietf.org
Subject: Re: [mpls] [PWE3] draft-bocci-mpls-tp-gach-gal-00.txt for mpls wg
	doc
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: mpls-bounces@ietf.org
Errors-To: mpls-bounces@ietf.org

Support.

Phil


On Oct 28, 2008, at 6:12 AM, Loa Andersson wrote:

> Working group(s),
>
> this is to initiate a two week poll to see if
> draft-bocci-mpls-tp-gach-gal-00.txt is in shape to
> become a mpls working group document.
>
> The current draft is a merge of to earlier draft
> one that defined the GAL and another that specified
> the generic associated channel.
>
> Please send your responses to the mpls working group
> mailing list (needs a bit of discipline, "replay all"
> won't do the trick ;) .
>
> Please respond on Tuesday Oct 11 the latest.
>
> /Loa
>
> -- 
> Loa Andersson
>
> Principal Networking Architect
> Acreo AB                           phone:  +46 8 632 77 14
> Isafjordsgatan 22                  mobile: +46 739 81 21 64
> Kista, Sweden                      email:  loa.andersson@acreo.se
>                                           loa@pi.nu
> _______________________________________________
> pwe3 mailing list
> pwe3@ietf.org
> https://www.ietf.org/mailman/listinfo/pwe3

_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls


From mpls-bounces@ietf.org  Wed Oct 29 06:46:26 2008
Return-Path: <mpls-bounces@ietf.org>
X-Original-To: mpls-archive@megatron.ietf.org
Delivered-To: ietfarch-mpls-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id A45773A6CDF;
	Wed, 29 Oct 2008 06:46:26 -0700 (PDT)
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 74BE03A6CAB
	for <mpls@core3.amsl.com>; Wed, 29 Oct 2008 06:46:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 9lTDPpiczvBe for <mpls@core3.amsl.com>;
	Wed, 29 Oct 2008 06:46:23 -0700 (PDT)
Received: from prattle.redback.com (prattle.redback.com [155.53.12.9])
	by core3.amsl.com (Postfix) with ESMTP id 6618F3A67EF
	for <mpls@ietf.org>; Wed, 29 Oct 2008 06:46:23 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1])
	by prattle.redback.com (Postfix) with ESMTP id CF2959C69D9;
	Wed, 29 Oct 2008 06:46:22 -0700 (PDT)
Received: from prattle.redback.com ([127.0.0.1])
	by localhost (prattle [127.0.0.1]) (amavisd-new, port 10024) with ESMTP
	id 09545-06; Wed, 29 Oct 2008 06:46:22 -0700 (PDT)
Received: from rbsjx.ad.redback.com (rbsjxh1.redback.com [155.53.14.105])
	by prattle.redback.com (Postfix) with ESMTP id A7B9F9C69D8;
	Wed, 29 Oct 2008 06:46:22 -0700 (PDT)
Received: from RBSJX.ad.redback.com ([155.53.14.103]) by
	rbsjxh1.ad.redback.com ([155.53.14.105]) with mapi;
	Wed, 29 Oct 2008 06:46:22 -0700
From: David Sinicrope <euddasi@redback.com>
To: Loa Andersson <loa@pi.nu>, "mpls@ietf.org" <mpls@ietf.org>
Date: Wed, 29 Oct 2008 06:46:19 -0700
Thread-Topic: [PWE3] draft-bocci-mpls-tp-gach-gal-00.txt for mpls wg doc
Thread-Index: Ack45a7VPby6RwUVQN+qUd/c1zwAGAA5wnGZ
Message-ID: <C52DE16B.BC76%euddasi@redback.com>
In-Reply-To: <4906E57E.4050105@pi.nu>
Accept-Language: en-US
Content-Language: en
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
MIME-Version: 1.0
X-Virus-Scanned: by amavisd-new at redback.com
Subject: Re: [mpls] [PWE3] draft-bocci-mpls-tp-gach-gal-00.txt for mpls wg
	doc
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1732250882=="
Sender: mpls-bounces@ietf.org
Errors-To: mpls-bounces@ietf.org

--===============1732250882==
Content-Language: en
Content-Type: multipart/alternative;
	boundary="_000_C52DE16BBC76euddasiredbackcom_"

--_000_C52DE16BBC76euddasiredbackcom_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable


Support.

On 10/28/08 6:12 AM, "Loa Andersson" <loa@pi.nu> wrote:

Working group(s),

this is to initiate a two week poll to see if
draft-bocci-mpls-tp-gach-gal-00.txt is in shape to
become a mpls working group document.

The current draft is a merge of to earlier draft
one that defined the GAL and another that specified
the generic associated channel.

Please send your responses to the mpls working group
mailing list (needs a bit of discipline, "replay all"
won't do the trick ;) .

Please respond on Tuesday Oct 11 the latest.

/Loa

--
Loa Andersson

Principal Networking Architect
Acreo AB                           phone:  +46 8 632 77 14
Isafjordsgatan 22                  mobile: +46 739 81 21 64
Kista, Sweden                      email:  loa.andersson@acreo.se
                                           loa@pi.nu
_______________________________________________
pwe3 mailing list
pwe3@ietf.org
https://www.ietf.org/mailman/listinfo/pwe3


--_000_C52DE16BBC76euddasiredbackcom_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<HTML>
<HEAD>
<TITLE>Re: [PWE3] draft-bocci-mpls-tp-gach-gal-00.txt for mpls wg doc</TITL=
E>
</HEAD>
<BODY>
<FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"><SPAN STYLE=3D'font-size:=
11pt'><BR>
Support.<BR>
<BR>
On 10/28/08 6:12 AM, &quot;Loa Andersson&quot; &lt;<a href=3D"loa@pi.nu">lo=
a@pi.nu</a>&gt; wrote:<BR>
<BR>
</SPAN></FONT><BLOCKQUOTE><FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"=
><SPAN STYLE=3D'font-size:11pt'>Working group(s),<BR>
<BR>
this is to initiate a two week poll to see if<BR>
draft-bocci-mpls-tp-gach-gal-00.txt is in shape to<BR>
become a mpls working group document.<BR>
<BR>
The current draft is a merge of to earlier draft<BR>
one that defined the GAL and another that specified<BR>
the generic associated channel.<BR>
<BR>
Please send your responses to the mpls working group<BR>
mailing list (needs a bit of discipline, &quot;replay all&quot;<BR>
won't do the trick ;) .<BR>
<BR>
Please respond on Tuesday Oct 11 the latest.<BR>
<BR>
/Loa<BR>
<BR>
--<BR>
Loa Andersson<BR>
<BR>
Principal Networking Architect<BR>
Acreo AB &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;phone: &nbsp;+46 8 632 77 14<BR>
Isafjordsgatan 22 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;mobile: +46 739 81 21 64<BR>
Kista, Sweden &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;email: &nb=
sp;<a href=3D"loa.andersson@acreo.se">loa.andersson@acreo.se</a><BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href=3D"loa@pi.nu">loa@pi.nu</a><BR>
_______________________________________________<BR>
pwe3 mailing list<BR>
<a href=3D"pwe3@ietf.org">pwe3@ietf.org</a><BR>
<a href=3D"https://www.ietf.org/mailman/listinfo/pwe3">https://www.ietf.org=
/mailman/listinfo/pwe3</a><BR>
<BR>
</SPAN></FONT></BLOCKQUOTE>
</BODY>
</HTML>


--_000_C52DE16BBC76euddasiredbackcom_--

--===============1732250882==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls

--===============1732250882==--


From mpls-bounces@ietf.org  Wed Oct 29 06:58:32 2008
Return-Path: <mpls-bounces@ietf.org>
X-Original-To: mpls-archive@megatron.ietf.org
Delivered-To: ietfarch-mpls-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 1B02128C28C;
	Wed, 29 Oct 2008 06:58:32 -0700 (PDT)
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 91D5128C20A
	for <mpls@core3.amsl.com>; Wed, 29 Oct 2008 06:58:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id qxNpi5PGq5KB for <mpls@core3.amsl.com>;
	Wed, 29 Oct 2008 06:58:30 -0700 (PDT)
Received: from hicks.ciena.com (hicks.ciena.com [63.118.34.22])
	by core3.amsl.com (Postfix) with ESMTP id 69CDE3A69B2
	for <mpls@ietf.org>; Wed, 29 Oct 2008 06:58:30 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: ApoEAFAICEk/dicV/2dsb2JhbADNJQGDUA
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.4325
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Wed, 29 Oct 2008 09:57:47 -0400
Message-ID: <6535C9CED6F87446B41D20EF170F2362138403@mamxm01.ciena.com>
In-Reply-To: <4906E57E.4050105@pi.nu>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [mpls] draft-bocci-mpls-tp-gach-gal-00.txt for mpls wg doc
Thread-Index: Ack45cBnquhYJyNnRlC5e/1/0rd3jAA6G/Jw
References: <4906E57E.4050105@pi.nu>
From: "Shah, Himanshu" <hshah@ciena.com>
Importance: normal
Priority: normal
To: <mpls@ietf.org>
X-OriginalArrivalTime: 29 Oct 2008 13:57:52.0713 (UTC)
	FILETIME=[56167B90:01C939CE]
Subject: Re: [mpls] draft-bocci-mpls-tp-gach-gal-00.txt for mpls wg doc
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mpls-bounces@ietf.org
Errors-To: mpls-bounces@ietf.org

Support..

/himanshu





-----Original Message-----
From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf Of
Loa Andersson
Sent: Tuesday, October 28, 2008 6:12 AM
To: mpls@ietf.org; pwe3; ahtmpls@itu.int; ccamp
Subject: [mpls] draft-bocci-mpls-tp-gach-gal-00.txt for mpls wg doc

Working group(s),

this is to initiate a two week poll to see if
draft-bocci-mpls-tp-gach-gal-00.txt is in shape to become a mpls working
group document.

The current draft is a merge of to earlier draft one that defined the
GAL and another that specified the generic associated channel.

Please send your responses to the mpls working group mailing list (needs
a bit of discipline, "replay all"
won't do the trick ;) .

Please respond on Tuesday Oct 11 the latest.

/Loa

--
Loa Andersson

Principal Networking Architect
Acreo AB                           phone:  +46 8 632 77 14
Isafjordsgatan 22                  mobile: +46 739 81 21 64
Kista, Sweden                      email:  loa.andersson@acreo.se
                                           loa@pi.nu
_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls
_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls


From mpls-bounces@ietf.org  Wed Oct 29 07:08:24 2008
Return-Path: <mpls-bounces@ietf.org>
X-Original-To: mpls-archive@megatron.ietf.org
Delivered-To: ietfarch-mpls-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 0B5153A6974;
	Wed, 29 Oct 2008 07:08:24 -0700 (PDT)
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id CF3523A6967
	for <mpls@core3.amsl.com>; Wed, 29 Oct 2008 07:08:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id XxYi5yh1bgcW for <mpls@core3.amsl.com>;
	Wed, 29 Oct 2008 07:08:21 -0700 (PDT)
Received: from rtp-iport-2.cisco.com (rtp-iport-2.cisco.com [64.102.122.149])
	by core3.amsl.com (Postfix) with ESMTP id 972353A686B
	for <mpls@ietf.org>; Wed, 29 Oct 2008 07:08:21 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,506,1220227200"; d="scan'208";a="26013839"
Received: from rtp-dkim-1.cisco.com ([64.102.121.158])
	by rtp-iport-2.cisco.com with ESMTP; 29 Oct 2008 14:08:20 +0000
Received: from rtp-core-1.cisco.com (rtp-core-1.cisco.com [64.102.124.12])
	by rtp-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id m9TE8KJF030393; 
	Wed, 29 Oct 2008 10:08:20 -0400
Received: from erosen-linux.cisco.com (erosen-linux.cisco.com [161.44.70.34])
	by rtp-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m9TE8K2g018533;
	Wed, 29 Oct 2008 14:08:20 GMT
Received: from erosen-linux (localhost.localdomain [127.0.0.1])
	by erosen-linux.cisco.com (8.13.1/8.13.1) with ESMTP id m9TE8Jp2032638; 
	Wed, 29 Oct 2008 10:08:19 -0400
To: Adrian Farrel <adrian@olddog.co.uk>
In-reply-to: Your message of Mon, 27 Oct 2008 23:57:04 -0000.
	<C48632358EF74F6595B4090FF4B42A39@your029b8cecfe> 
Date: Wed, 29 Oct 2008 10:08:19 -0400
Message-ID: <32637.1225289299@erosen-linux>
From: Eric Rosen <erosen@cisco.com>
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=3745; t=1225289300;
	x=1226153300; c=relaxed/simple; s=rtpdkim1001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=erosen@cisco.com;
	z=From:=20Eric=20Rosen=20<erosen@cisco.com>
	|Subject:=20Re=3A=20[mpls]=20draft-dasmith-mpls-ip-options-
	01.txt=20as=20a=20WG=20doc?=20 |Sender:=20
	|To:=20Adrian=20Farrel=20<adrian@olddog.co.uk>;
	bh=ez+UoZ1GEVLlmh7/SSEAyo7gDNb7QH8GSqZUUMuCg+0=;
	b=X6jN551dB3+nvU5n2ZS6khUMxNzUFhZzPJebWBqwLdI3RL28kKTDf04TjE
	ZA7NDiFeVT4IQhvBpVrp+QOX1GUGwrbWDp6tg7PO/ZRyx6+1rleFTwWnp2qx
	FuwSXTdT9R;
Authentication-Results: rtp-dkim-1; header.From=erosen@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim1001 verified; ); 
Cc: mpls@ietf.org
Subject: Re: [mpls] draft-dasmith-mpls-ip-options-01.txt as a WG doc?
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: erosen@cisco.com
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=subscribe>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mpls-bounces@ietf.org
Errors-To: mpls-bounces@ietf.org


I believe this draft is meant to solve a very simple problem.

It  has been observed  that there  are MPLS  implementations which  will not
encapsulate IP packets that have options.  

In many  environments, this behavior  is undesirable.  However, it  has been
observed that there  are some implementations in which  this behavior cannot
be shut off.

The draft  attempts to  avoid this  situation in the  future by  setting two
rules:

1. It  must be possible  to configure  an LER such  that it will  apply MPLS
   encapsulation irrespective of the presence of IP options.

2. This configuration setting is the default.

However,  the draft  also specifies  that  this is  not meant  to alter  the
processing of control protocols such as RSVP which may use IP options.

So I see basically two grounds on which this draft may be opposed:

- One might think it is perfectly  okay to have an MPLS implementation which
  cannot be configured to label packets that have IP options.

  This doesn't seem reasonable to me.

- One might  think that  the labeling  of a packet  with options  should not
  necessarily be the default behavior.

  This seems more  more reasonable, at least in  theory.  However, given the
  fact that IP  options have been in disrepute for  several decades, I don't
  really see that there's any problem caused by making this the default.

Adrian> It  really  does  seem  to  be  trying to  define  as  mandatory  an
Adrian> implementation  behavior  that  might  reasonably  be  flexible  for
Adrian> different reasons. 

I  think  the  intent  is  only  to define  the  behavior  as  mandatory  to
implement, not to prohibit the flexibility.

Adrian> If the use  of IP options in the core  is sufficiently worrying, why
Adrian> not disable them on the core routers?

I think that's  usually done, but I don't  see what that has to  do with the
fact that an LER may have refused to label a packet with options.

Adrian> If two IP  packets carry different explicit paths  in their options,
Adrian> why  should they not  be directed  to different  (explicitly routed)
Adrian> LSPs to conform to those routes even though they carry the same FEC?

This behavior  is not ruled  out if some  network wants to  support explicit
routing via IP  options.  Since the percentage of  service provider networks
that support  this is, err, low,  I don't think  it can be argued  that this
should be the default behavior.

Renwei> This draft imposes a new requirement on LER. But the new requirement
Renwei> has nothing to do with inter-op.

If some  router implementation  cannot label IP  packets that  have options,
then that implementation cannot operate as an LER in certain environments.  

Renwei> It could at most  serve as a CLI knob which can  be turned on or off
Renwei> according to whatever someone wants, 

All the draft does is make the CLI knob (and its default setting) mandatory.

Renwei> Moreover, when an  IP packet has an option, it  usually has a reason
Renwei> for having  such an option, and  thus expects to  be processed along
Renwei> the forwarding path in the network

I can't say what expectations the creator of such a packet may have had, but
if he  really expected  special processing all  along the path  through some
arbitrary network, then  he's expecting a practice which  hasn't been common
since the early days of the Internet.

Renwei> Some software vendors also develop their software tools based on the
Renwei> options 

The draft is really concerned with data packets, and isn't meant to prohibit
the use of IP options on  the control/monitoring protocols which are used in
a particular network environment.






_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls


From mpls-bounces@ietf.org  Wed Oct 29 08:37:20 2008
Return-Path: <mpls-bounces@ietf.org>
X-Original-To: mpls-archive@megatron.ietf.org
Delivered-To: ietfarch-mpls-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 016CF3A6A18;
	Wed, 29 Oct 2008 08:37:20 -0700 (PDT)
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 895EB3A687E
	for <mpls@core3.amsl.com>; Wed, 29 Oct 2008 08:37:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.599
X-Spam-Level: 
X-Spam-Status: No, score=-8.599 tagged_above=-999 required=5
	tests=[AWL=-2.001, BAYES_00=-2.599, HTML_MESSAGE=0.001,
	RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id Go03m1XCCqRR for <mpls@core3.amsl.com>;
	Wed, 29 Oct 2008 08:37:17 -0700 (PDT)
Received: from rtp-iport-1.cisco.com (rtp-iport-1.cisco.com [64.102.122.148])
	by core3.amsl.com (Postfix) with ESMTP id 6AB133A690E
	for <mpls@ietf.org>; Wed, 29 Oct 2008 08:37:17 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,506,1220227200"; d="scan'208,217";a="26061399"
Received: from rtp-dkim-2.cisco.com ([64.102.121.159])
	by rtp-iport-1.cisco.com with ESMTP; 29 Oct 2008 15:37:16 +0000
Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13])
	by rtp-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id m9TFbG92005703; 
	Wed, 29 Oct 2008 11:37:16 -0400
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com
	[64.102.31.12])
	by rtp-core-2.cisco.com (8.13.8/8.13.8) with ESMTP id m9TFbGeO007347;
	Wed, 29 Oct 2008 15:37:16 GMT
Received: from xmb-rtp-203.amer.cisco.com ([64.102.31.20]) by
	xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 29 Oct 2008 11:37:15 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Wed, 29 Oct 2008 11:36:32 -0400
Message-ID: <BABC859E6D0B9A4D8448CC7F41CD2B070764A62F@xmb-rtp-203.amer.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Updates to draft-ietf-ccamp-mpls-graceful-shutdown
Thread-Index: Ack53B6q/yDjWG9SR6aYcY8pbCH7Cw==
From: "Zafar Ali (zali)" <zali@cisco.com>
To: "Lou Berger" <lberger@labn.net>
X-OriginalArrivalTime: 29 Oct 2008 15:37:15.0817 (UTC)
	FILETIME=[385FF190:01C939DC]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=2153; t=1225294636;
	x=1226158636; c=relaxed/simple; s=rtpdkim2001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=zali@cisco.com;
	z=From:=20=22Zafar=20Ali=20(zali)=22=20<zali@cisco.com>
	|Subject:=20Updates=20to=20draft-ietf-ccamp-mpls-graceful-s
	hutdown |Sender:=20
	|To:=20=22Lou=20Berger=22=20<lberger@labn.net>;
	bh=VpMzwXBbUpvFyawbxtsGUvOe0/blVvr7ge7PGZr/nWQ=;
	b=dvkSajH3hEhGr/aHup9lqzBqSMfBNk5kASXkTXERoKZR0xhyeJqMKqIUl8
	XWODIm2mQ8ltAZnQiw9P7WrkLJhKrhVhJ2C+JuLHCDz1Em/lz+qzqeNYn6bR
	YKyS5GUwpr;
Authentication-Results: rtp-dkim-2; header.From=zali@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim2001 verified; ); 
Cc: mpls@ietf.org, "Newton, Jonathan" <Jonathan.Newton@cw.com>, jpv@cisco.com,
	ccamp@ops.ietf.org, "Anca Zamfir \(ancaz\)" <ancaz@cisco.com>
Subject: [mpls] Updates to draft-ietf-ccamp-mpls-graceful-shutdown
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0912908144=="
Sender: mpls-bounces@ietf.org
Errors-To: mpls-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0912908144==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C939DC.20E4766F"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C939DC.20E4766F
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi Lou, Adrian, Deborah, et al-=20

We have modified the draft-ietf-ccamp-mpls-graceful-shutdown to reflect
changes proposed in "draft-ietf-mpls-gmpls-lsp-reroute". This was a
comment from Lou during the last call of this draft. This was the only
outstanding comment from the LC.=20

In the light of the above, can you please take a quick look at
draft-ietf-ccamp-mpls-graceful-shutdown-08.txt to make sure that the
changes are correctly in synch with the
draft-ietf-mpls-gmpls-lsp-reroute work.=20

Thanks for your input.=20

Regards... Zafar=20


------_=_NextPart_001_01C939DC.20E4766F
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.5.7653.38">
<TITLE>Updates to draft-ietf-ccamp-mpls-graceful-shutdown</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/rtf format -->

<P><FONT COLOR=3D"#000080" FACE=3D"Times New Roman">Hi Lou, Adrian, =
Deborah, et al- </FONT>
</P>

<P><FONT COLOR=3D"#000080" FACE=3D"Times New Roman">We have modified the =
draft-ietf-ccamp-mpls-graceful-shutdown to reflect changes proposed in =
&quot;draft-ietf-mpls-gmpls-lsp-reroute&quot;. This was a comment from =
Lou during the last call of this draft. This was the only outstanding =
comment from the LC. </FONT></P>

<P><FONT COLOR=3D"#000080" FACE=3D"Times New Roman">In the light of the =
above, can you please take a quick look at =
draft-ietf-ccamp-mpls-graceful-shutdown-08.txt to make sure that the =
changes are correctly in synch with the =
draft-ietf-mpls-gmpls-lsp-reroute work. </FONT></P>

<P><FONT COLOR=3D"#000080" FACE=3D"Times New Roman">Thanks for your =
input. </FONT>
</P>

<P><FONT COLOR=3D"#000080" FACE=3D"Times New Roman">Regards... =
Zafar</FONT>=20
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C939DC.20E4766F--

--===============0912908144==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls

--===============0912908144==--


From mpls-bounces@ietf.org  Wed Oct 29 08:37:53 2008
Return-Path: <mpls-bounces@ietf.org>
X-Original-To: mpls-archive@megatron.ietf.org
Delivered-To: ietfarch-mpls-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id AED9828C39F;
	Wed, 29 Oct 2008 08:37:53 -0700 (PDT)
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 4DEF23A6A36
	for <mpls@core3.amsl.com>; Wed, 29 Oct 2008 08:37:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.041
X-Spam-Level: 
X-Spam-Status: No, score=-2.041 tagged_above=-999 required=5 tests=[AWL=0.557, 
	BAYES_00=-2.599, STOX_REPLY_TYPE=0.001]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id mwVsE0fapKgh for <mpls@core3.amsl.com>;
	Wed, 29 Oct 2008 08:37:51 -0700 (PDT)
Received: from asmtp2.iomartmail.com (asmtp2.iomartmail.com [62.128.201.249])
	by core3.amsl.com (Postfix) with ESMTP id 4367F3A687E
	for <mpls@ietf.org>; Wed, 29 Oct 2008 08:37:51 -0700 (PDT)
Received: from asmtp2.iomartmail.com (localhost.localdomain [127.0.0.1])
	by asmtp2.iomartmail.com (8.12.11.20060308/8.12.8) with ESMTP id
	m9TFbhNk013402; Wed, 29 Oct 2008 15:37:43 GMT
Received: from your029b8cecfe (dsl-sp-81-140-15-32.in-addr.broadbandscope.com
	[81.140.15.32]) (authenticated bits=0)
	by asmtp2.iomartmail.com (8.12.11.20060308/8.12.11) with ESMTP id
	m9TFbgJs013380; Wed, 29 Oct 2008 15:37:42 GMT
Message-ID: <18C4D46001964FB284505742417C15FF@your029b8cecfe>
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: <julien.meuric@orange-ftgroup.com>
References: <002801c935f2$9229cae0$0200a8c0@your029b8cecfe>
	<7DBAFEC6A76F3E42817DF1EBE64CB02605F7FFED@ftrdmel2>
	<E2075D5931364C61A7D9DF7C24E1E367@your029b8cecfe>
	<7DBAFEC6A76F3E42817DF1EBE64CB02605F800EF@ftrdmel2>
Date: Wed, 29 Oct 2008 15:35:55 -0000
MIME-Version: 1.0
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.5512
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579
Cc: mpls@ietf.org
Subject: Re: [mpls] A BNF specification for RSVP-TE
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Adrian Farrel <adrian@olddog.co.uk>
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: mpls-bounces@ietf.org
Errors-To: mpls-bounces@ietf.org

>>> Section 2.2.5: my 1st reaction when reading the example is what you say
>>> right after about grouping using round braquets instead of square ones.
>>> The direct consequence of your example is that the operator "..." is
>>> also defined for nil, which was not obvious before.
>>
>> Hmmm. I'm not sure what you are saying.
>
> [JM] Sorry if my writing was confusing. I was refering to the last note of
> 2.2.5. Let me try to rephrase.
> You're defining the operator "...". It applies to an object or a 
> construct,
> but I first wondered on what set/domain (that word again?!) the function
> was defined. Indeed, the early specification doesn't state if this
> operator/function is defined for the empty construct or not. A piece of
> answer if provided in the last example:
> "[ <MESSAGE_ID_ACK> | <MESSAGE_ID_NACK> ] ..."
> reveals that "..." can be applied to an empty construct as the optional
> part, marked by the square braquets, could be equal to the empty set.
>
> Am I more clear now?

OK.
I see what you are saying.

In fact, "..." does not apply to an empty construct. It applies to a 
construct that might be empty, but it is the construct that is repeatable, 
not the emptiness :-)

What comes out of this is that it would be helpful to describe exactly what 
"..." operates on.

I'll add that.

Cheers,
Adrian 

_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls


From mpls-bounces@ietf.org  Wed Oct 29 08:56:32 2008
Return-Path: <mpls-bounces@ietf.org>
X-Original-To: mpls-archive@megatron.ietf.org
Delivered-To: ietfarch-mpls-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E45793A6870;
	Wed, 29 Oct 2008 08:56:31 -0700 (PDT)
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 471903A6928
	for <mpls@core3.amsl.com>; Wed, 29 Oct 2008 08:56:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.265
X-Spam-Level: 
X-Spam-Status: No, score=-2.265 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id Wt4HD4+GsXg9 for <mpls@core3.amsl.com>;
	Wed, 29 Oct 2008 08:56:24 -0700 (PDT)
Received: from outbound-mail-129.bluehost.com (outbound-mail-129.bluehost.com
	[67.222.38.29]) by core3.amsl.com (Postfix) with SMTP id 42A583A686C
	for <mpls@ietf.org>; Wed, 29 Oct 2008 08:56:24 -0700 (PDT)
Received: (qmail 15319 invoked by uid 0); 29 Oct 2008 15:56:21 -0000
Received: from unknown (HELO box474.bluehost.com) (74.220.219.74)
	by outboundproxy4.bluehost.com with SMTP; 29 Oct 2008 15:56:21 -0000
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=labn.net;
	h=Received:X-Mailer:Date:To:From:Subject:Cc:In-Reply-To:References:Mime-Version:Content-Type:X-Identified-User;
	b=YeYob4qHtee2ukmqdDvuS76a7fonCCUnlPfU3SxKfd9FkSt7k7EyZU54KS//AV7wgB+DVEkS6mvzKbn8qmxhBMoBcvjc8d/BuqwQ+ILJqSlcNpUpoHbmzpDGnEY6R1vR;
Received: from box474.bluehost.com ([74.220.219.74] helo=LC2.labn.net)
	by box474.bluehost.com with esmtpa (Exim 4.69)
	(envelope-from <lberger@labn.net>)
	id 1KvDPA-0007x4-Ie; Wed, 29 Oct 2008 09:56:20 -0600
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Wed, 29 Oct 2008 11:56:18 -0400
To: "Zafar Ali (zali)" <zali@cisco.com>
From: Lou Berger <lberger@labn.net>
In-Reply-To: <BABC859E6D0B9A4D8448CC7F41CD2B070764A62F@xmb-rtp-203.amer.
	cisco.com>
References: <BABC859E6D0B9A4D8448CC7F41CD2B070764A62F@xmb-rtp-203.amer.cisco.com>
Mime-Version: 1.0
X-Identified-User: {2629:box474.bluehost.com:labnmobi:labn.net} {sentby:smtp
	auth 74.220.219.74 authed with lberger@labn.net}
Message-Id: <20081029155624.42A583A686C@core3.amsl.com>
Cc: mpls@ietf.org, "Newton, Jonathan" <Jonathan.Newton@cw.com>, jpv@cisco.com,
	ccamp@ops.ietf.org, "Anca Zamfir \(ancaz\)" <ancaz@cisco.com>
Subject: Re: [mpls] Updates to draft-ietf-ccamp-mpls-graceful-shutdown
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: mpls-bounces@ietf.org
Errors-To: mpls-bounces@ietf.org

Zafar,

Why does the document define new error codes (and why 4)?  Is it that 
the reroute document isn't sufficient clear on how to indicated each 
of the 4? Is it some other reason?

Thanks,
Lou


At 11:36 AM 10/29/2008, Zafar Ali (zali) wrote:

>Hi Lou, Adrian, Deborah, et al-
>
>We have modified the draft-ietf-ccamp-mpls-graceful-shutdown to 
>reflect changes proposed in "draft-ietf-mpls-gmpls-lsp-reroute". 
>This was a comment from Lou during the last call of this draft. This 
>was the only outstanding comment from the LC.
>
>In the light of the above, can you please take a quick look at 
>draft-ietf-ccamp-mpls-graceful-shutdown-08.txt to make sure that the 
>changes are correctly in synch with the 
>draft-ietf-mpls-gmpls-lsp-reroute work.
>
>Thanks for your input.
>
>Regards... Zafar

_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls


From mpls-bounces@ietf.org  Wed Oct 29 09:35:13 2008
Return-Path: <mpls-bounces@ietf.org>
X-Original-To: mpls-archive@megatron.ietf.org
Delivered-To: ietfarch-mpls-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 0600528C350;
	Wed, 29 Oct 2008 09:35:13 -0700 (PDT)
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 900603A6B21
	for <mpls@core3.amsl.com>; Wed, 29 Oct 2008 09:35:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.615
X-Spam-Level: 
X-Spam-Status: No, score=-6.615 tagged_above=-999 required=5
	tests=[AWL=-0.616, BAYES_00=-2.599, J_CHICKENPOX_21=0.6,
	RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id FagiaH6dnFbM for <mpls@core3.amsl.com>;
	Wed, 29 Oct 2008 09:35:07 -0700 (PDT)
Received: from sj-iport-3.cisco.com (sj-iport-3.cisco.com [171.71.176.72])
	by core3.amsl.com (Postfix) with ESMTP id 9C2903A6AB3
	for <mpls@ietf.org>; Wed, 29 Oct 2008 09:35:07 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,507,1220227200"; d="scan'208";a="111668681"
Received: from sj-dkim-3.cisco.com ([171.71.179.195])
	by sj-iport-3.cisco.com with ESMTP; 29 Oct 2008 16:35:07 +0000
Received: from sj-core-2.cisco.com (sj-core-2.cisco.com [171.71.177.254])
	by sj-dkim-3.cisco.com (8.12.11/8.12.11) with ESMTP id m9TGZ6HG029604; 
	Wed, 29 Oct 2008 09:35:06 -0700
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com
	[64.102.31.12])
	by sj-core-2.cisco.com (8.13.8/8.13.8) with ESMTP id m9TGZ6Zu011298;
	Wed, 29 Oct 2008 16:35:06 GMT
Received: from xmb-rtp-203.amer.cisco.com ([64.102.31.20]) by
	xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 29 Oct 2008 12:35:06 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Wed, 29 Oct 2008 12:34:47 -0400
Message-ID: <BABC859E6D0B9A4D8448CC7F41CD2B070764A683@xmb-rtp-203.amer.cisco.com>
In-Reply-To: <E1KvDPO-0005hs-RG@psg.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Updates to draft-ietf-ccamp-mpls-graceful-shutdown
Thread-Index: Ack53yEy/I+XfyB5TO2rHdRpEseqEwAA9bbA
References: <BABC859E6D0B9A4D8448CC7F41CD2B070764A62F@xmb-rtp-203.amer.cisco.com>
	<E1KvDPO-0005hs-RG@psg.com>
From: "Zafar Ali (zali)" <zali@cisco.com>
To: "Lou Berger" <lberger@labn.net>
X-OriginalArrivalTime: 29 Oct 2008 16:35:06.0082 (UTC)
	FILETIME=[4CD05C20:01C939E4]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=972; t=1225298107; x=1226162107;
	c=relaxed/simple; s=sjdkim3002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=zali@cisco.com;
	z=From:=20=22Zafar=20Ali=20(zali)=22=20<zali@cisco.com>
	|Subject:=20RE=3A=20Updates=20to=20draft-ietf-ccamp-mpls-gr
	aceful-shutdown |Sender:=20;
	bh=ppTpGEZ3QoX1+7NM1oqTa40cus0UgYf/sATwnuIRL5c=;
	b=eSCCiP3gLox9mwtGwVq3q7b21frK0PoMP74yvWFfF1vuo1HQFUuuyRyLH9
	77zRvpTiaR8ysLoArfFqPuQ0YutWtMo9FNrFN1Pry8OGjmyw/yLFLsgGJD1x
	RkwyMVU/sC;
Authentication-Results: sj-dkim-3; header.From=zali@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim3002 verified; ); 
Cc: mpls@ietf.org, "Newton, Jonathan" <Jonathan.Newton@cw.com>, jpv@cisco.com,
	ccamp@ops.ietf.org, "Anca Zamfir \(ancaz\)" <ancaz@cisco.com>
Subject: Re: [mpls] Updates to draft-ietf-ccamp-mpls-graceful-shutdown
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mpls-bounces@ietf.org
Errors-To: mpls-bounces@ietf.org

Hi Lou-  

> -----Original Message-----
> From: owner-ccamp@ops.ietf.org 
> [mailto:owner-ccamp@ops.ietf.org] On Behalf Of Lou Berger
> Sent: Wednesday, October 29, 2008 11:56 AM
> To: Zafar Ali (zali)
> Cc: Lou Berger; Adrian Farrel; ccamp@ops.ietf.org; 
> mpls@ietf.org; jpv@cisco.com; Anca Zamfir (ancaz); Newton, Jonathan
> Subject: Re: Updates to draft-ietf-ccamp-mpls-graceful-shutdown
> 
> Zafar,
> 
> Why does the document define new error codes (and why 4)?  Is 
> it that the reroute document isn't sufficient clear on how to 
> indicated each of the 4? Is it some other reason?
> 

This is because headend may be able to compute alternate route
("reroute" action) for mb4b differently, depending on the resource under
graceful shutdown, as detailed in the document. Hence one code is define
for TE node, TE link, component link of a bundled TE link, and label
resource, each. 

Thanks

Regards... Zafar 

<snip>
_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls


From mpls-bounces@ietf.org  Wed Oct 29 10:30:53 2008
Return-Path: <mpls-bounces@ietf.org>
X-Original-To: mpls-archive@megatron.ietf.org
Delivered-To: ietfarch-mpls-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B5BE43A6B0F;
	Wed, 29 Oct 2008 10:30:53 -0700 (PDT)
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 0D34728C37A
	for <mpls@core3.amsl.com>; Wed, 29 Oct 2008 10:30:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.614
X-Spam-Level: 
X-Spam-Status: No, score=-1.614 tagged_above=-999 required=5 tests=[AWL=0.051, 
	BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, J_CHICKENPOX_21=0.6]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id ADOKyWtnrv9X for <mpls@core3.amsl.com>;
	Wed, 29 Oct 2008 10:30:48 -0700 (PDT)
Received: from outbound-mail-148.bluehost.com (outbound-mail-148.bluehost.com
	[67.222.38.38]) by core3.amsl.com (Postfix) with SMTP id 4B8323A6B0F
	for <mpls@ietf.org>; Wed, 29 Oct 2008 10:30:48 -0700 (PDT)
Received: (qmail 11887 invoked by uid 0); 29 Oct 2008 17:30:17 -0000
Received: from unknown (HELO box474.bluehost.com) (74.220.219.74)
	by outboundproxy5.bluehost.com with SMTP; 29 Oct 2008 17:30:17 -0000
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=labn.net;
	h=Received:X-Mailer:Date:To:From:Subject:Cc:In-Reply-To:References:Mime-Version:Content-Type:X-Identified-User;
	b=bQv7GusXQAl1Eaj2ykrwVGf0zWTuxzGkB3B9LZDN1R9GLafSyLpDfLGdXv+nqxxpl17sTi52e0SnmQC9T28ULEC9S+woTmHWjHqZla9eHjPP6JMMXe/WVQsd1yabfxAr;
Received: from box474.bluehost.com ([74.220.219.74] helo=LC2.labn.net)
	by box474.bluehost.com with esmtpa (Exim 4.69)
	(envelope-from <lberger@labn.net>)
	id 1KvErm-0000zU-NL; Wed, 29 Oct 2008 11:29:58 -0600
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Wed, 29 Oct 2008 13:29:49 -0400
To: "Zafar Ali (zali)" <zali@cisco.com>
From: Lou Berger <lberger@labn.net>
In-Reply-To: <BABC859E6D0B9A4D8448CC7F41CD2B070764A683@xmb-rtp-203.amer.
	cisco.com>
References: <BABC859E6D0B9A4D8448CC7F41CD2B070764A62F@xmb-rtp-203.amer.cisco.com>
	<E1KvDPO-0005hs-RG@psg.com>
	<BABC859E6D0B9A4D8448CC7F41CD2B070764A683@xmb-rtp-203.amer.cisco.com>
Mime-Version: 1.0
X-Identified-User: {2629:box474.bluehost.com:labnmobi:labn.net} {sentby:smtp
	auth 74.220.219.74 authed with lberger@labn.net}
Message-Id: <20081029173048.4B8323A6B0F@core3.amsl.com>
Cc: mpls@ietf.org, "Newton, Jonathan" <Jonathan.Newton@cw.com>, jpv@cisco.com,
	ccamp@ops.ietf.org, "Anca Zamfir \(ancaz\)" <ancaz@cisco.com>
Subject: Re: [mpls] Updates to draft-ietf-ccamp-mpls-graceful-shutdown
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: mpls-bounces@ietf.org
Errors-To: mpls-bounces@ietf.org

Zafar,

In short, you don't need new error codes to support the upstream 
identification of type of reroute being indicated (node, interface, 
component, label).

This can be determined based on the ERROR_SPEC object and included 
TLVs.  This is already covered in the reroute draft.  I thought the 
text at the end of 2.1 of the reroute draft was sufficiently clear to 
indicate how one would do this with the existing error codes.  I 
guess some examples for each of the cases will make this more apparent.

looks like there are still open issues in the draft(s)...

Lou

At 12:34 PM 10/29/2008, Zafar Ali (zali) wrote:
>Hi Lou-
>
> > -----Original Message-----
> > From: owner-ccamp@ops.ietf.org
> > [mailto:owner-ccamp@ops.ietf.org] On Behalf Of Lou Berger
> > Sent: Wednesday, October 29, 2008 11:56 AM
> > To: Zafar Ali (zali)
> > Cc: Lou Berger; Adrian Farrel; ccamp@ops.ietf.org;
> > mpls@ietf.org; jpv@cisco.com; Anca Zamfir (ancaz); Newton, Jonathan
> > Subject: Re: Updates to draft-ietf-ccamp-mpls-graceful-shutdown
> >
> > Zafar,
> >
> > Why does the document define new error codes (and why 4)?  Is
> > it that the reroute document isn't sufficient clear on how to
> > indicated each of the 4? Is it some other reason?
> >
>
>This is because headend may be able to compute alternate route
>("reroute" action) for mb4b differently, depending on the resource under
>graceful shutdown, as detailed in the document. Hence one code is define
>for TE node, TE link, component link of a bundled TE link, and label
>resource, each.
>
>Thanks
>
>Regards... Zafar
>
><snip>

_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls


From mpls-bounces@ietf.org  Wed Oct 29 10:41:03 2008
Return-Path: <mpls-bounces@ietf.org>
X-Original-To: mpls-archive@megatron.ietf.org
Delivered-To: ietfarch-mpls-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 60F823A69C1;
	Wed, 29 Oct 2008 10:41:03 -0700 (PDT)
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id CCC1C3A69C1
	for <mpls@core3.amsl.com>; Wed, 29 Oct 2008 10:41:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 7FNMjAB86KzN for <mpls@core3.amsl.com>;
	Wed, 29 Oct 2008 10:41:02 -0700 (PDT)
Received: from enfiets1.dataconnection.com (enfiets1.dataconnection.com
	[192.91.191.38])
	by core3.amsl.com (Postfix) with ESMTP id CBCF33A67A5
	for <mpls@lists.ietf.org>; Wed, 29 Oct 2008 10:41:01 -0700 (PDT)
Received: from ENFIMBOX1.ad.datcon.co.uk (172.18.10.27) by
	enfiets1.dataconnection.com (172.18.4.21) with Microsoft SMTP Server
	(TLS) id 8.1.291.1; Wed, 29 Oct 2008 17:41:13 +0000
Received: from ENFIMBOX1.ad.datcon.co.uk ([172.18.10.27]) by
	ENFIMBOX1.ad.datcon.co.uk ([172.18.10.27]) with mapi; Wed, 29 Oct 2008
	17:40:59 +0000
From: Nic Neate <Nic.Neate@dataconnection.com>
To: labn - Lou Berger <lberger@labn.net>, ALU - Dimitri Papadimitriou
	<Dimitri.Papadimitriou@alcatel-lucent.be>, "jpv@cisco.com" <jpv@cisco.com>
Date: Wed, 29 Oct 2008 17:40:58 +0000
Thread-Topic: Comment on draft-ietf-mpls-gmpls-lsp-reroute-02
Thread-Index: Acky/h1G/4BWDZcNQG6DJd7ClgCiNQG7uSKw
Message-ID: <11DE3EEC54A8A44EAD99D8C0D3FD72075C68F01383@ENFIMBOX1.ad.datcon.co.uk>
References: <48FCFD7D.3080306@pi.nu>
In-Reply-To: <48FCFD7D.3080306@pi.nu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
MIME-Version: 1.0
Cc: "mpls@lists.ietf.org" <mpls@lists.ietf.org>
Subject: [mpls] Comment on draft-ietf-mpls-gmpls-lsp-reroute-02
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mpls-bounces@ietf.org
Errors-To: mpls-bounces@ietf.org

Hi Lou, Dimitri, JP,

draft-ietf-mpls-gmpls-lsp-reroute doesn't explicitly include or exclude P2MP LSPs, but I think most of the function applies equally to both P2P and P2MP.  I'd like to suggest a couple of tweaks for explicit P2MP support.

1.  Section 2.3 recommends that ingress nodes use make-before-break for rerouting:

   ... When an
   alternate path is identified, a corresponding make-before-break LSP
   SHOULD be initiated, and standard make-before-break procedures MUST
   be followed.

For P2MP LSPs, the PathErr will only apply to one sub-group (or a subset of the S2L sub-LSPs in a sub-group).  It would therefore be more efficient to use sub-group-based re-optimization (RFC 4875 section 14.2) rather than make-before-break.

2.  Section 2.2 of your draft states that transit nodes MUST use "standard local repair processing":

   When the reroute request can be processed locally, standard local
   repair processing MUST be followed.

For P2MP LSPs, I think that means sub-group-based re-optimization.  If you agree, it would be helpful to state it explicitly.  If not, please could you clarify.

Thanks,

Nic

-----Original Message-----
From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf Of Loa Andersson
Sent: 20 October 2008 22:52
To: mpls@ietf.org
Cc: Ross Callon; Cisco - David Ward
Subject: [mpls] last call on three mpls wg documents

Working group,

the authors of

draft-ietf-mpls-gmpls-lsp-reroute-02.txt
draft-ietf-mpls-soft-preemption-13.txt
draft-ietf-mpls-3209-patherr-03.txt

has asked that we issue a working group last call on these document as a group. This mail starts the wg last call.

There has gone quite an effort to align the three document and to create a coherent structure.

The working group last call will end on Nov 7.

Please send comments to the working group mailing-list or to the working group co-chairs.

/Loa

--
Loa Andersson

Principal Networking Architect
Acreo AB                           phone:  +46 8 632 77 14
Isafjordsgatan 22                  mobile: +46 739 81 21 64
Kista, Sweden                      email:  loa.andersson@acreo.se
                                           loa@pi.nu _______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls
_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls


From mpls-bounces@ietf.org  Wed Oct 29 11:33:25 2008
Return-Path: <mpls-bounces@ietf.org>
X-Original-To: mpls-archive@megatron.ietf.org
Delivered-To: ietfarch-mpls-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 3B6F528C3D3;
	Wed, 29 Oct 2008 11:33:25 -0700 (PDT)
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id A176C28C3C8
	for <mpls@core3.amsl.com>; Wed, 29 Oct 2008 11:33:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5
	tests=[AWL=-0.001, BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 0BxpScPEBh+5 for <mpls@core3.amsl.com>;
	Wed, 29 Oct 2008 11:33:22 -0700 (PDT)
Received: from omzesmtp01a.verizonbusiness.com
	(omzesmtp01a.verizonbusiness.com [199.249.25.195])
	by core3.amsl.com (Postfix) with ESMTP id BD16028C3D3
	for <mpls@ietf.org>; Wed, 29 Oct 2008 11:33:22 -0700 (PDT)
Received: from dgismtp02.mcilink.com ([166.38.58.142])
	by firewall.verizonbusiness.com
	(Sun Java(tm) System Messaging Server 6.3-5.02 (built Oct 12 2007;
	32bit))
	with ESMTP id <0K9I00589JJ9SW00@firewall.verizonbusiness.com> for
	mpls@ietf.org; Wed, 29 Oct 2008 18:33:09 +0000 (GMT)
Received: from dgismtp02.mcilink.com ([127.0.0.1])
	by dgismtp02.mcilink.com (iPlanet Messaging Server 5.2 HotFix 2.08
	(built Sep
	22 2005)) with SMTP id <0K9I00I21JJ84A@dgismtp02.mcilink.com> for
	mpls@ietf.org; Wed, 29 Oct 2008 18:33:09 +0000 (GMT)
Received: from ASHSRV142.mcilink.com ([153.39.68.168])
	by dgismtp02.mcilink.com (iPlanet Messaging Server 5.2 HotFix 2.08
	(built Sep
	22 2005)) with ESMTP id <0K9I00FL7JIZOY@dgismtp02.mcilink.com> for
	mpls@ietf.org; Wed, 29 Oct 2008 18:33:08 +0000 (GMT)
Received: from ASHEVS010.mcilink.com ([153.39.69.135])
	by ASHSRV142.mcilink.com with Microsoft SMTPSVC(6.0.3790.3959); Wed,
	29 Oct 2008 18:33:01 +0000
Date: Wed, 29 Oct 2008 18:33:00 +0000
From: "So, Ning" <ning.so@verizonbusiness.com>
To: mpls@ietf.org
Message-id: <84042721A487BB4C83FC772185400CB707C74984@ASHEVS010.mcilink.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
Thread-topic: new draft of the framework and requirements for Composite
	Transport Group
Thread-index: Ack59MV2td38Ol3zSiK/n0oUUMJseQ==
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
X-OriginalArrivalTime: 29 Oct 2008 18:33:01.0704 (UTC)
	FILETIME=[C6369880:01C939F4]
Subject: [mpls] new draft of the framework and requirements for Composite
 Transport Group
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1347698073=="
Sender: mpls-bounces@ietf.org
Errors-To: mpls-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1347698073==
Content-type: multipart/alternative;
 boundary="----_=_NextPart_001_01C939F4.C5B0E467"
Content-class: urn:content-classes:message

This is a multi-part message in MIME format.

------_=_NextPart_001_01C939F4.C5B0E467
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Dear all,

=20

We have uploaded the draft of the framework and requirements for
Composite Transport Group.

=20

=20

http://www.ietf.org/internet-drafts/draft-so-yong-mpls-ctg-framework-req
uirement-00.txt

=20

=20

Abstract

=20

   This document states a traffic distribution problem in today's IP/

   MPLS network when multiple links are configured between two routers.

   The document presents a Composite Transport Group framework as the

   solution for the problems and specifies a set of requirements for

   Composite Transport Group(CTG).

=20

We appreciate your input/comments and look forward to discussing in
Minneapolis.

=20

=20

Ning So

Lead Engineer

Data Traffic Engineering

972-729-7905

=20

=20


------_=_NextPart_001_01C939F4.C5B0E467
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:x=3D"urn:schemas-microsoft-com:office:excel" =
xmlns:st1=3D"urn:schemas-microsoft-com:office:smarttags" =
xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"City"/>
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"place"/>
<!--[if !mso]>
<style>
st1\:*{behavior:url(#default#ieooui) }
</style>
<![endif]-->
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:#606420;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:Arial;
	color:windowtext;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
	{page:Section1;}
-->
</style>

</head>

<body lang=3DEN-US link=3Dblue vlink=3D"#606420">

<div class=3DSection1>

<p class=3DMsoNormal><font size=3D3 face=3DTahoma><span =
style=3D'font-size:12.0pt;
font-family:Tahoma'>Dear all,<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3DTahoma><span =
style=3D'font-size:12.0pt;
font-family:Tahoma'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3DTahoma><span =
style=3D'font-size:12.0pt;
font-family:Tahoma'>We have uploaded the draft of the framework and =
requirements
for Composite Transport Group.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3DTahoma><span =
style=3D'font-size:12.0pt;
font-family:Tahoma'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3DTahoma><span =
style=3D'font-size:12.0pt;
font-family:Tahoma'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><u><font size=3D3 color=3Dblue face=3DTahoma><span
style=3D'font-size:12.0pt;font-family:Tahoma;color:blue'><a
href=3D"http://www.ietf.org/internet-drafts/draft-so-yong-mpls-ctg-framew=
ork-requirement-00.txt"
title=3D"http://www.ietf.org/internet-drafts/draft-so-yong-mpls-ctg-frame=
work-requirement-00.txt">http://www.ietf.org/internet-drafts/draft-so-yon=
g-mpls-ctg-framework-requirement-00.txt</a></span></font></u><font
face=3DTahoma><span =
style=3D'font-family:Tahoma'><o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3DTahoma><span =
style=3D'font-size:12.0pt;
font-family:Tahoma'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3DTahoma><span =
style=3D'font-size:12.0pt;
font-family:Tahoma'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3DTahoma><span =
style=3D'font-size:12.0pt;
font-family:Tahoma'>Abstract<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3DTahoma><span =
style=3D'font-size:12.0pt;
font-family:Tahoma'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3DTahoma><span =
style=3D'font-size:12.0pt;
font-family:Tahoma'>&nbsp;&nbsp; This document states a traffic =
distribution
problem in today's IP/<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3DTahoma><span =
style=3D'font-size:12.0pt;
font-family:Tahoma'>&nbsp;&nbsp; MPLS network when multiple links are
configured between two routers.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3DTahoma><span =
style=3D'font-size:12.0pt;
font-family:Tahoma'>&nbsp;&nbsp; The document presents a Composite =
Transport
Group framework as the<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3DTahoma><span =
style=3D'font-size:12.0pt;
font-family:Tahoma'>&nbsp;&nbsp; solution for the problems and specifies =
a set
of requirements for<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3DTahoma><span =
style=3D'font-size:12.0pt;
font-family:Tahoma'>&nbsp;&nbsp; Composite Transport =
Group(CTG).<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3DTahoma><span =
style=3D'font-size:12.0pt;
font-family:Tahoma'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3DTahoma><span =
style=3D'font-size:12.0pt;
font-family:Tahoma'>We appreciate your input/comments and look forward =
to
discussing in <st1:place w:st=3D"on"><st1:City =
w:st=3D"on">Minneapolis</st1:City></st1:place>.<o:p></o:p></span></font><=
/p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Ning So</span></font><o:p></o:p></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Lead Engineer</span></font><o:p></o:p></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Data Traffic Engineering</span></font><o:p></o:p></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>972-729-7905</span></font><o:p></o:p></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>&nbsp;</span><o:p></o:p></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

</div>

</body>

</html>

------_=_NextPart_001_01C939F4.C5B0E467--

--===============1347698073==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls

--===============1347698073==--


From mpls-bounces@ietf.org  Thu Oct 30 13:16:48 2008
Return-Path: <mpls-bounces@ietf.org>
X-Original-To: mpls-archive@megatron.ietf.org
Delivered-To: ietfarch-mpls-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 827DC3A6782;
	Thu, 30 Oct 2008 13:16:48 -0700 (PDT)
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id DF8D23A68BF
	for <mpls@core3.amsl.com>; Thu, 30 Oct 2008 13:16:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.072
X-Spam-Level: 
X-Spam-Status: No, score=-2.072 tagged_above=-999 required=5 tests=[AWL=0.526, 
	BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id avl+laYW-EP6 for <mpls@core3.amsl.com>;
	Thu, 30 Oct 2008 13:16:45 -0700 (PDT)
Received: from ashesmtp02.verizonbusiness.com (ashesmtp02.verizonbusiness.com
	[198.4.8.166]) by core3.amsl.com (Postfix) with ESMTP id A32C83A6B15
	for <mpls@ietf.org>; Thu, 30 Oct 2008 13:15:56 -0700 (PDT)
Received: from pmismtp02.mcilink.com ([166.37.158.162])
	by firewall.verizonbusiness.com
	(Sun Java(tm) System Messaging Server 6.3-5.02 (built Oct 12 2007;
	32bit))
	with ESMTP id <0K9K00262IYE4300@firewall.verizonbusiness.com> for
	mpls@ietf.org; Thu, 30 Oct 2008 20:15:51 +0000 (GMT)
Received: from pmismtp02.mcilink.com ([127.0.0.1])
	by pmismtp02.mcilink.com (iPlanet Messaging Server 5.2 HotFix 2.08
	(built Sep
	22 2005)) with SMTP id <0K9K004O8IYEP0@pmismtp02.mcilink.com> for
	mpls@ietf.org; Thu, 30 Oct 2008 20:15:50 +0000 (GMT)
Received: from ASHSRV142.mcilink.com ([153.39.68.168])
	by pmismtp02.mcilink.com (iPlanet Messaging Server 5.2 HotFix 2.08
	(built Sep
	22 2005)) with ESMTP id <0K9K004HIIYEO8@pmismtp02.mcilink.com> for
	mpls@ietf.org; Thu, 30 Oct 2008 20:15:50 +0000 (GMT)
Received: from ASHEVS010.mcilink.com ([153.39.69.135])
	by ASHSRV142.mcilink.com with Microsoft SMTPSVC(6.0.3790.3959); Thu,
	30 Oct 2008 20:15:50 +0000
Date: Thu, 30 Oct 2008 20:15:49 +0000
From: "So, Ning" <ning.so@verizonbusiness.com>
In-reply-to: <43B621735DF9CF41819D5DE90D12923E0679F5@intrepid.sycamorenet.com>
To: "Mirsky, Gregory" <gregory.mirsky@sycamorenet.com>, mpls@ietf.org
Message-id: <84042721A487BB4C83FC772185400CB707C74994@ASHEVS010.mcilink.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
Thread-topic: [mpls] new draft of the framework and requirements for Composite
	Transport Group
Thread-index: Ack59MV2td38Ol3zSiK/n0oUUMJseQAw7hlAAASjqvA=
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
References: <84042721A487BB4C83FC772185400CB707C74984@ASHEVS010.mcilink.com>
	<43B621735DF9CF41819D5DE90D12923E0679F5@intrepid.sycamorenet.com>
X-OriginalArrivalTime: 30 Oct 2008 20:15:50.0388 (UTC)
	FILETIME=[4D72D340:01C93ACC]
Subject: Re: [mpls] new draft of the framework and requirements for
 Composite Transport Group
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0449916782=="
Sender: mpls-bounces@ietf.org
Errors-To: mpls-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0449916782==
Content-type: multipart/alternative;
 boundary="----_=_NextPart_001_01C93ACC.4CBDB899"
Content-class: urn:content-classes:message

This is a multi-part message in MIME format.

------_=_NextPart_001_01C93ACC.4CBDB899
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Gregg,

=20

The LSP and connection mapping to the component link in CTG is done
using constrain based routing with the shortest path first.
Bi-directional LSPs being routed onto the same component link or not
should not be a problem in MPLS environment.  Are you saying that in
some cases in GMPLS environment, bi-directional LSP has to be carried on
the same component link?  What problem would occur if they are carried
on different component links?  Would that problem still exist if the
different component links have the same performance objectives such as
latency?  I need a bit more detail in order to understand your concern.=20

=20

Ning So

Lead Engineer

Data Traffic Engineering

972-729-7905

=20

________________________________

From: Mirsky, Gregory [mailto:gregory.mirsky@sycamorenet.com]=20
Sent: Thursday, October 30, 2008 1:17 PM
To: So, Ning; mpls@ietf.org
Subject: RE: [mpls] new draft of the framework and requirements for
Composite Transport Group

=20

Dear So,

if a bidirectional TE LSP is signaled by (G)MPLS how would CTG guarantee
that the same Component Link is used in each direction? As I understand,
mapping of particular TE LSP to the Component Link is local policy-based
decision. If my understanding is correct, should it be a requirement for
the CTG to provide controls to support co-routed mapping of
bidirectional/co-routed LSP?

=20

    Regards,

        Greg

=20

________________________________

From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf Of
So, Ning
Sent: Wednesday, October 29, 2008 2:33 PM
To: mpls@ietf.org
Subject: [mpls] new draft of the framework and requirements for
Composite Transport Group

Dear all,

=20

We have uploaded the draft of the framework and requirements for
Composite Transport Group.

=20

=20

http://www.ietf.org/internet-drafts/draft-so-yong-mpls-ctg-framework-req
uirement-00.txt

=20

=20

Abstract

=20

   This document states a traffic distribution problem in today's IP/

   MPLS network when multiple links are configured between two routers.

   The document presents a Composite Transport Group framework as the

   solution for the problems and specifies a set of requirements for

   Composite Transport Group(CTG).

=20

We appreciate your input/comments and look forward to discussing in
Minneapolis.

=20

=20

Ning So

Lead Engineer

Data Traffic Engineering

972-729-7905

=20

=20


------_=_NextPart_001_01C93ACC.4CBDB899
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:x=3D"urn:schemas-microsoft-com:office:excel" =
xmlns:st1=3D"urn:schemas-microsoft-com:office:smarttags" =
xmlns=3D"http://www.w3.org/TR/REC-html40"
xmlns:ns0=3D"urn:schemas-microsoft-com:office:smarttags">

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]--><o:SmartTagType
 namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags" =
name=3D"City"/>
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"place"/>
<!--[if !mso]>
<style>
st1\:*{behavior:url(#default#ieooui) }
</style>
<![endif]-->
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:#606420;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal;
	font-family:Arial;
	color:windowtext;}
span.EmailStyle18
	{mso-style-type:personal-reply;
	font-family:Arial;
	color:navy;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
	{page:Section1;}
-->
</style>

</head>

<body lang=3DEN-US link=3Dblue vlink=3D"#606420">

<div class=3DSection1>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Gregg,<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>The LSP and connection mapping to =
the
component link in CTG is done using constrain based routing with the =
shortest
path first.&nbsp; Bi-directional LSPs being routed onto the same =
component link
or not should not be a problem in MPLS environment. &nbsp;Are you saying =
that
in some cases in GMPLS environment, bi-directional LSP has to be carried =
on the
same component link?&nbsp; What problem would occur if they are carried =
on
different component links?&nbsp; Would that problem still exist if the =
different
component links have the same performance objectives such as =
latency?&nbsp; I
need a bit more detail in order to understand your concern. =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<div>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Ning So</span></font><font =
color=3Dnavy><span
style=3D'color:navy'><o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Lead Engineer</span></font><font
color=3Dnavy><span style=3D'color:navy'><o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Data Traffic =
Engineering</span></font><font
color=3Dnavy><span style=3D'color:navy'><o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>972-729-7905</span></font><font
color=3Dnavy><span style=3D'color:navy'><o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 color=3Dnavy face=3D"Times New =
Roman"><span
style=3D'font-size:12.0pt;color:navy'>&nbsp;</span></font><o:p></o:p></p>=


</div>

<div>

<div class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
face=3D"Times New Roman"><span style=3D'font-size:12.0pt'>

<hr size=3D2 width=3D"100%" align=3Dcenter tabindex=3D-1>

</span></font></div>

<p class=3DMsoNormal><b><font size=3D2 face=3DTahoma><span =
style=3D'font-size:10.0pt;
font-family:Tahoma;font-weight:bold'>From:</span></font></b><font =
size=3D2
face=3DTahoma><span style=3D'font-size:10.0pt;font-family:Tahoma'> =
Mirsky, Gregory
[mailto:gregory.mirsky@sycamorenet.com] <br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> Thursday, October =
30, 2008
1:17 PM<br>
<b><span style=3D'font-weight:bold'>To:</span></b> So, Ning; =
mpls@ietf.org<br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> RE: [mpls] new =
draft of
the framework and requirements for Composite Transport =
Group</span></font><o:p></o:p></p>

</div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblue face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:blue'>Dear =
So,</span></font><o:p></o:p></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblue face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:blue'>if a bidirectional TE LSP is =
signaled by
(G)MPLS how would CTG guarantee that the same Component Link is used in =
each
direction? As I understand, mapping of particular TE LSP to the =
Component Link
is local policy-based decision. If my understanding is correct, should =
it be a
requirement for the&nbsp;CTG to provide controls to support co-routed =
mapping
of bidirectional/co-routed LSP?</span></font><o:p></o:p></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>&nbsp;<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>&nbsp;&nbsp;&nbsp; </span></font><font size=3D2 color=3Dblue =
face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial;color:blue'>Regards,</span></=
font><o:p></o:p></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></font><font =
size=3D2
color=3Dblue face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;
color:blue'>Greg</span></font><o:p></o:p></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

<div class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
face=3D"Times New Roman"><span style=3D'font-size:12.0pt'>

<hr size=3D2 width=3D"100%" align=3Dcenter tabIndex=3D-1>

</span></font></div>

<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><b><font size=3D2 =
face=3DTahoma><span
style=3D'font-size:10.0pt;font-family:Tahoma;font-weight:bold'>From:</spa=
n></font></b><font
size=3D2 face=3DTahoma><span =
style=3D'font-size:10.0pt;font-family:Tahoma'>
mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] <b><span =
style=3D'font-weight:
bold'>On Behalf Of </span></b>So, Ning<br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> Wednesday, October =
29, 2008
2:33 PM<br>
<b><span style=3D'font-weight:bold'>To:</span></b> mpls@ietf.org<br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> [mpls] new draft =
of the
framework and requirements for Composite Transport =
Group</span></font><o:p></o:p></p>

<p class=3DMsoNormal><font size=3D3 face=3DTahoma><span =
style=3D'font-size:12.0pt;
font-family:Tahoma'>Dear all,<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3DTahoma><span =
style=3D'font-size:12.0pt;
font-family:Tahoma'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3DTahoma><span =
style=3D'font-size:12.0pt;
font-family:Tahoma'>We have uploaded the draft of the framework and
requirements for Composite Transport Group.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3DTahoma><span =
style=3D'font-size:12.0pt;
font-family:Tahoma'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3DTahoma><span =
style=3D'font-size:12.0pt;
font-family:Tahoma'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><u><font size=3D3 color=3Dblue face=3DTahoma><span
style=3D'font-size:12.0pt;font-family:Tahoma;color:blue'><a
href=3D"http://www.ietf.org/internet-drafts/draft-so-yong-mpls-ctg-framew=
ork-requirement-00.txt"
title=3D"http://www.ietf.org/internet-drafts/draft-so-yong-mpls-ctg-frame=
work-requirement-00.txt">http://www.ietf.org/internet-drafts/draft-so-yon=
g-mpls-ctg-framework-requirement-00.txt</a></span></font></u><font
face=3DTahoma><span =
style=3D'font-family:Tahoma'><o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3DTahoma><span =
style=3D'font-size:12.0pt;
font-family:Tahoma'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3DTahoma><span =
style=3D'font-size:12.0pt;
font-family:Tahoma'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3DTahoma><span =
style=3D'font-size:12.0pt;
font-family:Tahoma'>Abstract<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3DTahoma><span =
style=3D'font-size:12.0pt;
font-family:Tahoma'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3DTahoma><span =
style=3D'font-size:12.0pt;
font-family:Tahoma'>&nbsp;&nbsp; This document states a traffic =
distribution
problem in today's IP/<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3DTahoma><span =
style=3D'font-size:12.0pt;
font-family:Tahoma'>&nbsp;&nbsp; MPLS network when multiple links are
configured between two routers.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3DTahoma><span =
style=3D'font-size:12.0pt;
font-family:Tahoma'>&nbsp;&nbsp; The document presents a Composite =
Transport
Group framework as the<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3DTahoma><span =
style=3D'font-size:12.0pt;
font-family:Tahoma'>&nbsp;&nbsp; solution for the problems and specifies =
a set
of requirements for<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3DTahoma><span =
style=3D'font-size:12.0pt;
font-family:Tahoma'>&nbsp;&nbsp; Composite Transport =
Group(CTG).<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3DTahoma><span =
style=3D'font-size:12.0pt;
font-family:Tahoma'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3DTahoma><span =
style=3D'font-size:12.0pt;
font-family:Tahoma'>We appreciate your input/comments and look forward =
to
discussing in <st1:place w:st=3D"on"><st1:City w:st=3D"on"><st1:City =
w:st=3D"on"><st1:place
 =
w:st=3D"on">Minneapolis</st1:City></st1:place></st1:place></st1:City>.<o:=
p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Ning So</span></font><o:p></o:p></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Lead Engineer</span></font><o:p></o:p></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Data Traffic Engineering</span></font><o:p></o:p></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>972-729-7905</span></font><o:p></o:p></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>&nbsp;<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

</div>

</body>

</html>

------_=_NextPart_001_01C93ACC.4CBDB899--

--===============0449916782==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls

--===============0449916782==--


From mpls-bounces@ietf.org  Thu Oct 30 18:37:20 2008
Return-Path: <mpls-bounces@ietf.org>
X-Original-To: mpls-archive@megatron.ietf.org
Delivered-To: ietfarch-mpls-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id AC9AC3A6A8B;
	Thu, 30 Oct 2008 18:37:20 -0700 (PDT)
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id DCF813A6A34
	for <mpls@core3.amsl.com>; Thu, 30 Oct 2008 18:37:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id AwoNtRxJNw+u for <mpls@core3.amsl.com>;
	Thu, 30 Oct 2008 18:37:18 -0700 (PDT)
Received: from exprod7og108.obsmtp.com (exprod7og108.obsmtp.com [64.18.2.169])
	by core3.amsl.com (Postfix) with ESMTP id D7D053A687F
	for <mpls@ietf.org>; Thu, 30 Oct 2008 18:37:17 -0700 (PDT)
Received: from source ([66.129.228.6]) by exprod7ob108.postini.com
	([64.18.6.12]) with SMTP; Thu, 30 Oct 2008 18:37:17 PDT
Received: from emailcorp3.jnpr.net ([66.129.254.13]) by p-emsmtp01.jnpr.net
	with Microsoft SMTPSVC(6.0.3790.3959); 
	Thu, 30 Oct 2008 18:35:45 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Thu, 30 Oct 2008 18:35:45 -0700
Message-ID: <7FA0C743C38E5340BFC2873488FA1E8E025DDC5A@emailcorp3.jnpr.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: New Version Notification for
	draft-nitinb-lsp-ping-rsvp-protection-00 
Thread-Index: Ack4dbo1lHS2rBuCRIKckhxlha6i6wCgvGEA
From: "Nitin Bahadur" <nitinb@juniper.net>
To: <mpls@ietf.org>
X-OriginalArrivalTime: 31 Oct 2008 01:35:46.0055 (UTC)
	FILETIME=[FEF52970:01C93AF8]
Subject: [mpls] New Version Notification for
	draft-nitinb-lsp-ping-rsvp-protection-00
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mpls-bounces@ietf.org
Errors-To: mpls-bounces@ietf.org


Folks,

  I would appreciate comments on the new submission.

Thanks
Nitin 

-----Original Message-----
Filename:	 draft-nitinb-lsp-ping-rsvp-protection
Revision:	 00
Title:		 Mechanism for performing LSP-Ping over RSVP protection
paths

Abstract:
This document describes methods for performing lsp ping over mpls
rsvp-te protection paths, when the protection paths are not in use.
Conventional LSP-Ping follows the same path as data traffic.  In some
cases, it might be useful to follow the data path of protection paths
(detours and bypasses) to ensure that the those paths are fully
functional.  This document describes enhancements to LSP-Ping to perform
ping over such paths.
_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls


From mpls-bounces@ietf.org  Thu Oct 30 22:11:28 2008
Return-Path: <mpls-bounces@ietf.org>
X-Original-To: mpls-archive@megatron.ietf.org
Delivered-To: ietfarch-mpls-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id A3F4828C1D0;
	Thu, 30 Oct 2008 22:11:28 -0700 (PDT)
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 097C33A6994;
	Thu, 30 Oct 2008 22:11:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.09
X-Spam-Level: 
X-Spam-Status: No, score=-0.09 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id qArRpSRNq-rC; Thu, 30 Oct 2008 22:11:26 -0700 (PDT)
Received: from mail4.hitachi.co.jp (mail4.hitachi.co.jp [133.145.228.5])
	by core3.amsl.com (Postfix) with ESMTP id 7B55F3A684A;
	Thu, 30 Oct 2008 22:11:22 -0700 (PDT)
Received: from mlsv1.hitachi.co.jp (unknown [133.144.234.166])
	by mail4.hitachi.co.jp (Postfix) with ESMTP id C36F433CC6;
	Fri, 31 Oct 2008 14:11:20 +0900 (JST)
Received: from MFILTER-S3.hitachi.co.jp by mlsv1.hitachi.co.jp (8.13.1/8.13.1)
	id m9V5BKkX029425; Fri, 31 Oct 2008 14:11:20 +0900
Received: from vshuts2.hitachi.co.jp (unverified) by MFILTER-S3.hitachi.co.jp
	(Content Technologies SMTPRS 4.3.17) with ESMTP id
	<T8a5fa7353d0ac906ac5d0@MFILTER-S3.hitachi.co.jp>; 
	Fri, 31 Oct 2008 14:11:20 +0900
X-AuditID: 0ac90647-ac051ba00000286d-18-490a93789b77
Received: from gmml28.itg.hitachi.co.jp (unknown [158.213.165.131])
	by vshuts2.hitachi.co.jp (Symantec Mail Security) with ESMTP id
	7707F8B0217; Fri, 31 Oct 2008 14:11:20 +0900 (JST)
Received: from [127.0.0.1] by gmml28.itg.hitachi.co.jp
	(AIX5.2/8.11.6p2/8.11.0) id m9V5BKZ9142514;
	Fri, 31 Oct 2008 14:11:20 +0900
Date: Fri, 31 Oct 2008 14:11:20 +0900
From: Hideki ENDO <hideki.endo.es@hitachi.com>
To: pwe3 <pwe3@ietf.org>
In-Reply-To: <4906E57E.4050105@pi.nu>
References: <4906E57E.4050105@pi.nu>
Message-Id: <20081031140709.F11D.27B3C191@hitachi.com>
MIME-Version: 1.0
X-Mailer: Becky! ver. 2.48.02 [ja]
X-Brightmail-Tracker: AAAAAA==
Cc: ccamp <ccamp@ops.ietf.org>, "mpls@ietf.org" <mpls@ietf.org>, pwe3@ietf.org,
	"ahtmpls@itu.int" <ahtmpls@itu.int>
Subject: Re: [mpls] [PWE3] draft-bocci-mpls-tp-gach-gal-00.txt for mpls wg
	doc
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mpls-bounces@ietf.org
Errors-To: mpls-bounces@ietf.org

I support.

Best Regards, 
Hideki ENDO


On Tue, 28 Oct 2008 11:12:14 +0100
Loa Andersson <loa@pi.nu> wrote:

> Working group(s),
> 
> this is to initiate a two week poll to see if
> draft-bocci-mpls-tp-gach-gal-00.txt is in shape to
> become a mpls working group document.
> 
> The current draft is a merge of to earlier draft
> one that defined the GAL and another that specified
> the generic associated channel.
> 
> Please send your responses to the mpls working group
> mailing list (needs a bit of discipline, "replay all"
> won't do the trick ;) .
> 
> Please respond on Tuesday Oct 11 the latest.
> 
> /Loa
> 
> -- 
> Loa Andersson
> 
> Principal Networking Architect
> Acreo AB                           phone:  +46 8 632 77 14
> Isafjordsgatan 22                  mobile: +46 739 81 21 64
> Kista, Sweden                      email:  loa.andersson@acreo.se
>                                            loa@pi.nu
> _______________________________________________
> pwe3 mailing list
> pwe3@ietf.org
> https://www.ietf.org/mailman/listinfo/pwe3




_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls


From mpls-bounces@ietf.org  Fri Oct 31 04:08:53 2008
Return-Path: <mpls-bounces@ietf.org>
X-Original-To: mpls-archive@megatron.ietf.org
Delivered-To: ietfarch-mpls-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 1560C28C18D;
	Fri, 31 Oct 2008 04:08:53 -0700 (PDT)
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 9B46C28C1B4
	for <mpls@core3.amsl.com>; Fri, 31 Oct 2008 04:08:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.248
X-Spam-Level: 
X-Spam-Status: No, score=-3.248 tagged_above=-999 required=5 tests=[AWL=0.000, 
	BAYES_00=-2.599, HELO_EQ_FR=0.35, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id ofjbCacPHgla for <mpls@core3.amsl.com>;
	Fri, 31 Oct 2008 04:08:51 -0700 (PDT)
Received: from p-mail1.rd.francetelecom.com (p-mail1.rd.francetelecom.com
	[195.101.245.15])
	by core3.amsl.com (Postfix) with ESMTP id 7C4A128C18D
	for <mpls@ietf.org>; Fri, 31 Oct 2008 04:08:50 -0700 (PDT)
Received: from FTRDMEL2.rd.francetelecom.fr ([10.193.117.153]) by
	ftrdsmtp1.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 31 Oct 2008 12:08:44 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Fri, 31 Oct 2008 12:08:43 +0100
Message-ID: <8AA97249241F7148BE6D3D8B93D83F5A138DA1F8@ftrdmel2>
In-Reply-To: <C52CFC88.9CD1%swallow@cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [mpls] draft-bocci-mpls-tp-gach-gal-00.txt for mpls wg doc
Thread-Index: Ack45byfagYrwvvLT9mCMeJee3MqKwANnugwAAoEwGIAgON2QA==
References: <4A5028372622294A99B8FFF6BD06EB7B04C95204@USDALSMBS03.ad3.ad.alcatel.com>
	<C52CFC88.9CD1%swallow@cisco.com>
From: <frederic.jounay@orange-ftgroup.com>
To: <loa@pi.nu>,
	<mpls@ietf.org>
X-OriginalArrivalTime: 31 Oct 2008 11:08:44.0722 (UTC)
	FILETIME=[0A3D7120:01C93B49]
Subject: Re: [mpls] draft-bocci-mpls-tp-gach-gal-00.txt for mpls wg doc
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mpls-bounces@ietf.org
Errors-To: mpls-bounces@ietf.org

Support

Fred.

_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls
_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls


From mpls-bounces@ietf.org  Fri Oct 31 05:32:49 2008
Return-Path: <mpls-bounces@ietf.org>
X-Original-To: mpls-archive@megatron.ietf.org
Delivered-To: ietfarch-mpls-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E6E5E28C1ED;
	Fri, 31 Oct 2008 05:32:48 -0700 (PDT)
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 08EE228C0E3
	for <mpls@core3.amsl.com>; Fri, 31 Oct 2008 05:32:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id qTqBhudE7KGJ for <mpls@core3.amsl.com>;
	Fri, 31 Oct 2008 05:32:47 -0700 (PDT)
Received: from rtp-iport-1.cisco.com (rtp-iport-1.cisco.com [64.102.122.148])
	by core3.amsl.com (Postfix) with ESMTP id 2A9B028C166
	for <mpls@ietf.org>; Fri, 31 Oct 2008 05:32:47 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,522,1220227200"; d="scan'208";a="26332669"
Received: from rtp-dkim-1.cisco.com ([64.102.121.158])
	by rtp-iport-1.cisco.com with ESMTP; 31 Oct 2008 12:32:45 +0000
Received: from rtp-core-1.cisco.com (rtp-core-1.cisco.com [64.102.124.12])
	by rtp-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id m9VCWjsR032249; 
	Fri, 31 Oct 2008 08:32:45 -0400
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com
	[64.102.31.102])
	by rtp-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m9VCWj9Z012425;
	Fri, 31 Oct 2008 12:32:45 GMT
Received: from xmb-rtp-211.amer.cisco.com ([64.102.31.118]) by
	xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 31 Oct 2008 08:32:45 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Fri, 31 Oct 2008 08:32:44 -0400
Message-ID: <DD7E9F364F33B54881C225192D4872D7A879BE@xmb-rtp-211.amer.cisco.com>
In-Reply-To: <8AA97249241F7148BE6D3D8B93D83F5A138DA1F8@ftrdmel2>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [mpls] draft-bocci-mpls-tp-gach-gal-00.txt for mpls wg doc
Thread-Index: Ack45byfagYrwvvLT9mCMeJee3MqKwANnugwAAoEwGIAgON2QAADMIqQ
References: <4A5028372622294A99B8FFF6BD06EB7B04C95204@USDALSMBS03.ad3.ad.alcatel.com><C52CFC88.9CD1%swallow@cisco.com>
	<8AA97249241F7148BE6D3D8B93D83F5A138DA1F8@ftrdmel2>
From: "Luyuan Fang (lufang)" <lufang@cisco.com>
To: <loa@pi.nu>, <mpls@ietf.org>
X-OriginalArrivalTime: 31 Oct 2008 12:32:45.0285 (UTC)
	FILETIME=[C6A65150:01C93B54]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=23; t=1225456365; x=1226320365;
	c=relaxed/simple; s=rtpdkim1001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=lufang@cisco.com;
	z=From:=20=22Luyuan=20Fang=20(lufang)=22=20<lufang@cisco.com >
	|Subject:=20RE=3A=20[mpls]=20draft-bocci-mpls-tp-gach-gal-0
	0.txt=20for=20mpls=20wg=20doc |Sender:=20
	|To:=20<loa@pi.nu>,=20<mpls@ietf.org>;
	bh=mX2RULROPLFnHLeetUSKFag5tMHkHPt+dh1Ig2mhTi8=;
	b=YzrtcsgT5nbUWoriy63SCpa4za0PrdbfLqIogIGcD9u9LLbiBjWQ6hLY/D
	AumlusgoDWgqgl+b1gSZPMH3Kgyu7HfDmtoNHHE+pF9r5eOEjSCqAjd2UQHe
	6AI8LQHEnb;
Authentication-Results: rtp-dkim-1; header.From=lufang@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim1001 verified; ); 
Subject: Re: [mpls] draft-bocci-mpls-tp-gach-gal-00.txt for mpls wg doc
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mpls-bounces@ietf.org
Errors-To: mpls-bounces@ietf.org

Support.

Luyuan 
_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls


From mpls-bounces@ietf.org  Fri Oct 31 06:02:58 2008
Return-Path: <mpls-bounces@ietf.org>
X-Original-To: mpls-archive@megatron.ietf.org
Delivered-To: ietfarch-mpls-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 5A09F3A6C0F;
	Fri, 31 Oct 2008 06:02:58 -0700 (PDT)
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 17E723A6D7F;
	Fri, 31 Oct 2008 06:02:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 90KcsrBIH9-K; Fri, 31 Oct 2008 06:02:56 -0700 (PDT)
Received: from fg-out-1718.google.com (fg-out-1718.google.com [72.14.220.155])
	by core3.amsl.com (Postfix) with ESMTP id E44D03A6963;
	Fri, 31 Oct 2008 06:02:43 -0700 (PDT)
Received: by fg-out-1718.google.com with SMTP id d23so946012fga.41
	for <multiple recipients>; Fri, 31 Oct 2008 06:02:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
	h=domainkey-signature:received:received:message-id:date:from:to
	:subject:cc:in-reply-to:mime-version:content-type
	:content-transfer-encoding:content-disposition:references;
	bh=3XbTaHq7ddmUMfBBxkg/gJMGGzi08jjSx7VTgiv+a+8=;
	b=EJ6lAra3nE/8RuFfOJb8EEnrZ8ZwewXu39K901y8nW6gc74niWHr4XmPkEVCVGXOvi
	VgQ7xZrgRWvrtcsz7LAqw8bkWRv2fQXgEukYkkqpHX+jPxvoC8f2unsAyCBhSs8zy02X
	aiNbewj6BjM9Kf+jDnE6Y26PqFPmXq0UJzqBM=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=message-id:date:from:to:subject:cc:in-reply-to:mime-version
	:content-type:content-transfer-encoding:content-disposition
	:references;
	b=FKNFHFJUlxk3RkOxGmF3uQ5uwAE+ts9c3zE8dc6xXXgsgN1JnfeY/68q9J9qoExJQC
	7dsFg5nO+9WEHwIuSZlnha5hYhL7p7qQZrTN/Cdt1fdoo/15byyTFd2qdRYuEpM8AwHq
	8tm75zpwlO1MAkthzvJLgcHBUxOT2NpHuFxWI=
Received: by 10.86.59.18 with SMTP id h18mr8200545fga.42.1225458161330;
	Fri, 31 Oct 2008 06:02:41 -0700 (PDT)
Received: by 10.86.65.12 with HTTP; Fri, 31 Oct 2008 06:02:41 -0700 (PDT)
Message-ID: <b2d141720810310602p2d9d321ela1077c5e3ea0f6b7@mail.gmail.com>
Date: Fri, 31 Oct 2008 09:02:41 -0400
From: "Andrew G. Malis" <amalis@gmail.com>
To: "Loa Andersson" <loa@pi.nu>
In-Reply-To: <4906E57E.4050105@pi.nu>
MIME-Version: 1.0
Content-Disposition: inline
References: <4906E57E.4050105@pi.nu>
Cc: ccamp <ccamp@ops.ietf.org>, "mpls@ietf.org" <mpls@ietf.org>,
	pwe3 <pwe3@ietf.org>, "ahtmpls@itu.int" <ahtmpls@itu.int>
Subject: Re: [mpls] [PWE3] draft-bocci-mpls-tp-gach-gal-00.txt for mpls wg
	doc
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mpls-bounces@ietf.org
Errors-To: mpls-bounces@ietf.org

Support.

On Tue, Oct 28, 2008 at 6:12 AM, Loa Andersson <loa@pi.nu> wrote:
> Working group(s),
>
> this is to initiate a two week poll to see if
> draft-bocci-mpls-tp-gach-gal-00.txt is in shape to
> become a mpls working group document.
>
> The current draft is a merge of to earlier draft
> one that defined the GAL and another that specified
> the generic associated channel.
>
> Please send your responses to the mpls working group
> mailing list (needs a bit of discipline, "replay all"
> won't do the trick ;) .
>
> Please respond on Tuesday Oct 11 the latest.
>
> /Loa
>
> --
> Loa Andersson
>
> Principal Networking Architect
> Acreo AB                           phone:  +46 8 632 77 14
> Isafjordsgatan 22                  mobile: +46 739 81 21 64
> Kista, Sweden                      email:  loa.andersson@acreo.se
>                                           loa@pi.nu
> _______________________________________________
> pwe3 mailing list
> pwe3@ietf.org
> https://www.ietf.org/mailman/listinfo/pwe3
>
_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls


From mpls-bounces@ietf.org  Fri Oct 31 06:07:09 2008
Return-Path: <mpls-bounces@ietf.org>
X-Original-To: mpls-archive@megatron.ietf.org
Delivered-To: ietfarch-mpls-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 12D7228C402;
	Fri, 31 Oct 2008 06:07:09 -0700 (PDT)
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id CE70D28C1A8;
	Fri, 31 Oct 2008 06:07:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.598
X-Spam-Level: 
X-Spam-Status: No, score=-6.598 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id RoqmU1PbuD77; Fri, 31 Oct 2008 06:07:05 -0700 (PDT)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140])
	by core3.amsl.com (Postfix) with ESMTP id 0771E28C20F;
	Fri, 31 Oct 2008 06:06:57 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,522,1220227200"; d="scan'208,217";a="24311018"
Received: from ams-dkim-2.cisco.com ([144.254.224.139])
	by ams-iport-1.cisco.com with ESMTP; 31 Oct 2008 13:06:50 +0000
Received: from ams-core-1.cisco.com (ams-core-1.cisco.com [144.254.224.150])
	by ams-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id m9VD6o0f031991; 
	Fri, 31 Oct 2008 14:06:50 +0100
Received: from xbh-ams-331.emea.cisco.com (xbh-ams-331.cisco.com
	[144.254.231.71])
	by ams-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m9VD6oki001706;
	Fri, 31 Oct 2008 13:06:50 GMT
Received: from xmb-ams-33a.cisco.com ([144.254.231.85]) by
	xbh-ams-331.emea.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 31 Oct 2008 14:06:50 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Fri, 31 Oct 2008 14:06:40 +0100
Message-ID: <CE2BF2A7B1008C459FD7978065C6ECE00763AA34@xmb-ams-33a.emea.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [mpls] [PWE3] draft-bocci-mpls-tp-gach-gal-00.txt for mpls wgdoc
Thread-Index: Ack7WS9EhpS4syAKQEaSSiFm9mSLLwAAFSU+
References: <4906E57E.4050105@pi.nu>
	<b2d141720810310602p2d9d321ela1077c5e3ea0f6b7@mail.gmail.com>
From: "Monique Morrow (mmorrow)" <mmorrow@cisco.com>
To: "Andrew G. Malis" <amalis@gmail.com>, "Loa Andersson" <loa@pi.nu>
X-OriginalArrivalTime: 31 Oct 2008 13:06:50.0169 (UTC)
	FILETIME=[897EDA90:01C93B59]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=4841; t=1225458410;
	x=1226322410; c=relaxed/simple; s=amsdkim2001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=mmorrow@cisco.com;
	z=From:=20=22Monique=20Morrow=20(mmorrow)=22=20<mmorrow@cisc
	o.com>
	|Subject:=20RE=3A=20[mpls]=20[PWE3]=20draft-bocci-mpls-tp-g
	ach-gal-00.txt=20for=20mpls=20wgdoc |Sender:=20;
	bh=QJ2uxLl5H1+VTYJheR1xc2PXUCi/Xy6zo5KBu9c8JdU=;
	b=jp1/c5oHZhp+GYShSpWEp6KZIMTzWNWNbepe6uMIHBg9mHZM0vsLgsGQJf
	B75q4txzhiXkQ6Hj93iOch73wwACF3tx/+bIkEpscs/+tDn5qH8XeLPPyVn+
	YAjYidbakH;
Authentication-Results: ams-dkim-2; header.From=mmorrow@cisco.com; dkim=pass (
	sig from cisco.com/amsdkim2001 verified; ); 
Cc: ccamp <ccamp@ops.ietf.org>, mpls@ietf.org, pwe3 <pwe3@ietf.org>,
	ahtmpls@itu.int
Subject: Re: [mpls] [PWE3] draft-bocci-mpls-tp-gach-gal-00.txt for mpls wgdoc
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0503798120=="
Sender: mpls-bounces@ietf.org
Errors-To: mpls-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0503798120==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C93B59.8955C5E2"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C93B59.8955C5E2
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Also support

Monique Jeanne Morrow
SP APAC CTO/Distinguished Consulting Engineer



-----Original Message-----
From: mpls-bounces@ietf.org on behalf of Andrew G. Malis
Sent: Fri 10/31/2008 6:02 AM
To: Loa Andersson
Cc: ccamp; mpls@ietf.org; pwe3; ahtmpls@itu.int
Subject: Re: [mpls] [PWE3] draft-bocci-mpls-tp-gach-gal-00.txt for mpls =
wgdoc
=20
Support.

On Tue, Oct 28, 2008 at 6:12 AM, Loa Andersson <loa@pi.nu> wrote:
> Working group(s),
>
> this is to initiate a two week poll to see if
> draft-bocci-mpls-tp-gach-gal-00.txt is in shape to
> become a mpls working group document.
>
> The current draft is a merge of to earlier draft
> one that defined the GAL and another that specified
> the generic associated channel.
>
> Please send your responses to the mpls working group
> mailing list (needs a bit of discipline, "replay all"
> won't do the trick ;) .
>
> Please respond on Tuesday Oct 11 the latest.
>
> /Loa
>
> --
> Loa Andersson
>
> Principal Networking Architect
> Acreo AB                           phone:  +46 8 632 77 14
> Isafjordsgatan 22                  mobile: +46 739 81 21 64
> Kista, Sweden                      email:  loa.andersson@acreo.se
>                                           loa@pi.nu
> _______________________________________________
> pwe3 mailing list
> pwe3@ietf.org
> https://www.ietf.org/mailman/listinfo/pwe3
>
_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls


------_=_NextPart_001_01C93B59.8955C5E2
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.5.7653.38">
<TITLE>RE: [mpls] [PWE3] draft-bocci-mpls-tp-gach-gal-00.txt for mpls =
wgdoc</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->

<P><FONT SIZE=3D2>Also support<BR>
<BR>
Monique Jeanne Morrow<BR>
SP APAC CTO/Distinguished Consulting Engineer<BR>
<BR>
<BR>
<BR>
-----Original Message-----<BR>
From: mpls-bounces@ietf.org on behalf of Andrew G. Malis<BR>
Sent: Fri 10/31/2008 6:02 AM<BR>
To: Loa Andersson<BR>
Cc: ccamp; mpls@ietf.org; pwe3; ahtmpls@itu.int<BR>
Subject: Re: [mpls] [PWE3] draft-bocci-mpls-tp-gach-gal-00.txt for mpls =
wgdoc<BR>
<BR>
Support.<BR>
<BR>
On Tue, Oct 28, 2008 at 6:12 AM, Loa Andersson &lt;loa@pi.nu&gt; =
wrote:<BR>
&gt; Working group(s),<BR>
&gt;<BR>
&gt; this is to initiate a two week poll to see if<BR>
&gt; draft-bocci-mpls-tp-gach-gal-00.txt is in shape to<BR>
&gt; become a mpls working group document.<BR>
&gt;<BR>
&gt; The current draft is a merge of to earlier draft<BR>
&gt; one that defined the GAL and another that specified<BR>
&gt; the generic associated channel.<BR>
&gt;<BR>
&gt; Please send your responses to the mpls working group<BR>
&gt; mailing list (needs a bit of discipline, &quot;replay all&quot;<BR>
&gt; won't do the trick ;) .<BR>
&gt;<BR>
&gt; Please respond on Tuesday Oct 11 the latest.<BR>
&gt;<BR>
&gt; /Loa<BR>
&gt;<BR>
&gt; --<BR>
&gt; Loa Andersson<BR>
&gt;<BR>
&gt; Principal Networking Architect<BR>
&gt; Acreo =
AB&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp; phone:&nbsp; +46 8 632 77 14<BR>
&gt; Isafjordsgatan =
22&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; mobile: +46 739 81 21 64<BR>
&gt; Kista, =
Sweden&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; email:&nbsp; =
loa.andersson@acreo.se<BR>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; loa@pi.nu<BR>
&gt; _______________________________________________<BR>
&gt; pwe3 mailing list<BR>
&gt; pwe3@ietf.org<BR>
&gt; <A =
HREF=3D"https://www.ietf.org/mailman/listinfo/pwe3">https://www.ietf.org/=
mailman/listinfo/pwe3</A><BR>
&gt;<BR>
_______________________________________________<BR>
mpls mailing list<BR>
mpls@ietf.org<BR>
<A =
HREF=3D"https://www.ietf.org/mailman/listinfo/mpls">https://www.ietf.org/=
mailman/listinfo/mpls</A><BR>
<BR>
</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C93B59.8955C5E2--

--===============0503798120==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls

--===============0503798120==--


