draft-ietf-kitten-krb5-gssapi-domain-based-names-05.txt   rfc5179.txt 
NETWORK WORKING GROUP N. Williams Network Working Group N. Williams
Internet-Draft Sun Request for Comments: 5179 Sun
Expires: July 27, 2008 January 24, 2008 Generic Security Service Application Program Interface (GSS-API)
Domain-Based Service Names Mapping for the Kerberos V GSS Mechanism
GSS-API Domain-Based Service Names Mapping for the Kerberos V GSS
Mechanism
draft-ietf-kitten-krb5-gssapi-domain-based-names-05.txt
Status of this Memo
By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware
have been or will be disclosed, and any of which he or she becomes
aware will be disclosed, in accordance with Section 6 of BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet-
Drafts.
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."
The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html.
This Internet-Draft will expire on July 27, 2008.
Copyright Notice Status of This Memo
Copyright (C) The IETF Trust (2008). This document specifies an Internet standards track protocol for the
Internet community, and requests discussion and suggestions for
improvements. Please refer to the current edition of the "Internet
Official Protocol Standards" (STD 1) for the standardization state
and status of this protocol. Distribution of this memo is unlimited.
Abstract Abstract
This document describes the mapping of GSS-API domainname-based This document describes the mapping of Generic Security Service
service principal names onto Kerberos V principal names. Application Program Interface (GSS-API) domain-name-based service
principal names onto Kerberos V principal names.
Table of Contents Table of Contents
1. Conventions used in this document . . . . . . . . . . . . . . . 3 1. Domain-Based Names for the Kerberos V GSS-API Mechanism . . . . 2
2. Domain-Based Names for the Kerberos V GSS-API Mechanism . . . . 3 2. Conventions Used in This Document . . . . . . . . . . . . . . . 2
3. Internationalization considerations . . . . . . . . . . . . . . 3 3. Internationalization Considerations . . . . . . . . . . . . . . 2
4. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 4. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
5. Security Considerations . . . . . . . . . . . . . . . . . . . . 4 5. Security Considerations . . . . . . . . . . . . . . . . . . . . 3
6. Normative References . . . . . . . . . . . . . . . . . . . . . 4 6. Normative References . . . . . . . . . . . . . . . . . . . . . 3
Author's Address . . . . . . . . . . . . . . . . . . . . . . . 5
Intellectual Property and Copyright Statements . . . . . . . . 6
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. Domain-Based Names for the Kerberos V GSS-API Mechanism 1. Domain-Based Names for the Kerberos V GSS-API Mechanism
In accordance with [I-D.ietf-kitten-gssapi-domain-based-names] this In accordance with [RFC5178], this document provides the mechanism-
document provides the mechanism-specific details needed to implement specific details needed to implement GSS-API [RFC2743] domain-based
GSS-API [RFC2743] domain-based service names with the Kerberos V GSS- service names with the Kerberos V GSS-API mechanism [RFC4121].
API mechanism [RFC4121].
GSS_C_NT_DOMAINBASED_SERVICE name SHOULD be mapped to Kerberos V GSS_C_NT_DOMAINBASED_SERVICE name SHOULD be mapped to Kerberos V
principal names as follows: principal names as follows:
o the <service> name becomes the first (0th) component of the o the <service> name becomes the first (0th) component of the
Kerberos V principal name; Kerberos V principal name;
o the <hostname> becomes the second component of the Kerberos V o the <hostname> becomes the second component of the Kerberos V
principal name; principal name;
o the <domain> name becomes the third component of the Kerberos V o the <domain> name becomes the third component of the Kerberos V
principal name; principal name;
o the realm of the resulting principal name is that which o the realm of the resulting principal name is that which
corresponds to the domain name, treated as a hostname. corresponds to the domain name, treated as a hostname.
The same name canonicalization considerations and methods as used The same name canonicalization considerations and methods as used
elsewhere in the Kerberos V GSS-API mechanism [RFC4121] and Kerberos elsewhere in the Kerberos V GSS-API mechanism [RFC4121] and Kerberos
V [RFC4120] in general apply here. V [RFC4120] in general apply here.
Implementations SHOULD use a Kerberos V name-type of NT-SRV-HST- Implementations SHOULD use a Kerberos V name-type of
DOMAIN (integral value to be assigned, possibly after WGLC?) but MAY NTT-SRVT-HST-DOMAIN (which has the value 12) but MAY use NT-UNKNOWN
use NT-UNKNOWN instead. instead.
3. Internationalization considerations 2. 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].
3. Internationalization Considerations
It is unclear, at this time, how best to address internationalization It is unclear, at this time, how best to address internationalization
of Kerberos V domain-based principal names. This is because the of Kerberos V domain-based principal names. This is because the
Kerberos V core protocol internationalization project is incomplete. Kerberos V core protocol internationalization project is incomplete.
However, clearly the best way to interoperate when using Kerberos V However, clearly the best way to interoperate when using Kerberos V
domain-based principal names is to use ACE-encoded internationalized domain-based principal names is to use ACE-encoded internationalized
domain names [RFC3490] for the hostname and domain name slots of a domain names [RFC3490] for the hostname and domain name slots of a
Kerberos V domain-based principal name. Therefore Kerberos V GSS-API Kerberos V domain-based principal name. Therefore Kerberos V GSS-API
mechanism implementations MUST do just that. mechanism implementations MUST do just that.
4. Examples 4. Examples
o The domain based name, of generic form,
o The domain-based name, of generic form,
"ldap@foo.example@ds1.foo.example" may map to a Kerberos V "ldap@foo.example@ds1.foo.example" may map to a Kerberos V
principal name like: "ldap/ds1.foo.example/ principal name like: "ldap/ds1.foo.example/
foo.example@FOO.EXAMPLE" foo.example@FOO.EXAMPLE"
o The domain based name, of generic form,
o The domain-based name, of generic form,
"kadmin@foo.example@kdc1.foo.example" may map to a Kerberos V "kadmin@foo.example@kdc1.foo.example" may map to a Kerberos V
principal name like: "kadmin/kdc1.foo.example/ principal name like: "kadmin/kdc1.foo.example/
foo.example@FOO.EXAMPLE" foo.example@FOO.EXAMPLE"
5. Security Considerations 5. Security Considerations
See [I-D.ietf-kitten-gssapi-domain-based-names]. See [RFC5178].
It is important for the security of protocols using the Kerberos V It is important for the security of protocols using the Kerberos V
GSS-API mechanism and domain-based names, that the realm of domain- GSS-API mechanism and domain-based names, that the realm of domain-
based principal names be derived from the hostname, rather than the based principal names be derived from the hostname, rather than the
domain name slots of the input domain-based name string. domain name slots of the input domain-based name string.
6. Normative References 6. Normative References
[I-D.ietf-kitten-gssapi-domain-based-names]
Williams, N. and A. Melnikov, "GSS-API
Internationalization and Domain-Based Service Names and
Name Type", draft-ietf-kitten-gssapi-domain-based-names-05
(work in progress), December 2007.
[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 [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.
[RFC3490] Faltstrom, P., Hoffman, P., and A. Costello, [RFC3490] Faltstrom, P., Hoffman, P., and A. Costello,
"Internationalizing Domain Names in Applications (IDNA)", "Internationalizing Domain Names in Applications (IDNA)",
RFC 3490, March 2003. RFC 3490, March 2003.
[RFC4120] Neuman, C., Yu, T., Hartman, S., and K. Raeburn, "The [RFC4120] Neuman, C., Yu, T., Hartman, S., and K. Raeburn, "The
Kerberos Network Authentication Service (V5)", RFC 4120, Kerberos Network Authentication Service (V5)", RFC 4120,
July 2005. July 2005.
[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 2005. July 2005.
[RFC5178] Williams, N. and A. Melnikov, "Generic Security Service
Application Program Interface (GSS-API)
Internationalization and Domain-Based Service Names and
Name Type", RFC 5178, May 2008.
Author's Address Author's Address
Nicolas Williams Nicolas Williams
Sun Microsystems Sun Microsystems
5300 Riata Trace Ct 5300 Riata Trace Ct.
Austin, TX 78727 Austin, TX 78727
US US
Email: Nicolas.Williams@sun.com EMail: Nicolas.Williams@sun.com
Full Copyright Statement Full Copyright Statement
Copyright (C) The IETF Trust (2008). Copyright (C) The IETF Trust (2008).
This document is subject to the rights, licenses and restrictions This document is subject to the rights, licenses and restrictions
contained in BCP 78, and except as set forth therein, the authors contained in BCP 78, and except as set forth therein, the authors
retain all their rights. retain all their rights.
This document and the information contained herein are provided on an This document and the information contained herein are provided on an
skipping to change at page 6, line 44 skipping to change at line 173
attempt made to obtain a general license or permission for the use of attempt made to obtain a general license or permission for the use of
such proprietary rights by implementers or users of this such proprietary rights by implementers or users of this
specification can be obtained from the IETF on-line IPR repository at specification can be obtained from the IETF on-line IPR repository at
http://www.ietf.org/ipr. http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at this standard. Please address the information to the IETF at
ietf-ipr@ietf.org. ietf-ipr@ietf.org.
Acknowledgment
Funding for the RFC Editor function is provided by the IETF
Administrative Support Activity (IASA).
 End of changes. 21 change blocks. 
70 lines changed or deleted 49 lines changed or added

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