idnits 2.17.1 draft-turner-clearancesponsor-attribute-03.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year == Unrecognized Status in 'Intended Status: Informational Track', assuming Proposed Standard (Expected one of 'Standards Track', 'Full Standard', 'Draft Standard', 'Proposed Standard', 'Best Current Practice', 'Informational', 'Experimental', 'Informational', 'Historic'.) -- 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 1, 2010) is 5196 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) == Outdated reference: A later version (-08) exists of draft-ietf-pkix-new-asn1-07 ** Downref: Normative reference to an Informational draft: draft-ietf-pkix-new-asn1 (ref. 'RFCTBD') Summary: 1 error (**), 0 flaws (~~), 3 warnings (==), 3 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Network Working Group Sean Turner, IECA 2 Internet Draft February 1, 2010 3 Intended Status: Informational Track 4 Expires: August 1, 2010 6 Clearance Sponsor Attribute 7 draft-turner-clearancesponsor-attribute-03.txt 9 Abstract 11 This document defines the clearance sponsor attribute. It indicates 12 the entity that sponsored (i.e., granted) the clearance. This 13 attribute is intended for use in public key certificates and 14 attribute certificates that also include the clearance attribute. 16 Status of this Memo 18 This Internet-Draft is submitted to IETF in full conformance with the 19 provisions of BCP 78 and BCP 79. 21 Internet-Drafts are working documents of the Internet Engineering 22 Task Force (IETF), its areas, and its working groups. Note that 23 other groups may also distribute working documents as Internet- 24 Drafts. 26 Internet-Drafts are draft documents valid for a maximum of six months 27 and may be updated, replaced, or obsoleted by other documents at any 28 time. It is inappropriate to use Internet-Drafts as reference 29 material or to cite them other than as "work in progress." 31 The list of current Internet-Drafts can be accessed at 32 http://www.ietf.org/ietf/1id-abstracts.txt 34 The list of Internet-Draft Shadow Directories can be accessed at 35 http://www.ietf.org/shadow.html 37 This Internet-Draft will expire on August 1, 2010. 39 Copyright Notice 41 Copyright (c) 2010 IETF Trust and the persons identified as the 42 document authors. All rights reserved. 44 This document is subject to BCP 78 and the IETF Trust's Legal 45 Provisions Relating to IETF Documents 46 (http://trustee.ietf.org/license-info) in effect on the date of 47 publication of this document. Please review these documents 48 carefully, as they describe your rights and restrictions with respect 49 to this document. Code Components extracted from this document must 50 include Simplified BSD License text as described in Section 4.e of 51 the Trust Legal Provisions and are provided without warranty as 52 described in the Simplified BSD License. 54 1. Introduction 56 This document specifies the clearance sponsor attribute. It is 57 included in public key certificates [RFC5280] and attribute 58 certificates [RFC5755]. This attribute is only meaningful as a 59 companion of the clearance attribute [RFC5755]. The clearance 60 sponsor is the entity (e.g., agency, department, or organization) 61 that granted the clearance to the subject named in the certificate. 62 For example, the clearance sponsor for a subject asserting the Amoco 63 clearance values [RFC3114] could be "Engineering". 65 This attribute may be used in automated authorization decisions. For 66 example, a web server deciding whether to allow a user access could 67 check that the clearance sponsor present in the user's certificate is 68 on an "approved" list. This check is performed in addition to 69 certification path validation [RFC5280]. The mechanism for managing 70 the "approved" list is beyond the scope of this document. 72 NOTE: This document does not provide an equivalent LDAP schema 73 specification as this attribute is initially targeted at public key 74 certificates [RFC5280] and attribute certificates [RFC5755]. 75 Definition of an equivalent LDAP schema is left to a future 76 specification. 78 1.1. Terminology 80 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 81 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 82 document are to be interpreted as described in [RFC2119]. 84 1.2. ASN.1 Syntax Notation 86 The attribute is defined using ASN.1 [X.680] through [X.683]. 88 2. Clearance Sponsor 90 The clearance sponsor attribute, which is only meaningful if the 91 clearance attribute [RFC5755] is also present, indicates the sponsor 92 of the clearance of the subject with which this attribute is 93 associated. The clearance sponsor attribute is a DirectoryString 94 [RFC5280], which MUST use the UTF8String CHOICE, string with a 95 minimum size of 1 characters and a maximum of 64 characters. 97 The following object identifier identifies the sponsor attribute: 99 id-clearanceSponsor OBJECT IDENTIFIER ::= { 100 joint-iso-ccitt(2) country(16) us(840) organization(1) gov(101) 101 dod(2) infosec(1) attributes(5) 68 102 } 104 The ASN.1 syntax for the clearance sponsor attribute is as follows: 106 at-clearanceSponsor ATTRIBUTE ::= { 107 TYPE DirectoryString { ub-clearance-sponsor } 108 ( WITH COMPONENTS { utf8String PRESENT} ) 109 EQUALITY MATCHING RULE caseIgnoreMatch 110 IDENTIFIED BY id-clearanceSponsor 111 } 113 ub-clearance-sponsor INTEGER ::= 64 115 There MUST only be one value of clearanceSponsor associated with a 116 particular certificate. Distinct sponsors MUST be represented in 117 separate certificates. 119 When an environment uses the Clearance Sponsor attribute, it is 120 important that the same representation of the sponsor be used 121 throughout the environment (e.g., using the same acronym). Further, 122 the value in this attribute is not meant to be globally unique. When 123 included in certificates, it is unique within the scope of the 124 issuer. 126 3. Security Considerations 128 If this attribute is used as part of an authorization process, the 129 procedures employed by the entity that assigns each clearance sponsor 130 value must ensure that the correct value is applied. Including this 131 attribute in a public key certificate or attribute certificate 132 ensures the value for the clearance sponsor is integrity protected. 134 The certificate issuer and clearance sponsor are not necessarily the 135 same entity. If they are separate entities, then the mechanism used 136 by the clearance sponsor to convey to the certificate issuer that 137 clearance sponsor did in fact grant the clearance to the subject 138 needs to be protected from unauthorized modification. 140 If two entities are verifying each other's certificates, they do not 141 share the same issuer, and they use the same clearance sponsor value 142 (e.g., a United Kingdom PKI includes "MoD" and a New Zealand PKI also 143 includes "MoD"), then the relying party has two choices 1) accept the 144 two as strings as equivalent 2) indicate the sponsor as well as the 145 trust anchor. To solve this problem, a mechanism, which is out side 146 the scope of this specification, could be developed to allow a 147 relying party to group together issuers that share a same context 148 within which sponsor names have a unique significance. 150 While values of DirectoryString can include the NUL (U+0000) code 151 point, values used to represent clearance sponsors typically would 152 not. Implementations of the caseIgnoreMatch rule must, per X.501, 153 consider all of the assertion value and attribute value in matching 154 and hence protect against truncation attacks. 156 4. IANA Considerations 158 None: All identifiers are already registered. Please remove this 159 section prior to publication as an RFC. 161 5. References 163 5.1. Normative References 165 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 166 Requirement Levels", BCP 14, RFC 2119, March 1997. 168 [RFC5280] Cooper, D., et.al., "Internet X.509 Public Key 169 Infrastructure Certificate and Certification 170 Revocation List (CRL) Profile", RFC 5280, May 2008. 172 [RFC5755] Farrell, S., Housley, R., and S. Turner, "An Internet 173 Attribute Certificate Profile for Authorization", RFC 174 5755, January 2010. 176 [RFCTBD] Schaad, J., and P. Hoffman, "New ASN.1 Modules for 177 PKIX", draft-ietf-pkix-new-asn1-07.txt, work-in- 178 progress. 180 /** 181 RFC Editor: Please replace "RFCTBD" with "RFC####" where #### is the 182 number of the published RFC. Please do this in both the references 183 and the text. 184 **/ 186 [X.520] ITU-T Recommendation X.520 (2002) | ISO/IEC 9594- 187 6:2002, Information technology - The Directory: 188 Selected Attribute Types. 190 [X.680] ITU-T Recommendation X.680 (2002) | ISO/IEC 8824- 191 1:2002, Information technology - Abstract Syntax 192 Notation One (ASN.1): Specification of basic 193 notation. 195 [X.681] ITU-T Recommendation X.681 (2002) | ISO/IEC 8824- 196 2:2002. Information Technology - Abstract Syntax 197 Notation One: Information Object Specification. 199 [X.682] ITU-T Recommendation X.682 (2002) | ISO/IEC 8824- 200 3:2002. Information Technology - Abstract Syntax 201 Notation One: Constraint Specification. 203 [X.683] ITU-T Recommendation X.683 (2002) | ISO/IEC 8824- 204 4:2002. Information Technology - Abstract Syntax 205 Notation One: Parameterization of ASN.1 206 Specifications. 208 5.2. Informative References 210 [RFC3114] Nicolls, W., "Implementing Company Classification 211 Policy with the S/MIME Security Label", RFC 3114, May 212 2002. 214 Appendix A. ASN.1 Module 216 This appendix provides the normative ASN.1 [X.680] definitions for 217 the structures described in this specification using ASN.1 as defined 218 in [X.680] through [X.683]. 220 ClearanceSponsorAttribute-2008 221 { joint-iso-ccitt(2) country(16) us(840) organization(1) gov(101) 222 dod(2) infosec(1) modules(0) 223 id-clearanceSponsorAttribute-2008(35) } 225 DEFINITIONS IMPLICIT TAGS ::= 227 BEGIN 229 -- EXPORTS ALL -- 231 IMPORTS 233 -- Imports from New PKIX ASN.1 [RFCTBD] 235 DirectoryString 236 PKIX1Explicit-2009 237 { iso(1) identified-organization(3) dod(6) internet(1) 238 security(5) mechanisms(5) pkix(7) id-mod(0) 239 id-pkix1-explicit-02(51) } 241 -- Imports from New PKIX ASN.1 [RFCTBD] 243 ATTRIBUTE 244 FROM PKIX-CommonTypes-2009 245 { iso(1) identified-organization(3) dod(6) internet(1) 246 security(5) mechanisms(5) pkix(7) id-mod(0) 247 id-mod-pkixCommon-02(57) } 249 -- Imports from ITU-T X.520 [X.520] 251 caseIgnoreMatch 252 FROM SelectedAttributeTypes 253 { joint-iso-itu-t ds(5) module(1) selectedAttributeTypes(5) 4 } 255 ; 256 -- sponsor attribute OID and syntax 258 id-clearanceSponsor OBJECT IDENTIFIER ::= { 259 joint-iso-ccitt(2) country(16) us(840) organization(1) gov(101) 260 dod(2) infosec(1) attributes(5) 68 261 } 263 at-clearanceSponsor ATTRIBUTE ::= { 264 TYPE DirectoryString { ub-clearance-sponsor } 265 ( WITH COMPONENTS { utf8String PRESENT} ) 266 EQUALITY MATCHING RULE caseIgnoreMatch 267 IDENTIFIED BY id-clearanceSponsor 268 } 270 ub-clearance-sponsor INTEGER ::= 64 272 END 274 Author's Address 276 Sean Turner 277 IECA, Inc. 278 3057 Nutley Street, Suite 106 279 Fairfax, VA 22031 280 USA 282 EMail: turners@ieca.com