Re: Proposed Statement on "HTTPS everywhere for the IETF"

S Moonesamy <sm+ietf@elandsys.com> Tue, 02 June 2015 00:57 UTC

Return-Path: <sm@elandsys.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8B0F71A8720 for <ietf@ietfa.amsl.com>; Mon, 1 Jun 2015 17:57:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.01
X-Spam-Level:
X-Spam-Status: No, score=-2.01 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, T_RP_MATCHES_RCVD=-0.01] 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 TW44UriL3417 for <ietf@ietfa.amsl.com>; Mon, 1 Jun 2015 17:57:36 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id E3B471A6FFA for <ietf@ietf.org>; Mon, 1 Jun 2015 17:57:35 -0700 (PDT)
Received: from SUBMAN.elandsys.com ([197.227.200.226]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id t520vND7002111 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Mon, 1 Jun 2015 17:57:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1433206654; x=1433293054; bh=3dMmAkvc7XZibwrXliVIuzRRsstVJemFAcziyMlqyZs=; h=Date:To:From:Subject:In-Reply-To:References; b=4lCagYMcDBhoLVAccAUbDTdIYR4ZCaCPB+YDwvTZAnOsaWxHhhTTUD+wdoayoG2bM NWGUhyMIFNZnqOPHU8H0iE9kxtTDaVJ5dlfelvADUPntr4QagAQ2WkoEKF4XXqkrBq amw1KbepDDZ/1yuFyAjr5kKd/3pIHJ2WhTn55dKM=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1433206654; x=1433293054; i=@elandsys.com; bh=3dMmAkvc7XZibwrXliVIuzRRsstVJemFAcziyMlqyZs=; h=Date:To:From:Subject:In-Reply-To:References; b=T1Ki5/GCcJbr1eOHl0o+pSXrgsz9Qh0Jbaim8i+mLoxiwOR9mFsaLkoXVSyFt342G mWTTEv5wFAe318bZXL01r9VTHxT24FB2afMwMgaHDleEA9idOIB5oKSYXajt7UHZUq b5toYcDph/hCVBN6nVxyaAl9UDLUsZtQlSsYWYQI=
Message-Id: <6.2.5.6.2.20150601164015.0e3fef48@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Mon, 01 Jun 2015 17:54:26 -0700
To: ietf@ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: Proposed Statement on "HTTPS everywhere for the IETF"
In-Reply-To: <20150601164359.29999.35343.idtracker@ietfa.amsl.com>
References: <20150601164359.29999.35343.idtracker@ietfa.amsl.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/IRWk7yu550FBofjvUAL0cZ9Qt4E>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
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: Tue, 02 Jun 2015 00:57:37 -0000

At 09:43 01-06-2015, The IESG wrote:
>The IESG are planning to agree an IESG statement on "HTTPS Everywhere
>for the IETF," please see [1] for the current text.

The rules for "HTTPS Everywhere" are:

   from "^http://(www\.)?ietf\.org/" to "https://www.ietf.org/"
   from "^http://(tools|datatracker)\.ietf\.org/" to "https://$1.ietf.org/"

My reading of the proposed statement is that "all IETF information 
must, by default, be made available in a privacy friendly form" 
(HTTPS [1]) and that "all links to such information (e.g. href's in 
html) should default to causing access via" HTTPS [1].  Is the first 
part of that some kind of rewrite rule on the server-side?

I did a quick test by accessing www.ietf.org and it took about two 
seconds without the "S" and about seven seconds with the "S".  The 
extra seconds is a bit slow but it is okay if the objective is to 
have some confidentiality.  The note in the proposed statement covers 
more than the title of the proposed statement.

Regards,
S. Moonesamy

1. HTTPS URIs and appropriate TLS cipher-suites