Re: [MMUSIC] Data channel dcsa attribute usage and IANA

Paul Kyzivat <pkyzivat@alum.mit.edu> Thu, 29 August 2019 15:49 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 1E20F120918 for <mmusic@ietfa.amsl.com>; Thu, 29 Aug 2019 08:49:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HI7B2RV_e_EO for <mmusic@ietfa.amsl.com>; Thu, 29 Aug 2019 08:49:14 -0700 (PDT)
Received: from outgoing-alum.mit.edu (outgoing-alum.mit.edu [18.7.68.33]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8C3D7120902 for <mmusic@ietf.org>; Thu, 29 Aug 2019 08:49:14 -0700 (PDT)
Received: from Kokiri.localdomain (c-24-62-227-142.hsd1.ma.comcast.net [24.62.227.142]) (authenticated bits=0) (User authenticated as pkyzivat@ALUM.MIT.EDU) by outgoing-alum.mit.edu (8.14.7/8.12.4) with ESMTP id x7TFn9EX026239 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Thu, 29 Aug 2019 11:49:10 -0400
To: Christer Holmberg <christer.holmberg@ericsson.com>, "mmusic@ietf.org" <mmusic@ietf.org>
References: <FA58AC4B-B7CF-488A-A287-ACB14C9D9056@ericsson.com> <6E58094ECC8D8344914996DAD28F1CCD23D439E1@dggemm526-mbx.china.huawei.com> <e209505e-3ff6-7cd3-c3b6-7cfec897c98b@alum.mit.edu> <55E0F3DE-0789-485A-A973-BF9A6BDD3AE6@ericsson.com>
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
Message-ID: <c97a55a9-dd6e-13af-1a7d-4d08f5cb2007@alum.mit.edu>
Date: Thu, 29 Aug 2019 11:49:09 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:60.0) Gecko/20100101 Thunderbird/60.8.0
MIME-Version: 1.0
In-Reply-To: <55E0F3DE-0789-485A-A973-BF9A6BDD3AE6@ericsson.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/AsTw1m_1kzHsOYoPFle2PIQWVvg>
Subject: Re: [MMUSIC] Data channel dcsa attribute usage and IANA
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.29
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: <https://mailarchive.ietf.org/arch/browse/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: Thu, 29 Aug 2019 15:49:16 -0000

On 8/29/19 10:20 AM, Christer Holmberg wrote:
> Hi,
> 
>>> I think that dcsa(subprotocol) would have been enough, at least based on
>>> channel-sdpneg document, maybe Paul can help
>>     
>>     I'm sorry that this is coming up so late. In retrospect I think it
>>     deserved more discussion about how this is to work. IIRC this got tucked
>>     in quite some time ago, early in the definition of dcsa.
>>     
>>     I don't recall why both forms are shown. I don't know what "dcsa" alone
>>     would mean. The guess it could be a wildcard meaning that it can be used
>>     with all subprotocols. But that doesn't make any sense to me.
>    
> I was also first thinking whether dcsa without subprotocol it was some kind of "wildcard", but there is no such thing defined in data-channel-sdpneg: each subprotocol will have to define register its usage of attributes inside dcsa.
> 
>>     So I'm inclined to only use the "dcsa(subprotocol)" form. Perhaps we
>>     should file an errata against rfc4566bis as soon as it becomes an RFC.
>    
> Isn't this a fix that the RFC Editor can be requested to do? There is no reason to bring the draft back to the WG etc.
> 
> After all, this is not a technical change, only an administrative.

Yes, I think so.

I was just now reviewing IANA changes for 4566bis, and asked them to 
change "dcsa, dcsa(setup)" to "dcsa(setup)".

	Thanks,
	Paul