Generic Security Service API Version 2: Java Bindings Update
draft-ietf-kitten-rfc5653bis-07

[Ballot comment]
I support Alissa's discuss position. 5653 had  the 2119 boilerplate, but no upper-case keywords. IIUC, the authors removed the boilerplate because of that. But keep in mind moving to the 8174 boilerplate is not a drop-in replacement.

[Ballot discuss]
This is more for the shepherding AD than the authors/WG: in the discussion resulting from the Gen-ART review the author indicated that there would be another pass through the document to capitalize uses of normative must/should and add a reference to RFC 8174. That seems like the kind of thing where the WG should get another look at the changes to make sure everyone agrees on what the normative requirements were/are. Is that the plan?

(Via drafts-lastcall@iana.org): IESG/Authors/WG Chairs:

The IANA Services Operator has reviewed draft-ietf-kitten-rfc5653bis-05, which is currently in Last Call, and has the following comments:

We understand that this document doesn't require any registry actions.

While it's often helpful for a document's IANA Considerations section to remain in place upon publication even if there are no actions, if the authors strongly prefer to remove it, we do not object.

If this assessment is not accurate, please respond as soon as possible.

Thank you,

Sabrina Tanamal
IANA Services Specialist

The following Last Call announcement was sent out (ends 2017-09-11):

From: The IESG
To: IETF-Announce
CC: draft-ietf-kitten-rfc5653bis@ietf.org, kitten@ietf.org, ekr@rtfm.com, kitten-chairs@ietf.org, mrogers@redhat.com
Reply-To: ietf@ietf.org
Sender:
Subject: Last Call:  (Generic Security Service API Version 2: Java Bindings Update) to Proposed Standard


The IESG has received a request from the Common Authentication Technology
Next Generation WG (kitten) to consider the following document: - 'Generic
Security Service API Version 2: Java Bindings Update'
  as Proposed Standard

The IESG plans to make a decision in the next few weeks, and solicits final
comments on this action. Please send substantive comments to the
ietf@ietf.org mailing lists by 2017-09-11. Exceptionally, comments may be
sent to iesg@ietf.org instead. In either case, please retain the beginning of
the Subject line to allow automated sorting.

Abstract


  The Generic Security Services Application Program Interface (GSS-API)
  offers application programmers uniform access to security services
  atop a variety of underlying cryptographic mechanisms.  This document
  updates the Java bindings for the GSS-API that are specified in
  "Generic Security Service API Version 2 : Java Bindings Update" (RFC
  5653).  This document obsoletes RFC 5653 by adding a new output token
  field to the GSSException class so that when the initSecContext or
  acceptSecContext methods of the GSSContext class fails it has a
  chance to emit an error token which can be sent to the peer for
  debugging or informational purpose.  The stream-based GSSContext
  methods are also removed in this version.

  The GSS-API is described at a language-independent conceptual level
  in "Generic Security Service Application Program Interface Version 2,
  Update 1" (RFC 2743).  The GSS-API allows a caller application to
  authenticate a principal identity, to delegate rights to a peer, and
  to apply security services such as confidentiality and integrity on a
  per-message basis.  Examples of security mechanisms defined for GSS-
  API are "The Simple Public-Key GSS-API Mechanism" (RFC 2025) and "The
  Kerberos Version 5 Generic Security Service Application Program
  Interface (GSS-API) Mechanism: Version 2" (RFC 4121).




The file can be obtained via
https://datatracker.ietf.org/doc/draft-ietf-kitten-rfc5653bis/

IESG discussion can be tracked via
https://datatracker.ietf.org/doc/draft-ietf-kitten-rfc5653bis/ballot/


No IPR declarations have been submitted directly on this I-D.