Document Action: 'IPFIX Mediation: Framework' to Informational RFC (draft-ietf-ipfix-mediators-framework-09.txt)

The IESG <iesg-secretary@ietf.org> Mon, 20 December 2010 21:07 UTC

Return-Path: <iesg-secretary@ietf.org>
X-Original-To: ietf-announce@core3.amsl.com
Delivered-To: ietf-announce@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id DB0A63A6AF4; Mon, 20 Dec 2010 13:07:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level:
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 kYp5n3iyRcb3; Mon, 20 Dec 2010 13:07:07 -0800 (PST)
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0B1683A6AF5; Mon, 20 Dec 2010 13:07:07 -0800 (PST)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Subject: Document Action: 'IPFIX Mediation: Framework' to Informational RFC (draft-ietf-ipfix-mediators-framework-09.txt)
X-Test-IDTracker: no
X-IETF-IDTracker: 3.10
Message-ID: <20101220210707.32571.30069.idtracker@localhost>
Date: Mon, 20 Dec 2010 13:07:07 -0800
Cc: Internet Architecture Board <iab@iab.org>, ipfix chair <ipfix-chairs@tools.ietf.org>, ipfix mailing list <ipfix@ietf.org>, RFC Editor <rfc-editor@rfc-editor.org>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-announce>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 20 Dec 2010 21:07:09 -0000

The IESG has approved the following document:
- 'IPFIX Mediation: Framework'
  (draft-ietf-ipfix-mediators-framework-09.txt) as an Informational RFC

This document is the product of the IP Flow Information Export Working
Group.

The IESG contact persons are Dan Romascanu and Ron Bonica.

A URL of this Internet Draft is:
http://datatracker.ietf.org/doc/draft-ietf-ipfix-mediators-framework/



Technical Summary

   This document describes a framework for IPFIX Mediation.  This
   framework extends the IPFIX reference model by defining the IPFIX
   Mediator components.

Working Group Summary

   The mediation framework was added to the IPIFX charter in 2008.
   There is a strong consensus in the IPFIX WG to publish this version
   of the document. The document had multiple individual reviews from key 
   WG members during two WG last calls. Several comments were made 
   and have been addressed when updating the document after the WGLCs.
   There are no particular issues in the document without strong consensus 
   in the IPFIX WG.

Document Quality

   The document underwent two WG last call in the IPFIX WG.
   This way, a high document quality has been achieved already.

Personnel

   Juergen Quittek is the Document Shepherd. Dan Romascanu is the
   Responsible Area Director.

RFC Editor Note

1.  Add to the document header: 

Updates: 5470 (if approved)

2. In the Abstract:

OLD: 

    This document describes a framework for IPFIX Mediation.  This
    framework extends the IPFIX reference model by defining the IPFIX
    Mediator components.

NEW: 

    This document describes a framework for IPFIX Mediation.  This
    framework extends the IPFIX reference model specified in RFC5470
    by defining the IPFIX Mediator components.

3. Add RFC 5470 and RFC 5655 as Normative References

4. In Section 8: 

OLD: 

     IPFIX Mediation reuses the general information models from [RFC5102]
     and [RFC5477].  However, several Intermediate Processes would
     potentially require additional Information Elements as follows:

NEW: 

    IPFIX Mediation reuses the general information models from [RFC5102]
    and [RFC5477], and, depending on the Intermediate Processes type, potentially Information
    Elements such as:

5. Append at the end of Section 5.3 the following paragraph: 

       For example, an Intermediate Aggregation Process aggregating incoming
       Flow Records composed of the sourceIPv4Address and destinationIPv4Address
       Flow Keys into outgoing Flow Records with the destinationIPv4Address
       Flow Key, must the modify the incoming flowKeyIndicator to contain only the
       destinationIPv4Address.