On 07/29/2014 04:20 PM, Stephen Kent wrote: > In discussing features for the TCPINC work the charter says: > > ... > > - encryption and integrity protection without modifications to the upper > layers (no API changes),
I take this to mean that no additional API should be required for this
feature to work, not that we are precluded from offering an additional
API for aware applications to opt in and configure in more detail.
In particular, the "authentication hooks" also mentioned in the charter
suggest that some extra (optional) API is contemplated and within scope.
--dkg
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Tcpinc mailing list [email protected] https://www.ietf.org/mailman/listinfo/tcpinc
