IETF D. McWalter, Ed. Internet-Draft Data Connection Ltd Proposed Status: Standards Track March 1, 2007 Expires: September 2, 2007 Uniform Resource Identifier (URI) MIB draft-mcwalter-uri-mib-03.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 September 2, 2007. Copyright Notice Copyright (C) The IETF Trust (2007). Abstract This MIB module defines textual conventions to represent STD 66 Uniform Resource Identifiers (URIs). The intent is that these textual conventions will be imported and used in MIB modules that would otherwise define their own representation(s). McWalter Expires September 2, 2007 [Page 1] Internet-Draft URI MIB March 2007 Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. The Internet-Standard Management Framework . . . . . . . . . . 3 3. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 3 4. Security Considerations . . . . . . . . . . . . . . . . . . . 5 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 6 6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 6 7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 6 7.1 Normative References . . . . . . . . . . . . . . . . . . . 6 7.2 Informative References . . . . . . . . . . . . . . . . . . 6 Author's Address . . . . . . . . . . . . . . . . . . . . . . . 7 Intellectual Property and Copyright Statements . . . . . . . . 8 McWalter Expires September 2, 2007 [Page 2] Internet-Draft URI MIB March 2007 1. Introduction This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. It defines a textual convention to represent STD 66 [RFC3986] URIs. 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 RFC 2119 [RFC2119]. 2. The Internet-Standard Management Framework For a detailed overview of the documents that describe the current Internet-Standard Management Framework, please refer to section 7 of RFC 3410 [RFC3410]. Managed objects are accessed via a virtual information store, termed the Management Information Base or MIB. MIB objects are generally accessed through the Simple Network Management Protocol (SNMP). Objects in the MIB are defined using the mechanisms defined in the Structure of Management Information (SMI). This memo specifies a MIB module that is compliant to the SMIv2, which is described in STD 58, RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 [RFC2580]. 3. Definitions URI-TC-MIB DEFINITIONS ::= BEGIN IMPORTS MODULE-IDENTITY, mib-2 FROM SNMPv2-SMI -- [RFC2578] TEXTUAL-CONVENTION FROM SNMPv2-TC; -- [RFC2579] uriTcMIB MODULE-IDENTITY LAST-UPDATED "200703010000Z" -- 1 March 2007 ORGANIZATION "IETF Operations and Management (OPS) Area" CONTACT-INFO "EMail: ops-area@ietf.org Home page: http://www.ops.ietf.org/" DESCRIPTION "This MIB module defines textual conventions for representing URIs, as defined by RFC 3986 STD 66." REVISION "200703010000Z" -- 1 March 2007 DESCRIPTION "Initial revision, published as RFC yyyy. Copyright (C) The IETF Trust (2007). This version of this MIB module is part of RFC yyyy; see the RFC itself for full legal notices." McWalter Expires September 2, 2007 [Page 3] Internet-Draft URI MIB March 2007 -- RFC Ed.: replace yyyy with actual RFC number & remove this note ::= { mib-2 XXX } -- RFC Ed.: replace XXX with IANA-assigned number & remove this note Uri ::= TEXTUAL-CONVENTION DISPLAY-HINT "1a" STATUS current DESCRIPTION "A Uniform Resource Identifier (URI) as defined by STD 66. This URI MUST be a normalized as defined in section 6 of RFC 3986 STD 66. STD 66 defines that some parts of a URI are case-insensitive, but objects using this textual convention MUST use normalized URIs. The purpose of this restriction is to help provide unique URIs for use as MIB table indexes. Note that normalization of URIs does not by itself provide uniqueness: Two textually distinct normalized URIs may be equivalent. A zero-length URI is not a valid URI. This can be used to express 'URI absent' where required, for example when used as an index field." REFERENCE "RFC 3986 STD 66 and RFC 3305" SYNTAX OCTET STRING Uri255 ::= TEXTUAL-CONVENTION DISPLAY-HINT "255a" STATUS current DESCRIPTION "A Uniform Resource Identifier (URI) as defined by STD 66. This URI MUST be a normalized as defined in section 6 of RFC 3986 STD 66. STD 66 defines that some parts of a URI are case-insensitive, but objects using this textual convention MUST use normalized URIs. The purpose of this restriction is to help provide unique URIs for use as MIB table indexes. Note that normalization of URIs does not by itself provide uniqueness: Two textually distinct normalized URIs may be equivalent. STD 66 URIs are of unlimited length. Objects using this textual convention impose an arbitrary length limit on the URIs that they can represent. If no length restriction is required, then objects SHOULD use the 'Uri' textual convention instead. A zero-length URI is not a valid URI. This can be used to express 'URI absent' where required, for example when used McWalter Expires September 2, 2007 [Page 4] Internet-Draft URI MIB March 2007 as an index field." REFERENCE "RFC 3986 STD 66 and RFC 3305" SYNTAX OCTET STRING (SIZE (0..255)) Uri1024 ::= TEXTUAL-CONVENTION DISPLAY-HINT "1024a" STATUS current DESCRIPTION "A Uniform Resource Identifier (URI) as defined by STD 66. This URI MUST be a normalized as defined in section 6 of RFC 3986 STD 66. STD 66 defines that some parts of a URI are case-insensitive, but objects using this textual convention MUST use normalized URIs. The purpose of this restriction is to help provide unique URIs for use as MIB table indexes. Note that normalization of URIs does not by itself provide uniqueness: Two textually distinct normalized URIs may be equivalent. STD 66 URIs are of unlimited length. Objects using this textual convention impose an arbitrary length limit on the URIs that they can represent. If no length restriction is required, then objects SHOULD use the 'Uri' textual convention instead. A zero-length URI is not a valid URI. This can be used to express 'URI absent' where required, for example when used as an index field." REFERENCE "RFC 3986 STD 66 and RFC 3305" SYNTAX OCTET STRING (SIZE (0..1024)) END 4. Security Considerations See also the Security Considerations of STD 66 [RFC3986]. This MIB module does not define any management objects. Instead, it defines a textual convention that may be imported by other MIB modules and used for object definitions. Meaningful security considerations can only be written in the MIB modules that define management objects. This document therefore has no impact on the security of the Internet. McWalter Expires September 2, 2007 [Page 5] Internet-Draft URI MIB March 2007 5. IANA Considerations URI-TC-MIB should be rooted under the mib-2 subtree. IANA is requested to assign { mib-2 XXX } to the URI-TC-MIB module specified in this document. 6. Acknowledgements This module was generated by editing together contributions from Randy Presuhn, Dan Romascanu, Bill Fenner, Juergen Schoenwaelder, and others. 7. References 7.1 Normative References [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997. [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J. Schoenwaelder, Ed., "Structure of Management Information Version 2 (SMIv2)", STD 58, RFC 2578, April 1999. [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J. Schoenwaelder, Ed., "Textual Conventions for SMIv2", STD 58, RFC 2579, April 1999. [RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder, "Conformance Statements for SMIv2", STD 58, RFC 2580, April 1999. [RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform Resource Identifier (URI): Generic Syntax", STD 66, RFC 3986, January 2005. 7.2 Informative References [RFC3305] Mealling, M. and R. Denenberg, "Report from the Joint W3C/ IETF URI Planning Interest Group: Uniform Resource Identifiers (URIs), URLs, and Uniform Resource Names (URNs): Clarifications and Recommendations", RFC 3305, August 2002. [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, "Introduction and Applicability Statements for Internet- Standard Management Framework", RFC 3410, December 2002. McWalter Expires September 2, 2007 [Page 6] Internet-Draft URI MIB March 2007 Author's Address David McWalter (editor) Data Connection Ltd 100 Church Street Enfield EN2 6BQ United Kingdom Email: dmcw@dataconnection.com McWalter Expires September 2, 2007 [Page 7] Internet-Draft URI MIB March 2007 Intellectual Property Statement 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. Disclaimer of Validity 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. Copyright Statement Copyright (C) The IETF Trust (2007). 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. Acknowledgment Funding for the RFC Editor function is currently provided by the Internet Society. McWalter Expires September 2, 2007 [Page 8]