Network Working Group Sean Turner, IECA Internet DraftOctober 19, 2009February 1, 2010 Intended Status: Informational Track Expires:April 19,August 1, 2010 Device Owner Attributedraft-turner-deviceowner-attribute-02.txtdraft-turner-deviceowner-attribute-03.txt Abstract This document defines the Device Owner attribute. It indicates the entity (e.g., company, organization, department, agency) that owns the device. This attribute may be included in public key certificates and attribute certificates. 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 onApril 19,August 1, 2010. Copyright Notice Copyright (c)20092010 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 (http://trustee.ietf.org/license-info) in effect on the date of publication of thisdocument (http://trustee.ietf.org/license-info).document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document.Abstract ThisCode Components extracted from this documentdefinesmust include Simplified BSD License text as described in Section 4.e of theDevice Owner attribute. This attribute may be includedTrust Legal Provisions and are provided without warranty as described inlocations or protocols that support ASN.1 attributes.the Simplified BSD License. 1. Introduction This document specifies the Device Owner attribute.This attribute may be included in locations or protocols that support ASN.1 attribute definitions to indicateIt indicates thecountry or groupentity (e.g., company, organization, department, agency) that owns the device. This attribute is intended to be used in public key certificates [RFC5280] and attribute certificates [RFC5755]. This attribute may be used in automated authorization decisions. For example,a routerwhen two peers are deciding whether toconnect to another routercommunicate each could check that the device owner present in the other device's certificate is on an "approved" list. This check is performed in addition to certification path validation [RFC5280]. The mechanism for managing the "approved" list is beyond the scope of this document. NOTE: This document does not provideLDAPan equivalent LDAP schema specification as this attribute is targeted at public key certificates [RFC5280] and attribute certificates[RFC3281bis]. This[RFC5755]. Definition of an equivalent LDAP schema 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 Theattributes areattribute is defined using ASN.1[X.680].[X.680] through [X.683]. 2. Device Owner The Device Owner attribute indicates thecountry or organizationentity (e.g., company, organization, department, agency) that owns the Device with which this attribute is associated. Device Owner isa choice of ISO 3166 [ISO3166-1] and [ISO3166-2] country codes oran objectidentifier that represents a group of nations, an organization, or any entity other than a nation.identifier. The following object identifier identifies the Device Owner attribute: id-deviceOwner OBJECT IDENTIFIER ::= { joint-iso-ccitt(2) country(16) us(840) organization(1) gov(101) dod(2) infosec(1) attributes(5) 69 } The ASN.1 syntax for the Device Owner attribute is as follows:deviceOwnerat-deviceOwner ATTRIBUTE ::= {WITH SYNTAX DeviceOwnerTYPE OBJECT IDENTIFIER EQUALITY MATCHING RULEdeviceOwnerMatch SINGLE VALUE TRUE IDobjectIdentifierMatch IDENTIFIED BY id-deviceOwner }DeviceOwner ::= CHOICE { alpha2Country [0] PrintableString ( SIZE (2) ), -- ISO 3166-1 2 Letter Codes (aka diagram). alpha3Country [1] PrintableString ( SIZE (3) ), -- ISO 3166-1 3 Letter Codes (aka trigram). alpha4Country [2] PrintableString ( SIZE (4) ), -- ISO 3166-2 4 Letter Codes (ISO 3166-1 diagram and a hyphen -- followed by one alpha or numeric code). alpha5Country [3] PrintableString ( SIZE (5) ), -- ISO 3166-2 5 Letter Codes (ISO 3166-1 diagram and a hyphen -- followed by two alpha or numeric codes). alpha6Country [4] PrintableString ( SIZE (6) ), -- ISO 3166-2 6 Letter Codes (ISO 3166-1 diagram and a hyphen -- followed by three alpha or numeric codes). numericCountry INTEGER (0..999), -- ISO 3166-1 3 Digit Codes. group OBJECT IDENTIFIER }There MUST only be one value of Device Owner associated with adevice, as distinctdevice. Distinct ownersSHOULDMUST be represented in separate certificates.NOTE: When an environment uses the Device Owner attribute, it is important that the same CHOICE be used throughout the environment. The following object identifier identifies the Device Owner matching rule: id-matching-rule-deviceOwnerMatch OBJECT IDENTIFIER ::= { joint-iso-ccitt(2) country(16) us(840) organization(1) gov(101) dod(2) infosec(1) matching-rules(9) 6 } When performing a match the following matching rule is used: deviceOwnerMatch MATCHING-RULE ::= { SYNTAX DeviceOwner ID id-matching-rule-deviceOwnerMatch } This rule returns a TRUE if the strings are the same length and corresponding characters are identical except possibly with regard to case.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;Including thisbinding is normally performed by digitally signing overattribute in a public key certificate or attribute certificate ensures theobject andvalue for theattribute to ensure data integrity.device owner is integrity protected. 4. IANA Considerations None: All identifiers are already registered. Please remove this section prior to publication as an RFC. 5. References 5.1. Normative References[ISO3166-1] ISO 3166-1: Codes for the Representation of Names of Countries and Their Subdivisions - Part 1: Country Codes, 2006. [ISO3166-2] ISO 3166-2: Codes for the Representation of Names of Countries and Their Subdivisions - Part 2: Country Subdivision Code, 2007.[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997.[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.[RFC5280] Cooper, D., et. al., "Internet X.509 Public Key Infrastructure Certificate and Certification Revocation List (CRL) Profile", RFC 5280, May 2008.[RFC3281bis][RFC5755] Farrell, S., Housley, R., and S. Turner, "An Internet Attribute Certificate Profile for Authorization",draft-ietf-pkix-3281update-05.txt, work-in-progress.RFC 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. /** RFCEdit:Editor: Please replace"RFC3281bis""RFCTBD" with "RFC####" where####### is the number of the publishedRFCRFC. Please do this in both the references and the text. **/ [X.501] ITU-T Recommendation X.520 (2002) | ISO/IEC 9594- 2:2002, Information technology - The Directory: Models. [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. [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 None Appendix A. ASN.1 Module This appendix provides the normative ASN.1 [X.680]definitiondefinitions for thestructurestructures described in thisspecification.specification using ASN.1 as defined in [X.680] through [X.683]. DeviceOwnerAttribute-2008 { joint-iso-ccitt(2) country(16) us(840) organization(1) gov(101) dod(2) infosec(1) module(0) id-deviceOwnerAttribute-2008(34) } DEFINITIONS IMPLICIT TAGS ::= BEGIN -- EXPORTS ALL -- IMPORTS -- IMPORTSNOTHINGfrom 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.501 [X.501] objectIdentifierMatch FROM InformationFramework { joint-iso-itu-t ds(5) module(1) informationFramework(1) 4 } ; -- device owner attribute OID and syntax id-deviceOwner OBJECT IDENTIFIER ::= { joint-iso-ccitt(2) country(16) us(840) organization(1) gov(101) dod(2) infosec(1) attributes(5) 69 }deviceOwnerat-deviceOwner ATTRIBUTE ::= {WITH SYNTAX DeviceOwner EQUALITY MATCHING RULE deviceOwnerMatch SINGLE VALUE TRUE ID id-deviceOwner } DeviceOwner ::= CHOICE { alpha2Country [0] PrintableString ( SIZE (2) ), -- ISO 3166-1 2 Letter Codes (aka diagram). alpha3Country [1] PrintableString ( SIZE (3) ), -- ISO 3166-1 3 Letter Codes (aka trigram). alpha4Country [2] PrintableString ( SIZE (4) ), -- ISO 3166-2 4 Letter Codes (ISO 3166-1 diagram and a hyphen -- followed by one alpha or numeric code). alpha5Country [3] PrintableString ( SIZE (5) ), -- ISO 3166-2 5 Letter Codes (ISO 3166-1 diagram and a hyphen -- followed by two alpha or numeric codes). alpha6Country [4] PrintableString ( SIZE (6) ), -- ISO 3166-2 6 Letter Codes (ISO 3166-1 diagram and a hyphen -- followed by three alpha or numeric codes). numericCountry INTEGER (0..999), -- ISO 3166-1 3 Digit Codes. group OBJECT IDENTIFIER } id-matching-rule-deviceOwnerMatch OBJECT IDENTIFIER ::= { joint-iso-ccitt(2) country(16) us(840) organization(1) gov(101) dod(2) infosec(1) matching-rules(9) 6 } deviceOwnerMatch MATCHING-RULE ::= { SYNTAX DeviceOwner ID id-matching-rule-deviceOwnerMatch } 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, &idTYPE OBJECT IDENTIFIERUNIQUE } 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)objectIdentifierMatch IDENTIFIED BY id-deviceOwner } END Author'sAddressesAddress Sean Turner IECA, Inc. 3057 Nutley Street, Suite 106 Fairfax, VA 22031 USA EMail: turners@ieca.com