Distinct ONC RPC for IPv6 networks
Have you started thinking about porting your RPC based applications to IPv6? If you have not done this yet, here is some information you many need to consider. The IPv4 addressing model only uses 32bits for the IP address space which restricts the global IP addresses available to about 4 billion. In the early 1990’s it became clear that we would soon start running out of available IP addresses and the IETF started exploring different solutions which culminated in 1995 with the agreement to pursue IPv6 as the new standard for global IP addresses. The advent of NAT has prolonged the life of IPv4 networks but soon with the rapid global expansion of the Internet, numbers will be running out. That’s why IPv6 is once again becoming the buzz word of the day. With more and more companies planning a migration from IPv4 to IPv6, one thing is certain: networks are going to have a combination of IPv4 and IPv6 interoperating for many years to come. This is why when porting RPC servers, it is a good idea to ensure that the RPC server library being used supports both IPv4 and IPv6 connections.
The new IPv6 standard has caused the Sun ONC RPC specifications to be modified in a few areas. For example, IPv6 no longer supports UDP broadcasts, therefore RPC broadcast is now achieved through a well know multicast address reserved for ONC RPC.
If you have an existing project that uses The Distinct ONC RPC version for IPv4 networks, you will find that this new toolkit will allow you to port the RPC portion of that application with very few changes to your basic code. Porting should be effectively simple. As always our technical support staff will be available to answer any porting questions that relate to the Distinct RPC library that you may have.
The Distinct ONC RPC/XDR Toolkit – 32 for IPv6 networks includes the following salient features:
- Full multithreading in both client and server
- Supports asynchronous RPC calls
- Supports Batched calls
- Has support for both IPv4 and IPv6 networks
- Supports Unix Authentication
- RPCBIND protocol (versions 2, 3 and 4)
- Increased performance using Winsock version 2
- Supports RPC applications to run without the Portmapper or RPCBIND
- Broadcast RPC through Multicast
- RPCINFO with support for RPCBIND
- Samples for Microsoft® Visual C++™, CodeGear® C Builder™ and CodeGear® Delphi™
In addition RPCGEN:
- Supports multiple arguments per call (extended XDR-standard)
- Supports multiple interface versions in one server
- Allows the optional use of a C preprocessor (for code with #ifdefs)
So whether you are an existing user of Distinct ONC RPC/XDR or have a new project that requires rpc support on an IPv6 network,
request your trial copy of