IETF Logo Mail Archive

Re: https at ietf.org

Ted Lemon <Ted.Lemon@nominum.com> Thu, 07 November 2013 05:42 UTC

Return-Path: <Ted.Lemon@nominum.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 8EB8B11E81F9 for <ietf@ietfa.amsl.com>; Wed, 6 Nov 2013 21:42:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.589
X-Spam-Level:
X-Spam-Status: No, score=-106.589 tagged_above=-999 required=5 tests=[AWL=0.010, BAYES_00=-2.599, 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 D-iQXQdezXk8 for <ietf@ietfa.amsl.com>; Wed, 6 Nov 2013 21:42:10 -0800 (PST)
Received: from exprod7og108.obsmtp.com (exprod7og108.obsmtp.com [64.18.2.169]) by ietfa.amsl.com (Postfix) with ESMTP id 5B6F121F8DA3 for <ietf@ietf.org>; Wed, 6 Nov 2013 21:42:10 -0800 (PST)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob108.postini.com ([64.18.6.12]) with SMTP ID DSNKUnsoMH/sZ4/CXioT97uuL0CcK/XbJXJK@postini.com; Wed, 06 Nov 2013 21:42:10 PST
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 5B4C31B82C3 for <ietf@ietf.org>; Wed, 6 Nov 2013 21:42:08 -0800 (PST)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id 390AB190043; Wed, 6 Nov 2013 21:42:08 -0800 (PST) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-01.WIN.NOMINUM.COM ([64.89.228.131]) with mapi id 14.03.0158.001; Wed, 6 Nov 2013 21:42:02 -0800
From: Ted Lemon <Ted.Lemon@nominum.com>
To: Carsten Bormann <cabo@tzi.org>
Subject: Re: https at ietf.org
Thread-Topic: https at ietf.org
Thread-Index: AQHO2qIaRBarL/JKSEG/1rV78IBalZoYl5IAgAADF4CAACnmgIABADiAgAAEOwA=
Date: Thu, 07 Nov 2013 05:42:01 +0000
Message-ID: <D30A3FE8-8751-409B-A0D5-E5F82BB80D88@nominum.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> <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>
In-Reply-To: <D571EF71-FEFB-49F6-890F-78791EF3FCA7@tzi.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [192.168.1.10]
Content-Type: text/plain; charset="Windows-1252"
Content-ID: <09BDE6CE935BA64CA4710D0B8BC5F95D@nominum.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
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 05:42:16 -0000

On Nov 6, 2013, at 9:26 PM, Carsten Bormann <cabo@tzi.org> wrote:
> If that were the problem we are addressing, the best answer would involve RFC 6920.

No, that's not what I want, although it is a neat hack.

> 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.

v2.23.0 | Report a Bug | By Email