From pwe3-bounces@ietf.org Fri Jun 01 15:50:34 2007
Return-path: <pwe3-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HuD8l-0003Ny-BE; Fri, 01 Jun 2007 15:50:27 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HuD8M-0002ik-VX; Fri, 01 Jun 2007 15:50:02 -0400
Received: from ns0.neustar.com ([156.154.16.158])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HuD8M-0003Qk-6r; Fri, 01 Jun 2007 15:50:02 -0400
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10]) by ns0.neustar.com (Postfix) with ESMTP id 2E7B232992;
	Fri,  1 Jun 2007 19:50:02 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1HuD8M-0003je-2a; Fri, 01 Jun 2007 15:50:02 -0400
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1HuD8M-0003je-2a@stiedprstage1.ietf.org>
Date: Fri, 01 Jun 2007 15:50:02 -0400
X-Spam-Score: -2.5 (--)
X-Scan-Signature: b7b9551d71acde901886cc48bfc088a6
Cc: pwe3@ietf.org
Subject: [PWE3] I-D ACTION:draft-ietf-pwe3-pw-tc-mib-11.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>
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 Pseudowire Emulation Edge to Edge Working Group of the IETF.

	Title		: Definitions for Textual Conventions and for Managing Pseudo-Wires over PSN
	Author(s)	: T. Nadeau, et al.
	Filename	: draft-ietf-pwe3-pw-tc-mib-11.txt
	Pages		: 12
	Date		: 2007-6-1
	
This memo defines a Management Information Base (MIB) module which
   contains Textual Conventions (TCs) to represent commonly-used Pseudo
   Wire (PW) management information.  The intent is that these TCs will
   be imported and used in PW-related MIB modules that would otherwise
   define their own representations.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-pwe3-pw-tc-mib-11.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-pw-tc-mib-11.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-pw-tc-mib-11.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: <2007-6-1103151.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-pwe3-pw-tc-mib-11.txt

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

Content-Type: text/plain
Content-ID: <2007-6-1103151.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 Fri Jun 01 15:51:01 2007
Return-path: <pwe3-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HuD9I-0004bR-KS; Fri, 01 Jun 2007 15:51:00 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HuD8r-0003fZ-Oz; Fri, 01 Jun 2007 15:50:33 -0400
Received: from ns3.neustar.com ([156.154.24.138])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1HuD8q-00086b-EM; Fri, 01 Jun 2007 15:50:33 -0400
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10]) by ns3.neustar.com (Postfix) with ESMTP id 543A0175D0;
	Fri,  1 Jun 2007 19:50:02 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1HuD8M-0003jh-3C; Fri, 01 Jun 2007 15:50:02 -0400
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1HuD8M-0003jh-3C@stiedprstage1.ietf.org>
Date: Fri, 01 Jun 2007 15:50:02 -0400
X-Spam-Score: -2.5 (--)
X-Scan-Signature: b7b9551d71acde901886cc48bfc088a6
Cc: pwe3@ietf.org
Subject: [PWE3] I-D ACTION:draft-ietf-pwe3-pw-mib-11.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>
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 Pseudowire Emulation Edge to Edge Working Group of the IETF.

	Title		: Pseudo Wire (PW) Management Information Base
	Author(s)	: D. Zelig, et al.
	Filename	: draft-ietf-pwe3-pw-mib-11.txt
	Pages		: 63
	Date		: 2007-6-1
	
This memo defines an experimental portion of the Management
   Information Base for use with network management protocols in the
   Internet community.  In particular, it describes managed objects for
   modeling of Pseudo Wire Edge-to-Edge services carried over a general
   Packet Switched Network.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-pwe3-pw-mib-11.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-pw-mib-11.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-pw-mib-11.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: <2007-6-1103323.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-pwe3-pw-mib-11.txt

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

Content-Type: text/plain
Content-ID: <2007-6-1103323.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 Jun 05 08:30:48 2007
Return-path: <pwe3-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HvYBO-0004Xc-Mw; Tue, 05 Jun 2007 08:30:42 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HvYBN-0004XX-SE
	for pwe3@ietf.org; Tue, 05 Jun 2007 08:30:41 -0400
Received: from cat.tcb.net ([64.78.150.134] helo=dog.tcb.net)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HvYBL-0003qh-Hd
	for pwe3@ietf.org; Tue, 05 Jun 2007 08:30:41 -0400
Received: from [192.168.1.7] (VDSL-151-118-149-96.DNVR.QWEST.NET
	[151.118.149.96]) (using TLSv1 with cipher AES128-SHA (128/128 bits))
	(No client certificate requested)
	by dog.tcb.net (Postfix) with ESMTP id 84E1E64347
	for <pwe3@ietf.org>; Tue,  5 Jun 2007 06:30:30 -0600 (MDT)
Mime-Version: 1.0 (Apple Message framework v752.3)
References: <E1HtyJ0-0007GT-GA@stiedprstage1.ietf.org>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <640D1A82-AA2E-4259-BD2C-812C5FB8BC24@tcb.net>
Content-Transfer-Encoding: 7bit
From: Danny McPherson <danny@tcb.net>
Date: Tue, 5 Jun 2007 06:30:27 -0600
To: "pwe3 ((((((((E-mail)))))))) WG" <pwe3@ietf.org>
X-Mailer: Apple Mail (2.752.3)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4d87d2aa806f79fed918a62e834505ca
Subject: [PWE3] Fwd: Internet-Drafts Submission Cutoff Dates for the 69th
	IETF Meeting in Chicago, IL, USA 
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>
Errors-To: pwe3-bounces@ietf.org



Begin forwarded message:

> From: ietf-secretariat@ietf.org
> Date: May 31, 2007 10:00:02 PM MDT
> To: ietf-announce@ietf.org
> Subject: Internet-Drafts Submission Cutoff Dates for the 69th IETF   
> Meeting in Chicago, IL, USA
>
>
> There are two (2) Internet-Draft cutoff dates for the 69th
> IETF Meeting in Chicago, IL, USA:
>
> July 2nd: Cutoff Date for Initial (i.e., version -00)
> Internet-Draft Submissions
>
> All initial Internet-Drafts (version -00) must be submitted by Monday,
> July 2nd at 9:00 AM ET. As always, all initial submissions with a
> filename beginning with "draft-ietf" must be approved by the
> appropriate WG Chair before they can be processed or announced.  The
> Secretariat would appreciate receiving WG Chair approval by Monday,
> June 25th at 9:00 AM ET.
>
> July 9th: Cutoff Date for Revised (i.e., version -01 and higher)
> Internet-Draft Submissions
>
> All revised Internet-Drafts (version -01 and higher) must be submitted
> by Monday, July 9th at 9:00 AM ET.
>
> Initial and revised Internet-Drafts received after their respective
> cutoff dates will not be made available in the Internet-Drafts
> directory or announced until on or after Monday, July 23rd at 9:00
> AM ET, when Internet-Draft posting resumes.  Please do not wait until
> the last minute to submit.
>
> Thank you for your understanding and cooperation. If you have any
> questions or concerns, then please send a message to
> internet-drafts@ietf.org.
>
> The IETF Secretariat
>
> FYI: The Internet-Draft cutoff dates as well as other significant  
> dates
> for the 69th IETF Meeting can be found at http://www.ietf.org/ 
> meetings/cutoff_dates_69.html.
>
> _______________________________________________
> IETF-Announce mailing list
> IETF-Announce@ietf.org
> https://www1.ietf.org/mailman/listinfo/ietf-announce


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



From pwe3-bounces@ietf.org Tue Jun 05 08:35:26 2007
Return-path: <pwe3-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HvYFx-0000dD-FV; Tue, 05 Jun 2007 08:35:25 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HvYFw-0000d7-7w
	for pwe3@ietf.org; Tue, 05 Jun 2007 08:35:24 -0400
Received: from cat.tcb.net ([64.78.150.134] helo=dog.tcb.net)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HvYFv-0004fU-OK
	for pwe3@ietf.org; Tue, 05 Jun 2007 08:35:24 -0400
Received: from [192.168.1.7] (VDSL-151-118-149-96.DNVR.QWEST.NET
	[151.118.149.96]) (using TLSv1 with cipher AES128-SHA (128/128 bits))
	(No client certificate requested)
	by dog.tcb.net (Postfix) with ESMTP id C56D064347
	for <pwe3@ietf.org>; Tue,  5 Jun 2007 06:35:14 -0600 (MDT)
Mime-Version: 1.0 (Apple Message framework v752.3)
References: <E1HFJ1e-0006vT-Kv@stiedprstage1.ietf.org>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <EC5C009B-160F-4D0E-80EF-F66D31B17022@tcb.net>
Content-Transfer-Encoding: 7bit
From: Danny McPherson <danny@tcb.net>
Date: Tue, 5 Jun 2007 06:35:10 -0600
To: "pwe3 WG ((((((((E-mail))))))))" <pwe3@ietf.org>
X-Mailer: Apple Mail (2.752.3)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 3002fc2e661cd7f114cb6bae92fe88f1
Subject: [PWE3] WG LC:draft-ietf-pwe3-pw-tc-mib-10.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>
Errors-To: pwe3-bounces@ietf.org

Folks,
Please consider today the start of a two week WG LC for
this document.  The call for comments from the WG will end
on 6/19.  Please provide feedback to the mailing list or
authors ASAP.

Thanks!

-danny


Begin forwarded message:

> From: Internet-Drafts@ietf.org
> Date: February 8, 2007 4:50:02 PM MST
> To: i-d-announce@ietf.org
> Cc: pwe3@ietf.org
> Subject: [PWE3] I-D ACTION:draft-ietf-pwe3-pw-tc-mib-10.txt
>
> A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
> This draft is a work item of the Pseudowire Emulation Edge to Edge  
> Working Group of the IETF.
>
> 	Title		: Definitions for Textual Conventions and for Managing  
> Pseudo-Wires over PSN
> 	Author(s)	: T. Nadeau, et al.
> 	Filename	: draft-ietf-pwe3-pw-tc-mib-10.txt
> 	Pages		: 11
> 	Date		: 2007-2-8
> 	
> This memo defines a Management Information Base (MIB) module which
>    contains Textual Conventions (TCs) to represent commonly-used  
> Pseudo
>    Wire (PW) management information.  The intent is that these TCs  
> will
>    be imported and used in PW-related MIB modules that would otherwise
>    define their own representations.
>
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ietf-pwe3-pw-tc-mib-10.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-pw-tc-mib-10.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-pw-tc-mib-10.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-Type: text/plain
> Content-ID: <2007-2-8161613.I-D@ietf.org>
>
> _______________________________________________
> 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 Jun 05 08:35:45 2007
Return-path: <pwe3-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HvYGH-0001Vb-LH; Tue, 05 Jun 2007 08:35:45 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HvYGF-0001PI-SA
	for pwe3@ietf.org; Tue, 05 Jun 2007 08:35:43 -0400
Received: from cat.tcb.net ([64.78.150.134] helo=dog.tcb.net)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HvYGD-0004h1-FT
	for pwe3@ietf.org; Tue, 05 Jun 2007 08:35:43 -0400
Received: from [192.168.1.7] (VDSL-151-118-149-96.DNVR.QWEST.NET
	[151.118.149.96]) (using TLSv1 with cipher AES128-SHA (128/128 bits))
	(No client certificate requested)
	by dog.tcb.net (Postfix) with ESMTP id A470464347
	for <pwe3@ietf.org>; Tue,  5 Jun 2007 06:35:32 -0600 (MDT)
Mime-Version: 1.0 (Apple Message framework v752.3)
References: <E1HrJJy-0000kl-6O@stiedprstage1.ietf.org>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <642A8355-ED41-43C4-9CA0-6D7F38B45E86@tcb.net>
Content-Transfer-Encoding: 7bit
From: Danny McPherson <danny@tcb.net>
Date: Tue, 5 Jun 2007 06:35:30 -0600
To: "pwe3 ((((((((E-mail)))))))) WG" <pwe3@ietf.org>
X-Mailer: Apple Mail (2.752.3)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b7b9551d71acde901886cc48bfc088a6
Subject: [PWE3] WG LC:draft-ietf-pwe3-pw-mpls-mib-12.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>
Errors-To: pwe3-bounces@ietf.org

Folks,
Please consider today the start of a two week WG LC for
this document.  The call for comments from the WG will end
on 6/19.  Please provide feedback to the mailing list or
authors ASAP.

Thanks!

-danny


Begin forwarded message:

> From: Internet-Drafts@ietf.org
> Date: May 24, 2007 1:50:02 PM MDT
> To: i-d-announce@ietf.org
> Cc: pwe3@ietf.org
> Subject: [PWE3] I-D ACTION:draft-ietf-pwe3-pw-mpls-mib-12.txt
>
> A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
> This draft is a work item of the Pseudowire Emulation Edge to Edge  
> Working Group of the IETF.
>
> 	Title		: Pseudo-Wire (PW) over MPLS PSN Management Information Base
> 	Author(s)	: D. Zelig, T. Nadeau
> 	Filename	: draft-ietf-pwe3-pw-mpls-mib-12.txt
> 	Pages		: 32
> 	Date		: 2007-5-24
> 	
> This memo defines an experimental portion of the Management
>    Information Base (MIB) for use with network management protocols in
>    the Internet community.  In particular, it describes a MIB  
> module for
>    PW operation over Multi-Protocol Label Switching (MPLS) Label  
> Switch
>    Router (LSR).
>
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ietf-pwe3-pw-mpls-mib-12.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-pw-mpls-mib-12.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-pw-mpls-mib-12.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-Type: text/plain
> Content-ID: <2007-5-24134918.I-D@ietf.org>
>
> _______________________________________________
> 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 Jun 05 08:51:35 2007
Return-path: <pwe3-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HvYVa-0000bV-TX; Tue, 05 Jun 2007 08:51:34 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HvYVY-0000bQ-Vo
	for pwe3@ietf.org; Tue, 05 Jun 2007 08:51:32 -0400
Received: from cat.tcb.net ([64.78.150.134] helo=dog.tcb.net)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HvYVW-0006cc-Jd
	for pwe3@ietf.org; Tue, 05 Jun 2007 08:51:32 -0400
Received: from [192.168.1.7] (VDSL-151-118-149-96.DNVR.QWEST.NET
	[151.118.149.96]) (using TLSv1 with cipher AES128-SHA (128/128 bits))
	(No client certificate requested)
	by dog.tcb.net (Postfix) with ESMTP id DB49564347
	for <pwe3@ietf.org>; Tue,  5 Jun 2007 06:51:21 -0600 (MDT)
Mime-Version: 1.0 (Apple Message framework v752.3)
In-Reply-To: <46655BAD.7080806@cisco.com>
References: <E1HFJ1e-0006vT-Kv@stiedprstage1.ietf.org>
	<EC5C009B-160F-4D0E-80EF-F66D31B17022@tcb.net>
	<46655BAD.7080806@cisco.com>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <12C523C8-5521-4C04-A276-74D00FE0F1FE@tcb.net>
Content-Transfer-Encoding: 7bit
From: Danny McPherson <danny@tcb.net>
Subject: Re: [PWE3] WG LC:draft-ietf-pwe3-pw-tc-mib-10.txt
Date: Tue, 5 Jun 2007 06:51:19 -0600
To: "pwe3 WG ((((((((E-mail))))))))" <pwe3@ietf.org>
X-Mailer: Apple Mail (2.752.3)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 944ecb6e61f753561f559a497458fb4f
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>
Errors-To: pwe3-bounces@ietf.org


>
> Danny McPherson wrote:
>> Folks,
>> Please consider today the start of a two week WG LC for
>> this document.  The call for comments from the WG will end
>> on 6/19.  Please provide feedback to the mailing list or
>> authors ASAP.

Oops, folks, I forwarded the wrong I-D announcement, it should
have been the -11 revision, available here:

http://tools.ietf.org/id/draft-ietf-pwe3-pw-tc-mib-11.txt

-danny


>>
>> Thanks!
>>
>> -danny
>>
>>
>> Begin forwarded message:
>>
>>> From: Internet-Drafts@ietf.org
>>> Date: February 8, 2007 4:50:02 PM MST
>>> To: i-d-announce@ietf.org
>>> Cc: pwe3@ietf.org
>>> Subject: [PWE3] I-D ACTION:draft-ietf-pwe3-pw-tc-mib-10.txt
>>>
>>> A New Internet-Draft is available from the on-line Internet-Drafts
>>> directories.
>>> This draft is a work item of the Pseudowire Emulation Edge to  
>>> Edge Working Group of the IETF.
>>>
>>>     Title        : Definitions for Textual Conventions and for  
>>> Managing Pseudo-Wires over PSN
>>>     Author(s)    : T. Nadeau, et al.
>>>     Filename    : draft-ietf-pwe3-pw-tc-mib-10.txt
>>>     Pages        : 11
>>>     Date        : 2007-2-8
>>>     This memo defines a Management Information Base (MIB) module  
>>> which
>>>    contains Textual Conventions (TCs) to represent commonly-used  
>>> Pseudo
>>>    Wire (PW) management information.  The intent is that these  
>>> TCs will
>>>    be imported and used in PW-related MIB modules that would  
>>> otherwise
>>>    define their own representations.
>>>
>>> A URL for this Internet-Draft is:
>>> http://www.ietf.org/internet-drafts/draft-ietf-pwe3-pw-tc-mib-10.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-pw-tc-mib-10.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-pw-tc-mib-10.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-Type: text/plain
>>> Content-ID: <2007-2-8161613.I-D@ietf.org>
>>>
>>> _______________________________________________
>>> 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 Tue Jun 05 09:19:01 2007
Return-path: <pwe3-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HvYw8-00061y-8T; Tue, 05 Jun 2007 09:19:00 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HvYw7-00061l-De
	for pwe3@ietf.org; Tue, 05 Jun 2007 09:18:59 -0400
Received: from rtp-iport-1.cisco.com ([64.102.122.148])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HvYw7-0002qi-3I
	for pwe3@ietf.org; Tue, 05 Jun 2007 09:18:59 -0400
Received: from rtp-dkim-1.cisco.com ([64.102.121.158])
	by rtp-iport-1.cisco.com with ESMTP; 05 Jun 2007 09:18:59 -0400
X-IronPort-AV: i="4.16,385,1175486400"; 
	d="scan'208"; a="61964390:sNHT51348030"
Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13])
	by rtp-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id l55DIwX2015164; 
	Tue, 5 Jun 2007 09:18:58 -0400
Received: from stewart-bryants-computer.local (rtp-vpn2-479.cisco.com
	[10.82.241.223])
	by rtp-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id l55DIn5f022607; 
	Tue, 5 Jun 2007 13:18:49 GMT
Message-ID: <466562BC.4060403@cisco.com>
Date: Tue, 05 Jun 2007 14:18:52 +0100
From: Stewart Bryant <stbryant@cisco.com>
User-Agent: Thunderbird 2.0.0.0 (Macintosh/20070326)
MIME-Version: 1.0
To: Danny McPherson <danny@tcb.net>
Subject: Re: [PWE3] WG LC:draft-ietf-pwe3-pw-tc-mib-10.txt
References: <E1HFJ1e-0006vT-Kv@stiedprstage1.ietf.org>
	<EC5C009B-160F-4D0E-80EF-F66D31B17022@tcb.net>
In-Reply-To: <EC5C009B-160F-4D0E-80EF-F66D31B17022@tcb.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=4116; t=1181049538;
	x=1181913538; c=relaxed/simple; s=rtpdkim1001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=stbryant@cisco.com;
	z=From:=20Stewart=20Bryant=20<stbryant@cisco.com>
	|Subject:=20Re=3A=20[PWE3]=20WG=20LC=3Adraft-ietf-pwe3-pw-tc-mib-10.txt
	|Sender:=20 |To:=20Danny=20McPherson=20<danny@tcb.net>;
	bh=k0x2YnlcxzfK8I8FARj20A9kS0XiNk4Stt9ZSgNIk+s=;
	b=PvGc9WKOF0Y4UAbjEWx/xOEE/eRFWGq3djdAu1x/7MHGfDnYeJZtx4U39Yxh8JOzVfm9mm3+
	BOrvIR8wJ7sZ1s6yZmgWqDBSZLdYMVAFCtds9GYC+GxdCrBeKPdE9JZC;
Authentication-Results: rtp-dkim-1; header.From=stbryant@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim1001 verified; ); 
X-Spam-Score: 0.1 (/)
X-Scan-Signature: b132cb3ed2d4be2017585bf6859e1ede
Cc: "pwe3 WG \(\(\(\(\(\(\(\(E-mail\)\)\)\)\)\)\)\)" <pwe3@ietf.org>
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: stbryant@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>
Errors-To: pwe3-bounces@ietf.org



A few comments:


The current version is -11

======

There are instances of the term "pseudo wire" and "pseudo-wire" when we 
agreed a little while ago to use the term pseudowire.

======

DESCRIPTION
           "Pseudo-Wire Identifier. Used to identify the PW
            (together with some other fields) in the signaling
            session."
      SYNTAX  Unsigned32

Shouldn't this be a 1..2^32-1 (control spec says non-zero)

========

I am suprised that the PwOperStatusTC ::= TEXTUAL-CONVENTION states
do not have a one to one mapping with Pseudo Wire Status Codes Registry 
at least to the point of having the registry name in the text.


- Stewart

