Subject: AgentX transport MIB definitions

From: Lauren Heintz <[email-masked]>
Date: Mon, 03 Aug 1998 16:56:05 -0700

Hi,

-- Since RFC 2257 makes equal reference to both TCP and
Unix domain socket transports, shouldn't the AgentX MIB also do so?
For example, the MIB has an AgentXTCPAddress TC definition,
but no similar TC definition for Unix domain sockets.  Similarly,
an agentXTCPDomain object is defined, but not a corresponding one
for Unix domain sockets.

-- The AgentXTCPAddress TC should clarify the byte
contents and ordering for objects of this type.  For example:

	"Represents a TCP address consisting of a four byte
	 IP address value followed by a two byte port value
	 in network-byte order."

Lauren

--------------------------------------------------------------------------
Lauren Heintz                 BMC Software, Inc. (Formerly PEER Networks) 
Voice: +1 408 616-3169        Silicon Valley Division 
Fax:   +1 408 616-3339        965 Stewart Drive 
Email: [email-masked]  Sunnyvale, California 94086 USA 
--------------------------------------------------------------------------