home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!news.claremont.edu!ucivax!gateway
- From: S.Kille@isode.com (Steve Hardcastle-Kille)
- Subject: RFC 1237 - proposed fix
- Message-ID: <5886.721149668@isode.com>
- Content-Type: text/plain; charset="us-ascii"
- MIME-Version: 1.0
- Newsgroups: comp.protocols.iso.x400.gateway
- Approved: usenet@q2.ics.uci.edu
- Lines: 35
- Date: 7 Nov 92 19:54:32 GMT
- Phone: +44-71-223-4062
-
- I propose the following fix to RFC 1327. This assigns an entirely
- new OID. The one widely deployed implementation does not follow
- the specification either as written or intended (it truncates the long
- number to four octets). The proposed change
-
- 1) Corrects the specification
- 2) Removes the problem of the long digit
- 3) Moves the whole assignment to a safe part of the OID space
- (0.9.2342 is questionable - this is being discussed in the
- OSI-DS group).
-
-
- Could this revised text be discussed at the X400-ops WG in DC?
-
-
- Steve
-
-
-
- Appendix D - Object Identifier Assignment
-
-
- An object identifier is needed for the extension IPMS element.
- The following value shall be used.
-
-
- x400-rfc822 OBJECT IDENTIFIER ::=
- {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1)
- isode-consortium (453) x400-rfc822(9)}
-
-
- id-rfc-822-field-list OBJECT IDENTIFIER ::= {x400-rfc822 field(1)}
-
-
-
-