draft-ietf-kitten-krb5-gssapi-domain-based-names-00.txt   draft-ietf-kitten-krb5-gssapi-domain-based-names-01.txt 
NETWORK WORKING GROUP N. Williams NETWORK WORKING GROUP N. Williams
Internet-Draft Sun Internet-Draft Sun
Expires: December 30, 2004 July 2004 Expires: April 22, 2006 October 19, 2005
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-00.txt draft-ietf-kitten-krb5-gssapi-domain-based-names-01.txt
Status of this Memo Status of this Memo
By submitting this Internet-Draft, I certify that any applicable By submitting this Internet-Draft, each author represents that any
patent or other IPR claims of which I am aware have been disclosed, applicable patent or other IPR claims of which he or she is aware
and any of which I become aware will be disclosed, in accordance with have been or will be disclosed, and any of which he or she becomes
RFC 3668. 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
other groups may also distribute working documents as other groups may also distribute working documents as Internet-
Internet-Drafts. Drafts.
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."
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 December 30, 2004. This Internet-Draft will expire on April 22, 2006.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2004). All Rights Reserved. Copyright (C) The Internet Society (2005).
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 . . . . 4 2. Domain-Based Names for the Kerberos V GSS-API Mechanism . . . . 4
3. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 3. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
4. Security Considerations . . . . . . . . . . . . . . . . . . . . 6 4. Security Considerations . . . . . . . . . . . . . . . . . . . . 6
5. Normative . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 5. Normative . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 6 Author's Address . . . . . . . . . . . . . . . . . . . . . . . 7
Intellectual Property and Copyright Statements . . . . . . . . . 7 Intellectual Property and Copyright Statements . . . . . . . . 8
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 [DOMAIN-BASED-NAMES] this document provides the In accordance with [DOMAIN-BASED-NAMES] this document provides the
mechanism-specific details needed to implement GSS-API [RFC2743] mechanism-specific details needed to implement GSS-API [RFC2743]
domain-based service names with the Kerberos V GSS-API mechanism domain-based service names with the Kerberos V GSS-API mechanism
[RFC1964]. [RFC4121].
GSS_C_NT_DOMAINBASED_SERVICE name are mapped to Kerberos V principal GSS_C_NT_DOMAINBASED_SERVICE name are mapped to Kerberos V principal
names as follows: 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 [RFC1964] and Kerberos elsewhere in the Kerberos V GSS-API mechanism [RFC4121] and Kerberos
V [I-D.ietf-krb-wg-kerberos-clarifications] in general apply here. V [RFC4120] in general apply here.
Implementations SHOULD use a Kerberos V name-type of Implementations SHOULD use a Kerberos V name-type of NT-SRV-HST-
NT-SRV-HST-DOMAIN (integral value TBD) but MAY use NT-UNKNOWN DOMAIN (integral value TBD) but MAY use NT-UNKNOWN instead.
instead.
3. Examples 3. 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 4. Security Considerations
See [DOMAIN-BASED-NAMES]. See [DOMAIN-BASED-NAMES].
5 Normative 5. Normative
[DOMAIN-BASED-NAMES] [DOMAIN-BASED-NAMES]
Williams, N., "GSS-API Domain-Based Service Names and Name Williams, N., "GSS-API Domain-Based Service Names and Name
Type". Type".
[I-D.ietf-krb-wg-kerberos-clarifications]
Neuman, C., "The Kerberos Network Authentication Service
(V5)", draft-ietf-krb-wg-kerberos-clarifications-07 (work
in progress), September 2004.
[RFC1510] Kohl, J. and B. Neuman, "The Kerberos Network
Authentication Service (V5)", RFC 1510, September 1993.
[RFC1964] Linn, J., "The Kerberos Version 5 GSS-API Mechanism", RFC
1964, June 1996.
[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.
[RFC4120] Neuman, C., Yu, T., Hartman, S., and K. Raeburn, "The
Kerberos Network Authentication Service (V5)", RFC 4120,
July 2005.
[RFC4121] Zhu, L., Jaganathan, K., and S. Hartman, "The Kerberos
Version 5 Generic Security Service Application Program
Interface (GSS-API) Mechanism: Version 2", RFC 4121,
July 2005.
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
Intellectual Property Statement Intellectual Property Statement
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
on the procedures with respect to rights in RFC documents can be on the procedures with respect to rights in RFC documents can be
skipping to change at page 7, line 41 skipping to change at page 8, line 41
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 AND THE INTERNET
ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 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.
Copyright Statement Copyright Statement
Copyright (C) The Internet Society (2004). This document is subject Copyright (C) The Internet Society (2005). This document is subject
to the rights, licenses and restrictions contained in BCP 78, and to the rights, licenses and restrictions contained in BCP 78, and
except as set forth therein, the authors retain all their rights. except as set forth therein, the authors retain all their rights.
Acknowledgment Acknowledgment
Funding for the RFC Editor function is currently provided by the Funding for the RFC Editor function is currently provided by the
Internet Society. Internet Society.
 End of changes. 22 change blocks. 
33 lines changed or deleted 36 lines changed or added

This html diff was produced by rfcdiff 1.27, available from http://www.levkowetz.com/ietf/tools/rfcdiff/