Re: [Stox] Stephen Farrell's IESG feedback on draft-ietf-stox-core

Stephen Farrell <stephen.farrell@cs.tcd.ie> Mon, 10 February 2014 22:20 UTC

Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: stox@ietfa.amsl.com
Delivered-To: stox@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 39BA61A08A8; Mon, 10 Feb 2014 14:20:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.448
X-Spam-Level:
X-Spam-Status: No, score=-2.448 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.548] autolearn=ham
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 4hlNwvD2W78s; Mon, 10 Feb 2014 14:20:37 -0800 (PST)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) by ietfa.amsl.com (Postfix) with ESMTP id 7DDD61A08A1; Mon, 10 Feb 2014 14:20:37 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id 463DEBE39; Mon, 10 Feb 2014 22:20:36 +0000 (GMT)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oOqRtpAfRzpz; Mon, 10 Feb 2014 22:20:34 +0000 (GMT)
Received: from [10.87.48.4] (unknown [86.46.19.178]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 829D1BE25; Mon, 10 Feb 2014 22:20:34 +0000 (GMT)
Message-ID: <52F950B2.2050107@cs.tcd.ie>
Date: Mon, 10 Feb 2014 22:20:34 +0000
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: Peter Saint-Andre <stpeter@stpeter.im>, The IESG <iesg@ietf.org>
References: <52F91953.8010604@stpeter.im>
In-Reply-To: <52F91953.8010604@stpeter.im>
X-Enigmail-Version: 1.6
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: stox@ietf.org
Subject: Re: [Stox] Stephen Farrell's IESG feedback on draft-ietf-stox-core
X-BeenThere: stox@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: SIP-TO-XMPP Working Group discussion list <stox.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/stox>, <mailto:stox-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/stox/>
List-Post: <mailto:stox@ietf.org>
List-Help: <mailto:stox-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/stox>, <mailto:stox-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 10 Feb 2014 22:20:43 -0000

Hi Peter,

On 02/10/2014 06:24 PM, Peter Saint-Andre wrote:
> ( + STOX WG since one of the issues might deserve broader discussion )
> 
> Hi Stephen, thanks for your review:
> 
> https://datatracker.ietf.org/doc/draft-ietf-stox-core/ballot/
> 
> You wrote in part:
> 
>    - I wondered why you didn't just say that (D)TLS SHOULD
>    be used/supported between gateways. Given that all the
>    relevant bits of code are likely to support that, wouldn't
>    it be a good thing?
> 
> Yes, that seems eminently reasonable.

Just to be clear - the above is the only DISCUSS point.

> 
>    - Has anyone thought about confusability in the name
>    mappings? I expected to see a bit of text in the
>    security considerations but didn't see it.
> 
> Confusion is always possible. :-) Were you thinking about confusable
> characters from Unicode, or something else?

Right. Maybe its all there already and I just didn't see
if in the mapping stuff, or maybe not. I'm not sure.

> 
>    - It seems a shame to not be able to gateway when the To is
>    a sips URI at all but I understand that some loss of
>    security is inevitable for cases like this. Is there any
>    work planned for an update that would allow gatewaying for
>    such cases, e.g. if the 1st XMPP server is the one to which
>    the user is connected and the user is connected using
>    XMPP/TLS?
> 
> Hmm. I cannot say that I am aware of planning for updates to provide
> more secure gatewaying, although folks active in the STOX WG might be
> thinking along those lines.
> 
> Depending on the deployment architecture, I think there are cases where
> it is *possible* to TLS-protect all the hops. For instance, if
> sip.example.org has a direct server-to-server connection to
> xmpp.example.com (no intermediate hops) and both organizations agree to
> force the use of TLS for client connections (e.g., via SLA), then I
> suppose that sip.example.com could honor 'sips' URIs when sending
> traffic to xmpp.example.com. However, such an arrangement is rare enough
> right now that I don't know if it is worth mentioning.

Fair enough. I can see that detecting that you (probably) have
all (D)TLS hops might be tricky and error prone.

Cheers,
S.


> 
> Peter
>