Re: [Tcpcrypt] v3 of the charter

[marcelo bagnulo braun <[e-mail]>]

El 01/05/14 17:04, David Mazieres escribió:
> marcelo bagnulo braun <[e-mail]> writes:
>
>>> FWIW, mine too - IMO, the issue of anti-fingerprinting can be
>>> specified without reference to role, in which case whether
>>> simultaneous open is supported or not can be determined in a candidate
>>> solution.
>>>
>> could you propose text?
> How about eliminating the paragraph about anti-fingerprinting, and
> instead changing this text:
>
>> - An extended API describing how applications can obtain further
>>    benefits of the proposed extensions. In particular, the hooks for
>>    supporting external authentication will be defined in this
>>    document. This will be an informational document.
> To the following:
>
>          ... In particular, the hooks for supporting external
>          authentication will be defined in this document.  In addition,
>          the document shall specify functions that allow control over any
>          session parameters such as accepted ciphers or re-use of
>          cryptographic material from prior sessions (if the protocol
>          supports such re-use) and that help prevent multiple TCP
>          Inc. connections from being linked to the same endpoint.

Thanks for the text

However, i am uncovinced we should link this to the API at this stage.
I mean, current charter text basically says avoid additional 
fingerprinting, doesnt link this to the API, i am dubious we should do this.
For instance, i would think legacy apps that dont support the extended 
API would also want to avoid fingerprinting.

What do you think?

Regards, marcelo




> David
>