
From annamaria.fulignoli@ericsson.com  Mon Jun  1 05:47:16 2009
Return-Path: <annamaria.fulignoli@ericsson.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 208C13A6AE1; Mon,  1 Jun 2009 05:47:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.893
X-Spam-Level: 
X-Spam-Status: No, score=-5.893 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4, SARE_SUB_6CONS_WORD=0.356]
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 wrpvKWGVgXz8; Mon,  1 Jun 2009 05:47:15 -0700 (PDT)
Received: from mailgw3.ericsson.se (mailgw3.ericsson.se [193.180.251.60]) by core3.amsl.com (Postfix) with ESMTP id 5A8DF3A6ABB; Mon,  1 Jun 2009 05:47:14 -0700 (PDT)
X-AuditID: c1b4fb3c-b7b28ae000005484-66-4a23cdbde183
Received: from esealmw128.eemea.ericsson.se (Unknown_Domain [153.88.253.124]) by mailgw3.ericsson.se (Symantec Mail Security) with SMTP id 05.20.21636.DBDC32A4; Mon,  1 Jun 2009 14:46:53 +0200 (CEST)
Received: from esealmw118.eemea.ericsson.se ([153.88.200.77]) by esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830);  Mon, 1 Jun 2009 14:45:24 +0200
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: Mon, 1 Jun 2009 14:45:21 +0200
Message-ID: <93DFCD4B101EB440B5B72997456C5F9403CFC65E@esealmw118.eemea.ericsson.se>
In-Reply-To: <4A1A836E.7080804@pi.nu>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [mpls] poll on making draft-mansfield-mpls-tp-nm-framework a mplswg document
Thread-Index: AcndLYZ8PfIWoSYpTeyEhGL1GsrArgFiUOXQ
References: <4A1A836E.7080804@pi.nu>
From: "Annamaria Fulignoli" <annamaria.fulignoli@ericsson.com>
To: "Loa Andersson" <loa@pi.nu>, <mpls-tp@ietf.org>, <mpls@ietf.org>, <pwe3@ietf.org>
X-OriginalArrivalTime: 01 Jun 2009 12:45:24.0542 (UTC) FILETIME=[D5307DE0:01C9E2B6]
X-Brightmail-Tracker: AAAAAA==
Subject: Re: [PWE3] [mpls] poll on making draft-mansfield-mpls-tp-nm-framework a mplswg 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: <http://www.ietf.org/mail-archive/web/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, 01 Jun 2009 12:47:16 -0000

Support=20

-----Original Message-----
From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf Of =
Loa Andersson
Sent: luned=EC 25 maggio 2009 13.39
To: mpls-tp@ietf.org; mpls@ietf.org; pwe3@ietf.org
Subject: [mpls] poll on making draft-mansfield-mpls-tp-nm-framework a =
mplswg document

All,

this is to start a two week poll (to be ended on June 8th) on the =
suggestion to make draft-mansfield-mpls-tp-nm-framework
a mpls working group document.

Send your comment (approve or disapprove) to the mpls-tp list.

/Loa
--=20


Loa Andersson

Sr Strategy and Standards Manager    phone:  +46 10 717 52 13
Ericsson ///                                 +46 767 72 92 13=20


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


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

From annamaria.fulignoli@ericsson.com  Mon Jun  1 05:47:17 2009
Return-Path: <annamaria.fulignoli@ericsson.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 6ED223A6AE1; Mon,  1 Jun 2009 05:47:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.071
X-Spam-Level: 
X-Spam-Status: No, score=-6.071 tagged_above=-999 required=5 tests=[AWL=0.178,  BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4Bksek7Vziq4; Mon,  1 Jun 2009 05:47:16 -0700 (PDT)
Received: from mailgw3.ericsson.se (mailgw3.ericsson.se [193.180.251.60]) by core3.amsl.com (Postfix) with ESMTP id 09EF23A69BB; Mon,  1 Jun 2009 05:47:15 -0700 (PDT)
X-AuditID: c1b4fb3c-b7b28ae000005484-69-4a23cdbd1381
Received: from esealmw128.eemea.ericsson.se (Unknown_Domain [153.88.253.124]) by mailgw3.ericsson.se (Symantec Mail Security) with SMTP id 35.20.21636.DBDC32A4; Mon,  1 Jun 2009 14:46:53 +0200 (CEST)
Received: from esealmw118.eemea.ericsson.se ([153.88.200.77]) by esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830);  Mon, 1 Jun 2009 14:45:55 +0200
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: Mon, 1 Jun 2009 14:45:54 +0200
Message-ID: <93DFCD4B101EB440B5B72997456C5F9403CFC660@esealmw118.eemea.ericsson.se>
In-Reply-To: <4A1BB784.7030501@pi.nu>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [mpls] poll on the Rosetta Stone draft
Thread-Index: Acnd5SiZQEF1XylvQhOfFqL+MTTTkgE0bb1g
References: <4A1BB784.7030501@pi.nu>
From: "Annamaria Fulignoli" <annamaria.fulignoli@ericsson.com>
To: "Loa Andersson" <loa@pi.nu>, <mpls-tp@ietf.org>, <mpls@ietf.org>, <pwe3@ietf.org>
X-OriginalArrivalTime: 01 Jun 2009 12:45:55.0823 (UTC) FILETIME=[E7D597F0:01C9E2B6]
X-Brightmail-Tracker: AAAAAA==
Subject: Re: [PWE3] [mpls] poll on the Rosetta Stone draft
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: <http://www.ietf.org/mail-archive/web/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, 01 Jun 2009 12:47:17 -0000

Support=20

-----Original Message-----
From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf Of =
Loa Andersson
Sent: marted=EC 26 maggio 2009 11.34
To: mpls-tp@ietf.org; mpls@ietf.org; pwe3@ietf.org
Subject: [mpls] poll on the Rosetta Stone draft

All,

this is to start a two week poll on the suggestion to make the =
draft-helvoort-mpls-tp-rosetta-stone-00 an MPLS working group document.

Please send your comments (approval or disapproval) to the mpls-tp =
mailing list.

The poll ends on June 9th 2009.

/Loa


--=20


Loa Andersson

Sr Strategy and Standards Manager    phone:  +46 10 717 52 13
Ericsson ///                                 +46 767 72 92 13=20


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


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

From loa@pi.nu  Mon Jun  1 05:55:59 2009
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 6961C28C1A0; Mon,  1 Jun 2009 05:55:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xt2GdIK+UToJ; Mon,  1 Jun 2009 05:55:57 -0700 (PDT)
Received: from mail.pi.nu (mail.pi.nu [194.71.127.148]) by core3.amsl.com (Postfix) with ESMTP id 8910D28C15C; Mon,  1 Jun 2009 05:55:57 -0700 (PDT)
Received: from [192.36.158.96] (wdhcp-158-96.verkstad.net [192.36.158.96]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: loa@pi.nu) by mail.pi.nu (Postfix) with ESMTPSA id DA0C2D404F; Mon,  1 Jun 2009 14:55:55 +0200 (CEST)
Message-ID: <4A23CFD9.2060101@pi.nu>
Date: Mon, 01 Jun 2009 14:55:53 +0200
From: Loa Andersson <loa@pi.nu>
User-Agent: Thunderbird 2.0.0.21 (Windows/20090302)
MIME-Version: 1.0
To: mpls-tp@ietf.org, mpls@ietf.org, pwe3@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: [PWE3] new working group draft
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: <http://www.ietf.org/mail-archive/web/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, 01 Jun 2009 12:55:59 -0000

All,

I've instructed the authors of draft-bryant-mpls-tp-ach-tlv-02
to publish the draft as a mpls working group draft, as
draft-ietf-mpls-tp-ach-tlv-00

The reason is that the draft is closely related with the
gach-gal and gach-dcn draft that are progressing as working
group draft and we need the tlv draft to be able to
progress those drafts.

In this case I've bypassed the normal poll we do for working
documents, and taken the decisiion as working group chair.

/Loa


-- 


Loa Andersson

Sr Strategy and Standards Manager    phone:  +46 10 717 52 13
Ericsson ///                                 +46 767 72 92 13 


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



From stbryant@cisco.com  Mon Jun  1 05:59:00 2009
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 D99EE3A68AD; Mon,  1 Jun 2009 05:59:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.449
X-Spam-Level: 
X-Spam-Status: No, score=-8.449 tagged_above=-999 required=5 tests=[AWL=-1.850, 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 il6kjSzA2BMp; Mon,  1 Jun 2009 05:59:00 -0700 (PDT)
Received: from sj-iport-2.cisco.com (sj-iport-2.cisco.com [171.71.176.71]) by core3.amsl.com (Postfix) with ESMTP id 31C3D3A6843; Mon,  1 Jun 2009 05:59:00 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.41,284,1241395200"; d="scan'208";a="170951583"
Received: from ams-dkim-2.cisco.com ([144.254.224.139]) by sj-iport-2.cisco.com with ESMTP; 01 Jun 2009 12:58:59 +0000
Received: from ams-core-1.cisco.com (ams-core-1.cisco.com [144.254.224.150]) by ams-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id n51CwwhF010635;  Mon, 1 Jun 2009 14:58:58 +0200
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 n51Cww4Z029391; Mon, 1 Jun 2009 12:58:58 GMT
Received: from dhcp-bdlk09-vlan301-data-64-103-105-5.cisco.com (localhost [127.0.0.1]) by cisco.com (8.11.7p3+Sun/8.8.8) with ESMTP id n51Cwwf05268; Mon, 1 Jun 2009 13:58:58 +0100 (BST)
Message-ID: <4A23D092.8010005@cisco.com>
Date: Mon, 01 Jun 2009 13:58:58 +0100
From: Stewart Bryant <stbryant@cisco.com>
User-Agent: Thunderbird 2.0.0.19 (Macintosh/20081209)
MIME-Version: 1.0
To: Loa Andersson <loa@pi.nu>
References: <4A1BB784.7030501@pi.nu>
In-Reply-To: <4A1BB784.7030501@pi.nu>
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=459; t=1243861138; x=1244725138; c=relaxed/simple; s=amsdkim2001; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=stbryant@cisco.com; z=From:=20Stewart=20Bryant=20<stbryant@cisco.com> |Subject:=20Re=3A=20[mpls]=20poll=20on=20the=20Rosetta=20St one=20draft |Sender:=20; bh=5AM9CqO4XplyfDWzYlap7TXW05M6ivvyj5NlXg4YFYw=; b=jynGk05mUhuMpMAX1jlFSf+Vi+UDxQ3+9QZ6u0M2Sgx8LAlcjNrY4TuAg6 FyFX2zOduq9Y2kWy1/8sQ/NvV/sWlI7pEmc99htjjPM7eMAdp0JXGnIHzxwP LZr6QcnODH;
Authentication-Results: ams-dkim-2; header.From=stbryant@cisco.com; dkim=pass ( sig from cisco.com/amsdkim2001 verified; ); 
Cc: mpls@ietf.org, pwe3@ietf.org, mpls-tp@ietf.org
Subject: Re: [PWE3] [mpls] poll on the Rosetta Stone draft
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: <http://www.ietf.org/mail-archive/web/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, 01 Jun 2009 12:59:00 -0000

> this is to start a two week poll on the suggestion to make the
> draft-helvoort-mpls-tp-rosetta-stone-00 an MPLS working group
> document.
>
Normally we would require a draft to be in a cleaner
state before accepting it as a WG draft. None-the-less
I support this being a WG draft.

One question - I assume that it will not be published
as an RFC for a while so that we can continue to
add new terms to it as the project progresses.

Stewart

From Martin.Vigoureux@alcatel-lucent.com  Mon Jun  1 06:00:45 2009
Return-Path: <Martin.Vigoureux@alcatel-lucent.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 4CB783A6A03 for <pwe3@core3.amsl.com>; Mon,  1 Jun 2009 06:00:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.505
X-Spam-Level: 
X-Spam-Status: No, score=-5.505 tagged_above=-999 required=5 tests=[AWL=0.744,  BAYES_00=-2.599, HELO_EQ_FR=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id c-3huNzmRQ2h for <pwe3@core3.amsl.com>; Mon,  1 Jun 2009 06:00:44 -0700 (PDT)
Received: from smail5.alcatel.fr (smail5.alcatel.fr [62.23.212.27]) by core3.amsl.com (Postfix) with ESMTP id 253163A68AD for <pwe3@ietf.org>; Mon,  1 Jun 2009 06:00:43 -0700 (PDT)
Received: from FRVELSBHS06.ad2.ad.alcatel.com (frvelsbhs06.dc-m.alcatel-lucent.com [155.132.6.78]) by smail5.alcatel.fr (8.13.8/8.13.8/ICT) with ESMTP id n51D0KqN015751;  Mon, 1 Jun 2009 15:00:20 +0200
Received: from [172.27.205.109] ([172.27.205.109]) by FRVELSBHS06.ad2.ad.alcatel.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.3959); Mon, 1 Jun 2009 15:00:20 +0200
Message-ID: <4A23D0E3.9070107@alcatel-lucent.com>
Date: Mon, 01 Jun 2009 15:00:19 +0200
From: Martin Vigoureux <martin.vigoureux@alcatel-lucent.com>
Organization: Alcatel-Lucent
User-Agent: Thunderbird 2.0.0.19 (Windows/20081209)
MIME-Version: 1.0
To: Stewart Bryant <stbryant@cisco.com>, Matthew Bocci <matthew.bocci@alcatel-lucent.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
X-OriginalArrivalTime: 01 Jun 2009 13:00:20.0212 (UTC) FILETIME=[EB0CE340:01C9E2B8]
X-Scanned-By: MIMEDefang 2.57 on 155.132.188.13
Cc: George Swallow <swallow@cisco.com>, pwe3@ietf.org
Subject: [PWE3] [Fwd: Re: [mpls] mpls wg last call on draft-ietf-pwe3-mpls-transport-03]
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: <http://www.ietf.org/mail-archive/web/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, 01 Jun 2009 13:00:45 -0000

Dear Working Group Chairs,

the MPLS WG Last Call has ended.
No comment was posted on the MPLS WG list.
The MPLS WG is comfortable with the fact that you progress the draft.

martin

-------- Message original --------
Sujet : Re: [mpls] mpls wg last call on draft-ietf-pwe3-mpls-transport-03
Date : Mon, 01 Jun 2009 14:53:41 +0200
De : Martin Vigoureux <martin.vigoureux@alcatel-lucent.com>
Organisation : Alcatel-Lucent
Pour : mpls@ietf.org
Références : <4A1132A8.5020807@pi.nu>

Dear all,

the LC has ended. No comment was posted on the list.

martin

Loa Andersson a écrit :
> Working group,
> 
> we been asked by the pwe3 chairs to start a mpls working group
> last call on:
> 
> http://tools.ietf.org/html/draft-ietf-pwe3-mpls-transport-03
> 
> This mail starts a one week working group last call. The draft has
> already been working group last called in the pwe3 working group,\
> and the last called were copied to the mpls-tp list.
> 
> The last call ends May 25th.
> 
> Please send your comments to the pwe3 and mpls mailing lists.
> 
> Loa and George
> 


From loa@pi.nu  Mon Jun  1 06:06:19 2009
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 974643A7134; Mon,  1 Jun 2009 06:06:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id udvPk0IQhsXd; Mon,  1 Jun 2009 06:06:18 -0700 (PDT)
Received: from mail.pi.nu (mail.pi.nu [194.71.127.148]) by core3.amsl.com (Postfix) with ESMTP id B42C53A6B04; Mon,  1 Jun 2009 06:06:18 -0700 (PDT)
Received: from [192.36.158.96] (wdhcp-158-96.verkstad.net [192.36.158.96]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: loa@pi.nu) by mail.pi.nu (Postfix) with ESMTPSA id F1752D404F; Mon,  1 Jun 2009 15:06:16 +0200 (CEST)
Message-ID: <4A23D245.4070609@pi.nu>
Date: Mon, 01 Jun 2009 15:06:13 +0200
From: Loa Andersson <loa@pi.nu>
User-Agent: Thunderbird 2.0.0.21 (Windows/20090302)
MIME-Version: 1.0
To: stbryant@cisco.com
References: <4A1BB784.7030501@pi.nu> <4A23D092.8010005@cisco.com>
In-Reply-To: <4A23D092.8010005@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: mpls@ietf.org, pwe3@ietf.org, mpls-tp@ietf.org
Subject: Re: [PWE3] [mpls] poll on the Rosetta Stone draft
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: <http://www.ietf.org/mail-archive/web/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, 01 Jun 2009 13:06:19 -0000

Stewart,

you are right on both accounts, I'd also like to see a cleaner
draft, but think that the the draft is mature enough.

In my mind the Rosetta Stone draft will be the last of the
first set (first set = very poorly defined) of MPLS-TP drafts that
we progress to RFCs, we need a terminology that is stable.

/Loa


Stewart Bryant wrote:
> 
>> this is to start a two week poll on the suggestion to make the
>> draft-helvoort-mpls-tp-rosetta-stone-00 an MPLS working group
>> document.
>>
> Normally we would require a draft to be in a cleaner
> state before accepting it as a WG draft. None-the-less
> I support this being a WG draft.
> 
> One question - I assume that it will not be published
> as an RFC for a while so that we can continue to
> add new terms to it as the project progresses.
> 
> Stewart

-- 


Loa Andersson

Sr Strategy and Standards Manager    phone:  +46 10 717 52 13
Ericsson ///                                 +46 767 72 92 13 


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



From Markus.Lautenschlager@telekom.de  Tue Jun  2 05:56:21 2009
Return-Path: <Markus.Lautenschlager@telekom.de>
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 605FA3A6CC7; Tue,  2 Jun 2009 05:56:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.249
X-Spam-Level: 
X-Spam-Status: No, score=-3.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=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 8EgXHKImzEux; Tue,  2 Jun 2009 05:56:20 -0700 (PDT)
Received: from tcmail83.telekom.de (tcmail83.telekom.de [62.225.183.131]) by core3.amsl.com (Postfix) with ESMTP id 84E663A6A50; Tue,  2 Jun 2009 05:56:18 -0700 (PDT)
Received: from s4de8nsaaml.bmbg.telekom.de (HELO S4DE8NSAAML.sued.t-com.de) ([10.175.163.143]) by tcmail81.telekom.de with ESMTP; 02 Jun 2009 14:55:42 +0200
Received: from S4DE8DSAAGK.sued.t-com.de ([10.134.164.59]) by S4DE8NSAAML.sued.t-com.de with Microsoft SMTPSVC(6.0.3790.3959); Tue, 2 Jun 2009 14:55:30 +0200
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: Tue, 2 Jun 2009 14:55:29 +0200
Message-ID: <36081A6B2097944FBFBFCD658F1A9F68039CA03B@S4DE8DSAAGK.sued.t-com.de>
In-reply-to: <4A23D245.4070609@pi.nu>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [PWE3] [mpls] poll on the Rosetta Stone draft
Thread-Index: AcniudjxBvRLwq2OSV6o/Cw+GTbfKgAx1YYA
References: <4A1BB784.7030501@pi.nu> <4A23D092.8010005@cisco.com> <4A23D245.4070609@pi.nu>
From: <Markus.Lautenschlager@telekom.de>
To: <mpls-tp@ietf.org>, <pwe3@ietf.org>
X-OriginalArrivalTime: 02 Jun 2009 12:55:30.0496 (UTC) FILETIME=[68C77C00:01C9E381]
Subject: Re: [PWE3] [mpls] poll on the Rosetta Stone draft
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: <http://www.ietf.org/mail-archive/web/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, 02 Jun 2009 12:56:21 -0000

=20
I support the draft to be a WG draft


Mit freundlichen Gr=FC=DFen=20
Markus Lautenschlager=20


Deutsche Telekom Netzproduktion GmbH=20
Zentrum Technik Einf=FChrung
Dipl. Ing. Dipl. Wirtsch. Ing.=20
Markus Lautenschlager=20
TE241-11=20
Hansastr. 35, 90441 N=FCrnberg=20
+49 911 150 4233 (Tel.)=20
+49 951 91733648 (Fax)=20
+49 160 90719250 (Mobil)=20
E-Mail: Markus.Lautenschlager@telekom.de
http://www.telekom.com=20

Deutsche Telekom Netzproduktion GmbH=20
Aufsichtsrat: Timotheus H=F6ttges (Vorsitzender)=20
Gesch=E4ftsf=FChrung: Friedrich Fu=DF (Vorsitzender), Albert Matheis, =
Klaus Peren=20
Handelsregister: Amtsgericht Bonn HRB 14190=20
Sitz der Gesellschaft: Bonn=20
USt-IdNr.: DE 814645262

Erleben, was verbindet.

-----Urspr=FCngliche Nachricht-----
Von: pwe3-bounces@ietf.org [mailto:pwe3-bounces@ietf.org] Im Auftrag von =
Loa Andersson
Gesendet: Montag, 1. Juni 2009 15:06
An: stbryant@cisco.com
Cc: mpls@ietf.org; pwe3@ietf.org; mpls-tp@ietf.org
Betreff: Re: [PWE3] [mpls] poll on the Rosetta Stone draft

Stewart,

you are right on both accounts, I'd also like to see a cleaner
draft, but think that the the draft is mature enough.

In my mind the Rosetta Stone draft will be the last of the
first set (first set =3D very poorly defined) of MPLS-TP drafts that
we progress to RFCs, we need a terminology that is stable.

/Loa


Stewart Bryant wrote:
>=20
>> this is to start a two week poll on the suggestion to make the
>> draft-helvoort-mpls-tp-rosetta-stone-00 an MPLS working group
>> document.
>>
> Normally we would require a draft to be in a cleaner
> state before accepting it as a WG draft. None-the-less
> I support this being a WG draft.
>=20
> One question - I assume that it will not be published
> as an RFC for a while so that we can continue to
> add new terms to it as the project progresses.
>=20
> Stewart

--=20


Loa Andersson

Sr Strategy and Standards Manager    phone:  +46 10 717 52 13
Ericsson ///                                 +46 767 72 92 13=20


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


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

From stbryant@cisco.com  Tue Jun  2 11:51:14 2009
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 1BE153A6F0A for <pwe3@core3.amsl.com>; Tue,  2 Jun 2009 11:51:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.832
X-Spam-Level: 
X-Spam-Status: No, score=-9.832 tagged_above=-999 required=5 tests=[AWL=0.767,  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 2EeGz62zSsww for <pwe3@core3.amsl.com>; Tue,  2 Jun 2009 11:51:12 -0700 (PDT)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140]) by core3.amsl.com (Postfix) with ESMTP id 355DD3A67AE for <pwe3@ietf.org>; Tue,  2 Jun 2009 11:51:12 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.41,292,1241395200"; d="scan'208";a="41870593"
Received: from ams-dkim-2.cisco.com ([144.254.224.139]) by ams-iport-1.cisco.com with ESMTP; 02 Jun 2009 18:51:12 +0000
Received: from ams-core-1.cisco.com (ams-core-1.cisco.com [144.254.224.150]) by ams-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id n52IpCpi004866 for <pwe3@ietf.org>; Tue, 2 Jun 2009 20:51:12 +0200
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 n52IpBkJ007683 for <pwe3@ietf.org>; Tue, 2 Jun 2009 18:51:11 GMT
Received: from dhcp-gpk02-vlan300-64-103-65-102.cisco.com (localhost [127.0.0.1]) by cisco.com (8.11.7p3+Sun/8.8.8) with ESMTP id n52IpBo18148; Tue, 2 Jun 2009 19:51:11 +0100 (BST)
Message-ID: <4A25749E.301@cisco.com>
Date: Tue, 02 Jun 2009 19:51:10 +0100
From: Stewart Bryant <stbryant@cisco.com>
User-Agent: Thunderbird 2.0.0.19 (Macintosh/20081209)
MIME-Version: 1.0
To: stbryant@cisco.com
References: <49FAD530.4050406@cisco.com>
In-Reply-To: <49FAD530.4050406@cisco.com>
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=657; t=1243968672; x=1244832672; c=relaxed/simple; s=amsdkim2001; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=stbryant@cisco.com; z=From:=20Stewart=20Bryant=20<stbryant@cisco.com> |Subject:=20Re=3A=20[PWE3]=20WG=20Last=20Call=20for=20draft -ietf-pwe3-oam-msg-map-10 |Sender:=20; bh=s5nHtEj6c9EOtqdI4Q9mAIEJEcHBSoOm2+c9i9TAthY=; b=D9NR7bSeq9fL62nrd3T4UOzPZpck+QNbJcB4lXj/QXIhY2ODOZyhMKGefv fOQwmnsY5ZFaWF09hOYcSJPY5iCFdmQ7+GUBX0prIsYjPXDxQ1HDRr5LlHhZ YXCc0PzusV;
Authentication-Results: ams-dkim-2; header.From=stbryant@cisco.com; dkim=pass ( sig from cisco.com/amsdkim2001 verified; ); 
Cc: pwe3 <pwe3@ietf.org>
Subject: Re: [PWE3] WG Last Call for draft-ietf-pwe3-oam-msg-map-10
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: <http://www.ietf.org/mail-archive/web/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, 02 Jun 2009 18:51:14 -0000

Stewart Bryant wrote:
>
> This is the WG Last Call for
>
> draft-ietf-pwe3-oam-msg-map-10
>
> http://www.ietf.org/internet-drafts/draft-ietf-pwe3-oam-msg-map-10.txt
>
> Please send comments to the list by Friday 22nd May
>
> Thanks
>
> Stewart
> _______________________________________________
> pwe3 mailing list
> pwe3@ietf.org
> https://www.ietf.org/mailman/listinfo/pwe3
>
Last call for this has ended and I have seen only one comment

http://www.ietf.org/mail-archive/web/pwe3/current/msg10386.html

Please can I ask the authors to make the correction and
we will send the draft to the ADs for review and publication

Stewart



From wwwrun@core3.amsl.com  Tue Jun  2 13:01:28 2009
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 AD1CA28C17E; Tue,  2 Jun 2009 13:01:28 -0700 (PDT)
X-idtracker: yes
To: IETF-Announce <ietf-announce@ietf.org> 
From: The IESG <iesg-secretary@ietf.org>
Message-Id: <20090602200128.AD1CA28C17E@core3.amsl.com>
Date: Tue,  2 Jun 2009 13:01:28 -0700 (PDT)
Cc: pwe3@ietf.org
Subject: [PWE3] Last Call: draft-ietf-pwe3-ms-pw-arch (An Architecture for Multi-Segment Pseudowire Emulation Edge-to-Edge) to Informational RFC
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: ietf@ietf.org
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: <http://www.ietf.org/mail-archive/web/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, 02 Jun 2009 20:01:28 -0000

The IESG has received a request from the Pseudowire Emulation Edge to 
Edge WG (pwe3) to consider the following document:

- 'An Architecture for Multi-Segment Pseudowire Emulation Edge-to-Edge '
   <draft-ietf-pwe3-ms-pw-arch-06.txt> as an Informational RFC

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action.  Please send substantive comments to the
ietf@ietf.org mailing lists by 2009-06-16. Exceptionally, 
comments may be sent to iesg@ietf.org instead. In either case, please 
retain the beginning of the Subject line to allow automated sorting.

The file can be obtained via
http://www.ietf.org/internet-drafts/draft-ietf-pwe3-ms-pw-arch-06.txt


IESG discussion can be tracked via
https://datatracker.ietf.org/public/pidtracker.cgi?command=view_id&dTag=14143&rfc_flag=0


From lmartini@cisco.com  Tue Jun  2 13:17:29 2009
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 9ACDF3A7048; Tue,  2 Jun 2009 13:17:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.665
X-Spam-Level: 
X-Spam-Status: No, score=-1.665 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, J_CHICKENPOX_32=0.6]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6qOt3BJwsf6J; Tue,  2 Jun 2009 13:17:28 -0700 (PDT)
Received: from napoleon.monoski.com (napoleon.monoski.com [67.41.208.110]) by core3.amsl.com (Postfix) with ESMTP id 845863A7024; Tue,  2 Jun 2009 13:17:28 -0700 (PDT)
Received: from confusion.monoski.com (confusion.monoski.com [209.245.27.2]) (authenticated bits=0) by napoleon.monoski.com (8.13.8/8.13.8) with ESMTP id n52KHGd9011344 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 2 Jun 2009 14:17:17 -0600 (MDT)
Message-ID: <4A2588CC.2030502@cisco.com>
Date: Tue, 02 Jun 2009 14:17:16 -0600
From: Luca Martini <lmartini@cisco.com>
User-Agent: Thunderbird 2.0.0.19 (X11/20081209)
MIME-Version: 1.0
To: Sherry Xue <xueli@huawei.com>
References: <!&!AAAAAAAAAAAYAAAAAAAAAPMlHu4Uz9lFgBeeMEjMDZDCgAAAEAAAAGwaQ37ol8FHh5TinAuGcp4BAAAAAA==@huawei.com>
In-Reply-To: <!&!AAAAAAAAAAAYAAAAAAAAAPMlHu4Uz9lFgBeeMEjMDZDCgAAAEAAAAGwaQ37ol8FHh5TinAuGcp4BAAAAAA==@huawei.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Scanned-By: MIMEDefang 2.63 on 209.245.27.1
Cc: l2vpn@ietf.org, pwe3@ietf.org
Subject: Re: [PWE3] Some comments on draft-ietf-pwe3-segmented-pw-11
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: <http://www.ietf.org/mail-archive/web/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, 02 Jun 2009 20:17:29 -0000

Sherry Xue wrote:
> Hi,
> I have reviewed the draft-ietf-pwe3-segmented-pw-11, and have some comments,
> please find below.
>
> 1)	Section 4, some confused about figure 2, there are two "emulated
> service" identifiers, between the egress of CE1 and ingress of CE2, also
> between the ingress of PE1 and the egress of PE4.Does some amendment should
> be done to avoid the reduplicate emulated service?
>
>   
yes, it a mistake in the picture it now says: "Multi-Segment Pseudowire" 
at the top.

> 2)	Section 4, in the penultimate paragraph, "this document describes
> procedures for building multi-segment pseudo wires using manual
> configuration of the switching point PE2", the Switching point" PE2" should
> be "S-PE "which will be coincident with figure 3. And the identifier of the
> Switch point in the sentence should be consistent with figure 3. 
>
>   
it needs to be "PE1" I fixed it.

> 3)	Section 4, in the last paragraph, " no control messages are
> exchanged yet as the S-PE PE dose not have.", there are a redundant "PE",
> please delete it.
>
>   
done.
> 4)	Section 4, in the last paragraph, sentence as "first the S-PE is
> configured to switch a SS-PW from a specific peer to another SS-PW destined
> for a different peer".
>  I have some confusion about SS-PW definition used in the MS-PW as PW
> segment role. SS-PW is defined as "a PW setup directly between two T-PE
> devices. Each PW in one direction of a SS-PW traverses one PSN tunnel that
> connects the two T-PEs." in the terminology section of [segmented-pw]. But
>   
yes, it seems that the definition in  rfc5254 is incorrect.

> SS-PW is defined "a PW setup directly between two PE devices. Each direction
> of an SS-PW traverses one PSN tunnel that connects the two PEs" in RFC5254.
> They are different, because SS-PW is terminated on different PE roles, T-PE
> in former case, T-PE or S-PE in latter case. 
> IMO, SS-PW should be setup between TWO T-PE devices, there are some
> differences between SS-PW and PW segment. If it is right, the SS-PW could
> not be used the same as PW segment. So the sentence should be restructured
> as "first the S-PE is configured to switch a PW segment from a specific peer
> to another PW segment destined for a different peer...".  And concerted
> action should be taken in the draft.
>
>   
yes , this is correct , I will change it.
I also corrected this later in the status section.
> 5)	Section 7, in the first paragraph, the nomenclature should be
> identical with figure 3, such as PE2, PE3 should be amended as S-PE and
> T-PE, etc.
>
>   
yes this was already fixed as pointed out by Stewart.
( I have not yet sent out the revised version.)

> 6)	Section 7.4, in the second sentence, Should the"PW switching point
> TLV" in line 3 be "S-PE TLV"? In the fourth and fifth paragraphs, should the
> "PW switching point TLV" in line 1 be "S-PE TLV"?
>
>   
no, it's a personal editing choice, either way it's fine.

> 7)	Section 7.4.1, The title of section 7.4.1 should be accordant with
> the title of section 7.4, so "S-PE sub-TLV" may be better?
>
>   
I changed sec 7 , as strictly speaking i cannot use the abbreviation in 
the title.
the RFC editor would have corrected that.

> 8)	Section 8, the title, "MPLS-PW to PW-L2TPv3 control plane switching"
> may be amended as "MPLS-PW to L2TPv3-PW control plane switching"
>
>   
yes, fixed.

> 9)	Section 8.4.1, I have some confused about the session establishment.
> In the two example exchanges of message, I understand that the MS-PW is
> setup in one direction totally, and then the other direction. Dose I make a
> mistake? Now I have a question, take L2TPv2 PW- MPLS PW for example, whether
> the L2tpv3 ICRP must be send after the LDP label mapping receiving from the
> PE3? Should the PW switching node, map to LDP Label mapping forward and send
> L2TPv3 ICRP backwards simultaneity? 
>
>   
Both cases work fine. It really depends who starts the process first : 
the L2TPv3 side or the MPLS side.

> And I have a question, which is why VCCV CC type 2 is not supported for
> MS-PW? I think the reason is that the P device, which is neither S-PE nor
> T-PE, is not responsible to inspect the VCCV message? That is right?
>
>   
No. The problem is in processing the router attention label ( label 1). 
Also the real reason is that this mode is redundant , and was only 
supported to accommodate hardware limitations at the time when the VCCV 
document was written. This is no mode is longer necessary.

Thanks for all your good comments !
I really appreciate a fresh set of eyes reading this document.

Luca


> Regards 
>
> Sherry
>
>
>
>   


