[Pce] Alvaro Retana's No Objection on draft-ietf-pce-iro-update-06: (with COMMENT)

"Alvaro Retana" <aretana@cisco.com> Mon, 18 April 2016 16:03 UTC

Return-Path: <aretana@cisco.com>
X-Original-To: pce@ietf.org
Delivered-To: pce@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 5BE4312D93F; Mon, 18 Apr 2016 09:03:23 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: "Alvaro Retana" <aretana@cisco.com>
To: "The IESG" <iesg@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.19.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20160418160323.9332.67077.idtracker@ietfa.amsl.com>
Date: Mon, 18 Apr 2016 09:03:23 -0700
Archived-At: <http://mailarchive.ietf.org/arch/msg/pce/HRXYy-N8cDHcrwjcYMbv_MaJQxk>
Cc: draft-ietf-pce-iro-update@ietf.org, pce@ietf.org, pce-chairs@ietf.org
Subject: [Pce] Alvaro Retana's No Objection on draft-ietf-pce-iro-update-06: (with COMMENT)
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.17
List-Id: Path Computation Element <pce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pce>, <mailto:pce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pce/>
List-Post: <mailto:pce@ietf.org>
List-Help: <mailto:pce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 18 Apr 2016 16:03:23 -0000

Alvaro Retana has entered the following ballot position for
draft-ietf-pce-iro-update-06: 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-pce-iro-update/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

1. WG Consensus

The Abstract talks about this document resulting from an "informal
survey".  The Shepherd writeup also mentions the survey and how it was
"not unanimous".  However, while the survey itself is mentioned in the
document (10 times in 6 pages!), there is no reference, and more
importantly nothing is mentioned about WG consensus.

What I'm getting to here is the following:  regardless of what the survey
says (or not), this document is on the Standards Track so I expect the
update to be the result of WG consensus.  If the survey is not even
referenced (which is fine with me), then the document should forget about
it and simply point at the updates.  In other words, the survey, like
discussion on the mailing list, seems to have been used as a tool to
reach consensus — no need to repeatedly mention the tool.

I don't think this point raises to the level of a DISCUSS because it
should be an editorial change.  Even though the archives don't provide
much in terms of discussion around this document (or
draft-dhody-pce-iro-survey), I have to assume that it reached this point
because there is in fact consensus on the update.


2. Non conforming implementations

Section 3. (Other Considerations).  Given that other interpretations of
rfc5440 were possible, I think that the considerations in this section
are operational, so renaming may be a good idea.  I would expect that
because this is a Standards Track document that people will eventually
conform to it, so I think that the "RECOMMEND" at the bottom is not
needed.  [I think that's the only rfc2119 key word.]


3. Section 2.1. (Update to RFC 5440): 

a. Where should the new statements be added?  I'm assuming after the
first paragraph.

B. "An abstract node could be a simple abstract node…"  Is there a better
way to define "abstract node" than by using it in the definition?  Maybe
just point to rfc3209.