TLS and ACAP/IMAP/POP

There was a brief discussion of this specification at the ACAP WG (it's
not a WG document, but is related to the WG):

 <ftp://ds.internic.net/internet-drafts/draft-newman-tls-imappop-03.txt>

At the meeting it was suggested that language be added concerning shutting
down the TLS connection without shutting down the underlying TCP 
connection.  I don't know how to write this or what needs to be said, if
anything.  There are other issues concerning restrictions on certificates
and naming in certificates which were raised by others and may also not be
well specified by reference.

I see two choices:

(1) Delay this indefinitely until a co-author volunteers who is
comfortable writing the necessary text.  I don't have time to learn all
about variations in X.509 certs and SSL/TLS APIs which I consider 
necessary to write clear text on these topics.

(2) Do an IETF 4 week last call on the current document, publish as a 
proposed standard RFC and if it is necessary to revise it later we can 
recycle at proposed status.

I favor option (2) as I believe it is more important to have a standards
track spec describing how to integrate TLS into these protocols than it is
to have a perfect spec.  If I get no complaints, I will ask for a last
call on the current spec in one week.  Otherwise I will wait for a
volunteer (anyone who complains will be the obvious choice for
co-author :-).

Editorial comments or comments about other minor issues in the spec are
welcome prior to IETF last call and I will do my best to address them.  I
plan to make one more editorial revision before asking for IETF 4 week
last call. 

		- Chris