From lmartini@cisco.com  Tue Jun  2 14:30:27 2009
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 84B943A68E0; Tue,  2 Jun 2009 14:30:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.965
X-Spam-Level: 
X-Spam-Status: No, score=-1.965 tagged_above=-999 required=5 tests=[AWL=0.300,  BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id afU+iCPgXjYX; Tue,  2 Jun 2009 14:30:26 -0700 (PDT)
Received: from napoleon.monoski.com (napoleon.monoski.com [67.41.208.110]) by core3.amsl.com (Postfix) with ESMTP id 854693A6980; Tue,  2 Jun 2009 14:30:26 -0700 (PDT)
Received: from confusion.monoski.com (confusion.monoski.com [209.245.27.2]) (authenticated bits=0) by napoleon.monoski.com (8.13.8/8.13.8) with ESMTP id n52LSbMq013119 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 2 Jun 2009 15:28:38 -0600 (MDT)
Message-ID: <4A259985.90007@cisco.com>
Date: Tue, 02 Jun 2009 15:28:37 -0600
From: Luca Martini <lmartini@cisco.com>
User-Agent: Thunderbird 2.0.0.19 (X11/20081209)
MIME-Version: 1.0
To: iana@iana.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Scanned-By: MIMEDefang 2.63 on 209.245.27.1
Cc: "mpls@ietf.org" <mpls@ietf.org>, "PWE3 WG \(E-mail\)" <pwe3@ietf.org>
Subject: [PWE3] Typo in LDP FEC TYPE NAME SPACE registry.
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: <http://www.ietf.org/mail-archive/web/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, 02 Jun 2009 21:30:27 -0000

Iana,

The registry LDP FEC TYPE NAME SPACE, contains the following error:

OLD:

Value    Hex    Name                                Reference
-------  -----  -----------------------------       ---------
~
80       0x80   PWid FEC Element                    [RFC4447]
81       0x81   Generalized PWid FEC Element        [RFC4447]
82-191          Unassigned
~


NEW:
Value    Hex    Name                                Reference
-------  -----  -----------------------------       ---------
~
82-127          Unassigned
128      0x80   PWid FEC Element                    [RFC4447]
129      0x81   Generalized PWid FEC Element        [RFC4447]
130-191         Unassigned
~


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

Basically the error is in the Hex to Decimal conversion. 0x80 is equal to 128 decimal , not 80 decimal.
Please refer to RFC4447 which requests allocation of 0x80 and 0x81 in sec 7.3.

Thanks.
Luca





From enrique@alcatel-lucent.com  Wed Jun  3 07:12:25 2009
Return-Path: <enrique@alcatel-lucent.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 885DE3A6B49; Wed,  3 Jun 2009 07:12:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XGkZRjslTKrM; Wed,  3 Jun 2009 07:12:24 -0700 (PDT)
Received: from ihemail4.lucent.com (ihemail4.lucent.com [135.245.0.39]) by core3.amsl.com (Postfix) with ESMTP id B4EB13A6E01; Wed,  3 Jun 2009 07:12:24 -0700 (PDT)
Received: from ihrh1.emsr.lucent.com (h135-1-218-53.lucent.com [135.1.218.53]) by ihemail4.lucent.com (8.13.8/IER-o) with ESMTP id n53ECMnR010872;  Wed, 3 Jun 2009 09:12:22 -0500 (CDT)
Received: from USNAVSXCHHUB02.ndc.alcatel-lucent.com (usnavsxchhub02.ndc.alcatel-lucent.com [135.3.39.111]) by ihrh1.emsr.lucent.com (8.13.8/emsr) with ESMTP id n53ECJkE013763; Wed, 3 Jun 2009 09:12:21 -0500 (CDT)
Received: from USNAVSXCHMBSA2.ndc.alcatel-lucent.com ([135.3.39.127]) by USNAVSXCHHUB02.ndc.alcatel-lucent.com ([135.3.39.111]) with mapi; Wed, 3 Jun 2009 09:12:08 -0500
From: "Hernandez-Valencia, Enrique (Enrique)" <enrique@alcatel-lucent.com>
To: "'Loa Andersson'" <loa@pi.nu>, "'mpls-tp@ietf.org'" <mpls-tp@ietf.org>, "'mpls@ietf.org'" <mpls@ietf.org>, "'pwe3@ietf.org'" <pwe3@ietf.org>
Date: Wed, 3 Jun 2009 09:12:05 -0500
Thread-Topic: [mpls] poll on the Rosetta Stone draft
Thread-Index: Acnd5SUoB7MTFDObR3WxmvtxQWGHsAGcBfag
Message-ID: <25F56B1AA5E4FE48A6E5FD92CA1F95862B6A4E68@USNAVSXCHMBSA2.ndc.alcatel-lucent.com>
References: <4A1BB784.7030501@pi.nu>
In-Reply-To: <4A1BB784.7030501@pi.nu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.39
Subject: Re: [PWE3] [mpls] poll on the Rosetta Stone draft
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: <http://www.ietf.org/mail-archive/web/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, 03 Jun 2009 14:12:25 -0000

Support.

-----Original Message-----
From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf Of Loa=
 Andersson
Sent: Tuesday, May 26, 2009 5:34 AM
To: mpls-tp@ietf.org; mpls@ietf.org; pwe3@ietf.org
Subject: [mpls] poll on the Rosetta Stone draft

All,

this is to start a two week poll on the suggestion to make the
draft-helvoort-mpls-tp-rosetta-stone-00 an MPLS working group
document.

Please send your comments (approval or disapproval) to the mpls-tp
mailing list.

The poll ends on June 9th 2009.

/Loa


--=20


Loa Andersson

Sr Strategy and Standards Manager    phone:  +46 10 717 52 13
Ericsson ///                                 +46 767 72 92 13=20


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


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

From root@core3.amsl.com  Wed Jun  3 11:00:02 2009
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 EEAC03A6AA6; Wed,  3 Jun 2009 11:00:01 -0700 (PDT)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20090603180001.EEAC03A6AA6@core3.amsl.com>
Date: Wed,  3 Jun 2009 11:00:01 -0700 (PDT)
Cc: pwe3@ietf.org
Subject: [PWE3] I-D Action:draft-ietf-pwe3-segmented-pw-12.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: <http://www.ietf.org/mail-archive/web/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, 03 Jun 2009 18:00: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 Pseudowire
	Author(s)       : L. Martini, et al.
	Filename        : draft-ietf-pwe3-segmented-pw-12.txt
	Pages           : 43
	Date            : 2009-06-03

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-12.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-12.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

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


--NextPart--

From web-usrn@ISI.EDU  Thu Jun  4 06:17:08 2009
Return-Path: <web-usrn@ISI.EDU>
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 4C3DB3A6E7B for <pwe3@core3.amsl.com>; Thu,  4 Jun 2009 06:17:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.389
X-Spam-Level: 
X-Spam-Status: No, score=-17.389 tagged_above=-999 required=5 tests=[AWL=0.210, BAYES_00=-2.599, USER_IN_DEF_WHITELIST=-15]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RuZmdwoxpD4g for <pwe3@core3.amsl.com>; Thu,  4 Jun 2009 06:17:07 -0700 (PDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by core3.amsl.com (Postfix) with ESMTP id 5D3DF3A68AD for <pwe3@ietf.org>; Thu,  4 Jun 2009 06:17:07 -0700 (PDT)
Received: from boreas.isi.edu (localhost [127.0.0.1]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id n54DDa84016078 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 4 Jun 2009 06:13:37 -0700 (PDT)
Received: (from web-usrn@localhost) by boreas.isi.edu (8.13.8/8.13.8/Submit) id n54DDZQs016074; Thu, 4 Jun 2009 06:13:35 -0700 (PDT)
Date: Thu, 4 Jun 2009 06:13:35 -0700 (PDT)
Message-Id: <200906041313.n54DDZQs016074@boreas.isi.edu>
To: nabil.bitar@verizon.com, matthew.bocci@alcatel-lucent.co.uk, lmartini@cisco.com, rdroms@cisco.com, jari.arkko@piuha.net, stbryant@cisco.com, matthew.bocci@alcatel-lucent.com
From: RFC Errata System <rfc-editor@rfc-editor.org>
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: web-usrn@boreas.isi.edu
Cc: rfc-editor@rfc-editor.org, pwe3@ietf.org, stbryant@cisco.com
Subject: [PWE3] [Editorial Errata Reported] RFC5254 (1792)
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: <http://www.ietf.org/mail-archive/web/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, 04 Jun 2009 13:17:08 -0000

The following errata report has been submitted for RFC5254,
"Requirements for Multi-Segment Pseudowire Emulation Edge-to-Edge (PWE3)".

--------------------------------------
You may review the report below and at:
http://www.rfc-editor.org/errata_search.php?rfc=5254&eid=1792

--------------------------------------
Type: Editorial
Reported by: Stewart Bryant <stbryant@cisco.com>

Section: 2

Original Text
-------------
Single-Segment Pseudowire (SS-PW).  

A PW setup directly between two PE devices.  Each direction of an SS-PW traverses one PSN tunnel that connects the two PEs.



Corrected Text
--------------
Single-Segment Pseudowire (SS-PW). 

A PW setup directly between two T-PE devices. Each PW in one direction of a SS-PW traverses one PSN tunnel that connects the two T-PEs.


Notes
-----
The document defines two types of PE, T-PE and S-PE. An SS-PW can only exist between a pair of T-PEs, so this is an editorial rather than a technical errata.

This errata aligns the definition of SS-PW with draft-ietf-pwe3-ms-pw-arch

Instructions:
-------------
This errata is currently posted as "Reported". If necessary, please
use "Reply All" to discuss whether it should be verified or
rejected. When a decision is reached, the verifying party (IESG)
can log in to change the status and edit the report, if necessary. 

--------------------------------------
RFC5254 (draft-ietf-pwe3-ms-pw-requirements-07)
--------------------------------------
Title               : Requirements for Multi-Segment Pseudowire Emulation Edge-to-Edge (PWE3)
Publication Date    : October 2008
Author(s)           : N. Bitar, Ed., M. Bocci, Ed., L. Martini, Ed.
Category            : INFORMATIONAL
Source              : Pseudo Wire Emulation Edge to Edge
Area                : Internet
Stream              : IETF
Verifying Party     : IESG

From root@core3.amsl.com  Fri Jun  5 06:00:01 2009
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 CDF4D3A6898; Fri,  5 Jun 2009 06:00:01 -0700 (PDT)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20090605130001.CDF4D3A6898@core3.amsl.com>
Date: Fri,  5 Jun 2009 06:00:01 -0700 (PDT)
Cc: pwe3@ietf.org
Subject: [PWE3] I-D Action:draft-ietf-pwe3-vccv-bfd-05.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: <http://www.ietf.org/mail-archive/web/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, 05 Jun 2009 13:00: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-05.txt
	Pages           : 13
	Date            : 2009-06-05

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-05.txt

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

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

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

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


--NextPart--

From ostokes@extremenetworks.com  Fri Jun  5 07:02:55 2009
Return-Path: <ostokes@extremenetworks.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 9B9513A6C8F for <pwe3@core3.amsl.com>; Fri,  5 Jun 2009 07:02:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, 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 0iJZTVdJksj1 for <pwe3@core3.amsl.com>; Fri,  5 Jun 2009 07:02:49 -0700 (PDT)
Received: from ussc-casht-p1.extremenetworks.com (ussc-casht-p2.extremenetworks.com [207.179.9.62]) by core3.amsl.com (Postfix) with ESMTP id F17C33A6997 for <pwe3@ietf.org>; Fri,  5 Jun 2009 07:02:48 -0700 (PDT)
Received: from USEXCHANGE.corp.extremenetworks.com ([10.0.4.74]) by ussc-casht-p2.corp.extremenetworks.com ([10.255.181.88]) with mapi; Fri, 5 Jun 2009 07:02:51 -0700
From: Olen Stokes <ostokes@extremenetworks.com>
To: "pwe3@ietf.org" <pwe3@ietf.org>
Date: Fri, 5 Jun 2009 07:02:51 -0700
Thread-Topic: Questions on draft-martini-pwe3-iccp-01.txt
Thread-Index: Acnl5lAbmuz1bz0QSS6K0QRoYnHreA==
Message-ID: <6738A78F51650A4FAEDCF6844B26C21413554176FF@USEXCHANGE.corp.extremenetworks.com>
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_6738A78F51650A4FAEDCF6844B26C21413554176FFUSEXCHANGEcor_"
MIME-Version: 1.0
Subject: [PWE3] Questions on draft-martini-pwe3-iccp-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: <http://www.ietf.org/mail-archive/web/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, 05 Jun 2009 14:02:55 -0000

--_000_6738A78F51650A4FAEDCF6844B26C21413554176FFUSEXCHANGEcor_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

I have the following questions on draft-martini-pwe3-iccp-01.txt:

1)      In Section 4.1, it states that "the redundancy mechanism employed t=
owards the access node/network can be one of a multitude of technologies". =
 Are there any restrictions on the access network?  In particular, are ther=
e any restrictions about a given packet reaching both PE1 and PE2 from the =
access network in Figure 1?  If not, is it true that a packet received on a=
 PW at PE1 and sent toward the access network may reach PE2 via the access =
network?

2)      In Section 5.2, it states, "The RG will not become operational unti=
l the corresponding RG Connect Message has been received."  If a single nod=
e comes up and does not receive any ICCP capable announcements, does it bec=
ome operational?  What if it has been configured that a second node is supp=
osed to be present?  If so, what happens when a second node later advertise=
s that it is ICCP capable?  Is the RG operational between the second capabi=
lity announcement and the subsequent connect message?

3)      In Section 6, it states the following:

- BFD
       Run a BFD session [BFD] between the PEs that are members of a
       given RG, and use that to detect PE node failure. This assumes
       that resiliency mechanisms are in place to protect connectivity
       to the remote PE nodes, and hence loss of BFD periodic messages
       from a given PE node can only mean that the node itself has
       failed.

How is this guaranteed?  There can be n-links between two interconnected PE=
s in a Redundancy Group.  If the BFD session between the two PEs goes down,=
 all that is really known is that the two PEs cannot communicate over those=
 n-links.  How does this guarantee that the remote PE is not forwarding acc=
ess network data to the core network over other links?

Take a Redundancy Group as shown in Figure 1 where PE1 and PE2 are H-VPLS M=
TU-s switches with connections to the core.  Assume that they have dedicate=
d interconnection with n-links.  If somehow all n-interconnect links fail, =
then will not both nodes assume that the remote node has failed?  If so, th=
en it appears that a loop is very possible.  Losing connection to the core =
after a large number of failures would seem to be a better alternative than=
 any risk of a loop.

4)      Section 8.1.5 - It states that a PW Id TLV is "used to communicate =
the configuration of PWs for VPWS."  Is there some reason that this cannot =
be used with a (H)VPLS?  For example, there could be redundant MTUs that ar=
e connecting to a core group of PEs as discussed above.

5)      Section 8.1.5 - There is a Peer ID field included in the TLV.  What=
 is the intent of the Peer ID?

6)      Are there any provisions for when an access network might segment w=
ith part of the access network still having connectivity to one PE while th=
e remainder of the network has connectivity to the other PE?  I realize tha=
t how this condition is recognized may be out of the scope of this document=
, but how the PEs communicate this condition could potentially be included.

Thanks for your attention.

Cheers,
Olen







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

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Exchange Server">
<!-- converted from rtf -->
<style><!-- .EmailQuote { margin-left: 1pt; padding-left: 4pt; border-left:=
 #800000 2px solid; } --></style>
</head>
<body>
<font face=3D"Courier New, monospace" size=3D"2">
<div>I have the following questions on draft-martini-pwe3-iccp-01.txt:</div=
>
<div>&nbsp;</div>
<ol style=3D"margin-top: 0pt; margin-bottom: 0pt; margin-left: 36pt; ">
<li>In Section 4.1, it states that &#8220;the redundancy mechanism employed=
 towards the access node/network can be one of a multitude of technologies&=
#8221;.&nbsp; Are there any restrictions on the access network?&nbsp; In pa=
rticular, are there any restrictions about a given packet
reaching both PE1 and PE2 from the access network in Figure 1?&nbsp; If not=
, is it true that a packet received on a PW at PE1 and sent toward the acce=
ss network may reach PE2 via the access network?</li></ol>
<div style=3D"padding-left: 36pt; "><font face=3D"Calibri, sans-serif" size=
=3D"2">&nbsp;</font></div>
<ol start=3D"2" style=3D"margin-top: 0pt; margin-bottom: 0pt; margin-left: =
36pt; ">
<li>In Section 5.2, it states, &#8220;The RG will not become operational un=
til the corresponding RG Connect Message has been received.&#8221;&nbsp; If=
 a single node comes up and does not receive any ICCP capable announcements=
, does it become operational?&nbsp; What if it has been
configured that a second node is supposed to be present?&nbsp; If so, what =
happens when a second node later advertises that it is ICCP capable?&nbsp; =
Is the RG operational between the second capability announcement and the su=
bsequent connect message?&nbsp; </li></ol>
<div style=3D"padding-left: 36pt; "><font face=3D"Calibri, sans-serif" size=
=3D"2">&nbsp;</font></div>
<ol start=3D"3" style=3D"margin-top: 0pt; margin-bottom: 0pt; margin-left: =
36pt; ">
<li>In Section 6, it states the following:</li></ol>
<div style=3D"padding-left: 36pt; "><font face=3D"Calibri, sans-serif" size=
=3D"2">&nbsp;</font></div>
<div style=3D"padding-left: 36pt; ">- BFD</div>
<div style=3D"padding-left: 36pt; ">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Ru=
n a BFD session [BFD] between the PEs that are members of a</div>
<div style=3D"padding-left: 36pt; ">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; gi=
ven RG, and use that to detect PE node failure. This assumes</div>
<div style=3D"padding-left: 36pt; ">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; th=
at resiliency mechanisms are in place to protect connectivity</div>
<div style=3D"padding-left: 36pt; ">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; to=
 the remote PE nodes, and hence loss of BFD periodic messages</div>
<div style=3D"padding-left: 36pt; ">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; fr=
om a given PE node can only mean that the node itself has</div>
<div style=3D"padding-left: 36pt; ">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; fa=
iled.</div>
<div style=3D"padding-left: 36pt; "><font face=3D"Calibri, sans-serif" size=
=3D"2">&nbsp;</font></div>
<div style=3D"padding-left: 36pt; ">How is this guaranteed?&nbsp; There can=
 be n-links between two interconnected PEs in a Redundancy Group.&nbsp; If =
the BFD session between the two PEs goes down, all that is really known is =
that the two PEs cannot communicate over those
n-links.&nbsp; How does this guarantee that the remote PE is not forwarding=
 access network data to the core network over other links?&nbsp; </div>
<div style=3D"padding-left: 36pt; "><font face=3D"Calibri, sans-serif" size=
=3D"2">&nbsp;</font></div>
<div style=3D"padding-left: 36pt; ">Take a Redundancy Group as shown in Fig=
ure 1 where PE1 and PE2 are H-VPLS MTU-s switches with connections to the c=
ore.&nbsp; Assume that they have dedicated interconnection with n-links.&nb=
sp; If somehow all n-interconnect links fail,
then will not both nodes assume that the remote node has failed?&nbsp; If s=
o, then it appears that a loop is very possible.&nbsp; Losing connection to=
 the core after a large number of failures would seem to be a better altern=
ative than any risk of a loop.&nbsp; </div>
<div style=3D"padding-left: 36pt; "><font face=3D"Calibri, sans-serif" size=
=3D"2">&nbsp;</font></div>
<ol start=3D"4" style=3D"margin-top: 0pt; margin-bottom: 0pt; margin-left: =
36pt; ">
<li>Section 8.1.5 &#8211; It states that a PW Id TLV is &#8220;used to comm=
unicate the configuration of PWs for VPWS.&#8221;&nbsp; Is there some reaso=
n that this cannot be used with a (H)VPLS?&nbsp; For example, there could b=
e redundant MTUs that are connecting to a core group of PEs
as discussed above.</li></ol>
<div style=3D"padding-left: 36pt; "><font face=3D"Calibri, sans-serif" size=
=3D"2">&nbsp;</font></div>
<ol start=3D"5" style=3D"margin-top: 0pt; margin-bottom: 0pt; margin-left: =
36pt; ">
<li>Section 8.1.5 &#8211; There is a Peer ID field included in the TLV.&nbs=
p; What is the intent of the Peer ID?</li></ol>
<div style=3D"padding-left: 36pt; "><font face=3D"Calibri, sans-serif" size=
=3D"2">&nbsp;</font></div>
<ol start=3D"6" style=3D"margin-top: 0pt; margin-bottom: 0pt; margin-left: =
36pt; ">
<li>Are there any provisions for when an access network might segment with =
part of the access network still having connectivity to one PE while the re=
mainder of the network has connectivity to the other PE?&nbsp; I realize th=
at how this condition is recognized may
be out of the scope of this document, but how the PEs communicate this cond=
ition could potentially be included.</li></ol>
<div style=3D"padding-left: 36pt; "><font face=3D"Calibri, sans-serif" size=
=3D"2">&nbsp;</font></div>
<div>Thanks for your attention.</div>
<div><font face=3D"Calibri, sans-serif" size=3D"2">&nbsp;</font></div>
<div>Cheers,</div>
<div>Olen</div>
<div><font face=3D"Calibri, sans-serif" size=3D"2">&nbsp;</font></div>
<div><font face=3D"Calibri, sans-serif" size=3D"2">&nbsp;</font></div>
<div><font face=3D"Calibri, sans-serif" size=3D"2">&nbsp;</font></div>
<div><font face=3D"Calibri, sans-serif" size=3D"2">&nbsp;</font></div>
<div><font face=3D"Calibri, sans-serif" size=3D"2">&nbsp;</font></div>
<div><font face=3D"Calibri, sans-serif" size=3D"2">&nbsp;</font></div>
</font>
</body>
</html>

--_000_6738A78F51650A4FAEDCF6844B26C21413554176FFUSEXCHANGEcor_--

From frederic.jounay@orange-ftgroup.com  Mon Jun  8 05:27:42 2009
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 F38713A69B7 for <pwe3@core3.amsl.com>; Mon,  8 Jun 2009 05:27:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.248
X-Spam-Level: 
X-Spam-Status: No, score=-2.248 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_FR=0.35, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0kqd9P3B3n86 for <pwe3@core3.amsl.com>; Mon,  8 Jun 2009 05:27:40 -0700 (PDT)
Received: from R-MAIL1.rd.francetelecom.com (r-mail1.rd.francetelecom.com [217.108.152.41]) by core3.amsl.com (Postfix) with ESMTP id C8DA73A6885 for <pwe3@ietf.org>; Mon,  8 Jun 2009 05:27:39 -0700 (PDT)
Received: from ftrdmel1.rd.francetelecom.fr ([10.192.128.40]) by ftrdsmtp2.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.3959);  Mon, 8 Jun 2009 14:27:43 +0200
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_01C9E834.856E72FD"
Date: Mon, 8 Jun 2009 14:27:41 +0200
Message-ID: <AFC377AFCC0FBD4DABE49F4B81EC4F1A1CA5CC@ftrdmel1>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: LDP P2MP PW drafts discussion
Thread-Index: AcnoEuiA9AmdL5jvSUen3b1Q3Je0awACxyswAATFL3A=
From: <frederic.jounay@orange-ftgroup.com>
To: <pwe3@ietf.org>
X-OriginalArrivalTime: 08 Jun 2009 12:27:43.0372 (UTC) FILETIME=[85930CC0:01C9E834]
Subject: [PWE3] LDP P2MP PW drafts discussion
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: <http://www.ietf.org/mail-archive/web/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, 08 Jun 2009 12:27:42 -0000

This is a multi-part message in MIME format.

------_=_NextPart_001_01C9E834.856E72FD
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

> Luca,
>=20
> Please find some comments on the new draft
> http://tools.ietf.org/html/draft-martini-pwe3-p2mp-pw-00.
>=20
> From a general point of view it seems that your proposal relies on
> almost the same basic principles as the  draft
> http://tools.ietf.org/html/draft-jounay-niger-pwe3-source-initiated-p2
> mp-pw-02 (posted 2 years ago and presented during the last IETF
> meeting), with the main difference that it is restricted to the SS-PW
> case.
>=20
> The solution defined for P2MP SS-PW must be designed with the capacity
> to support also P2MP MS-PW. This is the case in the draft
> jounay-niger.=20
The v00 presented the procedure for MS-PW. We removed the MS-PW part
from the last version for sake of simplification in order to focus on
the basic protocol elements, but the capacity to support P2MP MS-PW
remains unchanged.=20

> As indicated in the introduction your draft is focused on the SS-PW
> case and in its current state does not allow the support of MS-PW for
> the following reasons :
> - The Group ID does not carry information about leaves identification
> (e.g. @ AII) and the signalling messages initiated by the root could
> not be routed to the leaves. In our proposal the S-PE forwards the
> signaling based on the TAII (leaf node @) transported in the TAII Leaf
> sub-TLV,
> -The downstream assigned label proposed for upstream traffic (from
> leaf to root) can be used in SS-PW to identify the leaf node itself.
> However this can not be the case for MS-PW due to the merging point
> (S-PE) for upstream traffic.
>=20
> I think that's worth coming back to the last point since it appears to
> be the main difference with the jounay-niger draft. This requirement
> has not yet been defined in the P2MP PW REQ draft. The leaf can report
> some OAM/PW status based on LDP Notification messages, but  so far it
> has not been identified as necessary to allow leaves to send traffic
> to the root. Is it a strong requirement? for which applications?  If
> yes, we need to address it first in the P2MP PW REQ draft.
>=20
> In the "incompatibilty issues" section (4.1), you propose to follow
> the same procedure as defined for P2P (bidirectionnal), i.e. the Leaf
> node initiates a LDP status with "PW not forwarding" when the PW type,
> CW or int/ parameters does not match with local configuration. We
> don't think it appropriate for a P2MP connectivity, because a pb on a
> given Leaf node shoud not impact other leaves belonging to the PW
> tree. We propose in the draft the definition of new status codes which
> allow the Ingress PE to determine exactly the issue (PW type non
> compliant code, i/f. Parameters incompatibility code,
> Unassigned/unrecognized AGI/P2MP ID).
>=20
> For the i/f parameters, there is some difference with P2P PW
> procedure, please refer the jounay-niger draft (section 4.5.6) or the
> draft P2MP PW REQ (section 3.4.2).
>=20
> Since the beginning of the P2MP PW work our proposal has been closely
> designed with the L2VPN WG, and in particular with the VPMS draft.
> From this joint work a definition of an optimized P2MP PW FEC has
> emerged with the definition of a P2MP ID. The P2MP ID is proposed to
> overcome some future operational contrainsts. Indeed in the case we
> want to provide similar protection scheme as PW redundancy, we need to
> differentiate the primary P2MP PW from the backup P2MP PW in terms of
> PW identifier. Such a piece is missing in your proposal  Please refer
> to section 4.7. or slides presented during the last IETF PWE3 meeting.
>=20
> Eventually You define a new Transport LSP TLV, used to indicate to the
> leaf node the PSN tunnel the P2MP PW is supported over. This is
> required due to the P2MP PW upstream label assignment.  There is
> already a draft which introduces such an Interface ID (Please refer to
> http://tools.ietf.org/html/draft-ietf-mpls-ldp-upstream-03). In order
> to avoid refining a new TLV for a common purpose it seems preferable
> to extend it to include MLDP P2MP LSP TLV as new Interface ID, as
> proposed in our draft.   =20
>=20
> Considering all these points we invite you to read the jounay-niger
> draft, and since this draft proposes a more general solution,
> extensible to MS-PW, we propose to work together to integrate in this
> proposal already on the table the new feature described in your draft
> (i.e. the P2P return connectivity from leaf to root).
>=20
Best Regards,
Fred

------_=_NextPart_001_01C9E834.856E72FD
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.5.7654.12">
<TITLE>LDP P2MP PW drafts discussion</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/rtf format -->

<P><FONT SIZE=3D2 FACE=3D"Arial">Luca,</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">Please find some comments on the new =
draft </FONT><A =
HREF=3D"http://tools.ietf.org/html/draft-martini-pwe3-p2mp-pw-00"><U><FON=
T COLOR=3D"#0000FF" SIZE=3D2 =
FACE=3D"Arial">http://tools.ietf.org/html/draft-martini-pwe3-p2mp-pw-00</=
FONT></U></A><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial">.</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">From a general point of view it seems =
that your proposal relies on almost the same basic principles as =
the&nbsp;</FONT><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial"> =
draft</FONT> <A =
HREF=3D"http://tools.ietf.org/html/draft-jounay-niger-pwe3-source-initiat=
ed-p2mp-pw-02"><U></U><U><FONT COLOR=3D"#0000FF" SIZE=3D2 =
FACE=3D"Arial">http://tools.ietf.org/html/draft-jounay-niger-pwe3-source-=
initiated-p2mp-pw-02</FONT></U></A><FONT SIZE=3D2 FACE=3D"Arial"> =
(posted 2 years ago and presented during the last IETF meeting), with =
the main difference that it is restricted to the SS-PW case.</FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Arial">The solution defined for P2MP SS-PW =
must be designed with the capacity to support also P2MP MS-PW. This is =
the case in the draft jounay-niger. </FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Arial">The v00 presented the procedure for =
MS-PW. We removed the MS-PW part from the last version for sake of =
simplification in order to focus on the basic protocol elements, but the =
capacity to support P2MP MS-PW remains unchanged. </FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Arial">As indicated in the introduction your =
draft is focused on the SS-PW case and in its current state does not =
allow the support of MS-PW for the following reasons :</FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Arial">- The Group ID does not carry =
information about leaves identification (e.g. @ AII) and the signalling =
messages initiated by the root could not be routed to the leaves. In our =
proposal the S-PE forwards the signaling based on the TAII (leaf node @) =
transported in the TAII Leaf sub-TLV,</FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Arial">-The downstream assigned label proposed =
for upstream traffic (from leaf to root) can be used in SS-PW to =
identify the leaf node itself. However this can not be the case for =
MS-PW due to the merging point (S-PE) for upstream traffic.</FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Arial">I think that's worth coming back to the =
last point since it appears to be the main difference with the =
jounay-niger draft. This requirement has not yet been defined in the =
P2MP PW REQ draft. The leaf can report some OAM/PW status based on LDP =
Notification messages, but&nbsp; so far it has not been identified as =
necessary to allow leaves to send traffic to the root. Is it a strong =
requirement? for which applications?&nbsp; If yes, we need to address it =
first in the P2MP PW REQ draft.</FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Arial">In the &quot;incompatibilty =
issues&quot; section (4.1), you propose to follow the same procedure as =
defined for P2P (bidirectionnal), i.e. the Leaf node initiates a LDP =
status with &quot;PW not forwarding&quot; when the PW type, CW or int/ =
parameters does not match with local configuration. We don't think it =
appropriate for a P2MP connectivity, because a pb on a given Leaf node =
shoud not impact other leaves belonging to the PW tree. We propose in =
the draft the definition of new status codes which allow the Ingress PE =
to determine exactly the issue (PW type non compliant code, i/f. =
Parameters incompatibility code, Unassigned/unrecognized AGI/P2MP =
ID).</FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Arial">For the i/f parameters, there is some =
difference with P2P PW procedure, please refer the jounay-niger draft =
(section 4.5.6) or the draft P2MP PW REQ (section 3.4.2).</FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Arial">Since the beginning of the P2MP PW work =
our proposal has been closely designed with the L2VPN WG, and in =
particular with the VPMS draft. From this joint work a definition of an =
optimized P2MP PW FEC has emerged with the definition of a P2MP ID. The =
P2MP ID is proposed to overcome some future operational contrainsts. =
Indeed in the case we want to provide similar protection scheme as PW =
redundancy, we need to differentiate the primary P2MP PW from the backup =
P2MP PW in terms of PW identifier. Such a piece is missing in your =
proposal&nbsp; Please refer to section 4.7. or slides presented during =
the last IETF PWE3 meeting.</FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Arial">Eventually You define a new Transport =
LSP TLV, used to indicate to the leaf node the PSN tunnel the P2MP PW is =
supported over. This is required due to the P2MP PW upstream label =
assignment.&nbsp; There is already a draft which introduces such an =
Interface ID (Please refer to </FONT><A =
HREF=3D"http://tools.ietf.org/html/draft-ietf-mpls-ldp-upstream-03"><U><F=
ONT COLOR=3D"#0000FF" SIZE=3D2 =
FACE=3D"Arial">http://tools.ietf.org/html/draft-ietf-mpls-ldp-upstream-03=
</FONT></U></A><FONT COLOR=3D"#0000FF" SIZE=3D2 =
FACE=3D"Arial">).</FONT><FONT SIZE=3D2 FACE=3D"Arial"> In order to avoid =
refining a new TLV for a common purpose it seems preferable to extend it =
to include MLDP P2MP LSP TLV as new Interface ID, as proposed in our =
draft.&nbsp;&nbsp;&nbsp; </FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Arial">Considering all these points we invite =
you to read the jounay-niger draft, and since this draft proposes a more =
general solution, extensible to MS-PW, we propose to work together to =
integrate in this proposal already on the table the new feature =
described in your draft (i.e. the P2P return connectivity from leaf to =
root).</FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Arial">Best Regards,</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">Fred</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C9E834.856E72FD--

From Martin.Vigoureux@alcatel-lucent.com  Wed Jun 10 01:22:56 2009
Return-Path: <Martin.Vigoureux@alcatel-lucent.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 1C3073A6DB9; Wed, 10 Jun 2009 01:22:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.877
X-Spam-Level: 
X-Spam-Status: No, score=-5.877 tagged_above=-999 required=5 tests=[AWL=0.372,  BAYES_00=-2.599, HELO_EQ_FR=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XmBU3lyXpOBC; Wed, 10 Jun 2009 01:22:55 -0700 (PDT)
Received: from smail2.alcatel.fr (smail2.alcatel.fr [62.23.212.57]) by core3.amsl.com (Postfix) with ESMTP id 2E3133A6DA5; Wed, 10 Jun 2009 01:22:54 -0700 (PDT)
Received: from FRVELSBHS04.ad2.ad.alcatel.com (frvelsbhs04.dc-m.alcatel-lucent.com [155.132.6.76]) by smail2.alcatel.fr (8.13.8/8.13.8/ICT) with ESMTP id n5A8Mie2017787;  Wed, 10 Jun 2009 10:22:56 +0200
Received: from [172.27.205.109] ([172.27.205.109]) by FRVELSBHS04.ad2.ad.alcatel.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.3959); Wed, 10 Jun 2009 10:22:51 +0200
Message-ID: <4A2F6D5B.5060104@alcatel-lucent.com>
Date: Wed, 10 Jun 2009 10:22:51 +0200
From: Martin Vigoureux <martin.vigoureux@alcatel-lucent.com>
Organization: Alcatel-Lucent
User-Agent: Thunderbird 2.0.0.19 (Windows/20081209)
MIME-Version: 1.0
To: mpls@ietf.org, Scott Mansfield <scott.mansfield@ericsson.com>, LAM Kam <hklam@alcatel-lucent.com>, Eric Gray <eric.gray@ericsson.com>
References: <4A1A836E.7080804@pi.nu>
In-Reply-To: <4A1A836E.7080804@pi.nu>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
X-OriginalArrivalTime: 10 Jun 2009 08:22:51.0973 (UTC) FILETIME=[A5A4F750:01C9E9A4]
X-Scanned-By: MIMEDefang 2.57 on 155.132.188.80
Cc: pwe3@ietf.org, mpls-tp@ietf.org
Subject: Re: [PWE3] [mpls] poll on making draft-mansfield-mpls-tp-nm-framework a mpls	wg 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: <http://www.ietf.org/mail-archive/web/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, 10 Jun 2009 08:22:56 -0000

All,

the poll has ended with clear support expressed.

Editors, please republish as draft-ietf-mpls-tp-nm-framework-00

thanks
martin

Loa Andersson a écrit :
> All,
> 
> this is to start a two week poll (to be ended on June 8th)
> on the suggestion to make draft-mansfield-mpls-tp-nm-framework
> a mpls working group document.
> 
> Send your comment (approve or disapprove) to the mpls-tp list.
> 
> /Loa

From Martin.Vigoureux@alcatel-lucent.com  Wed Jun 10 01:23:12 2009
Return-Path: <Martin.Vigoureux@alcatel-lucent.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 9BC623A6DCB; Wed, 10 Jun 2009 01:23:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.001
X-Spam-Level: 
X-Spam-Status: No, score=-4.001 tagged_above=-999 required=5 tests=[AWL=-1.752, BAYES_00=-2.599, HELO_EQ_FR=0.35]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GVIIX+PVxNwh; Wed, 10 Jun 2009 01:23:12 -0700 (PDT)
Received: from smail2.alcatel.fr (smail2.alcatel.fr [64.208.49.57]) by core3.amsl.com (Postfix) with ESMTP id A3D7F3A6DB9; Wed, 10 Jun 2009 01:23:11 -0700 (PDT)
Received: from FRVELSBHS04.ad2.ad.alcatel.com (frvelsbhs04.dc-m.alcatel-lucent.com [155.132.6.76]) by smail2.alcatel.fr (8.13.8/8.13.8/ICT) with ESMTP id n5A8Mie0017787;  Wed, 10 Jun 2009 10:22:55 +0200
Received: from [172.27.205.109] ([172.27.205.109]) by FRVELSBHS04.ad2.ad.alcatel.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.3959); Wed, 10 Jun 2009 10:22:44 +0200
Message-ID: <4A2F6D53.5060002@alcatel-lucent.com>
Date: Wed, 10 Jun 2009 10:22:43 +0200
From: Martin Vigoureux <martin.vigoureux@alcatel-lucent.com>
Organization: Alcatel-Lucent
User-Agent: Thunderbird 2.0.0.19 (Windows/20081209)
MIME-Version: 1.0
To: Loa Andersson <loa@pi.nu>, mpls@ietf.org, Huub van Helvoort <hhelvoort@huawei.com>, Nurit Sprecher <nurit.sprecher@nsn.com>
References: <4A1BB784.7030501@pi.nu>
In-Reply-To: <4A1BB784.7030501@pi.nu>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
X-OriginalArrivalTime: 10 Jun 2009 08:22:44.0223 (UTC) FILETIME=[A10668F0:01C9E9A4]
X-Scanned-By: MIMEDefang 2.57 on 155.132.188.80
Cc: pwe3@ietf.org, mpls-tp@ietf.org
Subject: Re: [PWE3] [mpls] poll on the Rosetta Stone draft
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: <http://www.ietf.org/mail-archive/web/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, 10 Jun 2009 08:23:12 -0000

