A new Request for Comments is now available in online RFC libraries. RFC 1443: Title: Textual Conventions for version 2 of the Simple Network Management Protocol (SNMPv2) Author: J. Case, K. McCloghrie, M. Rose, & S. Waldbusser Mailbox: case@snmp.com, kzm@hls.com, mrose@dbc.mtview.ca.us, waldbusser@cmu.edu Pages: 31 Characters: 60,947 Updates/Obsoletes: none Management information is viewed as a collection of managed objects, residing in a virtual information store, termed the Management Information Base (MIB). Collections of related objects are defined in MIB modules. When designing a MIB module, it is often useful to define new types similar to those defined in the SMI. In comparison to a type defined in the SMI, each of these new types has a different name, a similar syntax, but a more precise semantics. These types are termed textual conventions. It is the purpose of this document to define the initial set of textual conventions available to all MIB modules. This is a product of the SNMP Version 2 Working Group and the SNMP Security Working Group of the IETF. This is now a Proposed Standard Protocol. This RFC specifes an IAB standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "IAB Official Protocol Standards" for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST@CNRI.RESTON.VA.US. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-REQUEST@NIC.DDN.MIL. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to "rfc-info@ISI.EDU" with the message body "help: ways_to_get_rfcs". For example: To: rfc-info@ISI.EDU Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to NIC@NIC.DDN.MIL. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. Submissions for Requests for Comments should be sent to RFC-EDITOR@ISI.EDU. Please consult RFC 1111, "Instructions to RFC Authors", for further information. Joyce K. Reynolds USC/Information Sciences Institute