Re: [MMUSIC] [AVTCORE] WGLC on draft-ietf-avtcore-clksrc-03

Paul Kyzivat <pkyzivat@alum.mit.edu> Tue, 11 June 2013 14:59 UTC

Return-Path: <pkyzivat@alum.mit.edu>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0FED221F8D79 for <mmusic@ietfa.amsl.com>; Tue, 11 Jun 2013 07:59:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.238
X-Spam-Level:
X-Spam-Status: No, score=-0.238 tagged_above=-999 required=5 tests=[AWL=-0.157, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_NET=0.611, RDNS_NONE=0.1, SARE_SUB_6CONS_WORD=0.356]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xU7CtQd1v-Cl for <mmusic@ietfa.amsl.com>; Tue, 11 Jun 2013 07:59:44 -0700 (PDT)
Received: from qmta03.westchester.pa.mail.comcast.net (qmta03.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:43:76:96:62:32]) by ietfa.amsl.com (Postfix) with ESMTP id 9282921F8C20 for <mmusic@ietf.org>; Tue, 11 Jun 2013 07:59:43 -0700 (PDT)
Received: from omta18.westchester.pa.mail.comcast.net ([76.96.62.90]) by qmta03.westchester.pa.mail.comcast.net with comcast id n1LP1l0041wpRvQ532ziiZ; Tue, 11 Jun 2013 14:59:42 +0000
Received: from Paul-Kyzivats-MacBook-Pro.local ([50.138.229.164]) by omta18.westchester.pa.mail.comcast.net with comcast id n2zi1l00n3ZTu2S3e2zin4; Tue, 11 Jun 2013 14:59:42 +0000
Message-ID: <51B73B5D.6010704@alum.mit.edu>
Date: Tue, 11 Jun 2013 10:59:41 -0400
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: mmusic@ietf.org
References: <014401ce3e5a$f28208b0$d7861a10$@gmail.com> <C49313CD-DBFA-42D7-9623-EA44AAF59C25@csperkins.org> <CALw1_Q36fLC4O=EF9JbREvriqSc4GGYk-chv79P76C3Y3NtS7g@mail.gmail.com>
In-Reply-To: <CALw1_Q36fLC4O=EF9JbREvriqSc4GGYk-chv79P76C3Y3NtS7g@mail.gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20121106; t=1370962782; bh=ofDMmvOnnU3jSGoAf2TnyudRCnuCzSE24Sd2ddW5F94=; h=Received:Received:Message-ID:Date:From:MIME-Version:To:Subject: Content-Type; b=TafceGYZchuH+yLrSbxt1i4dznpG8UcJTudg3UiYefprH0DMrmk+P8Sxe3KhAU3Bz xHk3tG/0TAG3ASSU8NwaJa8g9pdZMsivaRK9JaC5D84+Uedb8ptzMg1LJxpF872PbI SGJkFgis+tdSmEaXXvrUIhXiRe5wpk5y5VDTjonbMveoEdS5ZegNj7Gljwmp6RACTK VSwLTXl6KCxoOVC52uT20g/rLu3Tpo29iGiP91O/Q1+Ka7WyEFHuUq/H/UhepGnNsu Laca98n/B5TtacZ56YGRqP4+LqC4MsXfP36Kj+BU1gKWcJOTN14huFoFiguLkgEVk+ 3aQ3hyKJEhM8w==
Subject: Re: [MMUSIC] [AVTCORE] WGLC on draft-ietf-avtcore-clksrc-03
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.12
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: Tue, 11 Jun 2013 14:59:48 -0000

On 6/11/13 9:30 AM, Kevin Gross wrote:
> I've read section 12.2 of RFC 5576 and it is unclear to me whether a
> properly-registered attribute also requires a separate registration to
> be used as a source-level attribute. I gather there's some uncertainty
> on Colin's part. Can anyone help clarify these requirements for us?

IMO this is a bit of a mess. We can ask the authors what they intended, 
but in the end it was a wg document, so maybe its up to the wg to 
decide. I'm also unclear whether the IANA registry structure that got 
built for this is exactly what was intended. IMO the collective IANA 
registry structures for registering SDP attributes is far from ideal.

As the registry is currently constructed there is definitely a need for 
a separate entry for source level attributes. Perhaps a single 
registration request can be for multiple entries - that comes down to 
details of what a "request" is.

IMO the registry should be restructured, so that there is a single table 
for all SDP attributes, with a column indicating in which context(s) it 
may be used: session level, media level, and/or source level. If that 
were so, then a single registration could define as many of those as 
made sense for an attribute.

	Thanks,
	Paul

> Kevin Gross
> +1-303-447-0517
> Media Network Consultant
> AVA Networks - www.AVAnw.com <http://www.avanw.com/>, www.X192.org
> <http://www.X192.org>
>
>
> On Fri, May 3, 2013 at 10:26 AM, Colin Perkins <csp@csperkins.org
> <mailto:csp@csperkins.org>> wrote:
>
>     On 21 Apr 2013, at 07:39, Roni Even wrote:
>      > I would like to start a WGLC on
>     http://tools.ietf.org/html/draft-ietf-avtcore-clksrc-03  , RTP Clock
>     Source Signalling.
>      >
>      > The WGLC will end on May 12th , 2013
>      >
>      > Please review the draft and send comments to the list.
>
>     This generally looks good, and I had only one comment: if I'm
>     reading RFC 5576 correctly, this draft needs to include IANA
>     registrations for "att-field (source level)" for the SDP attributes,
>     to allow them to be used in the a=ssrc: lines. Making this change
>     will probably also requires changes to the ABNF, to cleanly separate
>     the syntax for "a=..." and "a=ssrc: ..." forms so they can be
>     separately referenced.
>
>     --
>     Colin Perkins
>     http://csperkins.org/
>
>
>
>
>
>
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www.ietf.org/mailman/listinfo/mmusic
>