![]() |
|
|
Welcome to the { mindfrost82.com } forums. You are currently viewing our boards as a guest which gives you limited access to view most discussions and access our other features. By joining our free community you will have access to post topics, communicate privately with other members (PM), respond to polls, upload content and access many other special features. Registration is fast, simple and absolutely free so please, join our community today! If you have any problems with the registration process or your account login, please contact contact us. |
|
|||||||
![]() |
|
|
LinkBack | Thread Tools | Search this Thread | Display Modes |
|
|||
|
Re: TCP without IP
On Thu, 14 Aug 2008, in the Usenet newsgroup comp.os.linux.networking, in
article <g81p7b$co4$1@registered.motzarella.org>, Huibert Bol wrote: >aarklon@gmail.com wrote: >> Theoretically, you could have TCP without IP, some other n/w mechanism >> besides IP could deliver the data to an address, and TCP could still >> verify and sequence that data >> >> can any one give examples for this ? > >There is/was TCP over IPX (see rfc1791). Don't know whether it was >actually implemented. 1791 TCP And UDP Over IPX Networks With Fixed Path MTU. T. Sung. April 1995. (Format: TXT=22347 bytes) (Status: EXPERIMENTAL) 1792 TCP/IPX Connection Mib Specification. T. Sung. April 1995. (Format: TXT=16389 bytes) (Status: EXPERIMENTAL) Notice the 'Status:' tag, and then look at RFC2026 section 4.2.1 4.2.1 Experimental The "Experimental" designation typically denotes a specification that is part of some research or development effort. Such a specification is published for the general information of the Internet technical community and as an archival record of the work, subject only to editorial considerations and to verification that there has been adequate coordination with the standards process (see below). An Experimental specification may be the output of an organized Internet research effort (e.g., a Research Group of the IRTF), an IETF Working Group, or it may be an individual contribution. Tae Sung was working for Novell in San Jose, CA (.us) and this seems to have been a dead end - recall that Novell NetWare was an major networking O/S, but it was pretty well locked to IPX. I know you could get it to acknowledge the existence of IP and if you loaded the right NLMs on the server, you could get it to _route_ IP (and Appletalk Phase I), but I think it was some time later (after NetWare 4.1) before they bit the bullet and actually started _running_ IP (and even when they did, the basic directory services remained IPX). Old guy |
|
|||
|
Re: TCP without IP
Do you mean un numbered ip?
0.0.0.0? <aarklon@gmail.com> wrote in message news:7d3e7523-a58b-4c13-8e1a-7315b7521794@v1g2000pra.googlegroups.com... > Hi, > > I have read in some books as follows :- > > Theoretically, you could have TCP without IP, some other n/w mechanism > besides IP could deliver the data to an address, and TCP could still > verify and sequence that data > > can any one give examples for this ? |
|
|||
|
Re: TCP without IP
"Bill" <bargerw@bellsouth.net> writes:
> <aarklon@gmail.com> wrote in message > news:7d3e7523-a58b-4c13-8e1a-7315b7521794@v1g2000pra.googlegroups.com... >> Hi, >> >> I have read in some books as follows :- >> >> Theoretically, you could have TCP without IP, some other n/w mechanism >> besides IP could deliver the data to an address, and TCP could still >> verify and sequence that data >> >> can any one give examples for this ? > Do you mean un numbered ip? > 0.0.0.0? I would assume he meant "using some other protocol completely". |
![]() |
|
| Thread Tools | Search this Thread |
| Display Modes | |
|
|