--- xxx.old Wed Oct 29 17:23:48 2003 +++ xxx.new Wed Oct 29 17:23:48 2003 @@ -1,19 +1,19 @@ Network Working Group F. Strauss Internet-Draft TU Braunschweig -Expires: March 19, 2004 J. Schoenwaelder +Expires: April 28, 2004 J. Schoenwaelder International University Bremen - September 19, 2003 + October 29, 2003 SMIng Mappings to SNMP - draft-irtf-nmrg-sming-snmp-03 + draft-irtf-nmrg-sming-snmp-04 Status of this Memo This document is an Internet-Draft and is in full conformance with all provisions of Section 10 of RFC2026. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that other groups may also distribute working documents as Internet-Drafts. @@ -22,33 +22,35 @@ 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." The list of current Internet-Drafts can be accessed at http:// www.ietf.org/ietf/1id-abstracts.txt. The list of Internet-Draft Shadow Directories can be accessed at http://www.ietf.org/shadow.html. - This Internet-Draft will expire on March 19, 2004. + This Internet-Draft will expire on April 28, 2004. Copyright Notice Copyright (C) The Internet Society (2003). All Rights Reserved. Abstract - This memo defines an SMIng language extension that specifies the - mapping of SMIng definitions of identities, classes, and their - attributes and events to dedicated definitions of nodes, scalar - objects, tables and columnar objects, and notifications for - application in the SNMP management framework. + SMIng (Structure of Management Information, Next Generation) + [RFCxxx1] is a protocol-independent data definition language for + management information. This memo defines an SMIng language + extension that specifies the mapping of SMIng definitions of + identities, classes, and their attributes and events to dedicated + definitions of nodes, scalar objects, tables and columnar objects, + and notifications for application in the SNMP management framework. Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 4 1.1 Terms of Requirement Levels . . . . . . . . . . . . . . . . 4 2. SNMP Based Internet Management . . . . . . . . . . . . . . . 4 2.1 Kinds of Nodes . . . . . . . . . . . . . . . . . . . . . . . 5 2.2 Scalar and Columnar Object Instances . . . . . . . . . . . . 6 2.3 Object Identifier Hierarchy . . . . . . . . . . . . . . . . 7 3. SMIng Data Type Mappings . . . . . . . . . . . . . . . . . . 8 @@ -100,44 +102,46 @@ 4.7.4 The compliance's reference Statement . . . . . . . . . . . . 24 4.7.5 The compliance's mandatory Statement . . . . . . . . . . . . 24 4.7.6 The compliance's optional Statement . . . . . . . . . . . . 24 4.7.7 The compliance's refine Statement . . . . . . . . . . . . . 25 4.7.8 Usage Example . . . . . . . . . . . . . . . . . . . . . . . 26 5. NMRG-SMING-SNMP-EXT . . . . . . . . . . . . . . . . . . . . 27 6. NMRG-SMING-SNMP . . . . . . . . . . . . . . . . . . . . . . 33 7. Security Considerations . . . . . . . . . . . . . . . . . . 47 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 47 Normative References . . . . . . . . . . . . . . . . . . . . 47 - Informative References . . . . . . . . . . . . . . . . . . . 47 + Informative References . . . . . . . . . . . . . . . . . . . 48 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . 49 Intellectual Property and Copyright Statements . . . . . . . 50 1. Introduction - This memo defines an SMIng [SMIng] language extension that specifies - the mapping of SMIng definitions of identities, classes, and their - attributes and events to dedicated definitions of nodes, scalar - objects, tables and columnar objects, and notifications for - application in the SNMP management framework. + SMIng (Structure of Management Information, Next Generation) + [RFCxxx1] is a protocol-independent data definition language for + management information. This memo defines an SMIng language + extension that specifies the mapping of SMIng definitions of + identities, classes, and their attributes and events to dedicated + definitions of nodes, scalar objects, tables and columnar objects, + and notifications for application in the SNMP management framework. Section 2 introduces basics of the SNMP management framework. Section 3 defines how SMIng data types are mapped to the data types - supported by the SNMP protocol. It introduces some new ASN.1 + supported by the SNMP protocol. It introduces some new ASN.1 [ASN1] definitions which are used to represent new SMIng base types such as floats in the SNMP protocol. Section 4 describes the semantics of the SNMP mapping extensions for SMIng. The formal SMIng specification of the extension is provided in Section 5. - Section 6 contains an SMIng module which defines data types and - classes (such as RowStatus) that are specific to the SNMP mapping. + Section 6 contains an SMIng module which defines derived types (such + as RowStatus) that are specific to the SNMP mapping. 1.1 Terms of Requirement Levels The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in [RFC2119]. 2. SNMP Based Internet Management The SNMP network management framework [RFC3410] is based on the @@ -150,20 +154,21 @@ Nodes in the object identifier tree may also identify conceptual tables, rows of conceptual tables, notifications, groups of objects and/or notifications, compliance statements, modules or other information. Each node is identified by an unique "object identifier" value which is a sequence of non-negative numbers, named "sub-identifiers", where the left-most sub-identifier refers to the node next to the root of the tree and the right-most sub-identifier refers to the node that is identified by the complete object identifier value. Each sub-identifier has a value between 0 and + 2^32-1 (4294967295). The SMIng extensions described in this document are used to map SMIng data definitions to SNMP compliant managed objects. This mapping is designed to be readable to computer programs, named MIB compilers, as well as to human readers. 2.1 Kinds of Nodes Each node in the object identifier tree is of a certain kind and may @@ -198,23 +203,23 @@ sub-identifier) and represent a sequence of one or more columnar objects. A row node is implicitly defined for each table node. o Columnar objects, which belong to a row (that is, the columnar objects' object identifier consists of the row's full object identifier plus a single column-identifying sub-identifier) and have zero or more object instances and no child nodes. They are defined as follows: The classes that are implemented by a `table' statement are identified by `implements' statements. The statement block of each `implements' statement contains `object' + statements that specify the mapping of attributes to columnar objects of this table. Columnar objects MUST not have any child - node. o Notifications, which represent information that is sent by agents within unsolicited transmissions. The `notification' statement is used to map an SMIng event to a notification. A notification's object identifier SHOULD not have any child node. o Groups of objects and notifications, which may be used for compliance statements. They are defined using the `group' statement. @@ -246,20 +251,21 @@ The base types of the indexing objects indicate how to form the instance-identifier: o integer-valued or enumeration-valued: a single sub-identifier taking the integer value (this works only for non-negative integers and integers of a size of up to 32 bits), o string-valued, fixed-length strings (or variable-length with compact encoding): `n' sub-identifiers, where `n' is the length of the string (each octet of the string is encoded in a separate + sub-identifier), o string-valued, variable-length strings or bits-valued: `n+1' sub-identifiers, where `n' is the length of the string or bits encoding (the first sub-identifier is `n' itself, following this, each octet of the string or bits is encoded in a separate sub-identifier), o object identifier-valued (with compact encoding): `n' sub-identifiers, where `n' is the number of sub-identifiers in the @@ -293,20 +299,21 @@ o within a module originally written to conform to SMIv1, or o a row must contain at least one columnar object which is not an auxiliary object. In the event that all of a row's columnar objects are also specified to be indexing objects then one of them MUST be accessible. 2.3 Object Identifier Hierarchy The layers of the object identifier tree near the root are well + defined and organized by standardization bodies. The first level next to the root has three nodes: 0: ccitt 1: iso 2: joint-iso-ccitt Note that the renaming of the Commite Consultatif International de @@ -338,36 +345,36 @@ defined unilaterally. The `enterprises' (private.1) subtree beneath private is used, among other things, to permit providers of networking subsystems to register information modules of their products. These and some other nodes are defined in the SMIng module NMRG-SMING-SNMP-EXT (Section 5). 3. SMIng Data Type Mappings - SMIng [SMIng] supports the following set of base types: OctetString, - Pointer, Integer32, Integer64, Unsigned32, Unsigned64, Float32, - Float64, Float128, Enumeration, Bits, and ObjectIdentifier. The - SMIng core module NMRG-SMING [SMIng] defines additional derived data + SMIng [RFCxxx1] supports the following set of base types: + OctetString, Pointer, Integer32, Integer64, Unsigned32, Unsigned64, + Float32, Float64, Float128, Enumeration, Bits, and ObjectIdentifier. + + The SMIng core module NMRG-SMING [RFCxxx2] defines additional derived types, among them Counter32 (derived from Unsigned32), Counter64 (derived from Unsigned64), TimeTicks32 and TimeTicks64 (derived from - Unsigned32 and Unsigned64), IpAddress (derived from OctetString), and Opaque (derived from OctetString). The version 2 of the protocol operations for SNMP document [RFC3416] defines the following 9 data types which are distinguished by the protocol: INTEGER, OCTET STRING, OBJECT IDENTIFIER, IpAddress, Counter32, TimeTicks, Opaque, Counter64, Unsigned32. - The SMIng data types and their derived types are mapped to SNMP data + The SMIng base types and their derived types are mapped to SNMP data types according to the following table: SMIng Data Type SNMP Data Type Comment --------------- ------------------- ------- OctetString OCTET STRING (1) Pointer OBJECT IDENTIFIER Integer32 INTEGER Integer64 Opaque (Integer64) (2) Unsigned32 Unsigned32 (3) Unsigned64 Opaque (Unsigned64) (2) (4) @@ -380,33 +387,33 @@ Counter32 Counter32 Counter64 Counter64 TimeTicks32 TimeTicks TimeTicks64 Opaque (Unsigned64) (2) IpAddress IpAddress Opaque Opaque (1) This mapping includes all types derived from the OctetString type except those types derived from the IpAddress and Opaque SMIng - type defined in [SMIng]. + types defined in [RFCxxx2]. (2) This type is encoded according to the ASN.1 type with the same name defined in Section 3.1. The resulting BER encoded value is then wrapped in an Opaque value. (3) This mapping includes all types derived from the Unsigned32 type except those types derived from the Counter32 and TimeTicks32 - SMIng type defined in [SMIng]. + SMIng types defined in [RFCxxx2]. (4) This mapping includes all types derived from the Unsigned64 type except those types derived from the Counter64 SMIng type defined - in [SMIng]. + in [RFCxxx2]. 3.1 ASN.1 Definitions The ASN.1 [ASN1] type definitions below introduce data types which are used to map the new SMIng base types into the set of ASN.1 types supported by the second version of SNMP protocol operations [RFC3416]. NMRG-SMING-SNMP-MAPPING DEFINITIONS ::= BEGIN @@ -1154,38 +1161,38 @@ information on that object. See the `refineStatement' rule of the grammar (Section 5) for the formal syntax of the `refine' statement. 4.7.7.1 The refine's type Statement The refine's `type' statement, which need not be present, gets one argument that is used to provide a refined type for the correspondent object. Type restrictions may be applied by appending subtyping - information according to the rules of the base type. See [SMIng] for - SMIng base types and their type restrictions. In case of enumeration - or bitset types the order of named numbers is not significant. + information according to the rules of the base type. See [RFCxxx1] + for SMIng base types and their type restrictions. In case of + enumeration or bitset types the order of named numbers is not + significant. Note that if a `type' and a `writetype' statement are both present - then this type only applies when instances of the correspondent object are read. 4.7.7.2 The refine's writetype Statement The refine's `writetype' statement, which need not be present, gets one argument that is used to provide a refined type for the correspondent object, only when instances of that object are written. Type restrictions may be applied by appending subtyping information - according to the rules of the base type. See [SMIng] for SMIng base - types and their type restrictions. In case of enumeration or bitset - types the order of named numbers is not significant. + according to the rules of the base type. See [RFCxxx1] for SMIng + base types and their type restrictions. In case of enumeration or + bitset types the order of named numbers is not significant. 4.7.7.3 The refine's access Statement The refine's `access' statement, which need not be present, gets one argument that is used to specify the minimal level of access that the correspondent object must implement in the sense of its original `access' statement. Hence, the refine's `access' statement MUST NOT specify a greater level of access than is specified in the correspondent object definition. @@ -1224,24 +1231,24 @@ description "This group is mandatory for an SNMP entity which supports command responder applications, and is able to reinitialize itself such that its configuration is unaltered."; }; }; 5. NMRG-SMING-SNMP-EXT - The grammar of the SNMP mapping SMIng extension conforms to the - Augmented Backus-Naur Form (ABNF) [RFC2234]. It is included in the - abnf statement of the snmp SMIng extension definition in the - NMRG-SMING-SNMP-EXT module below. + The grammar of the snmp statement (including all its contained + statements) conforms to the Augmented Backus-Naur Form (ABNF) + [RFC2234]. It is included in the abnf statement of the snmp SMIng + extension definition in the NMRG-SMING-SNMP-EXT module below. module NMRG-SMING-SNMP-EXT { organization "IRTF Network Management Research Group (NMRG)"; contact "IRTF Network Management Research Group (NMRG) http://www.ibr.cs.tu-bs.de/projects/nmrg/ Frank Strauss TU Braunschweig @@ -1267,38 +1274,38 @@ and notifications, and additional information on module compliances. Copyright (C) The Internet Society (2003). All Rights Reserved. This version of this module is part of RFC XXXX, see the RFC itself for full legal notices."; revision { - date "2003-09-19"; + date "2003-10-29"; description "Initial revision, published as RFC XXXX."; }; // extension snmp { status current; description "The snmp statement maps SMIng definitions to SNMP conformant definitions."; abnf " ;; ;; sming-snmp.abnf -- Grammar of SNMP mappings in ABNF ;; notation (RFC 2234). ;; - ;; @(#) $Id: sming-snmp.abnf,v 1.13 2003/07/22 16:55:34 strauss Exp $ + ;; @(#) $Id: sming-snmp.abnf,v 1.14 2003/10/23 19:31:55 strauss Exp $ ;; ;; Copyright (C) The Internet Society (2003). All Rights Reserved. ;; ;; ;; Statement rules. ;; snmpStatement = snmpKeyword *1(sep lcIdentifier) optsep \"{\" stmtsep @@ -1484,27 +1491,27 @@ augmentsKeyword = %x61 %x75 %x67 %x6D %x65 %x6E %x74 %x73 reordersKeyword = %x72 %x65 %x6F %x72 %x64 %x65 %x72 %x73 extendsKeyword = %x65 %x78 %x74 %x65 %x6E %x64 %x73 expandsKeyword = %x65 %x78 %x70 %x61 %x6E %x64 %x73 createKeyword = %x63 %x72 %x65 %x61 %x74 %x65 membersKeyword = %x6D %x65 %x6D %x62 %x65 %x72 %x73 mandatoryKeyword = %x6D %x61 %x6E %x64 %x61 %x74 %x6F %x72 %x79 optionalKeyword = %x6F %x70 %x74 %x69 %x6F %x6E %x61 %x6C refineKeyword = %x72 %x65 %x66 %x69 %x6E %x65 writetypeKeyword = %x77 %x72 %x69 %x74 %x65 %x74 %x79 %x70 %x65 + + ;; End of ABNF "; }; // - // - snmp { node ccitt { oid 0; }; node zeroDotZero { oid 0.0; description "A null value used for pointers."; }; node iso { oid 1; }; @@ -1532,20 +1539,24 @@ identifier hierarchy"; reference "RFC 2578, Section 2."; }; }; 6. NMRG-SMING-SNMP + The module NMRG-SMING-SNMP specified below defines derived types that + + are specific to the SNMP mapping. + module NMRG-SMING-SNMP { organization "IRTF Network Management Research Group (NMRG)"; contact "IRTF Network Management Research Group (NMRG) http://www.ibr.cs.tu-bs.de/projects/nmrg/ Frank Strauss TU Braunschweig Muehlenpfordtstrasse 23 @@ -1567,36 +1578,36 @@ that are specific to the SNMP protocol and its naming system. Copyright (C) The Internet Society (2003). All Rights Reserved. This version of this module is part of RFC XXXX, see the RFC itself for full legal notices."; revision { - date "2003-09-19"; + date "2003-10-29"; description "Initial version, published as RFC XXXX."; }; typedef TestAndIncr { type Integer32 (0..2147483647); description "Represents integer-valued information used for atomic operations. When the management protocol is used to specify that an object instance having this type is to be modified, the new value supplied via the management + protocol must precisely match the value presently held by the instance. If not, the management protocol set operation fails with an error of `inconsistentValue'. Otherwise, if the current value is the maximum value of - 2^31-1 (2147483647 decimal), then the value held by the instance is wrapped to zero; otherwise, the value held by the instance is incremented by one. (Note that regardless of whether the management protocol set operation succeeds, the variable-binding in the request and response PDUs are identical.) The value of the SNMP access clause for objects having this type has to be `readwrite'. When an instance of a columnar object having this type is created, any value @@ -1627,25 +1638,25 @@ typedef RowPointer { type Pointer; description "Represents a pointer to a conceptual row. The value is the name of the instance of the first accessible columnar object in the conceptual row. For example, ifIndex.3 would point to the 3rd row in the ifTable (note that if ifIndex were not-accessible, then + ifDescr.3 would be used instead)."; }; typedef RowStatus { - type Enumeration (active(1), notInService(2), notReady(3), createAndGo(4), createAndWait(5), destroy(6)); description "The RowStatus type is used to manage the creation and deletion of conceptual rows, and is used as the type for the row status column of a conceptual row (as described in Section 7.7.1 of [2].) The status column has six defined values: @@ -1676,20 +1687,21 @@ - `destroy', which is supplied by a management station wishing to delete all of the instances associated with an existing conceptual row. Whereas five of the six values (all except `notReady') may be specified in a management protocol set operation, only three values will be returned in response to a management protocol retrieval operation: `notReady', `notInService' or `active'. That is, when queried, an existing conceptual row has only three states: it is either available for use by the + managed device (the status column has value `active'); it is not available for use by the managed device, though the agent has sufficient information to make it so (the status column has value `notInService'); or, it is not available for use by the managed device, and an attempt to make it so would fail because the agent has insufficient information (the state column has value `notReady'). NOTE WELL @@ -1722,25 +1734,25 @@ STATE +--------------+-----------+-------------+------------- | A | B | C | D | |status col.|status column| |status column | is | is |status column ACTION |does not exist| notReady | notInService| is active --------------+--------------+-----------+-------------+------------- set status |noError ->D|inconsist- |inconsistent-|inconsistent- column to | or | entValue| Value| Value + createAndGo |inconsistent- | | | | Value| | | --------------+--------------+-----------+-------------+------------- set status |noError see 1|inconsist- |inconsistent-|inconsistent- - column to | or | entValue| Value| Value createAndWait |wrongValue | | | --------------+--------------+-----------+-------------+------------- set status |inconsistent- |inconsist- |noError |noError column to | Value| entValue| | active | | | | | | or | | | | | | | |see 2 ->D|see 8 ->D| ->D --------------+--------------+-----------+-------------+------------- @@ -1770,25 +1782,25 @@ (3) if other variable bindings included in the same PDU, provide values for all columns which are missing but required, then return noError and goto C. (4) at the discretion of the agent, the return value may be either: inconsistentName: because the agent does not choose to create such an instance when the corresponding + RowStatus instance does not exist, or inconsistentValue: if the supplied value is inconsistent with the state of some other MIB object's - value, or noError: because the agent chooses to create the instance. If noError is returned, then the instance of the status column must also be created, and the new state is B or C, depending on the information available to the agent. If inconsistentName or inconsistentValue is returned, the row remains in state A. @@ -1822,21 +1834,20 @@ conceptual row: selecting an instance-identifier which is not in use; creating the conceptual row; initializing any objects for which the agent does not supply a default; and, making the conceptual row available for use by the managed device. Interaction 1: Selecting an Instance-Identifier The algorithm used to select an instance-identifier varies for each conceptual row. In some cases, the instance- - identifier is semantically significant, e.g., the destination address of a route, and a management station selects the instance-identifier according to the semantics. In other cases, the instance-identifier is used solely to distinguish conceptual rows, and a management station without specific knowledge of the conceptual row might examine the instances present in order to determine an unused instance-identifier. (This approach may be used, but it is often highly sub-optimal; however, it is also a @@ -1866,20 +1877,21 @@ efficiency of each algorithm). For tables in which a large number of entries are expected, it is recommended that a MIB object be defined that returns an acceptable index for creation. For tables with small numbers of entries, it is recommended that the latter pseudo-random index mechanism be used. Interaction 2: Creating the Conceptual Row Once an unused instance-identifier has been selected, the + management station determines if it wishes to create and activate the conceptual row in one transaction or in a negotiated set of interactions. Interaction 2a: Creating and Activating the Conceptual Row The management station must first determine the column requirements, i.e., it must determine those columns for which it must or must not provide values. Depending on the complexity of the table and the management station's @@ -1913,25 +1925,25 @@ management protocol set operations to create an instance of this column. Once the column requirements have been determined, a management protocol set operation is accordingly issued. This operation also sets the new instance of the status column to `createAndGo'. When the agent processes the set operation, it verifies that it has sufficient information to make the conceptual row + available for use by the managed device. The information available to the agent is provided by two sources: the management protocol set operation which creates the conceptual row, and, implementation-specific defaults - supplied by the agent (note that an agent must provide implementation-specific defaults for at least those objects which it implements as read-only). If there is sufficient information available, then the conceptual row is created, a `noError' response is returned, the status column is set to `active', and no further interactions are necessary (i.e., interactions 3 and 4 are skipped). If there is insufficient information, then the conceptual row is not created, and the set operation fails with an error of `inconsistentValue'. On this error, the management station can issue a management @@ -1960,25 +1972,25 @@ instance. If not, the management station re-issues the management protocol set operation, but without setting a value for that particular columnar instance; otherwise, the management station aborts the row creation algorithm. Interaction 2b: Negotiating the Creation of the Conceptual Row The management station issues a management protocol set + operation which sets the desired instance of the status column to `createAndWait'. If the agent is unwilling to process a request of this sort, the set operation fails with an error of `wrongValue'. (As a consequence, such an agent - must be prepared to accept a single management protocol set operation, i.e., interaction 2a above, containing all of the columns indicated by its column requirements.) Otherwise, the conceptual row is created, a `noError' response is returned, and the status column is immediately set to either `notInService' or `notReady', depending on whether it has sufficient information to make the conceptual row available for use by the managed device. If there is sufficient information available, then the status column is set to `notInService'; otherwise, if there is insufficient @@ -2008,25 +2020,25 @@ associated with this column, and that this column in at least one conceptual row would be accessible in the MIB view used by the retrieval were it to exist. However, the agent does not have sufficient information to provide a value, and until a value is provided, the conceptual row may not be made available for use by the managed device. For those columns to which the agent provides read-create access, the `noSuchInstance' exception tells the management station that it must issue additional management protocol set operations, in + order to provide a value associated with this column. - the exception `noSuchObject' is returned, indicating that the agent does not implement the object-type - associated with this column or that there is no conceptual row for which this column would be accessible in the MIB view used by the retrieval. As such, the management station can not issue any management protocol set operations to create an instance of this column. If the value associated with the status column is `notReady', then the management station must first deal with all `noSuchInstance' columns, if any. Having done so, the @@ -2056,25 +2068,25 @@ management protocol set operation which sets the status column to `active'. In this case, when the management protocol set operation is issued to set the status column to `active', the values held in the agent supersede those used by the managed device. If the management station is prevented from setting the status column to `active' (e.g., due to management station or network failure) the conceptual row will be left in the `notInService' or `notReady' state, consuming resources + indefinitely. The agent must detect conceptual rows that have been in either state for an abnormally long period of time and remove them. It is the responsibility of the DESCRIPTION clause of the status column to indicate what an - abnormally long period of time would be. This period of time should be long enough to allow for human response time (including `think time') between the creation of the conceptual row and the setting of the status to `active'. In the absence of such information in the DESCRIPTION clause, it is suggested that this period be approximately 5 minutes in length. This removal action applies not only to newly- created rows, but also to previously active rows which are set to, and left in, the notInService state for a prolonged period exceeding that which is considered normal for such a @@ -2104,25 +2116,25 @@ `notInService' or `active'.) If the operation succeeds, then all instances associated with the conceptual row are immediately removed."; }; typedef StorageType { type Enumeration (other(1), volatile(2), nonVolatile(3), permanent(4), readOnly(5)); description + "Describes the memory realization of a conceptual row. A row which is volatile(2) is lost upon reboot. A row which is either nonVolatile(3), permanent(4) or readOnly(5), is backed up by stable storage. A row which - is permanent(4) can be changed but not deleted. A row which is readOnly(5) cannot be changed nor deleted. If the value of an object with this syntax is either permanent(4) or readOnly(5), it cannot be modified. Conversely, if the value is either other(1), volatile(2) or nonVolatile(3), it cannot be modified to be permanent(4) or readOnly(5). (All illegal modifications result in a 'wrongValue' error.) @@ -2153,25 +2165,25 @@ value must be accompanied by a definition of a textual convention for use with that TDomain. Some possible textual conventions, such as SnmpUDPAddress for snmpUDPDomain, are defined in the SNMPv2-TM MIB module. Other possible textual conventions are defined in other MIB modules. A zero-length TAddress value denotes an unknown transport service address." reference + "The SNMPv2-TM MIB module is defined in RFC 3417." }; typedef TAddress { - type TAddressOrZero (1..255); description "Denotes a transport service address. This type does not allow a zero-length TAddress value." }; }; 7. Security Considerations @@ -2188,37 +2200,43 @@ and phrases are directly taken from the SMIv2 specifications [RFC2578], [RFC2579], [RFC2580] written by Jeff Case, Keith McCloghrie, David Perkins, Marshall T. Rose, Juergen Schoenwaelder, and Steven L. Waldbusser. The authors would like to thank all participants of the 7th NMRG meeting held in Schloss Kleinheubach from 6-8 September 2000, which was a major step towards the current status of this memo, namely Heiko Dassow, David Durham, Keith McCloghrie, and Bert Wijnen. + Furthmore, several discussions within the SMING Working Group + reflected experience with SMIv2 and influenced this specification at + some points. + Normative References - [SMIng] Strauss, F. and J. Schoenwaelder, "SMIng - Next Generation + [RFCxxx1] Strauss, F. and J. Schoenwaelder, "SMIng - Next Generation Structure of Management Information", - draft-irtf-nmrg-sming-05.txt, September 2003. + draft-irtf-nmrg-sming-06.txt, October 2003. + + [RFCxxx2] Strauss, F. and J. Schoenwaelder, "SMIng Core Modules", + draft-irtf-nmrg-sming-modules-04.txt, October 2003. [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", RFC 2119, BCP 14, March 1997. [RFC2234] Crocker, D. and P. Overell, "Augmented BNF for Syntax Specifications: ABNF", RFC 2234, November 1997. Informative References [RFC3410] Case, J., Mundy, R., Partain, D. and B. Stewart, "Introduction to Version 3 of the Internet-standard - Network Management Framework", RFC 3410, December 2002. [RFC3411] Harrington, D., Presuhn, R. and B. Wijnen, "An Architecture for Describing Simple Network Management Protocol (SNMP) Management Frameworks", RFC 3411, STD 62, December 2002. [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M. and S. Waldbusser, "Structure of Management Information Version 2 (SMIv2)", RFC 2578, STD 58, April