Re: [dispatch] [RAI] MSRP Expert Review of draft-pd-dispatch-msrp-websocket-04

Iñaki Baz Castillo <ibc@aliax.net> Wed, 29 January 2014 16:42 UTC

Return-Path: <ibc@aliax.net>
X-Original-To: dispatch@ietfa.amsl.com
Delivered-To: dispatch@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 193D51A03CB for <dispatch@ietfa.amsl.com>; Wed, 29 Jan 2014 08:42:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.678
X-Spam-Level:
X-Spam-Status: No, score=-1.678 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-0.7] autolearn=no
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 Kd2aFINbd3Gp for <dispatch@ietfa.amsl.com>; Wed, 29 Jan 2014 08:42:54 -0800 (PST)
Received: from mail-qa0-f54.google.com (mail-qa0-f54.google.com [209.85.216.54]) by ietfa.amsl.com (Postfix) with ESMTP id AC3EA1A036B for <dispatch@ietf.org>; Wed, 29 Jan 2014 08:42:54 -0800 (PST)
Received: by mail-qa0-f54.google.com with SMTP id i13so2763925qae.27 for <dispatch@ietf.org>; Wed, 29 Jan 2014 08:42:51 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type:content-transfer-encoding; bh=ETudGGDlNWpp44kYQpB4+dq+YL7WkqjGfyr4J5/F3zo=; b=mSM/rO79eGCuVDMJPLQQO995VDf8T9K5aFbXeLxac39wQvYHwtE10Emk2/k/3NBeVS 6iXC3j7bNTO1y86o37C5kAdNPkqd3H70fcjM6eDf6SENHXYJZMOQjv4oXvCWe1B6cOfs gIx6AS3+w60ipuof+U7n01X1hfWmIBX9KxPgijT0mhDoO6dHiT3gDeTIX9GL1Gttmqi+ g04/ReHqRbRMMl5oC4Klejdz5AHxSBf1FMSkOpZazlpsbfOdb4IfWFyryqtseru3mJGI lsLOjtVIy0XfisZvzu1YjP+aJCy/XM8Yf3midwDqeplZatnFzj0/4ZgbBLl/XPBfI2rg MHAg==
X-Gm-Message-State: ALoCoQnwIyEsQDXrINTXNeAzOyNtbDhxdYXxR2GPNs1cg9Wgm6zA3uOaysnXPVKyp8IqjN2eQ63Z
X-Received: by 10.224.7.10 with SMTP id b10mr13955531qab.50.1391013771562; Wed, 29 Jan 2014 08:42:51 -0800 (PST)
MIME-Version: 1.0
Received: by 10.96.101.232 with HTTP; Wed, 29 Jan 2014 08:42:31 -0800 (PST)
In-Reply-To: <A25E55DD-59E3-4F43-BE9A-6304378FAE0B@cisco.com>
References: <45B84D8F-AD8C-4B28-90DF-9B1C40771104@nostrum.com> <6833E320-7B45-4FC2-853B-62311DCF7E7B@nostrum.com> <A25E55DD-59E3-4F43-BE9A-6304378FAE0B@cisco.com>
From: =?UTF-8?Q?I=C3=B1aki_Baz_Castillo?= <ibc@aliax.net>
Date: Wed, 29 Jan 2014 17:42:31 +0100
Message-ID: <CALiegf=mn1Lg6ihhf8hamn6rVpkLnF3ydGxm1tK1JaNMaioxoQ@mail.gmail.com>
To: "Cullen Jennings (fluffy)" <fluffy@cisco.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Cc: Ben Campbell <ben@nostrum.com>, DISPATCH <dispatch@ietf.org>, "rai@ietf.org" <rai@ietf.org>, "draft-pd-dispatch-msrp-websocket.all@tools.ietf.org" <draft-pd-dispatch-msrp-websocket.all@tools.ietf.org>
Subject: Re: [dispatch] [RAI] MSRP Expert Review of draft-pd-dispatch-msrp-websocket-04
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: DISPATCH Working Group Mail List <dispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dispatch>, <mailto:dispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dispatch/>
List-Post: <mailto:dispatch@ietf.org>
List-Help: <mailto:dispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dispatch>, <mailto:dispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 29 Jan 2014 16:42:56 -0000

2014-01-29 Cullen Jennings (fluffy) <fluffy@cisco.com>om>:
> I don’t see why using websockets would require us to get rid of the MUST use TLS.
>
> The security of relays is a total disaster if you don’t have this so if the MUST be security authenticated goes away for relays, then I suspect this mechanisms is too broken to publish.

Neither I understand why the "MUST use TLS" should be dropped for MSRP
over WebSocket. I cannot figure out any reasons for getting rid of
that requirement. If it was valid and appropriate for MSRP over TCP
then it should also be for MSRP over WebSocket.

Just my opinion.


-- 
Iñaki Baz Castillo
<ibc@aliax.net>