🚀 go-pugleaf

From: Rudy_Nedved@RUDY.FAC.CS.CMU.EDU
Date: Sun, 07 Jul 91 01:19:46 -0400
Subject: Re: Why is the ampr.org namespace flat?


Let's get some ground rules straight.

1) You can pick any addressing system you want. I strongly recomend fixed
   length addresses since the computational overhead tends to be less.

2) You can either use IP addressing at the next level of the system or not.
   Using IP addressing has the win of letting you use IP protocols like UDP
   and TCP.

3) You can then plug this information into the name servers. If you hide your
   random lowest level addresses from the name service level and you use IP
   then you can take advantage of all the installed software out in the world
   that understands this stuff.

Now.....

Let's throw away all of the work that people have done and design a new system
but be practical about it.

A) Domain names are administrative not geographical or microsecond dynamic. Who
   is the administration for AMPR world....but thr Feds (aka FCC). The radios
   have a flat name space so .AMPR world has a flat name space.

B) The world has a running working internet protocol system called TCP/IP. You
   can use anything you want but enabling AMPR world to use TCP/IP is a big
   win. Therefore host have names and IP addresses.

C) You can do anything you damn well pleases with the relatively stable IP
   addresses. Heck you can even re-code the call letters into some weird IP
   address. It does not matter.
   HOWEVER you now have to have some magical box that connects and maintains
   the connection between the IP address world and the AMPR internal address
   world.

Design it, build it and persuade people to use it and you got it made!!! You
can even apply for a new top level domain and your own class A address....
Experimentation is welcome....good designs that are well thought out are rare
and frequently challenge.

Simple banter is old and boring.

-Rudy


----
From: Mark H. Levine <yba@space.mit.edu>
Date: Sat, 6 Jul 91 12:13:35 PDT
Subject: Re: Why is the ampr.org namespace flat?

	From: brian@ucsd.Edu (Brian Kantor)
	Subject: Re: Why is the ampr.org namespace flat?
	Date: 6 Jul 91 05:24:48 GMT

	Just because we're currently using the hack of routing network 44 as
	though it were a bunch of subnets doesn't mean we'll always be doing
	that.  I believe that routing should be taking place at the transport
	(AX.25) level, below the IP level, and that would make the IP address
	space flat too.  Someday we may be able to do it.

Yes, but: are you going to stay connected to internet or not?  Each network
does _not_ get to do its own routing after crossing a gateway.  And gateways
may be more than one, and will be at different points on the network -- so
you have to guranatee that non-AX.25 networks still speak your IP routing in
a way that makes sense.  The internet is _not_ going to move to one host at
a time routing tables to please hams!  You have just required every net 44
gateway to be internet on one side and (now for) something completely different
on the other.  Again, why do you bother with IP addresses at all?

(PS: the name server just became completely useless, too!)


----
From: barry@dgbt.doc.ca (Barry McLarnon)
Date: Sat, 6 Jul 91 16:33:21 EDT
Subject: Another mbox funny?

I recently installed the vanilla 0614 code on our local switch.  When I
telnet in and go into remote sysop mode, the session consistently hangs
when I do a 'route' command - it shows part of the routing table and then
goes into the weeds.  Anyone else seen this one?

Barry VE3JF


----