Identification MIB
RFC 1414

• Status
• IESG evaluation record
• IESG writeups
• Email expansions
• History

• Versions
• 03

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 restrictions are explicitly made
   for simplicity.

   The access-level of an object type defines whether it makes "protocol
   sense" to read and/or write the value of an instance of the object
   type.  (This access-level is independent of any administrative
   authorization policy.)

   The implementation-status of an object type indicates whether the
   object is mandatory, optional, obsolete, or deprecated.

St. Johns & Rose                                                [Page 2]
RFC 1414                   Identification MIB              February 1993

2.  Identification MIB

   The Identification MIB defines a uniform set of objects useful for
   identifying users associated with TCP connections.  End-systems which
   support TCP may, at their option, implement this MIB.  However,
   administrators should read Section 4 ("Security Considerations")
   before enabling these MIB objects.

3.  Definitions

          RFC1414-MIB DEFINITIONS ::= BEGIN

          IMPORTS
              OBJECT-TYPE
                  FROM RFC-1212
              tcpConnLocalAddress, tcpConnLocalPort,
              tcpConnRemAddress, tcpConnRemPort
                      FROM RFC1213-MIB;

          ident   OBJECT IDENTIFIER ::= { mib-2 24 }

          -- conformance groups

          identInfo       OBJECT IDENTIFIER ::= { ident 1 }

          -- textual conventions

          -- none

          -- the ident information system group