Danny McPherson wrote:
> Folks,
> Please consider today the start of a two week WG LC for
> this document.  The call for comments from the WG will end
> on 6/19.  Please provide feedback to the mailing list or
> authors ASAP.
>
> Thanks!
>
> -danny
>
>
> Begin forwarded message:
>
>> From: Internet-Drafts@ietf.org
>> Date: February 8, 2007 4:50:02 PM MST
>> To: i-d-announce@ietf.org
>> Cc: pwe3@ietf.org
>> Subject: [PWE3] I-D ACTION:draft-ietf-pwe3-pw-tc-mib-10.txt
>>
>> A New Internet-Draft is available from the on-line Internet-Drafts
>> directories.
>> This draft is a work item of the Pseudowire Emulation Edge to Edge 
>> Working Group of the IETF.
>>
>>     Title        : Definitions for Textual Conventions and for 
>> Managing Pseudo-Wires over PSN
>>     Author(s)    : T. Nadeau, et al.
>>     Filename    : draft-ietf-pwe3-pw-tc-mib-10.txt
>>     Pages        : 11
>>     Date        : 2007-2-8
>>     
>> This memo defines a Management Information Base (MIB) module which
>>    contains Textual Conventions (TCs) to represent commonly-used Pseudo
>>    Wire (PW) management information.  The intent is that these TCs will
>>    be imported and used in PW-related MIB modules that would otherwise
>>    define their own representations.
>>
>> A URL for this Internet-Draft is:
>> http://www.ietf.org/internet-drafts/draft-ietf-pwe3-pw-tc-mib-10.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-pw-tc-mib-10.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-pw-tc-mib-10.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-Type: text/plain
>> Content-ID: <2007-2-8161613.I-D@ietf.org>
>>
>> _______________________________________________
>> 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 Wed Jun 06 05:23:17 2007
Return-path: <pwe3-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HvrjQ-0003KO-CK; Wed, 06 Jun 2007 05:23:08 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hvrgt-0002Ml-6R
	for pwe3@ietf.org; Wed, 06 Jun 2007 05:20:31 -0400
Received: from tlvmail1.corrigent.com ([213.31.203.2])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hvrfh-0006lJ-2g
	for pwe3@ietf.org; Wed, 06 Jun 2007 05:19:17 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
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] WG LC:draft-ietf-pwe3-pw-tc-mib-10.txt
Date: Wed, 6 Jun 2007 12:18:34 +0300
Message-ID: <44F4E579A764584EA9BDFD07D0CA0813BFAFC7@tlvmail1.corrigent.com>
In-Reply-To: <466562BC.4060403@cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [PWE3] WG LC:draft-ietf-pwe3-pw-tc-mib-10.txt
Thread-Index: AcendB3XM6PPJCFBSbWmJnVKI3aoxAApc+Xw
References: <E1HFJ1e-0006vT-Kv@stiedprstage1.ietf.org><EC5C009B-160F-4D0E-80EF-F66D31B17022@tcb.net>
	<466562BC.4060403@cisco.com>
From: "David Zelig" <Davidz@corrigent.com>
To: <stbryant@cisco.com>,
	"Danny McPherson" <danny@tcb.net>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 03169bfe4792634a390035a01a6c6d2f
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>
Errors-To: pwe3-bounces@ietf.org

Stewart,
Please see inline=20

-----Original Message-----
From: Stewart Bryant [mailto:stbryant@cisco.com]=20
Sent: Tuesday, June 05, 2007 4:19 PM
To: Danny McPherson
Cc: pwe3 WG ((((((((E-mail))))))))
Subject: Re: [PWE3] WG LC:draft-ietf-pwe3-pw-tc-mib-10.txt



A few comments:


The current version is -11

=3D=3D=3D=3D=3D=3D

There are instances of the term "pseudo wire" and "pseudo-wire" when we
agreed a little while ago to use the term pseudowire.

[DZ] OK, will fix.

=3D=3D=3D=3D=3D=3D

DESCRIPTION
           "Pseudo-Wire Identifier. Used to identify the PW
            (together with some other fields) in the signaling
            session."
      SYNTAX  Unsigned32

Shouldn't this be a 1..2^32-1 (control spec says non-zero)

[DZ} We allow the value of zero in PW-STD-MIB module to allow manual
configuration or when the generalized FEC is used - The PW ID is not
applicable.
=3D=3D=3D=3D=3D=3D=3D=3D

I am suprised that the PwOperStatusTC ::=3D TEXTUAL-CONVENTION states do
not have a one to one mapping with Pseudo Wire Status Codes Registry at
least to the point of having the registry name in the text.

[DZ] This OperStatus is based on standard SNMP OperStatus, PwStatus =
::=3D
TEXTUAL-CONVENTION is the one that intends to match the Pseudo Wire
Status Codes Registry - I see that the object names can be phrased
better to match RFC 4446.

David

- Stewart

Danny McPherson wrote:
> Folks,
> Please consider today the start of a two week WG LC for
> this document.  The call for comments from the WG will end
> on 6/19.  Please provide feedback to the mailing list or
> authors ASAP.
>
> Thanks!
>
> -danny
>
>
> Begin forwarded message:
>
>> From: Internet-Drafts@ietf.org
>> Date: February 8, 2007 4:50:02 PM MST
>> To: i-d-announce@ietf.org
>> Cc: pwe3@ietf.org
>> Subject: [PWE3] I-D ACTION:draft-ietf-pwe3-pw-tc-mib-10.txt
>>
>> A New Internet-Draft is available from the on-line Internet-Drafts
>> directories.
>> This draft is a work item of the Pseudowire Emulation Edge to Edge=20
>> Working Group of the IETF.
>>
>>     Title        : Definitions for Textual Conventions and for=20
>> Managing Pseudo-Wires over PSN
>>     Author(s)    : T. Nadeau, et al.
>>     Filename    : draft-ietf-pwe3-pw-tc-mib-10.txt
>>     Pages        : 11
>>     Date        : 2007-2-8
>>    =20
>> This memo defines a Management Information Base (MIB) module which
>>    contains Textual Conventions (TCs) to represent commonly-used
Pseudo
>>    Wire (PW) management information.  The intent is that these TCs
will
>>    be imported and used in PW-related MIB modules that would
otherwise
>>    define their own representations.
>>
>> A URL for this Internet-Draft is:
>> http://www.ietf.org/internet-drafts/draft-ietf-pwe3-pw-tc-mib-10.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-pw-tc-mib-10.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-pw-tc-mib-10.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 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-Type: text/plain
>> Content-ID: <2007-2-8161613.I-D@ietf.org>
>>
>> _______________________________________________
>> 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


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



From pwe3-bounces@ietf.org Wed Jun 06 16:11:44 2007
Return-path: <pwe3-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hw1r4-0002I3-0a; Wed, 06 Jun 2007 16:11:42 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hw1dA-0005Ib-Mz; Wed, 06 Jun 2007 15:57:20 -0400
Received: from ns1.neustar.com ([2001:503:c779:1a::9c9a:108a])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1Hw1W6-0004Ps-L6; Wed, 06 Jun 2007 15:50:02 -0400
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10]) by ns1.neustar.com (Postfix) with ESMTP id 8434326F74;
	Wed,  6 Jun 2007 19:50:02 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1Hw1W6-0003yA-DB; Wed, 06 Jun 2007 15:50:02 -0400
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1Hw1W6-0003yA-DB@stiedprstage1.ietf.org>
Date: Wed, 06 Jun 2007 15:50:02 -0400
X-Spam-Score: -2.5 (--)
X-Scan-Signature: 10ba05e7e8a9aa6adb025f426bef3a30
Cc: pwe3@ietf.org
Subject: [PWE3] I-D ACTION:draft-ietf-pwe3-ms-pw-arch-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>
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 Pseudowire Emulation Edge to Edge Working Group of the IETF.

	Title		: An Architecture for Multi-Segment Pseudo Wire Emulation Edge-to-Edge
	Author(s)	: M. Bocci, S. Bryant
	Filename	: draft-ietf-pwe3-ms-pw-arch-03.txt
	Pages		: 20
	Date		: 2007-6-6
	
This document describes an architecture for extending pseudowire 
   emulation across multiple packet switched network segments. Scenarios 
   are discussed where each segment of a given edge-to-edge emulated 
   service spans a different provider's PSN, and where the emulated 
   service originates and terminates on the same providers PSN, but may 
   pass through several PSN tunnel segments in that PSN. It presents an 
   architectural framework for such multi-segment pseudowires, defines 
   terminology, and specifies the various protocol elements and their 
   functions.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-pwe3-ms-pw-arch-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-ms-pw-arch-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-ms-pw-arch-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: <2007-6-6125039.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-pwe3-ms-pw-arch-03.txt

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

Content-Type: text/plain
Content-ID: <2007-6-6125039.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 Thu Jun 07 02:22:02 2007
Return-path: <pwe3-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HwBNb-0005xO-Ug; Thu, 07 Jun 2007 02:21:55 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HwBNa-0005tT-T3
	for pwe3@ietf.org; Thu, 07 Jun 2007 02:21:54 -0400
Received: from main.gmane.org ([80.91.229.2] helo=ciao.gmane.org)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HwBNY-0007bY-TQ
	for pwe3@ietf.org; Thu, 07 Jun 2007 02:21:54 -0400
Received: from root by ciao.gmane.org with local (Exim 4.43)
	id 1HwBLm-0003YF-D5
	for pwe3@ietf.org; Thu, 07 Jun 2007 08:20:02 +0200
Received: from hasso.estpak.ee ([194.126.115.44])
	by main.gmane.org with esmtp (Gmexim 0.1 (Debian))
	id 1AlnuQ-0007hv-00
	for <pwe3@ietf.org>; Thu, 07 Jun 2007 08:20:02 +0200
Received: from hasso by hasso.estpak.ee with local (Gmexim 0.1 (Debian))
	id 1AlnuQ-0007hv-00
	for <pwe3@ietf.org>; Thu, 07 Jun 2007 08:20:02 +0200
X-Injected-Via-Gmane: http://gmane.org/
To: pwe3@ietf.org
From: Hasso Tepper <hasso@estpak.ee>
Date: Thu, 07 Jun 2007 08:51:00 +0300
Lines: 11
Message-ID: <f486c9$fan$1@sea.gmane.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7Bit
X-Complaints-To: usenet@sea.gmane.org
X-Gmane-NNTP-Posting-Host: hasso.estpak.ee
User-Agent: KNode/0.10.5
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 68c8cc8a64a9d0402e43b8eee9fc4199
Subject: [PWE3] LDP Label Withdrawal Procedures in RFC4447
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>
Errors-To: pwe3-bounces@ietf.org

RFC4447 6.3 states:

"The interface parameter sub-TLVs, or TLV, MUST NOT be present in any LDP PW
Label Withdraw or Label Release message."

I'd like to know what are the reasons behind this 'MUST NOT'? What breaks
from the protocol point of view?


-- 
Hasso Tepper


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



From pwe3-bounces@ietf.org Fri Jun 08 02:09:37 2007
Return-path: <pwe3-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HwXf8-0002Gf-If; Fri, 08 Jun 2007 02:09:30 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HwXf6-0002GX-ER
	for pwe3@ietf.org; Fri, 08 Jun 2007 02:09:28 -0400
Received: from ams-iport-1.cisco.com ([144.254.224.140])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HwXf4-0008Dh-Qv
	for pwe3@ietf.org; Fri, 08 Jun 2007 02:09:28 -0400
Received: from ams-dkim-1.cisco.com ([144.254.224.138])
	by ams-iport-1.cisco.com with ESMTP; 08 Jun 2007 08:09:26 +0200
Received: from ams-core-1.cisco.com (ams-core-1.cisco.com [144.254.224.150])
	by ams-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id l5869QZU019044
	for <pwe3@ietf.org>; Fri, 8 Jun 2007 08:09:26 +0200
Received: from stewart-bryants-computer.local (ams3-vpn-dhcp236.cisco.com
	[10.61.64.236])
	by ams-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id l5869LDR029313
	for <pwe3@ietf.org>; Fri, 8 Jun 2007 06:09:25 GMT
Message-ID: <4668F297.2050204@cisco.com>
Date: Fri, 08 Jun 2007 07:09:27 +0100
From: Stewart Bryant <stbryant@cisco.com>
User-Agent: Thunderbird 2.0.0.0 (Macintosh/20070326)
MIME-Version: 1.0
To: pwe3 <pwe3@ietf.org>
Content-Type: multipart/mixed; boundary="------------050302090900050206050908"
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=7003; t=1181282966;
	x=1182146966; c=relaxed/simple; s=amsdkim1002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=stbryant@cisco.com;
	z=From:=20Stewart=20Bryant=20<stbryant@cisco.com>
	|Subject:=20[Fwd=3A=20[arch-d]=20Invitation=20to=20join=20new=20unofficia
	l=20IETF=20mailing=20list=3A=0A=20re-ECN] |Sender:=20;
	bh=0plXs9L5EGTywH2ou2row1NwRGXorXDte9m/xCvc3nw=;
	b=vsDApm2YMmuCEnaTwUwGBSu/55D6uyg0ss61bOokr2R3/7B3eU0v8ibcqd1LxREqUqjsg8jL
	jaRTLYwJRBvD9XSh8guMx7A+lSO2N1H5OCc40TwbfvDigXdaSl5+s+kB;
Authentication-Results: ams-dkim-1; header.From=stbryant@cisco.com; dkim=pass (
	sig from cisco.com/amsdkim1002 verified; ); 
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 789c141a303c09204b537a4078e2a63f
Subject: [PWE3] [Fwd: [arch-d] Invitation to join new unofficial IETF
 mailing list: re-ECN]
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: stbryant@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>
Errors-To: pwe3-bounces@ietf.org

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



--------------050302090900050206050908
Content-Type: message/rfc822;
	name="[arch-d] Invitation to join new unofficial IETF mailing list:
	re-ECN.eml"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline;
	filename*0="[arch-d] Invitation to join new unofficial IETF mailing
	list"; filename*1=": re-ECN.eml"

X-Account-Key: account3
X-Mozilla-Keys: 
Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117])
	by cisco.com (8.8.8-Cisco List Logging/8.8.8) with ESMTP id LAA02906
	for <stbryant@mrwint.cisco.com>; Thu, 7 Jun 2007 11:58:41 +0100 (BST)
Received: from sj-dkim-2.cisco.com ([171.71.179.186])
	by sj-iport-6.cisco.com with ESMTP; 07 Jun 2007 03:58:40 -0700
Received: from sj-core-2.cisco.com (sj-core-2.cisco.com [171.71.177.254])
	by sj-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id l57AwYxk031622; 
	Thu, 7 Jun 2007 03:58:34 -0700
Received: from sj-inbound-f.cisco.com (sj-inbound-f.cisco.com
	[128.107.234.207])
	by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id l57AwSaN021837;
	Thu, 7 Jun 2007 10:58:34 GMT
Received: from odin.ietf.org (HELO megatron.ietf.org) ([156.154.16.145])
	by sj-inbound-f.cisco.com with ESMTP; 07 Jun 2007 03:58:30 -0700
X-from-outside-Cisco: 156.154.16.145
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgAAAOKAZ0acmhCRkmdsb2JhbACPaQEBAQEHCAYNHw
X-IronPort-AV: i="4.16,394,1175497200"; d="scan'208"; a="5912250:sNHT14456100"
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HwFh6-0001NM-Kr; Thu, 07 Jun 2007 06:58:20 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HwFh3-0001JJ-PJ
	for architecture-discuss@ietf.org; Thu, 07 Jun 2007 06:58:17 -0400
Received: from smtp3.smtp.bt.com ([217.32.164.138])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HwFh1-0006yQ-1B
	for architecture-discuss@ietf.org; Thu, 07 Jun 2007 06:58:17 -0400
Received: from i2kc06-ukbr.domain1.systemhost.net ([193.113.197.70]) by
	smtp3.smtp.bt.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 7 Jun 2007 11:58:14 +0100
Received: from cbibipnt05.iuser.iroot.adidom.com ([147.149.196.177]) by
	i2kc06-ukbr.domain1.systemhost.net with Microsoft
	SMTPSVC(6.0.3790.1830); Thu, 7 Jun 2007 11:58:14 +0100
Received: From bagheera.jungle.bt.co.uk ([132.146.168.158]) by
	cbibipnt05.iuser.iroot.adidom.com (WebShield SMTP v4.5 MR1a
	P0803.399); id 1181213892637; Thu, 7 Jun 2007 11:58:12 +0100
Received: from mut.jungle.bt.co.uk ([10.86.0.47])
	by bagheera.jungle.bt.co.uk (8.13.5/8.12.8) with ESMTP id
	l57Aw63i011973; Thu, 7 Jun 2007 11:58:09 +0100
Message-Id: <5.2.1.1.2.20070607110607.0525c8e0@pop3.jungle.bt.co.uk>
X-Sender: rbriscoe@pop3.jungle.bt.co.uk
X-Mailer: QUALCOMM Windows Eudora Version 5.2.1
Date: Thu, 07 Jun 2007 11:58:10 +0100
To: "tsvwg IETF list" <tsvwg@ietf.org>, "iccrg IRTF list" <iccrg@cs.ucl.ac.uk>,
	"arch-d list" <architecture-discuss@ietf.org>,
	"DCCP IETF list" <dccp@ietf.org>, "tsv-area IETF list" <tsv-area@ietf.org>,
	"e2e IRTF list" <end2end-interest@postel.org>,
	"eme IRTF list" <eme@irtf.org>
From: Bob Briscoe <rbriscoe@jungle.bt.co.uk>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Spam-Score: -3.77 () ALL_TRUSTED,AWL,BAYES_00
X-Scanned-By: MIMEDefang 2.56 on 132.146.168.158
X-OriginalArrivalTime: 07 Jun 2007 10:58:14.0128 (UTC)
	FILETIME=[BEE06F00:01C7A8F2]
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 50a516d93fd399dc60588708fd9a3002
Subject: [arch-d] Invitation to join new unofficial IETF mailing list: re-ECN
X-BeenThere: architecture-discuss@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: open discussion forum for long/wide-range architectural issues
	<architecture-discuss.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/architecture-discuss>, 
	<mailto:architecture-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/architecture-discuss>
List-Post: <mailto:architecture-discuss@ietf.org>
List-Help: <mailto:architecture-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/architecture-discuss>, 
	<mailto:architecture-discuss-request@ietf.org?subject=subscribe>
Errors-To: architecture-discuss-bounces@ietf.org
Authentication-Results: sj-dkim-2; header.From=rbriscoe@jungle.bt.co.uk;
	dkim=neutral

Folks,

You are invited to subscribe to a new unofficial IETF mailing list on 
re-ECN via <https://www1.ietf.org/mailman/listinfo/re-ecn>

Re-ECN is proposed as an extension to explicit congestion notification 
(ECN) intended to enable enforcement of fairness for congestion control & 
QoS including mitigation of DDoS and prevention of cheating between both 
networks & users.

Why has this list been created?:
At the last IETF in Prague, about 30-40 people got together at an 
unofficial BoF (Birds of a Feather) to hear about the architectural intent 
of re-ECN and to discuss how to move forward.

It was decided to take an ad hoc approach initially, somewhat along the 
lines of how HIP got started. If a community hangs together around this 
work, then it may form an IRTF or IETF working group.

The room was unanimous that re-ECN addresses a problem that is interesting, 
and about 75% were interested in using it, if it was implemented. Half a 
dozen people expressed interest in implementing the protocol. Full notes, 
transcript & slides as well as background papers are at:
<http://www.cs.ucl.ac.uk/staff/B.Briscoe/projects/refb/#Presentations>

If interested in discussion of design and implementation of the re-ECN 
protocol, pls subscribe via the link at the start.

---------------------------------------------------------------------------
Re-ECN is not an official working group of the IETF or IRTF. But the IETF 
has agreed to host the list to create a community around this work who may 
wish to bring it forward for standardisation. As such, if you subscribe, 
you will be asked to note well the normal IETF rules.

This invitation will only be sent to relevant lists once. But apologies if 
you are on more than one of these lists.

Cheers


Bob



____________________________________________________________________________
Bob Briscoe, <bob.briscoe@bt.com>      Networks Research Centre, BT Research
B54/77 Adastral Park,Martlesham Heath,Ipswich,IP5 3RE,UK.    +44 1473 645196  



_______________________________________________
Architecture-discuss mailing list
Architecture-discuss@ietf.org
https://www1.ietf.org/mailman/listinfo/architecture-discuss


--------------050302090900050206050908
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

--------------050302090900050206050908--




From pwe3-bounces@ietf.org Fri Jun 08 05:41:23 2007
Return-path: <pwe3-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hway3-00021z-EK; Fri, 08 Jun 2007 05:41:15 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hway1-00021k-Tx
	for pwe3@ietf.org; Fri, 08 Jun 2007 05:41:14 -0400
Received: from division.aa.arbor.net ([152.160.38.65] helo=gott.aa.arbor.net)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hway0-0001aU-GS
	for pwe3@ietf.org; Fri, 08 Jun 2007 05:41:13 -0400
Received: from [172.30.30.91] (unknown [10.0.6.158])
	by gott.aa.arbor.net (Postfix) with ESMTP id 849721424D
	for <pwe3@ietf.org>; Fri,  8 Jun 2007 05:39:15 -0400 (EDT)
Mime-Version: 1.0 (Apple Message framework v752.3)
References: <E1HrJJy-0000ki-5n@stiedprstage1.ietf.org>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <9E7EDEB4-D663-4039-AC39-EC31BED9F762@tcb.net>
Content-Transfer-Encoding: 7bit
From: Danny McPherson <danny@tcb.net>
Date: Fri, 8 Jun 2007 03:40:55 -0600
To: "pwe3 ((((((((E-mail)))))))) WG" <pwe3@ietf.org>
X-Mailer: Apple Mail (2.752.3)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b7b9551d71acde901886cc48bfc088a6
Subject: [PWE3] WG LC:draft-ietf-pwe3-cep-mib-10.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>
Errors-To: pwe3-bounces@ietf.org

Folks,
Please consider today the start of a two week WG LC for
this document.  The call for comments from the WG will end
on 6/22.  Please provide feedback to the mailing list or
authors ASAP.

Thanks!

-danny


Begin forwarded message:

