Re: [Pals] Alissa Cooper's No Objection on draft-ietf-pals-mpls-tp-pw-over-bidir-lsp-08: (with COMMENT)

Mach Chen <mach.chen@huawei.com> Tue, 12 July 2016 09:08 UTC

Return-Path: <mach.chen@huawei.com>
X-Original-To: pals@ietfa.amsl.com
Delivered-To: pals@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8BA7512D767; Tue, 12 Jul 2016 02:08:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.508
X-Spam-Level:
X-Spam-Status: No, score=-5.508 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.287, SPF_PASS=-0.001] autolearn=ham autolearn_force=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 YRxzCuQQPRcr; Tue, 12 Jul 2016 02:08:14 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C8BD512D75F; Tue, 12 Jul 2016 02:08:12 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml706-cah.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id CNN80085; Tue, 12 Jul 2016 09:08:10 +0000 (GMT)
Received: from SZXEMA417-HUB.china.huawei.com (10.82.72.34) by lhreml706-cah.china.huawei.com (10.201.5.182) with Microsoft SMTP Server (TLS) id 14.3.235.1; Tue, 12 Jul 2016 10:08:09 +0100
Received: from SZXEMA510-MBX.china.huawei.com ([169.254.3.173]) by SZXEMA417-HUB.china.huawei.com ([10.82.72.34]) with mapi id 14.03.0235.001; Tue, 12 Jul 2016 17:08:05 +0800
From: Mach Chen <mach.chen@huawei.com>
To: Alissa Cooper <alissa@cooperw.in>, The IESG <iesg@ietf.org>
Thread-Topic: Alissa Cooper's No Objection on draft-ietf-pals-mpls-tp-pw-over-bidir-lsp-08: (with COMMENT)
Thread-Index: AQHR19VaMAgQRoRgjESCYuS8BYPEkaAUiV/Q
Date: Tue, 12 Jul 2016 09:08:05 +0000
Message-ID: <F73A3CB31E8BE34FA1BBE3C8F0CB2AE28D763AA2@SZXEMA510-MBX.china.huawei.com>
References: <20160706222540.26716.61318.idtracker@ietfa.amsl.com>
In-Reply-To: <20160706222540.26716.61318.idtracker@ietfa.amsl.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.135]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A090201.5784B37B.0022, ss=1, re=0.000, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0, ip=169.254.3.173, so=2013-06-18 04:22:30, dmn=2013-03-21 17:37:32
X-Mirapoint-Loop-Id: c2437ffb5bfc2365e21e216aa9583f96
Archived-At: <https://mailarchive.ietf.org/arch/msg/pals/i723kfHa5zddZkLKhVxl6pA9j2Q>
Cc: "stewart.bryant@gmail.com" <stewart.bryant@gmail.com>, "pals-chairs@ietf.org" <pals-chairs@ietf.org>, "draft-ietf-pals-mpls-tp-pw-over-bidir-lsp@ietf.org" <draft-ietf-pals-mpls-tp-pw-over-bidir-lsp@ietf.org>, "pals@ietf.org" <pals@ietf.org>
Subject: Re: [Pals] Alissa Cooper's No Objection on draft-ietf-pals-mpls-tp-pw-over-bidir-lsp-08: (with COMMENT)
X-BeenThere: pals@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "Pseudowire And LDP-enabled Services dicussion list." <pals.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pals>, <mailto:pals-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pals/>
List-Post: <mailto:pals@ietf.org>
List-Help: <mailto:pals-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pals>, <mailto:pals-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 12 Jul 2016 09:08:19 -0000

Hi Alissa,

Thanks for your comments!

Please see my reply inline...

> -----Original Message-----
> From: Alissa Cooper [mailto:alissa@cooperw.in]
> Sent: Thursday, July 07, 2016 6:26 AM
> To: The IESG
> Cc: draft-ietf-pals-mpls-tp-pw-over-bidir-lsp@ietf.org; Stewart Bryant;
> pals-chairs@ietf.org; stewart.bryant@gmail.com; pals@ietf.org
> Subject: Alissa Cooper's No Objection on
> draft-ietf-pals-mpls-tp-pw-over-bidir-lsp-08: (with COMMENT)
> 
> Alissa Cooper has entered the following ballot position for
> draft-ietf-pals-mpls-tp-pw-over-bidir-lsp-08: No Objection
> 
> When responding, please keep the subject line intact and reply to all email
> addresses included in the To and CC lines. (Feel free to cut this introductory
> paragraph, however.)
> 
> 
> Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
> for more information about IESG DISCUSS and COMMENT positions.
> 
> 
> The document, along with other ballot positions, can be found here:
> https://datatracker.ietf.org/doc/draft-ietf-pals-mpls-tp-pw-over-bidir-lsp/
> 
> 
> 
> ----------------------------------------------------------------------
> COMMENT:
> ----------------------------------------------------------------------
> 
> In Section 1:
> 
> "Further, the
>    operators may apply different protection mechanisms on different
>    parts of the network.  As such, for optimal traffic management,
>    traffic belonging to a particular user should traverse over the same
>    fiber.  That implies that both forwarding and reserve direction PWs
>    that belong to the same user flow need to be mapped to the same co-
>    routed bi-directional LSP or two LSPs with the same route."
> 
> I'm wondering if this is a bit over-stated, and if "protection mechanisms"
> means specifically MPLS protection or if it is really a euphemism for a wide class
> of things, some of which are in an individual user's interest, and some of which
> are not (e.g., traffic shaping, content filtering, etc.). I think these claims should
> be stated more neutrally, e.g., "operators may prefer to have a user's traffic
> traverse the same fiber" rather than talking about "optimal traffic
> management."
> And "protection" should either be defined, or a more descriptive term should
> be used.

How about this:

"Further, the operators may apply different protection mechanisms on different parts of the network (e.g., deploy 1:1 protection in one part and 1+1 protection in other parts). As such, operators may prefer to have a user's traffic traverse the same fiber."

Best regards,
Mach
>