Re: [IPFIX] Gen-ART Telechat Review of draft-ietf-ipfix-data-link-layer-monitoring-07

Paul Aitken <paitken@cisco.com> Thu, 21 November 2013 14:21 UTC

Return-Path: <paitken@cisco.com>
X-Original-To: ipfix@ietfa.amsl.com
Delivered-To: ipfix@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 289BD1AE172; Thu, 21 Nov 2013 06:21:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.026
X-Spam-Level:
X-Spam-Status: No, score=-10.026 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.525, SPF_PASS=-0.001, 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 lRVPwN7VfdfP; Thu, 21 Nov 2013 06:21:39 -0800 (PST)
Received: from aer-iport-2.cisco.com (aer-iport-2.cisco.com [173.38.203.52]) by ietfa.amsl.com (Postfix) with ESMTP id CD8CF1AE180; Thu, 21 Nov 2013 06:21:38 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1800; q=dns/txt; s=iport; t=1385043692; x=1386253292; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=l3Kvaa+KXS9JbrrSiWjv7xXkcBVrdWDkeO2CyFYKGRU=; b=j51geSeu0i180rByu5JaPvICr4QFZ7ePebKNnDx66VeBO3GV2+HNP9Pg UPnIWQPHXsYMWnjPnLC3haWPAWkRJHt5Tp5BUUekshd5K7xXJJuepzD+c UTzLONvx9MLsTxGxd6NCSN37t4VzoALdfz2tcA04rPIbDna668VRv6+5t 0=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhkFAKoVjlKQ/khM/2dsb2JhbABZgwc4vVKBIhZ0giUBAQEEOEABEAsUBAkWDwkDAgECAUUGAQwBBwEBF4dmDcEMF40WglUHhDIDmBKBMIUSi06DKA
X-IronPort-AV: E=Sophos;i="4.93,744,1378857600"; d="scan'208";a="371162"
Received: from ams-core-3.cisco.com ([144.254.72.76]) by aer-iport-2.cisco.com with ESMTP; 21 Nov 2013 14:21:31 +0000
Received: from cisco.com (mrwint.cisco.com [64.103.70.36]) by ams-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id rALELP3M001189 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 21 Nov 2013 14:21:27 GMT
Received: from [10.61.102.55] (dhcp-10-61-102-55.cisco.com [10.61.102.55]) by cisco.com (8.14.4+Sun/8.8.8) with ESMTP id rALELNNu018400; Thu, 21 Nov 2013 14:21:24 GMT
Message-ID: <528E16DE.7090704@cisco.com>
Date: Thu, 21 Nov 2013 14:21:18 +0000
From: Paul Aitken <paitken@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:24.0) Gecko/20100101 Thunderbird/24.1.1
MIME-Version: 1.0
To: Ben Campbell <ben@nostrum.com>, draft-ietf-ipfix-data-link-layer-monitoring.all@tools.ietf.org, ipfix@ietf.org
References: <9F0317F4-CAC5-49C7-89C8-199FA2B78DF0@nostrum.com>
In-Reply-To: <9F0317F4-CAC5-49C7-89C8-199FA2B78DF0@nostrum.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: "gen-art@ietf.org Team (gen-art@ietf.org)" <gen-art@ietf.org>
Subject: Re: [IPFIX] Gen-ART Telechat Review of draft-ietf-ipfix-data-link-layer-monitoring-07
X-BeenThere: ipfix@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IPFIX WG discussion list <ipfix.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipfix>, <mailto:ipfix-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipfix/>
List-Post: <mailto:ipfix@ietf.org>
List-Help: <mailto:ipfix-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipfix>, <mailto:ipfix-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Nov 2013 14:21:41 -0000

Thanks Ben, we'll move 2804 to an informative reference.

P.



On 19/11/2013 21:17, Ben Campbell wrote:
> I am the assigned Gen-ART reviewer for this draft. For background on
> Gen-ART, please see the FAQ at
> < http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>
> Please wait for direction from your document shepherd
> or AD before posting a new version of the draft.
>
> Document: draft-ietf-ipfix-data-link-layer-monitoring-07
> Reviewer: Ben Campbell
> Review Date: 2013-11-19
> IESG Telechat date: 2013-11-21
>
> Summary: This draft is essentially ready for publication as a standards track RFC. However, there is one issue that I unfortunately missed in my last call review of version 06 that should be considered prior to publication.
>
> Major issues:
>
> None
>
> Minor issues:
>
> There's a normative downref to RFC 2804, which is informational. That seems a really odd draft for a normative reference. There may be precedent, as I note that RFC 5477, referenced here for security considerations, does the same thing.  I apologize for bringing this up this late in the process--I missed it in my earlier review at last call.
>
> As I understand it the context is that certain data elements can include payload octets. This is subject to the security considerations in 5477, which basically say don't include too much, because of guidance from 2804. But my reading of 2804 does not give specific guidance things like how much payload one can capture before it becomes too much.
>
> I think the simplest solution would be to keep the reference to the 5477 security considerations, and reiterate that this model is not intended for gross capture of payloads, perhaps with an _informative_ reference to 2804.
>
> Nits/editorial comments:
>
> None