[i2rs] Alvaro Retana's No Objection on draft-ietf-i2rs-rib-info-model-15: (with COMMENT)

Alvaro Retana <aretana.ietf@gmail.com> Tue, 03 April 2018 07:14 UTC

Return-Path: <aretana.ietf@gmail.com>
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 067C91201FA; Tue, 3 Apr 2018 00:14:10 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Alvaro Retana <aretana.ietf@gmail.com>
To: The IESG <iesg@ietf.org>
Cc: draft-ietf-i2rs-rib-info-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: <152273965001.13971.7531466101349529801.idtracker@ietfa.amsl.com>
Date: Tue, 03 Apr 2018 00:14:10 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/i2rs/4kPzqRHTBqx67GxWMLbzTeQDicg>
Subject: [i2rs] Alvaro Retana's No Objection on draft-ietf-i2rs-rib-info-model-15: (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 07:14:10 -0000

Alvaro Retana has entered the following ballot position for
draft-ietf-i2rs-rib-info-model-15: 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-info-model/



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

(1) Even if just Informative, it would be nice to have a reference to
draft-ietf-i2rs-rib-data-model.

(2) I think that the use of some Normative Language is not as expected.

(2.1) For example, in S2.1 (RIB definition): "There MAY be many routing
instances and each routing instance MAY contain RIBs."  In both cases "MAY"
seems to be a statement of fact, and not a normative statement to indicate that
a routing instance can optionally include RIBs.  Note that S2.2 (Routing
instance) identifies a rib-list as a mandatory component of a routing instance,
and there's no clear indication that the list may be empty.

(2.2) S2.1: "A routing instance MAY even have two or more RIBs of the same rib
family (e.g., IPv6)."  This use of "MAY" also seems to be stating a fact.

(2.3) "MAY be optionally", "MAY contain the following optional fields" are
redundant phrases as MAY already means optional.