Re: [ippm] Last Call: 'Packet Reordering Metric for IPPM' to Proposed Standard

Al Morton <acmorton@att.com> Sun, 09 April 2006 14:41 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FSb6Y-0004bn-8i; Sun, 09 Apr 2006 10:41:30 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FSb6W-0004a0-UI; Sun, 09 Apr 2006 10:41:28 -0400
Received: from mail126.messagelabs.com ([216.82.250.99]) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1FSb6V-0000QZ-J7; Sun, 09 Apr 2006 10:41:28 -0400
X-VirusChecked: Checked
X-Env-Sender: acmorton@att.com
X-Msg-Ref: server-2.tower-126.messagelabs.com!1144593686!10706829!1
X-StarScan-Version: 5.5.9.1; banners=-,-,-
X-Originating-IP: [134.24.146.4]
Received: (qmail 31299 invoked from network); 9 Apr 2006 14:41:26 -0000
Received: from unknown (HELO maillennium.att.com) (134.24.146.4) by server-2.tower-126.messagelabs.com with SMTP; 9 Apr 2006 14:41:26 -0000
Received: from acmt.att.com (unknown[135.70.150.5](misconfigured sender)) by maillennium.att.com (mailgw1) with SMTP id <20060409144124gw1001002ve>; Sun, 9 Apr 2006 14:41:25 +0000
Message-Id: <6.2.1.2.0.20060407224249.0229d900@postoffice.maillennium.att.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.1.2
Date: Sun, 09 Apr 2006 10:41:24 -0400
To: Lars Eggert <lars.eggert@netlab.nec.de>, Henk Uijterwaal <henk@ripe.net>, Matthew J Zekauskas <matt@internet2.edu>, Emile Stephan <emile.stephan@francetelecom.com>
From: Al Morton <acmorton@att.com>
Subject: Re: [ippm] Last Call: 'Packet Reordering Metric for IPPM' to Proposed Standard
In-Reply-To: <E1FO2Rj-0008Pd-Dq@stiedprstage1.ietf.org>
References: <E1FO2Rj-0008Pd-Dq@stiedprstage1.ietf.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4d87d2aa806f79fed918a62e834505ca
Cc: iesg@ietf.org, ippm@ietf.org
X-BeenThere: ippm@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF IP Performance Metrics Working Group <ippm.ietf.org >
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ippm>, <mailto:ippm-request@ietf.org ?subject=unsubscribe>
List-Post: <mailto:ippm@ietf.org >
List-Help: <mailto:ippm-request@ietf.org ?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ippm>, <mailto:ippm-request@ietf.org ?subject=subscribe>
Errors-To: ippm-bounces@ietf.org

At 08:52 PM 3/27/2006, The IESG wrote:
>- 'Packet Reordering Metric for IPPM '
>    <draft-ietf-ippm-reordering-11.txt> as a Proposed Standard
>
>The IESG plans to make a decision in the next few weeks, and solicits
>final comments on this action.  Please send any comments to the
>iesg@ietf.org or ietf@ietf.org mailing lists by 2006-04-10.

Lars, Henk, Matt,

Emile Stephan passed a comment to me in-person,
regarding the IPPM Metrics Registry.  He reminds that the IANA section
of the draft should request registration of the metrics,
as is done in the current version of the ippm-multimetrics draft:

9.  IANA Considerations

    Metrics defined in this memo should be registered in the IANA IPPM
    METRICS REGISTRY as described in initial version of the registry
    [RFC4148].

Emile -- As author of the registry RFC, is the text sufficient?
Or do we need to prepare a template for each new metric,
as RFC 4148 says:

>5.2.  Registration Template
>
>    The following is a proposed template to insert in the IANA
>    considerations section.  For each metric, that section would
>    instantiate the following statement:
>
>       IANA has registed the following metric in the IANA-IPPM-METRICS-
>       REGISTRY-MIB:
>
>        aNewMetricName OBJECT-IDENTITY
>        STATUS       current
>        DESCRIPTION
>           "The identifier for a new metric."
>        REFERENCE
>           "Reference R, section n."
>           ::= { ianaIppmMetrics nn }     -- IANA assigns nn

I don't mind preparing a template for each reordering metric with a
"Metric Name" section. But this seems like a lot of text
to insert at Last Call, although none of it would be controversial.

We might do this in a separate draft, too.
I'm open to opinions and suggestions.

Al



_______________________________________________
ippm mailing list
ippm@ietf.org 
https://www1.ietf.org/mailman/listinfo/ippm