[GROW] Alissa Cooper's No Objection on draft-ietf-grow-wkc-behavior-06: (with COMMENT)
Alissa Cooper via Datatracker <noreply@ietf.org> Mon, 10 June 2019 19:28 UTC
Return-Path: <noreply@ietf.org>
X-Original-To: grow@ietf.org
Delivered-To: grow@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 459F9120048; Mon, 10 Jun 2019 12:28:22 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Alissa Cooper via Datatracker <noreply@ietf.org>
To: The IESG <iesg@ietf.org>
Cc: draft-ietf-grow-wkc-behavior@ietf.org, Job Snijders <job@ntt.net>, grow-chairs@ietf.org, job@ntt.net, grow@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.97.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Alissa Cooper <alissa@cooperw.in>
Message-ID: <156019490227.14511.5752126140840043791.idtracker@ietfa.amsl.com>
Date: Mon, 10 Jun 2019 12:28:22 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/grow/YF17DkeT1sunZogAQ3YneK_WuuI>
Subject: [GROW] Alissa Cooper's No Objection on draft-ietf-grow-wkc-behavior-06: (with COMMENT)
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/grow/>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 10 Jun 2019 19:28:22 -0000
Alissa Cooper has entered the following ballot position for draft-ietf-grow-wkc-behavior-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-grow-wkc-behavior/ ---------------------------------------------------------------------- COMMENT: ---------------------------------------------------------------------- Requirements language: Please use the RFC 8174 boilerplate. Section 4.1: s/is not really on IANA's list/is not individually named on IANA's list/ Section 5: I'm not sure what the '>' character indicates. Section 6: "Vendors SHOULD clearly document the behavior of "set" directive in their implementations." I'm not sure normative language makes sense here (otherwise, what is the rationale for not using MUST?).
- [GROW] Alissa Cooper's No Objection on draft-ietf… Alissa Cooper via Datatracker
- Re: [GROW] Alissa Cooper's No Objection on draft-… Randy Bush