[Info-vax] What would you miss if DECnet got the chop? Was: "bad select 38" (OpenSSL on VMS)

[Dirk Munk]

Michael Moroney wrote:
> Dirk Munk <munk at home.nl> writes:
>
>> Michael Moroney wrote:
>>>
>>> Without looking into it, I would assume OSI over IP is just another user
>>> of IP and it "should work" with Multinet/the VSI IP.  But perhaps the
>>> DECnet V people conspired with the DEC TCPIP people to use an undocumented
>>> interface.  But we should already know the answer.  Does DECnet-Plus over
>>> IP work at all with the current Multinet implementation?
>
>> According to the DECnet-Plus SPD, only the HP IP stack is supported. It
>> does not explicitly say that no other IP stack works of course.
>
>> DECnet-Plus relies on the PWIP driver, it must be loaded.
>
>> DECnet-plus at present uses RFC1006 and RFC1859. For DECnet-Plus to use
>> IPv6, RFC2126 should also be implemented.
>
>> You should be able to see in the sources of DECnet-Plus and TCPIP
>> services how these two products interconnect, we can't do that.
>
> I will take a look in my copious spare time :-) at the DECnet/IP code
> to see what's going on and what would be needed.  I have no idea when....
>

It just occurred to me that you will have to look into these matters anyway.

TCP/IP services 10.5 will be based on Multinet, and Multinet has a PWIP 
driver.

DECnet-Plus is build on top of the PWIP driver, so you will have to 
check if the Multinet PWIP driver is DECnet-Plus compatible, or perhaps 
use the HPE PWIP driver?

Multinet also has a full blown IPv6 implementation, does that also apply 
to their PWIP driver?

Interesting issues to sort out for VSI.