Article View: comp.protocols.iso.dev-environ
Article #125Re: Encoding RFC 1006 addresses in X.500
From: Steve Kille
Date: Mon, 15 Jan 1990 09:19
Date: Mon, 15 Jan 1990 09:19
18 lines
1263 bytes
1263 bytes
You explain the problem with the AFI method yourself. It violates the standard - and this is very likely to come back and bite you later. I claim that my solution is about the best you can do within the framework. An important aspect is to choose addresses which will not confuse conformant OSI implementations, which do not know about all of the grody stuff you are doing here. (Rob's proposal falls here). A sound solution to some aspects of the problem is being pushed around the standards bodies by a "well known copmputer manufacturer". This modified the definition of presentation address to have an Object Identifier associated with each network address, which indicates which protocol is being used. Steve PS My paper and its companion are on the ISODE tape
Technical Details
Message-ID:
<1371.632395166@UK.AC.UCL.CS>Path:
arc1-ca.pugleaf.net!utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!tut.cis.ohio-state.edu!ucbvax!CS.UCL.AC.UK!S.KilleReferences:
<9001122056.AA24750@emu.ncsl.nist.gov>Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!tut.cis.ohio-state.edu!ucbvax!CS.UCL.AC.UK!S.Kille From: S.Kille@CS.UCL.AC.UK (Steve Kille) Newsgroups: comp.protocols.iso.dev-environ Subject: Re: Encoding RFC 1006 addresses in X.500 Message-ID: <1371.632395166@UK.AC.UCL.CS> Date: 15 Jan 90 09:19:26 GMT References: <9001122056.AA24750@emu.ncsl.nist.gov> Sender: daemon@ucbvax.BERKELEY.EDU Distribution: inet Organization: The Internet Lines: 18