Re: https at ietf.org

Måns Nilsson <mansaxel@besserwisser.org> Thu, 07 November 2013 08:02 UTC

Return-Path: <mansaxel@besserwisser.org>
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 0E52F21E80D5 for <ietf@ietfa.amsl.com>; Thu, 7 Nov 2013 00:02:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.3
X-Spam-Level:
X-Spam-Status: No, score=-2.3 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, 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 0Dv0GMqcQ1Ts for <ietf@ietfa.amsl.com>; Thu, 7 Nov 2013 00:02:10 -0800 (PST)
Received: from jaja.besserwisser.org (jaja.besserwisser.org [IPv6:2a01:298:4:0:211:43ff:fe36:1299]) by ietfa.amsl.com (Postfix) with ESMTP id 7403F21E80D4 for <ietf@ietf.org>; Thu, 7 Nov 2013 00:02:10 -0800 (PST)
Received: by jaja.besserwisser.org (Postfix, from userid 1004) id 9ED1D9D1A; Thu, 7 Nov 2013 09:02:09 +0100 (CET)
Date: Thu, 7 Nov 2013 09:02:09 +0100
From: =?utf-8?B?TcOlbnM=?= Nilsson <mansaxel@besserwisser.org>
To: Carsten Bormann <cabo@tzi.org>
Subject: Re: https at ietf.org
Message-ID: <20131107080209.GG21546@besserwisser.org>
References: <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> <EA2A8649-F8E6-4802-BDD7-AD593D387B9D@nominum.com> <D571EF71-FEFB-49F6-890F-78791EF3FCA7@tzi.org> <D30A3FE8-8751-409B-A0D5-E5F82BB80D88@nominum.com> <FB59737F-3D0A-42EF-9609-2910AFD754BB@tzi.org>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="GV0iVqYguTV4Q9ER"
Content-Disposition: inline
In-Reply-To: <FB59737F-3D0A-42EF-9609-2910AFD754BB@tzi.org>
X-URL: http://vvv.besserwisser.org
X-Purpose: More of everything NOW!
X-happyness: Life is good.
User-Agent: Mutt/1.5.20 (2009-06-14)
Cc: IETF-Discussion Discussion <ietf@ietf.org>
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 08:02:11 -0000

Subject: Re: https at ietf.org Date: Wed, Nov 06, 2013 at 10:36:55PM -0800 Quoting Carsten Bormann (cabo@tzi.org):
> > If you want encryption, definitely you should be able to get it, and indeed with ietf.org, you can.
> 
> No, I want privacy, and all my right-thinking crew-cut friends are using http://ietf.org, so I still stand out for STASI when I’m using https://ietf.org.
> 
> The whole debate is not so much about whether privacy is really needed for accessing the IETF site (not really that much) but about whether we want to lead by example.  I think we want to expose the browsable parts of the site such as the front page by https only, but keep tools access for constructible URIs such as http://tools.ietf.org/id/{draft-name}.  And rsync of course.  FTP is legacy anyways.

++;

-- 
Måns Nilsson     primary/secondary/besserwisser/machina
MN-1334-RIPE                             +46 705 989668
Used staples are good with SOY SAUCE!