Re: [i2rs] Alvaro Retana's No Objection on draft-ietf-i2rs-rib-info-model-15: (with COMMENT)
Nitin Bahadur <nitin_bahadur@yahoo.com> Sun, 22 April 2018 17:58 UTC
Return-Path: <nitin_bahadur@yahoo.com>
X-Original-To: i2rs@ietfa.amsl.com
Delivered-To: i2rs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A3FC21241FC for <i2rs@ietfa.amsl.com>; Sun, 22 Apr 2018 10:58:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=yahoo.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZJgv4mqKrz81 for <i2rs@ietfa.amsl.com>; Sun, 22 Apr 2018 10:57:57 -0700 (PDT)
Received: from sonic317-20.consmr.mail.gq1.yahoo.com (sonic317-20.consmr.mail.gq1.yahoo.com [98.137.66.146]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CCBAC126C0F for <i2rs@ietf.org>; Sun, 22 Apr 2018 10:57:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1524419877; bh=6ziUkG5EbQgX2gKNJuaH0ofdlKYuA1gkKOADS6BJK4Q=; h=Date:Subject:From:To:References:In-Reply-To:From:Subject; b=aleuVyepqR81G4rr/v+1Xl7bC317e5q4xPDV4GRZDe213/YYEDqRHV8eKUtxpztamMfgtGRWX9DSg9YRCG1tPFvDl0SmfKeZ3rQUi3Y9iMRXDZBzLDEq8yUqJVsvIIku4WS0MCUNkLdO5raifMRJJAmxILbVhTd7nmVryOjGMj8o68fcNlpsPBog6mee1xlIC4Y2H/+cfEZY2C+ROutCxDwHg2FyAod51MYMQ9kRygzjO3ic5Psxpqgfnu2J0uF6h8w3gcfSgPcpipT3NcrRex91YHAyPji9ShI2Ek8O4F9yU8sQ+b6nAnBIOHWx7mS/BjEjiX9s8yHGhvAuo5TMoA==
X-YMail-OSG: lpBaKN8VM1lYJju4iVipVB6qdecR1QKDB9gCHusdDetHfzO0OvNDtrwi_0j9zl4 fdy6m3lC7kDrqts_xAV7edJyvyTw7TVHZIBCLnVD4jeuHDvl4brDcjheCLqryhUKbU2I1Vc87iP7 gP_vw6_xdXOR6HxfwYK11lDGD2b.dWchWeasvLMj4JwciayQjrbu64T4d7XNj3p5FdACfvE7OJmD _oXrCK776XaOd6.7BMrUjgYbkTIqqBQZqQdWkf7Q_HuQLuHTXAEaisnJVbE4ZSMLRSxM7IjWKEkz XpY4oX2STwr2UQqch2qHw3ha7xE_ld9mukATyQXEEwNBmkumZtCUO2uhJAcQ4GL0f103gB0IyJoT yGuCndtIBWsKgLtanX5zPo5eRunUEwndwGWkE1TW95i_3tJtTHFklp4yY6rwh26N9W8YLysIGch7 K.P5oV13.H1pI54HSQyuh1lbZi.kdD8ZARwBswksT4bXooAz7Q4wPPsYDbjo5O4sUjNvJoV0yuSq oHrjOMne1V5TSfNEpifHcFY2UQ7ffjPcNLK1oGWV9nv5YA_KhgTtXFyTF2W0_XmmRRzUwEvl5cQb bGQ4CJv1M
Received: from sonic.gate.mail.ne1.yahoo.com by sonic317.consmr.mail.gq1.yahoo.com with HTTP; Sun, 22 Apr 2018 17:57:57 +0000
Received: from c-73-158-191-172.hsd1.ca.comcast.net (EHLO [192.168.0.109]) ([73.158.191.172]) by smtp401.mail.gq1.yahoo.com (Oath Hermes SMTP Server) with ESMTPA ID c0fee7a67cb76257dbcdb85b1e6c3f67; Sun, 22 Apr 2018 17:57:55 +0000 (UTC)
User-Agent: Microsoft-MacOutlook/10.9.0.180116
Date: Sun, 22 Apr 2018 10:57:54 -0700
From: Nitin Bahadur <nitin_bahadur@yahoo.com>
To: Susan Hares <shares@ndzh.com>, 'Alvaro Retana' <aretana.ietf@gmail.com>, 'The IESG' <iesg@ietf.org>
CC: i2rs@ietf.org, i2rs-chairs@ietf.org, draft-ietf-i2rs-rib-info-model@ietf.org
Message-ID: <AE503B49-9893-4A87-8D84-B05EF7EEC6A9@yahoo.com>
Thread-Topic: [i2rs] Alvaro Retana's No Objection on draft-ietf-i2rs-rib-info-model-15: (with COMMENT)
References: <152273965001.13971.7531466101349529801.idtracker@ietfa.amsl.com> <344B4088-7547-4479-8745-99DFBCD3A224@yahoo.com> <016301d3d341$0f4c4cf0$2de4e6d0$@ndzh.com>
In-Reply-To: <016301d3d341$0f4c4cf0$2de4e6d0$@ndzh.com>
Mime-version: 1.0
Content-type: text/plain; charset="UTF-8"
Content-transfer-encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/i2rs/V-yhJrqkw6xvSSXxb_OgDxIO0b4>
Subject: Re: [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
Precedence: list
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: Sun, 22 Apr 2018 17:58:01 -0000
>From a process perspective I disagree with this. Just because the 2 drafts will end up going to RFC-ed queue at the same time does not mean we should be adding circular references. But if that's what the IESG would like me to, I'd be happy to put in a sentence. Please provide me specifics of where I should add the sentence and what the sentence should look like. Thanks Nitin On 4/13/18, 9:04 AM, "Susan Hares" <shares@ndzh.com> wrote: Nitin: On #1) - These drafts will work through the process at the same time. There will be a "MISREF" - but it should be cleared. Originally we were concerned about this fact because we wanted to send the I2RS Info model earlier. However, due to the network management datastore model work in netmod/netconf - this work has been held up. Please put the reference in and spin it as -16.txt. Thanks! Sue Hares -----Original Message----- From: i2rs [mailto:i2rs-bounces@ietf.org] On Behalf Of Nitin Bahadur Sent: Friday, April 13, 2018 2:09 AM To: Alvaro Retana; The IESG Cc: i2rs@ietf.org; i2rs-chairs@ietf.org; Susan Hares; draft-ietf-i2rs-rib-info-model@ietf.org Subject: Re: [i2rs] Alvaro Retana's No Objection on draft-ietf-i2rs-rib-info-model-15: (with COMMENT) Hi Alvaro, Thanks for the review. Please see NB> below (1) Even if just Informative, it would be nice to have a reference to draft-ietf-i2rs-rib-data-model. NB> I'm not sure how referencing works. If I understand correctly, rib-info-model then can't be published until data-model is published...and then there is circular referencing. (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. NB> Rewording to " A network device MAY contain routing instances and each routing instance MAY contain 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. NB> Good point. I'll fix that. (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. NB> Yes it is a fact. So removed use of "MAY". (2.3) "MAY be optionally", "MAY contain the following optional fields" are redundant phrases as MAY already means optional. NB> Good point. Fixed. Thanks Nitin _______________________________________________ i2rs mailing list i2rs@ietf.org https://www.ietf.org/mailman/listinfo/i2rs
- [i2rs] Alvaro Retana's No Objection on draft-ietf… Alvaro Retana
- Re: [i2rs] Alvaro Retana's No Objection on draft-… Nitin Bahadur
- Re: [i2rs] Alvaro Retana's No Objection on draft-… Susan Hares
- Re: [i2rs] Alvaro Retana's No Objection on draft-… Nitin Bahadur