Re: [MMUSIC] I-D Action: draft-ietf-mmusic-msrp-usage-data-channel-10.txt - Comment on msrp-cema attribute

Jose M Recio <jose@ch3m4.com> Thu, 25 April 2019 11:29 UTC

Return-Path: <jose@ch3m4.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 6576B1200FE for <mmusic@ietfa.amsl.com>; Thu, 25 Apr 2019 04:29:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=ch3m4.com header.b=khxYYseU; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=8jnq8HLB
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 o6dLywi0qQhI for <mmusic@ietfa.amsl.com>; Thu, 25 Apr 2019 04:29:33 -0700 (PDT)
Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9A5BA120072 for <mmusic@ietf.org>; Thu, 25 Apr 2019 04:29:33 -0700 (PDT)
Received: from compute2.internal (compute2.nyi.internal [10.202.2.42]) by mailout.nyi.internal (Postfix) with ESMTP id B98A721FED; Thu, 25 Apr 2019 07:29:32 -0400 (EDT)
Received: from mailfrontend1 ([10.202.2.162]) by compute2.internal (MEProxy); Thu, 25 Apr 2019 07:29:32 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ch3m4.com; h= subject:to:references:from:message-id:date:mime-version :in-reply-to:content-type; s=fm3; bh=AE2PSor1ZC7LeiuL8U82fU+n1mp nvBe35Z2SbScu11Q=; b=khxYYseUt0JRCLyi7gfepIYSiXgug7UMWNQGpDLh075 8Ti5jX4nDZ6GUrH/i4403xCZyqupfHRNaqil3S/Fgan3nwJCUsD5htgbpkwVRkwZ o3h6U7Wq0gHrdhHyYqQIs0bNQGc9ceZ5Ottj3I0yvvhcwOX0+ddPp3JTBJfTWujq OK4X9GkFa3/COsQbS0ngx7odN8H+gNU0duZS54Jsz2afS+aYH47NEZ2DjgyICeVt 14CuDYFPOo36Bl9qG/5ODn067f9vv8/Y00pzXSgUSerkCKRR1sgQQxFKe1k2ZcwJ AK/0QK2RF/g5yW4LV0PNfTtIi9jCYHemP8D4kskrrhw==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=AE2PSo r1ZC7LeiuL8U82fU+n1mpnvBe35Z2SbScu11Q=; b=8jnq8HLBkHlwdtHo/eKt+9 zSfutgTIldrv3fgxiPZMAhcTV6KdeVdHTSB/8eU9WvLPqs7HNgazKy24U26NUPIM hk69YohETDRJDgsUao2I0LVaIsqEHqCzXvFr7jhr+YKnIRptksYIfgUs+NQz2NXN Tzrmo7VB4+hUFkLjmlh/0cfkguoXWE3J+qAuVuqTjGnxA7iDUVoZjNu7L3q53ElB NZ6sq0a9Ome93/pdrWjN4RZbptYkSpkWz3Hoa8D7blaRPxGqCNPsKr6yHZXPim2G 5S662CQE/VZYUmTgOuaRTL52CiujJoZqOU6RjL0lvs+IMeyF1vwrkPC1speTvLtw ==
X-ME-Sender: <xms:HJrBXHwfvTPZKzDrF1nG__rB92zY0md0dpzlUdObXIsXYg-D1Enzow>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduuddrheeggdeflecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpefuvfhfhffkffgfgggjtgesrgdtreertdefjeenucfhrhhomheplfhoshgvucfo ucftvggtihhouceojhhoshgvsegthhefmhegrdgtohhmqeenucfkphepieeirdeliedrvd dtgedrudegjeenucfrrghrrghmpehmrghilhhfrhhomhepjhhoshgvsegthhefmhegrdgt ohhmnecuvehluhhsthgvrhfuihiivgeptd
X-ME-Proxy: <xmx:HJrBXDjFRCHwFwPEDFD_RNwyPl_s1pA3o4JOIV6DOD08C2ZLnSRFBA> <xmx:HJrBXMU1wxQd0ZzJcGIA7ZDLzN6RR4qjs97Wz056i60remFm17mdQg> <xmx:HJrBXF3sB7DhIRwHDBplZzYF9Hqijl-2VhfwK0W2q_4Azydp3wI3oA> <xmx:HJrBXM8wgJTUgs3PvyMW0IHYI-QBV11h_NkTmN7dKfHM4XQ6geO9LQ>
Received: from [192.168.1.187] (unknown [66.96.204.147]) by mail.messagingengine.com (Postfix) with ESMTPA id 4E4DBE44D7; Thu, 25 Apr 2019 07:29:31 -0400 (EDT)
To: Christer Holmberg <christer.holmberg@ericsson.com>, "mmusic@ietf.org" <mmusic@ietf.org>
References: <61D3ED98-04FA-4746-BCDE-37BD38907803@ericsson.com> <bc4535ee-7d65-e35e-5e9e-604446bf9d0f@ch3m4.com> <E24A4C62-CBCB-47F0-973F-0BF253AC4A31@ericsson.com>
From: Jose M Recio <jose@ch3m4.com>
Message-ID: <b3e42338-f785-2bb3-6b29-63427f4ec75e@ch3m4.com>
Date: Thu, 25 Apr 2019 19:29:29 +0800
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.6.1
MIME-Version: 1.0
In-Reply-To: <E24A4C62-CBCB-47F0-973F-0BF253AC4A31@ericsson.com>
Content-Type: multipart/alternative; boundary="------------BEB1D4CE4443D4E85B8FF884"
Content-Language: en-GB
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/weq4EaznKr9lCKMIv5o7Jooovco>
Subject: Re: [MMUSIC] I-D Action: draft-ietf-mmusic-msrp-usage-data-channel-10.txt - Comment on msrp-cema 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: Thu, 25 Apr 2019 11:29:36 -0000

On 23/4/19 4:32 AM, Christer Holmberg wrote:

> Keep in mind (and that should probably better described in the document) that the normal MSRP routing procedures don't apply. The MSRP messages will be routed in the data channel, which is established between the SIP peers (or whatever signaling protocol is used). I guess proxies and application servers can look at the top-most path attribute, but that is not going to be the primary routing input. I don't think the draft says anything about that - it just seems to assume that the data channel will end up in the intended MSRP peer.

It indeed assumes that the data channel endpoint will be a MSRP peer, 
either another endpoint or a MSRP GW. If that's not clear enough it 
should be made more explicit.

If the endpoint is a GW, messages can be relayed, similar to the 
scenario where the connection to the GW is done using TLS, or 
WebSockets, instead of dc.