[IPFIX] Fwd: Last Call: <draft-ietf-ipfix-text-adt-07.txt> (Textual Representation of IPFIX Abstract Data Types) to Proposed Standard

Benoit Claise <bclaise@cisco.com> Wed, 16 July 2014 22:33 UTC

Return-Path: <bclaise@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 1437F1A037D for <ipfix@ietfa.amsl.com>; Wed, 16 Jul 2014 15:33:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.151
X-Spam-Level:
X-Spam-Status: No, score=-15.151 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.651, 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 nvwxGcpRaOWC for <ipfix@ietfa.amsl.com>; Wed, 16 Jul 2014 15:33:49 -0700 (PDT)
Received: from aer-iport-2.cisco.com (aer-iport-2.cisco.com [173.38.203.52]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1CEEF1A0378 for <ipfix@ietf.org>; Wed, 16 Jul 2014 15:33:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=6773; q=dns/txt; s=iport; t=1405550029; x=1406759629; h=message-id:date:from:mime-version:to:subject:references: in-reply-to; bh=ernd1NoA+VVordaEOdngyC6O0lRkyxZdSfUPNwIT4Ds=; b=ltGowS32O104D+9kChE3h0+8T7ZO2gwuE/qmjFIbPaOuB+SONXsisDwu FzsV2DZ9u7RVDbcQKGDh1EHBvQet1kmP7D29U/nstwotvUyOaQTmwmniN VK2z3E3kBAQZqD3Yrphxy9BNxvk4ZUvTz7gw66ovr8zv5pdNwnnf0RYJP 4=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AqoEALz8xlOtJssW/2dsb2JhbABag2BXwy0BCYdCAYEhdoQDAQEBBAEBAWsKDQQcAwECChYECwkDAgECARUfBwIIBg0GAgEBiD4NylEXjzoYBoQ9BZsdgUyFSI0YggKBRDsv
X-IronPort-AV: E=Sophos;i="5.01,674,1400025600"; d="scan'208,217";a="113918353"
Received: from aer-iport-nat.cisco.com (HELO aer-core-4.cisco.com) ([173.38.203.22]) by aer-iport-2.cisco.com with ESMTP; 16 Jul 2014 22:33:47 +0000
Received: from [10.60.67.84] (ams-bclaise-8913.cisco.com [10.60.67.84]) by aer-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id s6GMXleq020747 for <ipfix@ietf.org>; Wed, 16 Jul 2014 22:33:47 GMT
Message-ID: <53C6FDCB.5030804@cisco.com>
Date: Thu, 17 Jul 2014 00:33:47 +0200
From: Benoit Claise <bclaise@cisco.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: "ipfix@ietf.org" <ipfix@ietf.org>
References: <20140716222427.14473.7386.idtracker@ietfa.amsl.com>
In-Reply-To: <20140716222427.14473.7386.idtracker@ietfa.amsl.com>
X-Forwarded-Message-Id: <20140716222427.14473.7386.idtracker@ietfa.amsl.com>
Content-Type: multipart/alternative; boundary="------------030607020901070705010905"
Archived-At: http://mailarchive.ietf.org/arch/msg/ipfix/JrMw9uHeALod13gTvvp4LxBoMcg
Subject: [IPFIX] Fwd: Last Call: <draft-ietf-ipfix-text-adt-07.txt> (Textual Representation of IPFIX Abstract Data Types) to Proposed Standard
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: Wed, 16 Jul 2014 22:33:51 -0000

Dear IPFIX WG,

In the text below, I explain the reason behind the second IETF LC:

    During the IESG telechat, the IESG concluded that this document should be
    Proposed Standard, and not Informational as initially proposed in v6.
    This IETF LC should focus on the Proposed Standard changes in the
    latest version.


Regards, Benoit

-------- Original Message --------
Subject: 	[IPFIX] Last Call: <draft-ietf-ipfix-text-adt-07.txt> (Textual 
Representation of IPFIX Abstract Data Types) to Proposed Standard
Date: 	Wed, 16 Jul 2014 15:24:27 -0700
From: 	The IESG <iesg-secretary@ietf.org>
Reply-To: 	<ietf@ietf.org>
To: 	IETF-Announce <ietf-announce@ietf.org>
CC: 	<ipfix@ietf.org>



The IESG has received a request from the IP Flow Information Export WG
(ipfix) to consider the following document:
- 'Textual Representation of IPFIX Abstract Data Types'
   <draft-ietf-ipfix-text-adt-07.txt>

During the IESG telechat, the IESG concluded that this document should be
Proposed Standard, and not Informational as initially proposed in v6.
This IETF LC should focus on the Proposed Standard changes in the
latest version.

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action. Please send substantive comments to the
ietf@ietf.org mailing lists by 2014-07-30. Exceptionally, comments may be
sent to iesg@ietf.org instead. In either case, please retain the
beginning of the Subject line to allow automated sorting.

Abstract


    This document defines UTF-8 representations for IPFIX abstract data
    types, to support interoperable usage of the IPFIX Information
    Elements with protocols based on textual encodings.




The file can be obtained via
http://datatracker.ietf.org/doc/draft-ietf-ipfix-text-adt/

IESG discussion can be tracked via
http://datatracker.ietf.org/doc/draft-ietf-ipfix-text-adt/ballot/


No IPR declarations have been submitted directly on this I-D.


_______________________________________________
IPFIX mailing list
IPFIX@ietf.org
https://www.ietf.org/mailman/listinfo/ipfix
.