1 2 3 4NETWORK WORKING GROUP N. Williams 5Internet-Draft Sun 6Expires: April 19, 2006 October 16, 2005 7 8 9 Extended Generic Security Service Mechanism Inquiry APIs 10 draft-ietf-kitten-extended-mech-inquiry-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 introduces new application programming interfaces 44 (APIs) to the Generic Security Services API (GSS-API) for extended 45 mechanism attribute inquiry. These interfaces are primarily intended 46 for use in mechanism composition, but also to reduce instances of 47 hardcoding of mechanism identifiers in GSS applications. 48 49 These interfaces include: mechanism attributes and attribute sets, a 50 function for inquiring the attributes of a mechanism, a function for 51 indicating mechanisms that posses given attributes, and a function 52 53 54 55Williams Expires April 19, 2006 [Page 1] 56 57Internet-Draft Extended GSS Mech Inquiry October 2005 58 59 60 for displaying mechanism attributes. 61 62 63Table of Contents 64 65 1. Conventions used in this document . . . . . . . . . . . . 3 66 2. Introduction . . . . . . . . . . . . . . . . . . . . . . . 3 67 3. New GSS-API Interfaces . . . . . . . . . . . . . . . . . . 3 68 3.1. Mechanism Attributes and Attribute Sets . . . . . . . . . 3 69 3.2. Determination of Attribute Sets of Composite Mechs . . . . 4 70 3.3. List of Known Mechanism Attributes . . . . . . . . . . . . 4 71 3.4. Mechanism Attribute Sets of Existing Mechs . . . . . . . . 6 72 3.5. New GSS-API Function Interfaces . . . . . . . . . . . . . 8 73 3.5.1. GSS_Indicate_mechs_by_attr() . . . . . . . . . . . . . . . 8 74 3.5.2. GSS_Inquire_attrs_for_mech() . . . . . . . . . . . . . . . 9 75 3.5.3. GSS_Display_mech_attr() . . . . . . . . . . . . . . . . . 10 76 3.5.4. New Major Status Values . . . . . . . . . . . . . . . . . 10 77 3.5.5. C-Bindings . . . . . . . . . . . . . . . . . . . . . . . . 10 78 4. Requirements for Mechanism Designers . . . . . . . . . . . 11 79 5. IANA Considerations . . . . . . . . . . . . . . . . . . . 11 80 6. Security considerations . . . . . . . . . . . . . . . . . 11 81 7. References . . . . . . . . . . . . . . . . . . . . . . . . 12 82 7.1. Normative . . . . . . . . . . . . . . . . . . . . . . . . 12 83 7.2. Normative . . . . . . . . . . . . . . . . . . . . . . . . 12 84 Author's Address . . . . . . . . . . . . . . . . . . . . . 13 85 Intellectual Property and Copyright Statements . . . . . . 14 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 Extended GSS Mech Inquiry 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 1232. Introduction 124 125 1263. New GSS-API Interfaces 127 128 GSS-API applications face, today, the problem of how to select from 129 multiple GSS-API mechanisms that may be available. For example, 130 applications that support mechanism negotiation directly often have 131 to be careful not to use SPNEGO to avoid two-layer mechanism 132 negotiation, but since SPNEGO may be indicated by 133 GSS_Indicate_mechs() and since there's no way to know that a 134 mechanism negotiates mechanisms other than to hardcode the OIDs of 135 such mechanisms, such applications must hardcode the SPNEGO OID. 136 This problem is likely to be exacerbated by the introduction of 137 composite mechanisms. 138 139 To address this problem we introduce a new concept: that of mechanism 140 attributes. By allowing applications to query the set of attributes 141 associated with individual mechanisms and to find out which 142 mechanisms support a given set of attributes we allow applications to 143 select mechanisms based on their attributes yet without having to 144 hardcode mechanism OIDs. 145 146 Section 3.1 describes the mechanism attributes concept. Sections 147 3.5.1, 3.5.2 and 3.5.3 describe three new interfaces that deal in 148 mechanisms and attribute sets: 149 150 o GSS_Indicate_mechs_by_attrs() 151 o GSS_Inquire_attrs_for_mech() 152 o GSS_Display_mech_attr() 153 1543.1. Mechanism Attributes and Attribute Sets 155 156 An abstraction for the features provided by pseudo-mechanisms is 157 needed in order to facilitate the programmatic selection of 158 mechanisms as well as for the programmatic composition of mechanisms. 159 160 Two data types are needed: one for individual mechanism attributes 161 and one for mechanism attribute sets. To simplify the mechanism 162 attributes interfaces we reuse the 'OID' and 'OID set' data types and 163 model individual mechanism attribute types as OIDs. 164 165 166 167Williams Expires April 19, 2006 [Page 3] 168 169Internet-Draft Extended GSS Mech Inquiry October 2005 170 171 172 To this end we define an open namespace of mechanism attributes and 173 assign them arcs off of this OID: 174 175 <TBD> [1.3.6.1.5.5.12 appears to be available, registration w/ IANA 176 TBD] 177 1783.2. Determination of Attribute Sets of Composite Mechs 179 180 Each mechanism, composite or otherwise, has a set of mechanism 181 attributes that it supports as specified. 182 183 The mechanism attribute set of a composite mechanism is to be 184 determined by the top-most stackable pseudo-mechanism of the 185 composite according to its own attribute set and that of the 186 remainder of the composite mechanism stack below it. 187 188 It may well be that some composite mechanisms' attribute sets consist 189 of the union of those of their every component, however this need not 190 be the case and MUST NOT be assumed. 191 192 Every stackable pseudo-mechanism's specification MUST specify the 193 rules for determining the mechanism attribute set of mechanisms 194 composed by it. 195 1963.3. List of Known Mechanism Attributes 197 198 +-------------------------+--------+--------------------------------+ 199 | Mech Attr Name | OID | Arc Name | 200 | | Arc | | 201 +-------------------------+--------+--------------------------------+ 202 | GSS_C_MA_MECH_CONCRETE | (1) | concrete-mech | 203 | GSS_C_MA_MECH_STACKABLE | (2) | pseudo-mech | 204 | GSS_C_MA_MECH_COMPOSITE | (3) | composite-mech | 205 | GSS_C_MA_MECH_NEGO | (4) | mech-negotiation-mech | 206 | GSS_C_MA_MECH_GLUE | (5) | mech-glue | 207 | GSS_C_MA_NOT_MECH | (6) | not-mech | 208 | GSS_C_MA_DEPRECATED | (7) | mech-deprecated | 209 | GSS_C_MA_NOT_DFLT_MECH | (8) | mech-not-default | 210 | GSS_C_MA_ITOK_FRAMED | (9) | initial-is-framed | 211 | GSS_C_MA_AUTH_INIT | (10) | auth-init-princ | 212 | GSS_C_MA_AUTH_TARG | (11) | auth-targ-princ | 213 | GSS_C_MA_AUTH_INIT_INIT | (12) | auth-init-princ-initial | 214 | GSS_C_MA_AUTH_TARG_INIT | (13) | auth-targ-princ-initial | 215 | GSS_C_MA_AUTH_INIT_ANON | (14) | auth-init-princ-anon | 216 | GSS_C_MA_AUTH_TARG_ANON | (15) | auth-targ-princ-anon | 217 | GSS_C_MA_DELEG_CRED | (16) | deleg-cred | 218 | GSS_C_MA_INTEG_PROT | (17) | integ-prot | 219 | GSS_C_MA_CONF_PROT | (18) | conf-prot | 220 221 222 223Williams Expires April 19, 2006 [Page 4] 224 225Internet-Draft Extended GSS Mech Inquiry October 2005 226 227 228 | GSS_C_MA_MIC | (19) | mic | 229 | GSS_C_MA_WRAP | (20) | wap | 230 | GSS_C_MA_PROT_READY | (21) | prot-ready | 231 | GSS_C_MA_REPLAY_DET | (22) | replay-detection | 232 | GSS_C_MA_OOS_DET | (23) | oos-detection | 233 | GSS_C_MA_CBINDINGS | (24) | channel-bindings | 234 | GSS_C_MA_CBINDINGS_BIDI | (25) | channel-bindings-bidirectional | 235 | GSS_C_MA_CBINDINGS_NEGO | (26) | channel-bindings-negotiate | 236 | GSS_C_MA_PFS | (27) | pfs | 237 | GSS_C_MA_COMPRESS | (28) | compress | 238 | GSS_C_MA_CTX_TRANS | (29) | context-transfer | 239 | <reserved> | (30..) | | 240 +-------------------------+--------+--------------------------------+ 241 242 Table 1 243 244 +-------------------------+-----------------------------------------+ 245 | Mech Attr Name | Purpose | 246 +-------------------------+-----------------------------------------+ 247 | GSS_C_MA_MECH_CONCRETE | Indicates that a mech is neither a | 248 | | pseudo- mechanism nor a composite | 249 | | mechanism. | 250 | GSS_C_MA_MECH_STACKABLE | Indicates that a mech is a | 251 | | pseudo-mechanism. | 252 | GSS_C_MA_MECH_COMPOSITE | Indicates that a mech is a composite | 253 | | mechanism. | 254 | GSS_C_MA_MECH_NEGO | Indicates that a mech negotiates other | 255 | | mechs (e.g., SPNEGO has this | 256 | | attribute). | 257 | GSS_C_MA_MECH_GLUE | Indicates that the OID is not for a | 258 | | mechanism but for the GSS-API itself. | 259 | GSS_C_MA_NOT_MECH | Indicates that the OID is known, yet | 260 | | also known not to be the OID of any | 261 | | GSS-API mechanism (or the GSS-API | 262 | | itself). | 263 | GSS_C_MA_DEPRECATED | Indicates that a mech (or its OID) is | 264 | | deprecated and MUST NOT be used as a | 265 | | default mechanism. | 266 | GSS_C_MA_NOT_DFLT_MECH | Indicates that a mech (or its OID) MUST | 267 | | NOT be used as a default mechanism. | 268 | GSS_C_MA_ITOK_FRAMED | Indicates that the given mechanism's | 269 | | initial context tokens are properly | 270 | | framed as per-section 3.1 of rfc2743. | 271 | GSS_C_MA_AUTH_INIT | Indicates support for authentication of | 272 | | initiator to acceptor. | 273 | GSS_C_MA_AUTH_TARG | Indicates support for authentication of | 274 | | acceptor to initiator. | 275 | GSS_C_MA_AUTH_INIT_INIT | Indicates support for initial | 276 277 278 279Williams Expires April 19, 2006 [Page 5] 280 281Internet-Draft Extended GSS Mech Inquiry October 2005 282 283 284 | | authentication of initiator to | 285 | | acceptor. | 286 | GSS_C_MA_AUTH_TARG_INIT | Indicates support for initial | 287 | | authentication of acceptor to | 288 | | initiator. | 289 | GSS_C_MA_AUTH_INIT_ANON | Indicates support for initiator | 290 | | anonymity. | 291 | GSS_C_MA_AUTH_TARG_ANON | Indicates support for acceptor | 292 | | anonymity. | 293 | GSS_C_MA_DELEG_CRED | Indicates support for credential | 294 | | delegation. | 295 | GSS_C_MA_INTEG_PROT | Indicates support for per-message | 296 | | integrity protection. | 297 | GSS_C_MA_CONF_PROT | Indicates support for per-message | 298 | | confidentiality protection. | 299 | GSS_C_MA_MIC | Indicates support for MIC tokens. | 300 | GSS_C_MA_WRAP | Indicates support for WRAP tokens. | 301 | GSS_C_MA_PROT_READY | Indicates support for per-message | 302 | | protection prior to full context | 303 | | establishment. | 304 | GSS_C_MA_REPLAY_DET | Indicates support for replay detection. | 305 | GSS_C_MA_OOS_DET | Indicates support for out-of-sequence | 306 | | detection. | 307 | GSS_C_MA_CBINDINGS | Indicates support for channel bindings. | 308 | GSS_C_MA_CBINDINGS_BIDI | Indicates that acceptors | 309 | | unconditionally indicate to initiators | 310 | | whether their channel bindings were | 311 | | matched the acceptors', even when the | 312 | | acceptor applications use | 313 | | GSS_C_NO_CHANNEL_BINDINGS.. | 314 | GSS_C_MA_CBINDINGS_NEGO | Indicates that the mech acts as a | 315 | | signal for application support for and | 316 | | willingness to use channel bindings. | 317 | GSS_C_MA_PFS | Indicates support for Perfect Forward | 318 | | Security. | 319 | GSS_C_MA_COMPRESS | Indicates support for compression of | 320 | | data inputs to GSS_Wrap(). | 321 | GSS_C_MA_CTX_TRANS | Indicates support for security context | 322 | | export/import. | 323 +-------------------------+-----------------------------------------+ 324 325 Table 2 326 3273.4. Mechanism Attribute Sets of Existing Mechs 328 329 The Kerberos V mechanism [RFC1964] [CFX] provides the following 330 mechanism attributes: 331 332 333 334 335Williams Expires April 19, 2006 [Page 6] 336 337Internet-Draft Extended GSS Mech Inquiry October 2005 338 339 340 o GSS_C_MA_MECH_CONCRETE 341 o GSS_C_MA_ITOK_FRAMED 342 o GSS_C_MA_AUTH_INIT 343 o GSS_C_MA_AUTH_TARG 344 o GSS_C_MA_DELEG_CRED 345 o GSS_C_MA_INTEG_PROT 346 o GSS_C_MA_CONF_PROT 347 o GSS_C_MA_MIC 348 o GSS_C_MA_WRAP 349 o GSS_C_MA_PROT_READY 350 o GSS_C_MA_REPLAY_DET 351 o GSS_C_MA_OOS_DET 352 o GSS_C_MA_CBINDINGS 353 o GSS_C_MA_CTX_TRANS (some implementations, using implementation- 354 specific exported context token formats) 355 356 The Kerberos V mechanism also has a deprecated OID which has the same 357 mechanism attributes as above, and GSS_C_MA_DEPRECATED. 358 359 [The mechanism attributes of the SPKM family of mechanisms will be 360 provided in a separate document as SPKM is current being reviewed for 361 possibly significant changes due to problems in its specifications.] 362 363 The LIPKEY mechanism offers the following attributes: 364 365 o GSS_C_MA_MECH_CONCRETE (should be stackable, but does not compose) 366 o GSS_C_MA_ITOK_FRAMED 367 o GSS_C_MA_AUTH_INIT_INIT 368 o GSS_C_MA_AUTH_TARG (from SPKM-3) 369 o GSS_C_MA_AUTH_TARG_ANON (from SPKM-3) 370 o GSS_C_MA_INTEG_PROT 371 o GSS_C_MA_CONF_PROT 372 o GSS_C_MA_REPLAY_DET 373 o GSS_C_MA_OOS_DET 374 o GSS_C_MA_CTX_TRANS (some implementations, using implementation- 375 specific exported context token formats) 376 377 (LIPKEY should also provide GSS_C_MA_CBINDINGS, but SPKM-3 378 requires clarifications on this point.) 379 380 The SPNEGO mechanism [SPNEGO] provides the following attributes: 381 o GSS_C_MA_MECH_NEGO 382 o GSS_C_MA_ITOK_FRAMED 383 384 The attributes of mechanisms negotiated by SPNEGO are not modified by 385 the use of SPNEGO. 386 387 All other mechanisms' attributes will be described elsewhere. 388 389 390 391Williams Expires April 19, 2006 [Page 7] 392 393Internet-Draft Extended GSS Mech Inquiry October 2005 394 395 3963.5. New GSS-API Function Interfaces 397 398 Several new interfaces are given by which, for example, GSS-API 399 applications may determine what features are provided by a given 400 mechanism, what mechanisms provide what features and what 401 compositions are legal. 402 403 These new interfaces are all OPTIONAL. 404 405 In order to preserve backwards compatibility with applications that 406 do not use the new interfaces GSS_Indicate_mechs() MUST NOT indicate 407 support for any stackable pseduo-mechanisms. GSS_Indicate_mechs() 408 MAY indicate support for some, all or none of the available composite 409 mechanisms; which composite mechanisms, if any, are indicated through 410 GSS_Indicate_mechs() SHOULD be configurable. GSS_Acquire_cred() and 411 GSS_Add_cred() MUST NOT create credentials for composite mechanisms 412 not explicitly requested or, if no desired mechanism or mechanisms 413 are given, for composite mechanisms not indicated by 414 GSS_Indicate_mechs(). 415 416 Applications SHOULD use GSS_Indicate_mechs_by_attr() instead of 417 GSS_Indicate_mechs() wherever possible. 418 419 Applications can use GSS_Indicate_mechs_by_attr() to determine what, 420 if any, mechanisms provide a given set of features. 421 422 GSS_Indicate_mechs_by_attr() can also be used to indicate (as in 423 GSS_Indicate_mechs()) the set of available mechanisms of each type 424 (concrete, mechanism negotiation pseudo-mechanism, stackable pseudo- 425 mechanism and composite mechanisms). 426 427 Applications may use GSS_Inquire_attrs_for_mech() to test whether a 428 given composite mechanism is available and the set of features that 429 it offers. 430 4313.5.1. GSS_Indicate_mechs_by_attr() 432 433 Inputs: 434 o desired_mech_attrs SET OF OBJECT IDENTIFIER -- set of GSS_C_MA_* 435 OIDs that the mechanisms indicated in the mechs output parameter 436 MUST offer. 437 o except_mech_attrs SET OF OBJECT IDENTIFIER -- set of GSS_C_MA_* 438 OIDs that the mechanisms indicated in the mechs output parameter 439 MUST NOT offer. 440 441 Outputs: 442 o major_status INTEGER, 443 o minor_status INTEGER, 444 445 446 447Williams Expires April 19, 2006 [Page 8] 448 449Internet-Draft Extended GSS Mech Inquiry October 2005 450 451 452 o mechs SET OF OBJECT IDENTIFIER -- set of mechanisms that support 453 -- the desired_mech_attrs but not the except_mech_attrs. 454 455 Return major_status codes: 456 o GSS_S_COMPLETE indicates success; the output mechs parameter MAY 457 be the empty set (GSS_C_NO_OID_SET). 458 o GSS_BAD_MECH_ATTR indicates that at least one mechanism attribute 459 OID in desired_mech_attrs or except_mech_attrs is unknown to the 460 implementation. 461 o GSS_S_FAILURE indicates that the request failed for some other 462 reason. 463 464 GSS_Indicate_mechs_by_mech_attrs() returns the set of mechanism OIDs 465 that offer at least the desired_mech_attrs but none of the 466 except_mech_attrs. 467 468 When desired_mech_attrs and except_mech_attrs are the empty set this 469 function acts as a version of GSS_indicate_mechs() that outputs the 470 set of all supported mechanisms of all types. By setting the 471 desired_mechs input parameter to a set of a single GSS_C_MA_MECH* 472 feature applications can obtain the list of all supported mechanisms 473 of a given type (concrete, stackable, etc...). 474 4753.5.2. GSS_Inquire_attrs_for_mech() 476 477 Inputs: 478 o mech OBJECT IDENTIFIER -- mechanism OID 479 480 Outputs: 481 o major_status INTEGER, 482 o minor_status INTEGER, 483 o mech_attrs SET OF OBJECT IDENTIFIER -- set of mech_attrs OIDs 484 (GSS_C_MA_*) 485 486 Return major_status codes: 487 o GSS_S_COMPLETE indicates success; the output mech_attrs parameter 488 MAY be the empty set (GSS_C_NO_OID_SET). 489 o GSS_S_BAD_MECH indicates that the mechanism named by the mech 490 parameter does not exist or that mech is GSS_C_NO_OID and no 491 default mechanism could be determined. 492 o GSS_S_FAILURE indicates that the request failed for some other 493 reason. 494 495 GSS_Inquire_mech_attrs_for_mech() indicates the set of mechanism 496 attributes supported by a given mechanism. 497 498 Because the mechanism attribute sets of composite mechanisms need not 499 be the union of their components', when called to obtain the feature 500 501 502 503Williams Expires April 19, 2006 [Page 9] 504 505Internet-Draft Extended GSS Mech Inquiry October 2005 506 507 508 set of a composite mechanism GSS_Inquire_mech_attrs_for_mech() 509 obtains it by querying the mechanism at the top of the stack. See 510 Section 3.1. 511 5123.5.3. GSS_Display_mech_attr() 513 514 Inputs: 515 o mech_attr OBJECT IDENTIFIER -- mechanism attribute OID 516 517 Outputs: 518 o major_status INTEGER, 519 o minor_status INTEGER, 520 o name OCTET STRING, -- name of mechanism attribute (e.g., 521 GSS_C_MA_*) 522 o short_desc OCTET STRING, -- a short description of the mechanism 523 attribute 524 o long_desc OCTET STRING -- a longer description of the mechanism 525 attribute 526 527 Return major_status codes: 528 o GSS_S_COMPLETE indicates success. 529 o GSS_S_BAD_MECH_ATTR indicates that the mechanism attribute 530 referenced by the mech_attr parameter is unknown to the 531 implementation. 532 o GSS_S_FAILURE indicates that the request failed for some other 533 reason. 534 535 This function can be used to obtain human-readable descriptions of 536 GSS-API mechanism attributes. 537 5383.5.4. New Major Status Values 539 540 A single new major status code is added for GSS_Display_mech_attr(): 541 o GSS_S_BAD_MECH_ATTR 542 roughly corresponding to GSS_S_BAD_MECH, but applicable to mechanism 543 attribute OIDs, rather than to mechanism OIDs. 544 545 For the C-bindings GSS_S_BAD_MECH_ATTR shall have a routine error 546 number of 19 (this is shifted to the left by 547 GSS_C_ROUTINE_ERROR_OFFSET). 548 5493.5.5. C-Bindings 550 551 552 #define GSS_S_BAD_MECH_ATTR (19ul << GSS_C_ROUTINE_ERROR_OFFSET) 553 554 OM_uint32 gss_inquire_mechs_for_mech_attrs( 555 OM_uint32 *minor_status, 556 557 558 559Williams Expires April 19, 2006 [Page 10] 560 561Internet-Draft Extended GSS Mech Inquiry October 2005 562 563 564 const gss_OID_set desired_mech_attrs, 565 gss_OID_set *mechs); 566 567 OM_uint32 gss_inquire_mech_attrs_for_mech( 568 OM_uint32 *minor_status, 569 const gss_OID mech, 570 gss_OID_set *mech_attrs); 571 572 OM_uint32 gss_display_mech_attr( 573 OM_uint32 *minor_status, 574 const gss_OID mech_attr, 575 gss_buffer_t name, 576 gss_buffer_t short_desc, 577 gss_buffer_t long_desc); 578 579 580 Figure 1 581 582 5834. Requirements for Mechanism Designers 584 585 Stackable pseudo-mechanisms specifications MUST: 586 o list the set of GSS-API mechanism attributes associated with them 587 o list their initial mechanism composition rules 588 o specify a mechanism for updating their mechanism composition rules 589 590 All other mechanism specifications MUST: 591 o list the set of GSS-API mechanism attributes associated with them 592 593 5945. IANA Considerations 595 596 The namsepace of programming language symbols with names beginning 597 with GSS_C_MA_* is reserved for allocation by the IANA. 598 599 Allocation of arcs in the namespace of OIDs relative to the base 600 mechanism attribute OID specified in Section 3.1 is reserved to the 601 IANA. 602 603 6046. Security considerations 605 606 ... 607 608 6097. References 610 6117.1. Normative 612 613 614 615Williams Expires April 19, 2006 [Page 11] 616 617Internet-Draft Extended GSS Mech Inquiry October 2005 618 619 620 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 621 Requirement Levels", BCP 14, RFC 2119, March 1997. 622 623 [RFC2743] Linn, J., "Generic Security Service Application Program 624 Interface Version 2, Update 1", RFC 2743, January 2000. 625 626 [RFC2744] Wray, J., "Generic Security Service API Version 2 : 627 C-bindings", RFC 2744, January 2000. 628 6297.2. Normative 630 631 [RFC1964] Linn, J., "The Kerberos Version 5 GSS-API Mechanism", 632 RFC 1964, June 1996. 633 634 [RFC2478] Baize, E. and D. Pinkas, "The Simple and Protected GSS-API 635 Negotiation Mechanism", RFC 2478, December 1998. 636 637 638 639 640 641 642 643 644 645 646 647 648 649 650 651 652 653 654 655 656 657 658 659 660 661 662 663 664 665 666 667 668 669 670 671Williams Expires April 19, 2006 [Page 12] 672 673Internet-Draft Extended GSS Mech Inquiry October 2005 674 675 676Author's Address 677 678 Nicolas Williams 679 Sun Microsystems 680 5300 Riata Trace Ct 681 Austin, TX 78727 682 US 683 684 Email: Nicolas.Williams@sun.com 685 686 687 688 689 690 691 692 693 694 695 696 697 698 699 700 701 702 703 704 705 706 707 708 709 710 711 712 713 714 715 716 717 718 719 720 721 722 723 724 725 726 727Williams Expires April 19, 2006 [Page 13] 728 729Internet-Draft Extended GSS Mech Inquiry October 2005 730 731 732Intellectual Property Statement 733 734 The IETF takes no position regarding the validity or scope of any 735 Intellectual Property Rights or other rights that might be claimed to 736 pertain to the implementation or use of the technology described in 737 this document or the extent to which any license under such rights 738 might or might not be available; nor does it represent that it has 739 made any independent effort to identify any such rights. Information 740 on the procedures with respect to rights in RFC documents can be 741 found in BCP 78 and BCP 79. 742 743 Copies of IPR disclosures made to the IETF Secretariat and any 744 assurances of licenses to be made available, or the result of an 745 attempt made to obtain a general license or permission for the use of 746 such proprietary rights by implementers or users of this 747 specification can be obtained from the IETF on-line IPR repository at 748 http://www.ietf.org/ipr. 749 750 The IETF invites any interested party to bring to its attention any 751 copyrights, patents or patent applications, or other proprietary 752 rights that may cover technology that may be required to implement 753 this standard. Please address the information to the IETF at 754 ietf-ipr@ietf.org. 755 756 757Disclaimer of Validity 758 759 This document and the information contained herein are provided on an 760 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS 761 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET 762 ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, 763 INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE 764 INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 765 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 766 767 768Copyright Statement 769 770 Copyright (C) The Internet Society (2005). This document is subject 771 to the rights, licenses and restrictions contained in BCP 78, and 772 except as set forth therein, the authors retain all their rights. 773 774 775Acknowledgment 776 777 Funding for the RFC Editor function is currently provided by the 778 Internet Society. 779 780 781 782 783Williams Expires April 19, 2006 [Page 14] 784 785 786