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

t.p. <daedulus@btconnect.com> Wed, 03 June 2015 11:26 UTC

Return-Path: <daedulus@btconnect.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 8FFC91A1B98 for <ietf@ietfa.amsl.com>; Wed, 3 Jun 2015 04:26:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001] 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 kCbaxu_WHT8f for <ietf@ietfa.amsl.com>; Wed, 3 Jun 2015 04:26:23 -0700 (PDT)
Received: from emea01-am1-obe.outbound.protection.outlook.com (mail-am1on0719.outbound.protection.outlook.com [IPv6:2a01:111:f400:fe00::719]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B90181A1BAC for <ietf@ietf.org>; Wed, 3 Jun 2015 04:26:22 -0700 (PDT)
Received: from AM3PR07MB241.eurprd07.prod.outlook.com (10.242.18.139) by AM3PR07MB339.eurprd07.prod.outlook.com (10.242.109.24) with Microsoft SMTP Server (TLS) id 15.1.172.22; Wed, 3 Jun 2015 11:26:06 +0000
Authentication-Results: spf=none (sender IP is ) smtp.mailfrom=daedulus@btconnect.com;
Received: from pc6 (81.151.162.168) by AM3PR07MB241.eurprd07.prod.outlook.com (10.242.18.139) with Microsoft SMTP Server (TLS) id 15.1.184.17; Wed, 3 Jun 2015 11:26:05 +0000
Message-ID: <02e601d09def$bdacafe0$4001a8c0@gateway.2wire.net>
From: t.p. <daedulus@btconnect.com>
To: <stbryant@cisco.com>, <ietf@ietf.org>
References: <20150601164359.29999.35343.idtracker@ietfa.amsl.com> <CAL02cgRPFooA5fVFwvdprb3wPD+Y55pD+7RWjkACDv7T_TBW5Q@mail.gmail.com> <556DE0EF.2040809@isi.edu> <FE9A2408-555C-4B06-9009-D6C1D93356B4@nominum.com> <556DF072.4030202@isi.edu> <556EC6F9.9010801@cisco.com>
Subject: Re: Proposed Statement on "HTTPS everywhere for the IETF"
Date: Wed, 3 Jun 2015 11:56:01 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Originating-IP: [81.151.162.168]
X-ClientProxiedBy: AM3PR03CA048.eurprd03.prod.outlook.com (10.141.191.176) To AM3PR07MB241.eurprd07.prod.outlook.com (10.242.18.139)
X-Microsoft-Antispam: UriScan:; BCL:0; PCL:0; RULEID:; SRVR:AM3PR07MB241; UriScan:; BCL:0; PCL:0; RULEID:; SRVR:AM3PR07MB339;
X-Microsoft-Antispam-PRVS: <AM3PR07MB241CE79118DA03BD3F5E640C6B40@AM3PR07MB241.eurprd07.prod.outlook.com>
X-Exchange-Antispam-Report-Test: UriScan:;
X-Exchange-Antispam-Report-CFA-Test: BCL:0; PCL:0; RULEID:(601004)(520003)(5005006)(3002001); SRVR:AM3PR07MB241; BCL:0; PCL:0; RULEID:; SRVR:AM3PR07MB241;
X-Forefront-PRVS: 05961EBAFC
X-Forefront-Antispam-Report: SFV:NSPM; SFS:(10019020)(979002)(6009001)(13464003)(377454003)(479174004)(24454002)(189002)(51704005)(199003)(68736005)(92566002)(62966003)(1720100001)(40100003)(77156002)(122386002)(101416001)(42186005)(14496001)(19273905006)(77096005)(189998001)(66066001)(5001960100002)(50986999)(64706001)(47776003)(81686999)(76176999)(107886002)(106356001)(19580405001)(81816999)(116806002)(19580395003)(15975445007)(5001770100001)(105586002)(5001830100001)(5001860100001)(4001540100001)(81156007)(97736004)(87976001)(1556002)(50226001)(62236002)(84392001)(44736004)(93886004)(23746002)(61296003)(1456003)(33646002)(44716002)(46102003)(86362001)(50466002)(74416001)(7726001)(563064011)(969003)(989001)(999001)(1009001)(1019001); DIR:OUT; SFP:1102; SCL:1; SRVR:AM3PR07MB241; H:pc6; FPR:; SPF:None; PTR:InfoNoRecords; MX:1; A:0; LANG:en;
Received-SPF: None (protection.outlook.com: btconnect.com does not designate permitted sender hosts)
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 03 Jun 2015 11:26:05.1958 (UTC)
X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM3PR07MB241
X-OriginatorOrg: btconnect.com
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/ujcQJ4ERLhyVfKwTzLIaNAWfRp4>
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: Wed, 03 Jun 2015 11:26:25 -0000

----- Original Message -----
From: "Stewart Bryant" <stbryant@cisco.com>
To: <ietf@ietf.org>
Sent: Wednesday, June 03, 2015 10:20 AM
> On 02/06/2015 19:05, Joe Touch wrote:
> >
> > On 6/2/2015 11:02 AM, Ted Lemon wrote:
> >> On Jun 2, 2015, at 12:59 PM, Joe Touch <touch@isi.edu> wrote:
> >>> Leaving out the have-nots - or those whose access is blocked by
others
> >>> when content cannot be scanned - isn't moving forward.
> >> That would certainly be a problem if the consensus were not to
> >> provide both a secure and an, as you call it, "open" version of all
IETF documents.
> > The IETF is more than just the documents.
> >
> > All IETF content should be accessible via non-secure means.
> >
> > Joe
> >
> >
> s/should/MUST/

Which I don't think is the case at present.

I have never managed to get
http://www.ietf.org/mailman/listinfo/ietf
to resolve to anything other than a blank screen.
https://www.ietf.org/mailman/listinfo/ietf
works as I would expect it to.

Information on other mailing lists and their archives that I look at I
can access with http: (even if the IETF website first offers me https:).

Tom Petch

> Stewart
>