IETF Logo Mail Archive

Re: https at ietf.org

David Morris <dwm@xpasc.com> Wed, 06 November 2013 01:37 UTC

Return-Path: <dwm@xpasc.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 A138F21E8122 for <ietf@ietfa.amsl.com>; Tue, 5 Nov 2013 17:37:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.877
X-Spam-Level:
X-Spam-Status: No, score=-3.877 tagged_above=-999 required=5 tests=[AWL=-4.316, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, IP_NOT_FRIENDLY=0.334, J_CHICKENPOX_61=0.6, RDNS_NONE=0.1]
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 EF9lVR7nLiN5 for <ietf@ietfa.amsl.com>; Tue, 5 Nov 2013 17:37:27 -0800 (PST)
Received: from c2w3p-2.abacamail.com (unknown [67.231.154.153]) by ietfa.amsl.com (Postfix) with ESMTP id E65A421F8FDC for <ietf@ietf.org>; Tue, 5 Nov 2013 17:35:58 -0800 (PST)
Received: from xpasc.com (h-68-164-244-188.snva.ca.megapath.net [68.164.244.188]) by c2w3p-2.abacamail.com (Postfix) with ESMTP id 7941540544 for <ietf@ietf.org>; Wed, 6 Nov 2013 01:35:44 +0000 (UTC)
Received: from egate.xpasc.com (egate.xpasc.com [10.1.2.49]) by xpasc.com (8.13.8/8.13.8) with ESMTP id rA61ZdRU004248 for <ietf@ietf.org>; Tue, 5 Nov 2013 17:35:39 -0800
Date: Tue, 05 Nov 2013 17:35:39 -0800
From: David Morris <dwm@xpasc.com>
To: IETF-Discussion Discussion <ietf@ietf.org>
Subject: Re: https at ietf.org
In-Reply-To: <CAHBU6ivbrk=NXgd4_5Upik+8H0AbHRy3kJnN=8fcK+Bz3pOV9Q@mail.gmail.com>
Message-ID: <alpine.LRH.2.01.1311051733570.4200@egate.xpasc.com>
References: <CAHBU6ivbrk=NXgd4_5Upik+8H0AbHRy3kJnN=8fcK+Bz3pOV9Q@mail.gmail.com>
User-Agent: Alpine 2.01 (LRH 1266 2009-07-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: IETF-Discussion Discussion <ietf@ietf.org>
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, 06 Nov 2013 01:37:41 -0000

I don't see reason to use https for delivery of public documents such
as RFCs and Internet Drafts. All that would really accomplish is
reduce caching opportunities.

On Tue, 5 Nov 2013, Tim Bray wrote:

> Wouldn?t it be a good idea for everything at *.ietf.org to be served by
> HTTPS, and only by HTTPS?
>

v2.23.0 | Report a Bug | By Email