IETF                                                         D. McWalter
Internet-Draft                                       Data Connection Ltd
Expires: May 25, 2007                                  November 21, 2006


                 Uniform Resource Identifier (URI) MIB
                     draft-mcwalter-uri-mib-01.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 May 25, 2007.

Copyright Notice

   Copyright (C) The IETF Trust (2006).

Abstract

   This MIB module defines textual conventions to represent STD 66
   [RFC3986] 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 May 25, 2007                  [Page 1]


Internet-Draft                   URI MIB                   November 2006


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 May 25, 2007                  [Page 2]


Internet-Draft                   URI MIB                   November 2006


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-MIB DEFINITIONS ::= BEGIN

IMPORTS
    MODULE-IDENTITY, mib-2             FROM SNMPv2-SMI
    TEXTUAL-CONVENTION                 FROM SNMPv2-TC;

langTagMIB MODULE-IDENTITY
    LAST-UPDATED "200611210000Z" -- 21 November 2006
    ORGANIZATION "IETF Operations and Management Area"
    CONTACT-INFO "EMail: ops-area@ietf.org"
    DESCRIPTION
            "This MIB module defines a textual conventions for
            representing BCP 47 language tags."
    REVISION     "200611210000Z" -- 21 November 2006
    DESCRIPTION
           "Initial revision, published as RFC yyyy.

            Copyright (C) The IETF Trust (2006).  The initial version of
            this MIB module was published in RFC yyyy; for full legal
            notices see the RFC itself.  Supplementary information may
            be available at:



McWalter                  Expires May 25, 2007                  [Page 3]


Internet-Draft                   URI MIB                   November 2006


            http://www.ietf.org/copyrights/ianamib.html."
-- 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 "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."
   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."
   REFERENCE "RFC 3986 STD 66 and RFC 3305"
   SYNTAX      OCTET STRING (SIZE (0..255))

Uri1024 ::= TEXTUAL-CONVENTION
   DISPLAY-HINT "1024a"
   STATUS      current



McWalter                  Expires May 25, 2007                  [Page 4]


Internet-Draft                   URI MIB                   November 2006


   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."
   REFERENCE "RFC 3986 STD 66 and RFC 3305"
   SYNTAX      OCTET STRING (SIZE (0..1024))

END


4.  Security Considerations

   This module does not define any management objects.  Instead, it
   defines several textual conventions that may be imported by other MIB
   modules and used for object definitions.

   Whenever using limited-size arrays to implement objects using the
   textual conventions defined by this MIB module, implementers are
   encouraged to check length and bounds on input and memory in order to
   avoid introducing buffer overflow vulnerabilities.  This advice is
   particularly important for URLs, which have frequently been exploited
   in this way in recent years.

   SNMPv1 and SNMPv2c messages are not considered secure.  It is
   recommended that the implementors consider the use of SNMPv3 messages
   and the security features as provided by the SNMPv3 framework.
   Specifically, the use of the User-based Security Model STD 62, RFC
   3414 [RFC3414] and the View-based Access Control Model STD 62, RFC
   3415 [RFC3415] is recommended.

   It is then a customer/user responsibility to ensure that the SNMP
   entity giving access to a MIB is properly configured to give access
   to the objects only to those principals (users) that have legitimate
   rights to indeed GET or SET (change) them.




McWalter                  Expires May 25, 2007                  [Page 5]


Internet-Draft                   URI MIB                   November 2006


5.  IANA Considerations

   URI-MIB should be rooted under the mib-2 subtree.  IANA is requested
   to assign { mib-2 XXX } to the URI-MIB module specified in this
   document.

6.  Acknowledgements

   This module was generated by editing together suggestions from Randy
   Presuhn, Dan Romascanu, Bill Fenner, Juergen Schoenwaelder, and
   others.  The 'author' was in this case more of a 'secretary'.

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, Was Internet-Draft
              draft-fielding-uri-rfc2396bis-07, Current Status STANDARD,
              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,
              draft-mealling-uri-ig-02 (work in progress), Current
              Status INFORMATIONAL, August 2002.

   [RFC3410]  Case, J., Mundy, R., Partain, D., and B. Stewart,
              "Introduction and Applicability Statements for Internet-



McWalter                  Expires May 25, 2007                  [Page 6]


Internet-Draft                   URI MIB                   November 2006


              Standard Management Framework", RFC 3410, December 2002.

   [RFC3414]  Blumenthal, U. and B. Wijnen, "User-based Security Model
              (USM) for version 3 of the Simple Network Management
              Protocol (SNMPv3)", STD 62, RFC 3414,
              draft-ietf-snmpv3-usm-v2-rfc2574bis-01 (work in progress),
              Current Status STANDARD, December 2002.

   [RFC3415]  Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based
              Access Control Model (VACM) for the Simple Network
              Management Protocol (SNMP)", STD 62, RFC 3415,
              draft-ietf-snmpv3-vacm-v2-01 (work in progress), Current
              Status STANDARD, December 2002.


Author's Address

   David McWalter
   Data Connection Ltd
   100 Church Street
   Enfield  EN2 6BQ
   United Kingdom

   Email: dmcw@dataconnection.com



























McWalter                  Expires May 25, 2007                  [Page 7]


Internet-Draft                   URI MIB                   November 2006


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 (2006).  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 May 25, 2007                  [Page 8]