Re: [IPFIX] IPFIX at IETF 89, London
Andrew Feren <andrewf@plixer.com> Mon, 03 February 2014 15:40 UTC
Return-Path: <andrewf@plixer.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 1180A1A0115 for <ipfix@ietfa.amsl.com>; Mon, 3 Feb 2014 07:40:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.128
X-Spam-Level:
X-Spam-Status: No, score=-1.128 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.535, TRACKER_ID=1.306] 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 9ud594BRfKBo for <ipfix@ietfa.amsl.com>; Mon, 3 Feb 2014 07:40:11 -0800 (PST)
Received: from mx1.plixer.com (mx1.plixer.com [64.140.243.154]) by ietfa.amsl.com (Postfix) with ESMTP id D5A8C1A0032 for <ipfix@ietf.org>; Mon, 3 Feb 2014 07:40:10 -0800 (PST)
Received: from [10.1.14.85] (64.140.243.154) by mx1.plixer.com (10.1.5.1) with Microsoft SMTP Server (TLS) id 14.3.158.1; Mon, 3 Feb 2014 10:40:09 -0500
Message-ID: <52EFB85A.3070409@plixer.com>
Date: Mon, 03 Feb 2014 10:40:10 -0500
From: Andrew Feren <andrewf@plixer.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: Paul Aitken <paitken@cisco.com>, Nevil Brownlee <n.brownlee@auckland.ac.nz>, IPFIX list <ipfix@ietf.org>
References: <52EF4E92.3040906@auckland.ac.nz> <52EF71FA.3090005@cisco.com>
In-Reply-To: <52EF71FA.3090005@cisco.com>
Content-Type: multipart/alternative; boundary="------------010806080707070506010309"
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 15:40:13 -0000
Hi All, +1. Those drafts need to be addressed. -Andrew On 02/03/2014 05:39 AM, Paul Aitken wrote: > 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 >> > > > > _______________________________________________ > IPFIX mailing list > IPFIX@ietf.org > https://www.ietf.org/mailman/listinfo/ipfix
- [IPFIX] IPFIX at IETF 89, London Nevil Brownlee
- Re: [IPFIX] IPFIX at IETF 89, London Paul Aitken
- Re: [IPFIX] IPFIX at IETF 89, London Andrew Feren
- Re: [IPFIX] IPFIX at IETF 89, London Nevil Brownlee
- Re: [IPFIX] IPFIX at IETF 89, London Paul Aitken
- Re: [IPFIX] IPFIX at IETF 89, London Brian Trammell
- Re: [IPFIX] IPFIX at IETF 89, London joel jaeggli
- Re: [IPFIX] IPFIX at IETF 89, London Brian Trammell
- Re: [IPFIX] IPFIX at IETF 89, London Nevil Brownlee
- Re: [IPFIX] IPFIX at IETF 89, London Benoit Claise
- Re: [IPFIX] IPFIX at IETF 89, London Paul Aitken
- Re: [IPFIX] IPFIX at IETF 89, London Benoit Claise
- Re: [IPFIX] IPFIX at IETF 89, London Juergen Quittek
- Re: [IPFIX] IPFIX at IETF 89, London Andrew Feren
- Re: [IPFIX] IPFIX at IETF 89, London Juergen Quittek
- Re: [IPFIX] IPFIX at IETF 89, London Benoit Claise