IPP> SEC - SASL will soon go to IETF Wide (4 week) Last Call (fwd)

IPP> SEC - SASL will soon go to IETF Wide (4 week) Last Call (fwd)

IPP> SEC - SASL will soon go to IETF Wide (4 week) Last Call (fwd)

JK Martin jkm at underscore.com
Tue Jul 22 20:44:16 EDT 1997


This should be of interest to the IPP Security subgroup.


	...jay


----- Begin Included Message -----


Date: Tue, 22 Jul 1997 15:54:05 -0700 (PDT)
From: Chris Newman <Chris.Newman at innosoft.com>
Subject: SASL will soon go to IETF Wide (4 week) Last Call (fwd)
To: Application Authentication/Authorization List <ietf-aaarg at imc.org>,
        IETF ACAP Mailing List <ietf-acap at andrew.cmu.edu>
Originator-Info: login-id=chris; server=thor.innosoft.com


I believe this is of interest to this mailing list.


---------- Forwarded message ----------
Date: Tue, 22 Jul 1997 17:53:54 -0400
From: "Jeffrey I. Schiller" <jis at mit.edu>
Reply-To: ietf-tls at consensus.com
To: ietf-tls at consensus.com
Subject: SASL will soon go to IETF Wide (4 week) Last Call


-----BEGIN PGP SIGNED MESSAGE-----


I have just requested that the document:


"Simple Authentication and Security Layer (SASL)"
<draft-myers-auth-sasl-11.txt>


go to IETF wide last call. Because this document is not the product of
an IETF working group, I have requested a 4 week last call. How TLS
would interact with this proposal is articulated in an Appendix.




                                -Jeff


-----BEGIN PGP SIGNATURE-----
Version: PGP for Personal Privacy 5.0
Charset: noconv


iQCVAwUBM9UZnMUtR20Nv5BtAQF1ZQQAmjsS6lIdxmg9DvaHKATFAfgVP2tCQs0d
OlkeSC5vzdoR9w0IRrghyZT1wae5dODJl1VD0cuqbvE4MqOqEA0Q/UI1Rks+nQt1
CSEoJqMmOUcNaePGP5LJTv/m71xrSolq4vJhIiXcCKlBrR/aB80k0rHr6LJArw9C
HHTpdPgaDIM=
=3zo6
-----END PGP SIGNATURE-----








----- End Included Message -----



More information about the Ipp mailing list