Re: Encoding RFC 1006 addresses in X.500

Article View: comp.protocols.iso.dev-environ

Article #130

Back to comp.protocols.iso.dev-environ Previous Next

#130

From: hagens
Date: Wed, 17 Jan 1990 17:40

13 lines
1043 bytes

> 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).   

If your system can make a routing decision based upon a variable length
address prefix, then it is no harder to recognize 54.... as special-kludge-o-rama
than to recognize 470005000002.... as special-kludge-o-rama.

If your system can't make a routing decision based upon a variable length
address prefix, then wait for Berkeley's 4.4 distribution and copy their code.

rob

Technical Details

Message-ID: <9001171740.AA18406@janeb.cs.wisc.edu>

Path: arc1-ca.pugleaf.net!utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!tut.cis.ohio-state.edu!ucbvax!CS.WISC.EDU!hagens

References: <1371.632395166@UK.AC.UCL.CS>

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.WISC.EDU!hagens
From: hagens@CS.WISC.EDU
Newsgroups: comp.protocols.iso.dev-environ
Subject: Re: Encoding RFC 1006 addresses in X.500
Message-ID: <9001171740.AA18406@janeb.cs.wisc.edu>
Date: 17 Jan 90 17:40:52 GMT
References: <1371.632395166@UK.AC.UCL.CS>
Sender: daemon@ucbvax.BERKELEY.EDU
Distribution: inet
Organization: The Internet
Lines: 13

Reply to Parent Message