Xref: utzoo comp.protocols.iso:735 comp.protocols.tcp-ip:9881
Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!swrinde!emory!hubcap!ncrcae!secola!clefor
From: clefor@secola.Columbia.NCR.COM (Cheryl LeFor)
Newsgroups: comp.protocols.iso,comp.protocols.tcp-ip
Subject: SNMP standards
Keywords: SNMP
Message-ID: <469@secola.Columbia.NCR.COM>
Date: 11 Jan 90 22:27:22 GMT
Reply-To: clefor@secola.UUCP ()
Organization: NCR Comten Columbia
Lines: 37

Hi!

I have some questions about some SNMP standards and would appreciate any
feedback from "those in the know."

I am writing some applications that will communicate with an SNMP agent in
order to retrieve mib variables.  In one case, I retreive the mib Interface
Table entries.  My question concerns the ifPhysAddress field of the ifTable.

According to the RFC which describes the mib (RFC 1066), ifPhysAddress is
defined as such:

	OBJECT: 	ifPhysAddress	{ ifEntry 6 }
	Syntax: 	OCTET STRING
	Definition:
		The interface's address at the protocol layer immediately "below"
		IP in the protocol stack.

My question is: 	What is the standard format for this octet string?
                	6 byte phys addr:	080014118562
            OR, 	character string:	"08:00:14:11:85:62"

This question also pertains to the Address Translation Table atPhysAddress
field (OCTET STRING).

With the particular SNMP agent I'm using, ifPhysAddress came back in the 
"08:00..." form, and atPhysAddress came back in the 6 byte form.

One last question...
(This is probably more for a Nysernet dude but here goes..)
WHY are the components of the mib path defined as unsigned longs?  Isn't that
a lot of space for a number which is usually a one digit number?

			iso.org.dod.internet.mgmt.mib
	i.e.:	1.3.6.1.2.1   would have 6 unsigned longs.

	Thanks for your time!!