[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

conversion parsing tools



All:

For the last few weeks we have come up empty searching for a
tool that will help translate an ascii flat file into ietf 
compliant
TCP mib-speak for a new draft for Salt Lake City.  This effort is
an outgrowth of the www.web100.org project.

Below is an initial snippet of what we have today and need to 
have
translated to the properly formated mib-speak. I am aware of 
tools
that will help validate whether the submission is syntactically 
correct
and valid.  Its getting from what we have today to that stage 
that we
need help with.

Any and all suggestions and pointers would be welcome.

thanks for your consideration.


Peter

National Center for Atmospheric Research
Boulder, CO
303.497.1820

---------------

Documentation of variables for the Web100 TCP Kernel 
Instrumentation
Set (KIS) project.

        Matt Mathis
        Jeffrey Semke
        Raghu Reddy
        Pittsburgh Supercomputing Center
        Web 100 Project

(c) All rights reserved.  This document contains incomplete and
    unpublished research results.  This interim version is 
provided
    only to enable developers to build an initial tool set. 
Future
    version of this document are likely to differ from this 
version in
    incompatible ways -- newer versions will completely 
supersede this
    version.

Terminology:
        Local Host:     the host from which the KIS was read
        Remote Host:    a host that has a TCP connection between 
the local
                        host and itself
SNMP Data Types taken from RFC 1902 "Structure of Management 
Information
        for Version 2 of the Simple Network Management Protocol 
(SNMPv2)"

----------------------------------------------------------------
--------------
CATEGORY:       STATE
CatDescr:       Flags indicating if various protocol features or 
algorithms
                are enabled.  All of the options listed here are 
fully
                described in various standards documents.
----------------------------------------------------------------
--------------
VariableName:   State
ShortDescr:     TCP State
Category:       STATE
SNMPType:       INTEGER
Description:    An integer value representing the connection 
state from the
                TCP State Transition Diagram
R/W:            read-only
Reference:      RFC2012 (TCP-MIB v2)
                Transmission Control Protocol using SMIv2
Comment:        This is patterned after the Connection Table in 
RFC2012
PossibleValues:
                WC_STATE_CLOSED                   1
                WC_STATE_LISTEN                   2
                WC_STATE_SYNSENT                  3
                WC_STATE_SYNRECEIVED              4
                WC_STATE_ESTABLISHED              5
                WC_STATE_FINWAIT1                 6
                WC_STATE_FINWAIT2                 7
                WC_STATE_CLOSEWAIT                8
                WC_STATE_LASTACK                  9
                WC_STATE_CLOSING                  10
                WC_STATE_TIMEWAIT                 11
                WC_STATE_DELETETCB                12
Portability:    universal
ImplStatus:     5/23/00 implemented
----------------------------------------------------------------
--------------
VariableName:   SACKEnabled
ShortDescr:     SACK Enabled
Category:       STATE
SNMPType:       INTEGER (Boolean)
Description:    non-zero if SACK has been negotiated ON by both 
ends of the
                connection.  Zero otherwise.
R/W:            read-only
Reference:      RFC2018 TCP Selective Acknowledgement Options
Comment:
Portability:    nearly universal - SACK is a standard - This 
variable can
                be hard-wired to zero on systems not supporting 
SACK.
ImplStatus:     5/23/00 implemented & checked (jheffner 
7/28/2000)
----------------------------------------------------------------
--------------
VariableName:   TimestampsEnabled
ShortDescr:     Timestamps Enabled
Category:       STATE
SNMPType:       INTEGER (Boolean)
Description:    non-zero if Timestamps have been negotiated ON 
by both ends
                of the connection in the SYN.  Zero otherwise.
R/W:            read-only
Reference:      RFC1323 TCP Extensions for High Performance
Comment:
Portability:    nearly universal
ImplStatus:     5/23/00 implemented & checked (jheffner 
7/28/2000)
----------------------------------------------------------------
--------------
VariableName:   NagleEnabled
ShortDescr:     Nagle Algorithm Enabled
Category:       STATE
SNMPType:       INTEGER (Boolean)
Description:    non-zero if the Nagle algorithm is being used by 
the Local
                Host on this connection.  Zero otherwise.
R/W:            read-only
Reference:
Comment:
Portability:    nearly universal
ImplStatus:     5/23/00 implemented - need to validate descr
----------------------------------------------------------------
--------------
VariableName:   CurrTime
ShortDescr:     Current Time
Category:       STATE
SNMPType:       Counter32
Description:    Current Time in usec
R/W:            read-only
Reference:
Comment:
Portability:    uses do_gettimeofday routine that is arch 
dependent
----------------------------------------------------------------
--------------
VariableName:   syn_seq
ShortDescr:     Sequence Number in SYN (sent or received?)
Category:       STATE
SNMPType:       Counter32
Description:    The initial sequence number of SYN (sent or 
received?)
R/W:            read-only
Reference:
Comment:        need to think about this some more; in test mode
Portability:
----------------------------------------------------------------
--------------
CATEGORY:       CONNECTION ID
CatDescr:       The 4-tuple that uniquely identifies every 
connection.  We
                should include protocol type to support possible 
migration to
                additional TCP like protocols (e.g TCPv6).
----------------------------------------------------------------
etc, etc.