idnits 2.17.1 draft-presuhn-floats-01.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 3, 2010) is 4893 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 3, 2010 5 Expires: June 6, 2011 7 Textual Conventions for the Representation of Floating-Point Numbers 8 draft-presuhn-floats-01.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 6, 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 . . . . . . . . . . . . . . . . . . 3 53 3.1. MIB modules required for IMPORTS . . . . . . . . . . . . . 3 54 3.2. Documents required for REFERENCE clauses . . . . . . . . . 4 55 4. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . 4 56 5. Security Considerations . . . . . . . . . . . . . . . . . . . . 5 57 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 5 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 2. The Internet-Standard Management Framework 87 For a detailed overview of the documents that describe the current 88 Internet-Standard Management Framework, please refer to section 7 of 89 RFC 3410 [RFC3410]. 91 Managed objects are accessed via a virtual information store, termed 92 the Management Information Base or MIB. MIB objects are generally 93 accessed through the Simple Network Management Protocol (SNMP). 94 Objects in the MIB are defined using the mechanisms defined in the 95 Structure of Management Information (SMI). This memo specifies a MIB 96 module that is compliant to the SMIv2, which is described in STD 58, 97 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 98 [RFC2580]. 100 3. Structure of the MIB Module 102 This MIB module defines three textual conventions. It defines no MIB 103 objects. 105 3.1. MIB modules required for IMPORTS 107 This MIB module employs definitions from [RFC2578] and [RFC2579]. 109 3.2. Documents required for REFERENCE clauses 111 This MIB module contains REFERENCE clauses making reference to IEEE 112 754-2008 [IEEE.754.2008]. 114 4. Definitions 116 FLOAT-TC-MIB DEFINITIONS ::= BEGIN 118 IMPORTS 119 MODULE-IDENTITY, 120 mib-2 FROM SNMPv2-SMI 121 TEXTUAL-CONVENTION FROM SNMPv2-TC; 123 floatTcMIB MODULE-IDENTITY 124 LAST-UPDATED "201011290000Z" -- 29 November, 2010 125 ORGANIZATION "None" 126 CONTACT-INFO "Randy Presuhn 127 Email: randy_presuhn@mindspring.com" 129 DESCRIPTION "Textual conventions for the representation 130 of floating-point numbers. 132 Copyright (c) 2010 IETF Trust and the persons 133 identified as the document authors. All rights 134 reserved. 136 Redistribution and use in source and binary forms, 137 with or without modification, is permitted pursuant 138 to, and subject to the license terms contained in, 139 the Simplified BSD License set forth in Section 140 4.c of the IETF Trust's Legal Provisions Relating 141 to IETF Documents 142 (http://trustee.ietf.org/license-info). 144 This version of this MIB module is part of RFC XXXX; 145 see the RFC itself for full legal notices." 147 REVISION "201011290000Z" 148 DESCRIPTION "Initial version, published as RFC XXXX." 149 ::= { mib-2 XXX } 150 -- RFC Ed.: replace XXX with IANA-assigned number & remove this note 151 -- RFC Ed.: replace XXXX with the RFC number & remove this note 153 Float32TC ::= TEXTUAL-CONVENTION 154 STATUS current 155 DESCRIPTION 156 "This type represents a 32-bit (4-octet) IEEE 157 floating-point number in binary interchange format." 158 REFERENCE 159 "IEEE Standard for Binary Floating-Point Arithmetic, 160 Standard 754-2008" 161 SYNTAX OCTET STRING (SIZE(4)) 163 Float64TC ::= TEXTUAL-CONVENTION 164 STATUS current 165 DESCRIPTION 166 "This type represents a 64-bit (8-octet) IEEE 167 floating-point number in binary interchange format." 168 REFERENCE 169 "IEEE Standard for Binary Floating-Point Arithmetic, 170 Standard 754-2008" 171 SYNTAX OCTET STRING (SIZE(8)) 173 Float128TC ::= TEXTUAL-CONVENTION 174 STATUS current 175 DESCRIPTION 176 "This type represents a 128-bit (16-octet) IEEE 177 floating-point number in binary interchange format." 178 REFERENCE 179 "IEEE Standard for Binary Floating-Point Arithmetic, 180 Standard 754-2008" 181 SYNTAX OCTET STRING (SIZE(16)) 183 END 185 5. Security Considerations 187 This module does not define any management objects. Instead, it 188 defines a set of textual conventions that may be used by other MIB 189 modules to define management objects. 191 Meaningful security considerations can only be written in the MIB 192 modules that define management objects. Therefore, this memo has no 193 impact on the security of the Internet. 195 6. IANA Considerations 197 The MIB module in this document uses the following IANA-assigned 198 OBJECT IDENTIFIER value recorded in the SMI Numbers registry: 200 Descriptor OBJECT IDENTIFIER value 201 ---------- ----------------------- 202 floatTcMIB { mib-2 XXX } 204 Editor's Note (to be removed prior to publication): the IANA is 205 requested to assign a value for "XXX" under the 'mib-2' subtree and 206 to record the assignment in the SMI Numbers registry. When the 207 assignment has been made, the RFC Editor is asked to replace "XXX" 208 (here and in the MIB module) with the assigned value and to remove 209 this note. 211 7. Contributors 213 The following people provided helpful comments during the development 214 of this document: 216 o Juergen Quittek 218 8. References 220 8.1. Normative References 222 [IEEE.754.2008] 223 Institute of Electrical and Electronics Engineers, 224 "Standard for Binary Floating-Point Arithmetic", 225 IEEE Standard 754, August 2008. 227 [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J. 228 Schoenwaelder, Ed., "Structure of Management Information 229 Version 2 (SMIv2)", STD 58, RFC 2578, April 1999. 231 [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J. 232 Schoenwaelder, Ed., "Textual Conventions for SMIv2", 233 STD 58, RFC 2579, April 1999. 235 [RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder, 236 "Conformance Statements for SMIv2", STD 58, RFC 2580, 237 April 1999. 239 8.2. Informative References 241 [RFC3216] Elliott, C., Harrington, D., Jason, J., Schoenwaelder, J., 242 Strauss, F., and W. Weiss, "SMIng Objectives", RFC 3216, 243 December 2001. 245 [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, 246 "Introduction and Applicability Statements for Internet- 247 Standard Management Framework", RFC 3410, December 2002. 249 Author's Address 251 Randy Presuhn 252 None 253 San Jose, CA 95120 254 USA 256 Email: randy_presuhn@mindspring.com