home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!zaphod.mps.ohio-state.edu!usc!news.service.uci.edu!ucivax!gateway
- From: Stef@nma.com (Einar Stefferud)
- Subject: Re: RFC 1237 - proposed fix
- Message-ID: <10662.721181356@nma.com>
- In-reply-to: Your message of Sat, 07 Nov 1992 15:21:08 +0000.
- <5886.721149668@isode.com>
- Newsgroups: comp.protocols.iso.x400.gateway
- Reply-To: Stef@nma.com
- Approved: usenet@q2.ics.uci.edu
- Lines: 33
- Date: 8 Nov 92 00:17:56 GMT
-
- I have recently had a message exchange with Lyman with regard to ISOC
- quickly getting an ICD from BSI for IAB/IETF use. If that has been
- accomplished, it might be much much better to use an OID branch under
- it, if we can organize things fast enough...\Stef
-
- +++++++++++++
-
- From message <5886.721149668@isode.com> :
- >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)}
-