Re: [MMUSIC] AD Review: draft-ietf-mmusic-t140-usage-data-channel

Paul Kyzivat <pkyzivat@alum.mit.edu> Mon, 27 January 2020 19:39 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 2402C3A0A9D for <mmusic@ietfa.amsl.com>; Mon, 27 Jan 2020 11:39:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.989
X-Spam-Level:
X-Spam-Status: No, score=-1.989 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, T_SPF_TEMPERROR=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=alum.mit.edu
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 4Vb0YfXWqkAi for <mmusic@ietfa.amsl.com>; Mon, 27 Jan 2020 11:39:35 -0800 (PST)
Received: from NAM11-BN8-obe.outbound.protection.outlook.com (mail-bn8nam11on20608.outbound.protection.outlook.com [IPv6:2a01:111:f400:7eae::608]) (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 B67C23A0A9B for <mmusic@ietf.org>; Mon, 27 Jan 2020 11:38:50 -0800 (PST)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=IfrYT7tNrjMS3lKrR00CnPQE80hHaB9CvlfBrzbGjJLspFkxdK9PBAwdZjJ2ydcq0ToRpiRHdUq3/+18YbEjkVLj46Al/nP4GOFnw9egWHt+I3IvrLEZ/SviCJQp9sleDs2sXFq77WcsZC4pUHkGBiKdiukFtT0WG4EQcukVicOqr0I5VtLfG0Ec63OlXlcGrpy83yc2OVre95TqqL0Y6PqNnHzZ/kMuZUm8uJwtEICXFSGwtncPJuO00k5m685lmz3u2XilFMnISkV7pVm5+NwNBsP6FnltDR/Em8RFDa8ux8c718eSu9jKjf8RhJiGNuNhcEL9Gf/ffv5wgLx4ng==
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=Ysr/8+4dFMdgrAKjq+E/MNpYb688EM02HVa+T0xmV4c=; b=mS4UqqLD0wpXV7V9lhbFWoXMRKCSmdgL95pTZSO/fkou0L2TtBUKtJqsBGrIjrTUBcSxh0K9rNLwpkv5ayr683ZrvH06xRiB013rjyYnRUtktN7sXAfNMjRBvQKzmp8Y9KybcLhPRrkQl52dIquk/MGtvu77zp0ybvosQBdc54qwbUy6okMqX6B1OgOrXPXAxes2XOkOXiLybZQprAb/tGPKCYl3KLli5qp7hxTPdl2C/MyXR5gFVbBe/HoNYU6ggEUI2ileHq71RJT05NF0sap+rkRx6zpGhaMIQ8IhRD0ATHZsKuSqkEJltiNmRg+m1CayuKMr9RUl1fdLIGJr3w==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass (sender ip is 18.7.68.33) smtp.rcpttodomain=ietf.org smtp.mailfrom=alum.mit.edu; dmarc=bestguesspass action=none header.from=alum.mit.edu; dkim=none (message not signed); arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=alum.mit.edu; s=selector2; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=Ysr/8+4dFMdgrAKjq+E/MNpYb688EM02HVa+T0xmV4c=; b=aIXPvRvhoMa9x8ZH/hcSFuEQ/r0o6vDgbFOj0SbI9w3iH2pfEx860ADpV55FCVdOGzfLrMp0TrWQapSZERYVkHQ0HW81Q9gGU/4VXePDdbxtF4053eHU9p3OB4BXmojYupUZ4BrR+Smuhr0dXWx8/iGUWw8ht3DXbc0wrqQFkmk=
Received: from SN1PR12CA0083.namprd12.prod.outlook.com (2603:10b6:802:21::18) by MN2PR12MB3501.namprd12.prod.outlook.com (2603:10b6:208:c7::33) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2665.23; Mon, 27 Jan 2020 19:38:48 +0000
Received: from CY1NAM02FT059.eop-nam02.prod.protection.outlook.com (2a01:111:f400:7e45::202) by SN1PR12CA0083.outlook.office365.com (2603:10b6:802:21::18) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2644.21 via Frontend Transport; Mon, 27 Jan 2020 19:38:48 +0000
Authentication-Results: spf=pass (sender IP is 18.7.68.33) smtp.mailfrom=alum.mit.edu; ietf.org; dkim=none (message not signed) header.d=none;ietf.org; dmarc=bestguesspass action=none header.from=alum.mit.edu;
Received-SPF: Pass (protection.outlook.com: domain of alum.mit.edu designates 18.7.68.33 as permitted sender) receiver=protection.outlook.com; client-ip=18.7.68.33; helo=outgoing-alum.mit.edu;
Received: from outgoing-alum.mit.edu (18.7.68.33) by CY1NAM02FT059.mail.protection.outlook.com (10.152.74.211) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2665.18 via Frontend Transport; Mon, 27 Jan 2020 19:38:47 +0000
Received: from Kokiri.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 00RJcjd1022617 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT) for <mmusic@ietf.org>; Mon, 27 Jan 2020 14:38:46 -0500
To: mmusic@ietf.org
References: <25e5fd92-84c2-fd6c-d497-3fcfa452967e@nostrum.com> <556B5E81-09BE-41E4-9A2C-E902E870F0E0@ericsson.com> <715526dd-fa80-ea2b-5837-aa08193b7445@nostrum.com> <9C2BD899-6EC8-4920-96AC-6C2B170B6373@ericsson.com> <60b0aaa0-648d-4026-1820-9322743d7778@omnitor.se> <DB0C4D76-E849-4609-847E-6E454F14B7BC@ericsson.com> <659c43b1-7fa7-3bf4-0b9a-3dfa6ecaad93@omnitor.se> <8ee7d5b1-131c-9e47-4026-d64a8b0ba0c6@alum.mit.edu> <BBC0E0FA-99D0-48CB-9D35-DBAB0739D90B@ericsson.com> <f5db2705-7043-7dbf-0cb4-daed062882a6@alum.mit.edu> <AA322B3E-ECAD-4F94-8DC7-EB4715B0B6C8@ericsson.com>
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
Message-ID: <d1a40c44-0378-1e1f-f1a4-576e6232c924@alum.mit.edu>
Date: Mon, 27 Jan 2020 14:38:45 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:68.0) Gecko/20100101 Thunderbird/68.4.1
MIME-Version: 1.0
In-Reply-To: <AA322B3E-ECAD-4F94-8DC7-EB4715B0B6C8@ericsson.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
X-EOPAttributedMessage: 0
X-Forefront-Antispam-Report: CIP:18.7.68.33; IPV:CAL; SCL:-1; CTRY:US; EFV:NLI; SFV:NSPM; SFS:(10009020)(396003)(376002)(346002)(136003)(39860400002)(199004)(189003)(5660300002)(6916009)(246002)(956004)(2616005)(966005)(26826003)(478600001)(336012)(186003)(786003)(8936002)(53546011)(26005)(7596002)(316002)(8676002)(36906005)(356004)(75432002)(70586007)(70206006)(86362001)(2906002)(31686004)(31696002); DIR:OUT; SFP:1101; SCL:1; SRVR:MN2PR12MB3501; H:outgoing-alum.mit.edu; FPR:; SPF:Pass; LANG:en; PTR:outgoing-alum.mit.edu; A:1; MX:1;
X-MS-PublicTrafficType: Email
X-MS-Office365-Filtering-Correlation-Id: 95276293-ae9c-4904-fd01-08d7a360874a
X-MS-TrafficTypeDiagnostic: MN2PR12MB3501:
X-Microsoft-Antispam-PRVS: <MN2PR12MB35019A4D6BD246FBFF4A6AC8F90B0@MN2PR12MB3501.namprd12.prod.outlook.com>
X-MS-Oob-TLC-OOBClassifiers: OLM:10000;
X-Forefront-PRVS: 02951C14DC
X-MS-Exchange-SenderADCheck: 1
X-Microsoft-Antispam: BCL:0;
X-Microsoft-Antispam-Message-Info: s7oE/XDZz9NhOydvi0FACn/EZ3aTkzT4wAlFwjCODTTWuf0/1rZ+a0joGUROU6QtKkgpFvPcIz55SQg5USVgD8P2c3LrW+ABbNbMjliT+KCtSoQNg0IDKUswYXCvUoMyUZRs7wwfzfRM3kdDieansiJb8h5G2DKoifmN25GvZXGqqH2YSojUadU+92tHW0IyR7apayt/Y3xOLqmKiqAntB/SXM/lRp+NMRcWB3Kbp5pAlNq6iIOIyZ4SN1DmwWa5Jo4Zul5gkqC08p4xnmePNGATuiKmm67MebnbnMMCrv1ff8jjjzJWHuiMDSZr1tM7RBRMGBXw57wy0779hRcuJQ3ZWg514+LBUf/CDvDb0Enrkif5NkbbP6tZUTF7DIdIZDrGhZ+lhueDOGRzGamFvrNYjR0cOb9C7AS67+C5Ds9Bmc7IGXF6yIEbdnrqDgPkSelcmn35vo+sJjJFW1ffAn/8b3ZZsqvLUjBzgDTicWs=
X-OriginatorOrg: alum.mit.edu
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 27 Jan 2020 19:38:47.6399 (UTC)
X-MS-Exchange-CrossTenant-Network-Message-Id: 95276293-ae9c-4904-fd01-08d7a360874a
X-MS-Exchange-CrossTenant-Id: 3326b102-c043-408b-a990-b89e477d582f
X-MS-Exchange-CrossTenant-OriginalAttributedTenantConnectingIp: TenantId=3326b102-c043-408b-a990-b89e477d582f; Ip=[18.7.68.33]; Helo=[outgoing-alum.mit.edu]
X-MS-Exchange-CrossTenant-FromEntityHeader: HybridOnPrem
X-MS-Exchange-Transport-CrossTenantHeadersStamped: MN2PR12MB3501
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/x7TtK1aGU494TKK81reeZpRrJaU>
Subject: Re: [MMUSIC] AD Review: draft-ietf-mmusic-t140-usage-data-channel
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 19:39:46 -0000

