Re: [Gen-art] Gen-art telechat review of draft-ietf-i2rs-traceability-09

Joe Clarke <> Wed, 11 May 2016 15:18 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 0652B12DB40; Wed, 11 May 2016 08:18:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -15.517
X-Spam-Status: No, score=-15.517 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=-0.996, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id 5X_ea-CPSvoI; Wed, 11 May 2016 08:18:10 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 776A212D0E3; Wed, 11 May 2016 08:18:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple;;; l=1783; q=dns/txt; s=iport; t=1462979890; x=1464189490; h=subject:to:references:cc:from:message-id:date: mime-version:in-reply-to:content-transfer-encoding; bh=qyIrKCFGvf1lH21gzqkn0G2ar2TLZq4Zr3+a1ImIdiU=; b=ff1ec5f6IX7KxV8N6RwUkOldPuvV1u9hVDC7rw28+2BwV28fslIR5N2w 2KsZQW6Eezy3+FGFbz0NGLdIWVpPRFQMSdkxb1Dc9Xfxgd4U1OUTfuSaO WkspkQTqbpG4RuteS1toWbvOF/r0STww/hYP3wAggcWBlwFiyXDiAIeLZ A=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-AV: E=Sophos;i="5.24,608,1454976000"; d="scan'208";a="103217126"
Received: from ([]) by with ESMTP/TLS/DHE-RSA-AES256-SHA; 11 May 2016 15:18:09 +0000
Received: from [] ( []) by (8.14.5/8.14.5) with ESMTP id u4BFI9dp029477; Wed, 11 May 2016 15:18:09 GMT
To: Elwyn Davies <>, General area reviewing team <>
References: <> <> <>
From: Joe Clarke <>
Organization: Cisco Systems, Inc.
Message-ID: <>
Date: Wed, 11 May 2016 11:18:08 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.0
MIME-Version: 1.0
In-Reply-To: <>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <>
Subject: Re: [Gen-art] Gen-art telechat review of draft-ietf-i2rs-traceability-09
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Wed, 11 May 2016 15:18:13 -0000

On 5/10/16 17:51, Elwyn Davies wrote:
> s1, para 2: s/describes use cases/describe use cases/


> s5.2, Event ID:
>> An event can be a Client authenticating with the Agent, a Client to
>> Agent operation, or a Client disconnecting from an Agent.
> This is a good thing, but I am not sure that the format provides a way
> to identify the authentication and disconnection events.

The intent was that these would be Operations (i.e., AUTHENTICATE 
CLIENT, DISCONNECT CLIENT).  There is nothing in the text that precludes 
this.  We can explicitly state this.

> s5.2, Starting Timestamp:
> [I don't understand 'three points of prevision'.] Maybe...
> OLD:
> Given that many I2RS operations can occur in rapid succession, the use
> of fractional seconds MUST be used to provide adequate granularity.
> Fractional seconds SHOULD be expressed with at least three points of
> prevision in second.microsecond format.
> NEW:
> Given that many I2RS operations can occur in rapid succession, the
> fractional seconds element of the timestamp MUST be used to provide
> adequate granularity.  Fractional seconds SHOULD be expressed with at
> least three [or more?] significant digits in second.microsecond format.


> s5.2, Ending Timestamp:
> See the comments on the Starting Timestamp - though I think you could
> just refer to the words in the Starting Timestamp and avoid duplication.


> s7.4/s7.4.3: Given that the I2RS pub-sub access method is
> mandatory-to-implement, i think I-D.ietf-i2rs-pub-sub-requirements has
> to be a Normative Reference.


See the new text at 

Thanks again for the review!