Re: https at ietf.org

"MAISONNEUVE, JULIEN (JULIEN)" <julien.maisonneuve@alcatel-lucent.com> Wed, 06 November 2013 02:46 UTC

Return-Path: <julien.maisonneuve@alcatel-lucent.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 B0F5A11E81E0 for <ietf@ietfa.amsl.com>; Tue, 5 Nov 2013 18:46:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.598
X-Spam-Level:
X-Spam-Status: No, score=-10.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, 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 KE1g1jQxGitp for <ietf@ietfa.amsl.com>; Tue, 5 Nov 2013 18:45:55 -0800 (PST)
Received: from ihemail4.lucent.com (ihemail4.lucent.com [135.245.0.39]) by ietfa.amsl.com (Postfix) with ESMTP id 581DB21E80B2 for <ietf@ietf.org>; Tue, 5 Nov 2013 18:45:55 -0800 (PST)
Received: from fr712usmtp2.zeu.alcatel-lucent.com (h135-239-2-42.lucent.com [135.239.2.42]) by ihemail4.lucent.com (8.13.8/IER-o) with ESMTP id rA62jp3s028260 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Tue, 5 Nov 2013 20:45:52 -0600 (CST)
Received: from FR711WXCHHUB02.zeu.alcatel-lucent.com (fr711wxchhub02.zeu.alcatel-lucent.com [135.239.2.112]) by fr712usmtp2.zeu.alcatel-lucent.com (GMO) with ESMTP id rA62joSg020167 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 6 Nov 2013 03:45:50 +0100
Received: from FR712WXCHMBA12.zeu.alcatel-lucent.com ([169.254.8.36]) by FR711WXCHHUB02.zeu.alcatel-lucent.com ([135.239.2.112]) with mapi id 14.02.0247.003; Wed, 6 Nov 2013 03:45:50 +0100
From: "MAISONNEUVE, JULIEN (JULIEN)" <julien.maisonneuve@alcatel-lucent.com>
To: Tim Bray <tbray@textuality.com>
Subject: Re: https at ietf.org
Thread-Topic: https at ietf.org
Thread-Index: AQHO2pbmqAtjwiEgQkmxBro8u1z5SpoXa6UAgAATx7o=
Date: Wed, 06 Nov 2013 02:45:49 +0000
Message-ID: <0F7031AB-394D-4C72-90FA-20DCB99D2CCD@alcatel-lucent.com>
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>
In-Reply-To: <CAHBU6ivZS33r4HHbCC391Ug9fMtZkJ3nojEeeqH5L+0+o3ZqGQ@mail.gmail.com>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Content-Type: multipart/alternative; boundary="_000_0F7031AB394D4C7290FA20DCB99D2CCDalcatellucentcom_"
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.39
X-Mailman-Approved-At: Wed, 06 Nov 2013 09:48:55 -0800
Cc: "ned+ietf@mauve.mrochek.com" <ned+ietf@mauve.mrochek.com>, 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:46:00 -0000

Unfortunately there are scénarios in which you have the adéquate agent but not the corresponding proxy.

(JM, ex mobilum)

Le 5 nov. 2013 à 18:35, "Tim Bray" <tbray@textuality.com<mailto:tbray@textuality.com>> a écrit :

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<mailto: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