> From: Internet-Drafts@ietf.org
> Date: May 24, 2007 1:50:02 PM MDT
> To: i-d-announce@ietf.org
> Cc: pwe3@ietf.org
> Subject: I-D ACTION:draft-ietf-pwe3-cep-mib-10.txt
> Reply-To: internet-drafts@ietf.org
>
> A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
> This draft is a work item of the Pseudowire Emulation Edge to Edge  
> Working Group of the IETF.
>
> 	Title		: SONET/SDH Circuit Emulation Service Over Packet (CEP)  
> Management Information Base Using SMIv2
> 	Author(s)	: T. Nadeau, et al.
> 	Filename	: draft-ietf-pwe3-cep-mib-10.txt
> 	Pages		: 71
> 	Date		: 2007-5-24
> 	
> This memo defines an experimental portion of the Management
>    Information Base (MIB) for use with network management protocols in
>    the Internet community.  In particular, it describes managed  
> objects
>    for modeling SONET/SDH circuits over a Packet Switch Network (PSN).
>
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ietf-pwe3-cep-mib-10.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-cep-mib-10.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-cep-mib-10.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-Type: text/plain
> Content-ID: <2007-5-24134717.I-D@ietf.org>
>
> _______________________________________________
> I-D-Announce mailing list
> I-D-Announce@ietf.org
> https://www1.ietf.org/mailman/listinfo/i-d-announce


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



From pwe3-bounces@ietf.org Fri Jun 08 05:41:26 2007
Return-path: <pwe3-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HwayE-0002oS-8O; Fri, 08 Jun 2007 05:41:26 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HwayD-0002ke-I4
	for pwe3@ietf.org; Fri, 08 Jun 2007 05:41:25 -0400
Received: from division.aa.arbor.net ([152.160.38.65] helo=gott.aa.arbor.net)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HwayD-0001ic-4T
	for pwe3@ietf.org; Fri, 08 Jun 2007 05:41:25 -0400
Received: from [172.30.30.91] (unknown [10.0.6.158])
	by gott.aa.arbor.net (Postfix) with ESMTP id 142AB1424D
	for <pwe3@ietf.org>; Fri,  8 Jun 2007 05:39:29 -0400 (EDT)
Mime-Version: 1.0 (Apple Message framework v752.3)
References: <E1HuD8M-0003jh-3C@stiedprstage1.ietf.org>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <AFE8FA75-934A-4D36-936E-0065EACD9EB4@tcb.net>
Content-Transfer-Encoding: 7bit
From: Danny McPherson <danny@tcb.net>
Date: Fri, 8 Jun 2007 03:41:11 -0600
To: "pwe3 ((((((((E-mail)))))))) WG" <pwe3@ietf.org>
X-Mailer: Apple Mail (2.752.3)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 3002fc2e661cd7f114cb6bae92fe88f1
Subject: [PWE3] WG LC:draft-ietf-pwe3-pw-mib-11.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>
Errors-To: pwe3-bounces@ietf.org

Folks,
Please consider today the start of a two week WG LC for
this document.  The call for comments from the WG will end
on 6/22.  Please provide feedback to the mailing list or
authors ASAP.

Thanks!

-danny


Begin forwarded message:

> From: Internet-Drafts@ietf.org
> Date: June 1, 2007 1:50:02 PM MDT
> To: i-d-announce@ietf.org
> Cc: pwe3@ietf.org
> Subject: I-D ACTION:draft-ietf-pwe3-pw-mib-11.txt
> Reply-To: internet-drafts@ietf.org
>
> A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
> This draft is a work item of the Pseudowire Emulation Edge to Edge  
> Working Group of the IETF.
>
> 	Title		: Pseudo Wire (PW) Management Information Base
> 	Author(s)	: D. Zelig, et al.
> 	Filename	: draft-ietf-pwe3-pw-mib-11.txt
> 	Pages		: 63
> 	Date		: 2007-6-1
> 	
> This memo defines an experimental portion of the Management
>    Information Base for use with network management protocols in the
>    Internet community.  In particular, it describes managed objects  
> for
>    modeling of Pseudo Wire Edge-to-Edge services carried over a  
> general
>    Packet Switched Network.
>
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ietf-pwe3-pw-mib-11.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-pw-mib-11.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-pw-mib-11.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-Type: text/plain
> Content-ID: <2007-6-1103323.I-D@ietf.org>
>
> _______________________________________________
> I-D-Announce mailing list
> I-D-Announce@ietf.org
> https://www1.ietf.org/mailman/listinfo/i-d-announce


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



From pwe3-bounces@ietf.org Fri Jun 08 05:41:23 2007
Return-path: <pwe3-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hway8-0002Ja-QZ; Fri, 08 Jun 2007 05:41:20 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hway7-0002Ih-PV
	for pwe3@ietf.org; Fri, 08 Jun 2007 05:41:19 -0400
Received: from division.aa.arbor.net ([152.160.38.65] helo=gott.aa.arbor.net)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hway5-0001bu-Re
	for pwe3@ietf.org; Fri, 08 Jun 2007 05:41:19 -0400
Received: from [172.30.30.91] (unknown [10.0.6.158])
	by gott.aa.arbor.net (Postfix) with ESMTP id 08B271424D
	for <pwe3@ietf.org>; Fri,  8 Jun 2007 05:39:22 -0400 (EDT)
Mime-Version: 1.0 (Apple Message framework v752.3)
References: <E1HrJJy-0000ko-6y@stiedprstage1.ietf.org>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <9CD2D9AF-5DB9-4C9F-ABAC-43A30190DF98@tcb.net>
Content-Transfer-Encoding: 7bit
From: Danny McPherson <danny@tcb.net>
Date: Fri, 8 Jun 2007 03:41:04 -0600
To: "pwe3 ((((((((E-mail)))))))) WG" <pwe3@ietf.org>
X-Mailer: Apple Mail (2.752.3)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 31247fb3be228bb596db9127becad0bc
Subject: [PWE3] WG LC:draft-ietf-pwe3-enet-mib-11.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>
Errors-To: pwe3-bounces@ietf.org

Folks,
Please consider today the start of a two week WG LC for
this document.  The call for comments from the WG will end
on 6/22.  Please provide feedback to the mailing list or
authors ASAP.

Thanks!

-danny


Begin forwarded message:

> From: Internet-Drafts@ietf.org
> Date: May 24, 2007 1:50:02 PM MDT
> To: i-d-announce@ietf.org
> Cc: pwe3@ietf.org
> Subject: I-D ACTION:draft-ietf-pwe3-enet-mib-11.txt
> Reply-To: internet-drafts@ietf.org
>
> A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
> This draft is a work item of the Pseudowire Emulation Edge to Edge  
> Working Group of the IETF.
>
> 	Title		: Ethernet Pseudo-Wire (PW) Management Information Base
> 	Author(s)	: D. Zelig, T. Nadeau
> 	Filename	: draft-ietf-pwe3-enet-mib-11.txt
> 	Pages		: 24
> 	Date		: 2007-5-24
> 	
> This memo defines an experimental portion of the Management
>    Information Base (MIB) for use with network management protocols in
>    the Internet community.  In particular, it describes managed  
> objects
>    for modeling of Ethernet Pseudo-Wire (PW) services.
>
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ietf-pwe3-enet-mib-11.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-enet-mib-11.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-enet-mib-11.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-Type: text/plain
> Content-ID: <2007-5-24135154.I-D@ietf.org>
>
> _______________________________________________
> I-D-Announce mailing list
> I-D-Announce@ietf.org
> https://www1.ietf.org/mailman/listinfo/i-d-announce


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



From pwe3-bounces@ietf.org Fri Jun 08 05:47:29 2007
Return-path: <pwe3-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hwb45-0000bC-3f; Fri, 08 Jun 2007 05:47:29 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hwb44-0000b7-Fn
	for pwe3@ietf.org; Fri, 08 Jun 2007 05:47:28 -0400
Received: from division.aa.arbor.net ([152.160.38.65] helo=gott.aa.arbor.net)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hwb43-0004Rk-8n
	for pwe3@ietf.org; Fri, 08 Jun 2007 05:47:28 -0400
Received: from [172.30.30.91] (unknown [10.0.6.158])
	by gott.aa.arbor.net (Postfix) with ESMTP id 9CA4C1424D
	for <pwe3@ietf.org>; Fri,  8 Jun 2007 05:45:32 -0400 (EDT)
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Transfer-Encoding: 7bit
Message-Id: <A8C3912F-D99C-426D-8681-7DE0DF2E40F3@tcb.net>
Content-Type: text/plain; charset=US-ASCII; format=flowed
To: "pwe3 WG ((((((((E-mail))))))))" <pwe3@ietf.org>
From: Danny McPherson <danny@tcb.net>
Date: Fri, 8 Jun 2007 03:47:13 -0600
X-Mailer: Apple Mail (2.752.3)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 93238566e09e6e262849b4f805833007
Subject: [PWE3] MIB Last Call/Status Summary
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>
Errors-To: pwe3-bounces@ietf.org


Quick summary of PW MIBs recently WG last called:

WG LC ends on 6/19/2007:

draft-ietf-pwe3-pw-tc-mib-11.txt
draft-ietf-pwe3-pw-mpls-mib-12.txt

WG LC ends on 6/22/2007:

draft-ietf-pwe3-enet-mib-11.txt
draft-ietf-pwe3-pw-mib-11.txt
draft-ietf-pwe3-cep-mib-10.txt

Please provide comments on these documents either on
list or directly to the authors ASAP.

The ATM and TDM MIBs completed WG LC in March and are
awaiting MIB DR review completion before submission to the
IESG.

Any comments or questions please let us know.  Thanks!

-danny & Stewart

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



From pwe3-bounces@ietf.org Sat Jun 09 15:37:00 2007
Return-path: <pwe3-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hx6jc-0006rI-Sm; Sat, 09 Jun 2007 15:36:28 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hww32-0004fl-UV
	for pwe3@ietf.org; Sat, 09 Jun 2007 04:11:48 -0400
Received: from smtp4.actcom.co.il ([192.114.47.66])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hww2z-0003IX-Lm
	for pwe3@ietf.org; Sat, 09 Jun 2007 04:11:48 -0400
Received: from LORLYNICKLASS (l192-117-121-90.broadband.actcom.net.il
	[192.117.121.90])
	by smtp4.actcom.co.il (8.13.6/8.13.6) with ESMTP id l598BCGr009652;
	Sat, 9 Jun 2007 11:11:36 +0300
From: "Orly Nicklass" <orly-n@actcom.co.il>
To: <stbryant@cisco.com>, "'Danny McPherson'" <danny@tcb.net>
Subject: RE: [PWE3] WG LC:draft-ietf-pwe3-pw-tc-mib-10.txt
Date: Sat, 9 Jun 2007 11:11:11 +0300
Message-ID: <001b01c7aa6d$c55e7e90$6901a8c0@seabridge.co.il>
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook 11
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3028
Thread-Index: AcendCMVQ61JbWwaTCCtxc8dHkW26ACRG0Ew
In-Reply-To: <466562BC.4060403@cisco.com>
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 876202f9cbc0933cffbc58102e40f8f2
X-Mailman-Approved-At: Sat, 09 Jun 2007 15:36:27 -0400
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>
Content-Type: multipart/mixed; boundary="===============0806493268=="
Errors-To: pwe3-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0806493268==
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_001C_01C7AA86.ECD01D30"

This is a multi-part message in MIME format.

------=_NextPart_000_001C_01C7AA86.ECD01D30
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

PwOperStatusTC is aligned with ifOperStatus---- operational state of an
interface

 

  _____  

From: Stewart Bryant [mailto:stbryant@cisco.com] 
Sent: Tuesday, June 05, 2007 16:19
To: Danny McPherson
Cc: pwe3 WG ((((((((E-mail))))))))
Subject: Re: [PWE3] WG LC:draft-ietf-pwe3-pw-tc-mib-10.txt

 

 

A few comments:


The current version is -11

======

There are instances of the term "pseudo wire" and "pseudo-wire" when we
agreed a little while ago to use the term pseudowire.

======

DESCRIPTION
           "Pseudo-Wire Identifier. Used to identify the PW
            (together with some other fields) in the signaling
            session."
      SYNTAX  Unsigned32

Shouldn't this be a 1..2^32-1 (control spec says non-zero)

========

I am suprised that the PwOperStatusTC ::= TEXTUAL-CONVENTION states do not
have a one to one mapping with Pseudo Wire Status Codes Registry at least to
the point of having the registry name in the text.


- Stewart

Danny McPherson wrote:
> Folks,
> Please consider today the start of a two week WG LC for
> this document.  The call for comments from the WG will end
> on 6/19.  Please provide feedback to the mailing list or
> authors ASAP.
>
> Thanks!
>
> -danny
>
>
> Begin forwarded message:
>
>> From: Internet-Drafts@ietf.org
>> Date: February 8, 2007 4:50:02 PM MST
>> To: i-d-announce@ietf.org
>> Cc: pwe3@ietf.org
>> Subject: [PWE3] I-D ACTION:draft-ietf-pwe3-pw-tc-mib-10.txt
>>
>> A New Internet-Draft is available from the on-line Internet-Drafts
>> directories.
>> This draft is a work item of the Pseudowire Emulation Edge to Edge
>> Working Group of the IETF.
>>
>>     Title        : Definitions for Textual Conventions and for
>> Managing Pseudo-Wires over PSN
>>     Author(s)    : T. Nadeau, et al.
>>     Filename    : draft-ietf-pwe3-pw-tc-mib-10.txt
>>     Pages        : 11
>>     Date        : 2007-2-8
>>    
>> This memo defines a Management Information Base (MIB) module which
>>    contains Textual Conventions (TCs) to represent commonly-used Pseudo
>>    Wire (PW) management information.  The intent is that these TCs will
>>    be imported and used in PW-related MIB modules that would otherwise
>>    define their own representations.
>>
>> A URL for this Internet-Draft is:
>> http://www.ietf.org/internet-drafts/draft-ietf-pwe3-pw-tc-mib-10.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-pw-tc-mib-10.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-pw-tc-mib-10.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-Type: text/plain
>> Content-ID: <2007-2-8161613.I-D@ietf.org>
>>
>> _______________________________________________
>> 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


------=_NextPart_000_001C_01C7AA86.ECD01D30
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]-->
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:blue;
	text-decoration:underline;}
p
	{mso-margin-top-alt:auto;
	margin-right:0in;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	font-size:12.0pt;
	font-family:"Times New Roman";}
span.EmailStyle18
	{mso-style-type:personal-reply;
	font-family:Arial;
	color:navy;}
@page Section1
	{size:595.3pt 841.9pt;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
	{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]-->
</head>

<body lang=3DEN-US link=3Dblue vlink=3Dblue>

<div class=3DSection1 dir=3DRTL>

<p class=3DMsoNormal dir=3DLTR><font size=3D2 face=3D"Times New =
Roman"><span
style=3D'font-size:10.0pt'>PwOperStatusTC is aligned with =
ifOperStatus----</span></font>
operational state of an interface<font size=3D2 color=3Dnavy =
face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial;color:navy'><o:p></o:p></span=
></font></p>

<p class=3DMsoNormal dir=3DLTR><font size=3D2 color=3Dnavy =
face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p>=
</span></font></p>

<div style=3D'border:none;border-left:solid blue 1.5pt;padding:0in 0in =
0in 4.0pt'>

<div>

<div class=3DMsoNormal align=3Dcenter dir=3DLTR =
style=3D'text-align:center'><font
size=3D3 face=3D"Times New Roman"><span style=3D'font-size:12.0pt'>

<hr size=3D2 width=3D"100%" align=3Dcenter tabindex=3D-1>

</span></font></div>

<p class=3DMsoNormal dir=3DLTR><b><font size=3D2 face=3DTahoma><span =
style=3D'font-size:
10.0pt;font-family:Tahoma;font-weight:bold'>From:</span></font></b><font
size=3D2 face=3DTahoma><span =
style=3D'font-size:10.0pt;font-family:Tahoma'> Stewart
Bryant [mailto:stbryant@cisco.com] <br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> Tuesday, June 05, =
2007 16:19<br>
<b><span style=3D'font-weight:bold'>To:</span></b> Danny McPherson<br>
<b><span style=3D'font-weight:bold'>Cc:</span></b> pwe3 WG =
((((((((E-mail))))))))<br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> Re: [PWE3] WG
LC:draft-ietf-pwe3-pw-tc-mib-10.txt</span></font><o:p></o:p></p>

</div>

<p class=3DMsoNormal dir=3DLTR><font size=3D3 face=3D"Times New =
Roman"><span
style=3D'font-size:12.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal dir=3DLTR style=3D'margin-bottom:12.0pt'><font =
size=3D3
face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p dir=3DLTR><font size=3D2 face=3D"Times New Roman"><span =
style=3D'font-size:10.0pt'>A
few comments:<br>
<br>
<br>
The current version is -11<br>
<br>
=3D=3D=3D=3D=3D=3D<br>
<br>
There are instances of the term &quot;pseudo wire&quot; and
&quot;pseudo-wire&quot; when we agreed a little while ago to use the =
term
pseudowire.<br>
<br>
=3D=3D=3D=3D=3D=3D<br>
<br>
DESCRIPTION<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&quot;Pseudo-Wire
Identifier. Used to identify the PW<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
(together
with some other fields) in the signaling<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
session.&quot;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; SYNTAX&nbsp; Unsigned32<br>
<br>
Shouldn't this be a 1..2^32-1 (control spec says non-zero)<br>
<br>
=3D=3D=3D=3D=3D=3D=3D=3D<br>
<br>
I am suprised that the PwOperStatusTC ::=3D TEXTUAL-CONVENTION states do =
not have
a one to one mapping with Pseudo Wire Status Codes Registry at least to =
the
point of having the registry name in the text.<br>
<br>
<br>
- Stewart<br>
<br>
Danny McPherson wrote:<br>
&gt; Folks,<br>
&gt; Please consider today the start of a two week WG LC for<br>
&gt; this document.&nbsp; The call for comments from the WG will end<br>
&gt; on 6/19.&nbsp; Please provide feedback to the mailing list or<br>
&gt; authors ASAP.<br>
&gt;<br>
&gt; Thanks!<br>
&gt;<br>
&gt; -danny<br>
&gt;<br>
&gt;<br>
&gt; Begin forwarded message:<br>
&gt;<br>
&gt;&gt; From: Internet-Drafts@ietf.org<br>
&gt;&gt; Date: February 8, 2007 4:50:02 PM MST<br>
&gt;&gt; To: i-d-announce@ietf.org<br>
&gt;&gt; Cc: pwe3@ietf.org<br>
&gt;&gt; Subject: [PWE3] I-D ACTION:draft-ietf-pwe3-pw-tc-mib-10.txt<br>
&gt;&gt;<br>
&gt;&gt; A New Internet-Draft is available from the on-line =
Internet-Drafts<br>
&gt;&gt; directories.<br>
&gt;&gt; This draft is a work item of the Pseudowire Emulation Edge to =
Edge<br>
&gt;&gt; Working Group of the IETF.<br>
&gt;&gt;<br>
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;
Title&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; : Definitions for =
Textual
Conventions and for<br>
&gt;&gt; Managing Pseudo-Wires over PSN<br>
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp; Author(s)&nbsp;&nbsp;&nbsp; : T. =
Nadeau, et
al.<br>
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp; Filename&nbsp;&nbsp;&nbsp; :
draft-ietf-pwe3-pw-tc-mib-10.txt<br>
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp; =
Pages&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
: 11<br>
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp; =
Date&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
: 2007-2-8<br>
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;<br>
&gt;&gt; This memo defines a Management Information Base (MIB) module =
which<br>
&gt;&gt;&nbsp;&nbsp;&nbsp; contains Textual Conventions (TCs) to =
represent
commonly-used Pseudo<br>
&gt;&gt;&nbsp;&nbsp;&nbsp; Wire (PW) management information.&nbsp; The =
intent
is that these TCs will<br>
&gt;&gt;&nbsp;&nbsp;&nbsp; be imported and used in PW-related MIB =
modules that
would otherwise<br>
&gt;&gt;&nbsp;&nbsp;&nbsp; define their own representations.<br>
&gt;&gt;<br>
&gt;&gt; A URL for this Internet-Draft is:<br>
&gt;&gt; <a
href=3D"http://www.ietf.org/internet-drafts/draft-ietf-pwe3-pw-tc-mib-10.=
txt">http://www.ietf.org/internet-drafts/draft-ietf-pwe3-pw-tc-mib-10.txt=
</a><br>
&gt;&gt;<br>
&gt;&gt; To remove yourself from the I-D Announcement list, send a =
message to<br>
&gt;&gt; i-d-announce-request@ietf.org with the word unsubscribe in the =
body of<br>
&gt;&gt; the message.<br>
&gt;&gt; You can also visit <a
href=3D"https://www1.ietf.org/mailman/listinfo/I-D-announce">https://www1=
.ietf.org/mailman/listinfo/I-D-announce</a><br>
&gt;&gt; to change your subscription settings.<br>
&gt;&gt;<br>
&gt;&gt; Internet-Drafts are also available by anonymous FTP. Login with =
the<br>
&gt;&gt; username &quot;anonymous&quot; and a password of your e-mail =
address.
After<br>
&gt;&gt; logging in, type &quot;cd internet-drafts&quot; and then<br>
&gt;&gt; &quot;get draft-ietf-pwe3-pw-tc-mib-10.txt&quot;.<br>
&gt;&gt;<br>
&gt;&gt; A list of Internet-Drafts directories can be found in<br>
&gt;&gt; <a =
href=3D"http://www.ietf.org/shadow.html">http://www.ietf.org/shadow.html<=
/a><br>
&gt;&gt; or <a =
href=3D"ftp://ftp.ietf.org/ietf/1shadow-sites.txt">ftp://ftp.ietf.org/iet=
f/1shadow-sites.txt</a><br>
&gt;&gt;<br>
&gt;&gt; Internet-Drafts can also be obtained by e-mail.<br>
&gt;&gt;<br>
&gt;&gt; Send a message to:<br>
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp; mailserv@ietf.org.<br>
&gt;&gt; In the body type:<br>
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp; &quot;FILE
/internet-drafts/draft-ietf-pwe3-pw-tc-mib-10.txt&quot;.<br>
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;<br>
&gt;&gt; NOTE:&nbsp;&nbsp;&nbsp; The mail server at ietf.org can return =
the
document in<br>
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp; MIME-encoded form by using the
&quot;mpack&quot; utility.&nbsp; To use this<br>
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp; feature, insert the command =
&quot;ENCODING
mime&quot; before the &quot;FILE&quot;<br>
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp; command.&nbsp; To decode the =
response(s), you
will need &quot;munpack&quot; or<br>
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp; a MIME-compliant mail reader.&nbsp; =
Different
MIME-compliant mail readers<br>
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp; exhibit different behavior, especially =
when
dealing with<br>
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp; &quot;multipart&quot; MIME messages =
(i.e.
documents which have been split<br>
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp; up into multiple messages), so check =
your
local documentation on<br>
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp; how to manipulate these messages.<br>
&gt;&gt;<br>
&gt;&gt; Below is the data which will enable a MIME compliant mail =
reader<br>
&gt;&gt; implementation to automatically retrieve the ASCII version of =
the<br>
&gt;&gt; Internet-Draft.<br>
&gt;&gt; Content-Type: text/plain<br>
&gt;&gt; Content-ID: &lt;2007-2-8161613.I-D@ietf.org&gt;<br>
&gt;&gt;<br>
&gt;&gt; _______________________________________________<br>
&gt;&gt; pwe3 mailing list<br>
&gt;&gt; pwe3@ietf.org<br>
&gt;&gt; <a =
href=3D"https://www1.ietf.org/mailman/listinfo/pwe3">https://www1.ietf.or=
g/mailman/listinfo/pwe3</a><br>
&gt;<br>
&gt;<br>
&gt; _______________________________________________<br>
&gt; pwe3 mailing list<br>
&gt; pwe3@ietf.org<br>
&gt; <a =
href=3D"https://www1.ietf.org/mailman/listinfo/pwe3">https://www1.ietf.or=
g/mailman/listinfo/pwe3</a><br>
&gt;<br>
<br>
_______________________________________________<br>
pwe3 mailing list<br>
pwe3@ietf.org<br>
<a =
href=3D"https://www1.ietf.org/mailman/listinfo/pwe3">https://www1.ietf.or=
g/mailman/listinfo/pwe3</a></span></font><o:p></o:p></p>

</div>

</div>

</body>

</html>

------=_NextPart_000_001C_01C7AA86.ECD01D30--




--===============0806493268==
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

--===============0806493268==--






From pwe3-bounces@ietf.org Fri Jun 15 08:48:14 2007
Return-path: <pwe3-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HzBDe-0000iU-8X; Fri, 15 Jun 2007 08:48:02 -0400
Received: from pwe3 by megatron.ietf.org with local (Exim 4.43)
	id 1HzBDd-0000iP-OK
	for pwe3-confirm+ok@megatron.ietf.org; Fri, 15 Jun 2007 08:48:01 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HzBDd-0000iG-Ek
	for pwe3@ietf.org; Fri, 15 Jun 2007 08:48:01 -0400
Received: from smail.alcatel.fr ([62.23.212.165])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HzBDc-0000mm-1u
	for pwe3@ietf.org; Fri, 15 Jun 2007 08:48:01 -0400
Received: from gbmail02.netfr.alcatel.fr (gbmail02.netfr.alcatel.fr
	[155.132.251.26])
	by smail.alcatel.fr (8.13.4/8.13.4/ICT) with ESMTP id l5FCm2lL020485
	for <pwe3@ietf.org>; Fri, 15 Jun 2007 14:48:02 +0200
To: pwe3@ietf.org
X-Mailer: Lotus Notes Release 6.5 September 26, 2003
Message-ID: <OF0B9C072E.9181A48C-ON802572FB.0045344C-802572FB.0045D32B@netfr.alcatel.fr>
From: Matthew.Bocci@alcatel-lucent.co.uk
Date: Fri, 15 Jun 2007 13:42:40 +0100
X-MIMETrack: Serialize by Router on GBMAIL02/GB/ALCATEL(Release 5.0.13aHF163 |
	June 23, 2005) at 06/15/2007 13:47:57
MIME-Version: 1.0
Content-type: text/plain; charset=us-ascii
X-Scanned-By: MIMEDefang 2.51 on 155.132.180.81
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 79899194edc4f33a41f49410777972f8
Subject: [PWE3] Call for Slots in Chicago
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>
Errors-To: pwe3-bounces@ietf.org

We have a 2 hour session for PWE3 on Monday, July 23rd at 1pm.

Please can you let me know, by Friday 10th July, if you would like a slot.
As usual, please let me know the relevant draft  (if any), a summary of
what you want to talk about, and  the time you require.

Best regards,

Matthew


-----------------------------------------
Matthew Bocci
IP Division,
Alcatel-Lucent Telecom Limited,
Registered Office: Christchurch Way, Greenwich, London SE10 0AG.
Registered in England & Wales number 02650571
-----------------------------------------




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



From pwe3-bounces@ietf.org Fri Jun 15 09:47:40 2007
Return-path: <pwe3-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HzC9G-0004Vw-Ue; Fri, 15 Jun 2007 09:47:34 -0400
Received: from pwe3 by megatron.ietf.org with local (Exim 4.43)
	id 1HzC9F-0004Vq-E1
	for pwe3-confirm+ok@megatron.ietf.org; Fri, 15 Jun 2007 09:47:33 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HzC9F-0004Vf-4N
	for pwe3@ietf.org; Fri, 15 Jun 2007 09:47:33 -0400
Received: from sj-iport-5.cisco.com ([171.68.10.87])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HzC9B-00089s-GR
	for pwe3@ietf.org; Fri, 15 Jun 2007 09:47:33 -0400
Received: from sj-dkim-2.cisco.com ([171.71.179.186])
	by sj-iport-5.cisco.com with ESMTP; 15 Jun 2007 06:47:29 -0700
X-IronPort-AV: i="4.16,425,1175497200"; 
	d="scan'208"; a="162761761:sNHT63793656"
Received: from sj-core-5.cisco.com (sj-core-5.cisco.com [171.71.177.238])
	by sj-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id l5FDlSON016895
	for <pwe3@ietf.org>; Fri, 15 Jun 2007 06:47:28 -0700
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com
	[64.102.31.12])
	by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id l5FDlKtj009540
	for <pwe3@ietf.org>; Fri, 15 Jun 2007 13:47:28 GMT
