Re: [MMUSIC] SDPNEG: How to disable DCEP

Paul Kyzivat <pkyzivat@alum.mit.edu> Sun, 28 April 2019 15:55 UTC

Return-Path: <pkyzivat@alum.mit.edu>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6C787120161 for <mmusic@ietfa.amsl.com>; Sun, 28 Apr 2019 08:55:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=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 oGCSjBSiANVm for <mmusic@ietfa.amsl.com>; Sun, 28 Apr 2019 08:55:51 -0700 (PDT)
Received: from outgoing-alum.mit.edu (outgoing-alum.mit.edu [18.7.68.33]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3C61C1200DB for <mmusic@ietf.org>; Sun, 28 Apr 2019 08:55:50 -0700 (PDT)
Received: from PaulKyzivatsMBP.localdomain (c-24-62-227-142.hsd1.ma.comcast.net [24.62.227.142]) (authenticated bits=0) (User authenticated as pkyzivat@ALUM.MIT.EDU) by outgoing-alum.mit.edu (8.14.7/8.12.4) with ESMTP id x3SFsgpY029966 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Sun, 28 Apr 2019 11:54:42 -0400
To: Christer Holmberg <christer.holmberg@ericsson.com>, "Roni Even (A)" <roni.even@huawei.com>, "mmusic@ietf.org" <mmusic@ietf.org>
References: <8A9AAAC7-FB2D-4884-BAC6-268B98C7A0F0@ericsson.com> <eba7d468-a2a3-8c5f-c2b0-fa515fb2e55c@alum.mit.edu> <81169C37-95F2-418A-A221-CCC623392CD2@ericsson.com> <563cf2bd-474a-8fef-ceaf-e2c72ebc6dc4@alum.mit.edu> <6E58094ECC8D8344914996DAD28F1CCD18CDE434@dggemm526-mbx.china.huawei.com> <A3797048-4BD3-46ED-8231-3C90F52C89BC@ericsson.com>
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
Message-ID: <32fb1138-4bc1-6315-0c2f-d660ecfafdcd@alum.mit.edu>
Date: Sun, 28 Apr 2019 11:54:41 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:60.0) Gecko/20100101 Thunderbird/60.6.1
MIME-Version: 1.0
In-Reply-To: <A3797048-4BD3-46ED-8231-3C90F52C89BC@ericsson.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/uOL_QpRfnPq5IVR2g5Mj4IOuKgc>
Subject: Re: [MMUSIC] SDPNEG: How to disable DCEP
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.29
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: Sun, 28 Apr 2019 15:55:54 -0000

Christer,

You seem to be suggesting that using dcmap is mutually exclusive with 
using DCEP to negotiate channels. While I guess it would be possible to 
make such a rule I don't see why it is necessary, or a good thing. Why 
not allow them to be used together? (E.g., use SDP to establish the SCTP 
association and negotiate some initial channels, and later use DCEP to 
negotiate some additional channels.)

	Thanks,
	Paul

On 4/28/19 7:57 AM, Christer Holmberg wrote:
> Hi,
> 
>> I think that sections 6.3 and 6.4 that discuss offer/answer say that dcmap is the indication of ruing non dcep.
> 
> Section 6.3 and 6.4 describe how to use dcmap.
> 
> I think it would be useful to e.g., have an Applicability section in the beginning of the document, that explicitly indicates that the procedures in the document apply when a data channel is negotiated using the dcmap attribute, and that DCEP is then not used.
> 
> But, what if an offerer wants to negotiate a data channel, before deciding what exactly it is going to be used for, but still wants to indicate usage of SDPNEG. Including an empty dcmap attribute?
> 
>>     The example in section 7 say that if dcmap is rejected dcep may be negotiated.
>>     Maybe this line form section 7 should be in section 6.4?
> 
> Normative text should definitely not be in Section 7.
> 
> However, if the answerer does not want to use SDPNEG, I think it's up to the offerer to decide whether to continue the session establishment, or fallback to DCEP.
> 
> Regards,
> 
> Christer
> 
> 
> 
>      
>      -----Original Message-----
>      From: mmusic [mailto:mmusic-bounces@ietf.org] On Behalf Of Paul Kyzivat
>      Sent: Friday, April 26, 2019 6:16 PM
>      To: Christer Holmberg; mmusic@ietf.org
>      Subject: Re: [MMUSIC] SDPNEG: How to disable DCEP
>      
>      On 4/26/19 5:37 AM, Christer Holmberg wrote:
>      > Hi Paul,
>      >
>      > So, what is your suggestion? __
>      
>      It looks to me like the 2nd paragraph of Appendix A is the right place for this:
>      
>          A WebRTC application creates a data channel by providing a number of
>          setup parameters (subprotocol, label, maximal number of
>          retransmissions, maximal retransmission time, order of delivery,
>          priority).  The application also specifies if it wants to make use of
>          the negotiation using the DCEP [I-D.ietf-rtcweb-data-protocol], or if
>          the application intends to negotiate data channels using the SDP
>          offer/answer protocol.
>      
>      I'm inclined to tweak the above as follows:
>      
>          ...
>          the application intends to negotiate data channels using the SDP
>          offer/answer protocol, or both.
>      
>      And then, the note at the end of the section can be augmented:
>      
>          Note: The above SDP media description does not contain any channel-
>          specific information. If data channels are to be negotiated using
>          SDP, then the above will be supplemented as specified in Sections
>          6.3 and 6.4.
>      
>      But I'm not sure about "The application also specifies...". Is this referring to something specific in the webrtc API? If so, does it permit both? The presence of dcmap in the SDP will indicate the intent to use SDP negotiation, but must this first be enabled in the API?
>      
>      	Thanks,
>      	Paul
>      
>      > Regards,
>      >
>      > Christer
>      >
>      > On 25/04/2019, 1.25, "mmusic on behalf of Paul Kyzivat" <mmusic-bounces@ietf.org on behalf of pkyzivat@alum.mit.edu> wrote:
>      >
>      >      The distribution of specs across multiple documents makes it really
>      >      fuzzy what is normative for what.
>      >
>      >      Perhaps something should be said about the validity of using a
>      >      webrtc-datachannel media stream for establishing data channels via SDP
>      >      with dcmap and/or DCEP. I don't think this is said anywhere else.
>      
>      _______________________________________________
>      mmusic mailing list
>      mmusic@ietf.org
>      https://www.ietf.org/mailman/listinfo/mmusic
>      
>