< draft-mcwalter-langtag-mib-02.txt		draft-mcwalter-langtag-mib-03.txt >
	IETF D. McWalter, Ed.		IETF D. McWalter, Ed.
	Internet-Draft Data Connection Ltd		Internet-Draft Data Connection Ltd
	Proposed Status: Standards Track March 1, 2007		Proposed Status: Standards Track March 20, 2007
	Expires: September 2, 2007		Expires: September 21, 2007
	Language Tag MIB		A MIB Textual Convention for Language Tags
	draft-mcwalter-langtag-mib-02.txt		draft-mcwalter-langtag-mib-03.txt
	Status of this Memo		Status of this Memo
	By submitting this Internet-Draft, each author represents that any		By submitting this Internet-Draft, each author represents that any
	applicable patent or other IPR claims of which he or she is aware		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		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.		aware will be disclosed, in accordance with Section 6 of BCP 79.
	Internet-Drafts are working documents of the Internet Engineering		Internet-Drafts are working documents of the Internet Engineering
	Task Force (IETF), its areas, and its working groups. Note that		Task Force (IETF), its areas, and its working groups. Note that
	skipping to change at page 1, line 34 ¶		skipping to change at page 1, line 34 ¶
	and may be updated, replaced, or obsoleted by other documents at any		and may be updated, replaced, or obsoleted by other documents at any
	time. It is inappropriate to use Internet-Drafts as reference		time. It is inappropriate to use Internet-Drafts as reference
	material or to cite them other than as "work in progress."		material or to cite them other than as "work in progress."
	The list of current Internet-Drafts can be accessed at		The list of current Internet-Drafts can be accessed at
	http://www.ietf.org/ietf/1id-abstracts.txt.		http://www.ietf.org/ietf/1id-abstracts.txt.
	The list of Internet-Draft Shadow Directories can be accessed at		The list of Internet-Draft Shadow Directories can be accessed at
	http://www.ietf.org/shadow.html.		http://www.ietf.org/shadow.html.
	This Internet-Draft will expire on September 2, 2007.		This Internet-Draft will expire on September 21, 2007.
	Copyright Notice		Copyright Notice
	Copyright (C) The IETF Trust (2007).		Copyright (C) The IETF Trust (2007).
	Abstract		Abstract
	This MIB module defines a textual convention to represent BCP 47		This MIB module defines a textual convention to represent BCP 47
	language tags. The intent is that this textual convention will be		language tags. The intent is that this textual convention will be
	imported and used in MIB modules that would otherwise define their		imported and used in MIB modules that would otherwise define their
	own representation.		own representation.
	Table of Contents		Table of Contents
	1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3		1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
	2. The Internet-Standard Management Framework . . . . . . . . . . 3		2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3
	3. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 3		3. The Internet-Standard Management Framework . . . . . . . . . . 3
	4. Security Considerations . . . . . . . . . . . . . . . . . . . 4		4. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 4
	5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5		5. Security Considerations . . . . . . . . . . . . . . . . . . . 5
	6. Notes to the RFC editor - remove before publication . . . . . 5		6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5
	7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 5		7. Notes to the RFC editor - remove before publication . . . . . 5
	8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 5		8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 5
	8.1 Normative References . . . . . . . . . . . . . . . . . . . 5		9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 6
	8.2 Informative References . . . . . . . . . . . . . . . . . . 6		9.1 Normative References . . . . . . . . . . . . . . . . . . . 6
			9.2 Informative References . . . . . . . . . . . . . . . . . . 6
	Author's Address . . . . . . . . . . . . . . . . . . . . . . . 6		Author's Address . . . . . . . . . . . . . . . . . . . . . . . 6
	Intellectual Property and Copyright Statements . . . . . . . . 7		Intellectual Property and Copyright Statements . . . . . . . . 7
	1. Introduction		1. Introduction
	This memo defines a portion of the Management Information Base (MIB)		This memo defines a portion of the Management Information Base (MIB)
	for use with network management protocols in the Internet community.		for use with network management protocols in the Internet community.
	It defines a textual convention to represent BCP 47 [RFC4646]		It defines a textual convention to represent BCP 47 [RFC4646]
	language tags.		language tags.
	The LangTag textual convention defined by this RFC replaces the		The LangTag textual convention defined by this RFC replaces the
	similar LanguageTag textual convention defined by RFC 2932 [RFC2932].		similar LanguageTag textual convention defined by RFC 2932 [RFC2932].
			The old LanguageTag textual convention is used by some existing MIB
			modules. New MIB modules should use the LangTag textual convention,
			which has been created (and is to be preferred) for the following
			reasons:
			o Its syntax description is current, and is more comprehensive.
			o It is short enough to use as an index object without subtyping,
			yet is of adequate length to represent any language tag in
			practice.
			o It is provided in a dedicated MIB module to simplify module
			dependencies.
			It is not possible to apply changes in syntax and length to an
			existing textual convention. This is why the creation of a new
			textual convention with a new name was necessary.
			2. Terminology
	The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",		The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
	"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this		"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
	document are to be interpreted as described in RFC 2119 [RFC2119].		document are to be interpreted as described in RFC 2119 [RFC2119].
	2. The Internet-Standard Management Framework		3. The Internet-Standard Management Framework
	For a detailed overview of the documents that describe the current		For a detailed overview of the documents that describe the current
	Internet-Standard Management Framework, please refer to section 7 of		Internet-Standard Management Framework, please refer to section 7 of
	RFC 3410 [RFC3410].		RFC 3410 [RFC3410].
	Managed objects are accessed via a virtual information store, termed		Managed objects are accessed via a virtual information store, termed
	the Management Information Base or MIB. MIB objects are generally		the Management Information Base or MIB. MIB objects are generally
	accessed through the Simple Network Management Protocol (SNMP).		accessed through the Simple Network Management Protocol (SNMP).
	Objects in the MIB are defined using the mechanisms defined in the		Objects in the MIB are defined using the mechanisms defined in the
	Structure of Management Information (SMI). This memo specifies a MIB		Structure of Management Information (SMI). This memo specifies a MIB
	module that is compliant to the SMIv2, which is described in STD 58,		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		RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580
	[RFC2580].		[RFC2580].
	3. Definitions		4. Definitions
	LANGTAG-TC-MIB DEFINITIONS ::= BEGIN		LANGTAG-TC-MIB DEFINITIONS ::= BEGIN
	IMPORTS		IMPORTS
	MODULE-IDENTITY, mib-2 FROM SNMPv2-SMI -- [RFC2578]		MODULE-IDENTITY, mib-2 FROM SNMPv2-SMI -- [RFC2578]
	TEXTUAL-CONVENTION FROM SNMPv2-TC; -- [RFC2579]		TEXTUAL-CONVENTION FROM SNMPv2-TC; -- [RFC2579]
	langTagTcMIB MODULE-IDENTITY		langTagTcMIB MODULE-IDENTITY
	LAST-UPDATED "200703010000Z" -- 1 March 2007		LAST-UPDATED "200703200000Z" -- 20 March 2007
	ORGANIZATION "IETF Operations and Management (OPS) Area"		ORGANIZATION "IETF Operations and Management (OPS) Area"
	CONTACT-INFO "EMail: ops-area@ietf.org		CONTACT-INFO "EMail: ops-area@ietf.org
	Home page: http://www.ops.ietf.org/"		Home page: http://www.ops.ietf.org/"
	DESCRIPTION		DESCRIPTION
	"This MIB module defines a textual convention for		"This MIB module defines a textual convention for
	representing BCP 47 language tags."		representing BCP 47 language tags."
	REVISION "200703010000Z" -- 1 March 2007		REVISION "200703200000Z" -- 20 March 2007
	DESCRIPTION		DESCRIPTION
	"Initial revision, published as RFC yyyy.		"Initial revision, published as RFC yyyy.
	Copyright (C) The IETF Trust (2007). This version of this		Copyright (C) The IETF Trust (2007). This version of this
	MIB module is part of RFC yyyy; see the RFC itself for full		MIB module is part of RFC yyyy; see the RFC itself for full
	legal notices."		legal notices."
	-- RFC Ed.: replace yyyy with actual RFC number & remove this note		-- RFC Ed.: replace yyyy with actual RFC number & remove this note
	::= { mib-2 XXX }		::= { mib-2 XXX }
	-- RFC Ed.: replace XXX with IANA-assigned number & remove this note		-- RFC Ed.: replace XXX with IANA-assigned number & remove this note
	skipping to change at page 4, line 31 ¶		skipping to change at page 4, line 51 ¶
	interfaces, but objects using this textual convention MUST		interfaces, but objects using this textual convention MUST
	use only lowercase.		use only lowercase.
	Values MUST be well-formed language tags, in conformance		Values MUST be well-formed language tags, in conformance
	with the definition of well-formed tags in BCP 47. An		with the definition of well-formed tags in BCP 47. An
	implementation MAY further limit the values it accepts to		implementation MAY further limit the values it accepts to
	those permitted by a 'validating' processor, as defined in		those permitted by a 'validating' processor, as defined in
	BCP 47.		BCP 47.
	In theory, BCP 47 language tags are of unlimited length.		In theory, BCP 47 language tags are of unlimited length.
	This language tag is of limited length. The analysis of		The language tag described in this TC is of limited length.
	language tag lengths in BCP 47 confirms that this limit		The analysis of language tag lengths in BCP 47 confirms that
	will not pose a problem in practice. In particular, this		this limit will not pose a problem in practice. In
	length is greater than the minimum requirements set out in		particular, this length is greater than the minimum
	section 4.3.1.		requirements set out in section 4.3.1.
	A zero-length language tag is not a valid language tag.		A zero-length language tag is not a valid language tag.
	This can be used to express 'language tag absent' where		This can be used to express 'language tag absent' where
	required, for example when used as an index field."		required, for example when used as an index field."
	REFERENCE "RFC 4646 BCP 47"		REFERENCE "RFC 4646 BCP 47"
	SYNTAX OCTET STRING (SIZE (0 | 2..63))		SYNTAX OCTET STRING (SIZE (0 | 2..63))
	END		END
	4. Security Considerations		5. Security Considerations
	This MIB module does not define any management objects. Instead, it		This MIB module does not define any management objects. Instead, it
	defines a textual convention that may be imported by other MIB		defines a textual convention that may be imported by other MIB
	modules and used for object definitions.		modules and used for object definitions.
	Meaningful security considerations can only be written in the MIB		Meaningful security considerations can only be written in the MIB
	modules that define management objects. This document therefore has		modules that define management objects. This document therefore has
	no impact on the security of the Internet.		no impact on the security of the Internet.
	5. IANA Considerations		6. IANA Considerations
	LANGTAG-TC-MIB should be rooted under the mib-2 subtree. IANA is		LANGTAG-TC-MIB should be rooted under the mib-2 subtree. IANA is
	requested to assign { mib-2 XXX } to the LANGTAG-TC-MIB module		requested to assign { mib-2 XXX } to the LANGTAG-TC-MIB module
	specified in this document.		specified in this document.
	6. Notes to the RFC editor - remove before publication		7. Notes to the RFC editor - remove before publication
	This document should be published simultaneously with IPMCAST-MIB		This document should be published simultaneously with IPMCAST-MIB
	(draft-ietf-mboned-ip-mcast-mib).		(draft-ietf-mboned-ip-mcast-mib).
	This is because LANGTAG-MIB replaces the LanguageTag textual		This is because LANGTAG-MIB replaces the LanguageTag textual
	convention that is already present in RFC 2932, which will be		convention that is already present in RFC 2932, which will be
	obsoleted by the publication of IPMCAST-MIB.		obsoleted by the publication of IPMCAST-MIB.
	7. Acknowledgements		8. Acknowledgements
	This MIB module is a reworking of existing material from RFC 2932.		This MIB module is a reworking of existing material from RFC 2932.
	This module was generated by editing together contributions from		This module was generated by editing together contributions from
	Randy Presuhn, Dan Romascanu, Bill Fenner, Juergen Schoenwaelder,		Randy Presuhn, Dan Romascanu, Bill Fenner, Juergen Schoenwaelder,
	Bert Wijnen, Doug Ewell, and Ira McDonald.		Bert Wijnen, Doug Ewell, and Ira McDonald.
	8. References		9. References
			9.1 Normative References
	8.1 Normative References
	[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate		[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
	Requirement Levels", BCP 14, RFC 2119, March 1997.		Requirement Levels", BCP 14, RFC 2119, March 1997.
	[RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J.		[RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J.
	Schoenwaelder, Ed., "Structure of Management Information		Schoenwaelder, Ed., "Structure of Management Information
	Version 2 (SMIv2)", STD 58, RFC 2578, April 1999.		Version 2 (SMIv2)", STD 58, RFC 2578, April 1999.
	[RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J.		[RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J.
	Schoenwaelder, Ed., "Textual Conventions for SMIv2",		Schoenwaelder, Ed., "Textual Conventions for SMIv2",
	STD 58, RFC 2579, April 1999.		STD 58, RFC 2579, April 1999.
	[RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder,		[RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder,
	"Conformance Statements for SMIv2", STD 58, RFC 2580,		"Conformance Statements for SMIv2", STD 58, RFC 2580,
	April 1999.		April 1999.
	[RFC4646] Phillips, A. and M. Davis, "Tags for Identifying		[RFC4646] Phillips, A. and M. Davis, "Tags for Identifying
	Languages", BCP 47, RFC 4646, September 2006.		Languages", BCP 47, RFC 4646, September 2006.
	8.2 Informative References		9.2 Informative References
	[RFC2932] McCloghrie, K., Farinacci, D., and D. Thaler, "IPv4		[RFC2932] McCloghrie, K., Farinacci, D., and D. Thaler, "IPv4
	Multicast Routing MIB", RFC 2932, October 2000.		Multicast Routing MIB", RFC 2932, October 2000.
	[RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart,		[RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart,
	"Introduction and Applicability Statements for Internet-		"Introduction and Applicability Statements for Internet-
	Standard Management Framework", RFC 3410, December 2002.		Standard Management Framework", RFC 3410, December 2002.
	Author's Address		Author's Address
End of changes. 16 change blocks.
	31 lines changed or deleted		51 lines changed or added
This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/