idnits 2.17.1 draft-mcwalter-langtag-mib-02.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** It looks like you're using RFC 3978 boilerplate. You should update this to the boilerplate described in the IETF Trust License Policy document (see https://trustee.ietf.org/license-info), which is required now. -- Found old boilerplate from RFC 3978, Section 5.1 on line 15. -- Found old boilerplate from RFC 3978, Section 5.5, updated by RFC 4748 on line 256. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 233. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 240. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 246. ** The document seems to lack an RFC 3978 Section 5.4 Reference to BCP 78. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- == No 'Intended status' indicated for this document; assuming Proposed Standard Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust Copyright Line does not match the current year -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (March 1, 2007) is 6237 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) ** Obsolete normative reference: RFC 4646 (Obsoleted by RFC 5646) -- Obsolete informational reference (is this intentional?): RFC 2932 (Obsoleted by RFC 5132) Summary: 3 errors (**), 0 flaws (~~), 2 warnings (==), 8 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 IETF D. McWalter, Ed. 3 Internet-Draft Data Connection Ltd 4 Proposed Status: Standards Track March 1, 2007 5 Expires: September 2, 2007 7 Language Tag MIB 8 draft-mcwalter-langtag-mib-02.txt 10 Status of this Memo 12 By submitting this Internet-Draft, each author represents that any 13 applicable patent or other IPR claims of which he or she is aware 14 have been or will be disclosed, and any of which he or she becomes 15 aware will be disclosed, in accordance with Section 6 of BCP 79. 17 Internet-Drafts are working documents of the Internet Engineering 18 Task Force (IETF), its areas, and its working groups. Note that 19 other groups may also distribute working documents as Internet- 20 Drafts. 22 Internet-Drafts are draft documents valid for a maximum of six months 23 and may be updated, replaced, or obsoleted by other documents at any 24 time. It is inappropriate to use Internet-Drafts as reference 25 material or to cite them other than as "work in progress." 27 The list of current Internet-Drafts can be accessed at 28 http://www.ietf.org/ietf/1id-abstracts.txt. 30 The list of Internet-Draft Shadow Directories can be accessed at 31 http://www.ietf.org/shadow.html. 33 This Internet-Draft will expire on September 2, 2007. 35 Copyright Notice 37 Copyright (C) The IETF Trust (2007). 39 Abstract 41 This MIB module defines a textual convention to represent BCP 47 42 language tags. The intent is that this textual convention will be 43 imported and used in MIB modules that would otherwise define their 44 own representation. 46 Table of Contents 48 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 49 2. The Internet-Standard Management Framework . . . . . . . . . . 3 50 3. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 3 51 4. Security Considerations . . . . . . . . . . . . . . . . . . . 4 52 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5 53 6. Notes to the RFC editor - remove before publication . . . . . 5 54 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 5 55 8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 5 56 8.1 Normative References . . . . . . . . . . . . . . . . . . . 5 57 8.2 Informative References . . . . . . . . . . . . . . . . . . 6 58 Author's Address . . . . . . . . . . . . . . . . . . . . . . . 6 59 Intellectual Property and Copyright Statements . . . . . . . . 7 61 1. Introduction 63 This memo defines a portion of the Management Information Base (MIB) 64 for use with network management protocols in the Internet community. 65 It defines a textual convention to represent BCP 47 [RFC4646] 66 language tags. 68 The LangTag textual convention defined by this RFC replaces the 69 similar LanguageTag textual convention defined by RFC 2932 [RFC2932]. 71 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 72 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 73 document are to be interpreted as described in RFC 2119 [RFC2119]. 75 2. The Internet-Standard Management Framework 77 For a detailed overview of the documents that describe the current 78 Internet-Standard Management Framework, please refer to section 7 of 79 RFC 3410 [RFC3410]. 81 Managed objects are accessed via a virtual information store, termed 82 the Management Information Base or MIB. MIB objects are generally 83 accessed through the Simple Network Management Protocol (SNMP). 84 Objects in the MIB are defined using the mechanisms defined in the 85 Structure of Management Information (SMI). This memo specifies a MIB 86 module that is compliant to the SMIv2, which is described in STD 58, 87 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 88 [RFC2580]. 90 3. Definitions 92 LANGTAG-TC-MIB DEFINITIONS ::= BEGIN 94 IMPORTS 95 MODULE-IDENTITY, mib-2 FROM SNMPv2-SMI -- [RFC2578] 96 TEXTUAL-CONVENTION FROM SNMPv2-TC; -- [RFC2579] 98 langTagTcMIB MODULE-IDENTITY 99 LAST-UPDATED "200703010000Z" -- 1 March 2007 100 ORGANIZATION "IETF Operations and Management (OPS) Area" 101 CONTACT-INFO "EMail: ops-area@ietf.org 102 Home page: http://www.ops.ietf.org/" 103 DESCRIPTION 104 "This MIB module defines a textual convention for 105 representing BCP 47 language tags." 106 REVISION "200703010000Z" -- 1 March 2007 107 DESCRIPTION 108 "Initial revision, published as RFC yyyy. 110 Copyright (C) The IETF Trust (2007). This version of this 111 MIB module is part of RFC yyyy; see the RFC itself for full 112 legal notices." 113 -- RFC Ed.: replace yyyy with actual RFC number & remove this note 114 ::= { mib-2 XXX } 115 -- RFC Ed.: replace XXX with IANA-assigned number & remove this note 117 LangTag ::= TEXTUAL-CONVENTION 118 DISPLAY-HINT "1a" 119 STATUS current 120 DESCRIPTION 121 "A language tag, constructed in accordance with BCP 47. 123 Only lowercase characters are allowed. The purpose of this 124 restriction is to provide unique language tags for use as 125 indexes. BCP 47 recommends case conventions for user 126 interfaces, but objects using this textual convention MUST 127 use only lowercase. 129 Values MUST be well-formed language tags, in conformance 130 with the definition of well-formed tags in BCP 47. An 131 implementation MAY further limit the values it accepts to 132 those permitted by a 'validating' processor, as defined in 133 BCP 47. 135 In theory, BCP 47 language tags are of unlimited length. 136 This language tag is of limited length. The analysis of 137 language tag lengths in BCP 47 confirms that this limit 138 will not pose a problem in practice. In particular, this 139 length is greater than the minimum requirements set out in 140 section 4.3.1. 142 A zero-length language tag is not a valid language tag. 143 This can be used to express 'language tag absent' where 144 required, for example when used as an index field." 145 REFERENCE "RFC 4646 BCP 47" 146 SYNTAX OCTET STRING (SIZE (0 | 2..63)) 148 END 150 4. Security Considerations 152 This MIB module does not define any management objects. Instead, it 153 defines a textual convention that may be imported by other MIB 154 modules and used for object definitions. 156 Meaningful security considerations can only be written in the MIB 157 modules that define management objects. This document therefore has 158 no impact on the security of the Internet. 160 5. IANA Considerations 162 LANGTAG-TC-MIB should be rooted under the mib-2 subtree. IANA is 163 requested to assign { mib-2 XXX } to the LANGTAG-TC-MIB module 164 specified in this document. 166 6. Notes to the RFC editor - remove before publication 168 This document should be published simultaneously with IPMCAST-MIB 169 (draft-ietf-mboned-ip-mcast-mib). 171 This is because LANGTAG-MIB replaces the LanguageTag textual 172 convention that is already present in RFC 2932, which will be 173 obsoleted by the publication of IPMCAST-MIB. 175 7. Acknowledgements 177 This MIB module is a reworking of existing material from RFC 2932. 179 This module was generated by editing together contributions from 180 Randy Presuhn, Dan Romascanu, Bill Fenner, Juergen Schoenwaelder, 181 Bert Wijnen, Doug Ewell, and Ira McDonald. 183 8. References 185 8.1 Normative References 187 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 188 Requirement Levels", BCP 14, RFC 2119, March 1997. 190 [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J. 191 Schoenwaelder, Ed., "Structure of Management Information 192 Version 2 (SMIv2)", STD 58, RFC 2578, April 1999. 194 [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J. 195 Schoenwaelder, Ed., "Textual Conventions for SMIv2", 196 STD 58, RFC 2579, April 1999. 198 [RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder, 199 "Conformance Statements for SMIv2", STD 58, RFC 2580, 200 April 1999. 202 [RFC4646] Phillips, A. and M. Davis, "Tags for Identifying 203 Languages", BCP 47, RFC 4646, September 2006. 205 8.2 Informative References 207 [RFC2932] McCloghrie, K., Farinacci, D., and D. Thaler, "IPv4 208 Multicast Routing MIB", RFC 2932, October 2000. 210 [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, 211 "Introduction and Applicability Statements for Internet- 212 Standard Management Framework", RFC 3410, December 2002. 214 Author's Address 216 David McWalter (editor) 217 Data Connection Ltd 218 100 Church Street 219 Enfield EN2 6BQ 220 United Kingdom 222 Email: dmcw@dataconnection.com 224 Intellectual Property Statement 226 The IETF takes no position regarding the validity or scope of any 227 Intellectual Property Rights or other rights that might be claimed to 228 pertain to the implementation or use of the technology described in 229 this document or the extent to which any license under such rights 230 might or might not be available; nor does it represent that it has 231 made any independent effort to identify any such rights. Information 232 on the procedures with respect to rights in RFC documents can be 233 found in BCP 78 and BCP 79. 235 Copies of IPR disclosures made to the IETF Secretariat and any 236 assurances of licenses to be made available, or the result of an 237 attempt made to obtain a general license or permission for the use of 238 such proprietary rights by implementers or users of this 239 specification can be obtained from the IETF on-line IPR repository at 240 http://www.ietf.org/ipr. 242 The IETF invites any interested party to bring to its attention any 243 copyrights, patents or patent applications, or other proprietary 244 rights that may cover technology that may be required to implement 245 this standard. Please address the information to the IETF at 246 ietf-ipr@ietf.org. 248 Disclaimer of Validity 250 This document and the information contained herein are provided on an 251 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS 252 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND 253 THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS 254 OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF 255 THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 256 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 258 Copyright Statement 260 Copyright (C) The IETF Trust (2007). This document is subject to the 261 rights, licenses and restrictions contained in BCP 78, and except as 262 set forth therein, the authors retain all their rights. 264 Acknowledgment 266 Funding for the RFC Editor function is currently provided by the 267 Internet Society.