idnits 2.17.1 draft-ietf-kitten-extended-mech-inquiry-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 14. -- Found old boilerplate from RFC 3978, Section 5.5 on line 561. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 538. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 545. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 551. ** 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 : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year == Line 458 has weird spacing: '...OID_set desir...' -- 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 6515 days in the past. Is this intentional? -- Found something which looks like a code comment -- if you have code sections in the document, please surround them with '' and '' lines. 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: 'CFX' is mentioned on line 263, but not defined == Missing Reference: 'SPNEGO' is mentioned on line 306, but not defined == Unused Reference: 'RFC2743' is defined on line 505, but no explicit reference was found in the text == Unused Reference: 'RFC2744' is defined on line 508, but no explicit reference was found in the text == Unused Reference: 'RFC2478' is defined on line 516, but no explicit reference was found in the text ** Obsolete normative reference: RFC 2478 (Obsoleted by RFC 4178) Summary: 4 errors (**), 0 flaws (~~), 8 warnings (==), 8 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 Extended Generic Security Service Mechanism Inquiry APIs 7 draft-ietf-kitten-extended-mech-inquiry-02.txt 9 Status of this Memo 11 By submitting this Internet-Draft, each author represents that any 12 applicable patent or other IPR claims of which he or she is aware 13 have been or will be disclosed, and any of which he or she becomes 14 aware will be disclosed, in accordance with Section 6 of BCP 79. 16 Internet-Drafts are working documents of the Internet Engineering 17 Task Force (IETF), its areas, and its working groups. Note that 18 other groups may also distribute working documents as Internet- 19 Drafts. 21 Internet-Drafts are draft documents valid for a maximum of six months 22 and may be updated, replaced, or obsoleted by other documents at any 23 time. It is inappropriate to use Internet-Drafts as reference 24 material or to cite them other than as "work in progress." 26 The list of current Internet-Drafts can be accessed at 27 http://www.ietf.org/ietf/1id-abstracts.txt. 29 The list of Internet-Draft Shadow Directories can be accessed at 30 http://www.ietf.org/shadow.html. 32 This Internet-Draft will expire on December 28, 2006. 34 Copyright Notice 36 Copyright (C) The Internet Society (2006). 38 Abstract 40 This document introduces new application programming interfaces 41 (APIs) to the Generic Security Services API (GSS-API) for extended 42 mechanism attribute inquiry. These interfaces are primarily intended 43 for use in mechanism composition, but also to reduce instances of 44 hardcoding of mechanism identifiers in GSS applications. 46 These interfaces include: mechanism attributes and attribute sets, a 47 function for inquiring the attributes of a mechanism, a function for 48 indicating mechanisms that posses given attributes, and a function 49 for displaying mechanism attributes. 51 Table of Contents 53 1. Conventions used in this document . . . . . . . . . . . . 3 54 2. Introduction . . . . . . . . . . . . . . . . . . . . . . . 3 55 3. New GSS-API Interfaces . . . . . . . . . . . . . . . . . . 3 56 3.1. Mechanism Attributes and Attribute Sets . . . . . . . . . 3 57 3.2. Determination of Attribute Sets of Composite Mechs . . . . 4 58 3.3. List of Known Mechanism Attributes . . . . . . . . . . . . 4 59 3.4. Mechanism Attribute Sets of Existing Mechs . . . . . . . . 6 60 3.5. New GSS-API Function Interfaces . . . . . . . . . . . . . 8 61 3.5.1. GSS_Indicate_mechs_by_attr() . . . . . . . . . . . . . . . 8 62 3.5.2. GSS_Inquire_attrs_for_mech() . . . . . . . . . . . . . . . 9 63 3.5.3. GSS_Display_mech_attr() . . . . . . . . . . . . . . . . . 10 64 3.5.4. New Major Status Values . . . . . . . . . . . . . . . . . 10 65 3.5.5. C-Bindings . . . . . . . . . . . . . . . . . . . . . . . . 10 66 4. Requirements for Mechanism Designers . . . . . . . . . . . 11 67 5. IANA Considerations . . . . . . . . . . . . . . . . . . . 11 68 6. Security considerations . . . . . . . . . . . . . . . . . 11 69 7. References . . . . . . . . . . . . . . . . . . . . . . . . 12 70 7.1. Normative . . . . . . . . . . . . . . . . . . . . . . . . 12 71 7.2. Normative . . . . . . . . . . . . . . . . . . . . . . . . 12 72 Author's Address . . . . . . . . . . . . . . . . . . . . . 13 73 Intellectual Property and Copyright Statements . . . . . . 14 75 1. Conventions used in this document 77 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 78 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 79 document are to be interpreted as described in [RFC2119]. 81 2. Introduction 83 3. New GSS-API Interfaces 85 GSS-API applications face, today, the problem of how to select from 86 multiple GSS-API mechanisms that may be available. For example, 87 applications that support mechanism negotiation directly often have 88 to be careful not to use SPNEGO to avoid two-layer mechanism 89 negotiation, but since SPNEGO may be indicated by 90 GSS_Indicate_mechs() and since there's no way to know that a 91 mechanism negotiates mechanisms other than to hardcode the OIDs of 92 such mechanisms, such applications must hardcode the SPNEGO OID. 93 This problem is likely to be exacerbated by the introduction of 94 composite mechanisms. 96 To address this problem we introduce a new concept: that of mechanism 97 attributes. By allowing applications to query the set of attributes 98 associated with individual mechanisms and to find out which 99 mechanisms support a given set of attributes we allow applications to 100 select mechanisms based on their attributes yet without having to 101 hardcode mechanism OIDs. 103 Section 3.1 describes the mechanism attributes concept. Sections 104 3.5.1, 3.5.2 and 3.5.3 describe three new interfaces that deal in 105 mechanisms and attribute sets: 107 o GSS_Indicate_mechs_by_attrs() 108 o GSS_Inquire_attrs_for_mech() 109 o GSS_Display_mech_attr() 111 3.1. Mechanism Attributes and Attribute Sets 113 An abstraction for the features provided by pseudo-mechanisms is 114 needed in order to facilitate the programmatic selection of 115 mechanisms as well as for the programmatic composition of mechanisms. 117 Two data types are needed: one for individual mechanism attributes 118 and one for mechanism attribute sets. To simplify the mechanism 119 attributes interfaces we reuse the 'OID' and 'OID set' data types and 120 model individual mechanism attribute types as OIDs. 122 To this end we define an open namespace of mechanism attributes and 123 assign them arcs off of this OID: 125 [1.3.6.1.5.5.12 appears to be available, registration w/ IANA 126 TBD] 128 3.2. Determination of Attribute Sets of Composite Mechs 130 Each mechanism, composite or otherwise, has a set of mechanism 131 attributes that it supports as specified. 133 The mechanism attribute set of a composite mechanism is to be 134 determined by the top-most stackable pseudo-mechanism of the 135 composite according to its own attribute set and that of the 136 remainder of the composite mechanism stack below it. 138 It may well be that some composite mechanisms' attribute sets consist 139 of the union of those of their every component, however this need not 140 be the case and MUST NOT be assumed. 142 Every stackable pseudo-mechanism's specification MUST specify the 143 rules for determining the mechanism attribute set of mechanisms 144 composed by it. 146 3.3. List of Known Mechanism Attributes 148 +-------------------------+--------+--------------------------------+ 149 | Mech Attr Name | OID | Arc Name | 150 | | Arc | | 151 +-------------------------+--------+--------------------------------+ 152 | GSS_C_MA_MECH_CONCRETE | (1) | concrete-mech | 153 | GSS_C_MA_MECH_STACKABLE | (2) | pseudo-mech | 154 | GSS_C_MA_MECH_COMPOSITE | (3) | composite-mech | 155 | GSS_C_MA_MECH_NEGO | (4) | mech-negotiation-mech | 156 | GSS_C_MA_MECH_GLUE | (5) | mech-glue | 157 | GSS_C_MA_NOT_MECH | (6) | not-mech | 158 | GSS_C_MA_DEPRECATED | (7) | mech-deprecated | 159 | GSS_C_MA_NOT_DFLT_MECH | (8) | mech-not-default | 160 | GSS_C_MA_ITOK_FRAMED | (9) | initial-is-framed | 161 | GSS_C_MA_AUTH_INIT | (10) | auth-init-princ | 162 | GSS_C_MA_AUTH_TARG | (11) | auth-targ-princ | 163 | GSS_C_MA_AUTH_INIT_INIT | (12) | auth-init-princ-initial | 164 | GSS_C_MA_AUTH_TARG_INIT | (13) | auth-targ-princ-initial | 165 | GSS_C_MA_AUTH_INIT_ANON | (14) | auth-init-princ-anon | 166 | GSS_C_MA_AUTH_TARG_ANON | (15) | auth-targ-princ-anon | 167 | GSS_C_MA_DELEG_CRED | (16) | deleg-cred | 168 | GSS_C_MA_INTEG_PROT | (17) | integ-prot | 169 | GSS_C_MA_CONF_PROT | (18) | conf-prot | 170 | GSS_C_MA_MIC | (19) | mic | 171 | GSS_C_MA_WRAP | (20) | wap | 172 | GSS_C_MA_PROT_READY | (21) | prot-ready | 173 | GSS_C_MA_REPLAY_DET | (22) | replay-detection | 174 | GSS_C_MA_OOS_DET | (23) | oos-detection | 175 | GSS_C_MA_CBINDINGS | (24) | channel-bindings | 176 | GSS_C_MA_CBINDINGS_BIDI | (25) | channel-bindings-bidirectional | 177 | GSS_C_MA_CBINDINGS_NEGO | (26) | channel-bindings-negotiate | 178 | GSS_C_MA_PFS | (27) | pfs | 179 | GSS_C_MA_COMPRESS | (28) | compress | 180 | GSS_C_MA_CTX_TRANS | (29) | context-transfer | 181 | | (30..) | | 182 +-------------------------+--------+--------------------------------+ 184 Table 1 186 +-------------------------+-----------------------------------------+ 187 | Mech Attr Name | Purpose | 188 +-------------------------+-----------------------------------------+ 189 | GSS_C_MA_MECH_CONCRETE | Indicates that a mech is neither a | 190 | | pseudo- mechanism nor a composite | 191 | | mechanism. | 192 | GSS_C_MA_MECH_STACKABLE | Indicates that a mech is a | 193 | | pseudo-mechanism. | 194 | GSS_C_MA_MECH_COMPOSITE | Indicates that a mech is a composite | 195 | | mechanism. | 196 | GSS_C_MA_MECH_NEGO | Indicates that a mech negotiates other | 197 | | mechs (e.g., SPNEGO has this | 198 | | attribute). | 199 | GSS_C_MA_MECH_GLUE | Indicates that the OID is not for a | 200 | | mechanism but for the GSS-API itself. | 201 | GSS_C_MA_NOT_MECH | Indicates that the OID is known, yet | 202 | | also known not to be the OID of any | 203 | | GSS-API mechanism (or the GSS-API | 204 | | itself). | 205 | GSS_C_MA_DEPRECATED | Indicates that a mech (or its OID) is | 206 | | deprecated and MUST NOT be used as a | 207 | | default mechanism. | 208 | GSS_C_MA_NOT_DFLT_MECH | Indicates that a mech (or its OID) MUST | 209 | | NOT be used as a default mechanism. | 210 | GSS_C_MA_ITOK_FRAMED | Indicates that the given mechanism's | 211 | | initial context tokens are properly | 212 | | framed as per-section 3.1 of rfc2743. | 213 | GSS_C_MA_AUTH_INIT | Indicates support for authentication of | 214 | | initiator to acceptor. | 215 | GSS_C_MA_AUTH_TARG | Indicates support for authentication of | 216 | | acceptor to initiator. | 217 | GSS_C_MA_AUTH_INIT_INIT | Indicates support for initial | 218 | | authentication of initiator to | 219 | | acceptor. | 220 | GSS_C_MA_AUTH_TARG_INIT | Indicates support for initial | 221 | | authentication of acceptor to | 222 | | initiator. | 223 | GSS_C_MA_AUTH_INIT_ANON | Indicates support for initiator | 224 | | anonymity. | 225 | GSS_C_MA_AUTH_TARG_ANON | Indicates support for acceptor | 226 | | anonymity. | 227 | GSS_C_MA_DELEG_CRED | Indicates support for credential | 228 | | delegation. | 229 | GSS_C_MA_INTEG_PROT | Indicates support for per-message | 230 | | integrity protection. | 231 | GSS_C_MA_CONF_PROT | Indicates support for per-message | 232 | | confidentiality protection. | 233 | GSS_C_MA_MIC | Indicates support for MIC tokens. | 234 | GSS_C_MA_WRAP | Indicates support for WRAP tokens. | 235 | GSS_C_MA_PROT_READY | Indicates support for per-message | 236 | | protection prior to full context | 237 | | establishment. | 238 | GSS_C_MA_REPLAY_DET | Indicates support for replay detection. | 239 | GSS_C_MA_OOS_DET | Indicates support for out-of-sequence | 240 | | detection. | 241 | GSS_C_MA_CBINDINGS | Indicates support for channel bindings. | 242 | GSS_C_MA_CBINDINGS_BIDI | Indicates that acceptors | 243 | | unconditionally indicate to initiators | 244 | | whether their channel bindings were | 245 | | matched the acceptors', even when the | 246 | | acceptor applications use | 247 | | GSS_C_NO_CHANNEL_BINDINGS.. | 248 | GSS_C_MA_CBINDINGS_NEGO | Indicates that the mech acts as a | 249 | | signal for application support for and | 250 | | willingness to use channel bindings. | 251 | GSS_C_MA_PFS | Indicates support for Perfect Forward | 252 | | Security. | 253 | GSS_C_MA_COMPRESS | Indicates support for compression of | 254 | | data inputs to GSS_Wrap(). | 255 | GSS_C_MA_CTX_TRANS | Indicates support for security context | 256 | | export/import. | 257 +-------------------------+-----------------------------------------+ 259 Table 2 261 3.4. Mechanism Attribute Sets of Existing Mechs 263 The Kerberos V mechanism [RFC1964] [CFX] provides the following 264 mechanism attributes: 266 o GSS_C_MA_MECH_CONCRETE 267 o GSS_C_MA_ITOK_FRAMED 268 o GSS_C_MA_AUTH_INIT 269 o GSS_C_MA_AUTH_TARG 270 o GSS_C_MA_DELEG_CRED 271 o GSS_C_MA_INTEG_PROT 272 o GSS_C_MA_CONF_PROT 273 o GSS_C_MA_MIC 274 o GSS_C_MA_WRAP 275 o GSS_C_MA_PROT_READY 276 o GSS_C_MA_REPLAY_DET 277 o GSS_C_MA_OOS_DET 278 o GSS_C_MA_CBINDINGS 279 o GSS_C_MA_CTX_TRANS (some implementations, using implementation- 280 specific exported context token formats) 282 The Kerberos V mechanism also has a deprecated OID which has the same 283 mechanism attributes as above, and GSS_C_MA_DEPRECATED. 285 [The mechanism attributes of the SPKM family of mechanisms will be 286 provided in a separate document as SPKM is current being reviewed for 287 possibly significant changes due to problems in its specifications.] 289 The LIPKEY mechanism offers the following attributes: 291 o GSS_C_MA_MECH_CONCRETE (should be stackable, but does not compose) 292 o GSS_C_MA_ITOK_FRAMED 293 o GSS_C_MA_AUTH_INIT_INIT 294 o GSS_C_MA_AUTH_TARG (from SPKM-3) 295 o GSS_C_MA_AUTH_TARG_ANON (from SPKM-3) 296 o GSS_C_MA_INTEG_PROT 297 o GSS_C_MA_CONF_PROT 298 o GSS_C_MA_REPLAY_DET 299 o GSS_C_MA_OOS_DET 300 o GSS_C_MA_CTX_TRANS (some implementations, using implementation- 301 specific exported context token formats) 303 (LIPKEY should also provide GSS_C_MA_CBINDINGS, but SPKM-3 304 requires clarifications on this point.) 306 The SPNEGO mechanism [SPNEGO] provides the following attributes: 307 o GSS_C_MA_MECH_NEGO 308 o GSS_C_MA_ITOK_FRAMED 310 The attributes of mechanisms negotiated by SPNEGO are not modified by 311 the use of SPNEGO. 313 All other mechanisms' attributes will be described elsewhere. 315 3.5. New GSS-API Function Interfaces 317 Several new interfaces are given by which, for example, GSS-API 318 applications may determine what features are provided by a given 319 mechanism, what mechanisms provide what features and what 320 compositions are legal. 322 These new interfaces are all OPTIONAL. 324 In order to preserve backwards compatibility with applications that 325 do not use the new interfaces GSS_Indicate_mechs() MUST NOT indicate 326 support for any stackable pseduo-mechanisms. GSS_Indicate_mechs() 327 MAY indicate support for some, all or none of the available composite 328 mechanisms; which composite mechanisms, if any, are indicated through 329 GSS_Indicate_mechs() SHOULD be configurable. GSS_Acquire_cred() and 330 GSS_Add_cred() MUST NOT create credentials for composite mechanisms 331 not explicitly requested or, if no desired mechanism or mechanisms 332 are given, for composite mechanisms not indicated by 333 GSS_Indicate_mechs(). 335 Applications SHOULD use GSS_Indicate_mechs_by_attr() instead of 336 GSS_Indicate_mechs() wherever possible. 338 Applications can use GSS_Indicate_mechs_by_attr() to determine what, 339 if any, mechanisms provide a given set of features. 341 GSS_Indicate_mechs_by_attr() can also be used to indicate (as in 342 GSS_Indicate_mechs()) the set of available mechanisms of each type 343 (concrete, mechanism negotiation pseudo-mechanism, stackable pseudo- 344 mechanism and composite mechanisms). 346 Applications may use GSS_Inquire_attrs_for_mech() to test whether a 347 given composite mechanism is available and the set of features that 348 it offers. 350 3.5.1. GSS_Indicate_mechs_by_attr() 352 Inputs: 353 o desired_mech_attrs SET OF OBJECT IDENTIFIER -- set of GSS_C_MA_* 354 OIDs that the mechanisms indicated in the mechs output parameter 355 MUST offer. 356 o except_mech_attrs SET OF OBJECT IDENTIFIER -- set of GSS_C_MA_* 357 OIDs that the mechanisms indicated in the mechs output parameter 358 MUST NOT offer. 360 Outputs: 361 o major_status INTEGER, 362 o minor_status INTEGER, 363 o mechs SET OF OBJECT IDENTIFIER -- set of mechanisms that support 364 -- the desired_mech_attrs but not the except_mech_attrs. 366 Return major_status codes: 367 o GSS_S_COMPLETE indicates success; the output mechs parameter MAY 368 be the empty set (GSS_C_NO_OID_SET). 369 o GSS_BAD_MECH_ATTR indicates that at least one mechanism attribute 370 OID in desired_mech_attrs or except_mech_attrs is unknown to the 371 implementation. 372 o GSS_S_FAILURE indicates that the request failed for some other 373 reason. 375 GSS_Indicate_mechs_by_mech_attrs() returns the set of mechanism OIDs 376 that offer at least the desired_mech_attrs but none of the 377 except_mech_attrs. 379 When desired_mech_attrs and except_mech_attrs are the empty set this 380 function acts as a version of GSS_indicate_mechs() that outputs the 381 set of all supported mechanisms of all types. By setting the 382 desired_mechs input parameter to a set of a single GSS_C_MA_MECH* 383 feature applications can obtain the list of all supported mechanisms 384 of a given type (concrete, stackable, etc...). 386 3.5.2. GSS_Inquire_attrs_for_mech() 388 Inputs: 389 o mech OBJECT IDENTIFIER -- mechanism OID 391 Outputs: 392 o major_status INTEGER, 393 o minor_status INTEGER, 394 o mech_attrs SET OF OBJECT IDENTIFIER -- set of mech_attrs OIDs 395 (GSS_C_MA_*) 397 Return major_status codes: 398 o GSS_S_COMPLETE indicates success; the output mech_attrs parameter 399 MAY be the empty set (GSS_C_NO_OID_SET). 400 o GSS_S_BAD_MECH indicates that the mechanism named by the mech 401 parameter does not exist or that mech is GSS_C_NO_OID and no 402 default mechanism could be determined. 403 o GSS_S_FAILURE indicates that the request failed for some other 404 reason. 406 GSS_Inquire_mech_attrs_for_mech() indicates the set of mechanism 407 attributes supported by a given mechanism. 409 Because the mechanism attribute sets of composite mechanisms need not 410 be the union of their components', when called to obtain the feature 411 set of a composite mechanism GSS_Inquire_mech_attrs_for_mech() 412 obtains it by querying the mechanism at the top of the stack. See 413 Section 3.1. 415 3.5.3. GSS_Display_mech_attr() 417 Inputs: 418 o mech_attr OBJECT IDENTIFIER -- mechanism attribute OID 420 Outputs: 421 o major_status INTEGER, 422 o minor_status INTEGER, 423 o name OCTET STRING, -- name of mechanism attribute (e.g., 424 GSS_C_MA_*) 425 o short_desc OCTET STRING, -- a short description of the mechanism 426 attribute 427 o long_desc OCTET STRING -- a longer description of the mechanism 428 attribute 430 Return major_status codes: 431 o GSS_S_COMPLETE indicates success. 432 o GSS_S_BAD_MECH_ATTR indicates that the mechanism attribute 433 referenced by the mech_attr parameter is unknown to the 434 implementation. 435 o GSS_S_FAILURE indicates that the request failed for some other 436 reason. 438 This function can be used to obtain human-readable descriptions of 439 GSS-API mechanism attributes. 441 3.5.4. New Major Status Values 443 A single new major status code is added for GSS_Display_mech_attr(): 444 o GSS_S_BAD_MECH_ATTR 445 roughly corresponding to GSS_S_BAD_MECH, but applicable to mechanism 446 attribute OIDs, rather than to mechanism OIDs. 448 For the C-bindings GSS_S_BAD_MECH_ATTR shall have a routine error 449 number of 19 (this is shifted to the left by 450 GSS_C_ROUTINE_ERROR_OFFSET). 452 3.5.5. C-Bindings 454 #define GSS_S_BAD_MECH_ATTR (19ul << GSS_C_ROUTINE_ERROR_OFFSET) 456 OM_uint32 gss_inquire_mechs_for_mech_attrs( 457 OM_uint32 *minor_status, 458 const gss_OID_set desired_mech_attrs, 459 gss_OID_set *mechs); 461 OM_uint32 gss_inquire_mech_attrs_for_mech( 462 OM_uint32 *minor_status, 463 const gss_OID mech, 464 gss_OID_set *mech_attrs); 466 OM_uint32 gss_display_mech_attr( 467 OM_uint32 *minor_status, 468 const gss_OID mech_attr, 469 gss_buffer_t name, 470 gss_buffer_t short_desc, 471 gss_buffer_t long_desc); 473 Figure 1 475 4. Requirements for Mechanism Designers 477 Stackable pseudo-mechanisms specifications MUST: 478 o list the set of GSS-API mechanism attributes associated with them 479 o list their initial mechanism composition rules 480 o specify a mechanism for updating their mechanism composition rules 482 All other mechanism specifications MUST: 483 o list the set of GSS-API mechanism attributes associated with them 485 5. IANA Considerations 487 The namsepace of programming language symbols with names beginning 488 with GSS_C_MA_* is reserved for allocation by the IANA. 490 Allocation of arcs in the namespace of OIDs relative to the base 491 mechanism attribute OID specified in Section 3.1 is reserved to the 492 IANA. 494 6. Security considerations 496 ... 498 7. References 500 7.1. Normative 502 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 503 Requirement Levels", BCP 14, RFC 2119, March 1997. 505 [RFC2743] Linn, J., "Generic Security Service Application Program 506 Interface Version 2, Update 1", RFC 2743, January 2000. 508 [RFC2744] Wray, J., "Generic Security Service API Version 2 : 509 C-bindings", RFC 2744, January 2000. 511 7.2. Normative 513 [RFC1964] Linn, J., "The Kerberos Version 5 GSS-API Mechanism", 514 RFC 1964, June 1996. 516 [RFC2478] Baize, E. and D. Pinkas, "The Simple and Protected GSS-API 517 Negotiation Mechanism", RFC 2478, December 1998. 519 Author's Address 521 Nicolas Williams 522 Sun Microsystems 523 5300 Riata Trace Ct 524 Austin, TX 78727 525 US 527 Email: Nicolas.Williams@sun.com 529 Intellectual Property Statement 531 The IETF takes no position regarding the validity or scope of any 532 Intellectual Property Rights or other rights that might be claimed to 533 pertain to the implementation or use of the technology described in 534 this document or the extent to which any license under such rights 535 might or might not be available; nor does it represent that it has 536 made any independent effort to identify any such rights. Information 537 on the procedures with respect to rights in RFC documents can be 538 found in BCP 78 and BCP 79. 540 Copies of IPR disclosures made to the IETF Secretariat and any 541 assurances of licenses to be made available, or the result of an 542 attempt made to obtain a general license or permission for the use of 543 such proprietary rights by implementers or users of this 544 specification can be obtained from the IETF on-line IPR repository at 545 http://www.ietf.org/ipr. 547 The IETF invites any interested party to bring to its attention any 548 copyrights, patents or patent applications, or other proprietary 549 rights that may cover technology that may be required to implement 550 this standard. Please address the information to the IETF at 551 ietf-ipr@ietf.org. 553 Disclaimer of Validity 555 This document and the information contained herein are provided on an 556 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS 557 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET 558 ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, 559 INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE 560 INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 561 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 563 Copyright Statement 565 Copyright (C) The Internet Society (2006). This document is subject 566 to the rights, licenses and restrictions contained in BCP 78, and 567 except as set forth therein, the authors retain all their rights. 569 Acknowledgment 571 Funding for the RFC Editor function is currently provided by the 572 Internet Society.