idnits 2.17.1 draft-ietf-kitten-krb5-gssapi-domain-based-names-02.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** It looks like you're using RFC 3978 boilerplate. You should update this to the boilerplate described in the IETF Trust License Policy document (see https://trustee.ietf.org/license-info), which is required now. -- Found old boilerplate from RFC 3978, Section 5.1 on line 15. -- Found old boilerplate from RFC 3978, Section 5.5 on line 169. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 146. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 153. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 159. ** This document has an original RFC 3978 Section 5.4 Copyright Line, instead of the newer IETF Trust Copyright according to RFC 4748. ** This document has an original RFC 3978 Section 5.5 Disclaimer, instead of the newer disclaimer which includes the IETF Trust according to RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- == No 'Intended status' indicated for this document; assuming Proposed Standard Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an Introduction section. ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (June 26, 2006) is 6511 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) -- Missing reference section? 'RFC2119' on line 112 looks like a reference -- Missing reference section? 'DOMAIN-BASED-NAMES' on line 108 looks like a reference -- Missing reference section? 'RFC2743' on line 115 looks like a reference -- Missing reference section? 'RFC4121' on line 122 looks like a reference -- Missing reference section? 'RFC4120' on line 118 looks like a reference Summary: 5 errors (**), 0 flaws (~~), 2 warnings (==), 12 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 NETWORK WORKING GROUP N. Williams 3 Internet-Draft Sun 4 Expires: December 28, 2006 June 26, 2006 6 GSS-API Domain-Based Service Names Mapping for the Kerberos V GSS 7 Mechanism 8 draft-ietf-kitten-krb5-gssapi-domain-based-names-02.txt 10 Status of this Memo 12 By submitting this Internet-Draft, each author represents that any 13 applicable patent or other IPR claims of which he or she is aware 14 have been or will be disclosed, and any of which he or she becomes 15 aware will be disclosed, in accordance with Section 6 of BCP 79. 17 Internet-Drafts are working documents of the Internet Engineering 18 Task Force (IETF), its areas, and its working groups. Note that 19 other groups may also distribute working documents as Internet- 20 Drafts. 22 Internet-Drafts are draft documents valid for a maximum of six months 23 and may be updated, replaced, or obsoleted by other documents at any 24 time. It is inappropriate to use Internet-Drafts as reference 25 material or to cite them other than as "work in progress." 27 The list of current Internet-Drafts can be accessed at 28 http://www.ietf.org/ietf/1id-abstracts.txt. 30 The list of Internet-Draft Shadow Directories can be accessed at 31 http://www.ietf.org/shadow.html. 33 This Internet-Draft will expire on December 28, 2006. 35 Copyright Notice 37 Copyright (C) The Internet Society (2006). 39 Abstract 41 This document describes the mapping of GSS-API domainname-based 42 service principal names onto Kerberos V principal names. 44 Table of Contents 46 1. Conventions used in this document . . . . . . . . . . . . . . . 3 47 2. Domain-Based Names for the Kerberos V GSS-API Mechanism . . . . 4 48 3. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 49 4. Security Considerations . . . . . . . . . . . . . . . . . . . . 6 50 5. Normative . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 51 Author's Address . . . . . . . . . . . . . . . . . . . . . . . 7 52 Intellectual Property and Copyright Statements . . . . . . . . 8 54 1. Conventions used in this document 56 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 57 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 58 document are to be interpreted as described in [RFC2119]. 60 2. Domain-Based Names for the Kerberos V GSS-API Mechanism 62 In accordance with [DOMAIN-BASED-NAMES] this document provides the 63 mechanism-specific details needed to implement GSS-API [RFC2743] 64 domain-based service names with the Kerberos V GSS-API mechanism 65 [RFC4121]. 67 GSS_C_NT_DOMAINBASED_SERVICE name are mapped to Kerberos V principal 68 names as follows: 70 o the name becomes the first (0th) component of the 71 Kerberos V principal name; 73 o the becomes the second component of the Kerberos V 74 principal name; 76 o the name becomes the third component of the Kerberos V 77 principal name; 79 o the realm of the resulting principal name is that which 80 corresponds to the domain name, treated as a hostname. 82 The same name canonicalization considerations and methods as used 83 elsewhere in the Kerberos V GSS-API mechanism [RFC4121] and Kerberos 84 V [RFC4120] in general apply here. 86 Implementations SHOULD use a Kerberos V name-type of NT-SRV-HST- 87 DOMAIN (integral value to be assigned, possibly after WGLC?) but MAY 88 use NT-UNKNOWN instead. 90 3. Examples 92 o The domain based name, of generic form, 93 "ldap@Example.TLD@ds1.Example.TLD" may map to a Kerberos V 94 principal name like: "ldap/ds1.example.tld/ 95 example.tld@EXAMPLE.TLD" 97 o The domain based name, of generic form, 98 "kadmin@Example.TLD@kdc1.Example.TLD" may map to a Kerberos V 99 principal name like: "kadmin/kdc1.example.tld/ 100 example.tld@EXAMPLE.TLD" 102 4. Security Considerations 104 See [DOMAIN-BASED-NAMES]. 106 5. Normative 108 [DOMAIN-BASED-NAMES] 109 Williams, N., "GSS-API Domain-Based Service Names and Name 110 Type". 112 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 113 Requirement Levels", BCP 14, RFC 2119, March 1997. 115 [RFC2743] Linn, J., "Generic Security Service Application Program 116 Interface Version 2, Update 1", RFC 2743, January 2000. 118 [RFC4120] Neuman, C., Yu, T., Hartman, S., and K. Raeburn, "The 119 Kerberos Network Authentication Service (V5)", RFC 4120, 120 July 2005. 122 [RFC4121] Zhu, L., Jaganathan, K., and S. Hartman, "The Kerberos 123 Version 5 Generic Security Service Application Program 124 Interface (GSS-API) Mechanism: Version 2", RFC 4121, 125 July 2005. 127 Author's Address 129 Nicolas Williams 130 Sun Microsystems 131 5300 Riata Trace Ct 132 Austin, TX 78727 133 US 135 Email: Nicolas.Williams@sun.com 137 Intellectual Property Statement 139 The IETF takes no position regarding the validity or scope of any 140 Intellectual Property Rights or other rights that might be claimed to 141 pertain to the implementation or use of the technology described in 142 this document or the extent to which any license under such rights 143 might or might not be available; nor does it represent that it has 144 made any independent effort to identify any such rights. Information 145 on the procedures with respect to rights in RFC documents can be 146 found in BCP 78 and BCP 79. 148 Copies of IPR disclosures made to the IETF Secretariat and any 149 assurances of licenses to be made available, or the result of an 150 attempt made to obtain a general license or permission for the use of 151 such proprietary rights by implementers or users of this 152 specification can be obtained from the IETF on-line IPR repository at 153 http://www.ietf.org/ipr. 155 The IETF invites any interested party to bring to its attention any 156 copyrights, patents or patent applications, or other proprietary 157 rights that may cover technology that may be required to implement 158 this standard. Please address the information to the IETF at 159 ietf-ipr@ietf.org. 161 Disclaimer of Validity 163 This document and the information contained herein are provided on an 164 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS 165 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET 166 ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, 167 INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE 168 INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 169 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 171 Copyright Statement 173 Copyright (C) The Internet Society (2006). This document is subject 174 to the rights, licenses and restrictions contained in BCP 78, and 175 except as set forth therein, the authors retain all their rights. 177 Acknowledgment 179 Funding for the RFC Editor function is currently provided by the 180 Internet Society.