Hello tcpinc members,
I’m new to the group, and joined at Kyle and David’s invitation to give a
review of this draft before the WGLC expires:
"TCP-ENO: Encryption Negotiation Option"
https://datatracker.ietf.org/doc/draft-ietf-tcpinc-tcpeno/
The doc mostly looks pretty good to me. I couldn’t fi
te explanation of my objection.
I hope that helps.
-Jake
On 2/2/17, 9:14 PM, "David Mazieres" wrote:
"Holland, Jake" writes:
> A few suggestions that I think might improve the doc:
Thanks for going through the document.
> 1. There should be a MUST for an API that
On 2/3/17, 6:27 PM, "David Mazieres" wrote:
>"Holland, Jake" writes:
>> Should my app set the a-bit? I think this version of the ENO draft
>> says yes, because I have altered my behavior in the presence of
>> encrypted TCP (and it wasn’t practical for
On 2/4/17, 11:40 AM, "David Mazieres" wrote:
> Achieving stronger security with TCP-ENO requires verifying session
> IDs. Any application relying on ENO for communications security MUST
> incorporate session IDs into its endpoint authentication. By way of
> example, an authentication mec
