Groups | Search | Server Info | Login | Register


Groups > comp.mail.uucp > #205

Re: introducing the new federated anarchist networking protocol: UUCP

Path csiph.com!news.mixmin.net!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From immibis <news@immibis.com>
Newsgroups comp.mail.uucp
Subject Re: introducing the new federated anarchist networking protocol: UUCP
Date Tue, 19 Dec 2023 15:04:59 +0100
Organization A noiseless patient Spider
Lines 35
Message-ID <uls7ub$27po$5@dont-email.me> (permalink)
References <udkag0$idlh$1@dont-email.me> <udkelh$iocn$2@dont-email.me> <ulke8o$2eluu$2@dont-email.me> <ulkuai$qcq$2@tncsrv09.home.tnetconsulting.net> <ulkvhe$2hecm$1@dont-email.me> <ull181$mlk$1@tncsrv09.home.tnetconsulting.net> <ull5mm$2ib41$1@dont-email.me> <ulm37m$9se$1@tncsrv09.home.tnetconsulting.net> <ulouhj$3dih3$1@dont-email.me> <ulplvb$gp8$4@tncsrv09.home.tnetconsulting.net>
MIME-Version 1.0
Content-Type text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding 8bit
Injection-Date Tue, 19 Dec 2023 14:04:59 -0000 (UTC)
Injection-Info dont-email.me; posting-host="c95b9f06949c68a7be13f701a542acec"; logging-data="73528"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX19YfzxczGXo94tR5JbvMeW4"
User-Agent Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.14.0
Cancel-Lock sha1:Z1c+8Xy4Nr5+vK3Din9aFFop380=
Content-Language en-US
In-Reply-To <ulplvb$gp8$4@tncsrv09.home.tnetconsulting.net>
Xref csiph.com comp.mail.uucp:205

Show key headers only | View raw


On 12/18/23 15:46, Grant Taylor wrote:
> My interpretation was something along the lines of the years old issue 
> of needing to source route from the sender to the recipient.  For a 
> while there was effort under way to have UUCP nodes derive a route to 
> the destination node.  My understanding is that this was based on shared 
> data and wasn't automatically discoverable in any sense.
> 

Routing inherently relies on shared data. Nodes need to know how distant 
nodes are connected to each other. If you already have Usenet running, 
you can propagate it through Usenet.

Routing is a theoretically solved problem, but you might not like the 
tradeoffs of any particular solution. There are two main ideas: one is 
to propagate information about the entire network's connectivity 
throughout the entire network, so that each node can independently 
compute the paths it needs. This works quite well until it runs into 
scalability problems (probably in the hundreds of thousands, if not 
millions of nodes nowadays). This is called link-state routing, and is 
used in most routing protocols.

The other idea is for each node to tell its neighbours which nodes it 
knows how to reach. There's no non-local data sharing. While this works 
very well in a spanning tree, you have to add some extra information to 
make it handle loops acceptably. For UUCP you'd want to pass the whole 
bang path around (if you still want source routing), and you get a 
path-vector protocol similar to BGP. Most administratively closed 
networks use link-state routing, and the internet at large uses a 
path-vector protocol (BGP) which seems to work better as it requires 
less cooperation between nodes.

Note that link-state routing of hop-by-hop-routed protocols requires all 
nodes to compute exactly the same paths to avoid cycles. This may be 
another reason the Internet uses path-vector. This limitation doesn't 
apply to source-routed protocols.

Back to comp.mail.uucp | Previous | NextPrevious in thread | Next in thread | Find similar


Thread

introducing the new federated anarchist networking protocol: UUCP Mima-sama <mi@masa.ma> - 2023-09-10 19:49 +0800
  Re: introducing the new federated anarchist networking protocol: UUCP Marco Moock <mm+usenet-es@dorfdsl.de> - 2023-09-10 15:00 +0200
    Re: introducing the new federated anarchist networking protocol: UUCP immibis <news@immibis.com> - 2023-12-16 16:03 +0100
      Re: introducing the new federated anarchist networking protocol: UUCP Grant Taylor <gtaylor@tnetconsulting.net> - 2023-12-16 13:37 -0600
        Re: introducing the new federated anarchist networking protocol: UUCP Marco Moock <mm+usenet-es@dorfdsl.de> - 2023-12-16 20:58 +0100
          Re: introducing the new federated anarchist networking protocol: UUCP Grant Taylor <gtaylor@tnetconsulting.net> - 2023-12-16 14:27 -0600
            Re: introducing the new federated anarchist networking protocol: UUCP Marco Moock <mm+usenet-es@dorfdsl.de> - 2023-12-16 22:43 +0100
              Re: introducing the new federated anarchist networking protocol: UUCP Grant Taylor <gtaylor@tnetconsulting.net> - 2023-12-17 00:07 -0600
                Re: introducing the new federated anarchist networking protocol: UUCP immibis <news@immibis.com> - 2023-12-18 09:06 +0100
                Re: introducing the new federated anarchist networking protocol: UUCP Grant Taylor <gtaylor@tnetconsulting.net> - 2023-12-18 08:46 -0600
                Re: introducing the new federated anarchist networking protocol: UUCP immibis <news@immibis.com> - 2023-12-19 15:04 +0100
                Re: introducing the new federated anarchist networking protocol: UUCP Grant Taylor <gtaylor@tnetconsulting.net> - 2023-12-19 09:04 -0600
    Re: introducing the new federated anarchist networking protocol: UUCP Andy Valencia <vandys@vsta.org> - 2023-12-25 15:06 -0800
      Re: introducing the new federated anarchist networking protocol: UUCP immibis <news@immibis.com> - 2024-01-02 00:38 +0100
  Re: introducing the new federated anarchist networking protocol: UUCP cp@ruraldashnetwork.com (CP) - 2023-09-22 14:46 +0000

csiph-web