To:
"Steven M. Bellovin" <smb@research.att.com>
cc:
keydist@cafax.se, Jeff Schiller <jis@mit.edu>
From:
Michael Richardson <mcr@sandelman.ottawa.on.ca>
Date:
Mon, 30 Sep 2002 21:50:44 -0400
In-reply-to:
Your message of "Mon, 30 Sep 2002 17:08:42 EDT." <20020930210843.02C347B68@berkshire.research.att.com>
Sender:
owner-keydist@cafax.se
Subject:
Re: BoF slot applied for...
-----BEGIN PGP SIGNED MESSAGE-----
>>>>> "Steven" == Steven M Bellovin <smb@research.att.com> writes:
>> you need a security ad, smb or jis, to help you move it.
>>
>> randy
Steven> This is for a DNS record for a key for opportunistic encryption? I'll
Steven> be happy to approve the BoF -- send me the description, agenda, etc.,
Steven> and I'll inform the secretariat.
It could have other uses as well.
The proposal that I wrote defined the storage, but not the semantics. I
think that this is the way to go with this.
If we have a BOF with the intent to form a new WG (as opposed to adding it
to IPSEC or IPSP), then do we perhaps have to go through requirements,
etc.. on this? I mean, the requirements can probably be contained in the WG
description :-)
Along time ago we had a notion of creating small short-lived WGs to push
small IPSEC things forward. If this is to be an example of this great, and
I'll put together a description tomorrow.
I do not otherwise want to open any cans of worms.
] ON HUMILITY: to err is human. To moo, bovine. | firewalls [
] Michael Richardson, Sandelman Software Works, Ottawa, ON |net architect[
] mcr@sandelman.ottawa.on.ca http://www.sandelman.ottawa.on.ca/ |device driver[
] panic("Just another Debian GNU/Linux using, kernel hacking, security guy"); [
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)
Comment: Finger me for keys
iQCVAwUBPZj/cYqHRg3pndX9AQGHSQQAnvwlvDirqVKfzo8MEqISOvSZOju//9Fn
jmgOiudNygyOXvA3CkR6qlgZezIezFRKOnTTcO1UlixrZvTnxrAqK0jMy2AP+lf3
X9jxBg8raEh2NO8BYKoBitZym2OamB1a0EEAe/53rET9w1IN0UoA0ltpRNh4H708
s++2wbHajJw=
=w9/F
-----END PGP SIGNATURE-----