Re: [MMUSIC] AD Review: draft-ietf-mmusic-t140-usage-data-channel - the updated pull request
Christer Holmberg <christer.holmberg@ericsson.com> Mon, 27 January 2020 12:55 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 AC37512008D for <mmusic@ietfa.amsl.com>; Mon, 27 Jan 2020 04:55:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.002
X-Spam-Level:
X-Spam-Status: No, score=-2.002 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, 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 4xLkhKZfszEh for <mmusic@ietfa.amsl.com>; Mon, 27 Jan 2020 04:55:56 -0800 (PST)
Received: from EUR05-AM6-obe.outbound.protection.outlook.com (mail-am6eur05on2060.outbound.protection.outlook.com [40.107.22.60]) (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 1D4CD120115 for <mmusic@ietf.org>; Mon, 27 Jan 2020 04:55:56 -0800 (PST)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=Y5VTsAKB0LG9S9wyPJgT3AkdICcMQkLQKi0xb2WsVWxBcB1J4IPoix8yxTAfW8H81YzLXsEnVg98Lrk8r6l87tm43MtlSPR2len9c7tcUWwB8UzageYHOJzR0nmtRKhxvMM4vasm+lFgQQ3z9Gsi1Vg06PweiIqp15+Vcr9o4iLFNd6SXIU8MQs4ImrxEwImFN7/lIe+8pj3JLc1UMFgBFLhQAN6nFoBoG9CE+yxzZT0e6ipjaZbqwLxUVgjVL92PeTdCgltminRXId/UHIeGxAtMIMIz7ZMH7Hk3e01nIx6+wiiSJtQuNyGTaUATQ3HmyryKhrygj/LHkb7D+vT3w==
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=JeLr8gyQ8S/vORhI4yHhpXju1tPhpQIghUUG2/gImfw=; b=VVSeAaxWhXkaFwOJg7WS336lO/YgYSlPdc2LRuGWiPELpbhvy0lX7r0F05SsMXthB9OgGJb1RdVj1ibnByVRZZoftv2YWN/PEK/uDjwsO1e7FA/lqcgAeTlkcwQChmNVIsY5ADUhQtvrtqOM7o4nwXqZ2pEcmY8Tkdj1CbSc5ZimDnsBjscsa2PdY7GnSExzNQP0ia0EGts3vc/kNZSB4yO2Hadts8YFgS0EvT5OUlZmGSIokuzSsYVUZumRIL2PCSD0QIoPFa57h23p8c6UM3oc2t1XAoqKtEwJOGWIACaMi1DUwDK1csOQxq5wIOzYFQoBgROTuYTqOiY0QXy/ig==
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=JeLr8gyQ8S/vORhI4yHhpXju1tPhpQIghUUG2/gImfw=; b=TpMeNCUbic07hZgGkIqXvWiiBmAEwih+CpEZwqAAFxe4Vszf/j0TisiiNDuZz/ENAB/5SvwV+GqSRjQIVoTwIwbQcWROCRSyB3BX47DF0cQ9kI0K6mWd53eCbPEQGwffY69iOMJYwoQhvREGUW9PlNk2HMIoz54W7eCKNeHVsK0=
Received: from AM0PR07MB3987.eurprd07.prod.outlook.com (52.134.82.159) by AM0PR07MB5650.eurprd07.prod.outlook.com (20.178.113.17) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2686.14; Mon, 27 Jan 2020 12:55:53 +0000
Received: from AM0PR07MB3987.eurprd07.prod.outlook.com ([fe80::28e8:93ab:34a6:c38d]) by AM0PR07MB3987.eurprd07.prod.outlook.com ([fe80::28e8:93ab:34a6:c38d%3]) with mapi id 15.20.2686.019; Mon, 27 Jan 2020 12:55:53 +0000
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Gunnar Hellström <gunnar.hellstrom@omnitor.se>, Adam Roach <adam@nostrum.com>, "mmusic@ietf.org" <mmusic@ietf.org>
Thread-Topic: [MMUSIC] AD Review: draft-ietf-mmusic-t140-usage-data-channel - the updated pull request
Thread-Index: AQHV1REbhQi94O3RjkeaNmv1oFUgUA==
Date: Mon, 27 Jan 2020 12:55:53 +0000
Message-ID: <D0B17D8D-3B83-4D39-883C-4A29846BF744@ericsson.com>
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: [89.166.49.243]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 9766ace4-8533-4bb8-4fdd-08d7a3283e7f
x-ms-traffictypediagnostic: AM0PR07MB5650:
x-microsoft-antispam-prvs: <AM0PR07MB56504C8439BBDE70A3DEA790930B0@AM0PR07MB5650.eurprd07.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:9508;
x-forefront-prvs: 02951C14DC
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(4636009)(39860400002)(136003)(396003)(366004)(346002)(376002)(199004)(189003)(33656002)(26005)(6506007)(66946007)(44832011)(76116006)(66476007)(2616005)(71200400001)(5660300002)(2906002)(66446008)(64756008)(66556008)(966005)(8676002)(81166006)(81156014)(8936002)(186003)(86362001)(478600001)(36756003)(316002)(6486002)(66574012)(110136005)(6512007)(15650500001); DIR:OUT; SFP:1101; SCL:1; SRVR:AM0PR07MB5650; H:AM0PR07MB3987.eurprd07.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX: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: K6mkV9suO/hwC5WKb+7/RIseLQR1l7j8fJMolm2K4JUwyPSIdbo0RwaCst5FCMMhxIdPjdBWgcR5JbRY8c3zgaTBx2S7CDLdE3zQ2xSjdxkTHxo90Sid3QYSE07LPJW7BWIiDKuq/b8dB+J66aZvCjpyxgQSWVk9djA2AL7khw/27Fzo/B59pwNj1RxCVa9od3kCFKXLFRsMFHY07nv5gfLwTrjUXOJu1KKFS/BqFMD6N4L5w6sJ6NSJSVHesoexQoRCXM5WcqVHcrV8Sn0h3UlhSer2s58Jcbc5C7yQvpSzvg7BSEmhaQb4ruFjW9JFAAxsaH1sZWEriUXtCy3bxzy6lFV+Q4tz1kKVl0vdohmUTH35BcFwcl+Kx3a+tCIsQJu8TSl5Y0eLtgtHj4MpoZpnZjFxRm46dMBWuupO3TOAk4pgMxZwswdjZ7ampzcMhBKzPPEtPHZm5MfGyQ+EUzrdP0wjAzMdMYBCT2D7Mpw+4LhPJen8J5wD6Zy2qMVVgp6anD5uS6hQJ5FRJPxbQg==
x-ms-exchange-antispam-messagedata: XutmMu5GVDFts01UIVYMWQGCxOcZRvUNA1jiM+aUo9+IjaHsurQ24hbLZNJFlXToWQiBuzmc9WFDYia/4Xp7eTXDSVIwKNjJ/mSBg9CCZRNOEGbxibJJDegpVWtvv3zIbybk4AKiruSoZuwlCBltCA==
x-ms-exchange-transport-forked: True
Content-Type: text/plain; charset="utf-8"
Content-ID: <8D447D77D052FC409AE31D417D476C95@eurprd07.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: ericsson.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 9766ace4-8533-4bb8-4fdd-08d7a3283e7f
X-MS-Exchange-CrossTenant-originalarrivaltime: 27 Jan 2020 12:55:53.8175 (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: RBSnU1sn11allljfHzIsXqr837lVaH8sHSRLGCRLMrOto6I6m/IvtIVDgxb2CMDPkUmyr5gqL5sb25cKDeZJgMCwmJRUfbhmTUQcwxWDnbQ=
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM0PR07MB5650
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/nDPIhOcJ-8eO4OD32P_WAx0S4HE>
Subject: Re: [MMUSIC] AD Review: draft-ietf-mmusic-t140-usage-data-channel - the updated 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: Mon, 27 Jan 2020 12:55:59 -0000
Hi, Based on Gunnar's comments, I have updated the pull request. Regards, Christer On 27/01/2020, 13.46, "Gunnar Hellström" <gunnar.hellstrom@omnitor.se> wrote: Christer, you are right, clear and fine. No need for change. Gunnar Den 2020-01-27 kl. 08:38, skrev Christer Holmberg: > Hi, > >>>> I have proposed new wording for the sentences about updating RFC 8373 in Github. >>>> >>>> We do not update RFC 8373 for all WebRTC data channels. We only do it for 't140' subchannels. >>> We update 8373 for WebRTC data channels (the application/webrtc-datachannel) media type. >>> >>> We do NOT say that each subprotocol has to use the same language modality – we say that each >>> subprotocol (e.g., t140) will have to specify the language modality for that subprotocol. >> Right, sorry, I did not find that general update statement when I made my comment. I only found the two places that were >> modified. So, I withdraw my comments, but please check if it is sufficiently easy to find the actual update text for RFC 8373. > We have a dedicated section (Section 7) for the 8373 update, and it contains the statement I referred to earlier (saying that subprotocols > must define the language modality), so I don't see how it could be made more clear than that :) > > Regards, > > Christer > > > > > > > Den 2020-01-24 kl. 16:08, skrev Christer Holmberg: > Hi, > > Based on Adam's AD review, I have created a pull request. > > https://protect2.fireeye.com/v1/url?k=2c2d5b3e-70f95c92-2c2d1ba5-8667c4afe13e-d27a5c8e10d59d11&q=1&e=d6e7256a-9e02-4443-bca5-69fb5eaa056c&u=https://github.com/cdh4u/draft-datachannel-t140/pull/55 > > Adam indicated that I could implement the changes together with the changes based on the IETF last-call comments. But, assuming people are ok with the changes, I'd like to merge the PR and submit a new version for the IESG to review. > > Regards, > > Christer > > > > > On 24/01/2020, 15.10, "Christer Holmberg" mailto:christer.holmberg@ericsson.com wrote: > > Hi, > > --------------------------------------------------------------------------- > > >> §4.1: > >> > >> The offerer and answerer MUST NOT include the max-retr and max-time > >> attribute parameters in the 'dcmap' attribute. > >> > >> Ideally, this would include text that indicates what a recipient of such > >> messages would do (with the obvious choices being ignoring them or treating > >> them as an error). I suggest the easiest thing to specify is that recipients > >> of either attribute for a T.140 section MUST ignore them. > >> > >> Just to note: > >> > >> - The draft defines that the T.140 data channel is reliable. > >> - max-retr and max-time are used to indicate that a data channel is partially reliable, so there would be a conflict. > >> > >> So, the question is whether it is ok to just ignore, or whether it is a protocol error and the m- line therefore should be rejected. > >> > >> If *both* attribute parameters are included in an offer (which would also create a conflict), draft-channel-sdpneg says that the offer must be rejected. > > > > Given this last fact, it seems that the best approach would be to treat > > the presence of either parameter in this context as an error. The key > > here is that the behavior should be spelled out. > > I suggest the following: > > OLD: > > The offerer and answerer MUST NOT include the max-retr and max-time > attribute parameters in the 'dcmap' attribute. > > > NEW: > > The offerer and answerer MUST NOT include the max-retr and max-time > attribute parameters in the 'dcmap' attribute. If any of the > attribute parameters are included in an offer or answer, the receiver > MUST take the proper actions to reject the SDP. > > --------------------------------------------------------------------------- > > Regards, > > Christer > > > > > _______________________________________________ > mmusic mailing list > mailto:mmusic@ietf.org > https://www.ietf.org/mailman/listinfo/mmusic -- + + + + + + + + + + + + + + Gunnar Hellström Omnitor gunnar.hellstrom@omnitor.se +46 708 204 288
- Re: [MMUSIC] AD Review: draft-ietf-mmusic-t140-us… Christer Holmberg