
From pwe3-bounces@ietf.org  Mon Feb  2 14:15:04 2009
Return-Path: <pwe3-bounces@ietf.org>
X-Original-To: pwe3-archive@megatron.ietf.org
Delivered-To: ietfarch-pwe3-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4052A28C163; Mon,  2 Feb 2009 14:15:04 -0800 (PST)
X-Original-To: pwe3@ietf.org
Delivered-To: pwe3@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0) id 601EB3A6BCD; Mon,  2 Feb 2009 14:15:01 -0800 (PST)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20090202221501.601EB3A6BCD@core3.amsl.com>
Date: Mon,  2 Feb 2009 14:15:01 -0800 (PST)
Cc: pwe3@ietf.org
Subject: [PWE3] I-D ACTION:draft-ietf-pwe3-fc-flow-00.txt
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/pwe3>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=subscribe>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org

--NextPart

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

	Title		: Reliable Fibre Channel Transport Over MPLS Networks
	Author(s)	: M. Roth, R. Solomon, M. Tsurusawa
	Filename	: draft-ietf-pwe3-fc-flow-00.txt
	Pages		: 30
	Date		: 2009-1-15
	
   A Fibre Channel pseudowire (PW) is used to carry Fibre Channel frames 
   over an MPLS network. This enables service providers to offer 
   "emulated" Fibre Channel services over existing MPLS networks. This 
   document specifies the mechanisms controlling the reliable transport 
   of Fibre Channel PW over MPLS networks. The encapsulation of Fibre 
   Channel PDUs within a pseudowire and the procedures for using a PW to 
   provide a Fibre Channel service are specified in [FC-encap]. 

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-pwe3-fc-flow-00.txt

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

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

--NextPart
Content-Type: Message/External-body;
	name="draft-ietf-pwe3-fc-flow-00.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2009-2-2140128.I-D@ietf.org>


--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://www.ietf.org/mailman/listinfo/pwe3

--NextPart--


Return-Path: <lmartini@cisco.com>
X-Original-To: pwe3@core3.amsl.com
Delivered-To: pwe3@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E1C3628C11E for <pwe3@core3.amsl.com>; Wed,  4 Feb 2009 09:11:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.229
X-Spam-Level: 
X-Spam-Status: No, score=-2.229 tagged_above=-999 required=5 tests=[AWL=0.370,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HH3mhoXvX5Zd for <pwe3@core3.amsl.com>; Wed,  4 Feb 2009 09:11:39 -0800 (PST)
Received: from napoleon.monoski.com (black.monoski.com [63.227.123.238]) by core3.amsl.com (Postfix) with ESMTP id CF6813A6AFF for <pwe3@ietf.org>; Wed,  4 Feb 2009 09:11:38 -0800 (PST)
Received: from confusion.monoski.com (confusion.monoski.com [209.245.27.2]) (authenticated bits=0) by napoleon.monoski.com (8.13.8/8.13.8) with ESMTP id n14HAgse025583 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 4 Feb 2009 10:10:43 -0700 (MST)
Message-ID: <4989CC12.8060406@cisco.com>
Date: Wed, 04 Feb 2009 10:10:42 -0700
From: Luca Martini <lmartini@cisco.com>
User-Agent: Thunderbird 2.0.0.19 (X11/20081209)
MIME-Version: 1.0
To: "Jin, Lizhong (NSN - CN/Shanghai)" <lizhong.jin@nsn.com>
References: <328B9F5068825A48A4B8422A350B90470ECB1D@CNBEEXC006.nsn-intra.net>
In-Reply-To: <328B9F5068825A48A4B8422A350B90470ECB1D@CNBEEXC006.nsn-intra.net>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Scanned-By: MIMEDefang 2.63 on 209.245.27.1
Cc: yaakov_s@rad.com, matthew.bocci@alcatel-lucent.co.uk, "PWE3 WG \(E-mail\)" <pwe3@ietf.org>, sdelord@uecomm.com.au, mustapha.aissaoui@alcatel-lucent.com
Subject: Re: [PWE3] Comment of draft-ietf-pwe3-ldp-aii-reachability-00
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/pwe3>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 04 Feb 2009 17:11:40 -0000

Jin,
Comments below.


Jin, Lizhong (NSN - CN/Shanghai) wrote:
> Hi Simon and all:
> I read the draft-ietf-pwe3-ldp-aii-reachability-00, and have following 
> comments.
> Because LDP does not have the capability of path selection, which is 
> quite different with OSPF and BGP. So some problem will met when using 
> LDP to distribute AII reachability information. Although it has been 
> stated in the draft that: this document does not define a routing 
> protocol, but we also need to consider the following scenario.
> Section 4.1.2, line 381:
> "It MAY also re-advertise those addresses using any another supported 
> dynamic MS-PW routing mechanism."
> Does "dynamic MS-PW routing mechanism" also include LDP capability 
> described in this draft or not? If it does not include, then that 
> means only one LDP session can be supported. If it does include, the 
> S-PE will also re-advertise the AII information to next T-LDP 
> neighbor, and will course the following problem.
> If an S-PE receiving a address list TLV contain one AII address, S-PE 
> has already this L2 PW forwarding entry but with different nexthop, 
> what S-PE's behavior in this situation?
> -------
> --|S-PE2|--
> / ------- \
> /------/ \------\
> ------- ------- ------- -------
> |T-PE1|------|S-PE1| |S-PE3|------|T-PE2|
> ------- ------- ------- -------
> \------\ /------/
> \ ------- /
> --|S-PE4|--
> -------
> Please see the above scenario, the sessions between PEs are T-LDP, and 
> T-PE1 will send Address message to S-PE1. Then S-PE1 will send the 
> address message to S-PE2 and S-PE4. S-PE3 will receive two same 
> address message, one is from S-PE2, the other is from S-PE4. Then 
> S-PE2 needs to select which address message should be used for L2 PW 
> forwarding entry.
> There are following proposals:
> 1. S-PE will use the first received Address message. But this may 
> course non-optimal S-PE next-hop.
> 2. S-PE need the IP routing information to select the S-PE next-hop. 
> S-PE3 will lookup the IP routing table, the S-PE which has lower cost 
> from S-PE3 to S-PE next-hop will be selected, if the cost is the same, 
> then the first received address message can be selected.
> 3. S-PE will install both L2 PW forwarding entries, and let MS-PW 
> signaling mechanism select the special S-PE next-hop (MS-PW section 
> 7.2.3).
> For proposal 3, MS-PW signaling mechanism will evaluate PW BW and PSN 
> tunnel resources, which can determine the S-PE next-hop. But this 
> mechanism is complicated, and the MS-PW signaling mechanism should be 
> modified. I prefer proposal 2, it is simple and seems reasonable, but 
> not always optimal if consider BW and PSN tunnel.

This mechanism is not intended for S-PEs to advertise information to 
each other. Perhaps that is not clear in the document.
S-PE1 cannot send the T-PE1 address to S-PE2 using LDP , because it is 
not a local connected address. It will need to send the T-PE1 address 
using a routing protocol like BGP or OSPF.
The only routes that an S-PE can redistribute is connected (local) 
routes and a "default" route as an exception. I think this needs to be 
made clear in the document.


Thanks.
Luca




Return-Path: <root@core3.amsl.com>
X-Original-To: pwe3@ietf.org
Delivered-To: pwe3@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0) id 742693A6A20; Wed,  4 Feb 2009 14:45:02 -0800 (PST)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20090204224502.742693A6A20@core3.amsl.com>
Date: Wed,  4 Feb 2009 14:45:02 -0800 (PST)
Cc: pwe3@ietf.org
Subject: [PWE3] I-D Action:draft-ietf-pwe3-segmented-pw-10.txt
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/pwe3>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 04 Feb 2009 22:45:02 -0000

--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           : Segmented Pseudo Wire
	Author(s)       : L. Martini, et al.
	Filename        : draft-ietf-pwe3-segmented-pw-10.txt
	Pages           : 42
	Date            : 2009-02-04

This document describes how to connect pseudowires (PW) between two
distinct PW control planes or PSN domains. The PW control planes may
belong to independent autonomous systems, or the PSN technology is
heterogeneous, or a PW might need to be aggregated at a specific PSN
point. The PW packet data units are simply switched from one PW to
another without changing the PW payload.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-pwe3-segmented-pw-10.txt

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

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

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

Content-Type: text/plain
Content-ID: <2009-02-04143518.I-D@ietf.org>


--NextPart--


