A very nasty typo

Thread View: comp.protocols.iso.x400.gateway

1 messages

[T] Back to Threads [V] Tree View [G] Group Articles

1 total messages Started by Steve Hardcastle-Kille Tue, 06 Oct 1992 22:19

#101

Author: Steve Hardcastle-Kille
Date: Tue, 06 Oct 1992 22:19

36 lines
1841 bytes

Robert,

You are quite right that this is a problem.   However, the difficulty
is that there is a typo in RFC 1327.  The value of the UCL OID is
correct in other places (e.g., RFC 1274).

The OID component should be (19200300) and not (234219200300)

This clearly needs fixing.   I'm assuming that there will be a revised
1327 at some stage fairly soon in order to fold in the MIME-MHS
changes.   I'd propose waiting until then, rather than reissue for a
single typo.  However, I'm happy to take advice on this.

Another solution would be to shift to a less perverse OID.    (e.g.,
IANA or Enterpise assigned).


Steve

 >From:  "Robert S. Miles" <rsm@spyder.ssw.com>
 >To:    Steve Hardcastle-Kille <S.Kille@isode.com>
 >Subject: Re: RFC-1327 OIDs
 >Date:  Mon, 05 Oct 92 11:27:52 +0100

 >I wish I were wrong, but I believe this is a problem, particularly for
 >compatability with future implementations.
 >
 >	UCL OID element	value (per RFC 1327):			234219200300
 >	Common maximum unsigned integer ((2 ** 32) - 1):	  4294967295
 >	Truncated UCL OID element value (mod (2 ** 32)):	  2290966316
 >
 >Both ISODE and Retix use an array of integers to store OID elements
 >before encoding.  On 32 bit machines this means the OID element value
 >can be truncated.
 >
 >					-Bob

Thread Navigation

This is a paginated view of messages in the thread with full content displayed inline.

Messages are displayed in chronological order, with the original post highlighted in green.

Use pagination controls to navigate through all messages in large threads.

Back to All Threads