[FADCA] DNIC setup

[Chuck Hast]

On Fri, 19 Nov 2004 21:16:10 -0500, Dan Babilla <dbabilla at earthlink.net> wrote:
> Sounds like the GCI...Global Cellular Identification code for mobile
> telephone networks.

Yes, I think they use the DCC and NID as part of their digital
routing, particularly
the GSM world.
> 
> Guys,
> 
> Is there anyway we can incorporate TCP/IP network routing on the current or
> Linux version of FPAC or ROSE NET?

This is one of the reasons we want to move to Linux as the switch OS. IP is the
base communications stack in Linux as in any *nix computer. All the ports have
IP addresses even if they are boggus.  But one thing to remember IP by it's
self tends to be rather "messy" in it's routing, so you encap it in
other more stringent
protocols, and get it to it's destination. If you will look at most
networks IP still
runs inside other types of network pipes it does not run alone. But end the end
we want the user to see a IP address, indeed we are already mixing the two
the link from my switch to the switch in Paris France is using axip which encaps
the ax25 frames in IP and allows us to link the switches over the internet, this
mechanisim can go two ways, we can at the same time ship IP frames through
the FPAC network, which works quite well where we have noisy slow speed
links, that do a lot of retries, if it was pure IP the retries relie
on the TCP layer,
if you are using UDP there is no retrying, and UDP for many of our apps is
much more efficient, until we get high speed pipes we have to make things
run as efficient as possible. Here is a neat scenario. You hand a fpac box a
1500 byte ip frame, it frags it down into 6 256 byte ax25 frames and uses the
"M" bit to reconstruct the IP frame on the far end, if one of those pieces gets
lost, only that piece is retried and only between the two points where it got
lost. This will allow us to extend IP to places where we have not been able
to, the idea is to work the protocols off of each other in order to deliver the
service. I do not see FPAC going away, it will just run in the background
delivering IP or other services to where they are needed. As we move to
higher speeds we would be looking at possibly protocols more adept at handling
IP at higher speeds, though the extended ax25 (modulo 128) with selective
reject and the ability to pass frames up to 512 bytes in size would give a new
lease on life for ax25 in this app (this too is built into Linux), so
Linux will give
you what you want but allow us to continue to expand the network and at the
same time add and experiment with the other protocols



> 
> TCP/IP is the networking protocol and routing of the internet and most data
> network these days, we need move toward the current technology...

Yes, but just remember that it rides in things like SONET, ATM, FDDI, Ethernet,
and many other protcols and encap it, you do not see them but they are there.

IP  by it's self does not lend well to RF, that is why the cellular
and other wireless
systems use other protocols to carry it, we have the same sort of issues and we
have to tools at hand to experiment and make it even better.

Get a Linux box and start playing with it, you will see what I mean.