Article View: comp.protocols.iso.dev-environ
Article #141Re: Encoding RFC 1006 addresses in X.500
From: Marshall Rose
Date: Thu, 18 Jan 1990 17:14
Date: Thu, 18 Jan 1990 17:14
10 lines
932 bytes
932 bytes
Steve - we can consider adding the NSAP/ARP thing after we have a moving target to shoot at. Until I can see something concrete out of the standards body along with some working prototype, I don't even have a target to put my sights on. It's rather problematic to say "oh, we need to change X to conform to Y's model of the world", when Y's model of the world is yet to be defined in sufficient detail. OK? /mtr
Technical Details
Message-ID:
<29924.632682897@cheetah.nyser.net>Path:
arc1-ca.pugleaf.net!utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!uwm.edu!zaphod.mps.ohio-state.edu!tut.cis.ohio-state.edu!ucbvax!CHEETAH.NYSER.NET!mroseReferences:
<1199.632652618@UK.AC.UCL.CS>Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!uwm.edu!zaphod.mps.ohio-state.edu!tut.cis.ohio-state.edu!ucbvax!CHEETAH.NYSER.NET!mrose From: mrose@CHEETAH.NYSER.NET (Marshall Rose) Newsgroups: comp.protocols.iso.dev-environ Subject: Re: Encoding RFC 1006 addresses in X.500 Message-ID: <29924.632682897@cheetah.nyser.net> Date: 18 Jan 90 17:14:57 GMT References: <1199.632652618@UK.AC.UCL.CS> Sender: daemon@ucbvax.BERKELEY.EDU Distribution: inet Organization: The Internet Lines: 10