Subj : human-readable nodelist format
To   : Rick Van Ruth
From : Jasen Betts
Date : Mon Nov 11 2002 06:38 am

Hi Rick.

10-Nov-02 21:21:46, Rick Van Ruth wrote to Scott Little


RVR> Hello Scott.

RVR> 10 Nov 02 20:52, you wrote to me:

RR>>> Then I guess I need to see a full example of the implementation.
RR>>> Got any?

SL>> Erm, sorta.  I generated a list using the routing address syntax
SL>> (fugly, but it contains the full node hierarchy) to see what it
SL>> would look like. Just pretend the keywords are to Andrew's specs
SL>> instead... and ignore the blank keywords and other dodginess :)

SL>> http://members.optushome.com.au/rtscts/rnl.zip

RVR> Ok, I see.. but I still don't understand :-)

RVR> I can see you can have multiple "link" fields in yours, I assume
RVR> a link line for each phone number or domain/ net address?

RVR> Are there any other fields for the format? Like fields that
RVR> currently don't have relevance to the St Louis format but are
RVR> included in this format for future expansion?

It looks like the link feilds are more link records, each has provision for
a fuill set of capability flags, so a multiline and/or multiprotocol system
can list all it's connection methods and capabilities.

-=> Bye <=-

---
* Origin: Paul's Law:  You can't fall off the floor. (3:640/531.42)

You are viewing proxied material from vert.synchro.net. The copyright of proxied material belongs to its original authors. Any comments or complaints in relation to proxied material should be directed to the original authors of the content concerned. Please see the disclaimer for more details.