IETF Logo Mail Archive

Re: https at ietf.org

mrex@sap.com (Martin Rex) Fri, 08 November 2013 02:01 UTC

Return-Path: <mrex@sap.com>
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 17E9F11E8205 for <ietf@ietfa.amsl.com>; Thu, 7 Nov 2013 18:01:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.139
X-Spam-Level:
X-Spam-Status: No, score=-10.139 tagged_above=-999 required=5 tests=[AWL=0.110, BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_HI=-8]
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 JeZU8ES0vXOj for <ietf@ietfa.amsl.com>; Thu, 7 Nov 2013 18:01:37 -0800 (PST)
Received: from smtpde01.sap-ag.de (smtpde01.sap-ag.de [155.56.68.170]) by ietfa.amsl.com (Postfix) with ESMTP id 924F211E8204 for <ietf@ietf.org>; Thu, 7 Nov 2013 18:01:27 -0800 (PST)
Received: from mail06.wdf.sap.corp by smtpde01.sap-ag.de (26) with ESMTP id rA820XAW001164 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 8 Nov 2013 03:00:33 +0100 (MET)
Subject: Re: https at ietf.org
In-Reply-To: <527C2233.3030605@cis-india.org>
To: Pranesh Prakash <pranesh@cis-india.org>
Date: Fri, 08 Nov 2013 03:00:33 +0100
X-Mailer: ELM [version 2.4ME+ PL125 (25)]
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="US-ASCII"
Message-Id: <20131108020033.5CA851AA6A@ld9781.wdf.sap.corp>
From: mrex@sap.com
X-SAP: out
Cc: IETF-Discussion Discussion <ietf@ietf.org>, Eric Burger <eburger@standardstrack.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: mrex@sap.com
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: Fri, 08 Nov 2013 02:01:42 -0000

Pranesh Prakash wrote:

> Dave Cridland [2013-11-06 06:39]:
>
>> Requiring HTTPS, particularly with reasonable cipher suites,
>> might restrict use of from certain jurisdictions.
> 
> Could we have more concrete examples, please?

A significant number of IETF documents (including BCP 78)
contain this statement:

   Distribution of this memo is unlimited.

_Restricting_ access to such documents on the www.ietf.org/tools.ietf.org
to HTTPS only seems to be incompatible with this fundamental principle.

Like prohibiting to put RFC on open bookshelves in public libraries
because other folks could see you taking it out of the shelve.

-Martin

v2.23.0 | Report a Bug | By Email