Translation of Structure of Management Information Version 2 (SMIv2) MIB Modules to YANG Modules
RFC 6643
Document Type RFC - Proposed Standard (July 2012; Errata)
Last updated 2016-08-25
Replaces draft-schoenw-netmod-smi-yang
Stream IETF
Formats plain text pdf html bibtex
Stream WG state WG Document
Document shepherd No shepherd assigned
IESG IESG state RFC 6643 (Proposed Standard)
Consensus Boilerplate Unknown
Telechat date
Responsible AD Benoit Claise
IESG note David Kessens is the Document Shepherd
Send notices to (None)
Email authors IPR References Referenced by Nits 
Internet Engineering Task Force (IETF)                  J. Schoenwaelder
Request for Comments: 6643                             Jacobs University
Category: Standards Track                                      July 2012
ISSN: 2070-1721

  Translation of Structure of Management Information Version 2 (SMIv2)
                      MIB Modules to YANG Modules

Abstract

   YANG is a data modeling language used to model configuration and
   state data manipulated by the Network Configuration Protocol
   (NETCONF), NETCONF remote procedure calls, and NETCONF notifications.
   The Structure of Management Information (SMIv2) defines fundamental
   data types, an object model, and the rules for writing and revising
   MIB modules for use with the Simple Network Management Protocol
   (SNMP).  This document defines a translation of SMIv2 MIB modules
   into YANG modules, enabling read-only (config false) access to data
   objects defined in SMIv2 MIB modules via NETCONF.

Status of This Memo

   This is an Internet Standards Track document.

   This document is a product of the Internet Engineering Task Force
   (IETF).  It represents the consensus of the IETF community.  It has
   received public review and has been approved for publication by the
   Internet Engineering Steering Group (IESG).  Further information on
   Internet Standards is available in Section 2 of RFC 5741.

   Information about the current status of this document, any errata,
   and how to provide feedback on it may be obtained at
   http://www.rfc-editor.org/info/rfc6643.

Schoenwaelder                Standards Track                    [Page 1]
RFC 6643              Translation of SMIv2 to YANG             July 2012

Copyright Notice

   Copyright (c) 2012 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

   This document may contain material from IETF Documents or IETF
   Contributions published or made publicly available before November
   10, 2008.  The person(s) controlling the copyright in some of this
   material may not have granted the IETF Trust the right to allow
   modifications of such material outside the IETF Standards Process.
   Without obtaining an adequate license from the person(s) controlling
   the copyright in such materials, this document may not be modified
   outside the IETF Standards Process, and derivative works of it may
   not be created outside the IETF Standards Process, except to format
   it for publication as an RFC or to translate it into languages other
   than English.

Schoenwaelder                Standards Track                    [Page 2]
RFC 6643              Translation of SMIv2 to YANG             July 2012

Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  4
   2.  Mapping of Well-Known Types  . . . . . . . . . . . . . . . . .  4
   3.  Translation of SMIv2 Modules and SMIv2 IMPORT Clauses  . . . .  5
     3.1.  Example: IMPORTS of IF-MIB . . . . . . . . . . . . . . . .  6
   4.  Translation of the MODULE-IDENTITY Macro . . . . . . . . . . .  7
     4.1.  MODULE-IDENTITY Translation Rules  . . . . . . . . . . . .  7
     4.2.  Example: MODULE-IDENTITY of IF-MIB . . . . . . . . . . . .  8
   5.  Translation of the TEXTUAL-CONVENTION Macro  . . . . . . . . .  9
     5.1.  TEXTUAL-CONVENTION Translation Rules . . . . . . . . . . .  9
     5.2.  Example: OwnerString and InterfaceIndex of IF-MIB  . . . . 10
     5.3.  Example: IfDirection of the DIFFSERV-MIB . . . . . . . . . 11
   6.  Translation of OBJECT IDENTIFIER Assignments . . . . . . . . . 11
   7.  Translation of the OBJECT-TYPE Macro . . . . . . . . . . . . . 11
     7.1.  Scalar and Columnar Object Translation Rules . . . . . . . 11
     7.2.  Example: ifNumber and ifIndex of the IF-MIB  . . . . . . . 13
     7.3.  Non-Augmenting Conceptual Table Translation Rules  . . . . 13
     7.4.  Example: ifTable of the IF-MIB . . . . . . . . . . . . . . 15
     7.5.  Example: ifRcvAddressTable of the IF-MIB . . . . . . . . . 16
     7.6.  Example: alHostTable of the RMON2-MIB  . . . . . . . . . . 17
     7.7.  Augmenting Conceptual Tables Translation Rules . . . . . . 18
     7.8.  Example: ifXTable of the IF-MIB  . . . . . . . . . . . . . 20
Show full document text
ISOC IETF Trust RFC Editor IRTF IESG IETF IAB IASA & IAOC IETF Tools IANA