All,

the poll has ended with clear support expressed.

Editors, please republish as draft-ietf-mpls-tp-rosetta-stone-00

thanks
martin


Loa Andersson a écrit :
> All,
> 
> this is to start a two week poll on the suggestion to make the
> draft-helvoort-mpls-tp-rosetta-stone-00 an MPLS working group
> document.
> 
> Please send your comments (approval or disapproval) to the mpls-tp
> mailing list.
> 
> The poll ends on June 9th 2009.
> 
> /Loa
> 
> 

From loa@pi.nu  Wed Jun 10 03:37:29 2009
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 7146B3A69FF; Wed, 10 Jun 2009 03:37:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.474
X-Spam-Level: 
X-Spam-Status: No, score=-1.474 tagged_above=-999 required=5 tests=[AWL=-0.364, BAYES_05=-1.11]
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 idaq4e-0V6-Z; Wed, 10 Jun 2009 03:37:28 -0700 (PDT)
Received: from mail.pi.nu (mail.pi.nu [194.71.127.148]) by core3.amsl.com (Postfix) with ESMTP id A6DBD3A6E54; Wed, 10 Jun 2009 03:37:28 -0700 (PDT)
Received: from [192.36.158.76] (wdhcp-158-76.verkstad.net [192.36.158.76]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: loa@pi.nu) by mail.pi.nu (Postfix) with ESMTPSA id 0DF7CD4052; Wed, 10 Jun 2009 12:37:31 +0200 (CEST)
Message-ID: <4A2F8CEB.7000904@pi.nu>
Date: Wed, 10 Jun 2009 12:37:31 +0200
From: Loa Andersson <loa@pi.nu>
User-Agent: Thunderbird 2.0.0.21 (Windows/20090302)
MIME-Version: 1.0
To: mpls@ietf.org, mpls-tp@ietf.org, pwe3@ietf.org,  Stewart Bryant <stbryant@cisco.com>, Martin Vigoureux <martin.vigoureux@alcatel-lucent.com>,  BOCCI Matthew <Matthew.Bocci@alcatel-lucent.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: [PWE3] RFC 5586 published
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: <http://www.ietf.org/mail-archive/web/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, 10 Jun 2009 10:37:29 -0000

All,

we have a new RFC - RFC5586 "MPLS Generic Associated Channel" - just
published.

Please join me in congratulating the editors and authors.


/Loa

From wwwrun@core3.amsl.com  Mon Jun 15 07:52:44 2009
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 1BF7E3A6CFA; Mon, 15 Jun 2009 07:52:43 -0700 (PDT)
X-idtracker: yes
To: IETF-Announce <ietf-announce@ietf.org> 
From: The IESG <iesg-secretary@ietf.org>
Message-Id: <20090615145244.1BF7E3A6CFA@core3.amsl.com>
Date: Mon, 15 Jun 2009 07:52:44 -0700 (PDT)
Cc: pwe3@ietf.org
Subject: [PWE3] Last Call: draft-ietf-pwe3-vccv-bfd (Bidirectional Forwarding Detection (BFD) for the Pseudowire Virtual Circuit Connectivity Verification (VCCV)) to Proposed Standard
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: ietf@ietf.org
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: <http://www.ietf.org/mail-archive/web/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, 15 Jun 2009 14:52:44 -0000

The IESG has received a request from the Pseudowire Emulation Edge to 
Edge WG (pwe3) to consider the following document:

- 'Bidirectional Forwarding Detection (BFD) for the Pseudowire Virtual 
   Circuit Connectivity Verification (VCCV) '
   <draft-ietf-pwe3-vccv-bfd-05.txt> as a Proposed Standard

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action.  Please send substantive comments to the
ietf@ietf.org mailing lists by 2009-06-26. Exceptionally, 
comments may be sent to iesg@ietf.org instead. In either case, please 
retain the beginning of the Subject line to allow automated sorting.

The file can be obtained via
http://www.ietf.org/internet-drafts/draft-ietf-pwe3-vccv-bfd-05.txt


IESG discussion can be tracked via
https://datatracker.ietf.org/public/pidtracker.cgi?command=view_id&dTag=16598&rfc_flag=0


From wwwrun@core3.amsl.com  Mon Jun 15 08:22:11 2009
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 E0BC13A6CC6; Mon, 15 Jun 2009 08:22:08 -0700 (PDT)
X-idtracker: yes
To: IETF-Announce <ietf-announce@ietf.org> 
From: The IESG <iesg-secretary@ietf.org>
Message-Id: <20090615152211.E0BC13A6CC6@core3.amsl.com>
Date: Mon, 15 Jun 2009 08:22:08 -0700 (PDT)
Cc: pwe3@ietf.org
Subject: [PWE3] UPDATED Last Call: draft-ietf-pwe3-vccv-bfd (Bidirectional Forwarding Detection (BFD) for the Pseudowire Virtual Circuit Connectivity Verification (VCCV)) to Proposed Standard
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: ietf@ietf.org
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: <http://www.ietf.org/mail-archive/web/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, 15 Jun 2009 15:22:12 -0000

The IESG has received a request from the Pseudowire Emulation Edge to 
Edge WG (pwe3) to consider the following document:

- 'Bidirectional Forwarding Detection (BFD) for the Pseudowire Virtual 
   Circuit Connectivity Verification (VCCV) '
   <draft-ietf-pwe3-vccv-bfd-05.txt> as a Proposed Standard

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action.  Please send substantive comments to the
ietf@ietf.org mailing lists by 2009-06-29. Exceptionally, 
comments may be sent to iesg@ietf.org instead. In either case, please 
retain the beginning of the Subject line to allow automated sorting.

The file can be obtained via
http://www.ietf.org/internet-drafts/draft-ietf-pwe3-vccv-bfd-05.txt


IESG discussion can be tracked via
https://datatracker.ietf.org/public/pidtracker.cgi?command=view_id&dTag=16598&rfc_flag=0


From Scott.Brim@gmail.com  Sun Jun 14 08:08:12 2009
Return-Path: <Scott.Brim@gmail.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 D670D3A6940; Sun, 14 Jun 2009 08:08:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id x78dLFrSF64E; Sun, 14 Jun 2009 08:08:11 -0700 (PDT)
Received: from rtp-iport-2.cisco.com (rtp-iport-2.cisco.com [64.102.122.149]) by core3.amsl.com (Postfix) with ESMTP id 675483A6863; Sun, 14 Jun 2009 08:08:11 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.42,218,1243814400"; d="scan'208";a="47257722"
Received: from rtp-dkim-1.cisco.com ([64.102.121.158]) by rtp-iport-2.cisco.com with ESMTP; 14 Jun 2009 15:08:20 +0000
Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13]) by rtp-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id n5EF8JEJ026652;  Sun, 14 Jun 2009 11:08:19 -0400
Received: from cisco.com (ssh-rtp-2.cisco.com [64.102.8.172]) by rtp-core-2.cisco.com (8.13.8/8.13.8) with ESMTP id n5EF8Kah008525; Sun, 14 Jun 2009 15:08:20 GMT
Date: Sun, 14 Jun 2009 11:08:12 -0400
From: Scott Brim <Scott.Brim@gmail.com>
To: rdroms@cisco.com, pwe3@ietf.org, gen-art@ietf.org, ietf@ietf.org, david.sinicrope@ericsson.com
Message-ID: <20090614150812.GA22282@cisco.com>
Mail-Followup-To: Scott Brim <Scott.Brim@gmail.com>, rdroms@cisco.com, pwe3@ietf.org, gen-art@ietf.org, ietf@ietf.org, david.sinicrope@ericsson.com
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.5.19 (2009-01-05)
Authentication-Results: rtp-dkim-1; header.From=Scott.Brim@gmail.com; dkim=neutral
X-Mailman-Approved-At: Mon, 15 Jun 2009 09:13:17 -0700
Subject: [PWE3] gen-art review of 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: <http://www.ietf.org/mail-archive/web/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: Sun, 14 Jun 2009 15:08:12 -0000

I have been selected as the General Area Review Team (Gen-ART)
reviewer for this draft (for background on Gen-ART, please see
http://www.alvestrand.no/ietf/gen/art/gen-art-FAQ.html).

Please resolve these comments along with any other Last Call comments
you may receive.

Document: draft-ietf-pwe3-ms-pw-arch-06.txt
Reviewer: Scott Brim
Review Date:
IETF LC End Date: 2009-06-16
IESG Telechat date: (if known)

Summary: This draft is ready for publication as an informational RFC.

Major issues:

Minor issues:

Nits/editorial comments:

- In this one paragraph:

    Note that although Figure 4 only shows a single S-PE, a PW may
    transit more one S-PE along its path. This architecture is
    applicable when the S-PEs are statically chosen, or when they are
    chosen using a dynamic path selection mechanism. Both directions
    of an MS-PW must traverse the same set of S-PEs on a reciprocal
    path.  Note that although the S-PE path is therefore reciprocal,
    the path taken by the PSN tunnels between the T-PEs and S-PEs may
    not be reciprocal due to choices made by the PSN routing protocol. 

  ... "reciprocal" is used, but nowhere else in the document.  Should
  it be "bi-directional" (used elsewhere)?


- 15.1 "References" should be "Normative References"


Scott

From stbryant@cisco.com  Mon Jun 15 14:41:20 2009
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 082583A68EB; Mon, 15 Jun 2009 14:41:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.327
X-Spam-Level: 
X-Spam-Status: No, score=-10.327 tagged_above=-999 required=5 tests=[AWL=0.272, 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 FuoowGuudaGq; Mon, 15 Jun 2009 14:41:19 -0700 (PDT)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140]) by core3.amsl.com (Postfix) with ESMTP id 501813A69FE; Mon, 15 Jun 2009 14:41:18 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.42,224,1243814400"; d="scan'208";a="42861720"
Received: from ams-dkim-2.cisco.com ([144.254.224.139]) by ams-iport-1.cisco.com with ESMTP; 15 Jun 2009 21:41:19 +0000
Received: from ams-core-1.cisco.com (ams-core-1.cisco.com [144.254.224.150]) by ams-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id n5FLfJU5002058;  Mon, 15 Jun 2009 23:41:19 +0200
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 n5FLfJFZ022044; Mon, 15 Jun 2009 21:41:19 GMT
Received: from Stewarts-Computer-2.local (localhost [127.0.0.1]) by cisco.com (8.11.7p3+Sun/8.8.8) with ESMTP id n5FLfIK15591; Mon, 15 Jun 2009 22:41:18 +0100 (BST)
Message-ID: <4A36BFFD.7020002@cisco.com>
Date: Mon, 15 Jun 2009 22:41:17 +0100
From: Stewart Bryant <stbryant@cisco.com>
User-Agent: Thunderbird 2.0.0.19 (Macintosh/20081209)
MIME-Version: 1.0
To: Scott Brim <Scott.Brim@gmail.com>, rdroms@cisco.com, pwe3@ietf.org, gen-art@ietf.org, ietf@ietf.org, david.sinicrope@ericsson.com
References: <20090614150812.GA22282@cisco.com>
In-Reply-To: <20090614150812.GA22282@cisco.com>
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=1052; t=1245102079; x=1245966079; c=relaxed/simple; s=amsdkim2001; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=stbryant@cisco.com; z=From:=20Stewart=20Bryant=20<stbryant@cisco.com> |Subject:=20Re=3A=20gen-art=20review=20of=20draft-ietf-pwe3 -ms-pw-arch-06.txt |Sender:=20; bh=lJ0aQG1hfXGfhlYJZgkgRLgoAGSoAyx1YGJSl5qc1IA=; b=qGixP6R89Q7t6hZPNj5c93CM1Plj1wPiBy/sNGXgG1Sb85VaTCnED49mhT dMC/0coE+LmLJ8FoJBxSu0xnmbTdbLyDnltPXRYZUGzFVRPNLLgGvtU1GI+p 9AnfauaFeC;
Authentication-Results: ams-dkim-2; header.From=stbryant@cisco.com; dkim=pass ( sig from cisco.com/amsdkim2001 verified; ); 
Subject: Re: [PWE3] gen-art review of draft-ietf-pwe3-ms-pw-arch-06.txt
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: <http://www.ietf.org/mail-archive/web/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, 15 Jun 2009 21:41:20 -0000

Scott
>
> - In this one paragraph:
>
>     Note that although Figure 4 only shows a single S-PE, a PW may
>     transit more one S-PE along its path. This architecture is
>     applicable when the S-PEs are statically chosen, or when they are
>     chosen using a dynamic path selection mechanism. Both directions
>     of an MS-PW must traverse the same set of S-PEs on a reciprocal
>     path.  Note that although the S-PE path is therefore reciprocal,
>     the path taken by the PSN tunnels between the T-PEs and S-PEs may
>     not be reciprocal due to choices made by the PSN routing protocol. 
>
>   ... "reciprocal" is used, but nowhere else in the document.  Should
>   it be "bi-directional" (used elsewhere)?
>
>   
I am not sure.

In propagation and navigation a reciprocal path is the exact reverse of 
the outward path,
and that is exactly what we want to say. I this context it is also 
bidirectional.

> - 15.1 "References" should be "Normative References"
>
>   
We will split the list tomorrow.

Stewart

From Matthew.Bocci@alcatel-lucent.com  Tue Jun 16 07:44:48 2009
Return-Path: <Matthew.Bocci@alcatel-lucent.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 2C7C33A6B3A; Tue, 16 Jun 2009 07:44:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.873
X-Spam-Level: 
X-Spam-Status: No, score=-1.873 tagged_above=-999 required=5 tests=[AWL=0.376,  BAYES_00=-2.599, HELO_EQ_FR=0.35]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GifZ55qfrNrX; Tue, 16 Jun 2009 07:44:47 -0700 (PDT)
Received: from smail6.alcatel.fr (smail6.alcatel.fr [62.23.212.42]) by core3.amsl.com (Postfix) with ESMTP id 1401B3A6915; Tue, 16 Jun 2009 07:44:46 -0700 (PDT)
Received: from FRVELSBHS05.ad2.ad.alcatel.com (frvelsbhs05.dc-m.alcatel-lucent.com [155.132.6.77]) by smail6.alcatel.fr (8.13.8/8.13.8/ICT) with ESMTP id n5GEew9l024577;  Tue, 16 Jun 2009 16:40:59 +0200
Received: from FRVELSMBS11.ad2.ad.alcatel.com ([155.132.6.33]) by FRVELSBHS05.ad2.ad.alcatel.com with Microsoft SMTPSVC(6.0.3790.3959); Tue, 16 Jun 2009 16:40:56 +0200
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, 16 Jun 2009 16:40:55 +0200
Message-ID: <0458D2EE0C36744BABB36BE37805C29A03FB74D2@FRVELSMBS11.ad2.ad.alcatel.com>
In-Reply-To: <20090614150812.GA22282@cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [PWE3] gen-art review of draft-ietf-pwe3-ms-pw-arch-06.txt
Thread-Index: Acnt1Dv7xEcyn+zsTXKL/5A4gZpb4AAuquSA
References: <20090614150812.GA22282@cisco.com>
From: "BOCCI Matthew" <Matthew.Bocci@alcatel-lucent.com>
To: "Scott Brim" <Scott.Brim@gmail.com>, <rdroms@cisco.com>, <pwe3@ietf.org>,  <gen-art@ietf.org>
X-OriginalArrivalTime: 16 Jun 2009 14:40:56.0786 (UTC) FILETIME=[75533B20:01C9EE90]
X-Scanned-By: MIMEDefang 2.57 on 155.132.188.84
Cc: Stewart Bryant <stbryant@cisco.com>
Subject: Re: [PWE3] gen-art review of 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: <http://www.ietf.org/mail-archive/web/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, 16 Jun 2009 14:44:48 -0000

Scott,

Many thanks for your review.

> -----Original Message-----

[snip]

>=20
> Summary: This draft is ready for publication as an informational RFC.
>=20
> Major issues:
>=20
> Minor issues:
>=20
> Nits/editorial comments:
>=20
> - In this one paragraph:
>=20
>     Note that although Figure 4 only shows a single S-PE, a PW may
>     transit more one S-PE along its path. This architecture is
>     applicable when the S-PEs are statically chosen, or when they are
>     chosen using a dynamic path selection mechanism. Both directions
>     of an MS-PW must traverse the same set of S-PEs on a reciprocal
>     path.  Note that although the S-PE path is therefore reciprocal,
>     the path taken by the PSN tunnels between the T-PEs and S-PEs may
>     not be reciprocal due to choices made by the PSN routing protocol.
>=20
>   ... "reciprocal" is used, but nowhere else in the document.  Should
>   it be "bi-directional" (used elsewhere)?

We mean 'reciprocal' here rather than bidirectional. This section uses
the term reciprocal to refer to the corresponding, but opposite
directions of a PW. Thus we are using the navigational definition of the
term.

>=20
>=20
> - 15.1 "References" should be "Normative References"

Actually I think we need to split the references properly into normative
and informative references. Since this is also an informational draft,
it is also inappropriate to cite RFC2119. The editors therefore propose
rearranging the references as follows:

15. References
15.1. Normative References
[1]	Bryant, S. and Pate, P. (Editors), "Pseudo Wire Emulation
Edge-to-Edge (PWE3) Architecture", RFC 3985, March 2005
[2]	Andersson, L. and Madsen, T., "Provider Provisioned Virtual
Private Network (VPN) Terminology", RFC 4026, March 2005
[3]	Rosen, E. Viswanathan, A. and Callon, R., "Multiprotocol Label
Switching Architecture", RFC 3031, January 2001
[4]	Malis, A. and Townsley, M., "Pseudowire Emulation Edge-to-Edge
(PWE3) Fragmentation and Reassembly", RFC 4623, August 2006

15.2. Informative References

[5]	Martini, L. Bitar, N. and Bocci, M (Editors), "Requirements for
Multi-Segment Pseudowire Emulation Edge-to-Edge (PWE3)", RFC 5254,
October 2008=20
[6]	Bryant, S. & Andersson, L. "JWT Report on MPLS Architectural
Considerations for a Transport profile", RFC 5317, February 2009


Also, in removing the RFC2119 citation we spotted one MUST that is
inappropriate for this informational draft, and removed the 'conventions
used in this document' section. The inappropriate MUST is in section 1.3
bullet 3, where we propose the following change:

OLD:
o	Multi-Segment Pseudowire (MS-PW).  A static or dynamically
configured set of two or more contiguous PW segments that behave and
function as a single point-to-point PW. Each end of a MS-PW by
definition MUST terminate on a T-PE.

NEW:
o	Multi-Segment Pseudowire (MS-PW).  A static or dynamically
configured set of two or more contiguous PW segments that behave and
function as a single point-to-point PW. Each end of a MS-PW by
definition terminates on a T-PE.


Best regards

Matthew

>=20
>=20
> Scott
> _______________________________________________
> pwe3 mailing list
> pwe3@ietf.org
> https://www.ietf.org/mailman/listinfo/pwe3

From amalis@gmail.com  Tue Jun 16 08:00:19 2009
Return-Path: <amalis@gmail.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 DB56028C182; Tue, 16 Jun 2009 08:00:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.477
X-Spam-Level: 
X-Spam-Status: No, score=-2.477 tagged_above=-999 required=5 tests=[AWL=0.123,  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 IyWYsufywyyf; Tue, 16 Jun 2009 08:00:18 -0700 (PDT)
Received: from qw-out-2122.google.com (qw-out-2122.google.com [74.125.92.27]) by core3.amsl.com (Postfix) with ESMTP id 9C70628C181; Tue, 16 Jun 2009 08:00:18 -0700 (PDT)
Received: by qw-out-2122.google.com with SMTP id 3so3000234qwe.31 for <multiple recipients>; Tue, 16 Jun 2009 07:59:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :from:date:message-id:subject:to:cc:content-type :content-transfer-encoding; bh=t6TW/odAA11lyq/OOkoTtxqwwQMXAvXrSBiIR3GNxCI=; b=Njm+iRouKweEyfWcGMDUnYMgopV2dBWWWwUFY3J9nusZNiWdqP1wCEnhZJkgghepOq vTLXYIYYnSIyFXuoamQhKtsDwn/vTZT3okywC9rv4zsnjtWRGitQ4H7+8KME2o8mKQRz zNA4+ugrTmbA7kZrlIjliUZGHOYK5CP78RZ3M=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding; b=sj1bLjTf8O6ek8xB+pY7/E6NAnh6GLGqVdsCOuuVKGvWm8+KSv/gv8j0gt3jgzk/On CyNb+fwCKcMoK/UdAzNb/0A0jw7BRNdvrbENKkeFk4XEQohIEXQIpQq2zFlL0AQC/poN UT7GZIWmdoUXYQXV8Gh1laNf7CjGgMW+XBiHY=
MIME-Version: 1.0
Received: by 10.224.19.213 with SMTP id c21mr8481427qab.352.1245163952089;  Tue, 16 Jun 2009 07:52:32 -0700 (PDT)
In-Reply-To: <0458D2EE0C36744BABB36BE37805C29A03FB74D2@FRVELSMBS11.ad2.ad.alcatel.com>
References: <20090614150812.GA22282@cisco.com> <0458D2EE0C36744BABB36BE37805C29A03FB74D2@FRVELSMBS11.ad2.ad.alcatel.com>
From: "Andrew G. Malis" <amalis@gmail.com>
Date: Tue, 16 Jun 2009 10:52:12 -0400
Message-ID: <b2d141720906160752h22f1893bre17bdbafba050261@mail.gmail.com>
To: BOCCI Matthew <Matthew.Bocci@alcatel-lucent.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: pwe3@ietf.org, gen-art@ietf.org, Stewart Bryant <stbryant@cisco.com>, Scott Brim <Scott.Brim@gmail.com>, rdroms@cisco.com
Subject: Re: [PWE3] gen-art review of 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: <http://www.ietf.org/mail-archive/web/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, 16 Jun 2009 15:00:20 -0000

While I completely agree with Matthew's edits, do informative RFCs
normally have normative references? None of the text is normative ....

Cheers,
Andy

On Tue, Jun 16, 2009 at 10:40 AM, BOCCI
Matthew<Matthew.Bocci@alcatel-lucent.com> wrote:
> Scott,
>
> Many thanks for your review.
>
>> -----Original Message-----
>
> [snip]
>
>>
>> Summary: This draft is ready for publication as an informational RFC.
>>
>> Major issues:
>>
>> Minor issues:
>>
>> Nits/editorial comments:
>>
>> - In this one paragraph:
>>
>> =A0 =A0 Note that although Figure 4 only shows a single S-PE, a PW may
>> =A0 =A0 transit more one S-PE along its path. This architecture is
>> =A0 =A0 applicable when the S-PEs are statically chosen, or when they ar=
e
>> =A0 =A0 chosen using a dynamic path selection mechanism. Both directions
>> =A0 =A0 of an MS-PW must traverse the same set of S-PEs on a reciprocal
>> =A0 =A0 path. =A0Note that although the S-PE path is therefore reciproca=
l,
>> =A0 =A0 the path taken by the PSN tunnels between the T-PEs and S-PEs ma=
y
>> =A0 =A0 not be reciprocal due to choices made by the PSN routing protoco=
l.
>>
>> =A0 ... "reciprocal" is used, but nowhere else in the document. =A0Shoul=
d
>> =A0 it be "bi-directional" (used elsewhere)?
>
> We mean 'reciprocal' here rather than bidirectional. This section uses
> the term reciprocal to refer to the corresponding, but opposite
> directions of a PW. Thus we are using the navigational definition of the
> term.
>
>>
>>
>> - 15.1 "References" should be "Normative References"
>
> Actually I think we need to split the references properly into normative
> and informative references. Since this is also an informational draft,
> it is also inappropriate to cite RFC2119. The editors therefore propose
> rearranging the references as follows:
>
> 15. References
> 15.1. Normative References
> [1] =A0 =A0 Bryant, S. and Pate, P. (Editors), "Pseudo Wire Emulation
> Edge-to-Edge (PWE3) Architecture", RFC 3985, March 2005
> [2] =A0 =A0 Andersson, L. and Madsen, T., "Provider Provisioned Virtual
> Private Network (VPN) Terminology", RFC 4026, March 2005
> [3] =A0 =A0 Rosen, E. Viswanathan, A. and Callon, R., "Multiprotocol Labe=
l
> Switching Architecture", RFC 3031, January 2001
> [4] =A0 =A0 Malis, A. and Townsley, M., "Pseudowire Emulation Edge-to-Edg=
e
> (PWE3) Fragmentation and Reassembly", RFC 4623, August 2006
>
> 15.2. Informative References
>
> [5] =A0 =A0 Martini, L. Bitar, N. and Bocci, M (Editors), "Requirements f=
or
> Multi-Segment Pseudowire Emulation Edge-to-Edge (PWE3)", RFC 5254,
> October 2008
> [6] =A0 =A0 Bryant, S. & Andersson, L. "JWT Report on MPLS Architectural
> Considerations for a Transport profile", RFC 5317, February 2009
>
>
> Also, in removing the RFC2119 citation we spotted one MUST that is
> inappropriate for this informational draft, and removed the 'conventions
> used in this document' section. The inappropriate MUST is in section 1.3
> bullet 3, where we propose the following change:
>
> OLD:
> o =A0 =A0 =A0 Multi-Segment Pseudowire (MS-PW). =A0A static or dynamicall=
y
> configured set of two or more contiguous PW segments that behave and
> function as a single point-to-point PW. Each end of a MS-PW by
> definition MUST terminate on a T-PE.
>
> NEW:
> o =A0 =A0 =A0 Multi-Segment Pseudowire (MS-PW). =A0A static or dynamicall=
y
> configured set of two or more contiguous PW segments that behave and
> function as a single point-to-point PW. Each end of a MS-PW by
> definition terminates on a T-PE.
>
>
> Best regards
>
> Matthew
>
>>
>>
>> Scott
>> _______________________________________________
>> pwe3 mailing list
>> pwe3@ietf.org
>> https://www.ietf.org/mailman/listinfo/pwe3
> _______________________________________________
> pwe3 mailing list
> pwe3@ietf.org
> https://www.ietf.org/mailman/listinfo/pwe3
>

From stbryant@cisco.com  Tue Jun 16 08:13:07 2009
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 C1B743A6D8C; Tue, 16 Jun 2009 08:13:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.357
X-Spam-Level: 
X-Spam-Status: No, score=-10.357 tagged_above=-999 required=5 tests=[AWL=0.242, 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 0qjgErH0SCFG; Tue, 16 Jun 2009 08:13:07 -0700 (PDT)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140]) by core3.amsl.com (Postfix) with ESMTP id 658733A6D7F; Tue, 16 Jun 2009 08:13:06 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.42,229,1243814400"; d="scan'208";a="42938252"
Received: from ams-dkim-2.cisco.com ([144.254.224.139]) by ams-iport-1.cisco.com with ESMTP; 16 Jun 2009 15:11:39 +0000
Received: from ams-core-1.cisco.com (ams-core-1.cisco.com [144.254.224.150]) by ams-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id n5GFBdw2031165;  Tue, 16 Jun 2009 17:11:39 +0200
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 n5GFBc1Z025334; Tue, 16 Jun 2009 15:11:38 GMT
Received: from Stewarts-Computer-2.local (localhost [127.0.0.1]) by cisco.com (8.11.7p3+Sun/8.8.8) with ESMTP id n5GFBbA01834; Tue, 16 Jun 2009 16:11:37 +0100 (BST)
Message-ID: <4A37B629.1050503@cisco.com>
Date: Tue, 16 Jun 2009 16:11:37 +0100
From: Stewart Bryant <stbryant@cisco.com>
User-Agent: Thunderbird 2.0.0.19 (Macintosh/20081209)
MIME-Version: 1.0
To: "Andrew G. Malis" <amalis@gmail.com>
References: <20090614150812.GA22282@cisco.com> <0458D2EE0C36744BABB36BE37805C29A03FB74D2@FRVELSMBS11.ad2.ad.alcatel.com> <b2d141720906160752h22f1893bre17bdbafba050261@mail.gmail.com>
In-Reply-To: <b2d141720906160752h22f1893bre17bdbafba050261@mail.gmail.com>
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=385; t=1245165099; x=1246029099; c=relaxed/simple; s=amsdkim2001; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=stbryant@cisco.com; z=From:=20Stewart=20Bryant=20<stbryant@cisco.com> |Subject:=20Re=3A=20[PWE3]=20gen-art=20review=20of=20draft- ietf-pwe3-ms-pw-arch-06.txt |Sender:=20; bh=vCT4HB9SFrSc8JM7SiPkh4bdsB9deCpvN2fdaBrIKxI=; b=FRL1rxf0vEJjBOTQW/3ziJ1hl5jH0NDl0ZWG3ezjAkH/1Mn46hLwvJC1co qdbYVbw6w/pEAd4nDmmRh8Tl5OiZMBphYjpGa9VLv5TuFsTvnuObCBTY/L7z NqTfEMMF3d;
Authentication-Results: ams-dkim-2; header.From=stbryant@cisco.com; dkim=pass ( sig from cisco.com/amsdkim2001 verified; ); 
Cc: pwe3@ietf.org, BOCCI Matthew <Matthew.Bocci@alcatel-lucent.com>, gen-art@ietf.org, Scott Brim <Scott.Brim@gmail.com>, rdroms@cisco.com
Subject: Re: [PWE3] gen-art review of draft-ietf-pwe3-ms-pw-arch-06.txt
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: <http://www.ietf.org/mail-archive/web/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, 16 Jun 2009 15:13:07 -0000

Andrew G. Malis wrote:
> While I completely agree with Matthew's edits, do informative RFCs
> normally have normative references? None of the text is normative ....
>
> Cheers,
> Andy
>
>   
That was my first reaction when I saw Scott's comment, but we
(the editors) looked for a definitive guide and could not find one.
RFC3985 has the two classes of reference.

Stewart

