[mpls] Warren Kumari's No Objection on draft-ietf-mpls-tp-shared-ring-protection-05: (with COMMENT)
Warren Kumari <warren@kumari.net> Mon, 22 May 2017 15:02 UTC
Return-Path: <warren@kumari.net>
X-Original-To: mpls@ietf.org
Delivered-To: mpls@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id ACE27120046; Mon, 22 May 2017 08:02:04 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Warren Kumari <warren@kumari.net>
To: The IESG <iesg@ietf.org>
Cc: draft-ietf-mpls-tp-shared-ring-protection@ietf.org, Eric Gray <Eric.Gray@Ericsson.com>, mpls-chairs@ietf.org, Eric.Gray@Ericsson.com, mpls@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.51.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <149546532470.14956.16147225784444997069.idtracker@ietfa.amsl.com>
Date: Mon, 22 May 2017 08:02:04 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/mpls/yHjTyTxygzmBBvwFdqNklvU2aXY>
Subject: [mpls] Warren Kumari's No Objection on draft-ietf-mpls-tp-shared-ring-protection-05: (with COMMENT)
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.22
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mpls/>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 May 2017 15:02:05 -0000
Warren Kumari has entered the following ballot position for draft-ietf-mpls-tp-shared-ring-protection-05: 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-mpls-tp-shared-ring-protection/ ---------------------------------------------------------------------- COMMENT: ---------------------------------------------------------------------- Some nits and a question: 3. MPLS-TP Ring Protection Criteria and Requirements a. The number of OAM entities... "Each ring-node requires only one instance of the RPS protocol. " --- not super important, but is this "Each ring-node requires only one instance of the RPS protocol (regardless of the number of rings)" or "Each ring-node requires only one instance of the RPS protocol per ring"? -- if a node participates in multiple rings, does it need an instance for each ring? (I suspect that this is somewhat of an implementation choice, but am not sure). 4. Shared Ring Protection Architecture 4.1. Ring Tunnel "... ring tunnels which provides a server layer for the LSPs traverse the ring." I think "for the LSP's traversing the ring." (or perhaps "which traverse the ring.")
- [mpls] Warren Kumari's No Objection on draft-ietf… Warren Kumari