Re: [secdir] SecDir review of draft-ietf-ipfix-structured-data-05

Benoit Claise <bclaise@cisco.com> Tue, 15 March 2011 09:21 UTC

Return-Path: <bclaise@cisco.com>
X-Original-To: secdir@core3.amsl.com
Delivered-To: secdir@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 828A63A6BDA; Tue, 15 Mar 2011 02:21:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.642
X-Spam-Level:
X-Spam-Status: No, score=-2.642 tagged_above=-999 required=5 tests=[AWL=-0.043, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kO7u6BOHWDSS; Tue, 15 Mar 2011 02:21:06 -0700 (PDT)
Received: from av-tac-bru.cisco.com (weird-brew.cisco.com [144.254.15.118]) by core3.amsl.com (Postfix) with ESMTP id D42773A6C11; Tue, 15 Mar 2011 02:21:05 -0700 (PDT)
X-TACSUNS: Virus Scanned
Received: from strange-brew.cisco.com (localhost.cisco.com [127.0.0.1]) by av-tac-bru.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id p2F8HwEk022511; Tue, 15 Mar 2011 09:17:58 +0100 (CET)
Received: from [10.55.43.52] (ams-bclaise-8713.cisco.com [10.55.43.52]) by strange-brew.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id p2F8Hsxl010671; Tue, 15 Mar 2011 09:17:54 +0100 (CET)
Message-ID: <4D7F20B2.3070102@cisco.com>
Date: Tue, 15 Mar 2011 09:17:54 +0100
From: Benoit Claise <bclaise@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.9.2.15) Gecko/20110303 Thunderbird/3.1.9
MIME-Version: 1.0
To: Yaron Sheffer <yaronf.ietf@gmail.com>
References: <4D7F1516.6080401@gmail.com>
In-Reply-To: <4D7F1516.6080401@gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Tue, 15 Mar 2011 08:10:08 -0700
Cc: me <bclaise@cisco.com>, draft-ietf-ipfix-structured-data.all@tools.ietf.org, iesg@ietf.org, secdir@ietf.org
Subject: Re: [secdir] SecDir review of draft-ietf-ipfix-structured-data-05
X-BeenThere: secdir@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Security Area Directorate <secdir.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/secdir>, <mailto:secdir-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/secdir>
List-Post: <mailto:secdir@ietf.org>
List-Help: <mailto:secdir-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/secdir>, <mailto:secdir-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Mar 2011 09:21:07 -0000

Hi Yaron,

Thanks for your feedback.
Sure we should add your proposed sentence.

Regards, Benoit.
> I have reviewed this document as part of the security directorate's
> ongoing effort to review all IETF documents being processed by the IESG.
> These comments were written primarily for the benefit of the security
> area directors.  Document editors and WG chairs should treat these
> comments just like any other last call comments.
>
> IPFIX is a structured information model and protocol for transmitting 
> information about data flows. This document extends the model with 
> structured data, basically several types of lists.
>
> I have not reviewed the document in full, rather I have looked at the 
> security aspects only. The Security Considerations refer the reader to 
> the IPFIX protocol and data model RFCs, and I mostly agree, with one 
> exception. I suggest to add text similar to the next paragraph:
>
> The addition of complex data types necessarily complicates the 
> implementation of the Collector. This could easily result in new 
> security vulnerabilities (e.g., buffer overflows); this creates 
> additional risk in cases where either DTLS is not used, or if the 
> Observation Point and Collector belong to different trust domains.
>
> Thanks,
>     Yaron