Path: utzoo!utgpu!watserv1!watmath!att!rutgers!mit-eddie!bu.edu!xylogics!samsung!uakari.primate.wisc.edu!sdd.hp.com!ucsd!helios.ee.lbl.gov!pasteur!ucbvax!DDNUVAX.AF.MIL!beach From: beach@DDNUVAX.AF.MIL (darrel beach) Newsgroups: comp.protocols.tcp-ip Subject: GOSIP and X.25 Message-ID: Date: 16 Jul 90 13:47:07 GMT Sender: daemon@ucbvax.BERKELEY.EDU Organization: The Internet Lines: 27 X-Local-Date: 16 Jul 90 06:47:07 PDT Thanks to everyone who responded to my last inquiry on GOSIP. I'm still not very knowledgeable about the OSI suite. I have a couple more simple (I hope) questions. The first one has to do with X.25. Is it possible or practical to run both TCP/IP and the GOSIP suite over a single X.25 interface into a network?? and ditto for ethernets?? I suppose ether is easy relative to X.25. I'm most familiar with the milnet (standard) brand of TCP/IP over X.25, where CC is the first byte of call user data in call request packets, and where datagrams are sent as complete packet sequences, etc. It would seem that in order to support BOTH suites over a single X.25 interface, then it would be necessary ti parse which protocol is being used, IP or ISO8473, after the PDU is received. That doesn't seem too practical. Would a host now have to maintain a virtual circuit table that includes info on what kinds of PDUs can be sent on that vc (IP or 8473). This assumes the X.121 addresses for a dual protocol hosts is the same regardless of which suite is being called. In the case of Milnet, does anybody know how to address OSI suite hosts? Right now it looks like I just build a table of X.121 addresses. Will there ever be an algorithmic derivation to get the X.121 addresses?? Seems to be a knotty little topic, but maybe its easier than it seems. Darrel Beach