[AVT] Re: Q about draft-ietf-avt-rtp-new

Stephen Casner <casner@acm.org> Tue, 01 July 2003 17:47 UTC

Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA08059 for <avt-archive@odin.ietf.org>; Tue, 1 Jul 2003 13:47:43 -0400 (EDT)
Received: (from exim@localhost) by www1.ietf.org (8.11.6/8.11.6) id h5RIMuh21310 for avt-archive@odin.ietf.org; Fri, 27 Jun 2003 14:22:56 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19VxrK-0004ik-OA; Fri, 27 Jun 2003 14:22:06 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19VnLt-00006b-FC for avt@optimus.ietf.org; Fri, 27 Jun 2003 03:09:32 -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 DAA19697 for <avt@ietf.org>; Fri, 27 Jun 2003 03:08:54 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19VnLp-0001vZ-00 for avt@ietf.org; Fri, 27 Jun 2003 03:08:53 -0400
Received: from www.routeexplorer.com ([65.192.41.10] helo=mailman.packetdesign.com) by ietf-mx with esmtp (Exim 4.12) id 19VnLe-0001vC-00 for avt@ietf.org; Fri, 27 Jun 2003 03:08:42 -0400
Received: from packetdesign.com (main-fw-eth1.packetdesign.com [192.168.0.254]) by mailman.packetdesign.com (8.12.8/8.12.8) with ESMTP id h5R77bFl055740; Fri, 27 Jun 2003 00:07:37 -0700 (PDT) (envelope-from casner@acm.org)
Date: Fri, 27 Jun 2003 00:10:33 -0700
From: Stephen Casner <casner@acm.org>
To: Oren Peleg <OrenP@audiocodes.com>
cc: avt@ietf.org
In-Reply-To: <BF10CC312C7A9C4FA2988BE360BAE44D338C67@lodmsg01.corp.audiocodes.com>
Message-ID: <20030627000758.R92361-100000@oak.packetdesign.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"
Subject: [AVT] Re: Q about draft-ietf-avt-rtp-new
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>

On Thu, 26 Jun 2003, Oren Peleg wrote:

> Is this draft a potential RFC? or its like the avt-profile &
> avt-profile-new which one is the update of the other that is subject
> to future updates as well & therefore will never become an RFC.

Both draft-ietf-avt-rtp-new and draft-ietf-avt-profile-new are in the
final stage of editing with the RFC Editor (actually the "authors's 48
hours", i.e., the ball is in my court) and will be published as RFC's
soon.

I'm not sure where you got the idea that profile-new would never
become an RFC, other than the fact that the process has taken quite a
long time.

                                                        -- Steve


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