Browse Prior Art Database

Identification MIB (RFC1414)

IP.com Disclosure Number: IPCOM000002240D
Original Publication Date: 1993-Feb-01
Included in the Prior Art Database: 2019-Feb-10
Document File: 7 page(s) / 9K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

M. St. Johns: AUTHOR [+1]

Related Documents

10.17487/RFC1414: DOI

Abstract

This memo defines a MIB for use with identifying the users associated with TCP connections. It provides functionality approximately equivalent to that provided by the protocol defined in RFC 1413 [1]. [STANDARDS-TRACK]

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 25% of the total text.

Network Working Group M. St. Johns Request for Comments: 1414 US Department of Defense M. Rose Dover Beach Consulting, Inc. February 1993

Identification MIB

Status of this Memo

This RFC specifies 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.

Abstract

This memo defines a MIB for use with identifying the users associated with TCP connections. It provides functionality approximately equivalent to that provided by the protocol defined in RFC 1413 [1]. This document is a product of the TCP Client Identity Protocol Working Group of the Internet Engineering Task Force (IETF).

Table of Contents

1. The Network Management Framework ....................... 2 2. Identification MIB ..................................... 3 3. Definitions ............................................ 3 3.1 Conformance Groups .................................... 3 3.2 Textual Conventions ................................... 3 3.3 The Ident information Group ........................... 3 4. Security Considerations ................................ 6 5. References ............................................. 6 6. Authors’ Addresses ..................................... 7

St. Johns & Rose [Page 1]

RFC 1414 Identification MIB February 1993

1. The Network Management Framework

The Internet-standard Network Management Framework consists of three components. They are:

STD 16/RFC 1155 [2] which defines the SMI, the mechanisms used for describing and naming objects for the purpose of management. STD 16/RFC 1212 [3] defines a more concise description mechanism, which is wholly consistent with the SMI.

STD 17/RFC 1213 [4] which defines MIB-II, the core set of managed objects for the Internet suite of protocols.

STD 15/RFC 1157 [5] which defines the SNMP, the protocol used for network access to managed objects.

The Framework permits new objects to be defined for the purpose of experimentation and evaluation.

Managed objects are accessed via a virtual information store, termed the Management Information Base or MIB. Within a given MIB module, objects are defined using RFC 1212’s OBJECT-TYPE macro. At a minimum, each object has a name, a syntax, an access-level, and an implementation-status.

The name is an object identifier, an administratively assigned name, which specifies an object type. The object type together with an object instance serves to uniquely identify a specific instantiation of the object. For human convenience, we often use a textual string, termed the object descriptor, to also refer to the object type.

The syntax of an object type defines the abstract data structure corresponding to that object type. The ASN.1 [6] language is used for this purpose. However, RFC 1155 purposely restricts the ASN.1 constructs which may be used. These...

Processing...
Loading...