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

Paul Kyzivat <> Sun, 18 October 2015 16:54 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id 779BD1A90B4 for <>; Sun, 18 Oct 2015 09:54:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.235
X-Spam-Status: No, score=-1.235 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_SOFTFAIL=0.665] autolearn=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id txzWvZs-7n3Y for <>; Sun, 18 Oct 2015 09:54:33 -0700 (PDT)
Received: from ( [IPv6:2001:558:fe21:29:69:252:207:40]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 9A8501A90B1 for <>; Sun, 18 Oct 2015 09:54:33 -0700 (PDT)
Received: from ([]) by with comcast id WguY1r00927uzMh01guYn1; Sun, 18 Oct 2015 16:54:32 +0000
Received: from Paul-Kyzivats-MacBook-Pro.local ([]) by with comcast id WguY1r0063Ge9ey01guYBg; Sun, 18 Oct 2015 16:54:32 +0000
To: Christer Holmberg <>, "" <>
References: <> <> <> <> <> <> <> <> <> <> <> <> <> <>
From: Paul Kyzivat <>
Message-ID: <>
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: <>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 7bit
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=q20140121; t=1445187272; bh=tQuPxNrP6SFOH9efyfL1r7AsLeebKJHBy/cG8YMY4cY=; h=Received:Received:Subject:To:From:Message-ID:Date:MIME-Version: Content-Type; b=EW7RcURWpUNiwXhkR8S9oH5EovbzvuzJUeUQx5sr/i29vXdBFWeHM0KY6/HIKNnvm q7S6VciqXKYfCnIvdOEtoR9CEYBIumVdx4LNKtrTaJ/BNukYXi54dFTYUav+weYNbM ipo27taSPED4QoH2v7uFKVlhgcw4b3myjdHPFHapy0u1B4qDKnmefCaNPSkRxIBpVZ wZilHUJiBTV7z2x8fryGwPWnOp6CQnN7y40NH1q2GE5ywUhs7elSzpxYq3KU34LWV7 QFq6HB1szWJ7Nd5NOXEmNu9B+d2L6Cy3jzdozrkr1KRvRfERW3M0Zvk9QzPFUOEc4a bMYXwONelzvfw==
Archived-At: <>
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
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Sun, 18 Oct 2015 16:54:34 -0000

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.