Return-Path: <lizhong.jin@nsn.com>
X-Original-To: pwe3@core3.amsl.com
Delivered-To: pwe3@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3A9823A67F9 for <pwe3@core3.amsl.com>; Wed,  4 Feb 2009 17:55:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.299
X-Spam-Level: 
X-Spam-Status: No, score=-4.299 tagged_above=-999 required=5 tests=[AWL=-1.700, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ijIrYLLTrnyH for <pwe3@core3.amsl.com>; Wed,  4 Feb 2009 17:55:57 -0800 (PST)
Received: from demumfd002.nsn-inter.net (demumfd002.nsn-inter.net [217.115.75.234]) by core3.amsl.com (Postfix) with ESMTP id 041643A67F2 for <pwe3@ietf.org>; Wed,  4 Feb 2009 17:55:56 -0800 (PST)
Received: from demuprx016.emea.nsn-intra.net ([10.150.129.55]) by demumfd002.nsn-inter.net (8.12.11.20060308/8.12.11) with ESMTP id n151tN5d030362 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Thu, 5 Feb 2009 02:55:24 +0100
Received: from demuexc022.nsn-intra.net (demuexc022.nsn-intra.net [10.150.128.35]) by demuprx016.emea.nsn-intra.net (8.12.11.20060308/8.12.11) with ESMTP id n151tJkb022131; Thu, 5 Feb 2009 02:55:23 +0100
Received: from CNBEEXC006.nsn-intra.net ([10.159.192.11]) by demuexc022.nsn-intra.net with Microsoft SMTPSVC(6.0.3790.3959);  Thu, 5 Feb 2009 02:54:54 +0100
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
Date: Thu, 5 Feb 2009 09:54:09 +0800
Message-ID: <328B9F5068825A48A4B8422A350B90470ECC3F@CNBEEXC006.nsn-intra.net>
In-Reply-To: <4989CC12.8060406@cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [PWE3] Comment of draft-ietf-pwe3-ldp-aii-reachability-00
Thread-Index: AcmG652b9jmLTJ0HTbuucYIcZF2EvQARgq9g
References: <328B9F5068825A48A4B8422A350B90470ECB1D@CNBEEXC006.nsn-intra.net> <4989CC12.8060406@cisco.com>
From: "Jin, Lizhong (NSN - CN/Shanghai)" <lizhong.jin@nsn.com>
To: "ext Luca Martini" <lmartini@cisco.com>
X-OriginalArrivalTime: 05 Feb 2009 01:54:54.0599 (UTC) FILETIME=[BD9CD170:01C98734]
Cc: yaakov_s@rad.com, matthew.bocci@alcatel-lucent.co.uk, "PWE3 WG \(E-mail\)" <pwe3@ietf.org>, sdelord@uecomm.com.au, mustapha.aissaoui@alcatel-lucent.com
Subject: Re: [PWE3] Comment of draft-ietf-pwe3-ldp-aii-reachability-00
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/pwe3>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 05 Feb 2009 01:55:58 -0000

Hi Luca:
I get your meaning. Thank your very much.

Best Regards
Lizhong Jin


-----Original Message-----
From: ext Luca Martini [mailto:lmartini@cisco.com]=20
Sent: Thursday, February 05, 2009 1:11
To: Jin, Lizhong (NSN - CN/Shanghai)
Cc: sdelord@uecomm.com.au; frederic.jounay@orange-ftgroup.com;
philippe.niger@orange-ftgroup.com; mustapha.aissaoui@alcatel-lucent.com;
matthew.bocci@alcatel-lucent.co.uk; yaakov_s@rad.com;
caowayne@huawei.com; PWE3 WG (E-mail)
Subject: Re: [PWE3] Comment of draft-ietf-pwe3-ldp-aii-reachability-00

Jin,
Comments below.


Jin, Lizhong (NSN - CN/Shanghai) wrote:
> Hi Simon and all:
> I read the draft-ietf-pwe3-ldp-aii-reachability-00, and have following

> comments.
> Because LDP does not have the capability of path selection, which is=20
> quite different with OSPF and BGP. So some problem will met when using

> LDP to distribute AII reachability information. Although it has been=20
> stated in the draft that: this document does not define a routing=20
> protocol, but we also need to consider the following scenario.
> Section 4.1.2, line 381:
> "It MAY also re-advertise those addresses using any another supported=20
> dynamic MS-PW routing mechanism."
> Does "dynamic MS-PW routing mechanism" also include LDP capability=20
> described in this draft or not? If it does not include, then that=20
> means only one LDP session can be supported. If it does include, the=20
> S-PE will also re-advertise the AII information to next T-LDP=20
> neighbor, and will course the following problem.
> If an S-PE receiving a address list TLV contain one AII address, S-PE=20
> has already this L2 PW forwarding entry but with different nexthop,=20
> what S-PE's behavior in this situation?
> -------
> --|S-PE2|--
> / ------- \
> /------/ \------\
> ------- ------- ------- -------
> |T-PE1|------|S-PE1| |S-PE3|------|T-PE2|
> ------- ------- ------- -------
> \------\ /------/
> \ ------- /
> --|S-PE4|--
> -------
> Please see the above scenario, the sessions between PEs are T-LDP, and

> T-PE1 will send Address message to S-PE1. Then S-PE1 will send the=20
> address message to S-PE2 and S-PE4. S-PE3 will receive two same=20
> address message, one is from S-PE2, the other is from S-PE4. Then=20
> S-PE2 needs to select which address message should be used for L2 PW=20
> forwarding entry.
> There are following proposals:
> 1. S-PE will use the first received Address message. But this may=20
> course non-optimal S-PE next-hop.
> 2. S-PE need the IP routing information to select the S-PE next-hop.=20
> S-PE3 will lookup the IP routing table, the S-PE which has lower cost=20
> from S-PE3 to S-PE next-hop will be selected, if the cost is the same,

> then the first received address message can be selected.
> 3. S-PE will install both L2 PW forwarding entries, and let MS-PW=20
> signaling mechanism select the special S-PE next-hop (MS-PW section=20
> 7.2.3).
> For proposal 3, MS-PW signaling mechanism will evaluate PW BW and PSN=20
> tunnel resources, which can determine the S-PE next-hop. But this=20
> mechanism is complicated, and the MS-PW signaling mechanism should be=20
> modified. I prefer proposal 2, it is simple and seems reasonable, but=20
> not always optimal if consider BW and PSN tunnel.

This mechanism is not intended for S-PEs to advertise information to=20
each other. Perhaps that is not clear in the document.
S-PE1 cannot send the T-PE1 address to S-PE2 using LDP , because it is=20
not a local connected address. It will need to send the T-PE1 address=20
using a routing protocol like BGP or OSPF.
The only routes that an S-PE can redistribute is connected (local)=20
routes and a "default" route as an exception. I think this needs to be=20
made clear in the document.


Thanks.
Luca




Return-Path: <frederic.jounay@orange-ftgroup.com>
X-Original-To: pwe3@core3.amsl.com
Delivered-To: pwe3@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B819C3A67B6 for <pwe3@core3.amsl.com>; Fri,  6 Feb 2009 00:37:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.126
X-Spam-Level: 
X-Spam-Status: No, score=-3.126 tagged_above=-999 required=5 tests=[AWL=0.123,  BAYES_00=-2.599, HELO_EQ_FR=0.35, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CZBnOF5vQfSJ for <pwe3@core3.amsl.com>; Fri,  6 Feb 2009 00:37:37 -0800 (PST)
Received: from p-mail1.rd.francetelecom.com (p-mail1.rd.francetelecom.com [195.101.245.15]) by core3.amsl.com (Postfix) with ESMTP id 214573A6B85 for <pwe3@ietf.org>; Fri,  6 Feb 2009 00:37:36 -0800 (PST)
Received: from FTRDMEL2.rd.francetelecom.fr ([10.193.117.153]) by ftrdsmtp1.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.3959);  Fri, 6 Feb 2009 09:37:33 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Fri, 6 Feb 2009 09:37:32 +0100
Message-ID: <8AA97249241F7148BE6D3D8B93D83F5A14AA55A9@ftrdmel2>
In-Reply-To: <4989CC12.8060406@cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [PWE3] Comment of draft-ietf-pwe3-ldp-aii-reachability-00
Thread-Index: AcmG65/HN69R+2X1S1iIzx6b4EG5cwBSTJzw
References: <328B9F5068825A48A4B8422A350B90470ECB1D@CNBEEXC006.nsn-intra.net> <4989CC12.8060406@cisco.com>
From: <frederic.jounay@orange-ftgroup.com>
To: <lmartini@cisco.com>, <lizhong.jin@nsn.com>
X-OriginalArrivalTime: 06 Feb 2009 08:37:33.0129 (UTC) FILETIME=[27A1B390:01C98836]
Cc: yaakov_s@rad.com, matthew.bocci@alcatel-lucent.co.uk, pwe3@ietf.org, sdelord@uecomm.com.au, mustapha.aissaoui@alcatel-lucent.com
Subject: Re: [PWE3] Comment of draft-ietf-pwe3-ldp-aii-reachability-00
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/pwe3>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 06 Feb 2009 08:37:38 -0000

Lizhong, Luca,

Please find hereafter the changes proposed to clarify the point

An S-PE receiving an address list TLV containing one or more AII =
addresses should install those addresses in its local PW routing table. =
It MAY also re-advertise those addresses using any another supported =
dynamic MS-PW routing mechanism.
=3D> =20
An S-PE receiving an address list TLV containing one or more AII =
addresses should install those addresses in its local PW routing table. =
It MAY also re-advertise those addresses using any another supported =
dynamic MS-PW routing protocol like BGP [BGP AD] or OSPF [OSPF MS-PW]. =
An S-PE cannot send the attached T-PE address to other S-PE using T-LDP =
, because it is not a local connected address. The only routes that an =
S-PE MAY redistribute using T-LDP is connected (local) routes and a =
"default" route as an exception.=20

Let me know if this is still confusing, if not I 'll update the draft.

thanks,
Fred=20

-----Message d'origine-----
De : Luca Martini [mailto:lmartini@cisco.com]=20
Envoy=E9 : mercredi 4 f=E9vrier 2009 18:11
=C0 : Jin, Lizhong (NSN - CN/Shanghai)
Cc : sdelord@uecomm.com.au; JOUNAY Frederic RD-RESA-LAN; NIGER Philippe =
RD-RESA-LAN; mustapha.aissaoui@alcatel-lucent.com; =
matthew.bocci@alcatel-lucent.co.uk; yaakov_s@rad.com; =
caowayne@huawei.com; PWE3 WG (E-mail)
Objet : Re: [PWE3] Comment of draft-ietf-pwe3-ldp-aii-reachability-00

Jin,
Comments below.


Jin, Lizhong (NSN - CN/Shanghai) wrote:
> Hi Simon and all:
> I read the draft-ietf-pwe3-ldp-aii-reachability-00, and have following =

> comments.
> Because LDP does not have the capability of path selection, which is=20
> quite different with OSPF and BGP. So some problem will met when using =

> LDP to distribute AII reachability information. Although it has been=20
> stated in the draft that: this document does not define a routing=20
> protocol, but we also need to consider the following scenario.
> Section 4.1.2, line 381:
> "It MAY also re-advertise those addresses using any another supported=20
> dynamic MS-PW routing mechanism."
> Does "dynamic MS-PW routing mechanism" also include LDP capability=20
> described in this draft or not? If it does not include, then that=20
> means only one LDP session can be supported. If it does include, the=20
> S-PE will also re-advertise the AII information to next T-LDP=20
> neighbor, and will course the following problem.
> If an S-PE receiving a address list TLV contain one AII address, S-PE=20
> has already this L2 PW forwarding entry but with different nexthop,=20
> what S-PE's behavior in this situation?
> -------
> --|S-PE2|--
> / ------- \
> /------/ \------\
> ------- ------- ------- -------
> |T-PE1|------|S-PE1| |S-PE3|------|T-PE2|
> ------- ------- ------- -------
> \------\ /------/
> \ ------- /
> --|S-PE4|--
> -------
> Please see the above scenario, the sessions between PEs are T-LDP, and
> T-PE1 will send Address message to S-PE1. Then S-PE1 will send the=20
> address message to S-PE2 and S-PE4. S-PE3 will receive two same=20
> address message, one is from S-PE2, the other is from S-PE4. Then
> S-PE2 needs to select which address message should be used for L2 PW=20
> forwarding entry.
> There are following proposals:
> 1. S-PE will use the first received Address message. But this may=20
> course non-optimal S-PE next-hop.
> 2. S-PE need the IP routing information to select the S-PE next-hop.=20
> S-PE3 will lookup the IP routing table, the S-PE which has lower cost=20
> from S-PE3 to S-PE next-hop will be selected, if the cost is the same, =

> then the first received address message can be selected.
> 3. S-PE will install both L2 PW forwarding entries, and let MS-PW=20
> signaling mechanism select the special S-PE next-hop (MS-PW section=20
> 7.2.3).
> For proposal 3, MS-PW signaling mechanism will evaluate PW BW and PSN=20
> tunnel resources, which can determine the S-PE next-hop. But this=20
> mechanism is complicated, and the MS-PW signaling mechanism should be=20
> modified. I prefer proposal 2, it is simple and seems reasonable, but=20
> not always optimal if consider BW and PSN tunnel.

This mechanism is not intended for S-PEs to advertise information to =
each other. Perhaps that is not clear in the document.
S-PE1 cannot send the T-PE1 address to S-PE2 using LDP , because it is =
not a local connected address. It will need to send the T-PE1 address =
using a routing protocol like BGP or OSPF.
The only routes that an S-PE can redistribute is connected (local) =
routes and a "default" route as an exception. I think this needs to be =
made clear in the document.


Thanks.
Luca




Return-Path: <lizhong.jin@nsn.com>
X-Original-To: pwe3@core3.amsl.com
Delivered-To: pwe3@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 49A4B3A6B70 for <pwe3@core3.amsl.com>; Fri,  6 Feb 2009 00:48:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.449
X-Spam-Level: 
X-Spam-Status: No, score=-5.449 tagged_above=-999 required=5 tests=[AWL=1.150,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ktrrk0sOY-BO for <pwe3@core3.amsl.com>; Fri,  6 Feb 2009 00:48:53 -0800 (PST)
Received: from demumfd001.nsn-inter.net (demumfd001.nsn-inter.net [217.115.75.233]) by core3.amsl.com (Postfix) with ESMTP id D4AA83A68F3 for <pwe3@ietf.org>; Fri,  6 Feb 2009 00:48:52 -0800 (PST)
Received: from demuprx016.emea.nsn-intra.net ([10.150.129.55]) by demumfd001.nsn-inter.net (8.12.11.20060308/8.12.11) with ESMTP id n168met6024946 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Fri, 6 Feb 2009 09:48:40 +0100
Received: from demuexc024.nsn-intra.net (demuexc024.nsn-intra.net [10.159.32.11]) by demuprx016.emea.nsn-intra.net (8.12.11.20060308/8.12.11) with ESMTP id n168me2n003460; Fri, 6 Feb 2009 09:48:40 +0100
Received: from CNBEEXC006.nsn-intra.net ([10.159.192.11]) by demuexc024.nsn-intra.net with Microsoft SMTPSVC(6.0.3790.3959);  Fri, 6 Feb 2009 09:48:39 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Fri, 6 Feb 2009 16:48:36 +0800
Message-ID: <328B9F5068825A48A4B8422A350B90471143EB@CNBEEXC006.nsn-intra.net>
In-Reply-To: <8AA97249241F7148BE6D3D8B93D83F5A14AA55A9@ftrdmel2>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [PWE3] Comment of draft-ietf-pwe3-ldp-aii-reachability-00
Thread-Index: AcmG65/HN69R+2X1S1iIzx6b4EG5cwBSTJzwAACxKuA=
References: <328B9F5068825A48A4B8422A350B90470ECB1D@CNBEEXC006.nsn-intra.net> <4989CC12.8060406@cisco.com> <8AA97249241F7148BE6D3D8B93D83F5A14AA55A9@ftrdmel2>
From: "Jin, Lizhong (NSN - CN/Shanghai)" <lizhong.jin@nsn.com>
To: <frederic.jounay@orange-ftgroup.com>, <lmartini@cisco.com>
X-OriginalArrivalTime: 06 Feb 2009 08:48:39.0882 (UTC) FILETIME=[B50C22A0:01C98837]
Cc: yaakov_s@rad.com, matthew.bocci@alcatel-lucent.co.uk, pwe3@ietf.org, sdelord@uecomm.com.au, mustapha.aissaoui@alcatel-lucent.com
Subject: Re: [PWE3] Comment of draft-ietf-pwe3-ldp-aii-reachability-00
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/pwe3>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 06 Feb 2009 08:48:54 -0000

Hi Fred:
The change is clear now, thank you.

Best Regards
Lizhong Jin


-----Original Message-----
From: ext frederic.jounay@orange-ftgroup.com =
[mailto:frederic.jounay@orange-ftgroup.com]=20
Sent: Friday, February 06, 2009 16:38
To: lmartini@cisco.com; Jin, Lizhong (NSN - CN/Shanghai)
Cc: sdelord@uecomm.com.au; philippe.niger@orange-ftgroup.com; =
mustapha.aissaoui@alcatel-lucent.com; =
matthew.bocci@alcatel-lucent.co.uk; yaakov_s@rad.com; =
caowayne@huawei.com; pwe3@ietf.org
Subject: RE: [PWE3] Comment of draft-ietf-pwe3-ldp-aii-reachability-00

Lizhong, Luca,

Please find hereafter the changes proposed to clarify the point

An S-PE receiving an address list TLV containing one or more AII =
addresses should install those addresses in its local PW routing table. =
It MAY also re-advertise those addresses using any another supported =
dynamic MS-PW routing mechanism.
=3D> =20
An S-PE receiving an address list TLV containing one or more AII =
addresses should install those addresses in its local PW routing table. =
It MAY also re-advertise those addresses using any another supported =
dynamic MS-PW routing protocol like BGP [BGP AD] or OSPF [OSPF MS-PW]. =
An S-PE cannot send the attached T-PE address to other S-PE using T-LDP =
, because it is not a local connected address. The only routes that an =
S-PE MAY redistribute using T-LDP is connected (local) routes and a =
"default" route as an exception.=20

Let me know if this is still confusing, if not I 'll update the draft.

thanks,
Fred=20

-----Message d'origine-----
De : Luca Martini [mailto:lmartini@cisco.com]=20
Envoy=E9 : mercredi 4 f=E9vrier 2009 18:11
=C0 : Jin, Lizhong (NSN - CN/Shanghai)
Cc : sdelord@uecomm.com.au; JOUNAY Frederic RD-RESA-LAN; NIGER Philippe =
RD-RESA-LAN; mustapha.aissaoui@alcatel-lucent.com; =
matthew.bocci@alcatel-lucent.co.uk; yaakov_s@rad.com; =
caowayne@huawei.com; PWE3 WG (E-mail)
Objet : Re: [PWE3] Comment of draft-ietf-pwe3-ldp-aii-reachability-00

Jin,
Comments below.


Jin, Lizhong (NSN - CN/Shanghai) wrote:
> Hi Simon and all:
> I read the draft-ietf-pwe3-ldp-aii-reachability-00, and have following =

> comments.
> Because LDP does not have the capability of path selection, which is=20
> quite different with OSPF and BGP. So some problem will met when using =

> LDP to distribute AII reachability information. Although it has been=20
> stated in the draft that: this document does not define a routing=20
> protocol, but we also need to consider the following scenario.
> Section 4.1.2, line 381:
> "It MAY also re-advertise those addresses using any another supported=20
> dynamic MS-PW routing mechanism."
> Does "dynamic MS-PW routing mechanism" also include LDP capability=20
> described in this draft or not? If it does not include, then that=20
> means only one LDP session can be supported. If it does include, the=20
> S-PE will also re-advertise the AII information to next T-LDP=20
> neighbor, and will course the following problem.
> If an S-PE receiving a address list TLV contain one AII address, S-PE=20
> has already this L2 PW forwarding entry but with different nexthop,=20
> what S-PE's behavior in this situation?
> -------
> --|S-PE2|--
> / ------- \
> /------/ \------\
> ------- ------- ------- -------
> |T-PE1|------|S-PE1| |S-PE3|------|T-PE2|
> ------- ------- ------- -------
> \------\ /------/
> \ ------- /
> --|S-PE4|--
> -------
> Please see the above scenario, the sessions between PEs are T-LDP, and
> T-PE1 will send Address message to S-PE1. Then S-PE1 will send the=20
> address message to S-PE2 and S-PE4. S-PE3 will receive two same=20
> address message, one is from S-PE2, the other is from S-PE4. Then
> S-PE2 needs to select which address message should be used for L2 PW=20
> forwarding entry.
> There are following proposals:
> 1. S-PE will use the first received Address message. But this may=20
> course non-optimal S-PE next-hop.
> 2. S-PE need the IP routing information to select the S-PE next-hop.=20
> S-PE3 will lookup the IP routing table, the S-PE which has lower cost=20
> from S-PE3 to S-PE next-hop will be selected, if the cost is the same, =

> then the first received address message can be selected.
> 3. S-PE will install both L2 PW forwarding entries, and let MS-PW=20
> signaling mechanism select the special S-PE next-hop (MS-PW section=20
> 7.2.3).
> For proposal 3, MS-PW signaling mechanism will evaluate PW BW and PSN=20
> tunnel resources, which can determine the S-PE next-hop. But this=20
> mechanism is complicated, and the MS-PW signaling mechanism should be=20
> modified. I prefer proposal 2, it is simple and seems reasonable, but=20
> not always optimal if consider BW and PSN tunnel.

This mechanism is not intended for S-PEs to advertise information to =
each other. Perhaps that is not clear in the document.
S-PE1 cannot send the T-PE1 address to S-PE2 using LDP , because it is =
not a local connected address. It will need to send the T-PE1 address =
using a routing protocol like BGP or OSPF.
The only routes that an S-PE can redistribute is connected (local) =
routes and a "default" route as an exception. I think this needs to be =
made clear in the document.


Thanks.
Luca




Return-Path: <maheshsc@hcl.in>
X-Original-To: pwe3@core3.amsl.com
Delivered-To: pwe3@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 35E3D28C0EA for <pwe3@core3.amsl.com>; Fri,  6 Feb 2009 01:18:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.604
X-Spam-Level: 
X-Spam-Status: No, score=-1.604 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RELAY_IS_203=0.994]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GyAhRuRsq9mT for <pwe3@core3.amsl.com>; Fri,  6 Feb 2009 01:18:35 -0800 (PST)
Received: from gws04.hcl.in (gws04.hcl.in [203.105.186.20]) by core3.amsl.com (Postfix) with ESMTP id 5C4CF3A6B8A for <pwe3@ietf.org>; Fri,  6 Feb 2009 01:18:34 -0800 (PST)
Received: from gws04.hcl.in (gws04 [10.249.64.135]) by localhost.hcl.in (Postfix) with ESMTP id 1073F3640E5; Fri,  6 Feb 2009 14:48:33 +0530 (IST)
Received: from chn-egw01-out.corp.hcl.in (unknown [10.249.64.37])by  gws04.hcl.in (Postfix) with ESMTPid AE240364107; Fri,  6 Feb 2009 14:48:32 +0530 (IST)
Received: from CHN-HCLT-EVS02.HCLT.CORP.HCL.IN ([10.101.26.16]) by  chn-egw01-out.corp.hcl.in with Microsoft SMTPSVC(6.0.3790.3959); Fri, 6 Feb 2009 14:48:31 +0530
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C9883B.B36AA4F7"
Date: Fri, 6 Feb 2009 14:47:21 +0530
Message-ID: <B24A3277E6B11B4D9D53D272FE49B7C50276EB8B@CHN-HCLT-EVS02.HCLT.CORP.HCL.IN>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Need clarification on 5086 RFC - Section 5.3
thread-index: AcmIO7c1/CmIGmUoToiHXEZZV06pHQ==
From: "Mahesh Singh C" <maheshsc@hcl.in>
To: "Alexander Vainshtein" <Alexander.Vainshtein@ecitele.com>
X-OriginalArrivalTime: 06 Feb 2009 09:18:31.0852 (UTC)  FILETIME=[E1250EC0:01C9883B]
X-imss-version: 2.053
X-imss-result: Passed
X-imss-scanInfo: M:T L:E SM:1
X-imss-tmaseResult: TT:1 TS:-2.1513 TC:1F TRN:54 TV:5.5.1026(16446.006)
X-imss-scores: Clean:100.00000 C:0 M:0 S:0 R:0
X-imss-settings: Baseline:1 C:1 M:1 S:1 R:1 (0.0000 0.0000)
Cc: pwe3@ietf.org
Subject: [PWE3] Need clarification on 5086 RFC - Section 5.3
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/pwe3>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 06 Feb 2009 09:18:40 -0000

This is a multi-part message in MIME format.

------_=_NextPart_001_01C9883B.B36AA4F7
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable


Hi Sasha,

=20

 I would like to understand the below recommendation in RFC 5086 better=2E

=20

Section 5=2E3 Extending Basic NxDS0 Services with CE Application Signaling

=20

 "Signaling packets SHOULD be carried in a separate dedicated PW=2E

 However, implementations MAY carry them in the same PW as the TDM

 data packets for the basic NxDS0 service=2E  The methods of "pairing"

 the PWs carrying TDM data and signaling packets for the same extended

 NxDS0 service are out of scope of this document=2E"

=20

The first statement specifies SHOULD=2E From my understanding, if we try
to implement as per the next statement the meaning of first statement is
becoming false right?=20

=20

Is it mandatory to send signaling packets in separate PW and data
packets in another separate PW?

=20

OR=20

=20

Can we send signaling packets and data packets in the same PW=2E The
required information in the same PW packets can be distinguished using
its CW=2E Can we implement like this=2E This I believe as per the second
statement above=2E But, since the first statement has SHOULD, I am not
sure on this approach=2E=20

=20

Regards,

Mahesh

=20

=20



DISCLAIMER:
---------------------------------------------------------------------------=
--------------------------------------------

The contents of this e-mail and any attachment(s) are confidential and=
 intended for the named recipient(s) only=2E
It shall not attach any liability on the originator or HCL or its=
 affiliates=2E Any views or opinions presented in=20
this email are solely those of the author and may not necessarily reflect=
 the opinions of HCL or its affiliates=2E
Any form of reproduction, dissemination, copying, disclosure, modification,=
 distribution and / or publication of=20
this message without the prior written consent of the author of this e-mail=
 is strictly prohibited=2E If you have=20
received this email in error please delete it and notify the sender=
 immediately=2E Before opening any mail and=20
attachments please check them for viruses and defect=2E

---------------------------------------------------------------------------=
--------------------------------------------
------_=_NextPart_001_01C9883B.B36AA4F7
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=2Ew3=
=2Eorg/TR/REC-html40">

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">
<style>
<!--
 /* Style Definitions */
 p=2EMsoNormal, li=2EMsoNormal, div=2EMsoNormal
	{margin:0in;
	margin-bottom:=2E0001pt;
	font-size:12=2E0pt;
	font-family:"Times New Roman";}
a:link, span=2EMsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span=2EMsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
p=2EMsoPlainText, li=2EMsoPlainText, div=2EMsoPlainText
	{margin:0in;
	margin-bottom:=2E0001pt;
	font-size:10=2E0pt;
	font-family:"Courier New";}
span=2EEmailStyle17
	{mso-style-type:personal-compose;
	font-family:Arial;
	color:windowtext;}
@page Section1
	{size:8=2E5in 11=2E0in;
	margin:1=2E0in 1=2E25in 1=2E0in 1=2E25in;}
div=2ESection1
	{page:Section1;}
 /* List Definitions */
 @list l0
	{mso-list-id:2099673887;
	mso-list-type:hybrid;
	mso-list-template-ids:729193430 67698705 67698713 67698715 67698703=
 67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
	{mso-level-text:"%1\)";
	mso-level-tab-stop:=2E5in;
	mso-level-number-position:left;
	text-indent:-=2E25in;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
-->
</style>

</head>

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

<div class=3DSection1>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=
=3D'font-size:10=2E0pt;
font-family:Arial'>Hi Sasha,<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=
=3D'font-size:10=2E0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=
=3D'font-size:10=2E0pt;
font-family:Arial'>&nbsp;I would like to understand the below=
 recommendation in
RFC 5086 better=2E<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=
=3D'font-size:10=2E0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DArial><span style=
=3D'font-size:10=2E0pt;
font-family:Arial'>Section 5=2E3 </span></font>Extending Basic NxDS0=
 Services
with CE Application Signaling<o:p></o:p></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=
=3D'font-size:10=2E0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DArial><span style=
=3D'font-size:10=2E0pt;
font-family:Arial'>&nbsp;&#8220;</span></font>Signaling packets SHOULD be
carried in a separate dedicated PW=2E<o:p></o:p></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span style=
=3D'font-size:
10=2E0pt'>&nbsp;However, implementations MAY carry them in the same PW as=
 the TDM<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span style=
=3D'font-size:
10=2E0pt'>&nbsp;data packets for the basic NxDS0 service=2E&nbsp; The=
 methods of
&quot;pairing&quot;<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span style=
=3D'font-size:
10=2E0pt'>&nbsp;the PWs carrying TDM data and signaling packets for the=
 same
extended<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span style=
=3D'font-size:
10=2E0pt'>&nbsp;NxDS0 service are out of scope of this document=
=2E&#8221;<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span style=
=3D'font-size:
10=2E0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span style=
=3D'font-size:
10=2E0pt'>The first statement specifies SHOULD=2E From my understanding, if=
 we try
to implement as per the next statement the meaning of first statement is
becoming false right? <o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span style=
=3D'font-size:
10=2E0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span style=
=3D'font-size:
10=2E0pt'>Is it mandatory to send signaling packets in separate PW and data
packets in another separate PW?<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span style=
=3D'font-size:
10=2E0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span style=
=3D'font-size:
10=2E0pt'>OR <o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span style=
=3D'font-size:
10=2E0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span style=
=3D'font-size:
10=2E0pt'>Can we send signaling packets and data packets in the same PW=2E=
 The
required information in the same PW packets can be distinguished using its=
 CW=2E Can
we implement like this=2E This I believe as per the second statement above=
=2E But,
since the first statement has SHOULD, I am not sure on this approach=2E=
 <o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span style=
=3D'font-size:
10=2E0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span style=
=3D'font-size:
10=2E0pt'>Regards,<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span style=
=3D'font-size:
10=2E0pt'>Mahesh<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=
=3D'font-size:10=2E0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=
=3D'font-size:10=2E0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

</div>

</body>

</html>

<table><tr><td bgcolor=3D#ffffff><font color=3D#000000>DISCLAIMER:<br>
---------------------------------------------------------------------------=
--------------------------------------------<br>
<br>
The contents of this e-mail and any attachment(s) are confidential and=
 intended for the named recipient(s) only=2E<br>
It shall not attach any liability on the originator or HCL or its=
 affiliates=2E Any views or opinions presented in <br>
this email are solely those of the author and may not necessarily reflect=
 the opinions of HCL or its affiliates=2E<br>
Any form of reproduction, dissemination, copying, disclosure, modification,=
 distribution and / or publication of <br>
this message without the prior written consent of the author of this e-mail=
 is strictly prohibited=2E If you have <br>
received this email in error please delete it and notify the sender=
 immediately=2E Before opening any mail and <br>
attachments please check them for viruses and defect=2E<br>
<br>
---------------------------------------------------------------------------=
--------------------------------------------<br>
</font></td></tr></table>
------_=_NextPart_001_01C9883B.B36AA4F7--


Return-Path: <loa@pi.nu>
X-Original-To: pwe3@core3.amsl.com
Delivered-To: pwe3@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 260733A6A71; Fri,  6 Feb 2009 02:11:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.195
X-Spam-Level: 
X-Spam-Status: No, score=-2.195 tagged_above=-999 required=5 tests=[AWL=0.054,  BAYES_00=-2.599, HELO_EQ_SE=0.35]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SKqrQnIVFczd; Fri,  6 Feb 2009 02:11:18 -0800 (PST)
Received: from ns.elverljung.se (ns.elverljung.se [194.68.48.116]) by core3.amsl.com (Postfix) with ESMTP id 4D47F3A692D; Fri,  6 Feb 2009 02:11:18 -0800 (PST)
Received: from [192.168.0.101] (h133n2fls33o883.telia.com [217.208.62.133]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: loa) by ns.elverljung.se (Postfix) with ESMTPSA id E10BA2D81D9; Fri,  6 Feb 2009 11:11:17 +0100 (CET)
Message-ID: <498C0CBC.6050400@pi.nu>
Date: Fri, 06 Feb 2009 11:11:08 +0100
From: Loa Andersson <loa@pi.nu>
User-Agent: Thunderbird 2.0.0.19 (Windows/20081209)
MIME-Version: 1.0
To: mpls-tp@ietf.org, ahmpls-tp@lists.itu.int, ccamp@ops.ietf.org,  mpls@ietf.org, pwe3@ietf.org, l2vpn@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: [PWE3] working group last call on draft-ietf-mpls-tp-requirements-04
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/pwe3>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 06 Feb 2009 10:11:19 -0000

All,

this is to initiate a working group last call for 
draft-ietf-mpls-tp-requirements-04.

This document is one of the key documents for the mpls-tp work,
in particular it is important that the ITU-T mpls-tp ad hoc team
verifies the completeness of the requirements and that we have a
good review form all parties.

Please review and send your comments to the mpls-tp list,
i.e. try to avoid doing a "reply all on this message" !

The working group last call will end on Feb 28, 2009.

/Loa

-- 


Loa Andersson

Sr Strategy and Standards Manager
Ericsson ///                          phone:  +46 8 632 77 14

                                       email:  loa.andersson@ericsson.com
                                               loa.andersson@redback.com
                                               loa@pi.nu




Return-Path: <benjamin.niven-jenkins@bt.com>
X-Original-To: pwe3@core3.amsl.com
Delivered-To: pwe3@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D84CC28C23E; Fri,  6 Feb 2009 07:20:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.493
X-Spam-Level: 
X-Spam-Status: No, score=-3.493 tagged_above=-999 required=5 tests=[AWL=0.106,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pqqjmCCAsT9o; Fri,  6 Feb 2009 07:20:02 -0800 (PST)
Received: from smtp1.smtp.bt.com (smtp1.smtp.bt.com [217.32.164.137]) by core3.amsl.com (Postfix) with ESMTP id 026BB28C243; Fri,  6 Feb 2009 07:20:01 -0800 (PST)
Received: from E03MVB3-UKBR.domain1.systemhost.net ([193.113.197.107]) by smtp1.smtp.bt.com with Microsoft SMTPSVC(6.0.3790.1830);  Fri, 6 Feb 2009 15:20:01 +0000
Received: from 10.215.40.109 ([10.215.40.109]) by E03MVB3-UKBR.domain1.systemhost.net ([193.113.197.60]) via Exchange Front-End Server mail.bt.com ([193.113.197.32]) with Microsoft Exchange Server HTTP-DAV ; Fri,  6 Feb 2009 15:20:00 +0000
User-Agent: Microsoft-Entourage/12.15.0.081119
Date: Fri, 06 Feb 2009 15:20:00 +0000
From: Ben Niven-Jenkins <benjamin.niven-jenkins@bt.com>
To: Loa Andersson <loa@pi.nu>, <mpls-tp@ietf.org>, <ahmpls-tp@lists.itu.int>, <ccamp@ops.ietf.org>, <mpls@ietf.org>, <pwe3@ietf.org>, <l2vpn@ietf.org>
Message-ID: <C5B205A0.115F0%benjamin.niven-jenkins@bt.com>
Thread-Topic: [PWE3] working group last call on draft-ietf-mpls-tp-requirements-04
Thread-Index: AcmIbmBJQHo6yZksOEqy4kWTRLayXQ==
In-Reply-To: <498C0CBC.6050400@pi.nu>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
X-OriginalArrivalTime: 06 Feb 2009 15:20:01.0547 (UTC) FILETIME=[6135DDB0:01C9886E]
Subject: Re: [PWE3] working group last call on draft-ietf-mpls-tp-requirements-04
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/pwe3>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 06 Feb 2009 15:20:04 -0000

Colleagues,

In my rush to get this ready for last call I made an editing mistake,
requirement 30 currently reads

   30  MPLS-TP MUST support unidirectional, bidirectional and co-routed
       bidirectional point-to-point transport paths.

But it should read

   30  MPLS-TP MUST support unidirectional, bidirectional and associated
       bidirectional point-to-point transport paths.

This has no impact in terms of the meaning of the requirement, just an
editing error where I updated the terminology section to reflect discussion
on the MPLS-TP mailing list but forgot to subsequently update the
requirement to use the agreed term.

Ben

On 06/02/2009 10:11, "Loa Andersson" <loa@pi.nu> wrote:

> All,
> 
> this is to initiate a working group last call for
> draft-ietf-mpls-tp-requirements-04.
> 
> This document is one of the key documents for the mpls-tp work,
> in particular it is important that the ITU-T mpls-tp ad hoc team
> verifies the completeness of the requirements and that we have a
> good review form all parties.
> 
> Please review and send your comments to the mpls-tp list,
> i.e. try to avoid doing a "reply all on this message" !
> 
> The working group last call will end on Feb 28, 2009.
> 
> /Loa



Return-Path: <Alexander.Vainshtein@ecitele.com>
X-Original-To: pwe3@core3.amsl.com
Delivered-To: pwe3@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0C5433A694C for <pwe3@core3.amsl.com>; Sat,  7 Feb 2009 02:50:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.552
X-Spam-Level: 
X-Spam-Status: No, score=-2.552 tagged_above=-999 required=5 tests=[AWL=0.046,  BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2IuVEvaCMVpQ for <pwe3@core3.amsl.com>; Sat,  7 Feb 2009 02:50:22 -0800 (PST)
Received: from eci-iron1.ecitele.com (eci-iron1.ecitele.com [147.234.242.117]) by core3.amsl.com (Postfix) with ESMTP id 765B63A67F7 for <pwe3@ietf.org>; Sat,  7 Feb 2009 02:50:21 -0800 (PST)
Received: from unknown (HELO ILPTAM01.ecitele.com) ([147.234.244.44]) by eci-iron1.ecitele.com with ESMTP; 07 Feb 2009 12:58:14 +0200
Received: from ilptexch01.ecitele.com ([172.31.244.40]) by ILPTAM01.ecitele.com with Microsoft SMTPSVC(6.0.3790.3959);  Sat, 7 Feb 2009 12:49:53 +0200
Received: from ILPTMAIL02.ecitele.com ([147.234.244.213]) by ilptexch01.ecitele.com ([172.31.244.40]) with mapi; Sat, 7 Feb 2009 12:49:51 +0200
From: Alexander Vainshtein <Alexander.Vainshtein@ecitele.com>
To: Mahesh Singh C <maheshsc@hcl.in>
Date: Sat, 7 Feb 2009 12:49:51 +0200
Thread-Topic: Need clarification on 5086 RFC - Section 5.3
Thread-Index: AcmIO7c1/CmIGmUoToiHXEZZV06pHQA1Fito
Message-ID: <A3C5DF08D38B6049839A6F553B331C7698C4A1A251@ILPTMAIL02.ecitele.com>
References: <B24A3277E6B11B4D9D53D272FE49B7C50276EB8B@CHN-HCLT-EVS02.HCLT.CORP.HCL.IN>
In-Reply-To: <B24A3277E6B11B4D9D53D272FE49B7C50276EB8B@CHN-HCLT-EVS02.HCLT.CORP.HCL.IN>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_A3C5DF08D38B6049839A6F553B331C7698C4A1A251ILPTMAIL02eci_"
MIME-Version: 1.0
X-OriginalArrivalTime: 07 Feb 2009 10:49:53.0122 (UTC) FILETIME=[CEA63C20:01C98911]
Cc: "pwe3@ietf.org" <pwe3@ietf.org>
Subject: Re: [PWE3] Need clarification on 5086 RFC - Section 5.3
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/pwe3>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 07 Feb 2009 10:50:24 -0000

--_000_A3C5DF08D38B6049839A6F553B331C7698C4A1A251ILPTMAIL02eci_
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

Mahesh,
Quoting from RFC 2119 that defines the meaning of key words defining requir=
ement levels:

<quote>

SHOULD: This word, or the adjective "RECOMMENDED", mean that there may exis=
t valid reasons in particular circumstances to ignore a particular item, bu=
t the full implications must be understood and carefully weighed before cho=
osing a different course.

...

MAY: This word, or the adjective "OPTIONAL", mean that an item is truly opt=
ional.  One vendor may choose to include the item because a particular mark=
etplace requires it or because the vendor feels that it enhances the produc=
t while another vendor may omit the same item. An implementation which does=
 not include a particular option MUST be prepared to interoperate with anot=
her implementation which does include the option, though perhaps with reduc=
ed functionality. In the same vein an implementation which does include a p=
articular option MUST be prepared to interoperate with another implementati=
on which does not include the option (except, of course, for the feature th=
e option provides.)

<end quote>

IMHO the wording used in RFC 5086 allows you to carry signaling packets in =
the same PW with the data packets if you see compelling reasons to do that =
and fully understand the implications. One of these implications is, of cou=
rse, that your implementation will be non-interoperable with the implementa=
tions that carry signaling packets in separate PW.

I cannot say at the moment which implementations prevail in the industry to=
day, since CESoPSN applications I actually deal with lately do not require =
the signaling packets' functionality.

Hopefully, these notes will be helpful.


Regards,
     Sasha

________________________________
From: Mahesh Singh C [maheshsc@hcl.in]
Sent: Friday, February 06, 2009 11:17 AM
To: Alexander Vainshtein
Cc: pwe3@ietf.org
Subject: Need clarification on 5086 RFC - Section 5.3

Hi Sasha,

 I would like to understand the below recommendation in RFC 5086 better.


Section 5.3 Extending Basic NxDS0 Services with CE Application Signaling


 =93Signaling packets SHOULD be carried in a separate dedicated PW.

 However, implementations MAY carry them in the same PW as the TDM

 data packets for the basic NxDS0 service.  The methods of "pairing"

 the PWs carrying TDM data and signaling packets for the same extended

 NxDS0 service are out of scope of this document.=94



The first statement specifies SHOULD. From my understanding, if we try to i=
mplement as per the next statement the meaning of first statement is becomi=
ng false right?



Is it mandatory to send signaling packets in separate PW and data packets i=
n another separate PW?



OR



Can we send signaling packets and data packets in the same PW. The required=
 information in the same PW packets can be distinguished using its CW. Can =
we implement like this. This I believe as per the second statement above. B=
ut, since the first statement has SHOULD, I am not sure on this approach.



Regards,

Mahesh


DISCLAIMER:
---------------------------------------------------------------------------=
--------------------------------------------

The contents of this e-mail and any attachment(s) are confidential and inte=
nded for the named recipient(s) only.
It shall not attach any liability on the originator or HCL or its affiliate=
s. Any views or opinions presented in
this email are solely those of the author and may not necessarily reflect t=
he opinions of HCL or its affiliates.
Any form of reproduction, dissemination, copying, disclosure, modification,=
 distribution and / or publication of
this message without the prior written consent of the author of this e-mail=
 is strictly prohibited. If you have
received this email in error please delete it and notify the sender immedia=
tely. Before opening any mail and
attachments please check them for viruses and defect.

---------------------------------------------------------------------------=
--------------------------------------------


--_000_A3C5DF08D38B6049839A6F553B331C7698C4A1A251ILPTMAIL02eci_
Content-Type: text/html; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

<html dir=3D"ltr"><head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DWindows-1=
252">
<style>@page Section1 {margin: 1.0in 1.25in 1.0in 1.25in; }
P.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
LI.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
DIV.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
A:link {
	COLOR: blue; TEXT-DECORATION: underline
}
SPAN.MsoHyperlink {
	COLOR: blue; TEXT-DECORATION: underline
}
A:visited {
	COLOR: purple; TEXT-DECORATION: underline
}
SPAN.MsoHyperlinkFollowed {
	COLOR: purple; TEXT-DECORATION: underline
}
P.MsoPlainText {
	FONT-SIZE: 10pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Courier New"
}
LI.MsoPlainText {
	FONT-SIZE: 10pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Courier New"
}
DIV.MsoPlainText {
	FONT-SIZE: 10pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Courier New"
}
SPAN.EmailStyle17 {
	COLOR: windowtext; FONT-FAMILY: Arial
}
DIV.Section1 {
=09
}
OL {
	MARGIN-BOTTOM: 0in
}
UL {
	MARGIN-BOTTOM: 0in
}
</style>
<meta content=3D"MSHTML 6.00.2900.3492" name=3D"GENERATOR">
<style title=3D"owaParaStyle">P {
	MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px
}
</style>
<meta content=3D"WVGFNSAQMF" name=3D"SKYPE_FRAMEID">
</head>
<body lang=3D"EN-US" vlink=3D"purple" link=3D"blue" ocsi=3D"x">
<div dir=3D"ltr"><font face=3D"Times New Roman" color=3D"#000000" size=3D"3=
">Mahesh,</font></div>
<div dir=3D"ltr"><font face=3D"times new roman">Quoting from RFC 2119 that =
defines the meaning of key words defining requirement levels:</font></div>
<div dir=3D"ltr"><font face=3D"times new roman"></font>&nbsp;</div>
<div dir=3D"ltr"><font face=3D"times new roman">&lt;quote&gt;</font></div>
<blockquote dir=3D"ltr" style=3D"MARGIN-RIGHT: 0px">
<div dir=3D"ltr"><span class=3D"Apple-style-span" style=3D"WORD-SPACING: 0p=
x; FONT: 16px 'times new roman'; TEXT-TRANSFORM: none; COLOR: rgb(0,0,0); T=
EXT-INDENT: 0px; WHITE-SPACE: normal; LETTER-SPACING: normal; BORDER-COLLAP=
SE: separate; orphans: 2; widows: 2; webkit-border-horizontal-spacing: 0px;=
 webkit-border-vertical-spacing: 0px; webkit-text-decorations-in-effect: no=
ne; webkit-text-size-adjust: auto; webkit-text-stroke-width: 0">
<pre style=3D"WORD-WRAP: break-word">SHOULD: This word, or the adjective &q=
uot;RECOMMENDED&quot;, mean that there may exist valid reasons in particula=
r circumstances to ignore a particular item, but the full implications must=
 be understood and carefully weighed before choosing a different course.</p=
re>
<pre style=3D"WORD-WRAP: break-word"><font face=3D"courier new">...</font><=
/pre>
<pre style=3D"WORD-WRAP: break-word"><span class=3D"Apple-style-span" style=
=3D"WORD-SPACING: 0px; FONT: 16px 'times new roman'; TEXT-TRANSFORM: none; =
COLOR: rgb(0,0,0); TEXT-INDENT: 0px; WHITE-SPACE: normal; LETTER-SPACING: n=
ormal; BORDER-COLLAPSE: separate; orphans: 2; widows: 2; webkit-border-hori=
zontal-spacing: 0px; webkit-border-vertical-spacing: 0px; webkit-text-decor=
ations-in-effect: none; webkit-text-size-adjust: auto; webkit-text-stroke-w=
idth: 0"><pre style=3D"WORD-WRAP: break-word">MAY: This word, or the adject=
ive &quot;OPTIONAL&quot;, mean that an item is truly optional.  One vendor =
may choose to include the item because a particular marketplace requires it=
 or because the vendor feels that it enhances the product while another ven=
dor may omit the same item. An implementation which does not include a part=
icular option MUST be prepared to interoperate with another implementation =
which does include the option, though perhaps with reduced functionality. I=
n the same vein an implementation which does include a particular option MU=
ST be prepared to interoperate with another implementation which does not i=
nclude the option (except, of course, for the feature the option provides.)=
</pre></span></pre>
</span></div>
</blockquote>
<div dir=3D"ltr"><font face=3D"times new roman">&lt;end quote&gt;</font></d=
iv>
<div dir=3D"ltr"><font face=3D"times new roman"></font>&nbsp;</div>
<div dir=3D"ltr"><font face=3D"times new roman">IMHO the wording used in RF=
C 5086 allows you to carry signaling packets in the same PW with the data p=
ackets if you see compelling reasons to do that and fully understand the im=
plications. One of these implications
 is, of course, that your implementation will be non-interoperable with the=
 implementations that carry signaling packets in separate PW.
</font></div>
<div dir=3D"ltr"><font face=3D"times new roman"></font>&nbsp;</div>
<div dir=3D"ltr"><font face=3D"times new roman">I cannot say at the moment =
which implementations prevail in the industry today, since&nbsp;CESoPSN app=
lications I actually deal with lately do not require the signaling packets'=
 functionality.</font></div>
<div dir=3D"ltr"><font face=3D"times new roman"></font>&nbsp;</div>
<div dir=3D"ltr"><font face=3D"times new roman">Hopefully, these notes&nbsp=
;will be&nbsp;helpful.</font></div>
<div dir=3D"ltr"><font face=3D"times new roman"></font>&nbsp;</div>
<div dir=3D"ltr"><font face=3D"times new roman"></font>&nbsp;</div>
<div dir=3D"ltr"><font face=3D"times new roman">Regards,</font></div>
<div dir=3D"ltr">&nbsp;&nbsp;&nbsp;&nbsp; Sasha</div>
<div dir=3D"ltr"><font face=3D"times new roman"></font>&nbsp;</div>
<div id=3D"divRpF779996" style=3D"DIRECTION: ltr">
<hr tabindex=3D"-1">
<font face=3D"Tahoma" size=3D"2"><b>From:</b> Mahesh Singh C [maheshsc@hcl.=
in]<br>
<b>Sent:</b> Friday, February 06, 2009 11:17 AM<br>
<b>To:</b> Alexander Vainshtein<br>
<b>Cc:</b> pwe3@ietf.org<br>
<b>Subject:</b> Need clarification on 5086 RFC - Section 5.3<br>
</font><br>
</div>
<div></div>
<div>
<div class=3D"Section1">
<p class=3D"MsoNormal"><font face=3D"Arial" size=3D"2"><span style=3D"FONT-=
SIZE: 10pt; FONT-FAMILY: Arial">Hi Sasha,</span></font></p>
<p class=3D"MsoNormal"><font face=3D"Arial" size=3D"2"><span style=3D"FONT-=
SIZE: 10pt; FONT-FAMILY: Arial"></span></font>&nbsp;</p>
<p class=3D"MsoNormal"><font face=3D"Arial" size=3D"2"><span style=3D"FONT-=
SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;I would like to understand the below =
recommendation in RFC 5086 better.</span></font></p>
<p class=3D"MsoNormal"><font face=3D"Arial" size=3D"2"><span style=3D"FONT-=
SIZE: 10pt; FONT-FAMILY: Arial"></span></font>&nbsp;</p>
<p class=3D"MsoPlainText"><font face=3D"Arial" size=3D"2"><span style=3D"FO=
NT-SIZE: 10pt; FONT-FAMILY: Arial">Section 5.3
</span></font>Extending Basic NxDS0 Services with CE Application Signaling<=
/p>
<p class=3D"MsoNormal"><font face=3D"Arial" size=3D"2"><span style=3D"FONT-=
SIZE: 10pt; FONT-FAMILY: Arial"></span></font>&nbsp;</p>
<p class=3D"MsoPlainText"><font face=3D"Arial" size=3D"2"><span style=3D"FO=
NT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;=93</span></font>Signaling packets=
 SHOULD be carried in a separate dedicated PW.</p>
<p class=3D"MsoPlainText"><font face=3D"Courier New" size=3D"2"><span style=
=3D"FONT-SIZE: 10pt">&nbsp;However, implementations MAY carry them in the s=
ame PW as the TDM</span></font></p>
<p class=3D"MsoPlainText"><font face=3D"Courier New" size=3D"2"><span style=
=3D"FONT-SIZE: 10pt">&nbsp;data packets for the basic NxDS0 service.&nbsp; =
The methods of &quot;pairing&quot;</span></font></p>
<p class=3D"MsoPlainText"><font face=3D"Courier New" size=3D"2"><span style=
=3D"FONT-SIZE: 10pt">&nbsp;the PWs carrying TDM data and signaling packets =
for the same extended</span></font></p>
<p class=3D"MsoPlainText"><font face=3D"Courier New" size=3D"2"><span style=
=3D"FONT-SIZE: 10pt">&nbsp;NxDS0 service are out of scope of this document.=
=94</span></font></p>
<p class=3D"MsoPlainText"><font face=3D"Courier New" size=3D"2"><span style=
=3D"FONT-SIZE: 10pt"></span></font>&nbsp;</p>
<p class=3D"MsoPlainText"><font face=3D"Courier New" size=3D"2"><span style=
=3D"FONT-SIZE: 10pt">The first statement specifies SHOULD. From my understa=
nding, if we try to implement as per the next statement the meaning of firs=
t statement is becoming false right?
</span></font></p>
<p class=3D"MsoPlainText"><font face=3D"Courier New" size=3D"2"><span style=
=3D"FONT-SIZE: 10pt"></span></font>&nbsp;</p>
<p class=3D"MsoPlainText"><font face=3D"Courier New" size=3D"2"><span style=
=3D"FONT-SIZE: 10pt">Is it mandatory to send signaling packets in separate =
PW and data packets in another separate PW?</span></font></p>
<p class=3D"MsoPlainText"><font face=3D"Courier New" size=3D"2"><span style=
=3D"FONT-SIZE: 10pt"></span></font>&nbsp;</p>
<p class=3D"MsoPlainText"><font face=3D"Courier New" size=3D"2"><span style=
=3D"FONT-SIZE: 10pt">OR
</span></font></p>
<p class=3D"MsoPlainText"><font face=3D"Courier New" size=3D"2"><span style=
=3D"FONT-SIZE: 10pt"></span></font>&nbsp;</p>
<p class=3D"MsoPlainText"><font face=3D"Courier New" size=3D"2"><span style=
=3D"FONT-SIZE: 10pt">Can we send signaling packets and data packets in the =
same PW. The required information in the same PW packets can be distinguish=
ed using its CW. Can we implement like this.
 This I believe as per the second statement above. But, since the first sta=
tement has SHOULD, I am not sure on this approach.
</span></font></p>
<p class=3D"MsoPlainText"><font face=3D"Courier New" size=3D"2"><span style=
=3D"FONT-SIZE: 10pt"></span></font>&nbsp;</p>
<p class=3D"MsoPlainText"><font face=3D"Courier New" size=3D"2"><span style=
=3D"FONT-SIZE: 10pt">Regards,</span></font></p>
<p class=3D"MsoPlainText"><font face=3D"Courier New" size=3D"2"><span style=
=3D"FONT-SIZE: 10pt">Mahesh</span></font></p>
<p class=3D"MsoNormal"><font face=3D"Arial" size=3D"2"><span style=3D"FONT-=
SIZE: 10pt; FONT-FAMILY: Arial"></span></font>&nbsp;</p>
<p class=3D"MsoNormal"><font face=3D"Arial" size=3D"2"><span style=3D"FONT-=
SIZE: 10pt; FONT-FAMILY: Arial"></span></font>&nbsp;</p>
</div>
<table>
<tbody>
<tr>
<td bgcolor=3D"#ffffff"><font color=3D"#000000">DISCLAIMER:<br>
---------------------------------------------------------------------------=
--------------------------------------------<br>
<br>
The contents of this e-mail and any attachment(s) are confidential and inte=
nded for the named recipient(s) only.<br>
It shall not attach any liability on the originator or HCL or its affiliate=
s. Any views or opinions presented in
<br>
this email are solely those of the author and may not necessarily reflect t=
he opinions of HCL or its affiliates.<br>
Any form of reproduction, dissemination, copying, disclosure, modification,=
 distribution and / or publication of
<br>
this message without the prior written consent of the author of this e-mail=
 is strictly prohibited. If you have
<br>
received this email in error please delete it and notify the sender immedia=
tely. Before opening any mail and
<br>
attachments please check them for viruses and defect.<br>
<br>
---------------------------------------------------------------------------=
--------------------------------------------<br>
</font></td>
</tr>
</tbody>
</table>
</div>
</body>
</html>

--_000_A3C5DF08D38B6049839A6F553B331C7698C4A1A251ILPTMAIL02eci_--


Return-Path: <wwwrun@core3.amsl.com>
X-Original-To: pwe3@ietf.org
Delivered-To: pwe3@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 30) id 6C6213A6C9C; Mon,  9 Feb 2009 06:51:48 -0800 (PST)
X-idtracker: yes
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Message-Id: <20090209145148.6C6213A6C9C@core3.amsl.com>
Date: Mon,  9 Feb 2009 06:51:48 -0800 (PST)
Cc: Internet Architecture Board <iab@iab.org>, pwe3 mailing list <pwe3@ietf.org>, pwe3 chair <pwe3-chairs@tools.ietf.org>, RFC Editor <rfc-editor@rfc-editor.org>
Subject: [PWE3] Protocol Action: 'Managed Objects for TDM over Packet Switched Network (PSN)' to Proposed Standard
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/pwe3>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 09 Feb 2009 14:51:48 -0000

The IESG has approved the following document:

- 'Managed Objects for TDM over Packet Switched Network (PSN) '
   <draft-ietf-pwe3-tdm-mib-11.txt> as a Proposed Standard

This document is the product of the Pseudowire Emulation Edge to Edge 
Working Group. 

The IESG contact persons are Mark Townsley and Jari Arkko.

A URL of this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-pwe3-tdm-mib-11.txt

Technical Summary

This memo defines a portion of the Management Information Base (MIB)
for use with network management protocols in the Internet community.
In particular, it describes managed objects for pseudo wire
encapsulation for structured or unstructured TDM (T1, E1, T3, E3)
circuits over a Packet Switch Network (PSN).

Working Group Summary

This document has been reviewed by the experts in the PWE3 WG
and there are no outstanding issues.

Protocol Quality

This is a very simple and well written, no protocol issues are
anticipated and no outstanding technical issues exist..

Personnel

Who is the Document Shepherd for this document?

Danny McPherson (danny@tcb.net)

Who is the Responsible Area Director?

Mark Townsley (townsley@cisco.com)

RFC Editor's note:

OLD
pwTDMCfgEntry  OBJECT-TYPE
    SYNTAX            PwTDMCfgEntry
    MAX-ACCESS        not-accessible
    STATUS            current
    DESCRIPTION
        "These parameters define the characteristics of a
         TDM PW. They are grouped here to ease NMS burden.
         Once an entry is created here it may be re-used
         by many PWs.
         Unless otherwise specified, all objects in this table
         MUST NOT be changed after row activation (see [PWMIB])
         if the row index is in use by an entry in pwTDMTable.
         Rows must persist after reboot."
 

 NEW
 
 pwTDMCfgEntry  OBJECT-TYPE
     SYNTAX            PwTDMCfgEntry
     MAX-ACCESS        not-accessible
     STATUS            current
     DESCRIPTION
         "These parameters define the characteristics of a
           TDM PW. They are grouped here to ease NMS burden.
           Once an entry is created here it may be re-used
           by many PWs.
           Unless otherwise specified, all objects in this table
           MUST NOT be changed after row activation (see [PWMIB])"



Return-Path: <isacco.fontana@trentinonetwork.it>
X-Original-To: pwe3@core3.amsl.com
Delivered-To: pwe3@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8B9EF3A6ADF; Sun,  8 Feb 2009 22:23:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.718
X-Spam-Level: 
X-Spam-Status: No, score=-0.718 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245, STOX_REPLY_TYPE=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Yz+qyoXrugIH; Sun,  8 Feb 2009 22:23:12 -0800 (PST)
Received: from croce.trentinonetwork.it (croce.trentinonetwork.it [77.72.192.4]) by core3.amsl.com (Postfix) with ESMTP id 6D7A43A68B4; Sun,  8 Feb 2009 22:23:12 -0800 (PST)
Received: from croce.trentinonetwork.it (localhost [127.0.0.1]) by croce.trentinonetwork.it (Postfix) with ESMTP id 9CEAB8EC09F; Mon,  9 Feb 2009 07:23:07 +0100 (CET)
Received: from PCifontana (unknown [172.25.225.50]) by croce.trentinonetwork.it (Postfix) with ESMTP id 09F178EC09E; Mon,  9 Feb 2009 07:23:06 +0100 (CET)
Message-ID: <18657F094C8C42D283C2120B1F506046@PCifontana>
From: "Isacco Fontana" <isacco.fontana@trentinonetwork.it>
To: "Loa Andersson" <loa@pi.nu>, <mpls@ietf.org>, "pwe3" <pwe3@ietf.org>, "L2VPN" <l2vpn@ietf.org>, "ccamp" <ccamp@ops.ietf.org>, <ahtmpls@itu.int>, <mpls-tp@ietf.org>
References: <490F03D6.30408@pi.nu>
In-Reply-To: <490F03D6.30408@pi.nu>
Date: Mon, 9 Feb 2009 07:23:00 +0100
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Windows Mail 6.0.6000.16480
X-MimeOLE: Produced By Microsoft MimeOLE V6.0.6000.16545
X-Virus-Scanned: ClamAV using ClamSMTP
X-Mailman-Approved-At: Tue, 10 Feb 2009 08:44:43 -0800
Subject: Re: [PWE3] [mpls] Poll for MPLS-TP documents to become mpls working groupdocuments
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/pwe3>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 09 Feb 2009 06:23:13 -0000

support all.
----- Original Message ----- 
From: "Loa Andersson" <loa@pi.nu>
To: <mpls@ietf.org>; "pwe3" <pwe3@ietf.org>; "L2VPN" <l2vpn@ietf.org>; 
"ccamp" <ccamp@ops.ietf.org>; <ahtmpls@itu.int>; <mpls-tp@ietf.org>
Sent: Monday, November 03, 2008 2:59 PM
Subject: [mpls] Poll for MPLS-TP documents to become mpls working 
groupdocuments


> Working group(s)
>
> we have four documents from the MPLS-TP effort that the authors think
> are ready to become working group documents. The documents are listed 
> below.
>
> This mail initiate a two week working poll for comments on three of the
> documents, for the fourth document
> (draft-bocci-mpls-tp-gach-gal-00.txt) we already have an ongoing poll.
>
> Please send your comments before Nov 11 for
> draft-bocci-mpls-tp-gach-gal-00.txt and Nov 17 for the other three-
>
> *Note:*
> Please send your responses to the *mpls working group mailing list*,
> a bit of discipline is needed, "replay all" won't do the trick  ;).
>
> Comments Nov 11 the latest:
>
> Title : MPLS Generic Associated Channel
> Author(s): M. Vigoureux, M. Bocci, D. Ward, G. Swallow,
>                   R. Aggarwal
> Filename : draft-bocci-mpls-tp-gach-gal-00.txt
> Pages : 16
> Date : 2008-10-27
>
>
> Comments Nov 17 the latest:
>
> Title    : MPLS-TP Requirements
> Author(s): B. Niven-Jenkins, et al.
> Filename : draft-jenkins-mpls-mpls-tp-requirements-01.txt
> Pages    : 18
> Date     : 2008-10-31
>
> Title    : A Framework for MPLS in Transport Networks
> Author(s): M. Bocci, S. Bryant
> Filename : draft-blb-mpls-tp-framework-01.txt
> Pages    : 27
> Date     : 2008-10-31
>
> Title    : Requirements for OAM in MPLS Transport Networks
> Author(s): M. Vigoureux, D. Ward, M. Betts, M. Bocci, I.Busi
> Filename : draft-vigoureux-mpls-tp-oam-requirements-01.txt
> Pages : 16
> Date : 2008-11-1
>
> Loa and George
>
> -- 
> Loa Andersson
>
> Principal Networking Architect
> Acreo AB                           phone:  +46 8 632 77 14
> Isafjordsgatan 22                  mobile: +46 739 81 21 64
> Kista, Sweden                      email:  loa.andersson@acreo.se
>                                           loa@pi.nu
> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls
> 



Return-Path: <lmartini@cisco.com>
X-Original-To: pwe3@core3.amsl.com
Delivered-To: pwe3@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8712A3A6A07 for <pwe3@core3.amsl.com>; Wed, 11 Feb 2009 07:57:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id njq-7xJIyeCs for <pwe3@core3.amsl.com>; Wed, 11 Feb 2009 07:57:04 -0800 (PST)
Received: from napoleon.monoski.com (black.monoski.com [63.227.123.238]) by core3.amsl.com (Postfix) with ESMTP id ADC783A6971 for <pwe3@ietf.org>; Wed, 11 Feb 2009 07:57:04 -0800 (PST)
Received: from rasputin.monoski.com (62-50-197-109.client.stsn.net [62.50.197.109]) (authenticated bits=0) by napoleon.monoski.com (8.13.8/8.13.8) with ESMTP id n1BFv0G9003820 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 11 Feb 2009 08:57:01 -0700 (MST)
Message-ID: <4992F546.3040609@cisco.com>
Date: Wed, 11 Feb 2009 08:56:54 -0700
From: Luca Martini <lmartini@cisco.com>
User-Agent: Thunderbird 2.0.0.18 (X11/20081105)
MIME-Version: 1.0
To: Kevin F Wang <kfwang@juniper.net>
References: <44F0D6788897BD41866504CA639F87788B5D90@proton.jnpr.net>
In-Reply-To: <44F0D6788897BD41866504CA639F87788B5D90@proton.jnpr.net>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Scanned-By: MIMEDefang 2.63 on 63.227.123.227
Cc: tob@netapp.com, giles.heron@tellabs.com, erosen@cisco.com, nna@level3.net, pwe3@ietf.org
Subject: Re: [PWE3] Question for RFC 4447, PW Status TLV negotiation
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/pwe3>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 11 Feb 2009 15:57:05 -0000

Kevin F Wang wrote:
> In section 5.4.3 (page 18) of RFC 4447:
>
>  
>
>   "When a PW is first set up, the PEs MUST attempt to negotiate the
>
>    usage of the PW status TLV.  This is accomplished as follows: A PE
>
>    that supports the PW Status TLV MUST include it in the *initial*
> Label
>
>    Mapping message following the PW FEC and the interface parameter
>
>    sub-TLVs."
>
>  
>
> Here is my question:
>
> Router A sends Label Mapping message with PW Status TLV to router B
> initially. Later if it sends another Label Mapping message to router B
> with some updated parameters (like interface parameter), does it *still*
> need to include the PW Status TLV in the Label Mapping message (assuming
> no Label Withdraw was in between the two Label Mapping message)? 
>
>  
>   
no. you cannot send another label mapping that is different in any way.
The interface parameters are part of the FEC , and an update would
trigger an immediate LDP session fatal error.
So you MUST send a label withdraw between the two label mappings , and
the label mapping needs to  include the status TLV as in the usual case.

I hope this helps.
Luca

>  
>
> Thanks,
>
> -Kevin
>
>  
>
>
>   



Return-Path: <kfwang@juniper.net>
X-Original-To: pwe3@core3.amsl.com
Delivered-To: pwe3@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id AF1BF3A6AC0 for <pwe3@core3.amsl.com>; Wed, 11 Feb 2009 06:33:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.598
X-Spam-Level: 
X-Spam-Status: No, score=-6.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8lZMHv0GVNpK for <pwe3@core3.amsl.com>; Wed, 11 Feb 2009 06:33:24 -0800 (PST)
Received: from exprod7og109.obsmtp.com (exprod7og109.obsmtp.com [64.18.2.171]) by core3.amsl.com (Postfix) with ESMTP id D171A3A6935 for <pwe3@ietf.org>; Wed, 11 Feb 2009 06:33:16 -0800 (PST)
Received: from source ([66.129.224.36]) (using TLSv1) by exprod7ob109.postini.com ([64.18.6.12]) with SMTP ID DSNKSZLhrH9pRYEGcmHG6Y7QHrOPMgJYphJH@postini.com; Wed, 11 Feb 2009 06:33:29 PST
Received: from p-emfe01-sac.jnpr.net (66.129.254.72) by P-EMHUB01-HQ.jnpr.net (172.24.192.35) with Microsoft SMTP Server id 8.1.340.0; Wed, 11 Feb 2009 06:18:22 -0800
Received: from p-emlb01-sac.jnpr.net ([66.129.254.46]) by p-emfe01-sac.jnpr.net with Microsoft SMTPSVC(6.0.3790.3959); Wed, 11 Feb 2009 06:18:22 -0800
Received: from pi-smtp.jnpr.net ([10.10.2.36]) by p-emlb01-sac.jnpr.net with Microsoft SMTPSVC(6.0.3790.3959);	 Wed, 11 Feb 2009 06:18:22 -0800
Received: from proton.jnpr.net ([10.10.2.37]) by pi-smtp.jnpr.net with Microsoft SMTPSVC(5.0.2195.6713);	 Wed, 11 Feb 2009 09:18:20 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-Class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C98C53.9705E4CE"
Date: Wed, 11 Feb 2009 09:18:19 -0500
Message-ID: <44F0D6788897BD41866504CA639F87788B5D90@proton.jnpr.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Question for RFC 4447, PW Status TLV negotiation
Thread-Index: AcmMU5b06bE5edfORB+wJi47Tku+9Q==
From: Kevin F Wang <kfwang@juniper.net>
To: <lmartini@cisco.com>, <nna@level3.net>, <giles.heron@tellabs.com>, <erosen@cisco.com>, <tob@netapp.com>
X-OriginalArrivalTime: 11 Feb 2009 14:18:20.0492 (UTC) FILETIME=[974670C0:01C98C53]
X-Mailman-Approved-At: Wed, 11 Feb 2009 08:53:01 -0800
Cc: pwe3@ietf.org
Subject: [PWE3] Question for RFC 4447, PW Status TLV negotiation
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/pwe3>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 11 Feb 2009 14:40:45 -0000

------_=_NextPart_001_01C98C53.9705E4CE
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable

In section 5.4.3 (page 18) of RFC 4447:

=20

  "When a PW is first set up, the PEs MUST attempt to negotiate the

   usage of the PW status TLV.  This is accomplished as follows: A PE

   that supports the PW Status TLV MUST include it in the *initial*
Label

   Mapping message following the PW FEC and the interface parameter

   sub-TLVs."

=20

Here is my question:

Router A sends Label Mapping message with PW Status TLV to router B
initially. Later if it sends another Label Mapping message to router B
with some updated parameters (like interface parameter), does it *still*
need to include the PW Status TLV in the Label Mapping message (assuming
no Label Withdraw was in between the two Label Mapping message)?=20

=20

=20

Thanks,

-Kevin

=20


------_=_NextPart_001_01C98C53.9705E4CE
Content-Type: text/html; charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable

<html 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=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:SimSun;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:SimSun;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
 /* 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:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:Arial;
	color:windowtext;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
	{page:Section1;}
-->
</style>

</head>

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

<div class=3DSection1>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>In section 5.4.3 (page 18) of RFC =
4447:<o:p></o:p></span></font></p>

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

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>&nbsp; &#8220;When a PW is first set up, the PEs MUST
attempt to negotiate the<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>&nbsp;&nbsp; usage of the PW status TLV.&nbsp; This =
is
accomplished as follows: A PE<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>&nbsp;&nbsp; that supports the PW Status TLV MUST =
include it
in the *<b><span style=3D'font-weight:bold'>initial</span></b>* =
Label<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>&nbsp;&nbsp; Mapping message following the PW FEC and =
the
interface parameter<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>&nbsp;&nbsp; =
sub-TLVs.&#8221;<o:p></o:p></span></font></p>

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

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Here is my question:<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Router A sends Label Mapping message with PW Status =
TLV to
router B initially. Later if it sends another Label Mapping message to =
router B
with some updated parameters (like interface parameter), does it =
*<b><span
style=3D'font-weight:bold'>still</span></b>* need to include the PW =
Status TLV in
the Label Mapping message (assuming no Label Withdraw was in between the =
two
Label Mapping message)? <o:p></o:p></span></font></p>

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

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

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Thanks,</span></font><o:p></o:p></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>-Kevin</span></font><o:p></o:p></p>

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

</div>

</body>

</html>

------_=_NextPart_001_01C98C53.9705E4CE--


Return-Path: <kfwang@juniper.net>
X-Original-To: pwe3@core3.amsl.com
Delivered-To: pwe3@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A23393A688E for <pwe3@core3.amsl.com>; Wed, 11 Feb 2009 08:11:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.466
X-Spam-Level: 
X-Spam-Status: No, score=-6.466 tagged_above=-999 required=5 tests=[AWL=0.133,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fbY-MTehSmDK for <pwe3@core3.amsl.com>; Wed, 11 Feb 2009 08:11:35 -0800 (PST)
Received: from exprod7og109.obsmtp.com (exprod7og109.obsmtp.com [64.18.2.171]) by core3.amsl.com (Postfix) with ESMTP id B048C3A67A4 for <pwe3@ietf.org>; Wed, 11 Feb 2009 08:11:21 -0800 (PST)
Received: from source ([66.129.224.36]) (using TLSv1) by exprod7ob109.postini.com ([64.18.6.12]) with SMTP ID DSNKSZL4q314ypn08Fwq9NuNS2hYL10ejVWa@postini.com; Wed, 11 Feb 2009 08:11:40 PST
Received: from p-emfe01-sac.jnpr.net (66.129.254.72) by P-EMHUB01-HQ.jnpr.net (172.24.192.35) with Microsoft SMTP Server id 8.1.340.0; Wed, 11 Feb 2009 08:08:11 -0800
Received: from p-emlb01-sac.jnpr.net ([66.129.254.46]) by p-emfe01-sac.jnpr.net with Microsoft SMTPSVC(6.0.3790.3959); Wed, 11 Feb 2009 08:08:11 -0800
Received: from emailwf1.jnpr.net ([10.10.2.33]) by p-emlb01-sac.jnpr.net with Microsoft SMTPSVC(6.0.3790.3959);	 Wed, 11 Feb 2009 08:08:11 -0800
Received: from proton.jnpr.net ([10.10.2.37]) by emailwf1.jnpr.net with Microsoft SMTPSVC(6.0.3790.1830);	 Wed, 11 Feb 2009 11:08:09 -0500
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
Date: Wed, 11 Feb 2009 11:08:09 -0500
Message-ID: <44F0D6788897BD41866504CA639F87788B5E56@proton.jnpr.net>
In-Reply-To: <4992F546.3040609@cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Question for RFC 4447, PW Status TLV negotiation
Thread-Index: AcmMYWeBMacr10lfTj2gGY2VX8/xzwAANYPw
References: <44F0D6788897BD41866504CA639F87788B5D90@proton.jnpr.net> <4992F546.3040609@cisco.com>
From: Kevin F Wang <kfwang@juniper.net>
To: "Luca Martini" <lmartini@cisco.com>
X-OriginalArrivalTime: 11 Feb 2009 16:08:09.0869 (UTC) FILETIME=[EED993D0:01C98C62]
X-Mailman-Approved-At: Wed, 11 Feb 2009 08:53:15 -0800
Cc: tob@netapp.com, giles.heron@tellabs.com, erosen@cisco.com, nna@level3.net, pwe3@ietf.org
Subject: Re: [PWE3] Question for RFC 4447, PW Status TLV negotiation
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/pwe3>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 11 Feb 2009 16:11:36 -0000

Hi Luca,

Thanks a lot for the quick response. So is it fair to state that "A
Label Mapping message *MUST* include PW Status TLV if the sender want to
support PW Status TLV capability"?=20

Thanks,
Kevin

-----Original Message-----
From: Luca Martini [mailto:lmartini@cisco.com]=20
Sent: Wednesday, February 11, 2009 10:57 AM
To: Kevin F Wang
Cc: nna@level3.net; giles.heron@tellabs.com; erosen@cisco.com;
tob@netapp.com; pwe3@ietf.org
Subject: Re: Question for RFC 4447, PW Status TLV negotiation

Kevin F Wang wrote:
> In section 5.4.3 (page 18) of RFC 4447:
>
> =20
>
>   "When a PW is first set up, the PEs MUST attempt to negotiate the
>
>    usage of the PW status TLV.  This is accomplished as follows: A PE
>
>    that supports the PW Status TLV MUST include it in the *initial*
> Label
>
>    Mapping message following the PW FEC and the interface parameter
>
>    sub-TLVs."
>
> =20
>
> Here is my question:
>
> Router A sends Label Mapping message with PW Status TLV to router B
> initially. Later if it sends another Label Mapping message to router B
> with some updated parameters (like interface parameter), does it
*still*
> need to include the PW Status TLV in the Label Mapping message
(assuming
> no Label Withdraw was in between the two Label Mapping message)?=20
>
> =20
>  =20
no. you cannot send another label mapping that is different in any way.
The interface parameters are part of the FEC , and an update would
trigger an immediate LDP session fatal error.
So you MUST send a label withdraw between the two label mappings , and
the label mapping needs to  include the status TLV as in the usual case.

I hope this helps.
Luca

> =20
>
> Thanks,
>
> -Kevin
>
> =20
>
>
>  =20



Return-Path: <tnadeau@lucidvision.com>
X-Original-To: pwe3@core3.amsl.com
Delivered-To: pwe3@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 220E83A6975 for <pwe3@core3.amsl.com>; Wed, 11 Feb 2009 23:44:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HnxG4XpNHTnB for <pwe3@core3.amsl.com>; Wed, 11 Feb 2009 23:44:40 -0800 (PST)
Received: from lucidvision.com (lucidvision.com [72.71.250.34]) by core3.amsl.com (Postfix) with ESMTP id 2933B3A68CC for <pwe3@ietf.org>; Wed, 11 Feb 2009 23:44:40 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by lucidvision.com (Postfix) with ESMTP id 153273ABAE3F; Thu, 12 Feb 2009 02:44:45 -0500 (EST)
X-Virus-Scanned: amavisd-new at www.lucidvision.com
Received: from lucidvision.com ([127.0.0.1]) by localhost (static-72-71-250-34.cncdnh.fios.verizon.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OQpDv8gNfdij; Thu, 12 Feb 2009 02:44:42 -0500 (EST)
Received: from [25.245.68.250] (m3a5e36d0.tmodns.net [208.54.94.58]) by lucidvision.com (Postfix) with ESMTP id 3FB123ABAE34; Thu, 12 Feb 2009 02:44:40 -0500 (EST)
References: <44F0D6788897BD41866504CA639F87788B5D90@proton.jnpr.net> <4992F546.3040609@cisco.com> <44F0D6788897BD41866504CA639F87788B5E56@proton.jnpr.net>
Message-Id: <88CD5FA8-2128-48EE-89FE-7F7D3065AB34@lucidvision.com>
From: Thomas Nadeau <tnadeau@lucidvision.com>
To: Kevin F Wang <kfwang@juniper.net>
In-Reply-To: <44F0D6788897BD41866504CA639F87788B5E56@proton.jnpr.net>
Content-Type: text/plain; charset=us-ascii; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (iPhone Mail 5H11)
Date: Thu, 12 Feb 2009 07:49:40 +0100
X-Mailer: iPhone Mail (5H11)
Cc: "tob@netapp.com" <tob@netapp.com>, "giles.heron@tellabs.com" <giles.heron@tellabs.com>, Luca Martini <lmartini@cisco.com>, "nna@level3.net" <nna@level3.net>, "pwe3@ietf.org" <pwe3@ietf.org>, "erosen@cisco.com" <erosen@cisco.com>
Subject: Re: [PWE3] Question for RFC 4447, PW Status TLV negotiation
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/pwe3>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 12 Feb 2009 07:44:41 -0000

It is my understanding that you must include it initially; it cannot  
be renegotiated later.

Sent from my iPhone

On Feb 11, 2009, at 5:08 PM, Kevin F Wang <kfwang@juniper.net> wrote:

> Hi Luca,
>
> Thanks a lot for the quick response. So is it fair to state that "A
> Label Mapping message *MUST* include PW Status TLV if the sender  
> want to
> support PW Status TLV capability"?
>
> Thanks,
> Kevin
>
> -----Original Message-----
> From: Luca Martini [mailto:lmartini@cisco.com]
> Sent: Wednesday, February 11, 2009 10:57 AM
> To: Kevin F Wang
> Cc: nna@level3.net; giles.heron@tellabs.com; erosen@cisco.com;
> tob@netapp.com; pwe3@ietf.org
> Subject: Re: Question for RFC 4447, PW Status TLV negotiation
>
> Kevin F Wang wrote:
>> In section 5.4.3 (page 18) of RFC 4447:
>>
>>
>>
>>  "When a PW is first set up, the PEs MUST attempt to negotiate the
>>
>>   usage of the PW status TLV.  This is accomplished as follows: A PE
>>
>>   that supports the PW Status TLV MUST include it in the *initial*
>> Label
>>
>>   Mapping message following the PW FEC and the interface parameter
>>
>>   sub-TLVs."
>>
>>
>>
>> Here is my question:
>>
>> Router A sends Label Mapping message with PW Status TLV to router B
>> initially. Later if it sends another Label Mapping message to  
>> router B
>> with some updated parameters (like interface parameter), does it
> *still*
>> need to include the PW Status TLV in the Label Mapping message
> (assuming
>> no Label Withdraw was in between the two Label Mapping message)?
>>
>>
>>
> no. you cannot send another label mapping that is different in any  
> way.
> The interface parameters are part of the FEC , and an update would
> trigger an immediate LDP session fatal error.
> So you MUST send a label withdraw between the two label mappings , and
> the label mapping needs to  include the status TLV as in the usual  
> case.
>
> I hope this helps.
> Luca
>
>>
>>
>> Thanks,
>>
>> -Kevin
>>
>>
>>
>>
>>
>
> _______________________________________________
> pwe3 mailing list
> pwe3@ietf.org
> https://www.ietf.org/mailman/listinfo/pwe3
>


Return-Path: <root@core3.amsl.com>
X-Original-To: pwe3@ietf.org
Delivered-To: pwe3@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0) id EFEFB3A6AF5; Fri, 13 Feb 2009 15:45:01 -0800 (PST)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20090213234501.EFEFB3A6AF5@core3.amsl.com>
Date: Fri, 13 Feb 2009 15:45:01 -0800 (PST)
Cc: pwe3@ietf.org
Subject: [PWE3] I-D ACTION:draft-ietf-pwe3-ldp-aii-reachability-01.txt
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/pwe3>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 13 Feb 2009 23:45:02 -0000

--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		: LDP extensions for AII reachability
	Author(s)	: S. DeLord, F. JOUNAY, P. Niger, M. Aissaoui, M. Bocci
	Filename	: draft-ietf-pwe3-ldp-aii-reachability-01.txt
	Pages		: 10
	Date		: 2009-2-10
	
The dynamic End-to-End Multisegment pseudowire setup requires PEs to 
   maintain a pseudowire routing table when using FEC129. There is a 
   requirement to automatically advertise Attachment Individual 
   Identifiers to enable the pseudowire routing tables to be populated. 
   Two mechanisms already exist, a BGP reachability information 
   distribution mechanism and an IGP based one. Here we define a third 
   solution relying on LDP. It allows for automatic advertisement of the 
   Attachment Individual Identifier prefixes provisioned on a T-PE when 
   this node does not run BGP or IGP. The mechanism described here runs 
   on the T-LDP (Targeted LDP) session between the T-PE and S-PE, and is 
   intended to complement existing PW routing mechanisms using BGP or 
   OSPF.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-pwe3-ldp-aii-reachability-01.txt

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

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

--NextPart
Content-Type: Message/External-body;
	name="draft-ietf-pwe3-ldp-aii-reachability-01.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2009-2-13154138.I-D@ietf.org>


--NextPart--



Return-Path: <euddasi@redback.com>
X-Original-To: pwe3@core3.amsl.com
Delivered-To: pwe3@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 64F4E3A6918 for <pwe3@core3.amsl.com>; Sat, 14 Feb 2009 10:56:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JhgkqzYiydcV for <pwe3@core3.amsl.com>; Sat, 14 Feb 2009 10:56:46 -0800 (PST)
Received: from prattle.redback.com (prattle.redback.com [155.53.12.9]) by core3.amsl.com (Postfix) with ESMTP id 4B6163A6A57 for <PWE3@ietf.org>; Sat, 14 Feb 2009 10:56:43 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by prattle.redback.com (Postfix) with ESMTP id 803967B8150 for <PWE3@ietf.org>; Sat, 14 Feb 2009 10:56:51 -0800 (PST)
Received: from prattle.redback.com ([127.0.0.1]) by localhost (prattle [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 17776-08 for <PWE3@ietf.org>; Sat, 14 Feb 2009 10:56:51 -0800 (PST)
Received: from rbsjx.ad.redback.com (rbsjxh1.redback.com [155.53.14.105]) by prattle.redback.com (Postfix) with ESMTP id 6830D7B814E for <PWE3@ietf.org>; Sat, 14 Feb 2009 10:56:51 -0800 (PST)
Received: from RBSJX.ad.redback.com ([155.53.14.103]) by rbsjxh1.ad.redback.com ([155.53.14.105]) with mapi; Sat, 14 Feb 2009 10:56:51 -0800
From: David Sinicrope <euddasi@redback.com>
To: "PWE3@ietf.org" <PWE3@ietf.org>
Date: Sat, 14 Feb 2009 10:56:50 -0800
Thread-Topic: Time slots for IETF 74 PWE3 meeting
Thread-Index: AcmO1f4o4AcNXYD1F0eyztRRXFz+YA==
Message-ID: <C5BC7E22.1499%euddasi@redback.com>
Accept-Language: en-US
Content-Language: en
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_C5BC7E221499euddasiredbackcom_"
MIME-Version: 1.0
X-Virus-Scanned: by amavisd-new at redback.com
Subject: [PWE3] Time slots for IETF 74 PWE3 meeting
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/pwe3>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 14 Feb 2009 18:56:48 -0000

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

Hi All,
Please let me know if you would like a time slot for the PWE3 meeting durin=
g IETF 74.
I'll need the desired duration, topic, presenter for each request.
Thanks!
Dave

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

<HTML>
<HEAD>
<TITLE>Time slots for IETF 74 PWE3 meeting</TITLE>
</HEAD>
<BODY>
<FONT SIZE=3D"4"><FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"><SPAN ST=
YLE=3D'font-size:11pt'>Hi All,<BR>
Please let me know if you would like a time slot for the PWE3 meeting durin=
g IETF 74.<BR>
I&#8217;ll need the desired duration, topic, presenter for each request.<BR=
>
Thanks!<BR>
Dave </SPAN></FONT></FONT>
</BODY>
</HTML>


--_000_C5BC7E221499euddasiredbackcom_--


Return-Path: <root@core3.amsl.com>
X-Original-To: pwe3@ietf.org
Delivered-To: pwe3@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0) id 9FBA128C1A5; Wed, 18 Feb 2009 12:15:01 -0800 (PST)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20090218201501.9FBA128C1A5@core3.amsl.com>
Date: Wed, 18 Feb 2009 12:15:01 -0800 (PST)
Cc: pwe3@ietf.org
Subject: [PWE3] I-D Action:draft-ietf-pwe3-vccv-bfd-03.txt
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/pwe3>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 18 Feb 2009 20:15:01 -0000

--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           : Bidirectional Forwarding Detection (BFD) for the Pseudowire Virtual Circuit Connectivity Verification (VCCV)
	Author(s)       : T. Nadeau, C. Pignataro
	Filename        : draft-ietf-pwe3-vccv-bfd-03.txt
	Pages           : 14
	Date            : 2009-02-18

This document describes new Connectivity Verification (CV) types
using Bidirectional Forwarding Detection (BFD) with Virtual Circuit
Connectivity Verification (VCCV).  VCCV provides a control channel
that is associated with a Pseudowire (PW), as well as the
corresponding operations and management functions such as
connectivity verification to be used over that control channel.

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

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

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

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

Content-Type: text/plain
Content-ID: <2009-02-18120554.I-D@ietf.org>


--NextPart--


Return-Path: <root@core3.amsl.com>
X-Original-To: pwe3@ietf.org
Delivered-To: pwe3@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0) id D91283A6A35; Wed, 18 Feb 2009 23:30:01 -0800 (PST)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20090219073001.D91283A6A35@core3.amsl.com>
Date: Wed, 18 Feb 2009 23:30:01 -0800 (PST)
Cc: pwe3@ietf.org
Subject: [PWE3] I-D Action:draft-ietf-pwe3-segmented-pw-11.txt
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/pwe3>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 19 Feb 2009 07:30:01 -0000

--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           : Segmented Pseudowire
	Author(s)       : L. Martini, et al.
	Filename        : draft-ietf-pwe3-segmented-pw-11.txt
	Pages           : 43
	Date            : 2009-02-18

This document describes how to connect pseudowires (PW) between two
distinct PW control planes or PSN domains. The PW control planes may
belong to independent autonomous systems, or the PSN technology is
heterogeneous, or a PW might need to be aggregated at a specific PSN
point. The PW packet data units are simply switched from one PW to
another without changing the PW payload.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-pwe3-segmented-pw-11.txt

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

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

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

Content-Type: text/plain
Content-ID: <2009-02-18232308.I-D@ietf.org>


--NextPart--


Return-Path: <loa@pi.nu>
X-Original-To: pwe3@core3.amsl.com
Delivered-To: pwe3@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 90C553A69D5 for <pwe3@core3.amsl.com>; Fri, 20 Feb 2009 06:13:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.943
X-Spam-Level: 
X-Spam-Status: No, score=-1.943 tagged_above=-999 required=5 tests=[AWL=0.306,  BAYES_00=-2.599, HELO_EQ_SE=0.35]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cJjvZp+UP-zN for <pwe3@core3.amsl.com>; Fri, 20 Feb 2009 06:13:11 -0800 (PST)
Received: from ns.elverljung.se (ns.elverljung.se [194.68.48.116]) by core3.amsl.com (Postfix) with ESMTP id 091193A6A10 for <pwe3@ietf.org>; Fri, 20 Feb 2009 06:13:07 -0800 (PST)
Received: from [192.168.0.101] (h133n2fls33o883.telia.com [217.208.62.133]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: loa) by ns.elverljung.se (Postfix) with ESMTPSA id 60C6A2D823F for <pwe3@ietf.org>; Fri, 20 Feb 2009 15:13:20 +0100 (CET)
Message-ID: <499EBA78.5080907@pi.nu>
Date: Fri, 20 Feb 2009 15:13:12 +0100
From: Loa Andersson <loa@pi.nu>
User-Agent: Thunderbird 2.0.0.19 (Windows/20081209)
MIME-Version: 1.0
To: pwe3@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: [PWE3] the MPLS-TP RFC
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/pwe3>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 20 Feb 2009 14:13:11 -0000

All,

we have our first MPLS-TP RFC:

         RFC 5317

         Title:      Joint Working Team (JWT) Report
                     on MPLS Architectural Considerations for a
                     Transport Profile
         Author:     S. Bryant, Ed.,
                     L. Andersson, Ed.
         Status:     Informational
         Date:       February 2009
         Mailbox:    stbryant@cisco.com,
                     loa@pi.nu
         Pages:      10, 68
         Characters: 18367, 1411313
         Updates/Obsoletes/SeeAlso:   None

         I-D Tag:    draft-bryant-mpls-tp-jwt-report-00.txt

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


/Loa

-- 


Loa Andersson

Sr Strategy and Standards Manager
Ericsson ///                          phone:  +46 8 632 77 14

                                       email:  loa.andersson@ericsson.com
                                               loa.andersson@redback.com
                                               loa@pi.nu




Return-Path: <stbryant@cisco.com>
X-Original-To: pwe3@core3.amsl.com
Delivered-To: pwe3@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 264853A6986 for <pwe3@core3.amsl.com>; Fri, 20 Feb 2009 10:46:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.952
X-Spam-Level: 
X-Spam-Status: No, score=-9.952 tagged_above=-999 required=5 tests=[AWL=0.647,  BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ERdz1MRvUCBn for <pwe3@core3.amsl.com>; Fri, 20 Feb 2009 10:46:12 -0800 (PST)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140]) by core3.amsl.com (Postfix) with ESMTP id A93E53A67B4 for <pwe3@ietf.org>; Fri, 20 Feb 2009 10:46:11 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.38,242,1233532800"; d="scan'208";a="34421449"
Received: from ams-dkim-1.cisco.com ([144.254.224.138]) by ams-iport-1.cisco.com with ESMTP; 20 Feb 2009 18:46:21 +0000
Received: from ams-core-1.cisco.com (ams-core-1.cisco.com [144.254.224.150]) by ams-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id n1KIkL0s019787;  Fri, 20 Feb 2009 19:46:21 +0100
Received: from cisco.com (mrwint.cisco.com [64.103.71.48]) by ams-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id n1KIkKF3017984; Fri, 20 Feb 2009 18:46:20 GMT
Received: from dhcp-gpk02-vlan300-64-103-65-55.cisco.com (localhost [127.0.0.1]) by cisco.com (8.11.7p3+Sun/8.8.8) with ESMTP id n1KIkKc08408; Fri, 20 Feb 2009 18:46:20 GMT
Message-ID: <499EFA7C.8070508@cisco.com>
Date: Fri, 20 Feb 2009 18:46:20 +0000
From: Stewart Bryant <stbryant@cisco.com>
User-Agent: Thunderbird 2.0.0.19 (Macintosh/20081209)
MIME-Version: 1.0
To: pwe3 <pwe3@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=306; t=1235155581; x=1236019581; 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:=20draft-ietf-pwe3-segmented-pw=20WG=20last=20call |Sender:=20; bh=t43ozW5Kv3eJhCJrt6WSldAidznhQExrXVi5z+QjiRQ=; b=GSwNANjAekAkJvhYCSLwkDpU3z+O4JlB5fgPP/i7QFNXnaBInCLOREX4hO ErvcZq5KAivTJpSIgKk8b60bASiSfQRCwTIHFUmmJBANeOBt6j34wMLMMOMF oX90Kkf629;
Authentication-Results: ams-dkim-1; header.From=stbryant@cisco.com; dkim=pass ( sig from cisco.com/amsdkim1002 verified; ); 
Cc: draft-ietf-pwe3-segmented-pw@tools.ietf.org
Subject: [PWE3] draft-ietf-pwe3-segmented-pw WG last call
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: stbryant@cisco.com
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/pwe3>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 20 Feb 2009 18:46:13 -0000

This is the start of working group last call on

draft-ietf-pwe3-segmented-pw-11.txt

This draft can be found at

http://www.ietf.org/internet-drafts/draft-ietf-pwe3-segmented-pw-11.txt

Monday 9th March 2009.

Please read the document and provide feedback to the PWE3 list

Thanks

Stewart


Return-Path: <root@core3.amsl.com>
X-Original-To: pwe3@ietf.org
Delivered-To: pwe3@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0) id 4C0EF3A6895; Fri, 20 Feb 2009 16:30:01 -0800 (PST)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20090221003001.4C0EF3A6895@core3.amsl.com>
Date: Fri, 20 Feb 2009 16:30:01 -0800 (PST)
Cc: pwe3@ietf.org
Subject: [PWE3] I-D ACTION:draft-ietf-pwe3-enet-mib-14.txt
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/pwe3>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 21 Feb 2009 00:30:01 -0000

--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		: Ethernet Pseudowire (PW) Management Information Base (MIB)
	Author(s)	: D. Zelig, T. Nadeau
	Filename	: draft-ietf-pwe3-enet-mib-14.txt
	Pages		: 23
	Date		: 2009-2-20
	
This memo defines a portion of the Management Information Base (MIB)
   for use with network management protocols in the Internet community.
   In particular, it describes managed objects for modeling of Ethernet
   Pseudowire (PW) services.

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

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

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

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

Content-Type: text/plain
Content-ID: <2009-2-20161722.I-D@ietf.org>


--NextPart--



Return-Path: <loa@pi.nu>
X-Original-To: pwe3@core3.amsl.com
Delivered-To: pwe3@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0A0253A684D; Mon, 23 Feb 2009 06:25:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.003
X-Spam-Level: 
X-Spam-Status: No, score=-2.003 tagged_above=-999 required=5 tests=[AWL=0.246,  BAYES_00=-2.599, HELO_EQ_SE=0.35]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UvUripcmUqHV; Mon, 23 Feb 2009 06:25:54 -0800 (PST)
Received: from ns.elverljung.se (ns.elverljung.se [194.68.48.116]) by core3.amsl.com (Postfix) with ESMTP id 3FF1C3A67B6; Mon, 23 Feb 2009 06:25:54 -0800 (PST)
Received: from [192.36.158.94] (wdhcp-158-94.verkstad.net [192.36.158.94]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: loa) by ns.elverljung.se (Postfix) with ESMTPSA id B538A2D8593; Mon, 23 Feb 2009 15:26:10 +0100 (CET)
Message-ID: <49A2B201.8050603@pi.nu>
Date: Mon, 23 Feb 2009 15:26:09 +0100
From: Loa Andersson <loa@pi.nu>
User-Agent: Thunderbird 2.0.0.19 (Windows/20081209)
MIME-Version: 1.0
To: mpls-tp@ietf.org, mpls@ietf.org, pwe3@ietf.org, ccamp@ops.ietf.org,  l2vpn@ietf.org, Ross Callon <rcallon@juniper.net>,  David Ward <dward@cisco.com>, ITU-T ad hoc team on MPLS-TP <ahmpls-tp@lists.itu.int>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: [PWE3] new mpls(-tp) working group document
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/pwe3>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 23 Feb 2009 14:25:55 -0000

Dear all,

the poll for draft-gray-mpls-tp-nm-req to become MPLS WG document
has ended with full support.

Authors, please republish as: draft-ietf-mpls-tp-nm-req-00

/Loa

-- 


Loa Andersson

Sr Strategy and Standards Manager
Ericsson ///                          phone:  +46 8 632 77 14

                                       email:  loa.andersson@ericsson.com
                                               loa.andersson@redback.com
                                               loa@pi.nu




Return-Path: <root@core3.amsl.com>
X-Original-To: pwe3@ietf.org
Delivered-To: pwe3@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0) id 484E43A6A9B; Mon, 23 Feb 2009 16:30:00 -0800 (PST)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20090224003001.484E43A6A9B@core3.amsl.com>
Date: Mon, 23 Feb 2009 16:30:01 -0800 (PST)
Cc: pwe3@ietf.org
Subject: [PWE3] I-D ACTION:draft-ietf-pwe3-pw-tc-mib-15.txt
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/pwe3>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 24 Feb 2009 00:30:01 -0000

--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 of Textual Conventions for Pseudowires (PW) Management
	Author(s)	: T. Nadeau, D. Zelig, O. Nicklass
	Filename	: draft-ietf-pwe3-pw-tc-mib-15.txt
	Pages		: 11
	Date		: 2009-2-23
	
This memo defines a Management Information Base (MIB) module which
   contains Textual Conventions (TCs) to represent commonly-used
   Pseudowire (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-15.txt

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

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

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

Content-Type: text/plain
Content-ID: <2009-2-23162641.I-D@ietf.org>


--NextPart--



Return-Path: <loa@pi.nu>
X-Original-To: pwe3@core3.amsl.com
Delivered-To: pwe3@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3597028C14D; Tue, 24 Feb 2009 02:24:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.064
X-Spam-Level: 
X-Spam-Status: No, score=-2.064 tagged_above=-999 required=5 tests=[AWL=0.185,  BAYES_00=-2.599, HELO_EQ_SE=0.35]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DE-Hq9QU+6Tx; Tue, 24 Feb 2009 02:24:48 -0800 (PST)
Received: from ns.elverljung.se (ns.elverljung.se [194.68.48.116]) by core3.amsl.com (Postfix) with ESMTP id 692F428C14A; Tue, 24 Feb 2009 02:24:45 -0800 (PST)
Received: from [192.36.158.94] (wdhcp-158-94.verkstad.net [192.36.158.94]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: loa) by ns.elverljung.se (Postfix) with ESMTPSA id 226A02D8593; Tue, 24 Feb 2009 11:25:02 +0100 (CET)
Message-ID: <49A3CAFD.9060806@pi.nu>
Date: Tue, 24 Feb 2009 11:25:01 +0100
From: Loa Andersson <loa@pi.nu>
User-Agent: Thunderbird 2.0.0.19 (Windows/20081209)
MIME-Version: 1.0
To: mpls-tp@ietf.org, mpls@ietf.org, ccamp@ops.ietf.org, pwe3@ietf.org,  ITU-T ad hoc team on MPLS-TP <ahmpls-tp@lists.itu.int>, George Swallow <swallow@cisco.com>, Ross Callon <rcallon@juniper.net>,  David Ward <dward@cisco.com>, Malcolm Betts <betts01@nortel.com>,  VIGOUREUX MARTIN <Martin.Vigoureux@alcatel-lucent.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: [PWE3] 2nd wg last call on draft-ietf-mpls-tp-gach-gal
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/pwe3>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 24 Feb 2009 10:24:49 -0000

All,

an updated version (-02) of the draft-ietf-mpls-tp-gach-gal
has been published.

The draft is found at:

http://tools.ietf.org/html/draft-ietf-mpls-tp-gach-gal-02

Since the updates are significant this is to initiate a 2 week
working group last call on the new version.

Please send your comments to the mpls-tp@ietf.org mailing list.

The working group last call will end on March 11.

/Loa
-- 


Loa Andersson

Sr Strategy and Standards Manager
Ericsson ///                          phone:  +46 8 632 77 14

                                       email:  loa.andersson@ericsson.com
                                               loa.andersson@redback.com
                                               loa@pi.nu




Return-Path: <DALLAN@nortel.com>
X-Original-To: pwe3@core3.amsl.com
Delivered-To: pwe3@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0D2DD3A6977; Tue, 24 Feb 2009 10:34:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.299
X-Spam-Level: 
X-Spam-Status: No, score=-6.299 tagged_above=-999 required=5 tests=[AWL=0.300,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id S2+oV5ahGVeP; Tue, 24 Feb 2009 10:34:54 -0800 (PST)
Received: from zrtps0kp.nortel.com (zrtps0kp.nortel.com [47.140.192.56]) by core3.amsl.com (Postfix) with ESMTP id 7CAC63A6805; Tue, 24 Feb 2009 10:34:53 -0800 (PST)
Received: from zcarhxm2.corp.nortel.com (zcarhxm2.corp.nortel.com [47.129.230.99]) by zrtps0kp.nortel.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id n1OIYPm11593; Tue, 24 Feb 2009 18:34:25 GMT
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
Date: Tue, 24 Feb 2009 13:34:07 -0500
Message-ID: <87AC5F88F03E6249AEA68D40BD3E00BE193A7FD2@zcarhxm2.corp.nortel.com>
In-Reply-To: <49A3CAFD.9060806@pi.nu>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [mpls-tp] 2nd wg last call on draft-ietf-mpls-tp-gach-gal
Thread-Index: AcmWn8Efk5GurTo4ShOXgqKXjG6w5gAA52mw
References: <49A3CAFD.9060806@pi.nu>
From: "David Allan" <dallan@nortel.com>
To: "Loa Andersson" <loa@pi.nu>, <mpls-tp@ietf.org>, <mpls@ietf.org>, <ccamp@ops.ietf.org>, <pwe3@ietf.org>, "ITU-T ad hoc team on MPLS-TP" <ahmpls-tp@lists.itu.int>, "George Swallow" <swallow@cisco.com>, "Ross Callon" <rcallon@juniper.net>,  "David Ward" <dward@cisco.com>, "Malcolm Betts" <betts01@nortel.com>, "VIGOUREUX MARTIN" <Martin.Vigoureux@alcatel-lucent.com>
Subject: Re: [PWE3] [mpls-tp] 2nd wg last call on draft-ietf-mpls-tp-gach-gal
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/pwe3>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 24 Feb 2009 18:34:55 -0000

Well I'll make the same comment again....

In section 4.3 it states...

   o  Unlike the mechanisms described and referenced in RFC 3429 [18],
      MPLS-TP maintenance messages will not reside immediately after the
      GAL but instead behind the ACH, which itself resides after the
      bottom of the label stack.  This ensures that OAM, using the
      G-ACh, complies with RFC 4928 [11].

While RFC 4928 says

   It must also be noted that LSRs that correctly identify a payload as
   not being IP most often will load-share traffic across multiple
   equal-cost paths based on the label stack.  Any reserved label, no
   matter where it is located in the stack, may be included in the
   computation for load balancing.  Modification of the label stack
   between packets of a single flow could result in re-ordering that
   flow.  That is, were an explicit null or a router-alert label to be
   added to a packet, that packet could take a different path through
   the network.

So the mere presence of the GAL will violate RFC 4928....the presence of
the GACH cannot fix this...and claiming the GACH does provide compliance
is misleading....the paragraph in section 4.3 should be deleted...

Cheers
Dave





=20

-----Original Message-----
From: mpls-tp-bounces@ietf.org [mailto:mpls-tp-bounces@ietf.org] On
Behalf Of Loa Andersson
Sent: Tuesday, February 24, 2009 5:25 AM
To: mpls-tp@ietf.org; mpls@ietf.org; ccamp@ops.ietf.org; pwe3@ietf.org;
ITU-T ad hoc team on MPLS-TP; George Swallow; Ross Callon; David Ward;
Betts, Malcolm (CAR:X632); VIGOUREUX MARTIN
Subject: [mpls-tp] 2nd wg last call on draft-ietf-mpls-tp-gach-gal

All,

an updated version (-02) of the draft-ietf-mpls-tp-gach-gal has been
published.

The draft is found at:

http://tools.ietf.org/html/draft-ietf-mpls-tp-gach-gal-02

Since the updates are significant this is to initiate a 2 week working
group last call on the new version.

Please send your comments to the mpls-tp@ietf.org mailing list.

The working group last call will end on March 11.

/Loa
--=20


Loa Andersson

Sr Strategy and Standards Manager
Ericsson ///                          phone:  +46 8 632 77 14

                                       email:
loa.andersson@ericsson.com
                                               loa.andersson@redback.com
                                               loa@pi.nu


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


Return-Path: <root@core3.amsl.com>
X-Original-To: pwe3@ietf.org
Delivered-To: pwe3@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0) id 3B8793A6AB7; Wed, 25 Feb 2009 04:30:00 -0800 (PST)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20090225123001.3B8793A6AB7@core3.amsl.com>
Date: Wed, 25 Feb 2009 04:30:01 -0800 (PST)
Cc: pwe3@ietf.org
Subject: [PWE3] I-D Action:draft-ietf-pwe3-ms-pw-arch-06.txt
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/pwe3>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 25 Feb 2009 12:30:01 -0000

--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 Pseudowire Emulation Edge-to-Edge
	Author(s)       : M. Bocci, S. Bryant
	Filename        : draft-ietf-pwe3-ms-pw-arch-06.txt
	Pages           : 24
	Date            : 2009-02-25

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

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-pwe3-ms-pw-arch-06.txt

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

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

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

Content-Type: text/plain
Content-ID: <2009-02-25042443.I-D@ietf.org>


--NextPart--


Return-Path: <loa@pi.nu>
X-Original-To: pwe3@core3.amsl.com
Delivered-To: pwe3@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id EA8D33A6AAA; Thu, 26 Feb 2009 03:48:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.115
X-Spam-Level: 
X-Spam-Status: No, score=-2.115 tagged_above=-999 required=5 tests=[AWL=0.134,  BAYES_00=-2.599, HELO_EQ_SE=0.35]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DFUBDeOnsUcQ; Thu, 26 Feb 2009 03:48:56 -0800 (PST)
Received: from ns.elverljung.se (ns.elverljung.se [194.68.48.116]) by core3.amsl.com (Postfix) with ESMTP id 1DE933A69F7; Thu, 26 Feb 2009 03:48:56 -0800 (PST)
Received: from [192.36.158.94] (wdhcp-158-94.verkstad.net [192.36.158.94]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: loa) by ns.elverljung.se (Postfix) with ESMTPSA id AB4BA2D8257; Thu, 26 Feb 2009 12:49:15 +0100 (CET)
Message-ID: <49A681B5.6020501@pi.nu>
Date: Thu, 26 Feb 2009 12:49:09 +0100
From: Loa Andersson <loa@pi.nu>
User-Agent: Thunderbird 2.0.0.19 (Windows/20081209)
MIME-Version: 1.0
To: mpls-tp@ietf.org, mpls@ietf.org, ccamp@ops.ietf.org, pwe3@ietf.org,  ITU-T ad hoc team on MPLS-TP <ahmpls-tp@lists.itu.int>, l2vpn@ietf.org, IAB IAB <iab@iab.org>, "Iesg (E-mail)" <iesg@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: [PWE3] RFC 5462 the second MPLS-TP RFC
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/pwe3>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 26 Feb 2009 11:48:57 -0000

All,

we have just seen our second mpls-tp RFC being published:

RFC5462 'Multiprotocol Label Switching (MPLS) Label Stack Entry:
         "EXP" Field Renamed to "Traffic Class" Field'.

/Loa

-- 


Loa Andersson

Sr Strategy and Standards Manager
Ericsson ///                          phone:  +46 8 632 77 14

                                       email:  loa.andersson@ericsson.com
                                               loa.andersson@redback.com
                                               loa@pi.nu




Return-Path: <loa@pi.nu>
X-Original-To: pwe3@core3.amsl.com
Delivered-To: pwe3@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 54A2728C1E8; Thu, 26 Feb 2009 10:26:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.135
X-Spam-Level: 
X-Spam-Status: No, score=-2.135 tagged_above=-999 required=5 tests=[AWL=0.114,  BAYES_00=-2.599, HELO_EQ_SE=0.35]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kmPXearQgR+Q; Thu, 26 Feb 2009 10:26:00 -0800 (PST)
Received: from ns.elverljung.se (ns.elverljung.se [194.68.48.116]) by core3.amsl.com (Postfix) with ESMTP id 7AE9D28C0EE; Thu, 26 Feb 2009 10:26:00 -0800 (PST)
Received: from [192.36.158.94] (wdhcp-158-94.verkstad.net [192.36.158.94]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: loa) by ns.elverljung.se (Postfix) with ESMTPSA id 36BA22D8257; Thu, 26 Feb 2009 19:26:20 +0100 (CET)
Message-ID: <49A6DEC5.1010403@pi.nu>
Date: Thu, 26 Feb 2009 19:26:13 +0100
From: Loa Andersson <loa@pi.nu>
User-Agent: Thunderbird 2.0.0.19 (Windows/20081209)
MIME-Version: 1.0
To: mpls-tp@ietf.org, mpls@ietf.org,  ITU-T ad hoc team on MPLS-TP <ahmpls-tp@lists.itu.int>, ccamp@ops.ietf.org, pwe3@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: [PWE3] poll on making draft-sprecher-mpls-tp-survive-fwk-01.txt a working group document?
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/pwe3>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 26 Feb 2009 18:26:01 -0000

All,

we have received a request from the editors/authors of
draft-sprecher-mpls-tp-survive-fwk-01.txt to make the
document an mpls working group document.

Please send your comments to the mpls-tp mailing list.

This poll ends eob Thu Mar 12, 2009.

/Loa

-- 


Loa Andersson

Sr Strategy and Standards Manager
Ericsson ///                          phone:  +46 8 632 77 14

                                       email:  loa.andersson@ericsson.com
                                               loa.andersson@redback.com
                                               loa@pi.nu




Return-Path: <root@core3.amsl.com>
X-Original-To: pwe3@ietf.org
Delivered-To: pwe3@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0) id B48DA3A6896; Fri, 27 Feb 2009 12:45:01 -0800 (PST)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20090227204501.B48DA3A6896@core3.amsl.com>
Date: Fri, 27 Feb 2009 12:45:01 -0800 (PST)
Cc: pwe3@ietf.org
Subject: [PWE3] I-D Action:draft-ietf-pwe3-mpls-transport-03.txt
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/pwe3>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 27 Feb 2009 20:45:01 -0000

--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           : Application of Ethernet Pseudowires to MPLS Transport Networks
	Author(s)       : S. Bryant, et al.
	Filename        : draft-ietf-pwe3-mpls-transport-03.txt
	Pages           : 12
	Date            : 2009-02-27

A requirement has been identified by the operator community for the
transparent carriage of the MPLS(-TP) network of one party over the
MPLS(-TP) network of another party.  This document describes a method
of satisfying this need using the existing PWE3 Ethernet pseudowire
standard RFC4448.

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

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

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

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

Content-Type: text/plain
Content-ID: <2009-02-27123622.I-D@ietf.org>


--NextPart--
