< draft-turner-clearancesponsor-attribute-02.txt		draft-turner-clearancesponsor-attribute-03.txt >
	Network Working Group Sean Turner, IECA		Network Working Group Sean Turner, IECA
	Internet Draft October 20, 2009		Internet Draft February 1, 2010
	Intended Status: Informational Track		Intended Status: Informational Track
	Expires: April 20, 2010		Expires: August 1, 2010
	Clearance Sponsor Attribute		Clearance Sponsor Attribute
	draft-turner-clearancesponsor-attribute-02.txt		draft-turner-clearancesponsor-attribute-03.txt
			Abstract
			This document defines the clearance sponsor attribute. It indicates
			the entity that sponsored (i.e., granted) the clearance. This
			attribute is intended for use in public key certificates and
			attribute certificates that also include the clearance attribute.
	Status of this Memo		Status of this Memo
	This Internet-Draft is submitted to IETF in full conformance with the		This Internet-Draft is submitted to IETF in full conformance with the
	provisions of BCP 78 and BCP 79.		provisions of BCP 78 and BCP 79.
	Internet-Drafts are working documents of the Internet Engineering		Internet-Drafts are working documents of the Internet Engineering
	Task Force (IETF), its areas, and its working groups. Note that		Task Force (IETF), its areas, and its working groups. Note that
	other groups may also distribute working documents as Internet-		other groups may also distribute working documents as Internet-
	Drafts.		Drafts.
	skipping to change at page 1, line 31 ¶		skipping to change at page 1, line 38 ¶
	and may be updated, replaced, or obsoleted by other documents at any		and may be updated, replaced, or obsoleted by other documents at any
	time. It is inappropriate to use Internet-Drafts as reference		time. It is inappropriate to use Internet-Drafts as reference
	material or to cite them other than as "work in progress."		material or to cite them other than as "work in progress."
	The list of current Internet-Drafts can be accessed at		The list of current Internet-Drafts can be accessed at
	http://www.ietf.org/ietf/1id-abstracts.txt		http://www.ietf.org/ietf/1id-abstracts.txt
	The list of Internet-Draft Shadow Directories can be accessed at		The list of Internet-Draft Shadow Directories can be accessed at
	http://www.ietf.org/shadow.html		http://www.ietf.org/shadow.html
	This Internet-Draft will expire on April 20, 2010.		This Internet-Draft will expire on August 1, 2010.
	Copyright Notice		Copyright Notice
	Copyright (c) 2009 IETF Trust and the persons identified as the		Copyright (c) 2010 IETF Trust and the persons identified as the
	document authors. All rights reserved.		document authors. All rights reserved.
	This document is subject to BCP 78 and the IETF Trust's Legal		This document is subject to BCP 78 and the IETF Trust's Legal
	Provisions Relating to IETF Documents in effect on the date of		Provisions Relating to IETF Documents
	publication of this document (http://trustee.ietf.org/license-info).		(http://trustee.ietf.org/license-info) in effect on the date of
	Please review these documents carefully, as they describe your rights		publication of this document. Please review these documents
	and restrictions with respect to this document.		carefully, as they describe your rights and restrictions with respect
			to this document. Code Components extracted from this document must
	Abstract		include Simplified BSD License text as described in Section 4.e of
			the Trust Legal Provisions and are provided without warranty as
	This document defines the clearance sponsor attribute. This		described in the Simplified BSD License.
	attribute may be included in locations or protocols that support
	X.500 attributes.
	1. Introduction		1. Introduction
	This document specifies the clearance sponsor attribute. This		This document specifies the clearance sponsor attribute. It is
	attribute may be included in locations or protocols that support		included in public key certificates [RFC5280] and attribute
	X.500 attribute definitions to indicate the entity that sponsored the		certificates [RFC5755]. This attribute is only meaningful as a
	clearance. This attribute is only meaningful when the clearance		companion of the clearance attribute [RFC5755]. The clearance
	attribute [RFC3281bis] is also included.		sponsor is the entity (e.g., agency, department, or organization)
			that granted the clearance to the subject named in the certificate.
			For example, the clearance sponsor for a subject asserting the Amoco
			clearance values [RFC3114] could be "Engineering".
	This attribute may be used in authorization decisions. For example,		This attribute may be used in automated authorization decisions. For
	a web server deciding whether to allow a user access could check that		example, a web server deciding whether to allow a user access could
	the clearance sponsor present in the user's certificate is on an		check that the clearance sponsor present in the user's certificate is
	"approved" list. The web server could also check that the included		on an "approved" list. This check is performed in addition to
	clearance sponsor is on an "approved" list to issue the included		certification path validation [RFC5280]. The mechanism for managing
	clearance.		the "approved" list is beyond the scope of this document.
	NOTE: This document does not provide LDAP equivalent schema		NOTE: This document does not provide an equivalent LDAP schema
	specification as this attribute is initially targeted at public key		specification as this attribute is initially targeted at public key
	certificates [RFC5280] and attribute certificates [RFC3281bis]. This		certificates [RFC5280] and attribute certificates [RFC5755].
	is left to a future specification.		Definition of an equivalent LDAP schema is left to a future
			specification.
	1.1. Terminology		1.1. Terminology
	The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",		The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
	"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this		"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
	document are to be interpreted as described in [RFC2119].		document are to be interpreted as described in [RFC2119].
	1.2. ASN.1 Syntax Notation		1.2. ASN.1 Syntax Notation
	The attributes are defined using ASN.1 [X.680].		The attribute is defined using ASN.1 [X.680] through [X.683].
	2. Clearance Sponsor		2. Clearance Sponsor
	The clearance sponsor attribute indicates the sponsor of the		The clearance sponsor attribute, which is only meaningful if the
	clearance of the subject with which this attribute is associated.		clearance attribute [RFC5755] is also present, indicates the sponsor
	This attribute is only meaningful if the clearance attribute		of the clearance of the subject with which this attribute is
	[RFC3281bis] is also present. The clearance sponsor attribute is a		associated. The clearance sponsor attribute is a DirectoryString
	DirectoryString [RFC5280], which MUST use the UTF8String CHOICE,		[RFC5280], which MUST use the UTF8String CHOICE, string with a
	string with a minimum size of 1 characters and a maximum of 32		minimum size of 1 characters and a maximum of 64 characters.
	characters.
	The following object identifier identifies the sponsor attribute:		The following object identifier identifies the sponsor attribute:
	id-clearanceSponsor OBJECT IDENTIFIER ::= {		id-clearanceSponsor OBJECT IDENTIFIER ::= {
	joint-iso-ccitt(2) country(16) us(840) organization(1) gov(101)		joint-iso-ccitt(2) country(16) us(840) organization(1) gov(101)
	dod(2) infosec(1) attributes(5) 68		dod(2) infosec(1) attributes(5) 68
	}		}
	The ASN.1 syntax for the clearance sponsor attribute is as follows:		The ASN.1 syntax for the clearance sponsor attribute is as follows:
	clearanceSponsor ATTRIBUTE ::= {		at-clearanceSponsor ATTRIBUTE ::= {
	WITH SYNTAX DirectoryString { ub-clearance-sponsor }		TYPE DirectoryString { ub-clearance-sponsor }
	( WITH CONSTRAINT { utf8String PRESENT} )		( WITH COMPONENTS { utf8String PRESENT} )
	EQUALITY-MATCHING RULE caseIgnoreMatch		EQUALITY MATCHING RULE caseIgnoreMatch
	SINGLE VALUE TRUE		IDENTIFIED BY id-clearanceSponsor
	ID id-clearanceSponsor
	}		}
	ub-clearance-sponsor INTEGER ::= 32		ub-clearance-sponsor INTEGER ::= 64
	There MUST only be one value of clearanceSponsor associated with a		There MUST only be one value of clearanceSponsor associated with a
	particular certificate, as distinct sponsors SHOULD be represented in		particular certificate. Distinct sponsors MUST be represented in
	separate certificates.		separate certificates.
			When an environment uses the Clearance Sponsor attribute, it is
			important that the same representation of the sponsor be used
			throughout the environment (e.g., using the same acronym). Further,
			the value in this attribute is not meant to be globally unique. When
			included in certificates, it is unique within the scope of the
			issuer.
	3. Security Considerations		3. Security Considerations
	If this attribute is used as part of an authorization process, the		If this attribute is used as part of an authorization process, the
	procedures employed by the entity that assigns each value must ensure		procedures employed by the entity that assigns each clearance sponsor
	that the correct value is applied. Further, once applied to the		value must ensure that the correct value is applied. Including this
	object it must be bound to the object; this binding is normally		attribute in a public key certificate or attribute certificate
	performed by digitally signing over the object and the attribute to		ensures the value for the clearance sponsor is integrity protected.
	ensure data integrity.
			The certificate issuer and clearance sponsor are not necessarily the
			same entity. If they are separate entities, then the mechanism used
			by the clearance sponsor to convey to the certificate issuer that
			clearance sponsor did in fact grant the clearance to the subject
			needs to be protected from unauthorized modification.
			If two entities are verifying each other's certificates, they do not
			share the same issuer, and they use the same clearance sponsor value
			(e.g., a United Kingdom PKI includes "MoD" and a New Zealand PKI also
			includes "MoD"), then the relying party has two choices 1) accept the
			two as strings as equivalent 2) indicate the sponsor as well as the
			trust anchor. To solve this problem, a mechanism, which is out side
			the scope of this specification, could be developed to allow a
			relying party to group together issuers that share a same context
			within which sponsor names have a unique significance.
	While values of DirectoryString can include the NUL (U+0000) code		While values of DirectoryString can include the NUL (U+0000) code
	point, values used to represent clearance sponsors typically would		point, values used to represent clearance sponsors typically would
	not. Implementations of the caseIgnoreMatch rule must, per X.501,		not. Implementations of the caseIgnoreMatch rule must, per X.501,
	consider all of the assertion value and attribute value in matching		consider all of the assertion value and attribute value in matching
	and hence protect against truncation attacks.		and hence protect against truncation attacks.
	4. IANA Considerations		4. IANA Considerations
	None: All identifiers are already registered. Please remove this		None: All identifiers are already registered. Please remove this
	skipping to change at page 4, line 16 ¶		skipping to change at page 4, line 39 ¶
	5.1. Normative References		5.1. Normative References
	[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate		[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
	Requirement Levels", BCP 14, RFC 2119, March 1997.		Requirement Levels", BCP 14, RFC 2119, March 1997.
	[RFC5280] Cooper, D., et.al., "Internet X.509 Public Key		[RFC5280] Cooper, D., et.al., "Internet X.509 Public Key
	Infrastructure Certificate and Certification		Infrastructure Certificate and Certification
	Revocation List (CRL) Profile", RFC 5280, May 2008.		Revocation List (CRL) Profile", RFC 5280, May 2008.
	[RFC3281bis] Farrell, S., Housley, R., and S. Turner, "An Internet		[RFC5755] Farrell, S., Housley, R., and S. Turner, "An Internet
	Attribute Certificate Profile for Authorization",		Attribute Certificate Profile for Authorization", RFC
	draft-ietf-pkix-3281update-05.txt, work-in-progress.		5755, January 2010.
			[RFCTBD] Schaad, J., and P. Hoffman, "New ASN.1 Modules for
			PKIX", draft-ietf-pkix-new-asn1-07.txt, work-in-
			progress.
	/**		/**
	RFC Editor: Please replace "RFC3281bis" with "RFC####" where #### is		RFC Editor: Please replace "RFCTBD" with "RFC####" where #### is the
	the number of the published RFC in both the references and the text.		number of the published RFC. Please do this in both the references
			and the text.
	**/		**/
			[X.520] ITU-T Recommendation X.520 (2002) | ISO/IEC 9594-
			6:2002, Information technology - The Directory:
			Selected Attribute Types.
	[X.680] ITU-T Recommendation X.680 (2002) | ISO/IEC 8824-		[X.680] ITU-T Recommendation X.680 (2002) | ISO/IEC 8824-
	1:2002, Information technology - Abstract Syntax		1:2002, Information technology - Abstract Syntax
	Notation One (ASN.1): Specification of basic		Notation One (ASN.1): Specification of basic
	notation.		notation.
			[X.681] ITU-T Recommendation X.681 (2002) | ISO/IEC 8824-
			2:2002. Information Technology - Abstract Syntax
			Notation One: Information Object Specification.
			[X.682] ITU-T Recommendation X.682 (2002) | ISO/IEC 8824-
			3:2002. Information Technology - Abstract Syntax
			Notation One: Constraint Specification.
			[X.683] ITU-T Recommendation X.683 (2002) | ISO/IEC 8824-
			4:2002. Information Technology - Abstract Syntax
			Notation One: Parameterization of ASN.1
			Specifications.
	5.2. Informative References		5.2. Informative References
	None		[RFC3114] Nicolls, W., "Implementing Company Classification
			Policy with the S/MIME Security Label", RFC 3114, May
			2002.
	Appendix A. ASN.1 Module		Appendix A. ASN.1 Module
	This appendix provides the normative ASN.1 [X.680] definition for the		This appendix provides the normative ASN.1 [X.680] definitions for
	structure described in this specification.		the structures described in this specification using ASN.1 as defined
			in [X.680] through [X.683].
	ClearanceSponsorAttribute-2008		ClearanceSponsorAttribute-2008
	{ joint-iso-ccitt(2) country(16) us(840) organization(1) gov(101)		{ joint-iso-ccitt(2) country(16) us(840) organization(1) gov(101)
	dod(2) infosec(1) modules(0)		dod(2) infosec(1) modules(0)
	id-clearanceSponsorAttribute-2008(35) }		id-clearanceSponsorAttribute-2008(35) }
	DEFINITIONS IMPLICIT TAGS ::=		DEFINITIONS IMPLICIT TAGS ::=
	BEGIN		BEGIN
	-- EXPORTS ALL --		-- EXPORTS ALL --
	IMPORTS		IMPORTS
	-- Imports from RFC 5280 [RFC5280].
			-- Imports from New PKIX ASN.1 [RFCTBD]
	DirectoryString		DirectoryString
	PKIX1Explicit88		PKIX1Explicit-2009
	{ iso(1) identified-organization(3) dod(6) internet(1)		{ iso(1) identified-organization(3) dod(6) internet(1)
	security(5) mechanisms(5) pkix(7) id-mod(0)		security(5) mechanisms(5) pkix(7) id-mod(0)
	id-pkix1-explicit(18) }		id-pkix1-explicit-02(51) }
			-- Imports from New PKIX ASN.1 [RFCTBD]
			ATTRIBUTE
			FROM PKIX-CommonTypes-2009
			{ iso(1) identified-organization(3) dod(6) internet(1)
			security(5) mechanisms(5) pkix(7) id-mod(0)
			id-mod-pkixCommon-02(57) }
			-- Imports from ITU-T X.520 [X.520]
	-- Imports from ITU-T X.520 [X.520].
	caseIgnoreMatch		caseIgnoreMatch
	FROM SelectedAttributeTypes		FROM SelectedAttributeTypes
	{ joint-iso-itu-t ds(5) module(1) selectedAttributeTypes(5) 4 }		{ joint-iso-itu-t ds(5) module(1) selectedAttributeTypes(5) 4 }
	;		;
	-- sponsor attribute OID and syntax		-- sponsor attribute OID and syntax
	id-clearanceSponsor OBJECT IDENTIFIER ::= {		id-clearanceSponsor OBJECT IDENTIFIER ::= {
	joint-iso-ccitt(2) country(16) us(840) organization(1) gov(101)		joint-iso-ccitt(2) country(16) us(840) organization(1) gov(101)
	dod(2) infosec(1) attributes(5) 68		dod(2) infosec(1) attributes(5) 68
	}		}
	clearanceSponsor ATTRIBUTE ::= {		at-clearanceSponsor ATTRIBUTE ::= {
	WITH SYNTAX DirectoryString { ub-clearance-sponsor }		TYPE DirectoryString { ub-clearance-sponsor }
	( WITH CONSTRAINT { utf8String PRESENT} )		( WITH COMPONENTS { utf8String PRESENT} )
	EQUALITY-MATCHING RULE caseIgnoreMatch		EQUALITY MATCHING RULE caseIgnoreMatch
	SINGLE VALUE TRUE		IDENTIFIED BY id-clearanceSponsor
	ID id-clearanceSponsor
	}		}
	ub-clearance-sponsor INTEGER ::= 32		ub-clearance-sponsor INTEGER ::= 64
	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		END
	Author's Addresses		Author's Address
	Sean Turner		Sean Turner
	IECA, Inc.		IECA, Inc.
	3057 Nutley Street, Suite 106		3057 Nutley Street, Suite 106
	Fairfax, VA 22031		Fairfax, VA 22031
	USA		USA
	EMail: turners@ieca.com		EMail: turners@ieca.com
End of changes. 32 change blocks.
	113 lines changed or deleted		134 lines changed or added
This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/