SourceForge : View Wiki Page: SMI

Search Wiki Pages Project: scrm-wg Wiki > SMI > View Wiki Page

wiki1507: SMI

Standard

1. The name of the specification

Strutcure of Management Information Version 2 (SMIv2)

2. A short statement (<100 words) of the purpose and function of the specification

Managed objects are accessed via a virtual information store, termed the Management Information Base or MIB. MIB objects are generally accessed through the Simple Network Management Protocol (SNMP). Objects in the MIB are defined using the mechanisms defined in the Structure of Management Information (SMI). The current Internet Standard version of the SMI is SMIv2, defined in STD 58, composed of RFC 2578, RFC 2579 and RFC 2580.

3. The version number (or other distinct identifier) and date of the most recently approved version of the specification.

Version 2

4. If the specification is part of a group of explicitly related specifications from the same source, the name of the group of specifications.

The documents which specify the SMIv2 are part of the IETF Management Framework which is composed of:

* the data modeling/definition language (SMIv2),

* Management Information Base (MIB) modules,

* protocol operations (SNMPv2 protocol operations),

* SNMP message wrapper, and

* security and administration.

If we look at the 3 versions of SNMP, then we can summarize as follows:

SNMPv1

SNMPv1 message wrapper, which means no real security because it uses a plaint text password as a community name
Uses SNMPv1 protocol operations (GET, GET-NEXT, RESPONSE, SET, TRAP)
Carries management data defined with SMIv1

SNMPv2 (Often called SNMPv2c)

SNMPv2c message wrapper, which means no real security because it uses the same plaint text password as a community name as in SNMPv1.
Uses SNMPv2 protocol operations (GET, GET-NEXT, RESPONSE, SET, GET-BULK, INFORM, TRAPv2)
Carries management data defined with SMIv2

SNMPv3

SNMPv3 message wrapper, which means it adds real security and allows for authentication and encryption.
Uses SNMPv2 protocol operations (GET, GET-NEXT, RESPONSE, SET, GET-BULK, INFORM, TRAPv2)
Carries management data defined with SMIv2
Includes MIB Modules for the administration of users and access control.

So the above shows that SMIv2 is used in both SNMPv2c and SNMPv3.

5. URI for the normative text of the specification

Normative SMIv2 Internet Standard (STD 58):

Additional Document:

http://www.ietf.org/rfc/rfc3410.txt (Informational)
http://www.ietf.org/rfc/rfc4181.txt (Best Current Practice)

6. The name of the SDO that generated/authored/hosted the specification.

Internet Engineering Task Force (IETF)

7. URI for the SDO

http://www.ietf.org

8. The level of approval that the SDO has conferred on the specification as described by the SDO's process.

Internet Standard (STD 58)

9. The language or languages in which the specification is available.

US English

SUBJECT

10. Which of the ITU-T TMN FCAPS model layers does the specification's functionality address?

(http://en.wikipedia.org/wiki/FCAPS, http://www.futsoft.com/pdf/fcapswp.pdf) Fault Management: Fixing broken resources. Configuration Management: Controlling a resource's operational parameters. Accounting Management: Recording and analyzing resource use. Performance Management: Controlling speed and efficiency of resource use. Security Management: Controlling access to resources.

12. Where does the specification directly operate, as among the layers defined in the ISO Open System Interconnect (OSI) model?

(http://www.looselycoupled.com/opinion/2003/saruk-osi-infr0905.html ) Physical layer Data link layer Network layer Transport layer Session layer Presentation layer Application layer.

13. Which of the following (CIM based) functional areas does the model of the specification address?

(http://www.dmtf.org/standards/cim/)

Policy Management Infrastructure Physical Networks Logical Networks Physical Systems Logical Systems Physical Devices Logical Devices Physical Storage Logical Storage Operating Systems Databases Application Servers Applications Users Security Support

OPTIONAL

14. The level of approval of the specification in this generic lifecycle taxonomy:

IESG approved Internet Standard

15. URI for the applicable SDO's patent and copyright rules, if any, applicable to development and use of the specification.

http://www.ietf.org/rfc/rfc3978.txt and http://www.ietf.org/rfc/rfc3979.txt

16. URI for the SDO's posting location, (if any) for notices from participants or individuals regarding claims under the rules stated under number 15.

https://datatracker.ietf.org/public/ipr_disclosure.cgi

17. Interoperability, conformance, or certification test activity for the specification (by owner name or URI).

18. Known implementations of the specification (by owner name or URI).

19. A list (or URI pointer to same) of the other specifications* that are normatively referenced in the specification.

20. A list (or URI pointer to same) of the other specifications* that are referenced in the specification (except the ones listed under number 19).

21. A list (or URI pointer to same) of other specifications* with which the specification may (speculatively) interoperate or act in complementary, compatible fashion.

22. A list (or URI pointer to same) of other specifications* similar to this specification. (Whether or not substitutable.)

Show Details