jh@tut.fi (Juha Hein{nen) (02/24/90)
Hello Folks, I have been testing an X.400 implementation on a TCP/IP only host. In order to be able to communicate with other X.400 systems on X.25 only hosts, I have used the transport bridge included in Isode 6.0. When the transport bridge makes a connection to an X.25 host, it gives in my case the following source transport address: "TELEX+00728722+RFC-1006+03+131.177.104.142"/X121+24432315101521 The problem with this is that the transport selector "TELEX ... 142" is too long for many X.400 systems (eg. Route 400 and Dialcom). Also US Gosip 2.0 restricts the maximum length of the tsel to 32 octects which means that vendors are not too willing to start supporting tsels long enough for the tsbridge. So my conclusion is that the current tsbridge implementation is not very useful in promoting OSI migration. What could then be done to improve the situation? Since tsbridge maintains a state of its current connections, could the source tsel be any short string that is unique among connections or is there some important reason to use Kille's string encoding of the presentation address? Any other ideas? -- -- Juha Heinanen, Tampere Univ. of Technology, Finland jh@tut.fi (Internet), tut!jh (UUCP), jh@tut (Bitnet)
j.onions@computer-science.nottingham.ac.UK (Julian Onions) (02/26/90)
I have made a change to the tsbridge to deal with this problem. It is being tested at present in the UK - if anyone else needs such a change I can provide it. Julian.