Re: [MMUSIC] WGLC for draft-ietf-mmusic-data-channel-sdpneg

Paul Kyzivat <> Fri, 12 February 2016 16:59 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id C84F11A7000 for <>; Fri, 12 Feb 2016 08:59:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -0.035
X-Spam-Status: No, score=-0.035 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, J_CHICKENPOX_14=0.6, J_CHICKENPOX_15=0.6, SPF_SOFTFAIL=0.665] autolearn=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id sj9SxHiM1ea7 for <>; Fri, 12 Feb 2016 08:58:59 -0800 (PST)
Received: from ( [IPv6:2001:558:fe21:29:69:252:207:42]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 679E01A6FFA for <>; Fri, 12 Feb 2016 08:58:59 -0800 (PST)
Received: from ([]) by with comcast id HUya1s0062Ka2Q501UyyM9; Fri, 12 Feb 2016 16:58:58 +0000
Received: from Paul-Kyzivats-MacBook-Pro.local ([]) by with comcast id HUyx1s00h3KdFy101Uyy7A; Fri, 12 Feb 2016 16:58:58 +0000
To: Juergen Stoetzer-Bradler <>, Flemming Andreasen <>,, "DRAGE, Keith (Keith)" <>, "Makaraju, Maridi Raju (Raju)" <>
References: <> <> <> <> <> <> <> <> <> <> <> <> <> <> <> <> <> <> <> <> <> <> <> <> <>
From: Paul Kyzivat <>
Message-ID: <>
Date: Fri, 12 Feb 2016 11:58:57 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:38.0) Gecko/20100101 Thunderbird/38.5.1
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=1455296338; bh=zVYVk2sYDd1sl3B07bm7uNsZCr3WV1pAGkgtM7zkwok=; h=Received:Received:Subject:To:From:Message-ID:Date:MIME-Version: Content-Type; b=R0RN/7cxmTyTh9ctumPOoGGVk/w86VWxz+LEI6oixgc0bY0xMq/hx/1btgirIxqI9 2ntKgAjvgwTrZGvwQqIqNcuPHTxqHZWIBqNICpqJSPg3Nrh7z3LKXip7YNEK8tm7hk q+LTs1XeJ1CizQPuCRex4Md5PXl5dsSzGT9WcMAkRKYdym62NF9IEjAgk4p2ohN7PH 849i7fBhM2ou8GxFqnQ52SWV/ZO2htWRzOky4KdEBJQ6XckcqnJv8ur5GqH5DOQaYD lk8BvVteoZCcyz+V9r+oJOt8TWXXURIY36MBnCde7UWd74Lukzv83aD/DBtUKeBa6g rAuzPjtlp6zQw==
Archived-At: <>
Subject: Re: [MMUSIC] WGLC for draft-ietf-mmusic-data-channel-sdpneg
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: Fri, 12 Feb 2016 16:59:01 -0000


You bring up a point that perhaps needs further discussion: what does it 
mean when the subprotocol is not specified?

IIUC there are at least a couple of reasons this might come about:

1) The protocol to be used is not standardized. There is no globally 
unique name for it. The two ends know what protocol to use based on context.

2) The protocol to be used on the channel is not determined via SDP 
negotiation. The applications want to establish the channel, and then 
dynamically decide what protocol to use with it. (And that protocol may 
change over time.)

I guess that it still might be meaningful to use dcsa with (1), but 
there would be no way to determine by examination of the SDP whether the 
usage was compatible with the protocol. In this case the usage of the 
attributes would be "off label" - being adapted to the proprietary 
protocol in a way that hopefully the two ends agree.

I don't see how dcsa makes much sense for (2). If you don't know what 
protocol will be used then how do you know what attributes to use?


