draft-ietf-snmpv2-tc-ds-03.txt   draft-ietf-snmpv2-tc-ds-04.txt 
Textual Conventions Textual Conventions
for Version 2 of the for Version 2 of the
Simple Network Management Protocol (SNMPv2) Simple Network Management Protocol (SNMPv2)
Fri Jun 30 23:59:59 1995 20 September 1995 |
draft-ietf-snmpv2-tc-ds-03.txt
Jeffrey D. Case draft-ietf-snmpv2-tc-ds-04.txt |
SNMP Research, Inc.
case@snmp.com
Keith McCloghrie Keith McCloghrie
Editor +
Cisco Systems, Inc. Cisco Systems, Inc.
kzm@cisco.com kzm@cisco.com
Marshall T. Rose Status of this Memo -
Dover Beach Consulting, Inc.
mrose@dbc.mtview.ca.us
Steven Waldbusser
Carnegie Mellon University
waldbusser@cmu.edu
Status of this Memo
This document is an Internet-Draft. Internet-Drafts are working This document is an Internet-Draft. Internet-Drafts are working
documents of the Internet Engineering Task Force (IETF), its areas, and documents of the Internet Engineering Task Force (IETF), its areas, and
its working groups. Note that other groups may also distribute working its working groups. Note that other groups may also distribute working
documents as Internet-Drafts. 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
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet- Drafts as reference material time. It is inappropriate to use Internet- Drafts as reference material
or to cite them other than as ``work in progress.'' or to cite them other than as ``work in progress.''
skipping to change at page 21, line 12 skipping to change at page 20, line 12
also to previously active rows which are set to, and left also to previously active rows which are set to, and left
in, the notInService state for a prolonged period. in, the notInService state for a prolonged period.
Conceptual Row Suspension Conceptual Row Suspension
When a conceptual row is `active', the management station When a conceptual row is `active', the management station
may issue a management protocol set operation which sets the may issue a management protocol set operation which sets the
instance of the status column to `notInService'. If the instance of the status column to `notInService'. If the
agent is unwilling to do so, the set operation fails with an agent is unwilling to do so, the set operation fails with an
error of `wrongValue'. Otherwise, the conceptual row is error of `wrongValue'. Otherwise, the conceptual row is
taken out of service, and a `noError' response is returned. taken out of service, and a `noError' response is returned. |
It is the responsibility of the DESCRIPTION clause of the It is the responsibility of the DESCRIPTION clause of the |
status column to indicate under what circumstances the status |
status column should be taken out of service (e.g., in order column to indicate under what circumstances the status
for the value of some other column of the same conceptual column should be taken out of service (e.g., in order for
row to be modified). the value of some other column of the same conceptual row to
be modified).
Conceptual Row Deletion Conceptual Row Deletion
For deletion of conceptual rows, a management protocol set For deletion of conceptual rows, a management protocol set
operation is issued which sets the instance of the status operation is issued which sets the instance of the status
column to `destroy'. This request may be made regardless of column to `destroy'. This request may be made regardless of
the current value of the status column (e.g., it is possible the current value of the status column (e.g., it is possible
to delete conceptual rows which are either `notReady', to delete conceptual rows which are either `notReady',
`notInService' or `active'.) If the operation succeeds, then `notInService' or `active'.) If the operation succeeds, then
all instances associated with the conceptual row are all instances associated with the conceptual row are
skipping to change at page 28, line 7 skipping to change at page 27, line 7
3.5. Mapping of the SYNTAX clause 3.5. Mapping of the SYNTAX clause
The SYNTAX clause, which must be present, defines abstract data The SYNTAX clause, which must be present, defines abstract data
structure corresponding to the textual convention. The data structure structure corresponding to the textual convention. The data structure
must be one of the alternatives defined in the ObjectSyntax CHOICE or must be one of the alternatives defined in the ObjectSyntax CHOICE or
the BITS construct (see section 7.1 in [2]). the BITS construct (see section 7.1 in [2]).
4. Acknowledgements 4. Acknowledgements
The authors wish to acknowledge the contributions of the SNMPv2 Working This document is the result of significant work by the four major
Group in general. In particular, the authors extend a special thanks contributors:
for the contributions of:
Jeffrey Case (SNMP Research, case@snmp.com)
Keith McCloghrie (Cisco Systems, kzm@cisco.com)
Marshall Rose (Dover Beach Consulting, mrose@dbc.mtview.ca.us)
Steven Waldbusser (International Network Services, stevew@uni.ins.com)
In addition, the contributions of the SNMPv2 Working Group are
acknowledged. In particular, a special thanks is extended for the
contributions of:
Alexander I. Alten (Novell)
Dave Arneson (Cabletron) Dave Arneson (Cabletron)
Uri Blumenthal (IBM) Uri Blumenthal (IBM)
Doug Book (Chipcom) Doug Book (Chipcom)
Kim Curran (Bell-Northern Research) Kim Curran (Bell-Northern Research)
Jim Galvin (Trusted Information Systems)
Maria Greene (Ascom Timeplex) Maria Greene (Ascom Timeplex)
Deirdre Kostick (Bellcore) Iain Hanson (Digital)
Dave Harrington (Cabletron) Dave Harrington (Cabletron)
Nguyen Hien (IBM)
Jeff Johnson (Cisco Systems) Jeff Johnson (Cisco Systems)
Michael Kornegay (Object Quest)
Deirdre Kostick (AT&T Bell Labs)
David Levi (SNMP Research) David Levi (SNMP Research)
Daniel Mahoney (Cabletron)
Bob Natale (ACE*COMM)
Brian O'Keefe (Hewlett Packard) Brian O'Keefe (Hewlett Packard)
Andrew Pearson (SNMP Research) Andrew Pearson (SNMP Research)
Dave Perkins (Bay Networks) Dave Perkins (Peer Networks)
Randy Presuhn (Peer Networks) Randy Presuhn (Peer Networks)
Aleksey Romanov (Quality Quorum)
Shawn Routhier (Epilogue) Shawn Routhier (Epilogue)
Bob Stewart (Cisco Systems) Jon Saperia (BGS Systems)
Bob Stewart (Cisco Systems, bstewart@cisco.com), chair
Kaj Tesink (Bellcore) Kaj Tesink (Bellcore)
Glenn Waters (Bell-Northern Research)
Bert Wijnen (IBM) Bert Wijnen (IBM)
5. References 5. References
[1] Information processing systems - Open Systems Interconnection - [1] Information processing systems - Open Systems Interconnection -
Specification of Abstract Syntax Notation One (ASN.1), Specification of Abstract Syntax Notation One (ASN.1),
International Organization for Standardization. International International Organization for Standardization. International
Standard 8824, (December, 1987). Standard 8824, (December, 1987).
[2] Case, J., McCloghrie, K., Rose, M., and Waldbusser, S., "Structure [2] McCloghrie, K., Editor, |
of Management Information for Version 2 of the Simple Network "Structure of Management Information for Version 2 of the Simple
Management Protocol (SNMPv2)", Internet Draft, SNMP Research, Inc., Network Management Protocol (SNMPv2)", Internet Draft, Cisco |
Cisco Systems, Dover Beach Consulting, Inc., Carnegie Mellon Systems, September 1995. |
University, May 1995.
6. Security Considerations 6. Security Considerations
Security issues are not discussed in this memo. Security issues are not discussed in this memo.
7. Authors' Addresses 7. Editor's Address
Jeffrey D. Case
SNMP Research, Inc.
3001 Kimberlin Heights Rd.
Knoxville, TN 37920-9716
US
Phone: +1 615 573 1434
Email: case@snmp.com
Keith McCloghrie Keith McCloghrie -
Cisco Systems, Inc. Cisco Systems, Inc.
170 West Tasman Drive 170 West Tasman Drive |
San Jose, CA 95134-1706 San Jose, CA 95134-1706 |
US US |
Phone: +1 408 526 5260 Phone: +1 408 526 5260
Email: kzm@cisco.com Email: kzm@cisco.com
Marshall T. Rose Table of Contents -
Dover Beach Consulting, Inc.
420 Whisman Court
Mountain View, CA 94043-2186
US
Phone: +1 415 968 1052
Email: mrose@dbc.mtview.ca.us
Steven Waldbusser
Carnegie Mellon University
5000 Forbes Ave
Pittsburgh, PA 15213
US
Phone: +1 412 268 6628
Email: waldbusser@cmu.edu
Table of Contents
1 Introduction .................................................... 3 1 Introduction .................................................... 2
1.1 A Note on Terminology ......................................... 4 1.1 A Note on Terminology ......................................... 3
2 Definitions ..................................................... 5 2 Definitions ..................................................... 4
3 Mapping of the TEXTUAL-CONVENTION macro ......................... 25 3 Mapping of the TEXTUAL-CONVENTION macro ......................... 24
3.1 Mapping of the DISPLAY-HINT clause ............................ 25 3.1 Mapping of the DISPLAY-HINT clause ............................ 24
3.2 Mapping of the STATUS clause .................................. 27 3.2 Mapping of the STATUS clause .................................. 26
3.3 Mapping of the DESCRIPTION clause ............................. 27 3.3 Mapping of the DESCRIPTION clause ............................. 26
3.4 Mapping of the REFERENCE clause ............................... 27 3.4 Mapping of the REFERENCE clause ............................... 26
3.5 Mapping of the SYNTAX clause .................................. 27 3.5 Mapping of the SYNTAX clause .................................. 26
4 Acknowledgements ................................................ 28 4 Acknowledgements ................................................ 27
5 References ...................................................... 28 5 References ...................................................... 28
6 Security Considerations ......................................... 29 6 Security Considerations ......................................... 29
7 Authors' Addresses .............................................. 29 7 Editor's Address ................................................ 29
 End of changes. 23 change blocks. 
75 lines changed or deleted 55 lines changed or added

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