draft-ietf-snmpv3-update-transmap-06.txt   draft-ietf-snmpv3-update-transmap-07.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
3 October 2001
Transport Mappings for Transport Mappings for
the Simple Network Management Protocol the Simple Network Management Protocol
<draft-ietf-snmpv3-update-transmap-06.txt> <draft-ietf-snmpv3-update-transmap-07.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 31 skipping to change at page 2, line 31
5.3.3. How to Turn NBP names into DDP addresses ................ 11 5.3.3. How to Turn NBP names into DDP addresses ................ 11
5.3.4. What if NBP is broken ................................... 11 5.3.4. What if NBP is broken ................................... 11
6. SNMP over IPX ............................................... 12 6. SNMP over IPX ............................................... 12
6.1. Serialization ............................................. 12 6.1. Serialization ............................................. 12
6.2. Well-known Values ......................................... 12 6.2. Well-known Values ......................................... 12
7. Proxy to SNMPv1 ............................................. 13 7. Proxy to SNMPv1 ............................................. 13
8. Serialization using the Basic Encoding Rules ................ 13 8. Serialization using the Basic Encoding Rules ................ 13
8.1. Usage Example ............................................. 13 8.1. Usage Example ............................................. 13
9. Notice on Intellectual Property ............................. 14 9. Notice on Intellectual Property ............................. 14
10. Acknowledgments ............................................ 15 10. Acknowledgments ............................................ 15
11. Security Considerations .................................... 16 11. IANA Considerations ........................................ 16
12. References ................................................. 17 12. Security Considerations .................................... 16
13. Editor's Address ........................................... 19 13. References ................................................. 17
14. Changes from RFC 1906 ...................................... 19 14. Editor's Address ........................................... 19
15. Issues ..................................................... 20 15. Changes from RFC 1906 ...................................... 19
16. Full Copyright Statement ................................... 21 16. Issues ..................................................... 20
17. Full Copyright Statement ................................... 21
1. Introduction 1. Introduction
The SNMP Management Framework at the time of this writing consists of The SNMP Management Framework at the time of this writing consists of
five major components: five major components:
- An overall architecture, described in RFC -ARC [RFC-ARC]. - An overall architecture, described in RFC -ARC [RFC-ARC].
- Mechanisms for describing and naming objects and events for - Mechanisms for describing and naming objects and events for
the purpose of management. The first version of this the purpose of management. The first version of this
skipping to change at page 4, line 27 skipping to change at page 4, line 27
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 "200107021829Z" ! LAST-UPDATED "200110040534Z" !
ORGANIZATION "IETF SNMPv3 Working Group" ! ORGANIZATION "IETF SNMPv3 Working Group" !
CONTACT-INFO ! CONTACT-INFO !
"WG-EMail: snmpv3@lists.tislabs.com "WG-EMail: snmpv3@lists.tislabs.com
Subscribe: snmpv3-request@lists.tislabs.com Subscribe: snmpv3-request@lists.tislabs.com
Co-Chair: Russ Mundy Co-Chair: Russ Mundy
NAI Labs, NAI Labs,
Network Associates, Inc. Network Associates, Inc.
postal: 3060 Washington Rd. postal: 3060 Washington Rd.
Glenwood, MD 21738 Glenwood, MD 21738
skipping to change at page 5, line 13 skipping to change at page 5, line 13
phone: +1 603 337-2614 phone: +1 603 337-2614
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 "200107021829Z" REVISION "200110040534Z"
DESCRIPTION DESCRIPTION
"Clarifications, published as RFC -TMM." "Clarifications, published as RFC -TMM."
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??
skipping to change at page 16, line 34 skipping to change at page 16, line 34
Randy Presuhn Randy Presuhn
Aleksey Romanov Aleksey Romanov
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. IANA Considerations
The SNMPv2-TM MIB module requires the allocation of a single object !
identifier for its MODULE-IDENTITY. IANA should allocate this object !
identifier in the snmpModules subtree, defined in the SNMPv2-SMI MIB !
module. !
12. 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 -USM [RFC-USM] and the ! of the User-based Security Model RFC -USM [RFC-USM] and the !
skipping to change at page 16, line 46 skipping to change at page 17, line 4
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 -USM [RFC-USM] and the ! of the User-based Security Model RFC -USM [RFC-USM] and the !
View-based Access Control Model RFC -ACM [RFC-ACM] is recommended. ! View-based Access Control Model RFC -ACM [RFC-ACM] 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 13. References
[APPLETALK] Sidhu, G., Andrews, R., and A. Oppenheimer, Inside [APPLETALK] Sidhu, G., Andrews, R., and A. Oppenheimer, Inside
AppleTalk (second edition). Addison-Wesley, 1990. AppleTalk (second edition). Addison-Wesley, 1990.
[BER] Information processing systems - Open Systems [BER] Information processing systems - Open Systems
Interconnection - Specification of Basic Encoding Rules Interconnection - Specification of Basic Encoding Rules
for Abstract Syntax Notation One (ASN.1), International for Abstract Syntax Notation One (ASN.1), International
Organization for Standardization. International Standard Organization for Standardization. International Standard
8825, December 1987. 8825, December 1987.
skipping to change at page 18, line 16 skipping to change at page 18, line 20
"Introduction to Community-based SNMPv2", RFC 1901, "Introduction to Community-based SNMPv2", RFC 1901,
January 1996. January 1996.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2570] Case, J., Mundy, R., Partain, D., and B. Stewart, [RFC2570] Case, J., Mundy, R., Partain, D., and B. Stewart,
"Introduction to Version 3 of the Internet-standard "Introduction to Version 3 of the Internet-standard
Network Management Framework", RFC 2570, April 1999. Network Management Framework", RFC 2570, April 1999.
[RFC-ARC] Harrington, D., Presuhn, R. and B. Wijnen, "An
Architecture for describing SNMP Management Frameworks",
<draft-ietf-snmpv3-arch-v2-01.txt>, July 2001.
[RFC-MPD] Case, J., Harrington, D., Presuhn, R. and B. Wijnen,
"Message Processing and Dispatching for the Simple
Network Management Protocol (SNMP)",
<draft-ietf-snmpv3-mpd-v2-01.txt>, July 2001.
[RFC-APL] Levi, D., Meyer, P. and B. Stewart, "SNMP Applications",
<draft-ietf-snmpv3-appl-v3-01.txt>, July 2001.
[RFC-USM] Blumenthal, U. and B. Wijnen, "The User-Based Security
Model for Version 3 of the Simple Network Management
Protocol (SNMPv3)",
<draft-ietf-snmpv3-usm-v2-rfc2574bis-01.txt>, July 2001.
[RFC-ACM] Wijnen, B., Presuhn, R. and K. McCloghrie, "View-based
Access Control Model for the Simple Network Management
Protocol (SNMP)", <draft-ietf-snmpv3-vacm-04.txt>,
February 1999. <draft-ietf-snmpv3-vacm-v2-01.txt>, July
2001.
[RFC-COEX] Frye, R., Levi, D., Routhier, S., and B. Wijnen,
"Coexistence between Version 1, Version 2, and Version 3
of the Internet-standard Network Management Framework",
<draft-ietf-snmpv3-coex-v2-01.txt>, July 2001.
[RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
Rose, M., and S. Waldbusser, "Structure of Management Rose, M., and S. Waldbusser, "Structure of Management
Information Version 2 (SMIv2)", STD 58, RFC 2578, April Information Version 2 (SMIv2)", STD 58, RFC 2578, April
1999. 1999.
[RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
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-TMM] Presuhn, R., Case, J., McCloghrie, K., Rose, M., and S. [RFC-TMM] 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-06.txt>, July 2001. <draft-ietf-snmpv3-update-transmap-07.txt>, October 2001.
[RFC-PRO] Presuhn, R., Case, J., McCloghrie, K., Rose, M., and S. [RFC-PRO] 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-06.txt>, July 2001. <draft-ietf-snmpv3-update-proto-07.txt>, October 2001.
13. Editor's Address [RFC-ARC] Harrington, D., Presuhn, R. and B. Wijnen, "An
Architecture for describing SNMP Management Frameworks",
<draft-ietf-snmpv3-arch-v2-01.txt>, October 2001.
[RFC-MPD] Case, J., Harrington, D., Presuhn, R. and B. Wijnen,
"Message Processing and Dispatching for the Simple
Network Management Protocol (SNMP)",
<draft-ietf-snmpv3-mpd-v2-01.txt>, October 2001.
[RFC-APL] Levi, D., Meyer, P. and B. Stewart, "SNMP Applications",
<draft-ietf-snmpv3-appl-v3-01.txt>, October 2001.
[RFC-USM] Blumenthal, U. and B. Wijnen, "The User-Based Security
Model for Version 3 of the Simple Network Management
Protocol (SNMPv3)",
<draft-ietf-snmpv3-usm-v2-rfc2574bis-01.txt>, October
2001.
[RFC-ACM] Wijnen, B., Presuhn, R. and K. McCloghrie, "View-based
Access Control Model for the Simple Network Management
Protocol (SNMP)", <draft-ietf-snmpv3-vacm-v2-01.txt>,
October 2001.
[RFC-COEX] Frye, R., Levi, D., Routhier, S., and B. Wijnen,
"Coexistence between Version 1, Version 2, and Version 3
of the Internet-standard Network Management Framework",
<draft-ietf-snmpv3-coex-v2-01.txt>, October 2001.
14. 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
EMail: randy_presuhn@bmc.com EMail: randy_presuhn@bmc.com
14. Changes from RFC 1906 15. Changes from RFC 1906
These are the changes from RFC 1906: These are the changes from RFC 1906:
- Corrected typo in IPR statement; - Corrected typo in IPR statement;
- Updated copyright date; - Updated copyright date;
- Updated with new editor's name and contact information; - Updated with new editor's name and contact information;
- Cosmetic fixes to layout and typography; - Cosmetic fixes to layout and typography;
skipping to change at page 20, line 27 skipping to change at page 20, line 31
- Added an abstract; - Added an abstract;
- Strengthened conformance requirement for support of the UDP - Strengthened conformance requirement for support of the UDP
over IPv4 mapping; over IPv4 mapping;
- Updated working group mailing list address; - Updated working group mailing list address;
- Added address of working group co-chair; - Added address of working group co-chair;
- Corrected error in BER example. - Corrected error in BER example;
15. Issues Added IANA considerations section.
16. 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 38 skipping to change at page 21, line 45
1906-20 Done; resolution was to the mapping onto UDP over IPv4 1906-20 Done; resolution was to the mapping onto UDP over IPv4
mandatory for systems which support IPv4. mandatory for systems which support IPv4.
1906-21 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-22 Done; resolution was to make no change.
1906-23 Done; added abstract. 1906-23 Done; added abstract.
16. Full Copyright Statement 17. Full Copyright Statement
Copyright (C) The Internet Society (2001). All Rights Reserved. Copyright (C) The Internet Society (2001). 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
document itself may not be modified in any way, such as by removing document itself may not be modified in any way, such as by removing
 End of changes. 16 change blocks. 
47 lines changed or deleted 58 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/