draft-ietf-snmpv3-update-transmap-01.txt   draft-ietf-snmpv3-update-transmap-02.txt 
skipping to change at page 1, line 14 skipping to change at page 1, line 14
STD: XXX BMC Software, Inc. STD: XXX BMC Software, Inc.
Obsoletes: 1906 Authors of previous version: Obsoletes: 1906 Authors of previous version:
Category: Standards Track J. Case Category: Standards Track J. Case
SNMP Research, Inc. SNMP Research, Inc.
K. McCloghrie K. McCloghrie
Cisco Systems, Inc. Cisco Systems, Inc.
M. Rose M. Rose
Dover Beach Consulting, Inc. Dover Beach Consulting, Inc.
S. Waldbusser S. Waldbusser
International Network Services International Network Services
23 January 2000
Transport Mappings for Transport Mappings for
the Simple Network Management Protocol the Simple Network Management Protocol
<draft-ietf-snmpv3-update-transmap-01.txt> <draft-ietf-snmpv3-update-transmap-02.txt>
Status of this Memo Status of this Memo
This document is an Internet-Draft and is in full conformance with This document is an Internet-Draft and is in full conformance with
all provisions of Section 10 of RFC2026. Internet-Drafts are working all provisions of Section 10 of RFC2026. Internet-Drafts are working
documents of the Internet Engineering Task Force (IETF), its areas, documents of the Internet Engineering Task Force (IETF), its areas,
and its working groups. Note that other groups may also distribute and its working groups. Note that other groups may also distribute
working documents as Internet-Drafts. working documents as Internet-Drafts.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
skipping to change at page 2, line 9 skipping to change at page 2, line 9
Abstract Abstract
This document is intended to obsolete RFC 1906, Transport Mappings This document is intended to obsolete RFC 1906, Transport Mappings
for Version 2 of the Simple Network Management Protocol (SNMPv2). It for Version 2 of the Simple Network Management Protocol (SNMPv2). It
defines the transport of SNMP messages over various protocols. defines the transport of SNMP messages over various protocols.
Table of Contents Table of Contents
1. Introduction ................................................ 3 1. Introduction ................................................ 3
2. Definitions ................................................. 4 2. Definitions ................................................. 4
3. SNMP over UDP ............................................... 7 3. SNMP over UDP over IPv4 ..................................... 7
3.1. Serialization ............................................. 7 3.1. Serialization ............................................. 7
3.2. Well-known Values ......................................... 8 3.2. Well-known Values ......................................... 8
4. SNMP over OSI ............................................... 8 4. SNMP over OSI ............................................... 8
4.1. Serialization ............................................. 8 4.1. Serialization ............................................. 8
4.2. Well-known Values ......................................... 8 4.2. Well-known Values ......................................... 8
5. SNMP over DDP ............................................... 8 5. SNMP over DDP ............................................... 8
5.1. Serialization ............................................. 8 5.1. Serialization ............................................. 8
5.2. Well-known Values ......................................... 9 5.2. Well-known Values ......................................... 9
5.3. Discussion of AppleTalk Addressing ........................ 9 5.3. Discussion of AppleTalk Addressing ........................ 9
5.3.1. How to Acquire NBP names ................................ 10 5.3.1. How to Acquire NBP names ................................ 10
skipping to change at page 4, line 5 skipping to change at page 4, line 5
termed the Management Information Base or MIB. Objects in the termed the Management Information Base or MIB. Objects in the
MIB are defined using the mechanisms defined in the SMI. MIB are defined using the mechanisms defined in the SMI.
This document, Transport Mappings for the Simple Network This document, Transport Mappings for the Simple Network
Management Protocol, defines how the management protocol [RFC- Management Protocol, defines how the management protocol [RFC-
PROTO] may be carried over a variety of protocol suites. It is PROTO] may be carried over a variety of protocol suites. It is
the purpose of this document to define how the SNMP maps onto an the purpose of this document to define how the SNMP maps onto an
initial set of transport domains. Other mappings may be defined initial set of transport domains. Other mappings may be defined
in the future. in the future.
Although several mappings are defined, the mapping onto UDP is Although several mappings are defined, the mapping onto UDP over
the preferred mapping. As such, to provide for the greatest IPv4 is the preferred mapping. As such, to provide for the
level of interoperability, systems which choose to deploy other greatest level of interoperability, systems which choose to
mappings should also provide for proxy service to the UDP deploy other mappings should also provide for proxy service to
mapping. the UDP over IPv4 mapping.
2. Definitions 2. Definitions
SNMPv2-TM DEFINITIONS ::= BEGIN SNMPv2-TM DEFINITIONS ::= BEGIN
IMPORTS ! IMPORTS
MODULE-IDENTITY, OBJECT-IDENTITY, ! MODULE-IDENTITY, OBJECT-IDENTITY,
snmpModules, snmpDomains, snmpProxys snmpModules, snmpDomains, snmpProxys
FROM SNMPv2-SMI FROM SNMPv2-SMI
TEXTUAL-CONVENTION TEXTUAL-CONVENTION
FROM SNMPv2-TC; FROM SNMPv2-TC;
snmpv2tm MODULE-IDENTITY ! snmpv2tm MODULE-IDENTITY
LAST-UPDATED "200001231839Z" ! LAST-UPDATED "200004032350Z"
ORGANIZATION "IETF SNMPv3 Working Group" ! ORGANIZATION "IETF SNMPv3 Working Group"
CONTACT-INFO ! CONTACT-INFO
"WG-EMail: snmpv3@tis.com ! "WG-EMail: snmpv3@tis.com
Subscribe: majordomo@tis.com ! Subscribe: majordomo@tis.com
In message body: subscribe snmpv3 ! In message body: subscribe snmpv3
Chair: Russ Mundy ! Chair: Russ Mundy
TIS Labs at Network Associates ! TIS Labs at Network Associates
postal: 3060 Washington Rd ! postal: 3060 Washington Rd
Glenwood MD 21738 ! Glenwood MD 21738
USA ! USA
EMail: mundy@tislabs.com ! EMail: mundy@tislabs.com
phone: +1 301 854-6889 ! phone: +1 301 854-6889
Editor: Randy Presuhn ! Editor: Randy Presuhn
BMC Software, Inc. ! BMC Software, Inc.
postal: 2141 North First Street ! postal: 2141 North First Street
San Jose, CA 95131 ! San Jose, CA 95131
USA ! USA
EMail: randy_presuhn@bmc.com ! EMail: randy_presuhn@bmc.com
phone: +1 408 546-1006" ! phone: +1 408 546-1006"
DESCRIPTION ! DESCRIPTION
"The MIB module for SNMP transport mappings." ! "The MIB module for SNMP transport mappings."
REVISION "200001231839Z" ! REVISION "200004032350Z"
DESCRIPTION ! DESCRIPTION
"Clarifications, published as ! "Clarifications, published as
<draft-ietf-snmpv3-update-transmap-01.txt>" ! <draft-ietf-snmpv3-update-transmap-02.txt>"
REVISION "199601010000Z" ! REVISION "199601010000Z"
DESCRIPTION ! DESCRIPTION
"Clarifications, published as RFC 1906." ! "Clarifications, published as RFC 1906."
REVISION "199304010000Z" ! REVISION "199304010000Z"
DESCRIPTION ! DESCRIPTION
"The initial version, published as RFC 1449." ! "The initial version, published as RFC 1449."
::= { snmpModules ?? } -- to be assigned by IANA?? ! ::= { snmpModules ?? } -- to be assigned by IANA??
-- SNMP over UDP over IPv4 -- SNMP over UDP over IPv4
snmpUDPDomain OBJECT-IDENTITY snmpUDPDomain OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The SNMP over UDP transport domain. The corresponding "The SNMP over UDP over IPv4 transport domain.
transport address is of type SnmpUDPAddress." The corresponding transport address is of type
SnmpUDPAddress."
::= { snmpDomains 1 } ::= { snmpDomains 1 }
SnmpUDPAddress ::= TEXTUAL-CONVENTION SnmpUDPAddress ::= TEXTUAL-CONVENTION
DISPLAY-HINT "1d.1d.1d.1d/2d" DISPLAY-HINT "1d.1d.1d.1d/2d"
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents a UDP address: "Represents a UDP over IPv4 address:
octets contents encoding octets contents encoding
1-4 IP-address network-byte order 1-4 IP-address network-byte order
5-6 UDP-port network-byte order 5-6 UDP-port network-byte order
" "
SYNTAX OCTET STRING (SIZE (6)) SYNTAX OCTET STRING (SIZE (6))
-- SNMP over OSI -- SNMP over OSI
snmpCLNSDomain OBJECT-IDENTITY snmpCLNSDomain OBJECT-IDENTITY
skipping to change at page 7, line 33 skipping to change at page 7, line 33
" "
SYNTAX OCTET STRING (SIZE (12)) SYNTAX OCTET STRING (SIZE (12))
-- for proxy to SNMPv1 (RFC 1157) -- for proxy to SNMPv1 (RFC 1157)
rfc1157Proxy OBJECT IDENTIFIER ::= { snmpProxys 1 } rfc1157Proxy OBJECT IDENTIFIER ::= { snmpProxys 1 }
rfc1157Domain OBJECT-IDENTITY rfc1157Domain OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The transport domain for SNMPv1 over UDP. "The transport domain for SNMPv1 over UDP over IPv4.
The corresponding transport address is of type The corresponding transport address is of type
SnmpUDPAddress." SnmpUDPAddress."
::= { rfc1157Proxy 1 } ::= { rfc1157Proxy 1 }
-- ::= { rfc1157Proxy 2 } this OID is obsolete -- ::= { rfc1157Proxy 2 } this OID is obsolete
END END
3. SNMP over UDP 3. SNMP over UDP over IPv4
This is the preferred transport mapping. This is the preferred transport mapping.
3.1. Serialization 3.1. Serialization
Each instance of a message is serialized (i.e., encoded according to Each instance of a message is serialized (i.e., encoded according to
the convention of [ASN1]) onto a single UDP [RFC768] the convention of [ASN1]) onto a single UDP [RFC768] over IPv4
datagram, using the algorithm specified in Section 8. [RFC791] datagram, using the algorithm specified in Section 8.
3.2. Well-known Values 3.2. Well-known Values
It is suggested that administrators configure their SNMP entities It is suggested that administrators configure their SNMP entities
supporting command responder applications to listen on UDP port 161. supporting command responder applications to listen on UDP port 161.
Further, it is suggested that SNMP entities supporting notification Further, it is suggested that SNMP entities supporting notification
receiver applications be configured to listen on UDP port 162. receiver applications be configured to listen on UDP port 162.
When an SNMP entity uses this transport mapping, it must be capable When an SNMP entity uses this transport mapping, it must be capable
of accepting messages up to and including 484 octets in size. It is ! of accepting messages up to and including 484 octets in size. It is
recommended that implementations be capable of accepting messages of ! recommended that implementations be capable of accepting messages of
up to 1472 octets in size. Implementation of larger values is ! up to 1472 octets in size. Implementation of larger values is
encouraged whenever possible. encouraged whenever possible.
4. SNMP over OSI 4. SNMP over OSI
This is an optional transport mapping. This is an optional transport mapping.
4.1. Serialization 4.1. Serialization
Each instance of a message is serialized onto a single TSDU [IS8072] Each instance of a message is serialized onto a single TSDU [IS8072]
[IS8072A] for the OSI Connectionless-mode Transport Service (CLTS), [IS8072A] for the OSI Connectionless-mode Transport Service (CLTS),
skipping to change at page 12, line 35 skipping to change at page 12, line 35
supporting notification receiver applications be configured to listen supporting notification receiver applications be configured to listen
on IPX socket 36880 (9010 hexadecimal). on IPX socket 36880 (9010 hexadecimal).
When an SNMP entity uses this transport mapping, it must be capable When an SNMP entity uses this transport mapping, it must be capable
of accepting messages that are at least 546 octets in size. of accepting messages that are at least 546 octets in size.
Implementation of larger values is encouraged whenever possible. Implementation of larger values is encouraged whenever possible.
7. Proxy to SNMPv1 7. Proxy to SNMPv1
Historically, in order to support proxy to SNMPv1, as defined in Historically, in order to support proxy to SNMPv1, as defined in
[RFC-COEX], it was deemed useful to define a transport domain, [RFC2576], it was deemed useful to define a transport domain,
rfc1157Domain, which indicates the transport mapping for SNMP rfc1157Domain, which indicates the transport mapping for SNMP
messages as defined in [RFC1157]. Subsequently, this transport messages as defined in [RFC1157]. Subsequently, this transport
domain has proven useful in non-proxy situations. domain has proven useful in non-proxy situations.
8. Serialization using the Basic Encoding Rules 8. Serialization using the Basic Encoding Rules
When the Basic Encoding Rules [BER] are used for serialization: When the Basic Encoding Rules [BER] are used for serialization:
(1) When encoding the length field, only the definite form is used; (1) When encoding the length field, only the definite form is used;
use of the indefinite form encoding is prohibited. Note that use of the indefinite form encoding is prohibited. Note that
skipping to change at page 16, line 23 skipping to change at page 16, line 23
Shawn Routhier Shawn Routhier
Jon Saperia Jon Saperia
Juergen Schoenwaelder Juergen Schoenwaelder
Bob Stewart Bob Stewart
Kaj Tesink Kaj Tesink
Glenn Waters Glenn Waters
Bert Wijnen Bert Wijnen
11. Security Considerations 11. Security Considerations
SNMPv1 by itself is not a secure environment. Even if the network ! SNMPv1 by itself is not a secure environment. Even if the network
itself is secure (for example by using IPSec), even then, there is no ! itself is secure (for example by using IPSec), even then, there is no
control as to who on the secure network is allowed to access and ! control as to who on the secure network is allowed to access and
GET/SET (read/change) the objects accessible through a command ! GET/SET (read/change) the objects accessible through a command
responder application. ! responder application.
It is recommended that the implementors consider the security ! It is recommended that the implementors consider the security
features as provided by the SNMPv3 framework. Specifically, the use ! features as provided by the SNMPv3 framework. Specifically, the use
of the User-based Security Model RFC 2574 [RFC2574] and the ! of the User-based Security Model RFC 2574 [RFC2574] and the
View-based Access Control Model RFC 2575 [RFC2575] is recommended. ! View-based Access Control Model RFC 2575 [RFC2575] is recommended.
It is then a customer/user responsibility to ensure that the SNMP ! It is then a customer/user responsibility to ensure that the SNMP
entity giving access to a MIB is properly configured to give access ! entity giving access to a MIB is properly configured to give access
to the objects only to those principals (users) that have legitimate ! to the objects only to those principals (users) that have legitimate
rights to indeed GET or SET (change) them. ! rights to indeed GET or SET (change) them.
12. References 12. References
[RFC768] Postel, J., "User Datagram Protocol", STD 6, RFC 768, [APPLETALK] Sidhu, G., Andrews, R., and A. Oppenheimer, Inside
USC/Information Sciences Institute, August 1980. AppleTalk (second edition). Addison-Wesley, 1990.
[BER] Information processing systems - Open Systems
Interconnection - Specification of Basic Encoding Rules
for Abstract Syntax Notation One (ASN.1), International
Organization for Standardization. International Standard
8825, December 1987.
[IS8072] Information processing systems - Open Systems [IS8072] Information processing systems - Open Systems
Interconnection - Transport Service Definition, Interconnection - Transport Service Definition,
International Organization for Standardization. International Organization for Standardization.
International Standard 8072, June 1986. International Standard 8072, June 1986.
[IS8072A] Information processing systems - Open Systems [IS8072A] Information processing systems - Open Systems
Interconnection - Transport Service Definition - Addendum Interconnection - Transport Service Definition - Addendum
1: Connectionless-mode Transmission, International 1: Connectionless-mode Transmission, International
Organization for Standardization. International Standard Organization for Standardization. International Standard
8072/AD 1, December 1986. 8072/AD 1, December 1986.
[APPLETALK] Sidhu, G., Andrews, R., and A. Oppenheimer, Inside
AppleTalk (second edition). Addison-Wesley, 1990.
[RFC1742] Waldbusser, S. and K. Frisa, "AppleTalk Management
Information Base II", RFC 1742, January 1995.
[NOVELL] Network System Technical Interface Overview. Novell, [NOVELL] Network System Technical Interface Overview. Novell,
Inc, June 1989. Inc, June 1989.
[RFC-COEX] Frye, R., Levi, D., Routhier, S., and B. Wijnen, [RFC768] Postel, J., "User Datagram Protocol", STD 6, RFC 768,
"Coexistence between Version 1, Version 2, and Version 3 August 1980.
of the Internet-standard Network Management Framework",
<draft-ietf-snmpv3-coex-07.txt>, January, 2000.
[BER] Information processing systems - Open Systems
Interconnection - Specification of Basic Encoding Rules
for Abstract Syntax Notation One (ASN.1), International
Organization for Standardization. International Standard
8825, December 1987.
[RFC2571] Harrington, D., Presuhn, R., and B. Wijnen, "An [RFC791] Postel, J., "Internet Protocol", STD 5, RFC 791,
Architecture for Describing SNMP Management Frameworks", September 1981.
RFC 2571, April 1999.
[RFC1155] Rose, M., and K. McCloghrie, "Structure and [RFC1155] Rose, M., and K. McCloghrie, "Structure and
Identification of Management Information for TCP/IP-based Identification of Management Information for TCP/IP-based
Internets", STD 16, RFC 1155, May 1990. Internets", STD 16, RFC 1155, May 1990.
[RFC1157] Case, J., Fedor, M., Schoffstall, M., and J. Davin,
"Simple Network Management Protocol", STD 15, RFC 1157,
May 1990.
[RFC1212] Rose, M., and K. McCloghrie, "Concise MIB Definitions", [RFC1212] Rose, M., and K. McCloghrie, "Concise MIB Definitions",
STD 16, RFC 1212, March 1991. STD 16, RFC 1212, March 1991.
[RFC1215] Rose, M., "A Convention for Defining Traps for use with [RFC1215] Rose, M., "A Convention for Defining Traps for use with
the SNMP", RFC 1215, March 1991. the SNMP", RFC 1215, March 1991.
[RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., [RFC1742] Waldbusser, S. and K. Frisa, "AppleTalk Management
Rose, M., and S. Waldbusser, "Structure of Management Information Base II", RFC 1742, January 1995.
Information Version 2 (SMIv2)", STD 58, RFC 2578, April
1999.
[RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
Rose, M., and S. Waldbusser, "Textual Conventions for
SMIv2", STD 58, RFC 2579, April 1999.
[RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
Rose, M., and S. Waldbusser, "Conformance Statements for
SMIv2", STD 58, RFC 2580, April 1999.
[RFC1157] Case, J., Fedor, M., Schoffstall, M., and J. Davin,
"Simple Network Management Protocol", STD 15, RFC 1157,
May 1990.
[RFC1901] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, [RFC1901] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser,
"Introduction to Community-based SNMPv2", RFC 1901, "Introduction to Community-based SNMPv2", RFC 1901,
January 1996. January 1996.
[RFC-TM] Presuhn, R., Case, J., McCloghrie, K., Rose, M., and S. [RFC2570] Case, J., Mundy, R., Partain, D., and B. Stewart,
Waldbusser, "Transport Mappings for the Simple Network "Introduction to Version 3 of the Internet-standard
Management Protocol", Network Management Framework", RFC 2570, April 1999.
<draft-ietf-snmpv3-update-transmap-01.txt>, January 2000.
[RFC2571] Harrington, D., Presuhn, R., and B. Wijnen, "An
Architecture for Describing SNMP Management Frameworks",
RFC 2571, April 1999.
[RFC2572] Case, J., Harrington D., Presuhn R., and B. Wijnen, [RFC2572] Case, J., Harrington D., Presuhn R., and B. Wijnen,
"Message Processing and Dispatching for the Simple "Message Processing and Dispatching for the Simple
Network Management Protocol (SNMP)", RFC 2572, April Network Management Protocol (SNMP)", RFC 2572, April
1999. 1999.
[RFC2573] Levi, D., Meyer, P., and B. Stewart, "SNMPv3
Applications", RFC 2573, April 1999.
[RFC2574] Blumenthal, U., and B. Wijnen, "User-based Security Model [RFC2574] Blumenthal, U., and B. Wijnen, "User-based Security Model
(USM) for version 3 of the Simple Network Management (USM) for version 3 of the Simple Network Management
Protocol (SNMPv3)", RFC 2574, April 1999. Protocol (SNMPv3)", RFC 2574, April 1999.
[RFC-PROTO] Presuhn, R., Case, J., McCloghrie, K., Rose, M., and S.
Waldbusser, "Protocol Operations for the Simple Network
Management Protocol",
<draft-ietf-snmpv3-update-proto-01.txt>, January 2000.
[RFC2573] Levi, D., Meyer, P., and B. Stewart, "SNMPv3
Applications", RFC 2573, April 1999.
[RFC2575] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based [RFC2575] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based
Access Control Model (VACM) for the Simple Network Access Control Model (VACM) for the Simple Network
Management Protocol (SNMP)", RFC 2575, April 1999. Management Protocol (SNMP)", RFC 2575, April 1999.
[RFC2570] Case, J., Mundy, R., Partain, D., and B. Stewart, [RFC2576] Frye, R., Levi, D., Routhier, S., and B. Wijnen,
"Introduction to Version 3 of the Internet-standard "Coexistence between Version 1, Version 2, and Version 3
Network Management Framework", RFC 2570, April 1999. of the Internet-standard Network Management Framework",
RFC 2576, March, 2000.
[RFC2233] McCloghrie, K., and F. Kastenholz, "The Interfaces Group [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
MIB using SMIv2", RFC 2233, November 1997. Rose, M., and S. Waldbusser, "Structure of Management
Information Version 2 (SMIv2)", STD 58, RFC 2578, April
1999.
[RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
Rose, M., and S. Waldbusser, "Textual Conventions for
SMIv2", STD 58, RFC 2579, April 1999.
[RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
Rose, M., and S. Waldbusser, "Conformance Statements for
SMIv2", STD 58, RFC 2580, April 1999.
[RFC-TM] Presuhn, R., Case, J., McCloghrie, K., Rose, M., and S.
Waldbusser, "Transport Mappings for the Simple Network
Management Protocol",
<draft-ietf-snmpv3-update-transmap-02.txt>, April 2000.
[RFC-PROTO] Presuhn, R., Case, J., McCloghrie, K., Rose, M., and S.
Waldbusser, "Protocol Operations for the Simple Network
Management Protocol",
<draft-ietf-snmpv3-update-proto-02.txt>, April 2000.
13. Editor's Address 13. Editor's Address
Randy Presuhn Randy Presuhn
BMC Software, Inc. BMC Software, Inc.
2141 North First Street 2141 North First Street
San Jose, CA 95131 San Jose, CA 95131
USA USA
Phone: +1 408 546-1006 Phone: +1 408 546-1006
 End of changes. 29 change blocks. 
123 lines changed or deleted 122 lines changed or added

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