Re: Last Call: Recognising RFC1984 as a BCP

Harald Alvestrand <harald@alvestrand.no> Thu, 13 August 2015 05:31 UTC

Return-Path: <harald@alvestrand.no>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 977731B2A9E for <ietf@ietfa.amsl.com>; Wed, 12 Aug 2015 22:31:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.21
X-Spam-Level:
X-Spam-Status: No, score=-4.21 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FgDWwyFrVtPx for <ietf@ietfa.amsl.com>; Wed, 12 Aug 2015 22:31:49 -0700 (PDT)
Received: from mork.alvestrand.no (mork.alvestrand.no [158.38.152.117]) by ietfa.amsl.com (Postfix) with ESMTP id 7C7C01B2A9C for <ietf@ietf.org>; Wed, 12 Aug 2015 22:31:49 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mork.alvestrand.no (Postfix) with ESMTP id 954357C5371 for <ietf@ietf.org>; Thu, 13 Aug 2015 07:31:47 +0200 (CEST)
X-Virus-Scanned: Debian amavisd-new at alvestrand.no
Received: from mork.alvestrand.no ([127.0.0.1]) by localhost (mork.alvestrand.no [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9ytAOU8S5CWb for <ietf@ietf.org>; Thu, 13 Aug 2015 07:31:46 +0200 (CEST)
Received: from [IPv6:2001:470:de0a:27:71e7:a24f:297e:e2c3] (unknown [IPv6:2001:470:de0a:27:71e7:a24f:297e:e2c3]) by mork.alvestrand.no (Postfix) with ESMTPSA id 83CA47C3D85 for <ietf@ietf.org>; Thu, 13 Aug 2015 07:31:46 +0200 (CEST)
Message-ID: <55CC2BC2.8010002@alvestrand.no>
Date: Thu, 13 Aug 2015 07:31:46 +0200
From: Harald Alvestrand <harald@alvestrand.no>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.8.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Last Call: Recognising RFC1984 as a BCP
References: <20150810171306.11047.24159.idtracker@ietfa.amsl.com> <55C9070B.1050407@dcrocker.net> <55C9E1F7.7080900@cs.tcd.ie> <68BD9E21-5343-4D69-8A5F-FEA3F07CCC89@gbiv.com> <55CBBF4E.80006@alvestrand.no> <49F36C84-DD27-4932-8F5B-10A227104C2D@gbiv.com>
In-Reply-To: <49F36C84-DD27-4932-8F5B-10A227104C2D@gbiv.com>
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/uKMUGj8cdqxP4dlorB_UvhJ0lhQ>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
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: <https://mailarchive.ietf.org/arch/browse/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, 13 Aug 2015 05:31:51 -0000

Den 13. aug. 2015 01:31, skrev Roy T. Fielding:
>> On Aug 12, 2015, at 2:49 PM, Harald Alvestrand <harald@alvestrand.no> wrote:
>>
>> On 08/12/2015 11:02 PM, Roy T. Fielding wrote:
>>> The reason I read it that way is because, in fact, none of the protocols
>>> we developed at that time actually required strong cryptography.  They
>>> just assumed you would layer the right amount of cryptography underneath,
>>> using one of the (at that time) non-IETF security protocols with appropriate
>>> patent and export licensing.
>> I was in the room at the Danvers plenary, and that was not the
>> impression I got.
>> In particular, at that time many people believed very strongly that
>> IPSEC, an IETF protocol, would be THE most useful tool for achieving
>> security, once it was finished.
> 
> Yes, certainly.  But, IPsec didn't require strong encryption be used;
> it required an MTI algorithm of 56bit DES-CBC.  IPsec had algorithm and
> key length options, like everything else at the time.

At that time, 56bit DES-CBC was considered strong per the export rules.
What we were fighting against was 40bit RC4.