IETF Logo Mail Archive

Re: https at ietf.org

Carsten Bormann <cabo@tzi.org> Thu, 07 November 2013 06:37 UTC

Return-Path: <cabo@tzi.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 D1E0011E8189 for <ietf@ietfa.amsl.com>; Wed, 6 Nov 2013 22:37:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.348
X-Spam-Level:
X-Spam-Status: No, score=-106.348 tagged_above=-999 required=5 tests=[AWL=-0.099, BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 14KNtjvZujqO for <ietf@ietfa.amsl.com>; Wed, 6 Nov 2013 22:37:17 -0800 (PST)
Received: from informatik.uni-bremen.de (mailhost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::12]) by ietfa.amsl.com (Postfix) with ESMTP id 8386321E80B1 for <ietf@ietf.org>; Wed, 6 Nov 2013 22:37:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from smtp-fb3.informatik.uni-bremen.de (smtp-fb3.informatik.uni-bremen.de [134.102.224.120]) by informatik.uni-bremen.de (8.14.4/8.14.4) with ESMTP id rA76b1eX025789; Thu, 7 Nov 2013 07:37:01 +0100 (CET)
Received: from dhcp-9334.meeting.ietf.org (dhcp-9334.meeting.ietf.org [31.133.147.52]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp-fb3.informatik.uni-bremen.de (Postfix) with ESMTPSA id 539C149B; Thu, 7 Nov 2013 07:36:58 +0100 (CET)
Subject: Re: https at ietf.org
Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1816\))
Content-Type: text/plain; charset="windows-1252"
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <D30A3FE8-8751-409B-A0D5-E5F82BB80D88@nominum.com>
Date: Wed, 06 Nov 2013 22:36:55 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <FB59737F-3D0A-42EF-9609-2910AFD754BB@tzi.org>
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> <EA2A8649-F8E6-4802-BDD7-AD593D387B9D@nominum.com> <D571EF71-FEFB-49F6-890F-78791EF3FCA7@tzi.org> <D30A3FE8-8751-409B-A0D5-E5F82BB80D88@nominum.com>
To: Ted Lemon <Ted.Lemon@nominum.com>
X-Mailer: Apple Mail (2.1816)
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 06:37:28 -0000

On 06 Nov 2013, at 21:42, Ted Lemon <Ted.Lemon@nominum.com> wrote:

>> For privacy, though, STASI*) should not be able to find out that I’m retrieving RFC 1984 so that they can't identify me as a long-haired bomb-throwing leftist (or whatever retrieving RFC 1984 makes you in their minds).
> 
> 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.

Grüße, Carsten

v2.23.0 | Report a Bug | By Email