I prefer adoption of A (tcpinc-tls-option), because:
* I believe a profile of tls can be produced that will be acceptable to
kernel developers and can satisfy the "short, simple security proof"
goal described by proponents of tcpcrypt, and
* I believe that a solution based on that profile of TLS is more likely
to achieve the WG's stated goal of ubiquitous encryption, because it
will be easier to deploy into many environments due to existing security
and/or middlebox constraints.
That said, since my opinion is largely based on the assumption that an
acceptable profile can/will be produced, if that isn't the case by
Yokohama, I will be more inclined to accept either "adopt both" or
"adopt tcpcrypt".
--Brandon Williams
On 07/24/2015 05:16 AM, Martin Stiemerling wrote:
Dear all,
**Please use this CORRECTED version, as one option to choose from below
didn't make it into the original.****
Thanks to Erik Rescola for pointing this out to me directly.
This point got lost on the mailing list, but it has been decided in the
WG session here at IETF-93 that there will be a Last Call for consensus
about which document of the below ones to take as starting point for the
WG.
Here are the two drafts:
a) draft-rescorla-tcpinc-tls-option-03
b) draft-bittau-tcpinc-tcpcrypt-03
Please respond to the tcpinc wg mailing list until
July 31st, 2015
1pm CEST
on wether you prefer
- either draft a) or b)
- both drafts (a & b) as WG items
- or none
to be accepted as WG item(s).
Please write also your brief reasoning on why you made your choice.
Please note that accepting a draft is not the end of working on the
technical content of the draft, but it is actually the starting point
when the WG has full change control about the content of the draft!
Regards,
Martin Stiemerling
Transport Area Director
_______________________________________________
Tcpinc mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/tcpinc
--
Brandon Williams; Chief Architect
Cloud Networking; Akamai Technologies Inc.
_______________________________________________
Tcpinc mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/tcpinc
