The MPLS WG Archive

Cell Relay Retreat>MPLS WG Archive>month:2007-Mar> msg00288



[Date Prev][Date Next][Thread Prev][Thread Next]  
  [Date Index][Thread Index][Author Index][Subject Index]

[mpls] RE: [PWE3] Fwd: I-DACTION:draft-bryant-pwe3-mpls-transport-00.txt

  • From: "O'Connor, Don" <don.oconnor@us.fujitsu.com>
  • Date: Thu, 22 Mar 2007 10:52:23 -0500
  • Cc: mpls@ietf.org, rcallon@juniper.net, townsley@cisco.com
  • Thread-Index: AcdsZUCghmaL5W/bRlu7uwId1X/8NgALwHMw
  • Thread-Topic: [PWE3] Fwd: I-D ACTION:draft-bryant-pwe3-mpls-transport-00.txt
  • X-IronPort-AV: i="4.14,315,1170655200"; d="scan'208"; a="70751469:sNHT24437568"
  • X-MIME-Autoconverted: from quoted-printable to 8bit by cell.onecall.net id l2MG1Is07371

I do not support draft-bryant-pwe3-mpls-transport-00.txt as a WG draft for the following reasons

1) Transport MPLS as pursued by ITU encompasses functionality that overlaps work in multiple IETF WGs. A minimum subset is PWE3 and MPLS. Work in CCAMP is also most probably relevant. Without companion work in the MPLS WG on a T-MPLS implementation profile, draft-bryant-pwe3-mpls-transport-00.txt serves no useful purpose

I suggest that a first necessary step is that the appropriate Area Directors consider whether or not they want to take on the entire task of generating a complete Transport MPLS implementation profile based on current RFC / ID / extensions and doing it right and comprehensively. WG charters should be updated appropriately

In its present form draft-bryant-pwe3-mpls-transport-00.txt is an incomplete attempt at addressing a portion of what ITU SG 15 and ITU SG 13 are pursuing for Transport MPLS

If IETF leadership decides that they would like to pursue a comprehensive Transport MPLS implementation profile, it should be done in cooperation and coordination with leadership in ITU SG 15 and SG 13. I would support such as effort if it is done in this context. To date draft-bryant-pwe3-transport-00.txt does not fall into this category

2) draft-bryant-pwe3-mpls-transport-00.txt does not adequately address Transport MPLS OAM and Protection Switching requirements

2A) Protection Switching - linear protection switching coordinated by an appropriate OAM protocol is required. It is necessary to meet the requirements of G.8131

2B) Current pseudowire VCCC OAM lacks - Maintenance Entity Levels, MEP / MIP, AIS / RDI, PM measurement. It is necessary to provide the functionality being developed for Y.17tom

Regards

Don


-----Original Message-----
From: Danny McPherson [mailto:danny@tcb.net]
Sent: Thursday, March 22, 2007 4:31 AM
To: pwe3 ((((((((E-mail)))))))) WG
Subject: [PWE3] Fwd: I-D ACTION:draft-bryant-pwe3-mpls-transport-00.txt 


	
Folks,
As discussed in the meeting, I'd like to solicit WG feedback on
adopting this as a WG document.   If you're in favor or opposed
to adopting this please speak up now.

-danny


Begin forwarded message:

> From: Internet-Drafts@ietf.org
> Date: October 16, 2006 1:50:01 PM MDT
> To: i-d-announce@ietf.org
> Subject: I-D ACTION:draft-bryant-pwe3-mpls-transport-00.txt
> Reply-To: internet-drafts@ietf.org
>
> A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
>
>
> 	Title		: Application of PWE3 to MPLS Transport Networks
> 	Author(s)	: S. Bryant
> 	Filename	: draft-bryant-pwe3-mpls-transport-00.txt
> 	Pages		: 13
> 	Date		: 2006-10-16
> 	
>   A need has been identified to identify a strict subset of the PWE3
>   over MPLS pseudowire functionality suitable for the construction of
>   transport networks. This draft describes the IETF recommended  
> profile
>   for such cases. This document describes the IETF-recommended profile
>   for such a configuration. In particular the profile of an RFC4448
>   PWE3 Ethernet pseudowire that can be used to address these
>   requirements is described.
>
>
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-bryant-pwe3-mpls- 
> transport-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-bryant-pwe3-mpls-transport-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-bryant-pwe3-mpls-transport-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.
> Content-Type: text/plain
> Content-ID: <2006-10-16113713.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

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