[Docs] [txt|pdf] [Tracker] [WG] [Email] [Diff1] [Diff2] [Nits]

Versions: 00 01 02 03 04 05 RFC 5179

NETWORK WORKING GROUP                                        N. Williams
Internet-Draft                                                       Sun
Intended status: Informational                        September 12, 2006
Expires: March 16, 2007


   GSS-API Domain-Based Service Names Mapping for the Kerberos V GSS
                               Mechanism
        draft-ietf-kitten-krb5-gssapi-domain-based-names-03.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 March 16, 2007.

Copyright Notice

   Copyright (C) The Internet Society (2006).

Abstract

   This document describes the mapping of GSS-API domainname-based
   service principal names onto Kerberos V principal names.








Williams                 Expires March 16, 2007                 [Page 1]

Internet-Draft         Kerberos Domain Based Names        September 2006


Table of Contents

   1.  Conventions used in this document . . . . . . . . . . . . . . . 3
   2.  Domain-Based Names for the Kerberos V GSS-API Mechanism . . . . 3
   3.  Examples  . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
   4.  Security Considerations . . . . . . . . . . . . . . . . . . . . 3
   5.  Normative References  . . . . . . . . . . . . . . . . . . . . . 4
       Author's Address  . . . . . . . . . . . . . . . . . . . . . . . 4
       Intellectual Property and Copyright Statements  . . . . . . . . 5










































Williams                 Expires March 16, 2007                 [Page 2]

Internet-Draft         Kerberos Domain Based Names        September 2006


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

   In accordance with [I-D.ietf-kitten-gssapi-domain-based-names] this
   document provides the mechanism-specific details needed to implement
   GSS-API [RFC2743] domain-based service names with the Kerberos V GSS-
   API mechanism [RFC4121].

   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
      Kerberos V principal name;
   o  the <hostname> becomes the second component of the Kerberos V
      principal name;
   o  the <domain> name becomes the third component of the Kerberos V
      principal name;
   o  the realm of the resulting principal name is that which
      corresponds to the domain name, treated as a hostname.

   The same name canonicalization considerations and methods as used
   elsewhere in the Kerberos V GSS-API mechanism [RFC4121] and Kerberos
   V [RFC4120] in general apply here.

   Implementations SHOULD use a Kerberos V name-type of NT-SRV-HST-
   DOMAIN (integral value to be assigned, possibly after WGLC?) but MAY
   use NT-UNKNOWN instead.


3.  Examples

   o  The domain based name, of generic form,
      "ldap@Example.TLD@ds1.Example.TLD" may map to a Kerberos V
      principal name like: "ldap/ds1.example.tld/
      example.tld@EXAMPLE.TLD"
   o  The domain based name, of generic form,
      "kadmin@Example.TLD@kdc1.Example.TLD" may map to a Kerberos V
      principal name like: "kadmin/kdc1.example.tld/
      example.tld@EXAMPLE.TLD"


4.  Security Considerations




Williams                 Expires March 16, 2007                 [Page 3]

Internet-Draft         Kerberos Domain Based Names        September 2006


   See [I-D.ietf-kitten-gssapi-domain-based-names].


5.  Normative References

   [I-D.ietf-kitten-gssapi-domain-based-names]
              Williams, N., "GSS-API Domain-Based Service Names and Name
              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
              Requirement Levels", BCP 14, RFC 2119, March 1997.

   [RFC2743]  Linn, J., "Generic Security Service Application Program
              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

   Nicolas Williams
   Sun Microsystems
   5300 Riata Trace Ct
   Austin, TX  78727
   US

   Email: Nicolas.Williams@sun.com
















Williams                 Expires March 16, 2007                 [Page 4]

Internet-Draft         Kerberos Domain Based Names        September 2006


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
   Intellectual Property Rights or other rights that might be claimed to
   pertain to the implementation or use of the technology described in
   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
   made any independent effort to identify any such rights.  Information
   on the procedures with respect to rights in RFC documents can be
   found in BCP 78 and BCP 79.

   Copies of IPR disclosures made to the IETF Secretariat and any
   assurances of licenses to be made available, or the result of an
   attempt made to obtain a general license or permission for the use of
   such proprietary rights by implementers or users of this
   specification can be obtained from the IETF on-line IPR repository at
   http://www.ietf.org/ipr.

   The IETF invites any interested party to bring to its attention any
   copyrights, patents or patent applications, or other proprietary
   rights that may cover technology that may be required to implement
   this standard.  Please address the information to the IETF at
   ietf-ipr@ietf.org.


Acknowledgment

   Funding for the RFC Editor function is provided by the IETF
   Administrative Support Activity (IASA).





Williams                 Expires March 16, 2007                 [Page 5]


Html markup produced by rfcmarkup 1.109, available from https://tools.ietf.org/tools/rfcmarkup/