Re: [IPFIX] IPFIX at IETF 89, London
Juergen Quittek <Quittek@neclab.eu> Tue, 11 February 2014 09:02 UTC
Return-Path: <Quittek@neclab.eu>
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 62B751A0919 for <ipfix@ietfa.amsl.com>; Tue, 11 Feb 2014 01:02:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.15
X-Spam-Level:
X-Spam-Status: No, score=-3.15 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.548, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] 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 Nm0_jO-Q1wMy for <ipfix@ietfa.amsl.com>; Tue, 11 Feb 2014 01:02:18 -0800 (PST)
Received: from mailer1.neclab.eu (mailer1.neclab.eu [195.37.70.40]) by ietfa.amsl.com (Postfix) with ESMTP id 918E11A0914 for <ipfix@ietf.org>; Tue, 11 Feb 2014 01:02:18 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mailer1.neclab.eu (Postfix) with ESMTP id C7BC8106C2D; Tue, 11 Feb 2014 10:02:17 +0100 (CET)
X-Virus-Scanned: Amavisd on Debian GNU/Linux (netlab.nec.de)
Received: from mailer1.neclab.eu ([127.0.0.1]) by localhost (atlas-a.office.hd [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cdtinn2z-6Vh; Tue, 11 Feb 2014 10:02:17 +0100 (CET)
X-ENC: Last-Hop-TLS-encrypted
X-ENC: Last-Hop-TLS-encrypted
Received: from METHONE.office.hd (methone.office.hd [192.168.24.54]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by mailer1.neclab.eu (Postfix) with ESMTPS id AAA11106C25; Tue, 11 Feb 2014 10:01:42 +0100 (CET)
Received: from HYDRA.office.hd ([169.254.4.189]) by METHONE.office.hd ([192.168.24.54]) with mapi id 14.01.0323.003; Tue, 11 Feb 2014 10:01:42 +0100
From: Juergen Quittek <Quittek@neclab.eu>
To: joel jaeggli <joelja@bogus.com>, Brian Trammell <trammell@tik.ee.ethz.ch>, Paul Aitken <paitken@cisco.com>
Thread-Topic: [IPFIX] IPFIX at IETF 89, London
Thread-Index: AQHPJneAZA4W28tlf0eM8CyINORWQpqvwSsg
Date: Tue, 11 Feb 2014 09:01:42 +0000
Message-ID: <9AB93E4127C26F4BA7829DEFDCE5A6E877A36C4F@Hydra.office.hd>
References: <52EF4E92.3040906@auckland.ac.nz> <52EF71FA.3090005@cisco.com> <52F80BCA.2030408@auckland.ac.nz> <52F8AAB5.5050604@cisco.com> <0705D07E-6FB1-4BB7-8AD7-8A38656CDB93@tik.ee.ethz.ch> <52F8F490.3040500@bogus.com>
In-Reply-To: <52F8F490.3040500@bogus.com>
Accept-Language: de-DE, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.1.2.165]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "ipfix-ads@tools.ietf.org" <ipfix-ads@tools.ietf.org>, Nevil Brownlee <n.brownlee@auckland.ac.nz>, IPFIX Working Group <ipfix@ietf.org>, "ipfix-chairs@tools.ietf.org" <ipfix-chairs@tools.ietf.org>
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: Tue, 11 Feb 2014 09:02:22 -0000
Hi all, > -----Original Message----- > From: IPFIX [mailto:ipfix-bounces@ietf.org] On Behalf Of joel jaeggli > Sent: Montag, 10. Februar 2014 16:47 > To: Brian Trammell; Paul Aitken > Cc: ipfix-ads@tools.ietf.org; Nevil Brownlee; IPFIX Working Group; ipfix- > chairs@tools.ietf.org > Subject: Re: [IPFIX] IPFIX at IETF 89, London > > On 2/10/14, 7:31 AM, Brian Trammell wrote: > > There are a couple of questions here: (1) do we close / lay dormant / > > recharter the working group (and what do we do with these two drafts)? > > and (2) do we have a meeting in London? > > > From my point of view I can say that both drafts are important, have > > clearly had a good deal of discussion, and are probably at this point > > of a quality that they could be adopted as WG items. We had an idea in > > Vancouver that further work could be AD sponsored if the IPFIX WG > > closed. Recent experience in trying to AD sponsor other IPFIX-related > > drafts were not appreciated by the IESG, so I don't think that's an > > option for these two. > > Was not appreciated by some members of the IESG. under the > circumstances and for the document in question I think the method applied > was entirely apprpiate and that the results will speak for themselves. As far as I understood this issue, it was not appreciated by all IESG members, because there still was an IPFIX WG in place. If IPFIX is closed, I do not see how they could still have any problem. Juergen > > OPSAWG would be an option, but only if we definitively close IPFIX > > (otherwise the question is "why not recharter IPFIX"). > > > > Separate is the meeting-in-London question. At least here I can say I > > will not attend the currently-scheduled IPFIX meeting in London as it > > conflicts with a BoF I'm co-chairing; we've already tried to > > de-conflict this with no luck. > > > > Cheers, > > > > Brian > > > > On 10 Feb 2014, at 11:32, Paul Aitken <paitken@cisco.com> wrote: > > > >> Nevil, > >> > >>> Hi Paul, Andrew and IPFIXers: > >>> > >>> Looking back at the IPFIX minutes for IETF-88 (Vancouver), we said > >>> that "the WG will close when the current charter items are > >>> complete." The only remaining charter item is the MIB Variable > >>> Export draft, current version is -03, 21 Oct 2013. It's > >>> disappointing that we haven't seen a revision of that draft in 2014; > >>> when we have a new version, we should be able to start its WGLC. > >> > >> We're working on the next version. > >> > >> > >>> Paul and Andrew were the only two who responded to my 2 Feb email. > >>> Neither of the the two drafts they mentioned have been updated since > >>> January 2014, > >> > >> Oh come on Nevil! One's dated Dec 27th, the other Dec 31st. How fresh > >> do they need to be? > >> > >> So I have these two drafts which I believe are important to IPFIX, > >> and an independent second-opinion concurs. How can these drafts be > >> progressed? > >> > >> > >>> and there's been no discussion of them on the IPFIX list. > >> > >> I've presented these ideas in previous WG meetings, where the > >> consensus was to wait for the next re-charter. I'm sure they've been > >> discussed on-list too. > >> > >> > >> P. > >> > >> > >>> The same goes for the Cisco IEs draft, current version -09, 15 Jan > >>> 2014. > >>> > >>> Therefore, IPFIX will not hold a formal meeting in London, I'll > >>> inform the secretariat that we're cancelling the IPFIX meeting. > >>> > >>> Going forward from this ... > >>> > >>> - of course we can have an informal get-together of IPFIX people in > >>> London - any volunteers to organise such a gathering? > >>> > >>> - the IPFIX mailing list will remain open for quite some time, > >>> please use it to discuss anything relevant to IPFIX > >>> > >>> Cheers, Nevil > >>> > >>> > >>> On 3/02/14 11:39 PM, 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