datatracker.ietf.org
Sign in
Version 5.4.0, 2014-04-22
Report a bug

Clarifications and Extensions to the Generic Security Service Application Program Interface (GSS-API) for the Use of Channel Bindings
draft-ietf-kitten-gssapi-channel-bindings-07

Note: This ballot was opened for revision 06 and is now closed.

Summary: Needs a YES. Needs 9 more YES or NO OBJECTION positions to pass.

[Alexey Melnikov]

Comment (2009-03-26)

I was a WG chair for Kitten at the time of the publication request and were
involved in discussions about it.

[Cullen Jennings]

Comment (2009-04-06)

Support Lars discuss

[Russ Housley]

Comment (2009-04-06)

  Based on the response from the author to Brian Carpenter's Gen-ART
  Review, I was expecting this paragraph to be revised:
  >
  > Where a language binding of the GSS-API models channel bindings as
  > OCTET STRINGs (or the language's equivalent), then the implementation
  > MUST assume that the given bindings correspond only to the
  > application-data field of GSS-CHANNEL-BINDINGS as shown above, rather
  > than some encoding of GSS-CHANNEL-BINDINGS.
  >
  The expected update would be something like this:
  >
  > Where the language binding of the GSS-API model's channel bindings is
  > a single OCTET STRING (or the language's equivalent), then the
  > implementation SHOULD assume that the given bindings correspond only
  > to the application-data field of GSS-CHANNEL-BINDINGS shown above.