The IP Over NBMA (ION) Archive[Date Prev][Date Next][Thread Prev][Thread Next] [Date Index][Thread Index][Author Index][Subject Index] SCSP MIB: representing long serverIDs
Cliff,
> > 3) The best solution to solve this in-consistency is to limit the
> > serverID length to 6 bits in SCSP protocol and I will propose that
> > to SCSP authors at coming IETF. As a matter of fact, an address
> > length of 64 bytes seems to be long enough.
>
> Perhaps, as an alternative to restricting the SCSP protocol for the sake
> of the MIB, would be to use a unique index to reference each serverID
> and to have the actual serverID as an extra value in the table.
Something like this extra table, and using the SCSPIDEntryidIndex in
scspDCSTable replacing scspDCSID, and in scspLSTable replacing scspLSID.
SCSPIDEntryEntry OBJECT-TYPE
SYNTAX SCSPIDEntryEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Server ID entry"
INDEX {
SCSPIDEntryidIndex
}
::= { SCSPIDEntryTable 1 }
SCSPIDEntryEntry ::=
SEQUENCE {
SCSPIDEntryidIndex INTEGER,
SCSPIDEntryid OCTET STRING
}
SCSPIDEntryidIndex OBJECT-TYPE
SYNTAX INTEGER
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Index into server's table of IDs."
::= { SCSPIDEntryEntry 1 }
SCSPIDEntryid OBJECT-TYPE
SYNTAX OCTET STRING (SIZE (0..255))
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Server ID"
::= { SCSPIDEntryEntry 2 }
Hoylen
P.S. If you are still going to restrict the SCSP specification to fit
the MIB by making the serverID length six bits (a questionable
approach), then the OCTET STRINGs should have a size of 0..63 and not
0..64.
__________________________________________________________ Dr Hoylen Sue
h.sue@citr.com.au +61 7 3259 2222 CiTR Pty Ltd, PO Box 1643, Milton,
4064, Australia. Fax: +61 7 3259 2259 http://www.citr.com.au
http://www.dstc.edu.au/RDU/staff/hoylen
|
|