[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
IPSECond: Re: Extended authentication with ISAKMP/Oakley draft )
-----BEGIN PGP SIGNED MESSAGE-----
>>>>> "Steven" == Steven Bellovin <smb@research.att.com> writes:
Steven> Let's all agree on one thing, though -- barring a *major* flaw in
Steven> the protocol, we are *not* changing ISAKMP/Oakley at this point.
Steven> If you have new variants that don't change the basic protocol,
Steven> they should be written up in new RFCs.
Agreed. That doesn't prevent us from discussing different ways of doing
things, nor does it prevent us from getting some private operational
experience with extensions.
I'd like to propose that any discussion about things to occur after
proposed standard stage be prefixed life I've done above.
:!mcr!: | Network and security consulting/contract programming
Michael Richardson | I do IPsec policy code for SSH <http://www.ssh.fi/>
Personal: <A HREF="http://www.sandelman.ottawa.on.ca/People/Michael_Richardson/Bio.html">mcr@sandelman.ottawa.on.ca</A>. PGP key available.
Corporate: <A HREF="http://www.sandelman.ottawa.on.ca/SSW/">sales@sandelman.ottawa.on.ca</A>.
ON HUMILITY: To err is human, to moo bovine.
-----BEGIN PGP SIGNATURE-----
Version: 2.6.3ia
Charset: latin1
Comment: Processed by Mailcrypt 3.4, an Emacs/PGP interface
iQB1AwUBNJQhKqZpLyXYhL+BAQE9xQMAtZqrVgl0y69E3uqRm/a3dSE1EHpKXkCE
Sh3/74hV92Y2Aq223UWPVbwbg1kdI5EuyABJwuz6d5P0W72/PO2BL6wDci0bphzG
FBQrsQSiuXdMUY3+yIKHRQeF1Z3jFRdZ
=AvkP
-----END PGP SIGNATURE-----
References: