Re: [TLS] I-D ACTION:draft-ietf-tls-rfc4346-bis-10.txt
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [TLS] I-D ACTION:draft-ietf-tls-rfc4346-bis-10.txt



> Given that TLS 1.2 is already approved, these comments come a 
> bit late. The typos can be fixed during AUTH48, but adding
> new functionality is not possible.

Yes, the IESG message arrived 10 minutes after I sent my review.
I have been so busy that I've had to put TLS on the back burner
for the past few months.  I'm hoping to update my server soon.

I still think it would be a good idea to pursue an extension to
specify the dh_q value in ServerDHParams.  Clearly this could
be its own document (or put into the successor to RFC 4366).  I
think it could be a really simple empty extension that tells the
server that the client knows about q, and the server responds if
it will put q into ServerDHParams.

Mike
_______________________________________________
TLS mailing list
TLS at ietf.org
https://www.ietf.org/mailman/listinfo/tls



Note: Messages sent to this list are the opinions of the senders and do not imply endorsement by the IETF.