-----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 <[email protected] > <mailto:[email protected]>> wrote: > > Phillip, > >> On Sun, Dec 8, 2013 at 5:00 PM, Hannes Tschofenig >> <[email protected] <mailto:[email protected]>> >> 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 > [email protected] > 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 mailing list [email protected] https://www.ietf.org/mailman/listinfo/perpass
