Re: [IPFIX] IPFIX at IETF 89, London

Paul Aitken <paitken@cisco.com> Mon, 03 February 2014 14:13 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 52C2D1A01D1 for <ipfix@ietfa.amsl.com>; Mon, 3 Feb 2014 06:13:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.729
X-Spam-Level:
X-Spam-Status: No, score=-8.729 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, RP_MATCHES_RCVD=-0.535, SPF_PASS=-0.001, TRACKER_ID=1.306, USER_IN_DEF_DKIM_WL=-7.5] autolearn=no
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 xVPp-OCdyTRf for <ipfix@ietfa.amsl.com>; Mon, 3 Feb 2014 06:13:27 -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 4B3281A02B2 for <ipfix@ietf.org>; Mon, 3 Feb 2014 02:39:58 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=5135; q=dns/txt; s=iport; t=1391423998; x=1392633598; h=message-id:date:from:mime-version:to:subject:references: in-reply-to; bh=J2pyhNTQi1LMIgxah2P/oBi7PcV7L8h7rYqAxBbeXdo=; b=FpNcHRqYdoS9fP6DCgtsIsvbhqhRcKrlohiy38eON4G7mPS0cezqu5HX 9eswKFu9NswXWACi30cDNyC5CBxoff4ovmIgv9t04pYSgBBGvFNB7gIfY DbqjuDhy1lJHXZ/UR7ANQABxYDBk07AxArwIf58ak23gKzZrMldLYOaNn k=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhwFANFw71KQ/khR/2dsb2JhbABZDoJ+OIk1tTqBBRZ0giUBAQEEeBELBAoKCRYPCQMCAQIBRQYBDAgBAYgBDcwCF44nDgMBV4Q4BJgqgTKFFotZgm4/gXE
X-IronPort-AV: E=Sophos;i="4.95,771,1384300800"; d="scan'208,217";a="3912133"
Received: from ams-core-1.cisco.com ([144.254.72.81]) by aer-iport-2.cisco.com with ESMTP; 03 Feb 2014 10:39:56 +0000
Received: from cisco.com (mrwint.cisco.com [64.103.70.36]) by ams-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id s13AduGj031178 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 3 Feb 2014 10:39:56 GMT
Received: from [10.61.106.22] (dhcp-10-61-106-22.cisco.com [10.61.106.22]) by cisco.com (8.14.4+Sun/8.8.8) with ESMTP id s13AdsAh002266; Mon, 3 Feb 2014 10:39:55 GMT
Message-ID: <52EF71FA.3090005@cisco.com>
Date: Mon, 03 Feb 2014 10:39:54 +0000
From: Paul Aitken <paitken@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: Nevil Brownlee <n.brownlee@auckland.ac.nz>, IPFIX list <ipfix@ietf.org>
References: <52EF4E92.3040906@auckland.ac.nz>
In-Reply-To: <52EF4E92.3040906@auckland.ac.nz>
Content-Type: multipart/alternative; boundary="------------020808050803050101090108"
Subject: Re: [IPFIX] IPFIX at IETF 89, London
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: Mon, 03 Feb 2014 14:13:29 -0000

Nevil,

I updated a couple of drafts. If the WG is to close, then I'll be 
looking for a new home for these, because this is important work which 
does need addressed:


aitken-ipfix-equivalent-ies 
<http://tools.ietf.org/html/draft-aitken-ipfix-equivalent-ies>

    This document specifies a method for an Exporter to inform a
    Collector of equivalence between different Information Elements, so
    that the Collecting Process can understand the equivalence and be
    enabled to process data across a change of Information Elements,
    which allows a seamless transition from Enterprise-specific to
    IANA-standard elements.

aitken-ipfix-unobserved-fields 
<http://tools.ietf.org/html/draft-aitken-ipfix-unobserved-fields>

    This draft discusses several methods for reporting when fields are
    unavailable, reviews the advantages and disadvantage of each, and
    recommends methods which should be used.
    Cisco has already implemented some of the mechanisms in this draft.


P.


On 03/02/2014 08:08, Nevil Brownlee wrote:
>
> Hi IPFIXers:
>
> Back when session scheduling for IETF 89 started, I requested a
> slot for IPFIX, "just in case."
>
> Since then the Link-Layer Attributes and Mediation Protocol drafts
> have been sent to the RFC Editor, and the text-adt draft is in WGLC.
>
> We expect a new revision of the MIB Variable export draft shortly,
> so that would be the only agenda item for London.  I feel that
> version can be reviewed and discussed on the IPFIX list, so we
> don't now need to have a formal IPFIX meeting in London.
>
> If you believe that a meeting is needed, please email the list
> telling us what that is, and why we need meeting time for it.
> If I don't see such email(s) within the next week, we'll cancel
> the meeting.
>
> Cheers, Nevil
>