1 2NETWORK WORKING GROUP N. Williams 3Internet-Draft Sun 4Expires: July 2, 2005 January 2005 5 6 7 Namespace Considerations and Registries for GSS-API Extensions 8 draft-ietf-kitten-gssapi-extensions-iana-00.txt 9 10Status of this Memo 11 12 By submitting this Internet-Draft, I certify that any applicable 13 patent or other IPR claims of which I am aware have been disclosed, 14 and any of which I become aware will be disclosed, in accordance with 15 RFC 3668. 16 17 Internet-Drafts are working documents of the Internet Engineering 18 Task Force (IETF), its areas, and its working groups. Note that 19 other groups may also distribute working documents as 20 Internet-Drafts. 21 22 Internet-Drafts are draft documents valid for a maximum of six months 23 and may be updated, replaced, or obsoleted by other documents at any 24 time. It is inappropriate to use Internet-Drafts as reference 25 material or to cite them other than as "work in progress." 26 27 The list of current Internet-Drafts can be accessed at 28 http://www.ietf.org/ietf/1id-abstracts.txt. 29 30 The list of Internet-Draft Shadow Directories can be accessed at 31 http://www.ietf.org/shadow.html. 32 33 This Internet-Draft will expire on July 2, 2005. 34 35Copyright Notice 36 37 Copyright (C) The Internet Society (2005). All Rights Reserved. 38 39Abstract 40 41 This document describes the ways in which the GSS-API may be extended 42 and directs the creation of IANA registries for various GSS-API 43 namespaces. 44 45 46 47 48 49 50 51 52 53 54Williams Expires July 2, 2005 [Page 1] 55 56Internet-Draft GSS IANA Instructions January 2005 57 58 59Table of Contents 60 61 1. Conventions used in this document . . . . . . . . . . . . . . 3 62 2. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 63 3. Extensions to the GSS-API . . . . . . . . . . . . . . . . . . 3 64 4. Generic GSS-API Namespaces . . . . . . . . . . . . . . . . . . 3 65 5. Language Binding-Specific GSS-API Namespaces . . . . . . . . . 4 66 6. Extension-Specific GSS-API Namespaces . . . . . . . . . . . . 4 67 7. Registration Form(s) . . . . . . . . . . . . . . . . . . . . . 4 68 8. Initial Namespace Registrations . . . . . . . . . . . . . . . 6 69 9. Security Considerations . . . . . . . . . . . . . . . . . . . 6 70 10. Normative . . . . . . . . . . . . . . . . . . . . . . . . . . 6 71 Author's Address . . . . . . . . . . . . . . . . . . . . . . . 6 72 Intellectual Property and Copyright Statements . . . . . . . . 7 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110Williams Expires July 2, 2005 [Page 2] 111 112Internet-Draft GSS IANA Instructions January 2005 113 114 1151. Conventions used in this document 116 117 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 118 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 119 document are to be interpreted as described in [RFC2119]. 120 1212. Introduction 122 123 There is a need for generic and mechanism-specific extensions to the 124 Generic Security Services Application Programming Interface 125 (GSS-API). As such extensions are designed and standardized, both at 126 the IETF and elsewhere, there is a non-trivial risk of namespace 127 pollution and conflicts. To avoid this we set out guidelines for 128 extending the GSS-API and create IANA registries of GSS-API 129 namespaces. 130 131 The registration of name prefixes and constant value ranges is 132 allowed so as to save the IANA the trouble of registering every 133 GSS-API name and constant, and to allow for reservation of portions 134 of some GSS namespaces for private extensions or extensions which 135 lack IETF Standards-Track extensions. 136 1373. Extensions to the GSS-API 138 139 Extensions to the GSS-API can be categorized as follows: 140 o Generic 141 o Implementation-specific 142 o Mechanism-specific 143 o Language binding-specific 144 o Any combination of two or all three of the last three 145 146 Extensions to the GSS-API may be purely semantic, without effect on 147 the GSS-API's namespaces. Or they may introduce new functions, 148 constants, types, etc...; these clearly affect the GSS-API 149 namespaces. 150 151 Extensions that affect the GSS-API namespaces should be registered 152 with the IANA. 153 1544. Generic GSS-API Namespaces 155 156 All the function, constant and type names, as well as all the 157 constant values specified in the base GSS-API specification for the 158 basic generic GSS-API namespace. 159 160 The generic GSS-API namespaces are: 161 o Type names 162 o Function names 163 164 165 166Williams Expires July 2, 2005 [Page 3] 167 168Internet-Draft GSS IANA Instructions January 2005 169 170 171 o Constant names for each type 172 o Constant values for each type 173 o Mechanism OIDs 174 o Name Type OIDs 175 o Mechanism Attribute OIDs (see [EXTENDED-INQUIRY]) 176 1775. Language Binding-Specific GSS-API Namespaces 178 179 <Add text; discuss header, module, library, class, method namespaces 180 and whatever else comes up that is language-specific and appropriate 181 for registration with the IANA.> 182 1836. Extension-Specific GSS-API Namespaces 184 185 Extensions to the GSS-API may create additional namespaces. 186 Instructions to the IANA should included for the handling of such 187 namespaces. 188 1897. Registration Form(s) 190 191 Registrations for GSS-API namespaces SHALL take the following form: 192 193 +----------------------+----------------------+---------------------+ 194 | Registration Field | Possible Values | Description | 195 +----------------------+----------------------+---------------------+ 196 | Registration type | 'Individual', | Indicates whether | 197 | | 'Prefix', 'Range' | this entry reserves | 198 | | | a given symbol name | 199 | | | or constant value | 200 | | | or whether it | 201 | | | reserves an entire | 202 | | | sub-namespace (the | 203 | | | name is a "prefix") | 204 | | | or constant value | 205 | | | range. | 206 | Bindings | 'Generic', | Indicates the | 207 | | 'C-bindings', | language bindings | 208 | | 'Java', 'C#', etc... | that this | 209 | | | registration is | 210 | | | for, or, if | 211 | | | 'Generic', that | 212 | | | this is an entry | 213 | | | for the generic | 214 | | | GSS-API, not | 215 | | | specific to any | 216 | | | programming | 217 | | | language. | 218 | Object Type | 'Symbol', | Indicates whether | 219 220 221 222Williams Expires July 2, 2005 [Page 4] 223 224Internet-Draft GSS IANA Instructions January 2005 225 226 227 | | 'Constant-Value' | this registration | 228 | | | is for a symbol | 229 | | | (e.g., function, | 230 | | | constant name(s)) | 231 | | | or constant value. | 232 | Object Programming | 'Data-Type', | Indicates the type | 233 | Type | 'Function', | of the object(s) | 234 | | 'Method', 'Integer', | whose symbolic name | 235 | | 'String', 'OID' | or constant value | 236 | | | is this entry | 237 | | | registers. | 238 | Object Name | <Symbol name or name | The name(s) of | 239 | | prefix> | symbols or values | 240 | | | being registered. | 241 | Object Value | <Constant value> or | [Only for | 242 | | <constant value | Constant-Value | 243 | | range> | registrations.] The | 244 | | | value(s) | 245 | | | registered. | 246 | Description | <Text> | Description of | 247 | | | object(s) being | 248 | | | registered. | 249 | Reference | <Reference> | Reference to | 250 | | | document that | 251 | | | describes the | 252 | | | object(s) being | 253 | | | registered. | 254 | Status | 'Standards-Track', | | 255 | | 'Informational', | | 256 | | 'Experimental', | | 257 | | 'Obsolete' | | 258 +----------------------+----------------------+---------------------+ 259 260 The IANA should create a single GSS-API namespace registry, or 261 multiple registries, one for symbolic names and one for constant 262 values, or it may create a registry per-programming language, at its 263 convenience. 264 265 Entries in these registries should consist of all the fields from 266 their corresponding registration entries. 267 268 Entries SHOULD be sorted by object type, proggamming language, symbol 269 name. 270 271 <Add text on guidelines for IANA consideration of registration 272 applications, particularly with respect to entries lacking normative 273 references, "magic" entries (e.g., special values of 'time' types 274 which indicate something other than absolute or relative time, such 275 276 277 278Williams Expires July 2, 2005 [Page 5] 279 280Internet-Draft GSS IANA Instructions January 2005 281 282 283 as GSS_C_INDEFINITE), expert review requirements (if any) for 284 registrations lacking normative references, etc....> 285 2868. Initial Namespace Registrations 287 288 <Add registration entries for namespaces (name prefixes) for RFC2743/ 289 RFC2744/RFC2853.> 290 291 <Add registration entries for private namespaces (name prefixes) for 292 implementation- and/or platform-specific extensions.> 293 2949. Security Considerations 295 296 This document has no security considerations. 297 29810 Normative 299 300 [EXTENDED-INQUIRY] 301 Williams, N., "Extended Generic Security Service Mechanism 302 Inquiry APIs", 303 draft-ietf-kitten-extended-mech-inquiry-00.txt (work in 304 progress). 305 306 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 307 Requirement Levels", BCP 14, RFC 2119, March 1997. 308 309 [RFC2743] Linn, J., "Generic Security Service Application Program 310 Interface Version 2, Update 1", RFC 2743, January 2000. 311 312 [RFC2744] Wray, J., "Generic Security Service API Version 2 : 313 C-bindings", RFC 2744, January 2000. 314 315 316Author's Address 317 318 Nicolas Williams 319 Sun Microsystems 320 5300 Riata Trace Ct 321 Austin, TX 78727 322 US 323 324 EMail: Nicolas.Williams@sun.com 325 326 327 328 329 330 331 332 333 334Williams Expires July 2, 2005 [Page 6] 335 336Internet-Draft GSS IANA Instructions January 2005 337 338 339Intellectual Property Statement 340 341 The IETF takes no position regarding the validity or scope of any 342 Intellectual Property Rights or other rights that might be claimed to 343 pertain to the implementation or use of the technology described in 344 this document or the extent to which any license under such rights 345 might or might not be available; nor does it represent that it has 346 made any independent effort to identify any such rights. Information 347 on the procedures with respect to rights in RFC documents can be 348 found in BCP 78 and BCP 79. 349 350 Copies of IPR disclosures made to the IETF Secretariat and any 351 assurances of licenses to be made available, or the result of an 352 attempt made to obtain a general license or permission for the use of 353 such proprietary rights by implementers or users of this 354 specification can be obtained from the IETF on-line IPR repository at 355 http://www.ietf.org/ipr. 356 357 The IETF invites any interested party to bring to its attention any 358 copyrights, patents or patent applications, or other proprietary 359 rights that may cover technology that may be required to implement 360 this standard. Please address the information to the IETF at 361 ietf-ipr@ietf.org. 362 363 364Disclaimer of Validity 365 366 This document and the information contained herein are provided on an 367 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS 368 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET 369 ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, 370 INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE 371 INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 372 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 373 374 375Copyright Statement 376 377 Copyright (C) The Internet Society (2005). This document is subject 378 to the rights, licenses and restrictions contained in BCP 78, and 379 except as set forth therein, the authors retain all their rights. 380 381 382Acknowledgment 383 384 Funding for the RFC Editor function is currently provided by the 385 Internet Society. 386 387 388 389 390Williams Expires July 2, 2005 [Page 7] 391 392 393 394