1 LANGTAG-TC-MIB DEFINITIONS ::= BEGIN
4 MODULE-IDENTITY, mib-2 FROM SNMPv2-SMI -- [RFC2578]
5 TEXTUAL-CONVENTION FROM SNMPv2-TC; -- [RFC2579]
7 langTagTcMIB MODULE-IDENTITY
8 LAST-UPDATED "200711090000Z" -- 9 November 2007
9 ORGANIZATION "IETF Operations and Management (OPS) Area"
10 CONTACT-INFO "EMail: ops-area@ietf.org
11 Home page: http://www.ops.ietf.org/"
13 "This MIB module defines a textual convention for
14 representing BCP 47 language tags."
15 REVISION "200711090000Z" -- 9 November 2007
17 "Initial revision, published as RFC 5131.
19 Copyright (C) The IETF Trust (2007). This version of this
20 MIB module is part of RFC 5131; see the RFC itself for full
24 LangTag ::= TEXTUAL-CONVENTION
28 "A language tag, constructed in accordance with BCP 47.
30 Only lowercase characters are allowed. The purpose of this
31 restriction is to provide unique language tags for use as
32 indexes. BCP 47 recommends case conventions for user
33 interfaces, but objects using this TEXTUAL-CONVENTION MUST
36 Values MUST be well-formed language tags, in conformance
37 with the definition of well-formed tags in BCP 47. An
38 implementation MAY further limit the values it accepts to
39 those permitted by a 'validating' processor, as defined in
42 In theory, BCP 47 language tags are of unlimited length.
43 The language tag described in this TEXTUAL-CONVENTION is of
44 limited length. The analysis of language tag lengths in BCP
45 47 confirms that this limit will not pose a problem in
46 practice. In particular, this length is greater than the
50 minimum requirements set out in Section 4.3.1.
52 A zero-length language tag is not a valid language tag.
53 This can be used to express 'language tag absent' where
54 required, for example, when used as an index field."
55 REFERENCE "RFC 4646 BCP 47"
56 SYNTAX OCTET STRING (SIZE (0 | 2..63))