On 1/27/20 1:09 PM, Christer Holmberg wrote:
> Hi,
> 
>      >>>> sdpneg has the following wording in 6.2 for the error case when both
>      >>>> parameters are included in the answer:
>      >>>>
>      >>>>    "If an SDP answer contains both
>      >>>>     of these parameters then the offerer MUST treat the associated SDP
>      >>>>     offer/answer as failed."
>      >>>
>      >>> The tricky part of treating the O/A as having failed is that only the
>      >>> offerer knows this, while the answerer thinks it has succeeded. So the
>      >>> two sides have differing understandings of the state of the session.
>      >>> (Consider that there may also have been changes in another media
>      >>> section.) Things will not go well until this is corrected.
>      >>>
>      >>> I don't know if there is any document that specifies what to do in this
>      >>> situation. I think there are only two generic possibilities: drop the
>      >>> entire session (i.e., BYE), or start another O/A to try to fix this,
>      >>> perhaps by dropping the m= line. When following this latter course,
>      >>> there will be an extended period while the two sides are in
>      >>> disagreement, and no guarantee that the fix will work.
>      >>>
>      >>> The simplest solution is to simply say that this is a protocol
>      >>> violation, and recovery is an implementation issue. While simple to
>      >>> write, this is perhaps not the best solution.
>      >>
>      >> That is normally what we say.
>      >>
>      >> However, if more text is needed I think it belongs to the data channel sdpneg draft. I don't think that each data channel usage draft shall have to describe how it is done.
>      >
>      > Then I think the best path might be to update sdpneg with some specific
>      > language, and then update this draft to refer to that.
> 
> We can do that. However, we don't need to wait for that until we progress this draft. It is anyway not going to be published until sdpneg is done.

The only concern is that I think there ought to be a reference to 
whatever sdpneg will say on the subject. But perhaps it is possible to 
craft a reference that works assuming that sdpneg will be updated, 
without waiting for that update to be made.

	Thanks,
	Paul

> Regards,
> 
> Christer
> 
> 
>   
> 
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www.ietf.org/mailman/listinfo/mmusic
>