Re: [rtcweb] Scope of SDP m= line 'webrtc-datachannel'

Flemming Andreasen <fandreas@cisco.com> Mon, 22 April 2019 19:08 UTC

Return-Path: <fandreas@cisco.com>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0AE3B1200E9; Mon, 22 Apr 2019 12:08:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.501
X-Spam-Level:
X-Spam-Status: No, score=-14.501 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
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 HR7_rZsc34eR; Mon, 22 Apr 2019 12:08:37 -0700 (PDT)
Received: from rcdn-iport-3.cisco.com (rcdn-iport-3.cisco.com [173.37.86.74]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C6B27120128; Mon, 22 Apr 2019 12:08:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=9058; q=dns/txt; s=iport; t=1555960116; x=1557169716; h=subject:to:references:from:message-id:date:mime-version: in-reply-to; bh=XwFz4oM/tofrRj/Prz2as/Ru8X9Jw+3imBVIlDcxuk0=; b=mGy0SjlIbllWhGjdRKGJS4kJNggTm5RI5ne2tz1mLPv55EP6HC1PwmwC wdRxyt/8qBw9PjSVL+o3lQY8lWb97AtPRQMuLwJ6NhVlnP6PPZNTnpUhq MRt1wBsEGyZVmFtbW0V6hKM6cAqa0a5O3jVdUzpXc+Cpl5UHgtijkugIV k=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0BVAADQEL5c/5xdJa1mGwEBAQEDAQE?= =?us-ascii?q?BBwMBAQGBVAMBAQELAYEOgQJoUTMohA6TKIFgLYlIiQmHdRAYAQqEBEYChiM?= =?us-ascii?q?jNwYOAQMBAQQBAQIBAm0cDIVLAQEBAwEBIUsbCQIYKgICJzAGAQwGAgEBgx4?= =?us-ascii?q?BgXQUD4s9m2WBLx+FKIRdBoEyAYtJF4FAP4ERJ4JrPoJhAQGEa4JXBKZWCYI?= =?us-ascii?q?Khg+MFQYbgguGKYNBiR+IeoMKgR6FH44mgWUiKIEuTSMVO4JshX2FFIVbIwM?= =?us-ascii?q?wkHIBAQ?=
X-IronPort-AV: E=Sophos;i="5.60,382,1549929600"; d="scan'208,217";a="539064283"
Received: from rcdn-core-5.cisco.com ([173.37.93.156]) by rcdn-iport-3.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 22 Apr 2019 19:08:35 +0000
Received: from [10.118.10.21] (rtp-fandreas-2-8814.cisco.com [10.118.10.21]) by rcdn-core-5.cisco.com (8.15.2/8.15.2) with ESMTP id x3MJ8YHK006499; Mon, 22 Apr 2019 19:08:34 GMT
To: Christer Holmberg <christer.holmberg@ericsson.com>, "mmusic@ietf.org" <mmusic@ietf.org>, "rtcweb@ietf.org" <rtcweb@ietf.org>, "clue@ietf.org" <clue@ietf.org>
References: <D591F3E7-EBC8-4844-A0FA-6ED64DD2B5F6@ericsson.com>
From: Flemming Andreasen <fandreas@cisco.com>
Message-ID: <62f7a5fe-a78e-4c80-cc96-e73b18c12629@cisco.com>
Date: Mon, 22 Apr 2019 15:08:34 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:60.0) Gecko/20100101 Thunderbird/60.6.1
MIME-Version: 1.0
In-Reply-To: <D591F3E7-EBC8-4844-A0FA-6ED64DD2B5F6@ericsson.com>
Content-Type: multipart/alternative; boundary="------------CD0390048F45B55C26CA224E"
Content-Language: en-US
X-Outbound-SMTP-Client: 10.118.10.21, rtp-fandreas-2-8814.cisco.com
X-Outbound-Node: rcdn-core-5.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtcweb/c8Rdg9uU-WVLBwKkeBUkC1I8ipU>
Subject: Re: [rtcweb] Scope of SDP m= line 'webrtc-datachannel'
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Real-Time Communication in WEB-browsers working group list <rtcweb.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rtcweb/>
List-Post: <mailto:rtcweb@ietf.org>
List-Help: <mailto:rtcweb-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Apr 2019 19:08:39 -0000

Folks

Please take a look at the proposed update below and let the authors and 
MMUSIC chairs know if you have any concerns with this change (by April 29).

Thanks

-- Flemming (as MMUSIC co-chair)

On 4/21/19 7:12 PM, Christer Holmberg wrote:
>
> Hi,
>
> I am cross-posting this on multiple list, to make people aware of the 
> issue. However, I ask that any comments and discussions take place on 
> the MMUSIC list only.
>
> I found the following statement in section 4.5 of 
> draft-ietf-mmusic-sctp-sdp:
>
>    “NOTE: 'webrtc-datachannel' indicates the WebRTC Data Channel
>
>    Establishment Protocol defined in [I-D.ietf-rtcweb-data-protocol].”
>
> In addition, in the IANA registration of ‘webrtc-datachannel’ (section 
> 15.3), draft-ietf-rtcweb-data-protocol is referenced.
>
> To refresh everyone, draft-ietf-rtcweb-data-protocol defines DCEP (the 
> inband protocol for handling WebRTC Data Channels), and 
> ‘webrtc-datachannel’ is used in the SDP m= line when establishing an 
> SCTP association for such channel.
>
> However, both draft-ietf-mmusic-datachannel-sdp-neg and 
> draft-ietf-clue-data-channel use ‘webrtc-datachannel’ in the “m=” 
> line, and those drafts do not use DCEP.
>
> My suggestion to fix this is to modify the text in 
> draft-ietf-mmusic-sctp-sdp, to always use ‘webrtc-datachannel’ for 
> WebRTC Data Channels – no matter whether DCEP is used or not.
>
> I have created a pull request:
>
> https://github.com/cdh4u/draft-sctp-sdp/pull/15
>
> Regards,
>
> Christer
>
>
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb