[AVT] Revised WG last call status

Stephen Casner <casner@acm.org> Fri, 18 January 2002 02:49 UTC

Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA19102 for <avt-archive@odin.ietf.org>; Thu, 17 Jan 2002 21:49:49 -0500 (EST)
Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id VAA06153 for avt-archive@odin.ietf.org; Thu, 17 Jan 2002 21:49:52 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id VAA06084; Thu, 17 Jan 2002 21:45:43 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id VAA06057 for <avt@optimus.ietf.org>; Thu, 17 Jan 2002 21:45:41 -0500 (EST)
Received: from mailman.packetdesign.com (dns.packetdesign.com [65.192.41.10]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA19083 for <avt@ietf.org>; Thu, 17 Jan 2002 21:45:38 -0500 (EST)
Received: from ash.packetdesign.com (ash.packetdesign.com [192.168.0.243]) by mailman.packetdesign.com (8.11.0/8.11.0) with ESMTP id g0I2j9p16636; Thu, 17 Jan 2002 18:45:10 -0800 (PST) (envelope-from casner@acm.org)
Date: Thu, 17 Jan 2002 18:47:18 -0800
From: Stephen Casner <casner@acm.org>
To: AVT WG <avt@ietf.org>
Message-ID: <20020117184453.F91046-100000@ash.packetdesign.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit
Subject: [AVT] Revised WG last call status
Sender: avt-admin@ietf.org
Errors-To: avt-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
X-BeenThere: avt@ietf.org
Content-Transfer-Encoding: 8bit

At the end of the IETF meeting in SLC, I send a list of action items
from that meeting to be confirmed on the mailing list.  Included in
that list were several drafts to go to WG last call with an ending
date of January 11 (last Friday).  So, that WG last call period has
ended, but for most of these drafts, nary a peep was heard on the
list.

So, Colin and I have discussed this problem and decided on the
following plan:

********************************************************************
* This last call period is extended indefinitely for each draft    *
* until we get at least one valid review from someone not directly *
* involved with production of the draft (i.e., not an author or    *
* contributor).                                                    *
********************************************************************

We envision a couple of ways this might happen:

  - Working group participants who are interested in seeing a
    particular draft be published as an RFC may be motivated to
    provide such a review.

  - We suggest that authors of different drafts might wish to offer to
    to review each other's drafts, maybe pairwise or maybe in a
    "review ring".

  - I'm sure I needn't point out that more than one review would be
    most welcome.

Obviously, someone could dash off a quick message saying "I read draft
xxx and it looks fine to me" without even taking a look.  We're
depending on the integrity of the WG participants to do better than
that.

In making the review, keep in mind the things the IESG is going to be
considering, as described in

    http://www.ietf.org/ID-nits.html

An aspect of the review, as I discussed in my status report at the
start of the SLC meeting (and as reported in the minutes), is making
sure the language is clear and that there are not English nits --
misspellings, tenses mismatched, extraneous or missing plurals,
extraneous or missing articles, etc.  If the reviewer is willing to
mark all of those for the author, that would be great, but at least
please say whether or not the draft needs such corrections.

The drafts currently in WG last call are:

    Comfort Noise payload format (draft-ietf-avt-rtp-cn-04.txt)
        I have reviewed this one and I have a couple of comments I
        will be sending shortly.

    Enhanced CRTP (draft-ietf-avt-crtp-enhance-03.txt)

    Tunneled CRTP (draft-ietf-avt-tcrtp-05.txt)

    Unequal Erasure Protection (draft-ietf-avt-uxp-01.txt)

    Uneven Level Protection (draft-ietf-avt-ulp-03.txt )

    MPEG-4 generic (draft-ietf-avt-mpeg4-multisl-03.txt)

    MPEG-4 simple (draft-ietf-avt-mpeg4-simple-00.txt)

    Distributed Speech Recognition (draft-ietf-avt-dsr-00.txt)

Two more are supposed to start wg last call after being updated as
discussed at the SLC meeting:

    Extended RTP Profile for RTCP-based Feedback
        Actually, there was a message from Roni Even about this one,
        but not a reply.

    Secure RTP profile (draft-ietf-avt-srtp-02.txt)
        There was a question from Andre Flöper about this one, which
        implies at least a partial reading, and a reply.

    RTP Payload Format for EVRC, SMV and Frame-Based Vocoders
    (draft-li-avt-vocoder-00.txt)


The action item note I send in December also mentioned a draft that
had already gone to the IESG: the RTP payload format and file storage
format for AMR and AMR-WB audio (draft-ietf-avt-rtp-amr-10.txt).  I
mentioned that the IESG response was that the draft was not written
clearly enough.  Qiaobing Xie stepped up quickly with an offer to
rewrite the draft, and I proposed a schedule for the update that was
to have been finished by Christmas.  However, there has been quite a
bit of discussion among the authors, and I did a detailed review
myself which resulted in suggestions for substantial changes.  As a
consequence, it is appropriate that we have the WG review the revised
draft again before it goes back to the IESG.  You should see a new
draft soon.

Naturally, comments on this last call plan are also welcome.

							-- Steve


_______________________________________________
Audio/Video Transport Working Group
avt@ietf.org
https://www1.ietf.org/mailman/listinfo/avt