From amalis@gmail.com  Tue Jun 16 08:24:59 2009
Return-Path: <amalis@gmail.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 F00BC3A6D82; Tue, 16 Jun 2009 08:24:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.494
X-Spam-Level: 
X-Spam-Status: No, score=-2.494 tagged_above=-999 required=5 tests=[AWL=0.105,  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 P0TfB34wVQjG; Tue, 16 Jun 2009 08:24:58 -0700 (PDT)
Received: from qw-out-2122.google.com (qw-out-2122.google.com [74.125.92.25]) by core3.amsl.com (Postfix) with ESMTP id 0AF723A6D7E; Tue, 16 Jun 2009 08:24:57 -0700 (PDT)
Received: by qw-out-2122.google.com with SMTP id 3so3012529qwe.31 for <multiple recipients>; Tue, 16 Jun 2009 08:24:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :from:date:message-id:subject:to:cc:content-type :content-transfer-encoding; bh=glLjdzWSyu+J242xasPiSfMNlSo08X+0AuwvE7BwpHo=; b=Kr5Njx/EkLlemaEgewOZyZ6WpktDxAwpSDDYIqGadXsdmiEbOKotJ8LQEuEI2+nYbo IAxPeTZvXlYf+osRt+C+f0Sd+cUSOT3zg2JgUhvkEujlvMTXpZiXO3hV4gAvR3uWA45i /MHP2yeHbxR17LBjIf6X0lAj4PiIWiCXAwovY=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding; b=SzBZZBPNGlvV5u7/Nozd4m3+Rp4y85PP1CpVrbIIY/0RqDTHwpqUhLjvVet7ZyOG9Y WdEPW/HLN8F54D2b/q9+ouxzAew0rYEG/oWfqeJhCpUJ52BWrjHJbtQ3M86m8ytKPeaS 6rLSyJWfQpWyRfclTGEFa117+JX3xLbq0GzDg=
MIME-Version: 1.0
Received: by 10.224.36.212 with SMTP id u20mr8561949qad.126.1245165857109;  Tue, 16 Jun 2009 08:24:17 -0700 (PDT)
In-Reply-To: <4A37B629.1050503@cisco.com>
References: <20090614150812.GA22282@cisco.com> <0458D2EE0C36744BABB36BE37805C29A03FB74D2@FRVELSMBS11.ad2.ad.alcatel.com> <b2d141720906160752h22f1893bre17bdbafba050261@mail.gmail.com>  <4A37B629.1050503@cisco.com>
From: "Andrew G. Malis" <amalis@gmail.com>
Date: Tue, 16 Jun 2009 11:23:57 -0400
Message-ID: <b2d141720906160823w21a1d015sedac0fb71da6b39a@mail.gmail.com>
To: stbryant@cisco.com
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: pwe3@ietf.org, BOCCI Matthew <Matthew.Bocci@alcatel-lucent.com>, gen-art@ietf.org, Scott Brim <Scott.Brim@gmail.com>, rdroms@cisco.com
Subject: Re: [PWE3] gen-art review of 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: <http://www.ietf.org/mail-archive/web/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, 16 Jun 2009 15:24:59 -0000

Stewart,

I guess following precedent is the path of least resistance.

Cheers,
Andy

On Tue, Jun 16, 2009 at 11:11 AM, Stewart Bryant<stbryant@cisco.com> wrote:
> Andrew G. Malis wrote:
>>
>> While I completely agree with Matthew's edits, do informative RFCs
>> normally have normative references? None of the text is normative ....
>>
>> Cheers,
>> Andy
>>
>>
>
> That was my first reaction when I saw Scott's comment, but we
> (the editors) looked for a definitive guide and could not find one.
> RFC3985 has the two classes of reference.
>
> Stewart
>

From scott.brim@gmail.com  Tue Jun 16 08:39:35 2009
Return-Path: <scott.brim@gmail.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 4066D3A6A9C; Tue, 16 Jun 2009 08:39:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fwJiqbHskh70; Tue, 16 Jun 2009 08:39:34 -0700 (PDT)
Received: from qw-out-2122.google.com (qw-out-2122.google.com [74.125.92.26]) by core3.amsl.com (Postfix) with ESMTP id 590ED3A6804; Tue, 16 Jun 2009 08:39:34 -0700 (PDT)
Received: by qw-out-2122.google.com with SMTP id 3so3018902qwe.31 for <multiple recipients>; Tue, 16 Jun 2009 08:37:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=S9C139HmQGEjtE9tLvWr/L5U8W4QvJLeNfYmScF5sS8=; b=SInhVkO+O4ScaheMlgJld1JsZvNe8EVXp3hEl0jJQsXKpxva+rKG87aVsH1R3ogLoc 82VZBtN/bjJxB3yE/EWZoAcAOshWjAGeU1udJFcNkNw0rcx28kw1RpV5Qo4PEiHPNqji eutbU6nQSGu57y7uYqL06r9BocydZd4h7bUCU=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; b=dtq+9dtwxHKy/JUmelWo7CypKudPq7AiwRmf39cmphFIEW6j8A77bcigJbKbsoIn6M lmtM9Rp3wimddFkVP0e0TgruqwU9j5w1DOHor5ZIi8Lrbc0TXh5wkCTOZ6zCh2oJRlwY 3todBUTxnzK502lIuGyKhc/NrpV3agBz0zuHg=
Received: by 10.224.19.139 with SMTP id a11mr8560175qab.21.1245166672894; Tue, 16 Jun 2009 08:37:52 -0700 (PDT)
Received: from sbrim-mbp.local (198-135-0-233.cisco.com [198.135.0.233]) by mx.google.com with ESMTPS id 7sm75134qwf.59.2009.06.16.08.37.49 (version=TLSv1/SSLv3 cipher=RC4-MD5); Tue, 16 Jun 2009 08:37:50 -0700 (PDT)
Message-ID: <4A37BC4C.3070303@gmail.com>
Date: Tue, 16 Jun 2009 11:37:48 -0400
From: Scott Brim <scott.brim@gmail.com>
User-Agent: Thunderbird 2.0.0.21 (Macintosh/20090302)
MIME-Version: 1.0
To: BOCCI Matthew <Matthew.Bocci@alcatel-lucent.com>
References: <20090614150812.GA22282@cisco.com> <0458D2EE0C36744BABB36BE37805C29A03FB74D2@FRVELSMBS11.ad2.ad.alcatel.com>
In-Reply-To: <0458D2EE0C36744BABB36BE37805C29A03FB74D2@FRVELSMBS11.ad2.ad.alcatel.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: gen-art@ietf.org, Stewart Bryant <stbryant@cisco.com>, pwe3@ietf.org, rdroms@cisco.com
Subject: Re: [PWE3] gen-art review of 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: <http://www.ietf.org/mail-archive/web/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, 16 Jun 2009 15:39:35 -0000

BOCCI Matthew allegedly wrote on 06/16/2009 10:40 AM:
> Scott,
> 
> Many thanks for your review.

Matthew and all: Thanks for your excellent handling of this.  I'm very
happy.


From Alexander.Vainshtein@ecitele.com  Wed Jun 17 04:46:20 2009
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 243673A6C42 for <pwe3@core3.amsl.com>; Wed, 17 Jun 2009 04:46:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[AWL=-0.000, 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 HFmia+SlQmqT for <pwe3@core3.amsl.com>; Wed, 17 Jun 2009 04:46:19 -0700 (PDT)
Received: from ilptiron01.ecitele.com (ilptiron01.ecitele.com [147.234.242.161]) by core3.amsl.com (Postfix) with ESMTP id 06A113A6C2E for <pwe3@ietf.org>; Wed, 17 Jun 2009 04:46:18 -0700 (PDT)
Received: from unknown (HELO ILPTAM01.ecitele.com) ([147.234.244.44]) by ilptiron01.ecitele.com with ESMTP; 17 Jun 2009 14:42:22 +0300
Received: from ILPTEXCH02.ecitele.com ([147.234.245.181]) by ILPTAM01.ecitele.com with Microsoft SMTPSVC(6.0.3790.3959);  Wed, 17 Jun 2009 14:46:29 +0300
Received: from ILPTMAIL02.ecitele.com ([147.234.244.213]) by ILPTEXCH02.ecitele.com ([147.234.245.181]) with mapi; Wed, 17 Jun 2009 14:46:29 +0300
From: Alexander Vainshtein <Alexander.Vainshtein@ecitele.com>
To: "Praveen.muley@alcatel-lucent.com" <Praveen.muley@alcatel-lucent.com>
Date: Wed, 17 Jun 2009 14:46:29 +0300
Thread-Topic: Status of the PW redundancy drafts
Thread-Index: AcnvQUB7CRk2eR6KSqiN2qmvHq+Mkg==
Message-ID: <A3C5DF08D38B6049839A6F553B331C76A8D3F150E2@ILPTMAIL02.ecitele.com>
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_A3C5DF08D38B6049839A6F553B331C76A8D3F150E2ILPTMAIL02eci_"
MIME-Version: 1.0
X-OriginalArrivalTime: 17 Jun 2009 11:46:29.0695 (UTC) FILETIME=[40DDA4F0:01C9EF41]
Cc: "pwe3@ietf.org" <pwe3@ietf.org>
Subject: [PWE3] Status of the PW redundancy drafts
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: <http://www.ietf.org/mail-archive/web/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, 17 Jun 2009 11:46:20 -0000

--_000_A3C5DF08D38B6049839A6F553B331C76A8D3F150E2ILPTMAIL02eci_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Praveen hi,
I've noticed that both draft-ietf-pwe3-pw-redundancy-01 and draft-ietf-pwe3=
-pw-redundancy-bit-01 have expired almost 3 months ago.
Do you and your co-authors plan to refresh these drafts before Stockholm?
Do you foresee any issues before sending them to the WG Last call?

Regards,
     Sasha



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

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2900.3527" name=3DGENERATOR></HEAD>
<BODY>
<DIV><SPAN class=3D258202711-17062009><FONT face=3DArial size=3D2>Praveen=20
hi,</FONT></SPAN></DIV>
<DIV><SPAN class=3D258202711-17062009><FONT face=3DArial><FONT size=3D2>I'v=
e noticed=20
that both <FONT color=3D#0000ff><EM>draft-ietf-pwe3-pw-redundancy-01</EM></=
FONT>=20
and <EM><FONT color=3D#0000ff>draft-ietf-pwe3-pw-redundancy-bit-01</FONT></=
EM>=20
have expired almost 3 months ago.</FONT></FONT></SPAN></DIV>
<DIV><SPAN class=3D258202711-17062009><FONT face=3DArial size=3D2>Do you an=
d your=20
co-authors plan to refresh these drafts before Stockholm?</FONT></SPAN></DI=
V>
<DIV><SPAN class=3D258202711-17062009><FONT face=3DArial size=3D2>Do you fo=
resee any=20
issues before sending them to the WG Last call?</FONT></SPAN></DIV>
<DIV><SPAN class=3D258202711-17062009><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D258202711-17062009><FONT face=3DArial=20
size=3D2>Regards,</FONT></SPAN></DIV>
<DIV><SPAN class=3D258202711-17062009><FONT face=3DArial=20
size=3D2>&nbsp;&nbsp;&nbsp;&nbsp; Sasha</FONT></SPAN></DIV>
<DIV><SPAN class=3D258202711-17062009><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D258202711-17062009><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV></BODY></HTML>

--_000_A3C5DF08D38B6049839A6F553B331C76A8D3F150E2ILPTMAIL02eci_--

From root@core3.amsl.com  Wed Jun 17 05:15:01 2009
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 AD8B13A68CD; Wed, 17 Jun 2009 05:15:01 -0700 (PDT)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20090617121501.AD8B13A68CD@core3.amsl.com>
Date: Wed, 17 Jun 2009 05:15:01 -0700 (PDT)
Cc: pwe3@ietf.org
Subject: [PWE3] I-D Action:draft-ietf-pwe3-congestion-frmwk-02.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: <http://www.ietf.org/mail-archive/web/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, 17 Jun 2009 12: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           : Pseudowire Congestion Control Framework
	Author(s)       : S. Bryant, et al.
	Filename        : draft-ietf-pwe3-congestion-frmwk-02.txt
	Pages           : 26
	Date            : 2009-06-17

Pseudowires are sometimes used to carry non-TCP data flows.  In these
circumstances the service payload will not react to network
congestion by reducing its offered load.  Pseudowires should
therefore reduces their network bandwidth demands in the face of
significant packet loss, including if necessary completely ceasing
transmission.  Since it is difficult to determine a priori the number
of equivalent TCP flow that a pseudowire represents, a suitably
"fair" rate of back-off cannot be pre-determined.  This document
describes pseudowire congestion problem and provides guidance on the
development suitable solutions.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-pwe3-congestion-frmwk-02.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-congestion-frmwk-02.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

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


--NextPart--

From Mustapha.Aissaoui@alcatel-lucent.com  Wed Jun 17 06:09:10 2009
Return-Path: <Mustapha.Aissaoui@alcatel-lucent.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 255E528C232 for <pwe3@core3.amsl.com>; Wed, 17 Jun 2009 06:09:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jDgh-4hq+YcV for <pwe3@core3.amsl.com>; Wed, 17 Jun 2009 06:09:04 -0700 (PDT)
Received: from audl953.usa.alcatel.com (audl953.usa.alcatel.com [143.209.238.162]) by core3.amsl.com (Postfix) with ESMTP id 2C0FE3A6BC5 for <pwe3@ietf.org>; Wed, 17 Jun 2009 06:08:45 -0700 (PDT)
Received: from usdalsbhs02.ad3.ad.alcatel.com (usdalsbhs02.usa.alcatel.com [172.22.216.13]) by audl953.usa.alcatel.com (ALCANET) with ESMTP id n5HD8G1G025372; Wed, 17 Jun 2009 08:08:33 -0500
Received: from USDALSMBS03.ad3.ad.alcatel.com ([172.22.216.11]) by usdalsbhs02.ad3.ad.alcatel.com with Microsoft SMTPSVC(6.0.3790.3959); Wed, 17 Jun 2009 08:08:25 -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_01C9EF4C.9B33AB2E"
Date: Wed, 17 Jun 2009 08:07:44 -0500
Message-ID: <4A5028372622294A99B8FFF6BD06EB7B058722EB@USDALSMBS03.ad3.ad.alcatel.com>
In-Reply-To: <A3C5DF08D38B6049839A6F553B331C76A8D3F150E2@ILPTMAIL02.ecitele.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [PWE3] Status of the PW redundancy drafts
Thread-Index: AcnvQUB7CRk2eR6KSqiN2qmvHq+MkgACvGOg
References: <A3C5DF08D38B6049839A6F553B331C76A8D3F150E2@ILPTMAIL02.ecitele.com>
From: "AISSAOUI Mustapha" <Mustapha.Aissaoui@alcatel-lucent.com>
To: "Alexander Vainshtein" <Alexander.Vainshtein@ecitele.com>, "MULEY Praveen" <Praveen.Muley@alcatel-lucent.com>
X-OriginalArrivalTime: 17 Jun 2009 13:08:25.0241 (UTC) FILETIME=[B2C27090:01C9EF4C]
X-Scanned-By: MIMEDefang 2.64 on 143.209.238.34
Cc: pwe3@ietf.org
Subject: Re: [PWE3] Status of the PW redundancy drafts
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: <http://www.ietf.org/mail-archive/web/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, 17 Jun 2009 13:09:10 -0000

This is a multi-part message in MIME format.

------_=_NextPart_001_01C9EF4C.9B33AB2E
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Sasha,
we are going to issue a new version before Stockholm with a few minor
changes.
=20
As for WG last call, we need to add OAM behaviour and we are planning on
doing that sometimes in August. Apart from that, we believe the drafts
are stable content wise.
=20
Regards,
Mustapha.


________________________________

	From: pwe3-bounces@ietf.org [mailto:pwe3-bounces@ietf.org] On
Behalf Of Alexander Vainshtein
	Sent: Wednesday, June 17, 2009 7:46 AM
	To: MULEY Praveen
	Cc: pwe3@ietf.org
	Subject: [PWE3] Status of the PW redundancy drafts
=09
=09
	Praveen hi,
	I've noticed that both draft-ietf-pwe3-pw-redundancy-01 and
draft-ietf-pwe3-pw-redundancy-bit-01 have expired almost 3 months ago.
	Do you and your co-authors plan to refresh these drafts before
Stockholm?
	Do you foresee any issues before sending them to the WG Last
call?
	=20
	Regards,
	     Sasha
	=20
	=20


------_=_NextPart_001_01C9EF4C.9B33AB2E
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2900.3562" name=3DGENERATOR></HEAD>
<BODY>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D296490413-17062009><FONT =
face=3DArial=20
size=3D2>Sasha,</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D296490413-17062009><FONT =
face=3DArial=20
size=3D2>we are going to issue a new version before Stockholm with a few =
minor=20
changes.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D296490413-17062009><FONT =
face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D296490413-17062009><FONT =
face=3DArial=20
size=3D2>As for WG last call, we need to add OAM behaviour and we are =
planning on=20
doing that sometimes in August. Apart from that, we believe the drafts =
are=20
stable content wise.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D296490413-17062009><FONT =
face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D296490413-17062009><FONT =
face=3DArial=20
size=3D2>Regards,</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D296490413-17062009><FONT =
face=3DArial=20
size=3D2>Mustapha.</FONT></SPAN></DIV><BR>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px =
solid; MARGIN-RIGHT: 0px">
  <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
  <HR tabIndex=3D-1>
  <FONT face=3DTahoma size=3D2><B>From:</B> pwe3-bounces@ietf.org=20
  [mailto:pwe3-bounces@ietf.org] <B>On Behalf Of </B>Alexander=20
  Vainshtein<BR><B>Sent:</B> Wednesday, June 17, 2009 7:46 =
AM<BR><B>To:</B>=20
  MULEY Praveen<BR><B>Cc:</B> pwe3@ietf.org<BR><B>Subject:</B> [PWE3] =
Status of=20
  the PW redundancy drafts<BR></FONT><BR></DIV>
  <DIV></DIV>
  <DIV><SPAN class=3D258202711-17062009><FONT face=3DArial =
size=3D2>Praveen=20
  hi,</FONT></SPAN></DIV>
  <DIV><SPAN class=3D258202711-17062009><FONT face=3DArial><FONT =
size=3D2>I've noticed=20
  that both <FONT =
color=3D#0000ff><EM>draft-ietf-pwe3-pw-redundancy-01</EM></FONT>=20
  and <EM><FONT =
color=3D#0000ff>draft-ietf-pwe3-pw-redundancy-bit-01</FONT></EM>=20
  have expired almost 3 months ago.</FONT></FONT></SPAN></DIV>
  <DIV><SPAN class=3D258202711-17062009><FONT face=3DArial size=3D2>Do =
you and your=20
  co-authors plan to refresh these drafts before =
Stockholm?</FONT></SPAN></DIV>
  <DIV><SPAN class=3D258202711-17062009><FONT face=3DArial size=3D2>Do =
you foresee any=20
  issues before sending them to the WG Last call?</FONT></SPAN></DIV>
  <DIV><SPAN class=3D258202711-17062009><FONT face=3DArial=20
  size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV><SPAN class=3D258202711-17062009><FONT face=3DArial=20
  size=3D2>Regards,</FONT></SPAN></DIV>
  <DIV><SPAN class=3D258202711-17062009><FONT face=3DArial=20
  size=3D2>&nbsp;&nbsp;&nbsp;&nbsp; Sasha</FONT></SPAN></DIV>
  <DIV><SPAN class=3D258202711-17062009><FONT face=3DArial=20
  size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV><SPAN class=3D258202711-17062009><FONT face=3DArial=20
  size=3D2></FONT></SPAN>&nbsp;</DIV></BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01C9EF4C.9B33AB2E--

From Alexander.Vainshtein@ecitele.com  Wed Jun 17 07:19:06 2009
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 33E553A6E77 for <pwe3@core3.amsl.com>; Wed, 17 Jun 2009 07:19:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[AWL=-0.000, 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 DzD1CjmWyNb4 for <pwe3@core3.amsl.com>; Wed, 17 Jun 2009 07:19:05 -0700 (PDT)
Received: from ilptiron01.ecitele.com (ilptiron01.ecitele.com [147.234.242.161]) by core3.amsl.com (Postfix) with ESMTP id 62D0C3A6E6F for <pwe3@ietf.org>; Wed, 17 Jun 2009 07:18:56 -0700 (PDT)
Received: from unknown (HELO ILPTAM01.ecitele.com) ([147.234.244.44]) by ilptiron01.ecitele.com with ESMTP; 17 Jun 2009 17:14:59 +0300
Received: from ilptexch01.ecitele.com ([172.31.244.40]) by ILPTAM01.ecitele.com with Microsoft SMTPSVC(6.0.3790.3959);  Wed, 17 Jun 2009 17:19:07 +0300
Received: from ILPTMAIL02.ecitele.com ([147.234.244.213]) by ilptexch01.ecitele.com ([172.31.244.40]) with mapi; Wed, 17 Jun 2009 17:19:06 +0300
From: Alexander Vainshtein <Alexander.Vainshtein@ecitele.com>
To: AISSAOUI Mustapha <Mustapha.Aissaoui@alcatel-lucent.com>
Date: Wed, 17 Jun 2009 17:19:06 +0300
Thread-Topic: [PWE3] Status of the PW redundancy drafts
Thread-Index: AcnvQUB7CRk2eR6KSqiN2qmvHq+MkgACvGOgAAKQn7A=
Message-ID: <A3C5DF08D38B6049839A6F553B331C76A8D3F1516E@ILPTMAIL02.ecitele.com>
References: <A3C5DF08D38B6049839A6F553B331C76A8D3F150E2@ILPTMAIL02.ecitele.com> <4A5028372622294A99B8FFF6BD06EB7B058722EB@USDALSMBS03.ad3.ad.alcatel.com>
In-Reply-To: <4A5028372622294A99B8FFF6BD06EB7B058722EB@USDALSMBS03.ad3.ad.alcatel.com>
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_A3C5DF08D38B6049839A6F553B331C76A8D3F1516EILPTMAIL02eci_"
MIME-Version: 1.0
X-OriginalArrivalTime: 17 Jun 2009 14:19:07.0257 (UTC) FILETIME=[9332B690:01C9EF56]
Cc: "pwe3@ietf.org" <pwe3@ietf.org>
Subject: Re: [PWE3] Status of the PW redundancy drafts
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: <http://www.ietf.org/mail-archive/web/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, 17 Jun 2009 14:19:06 -0000

--_000_A3C5DF08D38B6049839A6F553B331C76A8D3F1516EILPTMAIL02eci_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Mustapha,
Lots of thanks for a prompt response.

I will be waiting for the refreshed drafts.

Regards,
     Sasha

________________________________
From: AISSAOUI Mustapha [mailto:Mustapha.Aissaoui@alcatel-lucent.com]
Sent: Wednesday, June 17, 2009 4:08 PM
To: Alexander Vainshtein; MULEY Praveen
Cc: pwe3@ietf.org
Subject: RE: [PWE3] Status of the PW redundancy drafts

Sasha,
we are going to issue a new version before Stockholm with a few minor chang=
es.

As for WG last call, we need to add OAM behaviour and we are planning on do=
ing that sometimes in August. Apart from that, we believe the drafts are st=
able content wise.

Regards,
Mustapha.

________________________________
From: pwe3-bounces@ietf.org [mailto:pwe3-bounces@ietf.org] On Behalf Of Ale=
xander Vainshtein
Sent: Wednesday, June 17, 2009 7:46 AM
To: MULEY Praveen
Cc: pwe3@ietf.org
Subject: [PWE3] Status of the PW redundancy drafts

Praveen hi,
I've noticed that both draft-ietf-pwe3-pw-redundancy-01 and draft-ietf-pwe3=
-pw-redundancy-bit-01 have expired almost 3 months ago.
Do you and your co-authors plan to refresh these drafts before Stockholm?
Do you foresee any issues before sending them to the WG Last call?

Regards,
     Sasha



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

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2900.3527" name=3DGENERATOR></HEAD>
<BODY>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D795151814-17062009>Mustapha,</SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN class=3D795151814-17=
062009>Lots=20
of thanks for a prompt response.</SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D795151814-17062009></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN class=3D795151814-17=
062009>I will=20
be waiting for the refreshed drafts.</SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D795151814-17062009></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D795151814-17062009>Regards,</SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D795151814-17062009>&nbsp;&nbsp;&nbsp;&nbsp; Sasha</SPAN></FONT></DI=
V><BR>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px soli=
d; MARGIN-RIGHT: 0px">
  <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
  <HR tabIndex=3D-1>
  <FONT face=3DTahoma size=3D2><B>From:</B> AISSAOUI Mustapha=20
  [mailto:Mustapha.Aissaoui@alcatel-lucent.com] <BR><B>Sent:</B> Wednesday,=
 June=20
  17, 2009 4:08 PM<BR><B>To:</B> Alexander Vainshtein; MULEY=20
  Praveen<BR><B>Cc:</B> pwe3@ietf.org<BR><B>Subject:</B> RE: [PWE3] Status =
of=20
  the PW redundancy drafts<BR></FONT><BR></DIV>
  <DIV></DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D296490413-17062009><FONT face=
=3DArial=20
  size=3D2>Sasha,</FONT></SPAN></DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D296490413-17062009><FONT face=
=3DArial=20
  size=3D2>we are going to issue a new version before Stockholm with a few =
minor=20
  changes.</FONT></SPAN></DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D296490413-17062009><FONT face=
=3DArial=20
  size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D296490413-17062009><FONT face=
=3DArial=20
  size=3D2>As for WG last call, we need to add OAM behaviour and we are pla=
nning=20
  on doing that sometimes in August. Apart from that, we believe the drafts=
 are=20
  stable content wise.</FONT></SPAN></DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D296490413-17062009><FONT face=
=3DArial=20
  size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D296490413-17062009><FONT face=
=3DArial=20
  size=3D2>Regards,</FONT></SPAN></DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D296490413-17062009><FONT face=
=3DArial=20
  size=3D2>Mustapha.</FONT></SPAN></DIV><BR>
  <BLOCKQUOTE dir=3Dltr=20
  style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px so=
lid; MARGIN-RIGHT: 0px">
    <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
    <HR tabIndex=3D-1>
    <FONT face=3DTahoma size=3D2><B>From:</B> pwe3-bounces@ietf.org=20
    [mailto:pwe3-bounces@ietf.org] <B>On Behalf Of </B>Alexander=20
    Vainshtein<BR><B>Sent:</B> Wednesday, June 17, 2009 7:46 AM<BR><B>To:</=
B>=20
    MULEY Praveen<BR><B>Cc:</B> pwe3@ietf.org<BR><B>Subject:</B> [PWE3] Sta=
tus=20
    of the PW redundancy drafts<BR></FONT><BR></DIV>
    <DIV></DIV>
    <DIV><SPAN class=3D258202711-17062009><FONT face=3DArial size=3D2>Prave=
en=20
    hi,</FONT></SPAN></DIV>
    <DIV><SPAN class=3D258202711-17062009><FONT face=3DArial><FONT size=3D2=
>I've=20
    noticed that both <FONT=20
    color=3D#0000ff><EM>draft-ietf-pwe3-pw-redundancy-01</EM></FONT> and <E=
M><FONT=20
    color=3D#0000ff>draft-ietf-pwe3-pw-redundancy-bit-01</FONT></EM> have e=
xpired=20
    almost 3 months ago.</FONT></FONT></SPAN></DIV>
    <DIV><SPAN class=3D258202711-17062009><FONT face=3DArial size=3D2>Do yo=
u and your=20
    co-authors plan to refresh these drafts before=20
Stockholm?</FONT></SPAN></DIV>
    <DIV><SPAN class=3D258202711-17062009><FONT face=3DArial size=3D2>Do yo=
u foresee=20
    any issues before sending them to the WG Last call?</FONT></SPAN></DIV>
    <DIV><SPAN class=3D258202711-17062009><FONT face=3DArial=20
    size=3D2></FONT></SPAN>&nbsp;</DIV>
    <DIV><SPAN class=3D258202711-17062009><FONT face=3DArial=20
    size=3D2>Regards,</FONT></SPAN></DIV>
    <DIV><SPAN class=3D258202711-17062009><FONT face=3DArial=20
    size=3D2>&nbsp;&nbsp;&nbsp;&nbsp; Sasha</FONT></SPAN></DIV>
    <DIV><SPAN class=3D258202711-17062009><FONT face=3DArial=20
    size=3D2></FONT></SPAN>&nbsp;</DIV>
    <DIV><SPAN class=3D258202711-17062009><FONT face=3DArial=20
    size=3D2></FONT></SPAN>&nbsp;</DIV></BLOCKQUOTE></BLOCKQUOTE></BODY></H=
TML>

--_000_A3C5DF08D38B6049839A6F553B331C76A8D3F1516EILPTMAIL02eci_--

From Matthew.Bocci@alcatel-lucent.com  Wed Jun 17 07:26:36 2009
Return-Path: <Matthew.Bocci@alcatel-lucent.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 6AC6E3A6AB9 for <pwe3@core3.amsl.com>; Wed, 17 Jun 2009 07:26:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.561
X-Spam-Level: 
X-Spam-Status: No, score=-2.561 tagged_above=-999 required=5 tests=[AWL=-0.313, BAYES_00=-2.599, HELO_EQ_FR=0.35, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YwtDRXnnX9iC for <pwe3@core3.amsl.com>; Wed, 17 Jun 2009 07:26:32 -0700 (PDT)
Received: from smail2.alcatel.fr (smail2.alcatel.fr [64.208.49.57]) by core3.amsl.com (Postfix) with ESMTP id 2A1423A68DF for <pwe3@ietf.org>; Wed, 17 Jun 2009 07:26:32 -0700 (PDT)
Received: from FRVELSBHS03.ad2.ad.alcatel.com (frvelsbhs03.dc-m.alcatel-lucent.com [155.132.6.75]) by smail2.alcatel.fr (8.13.8/8.13.8/ICT) with ESMTP id n5HEQ8Qd007879;  Wed, 17 Jun 2009 16:26:31 +0200
Received: from FRVELSMBS11.ad2.ad.alcatel.com ([155.132.6.33]) by FRVELSBHS03.ad2.ad.alcatel.com with Microsoft SMTPSVC(6.0.3790.3959); Wed, 17 Jun 2009 16:26:28 +0200
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_01C9EF57.9A216189"
Date: Wed, 17 Jun 2009 16:26:27 +0200
Message-ID: <0458D2EE0C36744BABB36BE37805C29A03FB7946@FRVELSMBS11.ad2.ad.alcatel.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Comments on draft-ietf-pwe3-mpls-transport-03.txt
Thread-Index: AcnvV5mAL6RQiHBISN2fhvcapyimEg==
From: "BOCCI Matthew" <Matthew.Bocci@alcatel-lucent.com>
To: <draft-ietf-pwe3-mpls-transport@tools.ietf.org>
X-OriginalArrivalTime: 17 Jun 2009 14:26:28.0473 (UTC) FILETIME=[9A2EEE90:01C9EF57]
X-Scanned-By: MIMEDefang 2.57 on 155.132.188.80
Cc: pwe3@ietf.org
Subject: [PWE3] Comments on 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: <http://www.ietf.org/mail-archive/web/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, 17 Jun 2009 14:26:36 -0000

This is a multi-part message in MIME format.

------_=_NextPart_001_01C9EF57.9A216189
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Authors,

In reviewing the draft while preparing the proto statement, I have noted
a few comments (mostly derived from ID NITS), as follows:

-	The draft is informational, but contains RFC2119 like language
e.g. capitalised SHOULD. Please check though the draft and revise
accordingly.
-	The reference to the mpls-tp requirements draft is out of date,
-	The reference to draft-ietf-pwe3-vccv-bfd is missing (line 214)
-	Line 204 shows a 'TBD' for the VCCV channel type for VCCV-BFD.
Please update this.
-	ali-mpls-rsvp-te-no-php-oob-mapping is cited as a normative
reference, but this expired a while ago.=20
-	Please check the boiler plate as to whether you need to add a
pre-RFC5378 disclaimer

Best regards

Matthew=20

------_=_NextPart_001_01C9EF57.9A216189
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.5.7655.1">
<TITLE>Comments on draft-ietf-pwe3-mpls-transport-03.txt</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/rtf format -->

<P DIR=3DLTR><SPAN LANG=3D"de"></SPAN><SPAN LANG=3D"de"></SPAN><SPAN =
LANG=3D"en-gb"></SPAN><SPAN LANG=3D"en-gb"><FONT SIZE=3D2 =
FACE=3D"Arial">Authors,</FONT></SPAN><SPAN LANG=3D"de"></SPAN><SPAN =
LANG=3D"de"></SPAN><SPAN LANG=3D"en-gb"></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"de"></SPAN><SPAN LANG=3D"de"></SPAN><SPAN =
LANG=3D"en-gb"></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-gb"><FONT SIZE=3D2 FACE=3D"Arial">In =
reviewing the draft while preparing the proto statement,</FONT><FONT =
SIZE=3D2 FACE=3D"Arial"> I have noted a few comments</FONT></SPAN><SPAN =
LANG=3D"de"></SPAN><SPAN LANG=3D"de"></SPAN><SPAN =
LANG=3D"en-gb"></SPAN><SPAN LANG=3D"en-gb"><FONT SIZE=3D2 =
FACE=3D"Arial"> (mostly derived from ID NITS)</FONT></SPAN><SPAN =
LANG=3D"de"></SPAN><SPAN LANG=3D"de"></SPAN><SPAN =
LANG=3D"en-gb"></SPAN><SPAN LANG=3D"en-gb"><FONT SIZE=3D2 =
FACE=3D"Arial">, as follows:</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-gb"><FONT SIZE=3D2 =
FACE=3D"Arial">-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</FONT></SPAN><SPAN =
LANG=3D"en-gb"></SPAN><SPAN LANG=3D"de"></SPAN><SPAN =
LANG=3D"de"></SPAN><SPAN LANG=3D"en-gb"></SPAN><SPAN LANG=3D"en-gb"> =
<FONT SIZE=3D2 FACE=3D"Arial">The draft is informational, =
but</FONT></SPAN><SPAN LANG=3D"de"></SPAN><SPAN LANG=3D"de"></SPAN><SPAN =
LANG=3D"en-gb"></SPAN><SPAN LANG=3D"en-gb"> <FONT SIZE=3D2 =
FACE=3D"Arial">contains</FONT></SPAN><SPAN LANG=3D"de"></SPAN><SPAN =
LANG=3D"de"></SPAN><SPAN LANG=3D"en-gb"></SPAN><SPAN =
LANG=3D"en-gb"><FONT SIZE=3D2 FACE=3D"Arial"> RFC2119 =
like</FONT></SPAN><SPAN LANG=3D"de"></SPAN><SPAN =
LANG=3D"de"></SPAN><SPAN LANG=3D"en-gb"></SPAN><SPAN LANG=3D"en-gb"> =
<FONT SIZE=3D2 FACE=3D"Arial">language</FONT></SPAN><SPAN =
LANG=3D"de"></SPAN><SPAN LANG=3D"de"></SPAN><SPAN =
LANG=3D"en-gb"></SPAN><SPAN LANG=3D"en-gb"><FONT SIZE=3D2 =
FACE=3D"Arial"> e.g.</FONT></SPAN><SPAN LANG=3D"de"></SPAN><SPAN =
LANG=3D"de"></SPAN><SPAN LANG=3D"en-gb"></SPAN><SPAN LANG=3D"en-gb"> =
<FONT SIZE=3D2 FACE=3D"Arial">capitalised SHOULD</FONT></SPAN><SPAN =
LANG=3D"de"></SPAN><SPAN LANG=3D"de"></SPAN><SPAN =
LANG=3D"en-gb"></SPAN><SPAN LANG=3D"en-gb"><FONT SIZE=3D2 =
FACE=3D"Arial">.</FONT></SPAN><SPAN LANG=3D"de"></SPAN><SPAN =
LANG=3D"de"></SPAN><SPAN LANG=3D"en-gb"></SPAN><SPAN LANG=3D"en-gb"> =
<FONT SIZE=3D2 FACE=3D"Arial">Please check though the draft and =
re</FONT><FONT SIZE=3D2 FACE=3D"Arial">vise =
accordingly.</FONT></SPAN><SPAN LANG=3D"de"></SPAN><SPAN =
LANG=3D"de"></SPAN><SPAN LANG=3D"en-gb"></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-gb"><FONT SIZE=3D2 =
FACE=3D"Arial">-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</FONT></SPAN><SPAN =
LANG=3D"en-gb"></SPAN><SPAN LANG=3D"de"></SPAN><SPAN =
LANG=3D"de"></SPAN><SPAN LANG=3D"en-gb"></SPAN><SPAN LANG=3D"en-gb"> =
<FONT SIZE=3D2 FACE=3D"Arial">The reference to the mpls-tp requirements =
draft is out of date,</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-gb"><FONT SIZE=3D2 =
FACE=3D"Arial">-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</FONT></SPAN><SPAN =
LANG=3D"en-gb"></SPAN><SPAN LANG=3D"de"></SPAN><SPAN =
LANG=3D"de"></SPAN><SPAN LANG=3D"en-gb"></SPAN><SPAN LANG=3D"en-gb"> =
<FONT SIZE=3D2 FACE=3D"Arial">The reference to</FONT></SPAN><SPAN =
LANG=3D"de"></SPAN><SPAN LANG=3D"de"></SPAN><SPAN =
LANG=3D"en-gb"></SPAN><SPAN LANG=3D"en-gb"> <FONT SIZE=3D2 =
FACE=3D"Arial">draft-ietf-pwe3-vccv-bfd</FONT></SPAN><SPAN =
LANG=3D"de"></SPAN><SPAN LANG=3D"de"></SPAN><SPAN =
LANG=3D"en-gb"></SPAN><SPAN LANG=3D"en-gb"><FONT SIZE=3D2 =
FACE=3D"Arial"> is missing</FONT><FONT SIZE=3D2 FACE=3D"Arial"> (line =
214)</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-gb"><FONT SIZE=3D2 =
FACE=3D"Arial">-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</FONT></SPAN><SPAN =
LANG=3D"en-gb"> <FONT SIZE=3D2 FACE=3D"Arial">Line 20</FONT></SPAN><SPAN =
LANG=3D"de"></SPAN><SPAN LANG=3D"de"></SPAN><SPAN =
LANG=3D"en-gb"></SPAN><SPAN LANG=3D"en-gb"><FONT SIZE=3D2 =
FACE=3D"Arial">4 shows a</FONT></SPAN><SPAN LANG=3D"de"></SPAN><SPAN =
LANG=3D"de"></SPAN><SPAN LANG=3D"en-gb"></SPAN><SPAN LANG=3D"en-gb"> =
<FONT SIZE=3D2 FACE=3D"Arial">&#8216;</FONT></SPAN><SPAN =
LANG=3D"de"></SPAN><SPAN LANG=3D"de"></SPAN><SPAN =
LANG=3D"en-gb"></SPAN><SPAN LANG=3D"en-gb"><FONT SIZE=3D2 =
FACE=3D"Arial">TBD</FONT></SPAN><SPAN LANG=3D"de"></SPAN><SPAN =
LANG=3D"de"></SPAN><SPAN LANG=3D"en-gb"></SPAN><SPAN =
LANG=3D"en-gb"><FONT SIZE=3D2 FACE=3D"Arial">&#8217;</FONT></SPAN><SPAN =
LANG=3D"de"></SPAN><SPAN LANG=3D"de"></SPAN><SPAN =
LANG=3D"en-gb"></SPAN><SPAN LANG=3D"en-gb"><FONT SIZE=3D2 =
FACE=3D"Arial"> for the VCCV channel ty</FONT><FONT SIZE=3D2 =
FACE=3D"Arial">pe for VCCV-BFD.</FONT> <FONT SIZE=3D2 =
FACE=3D"Arial">P</FONT><FONT SIZE=3D2 FACE=3D"Arial">lease update =
this.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-gb"><FONT SIZE=3D2 =
FACE=3D"Arial">-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</FONT></SPAN><SPAN =
LANG=3D"en-gb"></SPAN><SPAN LANG=3D"de"></SPAN><SPAN =
LANG=3D"de"></SPAN><SPAN LANG=3D"en-gb"></SPAN><SPAN LANG=3D"en-gb"> =
<FONT SIZE=3D2 =
FACE=3D"Arial">ali-mpls-rsvp-te-no-php-oob-mapping</FONT></SPAN><SPAN =
LANG=3D"de"></SPAN><SPAN LANG=3D"de"></SPAN><SPAN =
LANG=3D"en-gb"></SPAN><SPAN LANG=3D"en-gb"><FONT SIZE=3D2 =
FACE=3D"Arial"> is cited</FONT></SPAN><SPAN LANG=3D"de"></SPAN><SPAN =
LANG=3D"de"></SPAN><SPAN LANG=3D"en-gb"></SPAN><SPAN =
LANG=3D"en-gb"><FONT SIZE=3D2 FACE=3D"Arial"> as a normative =
reference</FONT></SPAN><SPAN LANG=3D"de"></SPAN><SPAN =
LANG=3D"de"></SPAN><SPAN LANG=3D"en-gb"></SPAN><SPAN =
LANG=3D"en-gb"><FONT SIZE=3D2 FACE=3D"Arial">, but this expired a while =
ago</FONT></SPAN><SPAN LANG=3D"de"></SPAN><SPAN LANG=3D"de"></SPAN><SPAN =
LANG=3D"en-gb"></SPAN><SPAN LANG=3D"en-gb"><FONT SIZE=3D2 =
FACE=3D"Arial">.</FONT></SPAN><SPAN LANG=3D"de"></SPAN><SPAN =
LANG=3D"de"></SPAN><SPAN LANG=3D"en-gb"> </SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-gb"><FONT SIZE=3D2 =
FACE=3D"Arial">-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</FONT></SPAN><SPAN =
LANG=3D"en-gb"></SPAN><SPAN LANG=3D"en-gb"> <FONT SIZE=3D2 =
FACE=3D"Arial">P</FONT><FONT SIZE=3D2 FACE=3D"Arial">lease</FONT> <FONT =
SIZE=3D2 FACE=3D"Arial">check the</FONT> <FONT SIZE=3D2 =
FACE=3D"Arial">boiler</FONT><FONT SIZE=3D2 FACE=3D"Arial"> plate as to =
whether you need to add a</FONT></SPAN><SPAN LANG=3D"de"></SPAN><SPAN =
LANG=3D"de"></SPAN><SPAN LANG=3D"en-gb"></SPAN><SPAN LANG=3D"en-gb"> =
<FONT SIZE=3D2 FACE=3D"Arial">pre-RFC5378</FONT></SPAN><SPAN =
LANG=3D"de"></SPAN><SPAN LANG=3D"de"></SPAN><SPAN =
LANG=3D"en-gb"></SPAN><SPAN LANG=3D"en-gb"><FONT SIZE=3D2 =
FACE=3D"Arial"> disclaimer</FONT></SPAN><SPAN LANG=3D"de"></SPAN><SPAN =
LANG=3D"de"></SPAN><SPAN LANG=3D"en-gb"></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"de"></SPAN><SPAN LANG=3D"de"></SPAN><SPAN =
LANG=3D"en-gb"></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"de"></SPAN><SPAN LANG=3D"de"></SPAN><SPAN =
LANG=3D"en-gb"></SPAN><SPAN LANG=3D"en-gb"><FONT SIZE=3D2 =
FACE=3D"Arial">B</FONT><FONT SIZE=3D2 FACE=3D"Arial">est =
regards</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-gb"><FONT SIZE=3D2 =
FACE=3D"Arial">Matthew</FONT></SPAN><SPAN LANG=3D"de"></SPAN><SPAN =
LANG=3D"de"></SPAN><SPAN LANG=3D"en-gb"></SPAN><SPAN =
LANG=3D"en-gb"><FONT SIZE=3D2 FACE=3D"Arial"></FONT></SPAN><SPAN =
LANG=3D"de"></SPAN><SPAN LANG=3D"de"></SPAN><SPAN LANG=3D"en-gb"> =
</SPAN></P>

</BODY>
</HTML>
------_=_NextPart_001_01C9EF57.9A216189--

From stbryant@cisco.com  Wed Jun 17 08:03:41 2009
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 EE88828C254 for <pwe3@core3.amsl.com>; Wed, 17 Jun 2009 08:03:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.401
X-Spam-Level: 
X-Spam-Status: No, score=-10.401 tagged_above=-999 required=5 tests=[AWL=0.198, 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 ACECJ2clC9xJ for <pwe3@core3.amsl.com>; Wed, 17 Jun 2009 08:03:41 -0700 (PDT)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140]) by core3.amsl.com (Postfix) with ESMTP id 7379C28C0E2 for <pwe3@ietf.org>; Wed, 17 Jun 2009 08:03:39 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.42,236,1243814400"; d="scan'208";a="43033138"
Received: from ams-dkim-2.cisco.com ([144.254.224.139]) by ams-iport-1.cisco.com with ESMTP; 17 Jun 2009 15:03:51 +0000
Received: from ams-core-1.cisco.com (ams-core-1.cisco.com [144.254.224.150]) by ams-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id n5HF3ppF007402;  Wed, 17 Jun 2009 17:03:51 +0200
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 n5HF3or2019921; Wed, 17 Jun 2009 15:03:50 GMT
Received: from Stewarts-Computer-2.local (localhost [127.0.0.1]) by cisco.com (8.11.7p3+Sun/8.8.8) with ESMTP id n5HF3nm22223; Wed, 17 Jun 2009 16:03:50 +0100 (BST)
Message-ID: <4A3905D5.7070000@cisco.com>
Date: Wed, 17 Jun 2009 16:03:49 +0100
From: Stewart Bryant <stbryant@cisco.com>
User-Agent: Thunderbird 2.0.0.19 (Macintosh/20081209)
MIME-Version: 1.0
To: BOCCI Matthew <Matthew.Bocci@alcatel-lucent.com>
References: <0458D2EE0C36744BABB36BE37805C29A03FB7946@FRVELSMBS11.ad2.ad.alcatel.com>
In-Reply-To: <0458D2EE0C36744BABB36BE37805C29A03FB7946@FRVELSMBS11.ad2.ad.alcatel.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1087; t=1245251031; x=1246115031; c=relaxed/simple; s=amsdkim2001; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=stbryant@cisco.com; z=From:=20Stewart=20Bryant=20<stbryant@cisco.com> |Subject:=20Re=3A=20[PWE3]=20Comments=20on=20draft-ietf-pwe 3-mpls-transport-03.txt |Sender:=20; bh=lXyjvOM1r8QE1FZki82RwGZ/TIdNem3QImn1acchvq8=; b=d+hdh3RyE26QCKzm9Mp3RLhFMBA7icT/AIIpH0+yQQyaVOsitkn1EG3pjd Yq6dKhDrOCmjBF7NZQ4YMFwQhFTZl4U/4qvTQB780zFExlAzfOMrMgsBojUN yr7QdoSDkt;
Authentication-Results: ams-dkim-2; header.From=stbryant@cisco.com; dkim=pass ( sig from cisco.com/amsdkim2001 verified; ); 
Cc: draft-ietf-pwe3-mpls-transport@tools.ietf.org, pwe3@ietf.org
Subject: Re: [PWE3] Comments on draft-ietf-pwe3-mpls-transport-03.txt
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: <http://www.ietf.org/mail-archive/web/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, 17 Jun 2009 15:03:42 -0000

BOCCI Matthew wrote:
>
> Authors,
>
> In reviewing the draft while preparing the proto statement, I have 
> noted a few comments (mostly derived from ID NITS), as follows:
>
> - The draft is informational, but contains RFC2119 like language e.g. 
> capitalised SHOULD. Please check though the draft and revise accordingly.
>
> - The reference to the mpls-tp requirements draft is out of date,
>
> - The reference to draft-ietf-pwe3-vccv-bfd is missing (line 214)
>
> - Line 204 shows a ‘TBD’ for the VCCV channel type for VCCV-BFD. 
> Please update this.
>
> - ali-mpls-rsvp-te-no-php-oob-mapping is cited as a normative 
> reference, but this expired a while ago.
>
> - Please check the boiler plate as to whether you need to add a 
> pre-RFC5378 disclaimer
>
> Best regards
>
> Matthew
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> pwe3 mailing list
> pwe3@ietf.org
> https://www.ietf.org/mailman/listinfo/pwe3
>   
Will deal with by the end of the week

Stewart

From rcallon@juniper.net  Wed Jun 17 19:45:48 2009
Return-Path: <rcallon@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 E4E523A6C0F for <pwe3@core3.amsl.com>; Wed, 17 Jun 2009 19:45:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.346
X-Spam-Level: 
X-Spam-Status: No, score=-6.346 tagged_above=-999 required=5 tests=[AWL=0.252,  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 XgdCkEddEaHW for <pwe3@core3.amsl.com>; Wed, 17 Jun 2009 19:45:48 -0700 (PDT)
Received: from exprod7og107.obsmtp.com (exprod7og107.obsmtp.com [64.18.2.167]) by core3.amsl.com (Postfix) with ESMTP id EBC453A6820 for <pwe3@ietf.org>; Wed, 17 Jun 2009 19:45:44 -0700 (PDT)
Received: from source ([66.129.224.36]) (using TLSv1) by exprod7ob107.postini.com ([64.18.6.12]) with SMTP ID DSNKSjmqZNFbU3wSLMVrEPfYagRfYNsrGYYF@postini.com; Wed, 17 Jun 2009 19:46:00 PDT
Received: from p-emfe02-wf.jnpr.net (172.28.145.25) by P-EMHUB02-HQ.jnpr.net (172.24.192.36) with Microsoft SMTP Server (TLS) id 8.1.375.2; Wed, 17 Jun 2009 19:45:48 -0700
Received: from EMBX01-WF.jnpr.net ([fe80::1914:3299:33d9:e43b]) by p-emfe02-wf.jnpr.net ([fe80::c126:c633:d2dc:8090%11]) with mapi; Wed, 17 Jun 2009 22:45:47 -0400
From: Ross Callon <rcallon@juniper.net>
To: BOCCI Matthew <Matthew.Bocci@alcatel-lucent.com>, "draft-ietf-pwe3-mpls-transport@tools.ietf.org" <draft-ietf-pwe3-mpls-transport@tools.ietf.org>
Date: Wed, 17 Jun 2009 22:45:45 -0400
Thread-Topic: Comments on draft-ietf-pwe3-mpls-transport-03.txt
Thread-Index: AcnvV5mAL6RQiHBISN2fhvcapyimEgAZsNEQ
Message-ID: <DF7F294AF4153D498141CBEFADB1770498239ADDF5@EMBX01-WF.jnpr.net>
References: <0458D2EE0C36744BABB36BE37805C29A03FB7946@FRVELSMBS11.ad2.ad.alcatel.com>
In-Reply-To: <0458D2EE0C36744BABB36BE37805C29A03FB7946@FRVELSMBS11.ad2.ad.alcatel.com>
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_DF7F294AF4153D498141CBEFADB1770498239ADDF5EMBX01WFjnprn_"
MIME-Version: 1.0
Cc: "pwe3@ietf.org" <pwe3@ietf.org>
Subject: Re: [PWE3] Comments on 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: <http://www.ietf.org/mail-archive/web/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, 18 Jun 2009 02:45:49 -0000

--_000_DF7F294AF4153D498141CBEFADB1770498239ADDF5EMBX01WFjnprn_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable


>  Authors,
>  In reviewing the draft while preparing the proto statement, I have noted=
 a few
> comments (mostly derived from ID NITS), as follows:
>
>  -       The draft is informational, but contains RFC2119 like language e=
.g.
>          capitalised SHOULD. Please check though the draft and revise acc=
ordingly.


Without commenting on the specifics of whether this language is appropriate=
 as used in this particular draft,
in general RFC2119 language is permitted in informational documents.

Thanks, Ross


--_000_DF7F294AF4153D498141CBEFADB1770498239ADDF5EMBX01WFjnprn_
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:sc=
hemas-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)">
<title>Comments on draft-ietf-pwe3-mpls-transport-03.txt</title>
<style>
<!--
 /* 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;}
p
	{mso-margin-top-alt:auto;
	margin-right:0in;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	font-size:12.0pt;
	font-family:"Times New Roman";}
span.EmailStyle18
	{mso-style-type:personal-reply;
	font-family:Arial;
	color:navy;}
@page Section1
	{size: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=3D3 face=3D"Times New Roman"><span style=3D=
'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

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

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span style=3D=
'font-size:
12.0pt'>&gt; &nbsp;In reviewing the draft while preparing the proto stateme=
nt,
I have noted a few<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span style=3D=
'font-size:
12.0pt'>&gt; comments (mostly derived from ID NITS), as follows:<o:p></o:p>=
</span></font></p>

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

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span style=3D=
'font-size:
12.0pt'>&gt;&nbsp; -&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; The draft is
informational, but contains RFC2119 like language e.g.<o:p></o:p></span></f=
ont></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span style=3D=
'font-size:
12.0pt'>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;capitali=
sed
SHOULD. Please check though the draft and revise accordingly.<o:p></o:p></s=
pan></font></p>

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

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

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span lang=3DE=
N-GB
style=3D'font-size:12.0pt'>Without commenting on the specifics of whether t=
his
language is appropriate as used in this particular draft, <o:p></o:p></span=
></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span lang=3DE=
N-GB
style=3D'font-size:12.0pt'>in general RFC2119 language is permitted in
informational documents. <o:p></o:p></span></font></p>

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

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span lang=3DE=
N-GB
style=3D'font-size:12.0pt'>Thanks, Ross<o:p></o:p></span></font></p>

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

</div>

</body>

</html>

--_000_DF7F294AF4153D498141CBEFADB1770498239ADDF5EMBX01WFjnprn_--

From Matthew.Bocci@alcatel-lucent.com  Thu Jun 18 01:09:08 2009
Return-Path: <Matthew.Bocci@alcatel-lucent.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 B8D2A3A67EB for <pwe3@core3.amsl.com>; Thu, 18 Jun 2009 01:09:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.498
X-Spam-Level: 
X-Spam-Status: No, score=-2.498 tagged_above=-999 required=5 tests=[AWL=-0.250, BAYES_00=-2.599, HELO_EQ_FR=0.35, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AVNE79cEAd77 for <pwe3@core3.amsl.com>; Thu, 18 Jun 2009 01:09:06 -0700 (PDT)
Received: from smail2.alcatel.fr (smail2.alcatel.fr [64.208.49.57]) by core3.amsl.com (Postfix) with ESMTP id CB20E3A6B79 for <pwe3@ietf.org>; Thu, 18 Jun 2009 01:08:44 -0700 (PDT)
Received: from FRVELSBHS03.ad2.ad.alcatel.com (frvelsbhs03.dc-m.alcatel-lucent.com [155.132.6.75]) by smail2.alcatel.fr (8.13.8/8.13.8/ICT) with ESMTP id n5I88rVs021000;  Thu, 18 Jun 2009 10:08:54 +0200
Received: from FRVELSMBS11.ad2.ad.alcatel.com ([155.132.6.33]) by FRVELSBHS03.ad2.ad.alcatel.com with Microsoft SMTPSVC(6.0.3790.3959); Thu, 18 Jun 2009 10:08:53 +0200
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_01C9EFEC.0550433C"
Date: Thu, 18 Jun 2009 10:08:51 +0200
Message-ID: <0458D2EE0C36744BABB36BE37805C29A03FB7B98@FRVELSMBS11.ad2.ad.alcatel.com>
In-Reply-To: <DF7F294AF4153D498141CBEFADB1770498239ADDF5@EMBX01-WF.jnpr.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Comments on draft-ietf-pwe3-mpls-transport-03.txt
Thread-Index: AcnvV5mAL6RQiHBISN2fhvcapyimEgAZsNEQAAtd/XA=
References: <0458D2EE0C36744BABB36BE37805C29A03FB7946@FRVELSMBS11.ad2.ad.alcatel.com> <DF7F294AF4153D498141CBEFADB1770498239ADDF5@EMBX01-WF.jnpr.net>
From: "BOCCI Matthew" <Matthew.Bocci@alcatel-lucent.com>
To: "Ross Callon" <rcallon@juniper.net>, <draft-ietf-pwe3-mpls-transport@tools.ietf.org>
X-OriginalArrivalTime: 18 Jun 2009 08:08:53.0787 (UTC) FILETIME=[0559EEB0:01C9EFEC]
X-Scanned-By: MIMEDefang 2.57 on 155.132.188.80
Cc: pwe3@ietf.org
Subject: Re: [PWE3] Comments on 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: <http://www.ietf.org/mail-archive/web/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, 18 Jun 2009 08:09:08 -0000

This is a multi-part message in MIME format.

------_=_NextPart_001_01C9EFEC.0550433C
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Ross,

=20

In that case, the draft should probably also include a 'Specification of
requirements' section and a reference to RFC2119.

=20

Regards

=20

Matthew

=20

________________________________

From: Ross Callon [mailto:rcallon@juniper.net]=20
Sent: 18 June 2009 03:46
To: BOCCI Matthew; draft-ietf-pwe3-mpls-transport@tools.ietf.org
Cc: pwe3@ietf.org
Subject: RE: Comments on draft-ietf-pwe3-mpls-transport-03.txt

=20

=20

>  Authors,

>  In reviewing the draft while preparing the proto statement, I have
noted a few

> comments (mostly derived from ID NITS), as follows:

>=20

>  -       The draft is informational, but contains RFC2119 like
language e.g.

>          capitalised SHOULD. Please check though the draft and revise
accordingly.

=20

=20

Without commenting on the specifics of whether this language is
appropriate as used in this particular draft,=20

in general RFC2119 language is permitted in informational documents.=20

=20

Thanks, Ross

=20


------_=_NextPart_001_01C9EFEC.0550433C
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:st1=3D"urn:schemas-microsoft-com:office:smarttags" =
xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]-->
<title>Comments on draft-ietf-pwe3-mpls-transport-03.txt</title>
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"PersonName"/>
<!--[if !mso]>
<style>
st1\:*{behavior:url(#default#ieooui) }
</style>
<![endif]-->
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:"MS Mincho";
	panose-1:2 2 6 9 4 2 5 8 3 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:"\@MS Mincho";
	panose-1:2 2 6 9 4 2 5 8 3 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	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;}
p
	{mso-margin-top-alt:auto;
	margin-right:0cm;
	mso-margin-bottom-alt:auto;
	margin-left:0cm;
	font-size:12.0pt;
	font-family:"Times New Roman";}
span.EmailStyle18
	{mso-style-type:personal;
	font-family:Arial;
	color:navy;}
span.EmailStyle19
	{mso-style-type:personal-reply;
	font-family:Arial;
	color:navy;}
@page Section1
	{size:612.0pt 792.0pt;
	margin:72.0pt 90.0pt 72.0pt 90.0pt;}
div.Section1
	{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]-->
</head>

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

<div class=3DSection1>

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

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

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>In that case, the draft should =
probably
also include a &#8216;Specification of requirements&#8217; section and a
reference to RFC2119.<o:p></o:p></span></font></p>

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

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


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

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


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

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

<div>

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

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

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

<p class=3DMsoNormal><b><font size=3D2 face=3DTahoma><span lang=3DEN-US
style=3D'font-size:10.0pt;font-family:Tahoma;font-weight:bold'>From:</spa=
n></font></b><font
size=3D2 face=3DTahoma><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:Tahoma'>
Ross Callon [mailto:rcallon@juniper.net] <br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> 18 June 2009 =
03:46<br>
<b><span style=3D'font-weight:bold'>To:</span></b> BOCCI Matthew; =
<st1:PersonName
w:st=3D"on">draft-ietf-pwe3-mpls-transport@tools.ietf.org</st1:PersonName=
><br>
<b><span style=3D'font-weight:bold'>Cc:</span></b> pwe3@ietf.org<br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> RE: Comments on
draft-ietf-pwe3-mpls-transport-03.txt</span></font><span =
lang=3DEN-US><o:p></o:p></span></p>

</div>

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

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

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

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
lang=3DEN-US
style=3D'font-size:12.0pt'>&gt; &nbsp;In reviewing the draft while =
preparing the
proto statement, I have noted a few<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
lang=3DEN-US
style=3D'font-size:12.0pt'>&gt; comments (mostly derived from ID NITS), =
as
follows:<o:p></o:p></span></font></p>

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

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
lang=3DEN-US
style=3D'font-size:12.0pt'>&gt;&nbsp; =
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; The
draft is informational, but contains RFC2119 like language =
e.g.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
lang=3DEN-US
style=3D'font-size:12.0pt'>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;
&nbsp;capitalised SHOULD. Please check though the draft and revise =
accordingly.<o:p></o:p></span></font></p>

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

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

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>Without commenting on the specifics of whether this language is
appropriate as used in this particular draft, =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>in general RFC2119 language is permitted in informational =
documents. <o:p></o:p></span></font></p>

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

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

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

</div>

</div>

</body>

</html>

------_=_NextPart_001_01C9EFEC.0550433C--

From root@core3.amsl.com  Thu Jun 18 23:30:01 2009
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 B6F213A6A72; Thu, 18 Jun 2009 23:30:01 -0700 (PDT)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20090619063001.B6F213A6A72@core3.amsl.com>
Date: Thu, 18 Jun 2009 23:30:01 -0700 (PDT)
Cc: pwe3@ietf.org
Subject: [PWE3] I-D Action:draft-ietf-pwe3-iccp-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: <http://www.ietf.org/mail-archive/web/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, 19 Jun 2009 06: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           : Inter-Chassis Communication Protocol for L2VPN PE Redundancy
	Author(s)       : L. Martini, et al.
	Filename        : draft-ietf-pwe3-iccp-00.txt
	Pages           : 60
	Date            : 2009-06-18

This document specifies an inter-chassis communication protocol
(ICCP) that enables Provider Edge (PE) device redundancy for Virtual
Private Wire Service (VPWS) and Virtual Private LAN Service (VPLS)
applications. The protocol runs within a set of two or more PEs,
forming a redundancy group, for the purpose of synchronizing data
amongst the systems. It accommodates multi-chassis attachment circuit
as well as pseudowire redundancy mechanisms.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-pwe3-iccp-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-iccp-00.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

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


--NextPart--

From prvs=4176daae3=euddasi@redback.com  Mon Jun 22 09:06:13 2009
Return-Path: <prvs=4176daae3=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 9128328C208 for <pwe3@core3.amsl.com>; Mon, 22 Jun 2009 09:06:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.226
X-Spam-Level: 
X-Spam-Status: No, score=-2.226 tagged_above=-999 required=5 tests=[AWL=0.373,  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 0uys3Bm6Zh8k for <pwe3@core3.amsl.com>; Mon, 22 Jun 2009 09:06:13 -0700 (PDT)
Received: from mgate.redback.com (mgate.redback.com [155.53.3.41]) by core3.amsl.com (Postfix) with ESMTP id ECA1C28C201 for <pwe3@ietf.org>; Mon, 22 Jun 2009 09:06:12 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.42,269,1243839600";  d="scan'208";a="2662674"
Received: from prattle.redback.com ([155.53.12.9]) by mgate.redback.com with ESMTP; 22 Jun 2009 09:06:28 -0700
Received: from localhost (localhost [127.0.0.1]) by prattle.redback.com (Postfix) with ESMTP id 97B9850CDC1 for <pwe3@ietf.org>; Mon, 22 Jun 2009 09:06:28 -0700 (PDT)
Received: from prattle.redback.com ([127.0.0.1]) by localhost (prattle [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 21464-01 for <pwe3@ietf.org>; Mon, 22 Jun 2009 09:06:28 -0700 (PDT)
Received: from rbsjx.ad.redback.com (rbsjxh2.redback.com [155.53.14.106]) by prattle.redback.com (Postfix) with ESMTP id 85F2450CDBE for <pwe3@ietf.org>; Mon, 22 Jun 2009 09:06:28 -0700 (PDT)
Received: from RBSJX.ad.redback.com ([155.53.14.103]) by rbsjxh2.ad.redback.com ([155.53.14.106]) with mapi; Mon, 22 Jun 2009 09:06:28 -0700
From: David Sinicrope <euddasi@redback.com>
To: "pwe3@ietf.org" <pwe3@ietf.org>
Date: Mon, 22 Jun 2009 09:06:27 -0700
Thread-Topic: Time slots for IETF 75 PWE3 meeting
Thread-Index: AcmO1f4o4AcNXYD1F0eyztRRXFz+YBkfWd+X
Message-ID: <C6652443.29D8B%euddasi@redback.com>
In-Reply-To: <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: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: [PWE3] Time slots for IETF 75 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: <http://www.ietf.org/mail-archive/web/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, 22 Jun 2009 16:07:36 -0000

Hi All,
Please let me know if you would like a time slot for the PWE3 meeting durin=
g
IETF 75.
I=B9ll need the desired duration, topic/title, and presenter for each reque=
st.
Thanks!
Dave=20


From benjamin.niven-jenkins@bt.com  Mon Jun 22 15:28:10 2009
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 D8CF528C253; Mon, 22 Jun 2009 15:28:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.375
X-Spam-Level: *
X-Spam-Status: No, score=1.375 tagged_above=-999 required=5 tests=[AWL=-2.906,  BAYES_20=-0.74, FRT_BELOW2=2.154, J_CHICKENPOX_34=0.6, J_CHICKENPOX_45=0.6, J_CHICKENPOX_46=0.6, RCVD_IN_DNSWL_LOW=-1, RCVD_NUMERIC_HELO=2.067]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id p5aw5QOS2760; Mon, 22 Jun 2009 15:28:07 -0700 (PDT)
Received: from smtp1.smtp.bt.com (smtp1.smtp.bt.com [217.32.164.137]) by core3.amsl.com (Postfix) with ESMTP id 7A3A328C266; Mon, 22 Jun 2009 15:28:05 -0700 (PDT)
Received: from E03MVB3-UKBR.domain1.systemhost.net ([193.113.197.108]) by smtp1.smtp.bt.com with Microsoft SMTPSVC(6.0.3790.3959);  Mon, 22 Jun 2009 23:28:19 +0100
Received: from 217.32.164.184 ([217.32.164.184]) by E03MVB3-UKBR.domain1.systemhost.net ([193.113.197.60]) via Exchange Front-End Server mail.bt.com ([193.113.197.28]) with Microsoft Exchange Server HTTP-DAV ; Mon, 22 Jun 2009 22:28:19 +0000
User-Agent: Microsoft-Entourage/12.17.0.090302
Date: Mon, 22 Jun 2009 23:28:16 +0100
From: Ben Niven-Jenkins <benjamin.niven-jenkins@bt.com>
To: Loa Andersson <loa@pi.nu>, <mpls-tp@ietf.org>, <mpls@ietf.org>, <pwe3@ietf.org>, <ccamp@ops.ietf.org>, <ahmpls-tp@lists.itu.int>
Message-ID: <C665C411.19A98%benjamin.niven-jenkins@bt.com>
Thread-Topic: working group last call on draft-ietf-mpls-tp-requirements-08.txt
Thread-Index: AcnziLx6UY80ux+oIUKmDZBfIJoyRA==
In-Reply-To: <4A117F44.1090503@pi.nu>
Mime-version: 1.0
Content-type: multipart/mixed; boundary="B_3328558098_51486309"
X-OriginalArrivalTime: 22 Jun 2009 22:28:19.0807 (UTC) FILETIME=[BEBF26F0:01C9F388]
Subject: Re: [PWE3] working group last call on draft-ietf-mpls-tp-requirements-08.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: <http://www.ietf.org/mail-archive/web/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, 22 Jun 2009 22:28:11 -0000

> This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

--B_3328558098_51486309
Content-type: text/plain;
	charset="US-ASCII"
Content-transfer-encoding: 7bit

Colleagues,

All comments received during this WG LC have been resolved and a new version
of the draft is available here:
http://www.ietf.org/internet-drafts/draft-ietf-mpls-tp-requirements-09.txt

I have attached an HTML document detailing the received WG LC comments and
the resolutions.

The document is also available here:
http://www.niven-jenkins.co.uk/MPLS-TP/MPLS-TPReqs2ndWGLC.htm

Ben


On 18/05/2009 16:31, "Loa Andersson" <loa@pi.nu> wrote:

> Working Group(s),
> 
> this is to start a two week working group last call on
> http://tools.ietf.org/id/draft-ietf-mpls-tp-requirements-08.txt
> 
> The document has been updated to address all comments received in the
> earlier working group last call and comments received from the
> ITU-T ad hoc team on MPLS-TP.
> 
> Please send your comments to the mpls-tp mailing list.
> 
> The working group last call ends on June 1st.
> 
> /Loa


--B_3328558098_51486309
Content-type: text/plain; name="MPLS-TPReqs2ndWGLC.htm";
 x-mac-creator="4D534945";
 x-mac-type="54455854"
Content-disposition: attachment;
	filename="MPLS-TPReqs2ndWGLC.htm"
Content-transfer-encoding: base64

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiCnhtbG5zOm89
InVybjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIKeG1sbnM6dz0idXJu
OnNjaGVtYXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIKeG1sbnM6bT0iaHR0cDovL3Nj
aGVtYXMubWljcm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIgp4bWxuczpjc3M9Imh0
dHA6Ly9tYWNWbWxTY2hlbWFVcmkiIHhtbG5zPSJodHRwOi8vd3d3LnczLm9yZy9UUi9SRUMt
aHRtbDQwIj4KCjxoZWFkPgo8bWV0YSBuYW1lPVRpdGxlIGNvbnRlbnQ9IiI+CjxtZXRhIG5h
bWU9S2V5d29yZHMgY29udGVudD0iIj4KPG1ldGEgaHR0cC1lcXVpdj1Db250ZW50LVR5cGUg
Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PW1hY2ludG9zaCI+CjxtZXRhIG5hbWU9UHJv
Z0lkIGNvbnRlbnQ9V29yZC5Eb2N1bWVudD4KPG1ldGEgbmFtZT1HZW5lcmF0b3IgY29udGVu
dD0iTWljcm9zb2Z0IFdvcmQgMjAwOCI+CjxtZXRhIG5hbWU9T3JpZ2luYXRvciBjb250ZW50
PSJNaWNyb3NvZnQgV29yZCAyMDA4Ij4KPGxpbmsgcmVsPUZpbGUtTGlzdApocmVmPSJNUExT
LVRQJTIwUmVxdWlyZW1lbnRzJTIwY29tbWVudCUyMHJlc29sdXRpb24lMjAwOCUyMHRvJTIw
MDlfMDFfZmlsZXMvZmlsZWxpc3QueG1sIj4KPCEtLVtpZiBndGUgbXNvIDldPjx4bWw+CiA8
bzpEb2N1bWVudFByb3BlcnRpZXM+CiAgPG86QXV0aG9yPkJlbmphbWluIE5pdmVuLUplbmtp
bnM8L286QXV0aG9yPgogIDxvOlRlbXBsYXRlPk5vcm1hbC5kb3RtPC9vOlRlbXBsYXRlPgog
IDxvOkxhc3RBdXRob3I+QmVuamFtaW4gTml2ZW4tSmVua2luczwvbzpMYXN0QXV0aG9yPgog
IDxvOlJldmlzaW9uPjI8L286UmV2aXNpb24+CiAgPG86VG90YWxUaW1lPjI0PC9vOlRvdGFs
VGltZT4KICA8bzpDcmVhdGVkPjIwMDktMDYtMjJUMTk6NDc6MDBaPC9vOkNyZWF0ZWQ+CiAg
PG86TGFzdFNhdmVkPjIwMDktMDYtMjJUMTk6NDc6MDBaPC9vOkxhc3RTYXZlZD4KICA8bzpQ
YWdlcz4yPC9vOlBhZ2VzPgogIDxvOldvcmRzPjc1NTwvbzpXb3Jkcz4KICA8bzpDaGFyYWN0
ZXJzPjQzMDc8L286Q2hhcmFjdGVycz4KICA8bzpMaW5lcz4zNTwvbzpMaW5lcz4KICA8bzpQ
YXJhZ3JhcGhzPjg8L286UGFyYWdyYXBocz4KICA8bzpDaGFyYWN0ZXJzV2l0aFNwYWNlcz41
Mjg5PC9vOkNoYXJhY3RlcnNXaXRoU3BhY2VzPgogIDxvOlZlcnNpb24+MTIuMDwvbzpWZXJz
aW9uPgogPC9vOkRvY3VtZW50UHJvcGVydGllcz4KIDxvOk9mZmljZURvY3VtZW50U2V0dGlu
Z3M+CiAgPG86QWxsb3dQTkcvPgogPC9vOk9mZmljZURvY3VtZW50U2V0dGluZ3M+CjwveG1s
PjwhW2VuZGlmXS0tPjwhLS1baWYgZ3RlIG1zbyA5XT48eG1sPgogPHc6V29yZERvY3VtZW50
PgogIDx3Olpvb20+MTI1PC93Olpvb20+CiAgPHc6U3BlbGxpbmdTdGF0ZT5DbGVhbjwvdzpT
cGVsbGluZ1N0YXRlPgogIDx3OkdyYW1tYXJTdGF0ZT5DbGVhbjwvdzpHcmFtbWFyU3RhdGU+
CiAgPHc6VHJhY2tNb3Zlcz5mYWxzZTwvdzpUcmFja01vdmVzPgogIDx3OlRyYWNrRm9ybWF0
dGluZy8+CiAgPHc6RGlzcGxheUhvcml6b250YWxEcmF3aW5nR3JpZEV2ZXJ5PjA8L3c6RGlz
cGxheUhvcml6b250YWxEcmF3aW5nR3JpZEV2ZXJ5PgogIDx3OkRpc3BsYXlWZXJ0aWNhbERy
YXdpbmdHcmlkRXZlcnk+MDwvdzpEaXNwbGF5VmVydGljYWxEcmF3aW5nR3JpZEV2ZXJ5Pgog
IDx3OlVzZU1hcmdpbnNGb3JEcmF3aW5nR3JpZE9yaWdpbi8+CiAgPHc6VmFsaWRhdGVBZ2Fp
bnN0U2NoZW1hcz5mYWxzZTwvdzpWYWxpZGF0ZUFnYWluc3RTY2hlbWFzPgogIDx3OlNhdmVJ
ZlhNTEludmFsaWQ+ZmFsc2U8L3c6U2F2ZUlmWE1MSW52YWxpZD4KICA8dzpJZ25vcmVNaXhl
ZENvbnRlbnQ+ZmFsc2U8L3c6SWdub3JlTWl4ZWRDb250ZW50PgogIDx3OkFsd2F5c1Nob3dQ
bGFjZWhvbGRlclRleHQ+ZmFsc2U8L3c6QWx3YXlzU2hvd1BsYWNlaG9sZGVyVGV4dD4KICA8
dzpEb05vdFVuZGVybGluZUludmFsaWRYTUwvPgogIDx3OkNvbXBhdGliaWxpdHk+CiAgIDx3
OkJyZWFrV3JhcHBlZFRhYmxlcy8+CiAgIDx3OlVzZU5vcm1hbFN0eWxlRm9yTGlzdC8+CiAg
IDx3OkRvbnRVc2VJbmRlbnRBc051bWJlcmluZ1RhYlN0b3AvPgogICA8dzpEb250R3Jvd0F1
dG9maXQvPgogICA8dzpGRUxpbmVCcmVhazExLz4KICAgPHc6V1cxMUluZGVudFJ1bGVzLz4K
ICAgPHc6RG9udEF1dG9maXRDb25zdHJhaW5lZFRhYmxlcy8+CiAgIDx3OkF1dG9maXRMaWtl
V1cxMS8+CiAgIDx3Okhhbmd1bFdpZHRoTGlrZVdXMTEvPgogIDwvdzpDb21wYXRpYmlsaXR5
PgogPC93OldvcmREb2N1bWVudD4KPC94bWw+PCFbZW5kaWZdLS0+PCEtLVtpZiBndGUgbXNv
IDldPjx4bWw+CiA8dzpMYXRlbnRTdHlsZXMgRGVmTG9ja2VkU3RhdGU9ImZhbHNlIiBMYXRl
bnRTdHlsZUNvdW50PSIyNzYiPgogPC93OkxhdGVudFN0eWxlcz4KPC94bWw+PCFbZW5kaWZd
LS0+CjxzdHlsZT4KPCEtLQogLyogRm9udCBEZWZpbml0aW9ucyAqLwpAZm9udC1mYWNlCgl7
Zm9udC1mYW1pbHk6Q2FtYnJpYTsKCXBhbm9zZS0xOjIgNCA1IDMgNSA0IDYgMyAyIDQ7Cglt
c28tZm9udC1jaGFyc2V0OjA7Cgltc28tZ2VuZXJpYy1mb250LWZhbWlseTphdXRvOwoJbXNv
LWZvbnQtcGl0Y2g6dmFyaWFibGU7Cgltc28tZm9udC1zaWduYXR1cmU6MyAwIDAgMCAxIDA7
fQogLyogU3R5bGUgRGVmaW5pdGlvbnMgKi8KcC5Nc29Ob3JtYWwsIGxpLk1zb05vcm1hbCwg
ZGl2Lk1zb05vcm1hbAoJe21zby1zdHlsZS1wYXJlbnQ6IiI7CgltYXJnaW4tdG9wOjBjbTsK
CW1hcmdpbi1yaWdodDowY207CgltYXJnaW4tYm90dG9tOjEwLjBwdDsKCW1hcmdpbi1sZWZ0
OjBjbTsKCW1zby1wYWdpbmF0aW9uOndpZG93LW9ycGhhbjsKCWZvbnQtc2l6ZToxMi4wcHQ7
Cglmb250LWZhbWlseToiVGltZXMgTmV3IFJvbWFuIjsKCW1zby1hc2NpaS1mb250LWZhbWls
eTpDYW1icmlhOwoJbXNvLWZhcmVhc3QtZm9udC1mYW1pbHk6Q2FtYnJpYTsKCW1zby1oYW5z
aS1mb250LWZhbWlseTpDYW1icmlhOwoJbXNvLWJpZGktZm9udC1mYW1pbHk6IlRpbWVzIE5l
dyBSb21hbiI7fQpzcGFuLlNwZWxsRQoJe21zby1zdHlsZS1uYW1lOiIiOwoJbXNvLXNwbC1l
Onllczt9CnNwYW4uR3JhbUUKCXttc28tc3R5bGUtbmFtZToiIjsKCW1zby1ncmFtLWU6eWVz
O30KQHBhZ2UgU2VjdGlvbjEKCXtzaXplOjYxMi4wcHQgNzkyLjBwdDsKCW1hcmdpbjo3Mi4w
cHQgMTIyLjk1cHQgNzIuMHB0IDkwLjBwdDsKCW1zby1oZWFkZXItbWFyZ2luOjM1LjRwdDsK
CW1zby1mb290ZXItbWFyZ2luOjM1LjRwdDsKCW1zby1wYXBlci1zb3VyY2U6MDt9CmRpdi5T
ZWN0aW9uMQoJe3BhZ2U6U2VjdGlvbjE7fQotLT4KPC9zdHlsZT4KPCEtLVtpZiBndGUgbXNv
IDEwXT4KPHN0eWxlPgogLyogU3R5bGUgRGVmaW5pdGlvbnMgKi8KdGFibGUuTXNvTm9ybWFs
VGFibGUKCXttc28tc3R5bGUtbmFtZToiVGFibGUgTm9ybWFsIjsKCW1zby10c3R5bGUtcm93
YmFuZC1zaXplOjA7Cgltc28tdHN0eWxlLWNvbGJhbmQtc2l6ZTowOwoJbXNvLXN0eWxlLW5v
c2hvdzp5ZXM7Cgltc28tc3R5bGUtcGFyZW50OiIiOwoJbXNvLXBhZGRpbmctYWx0OjBjbSA1
LjRwdCAwY20gNS40cHQ7Cgltc28tcGFyYS1tYXJnaW46MGNtOwoJbXNvLXBhcmEtbWFyZ2lu
LWJvdHRvbTouMDAwMXB0OwoJbXNvLXBhZ2luYXRpb246d2lkb3ctb3JwaGFuOwoJZm9udC1z
aXplOjEwLjBwdDsKCWZvbnQtZmFtaWx5OiJUaW1lcyBOZXcgUm9tYW4iOwoJbXNvLWFzY2lp
LWZvbnQtZmFtaWx5OkNhbWJyaWE7Cgltc28taGFuc2ktZm9udC1mYW1pbHk6Q2FtYnJpYTt9
Cjwvc3R5bGU+CjwhW2VuZGlmXS0tPjwhLS1baWYgZ3RlIG1zbyA5XT48eG1sPgogPG86c2hh
cGVkZWZhdWx0cyB2OmV4dD0iZWRpdCIgc3BpZG1heD0iMjA1MCIvPgo8L3htbD48IVtlbmRp
Zl0tLT48IS0tW2lmIGd0ZSBtc28gOV0+PHhtbD4KIDxvOnNoYXBlbGF5b3V0IHY6ZXh0PSJl
ZGl0Ij4KICA8bzppZG1hcCB2OmV4dD0iZWRpdCIgZGF0YT0iMSIvPgogPC9vOnNoYXBlbGF5
b3V0PjwveG1sPjwhW2VuZGlmXS0tPgo8L2hlYWQ+Cgo8Ym9keSBsYW5nPUVOLUdCIHN0eWxl
PSd0YWItaW50ZXJ2YWw6MzYuMHB0Jz4KCjxkaXYgY2xhc3M9U2VjdGlvbjE+Cgo8cCBjbGFz
cz1Nc29Ob3JtYWwgYWxpZ249Y2VudGVyIHN0eWxlPSd0ZXh0LWFsaWduOmNlbnRlcic+PGIg
c3R5bGU9J21zby1iaWRpLWZvbnQtd2VpZ2h0Ogpub3JtYWwnPkNvbW1lbnQgcmVzb2x1dGlv
bnMgZnJvbSAyPHN1cD5uZDwvc3VwPiBXRyBMYXN0IENhbGwgb24gTVBMUy1UUApSZXF1aXJl
bWVudHMgKGRyYWZ0LWlldGYtbXBscy10cC1yZXF1aXJlbWVudHMtMDgpPG86cD48L286cD48
L2I+PC9wPgoKPHAgY2xhc3M9TXNvTm9ybWFsIHN0eWxlPSd0ZXh0LWFsaWduOmp1c3RpZnkn
PjxiIHN0eWxlPSdtc28tYmlkaS1mb250LXdlaWdodDoKbm9ybWFsJz48bzpwPiZuYnNwOzwv
bzpwPjwvYj48L3A+Cgo8cCBjbGFzcz1Nc29Ob3JtYWwgc3R5bGU9J3RleHQtYWxpZ246anVz
dGlmeSc+QWxsIGNoYW5nZXMgbm90ZWQgYmVsb3cgYXJlCnJlZmxlY3RlZCBpbiB2ZXJzaW9u
IC0wOSB0aGF0IGlzIG5vdyBhdmFpbGFibGUgaW4gdGhlIEktRCByZXBvc2l0b3J5LjwvcD4K
CjxwIGNsYXNzPU1zb05vcm1hbCBzdHlsZT0ndGV4dC1hbGlnbjpqdXN0aWZ5Jz48YiBzdHls
ZT0nbXNvLWJpZGktZm9udC13ZWlnaHQ6Cm5vcm1hbCc+PG86cD4mbmJzcDs8L286cD48L2I+
PC9wPgoKPHAgY2xhc3M9TXNvTm9ybWFsIHN0eWxlPSd0ZXh0LWFsaWduOmp1c3RpZnknPjxi
IHN0eWxlPSdtc28tYmlkaS1mb250LXdlaWdodDoKbm9ybWFsJz5LZXk8bzpwPjwvbzpwPjwv
Yj48L3A+Cgo8cCBjbGFzcz1Nc29Ob3JtYWwgc3R5bGU9J3RleHQtYWxpZ246anVzdGlmeSc+
T3JpZ2luYWwgY29tbWVudDwvcD4KCjxwIGNsYXNzPU1zb05vcm1hbCBzdHlsZT0ndGV4dC1h
bGlnbjpqdXN0aWZ5Jz48c3BhbiBzdHlsZT0nY29sb3I6Ymx1ZSc+U2Vjb25kYXJ5CmNvbW1l
bnRlcjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4KCjxwIGNsYXNzPU1zb05vcm1hbCBzdHlsZT0n
dGV4dC1hbGlnbjpqdXN0aWZ5Jz48c3BhbiBjbGFzcz1TcGVsbEU+PHNwYW4Kc3R5bGU9J2Nv
bG9yOmdyZWVuJz5CUE7Vczwvc3Bhbj48L3NwYW4+PHNwYW4gc3R5bGU9J2NvbG9yOmdyZWVu
Jz4gcmVzcG9uc2U8bzpwPjwvbzpwPjwvc3Bhbj48L3A+Cgo8cCBjbGFzcz1Nc29Ob3JtYWwg
c3R5bGU9J3RleHQtYWxpZ246anVzdGlmeSc+PGIgc3R5bGU9J21zby1iaWRpLWZvbnQtd2Vp
Z2h0Ogpub3JtYWwnPjxvOnA+Jm5ic3A7PC9vOnA+PC9iPjwvcD4KCjxwIGNsYXNzPU1zb05v
cm1hbCBzdHlsZT0ndGV4dC1hbGlnbjpqdXN0aWZ5Jz48YiBzdHlsZT0nbXNvLWJpZGktZm9u
dC13ZWlnaHQ6Cm5vcm1hbCc+SVRVLVQgTGlhaXNvbiBmcm9tIFE5LCAxMCwgMTIsIDE0IFNH
MTU8bzpwPjwvbzpwPjwvYj48L3A+Cgo8cCBjbGFzcz1Nc29Ob3JtYWwgc3R5bGU9J3RleHQt
YWxpZ246anVzdGlmeSc+MSkgUmVxdWlyZW1lbnQgNTk6IEl0ZW0gYyBzaG91bGQKYmUgbW92
ZWQgZnJvbSByZXF1aXJlbWVudCA1OSB0byBhIHNlcGFyYXRlIHJlcXVpcmVtZW50IHNpbmNl
IGl0IGlzIG5vdCBwYXJ0IG9mCnRoZSBTTEE8L3A+Cgo8cCBjbGFzcz1Nc29Ob3JtYWwgc3R5
bGU9J3RleHQtYWxpZ246anVzdGlmeSc+PHNwYW4gc3R5bGU9J2NvbG9yOmdyZWVuJz5JIGhh
dmUKbW92ZWQgcmVxdWlyZW1lbnQgNTkgQyB0byBiZSBhIDxzcGFuIGNsYXNzPUdyYW1FPnN0
YW5kIGFsb25lPC9zcGFuPiByZXF1aXJlbWVudAppbiB0aGUgc2FtZSBzZWN0aW9uIChSZWNv
dmVyeSByZXF1aXJlbWVudHMpLjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4KCjxwIGNsYXNzPU1z
b05vcm1hbCBzdHlsZT0ndGV4dC1hbGlnbjpqdXN0aWZ5Jz4yKSBSZXF1aXJlbWVudCA3MDo8
c3BhbgpzdHlsZT0ibXNvLXNwYWNlcnVuOiB5ZXMiPiZuYnNwOyA8L3NwYW4+U2hvdWxkIGJl
IG1vdmVkIHRvIHRoZSByZXN0b3JhdGlvbgpzZWN0aW9uICgyLjguMikuIEN1cnJlbnRseSwg
aXQgaXMgdW5kZXIgdGhlIHByb3RlY3Rpb24gc2VjdGlvbi48L3A+Cgo8cCBjbGFzcz1Nc29O
b3JtYWwgc3R5bGU9J3RleHQtYWxpZ246anVzdGlmeSc+PHNwYW4gc3R5bGU9J2NvbG9yOmdy
ZWVuJz5JIGhhdmUKbW92ZWQgcmVxdWlyZW1lbnQgNzAgdG8gdGhlIHJlc3RvcmF0aW9uIHNl
Y3Rpb24gKDIuOC4yKS4gSSBhbHNvIG1vdmVkIHRoZQpwcm90ZWN0aW9uIHJlcXVpcmVtZW50
IHJlbGF0ZWQgdG8gcmV2ZXJzaW9uIHRvIHRoZSBwcm90ZWN0aW9uIHNlY3Rpb24gKDIuOC4x
LjEpCmFuZCBkZWxldGVkIHRoZSByZXZlcnNpb24gc2VjdGlvbiBhcyBpdCBub3cgY29udGFp
bnMgbm8gcmVxdWlyZW1lbnRzLjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4KCjxwIGNsYXNzPU1z
b05vcm1hbCBzdHlsZT0ndGV4dC1hbGlnbjpqdXN0aWZ5Jz4zKSBSZXF1aXJlbWVudCA2NiBE
OiBUaGUgdGVybQomcXVvdDtiYWNrdHJhY2tpbmcmcXVvdDsgc2hvdWxkIGJlIDxzcGFuIGNs
YXNzPUdyYW1FPmRlZmluZWQsPC9zcGFuPiB0aGlzCnNob3VsZCBiZSBpbmNsdWRlZCBpbiB0
aGUgPHNwYW4gY2xhc3M9U3BlbGxFPnJvc2V0dGE8L3NwYW4+IGRyYWZ0LiA8L3A+Cgo8cCBj
bGFzcz1Nc29Ob3JtYWwgc3R5bGU9J3RleHQtYWxpZ246anVzdGlmeSc+PHNwYW4gc3R5bGU9
J2NvbG9yOmdyZWVuJz5SZXdvcmRlZApyZXF1aXJlbWVudCA2NiBEIHRvIHRoZSBmb2xsb3dp
bmcgYXMgcGVyIFN0ZXdhcnQgQnJ5YW501XMgc3VnZ2VzdGlvbiB0byB0aGUKTVBMUy1UUCBJ
VFUgYW5kIElFVEYgbWFpbGluZyBsaXN0czo8bzpwPjwvbzpwPjwvc3Bhbj48L3A+Cgo8cCBj
bGFzcz1Nc29Ob3JtYWwgc3R5bGU9J3RleHQtYWxpZ246anVzdGlmeSc+PHNwYW4gc3R5bGU9
J2NvbG9yOmdyZWVuJz5UaGUgPHNwYW4KY2xhc3M9R3JhbUU+YWN0aW9uIG9mIHByb3RlY3Rp
b24gc3dpdGNoaW5nIE1VU1QgTk9UIGNhdXNlPC9zcGFuPiB0aGUgdXNlciBkYXRhCnRvIGVu
dGVyIGFuIHVuY29udHJvbGxlZCBsb29wLiBUaGUgcHJvdGVjdGlvbiBzd2l0Y2hpbmcgc3lz
dGVtIE1BWSBjYXVzZQp0cmFmZmljIHRvIHBhc3Mgb3ZlciBhIGdpdmVuIGxpbmsgbW9yZSB0
aGFuIG9uY2UsIGJ1dCBpdCBtdXN0IGRvIHNvIGluIGEKY29udHJvbGxlZCB3YXkgc3VjaCB0
aGF0IHVuY29udHJvbGxlZCBsb29wcyBkbyBub3QgZm9ybS48bzpwPjwvbzpwPjwvc3Bhbj48
L3A+Cgo8cCBjbGFzcz1Nc29Ob3JtYWwgc3R5bGU9J3RleHQtYWxpZ246anVzdGlmeSc+NCkg
UmluZyBwcm90ZWN0aW9uIHNlY3Rpb24gPHNwYW4KY2xhc3M9R3JhbUU+Mi44LjYuMSA6PC9z
cGFuPiA8L3A+Cgo8cCBjbGFzcz1Nc29Ob3JtYWwgc3R5bGU9J3RleHQtYWxpZ246anVzdGlm
eSc+VGhlIHBhcmFncmFwaCBiZWxvdyByZXF1aXJlbWVudAplLCByZXBsYWNlIHRoZSB3b3Jk
cyBpbiAmcXVvdDt0aGlzIHNlY3Rpb24mcXVvdDsgd2l0aCDSc2VjdGlvbiAyLjguNi4xJnF1
b3Q7CmFuZCByZXBsYWNlIHRoZSB3b3JkcyAmcXVvdDtleHByZXNzZWQgYWJvdmUmcXVvdDsg
YnkgJnF1b3Q7cmVxdWlyZW1lbnRzCmV4cHJlc3NlZCBpbiBzZWN0aW9ucyAyLjggdXAgdG8g
c2VjdGlvbiAyLjguNi4xJnF1b3Q7PC9wPgoKPHAgY2xhc3M9TXNvTm9ybWFsIHN0eWxlPSd0
ZXh0LWFsaWduOmp1c3RpZnknPjxzcGFuIHN0eWxlPSdjb2xvcjpncmVlbic+SSBoYXZlCm1h
ZGUgdGhlIGNoYW5nZXMgeW91IHN1Z2dlc3RlZCwgdGhlIHBhcmFncmFwaCBub3cgcmVhZHM6
PG86cD48L286cD48L3NwYW4+PC9wPgoKPHAgY2xhc3M9TXNvTm9ybWFsIHN0eWxlPSdtYXJn
aW4tbGVmdDoxLjBjbTt0ZXh0LWFsaWduOmp1c3RpZnknPjxzcGFuCnN0eWxlPSdjb2xvcjpn
cmVlbic+SXQgbWF5IGJlIG9ic2VydmVkIHRoYXQgdGhlIHJlcXVpcmVtZW50cyBpbiBTZWN0
aW9uIDIuOC42LjEKYXJlIGZ1bGx5IGNvbXBhdGlibGUgd2l0aCB0aGUgZ2VuZXJpYyByZXF1
aXJlbWVudHMgZXhwcmVzc2VkIGluIFNlY3Rpb24gMi44CnRocm91Z2ggU2VjdGlvbiAyLjgu
NiBpbmNsdXNpdmUsIGFuZCB0aGF0IG5vIHJlcXVpcmVtZW50cyB0aGF0IGFyZSBzcGVjaWZp
YyB0bwpyaW5nIHRvcG9sb2dpZXMgaGF2ZSBiZWVuIGlkZW50aWZpZWQuPG86cD48L286cD48
L3NwYW4+PC9wPgoKPHAgY2xhc3M9TXNvTm9ybWFsIHN0eWxlPSd0ZXh0LWFsaWduOmp1c3Rp
ZnknPjUpIFJlcXVpcmVtZW50IDEwN0I6IFJlcGxhY2UgdGhlCmN1cnJlbnQgdGV4dCB3aXRo
IGZvbGxvd2luZzo8L3A+Cgo8cCBjbGFzcz1Nc29Ob3JtYWwgc3R5bGU9J3RleHQtYWxpZ246
anVzdGlmeSc+SXQgU0hPVUxEIHByb3RlY3QgYWdhaW5zdAptdWx0aXBsZSBmYWlsdXJlczwv
cD4KCjxwIGNsYXNzPU1zb05vcm1hbCBzdHlsZT0ndGV4dC1hbGlnbjpqdXN0aWZ5Jz48c3Bh
biBzdHlsZT0nY29sb3I6Z3JlZW4nPkkgaGF2ZQpyZXBsYWNlZCB0aGUgY3VycmVudCB0ZXh0
IHdpdGggeW91ciBzdWdnZXN0ZWQgdGV4dC48bzpwPjwvbzpwPjwvc3Bhbj48L3A+Cgo8cCBj
bGFzcz1Nc29Ob3JtYWwgc3R5bGU9J3RleHQtYWxpZ246anVzdGlmeSc+PG86cD4mbmJzcDs8
L286cD48L3A+Cgo8cCBjbGFzcz1Nc29Ob3JtYWwgc3R5bGU9J3RleHQtYWxpZ246anVzdGlm
eSc+PGIgc3R5bGU9J21zby1iaWRpLWZvbnQtd2VpZ2h0Ogpub3JtYWwnPlByaXZhdGUgY29t
bWVudHMgZnJvbSA8c3BhbiBjbGFzcz1TcGVsbEU+SXRhbG88L3NwYW4+IDxzcGFuCmNsYXNz
PVNwZWxsRT5CdXNpPC9zcGFuPjo8bzpwPjwvbzpwPjwvYj48L3A+Cgo8cCBjbGFzcz1Nc29O
b3JtYWwgc3R5bGU9J3RleHQtYWxpZ246anVzdGlmeSc+MSkgSW4gdGhlIGxhc3QgbGluZSBv
ZiBzZWN0aW9uIDEKKGp1c3QgYmVmb3JlIHRoZSBoZWFkaW5nIG9mIHNlY3Rpb24gMS4xKSwg
dGhlcmUgaXMgc3RpbGwgdGhlIHRleHQgJnF1b3Q7Y29udHJvbApwbGFuZSBmb3IgZHluYW1p
YyBjb25maWd1cmF0aW9uJnF1b3Q7PC9wPgoKPHAgY2xhc3M9TXNvTm9ybWFsIHN0eWxlPSd0
ZXh0LWFsaWduOmp1c3RpZnknPk15IHVuZGVyc3RhbmRpbmcgZnJvbSB0aGUgTUVBRApjYWxs
IHdhcyB0aGF0LCB0byBhdm9pZCBjb25mdXNpb24gcmVnYXJkaW5nIHdoYXQgZG8gd2UgbWVh
biBieSBjb250cm9sIHBsYW5lIGluCnRoaXMgZG9jdW1lbnQsIHdlIGhhdmUgYWdyZWUgdG8g
YWRkIHRoZSBkZWZpbml0aW9uIG9mIGNvbnRyb2wgcGxhbmUgKHRoYXQgaXMKZmluZSkgYW5k
IHRvIHJlbW92ZSA8c3BhbiBjbGFzcz1TcGVsbEU+cmVtb3ZlPC9zcGFuPiAmcXVvdDtmb3Ig
ZHluYW1pYyBjb25maWd1cmF0aW9uJnF1b3Q7CmluIHRoZSB0ZXh0LjwvcD4KCjxwIGNsYXNz
PU1zb05vcm1hbCBzdHlsZT0ndGV4dC1hbGlnbjpqdXN0aWZ5Jz5IYXZlIEkgbWlzc2VkIHNv
bWV0aGluZz88L3A+Cgo8cCBjbGFzcz1Nc29Ob3JtYWwgc3R5bGU9J3RleHQtYWxpZ246anVz
dGlmeSc+PHNwYW4gc3R5bGU9J2NvbG9yOmdyZWVuJz5Oby4gSQpyZW1vdmVkIHJlZmVyZW5j
ZSB0byAmcXVvdDtjb250cm9sIHBsYW5lIGZvciBkeW5hbWljIGNvbmZpZ3VyYXRpb24mcXVv
dDsgZnJvbQpvbmUgb2YgdGhlIHJlcXVpcmVtZW50cyBidXQgb3Zlcmxvb2tlZCBpdCBpbiBz
ZWN0aW9uIDEuIEkgaGF2ZSByZW1vdmVkIGl0IGZyb20Kc2VjdGlvbiAxIGFzIHdlbGwuPG86
cD48L286cD48L3NwYW4+PC9wPgoKPHAgY2xhc3M9TXNvTm9ybWFsIHN0eWxlPSd0ZXh0LWFs
aWduOmp1c3RpZnknPjIpIEl0IGlzIG15IHVuZGVyc3RhbmRpbmcgdGhhdApyZXF1aXJlbWVu
dHMgOS0xMiBoYXZlIGJlZW4gbW92ZWQgZnJvbSBzZWN0aW9uIDIuMyB0byBzZWN0aW9uIDIu
MS48L3A+Cgo8cCBjbGFzcz1Nc29Ob3JtYWwgc3R5bGU9J3RleHQtYWxpZ246anVzdGlmeSc+
SSBkbyBub3QgcmVtZW1iZXIgdGhpcyBkaXNjdXNzaW9uCmJ1dCBJIGFtIGZpbmUgd2l0aCB0
aGlzIGNoYW5nZS48L3A+Cgo8cCBjbGFzcz1Nc29Ob3JtYWwgc3R5bGU9J3RleHQtYWxpZ246
anVzdGlmeSc+SG93ZXZlciwgZm9yIGNvbnNpc3RlbmN5LCBJIHRoaW5rCnRoYXQgYWxzbyBy
ZXF1aXJlbWVudCA0MCBzaG91bGQgYmUgbW92ZWQgZnJvbSAyLjMgdG8gMi4xLjwvcD4KCjxw
IGNsYXNzPU1zb05vcm1hbCBzdHlsZT0ndGV4dC1hbGlnbjpqdXN0aWZ5Jz48c3BhbiBzdHls
ZT0nY29sb3I6Z3JlZW4nPlRoZXJlCndhcyBzb21lIGRpc2N1c3Npb24gb2YgaXQgaW4gdGhl
IGNvbnRleHQgb2YgdGhlIHdvcmRpbmcgb24gdGhlIG1haWxpbmcgbGlzdCBhbmQKSSBqdWRn
ZWQgY29uc2Vuc3VzIG9mIHRoYXQgZGlzY3Vzc2lvbiB0byBhbHNvIGJlIHRvIG1vdmUgdGhl
bSB0byBzZWN0aW9uIDIuMS4gSQpoYXZlIG1vdmVkIHJlcXVpcmVtZW50IDQwIHRvIHNlY3Rp
b24gMi4xLjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4KCjxwIGNsYXNzPU1zb05vcm1hbCBzdHls
ZT0ndGV4dC1hbGlnbjpqdXN0aWZ5Jz4zKSBNeSB1bmRlcnN0YW5kaW5nIGZyb20gdGhlIE1F
QUQKY2FsbCB3ZSBhZ3JlZWQgdGhhdCB0aGF0IHJlcXVpcmVtZW50IDQ3IHNob3VsZCBiZSBt
b3ZlZCBmcm9tIHNlY3Rpb24gMi40IHRvCnNlY3Rpb24gMi4zIGFzIGl0IGlzIGEgZGF0YSBw
bGFuZSBhbmQgbm90IGEgY29udHJvbCBwbGFuZSByZXF1aXJlbWVudC48L3A+Cgo8cCBjbGFz
cz1Nc29Ob3JtYWwgc3R5bGU9J3RleHQtYWxpZ246anVzdGlmeSc+SGF2ZSBJIG1pc3NlZCBz
b21ldGhpbmc/PC9wPgoKPHAgY2xhc3M9TXNvTm9ybWFsIHN0eWxlPSd0ZXh0LWFsaWduOmp1
c3RpZnknPjxzcGFuIHN0eWxlPSdjb2xvcjpncmVlbic+SSBtdXN0CmhhdmUgbWlzc2VkIHRo
YXQsIEkgaGF2ZSBtb3ZlZCByZXF1aXJlbWVudCA0NyB0byBzZWN0aW9uIDIuMy48bzpwPjwv
bzpwPjwvc3Bhbj48L3A+Cgo8cCBjbGFzcz1Nc29Ob3JtYWwgc3R5bGU9J3RleHQtYWxpZ246
anVzdGlmeSc+PHNwYW4gc3R5bGU9J2NvbG9yOmdyZWVuJz48bzpwPiZuYnNwOzwvbzpwPjwv
c3Bhbj48L3A+Cgo8cCBjbGFzcz1Nc29Ob3JtYWwgc3R5bGU9J3RleHQtYWxpZ246anVzdGlm
eSc+PGIgc3R5bGU9J21zby1iaWRpLWZvbnQtd2VpZ2h0Ogpub3JtYWwnPkNvbW1lbnRzIG9u
IE1QTFMtVFAgbGlzdCBjb252ZXJzYXRpb24gYmV0d2VlbiA8c3BhbiBjbGFzcz1TcGVsbEU+
WWFhY292PC9zcGFuPgpXZWluZ2FydGVuICZhbXA7IDxzcGFuIHN0eWxlPSdjb2xvcjpibHVl
Jz5BZHJpYW4gPHNwYW4gY2xhc3M9U3BlbGxFPkZhcnJlbDwvc3Bhbj48L3NwYW4+PG86cD48
L286cD48L2I+PC9wPgoKPHAgY2xhc3M9TXNvTm9ybWFsIHN0eWxlPSd0ZXh0LWFsaWduOmp1
c3RpZnknPjEuIDxzcGFuIGNsYXNzPVNwZWxsRT5SZXE8L3NwYW4+CjI3LUM6IE1QTFMtVFAg
TVVTVCBzdXBwb3J0IHJpbmdzIG9mIGF0IGxlYXN0IDE2IG5vZGVzLi4uTVBMUy1UUCBTSE9V
TEQgc3VwcG9ydApyaW5ncyB3aXRoIG1vcmUgdGhhbiAxNiBub2Rlcy48L3A+Cgo8cCBjbGFz
cz1Nc29Ob3JtYWwgc3R5bGU9J3RleHQtYWxpZ246anVzdGlmeSc+U28gaXMgaXQgYSBNVVNU
IG9yIGEgU0hPVUxEPzxzcGFuCnN0eWxlPSJtc28tc3BhY2VydW46IHllcyI+Jm5ic3A7IDwv
c3Bhbj5Jc24ndCAmcXVvdDthdCBsZWFzdCAxNiZxdW90OyBhbmQKJnF1b3Q7bW9yZSB0aGFu
IDE2JnF1b3Q7IGFsbW9zdCBlcXVpdmFsZW50IChleGNlcHQgZm9yIGV4YWN0bHkgMTYpPzwv
cD4KCjxwIGNsYXNzPU1zb05vcm1hbCBzdHlsZT0ndGV4dC1hbGlnbjpqdXN0aWZ5Jz48c3Bh
biBzdHlsZT0nY29sb3I6Ymx1ZSc+UmlnaHQgPG86cD48L286cD48L3NwYW4+
PC9wPgoKPHAg
Y2xhc3M9TXNvTm9ybWFsIHN0eWxlPSd0ZXh0LWFsaWduOmp1c3RpZnknPjxzcGFuIHN0eWxl
PSdjb2xvcjpibHVlJz5NVVNUIHN1cHBvcnQKMC0xNiA8bzpwPjwvbzpwPjwvc3Bhbj48L3A+
Cgo8cCBjbGFzcz1Nc29Ob3JtYWwgc3R5bGU9J3RleHQtYWxpZ246anVzdGlmeSc+PHNwYW4g
c3R5bGU9J2NvbG9yOmJsdWUnPlNIT1VMRApzdXBwb3J0IDE3Li4uPG86cD48L286cD48L3Nw
YW4+PC9wPgoKPHAgY2xhc3M9TXNvTm9ybWFsIHN0eWxlPSd0ZXh0LWFsaWduOmp1c3RpZnkn
PjxzcGFuIHN0eWxlPSdjb2xvcjpibHVlJz5UaGF0IGlzCndoYXQgdGhlIHRleHQgc2F5cy48
bzpwPjwvbzpwPjwvc3Bhbj48L3A+Cgo8cCBjbGFzcz1Nc29Ob3JtYWwgc3R5bGU9J3RleHQt
YWxpZ246anVzdGlmeSc+PHNwYW4gc3R5bGU9J2NvbG9yOmJsdWUnPsk8bzpwPjwvbzpwPjwv
c3Bhbj48L3A+Cgo8cCBjbGFzcz1Nc29Ob3JtYWwgc3R5bGU9J3RleHQtYWxpZ246anVzdGlm
eSc+PHNwYW4gc3R5bGU9J2NvbG9yOmJsdWUnPkkgdGhpbmsKdGhpcyBpcyBnb29kIG1hdGVy
aWFsIGZvciBkaXNjdXNzaW9uIGluIFNvcGhpYSA8c3BhbiBjbGFzcz1TcGVsbEU+QW50aXBv
bGlzPC9zcGFuPi48YnI+CkFGQUlLLCB0aGU8YnI+CnByZWNpc2UKd29yZGluZyBjYW1lIGZy
b20gdGhlIElUVS1UIG1lZXRpbmcgaW4gR2VuZXZhLjxicj4KV2Ugc2hvdWxkLCB0aGVyZWZv
cmUsIGdldApzaWdub2ZmIGZyb20gSVRVLVQgZm9sayB3aGVuIHdlIGNoYW5nZSBpdC48bzpw
PjwvbzpwPjwvc3Bhbj48L3A+Cgo8cCBjbGFzcz1Nc29Ob3JtYWwgc3R5bGU9J3RleHQtYWxp
Z246anVzdGlmeSc+PHNwYW4gc3R5bGU9J2NvbG9yOmdyZWVuJz5Db25zZW5zdXMKaW4gU29w
aGlhIHdhcyB0aGF0IElUVS1UIGRpZCBub3QgcmVxdWlyZSBhbnkgY2hhbmdlcyB0byB0aGUg
dGV4dC48bzpwPjwvbzpwPjwvc3Bhbj48L3A+Cgo8cCBjbGFzcz1Nc29Ob3JtYWwgc3R5bGU9
J3RleHQtYWxpZ246anVzdGlmeSc+MikgSW4gPHNwYW4gY2xhc3M9U3BlbGxFPlJlcTwvc3Bh
bj4KMTAwICZhbXA7IDEwMiAtIFdoYXQgaXMgdGhlIGRpZmZlcmVuY2UgYmV0d2VlbiAmcXVv
dDtSZWNvdmVyeSBtZWNoYW5pc21zJnF1b3Q7CmFuZCAmcXVvdDtSZWNvdmVyeSB0ZWNobmlx
dWVzJnF1b3Q7PyBXaHkgaXMgdGhlIGZpcnN0IGEgTVVTVCBhbmQgdGhlIHNlY29uZCBhClNI
T1VMRD88L3A+Cgo8cCBjbGFzcz1Nc29Ob3JtYWwgc3R5bGU9J3RleHQtYWxpZ246anVzdGlm
eSc+PHNwYW4gc3R5bGU9J2NvbG9yOmJsdWUnPkdvb2QKY2F0Y2guPG86cD48L286cD48L3Nw
YW4+PC9wPgoKPHAgY2xhc3M9TXNvTm9ybWFsIHN0eWxlPSd0ZXh0LWFsaWduOmp1c3RpZnkn
PjxzcGFuIHN0eWxlPSdjb2xvcjpibHVlJz5Pbmx5IG9uZQpvZiB0aGUgdHdvIHJlcXVpcmVt
ZW50cyBzaG91bGQgcmVtYWluLjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4KCjxwIGNsYXNzPU1z
b05vcm1hbCBzdHlsZT0ndGV4dC1hbGlnbjpqdXN0aWZ5Jz48c3BhbiBjbGFzcz1HcmFtRT48
c3BhbgpzdHlsZT0nY29sb3I6Ymx1ZSc+QnV0IHdoaWNoPzwvc3Bhbj48L3NwYW4+PHNwYW4g
c3R5bGU9J2NvbG9yOmJsdWUnPjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4KCjxwIGNsYXNzPU1z
b05vcm1hbCBzdHlsZT0ndGV4dC1hbGlnbjpqdXN0aWZ5Jz48c3BhbiBzdHlsZT0nY29sb3I6
Z3JlZW4nPkkKcmVtb3ZlZCBSZXF1aXJlbWVudCAxMDAuPG86cD48L286cD48L3NwYW4+PC9w
PgoKPHAgY2xhc3M9TXNvTm9ybWFsIHN0eWxlPSd0ZXh0LWFsaWduOmp1c3RpZnknPjMpIEZp
bmFsbHksIGp1c3QgYSBsaXR0bGUKc3BlbGxpbmcgbm90ZTogaW4gPHNwYW4gY2xhc3M9U3Bl
bGxFPlJlcTwvc3Bhbj4gMzItQTogY2hhbmdlICZxdW90O2JlbGxvdyZxdW90Owp0byAmcXVv
dDtiZWxvdyZxdW90Oy48L3A+Cgo8cCBjbGFzcz1Nc29Ob3JtYWwgc3R5bGU9J3RleHQtYWxp
Z246anVzdGlmeSc+PHNwYW4gc3R5bGU9J2NvbG9yOmdyZWVuJz5Db3JyZWN0ZWQuPG86cD48
L286cD48L3NwYW4+PC9wPgoKPHAgY2xhc3M9TXNvTm9ybWFsIHN0eWxlPSd0ZXh0LWFsaWdu
Omp1c3RpZnknPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPgoKPHAgY2xhc3M9TXNvTm9ybWFsIHN0
eWxlPSd0ZXh0LWFsaWduOmp1c3RpZnknPjxiIHN0eWxlPSdtc28tYmlkaS1mb250LXdlaWdo
dDoKbm9ybWFsJz5Db21tZW50IGZyb20gPHNwYW4gY2xhc3M9U3BlbGxFPkppYTwvc3Bhbj4g
SGU8bzpwPjwvbzpwPjwvYj48L3A+Cgo8cCBjbGFzcz1Nc29Ob3JtYWwgc3R5bGU9J3RleHQt
YWxpZ246anVzdGlmeSc+T25lIG1pbm9yIGNvbW1lbnQgYWJvdXQKUmVxdWlyZW1lbnQgMjE8
L3A+Cgo8cCBjbGFzcz1Nc29Ob3JtYWwgc3R5bGU9J3RleHQtYWxpZ246anVzdGlmeSc+JnF1
b3Q7PHNwYW4gY2xhc3M9R3JhbUU+MjE8c3BhbgpzdHlsZT0ibXNvLXNwYWNlcnVuOiB5ZXMi
PiZuYnNwOyA8L3NwYW4+QTwvc3Bhbj4gc29sdXRpb24gTVVTVCBiZSBkZWZpbmVkIHRvCnN1
cHBvcnQgZHluYW1pYyBwcm92aXNpb25pbmcgYW5kPHNwYW4gc3R5bGU9Im1zby1zcGFjZXJ1
bjoKeWVzIj4mbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsgPC9z
cGFuPnJlc3RvcmF0aW9uIG9mIE1QTFMtVFAKdHJhbnNwb3J0IHBhdGhzIHZpYSBhIGNvbnRy
b2wgcGxhbmUuJnF1b3Q7PC9wPgoKPHAgY2xhc3M9TXNvTm9ybWFsIHN0eWxlPSd0ZXh0LWFs
aWduOmp1c3RpZnknPkknbSB3b25kZXJpbmcgd2hldGhlciB0aGlzIGlzCmJldHRlciB0byBi
ZSBpbmNsdWRlZCBpbiBTZWN0aW9uIDIuNCwgd2hpY2ggZm9jdXNlcyBvbiBjb250cm9sIHBs
YW5lCnJlcXVpcmVtZW50cywgcmF0aGVyIHRoYW4gaW4gU2VjdGlvbiAyLjEoR2VuZXJhbCBy
ZXF1aXJlbWVudHMpLjwvcD4KCjxwIGNsYXNzPU1zb05vcm1hbCBzdHlsZT0ndGV4dC1hbGln
bjpqdXN0aWZ5Jz48c3BhbiBzdHlsZT0nY29sb3I6Z3JlZW4nPkFncmVlbWVudApvZmZsaW5l
IHRoZSBNUExTLVRQIGxpc3QgdG8gbGVhdmUgcmVxdWlyZW1lbnQgMjEgaW4gc2VjdGlvbiAy
LjEgYnV0IHRvIG1vdmUgaXQKZGlyZWN0bHkgdW5kZXIgdGhlIHJlcXVpcmVtZW50IG9uIHN0
YXRpYyBwcm92aXNpb25pbmcuPG86cD48L286cD48L3NwYW4+PC9wPgoKPHAgY2xhc3M9TXNv
Tm9ybWFsIHN0eWxlPSd0ZXh0LWFsaWduOmp1c3RpZnknPjxvOnA+Jm5ic3A7PC9vOnA+PC9w
PgoKPHAgY2xhc3M9TXNvTm9ybWFsIHN0eWxlPSd0ZXh0LWFsaWduOmp1c3RpZnknPjxiIHN0
eWxlPSdtc28tYmlkaS1mb250LXdlaWdodDoKbm9ybWFsJz5Qcml2YXRlIGNvbW1lbnRzIGZy
b20gTG9hIDxzcGFuIGNsYXNzPVNwZWxsRT5BbmRlcnNzb248L3NwYW4+PG86cD48L286cD48
L2I+PC9wPgoKPHAgY2xhc3M9TXNvTm9ybWFsPjxzcGFuIGNsYXNzPUdyYW1FPnR3bzwvc3Bh
bj4gbml0cyAtIEFUTSBhbmQgUkFOIGlzIG9ubHkgdXNlZAppbiB0aGUgYWJicmV2aWF0aW9u
cyBzZWN0aW9uLjwvcD4KCjxwIGNsYXNzPU1zb05vcm1hbCBzdHlsZT0ndGV4dC1hbGlnbjpq
dXN0aWZ5Jz48c3BhbiBzdHlsZT0nY29sb3I6Z3JlZW4nPkkgaGF2ZQpyZW1vdmVkIFJBTiBm
cm9tIHRoZSBhYmJyZXZpYXRpb25zIHNlY3Rpb24uIEkgZGlkbtV0IHJlbW92ZSBBVE0gYXMg
aXQgaXMgdXNlZAppbiByZXF1aXJlbWVudCAzMS4gSSBhbHNvIHJlbW92ZWQgPHNwYW4gY2xh
c3M9R3JhbUU+QVNUTjwvc3Bhbj4gYXMgaXQgaXMgbm8KbG9uZ2VyIHVzZWQuPG86cD48L286
cD48L3NwYW4+PC9wPgoKPC9kaXY+Cgo8L2JvZHk+Cgo8L2h0bWw+Cg==
--B_3328558098_51486309--


From root@core3.amsl.com  Tue Jun 23 13:30:02 2009
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 2952E3A6D46; Tue, 23 Jun 2009 13:30:01 -0700 (PDT)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20090623203002.2952E3A6D46@core3.amsl.com>
Date: Tue, 23 Jun 2009 13:30:02 -0700 (PDT)
Cc: pwe3@ietf.org
Subject: [PWE3] I-D Action:draft-ietf-pwe3-iccp-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: <http://www.ietf.org/mail-archive/web/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, 23 Jun 2009 20:30: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           : Inter-Chassis Communication Protocol for L2VPN PE Redundancy
	Author(s)       : L. Martini, et al.
	Filename        : draft-ietf-pwe3-iccp-01.txt
	Pages           : 61
	Date            : 2009-06-23

This document specifies an inter-chassis communication protocol
(ICCP) that enables Provider Edge (PE) device redundancy for Virtual
Private Wire Service (VPWS) and Virtual Private LAN Service (VPLS)
applications. The protocol runs within a set of two or more PEs,
forming a redundancy group, for the purpose of synchronizing data
amongst the systems. It accommodates multi-chassis attachment circuit
as well as pseudowire redundancy mechanisms.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-pwe3-iccp-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-iccp-01.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

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


--NextPart--

From albert.john@zte.com.cn  Thu Jun 25 06:21:05 2009
Return-Path: <albert.john@zte.com.cn>
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 8BC9228C19C for <pwe3@core3.amsl.com>; Thu, 25 Jun 2009 06:21:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.487
X-Spam-Level: 
X-Spam-Status: No, score=-100.487 tagged_above=-999 required=5 tests=[AWL=0.751, BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_75=0.6, RCVD_DOUBLE_IP_LOOSE=0.76, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8xgXddCHOXJb for <pwe3@core3.amsl.com>; Thu, 25 Jun 2009 06:21:04 -0700 (PDT)
Received: from mx6.zte.com.cn (mx6.zte.com.cn [63.218.89.70]) by core3.amsl.com (Postfix) with ESMTP id 7FDD128C155 for <pwe3@ietf.org>; Thu, 25 Jun 2009 06:21:02 -0700 (PDT)
Received: from [10.30.17.100] by mx6.zte.com.cn with surfront esmtp id 91101397396305; Thu, 25 Jun 2009 21:08:56 +0800 (CST)
Received: from [10.30.3.18] by [10.30.17.100] with StormMail ESMTP id 59484.1397396305; Thu, 25 Jun 2009 20:29:12 +0800 (CST)
Received: from notes_smtp.zte.com.cn ([10.30.1.239]) by mse1.zte.com.cn with ESMTP id n5PCZXPk034320 for <pwe3@ietf.org>; Thu, 25 Jun 2009 20:35:33 +0800 (CST) (envelope-from albert.john@zte.com.cn)
To: pwe3@ietf.org
MIME-Version: 1.0
X-Mailer: Lotus Notes Release 6.5.4 March 27, 2005
Message-ID: <OF2078B999.D6312EAA-ON482575E0.00451B24-482575E0.00452654@zte.com.cn>
From: albert.john@zte.com.cn
Date: Thu, 25 Jun 2009 20:35:11 +0800
X-MIMETrack: S/MIME Sign by Notes Client on JiangXiaoWei181977/user/zte_ltd(Release 6.5.4|March 27, 2005) at 2009-06-25 20:35:17, Serialize by Notes Client on JiangXiaoWei181977/user/zte_ltd(Release 6.5.4|March 27, 2005) at 2009-06-25 20:35:17, Serialize complete at 2009-06-25 20:35:17, S/MIME Sign failed at 2009-06-25 20:35:17: ???????, Serialize by Router on notes_smtp/zte_ltd(Release 6.5.4|March 27, 2005) at 2009-06-25 20:35:21, Serialize complete at 2009-06-25 20:35:21
Content-Type: multipart/alternative; boundary="=_alternative 00452652482575E0_="
X-MAIL: mse1.zte.com.cn n5PCZXPk034320
Subject: [PWE3] New LDP GR for PW draft submitted, please help to review and comment, thank you
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: <http://www.ietf.org/mail-archive/web/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, 25 Jun 2009 13:21:05 -0000

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

Hi Group,

A new LDP GR for PW draft submitted, please help to review and 
comment,thank you!

This draft intends to be an update for  [RFC 3478] LDP GR.

Regards,
Albert


                    LDP Graceful Restart for Pseudowire
                      draft-jiang-pwe3-ldp-gr-00.txt



Abstract

   This document describes a LDP graceful restart(GR) mechanism that
   helps to minimize the negative effects on single or multi-segment
   pseudowire traffic caused by Provider Edge (PE) control plane restart,
   specifically by the restart of its Label Distribution Protocol (LDP)
   component.

Table of Contents


   1. Introduction................................................2
   2. Conventions used in this document...........................3
   3. Single-segment Pseudowire LDP Graceful Restart Mechanism....3
   4. Multi-segment Pseudowire LDP Graceful Restart Mechanism.....3
   5. Virtual Private LAN Service LDP Graceful Restart Mechanism..3
   6. Security Considerations.....................................4
   7. IANA Considerations.........................................4
   8. Conclusions.................................................4
   9. References..................................................4
      9.1. Normative References...................................4
      9.2. Informative References.................................5
   10. Acknowledgments............................................5

1. Introduction

   Single-segment pseudowire defined in [RFC 3985] allows multi services
   to be carried over packet switching networks.

   [RFC 4447] defines extension to LDP for single-segment pseudowire
   setup and maintenance. The extended LDP is called Targeted LDP and
   runs between the end points.

   As defined in [RFC 5254], multi-segment pseudowire allows pseudowire
   traffic to transport over multiple PSN administrative or
   technological domains. And it also states three setup mechanisms of
   static configuration, signaled with pre-determined route and signaled
   with dynamic route.

   [DYNAMIC MS-PW] defines extension to LDP for multi-segment pseudowire
   setup using generalized FEC 129 which needs the relay of LDP
   signaling cross each pseudowire segment.

   [RFC 3478] defines graceful restart mechanism for LDP, in which LSRs
   are enhanced with the ability to preserve MPLS forwarding state
   during LDP restart.

   The mechanism defined in [RFC 3478] is for MPLS LSP and can be
   applied to pseudowire. The purpose of this draft is to specify the
   procedures and possible extensions to LDP for single-segment and
   multi-segment pseudowire control plane graceful restart.


2. Conventions used in this document

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in [RFC 2119].

3. Single-segment Pseudowire LDP Graceful Restart Mechanism

   LDP graceful restart procedure for single-segment pseudowire follows
   the same mechanism described in LDP graceful restart for MPLS [RFC
   3478]. The difference is that in pseudowire scenario, the preserved
   labels are pseudowire labels, while in the case of MPLS, the reserved
   labels are for MPLS LSPs.

   Also, pseudowire status is UP and forwarding state is preserved
   during the LDP graceful restart. While upon graceful restart failure,
   pseudowire will be torn down. Pseudowire can be set up again later.

   It should be noticed that pseudowire LDP graceful restart capability
   is decoupled from MPLS LSP LDP graceful restart capability, because
   the outer layer tunnel for pseudowire could be other than MPLS LSP.

4. Multi-segment Pseudowire LDP Graceful Restart Mechanism

   Multi-segment pseudowire is segmented into a number of single segment
   pseudowires. Each single segment pseudowire can have its own LDP
   graceful restart procedure, which can be independent from each other.
   For each affected segment, the procedure is very similar to that of
   single-segment pseudowire LDP graceful restart, while it has extra
   steps for failure handling.

   When LDP graceful restart failed, PEs in relevant segment will send
   PW label withdraw message to their upstream peers and PW label
   release message to their downstream peers so as to tear down the
   multi-segment pseudowire. After that, MS-PW could be re-established.

5. Virtual Private LAN Service LDP Graceful Restart Mechanism

   As defined in [RFC 4762], full mesh LDP sessions are established
   among all PEs for VPLS PWs. LDP graceful restart for VPLS follows the
   same mechanism as defined in LDP graceful restart for SS-PW.

   In H-VPLS model defined in [RFC 4762], spoke links between MTU and
   hub PE may span multiple administrative domain in which case LDP
   graceful restart procedure for MS-PW may be used.

6. Security Considerations

   [RFC5036] describes the security considerations that apply to the
   base LDP specification. The same security framework and
   considerations apply to the capability mechanism described in this
   document.

7. IANA Considerations

   None.

8. Conclusions

   In this document, LDP graceful restart mechanism for MPLS LSP defined 
in [RFC 3478]
   is extended to cover pseudowire, and scenarios of SS-PW,MS-PW,VPLS and 
H-VPLS are
   discussed.


9. References

9.1. Normative References

   [RFC 5036] Andersson, L., Menei, I., and Thomas, B., Editors, "LDP
             Specification", RFC 5036, September 2007.

   [RFC 3478] Leelanivas, M., Aggarwal R., Editors, "Graceful Restart
             Mechanism for Label Distribution Protocol", RFC 3478,
             February 2003.

   [RFC 3479] Farrel, A., "Fault Tolerance for the Label
             Distribution Protocol (LDP)", RFC 3479, February 2003.

   [RFC 4447] Martini, L., Rosen, E., El-Aawar, N., Smith, T., Heron, G.,
             Editors, "Pseudowire Setup and Maintenance Using the Label
             Distribution Protocol (LDP)", RFC 4447, October 2008.

   [RFC 4762] Lasserre, M., Kompella, V., Editors, " Virtual Private LAN
             Service (VPLS) Using Label Distribution Protocol (LDP)
             Signaling", RFC 4762, January 2007.

   [RFC 2119] Bradner, S., Editor, "Key words for use in RFCs to
               Indicate Requirement Levels", BCP 14, RFC2119, March 1997.


9.2. Informative References

   [RFC 5254] Bitar, N., Bocci M., Martini, L., Editors, "Requirements
             for Multi-Segment Pseudowire Emulation Edge-to-Edge (PWE3)",
             RFC 5254, October 2008.

   [MS-PW_ARCH] Bocci M., Bryant, S., Editors, "An Architecture for
             Multi-Segment Pseudowire Emulation Edge-to-Edge" draft-
             ietf-pwe3-ms-pw-arch-06.txt, Work in Progress, February
             2009.

   [DYNAMIC MS-PW] Martini, L., Bocci M., Balus, F., Editors, "Dynamic
             Placement of Multi Segment Pseudo Wires" draft-ietf-pwe3-
             dynamic-ms-pw-09, Work in Progress, February 2009.

   [SEGMENTED PW] Martini, L., Metz, C., Nadeau, T., Bocci M., Balus,
             F., Aissaoui, M., Duckett, M., Editors, "Segmented
             Pseudowire" draft-ietf-pwe3-segmented-pw-11.txt, Work in
             Progress, February 2009.

   [LDP_CAPABILITY] Thomas, B., Aggarwal, S., Aggarwal, R., Le Roux,
             J.L., Syed Kamran Raza, Editors,  "LDP Capabilities" draft-
             ietf-mpls-ldp-capabilities-04.txt, Work in Progress, April
             2009.

10. Acknowledgments

   This document was prepared using 2-Word-v2.0.template.dot.


--------------------------------------------------------
ZTE Information Security Notice: The information contained in this mail is solely property of the sender's organization. This mail communication is confidential. Recipients named above are obligated to maintain secrecy and are not permitted to disclose the contents of this communication to others.
This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the originator of the message. Any views expressed in this message are those of the individual sender.
This message has been scanned for viruses and Spam by ZTE Anti-Spam system.

--=_alternative 00452652482575E0_=
Content-Type: text/html; charset="US-ASCII"


<br><font size=3><tt>Hi Group,</tt></font>
<br>
<br><font size=3><tt>A new LDP GR for PW draft submitted, please help to
review and comment,thank you!</tt></font>
<br>
<br><font size=3><tt>This draft intends to be an update for &nbsp;[RFC
3478] LDP GR.</tt></font>
<br>
<br><font size=3><tt>Regards,</tt></font>
<br><font size=3><tt>Albert<br>
<br>
<br>
 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;LDP
Graceful Restart for Pseudowire<br>
 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
&nbsp;draft-jiang-pwe3-ldp-gr-00.txt<br>
<br>
<br>
<br>
Abstract<br>
<br>
 &nbsp; This document describes a LDP graceful restart(GR) mechanism that<br>
 &nbsp; helps to minimize the negative effects on single or multi-segment<br>
 &nbsp; pseudowire traffic caused by Provider Edge (PE) control plane restart,<br>
 &nbsp; specifically by the restart of its Label Distribution Protocol
(LDP)<br>
 &nbsp; component.<br>
<br>
Table of Contents<br>
<br>
<br>
 &nbsp; 1. Introduction................................................2<br>
 &nbsp; 2. Conventions used in this document...........................3<br>
 &nbsp; 3. Single-segment Pseudowire LDP Graceful Restart Mechanism....3<br>
 &nbsp; 4. Multi-segment Pseudowire LDP Graceful Restart Mechanism.....3<br>
 &nbsp; 5. Virtual Private LAN Service LDP Graceful Restart Mechanism..3<br>
 &nbsp; 6. Security Considerations.....................................4<br>
 &nbsp; 7. IANA Considerations.........................................4<br>
 &nbsp; 8. Conclusions.................................................4<br>
 &nbsp; 9. References..................................................4<br>
 &nbsp; &nbsp; &nbsp;9.1. Normative References...................................4<br>
 &nbsp; &nbsp; &nbsp;9.2. Informative References.................................5<br>
 &nbsp; 10. Acknowledgments............................................5<br>
<br>
1. Introduction<br>
<br>
 &nbsp; Single-segment pseudowire defined in [RFC 3985] allows multi services<br>
 &nbsp; to be carried over packet switching networks.<br>
<br>
 &nbsp; [RFC 4447] defines extension to LDP for single-segment pseudowire<br>
 &nbsp; setup and maintenance. The extended LDP is called Targeted LDP
and<br>
 &nbsp; runs between the end points.<br>
<br>
 &nbsp; As defined in [RFC 5254], multi-segment pseudowire allows pseudowire<br>
 &nbsp; traffic to transport over multiple PSN administrative or<br>
 &nbsp; technological domains. And it also states three setup mechanisms
of<br>
 &nbsp; static configuration, signaled with pre-determined route and signaled<br>
 &nbsp; with dynamic route.<br>
<br>
 &nbsp; [DYNAMIC MS-PW] defines extension to LDP for multi-segment pseudowire<br>
 &nbsp; setup using generalized FEC 129 which needs the relay of LDP<br>
 &nbsp; signaling cross each pseudowire segment.<br>
<br>
 &nbsp; [RFC 3478] defines graceful restart mechanism for LDP, in which
LSRs<br>
 &nbsp; are enhanced with the ability to preserve MPLS forwarding state<br>
 &nbsp; during LDP restart.<br>
<br>
 &nbsp; The mechanism defined in [RFC 3478] is for MPLS LSP and can be<br>
 &nbsp; applied to pseudowire. The purpose of this draft is to specify
the<br>
 &nbsp; procedures and possible extensions to LDP for single-segment and<br>
 &nbsp; multi-segment pseudowire control plane graceful restart.<br>
<br>
<br>
2. Conventions used in this document<br>
<br>
 &nbsp; The key words &quot;MUST&quot;, &quot;MUST NOT&quot;, &quot;REQUIRED&quot;,
&quot;SHALL&quot;, &quot;SHALL NOT&quot;,<br>
 &nbsp; &quot;SHOULD&quot;, &quot;SHOULD NOT&quot;, &quot;RECOMMENDED&quot;,
&quot;MAY&quot;, and &quot;OPTIONAL&quot; in this<br>
 &nbsp; document are to be interpreted as described in [RFC 2119].<br>
<br>
3. Single-segment Pseudowire LDP Graceful Restart Mechanism<br>
<br>
 &nbsp; LDP graceful restart procedure for single-segment pseudowire follows<br>
 &nbsp; the same mechanism described in LDP graceful restart for MPLS [RFC<br>
 &nbsp; 3478]. The difference is that in pseudowire scenario, the preserved<br>
 &nbsp; labels are pseudowire labels, while in the case of MPLS, the reserved<br>
 &nbsp; labels are for MPLS LSPs.<br>
<br>
 &nbsp; Also, pseudowire status is UP and forwarding state is preserved<br>
 &nbsp; during the LDP graceful restart. While upon graceful restart failure,<br>
 &nbsp; pseudowire will be torn down. Pseudowire can be set up again later.<br>
<br>
 &nbsp; It should be noticed that pseudowire LDP graceful restart capability<br>
 &nbsp; is decoupled from MPLS LSP LDP graceful restart capability, because<br>
 &nbsp; the outer layer tunnel for pseudowire could be other than MPLS
LSP.<br>
<br>
4. Multi-segment Pseudowire LDP Graceful Restart Mechanism<br>
<br>
 &nbsp; Multi-segment pseudowire is segmented into a number of single segment<br>
 &nbsp; pseudowires. Each single segment pseudowire can have its own LDP<br>
 &nbsp; graceful restart procedure, which can be independent from each
other.<br>
 &nbsp; For each affected segment, the procedure is very similar to that
of<br>
 &nbsp; single-segment pseudowire LDP graceful restart, while it has extra<br>
 &nbsp; steps for failure handling.<br>
<br>
 &nbsp; When LDP graceful restart failed, PEs in relevant segment will
send<br>
 &nbsp; PW label withdraw message to their upstream peers and PW label<br>
 &nbsp; release message to their downstream peers so as to tear down the<br>
 &nbsp; multi-segment pseudowire. After that, MS-PW could be re-established.<br>
<br>
5. Virtual Private LAN Service LDP Graceful Restart Mechanism<br>
<br>
 &nbsp; As defined in [RFC 4762], full mesh LDP sessions are established<br>
 &nbsp; among all PEs for VPLS PWs. LDP graceful restart for VPLS follows
the<br>
 &nbsp; same mechanism as defined in LDP graceful restart for SS-PW.<br>
<br>
 &nbsp; In H-VPLS model defined in [RFC 4762], spoke links between MTU
and<br>
 &nbsp; hub PE may span multiple administrative domain in which case LDP<br>
 &nbsp; graceful restart procedure for MS-PW may be used.<br>
<br>
6. Security Considerations<br>
<br>
 &nbsp; [RFC5036] describes the security considerations that apply to the<br>
 &nbsp; base LDP specification. The same security framework and<br>
 &nbsp; considerations apply to the capability mechanism described in this<br>
 &nbsp; document.<br>
<br>
7. IANA Considerations<br>
<br>
 &nbsp; None.<br>
<br>
8. Conclusions<br>
<br>
 &nbsp; In this document, LDP graceful restart mechanism for MPLS LSP defined
in [RFC 3478]<br>
 &nbsp; is extended to cover pseudowire, and scenarios of SS-PW,MS-PW,VPLS
and H-VPLS are<br>
 &nbsp; discussed.<br>
<br>
<br>
9. References<br>
<br>
9.1. Normative References<br>
<br>
 &nbsp; [RFC 5036] Andersson, L., Menei, I., and Thomas, B., Editors, &quot;LDP<br>
 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Specification&quot;, RFC 5036,
September 2007.<br>
<br>
 &nbsp; [RFC 3478] Leelanivas, M., Aggarwal R., Editors, &quot;Graceful
Restart<br>
 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Mechanism for Label Distribution
Protocol&quot;, RFC 3478,<br>
 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; February 2003.<br>
<br>
 &nbsp; [RFC 3479] Farrel, A., &quot;Fault Tolerance for the Label<br>
 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Distribution Protocol (LDP)&quot;,
RFC 3479, February 2003.<br>
<br>
 &nbsp; [RFC 4447] Martini, L., Rosen, E., El-Aawar, N., Smith, T., Heron,
G.,<br>
 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Editors, &quot;Pseudowire Setup
and Maintenance Using the Label<br>
 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Distribution Protocol (LDP)&quot;,
RFC 4447, October 2008.<br>
<br>
 &nbsp; [RFC 4762] Lasserre, M., Kompella, V., Editors, &quot; Virtual
Private LAN<br>
 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Service (VPLS) Using Label Distribution
Protocol (LDP)<br>
 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Signaling&quot;, RFC 4762, January
2007.<br>
<br>
 &nbsp; [RFC 2119] Bradner, S., Editor, &quot;Key words for use in RFCs
to<br>
 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Indicate Requirement
Levels&quot;, BCP 14, RFC2119, March 1997.<br>
<br>
<br>
9.2. Informative References<br>
<br>
 &nbsp; [RFC 5254] Bitar, N., Bocci M., Martini, L., Editors, &quot;Requirements<br>
 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; for Multi-Segment Pseudowire
Emulation Edge-to-Edge (PWE3)&quot;,<br>
 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; RFC 5254, October 2008.<br>
<br>
 &nbsp; [MS-PW_ARCH] Bocci M., Bryant, S., Editors, &quot;An Architecture
for<br>
 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Multi-Segment Pseudowire Emulation
Edge-to-Edge&quot; draft-<br>
 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; ietf-pwe3-ms-pw-arch-06.txt,
Work in Progress, February<br>
 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2009.<br>
<br>
 &nbsp; [DYNAMIC MS-PW] Martini, L., Bocci M., Balus, F., Editors, &quot;Dynamic<br>
 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Placement of Multi Segment Pseudo
Wires&quot; draft-ietf-pwe3-<br>
 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; dynamic-ms-pw-09, Work in Progress,
February 2009.<br>
<br>
 &nbsp; [SEGMENTED PW] Martini, L., Metz, C., Nadeau, T., Bocci M., Balus,<br>
 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; F., Aissaoui, M., Duckett, M.,
Editors, &quot;Segmented<br>
 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Pseudowire&quot; draft-ietf-pwe3-segmented-pw-11.txt,
Work in<br>
 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Progress, February 2009.<br>
<br>
 &nbsp; [LDP_CAPABILITY] Thomas, B., Aggarwal, S., Aggarwal, R., Le Roux,<br>
 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; J.L., Syed Kamran Raza, Editors,
&nbsp;&quot;LDP Capabilities&quot; draft-<br>
 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; ietf-mpls-ldp-capabilities-04.txt,
Work in Progress, April<br>
 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2009.<br>
<br>
10. Acknowledgments<br>
<br>
 &nbsp; This document was prepared using 2-Word-v2.0.template.dot.<br>
</tt></font><br><pre>
--------------------------------------------------------
ZTE&nbsp;Information&nbsp;Security&nbsp;Notice:&nbsp;The&nbsp;information&nbsp;contained&nbsp;in&nbsp;this&nbsp;mail&nbsp;is&nbsp;solely&nbsp;property&nbsp;of&nbsp;the&nbsp;sender's&nbsp;organization.&nbsp;This&nbsp;mail&nbsp;communication&nbsp;is&nbsp;confidential.&nbsp;Recipients&nbsp;named&nbsp;above&nbsp;are&nbsp;obligated&nbsp;to&nbsp;maintain&nbsp;secrecy&nbsp;and&nbsp;are&nbsp;not&nbsp;permitted&nbsp;to&nbsp;disclose&nbsp;the&nbsp;contents&nbsp;of&nbsp;this&nbsp;communication&nbsp;to&nbsp;others.
This&nbsp;email&nbsp;and&nbsp;any&nbsp;files&nbsp;transmitted&nbsp;with&nbsp;it&nbsp;are&nbsp;confidential&nbsp;and&nbsp;intended&nbsp;solely&nbsp;for&nbsp;the&nbsp;use&nbsp;of&nbsp;the&nbsp;individual&nbsp;or&nbsp;entity&nbsp;to&nbsp;whom&nbsp;they&nbsp;are&nbsp;addressed.&nbsp;If&nbsp;you&nbsp;have&nbsp;received&nbsp;this&nbsp;email&nbsp;in&nbsp;error&nbsp;please&nbsp;notify&nbsp;the&nbsp;originator&nbsp;of&nbsp;the&nbsp;message.&nbsp;Any&nbsp;views&nbsp;expressed&nbsp;in&nbsp;this&nbsp;message&nbsp;are&nbsp;those&nbsp;of&nbsp;the&nbsp;individual&nbsp;sender.
This&nbsp;message&nbsp;has&nbsp;been&nbsp;scanned&nbsp;for&nbsp;viruses&nbsp;and&nbsp;Spam&nbsp;by&nbsp;ZTE&nbsp;Anti-Spam&nbsp;system.
</pre>
--=_alternative 00452652482575E0_=--


From root@core3.amsl.com  Thu Jun 25 15:45:01 2009
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 558A03A6966; Thu, 25 Jun 2009 15:45:01 -0700 (PDT)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20090625224501.558A03A6966@core3.amsl.com>
Date: Thu, 25 Jun 2009 15:45:01 -0700 (PDT)
Cc: pwe3@ietf.org
Subject: [PWE3] I-D ACTION:draft-ietf-pwe3-oam-msg-map-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: <http://www.ietf.org/mail-archive/web/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, 25 Jun 2009 22: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		: Pseudo Wire (PW) OAM Message Mapping
	Author(s)	: L. Martini, T. Nadeau, M. Aissaoui, D. Allan, Y. Stein
	Filename	: draft-ietf-pwe3-oam-msg-map-11.txt
	Pages		: 40
	Date		: 2009-6-25
	
This document specifies the mapping and notification of defect states 
   between a Pseudo Wire and the Attachment Circuits (AC) of the end-to-
   end emulated service. This document covers the case whereby the ACs 
   and the PWs are of the same type in accordance to the PWE3 
   architecture [RFC3985] such that a homogenous PW service can be 
   constructed. 

 

Conventions used in this document 

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 
document are to be interpreted as described in RFC-2119.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-pwe3-oam-msg-map-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-oam-msg-map-11.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

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


--NextPart--


From loa@pi.nu  Fri Jun 26 06:29:44 2009
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 C315E3A6B11; Fri, 26 Jun 2009 06:29:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.512
X-Spam-Level: 
X-Spam-Status: No, score=-2.512 tagged_above=-999 required=5 tests=[AWL=0.087,  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 BzIK149a5syn; Fri, 26 Jun 2009 06:29:44 -0700 (PDT)
Received: from mail.pi.nu (mail.pi.nu [194.71.127.148]) by core3.amsl.com (Postfix) with ESMTP id 8ED5E3A6B22; Fri, 26 Jun 2009 06:29:43 -0700 (PDT)
Received: from [192.168.0.100] (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@pi.nu) by mail.pi.nu (Postfix) with ESMTPSA id 997E3D4048; Fri, 26 Jun 2009 15:29:53 +0200 (CEST)
Message-ID: <4A44CD4E.1020901@pi.nu>
Date: Fri, 26 Jun 2009 15:29:50 +0200
From: Loa Andersson <loa@pi.nu>
User-Agent: Thunderbird 2.0.0.22 (Windows/20090605)
MIME-Version: 1.0
To: mpls@ietf.org, mpls-tp@ietf.org, pwe3@ietf.org, ccamp@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-nm-req-02.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: <http://www.ietf.org/mail-archive/web/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, 26 Jun 2009 13:29:44 -0000

All,

this is to start a working gorup last call on
draft-ietf-mpls-tp-nm-req-02.txt

The draft was wg lasted called earlier and has now been
updated according to comments.

Please direct your comments to the mpls-tp@ietf.org mailing list,
i.e. don't just reply to this mail.

The working group last call will end COB July 10.

/Loa



-- 


Loa Andersson

Sr Strategy and Standards Manager    phone:  +46 10 717 52 13
Ericsson ///                                 +46 767 72 92 13

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

From albert.john@zte.com.cn  Wed Jun 24 12:51:51 2009
Return-Path: <albert.john@zte.com.cn>
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 BE3CD3A6FDE for <pwe3@core3.amsl.com>; Wed, 24 Jun 2009 12:51:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.238
X-Spam-Level: 
X-Spam-Status: No, score=-101.238 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_75=0.6, RCVD_DOUBLE_IP_LOOSE=0.76, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OXdE1AmrU5P6 for <pwe3@core3.amsl.com>; Wed, 24 Jun 2009 12:51:50 -0700 (PDT)
Received: from mx5.zte.com.cn (mx5.zte.com.cn [63.217.80.70]) by core3.amsl.com (Postfix) with ESMTP id 5ADC03A6D75 for <pwe3@ietf.org>; Wed, 24 Jun 2009 12:51:48 -0700 (PDT)
Received: from [10.30.17.100] by mx5.zte.com.cn with surfront esmtp id 111641397396305; Wed, 24 Jun 2009 20:02:08 +0800 (CST)
Received: from [10.30.3.18] by [10.30.17.100] with StormMail ESMTP id 59484.1397396305; Wed, 24 Jun 2009 19:22:40 +0800 (CST)
Received: from notes_smtp.zte.com.cn ([10.30.1.239]) by mse1.zte.com.cn with ESMTP id n5OBSxSN070922 for <pwe3@ietf.org>; Wed, 24 Jun 2009 19:28:59 +0800 (CST) (envelope-from albert.john@zte.com.cn)
To: pwe3@ietf.org
MIME-Version: 1.0
X-Mailer: Lotus Notes Release 6.5.4 March 27, 2005
Message-ID: <OFFA043688.F6451537-ON482575DF.003E3806-482575DF.003F0DF0@zte.com.cn>
From: albert.john@zte.com.cn
Date: Wed, 24 Jun 2009 19:28:25 +0800
X-MIMETrack: S/MIME Sign by Notes Client on JiangXiaoWei181977/user/zte_ltd(Release 6.5.4|March 27, 2005) at 2009-06-24 19:28:43, Serialize by Notes Client on JiangXiaoWei181977/user/zte_ltd(Release 6.5.4|March 27, 2005) at 2009-06-24 19:28:43, Serialize complete at 2009-06-24 19:28:43, S/MIME Sign failed at 2009-06-24 19:28:43: ???????, Serialize by Router on notes_smtp/zte_ltd(Release 6.5.4|March 27, 2005) at 2009-06-24 19:28:50, Serialize complete at 2009-06-24 19:28:50
Content-Type: multipart/alternative; boundary="=_alternative 003F0DEF482575DF_="
X-MAIL: mse1.zte.com.cn n5OBSxSN070922
X-Mailman-Approved-At: Mon, 29 Jun 2009 01:44:28 -0700
Subject: [PWE3] New LDP GR for PW draft submitted, please help to review and comment, thank you
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: <http://www.ietf.org/mail-archive/web/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, 25 Jun 2009 00:42:32 -0000

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

Hi Group,

A new LDP GR for PW draft submitted, please help to review and 
comment,thank you!

This draft intends to be an update for  [RFC 3478] LDP GR.

Regards,
Albert


                    LDP Graceful Restart for Pseudowire
                      draft-jiang-pwe3-ldp-gr-00.txt



Abstract

   This document describes a LDP graceful restart(GR) mechanism that
   helps to minimize the negative effects on single or multi-segment
   pseudowire traffic caused by Provider Edge (PE) control plane restart,
   specifically by the restart of its Label Distribution Protocol (LDP)
   component.

Table of Contents


   1. Introduction................................................2
   2. Conventions used in this document...........................3
   3. Single-segment Pseudowire LDP Graceful Restart Mechanism....3
   4. Multi-segment Pseudowire LDP Graceful Restart Mechanism.....3
   5. Virtual Private LAN Service LDP Graceful Restart Mechanism..3
   6. Security Considerations.....................................4
   7. IANA Considerations.........................................4
   8. Conclusions.................................................4
   9. References..................................................4
      9.1. Normative References...................................4
      9.2. Informative References.................................5
   10. Acknowledgments............................................5

1. Introduction

   Single-segment pseudowire defined in [RFC 3985] allows multi services
   to be carried over packet switching networks.

   [RFC 4447] defines extension to LDP for single-segment pseudowire
   setup and maintenance. The extended LDP is called Targeted LDP and
   runs between the end points.

   As defined in [RFC 5254], multi-segment pseudowire allows pseudowire
   traffic to transport over multiple PSN administrative or
   technological domains. And it also states three setup mechanisms of
   static configuration, signaled with pre-determined route and signaled
   with dynamic route.

   [DYNAMIC MS-PW] defines extension to LDP for multi-segment pseudowire
   setup using generalized FEC 129 which needs the relay of LDP
   signaling cross each pseudowire segment.

   [RFC 3478] defines graceful restart mechanism for LDP, in which LSRs
   are enhanced with the ability to preserve MPLS forwarding state
   during LDP restart.

   The mechanism defined in [RFC 3478] is for MPLS LSP and can be
   applied to pseudowire. The purpose of this draft is to specify the
   procedures and possible extensions to LDP for single-segment and
   multi-segment pseudowire control plane graceful restart.


2. Conventions used in this document

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in [RFC 2119].

3. Single-segment Pseudowire LDP Graceful Restart Mechanism

   LDP graceful restart procedure for single-segment pseudowire follows
   the same mechanism described in LDP graceful restart for MPLS [RFC
   3478]. The difference is that in pseudowire scenario, the preserved
   labels are pseudowire labels, while in the case of MPLS, the reserved
   labels are for MPLS LSPs.

   Also, pseudowire status is UP and forwarding state is preserved
   during the LDP graceful restart. While upon graceful restart failure,
   pseudowire will be torn down. Pseudowire can be set up again later.

   It should be noticed that pseudowire LDP graceful restart capability
   is decoupled from MPLS LSP LDP graceful restart capability, because
   the outer layer tunnel for pseudowire could be other than MPLS LSP.

4. Multi-segment Pseudowire LDP Graceful Restart Mechanism

   Multi-segment pseudowire is segmented into a number of single segment
   pseudowires. Each single segment pseudowire can have its own LDP
   graceful restart procedure, which can be independent from each other.
   For each affected segment, the procedure is very similar to that of
   single-segment pseudowire LDP graceful restart, while it has extra
   steps for failure handling.

   When LDP graceful restart failed, PEs in relevant segment will send
   PW label withdraw message to their upstream peers and PW label
   release message to their downstream peers so as to tear down the
   multi-segment pseudowire. After that, MS-PW could be re-established.

5. Virtual Private LAN Service LDP Graceful Restart Mechanism

   As defined in [RFC 4762], full mesh LDP sessions are established
   among all PEs for VPLS PWs. LDP graceful restart for VPLS follows the
   same mechanism as defined in LDP graceful restart for SS-PW.

   In H-VPLS model defined in [RFC 4762], spoke links between MTU and
   hub PE may span multiple administrative domain in which case LDP
   graceful restart procedure for MS-PW may be used.

6. Security Considerations

   [RFC5036] describes the security considerations that apply to the
   base LDP specification. The same security framework and
   considerations apply to the capability mechanism described in this
   document.

7. IANA Considerations

   None.

8. Conclusions

   In this document, LDP graceful restart mechanism for MPLS LSP defined 
in [RFC 3478]
   is extended to cover pseudowire, and scenarios of SS-PW,MS-PW,VPLS and 
H-VPLS are
   discussed.


9. References

9.1. Normative References

   [RFC 5036] Andersson, L., Menei, I., and Thomas, B., Editors, "LDP
             Specification", RFC 5036, September 2007.

   [RFC 3478] Leelanivas, M., Aggarwal R., Editors, "Graceful Restart
             Mechanism for Label Distribution Protocol", RFC 3478,
             February 2003.

   [RFC 3479] Farrel, A., "Fault Tolerance for the Label
             Distribution Protocol (LDP)", RFC 3479, February 2003.

   [RFC 4447] Martini, L., Rosen, E., El-Aawar, N., Smith, T., Heron, G.,
             Editors, "Pseudowire Setup and Maintenance Using the Label
             Distribution Protocol (LDP)", RFC 4447, October 2008.

   [RFC 4762] Lasserre, M., Kompella, V., Editors, " Virtual Private LAN
             Service (VPLS) Using Label Distribution Protocol (LDP)
             Signaling", RFC 4762, January 2007.

   [RFC 2119] Bradner, S., Editor, "Key words for use in RFCs to
               Indicate Requirement Levels", BCP 14, RFC2119, March 1997.


9.2. Informative References

   [RFC 5254] Bitar, N., Bocci M., Martini, L., Editors, "Requirements
             for Multi-Segment Pseudowire Emulation Edge-to-Edge (PWE3)",
             RFC 5254, October 2008.

   [MS-PW_ARCH] Bocci M., Bryant, S., Editors, "An Architecture for
             Multi-Segment Pseudowire Emulation Edge-to-Edge" draft-
             ietf-pwe3-ms-pw-arch-06.txt, Work in Progress, February
             2009.

   [DYNAMIC MS-PW] Martini, L., Bocci M., Balus, F., Editors, "Dynamic
             Placement of Multi Segment Pseudo Wires" draft-ietf-pwe3-
             dynamic-ms-pw-09, Work in Progress, February 2009.

   [SEGMENTED PW] Martini, L., Metz, C., Nadeau, T., Bocci M., Balus,
             F., Aissaoui, M., Duckett, M., Editors, "Segmented
             Pseudowire" draft-ietf-pwe3-segmented-pw-11.txt, Work in
             Progress, February 2009.

   [LDP_CAPABILITY] Thomas, B., Aggarwal, S., Aggarwal, R., Le Roux,
             J.L., Syed Kamran Raza, Editors,  "LDP Capabilities" draft-
             ietf-mpls-ldp-capabilities-04.txt, Work in Progress, April
             2009.

10. Acknowledgments

   This document was prepared using 2-Word-v2.0.template.dot.


--------------------------------------------------------
ZTE Information Security Notice: The information contained in this mail is solely property of the sender's organization. This mail communication is confidential. Recipients named above are obligated to maintain secrecy and are not permitted to disclose the contents of this communication to others.
This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the originator of the message. Any views expressed in this message are those of the individual sender.
This message has been scanned for viruses and Spam by ZTE Anti-Spam system.

--=_alternative 003F0DEF482575DF_=
Content-Type: text/html; charset="US-ASCII"


<br><font size=3><tt>Hi Group,</tt></font>
<br>
<br><font size=3><tt>A new LDP GR for PW draft submitted, please help to
review and comment,thank you!</tt></font>
<br>
<br><font size=3><tt>This draft intends to be an update for &nbsp;[RFC
3478] LDP GR.</tt></font>
<br>
<br><font size=3><tt>Regards,</tt></font>
<br><font size=3><tt>Albert<br>
<br>
<br>
 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;LDP
Graceful Restart for Pseudowire<br>
 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
&nbsp;draft-jiang-pwe3-ldp-gr-00.txt<br>
<br>
<br>
<br>
Abstract<br>
<br>
 &nbsp; This document describes a LDP graceful restart(GR) mechanism that<br>
 &nbsp; helps to minimize the negative effects on single or multi-segment<br>
 &nbsp; pseudowire traffic caused by Provider Edge (PE) control plane restart,<br>
 &nbsp; specifically by the restart of its Label Distribution Protocol
(LDP)<br>
 &nbsp; component.<br>
<br>
Table of Contents<br>
<br>
<br>
 &nbsp; 1. Introduction................................................2<br>
 &nbsp; 2. Conventions used in this document...........................3<br>
 &nbsp; 3. Single-segment Pseudowire LDP Graceful Restart Mechanism....3<br>
 &nbsp; 4. Multi-segment Pseudowire LDP Graceful Restart Mechanism.....3<br>
 &nbsp; 5. Virtual Private LAN Service LDP Graceful Restart Mechanism..3<br>
 &nbsp; 6. Security Considerations.....................................4<br>
 &nbsp; 7. IANA Considerations.........................................4<br>
 &nbsp; 8. Conclusions.................................................4<br>
 &nbsp; 9. References..................................................4<br>
 &nbsp; &nbsp; &nbsp;9.1. Normative References...................................4<br>
 &nbsp; &nbsp; &nbsp;9.2. Informative References.................................5<br>
 &nbsp; 10. Acknowledgments............................................5<br>
<br>
1. Introduction<br>
<br>
 &nbsp; Single-segment pseudowire defined in [RFC 3985] allows multi services<br>
 &nbsp; to be carried over packet switching networks.<br>
<br>
 &nbsp; [RFC 4447] defines extension to LDP for single-segment pseudowire<br>
 &nbsp; setup and maintenance. The extended LDP is called Targeted LDP
and<br>
 &nbsp; runs between the end points.<br>
<br>
 &nbsp; As defined in [RFC 5254], multi-segment pseudowire allows pseudowire<br>
 &nbsp; traffic to transport over multiple PSN administrative or<br>
 &nbsp; technological domains. And it also states three setup mechanisms
of<br>
 &nbsp; static configuration, signaled with pre-determined route and signaled<br>
 &nbsp; with dynamic route.<br>
<br>
 &nbsp; [DYNAMIC MS-PW] defines extension to LDP for multi-segment pseudowire<br>
 &nbsp; setup using generalized FEC 129 which needs the relay of LDP<br>
 &nbsp; signaling cross each pseudowire segment.<br>
<br>
 &nbsp; [RFC 3478] defines graceful restart mechanism for LDP, in which
LSRs<br>
 &nbsp; are enhanced with the ability to preserve MPLS forwarding state<br>
 &nbsp; during LDP restart.<br>
<br>
 &nbsp; The mechanism defined in [RFC 3478] is for MPLS LSP and can be<br>
 &nbsp; applied to pseudowire. The purpose of this draft is to specify
the<br>
 &nbsp; procedures and possible extensions to LDP for single-segment and<br>
 &nbsp; multi-segment pseudowire control plane graceful restart.<br>
<br>
<br>
2. Conventions used in this document<br>
<br>
 &nbsp; The key words &quot;MUST&quot;, &quot;MUST NOT&quot;, &quot;REQUIRED&quot;,
&quot;SHALL&quot;, &quot;SHALL NOT&quot;,<br>
 &nbsp; &quot;SHOULD&quot;, &quot;SHOULD NOT&quot;, &quot;RECOMMENDED&quot;,
&quot;MAY&quot;, and &quot;OPTIONAL&quot; in this<br>
 &nbsp; document are to be interpreted as described in [RFC 2119].<br>
<br>
3. Single-segment Pseudowire LDP Graceful Restart Mechanism<br>
<br>
 &nbsp; LDP graceful restart procedure for single-segment pseudowire follows<br>
 &nbsp; the same mechanism described in LDP graceful restart for MPLS [RFC<br>
 &nbsp; 3478]. The difference is that in pseudowire scenario, the preserved<br>
 &nbsp; labels are pseudowire labels, while in the case of MPLS, the reserved<br>
 &nbsp; labels are for MPLS LSPs.<br>
<br>
 &nbsp; Also, pseudowire status is UP and forwarding state is preserved<br>
 &nbsp; during the LDP graceful restart. While upon graceful restart failure,<br>
 &nbsp; pseudowire will be torn down. Pseudowire can be set up again later.<br>
<br>
 &nbsp; It should be noticed that pseudowire LDP graceful restart capability<br>
 &nbsp; is decoupled from MPLS LSP LDP graceful restart capability, because<br>
 &nbsp; the outer layer tunnel for pseudowire could be other than MPLS
LSP.<br>
<br>
4. Multi-segment Pseudowire LDP Graceful Restart Mechanism<br>
<br>
 &nbsp; Multi-segment pseudowire is segmented into a number of single segment<br>
 &nbsp; pseudowires. Each single segment pseudowire can have its own LDP<br>
 &nbsp; graceful restart procedure, which can be independent from each
other.<br>
 &nbsp; For each affected segment, the procedure is very similar to that
of<br>
 &nbsp; single-segment pseudowire LDP graceful restart, while it has extra<br>
 &nbsp; steps for failure handling.<br>
<br>
 &nbsp; When LDP graceful restart failed, PEs in relevant segment will
send<br>
 &nbsp; PW label withdraw message to their upstream peers and PW label<br>
 &nbsp; release message to their downstream peers so as to tear down the<br>
 &nbsp; multi-segment pseudowire. After that, MS-PW could be re-established.<br>
<br>
5. Virtual Private LAN Service LDP Graceful Restart Mechanism<br>
<br>
 &nbsp; As defined in [RFC 4762], full mesh LDP sessions are established<br>
 &nbsp; among all PEs for VPLS PWs. LDP graceful restart for VPLS follows
the<br>
 &nbsp; same mechanism as defined in LDP graceful restart for SS-PW.<br>
<br>
 &nbsp; In H-VPLS model defined in [RFC 4762], spoke links between MTU
and<br>
 &nbsp; hub PE may span multiple administrative domain in which case LDP<br>
 &nbsp; graceful restart procedure for MS-PW may be used.<br>
<br>
6. Security Considerations<br>
<br>
 &nbsp; [RFC5036] describes the security considerations that apply to the<br>
 &nbsp; base LDP specification. The same security framework and<br>
 &nbsp; considerations apply to the capability mechanism described in this<br>
 &nbsp; document.<br>
<br>
7. IANA Considerations<br>
<br>
 &nbsp; None.<br>
<br>
8. Conclusions<br>
<br>
 &nbsp; In this document, LDP graceful restart mechanism for MPLS LSP defined
in [RFC 3478]<br>
 &nbsp; is extended to cover pseudowire, and scenarios of SS-PW,MS-PW,VPLS
and H-VPLS are<br>
 &nbsp; discussed.<br>
<br>
<br>
9. References<br>
<br>
9.1. Normative References<br>
<br>
 &nbsp; [RFC 5036] Andersson, L., Menei, I., and Thomas, B., Editors, &quot;LDP<br>
 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Specification&quot;, RFC 5036,
September 2007.<br>
<br>
 &nbsp; [RFC 3478] Leelanivas, M., Aggarwal R., Editors, &quot;Graceful
Restart<br>
 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Mechanism for Label Distribution
Protocol&quot;, RFC 3478,<br>
 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; February 2003.<br>
<br>
 &nbsp; [RFC 3479] Farrel, A., &quot;Fault Tolerance for the Label<br>
 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Distribution Protocol (LDP)&quot;,
RFC 3479, February 2003.<br>
<br>
 &nbsp; [RFC 4447] Martini, L., Rosen, E., El-Aawar, N., Smith, T., Heron,
G.,<br>
 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Editors, &quot;Pseudowire Setup
and Maintenance Using the Label<br>
 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Distribution Protocol (LDP)&quot;,
RFC 4447, October 2008.<br>
<br>
 &nbsp; [RFC 4762] Lasserre, M., Kompella, V., Editors, &quot; Virtual
Private LAN<br>
 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Service (VPLS) Using Label Distribution
Protocol (LDP)<br>
 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Signaling&quot;, RFC 4762, January
2007.<br>
<br>
 &nbsp; [RFC 2119] Bradner, S., Editor, &quot;Key words for use in RFCs
to<br>
 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Indicate Requirement
Levels&quot;, BCP 14, RFC2119, March 1997.<br>
<br>
<br>
9.2. Informative References<br>
<br>
 &nbsp; [RFC 5254] Bitar, N., Bocci M., Martini, L., Editors, &quot;Requirements<br>
 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; for Multi-Segment Pseudowire
Emulation Edge-to-Edge (PWE3)&quot;,<br>
 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; RFC 5254, October 2008.<br>
<br>
 &nbsp; [MS-PW_ARCH] Bocci M., Bryant, S., Editors, &quot;An Architecture
for<br>
 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Multi-Segment Pseudowire Emulation
Edge-to-Edge&quot; draft-<br>
 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; ietf-pwe3-ms-pw-arch-06.txt,
Work in Progress, February<br>
 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2009.<br>
<br>
 &nbsp; [DYNAMIC MS-PW] Martini, L., Bocci M., Balus, F., Editors, &quot;Dynamic<br>
 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Placement of Multi Segment Pseudo
Wires&quot; draft-ietf-pwe3-<br>
 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; dynamic-ms-pw-09, Work in Progress,
February 2009.<br>
<br>
 &nbsp; [SEGMENTED PW] Martini, L., Metz, C., Nadeau, T., Bocci M., Balus,<br>
 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; F., Aissaoui, M., Duckett, M.,
Editors, &quot;Segmented<br>
 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Pseudowire&quot; draft-ietf-pwe3-segmented-pw-11.txt,
Work in<br>
 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Progress, February 2009.<br>
<br>
 &nbsp; [LDP_CAPABILITY] Thomas, B., Aggarwal, S., Aggarwal, R., Le Roux,<br>
 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; J.L., Syed Kamran Raza, Editors,
&nbsp;&quot;LDP Capabilities&quot; draft-<br>
 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; ietf-mpls-ldp-capabilities-04.txt,
Work in Progress, April<br>
 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2009.<br>
<br>
10. Acknowledgments<br>
<br>
 &nbsp; This document was prepared using 2-Word-v2.0.template.dot.<br>
</tt></font><br><pre>
--------------------------------------------------------
ZTE&nbsp;Information&nbsp;Security&nbsp;Notice:&nbsp;The&nbsp;information&nbsp;contained&nbsp;in&nbsp;this&nbsp;mail&nbsp;is&nbsp;solely&nbsp;property&nbsp;of&nbsp;the&nbsp;sender's&nbsp;organization.&nbsp;This&nbsp;mail&nbsp;communication&nbsp;is&nbsp;confidential.&nbsp;Recipients&nbsp;named&nbsp;above&nbsp;are&nbsp;obligated&nbsp;to&nbsp;maintain&nbsp;secrecy&nbsp;and&nbsp;are&nbsp;not&nbsp;permitted&nbsp;to&nbsp;disclose&nbsp;the&nbsp;contents&nbsp;of&nbsp;this&nbsp;communication&nbsp;to&nbsp;others.
This&nbsp;email&nbsp;and&nbsp;any&nbsp;files&nbsp;transmitted&nbsp;with&nbsp;it&nbsp;are&nbsp;confidential&nbsp;and&nbsp;intended&nbsp;solely&nbsp;for&nbsp;the&nbsp;use&nbsp;of&nbsp;the&nbsp;individual&nbsp;or&nbsp;entity&nbsp;to&nbsp;whom&nbsp;they&nbsp;are&nbsp;addressed.&nbsp;If&nbsp;you&nbsp;have&nbsp;received&nbsp;this&nbsp;email&nbsp;in&nbsp;error&nbsp;please&nbsp;notify&nbsp;the&nbsp;originator&nbsp;of&nbsp;the&nbsp;message.&nbsp;Any&nbsp;views&nbsp;expressed&nbsp;in&nbsp;this&nbsp;message&nbsp;are&nbsp;those&nbsp;of&nbsp;the&nbsp;individual&nbsp;sender.
This&nbsp;message&nbsp;has&nbsp;been&nbsp;scanned&nbsp;for&nbsp;viruses&nbsp;and&nbsp;Spam&nbsp;by&nbsp;ZTE&nbsp;Anti-Spam&nbsp;system.
</pre>
--=_alternative 003F0DEF482575DF_=--


From prvs=42417507c=euddasi@redback.com  Mon Jun 29 06:28:47 2009
Return-Path: <prvs=42417507c=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 473203A6999 for <pwe3@core3.amsl.com>; Mon, 29 Jun 2009 06:28:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.412
X-Spam-Level: 
X-Spam-Status: No, score=-2.412 tagged_above=-999 required=5 tests=[AWL=0.187,  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 2YtWTFpckx3h for <pwe3@core3.amsl.com>; Mon, 29 Jun 2009 06:28:45 -0700 (PDT)
Received: from mgate.redback.com (mgate.redback.com [155.53.3.41]) by core3.amsl.com (Postfix) with ESMTP id 7C0FF3A67B3 for <pwe3@ietf.org>; Mon, 29 Jun 2009 06:28:44 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.42,309,1243839600";  d="scan'208";a="2908554"
Received: from prattle.redback.com ([155.53.12.9]) by mgate.redback.com with ESMTP; 29 Jun 2009 06:28:15 -0700
Received: from localhost (localhost [127.0.0.1]) by prattle.redback.com (Postfix) with ESMTP id B4D3F404A6F for <pwe3@ietf.org>; Mon, 29 Jun 2009 06:28:15 -0700 (PDT)
Received: from prattle.redback.com ([127.0.0.1]) by localhost (prattle [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 12544-09 for <pwe3@ietf.org>; Mon, 29 Jun 2009 06:28:15 -0700 (PDT)
Received: from rbsjx.ad.redback.com (rbsjxh1.redback.com [155.53.14.105]) by prattle.redback.com (Postfix) with ESMTP id A49E6404A6D for <pwe3@ietf.org>; Mon, 29 Jun 2009 06:28:15 -0700 (PDT)
Received: from RBSJX.ad.redback.com ([155.53.14.103]) by rbsjxh1.ad.redback.com ([155.53.14.105]) with mapi; Mon, 29 Jun 2009 06:28:15 -0700
From: David Sinicrope <euddasi@redback.com>
To: "pwe3@ietf.org" <pwe3@ietf.org>
Date: Mon, 29 Jun 2009 06:28:13 -0700
Thread-Topic: Time slots for IETF 75 PWE3 meeting
Thread-Index: AcmO1f4o4AcNXYD1F0eyztRRXFz+YBkfWd+XAVqDghE=
Message-ID: <C66E39AD.2ACF1%euddasi@redback.com>
In-Reply-To: <C6652443.29D8B%euddasi@redback.com>
Accept-Language: en-US
Content-Language: en
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [PWE3] Time slots for IETF 75 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: <http://www.ietf.org/mail-archive/web/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, 29 Jun 2009 13:33:17 -0000

Hi All,
Below are the requests for time slots I have received to date.  If you woul=
d
like a time slot for the PWE3 meeting during IETF 75, please send me the
desired duration, topic/title, and presenter for each draft.  The initial
IETF agenda had conflicts with PWE3 and MPLS as well as PWE3 meeting on
Friday.  Matthew and Stewart are working out the meeting dates and times
with the agenda folks.  As soon as firm dates and times are obtained, I'll
update the agenda with time slot durations.

- WG Status - Stewart Bryant and Matthew Bocci
- draft-ietf-pwe3-iccp-00.txt changes from previous version - Luca Martini
- draft-martini-pwe3-p2mp-pw-00.txt presentation and discussion - Luca
Martini
- draft-martini-pwe3-static-pw-status-00.txt forthcoming pw status for
static pws - Luca Martini
- draft-jiang-pwe3-ldp-gr-00.txt - Albert John


On 6/22/09 12:06 PM, "David Sinicrope" <euddasi@redback.com> wrote:

> Hi All,
> Please let me know if you would like a time slot for the PWE3 meeting dur=
ing
> IETF 75.
> I=B9ll need the desired duration, topic/title, and presenter for each req=
uest.
> Thanks!
> Dave=20


From loa@pi.nu  Mon Jun 29 06:37:53 2009
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 D442B3A6B6B; Mon, 29 Jun 2009 06:37:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.52
X-Spam-Level: 
X-Spam-Status: No, score=-2.52 tagged_above=-999 required=5 tests=[AWL=0.079,  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 P2s5owtx7RuC; Mon, 29 Jun 2009 06:37:53 -0700 (PDT)
Received: from mail.pi.nu (mail.pi.nu [194.71.127.148]) by core3.amsl.com (Postfix) with ESMTP id 0C2B03A6AF4; Mon, 29 Jun 2009 06:37:53 -0700 (PDT)
Received: from [192.168.0.100] (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@pi.nu) by mail.pi.nu (Postfix) with ESMTPSA id B8462D4048; Mon, 29 Jun 2009 15:37:35 +0200 (CEST)
Message-ID: <4A48C39D.7050609@pi.nu>
Date: Mon, 29 Jun 2009 15:37:33 +0200
From: Loa Andersson <loa@pi.nu>
User-Agent: Thunderbird 2.0.0.22 (Windows/20090605)
MIME-Version: 1.0
To: mpls@ietf.org, mpls-tp@ietf.org, ccamp@ietf.org, pwe3@ietf.org,  Ross Callon <rcallon@juniper.net>, Adrian Farrel <adrian@olddog.co.uk>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: [PWE3] WK Last Call on draft-ietf-mpls-tp-oam-requirements-02.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: <http://www.ietf.org/mail-archive/web/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, 29 Jun 2009 13:37:53 -0000

All,

This is to start a working group lat call on

draft-ietf-mpls-tp-oam-requirements-02.txt

that is is schedule to end July 17th.

We chosen to start this last call already now and prolong it
one week since we have a a parallel wg last call on the network
management requirements (ending July 10).

Please send comments to mpls-tp mailing list!

*I.e. do not simply do a reply all on this mail.*

/Loa


-- 


Loa Andersson

Sr Strategy and Standards Manager    phone:  +46 10 717 52 13
Ericsson ///                                 +46 767 72 92 13

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

From root@core3.amsl.com  Mon Jun 29 11:00:02 2009
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 5FFDB3A6B29; Mon, 29 Jun 2009 11:00:02 -0700 (PDT)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20090629180002.5FFDB3A6B29@core3.amsl.com>
Date: Mon, 29 Jun 2009 11:00:02 -0700 (PDT)
Cc: pwe3@ietf.org
Subject: [PWE3] I-D Action:draft-ietf-pwe3-mpls-transport-04.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: <http://www.ietf.org/mail-archive/web/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, 29 Jun 2009 18:00: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           : Application of Ethernet Pseudowires to MPLS Transport Networks
	Author(s)       : S. Bryant, et al.
	Filename        : draft-ietf-pwe3-mpls-transport-04.txt
	Pages           : 13
	Date            : 2009-06-29

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-04.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-04.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

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


--NextPart--

From loa@pi.nu  Tue Jun 30 07:20:18 2009
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 7A08B3A6975; Tue, 30 Jun 2009 07:20:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.68
X-Spam-Level: 
X-Spam-Status: No, score=-2.68 tagged_above=-999 required=5 tests=[AWL=-0.081,  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 ezcXLfYnu7Bv; Tue, 30 Jun 2009 07:20:17 -0700 (PDT)
Received: from mail.pi.nu (mail.pi.nu [194.71.127.148]) by core3.amsl.com (Postfix) with ESMTP id A352C3A6B07; Tue, 30 Jun 2009 07:20:17 -0700 (PDT)
Received: from [192.168.0.100] (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@pi.nu) by mail.pi.nu (Postfix) with ESMTPSA id B1F3FD4048; Tue, 30 Jun 2009 16:19:41 +0200 (CEST)
Message-ID: <4A4A1EFA.6040101@pi.nu>
Date: Tue, 30 Jun 2009 16:19:38 +0200
From: Loa Andersson <loa@pi.nu>
User-Agent: Thunderbird 2.0.0.22 (Windows/20090605)
MIME-Version: 1.0
To: mpls@ietf.org, mpls-tp@ietf.org, ccamp@ietf.org, pwe3@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: [PWE3] poll to make draft-andersson-mpls-tp-process-03.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: <http://www.ietf.org/mail-archive/web/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, 30 Jun 2009 14:20:18 -0000

All,

we have an individual draft, draft-andersson-mpls-tp-process-03.txt,
that describes additions to the mpls working group process to allow
ITU-T to give input on MPLS-TP Internet Drafts.

It pretty much captures current practice, and from the start we had no
intention to ever progress, but recently there has been comments that
it would have a better and clearer sttus if it were a working group
document.

We have had no plans to ever make it an RFC, but it has been pointed
out that it would be possible to publish as an Historical RFC. Whether
we execute on that or not is not yet decided.

Therefore, is is to start at two week poll on making
draft-andersson-mpls-tp-process-03.txt an MPLS working group document.

The poll ends on July 14.

Please send your comments to the mpls-tp list.

Please





-- 


Loa Andersson

Sr Strategy and Standards Manager    phone:  +46 10 717 52 13
Ericsson ///                                 +46 767 72 92 13

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

From yljiang@huawei.com  Tue Jun 30 19:22:55 2009
Return-Path: <yljiang@huawei.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 66C353A6BFA; Tue, 30 Jun 2009 19:22:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.099
X-Spam-Level: 
X-Spam-Status: No, score=-0.099 tagged_above=-999 required=5 tests=[AWL=0.396,  BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553,  RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PQexr64nXn4J; Tue, 30 Jun 2009 19:22:54 -0700 (PDT)
Received: from szxga01-in.huawei.com (unknown [119.145.14.64]) by core3.amsl.com (Postfix) with ESMTP id 777903A6B96; Tue, 30 Jun 2009 19:22:54 -0700 (PDT)
Received: from huawei.com (szxga01-in [172.24.2.3]) by szxga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KM200DZCZY97R@szxga01-in.huawei.com>; Wed, 01 Jul 2009 10:22:57 +0800 (CST)
Received: from huawei.com ([172.24.1.24]) by szxga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KM20005MZY9U1@szxga01-in.huawei.com>; Wed, 01 Jul 2009 10:22:57 +0800 (CST)
Received: from j59929 ([10.70.40.52]) by szxml04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0KM2007J8ZY8MG@szxml04-in.huawei.com>; Wed, 01 Jul 2009 10:22:56 +0800 (CST)
Date: Wed, 01 Jul 2009 10:22:55 +0800
From: Jiang Yuan-long <yljiang@huawei.com>
To: Loa Andersson <loa@pi.nu>, mpls@ietf.org, mpls-tp@ietf.org, ccamp@ietf.org, pwe3@ietf.org, Ross Callon <rcallon@juniper.net>, Adrian Farrel <adrian@olddog.co.uk>
Message-id: <004201c9f9f2$d82428a0$3428460a@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
X-Mailer: Microsoft Outlook Express 6.00.2900.3138
Content-type: text/plain; format=flowed; charset=iso-8859-1; reply-type=response
Content-transfer-encoding: 7BIT
X-Priority: 3
X-MSMail-priority: Normal
References: <4A48C39D.7050609@pi.nu>
Subject: Re: [PWE3] [mpls-tp] WK Last Call on draft-ietf-mpls-tp-oam-requirements-02.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: <http://www.ietf.org/mail-archive/web/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, 01 Jul 2009 02:22:55 -0000

Hi all,
In draft-ietf-mpls-tp-oam-requirements-02.txt,
1. In section 2.1.3, two requirements are presented, the first says:
  "...IP routing and forwarding capabilities are inherently present in
  the forwarding  plane..."
the second says:
  "...IP routing and forwarding capabilities may not necessarily be
  present in the user plane. In this case, it MUST be possible to
  operate the OAM functions without relying on IP routing and
  forwarding capabilities..."
AFAIS, user plane is only used for user traffic forwarding, so no IP 
capabilities in user
plane does not necessarily preclude OAM (which is logically different from 
user traffic) with IP.
Therefore, "user plane" should be replaced with the same "forwarding plane", 
IMO.

2. In section 2.1.4, it says:
"...It is also REQUIRED that
   the two first requirements of Section 2.1.3 still hold..."
Maybe "first" should be deleted?

   Thanks
Jiang Yuanlong


----- Original Message ----- 
From: "Loa Andersson" <loa@pi.nu>
To: <mpls@ietf.org>; <mpls-tp@ietf.org>; <ccamp@ietf.org>; <pwe3@ietf.org>; 
"Ross Callon" <rcallon@juniper.net>; "Adrian Farrel" <adrian@olddog.co.uk>
Sent: Monday, June 29, 2009 9:37 PM
Subject: [mpls-tp] WK Last Call on 
draft-ietf-mpls-tp-oam-requirements-02.txt


> All,
>
> This is to start a working group lat call on
>
> draft-ietf-mpls-tp-oam-requirements-02.txt
>
> that is is schedule to end July 17th.
>
> We chosen to start this last call already now and prolong it
> one week since we have a a parallel wg last call on the network
> management requirements (ending July 10).
>
> Please send comments to mpls-tp mailing list!
>
> *I.e. do not simply do a reply all on this mail.*
>
> /Loa
>
>
> -- 
>
>
> Loa Andersson
>
> Sr Strategy and Standards Manager    phone:  +46 10 717 52 13
> Ericsson ///                                 +46 767 72 92 13
>
>                                      email:  loa.andersson@ericsson.com
>                                              loa@pi.nu
> _______________________________________________
> mpls-tp mailing list
> mpls-tp@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls-tp 

