IETF Logo Mail Archive

Re: https at ietf.org

Tim Bray <tbray@textuality.com> Wed, 06 November 2013 02:35 UTC

Return-Path: <tbray@textuality.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 D41B411E8163 for <ietf@ietfa.amsl.com>; Tue, 5 Nov 2013 18:35:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.005
X-Spam-Level:
X-Spam-Status: No, score=-3.005 tagged_above=-999 required=5 tests=[AWL=-0.029, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-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 GLcira6FIGL3 for <ietf@ietfa.amsl.com>; Tue, 5 Nov 2013 18:35:03 -0800 (PST)
Received: from mail-ve0-f176.google.com (mail-ve0-f176.google.com [209.85.128.176]) by ietfa.amsl.com (Postfix) with ESMTP id 0CA9A21E80FA for <ietf@ietf.org>; Tue, 5 Nov 2013 18:35:02 -0800 (PST)
Received: by mail-ve0-f176.google.com with SMTP id jx11so3110635veb.21 for <ietf@ietf.org>; Tue, 05 Nov 2013 18:35:02 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=3ESji3v+OzlQhHrowu1ax7BlxKCAW1HcTzc/gFf4fiQ=; b=dpCQlTxgPg7tL8ifsrMQJVXPKii9QPwk/qGfpdsNsNplvVlFGdF4heZYqhJfUxH55J CR2BVTd+n+pi3z+4K4Yn6Yx2nS+YOOlhvP4u6SsdocmQ6qwp5giLXQxW+EHNR7MapCIs 5gEKZx8+EveNb0a+UxZenxW8dVhb4HjbL6llsOu+0oLutch/pi891fc4TUWBToYSJC7T NxPbCOVlBvKkpAPl0/AfhT+qwimgpifbAvfo7unm1BTY33t2dEoyiADSDflHeSK9ATLZ KAtX09devz3rtwncyvADN1OFjwWBW4eRA8eYidK86U4uaSUdyGYhxJj2qsDu9vfjmjRM cB5Q==
X-Gm-Message-State: ALoCoQnfMqNCJzcWExgYl94EooYoAimo0fMrwJ0Vh1OkcsDAw0fkIZHwFsYVgACohzxKxlfw5G+P
MIME-Version: 1.0
X-Received: by 10.52.233.2 with SMTP id ts2mr31483vdc.44.1383705302323; Tue, 05 Nov 2013 18:35:02 -0800 (PST)
Received: by 10.220.110.134 with HTTP; Tue, 5 Nov 2013 18:35:02 -0800 (PST)
X-Originating-IP: [24.84.235.32]
In-Reply-To: <01P0FR4HDQNG00004G@mauve.mrochek.com>
References: <CAHBU6ivbrk=NXgd4_5Upik+8H0AbHRy3kJnN=8fcK+Bz3pOV9Q@mail.gmail.com> <alpine.LRH.2.01.1311051733570.4200@egate.xpasc.com> <01P0FR4HDQNG00004G@mauve.mrochek.com>
Date: Tue, 05 Nov 2013 18:35:02 -0800
Message-ID: <CAHBU6ivZS33r4HHbCC391Ug9fMtZkJ3nojEeeqH5L+0+o3ZqGQ@mail.gmail.com>
Subject: Re: https at ietf.org
From: Tim Bray <tbray@textuality.com>
To: ned+ietf@mauve.mrochek.com
Content-Type: multipart/alternative; boundary="089e0111bbe404ea7704ea78ffb1"
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: Wed, 06 Nov 2013 02:35:11 -0000

I disagree. I can’t think of an scenario in which a human who wants/needs
to use IETF publications would not have access to an HTTPS-capable user
agent.  -T


On Tue, Nov 5, 2013 at 6:21 PM, <ned+ietf@mauve.mrochek.com> wrote:

>
> > 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.
>
> I don't have any problem with making things available via https, but it
> needs
> to be possible to retrieve things with regular http. Not everything gets
> retrieved by a browser and not every tool out there supports https.
>
>                                 Ned
>

v2.23.0 | Report a Bug | By Email