draft-ietf-kitten-krb5-gssapi-domain-based-names-03.txt   draft-ietf-kitten-krb5-gssapi-domain-based-names-04.txt 
NETWORK WORKING GROUP N. Williams NETWORK WORKING GROUP N. Williams
Internet-Draft Sun Internet-Draft Sun
Intended status: Informational September 12, 2006 Expires: May 22, 2008 November 19, 2007
Expires: March 16, 2007
GSS-API Domain-Based Service Names Mapping for the Kerberos V GSS GSS-API Domain-Based Service Names Mapping for the Kerberos V GSS
Mechanism Mechanism
draft-ietf-kitten-krb5-gssapi-domain-based-names-03.txt draft-ietf-kitten-krb5-gssapi-domain-based-names-04.txt
Status of this Memo Status of this Memo
By submitting this Internet-Draft, each author represents that any By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware 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 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. aware will be disclosed, in accordance with Section 6 of 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
skipping to change at page 1, line 35 skipping to change at page 1, line 34
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 March 16, 2007. This Internet-Draft will expire on May 22, 2008.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2006). Copyright (C) The IETF Trust (2007).
Abstract Abstract
This document describes the mapping of GSS-API domainname-based This document describes the mapping of GSS-API domainname-based
service principal names onto Kerberos V principal names. service principal names onto Kerberos V principal names.
Table of Contents Table of Contents
1. Conventions used in this document . . . . . . . . . . . . . . . 3 1. Conventions used in this document . . . . . . . . . . . . . . . 3
2. Domain-Based Names for the Kerberos V GSS-API Mechanism . . . . 3 2. Domain-Based Names for the Kerberos V GSS-API Mechanism . . . . 3
3. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 3. Internationalization considerations . . . . . . . . . . . . . . 3
4. Security Considerations . . . . . . . . . . . . . . . . . . . . 3 4. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
5. Normative References . . . . . . . . . . . . . . . . . . . . . 4 5. Security Considerations . . . . . . . . . . . . . . . . . . . . 4
6. Normative References . . . . . . . . . . . . . . . . . . . . . 4
Author's Address . . . . . . . . . . . . . . . . . . . . . . . 4 Author's Address . . . . . . . . . . . . . . . . . . . . . . . 4
Intellectual Property and Copyright Statements . . . . . . . . 5 Intellectual Property and Copyright Statements . . . . . . . . 6
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. Domain-Based Names for the Kerberos V GSS-API Mechanism 2. 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 [I-D.ietf-kitten-gssapi-domain-based-names] this
skipping to change at page 3, line 37 skipping to change at page 3, line 37
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 NT-SRV-HST-
DOMAIN (integral value to be assigned, possibly after WGLC?) but MAY DOMAIN (integral value to be assigned, possibly after WGLC?) but MAY
use NT-UNKNOWN instead. use NT-UNKNOWN instead.
3. Examples 3. Internationalization considerations
It is unclear, at this time, how best to address internationalization
of Kerberos V domain-based principal names. This is because the
Kerberos V core protocol internationalization project is incomplete.
However, clearly the best way to interoperate when using Kerberos V
domain-based principal names is to use ACE-encoded internationalized
domain names [RFC3490] for the hostname and domain name slots of a
Kerberos V domain-based principal name. Therefore Kerberos V GSS-API
mechanism implementations MUST do just that.
4. Examples
o The domain based name, of generic form, o The domain based name, of generic form,
"ldap@Example.TLD@ds1.Example.TLD" may map to a Kerberos V "ldap@Example.TLD@ds1.Example.TLD" may map to a Kerberos V
principal name like: "ldap/ds1.example.tld/ principal name like: "ldap/ds1.example.tld/
example.tld@EXAMPLE.TLD" example.tld@EXAMPLE.TLD"
o The domain based name, of generic form, o The domain based name, of generic form,
"kadmin@Example.TLD@kdc1.Example.TLD" may map to a Kerberos V "kadmin@Example.TLD@kdc1.Example.TLD" may map to a Kerberos V
principal name like: "kadmin/kdc1.example.tld/ principal name like: "kadmin/kdc1.example.tld/
example.tld@EXAMPLE.TLD" example.tld@EXAMPLE.TLD"
4. Security Considerations 5. Security Considerations
See [I-D.ietf-kitten-gssapi-domain-based-names]. See [I-D.ietf-kitten-gssapi-domain-based-names].
5. Normative References It is important for the security of protocols using the Kerberos V
GSS-API mechanism and domain-based names, that the realm of domain-
based principal names be derived from the hostname, rather than the
domain name slots of the input domain-based name string.
6. Normative References
[I-D.ietf-kitten-gssapi-domain-based-names] [I-D.ietf-kitten-gssapi-domain-based-names]
Williams, N., "GSS-API Domain-Based Service Names and Name Williams, N., "GSS-API Domain-Based Service Names and Name
Type", draft-ietf-kitten-gssapi-domain-based-names-01 Type", draft-ietf-kitten-gssapi-domain-based-names-03
(work in progress), October 2005. (work in progress), September 2006.
[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,
"Internationalizing Domain Names in Applications (IDNA)",
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.
Author's Address Author's Address
skipping to change at page 5, line 7 skipping to change at page 6, line 7
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 Internet Society (2006). Copyright (C) The IETF Trust (2007).
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
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND
ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS
INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Intellectual Property Intellectual Property
The IETF takes no position regarding the validity or scope of any The IETF takes no position regarding the validity or scope of any
Intellectual Property Rights or other rights that might be claimed to Intellectual Property Rights or other rights that might be claimed to
pertain to the implementation or use of the technology described in pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights this document or the extent to which any license under such rights
might or might not be available; nor does it represent that it has might or might not be available; nor does it represent that it has
made any independent effort to identify any such rights. Information made any independent effort to identify any such rights. Information
 End of changes. 14 change blocks. 
19 lines changed or deleted 40 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/