idnits 2.17.1 draft-ietf-kitten-extended-mech-inquiry-00.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 3667, Section 5.1 on line 14. -- Found old boilerplate from RFC 3978, Section 5.5 on line 574. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 551. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 558. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 564. ** Found boilerplate matching RFC 3978, Section 5.4, paragraph 1 (on line 580), which is fine, but *also* found old RFC 2026, Section 10.4C, paragraph 1 text on line 36. ** The document seems to lack an RFC 3978 Section 5.1 IPR Disclosure Acknowledgement -- however, there's a paragraph with a matching beginning. Boilerplate error? ** 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. ** The document uses RFC 3667 boilerplate or RFC 3978-like boilerplate instead of verbatim RFC 3978 boilerplate. After 6 May 2005, submission of drafts without verbatim RFC 3978 boilerplate is not accepted. The following non-3978 patterns matched text found in the document. That text should be removed or replaced: By submitting this Internet-Draft, I certify that any applicable patent or other IPR claims of which I am aware have been disclosed, or will be disclosed, and any of which I become aware will be disclosed, in accordance with RFC 3668. 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 471 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 (February 11, 2005) is 7013 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 277, but not defined == Missing Reference: 'SPNEGO' is mentioned on line 320, but not defined == Unused Reference: 'RFC2743' is defined on line 518, but no explicit reference was found in the text == Unused Reference: 'RFC2744' is defined on line 521, but no explicit reference was found in the text == Unused Reference: 'RFC2478' is defined on line 529, but no explicit reference was found in the text ** Obsolete normative reference: RFC 2478 (Obsoleted by RFC 4178) Summary: 7 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: August 12, 2005 February 11, 2005 6 Extended Generic Security Service Mechanism Inquiry APIs 7 draft-ietf-kitten-extended-mech-inquiry-00.txt 9 Status of this Memo 11 By submitting this Internet-Draft, I certify that any applicable 12 patent or other IPR claims of which I am aware have been disclosed, 13 and any of which I become aware will be disclosed, in accordance with 14 RFC 3668. 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 19 Internet-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 August 12, 2005. 34 Copyright Notice 36 Copyright (C) The Internet Society (2005). All Rights Reserved. 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 . . . . . . . . . 7 60 3.5 New GSS-API Function Interfaces . . . . . . . . . . . . . . 8 61 3.5.1 GSS_Indicate_mechs_by_attr() . . . . . . . . . . . . . . . . 9 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 . . . . . . . . . . . . . . . . . . . . . . . . . 11 66 4. Requirements for Mechanism Designers . . . . . . . . . . . . 11 67 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . 11 68 6. Security considerations . . . . . . . . . . . . . . . . . . 12 69 7. References . . . . . . . . . . . . . . . . . . . . . . . . . 12 70 7.1 Normative . . . . . . . . . . . . . . . . . . . . . . . . . 12 71 7.2 Normative . . . . . . . . . . . . . . . . . . . . . . . . . 12 72 Author's Address . . . . . . . . . . . . . . . . . . . . . . 12 73 Intellectual Property and Copyright Statements . . . . . . . 13 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 | Arc Name | 150 +-------------------------+---------+--------------------------------+ 151 | GSS_C_MA_MECH_CONCRETE | (1) | concrete-mech | 152 | GSS_C_MA_MECH_STACKABLE | (2) | pseudo-mech | 153 | GSS_C_MA_MECH_COMPOSITE | (3) | composite-mech | 154 | GSS_C_MA_MECH_NEGO | (4) | mech-negotiation-mech | 155 | GSS_C_MA_MECH_GLUE | (5) | mech-glue | 156 | GSS_C_MA_NOT_MECH | (6) | not-mech | 157 | GSS_C_MA_DEPRECATED | (7) | mech-deprecated | 158 | GSS_C_MA_NOT_DFLT_MECH | (8) | mech-not-default | 159 | GSS_C_MA_ITOK_FRAMED | (9) | initial-is-framed | 160 | GSS_C_MA_AUTH_INIT | (10) | auth-init-princ | 161 | GSS_C_MA_AUTH_TARG | (11) | auth-targ-princ | 162 | GSS_C_MA_AUTH_INIT_INIT | (12) | auth-init-princ-initial | 163 | GSS_C_MA_AUTH_TARG_INIT | (13) | auth-targ-princ-initial | 164 | GSS_C_MA_AUTH_INIT_ANON | (14) | auth-init-princ-anon | 165 | GSS_C_MA_AUTH_TARG_ANON | (15) | auth-targ-princ-anon | 166 | GSS_C_MA_DELEG_CRED | (16) | deleg-cred | 167 | GSS_C_MA_INTEG_PROT | (17) | integ-prot | 168 | GSS_C_MA_CONF_PROT | (18) | conf-prot | 169 | GSS_C_MA_MIC | (19) | mic | 170 | GSS_C_MA_WRAP | (20) | wap | 171 | GSS_C_MA_PROT_READY | (21) | prot-ready | 172 | GSS_C_MA_REPLAY_DET | (22) | replay-detection | 173 | GSS_C_MA_OOS_DET | (23) | oos-detection | 174 | GSS_C_MA_CBINDINGS | (24) | channel-bindings | 175 | GSS_C_MA_CBINDINGS_BIDI | (25) | channel-bindings-bidirectional | 176 | GSS_C_MA_CBINDINGS_NEGO | (26) | channel-bindings-negotiate | 177 | GSS_C_MA_PFS | (27) | pfs | 178 | GSS_C_MA_COMPRESS | (28) | compress | 179 | GSS_C_MA_CTX_TRANS | (29) | context-transfer | 180 | | (30..) | | 181 +-------------------------+---------+--------------------------------+ 183 Table 1 185 +---------------------------------+---------------------------------+ 186 | Mech Attr Name | Purpose | 187 +---------------------------------+---------------------------------+ 188 | GSS_C_MA_MECH_CONCRETE | Indicates that a mech is | 189 | | neither a pseudo- mechanism nor | 190 | | a composite mechanism. | 191 | GSS_C_MA_MECH_STACKABLE | Indicates that a mech is a | 192 | | pseudo-mechanism. | 193 | GSS_C_MA_MECH_COMPOSITE | Indicates that a mech is a | 194 | | composite mechanism. | 195 | GSS_C_MA_MECH_NEGO | Indicates that a mech | 196 | | negotiates other mechs (e.g., | 197 | | SPNEGO has this attribute). | 198 | GSS_C_MA_MECH_GLUE | Indicates that the OID is not | 199 | | for a mechanism but for the | 200 | | GSS-API itself. | 201 | GSS_C_MA_NOT_MECH | Indicates that the OID is | 202 | | known, yet also known not to be | 203 | | the OID of any GSS-API | 204 | | mechanism (or the GSS-API | 205 | | itself). | 206 | GSS_C_MA_DEPRECATED | Indicates that a mech (or its | 207 | | OID) is deprecated and MUST NOT | 208 | | be used as a default mechanism. | 209 | GSS_C_MA_NOT_DFLT_MECH | Indicates that a mech (or its | 210 | | OID) MUST NOT be used as a | 211 | | default mechanism. | 212 | GSS_C_MA_ITOK_FRAMED | Indicates that the given | 213 | | mechanism's initial context | 214 | | tokens are properly framed as | 215 | | per-section 3.1 of rfc2743. | 216 | GSS_C_MA_AUTH_INIT | Indicates support for | 217 | | authentication of initiator to | 218 | | acceptor. | 219 | GSS_C_MA_AUTH_TARG | Indicates support for | 220 | | authentication of acceptor to | 221 | | initiator. | 222 | GSS_C_MA_AUTH_INIT_INIT | Indicates support for initial | 223 | | authentication of initiator to | 224 | | acceptor. | 225 | GSS_C_MA_AUTH_TARG_INIT | Indicates support for initial | 226 | | authentication of acceptor to | 227 | | initiator. | 228 | GSS_C_MA_AUTH_INIT_ANON | Indicates support for initiator | 229 | | anonymity. | 230 | GSS_C_MA_AUTH_TARG_ANON | Indicates support for acceptor | 231 | | anonymity. | 232 | GSS_C_MA_DELEG_CRED | Indicates support for | 233 | | credential delegation. | 234 | GSS_C_MA_INTEG_PROT | Indicates support for | 235 | | per-message integrity | 236 | | protection. | 237 | GSS_C_MA_CONF_PROT | Indicates support for | 238 | | per-message confidentiality | 239 | | protection. | 240 | GSS_C_MA_MIC | Indicates support for MIC | 241 | | tokens. | 242 | GSS_C_MA_WRAP | Indicates support for WRAP | 243 | | tokens. | 244 | GSS_C_MA_PROT_READY | Indicates support for | 245 | | per-message protection prior to | 246 | | full context establishment. | 247 | GSS_C_MA_REPLAY_DET | Indicates support for replay | 248 | | detection. | 249 | GSS_C_MA_OOS_DET | Indicates support for | 250 | | out-of-sequence detection. | 251 | GSS_C_MA_CBINDINGS | Indicates support for channel | 252 | | bindings. | 253 | GSS_C_MA_CBINDINGS_BIDI | Indicates that acceptors | 254 | | unconditionally indicate to | 255 | | initiators whether their | 256 | | channel bindings were matched | 257 | | the acceptors', even when the | 258 | | acceptor applications use | 259 | | GSS_C_NO_CHANNEL_BINDINGS.. | 260 | GSS_C_MA_CBINDINGS_NEGO | Indicates that the mech acts as | 261 | | a signal for application | 262 | | support for and willingness to | 263 | | use channel bindings. | 264 | GSS_C_MA_PFS | Indicates support for Perfect | 265 | | Forward Security. | 266 | GSS_C_MA_COMPRESS | Indicates support for | 267 | | compression of data inputs to | 268 | | GSS_Wrap(). | 269 | GSS_C_MA_CTX_TRANS | Indicates support for security | 270 | | context export/import. | 271 +---------------------------------+---------------------------------+ 273 Table 2 275 3.4 Mechanism Attribute Sets of Existing Mechs 277 The Kerberos V mechanism [RFC1964] [CFX] provides the following 278 mechanism attributes: 280 o GSS_C_MA_MECH_CONCRETE 281 o GSS_C_MA_ITOK_FRAMED 282 o GSS_C_MA_AUTH_INIT 283 o GSS_C_MA_AUTH_TARG 284 o GSS_C_MA_DELEG_CRED 285 o GSS_C_MA_INTEG_PROT 286 o GSS_C_MA_CONF_PROT 287 o GSS_C_MA_MIC 288 o GSS_C_MA_WRAP 289 o GSS_C_MA_PROT_READY 290 o GSS_C_MA_REPLAY_DET 291 o GSS_C_MA_OOS_DET 292 o GSS_C_MA_CBINDINGS 293 o GSS_C_MA_CTX_TRANS (some implementations, using 294 implementation-specific exported context token formats) 296 The Kerberos V mechanism also has a deprecated OID which has the same 297 mechanism attributes as above, and GSS_C_MA_DEPRECATED. 299 [The mechanism attributes of the SPKM family of mechanisms will be 300 provided in a separate document as SPKM is current being reviewed for 301 possibly significant changes due to problems in its specifications.] 303 The LIPKEY mechanism offers the following attributes: 305 o GSS_C_MA_MECH_CONCRETE (should be stackable, but does not compose) 306 o GSS_C_MA_ITOK_FRAMED 307 o GSS_C_MA_AUTH_INIT_INIT 308 o GSS_C_MA_AUTH_TARG (from SPKM-3) 309 o GSS_C_MA_AUTH_TARG_ANON (from SPKM-3) 310 o GSS_C_MA_INTEG_PROT 311 o GSS_C_MA_CONF_PROT 312 o GSS_C_MA_REPLAY_DET 313 o GSS_C_MA_OOS_DET 314 o GSS_C_MA_CTX_TRANS (some implementations, using 315 implementation-specific exported context token formats) 317 (LIPKEY should also provide GSS_C_MA_CBINDINGS, but SPKM-3 318 requires clarifications on this point.) 320 The SPNEGO mechanism [SPNEGO] provides the following attributes: 321 o GSS_C_MA_MECH_NEGO 322 o GSS_C_MA_ITOK_FRAMED 324 The attributes of mechanisms negotiated by SPNEGO are not modified by 325 the use of SPNEGO. 327 All other mechanisms' attributes will be described elsewhere. 329 3.5 New GSS-API Function Interfaces 331 Several new interfaces are given by which, for example, GSS-API 332 applications may determine what features are provided by a given 333 mechanism, what mechanisms provide what features and what 334 compositions are legal. 336 These new interfaces are all OPTIONAL. 338 In order to preserve backwards compatibility with applications that 339 do not use the new interfaces GSS_Indicate_mechs() MUST NOT indicate 340 support for any stackable pseduo-mechanisms. GSS_Indicate_mechs() 341 MAY indicate support for some, all or none of the available composite 342 mechanisms; which composite mechanisms, if any, are indicated through 343 GSS_Indicate_mechs() SHOULD be configurable. GSS_Acquire_cred() and 344 GSS_Add_cred() MUST NOT create credentials for composite mechanisms 345 not explicitly requested or, if no desired mechanism or mechanisms 346 are given, for composite mechanisms not indicated by 347 GSS_Indicate_mechs(). 349 Applications SHOULD use GSS_Indicate_mechs_by_attr() instead of 350 GSS_Indicate_mechs() wherever possible. 352 Applications can use GSS_Indicate_mechs_by_attr() to determine what, 353 if any, mechanisms provide a given set of features. 355 GSS_Indicate_mechs_by_attr() can also be used to indicate (as in 356 GSS_Indicate_mechs()) the set of available mechanisms of each type 357 (concrete, mechanism negotiation pseudo-mechanism, stackable 358 pseudo-mechanism and composite mechanisms). 360 Applications may use GSS_Inquire_attrs_for_mech() to test whether a 361 given composite mechanism is available and the set of features that 362 it offers. 364 3.5.1 GSS_Indicate_mechs_by_attr() 366 Inputs: 367 o desired_mech_attrs SET OF OBJECT IDENTIFIER -- set of GSS_C_MA_* 368 OIDs that the mechanisms indicated in the mechs output parameter 369 MUST offer. 370 o except_mech_attrs SET OF OBJECT IDENTIFIER -- set of GSS_C_MA_* 371 OIDs that the mechanisms indicated in the mechs output parameter 372 MUST NOT offer. 374 Outputs: 375 o major_status INTEGER, 376 o minor_status INTEGER, 377 o mechs SET OF OBJECT IDENTIFIER -- set of mechanisms that support 378 -- the desired_mech_attrs but not the except_mech_attrs. 380 Return major_status codes: 381 o GSS_S_COMPLETE indicates success; the output mechs parameter MAY 382 be the empty set (GSS_C_NO_OID_SET). 383 o GSS_BAD_MECH_ATTR indicates that at least one mechanism attribute 384 OID in desired_mech_attrs or except_mech_attrs is unknown to the 385 implementation. 386 o GSS_S_FAILURE indicates that the request failed for some other 387 reason. 389 GSS_Indicate_mechs_by_mech_attrs() returns the set of mechanism OIDs 390 that offer at least the desired_mech_attrs but none of the 391 except_mech_attrs. 393 When desired_mech_attrs and except_mech_attrs are the empty set this 394 function acts as a version of GSS_indicate_mechs() that outputs the 395 set of all supported mechanisms of all types. By setting the 396 desired_mechs input parameter to a set of a single GSS_C_MA_MECH* 397 feature applications can obtain the list of all supported mechanisms 398 of a given type (concrete, stackable, etc...). 400 3.5.2 GSS_Inquire_attrs_for_mech() 402 Inputs: 403 o mech OBJECT IDENTIFIER -- mechanism OID 405 Outputs: 406 o major_status INTEGER, 407 o minor_status INTEGER, 408 o mech_attrs SET OF OBJECT IDENTIFIER -- set of mech_attrs OIDs 409 (GSS_C_MA_*) 411 Return major_status codes: 412 o GSS_S_COMPLETE indicates success; the output mech_attrs parameter 413 MAY be the empty set (GSS_C_NO_OID_SET). 414 o GSS_S_BAD_MECH indicates that the mechanism named by the mech 415 parameter does not exist or that mech is GSS_C_NO_OID and no 416 default mechanism could be determined. 417 o GSS_S_FAILURE indicates that the request failed for some other 418 reason. 420 GSS_Inquire_mech_attrs_for_mech() indicates the set of mechanism 421 attributes supported by a given mechanism. 423 Because the mechanism attribute sets of composite mechanisms need not 424 be the union of their components', when called to obtain the feature 425 set of a composite mechanism GSS_Inquire_mech_attrs_for_mech() 426 obtains it by querying the mechanism at the top of the stack. See 427 Section 3.1. 429 3.5.3 GSS_Display_mech_attr() 431 Inputs: 432 o mech_attr OBJECT IDENTIFIER -- mechanism attribute OID 434 Outputs: 435 o major_status INTEGER, 436 o minor_status INTEGER, 437 o name OCTET STRING, -- name of mechanism attribute (e.g., 438 GSS_C_MA_*) 439 o short_desc OCTET STRING, -- a short description of the mechanism 440 attribute 441 o long_desc OCTET STRING -- a longer description of the mechanism 442 attribute 444 Return major_status codes: 445 o GSS_S_COMPLETE indicates success. 446 o GSS_S_BAD_MECH_ATTR indicates that the mechanism attribute 447 referenced by the mech_attr parameter is unknown to the 448 implementation. 449 o GSS_S_FAILURE indicates that the request failed for some other 450 reason. 452 This function can be used to obtain human-readable descriptions of 453 GSS-API mechanism attributes. 455 3.5.4 New Major Status Values 456 A single new major status code is added for GSS_Display_mech_attr(): 457 o GSS_S_BAD_MECH_ATTR 458 roughly corresponding to GSS_S_BAD_MECH, but applicable to mechanism 459 attribute OIDs, rather than to mechanism OIDs. 461 For the C-bindings GSS_S_BAD_MECH_ATTR shall have a routine error 462 number of 19 (this is shifted to the left by 463 GSS_C_ROUTINE_ERROR_OFFSET). 465 3.5.5 C-Bindings 467 #define GSS_S_BAD_MECH_ATTR (19ul << GSS_C_ROUTINE_ERROR_OFFSET) 469 OM_uint32 gss_inquire_mechs_for_mech_attrs( 470 OM_uint32 *minor_status, 471 const gss_OID_set desired_mech_attrs, 472 gss_OID_set *mechs); 474 OM_uint32 gss_inquire_mech_attrs_for_mech( 475 OM_uint32 *minor_status, 476 const gss_OID mech, 477 gss_OID_set *mech_attrs); 479 OM_uint32 gss_display_mech_attr( 480 OM_uint32 *minor_status, 481 const gss_OID mech_attr, 482 gss_buffer_t name, 483 gss_buffer_t short_desc, 484 gss_buffer_t long_desc); 486 Figure 1 488 4. Requirements for Mechanism Designers 490 Stackable pseudo-mechanisms specifications MUST: 491 o list the set of GSS-API mechanism attributes associated with them 492 o list their initial mechanism composition rules 493 o specify a mechanism for updating their mechanism composition rules 495 All other mechanism specifications MUST: 496 o list the set of GSS-API mechanism attributes associated with them 498 5. IANA Considerations 500 The namsepace of programming language symbols with names beginning 501 with GSS_C_MA_* is reserved for allocation by the IANA. 503 Allocation of arcs in the namespace of OIDs relative to the base 504 mechanism attribute OID specified in Section 3.1 is reserved to the 505 IANA. 507 6. Security considerations 509 ... 511 7. References 513 7.1 Normative 515 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 516 Requirement Levels", BCP 14, RFC 2119, March 1997. 518 [RFC2743] Linn, J., "Generic Security Service Application Program 519 Interface Version 2, Update 1", RFC 2743, January 2000. 521 [RFC2744] Wray, J., "Generic Security Service API Version 2 : 522 C-bindings", RFC 2744, January 2000. 524 7.2 Normative 526 [RFC1964] Linn, J., "The Kerberos Version 5 GSS-API Mechanism", RFC 527 1964, June 1996. 529 [RFC2478] Baize, E. and D. Pinkas, "The Simple and Protected GSS-API 530 Negotiation Mechanism", RFC 2478, December 1998. 532 Author's Address 534 Nicolas Williams 535 Sun Microsystems 536 5300 Riata Trace Ct 537 Austin, TX 78727 538 US 540 EMail: Nicolas.Williams@sun.com 542 Intellectual Property Statement 544 The IETF takes no position regarding the validity or scope of any 545 Intellectual Property Rights or other rights that might be claimed to 546 pertain to the implementation or use of the technology described in 547 this document or the extent to which any license under such rights 548 might or might not be available; nor does it represent that it has 549 made any independent effort to identify any such rights. Information 550 on the procedures with respect to rights in RFC documents can be 551 found in BCP 78 and BCP 79. 553 Copies of IPR disclosures made to the IETF Secretariat and any 554 assurances of licenses to be made available, or the result of an 555 attempt made to obtain a general license or permission for the use of 556 such proprietary rights by implementers or users of this 557 specification can be obtained from the IETF on-line IPR repository at 558 http://www.ietf.org/ipr. 560 The IETF invites any interested party to bring to its attention any 561 copyrights, patents or patent applications, or other proprietary 562 rights that may cover technology that may be required to implement 563 this standard. Please address the information to the IETF at 564 ietf-ipr@ietf.org. 566 Disclaimer of Validity 568 This document and the information contained herein are provided on an 569 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS 570 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET 571 ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, 572 INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE 573 INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 574 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 576 Copyright Statement 578 Copyright (C) The Internet Society (2005). This document is subject 579 to the rights, licenses and restrictions contained in BCP 78, and 580 except as set forth therein, the authors retain all their rights. 582 Acknowledgment 584 Funding for the RFC Editor function is currently provided by the 585 Internet Society.