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

Flemming Andreasen <fandreas@cisco.com> Tue, 08 March 2016 03:04 UTC

Return-Path: <fandreas@cisco.com>
X-Original-To: mmusic@ietfc.amsl.com
Delivered-To: mmusic@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id 522651CDA83 for <mmusic@ietfc.amsl.com>; Mon, 7 Mar 2016 19:04:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.522
X-Spam-Level:
X-Spam-Status: No, score=-14.522 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfc.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
Received: from mail.ietf.org ([4.31.198.41]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id a8Ko2WVkQMCe for <mmusic@ietfc.amsl.com>; Mon, 7 Mar 2016 19:04:07 -0800 (PST)
Received: from rcdn-iport-5.cisco.com (rcdn-iport-5.cisco.com [173.37.86.76]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfc.amsl.com (Postfix) with ESMTPS id 9D0CD1CDA7A for <mmusic@ietf.org>; Mon, 7 Mar 2016 19:04:05 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1530; q=dns/txt; s=iport; t=1457406245; x=1458615845; h=subject:to:references:from:message-id:date:mime-version: in-reply-to:content-transfer-encoding; bh=SfS0joJeMjti28TbMVyW8e8k8wc8yFA4ZOE4BrT7OfU=; b=j/Q3hqEIgoIEZ0KhZm/T1q5vdfY7s4MLDgH+cTfhhzGQ6/uw5aNP7r8o 4nfP8Mw3mmcO+XedDkTwbRsGZVBXUzNtOheXWrungl9IEUbHyO8LPBLQN 7/6nx89Bhs1/Ig4iNt/Pkg5PGafaXBZDpX7Vd+VydD89MfqImCasczgdH o=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0AAAgCAQN5W/5JdJa1cgzpSbbg1ghMBD?= =?us-ascii?q?YFpIYVuAoE1OBQBAQEBAQEBZCeEQQEBAQMBOEAGCwsYCRYPCQMCAQIBRQYBDAg?= =?us-ascii?q?BAQWIEwgOvkUBAQEBAQEBAQEBAQEBAQEBARmGF4Q9iHQBBI4kiQaNbokphVGOV?= =?us-ascii?q?R4BAUKEAh4uAYl+AQEB?=
X-IronPort-AV: E=Sophos;i="5.22,554,1449532800"; d="scan'208";a="80643299"
Received: from rcdn-core-10.cisco.com ([173.37.93.146]) by rcdn-iport-5.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 08 Mar 2016 03:04:04 +0000
Received: from [10.98.149.198] (bxb-fandreas-8815.cisco.com [10.98.149.198]) by rcdn-core-10.cisco.com (8.14.5/8.14.5) with ESMTP id u28343qh011127; Tue, 8 Mar 2016 03:04:04 GMT
To: Christian Groves <Christian.Groves@nteczone.com>, Juergen Stoetzer-Bradler <juergen.stoetzer-bradler@nokia.com>, "mmusic@ietf.org" <mmusic@ietf.org>
References: <BBE9739C2C302046BD34B42713A1E2A22E88D533@ESESSMB105.ericsson.se> <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> <56BCF47E.2000603@cisco.com> <56BDB7BC.1060104@alcatel-lucent.com> <56BDF1C6.9080707@cisco.com> <56C05B63.4030007@alcatel-lucent.com> <56C6156C.2070308@cisco.com> <56C71EF3.6040208@alcatel-lucent.com> <56C74FDE.4040902@cisco.com> <56CC5E9B.5060307@alcatel-lucent.com> <56D61704.70205@cisco.com> <56D84051.4080303@alcatel-lucent.com> <56D84FB7.4050109@cisco.com> <56DCC592.2060503@nteczone.com>
From: Flemming Andreasen <fandreas@cisco.com>
Message-ID: <56DE4123.3030606@cisco.com>
Date: Mon, 7 Mar 2016 22:04:03 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:38.0) Gecko/20100101 Thunderbird/38.6.0
MIME-Version: 1.0
In-Reply-To: <56DCC592.2060503@nteczone.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/andMYDUBgbQ4aFozW_fKNCmVuRA>
Subject: Re: [MMUSIC] WGLC for draft-ietf-mmusic-data-channel-sdpneg
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
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: Tue, 08 Mar 2016 03:04:08 -0000


On 3/6/16 7:04 PM, Christian Groves wrote:
> Hello Flemming and Juergen,
>
> ..snip..
>>> I agree that in such cases such new attributes could indeed be added 
>>> to corresponding data channel subprotocol specific attribute 
>>> registries, which then could refer to the document introducing this 
>>> new attribute.
>> Right - and for consistency I think it then makes sense to have all 
>> subprotocol-specific attributes registered there.
>>
>>> An alternative might be to only add such a new SDP attribute to the 
>>> generic IANA SDP attribute registry (which probably would be done 
>>> anyhow). I assume that the generic SDP attribute registry would also 
>>> refer to the document introducing this new attribute.
>>>
>> Either would work, however my preference would be a complete listing 
>> of attributes that have subprotocol specific meaning.
>>
>> I'd be interested in what other people think though
>
> From looking at the existing IANA registry 
> http://www.iana.org/assignments/sdp-parameters/sdp-parameters.xhtml
>
> It feels like we should take the approach for att-field (source level) 
> and define att-field (data channel).
>
Thanks for the feedback Christian. Just to be clear: We would need to 
allow for multiple entries per attribute, since different sub-protocols 
could each define sub-protocol specific behavior for an attribute.

Thanks

-- Flemming


> Regards, Christian
>
>>
>>
>> Thanks
>>
>> -- Flemming (with my individual hat on)
>>
>
> .
>