[AVT] Open issue on hdrext draft

Tom Taylor <tom.taylor@rogers.com> Thu, 04 October 2007 02:02 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 1IdG32-0001qA-Qx; Wed, 03 Oct 2007 22:02:44 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IdG31-0001V5-G4 for avt@ietf.org; Wed, 03 Oct 2007 22:02:43 -0400
Received: from smtp102.rog.mail.re2.yahoo.com ([206.190.36.80]) by chiedprmail1.ietf.org with smtp (Exim 4.43) id 1IdG2w-000732-36 for avt@ietf.org; Wed, 03 Oct 2007 22:02:38 -0400
Received: (qmail 15649 invoked from network); 4 Oct 2007 02:02:37 -0000
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=rogers.com; h=Received:X-YMail-OSG:Message-ID:Date:From:User-Agent:MIME-Version:To:CC:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding; b=bmPiux4HHXQnTCaakiVp00LXRzIfIMajhM+Gg+x2ZlG+1XK2ktAZpriX8Ri21PpF6c/CAXFHH6mPkiq1idOw3ZzpUteMKo2voUn3ncaxwjtxLEbtDRdVAzU1fywCNKQAhbl9vSPu4caNFf8EJpFgBLzzdpXLWMWSCVNSy62lnUE= ;
Received: from unknown (HELO ?192.168.0.100?) (tom.taylor@rogers.com@74.105.35.229 with plain) by smtp102.rog.mail.re2.yahoo.com with SMTP; 4 Oct 2007 02:02:37 -0000
X-YMail-OSG: Z5UMrpMVM1lR9wewWkCMZTz3fQ9qIWZmjcA_IjMG56OoI6HIXJOz1dndu79JIUWfaQ--
Message-ID: <470449BC.50603@rogers.com>
Date: Wed, 03 Oct 2007 22:02:36 -0400
From: Tom Taylor <tom.taylor@rogers.com>
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: IETF AVT WG <avt@ietf.org>
References: <p06240851c316f756a59b@[10.0.1.9]>
In-Reply-To: <p06240851c316f756a59b@[10.0.1.9]>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32
Cc: Cullen Jennings <fluffy@cisco.com>, avt-chairs@tools.ietf.org
Subject: [AVT] Open issue on hdrext draft
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

Before the header extension draft can be approved we have to settle two or three 
points that have been raised after the document passed WGLC. One of them is the 
view of the Working Group regarding registration requirements.

Is it the Working Group's intention that:

(a) any SDO can standardize and register a new RTP header extension without IETF
review or consent; or

(b) all RTP header extensions require review and agreement by an IETF expert
before they can be registered; or

(c) all RTP header extensions require IETF consensus before they can be registered.

David Singer had a clear view on this question when he wrote the document in the 
first place. I should let him speak for himself, but his basic idea was to 
encourage registration as an alternative to hard-to-get-rid-of experimental 
identifiers, by making registration a simple process. His preference was thus 
toward alternative (a).

Last time we didn't ask the question in quite these stark terms, and only Magnus 
replied. It's hard to read a consensus from that. Would other people care to 
comment?

Tom Taylor

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