Re: [AVT] I-D ACTION:draft-ietf-avt-rfc2190-to-historic-01.txt

Colin Perkins <csp@csperkins.org> Sat, 29 January 2005 20:13 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 PAA09182 for <avt-archive@ietf.org>; Sat, 29 Jan 2005 15:13:46 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CuzG9-000301-TJ for avt-archive@ietf.org; Sat, 29 Jan 2005 15:31:59 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Cuyx1-0005J5-4D; Sat, 29 Jan 2005 15:12:11 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CuywV-00053p-7w for avt@megatron.ietf.org; Sat, 29 Jan 2005 15:11:39 -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 PAA08943 for <avt@ietf.org>; Sat, 29 Jan 2005 15:11:37 -0500 (EST)
Received: from mr1.dcs.gla.ac.uk ([130.209.249.184]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CuzE6-0002wd-EV for avt@ietf.org; Sat, 29 Jan 2005 15:29:50 -0500
Received: from csperkins-dsl.demon.co.uk ([80.176.225.173]:61084 helo=[192.168.0.2]) by mr1.dcs.gla.ac.uk with esmtpsa (TLSv1:RC4-SHA:128) (Exim 4.42) id 1Cuyvr-0003nq-Ja for avt@ietf.org; Sat, 29 Jan 2005 20:10:59 +0000
Mime-Version: 1.0 (Apple Message framework v619.2)
In-Reply-To: <200501272053.PAA23419@ietf.org>
References: <200501272053.PAA23419@ietf.org>
Content-Type: text/plain; charset="US-ASCII"; delsp="yes"; format="flowed"
Message-Id: <82db989d88222d8b84ad70a0870659b5@csperkins.org>
Content-Transfer-Encoding: 7bit
From: Colin Perkins <csp@csperkins.org>
Subject: Re: [AVT] I-D ACTION:draft-ietf-avt-rfc2190-to-historic-01.txt
Date: Sat, 29 Jan 2005 20:10:55 +0000
To: IETF AVT WG <avt@ietf.org>
X-Mailer: Apple Mail (2.619.2)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 82c9bddb247d9ba4471160a9a865a5f3
Content-Transfer-Encoding: 7bit
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: 02ec665d00de228c50c93ed6b5e4fc1a
Content-Transfer-Encoding: 7bit

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