IETF D. McWalter Internet-Draft Data Connection Ltd Expires: May 17, 2007 November 13, 2006 Language Tag MIB draft-mcwalter-langtag-mib-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 May 17, 2007. Copyright Notice Copyright (C) The Internet Society (2006). Abstract This MIB module defines a textual convention to represent BCP 47 [RFC4646] language tags. The intent is that this textual convention will be imported and used in MIB modules that would otherwise define their own representation. McWalter Expires May 17, 2007 [Page 1] Internet-Draft LANGTAG MIB November 2006 Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. The Internet-Standard Management Framework . . . . . . . . . . 3 3. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 3 4. Security Considerations . . . . . . . . . . . . . . . . . . . 4 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5 6. Notes to the RFC editor . . . . . . . . . . . . . . . . . . . 5 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 5 8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 6 8.1 Normative References . . . . . . . . . . . . . . . . . . . 6 8.2 Informative References . . . . . . . . . . . . . . . . . . 6 Author's Address . . . . . . . . . . . . . . . . . . . . . . . 7 Intellectual Property and Copyright Statements . . . . . . . . 8 McWalter Expires May 17, 2007 [Page 2] Internet-Draft LANGTAG 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 BCP 47 [RFC4646] language tags. This document is part of work in progress to obsolete RFC 2932 [RFC2932]. RFC 2932 defined a LanguageTag textual convention, but did so at an inappropriately scope; namely in a MIB module specific to IPv4 multicast routing. This draft aims to correct the structure of the MIB by placing this textual convention in a dedicated module that can be included without other dependencies. 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 LANGTAG-MIB DEFINITIONS ::= BEGIN IMPORTS MODULE-IDENTITY, mib-2 FROM SNMPv2-SMI TEXTUAL-CONVENTION FROM SNMPv2-TC; langTagMIB MODULE-IDENTITY LAST-UPDATED "200611130000Z" -- 13 November 2006 ORGANIZATION "IETF Operations and Management Area" CONTACT-INFO "EMail: ops-area@ietf.org" DESCRIPTION McWalter Expires May 17, 2007 [Page 3] Internet-Draft LANGTAG MIB November 2006 "This MIB module defines a textual conventions for representing BCP 47 language tags." REVISION "200611130000Z" -- 13 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: 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 LanguageTag ::= TEXTUAL-CONVENTION DISPLAY-HINT "100a" STATUS current DESCRIPTION "A language tag, constructed in accordance with BCP 47. Only lowercase characters are allowed. The purpose of this restriction is to provide unique language tags for use as indexes. BCP 47 recommends case conventions for user interfaces, but objects using this textual convention MUST use only lowercase. Values MUST be well-formed language tags, in conformance with the definition of well-formed tags in BCP 47. An implementation MAY further limit the values it accepts to those permitted by a 'validating' processor, as defined in BCP 47. In theory, BCP 47 language tags are of unlimited length. This language tag is of limited length. The analysis of language tag lengths in BCP 47 confirms that this limit will not pose a problem in practice." REFERENCE "RFC 4646 BCP 47" SYNTAX OCTET STRING (SIZE (1..100)) END 4. Security Considerations Whenever using limited-size arrays to implement objects such as those defined by this MIB module, implementers are encouraged to check length and bounds on input and memory in order to avoid introducing McWalter Expires May 17, 2007 [Page 4] Internet-Draft LANGTAG MIB November 2006 buffer overflow vulnerabilities." SNMP versions prior to SNMPv3 did not include adequate security. Even if the network itself is secure (for example by using IPSec), even then, there is no control as to who on the secure network is allowed to access and GET/SET (read/change/create/delete) the objects in this MIB module. It is RECOMMENDED that implementers consider the security features as provided by the SNMPv3 framework (see [RFC3410], section 8), including full support for the SNMPv3 cryptographic mechanisms (for authentication and privacy). Further, deployment of SNMP versions prior to SNMPv3 is NOT RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to enable cryptographic security. It is then a customer/operator responsibility to ensure that the SNMP entity giving access to an instance of this MIB module is properly configured to give access to the objects only to those principals (users) that have legitimate rights to indeed GET or SET (change/create/delete) them. 5. IANA Considerations LANGTAG-MIB should be rooted under the mib-2 subtree. IANA is requested to assign { mib-2 XXX } to the LANGTAG-MIB module specified in this document. 6. Notes to the RFC editor This document should be published simultaneously with IPMCAST-MIB [I-D.ietf-mboned-ip-mcast-mib]. This is because LANGTAG-MIB replaces the LanguageTag textual convention that is already present in RFC 2932, which will be obsoleted by the publication of IPMCAST-MIB. Normative references between LANGTAG-MIB and IPMCAST-MIB confirm this interdependency in publishing schedule. After publication has occurred, there shall be no dependence from LANGTAG-MIB to IPMCAST- MIB. The normative reference from this draft to IPMCAST-MIB should be removed at that time. The normative reference from IPMCAST-MIB to this draft should remain. 7. Acknowledgements This MIB module is a reworking of existing material from RFC 2932. This module was generated by editing together suggestions from Randy McWalter Expires May 17, 2007 [Page 5] Internet-Draft LANGTAG MIB November 2006 Presuhn, Dan Romascanu, Bill Fenner, Jeurgen Schoenwaelder, and others. The 'author' was in this case more of a 'secretary'." 8. References 8.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. [RFC4646] Phillips, A. and M. Davis, "Tags for Identifying Languages", BCP 47, RFC 4646, draft-ietf-ltru-registry-14 (work in progress), Current Status BEST CURRENT PRACTICE, September 2006. Note from RFC Editor: announcement message (11/05) said this doc should be published at same time as because together they obsolete bcp 47. is not here yet. [I-D.ietf-mboned-ip-mcast-mib] McWalter, D., "IP Multicast MIB", draft-ietf-mboned-ip-mcast-mib-04 (work in progress), November 2006. 8.2 Informative References [RFC2434] Narten, T. and H. Alvestrand, "Guidelines for Writing an IANA Considerations Section in RFCs", BCP 26, RFC 2434, October 1998. [RFC2932] McCloghrie, K., Farinacci, D., and D. Thaler, "IPv4 Multicast Routing MIB", RFC 2932, October 2000. [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, "Introduction and Applicability Statements for Internet- McWalter Expires May 17, 2007 [Page 6] Internet-Draft LANGTAG MIB November 2006 Standard Management Framework", RFC 3410, December 2002. [RFC3692] Narten, T., "Assigning Experimental and Testing Numbers Considered Useful", BCP 82, RFC 3692, draft-narten-iana-experimental-allocations-05 (work in progress), Current Status BEST CURRENT PRACTICE, January 2004. Author's Address David McWalter Data Connection Ltd 100 Church Street Enfield EN2 6BQ United Kingdom Email: dmcw@dataconnection.com McWalter Expires May 17, 2007 [Page 7] Internet-Draft LANGTAG 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 17, 2007 [Page 8]