Re: [Uta] draft adoption - draft-sheffer and xmpp

Pádraic Brady <padraic.brady@gmail.com> Mon, 03 February 2014 16:32 UTC

Return-Path: <padraic.brady@gmail.com>
X-Original-To: uta@ietfa.amsl.com
Delivered-To: uta@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1C6D91A00E0 for <uta@ietfa.amsl.com>; Mon, 3 Feb 2014 08:32:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.7
X-Spam-Level:
X-Spam-Status: No, score=-1.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, MIME_8BIT_HEADER=0.3, SPF_PASS=-0.001] 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 O4P5PzKkOJVu for <uta@ietfa.amsl.com>; Mon, 3 Feb 2014 08:32:06 -0800 (PST)
Received: from mail-qa0-x233.google.com (mail-qa0-x233.google.com [IPv6:2607:f8b0:400d:c00::233]) by ietfa.amsl.com (Postfix) with ESMTP id 7816D1A0032 for <uta@ietf.org>; Mon, 3 Feb 2014 08:32:06 -0800 (PST)
Received: by mail-qa0-f51.google.com with SMTP id f11so10497038qae.10 for <uta@ietf.org>; Mon, 03 Feb 2014 08:32:06 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=JC1SkI77/9oOo/OZv3MICoDlo9fLaM4XEowYlaLidtA=; b=G4gwFSPYx+J0rFsUF/aDfTct9fruFBwtWyMUKAd3vLe9OCB86uyX9bRRfLXgoBKr7u tx3/0ZmiuU/QUq/Qso5ZjHdVddctLwvZAdv654wQfacy2H2Nu2T9h+2t6uKw+vFyf81b O02rbePIKBdZlcWFk0z0MQVkZScbwtHtd2RSvJ5/hZcUEdN+EcgHwMa9v1Vr5UN5Zcf6 3Kb50HqVI+edN8TSOHsvC0Kmde+1Q4huLgjuu+9/wUYgqqBtavgwBteUA3kGMIKd4I1+ 0yZAErLXJAo5GR8gi0sCqqOM6oPUUMR6FR+W/c5e9cEceC4Gk6NWrI5CZnUfTYT+GZ7r 22Lg==
MIME-Version: 1.0
X-Received: by 10.236.86.141 with SMTP id w13mr34596151yhe.41.1391445126270; Mon, 03 Feb 2014 08:32:06 -0800 (PST)
Received: by 10.170.215.130 with HTTP; Mon, 3 Feb 2014 08:32:06 -0800 (PST)
In-Reply-To: <52EF8C0E.40105@cs.tcd.ie>
References: <52EF8C0E.40105@cs.tcd.ie>
Date: Mon, 03 Feb 2014 16:32:06 +0000
Message-ID: <CALwr1Gk20_kMsQCru=HRuom-YA+EubWwC4GCX8zvbPTvUpCE-Q@mail.gmail.com>
From: Pádraic Brady <padraic.brady@gmail.com>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Cc: uta@ietf.org
Subject: Re: [Uta] draft adoption - draft-sheffer and xmpp
X-BeenThere: uta@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: UTA working group mailing list <uta.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/uta>, <mailto:uta-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/uta/>
List-Post: <mailto:uta@ietf.org>
List-Help: <mailto:uta-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/uta>, <mailto:uta-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 03 Feb 2014 16:32:08 -0000

Hi all,

On 3 February 2014 12:31, Stephen Farrell <stephen.farrell@cs.tcd.ie> wrote:
>
> I would like to propose that the WG chairs just declare
> that the WG have adopted at least draft-sheffer-tls-bcp [1]
> and http://tools.ietf.org/html/draft-saintandre-xmpp-tls. [2]
>
> There may be others that are equally obvious but at least
> those two should be non controversial. Since Feb 14 is the
> cutoff for drafts before London that ought be done by now
> really IMO.
> [...]
>
> [1] https://tools.ietf.org/html/draft-sheffer-tls-bcp-01
> [2] https://tools.ietf.org/html/draft-saintandre-xmpp-tls
> _______________________________________________
> Uta mailing list
> Uta@ietf.org
> https://www.ietf.org/mailman/listinfo/uta

Speaking as an observer, the sheffer document reads very closely to
what we've been working to accomplish in the PHP programming language
for PHp 5.5. Daniel Lowry is currently running with an RFC [1] or two
[2] that would implement most of its recommendations.

In terms of implementation, PHP supports both its own layer (for PHP
Streams) based on openssl and a separate cURL extension using libcurl.
PHP Streams and sockets have historically had peer verification, etc.
disabled by default and this is being reversed at long last.

It also means that PHP is, for once, departing from openssl's DEFAULT
ciphersuite in favour of the current Mozilla recommendation [3]. This
is then divorced from openssl and curl. curl also departed from
openssl's DEFAULT earlier in January but doesn't prioritise for
perfect forward secrecy yet. That PHP, openssl and curl may soon
define three varying ciphersuites is a little confusing for us!

My point here is that I really appreciate the WG's mission and I hope
that something, whether it be the draft-sheffer-tls-bcp or another
document, emerge to get everyone on the same page. At the moment it's
down to pulling random pages off the internet as references and it
doesn't carry the same weight.

[1] https://wiki.php.net/rfc/tls-peer-verification
[2] https://wiki.php.net/rfc/improved-tls-defaults
[3] https://wiki.mozilla.org/Security/Server_Side_TLS#Recommended_Ciphersuite

--
Pádraic Brady