_
> OPSEC mailing list
> op...@ietf.org
> https://www.ietf.org/mailman/listinfo/opsec
--
SY, Jen Linkova aka Furry
___
TLS mailing list
TLS@ietf.org
https://www.ietf.org/mailman/listinfo/tls
.
Please review the document and express your support or concerns/comments.
Thanks!
--
SY, Jen Linkova aka Furry on behalf of the OpSec Chairs.
___
TLS mailing list
TLS@ietf.org
https://www.ietf.org/mailman/listinfo/tls
asking the TLS WG to review those documents and
provide feedback.
If you have commented on those drafts already - thank you very much!
If you have not - please take a look.
--
SY, Jen Linkova aka Furry on behalf of the OpSec Chairs.
___
TLS mailing lis
gt; that appear around the time of an IETF meeting, a timing that I sometimes
> think is designed to let it slip through unnoticed. Given all those other
> I-D - silly authors - it may be more than three weeks before I get my
> thoughts together.
Just to clarify: would you prefer n
n
undesirable outcome of people not paying enough attention.
But thanks for the comments, I'll take it into account - let's
consider it my learning curve..
BTW -02 has been posted so I hope your comments have been incorporated.
--
SY, Jen Linkova aka Furry
document describes.
Overall, we think these issues need to be addressed before the working
group can consider adopting this document.
Thanks to everyone who has reviewed the document and provided the feedback.
--
SY, Jen Linkova aka Furry
___
TLS mailing
thank both OpSec and TLS working groups for
reviewing the document.
--
SY, Jen Linkova aka Furry on behalf of the OpSec WG chairs.
___
TLS mailing list
TLS@ietf.org
https://www.ietf.org/mailman/listinfo/tls
Reviewer: Jen Linkova
Review result: Ready
The document is clearly written and easy to understand even by people who knows
very little about TLS (like this reviewer ;) I think the document has no
negative impact on deployments: quite the opposite, it might motivate people to
move to TLS1.3.
I
