To: Christer Holmberg <christer.holmberg@ericsson.com>,
 "mmusic@ietf.org" <mmusic@ietf.org>
References: <786615F3A85DF44AA2A76164A71FE1ACDF796695@FR711WXCHMBA01.zeu.alcatel-lucent.com>
 <56202783.3010300@cisco.com>
 <7594FB04B1934943A5C02806D1A2204B37B45C83@ESESSMB209.ericsson.se>
 <786615F3A85DF44AA2A76164A71FE1ACDF79D867@FR711WXCHMBA01.zeu.alcatel-lucent.com>
 <7594FB04B1934943A5C02806D1A2204B37B45FDB@ESESSMB209.ericsson.se>
 <56213DD9.8080308@alum.mit.edu>
 <7594FB04B1934943A5C02806D1A2204B37B46EA0@ESESSMB209.ericsson.se>
 <5621596C.3070706@alum.mit.edu> <56215EA6.2010503@omnitor.se>
 <CA+9kkMApRrks_aMbKTzZideXM=Y-W+tqEhWCSmJXzT+TrsE8Sw@mail.gmail.com>
 <56217878.4000009@omnitor.se>
 <CA+9kkMAr+QZxOowrxmGtjVX=MC1j8zR_Y4-EJECiPX_3t5_b8g@mail.gmail.com>
 <56226AB8.9060002@alum.mit.edu>
 <7594FB04B1934943A5C02806D1A2204B37B6469E@ESESSMB209.ericsson.se>
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
Message-ID: <5623CEC7.2010905@alum.mit.edu>
Date: Sun, 18 Oct 2015 12:54:31 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:38.0)
 Gecko/20100101 Thunderbird/38.3.0
MIME-Version: 1.0
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B37B6469E@ESESSMB209.ericsson.se>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/A0Lr9svUE8F3el4H6RjsxwVkG0M>
Subject: Re: [MMUSIC] WG adoption of other WebRTC data channel usage drafts?; 
 Re: New Version Notification for
 draft-ietf-mmusic-msrp-usage-data-channel-02.txt
Precedence: list

On 10/18/15 8:44 AM, Christer Holmberg wrote:
> Hi,
>
> ...
>
>> So I think what is needed is to register a protocol name for T.140 (or for RTT). While no spec is required to register the
>> name, one is needed to specify the semantics of the messages sent in that protocol. If it follows T.140 then it might
>> be a very simple document.
>
> For T.140 a specification makes sense, in order to ensure interoperability.
>
> But, what if company wants to use the data channel for a protocol related to a game? In order to avoid name collisions it would be good for them to register the name, but I don't think they would want to reveal the details of the game protocol.

Well, the registry exists, and is FCFS. Each registry entry contains a 
reference to a document. So there needs to be *something* to reference. 
I haven't investigated if there is any requirement on what it contains. 
And I don't think there are any police that check up on whether the 
referenced document continues to exist.

So, if you want to register a secret protocol you can probably do so.

	Thanks,
	Paul