Received: from xfe-rtp-202.amer.cisco.com ([64.102.31.21]) by
	xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 15 Jun 2007 09:47:28 -0400
Received: from [10.83.15.50] ([10.83.15.50]) by xfe-rtp-202.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 15 Jun 2007 09:47:28 -0400
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Transfer-Encoding: quoted-printable
Message-Id: <B380E070-7754-4C4C-B1F9-4A75DEE97B8B@cisco.com>
Content-Type: text/plain; charset=WINDOWS-1252; delsp=yes; format=flowed
To: "pwe3 WG ((((((((((((((((E-mail))))))))))))))))" <pwe3@ietf.org>
From: "Thomas D. Nadeau" <tnadeau@cisco.com>
Date: Fri, 15 Jun 2007 09:47:27 -0400
X-Mailer: Apple Mail (2.752.3)
X-OriginalArrivalTime: 15 Jun 2007 13:47:28.0104 (UTC)
	FILETIME=[B66C3680:01C7AF53]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=7430; t=1181915248;
	x=1182779248; c=relaxed/simple; s=sjdkim2002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=tnadeau@cisco.com;
	z=From:=20=22Thomas=20D.=20Nadeau=22=20<tnadeau@cisco.com>
	|Subject:=20=3D?WINDOWS-1252?Q?IEEE_ComMag_Feature_Topic_on_=22Next-Gener
	ation_C?=3D=0A=20=3D?WINDOWS-1252?Q?arrier_Ethernet_Transport_Technologies
	=3D94?=3D |Sender:=20;
	bh=PfocYZjhsK2e+1+hsu8ND/Sf76J4a5Gxbyw2DG6tTMo=;
	b=FIm80Sj7qTzHQRXG3eQ0WfL7HSKVjc2lk1Auuk8mjRWPbMGHBuXAYTPAPzRSdBBiLLEsDJdf
	mSGF88HMZRNWSd8nQCf+5R9uLB8WgQZSw0cANQUmjNiXEUfp410kFAtD;
Authentication-Results: sj-dkim-2; header.From=tnadeau@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim2002 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d2b46e3b2dfbff2088e0b72a54104985
Subject: [PWE3] =?windows-1252?q?IEEE_ComMag_Feature_Topic_on_=22Next-Gen?=
 =?windows-1252?q?eration_Carrier_Ethernet_Transport_Technologies=94?=
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>
Errors-To: pwe3-bounces@ietf.org


                                    CALL FOR PAPERS
                             ------------------------------

IEEE Communications Magazine Feature Topic on
"Next-Generation Carrier Ethernet Transport Technologies=94

Over the last few years, the share of packet-dominated traffic has =20
grown exponentially in networks worldwide. As a result packet-based =20
transport technologies such as MPLS are increasingly deemed to be =20
more efficient for carrying this traffic compared to legacy SDH/SONET =20=

technology (and its next-generation incarnations) or the more =20
familiar ATM/FR technology. A majority of this traffic is now either =20
Ethernet or Internet Protocol (IP), so enterprises (and even =20
residential customers) familiar with Ethernet technology have begun =20
demanding a simple, inexpensive and high-speed universal Ethernet =20
service. With the availability of low-cost, high-bandwidth Ethernet =20
beyond the Local Area Network, the Metro Ethernet Forum (MEF) has =20
defined such a service as Carrier Ethernet, and defined it as a =20
ubiquitous, standardized, carrier-class service/application =20
characterized by some key attributes: reliability, hard Quality-of-=20
Service (QoS), service management, and scalability.

These features set it apart from the ubiquitously deployed LAN-based =20
Ethernet and serve as an add-on to switched Ethernet (GigE, and =20
10GigE variants). There are, however, several options for building =20
the underlying transport infrastructure to deliver such a carrier =20
Ethernet service. These include, for example, using: IP/MPLS =20
technology to deliver point-to-point Ethernet circuits joined =20
together with physical Ethernet bridges/switches; IP/MPLS with =20
Virtual-Private LAN Service (VPLS) or Hierarchical Virtual Private =20
LAN Service (H-VPLS) (developed at the IETF); Transport-MPLS (T-MPLS) =20=

being proposed at the ITU-T, using modified Ethernet technology with =20
Provider Backbone Bridging (PBB) and Provider-Backbone Transport =20
(PBT) being proposed at the IEEE; using a combination of a modified =20
Ethernet data-plane and a GMPLS-based control-plane with VLAN cross-=20
connect (being proposed by several vendors and under consideration at =20=

the IETF) and Circuit Emulation Services (CES) over an Ethernet =20
fabric to provision Pseudo Wires (PWs).

The quest, therefore, is for the most feature rich, and CAPEX/OPEX =20
efficient, packet-based transport infrastructure for next-generation =20
Carrier Ethernet services. Debate and discussion is rife in the =20
industry and the academic/research communities about which technology =20=

will provide the best combination of cost, ease of use, OAM features, =20=

performance and service management, ability to offer Quality-of-=20
Service (QoS) guarantees, traffic engineering, and resilience, and =20
capability to manage and bill for services running atop the transport =20=

infrastructure.

This special issue aims to consolidate and disseminate the latest =20
developments and advances in transport technology options for Carrier =20=

Ethernet service. With this objective, the list of topics includes =20
(but will not be limited to) the following:

=95           Metro Ethernet and Carrier Ethernet evolutions =96 =20
requirements, services specifications, carrier drivers, customer drivers
=95           Requirements on QoS, traffic engineering, resilience, =20
manageability, OAM, and service scalability for carrier Ethernet =20
transport technologies
=95           IP/MPLS (VPLS, H-VPLS) for carrier Ethernet services =96 =20=

choices, pros, cons, costs/benefits
=95           Provider Backbone Bridging (PBB) and Provider Backbone =20
Transport-Traffic Engineered (PBT-TE) as alternatives to IP/MPLS for =20
Ethernet transport =96 pros, cons, costs/benefits
=95           Transport-MPLS for carrier Ethernet =96 pros, cons, costs/=20=

benefits
=95           GMPLS-based control of Ethernet networks =96 changes in =
the =20
data and control planes
=95           Assessment of the proposed transport solutions in terms =20=

of their ability to provide QoS, traffic engineering, resilience, =20
manageability, and so on.
=95           OAM, network management, service management =96 options, =20=

choices, pitfalls, needs, and cost analysis and comparison of solutions.
=95           Solutions that meet the perceived requirements of the =20
community that are alternatives to the ones being proposed in the =20
various standards bodies.
=95           Traffic engineering and dimensioning of carrier Ethernet =20=

transport networks
=95           Techniques to ensure QoS, especially with a mix of =20
transport technologies in use
=95           Analysis and studies of resilience and protection =20
approaches utilized by different transport architectures and =20
associated technologies
=95           Studies comparing the different transport technologies =20
along multiple dimensions =96 deployment cost, day-to-day running cost, =20=

features provided, ease of deployment/management, and so on
=95           Comparisons and case-studies from the provider community =20=

to highlight why existing technologies do not meet current and =20
evolving provider requirements.
=95           Commentaries from providers who feel existing techniques/=20=

choices meet their requirements or can be easily modified to meet =20
their requirements.
=95           Network operators, vendors, and standards bodies=92 =20
perspectives on any of the above.
=95           Implementations, test-beds and field trials related to =20
carrier Ethernet transport technologies
=95           State of current standards

Submission

Articles should be tutorial in nature and should be written in a =20
style comprehensible to readers outside the specialty of the article. =20=

Articles may be edited for clarity and grammatical accuracy, and will =20=

be copyedited according to the Magazine's style. Mathematical =20
equations should not be used (in justified cases up to three simple =20
equations could be allowed, provided there is consent of the Guest =20
Editor; more than three equations require permission from the Editor-=20
in-Chief). Articles should have no more than 4,500 words, no more =20
than 6 tables/figures, and no more than 15 references. Guidelines for =20=

prospective authors can be found on-line at http://www.comsoc.org/=20
pubs/commag/sub_guidelines.html. Please submit no later than 31 July =20
2007. All articles to be considered for publication must be submitted =20=

through IEEE Manuscript Central (http://commag-=20
ieee.manuscriptcentral.com). Please select "March 2008/Next-=20
Generation Carrier Ethernet Transport Technologies" in the drop down =20
menu. Accepted papers will also be included in Communications =20
Interactive (CI), the online version of Communications Magazine.

Manuscript Due:                        1 August  2007
Acceptance Notification:             1 November 2007
Final Manuscript Due:                1 December 2007
Publication Date:                       March 2008


Guest Editors:
Thomas D. Nadeau, Cisco Systems, Inc., (tnadeau@cisco.com)
Vishal Sharma, Metanoia, Inc. (v.sharma@ieee.org)
Ashwin Gumaste, Indian Institute of Technology Bombay (ashwing@ieee.org)



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



From pwe3-bounces@ietf.org Sun Jun 17 19:04:00 2007
Return-path: <pwe3-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I03mh-0008IH-Rg; Sun, 17 Jun 2007 19:03:51 -0400
Received: from pwe3 by megatron.ietf.org with local (Exim 4.43)
	id 1I03mg-0008IC-1K
	for pwe3-confirm+ok@megatron.ietf.org; Sun, 17 Jun 2007 19:03:50 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I03mf-0008I4-O9
	for pwe3@ietf.org; Sun, 17 Jun 2007 19:03:49 -0400
Received: from gdh.nwtbb.com ([203.98.138.35])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I03me-0006zM-0P
	for pwe3@ietf.org; Sun, 17 Jun 2007 19:03:49 -0400
Received: from [210.245.225.60] (helo=[210.245.225.60])
	by gdh.nwtbb.com with esmtp (Exim 3.34 #1) id 1I03mZ-0007KJ-00
	for pwe3@ietf.org; Mon, 18 Jun 2007 07:03:43 +0800
Mime-Version: 1.0 (Apple Message framework v752.3)
References: <E1Hz2yg-000209-Bx@stiedprstage1.ietf.org>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <1DA07327-9D2A-451D-AB33-0B5E27A379E9@tcb.net>
Content-Transfer-Encoding: 7bit
From: Danny McPherson <danny@tcb.net>
Date: Sun, 17 Jun 2007 17:03:42 -0600
To: pwe3@ietf.org
X-Mailer: Apple Mail (2.752.3)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4d87d2aa806f79fed918a62e834505ca
Subject: [PWE3] Fwd: Internet-Drafts Submission Cutoff Dates for the 69th
	IETF Meeting in Chicago, IL, USA 
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>
Errors-To: pwe3-bounces@ietf.org



Begin forwarded message:

> From: ietf-secretariat@ietf.org
> Date: June 14, 2007 10:00:02 PM MDT
> To: ietf-announce@ietf.org
> Subject: Internet-Drafts Submission Cutoff Dates for the 69th IETF   
> Meeting in Chicago, IL, USA
>
>
> There are two (2) Internet-Draft cutoff dates for the 69th
> IETF Meeting in Chicago, IL, USA:
>
> July 2nd: Cutoff Date for Initial (i.e., version -00)
> Internet-Draft Submissions
>
> All initial Internet-Drafts (version -00) must be submitted by Monday,
> July 2nd at 9:00 AM ET. As always, all initial submissions with a
> filename beginning with "draft-ietf" must be approved by the
> appropriate WG Chair before they can be processed or announced.  The
> Secretariat would appreciate receiving WG Chair approval by Monday,
> June 25th at 9:00 AM ET.
>
> July 9th: Cutoff Date for Revised (i.e., version -01 and higher)
> Internet-Draft Submissions
>
> All revised Internet-Drafts (version -01 and higher) must be submitted
> by Monday, July 9th at 9:00 AM ET.
>
> Initial and revised Internet-Drafts received after their respective
> cutoff dates will not be made available in the Internet-Drafts
> directory or announced until on or after Monday, July 23rd at 9:00
> AM ET, when Internet-Draft posting resumes.  Please do not wait until
> the last minute to submit.
>
> Thank you for your understanding and cooperation. If you have any
> questions or concerns, then please send a message to
> internet-drafts@ietf.org.
>
> The IETF Secretariat
>
> FYI: The Internet-Draft cutoff dates as well as other significant  
> dates
> for the 69th IETF Meeting can be found at http://www.ietf.org/ 
> meetings/cutoff_dates_69.html.
>
> _______________________________________________
> IETF-Announce mailing list
> IETF-Announce@ietf.org
> https://www1.ietf.org/mailman/listinfo/ietf-announce



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



From pwe3-bounces@ietf.org Sun Jun 17 19:06:35 2007
Return-path: <pwe3-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I03pL-00039W-6P; Sun, 17 Jun 2007 19:06:35 -0400
Received: from pwe3 by megatron.ietf.org with local (Exim 4.43)
	id 1I03pK-00039R-DV
	for pwe3-confirm+ok@megatron.ietf.org; Sun, 17 Jun 2007 19:06:34 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I03pK-00039J-46
	for pwe3@ietf.org; Sun, 17 Jun 2007 19:06:34 -0400
Received: from gdh.nwtbb.com ([203.98.138.35])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I03pI-0007ad-EJ
	for pwe3@ietf.org; Sun, 17 Jun 2007 19:06:34 -0400
Received: from [210.245.225.60] (helo=[210.245.225.60])
	by gdh.nwtbb.com with esmtp (Exim 3.34 #1)
	id 1I03pG-0000LW-00; Mon, 18 Jun 2007 07:06:30 +0800
Mime-Version: 1.0 (Apple Message framework v752.3)
References: <467415E9.7010009@qualcomm.com>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <21F25C63-CA84-4483-8AD9-36B2CA8EB562@tcb.net>
Content-Transfer-Encoding: 7bit
From: Danny McPherson <danny@tcb.net>
Date: Sun, 17 Jun 2007 17:06:33 -0600
To: pwe3@ietf.org
X-Mailer: Apple Mail (2.752.3)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ea4ac80f790299f943f0a53be7e1a21a
Subject: [PWE3] Fwd: Request to forward the Nomcom 2007-8 Announcement to
	lists you manage
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>
Errors-To: pwe3-bounces@ietf.org


FYI..   Nomcom is a solid way to influence IETF and it's leadership, I
encourage you to volunteer if you've for the cycles.

https://datatracker.ietf.org/public/show_nomcom_message.cgi?id=1234

-danny

Begin forwarded message:

> From: Lakshminath Dondeti <ldondeti@qualcomm.com>
> Date: June 16, 2007 10:55:05 AM MDT
> To: wgchairs@ietf.org, irsg@isi.edu, bofchairs@ietf.org
> Subject: Request to forward the Nomcom 2007-8 Announcement to lists  
> you manage
>
> Folks,
>
> We have around 50 volunteers so far for Nomcom 2007-8 voting member  
> selection.  We need a lot more!  Not everyone subscribes to the  
> IETF-Announce list.  Could you please forward the announcement  
> https://datatracker.ietf.org/public/show_nomcom_message.cgi?id=1234  
> to WG, RG, BoF, Area lists that you manage?
>
> Thanks in advance.
>
> best regards,
> Lakshminath
>



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



From pwe3-bounces@ietf.org Wed Jun 20 22:16:19 2007
Return-path: <pwe3-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I1CDX-0002hr-OM; Wed, 20 Jun 2007 22:16:15 -0400
Received: from pwe3 by megatron.ietf.org with local (Exim 4.43)
	id 1I1CDV-0002dt-Ty
	for pwe3-confirm+ok@megatron.ietf.org; Wed, 20 Jun 2007 22:16:13 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I1CDV-0002di-I3
	for pwe3@ietf.org; Wed, 20 Jun 2007 22:16:13 -0400
Received: from [61.233.3.220] (helo=mail.ruijie.com.cn)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I1CDT-0001Rq-Nt
	for pwe3@ietf.org; Wed, 20 Jun 2007 22:16:13 -0400
To: lmartini@cisco.com, nna@level3.net, giles.heron@tellabs.com,
	erosen@cisco.com, tob@netapp.com
MIME-Version: 1.0
X-Mailer: Lotus Notes Release 7.0.1 January 17, 2006
From: chenxb@ruijie.com.cn
Message-ID: <OFB2643948.F43A6682-ON88257301.005F038C-88257301.005F17E2@ruijie.com.cn>
Date: Wed, 20 Jun 2007 19:13:41 -0700
X-MIMETrack: Serialize by Router on mailserver/ruijie(Release 6.5.4FP3|January
	09, 2006) at 2007-06-21 10:13:44,
	Serialize complete at 2007-06-21 10:13:44
X-Spam-Score: 0.3 (/)
X-Scan-Signature: 244a2fd369eaf00ce6820a760a3de2e8
Cc: pwe3@ietf.org
Subject: [PWE3] [MPLS] One question about LDP in RFC4447
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="===============0279975940=="
Errors-To: pwe3-bounces@ietf.org

This is a multipart message in MIME format.
--===============0279975940==
Content-Type: multipart/alternative;
	boundary="=_alternative 005F140588257301_="

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

Hi all,
I have one question about LDP in RFC4447. 
Section 5 in RFC4447 say:
    The PW label bindings are distributed using the LDP downstream
    unsolicited mode described in [RFC3036].  The PEs will establish an
    LDP session using the Extended Discovery mechanism described in [LDP,
    sections 2.4.2 and 2.5].

My question is , 
if two PE is directly connected, can LDP session be established using the
 Basic Discovery mechanism described in [LDP RFC3036, section 2.4.1] ?

I consider that in this case  the session using the Extended Discovery 
mechanism is maybe the same session with using the Basic Discovery 
mechanism.



Thanks and Regards
   jerry king



--=_alternative 005F140588257301_=
Content-Type: text/html; charset="US-ASCII"


<br>
<br>
<br><font size=2 face="sans-serif">Hi all,</font>
<br><font size=2 face="sans-serif">I have one question about LDP in RFC4447.
</font>
<br><font size=2 face="sans-serif">Section 5 in RFC4447 say:</font>
<br><font size=2 face="sans-serif">&nbsp; &nbsp; The PW label bindings
are distributed using the LDP downstream</font>
<br><font size=2 face="sans-serif">&nbsp; &nbsp; unsolicited mode described
in [RFC3036]. &nbsp;The PEs will establish an</font>
<br><font size=2 face="sans-serif">&nbsp; &nbsp; LDP session using the
Extended Discovery mechanism described in [LDP,</font>
<br><font size=2 face="sans-serif">&nbsp; &nbsp; sections 2.4.2 and 2.5].<br>
</font>
<br><font size=2 face="sans-serif">My question is , </font>
<br><font size=2 face="sans-serif">if two PE is directly connected, can
LDP session be established using the</font>
<br><font size=2 face="sans-serif">&nbsp;Basic Discovery mechanism described
in [LDP RFC3036, section 2.4.1] ?</font>
<br>
<br><font size=2 face="sans-serif">I consider that in this case &nbsp;the
session using the Extended Discovery </font>
<br><font size=2 face="sans-serif">mechanism is maybe the same session
with using the Basic Discovery mechanism.</font>
<br><font size=2 face="sans-serif"><br>
<br>
</font>
<br><tt><font size=2>Thanks and Regards</font></tt>
<br><font size=2 face="sans-serif">&nbsp; &nbsp;jerry king</font>
<br><font size=2 face="sans-serif"><br>
<br>
</font>
--=_alternative 005F140588257301_=--



--===============0279975940==
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

--===============0279975940==--





From pwe3-bounces@ietf.org Thu Jun 21 15:50:20 2007
Return-path: <pwe3-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I1SfZ-00049a-N4; Thu, 21 Jun 2007 15:50:18 -0400
Received: from pwe3 by megatron.ietf.org with local (Exim 4.43)
	id 1I1SfL-0003d2-JT
	for pwe3-confirm+ok@megatron.ietf.org; Thu, 21 Jun 2007 15:50:03 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I1SfL-0003cc-1U; Thu, 21 Jun 2007 15:50:03 -0400
Received: from ns0.neustar.com ([156.154.16.158])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1I1SfK-0001aA-JD; Thu, 21 Jun 2007 15:50:03 -0400
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10]) by ns0.neustar.com (Postfix) with ESMTP id 8BC6632934;
	Thu, 21 Jun 2007 19:50:02 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1I1SfK-0000tG-F5; Thu, 21 Jun 2007 15:50:02 -0400
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1I1SfK-0000tG-F5@stiedprstage1.ietf.org>
Date: Thu, 21 Jun 2007 15:50:02 -0400
X-Spam-Score: -2.5 (--)
X-Scan-Signature: c3a18ef96977fc9bcc21a621cbf1174b
Cc: pwe3@ietf.org
Subject: [PWE3] I-D ACTION:draft-ietf-pwe3-dynamic-ms-pw-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>
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 Pseudowire Emulation Edge to Edge Working Group of the IETF.

	Title		: Dynamic Placement of Multi Segment Pseudo Wires
	Author(s)	: F. Balus, et al.
	Filename	: draft-ietf-pwe3-dynamic-ms-pw-03.txt
	Pages		: 20
	Date		: 2007-6-21
	
