Re: [MMUSIC] RFC 4856 is in the correct RFC category - Errata query? [was RE: Last Call: <draft-ietf-mmusic-sdp-g723-g729-04.txt> (Offer/Answer Considerations for G723 Annex A and G729 Annex B) to Proposed Standard]

Stephen Casner <casner@acm.org> Wed, 04 December 2013 04:46 UTC

Return-Path: <casner@acm.org>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CE43A1AE1C6 for <mmusic@ietfa.amsl.com>; Tue, 3 Dec 2013 20:46:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.235
X-Spam-Level:
X-Spam-Status: No, score=-1.235 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_SOFTFAIL=0.665] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FBgf3NRnr2cY for <mmusic@ietfa.amsl.com>; Tue, 3 Dec 2013 20:46:30 -0800 (PST)
Received: from mailman.packetdesign.com (firewall-gw-dirty-u.packetdesign.com [65.192.41.2]) by ietfa.amsl.com (Postfix) with ESMTP id C0CAB1AE1BB for <mmusic@ietf.org>; Tue, 3 Dec 2013 20:46:30 -0800 (PST)
Received: from packetdesign.com (vpn2-int.packetdesign.com [192.168.0.181]) by mailman.packetdesign.com (8.13.1/8.13.1) with ESMTP id rB44kJYI019528; Tue, 3 Dec 2013 20:46:19 -0800
Date: Tue, 03 Dec 2013 20:46:19 -0800
From: Stephen Casner <casner@acm.org>
To: SM <sm@resistor.net>
In-Reply-To: <6.2.5.6.2.20131203010105.0db5d630@resistor.net>
Message-ID: <alpine.OSX.1.10.1312032044050.62912@luft.gateway.2wire.net>
References: <20131030131748.6987.86198.idtracker@ietfa.amsl.com> <6.2.5.6.2.20131030185231.0ddfb7a8@resistor.net> <00a101ced981$77414d60$65c3e820$@co.in> <00ab01cee555$05f53560$11dfa020$@co.in> <6.2.5.6.2.20131119110213.0cb0dd40@resistor.net> <016b01ceed2f$0be29e90$23a7dbb0$@co.in> <alpine.OSX.1.10.1312020834220.60832@luft.gateway.2wire.net> <6.2.5.6.2.20131203010105.0db5d630@resistor.net>
User-Agent: Alpine 1.10 (OSX 962 2008-03-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"
Cc: Flemming Andreasen <fandreas@cisco.com>, Ari Kerdnen <ari.keranen@ericsson.com>, mmusic@ietf.org
Subject: Re: [MMUSIC] RFC 4856 is in the correct RFC category - Errata query? [was RE: Last Call: <draft-ietf-mmusic-sdp-g723-g729-04.txt> (Offer/Answer Considerations for G723 Annex A and G729 Annex B) to Proposed Standard]
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 04 Dec 2013 04:46:32 -0000

On Tue, 3 Dec 2013, SM wrote:

> Hi Stephen,
> At 08:52 02-12-2013, Stephen Casner wrote:
> > I believe the status of RFC 4856 is correct.  It updates RFC 3555 to
> > define and register the media types for the RTP profile RFC 3551.
> > What other status would be more appropriate for that ?
>
> There was an assumption that the status chosen for some previous RFC is
> correct.  The problem might have been with RFC 3555.  It is better not to look
> at the details of those old RFCs too closely. :-)

Since I am the author of the RFCs listed above, I dispute that.  I
assert that standards track is correct for all of these.  There is
nothing about them that is merely a "best current practice".

                                                        -- Steve