idnits 2.17.1 draft-presuhn-floats-02.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (December 6, 2010) is 4888 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) -- Possible downref: Non-RFC (?) normative reference: ref. 'IEEE.754.2008' Summary: 0 errors (**), 0 flaws (~~), 1 warning (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group R. Presuhn 3 Internet-Draft None 4 Intended status: Standards Track December 6, 2010 5 Expires: June 9, 2011 7 Textual Conventions for the Representation of Floating-Point Numbers 8 draft-presuhn-floats-02.txt 10 Abstract 12 This memo defines a Management Information Base (MIB) module 13 containing textual conventions (TCs) to represent floating-point 14 numbers. 16 Status of this Memo 18 This Internet-Draft is submitted in full conformance with the 19 provisions of BCP 78 and BCP 79. 21 Internet-Drafts are working documents of the Internet Engineering 22 Task Force (IETF). Note that other groups may also distribute 23 working documents as Internet-Drafts. The list of current Internet- 24 Drafts is at http://datatracker.ietf.org/drafts/current/. 26 Internet-Drafts are draft documents valid for a maximum of six months 27 and may be updated, replaced, or obsoleted by other documents at any 28 time. It is inappropriate to use Internet-Drafts as reference 29 material or to cite them other than as "work in progress." 31 This Internet-Draft will expire on June 9, 2011. 33 Copyright Notice 35 Copyright (c) 2010 IETF Trust and the persons identified as the 36 document authors. All rights reserved. 38 This document is subject to BCP 78 and the IETF Trust's Legal 39 Provisions Relating to IETF Documents 40 (http://trustee.ietf.org/license-info) in effect on the date of 41 publication of this document. Please review these documents 42 carefully, as they describe your rights and restrictions with respect 43 to this document. Code Components extracted from this document must 44 include Simplified BSD License text as described in Section 4.e of 45 the Trust Legal Provisions and are provided without warranty as 46 described in the Simplified BSD License. 48 Table of Contents 50 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 51 2. The Internet-Standard Management Framework . . . . . . . . . . 3 52 3. Structure of the MIB Module . . . . . . . . . . . . . . . . . . 4 53 3.1. MIB modules required for IMPORTS . . . . . . . . . . . . . 4 54 3.2. Documents required for REFERENCE clauses . . . . . . . . . 4 55 4. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . 4 56 5. Security Considerations . . . . . . . . . . . . . . . . . . . . 5 57 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 6 58 7. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 6 59 8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 6 60 8.1. Normative References . . . . . . . . . . . . . . . . . . . 6 61 8.2. Informative References . . . . . . . . . . . . . . . . . . 7 62 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 7 64 1. Introduction 66 This memo defines textual conventions for the representation of 67 floating-point numbers. All of these definitions are in terms of the 68 IEEE Standard for Floating-Point Arithmetic, IEEE 754-2008 69 [IEEE.754.2008]. 71 The IEEE Standard for Floating-Point Arithmetic, IEEE 754-2008 72 [IEEE.754.2008], provides for a variety of interchange formats for 73 floating point numbers. The need for three of these, namely 75 o 32-bit, 77 o 64-bit, 79 o 128-bit, 81 has been recognized in network management. For example, Section 82 4.2.3 of the SMIng Objectives [RFC3216] elaborates the need for these 83 three floating-point data types in network management protocols. 85 The selection of a floating-point format involves many considerations 86 and trade-offs, and an exhaustive discussion of these is beyond the 87 scope of this menu. However, one consideration peculiar to the SNMP 88 environment bears mentioning here: the SNMP "lexicographical" 89 ordering for INDEX objects using these textual conventions will 90 simply be that of the octet strings corresponding to the floating 91 point representations, which will not in general reflect the 92 numerical ordering of the corresponding floating point values. 94 2. The Internet-Standard Management Framework 96 For a detailed overview of the documents that describe the current 97 Internet-Standard Management Framework, please refer to section 7 of 98 RFC 3410 [RFC3410]. 100 Managed objects are accessed via a virtual information store, termed 101 the Management Information Base or MIB. MIB objects are generally 102 accessed through the Simple Network Management Protocol (SNMP). 103 Objects in the MIB are defined using the mechanisms defined in the 104 Structure of Management Information (SMI). This memo specifies a MIB 105 module that is compliant to the SMIv2, which is described in STD 58, 106 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 107 [RFC2580]. 109 3. Structure of the MIB Module 111 This MIB module defines three textual conventions. It defines no MIB 112 objects. 114 3.1. MIB modules required for IMPORTS 116 This MIB module employs definitions from [RFC2578] and [RFC2579]. 118 3.2. Documents required for REFERENCE clauses 120 This MIB module contains REFERENCE clauses making reference to IEEE 121 754-2008 [IEEE.754.2008]. 123 4. Definitions 125 FLOAT-TC-MIB DEFINITIONS ::= BEGIN 127 IMPORTS 128 MODULE-IDENTITY, 129 mib-2 FROM SNMPv2-SMI 130 TEXTUAL-CONVENTION FROM SNMPv2-TC; 132 floatTcMIB MODULE-IDENTITY 133 LAST-UPDATED "201012050000Z" -- 05 December, 2010 134 ORGANIZATION "None" 135 CONTACT-INFO "Randy Presuhn 136 Email: randy_presuhn@mindspring.com" 138 DESCRIPTION "Textual conventions for the representation 139 of floating-point numbers. 141 Copyright (c) 2010 IETF Trust and the persons 142 identified as the document authors. All rights 143 reserved. 145 Redistribution and use in source and binary forms, 146 with or without modification, is permitted pursuant 147 to, and subject to the license terms contained in, 148 the Simplified BSD License set forth in Section 149 4.c of the IETF Trust's Legal Provisions Relating 150 to IETF Documents 151 (http://trustee.ietf.org/license-info). 153 This version of this MIB module is part of RFC XXXX; 154 see the RFC itself for full legal notices." 156 REVISION "201012050000Z" 157 DESCRIPTION "Initial version, published as RFC XXXX." 158 ::= { mib-2 XXX } 159 -- RFC Ed.: replace XXX with IANA-assigned number & remove this note 160 -- RFC Ed.: replace XXXX with the RFC number & remove this note 162 Float32TC ::= TEXTUAL-CONVENTION 163 STATUS current 164 DESCRIPTION 165 "This type represents a 32-bit (4-octet) IEEE 166 floating-point number in binary interchange format." 167 REFERENCE 168 "IEEE Standard for Binary Floating-Point Arithmetic, 169 Standard 754-2008" 170 SYNTAX OCTET STRING (SIZE(4)) 172 Float64TC ::= TEXTUAL-CONVENTION 173 STATUS current 174 DESCRIPTION 175 "This type represents a 64-bit (8-octet) IEEE 176 floating-point number in binary interchange format." 177 REFERENCE 178 "IEEE Standard for Binary Floating-Point Arithmetic, 179 Standard 754-2008" 180 SYNTAX OCTET STRING (SIZE(8)) 182 Float128TC ::= TEXTUAL-CONVENTION 183 STATUS current 184 DESCRIPTION 185 "This type represents a 128-bit (16-octet) IEEE 186 floating-point number in binary interchange format." 187 REFERENCE 188 "IEEE Standard for Binary Floating-Point Arithmetic, 189 Standard 754-2008" 190 SYNTAX OCTET STRING (SIZE(16)) 192 END 194 5. Security Considerations 196 This module does not define any management objects. Instead, it 197 defines a set of textual conventions that may be used by other MIB 198 modules to define management objects. 200 Meaningful security considerations can only be written in the MIB 201 modules that define management objects. Therefore, this memo has no 202 impact on the security of the Internet. 204 6. IANA Considerations 206 The MIB module in this document uses the following IANA-assigned 207 OBJECT IDENTIFIER value recorded in the SMI Numbers registry: 209 Descriptor OBJECT IDENTIFIER value 210 ---------- ----------------------- 211 floatTcMIB { mib-2 XXX } 213 Editor's Note (to be removed prior to publication): the IANA is 214 requested to assign a value for "XXX" under the 'mib-2' subtree and 215 to record the assignment in the SMI Numbers registry. When the 216 assignment has been made, the RFC Editor is asked to replace "XXX" 217 (here and in the MIB module) with the assigned value and to remove 218 this note. 220 7. Contributors 222 The following people provided helpful comments during the development 223 of this document: 225 o Juergen Quittek 227 o Juergen Schoenwaeder 229 o Robert Story 231 8. References 233 8.1. Normative References 235 [IEEE.754.2008] 236 Institute of Electrical and Electronics Engineers, 237 "Standard for Binary Floating-Point Arithmetic", 238 IEEE Standard 754, August 2008. 240 [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J. 241 Schoenwaelder, Ed., "Structure of Management Information 242 Version 2 (SMIv2)", STD 58, RFC 2578, April 1999. 244 [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J. 245 Schoenwaelder, Ed., "Textual Conventions for SMIv2", 246 STD 58, RFC 2579, April 1999. 248 [RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder, 249 "Conformance Statements for SMIv2", STD 58, RFC 2580, 250 April 1999. 252 8.2. Informative References 254 [RFC3216] Elliott, C., Harrington, D., Jason, J., Schoenwaelder, J., 255 Strauss, F., and W. Weiss, "SMIng Objectives", RFC 3216, 256 December 2001. 258 [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, 259 "Introduction and Applicability Statements for Internet- 260 Standard Management Framework", RFC 3410, December 2002. 262 Author's Address 264 Randy Presuhn 265 None 266 San Jose, CA 95120 267 USA 269 Email: randy_presuhn@mindspring.com