There is a requirement for service providers to be able to extend the
   reach of pseudo wires (PW) across multiple Packet Switched Network
   domains. A Multi-Segment PW is defined as a set of two or more
   contiguous PW segments that behave and function as a single point-
   to-point PW. This document describes extensions to the PW control
   protocol to dynamically place the segments of the multi segment
   pseudo wire among a set of Provider Edge (PE) routers.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-pwe3-dynamic-ms-pw-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-dynamic-ms-pw-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-dynamic-ms-pw-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: <2007-6-21125717.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-pwe3-dynamic-ms-pw-03.txt

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

Content-Type: text/plain
Content-ID: <2007-6-21125717.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 Fri Jun 22 20:17:26 2007
Return-path: <pwe3-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I1tJQ-0006IK-F8; Fri, 22 Jun 2007 20:17:12 -0400
Received: from pwe3 by megatron.ietf.org with local (Exim 4.43)
	id 1I1tJO-0006IF-NF
	for pwe3-confirm+ok@megatron.ietf.org; Fri, 22 Jun 2007 20:17:10 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I1tJO-0006I7-Dn
	for pwe3@ietf.org; Fri, 22 Jun 2007 20:17:10 -0400
Received: from py-out-1112.google.com ([64.233.166.181])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I1tJM-0008Ey-TU
	for pwe3@ietf.org; Fri, 22 Jun 2007 20:17:10 -0400
Received: by py-out-1112.google.com with SMTP id f31so1674272pyh
	for <pwe3@ietf.org>; Fri, 22 Jun 2007 17:17:08 -0700 (PDT)
Received: by 10.64.183.6 with SMTP id g6mr6572458qbf.1182557828322;
	Fri, 22 Jun 2007 17:17:08 -0700 (PDT)
Received: from ?166.217.159.230? ( [166.217.159.230])
	by mx.google.com with ESMTP id q17sm3371960qbq.2007.06.22.17.17.04
	(version=TLSv1/SSLv3 cipher=RC4-MD5);
	Fri, 22 Jun 2007 17:17:06 -0700 (PDT)
Message-ID: <467C6633.3070708@pingpan.org>
Date: Fri, 22 Jun 2007 17:15:47 -0700
From: Ping Pan <pingpan@pingpan.org>
User-Agent: Thunderbird 2.0.0.4 (Windows/20070604)
MIME-Version: 1.0
To: pwe3 <pwe3@ietf.org>, ccamp-list <ccamp@ops.ietf.org>
Content-Type: multipart/mixed; boundary="------------020906040204010404030608"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 995b2e24d23b953c94bac5288c432399
Cc: 
Subject: [PWE3] [Fwd: I-D ACTION:draft-pan-pwe3-pbb-tunnels-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>
Errors-To: pwe3-bounces@ietf.org

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

Hi,

There has been much discussion on PBB/PBT vs. MPLS etc. Let's not go 
down that path here. ;-)

Here is a proposal that we think it solves a practical problem, and 
takes the advantage of PBB and MPLS/PWE3.

Please provide comment.

Thanks!

- Ping and others

--------------020906040204010404030608
Content-Type: message/rfc822;
	name="I-D ACTION:draft-pan-pwe3-pbb-tunnels-00.txt.eml"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline;
	filename="I-D ACTION:draft-pan-pwe3-pbb-tunnels-00.txt.eml"

X-Account-Key: account5
X-Mozilla-Keys: 
Delivered-To: pingpan@pingpan.org
Received: by 10.78.57.2 with SMTP id f2cs30698hua;
	Fri, 22 Jun 2007 12:57:03 -0700 (PDT)
Received: by 10.70.29.7 with SMTP id c7mr5340120wxc.1182542222904;
	Fri, 22 Jun 2007 12:57:02 -0700 (PDT)
Return-Path: <i-d-announce-bounces@ietf.org>
Received: from megatron.ietf.org (odin.ietf.ORG [156.154.16.145])
	by mx.google.com with ESMTP id h36si5187451wxd.2007.06.22.12.57.02;
	Fri, 22 Jun 2007 12:57:02 -0700 (PDT)
Received-SPF: pass (google.com: best guess record for domain of
	i-d-announce-bounces@ietf.org designates 156.154.16.145 as
	permitted sender)
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I1p96-0005xb-SY; Fri, 22 Jun 2007 15:50:16 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I1p8s-0005pa-TN
	for i-d-announce@ietf.org; Fri, 22 Jun 2007 15:50:02 -0400
Received: from ns1.neustar.com ([2001:503:c779:1a::9c9a:108a])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I1p8s-0000E2-7i
	for i-d-announce@ietf.org; Fri, 22 Jun 2007 15:50:02 -0400
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10]) by ns1.neustar.com (Postfix) with ESMTP id 15C1C26EAC
	for <i-d-announce@ietf.org>; Fri, 22 Jun 2007 19:50:02 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1I1p8r-0008R7-TT
	for i-d-announce@ietf.org; Fri, 22 Jun 2007 15:50:01 -0400
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
Cc: 
From: Internet-Drafts@ietf.org
Message-Id: <E1I1p8r-0008R7-TT@stiedprstage1.ietf.org>
Date: Fri, 22 Jun 2007 15:50:01 -0400
X-Spam-Score: -2.5 (--)
X-Scan-Signature: b7b9551d71acde901886cc48bfc088a6
Subject: I-D ACTION:draft-pan-pwe3-pbb-tunnels-00.txt 
X-BeenThere: i-d-announce@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: internet-drafts@ietf.org
List-Id: i-d-announce.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/i-d-announce>,
	<mailto:i-d-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/i-d-announce>
List-Post: <mailto:i-d-announce@ietf.org>
List-Help: <mailto:i-d-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/i-d-announce>,
	<mailto:i-d-announce-request@ietf.org?subject=subscribe>
Errors-To: i-d-announce-bounces@ietf.org

--NextPart

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


	Title		: Setup and Manage PBB-based Tunnels with PWE3 Mechanism 
	Author(s)	: P. Pan, et al.
	Filename	: draft-pan-pwe3-pbb-tunnels-00.txt
	Pages		: 11
	Date		: 2007-6-22
	
   This document describes a mechanism that enables providers to setup 
   point-to-point tunnels over PBB networks for the purpose of 
   aggregating customer flows. The interior network nodes will not be 
   disturbed with this mechanism. 


A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-pan-pwe3-pbb-tunnels-00.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-pan-pwe3-pbb-tunnels-00.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-pan-pwe3-pbb-tunnels-00.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: <2007-6-22124907.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-pan-pwe3-pbb-tunnels-00.txt

--OtherAccess
Content-Type: Message/External-body; name="draft-pan-pwe3-pbb-tunnels-00.txt"; 
	site="ftp.ietf.org"; access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2007-6-22124907.I-D@ietf.org>


--OtherAccess--

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

_______________________________________________
I-D-Announce mailing list
I-D-Announce@ietf.org
https://www1.ietf.org/mailman/listinfo/i-d-announce

--NextPart--



--------------020906040204010404030608
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

--------------020906040204010404030608--





From pwe3-bounces@ietf.org Sun Jun 24 15:27:56 2007
Return-path: <pwe3-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I2XkQ-00078H-AY; Sun, 24 Jun 2007 15:27:46 -0400
Received: from pwe3 by megatron.ietf.org with local (Exim 4.43)
	id 1I2XkO-00078C-QX
	for pwe3-confirm+ok@megatron.ietf.org; Sun, 24 Jun 2007 15:27:44 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I2XkO-000784-H6
	for pwe3@ietf.org; Sun, 24 Jun 2007 15:27:44 -0400
Received: from mu-out-0910.google.com ([209.85.134.184])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I2XkL-0001uX-Pt
	for pwe3@ietf.org; Sun, 24 Jun 2007 15:27:44 -0400
Received: by mu-out-0910.google.com with SMTP id w8so1423730mue
	for <pwe3@ietf.org>; Sun, 24 Jun 2007 12:27:40 -0700 (PDT)
Received: by 10.82.156.12 with SMTP id d12mr11115663bue.1182713259859;
	Sun, 24 Jun 2007 12:27:39 -0700 (PDT)
Received: by 10.82.190.12 with HTTP; Sun, 24 Jun 2007 12:27:39 -0700 (PDT)
Message-ID: <fa5f3d8c0706241227v17c98d48v44fbff4c53237e04@mail.gmail.com>
Date: Sun, 24 Jun 2007 12:27:39 -0700
From: "ping pan" <pingpan@pingpan.org>
To: pwe3 <pwe3@ietf.org>, ccamp-list <ccamp@ops.ietf.org>
In-Reply-To: <467C6633.3070708@pingpan.org>
MIME-Version: 1.0
References: <467C6633.3070708@pingpan.org>
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 287c806b254c6353fcb09ee0e53bbc5e
Cc: 
Subject: [PWE3] Re: [Fwd: I-D ACTION:draft-pan-pwe3-pbb-tunnels-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>
Content-Type: multipart/mixed; boundary="===============0964438572=="
Errors-To: pwe3-bounces@ietf.org

--===============0964438572==
Content-Type: multipart/alternative; 
	boundary="----=_Part_180664_551517.1182713259597"

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

On 6/22/07, Ping Pan <pingpan@pingpan.org> wrote:
>
> Hi,
>
> There has been much discussion on PBB/PBT vs. MPLS etc. Let's not go
> down that path here. ;-)
>
> Here is a proposal that we think it solves a practical problem, and
> takes the advantage of PBB and MPLS/PWE3.
>
> Please provide comment.
>
> Thanks!
>
> - Ping and others
>
> A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
>
>
>        Title           : Setup and Manage PBB-based Tunnels with PWE3
> Mechanism
>        Author(s)       : P. Pan, et al.
>        Filename        : draft-pan-pwe3-pbb-tunnels-00.txt
>        Pages           : 11
>        Date            : 2007-6-22
>
>   This document describes a mechanism that enables providers to setup
>   point-to-point tunnels over PBB networks for the purpose of
>   aggregating customer flows. The interior network nodes will not be
>   disturbed with this mechanism.
>
>
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-pan-pwe3-pbb-tunnels-00.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-pan-pwe3-pbb-tunnels-00.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-pan-pwe3-pbb-tunnels-00.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.
>
>
> _______________________________________________
> I-D-Announce mailing list
> I-D-Announce@ietf.org
> https://www1.ietf.org/mailman/listinfo/i-d-announce
>
>

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

<br>
<div><span class="gmail_quote">On 6/22/07, <b class="gmail_sendername">Ping Pan</b> &lt;<a href="mailto:pingpan@pingpan.org">pingpan@pingpan.org</a>&gt; wrote:</span>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">Hi,<br><br>There has been much discussion on PBB/PBT vs. MPLS etc. Let&#39;s not go<br>down that path here. ;-)
<br><br>Here is a proposal that we think it solves a practical problem, and<br>takes the advantage of PBB and MPLS/PWE3.<br><br>Please provide comment.<br><br>Thanks!<br><br>- Ping and others<br><br>A New Internet-Draft is available from the on-line Internet-Drafts
<br>directories.<br><br><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Title&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; : Setup and Manage PBB-based Tunnels with PWE3 Mechanism<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Author(s)&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; : P. Pan, et al.<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Filename&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;: draft-pan-pwe3-pbb-tunnels-00.txt<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Pages&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; : 11
<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Date&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;: 2007-6-22<br><br>&nbsp;&nbsp;This document describes a mechanism that enables providers to setup<br>&nbsp;&nbsp;point-to-point tunnels over PBB networks for the purpose of<br>&nbsp;&nbsp;aggregating customer flows. The interior network nodes will not be
<br>&nbsp;&nbsp;disturbed with this mechanism.<br><br><br>A URL for this Internet-Draft is:<br><a href="http://www.ietf.org/internet-drafts/draft-pan-pwe3-pbb-tunnels-00.txt">http://www.ietf.org/internet-drafts/draft-pan-pwe3-pbb-tunnels-00.txt
</a><br><br>To remove yourself from the I-D Announcement list, send a message to<br><a href="mailto:i-d-announce-request@ietf.org">i-d-announce-request@ietf.org</a> with the word unsubscribe in the body of<br>the message.
<br>You can also visit <a href="https://www1.ietf.org/mailman/listinfo/I-D-announce">https://www1.ietf.org/mailman/listinfo/I-D-announce</a><br>to change your subscription settings.<br><br>Internet-Drafts are also available by anonymous FTP. Login with the
<br>username &quot;anonymous&quot; and a password of your e-mail address. After<br>logging in, type &quot;cd internet-drafts&quot; and then<br>&quot;get draft-pan-pwe3-pbb-tunnels-00.txt&quot;.<br><br>A list of Internet-Drafts directories can be found in
<br><a href="http://www.ietf.org/shadow.html">http://www.ietf.org/shadow.html</a><br>or <a href="ftp://ftp.ietf.org/ietf/1shadow-sites.txt">ftp://ftp.ietf.org/ietf/1shadow-sites.txt</a><br><br>Internet-Drafts can also be obtained by e-mail.
<br><br>Send a message to:<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <a href="mailto:mailserv@ietf.org">mailserv@ietf.org</a>.<br>In the body type:<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &quot;FILE /internet-drafts/draft-pan-pwe3-pbb-tunnels-00.txt&quot;.<br><br>NOTE:&nbsp;&nbsp; The mail server at 
<a href="http://ietf.org">ietf.org</a> can return the document in<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; MIME-encoded form by using the &quot;mpack&quot; utility.&nbsp;&nbsp;To use this<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; feature, insert the command &quot;ENCODING mime&quot; before the &quot;FILE&quot;
<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; command.&nbsp;&nbsp;To decode the response(s), you will need &quot;munpack&quot; or<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; a MIME-compliant mail reader.&nbsp;&nbsp;Different MIME-compliant mail readers<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; exhibit different behavior, especially when dealing with
<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &quot;multipart&quot; MIME messages (i.e. documents which have been split<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; up into multiple messages), so check your local documentation on<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; how to manipulate these messages.<br><br>Below is the data which will enable a MIME compliant mail reader
<br>implementation to automatically retrieve the ASCII version of the<br>Internet-Draft.<br><br><br>_______________________________________________<br>I-D-Announce mailing list<br><a href="mailto:I-D-Announce@ietf.org">I-D-Announce@ietf.org
</a><br><a href="https://www1.ietf.org/mailman/listinfo/i-d-announce">https://www1.ietf.org/mailman/listinfo/i-d-announce</a><br><br></blockquote></div><br>

------=_Part_180664_551517.1182713259597--



--===============0964438572==
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

--===============0964438572==--





From pwe3-bounces@ietf.org Tue Jun 26 13:53:33 2007
Return-path: <pwe3-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I3FEI-0004gO-Ge; Tue, 26 Jun 2007 13:53:30 -0400
Received: from pwe3 by megatron.ietf.org with local (Exim 4.43)
	id 1I3BU8-00084R-Tl
	for pwe3-confirm+ok@megatron.ietf.org; Tue, 26 Jun 2007 09:53:36 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I3BU8-00084A-JF; Tue, 26 Jun 2007 09:53:36 -0400
Received: from ns3.neustar.com ([156.154.24.138])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1I3BU8-0005EI-E1; Tue, 26 Jun 2007 09:53:36 -0400
Received: from ietf.org (stiedprweb1.va.neustar.com [10.91.34.42])
	by ns3.neustar.com (Postfix) with ESMTP id 2B2EC175E4;
	Tue, 26 Jun 2007 13:53:06 +0000 (GMT)
Received: from mirror by ietf.org with local (Exim 4.43)
	id 1I3BTd-0001w7-Ov; Tue, 26 Jun 2007 09:53:05 -0400
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0
To: danny@arbor.net, stbryant@cisco.com, swallow@cisco.com, loa@pi.se
From: Greg Jones (ITU-T SG 15) <tsbsg15@itu.int>
Message-Id: <E1I3BTd-0001w7-Ov@ietf.org>
Date: Tue, 26 Jun 2007 09:53:05 -0400
X-Spam-Score: 0.6 (/)
X-Scan-Signature: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3
X-Mailman-Approved-At: Tue, 26 Jun 2007 13:53:30 -0400
Cc: mpls@lists.ietf.org, greg.jones@itu.int, sob@harvard.edu,
	yoichi.maeda@ntt-at.co.jp, pwe3@ietf.org, dward@cisco.com,
	tsbsg15@itu.int, townsley@cisco.com, betts01@nortel.com
Subject: [PWE3] New Liaison Statement, "G.8110.1 amendment 1" 
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: tsbsg15@itu.int
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>
Errors-To: pwe3-bounces@ietf.org


Title: G.8110.1 amendment 1
Submission Date: 2007-06-26
URL of the IETF Web page: https://datatracker.ietf.org/public/liaison_detail.cgi?detail_id=344 

