draft-ietf-kitten-gssapi-extensions-iana-05.txt   draft-ietf-kitten-gssapi-extensions-iana-06.txt 
NETWORK WORKING GROUP N. Williams NETWORK WORKING GROUP N. Williams
Internet-Draft Sun Internet-Draft Sun
Intended status: Standards Track March 25, 2009 Intended status: Standards Track April 1, 2009
Expires: September 26, 2009 Expires: October 3, 2009
Namespace Considerations and Registries for GSS-API Extensions Namespace Considerations and Registries for GSS-API Extensions
draft-ietf-kitten-gssapi-extensions-iana-05.txt draft-ietf-kitten-gssapi-extensions-iana-06.txt
Status of this Memo Status of this Memo
This Internet-Draft is submitted to IETF in full conformance with the This Internet-Draft is submitted to IETF 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), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet- other groups may also distribute working documents as Internet-
Drafts. Drafts.
skipping to change at page 1, line 32 skipping to change at page 1, line 32
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."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on September 26, 2009. This Internet-Draft will expire on October 3, 2009.
Copyright Notice Copyright Notice
Copyright (c) 2009 IETF Trust and the persons identified as the Copyright (c) 2009 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 in effect on the date of Provisions Relating to IETF Documents in effect on the date of
publication of this document (http://trustee.ietf.org/license-info). publication of this document (http://trustee.ietf.org/license-info).
Please review these documents carefully, as they describe your rights Please review these documents carefully, as they describe your rights
skipping to change at page 5, line 42 skipping to change at page 5, line 42
| | | and Sub-namespace | | | | and Sub-namespace |
| | | registrations of Constant | | | | registrations of Constant |
| | | object types. | | | | object types. |
+--------------+---------------------+------------------------------+ +--------------+---------------------+------------------------------+
| Description | <Text> | Description of the | | Description | <Text> | Description of the |
| | | registration. Multiple | | | | registration. Multiple |
| | | instances of this field may | | | | instances of this field may |
| | | result (see Section 8.2.3). | | | | result (see Section 8.2.3). |
+--------------+---------------------+------------------------------+ +--------------+---------------------+------------------------------+
| Registration | Values from | Describes the rules for | | Registration | Values from | Describes the rules for |
| Rules | [RFC2434], such as | allocation of items that | | Rules | [RFC5226], such as | allocation of items that |
| | 'IESG Approval', | fall in this sub-namespace, | | | 'IESG Approval', | fall in this sub-namespace, |
| | 'Expert Review', | for entries with | | | 'Expert Review', | for entries with |
| | 'First Come First | Registration Type of | | | 'First Come First | Registration Type of |
| | Served', 'Private | Sub-namespace (OPTIONAL). | | | Served', 'Private | Sub-namespace (OPTIONAL). |
| | Use', etcetera. | For private use | | | Use', etcetera. | For private use |
| | | sub-namespaces the submitter | | | | sub-namespaces the submitter |
| | | MUST provide the e-mail | | | | MUST provide the e-mail |
| | | address of a responsible | | | | address of a responsible |
| | | contact. | | | | contact. |
| Reference | <Reference> | Reference to document that | | Reference | <Reference> | Reference to document that |
skipping to change at page 9, line 20 skipping to change at page 9, line 20
Registrations may be modified by addtion, but under no circumstance Registrations may be modified by addtion, but under no circumstance
may any fields be modified except for the Status field. may any fields be modified except for the Status field.
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
General security considerations relating to IANA registration General security considerations relating to IANA registration
services apply; see [RFC2434]. 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.
[RFC2434] 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 2434, IANA Considerations Section in RFCs", BCP 26, RFC 5226,
October 1998. 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 1964, June 1996. RFC 1964, June 1996.
[RFC2743] Linn, J., "Generic Security Service Application Program [RFC2743] Linn, J., "Generic Security Service Application Program
Interface Version 2, Update 1", RFC 2743, January 2000. 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 :
 End of changes. 6 change blocks. 
9 lines changed or deleted 9 lines changed or added

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