Other Directory Sites: SeekWonder | Directory Owners Forum
The following archive was created by hippie-mail 7.98617-22 on Sat Apr 10 1999 - 01:11:01
mlynn@west.raytheon.com
Fri, 28 Aug 1998 09:57 -0700 (PDT)
Please help get me off your distribution list. I'm inundated with you
guys' emails. I think I'm somehow 'attached' to the "CodherPlunks"
address.
______________________________ Reply Separator _________________________________
Subject: IRC (was Re: Crypto Coding Project)
Author: Laurent.Demailly@Sun.COM at mime
Date: 8/27/98 07:04 PM
Just a couple of corrections :
(I don't either pretend to know all the details
of current ircd's but I used to know them a couple
of years ago).
Daniel Pittman writes:
> Mok-Kong Shen wrote:
>
> [Multicast protocols]
> > Could someone give a short yet concrete summary of the techniques
> > currently employed by IRC?
>
> Sure. I cannot speak for the latest and greatest enhanced networks, but
> I know the basic network technology fairly well. I do not believe that
> this has changed in fundamental use, just in the overlayed extensions.
>
> The IRC network can be seen as an acyclic graph of servers, with clients
> hanging off each server as leaf nodes. For the purposes of the actual
> network itself, client software can be ignored, pretty much.
>
> The basic architecture of the network is a hand woven system with links
> between servers constructed and maintained by hand. Any loop in the
> system will bring the entire thing to it's knees, while a dropped
no,
because each server knows about the other servers and
trying to (re)introduce a link already existing
immediatly cause the introducing server to be rejected (squit'ed).
(though lag could cause bad side effects linked to that)
> connection between servers will break the network into two parts.
>
> Message propogation is through a flooding algorythm. Each server on
> reciept of a new message will flood it to every server it contacts, with
> the exception of the originating server. Thus a message will jump from
It's an "implementation detail" but I don't think it is entirely true:
each server actually routes messages to downlinks only if those servers
actually have users 'subscribed' in the channels (they know all
users, thus scalability problems)
> server to server in an expanding ring, crossing the entire graph.
>
> Private messages are passed from a server only to the targeted client,
> while the channel concept is simply a list of client connections that
> recieve input directed to the channel as a name.
>
> The DCC (Direct Client Connection) protocol uses the network propogation
> to establish the location of both participants, then opens a direct
> TCP/IP connection between them, I believe.
>
> Every byte of data from a client goes to every server, with no
> intelligence in the routing. The fact it works at all on the current
no, see above
[...]
There have been ideas and discussions (and even some implementations)
for years on how to improve Irc, do a search to find the infos
if you are interested.
Best regards
Laurent
RFC-822-headers:
Received: from CONVERSION-DAEMON by mail.hac.com (PMDF V5.1-10 #26245)
id <0EYD00F01S0NK7@mail.hac.com>; Thu, 27 Aug 1998 20:50:48 -0700 (PDT)
Received: from PROCESS-DAEMON by mail.hac.com (PMDF V5.1-10 #26245)
id <0EYD00F01S0MK6@mail.hac.com>; Thu, 27 Aug 1998 20:50:47 -0700 (PDT)
Received: from fw-es05.hac.com by mail.hac.com (PMDF V5.1-10 #26245)
with ESMTP id <0EYD00C7DS0M3E@mail.hac.com>; Thu,
27 Aug 1998 20:50:46 -0700 (PDT)
Received: from toad.com ([140.174.2.1]) by fw-es05.hac.com (8.9.0/8.9.0)
with ESMTP id UAA12694; Thu, 27 Aug 1998 20:50:59 -0700 (PDT)
Received: (from Received: (from majordom@localhost) by toad.com (8.7.5/8.7.3)
id TAA22166 for CodherPlunks-outgoing; Thu, 27 Aug 1998 19:06:16 -0700 (PDT)
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
by toad.com (8.7.5/8.7.3) with SMTP id TAA22161 for <CodherPlunks@toad.com>;
Thu, 27 Aug 1998 19:06:13 -0700 (PDT)
Received: from sunmail1.Sun.COM ([129.145.1.2])
by mercury.Sun.COM (SMI-8.6/mail.byaddr) with SMTP id TAA07246; Thu,
27 Aug 1998 19:05:40 -0700
Received: from jurassic.eng.sun.com by sunmail1.Sun.COM (SMI-8.6/SMI-4.1)
id TAA13354; Thu, 27 Aug 1998 19:05:38 -0700
Received: from pomerol.eng.sun.com (pomerol [129.146.82.126])
by jurassic.eng.sun.com (8.9.1b+Sun/8.9.1) with SMTP id TAA16613; Thu,
27 Aug 1998 19:05:38 -0700 (PDT)
Received: by pomerol.eng.sun.com (SMI-8.6/SMI-SVR4) id TAA04680; Thu,
27 Aug 1998 19:04:30 -0700
Date: Thu, 27 Aug 1998 19:04:28 -0700 (PDT)
From: Laurent Demailly <Laurent.Demailly@Sun.COM>
Subject: IRC (was Re: Crypto Coding Project)
In-reply-to: <35E5485A.53AEA8D3@osa.de>
Sender: owner-CodherPlunks@toad.com
Message-id: <13798.4140.792190.734520@pomerol>
MIME-version: 1.0
X-Mailer: VM 6.59 under Emacs 19.34.1
Precedence: bulk
References: <199808191353.JAA19027@jekyll.piermont.com>
<35DAFE96.EE4A71CA@stud.uni-muenchen.de>
<19980827123432.A895@caffeine.ix.net.nz>
<35E517E6.BFF0786F@stud.uni-muenchen.de> <35E5485A.53AEA8D3@osa.de>
The following archive was created by hippie-mail 7.98617-22 on Sat Apr 10 1999 - 01:11:01