[i2rs] Alissa Cooper's No Objection on draft-ietf-i2rs-rib-data-model-10: (with COMMENT)
Alissa Cooper <alissa@cooperw.in> Tue, 03 April 2018 15:09 UTC
Return-Path: <alissa@cooperw.in>
X-Original-To: i2rs@ietf.org
Delivered-To: i2rs@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 2245F120724; Tue, 3 Apr 2018 08:09:56 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Alissa Cooper <alissa@cooperw.in>
To: The IESG <iesg@ietf.org>
Cc: draft-ietf-i2rs-rib-data-model@ietf.org, Susan Hares <shares@ndzh.com>, i2rs-chairs@ietf.org, shares@ndzh.com, i2rs@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.77.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <152276819613.22739.3895944015063617381.idtracker@ietfa.amsl.com>
Date: Tue, 03 Apr 2018 08:09:56 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/i2rs/sQ7dm2FfUslrshD8bzM7CCSO3PU>
Subject: [i2rs] Alissa Cooper's No Objection on draft-ietf-i2rs-rib-data-model-10: (with COMMENT)
X-BeenThere: i2rs@ietf.org
X-Mailman-Version: 2.1.22
List-Id: "Interface to The Internet Routing System \(IRS\)" <i2rs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/i2rs>, <mailto:i2rs-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/i2rs/>
List-Post: <mailto:i2rs@ietf.org>
List-Help: <mailto:i2rs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/i2rs>, <mailto:i2rs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 03 Apr 2018 15:09:56 -0000
Alissa Cooper has entered the following ballot position for draft-ietf-i2rs-rib-data-model-10: 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-i2rs-rib-data-model/ ---------------------------------------------------------------------- COMMENT: ---------------------------------------------------------------------- Sec 1.2: "YANG tree diagrams provide a concise representation of a YANG module, and SHOULD be included to help readers understand YANG module structure." This document does not seem like an appropriate place to have normative guidance about this. And if this sentence is removed, I don't see the point of including Section 1.2 otherwise. This would also imply deleting the reference to I-D.ietf-netmod-yang-tree-diagrams. Sec 2.1: Again here I'm confused about the use of normative language. Why do you need to specify normative requirements for what this very document is specifying? Or are these supposed to be requirements on implementations? Sec 2.5: s/causes/caused/
- [i2rs] Alissa Cooper's No Objection on draft-ietf… Alissa Cooper
- Re: [i2rs] Alissa Cooper's No Objection on draft-… Mach Chen
- Re: [i2rs] Alissa Cooper's No Objection on draft-… t.petch
- Re: [i2rs] Alissa Cooper's No Objection on draft-… Mach Chen
- Re: [i2rs] Alissa Cooper's No Objection on draft-… Alissa Cooper
- Re: [i2rs] Alissa Cooper's No Objection on draft-… t.petch
- Re: [i2rs] Alissa Cooper's No Objection on draft-… Susan Hares
- Re: [i2rs] Alissa Cooper's No Objection on draft-… Mach Chen
- Re: [i2rs] Alissa Cooper's No Objection on draft-… Benoit Claise
- Re: [i2rs] Alissa Cooper's No Objection on draft-… Mach Chen