Network Working Group Sean Turner, IECA Internet Draft October 19, 2009 Intended Status: Informational Track Expires: April 19, 2010 Device Owner Attribute draft-turner-deviceowner-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 19, 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 19, 2010 [Page 1] Internet-Draft Device Owner Attribute August 2009 Abstract This document defines the Device Owner attribute. This attribute may be included in locations or protocols that support ASN.1 attributes. 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 indicate the country or group that owns the device. This attribute may be used in authorization decisions. For example, a router deciding whether to connect to another router could check that the device owner present in the device's certificate is on an "approved" list. NOTE: This document does not provide LDAP equivalent schema specification as this attribute is 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. Device Owner The Device Owner attribute indicates the country or organization that owns the Device with which this attribute is associated. Device Owner is a choice of ISO 3166 [ISO3166-1] and [ISO3166-2] country codes or an object identifier that represents a group of nations, an organization, or any entity other than a nation. Turner Expires April 19, 2010 [Page 2] Internet-Draft Device Owner Attribute August 2009 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: 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 } There MUST only be one value of Device Owner associated with a device, as distinct owners SHOULD 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. Turner Expires April 19, 2010 [Page 3] Internet-Draft Device Owner Attribute August 2009 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; this binding is normally performed by digitally signing over the object and the attribute to ensure data integrity. 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. Turner Expires April 19, 2010 [Page 4] Internet-Draft Device Owner Attribute August 2009 [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] Farrell, S., Housley, R., and S. Turner, "An Internet Attribute Certificate Profile for Authorization", draft-ietf-pkix-3281update-05.txt, work-in-progress. /** RFC Edit: Please replace "RFC3281bis" with "RFC####" where ### is the number of the published RFC in both the references and the text. **/ 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. 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 NOTHING -- -- device owner attribute OID and syntax Turner Expires April 19, 2010 [Page 5] Internet-Draft Device Owner Attribute August 2009 id-deviceOwner OBJECT IDENTIFIER ::= { joint-iso-ccitt(2) country(16) us(840) organization(1) gov(101) dod(2) infosec(1) attributes(5) 69 } 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 } Turner Expires April 19, 2010 [Page 6] Internet-Draft Device Owner Attribute August 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 19, 2010 [Page 7] Internet-Draft Device Owner Attribute August 2009 Author's Addresses Sean Turner IECA, Inc. 3057 Nutley Street, Suite 106 Fairfax, VA 22031 USA EMail: turners@ieca.com Turner Expires April 19, 2010 [Page 8]