Re: [MMUSIC] T140: Usage of "-"fmt value in dcsa encapsulated fmtp attribute

Christer Holmberg <christer.holmberg@ericsson.com> Fri, 13 December 2019 11:50 UTC

Return-Path: <christer.holmberg@ericsson.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 12A351208BB; Fri, 13 Dec 2019 03:50:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level:
X-Spam-Status: No, score=-2.001 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, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ericsson.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 GetYjEgQemxF; Fri, 13 Dec 2019 03:50:40 -0800 (PST)
Received: from EUR04-DB3-obe.outbound.protection.outlook.com (mail-eopbgr60062.outbound.protection.outlook.com [40.107.6.62]) (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 83AF0120845; Fri, 13 Dec 2019 03:50:40 -0800 (PST)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=NtS+CBUX3EK/3ECNKSz61cMJdFqhYjRZ6hvWxBSKIuJwqsZBZ94vNBCkxJJRx4bGUoFEetBScWiD63sNiMlrVqTReXN0+YLsYrIqK9vzNNSk4eQSK7ZAaAGhTsJjkGcVmLz9E6TgqxRg6i7u9Jp3tXt8PRZUbhMt2+ktm2o56QJ8449JkIvikdyD+71yiEQiiWdvrvr3j6LQ6SRscWuNPH2G45f475FQ/NZ4CYrQ2gJtBMMrpx08YF0XKDoDumOUzwWKyiKtoutabsx04Oo+uP/L8QqdaMqNdNF3nvfU6oUqwkln/Qt7GHEpG90w19XxdfVFInFQ6U3hei1YNj3MBA==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=uMMbqRi3lCk2SvCl6KW2U7VYgH4yoxKMVe/vuFGVMKc=; b=l/7NBDIciqb6QZFhNldrVKTwQYcRA68t1OVX9bhEmJHQSGAHorwC/7mTKl4N4gZCx3wNzUdTaeuKow0BlMZEXIIu0/HeRAURoLNEMvK3nowl1EIQUB/HsWL7eYimC58hkctllAX8vPrIz3jJ8p+ZOta/e0C6bsoMI9/70OgJEMSzU8BSB16J0YcPSdmh+CzXDv98GkKFkroWzjsLy/UqgJdH5YIzBvgZ2OmuwIC+uw4sq6EXwEaiWbyp7nMUBpX02z+a65NL3/7cAEZUKWoqqMdDiN6ihfyKvl3tMO9zuZ4MsKm1diZttU1kDkbsz80PRuW3eWanY8beUKs6qHMXyQ==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=ericsson.com; dmarc=pass action=none header.from=ericsson.com; dkim=pass header.d=ericsson.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ericsson.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=uMMbqRi3lCk2SvCl6KW2U7VYgH4yoxKMVe/vuFGVMKc=; b=LvxNUWKeoHt0iqpMpHheIOy2nHdS2tKA7qPW0Bk8q3BcpgaYT/An1uJbav+ogl0wHjifJbzD+LhoENc1tIbcaCDfmvSUgTkzSCs3f1BDSGmNIZZtJ+bhJH6bUr3vx6SGJ1z2VEHjTPzcFbNS7T5CGMij37r2mgFQd4ojxc6b1jk=
Received: from DB6PR0701MB2421.eurprd07.prod.outlook.com (10.168.73.16) by DB6PR0701MB2311.eurprd07.prod.outlook.com (10.168.74.10) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2538.6; Fri, 13 Dec 2019 11:50:38 +0000
Received: from DB6PR0701MB2421.eurprd07.prod.outlook.com ([fe80::39bd:a590:dcd9:201e]) by DB6PR0701MB2421.eurprd07.prod.outlook.com ([fe80::39bd:a590:dcd9:201e%10]) with mapi id 15.20.2538.017; Fri, 13 Dec 2019 11:50:38 +0000
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Gunnar Hellström <gunnar.hellstrom@omnitor.se>, Christer Holmberg <christer.holmberg=40ericsson.com@dmarc.ietf.org>, "mmusic (mmusic@ietf.org)" <mmusic@ietf.org>, "mmusic-chairs@ietf.org" <mmusic-chairs@ietf.org>
Thread-Topic: [MMUSIC] T140: Usage of "-"fmt value in dcsa encapsulated fmtp attribute
Thread-Index: AQHVsR/lwYXoivuBwkKJ+MACi8tNi6e36BcAgAAuQAA=
Date: Fri, 13 Dec 2019 11:50:38 +0000
Message-ID: <5FF684F2-955E-4E52-AED5-69D9EA8D39F5@ericsson.com>
References: <DB6PR0701MB24219718E7408022DB6F256493550@DB6PR0701MB2421.eurprd07.prod.outlook.com> <1b757fea-b5ce-c498-8100-cb54a4a431fa@omnitor.se>
In-Reply-To: <1b757fea-b5ce-c498-8100-cb54a4a431fa@omnitor.se>
Accept-Language: en-US
Content-Language: en-GB
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/10.1e.0.191013
authentication-results: spf=none (sender IP is ) smtp.mailfrom=christer.holmberg@ericsson.com;
x-originating-ip: [2001:14b8:1829:11:ac6f:23b1:739f:922]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: e1117d25-80dc-47f9-9ece-08d77fc2ac10
x-ms-traffictypediagnostic: DB6PR0701MB2311:
x-microsoft-antispam-prvs: <DB6PR0701MB231105DF464800D72C3D461193540@DB6PR0701MB2311.eurprd07.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-forefront-prvs: 0250B840C1
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(4636009)(396003)(136003)(366004)(376002)(346002)(39860400002)(189003)(199004)(44832011)(66574012)(2906002)(2616005)(110136005)(6506007)(6512007)(8936002)(81166006)(36756003)(316002)(81156014)(8676002)(76116006)(478600001)(6486002)(186003)(71200400001)(966005)(4001150100001)(66556008)(64756008)(91956017)(66446008)(66946007)(5660300002)(33656002)(86362001)(66476007); DIR:OUT; SFP:1101; SCL:1; SRVR:DB6PR0701MB2311; H:DB6PR0701MB2421.eurprd07.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1;
received-spf: None (protection.outlook.com: ericsson.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: kaF6Xm+prFX5FwJ4ws4Ve5hjBX5TwWJF5KTLKCEw22aA1hcwJRqe7dndaJzgLdPwdh9GDLzShXXp5aOzU4D9+C0JOl7qYXMpG8HHh/10QWCIqUbqOnkc/9bELwIIMD+c1a1WJA2J/lvyyFatmpR9US0Lfwpj5Pp7G5CCdXxHRcBVDtv+uhAzAPTbD185SXfcGEsBrvtuMsklslEtB/PWjvRRNQIBiig9CjvLYd1a7l5FNRF+0UOLQS9GIZU48AasWxwXk03MFkrxq0enPciJmP1HGMn7e/kjOBhO+U6ehtrlftLgf7yqLe40l5JuS6foJYSO7ZOFxqZENJZsXvPkupfN3IJEfDvoEclWK6Y1WEcwnU6nxR/viF2jrMI47oxR98Ga4t2vfPuL+I9hfo998rxdlzXvLzSfSBSR4YSBRH7kWQCMAEG8gtan0s1AnT0YMXMyb+ThXanXI+2Jh0RQlPg8iGg2gyBBThH166TEHIg=
x-ms-exchange-transport-forked: True
Content-Type: text/plain; charset="utf-8"
Content-ID: <E0F9C8D837E74E4BA2C2FD72DA797BF3@eurprd07.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: ericsson.com
X-MS-Exchange-CrossTenant-Network-Message-Id: e1117d25-80dc-47f9-9ece-08d77fc2ac10
X-MS-Exchange-CrossTenant-originalarrivaltime: 13 Dec 2019 11:50:38.1618 (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-CrossTenant-userprincipalname: sGQpNRXuLBEWahKLFBGwG5w575lkQ8LzTVpwg9szi3jUPx4BXote9bXAQfraHqFL6s43pgjJqUjZIIR4k2NLR33JWu2E1XoABc6GR1s0RY0=
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DB6PR0701MB2311
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/06q6yCvdy_4VMSVti7jk3RZxOMo>
Subject: Re: [MMUSIC] T140: Usage of "-"fmt value in dcsa encapsulated fmtp attribute
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, 13 Dec 2019 11:50:46 -0000

Hi,

It seems to me that the solution for the "fmt" value definition might be found in sdpneg

>In sdpneg section 5.2.1
>https://tools.ietf.org/html/draft-ietf-mmusic-data-channel-sdpneg-28#section-5.2.1
>It is said:
> "There may be cases, where the usage of a subprotocol related media
>   level attribute depends on the subprotocol's transport protocol.  In
>   such cases the subprotocol related usage of the attribute is expected
>   to be described for the data channel transport.  A data channel
>   specific usage of a subprotocol attribute is expected to be specified
>   in the same document that registers the subprotocol's identifier for
>   data channel usage as described in https://tools.ietf.org/html/draft-ietf-mmusic-data-channel-sdpneg-28#section-9.1. "
>
>In t140-usage, section4.2.1, 
>https://tools.ietf.org/html/draft-ietf-mmusic-t140-usage-data-channel-10#section-4.2.1
>we have this sentence:
>   'If the 'fmtp' attribute is included, the 'format' attribute parameter MUST be set to "-". '

The text above is what triggered the discussion :)

>It seems to me that the t140-usage draft by that fulfills the requirements of sdpneg and we are fine with fmt=-
>Maybe we could even say that for the t.140-data-channel, "fmt" MUST be ommitted, in order to get a simpler syntax (?).
>
>However,
>
>This issue may also relate to the definition of "fmt" in rfc4566bis
> https://tools.ietf.org/html/draft-ietf-mmusic-rfc4566bis-37#section-8.2.3
>where we have the following sentences that seem to apply:
>"For other protocols, formats MAY be registered according to the rules
>   of the associated "proto" specification.
>
>   Registrations of new formats MUST specify which transport protocols
>   they apply to."
>
> I have not traced if we are bound to that requirement for dcsa definitions, and how it would map from protocol to sub-protocol, so I hope we can obey sdpneg.
>
> Summary: I would suggest to omit "fmt", or keep fmt=- and claim that the use of fmt is defined in t140-usage as required by sdpneg.

We DO define the usage as required by sdpneg,  so that is not the issue. 

The question is whether it in such definition is allowed to "override" the 4566bis statement saying that the format must be one of the formats specified for the media. As far as SDP is concerned, the only format is 'webrtc-datachannel'.

Again, I personally think we should keep "-" (I don't like to omit information elements), and add whatever text needed to indicate that the 4566bis text does not apply to sub-protocol specific fmtp attributes.

Regards,

Christer







Den 2019-12-12 kl. 20:12, skrev Christer Holmberg:
Hi,

When the chairs reviewed the T.140 data channel usage draft, the following issue was raised:

Currently, when we send an fmtp attribute encapsulated in a dcsa attribute, we use "-" as the fmt value.

     Example: a=dcsa:2 fmtp:- cps=20

However, 4566bis says the following about the fmtp attribute:

"The format must be one of the formats specified for the media."

Now, the format is 'webrtc-datachannel', so one could claim that should be used.

     Example: a=dcsa:2 fmtp:webrtc-datachannel cps=20


 But, that applies to the whole SCTP association, and the dcsa attribute is associated with a specific data channel usage. In addition, the usage and syntax of the fmtp attribute may vary depending on data channel usage.

Another option could be to include the sub-protocol:

     Example: a=dcsa:2 fmtp:t140 cps=20


But, the dcsa attribute already maps the fmtp attribute to the sub-protocol.


So, what to do?


My personal suggestion would be to keep "-", and perhaps add a note somewhere. Not sure we would need to update 4566bis, but if people want to do that we could for sure do it. 

Anyone having a different opinion?


Regards,


Christer




_______________________________________________
mmusic mailing list
mailto:mmusic@ietf.org
https://www.ietf.org/mailman/listinfo/mmusic
-- 

+ + + + + + + + + + + + + + 

Gunnar Hellström
Omnitor
mailto:gunnar.hellstrom@omnitor.se
+46 708 204 288