draft-ietf-snmpv2-tc-ds-04.txt   draft-ietf-snmpv2-tc-ds-05.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)
20 September 1995 | 28 September 1995 |
draft-ietf-snmpv2-tc-ds-04.txt | draft-ietf-snmpv2-tc-ds-05.txt |
Keith McCloghrie Keith McCloghrie
Editor + Editor +
Cisco Systems, Inc. Cisco Systems, Inc.
kzm@cisco.com kzm@cisco.com
Status of this Memo - 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
skipping to change at page 3, line 9 skipping to change at page 3, line 9
For all textual conventions defined in an information module, the name For all textual conventions defined in an information module, the name
shall be unique and mnemonic, and shall not exceed 64 characters in shall be unique and mnemonic, and shall not exceed 64 characters in
length. (However, names longer than 32 characters are not recommended.) length. (However, names longer than 32 characters are not recommended.)
All names used for the textual conventions defined in all "standard" All names used for the textual conventions defined in all "standard"
information modules shall be unique. information modules shall be unique.
1.1. A Note on Terminology 1.1. A Note on Terminology
For the purpose of exposition, the original Internet-standard Network For the purpose of exposition, the original Internet-standard Network
Management Framework, as described in RFCs 1155, 1157, and 1212, is Management Framework, as described in RFCs 1155, 1157, and 1212, is
termed the SNMP version 1 framework (SNMPv1). The current framework is termed the SNMP version 1 framework (SNMPv1). The current framework is |
termed the SNMP version 2 framework (SNMPv2). termed the SNMP version 2 framework (SNMPv2), as described in [3]. |
2. Definitions 2. Definitions
SNMPv2-TC DEFINITIONS ::= BEGIN SNMPv2-TC DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
ObjectSyntax, TimeTicks ObjectSyntax, TimeTicks
FROM SNMPv2-SMI; FROM SNMPv2-SMI;
-- definition of textual conventions -- definition of textual conventions
skipping to change at page 19, line 38 skipping to change at page 19, line 38
protocol set operation is issued to set the status protocol set operation is issued to set the status
column to `active', the values held in the agent column to `active', the values held in the agent
supersede those used by the managed device. supersede those used by the managed device.
If the management station is prevented from setting the If the management station is prevented from setting the
status column to `active' (e.g., due to management station status column to `active' (e.g., due to management station
or network failure) the conceptual row will be left in the or network failure) the conceptual row will be left in the
`notInService' or `notReady' state, consuming resources `notInService' or `notReady' state, consuming resources
indefinitely. The agent must detect conceptual rows that indefinitely. The agent must detect conceptual rows that
have been in either state for an abnormally long period of have been in either state for an abnormally long period of
time and remove them. This period of time should be long time and remove them. It is the responsibility of the +
enough to allow for human response time (including `think DESCRIPTION clause of the status column to indicate what an +
time') between the creation of the conceptual row and the abnormally long period of time would be. +
setting of the status to `active'. It is suggested that This period of time should be long enough to allow for human
this period be approximately 5 minutes in length. This response time (including `think time') between the creation
removal action applies not only to newly-created rows, but of the conceptual row and the setting of the status to
also to previously active rows which are set to, and left `active'. In the absense of such information in the |
in, the notInService state for a prolonged period. DESCRIPTION clause, it is suggested that this period be |
approximately 5 minutes in length. |
This removal action applies not only to newly-created rows,
but also to previously active rows which are set to, and
left in, the notInService state for a prolonged period |
exceeding that which is considered normal for such a |
conceptual row. |
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 | status column to indicate under what circumstances the
column to indicate under what circumstances the status status column should be taken out of service (e.g., in order
column should be taken out of service (e.g., in order for for the value of some other column of the same conceptual
the value of some other column of the same conceptual row to row to be modified).
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 23, line 32 skipping to change at page 24, line 32
specify the columnar objects which a permanent(4) row must specify the columnar objects which a permanent(4) row must
at a minimum allow to be writable." at a minimum allow to be writable."
SYNTAX INTEGER { SYNTAX INTEGER {
other(1), -- eh? other(1), -- eh?
volatile(2), -- e.g., in RAM volatile(2), -- e.g., in RAM
nonVolatile(3), -- e.g., in NVRAM nonVolatile(3), -- e.g., in NVRAM
permanent(4), -- e.g., partially in ROM permanent(4), -- e.g., partially in ROM
readOnly(5) -- e.g., completely in ROM readOnly(5) -- e.g., completely in ROM
} }
TDomain ::= TEXTUAL-CONVENTION +
STATUS current +
DESCRIPTION +
"Denotes a kind of transport service. +
Some possible values, such as snmpUDPDomain, are defined in +
'Transport Mappings for Version 2 of the Simple Network +
Management Protocol (SNMPv2)'." +
SYNTAX OBJECT IDENTIFIER +
TAddress ::= TEXTUAL-CONVENTION +
STATUS current +
DESCRIPTION +
"Denotes a transport service address. +
For snmpUDPDomain, a TAddress is 6 octets long, the initial 4 +
octets containing the IP-address in network-byte order and the +
last 2 containing the UDP port in network-byte order. Consult +
'Transport Mappings for Version 2 of the Simple Network +
Management Protocol (SNMPv2)' for further information on +
snmpUDPDomain." +
SYNTAX OCTET STRING (SIZE (1..255)) +
END END
3. Mapping of the TEXTUAL-CONVENTION macro 3. Mapping of the TEXTUAL-CONVENTION macro
The TEXTUAL-CONVENTION macro is used to convey the syntax and semantics The TEXTUAL-CONVENTION macro is used to convey the syntax and semantics
associated with a textual convention. It should be noted that the associated with a textual convention. It should be noted that the
expansion of the TEXTUAL-CONVENTION macro is something which expansion of the TEXTUAL-CONVENTION macro is something which
conceptually happens during implementation and not during run-time. conceptually happens during implementation and not during run-time.
For all descriptors appearing in an information module, the descriptor For all descriptors appearing in an information module, the descriptor
skipping to change at page 29, line 5 skipping to change at page 30, line 17
[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] McCloghrie, K., Editor, | [2] McCloghrie, K., Editor, |
"Structure of Management Information for Version 2 of the Simple "Structure of Management Information for Version 2 of the Simple
Network Management Protocol (SNMPv2)", Internet Draft, Cisco | Network Management Protocol (SNMPv2)", Internet Draft, Cisco |
Systems, September 1995. | Systems, September 1995. |
[3] McCloghrie, K., Editor, "Introduction to Version 2 of the |
Internet-standard Network Management Framework", Internet Draft, |
Cisco Systems, September 1995. |
[4] McCloghrie, K., Editor, "Transport Mappings for Version 2 of the |
Simple Network Management Protocol (SNMPv2)", Internet Draft, Cisco |
Systems, September 1995. |
6. Security Considerations 6. Security Considerations
Security issues are not discussed in this memo. Security issues are not discussed in this memo.
7. Editor's Address 7. Editor's Address
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
Table of Contents - Table of Contents -
1 Introduction .................................................... 2 1 Introduction .................................................... 2
1.1 A Note on Terminology ......................................... 3 1.1 A Note on Terminology ......................................... 3
2 Definitions ..................................................... 4 2 Definitions ..................................................... 4
3 Mapping of the TEXTUAL-CONVENTION macro ......................... 24 3 Mapping of the TEXTUAL-CONVENTION macro ......................... 26
3.1 Mapping of the DISPLAY-HINT clause ............................ 24 3.1 Mapping of the DISPLAY-HINT clause ............................ 26
3.2 Mapping of the STATUS clause .................................. 26 3.2 Mapping of the STATUS clause .................................. 28
3.3 Mapping of the DESCRIPTION clause ............................. 26 3.3 Mapping of the DESCRIPTION clause ............................. 28
3.4 Mapping of the REFERENCE clause ............................... 26 3.4 Mapping of the REFERENCE clause ............................... 28
3.5 Mapping of the SYNTAX clause .................................. 26 3.5 Mapping of the SYNTAX clause .................................. 28
4 Acknowledgements ................................................ 27 4 Acknowledgements ................................................ 29
5 References ...................................................... 28 5 References ...................................................... 30
6 Security Considerations ......................................... 29 6 Security Considerations ......................................... 31
7 Editor's Address ................................................ 29 7 Editor's Address ................................................ 31
 End of changes. 9 change blocks. 
22 lines changed or deleted 58 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/