draft-ietf-kitten-gssapi-extensions-iana-07.txt   draft-ietf-kitten-gssapi-extensions-iana-08.txt 
NETWORK WORKING GROUP N. Williams NETWORK WORKING GROUP N. Williams
Internet-Draft Cryptonector LLC Internet-Draft Cryptonector LLC
Intended status: Standards Track A. Melnikov Intended status: Standards Track A. Melnikov
Expires: December 1, 2012 Isode Ltd Expires: April 19, 2014 Isode Ltd
May 30, 2012 October 16, 2013
Namespace Considerations and Registries for GSS-API Extensions Namespace Considerations and Registries for GSS-API Extensions
draft-ietf-kitten-gssapi-extensions-iana-07.txt draft-ietf-kitten-gssapi-extensions-iana-08.txt
Abstract Abstract
This document describes the ways in which the GSS-API may be extended 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 and directs the creation of an IANA registry for various GSS-API
namespaces. namespaces.
Status of this Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on December 1, 2012. This Internet-Draft will expire on April 19, 2014.
Copyright Notice Copyright Notice
Copyright (c) 2012 IETF Trust and the persons identified as the Copyright (c) 2013 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Conventions used in this document . . . . . . . . . . . . 3 1. Conventions used in this document . . . . . . . . . . . . . . 2
2. Introduction . . . . . . . . . . . . . . . . . . . . . . . 3 2. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
3. Extensions to the GSS-API . . . . . . . . . . . . . . . . 3 3. Extensions to the GSS-API . . . . . . . . . . . . . . . . . . 2
4. Generic GSS-API Namespaces . . . . . . . . . . . . . . . . 3 4. Generic GSS-API Namespaces . . . . . . . . . . . . . . . . . 3
5. Language Binding-Specific GSS-API Namespaces . . . . . . . 4 5. Language Binding-Specific GSS-API Namespaces . . . . . . . . 3
6. Extension-Specific GSS-API Namespaces . . . . . . . . . . 4 6. Extension-Specific GSS-API Namespaces . . . . . . . . . . . . 3
7. Registration Form . . . . . . . . . . . . . . . . . . . . 4 7. Registration Form . . . . . . . . . . . . . . . . . . . . . . 4
8. IANA Considerations . . . . . . . . . . . . . . . . . . . 7 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7
8.1. Initial Namespace Registrations . . . . . . . . . . . . . 7 8.1. Initial Namespace Registrations . . . . . . . . . . . . . . 7
8.2. Registration Maintenance Guidelines . . . . . . . . . . . 7 8.2. Registration Maintenance Guidelines . . . . . . . . . . . . 7
8.2.1. Sub-Namespace Symbol Pattern Matching . . . . . . . . . . 7 8.2.1. Sub-Namespace Symbol Pattern Matching . . . . . . . . . . 7
8.2.2. Expert Reviews of Individual Submissions . . . . . . . . . 8 8.2.2. Expert Reviews of Individual Submissions . . . . . 8
8.2.3. Change Control . . . . . . . . . . . . . . . . . . . . . . 9 8.2.3. Change Control . . . . . . . . . . . . . . . . . . . . . 9
9. Security Considerations . . . . . . . . . . . . . . . . . 9 9. Security Considerations . . . . . . . . . . . . . . . . . . . 9
10. References . . . . . . . . . . . . . . . . . . . . . . . . 9 10. References . . . . . . . . . . . . . . . . . . . . . . . . . 9
10.1. Normative References . . . . . . . . . . . . . . . . . . . 9 10.1. Normative References . . . . . . . . . . . . . . . . . . . 10
10.2. Informative References . . . . . . . . . . . . . . . . . . 10 10.2. Informative References . . . . . . . . . . . . . . . . . . 10
Authors' Addresses . . . . . . . . . . . . . . . . . . . . 10 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 10
1. Conventions used in this document 1. Conventions used in this document
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [RFC2119]. document are to be interpreted as described in [RFC2119].
2. Introduction 2. Introduction
There is a need for private-use and mechanism-specific extensions to There is a need for private-use and mechanism-specific extensions to
skipping to change at page 3, line 44 skipping to change at page 3, line 19
the GSS-API's namespaces. Or they may introduce new functions, the GSS-API's namespaces. Or they may introduce new functions,
constants, types, etc...; these clearly affect the GSS-API constants, types, etc...; these clearly affect the GSS-API
namespaces. namespaces.
Extensions that affect the GSS-API namespaces should be registered Extensions that affect the GSS-API namespaces should be registered
with the IANA as described herein. with the IANA as described herein.
4. Generic GSS-API Namespaces 4. Generic GSS-API Namespaces
The abstract API namespaces for the GSS-API are: The abstract API namespaces for the GSS-API are:
o Type names o Type names
o Function names o Function names
o Constant names for various types o Constant names for various types
o Constant values for various types o Constant values for various types
o Name types (OID, type name and syntaxes) o Name types (OID, type name and syntaxes)
Additionally we have namespaces associates with the OBJECT IDENTIFIER Additionally we have namespaces associates with the OBJECT IDENTIFIER
(OID) type. The IANA already maintains a registry of such OIDs: (OID) type. The IANA already maintains a registry of such OIDs:
o Mechanism OIDs o Mechanism OIDs
o Name Type OIDs o Name Type OIDs
5. Language Binding-Specific GSS-API Namespaces 5. Language Binding-Specific GSS-API Namespaces
Language binding specific namespaces include, among others: Language binding specific namespaces include, among others:
o Header/interface module names o Header/interface module names
o Object classes and/or types o Object classes and/or types
o Methods and/or functions o Methods and/or functions
o Constant names o Constant names
o Constant values o Constant values
6. Extension-Specific GSS-API Namespaces 6. Extension-Specific GSS-API Namespaces
Extensions to the GSS-API may create additional namespaces. See Extensions to the GSS-API may create additional namespaces. See
Section 8.2. Section 8.2.
7. Registration Form 7. Registration Form
Registrations for GSS-API namespaces SHALL take the following form: Registrations for GSS-API namespaces SHALL take the following form:
+--------------+---------------------+------------------------------+ +----------------+-------------------------+------------------------+
| Registration | Possible Values | Description | | Registration | Possible Values | Description |
| Field | | | | Field | | |
+--------------+---------------------+------------------------------+ +----------------+-------------------------+------------------------+
| Bindings | 'Generic', | Indicates the name of the | | Bindings | 'Generic', | Indicates the name of |
| | 'C-bindings', | programming language that | | | 'C-bindings', 'Java', | the programming |
| | 'Java', 'C#', | this registration involves, | | | 'C#', <programming | language that this |
| | <programming | or, if 'Generic', that this | | | language name> | registration involves, |
| | language name> | is an entry for the generic | | | | or, if 'Generic', that |
| | | abstract GSS-API (i.e., not | | | | this is an entry for |
| | | specific to any programming | | | | the generic abstract |
| | | language). | | | | GSS-API (i.e., not |
+--------------+---------------------+------------------------------+ | | | specific to any |
| Registration | 'Instance', | Indicates whether this entry | | | | programming language). |
| type | 'Sub-Namespace' | reserves a given symbol name | +----------------+-------------------------+------------------------+
| | | (and possibly, constant | | Registration | 'Instance', 'Sub- | Indicates whether this |
| | | value), or whether it | | type | Namespace' | entry reserves a given |
| | | reserves an entire | | | | symbol name (and |
| | | sub-namespace (the name is a | | | | possibly, constant |
| | | pattern) or constant value | | | | value), or whether it |
| | | range. | | | | reserves an entire |
+--------------+---------------------+------------------------------+ | | | sub-namespace (the |
| Object Type | 'Data-Type', | Indicates the type of the | | | | name is a pattern) or |
| | 'Function', | object whose symbolic name | | | | constant value range. |
| | 'Method', | or constant value this entry | +----------------+-------------------------+------------------------+
| | 'Integer', | registers. The possible | | Object Type | <Symbol> defined by the | Indicates the type of |
| | 'String', 'OID', | values of this field depend | | | binding language (for | the object whose |
| | 'Context-Flag', | on the programming language | | | example 'Data-Type', | symbolic name or |
| | 'Name-Type', | in question, therefore they | | | 'Function', 'Method', | constant value this |
| | 'Macro', | are not all specified here. | | | 'Integer', 'String', | entry registers. The |
| | 'Header-File-Name', | | | | 'OID', 'Context-Flag', | possible values of |
| | 'Module-Name', | | | | 'Name-Type', 'Macro', | this field depend on |
| | 'Class', etcetera | | | | 'Header-File-Name', | the programming |
+--------------+---------------------+------------------------------+ | | 'Module-Name', 'Class') | language in question, |
| Symbol | <Symbol name or | The name of a symbol or | | | | therefore they are not |
| Name/Prefix | name pattern> | symbol sub-namespace being | | | | all specified here. |
| | | registered. See | +----------------+-------------------------+------------------------+
| | | Section 8.2.1 | | Symbol | <Symbol name or name | The name of a symbol |
+--------------+---------------------+------------------------------+ | Name/Prefix | pattern> | or symbol sub- |
| Binding of | <Name of abstract | If the registration is for a | | | | namespace being |
| | API element of | specific language binding of | | | | registered. See |
| | which this object | the GSS-API, then this names | | | | Section 8.2.1 |
| | is a binding> | the abstract API element of | +----------------+-------------------------+------------------------+
| | | which it is a binding | | Binding of | <Name of abstract API | If the registration is |
| | | (OPTIONAL). | | | element of which this | for a specific |
+--------------+---------------------+------------------------------+ | | object is a binding> | language binding of |
| Constant | <Constant value> or | The value of the constant | | | | the GSS-API, then this |
| Value/Range | <constant value | named by the <Symbol | | | | names the abstract API |
| | range> | Name/Prefix>. This field is | | | | element of which it is |
| | | present only for Instance | | | | a binding (OPTIONAL). |
| | | and Sub-namespace | +----------------+-------------------------+------------------------+
| | | registrations of Constant | | Constant | <Constant value> or | The value of the |
| | | object types. | | Value/Range | <constant value range> | constant named by the |
+--------------+---------------------+------------------------------+ | | | <Symbol Name/Prefix>. |
| Description | <Text> | Description of the | | | | This field is present |
| | | registration. Multiple | | | | only for Instance and |
| | | instances of this field may | | | | Sub-namespace |
| | | result (see Section 8.2.3). | | | | registrations of |
+--------------+---------------------+------------------------------+ | | | Constant object types. |
| Registration | Values from | Describes the rules for | +----------------+-------------------------+------------------------+
| Rules | [RFC5226], such as | allocation of items that | | Description | <Text> | Description of the |
| | 'IESG Approval', | fall in this sub-namespace, | | | | registration. |
| | 'Expert Review', | for entries with | | | | Multiple instances of |
| | 'First Come First | Registration Type of | | | | this field may result |
| | Served', 'Private | Sub-namespace (OPTIONAL). | | | | (see Section 8.2.3). |
| | Use', etcetera. | For private use | +----------------+-------------------------+------------------------+
| | | sub-namespaces the submitter | | Registration | <Reference> to an IANA | Describes the rules |
| | | MUST provide the e-mail | | Rules | registration Policy | for allocation of |
| | | address of a responsible | | | defined in [RFC5226] | items that fall in |
| | | contact. If this field is | | | (or an RFC that updates | this sub-namespace, |
| | | not specified for a | | | it), for instance 'IESG | for entries with |
| | | sub-namespace, the default | | | Approval', 'Expert | Registration Type of |
| | | registration rules specified | | | Review', 'First Come | Sub-namespace |
| | | in Section 8.2 apply. | | | First Served', 'Private | (OPTIONAL). For |
+--------------+---------------------+------------------------------+ | | Use'. | private use sub- |
| Reference | <Reference> | Reference to document that | | | | namespaces the |
| | | describes the registration, | | | | submitter MUST provide |
| | | if any (OPTIONAL). Multiple | | | | the e-mail address of |
| | | instances of this field are | | | | a responsible contact. |
| | | allowed, with one reference | | | | If this field is not |
| | | each. | | | | specified for a sub- |
+--------------+---------------------+------------------------------+ | | | namespace, the default |
| Expert | <Name of expert | OPTIONAL, see Section 8.2.2. | | | | registration rules |
| Reviewer | reviewers, possibly | Multiple instances of this | | | | specified in Section |
| | WG names> | field are allowed, with one | | | | 8.2 apply. |
| | | expert reviewer | +----------------+-------------------------+------------------------+
| | | per-instance. Leave this | | Reference | <Reference> | Reference to a |
| | | field blank when requesting | | | | document that |
| | | a registration. It will be | | | | describes the |
| | | filled in by the Expert who | | | | registration, if any |
| | | reviews the registration. | | | | (OPTIONAL). Multiple |
+--------------+---------------------+------------------------------+ | | | instances of this |
| Expert | <Notes from the | Expert reviewers may request | | | | field are allowed, |
| Review Notes | expert review> | that some comments be | | | | with one reference |
| | | included with the | | | | each. |
| | | registration, e.g., | +----------------+-------------------------+------------------------+
| | | regarding security | | Expert | <Name of expert | OPTIONAL, see Section |
| | | considerations of the | | Reviewer | reviewers, possibly WG | 8.2.2. Multiple |
| | | registered extension. | | | names> | instances of this |
+--------------+---------------------+------------------------------+ | | | field are allowed, |
| Status | 'Registered' or | Status of the registration. | | | | with one expert |
| | 'Obsoleted' | | | | | reviewer per-instance. |
+--------------+---------------------+------------------------------+ | | | Leave this field blank |
| Obsoleting | <Reference> | Reference to document, if | | | | when requesting a |
| Reference | | any, that obsoletes this | | | | registration. It will |
| | | registration. Multiple | | | | be filled in by the |
| | | instances of this field are | | | | Expert who reviews the |
| | | allowed, with one reference | | | | registration. |
| | | each. (OPTIONAL) | +----------------+-------------------------+------------------------+
+--------------+---------------------+------------------------------+ | Expert Review | <Notes from the expert | Expert reviewers may |
| Notes | review> | request that some |
| | | comments be included |
| | | with the registration, |
| | | e.g., regarding |
| | | security |
| | | considerations of the |
| | | registered extension. |
+----------------+-------------------------+------------------------+
| Status | 'Registered' or | Status of the |
| | 'Obsoleted' | registration. |
+----------------+-------------------------+------------------------+
| Obsoleting | <Reference> | Reference to a |
| Reference | | document, if any, that |
| | | obsoletes this |
| | | registration. |
| | | Multiple instances of |
| | | this field are |
| | | allowed, with one |
| | | reference each. |
| | | (OPTIONAL) |
+----------------+-------------------------+------------------------+
The IANA should create a single GSS-API namespace registry, or The IANA should create a single GSS-API namespace registry, or
multiple registries, one for symbolic names and one for constant multiple registries, one for symbolic names and one for constant
values, and/or it may create a registry per-programming language, at values, and/or it may create a registry per-programming language, at
its convenience. its convenience.
Entries in these registries should consist of all the fields from Entries in these registries should consist of all the fields from
their corresponding registration entries. their corresponding registration entries.
Entries should be sorted by: programming language, registration type, Entries should be sorted by: programming language, registration type,
object type, and symbol name/pattern. object type, and symbol name/pattern.
8. IANA Considerations 8. IANA Considerations
This document deals with IANA considerations throughout. This document deals with IANA considerations throughout.
Specifically it creates a single registry of various kinds of things, Specifically it creates a single registry of various kinds of things,
though the IANA may instead create multiple registries each for one though the IANA may instead create multiple registries, each for one
of those kinds of things. Of particular interest may be that IANA of those kinds of things. Of particular interest may be that IANA
will now be the registration authority for the GSS-API name type OID will now be the registration authority for the GSS-API name type OID
space. space.
8.1. Initial Namespace Registrations 8.1. Initial Namespace Registrations
Initial registry content corresponding to the items defined in Initial registry content corresponding to the items defined in
[RFC2743], [RFC2744], [RFC2853], [RFC1964] and [RFC4121] and others [RFC2743], [RFC2744], [RFC2853], [RFC1964] and [RFC4121] and others
will be supplied during the IANA review portion of the RFC publishing will be supplied during the IANA review portion of the RFC publishing
process. [[Note to RFC Editor: Delete the following sentence before process. [[Note to RFC Editor: Delete the following sentence before
skipping to change at page 7, line 50 skipping to change at page 8, line 4
SHALL allow such registrations if a) they are not conflicting, b) SHALL allow such registrations if a) they are not conflicting, b)
provided that the registration is for object types other than provided that the registration is for object types other than
Context-Flags, and c) subject to expert review. Guidelines for Context-Flags, and c) subject to expert review. Guidelines for
expert reviews are given below. expert reviews are given below.
8.2.1. Sub-Namespace Symbol Pattern Matching 8.2.1. Sub-Namespace Symbol Pattern Matching
Sub-namespace registrations must provide a pattern for matching Sub-namespace registrations must provide a pattern for matching
symbols for which the sub-namespace's registration rules apply. The symbols for which the sub-namespace's registration rules apply. The
pattern consists of a string with the following special tokens: pattern consists of a string with the following special tokens:
o '*', meaning "match any string." o '*', meaning "match any string."
o "%m", meaning "match any mechanism family short-hand name." o "%m", meaning "match any mechanism family short-hand name."
o "%i", meaning "match any implementor vanity short-hand name." o "%i", meaning "match any implementor vanity short-hand name."
For example, "GSS_%m_*" matches "GSS_krb5_foo" since "krb5" is a For example, "GSS_%m_*" matches "GSS_krb5_foo" since "krb5" is a
common short-hand for the Kerberos V GSS-API mechanism [RFC1964]. common short-hand for the Kerberos V GSS-API mechanism [RFC1964].
But "GSS_%m_*" does not match "GSS_foo_bar" unless "foo" is asserted But "GSS_%m_*" does not match "GSS_foo_bar" unless "foo" is asserted
to be a short-hand for some mechanism. to be a short-hand for some mechanism.
8.2.2. Expert Reviews of Individual Submissions 8.2.2. Expert Reviews of Individual Submissions
[[The following paragraph should be deleted from the document before
publication, as it will not age well. It should be moved to the
shepherding write-up.]]
Expert review selection SHALL be done as follows. If, at the time Expert review selection SHALL be done as follows. If, at the time
that the IANA receives an individual submission for registration in that the IANA receives an individual submission for registration in
this registry, there is are any IETF Working Groups chartered to this registry, there are any IETF Working Groups chartered to produce
produce GSS-API-related documents, then the IANA SHALL ask the chairs GSS-API-related documents, then the IANA SHALL ask the chairs of such
of such WGs to be expert reviewers or to name one. If there are no WGs to be expert reviewers or to name one. If there are no such WGs
such WGs at that time, then the IANA SHALL ask past chairs of the at that time, then the IANA SHALL ask past chairs of the KITTEN WG
KITTEN WG and the author/editor of this RFC to act as expert and the author/editor of this RFC to act as expert reviewers or name
reviewers or name an alternate. an alternate.
Expert reviewers of individual registration submissions with Expert reviewers of individual registration submissions with
Registration Type == Sub-namespace should check that the registration Registration Type == Sub-namespace should check that the registration
request has a suitable description (which doesn't need to be request has a suitable description (which doesn't need to be
sufficiently detailed for others to implement) and that the Symbol sufficiently detailed for others to implement) and that the Symbol
Name/Prefix is sufficiently descriptive of the purpose of the sub- Name/Prefix is sufficiently descriptive of the purpose of the sub-
namespace or reflective of the name of the submitter or associated namespace or reflective of the name of the submitter or associated
company. company.
Expert reviewers of individual registration submissions with Expert reviewers of individual registration submissions with
skipping to change at page 9, line 18 skipping to change at page 9, line 26
Registered entries may be marked obsoleted using the same expert Registered entries may be marked obsoleted using the same expert
review process as for registering new entries. Obsoleted entries are review process as for registering new entries. Obsoleted entries are
not, however, to be deleted, but merely marked having Obsoleted not, however, to be deleted, but merely marked having Obsoleted
Status. Note that entries may be created as obsoleted to record the Status. Note that entries may be created as obsoleted to record the
fact that the given symbol(s) have been used before, even though fact that the given symbol(s) have been used before, even though
continued use of them is discouraged. continued use of them is discouraged.
Registered entries may also be updated in two other ways: additional Registered entries may also be updated in two other ways: additional
references, obsoleting references, and descriptions may be added. references, obsoleting references, and descriptions may be added.
All changes are subject to expert review. The submitter of a change All changes are subject to expert review, except for changes to
request need not be the same as the original submitter. registrations in a sub-namespace which are subject to the rules of
the relevant sub-namespace. The submitter of a change request need
not be the same as the original submitter.
Registrations may be modified by addition, but under no circumstance Registrations may be modified by addition, but under no circumstance
may any fields be modified except for the Status field or Contact may any fields be modified except for the Status field or Contact
Address, or to correct for transcription errors in filing or Address, or to correct for transcription errors in filing or
processing registration requests. processing registration requests.
The IANA SHALL add a field describing the date that a an addition or The IANA SHALL add a field describing the date that a an addition or
modification was made, and a description of the change. modification was made, and a description of the change.
9. Security Considerations 9. Security Considerations
skipping to change at page 9, line 42 skipping to change at page 10, line 4
services apply; see [RFC5226]. services apply; see [RFC5226].
Also, expert reviewers should look for and may document security Also, expert reviewers should look for and may document security
related issues with submitters' GSS-API extensions, to the best of related issues with submitters' GSS-API extensions, to the best of
the reviewers' ability given the information furnished by the the reviewers' ability given the information furnished by the
submitter. Reviewers may add comments regarding their limited submitter. Reviewers may add comments regarding their limited
ability to review a submission for security problems if the submitter ability to review a submission for security problems if the submitter
is unwilling to provide sufficient documentation. is unwilling to provide sufficient documentation.
10. References 10. References
10.1. Normative References 10.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2743] Linn, J., "Generic Security Service Application Program
Interface Version 2, Update 1", RFC 2743, January 2000.
[RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an [RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an
IANA Considerations Section in RFCs", BCP 26, RFC 5226, IANA Considerations Section in RFCs", BCP 26, RFC 5226,
May 2008. May 2008.
10.2. Informative References 10.2. Informative References
[RFC1964] Linn, J., "The Kerberos Version 5 GSS-API Mechanism", [RFC1964] Linn, J., "The Kerberos Version 5 GSS-API Mechanism", RFC
RFC 1964, June 1996. 1964, June 1996.
[RFC2743] Linn, J., "Generic Security Service Application Program
Interface Version 2, Update 1", RFC 2743, January 2000.
[RFC2744] Wray, J., "Generic Security Service API Version 2 : [RFC2744] Wray, J., "Generic Security Service API Version 2 :
C-bindings", RFC 2744, January 2000. C-bindings", RFC 2744, January 2000.
[RFC2853] Kabat, J. and M. Upadhyay, "Generic Security Service API [RFC2853] Kabat, J. and M. Upadhyay, "Generic Security Service API
Version 2 : Java Bindings", RFC 2853, June 2000. Version 2 : Java Bindings", RFC 2853, June 2000.
[RFC4121] Zhu, L., Jaganathan, K., and S. Hartman, "The Kerberos [RFC4121] Zhu, L., Jaganathan, K., and S. Hartman, "The Kerberos
Version 5 Generic Security Service Application Program Version 5 Generic Security Service Application Program
Interface (GSS-API) Mechanism: Version 2", RFC 4121, Interface (GSS-API) Mechanism: Version 2", RFC 4121, July
July 2005. 2005.
Authors' Addresses Authors' Addresses
Nicolas Williams Nicolas Williams
Cryptonector LLC Cryptonector LLC
Email: nico@cryptonector.com Email: nico@cryptonector.com
Alexey Melnikov Alexey Melnikov
Isode Ltd Isode Ltd
5 Castle Business Village 5 Castle Business Village
36 Station Road 36 Station Road
Hampton, Middlesex TW12 2BX Hampton, Middlesex TW12 2BX
UK UK
 End of changes. 33 change blocks. 
153 lines changed or deleted 194 lines changed or added

This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/