Browse Prior Art Database

TCP/IPX Connection Mib Specification (RFC1792)

IP.com Disclosure Number: IPCOM000004046D
Original Publication Date: 1995-Apr-01
Included in the Prior Art Database: 2000-Sep-13
Document File: 7 page(s) / 15K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

T. Sung: AUTHOR

Abstract

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.

This text was extracted from a ASCII document.
This is the abbreviated version, containing approximately 18% of the total text.

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

-- 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 conta...