IETF Logo Mail Archive

Re: [i2rs] Stephen Farrell's No Objection on draft-ietf-i2rs-traceability-10: (with COMMENT)

Joe Clarke <jclarke@cisco.com> Sun, 15 May 2016 14:13 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 C8E0112D1A1; Sun, 15 May 2016 07:13:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.947
X-Spam-Level:
X-Spam-Status: No, score=-15.947 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.426, 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 TmFmiP4K1lLK; Sun, 15 May 2016 07:13:44 -0700 (PDT)
Received: from alln-iport-1.cisco.com (alln-iport-1.cisco.com [173.37.142.88]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9BAC712D18F; Sun, 15 May 2016 07:13:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=975; q=dns/txt; s=iport; t=1463321624; x=1464531224; h=subject:to:references:cc:from:message-id:date: mime-version:in-reply-to:content-transfer-encoding; bh=5Ji7gWEi8RXFzUHylrKGkKCm6IlgsIWnVuhbHME9Lbs=; b=LsR8t63XATDCUT/zWnKv7gyiDlpRO6rQlmJCwRL04/Z0z2M24qBLJWJi 68ZMkM0ehp6m4UV9JdDyUkP63/aFVpU1wgh9PHhTNJ9YNYmweaEeQybZB ERdEXxdWCdgW65zG9zxMCCcZZT9RXJ5/ZCVJANTA12yF0WgWua7tlQs26 8=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0DtBQDZgzhX/5tdJa1dgzeBALgogh2BdoYRAoEWORMBAQEBAQEBZSeEQwEBBCMPAQVBEAsYAgImAgJXBgEMCAEBiCurSZBMAQEBAQEBAQEBAQEBAQEBAQEBH4EBhSSBdoJXhz+CWQEEh36QKY4eiT+FWo9BIgE/gjeBUSCIOAEBAQ
X-IronPort-AV: E=Sophos;i="5.24,623,1454976000"; d="scan'208";a="273870627"
Received: from rcdn-core-4.cisco.com ([173.37.93.155]) by alln-iport-1.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 15 May 2016 14:13:40 +0000
Received: from [10.118.87.83] (rtp-jclarke-nitro2.cisco.com [10.118.87.83]) by rcdn-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id u4FEDe2D008652; Sun, 15 May 2016 14:13:40 GMT
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>, The IESG <iesg@ietf.org>
References: <20160515133925.14660.72669.idtracker@ietfa.amsl.com>
From: Joe Clarke <jclarke@cisco.com>
Organization: Cisco Systems, Inc.
Message-ID: <72fa2731-b940-b4d2-bc92-f20efbb67318@cisco.com>
Date: Sun, 15 May 2016 10:13:34 -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: <20160515133925.14660.72669.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/i2rs/niGILTHTmSH_v3tSmCykzkOrCSw>
Cc: i2rs@ietf.org, draft-ietf-i2rs-traceability@ietf.org, i2rs-chairs@ietf.org, shares@ndzh.com
Subject: Re: [i2rs] Stephen Farrell's No Objection on draft-ietf-i2rs-traceability-10: (with COMMENT)
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: Sun, 15 May 2016 14:13:46 -0000

On 5/15/16 09:39, Stephen Farrell wrote:
> ----------------------------------------------------------------------
> COMMENT:
> ----------------------------------------------------------------------
>
>
> Thanks for handling my discuss point. The comments below
> are old and I didn't check if you'd done anything about them
> in -10 but that's fine either way unless you want to chat more
> about 'em.
>
> --------- OLD COMMENTS
>
> - 5.2: Requested/Applied Operation Data - I would guess
> this can include sensitive values, e.g. keys/passwords.
> Shouldn’t you say to at least be careful of those, or
> perhaps to not log them, or to zero out known sensitive
> values before logging?
>
> - 7.2: how is privacy an implementation detail?
>
> - 7.4: What does "being preferred" mean in 2119 terms? Why
> is one of the three options not mandatory-to-implement?
>
>

All of these should now be addressed in -10.  Thanks again for the review.

Joe

v2.23.0 | Report a Bug | By Email