Re: [MMUSIC] SDPNEG: How to disable DCEP

Christer Holmberg <> Sun, 28 April 2019 11:57 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 7AD87120105 for <>; Sun, 28 Apr 2019 04:57:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.003
X-Spam-Status: No, score=-2.003 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, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id bLQYS9DqsmDu for <>; Sun, 28 Apr 2019 04:57:48 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 8E8991200A1 for <>; Sun, 28 Apr 2019 04:57:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=IeE+YGep5hAA0haILRI4efeHFIah+GnXssel6VEX0/c=; b=jNeL9zzwVLAZVN2PecYgGTox6c2VHMSY5GbkkdBk5oJtbkIkvBdLRU3M8kCrYsTU+x+t2bvW2ZewfSeezaPnyDo7UJ2RmlXZuhjuQ1NQfDL2XxhaXaojcgn61tJsugkNm1d8DdTrAfyaZtSOFUW8jPNRsqhhp/so5zk+LLzmboA=
Received: from ( by ( with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1856.5; Sun, 28 Apr 2019 11:57:43 +0000
Received: from ([fe80::c999:f848:9abc:d321]) by ([fe80::c999:f848:9abc:d321%6]) with mapi id 15.20.1856.008; Sun, 28 Apr 2019 11:57:43 +0000
From: Christer Holmberg <>
To: "Roni Even (A)" <>, Paul Kyzivat <>, "" <>
Thread-Topic: [MMUSIC] SDPNEG: How to disable DCEP
Thread-Index: AQHU+njrOtTA5N+Kv0Ox965sWihq+KZL5CwAgAKAjYCAACw0AIACj2qAgACQLAA=
Date: Sun, 28 Apr 2019 11:57:43 +0000
Message-ID: <>
References: <> <> <> <> <>
In-Reply-To: <>
Accept-Language: en-US
Content-Language: en-US
user-agent: Microsoft-MacOutlook/
authentication-results: spf=none (sender IP is );
x-originating-ip: []
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: cf460266-d801-4bc2-912e-08d6cbd0b913
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600141)(711020)(4605104)(2017052603328)(7193020); SRVR:HE1PR07MB3148;
x-ms-traffictypediagnostic: HE1PR07MB3148:
x-ms-exchange-purlcount: 1
x-microsoft-antispam-prvs: <>
x-forefront-prvs: 0021920B5A
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(346002)(366004)(39860400002)(136003)(396003)(376002)(13464003)(51444003)(189003)(199004)(305945005)(2906002)(6116002)(7736002)(97736004)(14444005)(6436002)(256004)(3846002)(86362001)(2501003)(76176011)(44832011)(53546011)(446003)(6506007)(99286004)(476003)(102836004)(2616005)(11346002)(486006)(68736007)(186003)(6486002)(316002)(26005)(110136005)(58126008)(6246003)(2171002)(229853002)(71200400001)(71190400001)(93886005)(83716004)(82746002)(66066001)(8676002)(478600001)(76116006)(73956011)(36756003)(966005)(25786009)(81156014)(5660300002)(33656002)(14454004)(66556008)(64756008)(81166006)(6306002)(6512007)(66446008)(53936002)(66476007)(66946007)(8936002); DIR:OUT; SFP:1101; SCL:1; SRVR:HE1PR07MB3148;; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1;
received-spf: None ( does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: XWazSm6c5yPX0aj0wA4tglG5kuJw9qaVIbDd9/HryOxUyz45pRuWKZXSkizxp4j9IOLADqKqP4YGxMwG1G/XFWZZ5KAiWNQ2IeKKGNJg1GEIxafp1sNCru9edfB5IBxPi4WjyOAf8HmULXs6y6/kSECtYQ//ygveYIk+vXulDgZ8uaSnicVW2WoNjQLpnN3V+BlRGMu3iRNOL2Vg7nimhsl5nzl0arN6t1zmPVXY9EeiDtEYTCmv8++BlwLM57sxhPCMW6WvXKcut6Yy5pEc1kelTC7E/i3gB84Isrsn7U3Pv9vNW7OZHJJbgJCMKCSn2qO/rUyMW3uJHg9U2IyU+14KmEIAzmNFO4M5ZLcOhgvI1zA+0VZEhtE+9Ox/D9vqnNiWCiI85lOjvEFP7rYZpAmjdWxOb7r7AqpAFro1G+o=
Content-Type: text/plain; charset="utf-8"
Content-ID: <>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: cf460266-d801-4bc2-912e-08d6cbd0b913
X-MS-Exchange-CrossTenant-originalarrivaltime: 28 Apr 2019 11:57:43.6578 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 92e84ceb-fbfd-47ab-be52-080c6b87953f
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-Transport-CrossTenantHeadersStamped: HE1PR07MB3148
Archived-At: <>
Subject: Re: [MMUSIC] SDPNEG: How to disable DCEP
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Sun, 28 Apr 2019 11:57:51 -0000


> 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. 



    -----Original Message-----
    From: mmusic [] On Behalf Of Paul Kyzivat
    Sent: Friday, April 26, 2019 6:16 PM
    To: Christer Holmberg;
    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?
    > Regards,
    > Christer
    > On 25/04/2019, 1.25, "mmusic on behalf of Paul Kyzivat" < on behalf of> 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