[ippm] publication request for draft-ietf-ippm-twamp-session-cntrl-03.txt

Henk Uijterwaal <henk@ripe.net> Thu, 18 February 2010 08:57 UTC

Return-Path: <henk@ripe.net>
X-Original-To: ippm@core3.amsl.com
Delivered-To: ippm@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D90093A7E72; Thu, 18 Feb 2010 00:57:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.911
X-Spam-Level:
X-Spam-Status: No, score=-1.911 tagged_above=-999 required=5 tests=[AWL=0.688, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Pvjj4-YpDzVT; Thu, 18 Feb 2010 00:57:56 -0800 (PST)
Received: from postlady.ripe.net (postlady.ipv6.ripe.net [IPv6:2001:610:240:11::c100:1341]) by core3.amsl.com (Postfix) with ESMTP id 568BF3A7E7F; Thu, 18 Feb 2010 00:57:56 -0800 (PST)
Received: from ayeaye.ripe.net ([193.0.1.103]) by postlady.ripe.net with esmtps (TLSv1:AES256-SHA:256) (Exim 4.63) (envelope-from <henk@ripe.net>) id 1Ni2EM-00061T-Ar; Thu, 18 Feb 2010 09:59:35 +0100
Received: from [193.0.21.124] (helo=guest-17.ripe.net) by ayeaye.ripe.net with esmtp (Exim 4.63) (envelope-from <henk@ripe.net>) id 1Ni2EM-00089O-82; Thu, 18 Feb 2010 09:59:30 +0100
Message-ID: <4B7D0172.5090204@ripe.net>
Date: Thu, 18 Feb 2010 09:59:30 +0100
From: Henk Uijterwaal <henk@ripe.net>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-GB; rv:1.9.1.7) Gecko/20100111 Lightning/1.0b1 Thunderbird/3.0.1
MIME-Version: 1.0
To: Lars Eggert <lars.eggert@nokia.com>, The IESG <iesg-secretary@ietf.org>, Matthew J Zekauskas <matt@internet2.edu>, IETF IPPM WG <ippm@ietf.org>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-RIPE-Signature: e0cdef1f45f89a40ad608d255b27e7d512f0ef141f9b57f9d51f6379ec334df5
X-RIPE-Spam-Level: ----
X-RIPE-Signature: e0cdef1f45f89a40ad608d255b27e7d512f0ef141f9b57f9d51f6379ec334df5
Subject: [ippm] publication request for draft-ietf-ippm-twamp-session-cntrl-03.txt
X-BeenThere: ippm@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF IP Performance Metrics Working Group <ippm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ippm>, <mailto:ippm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ippm>
List-Post: <mailto:ippm@ietf.org>
List-Help: <mailto:ippm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ippm>, <mailto:ippm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 18 Feb 2010 08:57:57 -0000

Lars, IESG-secretary,

The IPPM WG requests publication of draft-ietf-ippm-twamp-session-cntrl-03.txt
on the standards track.  The sheperd write-up for the document is below.

Henk

- - - -



   (1.a) Who is the Document Shepherd for this document? Has the
         Document Shepherd personally reviewed this version of the
         document and, in particular, does he or she believe this
         version is ready for forwarding to the IESG for publication?

Document sheperd is Henk Uijterwaal.  He would not have bothered to write
this note if he didn't believe that the document was ready for publication.

   (1.b) Has the document had adequate review both from key WG members
         and from key non-WG members?

This is a small feature request.  About half a dozen people have read the
document and confirmed that this request will work without affecting current
implementations.   The request itself seems to be a useful enhancement.

   (1.c) Does the Document Shepherd have concerns that the document
         needs more review from a particular or broader perspective,

No.

   (1.d) Does the Document Shepherd have any specific concerns or
         issues with this document that the Responsible Area Director
         and/or the IESG should be aware of?

No, there are no such concerns.

   (1.e) How solid is the WG consensus behind this document? Does it
         represent the strong concurrence of a few individuals, with
         others being silent, or does the WG as a whole understand and
         agree with it?

Decent, with some 6 members of the group reviewing it.

   (1.f) Has anyone threatened an appeal or otherwise indicated extreme
         discontent?

No.

   (1.g) Has the Document Shepherd personally verified that the
         document satisfies all ID nits?

All except a complaint about the boilerplate.  This can be fixed by
the editor easily.

   (1.h) Has the document split its references into normative and
         informative? Are there normative references to documents that
         are not ready for advancement or are otherwise in an unclear
         state?

Yes, draft-ietf-ippm-twamp-reflect-octets.  This draft has an ETA
of Q1/2010.

   (1.i) Has the Document Shepherd verified that the document IANA
         consideration section exists and is consistent with the body
         of the document?

Yes, it exists and appears to be complete and consistent

   (1.j) Has the Document Shepherd verified that sections of the
         document that are written in a formal language, such as XML
         code, BNF rules, MIB definitions, etc., validate correctly in
         an automated checker?

N/A.

   (1.k) The IESG approval announcement includes a Document
         Announcement Write-Up. Please provide such a Document
         Announcement Write-Up? Recent examples can be found in the
         "Action" announcements for approved documents. The approval
         announcement contains the following sections:

      Technical Summary
    The IETF has completed its work on the core specification of TWAMP -
    the Two-Way Active Measurement Protocol.  This memo describes a new
    feature for TWAMP, that gives the controlling host the ability to
    start and stop one or more individual test sessions using Session
    Identifiers.  The base capability of the TWAMP protocol requires all
    test sessions previously requested and accepted to start and stop at
    the same time.

      Working Group Summary
The normal WG process was followed and the document has been discussed for
several years.  The document as it is now, reflects WG consensus, with nothing
special worth noticing.

      Document Quality
Good
-- 
------------------------------------------------------------------------------
Henk Uijterwaal                           Email: henk.uijterwaal(at)ripe.net
RIPE Network Coordination Centre          http://www.xs4all.nl/~henku
P.O.Box 10096          Singel 258         Phone: +31.20.5354414
1001 EB Amsterdam      1016 AB Amsterdam  Fax: +31.20.5354445
The Netherlands        The Netherlands    Mobile: +31.6.55861746
------------------------------------------------------------------------------

Nobody ever went broke underestimating the taste of the American public.
                                                                  H.L.Mencken