Generic Security Service Application Programming Interface (GSS-API) Naming Extensions
RFC 6680

Approval announcement
Draft of message to be sent after approval:

From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Cc: RFC Editor <rfc-editor@rfc-editor.org>,
    kitten mailing list <kitten@ietf.org>,
    kitten chair <kitten-chairs@tools.ietf.org>
Subject: Protocol Action: 'GSS-API Naming Extensions' to Proposed Standard (draft-ietf-kitten-gssapi-naming-exts-15.txt)

The IESG has approved the following document:
- 'GSS-API Naming Extensions'
  (draft-ietf-kitten-gssapi-naming-exts-15.txt) as Proposed Standard

This document is the product of the Common Authentication Technology Next
Generation Working Group.

The IESG contact persons are Stephen Farrell and Sean Turner.

A URL of this Internet Draft is:
http://datatracker.ietf.org/doc/draft-ietf-kitten-gssapi-naming-exts/


Technical Summary

  The Generic Security Services API (GSS-API) provides a simple naming
  architecture that supports name-based authorization.  This document
  introduces new APIs that extend the GSS-API naming model to support
  name attribute transfer between GSS-API peers.

Working Group Summary

  Nothing worth noting regarding WG process.

Document Quality

  This protocol has been implemented in the MIT 1.8 release.  At least 
  one other vendor has plans on implementing this in the future as well.

Personnel

  The document shepherd is Shawn Emery
  The responsible AD is Stephen Farrell

RFC Editor Note

Please add the following NEW text to the IANA considerations and
replace the string TBD in 7.8 with the assigned OID value. And
please remove the statement that there are no requests for IANA.

NEW

   IANA is requested to register a new name-type OID in "SMI Security for
   Name System Designators Codes (nametypes)" 

      TBD gss-composite-export [RFC 6680]