From: Greg Jones(ITU-T SG 15) <tsbsg15@itu.int>
To: IETF PWE3 and MPLS WGs(danny@arbor.net,stbryant@cisco.com,swallow@cisco.com,loa@pi.se)
Cc: jari.arkko@piuha.net
townsley@cisco.com
pwe3@ietf.org
rcallon@juniper.net
dward@cisco.com
sob@harvard.edu
mpls@lists.ietf.org
sjtrowbridge@alcatel-lucent.com
yoichi.maeda@ntt-at.co.jp
greg.jones@itu.int
Reponse Contact: tsbsg15@itu.int
Technical Contact: betts01@nortel.com
Purpose: For information 
Body: 
Attachment(s):
     G.8110.1 amendment 1 - body text (https://datatracker.ietf.org/documents/LIAISON/file452.doc)





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



From pwe3-bounces@ietf.org Tue Jun 26 13:53:33 2007
Return-path: <pwe3-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I3FEI-0004gU-QJ; Tue, 26 Jun 2007 13:53:30 -0400
Received: from pwe3 by megatron.ietf.org with local (Exim 4.43)
	id 1I3BYB-0000g0-Se
	for pwe3-confirm+ok@megatron.ietf.org; Tue, 26 Jun 2007 09:57:47 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I3BYB-0000fE-IT; Tue, 26 Jun 2007 09:57:47 -0400
Received: from ns0.neustar.com ([156.154.16.158])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1I3BXp-0002j4-09; Tue, 26 Jun 2007 09:57:47 -0400
Received: from ietf.org (stiedprweb1.va.neustar.com [10.91.34.42])
	by ns0.neustar.com (Postfix) with ESMTP id CFA4F329F4;
	Tue, 26 Jun 2007 13:57:24 +0000 (GMT)
Received: from mirror by ietf.org with local (Exim 4.43)
	id 1I3BXo-0001zF-OG; Tue, 26 Jun 2007 09:57:24 -0400
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0
To: danny@arbor.net, stbryant@cisco.com, swallow@cisco.com, loa@pi.se
From: Greg Jones (ITU-T SG 15) <tsbsg15@itu.int>
Message-Id: <E1I3BXo-0001zF-OG@ietf.org>
Date: Tue, 26 Jun 2007 09:57:24 -0400
X-Spam-Score: -2.3 (--)
X-Scan-Signature: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3
X-Mailman-Approved-At: Tue, 26 Jun 2007 13:53:30 -0400
Cc: mpls@lists.ietf.org, greg.jones@itu.int, sob@harvard.edu,
	yoichi.maeda@ntt-at.co.jp, pwe3@ietf.org, dward@cisco.com,
	tsbsg15@itu.int, townsley@cisco.com, betts01@nortel.com
Subject: [PWE3] New Liaison Statement,
 "Response to PWE3 and MPLS WG concerns with G.8110.1 Amendment 1" 
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: tsbsg15@itu.int
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>
Errors-To: pwe3-bounces@ietf.org


Title: Response to PWE3 and MPLS WG concerns with G.8110.1 Amendment 1
Submission Date: 2007-06-26
URL of the IETF Web page: https://datatracker.ietf.org/public/liaison_detail.cgi?detail_id=345 

From: Greg Jones(ITU-T SG 15) <tsbsg15@itu.int>
To: IETF PWE3 and MPLS WGs(danny@arbor.net,stbryant@cisco.com,swallow@cisco.com,loa@pi.se)
Cc: jari.arkko@piuha.net
townsley@cisco.com
pwe3@ietf.org
rcallon@juniper.net
dward@cisco.com
sob@harvard.edu
mpls@lists.ietf.org
sjtrowbridge@alcatel-lucent.com
yoichi.maeda@ntt-at.co.jp
greg.jones@itu.int
Reponse Contact: tsbsg15@itu.int
Technical Contact: betts01@nortel.com
Purpose: For information 
Body: 
Attachment(s):
     Response to PWE3 and MPLS WG concerns with G.8110.1 Amendment 1 - body text (https://datatracker.ietf.org/documents/LIAISON/file453.doc)





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



From pwe3-bounces@ietf.org Tue Jun 26 15:54:50 2007
Return-path: <pwe3-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I3H7c-00010q-DM; Tue, 26 Jun 2007 15:54:44 -0400
Received: from pwe3 by megatron.ietf.org with local (Exim 4.43)
	id 1I3H7a-00010f-DE
	for pwe3-confirm+ok@megatron.ietf.org; Tue, 26 Jun 2007 15:54:42 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I3H7Y-00010O-UU
	for pwe3@ietf.org; Tue, 26 Jun 2007 15:54:41 -0400
Received: from sj-iport-5.cisco.com ([171.68.10.87])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I3H7Y-0006Pv-KP
	for pwe3@ietf.org; Tue, 26 Jun 2007 15:54:40 -0400
Received: from sj-dkim-3.cisco.com ([171.71.179.195])
	by sj-iport-5.cisco.com with ESMTP; 26 Jun 2007 12:54:40 -0700
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgAAALcLgUarR7PDh2dsb2JhbACPJgEBAQgOLA
X-IronPort-AV: i="4.16,464,1175497200"; 
	d="scan'208"; a="164287324:sNHT30296853"
Received: from sj-core-5.cisco.com (sj-core-5.cisco.com [171.71.177.238])
	by sj-dkim-3.cisco.com (8.12.11/8.12.11) with ESMTP id l5QJsdBW029525; 
	Tue, 26 Jun 2007 12:54:39 -0700
Received: from stewart-bryants-computer.local ([171.70.251.30])
	by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id l5QJsdka007359;
	Tue, 26 Jun 2007 19:54:39 GMT
Message-ID: <46816F00.9020209@cisco.com>
Date: Tue, 26 Jun 2007 20:54:40 +0100
From: Stewart Bryant <stbryant@cisco.com>
User-Agent: Thunderbird 2.0.0.4 (Macintosh/20070604)
MIME-Version: 1.0
Subject: Re: [PWE3] New Liaison Statement,
	"Response to PWE3 and MPLS WG concerns with G.8110.1 Amendment 1"
References: <E1I3BXo-0001zF-OG@ietf.org>
In-Reply-To: <E1I3BXo-0001zF-OG@ietf.org>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=2767; t=1182887679;
	x=1183751679; c=relaxed/simple; s=sjdkim3002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=stbryant@cisco.com;
	z=From:=20Stewart=20Bryant=20<stbryant@cisco.com>
	|Subject:=20Re=3A=20[PWE3]=20New=20Liaison=20Statement,
	=20=22Response=20t
	o=20PWE3=20and=20MPLS=20WG=20concerns=0A=20with=20G.8110.1=20Amendment=201
	=22 |Sender:=20;
	bh=jhLFopioNbpAJNYKC7nf1sPtuHcRYkLiK3XcSYUHz+Q=;
	b=TU8l37au+ged+OI3/lkwbziS8Wkq4BLSknoAhh7osjUeBTtR/JklFQWN6AEkPhWZBUgCvOEQ
	LhXSJ9urAAGMTn15g83E32NXGt2vUzBY8znNcnNMa55YpmzwXEQpzeRa;
Authentication-Results: sj-dkim-3; header.From=stbryant@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim3002 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c0bedb65cce30976f0bf60a0a39edea4
Cc: mpls@lists.ietf.org, pwe3@ietf.org
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: stbryant@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>
Errors-To: pwe3-bounces@ietf.org

The IETF response to our liaison of draft-ietf-pwe3-mpls-transport-00.txt
was sent as a word document. To make sure that all members of PWE3 are 
able to read it, I have extracted the substantive text as ASCII.

I have major concerns about the assumption of disjoint operation since I 
cannot see how the T-MPLS protocol prevents this.

I request WG input on how to respond to this liaison.

- Stewart

======

Thank you for your liaison statement “PWE3 and MPLS WG response to 
G.8110.1 Amendment 1”. 

We note your concerns with our work on T-MPLS and your draft 
http://www.ietf.org/internet-drafts/draft-ietf-pwe3-mpls-transport-00.txt.

It appears that the work in the IETF is addressing some different 
requirements:

“Input from network operators indicates that the key requirements is the 
transparent carriage of the MPLS network of one party over the MPLS 
network of another party, with the constraint that the MPLS design MUST 
NOT be changed and that the solution MUST be compatible with their 
existing large base of already deployed MPLS networks.”

Some members of SG 15 expressed support for these requirements.  
However, the basis for the work in SG 15 has been the development of a 
packet switched network that meets all of the network operators 
transport operations requirements.  The assumption we have made is that 
when deploying T-MPLS for this purpose it will be deployed on a network 
that is disjoint from any already deployed IP/MPLS network.

Equipment developed prior to the approval of the T-MPLS Recommendations 
is not expected to comply with these Recommendations.

Our intention in developing the suite of T-MPLS Recommendations is to 
define a packet based transport network technology.  The design 
objectives of T-MPLS are:

a) Follow the principles of the transport network used in other ITU-T 
defined transport technologies (e.g SDH, ATM, OTN).

b) To use the PDU and forwarding plane processes defined by the IETF for 
MPLS.

After the presentation of the Liaison Statement the following was noted:

•    T-MPLS OAM mechanisms have been developed by ITU-T G.8114/Y.1373 to 
provide transport-like fault and performance monitoring capabilities 
including alarm suppression, packet loss measurements and support of 
multiple ownerships

•    T-MPLS protection mechanisms have been developed by ITU-T G.8131 to 
provide transport-like protection schemes including trail and 
sub-network protection

•    The separation between the data plane and the control plane is a 
major requirement in transport networks

An electronic copy of this liaison statement is available at:
http://ties.itu.ch/ftp/public/itu-t/tsg15opticaltransport/COMMUNICATIONS/





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



From pwe3-bounces@ietf.org Tue Jun 26 19:03:42 2007
Return-path: <pwe3-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I3K4Q-0005Uf-F9; Tue, 26 Jun 2007 19:03:38 -0400
Received: from pwe3 by megatron.ietf.org with local (Exim 4.43)
	id 1I3K4P-0005UM-8i
	for pwe3-confirm+ok@megatron.ietf.org; Tue, 26 Jun 2007 19:03:37 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I3K4O-0005Sq-Sr
	for pwe3@ietf.org; Tue, 26 Jun 2007 19:03:36 -0400
Received: from rtp-iport-1.cisco.com ([64.102.122.148])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I3K3u-0007m6-Qd
	for pwe3@ietf.org; Tue, 26 Jun 2007 19:03:36 -0400
Received: from rtp-dkim-1.cisco.com ([64.102.121.158])
	by rtp-iport-1.cisco.com with ESMTP; 26 Jun 2007 19:03:07 -0400
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ao8CAGw4gUZAZnme/2dsb2JhbAA
X-IronPort-AV: i="4.16,464,1175486400"; 
	d="scan'208"; a="63753868:sNHT42693804"
Received: from rtp-core-1.cisco.com (rtp-core-1.cisco.com [64.102.124.12])
	by rtp-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id l5QN368V022632; 
	Tue, 26 Jun 2007 19:03:06 -0400
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com
	[64.102.31.12])
	by rtp-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id l5QN2mZj014943; 
	Tue, 26 Jun 2007 23:03:02 GMT
Received: from xmb-rtp-203.amer.cisco.com ([64.102.31.20]) by
	xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 26 Jun 2007 19:01:38 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
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] New Liaison Statement,
	"Response to PWE3 and MPLS WG concerns with G.8110.1 Amendment 1"
Date: Tue, 26 Jun 2007 19:01:37 -0400
Message-ID: <829173BE40A7F147AC51726688B0374B0310B77E@xmb-rtp-203.amer.cisco.com>
In-Reply-To: <46816F00.9020209@cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [PWE3] New Liaison Statement,
	"Response to PWE3 and MPLS WG concerns with G.8110.1 Amendment 1"
Thread-Index: Ace4K+iJ5DLN6SI/S96633bgfP4mKwAFUXnw
From: "Kyung-Yeop Hong \(hongk\)" <hongk@cisco.com>
To: "Stewart Bryant \(stbryant\)" <stbryant@cisco.com>
X-OriginalArrivalTime: 26 Jun 2007 23:01:38.0556 (UTC)
	FILETIME=[F3C7CBC0:01C7B845]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=3769; t=1182898986;
	x=1183762986; c=relaxed/simple; s=rtpdkim1001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=hongk@cisco.com;
	z=From:=20=22Kyung-Yeop=20Hong=20\(hongk\)=22=20<hongk@cisco.com>
	|Subject:=20RE=3A=20[PWE3]=20New=20Liaison=20Statement,
	=22Response=20to=2
	0PWE3=20and=20MPLS=20WG=20concerns=20with=20G.8110.1=20Amendment=201=22
	|Sender:=20
	|To:=20=22Stewart=20Bryant=20\(stbryant\)=22=20<stbryant@cisco.com>;
	bh=/hVbI7FH6NO+ZACdiD2mnAEhcC4Cam7NgxSWolmlumY=;
	b=cVXiC7Uv4B7NB68zSWowUOlD5LlnrBs6mg4vOSWx4piyF+i0d53zgUrs+u4H0FzAeOwa9yQ1
	TV+I+wuE+L+GyiY3Bxq48KypY0NVqeDUaP+h7nH8B1pruA2ys9hTHrpQ;
Authentication-Results: rtp-dkim-1; header.From=hongk@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim1001 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a87a9cdae4ac5d3fbeee75cd0026d632
Cc: mpls@lists.ietf.org, 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>
Errors-To: pwe3-bounces@ietf.org

I attended the discussion at the ITU-T SG15 meeting in Geneva when
Stewart presented the IETF liaison of
draft-ietf-pwe3-mpls-transport-00.txt.

Some members of SG15, including major carriers and vendors, expressed
their support for the IETF draft, and requested to include their
opinions in the response liaison statement. However, their requests were
not taken.
Stewart was there so he knows this as well.

It is surprising that this response liaison does not reflect the reality
of the discussion occurred at the SG15 meeting.

Kyung-Yeop


-----Original Message-----
From: Stewart Bryant (stbryant)=20
Sent: Tuesday, June 26, 2007 3:55 PM
Cc: mpls@lists.ietf.org; pwe3@ietf.org
Subject: Re: [PWE3] New Liaison Statement,"Response to PWE3 and MPLS WG
concerns with G.8110.1 Amendment 1"

The IETF response to our liaison of
draft-ietf-pwe3-mpls-transport-00.txt
was sent as a word document. To make sure that all members of PWE3 are=20
able to read it, I have extracted the substantive text as ASCII.

I have major concerns about the assumption of disjoint operation since I

cannot see how the T-MPLS protocol prevents this.

I request WG input on how to respond to this liaison.

- Stewart

=3D=3D=3D=3D=3D=3D

Thank you for your liaison statement "PWE3 and MPLS WG response to=20
G.8110.1 Amendment 1".=20

We note your concerns with our work on T-MPLS and your draft=20
http://www.ietf.org/internet-drafts/draft-ietf-pwe3-mpls-transport-00.tx
t.

It appears that the work in the IETF is addressing some different=20
requirements:

"Input from network operators indicates that the key requirements is the

transparent carriage of the MPLS network of one party over the MPLS=20
network of another party, with the constraint that the MPLS design MUST=20
NOT be changed and that the solution MUST be compatible with their=20
existing large base of already deployed MPLS networks."

Some members of SG 15 expressed support for these requirements. =20
However, the basis for the work in SG 15 has been the development of a=20
packet switched network that meets all of the network operators=20
transport operations requirements.  The assumption we have made is that=20
when deploying T-MPLS for this purpose it will be deployed on a network=20
that is disjoint from any already deployed IP/MPLS network.

Equipment developed prior to the approval of the T-MPLS Recommendations=20
is not expected to comply with these Recommendations.

Our intention in developing the suite of T-MPLS Recommendations is to=20
define a packet based transport network technology.  The design=20
objectives of T-MPLS are:

a) Follow the principles of the transport network used in other ITU-T=20
defined transport technologies (e.g SDH, ATM, OTN).

b) To use the PDU and forwarding plane processes defined by the IETF for

MPLS.

After the presentation of the Liaison Statement the following was noted:

*    T-MPLS OAM mechanisms have been developed by ITU-T G.8114/Y.1373 to

provide transport-like fault and performance monitoring capabilities=20
including alarm suppression, packet loss measurements and support of=20
multiple ownerships

*    T-MPLS protection mechanisms have been developed by ITU-T G.8131 to

provide transport-like protection schemes including trail and=20
sub-network protection

*    The separation between the data plane and the control plane is a=20
major requirement in transport networks

An electronic copy of this liaison statement is available at:
http://ties.itu.ch/ftp/public/itu-t/tsg15opticaltransport/COMMUNICATIONS
/





_______________________________________________
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 Jun 28 02:07:07 2007
Return-path: <pwe3-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I3n9f-0001mO-PI; Thu, 28 Jun 2007 02:06:59 -0400
Received: from pwe3 by megatron.ietf.org with local (Exim 4.43)
	id 1I3n9e-0001lp-9A
	for pwe3-confirm+ok@megatron.ietf.org; Thu, 28 Jun 2007 02:06:58 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I3n9d-0001kq-OE
	for pwe3@ietf.org; Thu, 28 Jun 2007 02:06:57 -0400
Received: from mx2-n.rad.co.il ([62.0.23.221] helo=antivir2.rad.co.il)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I3n9M-00034z-5n
	for pwe3@ietf.org; Thu, 28 Jun 2007 02:06:57 -0400
Received: from exrad3.rad.co.il (HELO exrad3.ad.rad.co.il) ([192.114.24.112])
	by antivir2.rad.co.il with ESMTP; 28 Jun 2007 09:06:37 +0300
X-MimeOLE: Produced By Microsoft Exchange V6.5
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] New Liaison Statement,
	"Response to PWE3 and MPLS WG concerns with G.8110.1 Amendment 1"
Date: Thu, 28 Jun 2007 09:06:36 +0300
Message-ID: <457D36D9D89B5B47BC06DA869B1C815D045C8EAE@exrad3.ad.rad.co.il>
In-Reply-To: <46816F00.9020209@cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [PWE3] New Liaison Statement,
	"Response to PWE3 and MPLS WG concerns with G.8110.1 Amendment 1"
Thread-Index: Ace4K+PmizzvDV9GRKSw6RIcLy6tAQBHbfSg
From: "Yaakov Stein" <yaakov_s@rad.com>
To: <stbryant@cisco.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7baded97d9887f7a0c7e8a33c2e3ea1b
Cc: mpls@lists.ietf.org, 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>
Errors-To: pwe3-bounces@ietf.org

Stewart,=20

If SG15's position is
  "The assumption we have made is that when deploying T-MPLS for this
purpose=20
   it will be deployed on a network that is disjoint from any already
deployed IP/MPLS network."
then they should explicitly state a limitation in the scope section of
the new Recommendation.

I recall several times when as editor I was forced to add such
limitations.

Something like
  "The protocol described in the Recommendation shall not be deployed in
any existing IP/MPLS network,
   nor shall it interwork in any fashion with such a network."

Y(J)S



-----Original Message-----
From: Stewart Bryant [mailto:stbryant@cisco.com]=20
Sent: Tuesday, June 26, 2007 22:55
Cc: mpls@lists.ietf.org; pwe3@ietf.org
Subject: Re: [PWE3] New Liaison Statement,"Response to PWE3 and MPLS WG
concerns with G.8110.1 Amendment 1"

The IETF response to our liaison of
draft-ietf-pwe3-mpls-transport-00.txt
was sent as a word document. To make sure that all members of PWE3 are
able to read it, I have extracted the substantive text as ASCII.

I have major concerns about the assumption of disjoint operation since I
cannot see how the T-MPLS protocol prevents this.

I request WG input on how to respond to this liaison.

- Stewart


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



From pwe3-bounces@ietf.org Thu Jun 28 02:23:07 2007
Return-path: <pwe3-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I3nPB-0003sp-Fy; Thu, 28 Jun 2007 02:23:01 -0400
Received: from pwe3 by megatron.ietf.org with local (Exim 4.43)
	id 1I3nP0-0003nT-IA
	for pwe3-confirm+ok@megatron.ietf.org; Thu, 28 Jun 2007 02:22:51 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I3nOz-0003eZ-3J
	for pwe3@ietf.org; Thu, 28 Jun 2007 02:22:49 -0400
Received: from mxa6.qos.net.il ([80.74.96.6] helo=mx05.qos.net.il)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I3nKn-0006u8-VS
	for pwe3@ietf.org; Thu, 28 Jun 2007 02:18:47 -0400
Received: from mail.axerra.com (webmail.axerra.com [80.74.100.75])
	by mx05.qos.net.il (Postfix) with ESMTP id 5A38737746A
	for <pwe3@ietf.org>; Thu, 28 Jun 2007 09:18:26 +0300 (IDT)
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [mpls] RE: [PWE3] New Liaison Statement,
	"Response to PWE3 and MPLS WG concerns with G.8110.1 Amendment 1"
Date: Thu, 28 Jun 2007 09:17:43 +0300
Message-ID: <D849FF14B5E0B142ADFC9A92C509E9BB010E7DE2@tlv2.iprad.local>
In-Reply-To: <457D36D9D89B5B47BC06DA869B1C815D045C8EAE@exrad3.ad.rad.co.il>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [mpls] RE: [PWE3] New Liaison Statement,
	"Response to PWE3 and MPLS WG concerns with G.8110.1 Amendment 1"
Thread-index: Ace4K+PmizzvDV9GRKSw6RIcLy6tAQBHbfSgAABIAlA=
From: "Sasha Vainshtein" <Sasha@AXERRA.com>
To: "Yaakov Stein" <yaakov_s@rad.com>,
	<stbryant@cisco.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d8ae4fd88fcaf47c1a71c804d04f413d
Cc: mpls@lists.ietf.org, 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>
Errors-To: pwe3-bounces@ietf.org

Yaakov, Stewart and all.

IMHO the only real way to assure disjoint operation of MPLS and T-MPLS=20
is to allocate dedicated protocol numbers (EtherType etc.) for T-MPLS.
Such an allocation would not harm T-MPLS in any way.

On the contrary, to the best of my understanding, usage of the same
protocol=20
numbers cannot not serve any purpose beyond facilitating MPLS/T-MPLS=20
interworking (be it intentional or not).

So I suggest we resurrect our old proposal to SG15 to switch to a
different
set of protocol numbers.

My 2c.

Regards,
                     Sasha
=20

-----Original Message-----
From: Yaakov Stein [mailto:yaakov_s@rad.com]=20
Sent: Thursday, June 28, 2007 9:07 AM
To: stbryant@cisco.com
Cc: mpls@lists.ietf.org; pwe3@ietf.org
Subject: [mpls] RE: [PWE3] New Liaison Statement,"Response to PWE3 and
MPLS WG concerns with G.8110.1 Amendment 1"

