RE: [AVT] I-D ACTION:draft-ietf-avt-rfc2190-to-historic-01.txt
"Even, Roni" <roni.even@polycom.co.il> Sun, 30 January 2005 13:41 UTC
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA00913 for <avt-archive@ietf.org>; Sun, 30 Jan 2005 08:41:55 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CvFcf-0001Wm-TB for avt-archive@ietf.org; Sun, 30 Jan 2005 09:00:18 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CvFHk-0005MZ-4c; Sun, 30 Jan 2005 08:38:40 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CvFGv-0005FF-Lu for avt@megatron.ietf.org; Sun, 30 Jan 2005 08:37:49 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA00548 for <avt@ietf.org>; Sun, 30 Jan 2005 08:37:47 -0500 (EST)
Received: from bzq-179-41-2.cust.bezeqint.net ([212.179.41.2] helo=isrexch01.israel.polycom.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CvFYd-0001Qp-Rz for avt@ietf.org; Sun, 30 Jan 2005 08:56:09 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [AVT] I-D ACTION:draft-ietf-avt-rfc2190-to-historic-01.txt
Date: Sun, 30 Jan 2005 15:37:58 +0200
Message-ID: <144ED8561CE90C41A3E5908EDECE315CE8B92F@IsrExch01.israel.polycom.com>
Thread-Topic: [AVT] I-D ACTION:draft-ietf-avt-rfc2190-to-historic-01.txt
Thread-Index: AcUGP0hFt6DQO8tcSryQb2OnomJ7cAAjze5g
From: "Even, Roni" <roni.even@polycom.co.il>
To: Colin Perkins <csp@csperkins.org>, IETF AVT WG <avt@ietf.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d185fa790257f526fedfd5d01ed9c976
Content-Transfer-Encoding: quoted-printable
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
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>
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c3a18ef96977fc9bcc21a621cbf1174b
Content-Transfer-Encoding: quoted-printable
Colin, Thanks for the comments. In section 4 do I need to have the full text of the MIME type registration from RFC3555 since the payload type I suggest moving to historic is called H263 Roni -----Original Message----- From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf Of Colin Perkins Sent: Saturday, January 29, 2005 10:11 PM To: IETF AVT WG Subject: Re: [AVT] I-D ACTION:draft-ietf-avt-rfc2190-to-historic-01.txt I have a few (mostly editorial) comments on this draft: - The 2nd paragraph of the introduction says "Implementations using the new features of the 1998 version of H.263 shall use the format described in this document", however the draft doesn't define a format. I assume this is a cut-and-paste error; please fix - The 3rd paragraph of the introduction explains that RFC 2429 is being revised to deprecate RFC 2190. Since RFC 2429 will be made obsolete by the new draft, it might be better for this draft to reference 2429bis, being published at the same time as 2429bis? - Also in the 3rd paragraph of the introduction, change "MUST" to "must" since this document doesn't make that normative statement (RFC2429bis does). You may then be able to remove section 2 entirely. - Section 4 notes to move the H263 payload type to historic status. What is the exact MIME type to be listed as historic? - Section 5: can you expand on the security considerations? Perhaps by explaining where one can find discussion of the security of the payload format, and why this change has no impact? Cheers, Colin On 27 Jan 2005, at 20:53, Internet-Drafts@ietf.org wrote: > A New Internet-Draft is available from the on-line Internet-Drafts > directories. > This draft is a work item of the Audio/Video Transport Working Group > of the IETF. > > Title : RTP Payload Format for H.263 using RFC2190 to Historic status > Author(s) : R. Even > Filename : draft-ietf-avt-rfc2190-to-historic-01.txt > Pages : 8 > Date : 2005-1-27 > > The first RFC that describes RTP payload format for H.263 is RFC2190. > This specification discusses why to move this RFC to historic status. > > A URL for this Internet-Draft is: > http://www.ietf.org/internet-drafts/draft-ietf-avt-rfc2190-to- > historic-01.txt _______________________________________________ Audio/Video Transport Working Group avt@ietf.org https://www1.ietf.org/mailman/listinfo/avt _______________________________________________ Audio/Video Transport Working Group avt@ietf.org https://www1.ietf.org/mailman/listinfo/avt
- [AVT] I-D ACTION:draft-ietf-avt-rfc2190-to-histor… Internet-Drafts
- [AVT] I-D ACTION:draft-ietf-avt-rfc2190-to-histor… philippe.gentric
- Re: [AVT] I-D ACTION:draft-ietf-avt-rfc2190-to-hi… Colin Perkins
- RE: [AVT] I-D ACTION:draft-ietf-avt-rfc2190-to-hi… Even, Roni
- Re: [AVT] I-D ACTION:draft-ietf-avt-rfc2190-to-hi… Colin Perkins