Telechat Review of draft-ietf-kitten-gssapi-channel-bindings-
review-ietf-kitten-gssapi-channel-bindings-secdir-telechat-canetti-2009-04-02-00

   *I have reviewed this document as part of the security directorate's
   *ongoing effort to review all IETF documents being processed by the
   *IESG.  These comments were written primarily for the benefit of the
   *security area directors.  Document editors and WG chairs should treat
   *these comments just like any other last call comments.


This is a very short document. It describes a more generic way of 
formatting the API for channel bindings. The move to a more generic format 
is welcome. One potential objection here, however, is to the requirement 
that compliant implementations MUST interpret the API as having the new 
format. This may have backwards compatibility issues, and for no apparent 
good reason. It might be better to specify the format so that an 
implementation will be able to take also older API formats.
(Since this is not an interoperability or security-sensitive issue, there 
seems to be no reason for the IETF to MANDATE one way over another.)

Best,
Ran


_______________________________________________
secdir mailing list
secdir at mit.edu


https://mailman.mit.edu/mailman/listinfo/secdir