- From: Brent <brent@eng.Sun.COM>
- Date: Thu, 04 Feb 1999 12:39:14 -0800
- To: discuss@apps.ietf.org
Chris Newman wrote: > XDR isn't a bad binary data encoding for the wire (certainly better than > ASN.1 BER), but it solves problems (like floating point numbers) which > almost never appear in real protocols. The RPC spec had to go into a lot > of detail about the model since RPCs are more constraining than > traditional IETF protocols. So there's a lot of stuff there that a "core > protocol" wouldn't need. I think ONC RPC is pretty "thin" as RPC protocols go. Is it really loaded with unnecessary baggage that disqualifies it as a candidate for core protocol ? It's been around for about 15 years, it's on IETF standards track, and hundreds of protocols have used it as a "core" protocol. What are the constraints that prevent ONCRPC from being the "core" protocol ? Can those constraints be removed by extending it to version 3 ? This discussion seems highly relevant to the ONCRPC mailing list: oncrpc-wg-request@sunroof.eng.sun.com. Brent
Received on Thursday, 4 February 1999 15:41:43 UTC