[Pals] Alissa Cooper's No Objection on draft-ietf-pals-mpls-tp-pw-over-bidir-lsp-08: (with COMMENT)
"Alissa Cooper" <alissa@cooperw.in> Wed, 06 July 2016 22:25 UTC
Return-Path: <alissa@cooperw.in>
X-Original-To: pals@ietf.org
Delivered-To: pals@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 64DCB12D0C3; Wed, 6 Jul 2016 15:25:40 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Alissa Cooper <alissa@cooperw.in>
To: The IESG <iesg@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.25.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20160706222540.26716.61318.idtracker@ietfa.amsl.com>
Date: Wed, 06 Jul 2016 15:25:40 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/pals/ZlCTcx3EFxfn2YRnIr1sWr8L-40>
Cc: stewart.bryant@gmail.com, pals-chairs@ietf.org, draft-ietf-pals-mpls-tp-pw-over-bidir-lsp@ietf.org, pals@ietf.org
Subject: [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
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: Wed, 06 Jul 2016 22:25:40 -0000
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.
- [Pals] Alissa Cooper's No Objection on draft-ietf… Alissa Cooper
- Re: [Pals] Alissa Cooper's No Objection on draft-… Mach Chen