As per Relevance of the word indicates, we have this rfc below:
Network Working Group M. St.
Request for Comments: 1414 US Department of
M.
Dover Beach Consulting, Inc
February 1993
Identification
Status of this
This RFC specifies an IAB standards track protocol for the
community, and requests discussion and suggestions for improvements
Please refer to the current edition of the "IAB Official
Standards" for the standardization state and status of this protocol
Distribution of this memo is unlimited
This memo defines a MIB for use with identifying the users
with TCP connections. It provides functionality
equivalent to that provided by the protocol defined in RFC 1413 [1].
This document is a product of the TCP Client Identity
Working Group of the Internet Engineering Task Force (IETF).
Table of
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
The Internet-standard Network Management Framework consists of
components. They are
STD 16/RFC 1155 [2] which defines the SMI, the mechanisms used
describing and naming objects for the purpose of management.
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
objects for the Internet suite of protocols
STD 15/RFC 1157 [5] which defines the SNMP, the protocol used
network access to managed objects
The Framework permits new objects to be defined for the purpose
experimentation and evaluation
Managed objects are accessed via a virtual information store,
the Management Information Base or MIB. Within a given MIB module
objects are defined using RFC 1212's OBJECT-TYPE macro. At
minimum, each object has a name, a syntax, an access-level, and
implementation-status
The name is an object identifier, an administratively assigned name
which specifies an object type. The object type together with
object instance serves to uniquely identify a specific
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
corresponding to that object type. The ASN.1 [6] language is
for this purpose. However, RFC 1155 purposely restricts the ASN.1
constructs which may be used. These restrictions are explicitly
for simplicity
The access-level of an object type defines whether it makes "
sense" to read and/or write the value of an instance of the
type. (This access-level is independent of any
authorization policy.)
The implementation-status of an object type indicates whether
object is mandatory, optional, obsolete, or deprecated
St. Johns & Rose [Page 2]
RFC 1414 Identification MIB February 1993
2. Identification
The Identification MIB defines a uniform set of objects useful
identifying users associated with TCP connections. End-systems
support TCP may, at their option, implement this MIB. However
administrators should read Section 4 ("Security Considerations")
before enabling these MIB objects
3.
RFC1414-MIB DEFINITIONS ::=
OBJECT-
FROM RFC-1212
tcpConnLocalAddress, tcpConnLocalPort
tcpConnRemAddress,
FROM RFC1213-MIB
ident OBJECT IDENTIFIER ::= { mib-2 24 }
-- conformance
identInfo OBJECT IDENTIFIER ::= { ident 1 }
-- textual
--
-- the ident information system
--
-- implementation of this group is
identTable OBJECT-
SYNTAX SEQUENCE OF
ACCESS not-
STATUS
"A table containing user information for
connections
Note that this table contains entries for all
connections on a managed system.
corresponding instance of tcpConnState (defined
MIB-II) indicates the state of a
St. Johns & Rose [Page 3]
RFC 1414 Identification MIB February 1993
connection."
::= { identInfo 1 }
identEntry OBJECT-
SYNTAX
ACCESS not-
STATUS
"User information about a particular
connection."
INDEX { tcpConnLocalAddress, tcpConnLocalPort
tcpConnRemAddress, tcpConnRemPort }
::= { identTable 1 }
IdentEntry ::=
SEQUENCE {
identStatus INTEGER
identOpSys OCTET STRING
identCharset OCTET STRING
identUserid OCTET STRING
identMisc OCTET
}
identStatus OBJECT-
SYNTAX INTEGER {
noError(1),
unknownError(2)
}
ACCESS read-
STATUS
"Indicates whether user information for
associated TCP connection can be determined.
value of `noError(1)' indicates that
information is available. A value
`unknownError(2)' indicates that user
is not available."
::= { identEntry 1 }
identOpSys OBJECT-
SYNTAX OCTET STRING (SIZE(0..40))
ACCESS read-
STATUS
"Indicates the type of operating system in use
In addition to identifying an operating system
each assignment made for this purpose
(implicitly) identifies the textual format
St. Johns & Rose [Page 4]
RFC 1414 Identification MIB February 1993
maximum size of the corresponding identUserid
identMisc objects
The legal values for the `indentOpSys'
are those listed in the SYSTEM NAMES section
the most recent edition of the ASSIGNED
RFC [8]."
::= { identEntry 2 }
identCharset OBJECT-
SYNTAX OCTET STRING (SIZE(0..40))
ACCESS read-
STATUS
"Indicates the repertoire of the
identUserid and identMisc objects
The legal values for the `identCharset'
are those listed in the CHARACTER SET section
the most recent edition of the ASSIGNED
RFC [8]."
::= { identEntry 3 }
identUserid OBJECT-
SYNTAX OCTET STRING (SIZE (0..255))
ACCESS read-
STATUS
"Indicates the user's identity. Interpretation
this object requires examination of
corresponding value of the identOpSys
identCharset objects."
::= { identEntry 4 }
identMisc OBJECT-
SYNTAX OCTET STRING (SIZE (0..255))
ACCESS read-
STATUS
"Indicates miscellaneous information about
user. Interpretation of this object
examination of the corresponding value of
identOpSys and identCharset objects."
::= { identEntry 5 }
St. Johns & Rose [Page 5]
RFC 1414 Identification MIB February 1993
4. Security
The information available through this MIB is at most as
as the host providing it OR the organization operating the host.
example, a PC in an open lab has few if any controls on it to
a user from having an SNMP query return any identifier the
wants. Likewise, if the host has been compromised the
returned may be completely erroneous and misleading
This portion of the MIB space should only be used to gain hints as
who "owns" a particular TCP connection -- information returned
NOT be considered authoritative for at least the reasons
above. At best, this MIB provides some additional
information with respect to TCP connections. At worse it can
misleading, incorrect or maliciously incorrect information
The use of the information contained in this MIB for other
auditing or normal network management functions is
discouraged. Specifically, using information from this MIB space
make access control decisions - either as the primary method (i.e.,
no other checks) or as an adjunct to other methods may result in
weakening of normal system security
This MIB provides access to information about users, entities
objects or processes which some systems might normally
private. The information accessible through this MIB is a
analog of the CallerID services provided by some phone companies
many of the same privacy consideration and arguments that apply
CallerID service apply to this MIB space. If you wouldn't run
"finger" server [7] due to privacy considerations, you might not
to provide access to this MIB space on a general basis. Access
this portion of the MIB tree may be controlled under the
methods available through SNMP agent implementations
7.
[1] St. Johns, M., "Identification Protocol", RFC 1413, US
of Defense, February 1993.
[2] Rose M., and K. McCloghrie, "Structure and Identification
Management Information for TCP/IP-based internets", STD 16,
1155, Performance Systems International, Hughes LAN Systems,
1990.
[3] Rose, M., and K. McCloghrie, Editors, "Concise MIB Definitions",
STD 16, RFC 1212, Performance Systems International, Hughes
Systems, March 1991.
St. Johns & Rose [Page 6]
RFC 1414 Identification MIB February 1993
[4] McCloghrie K., and M. Rose, Editors, "Management Information
for Network Management of TCP/IP-based internets", STD 17,
1213, Performance Systems International, March 1991.
[5] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "
Network Management Protocol", STD 15, RFC 1157, SNMP Research
Performance Systems International, Performance
International, MIT Laboratory for Computer Science, May 1990.
[6] Information processing systems - Open Systems Interconnection -
Specification of Abstract Syntax Notation One (ASN.1),
International Organization for Standardization,
Standard 8824, December 1987.
[7] Zimmerman, D., "The Finger User Information Protocol", RFC 1288,
Center for Discrete Mathematics and Theoretical Computer Science
December 1991.
[8] Reynolds, J., and J. Postel, "Assigned Numbers", STD 2, RFC 1340,
USC/Information Sciences Institute, July 1992.
8. Authors'
Michael C. St.
U.S. Department of
DARPA/
3701 N. Fairfax
Arlington, VA 22203
Phone: (703) 696-2271
EMail: stjohns@DARPA.
Marshall T.
Dover Beach Consulting, Inc
420 Whisman
Mountain View, CA 94043-2186
Phone: (415) 968-1052
EMail: mrose@dbc.mtview.ca.
St. Johns & Rose [Page 7]
if you see any problems within the linking, don't worry be happy,
this is version 0.1 of the Relevance System and you gotta expect some crappy subroutines sometimes,
just be content we did not write this in Java, which would have made this "bigger and better" HAHAHHA.
RFC documents can be found at I.E.T.F.
Relevance System Copyright © 2002 Spectrum WorldResearch
other technical nosh by ServerMasters Corporation
collaboration of BobX