On 2/12/16 5:45 AM, Juergen Stoetzer-Bradler wrote:
> Flemming, Paul,
> The current a=dcmap related text in
> draft-ietf-mmusic-data-channel-sdpneg doesn't require that the
> 'subprotocol' parameter must always be present - rather it is specified
> as an optional parameter. Thus, current sdpneg text would allow to
> create an SDP offer for a data channel, which contains one a=dcmap
> attribute and potentially multiple a=dcsa attributes without the
> subprotocol actually being given. Based on this discussion I am
> wondering if the subprotocol parameter should actually be mandatory.
> In the specific case of MSRP, the msrp-usage-data-channel draft says in
> that the dcmap attribute includes the label and subprotocol
> parameters. The current text could possible be made more explicit by
> saying that the 'subprotocol="MSRP"' parameter must always be present.
> Have just submitted version 04 of the msrp-usage-data-channel draft,
> which proposes to add subprotocol identifier "MSRP" to the WebSocket
> Subprotocol Name registry. This registry would then associate
> subprotocol id "MSRP" with the msrp-usage-data-channel document.
> There, in section the MSRP specific usages of the a=dcsa
> attribute are specified. And there the MSRP specific SDP attributes,
> which can be dcsa embedded, are described.
> 'setup' is an attribute, whose semantic changes when being dcsa embedded
> and associated with subprotocol MSRP, as compared to the meaning of an
> "a=setup" media level attribute of a TCP/MSRP m-line. Hence these
> semantical differences are explicitly addressed in the
> msrp-usage-data-channel draft.
> Regarding sdpneg, I also think that the current text in sdpneg seems to
> be sufficient regarding the usage of dcsa encapsulated SDP attributes as
> being bound to the data channel's subprotocol.  But as the semantic of a
> dcsa encapsulated attribute may be subprotocol specific (like 'setup'),
> I'd now tend to consider the subprotocol parameter in the dcmap
> attribute as being mandatory, as mentioned above. As already discussed,
> the Websocket subprotocol registry would then refer to the document,
> which specifies the subprotocol specific usage of dcsa encapsulated
> parameters.
> Thanks,
> Juergen
> On 11.02.2016 21:52, Flemming Andreasen wrote:
>> On 2/8/16 12:09 PM, Paul Kyzivat wrote:
>>> On 2/8/16 11:09 AM, Flemming Andreasen wrote:
>>>> On 2/6/16 1:44 PM, Paul Kyzivat wrote:
>>>>> On 2/4/16 10:43 PM, Christian Groves wrote:
>>>>>> Isn't this the approach we're taking today?
>>>>>> draft-ietf-mmusic-data-channel-sdpneg has general text and specific
>>>>>> drafts are used to describe protocols that use the mechanism (i.e.
>>>>>> draft-ietf-mmusic-msrp-usage-data-channel &
>>>>>> draft-ietf-clue-datachannel).
>>>>> It remains to be seen if that will be enough. E.g., there currently
>>>>> aren't any iana considerations in
>>>>> draft-ietf-mmusic-msrp-usage-data-channel.
>>>>> Suppose I encounter some sdp that uses msrp over a data channel, but
>>>>> that usage is unknown to me. How do I find the spec (the reference to
>>>>> draft-ietf-mmusic-msrp-usage-data-channel) that defines that usage?
>>>>> I would like to think that the iana registries will allow me to trace
>>>>> back to the relevant specs.
>>>> No disagreement on that part, however having taken another look at both
>>>> sdpneg and the msrp-usage documents, I still don't agree with your
>>>> original request for all (existing and new) attributes to specify how
>>>> they may or may not be used with the dcsa attribute defined by sdpneg.
>>>> As Christian noted, the sub-protocol specifics are defined in
>>>> individual
>>>> documents (like msrp-usage), which calls your the parameters that
>>>> are at
>>>> least needed to be supported for that usage. Taking MSRP as an example,
>>>> why isn't that enough, and how do you see the resulting set of
>>>> attributes that may or may not be used with MSRP differ between use
>>>> in a
>>>> data-channel (and hence encapsulated in dcsa) or as a regular media
>>>> stream ?
>>> Based on this discussion, I conclude that it should be sufficient for
>>> this draft to say that before an attribute can be used with dcsa,
>>> such usage must be defined somewhere. This could be either:
>>> - as part of the definition of the attribute, OR
>>> - as part of the definition of the protocol referenced on the m-line.
>> We are getting closer, but it's still not obvious to me that you
>> cannot use an attribute with dcsa if it has not been explicitly
>> defined for the attribute in question. Clearly, there are attributes
>> that wouldn't make sense over data channels, just like there are
>> attributes that don't make sense over particular media descriptions.
>> Again, I'd like to hear from more people on this, including the authors.
>> Thanks
>> -- Flemming
>>>     Thanks,
>>>     Paul
>>>> Also, it would be good to hear from more people on this, including the
>>>> document authors.
>>>> Thanks
>>>> -- Flemming
>>>>>     Thanks,
>>>>>     Paul
>>>>>> Regards, Christian
>>>>>> On 4/02/2016 3:58 PM, Paul Kyzivat wrote:
>>>>>>> On 2/3/16 5:42 PM, Flemming Andreasen wrote:
>>>>>>>> I'm not concerned about the IANA part. I agree that *if* we need to
>>>>>>>> expliclty specify attribute interactions for "dcsa", then it
>>>>>>>> should be
>>>>>>>> part of the IANA registry. What I am not agreeing with at this
>>>>>>>> point is
>>>>>>>> that there is indeed a need to explicitly speficy these
>>>>>>>> interactions as
>>>>>>>> opposed to relying on a more general algorithmic approach (plus the
>>>>>>>> offerer being responsible for generating a valid offer if he
>>>>>>>> wants to
>>>>>>>> establish a data channel).
>>>>>>> Well, an obvious one is that the protocol(s) the attribute
>>>>>>> pertains to
>>>>>>> need to be defined to work over data channels.
>>>>>>>     Thanks,
>>>>>>>     Paul
>>>>>>> _______________________________________________
>>>>>>> mmusic mailing list
>>>>>> _______________________________________________
>>>>>> mmusic mailing list
>>>>> _______________________________________________
>>>>> mmusic mailing list
>>>>> .
>>> _______________________________________________
>>> mmusic mailing list
>>> .