draft-ietf-opsawg-mib-floats-00.txt   draft-ietf-opsawg-mib-floats-01.txt 
Network Working Group R. Presuhn Network Working Group R. Presuhn
Internet-Draft None Internet-Draft None
Intended status: Standards Track January 18, 2011 Intended status: Standards Track April 25, 2011
Expires: July 22, 2011 Expires: October 28, 2011
Textual Conventions for the Representation of Floating-Point Numbers Textual Conventions for the Representation of Floating-Point Numbers
draft-ietf-opsawg-mib-floats-00.txt draft-ietf-opsawg-mib-floats-01.txt
Abstract Abstract
This memo defines a Management Information Base (MIB) module This memo defines a Management Information Base (MIB) module
containing textual conventions (TCs) to represent floating-point containing textual conventions (TCs) to represent floating-point
numbers. numbers.
Status of this Memo Status of this Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
skipping to change at page 1, line 32 skipping to change at page 1, line 32
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on July 22, 2011. This Internet-Draft will expire on October 28, 2011.
Copyright Notice Copyright Notice
Copyright (c) 2011 IETF Trust and the persons identified as the Copyright (c) 2011 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. The Internet-Standard Management Framework . . . . . . . . . . 3 2. The Internet-Standard Management Framework . . . . . . . . . . 3
3. Applicability . . . . . . . . . . . . . . . . . . . . . . . . . 3 3. Applicability . . . . . . . . . . . . . . . . . . . . . . . . . 4
4. Structure of the MIB Module . . . . . . . . . . . . . . . . . . 4 4. Structure of the MIB Module . . . . . . . . . . . . . . . . . . 5
4.1. MIB modules required for IMPORTS . . . . . . . . . . . . . 4 4.1. MIB modules required for IMPORTS . . . . . . . . . . . . . 5
4.2. Documents required for REFERENCE clauses . . . . . . . . . 5 4.2. Documents required for REFERENCE clauses . . . . . . . . . 5
5. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . 5 5. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . 5
6. Security Considerations . . . . . . . . . . . . . . . . . . . . 6 6. Security Considerations . . . . . . . . . . . . . . . . . . . . 6
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 6 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 7
8. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 7 8. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 7
9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 7 9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 7
9.1. Normative References . . . . . . . . . . . . . . . . . . . 7 9.1. Normative References . . . . . . . . . . . . . . . . . . . 7
9.2. Informative References . . . . . . . . . . . . . . . . . . 8 9.2. Informative References . . . . . . . . . . . . . . . . . . 8
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 8 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 8
1. Introduction 1. Introduction
This memo defines textual conventions for the representation of This memo defines textual conventions for the representation of
floating-point numbers. All of these definitions are in terms of the floating-point numbers. All of these definitions are in terms of the
skipping to change at page 3, line 32 skipping to change at page 3, line 32
has been recognized in network management. For example, Section has been recognized in network management. For example, Section
4.2.3 of the SMIng Objectives [RFC3216] elaborates the need for these 4.2.3 of the SMIng Objectives [RFC3216] elaborates the need for these
three floating-point data types in network management protocols. three floating-point data types in network management protocols.
The selection of a floating-point format involves many considerations The selection of a floating-point format involves many considerations
and trade-offs. For an introduction to the fundamentals of floating- and trade-offs. For an introduction to the fundamentals of floating-
point representations see chapter 4 of [KNUTH], and for a a point representations see chapter 4 of [KNUTH], and for a a
discussion of these issues specifically with respect to the IEEE discussion of these issues specifically with respect to the IEEE
formats, see [GOLDBERG]. formats, see [GOLDBERG].
All of these textual conventions employ the binary interchange format
defined in [IEEE.754.2008]. Specifically, this means that for all of
them, the highest-order bit of the first byte is the sign bit, with
the remaining bits of the octet string corresponding to the exponent
and fraction parts, in network byte order.
2. The Internet-Standard Management Framework 2. The Internet-Standard Management Framework
For a detailed overview of the documents that describe the current For a detailed overview of the documents that describe the current
Internet-Standard Management Framework, please refer to section 7 of Internet-Standard Management Framework, please refer to section 7 of
RFC 3410 [RFC3410]. RFC 3410 [RFC3410].
Managed objects are accessed via a virtual information store, termed Managed objects are accessed via a virtual information store, termed
the Management Information Base or MIB. MIB objects are generally the Management Information Base or MIB. MIB objects are generally
accessed through the Simple Network Management Protocol (SNMP). accessed through the Simple Network Management Protocol (SNMP).
Objects in the MIB are defined using the mechanisms defined in the Objects in the MIB are defined using the mechanisms defined in the
skipping to change at page 4, line 40 skipping to change at page 4, line 45
needed, as well as recognize that it could be inefficient to use, needed, as well as recognize that it could be inefficient to use,
for example, Float128TC when Float64TC would do. for example, Float128TC when Float64TC would do.
o Since these textual conventions are defined in terms of the OCTET o Since these textual conventions are defined in terms of the OCTET
STRING type, the SMI's mechanisms for formally setting range STRING type, the SMI's mechanisms for formally setting range
constraints are not available. MIB designers using these textual constraints are not available. MIB designers using these textual
conventions will need to use DESCRIPTION clauses to spell out any conventions will need to use DESCRIPTION clauses to spell out any
applicable range constraints beyond those implied by the applicable range constraints beyond those implied by the
underlying IEEE types. underlying IEEE types.
o Whenever these textual conventions are used in a MIB module, the
associated DESCRIPTION clause will need to clearly specify whether
denormalized numbers, NaNs ("not a number") or infinities are
permitted, along with any special semantics associated with these
cases. This is especially important for writeable objects.
4. Structure of the MIB Module 4. Structure of the MIB Module
This MIB module defines three textual conventions. It defines no MIB This MIB module defines three textual conventions. It defines no MIB
objects. objects.
4.1. MIB modules required for IMPORTS 4.1. MIB modules required for IMPORTS
This MIB module employs definitions from [RFC2578] and [RFC2579]. This MIB module employs definitions from [RFC2578] and [RFC2579].
4.2. Documents required for REFERENCE clauses 4.2. Documents required for REFERENCE clauses
skipping to change at page 7, line 28 skipping to change at page 7, line 36
o Andy Bierman o Andy Bierman
o Martin Duerst o Martin Duerst
o Alfred Hoenes o Alfred Hoenes
o Juergen Quittek o Juergen Quittek
o Juergen Schoenwaeder o Juergen Schoenwaeder
o Dave Shield
o Robert Story o Robert Story
9. References 9. References
9.1. Normative References 9.1. Normative References
[IEEE.754.2008] [IEEE.754.2008]
Institute of Electrical and Electronics Engineers, Institute of Electrical and Electronics Engineers,
"Standard for Binary Floating-Point Arithmetic", "Standard for Binary Floating-Point Arithmetic",
IEEE Standard 754, August 2008. IEEE Standard 754, August 2008.
 End of changes. 8 change blocks. 
8 lines changed or deleted 22 lines changed or added

This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/