Re: https at ietf.org

Dave Cridland <dave@cridland.net> Thu, 07 November 2013 11:25 UTC

Return-Path: <dave@cridland.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 595DC21E8131 for <ietf@ietfa.amsl.com>; Thu, 7 Nov 2013 03:25:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.67
X-Spam-Level:
X-Spam-Status: No, score=-1.67 tagged_above=-999 required=5 tests=[AWL=0.307, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rbq7XyXycS75 for <ietf@ietfa.amsl.com>; Thu, 7 Nov 2013 03:25:42 -0800 (PST)
Received: from mail-la0-x235.google.com (mail-la0-x235.google.com [IPv6:2a00:1450:4010:c03::235]) by ietfa.amsl.com (Postfix) with ESMTP id 6144311E813D for <ietf@ietf.org>; Thu, 7 Nov 2013 03:25:38 -0800 (PST)
Received: by mail-la0-f53.google.com with SMTP id eh20so301819lab.26 for <ietf@ietf.org>; Thu, 07 Nov 2013 03:25:38 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cridland.net; s=google; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=1cqK101ttfIGgRuep7hNt+STyqoJafoFExQNO7/9bTc=; b=NO040JEBewkUlSgiKwe4PcylbGocTsFC8Ev25Rsz/d7O408NW+FlTqnXMr8avf+yQ0 +ELh36rqn6EipNBfTRANOZxOIBgFjZEauKClwKxbolxgLPzulXpAM3QrEqph0AyLpxcJ ewlkvkZIDkO+sVVkYhOUXj+lvAmAckgrS2BGY=
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:date :message-id:subject:from:to:cc:content-type; bh=1cqK101ttfIGgRuep7hNt+STyqoJafoFExQNO7/9bTc=; b=YW7gCEwqb9VVhvrVw8zegjpcL/x2El6yTnoOH7srOqMRu3FhucVAxJ7EQICjyAuHgg odvMGxTvaLDKS+ZX+M/z3FLTz8QQqQYZ5zDEL3KS+Q/I1O8ufNyNvAMKC/1YBNEC7ky9 FBHnxGT4swXIdCpELyzi9rTLyuLAcvLwOMSgbSq3agLH/ka5bd9fFJjL0qFKAPLEFcwI Y1Imtgjr73FbQa5HvALp20mZvenKqLBnuRmwcres60R4VXRzYW0p59YPIaoZgRLScwMD vPpyyYHtQmbDciEC9HvZINJs4xRdwHoiLeo6Vplczya4p5rZOG1g3t3K5uj/6L320lxN l14A==
X-Gm-Message-State: ALoCoQlhbOKclMRvZ8T4dqMS/mzMGbD6Z2/blIZ/os8oFoYy3iFZzgI37zvmAff3L8QUGwIzfQ92
MIME-Version: 1.0
X-Received: by 10.152.6.74 with SMTP id y10mr6062150lay.16.1383823537852; Thu, 07 Nov 2013 03:25:37 -0800 (PST)
Received: by 10.114.183.47 with HTTP; Thu, 7 Nov 2013 03:25:37 -0800 (PST)
In-Reply-To: <01P0GHNIIOYE00004G@mauve.mrochek.com>
References: <CAHBU6ivbrk=NXgd4_5Upik+8H0AbHRy3kJnN=8fcK+Bz3pOV9Q@mail.gmail.com> <alpine.LRH.2.01.1311051733570.4200@egate.xpasc.com> <01P0FR4HDQNG00004G@mauve.mrochek.com> <CAHBU6ivZS33r4HHbCC391Ug9fMtZkJ3nojEeeqH5L+0+o3ZqGQ@mail.gmail.com> <01P0FU0CS96Q00004G@mauve.mrochek.com> <26C6A672-A5D2-44C4-B343-9CCE5E388348@standardstrack.com> <CAKHUCzzzT-0p89uT62zrxGqF1XACG+Ok7hNLcuTaDad7R7eCTQ@mail.gmail.com> <01P0GHNIIOYE00004G@mauve.mrochek.com>
Date: Thu, 7 Nov 2013 11:25:37 +0000
Message-ID: <CAKHUCzwU=yjb1yZ4Yi3gd5NV0eX0AfuSw4VRz09KyqTvi7OFKg@mail.gmail.com>
Subject: Re: https at ietf.org
From: Dave Cridland <dave@cridland.net>
To: Ned Freed <ned.freed@mrochek.com>
Content-Type: multipart/alternative; boundary=089e0149401a67e39b04ea948658
Cc: IETF-Discussion Discussion <ietf@ietf.org>, Eric Burger <eburger@standardstrack.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 07 Nov 2013 11:25:43 -0000

On Wed, Nov 6, 2013 at 3:01 PM, Ned Freed <ned.freed@mrochek.com> wrote:

> > Allowing HTTPS, on the other hand, does not. Unfortunately, because of
> the
> > nature of HTTP/HTTPS, we cannot perform opportunistic encryption in the
> > same way as with the mail and XMPP services we use.
>
> Perhaps that is a problem that deserves further attention.
>

It would mean getting UA and server support for RFC 2817, though.

Dave.