idnits 2.17.1 draft-ietf-kitten-extended-mech-inquiry-04.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, updated by RFC 4748 on line 559. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 570. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 577. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 583. 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 IETF Trust Copyright Line does not match the current year == Line 447 has weird spacing: '...OID_set desir...' == Line 448 has weird spacing: '...OID_set excep...' == Line 449 has weird spacing: '...OID_set criti...' -- 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 (March 21, 2008) is 5879 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) No issues found here. Summary: 1 error (**), 0 flaws (~~), 5 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: September 22, 2008 March 21, 2008 6 Extended Generic Security Service Mechanism Inquiry APIs 7 draft-ietf-kitten-extended-mech-inquiry-04.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 September 22, 2008. 34 Copyright Notice 36 Copyright (C) The IETF Trust (2008). 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 to reduce instances of hardcoding of mechanism identifiers in GSS 44 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. List of Known Mechanism Attributes . . . . . . . . . . . . 4 58 3.3. Mechanism Attribute Sets of Existing Mechs . . . . . . . . 6 59 3.4. New GSS-API Function Interfaces . . . . . . . . . . . . . 7 60 3.4.1. Mechanism Attribute Criticality . . . . . . . . . . . . . 8 61 3.4.2. GSS_Indicate_mechs_by_attr() . . . . . . . . . . . . . . . 8 62 3.4.3. GSS_Inquire_attrs_for_mech() . . . . . . . . . . . . . . . 9 63 3.4.4. GSS_Display_mech_attr() . . . . . . . . . . . . . . . . . 9 64 3.4.5. New Major Status Values . . . . . . . . . . . . . . . . . 10 65 3.4.6. 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 References . . . . . . . . . . . . . . . . . . . 12 71 7.2. Informative References . . . . . . . . . . . . . . . . . . 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 GSS-API [RFC2743] mechanisms have a number of properties that may be 84 of interest to applications. The lack of APIs for inquiring about 85 available mechanisms' properties has meant that many GSS-API 86 applications must hardcode mechanism OIDs. Ongoing work may result 87 in a variety of new GSS-API mechanisms. Applications should not have 88 to hardcode their OIDs. 90 For example, the SSHv2 protocol [RFC4251] supports the use of GSS-API 91 mechanisms for authentication [RFC4462], but it explicitly prohibits 92 the use of SPNEGO [RFC4178]. Future mechanisms that negotiate 93 mechanisms would have to be forbidden as well, but there is no way to 94 implement applications that inquire what mechanisms are available and 95 then programmatically exclude mechanisms "like SPNEGO". 97 3. New GSS-API Interfaces 99 We introduce a new concept: that of mechanism attributes. By 100 allowing applications to query the set of attributes associated with 101 individual mechanisms and to find out which mechanisms support a 102 given set of attributes we allow applications to select mechanisms 103 based on their attributes yet without having to hardcode mechanism 104 OIDs. 106 Section 3.1 describes the mechanism attributes concept. Sections 107 3.4.2, 3.4.3 and 3.4.4 describe three new interfaces that deal in 108 mechanisms and attribute sets: 110 o GSS_Indicate_mechs_by_attrs() 111 o GSS_Inquire_attrs_for_mech() 112 o GSS_Display_mech_attr() 114 3.1. Mechanism Attributes and Attribute Sets 116 An abstraction for the features provided by mechanisms and pseudo- 117 mechanisms is needed in order to facilitate the programmatic 118 selection of mechanisms. Pseudo-mechanisms are mechanisms which make 119 reference to other mechanisms in order to provide their services. 120 For example, SPNEGO is a pseudo-mechanism, for without other 121 mechanisms SPNEGO is useless. 123 Two data types are needed: one for individual mechanism attributes 124 and one for mechanism attribute sets. To simplify the mechanism 125 attributes interfaces we reuse the 'OID' and 'OID set' data types and 126 model individual mechanism attribute types as OIDs. 128 To this end we define an open namespace of mechanism attributes and 129 assign them arcs off of this OID: 131 [1.3.6.1.5.5.13 appears to be available; see 132 http://www.iana.org/assignments/smi-numbers] 134 Each mechanism has a set of mechanism attributes that it supports as 135 described in its specification. 137 3.2. List of Known Mechanism Attributes 139 +-------------------------+---------+-------------------------+ 140 | Mech Attr Name | OID Arc | Arc Name | 141 +-------------------------+---------+-------------------------+ 142 | GSS_C_MA_MECH_CONCRETE | (1) | concrete-mech | 143 | GSS_C_MA_MECH_PSEUDO | (2) | pseudo-mech | 144 | GSS_C_MA_MECH_COMPOSITE | (3) | composite-mech | 145 | GSS_C_MA_MECH_NEGO | (4) | mech-negotiation-mech | 146 | GSS_C_MA_MECH_GLUE | (5) | mech-glue | 147 | GSS_C_MA_NOT_MECH | (6) | not-mech | 148 | GSS_C_MA_DEPRECATED | (7) | mech-deprecated | 149 | GSS_C_MA_NOT_DFLT_MECH | (8) | mech-not-default | 150 | GSS_C_MA_ITOK_FRAMED | (9) | initial-is-framed | 151 | GSS_C_MA_AUTH_INIT | (10) | auth-init-princ | 152 | GSS_C_MA_AUTH_TARG | (11) | auth-targ-princ | 153 | GSS_C_MA_AUTH_INIT_INIT | (12) | auth-init-princ-initial | 154 | GSS_C_MA_AUTH_TARG_INIT | (13) | auth-targ-princ-initial | 155 | GSS_C_MA_AUTH_INIT_ANON | (14) | auth-init-princ-anon | 156 | GSS_C_MA_AUTH_TARG_ANON | (15) | auth-targ-princ-anon | 157 | GSS_C_MA_DELEG_CRED | (16) | deleg-cred | 158 | GSS_C_MA_INTEG_PROT | (17) | integ-prot | 159 | GSS_C_MA_CONF_PROT | (18) | conf-prot | 160 | GSS_C_MA_MIC | (19) | mic | 161 | GSS_C_MA_WRAP | (20) | wrap | 162 | GSS_C_MA_PROT_READY | (21) | prot-ready | 163 | GSS_C_MA_REPLAY_DET | (22) | replay-detection | 164 | GSS_C_MA_OOS_DET | (23) | oos-detection | 165 | GSS_C_MA_CBINDINGS | (24) | channel-bindings | 166 | GSS_C_MA_PFS | (25) | pfs | 167 | GSS_C_MA_COMPRESS | (26) | compress | 168 | GSS_C_MA_CTX_TRANS | (27) | context-transfer | 169 | | (28..) | | 170 +-------------------------+---------+-------------------------+ 172 Table 1 174 +-------------------------+-----------------------------------------+ 175 | Mech Attr Name | Purpose | 176 +-------------------------+-----------------------------------------+ 177 | GSS_C_MA_MECH_CONCRETE | Indicates that a mech is neither a | 178 | | pseudo- mechanism nor a composite | 179 | | mechanism. | 180 | GSS_C_MA_MECH_PSEUDO | Indicates that a mech is a | 181 | | pseudo-mechanism. | 182 | GSS_C_MA_MECH_COMPOSITE | Indicates that a mech is a composite of | 183 | | other mechanisms. This is reserved for | 184 | | a specification of "stackable" | 185 | | pseudo-mechanisms. | 186 | GSS_C_MA_MECH_NEGO | Indicates that a mech negotiates other | 187 | | mechs (e.g., SPNEGO has this | 188 | | attribute). | 189 | GSS_C_MA_MECH_GLUE | Indicates that the OID is not for a | 190 | | mechanism but for the GSS-API itself. | 191 | GSS_C_MA_NOT_MECH | Indicates that the OID is known, yet | 192 | | also known not to be the OID of any | 193 | | GSS-API mechanism (or the GSS-API | 194 | | itself). | 195 | GSS_C_MA_DEPRECATED | Indicates that a mech (or its OID) is | 196 | | deprecated and MUST NOT be used as a | 197 | | default mechanism. | 198 | GSS_C_MA_NOT_DFLT_MECH | Indicates that a mech (or its OID) MUST | 199 | | NOT be used as a default mechanism. | 200 | GSS_C_MA_ITOK_FRAMED | Indicates that the given mechanism's | 201 | | initial context tokens are properly | 202 | | framed as per-section 3.1 of rfc2743. | 203 | GSS_C_MA_AUTH_INIT | Indicates support for authentication of | 204 | | initiator to acceptor. | 205 | GSS_C_MA_AUTH_TARG | Indicates support for authentication of | 206 | | acceptor to initiator. | 207 | GSS_C_MA_AUTH_INIT_INIT | Indicates support for "initial" | 208 | | authentication of initiator to | 209 | | acceptor. "Initial authentication" | 210 | | refers to the use of passwords, or keys | 211 | | stored on tokens, for authentication. | 212 | | Whether a mechanism supports initial | 213 | | authentication may depend on IETF | 214 | | consensus (see Security | 215 | | Considerations). | 216 | GSS_C_MA_AUTH_TARG_INIT | Indicates support for initial | 217 | | authentication of acceptor to | 218 | | initiator. | 219 | GSS_C_MA_AUTH_INIT_ANON | Indicates support for | 220 | | GSS_C_NT_ANONYMOUS as an initiator | 221 | | principal name. | 222 | GSS_C_MA_AUTH_TARG_ANON | Indicates support for | 223 | | GSS_C_NT_ANONYMOUS as a target | 224 | | principal name. | 225 | GSS_C_MA_DELEG_CRED | Indicates support for credential | 226 | | delegation. | 227 | GSS_C_MA_INTEG_PROT | Indicates support for per-message | 228 | | integrity protection. | 229 | GSS_C_MA_CONF_PROT | Indicates support for per-message | 230 | | confidentiality protection. | 231 | GSS_C_MA_MIC | Indicates support for MIC tokens. | 232 | GSS_C_MA_WRAP | Indicates support for WRAP tokens. | 233 | GSS_C_MA_PROT_READY | Indicates support for per-message | 234 | | protection prior to full context | 235 | | establishment. | 236 | GSS_C_MA_REPLAY_DET | Indicates support for replay detection. | 237 | GSS_C_MA_OOS_DET | Indicates support for out-of-sequence | 238 | | detection. | 239 | GSS_C_MA_CBINDINGS | Indicates support for channel bindings. | 240 | GSS_C_MA_PFS | Indicates support for Perfect Forward | 241 | | Security. | 242 | GSS_C_MA_COMPRESS | Indicates support for compression of | 243 | | data inputs to GSS_Wrap(). | 244 | GSS_C_MA_CTX_TRANS | Indicates support for security context | 245 | | export/import. | 246 +-------------------------+-----------------------------------------+ 248 Table 2 250 3.3. Mechanism Attribute Sets of Existing Mechs 252 The Kerberos V mechanism [RFC1964] provides the following mechanism 253 attributes: 255 o GSS_C_MA_MECH_CONCRETE 256 o GSS_C_MA_ITOK_FRAMED 257 o GSS_C_MA_AUTH_INIT 258 o GSS_C_MA_AUTH_TARG 259 o GSS_C_MA_DELEG_CRED 260 o GSS_C_MA_INTEG_PROT 261 o GSS_C_MA_CONF_PROT 262 o GSS_C_MA_MIC 263 o GSS_C_MA_WRAP 264 o GSS_C_MA_PROT_READY 265 o GSS_C_MA_REPLAY_DET 266 o GSS_C_MA_OOS_DET 267 o GSS_C_MA_CBINDINGS 268 o GSS_C_MA_CTX_TRANS (some implementations, using implementation- 269 specific exported context token formats) 271 The Kerberos V mechanism also has a deprecated OID which has the same 272 mechanism attributes as above, and GSS_C_MA_DEPRECATED. 274 The mechanism attributes of the SPKM [RFC2025] family of mechanisms 275 will be provided in a separate document as SPKM is current being 276 reviewed for possibly significant changes due to problems in its 277 specifications. 279 The LIPKEY mechanism [RFC2847] offers the following attributes: 281 o GSS_C_MA_MECH_CONCRETE 282 o GSS_C_MA_ITOK_FRAMED 283 o GSS_C_MA_AUTH_INIT_INIT 284 o GSS_C_MA_AUTH_TARG (from SPKM-3) 285 o GSS_C_MA_AUTH_TARG_ANON (from SPKM-3) 286 o GSS_C_MA_INTEG_PROT 287 o GSS_C_MA_CONF_PROT 288 o GSS_C_MA_REPLAY_DET 289 o GSS_C_MA_OOS_DET 290 o GSS_C_MA_CTX_TRANS (some implementations, using implementation- 291 specific exported context token formats) 293 (LIPKEY should also provide GSS_C_MA_CBINDINGS, but SPKM-3 294 requires clarifications on this point.) 296 The SPNEGO mechanism [RFC4178] provides the following attributes: 297 o GSS_C_MA_MECH_NEGO 298 o GSS_C_MA_ITOK_FRAMED 300 All other mechanisms' attributes will be described elsewhere. 302 3.4. New GSS-API Function Interfaces 304 Several new interfaces are given by which, for example, GSS-API 305 applications may determine what features are provided by a given 306 mechanism and what mechanisms provide what features. 308 These new interfaces are all OPTIONAL. 310 Applications should use GSS_Indicate_mechs_by_attr() instead of 311 GSS_Indicate_mechs() wherever possible. 313 Applications can use GSS_Indicate_mechs_by_attr() to determine what, 314 if any, mechanisms provide a given set of features. 316 GSS_Indicate_mechs_by_attr() can also be used to indicate (as in 317 GSS_Indicate_mechs()) the set of available mechanisms of each type 318 (concrete, mechanism negotiation pseudo-mechanism, etc.). 320 3.4.1. Mechanism Attribute Criticality 322 Mechanism attributes may be added at any time. Not only may 323 attributes be added to the list of known mechanism attributes at any 324 time, but the set of mechanism attributes supported by a mechanism 325 can be changed at any time. 327 For example, new attributes might be added to reflect whether a 328 mechanism's initiator must contact online infrastructure, and/or 329 whether the acceptor must do so. In this example the Kerberos V 330 mechanism would gain a new attribute even though the mechanism itself 331 is not modified. 333 Applications making use of attributes not defined herein then would 334 have no way of knowing whether a GSS-API implementation and its 335 mechanisms know about new mechanism attributes. To address this 336 problem GSS_Indicate_mechs_by_attr() and GSS_Indicate_mechs_by_attr() 337 support a notion of critical mechanism attributes. Applications can 338 search for mechanisms that understand mechanism attributes that are 339 critical to the application, and the application may ask what 340 mechanism attributes are understood by a given mechanism. 342 3.4.2. GSS_Indicate_mechs_by_attr() 344 Inputs: 345 o desired_mech_attrs SET OF OBJECT IDENTIFIER -- set of GSS_C_MA_* 346 OIDs that the mechanisms indicated in the mechs output parameter 347 MUST offer 348 o except_mech_attrs SET OF OBJECT IDENTIFIER -- set of GSS_C_MA_* 349 OIDs that the mechanisms indicated in the mechs output parameter 350 MUST NOT offer 351 o critical_mech_attrs SET OF OBJECT IDENTIFIER -- set of GSS_C_MA_* 352 OIDs that the mechanisms indicated in the mechs output parameter 353 MUST understand (i.e., mechs must know whether critical attributes 354 are or are not supported) 356 Outputs: 357 o major_status INTEGER 358 o minor_status INTEGER 359 o mechs SET OF OBJECT IDENTIFIER -- set of mechanisms that support 360 the given desired_mech_attrs but not the except_mech_attrs, and 361 all of which understand the given critical_mech_attrs 363 Return major_status codes: 364 o GSS_S_COMPLETE indicates success; the output mechs parameter MAY 365 be the empty set (GSS_C_NO_OID_SET). 366 o GSS_S_FAILURE indicates that the request failed for some other 367 reason. 369 GSS_Indicate_mechs_by_attrs() returns the set of OIDs corresponding 370 to mechanisms that offer at least the desired_mech_attrs but none of 371 the except_mech_attrs, and which understand all of the attributes 372 listed in critical_mech_attrs. 374 When all three set of OID input parameters are the empty set this 375 function acts as a version of GSS_indicate_mechs() that outputs the 376 set of all supported mechanisms. 378 3.4.3. GSS_Inquire_attrs_for_mech() 380 Inputs: 381 o mech OBJECT IDENTIFIER -- mechanism OID 383 Outputs: 384 o major_status INTEGER 385 o minor_status INTEGER 386 o mech_attrs SET OF OBJECT IDENTIFIER -- set of mech_attrs OIDs 387 (GSS_C_MA_*) supported by the mechanism 388 o known_mech_attrs SET OF OBJECT IDENTIFIER -- set of mech_attrs 389 OIDs known to the mechanism implementation. 391 Return major_status codes: 392 o GSS_S_COMPLETE indicates success; the output mech_attrs parameter 393 MAY be the empty set (GSS_C_NO_OID_SET). 394 o GSS_S_BAD_MECH indicates that the mechanism named by the mech 395 parameter does not exist or that mech is GSS_C_NO_OID and no 396 default mechanism could be determined. 397 o GSS_S_FAILURE indicates that the request failed for some other 398 reason. 400 GSS_Inquire_mech_attrs_for_mech() indicates the set of mechanism 401 attributes supported by a given mechanism. 403 3.4.4. GSS_Display_mech_attr() 405 Inputs: 406 o mech_attr OBJECT IDENTIFIER -- mechanism attribute OID 408 Outputs: 410 o major_status INTEGER 411 o minor_status INTEGER 412 o name OCTET STRING, -- name of mechanism attribute (e.g., 413 GSS_C_MA_*) 414 o short_desc OCTET STRING, -- a short description of the mechanism 415 attribute 416 o long_desc OCTET STRING -- a longer description of the mechanism 417 attribute 419 Return major_status codes: 420 o GSS_S_COMPLETE indicates success. 421 o GSS_S_BAD_MECH_ATTR indicates that the mechanism attribute 422 referenced by the mech_attr parameter is unknown to the 423 implementation. 424 o GSS_S_FAILURE indicates that the request failed for some other 425 reason. 427 This function can be used to obtain human-readable descriptions of 428 GSS-API mechanism attributes. 430 3.4.5. New Major Status Values 432 A single new major status code is added for GSS_Display_mech_attr(): 433 o GSS_S_BAD_MECH_ATTR 434 roughly corresponding to GSS_S_BAD_MECH, but applicable to mechanism 435 attribute OIDs, rather than to mechanism OIDs. 437 For the C-bindings of the GSS-API [RFC2744] GSS_S_BAD_MECH_ATTR shall 438 have a routine error number of 19 (this is shifted to the left by 439 GSS_C_ROUTINE_ERROR_OFFSET). 441 3.4.6. C-Bindings 443 #define GSS_S_BAD_MECH_ATTR (19ul << GSS_C_ROUTINE_ERROR_OFFSET) 445 OM_uint32 gss_inquire_mechs_for_attrs( 446 OM_uint32 *minor_status, 447 const gss_OID_set desired_mech_attrs, 448 const gss_OID_set except_mech_attrs, 449 const gss_OID_set critical_mech_attrs, 450 gss_OID_set *mechs); 452 OM_uint32 gss_inquire_attrs_for_mech( 453 OM_uint32 *minor_status, 454 const gss_OID mech, 455 gss_OID_set *mech_attrs, 456 gss_OID_set *known_mech_attrs); 458 OM_uint32 gss_display_mech_attr( 459 OM_uint32 *minor_status, 460 const gss_OID mech_attr, 461 gss_buffer_t name, 462 gss_buffer_t short_desc, 463 gss_buffer_t long_desc); 465 Figure 1 467 4. Requirements for Mechanism Designers 469 All future GSS-API mechanism specifications MUST: 470 o list the set of GSS-API mechanism attributes associated with them 472 5. IANA Considerations 474 The namsepace of programming language symbols with names beginning 475 with GSS_C_MA_* is reserved for allocation by IESG Protocol Action. 476 The IANA should allocate a base OID, as an arc of 1.3.6.1.5.5, for 477 the set of GSS_C_MA_* described herein, and it should register all of 478 the GSS_C_MA_* values described in Section 3.2 480 6. Security considerations 482 This document specifies extensions to a security-related API. It 483 imposes new requirements on future GSS-API mechanisms, and the 484 specification of future protocols that use the GSS-API should make 485 reference to this document where applicable. The ability to inquire 486 about specific properties of mechanisms should improve security. 488 The semantics of each mechanism attribute may include a security 489 component. 491 Application developers must understand that mechanism attributes may 492 be added at any time, both, to the set of known mechanism attributes, 493 as well as to existing mechanism's sets of supported mechanism 494 attributes. Therefore application developers using the APIs 495 described herein must understand what mechanism attributes their 496 applications depend critically on, and must use the mechanism 497 attribute criticality features of these APIs. 499 7. References 500 7.1. Normative References 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. Informative References 513 [RFC1964] Linn, J., "The Kerberos Version 5 GSS-API Mechanism", 514 RFC 1964, June 1996. 516 [RFC2025] Adams, C., "The Simple Public-Key GSS-API Mechanism 517 (SPKM)", RFC 2025, October 1996. 519 [RFC2847] Eisler, M., "LIPKEY - A Low Infrastructure Public Key 520 Mechanism Using SPKM", RFC 2847, June 2000. 522 [RFC4178] Zhu, L., Leach, P., Jaganathan, K., and W. Ingersoll, "The 523 Simple and Protected Generic Security Service Application 524 Program Interface (GSS-API) Negotiation Mechanism", 525 RFC 4178, October 2005. 527 [RFC4251] Ylonen, T. and C. Lonvick, "The Secure Shell (SSH) 528 Protocol Architecture", RFC 4251, January 2006. 530 [RFC4462] Hutzelman, J., Salowey, J., Galbraith, J., and V. Welch, 531 "Generic Security Service Application Program Interface 532 (GSS-API) Authentication and Key Exchange for the Secure 533 Shell (SSH) Protocol", RFC 4462, May 2006. 535 Author's Address 537 Nicolas Williams 538 Sun Microsystems 539 5300 Riata Trace Ct 540 Austin, TX 78727 541 US 543 Email: Nicolas.Williams@sun.com 545 Full Copyright Statement 547 Copyright (C) The IETF Trust (2008). 549 This document is subject to the rights, licenses and restrictions 550 contained in BCP 78, and except as set forth therein, the authors 551 retain all their rights. 553 This document and the information contained herein are provided on an 554 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS 555 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND 556 THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS 557 OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF 558 THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 559 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 561 Intellectual Property 563 The IETF takes no position regarding the validity or scope of any 564 Intellectual Property Rights or other rights that might be claimed to 565 pertain to the implementation or use of the technology described in 566 this document or the extent to which any license under such rights 567 might or might not be available; nor does it represent that it has 568 made any independent effort to identify any such rights. Information 569 on the procedures with respect to rights in RFC documents can be 570 found in BCP 78 and BCP 79. 572 Copies of IPR disclosures made to the IETF Secretariat and any 573 assurances of licenses to be made available, or the result of an 574 attempt made to obtain a general license or permission for the use of 575 such proprietary rights by implementers or users of this 576 specification can be obtained from the IETF on-line IPR repository at 577 http://www.ietf.org/ipr. 579 The IETF invites any interested party to bring to its attention any 580 copyrights, patents or patent applications, or other proprietary 581 rights that may cover technology that may be required to implement 582 this standard. Please address the information to the IETF at 583 ietf-ipr@ietf.org. 585 Acknowledgment 587 Funding for the RFC Editor function is provided by the IETF 588 Administrative Support Activity (IASA).