draft-ietf-kitten-krb5-gssapi-domain-based-names-02.txt   draft-ietf-kitten-krb5-gssapi-domain-based-names-03.txt 
NETWORK WORKING GROUP N. Williams NETWORK WORKING GROUP N. Williams
Internet-Draft Sun Internet-Draft Sun
Expires: December 28, 2006 June 26, 2006 Intended status: Informational September 12, 2006
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-02.txt draft-ietf-kitten-krb5-gssapi-domain-based-names-03.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 34 skipping to change at page 1, line 35
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 28, 2006. This Internet-Draft will expire on March 16, 2007.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2006). Copyright (C) The Internet Society (2006).
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 . . . . 3
3. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 3. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
4. Security Considerations . . . . . . . . . . . . . . . . . . . . 6 4. Security Considerations . . . . . . . . . . . . . . . . . . . . 3
5. Normative . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 5. Normative References . . . . . . . . . . . . . . . . . . . . . 4
Author's Address . . . . . . . . . . . . . . . . . . . . . . . 7 Author's Address . . . . . . . . . . . . . . . . . . . . . . . 4
Intellectual Property and Copyright Statements . . . . . . . . 8 Intellectual Property and Copyright Statements . . . . . . . . 5
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 [I-D.ietf-kitten-gssapi-domain-based-names] this
mechanism-specific details needed to implement GSS-API [RFC2743] document provides the mechanism-specific details needed to implement
domain-based service names with the Kerberos V GSS-API mechanism GSS-API [RFC2743] domain-based service names with the Kerberos V GSS-
[RFC4121]. API mechanism [RFC4121].
GSS_C_NT_DOMAINBASED_SERVICE name are mapped to Kerberos V principal
names as follows:
GSS_C_NT_DOMAINBASED_SERVICE name SHOULD be mapped to Kerberos V
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 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.
skipping to change at page 5, line 11 skipping to change at page 3, line 43
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. 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 [I-D.ietf-kitten-gssapi-domain-based-names].
See [DOMAIN-BASED-NAMES]. 5. Normative References
5. Normative
[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". Type", draft-ietf-kitten-gssapi-domain-based-names-01
(work in progress), October 2005.
[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 [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.
skipping to change at page 8, line 5 skipping to change at page 5, line 5
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 Full Copyright Statement
Copyright (C) The Internet Society (2006).
This document is subject to the rights, licenses and restrictions
contained in BCP 78, and except as set forth therein, the authors
retain all their rights.
This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
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
on the procedures with respect to rights in RFC documents can be on the procedures with respect to rights in RFC documents can be
found in BCP 78 and BCP 79. found in BCP 78 and BCP 79.
skipping to change at page 8, line 29 skipping to change at page 5, line 45
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.
Disclaimer of Validity
This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Copyright Statement
Copyright (C) The Internet Society (2006). This document is subject
to the rights, licenses and restrictions contained in BCP 78, and
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 provided by the IETF
Internet Society. Administrative Support Activity (IASA).
 End of changes. 17 change blocks. 
42 lines changed or deleted 38 lines changed or added

This html diff was produced by rfcdiff 1.32. The latest version is available from http://www.levkowetz.com/ietf/tools/rfcdiff/