Skip to main content

On the Difference between Information Models and Data Models
draft-irtf-nmrg-im-dm-02

The information below is for an old version of the document that is already published as an RFC.
Document Type
This is an older version of an Internet-Draft that was ultimately published as RFC 3444.
Authors Aiko Pras , Jürgen Schönwälder
Last updated 2015-10-14 (Latest revision 2002-09-19)
RFC stream Internet Engineering Task Force (IETF)
Intended RFC status Informational
Formats
Stream WG state (None)
Document shepherd (None)
IESG IESG state Became RFC 3444 (Informational)
Action Holders
(None)
Consensus boilerplate Unknown
Telechat date (None)
Responsible AD Bert Wijnen
IESG note
Send notices to (None)
draft-irtf-nmrg-im-dm-02
A new Request for Comments is now available in online RFC libraries.

        RFC 3444

        Title:      On the Difference between Information Models and
                    Data Models
        Author(s):  A. Pras, J. Schoenwaelder
        Status:     Informational
        Date:       January 2003
        Mailbox:    pras@ctit.utwente.nl,
                    schoenw@informatik.uni-osnabrueck.de
        Pages:      8
        Characters: 18596
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-irtf-nmrg-im-dm-02.txt

        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc3444.txt

There has been ongoing confusion about the differences between
Information Models and Data Models for defining managed objects in
network management.  This document explains the differences between
these terms by analyzing how existing network management model
specifications (from the IETF and other bodies such as the
International Telecommunication Union (ITU) or the Distributed
Management Task Force (DMTF)) fit into the universe of Information
Models and Data Models.

This memo documents the main results of the 8th workshop of the
Network Management Research Group (NMRG) of the Internet Research
Task Force (IRTF) hosted by the University of Texas at Austin.

This memo provides information for the Internet community.  It does
not specify an Internet standard of any kind.  Distribution of this
memo is unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 
help: ways_to_get_rfcs.  For example:

        To: rfc-info@RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.echo 
Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.