Stewart,=20

If SG15's position is
  "The assumption we have made is that when deploying T-MPLS for this
purpose=20
   it will be deployed on a network that is disjoint from any already
deployed IP/MPLS network."
then they should explicitly state a limitation in the scope section of
the new Recommendation.

I recall several times when as editor I was forced to add such
limitations.

Something like
  "The protocol described in the Recommendation shall not be deployed in
any existing IP/MPLS network,
   nor shall it interwork in any fashion with such a network."

Y(J)S



-----Original Message-----
From: Stewart Bryant [mailto:stbryant@cisco.com]
Sent: Tuesday, June 26, 2007 22:55
Cc: mpls@lists.ietf.org; pwe3@ietf.org
Subject: Re: [PWE3] New Liaison Statement,"Response to PWE3 and MPLS WG
concerns with G.8110.1 Amendment 1"

The IETF response to our liaison of
draft-ietf-pwe3-mpls-transport-00.txt
was sent as a word document. To make sure that all members of PWE3 are
able to read it, I have extracted the substantive text as ASCII.

I have major concerns about the assumption of disjoint operation since I
cannot see how the T-MPLS protocol prevents this.

I request WG input on how to respond to this liaison.

- Stewart


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


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



From pwe3-bounces@ietf.org Fri Jun 29 03:16:54 2007
Return-path: <pwe3-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I4Aik-0001L4-Hr; Fri, 29 Jun 2007 03:16:46 -0400
Received: from pwe3 by megatron.ietf.org with local (Exim 4.43)
	id 1I4Aii-0001GJ-Vh
	for pwe3-confirm+ok@megatron.ietf.org; Fri, 29 Jun 2007 03:16:44 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I4Aii-0001Fr-Dq; Fri, 29 Jun 2007 03:16:44 -0400
Received: from colt-na7.alcatel.fr ([62.23.212.7] helo=smail6.alcatel.fr)
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1I4Aid-0002Mj-12; Fri, 29 Jun 2007 03:16:44 -0400
Received: from FRVELSBHS04.ad2.ad.alcatel.com (frvelsbhs04.ad2.ad.alcatel.com
	[155.132.6.76])
	by smail6.alcatel.fr (8.13.4/8.13.4/ICT) with ESMTP id l5T7GU5f020567; 
	Fri, 29 Jun 2007 09:16:30 +0200
Received: from itvimn0i34082 ([151.98.71.211]) by
	FRVELSBHS04.ad2.ad.alcatel.com over TLS secured channel with
	Microsoft SMTPSVC(6.0.3790.2499); Fri, 29 Jun 2007 09:16:36 +0200
From: "Italo Busi" <Italo.Busi@alcatel-lucent.it>
To: "'Yaakov Stein'" <yaakov_s@rad.com>, <stbryant@cisco.com>
Subject: RE: [PWE3] New Liaison Statement,
	"Response to PWE3 and MPLS WG concerns with G.8110.1 Amendment 1"
Date: Fri, 29 Jun 2007 09:17:06 +0200
Message-ID: <004401c7ba1d$7ff99730$d3476297@vim.tlt.alcatel.it>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3138
Thread-Index: Ace4K+PmizzvDV9GRKSw6RIcLy6tAQBHbfSgADS8wbA=
In-Reply-To: <457D36D9D89B5B47BC06DA869B1C815D045C8EAE@exrad3.ad.rad.co.il>
X-OriginalArrivalTime: 29 Jun 2007 07:16:36.0215 (UTC)
	FILETIME=[6DCA7070:01C7BA1D]
X-Scanned-By: MIMEDefang 2.51 on 155.132.188.84
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0fa76816851382eb71b0a882ccdc29ac
Cc: mpls@lists.ietf.org, 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>
Errors-To: pwe3-bounces@ietf.org

Yaakov,

actually G.8110.1 Amendment 1 inserts the following statement at the end of the
Scope clause of G.8110.1:

"
Equipment developed prior to the production of this Recommendation is not
expected to comply with this Recommendation.
" 

Note that the fact that T-MPLS is not intended for deployment inside existing
IP/MPLS networks does not mean that T-MPLS shall not interwork with IP/MPLS.

SDH, OTH and WDM are networks disjoint from IP/MPLS networks but these networks
interoperate (via a client/server relationship).

Italo

> -----Original Message-----
> From: Yaakov Stein [mailto:yaakov_s@rad.com] 
> Sent: Thursday, June 28, 2007 8:07 AM
> To: stbryant@cisco.com
> Cc: mpls@lists.ietf.org; pwe3@ietf.org
> Subject: RE: [PWE3] New Liaison Statement,"Response to PWE3 
> and MPLS WG concerns with G.8110.1 Amendment 1"
> 
> Stewart, 
> 
> If SG15's position is
>   "The assumption we have made is that when deploying T-MPLS for this
> purpose 
>    it will be deployed on a network that is disjoint from any already
> deployed IP/MPLS network."
> then they should explicitly state a limitation in the scope section of
> the new Recommendation.
> 
> I recall several times when as editor I was forced to add such
> limitations.
> 
> Something like
>   "The protocol described in the Recommendation shall not be 
> deployed in
> any existing IP/MPLS network,
>    nor shall it interwork in any fashion with such a network."
> 
> Y(J)S
> 
> 
> 
> -----Original Message-----
> From: Stewart Bryant [mailto:stbryant@cisco.com] 
> Sent: Tuesday, June 26, 2007 22:55
> Cc: mpls@lists.ietf.org; pwe3@ietf.org
> Subject: Re: [PWE3] New Liaison Statement,"Response to PWE3 
> and MPLS WG
> concerns with G.8110.1 Amendment 1"
> 
> The IETF response to our liaison of
> draft-ietf-pwe3-mpls-transport-00.txt
> was sent as a word document. To make sure that all members of PWE3 are
> able to read it, I have extracted the substantive text as ASCII.
> 
> I have major concerns about the assumption of disjoint 
> operation since I
> cannot see how the T-MPLS protocol prevents this.
> 
> I request WG input on how to respond to this liaison.
> 
> - 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 Fri Jun 29 03:37:16 2007
Return-path: <pwe3-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I4B2Y-0005Jx-Dj; Fri, 29 Jun 2007 03:37:14 -0400
Received: from pwe3 by megatron.ietf.org with local (Exim 4.43)
	id 1I4B2W-0005JZ-LP
	for pwe3-confirm+ok@megatron.ietf.org; Fri, 29 Jun 2007 03:37:12 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I4B2V-0005JQ-Qj; Fri, 29 Jun 2007 03:37:11 -0400
Received: from smail5.alcatel.fr ([62.23.212.27])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1I4B2N-0001wl-Rw; Fri, 29 Jun 2007 03:37:11 -0400
Received: from FRVELSBHS04.ad2.ad.alcatel.com (frvelsbhs04.ad2.ad.alcatel.com
	[155.132.6.76])
	by smail5.alcatel.fr (8.13.4/8.13.4/ICT) with ESMTP id l5T7ZH6j015491; 
	Fri, 29 Jun 2007 09:35:17 +0200
Received: from itvimn0i34082 ([151.98.71.211]) by
	FRVELSBHS04.ad2.ad.alcatel.com over TLS secured channel with
	Microsoft SMTPSVC(6.0.3790.2499); Fri, 29 Jun 2007 09:36:58 +0200
From: "Italo Busi" <Italo.Busi@alcatel-lucent.it>
To: "'Sasha Vainshtein'" <Sasha@AXERRA.com>,
	"'Yaakov Stein'" <yaakov_s@rad.com>, <stbryant@cisco.com>
Subject: RE: [mpls] RE: [PWE3] New Liaison Statement,
	"Response to PWE3 and MPLS WG concerns with G.8110.1 Amendment 1"
Date: Fri, 29 Jun 2007 09:37:28 +0200
Message-ID: <004d01c7ba20$5840a5a0$d3476297@vim.tlt.alcatel.it>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3138
Thread-Index: Ace4K+PmizzvDV9GRKSw6RIcLy6tAQBHbfSgAABIAlAANLu9EA==
In-Reply-To: <D849FF14B5E0B142ADFC9A92C509E9BB010E7DE2@tlv2.iprad.local>
X-OriginalArrivalTime: 29 Jun 2007 07:36:58.0082 (UTC)
	FILETIME=[46148C20:01C7BA20]
X-Scanned-By: MIMEDefang 2.51 on 155.132.188.13
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2086112c730e13d5955355df27e3074b
Cc: mpls@lists.ietf.org, 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>
Errors-To: pwe3-bounces@ietf.org

Sasha,

when the issue was discussed during the approval phase of G.8110.1, appendix III
was added to G.8110.1 to clarify why T-MPLS reuses the same protocol number
(e.g. EtherType) of MPLS and which are the implications for that.

In particular this appendix clearly states that:

"
When a pakcet is received on an Ethernet interface with EtherType 0x8847, it is
looked up in one particular label space as defined in IETF RFC 3031 section 3.4.

The label manager is responsible for the allocation and reclamation of the
labels that are used within an MPLS or T-MPLS adaptation function.
"

Given this behavior, I cannot understand any real technical argument in favour
of a different protocol number (e.g. EtherType).

T-MPLS and MPLS have the same forwarding plane. As you have stated, having the
same forwarding plane (including the same protocol number) is facilitating
MPLS/T-MPLS interworking.

This is for me another good technical reason not to change the protocol number
(e.g. EtherType).

Best regards, Italo

> -----Original Message-----
> From: Sasha Vainshtein [mailto:Sasha@AXERRA.com] 
> Sent: Thursday, June 28, 2007 8:18 AM
> To: Yaakov Stein; stbryant@cisco.com
> Cc: mpls@lists.ietf.org; pwe3@ietf.org
> Subject: RE: [mpls] RE: [PWE3] New Liaison 
> Statement,"Response to PWE3 and MPLS WG concerns with 
> G.8110.1 Amendment 1"
> 
> Yaakov, Stewart and all.
> 
> IMHO the only real way to assure disjoint operation of MPLS 
> and T-MPLS 
> is to allocate dedicated protocol numbers (EtherType etc.) for T-MPLS.
> Such an allocation would not harm T-MPLS in any way.
> 
> On the contrary, to the best of my understanding, usage of the same
> protocol 
> numbers cannot not serve any purpose beyond facilitating MPLS/T-MPLS 
> interworking (be it intentional or not).
> 
> So I suggest we resurrect our old proposal to SG15 to switch to a
> different
> set of protocol numbers.
> 
> My 2c.
> 
> Regards,
>                      Sasha
>  
> 
> -----Original Message-----
> From: Yaakov Stein [mailto:yaakov_s@rad.com] 
> Sent: Thursday, June 28, 2007 9:07 AM
> To: stbryant@cisco.com
> Cc: mpls@lists.ietf.org; pwe3@ietf.org
> Subject: [mpls] RE: [PWE3] New Liaison Statement,"Response to PWE3 and
> MPLS WG concerns with G.8110.1 Amendment 1"
> 
> Stewart, 
> 
> If SG15's position is
>   "The assumption we have made is that when deploying T-MPLS for this
> purpose 
>    it will be deployed on a network that is disjoint from any already
> deployed IP/MPLS network."
> then they should explicitly state a limitation in the scope section of
> the new Recommendation.
> 
> I recall several times when as editor I was forced to add such
> limitations.
> 
> Something like
>   "The protocol described in the Recommendation shall not be 
> deployed in
> any existing IP/MPLS network,
>    nor shall it interwork in any fashion with such a network."
> 
> Y(J)S
> 
> 
> 
> -----Original Message-----
> From: Stewart Bryant [mailto:stbryant@cisco.com]
> Sent: Tuesday, June 26, 2007 22:55
> Cc: mpls@lists.ietf.org; pwe3@ietf.org
> Subject: Re: [PWE3] New Liaison Statement,"Response to PWE3 
> and MPLS WG
> concerns with G.8110.1 Amendment 1"
> 
> The IETF response to our liaison of
> draft-ietf-pwe3-mpls-transport-00.txt
> was sent as a word document. To make sure that all members of PWE3 are
> able to read it, I have extracted the substantive text as ASCII.
> 
> I have major concerns about the assumption of disjoint 
> operation since I
> cannot see how the T-MPLS protocol prevents this.
> 
> I request WG input on how to respond to this liaison.
> 
> - Stewart
> 
> 
> _______________________________________________
> mpls mailing list
> mpls@lists.ietf.org
> https://www1.ietf.org/mailman/listinfo/mpls
> 
> 
> _______________________________________________
> 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 Jun 29 09:43:22 2007
Return-path: <pwe3-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I4Gkp-0005g0-Hc; Fri, 29 Jun 2007 09:43:19 -0400
Received: from pwe3 by megatron.ietf.org with local (Exim 4.43)
	id 1I4Gkn-0005fd-Hz
	for pwe3-confirm+ok@megatron.ietf.org; Fri, 29 Jun 2007 09:43:17 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I4Gkn-0005fJ-2P
	for pwe3@ietf.org; Fri, 29 Jun 2007 09:43:17 -0400
Received: from ams-iport-1.cisco.com ([144.254.224.140])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I4Gkm-0003z1-Kh
	for pwe3@ietf.org; Fri, 29 Jun 2007 09:43:16 -0400
Received: from ams-dkim-1.cisco.com ([144.254.224.138])
	by ams-iport-1.cisco.com with ESMTP; 29 Jun 2007 15:42:29 +0200
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgAAAEOphEaQ/uCKh2dsb2JhbACPKwIJDiw
X-IronPort-AV: i="4.16,475,1175464800"; 
	d="scan'208"; a="146861848:sNHT57710891538"
Received: from ams-core-1.cisco.com (ams-core-1.cisco.com [144.254.224.150])
	by ams-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id l5TDgT1p026929; 
	Fri, 29 Jun 2007 15:42:29 +0200
Received: from stewart-bryants-computer.local (ams3-vpn-dhcp741.cisco.com
	[10.61.66.229])
	by ams-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id l5TDgJTC025696; 
	Fri, 29 Jun 2007 13:42:23 GMT
Message-ID: <46850C3C.1020809@cisco.com>
Date: Fri, 29 Jun 2007 14:42:20 +0100
From: Stewart Bryant <stbryant@cisco.com>
User-Agent: Thunderbird 2.0.0.4 (Macintosh/20070604)
MIME-Version: 1.0
To: Italo Busi <Italo.Busi@alcatel-lucent.it>
Subject: Re: [PWE3] New Liaison Statement,
	"Response to PWE3 and MPLS WG concerns with G.8110.1 Amendment 1"
References: <004401c7ba1d$7ff99730$d3476297@vim.tlt.alcatel.it>
In-Reply-To: <004401c7ba1d$7ff99730$d3476297@vim.tlt.alcatel.it>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=2919; t=1183124549;
	x=1183988549; c=relaxed/simple; s=amsdkim1002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=stbryant@cisco.com;
	z=From:=20Stewart=20Bryant=20<stbryant@cisco.com>
	|Subject:=20Re=3A=20[PWE3]=20New=20Liaison=20Statement,
	=22Response=20to=2
	0PWE3=20and=20MPLS=20WG=20concerns=0A=20with=20G.8110.1=20Amendment=201=22
	|Sender:=20; bh=WrT8U3HNpLj5B+TRb6AaL8e7gKaecRA5zXpkjk39XwE=;
	b=j63z4wdGJLQpwO80YBcx9petvfKnQSfBhTvY6BHaJRnSj0G8GMKygAkq236xesl7Z1G2BjjA
	AvGnmYx6K1LFxY7FAGg+0EQEG+WpolVX9xWkb6RnMcwdnVVrvaPKY3v6;
Authentication-Results: ams-dkim-1; header.From=stbryant@cisco.com; dkim=pass (
	sig from cisco.com/amsdkim1002 verified; ); 
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 244a2fd369eaf00ce6820a760a3de2e8
Cc: mpls@lists.ietf.org, 'Yaakov Stein' <yaakov_s@rad.com>, pwe3@ietf.org
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: stbryant@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>
Errors-To: pwe3-bounces@ietf.org

Italo Busi wrote:
> Yaakov,
>
> actually G.8110.1 Amendment 1 inserts the following statement at the end of the
> Scope clause of G.8110.1:
>
> "
> Equipment developed prior to the production of this Recommendation is not
> expected to comply with this Recommendation.
> " 
>
>   
What that says is that MPLS equipment is not expected to comply with the 
T-MPLS design. I am not sure how concerned we need to be about that.

What is of concern is the inverse i.e. that T-MPLS - which runs on the 
same code-point as MPLS - MUST comply with the MPLS design, and the 
sentence above does not address that concern.

The concern here is that nothing in T-MPLS breaks MPLS (historic, 
current or future) in any MPLS deployment scenario.

> Note that the fact that T-MPLS is not intended for deployment inside existing
> IP/MPLS networks does not mean that T-MPLS shall not interwork with IP/MPLS.
>   
Hm - I am sure I saw Maartin present a contribution at ITU showing an 
T-MPLS equipment interworking with an MPLS equipment - could you make a 
copy of the contribution available to the IETF?

The first half of the sentence is clearly incorrect, in that IF T-MPLS 
is ever deployed, MPLS WILL be carried over T-MPLS. Given that LSRs 
terminate other transport network interfaces - SDH, SONET, T1/E1, 
Ethernet, the clear expectation is that future integration needs will 
mean that LSRs will need to terminate T-MPLS transport network 
interfaces. Therefore one equipment will need to be able to process MPLS 
and T-MPLS packets without ambiguity.

As we have said there are two ways to do this, either provide some clear 
method of discrimination - for example a separate set of codepoints, or 
provide complete compatibility - which requires T-MPLS to call by 
reference the MPLS specs so that there is no distinction between the two 
protocols.

I suppose one could take another approach and specify a mandatoty 
mechanism whereby presence of MPLS poisons the T-MPLS network so that if 
anyone ever attempts to interconnect MPLS and T-MPLS, the T-MPLS network 
crashes. Given the SG15 conviction that MPLS and T-MPLS will never be 
interconnected there should be no objection to the inclusion of this 
feature :)
> SDH, OTH and WDM are networks disjoint from IP/MPLS networks but these networks
> interoperate (via a client/server relationship).
>   
Firstly from the above you clearly accept my point that an LSR will need 
to terminate T-MPLS just as it does SDH etc.

Secondly the key difference is that there is no way that an an equipment 
can be become confused about whether it is dealing with an SDH frame or 
an IP packet. Here the ITU has deliberately constructed a mechanism 
whereby it is impossible to determine whether a packet is an MPLS packet 
or a T-MPLS packet, and that is the root of our concern and needs to be 
addressed.

- Stewart



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



From pwe3-bounces@ietf.org Fri Jun 29 09:47:10 2007
Return-path: <pwe3-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I4GoX-0001HC-Rq; Fri, 29 Jun 2007 09:47:09 -0400
Received: from pwe3 by megatron.ietf.org with local (Exim 4.43)
	id 1I4GoW-0001Gy-3q
	for pwe3-confirm+ok@megatron.ietf.org; Fri, 29 Jun 2007 09:47:08 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I4GoV-0001Gb-PY
	for pwe3@ietf.org; Fri, 29 Jun 2007 09:47:07 -0400
Received: from ams-iport-1.cisco.com ([144.254.224.140])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I4GoV-0004F5-Cr
	for pwe3@ietf.org; Fri, 29 Jun 2007 09:47:07 -0400
Received: from ams-dkim-1.cisco.com ([144.254.224.138])
	by ams-iport-1.cisco.com with ESMTP; 29 Jun 2007 15:46:49 +0200
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgAAAKqqhEaQ/uCKh2dsb2JhbACPKwIJDiw
X-IronPort-AV: i="4.16,475,1175464800"; 
	d="scan'208"; a="146862305:sNHT10252306586"
Received: from ams-core-1.cisco.com (ams-core-1.cisco.com [144.254.224.150])
	by ams-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id l5TDknaC028103; 
	Fri, 29 Jun 2007 15:46:49 +0200
Received: from stewart-bryants-computer.local (ams3-vpn-dhcp741.cisco.com
	[10.61.66.229])
	by ams-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id l5TDklTC026926; 
	Fri, 29 Jun 2007 13:46:47 GMT
Message-ID: <46850D48.2000703@cisco.com>
Date: Fri, 29 Jun 2007 14:46:48 +0100
From: Stewart Bryant <stbryant@cisco.com>
User-Agent: Thunderbird 2.0.0.4 (Macintosh/20070604)
MIME-Version: 1.0
To: Italo Busi <Italo.Busi@alcatel-lucent.it>
Subject: Re: [mpls] RE: [PWE3] New Liaison Statement,"Response to PWE3 and
	MPLS WG concerns with G.8110.1 Amendment 1"
References: <004d01c7ba20$5840a5a0$d3476297@vim.tlt.alcatel.it>
In-Reply-To: <004d01c7ba20$5840a5a0$d3476297@vim.tlt.alcatel.it>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=301; t=1183124809;
	x=1183988809; c=relaxed/simple; s=amsdkim1002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=stbryant@cisco.com;
	z=From:=20Stewart=20Bryant=20<stbryant@cisco.com>
	|Subject:=20Re=3A=20[mpls]=20RE=3A=20[PWE3]=20New=20Liaison=20Statement,
	=
	22Response=20to=20PWE3=20and=0A=20MPLS=20WG=20concerns=20with=20G.8110.1=2
	0Amendment=201=22 |Sender:=20;
	bh=mepbatB6boE6B0MPZLYyZbnzMNykC442l7FYIonIfEo=;
	b=mp7Y8EXsAn/ilB2+LjYgNIZDkQg8q8DHA3ttjrDjx8zBP2JVfa32oVb1t90IxHIdwzBOmsKf
	zx12WGmvBu7upAohjDx18SQI384UXtetvNi8805ARnOxZs+tfUEydZHO;
