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

Xiaoyin Liu <> Tue, 02 June 2015 09:37 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id E4F261A9098 for <>; Tue, 2 Jun 2015 02:37:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: 1.001
X-Spam-Level: *
X-Spam-Status: No, score=1.001 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, FREEMAIL_FROM=0.001, HK_RANDOM_ENVFROM=0.001, HK_RANDOM_FROM=1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id tsO-V_wYTlbi for <>; Tue, 2 Jun 2015 02:37:47 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 6A1B31A9097 for <>; Tue, 2 Jun 2015 02:37:47 -0700 (PDT)
Received: from BAY180-W54 ([]) by over TLS secured channel with Microsoft SMTPSVC(7.5.7601.22751); Tue, 2 Jun 2015 02:37:47 -0700
X-TMN: [e5oTtlgI1x8Nzp5wi8Wv4B2h0HmfSVtN]
X-Originating-Email: []
Message-ID: <BAY180-W5419C8EA8F03D7995A568BFFB50@phx.gbl>
Content-Type: multipart/alternative; boundary="_7bccda10-009f-4083-b1ea-be580d7ab51b_"
From: Xiaoyin Liu <>
To: "" <>
Subject: Re: Proposed Statement on "HTTPS everywhere for the IETF"
Date: Tue, 2 Jun 2015 05:37:46 -0400
Importance: Normal
MIME-Version: 1.0
X-OriginalArrivalTime: 02 Jun 2015 09:37:47.0495 (UTC) FILETIME=[C8F36F70:01D09D17]
Archived-At: <>
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 02 Jun 2015 09:37:49 -0000

I support this IESG statement. Here are my suggestions on how to implement this statement:
1) Fix all the mixed content issues on the IETF websites, such as, which contains JavaScript loaded from
2) Change all hardcoded http links to protocol relative or https, such as the "List Archive" link on [1].
3) Add <link rel="canonical" href="https://..."> to every page, so that search engines will prefer to index HTTPS links.[2][3]
4) Enable HTTP Strict Transport Security for every IETF subdomains, and submit to the HSTS preload list.[4] I know that the IESG still wants cleartext content to be available. But I think HSTS is very important. There are many HTTP links to IETF on the Internet, such as those on our mailing lists, that are unlikely to update regardless of this statement. HSTS can help in this case. People using non-browser clients, IE, and old phone browsers are not affected by HSTS.
5) Please ask the RFC Editor Team to update their website ( according to this IESG statement as well. Currently there is no way to submit or view RFC errata over HTTPS. redirects to
Xiaoyin Liu