Re: [i2rs] WG Adoption call for draft-clarke-i2rs-traceability-03 from 11/24 to 12/9/14

Joe Clarke <jclarke@cisco.com> Sat, 29 November 2014 17:36 UTC

Return-Path: <jclarke@cisco.com>
X-Original-To: i2rs@ietfa.amsl.com
Delivered-To: i2rs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DC5831A0169 for <i2rs@ietfa.amsl.com>; Sat, 29 Nov 2014 09:36:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.511
X-Spam-Level:
X-Spam-Status: No, score=-14.511 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, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
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 UOG2dyL1KL2q for <i2rs@ietfa.amsl.com>; Sat, 29 Nov 2014 09:36:17 -0800 (PST)
Received: from rcdn-iport-4.cisco.com (rcdn-iport-4.cisco.com [173.37.86.75]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 37DAE1A00A2 for <i2rs@ietf.org>; Sat, 29 Nov 2014 09:36:17 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2234; q=dns/txt; s=iport; t=1417282578; x=1418492178; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=VnLdV+C1cljZPGLtXC6h5v2vlrX4TPJ6hc/23q4pyTg=; b=gJfkw6jkLNYofIbZcsPWa9+XMjKlg6ZoB9Jy4XiHNBI5jucRmW1kMRu6 0ctA1LB+UpvZQ3HIQk44y3i2EMKr9R/FKufwKjzUw/h0Fe5w+ISFc0OU+ Wppbqyvy67TbgINmdCFn7JDRCx6+n/ZaPJwgkUrlYxo5lF0WeL44wWcrH k=;
X-IronPort-AV: E=Sophos;i="5.07,484,1413244800"; d="scan'208";a="376279813"
Received: from rcdn-core-1.cisco.com ([173.37.93.152]) by rcdn-iport-4.cisco.com with ESMTP; 29 Nov 2014 17:36:17 +0000
Received: from [10.117.46.164] (rtp-jclarke-8913.cisco.com [10.117.46.164]) by rcdn-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id sATHaGjW019864; Sat, 29 Nov 2014 17:36:16 GMT
Message-ID: <547A040F.2030202@cisco.com>
Date: Sat, 29 Nov 2014 12:36:15 -0500
From: Joe Clarke <jclarke@cisco.com>
Organization: Cisco Systems, Inc.
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:31.0) Gecko/20100101 Thunderbird/31.2.0
MIME-Version: 1.0
To: "Nobo Akiya (nobo)" <nobo@cisco.com>, Susan Hares <shares@ndzh.com>, "i2rs@ietf.org" <i2rs@ietf.org>
References: <003701d0086d$2984f060$7c8ed120$@ndzh.com> <CECE764681BE964CBE1DFF78F3CDD3943F5A7920@xmb-aln-x01.cisco.com>
In-Reply-To: <CECE764681BE964CBE1DFF78F3CDD3943F5A7920@xmb-aln-x01.cisco.com>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: http://mailarchive.ietf.org/arch/msg/i2rs/JIj7j-QkV30TlkhUtQhQj_vb0yM
Cc: 'Jeffrey Haas' <jhaas@pfrc.org>, 'Alia Atlas' <akatlas@gmail.com>
Subject: Re: [i2rs] WG Adoption call for draft-clarke-i2rs-traceability-03 from 11/24 to 12/9/14
X-BeenThere: i2rs@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Sat, 29 Nov 2014 17:36:19 -0000

On 11/28/14 8:24 PM, Nobo Akiya (nobo) wrote:
> Hi Sue, Jeff,
>
> The document describes a good framework which enables trace-ability of
> the interactions amongst I2RS modules, and provides data points for
> record/debugging purposes. I believe this framework provides a good
> value, thus I support the adoption of this document as a WG document.
>
> I do have one question/comment to the authors but not a blocker for its
> WG adoption.
>
> The Log Entity describe one Timestamp. What does this Timestamp describe?
>
> Realistically, I can see 4 possibilities.
>
> - Time when I2RS agent received the request from an I2RS client.
>
> - Time when I2RS agent made the request to the Routing System.
>
> - Time when I2RS agent received the reply from the Routing System.
>
> - Time when I2RS agent sent the reply to to the I2RS client.
>
> If one was attempting to make sense of a scaled number of requests being
> processed by the I2RS agent (and some processed in parallel), having
> more than one Timestamp in a Log Entry may provide more insights into
> what was happening in the system.

This is a very good observation, Nobo.  Initially, we meant for the 
timestamp to be the time at which the agent received the request from 
the client (since the request may not complete).  But we should have 
another timestamp populated upon completion so that one can gage 
performance as well.

This is the kind of feedback we want, and hopefully this will help drive 
the work forward as a working group item.  Thanks.

Joe

>
> Thanks!
>
> -Nobo
>
> *From:*i2rs [mailto:i2rs-bounces@ietf.org] *On Behalf Of *Susan Hares
> *Sent:* Tuesday, November 25, 2014 12:03 AM
> *To:* i2rs@ietf.org
> *Cc:* 'Jeffrey Haas'; 'Alia Atlas'
> *Subject:* [i2rs] WG Adoption call for draft-clarke-i2rs-traceability-03
> from 11/24 to 12/9/14
>
> This is to begin a 2 week adoption call for
> draft-clarke-i2rs-traceability-03.  Please include in your comments an
> indication of “support” or “no support.”
>
> Thank you,
>
> Sue Hares and Jeff Haas
>
>
>
> _______________________________________________
> i2rs mailing list
> i2rs@ietf.org
> https://www.ietf.org/mailman/listinfo/i2rs
>