[IPFIX] FW: DISCUSS: draft-ietf-ipfix-mediators-problem-statement

"Romascanu, Dan (Dan)" <dromasca@avaya.com> Thu, 06 May 2010 08:51 UTC

Return-Path: <dromasca@avaya.com>
X-Original-To: ipfix@core3.amsl.com
Delivered-To: ipfix@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 311C23A67D1 for <ipfix@core3.amsl.com>; Thu, 6 May 2010 01:51:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.072
X-Spam-Level:
X-Spam-Status: No, score=-2.072 tagged_above=-999 required=5 tests=[AWL=0.527, 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 P1w0TBL9VTUK for <ipfix@core3.amsl.com>; Thu, 6 May 2010 01:51:43 -0700 (PDT)
Received: from co300216-co-outbound.net.avaya.com (co300216-co-outbound.net.avaya.com [198.152.13.100]) by core3.amsl.com (Postfix) with ESMTP id 718DC3A68B1 for <ipfix@ietf.org>; Thu, 6 May 2010 01:51:39 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.52,339,1270440000"; d="scan'208";a="216738275"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by co300216-co-outbound.net.avaya.com with ESMTP; 06 May 2010 04:51:26 -0400
X-IronPort-AV: E=Sophos;i="4.52,339,1270440000"; d="scan'208";a="471465311"
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.13]) by co300216-co-erhwest-out.avaya.com with ESMTP; 06 May 2010 04:51:25 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 06 May 2010 10:51:24 +0200
Message-ID: <EDC652A26FB23C4EB6384A4584434A0402180465@307622ANEX5.global.avaya.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: DISCUSS: draft-ietf-ipfix-mediators-problem-statement
Thread-Index: Acrsz2Jk5cffzY8iSGS2ZXIMZeirLQAKdQ7w
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: ipfix@ietf.org
Subject: [IPFIX] FW: DISCUSS: draft-ietf-ipfix-mediators-problem-statement
X-BeenThere: ipfix@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IPFIX WG discussion list <ipfix.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 06 May 2010 08:51:44 -0000

Editors and Chairs,

Please address the issue raised by Sean in his DISCUSS. 

Thanks and Regards,

Dan


-----Original Message-----
From: iesg-bounces@ietf.org [mailto:iesg-bounces@ietf.org] On Behalf Of
Sean Turner
Sent: Thursday, May 06, 2010 6:51 AM
To: iesg@ietf.org
Cc: draft-ietf-ipfix-mediators-problem-statement@tools.ietf.org;
ipfix-chairs@tools.ietf.org
Subject: DISCUSS: draft-ietf-ipfix-mediators-problem-statement 

Discuss:
#1) The SECDIR review pointed out that the trust model needs to be
explained.   Atsushi suggested that there were two scenarios and they
should probably go in the follow-on framework document.  If that is the
case, then a normative reference is needed to point from the trust model
text/section to that particular section in the framework document.
However, the -06 of draft-ietf-ipfix-mediators-framework does not seem
to include this text.  Is it going to be included or is the trust model
going to be included in problem-statement?