[mpls] Warren Kumari's No Objection on draft-ietf-mpls-app-aware-tldp-08: (with COMMENT)

Warren Kumari <warren@kumari.net> Wed, 21 June 2017 15:59 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 C8B6D12EBF2; Wed, 21 Jun 2017 08:59:03 -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-app-aware-tldp@ietf.org, mpls-chairs@ietf.org, loa@pi.nu, mpls@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.55.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <149806074381.15547.15809082916681136670.idtracker@ietfa.amsl.com>
Date: Wed, 21 Jun 2017 08:59:03 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/mpls/AHl9BAK5M1y5Dtskvzq5KeUqVX8>
Subject: [mpls] Warren Kumari's No Objection on draft-ietf-mpls-app-aware-tldp-08: (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: Wed, 21 Jun 2017 15:59:04 -0000

Warren Kumari has entered the following ballot position for
draft-ietf-mpls-app-aware-tldp-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:


1: Does this document really need 6 front page authors?

2: The shepherd writeup says: "We are aware of several intentions to implement
this secification. An implementation poll has been sent to the working group
and as further information is received, the write-up will be updated." -- was
any further info received?

3: The shepherd writeup also says: "There is one small issue that I'm currently
clearing with IANA." -- is this the value of the status code E bit? Or some
other issue?

1: There are are a number of unexpanded acronyms -- e.g: LSP is no "well known"
- https://www.rfc-editor.org/materials/abbrev.expansion.txt

2: Sec 1  Introduction
"LDP uses extended discovery mechanism to establish..." - "LDP uses *the*
extended discovery mechanism" (or discovery *mechanisms*)

3: Sec 1  Introduction
 "An LSR initiates extended discovery... " - "A LSR..." ("An Label Switch"
 wouldn't make much sense)

4: Sec 1  Introduction
"In addition, since the session is initiated and established after adjacency
formation, the responding LSR has no targeted applications information to
choose the targeted application" - "has no targeted applications information
available to choose which targeted application".

5: Sec 1  Introduction
"Also, targeted LDP application is mapped .." - "Also, the targeted LDP
application is mapped"

6: Sec 1.2 Terminology
"This document uses terminology discussed in [RFC7473] along with others
defined in this document." feels clumsy. How about: "In addition to the
terminology defined in [RFC7473], this document uses the following terms: "

7: Sec 2.1 Encoding
"An LSR MAY advertise that it is capable to negotiate a targeted LDP ..." - "An
LSR MAY advertise that it is capable of negotiating a targeted LDP ..."