Re: [perpass] NULL Cipher RFC 2410 to HISTORIC ???
Paul Ferguson <fergdawgster@mykolab.com> Mon, 09 December 2013 20:52 UTC
Return-Path: <fergdawgster@mykolab.com>
X-Original-To: perpass@ietfa.amsl.com
Delivered-To: perpass@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0819D1AE0A6 for <perpass@ietfa.amsl.com>; Mon, 9 Dec 2013 12:52:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.901
X-Spam-Level:
X-Spam-Status: No, score=-0.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, FREEMAIL_REPLYTO=1, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=no
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 W3TA9CPR5XjX for <perpass@ietfa.amsl.com>; Mon, 9 Dec 2013 12:52:30 -0800 (PST)
Received: from mx01.mykolab.com (mx01.mykolab.com [95.128.36.1]) by ietfa.amsl.com (Postfix) with ESMTP id 08DDD1AE06F for <perpass@ietf.org>; Mon, 9 Dec 2013 12:52:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at kolabsys.net
Sender: fergdawgster@mykolab.com
Message-ID: <52A62D80.5010504@mykolab.com>
Date: Mon, 09 Dec 2013 12:52:16 -0800
From: Paul Ferguson <fergdawgster@mykolab.com>
Organization: Clowns R. Mofos
To: Phillip Hallam-Baker <hallam@gmail.com>
References: <CAMm+LwijWwanC+KLaSC-Kgq4vP=8in8Juo2Gbd=URh4zVf55nA@mail.gmail.com> <52A5D9C5.1050700@bbn.com> <CAMm+LwgfXVc=ED7piSnoPrZPTs_Y+m5ShxJcEbSAXF4DsFoo4g@mail.gmail.com>
In-Reply-To: <CAMm+LwgfXVc=ED7piSnoPrZPTs_Y+m5ShxJcEbSAXF4DsFoo4g@mail.gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: perpass <perpass@ietf.org>
Subject: Re: [perpass] NULL Cipher RFC 2410 to HISTORIC ???
X-BeenThere: perpass@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: fergdawgster@mykolab.com
List-Id: "The perpass list is for IETF discussion of pervasive monitoring. " <perpass.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/perpass>, <mailto:perpass-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/perpass/>
List-Post: <mailto:perpass@ietf.org>
List-Help: <mailto:perpass-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/perpass>, <mailto:perpass-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 09 Dec 2013 20:52:32 -0000
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Below: On 12/9/2013 10:05 AM, Phillip Hallam-Baker wrote: > > > > On Mon, Dec 9, 2013 at 9:55 AM, Stephen Kent <kent@bbn.com > <mailto:kent@bbn.com>> wrote: > > Phillip, > >> On Sun, Dec 8, 2013 at 5:00 PM, Hannes Tschofenig >> <hannes.tschofenig@gmx.net <mailto:hannes.tschofenig@gmx.net>> >> wrote: >> >> Hi Stephen, Hi Nicholas, >> >> it would be interesting (as a history lesson) if someone could >> tell us why the group at that time decided to develop a NULL >> encryption mechanism. Stephen Kent (co-author of RFC 2410) >> might remember. I have no heard >> >> >> It was for testing > no, it was not. please see my response to Hannes. > > Steve > > > Well what I should have said is 'testing and other legit stuff'. The > people I talked to said they wanted it for testing. The point was that > it was a completely reasonable proposal. > > Given the attitude of the IETF to NAT back in those days there would be > good reason not to lead with NAT bypass as the motivation for the spec. > Regardless of the IETF's position on NAT then (I was *much* more active in various IETF WGs back then) or now, NAT is a operational reality, will be for the foreseeable future. It's "technical impurities" matter not, in that regard. - - ferg > > As for the language being 'delightfully tongue in cheek', its the sort > of thing that looks fun when written but can look awfully bad if there > is an issue resulting. > > At any rate, I think the point is made sufficiently that NULL ciphers in > legacy suites do not represent a policy precedent against the PERPASS > work. > > --- > Website: http://hallambaker.com/ > > > _______________________________________________ > perpass mailing list > perpass@ietf.org > https://www.ietf.org/mailman/listinfo/perpass > -----BEGIN PGP SIGNATURE----- Version: PGP Desktop 10.2.0 (Build 2317) Charset: utf-8 wj8DBQFSpi14q1pz9mNUZTMRAlooAKDi4+KZtbzbvLK4ZNPiqr9BCZfIJwCcDH23 wZwZcquGS3e8f/Zh0pqfaRQ= =7K0s -----END PGP SIGNATURE----- -- Paul Ferguson PGP Public Key ID: 0x63546533
- [perpass] NULL Cipher RFC 2410 to HISTORIC ??? Phillip Hallam-Baker
- Re: [perpass] NULL Cipher RFC 2410 to HISTORIC ??? Merike Kaeo
- Re: [perpass] NULL Cipher RFC 2410 to HISTORIC ??? Merike Kaeo
- Re: [perpass] NULL Cipher RFC 2410 to HISTORIC ??? Phillip Hallam-Baker
- Re: [perpass] NULL Cipher RFC 2410 to HISTORIC ??? Yoav Nir
- Re: [perpass] NULL Cipher RFC 2410 to HISTORIC ??? Phillip Hallam-Baker
- Re: [perpass] NULL Cipher RFC 2410 to HISTORIC ??? Moriarty, Kathleen
- Re: [perpass] NULL Cipher RFC 2410 to HISTORIC ??? Yoav Nir
- Re: [perpass] NULL Cipher RFC 2410 to HISTORIC ??? Michael Richardson
- Re: [perpass] NULL Cipher RFC 2410 to HISTORIC ??? Stephen Kent
- Re: [perpass] NULL Cipher RFC 2410 to HISTORIC ??? Stephen Kent
- Re: [perpass] NULL Cipher RFC 2410 to HISTORIC ??? Stephen Kent
- Re: [perpass] NULL Cipher RFC 2410 to HISTORIC ??? Michael Richardson
- Re: [perpass] NULL Cipher RFC 2410 to HISTORIC ??? Moriarty, Kathleen
- Re: [perpass] NULL Cipher RFC 2410 to HISTORIC ??? Phillip Hallam-Baker
- Re: [perpass] NULL Cipher RFC 2410 to HISTORIC ??? Paul Wouters
- Re: [perpass] NULL Cipher RFC 2410 to HISTORIC ??? Paul Ferguson