[i2rs] Comments on draft-ietf-i2rs-ephemeral-state-21

Joe Clarke <jclarke@cisco.com> Mon, 31 October 2016 15:50 UTC

Return-Path: <jclarke@cisco.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 D7EE5129795 for <i2rs@ietfa.amsl.com>; Mon, 31 Oct 2016 08:50:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -16.018
X-Spam-Level:
X-Spam-Status: No, score=-16.018 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.497, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.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 VqrJFSXQDIg7 for <i2rs@ietfa.amsl.com>; Mon, 31 Oct 2016 08:50:59 -0700 (PDT)
Received: from rcdn-iport-6.cisco.com (rcdn-iport-6.cisco.com [173.37.86.77]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CC8631297E4 for <i2rs@ietf.org>; Mon, 31 Oct 2016 08:50:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2297; q=dns/txt; s=iport; t=1477929058; x=1479138658; h=to:from:subject:message-id:date:mime-version: content-transfer-encoding; bh=de+m7H+FdvcQoyl3FQdWs4i22xWPoyUXPZIJYQ0M8q8=; b=aCGMehYVDRDAbRLJUG66E8hqbWNwyqPDlYnv7rDmIBCUcMQP/8m6eWj7 thCdVYY6D6NVWwe35CZ0HOzxBno0eXq+hzEl6o5Bmi7TmEUhYO6gf1uoq 5bGmDOdfodsUZM73gIwbqEf9MZOVzfgvAUq4JG4mTI9jOln7xM3BofNhS 4=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0ApAgAQaBdY/5pdJa1cGgEBAQECAQEBA?= =?us-ascii?q?QgBAQEBgyoBAQEBAR9bJ44JqzyCB4guPxQBAgEBAQEBAQFiHQuFDBVuCAImAks?= =?us-ascii?q?UDQgBAYhQoFyPcYxcAQEIAiWBB4U2gX2KI4JcBZoYgT6OcoFuiAQjhW+REx42Y?= =?us-ascii?q?IUuIog9AQEB?=
X-IronPort-AV: E=Sophos;i="5.31,575,1473120000"; d="scan'208";a="165749791"
Received: from rcdn-core-3.cisco.com ([173.37.93.154]) by rcdn-iport-6.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 31 Oct 2016 15:50:58 +0000
Received: from [10.150.55.152] (dhcp-10-150-55-152.cisco.com [10.150.55.152]) by rcdn-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id u9VFovdf012582 for <i2rs@ietf.org>; Mon, 31 Oct 2016 15:50:58 GMT
To: "i2rs@ietf.org" <i2rs@ietf.org>
From: Joe Clarke <jclarke@cisco.com>
Organization: Cisco Systems, Inc.
Message-ID: <8a6cde88-3f3d-958f-e32a-7df701e843e5@cisco.com>
Date: Mon, 31 Oct 2016 11:50:57 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:45.0) Gecko/20100101 Thunderbird/45.4.0
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/i2rs/q40V8dKom6vFQlxoRUIhqY8wElk>
Subject: [i2rs] Comments on draft-ietf-i2rs-ephemeral-state-21
X-BeenThere: i2rs@ietf.org
X-Mailman-Version: 2.1.17
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: Mon, 31 Oct 2016 15:51:00 -0000

I have read through the latest -21 rev of 
draft-ietf-i2rs-ephemeral-state, and I'd like to raise some additional 
(mostly minor) comments:

Section 1:

OLD:

The I2RS Architecture
    document [RFC7921] abstractly documents a number of requirements for
    implementing the I2RS requirements

NEW:

The I2RS Architecture
    document [RFC7921] abstractly documents a number of requirements for
    implementing the I2RS.

===

You talk about YANG as a data modeling language and NETCONF/RESTCONF as 
protocols.  Good.  However, in section 1, you go on to say:

What does re-use of a protocol mean?  Re-use means that while YANG,
    NETCONF and RESTCONF are a good starting basis for the I2RS protocol

YANG is not a protocol.  This is a nit, but perhaps YANG can be dropped 
from this sentence since it speaks to _protocol_ re-use.  Either that, 
or say something like:

What does re-use mean in this case?  Re-use means that while YANG, 
NETCONF and RESTCONF are good starting points for defining the I2RS data 
model and protocol...

===

Section 2:

The requirements are technically distilled from RFC7921 AND RFC7920 now.

===

Section 2, bullet 1:

OLD:

The I2RS protocol SHOULD support an interface asynchronous
        programmatic interface interface with properties of described in
        section 5 of [RFC7920] (e.g. high throughput) with support for
        target information streams, filtered evens, and thresholded
        events (real-time events) sent by an I2RS agent to an I2RS Client
        (Key points from section 1.1 of [RFC7921]).

NEW:

The I2RS protocol SHOULD support an asynchronous
        programmatic interface interface with properties of described in
        section 5 of [RFC7920] (e.g. high throughput) with support for
        target information streams, filtered evens, and thresholded
        events (real-time events) sent by an I2RS agent to an I2RS Client
        (Key points from section 1.1 of [RFC7921]).

===

Do a pass through this doc to lowercase the 'c' in client.  You have a 
number of cases that read "I2RS Client" where we previously standardized 
on "I2RS client."

===

Section 7:

OLD:

MUST BE

NEW:

MUST be

(This has been called out by others.)

Joe