From: SMTP%"RELAY-INFO-VAX@CRVAX.SRI.COM" 21-JUN-1993 18:48:53.38 To: EVERHART CC: Subj: SERIOUS problem with CISCO/Decnet phase IV/V Date: Mon, 21 JUN 93 19:04:54 GMT From: WILLIAMS_B@snd01.pcr.co.uk To: Info-VAX Subject: SERIOUS problem with CISCO/Decnet phase IV/V X-Reply-to: williams_b@snd01.pcr.co.uk X-App-Relay: uknet.ac.uk X-Usenet: ..mcsun!uknet!pfizer!williams_b X-Name: Brian Williams X-Service: Sandwich VAX 8600 X-Address: Pfizer Central Research, Sandwich, Kent CT13 9NJ UK X-Telephone: Sandwich (0304) 616223 X-UK: Brian Williams This message is addressed to all CISCO router owners who will be running multi-area Decnet within the next 2 years. We have a CISCO backbone and have been investigating a transition plan from Phase IV to Phase V (Decnet/OSI). I have just come back from Atlanta where I have been researching what needs to be done, and it seems that there are serious problems with migrating to Phase V if you have CISCO backbone routers. The problem is that the method that Dec uses to translate PIV to PV differs from that used by CISCO. The result is that if you want to migrate gradually, it is possible for Ph.IV adjacencies in different area to not be propagated across the network. The problem is recognised by both Dec and Cisco. The ideal solution would be for Cisco to change their method of translating Ph.IV-Ph.V to the way that Dec do it; however, I gather that this does not have a very high work priority. I am concerned because Phase IV will be frozen soon. It's status within about 18 months will become like that of Phase III. It will still work, but the expertise in Dec to support it will atrophy. It will not be available on Alphas. Decnet/OSI _will_ be _the_ Decnet within 2 years. I fear that if this problem is not dealt with in this timeframe, then migration to Phase V is going to be a very messy business, very likely involving the use of some form of static routing. It is in the interests of all Cisco users who envisage migration to Phase V to contact Cisco and raise the profile of this problem, and hopefully resources will then be found to deal with it. Disclaimer: these are my opinions, not necessarily that of my company. However, I would love for Cisco or Dec to tell me that I am wrong, in which case I will publish a full retraction and apology. Brian Williams