Authentication-Results: ams-dkim-1; header.From=stbryant@cisco.com; dkim=pass (
	sig from cisco.com/amsdkim1002 verified; ); 
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 68c8cc8a64a9d0402e43b8eee9fc4199
Cc: mpls@lists.ietf.org, 'Yaakov Stein' <yaakov_s@rad.com>, pwe3@ietf.org,
	'Sasha Vainshtein' <Sasha@AXERRA.com>
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: stbryant@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>
Errors-To: pwe3-bounces@ietf.org


>
> T-MPLS and MPLS have the same forwarding plane. As you have stated, having the
> same forwarding plane (including the same protocol number) is facilitating
> MPLS/T-MPLS interworking.
>   
Italo

Can we be crystal clear on this - is MPLS/T-MPLS interworking allowed or 
not?

Stewart


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



From pwe3-bounces@ietf.org Fri Jun 29 13:20:43 2007
Return-path: <pwe3-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I4K96-0005n9-Um; Fri, 29 Jun 2007 13:20:36 -0400
Received: from pwe3 by megatron.ietf.org with local (Exim 4.43)
	id 1I4K94-0005lV-6P
	for pwe3-confirm+ok@megatron.ietf.org; Fri, 29 Jun 2007 13:20:34 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I4K93-0005lJ-17
	for pwe3@ietf.org; Fri, 29 Jun 2007 13:20:33 -0400
Received: from mxa5.qos.net.il ([80.74.96.15] helo=mxa6.qos.net.il)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I4K8u-0003Z0-5t
	for pwe3@ietf.org; Fri, 29 Jun 2007 13:20:33 -0400
Received: from mail.axerra.com (webmail.axerra.com [80.74.100.75])
	by mxa6.qos.net.il (Postfix) with ESMTP id 0A6CB602720
	for <pwe3@ietf.org>; Fri, 29 Jun 2007 20:05:46 +0300 (IDT)
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [mpls] RE: [PWE3] New Liaison Statement,
	"Response to PWE3 and MPLS WG concerns with G.8110.1 Amendment 1"
Date: Fri, 29 Jun 2007 20:19:33 +0300
Message-ID: <D849FF14B5E0B142ADFC9A92C509E9BB010E7EEA@tlv2.iprad.local>
In-Reply-To: <004d01c7ba20$5840a5a0$d3476297@vim.tlt.alcatel.it>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [mpls] RE: [PWE3] New Liaison Statement,
	"Response to PWE3 and MPLS WG concerns with G.8110.1 Amendment 1"
Thread-index: Ace4K+PmizzvDV9GRKSw6RIcLy6tAQBHbfSgAABIAlAANLu9EAAUgNIw
From: "Sasha Vainshtein" <Sasha@AXERRA.com>
To: "Italo Busi" <Italo.Busi@alcatel-lucent.it>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2e8fc473f5174be667965460bd5288ba
Cc: mpls@lists.ietf.org, Yaakov Stein <yaakov_s@rad.com>, pwe3@ietf.org,
	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>
Errors-To: pwe3-bounces@ietf.org

Italo and all,
Please see inline below.

Regards,
                Sasha


-----Original Message-----
From: Italo Busi [mailto:Italo.Busi@alcatel-lucent.it]=20
Sent: Friday, June 29, 2007 10:37 AM
To: Sasha Vainshtein; 'Yaakov Stein'; stbryant@cisco.com
Cc: mpls@lists.ietf.org; pwe3@ietf.org
Subject: RE: [mpls] RE: [PWE3] New Liaison Statement,"Response to PWE3
and MPLS WG concerns with G.8110.1 Amendment 1"

Sasha,

when the issue was discussed during the approval phase of G.8110.1,
appendix III was added to G.8110.1 to clarify why T-MPLS reuses the same
protocol number (e.g. EtherType) of MPLS and which are the implications
for that.

In particular this appendix clearly states that:

"
When a pakcet is received on an Ethernet interface with EtherType
0x8847, it is looked up in one particular label space as defined in IETF
RFC 3031 section 3.4.

The label manager is responsible for the allocation and reclamation of
the labels that are used within an MPLS or T-MPLS adaptation function.
"
[Sasha] The problem, IMHO, is that the existing "label managers" (used
by the MPLS label distribution protocols) are NOT aware of
this distinction since it is NOT part of the existing MPLS control plane
specs.=20
The text you've quoted implicitly assumes  that the MPLS control plane
(specified, implemented and deployed) and the T-MPLS management plane
MUST interwork properly (by splitting the label spaces) in order to
prevent T-MPLS being poisoned by MPLS or vice versa. This sounds like
imposing a new requirement on the MPLS control protocols designed by the
IETF.
Did I miss something?

Given this behavior, I cannot understand any real technical argument in
favour of a different protocol number (e.g. EtherType).

T-MPLS and MPLS have the same forwarding plane. As you have stated,
having the same forwarding plane (including the same protocol number) is
facilitating MPLS/T-MPLS interworking.

This is for me another good technical reason not to change the protocol
number (e.g. EtherType).

[Sasha] I am completely confused now. Are MPLS and T-MPLS supposed to
interwork, or not?
Please note also that the current designs for, say P2MP (multicast) LSPs
use (to some extent) mapping of the protocol numbers to label spaces.
Hence using a separate protocol number for T-MPLS would be in line with
the common trend.


Best regards, Italo

> -----Original Message-----
> From: Sasha Vainshtein [mailto:Sasha@AXERRA.com]
> Sent: Thursday, June 28, 2007 8:18 AM
> To: Yaakov Stein; stbryant@cisco.com
> Cc: mpls@lists.ietf.org; pwe3@ietf.org
> Subject: RE: [mpls] RE: [PWE3] New Liaison Statement,"Response to PWE3

> and MPLS WG concerns with
> G.8110.1 Amendment 1"
>=20
> Yaakov, Stewart and all.
>=20
> IMHO the only real way to assure disjoint operation of MPLS and T-MPLS

> is to allocate dedicated protocol numbers (EtherType etc.) for T-MPLS.
> Such an allocation would not harm T-MPLS in any way.
>=20
> On the contrary, to the best of my understanding, usage of the same=20
> protocol numbers cannot not serve any purpose beyond facilitating=20
> MPLS/T-MPLS interworking (be it intentional or not).
>=20
> So I suggest we resurrect our old proposal to SG15 to switch to a=20
> different set of protocol numbers.
>=20
> My 2c.
>=20
> Regards,
>                      Sasha
> =20
>=20
> -----Original Message-----
> From: Yaakov Stein [mailto:yaakov_s@rad.com]
> Sent: Thursday, June 28, 2007 9:07 AM
> To: stbryant@cisco.com
> Cc: mpls@lists.ietf.org; pwe3@ietf.org
> Subject: [mpls] RE: [PWE3] New Liaison Statement,"Response to PWE3 and

> MPLS WG concerns with G.8110.1 Amendment 1"
>=20
> Stewart,
>=20
> If SG15's position is
>   "The assumption we have made is that when deploying T-MPLS for this=20
> purpose
>    it will be deployed on a network that is disjoint from any already=20
> deployed IP/MPLS network."
> then they should explicitly state a limitation in the scope section of

> the new Recommendation.
>=20
> I recall several times when as editor I was forced to add such=20
> limitations.
>=20
> Something like
>   "The protocol described in the Recommendation shall not be deployed=20
> in any existing IP/MPLS network,
>    nor shall it interwork in any fashion with such a network."
>=20
> Y(J)S
>=20
>=20
>=20
> -----Original Message-----
> From: Stewart Bryant [mailto:stbryant@cisco.com]
> Sent: Tuesday, June 26, 2007 22:55
> Cc: mpls@lists.ietf.org; pwe3@ietf.org
> Subject: Re: [PWE3] New Liaison Statement,"Response to PWE3 and MPLS=20
> WG concerns with G.8110.1 Amendment 1"
>=20
> The IETF response to our liaison of
> draft-ietf-pwe3-mpls-transport-00.txt
> was sent as a word document. To make sure that all members of PWE3 are

> able to read it, I have extracted the substantive text as ASCII.
>=20
> I have major concerns about the assumption of disjoint operation since

> I cannot see how the T-MPLS protocol prevents this.
>=20
> I request WG input on how to respond to this liaison.
>=20
> - Stewart
>=20
>=20
> _______________________________________________
> mpls mailing list
> mpls@lists.ietf.org
> https://www1.ietf.org/mailman/listinfo/mpls
>=20
>=20
> _______________________________________________
> pwe3 mailing list
> pwe3@ietf.org
> https://www1.ietf.org/mailman/listinfo/pwe3
>=20


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



From pwe3-bounces@ietf.org Fri Jun 29 13:27:25 2007
Return-path: <pwe3-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I4KFh-0001Ys-93; Fri, 29 Jun 2007 13:27:25 -0400
Received: from pwe3 by megatron.ietf.org with local (Exim 4.43)
	id 1I4KFf-0001U7-D7
	for pwe3-confirm+ok@megatron.ietf.org; Fri, 29 Jun 2007 13:27:23 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I4KFe-0001Tl-Vu
	for pwe3@ietf.org; Fri, 29 Jun 2007 13:27:22 -0400
Received: from sj-iport-6.cisco.com ([171.71.176.117])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I4KEw-0005Pe-8M
	for pwe3@ietf.org; Fri, 29 Jun 2007 13:27:22 -0400
Received: from sj-dkim-3.cisco.com ([171.71.179.195])
	by sj-iport-6.cisco.com with ESMTP; 29 Jun 2007 10:26:37 -0700
X-IronPort-AV: i="4.16,476,1175497200"; 
	d="scan'208"; a="174488237:sNHT61810776"
Received: from sj-core-1.cisco.com (sj-core-1.cisco.com [171.71.177.237])
	by sj-dkim-3.cisco.com (8.12.11/8.12.11) with ESMTP id l5THQa3W031458; 
	Fri, 29 Jun 2007 10:26:36 -0700
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com
	[64.102.31.12])
	by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id l5THQFXr010373;
	Fri, 29 Jun 2007 17:26:35 GMT
Received: from xfe-rtp-201.amer.cisco.com ([64.102.31.38]) by
	xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 29 Jun 2007 13:26:35 -0400
Received: from [10.83.15.51] ([10.83.15.51]) by xfe-rtp-201.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 29 Jun 2007 13:26:34 -0400
In-Reply-To: <D849FF14B5E0B142ADFC9A92C509E9BB010E7EEA@tlv2.iprad.local>
References: <D849FF14B5E0B142ADFC9A92C509E9BB010E7EEA@tlv2.iprad.local>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <D2A652E2-DF6E-4079-B7C6-792C7753CCBC@cisco.com>
Content-Transfer-Encoding: 7bit
From: "Thomas D. Nadeau" <tnadeau@cisco.com>
Subject: Re: [mpls] RE: [PWE3] New Liaison Statement,
	"Response to PWE3 and MPLS WG concerns with G.8110.1 Amendment 1"
Date: Fri, 29 Jun 2007 13:26:32 -0400
To: "Sasha Vainshtein" <Sasha@AXERRA.com>
X-Mailer: Apple Mail (2.752.3)
X-OriginalArrivalTime: 29 Jun 2007 17:26:34.0680 (UTC)
	FILETIME=[A42D0380:01C7BA72]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=6023; t=1183137996;
	x=1184001996; c=relaxed/simple; s=sjdkim3002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=tnadeau@cisco.com;
	z=From:=20=22Thomas=20D.=20Nadeau=22=20<tnadeau@cisco.com>
	|Subject:=20Re=3A=20[mpls]=20RE=3A=20[PWE3]=20New=20Liaison=20Statement,
	=
	20=22Response=20to=20PWE3=20and=20MPLS=20WG=20concerns=20with=20G.8110.1=2
	0Amendment=201=22 |Sender:=20;
	bh=v39AAqk9WrAH1MBLV3tQdZrwtTfJxokGaPL+dot1oHM=;
	b=S8T3JFUU4HNQfKpvGg3JT0kjsUaTrg3OTB8n9YJMVgdnbPvnzLDyF+rXFMsZkLOnb37elbdd
	ZhQ5mF4bDR6m053Amv/K4kdQavglO2gu5ZP43lhSH6RqvqcIN5j8jk2+;
Authentication-Results: sj-dkim-3; header.From=tnadeau@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim3002 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 43317e64100dd4d87214c51822b582d1
Cc: mpls@lists.ietf.org, Italo Busi <Italo.Busi@alcatel-lucent.it>,
	Yaakov Stein <yaakov_s@rad.com>, pwe3@ietf.org, 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>
Errors-To: pwe3-bounces@ietf.org


On Jun 29, 2007:1:19 PM, at 1:19 PM, Sasha Vainshtein wrote:

> Italo and all,
> Please see inline below.
>
> Regards,
>                 Sasha
>
>
> -----Original Message-----
> From: Italo Busi [mailto:Italo.Busi@alcatel-lucent.it]
> Sent: Friday, June 29, 2007 10:37 AM
> To: Sasha Vainshtein; 'Yaakov Stein'; stbryant@cisco.com
> Cc: mpls@lists.ietf.org; pwe3@ietf.org
> Subject: RE: [mpls] RE: [PWE3] New Liaison Statement,"Response to PWE3
> and MPLS WG concerns with G.8110.1 Amendment 1"
>
> Sasha,
>
> when the issue was discussed during the approval phase of G.8110.1,
> appendix III was added to G.8110.1 to clarify why T-MPLS reuses the  
> same
> protocol number (e.g. EtherType) of MPLS and which are the  
> implications
> for that.
>
> In particular this appendix clearly states that:
>
> "
> When a pakcet is received on an Ethernet interface with EtherType
> 0x8847, it is looked up in one particular label space as defined in  
> IETF
> RFC 3031 section 3.4.
>
> The label manager is responsible for the allocation and reclamation of
> the labels that are used within an MPLS or T-MPLS adaptation function.
> "
> [Sasha] The problem, IMHO, is that the existing "label managers" (used
> by the MPLS label distribution protocols) are NOT aware of
> this distinction since it is NOT part of the existing MPLS control  
> plane
> specs.
> The text you've quoted implicitly assumes  that the MPLS control plane
> (specified, implemented and deployed) and the T-MPLS management plane
> MUST interwork properly (by splitting the label spaces) in order to
> prevent T-MPLS being poisoned by MPLS or vice versa. This sounds like
> imposing a new requirement on the MPLS control protocols designed  
> by the
> IETF.
> Did I miss something?
>
> Given this behavior, I cannot understand any real technical  
> argument in
> favour of a different protocol number (e.g. EtherType).
>
> T-MPLS and MPLS have the same forwarding plane. As you have stated,
> having the same forwarding plane (including the same protocol  
> number) is
> facilitating MPLS/T-MPLS interworking.
>
> This is for me another good technical reason not to change the  
> protocol
> number (e.g. EtherType).
>
> [Sasha] I am completely confused now. Are MPLS and T-MPLS supposed to
> interwork, or not?
> Please note also that the current designs for, say P2MP (multicast)  
> LSPs
> use (to some extent) mapping of the protocol numbers to label spaces.
> Hence using a separate protocol number for T-MPLS would be in line  
> with
> the common trend.

	This is clearly what is the most ridiculous part here.
If we just keep MPLS <= T-MPLS "interworking" or any other translation
functions are a non-issue. Let us please keep things simple.

	--Tom



> Best regards, Italo
>
>> -----Original Message-----
>> From: Sasha Vainshtein [mailto:Sasha@AXERRA.com]
>> Sent: Thursday, June 28, 2007 8:18 AM
>> To: Yaakov Stein; stbryant@cisco.com
>> Cc: mpls@lists.ietf.org; pwe3@ietf.org
>> Subject: RE: [mpls] RE: [PWE3] New Liaison Statement,"Response to  
>> PWE3
>
>> and MPLS WG concerns with
>> G.8110.1 Amendment 1"
>>
>> Yaakov, Stewart and all.
>>
>> IMHO the only real way to assure disjoint operation of MPLS and T- 
>> MPLS
>
>> is to allocate dedicated protocol numbers (EtherType etc.) for T- 
>> MPLS.
>> Such an allocation would not harm T-MPLS in any way.
>>
>> On the contrary, to the best of my understanding, usage of the same
>> protocol numbers cannot not serve any purpose beyond facilitating
>> MPLS/T-MPLS interworking (be it intentional or not).
>>
>> So I suggest we resurrect our old proposal to SG15 to switch to a
>> different set of protocol numbers.
>>
>> My 2c.
>>
>> Regards,
>>                      Sasha
>>
>>
>> -----Original Message-----
>> From: Yaakov Stein [mailto:yaakov_s@rad.com]
>> Sent: Thursday, June 28, 2007 9:07 AM
>> To: stbryant@cisco.com
>> Cc: mpls@lists.ietf.org; pwe3@ietf.org
>> Subject: [mpls] RE: [PWE3] New Liaison Statement,"Response to PWE3  
>> and
>
>> MPLS WG concerns with G.8110.1 Amendment 1"
>>
>> Stewart,
>>
>> If SG15's position is
>>   "The assumption we have made is that when deploying T-MPLS for this
>> purpose
>>    it will be deployed on a network that is disjoint from any already
>> deployed IP/MPLS network."
>> then they should explicitly state a limitation in the scope  
>> section of
>
>> the new Recommendation.
>>
>> I recall several times when as editor I was forced to add such
>> limitations.
>>
>> Something like
>>   "The protocol described in the Recommendation shall not be deployed
>> in any existing IP/MPLS network,
>>    nor shall it interwork in any fashion with such a network."
>>
>> Y(J)S
>>
>>
>>
>> -----Original Message-----
>> From: Stewart Bryant [mailto:stbryant@cisco.com]
>> Sent: Tuesday, June 26, 2007 22:55
>> Cc: mpls@lists.ietf.org; pwe3@ietf.org
>> Subject: Re: [PWE3] New Liaison Statement,"Response to PWE3 and MPLS
>> WG concerns with G.8110.1 Amendment 1"
>>
>> The IETF response to our liaison of
>> draft-ietf-pwe3-mpls-transport-00.txt
>> was sent as a word document. To make sure that all members of PWE3  
>> are
>
>> able to read it, I have extracted the substantive text as ASCII.
>>
>> I have major concerns about the assumption of disjoint operation  
>> since
>
>> I cannot see how the T-MPLS protocol prevents this.
>>
>> I request WG input on how to respond to this liaison.
>>
>> - Stewart
>>
>>
>> _______________________________________________
>> mpls mailing list
>> mpls@lists.ietf.org
>> https://www1.ietf.org/mailman/listinfo/mpls
>>
>>
>> _______________________________________________
>> pwe3 mailing list
>> pwe3@ietf.org
>> https://www1.ietf.org/mailman/listinfo/pwe3
>>
>
>
> _______________________________________________
> mpls mailing list
> mpls@lists.ietf.org
> https://www1.ietf.org/mailman/listinfo/mpls


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



From pwe3-bounces@ietf.org Fri Jun 29 15:32:03 2007
Return-path: <pwe3-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I4MCG-0008B8-Fo; Fri, 29 Jun 2007 15:32:00 -0400
Received: from pwe3 by megatron.ietf.org with local (Exim 4.43)
	id 1I4MCF-0008Ae-2X
	for pwe3-confirm+ok@megatron.ietf.org; Fri, 29 Jun 2007 15:31:59 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I4MCE-00089l-Of; Fri, 29 Jun 2007 15:31:58 -0400
Received: from winger.mail.pas.earthlink.net ([207.217.120.100])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1I4MBv-0006ex-MB; Fri, 29 Jun 2007 15:31:58 -0400
Received: from [207.69.182.216] (helo=[207.69.182.216])
	by winger.mail.pas.earthlink.net with asmtp (Exim 4.34)
	id 1I4M19-0003uO-TZ; Fri, 29 Jun 2007 14:20:32 -0500
In-Reply-To: <D849FF14B5E0B142ADFC9A92C509E9BB010E7EEA@tlv2.iprad.local>
References: <D849FF14B5E0B142ADFC9A92C509E9BB010E7EEA@tlv2.iprad.local>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <390CD596-7947-44E3-8735-3D9D62AA7919@gmail.com>
Content-Transfer-Encoding: 7bit
From: Phil Bedard <bedard.phil@gmail.com>
Subject: Re: [mpls] RE: [PWE3] New Liaison Statement,
	"Response to PWE3 and MPLS WG concerns with G.8110.1 Amendment 1"
Date: Fri, 29 Jun 2007 15:20:30 -0400
To: "Sasha Vainshtein" <Sasha@AXERRA.com>
X-Mailer: Apple Mail (2.752.3)
X-ELNK-Trace: eb8212ccd47acc465a752383f42c064374bf435c0eb9d47825234a3a243c1acbb96e1c2c9e3827efc3f3c0be03b52a5f350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 207.69.182.216
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e5ba305d0e64821bf3d8bc5d3bb07228
Cc: mpls@lists.ietf.org, Italo Busi <Italo.Busi@alcatel-lucent.it>,
	Yaakov Stein <yaakov_s@rad.com>, pwe3@ietf.org, 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>
Errors-To: pwe3-bounces@ietf.org

Excuse me if this has already been covered, I've just read some of  
the current messages and to me it seems the definition of  
"interworking" needs to be better defined in these discussions.   To  
me interworking is a translation function on the same data plane, not  
one framing technology encapsulating another.   The connection- 
oriented specifications of T-MPLS seem to not allow its frames to be  
translated and carried on an IP/MPLS network without special  
treatment, unless I'm mistaken.   So there really isn't  
"interworking".    The fact they use the same forwarding plane,  
packet format, and codepoints seems to confuse things.   If they are  
truly distinct protocols that serve different purposes, as the T-MPLS  
advocates seem to say, then clear separation needs to be made between  
the two.

Phil


On Jun 29, 2007, at 1:19 PM, Sasha Vainshtein wrot

>
> [Sasha] I am completely confused now. Are MPLS and T-MPLS supposed to
> interwork, or not?
> Please note also that the current designs for, say P2MP (multicast)  
> LSPs
> use (to some extent) mapping of the protocol numbers to label spaces.
> Hence using a separate protocol number for T-MPLS would be in line  
> with
> the common trend.
>




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



