-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi all,
I at some point in the (near, hopefully) future wish to submit an internet
draft - STRN, ESMTP extension for secure client-server role exchange - but
notice that the guidelines set out in 1id-guidelines.txt appear to mandate
certain formatting requirements.
A) I don't see any RFC or draft that proposes this mechanism already
(though I did notice an obscure atrn and turn used as an extension for
authenticated turn once on a Microsoft SMTP service). Is it already
available or otherwise documented? My reasons for defining it are really
for another message/draft.
B) I am totally blind, so the process of formatting the document -
especially in plain text - is going to prove very difficult. Are there
other provisions that I might take advantage of that would solve this
problem?
Any ideas/suggestions much appreciated.
Cheers,
Sabahattin
- --
Thought for the day:
Advertising (n): the science of arresting the human
intelligence for long enough to get money from it.
-- Stephen Leacock.
Latest PGP Public key? Click:
<mailto:PGPPublicKey@sabahattin-gucukoglu.com>
and send that message as is.
Sabahattin Gucukoglu
Phone: +44 (0)20 7,502-1615
Mobile: +44 (0)7986 053399
http://www.sabahattin-gucukoglu.com/
E-mail or MSN Messenger: <mail@Sabahattin-Gucukoglu.com>
-----BEGIN PGP SIGNATURE-----
Version: PGP 8.0 -- QDPGP 2.70
Comment: Previous public key for ID <Sabahattin_Gucukoglu@mailandnews.co.uk> revoked due to invalidated primary address.
iQA/AwUBPp+PEyNEOmEWtR2TEQKRDwCfYxDFS6ye0Eab148Zh92SjB3cPFsAoIdh
mTnNUnbCppDjx9M9hIx2RyPI
=U+kJ
-----END PGP SIGNATURE-----