1 2 3 4NETWORK WORKING GROUP N. Williams 5Internet-Draft Sun 6Expires: April 19, 2006 October 16, 2005 7 8 9 GSS-API Domain-Based Service Names and Name Type 10 draft-ietf-kitten-gssapi-domain-based-names-01.txt 11 12Status of this Memo 13 14 By submitting this Internet-Draft, each author represents that any 15 applicable patent or other IPR claims of which he or she is aware 16 have been or will be disclosed, and any of which he or she becomes 17 aware will be disclosed, in accordance with Section 6 of BCP 79. 18 19 Internet-Drafts are working documents of the Internet Engineering 20 Task Force (IETF), its areas, and its working groups. Note that 21 other groups may also distribute working documents as Internet- 22 Drafts. 23 24 Internet-Drafts are draft documents valid for a maximum of six months 25 and may be updated, replaced, or obsoleted by other documents at any 26 time. It is inappropriate to use Internet-Drafts as reference 27 material or to cite them other than as "work in progress." 28 29 The list of current Internet-Drafts can be accessed at 30 http://www.ietf.org/ietf/1id-abstracts.txt. 31 32 The list of Internet-Draft Shadow Directories can be accessed at 33 http://www.ietf.org/shadow.html. 34 35 This Internet-Draft will expire on April 19, 2006. 36 37Copyright Notice 38 39 Copyright (C) The Internet Society (2005). 40 41Abstract 42 43 This document describes domainname-based service principal names and 44 the corresponding name type for the Generic Security Service 45 Application Programming Interface (GSS-API). 46 47 Domain-based service names are similar to host-based service names, 48 but using a domain name (not necessarily and Internat domain name) 49 instead of or in addition to a hostname. The primary purpose of 50 domain-based service names is to provide a way to name clustered 51 services after the domain which they service, thereby allowing their 52 53 54 55Williams Expires April 19, 2006 [Page 1] 56 57Internet-Draft GSS Domain Based Names October 2005 58 59 60 clients to authorize the service's servers based on authentication of 61 their names. 62 63 64Table of Contents 65 66 1. Conventions used in this document . . . . . . . . . . . . . 3 67 2. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 4 68 3. Name Type OID and Symbolic Name . . . . . . . . . . . . . . 5 69 4. Query and Display Syntaxes . . . . . . . . . . . . . . . . . 6 70 5. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . 7 71 6. Security Considerations . . . . . . . . . . . . . . . . . . 8 72 7. References . . . . . . . . . . . . . . . . . . . . . . . . . 9 73 7.1. Normative . . . . . . . . . . . . . . . . . . . . . . . . . 9 74 7.2. Informative . . . . . . . . . . . . . . . . . . . . . . . . 9 75 Author's Address . . . . . . . . . . . . . . . . . . . . . . 10 76 Intellectual Property and Copyright Statements . . . . . . . 11 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 111Williams Expires April 19, 2006 [Page 2] 112 113Internet-Draft GSS Domain Based Names October 2005 114 115 1161. Conventions used in this document 117 118 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 119 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 120 document are to be interpreted as described in [RFC2119]. 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 167Williams Expires April 19, 2006 [Page 3] 168 169Internet-Draft GSS Domain Based Names October 2005 170 171 1722. Introduction 173 174 The use of hostbased principal names for domain-wide services 175 presents the problem of how to distinguish between an instance of a 176 hostbased service that is authorized to respond for a domain and one 177 that isn't. 178 179 Consider LDAP. LDAP [RFC3377] with SASL [RFC2222] and the Kerberos V 180 mechanism [RFC1964] for the GSS-API [RFC2743] uses a hostbased 181 principal with a service name of "ldap", a reasonable approach, 182 provided there is only one logical LDAP directory in a Kerberos 183 realm's domain, and that all ldap servers in that realm serve that 184 one LDAP directory. If there were other LDAP directories, then 185 clients could not tell which service is authorized to serve which 186 directory, not without assuming a secure method for finding LDAP 187 servers (e.g., DNSSEC). This is a significant, and oft-unstated 188 restriction on users of LDAP. 189 190 Domain based names can eliminate this problem by allowing LDAP 191 service names to indicate which LDAP directory they are authorized to 192 serve. 193 194 A domain-based name consists of three required elements: 195 196 o a service name 197 198 o a domain name 199 200 o a hostname 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223Williams Expires April 19, 2006 [Page 4] 224 225Internet-Draft GSS Domain Based Names October 2005 226 227 2283. Name Type OID and Symbolic Name 229 230 The new name type has an OID of 231 232 [NOTE: OID assignment to be made with IANA.] 233 234 {iso(1) org(3) dod(6) internet(1) security(5) nametypes(6) gss- 235 domain-based(5)} 236 237 The recommended symbolic name for this GSS-API name type is 238 "GSS_C_NT_DOMAINBASED_SERVICE". 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 279Williams Expires April 19, 2006 [Page 5] 280 281Internet-Draft GSS Domain Based Names October 2005 282 283 2844. Query and Display Syntaxes 285 286 There is a single name syntax for domain-based names. 287 288 The syntax is: 289 290 domain-based-name := 291 292 | <service> '@' <domain> '@' <hostname> 293 294 Note that for Internet domain names the trailing '.' is not and MUST 295 NOT be included in the domain name (or hostname) parts of the display 296 form GSS-API domain-based MNs. 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335Williams Expires April 19, 2006 [Page 6] 336 337Internet-Draft GSS Domain Based Names October 2005 338 339 3405. Examples 341 342 o ldap@example.tld@ds1.example.tld 343 344 o kadmin@example.tld@kdc1.example.tld 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 360 361 362 363 364 365 366 367 368 369 370 371 372 373 374 375 376 377 378 379 380 381 382 383 384 385 386 387 388 389 390 391Williams Expires April 19, 2006 [Page 7] 392 393Internet-Draft GSS Domain Based Names October 2005 394 395 3966. Security Considerations 397 398 Use of GSS-API domain-based names may not be negotiable by some GSS- 399 API mechanisms, and some acceptors may not support GSS-API domain- 400 based names. In such cases initiators are left to fallback on the 401 use of hostbased names, in which case the initiators MUST also verify 402 that the acceptor's hostbased name is authorized to provide the given 403 service for the domain that the initiator had wanted. 404 405 The above security consideration also applies to all GSS-API 406 initiators who lack support for domain-based service names. 407 408 409 410 411 412 413 414 415 416 417 418 419 420 421 422 423 424 425 426 427 428 429 430 431 432 433 434 435 436 437 438 439 440 441 442 443 444 445 446 447Williams Expires April 19, 2006 [Page 8] 448 449Internet-Draft GSS Domain Based Names October 2005 450 451 4527. References 453 4547.1. Normative 455 456 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 457 Requirement Levels", BCP 14, RFC 2119, March 1997. 458 459 [RFC2743] Linn, J., "Generic Security Service Application Program 460 Interface Version 2, Update 1", RFC 2743, January 2000. 461 4627.2. Informative 463 464 [RFC1964] Linn, J., "The Kerberos Version 5 GSS-API Mechanism", 465 RFC 1964, June 1996. 466 467 [RFC2222] Myers, J., "Simple Authentication and Security Layer 468 (SASL)", RFC 2222, October 1997. 469 470 [RFC3377] Hodges, J. and R. Morgan, "Lightweight Directory Access 471 Protocol (v3): Technical Specification", RFC 3377, 472 September 2002. 473 474 475 476 477 478 479 480 481 482 483 484 485 486 487 488 489 490 491 492 493 494 495 496 497 498 499 500 501 502 503Williams Expires April 19, 2006 [Page 9] 504 505Internet-Draft GSS Domain Based Names October 2005 506 507 508Author's Address 509 510 Nicolas Williams 511 Sun Microsystems 512 5300 Riata Trace Ct 513 Austin, TX 78727 514 US 515 516 Email: Nicolas.Williams@sun.com 517 518 519 520 521 522 523 524 525 526 527 528 529 530 531 532 533 534 535 536 537 538 539 540 541 542 543 544 545 546 547 548 549 550 551 552 553 554 555 556 557 558 559Williams Expires April 19, 2006 [Page 10] 560 561Internet-Draft GSS Domain Based Names October 2005 562 563 564Intellectual Property Statement 565 566 The IETF takes no position regarding the validity or scope of any 567 Intellectual Property Rights or other rights that might be claimed to 568 pertain to the implementation or use of the technology described in 569 this document or the extent to which any license under such rights 570 might or might not be available; nor does it represent that it has 571 made any independent effort to identify any such rights. Information 572 on the procedures with respect to rights in RFC documents can be 573 found in BCP 78 and BCP 79. 574 575 Copies of IPR disclosures made to the IETF Secretariat and any 576 assurances of licenses to be made available, or the result of an 577 attempt made to obtain a general license or permission for the use of 578 such proprietary rights by implementers or users of this 579 specification can be obtained from the IETF on-line IPR repository at 580 http://www.ietf.org/ipr. 581 582 The IETF invites any interested party to bring to its attention any 583 copyrights, patents or patent applications, or other proprietary 584 rights that may cover technology that may be required to implement 585 this standard. Please address the information to the IETF at 586 ietf-ipr@ietf.org. 587 588 589Disclaimer of Validity 590 591 This document and the information contained herein are provided on an 592 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS 593 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET 594 ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, 595 INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE 596 INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 597 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 598 599 600Copyright Statement 601 602 Copyright (C) The Internet Society (2005). This document is subject 603 to the rights, licenses and restrictions contained in BCP 78, and 604 except as set forth therein, the authors retain all their rights. 605 606 607Acknowledgment 608 609 Funding for the RFC Editor function is currently provided by the 610 Internet Society. 611 612 613 614 615Williams Expires April 19, 2006 [Page 11] 616 617 618