Groups | Search | Server Info | Login | Register


Groups > comp.mail.uucp > #202

Re: introducing the new federated anarchist networking protocol: UUCP

From Grant Taylor <gtaylor@tnetconsulting.net>
Newsgroups comp.mail.uucp
Subject Re: introducing the new federated anarchist networking protocol: UUCP
Date 2023-12-17 00:07 -0600
Organization TNet Consulting
Message-ID <ulm37m$9se$1@tncsrv09.home.tnetconsulting.net> (permalink)
References (2 earlier) <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>

Show all headers | View raw


On 12/16/23 15:43, Marco Moock wrote:
> Multicast exactly has that ability to have that decision already when 
> processing the MAC address (the NIC only needs to accept multicast 
> frames for multicast MAC addresses the devices listens to) and the 
> dst IP address.

Either the NIC needs to support multicast or it passes the frame up to 
the software to filter.

Even if the NIC supports multicast directly, it has an upper bound on 
the number of multicast MACs that it supports.

There is a small amount of additional demand for processing multicast 
frames.  It's a question of how much and where it is.

> Define network.

I'll go with any layer 2 connection that is able to carry broadcast frames.

> Multicast routing is possible, IIRC it should also be 
> possible between multiple AS,

Yes, it is technically possible.

> but as I know, it isn't used very much.
That is the rub.  Virtually nobody enables support, or explicitly 
disables support, for multicast across the Internet.

> It least for IPTV it is used inside an AS, at least for Deutsche 
> Telekom's Magenta TV service.

Yes, multicast works quite well in closed systems, or within an AS.

Crossing the Internet is decidedly not within an AS.



-- 
Grant. . . .

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