[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: 16 bit numbers

To: jparker@axiowave.com
Subject: Re: 16 bit numbers
From: Juergen Schoenwaelder <schoenw@ibr.cs.tu-bs.de>
Date: Thu, 10 Oct 2002 23:54:24 +0200
Cc: mibs@ops.ietf.org
In-reply-to: <EB5FFC72F183D411B38200062957342902A745F6@r2d2.axiowave.com>(message from Jeff Parker on Thu, 10 Oct 2002 17:45:11 -0400)
References: <EB5FFC72F183D411B38200062957342902A745F6@r2d2.axiowave.com>

>>>>> Jeff Parker writes:

Jeff> What is the prefered way to describe a 16 bit unsigned number?
Jeff> SNMPv2-SMI does not define Unsigned16.  Is there anything better
Jeff> than to use an octet string of length 2?

Unsigned16 ::= TEXTUAL-CONVENTION
    STATUS       current
    DESCRIPTION
        "An Unsigned32 further restricted to 16 Bits. Note that
         the ASN.1 BER encoding may still require 24 Bits for 
         some values."
    SYNTAX       Unsigned32 (0..65535)

The InetPortNumber (RFC 3291) is for example defined in this way.

/js

-- 
Juergen Schoenwaelder    <http://www.informatik.uni-osnabrueck.de/schoenw/>

References:
- 16 bit numbers
  - From: Jeff Parker <jparker@axiowave.com>

Prev by Date: Re: 16 bit numbers
Next by Date: RE: 16 bit numbers
Previous by thread: Re: 16 bit numbers
Next by thread: RE: 16 bit numbers
Index(es):
- Date
- Thread