TCP/IPX Connection Mib Specification
RFC 1792

Document Type RFC - Experimental (April 1995; No errata)
Last updated 2013-03-02
Stream Legacy
Formats plain text pdf html bibtex
Stream Legacy state (None)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state RFC 1792 (Experimental)
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                            T. Sung
Request for Comments: 1792                                  Novell, Inc.
Category: Experimental                                        April 1995

                  TCP/IPX Connection Mib Specification

Status of this Memo

   This document defines an Experimental Protocol for the Internet
   community.  This does not specify an Internet standard of any kind.
   Discussion and suggestions for improvement are requested.
   Distribution of this memo is unlimited.

IESG Note:

   Internet Engineering Steering Group comment from the Area Director
   for Transport Services: Please note well that this memo is an
   individual product of the author.  Implementation experience,
   particularly on the effectiveness of the protocols in dual-stack
   environments, is needed.

1.  Introduction

   Traditionally, TCP and UDP runs over IP.  STD 17, RFC 1213 defines
   TCP connection MIB object and UDP listener object assuming just that.
   For TCP and UDP running over IPX, tcpConnTable and udpTable objects
   from RFC 1213 cannot be used since they define the address to be of
   type IpAddress.  As such, we need to define new objects that can
   properly describe TCP and UDP connections over IPX.

   New MIB objects, tcpIpxConnTable, udpIpxTable, tcpUnspecConnTable and
   udpUnspecTable are presented in this paper, to be used in place of
   tcpConnTable and udpListenerTable when TCP and UDP are running over
   IPX.

2.  Objects

           TCPIPX-MIB DEFINITIONS ::= BEGIN

           IMPORTS
                   OBJECT-TYPE
                           FROM RFC-1212;

        -- IPX address type.
        -- First 4 octests are the network numbers and the last 6
        -- octests are the node numbers.  In ascii, it is represented

Sung                                                            [Page 1]
RFC 1792                      TCP/IPX MIB                     April 1995

        -- as hex digits, as in:  nnnnnnnn:mmmmmmmmmmmm

        IpxAddress ::= OCTET STRING (size (10))

           -- TCP/IPX MIB object idenfifiers

        novell        OBJECT IDENTIFIER ::= { enterprises 23 }
        mibDoc        OBJECT IDENTIFIER ::= { novell 2 }
        tcpx          OBJECT IDENTIFIER ::= { mibDoc 29 }
        tcpxTcp       OBJECT IDENTIFIER ::= { tcpx 1 }
        tcpxUdp       OBJECT IDENTIFIER ::= { tcpx 2 }

          -- the TCP/IPX Connection table

           -- The TCP/IPX connection table contains information
           -- about this entity's existing TCP connections over
           -- IPX.

           tcpIpxConnTable OBJECT-TYPE
               SYNTAX  SEQUENCE OF TcpIpxConnEntry
               ACCESS  not-accessible
               STATUS  mandatory
               DESCRIPTION
                       "A table containing information specific on
                       TCP connection over IPX network layer."

               ::= { tcpxTcp 1 }

           tcpIpxConnEntry OBJECT-TYPE
               SYNTAX  TcpIpxConnEntry
               ACCESS  not-accessible
               STATUS  mandatory
               DESCRIPTION
                       "Information about a particular current TCP
                       connection over IPX  An object of this type is
                       transient, in that it ceases to exist when (or
                       soon after) the connection makes the transition
                       to the CLOSED state."
               INDEX   { tcpIpxConnLocalAddress,
                         tcpIpxConnLocalPort,
                         tcpIpxConnRemAddress,
                         tcpIpxConnRemPort }
              ::= { tcpIpxConnTable 1 }

           TcpIpxConnEntry ::=
               SEQUENCE {

Sung                                                            [Page 2]
RFC 1792                      TCP/IPX MIB                     April 1995

                   tcpIpxConnState
                       INTEGER,
                   tcpIpxConnLocalAddress
                       IpxAddress
                   tcpIpxConnLocalPort
                       INTEGER (0..65535),
                   tcpIpxConnRemAddress
                       IpxAddress,
                   tcpIpxConnRemPort
                       INTEGER (0..65535)
               }

           tcpIpxConnState OBJECT-TYPE
               SYNTAX  INTEGER {
                           closed(1),
                           listen(2),
                           synSent(3),
                           synReceived(4),
                           established(5),
                           finWait1(6),
                           finWait2(7),
                           closeWait(8),
                           lastAck(9),
                           closing(10),
                           timeWait(11),
                           deleteTCB(12)
                       }
               ACCESS  read-write
               STATUS  mandatory
               DESCRIPTION
                       "The state of this TCP connection.
Show full document text