From 98a672123c7872f6b9b75a9a2b6bb3aea504de6a Mon Sep 17 00:00:00 2001 From: David Leutgeb Date: Tue, 5 Dec 2023 12:25:34 +0100 Subject: Initial commit --- MIBS/nokia/LANGTAG-TC-MIB | 55 +++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 55 insertions(+) create mode 100644 MIBS/nokia/LANGTAG-TC-MIB (limited to 'MIBS/nokia/LANGTAG-TC-MIB') diff --git a/MIBS/nokia/LANGTAG-TC-MIB b/MIBS/nokia/LANGTAG-TC-MIB new file mode 100644 index 0000000..fcabfa3 --- /dev/null +++ b/MIBS/nokia/LANGTAG-TC-MIB @@ -0,0 +1,55 @@ +LANGTAG-TC-MIB DEFINITIONS ::= BEGIN + +IMPORTS + MODULE-IDENTITY, mib-2 FROM SNMPv2-SMI -- [RFC2578] + TEXTUAL-CONVENTION FROM SNMPv2-TC; -- [RFC2579] + +langTagTcMIB MODULE-IDENTITY + LAST-UPDATED "200711090000Z" -- 9 November 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 a textual convention for + representing BCP 47 language tags." + REVISION "200711090000Z" -- 9 November 2007 + DESCRIPTION + "Initial revision, published as RFC 5131. + + Copyright (C) The IETF Trust (2007). This version of this + MIB module is part of RFC 5131; see the RFC itself for full + legal notices." + ::= { mib-2 165 } + +LangTag ::= TEXTUAL-CONVENTION + DISPLAY-HINT "1a" + 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. + The language tag described in this TEXTUAL-CONVENTION is of + limited length. The analysis of language tag lengths in BCP + 47 confirms that this limit will not pose a problem in + practice. In particular, this length is greater than the + minimum requirements set out in Section 4.3.1. + + A zero-length language tag is not a valid language tag. + This can be used to express 'language tag absent' where + required, for example, when used as an index field." + REFERENCE "RFC 4646 BCP 47" + SYNTAX OCTET STRING (SIZE (0 | 2..63)) + +END -- cgit v1.2.3