1NETWORK WORKING GROUP N. Williams 2Internet-Draft Sun 3Expires: December 30, 2004 July 2004 4 5 6 7 GSS-API Domain-Based Service Names and Name Type 8 draft-williams-gssapi-domain-based-names-00.txt 9 10 11Status of this Memo 12 13 14 By submitting this Internet-Draft, I certify that any applicable 15 patent or other IPR claims of which I am aware have been disclosed, 16 and any of which I become aware will be disclosed, in accordance with 17 RFC 3668. 18 19 20 Internet-Drafts are working documents of the Internet Engineering 21 Task Force (IETF), its areas, and its working groups. Note that 22 other groups may also distribute working documents as 23 Internet-Drafts. 24 25 26 Internet-Drafts are draft documents valid for a maximum of six months 27 and may be updated, replaced, or obsoleted by other documents at any 28 time. It is inappropriate to use Internet-Drafts as reference 29 material or to cite them other than as "work in progress." 30 31 32 The list of current Internet-Drafts can be accessed at 33 http://www.ietf.org/ietf/1id-abstracts.txt. 34 35 36 The list of Internet-Draft Shadow Directories can be accessed at 37 http://www.ietf.org/shadow.html. 38 39 40 This Internet-Draft will expire on December 30, 2004. 41 42 43Copyright Notice 44 45 46 Copyright (C) The Internet Society (2004). All Rights Reserved. 47 48 49Abstract 50 51 52 This document describes domainname-based service principal names and 53 the corresponding name type for the GSS-API. 54 55 56 Domain-based service names are similar to host-based service names, 57 but using a domain name (not necessarily and Internat domain name) 58 instead of or in addition to a hostname. The primary purpose of 59 domain-based service names is to provide a way to name clustered 60 services after the domain which they service, thereby allowing their 61 clients to authorize the service's servers based on authentication of 62 their names. 63 64 65 66 67Williams Expires December 30, 2004 [Page 1] 68Internet-Draft GSS Domain Based Names July 2004 69 70 71 72Table of Contents 73 74 75 1. Conventions used in this document . . . . . . . . . . . . . . . 3 76 2. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . 4 77 3. Name Type OID and Symbolic Name . . . . . . . . . . . . . . . . 5 78 4. Query and Display Syntaxes . . . . . . . . . . . . . . . . . . . 6 79 5. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 80 6. Security Considerations . . . . . . . . . . . . . . . . . . . . 8 81 7. Normative . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 82 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 8 83 Intellectual Property and Copyright Statements . . . . . . . . . 9 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 125Williams Expires December 30, 2004 [Page 2] 126Internet-Draft GSS Domain Based Names July 2004 127 128 129 1301. Conventions used in this document 131 132 133 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 134 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 135 document are to be interpreted as described in [RFC2119]. 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 183Williams Expires December 30, 2004 [Page 3] 184Internet-Draft GSS Domain Based Names July 2004 185 186 187 1882. Introduction 189 190 191 The use of hostbased principal names for domain-wide services 192 presents the problem of how to distinguish between an instance of a 193 hostbased service that is authorized to respond for a domain and one 194 that isn't. 195 196 197 Consider LDAP. LDAP with SASL and the Kerberos V GSS-API mechanism 198 uses a hostbased principal with a service name of "ldap", a 199 reasonable approach, provided there is only one logical LDAP 200 directory in a Kerberos realm's domain, and that all ldap servers in 201 that realm serve that one LDAP directory. If there were other LDAP 202 directories, then clients could not tell which service is authorized 203 to serve which directory, not without assuming a secure method for 204 finding LDAP servers (e.g., DNSSEC). This is a significant, and 205 oft-unstated restriction on users of LDAP. 206 207 208 Domain based names can eliminate this problem by allowing LDAP 209 service names to indicate which LDAP directory they are authorized to 210 serve. 211 212 213 A domain-based name consists of three required elements: 214 o a service name 215 o a domain name 216 o a hostname 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 244Williams Expires December 30, 2004 [Page 4] 245Internet-Draft GSS Domain Based Names July 2004 246 247 248 2493. Name Type OID and Symbolic Name 250 251 252 The new name type has an OID of 253 [NOTE: OID assignment to be made with IANA.] 254 255 256 {iso(1) org(3) dod(6) internet(1) security(5) nametypes(6) 257 gss-domain-based(5)} 258 259 260 The recommended symbolic name for this GSS-API name type is 261 "GSS_C_NT_DOMAINBASED_SERVICE". 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304Williams Expires December 30, 2004 [Page 5] 305Internet-Draft GSS Domain Based Names July 2004 306 307 308 3094. Query and Display Syntaxes 310 311 312 There is a single syntax that applies to both query and display forms 313 of domain-based names. (We ignore string profile matters here as the 314 GSS-API's, and its mechanisms' use of character strings are out of 315 scope for this document.) 316 317 318 The syntax is: 319 domain-based-name := 320 | <service> '@' <domain> '@' <hostname> 321 | <service> '@@' <hostname> 322 323 324 The domain name element is only optional in the query syntax of 325 domain-based names. 326 327 328 A missing domain name is always to be added by the GSS-API mechanisms 329 during name canonicalization, using whatever default values are 330 appropriate for the mechanisms. 331 332 333 Therefore the display form of domain-based MNs (see [RFC2743]) MUST 334 include all three elements of domain-based names. 335 336 337 Note that for Internet domain names the trailing '.' is not and MUST 338 NOT be included in the domain name (or hostname) parts of the display 339 form GSS-API domain-based MNs. 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 360 361 362 363 364 365 366 367Williams Expires December 30, 2004 [Page 6] 368Internet-Draft GSS Domain Based Names July 2004 369 370 371 3725. Examples 373 374 375 o ldap@@ds1.example.tld 376 o ldap@example.tld@ds1.example.tld 377 378 379 o kadmin@@kdc1.example.tld 380 o kadmin@example.tld@kdc1.example.tld 381 382 383 384 385 386 387 388 389 390 391 392 393 394 395 396 397 398 399 400 401 402 403 404 405 406 407 408 409 410 411 412 413 414 415 416 417 418 419 420 421 422 423 424 425 426Williams Expires December 30, 2004 [Page 7] 427Internet-Draft GSS Domain Based Names July 2004 428 429 430 4316. Security Considerations 432 433 434 Use of GSS-API domain-based names may not be negotiable by some 435 GSS-API mechanisms, and some acceptors may not support GSS-API 436 domain-based names. In such cases initiators are left to fallback on 437 the use of hostbased names, in which case the initiators MUST also 438 verify that the acceptor's hostbased name is authorized to provide 439 the given service for the domain that the initiator had wanted. 440 441 442 The above security consideration also applies to all GSS-API 443 initiators who lack support for domain-based service names. 444 445 4467 Normative 447 448 449 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 450 Requirement Levels", BCP 14, RFC 2119, March 1997. 451 452 453 [RFC2743] Linn, J., "Generic Security Service Application Program 454 Interface Version 2, Update 1", RFC 2743, January 2000. 455 456 457 [RFC2744] Wray, J., "Generic Security Service API Version 2 : 458 C-bindings", RFC 2744, January 2000. 459 460 461 462Author's Address 463 464 465 Nicolas Williams 466 Sun Microsystems 467 5300 Riata Trace Ct 468 Austin, TX 78727 469 US 470 471 472 EMail: Nicolas.Williams@sun.com 473 474 475 476 477 478 479 480 481 482 483 484 485 486 487 488 489 490 491 492Williams Expires December 30, 2004 [Page 8] 493Internet-Draft GSS Domain Based Names July 2004 494 495 496 497Intellectual Property Statement 498 499 500 The IETF takes no position regarding the validity or scope of any 501 Intellectual Property Rights or other rights that might be claimed to 502 pertain to the implementation or use of the technology described in 503 this document or the extent to which any license under such rights 504 might or might not be available; nor does it represent that it has 505 made any independent effort to identify any such rights. Information 506 on the procedures with respect to rights in RFC documents can be 507 found in BCP 78 and BCP 79. 508 509 510 Copies of IPR disclosures made to the IETF Secretariat and any 511 assurances of licenses to be made available, or the result of an 512 attempt made to obtain a general license or permission for the use of 513 such proprietary rights by implementers or users of this 514 specification can be obtained from the IETF on-line IPR repository at 515 http://www.ietf.org/ipr. 516 517 518 The IETF invites any interested party to bring to its attention any 519 copyrights, patents or patent applications, or other proprietary 520 rights that may cover technology that may be required to implement 521 this standard. Please address the information to the IETF at 522 ietf-ipr@ietf.org. 523 524 525 526Disclaimer of Validity 527 528 529 This document and the information contained herein are provided on an 530 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS 531 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET 532 ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, 533 INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE 534 INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 535 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 536 537 538 539Copyright Statement 540 541 542 Copyright (C) The Internet Society (2004). This document is subject 543 to the rights, licenses and restrictions contained in BCP 78, and 544 except as set forth therein, the authors retain all their rights. 545 546 547 548Acknowledgment 549 550 551 Funding for the RFC Editor function is currently provided by the 552 Internet Society. 553 554 555 556 557Williams Expires December 30, 2004 [Page 9]