Re: [MMUSIC] T.140 in Data Channel scenarios - SDP support- the pull request

Bernard Aboba <bernard.aboba@gmail.com> Fri, 27 September 2019 11:03 UTC

Return-Path: <bernard.aboba@gmail.com>
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 2E10B1200B7 for <mmusic@ietfa.amsl.com>; Fri, 27 Sep 2019 04:03:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.996
X-Spam-Level:
X-Spam-Status: No, score=-1.996 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 jyqfDQfvITxd for <mmusic@ietfa.amsl.com>; Fri, 27 Sep 2019 04:03:20 -0700 (PDT)
Received: from mail-pf1-x430.google.com (mail-pf1-x430.google.com [IPv6:2607:f8b0:4864:20::430]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EF46D12004F for <mmusic@ietf.org>; Fri, 27 Sep 2019 04:03:19 -0700 (PDT)
Received: by mail-pf1-x430.google.com with SMTP id v4so1383405pff.6 for <mmusic@ietf.org>; Fri, 27 Sep 2019 04:03:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=content-transfer-encoding:from:mime-version:subject:date:message-id :references:cc:in-reply-to:to; bh=lIHbD0H5cl6mSU9usuFtyAO/Yj6bmVSpdnYJvPGUH2w=; b=NgUEoKUUJQVx6wziESKIUPF8XimrI930A3UalKKQk4LmUKSmX8KxpU1PCu13q7lY+R 87bYOVUaMwxi1QMhraYMuaIdXxSvM39ODFcr5b16Gx1kCI3N0Emhyxd19Dpehnzk2EqT KZNkDPFz8xxkd6nyk6EpszLJqmmp7DZpH0dS4Pt1eD+MombcLd3g+vQEwa6agutxlzmA OxZEtxggpVu/JGRmZYkOkb/SfHldbJ4bbXDFiaU35qE/sC0GuZm0qIF+tmKUikiJ3vYX 31Vz8x6ckB2PFcFUWlEIIXVNyMYdvuj2Xxz4ZtSM6gzcNgQzxHjM55jGGHfwJ3lRS0v3 Nyxg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:content-transfer-encoding:from:mime-version :subject:date:message-id:references:cc:in-reply-to:to; bh=lIHbD0H5cl6mSU9usuFtyAO/Yj6bmVSpdnYJvPGUH2w=; b=kXMlnyvIbbbi+wAZO6/tQGbrARJsNP5Wylf0M4VcTlRT+2RJc2JrtcYcCirL/2YJu2 sRbYFZ/j102YUz/hsXkDwLXcdjPGuiay9WQU5DBl8t3JMGaEOV5iq3YQRhSPvtNk9j8w Q9Q+GwW2U4C8fL7kqyCjCknvEeInn1VT9w1Kr0C+lhqyrIdh1eWK/2hjNV56+vhM97e+ 3K5fjmZn9EMSqWQVyeKTbh3UyT6ylkVhvspUMFJTe53wt0Oxi1BE5FYDEfUBC2fhTTN3 YejASa8LCNOdnRJzrkjqqQNIaQzo4ACMO9AfDKpWppNkwfQHSPg0NvlVG9me/Gyg5oRp YAZA==
X-Gm-Message-State: APjAAAXaLWvZzRyEldExtutQTng2dADfLQ4xYuTspxM8RAKCtoKVj2cj GM/V3OZian7vT4UBFJbTtH4=
X-Google-Smtp-Source: APXvYqw7fUUZjog/b5XcNYtv32HgsX15eM1SChAMf4+XPtN267SlF0vPZcwvcazXFs5dF2z9ThbotA==
X-Received: by 2002:a62:5a85:: with SMTP id o127mr3624831pfb.212.1569582198979; Fri, 27 Sep 2019 04:03:18 -0700 (PDT)
Received: from [192.168.1.107] (c-71-227-236-207.hsd1.wa.comcast.net. [71.227.236.207]) by smtp.gmail.com with ESMTPSA id f6sm4133554pga.50.2019.09.27.04.03.18 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Fri, 27 Sep 2019 04:03:18 -0700 (PDT)
Content-Type: multipart/alternative; boundary="Apple-Mail-F1991D84-610D-4D8C-AC4B-AD7EBD051973"
Content-Transfer-Encoding: 7bit
From: Bernard Aboba <bernard.aboba@gmail.com>
Mime-Version: 1.0 (1.0)
Date: Fri, 27 Sep 2019 04:03:17 -0700
Message-Id: <F02A157E-8D2D-45F5-A21D-204BCEADD6CD@gmail.com>
References: <667F39A8-C0DD-45E5-B48C-D57A6FAB87C0@ericsson.com>
Cc: Gunnar Hellström <gunnar.hellstrom@omnitor.se>, mmusic WG <mmusic@ietf.org>
In-Reply-To: <667F39A8-C0DD-45E5-B48C-D57A6FAB87C0@ericsson.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>
X-Mailer: iPhone Mail (17A844)
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/xaIR75QTtGvTpvYMIuRIkZSgEM8>
Subject: Re: [MMUSIC] T.140 in Data Channel scenarios - SDP support- the pull request
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: Fri, 27 Sep 2019 11:03:22 -0000

I do not understand the PR. 

> On Sep 27, 2019, at 2:41 AM, Christer Holmberg <christer.holmberg@ericsson.com> wrote:
> 
> 
> https://github.com/cdh4u/draft-datachannel-t140/pull/35
> 
> JSEP has a statement in section 5.2.1  https://tools.ietf.org/html/draft-ietf-rtcweb-jsep-25#section-5.2.1 about creation of an offer for a data channel saying
> 
> "Attributes other than the ones specified above MAY be included"
> 
[BA] No existing browser generates the attributes defined in the draft in createOffer(). Since the SDP cannot be changed, that also means that if you pass the draft attributes to SLD/SRD these calls will fail.
> So, to me it seems that the API and JSEP together not really supports, but also not forbids use of additional attributes in data channel specifications.
> 
[BA] That is not correct. If you pass the draft attributes to SLD/SRD all browsers will fail.
> Therefore, the discussed note seems too strong
> 

The note is correct as written. What could be clarified is that if support for the attributes can be handled in the application, browser support is not required.