Re: [IPFIX] draft-ietf-ipfix-ie-doctors-04.txt

Brian Trammell <trammell@tik.ee.ethz.ch> Fri, 14 September 2012 13:35 UTC

Return-Path: <trammell@tik.ee.ethz.ch>
X-Original-To: ipfix@ietfa.amsl.com
Delivered-To: ipfix@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8E3B521F849A for <ipfix@ietfa.amsl.com>; Fri, 14 Sep 2012 06:35:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level:
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DFwVZfKTWZHU for <ipfix@ietfa.amsl.com>; Fri, 14 Sep 2012 06:34:59 -0700 (PDT)
Received: from smtp.ee.ethz.ch (smtp.ee.ethz.ch [129.132.2.219]) by ietfa.amsl.com (Postfix) with ESMTP id 3B61421F8498 for <ipfix@ietf.org>; Fri, 14 Sep 2012 06:34:59 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by smtp.ee.ethz.ch (Postfix) with ESMTP id C01CDD930D; Fri, 14 Sep 2012 15:34:57 +0200 (MEST)
X-Virus-Scanned: by amavisd-new on smtp.ee.ethz.ch
Received: from smtp.ee.ethz.ch ([127.0.0.1]) by localhost (.ee.ethz.ch [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 3ll7dIgl-tlH; Fri, 14 Sep 2012 15:34:57 +0200 (MEST)
Received: from pb-10243.ethz.ch (pb-10243.ethz.ch [82.130.102.152]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: briant) by smtp.ee.ethz.ch (Postfix) with ESMTPSA id 8C016D930A; Fri, 14 Sep 2012 15:34:57 +0200 (MEST)
Mime-Version: 1.0 (Apple Message framework v1278)
Content-Type: text/plain; charset="us-ascii"
From: Brian Trammell <trammell@tik.ee.ethz.ch>
In-Reply-To: <918337CC-0D0B-4AB9-B3F7-BE4AC6828CE5@tik.ee.ethz.ch>
Date: Fri, 14 Sep 2012 15:34:57 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <699C6609-B366-4771-8718-FDEC11F23C08@tik.ee.ethz.ch>
References: <20120831165653.9430.22489.idtracker@ietfa.amsl.com> <5044C8A9.6090703@cisco.com> <56DE85D5-8B82-4351-826F-2B5D75E3F95C@tik.ee.ethz.ch> <5044E42A.7050303@cisco.com> <918337CC-0D0B-4AB9-B3F7-BE4AC6828CE5@tik.ee.ethz.ch>
To: Paul Aitken <paitken@cisco.com>
X-Mailer: Apple Mail (2.1278)
Cc: IETF IPFIX Working Group <ipfix@ietf.org>
Subject: Re: [IPFIX] draft-ietf-ipfix-ie-doctors-04.txt
X-BeenThere: ipfix@ietf.org
X-Mailman-Version: 2.1.12
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: Fri, 14 Sep 2012 13:35:01 -0000

Hi, Paul, all,

On reflection, I can't really see how fixing the status of the Units registry in 5610 would be in scope for this draft; therefore, in my opinion, ie-doctors-04 is in its present state ready for the IESG, with the note that a revision addressing comments/discusses from the IESG will also include an update to note that Units is extended subject to Expert Review, and to correct Benoit's address.

I'm still not certain as to the best approach to fix 5610 with respect to its definition of the Units registry as FCFS; would a technical erratum suffice? (Is there an AD in the house with an opinion? :) )

Best regards,

Brian

On Sep 3, 2012, at 7:53 PM, Brian Trammell wrote:

> Hi, Paul,
> 
> As the registry (to date) has been de facto expert review (and there have been no registrations), I don't see any problem with this.
> 
> However, can IE-DOCTORS update 5610? 5610 is Standards Track, and IE-DOCTORS targets BCP. If not, this would be a technical erratum on 5610.
> 
> Cheers,
> 
> Brian
> 
> 
> On Sep 3, 2012, at 7:08 PM, Paul Aitken wrote:
> 
>> Brian,
>> 
>>> Hi, Paul,
>>> 
>>> Interesting.
>>> 
>>> I hadn't checked the registry, but I can say that the FCFS policy for Units was intentional: imagine a an enterprise-specific information element designed to do something very odd with unorthodox units, say, counting rats crawling around in the underfloor space in a data center (perhaps to attempt to correlate packet loss with rodent infestation). Now, the IEs for this would be ESIEs, but since this is a research study, we'd want to annotate the data (stored in files) with 5610 type information records.
>> 
>> ie, 5610 allows units to be expressed for enterprise-specific IEs.
>> 
>> 
>>> However, on review, perhaps Units in the IANA registry should cover only those IEs in the IANA registry, and if you want to do something really odd, you should leave units blank and explain "expressed in rats per cubic meter as measured by the Yoyodyne Underfloor Rat Counter model 19" in the informationElementDescription field. But that was the intent.
>> 
>> This would prevent 5610 from working properly, since I couldn't created a "rats" unit for my ESIEs.
>> 
>> And if an IE is already in IANA's IPFIX registry, then it already has a type - so there'd be no need for it in 5610.
>> 
>> 
>>> If we decide this, the proper thing to do is to go with the registry as is and change IE-DOCTORS to update RFC 5610.
>> 
>> I think the "IPFIX units" registry should be subject to expert review - which allows enterprises to request "rats" for their enterprise-specific IEs if they want to use 5610, provided they can convince the expert reviewer that they have an IPFIX-enabled rat counter.
>> 
>> However, it ensures that IANA won't assign a lot of stupid units which may be requested by miscreants.
>> 
>> If all agree, then I'd be happy for IE-docs to update 5610 (and leave the registry unchanged).
>> 
>> P.
> 
> _______________________________________________
> IPFIX mailing list
> IPFIX@ietf.org
> https://www.ietf.org/mailman/listinfo/ipfix