From pwe3-bounces@ietf.org  Fri Apr  1 11:35:18 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA12732
	for <pwe3-archive@ietf.org>; Fri, 1 Apr 2005 11:35:18 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DHPEX-00012P-4v
	for pwe3-archive@ietf.org; Fri, 01 Apr 2005 11:42:57 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DHOww-0001Ld-AV; Fri, 01 Apr 2005 11:24:46 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DHOwr-0001LD-Pu
	for pwe3@megatron.ietf.org; Fri, 01 Apr 2005 11:24:44 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA10452
	for <pwe3@ietf.org>; Fri, 1 Apr 2005 11:24:39 -0500 (EST)
Received: from rtp-iport-1.cisco.com ([64.102.122.148])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DHP4D-0000BE-1k
	for pwe3@ietf.org; Fri, 01 Apr 2005 11:32:18 -0500
Received: from rtp-core-2.cisco.com (64.102.124.13)
	by rtp-iport-1.cisco.com with ESMTP; 01 Apr 2005 11:44:57 -0500
X-IronPort-AV: i="3.91,141,1110171600"; 
	d="scan'208"; a="42820034:sNHT26010516"
Received: from cisco.com (erosen-u10.cisco.com [161.44.70.36])
	by rtp-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id j31GOSjI019353; 
	Fri, 1 Apr 2005 11:24:29 -0500 (EST)
Message-Id: <200504011624.j31GOSjI019353@rtp-core-2.cisco.com>
To: richard.spencer@bt.com
Subject: Re: [PWE3] RE: Proposed MS-PW "QoS" Requirements Clarifications 
In-reply-to: Your message of Thu, 31 Mar 2005 08:43:20 +0100.
	<B5E87B043D4C514389141E2661D255EC0A835969@i2km41-ukdy.domain1.systemhost.net>
User-Agent: EMH/1.14.1 SEMI/1.14.3 (Ushinoya) FLIM/1.14.3
	(=?ISO-8859-4?Q?Unebigory=F2mae?=) APEL/10.3 Emacs/21.3
	(sparc-sun-solaris2.8) MULE/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.3 - "Ushinoya")
Content-Type: text/plain; charset=US-ASCII
Date: Fri, 01 Apr 2005 11:24:28 -0500
From: Eric Rosen <erosen@cisco.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e1e48a527f609d1be2bc8d8a70eb76cb
Cc: dave.mcdysan@mci.com, pwe3@ietf.org
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: erosen@cisco.com
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=subscribe>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4adaf050708fb13be3316a9eee889caa


Richard> Dave,  Regarding your suggestion  to carry  parameters such  as the
Richard> average rate, burst duration and  peak rate, and your references to
Richard> RFC2697/RFC2698,  I  assume  that  this  is to  support  per  MS-PW
Richard> policing/queuing at S-PEs?  

I  thought it  was  more to  enable mapping  of  the PEs  to appropriate  TE
tunnels. 

Richard> One case where per MS-PW policing will be needed is at border S-PEs
Richard> where  a  provider  may   not  trust  another  provider  to  police
Richard> individual MS-PWs correctly

I'm  not sure  I understand  why  per-PW policing  is needed  at the  second
provider, as opposed to some sort  of aggregate policing.  Then if the first
provider  is not  policing  properly,  the enduser  service  might not  work
properly, but  presumably that's the fault  of the first  provider, and it's
the first provider who has direct contact with the enduser anyway. 

If you really want per-PW policing and shaping at each S-PE, then the proper
model may  be that  each segment looks  like an  access circuit to  the next
segment.  That might  turn out to be very different than  the model in which
the S-PE points are transparent to the data plane.

Richard> One case  where per MS-PW queues (and  associated traffic counters)
Richard> could  be  used  is at  border  S-PEs  to  obtain per  MS-PW  usage
Richard> information in order to support usage based inter-provider charging
Richard> models.

Support for this  charging model requires per PW  usage information, but not
per-PW queues. 

But  do you really  plan to  have per-pseudowire  usage-based inter-provider
billing? 

Richard> different providers  will offer different class  of service options
Richard> with varying traffic characteristics,  and therefore it may be very
Richard> difficult  or not  possible  to map  class  of service  definitions
Richard> between providers 

In which case there would not be much point in signaling QoS parameters. 

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


From pwe3-bounces@ietf.org  Fri Apr  1 15:54:26 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA14814
	for <pwe3-archive@ietf.org>; Fri, 1 Apr 2005 15:54:25 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DHTHK-000567-EY
	for pwe3-archive@ietf.org; Fri, 01 Apr 2005 16:02:06 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DHSjK-00031W-Nv; Fri, 01 Apr 2005 15:26:58 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DHSjG-00030p-Lz; Fri, 01 Apr 2005 15:26:54 -0500
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA06177;
	Fri, 1 Apr 2005 15:26:50 -0500 (EST)
Message-Id: <200504012026.PAA06177@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Date: Fri, 01 Apr 2005 15:26:50 -0500
Cc: pwe3@ietf.org
Subject: [PWE3] I-D ACTION:draft-ietf-pwe3-iana-allocation-09.txt
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=subscribe>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org
X-Spam-Score: 0.4 (/)
X-Scan-Signature: cf3becbbd6d1a45acbe2ffd4ab88bdc2

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Pseudo Wire Emulation Edge to Edge Working Group of the IETF.

	Title		: IANA Allocations for pseudo Wire Edge to Edge Emulation (PWE3)
	Author(s)	: L. Martini, M. Townsley
	Filename	: draft-ietf-pwe3-iana-allocation-09.txt
	Pages		: 7
	Date		: 2005-4-1
	
The Control and maintenance protocol for providing various Layer 1
and Layer 2 services over a Packet Switched Network has been
described in [2]. This document pre-allocates the fixed Pseudo-wire
identifier , and other fixed protocol values that are to be assigned
by IANA using the 'IETF Consensus' policy defined in RFC2434

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-pwe3-iana-allocation-09.txt

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request@ietf.org with the word unsubscribe in the body of the message.  
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.


Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-pwe3-iana-allocation-09.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-pwe3-iana-allocation-09.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
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: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body; access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID: <2005-4-1155124.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-pwe3-iana-allocation-09.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-pwe3-iana-allocation-09.txt";
	site="ftp.ietf.org"; access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2005-4-1155124.I-D@ietf.org>


--OtherAccess--

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

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

--NextPart--





From pwe3-bounces@ietf.org  Mon Apr  4 11:06:16 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA16303
	for <pwe3-archive@ietf.org>; Mon, 4 Apr 2005 11:06:16 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DITHb-0001L5-C5
	for pwe3-archive@ietf.org; Mon, 04 Apr 2005 11:14:32 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DIT4c-0003qk-1e; Mon, 04 Apr 2005 11:01:06 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DGtTn-0007DO-JW
	for pwe3@megatron.ietf.org; Thu, 31 Mar 2005 01:48:35 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA17600
	for <pwe3@ietf.org>; Thu, 31 Mar 2005 01:48:34 -0500 (EST)
Received: from rose.ctd.hcltech.com ([202.54.64.23])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DGtaq-0002wk-Vy
	for pwe3@ietf.org; Thu, 31 Mar 2005 01:55:54 -0500
X-MessageTextProcessor: DisclaimIt (2.50.252) [HCL Technologies Limited]
Content-Class: urn:content-classes:message
Received: from Ganesh.ctd.hcltech.com ([202.54.64.2]) by rose.ctd.hcltech.com
	with Microsoft SMTPSVC(5.0.2195.6713);
	Thu, 31 Mar 2005 12:17:56 +0530
Received: by Ganesh.ctd.hcltech.com with Internet Mail Service (5.5.2653.19)
	id <HP3D6J7P>; Thu, 31 Mar 2005 12:17:56 +0530
Message-ID: <68C9DA8F50019B4E8622C53811BEE1D60299A711@kavithai.ctd.hcltech.com>
From: "Vijayanand C - CTD, Chennai." <vijayc@hcltech.com>
To: <prabakarts@future.futsoft.com>, <pwe3@ietf.org>
Content-Transfer-Encoding: quoted-printable
Subject: RE: [PWE3] FW: I-D ACTION:draft-praba-l2vpn-vpls-mcast-emul-01.txt
Date: Thu, 31 Mar 2005 12:17:45 +0530
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-OriginalArrivalTime: 31 Mar 2005 06:47:56.0731 (UTC)
	FILETIME=[922B00B0:01C535BD]
X-Spam-Score: 0.3 (/)
X-Scan-Signature: 03169bfe4792634a390035a01a6c6d2f
Content-Transfer-Encoding: quoted-printable
X-Mailman-Approved-At: Mon, 04 Apr 2005 11:01:03 -0400
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=subscribe>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org
X-Spam-Score: 0.3 (/)
X-Scan-Signature: 3fbd9b434023f8abfcb1532abaec7a21
Content-Transfer-Encoding: quoted-printable

I have a few questions on this draft.

You seem to be sending multicast unregister information through a status =
TLV
in the notification message. if the peer PE does nt support this feature
this might be silently ignored and unwanted multicast traffic may still =
be
sent to the peer whos not interested in it. Is there any provision for a =
PE
to notify this and/or withdraw labels it has sent or any other measure =
to
stop receiving such unwanted traffic.=20

It is not clear how multiple instances handled in the signalling.


Vijay
> -----Original Message-----
> From: Prabakaran T Sampath [mailto:prabakarts@future.futsoft.com]
> Sent: Thursday, March 31, 2005 12:08 PM
> To: pwe3@ietf.org
> Subject: [PWE3] FW: I-D=20
> ACTION:draft-praba-l2vpn-vpls-mcast-emul-01.txt
>=20
>=20
> Dear PWE3-WG,
>=20
> This is Prabakaran T.S. and Musthafa A.S. from FutureSoft, a=20
> Flextronics
> company.
> We have come up with some concept and contributed it as a IETF
> draft in VPLS. Kindly go through this review comments updated draft
> and give us your valuable comments and feedback either in
> IETF VPLS/PWE3 working group or directly to us by email.
>=20
> Thanks in advance,
>=20
> Best regards,
> Prabakaran T.S.
> Musthafa A.S.
> FutureSoft, a Flextronics company,
> 480-481 Anna salai,
> Nandanam,
> Chennai-600035. INDIA.
> Ph: +91-44-24330550, extn: 459
>=20
> -----Original Message-----
> From: i-d-announce-bounces@ietf.org
> [mailto:i-d-announce-bounces@ietf.org]On Behalf Of
> Internet-Drafts@ietf.org
> Sent: Thursday, 31 March 2005 2:08 AM
> To: i-d-announce@ietf.org
> Subject: I-D ACTION:draft-praba-l2vpn-vpls-mcast-emul-01.txt
>=20
>=20
> A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
>=20
>=20
> 	Title		: Multicast Emulation over VPLS
> 	Author(s)	: Prabakaran. Ts, Musthafa. As
> 	Filename	: draft-praba-l2vpn-vpls-mcast-emul-01.txt
> 	Pages		: 14
> 	Date		: 2005-3-30
>=20
> In Virtual Private LAN Service (VPLS), the PE devices provide a
>    logical interconnect such that CE devices belonging to a specific
>    VPLS instance appear to be connected by a single LAN.  A VPLS
>    solution performs replication for multicast traffic at the ingress
>    PE devices.  When replicated at the ingress PE, multicast traffic
>    wastes bandwidth when 1. Multicast traffic is sent to sites with no
>    members, and 2. Pseudo wires to different sites go through a shared
>    path. This document addresses the above cases by using LDP
>    signaling to emulate Multicast operation over VPLS with out using
>    IGMP and PIM snooping as described in [VPLS-MCAST].
>=20
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-praba-l2vpn-vpls-mca
> st-emul-01.txt
>=20
> To remove yourself from the I-D Announcement list, send a message to
> i-d-announce-request@ietf.org with the word unsubscribe in=20
> the body of the
> message.
> You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce
> to change your subscription settings.
>=20
>=20
> Internet-Drafts are also available by anonymous FTP. Login=20
> with the username
> "anonymous" and a password of your e-mail address. After logging in,
> type "cd internet-drafts" and then
> 	"get draft-praba-l2vpn-vpls-mcast-emul-01.txt".
>=20
> A list of Internet-Drafts directories can be found in
> http://www.ietf.org/shadow.html
> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
>=20
>=20
> Internet-Drafts can also be obtained by e-mail.
>=20
> Send a message to:
> 	mailserv@ietf.org.
> In the body type:
> 	"FILE=20
> /internet-drafts/draft-praba-l2vpn-vpls-mcast-emul-01.txt".
>=20
> NOTE:	The mail server at ietf.org can return the document in
> 	MIME-encoded form by using the "mpack" utility.  To use this
> 	feature, insert the command "ENCODING mime" before the "FILE"
> 	command.  To decode the response(s), you will need "munpack" or
> 	a MIME-compliant mail reader.  Different MIME-compliant=20
> mail readers
> 	exhibit different behavior, especially when dealing with
> 	"multipart" MIME messages (i.e. documents which have been split
> 	up into multiple messages), so check your local documentation on
> 	how to manipulate these messages.
>=20
>=20
> Below is the data which will enable a MIME compliant mail reader
> implementation to automatically retrieve the ASCII version of the
> Internet-Draft.
>=20
>=20
> **************************************************************
> *************
> This message is proprietary to Future Software Limited (FSL)
> and is intended solely for the use of the individual to whom it
> is addressed. It may contain  privileged or confidential information
> and should not be circulated or used for any purpose other than for
> what it is intended.
>=20
> If you have received this message in error, please notify the
> originator immediately. If you are not the intended recipient,
> you are notified that you are strictly prohibited from using,
> copying, altering, or disclosing the contents of this message.
> FSL accepts no responsibility for loss or damage arising from
> the use of the information transmitted by this email including
> damage from virus.
> **************************************************************
> *************
>=20
>=20
DISCLAIMER=20
This message and any attachment(s) contained here are information that =
is confidential, proprietary to HCL Technologies=20
and its customers. Contents may be privileged or otherwise protected by =
law. The information is solely intended for the=20
individual or the entity it is addressed to. If you are not the intended =
recipient of this message, you are not authorized to=20
read, forward, print, retain, copy or disseminate this message or any =
part of it. If you have received this e-mail in error,=20
please notify the sender immediately by return e-mail and delete it from =
your computer


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


From pwe3-bounces@ietf.org  Mon Apr  4 11:44:32 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA19997
	for <pwe3-archive@ietf.org>; Mon, 4 Apr 2005 11:44:32 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DITsd-0003PV-V0
	for pwe3-archive@ietf.org; Mon, 04 Apr 2005 11:52:48 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DIThW-0007m1-Kj; Mon, 04 Apr 2005 11:41:18 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DIThT-0007lw-L0
	for pwe3@megatron.ietf.org; Mon, 04 Apr 2005 11:41:17 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA19623
	for <pwe3@ietf.org>; Mon, 4 Apr 2005 11:41:13 -0400 (EDT)
From: richard.spencer@bt.com
Received: from smtp3.smtp.bt.com ([217.32.164.138])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DITpR-0003LF-2D
	for pwe3@ietf.org; Mon, 04 Apr 2005 11:49:29 -0400
Received: from i2km98-ukbr.domain1.systemhost.net ([193.113.197.85]) by
	smtp3.smtp.bt.com with Microsoft SMTPSVC(6.0.3790.80); 
	Mon, 4 Apr 2005 16:41:05 +0100
Received: from i2km41-ukdy.domain1.systemhost.net ([193.113.30.29]) by
	i2km98-ukbr.domain1.systemhost.net with Microsoft
	SMTPSVC(5.0.2195.6713); Mon, 4 Apr 2005 16:41:04 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [PWE3] RE: Proposed MS-PW "QoS" Requirements Clarifications 
Date: Mon, 4 Apr 2005 16:40:38 +0100
Message-ID: <B5E87B043D4C514389141E2661D255EC074C4D6E@i2km41-ukdy.domain1.systemhost.net>
Thread-Topic: [PWE3] RE: Proposed MS-PW "QoS" Requirements Clarifications 
Thread-Index: AcU210lmYgAncZw7TbGcJCwVDWOygwAfcM6g
To: <erosen@cisco.com>
X-OriginalArrivalTime: 04 Apr 2005 15:41:04.0847 (UTC)
	FILETIME=[B63925F0:01C5392C]
X-Spam-Score: 0.3 (/)
X-Scan-Signature: 2beba50d0fcdeee5f091c59f204d4365
Content-Transfer-Encoding: quoted-printable
Cc: dave.mcdysan@mci.com, pwe3@ietf.org
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=subscribe>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org
X-Spam-Score: 0.3 (/)
X-Scan-Signature: dbb8771284c7a36189745aa720dc20ab
Content-Transfer-Encoding: quoted-printable

Eric,

> Richard> Dave, Regarding your suggestion to carry parameters such as =
the
> Richard> average rate, burst duration and peak rate, and your =
references to
> Richard> RFC2697/RFC2698, I assume that this is to support per MS-PW
> Richard> policing/queuing at S-PEs? =20
>=20
> I thought it was more to enable mapping of the PEs to appropriate  TE
> tunnels.=20

How? To map MS-PWs to TE tunnels requires the traffic parameters carried =
in the signalling protocol to match TE tunnel properties/characteristics =
(e.g. an EXP value mapping to a DS-TE tunnel). Lets take burst duration =
for example, if a S-PE gets a MS-PW setup request with a requirement for =
a 2sec burst, how does this help the S-PE select an appropriate TE =
tunnel? Also, RFC2697/RFC2698 describe single/two rate three colour =
marking, what do these have to do with TE tunnel mapping?=20

> Richard> One case where per MS-PW policing will be needed is at border =
S-PEs
> Richard> where a provider may not trust another provider to police
> Richard> individual MS-PWs correctly
>=20
> I'm  not sure  I understand  why  per-PW policing  is needed =20
> at the  second provider, as opposed to some sort  of aggregate =
policing.

Aggregate policing allows the provider to ensure that there is enough =
bandwidth in the network to meet the requirements of the aggregate, but =
does not provide fairness between MS-PWs within the aggregate. For =
example, you could use aggregate policing to ensure that a S-PE never =
accepts more than 10Mbit/s of Class 1 traffic from another provider. =
However, if the other provider hasn't policed the individual MS-PWs, =
then some of the MS-PW packets may be in-contract and some may be =
out-of-contract. As there is no way to distinguish between in-contract =
and out-of-contract packets within a class, when the amount of class 1 =
traffic received exceeds 10Mbit/s some in-contract packets will be =
dropped and some out-of-contract packets will get through. So, a =
customer that buys 500Kbit/s of class 1 traffic and is only transmitting =
400kbit/s, may have packets dropped because another customer who has =
also purchased 500Kbit/s of class 1 traffic is actually sending 1Mbit/s.

Also, aggregate policing only works if there is a hard limit on traffic =
class bandwidth. If the QoS model supports re-use of unused bandwidth =
between classes, i.e. classes can burst if bandwidth is available, then =
this approach won't work.

> Then if the first provider is not policing properly, the enduser =
service =20
> might not work properly, but presumably that's the fault of the first  =

> provider, and it's the first provider who has direct contact with the =
enduser anyway.

No, in an inter-provider case where one user of the service (e.g. user =
A) is in one providers network (e.g. SP1) and the other user (e.g. user =
B) is in another providers network (e.g. SP2), then both users are =
likely to be affected as communication is generally two-way. Even if the =
communication is more one way (e.g. a UDP file transfer request) and if =
SP2 is not policing at the edge, then it will actually be user A in SP1s =
network that will be affected.

Dropping in-contract packets because the other provider is sending too =
many out-of-contract packets (due to not policing correctly) is a =
difficult subject when it comes to blame and responsibility. I don't =
think the response "Well SP2 is sending me more traffic than it should =
be for customer X and Y, so that's why I'm dropping half of your packets =
I'm afraid customer Z" would go down too well. The customer has a =
contract with the providers and doesn't care what agreements the =
providers have with each other.

It appears to me there are only two alternatives:

1. You use aggregate (e.g. class based) policing with hard bandwidth =
limits on each class at border S-PEs, and you sign an agreement with the =
other provider that says if the traffic it sends exceeds agreed class =
limits (forcing you to potentially drop in-contract traffic within a =
class) then they will take full responsibility and compensate the =
customer accordingly.=20

2. You perform per MS-PW policing.

If there are other alternatives I'd be interested in hearing about them?

> If you really want per-PW policing and shaping at each S-PE, then the =
proper
> model may be that each segment looks like an access circuit to  the =
next
> segment. That might turn out to be very different than the model in =
which
> the S-PE points are transparent to the data plane.

I'm not sure exactly what you mean here, the S-PE points are transparent =
to which data plane? - The tunnel LSP, the MS-PW, or the client (e.g. =
AT,, Ethernet, TDM, etc.) data plane? If you are referring to the =
client, then this should always be transparent to S-PEs.=20

> Richard> One case  where per MS-PW queues (and  associated traffic =
counters)
> Richard> could  be  used  is at  border  S-PEs  to  obtain per  MS-PW  =
usage
> Richard> information in order to support usage based inter-provider =
charging
> Richard> models.
>=20
> Support for this charging model requires per PW usage information, but =
not
> per-PW queues.=20

Agreed, although I didn't say anything to the contrary. I said that =
MS-PW queues could be used to support usage based billing, I didn't say =
that there weren't any other methods.

> But do you really plan to have per-pseudowire usage-based=20
> inter-provider billing?

The commercial and regulatory requirements for inter-provider MPLS/PWs =
have not been defined yet, and therefore I would not like to speculate =
on what inter-provider billing requirements will be. I would say though =
that usage based billing as opposed to flat rate billing for packet =
based services appears to be gaining significant interest. For example, =
Korea Telecom plans to introduce usage based billing for Internet access =
around 2007 in order to address peer-to-peer traffic concerns and to =
introduce fairness, i.e. those customers that use the network the most =
will pay the most.
=20
Regards,
Richard

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


From pwe3-bounces@ietf.org  Mon Apr  4 13:14:43 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA00243
	for <pwe3-archive@ietf.org>; Mon, 4 Apr 2005 13:14:42 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DIVHw-00005R-CR
	for pwe3-archive@ietf.org; Mon, 04 Apr 2005 13:23:00 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DIV8M-0001r6-IB; Mon, 04 Apr 2005 13:13:06 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DIV8K-0001px-VX
	for pwe3@megatron.ietf.org; Mon, 04 Apr 2005 13:13:05 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA29885
	for <pwe3@ietf.org>; Mon, 4 Apr 2005 13:13:01 -0400 (EDT)
Received: from mail.hammerheadsystems.com ([65.113.43.2])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DIVGE-0008PT-SX
	for pwe3@ietf.org; Mon, 04 Apr 2005 13:21:19 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Mon, 4 Apr 2005 10:12:42 -0700
Message-ID: <2DAC9E7A4640234B85975565E5D83AE110D44F@srvcaexg01.headquarters.hammerheadsystems.com>
Thread-Topic: How to choose Interface MTU for PW heterogeneous transport 
Thread-Index: AcU5OYL0KIf1w76+TAmneuqGGYw27Q==
From: "Yijun Xiong" <yxiong@hammerheadsystems.com>
To: <pwe3@ietf.org>
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 057ebe9b96adec30a7efb2aeda4c26a4
Subject: [PWE3] How to choose Interface MTU for PW heterogeneous transport 
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0719961694=="
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org
X-Spam-Score: 0.5 (/)
X-Scan-Signature: b22590c27682ace61775ee7b453b40d3

This is a multi-part message in MIME format.

--===============0719961694==
content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C53939.8347AFD4"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C53939.8347AFD4
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi,
=20
In draft-ietf-pwe3-control-protocol-16.txt "Pseudowire Setup and
Maintenance using LDP", Interface MTU parameter is used when setting up
PWs. It is stated that if this parameter does not match in both
directions of a specific PW, that PW MUST NOT be enabled.
=20
I have the following questions while implementing the heterogeneous
transport, e.g., when one AC (between CE1 and PE1) is ATM, another AC
(between PE2 and CE2) is FR.
=20
(1) Suppose PW1 is for ATM to FR direction, PW2 for FR to ATM direction,
how to select PW type, ATM PW or FR PW for PW1 and PW2? Can PW1 be ATM
type and PW2 be FR type?
=20
(2) For FR AC, I would assume that one can use FR UNI MTU as interface
MTU for PW, How to choose interface MTU for ATM AC, as ATM UNI has no
such parameter like MTU?
=20
=20
Thanks.
=20
Yijun Xiong=20
Hammerhead Systems Inc.

------_=_NextPart_001_01C53939.8347AFD4
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD><TITLE>Message</TITLE>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2800.1479" name=3DGENERATOR></HEAD>
<BODY>
<DIV><FONT face=3DArial><SPAN class=3D127020617-04042005>
<DIV><FONT face=3DCourier size=3D2><SPAN=20
class=3D348252119-01042005>Hi,</SPAN></FONT></DIV>
<DIV><FONT face=3DCourier size=3D2><SPAN=20
class=3D348252119-01042005></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DCourier size=3D2><SPAN class=3D348252119-01042005>In=20
draft-ietf-pwe3-control-protocol-16.txt "Pseudowire Setup and =
Maintenance using=20
LDP", Interface MTU parameter is used when setting up PWs. It is stated =
that if=20
this parameter does not match in both directions of a specific PW, that =
PW MUST=20
NOT be enabled.</SPAN></FONT></DIV>
<DIV><FONT face=3DCourier size=3D2><SPAN=20
class=3D348252119-01042005></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DCourier size=3D2><SPAN =
class=3D348252119-01042005>I&nbsp;have the=20
following&nbsp;questions while implementing the heterogeneous transport, =
e.g.,=20
when&nbsp;one AC&nbsp;<SPAN class=3D127020617-04042005>(between CE1 and =
PE1)=20
</SPAN>is ATM, another AC&nbsp;<SPAN class=3D127020617-04042005>(between =
PE2 and=20
CE2) </SPAN>is FR.</SPAN></FONT></DIV>
<DIV><FONT face=3DCourier size=3D2><SPAN=20
class=3D348252119-01042005></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DCourier size=3D2><SPAN =
class=3D348252119-01042005>(1)&nbsp;<SPAN=20
class=3D127020617-04042005>Suppose PW1 is for ATM to FR direction, PW2 =
for FR to=20
ATM direction, h</SPAN>ow to select PW type, ATM&nbsp;PW&nbsp;or FR PW =
for PW1=20
and PW2? Can PW1 be ATM type and PW2 be FR type?</SPAN></FONT></DIV>
<DIV><FONT face=3DCourier size=3D2><SPAN=20
class=3D348252119-01042005></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DCourier size=3D2><SPAN class=3D348252119-01042005>(2) =
For FR AC, I=20
would assume that one can use FR UNI MTU as interface MTU for PW, How to =
choose=20
interface MTU for ATM AC, as ATM UNI has no such parameter like=20
MTU?</SPAN></FONT></DIV>
<DIV><FONT face=3DCourier size=3D2><SPAN=20
class=3D348252119-01042005></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DCourier size=3D2><SPAN=20
class=3D348252119-01042005></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DCourier size=3D2><SPAN class=3D348252119-01042005>
<DIV><FONT face=3DArial><SPAN class=3D348252119-01042005><FONT =
face=3DCourier=20
size=3D2>Thanks.</FONT></SPAN></FONT></DIV>
<DIV><FONT face=3DArial><SPAN class=3D348252119-01042005><FONT =
face=3DCourier=20
size=3D2></FONT></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT size=3D+0><SPAN class=3D348252119-01042005><FONT =
face=3DCourier=20
size=3D2>Yijun Xiong </FONT></SPAN></FONT></DIV>
<DIV><FONT size=3D+0><SPAN class=3D348252119-01042005><FONT =
size=3D2><FONT=20
face=3DCourier>Hammerhead Systems=20
Inc.</FONT></DIV></FONT></SPAN></FONT></SPAN></FONT></DIV></SPAN></FONT><=
/DIV></BODY></HTML>
=00
------_=_NextPart_001_01C53939.8347AFD4--


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

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

--===============0719961694==--



From pwe3-bounces@ietf.org  Thu Apr  7 11:07:13 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA02374
	for <pwe3-archive@ietf.org>; Thu, 7 Apr 2005 11:07:13 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DJYjn-0006KP-Vc
	for pwe3-archive@ietf.org; Thu, 07 Apr 2005 11:16:08 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DJYFB-00060S-SG; Thu, 07 Apr 2005 10:44:29 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DJYFA-00060J-6d
	for pwe3@megatron.ietf.org; Thu, 07 Apr 2005 10:44:28 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA29711
	for <pwe3@ietf.org>; Thu, 7 Apr 2005 10:44:25 -0400 (EDT)
Received: from rtp-iport-1.cisco.com ([64.102.122.148])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DJYNi-0005Fk-PM
	for pwe3@ietf.org; Thu, 07 Apr 2005 10:53:20 -0400
Received: from rtp-core-2.cisco.com (64.102.124.13)
	by rtp-iport-1.cisco.com with ESMTP; 07 Apr 2005 11:05:43 -0400
X-IronPort-AV: i="3.92,84,1112587200"; 
	d="scan'208"; a="43531511:sNHT629035346"
Received: from cisco.com (erosen-u10.cisco.com [161.44.70.36])
	by rtp-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id j37EiBjI016222; 
	Thu, 7 Apr 2005 10:44:11 -0400 (EDT)
Message-Id: <200504071444.j37EiBjI016222@rtp-core-2.cisco.com>
To: richard.spencer@bt.com
Subject: Re: [PWE3] RE: Proposed MS-PW "QoS" Requirements Clarifications 
In-reply-to: Your message of Mon, 04 Apr 2005 16:40:38 +0100.
	<B5E87B043D4C514389141E2661D255EC074C4D6E@i2km41-ukdy.domain1.systemhost.net>
User-Agent: EMH/1.14.1 SEMI/1.14.3 (Ushinoya) FLIM/1.14.3
	(=?ISO-8859-4?Q?Unebigory=F2mae?=) APEL/10.3 Emacs/21.3
	(sparc-sun-solaris2.8) MULE/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.3 - "Ushinoya")
Content-Type: text/plain; charset=US-ASCII
Date: Thu, 07 Apr 2005 10:44:11 -0400
From: Eric Rosen <erosen@cisco.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f607d15ccc2bc4eaf3ade8ffa8af02a0
Cc: dave.mcdysan@mci.com, pwe3@ietf.org
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: erosen@cisco.com
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=subscribe>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 52f7a77164458f8c7b36b66787c853da


> To map MS-PWs to TE tunnels requires the traffic parameters carried in the
> signalling protocol to match TE tunnel properties/characteristics (e.g. an
> EXP value mapping to a DS-TE tunnel).  

Yes, I thought that that was the requirement being posed by at least some of
the folks who want QoS signaling for PWs. 

> if a S-PE gets a MS-PW setup  request with a requirement for a 2sec burst,
> how does this help the S-PE select an appropriate TE tunnel 

If it doesn't, maybe there's no need to signal it. 

> As there is no way  to distinguish between in-contract and out-of-contract
> packets within a class 

So, the requirement you are posing here is the need for a method by which an
S-PE  can  distinguish   in-contract  from  out-of-contract  packets.   This
requirement is there to handle the following case: 

- SP  A accepts  more traffic  from  its endusers  than it  is obligated  to
  accept,

- SP A sends SP B more traffic than SP B is obligated to accept from SP A. 

One might  think that SP A  is at fault here,  but perhaps SP B  wants to do
what it  can to compensate for  SP A's shoddy practices.   However, since in
general SP B cannot  compensate for shoddy practices on the part  of SP A, I
don't understand why this particular case is worth a large investment on the
part of SP B.

In any  event, if  there is a  valid requirement to  distinguish in-contract
from out-of-contract  packets at the switching point,  having each switching
point try to perform that  classification itself is not necessarily the best
solution.

>> If you really want per-PW policing and shaping at each S-PE, then the proper
>> model may be that each segment looks like an access circuit to  the next
>> segment. That might turn out to be very different than the model in which
>> the S-PE points are transparent to the data plane. 

> I'm not sure  exactly what you mean here, the  S-PE points are transparent
> to which data plane? - The tunnel LSP, the MS-PW, or the client (e.g. AT,,
> Ethernet, TDM, etc.) data plane? 

I meant  to the  MPLS data plane.   I think  it should be  a goal  that data
packet  switching  at  the  S-PEs  be  done  by  "ordinary"  MPLS  switching
procedures, which  have no knowledge that  they are functioning  in an S-PE.
I'm sure this goal will need to be compromised to some degree, as it may be
necessary to process  in-band control channel info, if there  is any.  But I
think the solution becomes much more  expensive if the S-PE has to the exact
same per-PW processing that is done at the PW ingress and PW egress. 









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


From pwe3-bounces@ietf.org  Sun Apr 10 04:28:18 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA02293
	for <pwe3-archive@ietf.org>; Sun, 10 Apr 2005 04:28:18 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DKXwv-0005yI-T9
	for pwe3-archive@ietf.org; Sun, 10 Apr 2005 04:37:47 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DKXkJ-0006md-L3; Sun, 10 Apr 2005 04:24:43 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DKXkE-0006mY-CE
	for pwe3@megatron.ietf.org; Sun, 10 Apr 2005 04:24:41 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA02147
	for <pwe3@ietf.org>; Sun, 10 Apr 2005 04:24:36 -0400 (EDT)
Received: from ams-iport-1.cisco.com ([144.254.224.140])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DKXtJ-0005oz-PQ
	for pwe3@ietf.org; Sun, 10 Apr 2005 04:34:05 -0400
Received: from ams-core-1.cisco.com (144.254.224.150)
	by ams-iport-1.cisco.com with ESMTP; 10 Apr 2005 10:24:25 +0200
Received: from cisco.com (mrwint.cisco.com [64.103.71.48])
	by ams-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id j3A8OLt5003501; 
	Sun, 10 Apr 2005 10:24:22 +0200 (MEST)
Received: from cisco.com (ams-clip-vpn-dhcp272.cisco.com [10.61.65.16])
	by cisco.com (8.8.8-Cisco List Logging/8.8.8) with ESMTP id JAA13056;
	Sun, 10 Apr 2005 09:24:20 +0100 (BST)
Message-ID: <4258E2B3.8030601@cisco.com>
Date: Sun, 10 Apr 2005 09:24:19 +0100
From: Stewart Bryant <stbryant@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: pwe3 <pwe3@ietf.org>
References: <4243E121.8070207@cisco.com>
In-Reply-To: <4243E121.8070207@cisco.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32
Content-Transfer-Encoding: 7bit
Cc: George Swallow <swallow@cisco.com>,
        "W. Mark Townsley" <townsley@cisco.com>,
        Danny McPherson <danny@arbor.net>
Subject: [PWE3] Re: draft-ietf-pwe3-cw-03.txt
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=subscribe>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ea4ac80f790299f943f0a53be7e1a21a
Content-Transfer-Encoding: 7bit

There have been no comments on <draft-ietf-pwe3-cw-03.txt>

I am therefore going to ask Mark to progress this through the
IESG.

Regards

Stewart

Stewart Bryant wrote:
> 
> draft-ietf-pwe3-cw-03.txt has been updated to include the
> text discussed at IETF62 and is now available at:
> 
> http://www.ietf.org/internet-drafts/draft-ietf-pwe3-cw-03.txt
> 
> This is the last call for comments before we send it back
> to the IESG.
> 
> This last call will end 8th April 2005.
> 
> Stewart
> 
> 
> 

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


From pwe3-bounces@ietf.org  Mon Apr 11 16:15:01 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA18162
	for <pwe3-archive@ietf.org>; Mon, 11 Apr 2005 16:15:01 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DL5Sj-0004HG-S4
	for pwe3-archive@ietf.org; Mon, 11 Apr 2005 16:24:50 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DL4pi-0008OH-Qa; Mon, 11 Apr 2005 15:44:30 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DL4pf-0008Np-8n; Mon, 11 Apr 2005 15:44:27 -0400
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA13649;
	Mon, 11 Apr 2005 15:44:24 -0400 (EDT)
Message-Id: <200504111944.PAA13649@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Date: Mon, 11 Apr 2005 15:44:24 -0400
Cc: pwe3@ietf.org
Subject: [PWE3] I-D ACTION:draft-ietf-pwe3-tdm-requirements-08.txt
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=subscribe>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org
X-Spam-Score: 0.4 (/)
X-Scan-Signature: a8a20a483a84f747e56475e290ee868e

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Pseudo Wire Emulation Edge to Edge Working Group of the IETF.

	Title		: Requirements for Edge-to-Edge Emulation of TDM 
			  Circuits over Packet Switching Networks
	Author(s)	: M. Riegel
	Filename	: draft-ietf-pwe3-tdm-requirements-08.txt
	Pages		: 25
	Date		: 2005-4-11
	
This document defines the specific requirements for edge-to-edge
   emulation of circuits carrying Time Division Multiplexed (TDM)
   digital signals of the Plesiochronous Digital Hierarchy as well as
   the Synchronous Optical NETwork/Synchronous Digital Hierarchy over
   packet-switched networks.  It is aligned to the common architecture
   for Pseudo Wire Emulation Edge-to-Edge (PWE3).
   It makes references to the generic requirements for PWE3 where
   applicable and complements them by defining requirements originating
   from specifics of TDM circuits.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-pwe3-tdm-requirements-08.txt

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request@ietf.org with the word unsubscribe in the body of the message.  
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.


Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-pwe3-tdm-requirements-08.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-pwe3-tdm-requirements-08.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
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: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body; access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID: <2005-4-11161427.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-pwe3-tdm-requirements-08.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-pwe3-tdm-requirements-08.txt";
	site="ftp.ietf.org"; access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2005-4-11161427.I-D@ietf.org>


--OtherAccess--

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

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

--NextPart--





From pwe3-bounces@ietf.org  Mon Apr 11 16:59:52 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA27246
	for <pwe3-archive@ietf.org>; Mon, 11 Apr 2005 16:59:52 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DL6A9-0007KB-KH
	for pwe3-archive@ietf.org; Mon, 11 Apr 2005 17:09:41 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DL4pH-0008NC-8P; Mon, 11 Apr 2005 15:44:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DL4pD-0008MU-DX; Mon, 11 Apr 2005 15:43:59 -0400
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA13590;
	Mon, 11 Apr 2005 15:43:57 -0400 (EDT)
Message-Id: <200504111943.PAA13590@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Date: Mon, 11 Apr 2005 15:43:56 -0400
Cc: pwe3@ietf.org
Subject: [PWE3] I-D ACTION:draft-ietf-pwe3-satop-mib-03.txt
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=subscribe>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org
X-Spam-Score: 0.4 (/)
X-Scan-Signature: 8de5f93cb2b4e3bee75302e9eacc33db

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Pseudo Wire Emulation Edge to Edge Working Group of the IETF.

	Title		: Managed Objects for Structure-Agnostic TDM over Packet Network
	Author(s)	: O. Nicklass
	Filename	: draft-ietf-pwe3-satop-mib-03.txt
	Pages		: 20
	Date		: 2005-4-11
	
This memo defines a portion of the Management Information Base (MIB)
   for use with network management protocols in the Internet community.
   In particular, it describes managed objects for pseudo wire
   encapsulation for TDM (T1, E1, T3, E3) bit-streams circuits over a
   Packet Switch Network (PSN).

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-pwe3-satop-mib-03.txt

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request@ietf.org with the word unsubscribe in the body of the message.  
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.


Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-pwe3-satop-mib-03.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-pwe3-satop-mib-03.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
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: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body; access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID: <2005-4-11161419.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-pwe3-satop-mib-03.txt

--OtherAccess
Content-Type: Message/External-body; name="draft-ietf-pwe3-satop-mib-03.txt";
	site="ftp.ietf.org"; access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2005-4-11161419.I-D@ietf.org>


--OtherAccess--

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

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

--NextPart--





From pwe3-bounces@ietf.org  Mon Apr 11 17:11:48 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA00699
	for <pwe3-archive@ietf.org>; Mon, 11 Apr 2005 17:11:48 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DL6Lg-00006s-Ef
	for pwe3-archive@ietf.org; Mon, 11 Apr 2005 17:21:37 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DL64a-0000Su-3D; Mon, 11 Apr 2005 17:03:56 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DL64Y-0000Rk-CI
	for pwe3@megatron.ietf.org; Mon, 11 Apr 2005 17:03:54 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA28321
	for <pwe3@ietf.org>; Mon, 11 Apr 2005 17:03:43 -0400 (EDT)
Received: from rtp-iport-1.cisco.com ([64.102.122.148])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DL6Dr-0007gs-N1
	for pwe3@ietf.org; Mon, 11 Apr 2005 17:13:32 -0400
Received: from rtp-core-2.cisco.com (64.102.124.13)
	by rtp-iport-1.cisco.com with ESMTP; 11 Apr 2005 17:25:51 -0400
X-IronPort-AV: i="3.92,94,1112587200"; d="scan'208"; a="44074430:sNHT34266284"
Received: from fruitpie.cisco.com (IDENT:mirapoint@fruitpie.cisco.com
	[64.102.16.27])
	by rtp-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id j3BL3SeX012066; 
	Mon, 11 Apr 2005 17:03:33 -0400 (EDT)
Received: from [10.83.1.101] (rtp-townsley-vpn4.cisco.com [10.83.1.101])
	by fruitpie.cisco.com (MOS 3.4.6-GR) with SMTP id BGQ89145;
	Mon, 11 Apr 2005 14:03:24 -0700 (PDT)
Message-ID: <425AE61B.2030909@cisco.com>
Date: Mon, 11 Apr 2005 17:03:23 -0400
From: "W. Mark Townsley" <townsley@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
	rv:1.7) Gecko/20040616
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Stewart Bryant <stbryant@cisco.com>, Danny McPherson <danny@tcb.net>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9aa22b77adc37e7d33e29644e4dc0b33
Content-Transfer-Encoding: 7bit
Cc: "PWE3 WG \(E-mail\)" <pwe3@ietf.org>
Subject: [PWE3] AD Review of draft-ietf-pwe3-cw-03.txt 
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=subscribe>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2c6813ed945e40b4b5bea39da243c669
Content-Transfer-Encoding: 7bit


Please find comments inline.

Thanks,

- Mark

>                                                                         
> Network Working Group                                         S. Bryant 
> Internet Draft                                               G. Swallow 
> Expiration Date: September 2005                           Cisco Systems 
>                                                            D. McPherson 
>                                                          Arbor Networks 
>                                                                         
>                                                              March 2005 
>                                                                         
>                                                                         
>                 PWE3 Control Word for use over an MPLS PSN 
> 
>                         draft-ietf-pwe3-cw-03.txt 
> 
>   
>   
>     
> Status of this Memo  
> 
>    By submitting this Internet-Draft, we certify that any applicable 
>    patent or other IPR claims of which we are aware have been 
>    disclosed, or will be disclosed, and any of which we become aware 
>    will be disclosed, in accordance with RFC 3668. 
> 
>    Internet-Drafts are working documents of the Internet Engineering 
>    Task Force (IETF), its areas, and its working groups.  Note that 
>    other groups may also distribute working documents as        
>    Internet-Drafts. 
> 
>    Internet-Drafts are draft documents valid for a maximum of six 
>    months and may be updated, replaced, or obsoleted by other documents 
>    at any time.  It is inappropriate to use Internet-Drafts as 
>    reference material or to cite them other than as "work in progress". 
> 
>    The list of current Internet-Drafts can be accessed at 
>    http://www.ietf.org/1id-abstracts.html  
> 
>    The list of Internet-Draft Shadow Directories can be accessed at 
>    http://www.ietf.org/shadow.html 
> 
> Abstract  
>  
>    This document describes the preferred designs of the PWE3 MPLS 
>    Control Word, and the PW Associated Channel Header. The design of 
>    these fields is chosen so that an MPLS LSR performing MPLS payload 
>    inspection will not confuse a PWE3 payload with an IP payload. 
> 
> Conventions used in this document  
>      
> 
> 
> 
> 
>  
> Bryant et al            Expires September 2005               [Page 1] 
> 
> 
> 
> 
> INTERNET DRAFT   PWE3 Control Word for use over an MPLS PSN   Mar 2005 
> 
>    The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 
>    "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 
>    document are to be interpreted as described in RFC 2119 [RFC2119]. 
> 
>  
> 1.   Introduction 
> 
>    The standard MPLS encapsulations have no explicit protocol 
>    identifier. In order for a pseudo wire (PW) [RFC3985] to operate 
>    correctly over an MPLS packet switched network (PSN) that performs 
>    MPLS payload inspection, a PW packet must not appear to the LSR as 
>    if it were an IP packet [BCP]. An example of an LSR that performs 
>    MPLS payload inspection is one that is performing equal-cost 
>    multiple-path load-balancing (ECMP) [RFC2992]. If ECMP were 
>    performed on PWE3 packets, the packets in the PW may not all follow 
>    the same path through the PSN. This may result in misordered packet 
>    delivery to the egress PE. The inability to ensure that all packets 
>    belonging to a PW follow the same path may also prevent the PW OAM 
>    [VCCV] mechanism from correctly monitoring the PW.  
> 
>    This draft specifies how a PW header distinguishes a PW payload from 
>    an IP payload carried over an MPLS PSN. 
> 
> 2.   PWE3 Packet Identification 
> 
>    All IP packets [RFC791][RFC1883] start with a version number that is 
>    checked by LSRs performing MPLS payload inspection. To prevent the 
>    incorrect processing of packets carried within a PW, PW packets 
>    carried over an MPLS PSN SHOULD NOT start with the value 4 (IPv4) or 
>    the value 6 (IPv6) in the first nibble [BCP], as those are assumed 
>    to carry normal IP payloads. 

Why not specify a MUST NOT here?

> 
>    This document defines a PW header and two general formats of that 
>    header. These two formats are the PW MPLS Control Word (PWMCW) used 
>    for data passing across the PW, and a PW Associated Channel Header 
>    (PW-ACH) that can be used for functions such as OAM. 
> 
>    If the first nibble of a PWE3 packet carried over an MPLS PSN has a 
>    value of 0, it starts with a PWMCW. If the first nibble of a packet 
>    carried over an MPLS PSN has a value of 1, it starts with a PW-ACH. 
>    The use of any other first nibble value for a PWE3 packet carried 
>    over an MPLS PSN is deprecated. 
> 
>    A PW carried over an MPLS PSN that uses the contents of the MPLS 
>    payload to select the ECMP path SHOULD employ the PW MPLS Control 
>    Word described in Section 3 for data, and the PW Associated Channel 
>    Header described in Section 4 for channel associated traffic. These 
>    Control Words MUST immediately follow the bottom of the MPLS label 
>    stack. 
> 
> 
> 
> 
> 
> 
>  
> Bryant et al            Expires September 2005               [Page 2] 
> 
> 
> 
> 
> INTERNET DRAFT   PWE3 Control Word for use over an MPLS PSN   Mar 2005 
> 
> 3.   Generic PW MPLS Control Word 
> 
>    The Generic PW MPLS Control Word is shown in Figure 1.  
> 
>  
>     0                   1                   2                   3 
>     0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 
>    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 
>    |0 0 0 0|          Specified by PW Encapsulation                | 
>    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 
>     
>          Figure 1: Generic PW MPLS Control Word 
>  
>  
>    The PW set-up protocol or configuration mechanism determines whether 
>    a PW uses a PW MPLS Control Word (PWMCW). Bits 0..3 differ from the 
>    first four bits of an IP packet [BCP] and hence provide the 
>    necessary MPLS payload discrimination. 
> 
>    When a PWMCW is used, it MUST adhere to the Generic MPLS Control 
>    Word format as illustrated in Figure 1 above. It is however strongly 
>    recommended that it also follows the following format:  

Is this a capital RECOMMENDED or SHOULD?

> 
>  
>     0                   1                   2                   3 
>     0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 
>    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 
>    |0 0 0 0| Flags |FRG|  Length   | Sequence Number               | 
>    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 
> 
>         Figure 2: PW Preferred MPLS Control Word 
> 
>    The meaning of the fields of the PW Preferred MPLS Control Word 
>    (Figure 2) are as follows: 
> 
>    Flags (bits 4 to 7): 
> 
>           These bits are available for per-payload signalling.  Their 

s/ll/l

>           definition is encapsulation specific as defined in 
>           [pointer?]. 

"pointer?" needs to be defined.

> 
>    FRG (bits 8 and 9): 
> 
>           These bits are used when fragmenting a PW payload. Their use 
>           is described in [FRAG] which is currently a work in progress. 

Simply refer to [FRAG] here as if this reference was solid so as not to burden 
the RFC Editor with catching this sentence.

>           When the PW is of a type that will never need payload 
>           fragmentation, these bits may be used as general purpose 
>           flags. 
> 
>    Length (bits 10 to 15): 
> 
> 
> 
> 
> 
>  
> Bryant et al            Expires September 2005               [Page 3] 
> 
> 
> 
> 
> INTERNET DRAFT   PWE3 Control Word for use over an MPLS PSN   Mar 2005 
> 
>           The value of the length field, if non-zero, can be used to 
>           remove any padding added by the PSN. If the entire packet 
>           length is less than 64 bytes, the length field MUST be set to 
>           the length of the PW payload plus the length of the control 
>           word. Otherwise it MUST be set to zero.  
> 
>           If a non-zero length field is received, the PW payload MUST 
>           be trimmed if required. 

What is meant by "if required" - To me, this either MUST be trimmed or not (no 
need to suggest an implementation loophole if none should exist).

> 
>    Sequence number (Bit 16 to 31): 
> 
>           If the sequence number is not used, it is set to zero by the 
>           sender and ignored by the receiver.  Otherwise it specifies 
>           the sequence number of a packet.  A circular list of sequence 
>           numbers is used.  A sequence number takes a value from 1 to 
>           65535 (2**16-1). The sequence number window size for packet 
>           acceptance is dependent on the parameters of both the PW and 
>           the MPLS PSN, and SHOULD be configurable. The mechanism used 
>           by the decapsulating PE to syncronise the expected sequence 

s/syncronise/synchronize

That's two I caught, there must be more. Please run the doc through a spell checker.

>           number with the received sequence number is implementation 
>           dependent. 
> 
> 4.   PW Associated Channel 
> 
>    For some features of PWs, such as OAM, an associated channel is 
>    required. An associated channel is a channel that is multiplexed 
>    over the PW so that it follows exactly the same path through the PSN 
>    as the PW. Note that the use of the term "channel" is not a "PW 
>    channel type" as used in subsection 5.1.2 of [RFC3985] 
> 
>    When MPLS is used as the PSN, the PW Associated Channel is 
>    identified by the following header:  
> 
>    0                   1                   2                   3 
>    0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 
>    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 
>    |0 0 0 1| FmtID |   Reserved    |         Channel Type          | 
>    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+  
> 
>        Figure 3: PW Associated Channel Header  
> 
>    The meaning of the fields in the PW Associated Channel Header 
>    (Figure 3) are as follows: 
> 
>    FmtID:  
> 
>           Format ID for the remaining 3 octets of the header. A FmtID 
>           of 0 indicates that the 3 octets are as shown in Figure 3.  
> 
>    Reserved: 
> 
> 
> 
> 
> 
>  
> Bryant et al            Expires September 2005               [Page 4] 
> 
> 
> 
> 
> INTERNET DRAFT   PWE3 Control Word for use over an MPLS PSN   Mar 2005 
> 
>           Must be sent as 0, and ignored on reception. 
> 
>    Channel Type: 
> 
>           The PW Associated Channel Type is defined in the IANA PW 
>           Associated Channel Type registry [IANA]. 
> 
>    Bits 0..3 MUST be 0x01, and hence differ from the first four bits of 
>    an IP packet [BCP]. This provides the necessary MPLS payload 

The first bits being 0x01 also differ this payload from being a PW payload.

>    discrimination.  

The last sentence here could use a little more qualification, e.g., 
"...necessary MPLS payload discrimination for ECMP and other methods which 
require MPLS payload inspection..." or some such.

> 
>    Note that L2TPv3 [REFERENCE] has its own mechanisms for providing 
>    this associated channel, and is therefore out of the scope of this 
>    document. 

Need to define REFERENCE (RFC3931).

> 
> 5.   IANA considerations 
> 
>    IANA needs to set up a registry of "Pseudowire Associated Channel 
>    Types". These are 16-bit values. Registry entries are assigned by 
>    using the "IETF Consensus" policy defined in [RFC2434]. 

What about FMT IDs?

> 
> 6.   Security Considerations 
> 
>    An application using PW Associated Channel to provide an OAM [VCCV] 

Please provide the [VCCV] reference earlier in this document, the first time OAM 
is mentioned (and not necessarily here).

>    or other message channel MUST be aware that this can potentially be 
>    misused. Any application using the Associated Channel must therefore 
>    fully consider the resultant security issues, and provide mechanisms 
>    to prevent an attacker from using this as a mechanism to disrupt the 
>    operation of the PW or the PE, and to stop this channel from being 
>    used as a conduit to deliver packets elsewhere. 
> 
>    If a PW has been configured to operate without a CW, the PW 
>    Associated Channel Type mechanism described in the document MUST NOT 
>    be used. This is to prevent user payloads being fabricated in such a 
>    way that they mimic the PW Associated Channel Header, and thereby 
>    provide a method of attacking the application that is using the 
>    Associated Channel. 
> 
>     
> 
> 7.   Acknowledgements 
> 
>    The authors wish to thank David Allan, Luca Martini, Thomas Nadeau 
>    and Mark Townsley for their input to this work. 
> 
> 8.   Intellectual Property Statement 
> 
>  
>    The IETF takes no position regarding the validity or scope of any   
>    Intellectual Property Rights or other rights that might be claimed 
> 
> 
> 
> 
> 
>  
> Bryant et al            Expires September 2005               [Page 5] 
> 
> 
> 
> 
> INTERNET DRAFT   PWE3 Control Word for use over an MPLS PSN   Mar 2005 
> 
>    to pertain to the implementation or use of the technology described 
>    in this document or the extent to which any license under such 
>    rights might or might not be available; nor does it represent that 
>    it has made any independent effort to identify any such rights.  
>    Information on the procedures with respect to rights in RFC 
>    documents can be found in BCP 78 and BCP 79. 
> 
>    Copies of IPR disclosures made to the IETF Secretariat and any 
>    assurances of licenses to be made available, or the result of an   
>    attempt made to obtain a general license or permission for the use 
>    of such proprietary rights by implementers or users of this 
>    specification can be obtained from the IETF on-line IPR repository 
>    at http://www.ietf.org/ipr. 
> 
>    The IETF invites any interested party to bring to its attention any 
>    copyrights, patents or patent applications, or other proprietary 
>    rights that may cover technology that may be required to implement 
>    this standard.  Please address the information to the IETF at ietf-
>    ipr@ietf.org. 
> 
>  
> 9.    Full copyright statement 
> 
>    Copyright (C) The Internet Society (2004). This document is subject 
>    to the rights, licenses and restrictions contained in BCP 78, and 
>    except as set forth therein, the authors retain all their rights. 
> 
>    This document and the information contained herein are provided on 
>    an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE 
>    REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE 
>    INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR 
>    IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF 
>    THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 
>    WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 
> 
>     
> 
> 10.    Normative References 
> 
>    Internet-drafts are works in progress available from   
>    http://www.ietf.org/internet-drafts/ 
> 
>    [RFC791]   RFC-791: DARPA Internet Program, Protocol 
>                Specification, ISI, September 1981. 
> 
>    [RFC1883]  RFC-1883: Internet Protocol, Version 6 (IPv6), S. 
>                Deering, et al, December 1995 
> 
>     
> 
> 
> 
> 
> 
> 
>  
> Bryant et al            Expires September 2005               [Page 6] 
> 
> 
> 
> 
> INTERNET DRAFT   PWE3 Control Word for use over an MPLS PSN   Mar 2005 
> 
>     
> 
> 11.    Informative References 
> 
>  
>    Internet-drafts are works in progress available from   
>    <http://www.ietf.org/internet-drafts/> 
> 
>    [BCP]     Swallow, G. et al, "Avoiding Equal Cost Multipath 
>               Treatment in MPLS Networks", Internet Draft         
>               <draft-ietf-mpls-ecmp-bcp-00.txt>, September 2004, 
>               Work in Progress. 
> 
>    [FRAG]    Malis, A., Townsley, M., "PWE3 Fragmentation and 
>               Reassembly", Internet Draft, <draft-ietf-pwe3-
>               fragmentation-08.txt>, February 2005, Work in 
>               Progress. 
> 
>    [IANA]    Martini, L., Townsley M., "IANA Allocations for 
>               pseudo Wire Edge to Edge Emulation (PWE3) ", 
>               Internet Draft, <draft-ietf-pwe3-iana-allocation-
>               07.txt>, October 2004, Work in Progress. 
>                
>    [RFC2434] RFC-2434: Guidelines for Writing an IANA 
>               Considerations Section in RFCs, Narten, T., 
>               Alvestrand, H., October 1998 
>                
>    [RFC2992] RFC-2992:  Analysis of an Equal-Cost Multi-Path 
>               Algorithm, C. Hopps, November 2000 
>    [RFC3985] RFC-3985: PWE3 Architecture, Bryant, S. ed., Pate, 
>               P. ed. , To be published.  
>    [VCCV]    Nadeau, T., Aggarwal, T., "Pseudo Wire (PW) Virtual 
>               Circuit Connection Verification (VCCV)", Internet 
>               Draft, <draft-ietf-pwe3-vccv-04.txt>, Feb. 2005, 
>               Work in Progress. 

Line spacing above.



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


From pwe3-bounces@ietf.org  Tue Apr 12 06:58:30 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA18840
	for <pwe3-archive@ietf.org>; Tue, 12 Apr 2005 06:58:30 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DLJFr-0004wD-42
	for pwe3-archive@ietf.org; Tue, 12 Apr 2005 07:08:27 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DLIt0-0002jO-33; Tue, 12 Apr 2005 06:44:50 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DLIsy-0002ir-Bs
	for pwe3@megatron.ietf.org; Tue, 12 Apr 2005 06:44:48 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA17743
	for <pwe3@ietf.org>; Tue, 12 Apr 2005 06:44:37 -0400 (EDT)
Received: from radmail2.rad.co.il ([80.74.100.136] helo=antivir1.rad.co.il)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DLJ2M-0004WS-Ou
	for pwe3@ietf.org; Tue, 12 Apr 2005 06:54:33 -0400
Received: from antivir1.rad.co.il (localhost [127.0.0.1])
	by antivir1.rad.co.il (8.12.10/8.12.10) with ESMTP id j3CAhO3O027823
	for <pwe3@ietf.org>; Tue, 12 Apr 2005 13:43:26 +0300 (IDT)
Received: from exrad2.ad.rad.co.il (exrad2 [192.114.24.112])
	by antivir1.rad.co.il (8.12.10/8.12.10) with ESMTP id j3CAhOgd027820;
	Tue, 12 Apr 2005 13:43:24 +0300 (IDT)
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [PWE3] AD Review of draft-ietf-pwe3-cw-03.txt 
Date: Tue, 12 Apr 2005 13:43:56 +0200
Message-ID: <27A0F290348F8E45AEF79889DDE65A520450C3BA@exrad2.ad.rad.co.il>
Thread-Topic: [PWE3] AD Review of draft-ietf-pwe3-cw-03.txt 
Thread-Index: AcU+4xy3n0EziFSYSySg+aKlos7iPgAcNxOw
From: "Yaakov Stein" <yaakov_s@rad.com>
To: "W. Mark Townsley" <townsley@cisco.com>,
        "Stewart Bryant" <stbryant@cisco.com>,
        "Danny McPherson" <danny@tcb.net>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0bc60ec82efc80c84b8d02f4b0e4de22
Content-Transfer-Encoding: quoted-printable
Cc: "PWE3 WG \(E-mail\)" <pwe3@ietf.org>
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=subscribe>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b19722fc8d3865b147c75ae2495625f2
Content-Transfer-Encoding: quoted-printable

=20
> >           If a non-zero length field is received, the PW payload
MUST=20
> >           be trimmed if required.=20
>=20
> What is meant by "if required" - To me, this either MUST be=20
> trimmed or not (no need to suggest an implementation loophole=20
> if none should exist).

How about this ?
  If a non-zero length field is received, the PW payload MUST=20
  be trimmed if the actual packet length is larger than that indicated.

<snip>=20
> That's two I caught, there must be more. Please run the doc=20
> through a spell checker.

The question is how to set the spelling checker=20
when we have Danny and Stewart as co-chairs.
Should it be set to American spelling
(signaling, synchronize)
or British
(signalling, sycnhronise) ?
But in either case syncronise would be flagged.


Y(J)S


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


From pwe3-bounces@ietf.org  Wed Apr 13 13:03:08 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA13995
	for <pwe3-archive@ietf.org>; Wed, 13 Apr 2005 13:03:08 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DLlQW-0004oc-0c
	for pwe3-archive@ietf.org; Wed, 13 Apr 2005 13:13:20 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DLlAJ-0002m9-MO; Wed, 13 Apr 2005 12:56:35 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DLlAH-0002lI-Ja
	for pwe3@megatron.ietf.org; Wed, 13 Apr 2005 12:56:33 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA13416
	for <pwe3@ietf.org>; Wed, 13 Apr 2005 12:56:22 -0400 (EDT)
Received: from napoleon.monoski.com ([63.225.114.233])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DLlJx-0004ae-GL
	for pwe3@ietf.org; Wed, 13 Apr 2005 13:06:35 -0400
Received: from [2.0.1.6] (rasputin-gw [2.0.1.6]) (authenticated bits=0)
	by napoleon.monoski.com (8.13.2/8.13.2) with ESMTP id j3DGu4eI027961;
	Wed, 13 Apr 2005 10:56:05 -0600 (MDT)
Message-ID: <425D4F21.4060205@cisco.com>
Date: Wed, 13 Apr 2005 10:56:01 -0600
From: Luca Martini <lmartini@cisco.com>
User-Agent: Mozilla Thunderbird 1.0 (X11/20041206)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Yijun Xiong <yxiong@hammerheadsystems.com>
Subject: Re: [PWE3] How to choose Interface MTU for PW heterogeneous transport
References: <2DAC9E7A4640234B85975565E5D83AE110D44F@srvcaexg01.headquarters.hammerheadsystems.com>
In-Reply-To: <2DAC9E7A4640234B85975565E5D83AE110D44F@srvcaexg01.headquarters.hammerheadsystems.com>
X-Scanned-By: MIMEDefang 2.28 (www . roaringpenguin . com / mimedefang)
X-Spam-Score: 0.7 (/)
X-Scan-Signature: f49c97ce49302a02285a2d36a99eef8c
Cc: pwe3@ietf.org
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1846266010=="
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org
X-Spam-Score: 1.0 (+)
X-Scan-Signature: 225414c974e0d6437992164e91287a51

This is a multi-part message in MIME format...

--===============1846266010==
Content-Type: multipart/alternative;
	boundary="------------020405010106000405070506"

This is a multi-part message in MIME format...

--------------020405010106000405070506
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

Yijun Xiong wrote:

> Hi,   In draft-ietf-pwe3-control-protocol-16.txt "Pseudowire Setup and 
> Maintenance using LDP", Interface MTU parameter is used when setting 
> up PWs. It is stated that if this parameter does not match in both 
> directions of a specific PW, that PW MUST NOT be enabled.   I have the 
> following questions while implementing the heterogeneous transport, 
> e.g., when one AC (between CE1 and PE1) is ATM, another AC (between 
> PE2 and CE2) is FR.   (1) Suppose PW1 is for ATM to FR direction, PW2 
> for FR to ATM direction, how to select PW type, ATM PW or FR PW for 
> PW1 and PW2? Can PW1 be ATM type and PW2 be FR type?   (2) For FR AC, 
> I would assume that one can use FR UNI MTU as interface MTU for PW, 
> How to choose interface MTU for ATM AC, as ATM UNI has no such 
> parameter like MTU?     Thanks.   Yijun Xiong Hammerhead Systems Inc.
>
>  
>
Interworking of frame-relay - ATM is not part of the PWE3 specification. 
The PW has to be of the same type on both ends , just pick one.
Then implement the interworking function at one end to convert the ATM 
to F/R.
The interface MTU is determined by the interworking function. So if you 
are converting ATM AAL5 , presumably you'll have a maximum AAL5 fame 
size. you can use that as the MTU of the F/R PW.

Luca

>------------------------------------------------------------------------
>
>_______________________________________________
>pwe3 mailing list
>pwe3@ietf.org
>https://www1.ietf.org/mailman/listinfo/pwe3
>  
>


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

<DEFANGED_!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">
Yijun Xiong wrote:
<blockquote
 cite="mid2DAC9E7A4640234B85975565E5D83AE110D44F@srvcaexg01.headquarters.hammerheadsystems.com"
 type="cite"><DEFANGED_ !doctype="" public="" -//w3c//dtd="" html=""
 4.0="" transitional//en="">
  <title>Message</title>
  <meta http-equiv="Content-Type" content="text/html; ">
  <meta content="MSHTML 6.00.2800.1479" name="GENERATOR">
  <DEFANGED_DIV><font face="Arial"><DEFANGED_SPAN
 class="127020617-04042005">
  <DEFANGED_DIV><font face="Courier" size="2"><DEFANGED_SPAN
 class="348252119-01042005">Hi,</DEFANGED_SPAN></font></DEFANGED_DIV>
  <DEFANGED_DIV><font face="Courier" size="2"><DEFANGED_SPAN
 class="348252119-01042005"></DEFANGED_SPAN></font>&nbsp;</DEFANGED_DIV>
  <DEFANGED_DIV><font face="Courier" size="2"><DEFANGED_SPAN
 class="348252119-01042005">In draft-ietf-pwe3-control-protocol-16.txt
"Pseudowire Setup and Maintenance using LDP", Interface MTU parameter
is used when setting up PWs. It is stated that if this parameter does
not match in both directions of a specific PW, that PW MUST NOT be
enabled.</DEFANGED_SPAN></font></DEFANGED_DIV>
  <DEFANGED_DIV><font face="Courier" size="2"><DEFANGED_SPAN
 class="348252119-01042005"></DEFANGED_SPAN></font>&nbsp;</DEFANGED_DIV>
  <DEFANGED_DIV><font face="Courier" size="2"><DEFANGED_SPAN
 class="348252119-01042005">I&nbsp;have the following&nbsp;questions while
implementing the heterogeneous transport, e.g., when&nbsp;one AC&nbsp;<DEFANGED_SPAN
 class="127020617-04042005">(between CE1 and PE1) </DEFANGED_SPAN>is
ATM, another AC&nbsp;<DEFANGED_SPAN class="127020617-04042005">(between PE2
and CE2) </DEFANGED_SPAN>is FR.</DEFANGED_SPAN></font></DEFANGED_DIV>
  <DEFANGED_DIV><font face="Courier" size="2"><DEFANGED_SPAN
 class="348252119-01042005"></DEFANGED_SPAN></font>&nbsp;</DEFANGED_DIV>
  <DEFANGED_DIV><font face="Courier" size="2"><DEFANGED_SPAN
 class="348252119-01042005">(1)&nbsp;<DEFANGED_SPAN
 class="127020617-04042005">Suppose PW1 is for ATM to FR direction, PW2
for FR to ATM direction, h</DEFANGED_SPAN>ow to select PW type,
ATM&nbsp;PW&nbsp;or FR PW for PW1 and PW2? Can PW1 be ATM type and PW2 be FR type?</DEFANGED_SPAN></font></DEFANGED_DIV>
  <DEFANGED_DIV><font face="Courier" size="2"><DEFANGED_SPAN
 class="348252119-01042005"></DEFANGED_SPAN></font>&nbsp;</DEFANGED_DIV>
  <DEFANGED_DIV><font face="Courier" size="2"><DEFANGED_SPAN
 class="348252119-01042005">(2) For FR AC, I would assume that one can
use FR UNI MTU as interface MTU for PW, How to choose interface MTU for
ATM AC, as ATM UNI has no such parameter like MTU?</DEFANGED_SPAN></font></DEFANGED_DIV>
  <DEFANGED_DIV><font face="Courier" size="2"><DEFANGED_SPAN
 class="348252119-01042005"></DEFANGED_SPAN></font>&nbsp;</DEFANGED_DIV>
  <DEFANGED_DIV><font face="Courier" size="2"><DEFANGED_SPAN
 class="348252119-01042005"></DEFANGED_SPAN></font>&nbsp;</DEFANGED_DIV>
  <DEFANGED_DIV><font face="Courier" size="2"><DEFANGED_SPAN
 class="348252119-01042005"><DEFANGED_DIV><font face="Arial"><DEFANGED_SPAN
 class="348252119-01042005"><font face="Courier" size="2">Thanks.</font></DEFANGED_SPAN></font></DEFANGED_DIV>
  <DEFANGED_DIV><font face="Arial"><DEFANGED_SPAN
 class="348252119-01042005"></DEFANGED_SPAN></font>&nbsp;</DEFANGED_DIV>
  <DEFANGED_DIV><font size="+0"><DEFANGED_SPAN
 class="348252119-01042005"><font face="Courier" size="2">Yijun Xiong </font></DEFANGED_SPAN></font></DEFANGED_DIV>
  <DEFANGED_DIV><font size="+0"><DEFANGED_SPAN
 class="348252119-01042005"><font size="2"><font face="Courier">Hammerhead
Systems Inc.</font></font></DEFANGED_SPAN></font></DEFANGED_DIV></DEFANGED_SPAN></font></DEFANGED_DIV></DEFANGED_SPAN></font></DEFANGED_DIV></DEFANGED_>
  <pre wrap="">
  </pre>
</blockquote>
Interworking of frame-relay - ATM is not part of the PWE3
specification. The PW has to be of the same type on both ends , just
pick one.<br>
Then implement the interworking function at one end to convert the ATM
to F/R. <br>
The interface MTU is determined by the interworking function. So if you
are converting ATM AAL5 , presumably you'll have a maximum AAL5 fame
size. you can use that as the MTU of the F/R PW.<br>
<br>
Luca<br>
<br>
<blockquote
 cite="mid2DAC9E7A4640234B85975565E5D83AE110D44F@srvcaexg01.headquarters.hammerheadsystems.com"
 type="cite">
  <pre wrap=""><hr size="4" width="90%">
_______________________________________________
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://www1.ietf.org/mailman/listinfo/pwe3">https://www1.ietf.org/mailman/listinfo/pwe3</a>
  </pre>
</blockquote>
<br>
</body>
</html>

--------------020405010106000405070506--


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

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

--===============1846266010==--



From pwe3-bounces@ietf.org  Wed Apr 13 14:55:03 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA22575
	for <pwe3-archive@ietf.org>; Wed, 13 Apr 2005 14:55:02 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DLnAo-0007uw-AE
	for pwe3-archive@ietf.org; Wed, 13 Apr 2005 15:05:14 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DLmuk-000663-Al; Wed, 13 Apr 2005 14:48:38 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DLmui-00065k-Su
	for pwe3@megatron.ietf.org; Wed, 13 Apr 2005 14:48:37 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA22021
	for <pwe3@ietf.org>; Wed, 13 Apr 2005 14:48:27 -0400 (EDT)
Received: from napoleon.monoski.com ([63.225.114.233])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DLn4Q-0007j5-3Y
	for pwe3@ietf.org; Wed, 13 Apr 2005 14:58:39 -0400
Received: from [2.0.1.6] (rasputin-gw [2.0.1.6]) (authenticated bits=0)
	by napoleon.monoski.com (8.13.2/8.13.2) with ESMTP id j3DIlxtX028450;
	Wed, 13 Apr 2005 12:48:00 -0600 (MDT)
Message-ID: <425D695D.3080709@cisco.com>
Date: Wed, 13 Apr 2005 12:47:57 -0600
From: Luca Martini <lmartini@cisco.com>
User-Agent: Mozilla Thunderbird 1.0 (X11/20041206)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "W. Mark Townsley" <townsley@cisco.com>
Subject: Re: [PWE3] AD Review of draft-ietf-pwe3-cw-03.txt
References: <425AE61B.2030909@cisco.com>
In-Reply-To: <425AE61B.2030909@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Scanned-By: MIMEDefang 2.28 (www . roaringpenguin . com / mimedefang)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ea36de7a5e28e9b4461c8d685f4e97f1
Content-Transfer-Encoding: 7bit
Cc: Danny McPherson <danny@tcb.net>, "PWE3 WG \(E-mail\)" <pwe3@ietf.org>,
        Stewart Bryant <stbryant@cisco.com>
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=subscribe>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 82b297dca242a35ee50ccecf5bf2e37f
Content-Transfer-Encoding: 7bit

some comments inline.
Tks
Luca

W. Mark Townsley wrote:

>
> Please find comments inline.
>
> Thanks,
>
> - Mark
>
>>                                                                         
>> Network Working Group                                         S. 
>> Bryant Internet Draft                                               
>> G. Swallow Expiration Date: September 2005                           
>> Cisco Systems 
>>                                                            D. 
>> McPherson                                                          
>> Arbor Networks 
>>                                                                         
>>                                                              March 
>> 2005 
>>                                                                         
>>                                                                         
>>                 PWE3 Control Word for use over an MPLS PSN
>>                         draft-ietf-pwe3-cw-03.txt
>>         Status of this Memo 
>>    By submitting this Internet-Draft, we certify that any applicable 
>>    patent or other IPR claims of which we are aware have been    
>> disclosed, or will be disclosed, and any of which we become aware    
>> will be disclosed, in accordance with RFC 3668.
>>    Internet-Drafts are working documents of the Internet Engineering 
>>    Task Force (IETF), its areas, and its working groups.  Note that 
>>    other groups may also distribute working documents as           
>> Internet-Drafts.
>>    Internet-Drafts are draft documents valid for a maximum of six    
>> months and may be updated, replaced, or obsoleted by other documents 
>>    at any time.  It is inappropriate to use Internet-Drafts as    
>> reference material or to cite them other than as "work in progress".
>>    The list of current Internet-Drafts can be accessed at    
>> http://www.ietf.org/1id-abstracts.html 
>>    The list of Internet-Draft Shadow Directories can be accessed at 
>>    http://www.ietf.org/shadow.html
>> Abstract   
>>    This document describes the preferred designs of the PWE3 MPLS    
>> Control Word, and the PW Associated Channel Header. The design of    
>> these fields is chosen so that an MPLS LSR performing MPLS payload    
>> inspection will not confuse a PWE3 payload with an IP payload.
>> Conventions used in this document      
>>
>>
>>
>>  
>> Bryant et al            Expires September 2005               [Page 1] 
>>
>>
>>
>> INTERNET DRAFT   PWE3 Control Word for use over an MPLS PSN   Mar 2005
>>    The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL 
>> NOT",    "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" 
>> in this    document are to be interpreted as described in RFC 2119 
>> [RFC2119].
>>  
>> 1.   Introduction
>>    The standard MPLS encapsulations have no explicit protocol    
>> identifier. In order for a pseudo wire (PW) [RFC3985] to operate    
>> correctly over an MPLS packet switched network (PSN) that performs    
>> MPLS payload inspection, a PW packet must not appear to the LSR as    
>> if it were an IP packet [BCP]. An example of an LSR that performs    
>> MPLS payload inspection is one that is performing equal-cost    
>> multiple-path load-balancing (ECMP) [RFC2992]. If ECMP were    
>> performed on PWE3 packets, the packets in the PW may not all follow 
>>    the same path through the PSN. This may result in misordered 
>> packet    delivery to the egress PE. The inability to ensure that all 
>> packets    belonging to a PW follow the same path may also prevent 
>> the PW OAM    [VCCV] mechanism from correctly monitoring the PW. 
>>    This draft specifies how a PW header distinguishes a PW payload 
>> from    an IP payload carried over an MPLS PSN.
>> 2.   PWE3 Packet Identification
>>    All IP packets [RFC791][RFC1883] start with a version number that 
>> is    checked by LSRs performing MPLS payload inspection. To prevent 
>> the    incorrect processing of packets carried within a PW, PW 
>> packets    carried over an MPLS PSN SHOULD NOT start with the value 4 
>> (IPv4) or    the value 6 (IPv6) in the first nibble [BCP], as those 
>> are assumed    to carry normal IP payloads. 
>
>
> Why not specify a MUST NOT here?
>
Some of the TDM PWs might start with a 4, as they do not have a 
conformant CW.

>>
>>    This document defines a PW header and two general formats of that 
>>    header. These two formats are the PW MPLS Control Word (PWMCW) 
>> used    for data passing across the PW, and a PW Associated Channel 
>> Header    (PW-ACH) that can be used for functions such as OAM.
>>    If the first nibble of a PWE3 packet carried over an MPLS PSN has 
>> a    value of 0, it starts with a PWMCW. If the first nibble of a 
>> packet    carried over an MPLS PSN has a value of 1, it starts with a 
>> PW-ACH.    The use of any other first nibble value for a PWE3 packet 
>> carried    over an MPLS PSN is deprecated.
>>    A PW carried over an MPLS PSN that uses the contents of the MPLS 
>>    payload to select the ECMP path SHOULD employ the PW MPLS Control 
>>    Word described in Section 3 for data, and the PW Associated 
>> Channel    Header described in Section 4 for channel associated 
>> traffic. These    Control Words MUST immediately follow the bottom of 
>> the MPLS label    stack.
>>
>>
>>
>>
>>
>>  
>> Bryant et al            Expires September 2005               [Page 2] 
>>
>>
>>
>> INTERNET DRAFT   PWE3 Control Word for use over an MPLS PSN   Mar 2005
>> 3.   Generic PW MPLS Control Word
>>    The Generic PW MPLS Control Word is shown in Figure 1. 
>>  
>>     0                   1                   2                   3     
>> 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1    
>> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+    
>> |0 0 0 0|          Specified by PW Encapsulation                |    
>> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+     
>>          Figure 1: Generic PW MPLS Control Word  
>>  
>>    The PW set-up protocol or configuration mechanism determines 
>> whether    a PW uses a PW MPLS Control Word (PWMCW). Bits 0..3 differ 
>> from the    first four bits of an IP packet [BCP] and hence provide 
>> the    necessary MPLS payload discrimination.
>>    When a PWMCW is used, it MUST adhere to the Generic MPLS Control 
>>    Word format as illustrated in Figure 1 above. It is however 
>> strongly    recommended that it also follows the following format:  
>
>
> Is this a capital RECOMMENDED or SHOULD?
>
yes i think it needs a capital RECOMMENDED.

>>
>>  
>>     0                   1                   2                   3     
>> 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1    
>> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+    
>> |0 0 0 0| Flags |FRG|  Length   | Sequence Number               |    
>> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>         Figure 2: PW Preferred MPLS Control Word
>>    The meaning of the fields of the PW Preferred MPLS Control Word    
>> (Figure 2) are as follows:
>>    Flags (bits 4 to 7):
>>           These bits are available for per-payload signalling.  Their 
>
>
> s/ll/l
>
>>           definition is encapsulation specific as defined in 
>>           [pointer?]. 
>
>
> "pointer?" needs to be defined.
>
omission - this needs to be removed ....

>>
>>    FRG (bits 8 and 9):
>>           These bits are used when fragmenting a PW payload. Their 
>> use           is described in [FRAG] which is currently a work in 
>> progress. 
>
>
> Simply refer to [FRAG] here as if this reference was solid so as not 
> to burden the RFC Editor with catching this sentence.
>
>>           When the PW is of a type that will never need payload 
>>           fragmentation, these bits may be used as general purpose 
>>           flags.
>>    Length (bits 10 to 15):
>>
>>
>>
>>
>>  
>> Bryant et al            Expires September 2005               [Page 3] 
>>
>>
>>
>> INTERNET DRAFT   PWE3 Control Word for use over an MPLS PSN   Mar 2005
>>           The value of the length field, if non-zero, can be used to 
>>           remove any padding added by the PSN. If the entire packet 
>>           length is less than 64 bytes, the length field MUST be set 
>> to           the length of the PW payload plus the length of the 
>> control           word. Otherwise it MUST be set to zero. 
>>           If a non-zero length field is received, the PW payload MUST 
>>           be trimmed if required. 
>
>
> What is meant by "if required" - To me, this either MUST be trimmed or 
> not (no need to suggest an implementation loophole if none should exist).
>
no, it means that the payload might already be the correct length , 
hence it might not need to be trimmed....
Not all short packet have to be padded , some media do not require 
padding ....

>>
>>    Sequence number (Bit 16 to 31):
>>           If the sequence number is not used, it is set to zero by 
>> the           sender and ignored by the receiver.  Otherwise it 
>> specifies           the sequence number of a packet.  A circular list 
>> of sequence           numbers is used.  A sequence number takes a 
>> value from 1 to           65535 (2**16-1). The sequence number window 
>> size for packet           acceptance is dependent on the parameters 
>> of both the PW and           the MPLS PSN, and SHOULD be 
>> configurable. The mechanism used           by the decapsulating PE to 
>> syncronise the expected sequence 
>
>
> s/syncronise/synchronize
>
> That's two I caught, there must be more. Please run the doc through a 
> spell checker.
>
>>           number with the received sequence number is implementation 
>>           dependent.
>> 4.   PW Associated Channel
>>    For some features of PWs, such as OAM, an associated channel is    
>> required. An associated channel is a channel that is multiplexed    
>> over the PW so that it follows exactly the same path through the PSN 
>>    as the PW. Note that the use of the term "channel" is not a "PW    
>> channel type" as used in subsection 5.1.2 of [RFC3985]
>>    When MPLS is used as the PSN, the PW Associated Channel is    
>> identified by the following header: 
>>    0                   1                   2                   3    0 
>> 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1    
>> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+    
>> |0 0 0 1| FmtID |   Reserved    |         Channel Type          |    
>> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 
>>        Figure 3: PW Associated Channel Header 
>>    The meaning of the fields in the PW Associated Channel Header    
>> (Figure 3) are as follows:
>>    FmtID: 
>>           Format ID for the remaining 3 octets of the header. A FmtID 
>>           of 0 indicates that the 3 octets are as shown in Figure 3. 
>>    Reserved:
>>
>>
>>
>>
>>  
>> Bryant et al            Expires September 2005               [Page 4] 
>>
>>
>>
>> INTERNET DRAFT   PWE3 Control Word for use over an MPLS PSN   Mar 2005
>>           Must be sent as 0, and ignored on reception.
>>    Channel Type:
>>           The PW Associated Channel Type is defined in the IANA PW 
>>           Associated Channel Type registry [IANA].
>>    Bits 0..3 MUST be 0x01, and hence differ from the first four bits 
>> of    an IP packet [BCP]. This provides the necessary MPLS payload 
>
>
> The first bits being 0x01 also differ this payload from being a PW 
> payload.
>
>>    discrimination.  
>
>
> The last sentence here could use a little more qualification, e.g., 
> "...necessary MPLS payload discrimination for ECMP and other methods 
> which require MPLS payload inspection..." or some such.
>
>>
>>    Note that L2TPv3 [REFERENCE] has its own mechanisms for providing 
>>    this associated channel, and is therefore out of the scope of this 
>>    document. 
>
>
> Need to define REFERENCE (RFC3931).
>
>>
>> 5.   IANA considerations
>>    IANA needs to set up a registry of "Pseudowire Associated Channel 
>>    Types". These are 16-bit values. Registry entries are assigned by 
>>    using the "IETF Consensus" policy defined in [RFC2434]. 
>
>
> What about FMT IDs?
>
r

>>
>> 6.   Security Considerations
>>    An application using PW Associated Channel to provide an OAM [VCCV] 
>
>
> Please provide the [VCCV] reference earlier in this document, the 
> first time OAM is mentioned (and not necessarily here).
>
>>    or other message channel MUST be aware that this can potentially 
>> be    misused. Any application using the Associated Channel must 
>> therefore    fully consider the resultant security issues, and 
>> provide mechanisms    to prevent an attacker from using this as a 
>> mechanism to disrupt the    operation of the PW or the PE, and to 
>> stop this channel from being    used as a conduit to deliver packets 
>> elsewhere.
>>    If a PW has been configured to operate without a CW, the PW    
>> Associated Channel Type mechanism described in the document MUST NOT 
>>    be used. This is to prevent user payloads being fabricated in such 
>> a    way that they mimic the PW Associated Channel Header, and 
>> thereby    provide a method of attacking the application that is 
>> using the    Associated Channel.
>>    
>> 7.   Acknowledgements
>>    The authors wish to thank David Allan, Luca Martini, Thomas Nadeau 
>>    and Mark Townsley for their input to this work.
>> 8.   Intellectual Property Statement
>>  
>>    The IETF takes no position regarding the validity or scope of 
>> any      Intellectual Property Rights or other rights that might be 
>> claimed
>>
>>
>>
>>
>>  
>> Bryant et al            Expires September 2005               [Page 5] 
>>
>>
>>
>> INTERNET DRAFT   PWE3 Control Word for use over an MPLS PSN   Mar 2005
>>    to pertain to the implementation or use of the technology 
>> described    in this document or the extent to which any license 
>> under such    rights might or might not be available; nor does it 
>> represent that    it has made any independent effort to identify any 
>> such rights.     Information on the procedures with respect to rights 
>> in RFC    documents can be found in BCP 78 and BCP 79.
>>    Copies of IPR disclosures made to the IETF Secretariat and any    
>> assurances of licenses to be made available, or the result of an      
>> attempt made to obtain a general license or permission for the use    
>> of such proprietary rights by implementers or users of this    
>> specification can be obtained from the IETF on-line IPR repository    
>> at http://www.ietf.org/ipr.
>>    The IETF invites any interested party to bring to its attention 
>> any    copyrights, patents or patent applications, or other 
>> proprietary    rights that may cover technology that may be required 
>> to implement    this standard.  Please address the information to the 
>> IETF at ietf-
>>    ipr@ietf.org.
>>  
>> 9.    Full copyright statement
>>    Copyright (C) The Internet Society (2004). This document is 
>> subject    to the rights, licenses and restrictions contained in BCP 
>> 78, and    except as set forth therein, the authors retain all their 
>> rights.
>>    This document and the information contained herein are provided on 
>>    an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE    
>> REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE 
>>    INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS 
>> OR    IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE 
>> OF    THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY 
>> IMPLIED    WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR 
>> PURPOSE.
>>    
>> 10.    Normative References
>>    Internet-drafts are works in progress available from      
>> http://www.ietf.org/internet-drafts/
>>    [RFC791]   RFC-791: DARPA Internet Program, Protocol 
>>                Specification, ISI, September 1981.
>>    [RFC1883]  RFC-1883: Internet Protocol, Version 6 (IPv6), S. 
>>                Deering, et al, December 1995
>>    
>>
>>
>>
>>
>>
>>  
>> Bryant et al            Expires September 2005               [Page 6] 
>>
>>
>>
>> INTERNET DRAFT   PWE3 Control Word for use over an MPLS PSN   Mar 2005
>>    
>> 11.    Informative References
>>  
>>    Internet-drafts are works in progress available from      
>> <http://www.ietf.org/internet-drafts/>
>>    [BCP]     Swallow, G. et al, "Avoiding Equal Cost Multipath 
>>               Treatment in MPLS Networks", Internet Draft         
>>               <draft-ietf-mpls-ecmp-bcp-00.txt>, September 2004, 
>>               Work in Progress.
>>    [FRAG]    Malis, A., Townsley, M., "PWE3 Fragmentation and 
>>               Reassembly", Internet Draft, <draft-ietf-pwe3-
>>               fragmentation-08.txt>, February 2005, Work in 
>>               Progress.
>>    [IANA]    Martini, L., Townsley M., "IANA Allocations for 
>>               pseudo Wire Edge to Edge Emulation (PWE3) ", 
>>               Internet Draft, <draft-ietf-pwe3-iana-allocation-
>>               07.txt>, October 2004, Work in Progress.                
>>    [RFC2434] RFC-2434: Guidelines for Writing an IANA               
>> Considerations Section in RFCs, Narten, T.,               Alvestrand, 
>> H., October 1998                   [RFC2992] RFC-2992:  Analysis of 
>> an Equal-Cost Multi-Path               Algorithm, C. Hopps, November 
>> 2000    [RFC3985] RFC-3985: PWE3 Architecture, Bryant, S. ed., Pate, 
>>               P. ed. , To be published.     [VCCV]    Nadeau, T., 
>> Aggarwal, T., "Pseudo Wire (PW) Virtual               Circuit 
>> Connection Verification (VCCV)", Internet               Draft, 
>> <draft-ietf-pwe3-vccv-04.txt>, Feb. 2005,               Work in 
>> Progress. 
>
>
> Line spacing above.
>
>
>
> _______________________________________________
> pwe3 mailing list
> pwe3@ietf.org
> https://www1.ietf.org/mailman/listinfo/pwe3



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


From pwe3-bounces@ietf.org  Wed Apr 13 16:33:48 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA04900
	for <pwe3-archive@ietf.org>; Wed, 13 Apr 2005 16:33:48 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DLoiP-0003bk-8G
	for pwe3-archive@ietf.org; Wed, 13 Apr 2005 16:44:01 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DLoTW-00058V-N6; Wed, 13 Apr 2005 16:28:38 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DLoTU-00056t-HI
	for pwe3@megatron.ietf.org; Wed, 13 Apr 2005 16:28:36 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA03815
	for <pwe3@ietf.org>; Wed, 13 Apr 2005 16:28:26 -0400 (EDT)
Received: from rtp-iport-1.cisco.com ([64.102.122.148])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DLod9-0003EL-F3
	for pwe3@ietf.org; Wed, 13 Apr 2005 16:38:39 -0400
Received: from rtp-core-2.cisco.com (64.102.124.13)
	by rtp-iport-1.cisco.com with ESMTP; 13 Apr 2005 16:38:04 -0400
X-IronPort-AV: i="3.92,98,1112587200"; 
	d="scan'208"; a="44461147:sNHT285415584"
Received: from fruitpie.cisco.com (IDENT:mirapoint@fruitpie.cisco.com
	[64.102.16.27])
	by rtp-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id j3DKSBHd001761; 
	Wed, 13 Apr 2005 16:28:11 -0400 (EDT)
Received: from [10.83.1.102] (rtp-townsley-vpn5.cisco.com [10.83.1.102])
	by fruitpie.cisco.com (MOS 3.4.6-GR) with SMTP id BGR79508;
	Wed, 13 Apr 2005 13:28:07 -0700 (PDT)
Message-ID: <425D80D5.2080604@cisco.com>
Date: Wed, 13 Apr 2005 16:28:05 -0400
From: "W. Mark Townsley" <townsley@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
	rv:1.7) Gecko/20040616
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Luca Martini <lmartini@cisco.com>
Subject: Re: [PWE3] AD Review of draft-ietf-pwe3-cw-03.txt
References: <425AE61B.2030909@cisco.com> <425D695D.3080709@cisco.com>
In-Reply-To: <425D695D.3080709@cisco.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 08582f3b796126054df71137d5cb69f8
Content-Transfer-Encoding: 7bit
Cc: Stewart Bryant <stbryant@cisco.com>, "PWE3 WG \(E-mail\)" <pwe3@ietf.org>,
        Danny McPherson <danny@tcb.net>
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=subscribe>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c8d1e86bb8f49de8156b6392faa4a63b
Content-Transfer-Encoding: 7bit


Apologies for the CR/LF problem in the earlier email. I think that it should be 
fixed in this one.

I have reinserted Luca and I's comments inline marked with "Luca>" and "Mark>". 
Luca, I have a few additional comments/responses inline after yours.

Thanks,

- Mark

 >
 > Network Working Group                                         S. Bryant
 > Internet Draft                                               G. Swallow
 > Expiration Date: September 2005                           Cisco Systems
 >                                                            D. McPherson
 >                                                          Arbor Networks
 >
 >                                                              March 2005
 >
 >
 >                 PWE3 Control Word for use over an MPLS PSN
 >
 >                         draft-ietf-pwe3-cw-03.txt
 >
 >
 >
 >
 > Status of this Memo
 >
 >    By submitting this Internet-Draft, we certify that any applicable
 >    patent or other IPR claims of which we are aware have been
 >    disclosed, or will be disclosed, and any of which we become aware
 >    will be disclosed, in accordance with RFC 3668.
 >
 >    Internet-Drafts are working documents of the Internet Engineering
 >    Task Force (IETF), its areas, and its working groups.  Note that
 >    other groups may also distribute working documents as
 >    Internet-Drafts.
 >
 >    Internet-Drafts are draft documents valid for a maximum of six
 >    months and may be updated, replaced, or obsoleted by other documents
 >    at any time.  It is inappropriate to use Internet-Drafts as
 >    reference material or to cite them other than as "work in progress".
 >
 >    The list of current Internet-Drafts can be accessed at
 >    http://www.ietf.org/1id-abstracts.html
 >
 >    The list of Internet-Draft Shadow Directories can be accessed at
 >    http://www.ietf.org/shadow.html
 >
 > Abstract
 >
 >    This document describes the preferred designs of the PWE3 MPLS
 >    Control Word, and the PW Associated Channel Header. The design of
 >    these fields is chosen so that an MPLS LSR performing MPLS payload
 >    inspection will not confuse a PWE3 payload with an IP payload.
 >
 > Conventions used in this document
 >
 >
 >
 >
 >
 >
 > Bryant et al            Expires September 2005               [Page 1]
 > 
 >
 >
 >
 > INTERNET DRAFT   PWE3 Control Word for use over an MPLS PSN   Mar 2005
 >
 >    The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
 >    "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
 >    document are to be interpreted as described in RFC 2119 [RFC2119].
 >
 >
 > 1.   Introduction
 >
 >    The standard MPLS encapsulations have no explicit protocol
 >    identifier. In order for a pseudo wire (PW) [RFC3985] to operate
 >    correctly over an MPLS packet switched network (PSN) that performs
 >    MPLS payload inspection, a PW packet must not appear to the LSR as
 >    if it were an IP packet [BCP]. An example of an LSR that performs
 >    MPLS payload inspection is one that is performing equal-cost
 >    multiple-path load-balancing (ECMP) [RFC2992]. If ECMP were
 >    performed on PWE3 packets, the packets in the PW may not all follow
 >    the same path through the PSN. This may result in misordered packet
 >    delivery to the egress PE. The inability to ensure that all packets
 >    belonging to a PW follow the same path may also prevent the PW OAM
 >    [VCCV] mechanism from correctly monitoring the PW.
 >
 >    This draft specifies how a PW header distinguishes a PW payload from
 >    an IP payload carried over an MPLS PSN.
 >
 > 2.   PWE3 Packet Identification
 >
 >    All IP packets [RFC791][RFC1883] start with a version number that is
 >    checked by LSRs performing MPLS payload inspection. To prevent the
 >    incorrect processing of packets carried within a PW, PW packets
 >    carried over an MPLS PSN SHOULD NOT start with the value 4 (IPv4) or
 >    the value 6 (IPv6) in the first nibble [BCP], as those are assumed
 >    to carry normal IP payloads.

Mark> Why not specify a MUST NOT here?

Luca> Some of the TDM PWs might start with a 4, as they do not have a
Luca> conformant CW.

So they are non-conformant and it should be duly noted. I don't think that just 
because the TDM specs happen to already be in violation we should relax the 
requirement for all. If the correct recommendation is that 4 and 6 can break 
ECMP, then go ahead and make it a MUST NOT here, and let the non-comformant PWs 
state in their doc that they are non-conformant and could possibly cause 
problems with ECMP. Otherwise, I think the issue may get lost.

I don't want to rathole on this. So, if it has already been hashed out in the WG 
extensively, I'll take a call from the chairs on this. But, it seems to me that 
since this is a basic construct for a lot of other documents, the fundamentals 
should be defined correctly.

 >
 >    This document defines a PW header and two general formats of that
 >    header. These two formats are the PW MPLS Control Word (PWMCW) used
 >    for data passing across the PW, and a PW Associated Channel Header
 >    (PW-ACH) that can be used for functions such as OAM.
 >
 >    If the first nibble of a PWE3 packet carried over an MPLS PSN has a
 >    value of 0, it starts with a PWMCW. If the first nibble of a packet
 >    carried over an MPLS PSN has a value of 1, it starts with a PW-ACH.
 >    The use of any other first nibble value for a PWE3 packet carried
 >    over an MPLS PSN is deprecated.
 >
 >    A PW carried over an MPLS PSN that uses the contents of the MPLS
 >    payload to select the ECMP path SHOULD employ the PW MPLS Control
 >    Word described in Section 3 for data, and the PW Associated Channel
 >    Header described in Section 4 for channel associated traffic. These
 >    Control Words MUST immediately follow the bottom of the MPLS label
 >    stack.
 >
 >
 >
 >
 >
 >
 >
 > Bryant et al            Expires September 2005               [Page 2]
 > 
 >
 >
 >
 > INTERNET DRAFT   PWE3 Control Word for use over an MPLS PSN   Mar 2005
 >
 > 3.   Generic PW MPLS Control Word
 >
 >    The Generic PW MPLS Control Word is shown in Figure 1.
 >
 >
 >     0                   1                   2                   3
 >     0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
 >    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
 >    |0 0 0 0|          Specified by PW Encapsulation                |
 >    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
 >
 >          Figure 1: Generic PW MPLS Control Word
 >
 >
 >    The PW set-up protocol or configuration mechanism determines whether
 >    a PW uses a PW MPLS Control Word (PWMCW). Bits 0..3 differ from the
 >    first four bits of an IP packet [BCP] and hence provide the
 >    necessary MPLS payload discrimination.
 >
 >    When a PWMCW is used, it MUST adhere to the Generic MPLS Control
 >    Word format as illustrated in Figure 1 above. It is however strongly
 >    recommended that it also follows the following format:

Mark> Is this a capital RECOMMENDED or SHOULD?

Luca> yes i think it needs a capital RECOMMENDED.

 >
 >
 >     0                   1                   2                   3
 >     0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
 >    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
 >    |0 0 0 0| Flags |FRG|  Length   | Sequence Number               |
 >    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
 >
 >         Figure 2: PW Preferred MPLS Control Word
 >
 >    The meaning of the fields of the PW Preferred MPLS Control Word
 >    (Figure 2) are as follows:
 >
 >    Flags (bits 4 to 7):
 >
 >           These bits are available for per-payload signalling.  Their
 >           definition is encapsulation specific as defined in
 >           [pointer?].

Mark> "pointer?" needs to be defined.

Luca> omission - this needs to be removed ....

 >
 >    FRG (bits 8 and 9):
 >
 >           These bits are used when fragmenting a PW payload. Their use
 >           is described in [FRAG] which is currently a work in progress.
 >           When the PW is of a type that will never need payload
 >           fragmentation, these bits may be used as general purpose
 >           flags.
 >
 >    Length (bits 10 to 15):
 >
 >
 >
 >
 >
 >
 > Bryant et al            Expires September 2005               [Page 3]
 > 
 >
 >
 >
 > INTERNET DRAFT   PWE3 Control Word for use over an MPLS PSN   Mar 2005
 >
 >           The value of the length field, if non-zero, can be used to
 >           remove any padding added by the PSN. If the entire packet
 >           length is less than 64 bytes, the length field MUST be set to
 >           the length of the PW payload plus the length of the control
 >           word. Otherwise it MUST be set to zero.
 >
 >           If a non-zero length field is received, the PW payload MUST
 >           be trimmed if required.

Mark> What is meant by "if required" - To me, this either MUST be trimmed or
Mark> not (no need to suggest an implementation loophole if none should exist).
Mark>

Luca> no, it means that the payload might already be the correct length ,
Luca> hence it might not need to be trimmed....
Luca> Not all short packet have to be padded , some media do not require
Luca> padding ....

So, just to be sure, we are stating that the payload length field MUST be set 
for < 64 byte payloads regardless of media type, but there is an "if required" 
on the trimming when receiving a non-zero length as some media types do not need 
the length field.

Yes, I understand the issue here is ethernet, I'm not debating when it is 
necessary or not. I simply find it odd that we have an exception clause on the 
trimming, but not on the setting of the field.

Also, I think it might be helpful for interoperability to point out ethernet as 
an example of when this field would be used. This shouldn't take more than a 
sentence or two and perhaps a reference.

 >
 >    Sequence number (Bit 16 to 31):
 >
 >           If the sequence number is not used, it is set to zero by the
 >           sender and ignored by the receiver.  Otherwise it specifies
 >           the sequence number of a packet.  A circular list of sequence
 >           numbers is used.  A sequence number takes a value from 1 to
 >           65535 (2**16-1). The sequence number window size for packet
 >           acceptance is dependent on the parameters of both the PW and
 >           the MPLS PSN, and SHOULD be configurable. The mechanism used
 >           by the decapsulating PE to syncronise the expected sequence
 >           number with the received sequence number is implementation
 >           dependent.

Mark> s/syncronise/synchronize

Mark> That's two I caught, there must be more. Please run the doc through a
Mark> spell checker.

 >
 > 4.   PW Associated Channel
 >
 >    For some features of PWs, such as OAM, an associated channel is
 >    required. An associated channel is a channel that is multiplexed
 >    over the PW so that it follows exactly the same path through the PSN
 >    as the PW. Note that the use of the term "channel" is not a "PW
 >    channel type" as used in subsection 5.1.2 of [RFC3985]
 >
 >    When MPLS is used as the PSN, the PW Associated Channel is
 >    identified by the following header:
 >
 >    0                   1                   2                   3
 >    0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
 >    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
 >    |0 0 0 1| FmtID |   Reserved    |         Channel Type          |
 >    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
 >
 >        Figure 3: PW Associated Channel Header
 >
 >    The meaning of the fields in the PW Associated Channel Header
 >    (Figure 3) are as follows:
 >
 >    FmtID:
 >
 >           Format ID for the remaining 3 octets of the header. A FmtID
 >           of 0 indicates that the 3 octets are as shown in Figure 3.
 >
 >    Reserved:
 >
 >
 >
 >
 >
 >
 > Bryant et al            Expires September 2005               [Page 4]
 > 
 >
 >
 >
 > INTERNET DRAFT   PWE3 Control Word for use over an MPLS PSN   Mar 2005
 >
 >           Must be sent as 0, and ignored on reception.
 >
 >    Channel Type:
 >
 >           The PW Associated Channel Type is defined in the IANA PW
 >           Associated Channel Type registry [IANA].
 >
 >    Bits 0..3 MUST be 0x01, and hence differ from the first four bits of
 >    an IP packet [BCP]. This provides the necessary MPLS payload

Mark> The first bits being 0x01 also differ this payload from being a PW
Mark> payload.

My point here was simply that 0x01 does more than just differ this packet from 
being a non-IP packet. It also makes it differ from being a PWE3 data packet.


 >    discrimination.
 >
 >    Note that L2TPv3 [REFERENCE] has its own mechanisms for providing
 >    this associated channel, and is therefore out of the scope of this
 >    document.

Mark> Need to define REFERENCE (RFC3931).

 >
 > 5.   IANA considerations
 >
 >    IANA needs to set up a registry of "Pseudowire Associated Channel
 >    Types". These are 16-bit values. Registry entries are assigned by
 >    using the "IETF Consensus" policy defined in [RFC2434].

Mark> What about FMT IDs?

Luca> r

Looks like part of your response got cut off here.

 >
 > 6.   Security Considerations
 >
 >    An application using PW Associated Channel to provide an OAM [VCCV]
 >    or other message channel MUST be aware that this can potentially be
 >    misused. Any application using the Associated Channel must therefore
 >    fully consider the resultant security issues, and provide mechanisms
 >    to prevent an attacker from using this as a mechanism to disrupt the
 >    operation of the PW or the PE, and to stop this channel from being
 >    used as a conduit to deliver packets elsewhere.
 >
 >    If a PW has been configured to operate without a CW, the PW
 >    Associated Channel Type mechanism described in the document MUST NOT
 >    be used. This is to prevent user payloads being fabricated in such a
 >    way that they mimic the PW Associated Channel Header, and thereby
 >    provide a method of attacking the application that is using the
 >    Associated Channel.
 >
 >
 >
 > 7.   Acknowledgements
 >
 >    The authors wish to thank David Allan, Luca Martini, Thomas Nadeau
 >    and Mark Townsley for their input to this work.
 >
 > 8.   Intellectual Property Statement
 >
 >
 >    The IETF takes no position regarding the validity or scope of any
 >    Intellectual Property Rights or other rights that might be claimed
 >
 >
 >
 >
 >
 >
 > Bryant et al            Expires September 2005               [Page 5]
 > 
 >
 >
 >
 > INTERNET DRAFT   PWE3 Control Word for use over an MPLS PSN   Mar 2005
 >
 >    to pertain to the implementation or use of the technology described
 >    in this document or the extent to which any license under such
 >    rights might or might not be available; nor does it represent that
 >    it has made any independent effort to identify any such rights.
 >    Information on the procedures with respect to rights in RFC
 >    documents can be found in BCP 78 and BCP 79.
 >
 >    Copies of IPR disclosures made to the IETF Secretariat and any
 >    assurances of licenses to be made available, or the result of an
 >    attempt made to obtain a general license or permission for the use
 >    of such proprietary rights by implementers or users of this
 >    specification can be obtained from the IETF on-line IPR repository
 >    at http://www.ietf.org/ipr.
 >
 >    The IETF invites any interested party to bring to its attention any
 >    copyrights, patents or patent applications, or other proprietary
 >    rights that may cover technology that may be required to implement
 >    this standard.  Please address the information to the IETF at ietf-
 >    ipr@ietf.org.
 >
 >
 > 9.    Full copyright statement
 >
 >    Copyright (C) The Internet Society (2004). This document is subject
 >    to the rights, licenses and restrictions contained in BCP 78, and
 >    except as set forth therein, the authors retain all their rights.
 >
 >    This document and the information contained herein are provided on
 >    an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE
 >    REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE
 >    INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR
 >    IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
 >    THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
 >    WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
 >
 >
 >
 > 10.    Normative References
 >
 >    Internet-drafts are works in progress available from
 >    http://www.ietf.org/internet-drafts/
 >
 >    [RFC791]   RFC-791: DARPA Internet Program, Protocol
 >                Specification, ISI, September 1981.
 >
 >    [RFC1883]  RFC-1883: Internet Protocol, Version 6 (IPv6), S.
 >                Deering, et al, December 1995
 >
 >
 >
 >
 >
 >
 >
 >
 >
 > Bryant et al            Expires September 2005               [Page 6]
 > 
 >
 >
 >
 > INTERNET DRAFT   PWE3 Control Word for use over an MPLS PSN   Mar 2005
 >
 >
 >
 > 11.    Informative References
 >
 >
 >    Internet-drafts are works in progress available from
 >    <http://www.ietf.org/internet-drafts/>
 >
 >    [BCP]     Swallow, G. et al, "Avoiding Equal Cost Multipath
 >               Treatment in MPLS Networks", Internet Draft
 >               <draft-ietf-mpls-ecmp-bcp-00.txt>, September 2004,
 >               Work in Progress.
 >
 >    [FRAG]    Malis, A., Townsley, M., "PWE3 Fragmentation and
 >               Reassembly", Internet Draft, <draft-ietf-pwe3-
 >               fragmentation-08.txt>, February 2005, Work in
 >               Progress.
 >
 >    [IANA]    Martini, L., Townsley M., "IANA Allocations for
 >               pseudo Wire Edge to Edge Emulation (PWE3) ",
 >               Internet Draft, <draft-ietf-pwe3-iana-allocation-
 >               07.txt>, October 2004, Work in Progress.
 >
 >    [RFC2434] RFC-2434: Guidelines for Writing an IANA
 >               Considerations Section in RFCs, Narten, T.,
 >               Alvestrand, H., October 1998
 >
 >    [RFC2992] RFC-2992:  Analysis of an Equal-Cost Multi-Path
 >               Algorithm, C. Hopps, November 2000
 >    [RFC3985] RFC-3985: PWE3 Architecture, Bryant, S. ed., Pate,
 >               P. ed. , To be published.
 >    [VCCV]    Nadeau, T., Aggarwal, T., "Pseudo Wire (PW) Virtual
 >               Circuit Connection Verification (VCCV)", Internet
 >               Draft, <draft-ietf-pwe3-vccv-04.txt>, Feb. 2005,
 >               Work in Progress.

Mark> Line spacing above.

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


From pwe3-bounces@ietf.org  Thu Apr 14 03:23:04 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA10377
	for <pwe3-archive@ietf.org>; Thu, 14 Apr 2005 03:23:03 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DLyqn-00038h-R7
	for pwe3-archive@ietf.org; Thu, 14 Apr 2005 03:33:22 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DLySq-0000Kd-Ns; Thu, 14 Apr 2005 03:08:36 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DLySl-0000JK-Oo
	for pwe3@megatron.ietf.org; Thu, 14 Apr 2005 03:08:32 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA09432
	for <pwe3@ietf.org>; Thu, 14 Apr 2005 03:08:21 -0400 (EDT)
Received: from mx100.qos.net.il ([80.74.96.6])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DLycZ-0002jQ-MP
	for pwe3@ietf.org; Thu, 14 Apr 2005 03:18:40 -0400
Received: from tlv1.axerra.com (tlv1.axerra.com [80.74.100.68])
	by mx100.qos.net.il (8.12.8/8.12.8) with ESMTP id j3E73XtA030048;
	Thu, 14 Apr 2005 10:03:34 +0300
Received: by TLV1 with Internet Mail Service (5.5.2653.19)
	id <GZ9PCRCJ>; Thu, 14 Apr 2005 10:05:46 +0200
Message-ID: <AF5018AC03D1D411ABB70002A5091326015E1D75@TLV1>
From: Sasha Vainshtein <Sasha@AXERRA.com>
To: "'W. Mark Townsley'" <townsley@cisco.com>
Subject: RE: [PWE3] AD Review of draft-ietf-pwe3-cw-03.txt
Date: Thu, 14 Apr 2005 10:05:45 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="ISO-8859-8"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b22590c27682ace61775ee7b453b40d3
Cc: "Yaakov Stein \(E-mail\)" <yaakov_s@rad.com>,
        "PWE3 WG \(E-mail\)" <pwe3@ietf.org>, Danny McPherson <danny@tcb.net>,
        "Andrew G. Malis \(E-mail\)" <Andy.Malis@tellabs.com>,
        "Ron Cohen \(E-mail\)" <ronc@lyciumnetworks.com>,
        Luca Martini <lmartini@cisco.com>, Stewart Bryant <stbryant@cisco.com>
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=subscribe>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org
X-Spam-Score: 2.5 (++)
X-Scan-Signature: b1c41982e167b872076d0018e4e1dc3c

Mark and all,
Please see some comments inline below.
I have snipped the portions of the text that are not relevant for these
comments.

Regards,
                                  Sasha Vainshtein
email:                         sasha@axerra.com <mailto:sasha@axerra.com> 
phone:                       +972-3-7569993 (office)
fax:                            +972-3-6487779
mobile:                      +972-52-8674833 


> -----Original Message-----
> From: W. Mark Townsley [mailto:townsley@cisco.com]
> Sent: Wednesday, April 13, 2005 10:28 PM
> To: Luca Martini
> Cc: Stewart Bryant; PWE3 WG (E-mail); Danny McPherson
> Subject: Re: [PWE3] AD Review of draft-ietf-pwe3-cw-03.txt
> 
... snipped 
>  > 2.   PWE3 Packet Identification
>  >
>  >    All IP packets [RFC791][RFC1883] start with a version 
>  >    number that is
>  >    checked by LSRs performing MPLS payload inspection. To 
>  >    prevent the
>  >    incorrect processing of packets carried within a PW, PW packets
>  >    carried over an MPLS PSN SHOULD NOT start with the 
>  >    value 4 (IPv4) or the value 6 (IPv6) in the first nibble [BCP], 
>  >    as those are assumed to carry normal IP payloads.
> 
> Mark> Why not specify a MUST NOT here?
> 
> Luca> Some of the TDM PWs might start with a 4, as they do not have a
> Luca> conformant CW.
> So they are non-conformant and it should be duly noted. I 
> don't think that just because the TDM specs happen to already 
> be in violation we should relax the requirement for all. 
>
[Sasha]AFAIK the only PW that still uses a non-comformant CW
[Sasha]is CEP (draft-ietf-pwe3-sonet-10.txt), and this document
[Sasha]both states the problem and describes a solution.
[Sasha](Low-rate) TDM PW encapsulations described in the SAToP
[Sasha](draft-ietf-pwe3-satop-01.txt), CESoPSN 
[Sasha](draft-ietf-pwe3-cesopsn-02.txt) and TDMoIP 
(draft-ietf-pwe3-tdmoip-03.txt) docs all use a conformant CW. 
[Sasha]Hence I would say that TDM PWs are NOT in violation and
[Sasha]should not be cited as the reason to relax a requirement
[Sasha]if such is deemed necessary.
> 
... snipped
>  > 3.   Generic PW MPLS Control Word
>  >
>  >    Length (bits 10 to 15):
>  >           The value of the length field, if non-zero, can 
>  >           be used to
>  >           remove any padding added by the PSN. If the entire packet
>  >           length is less than 64 bytes, the length field 
>  >           MUST be set to
>  >           the length of the PW payload plus the length of 
>  >           the control word. Otherwise it MUST be set to zero.
>  >
>  >           If a non-zero length field is received, the PW 
>  >           payload MUST be trimmed if required.
> 
> Mark> What is meant by "if required" - To me, this either 
> MUST be trimmed or
> Mark> not (no need to suggest an implementation loophole if 
> none should exist).
> Mark>
> 
> Luca> no, it means that the payload might already be the 
> correct length ,
> Luca> hence it might not need to be trimmed....
> Luca> Not all short packet have to be padded , some media do 
> not require
> Luca> padding ....
> 
> So, just to be sure, we are stating that the payload length 
> field MUST be set 
> for < 64 byte payloads regardless of media type, but there is 
> an "if required" 
> on the trimming when receiving a non-zero length as some 
> media types do not need 
> the length field.
>
[Sasha] I have commented on this subject already.

[Sasha]Neither this draft nor any service-specific
[Sasha]draft explains how to treat the following situations
[Sasha](LEN_CW is the value of the Length field and LEN_L2
[Sasha]is the length of the MPLS payload derived from the Layer 2
[Sasha]lentgh after stripping the Layer 2 header and the label stack,
[Sasha]MAX_PAD = 46 is the max. padding that can be added by Ethernet):
[Sasha]
[Sasha](1) (LEN_CW == 0) && (LEN_L2 < 64)       
[Sasha](2) (LEN_CW > 0) && (LEN_L2 < LEN_CW)
[Sasha](3) (LEN_CW > 0) && (LEN_L2 > LEN_CW + MAX_PAD) 
[Sasha]
[Sasha]To me all the cases above look like malformed packets to be
[Sasha] silently discarded...
[Sasha]Note that in these terms  "trimming is not
[Sasha]required" means that (LEN_CW > 0) && (LEN_L2 == LEN_CW).
[Sasha]I'd also say that "trimming is required" means

[Sasha](LEN_CW > 0) && (LEN_L2 > LEN_CW) && (LEN_L2 <= LEN_CW + MAX_PAD)

[Sasha]Maybe it is worth explicitly specifying these rules?
>
> Yes, I understand the issue here is ethernet, I'm not 
> debating when it is 
> necessary or not. I simply find it odd that we have an 
> exception clause on the 
> trimming, but not on the setting of the field.
> 
> Also, I think it might be helpful for interoperability to 
> point out ethernet as 
> an example of when this field would be used. This shouldn't 
> take more than a 
> sentence or two and perhaps a reference.
>
[Sasha] IMO it is also worth noting that any hypothetical media
that pads L2 frames to sizes exceeding 64 would not be suitable
for carrying MPLS PWs oaver it. 
>
... snipped to the end ...

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


From pwe3-bounces@ietf.org  Thu Apr 14 09:35:38 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA11273
	for <pwe3-archive@ietf.org>; Thu, 14 Apr 2005 09:35:38 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DM4fP-0007ab-5f
	for pwe3-archive@ietf.org; Thu, 14 Apr 2005 09:46:00 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DM4Sh-0000Lt-Pg; Thu, 14 Apr 2005 09:32:51 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DLdfb-0003kj-7t
	for pwe3@megatron.ietf.org; Wed, 13 Apr 2005 04:56:23 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA06826
	for <pwe3@ietf.org>; Wed, 13 Apr 2005 04:56:10 -0400 (EDT)
Received: from web8506.mail.in.yahoo.com ([202.43.219.168])
	by ietf-mx.ietf.org with smtp (Exim 4.33) id 1DLdp9-0000EE-7i
	for pwe3@ietf.org; Wed, 13 Apr 2005 05:06:18 -0400
Received: (qmail 48361 invoked by uid 60001); 13 Apr 2005 08:55:59 -0000
Message-ID: <20050413085559.48358.qmail@web8506.mail.in.yahoo.com>
Received: from [210.18.74.42] by web8506.mail.in.yahoo.com via HTTP;
	Wed, 13 Apr 2005 09:55:59 BST
Date: Wed, 13 Apr 2005 09:55:59 +0100 (BST)
From: manomugdha biswas <manomugdhab@yahoo.co.in>
To: pwe3@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
X-Spam-Score: 0.1 (/)
X-Scan-Signature: de4f315c9369b71d7dd5909b42224370
Content-Transfer-Encoding: 8bit
X-Mailman-Approved-At: Thu, 14 Apr 2005 09:32:48 -0400
Subject: [PWE3] martini test topology
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=subscribe>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab
Content-Transfer-Encoding: 8bit

Hi,
I am reading some martini drafts in my own interest.
For this if I get some tests which deal about martini
draft (e.g. ethernet encap)it will be a great help.
Actually I want to see the topology for this. If you
have some topology diagram and some tests please send
me.

Regards,
Manomugdha


Manomugdha Biswas

________________________________________________________________________
Yahoo! India Matrimony: Find your life partner online
Go to: http://yahoo.shaadi.com/india-matrimony

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


From pwe3-bounces@ietf.org  Thu Apr 14 10:16:26 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA16712
	for <pwe3-archive@ietf.org>; Thu, 14 Apr 2005 10:16:26 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DM5Iv-00015M-6G
	for pwe3-archive@ietf.org; Thu, 14 Apr 2005 10:26:49 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DM51k-00071W-BD; Thu, 14 Apr 2005 10:09:04 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DM51h-00070o-Sw
	for pwe3@megatron.ietf.org; Thu, 14 Apr 2005 10:09:02 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA15443
	for <pwe3@ietf.org>; Thu, 14 Apr 2005 10:08:59 -0400 (EDT)
Received: from rtp-iport-1.cisco.com ([64.102.122.148])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DM5Bi-0000id-24
	for pwe3@ietf.org; Thu, 14 Apr 2005 10:19:22 -0400
Received: from rtp-core-1.cisco.com (64.102.124.12)
	by rtp-iport-1.cisco.com with ESMTP; 14 Apr 2005 10:18:16 -0400
X-IronPort-AV: i="3.92,102,1112587200"; 
	d="scan'208"; a="44577602:sNHT95249811088"
Received: from fruitpie.cisco.com (IDENT:mirapoint@fruitpie.cisco.com
	[64.102.16.27])
	by rtp-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id j3EE8Cbb020224; 
	Thu, 14 Apr 2005 10:08:12 -0400 (EDT)
Received: from [10.83.1.102] (rtp-townsley-vpn5.cisco.com [10.83.1.102])
	by fruitpie.cisco.com (MOS 3.4.6-GR) with SMTP id BGS03440;
	Thu, 14 Apr 2005 07:08:09 -0700 (PDT)
Message-ID: <425E7948.6010400@cisco.com>
Date: Thu, 14 Apr 2005 10:08:08 -0400
From: "W. Mark Townsley" <townsley@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
	rv:1.7) Gecko/20040616
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Sasha Vainshtein <Sasha@AXERRA.com>
Subject: Re: [PWE3] AD Review of draft-ietf-pwe3-cw-03.txt
References: <AF5018AC03D1D411ABB70002A5091326015E1D75@TLV1>
In-Reply-To: <AF5018AC03D1D411ABB70002A5091326015E1D75@TLV1>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 6ffdee8af20de249c24731d8414917d3
Content-Transfer-Encoding: 7bit
Cc: "Yaakov Stein \(E-mail\)" <yaakov_s@rad.com>,
        "PWE3 WG \(E-mail\)" <pwe3@ietf.org>, Danny McPherson <danny@tcb.net>,
        "Andrew G. Malis \(E-mail\)" <Andy.Malis@tellabs.com>,
        "Ron Cohen \(E-mail\)" <ronc@lyciumnetworks.com>,
        Luca Martini <lmartini@cisco.com>, Stewart Bryant <stbryant@cisco.com>
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=subscribe>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8fbbaa16f9fd29df280814cb95ae2290
Content-Transfer-Encoding: 7bit


Thanks Sasha... Responses inline..

Sasha Vainshtein wrote:

>> >    All IP packets [RFC791][RFC1883] start with a version 
>> >    number that is
>> >    checked by LSRs performing MPLS payload inspection. To 
>> >    prevent the
>> >    incorrect processing of packets carried within a PW, PW packets
>> >    carried over an MPLS PSN SHOULD NOT start with the 
>> >    value 4 (IPv4) or the value 6 (IPv6) in the first nibble [BCP], 
>> >    as those are assumed to carry normal IP payloads.
>>
>>Mark> Why not specify a MUST NOT here?
>>
>>Luca> Some of the TDM PWs might start with a 4, as they do not have a
>>Luca> conformant CW.
>>So they are non-conformant and it should be duly noted. I 
>>don't think that just because the TDM specs happen to already 
>>be in violation we should relax the requirement for all. 
>>
> 
> [Sasha]AFAIK the only PW that still uses a non-comformant CW
> [Sasha]is CEP (draft-ietf-pwe3-sonet-10.txt), and this document
> [Sasha]both states the problem and describes a solution.
> [Sasha](Low-rate) TDM PW encapsulations described in the SAToP
> [Sasha](draft-ietf-pwe3-satop-01.txt), CESoPSN 
> [Sasha](draft-ietf-pwe3-cesopsn-02.txt) and TDMoIP 
> (draft-ietf-pwe3-tdmoip-03.txt) docs all use a conformant CW. 
> [Sasha]Hence I would say that TDM PWs are NOT in violation and
> [Sasha]should not be cited as the reason to relax a requirement
> [Sasha]if such is deemed necessary.

Then in your mind we can use a MUST NOT here in the CW spec?

> 
> ... snipped
> 
>> > 3.   Generic PW MPLS Control Word
>> >
>> >    Length (bits 10 to 15):
>> >           The value of the length field, if non-zero, can 
>> >           be used to
>> >           remove any padding added by the PSN. If the entire packet
>> >           length is less than 64 bytes, the length field 
>> >           MUST be set to
>> >           the length of the PW payload plus the length of 
>> >           the control word. Otherwise it MUST be set to zero.
>> >
>> >           If a non-zero length field is received, the PW 
>> >           payload MUST be trimmed if required.
>>
>>Mark> What is meant by "if required" - To me, this either 
>>MUST be trimmed or
>>Mark> not (no need to suggest an implementation loophole if 
>>none should exist).
>>Mark>
>>
>>Luca> no, it means that the payload might already be the 
>>correct length ,
>>Luca> hence it might not need to be trimmed....
>>Luca> Not all short packet have to be padded , some media do 
>>not require
>>Luca> padding ....
>>
>>So, just to be sure, we are stating that the payload length 
>>field MUST be set 
>>for < 64 byte payloads regardless of media type, but there is 
>>an "if required" 
>>on the trimming when receiving a non-zero length as some 
>>media types do not need 
>>the length field.
>>
> 
> [Sasha] I have commented on this subject already.
> 
> [Sasha]Neither this draft nor any service-specific
> [Sasha]draft explains how to treat the following situations
> [Sasha](LEN_CW is the value of the Length field and LEN_L2
> [Sasha]is the length of the MPLS payload derived from the Layer 2
> [Sasha]lentgh after stripping the Layer 2 header and the label stack,
> [Sasha]MAX_PAD = 46 is the max. padding that can be added by Ethernet):
> [Sasha]
> [Sasha](1) (LEN_CW == 0) && (LEN_L2 < 64)       
> [Sasha](2) (LEN_CW > 0) && (LEN_L2 < LEN_CW)
> [Sasha](3) (LEN_CW > 0) && (LEN_L2 > LEN_CW + MAX_PAD) 
> [Sasha]
> [Sasha]To me all the cases above look like malformed packets to be
> [Sasha] silently discarded...

I'm not sure the document needs to specify all possible error conditions. It 
would certainly be nice, but I'm not sure it is 100% necessary.

> [Sasha]Note that in these terms  "trimming is not
> [Sasha]required" means that (LEN_CW > 0) && (LEN_L2 == LEN_CW).
> [Sasha]I'd also say that "trimming is required" means
> 
> [Sasha](LEN_CW > 0) && (LEN_L2 > LEN_CW) && (LEN_L2 <= LEN_CW + MAX_PAD)
> 
> [Sasha]Maybe it is worth explicitly specifying these rules?

Perhaps so. My concern was a bit less comprehensive, but you make a good point. 
I'll wait to hear other opinions if there are any...

> 
>>Yes, I understand the issue here is ethernet, I'm not 
>>debating when it is 
>>necessary or not. I simply find it odd that we have an 
>>exception clause on the 
>>trimming, but not on the setting of the field.
>>
>>Also, I think it might be helpful for interoperability to 
>>point out ethernet as 
>>an example of when this field would be used. This shouldn't 
>>take more than a 
>>sentence or two and perhaps a reference.
>>
> 
> [Sasha] IMO it is also worth noting that any hypothetical media
> that pads L2 frames to sizes exceeding 64 would not be suitable
> for carrying MPLS PWs oaver it. 

Yes, I agree.

- Mark

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


From pwe3-bounces@ietf.org  Thu Apr 14 10:19:18 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA17192
	for <pwe3-archive@ietf.org>; Thu, 14 Apr 2005 10:19:18 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DM5Lg-0001F0-U1
	for pwe3-archive@ietf.org; Thu, 14 Apr 2005 10:29:41 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DM5BA-0000ZN-8U; Thu, 14 Apr 2005 10:18:48 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DM5B7-0000YQ-3b
	for pwe3@megatron.ietf.org; Thu, 14 Apr 2005 10:18:46 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA17086
	for <pwe3@ietf.org>; Thu, 14 Apr 2005 10:18:35 -0400 (EDT)
Received: from mx100.qos.net.il ([80.74.96.6])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DM5Kx-0001D3-TY
	for pwe3@ietf.org; Thu, 14 Apr 2005 10:28:57 -0400
Received: from tlv1.axerra.com (tlv1.axerra.com [80.74.100.68])
	by mx100.qos.net.il (8.12.8/8.12.8) with ESMTP id j3EEClae006222;
	Thu, 14 Apr 2005 17:12:48 +0300
Received: by TLV1 with Internet Mail Service (5.5.2653.19)
	id <GZ9PCR88>; Thu, 14 Apr 2005 17:15:01 +0200
Message-ID: <AF5018AC03D1D411ABB70002A5091326015E1D7E@TLV1>
From: Sasha Vainshtein <Sasha@AXERRA.com>
To: "'W. Mark Townsley'" <townsley@cisco.com>
Subject: RE: [PWE3] AD Review of draft-ietf-pwe3-cw-03.txt
Date: Thu, 14 Apr 2005 17:15:00 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="ISO-8859-8"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7e439b86d3292ef5adf93b694a43a576
Cc: "Yaakov Stein \(E-mail\)" <yaakov_s@rad.com>,
        "PWE3 WG \(E-mail\)" <pwe3@ietf.org>, Danny McPherson <danny@tcb.net>,
        "Andrew G. Malis \(E-mail\)" <Andy.Malis@tellabs.com>,
        "Ron Cohen \(E-mail\)" <ronc@lyciumnetworks.com>,
        Luca Martini <lmartini@cisco.com>, Stewart Bryant <stbryant@cisco.com>
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=subscribe>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org
X-Spam-Score: 2.5 (++)
X-Scan-Signature: 25eb6223a37c19d53ede858176b14339

Mark (and all),
Thank you for a prompt response.
Please see a few answers inline below.

Regards,
                                  Sasha Vainshtein
email:                         sasha@axerra.com <mailto:sasha@axerra.com> 
phone:                       +972-3-7569993 (office)
fax:                            +972-3-6487779
mobile:                      +972-52-8674833 


> -----Original Message-----
> From: W. Mark Townsley [mailto:townsley@cisco.com]
> Sent: Thursday, April 14, 2005 4:08 PM
> To: Sasha Vainshtein
> Cc: Stewart Bryant; PWE3 WG (E-mail); Danny McPherson; Luca 
> Martini; Ron Cohen (E-mail); Yaakov Stein (E-mail); Andrew G. 
> Malis (E-mail)
> Subject: Re: [PWE3] AD Review of draft-ietf-pwe3-cw-03.txt
> 
> 
> 
> Thanks Sasha... Responses inline..
> 
> Sasha Vainshtein wrote:
> 
> >> >    All IP packets [RFC791][RFC1883] start with a version 
> >> >    number that is
> >> >    checked by LSRs performing MPLS payload inspection. To 
> >> >    prevent the
> >> >    incorrect processing of packets carried within a PW, 
> PW packets
> >> >    carried over an MPLS PSN SHOULD NOT start with the 
> >> >    value 4 (IPv4) or the value 6 (IPv6) in the first 
> nibble [BCP], 
> >> >    as those are assumed to carry normal IP payloads.
> >>
> >>Mark> Why not specify a MUST NOT here?
> >>
> >>Luca> Some of the TDM PWs might start with a 4, as they do 
> not have a
> >>Luca> conformant CW.
> >>So they are non-conformant and it should be duly noted. I 
> >>don't think that just because the TDM specs happen to already 
> >>be in violation we should relax the requirement for all. 
> >>
> > 
> > [Sasha]AFAIK the only PW that still uses a non-comformant CW
> > [Sasha]is CEP (draft-ietf-pwe3-sonet-10.txt), and this document
> > [Sasha]both states the problem and describes a solution.
> > [Sasha](Low-rate) TDM PW encapsulations described in the SAToP
> > [Sasha](draft-ietf-pwe3-satop-01.txt), CESoPSN 
> > [Sasha](draft-ietf-pwe3-cesopsn-02.txt) and TDMoIP 
> > (draft-ietf-pwe3-tdmoip-03.txt) docs all use a conformant CW. 
> > [Sasha]Hence I would say that TDM PWs are NOT in violation and
> > [Sasha]should not be cited as the reason to relax a requirement
> > [Sasha]if such is deemed necessary.
> 
> Then in your mind we can use a MUST NOT here in the CW spec?
>
[Sasha] I do not see any problem with that.  
>
> > 
> > ... snipped
> > 
> >> > 3.   Generic PW MPLS Control Word
> >> >
> >> >    Length (bits 10 to 15):
> >> >           The value of the length field, if non-zero, can 
> >> >           be used to
> >> >           remove any padding added by the PSN. If the 
> entire packet
> >> >           length is less than 64 bytes, the length field 
> >> >           MUST be set to
> >> >           the length of the PW payload plus the length of 
> >> >           the control word. Otherwise it MUST be set to zero.
> >> >
> >> >           If a non-zero length field is received, the PW 
> >> >           payload MUST be trimmed if required.
> >>
> >>Mark> What is meant by "if required" - To me, this either 
> >>MUST be trimmed or
> >>Mark> not (no need to suggest an implementation loophole if 
> >>none should exist).
> >>Mark>
> >>
> >>Luca> no, it means that the payload might already be the 
> >>correct length ,
> >>Luca> hence it might not need to be trimmed....
> >>Luca> Not all short packet have to be padded , some media do 
> >>not require
> >>Luca> padding ....
> >>
> >>So, just to be sure, we are stating that the payload length 
> >>field MUST be set 
> >>for < 64 byte payloads regardless of media type, but there is 
> >>an "if required" 
> >>on the trimming when receiving a non-zero length as some 
> >>media types do not need 
> >>the length field.
> >>
> > 
> > [Sasha] I have commented on this subject already.
> > 
> > [Sasha]Neither this draft nor any service-specific
> > [Sasha]draft explains how to treat the following situations
> > [Sasha](LEN_CW is the value of the Length field and LEN_L2
> > [Sasha]is the length of the MPLS payload derived from the Layer 2
> > [Sasha]lentgh after stripping the Layer 2 header and the 
> label stack,
> > [Sasha]MAX_PAD = 46 is the max. padding that can be added 
> by Ethernet):
> > [Sasha]
> > [Sasha](1) (LEN_CW == 0) && (LEN_L2 < 64)       
> > [Sasha](2) (LEN_CW > 0) && (LEN_L2 < LEN_CW)
> > [Sasha](3) (LEN_CW > 0) && (LEN_L2 > LEN_CW + MAX_PAD) 
> > [Sasha]
> > [Sasha]To me all the cases above look like malformed packets to be
> > [Sasha] silently discarded...
> 
> I'm not sure the document needs to specify all possible error 
> conditions. It 
> would certainly be nice, but I'm not sure it is 100% necessary.
> 
> > [Sasha]Note that in these terms  "trimming is not
> > [Sasha]required" means that (LEN_CW > 0) && (LEN_L2 == LEN_CW).
> > [Sasha]I'd also say that "trimming is required" means
> > 
> > [Sasha](LEN_CW > 0) && (LEN_L2 > LEN_CW) && (LEN_L2 <= 
> LEN_CW + MAX_PAD)
> > 
> > [Sasha]Maybe it is worth explicitly specifying these rules?
> 
> Perhaps so. My concern was a bit less comprehensive, but you 
> make a good point. 
> I'll wait to hear other opinions if there are any...
[Sasha] Basically I have written this text to explain 
that "is required" is ambiguous, and IMO your concern 
was exactly about that. How to make it unambiguous is
a different issue.
> 
> > 
> >>Yes, I understand the issue here is ethernet, I'm not 
> >>debating when it is 
> >>necessary or not. I simply find it odd that we have an 
> >>exception clause on the 
> >>trimming, but not on the setting of the field.
> >>
> >>Also, I think it might be helpful for interoperability to 
> >>point out ethernet as 
> >>an example of when this field would be used. This shouldn't 
> >>take more than a 
> >>sentence or two and perhaps a reference.
> >>
> > 
> > [Sasha] IMO it is also worth noting that any hypothetical media
> > that pads L2 frames to sizes exceeding 64 would not be suitable
> > for carrying MPLS PWs oaver it. 
> 
> Yes, I agree.
> 
> - Mark
> 

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


From pwe3-bounces@ietf.org  Thu Apr 14 14:46:05 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA11204
	for <pwe3-archive@ietf.org>; Thu, 14 Apr 2005 14:46:05 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DM9Vt-0004Bf-HK
	for pwe3-archive@ietf.org; Thu, 14 Apr 2005 14:56:29 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DM9Eu-0003ND-Lr; Thu, 14 Apr 2005 14:38:56 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DM9Es-0003Mb-Ed
	for pwe3@megatron.ietf.org; Thu, 14 Apr 2005 14:38:55 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA10352
	for <pwe3@ietf.org>; Thu, 14 Apr 2005 14:38:44 -0400 (EDT)
Received: from lml101.siteprotect.com ([66.113.136.249])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DM9Om-0003tN-Lf
	for pwe3@ietf.org; Thu, 14 Apr 2005 14:49:09 -0400
Received: from RONL (209-77-219-119.ded.pacbell.net [209.77.219.119] (may be
	forged))
	by lml101.siteprotect.com (8.9.3/8.9.3) with ESMTP id NAA18585;
	Thu, 14 Apr 2005 13:38:31 -0500
From: "Ron Cohen" <ronc@lyciumnetworks.com>
To: "'Sasha Vainshtein'" <Sasha@AXERRA.com>,
        "'W. Mark Townsley'" <townsley@cisco.com>
Subject: RE: [PWE3] AD Review of draft-ietf-pwe3-cw-03.txt
Date: Thu, 14 Apr 2005 21:34:10 +0300
Message-ID: <000401c54120$8e978220$0a00660a@il.reduxcom.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-8"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.4024
In-Reply-To: <AF5018AC03D1D411ABB70002A5091326015E1D7E@TLV1>
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0bb031f3a6fb29f760794ac9bf1997ae
Content-Transfer-Encoding: 7bit
Cc: "'Yaakov Stein \(E-mail\)'" <yaakov_s@rad.com>,
        "'PWE3 WG \(E-mail\)'" <pwe3@ietf.org>,
        "'Danny McPherson'" <danny@tcb.net>,
        "'Andrew G. Malis \(E-mail\)'" <Andy.Malis@tellabs.com>,
        "'Luca Martini'" <lmartini@cisco.com>,
        "'Stewart Bryant'" <stbryant@cisco.com>
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=subscribe>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8a85b14f27c9dcbe0719e27d46abc1f8
Content-Transfer-Encoding: 7bit

Hi,

The authors of CEP draft are working to align the CEP CW with the
recommended PW CW. 

However, I do see a problem with the current sequence number text.
The TDM emulation drafts all work on all values of the sequence number
and do not skip over the 0 value. This is aligned with the use of
sequence numbers in RTP. 

Best would be to mandate the use of the entire range of sequence numbers
when configured to set and track sequence numbers for all services (not
only TDM), and set the sequence number to zero when not used.

If no consensus on this change for all PW services can be agreed, I
suggest to change the current text in CW draft to something similar to
the following:

Sequence number (Bit 16 to 31): 

          The sequence number specifies the sequence number of a packet
          Usage of the sequence number field is OPTIONAL or MANDATORY 
          depending on the emulated service. For services for which 
          usage of the sequence number is MANDATORY, the sequence
          number cycles over all values. For services for which usage
          of the sequence number is OPTIONAL it MUST be set to zero
          by the sender and ignored by the receiver if not used.  
          Otherwise it MUST cycle from 1 to 65535 (2**16-1). The 
          sequence number window size for packet acceptance is dependent
          on the parameters of both the PW and 
          the MPLS PSN, and SHOULD be configurable. The mechanism used 
          by the decapsulating PE to syncronise the expected sequence 
          number with the received sequence number is implementation 
          dependent.   

Regards
Ron






-----Original Message-----
From: pwe3-bounces@ietf.org [mailto:pwe3-bounces@ietf.org] On Behalf Of
Sasha Vainshtein
Sent: Thursday, April 14, 2005 6:15 PM
To: 'W. Mark Townsley'
Cc: Yaakov Stein (E-mail); PWE3 WG (E-mail); Danny McPherson; Andrew G.
Malis (E-mail); Ron Cohen (E-mail); Luca Martini; Stewart Bryant
Subject: RE: [PWE3] AD Review of draft-ietf-pwe3-cw-03.txt


Mark (and all),
Thank you for a prompt response.
Please see a few answers inline below.

Regards,
                                  Sasha Vainshtein
email:                         sasha@axerra.com
<mailto:sasha@axerra.com> 
phone:                       +972-3-7569993 (office)
fax:                            +972-3-6487779
mobile:                      +972-52-8674833 


> -----Original Message-----
> From: W. Mark Townsley [mailto:townsley@cisco.com]
> Sent: Thursday, April 14, 2005 4:08 PM
> To: Sasha Vainshtein
> Cc: Stewart Bryant; PWE3 WG (E-mail); Danny McPherson; Luca
> Martini; Ron Cohen (E-mail); Yaakov Stein (E-mail); Andrew G. 
> Malis (E-mail)
> Subject: Re: [PWE3] AD Review of draft-ietf-pwe3-cw-03.txt
> 
> 
> 
> Thanks Sasha... Responses inline..
> 
> Sasha Vainshtein wrote:
> 
> >> >    All IP packets [RFC791][RFC1883] start with a version 
> >> >    number that is
> >> >    checked by LSRs performing MPLS payload inspection. To 
> >> >    prevent the
> >> >    incorrect processing of packets carried within a PW,
> PW packets
> >> >    carried over an MPLS PSN SHOULD NOT start with the 
> >> >    value 4 (IPv4) or the value 6 (IPv6) in the first
> nibble [BCP],
> >> >    as those are assumed to carry normal IP payloads.
> >>
> >>Mark> Why not specify a MUST NOT here?
> >>
> >>Luca> Some of the TDM PWs might start with a 4, as they do
> not have a
> >>Luca> conformant CW.
> >>So they are non-conformant and it should be duly noted. I
> >>don't think that just because the TDM specs happen to already 
> >>be in violation we should relax the requirement for all. 
> >>
> > 
> > [Sasha]AFAIK the only PW that still uses a non-comformant CW 
> > [Sasha]is CEP (draft-ietf-pwe3-sonet-10.txt), and this document 
> > [Sasha]both states the problem and describes a solution.
> > [Sasha](Low-rate) TDM PW encapsulations described in the SAToP 
> > [Sasha](draft-ietf-pwe3-satop-01.txt), CESoPSN
> > [Sasha](draft-ietf-pwe3-cesopsn-02.txt) and TDMoIP
> > (draft-ietf-pwe3-tdmoip-03.txt) docs all use a conformant CW. 
> > [Sasha]Hence I would say that TDM PWs are NOT in violation and
> > [Sasha]should not be cited as the reason to relax a requirement
> > [Sasha]if such is deemed necessary.
> 
> Then in your mind we can use a MUST NOT here in the CW spec?
>
[Sasha] I do not see any problem with that.  
>
> > 
> > ... snipped
> > 
> >> > 3.   Generic PW MPLS Control Word
> >> >
> >> >    Length (bits 10 to 15):
> >> >           The value of the length field, if non-zero, can 
> >> >           be used to
> >> >           remove any padding added by the PSN. If the
> entire packet
> >> >           length is less than 64 bytes, the length field 
> >> >           MUST be set to
> >> >           the length of the PW payload plus the length of 
> >> >           the control word. Otherwise it MUST be set to zero.
> >> >
> >> >           If a non-zero length field is received, the PW 
> >> >           payload MUST be trimmed if required.
> >>
> >>Mark> What is meant by "if required" - To me, this either
> >>MUST be trimmed or
> >>Mark> not (no need to suggest an implementation loophole if
> >>none should exist).
> >>Mark>
> >>
> >>Luca> no, it means that the payload might already be the
> >>correct length ,
> >>Luca> hence it might not need to be trimmed....
> >>Luca> Not all short packet have to be padded , some media do
> >>not require
> >>Luca> padding ....
> >>
> >>So, just to be sure, we are stating that the payload length
> >>field MUST be set 
> >>for < 64 byte payloads regardless of media type, but there is 
> >>an "if required" 
> >>on the trimming when receiving a non-zero length as some 
> >>media types do not need 
> >>the length field.
> >>
> > 
> > [Sasha] I have commented on this subject already.
> > 
> > [Sasha]Neither this draft nor any service-specific [Sasha]draft 
> > explains how to treat the following situations [Sasha](LEN_CW is the

> > value of the Length field and LEN_L2 [Sasha]is the length of the 
> > MPLS payload derived from the Layer 2 [Sasha]lentgh after stripping 
> > the Layer 2 header and the
> label stack,
> > [Sasha]MAX_PAD = 46 is the max. padding that can be added
> by Ethernet):
> > [Sasha]
> > [Sasha](1) (LEN_CW == 0) && (LEN_L2 < 64)       
> > [Sasha](2) (LEN_CW > 0) && (LEN_L2 < LEN_CW)
> > [Sasha](3) (LEN_CW > 0) && (LEN_L2 > LEN_CW + MAX_PAD)
> > [Sasha]
> > [Sasha]To me all the cases above look like malformed packets to be
> > [Sasha] silently discarded...
> 
> I'm not sure the document needs to specify all possible error
> conditions. It 
> would certainly be nice, but I'm not sure it is 100% necessary.
> 
> > [Sasha]Note that in these terms  "trimming is not [Sasha]required" 
> > means that (LEN_CW > 0) && (LEN_L2 == LEN_CW). [Sasha]I'd also say 
> > that "trimming is required" means
> > 
> > [Sasha](LEN_CW > 0) && (LEN_L2 > LEN_CW) && (LEN_L2 <=
> LEN_CW + MAX_PAD)
> > 
> > [Sasha]Maybe it is worth explicitly specifying these rules?
> 
> Perhaps so. My concern was a bit less comprehensive, but you
> make a good point. 
> I'll wait to hear other opinions if there are any...
[Sasha] Basically I have written this text to explain 
that "is required" is ambiguous, and IMO your concern 
was exactly about that. How to make it unambiguous is
a different issue.
> 
> > 
> >>Yes, I understand the issue here is ethernet, I'm not
> >>debating when it is 
> >>necessary or not. I simply find it odd that we have an 
> >>exception clause on the 
> >>trimming, but not on the setting of the field.
> >>
> >>Also, I think it might be helpful for interoperability to
> >>point out ethernet as 
> >>an example of when this field would be used. This shouldn't 
> >>take more than a 
> >>sentence or two and perhaps a reference.
> >>
> > 
> > [Sasha] IMO it is also worth noting that any hypothetical media that

> > pads L2 frames to sizes exceeding 64 would not be suitable for 
> > carrying MPLS PWs oaver it.
> 
> Yes, I agree.
> 
> - Mark
> 

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


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


From pwe3-bounces@ietf.org  Fri Apr 15 20:50:10 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA13929
	for <pwe3-archive@ietf.org>; Fri, 15 Apr 2005 20:50:10 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DMbg2-0004hr-3K
	for pwe3-archive@ietf.org; Fri, 15 Apr 2005 21:00:50 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DMbSl-0007H8-8V; Fri, 15 Apr 2005 20:47:07 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DMbSj-0007Gw-Ts
	for pwe3@megatron.ietf.org; Fri, 15 Apr 2005 20:47:05 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA13740
	for <pwe3@ietf.org>; Fri, 15 Apr 2005 20:47:04 -0400 (EDT)
From: ronc@lyciumnetworks.com
Received: from lml101.siteprotect.com ([66.113.136.249])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DMbd2-0004UM-4e
	for pwe3@ietf.org; Fri, 15 Apr 2005 20:57:44 -0400
Received: from vecchi (vecchi.siteprotect.com [66.113.136.10])
	by lml101.siteprotect.com (8.9.3/8.9.3) with ESMTP id TAA24451;
	Fri, 15 Apr 2005 19:46:56 -0500
Date: Fri, 15 Apr 2005 19:46:56 -0500
Message-Id: <200504160046.TAA24451@lml101.siteprotect.com>
To: pwe3@ietf.org
X-Mailer: mymail.siteprotect.com (user 67.126.114.123)
MIME-Version: 1.0
Content-Type: multipart/mixed;
	boundary="66.113.136.10.509.28367.1113612415.080.17500"
X-Spam-Score: 0.3 (/)
X-Scan-Signature: 2beba50d0fcdeee5f091c59f204d4365
Cc: ronc@lyciumnetworks.com
Subject: [PWE3] Proposed Changes to CEP
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: ronc@lyciumnetworks.com
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=subscribe>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org
X-Spam-Score: 0.3 (/)
X-Scan-Signature: 8f374d0786b25a451ef87d82c076f593

This is a multipart message in MIME format.

--66.113.136.10.509.28367.1113612415.080.17500
Content-Type: text/plain

Dear PWE3ers

Below is a proposal by CEP authors that aligns the CEP draft with draft-ietf-pwe3-cw-03.txt and with the other TDM emulation drafts. Please send your comments as soon as possible. If no substential comments are received in the coming week a new draft CEP-11 will be issued detailing these changes. New CEP header description is attached.

Proposed changes to CEP-10:

Changes summary:
1. CEP header: align with recommended control word. Use L and R
  bits similar for remote/forward defect indications. Use 16 bit
  sequence number, length and fragmentations bits. Shorten structure
  pointer from 13 to 12 bits supporting payload sizes up to 4096 bytes. 
2. Align LDP interface parameters with above changes. Align MIB
  with above changes
3. Remove L2TPv3 encapsulation (to be described in a separate
  draft at a later time)
4. Remove RTP encapsulation

Happy tax day
Ron

Ron Cohen
CTO
Resolute Networks
Redux and Lycium Unite 

--66.113.136.10.509.28367.1113612415.080.17500
Content-Type: text/plain;
    name="New CEP.txt"
Content-Description: New CEP.txt
Content-Disposition: attachment; filename="New CEP.txt"





CEP header


   The CEP control word has the following format:

     0                   1                   2                   3
     0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    |0|0|0|0|L|R|N|P|FRG|Length[0:5]|    Sequence Number[0:15]      |
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    |               Reserved                |Structure Pointer[0:11]|
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

                Figure 2 - CEP Control Word Format


   The above fields are defined as follows:

   L bit: CEP-AIS. This bit MUST be set to one to signal to the
   downstream PE that a failure condition has been detected on the
   attachment circuit.
   Failure conditions leading to generation of CEP-AIS and the
   mapping of CEP-AIS siganl on the downstream attachment
   circuit are described in section 6.

   R bit: CEP-RDI. This bit MUST be set to one to signal to the
   upstream PE that a loss of packet synchronization has occurred.
   This bit MUST be set to zero once packet synchronization is
   acquired.

   N and P bits: These bits are used to explicitly relay negative
   and positive pointer adjustments events across the PSN. The use
   of N and P bits is OPTIONAL. See section 8 for details.

   Table 2 describes the interpretation of N and P bits settings.

         +---+---+--------------------------------------+
         | N | P |         Interpretation               |
         +---+---+--------------------------------------+
         | 0 | 0 | No Pointer Changes                   |
         | 0 | 1 | Positive Pointer Adjustment          |
         | 1 | 0 | Negative Pointer Adjustment          |
         | 1 | 1 | Error Condition                      |
         +---+---+---+----------------------------------+

             Table 2 - Interpretation of N and P bits

   N and P bits MUST be set to 1 when L bit is set to 1.

   FRG bits: FRG bits MUST be set to zero by sender and ignored
   by receiver.
   SONET data is continuously fragmented into packets.
   The structure pointer field designates the offset between the 
   SONET SPE or VT structure and the packet boundary.

   Length [0:5]: The Length field, if non zero, indicates the
   length of the control word plus the length of the payload field.
   The Length field MUST be set if it is less or equal to 64 bytes
   and MUST be set to zero otherwise. In particular, if DBA mode
   is used, and the packet does not carry any payload, the Length
   field MUST be set to the control word length.

   Sequence Number [0:15]:  The packet sequence number
   MUST continuously cycle from 0 to 0xFFFF.  It is generated and
   processed in accordance with the rules established in [RFC1889].

   Structure Pointer [0:11]: The Structure Pointer MUST contain the
   offset of the first byte of the SONET structure within the packet
   payload. For SPE emulation, the structure pointer locates the J1
   byte within the CEP packet.  For VT emulation the structure
   pointer locates the V5 byte within the packet.  The structure
   pointer value is from 0 to 0xFFE, where 0 means the first byte
   after the CEP header. The Structure Pointer MUST be set to 0xFFF
   if a packet does not carry the J1 (or V5) byte.
   An arbitrary pointer change (NDF event) in the attachment circuit
   changes the offset of the SONET structure within the CEP packet
   and therefore changes the Structure Pointer value.

   Reserved Field: The reserved field MUST be set to zero by sender
   and ignored by receiver.

Ron Cohen
CTO
Resolute Networks
Redux and Lycium Unite


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

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

--66.113.136.10.509.28367.1113612415.080.17500--





From pwe3-bounces@ietf.org Sat Apr 16 15:18:56 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DMsoi-0007mX-Hv; Sat, 16 Apr 2005 15:18:56 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DMsog-0007ln-Ra
	for pwe3@megatron.ietf.org; Sat, 16 Apr 2005 15:18:55 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA28359
	for <pwe3@ietf.org>; Sat, 16 Apr 2005 15:18:50 -0400 (EDT)
Received: from mx100.qos.net.il ([80.74.96.6])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DMpmG-0004uY-Kp
	for pwe3@ietf.org; Sat, 16 Apr 2005 12:04:14 -0400
Received: from tlv1.axerra.com (tlv1.axerra.com [80.74.100.68])
	by mx100.qos.net.il (8.12.8/8.12.8) with ESMTP id j3GFmiae024193;
	Sat, 16 Apr 2005 18:48:45 +0300
Received: by TLV1 with Internet Mail Service (5.5.2653.19)
	id <GZ9PCVCN>; Sat, 16 Apr 2005 18:51:01 +0200
Message-ID: <AF5018AC03D1D411ABB70002A5091326015E1D7F@TLV1>
From: Sasha Vainshtein <Sasha@AXERRA.com>
To: "'ronc@lyciumnetworks.com '" <ronc@lyciumnetworks.com>,
	"'pwe3@ietf.org '" <pwe3@ietf.org>
Subject: RE: [PWE3] Proposed Changes to CEP
Date: Sat, 16 Apr 2005 18:50:55 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="ISO-8859-8"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 21c69d3cfc2dd19218717dbe1d974352
Cc: 
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=subscribe>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org

Ron (and all),
What has happened to the previously supported extension of the CEP CW?
In the previous versions it has been used to report the set of the active
VTs in SPE or VCs in VC4 for partually populated SPE/VC4...

Regards,
                      Sasha

-----Original Message-----
From: ronc@lyciumnetworks.com
To: pwe3@ietf.org
Cc: ronc@lyciumnetworks.com
Sent: 4/16/2005 2:46 AM
Subject: [PWE3] Proposed Changes to CEP

Dear PWE3ers

Below is a proposal by CEP authors that aligns the CEP draft with
draft-ietf-pwe3-cw-03.txt and with the other TDM emulation drafts.
Please send your comments as soon as possible. If no substential
comments are received in the coming week a new draft CEP-11 will be
issued detailing these changes. New CEP header description is attached.

Proposed changes to CEP-10:

Changes summary:
1. CEP header: align with recommended control word. Use L and R
  bits similar for remote/forward defect indications. Use 16 bit
  sequence number, length and fragmentations bits. Shorten structure
  pointer from 13 to 12 bits supporting payload sizes up to 4096 bytes. 
2. Align LDP interface parameters with above changes. Align MIB
  with above changes
3. Remove L2TPv3 encapsulation (to be described in a separate
  draft at a later time)
4. Remove RTP encapsulation

Happy tax day
Ron

Ron Cohen
CTO
Resolute Networks
Redux and Lycium Unite 
 <<New CEP.txt>>  <<ATT95243.txt>> 

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



From pwe3-bounces@ietf.org Sat Apr 16 22:01:42 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DMz6U-0001kI-7B; Sat, 16 Apr 2005 22:01:42 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DMz6R-0001kC-Tw
	for pwe3@megatron.ietf.org; Sat, 16 Apr 2005 22:01:39 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA25316
	for <pwe3@ietf.org>; Sat, 16 Apr 2005 22:01:37 -0400 (EDT)
Received: from lml101.siteprotect.com ([66.113.136.249])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DMzGv-0000E4-RH
	for pwe3@ietf.org; Sat, 16 Apr 2005 22:12:32 -0400
Received: from RONL (66-160-72-220-ntkk.cavtel.net [66.160.72.220])
	by lml101.siteprotect.com (8.9.3/8.9.3) with ESMTP id VAA00762;
	Sat, 16 Apr 2005 21:01:24 -0500
From: "Ron Cohen" <ronc@lyciumnetworks.com>
To: "'Sasha Vainshtein'" <Sasha@AXERRA.com>, <pwe3@ietf.org>
Subject: RE: [PWE3] Proposed Changes to CEP
Date: Sun, 17 Apr 2005 04:57:05 +0300
Message-ID: <006c01c542f0$c2aba420$0a00660a@il.reduxcom.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="ISO-8859-8"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.4024
Importance: Normal
X-Mimeole: Produced By Microsoft MimeOLE V6.00.2900.2180
In-Reply-To: <AF5018AC03D1D411ABB70002A5091326015E1D7F@TLV1>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 082a9cbf4d599f360ac7f815372a6a15
Content-Transfer-Encoding: 7bit
Cc: 
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=subscribe>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org

Sasha,

I attached only the CEP control word without extensions, where the
signficant changes are made. The control word extensions for fractional
STS-1 and VC4 circuits will continue to be supported as described in
CEP-10.

Thanks
Ron

-----Original Message-----
From: Sasha Vainshtein [mailto:Sasha@AXERRA.com] 
Sent: Saturday, April 16, 2005 7:51 PM
To: 'ronc@lyciumnetworks.com '; 'pwe3@ietf.org '
Subject: RE: [PWE3] Proposed Changes to CEP


Ron (and all),
What has happened to the previously supported extension of the CEP CW?
In the previous versions it has been used to report the set of the
active VTs in SPE or VCs in VC4 for partually populated SPE/VC4...

Regards,
                      Sasha

-----Original Message-----
From: ronc@lyciumnetworks.com
To: pwe3@ietf.org
Cc: ronc@lyciumnetworks.com
Sent: 4/16/2005 2:46 AM
Subject: [PWE3] Proposed Changes to CEP

Dear PWE3ers

Below is a proposal by CEP authors that aligns the CEP draft with
draft-ietf-pwe3-cw-03.txt and with the other TDM emulation drafts.
Please send your comments as soon as possible. If no substential
comments are received in the coming week a new draft CEP-11 will be
issued detailing these changes. New CEP header description is attached.

Proposed changes to CEP-10:

Changes summary:
1. CEP header: align with recommended control word. Use L and R
  bits similar for remote/forward defect indications. Use 16 bit
  sequence number, length and fragmentations bits. Shorten structure
  pointer from 13 to 12 bits supporting payload sizes up to 4096 bytes. 
2. Align LDP interface parameters with above changes. Align MIB
  with above changes
3. Remove L2TPv3 encapsulation (to be described in a separate
  draft at a later time)
4. Remove RTP encapsulation

Happy tax day
Ron

Ron Cohen
CTO
Resolute Networks
Redux and Lycium Unite 
 <<New CEP.txt>>  <<ATT95243.txt>> 


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



From pwe3-bounces@ietf.org Sun Apr 17 01:27:48 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DN2Ju-00053z-7V; Sun, 17 Apr 2005 01:27:46 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DN2Js-00053p-1b
	for pwe3@megatron.ietf.org; Sun, 17 Apr 2005 01:27:44 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA03940
	for <pwe3@ietf.org>; Sun, 17 Apr 2005 01:27:41 -0400 (EDT)
Received: from radmail2.rad.co.il ([80.74.100.136] helo=antivir1.rad.co.il)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DN2UJ-00089H-IY
	for pwe3@ietf.org; Sun, 17 Apr 2005 01:38:36 -0400
Received: from antivir1.rad.co.il (localhost [127.0.0.1])
	by antivir1.rad.co.il (8.12.10/8.12.10) with ESMTP id j3H5QI3M003083
	for <pwe3@ietf.org>; Sun, 17 Apr 2005 08:26:18 +0300 (IDT)
Received: from exrad2.ad.rad.co.il (exrad2 [192.114.24.112])
	by antivir1.rad.co.il (8.12.10/8.12.10) with ESMTP id j3H5QHgd003079;
	Sun, 17 Apr 2005 08:26:17 +0300 (IDT)
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [PWE3] Proposed Changes to CEP
Date: Sun, 17 Apr 2005 08:26:44 +0200
Message-ID: <27A0F290348F8E45AEF79889DDE65A52045B3CFE@exrad2.ad.rad.co.il>
Thread-Topic: [PWE3] Proposed Changes to CEP
Thread-Index: AcVCJmbD47XhGn+DR5WpcntabJD7wgA71BMg
From: "Yaakov Stein" <yaakov_s@rad.com>
To: <ronc@lyciumnetworks.com>, <pwe3@ietf.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2409bba43e9c8d580670fda8b695204a
Content-Transfer-Encoding: quoted-printable
Cc: 
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=subscribe>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org

Ron, =20

> 1. CEP header: align with recommended control word. Use L and R
>   bits similar for remote/forward defect indications. Use 16 bit
>   sequence number, length and fragmentations bits. Shorten structure
>   pointer from 13 to 12 bits supporting payload sizes up to 4096
bytes.=20

I think this is a great idea.

(and if you need an extended CW, that requirement will be signalled
and constant for the life of the connection,
and thus does not need an indication in the CW.)

We can now make the PWE CW not merely the "recommended CW"
but the mandatory one.

Y(J)S

<snip>

> 4. Remove RTP encapsulation

Does that mean you do not see any use for common-clock
mode timing recovery ?

Y(J)S

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



From pwe3-bounces@ietf.org Sun Apr 17 09:25:30 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DN9mD-0002MB-Q8; Sun, 17 Apr 2005 09:25:29 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DN9mC-0002M3-7t
	for pwe3@megatron.ietf.org; Sun, 17 Apr 2005 09:25:28 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA17998
	for <pwe3@ietf.org>; Sun, 17 Apr 2005 09:25:26 -0400 (EDT)
Received: from lml101.siteprotect.com ([66.113.136.249])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DN9wn-0000JR-9W
	for pwe3@ietf.org; Sun, 17 Apr 2005 09:36:26 -0400
Received: from RONL (66-160-72-220-ntkk.cavtel.net [66.160.72.220])
	by lml101.siteprotect.com (8.9.3/8.9.3) with ESMTP id IAA12415;
	Sun, 17 Apr 2005 08:25:06 -0500
From: "Ron Cohen" <ronc@lyciumnetworks.com>
To: "'Yaakov Stein'" <yaakov_s@rad.com>, <pwe3@ietf.org>
Subject: RE: [PWE3] Proposed Changes to CEP
Date: Sun, 17 Apr 2005 16:20:47 +0300
Message-ID: <000201c54350$45de5310$0a00660a@il.reduxcom.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.4024
Importance: Normal
In-Reply-To: <27A0F290348F8E45AEF79889DDE65A52045B3CFE@exrad2.ad.rad.co.il>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0ddefe323dd869ab027dbfff7eff0465
Content-Transfer-Encoding: 7bit
Cc: 
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=subscribe>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org

Yaakov,

> Does that mean you do not see any use for common-clock
> mode timing recovery ?

EPAR is a built-in CEP mechanism described in CEP-10 used in all
deployments to deliver differences between service clock and common
clock. We have not seen up till now a scenario where RTP adds benefit on
top of EPAR. Use of RTP is described in CEP-10 and we will follow WG
input whether to leave it there or remove it from CEP-11.

Thanks
Ron 


-----Original Message-----
From: Yaakov Stein [mailto:yaakov_s@rad.com] 
Sent: Sunday, April 17, 2005 9:27 AM
To: ronc@lyciumnetworks.com; pwe3@ietf.org
Subject: RE: [PWE3] Proposed Changes to CEP


Ron,  

> 1. CEP header: align with recommended control word. Use L and R
>   bits similar for remote/forward defect indications. Use 16 bit
>   sequence number, length and fragmentations bits. Shorten structure
>   pointer from 13 to 12 bits supporting payload sizes up to 4096
bytes. 

I think this is a great idea.

(and if you need an extended CW, that requirement will be signalled and
constant for the life of the connection, and thus does not need an
indication in the CW.)

We can now make the PWE CW not merely the "recommended CW"
but the mandatory one.

Y(J)S

<snip>

> 4. Remove RTP encapsulation

Does that mean you do not see any use for common-clock
mode timing recovery ?

Y(J)S


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



From pwe3-bounces@ietf.org Tue Apr 19 07:39:02 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DNr4I-0007mK-Oy; Tue, 19 Apr 2005 07:39:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DNr4H-0007mA-Ch
	for pwe3@megatron.ietf.org; Tue, 19 Apr 2005 07:39:01 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA00616
	for <pwe3@ietf.org>; Tue, 19 Apr 2005 07:38:59 -0400 (EDT)
Received: from ams-iport-1.cisco.com ([144.254.224.140])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DNrFG-0002Hp-T2
	for pwe3@ietf.org; Tue, 19 Apr 2005 07:50:24 -0400
Received: from ams-core-1.cisco.com (144.254.224.150)
	by ams-iport-1.cisco.com with ESMTP; 19 Apr 2005 13:38:51 +0200
Received: from cisco.com (mrwint.cisco.com [64.103.71.48])
	by ams-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id j3JBcK54007493; 
	Tue, 19 Apr 2005 13:38:20 +0200 (MEST)
Received: from cisco.com (ams-clip-vpn-dhcp4524.cisco.com [10.61.81.171])
	by cisco.com (8.8.8-Cisco List Logging/8.8.8) with ESMTP id MAA07770;
	Tue, 19 Apr 2005 12:38:18 +0100 (BST)
Message-ID: <4264EDA9.3050404@cisco.com>
Date: Tue, 19 Apr 2005 12:38:17 +0100
From: Stewart Bryant <stbryant@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: ronc@lyciumnetworks.com
Subject: Re: [PWE3] Proposed Changes to CEP
References: <200504160046.TAA24451@lml101.siteprotect.com>
In-Reply-To: <200504160046.TAA24451@lml101.siteprotect.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e1e48a527f609d1be2bc8d8a70eb76cb
Content-Transfer-Encoding: 7bit
Cc: pwe3@ietf.org
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=subscribe>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org

With my individual contributor hat on I agree with the changes.

 From a chair perspective I am pleased that we are aligning
with the CW text.

Stewart

ronc@lyciumnetworks.com wrote:

> Dear PWE3ers
> 
> Below is a proposal by CEP authors that aligns the CEP draft with draft-ietf-pwe3-cw-03.txt and with the other TDM emulation drafts. Please send your comments as soon as possible. If no substential comments are received in the coming week a new draft CEP-11 will be issued detailing these changes. New CEP header description is attached.
> 
> Proposed changes to CEP-10:
> 
> Changes summary:
> 1. CEP header: align with recommended control word. Use L and R
>   bits similar for remote/forward defect indications. Use 16 bit
>   sequence number, length and fragmentations bits. Shorten structure
>   pointer from 13 to 12 bits supporting payload sizes up to 4096 bytes. 
> 2. Align LDP interface parameters with above changes. Align MIB
>   with above changes
> 3. Remove L2TPv3 encapsulation (to be described in a separate
>   draft at a later time)
> 4. Remove RTP encapsulation
> 
> Happy tax day
> Ron
> 
> Ron Cohen
> CTO
> Resolute Networks
> Redux and Lycium Unite 
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> pwe3 mailing list
> pwe3@ietf.org
> https://www1.ietf.org/mailman/listinfo/pwe3

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



From pwe3-bounces@ietf.org Tue Apr 19 15:32:16 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DNySG-00077g-4M; Tue, 19 Apr 2005 15:32:16 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DNySE-00077b-VE
	for pwe3@megatron.ietf.org; Tue, 19 Apr 2005 15:32:14 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA12448
	for <pwe3@ietf.org>; Tue, 19 Apr 2005 15:32:12 -0400 (EDT)
Received: from ams-iport-1.cisco.com ([144.254.224.140])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DNydI-0002rK-LA
	for pwe3@ietf.org; Tue, 19 Apr 2005 15:43:41 -0400
Received: from ams-core-1.cisco.com (144.254.224.150)
	by ams-iport-1.cisco.com with ESMTP; 19 Apr 2005 21:32:04 +0200
Received: from cisco.com (mrwint.cisco.com [64.103.71.48])
	by ams-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id j3JJW154021767
	for <pwe3@ietf.org>; Tue, 19 Apr 2005 21:32:01 +0200 (MEST)
Received: from cisco.com (ams-clip-vpn-dhcp4524.cisco.com [10.61.81.171])
	by cisco.com (8.8.8-Cisco List Logging/8.8.8) with ESMTP id UAA25188;
	Tue, 19 Apr 2005 20:32:00 +0100 (BST)
Message-ID: <42655CB0.6090902@cisco.com>
Date: Tue, 19 Apr 2005 20:32:00 +0100
From: Stewart Bryant <stbryant@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: pwe3 <pwe3@ietf.org>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d17f825e43c9aed4fd65b7edddddec89
Content-Transfer-Encoding: 7bit
Subject: [PWE3] IANA last call
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=subscribe>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org

I am reminded that we have never issued a last call request for
the IANA draft.

This is the start of Last Call for
IANA Allocations for pseudo Wire Edge to Edge Emulation (PWE3)

http://www.ietf.org/internet-drafts/draft-ietf-pwe3-iana-allocation-09.txt

Last call will end WEdnesday 4th May 2005

Stewart

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



From pwe3-bounces@ietf.org Tue Apr 19 15:39:12 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DNyYy-00086X-Mr; Tue, 19 Apr 2005 15:39:12 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DNyYu-00085j-KO; Tue, 19 Apr 2005 15:39:08 -0400
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA12992;
	Tue, 19 Apr 2005 15:39:06 -0400 (EDT)
Message-Id: <200504191939.PAA12992@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Date: Tue, 19 Apr 2005 15:39:06 -0400
Cc: pwe3@ietf.org
Subject: [PWE3] I-D ACTION:draft-ietf-pwe3-atm-encap-08.txt
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=subscribe>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-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 Pseudo Wire Emulation Edge to Edge Working Group of the IETF.

	Title		: Encapsulation Methods for Transport of ATM Over 
			  MPLS Networks
	Author(s)	: L. Martini, et al.
	Filename	: draft-ietf-pwe3-atm-encap-08.txt
	Pages		: 40
	Date		: 2005-4-19
	
An ATM Pseudowire (PW) is used to carry ATM cells over an MPLS
   network. This enables service providers to offer "emulated" ATM
   services over existing IP or MPLS networks. This document specifies
   methods for the encapsulation of ATM cells within a pseudowire. It
   also specifies the procedures for using a PW to provide a ATM
   service.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-pwe3-atm-encap-08.txt

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request@ietf.org with the word unsubscribe in the body of the message.  
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.


Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-pwe3-atm-encap-08.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-pwe3-atm-encap-08.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
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: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body; access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID: <2005-4-19154333.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-pwe3-atm-encap-08.txt

--OtherAccess
Content-Type: Message/External-body; name="draft-ietf-pwe3-atm-encap-08.txt";
	site="ftp.ietf.org"; access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2005-4-19154333.I-D@ietf.org>


--OtherAccess--

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

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

--NextPart--






From pwe3-bounces@ietf.org Tue Apr 19 17:39:40 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DO0RY-0007rS-PP; Tue, 19 Apr 2005 17:39:40 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DO0RV-0007rK-RF
	for pwe3@megatron.ietf.org; Tue, 19 Apr 2005 17:39:38 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA29039
	for <pwe3@ietf.org>; Tue, 19 Apr 2005 17:39:34 -0400 (EDT)
Received: from sj-iport-4.cisco.com ([171.68.10.86])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DO0ca-0000oK-OR
	for pwe3@ietf.org; Tue, 19 Apr 2005 17:51:06 -0400
Received: from sj-core-4.cisco.com (171.68.223.138)
	by sj-iport-4.cisco.com with ESMTP; 19 Apr 2005 14:39:27 -0700
Received: from cisco.com (mrwint.cisco.com [64.103.71.48])
	by sj-core-4.cisco.com (8.12.10/8.12.6) with ESMTP id j3JLdLpR003612;
	Tue, 19 Apr 2005 14:39:22 -0700 (PDT)
Received: from cisco.com (ams-clip-vpn-dhcp4524.cisco.com [10.61.81.171])
	by cisco.com (8.8.8-Cisco List Logging/8.8.8) with ESMTP id WAA05046;
	Tue, 19 Apr 2005 22:39:08 +0100 (BST)
Message-ID: <42657A76.2070701@cisco.com>
Date: Tue, 19 Apr 2005 22:39:02 +0100
From: Stewart Bryant <stbryant@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Ron Cohen <ronc@lyciumnetworks.com>
Subject: Re: [PWE3] AD Review of draft-ietf-pwe3-cw-03.txt
References: <000401c54120$8e978220$0a00660a@il.reduxcom.com>
In-Reply-To: <000401c54120$8e978220$0a00660a@il.reduxcom.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4d87d2aa806f79fed918a62e834505ca
Content-Transfer-Encoding: 7bit
Cc: "'Yaakov Stein \(E-mail\)'" <yaakov_s@rad.com>,
	"'PWE3 WG \(E-mail\)'" <pwe3@ietf.org>, 'Danny McPherson' <danny@tcb.net>,
	"'Andrew G. Malis \(E-mail\)'" <Andy.Malis@tellabs.com>,
	"'W. Mark Townsley'" <townsley@cisco.com>,
	'Luca Martini' <lmartini@cisco.com>, 'Sasha Vainshtein' <Sasha@AXERRA.com>
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=subscribe>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org



Ron Cohen wrote:
> Hi,
> 
> The authors of CEP draft are working to align the CEP CW with the
> recommended PW CW. 
> 
> However, I do see a problem with the current sequence number text.
> The TDM emulation drafts all work on all values of the sequence number
> and do not skip over the 0 value. This is aligned with the use of
> sequence numbers in RTP. 
> 
> Best would be to mandate the use of the entire range of sequence numbers
> when configured to set and track sequence numbers for all services (not
> only TDM), and set the sequence number to zero when not used.
> 
> If no consensus on this change for all PW services can be agreed, I
> suggest to change the current text in CW draft to something similar to
> the following:

Given the number of implementations that skip 0, I think that we can
take it as read that there will be no consensus for this.

> 
> Sequence number (Bit 16 to 31): 
> 
>           The sequence number specifies the sequence number of a packet
>           Usage of the sequence number field is OPTIONAL or MANDATORY 
>           depending on the emulated service. For services for which 
>           usage of the sequence number is MANDATORY, the sequence
>           number cycles over all values. For services for which usage
>           of the sequence number is OPTIONAL it MUST be set to zero
>           by the sender and ignored by the receiver if not used.  
>           Otherwise it MUST cycle from 1 to 65535 (2**16-1). The 
>           sequence number window size for packet acceptance is dependent
>           on the parameters of both the PW and 
>           the MPLS PSN, and SHOULD be configurable. The mechanism used 
>           by the decapsulating PE to syncronise the expected sequence 
>           number with the received sequence number is implementation 
>           dependent.   
> 

I would be happy to include this. This is what has been implemented
far. Including the text would save four drafts including exception
text explaining why they used the complete sequence space.

I don't think that we should let this drag on, so unless I hear technical
reasons for doing otherwise I will include this amendment in the next
vesion of the control word draft.

Stewart

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



From pwe3-bounces@ietf.org Tue Apr 19 17:55:04 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DO0gS-0001wi-D1; Tue, 19 Apr 2005 17:55:04 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DO0gO-0001st-MO; Tue, 19 Apr 2005 17:55:02 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA29991;
	Tue, 19 Apr 2005 17:54:57 -0400 (EDT)
From: Tim.Frost@Zarlink.Com
Received: from cangate.zarlink.com ([209.226.172.89])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DO0rS-0001GK-T3; Tue, 19 Apr 2005 18:06:28 -0400
Received: from semigate.zarlink.com (semigate.zarlink.com [134.199.97.245])
	by cangate.zarlink.com (8.12.10/8.12.10) with ESMTP id j3JLspja021674; 
	Tue, 19 Apr 2005 17:54:51 -0400
Received: from OTTMTA01.zarlink.com (ottmta01 [134.199.14.110])
	by semigate.zarlink.com (8.11.6+Sun/8.11.6) with ESMTP id j3JLseI08977; 
	Tue, 19 Apr 2005 17:54:40 -0400 (EDT)
In-Reply-To: <42657A76.2070701@cisco.com>
To: Stewart Bryant <stbryant@cisco.com>
Subject: Re: [PWE3] AD Review of draft-ietf-pwe3-cw-03.txt
MIME-Version: 1.0
X-Mailer: Lotus Notes Release 6.5.1 January 21, 2004
Message-ID: <OFCBA370EF.A2088807-ON80256FE8.00782D1C-80256FE8.007856B8@Zarlink.Com>
Date: Tue, 19 Apr 2005 22:54:17 +0100
X-MIMETrack: Serialize by Router on ottmta01/Zarlink(Release 6.5.1|January 21,
	2004) at 04/19/2005 05:54:40 PM,
	Serialize complete at 04/19/2005 05:54:40 PM
X-Spam-Score: -98.31 () CONTROL_RULE, HTML_20_30, HTML_MESSAGE, NO_REAL_NAME,
	USER_IN_WHITELIST
X-Scanned-By: MIMEDefang 2.38
X-Spam-Score: 0.8 (/)
X-Scan-Signature: 926f893f9bbbfa169f045f85f0cdb955
Cc: pwe3-bounces@ietf.org, "'W. Mark Townsley'" <townsley@cisco.com>,
	"'PWE3 WG \(E-mail\)'" <pwe3@ietf.org>,
	"'Yaakov Stein \(E-mail\)'" <yaakov_s@rad.com>,
	'Danny McPherson' <danny@tcb.net>,
	"'Andrew G. Malis \(E-mail\)'" <Andy.Malis@tellabs.com>,
	Ron Cohen <ronc@lyciumnetworks.com>, 'Luca Martini' <lmartini@cisco.com>,
	'Sasha Vainshtein' <Sasha@AXERRA.com>
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0742937898=="
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org

This is a multipart message in MIME format.
--===============0742937898==
Content-Type: multipart/alternative;
	boundary="=_alternative 007856A980256FE8_="

This is a multipart message in MIME format.
--=_alternative 007856A980256FE8_=
Content-Type: text/plain; charset="US-ASCII"

Hi Stewart, Ron,
I support this wording.
Tim




Stewart Bryant <stbryant@cisco.com> 
Sent by: pwe3-bounces@ietf.org
19/04/2005 22:39

To
Ron Cohen <ronc@lyciumnetworks.com>
cc
"'Yaakov Stein \(E-mail\)'" <yaakov_s@rad.com>, "'PWE3 WG \(E-mail\)'" 
<pwe3@ietf.org>, "'Danny McPherson'" <danny@tcb.net>, "'Andrew G. Malis 
\(E-mail\)'" <Andy.Malis@tellabs.com>, "'W. Mark Townsley'" 
<townsley@cisco.com>, "'Luca Martini'" <lmartini@cisco.com>, "'Sasha 
Vainshtein'" <Sasha@AXERRA.com>
Subject
Re: [PWE3] AD Review of draft-ietf-pwe3-cw-03.txt








Ron Cohen wrote:
> Hi,
> 
> The authors of CEP draft are working to align the CEP CW with the
> recommended PW CW. 
> 
> However, I do see a problem with the current sequence number text.
> The TDM emulation drafts all work on all values of the sequence number
> and do not skip over the 0 value. This is aligned with the use of
> sequence numbers in RTP. 
> 
> Best would be to mandate the use of the entire range of sequence numbers
> when configured to set and track sequence numbers for all services (not
> only TDM), and set the sequence number to zero when not used.
> 
> If no consensus on this change for all PW services can be agreed, I
> suggest to change the current text in CW draft to something similar to
> the following:

Given the number of implementations that skip 0, I think that we can
take it as read that there will be no consensus for this.

> 
> Sequence number (Bit 16 to 31): 
> 
>           The sequence number specifies the sequence number of a packet
>           Usage of the sequence number field is OPTIONAL or MANDATORY 
>           depending on the emulated service. For services for which 
>           usage of the sequence number is MANDATORY, the sequence
>           number cycles over all values. For services for which usage
>           of the sequence number is OPTIONAL it MUST be set to zero
>           by the sender and ignored by the receiver if not used. 
>           Otherwise it MUST cycle from 1 to 65535 (2**16-1). The 
>           sequence number window size for packet acceptance is dependent
>           on the parameters of both the PW and 
>           the MPLS PSN, and SHOULD be configurable. The mechanism used 
>           by the decapsulating PE to syncronise the expected sequence 
>           number with the received sequence number is implementation 
>           dependent. 
> 

I would be happy to include this. This is what has been implemented
far. Including the text would save four drafts including exception
text explaining why they used the complete sequence space.

I don't think that we should let this drag on, so unless I hear technical
reasons for doing otherwise I will include this amendment in the next
vesion of the control word draft.

Stewart

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


--=_alternative 007856A980256FE8_=
Content-Type: text/html; charset="US-ASCII"


<br><font size=2 face="sans-serif">Hi Stewart, Ron,</font>
<br><font size=2 face="sans-serif">I support this wording.</font>
<br><font size=2 face="sans-serif">Tim</font>
<br>
<br>
<br>
<br>
<table width=100%>
<tr valign=top>
<td width=40%><font size=1 face="sans-serif"><b>Stewart Bryant &lt;stbryant@cisco.com&gt;</b>
</font>
<br><font size=1 face="sans-serif">Sent by: pwe3-bounces@ietf.org</font>
<p><font size=1 face="sans-serif">19/04/2005 22:39</font>
<td width=59%>
<table width=100%>
<tr>
<td>
<div align=right><font size=1 face="sans-serif">To</font></div>
<td valign=top><font size=1 face="sans-serif">Ron Cohen &lt;ronc@lyciumnetworks.com&gt;</font>
<tr>
<td>
<div align=right><font size=1 face="sans-serif">cc</font></div>
<td valign=top><font size=1 face="sans-serif">&quot;'Yaakov Stein \(E-mail\)'&quot;
&lt;yaakov_s@rad.com&gt;, &quot;'PWE3 WG \(E-mail\)'&quot; &lt;pwe3@ietf.org&gt;,
&quot;'Danny McPherson'&quot; &lt;danny@tcb.net&gt;, &quot;'Andrew G. Malis
\(E-mail\)'&quot; &lt;Andy.Malis@tellabs.com&gt;, &quot;'W. Mark Townsley'&quot;
&lt;townsley@cisco.com&gt;, &quot;'Luca Martini'&quot; &lt;lmartini@cisco.com&gt;,
&quot;'Sasha Vainshtein'&quot; &lt;Sasha@AXERRA.com&gt;</font>
<tr>
<td>
<div align=right><font size=1 face="sans-serif">Subject</font></div>
<td valign=top><font size=1 face="sans-serif">Re: [PWE3] AD Review of draft-ietf-pwe3-cw-03.txt</font></table>
<br>
<table>
<tr valign=top>
<td>
<td></table>
<br></table>
<br>
<br>
<br><font size=2><tt><br>
<br>
Ron Cohen wrote:<br>
&gt; Hi,<br>
&gt; <br>
&gt; The authors of CEP draft are working to align the CEP CW with the<br>
&gt; recommended PW CW. <br>
&gt; <br>
&gt; However, I do see a problem with the current sequence number text.<br>
&gt; The TDM emulation drafts all work on all values of the sequence number<br>
&gt; and do not skip over the 0 value. This is aligned with the use of<br>
&gt; sequence numbers in RTP. <br>
&gt; <br>
&gt; Best would be to mandate the use of the entire range of sequence numbers<br>
&gt; when configured to set and track sequence numbers for all services
(not<br>
&gt; only TDM), and set the sequence number to zero when not used.<br>
&gt; <br>
&gt; If no consensus on this change for all PW services can be agreed,
I<br>
&gt; suggest to change the current text in CW draft to something similar
to<br>
&gt; the following:<br>
<br>
Given the number of implementations that skip 0, I think that we can<br>
take it as read that there will be no consensus for this.<br>
<br>
&gt; <br>
&gt; Sequence number (Bit 16 to 31): <br>
&gt; <br>
&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; The sequence number specifies the
sequence number of a packet<br>
&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Usage of the sequence number field
is OPTIONAL or MANDATORY <br>
&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; depending on the emulated service.
For services for which <br>
&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; usage of the sequence number is
MANDATORY, the sequence<br>
&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; number cycles over all values.
For services for which usage<br>
&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; of the sequence number is OPTIONAL
it MUST be set to zero<br>
&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; by the sender and ignored by the
receiver if not used. &nbsp;<br>
&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Otherwise it MUST cycle from 1
to 65535 (2**16-1). The <br>
&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; sequence number window size for
packet acceptance is dependent<br>
&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; on the parameters of both the PW
and <br>
&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; the MPLS PSN, and SHOULD be configurable.
The mechanism used <br>
&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; by the decapsulating PE to syncronise
the expected sequence <br>
&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; number with the received sequence
number is implementation <br>
&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; dependent. &nbsp; <br>
&gt; <br>
<br>
I would be happy to include this. This is what has been implemented<br>
far. Including the text would save four drafts including exception<br>
text explaining why they used the complete sequence space.<br>
<br>
I don't think that we should let this drag on, so unless I hear technical<br>
reasons for doing otherwise I will include this amendment in the next<br>
vesion of the control word draft.<br>
<br>
Stewart<br>
<br>
_______________________________________________<br>
pwe3 mailing list<br>
pwe3@ietf.org<br>
https://www1.ietf.org/mailman/listinfo/pwe3<br>
</tt></font>
<br>
--=_alternative 007856A980256FE8_=--


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

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

--===============0742937898==--




From pwe3-bounces@ietf.org Tue Apr 19 17:56:04 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DO0hQ-0001zh-9Z; Tue, 19 Apr 2005 17:56:04 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DO0hO-0001zc-FU
	for pwe3@megatron.ietf.org; Tue, 19 Apr 2005 17:56:02 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA00061
	for <pwe3@ietf.org>; Tue, 19 Apr 2005 17:55:59 -0400 (EDT)
Received: from sj-iport-5.cisco.com ([171.68.10.87])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DO0sT-0001K8-85
	for pwe3@ietf.org; Tue, 19 Apr 2005 18:07:30 -0400
Received: from sj-core-3.cisco.com (171.68.223.137)
	by sj-iport-5.cisco.com with ESMTP; 19 Apr 2005 14:55:52 -0700
Received: from cisco.com (mrwint.cisco.com [64.103.71.48])
	by sj-core-3.cisco.com (8.12.10/8.12.6) with ESMTP id j3JLtmb4018452;
	Tue, 19 Apr 2005 14:55:48 -0700 (PDT)
Received: from cisco.com (ams-clip-vpn-dhcp4524.cisco.com [10.61.81.171])
	by cisco.com (8.8.8-Cisco List Logging/8.8.8) with ESMTP id WAA06578;
	Tue, 19 Apr 2005 22:55:46 +0100 (BST)
Message-ID: <42657E62.1080605@cisco.com>
Date: Tue, 19 Apr 2005 22:55:46 +0100
From: Stewart Bryant <stbryant@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "W. Mark Townsley" <townsley@cisco.com>
Subject: Re: [PWE3] AD Review of draft-ietf-pwe3-cw-03.txt
References: <425AE61B.2030909@cisco.com> <425D695D.3080709@cisco.com>
	<425D80D5.2080604@cisco.com>
In-Reply-To: <425D80D5.2080604@cisco.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 963faf56c3a5b6715f0b71b66181e01a
Content-Transfer-Encoding: 7bit
Cc: "PWE3 WG \(E-mail\)" <pwe3@ietf.org>, Luca Martini <lmartini@cisco.com>,
	Danny McPherson <danny@tcb.net>
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=subscribe>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org

Firstly I am sorry that I am so late in responding to this thread.
I was traveling last week.

I will attempt to persuade my copy of word to use an American
dictionary. The two spelling that Mark picked up were, believe,
both proper English spellings. I will also address the references
and other typos.

>  > 2.   PWE3 Packet Identification
>  >
>  >    All IP packets [RFC791][RFC1883] start with a version number that is
>  >    checked by LSRs performing MPLS payload inspection. To prevent the
>  >    incorrect processing of packets carried within a PW, PW packets
>  >    carried over an MPLS PSN SHOULD NOT start with the value 4 (IPv4) or
>  >    the value 6 (IPv6) in the first nibble [BCP], as those are assumed
>  >    to carry normal IP payloads.
> 
> Mark> Why not specify a MUST NOT here?
> 
> Luca> Some of the TDM PWs might start with a 4, as they do not have a
> Luca> conformant CW.

Given the SONET proposal to use a the standard CW, I think that the use
of MUST NOT would be appropriate.

>  >    When a PWMCW is used, it MUST adhere to the Generic MPLS Control
>  >    Word format as illustrated in Figure 1 above. It is however strongly
>  >    recommended that it also follows the following format:
> 
> Mark> Is this a capital RECOMMENDED or SHOULD?
> 
> Luca> yes i think it needs a capital RECOMMENDED.
> 

Again, given the SONET change, I think that we can make this a SHOULD

>  >           definition is encapsulation specific as defined in
>  >           [pointer?].
> 
> Mark> "pointer?" needs to be defined.
> 
> Luca> omission - this needs to be removed ....
> 

Will do.

>  >    Length (bits 10 to 15):

>  >           The value of the length field, if non-zero, can be used to
>  >           remove any padding added by the PSN. If the entire packet
>  >           length is less than 64 bytes, the length field MUST be set to
>  >           the length of the PW payload plus the length of the control
>  >           word. Otherwise it MUST be set to zero.
>  >
>  >           If a non-zero length field is received, the PW payload MUST
>  >           be trimmed if required.
> 
> Mark> What is meant by "if required" - To me, this either MUST be 
> trimmed or
> Mark> not (no need to suggest an implementation loophole if none should 
> exist).
> Mark>
> 
> Luca> no, it means that the payload might already be the correct length ,
> Luca> hence it might not need to be trimmed....
> Luca> Not all short packet have to be padded , some media do not require
> Luca> padding ....
> 
> So, just to be sure, we are stating that the payload length field MUST 
> be set for < 64 byte payloads regardless of media type, but there is an 
> "if required" on the trimming when receiving a non-zero length as some 
> media types do not need the length field.
> 
> Yes, I understand the issue here is ethernet, I'm not debating when it 
> is necessary or not. I simply find it odd that we have an exception 
> clause on the trimming, but not on the setting of the field.
> 
> Also, I think it might be helpful for interoperability to point out 
> ethernet as an example of when this field would be used. This shouldn't 
> take more than a sentence or two and perhaps a reference.


How about:

When the PSN path between the PEs includes an Ethernet, the PW packet
arriving at the CE-bound PE may include padding appended by the Ethernet
data link layer. The CE-bound PE uses the length field to determined
the size of the padding and hence extract the PW payload from the
PW packet.

If the entire packet length is less than 64 bytes, the length field
MUST be set to the length of the PW payload plus the length of the
control word. Otherwise it MUST be set to zero.

> 
>  >
>  >    Sequence number (Bit 16 to 31):
>  >
>  >           If the sequence number is not used, it is set to zero by the
>  >           sender and ignored by the receiver.  Otherwise it specifies
>  >           the sequence number of a packet.  A circular list of sequence
>  >           numbers is used.  A sequence number takes a value from 1 to
>  >           65535 (2**16-1). The sequence number window size for packet
>  >           acceptance is dependent on the parameters of both the PW and
>  >           the MPLS PSN, and SHOULD be configurable. The mechanism used
>  >           by the decapsulating PE to syncronise the expected sequence
>  >           number with the received sequence number is implementation
>  >           dependent.
> 
> Mark> s/syncronise/synchronize
> 
> Mark> That's two I caught, there must be more. Please run the doc through a
> Mark> spell checker.

See other mail in response to Ron's proposal


>  >    Bits 0..3 MUST be 0x01, and hence differ from the first four bits of
>  >    an IP packet [BCP]. This provides the necessary MPLS payload discrimination.
> 
> Mark> The first bits being 0x01 also differ this payload from being a PW
> Mark> payload.
> 
> My point here was simply that 0x01 does more than just differ this 
> packet from being a non-IP packet. It also makes it differ from being a 
> PWE3 data packet.
> 

How about

Bits 0..3 MUST be 0x01. This allows the packet the packet to be distinguished
from an IP packet [BCP] and from a PWE3 data packet.

>  >    
>  >
>  >    Note that L2TPv3 [REFERENCE] has its own mechanisms for providing
>  >    this associated channel, and is therefore out of the scope of this
>  >    document.
> 
> Mark> Need to define REFERENCE (RFC3931).

Will do.

> 
>  >
>  > 5.   IANA considerations
>  >
>  >    IANA needs to set up a registry of "Pseudowire Associated Channel
>  >    Types". These are 16-bit values. Registry entries are assigned by
>  >    using the "IETF Consensus" policy defined in [RFC2434].
> 
> Mark> What about FMT IDs?
> 

Propose to add:
IANA also needs to set up a registry of "Pseudowire Format Identifiers".
These are 4-bit values. Registry entries are assigned by
using the "IETF Consensus" policy defined in [RFC2434].


Also propose to change

FmtID:

           Format ID for the remaining 3 octets of the header......
                  ^^
to
           Format identifier for the remaining 3 octets of the header.....
                  ^^^^^^^^^^

to allow the for better consistency between the text and the
registry.

> 
                Algorithm, C. Hopps, November 2000
>  >    [RFC3985] RFC-3985: PWE3 Architecture, Bryant, S. ed., Pate,
>  >               P. ed. , To be published.
>  >    [VCCV]    Nadeau, T., Aggarwal, T., "Pseudo Wire (PW) Virtual
>  >               Circuit Connection Verification (VCCV)", Internet
>  >               Draft, <draft-ietf-pwe3-vccv-04.txt>, Feb. 2005,
>  >               Work in Progress.
> 
> Mark> Line spacing above.

Yes. Also need to add the RFC 3931 to references.

Stewart

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



From pwe3-bounces@ietf.org Wed Apr 20 03:42:51 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DO9rH-0006uh-6J; Wed, 20 Apr 2005 03:42:51 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DO9rF-0006uO-3F
	for pwe3@megatron.ietf.org; Wed, 20 Apr 2005 03:42:49 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA11934
	for <pwe3@ietf.org>; Wed, 20 Apr 2005 03:42:47 -0400 (EDT)
Received: from rtp-iport-2.cisco.com ([64.102.122.149])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DOA2Q-0000hb-0x
	for pwe3@ietf.org; Wed, 20 Apr 2005 03:54:22 -0400
Received: from rtp-core-2.cisco.com (64.102.124.13)
	by rtp-iport-2.cisco.com with ESMTP; 20 Apr 2005 03:42:40 -0400
Received: from fruitpie.cisco.com (IDENT:mirapoint@fruitpie.cisco.com
	[64.102.16.27])
	by rtp-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id j3K7gadr027579; 
	Wed, 20 Apr 2005 03:42:37 -0400 (EDT)
Received: from [10.83.1.102] (rtp-townsley-vpn5.cisco.com [10.83.1.102])
	by fruitpie.cisco.com (MOS 3.4.6-GR) with SMTP id BGT83198;
	Wed, 20 Apr 2005 00:42:31 -0700 (PDT)
Message-ID: <426607E4.3060508@cisco.com>
Date: Wed, 20 Apr 2005 03:42:28 -0400
From: "W. Mark Townsley" <townsley@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
	rv:1.7) Gecko/20040616
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Stewart Bryant <stbryant@cisco.com>
Subject: Re: [PWE3] AD Review of draft-ietf-pwe3-cw-03.txt
References: <425AE61B.2030909@cisco.com> <425D695D.3080709@cisco.com>
	<425D80D5.2080604@cisco.com> <42657E62.1080605@cisco.com>
In-Reply-To: <42657E62.1080605@cisco.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: bacfc6c7290e34d410f9bc22b825ce96
Content-Transfer-Encoding: 7bit
Cc: "PWE3 WG \(E-mail\)" <pwe3@ietf.org>, Luca Martini <lmartini@cisco.com>,
	Danny McPherson <danny@tcb.net>
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=subscribe>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org



Stewart Bryant wrote:

> Firstly I am sorry that I am so late in responding to this thread.
> I was traveling last week.
> 
> I will attempt to persuade my copy of word to use an American
> dictionary. The two spelling that Mark picked up were, believe,
> both proper English spellings. 

Apologies, my brain was programmed with an American bias beginning at a very 
early age. If the document consistently uses correct English spellings, I'm 
happy if the RFC Editor is happy.

Thanks,

- Mark

 > I will also address the references
> and other typos.
> 
>>  > 2.   PWE3 Packet Identification
>>  >
>>  >    All IP packets [RFC791][RFC1883] start with a version number 
>> that is
>>  >    checked by LSRs performing MPLS payload inspection. To prevent the
>>  >    incorrect processing of packets carried within a PW, PW packets
>>  >    carried over an MPLS PSN SHOULD NOT start with the value 4 
>> (IPv4) or
>>  >    the value 6 (IPv6) in the first nibble [BCP], as those are assumed
>>  >    to carry normal IP payloads.
>>
>> Mark> Why not specify a MUST NOT here?
>>
>> Luca> Some of the TDM PWs might start with a 4, as they do not have a
>> Luca> conformant CW.
> 
> 
> Given the SONET proposal to use a the standard CW, I think that the use
> of MUST NOT would be appropriate.
> 
>>  >    When a PWMCW is used, it MUST adhere to the Generic MPLS Control
>>  >    Word format as illustrated in Figure 1 above. It is however 
>> strongly
>>  >    recommended that it also follows the following format:
>>
>> Mark> Is this a capital RECOMMENDED or SHOULD?
>>
>> Luca> yes i think it needs a capital RECOMMENDED.
>>
> 
> Again, given the SONET change, I think that we can make this a SHOULD
> 
>>  >           definition is encapsulation specific as defined in
>>  >           [pointer?].
>>
>> Mark> "pointer?" needs to be defined.
>>
>> Luca> omission - this needs to be removed ....
>>
> 
> Will do.
> 
>>  >    Length (bits 10 to 15):
> 
> 
>>  >           The value of the length field, if non-zero, can be used to
>>  >           remove any padding added by the PSN. If the entire packet
>>  >           length is less than 64 bytes, the length field MUST be 
>> set to
>>  >           the length of the PW payload plus the length of the control
>>  >           word. Otherwise it MUST be set to zero.
>>  >
>>  >           If a non-zero length field is received, the PW payload MUST
>>  >           be trimmed if required.
>>
>> Mark> What is meant by "if required" - To me, this either MUST be 
>> trimmed or
>> Mark> not (no need to suggest an implementation loophole if none 
>> should exist).
>> Mark>
>>
>> Luca> no, it means that the payload might already be the correct length ,
>> Luca> hence it might not need to be trimmed....
>> Luca> Not all short packet have to be padded , some media do not require
>> Luca> padding ....
>>
>> So, just to be sure, we are stating that the payload length field MUST 
>> be set for < 64 byte payloads regardless of media type, but there is 
>> an "if required" on the trimming when receiving a non-zero length as 
>> some media types do not need the length field.
>>
>> Yes, I understand the issue here is ethernet, I'm not debating when it 
>> is necessary or not. I simply find it odd that we have an exception 
>> clause on the trimming, but not on the setting of the field.
>>
>> Also, I think it might be helpful for interoperability to point out 
>> ethernet as an example of when this field would be used. This 
>> shouldn't take more than a sentence or two and perhaps a reference.
> 
> 
> 
> How about:
> 
> When the PSN path between the PEs includes an Ethernet, the PW packet
> arriving at the CE-bound PE may include padding appended by the Ethernet
> data link layer. The CE-bound PE uses the length field to determined
> the size of the padding and hence extract the PW payload from the
> PW packet.
> 
> If the entire packet length is less than 64 bytes, the length field
> MUST be set to the length of the PW payload plus the length of the
> control word. Otherwise it MUST be set to zero.
> 
>>
>>  >
>>  >    Sequence number (Bit 16 to 31):
>>  >
>>  >           If the sequence number is not used, it is set to zero by the
>>  >           sender and ignored by the receiver.  Otherwise it specifies
>>  >           the sequence number of a packet.  A circular list of 
>> sequence
>>  >           numbers is used.  A sequence number takes a value from 1 to
>>  >           65535 (2**16-1). The sequence number window size for packet
>>  >           acceptance is dependent on the parameters of both the PW and
>>  >           the MPLS PSN, and SHOULD be configurable. The mechanism used
>>  >           by the decapsulating PE to syncronise the expected sequence
>>  >           number with the received sequence number is implementation
>>  >           dependent.
>>
>> Mark> s/syncronise/synchronize
>>
>> Mark> That's two I caught, there must be more. Please run the doc 
>> through a
>> Mark> spell checker.
> 
> 
> See other mail in response to Ron's proposal
> 
> 
>>  >    Bits 0..3 MUST be 0x01, and hence differ from the first four 
>> bits of
>>  >    an IP packet [BCP]. This provides the necessary MPLS payload 
>> discrimination.
>>
>> Mark> The first bits being 0x01 also differ this payload from being a PW
>> Mark> payload.
>>
>> My point here was simply that 0x01 does more than just differ this 
>> packet from being a non-IP packet. It also makes it differ from being 
>> a PWE3 data packet.
>>
> 
> How about
> 
> Bits 0..3 MUST be 0x01. This allows the packet the packet to be 
> distinguished
> from an IP packet [BCP] and from a PWE3 data packet.
> 
>>  >     >
>>  >    Note that L2TPv3 [REFERENCE] has its own mechanisms for providing
>>  >    this associated channel, and is therefore out of the scope of this
>>  >    document.
>>
>> Mark> Need to define REFERENCE (RFC3931).
> 
> 
> Will do.
> 
>>
>>  >
>>  > 5.   IANA considerations
>>  >
>>  >    IANA needs to set up a registry of "Pseudowire Associated Channel
>>  >    Types". These are 16-bit values. Registry entries are assigned by
>>  >    using the "IETF Consensus" policy defined in [RFC2434].
>>
>> Mark> What about FMT IDs?
>>
> 
> Propose to add:
> IANA also needs to set up a registry of "Pseudowire Format Identifiers".
> These are 4-bit values. Registry entries are assigned by
> using the "IETF Consensus" policy defined in [RFC2434].
> 
> 
> Also propose to change
> 
> FmtID:
> 
>           Format ID for the remaining 3 octets of the header......
>                  ^^
> to
>           Format identifier for the remaining 3 octets of the header.....
>                  ^^^^^^^^^^
> 
> to allow the for better consistency between the text and the
> registry.
> 
>>
>                Algorithm, C. Hopps, November 2000
> 
>>  >    [RFC3985] RFC-3985: PWE3 Architecture, Bryant, S. ed., Pate,
>>  >               P. ed. , To be published.
>>  >    [VCCV]    Nadeau, T., Aggarwal, T., "Pseudo Wire (PW) Virtual
>>  >               Circuit Connection Verification (VCCV)", Internet
>>  >               Draft, <draft-ietf-pwe3-vccv-04.txt>, Feb. 2005,
>>  >               Work in Progress.
>>
>> Mark> Line spacing above.
> 
> 
> Yes. Also need to add the RFC 3931 to references.
> 
> Stewart
> 

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



From pwe3-bounces@ietf.org Wed Apr 20 13:30:17 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DOJ1l-0000Rz-O0; Wed, 20 Apr 2005 13:30:17 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DOJ1k-0000Rn-TM
	for pwe3@megatron.ietf.org; Wed, 20 Apr 2005 13:30:17 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA00089
	for <pwe3@ietf.org>; Wed, 20 Apr 2005 13:30:14 -0400 (EDT)
Received: from rtp-iport-1.cisco.com ([64.102.122.148])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DOJD0-00025g-6k
	for pwe3@ietf.org; Wed, 20 Apr 2005 13:41:55 -0400
Received: from rtp-core-2.cisco.com (64.102.124.13)
	by rtp-iport-1.cisco.com with ESMTP; 20 Apr 2005 13:41:11 -0400
X-IronPort-AV: i="3.92,117,1112587200"; 
	d="scan'208"; a="45404790:sNHT28037720"
Received: from [209.245.27.1] ([10.32.241.115])
	by rtp-core-2.cisco.com (8.12.10/8.12.6) with SMTP id j3KHTqdr006552;
	Wed, 20 Apr 2005 13:29:58 -0400 (EDT)
Message-ID: <42669190.9030808@cisco.com>
Date: Wed, 20 Apr 2005 11:29:52 -0600
From: Luca Martini <lmartini@cisco.com>
User-Agent: Mozilla Thunderbird 1.0 (X11/20041208)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Stewart Bryant <stbryant@cisco.com>
Subject: Re: [PWE3] AD Review of draft-ietf-pwe3-cw-03.txt
References: <425AE61B.2030909@cisco.com>
	<425D695D.3080709@cisco.com>	<425D80D5.2080604@cisco.com>
	<42657E62.1080605@cisco.com>
In-Reply-To: <42657E62.1080605@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-PMX-Version: 4.7.0.111621
X-from-outside-Cisco: [10.32.241.115]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 00e94c813bef7832af255170dca19e36
Content-Transfer-Encoding: 7bit
Cc: "W. Mark Townsley" <townsley@cisco.com>,
	"PWE3 WG \(E-mail\)" <pwe3@ietf.org>, Danny McPherson <danny@tcb.net>
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=subscribe>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org

Stewart Bryant wrote:

Snip ....

 >           The value of the length field, if non-zero, can be used to

>>  >           remove any padding added by the PSN. If the entire packet
>>  >           length is less than 64 bytes, the length field MUST be 
>> set to
>>  >           the length of the PW payload plus the length of the control
>>  >           word. Otherwise it MUST be set to zero.
>>  >
>>  >           If a non-zero length field is received, the PW payload MUST
>>  >           be trimmed if required.
>>
>> Mark> What is meant by "if required" - To me, this either MUST be 
>> trimmed or
>> Mark> not (no need to suggest an implementation loophole if none 
>> should exist).
>> Mark>
>>
>> Luca> no, it means that the payload might already be the correct 
>> length ,
>> Luca> hence it might not need to be trimmed....
>> Luca> Not all short packet have to be padded , some media do not require
>> Luca> padding ....
>>
>> So, just to be sure, we are stating that the payload length field 
>> MUST be set for < 64 byte payloads regardless of media type, but 
>> there is an "if required" on the trimming when receiving a non-zero 
>> length as some media types do not need the length field.
>>
>> Yes, I understand the issue here is ethernet, I'm not debating when 
>> it is necessary or not. I simply find it odd that we have an 
>> exception clause on the trimming, but not on the setting of the field.
>>
>> Also, I think it might be helpful for interoperability to point out 
>> ethernet as an example of when this field would be used. This 
>> shouldn't take more than a sentence or two and perhaps a reference.
>
>
>
> How about:
>
> When the PSN path between the PEs includes an Ethernet, the PW packet
> arriving at the CE-bound PE may include padding appended by the Ethernet
> data link layer. The CE-bound PE uses the length field to determined
> the size of the padding and hence extract the PW payload from the
> PW packet.
>
> If the entire packet length is less than 64 bytes, the length field
> MUST be set to the length of the PW payload plus the length of the
> control word. Otherwise it MUST be set to zero.
>
>

CEE-bound PE -> need to change to something like "packet received on the 
PW from the PSN"
Snip...

>
> Bits 0..3 MUST be 0x01. This allows the packet the packet to be 
> distinguished
> from an IP packet [BCP] and from a PWE3 data packet.
>
>>  >     >
>>  >    Note that L2TPv3 [REFERENCE] has its own mechanisms for providing
>>  >    this associated channel, and is therefore out of the scope of this
>>  >    document.
>>
>> Mark> Need to define REFERENCE (RFC3931).
>
>
> Will do.
>
can you please change to "bit 0 to bit 3 MUST be set to 0001 "

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



From pwe3-bounces@ietf.org Thu Apr 21 01:55:23 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DOUep-00088T-87; Thu, 21 Apr 2005 01:55:23 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DOUem-00088H-PA
	for pwe3@megatron.ietf.org; Thu, 21 Apr 2005 01:55:20 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA04179
	for <pwe3@ietf.org>; Thu, 21 Apr 2005 01:55:18 -0400 (EDT)
Received: from radmail1.rad.co.il ([62.0.23.193] helo=antivir1.rad.co.il)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DOUq3-0004Il-AO
	for pwe3@ietf.org; Thu, 21 Apr 2005 02:07:04 -0400
Received: from antivir1.rad.co.il (localhost [127.0.0.1])
	by antivir1.rad.co.il (8.12.10/8.12.10) with ESMTP id j3L5ru3O015458
	for <pwe3@ietf.org>; Thu, 21 Apr 2005 08:53:56 +0300 (IDT)
Received: from exrad2.ad.rad.co.il (exrad2 [192.114.24.112])
	by antivir1.rad.co.il (8.12.10/8.12.10) with ESMTP id j3L5rtgd015455;
	Thu, 21 Apr 2005 08:53:55 +0300 (IDT)
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [PWE3] IANA last call
Date: Thu, 21 Apr 2005 08:54:17 +0200
Message-ID: <27A0F290348F8E45AEF79889DDE65A5204660052@exrad2.ad.rad.co.il>
Thread-Topic: [PWE3] IANA last call
Thread-Index: AcVFH01HcErr5Bg3S7WiVwBwEqEpdwBHJRKw
From: "Yaakov Stein" <yaakov_s@rad.com>
To: "Stewart Bryant" <stbryant@cisco.com>, "pwe3" <pwe3@ietf.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: bb8f917bb6b8da28fc948aeffb74aa17
Content-Transfer-Encoding: quoted-printable
Cc: Luca Martini <lmartini@cisco.com>
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=subscribe>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org

=20
> This is the start of Last Call for
> IANA Allocations for pseudo Wire Edge to Edge Emulation (PWE3)
>=20
>
http://www.ietf.org/internet-drafts/draft-ietf-pwe3-iana-allocation-09.t
xt

Once again, there is a problem with the PW types for TDMoIP.

Right now there are
     0x0016  TDMoIP basic mode
     0x0018  TDMoIP TDM with CAS
which were probably allocated in analogy to the CESoPSN case.

However, there is no "basic" mode for TDMoIP,
and now that I have dropped the FORMID field
(in order to use 0000 in the first CW nibble for all cases)
I need the differentiation between the 4 modes described
in the TDMoIP draft.

These modes are:

   AAL1 mode - unstructured
   AAL1 mode - structured
   AAL1 mode - structured with CAS
   AAL2 mode

The final mode (used for sending SS7 or ISDN PRI signaling)
will use 0x0006 allocated for HDLC.

So please allocate 4 PW types as described above.

Y(J)S


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



From pwe3-bounces@ietf.org Thu Apr 21 10:07:45 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DOcLJ-0007Aa-0o; Thu, 21 Apr 2005 10:07:45 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DOcLH-0007AV-AS
	for pwe3@megatron.ietf.org; Thu, 21 Apr 2005 10:07:43 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA02525
	for <pwe3@ietf.org>; Thu, 21 Apr 2005 10:07:40 -0400 (EDT)
Received: from radmail.rad.co.il ([212.117.147.38] helo=antivir1.rad.co.il)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DOcWe-000075-8r
	for pwe3@ietf.org; Thu, 21 Apr 2005 10:19:31 -0400
Received: from antivir1.rad.co.il (localhost [127.0.0.1])
	by antivir1.rad.co.il (8.12.10/8.12.10) with ESMTP id j3LE6J3O004202
	for <pwe3@ietf.org>; Thu, 21 Apr 2005 17:06:19 +0300 (IDT)
Received: from exrad2.ad.rad.co.il (exrad2 [192.114.24.112])
	by antivir1.rad.co.il (8.12.10/8.12.10) with ESMTP id j3LE6Igd004199;
	Thu, 21 Apr 2005 17:06:18 +0300 (IDT)
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [PWE3] AD Review of draft-ietf-pwe3-cw-03.txt
Date: Thu, 21 Apr 2005 17:06:37 +0200
Message-ID: <27A0F290348F8E45AEF79889DDE65A52046602A2@exrad2.ad.rad.co.il>
Thread-Topic: [PWE3] AD Review of draft-ietf-pwe3-cw-03.txt
Thread-Index: AcVFMJCIVW8Hej2yTQahU8djIS0qQwBUakig
From: "Yaakov Stein" <yaakov_s@rad.com>
To: "Stewart Bryant" <stbryant@cisco.com>,
	"Ron Cohen" <ronc@lyciumnetworks.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 082a9cbf4d599f360ac7f815372a6a15
Content-Transfer-Encoding: quoted-printable
Cc: "PWE3 WG \(E-mail\)" <pwe3@ietf.org>
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=subscribe>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org

=20
> > Sequence number (Bit 16 to 31):=20
> >=20
> >           The sequence number specifies the sequence number of a
packet
> >           Usage of the sequence number field is OPTIONAL or
MANDATORY=20
> >           depending on the emulated service. For services for which=20
> >           usage of the sequence number is MANDATORY, the sequence
> >           number cycles over all values. For services for which
usage
> >           of the sequence number is OPTIONAL it MUST be set to zero
> >           by the sender and ignored by the receiver if not used. =20
> >           Otherwise it MUST cycle from 1 to 65535 (2**16-1). The=20
> >           sequence number window size for packet acceptance is
dependent
> >           on the parameters of both the PW and=20
> >           the MPLS PSN, and SHOULD be configurable. The mechanism
used=20
> >           by the decapsulating PE to syncronise the expected
sequence=20
> >           number with the received sequence number is implementation

> >           dependent.  =20
>=20
> I would be happy to include this. This is what has been=20
> implemented far. Including the text would save four drafts=20
> including exception text explaining why they used the=20
> complete sequence space.
>=20

Stewart,=20

Not only does this capture what HAS been implemented,
it captures WHY that is the case (simply those cases
where the SN is mandatory do not need to keep SN=3D0
as a special case).

I fully support this type of wording, but think it is a bit
to complex.

The following is a bit simpler (at least to me):

          The sequence number implements the sequencing function [ARCH].
          For some emulated services usage of the sequence number field
is OPTIONAL=20
          while for others it is MANDATORY. For services for which=20
          usage is MANDATORY, the sequence number cycles over all values

          from 0 to 65535 (2**16-1).
          For services for which usage is OPTIONAL, when the sequence
number=20
          is used it cycles from 1 to 65535 (2**16-1), and a zero value
          indicates that it is not used.
          The size of the window used for packet acceptance is dependent
          on the parameters of both the PW and the MPLS PSN, and=20
          SHOULD be configurable. The mechanism used by a receiver
          to synchronise the expected and received sequence numbers=20
          is implementation dependent.  =20

Y(J)S


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



From pwe3-bounces@ietf.org Thu Apr 21 13:06:03 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DOf7q-0006Hd-Uk; Thu, 21 Apr 2005 13:06:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DOf7q-0006HY-2H
	for pwe3@megatron.ietf.org; Thu, 21 Apr 2005 13:06:02 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA17490
	for <pwe3@ietf.org>; Thu, 21 Apr 2005 13:05:59 -0400 (EDT)
Received: from rtp-iport-1.cisco.com ([64.102.122.148])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DOfJI-0004sB-1h
	for pwe3@ietf.org; Thu, 21 Apr 2005 13:17:53 -0400
Received: from rtp-core-1.cisco.com (64.102.124.12)
	by rtp-iport-1.cisco.com with ESMTP; 21 Apr 2005 13:17:05 -0400
X-IronPort-AV: i="3.92,121,1112587200"; 
	d="scan'208"; a="45598131:sNHT4079615834"
Received: from [209.245.27.1] ([10.32.241.115])
	by rtp-core-1.cisco.com (8.12.10/8.12.6) with SMTP id j3LH5kRQ029967;
	Thu, 21 Apr 2005 13:05:47 -0400 (EDT)
Message-ID: <4267DD69.7070008@cisco.com>
Date: Thu, 21 Apr 2005 11:05:45 -0600
From: Luca Martini <lmartini@cisco.com>
User-Agent: Mozilla Thunderbird 1.0 (X11/20041208)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Yaakov Stein <yaakov_s@rad.com>
Subject: Re: [PWE3] IANA last call
References: <27A0F290348F8E45AEF79889DDE65A5204660052@exrad2.ad.rad.co.il>
In-Reply-To: <27A0F290348F8E45AEF79889DDE65A5204660052@exrad2.ad.rad.co.il>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-PMX-Version: 4.7.0.111621
X-from-outside-Cisco: [10.32.241.115]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 5a9a1bd6c2d06a21d748b7d0070ddcb8
Content-Transfer-Encoding: 7bit
Cc: pwe3 <pwe3@ietf.org>, Stewart Bryant <stbryant@cisco.com>
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=subscribe>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org

Yaakov,

This is a minor change.
So , please send me exact text.
I take it that you want pw type 0x16 changed ? 0x18 renamed ?
and 2 more modes ? ( 0x20, 0x2A ) ?
Also keep in mind that these are pw types , not modes.

Thanks.
Luca




Yaakov Stein wrote:

> 
>  
>
>>This is the start of Last Call for
>>IANA Allocations for pseudo Wire Edge to Edge Emulation (PWE3)
>>
>>
>>    
>>
>http://www.ietf.org/internet-drafts/draft-ietf-pwe3-iana-allocation-09.t
>xt
>
>Once again, there is a problem with the PW types for TDMoIP.
>
>Right now there are
>     0x0016  TDMoIP basic mode
>     0x0018  TDMoIP TDM with CAS
>which were probably allocated in analogy to the CESoPSN case.
>
>However, there is no "basic" mode for TDMoIP,
>and now that I have dropped the FORMID field
>(in order to use 0000 in the first CW nibble for all cases)
>I need the differentiation between the 4 modes described
>in the TDMoIP draft.
>
>These modes are:
>
>   AAL1 mode - unstructured
>   AAL1 mode - structured
>   AAL1 mode - structured with CAS
>   AAL2 mode
>
>The final mode (used for sending SS7 or ISDN PRI signaling)
>will use 0x0006 allocated for HDLC.
>
>So please allocate 4 PW types as described above.
>
>Y(J)S
>
>  
>

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



From pwe3-bounces@ietf.org Thu Apr 21 15:39:40 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DOhWW-0007rH-1h; Thu, 21 Apr 2005 15:39:40 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DOhWS-0007rA-HP
	for pwe3@megatron.ietf.org; Thu, 21 Apr 2005 15:39:38 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA01135
	for <pwe3@ietf.org>; Thu, 21 Apr 2005 15:39:35 -0400 (EDT)
Received: from rtp-iport-1.cisco.com ([64.102.122.148])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DOhhv-0000Gf-PU
	for pwe3@ietf.org; Thu, 21 Apr 2005 15:51:29 -0400
Received: from rtp-core-1.cisco.com (64.102.124.12)
	by rtp-iport-1.cisco.com with ESMTP; 21 Apr 2005 15:50:40 -0400
X-IronPort-AV: i="3.92,121,1112587200"; 
	d="scan'208"; a="45626046:sNHT2226463140"
Received: from [209.245.27.1] ([10.32.241.115])
	by rtp-core-1.cisco.com (8.12.10/8.12.6) with SMTP id j3LJdBRQ015123;
	Thu, 21 Apr 2005 15:39:21 -0400 (EDT)
Message-ID: <4268015F.4010305@cisco.com>
Date: Thu, 21 Apr 2005 13:39:11 -0600
From: Luca Martini <lmartini@cisco.com>
User-Agent: Mozilla Thunderbird 1.0 (X11/20041208)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Dov Faust <dov.faust@telrad.co.il>
References: <C0F328F4B564A544ADBA98DA8BBE86F11C5E8A@tpa-mail1.telrad.co.il>
In-Reply-To: <C0F328F4B564A544ADBA98DA8BBE86F11C5E8A@tpa-mail1.telrad.co.il>
Content-Type: text/plain; charset=windows-1255; format=flowed
Content-Transfer-Encoding: 7bit
X-PMX-Version: 4.7.0.111621
X-from-outside-Cisco: [10.32.241.115]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 69a74e02bbee44ab4f8eafdbcedd94a1
Content-Transfer-Encoding: 7bit
Cc: 'Giles Heron' <giles.heron@tellabs.com>, 'Nasser El-Aawar' <nna@level3.net>,
	"PWE3 WG \(E-mail\)" <pwe3@ietf.org>,
	Gali Malkiel <gali.malkiel@telrad.co.il>
Subject: [PWE3] Re: Comments on "draft-ietf-pwe3-ethernet-encap-09"
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=subscribe>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org

Dov,

That you for the comments. This draft is past the AD review stage, and I 
cannot make any changes to it.
However I have fixed all the spelling errors that you identified ( 
including the references ). These fixes should appear in the final RFC.
I is difficult for me to edit the document you attached , so I cannot 
send you a detailed reply. Please do not use the HTML document, a simple 
in line comment is much easier to read.

Luca


Dov Faust wrote:

>hI,
>
>Please find attached an HTML version of your document
>draft-ietf-pwe3-ethernet-encap-09, dated Feb. 2005, with a few comments.
>
>My comments are marked as [d1][d2]...[d10].
>
>You may access the file using your browser or (as I did) just using MS-Word
>and looking MS-Word comments - I get them as yellow background of the
>commented text.
>
>Regards,
>
>Dov.Faust
>(dov.faust@telrad.co.il)
>
>Telrad Networks 
>Rosh Ha-Ayin
>Israel
>
> <<draft-ietf-pwe3-ethernet-encap-09-DovFaustComments.htm>> 
>  
>

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



From pwe3-bounces@ietf.org Thu Apr 21 18:05:14 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DOjnO-0001Ej-5t; Thu, 21 Apr 2005 18:05:14 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DOjnM-0001EL-72
	for pwe3@megatron.ietf.org; Thu, 21 Apr 2005 18:05:12 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA21361
	for <pwe3@ietf.org>; Thu, 21 Apr 2005 18:05:09 -0400 (EDT)
Received: from almso1.att.com ([192.128.167.69] helo=almso1.proxy.att.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DOjyr-0006qg-KK
	for pwe3@ietf.org; Thu, 21 Apr 2005 18:17:06 -0400
Received: from attrh5i.attrh.att.com ([135.38.62.12])
	by almso1.proxy.att.com (AT&T IPNS/MSO-5.5) with ESMTP id
	j3LM4Uwi022369 for <pwe3@ietf.org>; Thu, 21 Apr 2005 18:05:02 -0400
Received: from kcclust06evs1.ugd.att.com (135.38.164.88) by
	attrh5i.attrh.att.com (7.2.052)
	id 426289720014C818 for pwe3@ietf.org; Thu, 21 Apr 2005 18:05:02 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 21 Apr 2005 17:05:02 -0500
Message-ID: <9473683187ADC049A855ED2DA739ABCA060CE569@KCCLUST06EVS1.ugd.att.com>
Thread-Topic: I-D ACTION:draft-ash-avt-hc-over-mpls-protocol-00.txt
Thread-Index: AcVGsK+ZB2HmnyVzRdmKlM478mx93gAB+qAAAAFCAXA=
From: "Ash, Gerald R \(Jerry\), ALABS" <gash@att.com>
To: <pwe3@ietf.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a2c12dacc0736f14d6b540e805505a86
Content-Transfer-Encoding: quoted-printable
Cc: "Ash, Gerald R \(Jerry\), ALABS" <gash@att.com>
Subject: [PWE3] RE: I-D ACTION:draft-ash-avt-hc-over-mpls-protocol-00.txt
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=subscribe>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org

Hi All,

Please review and comment on the (significantly) updated draft "Protocol
Extensions for Header Compression over MPLS"
(http://www.ietf.org/internet-drafts/draft-ash-avt-hc-over-mpls-protocol
-00.txt).

Here is a brief background and overview/explanation of the updates:

Work on requirements for header compression over MPLS
(http://www.ietf.org/internet-drafts/draft-ietf-avt-hc-mpls-reqs-03.txt)
is complete, and work on protocol extensions for header compression over
MPLS is underway (previous draft at
http://ietf.org/internet-drafts/draft-ash-avt-ecrtp-over-mpls-protocol-0
2.txt).  Chartering of the protocol work in the AVT working group has
been submitted for approval with the following milestone:

Dec 05: Submit any extensions for RTP HC on MPLS networks for Proposed
Standard

There has been considerable discussion on the previous protocol
extensions draft
(http://ietf.org/internet-drafts/draft-ash-avt-ecrtp-over-mpls-protocol-
02.txt) in the last couple of months.  I presented the update on the
header compression over MPLS protocol extensions work at the AVT meeting
at IETF-62; slides and minutes are available at
https://datatracker.ietf.org/public/proceeding_interim.cgi?meeting_num=3D=
6
2 (look under AVT for minutes and slides).  The recent discussion and
issues regarding the basic approach are summarized in the slides.

Header compression experts in the AVT and ROHC working groups wish to
re-use, and extend, the existing layer 2 approaches for assignment of
context identification (CID) and header compression parameter
negotiation.  In a multipoint-to-point MPLS environment, one approach
would be to have the various header compressors assign CIDs as they do
now, with the possible need to resolve CID conflicts/collisions at the
header decompressor.  Some comments were made that current header
compression methods do not have to resolve CID collisions, however the
synchronization source (SSRC) assigned in RTP could need
collision/conflict resolution.

A second approach, suggested by Andy Malis and Loa Andersson, is to use
pseudowires and/or targeted LDP to create 'point-to-point' sessions
between header compressor and header decompressor, thereby avoiding any
issue of CID collision.  The disadvantage of this approach is that it
requires an additional 4-byte label to be carried with each packet. =20

The updated draft based on the second approach is available at
http://www.ietf.org/internet-drafts/draft-ash-avt-hc-over-mpls-protocol-
00.txt.

Once again, please review and comment on the updated draft.

Thanks,
Jerry

-----Original Message-----
From: i-d-announce-bounces@ietf.org
[mailto:i-d-announce-bounces@ietf.org] On Behalf Of
Internet-Drafts@ietf.org
Sent: Thursday, April 21, 2005 3:39 PM
To: i-d-announce@ietf.org
Subject: I-D ACTION:draft-ash-avt-hc-over-mpls-protocol-00.txt

A New Internet-Draft is available from the on-line Internet-Drafts
directories.


	Title		: Protocol Extensions for Header Compression
over MPLS
	Author(s)	: J. Ash, et al.
	Filename	: draft-ash-avt-hc-over-mpls-protocol-00.txt
	Pages		: 12
	Date		: 2005-4-21
=09
VoIP typically uses the encapsulation voice/RTP/UDP/IP. When MPLS labels
are added, this becomes voice/RTP/UDP/IP/MPLS-labels. For an MPLS VPN,
the packet header is at least 48 bytes, while the voice payload is often
no more than 30 bytes, for example. Header compression can significantly
reduce the overhead through various compression mechanisms.  MPLS is
used to route header-compressed (HC) packets over an MPLS LSP without
compression/decompression cycles at each router. Such an HC over MPLS
capability increases the bandwidth efficiency as well as processing
scalability of the maximum number of simultaneous compressed flows that
use HC at each router.  MPLS pseudowires are used to transport the HC
context and other control messages between the ingress and egress MPLS
label switched router (LSR), and the pseudowires define a point to point
instance of each HC session at the header decompressor.  Standard HC
methods (e.g., ECRTP, ROHC, etc.) are re-used to determine the context.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ash-avt-hc-over-mpls-protocol-
00.txt

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



From pwe3-bounces@ietf.org Fri Apr 22 15:54:55 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DP4Ep-0003El-F8; Fri, 22 Apr 2005 15:54:55 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DP4Ek-0003DO-RE; Fri, 22 Apr 2005 15:54:50 -0400
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA18393;
	Fri, 22 Apr 2005 15:54:49 -0400 (EDT)
Message-Id: <200504221954.PAA18393@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Date: Fri, 22 Apr 2005 15:54:49 -0400
Cc: pwe3@ietf.org
Subject: [PWE3] I-D ACTION:draft-ietf-pwe3-frame-relay-05.txt
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=subscribe>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-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 Pseudo Wire Emulation Edge to Edge Working Group of the IETF.

	Title		: Encapsulation Methods for Transport of Frame Relay Over MPLS Networks
	Author(s)	: L. Martini, C. Kawa
	Filename	: draft-ietf-pwe3-frame-relay-05.txt
	Pages		: 20
	Date		: 2005-4-22
	
A frame relay pseudo-wire is a mechanism that exists between a
   provider's edge network nodes and support as faithfully as possible
   frame relay services over MPLS packet switched network (PSN). This
   document describes the detailed encapsulation necessary to transport
   frame-relay packets over an MPLS network.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-pwe3-frame-relay-05.txt

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request@ietf.org with the word unsubscribe in the body of the message.  
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.


Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-pwe3-frame-relay-05.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-pwe3-frame-relay-05.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
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: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body; access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID: <2005-4-22162323.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-pwe3-frame-relay-05.txt

--OtherAccess
Content-Type: Message/External-body; name="draft-ietf-pwe3-frame-relay-05.txt";
	site="ftp.ietf.org"; access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2005-4-22162323.I-D@ietf.org>


--OtherAccess--

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

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

--NextPart--






From pwe3-bounces@ietf.org Mon Apr 25 06:56:48 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DQ1Gi-0006u4-Sd; Mon, 25 Apr 2005 06:56:48 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DQ1Gh-0006tz-EW
	for pwe3@megatron.ietf.org; Mon, 25 Apr 2005 06:56:47 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA05044
	for <pwe3@ietf.org>; Mon, 25 Apr 2005 06:56:44 -0400 (EDT)
Received: from ams-iport-1.cisco.com ([144.254.224.140])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DQ1Su-0002qV-Pj
	for pwe3@ietf.org; Mon, 25 Apr 2005 07:09:26 -0400
Received: from ams-core-1.cisco.com (144.254.224.150)
	by ams-iport-1.cisco.com with ESMTP; 25 Apr 2005 12:56:36 +0200
Received: from cisco.com (mrwint.cisco.com [64.103.71.48])
	by ams-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id j3PAuY54022592
	for <pwe3@ietf.org>; Mon, 25 Apr 2005 12:56:34 +0200 (MEST)
Received: from cisco.com (ams-clip-vpn-dhcp4223.cisco.com [10.61.80.126])
	by cisco.com (8.8.8-Cisco List Logging/8.8.8) with ESMTP id LAA28891;
	Mon, 25 Apr 2005 11:56:33 +0100 (BST)
Message-ID: <426CCCC5.5080002@cisco.com>
Date: Mon, 25 Apr 2005 11:56:05 +0100
From: Stewart Bryant <stbryant@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: pwe3 <pwe3@ietf.org>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 52f7a77164458f8c7b36b66787c853da
Content-Transfer-Encoding: 7bit
Subject: [PWE3] Generic vs Preferred CW
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=subscribe>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org

I am working on -04 of the CW draft that takes into a/c
the feedback that I have received from the list and
AD on -03.

Before I complete this I need to ask the list to
consider the following proposed text:

---------------------------------------------------------------


3.   Generic PW MPLS Control Word

    The Generic PW MPLS Control Word is shown in Figure 1.


     0                   1                   2                   3
     0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    |0 0 0 0|          Specified by PW Encapsulation                |
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

          Figure 1: Generic PW MPLS Control Word


    The PW set-up protocol or configuration mechanism determines whether
    a PW uses a PW MPLS Control Word (PWMCW). Bits 0..3 differ from the
    first four bits of an IP packet [BCP] and hence provide the
    necessary MPLS payload discrimination.

    When a PWMCW is used, it MUST adhere to the Generic MPLS Control
    Word format as illustrated in Figure 1 above. It SHOULD also follow
    the following format:


     0                   1                   2                   3
     0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    |0 0 0 0| Flags |FRG|  Length   | Sequence Number               |
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

         Figure 2: PW Preferred MPLS Control Word

    The meaning of the fields of the PW Preferred MPLS Control Word
    (Figure 2) is as follows:

--------------------------------------------------------------------

With the proposed changes to the CEP draft, the only encaps that do not
use the preferred CW is ATM 1 to 1 Cell Mode AAL5 PDU Frame Mode.

We therefore have two choices:

a) Leave the text above and thereby leave the ambiguity as to how
important it is to use preferred vs generic CW.

b) Change the text to say that the encap MUST use the Preferred
CW, and add exception text to the ATM draft.

I think that option (b) is better, because it requires
future encapsulations that do not adhere to the Preferred CW
to draw attention to the technical reasons why.

Views?

- Stewart

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



From pwe3-bounces@ietf.org Mon Apr 25 08:18:06 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DQ2XO-0003py-3k; Mon, 25 Apr 2005 08:18:06 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DQ2XM-0003pq-BR
	for pwe3@megatron.ietf.org; Mon, 25 Apr 2005 08:18:04 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA10439
	for <pwe3@ietf.org>; Mon, 25 Apr 2005 08:18:02 -0400 (EDT)
Received: from gateway.avici.com ([208.246.215.5] helo=mailhost.avici.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DQ2jb-0006iv-Ef
	for pwe3@ietf.org; Mon, 25 Apr 2005 08:30:43 -0400
Received: from aatlas-lt.avici.com (b2-pc249.avici.com [10.2.100.249])
	by mailhost.avici.com (8.12.8/8.12.8) with ESMTP id j3PCHk7l029817;
	Mon, 25 Apr 2005 08:17:47 -0400
Message-Id: <5.1.0.14.2.20050425081608.01fa3cb8@10.2.0.68>
X-Sender: aatlas@10.2.0.68
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Mon, 25 Apr 2005 08:17:03 -0400
To: Stewart Bryant <stbryant@cisco.com>
From: Alia Atlas <aatlas@avici.com>
Subject: Re: [PWE3] Generic vs Preferred CW
In-Reply-To: <426CCCC5.5080002@cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Avici-MailScanner-Information: Please contact the ISP for more information
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 6cca30437e2d04f45110f2ff8dc1b1d5
Cc: pwe3 <pwe3@ietf.org>
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=subscribe>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org

I agree that option (b) sounds better, because it requires an explicit 
reason to diverge.

Alia

At 06:56 AM 4/25/2005, Stewart Bryant wrote:
>I am working on -04 of the CW draft that takes into a/c
>the feedback that I have received from the list and
>AD on -03.
>
>Before I complete this I need to ask the list to
>consider the following proposed text:
>
>---------------------------------------------------------------
>
>
>3.   Generic PW MPLS Control Word
>
>    The Generic PW MPLS Control Word is shown in Figure 1.
>
>
>     0                   1                   2                   3
>     0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
>    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>    |0 0 0 0|          Specified by PW Encapsulation                |
>    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>
>          Figure 1: Generic PW MPLS Control Word
>
>
>    The PW set-up protocol or configuration mechanism determines whether
>    a PW uses a PW MPLS Control Word (PWMCW). Bits 0..3 differ from the
>    first four bits of an IP packet [BCP] and hence provide the
>    necessary MPLS payload discrimination.
>
>    When a PWMCW is used, it MUST adhere to the Generic MPLS Control
>    Word format as illustrated in Figure 1 above. It SHOULD also follow
>    the following format:
>
>
>     0                   1                   2                   3
>     0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
>    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>    |0 0 0 0| Flags |FRG|  Length   | Sequence Number               |
>    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>
>         Figure 2: PW Preferred MPLS Control Word
>
>    The meaning of the fields of the PW Preferred MPLS Control Word
>    (Figure 2) is as follows:
>
>--------------------------------------------------------------------
>
>With the proposed changes to the CEP draft, the only encaps that do not
>use the preferred CW is ATM 1 to 1 Cell Mode AAL5 PDU Frame Mode.
>
>We therefore have two choices:
>
>a) Leave the text above and thereby leave the ambiguity as to how
>important it is to use preferred vs generic CW.
>
>b) Change the text to say that the encap MUST use the Preferred
>CW, and add exception text to the ATM draft.
>
>I think that option (b) is better, because it requires
>future encapsulations that do not adhere to the Preferred CW
>to draw attention to the technical reasons why.
>
>Views?
>
>- Stewart
>
>_______________________________________________
>pwe3 mailing list
>pwe3@ietf.org
>https://www1.ietf.org/mailman/listinfo/pwe3



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



From pwe3-bounces@ietf.org Mon Apr 25 08:27:50 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DQ2go-0004Ux-0E; Mon, 25 Apr 2005 08:27:50 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DQ2gm-0004Us-5d
	for pwe3@megatron.ietf.org; Mon, 25 Apr 2005 08:27:48 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA11138
	for <pwe3@ietf.org>; Mon, 25 Apr 2005 08:27:46 -0400 (EDT)
Received: from mx100.qos.net.il ([80.74.96.6])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DQ2t1-0007AM-13
	for pwe3@ietf.org; Mon, 25 Apr 2005 08:40:27 -0400
Received: from tlv1.axerra.com (tlv1.axerra.com [80.74.100.68])
	by mx100.qos.net.il (8.12.8/8.12.8) with ESMTP id j3PCMbFB019007;
	Mon, 25 Apr 2005 15:22:37 +0300
Received: by TLV1 with Internet Mail Service (5.5.2653.19)
	id <GZ9PDF5B>; Mon, 25 Apr 2005 15:25:11 +0200
Message-ID: <AF5018AC03D1D411ABB70002A5091326015E1DB7@TLV1>
From: Sasha Vainshtein <Sasha@AXERRA.com>
To: "'Stewart Bryant'" <stbryant@cisco.com>
Subject: RE: [PWE3] Generic vs Preferred CW
Date: Mon, 25 Apr 2005 15:25:10 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="ISO-8859-8"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 093efd19b5f651b2707595638f6c4003
Cc: pwe3 <pwe3@ietf.org>
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=subscribe>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org


Stewart and all,
I believe that this issue has been raised many, many times on this list, 
but still...

Please note that while all the TDM (SAToP, CESoPSN, TDMoIP and now CEP) 
encapsulations comply with the format of the preferred CW, they
all use the sequence number field in a way that differs from the way 
it is used in the rest of the encasulations: 

- there is no option NOT to support sequencing 
- the value 0 is not diferent from any other value of the
  sequence number and is not skiped on wrap-around
- the sequence number in the first packet of the PW
  is set to a random number.

One of the non-historic reasons for this diffference is that
TDM PWs use sequence numbers not just to detect misordered and,
possibly lost packets, but also to compensate for each lost packet
and, where possible, to re-order mis-ordered packets. All this
must be done in the data path of the TDM PWs and becomes simpler 
if the circular sequence number space without any gaps is used.

Today the logic of setting and processing the sequence number is defined
in the service-specific drafts, and I do not see any reason why it
should not remain so. (In the case of multi-hop/multi-segment PWs
this logic shall, hopefully, be limited to U-PEs which are
service-specific.)

The bottom line:

I do not see any problem with enforcing the format of the preferred CW 
(i.e. Option "b") provided that specification of the usage of the sequence 
number field should be left to service-specific drafts.
  
Regards,
                                  Sasha Vainshtein
email:                         sasha@axerra.com <mailto:sasha@axerra.com> 
phone:                       +972-3-7569993 (office)
fax:                            +972-3-6487779
mobile:                      +972-52-8674833 


> -----Original Message-----
> From: Stewart Bryant [mailto:stbryant@cisco.com]
> Sent: Monday, April 25, 2005 12:56 PM
> To: pwe3
> Subject: [PWE3] Generic vs Preferred CW
> 
> 
> I am working on -04 of the CW draft that takes into a/c
> the feedback that I have received from the list and
> AD on -03.
> 
> Before I complete this I need to ask the list to
> consider the following proposed text:
> 
> ---------------------------------------------------------------
> 
> 
> 3.   Generic PW MPLS Control Word
> 
>     The Generic PW MPLS Control Word is shown in Figure 1.
> 
> 
>      0                   1                   2                   3
>      0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
>     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>     |0 0 0 0|          Specified by PW Encapsulation                |
>     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> 
>           Figure 1: Generic PW MPLS Control Word
> 
> 
>     The PW set-up protocol or configuration mechanism 
> determines whether
>     a PW uses a PW MPLS Control Word (PWMCW). Bits 0..3 
> differ from the
>     first four bits of an IP packet [BCP] and hence provide the
>     necessary MPLS payload discrimination.
> 
>     When a PWMCW is used, it MUST adhere to the Generic MPLS Control
>     Word format as illustrated in Figure 1 above. It SHOULD 
> also follow
>     the following format:
> 
> 
>      0                   1                   2                   3
>      0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
>     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>     |0 0 0 0| Flags |FRG|  Length   | Sequence Number               |
>     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> 
>          Figure 2: PW Preferred MPLS Control Word
> 
>     The meaning of the fields of the PW Preferred MPLS Control Word
>     (Figure 2) is as follows:
> 
> --------------------------------------------------------------------
> 
> With the proposed changes to the CEP draft, the only encaps 
> that do not
> use the preferred CW is ATM 1 to 1 Cell Mode AAL5 PDU Frame Mode.
> 
> We therefore have two choices:
> 
> a) Leave the text above and thereby leave the ambiguity as to how
> important it is to use preferred vs generic CW.
> 
> b) Change the text to say that the encap MUST use the Preferred
> CW, and add exception text to the ATM draft.
> 
> I think that option (b) is better, because it requires
> future encapsulations that do not adhere to the Preferred CW
> to draw attention to the technical reasons why.
> 
> Views?
> 
> - Stewart
> 
> _______________________________________________
> pwe3 mailing list
> pwe3@ietf.org
> https://www1.ietf.org/mailman/listinfo/pwe3
> 

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



From pwe3-bounces@ietf.org Mon Apr 25 09:05:58 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DQ3Hi-0007KV-MN; Mon, 25 Apr 2005 09:05:58 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DQ3Hg-0007KI-Uj
	for pwe3@megatron.ietf.org; Mon, 25 Apr 2005 09:05:57 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA13561
	for <pwe3@ietf.org>; Mon, 25 Apr 2005 09:05:48 -0400 (EDT)
Received: from radmail2.rad.co.il ([80.74.100.136] helo=antivir1.rad.co.il)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DQ3Tm-0008Q7-IH
	for pwe3@ietf.org; Mon, 25 Apr 2005 09:18:30 -0400
Received: from antivir1.rad.co.il (localhost [127.0.0.1])
	by antivir1.rad.co.il (8.12.10/8.12.10) with ESMTP id j3PD4I3Q004928
	for <pwe3@ietf.org>; Mon, 25 Apr 2005 16:04:20 +0300 (IDT)
Received: from exrad2.ad.rad.co.il (exrad2 [192.114.24.112])
	by antivir1.rad.co.il (8.12.10/8.12.10) with ESMTP id j3PD4Igd004925;
	Mon, 25 Apr 2005 16:04:18 +0300 (IDT)
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [PWE3] Generic vs Preferred CW
Date: Mon, 25 Apr 2005 16:04:34 +0200
Message-ID: <27A0F290348F8E45AEF79889DDE65A52046605E0@exrad2.ad.rad.co.il>
Thread-Topic: [PWE3] Generic vs Preferred CW
Thread-Index: AcVJmrdS8AKUHD3QTUOdZT5lWPH8qwAAyeVQ
From: "Yaakov Stein" <yaakov_s@rad.com>
To: "Sasha Vainshtein" <Sasha@AXERRA.com>,
	"Stewart Bryant" <stbryant@cisco.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3
Content-Transfer-Encoding: quoted-printable
Cc: pwe3 <pwe3@ietf.org>
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=subscribe>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org

 Sasha/Stewart,=20

We have already dealt with the sequencing function,
the only question now is whether to call the CW
format "preferred" (as in the ATM encap draft)
or "generic" (as in the CW draft) or "mandatory".

I think the term is superfluous,
as we can now simply call the CW presented
"the PWE control word"
(i.e. "THE PWE control word").

Is anyone really still interested in keeping
the nonstandard CW for some of the atm encap modes?
I know that this was part of the historic compromise,
but if the CEP draft fell in line, perhaps we can push
these into alignment too?

In any case, I am glad that 2 1/2 years after I originally
brought up the problem of the divergent CWs
in draft-stein-pwe3-controlword-00
(presented at the 55th IETF) my proposal
of agreeing on a single CW has finally (almost)=20
become a reality.

Y(J)S

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



From pwe3-bounces@ietf.org Mon Apr 25 09:09:08 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DQ3Km-0007eh-Me; Mon, 25 Apr 2005 09:09:08 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DQ3Kk-0007eZ-P9
	for pwe3@megatron.ietf.org; Mon, 25 Apr 2005 09:09:06 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA13791
	for <pwe3@ietf.org>; Mon, 25 Apr 2005 09:09:04 -0400 (EDT)
Received: from rtp-iport-1.cisco.com ([64.102.122.148])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DQ3Wz-00009i-2u
	for pwe3@ietf.org; Mon, 25 Apr 2005 09:21:46 -0400
Received: from rtp-core-1.cisco.com (64.102.124.12)
	by rtp-iport-1.cisco.com with ESMTP; 25 Apr 2005 09:20:52 -0400
X-IronPort-AV: i="3.92,128,1112587200"; 
	d="scan'208"; a="45951245:sNHT30086548"
Received: from [209.245.27.1] ([10.32.241.115])
	by rtp-core-1.cisco.com (8.12.10/8.12.6) with SMTP id j3PD8qRQ001479
	for <pwe3@ietf.org>; Mon, 25 Apr 2005 09:08:54 -0400 (EDT)
Message-ID: <426CEBE4.4050408@cisco.com>
Date: Mon, 25 Apr 2005 07:08:52 -0600
From: Luca Martini <lmartini@cisco.com>
User-Agent: Mozilla Thunderbird 1.0 (X11/20041208)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: pwe3@ietf.org
References: <200504221954.PAA18393@ietf.org>
In-Reply-To: <200504221954.PAA18393@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-PMX-Version: 4.7.0.111621
X-from-outside-Cisco: [10.32.241.115]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 21bf7a2f1643ae0bf20c1e010766eb78
Content-Transfer-Encoding: 7bit
Subject: [PWE3] Re: draft-ietf-pwe3-frame-relay-05.txt
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=subscribe>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org

Wg,


Please read this draft over , as it has been significantly re-written.

Changes:
- PSN terminology is almost gone, I reverted to "mpls network"
- Removed frame-relay port mode. IT is still mentioned, but the 
definition is now in the ppp/hdlc draft.
- Fixed lot's of grammar/spelling errors.
- removed unclear / superfluous text near the beginning of the draft
- Fixed author's addresses.


If there are no major issues I would like to WG last call this draft soon.

Thanks.
Luca



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 Pseudo Wire Emulation Edge to Edge Working Group of the IETF.
>
>	Title		: Encapsulation Methods for Transport of Frame Relay Over MPLS Networks
>	Author(s)	: L. Martini, C. Kawa
>	Filename	: draft-ietf-pwe3-frame-relay-05.txt
>	Pages		: 20
>	Date		: 2005-4-22
>	
>A frame relay pseudo-wire is a mechanism that exists between a
>   provider's edge network nodes and support as faithfully as possible
>   frame relay services over MPLS packet switched network (PSN). This
>   document describes the detailed encapsulation necessary to transport
>   frame-relay packets over an MPLS network.
>
>A URL for this Internet-Draft is:
>http://www.ietf.org/internet-drafts/draft-ietf-pwe3-frame-relay-05.txt
>
>To remove yourself from the I-D Announcement list, send a message to 
>i-d-announce-request@ietf.org with the word unsubscribe in the body of the message.  
>You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
>to change your subscription settings.
>
>
>Internet-Drafts are also available by anonymous FTP. Login with the username
>"anonymous" and a password of your e-mail address. After logging in,
>type "cd internet-drafts" and then
>	"get draft-ietf-pwe3-frame-relay-05.txt".
>
>A list of Internet-Drafts directories can be found in
>http://www.ietf.org/shadow.html 
>or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
>
>
>Internet-Drafts can also be obtained by e-mail.
>
>Send a message to:
>	mailserv@ietf.org.
>In the body type:
>	"FILE /internet-drafts/draft-ietf-pwe3-frame-relay-05.txt".
>	
>NOTE:	The mail server at ietf.org can return the document in
>	MIME-encoded form by using the "mpack" utility.  To use this
>	feature, insert the command "ENCODING mime" before the "FILE"
>	command.  To decode the response(s), you will need "munpack" or
>	a MIME-compliant mail reader.  Different MIME-compliant mail readers
>	exhibit different behavior, especially when dealing with
>	"multipart" MIME messages (i.e. documents which have been split
>	up into multiple messages), so check your local documentation on
>	how to manipulate these messages.
>		
>		
>Below is the data which will enable a MIME compliant mail reader
>implementation to automatically retrieve the ASCII version of the
>Internet-Draft.
>-------------------------------------------------------------------------
>CONTENT ABOVE THIS LINE IS *NOT* FROM CISCO INFORMATION TECHNOLOGY
>-------------------------------------------------------------------------
>In order to maintain computing infrastructure integrity, Cisco Systems
>Enterprise Messaging Services and InfoSec teams have set a mail policy
>disallowing executable attachments in email.
>
>This message contained an executable attachment type that is prohibited 
>by this policy. The attachment has been removed from this message and 
>copied to quarantine by our systems. It will be held in quarantine for
>seven days in the event that the content needs to be retrieved.
>
>Please be aware many viruses attempt to look like legitimate email or 
>notifications from anti-virus systems. We will clearly mark a seperation
>between our notifications and the original email as follows:
>
>  "CONTENT ABOVE THIS LINE IS *NOT* FROM CISCO INFORMATION TECHNOLOGY"
>
>For further reference information about viruses and email antivirus 
>efforts within Cisco, please visit:
>
>http://wwwin.cisco.com/it/ems/services/antiviral
>
>If your concern isn't addressed by the information in this notification 
>or the above web page, you may open a support request:
>
>http://wwwin.cisco.com/support/
>
>Select "Messaging", "Email-Related", "Mail Routing"
>
>Please include in the text of your case the following information:
>
>* Full headers of the message. Documentation on displaying the full 
>headers is available at this URL:
>
>http://wwwin.cisco.com/support/library/faqs/solution002471.html 
>
>* This unique quarantine identifier: j3MK2W5b021748
>
>If the matter is urgent, you may follow up by calling one of the below 
>referenced numbers. Please make every effort to provide the above 
>requested information via the support web tool prior to calling as it 
>will greatly aid the resolution of your issue.
>
>Americas:
>1 408 526 8888
>
>Asiapac
>+61 2 8446 8888
>
>EMEA
>+31 20 485 4888
>
>Japan
>+81 3 5549 6888
>
>US (Toll Free)
>1| 800| 888| 8187| (ext.68888)
>
>Thank you for your cooperation,
>
>Enterprise Messaging Services
>Cisco Systems, Inc
>  
>
>------------------------------------------------------------------------
>
>_______________________________________________
>pwe3 mailing list
>pwe3@ietf.org
>https://www1.ietf.org/mailman/listinfo/pwe3
>
>  
>

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



From pwe3-bounces@ietf.org Mon Apr 25 09:21:51 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DQ3X5-00005e-7F; Mon, 25 Apr 2005 09:21:51 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DQ3X3-00005W-Du
	for pwe3@megatron.ietf.org; Mon, 25 Apr 2005 09:21:49 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA14683
	for <pwe3@ietf.org>; Mon, 25 Apr 2005 09:21:47 -0400 (EDT)
Received: from ams-iport-1.cisco.com ([144.254.224.140])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DQ3jI-0000c1-So
	for pwe3@ietf.org; Mon, 25 Apr 2005 09:34:29 -0400
Received: from ams-core-1.cisco.com (144.254.224.150)
	by ams-iport-1.cisco.com with ESMTP; 25 Apr 2005 15:21:39 +0200
Received: from cisco.com (mrwint.cisco.com [64.103.71.48])
	by ams-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id j3PDLa54008558; 
	Mon, 25 Apr 2005 15:21:36 +0200 (MEST)
Received: from cisco.com (ams-clip-vpn-dhcp4427.cisco.com [10.61.81.74])
	by cisco.com (8.8.8-Cisco List Logging/8.8.8) with ESMTP id OAA11466;
	Mon, 25 Apr 2005 14:21:35 +0100 (BST)
Message-ID: <426CEEC0.9000404@cisco.com>
Date: Mon, 25 Apr 2005 14:21:04 +0100
From: Stewart Bryant <stbryant@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Sasha Vainshtein <Sasha@AXERRA.com>
Subject: Re: [PWE3] Generic vs Preferred CW 
References: <AF5018AC03D1D411ABB70002A5091326015E1DB7@TLV1>
In-Reply-To: <AF5018AC03D1D411ABB70002A5091326015E1DB7@TLV1>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 93e7fb8fef2e780414389440f367c879
Content-Transfer-Encoding: 7bit
Cc: pwe3 <pwe3@ietf.org>
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=subscribe>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org




Sasha Vainshtein wrote:
> Stewart and all,
> I believe that this issue has been raised many, many times on this list, 
> but still...
> 
> Please note that while all the TDM (SAToP, CESoPSN, TDMoIP and now CEP) 
> encapsulations comply with the format of the preferred CW, they
> all use the sequence number field in a way that differs from the way 
> it is used in the rest of the encasulations: 
> 
> - there is no option NOT to support sequencing 
> - the value 0 is not diferent from any other value of the
>   sequence number and is not skiped on wrap-around
> - the sequence number in the first packet of the PW
>   is set to a random number.
> 
> One of the non-historic reasons for this diffference is that
> TDM PWs use sequence numbers not just to detect misordered and,
> possibly lost packets, but also to compensate for each lost packet
> and, where possible, to re-order mis-ordered packets. All this
> must be done in the data path of the TDM PWs and becomes simpler 
> if the circular sequence number space without any gaps is used.
> 
> Today the logic of setting and processing the sequence number is defined
> in the service-specific drafts, and I do not see any reason why it
> should not remain so. (In the case of multi-hop/multi-segment PWs
> this logic shall, hopefully, be limited to U-PEs which are
> service-specific.)
> 
> The bottom line:
> 
> I do not see any problem with enforcing the format of the preferred CW 
> (i.e. Option "b") provided that specification of the usage of the sequence 
> number field should be left to service-specific drafts.

I was proposing to use the text that Yaakov recently proposed.
I will publish in a seperate thread.

Stewart

>   
> Regards,
>                                   Sasha Vainshtein
> email:                         sasha@axerra.com <mailto:sasha@axerra.com> 
> phone:                       +972-3-7569993 (office)
> fax:                            +972-3-6487779
> mobile:                      +972-52-8674833 
> 
> 
> 
>>-----Original Message-----
>>From: Stewart Bryant [mailto:stbryant@cisco.com]
>>Sent: Monday, April 25, 2005 12:56 PM
>>To: pwe3
>>Subject: [PWE3] Generic vs Preferred CW
>>
>>
>>I am working on -04 of the CW draft that takes into a/c
>>the feedback that I have received from the list and
>>AD on -03.
>>
>>Before I complete this I need to ask the list to
>>consider the following proposed text:
>>
>>---------------------------------------------------------------
>>
>>
>>3.   Generic PW MPLS Control Word
>>
>>    The Generic PW MPLS Control Word is shown in Figure 1.
>>
>>
>>     0                   1                   2                   3
>>     0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
>>    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>    |0 0 0 0|          Specified by PW Encapsulation                |
>>    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>
>>          Figure 1: Generic PW MPLS Control Word
>>
>>
>>    The PW set-up protocol or configuration mechanism 
>>determines whether
>>    a PW uses a PW MPLS Control Word (PWMCW). Bits 0..3 
>>differ from the
>>    first four bits of an IP packet [BCP] and hence provide the
>>    necessary MPLS payload discrimination.
>>
>>    When a PWMCW is used, it MUST adhere to the Generic MPLS Control
>>    Word format as illustrated in Figure 1 above. It SHOULD 
>>also follow
>>    the following format:
>>
>>
>>     0                   1                   2                   3
>>     0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
>>    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>    |0 0 0 0| Flags |FRG|  Length   | Sequence Number               |
>>    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>
>>         Figure 2: PW Preferred MPLS Control Word
>>
>>    The meaning of the fields of the PW Preferred MPLS Control Word
>>    (Figure 2) is as follows:
>>
>>--------------------------------------------------------------------
>>
>>With the proposed changes to the CEP draft, the only encaps 
>>that do not
>>use the preferred CW is ATM 1 to 1 Cell Mode AAL5 PDU Frame Mode.
>>
>>We therefore have two choices:
>>
>>a) Leave the text above and thereby leave the ambiguity as to how
>>important it is to use preferred vs generic CW.
>>
>>b) Change the text to say that the encap MUST use the Preferred
>>CW, and add exception text to the ATM draft.
>>
>>I think that option (b) is better, because it requires
>>future encapsulations that do not adhere to the Preferred CW
>>to draw attention to the technical reasons why.
>>
>>Views?
>>
>>- Stewart
>>
>>_______________________________________________
>>pwe3 mailing list
>>pwe3@ietf.org
>>https://www1.ietf.org/mailman/listinfo/pwe3
>>
> 
> 
> 

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



From pwe3-bounces@ietf.org Mon Apr 25 09:24:47 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DQ3Zv-0000T4-7Q; Mon, 25 Apr 2005 09:24:47 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DQ3Zt-0000Sj-FJ
	for pwe3@megatron.ietf.org; Mon, 25 Apr 2005 09:24:45 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA14977
	for <pwe3@ietf.org>; Mon, 25 Apr 2005 09:24:43 -0400 (EDT)
Received: from ams-iport-1.cisco.com ([144.254.224.140])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DQ3m9-0000ju-6R
	for pwe3@ietf.org; Mon, 25 Apr 2005 09:37:25 -0400
Received: from ams-core-1.cisco.com (144.254.224.150)
	by ams-iport-1.cisco.com with ESMTP; 25 Apr 2005 15:24:36 +0200
Received: from cisco.com (mrwint.cisco.com [64.103.71.48])
	by ams-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id j3PDOX54009468
	for <pwe3@ietf.org>; Mon, 25 Apr 2005 15:24:34 +0200 (MEST)
Received: from cisco.com (ams-clip-vpn-dhcp4427.cisco.com [10.61.81.74])
	by cisco.com (8.8.8-Cisco List Logging/8.8.8) with ESMTP id OAA11704;
	Mon, 25 Apr 2005 14:24:32 +0100 (BST)
Message-ID: <426CEF72.5080707@cisco.com>
Date: Mon, 25 Apr 2005 14:24:02 +0100
From: Stewart Bryant <stbryant@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: pwe3 <pwe3@ietf.org>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32
Content-Transfer-Encoding: 7bit
Subject: [PWE3] Sequence numbers
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=subscribe>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org

Since Sasha raises it, here is the sequence number text
proposed by Yaakov.

I will wait to see the consenus on the a/b choice and then
publish control word -04 in a day or so.

Stewart

Sequence number (Bit 16 to 31):

           The sequence number implements the sequencing function
           [RFC3985]. For some emulated services usage of the sequence
           number field is OPTIONAL while for others it is MANDATORY.
           For services for which usage is MANDATORY, the sequence
           number cycles over all values from 0 to 65535 (2**16-1).

           For services for which usage is OPTIONAL, when the sequence
           number is used it cycles from 1 to 65535 (2**16-1), and a
           zero value indicates that it is not used.

           The size of the window used for packet acceptance is
           dependent on the parameters of both the PW and the MPLS PSN,
           and SHOULD be configurable. The mechanism used by a receiver
           to synchronize the expected and received sequence numbers
           is implementation dependent.

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



From pwe3-bounces@ietf.org Mon Apr 25 10:02:28 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DQ4AO-00039C-6J; Mon, 25 Apr 2005 10:02:28 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DQ4AL-000397-Or
	for pwe3@megatron.ietf.org; Mon, 25 Apr 2005 10:02:26 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA17089
	for <pwe3@ietf.org>; Mon, 25 Apr 2005 10:02:23 -0400 (EDT)
Received: from sccrmhc12.comcast.net ([204.127.202.56])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DQ4MZ-0001vG-Ov
	for pwe3@ietf.org; Mon, 25 Apr 2005 10:15:06 -0400
Received: from default.mail.com (unknown[12.46.111.111])
	by comcast.net (sccrmhc12) with SMTP
	id <20050425140213012005r1n5e>; Mon, 25 Apr 2005 14:02:14 +0000
Message-Id: <6.2.1.2.2.20050425094746.057c4a20@mail.comcast.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.1.2
Date: Mon, 25 Apr 2005 10:02:12 -0400
To: Stewart Bryant <stbryant@cisco.com>
From: "Andrew G. Malis" <andymalis@comcast.net>
Subject: Re: [PWE3] Generic vs Preferred CW
In-Reply-To: <426CCCC5.5080002@cisco.com>
References: <426CCCC5.5080002@cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 73734d43604d52d23b3eba644a169745
Cc: "Ash, Gerald R \(Jerry\), ALABS" <gash@att.com>, pwe3 <pwe3@ietf.org>
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=subscribe>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org

Stewart,

I prefer option a.  There is now another draft, 
http://www.ietf.org/internet-drafts/draft-ash-avt-hc-over-mpls-protocol-00.txt 
, that follows the generic control word (the first four bits are 0000) but 
diverges from the preferred CW.  This draft defines a new pseudowire type, 
header-compressed VoIP over MPLS (voice/RTP/UDP/IP/MPLS labels).  The CW is 
only one octet in length, because for this application every octet counts 
and packet reordering is allowed.

Thanks,
Andy

---------

At 4/25/2005 11:56 +0100, Stewart Bryant wrote:
>I am working on -04 of the CW draft that takes into a/c
>the feedback that I have received from the list and
>AD on -03.
>
>Before I complete this I need to ask the list to
>consider the following proposed text:
>
>---------------------------------------------------------------
>
>
>3.   Generic PW MPLS Control Word
>
>    The Generic PW MPLS Control Word is shown in Figure 1.
>
>
>     0                   1                   2                   3
>     0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
>    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>    |0 0 0 0|          Specified by PW Encapsulation                |
>    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>
>          Figure 1: Generic PW MPLS Control Word
>
>
>    The PW set-up protocol or configuration mechanism determines whether
>    a PW uses a PW MPLS Control Word (PWMCW). Bits 0..3 differ from the
>    first four bits of an IP packet [BCP] and hence provide the
>    necessary MPLS payload discrimination.
>
>    When a PWMCW is used, it MUST adhere to the Generic MPLS Control
>    Word format as illustrated in Figure 1 above. It SHOULD also follow
>    the following format:
>
>
>     0                   1                   2                   3
>     0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
>    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>    |0 0 0 0| Flags |FRG|  Length   | Sequence Number               |
>    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>
>         Figure 2: PW Preferred MPLS Control Word
>
>    The meaning of the fields of the PW Preferred MPLS Control Word
>    (Figure 2) is as follows:
>
>--------------------------------------------------------------------
>
>With the proposed changes to the CEP draft, the only encaps that do not
>use the preferred CW is ATM 1 to 1 Cell Mode AAL5 PDU Frame Mode.
>
>We therefore have two choices:
>
>a) Leave the text above and thereby leave the ambiguity as to how
>important it is to use preferred vs generic CW.
>
>b) Change the text to say that the encap MUST use the Preferred
>CW, and add exception text to the ATM draft.
>
>I think that option (b) is better, because it requires
>future encapsulations that do not adhere to the Preferred CW
>to draw attention to the technical reasons why.
>
>Views?
>
>- Stewart
>
>_______________________________________________
>pwe3 mailing list
>pwe3@ietf.org
>https://www1.ietf.org/mailman/listinfo/pwe3


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



From pwe3-bounces@ietf.org Mon Apr 25 10:09:09 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DQ4Gr-0003en-JB; Mon, 25 Apr 2005 10:09:09 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DQ4Gq-0003ef-Fn
	for pwe3@megatron.ietf.org; Mon, 25 Apr 2005 10:09:08 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA17863
	for <pwe3@ietf.org>; Mon, 25 Apr 2005 10:09:06 -0400 (EDT)
Received: from mx100.qos.net.il ([80.74.96.6])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DQ4T4-0002BX-84
	for pwe3@ietf.org; Mon, 25 Apr 2005 10:21:48 -0400
Received: from tlv1.axerra.com (tlv1.axerra.com [80.74.100.68])
	by mx100.qos.net.il (8.12.8/8.12.8) with ESMTP id j3PE2wFB021260;
	Mon, 25 Apr 2005 17:02:58 +0300
Received: by TLV1 with Internet Mail Service (5.5.2653.19)
	id <GZ9PDGAR>; Mon, 25 Apr 2005 17:05:32 +0200
Message-ID: <AF5018AC03D1D411ABB70002A5091326015E1DBB@TLV1>
From: Sasha Vainshtein <Sasha@AXERRA.com>
To: "'Stewart Bryant'" <stbryant@cisco.com>, "Yaakov Stein (E-mail)"
	<yaakov_s@rad.com>
Subject: RE: [PWE3] Sequence numbers
Date: Mon, 25 Apr 2005 17:05:31 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="ISO-8859-8"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 52f7a77164458f8c7b36b66787c853da
Cc: pwe3 <pwe3@ietf.org>
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=subscribe>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org

Stewart, Yaakov and all,
I am not sure that the binding between MANDATORY/OPTIONAL 
sequencing support and skipping zero is a good idea even if
it happens to reflect correctly the current state of things.

Please consider the hypothetical use case when, for some reason, 
the ATM N-to-one Cell PW encapsulation changes its currently OPTIONAL 
sequencing support to MANDATORY (may be not quite a crazy idea because
this is the only way to guarantee that ATM PM works properly across
these PWs). Such a change would make ALL the implementations - both ones 
that did not support sequencing and ones that did - non-compliant
because the sequencing method must be now changed in the latter, not just
added to the former...

Passing the description of how the sequencing is performed to the 
service-specific documents looks much more stable to me.

Regards,
                                  Sasha Vainshtein
email:                         sasha@axerra.com <mailto:sasha@axerra.com> 
phone:                       +972-3-7569993 (office)
fax:                            +972-3-6487779
mobile:                      +972-52-8674833 


> -----Original Message-----
> From: Stewart Bryant [mailto:stbryant@cisco.com]
> Sent: Monday, April 25, 2005 3:24 PM
> To: pwe3
> Subject: [PWE3] Sequence numbers
> 
> 
> Since Sasha raises it, here is the sequence number text
> proposed by Yaakov.
> 
> I will wait to see the consenus on the a/b choice and then
> publish control word -04 in a day or so.
> 
> Stewart
> 
> Sequence number (Bit 16 to 31):
> 
>            The sequence number implements the sequencing function
>            [RFC3985]. For some emulated services usage of the sequence
>            number field is OPTIONAL while for others it is MANDATORY.
>            For services for which usage is MANDATORY, the sequence
>            number cycles over all values from 0 to 65535 (2**16-1).
> 
>            For services for which usage is OPTIONAL, when the sequence
>            number is used it cycles from 1 to 65535 (2**16-1), and a
>            zero value indicates that it is not used.
> 
>            The size of the window used for packet acceptance is
>            dependent on the parameters of both the PW and the 
> MPLS PSN,
>            and SHOULD be configurable. The mechanism used by 
> a receiver
>            to synchronize the expected and received sequence numbers
>            is implementation dependent.
> 
> _______________________________________________
> pwe3 mailing list
> pwe3@ietf.org
> https://www1.ietf.org/mailman/listinfo/pwe3
> 

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



From pwe3-bounces@ietf.org Mon Apr 25 10:17:54 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DQ4PK-0004Vw-Nd; Mon, 25 Apr 2005 10:17:54 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DQ4PI-0004Vr-LA
	for pwe3@megatron.ietf.org; Mon, 25 Apr 2005 10:17:52 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA19018
	for <pwe3@ietf.org>; Mon, 25 Apr 2005 10:17:50 -0400 (EDT)
Received: from kanfw1.ottawa.alcatel.ca ([192.75.23.69]
	helo=tm3.ca.alcatel.com) by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DQ4bW-0002Tv-Ic
	for pwe3@ietf.org; Mon, 25 Apr 2005 10:30:33 -0400
Received: from caottn00499 (localhost [127.0.0.1])
	by tm3.ca.alcatel.com (8.13.0/8.13.0) with ESMTP id j3PEHYgJ004320;
	Mon, 25 Apr 2005 10:17:35 -0400 (EDT)
Message-Id: <200504251417.j3PEHYgJ004320@tm3.ca.alcatel.com>
From: "Mustapha Aissaoui" <mustapha.aissaoui@alcatel.com>
To: "'Andrew G. Malis'" <andymalis@comcast.net>,
	"'Stewart Bryant'" <stbryant@cisco.com>
Subject: RE: [PWE3] Generic vs Preferred CW
Date: Mon, 25 Apr 2005 10:14:18 -0400
X-Mailer: Microsoft Office Outlook, Build 11.0.6353
In-reply-to: <6.2.1.2.2.20050425094746.057c4a20@mail.comcast.net>
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
Thread-index: AcVJn69SnDUKkSZLRj2JLi2Z6FFZ+AAAMzew
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 6d95a152022472c7d6cdf886a0424dc6
Cc: "'Ash, Gerald R \(Jerry\), ALABS'" <gash@att.com>, 'pwe3' <pwe3@ietf.org>
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=subscribe>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org

I agree with Andy. Option (a) is all what is required for the BCP. We cannot
anticipate the preffered control word will be suitable to future application
of PWs.

Regards,
Mustapha.

-----Original Message-----
From: pwe3-bounces@ietf.org [mailto:pwe3-bounces@ietf.org] On Behalf Of
Andrew G. Malis
Sent: Monday, April 25, 2005 10:02 AM
To: Stewart Bryant
Cc: Ash, Gerald R (Jerry), ALABS; pwe3
Subject: Re: [PWE3] Generic vs Preferred CW

Stewart,

I prefer option a.  There is now another draft,
http://www.ietf.org/internet-drafts/draft-ash-avt-hc-over-mpls-protocol-00.t
xt
, that follows the generic control word (the first four bits are 0000) but
diverges from the preferred CW.  This draft defines a new pseudowire type,
header-compressed VoIP over MPLS (voice/RTP/UDP/IP/MPLS labels).  The CW is
only one octet in length, because for this application every octet counts
and packet reordering is allowed.

Thanks,
Andy

---------

At 4/25/2005 11:56 +0100, Stewart Bryant wrote:
>I am working on -04 of the CW draft that takes into a/c the feedback
>that I have received from the list and AD on -03.
>
>Before I complete this I need to ask the list to consider the following
>proposed text:
>
>---------------------------------------------------------------
>
>
>3.   Generic PW MPLS Control Word
>
>    The Generic PW MPLS Control Word is shown in Figure 1.
>
>
>     0                   1                   2                   3
>     0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
>    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>    |0 0 0 0|          Specified by PW Encapsulation                |
>    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>
>          Figure 1: Generic PW MPLS Control Word
>
>
>    The PW set-up protocol or configuration mechanism determines whether
>    a PW uses a PW MPLS Control Word (PWMCW). Bits 0..3 differ from the
>    first four bits of an IP packet [BCP] and hence provide the
>    necessary MPLS payload discrimination.
>
>    When a PWMCW is used, it MUST adhere to the Generic MPLS Control
>    Word format as illustrated in Figure 1 above. It SHOULD also follow
>    the following format:
>
>
>     0                   1                   2                   3
>     0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
>    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>    |0 0 0 0| Flags |FRG|  Length   | Sequence Number               |
>    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>
>         Figure 2: PW Preferred MPLS Control Word
>
>    The meaning of the fields of the PW Preferred MPLS Control Word
>    (Figure 2) is as follows:
>
>--------------------------------------------------------------------
>
>With the proposed changes to the CEP draft, the only encaps that do not
>use the preferred CW is ATM 1 to 1 Cell Mode AAL5 PDU Frame Mode.
>
>We therefore have two choices:
>
>a) Leave the text above and thereby leave the ambiguity as to how
>important it is to use preferred vs generic CW.
>
>b) Change the text to say that the encap MUST use the Preferred CW, and
>add exception text to the ATM draft.
>
>I think that option (b) is better, because it requires future
>encapsulations that do not adhere to the Preferred CW to draw attention
>to the technical reasons why.
>
>Views?
>
>- Stewart
>
>_______________________________________________
>pwe3 mailing list
>pwe3@ietf.org
>https://www1.ietf.org/mailman/listinfo/pwe3


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



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



From pwe3-bounces@ietf.org Mon Apr 25 10:48:56 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DQ4tM-0007pl-GP; Mon, 25 Apr 2005 10:48:56 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DQ4tK-0007pT-Sc
	for pwe3@megatron.ietf.org; Mon, 25 Apr 2005 10:48:54 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA21948
	for <pwe3@ietf.org>; Mon, 25 Apr 2005 10:48:52 -0400 (EDT)
Received: from ams-iport-1.cisco.com ([144.254.224.140])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DQ55a-0003iP-A7
	for pwe3@ietf.org; Mon, 25 Apr 2005 11:01:35 -0400
Received: from ams-core-1.cisco.com (144.254.224.150)
	by ams-iport-1.cisco.com with ESMTP; 25 Apr 2005 16:48:45 +0200
Received: from cisco.com (ams-clip-vpn-dhcp286.cisco.com [10.61.65.30])
	by ams-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id j3PEme54004531; 
	Mon, 25 Apr 2005 16:48:41 +0200 (MEST)
Message-ID: <426D0345.3070105@cisco.com>
Date: Mon, 25 Apr 2005 15:48:37 +0100
From: Stewart Bryant <stbryant@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Sasha Vainshtein <Sasha@AXERRA.com>
Subject: Re: [PWE3] Sequence numbers
References: <AF5018AC03D1D411ABB70002A5091326015E1DBB@TLV1>
In-Reply-To: <AF5018AC03D1D411ABB70002A5091326015E1DBB@TLV1>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 10ba05e7e8a9aa6adb025f426bef3a30
Content-Transfer-Encoding: 7bit
Cc: "Yaakov Stein \(E-mail\)" <yaakov_s@rad.com>, pwe3 <pwe3@ietf.org>
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=subscribe>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org



Sasha Vainshtein wrote:

> Stewart, Yaakov and all,
> I am not sure that the binding between MANDATORY/OPTIONAL 
> sequencing support and skipping zero is a good idea even if
> it happens to reflect correctly the current state of things.
> 
> Please consider the hypothetical use case when, for some reason, 
> the ATM N-to-one Cell PW encapsulation changes its currently OPTIONAL 
> sequencing support to MANDATORY (may be not quite a crazy idea because
> this is the only way to guarantee that ATM PM works properly across
> these PWs). Such a change would make ALL the implementations - both ones 
> that did not support sequencing and ones that did - non-compliant
> because the sequencing method must be now changed in the latter, not just
> added to the former...
> 
> Passing the description of how the sequencing is performed to the 
> service-specific documents looks much more stable to me.

Sasha

It seems unlikely that we will need a third type of sequence number
design unless we move to a larger number. It would therefore be
a good thing if we could write down in one place the description
of the two cases. Perhaps we could find a better pair of words
than OPTIONAL/MANDATORY to describe the two cases.

Stewart

> 
> Regards,
>                                   Sasha Vainshtein
> email:                         sasha@axerra.com <mailto:sasha@axerra.com> 
> phone:                       +972-3-7569993 (office)
> fax:                            +972-3-6487779
> mobile:                      +972-52-8674833 
> 
> 
> 
>>-----Original Message-----
>>From: Stewart Bryant [mailto:stbryant@cisco.com]
>>Sent: Monday, April 25, 2005 3:24 PM
>>To: pwe3
>>Subject: [PWE3] Sequence numbers
>>
>>
>>Since Sasha raises it, here is the sequence number text
>>proposed by Yaakov.
>>
>>I will wait to see the consenus on the a/b choice and then
>>publish control word -04 in a day or so.
>>
>>Stewart
>>
>>Sequence number (Bit 16 to 31):
>>
>>           The sequence number implements the sequencing function
>>           [RFC3985]. For some emulated services usage of the sequence
>>           number field is OPTIONAL while for others it is MANDATORY.
>>           For services for which usage is MANDATORY, the sequence
>>           number cycles over all values from 0 to 65535 (2**16-1).
>>
>>           For services for which usage is OPTIONAL, when the sequence
>>           number is used it cycles from 1 to 65535 (2**16-1), and a
>>           zero value indicates that it is not used.
>>
>>           The size of the window used for packet acceptance is
>>           dependent on the parameters of both the PW and the 
>>MPLS PSN,
>>           and SHOULD be configurable. The mechanism used by 
>>a receiver
>>           to synchronize the expected and received sequence numbers
>>           is implementation dependent.
>>
>>_______________________________________________
>>pwe3 mailing list
>>pwe3@ietf.org
>>https://www1.ietf.org/mailman/listinfo/pwe3
>>
> 
> 
> _______________________________________________
> pwe3 mailing list
> pwe3@ietf.org
> https://www1.ietf.org/mailman/listinfo/pwe3
> 
> 

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



From pwe3-bounces@ietf.org Mon Apr 25 10:49:17 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DQ4th-0007sK-2Q; Mon, 25 Apr 2005 10:49:17 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DQ4tf-0007r4-1g
	for pwe3@megatron.ietf.org; Mon, 25 Apr 2005 10:49:15 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA21973
	for <pwe3@ietf.org>; Mon, 25 Apr 2005 10:49:10 -0400 (EDT)
Received: from rwcrmhc12.comcast.net ([216.148.227.85])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DQ55s-0003il-Cr
	for pwe3@ietf.org; Mon, 25 Apr 2005 11:01:53 -0400
Received: from default.mail.com (unknown[12.46.111.111])
	by comcast.net (rwcrmhc12) with SMTP
	id <2005042514485501400qb97be>; Mon, 25 Apr 2005 14:49:01 +0000
Message-Id: <6.2.1.2.2.20050425104823.05815190@mail.comcast.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.1.2
Date: Mon, 25 Apr 2005 10:48:53 -0400
To: Sasha Vainshtein <Sasha@AXERRA.com>
From: "Andrew G. Malis" <andymalis@comcast.net>
Subject: RE: [PWE3] Sequence numbers
In-Reply-To: <AF5018AC03D1D411ABB70002A5091326015E1DBB@TLV1>
References: <AF5018AC03D1D411ABB70002A5091326015E1DBB@TLV1>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cd26b070c2577ac175cd3a6d878c6248
Cc: "Yaakov Stein \(E-mail\)" <yaakov_s@rad.com>, pwe3 <pwe3@ietf.org>,
	'Stewart Bryant' <stbryant@cisco.com>
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=subscribe>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org

I agree with Sasha's comment below.

Cheers,
Andy

----------

At 4/25/2005 17:05 +0200, Sasha Vainshtein wrote:
>Stewart, Yaakov and all,
>I am not sure that the binding between MANDATORY/OPTIONAL
>sequencing support and skipping zero is a good idea even if
>it happens to reflect correctly the current state of things.
>
>Please consider the hypothetical use case when, for some reason,
>the ATM N-to-one Cell PW encapsulation changes its currently OPTIONAL
>sequencing support to MANDATORY (may be not quite a crazy idea because
>this is the only way to guarantee that ATM PM works properly across
>these PWs). Such a change would make ALL the implementations - both ones
>that did not support sequencing and ones that did - non-compliant
>because the sequencing method must be now changed in the latter, not just
>added to the former...
>
>Passing the description of how the sequencing is performed to the
>service-specific documents looks much more stable to me.
>
>Regards,
>                                   Sasha Vainshtein
>email:                         sasha@axerra.com <mailto:sasha@axerra.com>
>phone:                       +972-3-7569993 (office)
>fax:                            +972-3-6487779
>mobile:                      +972-52-8674833
>
>
> > -----Original Message-----
> > From: Stewart Bryant [mailto:stbryant@cisco.com]
> > Sent: Monday, April 25, 2005 3:24 PM
> > To: pwe3
> > Subject: [PWE3] Sequence numbers
> >
> >
> > Since Sasha raises it, here is the sequence number text
> > proposed by Yaakov.
> >
> > I will wait to see the consenus on the a/b choice and then
> > publish control word -04 in a day or so.
> >
> > Stewart
> >
> > Sequence number (Bit 16 to 31):
> >
> >            The sequence number implements the sequencing function
> >            [RFC3985]. For some emulated services usage of the sequence
> >            number field is OPTIONAL while for others it is MANDATORY.
> >            For services for which usage is MANDATORY, the sequence
> >            number cycles over all values from 0 to 65535 (2**16-1).
> >
> >            For services for which usage is OPTIONAL, when the sequence
> >            number is used it cycles from 1 to 65535 (2**16-1), and a
> >            zero value indicates that it is not used.
> >
> >            The size of the window used for packet acceptance is
> >            dependent on the parameters of both the PW and the
> > MPLS PSN,
> >            and SHOULD be configurable. The mechanism used by
> > a receiver
> >            to synchronize the expected and received sequence numbers
> >            is implementation dependent.
> >
> > _______________________________________________
> > pwe3 mailing list
> > pwe3@ietf.org
> > https://www1.ietf.org/mailman/listinfo/pwe3
> >
>
>_______________________________________________
>pwe3 mailing list
>pwe3@ietf.org
>https://www1.ietf.org/mailman/listinfo/pwe3


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



From pwe3-bounces@ietf.org Mon Apr 25 11:15:38 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DQ5JC-0001rh-4b; Mon, 25 Apr 2005 11:15:38 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DQ5JA-0001ra-T3
	for pwe3@megatron.ietf.org; Mon, 25 Apr 2005 11:15:36 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA23607
	for <pwe3@ietf.org>; Mon, 25 Apr 2005 11:15:34 -0400 (EDT)
Received: from mx100.qos.net.il ([80.74.96.6])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DQ5VR-0004dZ-82
	for pwe3@ietf.org; Mon, 25 Apr 2005 11:28:17 -0400
Received: from tlv1.axerra.com (tlv1.axerra.com [80.74.100.68])
	by mx100.qos.net.il (8.12.8/8.12.8) with ESMTP id j3PFASFB022580;
	Mon, 25 Apr 2005 18:10:28 +0300
Received: by TLV1 with Internet Mail Service (5.5.2653.19)
	id <GZ9PDGFJ>; Mon, 25 Apr 2005 18:13:02 +0200
Message-ID: <AF5018AC03D1D411ABB70002A5091326015E1DBE@TLV1>
From: Sasha Vainshtein <Sasha@AXERRA.com>
To: "'Stewart Bryant'" <stbryant@cisco.com>
Subject: RE: [PWE3] Sequence numbers
Date: Mon, 25 Apr 2005 18:13:01 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="ISO-8859-8"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b2809b6f39decc6de467dcf252f42af1
Cc: "Yaakov Stein \(E-mail\)" <yaakov_s@rad.com>, pwe3 <pwe3@ietf.org>
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=subscribe>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org

Stewart and all,

Please see some comments inline below.




Regards,
                                  Sasha Vainshtein
email:                         sasha@axerra.com <mailto:sasha@axerra.com> 
phone:                       +972-3-7569993 (office)
fax:                            +972-3-6487779
mobile:                      +972-52-8674833 


> -----Original Message-----
> From: Stewart Bryant [mailto:stbryant@cisco.com]
> Sent: Monday, April 25, 2005 4:49 PM
> To: Sasha Vainshtein
> Cc: Yaakov Stein (E-mail); pwe3
> Subject: Re: [PWE3] Sequence numbers
> 
> 
> 
> 
> Sasha Vainshtein wrote:
> 
> > Stewart, Yaakov and all,
> > I am not sure that the binding between MANDATORY/OPTIONAL 
> > sequencing support and skipping zero is a good idea even if
> > it happens to reflect correctly the current state of things.
> > 
> > Please consider the hypothetical use case when, for some reason, 
> > the ATM N-to-one Cell PW encapsulation changes its 
> currently OPTIONAL 
> > sequencing support to MANDATORY (may be not quite a crazy 
> idea because
> > this is the only way to guarantee that ATM PM works properly across
> > these PWs). Such a change would make ALL the 
> implementations - both ones 
> > that did not support sequencing and ones that did - non-compliant
> > because the sequencing method must be now changed in the 
> latter, not just
> > added to the former...
> > 
> > Passing the description of how the sequencing is performed to the 
> > service-specific documents looks much more stable to me.
> 
> Sasha
> 
> It seems unlikely that we will need a third type of sequence number
> design unless we move to a larger number. 
>
[Sasha] I hope so.
>
> It would therefore be a good thing if we could write down in one 
> place the description of the two cases. 
>
[Sasha] Sure - if the mapping between the specific encapsulations
and the common methods can be defined in a stable way. 
Otherwise we can provide the description of the two cases 
(possibly with some hints to their respective pros and cons) 
and leave the definition of the specific mapping in the 
service-specific documents. 
>
> Perhaps we could find a better pair of words
> than OPTIONAL/MANDATORY to describe the two cases.
> Stewart
> 
> > 
> > Regards,
> >                                   Sasha Vainshtein
> > email:                         sasha@axerra.com 
<mailto:sasha@axerra.com> 
> phone:                       +972-3-7569993 (office)
> fax:                            +972-3-6487779
> mobile:                      +972-52-8674833 
> 
> 
> 
>>-----Original Message-----
>>From: Stewart Bryant [mailto:stbryant@cisco.com]
>>Sent: Monday, April 25, 2005 3:24 PM
>>To: pwe3
>>Subject: [PWE3] Sequence numbers
>>
>>
>>Since Sasha raises it, here is the sequence number text
>>proposed by Yaakov.
>>
>>I will wait to see the consenus on the a/b choice and then
>>publish control word -04 in a day or so.
>>
>>Stewart
>>
>>Sequence number (Bit 16 to 31):
>>
>>           The sequence number implements the sequencing function
>>           [RFC3985]. For some emulated services usage of the sequence
>>           number field is OPTIONAL while for others it is MANDATORY.
>>           For services for which usage is MANDATORY, the sequence
>>           number cycles over all values from 0 to 65535 (2**16-1).
>>
>>           For services for which usage is OPTIONAL, when the sequence
>>           number is used it cycles from 1 to 65535 (2**16-1), and a
>>           zero value indicates that it is not used.
>>
>>           The size of the window used for packet acceptance is
>>           dependent on the parameters of both the PW and the 
>>MPLS PSN,
>>           and SHOULD be configurable. The mechanism used by 
>>a receiver
>>           to synchronize the expected and received sequence numbers
>>           is implementation dependent.
>>
>>_______________________________________________
>>pwe3 mailing list
>>pwe3@ietf.org
>>https://www1.ietf.org/mailman/listinfo/pwe3
>>
> 
> 
> _______________________________________________
> pwe3 mailing list
> pwe3@ietf.org
> https://www1.ietf.org/mailman/listinfo/pwe3
> 
> 

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



From pwe3-bounces@ietf.org Mon Apr 25 11:41:04 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DQ5hn-0004qf-T5; Mon, 25 Apr 2005 11:41:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DQ5hn-0004qa-43
	for pwe3@megatron.ietf.org; Mon, 25 Apr 2005 11:41:03 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA25882
	for <pwe3@ietf.org>; Mon, 25 Apr 2005 11:41:00 -0400 (EDT)
Received: from rtp-iport-1.cisco.com ([64.102.122.148])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DQ5u2-0005aj-W8
	for pwe3@ietf.org; Mon, 25 Apr 2005 11:53:44 -0400
Received: from rtp-core-2.cisco.com (64.102.124.13)
	by rtp-iport-1.cisco.com with ESMTP; 25 Apr 2005 11:52:50 -0400
X-IronPort-AV: i="3.92,128,1112587200"; 
	d="scan'208"; a="45980541:sNHT79650342"
Received: from [209.245.27.1] ([10.32.241.115])
	by rtp-core-2.cisco.com (8.12.10/8.12.6) with SMTP id j3PFekdr006063;
	Mon, 25 Apr 2005 11:40:49 -0400 (EDT)
Message-ID: <426D0F7D.6070506@cisco.com>
Date: Mon, 25 Apr 2005 09:40:45 -0600
From: Luca Martini <lmartini@cisco.com>
User-Agent: Mozilla Thunderbird 1.0 (X11/20041208)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Yaakov Stein <yaakov_s@rad.com>
Subject: Re: [PWE3] Generic vs Preferred CW
References: <27A0F290348F8E45AEF79889DDE65A52046605E0@exrad2.ad.rad.co.il>
In-Reply-To: <27A0F290348F8E45AEF79889DDE65A52046605E0@exrad2.ad.rad.co.il>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-PMX-Version: 4.7.0.111621
X-from-outside-Cisco: [10.32.241.115]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9ed51c9d1356100bce94f1ae4ec616a9
Content-Transfer-Encoding: 7bit
Cc: pwe3 <pwe3@ietf.org>, Sasha Vainshtein <Sasha@AXERRA.com>,
	Stewart Bryant <stbryant@cisco.com>
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=subscribe>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org

Yaakov,

I agree , let's just remove the mandatory/optional/show words.
Option a sounds better otherwise.

Luca

Yaakov Stein wrote:

> Sasha/Stewart, 
>
>We have already dealt with the sequencing function,
>the only question now is whether to call the CW
>format "preferred" (as in the ATM encap draft)
>or "generic" (as in the CW draft) or "mandatory".
>
>I think the term is superfluous,
>as we can now simply call the CW presented
>"the PWE control word"
>(i.e. "THE PWE control word").
>
>Is anyone really still interested in keeping
>the nonstandard CW for some of the atm encap modes?
>I know that this was part of the historic compromise,
>but if the CEP draft fell in line, perhaps we can push
>these into alignment too?
>
>In any case, I am glad that 2 1/2 years after I originally
>brought up the problem of the divergent CWs
>in draft-stein-pwe3-controlword-00
>(presented at the 55th IETF) my proposal
>of agreeing on a single CW has finally (almost) 
>become a reality.
>
>Y(J)S
>
>_______________________________________________
>pwe3 mailing list
>pwe3@ietf.org
>https://www1.ietf.org/mailman/listinfo/pwe3
>
>  
>

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



From pwe3-bounces@ietf.org Tue Apr 26 04:22:07 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DQLKY-00045p-Sk; Tue, 26 Apr 2005 04:22:06 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DQLKX-000452-Hb
	for pwe3@megatron.ietf.org; Tue, 26 Apr 2005 04:22:05 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA13122
	for <pwe3@ietf.org>; Tue, 26 Apr 2005 04:22:02 -0400 (EDT)
Received: from radmail.rad.co.il ([212.117.147.38] helo=antivir1.rad.co.il)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DQLWq-00057J-Ad
	for pwe3@ietf.org; Tue, 26 Apr 2005 04:34:54 -0400
Received: from antivir1.rad.co.il (localhost [127.0.0.1])
	by antivir1.rad.co.il (8.12.10/8.12.10) with ESMTP id j3Q8KV3Q006502
	for <pwe3@ietf.org>; Tue, 26 Apr 2005 11:20:32 +0300 (IDT)
Received: from exrad2.ad.rad.co.il (exrad2 [192.114.24.112])
	by antivir1.rad.co.il (8.12.10/8.12.10) with ESMTP id j3Q8KVgd006499;
	Tue, 26 Apr 2005 11:20:31 +0300 (IDT)
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [PWE3] Sequence numbers
Date: Tue, 26 Apr 2005 11:20:46 +0200
Message-ID: <27A0F290348F8E45AEF79889DDE65A5204660780@exrad2.ad.rad.co.il>
Thread-Topic: [PWE3] Sequence numbers
Thread-Index: AcVJqJ3SDFcRR4yDQDGcB61y4aWHFQAmCFyw
From: "Yaakov Stein" <yaakov_s@rad.com>
To: "Sasha Vainshtein" <Sasha@AXERRA.com>,
	"Stewart Bryant" <stbryant@cisco.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: de4f315c9369b71d7dd5909b42224370
Content-Transfer-Encoding: quoted-printable
Cc: pwe3 <pwe3@ietf.org>
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=subscribe>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org

=20
> Stewart, Yaakov and all,
> I am not sure that the binding between MANDATORY/OPTIONAL=20
> sequencing support and skipping zero is a good idea even if=20
> it happens to reflect correctly the current state of things.

I repeat my previous comment that the only reason
to skip zero is due to its being used to indicate that
the SN is not being used. So there is a strong binding
between the two.

If you do not see the reason for this binding,
why were you so interested in the TDM encaps
NOT skipping the zero? They could have easily skipped
zero even though the CW was mandatory.

Y(J)S

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



From pwe3-bounces@ietf.org Tue Apr 26 05:15:44 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DQMAR-00039I-Sr; Tue, 26 Apr 2005 05:15:43 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DQMAN-00038p-Rb
	for pwe3@megatron.ietf.org; Tue, 26 Apr 2005 05:15:40 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA16980
	for <pwe3@ietf.org>; Tue, 26 Apr 2005 05:15:37 -0400 (EDT)
Received: from mx100.qos.net.il ([80.74.96.6])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DQMMn-0006G9-Rr
	for pwe3@ietf.org; Tue, 26 Apr 2005 05:28:30 -0400
Received: from tlv1.axerra.com (tlv1.axerra.com [80.74.100.68])
	by mx100.qos.net.il (8.12.8/8.12.8) with ESMTP id j3Q9AVFB010419;
	Tue, 26 Apr 2005 12:10:31 +0300
Received: by TLV1 with Internet Mail Service (5.5.2653.19)
	id <GZ9PDHR4>; Tue, 26 Apr 2005 12:13:06 +0200
Message-ID: <AF5018AC03D1D411ABB70002A5091326015E1DC5@TLV1>
From: Sasha Vainshtein <Sasha@AXERRA.com>
To: "'Yaakov Stein'" <yaakov_s@rad.com>
Subject: Re: [PWE3] Sequence numbers
Date: Tue, 26 Apr 2005 12:13:06 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="ISO-8859-8"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 769a46790fb42fbb0b0cc700c82f7081
Cc: "PWE3 WG \(E-mail\)" <pwe3@ietf.org>,
	"Stewart Bryant \(E-mail\)" <stbryant@cisco.com>
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=subscribe>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org

Yaakov,
Of course your reasoning is logically perfect.

The problem is that the decision to make sequencing
support for a specific PW service OPTIONAL or MANDATORY 
in many cases is NOT based on any logic.

Even some TDM encapsulation could do without the CW
sequencing (e.g., for TDMoIP in AAL1 mode the sequencing 
function could be provided by the AAL1 sequence numbers). 

And when you apply a perfect logical rule to a basically 
illogical situation, the results can be quite embarassing.

Regards,
                                  Sasha Vainshtein
email:                         sasha@axerra.com <mailto:sasha@axerra.com> 
phone:                       +972-3-7569993 (office)
fax:                            +972-3-6487779
mobile:                      +972-52-8674833 


> -----Original Message-----
> From: Yaakov Stein [mailto:yaakov_s@rad.com]
> Sent: Tuesday, April 26, 2005 11:21 AM
> To: Sasha Vainshtein; Stewart Bryant
> Cc: pwe3
> Subject: RE: [PWE3] Sequence numbers
> 
> 
>  
> > Stewart, Yaakov and all,
> > I am not sure that the binding between MANDATORY/OPTIONAL 
> > sequencing support and skipping zero is a good idea even if 
> > it happens to reflect correctly the current state of things.
> 
> I repeat my previous comment that the only reason
> to skip zero is due to its being used to indicate that
> the SN is not being used. So there is a strong binding
> between the two.
> 
> If you do not see the reason for this binding,
> why were you so interested in the TDM encaps
> NOT skipping the zero? They could have easily skipped
> zero even though the CW was mandatory.
> 
> Y(J)S
> 

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



From pwe3-bounces@ietf.org Tue Apr 26 09:04:09 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DQPjV-0003Kd-Ff; Tue, 26 Apr 2005 09:04:09 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DQPjT-0003KX-1F
	for pwe3@megatron.ietf.org; Tue, 26 Apr 2005 09:04:07 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA05878
	for <pwe3@ietf.org>; Tue, 26 Apr 2005 09:04:05 -0400 (EDT)
Received: from napoleon.monoski.com ([63.225.114.233])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DQPvu-0003XE-9O
	for pwe3@ietf.org; Tue, 26 Apr 2005 09:16:59 -0400
Received: from [2.0.1.6] (rasputin-gw [2.0.1.6]) (authenticated bits=0)
	by napoleon.monoski.com (8.13.2/8.13.2) with ESMTP id j3QD3W5X019939;
	Tue, 26 Apr 2005 07:03:33 -0600 (MDT)
Message-ID: <425D96CA.7060806@cisco.com>
Date: Wed, 13 Apr 2005 16:01:46 -0600
From: Luca Martini <lmartini@cisco.com>
User-Agent: Mozilla Thunderbird 1.0 (X11/20041206)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "W. Mark Townsley" <townsley@cisco.com>
Subject: Re: [PWE3] AD Review of draft-ietf-pwe3-cw-03.txt
References: <425AE61B.2030909@cisco.com> <425D695D.3080709@cisco.com>
	<425D80D5.2080604@cisco.com>
In-Reply-To: <425D80D5.2080604@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Scanned-By: MIMEDefang 2.28 (www . roaringpenguin . com / mimedefang)
X-Spam-Score: 1.2 (+)
X-Scan-Signature: 210770d71723b650f9c8e3db4e95b596
Content-Transfer-Encoding: 7bit
Cc: Danny McPherson <danny@tcb.net>, "PWE3 WG \(E-mail\)" <pwe3@ietf.org>,
	Stewart Bryant <stbryant@cisco.com>
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=subscribe>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org

W. Mark Townsley wrote:

>
> Apologies for the CR/LF problem in the earlier email. I think that it 
> should be fixed in this one.
>
> I have reinserted Luca and I's comments inline marked with "Luca>" and 
> "Mark>". Luca, I have a few additional comments/responses inline after 
> yours.
>
> Thanks,
>
> - Mark
>
> >
> > Network Working Group                                         S. Bryant
> > Internet Draft                                               G. Swallow
> > Expiration Date: September 2005                           Cisco Systems
> >                                                            D. McPherson
> >                                                          Arbor Networks
> >
> >                                                              March 2005
> >
> >
> >                 PWE3 Control Word for use over an MPLS PSN
> >
> >                         draft-ietf-pwe3-cw-03.txt
> >
> >
> >
> >
> > Status of this Memo
> >
> >    By submitting this Internet-Draft, we certify that any applicable
> >    patent or other IPR claims of which we are aware have been
> >    disclosed, or will be disclosed, and any of which we become aware
> >    will be disclosed, in accordance with RFC 3668.
> >
> >    Internet-Drafts are working documents of the Internet Engineering
> >    Task Force (IETF), its areas, and its working groups.  Note that
> >    other groups may also distribute working documents as
> >    Internet-Drafts.
> >
> >    Internet-Drafts are draft documents valid for a maximum of six
> >    months and may be updated, replaced, or obsoleted by other documents
> >    at any time.  It is inappropriate to use Internet-Drafts as
> >    reference material or to cite them other than as "work in progress".
> >
> >    The list of current Internet-Drafts can be accessed at
> >    http://www.ietf.org/1id-abstracts.html
> >
> >    The list of Internet-Draft Shadow Directories can be accessed at
> >    http://www.ietf.org/shadow.html
> >
> > Abstract
> >
> >    This document describes the preferred designs of the PWE3 MPLS
> >    Control Word, and the PW Associated Channel Header. The design of
> >    these fields is chosen so that an MPLS LSR performing MPLS payload
> >    inspection will not confuse a PWE3 payload with an IP payload.
> >
> > Conventions used in this document
> >
> >
> >
> >
> >
> >
> > Bryant et al            Expires September 2005               [Page 1]
> > 
> >
> >
> >
> > INTERNET DRAFT   PWE3 Control Word for use over an MPLS PSN   Mar 2005
> >
> >    The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
> >    "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
> >    document are to be interpreted as described in RFC 2119 [RFC2119].
> >
> >
> > 1.   Introduction
> >
> >    The standard MPLS encapsulations have no explicit protocol
> >    identifier. In order for a pseudo wire (PW) [RFC3985] to operate
> >    correctly over an MPLS packet switched network (PSN) that performs
> >    MPLS payload inspection, a PW packet must not appear to the LSR as
> >    if it were an IP packet [BCP]. An example of an LSR that performs
> >    MPLS payload inspection is one that is performing equal-cost
> >    multiple-path load-balancing (ECMP) [RFC2992]. If ECMP were
> >    performed on PWE3 packets, the packets in the PW may not all follow
> >    the same path through the PSN. This may result in misordered packet
> >    delivery to the egress PE. The inability to ensure that all packets
> >    belonging to a PW follow the same path may also prevent the PW OAM
> >    [VCCV] mechanism from correctly monitoring the PW.
> >
> >    This draft specifies how a PW header distinguishes a PW payload from
> >    an IP payload carried over an MPLS PSN.
> >
> > 2.   PWE3 Packet Identification
> >
> >    All IP packets [RFC791][RFC1883] start with a version number that is
> >    checked by LSRs performing MPLS payload inspection. To prevent the
> >    incorrect processing of packets carried within a PW, PW packets
> >    carried over an MPLS PSN SHOULD NOT start with the value 4 (IPv4) or
> >    the value 6 (IPv6) in the first nibble [BCP], as those are assumed
> >    to carry normal IP payloads.
>
> Mark> Why not specify a MUST NOT here?
>
> Luca> Some of the TDM PWs might start with a 4, as they do not have a
> Luca> conformant CW.
>
> So they are non-conformant and it should be duly noted. I don't think 
> that just because the TDM specs happen to already be in violation we 
> should relax the requirement for all. If the correct recommendation is 
> that 4 and 6 can break ECMP, then go ahead and make it a MUST NOT 
> here, and let the non-comformant PWs state in their doc that they are 
> non-conformant and could possibly cause problems with ECMP. Otherwise, 
> I think the issue may get lost.
>
I agree.

> I don't want to rathole on this. So, if it has already been hashed out 
> in the WG extensively, I'll take a call from the chairs on this. But, 
> it seems to me that since this is a basic construct for a lot of other 
> documents, the fundamentals should be defined correctly.
>
> >
> >    This document defines a PW header and two general formats of that
> >    header. These two formats are the PW MPLS Control Word (PWMCW) used
> >    for data passing across the PW, and a PW Associated Channel Header
> >    (PW-ACH) that can be used for functions such as OAM.
> >
> >    If the first nibble of a PWE3 packet carried over an MPLS PSN has a
> >    value of 0, it starts with a PWMCW. If the first nibble of a packet
> >    carried over an MPLS PSN has a value of 1, it starts with a PW-ACH.
> >    The use of any other first nibble value for a PWE3 packet carried
> >    over an MPLS PSN is deprecated.
> >
> >    A PW carried over an MPLS PSN that uses the contents of the MPLS
> >    payload to select the ECMP path SHOULD employ the PW MPLS Control
> >    Word described in Section 3 for data, and the PW Associated Channel
> >    Header described in Section 4 for channel associated traffic. These
> >    Control Words MUST immediately follow the bottom of the MPLS label
> >    stack.
> >
> >
> >
> >
> >
> >
> >
> > Bryant et al            Expires September 2005               [Page 2]
> > 
> >
> >
> >
> > INTERNET DRAFT   PWE3 Control Word for use over an MPLS PSN   Mar 2005
> >
> > 3.   Generic PW MPLS Control Word
> >
> >    The Generic PW MPLS Control Word is shown in Figure 1.
> >
> >
> >     0                   1                   2                   3
> >     0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
> >    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> >    |0 0 0 0|          Specified by PW Encapsulation                |
> >    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> >
> >          Figure 1: Generic PW MPLS Control Word
> >
> >
> >    The PW set-up protocol or configuration mechanism determines whether
> >    a PW uses a PW MPLS Control Word (PWMCW). Bits 0..3 differ from the
> >    first four bits of an IP packet [BCP] and hence provide the
> >    necessary MPLS payload discrimination.
> >
> >    When a PWMCW is used, it MUST adhere to the Generic MPLS Control
> >    Word format as illustrated in Figure 1 above. It is however strongly
> >    recommended that it also follows the following format:
>
> Mark> Is this a capital RECOMMENDED or SHOULD?
>
> Luca> yes i think it needs a capital RECOMMENDED.
>
> >
> >
> >     0                   1                   2                   3
> >     0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
> >    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> >    |0 0 0 0| Flags |FRG|  Length   | Sequence Number               |
> >    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> >
> >         Figure 2: PW Preferred MPLS Control Word
> >
> >    The meaning of the fields of the PW Preferred MPLS Control Word
> >    (Figure 2) are as follows:
> >
> >    Flags (bits 4 to 7):
> >
> >           These bits are available for per-payload signalling.  Their
> >           definition is encapsulation specific as defined in
> >           [pointer?].
>
> Mark> "pointer?" needs to be defined.
>
> Luca> omission - this needs to be removed ....
>
> >
> >    FRG (bits 8 and 9):
> >
> >           These bits are used when fragmenting a PW payload. Their use
> >           is described in [FRAG] which is currently a work in progress.
> >           When the PW is of a type that will never need payload
> >           fragmentation, these bits may be used as general purpose
> >           flags.
> >
> >    Length (bits 10 to 15):
> >
> >
> >
> >
> >
> >
> > Bryant et al            Expires September 2005               [Page 3]
> > 
> >
> >
> >
> > INTERNET DRAFT   PWE3 Control Word for use over an MPLS PSN   Mar 2005
> >
> >           The value of the length field, if non-zero, can be used to
> >           remove any padding added by the PSN. If the entire packet
> >           length is less than 64 bytes, the length field MUST be set to
> >           the length of the PW payload plus the length of the control
> >           word. Otherwise it MUST be set to zero.
> >
> >           If a non-zero length field is received, the PW payload MUST
> >           be trimmed if required.
>
> Mark> What is meant by "if required" - To me, this either MUST be 
> trimmed or
> Mark> not (no need to suggest an implementation loophole if none 
> should exist).
> Mark>
>
> Luca> no, it means that the payload might already be the correct length ,
> Luca> hence it might not need to be trimmed....
> Luca> Not all short packet have to be padded , some media do not require
> Luca> padding ....
>
> So, just to be sure, we are stating that the payload length field MUST 
> be set for < 64 byte payloads regardless of media type, but there is 
> an "if required" on the trimming when receiving a non-zero length as 
> some media types do not need the length field.
>
> Yes, I understand the issue here is ethernet, I'm not debating when it 
> is necessary or not. I simply find it odd that we have an exception 
> clause on the trimming, but not on the setting of the field.
>
> Also, I think it might be helpful for interoperability to point out 
> ethernet as an example of when this field would be used. This 
> shouldn't take more than a sentence or two and perhaps a reference.
>
ok, we can expand it to explicitly state that trimming is required if 
the actual received packet length exceeds the value in the length files.


> >
> >    Sequence number (Bit 16 to 31):
> >
> >           If the sequence number is not used, it is set to zero by the
> >           sender and ignored by the receiver.  Otherwise it specifies
> >           the sequence number of a packet.  A circular list of sequence
> >           numbers is used.  A sequence number takes a value from 1 to
> >           65535 (2**16-1). The sequence number window size for packet
> >           acceptance is dependent on the parameters of both the PW and
> >           the MPLS PSN, and SHOULD be configurable. The mechanism used
> >           by the decapsulating PE to syncronise the expected sequence
> >           number with the received sequence number is implementation
> >           dependent.
>
> Mark> s/syncronise/synchronize
>
> Mark> That's two I caught, there must be more. Please run the doc 
> through a
> Mark> spell checker.
>
> >
> > 4.   PW Associated Channel
> >
> >    For some features of PWs, such as OAM, an associated channel is
> >    required. An associated channel is a channel that is multiplexed
> >    over the PW so that it follows exactly the same path through the PSN
> >    as the PW. Note that the use of the term "channel" is not a "PW
> >    channel type" as used in subsection 5.1.2 of [RFC3985]
> >
> >    When MPLS is used as the PSN, the PW Associated Channel is
> >    identified by the following header:
> >
> >    0                   1                   2                   3
> >    0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
> >    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> >    |0 0 0 1| FmtID |   Reserved    |         Channel Type          |
> >    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> >
> >        Figure 3: PW Associated Channel Header
> >
> >    The meaning of the fields in the PW Associated Channel Header
> >    (Figure 3) are as follows:
> >
> >    FmtID:
> >
> >           Format ID for the remaining 3 octets of the header. A FmtID
> >           of 0 indicates that the 3 octets are as shown in Figure 3.
> >
> >    Reserved:
> >
> >
> >
> >
> >
> >
> > Bryant et al            Expires September 2005               [Page 4]
> > 
> >
> >
> >
> > INTERNET DRAFT   PWE3 Control Word for use over an MPLS PSN   Mar 2005
> >
> >           Must be sent as 0, and ignored on reception.
> >
> >    Channel Type:
> >
> >           The PW Associated Channel Type is defined in the IANA PW
> >           Associated Channel Type registry [IANA].
> >
> >    Bits 0..3 MUST be 0x01, and hence differ from the first four bits of
> >    an IP packet [BCP]. This provides the necessary MPLS payload
>
> Mark> The first bits being 0x01 also differ this payload from being a PW
> Mark> payload.
>
> My point here was simply that 0x01 does more than just differ this 
> packet from being a non-IP packet. It also makes it differ from being 
> a PWE3 data packet.
>
>
> >    discrimination.
> >
> >    Note that L2TPv3 [REFERENCE] has its own mechanisms for providing
> >    this associated channel, and is therefore out of the scope of this
> >    document.
>
> Mark> Need to define REFERENCE (RFC3931).
>
> >
> > 5.   IANA considerations
> >
> >    IANA needs to set up a registry of "Pseudowire Associated Channel
> >    Types". These are 16-bit values. Registry entries are assigned by
> >    using the "IETF Consensus" policy defined in [RFC2434].
>
> Mark> What about FMT IDs?
>
> Luca> r
>
yes- the fmt id=0  is the format described in this draft. So a new draft 
would be required to define a new format and a new fmt id.
we can either remove it and make it reserved - must be 0 ( my preference )
or create another IANA registry for it .

Luca

> Looks like part of your response got cut off here.
>
> >
> > 6.   Security Considerations
> >
> >    An application using PW Associated Channel to provide an OAM [VCCV]
> >    or other message channel MUST be aware that this can potentially be
> >    misused. Any application using the Associated Channel must therefore
> >    fully consider the resultant security issues, and provide mechanisms
> >    to prevent an attacker from using this as a mechanism to disrupt the
> >    operation of the PW or the PE, and to stop this channel from being
> >    used as a conduit to deliver packets elsewhere.
> >
> >    If a PW has been configured to operate without a CW, the PW
> >    Associated Channel Type mechanism described in the document MUST NOT
> >    be used. This is to prevent user payloads being fabricated in such a
> >    way that they mimic the PW Associated Channel Header, and thereby
> >    provide a method of attacking the application that is using the
> >    Associated Channel.
> >
> >
> >
> > 7.   Acknowledgements
> >
> >    The authors wish to thank David Allan, Luca Martini, Thomas Nadeau
> >    and Mark Townsley for their input to this work.
> >
> > 8.   Intellectual Property Statement
> >
> >
> >    The IETF takes no position regarding the validity or scope of any
> >    Intellectual Property Rights or other rights that might be claimed
> >
> >
> >
> >
> >
> >
> > Bryant et al            Expires September 2005               [Page 5]
> > 
> >
> >
> >
> > INTERNET DRAFT   PWE3 Control Word for use over an MPLS PSN   Mar 2005
> >
> >    to pertain to the implementation or use of the technology described
> >    in this document or the extent to which any license under such
> >    rights might or might not be available; nor does it represent that
> >    it has made any independent effort to identify any such rights.
> >    Information on the procedures with respect to rights in RFC
> >    documents can be found in BCP 78 and BCP 79.
> >
> >    Copies of IPR disclosures made to the IETF Secretariat and any
> >    assurances of licenses to be made available, or the result of an
> >    attempt made to obtain a general license or permission for the use
> >    of such proprietary rights by implementers or users of this
> >    specification can be obtained from the IETF on-line IPR repository
> >    at http://www.ietf.org/ipr.
> >
> >    The IETF invites any interested party to bring to its attention any
> >    copyrights, patents or patent applications, or other proprietary
> >    rights that may cover technology that may be required to implement
> >    this standard.  Please address the information to the IETF at ietf-
> >    ipr@ietf.org.
> >
> >
> > 9.    Full copyright statement
> >
> >    Copyright (C) The Internet Society (2004). This document is subject
> >    to the rights, licenses and restrictions contained in BCP 78, and
> >    except as set forth therein, the authors retain all their rights.
> >
> >    This document and the information contained herein are provided on
> >    an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE
> >    REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE
> >    INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR
> >    IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
> >    THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
> >    WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
> >
> >
> >
> > 10.    Normative References
> >
> >    Internet-drafts are works in progress available from
> >    http://www.ietf.org/internet-drafts/
> >
> >    [RFC791]   RFC-791: DARPA Internet Program, Protocol
> >                Specification, ISI, September 1981.
> >
> >    [RFC1883]  RFC-1883: Internet Protocol, Version 6 (IPv6), S.
> >                Deering, et al, December 1995
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > Bryant et al            Expires September 2005               [Page 6]
> > 
> >
> >
> >
> > INTERNET DRAFT   PWE3 Control Word for use over an MPLS PSN   Mar 2005
> >
> >
> >
> > 11.    Informative References
> >
> >
> >    Internet-drafts are works in progress available from
> >    <http://www.ietf.org/internet-drafts/>
> >
> >    [BCP]     Swallow, G. et al, "Avoiding Equal Cost Multipath
> >               Treatment in MPLS Networks", Internet Draft
> >               <draft-ietf-mpls-ecmp-bcp-00.txt>, September 2004,
> >               Work in Progress.
> >
> >    [FRAG]    Malis, A., Townsley, M., "PWE3 Fragmentation and
> >               Reassembly", Internet Draft, <draft-ietf-pwe3-
> >               fragmentation-08.txt>, February 2005, Work in
> >               Progress.
> >
> >    [IANA]    Martini, L., Townsley M., "IANA Allocations for
> >               pseudo Wire Edge to Edge Emulation (PWE3) ",
> >               Internet Draft, <draft-ietf-pwe3-iana-allocation-
> >               07.txt>, October 2004, Work in Progress.
> >
> >    [RFC2434] RFC-2434: Guidelines for Writing an IANA
> >               Considerations Section in RFCs, Narten, T.,
> >               Alvestrand, H., October 1998
> >
> >    [RFC2992] RFC-2992:  Analysis of an Equal-Cost Multi-Path
> >               Algorithm, C. Hopps, November 2000
> >    [RFC3985] RFC-3985: PWE3 Architecture, Bryant, S. ed., Pate,
> >               P. ed. , To be published.
> >    [VCCV]    Nadeau, T., Aggarwal, T., "Pseudo Wire (PW) Virtual
> >               Circuit Connection Verification (VCCV)", Internet
> >               Draft, <draft-ietf-pwe3-vccv-04.txt>, Feb. 2005,
> >               Work in Progress.
>
> Mark> Line spacing above.
>
> _______________________________________________
> pwe3 mailing list
> pwe3@ietf.org
> https://www1.ietf.org/mailman/listinfo/pwe3




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



From pwe3-bounces@ietf.org Thu Apr 28 09:56:17 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DR9V3-0001yA-3y; Thu, 28 Apr 2005 09:56:17 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DR9V1-0001xr-7S
	for pwe3@megatron.ietf.org; Thu, 28 Apr 2005 09:56:15 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA16450
	for <pwe3@ietf.org>; Thu, 28 Apr 2005 09:56:13 -0400 (EDT)
Received: from wproxy.gmail.com ([64.233.184.198])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DR9hs-0003O1-9Z
	for pwe3@ietf.org; Thu, 28 Apr 2005 10:09:33 -0400
Received: by wproxy.gmail.com with SMTP id 71so605538wri
	for <pwe3@ietf.org>; Thu, 28 Apr 2005 06:56:04 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com;
	h=received:message-id:date:from:reply-to:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition;
	b=JWRp6FXG+objYzgti4hjm3ULkd+14QGUN6P7r7+KQKPf7MYovuoK1UPE1XZ7SYi+R5hHtsGmg2jJz11w3aP5Twish7uDkkmW3WcJe9MZdsi+XqSOzO3kzoW4o3MVhBBU6bZj/XoITazfSrMHpID8sH7pV1Joh/xG6GdIUfRAaf4=
Received: by 10.54.120.5 with SMTP id s5mr746990wrc;
	Thu, 28 Apr 2005 06:56:04 -0700 (PDT)
Received: by 10.54.70.2 with HTTP; Thu, 28 Apr 2005 06:56:03 -0700 (PDT)
Message-ID: <db3e291305042806566c8dffe8@mail.gmail.com>
Date: Thu, 28 Apr 2005 09:56:03 -0400
From: Rurick Kellermann <rurick@gmail.com>
To: pwe3@ietf.org
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
X-Spam-Score: 0.0 (/)
X-Scan-Signature: bb8eae9af85e4fcfe76f325e38493bf4
Content-Transfer-Encoding: quoted-printable
Subject: [PWE3] test message - pls. ignore
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Rurick Kellermann <rurick@gmail.com>
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=subscribe>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org



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



From pwe3-bounces@ietf.org Thu Apr 28 12:20:55 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DRBl1-0002iv-Fm; Thu, 28 Apr 2005 12:20:55 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DRBky-0002ij-3P
	for pwe3@megatron.ietf.org; Thu, 28 Apr 2005 12:20:53 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA01590
	for <pwe3@ietf.org>; Thu, 28 Apr 2005 12:20:47 -0400 (EDT)
Received: from omzesmtp01.mci.com ([199.249.17.7])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DRBxo-0001ao-87
	for pwe3@ietf.org; Thu, 28 Apr 2005 12:34:09 -0400
Received: from dgismtp03.wcomnet.com ([166.38.58.143])
	by firewall.mci.com (Iplanet MTA 5.2)
	with ESMTP id <0IFO0044P01NG3@firewall.mci.com> for pwe3@ietf.org; Thu,
	28 Apr 2005 16:20:12 +0000 (GMT)
Received: from dgismtp03.wcomnet.com by dgismtp03.mcilink.com
	(iPlanet Messaging Server 5.2 HotFix 1.14 (built Mar 18 2003))
	with SMTP id <0IFO0070100EG3@dgismtp03.mcilink.com>; Thu,
	28 Apr 2005 16:20:11 +0000 (GMT)
Received: from XS344V8061891 ([153.39.146.164])
	by dgismtp03.mcilink.com (iPlanet Messaging Server 5.2 HotFix 1.14
	(built Mar
	18 2003)) with ESMTP id <0IFO0074100RAY@dgismtp03.mcilink.com>; Thu,
	28 Apr 2005 16:19:39 +0000 (GMT)
Date: Thu, 28 Apr 2005 12:19:34 -0400
From: David McDysan <dave.mcdysan@mci.com>
In-reply-to: <B5E87B043D4C514389141E2661D255EC0A835969@i2km41-ukdy.domain1.systemhost.net>
To: richard.spencer@bt.com
Message-id: <0IFO0074200RAY@dgismtp03.mcilink.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7bit
Thread-index: AcUwtpMJ85gv5TOKRqShcivapkROKQAWNy0lAA2lRHABH6B/ZgWRxjhg
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 21f6736b171db90b7af90d77f0c0e285
Content-Transfer-Encoding: 7bit
Cc: pwe3@ietf.org
Subject: [PWE3] RE: Proposed MS-PW "QoS" Requirements Clarifications
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=subscribe>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org

Richard,

A few responses in line below.

Dave 

> -----Original Message-----
> From: richard.spencer@bt.com [mailto:richard.spencer@bt.com] 
> Sent: Thursday, March 31, 2005 2:43 AM
> To: dave.mcdysan@mci.com
> Cc: pwe3@ietf.org
> Subject: RE: Proposed MS-PW "QoS" Requirements Clarifications
> 
> Dave,
>  
> Regarding your suggestion to carry parameters such as the 
> average rate, burst duration and peak rate, and your 
> references to RFC2697/RFC2698, I assume that this is to 
> support per MS-PW policing/queuing at S-PEs? One case where 
> per MS-PW policing will be needed is at border S-PEs where a 
> provider may not trust another provider to police individual 
> MS-PWs correctly. One case where per MS-PW queues (and 
> associated traffic counters) could be used is at border S-PEs 
> to obtain per MS-PW usage information in order to support 
> usage based inter-provider charging models. Based on these 
> inter-provider use cases, I agree that there will be a 
> requirement to carry traffic parameters in order to support 
> per MS-PW policing/queuing.
>  

I think that a minimum these parameters are necessary for admission control
at S-PEs. Note that concatenated policing must account for accumulated
variation.

> In the intra-provider case however, my view is that per MS-PW 
> policing/queuing at S-PEs will not be required (in most 
> cases). I believe a common approach will be to use per 
> MS-PW/AC policing at the edge and class based 
> queuing/policing everywhere else. At non PW switching capable 
> nodes, packets will be classified/queued based on information 
> in the tunnel LSP header (e.g. EXP field, label). At S-PEs, 
> after popping the tunnel label, packets will need to be 
> classified based on information in the MS-PW LSP header, 
> mapped to the appropriate tunnel LSP (and EXP value) and 
> queued accordingly. In this scenario, assuming each S-PE has 
> a route to reach the destination U-PE (based on reachability 
> or topology information), the MS-PW signalling protocol just 
> needs to specify how much bandwidth is required and carry 
> enough information (e.g. EXP field) to perform CAC and 
> reserve the required bandwidth for the corresponding DS-TE 
> tunnel LSP (or CT in the multi-class LSP case, 
> draft-minei-diffserv-te-multi-class-00.txt).

I agree that CAC as the principal usage in an intra-provider case.

>  
> This approach is well suited to MS-PWs that map to a single 
> class of service. If a MS-PW maps to multiple classes of 
> service then things get more complicated as the signalling 
> protocol needs to carry <bandwidth, EXP> pairs, and multiple 
> bandwidth reservations and CAC decisions must be made at each 

S-PE

> hop. In addition, in the DS-TE case, depending on the network 
> design/topology, tunnels for different CTs could potentially 
> traverse different S-PEs, making things significantly more 
> complicated.
> Rather than reserve bandwidth at each hop for some types of 
> MS-PWs, an alternative will be to set up the MS-PWs without 
> performing any CAC or reserving any bandwidth in the same way 
> that RFC2547 VPNs are set up. This approach relies on per 
> MS-PW/AC policing at the edge, and network 
> monitoring/planning to configure appropriate queue weights in 
> order to ensure that there is enough bandwidth available. 
> Obviously MS-PWs that have been setup without using CAC must 
> use different tunnel LSPs to MS-PWs setup using CAC, 
> otherwise performing CAC on those MS-PWs is a waste of time.

I am suggesting that MS-PW signaling carry object(s) that indicate the
desired quality. The set of S-PE domains traversed may use different means
for providing the requested quality. You have mentioned some possible
methods.

>  
> Regarding your suggestion to carry QoS parameters such as 
> latency, jitter, loss, my feeling is that this should be for 
> further study and is not a short term requirement (although 
> other providers may disagree ?). Firstly, to support this 
> model, standardised performance monitoring tools/MIBs would 
> be required to provide source U-PEs and S-PEs with network 
> performance information on a per tunnel LSP/class of service 
> basis. I do not believe these are available today and I am 
> not aware of any work in progress in this area? 

Some of the IPPM work could be applied here. I agree that additional work is
necessary to complete the full operational solution. The reported parameters
need not be the actual measurement, but a value that the segment can deliver
(e.g., as in PNNI).

> Secondly, in 
> the intra-provider case where class based queuing is commonly 
> used, by signalling a specific class of service for a MS-PW 
> (e.g. by specifying an EXP value) then the latency, jitter, 
> loss, etc. characteristics will be inherited from the tunnels 
> LSPs. Therefore, by mapping ACs to classes of service at the 
> edge that can meet the required (latency, jitter, loss) 
> requirements, there is no need to signal the traffic 
> characteristics using the MS-PW signalling protocol. 

This is true if the set of S-PE domains all implement the same PHB for the
EXP bits. However, this is not a general solution and may not be applicable
for all intra-provider environments, in addition to the inter-provider case
you mention below. I was proposing a more general form of solution.

>  
> This approach does not work well in the inter-provider case 
> because different providers will offer different class of 
> service options with varying traffic characteristics, and 
> therefore it may be very difficult or not possible to map 
> class of service definitions between providers. However, 
> inter-provider PW setup is a general issue and I do not think 
> the MS-PW requirements document needs to state exactly what 
> parameters must be carried in order to solve the problem as 
> these will be dependent on the solutions. For example, an 
> inter-provider solution might be developed that uses BGP for 
> signalling and routing, in which case BGP communities might 
> be used to signal QoS parameters, e.g. Well Known Community X 
> means that a MS-PW requires <200ms delay.
> 
> I agree that if the QoS requirements are too vague then we 
> need to provide further clarification, although we don't want 
> to start getting too specific otherwise we will end up trying 
> to write a protocol design specification. If consensus is 
> that the requirements document should specify exactly which 
> traffic parameters should be carried then I don't have any 
> strong objections. However, I think it will be difficult to 
> cover all current and future intra and inter provider cases 
> as QoS models vary significantly between providers and new 
> solutions will become available over time. 

We either need to get specific now, or do it later. My preference would be
to be specific in the requirements such that different solutions have the
same parameters and semantics for traffic quantity and performance quality.
Otherwise there is a good chance that different solutions will pick
different parameters, encodings and semantics.

> I would prefer to 
> define requirements along the lines of:
>  
> - The MS-PW signalling protocol must support the option to 
> carry traffic parameters that allow per MS-PS policers and 
> queues to be dynamically configured 

as well as perform admission control

> during MS-PW setup at U-PEs/S-PEs.

Suggest to the editors that they merge the traffic parameters and
(potential) policing use into 6.3.1 i.

> - The MS-PW signalling protocol must carry enough information 
> for a S-PEs to be able to select appropriate tunnel LSPs, 
> e.g. EXP field corresponding to required traffic class.

This appears to be similar to 6.3.1 i (adds EXP bit usage as example). 

> - The MS-PW signalling protocol must carry traffic parameters 
> that will support inter-provider signalling, e.g. to support 
> future PCE solutions.

I think that a more general statement is inter-AS (need not be only
inter-provider). 

>  
> Regards,
> Richard
> 
> 	-----Original Message----- 
> 	From: David McDysan [mailto:dave.mcdysan@mci.com] 
> 	Sent: Fri 25/03/2005 09:53 
> 	To: Spencer,R,Richard,XDE73 R 
> 	Cc: pwe3@ietf.org 
> 	Subject: Proposed MS-PW "QoS" Requirements Clarifications
> 	
> 	
> 
> 	Richard,
> 	
> 	I agree with the sentiment of your comment. Here are a 
> few specific
> 	proposals on changing section 6.3
> 	draft-martini-pwe3-mh-pw-requirements-01.txt with the 
> intent of clarifying
> 	the requirements:
> 	
> 	I made a comment similar to the following on 1/19/05 
> and that has not been
> 	addressed in the -01 requirements draft:
> 	
> 	The current requirement on traffic parameters is much 
> too general. There
> 	needs to be standard on how to signal the requested 
> Quantity of Service
> 	(QoS) (i.e.,  traffic parameters (e.g., the average 
> rate, burst duration and
> 	peak rate from RFC 2215, the FR style parameters from
> 	draft-shah-pwe3-pw-qos-signaling-02.txt, or the SRTCM 
> or DRTCM from RFCs
> 	2697 and 2698, respectively).  A number of these 
> traffic parameter specs do
> 	have an equivalence for cerating
> 	
> 	The requirements also need to precisely specify how the 
> Quality of Service
> 	(QoS) characteristics are signaled. The current 
> requirement is too general.
> 	There must also be some reference for the defintion of 
> "QoS Class." Possible
> 	references are a minimal set of Diffserv PHBs and the 
> associated semantics
> 	from Baker/Babriaz being discussed in tsvwg or the 
> effort in the ITU-T
> 	updating Y.1540 and Y.1541. 
> 	
> 	Gerry Ash pointed out NSIS-based QoS-NSLP signaling for 
> Y.1541 QoS classes
> 	that could also be relevant, see
> 	http://ietf.org/internet-drafts/draft-ash-nsis-y1541-qsp-00.txt.
> 	
> 	I pointed this out again on 2/9/05 and also made the 
> following comment based
> 	upon reading the above draft.
> 	
> 	Signaling the accumulated QoS parameter (latency, 
> latency variation, loss,
> 	etc.) is more general, yet more complex. The use of 
> certain class or service
> 	(CoS) (e.g., Y.1541) implicitly assumes a reference 
> configuration, which may
> 	or may not be appropriate. If this CoS method is used, 
> the protocol SHOULD
> 	track the domains traversed so that it could be mapped 
> against the reference
> 	model.
> 	
> 	Suggest that both methods: accumulate QoS parms and use 
> CoS be mentioned in
> 	the next version.
> 	
> 	Also, I recommend that specifics on Quality of Service 
> metrics and
> 	measurement methods be added. The ietf ippm working 
> group has produced a
> 	number of documents in this area that should be referenced.
> 	
> 	Does anyone object to adding the above more specific 
> requirements and cited
> 	references to the pwe3 wg document that will be based upon
> 	draft-martini-pwe3-mh-pw-requirements-01.txt?
> 	
> 	Thanks,
> 	
> 	Dave
> 	
> 	> -----Original Message-----
> 	> From: pwe3-bounces@ietf.org [mailto:pwe3-bounces@ietf.org] On
> 	> Behalf Of richard.spencer@bt.com
> 	> Sent: Friday, March 25, 2005 3:48 AM
> 	> To: Eric.Gray@marconi.com; bdavie@cisco.com
> 	> Cc: kireeti@juniper.net; pwe3@ietf.org
> 	> Subject: RE: [PWE3] draft-raggarwa-rsvpte-pw-01.txt
> 	>
> 	> I really can't understand why there is speculation over the
> 	> agreement of requirements in the requirements draft (which
> 	> has been accepted as a WG document). The MS-PW requirements
> 	> draft is a joint effort between a number of tier 1 service
> 	> providers. Every requirement has been submitted by one of the
> 	> contributing providers, and I would assume that each of the
> 	> requirements is based on current/planned network deployments
> 	> and associated network design goals - I do not think the
> 	> contributing authors would waste their time submitting
> 	> requirements otherwise.
> 	> 
> 	> There may be requirements that are still missing,
> 	> particulalry from providers that have not yet contributed to
> 	> the draft. Some of the requirements included in the draft may
> 	> need further explanation, and the draft itself may need
> 	> further work to tidy it up (i.e. remove duplication, improve
> 	> readability). Also, over time some of the requirements may
> 	> change as new solutions/services become available and
> 	> networks evolve. However, the current draft describes the
> 	> MS-PW requirements as perceived by the contributing tier 1
> 	> service providers today, and these requirements will not
> 	> change significantly in the short term.
> 	> 
> 	> Therefore, for the purposes of MS-PW discussions, these
> 	> requirements should be accepted as the definitive MS-PW
> 	> requirements regardless of what stage in the IETF
> 	> standardisation process the requirements draft is at.
> 	> 
> 	> Regards,
> 	> Richard
> 	>
> 	>       -----Original Message-----
> 	>       From: pwe3-bounces@ietf.org on behalf of Gray, Eric
> 	>       Sent: Thu 24/03/2005 16:14
> 	>       To: Bruce Davie
> 	>       Cc: 'Kireeti Kompella'; pwe3@ietf.org
> 	>       Subject: RE: [PWE3] draft-raggarwa-rsvpte-pw-01.txt
> 	>      
> 	>      
> 	>
> 	>       Bruce,
> 	>      
> 	>               You left out the obvious point at which we might
> 	>       "have [requirements]" - when there are customers who
> 	>       say they would like to have it...  :-)
> 	>      
> 	>       --
> 	>       Eric
> 	>      
> 	>       -----Original Message-----
> 	>       From: pwe3-bounces@ietf.org
> 	> [mailto:pwe3-bounces@ietf.org]On Behalf Of
> 	>       Kireeti Kompella
> 	>       Sent: Thursday, March 24, 2005 3:45 PM
> 	>       To: Bruce Davie
> 	>       Cc: pwe3@ietf.org
> 	>       Subject: Re: [PWE3] draft-raggarwa-rsvpte-pw-01.txt
> 	>      
> 	>      
> 	>       On Wed, 23 Mar 2005, Bruce Davie wrote:
> 	>      
> 	>       > --On Wednesday, March 23, 2005 11:48 AM -0800 
> Kireeti Kompella
> 	>       > <kireeti@juniper.net> wrote:
> 	>       >
> 	>       > > On Wed, 23 Mar 2005, Bruce Davie wrote:
> 	>       ...
> 	>       > I haven't passed judgment on RSVP. It certainly seems
> 	> premature to start
> 	>       > increasing the number of protocols for PWs before we
> 	> agree on the
> 	>       > requirements.
> 	>      
> 	>       Good to hear that.
> 	>      
> 	>       However (believe it or not), the authors didn't propose
> 	> the above
> 	>       document solely for the purpose of increasing 
> the number of PW
> 	>       protocols.  Thay have what they believe are 
> sound technical and
> 	>       pragmatic reasons.
> 	>      
> 	>       > > For that matter, it's not like we have a single PW
> 	> protocol.  The
> 	>       > > "unhelpful" event already occurred, for better or
> 	> worse.  Now we
> 	>       > > should focus on what's the most suitable protocol
> 	> for the reqts.
> 	>       >
> 	>       > Once we have the reqts, I agree.
> 	>      
> 	>       When do we "have the reqts"?  When:
> 	>       a) it's a WG doc?
> 	>       b) it's in WG Last Call?
> 	>       c) it's in IETF Last Call?
> 	>       d) it's an RFC?
> 	>      
> 	>       > I chose my words carefully. By saying "at this time"
> 	> I do indeed
> 	>       > mean that, when we have a better sense of the
> 	> requirements, it would
> 	>       > be a good time to decide which protocol(s) the
> 	> working group will
> 	>       > adopt to meet them.
> 	>      
> 	>       Same question as above: when can we say that we have a
> 	> better sense of
> 	>       the requirements?
> 	>      
> 	>       Kireeti.
> 	>       -------
> 	>      
> 	>       _______________________________________________
> 	>       pwe3 mailing list
> 	>       pwe3@ietf.org
> 	>       https://www1.ietf.org/mailman/listinfo/pwe3
> 	>      
> 	>       _______________________________________________
> 	>       pwe3 mailing list
> 	>       pwe3@ietf.org
> 	>       https://www1.ietf.org/mailman/listinfo/pwe3
> 	>      
> 	>
> 	>
> 	
> 	
> 
> 


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



