cryptoanarchy.wiki

Arise, you have nothing to lose but your barbed wire fences!

1996-03-28 - Re: HP & Export of DCE

Header Data

From: “Perry E. Metzger” <perry@piermont.com>
To: janzen@idacom.hp.com
Message Hash: 5adb0421c3b8e7291899083149700d68d21107debe018c7dbc1e0bde56f0a25b
Message ID: <199603272233.RAA06214@jekyll.piermont.com>
Reply To: <9603272138.AA03891@sabel.idacom.hp.com>
UTC Datetime: 1996-03-28 23:57:02 UTC
Raw Date: Fri, 29 Mar 1996 07:57:02 +0800

Raw message

From: "Perry E. Metzger" <perry@piermont.com>
Date: Fri, 29 Mar 1996 07:57:02 +0800
To: janzen@idacom.hp.com
Subject: Re: HP & Export of DCE
In-Reply-To: <9603272138.AA03891@sabel.idacom.hp.com>
Message-ID: <199603272233.RAA06214@jekyll.piermont.com>
MIME-Version: 1.0
Content-Type: text/plain



Martin Janzen writes:
> The first "RPC" was produced by Sun's Open Network Computing group.

Not even remotely the case -- RPC predates Sun Microsystems by a lot.

> Another "RPC" comes from the Open Software Foundation, who unfortunately
> chose the same acronym for the remote procedure calling mechanism in their
> Distributed Computing Environment (DCE).

I'm not sure its so bad, given that there are at least a dozen RPCs
out there or more.

> In short, it would help to avoid massive confusion if people were more
> specific: refer to "DCE RPC", "ONC RPC" (or "Sun RPC", if you must :),
> or "Microsoft RPC", not just to "RPC".

Probably the case...

Perry

Thread