Re: [AVT] RTP MIDI ...

Colin Perkins <csp@csperkins.org> Tue, 02 September 2003 13:40 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 JAA24887 for <avt-archive@odin.ietf.org>; Tue, 2 Sep 2003 09:40:39 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19uBOH-0002em-6L for avt-archive@odin.ietf.org; Tue, 02 Sep 2003 09:40:13 -0400
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h82DeC8i010159 for avt-archive@odin.ietf.org; Tue, 2 Sep 2003 09:40:12 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19uBOA-0002cy-OH; Tue, 02 Sep 2003 09:40:06 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19uA0w-00063N-RA for avt@optimus.ietf.org; Tue, 02 Sep 2003 08:12:03 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA15187 for <avt@ietf.org>; Tue, 2 Sep 2003 08:11:58 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19uA0v-0006CJ-00 for avt@ietf.org; Tue, 02 Sep 2003 08:12:01 -0400
Received: from dundee.dcs.gla.ac.uk ([130.209.242.163]) by ietf-mx with esmtp (Exim 4.12) id 19uA0v-00068r-00 for avt@ietf.org; Tue, 02 Sep 2003 08:12:01 -0400
Received: from bisa ([130.209.247.104]:51502 helo=csperkins.org) by dundee.dcs.gla.ac.uk with asmtp (TLSv1:DES-CBC3-SHA:168) (Exim 4.04) id 19uA0P-0006Cd-00; Tue, 02 Sep 2003 13:11:29 +0100
Date: Tue, 02 Sep 2003 13:11:26 +0100
Subject: Re: [AVT] RTP MIDI ...
Content-Type: text/plain; charset="US-ASCII"; format="flowed"
Mime-Version: 1.0 (Apple Message framework v552)
Cc: avt@ietf.org
To: John Lazzaro <lazzaro@CS.Berkeley.EDU>
From: Colin Perkins <csp@csperkins.org>
In-Reply-To: <200309010234.h812YsV13071@snap.CS.Berkeley.EDU>
Message-Id: <93583C57-DD3E-11D7-BB55-000A957FC5F2@csperkins.org>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.552)
Content-Transfer-Encoding: 7bit
Sender: avt-admin@ietf.org
Errors-To: avt-admin@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

On Monday, Sep 1, 2003, at 03:34 Europe/London, John Lazzaro wrote:
> 	Just a quick note to let everyone know that progress on RTP
> MIDI continues, the last few months have been spent recoding sfront to
> be compliant with the I-D, and finding and fixing (thankfully small)
> payload format errors in the process.
>
> 	I estimate sometime in September new normative and guideline
> I-Ds would be ready that reflect these changes.  I would anticipate a
> release of those I-Ds, followed by WG discussion, and if there are no
> outstanding issues, a minor refresh that would be the Last Call I-Ds.
>
> 	This posting concerns I-D renaming.  I posted a request
> pre-Vienna for WG status for the non-normative coding guidelines I-D,
> and to my knowledge there were no objections.  This re-badging would
> also be a good time to rename the normative I-D, since its current
> name uses the now-obsolete "mwpp".
>
> 	So, I propose these names for the two WG Item I-Ds:
>
>           draft-ietf-avt-rtp-midi-format-00.txt
>           draft-ietf-avt-rtp-midi-guidelines-00.txt
>
> 	Any comments or concerns?  The goal would be to keep these two
> documents in lockstep throughout the remainder of the process.  If I
> understand the new procedures correctly, internet-drafts@ietf.org
> needs an official heads-up from the chairs for new WG Item I-D names,
> thus this early email on the topic.

There was a hum in Vienna to accept the guidelines draft, but decisions 
such as this need to be confirmed on the mailing list. Accordingly, I 
now wish to ask if there are any objections to accepting the guidelines 
draft as an AVT work item?

The payload format itself is already a work item, I see no problem with 
renaming the draft to reflect the new title.

-- 
Colin Perkins
http://csperkins.org/


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