Translation of SMIv2 MIB Modules to YANG Modules
draft-ietf-netmod-smi-yang-04

The information below is for an old version of the document
Document Type Active Internet-Draft (netmod WG)
Last updated 2012-04-12 (latest revision 2012-01-19)
Replaces draft-schoenw-netmod-smi-yang
Stream IETF
Intended RFC status Proposed Standard
Formats plain text pdf html
Stream WG state WG Document
Consensus Unknown
Document shepherd None
IESG IESG state Waiting for AD Go-Ahead
Telechat date
Responsible AD Benoit Claise
IESG note David Kessens is the Document Shepherd
Send notices to netmod-chairs@tools.ietf.org, draft-ietf-netmod-smi-yang@tools.ietf.org
Network Working Group                                   J. Schoenwaelder
Internet-Draft                                         Jacobs University
Intended status: Standards Track                        January 19, 2012
Expires: July 22, 2012

            Translation of SMIv2 MIB Modules to YANG Modules
                     draft-ietf-netmod-smi-yang-04

Abstract

   YANG is a data modeling language used to model configuration and
   state data manipulated by the NETCONF protocol, 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 SNMP protocol.  This document defines a translation of
   SMIv2 MIB modules into YANG modules, enabling read-only access to
   data objects defined in SMIv2 MIB modules via NETCONF.

Status of this Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on July 22, 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

Schoenwaelder             Expires July 22, 2012                 [Page 1]
Internet-Draft        Translation of SMIv2 to YANG          January 2012

   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.

Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  3
   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 . . . . . . . . . 10
   6.  Translation of OBJECT IDENTIFIER Assignments . . . . . . . . . 12
   7.  Translation of the OBJECT-TYPE Macro . . . . . . . . . . . . . 13
     7.1.  Scalar and Columnar Object Translation Rules . . . . . . . 13
     7.2.  Example: ifNumber and ifIndex of the IF-MIB  . . . . . . . 14
     7.3.  Non-Augmenting Conceptual Table Translation Rules  . . . . 15
     7.4.  Example: ifTable of the IF-MIB . . . . . . . . . . . . . . 17
     7.5.  Example: ifRcvAddressTable of the IF-MIB . . . . . . . . . 17
     7.6.  Example: alHostTable of the RMON2-MIB  . . . . . . . . . . 19
     7.7.  Augmenting Conceptual Tables Translation Rules . . . . . . 20
     7.8.  Example: ifXTable of the IF-MIB  . . . . . . . . . . . . . 21
   8.  Translation of the OBJECT-IDENTITY Macro . . . . . . . . . . . 23
     8.1.  OBJECT-IDENTITY Translation Rules  . . . . . . . . . . . . 23
     8.2.  Example: diffServTBParamSimpleTokenBucket of the
           DIFFSERV-MIB . . . . . . . . . . . . . . . . . . . . . . . 23
   9.  Translation of the NOTIFICATION-TYPE Macro . . . . . . . . . . 24
     9.1.  NOTIFICATION-TYPE Translation Rules  . . . . . . . . . . . 24
     9.2.  Example: linkDown NOTIFICATION-TYPE of IF-MIB  . . . . . . 24
   10. YANG Language Extension Definition . . . . . . . . . . . . . . 27
   11. Implementing Configuration Data Nodes  . . . . . . . . . . . . 31
     11.1. Example: addressMapControlTable of RMON2-MIB . . . . . . . 31
   12. IANA Considerations  . . . . . . . . . . . . . . . . . . . . . 34
   13. Security Considerations  . . . . . . . . . . . . . . . . . . . 35
Show full document text