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

Paul Kyzivat <pkyzivat@alum.mit.edu> Mon, 08 February 2016 17:17 UTC

Return-Path: <pkyzivat@alum.mit.edu>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4F2111B2F64 for <mmusic@ietfa.amsl.com>; Mon, 8 Feb 2016 09:17:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.635
X-Spam-Level:
X-Spam-Status: No, score=-0.635 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, J_CHICKENPOX_14=0.6, SPF_SOFTFAIL=0.665] autolearn=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 Kc7BTbfE6hWA for <mmusic@ietfa.amsl.com>; Mon, 8 Feb 2016 09:17:41 -0800 (PST)
Received: from resqmta-ch2-02v.sys.comcast.net (resqmta-ch2-02v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:34]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D26321AD09B for <mmusic@ietf.org>; Mon, 8 Feb 2016 09:17:40 -0800 (PST)
Received: from resomta-ch2-01v.sys.comcast.net ([69.252.207.97]) by resqmta-ch2-02v.sys.comcast.net with comcast id FtGu1s00D26dK1R01tHgCy; Mon, 08 Feb 2016 17:17:40 +0000
Received: from Paul-Kyzivats-MacBook-Pro.local ([73.218.51.154]) by resomta-ch2-01v.sys.comcast.net with comcast id FtHf1s00N3KdFy101tHfa1; Mon, 08 Feb 2016 17:17:39 +0000
To: mmusic@ietf.org
References: <BBE9739C2C302046BD34B42713A1E2A22E88D533@ESESSMB105.ericsson.se> <565C6CE3.3050007@alum.mit.edu> <565CDF90.7050107@nteczone.com> <565CEA14.2040607@alum.mit.edu> <565CEF7B.7010305@nteczone.com> <949EF20990823C4C85C18D59AA11AD8BADE16A00@FR712WXCHMBA11.zeu.alcatel-lucent.com> <56682B96.9020008@alcatel-lucent.com> <56684C13.9030106@alum.mit.edu> <5668F9C1.4040606@nteczone.com> <566903E3.8020108@alum.mit.edu> <566A16D2.1070108@nteczone.com> <949EF20990823C4C85C18D59AA11AD8BADE22AB4@FR712WXCHMBA11.zeu.alcatel-lucent.com> <566AEB05.3040501@alum.mit.edu> <56AACC37.8090900@cisco.com> <56AB8596.9090304@alum.mit.edu> <56B12F48.409@cisco.com> <56B25159.70002@alum.mit.edu> <56B28240.7080206@cisco.com> <56B2DA8D.2000909@alum.mit.edu> <56B41A47.10901@nteczone.com> <56B63EF8.8080100@alum.mit.edu> <56B8BDA4.7060305@cisco.com> <56B8CBB5.7070507@alum.mit.edu>
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
Message-ID: <56B8CDB2.9080505@alum.mit.edu>
Date: Mon, 8 Feb 2016 12:17:38 -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: <56B8CBB5.7070507@alum.mit.edu>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1454951860; bh=WXIkevpoxNWDD5rVVUdy/hPvN87GP3X18frXEg16574=; h=Received:Received:Subject:To:From:Message-ID:Date:MIME-Version: Content-Type; b=cAspGHpppnYoD2CiMlvhTey4gi5BZ+LV9hunZcnihm0Th/ehvf+hNYrKT5SmC/iCO +oGLi/RKpRb+mBo9ub9Pm/1IVGYDQGUEKXXra8+oPVPfs8nbII/uYJqdpF+qi3IaXZ +LSYNLoalMihct8IiX1+sjsZ2cB+TdLPzDGhyGZTEaLJoUhp7n+tELpzRdPFeE0Sts jk7P5YvX8ekz3prZYtCJvFTOcAEOxLNt0ha2b+xgY2Yxgl8uhF+hGdykADLGAswv3V s6d48MOEf4f48INqokfoBQyJYOBWXAQOySCusyT4n5Jk0uLTTMnu3ZvSrZ9SDDHZO1 iePH1wyPUpMgg==
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/IsomMxvfj1iLjNgloDN2e_jQu4E>
Subject: Re: [MMUSIC] WGLC for draft-ietf-mmusic-data-channel-sdpneg
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.15
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: Mon, 08 Feb 2016 17:17:42 -0000

BTW, ISTM that whatever is decided here will apply equally to attributes 
used with a=ssrc.

	Thanks,
	Paul

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.
>
>      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@ietf.org
>>>>> https://www.ietf.org/mailman/listinfo/mmusic
>>>>>
>>>>
>>>> _______________________________________________
>>>> mmusic mailing list
>>>> mmusic@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/mmusic
>>>>
>>>
>>> _______________________________________________
>>> mmusic mailing list
>>> mmusic@ietf.org
>>> https://www.ietf.org/mailman/listinfo/mmusic
>>> .
>>>
>>
>>
>
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www.ietf.org/mailman/listinfo/mmusic
>