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

Re: Photuris // Variable-Precision numbers

To: alten@na.sjf.novell.com (Alex Alten)
Subject: Re: Photuris // Variable-Precision numbers
From: Bernhard Schneck <Bernhard_Schneck@GeNUA.DE>
Date: Wed, 18 Oct 1995 09:15:15 +0100
Cc: bsimpson@morningstar.com (William Allen Simpson), ipsec@ans.net
In-Reply-To: Your message of Tue, 17 Oct 1995 18:18:43 -0700. <199510180124.AA22890@interlock.ans.net>

In message <199510180124.AA22890@interlock.ans.net>you write:
 > 
 > May I suggest that you use ASN.1 encoding for the multiprecision integers?
 > This is a standard that is in use (by SNMP) and has both commercial and 
 > public domain software libraries available.  The only extra overhead is 
 > one leading byte for the data type field, otherwise it is the same thing 
 > as you and Ron are discussing, with a length field followed by the integer 
 > (data).  

With the following differences:

- ASN.1 counts bytes in the size field, the Photuris draft counts bits
- ASN.1 has signed integers, the Photuris draft uses unsigned
- ASN.1 encoding rules can be a pain in <wherever> to get right for
  some values (eg. 128 is encoded as 02 02 00 80, ie. it requires at
  least two bytes for the value)

\Bernhard.

References:

Re: Photuris // Variable-Precision numbers

From: alten@na.SJF.Novell.COM (Alex Alten)

Prev by Date: Re: Photuris // Variable-Precision numbers
Next by Date: Photuris // entities
Prev by thread: Re: Photuris // Variable-Precision numbers
Next by thread: Photuris // Variable-Precision numbers
Index(es):
- Main
- Thread