idnits 2.17.1 draft-ietf-mpsnmp-overosi-03.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Cannot find the required boilerplate sections (Copyright, IPR, etc.) in this document. Expected boilerplate is as follows today (2024-04-25) according to https://trustee.ietf.org/license-info : IETF Trust Legal Provisions of 28-dec-2009, Section 6.a: This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. IETF Trust Legal Provisions of 28-dec-2009, Section 6.b(i), paragraph 2: Copyright (c) 2024 IETF Trust and the persons identified as the document authors. All rights reserved. IETF Trust Legal Provisions of 28-dec-2009, Section 6.b(i), paragraph 3: This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** Missing document type: Expected "INTERNET-DRAFT" in the upper left hand corner of the first page ** Missing expiration date. The document expiration date should appear on the first and last page. ** The document seems to lack a 1id_guidelines paragraph about Internet-Drafts being working documents. ** The document seems to lack a 1id_guidelines paragraph about 6 months document validity. ** The document seems to lack a 1id_guidelines paragraph about the list of current Internet-Drafts. ** The document seems to lack a 1id_guidelines paragraph about the list of Shadow Directories. ** Expected the document's filename to be given on the first page, but didn't find any == No 'Intended status' indicated for this document; assuming Proposed Standard Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an Abstract section. ** The document seems to lack an Introduction section. (A line matching the expected section header was found, but with an unexpected indentation: ' 2. Background' ) ** The document seems to lack a Security Considerations section. (A line matching the expected section header was found, but with an unexpected indentation: ' 4. Security Considerations' ) ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) ** The document seems to lack an Authors' Addresses Section. ** There are 5 instances of too long lines in the document, the longest one being 2 characters in excess of 72. Miscellaneous warnings: ---------------------------------------------------------------------------- == Couldn't figure out when the document was first submitted -- there may comments or warnings related to the use of a disclaimer for pre-RFC5378 work that could not be issued because of this. Please check the Legal Provisions document at https://trustee.ietf.org/license-info to determine if you need the pre-RFC5378 disclaimer. -- Couldn't find a document date in the document -- date freshness check skipped. Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) -- Missing reference section? '1' on line 220 looks like a reference -- Missing reference section? '2' on line 224 looks like a reference -- Missing reference section? '3' on line 228 looks like a reference -- Missing reference section? '4' on line 231 looks like a reference -- Missing reference section? '5' on line 235 looks like a reference -- Missing reference section? '6' on line 238 looks like a reference -- Missing reference section? '7' on line 241 looks like a reference -- Missing reference section? '8' on line 247 looks like a reference -- Missing reference section? '9' on line 253 looks like a reference Summary: 14 errors (**), 0 flaws (~~), 2 warnings (==), 10 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Internet Draft SNMP over OSI July 92 4 SNMP over OSI 6 Tue Jul 14 19:58:54 1992 8 Marshall T. Rose 9 Dover Beach Consulting, Inc. 10 mrose@dbc.mtview.ca.us 12 1. Status of this Memo 14 This document is an Internet Draft. Internet Drafts are 15 working documents of the Internet Engineering Task Force 16 (IETF), its Areas, and its Working Groups. Note that other 17 groups may also distribute working documents as Internet 18 Drafts. 20 Internet Drafts are draft documents valid for a maximum of six 21 months. Internet Drafts may be updated, replaced, or 22 obsoleted by other documents at any time. It is not 23 appropriate to use Internet Drafts as reference material or to 24 cite them other than as a "working draft" or "work in 25 progress". 27 Please check the 1id-abstracts.txt listing contained in the 28 internet-drafts Shadow Directories on nic.ddn.mil, 29 nnsc.nsf.net, nic.nordu.net, ftp.nisc.sri.com, or 30 munnari.oz.au to learn the current status of any Internet 31 Draft. 33 This draft document is being circulated for comment. If 34 consensus is reached in the IETF's "SNMP in a Multi-Protocol 35 Internet" working group, it will be submitted to the RFC 36 editor as a Proposed Standard protocol specification. Please 37 send comments to the author. 39 If published as an RFC, this document will obsolete RFCs 1161 40 and 1283. 42 Internet Draft SNMP over OSI July 92 44 2. Background 46 The Simple Network Management Protocol (SNMP) as defined in 47 [1] is now used as an integral part of the network management 48 framework for TCP/IP-based internets. Together with its 49 companions standards, which define the Structure of Management 50 Information (SMI) [2,3], and the Management Information Base 51 (MIB) [4], the SNMP has received widespread deployment in many 52 operational networks running the Internet suite of protocols. 54 It should not be surprising that many of these sites might 55 acquire OSI capabilities and may wish to leverage their 56 investment in SNMP technology towards managing those OSI 57 components. This memo addresses these concerns by defining a 58 framework for running the SNMP in an environment which 59 supports the OSI connectionless-mode transport service. 61 However, as noted in [5], the preferred mapping for SNMP is 62 onto the UDP[6]. As such, this specification is intended for 63 use in environments where UDP transport is not available. No 64 aspect of this specification should be construed as a 65 suggestion that, in a heterogeneous transport environment, a 66 managed agent should support more than one mapping. 67 Conversely, management stations are strongly encouraged to 68 support mappings of SNMP onto all popular transports. 70 Internet Draft SNMP over OSI July 92 72 3. Mapping onto the CLTS 74 Mapping the SNMP onto the CLTS[7,8] is straight-forward. The 75 elements of procedure are identical to that of using the UDP. 76 Note that the CLTS and the service offered by the UDP both 77 transmit packets of information which contain full addressing 78 information. Thus, mapping the SNMP onto the CLTS, a 79 "transport address" in the context of [1], is simply a 80 transport-selector and network address. 82 It should be noted that the mapping of SNMP onto a 83 connectionless-mode transport service is wholly consistent 84 with SNMP's architectural principles, as described in [1,5]. 85 However, the CLTS itself can be realized using either a 86 connectionless-mode or a connection-oriented network service. 87 The mapping described in this mapping allows for either 88 realization. (When both network services are available, the 89 CLNS should be used as the basis of realization.) 91 3.1. Well-known Addresses 93 Unlike the Internet suite of protocols, OSI does not use 94 well-known ports. Rather, 95 demultiplexing occurs on the basis of "selectors", opaque 96 strings of octets which have local significance. In order to 97 foster interoperable implementations of the SNMP over the 98 CLTS, it is necessary define four selectors for this purpose. 100 When the CLTS is used to provide the transport backing for the 101 SNMP, and the CLTS uses a connectionless-mode network service, 102 then transport selector used shall be "snmp-l" which consists 103 of six ASCII characters; and, SNMP traps are, by convention, 104 sent to an SNMP manager listening on the transport selector 105 "snmpt-l" which consists of seven ASCII characters. 107 When the CLTS is used to provide the transport backing for the 108 SNMP, and the CLTS uses a connection-oriented network service, 109 then transport selector used shall be "snmp-o" which consists 110 of six ASCII characters; and, SNMP traps are, by convention, 111 sent to an SNMP manager listening on the transport selector 112 "snmpt-o" which consists of seven ASCII characters. 114 Internet Draft SNMP over OSI July 92 116 3.2. Traps 118 When SNMP traps are sent over the CLTS, the agent-addr field 119 in the Trap-PDU contains the IP-address "0.0.0.0" An SNMP 120 manager may ascertain the source of the trap based on 121 information provided by the transport service (i.e., from the 122 T-UNIT-DATA.INDICATION primitive). 124 3.3. Maximum Message Size 126 An entity implementing SNMP over OSI must be prepared to 127 accept messages whose size is at least 484 octets. 128 Implementation of larger values is encouraged whenever 129 possible. 131 3.4. Party Information 133 For use with the Party MIB [9], SNMP mapped onto the CLTS 134 (using a CL-mode network service) is referenced as the 135 "rfcXxxxlDomain". Similarly, SNMP mapped onto the CLTS (using 136 a CO-mode network service) is referenced as the 137 "rfcXxxxoDomain". 139 Internet Draft SNMP over OSI July 92 141 RFCxxxx DEFINITIONS ::= BEGIN 143 IMPORTS 144 experimental 145 FROM RFC1155-SMI; 147 -- If this document is issued as an RFC -- 148 -- then these OID assignments will be changed -- 150 snmpOverOSI OBJECT IDENTIFIER ::= 151 { experimental xx } 153 snmpOverOSIdomains OBJECT IDENTIFIER ::= 154 { smpOverOSI 1 } 156 rfcXxxxlDomain OBJECT IDENTIFIER ::= 157 { snmpOverOSIdomains 1 } 159 rfcXxxxoDomain OBJECT IDENTIFIER ::= 160 { snmpOverOSIdomains 2 } 162 -- For either rfcXxxxlDomain or rfcXxxxoDomain, a 163 -- TAddress is `m' octets long. The initial octet 164 -- indicates the length of the NSAP, `n', octets 2 165 -- through `n+1' contain the NSAP using the concrete 166 -- binary representation, and the remaining octets (if any) 167 -- contain the transport selector. 169 Internet Draft SNMP over OSI July 92 171 -- When devices are installed, they need to be configured 172 -- with an initial set of SNMP parties. The configuration 173 -- of SNMP parties requires (among other things) the 174 -- assignment of several OBJECT IDENTIFIERs. Any local network 175 -- administration can obtain the delegated authority necessary 176 -- to assign its own OBJECT IDENTIFIERs. However, to cater 177 -- for those administrations who have not obtained the necessary 178 -- authority, this document allocates a branch of the naming 179 -- tree for use with the following conventions. 181 initialOSIPartyId OBJECT IDENTIFIER ::= 182 { snmpOverOSI 2 } 184 -- This prefix is used in an analogous fashion as 185 -- 186 -- initialPartyId 187 -- 188 -- as defined in [9]. For an SNMP protocol entity residing at 189 -- NSAP `N' (with length `n'), the identities of its six initial 190 -- parties are formed by appending `n' sub-identifiers, one 191 -- sub-identifier for each octet in the NSAP, to 192 -- 193 -- initialOSIPartyId 194 -- 195 -- NB: 1. If the device being configured has at least one 196 -- IP-address, then the initialPartyId prefix defined in 197 -- the Party MIB should be used instead of the 198 -- initialOSIPartyId prefix. 199 -- 200 -- 2. Use of the initialOSIPartyId prefix is not necessary 201 -- for operation of the SNMP over the CLTS. 203 END 204 Internet Draft SNMP over OSI July 92 206 4. Security Considerations 208 Security issues are not discussed in this memo. 210 5. Acknowledgements 212 This specification was derived from RFC 1283, based on 213 discussions in the IETF's "SNMP in a Multi-Protocol Internet" 214 working group. 216 Internet Draft SNMP over OSI July 92 218 6. References 220 [1] J.D. Case, M.S. Fedor, M.L. Schoffstall, and J.R. Davin, 221 Simple Network Management Protocol. Request for Comments 222 1157, (May, 1990). 224 [2] M.T. Rose, K. McCloghrie, Structure and Identification of 225 Management Information for TCP/IP-based internets. 226 Request for Comments 1155, (May, 1990). 228 [3] M.T. Rose, K. McCloghrie, Concise MIB Definitions. 229 Request for Comments 1212, (March, 1991). 231 [4] K. McCloghrie, M.T. Rose, Management Information Base for 232 Network Management of TCP/IP-based internets. Request 233 for Comments 1213, (March, 1991). 235 [5] F. Kastenholz, SNMP Communication Services. Request for 236 Comments 1270, (October, 1991). 238 [6] J.B. Postel, User Datagram Protocol. Request for 239 Comments 768, (August, 1980). 241 [7] Information processing systems - Open Systems 242 Interconnection - Transport Service Definition - Addendum 243 1: Connectionless-mode Transmission, International 244 Organization for Standardization. International Standard 245 8072/AD 1, (June, 1986). 247 [8] Information processing systems - Open Systems 248 Interconnection - Protocol Specification for Providing 249 the Connectionless-mode Transport Service, International 250 Organization for Standardization. International Standard 251 8602, (December, 1987). 253 [9] K. McCloghrie, J.D. Davin, J.M. Galvin, Definitions of 254 Managed Objects for Administration of SNMP Parties. 255 Request for Comments 1353, (July, 1992). 257 Internet Draft SNMP over OSI July 92 259 Table of Contents 261 1 Status of this Memo ................................... 1 262 2 Background ............................................ 2 263 3 Mapping onto the CLTS ................................. 3 264 3.1 Well-known Addresses ................................ 3 265 3.2 Traps ............................................... 4 266 3.3 Maximum Message Size ................................ 4 267 3.4 Party Information ................................... 4 268 4 Security Considerations ............................... 1 269 5 Acknowledgements ...................................... 1 270 6 References ............................................ 2