[Teas] Ben Campbell's No Objection on draft-ietf-teas-rsvp-te-scaling-rec-07: (with COMMENT)

Ben Campbell <ben@nostrum.com> Thu, 28 September 2017 01:17 UTC

Return-Path: <ben@nostrum.com>
X-Original-To: teas@ietf.org
Delivered-To: teas@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id A00C7135211; Wed, 27 Sep 2017 18:17:37 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Ben Campbell <ben@nostrum.com>
To: The IESG <iesg@ietf.org>
Cc: draft-ietf-teas-rsvp-te-scaling-rec@ietf.org, Lou Berger <lberger@labn.net>, teas-chairs@ietf.org, lberger@labn.net, teas@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.62.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <150656145760.13808.17318350937488343363.idtracker@ietfa.amsl.com>
Date: Wed, 27 Sep 2017 18:17:37 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/teas/bri1fS27OBhjoXBry_heEcOSb3A>
Subject: [Teas] Ben Campbell's No Objection on draft-ietf-teas-rsvp-te-scaling-rec-07: (with COMMENT)
X-BeenThere: teas@ietf.org
X-Mailman-Version: 2.1.22
List-Id: Traffic Engineering Architecture and Signaling working group discussion list <teas.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/teas>, <mailto:teas-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/teas/>
List-Post: <mailto:teas@ietf.org>
List-Help: <mailto:teas-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/teas>, <mailto:teas-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Sep 2017 01:17:38 -0000

Ben Campbell has entered the following ballot position for
draft-ietf-teas-rsvp-te-scaling-rec-07: 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-teas-rsvp-te-scaling-rec/



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

[Note: The authors revised this draft between the time I reviewed it and
transcribed my notes. This is a review of version 06. I will not have time to
re-review 07 prior to the telechat to see if my comments still apply.]

Substantive:

- General: I agree with the "major issues" comments from Elwyn's Gen-ART review.

- General: There's a fair amount of 2119 language in this draft that refers to
options in prior RFCs. It's not clear which of those are new normative
requirements vs restatements of existing requirements. In the former case, this
draft would need to update those respective RFCs. In the latter case, this
draft should use descriptive language rather than 2119 keywords (unless in the
form of direct quotes.)

-1, last paragraph: "In order to reap maximum scaling benefits, it is
   strongly RECOMMENDED that implementations support both the
   techniques."

That statement seems to require updating ... something. Maybe 3209 or 2961?

-2.1.3, 2nd paragraph: Does this update RFC 2961?  Or if not, is the normative
language appropriate here?

-2.2, bullet list: Are these new normative requirements or restatements of
existing ones?

-6: "This document does not introduce new security issues."
Please document the reasoning behind that statement.

Editorial:

-2.1, section title: Why the quotes?

-2.2, first bullet: Section 1 already normatively states these. This text
effectively says "MUST follow the MUSTs...". (Note that this pattern recurs in
several places.)

-2.3, first paragraph: "The set of recommendations discussed in this section..."
As written, many of those are requirements rather than recommendations.