Hi Folks,

Given the direction some of the recent discussion has taken, I think some
more explaination is needed, so I have written a scenario that hopefully
should better explain what I mean.

The following is purely theoretical, and any node numbers used are
imaginary. The domain name "fidonet.org" used here is purely an
example, and may not actually be available. The IP numbers used are also
theoretical.

For the purposes of this discussion, the calling node is 1:222/333. That
node wishes to contact node 2:333/444 via IP.

Here are a couple of different scenarios. The first assumes that the target
system is available 24x7 and will therefore always reply -

   1. Node 1:222/333 performs a DNS lookup for its intended target -
        n333.n222.z1.fidonet.org
      and receives an IP address 1.2.3.4.

   2. Node 1:222/333 contacts IP 1.2.3.4, expecting to find a
      "Fidonet Capabilities Server" on that IP address. It identifies 
      itself as node 1:222/333 and asks 1.2.3.4 for the capabilities of    
  node 2:333/444. Note here that the caller does not ask for a 
      specific service, only what services are available.

   3. IP 1.2.3.4 replies to 1:222/333 that node 2:333/444 is currently
      available using -
        BinkP to IP 5.6.7.8 on port 24554
        Telnet to IP 6.7.8.9 on port 24567
      Note that different target IP addresses could be provided here.

   4. Node 1:222/333 decides to use BinkP, so sets about establishing a
      BinkP connection to 5.6.7.8.

   5 All further operations are via BinkP.

Now, let us assume that the target node is "part time" IP. The
above scenario is repeated, however it is the target nodes responsibility
to advise the "Fidonet Capabilities Server" which functions are
currently available for the target. If nothing is available, then at step
3. above, the reply would be "No service is currently available",
otherwise things proceed exactly as before. 
The Capability Server advertises WHAT service is CURRENTLY available, but
only IF the target has told it that it is available. This available table
needs to be updated at regular itervals for part time nodes.

Some notes -

  1. The domain Fidonet.org and all higher level domains, could be      
delegated down the Fidonet *C structure, so that NC's could manage
     their own Network DNS entries, exactly as they do now for Nodelisted
     nodes. The same for RC's and ZC's.

  2. A full time node need not operate a "Fidonet Capabilties Server",
     it could in fact list specific services under its own domain name
     such as -
        n333.n222.z1.fidonet.org        pointing to a host without a server,
        binkp.n333.n222.z1.fidonet.org  pointing to a BinkP host.
     In which case, the calling node attempts to contact the Capabilities  
   Server, which fails, so it can then decide to use DIRECT contact     
methods, to higher levels below the nodes root DNS entry.

  3. The above only refers to IP nodes, all PSTN functionality remains
exactly as it is now. 

I hope this makes it easier to understand just one possible scenario.

Cheers...................pk.


--- Maximus/2 3.01