1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
|
Network Working Group N. Williams
Request for Comments: 5179 Sun
Category: Standards Track May 2008
Generic Security Service Application Program Interface (GSS-API)
Domain-Based Service Names Mapping for the Kerberos V GSS Mechanism
Status of This Memo
This document specifies an Internet standards track protocol for the
Internet community, and requests discussion and suggestions for
improvements. Please refer to the current edition of the "Internet
Official Protocol Standards" (STD 1) for the standardization state
and status of this protocol. Distribution of this memo is unlimited.
Abstract
This document describes the mapping of Generic Security Service
Application Program Interface (GSS-API) domain-name-based service
principal names onto Kerberos V principal names.
Table of Contents
1. Domain-Based Names for the Kerberos V GSS-API Mechanism . . . . 2
2. Conventions Used in This Document . . . . . . . . . . . . . . . 2
3. Internationalization Considerations . . . . . . . . . . . . . . 2
4. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
5. Security Considerations . . . . . . . . . . . . . . . . . . . . 3
6. Normative References . . . . . . . . . . . . . . . . . . . . . 3
Williams Standards Track [Page 1]
^L
RFC 5179 Kerberos Domain-Based Names May 2008
1. Domain-Based Names for the Kerberos V GSS-API Mechanism
In accordance with [RFC5178], 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
NTT-SRVT-HST-DOMAIN (which has the value 12) but MAY use NT-UNKNOWN
instead.
2. 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].
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.
Williams Standards Track [Page 2]
^L
RFC 5179 Kerberos Domain-Based Names May 2008
4. Examples
o The domain-based name, of generic form,
"ldap@foo.example@ds1.foo.example" may map to a Kerberos V
principal name like: "ldap/ds1.foo.example/
foo.example@FOO.EXAMPLE"
o The domain-based name, of generic form,
"kadmin@foo.example@kdc1.foo.example" may map to a Kerberos V
principal name like: "kadmin/kdc1.foo.example/
foo.example@FOO.EXAMPLE"
5. Security Considerations
See [RFC5178].
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
[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.
[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
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.
[RFC5178] Williams, N. and A. Melnikov, "Generic Security Service
Application Program Interface (GSS-API)
Internationalization and Domain-Based Service Names and
Name Type", RFC 5178, May 2008.
Williams Standards Track [Page 3]
^L
RFC 5179 Kerberos Domain-Based Names May 2008
Author's Address
Nicolas Williams
Sun Microsystems
5300 Riata Trace Ct.
Austin, TX 78727
US
EMail: Nicolas.Williams@sun.com
Williams Standards Track [Page 4]
^L
RFC 5179 Kerberos Domain-Based Names May 2008
Full Copyright Statement
Copyright (C) The IETF Trust (2008).
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, THE IETF TRUST 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.
Williams Standards Track [Page 5]
^L
|
