Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.1 6/24/83; site decvax.UUCP
Path: utzoo!linus!decvax!goutal
From: goutal@decvax.UUCP (Kenneth G. "Kenn" Goutal)
Newsgroups: net.news
Subject: Re: charging for path info
Message-ID: <180@decvax.UUCP>
Date: Wed, 24-Aug-83 10:43:36 EDT
Article-I.D.: decvax.180
Posted: Wed Aug 24 10:43:36 1983
Date-Received: Wed, 24-Aug-83 14:55:13 EDT
References: <611@hao.UUCP>
Organization: DEC UNIX Engineering Group, Merrimack, NH
Lines: 14

I can agree that compiling path info is by no means trivial,
and that if you're doing it by hand it's a pain in the neck.
But don't we already have programs that do this?  If not, why not?
I feel constrained to point out that DECnet (which is set of protocols
and code implementing them, not a specific set of wires and machines)
does this automatically -- it's just a part of normal protocol
to pass routing information around.
Now, I realize that actually changing uucp so that it did this could
be a collossal task, and will probably never happen.
However, it does not seem unreasonable to suggest that path-building 
software could somehow be grafted on top of Usenet,
based on existing software and conventions.
-- Kenn (decvax!goutal)