draft-ietf-snmpv3-update-transmap-03.txt   draft-ietf-snmpv3-update-transmap-04.txt 
skipping to change at page 1, line 16 skipping to change at page 1, line 16
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
Transport Mappings for Transport Mappings for
the Simple Network Management Protocol the Simple Network Management Protocol
<draft-ietf-snmpv3-update-transmap-03.txt> <draft-ietf-snmpv3-update-transmap-04.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 1, line 43 skipping to change at page 1, line 43
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html http://www.ietf.org/shadow.html
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2000). All Rights Reserved. Copyright (C) The Internet Society (2000). All Rights Reserved.
Abstract Abstract
This document is intended to obsolete RFC 1906, Transport Mappings This document defines the transport of SNMP messages over various
for Version 2 of the Simple Network Management Protocol (SNMPv2). It protocols. This document obsoletes RFC 1906.
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 over IPv4 ..................................... 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
skipping to change at page 3, line 40 skipping to change at page 3, line 40
- Protocol operations for accessing management information. - Protocol operations for accessing management information.
The first set of protocol operations and associated PDU The first set of protocol operations and associated PDU
formats is described in STD 15, RFC 1157 [RFC1157]. A formats is described in STD 15, RFC 1157 [RFC1157]. A
second set of protocol operations and associated PDU second set of protocol operations and associated PDU
formats is described RFC -PROTO [RFC-PROTO]. formats is described RFC -PROTO [RFC-PROTO].
- A set of fundamental applications described in RFC 2573 - A set of fundamental applications described in RFC 2573
[RFC2573] and the view-based access control mechanism [RFC2573] and the view-based access control mechanism
described in RFC 2575 [RFC2575]. described in RFC 2575 [RFC2575].
A more detailed introduction to the SNMP Management Framework at A more detailed introduction to the SNMP Management Framework at the
the time of this writing can be found in RFC 2570 [RFC2570]. time of this writing can be found in RFC 2570 [RFC2570].
Managed objects are accessed via a virtual information store, Managed objects are accessed via a virtual information store, termed
termed the Management Information Base or MIB. Objects in the the Management Information Base or MIB. Objects in the MIB are
MIB are defined using the mechanisms defined in the SMI. 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
Management Protocol, defines how the management protocol [RFC- Protocol, defines how the management protocol [RFC-PROTO] may be
PROTO] may be carried over a variety of protocol suites. It is carried over a variety of protocol suites. It is the purpose of this
the purpose of this document to define how the SNMP maps onto an document to define how the SNMP maps onto an initial set of transport
initial set of transport domains. Other mappings may be defined domains. Other mappings may be defined in the future.
in the future.
Although several mappings are defined, the mapping onto UDP over Although several mappings are defined, the mapping onto UDP over IPv4
IPv4 is the preferred mapping. As such, to provide for the is the preferred mapping. As such, to provide for the greatest level
greatest level of interoperability, systems which choose to of interoperability, systems which choose to deploy other mappings
deploy other mappings should also provide for access via UDP should also provide for access via UDP over IPv4 mapping.
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 "200006030101Z" LAST-UPDATED "200007141725Z"
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
skipping to change at page 4, line 47 skipping to change at page 4, line 46
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 "200006030101Z" REVISION "200007141725Z"
DESCRIPTION DESCRIPTION
"Clarifications, published as "Clarifications, published as
<draft-ietf-snmpv3-update-transmap-03.txt>" <draft-ietf-snmpv3-update-transmap-04.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
skipping to change at page 11, line 21 skipping to change at page 11, line 21
5.3.3. How to Turn NBP names into DDP addresses 5.3.3. How to Turn NBP names into DDP addresses
If the only piece of information available is the NBP name, then an If the only piece of information available is the NBP name, then an
NBP lookup should be performed to turn that name into a DDP address. NBP lookup should be performed to turn that name into a DDP address.
However, if there is a piece of stale information, it can be used as However, if there is a piece of stale information, it can be used as
a hint to perform an NBP confirm (which sends a unicast to the a hint to perform an NBP confirm (which sends a unicast to the
network address which is presumed to be the target of the name network address which is presumed to be the target of the name
lookup) to see if the stale information is, in fact, still valid. lookup) to see if the stale information is, in fact, still valid.
An NBP name to DDP address mapping can also be confirmed implicitly An NBP name to DDP address mapping can also be confirmed implicitly
using only SNMP transactions. For example, an SNMP entity acting using only SNMP transactions. For example, an SNMP entity supporting
supporting command generator applications issuing a retrieval command generator applications issuing a retrieval operation could
operation could also retrieve the relevant objects from the NBP group also retrieve the relevant objects from the NBP group [RFC1742] for
[RFC1742] for the SNMP entity supporting the command responder the SNMP entity supporting the command responder application. This
application. This information can then be correlated with the source information can then be correlated with the source DDP address of the
DDP address of the response. response.
5.3.4. What if NBP is broken 5.3.4. What if NBP is broken
Under some circumstances, there may be connectivity between two SNMP Under some circumstances, there may be connectivity between two SNMP
entities, but the NBP mapping machinery may be broken, e.g., entities, but the NBP mapping machinery may be broken, e.g.,
o the NBP FwdReq (forward NBP lookup onto local attached network) o the NBP FwdReq (forward NBP lookup onto local attached network)
mechanism might be broken at a router on the other entity's mechanism might be broken at a router on the other entity's
network; or, network; or,
skipping to change at page 18, line 42 skipping to change at page 18, line 42
Rose, M., and S. Waldbusser, "Textual Conventions for Rose, M., and S. Waldbusser, "Textual Conventions for
SMIv2", STD 58, RFC 2579, April 1999. SMIv2", STD 58, RFC 2579, April 1999.
[RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
Rose, M., and S. Waldbusser, "Conformance Statements for Rose, M., and S. Waldbusser, "Conformance Statements for
SMIv2", STD 58, RFC 2580, April 1999. SMIv2", STD 58, RFC 2580, April 1999.
[RFC-TM] Presuhn, R., Case, J., McCloghrie, K., Rose, M., and S. [RFC-TM] Presuhn, R., Case, J., McCloghrie, K., Rose, M., and S.
Waldbusser, "Transport Mappings for the Simple Network Waldbusser, "Transport Mappings for the Simple Network
Management Protocol", Management Protocol",
<draft-ietf-snmpv3-update-transmap-03.txt>, June 2000. <draft-ietf-snmpv3-update-transmap-04.txt>, July 2000.
[RFC-PROTO] Presuhn, R., Case, J., McCloghrie, K., Rose, M., and S. [RFC-PROTO] Presuhn, R., Case, J., McCloghrie, K., Rose, M., and S.
Waldbusser, "Protocol Operations for the Simple Network Waldbusser, "Protocol Operations for the Simple Network
Management Protocol", Management Protocol",
<draft-ietf-snmpv3-update-proto-03.txt>, June 2000. <draft-ietf-snmpv3-update-proto-04.txt>, July 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
skipping to change at page 20, line 5 skipping to change at page 20, line 5
- Added MODULE-IDENTITY; - Added MODULE-IDENTITY;
- Re-wrote introduction section using current boilerplate; - Re-wrote introduction section using current boilerplate;
- Added recommendation for larger message size support; - Added recommendation for larger message size support;
- Added historical background on use of rfc1157Domain with - Added historical background on use of rfc1157Domain with
proxy and changed status to "deprecated". proxy and changed status to "deprecated".
- Added an abstract.
15. Issues 15. Issues
This section is to be deleted when it is time to publish this This section is to be deleted when it is time to publish this
document as an RFC. The issue labels are the same as those used in document as an RFC. The issue labels are the same as those used in
the on-line issues list at the on-line issues list at
ftp://amethyst.bmc.com/pub/snmpv3/Update567/rfc1906/index.html ftp://amethyst.bmc.com/pub/snmpv3/Update567/rfc1906/index.html
1906-01 Done; title changed. 1906-01 Done; title changed.
1906-02 Done; introduction clause replaced. 1906-02 Done; introduction clause replaced.
skipping to change at page 21, line 7 skipping to change at page 21, line 9
1906-16 Done; references and acknowledgments updated. 1906-16 Done; references and acknowledgments updated.
1906-17 Done; IPR and copyright notices updated. 1906-17 Done; IPR and copyright notices updated.
1906-18 Done; resolution required no changes. 1906-18 Done; resolution required no changes.
1906-19 Done; MODULE-IDENTITY added. 1906-19 Done; MODULE-IDENTITY added.
1906-20 Done; resolution was to make no change. 1906-20 Done; resolution was to make no change.
1906-21 Done; resolution was to make no change.
1906-22 Done; resolution was to make no change.
1906-23 Done; added abstract.
16. Full Copyright Statement 16. Full Copyright Statement
Copyright (C) The Internet Society (2000). All Rights Reserved. Copyright (C) The Internet Society (2000). All Rights Reserved.
This document and translations of it may be copied and furnished to This document and translations of it may be copied and furnished to
others, and derivative works that comment on or otherwise explain it others, and derivative works that comment on or otherwise explain it
or assist in its implementation may be prepared, copied, published or assist in its implementation may be prepared, copied, published
and distributed, in whole or in part, without restriction of any and distributed, in whole or in part, without restriction of any
kind, provided that the above copyright notice and this paragraph are kind, provided that the above copyright notice and this paragraph are
included on all such copies and derivative works. However, this included on all such copies and derivative works. However, this
 End of changes. 14 change blocks. 
31 lines changed or deleted 36 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/