This is a static archive of the previous Open Grid Forum GridForge content management system saved from host forge.ogf.org file /sf/wiki/do/viewPage/projects.scrm-wg/wiki/SNMP at Thu, 03 Nov 2022 00:17:12 GMT SourceForge : View Wiki Page: SNMP

Project Home

Tracker

Documents

Tasks

Source Code

Discussions

File Releases

Wiki

Project Admin
Search Wiki Pages Project: scrm-wg     Wiki > SNMP > View Wiki Page
wiki1508: SNMP

Standard

1. The name of the specification

Simple Network Management Protocol (SNMP)

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

These specifications, and its companion documents, were produced by the SNMPv3 Working Group of the Internet Engineering Task Force (IETF). The SNMPv3 Working Group was chartered to prepare recommendations for the next generation of SNMP. The goal of the Working Group was to produce the necessary set of documents that provide a single standard for the next generation of core SNMP functions. The single, most critical need in the next generation is a definition of security and administration that makes SNMP-based management transactions secure in a way which is useful for users who wish to use SNMPv3 to manage networks, the systems that make up those networks, and the applications which reside on those systems, including manager-to- agent, agent-to-manager, and manager-to-manager transactions.

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

Version 3

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 SNMPv3 Management Framework follow the same architecture as those of the prior versions and can be organized for expository purposes into four main categories as follows:

* 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.

5. URI for the normative text of the specification

Informative overview and applicability statement: http://www.ietf.org/rfc/rfc3410.txt (Informational)

Normative SNMPv3 Internet Standard (STD 62):

Additional Documents:

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 62)

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.)

 




The Open Grid Forum Contact Webmaster | Report a problem | GridForge Help
This is a static archive of the previous Open Grid Forum GridForge content management system saved from host forge.ogf.org file /sf/wiki/do/viewPage/projects.scrm-wg/wiki/SNMP at Thu, 03 Nov 2022 00:17:12 GMT