datatracker.ietf.org
Sign in
Version 5.3.0, 2014-04-12
Report a bug

Namespace Considerations and Registries for GSS-API Extensions
draft-ietf-kitten-gssapi-extensions-iana-08

NETWORK WORKING GROUP                                        N. Williams
Internet-Draft                                          Cryptonector LLC
Intended status: Standards Track                             A. Melnikov
Expires: April 19, 2014                                        Isode Ltd
                                                        October 16, 2013

     Namespace Considerations and Registries for GSS-API Extensions
            draft-ietf-kitten-gssapi-extensions-iana-08.txt

Abstract

   This document describes the ways in which the GSS-API may be extended
   and directs the creation of an IANA registry for various GSS-API
   namespaces.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on April 19, 2014.

Copyright Notice

   Copyright (c) 2013 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Williams & Melnikov      Expires April 19, 2014                 [Page 1]
Internet-Draft            GSS IANA Instructions             October 2013

Table of Contents

   1.  Conventions used in this document . . . . . . . . . . . . . .   2
   2.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   3.  Extensions to the GSS-API . . . . . . . . . . . . . . . . . .   2
   4.  Generic GSS-API Namespaces  . . . . . . . . . . . . . . . . .   3
   5.  Language Binding-Specific GSS-API Namespaces  . . . . . . . .   3
   6.  Extension-Specific GSS-API Namespaces . . . . . . . . . . . .   3
   7.  Registration Form . . . . . . . . . . . . . . . . . . . . . .   4
   8.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   7
   8.1.  Initial Namespace Registrations . . . . . . . . . . . . . .   7
   8.2.  Registration Maintenance Guidelines . . . . . . . . . . . .   7
   8.2.1.  Sub-Namespace Symbol Pattern Matching . . . . . . . . . .   7
   8.2.2.  Expert Reviews of       Individual Submissions  . . . . .   8
   8.2.3.  Change Control  . . . . . . . . . . . . . . . . . . . . .   9
   9.  Security Considerations . . . . . . . . . . . . . . . . . . .   9
   10. References  . . . . . . . . . . . . . . . . . . . . . . . . .   9
   10.1.  Normative References . . . . . . . . . . . . . . . . . . .  10
   10.2.  Informative References . . . . . . . . . . . . . . . . . .  10
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  10

1.  Conventions used in this document

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in [RFC2119].

2.  Introduction

   There is a need for private-use and mechanism-specific extensions to
   the Generic Security Services Application Programming Interface (GSS-
   API).  As such extensions are designed and standardized (or not),
   both at the IETF and elsewhere, there is a non-trivial risk of
   namespace pollution and conflicts.  To avoid this we set out
   guidelines for extending the GSS-API and direct the creation of an
   IANA registry for GSS-API namespaces.

   Registrations of individual items and sub-namespaces are allowed.
   Each sub-namespace may provide different rules for registration,
   e.g., for mechanism-specific and private-use extensions.

3.  Extensions to the GSS-API

   Extensions to the GSS-API can be categorized as follows:

   o  Abstract API extensions

   o  Implementation-specific

Williams & Melnikov      Expires April 19, 2014                 [Page 2]

[include full document text]