Network Working Group Sean Turner, IECA
Internet Draft October 20, 2009
Intended Status: Informational Track
Expires: April 20, 2010
Clearance Sponsor Attribute
draft-turner-clearancesponsor-attribute-02.txt
Status of this Memo
This Internet-Draft is submitted to IETF in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet-
Drafts.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt
The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html
This Internet-Draft will expire on April 20, 2010.
Copyright Notice
Copyright (c) 2009 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents in effect on the date of
publication of this document (http://trustee.ietf.org/license-info).
Please review these documents carefully, as they describe your rights
and restrictions with respect to this document.
Turner Expires April 20, 2010 [Page 1]
Internet-Draft Clearance Sponsor Attribute October 2009
Abstract
This document defines the clearance sponsor attribute. This
attribute may be included in locations or protocols that support
X.500 attributes.
1. Introduction
This document specifies the clearance sponsor attribute. This
attribute may be included in locations or protocols that support
X.500 attribute definitions to indicate the entity that sponsored the
clearance. This attribute is only meaningful when the clearance
attribute [RFC3281bis] is also included.
This attribute may be used in authorization decisions. For example,
a web server deciding whether to allow a user access could check that
the clearance sponsor present in the user's certificate is on an
"approved" list. The web server could also check that the included
clearance sponsor is on an "approved" list to issue the included
clearance.
NOTE: This document does not provide LDAP equivalent schema
specification as this attribute is initially targeted at public key
certificates [RFC5280] and attribute certificates [RFC3281bis]. This
is left to a future specification.
1.1. Terminology
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [RFC2119].
1.2. ASN.1 Syntax Notation
The attributes are defined using ASN.1 [X.680].
2. Clearance Sponsor
The clearance sponsor attribute indicates the sponsor of the
clearance of the subject with which this attribute is associated.
This attribute is only meaningful if the clearance attribute
[RFC3281bis] is also present. The clearance sponsor attribute is a
DirectoryString [RFC5280], which MUST use the UTF8String CHOICE,
string with a minimum size of 1 characters and a maximum of 32
characters.
Turner Expires April 20, 2010 [Page 2]
Internet-Draft Clearance Sponsor Attribute October 2009
The following object identifier identifies the sponsor attribute:
id-clearanceSponsor OBJECT IDENTIFIER ::= {
joint-iso-ccitt(2) country(16) us(840) organization(1) gov(101)
dod(2) infosec(1) attributes(5) 68
}
The ASN.1 syntax for the clearance sponsor attribute is as follows:
clearanceSponsor ATTRIBUTE ::= {
WITH SYNTAX DirectoryString { ub-clearance-sponsor }
( WITH CONSTRAINT { utf8String PRESENT} )
EQUALITY-MATCHING RULE caseIgnoreMatch
SINGLE VALUE TRUE
ID id-clearanceSponsor
}
ub-clearance-sponsor INTEGER ::= 32
There MUST only be one value of clearanceSponsor associated with a
particular certificate, as distinct sponsors SHOULD be represented in
separate certificates.
3. Security Considerations
If this attribute is used as part of an authorization process, the
procedures employed by the entity that assigns each value must ensure
that the correct value is applied. Further, once applied to the
object it must be bound to the object; this binding is normally
performed by digitally signing over the object and the attribute to
ensure data integrity.
While values of DirectoryString can include the NUL (U+0000) code
point, values used to represent clearance sponsors typically would
not. Implementations of the caseIgnoreMatch rule must, per X.501,
consider all of the assertion value and attribute value in matching
and hence protect against truncation attacks.
4. IANA Considerations
None: All identifiers are already registered. Please remove this
section prior to publication as an RFC.
Turner Expires April 20, 2010 [Page 3]
Internet-Draft Clearance Sponsor Attribute October 2009
5. References
5.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC5280] Cooper, D., et.al., "Internet X.509 Public Key
Infrastructure Certificate and Certification
Revocation List (CRL) Profile", RFC 5280, May 2008.
[RFC3281bis] Farrell, S., Housley, R., and S. Turner, "An Internet
Attribute Certificate Profile for Authorization",
draft-ietf-pkix-3281update-05.txt, work-in-progress.
/**
RFC Editor: Please replace "RFC3281bis" with "RFC####" where #### is
the number of the published RFC in both the references and the text.
**/
[X.680] ITU-T Recommendation X.680 (2002) | ISO/IEC 8824-
1:2002, Information technology - Abstract Syntax
Notation One (ASN.1): Specification of basic
notation.
5.2. Informative References
None
Appendix A. ASN.1 Module
This appendix provides the normative ASN.1 [X.680] definition for the
structure described in this specification.
ClearanceSponsorAttribute-2008
{ joint-iso-ccitt(2) country(16) us(840) organization(1) gov(101)
dod(2) infosec(1) modules(0)
id-clearanceSponsorAttribute-2008(35) }
DEFINITIONS IMPLICIT TAGS ::=
BEGIN
-- EXPORTS ALL --
IMPORTS
Turner Expires April 20, 2010 [Page 4]
Internet-Draft Clearance Sponsor Attribute October 2009
-- Imports from RFC 5280 [RFC5280].
DirectoryString
PKIX1Explicit88
{ iso(1) identified-organization(3) dod(6) internet(1)
security(5) mechanisms(5) pkix(7) id-mod(0)
id-pkix1-explicit(18) }
-- Imports from ITU-T X.520 [X.520].
caseIgnoreMatch
FROM SelectedAttributeTypes
{ joint-iso-itu-t ds(5) module(1) selectedAttributeTypes(5) 4 }
;
-- sponsor attribute OID and syntax
id-clearanceSponsor OBJECT IDENTIFIER ::= {
joint-iso-ccitt(2) country(16) us(840) organization(1) gov(101)
dod(2) infosec(1) attributes(5) 68
}
clearanceSponsor ATTRIBUTE ::= {
WITH SYNTAX DirectoryString { ub-clearance-sponsor }
( WITH CONSTRAINT { utf8String PRESENT} )
EQUALITY-MATCHING RULE caseIgnoreMatch
SINGLE VALUE TRUE
ID id-clearanceSponsor
}
ub-clearance-sponsor INTEGER ::= 32
Turner Expires April 20, 2010 [Page 5]
Internet-Draft Clearance Sponsor Attribute October 2009
ATTRIBUTE ::= CLASS {
&derivation ATTRIBUTE OPTIONAL,
&Type OPTIONAL,
-- either &Type or &derivation required
&equality-match MATCHING-RULE OPTIONAL,
&ordering-match MATCHING-RULE OPTIONAL,
&substrings-match MATCHING-RULE OPTIONAL,
&single-valued BOOLEAN DEFAULT FALSE,
&collective BOOLEAN DEFAULT FALSE,
-- operational extensions
&no-user-modification BOOLEAN DEFAULT FALSE,
&usage AttributeUsage DEFAULT userApplications,
&id OBJECT IDENTIFIER UNIQUE }
WITH SYNTAX {
[ SUBTYPE OF &derivation ]
[ WITH SYNTAX &Type ]
[ EQUALITY MATCHING RULE &equality-match ]
[ ORDERING MATCHING RULE &ordering-match ]
[ SUBSTRINGS MATCHING RULE &substrings-match ]
[ SINGLE VALUE &single-valued ]
[ COLLECTIVE &collective ]
[ NO USER MODIFICATION &no-user-modification ]
[ USAGE &usage ]
ID &id }
MATCHING-RULE ::= CLASS {
&AssertionType OPTIONAL,
&id OBJECT IDENTIFIER UNIQUE }
WITH SYNTAX {
[ SYNTAX &AssertionType ]
ID &id }
AttributeType ::= ATTRIBUTE.&id
AttributeValue ::= ATTRIBUTE.&Type
AttributeUsage ::= ENUMERATED {
userApplications (0),
directoryOperation (1),
distributedOperation (2),
dSAOperation (3) }
END
Turner Expires April 20, 2010 [Page 6]
Internet-Draft Clearance Sponsor Attribute October 2009
Author's Addresses
Sean Turner
IECA, Inc.
3057 Nutley Street, Suite 106
Fairfax, VA 22031
USA
EMail: turners@ieca.com
Turner Expires April 20, 2010 [Page 7]
