Re: [AVT] Inquiry about RFC 4629 (optional parameters in SDP)
Carsten Bormann <cabo@tzi.org> Wed, 05 September 2007 08:12 UTC
Return-path: <avt-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1ISq0J-0004l3-S2; Wed, 05 Sep 2007 04:12:51 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1ISq0I-0004g4-EN for avt@ietf.org; Wed, 05 Sep 2007 04:12:50 -0400
Received: from mailhost.informatik.uni-bremen.de ([2001:638:708:30c9:209:3dff:fe00:7136] helo=informatik.uni-bremen.de) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ISq0G-0003UX-SM for avt@ietf.org; Wed, 05 Sep 2007 04:12:50 -0400
Received: from [127.0.0.1] (maildrop [134.102.201.19]) by informatik.uni-bremen.de (8.14.0/8.14.0) with ESMTP id l858CeHf013584; Wed, 5 Sep 2007 10:12:40 +0200 (CEST)
In-Reply-To: <ybu642pda28.fsf@jesup.eng.wgate.com>
References: <144ED8561CE90C41A3E5908EDECE315C04DE8345@IsrExch01.israel.polycom.com> <ybu642pda28.fsf@jesup.eng.wgate.com>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset="US-ASCII"; delsp="yes"; format="flowed"
Message-Id: <B056ACFC-5DC3-4B65-BEDF-09A1E710DC09@tzi.org>
Content-Transfer-Encoding: 7bit
From: Carsten Bormann <cabo@tzi.org>
Subject: Re: [AVT] Inquiry about RFC 4629 (optional parameters in SDP)
Date: Wed, 05 Sep 2007 10:12:36 +0200
To: Randell Jesup <rjesup@wgate.com>
X-Mailer: Apple Mail (2.752.3)
X-Virus-Scanned: by amavisd-new
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7d33c50f3756db14428398e2bdedd581
Cc: Carsten Bormann <cabo@tzi.org>, "Even, Roni" <roni.even@polycom.co.il>, avt@ietf.org, Regis Crinon <regisc@exchange.microsoft.com>
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>
Errors-To: avt-bounces@ietf.org
On Sep 05 2007, at 06:13, Randell Jesup wrote: > but I'm not clear about "for a standard you > must have only parameters that are used" and how exactly it applies > here. I think the point is that 2429 (4629's predecessor) has been around for a while, and apparently there was no need for the other Annexes, at least as perceived by the WG. 4629 might actually even be the basis for going to Draft Standard, where there is indeed a requirement to only have options for which independent interoperable implementations can be demonstrated. As a general observation about the grim reality, codec "standards" generally carry lots of baggage that is motivated by company X wanting to get their random patents in, too. You don't really want to weigh down real-world standards by all that _a__age. So, in a way, 2429/4629 are "profiling" H.263 for Internet work. Gruesse, Carsten _______________________________________________ Audio/Video Transport Working Group avt@ietf.org https://www1.ietf.org/mailman/listinfo/avt
- [AVT] Inquiry about RFC 4629 (optional parameters… Regis Crinon
- RE: [AVT] Inquiry about RFC 4629 (optional parame… Even, Roni
- Re: [AVT] Inquiry about RFC 4629 (optional parame… Randell Jesup
- RE: [AVT] Inquiry about RFC 4629 (optional parame… Even, Roni
- Re: [AVT] Inquiry about RFC 4629 (optional parame… Randell Jesup
- Re: [AVT] Inquiry about RFC 4629 (optional parame… Carsten Bormann