
From internet-drafts@ietf.org  Mon Dec  2 04:47:32 2013
Return-Path: <internet-drafts@ietf.org>
X-Original-To: pwe3@ietfa.amsl.com
Delivered-To: pwe3@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 80BED1AE47D; Mon,  2 Dec 2013 04:47:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id r4GoYTUMG_Hx; Mon,  2 Dec 2013 04:47:31 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 2D2091AE343; Mon,  2 Dec 2013 04:47:31 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 4.83.p1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20131202124730.16744.64556.idtracker@ietfa.amsl.com>
Date: Mon, 02 Dec 2013 04:47:30 -0800
Cc: pwe3@ietf.org
Subject: [PWE3] I-D Action: draft-ietf-pwe3-dynamic-ms-pw-20.txt
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.15
List-Id: Pseudowire Emulation Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 02 Dec 2013 12:47:32 -0000

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

	Title           : Dynamic Placement of Multi-Segment Pseudowires
	Author(s)       : Luca Martini
                          Matthew Bocci
                          Florin Balus
	Filename        : draft-ietf-pwe3-dynamic-ms-pw-20.txt
	Pages           : 23
	Date            : 2013-12-02

Abstract:
   RFC5254 describes the service provider requirements for extending the
   reach of pseudowires (PW) across multiple Packet Switched Network
   domains. A Multi-Segment PW is defined as a set of two or more
   contiguous PW segments that behave and function as a single point-
   to-point PW. This document describes extensions to the PW control
   protocol to dynamically place the segments of the multi-segment
   pseudowire among a set of Provider Edge (PE) routers. This document
   also updates RFC6073 as follows: it updates the
    value of the length field of the PW Switching Point PE Sub-TLV Type
   0x06 to 14.




The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-pwe3-dynamic-ms-pw

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-pwe3-dynamic-ms-pw-20

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-pwe3-dynamic-ms-pw-20


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

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


From agmalis@gmail.com  Mon Dec  2 11:51:23 2013
Return-Path: <agmalis@gmail.com>
X-Original-To: pwe3@ietfa.amsl.com
Delivered-To: pwe3@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7C19B1AC4A7 for <pwe3@ietfa.amsl.com>; Mon,  2 Dec 2013 11:51:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5kvOsztkdgzf for <pwe3@ietfa.amsl.com>; Mon,  2 Dec 2013 11:51:21 -0800 (PST)
Received: from mail-wg0-x236.google.com (mail-wg0-x236.google.com [IPv6:2a00:1450:400c:c00::236]) by ietfa.amsl.com (Postfix) with ESMTP id 773061AD986 for <pwe3@ietf.org>; Mon,  2 Dec 2013 11:51:21 -0800 (PST)
Received: by mail-wg0-f54.google.com with SMTP id n12so11216982wgh.21 for <pwe3@ietf.org>; Mon, 02 Dec 2013 11:51:18 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; bh=/6dCJIKrDJ0sCeAQWRwlY30+Okk88YwmUR7r1U9xFs0=; b=iPEqfUUKLoV/JPP/6AJlOvbHWRGIgrSPZzD2eedaUL+6P5BpsGFtlqr//NLoNOC/FX v6wExzoPQgO/ebtKlzy7E6v02MsGErmBwLoRF8huEcfmtk6v0UWyc4Br5X67d2vzZFS0 r/IjDnP9Aqv4PuBi69jTzQO1HigEYBjDsClXlbUsJ/yV+0M3iQo8aZP0j7sfWGetwiuH wKDenfIZGZm2LC2nnxMo05S+6QPfBj+8uuj+rLgJVk1hgrzg0jzLDfcTqVZERpWKw42f 6/Et6Qo+qlPvQ9ToPkwMwjFylk83/WXuedrTDjio8dL2VeEev3ksC9jyJMeuGp+x7/7B AuDw==
X-Received: by 10.180.87.130 with SMTP id ay2mr8770672wib.60.1386013878471; Mon, 02 Dec 2013 11:51:18 -0800 (PST)
MIME-Version: 1.0
Received: by 10.216.127.68 with HTTP; Mon, 2 Dec 2013 11:50:58 -0800 (PST)
In-Reply-To: <20131202191607.7758.4326.idtracker@ietfa.amsl.com>
References: <20131202191607.7758.4326.idtracker@ietfa.amsl.com>
From: "Andrew G. Malis" <agmalis@gmail.com>
Date: Mon, 2 Dec 2013 14:50:58 -0500
Message-ID: <CAA=duU1B4L3zwBUG08-yBO-_Xcdv3R1RZKkJcU334a7Z87EhKA@mail.gmail.com>
To: "pwe3@ietf.org" <pwe3@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1
Subject: [PWE3] Fwd: New Liaison Statement, "Response to Liaison statement on clarifying Point to Multi Point (P2MP) combinations (to IETF PWE3 and MPLS WGs)"
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Pseudowire Emulation Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 02 Dec 2013 19:51:23 -0000

For some reason, this went to pwe3-request rather than pwe3@ietf.org.
Apologies if you're receiving it twice.

Cheers,
Andy

---------- Forwarded message ----------
From: Liaison Statement Management Tool <lsmt@ietf.org>
Date: Mon, Dec 2, 2013 at 2:16 PM
Subject: New Liaison Statement, "Response to Liaison statement on
clarifying Point to Multi Point (P2MP) combinations (to IETF PWE3 and
MPLS WGs)"
To: sshew@ciena.com
Cc: Andrew Malis <agmalis@gmail.com>, Stewart Bryant
<stbryant@cisco.com>, Adrian Farrel <adrian@olddog.co.uk>, Pseudowire
Emulation Edge to Edge Discussion List <pwe3-request@ietf.org>,
swallow@cisco.com, rcallon@juniper.net, jdrake@juniper.net,
Scott.Mansfield@ericsson.com, tsbsg15@itu.int, db3546@att.com,
mpls@ietf.org, matthew.bocci@alcatel-lucent.com


Title: Response to Liaison statement on clarifying Point to Multi
Point (P2MP) combinations (to IETF PWE3 and MPLS WGs)
Submission Date: 2013-11-27
URL of the IETF Web page: http://datatracker.ietf.org/liaison/1295/

From: Pseudowire Emulation Edge to Edge (Matthew Bocci
<matthew.bocci@alcatel-lucent.com>)
To: ITU-T SG15 Q10, Q12 (sshew@ciena.com)
Cc: Andrew Malis <agmalis@gmail.com>,Stewart Bryant
<stbryant@cisco.com>,Adrian Farrel <adrian@olddog.co.uk>,Pseudowire
Emulation Edge to Edge Discussion List
<pwe3-request@ietf.org>,swallow@cisco.com,rcallon@juniper.net,jdrake@juniper.net,Scott.Mansfield@Ericsson.com,tsbsg15@itu.int,db3546@att.com,mpls@ietf.org
Reponse Contact: matthew.bocci@alcatel-lucent.com
Technical Contact: matthew.bocci@alcatel-lucent.com
Purpose: In response
Referenced liaison: Liaison statement on clarifying Point to Multi
Point (P2MP) combinations (to IETF PWE3 and MPLS WGs)
(http://datatracker.ietf.org/liaison/1274/)
Body: Attachments:       (none)

Body:

Thank you for your liaison of July 2013 inquiring on the valid use of
p2mp pseudowires and LSPs. A new version of the Requirements and
Framework for Point-to-Multipoint Pseudowires over MPLS PSNs" is
available (see
http://www.ietf.org/id/draft-ietf-pwe3-p2mp-pw-requirements-06.txt)
that should help to clarify the points in your liaison.

Additionally, point-to-point PWs are not intended to be used in
conjunction with P2MP LSPs.  There is currently no way for the PEs
terminating all of the P2MP LSP leaves to establish the applicable
PW/FEC label mappings.  We do not believe that this case is supported
by the PWE3 architecture.  The only use case for P2MP PWs described in
the draft referenced above is when used with corresponding P2MP LSPs.
Other more complex use cases are for further study. If required,
participants are encouraged to bring extensions to this architecture
to the PWE3 working group.

Best regards,


Matthew Bocci
Andrew Malis

IETF PWE3 Working Group Chairs
Attachments:

No document has been attached

From martin.vigoureux@alcatel-lucent.com  Wed Dec  4 02:25:24 2013
Return-Path: <martin.vigoureux@alcatel-lucent.com>
X-Original-To: pwe3@ietfa.amsl.com
Delivered-To: pwe3@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0EB0A1AE0E6 for <pwe3@ietfa.amsl.com>; Wed,  4 Dec 2013 02:25:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.9
X-Spam-Level: 
X-Spam-Status: No, score=-6.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NSGrVp2ugxFw for <pwe3@ietfa.amsl.com>; Wed,  4 Dec 2013 02:25:21 -0800 (PST)
Received: from ihemail3.lucent.com (ihemail3.lucent.com [135.245.0.37]) by ietfa.amsl.com (Postfix) with ESMTP id EC1081AE093 for <pwe3@ietf.org>; Wed,  4 Dec 2013 02:25:20 -0800 (PST)
Received: from fr711usmtp1.zeu.alcatel-lucent.com (h135-239-2-122.lucent.com [135.239.2.122]) by ihemail3.lucent.com (8.13.8/IER-o) with ESMTP id rB4APCbo008398 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Wed, 4 Dec 2013 04:25:14 -0600 (CST)
Received: from FR711WXCHHUB01.zeu.alcatel-lucent.com (fr711wxchhub01.zeu.alcatel-lucent.com [135.239.2.111]) by fr711usmtp1.zeu.alcatel-lucent.com (GMO) with ESMTP id rB4APC4C010243 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 4 Dec 2013 11:25:12 +0100
Received: from [172.27.205.188] (135.239.27.41) by FR711WXCHHUB01.zeu.alcatel-lucent.com (135.239.2.111) with Microsoft SMTP Server (TLS) id 14.2.247.3; Wed, 4 Dec 2013 11:25:12 +0100
Message-ID: <529F0307.4090008@alcatel-lucent.com>
Date: Wed, 4 Dec 2013 11:25:11 +0100
From: Martin Vigoureux <martin.vigoureux@alcatel-lucent.com>
Organization: Alcatel-Lucent
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130307 Thunderbird/17.0.4
MIME-Version: 1.0
To: "Andrew G. Malis" <amalis@gmail.com>
References: <CAK+d4xsvbGWT5MRLHV-0TbwpxSxwLvJHR+mx7qGaPGaWyVGe5w@mail.gmail.com>
In-Reply-To: <CAK+d4xsvbGWT5MRLHV-0TbwpxSxwLvJHR+mx7qGaPGaWyVGe5w@mail.gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 8bit
X-Originating-IP: [135.239.27.41]
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.37
Cc: "pwe3@ietf.org" <pwe3@ietf.org>
Subject: Re: [PWE3] Second WG last call (and IPR call) for draft-ietf-pwe3-p2mp-pw-requirements
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Pseudowire Emulation Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 04 Dec 2013 10:25:24 -0000

Andy,

I am not aware of any undisclosed IPR that applies to this draft.

-m

Le 28/10/2013 18:56, Andrew G. Malis a écrit :
> PWE3ers,
>
> You may recall that almost exactly two years ago, we sent
> draft-ietf-pwe3-p2mp-pw-requirements-05 to the IESG. It was sent back to
> the WG in February of 2012, and it took a while, but we now have that
> rewrite to submit back to the IESG.
>
> However, because of the length of time, and the fact that -06 just came
> out about a week ago (so few people have had a chance to re-read it), we
> are going to have a second WG last call before sending it back to the IESG.
>
> So please review the draft, which you can find at
> https://tools.ietf.org/html/draft-ietf-pwe3-p2mp-pw-requirements-06 . If
> you would like to see what's changed, you can easily see that here:
> https://tools.ietf.org/rfcdiff?url2=draft-ietf-pwe3-p2mp-pw-requirements-06.txt
> .
>
> Coincidentally, we are also polling for knowledge of IPR that
> applies to this draft to ensure that IPR has been disclosed in
> compliance with IETF IPR rules (see RFCs 3979, 4879, 3669 and 5378
> for more details). To date, there have been no IPR declarations on this
> draft.
>
> If you are listed as a document author or contributor please respond
> to this email whether or not you are aware of any additional IPR. The
> draft will not be forwarded to the IESG until a response has been
> received from each author and contributor. See the list of contributing
> authors in Section 8 to refresh your memory.
>
> If you are on the PWE3 WG email list but are not listed as an author
> or contributor, then please explicitly respond only if you are aware
> of any IPR that has not yet been disclosed in conformance with IETF
> rules.
>
> Also, if you are listed as an author or contributor and your address
> info has changed, please email back privately so that we can get that
> updated before submitting it to the IESG.
>
> Because this last call spans the IETF meeting, it will be open for three
> weeks, ending on November 18.
>
> Thanks,
> Andy
>
>
>
> _______________________________________________
> pwe3 mailing list
> pwe3@ietf.org
> https://www.ietf.org/mailman/listinfo/pwe3
>

From agmalis@gmail.com  Wed Dec  4 12:53:28 2013
Return-Path: <agmalis@gmail.com>
X-Original-To: pwe3@ietfa.amsl.com
Delivered-To: pwe3@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D17551AE319 for <pwe3@ietfa.amsl.com>; Wed,  4 Dec 2013 12:53:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4X-lPgmGRanD for <pwe3@ietfa.amsl.com>; Wed,  4 Dec 2013 12:53:27 -0800 (PST)
Received: from mail-we0-x231.google.com (mail-we0-x231.google.com [IPv6:2a00:1450:400c:c03::231]) by ietfa.amsl.com (Postfix) with ESMTP id C08E41AE30A for <pwe3@ietf.org>; Wed,  4 Dec 2013 12:53:26 -0800 (PST)
Received: by mail-we0-f177.google.com with SMTP id p61so15242870wes.8 for <pwe3@ietf.org>; Wed, 04 Dec 2013 12:53:23 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:from:date:message-id:subject:to:content-type; bh=zS+LyXntRJvJuDjUCwKj0WEksBvTska7dUp7b1i5KoA=; b=DAI69oa8xIcRFIPZIhzSHQoJwd44Vzh0ajKtYa2l8FjN+Fh5ds33qo/CaRjq9PpX5x TGa2CPgfVtm22vhQ518vdswAffFil06Y4rvlZQgLG8Rdzun+wtFxKXHiJbReQNXf76JV STO/ZFloFsj3tK4uZuVC+4CTLqOH/2jpL/M1aHk02x817qy/ZRDgMapZeh3gfYqFIqq1 3R0kWRIOqalRU6VWRuAEHyktn0CvtXhCbC/RKjVurKr9NLzykzg9yygrqCc6YrljtR81 R52vpmZK7fbzpzc/9KgkoH/7xunyb32uuPOIT9qidsql+EGRSL4EsFxQSdxdHqIw8ni5 xI6g==
X-Received: by 10.194.21.225 with SMTP id y1mr14115110wje.60.1386190403108; Wed, 04 Dec 2013 12:53:23 -0800 (PST)
MIME-Version: 1.0
Received: by 10.216.127.68 with HTTP; Wed, 4 Dec 2013 12:53:02 -0800 (PST)
From: "Andrew G. Malis" <agmalis@gmail.com>
Date: Wed, 4 Dec 2013 15:53:02 -0500
Message-ID: <CAA=duU1X6SWzxNOVdXJHA4TsxnVf6u4jGO=0MaoYkc-661XWDw@mail.gmail.com>
To: "pwe3@ietf.org" <pwe3@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1
Subject: [PWE3] Poll for WG adoption and IPR check of draft-zhang-pwe3-iccp-stp-00
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Pseudowire Emulation Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 04 Dec 2013 20:53:29 -0000

This email begins a two week poll to help the chairs determine if
there is consensus to adopt draft-zhang-pwe3-iccp-stp-00 as an PWE3
working group draft.

The draft can be found here:
http://tools.ietf.org/html/draft-zhang-pwe3-iccp-stp-00

Please read the draft and indicate to the list if you support
adoption, or if you do not support adoption (giving reasons).

Please note that this is only a call for adoption. There needs to be
consensus that this draft is a good basis for the work, but it does
not need to be perfect at this stage.

Coincidentally, we are also polling for knowledge of any IPR that
applies to this draft, to ensure that IPR has been disclosed in
compliance with IETF IPR rules (see RFCs 3979, 4879, 3669 and 5378 for
more details).

If you are listed as a document author or contributor please respond
to this email whether or not you are aware of any relevant IPR. The
draft will not be adopted until a response has been received from each
author and contributor.

If you are on the PWE3 WG email list but are not listed as an author
or contributor, then please explicitly respond regarding IPR only if
you are aware of any IPR that has not yet been disclosed in
conformance with IETF rules.

The poll for adoption will close in two weeks time, on Wednesday 18th December.

Best regards,
Andy

From gregory.mirsky@ericsson.com  Wed Dec  4 13:59:37 2013
Return-Path: <gregory.mirsky@ericsson.com>
X-Original-To: pwe3@ietfa.amsl.com
Delivered-To: pwe3@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B83801ADF55 for <pwe3@ietfa.amsl.com>; Wed,  4 Dec 2013 13:59:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 68gOcLijoT-j for <pwe3@ietfa.amsl.com>; Wed,  4 Dec 2013 13:59:24 -0800 (PST)
Received: from usevmg20.ericsson.net (usevmg20.ericsson.net [198.24.6.45]) by ietfa.amsl.com (Postfix) with ESMTP id F15AC1AD8F5 for <pwe3@ietf.org>; Wed,  4 Dec 2013 13:59:22 -0800 (PST)
X-AuditID: c618062d-b7f278e000005a8f-d5-529fa5b3286c
Received: from EUSAAHC005.ericsson.se (Unknown_Domain [147.117.188.87]) by usevmg20.ericsson.net (Symantec Mail Security) with SMTP id F1.6A.23183.3B5AF925; Wed,  4 Dec 2013 22:59:16 +0100 (CET)
Received: from EUSAAMB103.ericsson.se ([147.117.188.120]) by EUSAAHC005.ericsson.se ([147.117.188.87]) with mapi id 14.02.0347.000; Wed, 4 Dec 2013 16:59:12 -0500
From: Gregory Mirsky <gregory.mirsky@ericsson.com>
To: "Andrew G. Malis" <agmalis@gmail.com>, "pwe3@ietf.org" <pwe3@ietf.org>
Thread-Topic: [PWE3] Poll for WG adoption and IPR check of draft-zhang-pwe3-iccp-stp-00
Thread-Index: AQHO8TLl2Y/vcsEkEkCZkiV4WHcmSppElETg
Date: Wed, 4 Dec 2013 21:59:11 +0000
Message-ID: <7347100B5761DC41A166AC17F22DF1121B723A1F@eusaamb103.ericsson.se>
References: <CAA=duU1X6SWzxNOVdXJHA4TsxnVf6u4jGO=0MaoYkc-661XWDw@mail.gmail.com>
In-Reply-To: <CAA=duU1X6SWzxNOVdXJHA4TsxnVf6u4jGO=0MaoYkc-661XWDw@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [147.117.188.135]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrALMWRmVeSWpSXmKPExsUyuXRPuO6WpfODDG4+FrY4/fwUm0Xfpy0s DkweO2fdZfdYsuQnUwBTFJdNSmpOZllqkb5dAlfG5WP7mAq6BCqe/j7B3MD4j6eLkZNDQsBE 4tmxhWwQtpjEhXvrgWwuDiGBI4wSTfMPsEM4yxglPr7qYwWpYhMwknixsYcdxBYR8JLYeHMh mC0sECHx8MR1Roh4pMSRi7OgbCOJe7vPMnUxcnCwCKhIbL0rDWLyCvhKLPpSD1IhJBAgcejt WbBqToFAid+7G8EmMgLd8/3UGiYQm1lAXOLWk/lMEHcKSCzZc54ZwhaVePn4HyuErSzxfc4j Foh6HYkFuz+xQdjaEssWvgar5xUQlDg58wnLBEbRWUjGzkLSMgtJyywkLQsYWVYxcpQWp5bl phsZbGIExsIxCTbdHYx7XloeYpTmYFES5/3y1jlISCA9sSQ1OzW1ILUovqg0J7X4ECMTB6dU A2PEW88l5x7w3Ltx4pmP5Gbjquq2gEVTSu8Ke8fcMFZ5xOUgeTGtjNEkJ71W7ZLo7I/tWzMP H7+9aOnSu+YZB2Krkx9Pvlg9s0BX9Jr2uTcfphprdXfquwkWn3hv0cQVXnfGwLFg8svJl/d3 X9s41bUoeEPAznSz9O++X2Yf5Lq4nYPhxur4c21KLMUZiYZazEXFiQBoJt88UwIAAA==
Subject: Re: [PWE3] Poll for WG adoption and IPR check of	draft-zhang-pwe3-iccp-stp-00
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Pseudowire Emulation Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 04 Dec 2013 21:59:38 -0000

Hi,
I think that the proposal would benefit from stronger description of use ca=
se(s) that it intended to address. At this time, the topology presented in =
Fig.2.1 can be supported with what already is defined in draft-ietf-pwe3-ic=
cp-12. Hence,
no/do not support

	Regards,
		Greg

-----Original Message-----
From: pwe3 [mailto:pwe3-bounces@ietf.org] On Behalf Of Andrew G. Malis
Sent: Wednesday, December 04, 2013 12:53 PM
To: pwe3@ietf.org
Subject: [PWE3] Poll for WG adoption and IPR check of draft-zhang-pwe3-iccp=
-stp-00

This email begins a two week poll to help the chairs determine if there is =
consensus to adopt draft-zhang-pwe3-iccp-stp-00 as an PWE3 working group dr=
aft.

The draft can be found here:
http://tools.ietf.org/html/draft-zhang-pwe3-iccp-stp-00

Please read the draft and indicate to the list if you support adoption, or =
if you do not support adoption (giving reasons).

Please note that this is only a call for adoption. There needs to be consen=
sus that this draft is a good basis for the work, but it does not need to b=
e perfect at this stage.

Coincidentally, we are also polling for knowledge of any IPR that applies t=
o this draft, to ensure that IPR has been disclosed in compliance with IETF=
 IPR rules (see RFCs 3979, 4879, 3669 and 5378 for more details).

If you are listed as a document author or contributor please respond to thi=
s email whether or not you are aware of any relevant IPR. The draft will no=
t be adopted until a response has been received from each author and contri=
butor.

If you are on the PWE3 WG email list but are not listed as an author or con=
tributor, then please explicitly respond regarding IPR only if you are awar=
e of any IPR that has not yet been disclosed in conformance with IETF rules=
.

The poll for adoption will close in two weeks time, on Wednesday 18th Decem=
ber.

Best regards,
Andy
_______________________________________________
pwe3 mailing list
pwe3@ietf.org
https://www.ietf.org/mailman/listinfo/pwe3

From zhangmingui@huawei.com  Wed Dec  4 18:26:28 2013
Return-Path: <zhangmingui@huawei.com>
X-Original-To: pwe3@ietfa.amsl.com
Delivered-To: pwe3@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AE0231AE042 for <pwe3@ietfa.amsl.com>; Wed,  4 Dec 2013 18:26:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.202
X-Spam-Level: 
X-Spam-Status: No, score=-4.202 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dXENwaoLe0PO for <pwe3@ietfa.amsl.com>; Wed,  4 Dec 2013 18:26:26 -0800 (PST)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 6D6711ADEAE for <pwe3@ietf.org>; Wed,  4 Dec 2013 18:26:26 -0800 (PST)
Received: from 172.18.7.190 (EHLO lhreml203-edg.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BBA39254; Thu, 05 Dec 2013 02:26:22 +0000 (GMT)
Received: from LHREML406-HUB.china.huawei.com (10.201.5.243) by lhreml203-edg.huawei.com (172.18.7.221) with Microsoft SMTP Server (TLS) id 14.3.158.1; Thu, 5 Dec 2013 02:25:28 +0000
Received: from nkgeml407-hub.china.huawei.com (10.98.56.38) by lhreml406-hub.china.huawei.com (10.201.5.243) with Microsoft SMTP Server (TLS) id 14.3.158.1; Thu, 5 Dec 2013 02:26:22 +0000
Received: from NKGEML508-MBX.china.huawei.com ([169.254.7.180]) by nkgeml407-hub.china.huawei.com ([10.98.56.38]) with mapi id 14.03.0158.001; Thu, 5 Dec 2013 10:26:14 +0800
From: Mingui Zhang <zhangmingui@huawei.com>
To: "Andrew G. Malis" <agmalis@gmail.com>, "pwe3@ietf.org" <pwe3@ietf.org>
Thread-Topic: [PWE3] Poll for WG adoption and IPR check of draft-zhang-pwe3-iccp-stp-00
Thread-Index: AQHO8TLn49fI/S0E2UKJI6ivtPFP7JpE382A
Date: Thu, 5 Dec 2013 02:26:13 +0000
Message-ID: <4552F0907735844E9204A62BBDD325E73368DB3B@nkgeml508-mbx.china.huawei.com>
References: <CAA=duU1X6SWzxNOVdXJHA4TsxnVf6u4jGO=0MaoYkc-661XWDw@mail.gmail.com>
In-Reply-To: <CAA=duU1X6SWzxNOVdXJHA4TsxnVf6u4jGO=0MaoYkc-661XWDw@mail.gmail.com>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.111.102.175]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Subject: Re: [PWE3] Poll for WG adoption and IPR check of	draft-zhang-pwe3-iccp-stp-00
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Pseudowire Emulation Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 05 Dec 2013 02:26:28 -0000

I am not aware of any IPR in this draft.

Thanks,
Mingui

>-----Original Message-----
>From: pwe3 [mailto:pwe3-bounces@ietf.org] On Behalf Of Andrew G. Malis
>Sent: Thursday, December 05, 2013 4:53 AM
>To: pwe3@ietf.org
>Subject: [PWE3] Poll for WG adoption and IPR check of
>draft-zhang-pwe3-iccp-stp-00
>
>This email begins a two week poll to help the chairs determine if there is
>consensus to adopt draft-zhang-pwe3-iccp-stp-00 as an PWE3 working group
>draft.
>
>The draft can be found here:
>http://tools.ietf.org/html/draft-zhang-pwe3-iccp-stp-00
>
>Please read the draft and indicate to the list if you support adoption, or=
 if you do
>not support adoption (giving reasons).
>
>Please note that this is only a call for adoption. There needs to be conse=
nsus
>that this draft is a good basis for the work, but it does not need to be p=
erfect at
>this stage.
>
>Coincidentally, we are also polling for knowledge of any IPR that applies =
to this
>draft, to ensure that IPR has been disclosed in compliance with IETF IPR r=
ules
>(see RFCs 3979, 4879, 3669 and 5378 for more details).
>
>If you are listed as a document author or contributor please respond to th=
is
>email whether or not you are aware of any relevant IPR. The draft will not=
 be
>adopted until a response has been received from each author and contributo=
r.
>
>If you are on the PWE3 WG email list but are not listed as an author or
>contributor, then please explicitly respond regarding IPR only if you are =
aware of
>any IPR that has not yet been disclosed in conformance with IETF rules.
>
>The poll for adoption will close in two weeks time, on Wednesday 18th
>December.
>
>Best regards,
>Andy
>_______________________________________________
>pwe3 mailing list
>pwe3@ietf.org
>https://www.ietf.org/mailman/listinfo/pwe3

From wenhuafeng@huawei.com  Wed Dec  4 20:01:29 2013
Return-Path: <wenhuafeng@huawei.com>
X-Original-To: pwe3@ietfa.amsl.com
Delivered-To: pwe3@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D07FB1AE031 for <pwe3@ietfa.amsl.com>; Wed,  4 Dec 2013 20:01:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.748
X-Spam-Level: *
X-Spam-Status: No, score=1.748 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, CHARSET_FARAWAY_HEADER=3.2, MIME_8BIT_HEADER=0.3, MIME_CHARSET_FARAWAY=2.45, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Kci8O6YubwrA for <pwe3@ietfa.amsl.com>; Wed,  4 Dec 2013 20:01:27 -0800 (PST)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 4C9031ADFC1 for <pwe3@ietf.org>; Wed,  4 Dec 2013 20:01:27 -0800 (PST)
Received: from 172.18.7.190 (EHLO lhreml203-edg.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BBA46162; Thu, 05 Dec 2013 04:01:23 +0000 (GMT)
Received: from LHREML406-HUB.china.huawei.com (10.201.5.243) by lhreml203-edg.huawei.com (172.18.7.221) with Microsoft SMTP Server (TLS) id 14.3.158.1; Thu, 5 Dec 2013 04:00:22 +0000
Received: from NKGEML406-HUB.china.huawei.com (10.98.56.37) by lhreml406-hub.china.huawei.com (10.201.5.243) with Microsoft SMTP Server (TLS) id 14.3.158.1; Thu, 5 Dec 2013 04:01:15 +0000
Received: from NKGEML503-MBS.china.huawei.com ([169.254.6.87]) by nkgeml406-hub.china.huawei.com ([10.98.56.37]) with mapi id 14.03.0158.001; Thu, 5 Dec 2013 12:01:08 +0800
From: Wenhuafeng <wenhuafeng@huawei.com>
To: "Andrew G. Malis" <agmalis@gmail.com>, "pwe3@ietf.org" <pwe3@ietf.org>
Thread-Topic: [PWE3] Poll for WG adoption and IPR check of draft-zhang-pwe3-iccp-stp-00
Thread-Index: AQHO8TLngVxE2kKdTUeWUqO+kYgZm5pE+nQh
Date: Thu, 5 Dec 2013 04:01:08 +0000
Message-ID: <B51493B1D374244F9572F031F74684294FDCD5B7@nkgeml503-mbs.china.huawei.com>
References: <CAA=duU1X6SWzxNOVdXJHA4TsxnVf6u4jGO=0MaoYkc-661XWDw@mail.gmail.com>
In-Reply-To: <CAA=duU1X6SWzxNOVdXJHA4TsxnVf6u4jGO=0MaoYkc-661XWDw@mail.gmail.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.135.30.158]
Content-Type: text/plain; charset="gb2312"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Subject: [PWE3] =?gb2312?b?tPC4tDogIFBvbGwgZm9yIFdHIGFkb3B0aW9uIGFuZCBJ?= =?gb2312?b?UFIgY2hlY2sgb2YJZHJhZnQtemhhbmctcHdlMy1pY2NwLXN0cC0wMA==?=
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Pseudowire Emulation Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 05 Dec 2013 04:01:30 -0000

SSBhbSBub3QgYXdhcmUgb2YgYW55IElQUiB0aGF0IGlzIHJlbGV2YW50IHRvIHRoaXMgZHJhZnQu
CgpUaGFua3MsCkh1YWZlbmcgCgpfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fCreivP7IyzogcHdlMyBbcHdlMy1ib3VuY2VzQGlldGYub3JnXSC0+rHtIEFuZHJldyBHLiBN
YWxpcyBbYWdtYWxpc0BnbWFpbC5jb21dCreiy83KsbzkOiAyMDEzxOoxMtTCNcjVIDQ6NTMKytW8
/sjLOiBwd2UzQGlldGYub3JnCtb3zOI6IFtQV0UzXSBQb2xsIGZvciBXRyBhZG9wdGlvbiBhbmQg
SVBSIGNoZWNrIG9mICAgICAgICBkcmFmdC16aGFuZy1wd2UzLWljY3Atc3RwLTAwCgpUaGlzIGVt
YWlsIGJlZ2lucyBhIHR3byB3ZWVrIHBvbGwgdG8gaGVscCB0aGUgY2hhaXJzIGRldGVybWluZSBp
Zgp0aGVyZSBpcyBjb25zZW5zdXMgdG8gYWRvcHQgZHJhZnQtemhhbmctcHdlMy1pY2NwLXN0cC0w
MCBhcyBhbiBQV0UzCndvcmtpbmcgZ3JvdXAgZHJhZnQuCgpUaGUgZHJhZnQgY2FuIGJlIGZvdW5k
IGhlcmU6Cmh0dHA6Ly90b29scy5pZXRmLm9yZy9odG1sL2RyYWZ0LXpoYW5nLXB3ZTMtaWNjcC1z
dHAtMDAKClBsZWFzZSByZWFkIHRoZSBkcmFmdCBhbmQgaW5kaWNhdGUgdG8gdGhlIGxpc3QgaWYg
eW91IHN1cHBvcnQKYWRvcHRpb24sIG9yIGlmIHlvdSBkbyBub3Qgc3VwcG9ydCBhZG9wdGlvbiAo
Z2l2aW5nIHJlYXNvbnMpLgoKUGxlYXNlIG5vdGUgdGhhdCB0aGlzIGlzIG9ubHkgYSBjYWxsIGZv
ciBhZG9wdGlvbi4gVGhlcmUgbmVlZHMgdG8gYmUKY29uc2Vuc3VzIHRoYXQgdGhpcyBkcmFmdCBp
cyBhIGdvb2QgYmFzaXMgZm9yIHRoZSB3b3JrLCBidXQgaXQgZG9lcwpub3QgbmVlZCB0byBiZSBw
ZXJmZWN0IGF0IHRoaXMgc3RhZ2UuCgpDb2luY2lkZW50YWxseSwgd2UgYXJlIGFsc28gcG9sbGlu
ZyBmb3Iga25vd2xlZGdlIG9mIGFueSBJUFIgdGhhdAphcHBsaWVzIHRvIHRoaXMgZHJhZnQsIHRv
IGVuc3VyZSB0aGF0IElQUiBoYXMgYmVlbiBkaXNjbG9zZWQgaW4KY29tcGxpYW5jZSB3aXRoIElF
VEYgSVBSIHJ1bGVzIChzZWUgUkZDcyAzOTc5LCA0ODc5LCAzNjY5IGFuZCA1Mzc4IGZvcgptb3Jl
IGRldGFpbHMpLgoKSWYgeW91IGFyZSBsaXN0ZWQgYXMgYSBkb2N1bWVudCBhdXRob3Igb3IgY29u
dHJpYnV0b3IgcGxlYXNlIHJlc3BvbmQKdG8gdGhpcyBlbWFpbCB3aGV0aGVyIG9yIG5vdCB5b3Ug
YXJlIGF3YXJlIG9mIGFueSByZWxldmFudCBJUFIuIFRoZQpkcmFmdCB3aWxsIG5vdCBiZSBhZG9w
dGVkIHVudGlsIGEgcmVzcG9uc2UgaGFzIGJlZW4gcmVjZWl2ZWQgZnJvbSBlYWNoCmF1dGhvciBh
bmQgY29udHJpYnV0b3IuCgpJZiB5b3UgYXJlIG9uIHRoZSBQV0UzIFdHIGVtYWlsIGxpc3QgYnV0
IGFyZSBub3QgbGlzdGVkIGFzIGFuIGF1dGhvcgpvciBjb250cmlidXRvciwgdGhlbiBwbGVhc2Ug
ZXhwbGljaXRseSByZXNwb25kIHJlZ2FyZGluZyBJUFIgb25seSBpZgp5b3UgYXJlIGF3YXJlIG9m
IGFueSBJUFIgdGhhdCBoYXMgbm90IHlldCBiZWVuIGRpc2Nsb3NlZCBpbgpjb25mb3JtYW5jZSB3
aXRoIElFVEYgcnVsZXMuCgpUaGUgcG9sbCBmb3IgYWRvcHRpb24gd2lsbCBjbG9zZSBpbiB0d28g
d2Vla3MgdGltZSwgb24gV2VkbmVzZGF5IDE4dGggRGVjZW1iZXIuCgpCZXN0IHJlZ2FyZHMsCkFu
ZHkKX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KcHdlMyBt
YWlsaW5nIGxpc3QKcHdlM0BpZXRmLm9yZwpodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xp
c3RpbmZvL3B3ZTMK

From zhangmingui@huawei.com  Thu Dec  5 16:46:04 2013
Return-Path: <zhangmingui@huawei.com>
X-Original-To: pwe3@ietfa.amsl.com
Delivered-To: pwe3@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3168D1AE236 for <pwe3@ietfa.amsl.com>; Thu,  5 Dec 2013 16:46:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.202
X-Spam-Level: 
X-Spam-Status: No, score=-4.202 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LvILD6XJGczP for <pwe3@ietfa.amsl.com>; Thu,  5 Dec 2013 16:46:02 -0800 (PST)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id A2DCF1AE23A for <pwe3@ietf.org>; Thu,  5 Dec 2013 16:46:01 -0800 (PST)
Received: from 172.18.7.190 (EHLO lhreml204-edg.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id AYR18273; Fri, 06 Dec 2013 00:45:56 +0000 (GMT)
Received: from LHREML403-HUB.china.huawei.com (10.201.5.217) by lhreml204-edg.china.huawei.com (172.18.7.223) with Microsoft SMTP Server (TLS) id 14.3.158.1; Fri, 6 Dec 2013 00:45:03 +0000
Received: from NKGEML406-HUB.china.huawei.com (10.98.56.37) by lhreml403-hub.china.huawei.com (10.201.5.217) with Microsoft SMTP Server (TLS) id 14.3.158.1; Fri, 6 Dec 2013 00:45:54 +0000
Received: from NKGEML508-MBX.china.huawei.com ([169.254.7.180]) by nkgeml406-hub.china.huawei.com ([10.98.56.37]) with mapi id 14.03.0158.001; Fri, 6 Dec 2013 08:45:47 +0800
From: Mingui Zhang <zhangmingui@huawei.com>
To: Gregory Mirsky <gregory.mirsky@ericsson.com>, "Andrew G. Malis" <agmalis@gmail.com>, "pwe3@ietf.org" <pwe3@ietf.org>
Thread-Topic: [PWE3] Poll for WG adoption and IPR check	of draft-zhang-pwe3-iccp-stp-00
Thread-Index: AQHO8TwlCkXQzt/PFEWJQ1M2OraNH5pExIrA
Date: Fri, 6 Dec 2013 00:45:46 +0000
Message-ID: <4552F0907735844E9204A62BBDD325E73368ED8E@nkgeml508-mbx.china.huawei.com>
References: <CAA=duU1X6SWzxNOVdXJHA4TsxnVf6u4jGO=0MaoYkc-661XWDw@mail.gmail.com> <7347100B5761DC41A166AC17F22DF1121B723A1F@eusaamb103.ericsson.se>
In-Reply-To: <7347100B5761DC41A166AC17F22DF1121B723A1F@eusaamb103.ericsson.se>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.111.102.175]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Subject: Re: [PWE3] Poll for WG adoption and IPR check	of	draft-zhang-pwe3-iccp-stp-00
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Pseudowire Emulation Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 06 Dec 2013 00:46:04 -0000

Hi Greg,

Thanks for attention. This solution is designed for the use case that geo-d=
ispersed DSLAMs running STP need enhance the reliability of the connections=
 between the entire STP network and the carrier network.

Want to address several key points here: 1. These DSLAMs are running STP. 2=
. These DSLAMs are not geo-close to each other. Multiple DSLAMs are connect=
ed to the carrier network at different locations. 3. When one connection to=
 the carrier network fails, customers wish a connection in another location=
 can continue to work after the re-convergence of the STP rather than compr=
omising the whole STP network. The failure of the connection may be due to =
the failure of the PE, the AC or even the CE (a DSLAM) itself. 4. Customers=
 want to balance the load among those connections, therefore all these conn=
ections need be active.=20

Please note that the draft is not proposed to replace anything. I agree wit=
h you that the application "can be supported". That's why we want to introd=
uce the proposal into the ICCP draft as an _additional_ application. Curren=
tly, there are two applications in the ICCP draft, PW-RED and mLACP. These =
two applications are not applicable to above use case to meet the requireme=
nts of customers.=20

If I misunderstood anything, please correct me.

--
Mingui

>-----Original Message-----
>From: pwe3 [mailto:pwe3-bounces@ietf.org] On Behalf Of Gregory Mirsky
>Sent: Thursday, December 05, 2013 5:59 AM
>To: Andrew G. Malis; pwe3@ietf.org
>Subject: Re: [PWE3] Poll for WG adoption and IPR check of
>draft-zhang-pwe3-iccp-stp-00
>
>Hi,
>I think that the proposal would benefit from stronger description of use c=
ase(s)
>that it intended to address. At this time, the topology presented in Fig.2=
.1 can
>be supported with what already is defined in draft-ietf-pwe3-iccp-12. Henc=
e,
>no/do not support
>
>	Regards,
>		Greg
>
>-----Original Message-----
>From: pwe3 [mailto:pwe3-bounces@ietf.org] On Behalf Of Andrew G. Malis
>Sent: Wednesday, December 04, 2013 12:53 PM
>To: pwe3@ietf.org
>Subject: [PWE3] Poll for WG adoption and IPR check of
>draft-zhang-pwe3-iccp-stp-00
>
>This email begins a two week poll to help the chairs determine if there is
>consensus to adopt draft-zhang-pwe3-iccp-stp-00 as an PWE3 working group
>draft.
>
>The draft can be found here:
>http://tools.ietf.org/html/draft-zhang-pwe3-iccp-stp-00
>
>Please read the draft and indicate to the list if you support adoption, or=
 if you do
>not support adoption (giving reasons).
>
>Please note that this is only a call for adoption. There needs to be conse=
nsus
>that this draft is a good basis for the work, but it does not need to be p=
erfect at
>this stage.
>
>Coincidentally, we are also polling for knowledge of any IPR that applies =
to this
>draft, to ensure that IPR has been disclosed in compliance with IETF IPR r=
ules
>(see RFCs 3979, 4879, 3669 and 5378 for more details).
>
>If you are listed as a document author or contributor please respond to th=
is
>email whether or not you are aware of any relevant IPR. The draft will not=
 be
>adopted until a response has been received from each author and contributo=
r.
>
>If you are on the PWE3 WG email list but are not listed as an author or
>contributor, then please explicitly respond regarding IPR only if you are =
aware of
>any IPR that has not yet been disclosed in conformance with IETF rules.
>
>The poll for adoption will close in two weeks time, on Wednesday 18th
>December.
>
>Best regards,
>Andy
>_______________________________________________
>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 wenhuafeng@huawei.com  Fri Dec  6 02:03:19 2013
Return-Path: <wenhuafeng@huawei.com>
X-Original-To: pwe3@ietfa.amsl.com
Delivered-To: pwe3@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2373A1AE315 for <pwe3@ietfa.amsl.com>; Fri,  6 Dec 2013 02:03:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.202
X-Spam-Level: 
X-Spam-Status: No, score=-4.202 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dYCEMga2HutD for <pwe3@ietfa.amsl.com>; Fri,  6 Dec 2013 02:03:16 -0800 (PST)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 1EF271ADC03 for <pwe3@ietf.org>; Fri,  6 Dec 2013 02:03:15 -0800 (PST)
Received: from 172.18.7.190 (EHLO lhreml204-edg.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id AYR56608; Fri, 06 Dec 2013 10:03:11 +0000 (GMT)
Received: from LHREML404-HUB.china.huawei.com (10.201.5.218) by lhreml204-edg.china.huawei.com (172.18.7.223) with Microsoft SMTP Server (TLS) id 14.3.158.1; Fri, 6 Dec 2013 10:02:17 +0000
Received: from NKGEML406-HUB.china.huawei.com (10.98.56.37) by lhreml404-hub.china.huawei.com (10.201.5.218) with Microsoft SMTP Server (TLS) id 14.3.158.1; Fri, 6 Dec 2013 10:03:08 +0000
Received: from NKGEML503-MBS.china.huawei.com ([169.254.6.87]) by nkgeml406-hub.china.huawei.com ([10.98.56.37]) with mapi id 14.03.0158.001; Fri, 6 Dec 2013 18:02:58 +0800
From: Wenhuafeng <wenhuafeng@huawei.com>
To: Mingui Zhang <zhangmingui@huawei.com>, Gregory Mirsky <gregory.mirsky@ericsson.com>, "Andrew G. Malis" <agmalis@gmail.com>, "pwe3@ietf.org" <pwe3@ietf.org>
Thread-Topic: [PWE3] Poll for WG adoption and IPR	check	of draft-zhang-pwe3-iccp-stp-00
Thread-Index: AQHO8h6LX9GJpW77HESMawVPYjy+fZpG7+bs
Date: Fri, 6 Dec 2013 10:02:57 +0000
Message-ID: <B51493B1D374244F9572F031F74684294FDCD678@nkgeml503-mbs.china.huawei.com>
References: <CAA=duU1X6SWzxNOVdXJHA4TsxnVf6u4jGO=0MaoYkc-661XWDw@mail.gmail.com> <7347100B5761DC41A166AC17F22DF1121B723A1F@eusaamb103.ericsson.se>, <4552F0907735844E9204A62BBDD325E73368ED8E@nkgeml508-mbx.china.huawei.com>
In-Reply-To: <4552F0907735844E9204A62BBDD325E73368ED8E@nkgeml508-mbx.china.huawei.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.135.30.158]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Subject: Re: [PWE3] Poll for WG adoption and IPR	check	of	draft-zhang-pwe3-iccp-stp-00
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Pseudowire Emulation Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 06 Dec 2013 10:03:19 -0000

VGhlIHVzZSBjYXNlIGlzIHZhbGlkLsKgClN1cHBvcnQgZm9yIGFkb3B0aW9uIGFzIGEgY29hdXRo
b3IuCgpSZWdhcmRzLApIdWFmZW5nIAoKX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fXwrlj5Hku7bkuro6IHB3ZTMgW3B3ZTMtYm91bmNlc0BpZXRmLm9yZ10g5Luj6KGoIE1p
bmd1aSBaaGFuZyBbemhhbmdtaW5ndWlAaHVhd2VpLmNvbV0K5Y+R6YCB5pe26Ze0OiAyMDEz5bm0
MTLmnIg25pelIDg6NDUK5pS25Lu25Lq6OiBHcmVnb3J5IE1pcnNreTsgQW5kcmV3IEcuIE1hbGlz
OyBwd2UzQGlldGYub3JnCuS4u+mimDogUmU6IFtQV0UzXSBQb2xsIGZvciBXRyBhZG9wdGlvbiBh
bmQgSVBSICAgICBjaGVjayAgIG9mICAgICAgZHJhZnQtemhhbmctcHdlMy1pY2NwLXN0cC0wMAoK
SGkgR3JlZywKClRoYW5rcyBmb3IgYXR0ZW50aW9uLiBUaGlzIHNvbHV0aW9uIGlzIGRlc2lnbmVk
IGZvciB0aGUgdXNlIGNhc2UgdGhhdCBnZW8tZGlzcGVyc2VkIERTTEFNcyBydW5uaW5nIFNUUCBu
ZWVkIGVuaGFuY2UgdGhlIHJlbGlhYmlsaXR5IG9mIHRoZSBjb25uZWN0aW9ucyBiZXR3ZWVuIHRo
ZSBlbnRpcmUgU1RQIG5ldHdvcmsgYW5kIHRoZSBjYXJyaWVyIG5ldHdvcmsuCgpXYW50IHRvIGFk
ZHJlc3Mgc2V2ZXJhbCBrZXkgcG9pbnRzIGhlcmU6IDEuIFRoZXNlIERTTEFNcyBhcmUgcnVubmlu
ZyBTVFAuIDIuIFRoZXNlIERTTEFNcyBhcmUgbm90IGdlby1jbG9zZSB0byBlYWNoIG90aGVyLiBN
dWx0aXBsZSBEU0xBTXMgYXJlIGNvbm5lY3RlZCB0byB0aGUgY2FycmllciBuZXR3b3JrIGF0IGRp
ZmZlcmVudCBsb2NhdGlvbnMuIDMuIFdoZW4gb25lIGNvbm5lY3Rpb24gdG8gdGhlIGNhcnJpZXIg
bmV0d29yayBmYWlscywgY3VzdG9tZXJzIHdpc2ggYSBjb25uZWN0aW9uIGluIGFub3RoZXIgbG9j
YXRpb24gY2FuIGNvbnRpbnVlIHRvIHdvcmsgYWZ0ZXIgdGhlIHJlLWNvbnZlcmdlbmNlIG9mIHRo
ZSBTVFAgcmF0aGVyIHRoYW4gY29tcHJvbWlzaW5nIHRoZSB3aG9sZSBTVFAgbmV0d29yay4gVGhl
IGZhaWx1cmUgb2YgdGhlIGNvbm5lY3Rpb24gbWF5IGJlIGR1ZSB0byB0aGUgZmFpbHVyZSBvZiB0
aGUgUEUsIHRoZSBBQyBvciBldmVuIHRoZSBDRSAoYSBEU0xBTSkgaXRzZWxmLiA0LiBDdXN0b21l
cnMgd2FudCB0byBiYWxhbmNlIHRoZSBsb2FkIGFtb25nIHRob3NlIGNvbm5lY3Rpb25zLCB0aGVy
ZWZvcmUgYWxsIHRoZXNlIGNvbm5lY3Rpb25zIG5lZWQgYmUgYWN0aXZlLgoKUGxlYXNlIG5vdGUg
dGhhdCB0aGUgZHJhZnQgaXMgbm90IHByb3Bvc2VkIHRvIHJlcGxhY2UgYW55dGhpbmcuIEkgYWdy
ZWUgd2l0aCB5b3UgdGhhdCB0aGUgYXBwbGljYXRpb24gImNhbiBiZSBzdXBwb3J0ZWQiLiBUaGF0
J3Mgd2h5IHdlIHdhbnQgdG8gaW50cm9kdWNlIHRoZSBwcm9wb3NhbCBpbnRvIHRoZSBJQ0NQIGRy
YWZ0IGFzIGFuIF9hZGRpdGlvbmFsXyBhcHBsaWNhdGlvbi4gQ3VycmVudGx5LCB0aGVyZSBhcmUg
dHdvIGFwcGxpY2F0aW9ucyBpbiB0aGUgSUNDUCBkcmFmdCwgUFctUkVEIGFuZCBtTEFDUC4gVGhl
c2UgdHdvIGFwcGxpY2F0aW9ucyBhcmUgbm90IGFwcGxpY2FibGUgdG8gYWJvdmUgdXNlIGNhc2Ug
dG8gbWVldCB0aGUgcmVxdWlyZW1lbnRzIG9mIGN1c3RvbWVycy4KCklmIEkgbWlzdW5kZXJzdG9v
ZCBhbnl0aGluZywgcGxlYXNlIGNvcnJlY3QgbWUuCgotLQpNaW5ndWkKCj4tLS0tLU9yaWdpbmFs
IE1lc3NhZ2UtLS0tLQo+RnJvbTogcHdlMyBbbWFpbHRvOnB3ZTMtYm91bmNlc0BpZXRmLm9yZ10g
T24gQmVoYWxmIE9mIEdyZWdvcnkgTWlyc2t5Cj5TZW50OiBUaHVyc2RheSwgRGVjZW1iZXIgMDUs
IDIwMTMgNTo1OSBBTQo+VG86IEFuZHJldyBHLiBNYWxpczsgcHdlM0BpZXRmLm9yZwo+U3ViamVj
dDogUmU6IFtQV0UzXSBQb2xsIGZvciBXRyBhZG9wdGlvbiBhbmQgSVBSIGNoZWNrIG9mCj5kcmFm
dC16aGFuZy1wd2UzLWljY3Atc3RwLTAwCj4KPkhpLAo+SSB0aGluayB0aGF0IHRoZSBwcm9wb3Nh
bCB3b3VsZCBiZW5lZml0IGZyb20gc3Ryb25nZXIgZGVzY3JpcHRpb24gb2YgdXNlIGNhc2UocykK
PnRoYXQgaXQgaW50ZW5kZWQgdG8gYWRkcmVzcy4gQXQgdGhpcyB0aW1lLCB0aGUgdG9wb2xvZ3kg
cHJlc2VudGVkIGluIEZpZy4yLjEgY2FuCj5iZSBzdXBwb3J0ZWQgd2l0aCB3aGF0IGFscmVhZHkg
aXMgZGVmaW5lZCBpbiBkcmFmdC1pZXRmLXB3ZTMtaWNjcC0xMi4gSGVuY2UsCj5uby9kbyBub3Qg
c3VwcG9ydAo+Cj4gICAgICAgUmVnYXJkcywKPiAgICAgICAgICAgICAgIEdyZWcKPgo+LS0tLS1P
cmlnaW5hbCBNZXNzYWdlLS0tLS0KPkZyb206IHB3ZTMgW21haWx0bzpwd2UzLWJvdW5jZXNAaWV0
Zi5vcmddIE9uIEJlaGFsZiBPZiBBbmRyZXcgRy4gTWFsaXMKPlNlbnQ6IFdlZG5lc2RheSwgRGVj
ZW1iZXIgMDQsIDIwMTMgMTI6NTMgUE0KPlRvOiBwd2UzQGlldGYub3JnCj5TdWJqZWN0OiBbUFdF
M10gUG9sbCBmb3IgV0cgYWRvcHRpb24gYW5kIElQUiBjaGVjayBvZgo+ZHJhZnQtemhhbmctcHdl
My1pY2NwLXN0cC0wMAo+Cj5UaGlzIGVtYWlsIGJlZ2lucyBhIHR3byB3ZWVrIHBvbGwgdG8gaGVs
cCB0aGUgY2hhaXJzIGRldGVybWluZSBpZiB0aGVyZSBpcwo+Y29uc2Vuc3VzIHRvIGFkb3B0IGRy
YWZ0LXpoYW5nLXB3ZTMtaWNjcC1zdHAtMDAgYXMgYW4gUFdFMyB3b3JraW5nIGdyb3VwCj5kcmFm
dC4KPgo+VGhlIGRyYWZ0IGNhbiBiZSBmb3VuZCBoZXJlOgo+aHR0cDovL3Rvb2xzLmlldGYub3Jn
L2h0bWwvZHJhZnQtemhhbmctcHdlMy1pY2NwLXN0cC0wMAo+Cj5QbGVhc2UgcmVhZCB0aGUgZHJh
ZnQgYW5kIGluZGljYXRlIHRvIHRoZSBsaXN0IGlmIHlvdSBzdXBwb3J0IGFkb3B0aW9uLCBvciBp
ZiB5b3UgZG8KPm5vdCBzdXBwb3J0IGFkb3B0aW9uIChnaXZpbmcgcmVhc29ucykuCj4KPlBsZWFz
ZSBub3RlIHRoYXQgdGhpcyBpcyBvbmx5IGEgY2FsbCBmb3IgYWRvcHRpb24uIFRoZXJlIG5lZWRz
IHRvIGJlIGNvbnNlbnN1cwo+dGhhdCB0aGlzIGRyYWZ0IGlzIGEgZ29vZCBiYXNpcyBmb3IgdGhl
IHdvcmssIGJ1dCBpdCBkb2VzIG5vdCBuZWVkIHRvIGJlIHBlcmZlY3QgYXQKPnRoaXMgc3RhZ2Uu
Cj4KPkNvaW5jaWRlbnRhbGx5LCB3ZSBhcmUgYWxzbyBwb2xsaW5nIGZvciBrbm93bGVkZ2Ugb2Yg
YW55IElQUiB0aGF0IGFwcGxpZXMgdG8gdGhpcwo+ZHJhZnQsIHRvIGVuc3VyZSB0aGF0IElQUiBo
YXMgYmVlbiBkaXNjbG9zZWQgaW4gY29tcGxpYW5jZSB3aXRoIElFVEYgSVBSIHJ1bGVzCj4oc2Vl
IFJGQ3MgMzk3OSwgNDg3OSwgMzY2OSBhbmQgNTM3OCBmb3IgbW9yZSBkZXRhaWxzKS4KPgo+SWYg
eW91IGFyZSBsaXN0ZWQgYXMgYSBkb2N1bWVudCBhdXRob3Igb3IgY29udHJpYnV0b3IgcGxlYXNl
IHJlc3BvbmQgdG8gdGhpcwo+ZW1haWwgd2hldGhlciBvciBub3QgeW91IGFyZSBhd2FyZSBvZiBh
bnkgcmVsZXZhbnQgSVBSLiBUaGUgZHJhZnQgd2lsbCBub3QgYmUKPmFkb3B0ZWQgdW50aWwgYSBy
ZXNwb25zZSBoYXMgYmVlbiByZWNlaXZlZCBmcm9tIGVhY2ggYXV0aG9yIGFuZCBjb250cmlidXRv
ci4KPgo+SWYgeW91IGFyZSBvbiB0aGUgUFdFMyBXRyBlbWFpbCBsaXN0IGJ1dCBhcmUgbm90IGxp
c3RlZCBhcyBhbiBhdXRob3Igb3IKPmNvbnRyaWJ1dG9yLCB0aGVuIHBsZWFzZSBleHBsaWNpdGx5
IHJlc3BvbmQgcmVnYXJkaW5nIElQUiBvbmx5IGlmIHlvdSBhcmUgYXdhcmUgb2YKPmFueSBJUFIg
dGhhdCBoYXMgbm90IHlldCBiZWVuIGRpc2Nsb3NlZCBpbiBjb25mb3JtYW5jZSB3aXRoIElFVEYg
cnVsZXMuCj4KPlRoZSBwb2xsIGZvciBhZG9wdGlvbiB3aWxsIGNsb3NlIGluIHR3byB3ZWVrcyB0
aW1lLCBvbiBXZWRuZXNkYXkgMTh0aAo+RGVjZW1iZXIuCj4KPkJlc3QgcmVnYXJkcywKPkFuZHkK
Pl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fCj5wd2UzIG1h
aWxpbmcgbGlzdAo+cHdlM0BpZXRmLm9yZwo+aHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9s
aXN0aW5mby9wd2UzCj5fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fXwo+cHdlMyBtYWlsaW5nIGxpc3QKPnB3ZTNAaWV0Zi5vcmcKPmh0dHBzOi8vd3d3LmlldGYu
b3JnL21haWxtYW4vbGlzdGluZm8vcHdlMwpfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fXwpwd2UzIG1haWxpbmcgbGlzdApwd2UzQGlldGYub3JnCmh0dHBzOi8v
d3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vcHdlMwo=

From yaakov_s@rad.com  Mon Dec  9 02:51:43 2013
Return-Path: <yaakov_s@rad.com>
X-Original-To: pwe3@ietfa.amsl.com
Delivered-To: pwe3@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DB8F01AE275 for <pwe3@ietfa.amsl.com>; Mon,  9 Dec 2013 02:51:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.59
X-Spam-Level: 
X-Spam-Status: No, score=-1.59 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HOST_MISMATCH_COM=0.311, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7dSCs-E55LIj for <pwe3@ietfa.amsl.com>; Mon,  9 Dec 2013 02:51:42 -0800 (PST)
Received: from rad.co.il (mailrelay01-ib2.rad.com [91.143.228.146]) by ietfa.amsl.com (Postfix) with ESMTP id 7EEB61ADEC4 for <pwe3@ietf.org>; Mon,  9 Dec 2013 02:51:41 -0800 (PST)
Received: from Internal Mail-Server by MailRelay01 (envelope-from yaakov?s@rad.com) with RC4-SHA encrypted SMTP; 9 Dec 2013 12:51:34 +0200
Received: from EXRAD6.ad.rad.co.il (2002:c072:18be::c072:18be) by exrad6.ad.rad.co.il (2002:c072:18be::c072:18be) with Microsoft SMTP Server (TLS) id 15.0.775.38; Mon, 9 Dec 2013 12:51:33 +0200
Received: from EXRAD6.ad.rad.co.il ([fe80::f157:6202:5fc8:a4f0]) by exrad6.ad.rad.co.il ([fe80::f157:6202:5fc8:a4f0%12]) with mapi id 15.00.0775.031; Mon, 9 Dec 2013 12:51:33 +0200
From: Yaakov Stein <yaakov_s@rad.com>
To: "Andrew G. Malis" <agmalis@gmail.com>, "pwe3@ietf.org" <pwe3@ietf.org>
Thread-Topic: [PWE3] Poll for WG adoption and IPR check of draft-zhang-pwe3-iccp-stp-00
Thread-Index: AQHO8TLoTJ6Y9wddH0iiXogySHCyvZpLtm5g
Date: Mon, 9 Dec 2013 10:51:32 +0000
Message-ID: <6e6993502ff243d29c52ed9047deed0e@exrad6.ad.rad.co.il>
References: <CAA=duU1X6SWzxNOVdXJHA4TsxnVf6u4jGO=0MaoYkc-661XWDw@mail.gmail.com>
In-Reply-To: <CAA=duU1X6SWzxNOVdXJHA4TsxnVf6u4jGO=0MaoYkc-661XWDw@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [94.188.160.12]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Commtouch-Refid: str=0001.0A0C0202.52A5A0B6.0080, ss=1, re=0.000, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0 (Unknown)
Subject: Re: [PWE3] Poll for WG adoption and IPR check of	draft-zhang-pwe3-iccp-stp-00
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Pseudowire Emulation Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 09 Dec 2013 10:51:44 -0000

I do not support adoption,
partly because I don't think PWE3 should be taking on any new work,
and partly because I don't think the use case is sufficiently interesting.

Y(J)S


-----Original Message-----
From: pwe3 [mailto:pwe3-bounces@ietf.org] On Behalf Of Andrew G. Malis
Sent: 04 December, 2013 22:53
To: pwe3@ietf.org
Subject: [PWE3] Poll for WG adoption and IPR check of draft-zhang-pwe3-iccp=
-stp-00

This email begins a two week poll to help the chairs determine if there is =
consensus to adopt draft-zhang-pwe3-iccp-stp-00 as an PWE3 working group dr=
aft.

The draft can be found here:
http://tools.ietf.org/html/draft-zhang-pwe3-iccp-stp-00

Please read the draft and indicate to the list if you support adoption, or =
if you do not support adoption (giving reasons).

Please note that this is only a call for adoption. There needs to be consen=
sus that this draft is a good basis for the work, but it does not need to b=
e perfect at this stage.

Coincidentally, we are also polling for knowledge of any IPR that applies t=
o this draft, to ensure that IPR has been disclosed in compliance with IETF=
 IPR rules (see RFCs 3979, 4879, 3669 and 5378 for more details).

If you are listed as a document author or contributor please respond to thi=
s email whether or not you are aware of any relevant IPR. The draft will no=
t be adopted until a response has been received from each author and contri=
butor.

If you are on the PWE3 WG email list but are not listed as an author or con=
tributor, then please explicitly respond regarding IPR only if you are awar=
e of any IPR that has not yet been disclosed in conformance with IETF rules=
.

The poll for adoption will close in two weeks time, on Wednesday 18th Decem=
ber.

Best regards,
Andy
_______________________________________________
pwe3 mailing list
pwe3@ietf.org
https://www.ietf.org/mailman/listinfo/pwe3

From amalis@gmail.com  Mon Dec  9 06:49:23 2013
Return-Path: <amalis@gmail.com>
X-Original-To: pwe3@ietfa.amsl.com
Delivered-To: pwe3@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 33E941AE2F4 for <pwe3@ietfa.amsl.com>; Mon,  9 Dec 2013 06:49:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.999
X-Spam-Level: 
X-Spam-Status: No, score=-101.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VKIDuYLqw0vS for <pwe3@ietfa.amsl.com>; Mon,  9 Dec 2013 06:49:19 -0800 (PST)
Received: from mail-ob0-x231.google.com (mail-ob0-x231.google.com [IPv6:2607:f8b0:4003:c01::231]) by ietfa.amsl.com (Postfix) with ESMTP id AF97D1AE2F3 for <pwe3@ietf.org>; Mon,  9 Dec 2013 06:49:19 -0800 (PST)
Received: by mail-ob0-f177.google.com with SMTP id va2so3784119obc.36 for <pwe3@ietf.org>; Mon, 09 Dec 2013 06:49:14 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=RAKbjgtefrGH8KtH9NZoMeYFNx5AmNMQYcBCnKYHPwQ=; b=oLP0H5HdW8R76Hx55eEkjxdnkKG1PEvt7VcQNydj7WPUOzGU1GaCsn6FN/E412kWGE 1MriCaUabyzFRNg5bQI+9ZzzglmCPMIa/xSu4ypsGjiS+M+Qqnbf1Q6rrwVG5Q+CtJYd +eBA0xip1tEBQPb6/3JBETB+Aop8+Qpa9RmSPk5DVyq/lwoGEOMpnD2YkT7amscQgDYE drsXligzBUcJxDQtyvjMPFZtPiOSUe7bsnnAiMwky3cPYfrGZzEhEAwPtZwv3iGFWNPW W3HYgQxaty9YCbk6ZWw12TDBGDORmNdWrMiCybsFf4ah3NP61vYZLc8F9kZ5FIH24Ws1 6XKQ==
X-Received: by 10.182.232.4 with SMTP id tk4mr13134507obc.9.1386600554728; Mon, 09 Dec 2013 06:49:14 -0800 (PST)
MIME-Version: 1.0
Received: by 10.76.182.9 with HTTP; Mon, 9 Dec 2013 06:48:54 -0800 (PST)
In-Reply-To: <CAK+d4xsvbGWT5MRLHV-0TbwpxSxwLvJHR+mx7qGaPGaWyVGe5w@mail.gmail.com>
References: <CAK+d4xsvbGWT5MRLHV-0TbwpxSxwLvJHR+mx7qGaPGaWyVGe5w@mail.gmail.com>
From: "Andrew G. Malis" <amalis@gmail.com>
Date: Mon, 9 Dec 2013 09:48:54 -0500
Message-ID: <CAK+d4xu=kKnEMBPbzSxgvD8bbtN4nHNqugo9DTNVWU6e9MgSZg@mail.gmail.com>
To: "pwe3@ietf.org" <pwe3@ietf.org>
Content-Type: multipart/alternative; boundary=f46d0445178f82971004ed1b19c9
Cc: Rahul Aggarwal <raggarwa_1@yahoo.com>
Subject: Re: [PWE3] Second WG last call (and IPR call) for draft-ietf-pwe3-p2mp-pw-requirements
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Pseudowire Emulation Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 09 Dec 2013 14:49:23 -0000

--f46d0445178f82971004ed1b19c9
Content-Type: text/plain; charset=ISO-8859-1

This ends the second WG last call for draft-ietf-pwe3-p2mp-pw-requirements,
with no comments received other than IPR confirmations from the authors. It
will be forwarded to the IESG for publication.

Thanks,
Andy


On Mon, Oct 28, 2013 at 1:56 PM, Andrew G. Malis <amalis@gmail.com> wrote:

> PWE3ers,
>
> You may recall that almost exactly two years ago, we sent
> draft-ietf-pwe3-p2mp-pw-requirements-05 to the IESG. It was sent back to
> the WG in February of 2012, and it took a while, but we now have that
> rewrite to submit back to the IESG.
>
> However, because of the length of time, and the fact that -06 just came
> out about a week ago (so few people have had a chance to re-read it), we
> are going to have a second WG last call before sending it back to the IESG.
>
> So please review the draft, which you can find at
> https://tools.ietf.org/html/draft-ietf-pwe3-p2mp-pw-requirements-06 . If
> you would like to see what's changed, you can easily see that here:
> https://tools.ietf.org/rfcdiff?url2=draft-ietf-pwe3-p2mp-pw-requirements-06.txt.
>
> Coincidentally, we are also polling for knowledge of IPR that
> applies to this draft to ensure that IPR has been disclosed in
> compliance with IETF IPR rules (see RFCs 3979, 4879, 3669 and 5378
> for more details). To date, there have been no IPR declarations on this
> draft.
>
> If you are listed as a document author or contributor please respond
> to this email whether or not you are aware of any additional IPR. The
> draft will not be forwarded to the IESG until a response has been
> received from each author and contributor. See the list of contributing
> authors in Section 8 to refresh your memory.
>
> If you are on the PWE3 WG email list but are not listed as an author
> or contributor, then please explicitly respond only if you are aware
> of any IPR that has not yet been disclosed in conformance with IETF
> rules.
>
> Also, if you are listed as an author or contributor and your address info
> has changed, please email back privately so that we can get that updated
> before submitting it to the IESG.
>
> Because this last call spans the IETF meeting, it will be open for three
> weeks, ending on November 18.
>
> Thanks,
> Andy
>
>

--f46d0445178f82971004ed1b19c9
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>This ends the second WG last call for <span class=3D"=
">draft</span>-<span class=3D"">ietf</span>-<span class=3D"">pwe3</span>-<s=
pan class=3D"">p2mp</span>-<span class=3D"">pw</span>-<span class=3D"">requ=
irements, with no comments received other than IPR confirmations from the a=
uthors. It will be forwarded to the IESG for publication.<br>

<br></span></div><span class=3D"">Thanks,<br>Andy<br></span></div><div clas=
s=3D"gmail_extra"><br><br><div class=3D"gmail_quote">On Mon, Oct 28, 2013 a=
t 1:56 PM, Andrew G. Malis <span dir=3D"ltr">&lt;<a href=3D"mailto:amalis@g=
mail.com" target=3D"_blank">amalis@gmail.com</a>&gt;</span> wrote:<br>

<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div dir=3D"ltr"><div><div><div><div>PWE3ers=
,<br><br></div>You may recall that almost exactly two years ago, we sent dr=
aft-ietf-pwe3-p2mp-pw-requirements-05 to the IESG. It was sent back to the =
WG in February of 2012, and it took a while, but we now have that rewrite t=
o submit back to the IESG.<br>


<br></div>However, because of the length of time, and the fact that -06 jus=
t came out about a week ago (so few people have had a chance to re-read it)=
, we are going to have a second WG last call before sending it back to the =
IESG.<br>


<br></div>So please review the draft, which you can find at <a href=3D"http=
s://tools.ietf.org/html/draft-ietf-pwe3-p2mp-pw-requirements-06" target=3D"=
_blank">https://tools.ietf.org/html/draft-ietf-pwe3-p2mp-pw-requirements-06=
</a> . If you would like to see what&#39;s changed, you can easily see that=
 here: <a href=3D"https://tools.ietf.org/rfcdiff?url2=3Ddraft-ietf-pwe3-p2m=
p-pw-requirements-06.txt" target=3D"_blank">https://tools.ietf.org/rfcdiff?=
url2=3Ddraft-ietf-pwe3-p2mp-pw-requirements-06.txt</a> .<br>


<br>Coincidentally, we are also polling for knowledge of IPR that<br>
applies to this draft to ensure that IPR has been disclosed in<br>
compliance with IETF IPR rules (see RFCs 3979, 4879, 3669 and 5378 <br>for =
more details). To date, there have been no IPR declarations on this<br>draf=
t.<br>
<br>
If you are listed as a document author or contributor please respond<br>
to this email whether or not you are aware of any additional IPR. The<br>
draft will not be forwarded to the IESG until a response has been<br>
received from each author and contributor. See the list of contributing<br>=
authors in Section 8 to refresh your memory.<br>
<br>
If you are on the <span>PWE3</span> <span>WG</span> email list but are not =
listed as an author<br>
or contributor, then please explicitly respond only if you are aware<br>
of any IPR that has not yet been disclosed in conformance with IETF<br>
rules.<br><br></div><div>Also, if you are listed as an author or contributo=
r and your address info has changed, please email back privately so that we=
 can get that updated before submitting it to the IESG.<br></div><div>


<br></div><div>Because this last call spans the IETF meeting, it will be op=
en for three weeks, ending on November 18.<br><br></div><div>Thanks,<br>And=
y<br><br></div></div>
</blockquote></div><br></div>

--f46d0445178f82971004ed1b19c9--

From d3e3e3@gmail.com  Tue Dec 10 12:56:38 2013
Return-Path: <d3e3e3@gmail.com>
X-Original-To: pwe3@ietfa.amsl.com
Delivered-To: pwe3@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C5BD21AE00C for <pwe3@ietfa.amsl.com>; Tue, 10 Dec 2013 12:56:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.75
X-Spam-Level: 
X-Spam-Status: No, score=-1.75 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gedpSQ_vLl5W for <pwe3@ietfa.amsl.com>; Tue, 10 Dec 2013 12:56:37 -0800 (PST)
Received: from mail-oa0-x234.google.com (mail-oa0-x234.google.com [IPv6:2607:f8b0:4003:c02::234]) by ietfa.amsl.com (Postfix) with ESMTP id 83AF61ADFF5 for <pwe3@ietf.org>; Tue, 10 Dec 2013 12:56:37 -0800 (PST)
Received: by mail-oa0-f52.google.com with SMTP id h16so6229185oag.39 for <pwe3@ietf.org>; Tue, 10 Dec 2013 12:56:32 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; bh=8yKqU8xdchtdzrmdrduPNlf4Y0PbNIo8jpMfMCTTVHY=; b=rzBi+LjXEeXhjpBDnCiN4SF161Kp6rYo93Olx/CifQuGW0t4h89Cm7jJWA6hXLFvfj RKnCd7BIQ2YPZB+2HkvgUsTlV34EEb2HcqFB21qnfciQKbRq+UqvuaLUwFpuG1dbSb5R e4TYQjlMtH3b7dkeNiUnjsQBaWgNozuaWoB5MEncmW1nWZgSiUcbwLr8flpTeM5HF4ca RvAL6ryDXsd2ZxV0zwQuAbPEOcEVIsCs1uIObkkggk4xNUuWyOVB9pH6mv6XUQ8B33/K 7ht10j+WmiKkOcOAU7KSfaFP+3+oiiaX+W8WzpEivBWI5xdSqWHdNMf+FpCMH3YGM1fq 7q/A==
X-Received: by 10.60.117.198 with SMTP id kg6mr1780135oeb.80.1386708992147; Tue, 10 Dec 2013 12:56:32 -0800 (PST)
MIME-Version: 1.0
Received: by 10.76.33.102 with HTTP; Tue, 10 Dec 2013 12:56:12 -0800 (PST)
In-Reply-To: <20131209231940.439.3411.idtracker@ietfa.amsl.com>
References: <20131209231940.439.3411.idtracker@ietfa.amsl.com>
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Tue, 10 Dec 2013 15:56:12 -0500
Message-ID: <CAF4+nEHdqC+UVF_Q-Q62AbxP-Paj47_=nNun2+3hE8PzZKBpyg@mail.gmail.com>
To: "pwe3@ietf.org" <pwe3@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1
Subject: [PWE3] Fwd: Last Call: <draft-ietf-trill-o-pw-03.txt> (Transport of TRILL Using Pseudowires) to Proposed Standard
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Pseudowire Emulation Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 10 Dec 2013 20:56:39 -0000

Hi,

The following IETF Last Call may be of interest to some PWE3 WG participants.

Thanks,
Donald
=============================
 Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
 155 Beaver Street, Milford, MA 01757 USA
 d3e3e3@gmail.com

---------- Forwarded message ----------
From: The IESG <iesg-secretary@ietf.org>
Date: Mon, Dec 9, 2013 at 6:19 PM
Subject: Last Call: <draft-ietf-trill-o-pw-03.txt> (Transport of TRILL
Using Pseudowires) to Proposed Standard
To: IETF-Announce <ietf-announce@ietf.org>
Cc: trill@ietf.org

The IESG has received a request from the Transparent Interconnection of
Lots of Links WG (trill) to consider the following document:
- 'Transport of TRILL Using Pseudowires'
  <draft-ietf-trill-o-pw-03.txt> as 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 2013-12-23. 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.

Abstract

   This document specifies how to interconnect a pair of TRILL
   (Transparent Interconnection of Lots of Links) switch ports using
   pseudowires under existing TRILL and PWE3 (Pseudowire Emulation End-
   to-End) standards.




The file can be obtained via
http://datatracker.ietf.org/doc/draft-ietf-trill-o-pw/

IESG discussion can be tracked via
http://datatracker.ietf.org/doc/draft-ietf-trill-o-pw/ballot/


No IPR declarations have been submitted directly on this I-D.

From Alexander.Vainshtein@ecitele.com  Tue Dec 10 22:05:33 2013
Return-Path: <Alexander.Vainshtein@ecitele.com>
X-Original-To: pwe3@ietfa.amsl.com
Delivered-To: pwe3@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 663B11AE392; Tue, 10 Dec 2013 22:05:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kUDT-vDZH-T6; Tue, 10 Dec 2013 22:05:30 -0800 (PST)
Received: from emea01-db3-obe.outbound.protection.outlook.com (mail-db3lp0080.outbound.protection.outlook.com [213.199.154.80]) by ietfa.amsl.com (Postfix) with ESMTP id 79C831AE390; Tue, 10 Dec 2013 22:05:29 -0800 (PST)
Received: from AM3PR03MB529.eurprd03.prod.outlook.com (10.242.109.153) by AM3PR03MB562.eurprd03.prod.outlook.com (10.242.111.147) with Microsoft SMTP Server (TLS) id 15.0.837.10; Wed, 11 Dec 2013 06:05:23 +0000
Received: from AM3PR03MB532.eurprd03.prod.outlook.com (10.242.109.156) by AM3PR03MB529.eurprd03.prod.outlook.com (10.242.109.153) with Microsoft SMTP Server (TLS) id 15.0.842.7; Wed, 11 Dec 2013 06:05:21 +0000
Received: from AM3PR03MB532.eurprd03.prod.outlook.com ([10.242.109.156]) by AM3PR03MB532.eurprd03.prod.outlook.com ([10.242.109.156]) with mapi id 15.00.0837.004; Wed, 11 Dec 2013 06:05:21 +0000
From: Alexander Vainshtein <Alexander.Vainshtein@ecitele.com>
To: "curtis@occnc.com" <curtis@occnc.com>
Thread-Topic: [PWE3] Pseudowire Sequence Number in draft-ietf-mpls-forwarding: a minor comment
Thread-Index: AQHO9b9GSq0tCZZscUehMpHq+OAdtZpOe00f
Date: Wed, 11 Dec 2013 06:05:20 +0000
Message-ID: <774d74926b684ffba7f4f89ace758547@AM3PR03MB532.eurprd03.prod.outlook.com>
References: Your message of "Tue, 26 Nov 2013 16:26:43 +0000." <F9336571731ADE42A5397FC831CEAA025AC56C9D@ILPTWPVEXMB02.ecitele.com>, <201312101547.rBAFl9Be033270@gateway1.ipv6.occnc.com>
In-Reply-To: <201312101547.rBAFl9Be033270@gateway1.ipv6.occnc.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [5.153.9.203]
x-forefront-prvs: 0057EE387C
x-forefront-antispam-report: SFV:NSPM; SFS:(10009001)(13464003)(53754006)(199002)(189002)(377454003)(52604005)(51704005)(76482001)(81342001)(81816001)(4396001)(33646001)(69226001)(81542001)(47736001)(47976001)(50986001)(76576001)(76786001)(47446002)(74502001)(74316001)(31966008)(74662001)(49866001)(71446004)(74366001)(56816005)(66066001)(90146001)(51856001)(85852003)(74706001)(63696002)(76796001)(85306002)(65816001)(80022001)(87266001)(87936001)(19580405001)(19580395003)(80976001)(2656002)(46102001)(83322001)(83072002)(59766001)(77982001)(54316002)(56776001)(79102001)(74876001)(81686001)(54356001)(53806001)(427584002)(24736002); DIR:OUT; SFP:1101; SCL:1; SRVR:AM3PR03MB529; H:AM3PR03MB532.eurprd03.prod.outlook.com; CLIP:5.153.9.203; FPR:; RD:InfoNoRecords; A:1; MX:1; LANG:en; 
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: ecitele.com
Cc: "samante@apple.com" <samante@apple.com>, "Yaakov Stein \(yaakov_s@rad.com\)" <yaakov_s@rad.com>, "cpignata@cisco.com" <cpignata@cisco.com>, "kireeti@juniper.net" <kireeti@juniper.net>, "mpls@ietf.org" <mpls@ietf.org>, "pwe3 \(pwe3@ietf.org\)" <pwe3@ietf.org>
Subject: Re: [PWE3] Pseudowire Sequence Number in draft-ietf-mpls-forwarding: a minor comment
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Pseudowire Emulation Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 11 Dec 2013 06:05:33 -0000

Curtis,=0A=
Lots of thanks for sending out the new text.=0A=
=0A=
I still have a couple of issues with this version of the text: one technica=
l and one editorial.=0A=
=0A=
The technical issue is about the fragment "A small jitter buffer is always =
necessary". =0A=
=0A=
I am not sure this is correct, since I am aware of several PW implementatio=
ns that pass the payload of a received PW packet directly for transmission =
via the corresdponding attachment circuit. Of course this payload would be =
stored in some Tx queue associated with the attachment circuit and controll=
ed by the appropriate egress scheduler, but IMO this does not constitue a P=
W jitter bufer, since the PW interworking function does not exersize any co=
ntrol over these queues.=0A=
In particular, these queues could not be used for re-ordering misordered PW=
 packets.=0A=
IMHO and FWIW this understanding matches RFC 3985 which mentions (in Sectio=
n 5.2.1.1 "Frame Ordering") that reodering as the strategy for handling mis=
-ordered packets introduces additional delay (i.e., requires a ddicated jit=
ter buffer), while the alternative strategy of discarding mis-ordered packe=
ts does not introduce such additional delay.=0A=
=0A=
The editorial issue is about the entire sentence that contains the above-me=
ntioned fragment, i.e., "A small jitter buffer is always necessary and the =
jitter buffer is needed regardless of whether reordering is done" - to me t=
his looks like an unnecessary repetition if if it were techically correct.=
=0A=
=0A=
Hence I would like to suggest discrading the problematic sentence as the si=
mplest way to resolve both issues.=0A=
=0A=
Hopefully these notes will e helpful.=0A=
=0A=
Regards,=0A=
     Sasha=0A=
=0A=
=0A=
________________________________________=0A=
From: Curtis Villamizar <curtis@occnc.com>=0A=
Sent: Tuesday, December 10, 2013 5:47 PM=0A=
To: Alexander Vainshtein=0A=
Cc: curtis@ipv6.occnc.com; curtis@occnc.com; kireeti@juniper.net; samante@a=
pple.com; agmalis@gmail.com; cpignata@cisco.com; mpls@ietf.org; Yaakov Stei=
n (yaakov_s@rad.com); pwe3 (pwe3@ietf.org)=0A=
Subject: Re: [PWE3] Pseudowire Sequence Number in draft-ietf-mpls-forwardin=
g: a minor comment=0A=
=0A=
In message <F9336571731ADE42A5397FC831CEAA025AC56C9D@ILPTWPVEXMB02.ecitele.=
com>=0A=
Alexander Vainshtein writes:=0A=
>=0A=
> Curtis,=0A=
>=0A=
> Lots of thanks for a prompt and very detailed response.=0A=
> May I suggest an alternative version of the following text fragment?=0A=
>=0A=
> <Curtis>=0A=
> >   Identifying the position of any lost packets is important=0A=
> >    for PW services which are attempting to reconstruct a bit stream=0A=
> >    which maintains bit timing, such as time division multiplexing (TDM)=
=0A=
> >    services.  TDM and other PW services which require strict ordering=
=0A=
> >    also require that misordered packets be either dropped or reordered.=
=0A=
=0A=
Invalid XML - you didn't close this element.  :-)=0A=
=0A=
>  <Sasha>=0A=
>=0A=
>    Identifying lost PW packets and exact amount of lost payload is=0A=
>    critical for PW services which maintain bit timing, such as Time=0A=
>    Division Multiplexing (TDM) services since these services MUST=0A=
>    compensate lost payload on a bit-for-bit basis.=0A=
>=0A=
>    With these services PW packets that have been received out of order=0A=
>    also MUST also be identified and may be either re-ordered or=0A=
>    dropped.  Reordering requires, in addition to sequence numbering, a=0A=
>    "de-jitter buffer" in the egress PE, and ability to reorder is=0A=
>    limited by the depth of this buffer. The down side of maintaining a=0A=
>    de-jitter buffer is added end-to-end service delay.=0A=
>=0A=
>   </Sasha>=0A=
=0A=
Accepted with a small change.=0A=
=0A=
After the words "down side"=0A=
s/de-jitter buffer/large jitter buffer/=0A=
Elsewhere=0A=
s/de-jitter buffer/jitter buffer/g=0A=
Then add the sentence.=0A=
=0A=
   A small jitter buffer is always necessary and the jitter buffer=0A=
   is needed regardless of whether reordering is done.=0A=
=0A=
This yields a slightly changed second paragraph.=0A=
=0A=
   With these services PW packets that have been received out of order=0A=
   also MUST also be identified and may be either re-ordered or=0A=
   dropped.  Reordering requires, in addition to sequence numbering, a=0A=
   "jitter buffer" in the egress PE, and ability to reorder is limited=0A=
   by the depth of this buffer. The down side of maintaining a large=0A=
   jitter buffer is added end-to-end service delay.  A small jitter=0A=
   buffer is always necessary and the jitter buffer is needed=0A=
   regardless of whether reordering is done.=0A=
=0A=
Is this wording OK with you?=0A=
=0A=
Curtis=0A=
=0A=
> Hopefully this will be useful.=0A=
>=0A=
>=0A=
> Regards,=0A=
>      Sasha=0A=
>=0A=
> > -----Original Message-----=0A=
> > From: Curtis Villamizar [mailto:curtis@ipv6.occnc.com]=0A=
> > Sent: Monday, November 25, 2013 8:30 PM=0A=
> > To: Alexander Vainshtein=0A=
> > Cc: curtis@occnc.com; kireeti@juniper.net; samante@apple.com;=0A=
> > agmalis@gmail.com; cpignata@cisco.com; mpls@ietf.org; Yaakov Stein=0A=
> > (yaakov_s@rad.com); pwe3 (pwe3@ietf.org)=0A=
> > Subject: Re: [PWE3] Pseudowire Sequence Number in draft-ietf-mpls-=0A=
> > forwarding: a minor comment=0A=
> >=0A=
> >=0A=
> > In message=0A=
> > <F9336571731ADE42A5397FC831CEAA025392F92F@ILPTWPVEXMB01.ecitele.c=0A=
> > om>=0A=
> > Alexander Vainshtein writes:=0A=
> > >=0A=
> > > Hi all,=0A=
> > >=0A=
> > > I would like to comment on the text in Section 2.1.8.1 "Pseudowire=0A=
> > > Sequence Number" in draft-ietf-mpls-forwarding-03 - MPLS Forwarding=
=0A=
> > > Compliance and Performance Requirements=0A=
> > > <http://tools.ietf.org/html/draft-ietf-mpls-forwarding-03>.=0A=
> > >=0A=
> > > This section states, in short, that the main drive for using the=0A=
> > > sequence number in the PW Control Word is handling of packet=0A=
> > > reordering events. TDM PWs are presented as a major example, with CBR=
=0A=
> > > ATM services as another example.=0A=
> > >=0A=
> > > In fact, this statement is not accurate.=0A=
> >=0A=
> > Yes.  You are correct in pointing this out as inaccurate by omitting=0A=
> > the other important function of identifying drops for the purpose of=0A=
> > recunstructing TDM bit streams.=0A=
> >=0A=
> > Andy brought up resequencing being a strong provider request.=0A=
> > Reordering is far more common than loss particularly for high priority=
=0A=
> > services on provider networks and without resequencing reorder results=
=0A=
> > in PW loss in what could otherwise be lossless service.=0A=
> >=0A=
> > So we should get the base requirements right but still reflect this,=0A=
> > but strictly as advice with no normative wording.  We had used the=0A=
> > phrase "is beneficial" and will retain that.=0A=
> >=0A=
> > Andy brought up the topic.  The incorrect wording in the existing=0A=
> > draft is my fault.  This text went in fairly early with a lot of other=
=0A=
> > changes and it appears that no one had since given it a careful enough=
=0A=
> > read and review until you came along.=0A=
> >=0A=
> > > The main drive for mandating the use of sequence number in TM PWs is=
=0A=
> > > the need to detect and count lost packets because the egress PE MUST=
=0A=
> > > compensate the lost payload bit for bit.=0A=
> > >=0A=
> > > Ability to compensate reordering of PW packets at egress is a side=0A=
> > > effect of (a) sequence number usage and (b) usage of the de-jitter=0A=
> > > buffer in the egress PW. It is not mandatory and in any case is=0A=
> > > limited by the depth of the de-jitter buffer: re-ordered packets that=
=0A=
> > > cannot be accommodated within this buffer are treated as lost.=0A=
> > >=0A=
> > > Additional details can be found, e.g., in section 6.2.2 of RFC=0A=
> > > 4553<http://tools.ietf.org/html/rfc4553>. Ability to re-order=0A=
> > > mis-ordered PW packets is defined there as OPTIONAL, while replacemen=
t=0A=
> > > of the payload of lost PW packets is defined as MANDATORY.=0A=
> >=0A=
> > The change below at the top of the section more accurately reflects=0A=
> > requirements in the RFCs but still states that resequencing can be=0A=
> > beneficial.  The comments about EPD and PPD are dropped and therefore=
=0A=
> > also the informative reference.=0A=
> >=0A=
> >  Context:=0A=
> >=0A=
> >  2.1.8.1.  Pseudowire Sequence Number=0A=
> >=0A=
> >  OLD=0A=
> >=0A=
> >    Pseudowire (PW) sequence number support is most important for PW=0A=
> >    payload types with a high expectation of in-order delivery.=0A=
> >    Resequencing support, rather than dropping at egress on out of order=
=0A=
> >    arrival, is most important for PW payload types with a high=0A=
> >    expectation of lossless delivery.  For example, TDM payloads require=
=0A=
> >    sequence number support and require resequencing support.  The same=
=0A=
> >    is true of ATM CBR service.  ATM VBR or ABR may have somewhat relaxe=
d=0A=
> >    requirements, but generally require ATM Early Packet Discard (EPD) o=
r=0A=
> >    ATM Partial Packet Discard (PPD) [ATM-EPD-and-PPD].  Though sequence=
=0A=
> >    number support and resequencing support are beneficial to PW packet=
=0A=
> >    oriented payloads such as FR and Ethernet, they are highly desirable=
=0A=
> >    but not as strongly required.=0A=
> >=0A=
> > NEW=0A=
> >=0A=
> >    Pseudowire (PW) sequence number support is most important for PW=0A=
> >    payload types with a high expectation of lossless and/or in-order=0A=
> >    delivery.  Identifying the position of any lost packets is important=
=0A=
> >    for PW services which are attempting to reconstruct a bit stream=0A=
> >    which maintains bit timing, such as time division multiplexing (TDM)=
=0A=
> >    services.  TDM and other PW services which require strict ordering=
=0A=
> >    also require that misordered packets be either dropped or reordered.=
=0A=
> >=0A=
> >    PW services which are not timing critical bit streams in nature are=
=0A=
> >    cell oriented or frame oriented.  Though resequencing support is=0A=
> >    beneficial to PW cell and frame oriented payloads such as ATM, FR an=
d=0A=
> >    Ethernet, they are highly desirable but not required.=0A=
> >=0A=
> > NEW (end of subsection after list of possible reording causes)=0A=
> >=0A=
> >    In provider networks which use multipath techniques and which may=0A=
> >    occassionally rebalance traffic or which may change PW paths=0A=
> >    occasionally for other reasons, reordering may be far more common=0A=
> >    than loss.  Where reordering is more common than loss, resequencing=
=0A=
> >    packets is beneficial, rather than dropping packets at egress when=
=0A=
> >    out of order arrival occus.  Resequencing is most important for PW=
=0A=
> >    payload types with a high expectation of lossless delivery since in=
=0A=
> >    such cases out of order delivery within the network results in PW=0A=
> >    loss.=0A=
> >=0A=
> > The final paragraph sums up the motivation for highlighting=0A=
> > resequencing as beneficial and desirable.  It does so without any=0A=
> > normative wording.=0A=
> >=0A=
> > > Hopefully these notes will be useful.=0A=
> > >=0A=
> > > Regards,=0A=
> > >      Sasha=0A=
> >=0A=
> > These notes are very useful.  Thank you.=0A=
> >=0A=
> > Please let us know if you (and the WG) are OK with the rewording=0A=
> > proposed above.=0A=
> >=0A=
> > Curtis=0A=

From Alexander.Vainshtein@ecitele.com  Tue Dec 10 22:05:41 2013
Return-Path: <Alexander.Vainshtein@ecitele.com>
X-Original-To: pwe3@ietfa.amsl.com
Delivered-To: pwe3@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D4A0E1AE39F; Tue, 10 Dec 2013 22:05:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level: 
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3ArpOVN4fIcz; Tue, 10 Dec 2013 22:05:38 -0800 (PST)
Received: from emea01-am1-obe.outbound.protection.outlook.com (mail-am1lp0017.outbound.protection.outlook.com [213.199.154.17]) by ietfa.amsl.com (Postfix) with ESMTP id 9FA261AE39C; Tue, 10 Dec 2013 22:05:37 -0800 (PST)
Received: from AM3PR03MB532.eurprd03.prod.outlook.com (10.242.109.156) by AM3PR03MB530.eurprd03.prod.outlook.com (10.242.109.154) with Microsoft SMTP Server (TLS) id 15.0.837.10; Wed, 11 Dec 2013 06:05:30 +0000
Received: from AM3PR03MB532.eurprd03.prod.outlook.com ([10.242.109.156]) by AM3PR03MB532.eurprd03.prod.outlook.com ([10.242.109.156]) with mapi id 15.00.0837.004; Wed, 11 Dec 2013 06:05:30 +0000
From: Alexander Vainshtein <Alexander.Vainshtein@ecitele.com>
To: "curtis@occnc.com" <curtis@occnc.com>
Thread-Topic: [PWE3] Pseudowire Sequence Number in draft-ietf-mpls-forwarding: a minor comment
Thread-Index: AQHO9jb+Sq0tCZZscUehMpHq+OAdtQ==
Date: Wed, 11 Dec 2013 06:05:29 +0000
Message-ID: <96907ab6f1ec48c1971db740f7845ff4@AM3PR03MB532.eurprd03.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [5.153.9.203]
x-forefront-prvs: 0057EE387C
x-forefront-antispam-report: SFV:NSPM; SFS:(10009001)(189002)(199002)(13464003)(377454003)(52604005)(51704005)(53754006)(81542001)(76786001)(81342001)(76576001)(4396001)(49866001)(33646001)(46102001)(74662001)(47446002)(85852003)(83072002)(31966008)(51856001)(76176001)(47976001)(47736001)(76796001)(50986001)(74502001)(74876001)(54356001)(76482001)(74316001)(74706001)(65816001)(87266001)(2656002)(80022001)(63696002)(87936001)(66066001)(74366001)(83322001)(19580405001)(85306002)(90146001)(19580395003)(69226001)(56776001)(80976001)(54316002)(79102001)(53806001)(59766001)(71446004)(81816001)(56816005)(77982001)(81686001)(427584002)(24736002); DIR:OUT; SFP:1101; SCL:1; SRVR:AM3PR03MB530; H:AM3PR03MB532.eurprd03.prod.outlook.com; CLIP:5.153.9.203; FPR:; RD:InfoNoRecords; MX:1; A:1; LANG:en; 
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: ecitele.com
Cc: "samante@apple.com" <samante@apple.com>, "Yaakov Stein \(yaakov_s@rad.com\)" <yaakov_s@rad.com>, "cpignata@cisco.com" <cpignata@cisco.com>, "kireeti@juniper.net" <kireeti@juniper.net>, "mpls@ietf.org" <mpls@ietf.org>, "pwe3 \(pwe3@ietf.org\)" <pwe3@ietf.org>
Subject: Re: [PWE3] Pseudowire Sequence Number in draft-ietf-mpls-forwarding: a minor comment
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Pseudowire Emulation Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 11 Dec 2013 06:05:42 -0000

Curtis,=0A=
Lots of thanks for sending out the new text.=0A=
=0A=
I still have a couple of issues with this version of the text: one technica=
l and one editorial.=0A=
=0A=
The technical issue is about the fragment "A small jitter buffer is always =
necessary". =0A=
=0A=
I am not sure this is correct, since I am aware of several PW implementatio=
ns that pass the payload of a received PW packet directly for transmission =
via the corresdponding attachment circuit. Of course this payload would be =
stored in some Tx queue associated with the attachment circuit and controll=
ed by the appropriate egress scheduler, but IMO this does not constitue a P=
W jitter bufer, since the PW interworking function does not exersize any co=
ntrol over these queues.=0A=
In particular, these queues could not be used for re-ordering misordered PW=
 packets.=0A=
IMHO and FWIW this understanding matches RFC 3985 which mentions (in Sectio=
n 5.2.1.1 "Frame Ordering") that reodering as the strategy for handling mis=
-ordered packets introduces additional delay (i.e., requires a ddicated jit=
ter buffer), while the alternative strategy of discarding mis-ordered packe=
ts does not introduce such additional delay.=0A=
=0A=
The editorial issue is about the entire sentence that contains the above-me=
ntioned fragment, i.e., "A small jitter buffer is always necessary and the =
jitter buffer is needed regardless of whether reordering is done" - to me t=
his looks like an unnecessary repetition if if it were techically correct.=
=0A=
=0A=
Hence I would like to suggest discrading the problematic sentence as the si=
mplest way to resolve both issues.=0A=
=0A=
Hopefully these notes will e helpful.=0A=
=0A=
Regards,=0A=
     Sasha=0A=
=0A=
=0A=
________________________________________=0A=
From: Curtis Villamizar <curtis@occnc.com>=0A=
Sent: Tuesday, December 10, 2013 5:47 PM=0A=
To: Alexander Vainshtein=0A=
Cc: curtis@ipv6.occnc.com; curtis@occnc.com; kireeti@juniper.net; samante@a=
pple.com; agmalis@gmail.com; cpignata@cisco.com; mpls@ietf.org; Yaakov Stei=
n (yaakov_s@rad.com); pwe3 (pwe3@ietf.org)=0A=
Subject: Re: [PWE3] Pseudowire Sequence Number in draft-ietf-mpls-forwardin=
g: a minor comment=0A=
=0A=
In message <F9336571731ADE42A5397FC831CEAA025AC56C9D@ILPTWPVEXMB02.ecitele.=
com>=0A=
Alexander Vainshtein writes:=0A=
>=0A=
> Curtis,=0A=
>=0A=
> Lots of thanks for a prompt and very detailed response.=0A=
> May I suggest an alternative version of the following text fragment?=0A=
>=0A=
> <Curtis>=0A=
> >   Identifying the position of any lost packets is important=0A=
> >    for PW services which are attempting to reconstruct a bit stream=0A=
> >    which maintains bit timing, such as time division multiplexing (TDM)=
=0A=
> >    services.  TDM and other PW services which require strict ordering=
=0A=
> >    also require that misordered packets be either dropped or reordered.=
=0A=
=0A=
Invalid XML - you didn't close this element.  :-)=0A=
=0A=
>  <Sasha>=0A=
>=0A=
>    Identifying lost PW packets and exact amount of lost payload is=0A=
>    critical for PW services which maintain bit timing, such as Time=0A=
>    Division Multiplexing (TDM) services since these services MUST=0A=
>    compensate lost payload on a bit-for-bit basis.=0A=
>=0A=
>    With these services PW packets that have been received out of order=0A=
>    also MUST also be identified and may be either re-ordered or=0A=
>    dropped.  Reordering requires, in addition to sequence numbering, a=0A=
>    "de-jitter buffer" in the egress PE, and ability to reorder is=0A=
>    limited by the depth of this buffer. The down side of maintaining a=0A=
>    de-jitter buffer is added end-to-end service delay.=0A=
>=0A=
>   </Sasha>=0A=
=0A=
Accepted with a small change.=0A=
=0A=
After the words "down side"=0A=
s/de-jitter buffer/large jitter buffer/=0A=
Elsewhere=0A=
s/de-jitter buffer/jitter buffer/g=0A=
Then add the sentence.=0A=
=0A=
   A small jitter buffer is always necessary and the jitter buffer=0A=
   is needed regardless of whether reordering is done.=0A=
=0A=
This yields a slightly changed second paragraph.=0A=
=0A=
   With these services PW packets that have been received out of order=0A=
   also MUST also be identified and may be either re-ordered or=0A=
   dropped.  Reordering requires, in addition to sequence numbering, a=0A=
   "jitter buffer" in the egress PE, and ability to reorder is limited=0A=
   by the depth of this buffer. The down side of maintaining a large=0A=
   jitter buffer is added end-to-end service delay.  A small jitter=0A=
   buffer is always necessary and the jitter buffer is needed=0A=
   regardless of whether reordering is done.=0A=
=0A=
Is this wording OK with you?=0A=
=0A=
Curtis=0A=
=0A=
> Hopefully this will be useful.=0A=
>=0A=
>=0A=
> Regards,=0A=
>      Sasha=0A=
>=0A=
> > -----Original Message-----=0A=
> > From: Curtis Villamizar [mailto:curtis@ipv6.occnc.com]=0A=
> > Sent: Monday, November 25, 2013 8:30 PM=0A=
> > To: Alexander Vainshtein=0A=
> > Cc: curtis@occnc.com; kireeti@juniper.net; samante@apple.com;=0A=
> > agmalis@gmail.com; cpignata@cisco.com; mpls@ietf.org; Yaakov Stein=0A=
> > (yaakov_s@rad.com); pwe3 (pwe3@ietf.org)=0A=
> > Subject: Re: [PWE3] Pseudowire Sequence Number in draft-ietf-mpls-=0A=
> > forwarding: a minor comment=0A=
> >=0A=
> >=0A=
> > In message=0A=
> > <F9336571731ADE42A5397FC831CEAA025392F92F@ILPTWPVEXMB01.ecitele.c=0A=
> > om>=0A=
> > Alexander Vainshtein writes:=0A=
> > >=0A=
> > > Hi all,=0A=
> > >=0A=
> > > I would like to comment on the text in Section 2.1.8.1 "Pseudowire=0A=
> > > Sequence Number" in draft-ietf-mpls-forwarding-03 - MPLS Forwarding=
=0A=
> > > Compliance and Performance Requirements=0A=
> > > <http://tools.ietf.org/html/draft-ietf-mpls-forwarding-03>.=0A=
> > >=0A=
> > > This section states, in short, that the main drive for using the=0A=
> > > sequence number in the PW Control Word is handling of packet=0A=
> > > reordering events. TDM PWs are presented as a major example, with CBR=
=0A=
> > > ATM services as another example.=0A=
> > >=0A=
> > > In fact, this statement is not accurate.=0A=
> >=0A=
> > Yes.  You are correct in pointing this out as inaccurate by omitting=0A=
> > the other important function of identifying drops for the purpose of=0A=
> > recunstructing TDM bit streams.=0A=
> >=0A=
> > Andy brought up resequencing being a strong provider request.=0A=
> > Reordering is far more common than loss particularly for high priority=
=0A=
> > services on provider networks and without resequencing reorder results=
=0A=
> > in PW loss in what could otherwise be lossless service.=0A=
> >=0A=
> > So we should get the base requirements right but still reflect this,=0A=
> > but strictly as advice with no normative wording.  We had used the=0A=
> > phrase "is beneficial" and will retain that.=0A=
> >=0A=
> > Andy brought up the topic.  The incorrect wording in the existing=0A=
> > draft is my fault.  This text went in fairly early with a lot of other=
=0A=
> > changes and it appears that no one had since given it a careful enough=
=0A=
> > read and review until you came along.=0A=
> >=0A=
> > > The main drive for mandating the use of sequence number in TM PWs is=
=0A=
> > > the need to detect and count lost packets because the egress PE MUST=
=0A=
> > > compensate the lost payload bit for bit.=0A=
> > >=0A=
> > > Ability to compensate reordering of PW packets at egress is a side=0A=
> > > effect of (a) sequence number usage and (b) usage of the de-jitter=0A=
> > > buffer in the egress PW. It is not mandatory and in any case is=0A=
> > > limited by the depth of the de-jitter buffer: re-ordered packets that=
=0A=
> > > cannot be accommodated within this buffer are treated as lost.=0A=
> > >=0A=
> > > Additional details can be found, e.g., in section 6.2.2 of RFC=0A=
> > > 4553<http://tools.ietf.org/html/rfc4553>. Ability to re-order=0A=
> > > mis-ordered PW packets is defined there as OPTIONAL, while replacemen=
t=0A=
> > > of the payload of lost PW packets is defined as MANDATORY.=0A=
> >=0A=
> > The change below at the top of the section more accurately reflects=0A=
> > requirements in the RFCs but still states that resequencing can be=0A=
> > beneficial.  The comments about EPD and PPD are dropped and therefore=
=0A=
> > also the informative reference.=0A=
> >=0A=
> >  Context:=0A=
> >=0A=
> >  2.1.8.1.  Pseudowire Sequence Number=0A=
> >=0A=
> >  OLD=0A=
> >=0A=
> >    Pseudowire (PW) sequence number support is most important for PW=0A=
> >    payload types with a high expectation of in-order delivery.=0A=
> >    Resequencing support, rather than dropping at egress on out of order=
=0A=
> >    arrival, is most important for PW payload types with a high=0A=
> >    expectation of lossless delivery.  For example, TDM payloads require=
=0A=
> >    sequence number support and require resequencing support.  The same=
=0A=
> >    is true of ATM CBR service.  ATM VBR or ABR may have somewhat relaxe=
d=0A=
> >    requirements, but generally require ATM Early Packet Discard (EPD) o=
r=0A=
> >    ATM Partial Packet Discard (PPD) [ATM-EPD-and-PPD].  Though sequence=
=0A=
> >    number support and resequencing support are beneficial to PW packet=
=0A=
> >    oriented payloads such as FR and Ethernet, they are highly desirable=
=0A=
> >    but not as strongly required.=0A=
> >=0A=
> > NEW=0A=
> >=0A=
> >    Pseudowire (PW) sequence number support is most important for PW=0A=
> >    payload types with a high expectation of lossless and/or in-order=0A=
> >    delivery.  Identifying the position of any lost packets is important=
=0A=
> >    for PW services which are attempting to reconstruct a bit stream=0A=
> >    which maintains bit timing, such as time division multiplexing (TDM)=
=0A=
> >    services.  TDM and other PW services which require strict ordering=
=0A=
> >    also require that misordered packets be either dropped or reordered.=
=0A=
> >=0A=
> >    PW services which are not timing critical bit streams in nature are=
=0A=
> >    cell oriented or frame oriented.  Though resequencing support is=0A=
> >    beneficial to PW cell and frame oriented payloads such as ATM, FR an=
d=0A=
> >    Ethernet, they are highly desirable but not required.=0A=
> >=0A=
> > NEW (end of subsection after list of possible reording causes)=0A=
> >=0A=
> >    In provider networks which use multipath techniques and which may=0A=
> >    occassionally rebalance traffic or which may change PW paths=0A=
> >    occasionally for other reasons, reordering may be far more common=0A=
> >    than loss.  Where reordering is more common than loss, resequencing=
=0A=
> >    packets is beneficial, rather than dropping packets at egress when=
=0A=
> >    out of order arrival occus.  Resequencing is most important for PW=
=0A=
> >    payload types with a high expectation of lossless delivery since in=
=0A=
> >    such cases out of order delivery within the network results in PW=0A=
> >    loss.=0A=
> >=0A=
> > The final paragraph sums up the motivation for highlighting=0A=
> > resequencing as beneficial and desirable.  It does so without any=0A=
> > normative wording.=0A=
> >=0A=
> > > Hopefully these notes will be useful.=0A=
> > >=0A=
> > > Regards,=0A=
> > >      Sasha=0A=
> >=0A=
> > These notes are very useful.  Thank you.=0A=
> >=0A=
> > Please let us know if you (and the WG) are OK with the rewording=0A=
> > proposed above.=0A=
> >=0A=
> > Curtis=0A=

From zhangmingui@huawei.com  Tue Dec 10 23:18:59 2013
Return-Path: <zhangmingui@huawei.com>
X-Original-To: pwe3@ietfa.amsl.com
Delivered-To: pwe3@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8B7C41AE3BA for <pwe3@ietfa.amsl.com>; Tue, 10 Dec 2013 23:18:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.202
X-Spam-Level: 
X-Spam-Status: No, score=-4.202 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QeNoCPEFESn7 for <pwe3@ietfa.amsl.com>; Tue, 10 Dec 2013 23:18:58 -0800 (PST)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id A9F771AD8E3 for <pwe3@ietf.org>; Tue, 10 Dec 2013 23:18:57 -0800 (PST)
Received: from 172.18.7.190 (EHLO lhreml204-edg.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BBG22624; Wed, 11 Dec 2013 07:18:51 +0000 (GMT)
Received: from LHREML406-HUB.china.huawei.com (10.201.5.243) by lhreml204-edg.china.huawei.com (172.18.7.223) with Microsoft SMTP Server (TLS) id 14.3.158.1; Wed, 11 Dec 2013 07:18:28 +0000
Received: from NKGEML403-HUB.china.huawei.com (10.98.56.34) by lhreml406-hub.china.huawei.com (10.201.5.243) with Microsoft SMTP Server (TLS) id 14.3.158.1; Wed, 11 Dec 2013 07:18:37 +0000
Received: from NKGEML508-MBX.china.huawei.com ([169.254.7.180]) by nkgeml403-hub.china.huawei.com ([10.98.56.34]) with mapi id 14.03.0158.001; Wed, 11 Dec 2013 15:18:30 +0800
From: Mingui Zhang <zhangmingui@huawei.com>
To: Yaakov Stein <yaakov_s@rad.com>, "Andrew G. Malis" <agmalis@gmail.com>, "pwe3@ietf.org" <pwe3@ietf.org>
Thread-Topic: [PWE3] Poll for WG adoption and IPR check	of draft-zhang-pwe3-iccp-stp-00
Thread-Index: AQHO9MyrnVnG+A98EUimub8Zug+tUJpOUNog
Date: Wed, 11 Dec 2013 07:18:28 +0000
Message-ID: <4552F0907735844E9204A62BBDD325E73368FF27@nkgeml508-mbx.china.huawei.com>
References: <CAA=duU1X6SWzxNOVdXJHA4TsxnVf6u4jGO=0MaoYkc-661XWDw@mail.gmail.com> <6e6993502ff243d29c52ed9047deed0e@exrad6.ad.rad.co.il>
In-Reply-To: <6e6993502ff243d29c52ed9047deed0e@exrad6.ad.rad.co.il>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.111.102.175]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Subject: Re: [PWE3] Poll for WG adoption and IPR check	of	draft-zhang-pwe3-iccp-stp-00
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Pseudowire Emulation Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 11 Dec 2013 07:18:59 -0000

Hi Yaakov,=20

Thanks for the comment!

As I know from vendor implementers, 'ring' topology is widely used by custo=
mers in their DSLAM networks. It's common for such a network to have multip=
le attach points to an SP's L2VPN network... For such kind of connections, =
there are various private solutions to meet customers' requirements. That's=
 why we designed this standard proposal for customers.

I find implementers are interested in such proposal, from which I see a cha=
nce to bring implementations to the existing pwe3 draft.=20

Not to debate. Just to add some info.

Regards,
Mingui

>-----Original Message-----
>From: pwe3 [mailto:pwe3-bounces@ietf.org] On Behalf Of Yaakov Stein
>Sent: Monday, December 09, 2013 6:52 PM
>To: Andrew G. Malis; pwe3@ietf.org
>Subject: Re: [PWE3] Poll for WG adoption and IPR check of
>draft-zhang-pwe3-iccp-stp-00
>
>I do not support adoption,
>partly because I don't think PWE3 should be taking on any new work, and pa=
rtly
>because I don't think the use case is sufficiently interesting.
>
>Y(J)S
>
>
>-----Original Message-----
>From: pwe3 [mailto:pwe3-bounces@ietf.org] On Behalf Of Andrew G. Malis
>Sent: 04 December, 2013 22:53
>To: pwe3@ietf.org
>Subject: [PWE3] Poll for WG adoption and IPR check of
>draft-zhang-pwe3-iccp-stp-00
>
>This email begins a two week poll to help the chairs determine if there is
>consensus to adopt draft-zhang-pwe3-iccp-stp-00 as an PWE3 working group
>draft.
>
>The draft can be found here:
>http://tools.ietf.org/html/draft-zhang-pwe3-iccp-stp-00
>
>Please read the draft and indicate to the list if you support adoption, or=
 if you do
>not support adoption (giving reasons).
>
>Please note that this is only a call for adoption. There needs to be conse=
nsus
>that this draft is a good basis for the work, but it does not need to be p=
erfect at
>this stage.
>
>Coincidentally, we are also polling for knowledge of any IPR that applies =
to this
>draft, to ensure that IPR has been disclosed in compliance with IETF IPR r=
ules
>(see RFCs 3979, 4879, 3669 and 5378 for more details).
>
>If you are listed as a document author or contributor please respond to th=
is
>email whether or not you are aware of any relevant IPR. The draft will not=
 be
>adopted until a response has been received from each author and contributo=
r.
>
>If you are on the PWE3 WG email list but are not listed as an author or
>contributor, then please explicitly respond regarding IPR only if you are =
aware of
>any IPR that has not yet been disclosed in conformance with IETF rules.
>
>The poll for adoption will close in two weeks time, on Wednesday 18th
>December.
>
>Best regards,
>Andy
>_______________________________________________
>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 wenhuafeng@huawei.com  Tue Dec 10 23:56:27 2013
Return-Path: <wenhuafeng@huawei.com>
X-Original-To: pwe3@ietfa.amsl.com
Delivered-To: pwe3@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 345D61AE2A0 for <pwe3@ietfa.amsl.com>; Tue, 10 Dec 2013 23:56:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.413
X-Spam-Level: 
X-Spam-Status: No, score=-1.413 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, CN_BODY_35=0.339, MIME_CHARSET_FARAWAY=2.45, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YM6l76B8iJmZ for <pwe3@ietfa.amsl.com>; Tue, 10 Dec 2013 23:56:26 -0800 (PST)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 433C11A1F5B for <pwe3@ietf.org>; Tue, 10 Dec 2013 23:56:25 -0800 (PST)
Received: from 172.18.7.190 (EHLO lhreml204-edg.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BBG26616; Wed, 11 Dec 2013 07:56:19 +0000 (GMT)
Received: from LHREML401-HUB.china.huawei.com (10.201.5.240) by lhreml204-edg.china.huawei.com (172.18.7.223) with Microsoft SMTP Server (TLS) id 14.3.158.1; Wed, 11 Dec 2013 07:56:08 +0000
Received: from NKGEML408-HUB.china.huawei.com (10.98.56.39) by lhreml401-hub.china.huawei.com (10.201.5.240) with Microsoft SMTP Server (TLS) id 14.3.158.1; Wed, 11 Dec 2013 07:56:17 +0000
Received: from NKGEML503-MBS.china.huawei.com ([169.254.6.87]) by nkgeml408-hub.china.huawei.com ([10.98.56.39]) with mapi id 14.03.0158.001; Wed, 11 Dec 2013 15:56:06 +0800
From: Wenhuafeng <wenhuafeng@huawei.com>
To: Mingui Zhang <zhangmingui@huawei.com>, Yaakov Stein <yaakov_s@rad.com>, "Andrew G. Malis" <agmalis@gmail.com>, "pwe3@ietf.org" <pwe3@ietf.org>
Thread-Topic: [PWE3] Poll for WG adoption and IPR	check	of draft-zhang-pwe3-iccp-stp-00
Thread-Index: AQHO9kLVArUWwnOoZk+G3d53/PHYmJpOoAhw
Date: Wed, 11 Dec 2013 07:56:05 +0000
Message-ID: <B51493B1D374244F9572F031F74684294FDCE912@nkgeml503-mbs.china.huawei.com>
References: <CAA=duU1X6SWzxNOVdXJHA4TsxnVf6u4jGO=0MaoYkc-661XWDw@mail.gmail.com> <6e6993502ff243d29c52ed9047deed0e@exrad6.ad.rad.co.il> <4552F0907735844E9204A62BBDD325E73368FF27@nkgeml508-mbx.china.huawei.com>
In-Reply-To: <4552F0907735844E9204A62BBDD325E73368FF27@nkgeml508-mbx.china.huawei.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.135.30.158]
Content-Type: text/plain; charset="gb2312"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Subject: Re: [PWE3] Poll for WG adoption and IPR	check	of	draft-zhang-pwe3-iccp-stp-00
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Pseudowire Emulation Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 11 Dec 2013 07:56:27 -0000

U3VwcG9ydCBhcyBhbiBpbXBsZW1lbnRlciA6KQ0KDQpIdWFmZW5nDQoNCi0tLS0t08q8/tStvP4t
LS0tLQ0Kt6K8/sjLOiBwd2UzIFttYWlsdG86cHdlMy1ib3VuY2VzQGlldGYub3JnXSC0+rHtIE1p
bmd1aSBaaGFuZw0Kt6LLzcqxvOQ6IDIwMTPE6jEy1MIxMcjVIDE1OjE4DQrK1bz+yMs6IFlhYWtv
diBTdGVpbjsgQW5kcmV3IEcuIE1hbGlzOyBwd2UzQGlldGYub3JnDQrW98ziOiBSZTogW1BXRTNd
IFBvbGwgZm9yIFdHIGFkb3B0aW9uIGFuZCBJUFIgY2hlY2sgb2YgZHJhZnQtemhhbmctcHdlMy1p
Y2NwLXN0cC0wMA0KDQpIaSBZYWFrb3YsIA0KDQpUaGFua3MgZm9yIHRoZSBjb21tZW50IQ0KDQpB
cyBJIGtub3cgZnJvbSB2ZW5kb3IgaW1wbGVtZW50ZXJzLCAncmluZycgdG9wb2xvZ3kgaXMgd2lk
ZWx5IHVzZWQgYnkgY3VzdG9tZXJzIGluIHRoZWlyIERTTEFNIG5ldHdvcmtzLiBJdCdzIGNvbW1v
biBmb3Igc3VjaCBhIG5ldHdvcmsgdG8gaGF2ZSBtdWx0aXBsZSBhdHRhY2ggcG9pbnRzIHRvIGFu
IFNQJ3MgTDJWUE4gbmV0d29yay4uLiBGb3Igc3VjaCBraW5kIG9mIGNvbm5lY3Rpb25zLCB0aGVy
ZSBhcmUgdmFyaW91cyBwcml2YXRlIHNvbHV0aW9ucyB0byBtZWV0IGN1c3RvbWVycycgcmVxdWly
ZW1lbnRzLiBUaGF0J3Mgd2h5IHdlIGRlc2lnbmVkIHRoaXMgc3RhbmRhcmQgcHJvcG9zYWwgZm9y
IGN1c3RvbWVycy4NCg0KSSBmaW5kIGltcGxlbWVudGVycyBhcmUgaW50ZXJlc3RlZCBpbiBzdWNo
IHByb3Bvc2FsLCBmcm9tIHdoaWNoIEkgc2VlIGEgY2hhbmNlIHRvIGJyaW5nIGltcGxlbWVudGF0
aW9ucyB0byB0aGUgZXhpc3RpbmcgcHdlMyBkcmFmdC4gDQoNCk5vdCB0byBkZWJhdGUuIEp1c3Qg
dG8gYWRkIHNvbWUgaW5mby4NCg0KUmVnYXJkcywNCk1pbmd1aQ0KDQo+LS0tLS1PcmlnaW5hbCBN
ZXNzYWdlLS0tLS0NCj5Gcm9tOiBwd2UzIFttYWlsdG86cHdlMy1ib3VuY2VzQGlldGYub3JnXSBP
biBCZWhhbGYgT2YgWWFha292IFN0ZWluDQo+U2VudDogTW9uZGF5LCBEZWNlbWJlciAwOSwgMjAx
MyA2OjUyIFBNDQo+VG86IEFuZHJldyBHLiBNYWxpczsgcHdlM0BpZXRmLm9yZw0KPlN1YmplY3Q6
IFJlOiBbUFdFM10gUG9sbCBmb3IgV0cgYWRvcHRpb24gYW5kIElQUiBjaGVjayBvZg0KPmRyYWZ0
LXpoYW5nLXB3ZTMtaWNjcC1zdHAtMDANCj4NCj5JIGRvIG5vdCBzdXBwb3J0IGFkb3B0aW9uLA0K
PnBhcnRseSBiZWNhdXNlIEkgZG9uJ3QgdGhpbmsgUFdFMyBzaG91bGQgYmUgdGFraW5nIG9uIGFu
eSBuZXcgd29yaywgYW5kIA0KPnBhcnRseSBiZWNhdXNlIEkgZG9uJ3QgdGhpbmsgdGhlIHVzZSBj
YXNlIGlzIHN1ZmZpY2llbnRseSBpbnRlcmVzdGluZy4NCj4NCj5ZKEopUw0KPg0KPg0KPi0tLS0t
T3JpZ2luYWwgTWVzc2FnZS0tLS0tDQo+RnJvbTogcHdlMyBbbWFpbHRvOnB3ZTMtYm91bmNlc0Bp
ZXRmLm9yZ10gT24gQmVoYWxmIE9mIEFuZHJldyBHLiBNYWxpcw0KPlNlbnQ6IDA0IERlY2VtYmVy
LCAyMDEzIDIyOjUzDQo+VG86IHB3ZTNAaWV0Zi5vcmcNCj5TdWJqZWN0OiBbUFdFM10gUG9sbCBm
b3IgV0cgYWRvcHRpb24gYW5kIElQUiBjaGVjayBvZg0KPmRyYWZ0LXpoYW5nLXB3ZTMtaWNjcC1z
dHAtMDANCj4NCj5UaGlzIGVtYWlsIGJlZ2lucyBhIHR3byB3ZWVrIHBvbGwgdG8gaGVscCB0aGUg
Y2hhaXJzIGRldGVybWluZSBpZiB0aGVyZSANCj5pcyBjb25zZW5zdXMgdG8gYWRvcHQgZHJhZnQt
emhhbmctcHdlMy1pY2NwLXN0cC0wMCBhcyBhbiBQV0UzIHdvcmtpbmcgDQo+Z3JvdXAgZHJhZnQu
DQo+DQo+VGhlIGRyYWZ0IGNhbiBiZSBmb3VuZCBoZXJlOg0KPmh0dHA6Ly90b29scy5pZXRmLm9y
Zy9odG1sL2RyYWZ0LXpoYW5nLXB3ZTMtaWNjcC1zdHAtMDANCj4NCj5QbGVhc2UgcmVhZCB0aGUg
ZHJhZnQgYW5kIGluZGljYXRlIHRvIHRoZSBsaXN0IGlmIHlvdSBzdXBwb3J0IGFkb3B0aW9uLCAN
Cj5vciBpZiB5b3UgZG8gbm90IHN1cHBvcnQgYWRvcHRpb24gKGdpdmluZyByZWFzb25zKS4NCj4N
Cj5QbGVhc2Ugbm90ZSB0aGF0IHRoaXMgaXMgb25seSBhIGNhbGwgZm9yIGFkb3B0aW9uLiBUaGVy
ZSBuZWVkcyB0byBiZSANCj5jb25zZW5zdXMgdGhhdCB0aGlzIGRyYWZ0IGlzIGEgZ29vZCBiYXNp
cyBmb3IgdGhlIHdvcmssIGJ1dCBpdCBkb2VzIG5vdCANCj5uZWVkIHRvIGJlIHBlcmZlY3QgYXQg
dGhpcyBzdGFnZS4NCj4NCj5Db2luY2lkZW50YWxseSwgd2UgYXJlIGFsc28gcG9sbGluZyBmb3Ig
a25vd2xlZGdlIG9mIGFueSBJUFIgdGhhdCANCj5hcHBsaWVzIHRvIHRoaXMgZHJhZnQsIHRvIGVu
c3VyZSB0aGF0IElQUiBoYXMgYmVlbiBkaXNjbG9zZWQgaW4gDQo+Y29tcGxpYW5jZSB3aXRoIElF
VEYgSVBSIHJ1bGVzIChzZWUgUkZDcyAzOTc5LCA0ODc5LCAzNjY5IGFuZCA1Mzc4IGZvciBtb3Jl
IGRldGFpbHMpLg0KPg0KPklmIHlvdSBhcmUgbGlzdGVkIGFzIGEgZG9jdW1lbnQgYXV0aG9yIG9y
IGNvbnRyaWJ1dG9yIHBsZWFzZSByZXNwb25kIHRvIA0KPnRoaXMgZW1haWwgd2hldGhlciBvciBu
b3QgeW91IGFyZSBhd2FyZSBvZiBhbnkgcmVsZXZhbnQgSVBSLiBUaGUgZHJhZnQgDQo+d2lsbCBu
b3QgYmUgYWRvcHRlZCB1bnRpbCBhIHJlc3BvbnNlIGhhcyBiZWVuIHJlY2VpdmVkIGZyb20gZWFj
aCBhdXRob3IgYW5kIGNvbnRyaWJ1dG9yLg0KPg0KPklmIHlvdSBhcmUgb24gdGhlIFBXRTMgV0cg
ZW1haWwgbGlzdCBidXQgYXJlIG5vdCBsaXN0ZWQgYXMgYW4gYXV0aG9yIG9yIA0KPmNvbnRyaWJ1
dG9yLCB0aGVuIHBsZWFzZSBleHBsaWNpdGx5IHJlc3BvbmQgcmVnYXJkaW5nIElQUiBvbmx5IGlm
IHlvdSANCj5hcmUgYXdhcmUgb2YgYW55IElQUiB0aGF0IGhhcyBub3QgeWV0IGJlZW4gZGlzY2xv
c2VkIGluIGNvbmZvcm1hbmNlIHdpdGggSUVURiBydWxlcy4NCj4NCj5UaGUgcG9sbCBmb3IgYWRv
cHRpb24gd2lsbCBjbG9zZSBpbiB0d28gd2Vla3MgdGltZSwgb24gV2VkbmVzZGF5IDE4dGggDQo+
RGVjZW1iZXIuDQo+DQo+QmVzdCByZWdhcmRzLA0KPkFuZHkNCj5fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fXw0KPnB3ZTMgbWFpbGluZyBsaXN0DQo+cHdlM0Bp
ZXRmLm9yZw0KPmh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vcHdlMw0KPl9f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQo+cHdlMyBtYWls
aW5nIGxpc3QNCj5wd2UzQGlldGYub3JnDQo+aHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9s
aXN0aW5mby9wd2UzDQpfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fXw0KcHdlMyBtYWlsaW5nIGxpc3QNCnB3ZTNAaWV0Zi5vcmcNCmh0dHBzOi8vd3d3LmlldGYu
b3JnL21haWxtYW4vbGlzdGluZm8vcHdlMw0K

From Alexander.Vainshtein@ecitele.com  Wed Dec 11 21:49:40 2013
Return-Path: <Alexander.Vainshtein@ecitele.com>
X-Original-To: pwe3@ietfa.amsl.com
Delivered-To: pwe3@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 518F51AE006; Wed, 11 Dec 2013 21:49:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level: 
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VxtZXleP4YZZ; Wed, 11 Dec 2013 21:49:35 -0800 (PST)
Received: from emea01-am1-obe.outbound.protection.outlook.com (mail-am1lp0012.outbound.protection.outlook.com [213.199.154.12]) by ietfa.amsl.com (Postfix) with ESMTP id 6ACBE1A802D; Wed, 11 Dec 2013 21:49:32 -0800 (PST)
Received: from AM3PR03MB529.eurprd03.prod.outlook.com (10.242.109.153) by AM3PR03MB401.eurprd03.prod.outlook.com (10.242.110.14) with Microsoft SMTP Server (TLS) id 15.0.837.10; Thu, 12 Dec 2013 05:49:26 +0000
Received: from AM3PR03MB532.eurprd03.prod.outlook.com (10.242.109.156) by AM3PR03MB529.eurprd03.prod.outlook.com (10.242.109.153) with Microsoft SMTP Server (TLS) id 15.0.842.7; Thu, 12 Dec 2013 05:49:24 +0000
Received: from AM3PR03MB532.eurprd03.prod.outlook.com ([10.242.109.156]) by AM3PR03MB532.eurprd03.prod.outlook.com ([10.242.109.156]) with mapi id 15.00.0842.003; Thu, 12 Dec 2013 05:49:23 +0000
From: Alexander Vainshtein <Alexander.Vainshtein@ecitele.com>
To: "curtis@ipv6.occnc.com" <curtis@ipv6.occnc.com>
Thread-Topic: [PWE3] Pseudowire Sequence Number in draft-ietf-mpls-forwarding: a minor comment
Thread-Index: AQHO9vYcSq0tCZZscUehMpHq+OAdtZpQDFrZ
Date: Thu, 12 Dec 2013 05:49:22 +0000
Message-ID: <4946c79f4554497d84cd676684739124@AM3PR03MB532.eurprd03.prod.outlook.com>
References: Your message of "Wed, 11 Dec 2013 06:05:20 +0000." <774d74926b684ffba7f4f89ace758547@AM3PR03MB532.eurprd03.prod.outlook.com>, <201312120453.rBC4rYp4065163@gateway1.ipv6.occnc.com>
In-Reply-To: <201312120453.rBC4rYp4065163@gateway1.ipv6.occnc.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [5.153.9.202]
x-forefront-prvs: 0058ABBBC7
x-forefront-antispam-report: SFV:NSPM; SFS:(10009001)(13464003)(53754006)(189002)(199002)(43784003)(377454003)(52604005)(51704005)(76482001)(47736001)(50986001)(47976001)(81342001)(4396001)(81816001)(76576001)(74662001)(47446002)(74502001)(76786001)(31966008)(74316001)(49866001)(71446004)(74366001)(56816005)(90146001)(66066001)(74706001)(63696002)(76796001)(85306002)(65816001)(80022001)(87266001)(87936001)(19580405001)(19580395003)(80976001)(2656002)(46102001)(83322001)(56776001)(79102001)(74876001)(77982001)(59766001)(83072002)(81542001)(51856001)(85852003)(33646001)(69226001)(54356001)(81686001)(54316002)(53806001)(427584002)(24736002); DIR:OUT; SFP:1101; SCL:1; SRVR:AM3PR03MB529; H:AM3PR03MB532.eurprd03.prod.outlook.com; CLIP:5.153.9.202; FPR:; RD:InfoNoRecords; MX:1; A:1; LANG:en; 
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: ecitele.com
Cc: "samante@apple.com" <samante@apple.com>, "Yaakov Stein \(yaakov_s@rad.com\)" <yaakov_s@rad.com>, "cpignata@cisco.com" <cpignata@cisco.com>, "kireeti@juniper.net" <kireeti@juniper.net>, "mpls@ietf.org" <mpls@ietf.org>, "curtis@occnc.com" <curtis@occnc.com>, "pwe3 \(pwe3@ietf.org\)" <pwe3@ietf.org>
Subject: Re: [PWE3] Pseudowire Sequence Number in draft-ietf-mpls-forwarding: a minor comment
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Pseudowire Emulation Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 12 Dec 2013 05:49:40 -0000

Curtis,=0A=
Lots of hanks for a long and detailed explanation.=0A=
=0A=
It appears that your original comment about the need of jitter buffer refer=
ed to TDM (or TDM-like) PWs (bit-stream PWs in the Architecture RFC). If th=
is was indeed the case, there is nothing to argue about, because I agree co=
mpletely that jitter buffer is absolutely necessary for these.=0A=
=0A=
My impression from reading the original text has been that it referred to A=
LL kinds of PWs (bit-stream, celland packet) alike. Apparently this has bee=
n my mis-interptetation; if this is indeed so, then maybe some clarificatio=
n (placing the jiter buffer discussion in the proper context) would hopeful=
ly help.=0A=
=0A=
Regards,=0A=
     Sasha=0A=
________________________________________=0A=
From: Curtis Villamizar <curtis@ipv6.occnc.com>=0A=
Sent: Thursday, December 12, 2013 6:53 AM=0A=
To: Alexander Vainshtein=0A=
Cc: curtis@occnc.com; curtis@ipv6.occnc.com; kireeti@juniper.net; samante@a=
pple.com; agmalis@gmail.com; cpignata@cisco.com; mpls@ietf.org; Yaakov Stei=
n (yaakov_s@rad.com); pwe3 (pwe3@ietf.org)=0A=
Subject: Re: [PWE3] Pseudowire Sequence Number in draft-ietf-mpls-forwardin=
g: a minor comment=0A=
=0A=
In message <774d74926b684ffba7f4f89ace758547@AM3PR03MB532.eurprd03.prod.out=
look.com>=0A=
Alexander Vainshtein writes:=0A=
=0A=
> Curtis,=0A=
> Lots of thanks for sending out the new text.=0A=
>=0A=
> I still have a couple of issues with this version of the text: one=0A=
> technical and one editorial.=0A=
>=0A=
> The technical issue is about the fragment "A small jitter buffer is=0A=
> always necessary".=0A=
>=0A=
> I am not sure this is correct, since I am aware of several PW=0A=
> implementations that pass the payload of a received PW packet directly=0A=
> for transmission via the corresdponding attachment circuit. Of course=0A=
> this payload would be stored in some Tx queue associated with the=0A=
> attachment circuit and controlled by the appropriate egress scheduler,=0A=
> but IMO this does not constitue a PW jitter bufer, since the PW=0A=
> interworking function does not exersize any control over these=0A=
> queues.=0A=
=0A=
Well if its a technical argument you want, then here goes ...=0A=
=0A=
Even in pure TDM systems some jitter exist due to the longer time it=0A=
takes if multiple passes of the FEC algorithm are needed.  In that=0A=
case there is a very small jitter buffer that can be set to the=0A=
maximum needed for a worst case FEC, or set lower to decrease delay=0A=
with the potential to make a greater number of errors uncorrectable.=0A=
=0A=
For IP, even if IP EF service is used and there is a very small amount=0A=
of EF traffic, some jitter exists.  For most systems there is some=0A=
jitter crossing the fabric and internal jitter elsewhere.  The egress=0A=
buffer in most chips is very small but needed for that jitter.  For=0A=
TDM, the egress buffer can never run dry or there will be a timing=0A=
slip.=0A=
=0A=
Consider what happens when packets arrive late in a system with only a=0A=
non-zero egress buffer.  For example, assume 1% of packets arrive=0A=
about one packet time late (one other EF packet in queue somewhere on=0A=
the path), 0.1% arrive two packets late.  Note that this would be an=0A=
extremely light EF load.  Generally most packets arrive at least zero=0A=
to one minus epsilon packet times late due to a lower priority packet=0A=
partially transmited when the EF packet is moved to the front of the=0A=
queue.  If there is no egress buffer at all or considerably less than=0A=
a packet time, lots of data would be dropped.  If the egress buffer=0A=
could hold just a few packets data drop would be very low.=0A=
=0A=
If a packet arrives late and there is no standing queue the egress=0A=
runs dry, there is a timing slip.  When the packet does arrive a=0A=
little late the packet is sent, albiet late.  Every packet to follow=0A=
is now late by that amount of time (if the egress buffer has not=0A=
overflowed on a later packet).=0A=
=0A=
At that point there is an standing queue in the egress buffer which=0A=
acts as a jitter buffer.  Most packets arrive early.  A few arrive a=0A=
little later but as long as the queue doesn't run dry again, the=0A=
jitter is compensated for.=0A=
=0A=
If the egress buffer is large, then it will tend to grow to the worst=0A=
case packet delay and keep a large standing queue.  This is with no=0A=
reorder and no drop.  If the egress buffer is small (or configured to=0A=
be small) then when a packet arrives very late followed by a set of=0A=
packets in close succession, the buffer runs dry until that first late=0A=
packet arrives.  This packet is transmitted but very late.  Subsequent=0A=
packets arrive and some of them have to be dropped due to the limited=0A=
queue capacity.  This in effect puts a cap on the jitter buffer.=0A=
=0A=
With only an egress buffer there are multiple strategies for dealing=0A=
with dropped packets.=0A=
=0A=
  1.  Just ignore it and send the next one.=0A=
  2.  Put one packet time worth of all zeros in the queue.=0A=
=0A=
Now consider what happens with a dropped packet and a standing queue.=0A=
The first strategy creates a hidden timing slip.  The second strategy=0A=
avoids the timing slip.=0A=
=0A=
So my argument is that the egress buffer is in effect the jitter=0A=
buffer.  When jitter occurs a standing buffer forms that reflects the=0A=
lesser of the limit of the buffer size or the worst case jitter.=0A=
There is always a jitter buffer.  There always needs to be a jitter=0A=
buffer of at least one large packet time, otherwise high loss of data=0A=
will occur.  There should be a jitter buffer that can be made larger=0A=
so that jitter of multiple packet times doesn't turn in to loss.=0A=
=0A=
Therefore I assert that a jitter buffer is always present and is=0A=
always needed because jitter is always non-zero.  Therefore this=0A=
statement is true:=0A=
=0A=
   A small jitter buffer is always necessary and the jitter buffer is=0A=
   needed regardless of whether reordering is done.=0A=
=0A=
> In particular, these queues could not be used for re-ordering=0A=
> misordered PW packets.=0A=
=0A=
That does not mean that they can't be used to compensate for jitter=0A=
which is by definition what a jitter buffer is for.=0A=
=0A=
When reordering is done, the egress buffer is made small and a buffer=0A=
preceding that is used which has some ability to reorder packets.  In=0A=
hardware a circular queue makes sense with packets place according to=0A=
their sequence number.  If you prescribe to the "just insert zeros"=0A=
idea when a packet is dropped, then after moving a packet to the=0A=
egress queue, zero the buffer or mark it as unoccupied and more the=0A=
circular buffer a bit.  If the packet that is later supposed to occupy=0A=
that slot never arrives, then it is already zerod (or marked as=0A=
missing in which case a packet of all zeros is put on the egress=0A=
queue).=0A=
=0A=
So ... reording within a small jitter buffer is not hard to do.=0A=
=0A=
Reordering can be supported with a small jitter buffer but adding=0A=
reordering to a small buffer may be ineffective.  If reordering is due=0A=
to a path change, then the buffer of a small number of packet times=0A=
may yield no improvement.  To be effective in that situation, the=0A=
buffer may need to be larger.  OTOH if moving EF traffic from one=0A=
queue with no standing EF queue to another with no standing EF queue=0A=
and the path change is just moving to another wave on the WDM,=0A=
reordering with a small jitter buffer may help.=0A=
=0A=
> IMHO and FWIW this understanding matches RFC 3985 which mentions (in=0A=
> Section 5.2.1.1 "Frame Ordering") that reodering as the strategy for=0A=
> handling mis-ordered packets introduces additional delay (i.e.,=0A=
> requires a ddicated jitter buffer), while the alternative strategy of=0A=
> discarding mis-ordered packets does not introduce such additional=0A=
> delay.=0A=
=0A=
You quoted the framework and not a TDM document.  Nowhere in that text=0A=
is there mention of a jitter buffer because that text is not specific=0A=
to TDM.=0A=
=0A=
For packet traffic you have no idea if a prior packet is dropped or=0A=
will arrive out of order and so when a drop occurs packets have to be=0A=
held for a non-zero amount of time rather than transmitted as soon as=0A=
they arrive.  This applies to all cell or packet AC, such as FR, ATM,=0A=
Ethernet, etc.=0A=
=0A=
You might want to look at section 5.2.2.1.  Clock Recovery which does=0A=
apply to TDM.  It points to RFC3550 (RTP) which assumes a jitter=0A=
buffer is always needed.=0A=
=0A=
> The editorial issue is about the entire sentence that contains the=0A=
> above-mentioned fragment, i.e., "A small jitter buffer is always=0A=
> necessary and the jitter buffer is needed regardless of whether=0A=
> reordering is done" - to me this looks like an unnecessary repetition=0A=
> if if it were techically correct.=0A=
=0A=
The second part of the sentence was to emphasis that the need for a=0A=
jitter buffer is not contingent on implementation or reordering.=0A=
Perhaps it would be more clear if the two points were separated.  How=0A=
about this=0A=
=0A=
 OLD new sentence=0A=
=0A=
   A small jitter buffer is always necessary and the jitter buffer=0A=
   is needed regardless of whether reordering is done.=0A=
=0A=
 NEW new sentence=0A=
=0A=
   A small jitter buffer is always necessary.  A jitter buffer is=0A=
   needed regardless of whether reordering is done.=0A=
=0A=
> Hence I would like to suggest discrading the problematic sentence as=0A=
> the simplest way to resolve both issues.=0A=
=0A=
I think the sentence provides an important clarification.  I think the=0A=
need to have this discussion proves that the clarification is needed.=0A=
=0A=
If we can agree on keeping this, I can submit the updated draft.=0A=
=0A=
> Hopefully these notes will e helpful.=0A=
>=0A=
> Regards,=0A=
>      Sasha=0A=
=0A=
Thanks again for the review and good comments.=0A=
=0A=
Regards,=0A=
=0A=
Curtis=0A=
=0A=
=0A=
> ________________________________________=0A=
> From: Curtis Villamizar <curtis@occnc.com>=0A=
> Sent: Tuesday, December 10, 2013 5:47 PM=0A=
> To: Alexander Vainshtein=0A=
> Cc: curtis@ipv6.occnc.com; curtis@occnc.com; kireeti@juniper.net; samante=
@apple.com; agmalis@gmail.com; cpignata@cisco.com; mpls@ietf.org; Yaakov St=
ein (yaakov_s@rad.com); pwe3 (pwe3@ietf.org)=0A=
> Subject: Re: [PWE3] Pseudowire Sequence Number in draft-ietf-mpls-forward=
ing: a minor comment=0A=
>=0A=
> In message <F9336571731ADE42A5397FC831CEAA025AC56C9D@ILPTWPVEXMB02.ecitel=
e.com>=0A=
> Alexander Vainshtein writes:=0A=
> >=0A=
> > Curtis,=0A=
> >=0A=
> > Lots of thanks for a prompt and very detailed response.=0A=
> > May I suggest an alternative version of the following text fragment?=0A=
> >=0A=
> > <Curtis>=0A=
> > >   Identifying the position of any lost packets is important=0A=
> > >    for PW services which are attempting to reconstruct a bit stream=
=0A=
> > >    which maintains bit timing, such as time division multiplexing (TD=
M)=0A=
> > >    services.  TDM and other PW services which require strict ordering=
=0A=
> > >    also require that misordered packets be either dropped or reordere=
d.=0A=
>=0A=
> Invalid XML - you didn't close this element.  :-)=0A=
>=0A=
> >  <Sasha>=0A=
> >=0A=
> >    Identifying lost PW packets and exact amount of lost payload is=0A=
> >    critical for PW services which maintain bit timing, such as Time=0A=
> >    Division Multiplexing (TDM) services since these services MUST=0A=
> >    compensate lost payload on a bit-for-bit basis.=0A=
> >=0A=
> >    With these services PW packets that have been received out of order=
=0A=
> >    also MUST also be identified and may be either re-ordered or=0A=
> >    dropped.  Reordering requires, in addition to sequence numbering, a=
=0A=
> >    "de-jitter buffer" in the egress PE, and ability to reorder is=0A=
> >    limited by the depth of this buffer. The down side of maintaining a=
=0A=
> >    de-jitter buffer is added end-to-end service delay.=0A=
> >=0A=
> >   </Sasha>=0A=
>=0A=
> Accepted with a small change.=0A=
>=0A=
> After the words "down side"=0A=
> s/de-jitter buffer/large jitter buffer/=0A=
> Elsewhere=0A=
> s/de-jitter buffer/jitter buffer/g=0A=
> Then add the sentence.=0A=
>=0A=
>    A small jitter buffer is always necessary and the jitter buffer=0A=
>    is needed regardless of whether reordering is done.=0A=
>=0A=
> This yields a slightly changed second paragraph.=0A=
>=0A=
>    With these services PW packets that have been received out of order=0A=
>    also MUST also be identified and may be either re-ordered or=0A=
>    dropped.  Reordering requires, in addition to sequence numbering, a=0A=
>    "jitter buffer" in the egress PE, and ability to reorder is limited=0A=
>    by the depth of this buffer. The down side of maintaining a large=0A=
>    jitter buffer is added end-to-end service delay.  A small jitter=0A=
>    buffer is always necessary and the jitter buffer is needed=0A=
>    regardless of whether reordering is done.=0A=
>=0A=
> Is this wording OK with you?=0A=
>=0A=
> Curtis=0A=
>=0A=
> > Hopefully this will be useful.=0A=
> >=0A=
> >=0A=
> > Regards,=0A=
> >      Sasha=0A=
> >=0A=
> > > -----Original Message-----=0A=
> > > From: Curtis Villamizar [mailto:curtis@ipv6.occnc.com]=0A=
> > > Sent: Monday, November 25, 2013 8:30 PM=0A=
> > > To: Alexander Vainshtein=0A=
> > > Cc: curtis@occnc.com; kireeti@juniper.net; samante@apple.com;=0A=
> > > agmalis@gmail.com; cpignata@cisco.com; mpls@ietf.org; Yaakov Stein=0A=
> > > (yaakov_s@rad.com); pwe3 (pwe3@ietf.org)=0A=
> > > Subject: Re: [PWE3] Pseudowire Sequence Number in draft-ietf-mpls-=0A=
> > > forwarding: a minor comment=0A=
> > >=0A=
> > >=0A=
> > > In message=0A=
> > > <F9336571731ADE42A5397FC831CEAA025392F92F@ILPTWPVEXMB01.ecitele.c=0A=
> > > om>=0A=
> > > Alexander Vainshtein writes:=0A=
> > > >=0A=
> > > > Hi all,=0A=
> > > >=0A=
> > > > I would like to comment on the text in Section 2.1.8.1 "Pseudowire=
=0A=
> > > > Sequence Number" in draft-ietf-mpls-forwarding-03 - MPLS Forwarding=
=0A=
> > > > Compliance and Performance Requirements=0A=
> > > > <http://tools.ietf.org/html/draft-ietf-mpls-forwarding-03>.=0A=
> > > >=0A=
> > > > This section states, in short, that the main drive for using the=0A=
> > > > sequence number in the PW Control Word is handling of packet=0A=
> > > > reordering events. TDM PWs are presented as a major example, with C=
BR=0A=
> > > > ATM services as another example.=0A=
> > > >=0A=
> > > > In fact, this statement is not accurate.=0A=
> > >=0A=
> > > Yes.  You are correct in pointing this out as inaccurate by omitting=
=0A=
> > > the other important function of identifying drops for the purpose of=
=0A=
> > > recunstructing TDM bit streams.=0A=
> > >=0A=
> > > Andy brought up resequencing being a strong provider request.=0A=
> > > Reordering is far more common than loss particularly for high priorit=
y=0A=
> > > services on provider networks and without resequencing reorder result=
s=0A=
> > > in PW loss in what could otherwise be lossless service.=0A=
> > >=0A=
> > > So we should get the base requirements right but still reflect this,=
=0A=
> > > but strictly as advice with no normative wording.  We had used the=0A=
> > > phrase "is beneficial" and will retain that.=0A=
> > >=0A=
> > > Andy brought up the topic.  The incorrect wording in the existing=0A=
> > > draft is my fault.  This text went in fairly early with a lot of othe=
r=0A=
> > > changes and it appears that no one had since given it a careful enoug=
h=0A=
> > > read and review until you came along.=0A=
> > >=0A=
> > > > The main drive for mandating the use of sequence number in TM PWs i=
s=0A=
> > > > the need to detect and count lost packets because the egress PE MUS=
T=0A=
> > > > compensate the lost payload bit for bit.=0A=
> > > >=0A=
> > > > Ability to compensate reordering of PW packets at egress is a side=
=0A=
> > > > effect of (a) sequence number usage and (b) usage of the de-jitter=
=0A=
> > > > buffer in the egress PW. It is not mandatory and in any case is=0A=
> > > > limited by the depth of the de-jitter buffer: re-ordered packets th=
at=0A=
> > > > cannot be accommodated within this buffer are treated as lost.=0A=
> > > >=0A=
> > > > Additional details can be found, e.g., in section 6.2.2 of RFC=0A=
> > > > 4553<http://tools.ietf.org/html/rfc4553>. Ability to re-order=0A=
> > > > mis-ordered PW packets is defined there as OPTIONAL, while replacem=
ent=0A=
> > > > of the payload of lost PW packets is defined as MANDATORY.=0A=
> > >=0A=
> > > The change below at the top of the section more accurately reflects=
=0A=
> > > requirements in the RFCs but still states that resequencing can be=0A=
> > > beneficial.  The comments about EPD and PPD are dropped and therefore=
=0A=
> > > also the informative reference.=0A=
> > >=0A=
> > >  Context:=0A=
> > >=0A=
> > >  2.1.8.1.  Pseudowire Sequence Number=0A=
> > >=0A=
> > >  OLD=0A=
> > >=0A=
> > >    Pseudowire (PW) sequence number support is most important for PW=
=0A=
> > >    payload types with a high expectation of in-order delivery.=0A=
> > >    Resequencing support, rather than dropping at egress on out of ord=
er=0A=
> > >    arrival, is most important for PW payload types with a high=0A=
> > >    expectation of lossless delivery.  For example, TDM payloads requi=
re=0A=
> > >    sequence number support and require resequencing support.  The sam=
e=0A=
> > >    is true of ATM CBR service.  ATM VBR or ABR may have somewhat rela=
xed=0A=
> > >    requirements, but generally require ATM Early Packet Discard (EPD)=
 or=0A=
> > >    ATM Partial Packet Discard (PPD) [ATM-EPD-and-PPD].  Though sequen=
ce=0A=
> > >    number support and resequencing support are beneficial to PW packe=
t=0A=
> > >    oriented payloads such as FR and Ethernet, they are highly desirab=
le=0A=
> > >    but not as strongly required.=0A=
> > >=0A=
> > > NEW=0A=
> > >=0A=
> > >    Pseudowire (PW) sequence number support is most important for PW=
=0A=
> > >    payload types with a high expectation of lossless and/or in-order=
=0A=
> > >    delivery.  Identifying the position of any lost packets is importa=
nt=0A=
> > >    for PW services which are attempting to reconstruct a bit stream=
=0A=
> > >    which maintains bit timing, such as time division multiplexing (TD=
M)=0A=
> > >    services.  TDM and other PW services which require strict ordering=
=0A=
> > >    also require that misordered packets be either dropped or reordere=
d.=0A=
> > >=0A=
> > >    PW services which are not timing critical bit streams in nature ar=
e=0A=
> > >    cell oriented or frame oriented.  Though resequencing support is=
=0A=
> > >    beneficial to PW cell and frame oriented payloads such as ATM, FR =
and=0A=
> > >    Ethernet, they are highly desirable but not required.=0A=
> > >=0A=
> > > NEW (end of subsection after list of possible reording causes)=0A=
> > >=0A=
> > >    In provider networks which use multipath techniques and which may=
=0A=
> > >    occassionally rebalance traffic or which may change PW paths=0A=
> > >    occasionally for other reasons, reordering may be far more common=
=0A=
> > >    than loss.  Where reordering is more common than loss, resequencin=
g=0A=
> > >    packets is beneficial, rather than dropping packets at egress when=
=0A=
> > >    out of order arrival occus.  Resequencing is most important for PW=
=0A=
> > >    payload types with a high expectation of lossless delivery since i=
n=0A=
> > >    such cases out of order delivery within the network results in PW=
=0A=
> > >    loss.=0A=
> > >=0A=
> > > The final paragraph sums up the motivation for highlighting=0A=
> > > resequencing as beneficial and desirable.  It does so without any=0A=
> > > normative wording.=0A=
> > >=0A=
> > > > Hopefully these notes will be useful.=0A=
> > > >=0A=
> > > > Regards,=0A=
> > > >      Sasha=0A=
> > >=0A=
> > > These notes are very useful.  Thank you.=0A=
> > >=0A=
> > > Please let us know if you (and the WG) are OK with the rewording=0A=
> > > proposed above.=0A=
> > >=0A=
> > > Curtis=0A=

From zhangxudong@huawei.com  Wed Dec 11 22:50:36 2013
Return-Path: <zhangxudong@huawei.com>
X-Original-To: pwe3@ietfa.amsl.com
Delivered-To: pwe3@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DD91A1AE18D for <pwe3@ietfa.amsl.com>; Wed, 11 Dec 2013 22:50:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.413
X-Spam-Level: 
X-Spam-Status: No, score=-1.413 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, CN_BODY_35=0.339, MIME_CHARSET_FARAWAY=2.45, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id F0l7M6SNKKdb for <pwe3@ietfa.amsl.com>; Wed, 11 Dec 2013 22:50:34 -0800 (PST)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 158411AE186 for <pwe3@ietf.org>; Wed, 11 Dec 2013 22:50:33 -0800 (PST)
Received: from 172.18.7.190 (EHLO lhreml204-edg.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id AYX18664; Thu, 12 Dec 2013 06:50:27 +0000 (GMT)
Received: from LHREML403-HUB.china.huawei.com (10.201.5.217) by lhreml204-edg.china.huawei.com (172.18.7.223) with Microsoft SMTP Server (TLS) id 14.3.158.1; Thu, 12 Dec 2013 06:50:10 +0000
Received: from SZXEML413-HUB.china.huawei.com (10.82.67.152) by lhreml403-hub.china.huawei.com (10.201.5.217) with Microsoft SMTP Server (TLS) id 14.3.158.1; Thu, 12 Dec 2013 06:50:21 +0000
Received: from SZXEML501-MBS.china.huawei.com ([169.254.5.216]) by szxeml413-hub.china.huawei.com ([10.82.67.152]) with mapi id 14.03.0158.001; Thu, 12 Dec 2013 14:50:12 +0800
From: "Zhangxudong (zhangxudong, VRP)" <zhangxudong@huawei.com>
To: "pwe3@ietf.org" <pwe3@ietf.org>
Thread-Topic: [PWE3] Poll for WG adoption and IPR check of draft-zhang-pwe3-iccp-stp-00
Thread-Index: AQHO9wZn7dqvd9YkiUeNCqeMNJANXg==
Date: Thu, 12 Dec 2013 06:50:11 +0000
Message-ID: <A987F4BC55F40A408FB445FA5B021C34774AE059@SZXEML501-MBS.china.huawei.com>
References: <4552F0907735844E9204A62BBDD325E73369017B@nkgeml508-mbx.china.huawei.com>
In-Reply-To: <4552F0907735844E9204A62BBDD325E73369017B@nkgeml508-mbx.china.huawei.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.111.77.20]
Content-Type: text/plain; charset="gb2312"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Cc: Lizhenbin <lizhenbin@huawei.com>
Subject: Re: [PWE3] Poll for WG adoption and IPR check of draft-zhang-pwe3-iccp-stp-00
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Pseudowire Emulation Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 12 Dec 2013 06:50:37 -0000

KzENCg0KPi0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQo+RnJvbTogV2VuaHVhZmVuZw0KPlNl
bnQ6IFdlZG5lc2RheSwgRGVjZW1iZXIgMTEsIDIwMTMgMzo1NiBQTQ0KPlRvOiBNaW5ndWkgWmhh
bmc7IFlhYWtvdiBTdGVpbjsgQW5kcmV3IEcuIE1hbGlzOyBwd2UzQGlldGYub3JnDQo+U3ViamVj
dDogUmU6IFtQV0UzXSBQb2xsIGZvciBXRyBhZG9wdGlvbiBhbmQgSVBSIGNoZWNrIG9mDQo+ZHJh
ZnQtemhhbmctcHdlMy1pY2NwLXN0cC0wMA0KPg0KPlN1cHBvcnQgYXMgYW4gaW1wbGVtZW50ZXIg
OikNCj4NCj5IdWFmZW5nDQo+DQo+LS0tLS3Tyrz+1K28/i0tLS0tDQo+t6K8/sjLOiBwd2UzIFtt
YWlsdG86cHdlMy1ib3VuY2VzQGlldGYub3JnXSC0+rHtIE1pbmd1aSBaaGFuZw0KPreiy83Ksbzk
OiAyMDEzxOoxMtTCMTHI1SAxNToxOA0KPsrVvP7IyzogWWFha292IFN0ZWluOyBBbmRyZXcgRy4g
TWFsaXM7IHB3ZTNAaWV0Zi5vcmcNCj7W98ziOiBSZTogW1BXRTNdIFBvbGwgZm9yIFdHIGFkb3B0
aW9uIGFuZCBJUFIgY2hlY2sgb2YNCj5kcmFmdC16aGFuZy1wd2UzLWljY3Atc3RwLTAwDQo+DQo+
SGkgWWFha292LA0KPg0KPlRoYW5rcyBmb3IgdGhlIGNvbW1lbnQhDQo+DQo+QXMgSSBrbm93IGZy
b20gdmVuZG9yIGltcGxlbWVudGVycywgJ3JpbmcnIHRvcG9sb2d5IGlzIHdpZGVseSB1c2VkIGJ5
IA0KPmN1c3RvbWVycyBpbiB0aGVpciBEU0xBTSBuZXR3b3Jrcy4gSXQncyBjb21tb24gZm9yIHN1
Y2ggYSBuZXR3b3JrIHRvIA0KPmhhdmUgbXVsdGlwbGUgYXR0YWNoIHBvaW50cyB0byBhbiBTUCdz
IEwyVlBOIG5ldHdvcmsuLi4gRm9yIHN1Y2gga2luZCANCj5vZiBjb25uZWN0aW9ucywgdGhlcmUg
YXJlIHZhcmlvdXMgcHJpdmF0ZSBzb2x1dGlvbnMgdG8gbWVldCBjdXN0b21lcnMnIA0KPnJlcXVp
cmVtZW50cy4gVGhhdCdzIHdoeSB3ZSBkZXNpZ25lZCB0aGlzIHN0YW5kYXJkIHByb3Bvc2FsIGZv
ciBjdXN0b21lcnMuDQo+DQo+SSBmaW5kIGltcGxlbWVudGVycyBhcmUgaW50ZXJlc3RlZCBpbiBz
dWNoIHByb3Bvc2FsLCBmcm9tIHdoaWNoIEkgc2VlIGEgDQo+Y2hhbmNlIHRvIGJyaW5nIGltcGxl
bWVudGF0aW9ucyB0byB0aGUgZXhpc3RpbmcgcHdlMyBkcmFmdC4NCj4NCj5Ob3QgdG8gZGViYXRl
LiBKdXN0IHRvIGFkZCBzb21lIGluZm8uDQo+DQo+UmVnYXJkcywNCj5NaW5ndWkNCj4NCj4+LS0t
LS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCj4+RnJvbTogcHdlMyBbbWFpbHRvOnB3ZTMtYm91bmNl
c0BpZXRmLm9yZ10gT24gQmVoYWxmIE9mIFlhYWtvdiBTdGVpbg0KPj5TZW50OiBNb25kYXksIERl
Y2VtYmVyIDA5LCAyMDEzIDY6NTIgUE0NCj4+VG86IEFuZHJldyBHLiBNYWxpczsgcHdlM0BpZXRm
Lm9yZw0KPj5TdWJqZWN0OiBSZTogW1BXRTNdIFBvbGwgZm9yIFdHIGFkb3B0aW9uIGFuZCBJUFIg
Y2hlY2sgb2YNCj4+ZHJhZnQtemhhbmctcHdlMy1pY2NwLXN0cC0wMA0KPj4NCj4+SSBkbyBub3Qg
c3VwcG9ydCBhZG9wdGlvbiwNCj4+cGFydGx5IGJlY2F1c2UgSSBkb24ndCB0aGluayBQV0UzIHNo
b3VsZCBiZSB0YWtpbmcgb24gYW55IG5ldyB3b3JrLCANCj4+YW5kIHBhcnRseSBiZWNhdXNlIEkg
ZG9uJ3QgdGhpbmsgdGhlIHVzZSBjYXNlIGlzIHN1ZmZpY2llbnRseSBpbnRlcmVzdGluZy4NCj4+
DQo+PlkoSilTDQo+Pg0KPj4NCj4+LS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCj4+RnJvbTog
cHdlMyBbbWFpbHRvOnB3ZTMtYm91bmNlc0BpZXRmLm9yZ10gT24gQmVoYWxmIE9mIEFuZHJldyBH
LiBNYWxpcw0KPj5TZW50OiAwNCBEZWNlbWJlciwgMjAxMyAyMjo1Mw0KPj5UbzogcHdlM0BpZXRm
Lm9yZw0KPj5TdWJqZWN0OiBbUFdFM10gUG9sbCBmb3IgV0cgYWRvcHRpb24gYW5kIElQUiBjaGVj
ayBvZg0KPj5kcmFmdC16aGFuZy1wd2UzLWljY3Atc3RwLTAwDQo+Pg0KPj5UaGlzIGVtYWlsIGJl
Z2lucyBhIHR3byB3ZWVrIHBvbGwgdG8gaGVscCB0aGUgY2hhaXJzIGRldGVybWluZSBpZiANCj4+
dGhlcmUgaXMgY29uc2Vuc3VzIHRvIGFkb3B0IGRyYWZ0LXpoYW5nLXB3ZTMtaWNjcC1zdHAtMDAg
YXMgYW4gUFdFMyANCj4+d29ya2luZyBncm91cCBkcmFmdC4NCj4+DQo+PlRoZSBkcmFmdCBjYW4g
YmUgZm91bmQgaGVyZToNCj4+aHR0cDovL3Rvb2xzLmlldGYub3JnL2h0bWwvZHJhZnQtemhhbmct
cHdlMy1pY2NwLXN0cC0wMA0KPj4NCj4+UGxlYXNlIHJlYWQgdGhlIGRyYWZ0IGFuZCBpbmRpY2F0
ZSB0byB0aGUgbGlzdCBpZiB5b3Ugc3VwcG9ydCANCj4+YWRvcHRpb24sIG9yIGlmIHlvdSBkbyBu
b3Qgc3VwcG9ydCBhZG9wdGlvbiAoZ2l2aW5nIHJlYXNvbnMpLg0KPj4NCj4+UGxlYXNlIG5vdGUg
dGhhdCB0aGlzIGlzIG9ubHkgYSBjYWxsIGZvciBhZG9wdGlvbi4gVGhlcmUgbmVlZHMgdG8gYmUg
DQo+PmNvbnNlbnN1cyB0aGF0IHRoaXMgZHJhZnQgaXMgYSBnb29kIGJhc2lzIGZvciB0aGUgd29y
aywgYnV0IGl0IGRvZXMgDQo+Pm5vdCBuZWVkIHRvIGJlIHBlcmZlY3QgYXQgdGhpcyBzdGFnZS4N
Cj4+DQo+PkNvaW5jaWRlbnRhbGx5LCB3ZSBhcmUgYWxzbyBwb2xsaW5nIGZvciBrbm93bGVkZ2Ug
b2YgYW55IElQUiB0aGF0IA0KPj5hcHBsaWVzIHRvIHRoaXMgZHJhZnQsIHRvIGVuc3VyZSB0aGF0
IElQUiBoYXMgYmVlbiBkaXNjbG9zZWQgaW4gDQo+PmNvbXBsaWFuY2Ugd2l0aCBJRVRGIElQUiBy
dWxlcyAoc2VlIFJGQ3MgMzk3OSwgNDg3OSwgMzY2OSBhbmQgNTM3OCBmb3IgDQo+Pm1vcmUNCj5k
ZXRhaWxzKS4NCj4+DQo+PklmIHlvdSBhcmUgbGlzdGVkIGFzIGEgZG9jdW1lbnQgYXV0aG9yIG9y
IGNvbnRyaWJ1dG9yIHBsZWFzZSByZXNwb25kIA0KPj50byB0aGlzIGVtYWlsIHdoZXRoZXIgb3Ig
bm90IHlvdSBhcmUgYXdhcmUgb2YgYW55IHJlbGV2YW50IElQUi4gVGhlIA0KPj5kcmFmdCB3aWxs
IG5vdCBiZSBhZG9wdGVkIHVudGlsIGEgcmVzcG9uc2UgaGFzIGJlZW4gcmVjZWl2ZWQgZnJvbSBl
YWNoIA0KPj5hdXRob3IgYW5kDQo+Y29udHJpYnV0b3IuDQo+Pg0KPj5JZiB5b3UgYXJlIG9uIHRo
ZSBQV0UzIFdHIGVtYWlsIGxpc3QgYnV0IGFyZSBub3QgbGlzdGVkIGFzIGFuIGF1dGhvciANCj4+
b3IgY29udHJpYnV0b3IsIHRoZW4gcGxlYXNlIGV4cGxpY2l0bHkgcmVzcG9uZCByZWdhcmRpbmcg
SVBSIG9ubHkgaWYgDQo+PnlvdSBhcmUgYXdhcmUgb2YgYW55IElQUiB0aGF0IGhhcyBub3QgeWV0
IGJlZW4gZGlzY2xvc2VkIGluIA0KPj5jb25mb3JtYW5jZSB3aXRoIElFVEYNCj5ydWxlcy4NCj4+
DQo+PlRoZSBwb2xsIGZvciBhZG9wdGlvbiB3aWxsIGNsb3NlIGluIHR3byB3ZWVrcyB0aW1lLCBv
biBXZWRuZXNkYXkgMTh0aCANCj4+RGVjZW1iZXIuDQo+Pg0KPj5CZXN0IHJlZ2FyZHMsDQo+PkFu
ZHkNCj4+X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCj4+
cHdlMyBtYWlsaW5nIGxpc3QNCj4+cHdlM0BpZXRmLm9yZw0KPj5odHRwczovL3d3dy5pZXRmLm9y
Zy9tYWlsbWFuL2xpc3RpbmZvL3B3ZTMNCj4+X19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX18NCj4+cHdlMyBtYWlsaW5nIGxpc3QNCj4+cHdlM0BpZXRmLm9yZw0K
Pj5odHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL3B3ZTMNCj5fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXw0KPnB3ZTMgbWFpbGluZyBsaXN0
DQo+cHdlM0BpZXRmLm9yZw0KPmh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8v
cHdlMw0K

From gregory.mirsky@ericsson.com  Wed Dec 11 23:05:35 2013
Return-Path: <gregory.mirsky@ericsson.com>
X-Original-To: pwe3@ietfa.amsl.com
Delivered-To: pwe3@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 238221AE1A4 for <pwe3@ietfa.amsl.com>; Wed, 11 Dec 2013 23:05:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3U8sWqdyKGn3 for <pwe3@ietfa.amsl.com>; Wed, 11 Dec 2013 23:05:33 -0800 (PST)
Received: from usevmg20.ericsson.net (usevmg20.ericsson.net [198.24.6.45]) by ietfa.amsl.com (Postfix) with ESMTP id C97CF1AE19E for <pwe3@ietf.org>; Wed, 11 Dec 2013 23:05:32 -0800 (PST)
X-AuditID: c618062d-b7f278e000005a8f-ad-52a96034a16c
Received: from EUSAAHC002.ericsson.se (Unknown_Domain [147.117.188.78]) by usevmg20.ericsson.net (Symantec Mail Security) with SMTP id 0A.11.23183.43069A25; Thu, 12 Dec 2013 08:05:24 +0100 (CET)
Received: from EUSAAMB103.ericsson.se ([147.117.188.120]) by EUSAAHC002.ericsson.se ([147.117.188.78]) with mapi id 14.02.0347.000; Thu, 12 Dec 2013 02:05:25 -0500
From: Gregory Mirsky <gregory.mirsky@ericsson.com>
To: Mingui Zhang <zhangmingui@huawei.com>, "Andrew G. Malis" <agmalis@gmail.com>, "pwe3@ietf.org" <pwe3@ietf.org>
Thread-Topic: [PWE3] Poll for WG adoption and IPR check	of draft-zhang-pwe3-iccp-stp-00
Thread-Index: AQHO8hyIw9QIC/74IEaSdMEFRphGq5pQKrbA
Date: Thu, 12 Dec 2013 07:05:25 +0000
Message-ID: <7347100B5761DC41A166AC17F22DF1121B732ECB@eusaamb103.ericsson.se>
References: <CAA=duU1X6SWzxNOVdXJHA4TsxnVf6u4jGO=0MaoYkc-661XWDw@mail.gmail.com> <7347100B5761DC41A166AC17F22DF1121B723A1F@eusaamb103.ericsson.se> <4552F0907735844E9204A62BBDD325E73368ED8E@nkgeml508-mbx.china.huawei.com>
In-Reply-To: <4552F0907735844E9204A62BBDD325E73368ED8E@nkgeml508-mbx.china.huawei.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [147.117.188.134]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrNLMWRmVeSWpSXmKPExsUyuXSPn65Jwsogg0fTrC1OPz/FZtH3aQuL xZW5jWwOzB47Z91l92g58pbVY8mSn0wBzFFcNimpOZllqUX6dglcGdd3tjMWbFeuuHBzPXsD Y7tsFyMnh4SAicS7k0tZIWwxiQv31rN1MXJxCAkcYZQ4f2sWO0hCSGA5o0TnDGUQm03ASOLF xh6wuIhAscSbo1/BbGGBCInbT24wQsQjJe7fec8MYRtJrFr2ig3EZhFQlVj1/DxQPQcHr4Cv xJ5VzhC7HjBKXLp9gwmkhlMgTGLxgrNg9YxAB30/tQYsziwgLnHryXwmiEMFJJbsOc8MYYtK vHz8D+oBZYklT/azQNTrSCzY/YkNwtaWWLbwNVg9r4CgxMmZT1gmMIrOQjJ2FpKWWUhaZiFp WcDIsoqRo7Q4tSw33chgEyMwQo5JsOnuYNzz0vIQozQHi5I475e3zkFCAumJJanZqakFqUXx RaU5qcWHGJk4OKUaGGu/iJdkhV1qtM5Y7WhjXDD79aGtf4/Wvlhuylkh1nNik9Mm+YVat13M j+rMSlihF+yYK3/8ycVnzkpcPbEbzsXJ16e/XShxfYO4vrP9NubGle+ruHe7a18tmb/+5ZZT Akum8jkef1js0W5+PKfu2pcr025eStb7Inki4wrbiRUML/aJTQu0v6rEUpyRaKjFXFScCADf ecDmXgIAAA==
Subject: Re: [PWE3] Poll for WG adoption and IPR check	of	draft-zhang-pwe3-iccp-stp-00
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Pseudowire Emulation Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 12 Dec 2013 07:05:35 -0000

Hi Mingui,
thank you for the extensive explanation. Have to admit, that I still am not=
 convinced that the Fig.2.1 and the description make strong case for new pr=
otocol extension. I think that there are other possibilities, e.g. tunnel B=
PDUs over PW and use RFC 7023 for MPLS and Ethernet OAM interworking. Do yo=
u think that will work?

	Regards,
		Greg

-----Original Message-----
From: Mingui Zhang [mailto:zhangmingui@huawei.com]=20
Sent: Thursday, December 05, 2013 4:46 PM
To: Gregory Mirsky; Andrew G. Malis; pwe3@ietf.org
Subject: RE: [PWE3] Poll for WG adoption and IPR check of draft-zhang-pwe3-=
iccp-stp-00

Hi Greg,

Thanks for attention. This solution is designed for the use case that geo-d=
ispersed DSLAMs running STP need enhance the reliability of the connections=
 between the entire STP network and the carrier network.

Want to address several key points here: 1. These DSLAMs are running STP. 2=
. These DSLAMs are not geo-close to each other. Multiple DSLAMs are connect=
ed to the carrier network at different locations. 3. When one connection to=
 the carrier network fails, customers wish a connection in another location=
 can continue to work after the re-convergence of the STP rather than compr=
omising the whole STP network. The failure of the connection may be due to =
the failure of the PE, the AC or even the CE (a DSLAM) itself. 4. Customers=
 want to balance the load among those connections, therefore all these conn=
ections need be active.=20

Please note that the draft is not proposed to replace anything. I agree wit=
h you that the application "can be supported". That's why we want to introd=
uce the proposal into the ICCP draft as an _additional_ application. Curren=
tly, there are two applications in the ICCP draft, PW-RED and mLACP. These =
two applications are not applicable to above use case to meet the requireme=
nts of customers.=20

If I misunderstood anything, please correct me.

--
Mingui

>-----Original Message-----
>From: pwe3 [mailto:pwe3-bounces@ietf.org] On Behalf Of Gregory Mirsky
>Sent: Thursday, December 05, 2013 5:59 AM
>To: Andrew G. Malis; pwe3@ietf.org
>Subject: Re: [PWE3] Poll for WG adoption and IPR check of
>draft-zhang-pwe3-iccp-stp-00
>
>Hi,
>I think that the proposal would benefit from stronger description of=20
>use case(s) that it intended to address. At this time, the topology=20
>presented in Fig.2.1 can be supported with what already is defined in=20
>draft-ietf-pwe3-iccp-12. Hence, no/do not support
>
>	Regards,
>		Greg
>
>-----Original Message-----
>From: pwe3 [mailto:pwe3-bounces@ietf.org] On Behalf Of Andrew G. Malis
>Sent: Wednesday, December 04, 2013 12:53 PM
>To: pwe3@ietf.org
>Subject: [PWE3] Poll for WG adoption and IPR check of
>draft-zhang-pwe3-iccp-stp-00
>
>This email begins a two week poll to help the chairs determine if there=20
>is consensus to adopt draft-zhang-pwe3-iccp-stp-00 as an PWE3 working=20
>group draft.
>
>The draft can be found here:
>http://tools.ietf.org/html/draft-zhang-pwe3-iccp-stp-00
>
>Please read the draft and indicate to the list if you support adoption,=20
>or if you do not support adoption (giving reasons).
>
>Please note that this is only a call for adoption. There needs to be=20
>consensus that this draft is a good basis for the work, but it does not=20
>need to be perfect at this stage.
>
>Coincidentally, we are also polling for knowledge of any IPR that=20
>applies to this draft, to ensure that IPR has been disclosed in=20
>compliance with IETF IPR rules (see RFCs 3979, 4879, 3669 and 5378 for mor=
e details).
>
>If you are listed as a document author or contributor please respond to=20
>this email whether or not you are aware of any relevant IPR. The draft=20
>will not be adopted until a response has been received from each author an=
d contributor.
>
>If you are on the PWE3 WG email list but are not listed as an author or=20
>contributor, then please explicitly respond regarding IPR only if you=20
>are aware of any IPR that has not yet been disclosed in conformance with I=
ETF rules.
>
>The poll for adoption will close in two weeks time, on Wednesday 18th=20
>December.
>
>Best regards,
>Andy
>_______________________________________________
>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 yshen@juniper.net  Thu Dec 12 05:37:40 2013
Return-Path: <yshen@juniper.net>
X-Original-To: pwe3@ietfa.amsl.com
Delivered-To: pwe3@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 85C721AD9A9 for <pwe3@ietfa.amsl.com>; Thu, 12 Dec 2013 05:37:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level: 
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TMcpWcy2cQhF for <pwe3@ietfa.amsl.com>; Thu, 12 Dec 2013 05:37:38 -0800 (PST)
Received: from va3outboundpool.messaging.microsoft.com (va3ehsobe005.messaging.microsoft.com [216.32.180.31]) by ietfa.amsl.com (Postfix) with ESMTP id 2963D1AC7F0 for <pwe3@ietf.org>; Thu, 12 Dec 2013 05:37:37 -0800 (PST)
Received: from mail112-va3-R.bigfish.com (10.7.14.254) by VA3EHSOBE007.bigfish.com (10.7.40.11) with Microsoft SMTP Server id 14.1.225.22; Thu, 12 Dec 2013 13:37:31 +0000
Received: from mail112-va3 (localhost [127.0.0.1])	by mail112-va3-R.bigfish.com (Postfix) with ESMTP id AA9434C0159;	Thu, 12 Dec 2013 13:37:31 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.240.101; KIP:(null); UIP:(null); IPV:NLI; H:BL2PRD0510HT002.namprd05.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: 2
X-BigFish: VPS2(zzzz1f42h2148h208ch1ee6h1de0h1fdah2073h2146h1202h1e76h2189h1d1ah1d2ah1fc6hzc2hz1de097hz2fh109h2a8h839h944hd24hf0ah1220h1288h12a5h12a9h12bdh137ah13b6h1441h1504h1537h153bh162dh1631h1758h18e1h1946h19b5h19ceh1ad9h1b0ah224fh1d07h1d0ch1d2eh1d3fh1dc1h1de9h1dfeh1dffh1fe8h1ff5h2216h22d0h2336h9a9j1155h)
Received-SPF: pass (mail112-va3: domain of juniper.net designates 157.56.240.101 as permitted sender) client-ip=157.56.240.101; envelope-from=yshen@juniper.net; helo=BL2PRD0510HT002.namprd05.prod.outlook.com ; .outlook.com ; 
X-Forefront-Antispam-Report-Untrusted: SFV:NSPM; SFS:(10009001)(189002)(199002)(49866001)(79102001)(90146001)(87266001)(83322001)(19580395003)(76576001)(74366001)(74316001)(2656002)(4396001)(85852003)(87936001)(83072002)(69226001)(46102001)(47736001)(74706001)(76482001)(1941001)(76796001)(76786001)(33646001)(54316002)(56816005)(31966008)(56776001)(54356001)(50986001)(81686001)(59766001)(51856001)(53806001)(76176001)(47976001)(63696002)(74502001)(80022001)(81816001)(80976001)(81542001)(77982001)(74876001)(65816001)(66066001)(47446002)(74662001)(85306002)(81342001)(24736002); DIR:OUT; SFP:1101; SCL:1; SRVR:BY2PR05MB160; H:BY2PR05MB728.namprd05.prod.outlook.com; CLIP:66.129.241.19; FPR:; RD:InfoNoRecords; MX:1; A:1; LANG:en; 
Received: from mail112-va3 (localhost.localdomain [127.0.0.1]) by mail112-va3 (MessageSwitch) id 1386855442642719_11850; Thu, 12 Dec 2013 13:37:22 +0000 (UTC)
Received: from VA3EHSMHS004.bigfish.com (unknown [10.7.14.229])	by mail112-va3.bigfish.com (Postfix) with ESMTP id 9061342024D; Thu, 12 Dec 2013 13:37:22 +0000 (UTC)
Received: from BL2PRD0510HT002.namprd05.prod.outlook.com (157.56.240.101) by VA3EHSMHS004.bigfish.com (10.7.99.14) with Microsoft SMTP Server (TLS) id 14.16.227.3; Thu, 12 Dec 2013 13:37:20 +0000
Received: from BY2PR05MB160.namprd05.prod.outlook.com (10.242.39.151) by BL2PRD0510HT002.namprd05.prod.outlook.com (10.255.100.37) with Microsoft SMTP Server (TLS) id 14.16.383.1; Thu, 12 Dec 2013 13:37:19 +0000
Received: from BY2PR05MB728.namprd05.prod.outlook.com (10.141.223.25) by BY2PR05MB160.namprd05.prod.outlook.com (10.242.39.151) with Microsoft SMTP Server (TLS) id 15.0.837.10; Thu, 12 Dec 2013 13:37:17 +0000
Received: from BY2PR05MB728.namprd05.prod.outlook.com ([10.141.223.25]) by BY2PR05MB728.namprd05.prod.outlook.com ([10.141.223.25]) with mapi id 15.00.0837.004; Thu, 12 Dec 2013 13:37:16 +0000
From: Yimin Shen <yshen@juniper.net>
To: "matthew.bocci@alcatel-lucent.com" <matthew.bocci@alcatel-lucent.com>, "agmalis@gmail.com" <agmalis@gmail.com>, "stbryant@cisco.com" <stbryant@cisco.com>, "adrian@olddog.co.uk" <adrian@olddog.co.uk>, Adrian Farrel <afarrel@juniper.net>
Thread-Topic: PWE3 draft-shen-pwe3-endpoint-fast-protection
Thread-Index: Ac73P0T/HBM6FQ6jQO6sDQer/guRAA==
Date: Thu, 12 Dec 2013 13:37:16 +0000
Message-ID: <70b3084d60364d09b936284ab47be52c@BY2PR05MB728.namprd05.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [66.129.241.19]
x-forefront-prvs: 0058ABBBC7
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
X-FOPE-CONNECTOR: Id%0$Dn%*$RO%0$TLS%0$FQDN%$TlsDn%
Cc: "pwe3@ietf.org" <pwe3@ietf.org>
Subject: [PWE3] PWE3 draft-shen-pwe3-endpoint-fast-protection
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Pseudowire Emulation Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 12 Dec 2013 13:37:40 -0000

Hi chairs,

draft-shen-pwe3-endpoint-fast-protection-04.txt seems to be stuck. It looks=
 like you got a positive response to the poll for working group adoption, a=
nd you received responses from all but one of the co-authors to your questi=
on about IPR. The final author, Rahul Aggarwal, seems to be missing in acti=
on.=20

(BTW, Juniper has done IPR disclosure for two patents related to this draft=
.)

Do you intend to block advancement of the draft until you get a response fr=
om Rahul, or can you just bring the situation to the attention of the worki=
ng group and move on? I should point out that the I-D does contain the boil=
erplate statement that all authors will follow the terms of BCP and the IET=
F Trust Legal Provisions.


Regards,

/Yimin





From matthew.bocci@alcatel-lucent.com  Thu Dec 12 06:31:11 2013
Return-Path: <matthew.bocci@alcatel-lucent.com>
X-Original-To: pwe3@ietfa.amsl.com
Delivered-To: pwe3@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7722C1ADF26 for <pwe3@ietfa.amsl.com>; Thu, 12 Dec 2013 06:31:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.9
X-Spam-Level: 
X-Spam-Status: No, score=-6.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yeRUk-lX7194 for <pwe3@ietfa.amsl.com>; Thu, 12 Dec 2013 06:31:08 -0800 (PST)
Received: from ihemail3.lucent.com (ihemail3.lucent.com [135.245.0.37]) by ietfa.amsl.com (Postfix) with ESMTP id A31311ADBD5 for <pwe3@ietf.org>; Thu, 12 Dec 2013 06:31:08 -0800 (PST)
Received: from fr712usmtp2.zeu.alcatel-lucent.com (h135-239-2-42.lucent.com [135.239.2.42]) by ihemail3.lucent.com (8.13.8/IER-o) with ESMTP id rBCEUtVd010642 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Thu, 12 Dec 2013 08:30:57 -0600 (CST)
Received: from FR711WXCHHUB01.zeu.alcatel-lucent.com (fr711wxchhub01.zeu.alcatel-lucent.com [135.239.2.111]) by fr712usmtp2.zeu.alcatel-lucent.com (GMO) with ESMTP id rBCEUkBH010345 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 12 Dec 2013 15:30:55 +0100
Received: from FR711WXCHMBA05.zeu.alcatel-lucent.com ([169.254.1.146]) by FR711WXCHHUB01.zeu.alcatel-lucent.com ([135.239.2.111]) with mapi id 14.02.0247.003; Thu, 12 Dec 2013 15:30:53 +0100
From: "Bocci, Matthew (Matthew)" <matthew.bocci@alcatel-lucent.com>
To: Yimin Shen <yshen@juniper.net>, "agmalis@gmail.com" <agmalis@gmail.com>, "stbryant@cisco.com" <stbryant@cisco.com>, "adrian@olddog.co.uk" <adrian@olddog.co.uk>, Adrian Farrel <afarrel@juniper.net>
Thread-Topic: PWE3 draft-shen-pwe3-endpoint-fast-protection
Thread-Index: Ac73P0T/HBM6FQ6jQO6sDQer/guRAP///jWA
Date: Thu, 12 Dec 2013 14:30:52 +0000
Message-ID: <CECF788C.59507%matthew.bocci@alcatel-lucent.com>
References: <70b3084d60364d09b936284ab47be52c@BY2PR05MB728.namprd05.prod.outlook.com>
In-Reply-To: <70b3084d60364d09b936284ab47be52c@BY2PR05MB728.namprd05.prod.outlook.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.3.9.131030
x-originating-ip: [135.239.27.39]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <CE3AE1B54760B046A6DB9155542AD017@exchange.lucent.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.37
Cc: "pwe3@ietf.org" <pwe3@ietf.org>
Subject: Re: [PWE3] PWE3 draft-shen-pwe3-endpoint-fast-protection
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Pseudowire Emulation Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 12 Dec 2013 14:31:11 -0000

Hi Yimin

I think that given the general support for this, it makes sense to adopt
it, but I need to make sure the WG is aware of the fact that one of the
co-authors is not responding. I=B9ll send a note to the list about this.
There will be another call for IPR when we go through WG last call, anyway.

Matthew

On 12/12/2013 13:37, "Yimin Shen" <yshen@juniper.net> wrote:

>Hi chairs,
>
>draft-shen-pwe3-endpoint-fast-protection-04.txt seems to be stuck. It
>looks like you got a positive response to the poll for working group
>adoption, and you received responses from all but one of the co-authors
>to your question about IPR. The final author, Rahul Aggarwal, seems to be
>missing in action.
>
>(BTW, Juniper has done IPR disclosure for two patents related to this
>draft.)
>
>Do you intend to block advancement of the draft until you get a response
>from Rahul, or can you just bring the situation to the attention of the
>working group and move on? I should point out that the I-D does contain
>the boilerplate statement that all authors will follow the terms of BCP
>and the IETF Trust Legal Provisions.
>
>
>Regards,
>
>/Yimin
>
>
>
>


From yinyuanbin@huawei.com  Thu Dec 12 03:34:58 2013
Return-Path: <yinyuanbin@huawei.com>
X-Original-To: pwe3@ietfa.amsl.com
Delivered-To: pwe3@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 742371A1F48 for <pwe3@ietfa.amsl.com>; Thu, 12 Dec 2013 03:34:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.087
X-Spam-Level: **
X-Spam-Status: No, score=2.087 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, CHARSET_FARAWAY_HEADER=3.2, CN_BODY_35=0.339, MIME_8BIT_HEADER=0.3, MIME_CHARSET_FARAWAY=2.45, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fG3Aix_pos2z for <pwe3@ietfa.amsl.com>; Thu, 12 Dec 2013 03:34:56 -0800 (PST)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 113781AE23A for <pwe3@ietf.org>; Thu, 12 Dec 2013 03:34:55 -0800 (PST)
Received: from 172.18.7.190 (EHLO lhreml204-edg.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BBH53024; Thu, 12 Dec 2013 11:34:49 +0000 (GMT)
Received: from LHREML404-HUB.china.huawei.com (10.201.5.218) by lhreml204-edg.china.huawei.com (172.18.7.223) with Microsoft SMTP Server (TLS) id 14.3.158.1; Thu, 12 Dec 2013 11:34:37 +0000
Received: from NKGEML408-HUB.china.huawei.com (10.98.56.39) by lhreml404-hub.china.huawei.com (10.201.5.218) with Microsoft SMTP Server (TLS) id 14.3.158.1; Thu, 12 Dec 2013 11:34:48 +0000
Received: from NKGEML507-MBS.china.huawei.com ([169.254.6.75]) by nkgeml408-hub.china.huawei.com ([10.98.56.39]) with mapi id 14.03.0158.001; Thu, 12 Dec 2013 19:34:45 +0800
From: Yinyuanbin <yinyuanbin@huawei.com>
To: "pwe3@ietf.org" <pwe3@ietf.org>
Thread-Topic: [PWE3] Poll for WG adoption and IPR check of draft-zhang-pwe3-iccp-stp-00
Thread-Index: AQHO9wZn7dqvd9YkiUeNCqeMNJANXppQbe8g
Date: Thu, 12 Dec 2013 11:34:44 +0000
Message-ID: <682A038C03AB2446A2DC8E6FEF565C92316E8955@nkgeml507-mbs.china.huawei.com>
References: <4552F0907735844E9204A62BBDD325E73369017B@nkgeml508-mbx.china.huawei.com> <A987F4BC55F40A408FB445FA5B021C34774AE059@SZXEML501-MBS.china.huawei.com>
In-Reply-To: <A987F4BC55F40A408FB445FA5B021C34774AE059@SZXEML501-MBS.china.huawei.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.111.84.134]
Content-Type: text/plain; charset="gb2312"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mailman-Approved-At: Thu, 12 Dec 2013 08:03:55 -0800
Subject: [PWE3] =?gb2312?b?tPC4tDogIFBvbGwgZm9yIFdHIGFkb3B0aW9uIGFuZCBJ?= =?gb2312?b?UFIgY2hlY2sgb2YgZHJhZnQtemhhbmctcHdlMy1pY2NwLXN0cC0wMA==?=
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Pseudowire Emulation Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 12 Dec 2013 11:34:58 -0000

KzENCg0KDQo+LS0tLS3Tyrz+1K28/i0tLS0tDQo+t6K8/sjLOiBwd2UzIFttYWlsdG86cHdlMy1i
b3VuY2VzQGlldGYub3JnXSC0+rHtIE1pbmd1aSBaaGFuZw0KPreiy83KsbzkOiAyMDEzxOoxMtTC
MTHI1SAxNToxOA0KPsrVvP7IyzogWWFha292IFN0ZWluOyBBbmRyZXcgRy4gTWFsaXM7IHB3ZTNA
aWV0Zi5vcmcNCj7W98ziOiBSZTogW1BXRTNdIFBvbGwgZm9yIFdHIGFkb3B0aW9uIGFuZCBJUFIg
Y2hlY2sgb2YNCj5kcmFmdC16aGFuZy1wd2UzLWljY3Atc3RwLTAwDQo+DQo+SGkgWWFha292LA0K
Pg0KPlRoYW5rcyBmb3IgdGhlIGNvbW1lbnQhDQo+DQo+QXMgSSBrbm93IGZyb20gdmVuZG9yIGlt
cGxlbWVudGVycywgJ3JpbmcnIHRvcG9sb2d5IGlzIHdpZGVseSB1c2VkIGJ5IA0KPmN1c3RvbWVy
cyBpbiB0aGVpciBEU0xBTSBuZXR3b3Jrcy4gSXQncyBjb21tb24gZm9yIHN1Y2ggYSBuZXR3b3Jr
IHRvIA0KPmhhdmUgbXVsdGlwbGUgYXR0YWNoIHBvaW50cyB0byBhbiBTUCdzIEwyVlBOIG5ldHdv
cmsuLi4gRm9yIHN1Y2gga2luZCANCj5vZiBjb25uZWN0aW9ucywgdGhlcmUgYXJlIHZhcmlvdXMg
cHJpdmF0ZSBzb2x1dGlvbnMgdG8gbWVldCBjdXN0b21lcnMnDQo+cmVxdWlyZW1lbnRzLiBUaGF0
J3Mgd2h5IHdlIGRlc2lnbmVkIHRoaXMgc3RhbmRhcmQgcHJvcG9zYWwgZm9yIGN1c3RvbWVycy4N
Cj4NCj5JIGZpbmQgaW1wbGVtZW50ZXJzIGFyZSBpbnRlcmVzdGVkIGluIHN1Y2ggcHJvcG9zYWws
IGZyb20gd2hpY2ggSSBzZWUgYSANCj5jaGFuY2UgdG8gYnJpbmcgaW1wbGVtZW50YXRpb25zIHRv
IHRoZSBleGlzdGluZyBwd2UzIGRyYWZ0Lg0KPg0KPk5vdCB0byBkZWJhdGUuIEp1c3QgdG8gYWRk
IHNvbWUgaW5mby4NCj4NCj5SZWdhcmRzLA0KPk1pbmd1aQ0KPg0KPj4tLS0tLU9yaWdpbmFsIE1l
c3NhZ2UtLS0tLQ0KPj5Gcm9tOiBwd2UzIFttYWlsdG86cHdlMy1ib3VuY2VzQGlldGYub3JnXSBP
biBCZWhhbGYgT2YgWWFha292IFN0ZWluDQo+PlNlbnQ6IE1vbmRheSwgRGVjZW1iZXIgMDksIDIw
MTMgNjo1MiBQTQ0KPj5UbzogQW5kcmV3IEcuIE1hbGlzOyBwd2UzQGlldGYub3JnDQo+PlN1Ympl
Y3Q6IFJlOiBbUFdFM10gUG9sbCBmb3IgV0cgYWRvcHRpb24gYW5kIElQUiBjaGVjayBvZg0KPj5k
cmFmdC16aGFuZy1wd2UzLWljY3Atc3RwLTAwDQo+Pg0KPj5JIGRvIG5vdCBzdXBwb3J0IGFkb3B0
aW9uLA0KPj5wYXJ0bHkgYmVjYXVzZSBJIGRvbid0IHRoaW5rIFBXRTMgc2hvdWxkIGJlIHRha2lu
ZyBvbiBhbnkgbmV3IHdvcmssIA0KPj5hbmQgcGFydGx5IGJlY2F1c2UgSSBkb24ndCB0aGluayB0
aGUgdXNlIGNhc2UgaXMgc3VmZmljaWVudGx5IGludGVyZXN0aW5nLg0KPj4NCj4+WShKKVMNCj4+
DQo+Pg0KPj4tLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KPj5Gcm9tOiBwd2UzIFttYWlsdG86
cHdlMy1ib3VuY2VzQGlldGYub3JnXSBPbiBCZWhhbGYgT2YgQW5kcmV3IEcuIE1hbGlzDQo+PlNl
bnQ6IDA0IERlY2VtYmVyLCAyMDEzIDIyOjUzDQo+PlRvOiBwd2UzQGlldGYub3JnDQo+PlN1Ympl
Y3Q6IFtQV0UzXSBQb2xsIGZvciBXRyBhZG9wdGlvbiBhbmQgSVBSIGNoZWNrIG9mDQo+PmRyYWZ0
LXpoYW5nLXB3ZTMtaWNjcC1zdHAtMDANCj4+DQo+PlRoaXMgZW1haWwgYmVnaW5zIGEgdHdvIHdl
ZWsgcG9sbCB0byBoZWxwIHRoZSBjaGFpcnMgZGV0ZXJtaW5lIGlmIA0KPj50aGVyZSBpcyBjb25z
ZW5zdXMgdG8gYWRvcHQgZHJhZnQtemhhbmctcHdlMy1pY2NwLXN0cC0wMCBhcyBhbiBQV0UzIA0K
Pj53b3JraW5nIGdyb3VwIGRyYWZ0Lg0KPj4NCj4+VGhlIGRyYWZ0IGNhbiBiZSBmb3VuZCBoZXJl
Og0KPj5odHRwOi8vdG9vbHMuaWV0Zi5vcmcvaHRtbC9kcmFmdC16aGFuZy1wd2UzLWljY3Atc3Rw
LTAwDQo+Pg0KPj5QbGVhc2UgcmVhZCB0aGUgZHJhZnQgYW5kIGluZGljYXRlIHRvIHRoZSBsaXN0
IGlmIHlvdSBzdXBwb3J0IA0KPj5hZG9wdGlvbiwgb3IgaWYgeW91IGRvIG5vdCBzdXBwb3J0IGFk
b3B0aW9uIChnaXZpbmcgcmVhc29ucykuDQo+Pg0KPj5QbGVhc2Ugbm90ZSB0aGF0IHRoaXMgaXMg
b25seSBhIGNhbGwgZm9yIGFkb3B0aW9uLiBUaGVyZSBuZWVkcyB0byBiZSANCj4+Y29uc2Vuc3Vz
IHRoYXQgdGhpcyBkcmFmdCBpcyBhIGdvb2QgYmFzaXMgZm9yIHRoZSB3b3JrLCBidXQgaXQgZG9l
cyANCj4+bm90IG5lZWQgdG8gYmUgcGVyZmVjdCBhdCB0aGlzIHN0YWdlLg0KPj4NCj4+Q29pbmNp
ZGVudGFsbHksIHdlIGFyZSBhbHNvIHBvbGxpbmcgZm9yIGtub3dsZWRnZSBvZiBhbnkgSVBSIHRo
YXQgDQo+PmFwcGxpZXMgdG8gdGhpcyBkcmFmdCwgdG8gZW5zdXJlIHRoYXQgSVBSIGhhcyBiZWVu
IGRpc2Nsb3NlZCBpbiANCj4+Y29tcGxpYW5jZSB3aXRoIElFVEYgSVBSIHJ1bGVzIChzZWUgUkZD
cyAzOTc5LCA0ODc5LCAzNjY5IGFuZCA1Mzc4IGZvciANCj4+bW9yZQ0KPmRldGFpbHMpLg0KPj4N
Cj4+SWYgeW91IGFyZSBsaXN0ZWQgYXMgYSBkb2N1bWVudCBhdXRob3Igb3IgY29udHJpYnV0b3Ig
cGxlYXNlIHJlc3BvbmQgDQo+PnRvIHRoaXMgZW1haWwgd2hldGhlciBvciBub3QgeW91IGFyZSBh
d2FyZSBvZiBhbnkgcmVsZXZhbnQgSVBSLiBUaGUgDQo+PmRyYWZ0IHdpbGwgbm90IGJlIGFkb3B0
ZWQgdW50aWwgYSByZXNwb25zZSBoYXMgYmVlbiByZWNlaXZlZCBmcm9tIGVhY2ggDQo+PmF1dGhv
ciBhbmQNCj5jb250cmlidXRvci4NCj4+DQo+PklmIHlvdSBhcmUgb24gdGhlIFBXRTMgV0cgZW1h
aWwgbGlzdCBidXQgYXJlIG5vdCBsaXN0ZWQgYXMgYW4gYXV0aG9yIA0KPj5vciBjb250cmlidXRv
ciwgdGhlbiBwbGVhc2UgZXhwbGljaXRseSByZXNwb25kIHJlZ2FyZGluZyBJUFIgb25seSBpZiAN
Cj4+eW91IGFyZSBhd2FyZSBvZiBhbnkgSVBSIHRoYXQgaGFzIG5vdCB5ZXQgYmVlbiBkaXNjbG9z
ZWQgaW4gDQo+PmNvbmZvcm1hbmNlIHdpdGggSUVURg0KPnJ1bGVzLg0KPj4NCj4+VGhlIHBvbGwg
Zm9yIGFkb3B0aW9uIHdpbGwgY2xvc2UgaW4gdHdvIHdlZWtzIHRpbWUsIG9uIFdlZG5lc2RheSAx
OHRoIA0KPj5EZWNlbWJlci4NCj4+DQo+PkJlc3QgcmVnYXJkcywNCj4+QW5keQ0KPj5fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXw0KPj5wd2UzIG1haWxpbmcg
bGlzdA0KPj5wd2UzQGlldGYub3JnDQo+Pmh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlz
dGluZm8vcHdlMw0KPj5fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fXw0KPj5wd2UzIG1haWxpbmcgbGlzdA0KPj5wd2UzQGlldGYub3JnDQo+Pmh0dHBzOi8vd3d3
LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vcHdlMw0KPl9fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fDQo+cHdlMyBtYWlsaW5nIGxpc3QNCj5wd2UzQGlldGYu
b3JnDQo+aHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9wd2UzDQo=

From yangang@huawei.com  Thu Dec 12 03:34:35 2013
Return-Path: <yangang@huawei.com>
X-Original-To: pwe3@ietfa.amsl.com
Delivered-To: pwe3@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 121521A1F64 for <pwe3@ietfa.amsl.com>; Thu, 12 Dec 2013 03:34:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.413
X-Spam-Level: 
X-Spam-Status: No, score=-1.413 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, CN_BODY_35=0.339, MIME_CHARSET_FARAWAY=2.45, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sJyc6acxQhSi for <pwe3@ietfa.amsl.com>; Thu, 12 Dec 2013 03:34:32 -0800 (PST)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id D5B8A1A1F48 for <pwe3@ietf.org>; Thu, 12 Dec 2013 03:34:31 -0800 (PST)
Received: from 172.18.7.190 (EHLO lhreml204-edg.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id AYX47704; Thu, 12 Dec 2013 11:34:25 +0000 (GMT)
Received: from LHREML402-HUB.china.huawei.com (10.201.5.241) by lhreml204-edg.china.huawei.com (172.18.7.223) with Microsoft SMTP Server (TLS) id 14.3.158.1; Thu, 12 Dec 2013 11:34:12 +0000
Received: from nkgeml407-hub.china.huawei.com (10.98.56.38) by lhreml402-hub.china.huawei.com (10.201.5.241) with Microsoft SMTP Server (TLS) id 14.3.158.1; Thu, 12 Dec 2013 11:34:25 +0000
Received: from NKGEML507-MBS.china.huawei.com ([169.254.6.75]) by nkgeml407-hub.china.huawei.com ([10.98.56.38]) with mapi id 14.03.0158.001; Thu, 12 Dec 2013 19:34:18 +0800
From: Yangang <yangang@huawei.com>
To: "pwe3@ietf.org" <pwe3@ietf.org>
Thread-Topic: [PWE3] Poll for WG adoption and IPR check of draft-zhang-pwe3-iccp-stp-00
Thread-Index: AQHO9wZn7dqvd9YkiUeNCqeMNJANXppQbeYA
Date: Thu, 12 Dec 2013 11:34:17 +0000
Message-ID: <D496C972D1A13540A730720631EC73413A3B6634@nkgeml507-mbs.china.huawei.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.111.72.210]
Content-Type: text/plain; charset="gb2312"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mailman-Approved-At: Thu, 12 Dec 2013 08:03:55 -0800
Subject: Re: [PWE3] Poll for WG adoption and IPR check of draft-zhang-pwe3-iccp-stp-00
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Pseudowire Emulation Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 12 Dec 2013 11:34:35 -0000

U3VwcG9ydCBhZG9wdGlvbiENCg0KPi0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQo+RnJvbTog
V2VuaHVhZmVuZw0KPlNlbnQ6IFdlZG5lc2RheSwgRGVjZW1iZXIgMTEsIDIwMTMgMzo1NiBQTQ0K
PlRvOiBNaW5ndWkgWmhhbmc7IFlhYWtvdiBTdGVpbjsgQW5kcmV3IEcuIE1hbGlzOyBwd2UzQGll
dGYub3JnDQo+U3ViamVjdDogUmU6IFtQV0UzXSBQb2xsIGZvciBXRyBhZG9wdGlvbiBhbmQgSVBS
IGNoZWNrIG9mDQo+ZHJhZnQtemhhbmctcHdlMy1pY2NwLXN0cC0wMA0KPg0KPlN1cHBvcnQgYXMg
YW4gaW1wbGVtZW50ZXIgOikNCj4NCj5IdWFmZW5nDQo+DQo+LS0tLS3Tyrz+1K28/i0tLS0tDQo+
t6K8/sjLOiBwd2UzIFttYWlsdG86cHdlMy1ib3VuY2VzQGlldGYub3JnXSC0+rHtIE1pbmd1aSBa
aGFuZw0KPreiy83KsbzkOiAyMDEzxOoxMtTCMTHI1SAxNToxOA0KPsrVvP7IyzogWWFha292IFN0
ZWluOyBBbmRyZXcgRy4gTWFsaXM7IHB3ZTNAaWV0Zi5vcmcNCj7W98ziOiBSZTogW1BXRTNdIFBv
bGwgZm9yIFdHIGFkb3B0aW9uIGFuZCBJUFIgY2hlY2sgb2YNCj5kcmFmdC16aGFuZy1wd2UzLWlj
Y3Atc3RwLTAwDQo+DQo+SGkgWWFha292LA0KPg0KPlRoYW5rcyBmb3IgdGhlIGNvbW1lbnQhDQo+
DQo+QXMgSSBrbm93IGZyb20gdmVuZG9yIGltcGxlbWVudGVycywgJ3JpbmcnIHRvcG9sb2d5IGlz
IHdpZGVseSB1c2VkIGJ5IA0KPmN1c3RvbWVycyBpbiB0aGVpciBEU0xBTSBuZXR3b3Jrcy4gSXQn
cyBjb21tb24gZm9yIHN1Y2ggYSBuZXR3b3JrIHRvIA0KPmhhdmUgbXVsdGlwbGUgYXR0YWNoIHBv
aW50cyB0byBhbiBTUCdzIEwyVlBOIG5ldHdvcmsuLi4gRm9yIHN1Y2gga2luZCANCj5vZiBjb25u
ZWN0aW9ucywgdGhlcmUgYXJlIHZhcmlvdXMgcHJpdmF0ZSBzb2x1dGlvbnMgdG8gbWVldCBjdXN0
b21lcnMnDQo+cmVxdWlyZW1lbnRzLiBUaGF0J3Mgd2h5IHdlIGRlc2lnbmVkIHRoaXMgc3RhbmRh
cmQgcHJvcG9zYWwgZm9yIGN1c3RvbWVycy4NCj4NCj5JIGZpbmQgaW1wbGVtZW50ZXJzIGFyZSBp
bnRlcmVzdGVkIGluIHN1Y2ggcHJvcG9zYWwsIGZyb20gd2hpY2ggSSBzZWUgYSANCj5jaGFuY2Ug
dG8gYnJpbmcgaW1wbGVtZW50YXRpb25zIHRvIHRoZSBleGlzdGluZyBwd2UzIGRyYWZ0Lg0KPg0K
Pk5vdCB0byBkZWJhdGUuIEp1c3QgdG8gYWRkIHNvbWUgaW5mby4NCj4NCj5SZWdhcmRzLA0KPk1p
bmd1aQ0KPg0KPj4tLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KPj5Gcm9tOiBwd2UzIFttYWls
dG86cHdlMy1ib3VuY2VzQGlldGYub3JnXSBPbiBCZWhhbGYgT2YgWWFha292IFN0ZWluDQo+PlNl
bnQ6IE1vbmRheSwgRGVjZW1iZXIgMDksIDIwMTMgNjo1MiBQTQ0KPj5UbzogQW5kcmV3IEcuIE1h
bGlzOyBwd2UzQGlldGYub3JnDQo+PlN1YmplY3Q6IFJlOiBbUFdFM10gUG9sbCBmb3IgV0cgYWRv
cHRpb24gYW5kIElQUiBjaGVjayBvZg0KPj5kcmFmdC16aGFuZy1wd2UzLWljY3Atc3RwLTAwDQo+
Pg0KPj5JIGRvIG5vdCBzdXBwb3J0IGFkb3B0aW9uLA0KPj5wYXJ0bHkgYmVjYXVzZSBJIGRvbid0
IHRoaW5rIFBXRTMgc2hvdWxkIGJlIHRha2luZyBvbiBhbnkgbmV3IHdvcmssIA0KPj5hbmQgcGFy
dGx5IGJlY2F1c2UgSSBkb24ndCB0aGluayB0aGUgdXNlIGNhc2UgaXMgc3VmZmljaWVudGx5IGlu
dGVyZXN0aW5nLg0KPj4NCj4+WShKKVMNCj4+DQo+Pg0KPj4tLS0tLU9yaWdpbmFsIE1lc3NhZ2Ut
LS0tLQ0KPj5Gcm9tOiBwd2UzIFttYWlsdG86cHdlMy1ib3VuY2VzQGlldGYub3JnXSBPbiBCZWhh
bGYgT2YgQW5kcmV3IEcuIE1hbGlzDQo+PlNlbnQ6IDA0IERlY2VtYmVyLCAyMDEzIDIyOjUzDQo+
PlRvOiBwd2UzQGlldGYub3JnDQo+PlN1YmplY3Q6IFtQV0UzXSBQb2xsIGZvciBXRyBhZG9wdGlv
biBhbmQgSVBSIGNoZWNrIG9mDQo+PmRyYWZ0LXpoYW5nLXB3ZTMtaWNjcC1zdHAtMDANCj4+DQo+
PlRoaXMgZW1haWwgYmVnaW5zIGEgdHdvIHdlZWsgcG9sbCB0byBoZWxwIHRoZSBjaGFpcnMgZGV0
ZXJtaW5lIGlmIA0KPj50aGVyZSBpcyBjb25zZW5zdXMgdG8gYWRvcHQgZHJhZnQtemhhbmctcHdl
My1pY2NwLXN0cC0wMCBhcyBhbiBQV0UzIA0KPj53b3JraW5nIGdyb3VwIGRyYWZ0Lg0KPj4NCj4+
VGhlIGRyYWZ0IGNhbiBiZSBmb3VuZCBoZXJlOg0KPj5odHRwOi8vdG9vbHMuaWV0Zi5vcmcvaHRt
bC9kcmFmdC16aGFuZy1wd2UzLWljY3Atc3RwLTAwDQo+Pg0KPj5QbGVhc2UgcmVhZCB0aGUgZHJh
ZnQgYW5kIGluZGljYXRlIHRvIHRoZSBsaXN0IGlmIHlvdSBzdXBwb3J0IA0KPj5hZG9wdGlvbiwg
b3IgaWYgeW91IGRvIG5vdCBzdXBwb3J0IGFkb3B0aW9uIChnaXZpbmcgcmVhc29ucykuDQo+Pg0K
Pj5QbGVhc2Ugbm90ZSB0aGF0IHRoaXMgaXMgb25seSBhIGNhbGwgZm9yIGFkb3B0aW9uLiBUaGVy
ZSBuZWVkcyB0byBiZSANCj4+Y29uc2Vuc3VzIHRoYXQgdGhpcyBkcmFmdCBpcyBhIGdvb2QgYmFz
aXMgZm9yIHRoZSB3b3JrLCBidXQgaXQgZG9lcyANCj4+bm90IG5lZWQgdG8gYmUgcGVyZmVjdCBh
dCB0aGlzIHN0YWdlLg0KPj4NCj4+Q29pbmNpZGVudGFsbHksIHdlIGFyZSBhbHNvIHBvbGxpbmcg
Zm9yIGtub3dsZWRnZSBvZiBhbnkgSVBSIHRoYXQgDQo+PmFwcGxpZXMgdG8gdGhpcyBkcmFmdCwg
dG8gZW5zdXJlIHRoYXQgSVBSIGhhcyBiZWVuIGRpc2Nsb3NlZCBpbiANCj4+Y29tcGxpYW5jZSB3
aXRoIElFVEYgSVBSIHJ1bGVzIChzZWUgUkZDcyAzOTc5LCA0ODc5LCAzNjY5IGFuZCA1Mzc4IGZv
ciANCj4+bW9yZQ0KPmRldGFpbHMpLg0KPj4NCj4+SWYgeW91IGFyZSBsaXN0ZWQgYXMgYSBkb2N1
bWVudCBhdXRob3Igb3IgY29udHJpYnV0b3IgcGxlYXNlIHJlc3BvbmQgDQo+PnRvIHRoaXMgZW1h
aWwgd2hldGhlciBvciBub3QgeW91IGFyZSBhd2FyZSBvZiBhbnkgcmVsZXZhbnQgSVBSLiBUaGUg
DQo+PmRyYWZ0IHdpbGwgbm90IGJlIGFkb3B0ZWQgdW50aWwgYSByZXNwb25zZSBoYXMgYmVlbiBy
ZWNlaXZlZCBmcm9tIGVhY2ggDQo+PmF1dGhvciBhbmQNCj5jb250cmlidXRvci4NCj4+DQo+Pklm
IHlvdSBhcmUgb24gdGhlIFBXRTMgV0cgZW1haWwgbGlzdCBidXQgYXJlIG5vdCBsaXN0ZWQgYXMg
YW4gYXV0aG9yIA0KPj5vciBjb250cmlidXRvciwgdGhlbiBwbGVhc2UgZXhwbGljaXRseSByZXNw
b25kIHJlZ2FyZGluZyBJUFIgb25seSBpZiANCj4+eW91IGFyZSBhd2FyZSBvZiBhbnkgSVBSIHRo
YXQgaGFzIG5vdCB5ZXQgYmVlbiBkaXNjbG9zZWQgaW4gDQo+PmNvbmZvcm1hbmNlIHdpdGggSUVU
Rg0KPnJ1bGVzLg0KPj4NCj4+VGhlIHBvbGwgZm9yIGFkb3B0aW9uIHdpbGwgY2xvc2UgaW4gdHdv
IHdlZWtzIHRpbWUsIG9uIFdlZG5lc2RheSAxOHRoIA0KPj5EZWNlbWJlci4NCj4+DQo+PkJlc3Qg
cmVnYXJkcywNCj4+QW5keQ0KPj5fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fXw0KPj5wd2UzIG1haWxpbmcgbGlzdA0KPj5wd2UzQGlldGYub3JnDQo+Pmh0dHBz
Oi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vcHdlMw0KPj5fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXw0KPj5wd2UzIG1haWxpbmcgbGlzdA0KPj5w
d2UzQGlldGYub3JnDQo+Pmh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vcHdl
Mw0KPl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQo+cHdl
MyBtYWlsaW5nIGxpc3QNCj5wd2UzQGlldGYub3JnDQo+aHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFp
bG1hbi9saXN0aW5mby9wd2UzDQo=

From zhai.hongjun@zte.com.cn  Thu Dec 12 18:34:11 2013
Return-Path: <zhai.hongjun@zte.com.cn>
X-Original-To: pwe3@ietfa.amsl.com
Delivered-To: pwe3@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2F5581AE5E1 for <pwe3@ietfa.amsl.com>; Thu, 12 Dec 2013 18:34:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -97.55
X-Spam-Level: 
X-Spam-Status: No, score=-97.55 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, HTML_MESSAGE=0.001, MIME_CHARSET_FARAWAY=2.45, MSGID_FROM_MTA_HEADER=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.001, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hhG512S56miR for <pwe3@ietfa.amsl.com>; Thu, 12 Dec 2013 18:34:09 -0800 (PST)
Received: from mx5.zte.com.cn (mx5.zte.com.cn [63.217.80.70]) by ietfa.amsl.com (Postfix) with ESMTP id AF1431AE5DE for <pwe3@ietf.org>; Thu, 12 Dec 2013 18:34:08 -0800 (PST)
Received: from mse02.zte.com.cn (unknown [10.30.3.21]) by Websense Email Security Gateway with ESMTPS id A25B21271523 for <pwe3@ietf.org>; Fri, 13 Dec 2013 10:33:53 +0800 (CST)
Received: (from root@localhost) by mse02.zte.com.cn id rBD2XtGc026165 for <pwe3@ietf.org>; Fri, 13 Dec 2013 10:33:55 +0800 (GMT-8) (envelope-from zhai.hongjun@zte.com.cn)
Message-Id: <201312130233.rBD2XtGc026165@mse02.zte.com.cn>
Received: from notes_smtp.zte.com.cn ([10.30.1.239]) by mse02.zte.com.cn with ESMTP id rBD2Tql4016529; Fri, 13 Dec 2013 10:29:52 +0800 (GMT-8) (envelope-from zhai.hongjun@zte.com.cn)
In-Reply-To: <CAA=duU1X6SWzxNOVdXJHA4TsxnVf6u4jGO=0MaoYkc-661XWDw@mail.gmail.com>
To: "Andrew G. Malis" <agmalis@gmail.com>
MIME-Version: 1.0
X-KeepSent: A69E3C91:F4193F32-48257C40:000DA33E; type=4; name=$KeepSent
X-Mailer: Lotus Notes Release 6.5.6 March 06, 2007
From: zhai.hongjun@zte.com.cn
Date: Fri, 13 Dec 2013 10:29:56 +0800
X-MIMETrack: Serialize by Router on notes_smtp/zte_ltd(Release 8.5.3FP1 HF212|May 23, 2012) at 2013-12-13 10:29:43, Serialize complete at 2013-12-13 10:29:43
Content-Type: multipart/alternative; boundary="=_alternative 000E006548257C40_="
X-MAIL: mse02.zte.com.cn rBD2XtGc026165
X-MSS: AUDITRELEASE@mse02.zte.com.cn
Cc: pwe3 <pwe3-bounces@ietf.org>, "pwe3@ietf.org" <pwe3@ietf.org>
Subject: Re: [PWE3] Poll for WG adoption and IPR check of draft-zhang-pwe3-iccp-stp-00
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Pseudowire Emulation Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 13 Dec 2013 02:34:11 -0000

This is a multipart message in MIME format.
--=_alternative 000E006548257C40_=
Content-Type: text/plain; charset="GB2312"
Content-Transfer-Encoding: base64

U3VwcG9ydCB0aGUgYWRvcHRpb24uDQoNCg0KDQoNClRoYW5rcywNCkhvbmdqdW4gWmhhaQ0KLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tDQpBZGQ6IE5vLjY4IFpp
amluZ2h1YSBSb2FkLCBZdWh1YXRhaSBEaXN0cmljdCwNCk5hbmppbmcgQ2l0eSwgUi5QLiBDaGlu
YSwgMjEwMDEyDQoNClRlbDogKzg2IDAyNSA1Mjg3NzM0NQ0KRW1haWw6IHpoYWkuaG9uZ2p1bkB6
dGUuY29tLmNuDQotLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0N
Cg0KDQoNCg0KIkFuZHJldyBHLiBNYWxpcyIgPGFnbWFsaXNAZ21haWwuY29tPiANCreivP7Iyzog
ICJwd2UzIiA8cHdlMy1ib3VuY2VzQGlldGYub3JnPg0KMjAxMy0xMi0wNSAwNDo1Mw0KDQrK1bz+
yMsNCiJwd2UzQGlldGYub3JnIiA8cHdlM0BpZXRmLm9yZz4NCrOty80NCg0K1vfM4g0KW1BXRTNd
IFBvbGwgZm9yIFdHIGFkb3B0aW9uIGFuZCBJUFIgY2hlY2sgb2YgZHJhZnQtemhhbmctcHdlMy1p
Y2NwLXN0cC0wMA0KDQoNCg0KDQoNCg0KVGhpcyBlbWFpbCBiZWdpbnMgYSB0d28gd2VlayBwb2xs
IHRvIGhlbHAgdGhlIGNoYWlycyBkZXRlcm1pbmUgaWYNCnRoZXJlIGlzIGNvbnNlbnN1cyB0byBh
ZG9wdCBkcmFmdC16aGFuZy1wd2UzLWljY3Atc3RwLTAwIGFzIGFuIFBXRTMNCndvcmtpbmcgZ3Jv
dXAgZHJhZnQuDQoNClRoZSBkcmFmdCBjYW4gYmUgZm91bmQgaGVyZToNCmh0dHA6Ly90b29scy5p
ZXRmLm9yZy9odG1sL2RyYWZ0LXpoYW5nLXB3ZTMtaWNjcC1zdHAtMDANCg0KUGxlYXNlIHJlYWQg
dGhlIGRyYWZ0IGFuZCBpbmRpY2F0ZSB0byB0aGUgbGlzdCBpZiB5b3Ugc3VwcG9ydA0KYWRvcHRp
b24sIG9yIGlmIHlvdSBkbyBub3Qgc3VwcG9ydCBhZG9wdGlvbiAoZ2l2aW5nIHJlYXNvbnMpLg0K
DQpQbGVhc2Ugbm90ZSB0aGF0IHRoaXMgaXMgb25seSBhIGNhbGwgZm9yIGFkb3B0aW9uLiBUaGVy
ZSBuZWVkcyB0byBiZQ0KY29uc2Vuc3VzIHRoYXQgdGhpcyBkcmFmdCBpcyBhIGdvb2QgYmFzaXMg
Zm9yIHRoZSB3b3JrLCBidXQgaXQgZG9lcw0Kbm90IG5lZWQgdG8gYmUgcGVyZmVjdCBhdCB0aGlz
IHN0YWdlLg0KDQpDb2luY2lkZW50YWxseSwgd2UgYXJlIGFsc28gcG9sbGluZyBmb3Iga25vd2xl
ZGdlIG9mIGFueSBJUFIgdGhhdA0KYXBwbGllcyB0byB0aGlzIGRyYWZ0LCB0byBlbnN1cmUgdGhh
dCBJUFIgaGFzIGJlZW4gZGlzY2xvc2VkIGluDQpjb21wbGlhbmNlIHdpdGggSUVURiBJUFIgcnVs
ZXMgKHNlZSBSRkNzIDM5NzksIDQ4NzksIDM2NjkgYW5kIDUzNzggZm9yDQptb3JlIGRldGFpbHMp
Lg0KDQpJZiB5b3UgYXJlIGxpc3RlZCBhcyBhIGRvY3VtZW50IGF1dGhvciBvciBjb250cmlidXRv
ciBwbGVhc2UgcmVzcG9uZA0KdG8gdGhpcyBlbWFpbCB3aGV0aGVyIG9yIG5vdCB5b3UgYXJlIGF3
YXJlIG9mIGFueSByZWxldmFudCBJUFIuIFRoZQ0KZHJhZnQgd2lsbCBub3QgYmUgYWRvcHRlZCB1
bnRpbCBhIHJlc3BvbnNlIGhhcyBiZWVuIHJlY2VpdmVkIGZyb20gZWFjaA0KYXV0aG9yIGFuZCBj
b250cmlidXRvci4NCg0KSWYgeW91IGFyZSBvbiB0aGUgUFdFMyBXRyBlbWFpbCBsaXN0IGJ1dCBh
cmUgbm90IGxpc3RlZCBhcyBhbiBhdXRob3INCm9yIGNvbnRyaWJ1dG9yLCB0aGVuIHBsZWFzZSBl
eHBsaWNpdGx5IHJlc3BvbmQgcmVnYXJkaW5nIElQUiBvbmx5IGlmDQp5b3UgYXJlIGF3YXJlIG9m
IGFueSBJUFIgdGhhdCBoYXMgbm90IHlldCBiZWVuIGRpc2Nsb3NlZCBpbg0KY29uZm9ybWFuY2Ug
d2l0aCBJRVRGIHJ1bGVzLg0KDQpUaGUgcG9sbCBmb3IgYWRvcHRpb24gd2lsbCBjbG9zZSBpbiB0
d28gd2Vla3MgdGltZSwgb24gV2VkbmVzZGF5IDE4dGggDQpEZWNlbWJlci4NCg0KQmVzdCByZWdh
cmRzLA0KQW5keQ0KX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X18NCnB3ZTMgbWFpbGluZyBsaXN0DQpwd2UzQGlldGYub3JnDQpodHRwczovL3d3dy5pZXRmLm9y
Zy9tYWlsbWFuL2xpc3RpbmZvL3B3ZTMNCg0KDQo=
--=_alternative 000E006548257C40_=
Content-Type: text/html; charset="GB2312"
Content-Transfer-Encoding: base64

DQo8YnI+PGZvbnQgc2l6ZT0yIGZhY2U9InNhbnMtc2VyaWYiPlN1cHBvcnQgdGhlIGFkb3B0aW9u
LjwvZm9udD4NCjxicj48Zm9udCBzaXplPTIgZmFjZT0ic2Fucy1zZXJpZiI+PGJyPg0KPGJyPg0K
PGJyPg0KPGJyPg0KVGhhbmtzLDxicj4NCkhvbmdqdW4gWmhhaTxicj4NCi0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLTxicj4NCkFkZDogTm8uNjggWmlqaW5naHVh
IFJvYWQsIFl1aHVhdGFpIERpc3RyaWN0LDxicj4NCk5hbmppbmcgQ2l0eSwgUi5QLiBDaGluYSwg
MjEwMDEyPGJyPg0KPGJyPg0KVGVsOiArODYgMDI1IDUyODc3MzQ1PGJyPg0KRW1haWw6IHpoYWku
aG9uZ2p1bkB6dGUuY29tLmNuPGJyPg0KLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tPGJyPg0KPC9mb250Pg0KPGJyPg0KPGJyPg0KPGJyPg0KPHRhYmxlIHdpZHRo
PTEwMCU+DQo8dHIgdmFsaWduPXRvcD4NCjx0ZCB3aWR0aD0zNiU+PGZvbnQgc2l6ZT0xIGZhY2U9
InNhbnMtc2VyaWYiPjxiPiZxdW90O0FuZHJldyBHLiBNYWxpcyZxdW90Ow0KJmx0O2FnbWFsaXNA
Z21haWwuY29tJmd0OzwvYj4gPC9mb250Pg0KPGJyPjxmb250IHNpemU9MSBmYWNlPSJzYW5zLXNl
cmlmIj63orz+yMs6ICZuYnNwOyZxdW90O3B3ZTMmcXVvdDsgJmx0O3B3ZTMtYm91bmNlc0BpZXRm
Lm9yZyZndDs8L2ZvbnQ+DQo8cD48Zm9udCBzaXplPTEgZmFjZT0ic2Fucy1zZXJpZiI+MjAxMy0x
Mi0wNSAwNDo1MzwvZm9udD4NCjx0ZCB3aWR0aD02MyU+DQo8dGFibGUgd2lkdGg9MTAwJT4NCjx0
ciB2YWxpZ249dG9wPg0KPHRkPg0KPGRpdiBhbGlnbj1yaWdodD48Zm9udCBzaXplPTEgZmFjZT0i
c2Fucy1zZXJpZiI+ytW8/sjLPC9mb250PjwvZGl2Pg0KPHRkPjxmb250IHNpemU9MSBmYWNlPSJz
YW5zLXNlcmlmIj4mcXVvdDtwd2UzQGlldGYub3JnJnF1b3Q7ICZsdDtwd2UzQGlldGYub3JnJmd0
OzwvZm9udD4NCjx0ciB2YWxpZ249dG9wPg0KPHRkPg0KPGRpdiBhbGlnbj1yaWdodD48Zm9udCBz
aXplPTEgZmFjZT0ic2Fucy1zZXJpZiI+s63LzTwvZm9udD48L2Rpdj4NCjx0ZD4NCjx0ciB2YWxp
Z249dG9wPg0KPHRkPg0KPGRpdiBhbGlnbj1yaWdodD48Zm9udCBzaXplPTEgZmFjZT0ic2Fucy1z
ZXJpZiI+1vfM4jwvZm9udD48L2Rpdj4NCjx0ZD48Zm9udCBzaXplPTEgZmFjZT0ic2Fucy1zZXJp
ZiI+W1BXRTNdIFBvbGwgZm9yIFdHIGFkb3B0aW9uIGFuZCBJUFINCmNoZWNrIG9mICZuYnNwOyAm
bmJzcDsgJm5ic3A7ICZuYnNwO2RyYWZ0LXpoYW5nLXB3ZTMtaWNjcC1zdHAtMDA8L2ZvbnQ+PC90
YWJsZT4NCjxicj4NCjx0YWJsZT4NCjx0ciB2YWxpZ249dG9wPg0KPHRkPg0KPHRkPjwvdGFibGU+
DQo8YnI+PC90YWJsZT4NCjxicj4NCjxicj4NCjxicj48dHQ+PGZvbnQgc2l6ZT0yPlRoaXMgZW1h
aWwgYmVnaW5zIGEgdHdvIHdlZWsgcG9sbCB0byBoZWxwIHRoZSBjaGFpcnMNCmRldGVybWluZSBp
Zjxicj4NCnRoZXJlIGlzIGNvbnNlbnN1cyB0byBhZG9wdCBkcmFmdC16aGFuZy1wd2UzLWljY3At
c3RwLTAwIGFzIGFuIFBXRTM8YnI+DQp3b3JraW5nIGdyb3VwIGRyYWZ0Ljxicj4NCjxicj4NClRo
ZSBkcmFmdCBjYW4gYmUgZm91bmQgaGVyZTo8YnI+DQpodHRwOi8vdG9vbHMuaWV0Zi5vcmcvaHRt
bC9kcmFmdC16aGFuZy1wd2UzLWljY3Atc3RwLTAwPGJyPg0KPGJyPg0KUGxlYXNlIHJlYWQgdGhl
IGRyYWZ0IGFuZCBpbmRpY2F0ZSB0byB0aGUgbGlzdCBpZiB5b3Ugc3VwcG9ydDxicj4NCmFkb3B0
aW9uLCBvciBpZiB5b3UgZG8gbm90IHN1cHBvcnQgYWRvcHRpb24gKGdpdmluZyByZWFzb25zKS48
YnI+DQo8YnI+DQpQbGVhc2Ugbm90ZSB0aGF0IHRoaXMgaXMgb25seSBhIGNhbGwgZm9yIGFkb3B0
aW9uLiBUaGVyZSBuZWVkcyB0byBiZTxicj4NCmNvbnNlbnN1cyB0aGF0IHRoaXMgZHJhZnQgaXMg
YSBnb29kIGJhc2lzIGZvciB0aGUgd29yaywgYnV0IGl0IGRvZXM8YnI+DQpub3QgbmVlZCB0byBi
ZSBwZXJmZWN0IGF0IHRoaXMgc3RhZ2UuPGJyPg0KPGJyPg0KQ29pbmNpZGVudGFsbHksIHdlIGFy
ZSBhbHNvIHBvbGxpbmcgZm9yIGtub3dsZWRnZSBvZiBhbnkgSVBSIHRoYXQ8YnI+DQphcHBsaWVz
IHRvIHRoaXMgZHJhZnQsIHRvIGVuc3VyZSB0aGF0IElQUiBoYXMgYmVlbiBkaXNjbG9zZWQgaW48
YnI+DQpjb21wbGlhbmNlIHdpdGggSUVURiBJUFIgcnVsZXMgKHNlZSBSRkNzIDM5NzksIDQ4Nzks
IDM2NjkgYW5kIDUzNzggZm9yPGJyPg0KbW9yZSBkZXRhaWxzKS48YnI+DQo8YnI+DQpJZiB5b3Ug
YXJlIGxpc3RlZCBhcyBhIGRvY3VtZW50IGF1dGhvciBvciBjb250cmlidXRvciBwbGVhc2UgcmVz
cG9uZDxicj4NCnRvIHRoaXMgZW1haWwgd2hldGhlciBvciBub3QgeW91IGFyZSBhd2FyZSBvZiBh
bnkgcmVsZXZhbnQgSVBSLiBUaGU8YnI+DQpkcmFmdCB3aWxsIG5vdCBiZSBhZG9wdGVkIHVudGls
IGEgcmVzcG9uc2UgaGFzIGJlZW4gcmVjZWl2ZWQgZnJvbSBlYWNoPGJyPg0KYXV0aG9yIGFuZCBj
b250cmlidXRvci48YnI+DQo8YnI+DQpJZiB5b3UgYXJlIG9uIHRoZSBQV0UzIFdHIGVtYWlsIGxp
c3QgYnV0IGFyZSBub3QgbGlzdGVkIGFzIGFuIGF1dGhvcjxicj4NCm9yIGNvbnRyaWJ1dG9yLCB0
aGVuIHBsZWFzZSBleHBsaWNpdGx5IHJlc3BvbmQgcmVnYXJkaW5nIElQUiBvbmx5IGlmPGJyPg0K
eW91IGFyZSBhd2FyZSBvZiBhbnkgSVBSIHRoYXQgaGFzIG5vdCB5ZXQgYmVlbiBkaXNjbG9zZWQg
aW48YnI+DQpjb25mb3JtYW5jZSB3aXRoIElFVEYgcnVsZXMuPGJyPg0KPGJyPg0KVGhlIHBvbGwg
Zm9yIGFkb3B0aW9uIHdpbGwgY2xvc2UgaW4gdHdvIHdlZWtzIHRpbWUsIG9uIFdlZG5lc2RheSAx
OHRoIERlY2VtYmVyLjxicj4NCjxicj4NCkJlc3QgcmVnYXJkcyw8YnI+DQpBbmR5PGJyPg0KX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX188YnI+DQpwd2UzIG1h
aWxpbmcgbGlzdDxicj4NCnB3ZTNAaWV0Zi5vcmc8YnI+DQpodHRwczovL3d3dy5pZXRmLm9yZy9t
YWlsbWFuL2xpc3RpbmZvL3B3ZTM8YnI+DQo8L2ZvbnQ+PC90dD4NCjxicj4NCg==
--=_alternative 000E006548257C40_=--

From zhangmingui@huawei.com  Fri Dec 13 00:59:37 2013
Return-Path: <zhangmingui@huawei.com>
X-Original-To: pwe3@ietfa.amsl.com
Delivered-To: pwe3@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 090B81AD8E2 for <pwe3@ietfa.amsl.com>; Fri, 13 Dec 2013 00:59:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.202
X-Spam-Level: 
X-Spam-Status: No, score=-4.202 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id W65uV368MRIZ for <pwe3@ietfa.amsl.com>; Fri, 13 Dec 2013 00:59:32 -0800 (PST)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 4110A1AD937 for <pwe3@ietf.org>; Fri, 13 Dec 2013 00:59:32 -0800 (PST)
Received: from 172.18.7.190 (EHLO lhreml203-edg.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BBI33782; Fri, 13 Dec 2013 08:59:24 +0000 (GMT)
Received: from LHREML405-HUB.china.huawei.com (10.201.5.242) by lhreml203-edg.huawei.com (172.18.7.221) with Microsoft SMTP Server (TLS) id 14.3.158.1; Fri, 13 Dec 2013 08:59:07 +0000
Received: from NKGEML401-HUB.china.huawei.com (10.98.56.32) by lhreml405-hub.china.huawei.com (10.201.5.242) with Microsoft SMTP Server (TLS) id 14.3.158.1; Fri, 13 Dec 2013 08:59:22 +0000
Received: from NKGEML508-MBX.china.huawei.com ([169.254.7.180]) by nkgeml401-hub.china.huawei.com ([10.98.56.32]) with mapi id 14.03.0158.001; Fri, 13 Dec 2013 16:59:19 +0800
From: Mingui Zhang <zhangmingui@huawei.com>
To: Gregory Mirsky <gregory.mirsky@ericsson.com>, "Andrew G. Malis" <agmalis@gmail.com>, "pwe3@ietf.org" <pwe3@ietf.org>
Thread-Topic: [PWE3] Poll for WG adoption and IPR check	of draft-zhang-pwe3-iccp-stp-00
Thread-Index: AQHO8TwlCkXQzt/PFEWJQ1M2OraNH5pExIrAgArj8ICAAgDSsA==
Date: Fri, 13 Dec 2013 08:59:19 +0000
Message-ID: <4552F0907735844E9204A62BBDD325E7336903A9@nkgeml508-mbx.china.huawei.com>
References: <CAA=duU1X6SWzxNOVdXJHA4TsxnVf6u4jGO=0MaoYkc-661XWDw@mail.gmail.com> <7347100B5761DC41A166AC17F22DF1121B723A1F@eusaamb103.ericsson.se> <4552F0907735844E9204A62BBDD325E73368ED8E@nkgeml508-mbx.china.huawei.com> <7347100B5761DC41A166AC17F22DF1121B732ECB@eusaamb103.ericsson.se>
In-Reply-To: <7347100B5761DC41A166AC17F22DF1121B732ECB@eusaamb103.ericsson.se>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.111.102.175]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Subject: Re: [PWE3] Poll for WG adoption and IPR check	of	draft-zhang-pwe3-iccp-stp-00
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Pseudowire Emulation Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 13 Dec 2013 08:59:37 -0000

Hi Greg,

Let me give an analysis of the "BPDU tunneling over PW+RFC7023 model". The =
following figure is used.

              +--------------+       +=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D+
              |              |       |             |
              |              |       |             |
              |       +---+  |       |  +-----+    |
              |   +---+CE1+<6>-------<5>+ PE1 |    |
              |  <1>  +---+  |       |  +-----+    |
              | +-+-+        |       |     ||      |
              | |CE3|        |       |     ||tunnel|
              | +-+-+        |       |     ||      |
              |  <2>  +---+  |       |  +-----+    |
              |   +---+CE2+<3>-------<4>+ PE2 |    |
              |       +---+  |       |  +-----+    |
              |              |       |             |
              | Multi-homed  |       |             |
              | STP Network  |       |             |
              +--------------+       +=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D+

In this model, the ports connected to the STP network at the PEs' side are =
non-bridge ports (e.g., port <4>, <5>). The tunnel between PE1 and PE2 is a=
 transparent tunnel of BPDUs. For CE1 and CE2, they regard that there is a =
direct link between them.

[Issue1] Assume port <1> was blocked according to the STP calculation. Now,=
 link CE3-CE2 fails, port <2> is blocked while port <1> is unblocked. Since=
 the BPDUs is just tunneled, PE2 is unaware of this change. It may continue=
 to send traffic to CE3 via CE2 where a black-hole happens.=20

In order to handle this issue, PEs have to snoop the TC message of the STP =
network so the tunnel is not "transparent" to BPDUs anymore. When the Topol=
ogy Change event is sensed, these PEs should withdraw MAC addresses of thos=
e instances affected by the TC event across the L2VPN network.

[Issue2] When port <4> fails, CE1 is unaware. Suppose CE2 is the root bridg=
e, port <6> has to wait for 3 STP HELLO Intervals (3*2s) and 2 Forwarding D=
elays (2*15s). The STP network takes at least 36 seconds to complete the co=
nvergence. The convergence process of the STP network is greatly slowed dow=
n. This actually changes the behavior of customers' STP networks!

In order to speed up the convergence, CE1 has to sense the state of the lin=
k between CE2 and PE2. The interworking PEs and CEs have to cope with vario=
us combinations of failures. There is no standard solution yet.

[Issue3] As I know, RFC7023 is scoped to only single segment PWs. When the =
STP network is attached to more than two PEs, I guess a full mesh PWs have =
to be set up. Not clear yet what behaviors these PEs should have.

Jump to an upper level, in the "ICCP-STP" model, PEs "participate" the STP =
calculation, therefore we need not design the complex interworking mechanis=
m.

Thanks,
Mingui


>-----Original Message-----
>From: Gregory Mirsky [mailto:gregory.mirsky@ericsson.com]
>Sent: Thursday, December 12, 2013 3:05 PM
>To: Mingui Zhang; Andrew G. Malis; pwe3@ietf.org
>Subject: RE: [PWE3] Poll for WG adoption and IPR check of
>draft-zhang-pwe3-iccp-stp-00
>
>Hi Mingui,
>thank you for the extensive explanation. Have to admit, that I still am no=
t
>convinced that the Fig.2.1 and the description make strong case for new
>protocol extension. I think that there are other possibilities, e.g. tunne=
l BPDUs
>over PW and use RFC 7023 for MPLS and Ethernet OAM interworking. Do you
>think that will work?
>
>	Regards,
>		Greg
>
>-----Original Message-----
>From: Mingui Zhang [mailto:zhangmingui@huawei.com]
>Sent: Thursday, December 05, 2013 4:46 PM
>To: Gregory Mirsky; Andrew G. Malis; pwe3@ietf.org
>Subject: RE: [PWE3] Poll for WG adoption and IPR check of
>draft-zhang-pwe3-iccp-stp-00
>
>Hi Greg,
>
>Thanks for attention. This solution is designed for the use case that
>geo-dispersed DSLAMs running STP need enhance the reliability of the
>connections between the entire STP network and the carrier network.
>
>Want to address several key points here: 1. These DSLAMs are running STP. =
2.
>These DSLAMs are not geo-close to each other. Multiple DSLAMs are connecte=
d
>to the carrier network at different locations. 3. When one connection to t=
he
>carrier network fails, customers wish a connection in another location can
>continue to work after the re-convergence of the STP rather than compromis=
ing
>the whole STP network. The failure of the connection may be due to the fai=
lure of
>the PE, the AC or even the CE (a DSLAM) itself. 4. Customers want to balan=
ce
>the load among those connections, therefore all these connections need be
>active.
>
>Please note that the draft is not proposed to replace anything. I agree wi=
th you
>that the application "can be supported". That's why we want to introduce t=
he
>proposal into the ICCP draft as an _additional_ application. Currently, th=
ere are
>two applications in the ICCP draft, PW-RED and mLACP. These two applicatio=
ns
>are not applicable to above use case to meet the requirements of customers=
.
>
>If I misunderstood anything, please correct me.
>
>--
>Mingui
>
>>-----Original Message-----
>>From: pwe3 [mailto:pwe3-bounces@ietf.org] On Behalf Of Gregory Mirsky
>>Sent: Thursday, December 05, 2013 5:59 AM
>>To: Andrew G. Malis; pwe3@ietf.org
>>Subject: Re: [PWE3] Poll for WG adoption and IPR check of
>>draft-zhang-pwe3-iccp-stp-00
>>
>>Hi,
>>I think that the proposal would benefit from stronger description of
>>use case(s) that it intended to address. At this time, the topology
>>presented in Fig.2.1 can be supported with what already is defined in
>>draft-ietf-pwe3-iccp-12. Hence, no/do not support
>>
>>	Regards,
>>		Greg
>>
>>-----Original Message-----
>>From: pwe3 [mailto:pwe3-bounces@ietf.org] On Behalf Of Andrew G. Malis
>>Sent: Wednesday, December 04, 2013 12:53 PM
>>To: pwe3@ietf.org
>>Subject: [PWE3] Poll for WG adoption and IPR check of
>>draft-zhang-pwe3-iccp-stp-00
>>
>>This email begins a two week poll to help the chairs determine if there
>>is consensus to adopt draft-zhang-pwe3-iccp-stp-00 as an PWE3 working
>>group draft.
>>
>>The draft can be found here:
>>http://tools.ietf.org/html/draft-zhang-pwe3-iccp-stp-00
>>
>>Please read the draft and indicate to the list if you support adoption,
>>or if you do not support adoption (giving reasons).
>>
>>Please note that this is only a call for adoption. There needs to be
>>consensus that this draft is a good basis for the work, but it does not
>>need to be perfect at this stage.
>>
>>Coincidentally, we are also polling for knowledge of any IPR that
>>applies to this draft, to ensure that IPR has been disclosed in
>>compliance with IETF IPR rules (see RFCs 3979, 4879, 3669 and 5378 for mo=
re
>details).
>>
>>If you are listed as a document author or contributor please respond to
>>this email whether or not you are aware of any relevant IPR. The draft
>>will not be adopted until a response has been received from each author a=
nd
>contributor.
>>
>>If you are on the PWE3 WG email list but are not listed as an author or
>>contributor, then please explicitly respond regarding IPR only if you
>>are aware of any IPR that has not yet been disclosed in conformance with =
IETF
>rules.
>>
>>The poll for adoption will close in two weeks time, on Wednesday 18th
>>December.
>>
>>Best regards,
>>Andy
>>_______________________________________________
>>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 matthew.bocci@alcatel-lucent.com  Fri Dec 13 08:32:01 2013
Return-Path: <matthew.bocci@alcatel-lucent.com>
X-Original-To: pwe3@ietfa.amsl.com
Delivered-To: pwe3@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D25A61AE323 for <pwe3@ietfa.amsl.com>; Fri, 13 Dec 2013 08:32:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.899
X-Spam-Level: 
X-Spam-Status: No, score=-6.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Bd4_BEGEz_m7 for <pwe3@ietfa.amsl.com>; Fri, 13 Dec 2013 08:31:59 -0800 (PST)
Received: from ihemail4.lucent.com (ihemail4.lucent.com [135.245.0.39]) by ietfa.amsl.com (Postfix) with ESMTP id 8AD931ADFCB for <pwe3@ietf.org>; Fri, 13 Dec 2013 08:31:59 -0800 (PST)
Received: from fr711usmtp1.zeu.alcatel-lucent.com (h135-239-2-122.lucent.com [135.239.2.122]) by ihemail4.lucent.com (8.13.8/IER-o) with ESMTP id rBDGVo7E021608 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for <pwe3@ietf.org>; Fri, 13 Dec 2013 10:31:51 -0600 (CST)
Received: from FR712WXCHHUB03.zeu.alcatel-lucent.com (fr712wxchhub03.zeu.alcatel-lucent.com [135.239.2.74]) by fr711usmtp1.zeu.alcatel-lucent.com (GMO) with ESMTP id rBDGVnCa018699 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <pwe3@ietf.org>; Fri, 13 Dec 2013 17:31:49 +0100
Received: from FR711WXCHMBA05.zeu.alcatel-lucent.com ([169.254.1.146]) by FR712WXCHHUB03.zeu.alcatel-lucent.com ([135.239.2.74]) with mapi id 14.02.0247.003; Fri, 13 Dec 2013 17:31:49 +0100
From: "Bocci, Matthew (Matthew)" <matthew.bocci@alcatel-lucent.com>
To: "pwe3@ietf.org" <pwe3@ietf.org>
Thread-Topic: WG adoption of draft-shen-pwe3-endpoint-fast-protection-04
Thread-Index: AQHO+CDSSHoXXdc/LU6GHHGZZQnFWA==
Date: Fri, 13 Dec 2013 16:31:49 +0000
Message-ID: <CED0E5EA.5963D%matthew.bocci@alcatel-lucent.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.3.9.131030
x-originating-ip: [135.239.27.40]
Content-Type: multipart/alternative; boundary="_000_CED0E5EA5963Dmatthewboccialcatellucentcom_"
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.39
Subject: [PWE3] WG adoption of draft-shen-pwe3-endpoint-fast-protection-04
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Pseudowire Emulation Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 13 Dec 2013 16:32:02 -0000

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

WG,

A while ago (last september) we ran an adoption poll for draft-shen-pwe3-en=
dpoint-fast-protection-04. At the same time we ran a call for IPR declarati=
ons against the draft.

While there appears to be consensus to adopt the draft as a PWE3 working gr=
oup document, we are still missing one response from one of the co-authors =
(Rahul Aggarwal) regarding any knowledge of IPR relevant to the draft. We h=
ave not been able to contact Rahul in the mean time.

Normally we would require a response from every co-author. However, in this=
 case, since there are already relevant IPR declarations against the draft =
(2242 and 2262) and there will be a further IPR poll in the future when thi=
s draft goes through working group last call, I believe it is reasonable to=
 adopt this draft.

Could the authors please upload a new version of the draft with the name ch=
anged to draft-ietf-pwe3-endpoint-fast-protection-00.

Best regards

Matthew

--_000_CED0E5EA5963Dmatthewboccialcatellucentcom_
Content-Type: text/html; charset="us-ascii"
Content-ID: <949AB11AFD7E4E4495A62638B1741835@exchange.lucent.com>
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
</head>
<body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-lin=
e-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-fami=
ly: Calibri, sans-serif;">
<div>WG,</div>
<div><br>
</div>
<div>A while ago (last september) we ran an adoption poll for&nbsp;<span st=
yle=3D"white-space: pre-wrap;">draft-shen-pwe3-endpoint-fast-protection-04.=
 At the same time we ran a call for IPR declarations against the draft.</sp=
an></div>
<div><span style=3D"white-space: pre-wrap;"><br>
</span></div>
<div>While there appears to be consensus to adopt the draft as a PWE3 worki=
ng group document, we are still missing one response from one of the co-aut=
hors (Rahul Aggarwal) regarding any knowledge of IPR relevant to the draft.=
 We have not been able to contact
 Rahul in the mean time.</div>
<div><br>
</div>
<div>Normally we would require a response from every co-author. However, in=
 this case, since there are already relevant IPR declarations against the d=
raft (2242 and 2262) and there will be a further IPR poll in the future whe=
n this draft goes through working
 group last call, I believe it is reasonable to adopt this draft.</div>
<div><br>
</div>
<div>Could the authors please upload a new version of the draft with the na=
me changed to draft-ietf-pwe3-endpoint-fast-protection-00.</div>
<div><br>
</div>
<div>Best regards</div>
<div><br>
</div>
<div>Matthew</div>
</body>
</html>

--_000_CED0E5EA5963Dmatthewboccialcatellucentcom_--

From internet-drafts@ietf.org  Fri Dec 13 14:20:43 2013
Return-Path: <internet-drafts@ietf.org>
X-Original-To: pwe3@ietfa.amsl.com
Delivered-To: pwe3@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A0CEC1AE416; Fri, 13 Dec 2013 14:20:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5CEtGi-KBVbb; Fri, 13 Dec 2013 14:20:42 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 479521ADFD6; Fri, 13 Dec 2013 14:20:42 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 4.83.p1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20131213222042.9049.6719.idtracker@ietfa.amsl.com>
Date: Fri, 13 Dec 2013 14:20:42 -0800
Cc: pwe3@ietf.org
Subject: [PWE3] I-D Action: draft-ietf-pwe3-endpoint-fast-protection-00.txt
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.15
List-Id: Pseudowire Emulation Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 13 Dec 2013 22:20:44 -0000

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

	Title           : PW Endpoint Fast Failure Protection
	Author(s)       : Yimin Shen
                          Rahul Aggarwal
                          Wim Henderickx
                          Yuanlong Jiang
	Filename        : draft-ietf-pwe3-endpoint-fast-protection-00.txt
	Pages           : 28
	Date            : 2013-12-13

Abstract:
   This document specifies a fast mechanism for protecting pseudowires
   against egress endpoint failures, including egress attachment circuit
   failure, egress PE failure, multi-segment PW terminating PE failure,
   and multi-segment PW switching PE failure.  Designed on the basis of
   multi-homed CE, PW redundancy, upstream label assignment and context
   specific label switching, the mechanism enables local repair to be
   performed by the router upstream adjacent to a failure.  In
   particular, the router can restore PW traffic in the order of tens of
   milliseconds, by transmitting the traffic to a protector through a
   pre-established bypass tunnel.  Therefore, the mechanism can reduce
   traffic loss before global repair reacts to the failure and the
   network converges on the topology changes due to the failure.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-pwe3-endpoint-fast-protection

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-pwe3-endpoint-fast-protection-00


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

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


From Alexander.Vainshtein@ecitele.com  Fri Dec 13 22:27:38 2013
Return-Path: <Alexander.Vainshtein@ecitele.com>
X-Original-To: pwe3@ietfa.amsl.com
Delivered-To: pwe3@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4FA3E1AE4B3; Fri, 13 Dec 2013 22:27:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level: 
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mvaI8sfUXvuB; Fri, 13 Dec 2013 22:27:32 -0800 (PST)
Received: from emea01-am1-obe.outbound.protection.outlook.com (mail-am1lp0014.outbound.protection.outlook.com [213.199.154.14]) by ietfa.amsl.com (Postfix) with ESMTP id 75D361A802D; Fri, 13 Dec 2013 22:27:30 -0800 (PST)
Received: from AM3PR03MB532.eurprd03.prod.outlook.com (10.242.109.156) by AM3PR03MB530.eurprd03.prod.outlook.com (10.242.109.154) with Microsoft SMTP Server (TLS) id 15.0.842.7; Sat, 14 Dec 2013 06:27:21 +0000
Received: from AM3PR03MB532.eurprd03.prod.outlook.com ([10.242.109.156]) by AM3PR03MB532.eurprd03.prod.outlook.com ([10.242.109.156]) with mapi id 15.00.0842.003; Sat, 14 Dec 2013 06:27:20 +0000
From: Alexander Vainshtein <Alexander.Vainshtein@ecitele.com>
To: "curtis@ipv6.occnc.com" <curtis@ipv6.occnc.com>
Thread-Topic: [PWE3] Pseudowire Sequence Number in draft-ietf-mpls-forwarding: a minor comment
Thread-Index: AQHO+DfmSq0tCZZscUehMpHq+OAdtZpTOidO
Date: Sat, 14 Dec 2013 06:27:20 +0000
Message-ID: <a04140f1c92143ee97a69cf10cba5c03@AM3PR03MB532.eurprd03.prod.outlook.com>
References: Your message of "Thu, 12 Dec 2013 05:49:22 +0000." <4946c79f4554497d84cd676684739124@AM3PR03MB532.eurprd03.prod.outlook.com>, <201312131917.rBDJH1ev034508@gateway1.ipv6.occnc.com>
In-Reply-To: <201312131917.rBDJH1ev034508@gateway1.ipv6.occnc.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [5.153.9.203]
x-forefront-prvs: 00603B7EEF
x-forefront-antispam-report: SFV:NSPM; SFS:(10009001)(53754006)(43784003)(199002)(189002)(13464003)(51704005)(52604005)(377454003)(31966008)(74316001)(19580405001)(19580395003)(85306002)(85852003)(59766001)(83322001)(71446004)(74366001)(54356001)(4396001)(33646001)(47976001)(50986001)(49866001)(74706001)(74662001)(47736001)(81816001)(46102001)(81686001)(76576001)(76786001)(76482001)(51856001)(76796001)(56776001)(2656002)(47446002)(69226001)(65816001)(87266001)(74876001)(81342001)(83072002)(87936001)(66066001)(74502001)(53806001)(80976001)(81542001)(80022001)(54316002)(77982001)(79102001)(56816005)(90146001)(63696002)(427584002)(24736002)(579004)(559001); DIR:OUT; SFP:1101; SCL:1; SRVR:AM3PR03MB530; H:AM3PR03MB532.eurprd03.prod.outlook.com; CLIP:5.153.9.203; FPR:; RD:InfoNoRecords; A:1; MX:1; LANG:en; 
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: ecitele.com
Cc: "samante@apple.com" <samante@apple.com>, "Yaakov Stein \(yaakov_s@rad.com\)" <yaakov_s@rad.com>, "cpignata@cisco.com" <cpignata@cisco.com>, "kireeti@juniper.net" <kireeti@juniper.net>, "mpls@ietf.org" <mpls@ietf.org>, "curtis@occnc.com" <curtis@occnc.com>, "pwe3 \(pwe3@ietf.org\)" <pwe3@ietf.org>
Subject: Re: [PWE3] Pseudowire Sequence Number in draft-ietf-mpls-forwarding: a minor comment
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Pseudowire Emulation Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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: Sat, 14 Dec 2013 06:27:38 -0000

Curtis,=0A=
Lots of thanks for a prompt and most encouraging response.=0A=
=0A=
I believe that the last proposed text fully addreses both my original comme=
nt and the misunderstanding that has been encountered at some stage in this=
 email thread.=0A=
=0A=
Regards,=0A=
     Sassha=0A=
________________________________________=0A=
From: Curtis Villamizar <curtis@ipv6.occnc.com>=0A=
Sent: Friday, December 13, 2013 9:17 PM=0A=
To: Alexander Vainshtein=0A=
Cc: curtis@ipv6.occnc.com; curtis@occnc.com; kireeti@juniper.net; samante@a=
pple.com; agmalis@gmail.com; cpignata@cisco.com; mpls@ietf.org; Yaakov Stei=
n (yaakov_s@rad.com); pwe3 (pwe3@ietf.org)=0A=
Subject: Re: [PWE3] Pseudowire Sequence Number in draft-ietf-mpls-forwardin=
g: a minor comment=0A=
=0A=
Sasha,=0A=
=0A=
Thanks for pointing out the lack of clarity regarding the context of=0A=
the statement we were discussing.  These are the first three paragraphs=0A=
(originally one) of "2.1.8.1.  Pseudowire Sequence Number" that we've=0A=
been discussing=0A=
=0A=
 Original (draft-ietf-mpls-forwarding-03, short but inaccurate)=0A=
=0A=
   Pseudowire (PW) sequence number support is most important for PW=0A=
   payload types with a high expectation of in-order delivery.=0A=
   Resequencing support, rather than dropping at egress on out of order=0A=
   arrival, is most important for PW payload types with a high=0A=
   expectation of lossless delivery.  For example, TDM payloads require=0A=
   sequence number support and require resequencing support.  The same=0A=
   is true of ATM CBR service.  ATM VBR or ABR may have somewhat relaxed=0A=
   requirements, but generally require ATM Early Packet Discard (EPD) or=0A=
   ATM Partial Packet Discard (PPD) [ATM-EPD-and-PPD].  Though sequence=0A=
   number support and resequencing support are beneficial to PW packet=0A=
   oriented payloads such as FR and Ethernet, they are highly desirable=0A=
   but not as strongly required.=0A=
=0A=
 First change=0A=
=0A=
   Pseudowire (PW) sequence number support is most important for PW=0A=
   payload types with a high expectation of lossless and/or in-order=0A=
   delivery.  Identifying the position of any lost packets is important=0A=
   for PW services which are attempting to reconstruct a bit stream=0A=
   which maintains bit timing, such as time division multiplexing (TDM)=0A=
   services.  TDM and other PW services which require strict ordering=0A=
   also require that misordered packets be either dropped or reordered.=0A=
=0A=
   PW services which are not timing critical bit streams in nature are=0A=
   cell oriented or frame oriented.  Though resequencing support is=0A=
   beneficial to PW cell and frame oriented payloads such as ATM, FR and=0A=
   Ethernet, they are highly desirable but not required.=0A=
=0A=
 Suggested new para (Sasha) - part of second para rewritten=0A=
=0A=
   Pseudowire (PW) sequence number support is most important for PW=0A=
   payload types with a high expectation of lossless and/or in-order=0A=
   delivery.  Identifying lost PW packets and exact amount of lost=0A=
   payload is critical for PW services which maintain bit timing, such=0A=
   as Time Division Multiplexing (TDM) services since these services=0A=
   MUST compensate lost payload on a bit-for-bit basis.=0A=
=0A=
   With these services PW packets that have been received out of order=0A=
   also MUST also be identified and may be either re-ordered or=0A=
   dropped.  Reordering requires, in addition to sequence numbering, a=0A=
   "de-jitter buffer" in the egress PE, and ability to reorder is=0A=
   limited by the depth of this buffer. The down side of maintaining a=0A=
   de-jitter buffer is added end-to-end service delay.=0A=
=0A=
   PW services which are not timing critical bit streams in nature are=0A=
   cell oriented or frame oriented.  Though resequencing support is=0A=
   beneficial to PW cell and frame oriented payloads such as ATM, FR and=0A=
   Ethernet, they are highly desirable but not required.=0A=
=0A=
 Suggested change to above (Curtis) - minor plus add last sentence=0A=
=0A=
   Pseudowire (PW) sequence number support is most important for PW=0A=
   payload types with a high expectation of lossless and/or in-order=0A=
   delivery.  Identifying lost PW packets and exact amount of lost=0A=
   payload is critical for PW services which maintain bit timing, such=0A=
   as Time Division Multiplexing (TDM) services since these services=0A=
   MUST compensate lost payload on a bit-for-bit basis.=0A=
=0A=
   With these services PW packets that have been received out of order=0A=
   also MUST also be identified and may be either re-ordered or=0A=
   dropped.  Reordering requires, in addition to sequence numbering, a=0A=
   "jitter buffer" in the egress PE, and ability to reorder is limited=0A=
   by the depth of this buffer. The down side of maintaining a large=0A=
   jitter buffer is added end-to-end service delay.  A small jitter=0A=
   buffer is always necessary and the jitter buffer is needed=0A=
   regardless of whether reordering is done.=0A=
=0A=
   PW services which are not timing critical bit streams in nature are=0A=
   cell oriented or frame oriented.  Though resequencing support is=0A=
   beneficial to PW cell and frame oriented payloads such as ATM, FR=0A=
   and Ethernet, they are highly desirable but not required.=0A=
=0A=
 Reorder paragraphs and edit for clarity of context=0A=
=0A=
   Pseudowire (PW) sequence number support is most important for PW=0A=
   payload types with a high expectation of lossless and/or in-order=0A=
   delivery.  Identifying lost PW packets and exact amount of lost=0A=
   payload is critical for PW services which maintain bit timing, such=0A=
   as Time Division Multiplexing (TDM) services since these services=0A=
   MUST compensate lost payload on a bit-for-bit basis.=0A=
=0A=
   With PW services which maintain bit timing, packets that have been=0A=
   received out of order also MUST be identified and may be either=0A=
   re-ordered or dropped.  Reordering requires, in addition to=0A=
   sequence numbering, a "reorder buffer" in the egress PE, and ability=0A=
   to reorder is limited by the depth of this buffer. The down side of=0A=
   maintaining a large reorder buffer is added end-to-end service=0A=
   delay.=0A=
=0A=
   For PW services which maintain bit timing or any other service=0A=
   where jitter must be bounded, a jitter buffer is always necessary.=0A=
   The jitter buffer is needed regardless of whether reordering is=0A=
   done.  In order to be effective, a reorder buffer must often be=0A=
   larger than a jitter buffer needs to be creating a tradeoff between=0A=
   reducing loss and minimizing delay.=0A=
=0A=
   PW services which are not timing critical bit streams in nature are=0A=
   cell oriented or frame oriented.  Though resequencing support may=0A=
   be beneficial to PW cell and frame oriented payloads such as ATM,=0A=
   FR and Ethernet, this support is desirable but not required.=0A=
   Requirements to hamdle out of order packets at all vary among=0A=
   services and deployments.  For example for Ethernet PW, occasional=0A=
   (very rare) reordering is usually acceptable.  If the Ethernet PW=0A=
   is carrying MPLS-TP, then this reordering may be acceptable.=0A=
=0A=
   Reducing jitter is best done by an end-system, given that the=0A=
   tradeoff of loss vs delay varies among services.  For example with=0A=
   interactive real time services low delay is preferred, while with=0A=
   non-interactive (one way) real time services low loss is preferred.=0A=
   The same end-site may be receiving both types of traffic.=0A=
   Regardless of this, bounded jitter is sometimes a requiremnet for=0A=
   specific deployments.=0A=
=0A=
In the prior iteration a paragraph began with "With these services"=0A=
following the prior paragraph discussing "PW services which maintain=0A=
bit timing, such as Time Division Multiplexing (TDM) services" which=0A=
did not clearly carry over the context.=0A=
=0A=
At this point, each paragraph clearly indicates its context, either=0A=
bit timing, not bit timing, or all PW.  It also makes a distinction=0A=
between a reorder buffer and a jitter buffer.=0A=
=0A=
This is a more thorough treatment of the tradeoffs of using PW=0A=
sequence in supporting de-jitter and reordering in PW services than=0A=
what was originally in the document (but given that it wasn't correct=0A=
some change was needed).=0A=
=0A=
Curtis=0A=
=0A=
=0A=
ps - Needed to top post a summary since your repeated top posting was=0A=
obscuring the context of the (longish) conversation thread.  You've=0A=
probably seen something like this before:=0A=
=0A=
  You're welcome.=0A=
  I get it.  Thanks.=0A=
  Because it is the default in most pee-cee mailers.=0A=
  Why do people do it so often then?=0A=
  Because it loses context and reverses the order of the discussion.=0A=
  Why?=0A=
  Yes.=0A=
  Is top posting a bad practice?=0A=
=0A=
=0A=
In message <4946c79f4554497d84cd676684739124@AM3PR03MB532.eurprd03.prod.out=
look.com>=0A=
Alexander Vainshtein writes:=0A=
=0A=
Curtis,=0A=
Lots of hanks for a long and detailed explanation.=0A=
=0A=
It appears that your original comment about the need of jitter buffer=0A=
refered to TDM (or TDM-like) PWs (bit-stream PWs in the Architecture=0A=
RFC). If this was indeed the case, there is nothing to argue about,=0A=
because I agree completely that jitter buffer is absolutely necessary=0A=
for these.=0A=
=0A=
My impression from reading the original text has been that it referred=0A=
to ALL kinds of PWs (bit-stream, celland packet) alike. Apparently=0A=
this has been my mis-interptetation; if this is indeed so, then maybe=0A=
some clarification (placing the jiter buffer discussion in the proper=0A=
context) would hopefully help.=0A=
=0A=
Regards,=0A=
     Sasha=0A=
________________________________________=0A=
From: Curtis Villamizar <curtis@ipv6.occnc.com>=0A=
Sent: Thursday, December 12, 2013 6:53 AM=0A=
To: Alexander Vainshtein=0A=
Cc: curtis@occnc.com; curtis@ipv6.occnc.com; kireeti@juniper.net; samante@a=
pple.com; agmalis@gmail.com; cpignata@cisco.com; mpls@ietf.org; Yaakov Stei=
n (yaakov_s@rad.com); pwe3 (pwe3@ietf.org)=0A=
Subject: Re: [PWE3] Pseudowire Sequence Number in draft-ietf-mpls-forwardin=
g: a minor comment=0A=
=0A=
In message <774d74926b684ffba7f4f89ace758547@AM3PR03MB532.eurprd03.prod.out=
look.com>=0A=
Alexander Vainshtein writes:=0A=
=0A=
> Curtis,=0A=
> Lots of thanks for sending out the new text.=0A=
>=0A=
> I still have a couple of issues with this version of the text: one=0A=
> technical and one editorial.=0A=
>=0A=
> The technical issue is about the fragment "A small jitter buffer is=0A=
> always necessary".=0A=
>=0A=
> I am not sure this is correct, since I am aware of several PW=0A=
> implementations that pass the payload of a received PW packet directly=0A=
> for transmission via the corresdponding attachment circuit. Of course=0A=
> this payload would be stored in some Tx queue associated with the=0A=
> attachment circuit and controlled by the appropriate egress scheduler,=0A=
> but IMO this does not constitue a PW jitter bufer, since the PW=0A=
> interworking function does not exersize any control over these=0A=
> queues.=0A=
=0A=
Well if its a technical argument you want, then here goes ...=0A=
=0A=
Even in pure TDM systems some jitter exist due to the longer time it=0A=
takes if multiple passes of the FEC algorithm are needed.  In that=0A=
case there is a very small jitter buffer that can be set to the=0A=
maximum needed for a worst case FEC, or set lower to decrease delay=0A=
with the potential to make a greater number of errors uncorrectable.=0A=
=0A=
For IP, even if IP EF service is used and there is a very small amount=0A=
of EF traffic, some jitter exists.  For most systems there is some=0A=
jitter crossing the fabric and internal jitter elsewhere.  The egress=0A=
buffer in most chips is very small but needed for that jitter.  For=0A=
TDM, the egress buffer can never run dry or there will be a timing=0A=
slip.=0A=
=0A=
Consider what happens when packets arrive late in a system with only a=0A=
non-zero egress buffer.  For example, assume 1% of packets arrive=0A=
about one packet time late (one other EF packet in queue somewhere on=0A=
the path), 0.1% arrive two packets late.  Note that this would be an=0A=
extremely light EF load.  Generally most packets arrive at least zero=0A=
to one minus epsilon packet times late due to a lower priority packet=0A=
partially transmited when the EF packet is moved to the front of the=0A=
queue.  If there is no egress buffer at all or considerably less than=0A=
a packet time, lots of data would be dropped.  If the egress buffer=0A=
could hold just a few packets data drop would be very low.=0A=
=0A=
If a packet arrives late and there is no standing queue the egress=0A=
runs dry, there is a timing slip.  When the packet does arrive a=0A=
little late the packet is sent, albiet late.  Every packet to follow=0A=
is now late by that amount of time (if the egress buffer has not=0A=
overflowed on a later packet).=0A=
=0A=
At that point there is an standing queue in the egress buffer which=0A=
acts as a jitter buffer.  Most packets arrive early.  A few arrive a=0A=
little later but as long as the queue doesn't run dry again, the=0A=
jitter is compensated for.=0A=
=0A=
If the egress buffer is large, then it will tend to grow to the worst=0A=
case packet delay and keep a large standing queue.  This is with no=0A=
reorder and no drop.  If the egress buffer is small (or configured to=0A=
be small) then when a packet arrives very late followed by a set of=0A=
packets in close succession, the buffer runs dry until that first late=0A=
packet arrives.  This packet is transmitted but very late.  Subsequent=0A=
packets arrive and some of them have to be dropped due to the limited=0A=
queue capacity.  This in effect puts a cap on the jitter buffer.=0A=
=0A=
With only an egress buffer there are multiple strategies for dealing=0A=
with dropped packets.=0A=
=0A=
  1.  Just ignore it and send the next one.=0A=
  2.  Put one packet time worth of all zeros in the queue.=0A=
=0A=
Now consider what happens with a dropped packet and a standing queue.=0A=
The first strategy creates a hidden timing slip.  The second strategy=0A=
avoids the timing slip.=0A=
=0A=
So my argument is that the egress buffer is in effect the jitter=0A=
buffer.  When jitter occurs a standing buffer forms that reflects the=0A=
lesser of the limit of the buffer size or the worst case jitter.=0A=
There is always a jitter buffer.  There always needs to be a jitter=0A=
buffer of at least one large packet time, otherwise high loss of data=0A=
will occur.  There should be a jitter buffer that can be made larger=0A=
so that jitter of multiple packet times doesn't turn in to loss.=0A=
=0A=
Therefore I assert that a jitter buffer is always present and is=0A=
always needed because jitter is always non-zero.  Therefore this=0A=
statement is true:=0A=
=0A=
   A small jitter buffer is always necessary and the jitter buffer is=0A=
   needed regardless of whether reordering is done.=0A=
=0A=
> In particular, these queues could not be used for re-ordering=0A=
> misordered PW packets.=0A=
=0A=
That does not mean that they can't be used to compensate for jitter=0A=
which is by definition what a jitter buffer is for.=0A=
=0A=
When reordering is done, the egress buffer is made small and a buffer=0A=
preceding that is used which has some ability to reorder packets.  In=0A=
hardware a circular queue makes sense with packets place according to=0A=
their sequence number.  If you prescribe to the "just insert zeros"=0A=
idea when a packet is dropped, then after moving a packet to the=0A=
egress queue, zero the buffer or mark it as unoccupied and more the=0A=
circular buffer a bit.  If the packet that is later supposed to occupy=0A=
that slot never arrives, then it is already zerod (or marked as=0A=
missing in which case a packet of all zeros is put on the egress=0A=
queue).=0A=
=0A=
So ... reording within a small jitter buffer is not hard to do.=0A=
=0A=
Reordering can be supported with a small jitter buffer but adding=0A=
reordering to a small buffer may be ineffective.  If reordering is due=0A=
to a path change, then the buffer of a small number of packet times=0A=
may yield no improvement.  To be effective in that situation, the=0A=
buffer may need to be larger.  OTOH if moving EF traffic from one=0A=
queue with no standing EF queue to another with no standing EF queue=0A=
and the path change is just moving to another wave on the WDM,=0A=
reordering with a small jitter buffer may help.=0A=
=0A=
> IMHO and FWIW this understanding matches RFC 3985 which mentions (in=0A=
> Section 5.2.1.1 "Frame Ordering") that reodering as the strategy for=0A=
> handling mis-ordered packets introduces additional delay (i.e.,=0A=
> requires a ddicated jitter buffer), while the alternative strategy of=0A=
> discarding mis-ordered packets does not introduce such additional=0A=
> delay.=0A=
=0A=
You quoted the framework and not a TDM document.  Nowhere in that text=0A=
is there mention of a jitter buffer because that text is not specific=0A=
to TDM.=0A=
=0A=
For packet traffic you have no idea if a prior packet is dropped or=0A=
will arrive out of order and so when a drop occurs packets have to be=0A=
held for a non-zero amount of time rather than transmitted as soon as=0A=
they arrive.  This applies to all cell or packet AC, such as FR, ATM,=0A=
Ethernet, etc.=0A=
=0A=
You might want to look at section 5.2.2.1.  Clock Recovery which does=0A=
apply to TDM.  It points to RFC3550 (RTP) which assumes a jitter=0A=
buffer is always needed.=0A=
=0A=
> The editorial issue is about the entire sentence that contains the=0A=
> above-mentioned fragment, i.e., "A small jitter buffer is always=0A=
> necessary and the jitter buffer is needed regardless of whether=0A=
> reordering is done" - to me this looks like an unnecessary repetition=0A=
> if if it were techically correct.=0A=
=0A=
The second part of the sentence was to emphasis that the need for a=0A=
jitter buffer is not contingent on implementation or reordering.=0A=
Perhaps it would be more clear if the two points were separated.  How=0A=
about this=0A=
=0A=
 OLD new sentence=0A=
=0A=
   A small jitter buffer is always necessary and the jitter buffer=0A=
   is needed regardless of whether reordering is done.=0A=
=0A=
 NEW new sentence=0A=
=0A=
   A small jitter buffer is always necessary.  A jitter buffer is=0A=
   needed regardless of whether reordering is done.=0A=
=0A=
> Hence I would like to suggest discrading the problematic sentence as=0A=
> the simplest way to resolve both issues.=0A=
=0A=
I think the sentence provides an important clarification.  I think the=0A=
need to have this discussion proves that the clarification is needed.=0A=
=0A=
If we can agree on keeping this, I can submit the updated draft.=0A=
=0A=
> Hopefully these notes will e helpful.=0A=
>=0A=
> Regards,=0A=
>      Sasha=0A=
=0A=
Thanks again for the review and good comments.=0A=
=0A=
Regards,=0A=
=0A=
Curtis=0A=
=0A=
=0A=
> ________________________________________=0A=
> From: Curtis Villamizar <curtis@occnc.com>=0A=
> Sent: Tuesday, December 10, 2013 5:47 PM=0A=
> To: Alexander Vainshtein=0A=
> Cc: curtis@ipv6.occnc.com; curtis@occnc.com; kireeti@juniper.net; samante=
@apple.com; agmalis@gmail.com; cpignata@cisco.com; mpls@ietf.org; Yaakov St=
ein (yaakov_s@rad.com); pwe3 (pwe3@ietf.org)=0A=
> Subject: Re: [PWE3] Pseudowire Sequence Number in draft-ietf-mpls-forward=
ing: a minor comment=0A=
>=0A=
> In message <F9336571731ADE42A5397FC831CEAA025AC56C9D@ILPTWPVEXMB02.ecitel=
e.com>=0A=
> Alexander Vainshtein writes:=0A=
> >=0A=
> > Curtis,=0A=
> >=0A=
> > Lots of thanks for a prompt and very detailed response.=0A=
> > May I suggest an alternative version of the following text fragment?=0A=
> >=0A=
> > <Curtis>=0A=
> > >   Identifying the position of any lost packets is important=0A=
> > >    for PW services which are attempting to reconstruct a bit stream=
=0A=
> > >    which maintains bit timing, such as time division multiplexing (TD=
M)=0A=
> > >    services.  TDM and other PW services which require strict ordering=
=0A=
> > >    also require that misordered packets be either dropped or reordere=
d.=0A=
>=0A=
> Invalid XML - you didn't close this element.  :-)=0A=
>=0A=
> >  <Sasha>=0A=
> >=0A=
> >    Identifying lost PW packets and exact amount of lost payload is=0A=
> >    critical for PW services which maintain bit timing, such as Time=0A=
> >    Division Multiplexing (TDM) services since these services MUST=0A=
> >    compensate lost payload on a bit-for-bit basis.=0A=
> >=0A=
> >    With these services PW packets that have been received out of order=
=0A=
> >    also MUST also be identified and may be either re-ordered or=0A=
> >    dropped.  Reordering requires, in addition to sequence numbering, a=
=0A=
> >    "de-jitter buffer" in the egress PE, and ability to reorder is=0A=
> >    limited by the depth of this buffer. The down side of maintaining a=
=0A=
> >    de-jitter buffer is added end-to-end service delay.=0A=
> >=0A=
> >   </Sasha>=0A=
>=0A=
> Accepted with a small change.=0A=
>=0A=
> After the words "down side"=0A=
> s/de-jitter buffer/large jitter buffer/=0A=
> Elsewhere=0A=
> s/de-jitter buffer/jitter buffer/g=0A=
> Then add the sentence.=0A=
>=0A=
>    A small jitter buffer is always necessary and the jitter buffer=0A=
>    is needed regardless of whether reordering is done.=0A=
>=0A=
> This yields a slightly changed second paragraph.=0A=
>=0A=
>    With these services PW packets that have been received out of order=0A=
>    also MUST also be identified and may be either re-ordered or=0A=
>    dropped.  Reordering requires, in addition to sequence numbering, a=0A=
>    "jitter buffer" in the egress PE, and ability to reorder is limited=0A=
>    by the depth of this buffer. The down side of maintaining a large=0A=
>    jitter buffer is added end-to-end service delay.  A small jitter=0A=
>    buffer is always necessary and the jitter buffer is needed=0A=
>    regardless of whether reordering is done.=0A=
>=0A=
> Is this wording OK with you?=0A=
>=0A=
> Curtis=0A=
>=0A=
> > Hopefully this will be useful.=0A=
> >=0A=
> >=0A=
> > Regards,=0A=
> >      Sasha=0A=
> >=0A=
> > > -----Original Message-----=0A=
> > > From: Curtis Villamizar [mailto:curtis@ipv6.occnc.com]=0A=
> > > Sent: Monday, November 25, 2013 8:30 PM=0A=
> > > To: Alexander Vainshtein=0A=
> > > Cc: curtis@occnc.com; kireeti@juniper.net; samante@apple.com;=0A=
> > > agmalis@gmail.com; cpignata@cisco.com; mpls@ietf.org; Yaakov Stein=0A=
> > > (yaakov_s@rad.com); pwe3 (pwe3@ietf.org)=0A=
> > > Subject: Re: [PWE3] Pseudowire Sequence Number in draft-ietf-mpls-=0A=
> > > forwarding: a minor comment=0A=
> > >=0A=
> > >=0A=
> > > In message=0A=
> > > <F9336571731ADE42A5397FC831CEAA025392F92F@ILPTWPVEXMB01.ecitele.c=0A=
> > > om>=0A=
> > > Alexander Vainshtein writes:=0A=
> > > >=0A=
> > > > Hi all,=0A=
> > > >=0A=
> > > > I would like to comment on the text in Section 2.1.8.1 "Pseudowire=
=0A=
> > > > Sequence Number" in draft-ietf-mpls-forwarding-03 - MPLS Forwarding=
=0A=
> > > > Compliance and Performance Requirements=0A=
> > > > <http://tools.ietf.org/html/draft-ietf-mpls-forwarding-03>.=0A=
> > > >=0A=
> > > > This section states, in short, that the main drive for using the=0A=
> > > > sequence number in the PW Control Word is handling of packet=0A=
> > > > reordering events. TDM PWs are presented as a major example, with C=
BR=0A=
> > > > ATM services as another example.=0A=
> > > >=0A=
> > > > In fact, this statement is not accurate.=0A=
> > >=0A=
> > > Yes.  You are correct in pointing this out as inaccurate by omitting=
=0A=
> > > the other important function of identifying drops for the purpose of=
=0A=
> > > recunstructing TDM bit streams.=0A=
> > >=0A=
> > > Andy brought up resequencing being a strong provider request.=0A=
> > > Reordering is far more common than loss particularly for high priorit=
y=0A=
> > > services on provider networks and without resequencing reorder result=
s=0A=
> > > in PW loss in what could otherwise be lossless service.=0A=
> > >=0A=
> > > So we should get the base requirements right but still reflect this,=
=0A=
> > > but strictly as advice with no normative wording.  We had used the=0A=
> > > phrase "is beneficial" and will retain that.=0A=
> > >=0A=
> > > Andy brought up the topic.  The incorrect wording in the existing=0A=
> > > draft is my fault.  This text went in fairly early with a lot of othe=
r=0A=
> > > changes and it appears that no one had since given it a careful enoug=
h=0A=
> > > read and review until you came along.=0A=
> > >=0A=
> > > > The main drive for mandating the use of sequence number in TM PWs i=
s=0A=
> > > > the need to detect and count lost packets because the egress PE MUS=
T=0A=
> > > > compensate the lost payload bit for bit.=0A=
> > > >=0A=
> > > > Ability to compensate reordering of PW packets at egress is a side=
=0A=
> > > > effect of (a) sequence number usage and (b) usage of the de-jitter=
=0A=
> > > > buffer in the egress PW. It is not mandatory and in any case is=0A=
> > > > limited by the depth of the de-jitter buffer: re-ordered packets th=
at=0A=
> > > > cannot be accommodated within this buffer are treated as lost.=0A=
> > > >=0A=
> > > > Additional details can be found, e.g., in section 6.2.2 of RFC=0A=
> > > > 4553<http://tools.ietf.org/html/rfc4553>. Ability to re-order=0A=
> > > > mis-ordered PW packets is defined there as OPTIONAL, while replacem=
ent=0A=
> > > > of the payload of lost PW packets is defined as MANDATORY.=0A=
> > >=0A=
> > > The change below at the top of the section more accurately reflects=
=0A=
> > > requirements in the RFCs but still states that resequencing can be=0A=
> > > beneficial.  The comments about EPD and PPD are dropped and therefore=
=0A=
> > > also the informative reference.=0A=
> > >=0A=
> > >  Context:=0A=
> > >=0A=
> > >  2.1.8.1.  Pseudowire Sequence Number=0A=
> > >=0A=
> > >  OLD=0A=
> > >=0A=
> > >    Pseudowire (PW) sequence number support is most important for PW=
=0A=
> > >    payload types with a high expectation of in-order delivery.=0A=
> > >    Resequencing support, rather than dropping at egress on out of ord=
er=0A=
> > >    arrival, is most important for PW payload types with a high=0A=
> > >    expectation of lossless delivery.  For example, TDM payloads requi=
re=0A=
> > >    sequence number support and require resequencing support.  The sam=
e=0A=
> > >    is true of ATM CBR service.  ATM VBR or ABR may have somewhat rela=
xed=0A=
> > >    requirements, but generally require ATM Early Packet Discard (EPD)=
 or=0A=
> > >    ATM Partial Packet Discard (PPD) [ATM-EPD-and-PPD].  Though sequen=
ce=0A=
> > >    number support and resequencing support are beneficial to PW packe=
t=0A=
> > >    oriented payloads such as FR and Ethernet, they are highly desirab=
le=0A=
> > >    but not as strongly required.=0A=
> > >=0A=
> > > NEW=0A=
> > >=0A=
> > >    Pseudowire (PW) sequence number support is most important for PW=
=0A=
> > >    payload types with a high expectation of lossless and/or in-order=
=0A=
> > >    delivery.  Identifying the position of any lost packets is importa=
nt=0A=
> > >    for PW services which are attempting to reconstruct a bit stream=
=0A=
> > >    which maintains bit timing, such as time division multiplexing (TD=
M)=0A=
> > >    services.  TDM and other PW services which require strict ordering=
=0A=
> > >    also require that misordered packets be either dropped or reordere=
d.=0A=
> > >=0A=
> > >    PW services which are not timing critical bit streams in nature ar=
e=0A=
> > >    cell oriented or frame oriented.  Though resequencing support is=
=0A=
> > >    beneficial to PW cell and frame oriented payloads such as ATM, FR =
and=0A=
> > >    Ethernet, they are highly desirable but not required.=0A=
> > >=0A=
> > > NEW (end of subsection after list of possible reording causes)=0A=
> > >=0A=
> > >    In provider networks which use multipath techniques and which may=
=0A=
> > >    occassionally rebalance traffic or which may change PW paths=0A=
> > >    occasionally for other reasons, reordering may be far more common=
=0A=
> > >    than loss.  Where reordering is more common than loss, resequencin=
g=0A=
> > >    packets is beneficial, rather than dropping packets at egress when=
=0A=
> > >    out of order arrival occus.  Resequencing is most important for PW=
=0A=
> > >    payload types with a high expectation of lossless delivery since i=
n=0A=
> > >    such cases out of order delivery within the network results in PW=
=0A=
> > >    loss.=0A=
> > >=0A=
> > > The final paragraph sums up the motivation for highlighting=0A=
> > > resequencing as beneficial and desirable.  It does so without any=0A=
> > > normative wording.=0A=
> > >=0A=
> > > > Hopefully these notes will be useful.=0A=
> > > >=0A=
> > > > Regards,=0A=
> > > >      Sasha=0A=
> > >=0A=
> > > These notes are very useful.  Thank you.=0A=
> > >=0A=
> > > Please let us know if you (and the WG) are OK with the rewording=0A=
> > > proposed above.=0A=
> > >=0A=
> > > Curtis=0A=
=0A=

From Alexander.Vainshtein@ecitele.com  Fri Dec 13 22:27:45 2013
Return-Path: <Alexander.Vainshtein@ecitele.com>
X-Original-To: pwe3@ietfa.amsl.com
Delivered-To: pwe3@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 34D5D1AE4E8; Fri, 13 Dec 2013 22:27:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level: 
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id L9k3Gcpf30vQ; Fri, 13 Dec 2013 22:27:40 -0800 (PST)
Received: from emea01-am1-obe.outbound.protection.outlook.com (mail-am1lp0017.outbound.protection.outlook.com [213.199.154.17]) by ietfa.amsl.com (Postfix) with ESMTP id 4FA461A802D; Fri, 13 Dec 2013 22:27:39 -0800 (PST)
Received: from AM3PR03MB532.eurprd03.prod.outlook.com (10.242.109.156) by AM3PR03MB532.eurprd03.prod.outlook.com (10.242.109.156) with Microsoft SMTP Server (TLS) id 15.0.842.7; Sat, 14 Dec 2013 06:27:30 +0000
Received: from AM3PR03MB532.eurprd03.prod.outlook.com ([10.242.109.156]) by AM3PR03MB532.eurprd03.prod.outlook.com ([10.242.109.156]) with mapi id 15.00.0842.003; Sat, 14 Dec 2013 06:27:29 +0000
From: Alexander Vainshtein <Alexander.Vainshtein@ecitele.com>
To: "curtis@ipv6.occnc.com" <curtis@ipv6.occnc.com>
Thread-Topic: [PWE3] Pseudowire Sequence Number in draft-ietf-mpls-forwarding: a minor comment
Thread-Index: AQHO+JWQSq0tCZZscUehMpHq+OAdtQ==
Date: Sat, 14 Dec 2013 06:27:29 +0000
Message-ID: <0e9fa8a68b14411983975b85d76678ca@AM3PR03MB532.eurprd03.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [5.153.9.203]
x-forefront-prvs: 00603B7EEF
x-forefront-antispam-report: SFV:NSPM; SFS:(10009001)(52604005)(377454003)(43784003)(189002)(199002)(53754006)(13464003)(51704005)(81342001)(65816001)(74502001)(87936001)(83072002)(74706001)(56776001)(76576001)(76786001)(87266001)(76796001)(74876001)(69226001)(51856001)(76176001)(81542001)(2656002)(90146001)(56816005)(47446002)(79102001)(53806001)(63696002)(66066001)(80022001)(76482001)(74662001)(71446004)(85852003)(77982001)(54316002)(81686001)(74366001)(31966008)(74316001)(83322001)(4396001)(46102001)(54356001)(80976001)(81816001)(59766001)(33646001)(47976001)(19580395003)(19580405001)(85306002)(47736001)(50986001)(49866001)(427584002)(24736002)(559001)(579004); DIR:OUT; SFP:1101; SCL:1; SRVR:AM3PR03MB532; H:AM3PR03MB532.eurprd03.prod.outlook.com; CLIP:5.153.9.203; FPR:; RD:InfoNoRecords; MX:1; A:1; LANG:en; 
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: ecitele.com
Cc: "samante@apple.com" <samante@apple.com>, "Yaakov Stein \(yaakov_s@rad.com\)" <yaakov_s@rad.com>, "cpignata@cisco.com" <cpignata@cisco.com>, "kireeti@juniper.net" <kireeti@juniper.net>, "mpls@ietf.org" <mpls@ietf.org>, "curtis@occnc.com" <curtis@occnc.com>, "pwe3 \(pwe3@ietf.org\)" <pwe3@ietf.org>
Subject: Re: [PWE3] Pseudowire Sequence Number in draft-ietf-mpls-forwarding: a minor comment
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Pseudowire Emulation Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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: Sat, 14 Dec 2013 06:27:45 -0000

Curtis,=0A=
Lots of thanks for a prompt and most encouraging response.=0A=
=0A=
I believe that the last proposed text fully addreses both my original comme=
nt and the misunderstanding that has been encountered at some stage in this=
 email thread.=0A=
=0A=
Regards,=0A=
     Sassha=0A=
________________________________________=0A=
From: Curtis Villamizar <curtis@ipv6.occnc.com>=0A=
Sent: Friday, December 13, 2013 9:17 PM=0A=
To: Alexander Vainshtein=0A=
Cc: curtis@ipv6.occnc.com; curtis@occnc.com; kireeti@juniper.net; samante@a=
pple.com; agmalis@gmail.com; cpignata@cisco.com; mpls@ietf.org; Yaakov Stei=
n (yaakov_s@rad.com); pwe3 (pwe3@ietf.org)=0A=
Subject: Re: [PWE3] Pseudowire Sequence Number in draft-ietf-mpls-forwardin=
g: a minor comment=0A=
=0A=
Sasha,=0A=
=0A=
Thanks for pointing out the lack of clarity regarding the context of=0A=
the statement we were discussing.  These are the first three paragraphs=0A=
(originally one) of "2.1.8.1.  Pseudowire Sequence Number" that we've=0A=
been discussing=0A=
=0A=
 Original (draft-ietf-mpls-forwarding-03, short but inaccurate)=0A=
=0A=
   Pseudowire (PW) sequence number support is most important for PW=0A=
   payload types with a high expectation of in-order delivery.=0A=
   Resequencing support, rather than dropping at egress on out of order=0A=
   arrival, is most important for PW payload types with a high=0A=
   expectation of lossless delivery.  For example, TDM payloads require=0A=
   sequence number support and require resequencing support.  The same=0A=
   is true of ATM CBR service.  ATM VBR or ABR may have somewhat relaxed=0A=
   requirements, but generally require ATM Early Packet Discard (EPD) or=0A=
   ATM Partial Packet Discard (PPD) [ATM-EPD-and-PPD].  Though sequence=0A=
   number support and resequencing support are beneficial to PW packet=0A=
   oriented payloads such as FR and Ethernet, they are highly desirable=0A=
   but not as strongly required.=0A=
=0A=
 First change=0A=
=0A=
   Pseudowire (PW) sequence number support is most important for PW=0A=
   payload types with a high expectation of lossless and/or in-order=0A=
   delivery.  Identifying the position of any lost packets is important=0A=
   for PW services which are attempting to reconstruct a bit stream=0A=
   which maintains bit timing, such as time division multiplexing (TDM)=0A=
   services.  TDM and other PW services which require strict ordering=0A=
   also require that misordered packets be either dropped or reordered.=0A=
=0A=
   PW services which are not timing critical bit streams in nature are=0A=
   cell oriented or frame oriented.  Though resequencing support is=0A=
   beneficial to PW cell and frame oriented payloads such as ATM, FR and=0A=
   Ethernet, they are highly desirable but not required.=0A=
=0A=
 Suggested new para (Sasha) - part of second para rewritten=0A=
=0A=
   Pseudowire (PW) sequence number support is most important for PW=0A=
   payload types with a high expectation of lossless and/or in-order=0A=
   delivery.  Identifying lost PW packets and exact amount of lost=0A=
   payload is critical for PW services which maintain bit timing, such=0A=
   as Time Division Multiplexing (TDM) services since these services=0A=
   MUST compensate lost payload on a bit-for-bit basis.=0A=
=0A=
   With these services PW packets that have been received out of order=0A=
   also MUST also be identified and may be either re-ordered or=0A=
   dropped.  Reordering requires, in addition to sequence numbering, a=0A=
   "de-jitter buffer" in the egress PE, and ability to reorder is=0A=
   limited by the depth of this buffer. The down side of maintaining a=0A=
   de-jitter buffer is added end-to-end service delay.=0A=
=0A=
   PW services which are not timing critical bit streams in nature are=0A=
   cell oriented or frame oriented.  Though resequencing support is=0A=
   beneficial to PW cell and frame oriented payloads such as ATM, FR and=0A=
   Ethernet, they are highly desirable but not required.=0A=
=0A=
 Suggested change to above (Curtis) - minor plus add last sentence=0A=
=0A=
   Pseudowire (PW) sequence number support is most important for PW=0A=
   payload types with a high expectation of lossless and/or in-order=0A=
   delivery.  Identifying lost PW packets and exact amount of lost=0A=
   payload is critical for PW services which maintain bit timing, such=0A=
   as Time Division Multiplexing (TDM) services since these services=0A=
   MUST compensate lost payload on a bit-for-bit basis.=0A=
=0A=
   With these services PW packets that have been received out of order=0A=
   also MUST also be identified and may be either re-ordered or=0A=
   dropped.  Reordering requires, in addition to sequence numbering, a=0A=
   "jitter buffer" in the egress PE, and ability to reorder is limited=0A=
   by the depth of this buffer. The down side of maintaining a large=0A=
   jitter buffer is added end-to-end service delay.  A small jitter=0A=
   buffer is always necessary and the jitter buffer is needed=0A=
   regardless of whether reordering is done.=0A=
=0A=
   PW services which are not timing critical bit streams in nature are=0A=
   cell oriented or frame oriented.  Though resequencing support is=0A=
   beneficial to PW cell and frame oriented payloads such as ATM, FR=0A=
   and Ethernet, they are highly desirable but not required.=0A=
=0A=
 Reorder paragraphs and edit for clarity of context=0A=
=0A=
   Pseudowire (PW) sequence number support is most important for PW=0A=
   payload types with a high expectation of lossless and/or in-order=0A=
   delivery.  Identifying lost PW packets and exact amount of lost=0A=
   payload is critical for PW services which maintain bit timing, such=0A=
   as Time Division Multiplexing (TDM) services since these services=0A=
   MUST compensate lost payload on a bit-for-bit basis.=0A=
=0A=
   With PW services which maintain bit timing, packets that have been=0A=
   received out of order also MUST be identified and may be either=0A=
   re-ordered or dropped.  Reordering requires, in addition to=0A=
   sequence numbering, a "reorder buffer" in the egress PE, and ability=0A=
   to reorder is limited by the depth of this buffer. The down side of=0A=
   maintaining a large reorder buffer is added end-to-end service=0A=
   delay.=0A=
=0A=
   For PW services which maintain bit timing or any other service=0A=
   where jitter must be bounded, a jitter buffer is always necessary.=0A=
   The jitter buffer is needed regardless of whether reordering is=0A=
   done.  In order to be effective, a reorder buffer must often be=0A=
   larger than a jitter buffer needs to be creating a tradeoff between=0A=
   reducing loss and minimizing delay.=0A=
=0A=
   PW services which are not timing critical bit streams in nature are=0A=
   cell oriented or frame oriented.  Though resequencing support may=0A=
   be beneficial to PW cell and frame oriented payloads such as ATM,=0A=
   FR and Ethernet, this support is desirable but not required.=0A=
   Requirements to hamdle out of order packets at all vary among=0A=
   services and deployments.  For example for Ethernet PW, occasional=0A=
   (very rare) reordering is usually acceptable.  If the Ethernet PW=0A=
   is carrying MPLS-TP, then this reordering may be acceptable.=0A=
=0A=
   Reducing jitter is best done by an end-system, given that the=0A=
   tradeoff of loss vs delay varies among services.  For example with=0A=
   interactive real time services low delay is preferred, while with=0A=
   non-interactive (one way) real time services low loss is preferred.=0A=
   The same end-site may be receiving both types of traffic.=0A=
   Regardless of this, bounded jitter is sometimes a requiremnet for=0A=
   specific deployments.=0A=
=0A=
In the prior iteration a paragraph began with "With these services"=0A=
following the prior paragraph discussing "PW services which maintain=0A=
bit timing, such as Time Division Multiplexing (TDM) services" which=0A=
did not clearly carry over the context.=0A=
=0A=
At this point, each paragraph clearly indicates its context, either=0A=
bit timing, not bit timing, or all PW.  It also makes a distinction=0A=
between a reorder buffer and a jitter buffer.=0A=
=0A=
This is a more thorough treatment of the tradeoffs of using PW=0A=
sequence in supporting de-jitter and reordering in PW services than=0A=
what was originally in the document (but given that it wasn't correct=0A=
some change was needed).=0A=
=0A=
Curtis=0A=
=0A=
=0A=
ps - Needed to top post a summary since your repeated top posting was=0A=
obscuring the context of the (longish) conversation thread.  You've=0A=
probably seen something like this before:=0A=
=0A=
  You're welcome.=0A=
  I get it.  Thanks.=0A=
  Because it is the default in most pee-cee mailers.=0A=
  Why do people do it so often then?=0A=
  Because it loses context and reverses the order of the discussion.=0A=
  Why?=0A=
  Yes.=0A=
  Is top posting a bad practice?=0A=
=0A=
=0A=
In message <4946c79f4554497d84cd676684739124@AM3PR03MB532.eurprd03.prod.out=
look.com>=0A=
Alexander Vainshtein writes:=0A=
=0A=
Curtis,=0A=
Lots of hanks for a long and detailed explanation.=0A=
=0A=
It appears that your original comment about the need of jitter buffer=0A=
refered to TDM (or TDM-like) PWs (bit-stream PWs in the Architecture=0A=
RFC). If this was indeed the case, there is nothing to argue about,=0A=
because I agree completely that jitter buffer is absolutely necessary=0A=
for these.=0A=
=0A=
My impression from reading the original text has been that it referred=0A=
to ALL kinds of PWs (bit-stream, celland packet) alike. Apparently=0A=
this has been my mis-interptetation; if this is indeed so, then maybe=0A=
some clarification (placing the jiter buffer discussion in the proper=0A=
context) would hopefully help.=0A=
=0A=
Regards,=0A=
     Sasha=0A=
________________________________________=0A=
From: Curtis Villamizar <curtis@ipv6.occnc.com>=0A=
Sent: Thursday, December 12, 2013 6:53 AM=0A=
To: Alexander Vainshtein=0A=
Cc: curtis@occnc.com; curtis@ipv6.occnc.com; kireeti@juniper.net; samante@a=
pple.com; agmalis@gmail.com; cpignata@cisco.com; mpls@ietf.org; Yaakov Stei=
n (yaakov_s@rad.com); pwe3 (pwe3@ietf.org)=0A=
Subject: Re: [PWE3] Pseudowire Sequence Number in draft-ietf-mpls-forwardin=
g: a minor comment=0A=
=0A=
In message <774d74926b684ffba7f4f89ace758547@AM3PR03MB532.eurprd03.prod.out=
look.com>=0A=
Alexander Vainshtein writes:=0A=
=0A=
> Curtis,=0A=
> Lots of thanks for sending out the new text.=0A=
>=0A=
> I still have a couple of issues with this version of the text: one=0A=
> technical and one editorial.=0A=
>=0A=
> The technical issue is about the fragment "A small jitter buffer is=0A=
> always necessary".=0A=
>=0A=
> I am not sure this is correct, since I am aware of several PW=0A=
> implementations that pass the payload of a received PW packet directly=0A=
> for transmission via the corresdponding attachment circuit. Of course=0A=
> this payload would be stored in some Tx queue associated with the=0A=
> attachment circuit and controlled by the appropriate egress scheduler,=0A=
> but IMO this does not constitue a PW jitter bufer, since the PW=0A=
> interworking function does not exersize any control over these=0A=
> queues.=0A=
=0A=
Well if its a technical argument you want, then here goes ...=0A=
=0A=
Even in pure TDM systems some jitter exist due to the longer time it=0A=
takes if multiple passes of the FEC algorithm are needed.  In that=0A=
case there is a very small jitter buffer that can be set to the=0A=
maximum needed for a worst case FEC, or set lower to decrease delay=0A=
with the potential to make a greater number of errors uncorrectable.=0A=
=0A=
For IP, even if IP EF service is used and there is a very small amount=0A=
of EF traffic, some jitter exists.  For most systems there is some=0A=
jitter crossing the fabric and internal jitter elsewhere.  The egress=0A=
buffer in most chips is very small but needed for that jitter.  For=0A=
TDM, the egress buffer can never run dry or there will be a timing=0A=
slip.=0A=
=0A=
Consider what happens when packets arrive late in a system with only a=0A=
non-zero egress buffer.  For example, assume 1% of packets arrive=0A=
about one packet time late (one other EF packet in queue somewhere on=0A=
the path), 0.1% arrive two packets late.  Note that this would be an=0A=
extremely light EF load.  Generally most packets arrive at least zero=0A=
to one minus epsilon packet times late due to a lower priority packet=0A=
partially transmited when the EF packet is moved to the front of the=0A=
queue.  If there is no egress buffer at all or considerably less than=0A=
a packet time, lots of data would be dropped.  If the egress buffer=0A=
could hold just a few packets data drop would be very low.=0A=
=0A=
If a packet arrives late and there is no standing queue the egress=0A=
runs dry, there is a timing slip.  When the packet does arrive a=0A=
little late the packet is sent, albiet late.  Every packet to follow=0A=
is now late by that amount of time (if the egress buffer has not=0A=
overflowed on a later packet).=0A=
=0A=
At that point there is an standing queue in the egress buffer which=0A=
acts as a jitter buffer.  Most packets arrive early.  A few arrive a=0A=
little later but as long as the queue doesn't run dry again, the=0A=
jitter is compensated for.=0A=
=0A=
If the egress buffer is large, then it will tend to grow to the worst=0A=
case packet delay and keep a large standing queue.  This is with no=0A=
reorder and no drop.  If the egress buffer is small (or configured to=0A=
be small) then when a packet arrives very late followed by a set of=0A=
packets in close succession, the buffer runs dry until that first late=0A=
packet arrives.  This packet is transmitted but very late.  Subsequent=0A=
packets arrive and some of them have to be dropped due to the limited=0A=
queue capacity.  This in effect puts a cap on the jitter buffer.=0A=
=0A=
With only an egress buffer there are multiple strategies for dealing=0A=
with dropped packets.=0A=
=0A=
  1.  Just ignore it and send the next one.=0A=
  2.  Put one packet time worth of all zeros in the queue.=0A=
=0A=
Now consider what happens with a dropped packet and a standing queue.=0A=
The first strategy creates a hidden timing slip.  The second strategy=0A=
avoids the timing slip.=0A=
=0A=
So my argument is that the egress buffer is in effect the jitter=0A=
buffer.  When jitter occurs a standing buffer forms that reflects the=0A=
lesser of the limit of the buffer size or the worst case jitter.=0A=
There is always a jitter buffer.  There always needs to be a jitter=0A=
buffer of at least one large packet time, otherwise high loss of data=0A=
will occur.  There should be a jitter buffer that can be made larger=0A=
so that jitter of multiple packet times doesn't turn in to loss.=0A=
=0A=
Therefore I assert that a jitter buffer is always present and is=0A=
always needed because jitter is always non-zero.  Therefore this=0A=
statement is true:=0A=
=0A=
   A small jitter buffer is always necessary and the jitter buffer is=0A=
   needed regardless of whether reordering is done.=0A=
=0A=
> In particular, these queues could not be used for re-ordering=0A=
> misordered PW packets.=0A=
=0A=
That does not mean that they can't be used to compensate for jitter=0A=
which is by definition what a jitter buffer is for.=0A=
=0A=
When reordering is done, the egress buffer is made small and a buffer=0A=
preceding that is used which has some ability to reorder packets.  In=0A=
hardware a circular queue makes sense with packets place according to=0A=
their sequence number.  If you prescribe to the "just insert zeros"=0A=
idea when a packet is dropped, then after moving a packet to the=0A=
egress queue, zero the buffer or mark it as unoccupied and more the=0A=
circular buffer a bit.  If the packet that is later supposed to occupy=0A=
that slot never arrives, then it is already zerod (or marked as=0A=
missing in which case a packet of all zeros is put on the egress=0A=
queue).=0A=
=0A=
So ... reording within a small jitter buffer is not hard to do.=0A=
=0A=
Reordering can be supported with a small jitter buffer but adding=0A=
reordering to a small buffer may be ineffective.  If reordering is due=0A=
to a path change, then the buffer of a small number of packet times=0A=
may yield no improvement.  To be effective in that situation, the=0A=
buffer may need to be larger.  OTOH if moving EF traffic from one=0A=
queue with no standing EF queue to another with no standing EF queue=0A=
and the path change is just moving to another wave on the WDM,=0A=
reordering with a small jitter buffer may help.=0A=
=0A=
> IMHO and FWIW this understanding matches RFC 3985 which mentions (in=0A=
> Section 5.2.1.1 "Frame Ordering") that reodering as the strategy for=0A=
> handling mis-ordered packets introduces additional delay (i.e.,=0A=
> requires a ddicated jitter buffer), while the alternative strategy of=0A=
> discarding mis-ordered packets does not introduce such additional=0A=
> delay.=0A=
=0A=
You quoted the framework and not a TDM document.  Nowhere in that text=0A=
is there mention of a jitter buffer because that text is not specific=0A=
to TDM.=0A=
=0A=
For packet traffic you have no idea if a prior packet is dropped or=0A=
will arrive out of order and so when a drop occurs packets have to be=0A=
held for a non-zero amount of time rather than transmitted as soon as=0A=
they arrive.  This applies to all cell or packet AC, such as FR, ATM,=0A=
Ethernet, etc.=0A=
=0A=
You might want to look at section 5.2.2.1.  Clock Recovery which does=0A=
apply to TDM.  It points to RFC3550 (RTP) which assumes a jitter=0A=
buffer is always needed.=0A=
=0A=
> The editorial issue is about the entire sentence that contains the=0A=
> above-mentioned fragment, i.e., "A small jitter buffer is always=0A=
> necessary and the jitter buffer is needed regardless of whether=0A=
> reordering is done" - to me this looks like an unnecessary repetition=0A=
> if if it were techically correct.=0A=
=0A=
The second part of the sentence was to emphasis that the need for a=0A=
jitter buffer is not contingent on implementation or reordering.=0A=
Perhaps it would be more clear if the two points were separated.  How=0A=
about this=0A=
=0A=
 OLD new sentence=0A=
=0A=
   A small jitter buffer is always necessary and the jitter buffer=0A=
   is needed regardless of whether reordering is done.=0A=
=0A=
 NEW new sentence=0A=
=0A=
   A small jitter buffer is always necessary.  A jitter buffer is=0A=
   needed regardless of whether reordering is done.=0A=
=0A=
> Hence I would like to suggest discrading the problematic sentence as=0A=
> the simplest way to resolve both issues.=0A=
=0A=
I think the sentence provides an important clarification.  I think the=0A=
need to have this discussion proves that the clarification is needed.=0A=
=0A=
If we can agree on keeping this, I can submit the updated draft.=0A=
=0A=
> Hopefully these notes will e helpful.=0A=
>=0A=
> Regards,=0A=
>      Sasha=0A=
=0A=
Thanks again for the review and good comments.=0A=
=0A=
Regards,=0A=
=0A=
Curtis=0A=
=0A=
=0A=
> ________________________________________=0A=
> From: Curtis Villamizar <curtis@occnc.com>=0A=
> Sent: Tuesday, December 10, 2013 5:47 PM=0A=
> To: Alexander Vainshtein=0A=
> Cc: curtis@ipv6.occnc.com; curtis@occnc.com; kireeti@juniper.net; samante=
@apple.com; agmalis@gmail.com; cpignata@cisco.com; mpls@ietf.org; Yaakov St=
ein (yaakov_s@rad.com); pwe3 (pwe3@ietf.org)=0A=
> Subject: Re: [PWE3] Pseudowire Sequence Number in draft-ietf-mpls-forward=
ing: a minor comment=0A=
>=0A=
> In message <F9336571731ADE42A5397FC831CEAA025AC56C9D@ILPTWPVEXMB02.ecitel=
e.com>=0A=
> Alexander Vainshtein writes:=0A=
> >=0A=
> > Curtis,=0A=
> >=0A=
> > Lots of thanks for a prompt and very detailed response.=0A=
> > May I suggest an alternative version of the following text fragment?=0A=
> >=0A=
> > <Curtis>=0A=
> > >   Identifying the position of any lost packets is important=0A=
> > >    for PW services which are attempting to reconstruct a bit stream=
=0A=
> > >    which maintains bit timing, such as time division multiplexing (TD=
M)=0A=
> > >    services.  TDM and other PW services which require strict ordering=
=0A=
> > >    also require that misordered packets be either dropped or reordere=
d.=0A=
>=0A=
> Invalid XML - you didn't close this element.  :-)=0A=
>=0A=
> >  <Sasha>=0A=
> >=0A=
> >    Identifying lost PW packets and exact amount of lost payload is=0A=
> >    critical for PW services which maintain bit timing, such as Time=0A=
> >    Division Multiplexing (TDM) services since these services MUST=0A=
> >    compensate lost payload on a bit-for-bit basis.=0A=
> >=0A=
> >    With these services PW packets that have been received out of order=
=0A=
> >    also MUST also be identified and may be either re-ordered or=0A=
> >    dropped.  Reordering requires, in addition to sequence numbering, a=
=0A=
> >    "de-jitter buffer" in the egress PE, and ability to reorder is=0A=
> >    limited by the depth of this buffer. The down side of maintaining a=
=0A=
> >    de-jitter buffer is added end-to-end service delay.=0A=
> >=0A=
> >   </Sasha>=0A=
>=0A=
> Accepted with a small change.=0A=
>=0A=
> After the words "down side"=0A=
> s/de-jitter buffer/large jitter buffer/=0A=
> Elsewhere=0A=
> s/de-jitter buffer/jitter buffer/g=0A=
> Then add the sentence.=0A=
>=0A=
>    A small jitter buffer is always necessary and the jitter buffer=0A=
>    is needed regardless of whether reordering is done.=0A=
>=0A=
> This yields a slightly changed second paragraph.=0A=
>=0A=
>    With these services PW packets that have been received out of order=0A=
>    also MUST also be identified and may be either re-ordered or=0A=
>    dropped.  Reordering requires, in addition to sequence numbering, a=0A=
>    "jitter buffer" in the egress PE, and ability to reorder is limited=0A=
>    by the depth of this buffer. The down side of maintaining a large=0A=
>    jitter buffer is added end-to-end service delay.  A small jitter=0A=
>    buffer is always necessary and the jitter buffer is needed=0A=
>    regardless of whether reordering is done.=0A=
>=0A=
> Is this wording OK with you?=0A=
>=0A=
> Curtis=0A=
>=0A=
> > Hopefully this will be useful.=0A=
> >=0A=
> >=0A=
> > Regards,=0A=
> >      Sasha=0A=
> >=0A=
> > > -----Original Message-----=0A=
> > > From: Curtis Villamizar [mailto:curtis@ipv6.occnc.com]=0A=
> > > Sent: Monday, November 25, 2013 8:30 PM=0A=
> > > To: Alexander Vainshtein=0A=
> > > Cc: curtis@occnc.com; kireeti@juniper.net; samante@apple.com;=0A=
> > > agmalis@gmail.com; cpignata@cisco.com; mpls@ietf.org; Yaakov Stein=0A=
> > > (yaakov_s@rad.com); pwe3 (pwe3@ietf.org)=0A=
> > > Subject: Re: [PWE3] Pseudowire Sequence Number in draft-ietf-mpls-=0A=
> > > forwarding: a minor comment=0A=
> > >=0A=
> > >=0A=
> > > In message=0A=
> > > <F9336571731ADE42A5397FC831CEAA025392F92F@ILPTWPVEXMB01.ecitele.c=0A=
> > > om>=0A=
> > > Alexander Vainshtein writes:=0A=
> > > >=0A=
> > > > Hi all,=0A=
> > > >=0A=
> > > > I would like to comment on the text in Section 2.1.8.1 "Pseudowire=
=0A=
> > > > Sequence Number" in draft-ietf-mpls-forwarding-03 - MPLS Forwarding=
=0A=
> > > > Compliance and Performance Requirements=0A=
> > > > <http://tools.ietf.org/html/draft-ietf-mpls-forwarding-03>.=0A=
> > > >=0A=
> > > > This section states, in short, that the main drive for using the=0A=
> > > > sequence number in the PW Control Word is handling of packet=0A=
> > > > reordering events. TDM PWs are presented as a major example, with C=
BR=0A=
> > > > ATM services as another example.=0A=
> > > >=0A=
> > > > In fact, this statement is not accurate.=0A=
> > >=0A=
> > > Yes.  You are correct in pointing this out as inaccurate by omitting=
=0A=
> > > the other important function of identifying drops for the purpose of=
=0A=
> > > recunstructing TDM bit streams.=0A=
> > >=0A=
> > > Andy brought up resequencing being a strong provider request.=0A=
> > > Reordering is far more common than loss particularly for high priorit=
y=0A=
> > > services on provider networks and without resequencing reorder result=
s=0A=
> > > in PW loss in what could otherwise be lossless service.=0A=
> > >=0A=
> > > So we should get the base requirements right but still reflect this,=
=0A=
> > > but strictly as advice with no normative wording.  We had used the=0A=
> > > phrase "is beneficial" and will retain that.=0A=
> > >=0A=
> > > Andy brought up the topic.  The incorrect wording in the existing=0A=
> > > draft is my fault.  This text went in fairly early with a lot of othe=
r=0A=
> > > changes and it appears that no one had since given it a careful enoug=
h=0A=
> > > read and review until you came along.=0A=
> > >=0A=
> > > > The main drive for mandating the use of sequence number in TM PWs i=
s=0A=
> > > > the need to detect and count lost packets because the egress PE MUS=
T=0A=
> > > > compensate the lost payload bit for bit.=0A=
> > > >=0A=
> > > > Ability to compensate reordering of PW packets at egress is a side=
=0A=
> > > > effect of (a) sequence number usage and (b) usage of the de-jitter=
=0A=
> > > > buffer in the egress PW. It is not mandatory and in any case is=0A=
> > > > limited by the depth of the de-jitter buffer: re-ordered packets th=
at=0A=
> > > > cannot be accommodated within this buffer are treated as lost.=0A=
> > > >=0A=
> > > > Additional details can be found, e.g., in section 6.2.2 of RFC=0A=
> > > > 4553<http://tools.ietf.org/html/rfc4553>. Ability to re-order=0A=
> > > > mis-ordered PW packets is defined there as OPTIONAL, while replacem=
ent=0A=
> > > > of the payload of lost PW packets is defined as MANDATORY.=0A=
> > >=0A=
> > > The change below at the top of the section more accurately reflects=
=0A=
> > > requirements in the RFCs but still states that resequencing can be=0A=
> > > beneficial.  The comments about EPD and PPD are dropped and therefore=
=0A=
> > > also the informative reference.=0A=
> > >=0A=
> > >  Context:=0A=
> > >=0A=
> > >  2.1.8.1.  Pseudowire Sequence Number=0A=
> > >=0A=
> > >  OLD=0A=
> > >=0A=
> > >    Pseudowire (PW) sequence number support is most important for PW=
=0A=
> > >    payload types with a high expectation of in-order delivery.=0A=
> > >    Resequencing support, rather than dropping at egress on out of ord=
er=0A=
> > >    arrival, is most important for PW payload types with a high=0A=
> > >    expectation of lossless delivery.  For example, TDM payloads requi=
re=0A=
> > >    sequence number support and require resequencing support.  The sam=
e=0A=
> > >    is true of ATM CBR service.  ATM VBR or ABR may have somewhat rela=
xed=0A=
> > >    requirements, but generally require ATM Early Packet Discard (EPD)=
 or=0A=
> > >    ATM Partial Packet Discard (PPD) [ATM-EPD-and-PPD].  Though sequen=
ce=0A=
> > >    number support and resequencing support are beneficial to PW packe=
t=0A=
> > >    oriented payloads such as FR and Ethernet, they are highly desirab=
le=0A=
> > >    but not as strongly required.=0A=
> > >=0A=
> > > NEW=0A=
> > >=0A=
> > >    Pseudowire (PW) sequence number support is most important for PW=
=0A=
> > >    payload types with a high expectation of lossless and/or in-order=
=0A=
> > >    delivery.  Identifying the position of any lost packets is importa=
nt=0A=
> > >    for PW services which are attempting to reconstruct a bit stream=
=0A=
> > >    which maintains bit timing, such as time division multiplexing (TD=
M)=0A=
> > >    services.  TDM and other PW services which require strict ordering=
=0A=
> > >    also require that misordered packets be either dropped or reordere=
d.=0A=
> > >=0A=
> > >    PW services which are not timing critical bit streams in nature ar=
e=0A=
> > >    cell oriented or frame oriented.  Though resequencing support is=
=0A=
> > >    beneficial to PW cell and frame oriented payloads such as ATM, FR =
and=0A=
> > >    Ethernet, they are highly desirable but not required.=0A=
> > >=0A=
> > > NEW (end of subsection after list of possible reording causes)=0A=
> > >=0A=
> > >    In provider networks which use multipath techniques and which may=
=0A=
> > >    occassionally rebalance traffic or which may change PW paths=0A=
> > >    occasionally for other reasons, reordering may be far more common=
=0A=
> > >    than loss.  Where reordering is more common than loss, resequencin=
g=0A=
> > >    packets is beneficial, rather than dropping packets at egress when=
=0A=
> > >    out of order arrival occus.  Resequencing is most important for PW=
=0A=
> > >    payload types with a high expectation of lossless delivery since i=
n=0A=
> > >    such cases out of order delivery within the network results in PW=
=0A=
> > >    loss.=0A=
> > >=0A=
> > > The final paragraph sums up the motivation for highlighting=0A=
> > > resequencing as beneficial and desirable.  It does so without any=0A=
> > > normative wording.=0A=
> > >=0A=
> > > > Hopefully these notes will be useful.=0A=
> > > >=0A=
> > > > Regards,=0A=
> > > >      Sasha=0A=
> > >=0A=
> > > These notes are very useful.  Thank you.=0A=
> > >=0A=
> > > Please let us know if you (and the WG) are OK with the rewording=0A=
> > > proposed above.=0A=
> > >=0A=
> > > Curtis=0A=
=0A=

From Alexander.Vainshtein@ecitele.com  Fri Dec 13 22:28:49 2013
Return-Path: <Alexander.Vainshtein@ecitele.com>
X-Original-To: pwe3@ietfa.amsl.com
Delivered-To: pwe3@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1C86B1AE4E7; Fri, 13 Dec 2013 22:28:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level: 
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HH07WchPCwGO; Fri, 13 Dec 2013 22:28:44 -0800 (PST)
Received: from emea01-am1-obe.outbound.protection.outlook.com (mail-am1lp0011.outbound.protection.outlook.com [213.199.154.11]) by ietfa.amsl.com (Postfix) with ESMTP id BB2E01AE4F0; Fri, 13 Dec 2013 22:28:42 -0800 (PST)
Received: from AM3PR03MB532.eurprd03.prod.outlook.com (10.242.109.156) by AM3PR03MB531.eurprd03.prod.outlook.com (10.242.109.155) with Microsoft SMTP Server (TLS) id 15.0.842.7; Sat, 14 Dec 2013 06:28:33 +0000
Received: from AM3PR03MB532.eurprd03.prod.outlook.com ([10.242.109.156]) by AM3PR03MB532.eurprd03.prod.outlook.com ([10.242.109.156]) with mapi id 15.00.0842.003; Sat, 14 Dec 2013 06:28:33 +0000
From: Alexander Vainshtein <Alexander.Vainshtein@ecitele.com>
To: "curtis@ipv6.occnc.com" <curtis@ipv6.occnc.com>
Thread-Topic: [PWE3] Pseudowire Sequence Number in draft-ietf-mpls-forwarding: a minor comment
Thread-Index: AQHO+JWQSq0tCZZscUehMpHq+OAdtZpTOhu1
Date: Sat, 14 Dec 2013 06:28:33 +0000
Message-ID: <ae73bface437479cb112d724f5d642a7@AM3PR03MB532.eurprd03.prod.outlook.com>
References: <0e9fa8a68b14411983975b85d76678ca@AM3PR03MB532.eurprd03.prod.outlook.com>
In-Reply-To: <0e9fa8a68b14411983975b85d76678ca@AM3PR03MB532.eurprd03.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [5.153.9.203]
x-forefront-prvs: 00603B7EEF
x-forefront-antispam-report: SFV:NSPM; SFS:(10009001)(43784003)(199002)(189002)(53754006)(51704005)(52604005)(377454003)(13464003)(74316001)(31966008)(83322001)(19580395003)(19580405001)(54316002)(77982001)(85852003)(71446004)(85306002)(33646001)(50986001)(47976001)(47736001)(49866001)(4396001)(81816001)(59766001)(80976001)(65816001)(46102001)(81686001)(74662001)(76576001)(74706001)(76796001)(76786001)(83072002)(53806001)(69226001)(87266001)(74876001)(2656002)(51856001)(81542001)(81342001)(87936001)(74502001)(56776001)(66066001)(80022001)(63696002)(74366001)(76482001)(54356001)(47446002)(79102001)(90146001)(56816005)(427584002)(24736002)(559001)(579004); DIR:OUT; SFP:1101; SCL:1; SRVR:AM3PR03MB531; H:AM3PR03MB532.eurprd03.prod.outlook.com; CLIP:5.153.9.203; FPR:; RD:InfoNoRecords; A:1; MX:1; LANG:en; 
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: ecitele.com
Cc: "samante@apple.com" <samante@apple.com>, "Yaakov Stein \(yaakov_s@rad.com\)" <yaakov_s@rad.com>, "cpignata@cisco.com" <cpignata@cisco.com>, "kireeti@juniper.net" <kireeti@juniper.net>, "mpls@ietf.org" <mpls@ietf.org>, "curtis@occnc.com" <curtis@occnc.com>, "pwe3 \(pwe3@ietf.org\)" <pwe3@ietf.org>
Subject: Re: [PWE3] Pseudowire Sequence Number in draft-ietf-mpls-forwarding: a minor comment
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Pseudowire Emulation Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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: Sat, 14 Dec 2013 06:28:49 -0000

Re-sending due to an unspecified issue with my mail server... =0A=
________________________________________=0A=
From: Alexander Vainshtein=0A=
Sent: Saturday, December 14, 2013 8:27 AM=0A=
To: curtis@ipv6.occnc.com=0A=
Cc: curtis@occnc.com; kireeti@juniper.net; samante@apple.com; agmalis@gmail=
.com; cpignata@cisco.com; mpls@ietf.org; Yaakov Stein (yaakov_s@rad.com); p=
we3 (pwe3@ietf.org)=0A=
Subject: RE: [PWE3] Pseudowire Sequence Number in draft-ietf-mpls-forwardin=
g: a minor comment=0A=
=0A=
Curtis,=0A=
Lots of thanks for a prompt and most encouraging response.=0A=
=0A=
I believe that the last proposed text fully addreses both my original comme=
nt and the misunderstanding that has been encountered at some stage in this=
 email thread.=0A=
=0A=
Regards,=0A=
     Sassha=0A=
________________________________________=0A=
From: Curtis Villamizar <curtis@ipv6.occnc.com>=0A=
Sent: Friday, December 13, 2013 9:17 PM=0A=
To: Alexander Vainshtein=0A=
Cc: curtis@ipv6.occnc.com; curtis@occnc.com; kireeti@juniper.net; samante@a=
pple.com; agmalis@gmail.com; cpignata@cisco.com; mpls@ietf.org; Yaakov Stei=
n (yaakov_s@rad.com); pwe3 (pwe3@ietf.org)=0A=
Subject: Re: [PWE3] Pseudowire Sequence Number in draft-ietf-mpls-forwardin=
g: a minor comment=0A=
=0A=
Sasha,=0A=
=0A=
Thanks for pointing out the lack of clarity regarding the context of=0A=
the statement we were discussing.  These are the first three paragraphs=0A=
(originally one) of "2.1.8.1.  Pseudowire Sequence Number" that we've=0A=
been discussing=0A=
=0A=
 Original (draft-ietf-mpls-forwarding-03, short but inaccurate)=0A=
=0A=
   Pseudowire (PW) sequence number support is most important for PW=0A=
   payload types with a high expectation of in-order delivery.=0A=
   Resequencing support, rather than dropping at egress on out of order=0A=
   arrival, is most important for PW payload types with a high=0A=
   expectation of lossless delivery.  For example, TDM payloads require=0A=
   sequence number support and require resequencing support.  The same=0A=
   is true of ATM CBR service.  ATM VBR or ABR may have somewhat relaxed=0A=
   requirements, but generally require ATM Early Packet Discard (EPD) or=0A=
   ATM Partial Packet Discard (PPD) [ATM-EPD-and-PPD].  Though sequence=0A=
   number support and resequencing support are beneficial to PW packet=0A=
   oriented payloads such as FR and Ethernet, they are highly desirable=0A=
   but not as strongly required.=0A=
=0A=
 First change=0A=
=0A=
   Pseudowire (PW) sequence number support is most important for PW=0A=
   payload types with a high expectation of lossless and/or in-order=0A=
   delivery.  Identifying the position of any lost packets is important=0A=
   for PW services which are attempting to reconstruct a bit stream=0A=
   which maintains bit timing, such as time division multiplexing (TDM)=0A=
   services.  TDM and other PW services which require strict ordering=0A=
   also require that misordered packets be either dropped or reordered.=0A=
=0A=
   PW services which are not timing critical bit streams in nature are=0A=
   cell oriented or frame oriented.  Though resequencing support is=0A=
   beneficial to PW cell and frame oriented payloads such as ATM, FR and=0A=
   Ethernet, they are highly desirable but not required.=0A=
=0A=
 Suggested new para (Sasha) - part of second para rewritten=0A=
=0A=
   Pseudowire (PW) sequence number support is most important for PW=0A=
   payload types with a high expectation of lossless and/or in-order=0A=
   delivery.  Identifying lost PW packets and exact amount of lost=0A=
   payload is critical for PW services which maintain bit timing, such=0A=
   as Time Division Multiplexing (TDM) services since these services=0A=
   MUST compensate lost payload on a bit-for-bit basis.=0A=
=0A=
   With these services PW packets that have been received out of order=0A=
   also MUST also be identified and may be either re-ordered or=0A=
   dropped.  Reordering requires, in addition to sequence numbering, a=0A=
   "de-jitter buffer" in the egress PE, and ability to reorder is=0A=
   limited by the depth of this buffer. The down side of maintaining a=0A=
   de-jitter buffer is added end-to-end service delay.=0A=
=0A=
   PW services which are not timing critical bit streams in nature are=0A=
   cell oriented or frame oriented.  Though resequencing support is=0A=
   beneficial to PW cell and frame oriented payloads such as ATM, FR and=0A=
   Ethernet, they are highly desirable but not required.=0A=
=0A=
 Suggested change to above (Curtis) - minor plus add last sentence=0A=
=0A=
   Pseudowire (PW) sequence number support is most important for PW=0A=
   payload types with a high expectation of lossless and/or in-order=0A=
   delivery.  Identifying lost PW packets and exact amount of lost=0A=
   payload is critical for PW services which maintain bit timing, such=0A=
   as Time Division Multiplexing (TDM) services since these services=0A=
   MUST compensate lost payload on a bit-for-bit basis.=0A=
=0A=
   With these services PW packets that have been received out of order=0A=
   also MUST also be identified and may be either re-ordered or=0A=
   dropped.  Reordering requires, in addition to sequence numbering, a=0A=
   "jitter buffer" in the egress PE, and ability to reorder is limited=0A=
   by the depth of this buffer. The down side of maintaining a large=0A=
   jitter buffer is added end-to-end service delay.  A small jitter=0A=
   buffer is always necessary and the jitter buffer is needed=0A=
   regardless of whether reordering is done.=0A=
=0A=
   PW services which are not timing critical bit streams in nature are=0A=
   cell oriented or frame oriented.  Though resequencing support is=0A=
   beneficial to PW cell and frame oriented payloads such as ATM, FR=0A=
   and Ethernet, they are highly desirable but not required.=0A=
=0A=
 Reorder paragraphs and edit for clarity of context=0A=
=0A=
   Pseudowire (PW) sequence number support is most important for PW=0A=
   payload types with a high expectation of lossless and/or in-order=0A=
   delivery.  Identifying lost PW packets and exact amount of lost=0A=
   payload is critical for PW services which maintain bit timing, such=0A=
   as Time Division Multiplexing (TDM) services since these services=0A=
   MUST compensate lost payload on a bit-for-bit basis.=0A=
=0A=
   With PW services which maintain bit timing, packets that have been=0A=
   received out of order also MUST be identified and may be either=0A=
   re-ordered or dropped.  Reordering requires, in addition to=0A=
   sequence numbering, a "reorder buffer" in the egress PE, and ability=0A=
   to reorder is limited by the depth of this buffer. The down side of=0A=
   maintaining a large reorder buffer is added end-to-end service=0A=
   delay.=0A=
=0A=
   For PW services which maintain bit timing or any other service=0A=
   where jitter must be bounded, a jitter buffer is always necessary.=0A=
   The jitter buffer is needed regardless of whether reordering is=0A=
   done.  In order to be effective, a reorder buffer must often be=0A=
   larger than a jitter buffer needs to be creating a tradeoff between=0A=
   reducing loss and minimizing delay.=0A=
=0A=
   PW services which are not timing critical bit streams in nature are=0A=
   cell oriented or frame oriented.  Though resequencing support may=0A=
   be beneficial to PW cell and frame oriented payloads such as ATM,=0A=
   FR and Ethernet, this support is desirable but not required.=0A=
   Requirements to hamdle out of order packets at all vary among=0A=
   services and deployments.  For example for Ethernet PW, occasional=0A=
   (very rare) reordering is usually acceptable.  If the Ethernet PW=0A=
   is carrying MPLS-TP, then this reordering may be acceptable.=0A=
=0A=
   Reducing jitter is best done by an end-system, given that the=0A=
   tradeoff of loss vs delay varies among services.  For example with=0A=
   interactive real time services low delay is preferred, while with=0A=
   non-interactive (one way) real time services low loss is preferred.=0A=
   The same end-site may be receiving both types of traffic.=0A=
   Regardless of this, bounded jitter is sometimes a requiremnet for=0A=
   specific deployments.=0A=
=0A=
In the prior iteration a paragraph began with "With these services"=0A=
following the prior paragraph discussing "PW services which maintain=0A=
bit timing, such as Time Division Multiplexing (TDM) services" which=0A=
did not clearly carry over the context.=0A=
=0A=
At this point, each paragraph clearly indicates its context, either=0A=
bit timing, not bit timing, or all PW.  It also makes a distinction=0A=
between a reorder buffer and a jitter buffer.=0A=
=0A=
This is a more thorough treatment of the tradeoffs of using PW=0A=
sequence in supporting de-jitter and reordering in PW services than=0A=
what was originally in the document (but given that it wasn't correct=0A=
some change was needed).=0A=
=0A=
Curtis=0A=
=0A=
=0A=
ps - Needed to top post a summary since your repeated top posting was=0A=
obscuring the context of the (longish) conversation thread.  You've=0A=
probably seen something like this before:=0A=
=0A=
  You're welcome.=0A=
  I get it.  Thanks.=0A=
  Because it is the default in most pee-cee mailers.=0A=
  Why do people do it so often then?=0A=
  Because it loses context and reverses the order of the discussion.=0A=
  Why?=0A=
  Yes.=0A=
  Is top posting a bad practice?=0A=
=0A=
=0A=
In message <4946c79f4554497d84cd676684739124@AM3PR03MB532.eurprd03.prod.out=
look.com>=0A=
Alexander Vainshtein writes:=0A=
=0A=
Curtis,=0A=
Lots of hanks for a long and detailed explanation.=0A=
=0A=
It appears that your original comment about the need of jitter buffer=0A=
refered to TDM (or TDM-like) PWs (bit-stream PWs in the Architecture=0A=
RFC). If this was indeed the case, there is nothing to argue about,=0A=
because I agree completely that jitter buffer is absolutely necessary=0A=
for these.=0A=
=0A=
My impression from reading the original text has been that it referred=0A=
to ALL kinds of PWs (bit-stream, celland packet) alike. Apparently=0A=
this has been my mis-interptetation; if this is indeed so, then maybe=0A=
some clarification (placing the jiter buffer discussion in the proper=0A=
context) would hopefully help.=0A=
=0A=
Regards,=0A=
     Sasha=0A=
________________________________________=0A=
From: Curtis Villamizar <curtis@ipv6.occnc.com>=0A=
Sent: Thursday, December 12, 2013 6:53 AM=0A=
To: Alexander Vainshtein=0A=
Cc: curtis@occnc.com; curtis@ipv6.occnc.com; kireeti@juniper.net; samante@a=
pple.com; agmalis@gmail.com; cpignata@cisco.com; mpls@ietf.org; Yaakov Stei=
n (yaakov_s@rad.com); pwe3 (pwe3@ietf.org)=0A=
Subject: Re: [PWE3] Pseudowire Sequence Number in draft-ietf-mpls-forwardin=
g: a minor comment=0A=
=0A=
In message <774d74926b684ffba7f4f89ace758547@AM3PR03MB532.eurprd03.prod.out=
look.com>=0A=
Alexander Vainshtein writes:=0A=
=0A=
> Curtis,=0A=
> Lots of thanks for sending out the new text.=0A=
>=0A=
> I still have a couple of issues with this version of the text: one=0A=
> technical and one editorial.=0A=
>=0A=
> The technical issue is about the fragment "A small jitter buffer is=0A=
> always necessary".=0A=
>=0A=
> I am not sure this is correct, since I am aware of several PW=0A=
> implementations that pass the payload of a received PW packet directly=0A=
> for transmission via the corresdponding attachment circuit. Of course=0A=
> this payload would be stored in some Tx queue associated with the=0A=
> attachment circuit and controlled by the appropriate egress scheduler,=0A=
> but IMO this does not constitue a PW jitter bufer, since the PW=0A=
> interworking function does not exersize any control over these=0A=
> queues.=0A=
=0A=
Well if its a technical argument you want, then here goes ...=0A=
=0A=
Even in pure TDM systems some jitter exist due to the longer time it=0A=
takes if multiple passes of the FEC algorithm are needed.  In that=0A=
case there is a very small jitter buffer that can be set to the=0A=
maximum needed for a worst case FEC, or set lower to decrease delay=0A=
with the potential to make a greater number of errors uncorrectable.=0A=
=0A=
For IP, even if IP EF service is used and there is a very small amount=0A=
of EF traffic, some jitter exists.  For most systems there is some=0A=
jitter crossing the fabric and internal jitter elsewhere.  The egress=0A=
buffer in most chips is very small but needed for that jitter.  For=0A=
TDM, the egress buffer can never run dry or there will be a timing=0A=
slip.=0A=
=0A=
Consider what happens when packets arrive late in a system with only a=0A=
non-zero egress buffer.  For example, assume 1% of packets arrive=0A=
about one packet time late (one other EF packet in queue somewhere on=0A=
the path), 0.1% arrive two packets late.  Note that this would be an=0A=
extremely light EF load.  Generally most packets arrive at least zero=0A=
to one minus epsilon packet times late due to a lower priority packet=0A=
partially transmited when the EF packet is moved to the front of the=0A=
queue.  If there is no egress buffer at all or considerably less than=0A=
a packet time, lots of data would be dropped.  If the egress buffer=0A=
could hold just a few packets data drop would be very low.=0A=
=0A=
If a packet arrives late and there is no standing queue the egress=0A=
runs dry, there is a timing slip.  When the packet does arrive a=0A=
little late the packet is sent, albiet late.  Every packet to follow=0A=
is now late by that amount of time (if the egress buffer has not=0A=
overflowed on a later packet).=0A=
=0A=
At that point there is an standing queue in the egress buffer which=0A=
acts as a jitter buffer.  Most packets arrive early.  A few arrive a=0A=
little later but as long as the queue doesn't run dry again, the=0A=
jitter is compensated for.=0A=
=0A=
If the egress buffer is large, then it will tend to grow to the worst=0A=
case packet delay and keep a large standing queue.  This is with no=0A=
reorder and no drop.  If the egress buffer is small (or configured to=0A=
be small) then when a packet arrives very late followed by a set of=0A=
packets in close succession, the buffer runs dry until that first late=0A=
packet arrives.  This packet is transmitted but very late.  Subsequent=0A=
packets arrive and some of them have to be dropped due to the limited=0A=
queue capacity.  This in effect puts a cap on the jitter buffer.=0A=
=0A=
With only an egress buffer there are multiple strategies for dealing=0A=
with dropped packets.=0A=
=0A=
  1.  Just ignore it and send the next one.=0A=
  2.  Put one packet time worth of all zeros in the queue.=0A=
=0A=
Now consider what happens with a dropped packet and a standing queue.=0A=
The first strategy creates a hidden timing slip.  The second strategy=0A=
avoids the timing slip.=0A=
=0A=
So my argument is that the egress buffer is in effect the jitter=0A=
buffer.  When jitter occurs a standing buffer forms that reflects the=0A=
lesser of the limit of the buffer size or the worst case jitter.=0A=
There is always a jitter buffer.  There always needs to be a jitter=0A=
buffer of at least one large packet time, otherwise high loss of data=0A=
will occur.  There should be a jitter buffer that can be made larger=0A=
so that jitter of multiple packet times doesn't turn in to loss.=0A=
=0A=
Therefore I assert that a jitter buffer is always present and is=0A=
always needed because jitter is always non-zero.  Therefore this=0A=
statement is true:=0A=
=0A=
   A small jitter buffer is always necessary and the jitter buffer is=0A=
   needed regardless of whether reordering is done.=0A=
=0A=
> In particular, these queues could not be used for re-ordering=0A=
> misordered PW packets.=0A=
=0A=
That does not mean that they can't be used to compensate for jitter=0A=
which is by definition what a jitter buffer is for.=0A=
=0A=
When reordering is done, the egress buffer is made small and a buffer=0A=
preceding that is used which has some ability to reorder packets.  In=0A=
hardware a circular queue makes sense with packets place according to=0A=
their sequence number.  If you prescribe to the "just insert zeros"=0A=
idea when a packet is dropped, then after moving a packet to the=0A=
egress queue, zero the buffer or mark it as unoccupied and more the=0A=
circular buffer a bit.  If the packet that is later supposed to occupy=0A=
that slot never arrives, then it is already zerod (or marked as=0A=
missing in which case a packet of all zeros is put on the egress=0A=
queue).=0A=
=0A=
So ... reording within a small jitter buffer is not hard to do.=0A=
=0A=
Reordering can be supported with a small jitter buffer but adding=0A=
reordering to a small buffer may be ineffective.  If reordering is due=0A=
to a path change, then the buffer of a small number of packet times=0A=
may yield no improvement.  To be effective in that situation, the=0A=
buffer may need to be larger.  OTOH if moving EF traffic from one=0A=
queue with no standing EF queue to another with no standing EF queue=0A=
and the path change is just moving to another wave on the WDM,=0A=
reordering with a small jitter buffer may help.=0A=
=0A=
> IMHO and FWIW this understanding matches RFC 3985 which mentions (in=0A=
> Section 5.2.1.1 "Frame Ordering") that reodering as the strategy for=0A=
> handling mis-ordered packets introduces additional delay (i.e.,=0A=
> requires a ddicated jitter buffer), while the alternative strategy of=0A=
> discarding mis-ordered packets does not introduce such additional=0A=
> delay.=0A=
=0A=
You quoted the framework and not a TDM document.  Nowhere in that text=0A=
is there mention of a jitter buffer because that text is not specific=0A=
to TDM.=0A=
=0A=
For packet traffic you have no idea if a prior packet is dropped or=0A=
will arrive out of order and so when a drop occurs packets have to be=0A=
held for a non-zero amount of time rather than transmitted as soon as=0A=
they arrive.  This applies to all cell or packet AC, such as FR, ATM,=0A=
Ethernet, etc.=0A=
=0A=
You might want to look at section 5.2.2.1.  Clock Recovery which does=0A=
apply to TDM.  It points to RFC3550 (RTP) which assumes a jitter=0A=
buffer is always needed.=0A=
=0A=
> The editorial issue is about the entire sentence that contains the=0A=
> above-mentioned fragment, i.e., "A small jitter buffer is always=0A=
> necessary and the jitter buffer is needed regardless of whether=0A=
> reordering is done" - to me this looks like an unnecessary repetition=0A=
> if if it were techically correct.=0A=
=0A=
The second part of the sentence was to emphasis that the need for a=0A=
jitter buffer is not contingent on implementation or reordering.=0A=
Perhaps it would be more clear if the two points were separated.  How=0A=
about this=0A=
=0A=
 OLD new sentence=0A=
=0A=
   A small jitter buffer is always necessary and the jitter buffer=0A=
   is needed regardless of whether reordering is done.=0A=
=0A=
 NEW new sentence=0A=
=0A=
   A small jitter buffer is always necessary.  A jitter buffer is=0A=
   needed regardless of whether reordering is done.=0A=
=0A=
> Hence I would like to suggest discrading the problematic sentence as=0A=
> the simplest way to resolve both issues.=0A=
=0A=
I think the sentence provides an important clarification.  I think the=0A=
need to have this discussion proves that the clarification is needed.=0A=
=0A=
If we can agree on keeping this, I can submit the updated draft.=0A=
=0A=
> Hopefully these notes will e helpful.=0A=
>=0A=
> Regards,=0A=
>      Sasha=0A=
=0A=
Thanks again for the review and good comments.=0A=
=0A=
Regards,=0A=
=0A=
Curtis=0A=
=0A=
=0A=
> ________________________________________=0A=
> From: Curtis Villamizar <curtis@occnc.com>=0A=
> Sent: Tuesday, December 10, 2013 5:47 PM=0A=
> To: Alexander Vainshtein=0A=
> Cc: curtis@ipv6.occnc.com; curtis@occnc.com; kireeti@juniper.net; samante=
@apple.com; agmalis@gmail.com; cpignata@cisco.com; mpls@ietf.org; Yaakov St=
ein (yaakov_s@rad.com); pwe3 (pwe3@ietf.org)=0A=
> Subject: Re: [PWE3] Pseudowire Sequence Number in draft-ietf-mpls-forward=
ing: a minor comment=0A=
>=0A=
> In message <F9336571731ADE42A5397FC831CEAA025AC56C9D@ILPTWPVEXMB02.ecitel=
e.com>=0A=
> Alexander Vainshtein writes:=0A=
> >=0A=
> > Curtis,=0A=
> >=0A=
> > Lots of thanks for a prompt and very detailed response.=0A=
> > May I suggest an alternative version of the following text fragment?=0A=
> >=0A=
> > <Curtis>=0A=
> > >   Identifying the position of any lost packets is important=0A=
> > >    for PW services which are attempting to reconstruct a bit stream=
=0A=
> > >    which maintains bit timing, such as time division multiplexing (TD=
M)=0A=
> > >    services.  TDM and other PW services which require strict ordering=
=0A=
> > >    also require that misordered packets be either dropped or reordere=
d.=0A=
>=0A=
> Invalid XML - you didn't close this element.  :-)=0A=
>=0A=
> >  <Sasha>=0A=
> >=0A=
> >    Identifying lost PW packets and exact amount of lost payload is=0A=
> >    critical for PW services which maintain bit timing, such as Time=0A=
> >    Division Multiplexing (TDM) services since these services MUST=0A=
> >    compensate lost payload on a bit-for-bit basis.=0A=
> >=0A=
> >    With these services PW packets that have been received out of order=
=0A=
> >    also MUST also be identified and may be either re-ordered or=0A=
> >    dropped.  Reordering requires, in addition to sequence numbering, a=
=0A=
> >    "de-jitter buffer" in the egress PE, and ability to reorder is=0A=
> >    limited by the depth of this buffer. The down side of maintaining a=
=0A=
> >    de-jitter buffer is added end-to-end service delay.=0A=
> >=0A=
> >   </Sasha>=0A=
>=0A=
> Accepted with a small change.=0A=
>=0A=
> After the words "down side"=0A=
> s/de-jitter buffer/large jitter buffer/=0A=
> Elsewhere=0A=
> s/de-jitter buffer/jitter buffer/g=0A=
> Then add the sentence.=0A=
>=0A=
>    A small jitter buffer is always necessary and the jitter buffer=0A=
>    is needed regardless of whether reordering is done.=0A=
>=0A=
> This yields a slightly changed second paragraph.=0A=
>=0A=
>    With these services PW packets that have been received out of order=0A=
>    also MUST also be identified and may be either re-ordered or=0A=
>    dropped.  Reordering requires, in addition to sequence numbering, a=0A=
>    "jitter buffer" in the egress PE, and ability to reorder is limited=0A=
>    by the depth of this buffer. The down side of maintaining a large=0A=
>    jitter buffer is added end-to-end service delay.  A small jitter=0A=
>    buffer is always necessary and the jitter buffer is needed=0A=
>    regardless of whether reordering is done.=0A=
>=0A=
> Is this wording OK with you?=0A=
>=0A=
> Curtis=0A=
>=0A=
> > Hopefully this will be useful.=0A=
> >=0A=
> >=0A=
> > Regards,=0A=
> >      Sasha=0A=
> >=0A=
> > > -----Original Message-----=0A=
> > > From: Curtis Villamizar [mailto:curtis@ipv6.occnc.com]=0A=
> > > Sent: Monday, November 25, 2013 8:30 PM=0A=
> > > To: Alexander Vainshtein=0A=
> > > Cc: curtis@occnc.com; kireeti@juniper.net; samante@apple.com;=0A=
> > > agmalis@gmail.com; cpignata@cisco.com; mpls@ietf.org; Yaakov Stein=0A=
> > > (yaakov_s@rad.com); pwe3 (pwe3@ietf.org)=0A=
> > > Subject: Re: [PWE3] Pseudowire Sequence Number in draft-ietf-mpls-=0A=
> > > forwarding: a minor comment=0A=
> > >=0A=
> > >=0A=
> > > In message=0A=
> > > <F9336571731ADE42A5397FC831CEAA025392F92F@ILPTWPVEXMB01.ecitele.c=0A=
> > > om>=0A=
> > > Alexander Vainshtein writes:=0A=
> > > >=0A=
> > > > Hi all,=0A=
> > > >=0A=
> > > > I would like to comment on the text in Section 2.1.8.1 "Pseudowire=
=0A=
> > > > Sequence Number" in draft-ietf-mpls-forwarding-03 - MPLS Forwarding=
=0A=
> > > > Compliance and Performance Requirements=0A=
> > > > <http://tools.ietf.org/html/draft-ietf-mpls-forwarding-03>.=0A=
> > > >=0A=
> > > > This section states, in short, that the main drive for using the=0A=
> > > > sequence number in the PW Control Word is handling of packet=0A=
> > > > reordering events. TDM PWs are presented as a major example, with C=
BR=0A=
> > > > ATM services as another example.=0A=
> > > >=0A=
> > > > In fact, this statement is not accurate.=0A=
> > >=0A=
> > > Yes.  You are correct in pointing this out as inaccurate by omitting=
=0A=
> > > the other important function of identifying drops for the purpose of=
=0A=
> > > recunstructing TDM bit streams.=0A=
> > >=0A=
> > > Andy brought up resequencing being a strong provider request.=0A=
> > > Reordering is far more common than loss particularly for high priorit=
y=0A=
> > > services on provider networks and without resequencing reorder result=
s=0A=
> > > in PW loss in what could otherwise be lossless service.=0A=
> > >=0A=
> > > So we should get the base requirements right but still reflect this,=
=0A=
> > > but strictly as advice with no normative wording.  We had used the=0A=
> > > phrase "is beneficial" and will retain that.=0A=
> > >=0A=
> > > Andy brought up the topic.  The incorrect wording in the existing=0A=
> > > draft is my fault.  This text went in fairly early with a lot of othe=
r=0A=
> > > changes and it appears that no one had since given it a careful enoug=
h=0A=
> > > read and review until you came along.=0A=
> > >=0A=
> > > > The main drive for mandating the use of sequence number in TM PWs i=
s=0A=
> > > > the need to detect and count lost packets because the egress PE MUS=
T=0A=
> > > > compensate the lost payload bit for bit.=0A=
> > > >=0A=
> > > > Ability to compensate reordering of PW packets at egress is a side=
=0A=
> > > > effect of (a) sequence number usage and (b) usage of the de-jitter=
=0A=
> > > > buffer in the egress PW. It is not mandatory and in any case is=0A=
> > > > limited by the depth of the de-jitter buffer: re-ordered packets th=
at=0A=
> > > > cannot be accommodated within this buffer are treated as lost.=0A=
> > > >=0A=
> > > > Additional details can be found, e.g., in section 6.2.2 of RFC=0A=
> > > > 4553<http://tools.ietf.org/html/rfc4553>. Ability to re-order=0A=
> > > > mis-ordered PW packets is defined there as OPTIONAL, while replacem=
ent=0A=
> > > > of the payload of lost PW packets is defined as MANDATORY.=0A=
> > >=0A=
> > > The change below at the top of the section more accurately reflects=
=0A=
> > > requirements in the RFCs but still states that resequencing can be=0A=
> > > beneficial.  The comments about EPD and PPD are dropped and therefore=
=0A=
> > > also the informative reference.=0A=
> > >=0A=
> > >  Context:=0A=
> > >=0A=
> > >  2.1.8.1.  Pseudowire Sequence Number=0A=
> > >=0A=
> > >  OLD=0A=
> > >=0A=
> > >    Pseudowire (PW) sequence number support is most important for PW=
=0A=
> > >    payload types with a high expectation of in-order delivery.=0A=
> > >    Resequencing support, rather than dropping at egress on out of ord=
er=0A=
> > >    arrival, is most important for PW payload types with a high=0A=
> > >    expectation of lossless delivery.  For example, TDM payloads requi=
re=0A=
> > >    sequence number support and require resequencing support.  The sam=
e=0A=
> > >    is true of ATM CBR service.  ATM VBR or ABR may have somewhat rela=
xed=0A=
> > >    requirements, but generally require ATM Early Packet Discard (EPD)=
 or=0A=
> > >    ATM Partial Packet Discard (PPD) [ATM-EPD-and-PPD].  Though sequen=
ce=0A=
> > >    number support and resequencing support are beneficial to PW packe=
t=0A=
> > >    oriented payloads such as FR and Ethernet, they are highly desirab=
le=0A=
> > >    but not as strongly required.=0A=
> > >=0A=
> > > NEW=0A=
> > >=0A=
> > >    Pseudowire (PW) sequence number support is most important for PW=
=0A=
> > >    payload types with a high expectation of lossless and/or in-order=
=0A=
> > >    delivery.  Identifying the position of any lost packets is importa=
nt=0A=
> > >    for PW services which are attempting to reconstruct a bit stream=
=0A=
> > >    which maintains bit timing, such as time division multiplexing (TD=
M)=0A=
> > >    services.  TDM and other PW services which require strict ordering=
=0A=
> > >    also require that misordered packets be either dropped or reordere=
d.=0A=
> > >=0A=
> > >    PW services which are not timing critical bit streams in nature ar=
e=0A=
> > >    cell oriented or frame oriented.  Though resequencing support is=
=0A=
> > >    beneficial to PW cell and frame oriented payloads such as ATM, FR =
and=0A=
> > >    Ethernet, they are highly desirable but not required.=0A=
> > >=0A=
> > > NEW (end of subsection after list of possible reording causes)=0A=
> > >=0A=
> > >    In provider networks which use multipath techniques and which may=
=0A=
> > >    occassionally rebalance traffic or which may change PW paths=0A=
> > >    occasionally for other reasons, reordering may be far more common=
=0A=
> > >    than loss.  Where reordering is more common than loss, resequencin=
g=0A=
> > >    packets is beneficial, rather than dropping packets at egress when=
=0A=
> > >    out of order arrival occus.  Resequencing is most important for PW=
=0A=
> > >    payload types with a high expectation of lossless delivery since i=
n=0A=
> > >    such cases out of order delivery within the network results in PW=
=0A=
> > >    loss.=0A=
> > >=0A=
> > > The final paragraph sums up the motivation for highlighting=0A=
> > > resequencing as beneficial and desirable.  It does so without any=0A=
> > > normative wording.=0A=
> > >=0A=
> > > > Hopefully these notes will be useful.=0A=
> > > >=0A=
> > > > Regards,=0A=
> > > >      Sasha=0A=
> > >=0A=
> > > These notes are very useful.  Thank you.=0A=
> > >=0A=
> > > Please let us know if you (and the WG) are OK with the rewording=0A=
> > > proposed above.=0A=
> > >=0A=
> > > Curtis=0A=
=0A=

From jiangyuanlong@huawei.com  Mon Dec 16 18:37:20 2013
Return-Path: <jiangyuanlong@huawei.com>
X-Original-To: pwe3@ietfa.amsl.com
Delivered-To: pwe3@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 96C471AE03F for <pwe3@ietfa.amsl.com>; Mon, 16 Dec 2013 18:37:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.225
X-Spam-Level: 
X-Spam-Status: No, score=-3.225 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.538, SPF_PASS=-0.001, URIBL_RHS_DOB=1.514] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UIgHYzuYg_9b for <pwe3@ietfa.amsl.com>; Mon, 16 Dec 2013 18:37:18 -0800 (PST)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id A6E6B1AE036 for <pwe3@ietf.org>; Mon, 16 Dec 2013 18:37:17 -0800 (PST)
Received: from 172.18.7.190 (EHLO lhreml204-edg.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BBM70609; Tue, 17 Dec 2013 02:37:16 +0000 (GMT)
Received: from LHREML406-HUB.china.huawei.com (10.201.5.243) by lhreml204-edg.china.huawei.com (172.18.7.223) with Microsoft SMTP Server (TLS) id 14.3.158.1; Tue, 17 Dec 2013 02:36:48 +0000
Received: from SZXEMA409-HUB.china.huawei.com (10.82.72.41) by lhreml406-hub.china.huawei.com (10.201.5.243) with Microsoft SMTP Server (TLS) id 14.3.158.1; Tue, 17 Dec 2013 02:37:13 +0000
Received: from SZXEMA506-MBS.china.huawei.com ([169.254.4.204]) by SZXEMA409-HUB.china.huawei.com ([10.82.72.41]) with mapi id 14.03.0158.001; Tue, 17 Dec 2013 10:37:03 +0800
From: Jiangyuanlong <jiangyuanlong@huawei.com>
To: "Andrew G. Malis" <agmalis@gmail.com>, "pwe3@ietf.org" <pwe3@ietf.org>
Thread-Topic: [PWE3] Poll for WG adoption and IPR check of draft-zhang-pwe3-iccp-stp-00
Thread-Index: AQHO8TLnonycndk/7EulJgNPa9JppZpXvpvg
Date: Tue, 17 Dec 2013 02:37:03 +0000
Message-ID: <3B0A1BED22CAD649A1B3E97BE5DDD68B5A6CCA8D@szxema506-mbs.china.huawei.com>
References: <CAA=duU1X6SWzxNOVdXJHA4TsxnVf6u4jGO=0MaoYkc-661XWDw@mail.gmail.com>
In-Reply-To: <CAA=duU1X6SWzxNOVdXJHA4TsxnVf6u4jGO=0MaoYkc-661XWDw@mail.gmail.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.66.76.118]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Subject: Re: [PWE3] Poll for WG adoption and IPR check of	draft-zhang-pwe3-iccp-stp-00
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Pseudowire Emulation Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 17 Dec 2013 02:37:20 -0000

Support adoption.

Regards,
Yuanlong


-----Original Message-----
From: pwe3 [mailto:pwe3-bounces@ietf.org] On Behalf Of Andrew G. Malis
Sent: Thursday, December 05, 2013 4:53 AM
To: pwe3@ietf.org
Subject: [PWE3] Poll for WG adoption and IPR check of draft-zhang-pwe3-iccp=
-stp-00

This email begins a two week poll to help the chairs determine if
there is consensus to adopt draft-zhang-pwe3-iccp-stp-00 as an PWE3
working group draft.

The draft can be found here:
http://tools.ietf.org/html/draft-zhang-pwe3-iccp-stp-00

Please read the draft and indicate to the list if you support
adoption, or if you do not support adoption (giving reasons).

Please note that this is only a call for adoption. There needs to be
consensus that this draft is a good basis for the work, but it does
not need to be perfect at this stage.

Coincidentally, we are also polling for knowledge of any IPR that
applies to this draft, to ensure that IPR has been disclosed in
compliance with IETF IPR rules (see RFCs 3979, 4879, 3669 and 5378 for
more details).

If you are listed as a document author or contributor please respond
to this email whether or not you are aware of any relevant IPR. The
draft will not be adopted until a response has been received from each
author and contributor.

If you are on the PWE3 WG email list but are not listed as an author
or contributor, then please explicitly respond regarding IPR only if
you are aware of any IPR that has not yet been disclosed in
conformance with IETF rules.

The poll for adoption will close in two weeks time, on Wednesday 18th Decem=
ber.

Best regards,
Andy
_______________________________________________
pwe3 mailing list
pwe3@ietf.org
https://www.ietf.org/mailman/listinfo/pwe3

From agmalis@gmail.com  Thu Dec 19 09:04:52 2013
Return-Path: <agmalis@gmail.com>
X-Original-To: pwe3@ietfa.amsl.com
Delivered-To: pwe3@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7A4031AE0A3 for <pwe3@ietfa.amsl.com>; Thu, 19 Dec 2013 09:04:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wNrZoJ4f7vUX for <pwe3@ietfa.amsl.com>; Thu, 19 Dec 2013 09:04:51 -0800 (PST)
Received: from mail-qc0-x22e.google.com (mail-qc0-x22e.google.com [IPv6:2607:f8b0:400d:c01::22e]) by ietfa.amsl.com (Postfix) with ESMTP id F3B6A1AE092 for <pwe3@ietf.org>; Thu, 19 Dec 2013 09:04:50 -0800 (PST)
Received: by mail-qc0-f174.google.com with SMTP id n7so1136797qcx.5 for <pwe3@ietf.org>; Thu, 19 Dec 2013 09:04:49 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; bh=Pl6Uysi5IZkSVFloArmTh0ZiY1h6Xn9f6yGWzz7/bNs=; b=boCy492aEQPfHXW1y8Cx4TegIza6OdHfZreWUFEsRqP/Tw/sfdlMDkcCcifYJfRyeA iuaiQUV6B6pQ/dPRak8Q9UTrBOuoxws/8PpTawbfDALAxZIZDXdJEjTnTW1RWyq/76VP KTri/jIqcXepIr0mYu9QNcEPnvqQNqFr6NiP7iyNxSGYy2BqcE27eAWClq9hKXdjIlb0 4m8X/5+SiaOZtdn0QGPO/Hpfk4bCMz0EaOHlqls/R7G/9UsbJ6S4Z2RMFbnN2nYQUdpq efubb+UR2qHumSniT1MOhhVURh9g0FrvSyreogKVNpb9o84p8nNvy7q8bEV8rStAqdOD whyQ==
X-Received: by 10.49.41.104 with SMTP id e8mr4893113qel.1.1387472688938; Thu, 19 Dec 2013 09:04:48 -0800 (PST)
MIME-Version: 1.0
Received: by 10.229.166.9 with HTTP; Thu, 19 Dec 2013 09:04:28 -0800 (PST)
In-Reply-To: <CAA=duU1X6SWzxNOVdXJHA4TsxnVf6u4jGO=0MaoYkc-661XWDw@mail.gmail.com>
References: <CAA=duU1X6SWzxNOVdXJHA4TsxnVf6u4jGO=0MaoYkc-661XWDw@mail.gmail.com>
From: "Andrew G. Malis" <agmalis@gmail.com>
Date: Thu, 19 Dec 2013 12:04:28 -0500
Message-ID: <CAA=duU3eBAc8OAdc0TBh0-4SCg3U+MG0Kr5-P67J_Z3N_VCzAw@mail.gmail.com>
To: "pwe3@ietf.org" <pwe3@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1
Subject: Re: [PWE3] Poll for WG adoption and IPR check of draft-zhang-pwe3-iccp-stp-00
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Pseudowire Emulation Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 19 Dec 2013 17:04:52 -0000

This ends the adoption poll for draft-zhang-pwe3-iccp-stp-00. There
was a good discussion, and resulting changes to be included in an
update of the draft in order to reflect rough consensus. The authors
are going to produce draft-zhang-pwe3-iccp-stp-01 to incorporate the
discussion, and following that they will just change the name to then
produce draft-ietf-pwe3-iccp-stp-00.

Cheers,
Andy

On Wed, Dec 4, 2013 at 3:53 PM, Andrew G. Malis <agmalis@gmail.com> wrote:
> This email begins a two week poll to help the chairs determine if
> there is consensus to adopt draft-zhang-pwe3-iccp-stp-00 as an PWE3
> working group draft.
>
> The draft can be found here:
> http://tools.ietf.org/html/draft-zhang-pwe3-iccp-stp-00
>
> Please read the draft and indicate to the list if you support
> adoption, or if you do not support adoption (giving reasons).
>
> Please note that this is only a call for adoption. There needs to be
> consensus that this draft is a good basis for the work, but it does
> not need to be perfect at this stage.
>
> Coincidentally, we are also polling for knowledge of any IPR that
> applies to this draft, to ensure that IPR has been disclosed in
> compliance with IETF IPR rules (see RFCs 3979, 4879, 3669 and 5378 for
> more details).
>
> If you are listed as a document author or contributor please respond
> to this email whether or not you are aware of any relevant IPR. The
> draft will not be adopted until a response has been received from each
> author and contributor.
>
> If you are on the PWE3 WG email list but are not listed as an author
> or contributor, then please explicitly respond regarding IPR only if
> you are aware of any IPR that has not yet been disclosed in
> conformance with IETF rules.
>
> The poll for adoption will close in two weeks time, on Wednesday 18th December.
>
> Best regards,
> Andy

From internet-drafts@ietf.org  Sun Dec 22 21:42:01 2013
Return-Path: <internet-drafts@ietf.org>
X-Original-To: pwe3@ietfa.amsl.com
Delivered-To: pwe3@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 898021AED4F; Sun, 22 Dec 2013 21:42:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id x0j-2cmf-f0Y; Sun, 22 Dec 2013 21:42:00 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 60ACC1AE183; Sun, 22 Dec 2013 21:42:00 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 4.90
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20131223054200.6350.44958.idtracker@ietfa.amsl.com>
Date: Sun, 22 Dec 2013 21:42:00 -0800
Cc: pwe3@ietf.org
Subject: [PWE3] I-D Action: draft-ietf-pwe3-mpls-tp-cv-adv-03.txt
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.15
List-Id: Pseudowire Emulation Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 23 Dec 2013 05:42:01 -0000

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

        Title           : VCCV MPLS-TP Connectivity Verification (CV) Capab=
ility Advertisement
        Author          : Greg Mirsky
	Filename        : draft-ietf-pwe3-mpls-tp-cv-adv-03.txt
	Pages           : 7
	Date            : 2013-12-22

Abstract:
   This document specifies how use of proactive Connectivity
   Verification (CV), Continuity Check (CC), and Remote Defect
   Indication (RDI) for the MPLS Transport Profile (MPLS-TP) affects
   operation and management function election for Pseudowire (PW)
   Virtual Circuit Connectivity Verification (VCCV).


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-pwe3-mpls-tp-cv-adv/

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-pwe3-mpls-tp-cv-adv-03

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-pwe3-mpls-tp-cv-adv-03


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

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


From agmalis@gmail.com  Mon Dec 23 12:03:11 2013
Return-Path: <agmalis@gmail.com>
X-Original-To: pwe3@ietfa.amsl.com
Delivered-To: pwe3@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6E87F1AE2AC for <pwe3@ietfa.amsl.com>; Mon, 23 Dec 2013 12:03:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FbLOJYMg17fC for <pwe3@ietfa.amsl.com>; Mon, 23 Dec 2013 12:03:10 -0800 (PST)
Received: from mail-qe0-x22b.google.com (mail-qe0-x22b.google.com [IPv6:2607:f8b0:400d:c02::22b]) by ietfa.amsl.com (Postfix) with ESMTP id 28A3C1AE2AB for <pwe3@ietf.org>; Mon, 23 Dec 2013 12:03:10 -0800 (PST)
Received: by mail-qe0-f43.google.com with SMTP id jy17so5564344qeb.2 for <pwe3@ietf.org>; Mon, 23 Dec 2013 12:03:06 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:from:date:message-id:subject:to:cc:content-type; bh=C8P9LexNIageXjkjMhX+NB3/aYTWqT3Kj4b2qcduvJE=; b=MWeixWGEeso6b4SJIcF02DzV9l4hKafAcKqj5ZUA8qUa4ydlk0TehTgHsFhIkRo2NA NLheGRPKGhweUeqjT+HgUBxPsJ9jVCmY8xzUNE9f3AJvjkeowxXFBViZXDzZd0ZWnGWr shntOP35gLApANaLzAxtWmNV2y1tH9KJ2ca5JAv4/4fZDTdlnj7uQuLuMRD7q3BgQYkb E14DxRjCt+BOIvmqgdMIP63PnA/06USvj+/evNmEbNlBtaqa4yqUvPVmI5KU8PQMUE0r T90orEX9IInxrSw6Y22g2Du2Ht0BRyiF4HPD+EZd7Wikxzf9umLkKrMhKYvSt8h1AYoO 8Yew==
X-Received: by 10.49.41.104 with SMTP id e8mr46241572qel.1.1387828986589; Mon, 23 Dec 2013 12:03:06 -0800 (PST)
MIME-Version: 1.0
Received: by 10.229.166.9 with HTTP; Mon, 23 Dec 2013 12:02:46 -0800 (PST)
From: "Andrew G. Malis" <agmalis@gmail.com>
Date: Mon, 23 Dec 2013 15:02:46 -0500
Message-ID: <CAA=duU1UKajWNPj=DT1_AJw0=ad9d6sJh+p=_VTfBenvOuu_yA@mail.gmail.com>
To: "pwe3@ietf.org" <pwe3@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1
Cc: draft-ietf-pwe3-p2mp-pw-requirements@tools.ietf.org
Subject: [PWE3] IPR issue with draft-ietf-pwe3-p2mp-pw-requirements-06
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Pseudowire Emulation Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 23 Dec 2013 20:03:11 -0000

I would like to make the WG aware of a potential IPR issue with
draft-ietf-pwe3-p2mp-pw-requirements-06, which I've been getting ready
for submission to the IESG. On Nov. 13, 2013, ORANGE filed an IPR
disclosure, https://datatracker.ietf.org/ipr/2249/ . The IPR concerns
multipoint to point PWs, which are are one of two optional return
paths discussed in draft-ietf-pwe3-p2mp-pw-requirements-06.
Point-to-point PWs are the other optional return path discussed in the
draft.

Given that this IPR was disclosed late in the process, before
submitting this draft to the IESG, I would like to get a sense of the
WG as to whether it is OK to submit the draft as is, or if the WG
would prefer that the optional MP2P return path be removed from the
draft.

As this is over the holidays, and many people are on vacation, I won't
take any action on the draft until at least the second week of
January.

Thanks,
Andy

From internet-drafts@ietf.org  Tue Dec 24 05:08:44 2013
Return-Path: <internet-drafts@ietf.org>
X-Original-To: pwe3@ietfa.amsl.com
Delivered-To: pwe3@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 91FEA1ADF5C; Tue, 24 Dec 2013 05:08:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dNylalnv_6Hv; Tue, 24 Dec 2013 05:08:43 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 36ECA1ADF4D; Tue, 24 Dec 2013 05:08:43 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 4.90
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20131224130842.1022.233.idtracker@ietfa.amsl.com>
Date: Tue, 24 Dec 2013 05:08:42 -0800
Cc: pwe3@ietf.org
Subject: [PWE3] I-D Action: draft-ietf-pwe3-iccp-stp-00.txt
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.15
List-Id: Pseudowire Emulation Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 24 Dec 2013 13:08:45 -0000

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

        Title           : STP Application of ICCP
        Authors         : Mingui Zhang
                          Huafeng Wen
                          Jie Hu
	Filename        : draft-ietf-pwe3-iccp-stp-00.txt
	Pages           : 19
	Date            : 2013-12-23

Abstract:
   Inter-Chassis Communication Protocol (ICCP) supports the inter-
   chassis redundancy mechanism which achieves high network
   availability.

   In this document, the PEs in a Redundant Group (RG) running ICCP are
   used to offer multi-homed connectivity to Spanning Tree Protocol
   (STP) networks. The ICCP TLVs for the STP application are defined,
   therefore PEs from the RG can make use of these TLVs to synchronize
   the state and configuration data of the STP network.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-pwe3-iccp-stp/

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-pwe3-iccp-stp-00


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

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


From iesg-secretary@ietf.org  Tue Dec 24 08:45:39 2013
Return-Path: <iesg-secretary@ietf.org>
X-Original-To: pwe3@ietfa.amsl.com
Delivered-To: pwe3@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BA6561ADFFD; Tue, 24 Dec 2013 08:45:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id V0hYfJX_JE_P; Tue, 24 Dec 2013 08:45:38 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 953621ADF7F; Tue, 24 Dec 2013 08:45:38 -0800 (PST)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 4.90
Auto-Submitted: auto-generated
Precedence: bulk
Sender: <iesg-secretary@ietf.org>
Message-ID: <20131224164538.14798.40166.idtracker@ietfa.amsl.com>
Date: Tue, 24 Dec 2013 08:45:38 -0800
Cc: pwe3@ietf.org
Subject: [PWE3] Last Call: <draft-ietf-pwe3-mpls-tp-cv-adv-03.txt> (VCCV MPLS-TP Connectivity Verification (CV) Capability Advertisement) to Proposed Standard
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.15
Reply-To: ietf@ietf.org
List-Id: Pseudowire Emulation Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 24 Dec 2013 16:45:40 -0000

The IESG has received a request from the Pseudowire Emulation Edge to
Edge WG (pwe3) to consider the following document:
- 'VCCV MPLS-TP Connectivity Verification (CV) Capability Advertisement'
  <draft-ietf-pwe3-mpls-tp-cv-adv-03.txt> as 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 2014-01-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.

Abstract


   This document specifies how use of proactive Connectivity
   Verification (CV), Continuity Check (CC), and Remote Defect
   Indication (RDI) for the MPLS Transport Profile (MPLS-TP) affects
   operation and management function election for Pseudowire (PW)
   Virtual Circuit Connectivity Verification (VCCV).




The file can be obtained via
http://datatracker.ietf.org/doc/draft-ietf-pwe3-mpls-tp-cv-adv/

IESG discussion can be tracked via
http://datatracker.ietf.org/doc/draft-ietf-pwe3-mpls-tp-cv-adv/ballot/


No IPR declarations have been submitted directly on this I-D.



From agmalis@gmail.com  Tue Dec 31 14:40:53 2013
Return-Path: <agmalis@gmail.com>
X-Original-To: pwe3@ietfa.amsl.com
Delivered-To: pwe3@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 03F001AE3B1 for <pwe3@ietfa.amsl.com>; Tue, 31 Dec 2013 14:40:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BiEqKdjBKnJK for <pwe3@ietfa.amsl.com>; Tue, 31 Dec 2013 14:40:51 -0800 (PST)
Received: from mail-qc0-x22c.google.com (mail-qc0-x22c.google.com [IPv6:2607:f8b0:400d:c01::22c]) by ietfa.amsl.com (Postfix) with ESMTP id 21AE31AE372 for <pwe3@ietf.org>; Tue, 31 Dec 2013 14:40:51 -0800 (PST)
Received: by mail-qc0-f172.google.com with SMTP id e16so12434670qcx.3 for <pwe3@ietf.org>; Tue, 31 Dec 2013 14:40:44 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; bh=Sly40U8G43GG8OtaHG4G/UOfFxkKcynhKhXz22SQYEM=; b=iXbbpyFjl0EWT3wmHUpDyq9rQ66mH0muaB7qQc10vN7l3oRk2ot08IZ9urkAAGnTT+ 9uyxUIGCnG1/Fh86WjnuDifYRZT5JdBZDFXcAWuZUQ75feDWI40890QYvZoHEfblyrfj +S7BJRMm2fYciyXeVKW5fHCaBMNPfh1BMxf2WKVeJ1mTOH7MvTYgQLp86mg7ll93BeCa 6k3C03py+Qljx9Arrx9Roqu7FHP/z5KyqgaCGcUEvns5jYovr2kiY5/8mlK8JiNgcTwP X+8P47ITyOM8BvYQwfkrWMm47BBTXOK+x0xckuabVr69PGofgQVZeTzl9ads6ZHZJxj7 Tmhw==
X-Received: by 10.49.41.104 with SMTP id e8mr126850619qel.1.1388529644631; Tue, 31 Dec 2013 14:40:44 -0800 (PST)
MIME-Version: 1.0
Received: by 10.229.166.9 with HTTP; Tue, 31 Dec 2013 14:40:24 -0800 (PST)
In-Reply-To: <CAF4+nEFGZUqTMdqqfQKJq_Br_JxZjaNrp5QQkdAPvU6axG+c8w@mail.gmail.com>
References: <20131231152543.26111.20972.idtracker@ietfa.amsl.com> <CAF4+nEFGZUqTMdqqfQKJq_Br_JxZjaNrp5QQkdAPvU6axG+c8w@mail.gmail.com>
From: "Andrew G. Malis" <agmalis@gmail.com>
Date: Tue, 31 Dec 2013 17:40:24 -0500
Message-ID: <CAA=duU3M9oyPUckZ0uFdKf+LS5q21ZKsttMVGqFGzvod83cWNg@mail.gmail.com>
To: "pwe3@ietf.org" <pwe3@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1
Subject: [PWE3] Fwd: [trill] I-D Action: draft-ietf-trill-o-pw-04.txt
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Pseudowire Emulation Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 31 Dec 2013 22:40:53 -0000

---------- Forwarded message ----------
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Tue, Dec 31, 2013 at 3:15 PM
Subject: Re: [trill] I-D Action: draft-ietf-trill-o-pw-04.txt
To: internet-drafts@ietf.org
Cc: "trill@ietf.org" <trill@ietf.org>, i-d-announce@ietf.org


This version has minor changes resolving SECDIR and GENART comments
and a comment by AD Barry Leiba.

Thanks,
Donald
=============================
 Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
 155 Beaver Street, Milford, MA 01757 USA
 d3e3e3@gmail.com


On Tue, Dec 31, 2013 at 10:25 AM,  <internet-drafts@ietf.org> wrote:
>
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
>  This draft is a work item of the Transparent Interconnection of Lots of Links Working Group of the IETF.
>
>         Title           : Transport of TRILL Using Pseudowires
>         Authors         : Lucy Yong
>                           Donald E. Eastlake
>                           Sam Aldrin
>                           Jon Hudson
>         Filename        : draft-ietf-trill-o-pw-04.txt
>         Pages           : 14
>         Date            : 2013-12-31
>
> Abstract:
>    This document specifies how to interconnect a pair of TRILL
>    (Transparent Interconnection of Lots of Links) switch ports using
>    pseudowires under existing TRILL and PWE3 (Pseudowire Emulation End-
>    to-End) standards.
>
>
>
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-trill-o-pw/
>
> There's also a htmlized version available at:
> http://tools.ietf.org/html/draft-ietf-trill-o-pw-04
>
> A diff from the previous version is available at:
> http://www.ietf.org/rfcdiff?url2=draft-ietf-trill-o-pw-04
>
>
> Please note that it may take a couple of minutes from the time of submission
> until the htmlized version and diff are available at tools.ietf.org.
>
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>
> _______________________________________________
> trill mailing list
> trill@ietf.org
> https://www.ietf.org/mailman/listinfo/trill
_______________________________________________
trill mailing list
trill@ietf.org
https://www.ietf.org/mailman/listinfo/trill
