Network Working Group Sean Turner, IECA Internet Draft October 3, 2008 Intended Status: Informational Track Expires: April 3, 2009 Device Owner Attribute draft-turner-deviceowner-attribute-00.txt Status of this Memo By submitting this Internet-Draft, each author represents that any applicable patent or other IPR claims of which he or she is aware have been or will be disclosed, and any of which he or she becomes aware will be disclosed, in accordance with Section 6 of 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 3, 2009. Copyright Notice Copyright (C) The IETF Trust (2008). Abstract This document defines the deviceOwner attribute. This attribute may be carried in a public key certificate in the Subject Directory Attributes extension, in an attribute certificate in the attribute field, in a directory as an attribute, or in protocols that support attributes. Turner Expires April 3, 2009 [Page 1] Internet-Draft Device Owner Attribute October 2008 1. Introduction This document specifies the Device Owner attribute. This attribute may be included in public key certificates [RFC5280], attribute certificates [RFC3281], directories [X.500]/[RFC4512], or locations that support attributes. This attribute may be used in authorization decisions. 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. One of the choices MUST be present. The following object identifier identifies the Device Owner attribute: id-aa-KP-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 SINGLE VALUE TRUE IDENTIFIED BY id-deviceOwner } Turner Expires April 3, 2009 [Page 2] Internet-Draft Device Owner Attribute October 2008 DeviceOwner ::= CHOICE { alpha2Country [0] PrintableString ( SIZE (2) ), -- ISO 3166-1 2 Letter Codes (aka digram) 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 digram and a hyphen -- followed by one alpha or numeric code). alpha5Country [3] PrintableString ( SIZE (5) ), -- ISO 3166-2 5 Letter Codes (ISO 3166-1 digram and a hyphen -- followed by two alpha or numeric code). alpha6Country [4] PrintableString ( SIZE (6) ), -- ISO 3166-2 6 Letter Codes (ISO 3166-1 digram and a hyphen -- followed by three alpha or numeric code). numericCountry INTEGER ( SIZE (3) ), -- ISO 3166-1 3 Digit Codes group OBJECT IDENTIFIER } There must only be one value of Device Owner associated with a device. 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. Turner Expires April 3, 2009 [Page 3] Internet-Draft Device Owner Attribute October 2008 [ISO3166-2] ISO 3166-2: Codes for the Representation of Names of Countries and Their Subdivisions - Part 2: Country Subdivision Code, 2007. [RFC3281] Farrell, S., and R. Housley, "An Internet Attribute Certificate Profile for Authorization", RFC 3281, April 2002. [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: Information Technology - Abstract Syntax Notation One, 1997. 5.2. Informative References [RFC4512] Sermersheim, J., "Lightweight Directory Access Protocol (LDAP): Directory Information Models", RFC 4512, June 2006. [RFC5280] Cooper, D., et. al., "Internet X.509 Public Key Infrastructure Certificate and Certification Revocation List (CRL) Profile", RFC 5280, May 2008. [X.500] ITU-T Recommendation X.500: Information Technology - Open Systems Interconnection - The Directory, 1993. 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 IMPLICT TAGS ::= BEGIN -- EXPORTS ALL -- -- IMPORTS NOTHING -- -- device owner attribute OID and syntax Turner Expires April 3, 2009 [Page 4] Internet-Draft Device Owner Attribute October 2008 id-aa-KP-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 SINGLE VALUE TRUE IDENTIFIED BY id-deviceOwner } DeviceOwner ::= CHOICE { Alpha2Country [0] PrintableString ( SIZE (2) ), -- ISO 3166-1 2 Letter Codes (aka digram) 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 digram and a hyphen -- followed by one alpha or numeric code). Alpha5Country [3] PrintableString ( SIZE (5) ), -- ISO 3166-2 5 Letter Codes (ISO 3166-1 digram and a hyphen -- followed by two alpha or numeric code). Alpha6Country [4] PrintableString ( SIZE (6) ), -- ISO 3166-2 6 Letter Codes (ISO 3166-1 digram and a hyphen -- followed by three alpha or numeric code). NumericCountry INTEGER ( SIZE (3) ), -- ISO 3166-1 3 Digit Codes group OBJECT IDENTIFIER } Turner Expires April 3, 2009 [Page 5] Internet-Draft Device Owner Attribute October 2008 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 3, 2009 [Page 6] Internet-Draft Device Owner Attribute October 2008 Author's Addresses Sean Turner IECA, Inc. 3057 Nutley Street, Suite 106 Fairfax, VA 22031 USA EMail: turners@ieca.com Turner Expires April 3, 2009 [Page 7] Internet-Draft Device Owner Attribute October 2008 Full Copyright Statement Copyright (C) The IETF Trust (2008). This document is subject to the rights, licenses and restrictions contained in BCP 78, and except as set forth therein, the authors retain all their rights. This document and the information contained herein are provided on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Intellectual Property The IETF takes no position regarding the validity or scope of any Intellectual Property Rights or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; nor does it represent that it has made any independent effort to identify any such rights. Information on the procedures with respect to rights in RFC documents can be found in BCP 78 and BCP 79. Copies of IPR disclosures made to the IETF Secretariat and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users of this specification can be obtained from the IETF on-line IPR repository at http://www.ietf.org/ipr. The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights that may cover technology that may be required to implement this standard. Please address the information to the IETF at ietf- ipr@ietf.org. Acknowledgment Funding for the RFC Editor function is provided by the IETF Administrative Support Activity (IASA). Turner Expires April 3, 2009 [Page 8]