From MAILER-DAEMON Thu Feb 20 18:34:07 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18m0CS-0000AI-00
	for mharc-unity-irc3@gnu.org; Thu, 20 Feb 2003 18:33:56 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18m0CO-0008ST-00
	for unity-irc3@nongnu.org; Thu, 20 Feb 2003 18:33:52 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18m0C9-00083N-00
	for unity-irc3@nongnu.org; Thu, 20 Feb 2003 18:33:38 -0500
Received: from ms-2.rz.rwth-aachen.de ([134.130.3.131]
	helo=ms-dienst.rz.rwth-aachen.de)
	by monty-python.gnu.org with esmtp (Exim 4.10.13)	id 18m0BE-0006ao-00
	for unity-irc3@nongnu.org; Thu, 20 Feb 2003 18:32:40 -0500
Received: from ms-2 (ms-dienst.rz.RWTH-Aachen.DE [134.130.3.132])
 by ms-dienst.rz.rwth-aachen.de
 (iPlanet Messaging Server 5.2 Patch 1 (built Aug 19 2002))
 with ESMTP id <0HAM00J7WS24AA@ms-dienst.rz.rwth-aachen.de> for
 unity-irc3@nongnu.org; Fri, 21 Feb 2003 00:32:29 +0100 (MET)
Received: from r220-1.rz.RWTH-Aachen.DE ([134.130.3.31])
	by ms-2 (MailMonitor for SMTP v1.2.2 ) ;
	Fri, 21 Feb 2003 00:32:28 +0100 (MET)
Received: from neuron (jast@p508D98EE.dip.t-dialin.net [80.141.152.238])
	h1KNWIGi000005	for
	<unity-irc3@nongnu.org>; Fri, 21 Feb 2003 00:32:18 +0100 (MET)
Date: Fri, 21 Feb 2003 00:34:42 +0100
From: Jan Krueger <jan.krueger@rwth-aachen.de>
To: unity-irc3@nongnu.org
Message-id: <20030221003442.31c1e239.jan.krueger@rwth-aachen.de>
MIME-version: 1.0
X-Mailer: Sylpheed version 0.8.10claws (GTK+ 1.2.10; i686-pc-linux-gnu)
Content-type: text/plain; charset=ISO-8859-1
Content-transfer-encoding: quoted-printable
Subject: [Unity-irc3] Realistic review of drafts; revival of list
X-BeenThere: unity-irc3@nongnu.org
X-Mailman-Version: 2.1b5
Precedence: list
Reply-To: "irc3 \(Unity\) public discussion" <unity-irc3@nongnu.org>
List-Id: irc3 (Unity) public discussion <unity-irc3.nongnu.org>
List-Help: <mailto:unity-irc3-request@nongnu.org?subject=help>
List-Post: <mailto:unity-irc3@nongnu.org>
List-Subscribe: <http://mail.nongnu.org/mailman/listinfo/unity-irc3>,
	<mailto:unity-irc3-request@nongnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/unity-irc3>
List-Unsubscribe: <http://mail.nongnu.org/mailman/listinfo/unity-irc3>,
	<mailto:unity-irc3-request@nongnu.org?subject=unsubscribe>
X-List-Received-Date: Thu, 20 Feb 2003 23:33:53 -0000

Hi everyone,

I've been thinking about our stuff again. First of all, I wondered if you're
all still alive. If you are but ceased to be interested in this projects - =
no
problem. Just let me know; I don't want to talk to e-mail filters all the
time. ;)

Ok, here are my new ideas. Comment and questonise as much as you can.
For a start: this design is much more simple (read: easier to code ;)).

* Separation of one-to-one and one-to-many (channels)
  - by moving the responsibility for managing channels to different servers,
    we get rid of the question of domains and politics. Since most of a
    network's politics are about channels, this would be really useful.
    People could just choose where they get their account from and then
    where they get their channel from. Again, this design would require most
    of the servers to require account registrations. Of course, traditional
    IRCNet-style non-owned nicks and channels are possible as well. But
    who'd want that. ;)
  - we'd have the usual network of servers which clients can connect to. But
    in order to join a channel, they'd have to establish another connection
    to the server that runs a channel. They can then exchange all informati=
on
    via that server - including state information and stuff. No impact on t=
he
    network any longer - everything would remain on the channel server.
  - another beauty: everyone could run their own channel server for tempora=
ry
    channels without having to register one.
  - channel politics are decided one by the channel server - it's the absol=
ute
    authority of the channels it manages.
  - can't stress it enough ;) - no desyncs, no impact on the network when
    channels get spammed. The network itself wouldn't even have to provide
    channel servers - other providers could do that.
* Less network, more server
  - that's quite the opposite of what we thought about before. Server have
    their own domain each, registrations are only local as well.
    On a server called server1.quackweb.org, a user can register an account
    called user@server1.quackweb.org.
    On a channel server called cs.quackweb.org, a user can register a chann=
el
    called #channel@cs.quackweb.org (FIXME: do we still want '#'? looks ugl=
y).
  - network-wide bans are no longer possible. I suggest a central blacklist
    that considers a user blacklisted if a certain percentage of all known
    servers have added a complaint about the user. To be decided on.
    This mechanism might also be used for badly behaving servers.
    Channel servers, however, don't need to be banned since they are passiv=
e.
    Well, mostly. Of course they have to validate the identity of users
    connecting to them and stuff.
  - here's the real beauty: Server operators don't have any noticable power
    whatsoever! Only things they can do is place a local ban/jupe, complain=
 to
    a blacklist server, disconnect users, delete accounts. Welcome back.
  - channel server operators, however, have some more power. Anyway, since
    channel servers don't require any kind of IRC services, everyone should
    have the same rights for a full-featured channel, so the operators don't
    really have an advantage. Of course, they can badchan, unregister/close
    channels and stuff. They could even take control on a channel they don't
    own. But then again, nobody would use a channel server with corrupted
    opers, would they? ;)
  - here's an idea about the network mechanism. To keep the routing algorit=
hm
    simple (read: avoid writing one at all), how about directly connecting =
to
    remote servers? We could reserve a couple of FDs to connecting to other
    servers, then keeping connections open after sending something to anoth=
er
    server. When we get an overflow, throw out the less-used connection and
    connect to the new server instead.
    Obvious advantages: no routing algorithm needed (i.e. routing mechanisms
    of The Internet are used), should still be pretty fast.
  - now it's scalable like hell. Everything can be torn apart without any
    problems. Just add a server here and another one there and we have
    sufficient capacity again.
  - again, we'd want to make it easy for people to contribute a server.
    I hear the SAuth ringing. ;)
* Obvious changes
  - no network-wide index of people online. It's no problem to list other
    users within the same domain, but it's just impossible to do that for
    the entire network. What do we do?
    We add some kind of directory server.
    We add an ICQ-style notify list.
    We could even add a regional index of people that's updated automatical=
ly,
       i.e. a Really Useful directory of people that live in the same region
       as the one who asks for info. This would require one directory server
       per region, obviously.
    Note that directories are some kind of luxury. People can spread their
    personal chat address (why not URL style?
    greatchat://server.domain.org:port/username - or e-mail style?
    username@server.domain.org:port) in whatever way they want.
    Let the WWW be our directory. Saves us a lot of trouble. ;)
  - same for index of channels. Every channel server could supply a detailed
    description of the channels registered with it, however. Their choice,
    not ours.
* Benefits for users
  - they can choose a domain (remember, domains are l33t)
  - they can register an account
  - it'll be easy for them to remember the server to connect to since it wi=
ll
    be the same as the domain part of their chat ID
  - they can register channels with different domains
  - they have full control over their channels (we could even build a nice =
web
    interface into the channel server software)
  - they can provide their own channel server without having to run their o=
wn
    network (expansion!).
  - people can still decide whether they want registrations or not (servers
    that don't support/allow registration should tell the other servers so
    users (and channel servers) don't get confused if the person behind an
    ID changes).


Questions? Suggestions? Flames? Eager to hear whatever you can come up with.
And now:
__      __    _                   _
\ \    / /_ _| |_____   _  _ _ __| |
 \ \/\/ / _` | / / -_) | || | '_ \_|
  \_/\_/\__,_|_\_\___|  \_,_| .__( )  ;)
                            |_|
--
regards,                                 |     http://arc.pasp.de
Jan Kr=FCger                               | ()  ascii ribbon campaign
primary mail: jan.krueger@rwth-aachen.de | /\  - against html mail
http://www.jast.net.tc/                  |     - against microsoft attachme=
nts




From MAILER-DAEMON Thu Feb 20 20:38:57 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18m29O-0005mI-00
	for mharc-unity-irc3@gnu.org; Thu, 20 Feb 2003 20:38:54 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18m29H-0005OW-00
	for unity-irc3@nongnu.org; Thu, 20 Feb 2003 20:38:47 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18m299-0005Dp-00
	for unity-irc3@nongnu.org; Thu, 20 Feb 2003 20:38:40 -0500
Received: from dwestley.demon.co.uk ([62.49.21.22] helo=fragalot.com)
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18m291-00050T-00
	for unity-irc3@nongnu.org; Thu, 20 Feb 2003 20:38:31 -0500
Received: from biggeek ([10.0.0.3])
	by fragalot.com ([10.0.0.5])
	with SMTP (MDaemon.PRO.v6.0.7.R)
	for <unity-irc3@nongnu.org>; Fri, 21 Feb 2003 01:38:24 +0000
From: "David Westley" <dave@fragalot.com>
To: "irc3 \(Unity\) public discussion" <unity-irc3@nongnu.org>
Subject: RE: [Unity-irc3] Realistic review of drafts; revival of list
Date: Fri, 21 Feb 2003 01:38:23 -0000
Message-ID: <AIEGKGKEDNIIMGHFPGOOOEMMDHAA.dave@fragalot.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
Importance: Normal
In-Reply-To: <20030221003442.31c1e239.jan.krueger@rwth-aachen.de>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
X-Authenticated-Sender: dave@fragalot.com
X-MDRemoteIP: 10.0.0.3
X-Return-Path: dave@fragalot.com
X-MDaemon-Deliver-To: unity-irc3@nongnu.org
X-BeenThere: unity-irc3@nongnu.org
X-Mailman-Version: 2.1b5
Precedence: list
Reply-To: dave@fragalot.com, "irc3 \(Unity\) public discussion"
	<unity-irc3@nongnu.org>
List-Id: irc3 (Unity) public discussion <unity-irc3.nongnu.org>
List-Help: <mailto:unity-irc3-request@nongnu.org?subject=help>
List-Post: <mailto:unity-irc3@nongnu.org>
List-Subscribe: <http://mail.nongnu.org/mailman/listinfo/unity-irc3>,
	<mailto:unity-irc3-request@nongnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/unity-irc3>
List-Unsubscribe: <http://mail.nongnu.org/mailman/listinfo/unity-irc3>,
	<mailto:unity-irc3-request@nongnu.org?subject=unsubscribe>
X-List-Received-Date: Fri, 21 Feb 2003 01:38:53 -0000


Still alive and still interested...just been a bit busy with work! :/

------------------------------ <snip> ------------------------------

* Separation of one-to-one and one-to-many (channels)
  - by moving the responsibility for managing channels to different servers,
    we get rid of the question of domains and politics. Since most of a
    network's politics are about channels, this would be really useful.
    People could just choose where they get their account from and then
    where they get their channel from. Again, this design would require most
    of the servers to require account registrations. Of course, traditional
    IRCNet-style non-owned nicks and channels are possible as well. But
    who'd want that. ;)

------------------------------ </snip> ------------------------------

Most networks politics is about content and users not how channels are
run...that's a channel operators deal, also isn't nick/channel registration
a network politics area??

------------------------------ <snip> ------------------------------

  - we'd have the usual network of servers which clients can connect to. But
    in order to join a channel, they'd have to establish another connection
    to the server that runs a channel. They can then exchange all
information
    via that server - including state information and stuff. No impact on
the
    network any longer - everything would remain on the channel server.

------------------------------ </snip> ------------------------------

This would need a client change would it not? Can you be sure that the
client coders would be willing to change their programs to support this, and
if so would it be possible for them to support both protocols with a single
codebase?

------------------------------ <snip> ------------------------------

  - another beauty: everyone could run their own channel server for
temporary
    channels without having to register one.

------------------------------ </snip> ------------------------------

Am I right in thinking that if you wanted people to connect to a channel
you've made on your own little channel server they'd need to connect to your
IP/hostname to be able to talk on that channel, there by making old local
channels available but NOT part of the general server software?

------------------------------ <snip> ------------------------------

  - channel politics are decided one by the channel server - it's the
absolute
    authority of the channels it manages.

------------------------------ </snip> ------------------------------

See 1st comment

------------------------------ <snip> ------------------------------

* Less network, more server
  - that's quite the opposite of what we thought about before. Server have
    their own domain each, registrations are only local as well.
    On a server called server1.quackweb.org, a user can register an account
    called user@server1.quackweb.org.
    On a channel server called cs.quackweb.org, a user can register a
channel
    called #channel@cs.quackweb.org (FIXME: do we still want '#'? looks
ugly).

------------------------------ </snip> ------------------------------

Could you expand on this a bit more as I'm not sure I understand this fully.
(Yeah I know I'm supposed to be one of the brainer ones but sometimes ideas
need to be explained a fair bit before people understand them :P)

------------------------------ <snip> ------------------------------

  - network-wide bans are no longer possible. I suggest a central blacklist
    that considers a user blacklisted if a certain percentage of all known
    servers have added a complaint about the user. To be decided on.
    This mechanism might also be used for badly behaving servers.
    Channel servers, however, don't need to be banned since they are
passive.
    Well, mostly. Of course they have to validate the identity of users
    connecting to them and stuff.

------------------------------ </snip> ------------------------------

I can hear the cries of IRC Operators..."I can't ban this fucker from the
network anymore!!!!!" Also how exactly would these channel servers validate
the identity of the users connecting to them without connecting to a client
server and requesting information from it, and if that is what it does then
how do you get around corrupt channel server operator or maybe a comprimised
channel server?

------------------------------ <snip> ------------------------------

  - channel server operators, however, have some more power. Anyway, since
    channel servers don't require any kind of IRC services, everyone should
    have the same rights for a full-featured channel, so the operators don't
    really have an advantage. Of course, they can badchan, unregister/close
    channels and stuff. They could even take control on a channel they don't
    own. But then again, nobody would use a channel server with corrupted
    opers, would they? ;)

------------------------------ </snip> ------------------------------

How would you stop someone from stealing your channel when you no one is
around if there are no services?

------------------------------ <snip> ------------------------------

  - here's an idea about the network mechanism. To keep the routing
algorithm
    simple (read: avoid writing one at all), how about directly connecting
to
    remote servers? We could reserve a couple of FDs to connecting to other
    servers, then keeping connections open after sending something to
another
    server. When we get an overflow, throw out the less-used connection and
    connect to the new server instead.
    Obvious advantages: no routing algorithm needed (i.e. routing mechanisms
    of The Internet are used), should still be pretty fast.
  - now it's scalable like hell. Everything can be torn apart without any
    problems. Just add a server here and another one there and we have
    sufficient capacity again.

------------------------------ </snip> ------------------------------

This could do with more explaination too.

------------------------------ <snip> ------------------------------

* Obvious changes
  - no network-wide index of people online. It's no problem to list other
    users within the same domain, but it's just impossible to do that for
    the entire network. What do we do?
    We add some kind of directory server.
    We add an ICQ-style notify list.
    We could even add a regional index of people that's updated
automatically,
       i.e. a Really Useful directory of people that live in the same region
       as the one who asks for info. This would require one directory server
       per region, obviously.
    Note that directories are some kind of luxury. People can spread their
    personal chat address (why not URL style?
    greatchat://server.domain.org:port/username - or e-mail style?
    username@server.domain.org:port) in whatever way they want.
    Let the WWW be our directory. Saves us a lot of trouble. ;)
  - same for index of channels. Every channel server could supply a detailed
    description of the channels registered with it, however. Their choice,
    not ours.

------------------------------ </snip> ------------------------------

I really like the idea of a regional index of users online however it would
need to take its info from some registration details (assuming people don't
lie) or use the information from an IP block lookup but again that can be
faked by people using a bouncer. Granted that with IPv6 it would be
impossible (I think) to spoof/fake your OWN IP but you've still got n+1
users on bouncers.
Alot of this stuff still needs alot more explaination.




I know it looks like I've pulled this apart but it's what you asked to be
done, also this way other people might better understand it :)


David Westley




From MAILER-DAEMON Fri Feb 21 09:23:17 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18mE2P-0005xT-00
	for mharc-unity-irc3@gnu.org; Fri, 21 Feb 2003 09:20:29 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18m7SJ-0007xt-00
	for unity-irc3@nongnu.org; Fri, 21 Feb 2003 02:18:47 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18m7SH-0007qU-00
	for unity-irc3@nongnu.org; Fri, 21 Feb 2003 02:18:46 -0500
Received: from smtp.hccnet.nl ([62.251.0.13])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18m7SG-0007hK-00
	for unity-irc3@nongnu.org; Fri, 21 Feb 2003 02:18:44 -0500
Received: from spare.hccnet.nl by smtp.hccnet.nl
	<unity-irc3@nongnu.org>	id h1L7IfVD005401 (8.12.5/2.00);
	Fri, 21 Feb 2003 08:18:41 +0100 (MET)
Message-Id: <200302210718.h1L7IfVD005401@smtp.hccnet.nl>
Content-Transfer-Encoding: binary
Content-Type: multipart/mixed; boundary="_----------=_104581192164023"
MIME-Version: 1.0
X-Mailer: MIME::Lite 2.102  (B2.11; Q2.03)
Date: Fri, 21 Feb 2003 07:18:41 UT
From: c.hoogenboezem@hccnet.nl
To: unity-irc3@nongnu.org
Cc: 
Subject: Re: [Unity-irc3] Realistic review of drafts; revival of list
X-Mailman-Approved-At: Fri, 21 Feb 2003 09:20:27 -0500
X-BeenThere: unity-irc3@nongnu.org
X-Mailman-Version: 2.1b5
Precedence: list
Reply-To: "irc3 \(Unity\) public discussion" <unity-irc3@nongnu.org>
List-Id: irc3 (Unity) public discussion <unity-irc3.nongnu.org>
List-Help: <mailto:unity-irc3-request@nongnu.org?subject=help>
List-Post: <mailto:unity-irc3@nongnu.org>
List-Subscribe: <http://mail.nongnu.org/mailman/listinfo/unity-irc3>,
	<mailto:unity-irc3-request@nongnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/unity-irc3>
List-Unsubscribe: <http://mail.nongnu.org/mailman/listinfo/unity-irc3>,
	<mailto:unity-irc3-request@nongnu.org?subject=unsubscribe>
X-List-Received-Date: Fri, 21 Feb 2003 07:18:48 -0000

This is a multi-part message in MIME format.

--_----------=_104581192164023
Content-Disposition: inline
Content-Length: 109
Content-Transfer-Encoding: binary
Content-Type: text/plain

I certainly am alive :) I will read your emails when I get home at once.

Thanks,
Chris "raz" Hoogenboezem
--_----------=_104581192164023--




From MAILER-DAEMON Sat Feb 22 10:24:16 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18mbVf-00086B-00
	for mharc-unity-irc3@gnu.org; Sat, 22 Feb 2003 10:24:15 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18mbVd-00082Y-00
	for unity-irc3@nongnu.org; Sat, 22 Feb 2003 10:24:13 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18mbV7-00074T-00
	for unity-irc3@nongnu.org; Sat, 22 Feb 2003 10:24:13 -0500
Received: from ms-2.rz.rwth-aachen.de ([134.130.3.131]
	helo=ms-dienst.rz.rwth-aachen.de)
	by monty-python.gnu.org with esmtp (Exim 4.10.13)	id 18mbV7-0006zg-00
	for unity-irc3@nongnu.org; Sat, 22 Feb 2003 10:23:41 -0500
Received: from ms-1 (ms-1 [134.130.3.130]) by ms-dienst.rz.rwth-aachen.de
 (iPlanet Messaging Server 5.2 Patch 1 (built Aug 19 2002))
 with ESMTP id <0HAP00BP0U8Q52@ms-dienst.rz.rwth-aachen.de> for
 unity-irc3@nongnu.org; Sat, 22 Feb 2003 16:12:26 +0100 (MET)
Received: from r220-1.rz.RWTH-Aachen.DE ([134.130.3.31])
	by ms-1 (MailMonitor for SMTP v1.2.2 ) ;
	Sat, 22 Feb 2003 16:12:25 +0100 (MET)
Received: from neuron (jast@p508DA63C.dip.t-dialin.net [80.141.166.60])
	h1MFCFdJ026652	for
	<unity-irc3@nongnu.org>; Sat, 22 Feb 2003 16:12:16 +0100 (MET)
Date: Sat, 22 Feb 2003 16:14:53 +0100
From: Jan Krueger <jan.krueger@rwth-aachen.de>
Subject: Re: [Unity-irc3] Realistic review of drafts; revival of list
In-reply-to: <AIEGKGKEDNIIMGHFPGOOOEMMDHAA.dave@fragalot.com>
To: "irc3 (Unity) public discussion" <unity-irc3@nongnu.org>
Message-id: <20030222161453.0aba991b.jan.krueger@rwth-aachen.de>
MIME-version: 1.0
X-Mailer: Sylpheed version 0.8.10claws (GTK+ 1.2.10; i686-pc-linux-gnu)
Content-type: text/plain; charset=ISO-8859-1
Content-transfer-encoding: quoted-printable
References: <20030221003442.31c1e239.jan.krueger@rwth-aachen.de>
 <AIEGKGKEDNIIMGHFPGOOOEMMDHAA.dave@fragalot.com>
X-BeenThere: unity-irc3@nongnu.org
X-Mailman-Version: 2.1b5
Precedence: list
Reply-To: "irc3 \(Unity\) public discussion" <unity-irc3@nongnu.org>
List-Id: irc3 (Unity) public discussion <unity-irc3.nongnu.org>
List-Help: <mailto:unity-irc3-request@nongnu.org?subject=help>
List-Post: <mailto:unity-irc3@nongnu.org>
List-Subscribe: <http://mail.nongnu.org/mailman/listinfo/unity-irc3>,
	<mailto:unity-irc3-request@nongnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/unity-irc3>
List-Unsubscribe: <http://mail.nongnu.org/mailman/listinfo/unity-irc3>,
	<mailto:unity-irc3-request@nongnu.org?subject=unsubscribe>
X-List-Received-Date: Sat, 22 Feb 2003 15:24:14 -0000

Hi.
Thanks for questions and stuff. Here goes reply.


> Most networks politics is about content and users not how channels are
> run...that's a channel operators deal, also isn't nick/channel registrati=
on
> a network politics area??
Not any longer if we move channels out of the network. Users can now choose
seperately between what kind of channels to use and what kind of network to
use. What's best: if they get fed up with their server, they can just use
another one and resume chatting with the same people.
Obvious problem here: global network bans. We need to discuss those. Do we
want them? If so, who'll be allowed to place one?


> This would need a client change would it not? Can you be sure that the
> client coders would be willing to change their programs to support this, =
and
> if so would it be possible for them to support both protocols with a sing=
le
> codebase?
We could support different client protocols. In fact, this would make it
easier for people to switch anyway, so I'm all for it. We could even run
proxy servers that proxy IRC clients into the network transparently.
We'll have to design different protocols in that case - our own, an IRC2
compatible and perhaps (AIM|ICQ|Jabber|MSN) compatible ones.


> Am I right in thinking that if you wanted people to connect to a channel
> you've made on your own little channel server they'd need to connect to y=
our
> IP/hostname to be able to talk on that channel, there by making old local
> channels available but NOT part of the general server software?
Since people will be connecting to the channel server, channels will be loc=
al
and global at the same time. Local - they reside on one server. Global -
everyone can use them.
In the case of proxies mentioned above, clients won't even notice that they=
're
opening a separate connection to a channel since the proxy will do it for
them.
We could even make the main server software tunnel all channel traffic, but=
 in
that case we'd waste quite some additional FDs on the server.


>> [channel politics]
> See 1st comment
I'm talking about what features channel operators get. I think that's a
politic thing as well - some of the present networks offer registrations, s=
ome
don't. Then there's Q and there's ChanServ. With the design I'm talking abo=
ut
right now, clients can decide what kind of channel they want on their own
(provided there's a server that offers what they want).


>> [domains, channel domains and stuff]
> Could you expand on this a bit more as I'm not sure I understand this ful=
ly.
> (Yeah I know I'm supposed to be one of the brainer ones but sometimes ide=
as
> need to be explained a fair bit before people understand them :P)
Sure.
With the original Unity design, we had the ideas of domains. Every domain
contains a bunch of servers, every domain has its channels, and so on.
What is new now is that every domain contains one server only. This way, we
don't need to do any bursts at all! No bursts, no lists of users and
channels to be sync'd, no desyncs.
This is much like with e-mails - a mail domain is handled by one MX server.
Still you can easily contact people that reside on another server.
Now we can have user domains and channel domains, thus we'd have two differ=
ent
kinds of servers, namely user servers and channel servers. User servers host
users while channel servers host groups/channels. Staying with the example,=
 a
channel server could be compared with a mailing list server in the e-mail
world.
Of course, nobody says there can't be a mixed domain - we have those too in
the e-mail world, i.e. a server that provides e-mail accounts for people and
mailing lists at the same time. Nongnu.org is one of those servers.


> I can hear the cries of IRC Operators..."I can't ban this fucker from the
> network anymore!!!!!" Also how exactly would these channel servers valida=
te
> the identity of the users connecting to them without connecting to a clie=
nt
> server and requesting information from it, and if that is what it does th=
en
> how do you get around corrupt channel server operator or maybe a comprimi=
sed
> channel server?
* That's the only drawback of the design that I can think of right now - it=
's
  more decentralised. Only thing we can do about global bans is setting up a
  team of people who maintain a blacklist. Corruption alert though.
  Global bans can always be bad - imagine an operator who dislikes a user a=
nd
  decides to ban him so he doesn't need to talk to them any longer...
  I think this global banning issue is worth a separate discussion.
  Another idea - everyone can run their own blacklists. Servers can then ag=
ree
  on using any of them.
* About compromised channel servers: that's a good point. Another reason why
  we should make the user's server connect to the channel server instead of
  direct connections...
  We'll have to use very good network code in that case. I can think of some
  design but I'm not sure yet whether it'll be scalable enough. In the very
  worst case, it will become a little laggy with a huge lot of servers.


> How would you stop someone from stealing your channel when you no one is
> around if there are no services?
Channel servers could provide channel ownership and stuff. Same thing as wi=
th
the basic idea of Unity - channel servers don't need services since they can
do everything themselves.


>> [network mechanism]
> This could do with more explaination too.
Perhaps we'd better move this to the -code list, what do you think?


> I really like the idea of a regional index of users online however it wou=
ld
> need to take its info from some registration details (assuming people don=
't
> lie) or use the information from an IP block lookup but again that can be
> faked by people using a bouncer. Granted that with IPv6 it would be
> impossible (I think) to spoof/fake your OWN IP but you've still got n+1
> users on bouncers.
> Alot of this stuff still needs alot more explaination.
Sure, it can't be a true and all perfect regional index. It will just gathe=
r a
list of users on a bunch of domains that are supposed to belong to a specif=
ic
region. An index might, for example, get info about all domains that are
believed to reside in southern UK. If users want to cheat the index by using
bouncers and the like, they can. In the end, getting true information is
nearly impossible anyway.


> I know it looks like I've pulled this apart but it's what you asked to be
> done, also this way other people might better understand it :)
Sure thing. Waiting for more. :)

--=20
regards,                                 |     http://arc.pasp.de
Jan Kr=FCger                               | ()  ascii ribbon campaign
primary mail: jan.krueger@rwth-aachen.de | /\  - against html mail
http://www.jast.net.tc/                  |     - against microsoft attachme=
nts




From MAILER-DAEMON Sat Feb 22 17:15:43 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18mhvr-0001uF-00
	for mharc-unity-irc3@gnu.org; Sat, 22 Feb 2003 17:15:43 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18mhvp-0001t6-00
	for unity-irc3@nongnu.org; Sat, 22 Feb 2003 17:15:41 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18mhvn-0001sO-00
	for unity-irc3@nongnu.org; Sat, 22 Feb 2003 17:15:41 -0500
Received: from dwestley.demon.co.uk ([62.49.21.22] helo=fragalot.com)
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18mhvc-0001cF-00
	for unity-irc3@nongnu.org; Sat, 22 Feb 2003 17:15:28 -0500
Received: from biggeek ([10.0.0.3])
	by fragalot.com ([10.0.0.5])
	with SMTP (MDaemon.PRO.v6.0.7.R)
	for <unity-irc3@nongnu.org>; Sat, 22 Feb 2003 22:15:23 +0000
From: "David Westley" <dave@fragalot.com>
To: "irc3 \(Unity\) public discussion" <unity-irc3@nongnu.org>
Subject: RE: [Unity-irc3] Realistic review of drafts; revival of list
Date: Sat, 22 Feb 2003 22:15:22 -0000
Message-ID: <AIEGKGKEDNIIMGHFPGOOAENHDHAA.dave@fragalot.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Importance: Normal
In-Reply-To: <20030222161453.0aba991b.jan.krueger@rwth-aachen.de>
X-Authenticated-Sender: dave@fragalot.com
X-MDRemoteIP: 10.0.0.3
X-Return-Path: dave@fragalot.com
X-MDaemon-Deliver-To: unity-irc3@nongnu.org
X-BeenThere: unity-irc3@nongnu.org
X-Mailman-Version: 2.1b5
Precedence: list
Reply-To: dave@fragalot.com, "irc3 \(Unity\) public discussion"
	<unity-irc3@nongnu.org>
List-Id: irc3 (Unity) public discussion <unity-irc3.nongnu.org>
List-Help: <mailto:unity-irc3-request@nongnu.org?subject=help>
List-Post: <mailto:unity-irc3@nongnu.org>
List-Subscribe: <http://mail.nongnu.org/mailman/listinfo/unity-irc3>,
	<mailto:unity-irc3-request@nongnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/unity-irc3>
List-Unsubscribe: <http://mail.nongnu.org/mailman/listinfo/unity-irc3>,
	<mailto:unity-irc3-request@nongnu.org?subject=unsubscribe>
X-List-Received-Date: Sat, 22 Feb 2003 22:15:42 -0000

>
>
>Hi.
>Thanks for questions and stuff. Here goes reply.
and now for even more rebuttal :)
>
>
>> Most networks politics is about content and users not how channels are
>> run...that's a channel operators deal, also isn't nick/channel
>registration
>> a network politics area??
>Not any longer if we move channels out of the network. Users can now choose
>seperately between what kind of channels to use and what kind of network to
>use. What's best: if they get fed up with their server, they can just use
>another one and resume chatting with the same people.
>Obvious problem here: global network bans. We need to discuss those. Do we
>want them? If so, who'll be allowed to place one?
Let me see if I understand this...

uk.quakenet.org (a quakenet client server) <---> uk.undernet.org (an
undernet client server)
                                             |
                                             |
                           uk.channels.irc.net (uk channel server)

A user could be on uk.quakenet.org and join #channel_1 on
uk.channels.irc.net and another user could be on uk.undernet.org and also
join #channel_1 on uk.channels.irc.net and they would both be on the same
channel, however, if the user on uk.undernet.org didn't like the politics of
undernet or were banned from the UK undernet server they could move to
uk.quakenet.org and still be on the same channel yeah? That way each network
would have their own politics and rules about users etc.. but channels would
be on a non-politically controlled server? ...... If this is the case then
the channel servers would either have to have no controllers (operators)
which would mean anarchy OR decisions would have to be made by a kinda
committee so that political/religious views don't taint decisions. (I hate
politics!)

As to intra-network bans....I'd say that they would be a very very bad idea.
People would be stepping on other peoples toes and I can see major fights
breaking out!

>
>
>> This would need a client change would it not? Can you be sure that the
>> client coders would be willing to change their programs to
>support this, and
>> if so would it be possible for them to support both protocols
>with a single
>> codebase?
>We could support different client protocols. In fact, this would make it
>easier for people to switch anyway, so I'm all for it. We could even run
>proxy servers that proxy IRC clients into the network transparently.
>We'll have to design different protocols in that case - our own, an IRC2
>compatible and perhaps (AIM|ICQ|Jabber|MSN) compatible ones.
This point really needs to be thrashed out alot...maybe once we have a
protocol standard kinda sorted out it might be an idea to approach some of
the current client coders to see if A) they would be willing to change their
codebase and B) if it would be possible for them to support multiple
protocols easily.

>
>
>> Am I right in thinking that if you wanted people to connect to a channel
>> you've made on your own little channel server they'd need to
>connect to your
>> IP/hostname to be able to talk on that channel, there by making old local
>> channels available but NOT part of the general server software?
>Since people will be connecting to the channel server, channels
>will be local
>and global at the same time. Local - they reside on one server. Global -
>everyone can use them.
>In the case of proxies mentioned above, clients won't even notice
>that they're
>opening a separate connection to a channel since the proxy will do it for
>them.
>We could even make the main server software tunnel all channel
>traffic, but in
>that case we'd waste quite some additional FDs on the server.
Saying that a channel is local because it resides on a single server isn't
what I'd class as a local channel... local to me would be like the old irc2
local channels, you join it and it only exists on THAT server...so if
general users could run up their own channel server then you could have
#my_private_channel on my.private.channel.server.net but that would need
users to have either a reverse lookup (which not everyone will/can have) or
connect via IP.

on a side note, how does "/join #channel@some.channel.server.irc.net" grab
anyone as a way to join channels? and yes if you wanted you could get rid of
the # sign to make it look more like an email address ;)

>
>
>>> [channel politics]
>> See 1st comment
>I'm talking about what features channel operators get. I think that's a
>politic thing as well - some of the present networks offer
>registrations, some
>don't. Then there's Q and there's ChanServ. With the design I'm
>talking about
>right now, clients can decide what kind of channel they want on their own
>(provided there's a server that offers what they want).
So individual networks could run their own channel servers with
services/registrations of their choice and independent people could run
their own channel servers with their own features yeah?

>
>
>>> [domains, channel domains and stuff]
>> Could you expand on this a bit more as I'm not sure I understand
>this fully.
>> (Yeah I know I'm supposed to be one of the brainier ones but
>sometimes ideas
>> need to be explained a fair bit before people understand them :P)
>Sure.
>With the original Unity design, we had the ideas of domains. Every domain
>contains a bunch of servers, every domain has its channels, and so on.
>What is new now is that every domain contains one server only. This way, we
>don't need to do any bursts at all! No bursts, no lists of users and
>channels to be sync'd, no desyncs.
>This is much like with e-mails - a mail domain is handled by one MX server.
>Still you can easily contact people that reside on another server.
>Now we can have user domains and channel domains, thus we'd have
>two different
>kinds of servers, namely user servers and channel servers. User
>servers host
>users while channel servers host groups/channels. Staying with the
>example, a
>channel server could be compared with a mailing list server in the e-mail
>world.
>Of course, nobody says there can't be a mixed domain - we have those too in
>the e-mail world, i.e. a server that provides e-mail accounts for
>people and
>mailing lists at the same time. Nongnu.org is one of those servers.
Okay! So we could have DALNet with just client servers with its users using
someone elses channel servers and Quakenet with its own channel servers as
well as client servers yeah? (BTW mail domains can have multiple MX records
which have a priority number and are used in a fashion similar to DNS
round-robin so you could have 5 mail servers for a single domain) :)

>
>
>> I can hear the cries of IRC Operators..."I can't ban this fucker from the
>> network anymore!!!!!" Also how exactly would these channel
>servers validate
>> the identity of the users connecting to them without connecting
>to a client
>> server and requesting information from it, and if that is what
>it does then
>> how do you get around corrupt channel server operator or maybe a
>comprimised
>> channel server?
>* That's the only drawback of the design that I can think of right
>now - it's
>  more decentralised. Only thing we can do about global bans is
>setting up a
>  team of people who maintain a blacklist. Corruption alert though.
>  Global bans can always be bad - imagine an operator who dislikes
>a user and
>  decides to ban him so he doesn't need to talk to them any longer...
>  I think this global banning issue is worth a separate discussion.
>  Another idea - everyone can run their own blacklists. Servers
>can then agree
>  on using any of them.
I have an idea about this but it's very.....political! At the end of the day
this is more a network politics issue rather than a protocol design issue.

>* About compromised channel servers: that's a good point. Another
>reason why
>  we should make the user's server connect to the channel server instead of
>  direct connections...
>  We'll have to use very good network code in that case. I can
>think of some
>  design but I'm not sure yet whether it'll be scalable enough. In the very
>  worst case, it will become a little laggy with a huge lot of servers.
I agree...this is one aspect that will need an awful lot of discussion and
design work.

>
>
>> How would you stop someone from stealing your channel when you no one is
>> around if there are no services?
>Channel servers could provide channel ownership and stuff. Same
>thing as with
>the basic idea of Unity - channel servers don't need services
>since they can
>do everything themselves.
>
>
>>> [network mechanism]
>> This could do with more explaination too.
>Perhaps we'd better move this to the -code list, what do you think?
Yeah if you think it'd be better on that list.

>
>
>> I really like the idea of a regional index of users online
>however it would
>> need to take its info from some registration details (assuming
>people don't
>> lie) or use the information from an IP block lookup but again that can be
>> faked by people using a bouncer. Granted that with IPv6 it would be
>> impossible (I think) to spoof/fake your OWN IP but you've still got n+1
>> users on bouncers.
>> Alot of this stuff still needs alot more explanation.
>Sure, it can't be a true and all perfect regional index. It will
>just gather a
>list of users on a bunch of domains that are supposed to belong to
>a specific
>region. An index might, for example, get info about all domains that are
>believed to reside in southern UK. If users want to cheat the
>index by using
>bouncers and the like, they can. In the end, getting true information is
>nearly impossible anyway.
>
Personally if this regional index was to be of any use it would have to
contain true information otherwise it's about as useful as /whois and it
would just be a duplicate and waste don't you think unless I've got the
point of this regional index totally wrong? (which is entirely possible!)


Another long ass mail brought to you by your friendly neighbourhood Penguin
;)




From MAILER-DAEMON Mon Feb 24 18:49:09 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18nSLN-0004t6-00
	for mharc-unity-irc3@gnu.org; Mon, 24 Feb 2003 18:49:09 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18nSLL-0004rD-00
	for unity-irc3@nongnu.org; Mon, 24 Feb 2003 18:49:07 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18nSKp-0004AM-00
	for unity-irc3@nongnu.org; Mon, 24 Feb 2003 18:49:06 -0500
Received: from ms-2.rz.rwth-aachen.de ([134.130.3.131]
	helo=ms-dienst.rz.rwth-aachen.de)
	by monty-python.gnu.org with esmtp (Exim 4.10.13)	id 18nSKo-00046h-00
	for unity-irc3@nongnu.org; Mon, 24 Feb 2003 18:48:34 -0500
Received: from ms-1 (ms-1 [134.130.3.130]) by ms-dienst.rz.rwth-aachen.de
 (iPlanet Messaging Server 5.2 Patch 1 (built Aug 19 2002))
 with ESMTP id <0HAU0095G7AWOK@ms-dienst.rz.rwth-aachen.de> for
 unity-irc3@nongnu.org; Tue, 25 Feb 2003 00:44:56 +0100 (MET)
Received: from r220-1.rz.RWTH-Aachen.DE ([134.130.3.31])
	by ms-1 (MailMonitor for SMTP v1.2.2 ) ;
	Tue, 25 Feb 2003 00:44:56 +0100 (MET)
Received: from neuron (jast@p508D8F50.dip.t-dialin.net [80.141.143.80])
	h1ONijdJ015108	for
	<unity-irc3@nongnu.org>; Tue, 25 Feb 2003 00:44:45 +0100 (MET)
Date: Tue, 25 Feb 2003 00:45:16 +0100
From: Jan Krueger <jan.krueger@rwth-aachen.de>
Subject: Re: [Unity-irc3] Realistic review of drafts; revival of list
In-reply-to: <AIEGKGKEDNIIMGHFPGOOAENHDHAA.dave@fragalot.com>
To: "irc3 (Unity) public discussion" <unity-irc3@nongnu.org>
Message-id: <20030225004516.14f9ce39.jan.krueger@rwth-aachen.de>
MIME-version: 1.0
X-Mailer: Sylpheed version 0.8.10claws (GTK+ 1.2.10; i686-pc-linux-gnu)
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
References: <20030222161453.0aba991b.jan.krueger@rwth-aachen.de>
 <AIEGKGKEDNIIMGHFPGOOAENHDHAA.dave@fragalot.com>
X-BeenThere: unity-irc3@nongnu.org
X-Mailman-Version: 2.1b5
Precedence: list
Reply-To: "irc3 \(Unity\) public discussion" <unity-irc3@nongnu.org>
List-Id: irc3 (Unity) public discussion <unity-irc3.nongnu.org>
List-Help: <mailto:unity-irc3-request@nongnu.org?subject=help>
List-Post: <mailto:unity-irc3@nongnu.org>
List-Subscribe: <http://mail.nongnu.org/mailman/listinfo/unity-irc3>,
	<mailto:unity-irc3-request@nongnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/unity-irc3>
List-Unsubscribe: <http://mail.nongnu.org/mailman/listinfo/unity-irc3>,
	<mailto:unity-irc3-request@nongnu.org?subject=unsubscribe>
X-List-Received-Date: Mon, 24 Feb 2003 23:49:08 -0000

Hi again.

> however, if the user on uk.undernet.org didn't like the politics of
> undernet or were banned from the UK undernet server they could move to
> uk.quakenet.org and still be on the same channel yeah? That way each network
> would have their own politics and rules about users etc.. but channels would
> be on a non-politically controlled server? ...... If this is the case then
> the channel servers would either have to have no controllers (operators)
> which would mean anarchy OR decisions would have to be made by a kinda
> committee so that political/religious views don't taint decisions. (I hate
> politics!)
Precisely. Committee sounds good. However, in the end it's up to the people
who run a channel server. If they want dictatorship, they get it.
I'm trusting in the users here... since they can choose where to create their
channel, I hope they'll just abandon badly-managed and corrupt channel
servers, leaving them empty. Instant feedback style.


> As to intra-network bans....I'd say that they would be a very very bad idea.
> People would be stepping on other peoples toes and I can see major fights
> breaking out!
Since we only have one network, there is no 'intra network ban'. Here's
another idea: a bunch of client servers gather together and setup a blacklist
that's valid for all of the servers involved. They could then decide how to
handle this all.
Anyway, they commit their blacklist entries to a central server. That server
receives incoming entries and stores them, remembering which blacklist
committee set it. Servers in a BL (blacklist) committee will periodically
fetch the list to use it locally; they will only get their own entries though.
We could also make the central blacklist server place superglobal bans if
someone is blacklisted on a bunch of BL committees (if someone is banned from
several groups of server, that's a pretty obvious sign for that they're really
malicious, it could be a political issue otherwise).
Last but not least, a superglobal BL committee could place global bans, but I
guess that'll cause lots of fights, so let's not do this.


> This point really needs to be thrashed out alot...maybe once we have a
> protocol standard kinda sorted out it might be an idea to approach some of
> the current client coders to see if A) they would be willing to change their
> codebase and B) if it would be possible for them to support multiple
> protocols easily.
We can write our own client for a start, we could write client-sided proxies
for compatibility with old clients, and we can provide server-sided proxies,
which is absolutely desirable. People could keep using their old clients
without missing a single feature.
A customized client wouldn't be bad, of course. Next time I meet Khaled, I'll
ask him. ;o)


> Saying that a channel is local because it resides on a single server isn't
> what I'd class as a local channel... local to me would be like the old irc2
> local channels, you join it and it only exists on THAT server...so if
> general users could run up their own channel server then you could have
> #my_private_channel on my.private.channel.server.net but that would need
> users to have either a reverse lookup (which not everyone will/can have) or
> connect via IP.
True true. I don't think a reverse lookup is necessary however; a forward one
is enough for people to find the channel server.

> on a side note, how does "/join #channel@some.channel.server.irc.net" grab
> anyone as a way to join channels? and yes if you wanted you could get rid of
> the # sign to make it look more like an email address ;)
Well, we'll have to change something. It might not look pretty but still we
have to do something. Side note, the "/join" might get replaced by another
syntax in the new protocol (which doesn't say IRC2 compatibility will be
thrown away).


> So individual networks could run their own channel servers with
> services/registrations of their choice and independent people could run
> their own channel servers with their own features yeah?
I don't see why not. ;)
Advantages: users get a lot of choice and since everyone can easily add their
own server, there won't be staff fights about politics in terms of features
supplied by the channel server.


> Okay! So we could have DALNet with just client servers with its users using
> someone elses channel servers and Quakenet with its own channel servers as
> well as client servers yeah? (BTW mail domains can have multiple MX records
> which have a priority number and are used in a fashion similar to DNS
> round-robin so you could have 5 mail servers for a single domain) :)
Yes, and you might even have ChannelNet that only offers channels but no
client servers.
Round robins are something we could think about too. That
would bring back a bit of the old "multiple servers on one domain" feeling.
Sounds good.


> I have an idea about this but it's very.....political! At the end of the day
> this is more a network politics issue rather than a protocol design issue.
Whatever you can think of, let's discuss it. I'd really love some more threads
in this list. :)


> >  ... but I'm not sure yet whether it'll be scalable enough. In the very
> >  worst case, it will become a little laggy with a huge lot of servers.
> I agree...this is one aspect that will need an awful lot of discussion and
> design work.
Even though I said earlier that I want this on the -code list, I do now think
it's too much of a protocol question to move it away from here. I'll start a
new thread about it later.


> Personally if this regional index was to be of any use it would have to
> contain true information otherwise it's about as useful as /whois and it
> would just be a duplicate and waste don't you think unless I've got the
> point of this regional index totally wrong? (which is entirely possible!)
It's about as useful as /whois, that's right. However, with a syncless
network, we don't have a global /whois any longer - it's restricted to your
local server. Those regional indices would jump in and offer something alike.


That's it for now. By the way, I've added a new page to the website. Pheer.
\o\

regards,
jast




From MAILER-DAEMON Mon Feb 24 20:39:23 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18nU42-0002HP-00
	for mharc-unity-irc3@gnu.org; Mon, 24 Feb 2003 20:39:22 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18nU40-0002GV-00
	for unity-irc3@nongnu.org; Mon, 24 Feb 2003 20:39:20 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18nU3y-00029x-00
	for unity-irc3@nongnu.org; Mon, 24 Feb 2003 20:39:19 -0500
Received: from dwestley.demon.co.uk ([62.49.21.22] helo=fragalot.com)
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18nU3y-00023e-00
	for unity-irc3@nongnu.org; Mon, 24 Feb 2003 20:39:18 -0500
Received: from biggeek ([10.0.0.3])
	by fragalot.com ([10.0.0.5])
	with SMTP (MDaemon.PRO.v6.0.7.R)
	for <unity-irc3@nongnu.org>; Tue, 25 Feb 2003 01:39:16 +0000
From: "David Westley" <dave@fragalot.com>
To: "irc3 \(Unity\) public discussion" <unity-irc3@nongnu.org>
Subject: RE: [Unity-irc3] Realistic review of drafts; revival of list
Date: Tue, 25 Feb 2003 01:39:15 -0000
Message-ID: <AIEGKGKEDNIIMGHFPGOOOENODHAA.dave@fragalot.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Importance: Normal
In-Reply-To: <20030225004516.14f9ce39.jan.krueger@rwth-aachen.de>
X-Authenticated-Sender: dave@fragalot.com
X-MDRemoteIP: 10.0.0.3
X-Return-Path: dave@fragalot.com
X-MDaemon-Deliver-To: unity-irc3@nongnu.org
X-BeenThere: unity-irc3@nongnu.org
X-Mailman-Version: 2.1b5
Precedence: list
Reply-To: dave@fragalot.com, "irc3 \(Unity\) public discussion"
	<unity-irc3@nongnu.org>
List-Id: irc3 (Unity) public discussion <unity-irc3.nongnu.org>
List-Help: <mailto:unity-irc3-request@nongnu.org?subject=help>
List-Post: <mailto:unity-irc3@nongnu.org>
List-Subscribe: <http://mail.nongnu.org/mailman/listinfo/unity-irc3>,
	<mailto:unity-irc3-request@nongnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/unity-irc3>
List-Unsubscribe: <http://mail.nongnu.org/mailman/listinfo/unity-irc3>,
	<mailto:unity-irc3-request@nongnu.org?subject=unsubscribe>
X-List-Received-Date: Tue, 25 Feb 2003 01:39:21 -0000


<Excess stuff removed>

>That's it for now. By the way, I've added a new page to the website. Pheer.
>\o\
>
>regards,
>jast
>


Reading....Pheering....Digesting....Pingu will return!! :)





From MAILER-DAEMON Wed Feb 26 19:22:40 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18oBoZ-0000nW-00
	for mharc-unity-irc3@gnu.org; Wed, 26 Feb 2003 19:22:19 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18oBoS-0000bO-00
	for unity-irc3@nongnu.org; Wed, 26 Feb 2003 19:22:12 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18oBoF-0000MW-00
	for unity-irc3@nongnu.org; Wed, 26 Feb 2003 19:22:00 -0500
Received: from [62.21.241.225] (helo=lightning.digitalcraze.nl)
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18oBnS-0008HE-00
	for unity-irc3@nongnu.org; Wed, 26 Feb 2003 19:21:10 -0500
Received: from raz (chris.home.digitalcraze.nl [192.168.0.1])
	h1QJaW1M009559
	for <unity-irc3@nongnu.org>; Wed, 26 Feb 2003 20:36:32 +0100
Message-ID: <000201c2ddce$4fcb24f0$0100a8c0@raz>
From: "C.W.L. Hoogenboezem" <root@digitalcraze.nl>
To: <unity-irc3@nongnu.org>
Date: Wed, 26 Feb 2003 11:48:33 +0100
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0013_01C2DD8C.FD3034B0"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Subject: [Unity-irc3] Hail
X-BeenThere: unity-irc3@nongnu.org
X-Mailman-Version: 2.1b5
Precedence: list
Reply-To: "irc3 \(Unity\) public discussion" <unity-irc3@nongnu.org>
List-Id: irc3 (Unity) public discussion <unity-irc3.nongnu.org>
List-Help: <mailto:unity-irc3-request@nongnu.org?subject=help>
List-Post: <mailto:unity-irc3@nongnu.org>
List-Subscribe: <http://mail.nongnu.org/mailman/listinfo/unity-irc3>,
	<mailto:unity-irc3-request@nongnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/unity-irc3>
List-Unsubscribe: <http://mail.nongnu.org/mailman/listinfo/unity-irc3>,
	<mailto:unity-irc3-request@nongnu.org?subject=unsubscribe>
X-List-Received-Date: Thu, 27 Feb 2003 00:22:17 -0000

This is a multi-part message in MIME format.

------=_NextPart_000_0013_01C2DD8C.FD3034B0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Dear mistarz,

Sorry for my inactivity lately, I think a small explanation may be =
appropriate :)

I have been visiting some relatives in the United Kingdom, I guess you =
could say I've been back to my rootz :p
I aswell have been working and seXoring my back off, and in the =
meanwhile I even managed to write an anti-german essay! =
(http://crap.digitalcraze.nl - this doesnt apply to you, Janx0r)
So much for my inactivity. I'm planning to get fully involved in the =
next couple of days/weeks, so you can expect me to give my own input to =
the project soon. I'm reading all mails and I'm gonna put up a =
summarized version online as soon as possible, either for myself or for =
the rest of the people involved in irc3. I'll pass on the url as soon as =
I am finished.

As for my gline on Quakenet; froo emailed me yesterday:

"Hi Chris / raz

the vote regarding your ungline has just been posted, cross your fingers =
:)
i'll let you in on the results in 7 days (when the vote is over)"

Now this is major bullshit. My gline was there for a set three months, =
they have been passed for already one week now, and it's not yet =
removed. So if my vote returns a negative result, I'm going to fucking =
annoy these quackweb high-official-fucktards to oblivion, mark my words; =
I've been waiting for the gline to expire as a normal quakenet luser and =
now they're setting me up teh bomb, which I don't like. This might be =
food for my crap repository.

Laterz,

Chris


------=_NextPart_000_0013_01C2DD8C.FD3034B0
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=3D"text/html; charset=3Diso-8859-1" =
http-equiv=3DContent-Type>
<META content=3D"MSHTML 5.00.3502.5390" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DCourier size=3D2>Dear mistarz,</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DCourier size=3D2>Sorry for my inactivity lately, I =
think a small=20
explanation may be appropriate :)</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DCourier size=3D2>I have been visiting some relatives =
in the United=20
Kingdom, I guess you could say I've been back to my rootz =
:p</FONT></DIV>
<DIV><FONT size=3D2><FONT face=3DCourier>I aswell have been working and =
seXoring my=20
back off, and in the meanwhile I even managed to write an anti-german =
essay!=20
(</FONT><A href=3D"http://crap.digitalcraze.nl"><FONT=20
face=3DCourier>http://crap.digitalcraze.nl</FONT></A><FONT =
face=3DCourier>&nbsp;-=20
this doesnt apply to you, Janx0r)</FONT></FONT></DIV>
<DIV><FONT face=3DCourier size=3D2>So much for my inactivity. I'm =
planning to get=20
fully involved in the next couple of days/weeks, so you can expect me to =
give my=20
own input to the project soon. I'm reading all mails and I'm gonna put =
up a=20
summarized version online as soon as possible, either for myself or for =
the rest=20
of the people involved in irc3. I'll pass on the url as soon as I am=20
finished.</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DCourier size=3D2>As for my gline on Quakenet; froo =
emailed me=20
yesterday:</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DCourier size=3D2>"Hi Chris / raz<BR><BR>the vote =
regarding your=20
ungline has just been posted, cross your fingers :)<BR>i'll let you in =
on the=20
results in 7 days (when the vote is over)"</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DCourier size=3D2>Now this is major bullshit. My gline =
was there=20
for a <STRONG>set</STRONG> three months, they have been passed for =
already one=20
week now, and it's not yet removed. So if my vote returns a negative =
result, I'm=20
going to fucking annoy these quackweb high-official-fucktards to =
oblivion, mark=20
my words; I've been waiting for the gline to expire as a normal quakenet =
luser=20
and now they're setting me up teh bomb, which I don't like. This might =
be food=20
for my crap repository.</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DCourier size=3D2>Laterz,</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DCourier size=3D2>Chris<BR></FONT></DIV></BODY></HTML>

------=_NextPart_000_0013_01C2DD8C.FD3034B0--




From MAILER-DAEMON Wed Feb 26 19:22:54 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18oBp1-0001SO-00
	for mharc-unity-irc3@gnu.org; Wed, 26 Feb 2003 19:22:47 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18oBoj-00014Q-00
	for unity-irc3@nongnu.org; Wed, 26 Feb 2003 19:22:29 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18oBoY-0000mB-00
	for unity-irc3@nongnu.org; Wed, 26 Feb 2003 19:22:21 -0500
Received: from [62.21.241.225] (helo=lightning.digitalcraze.nl)
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 18oBnZ-0008HE-00
	for unity-irc3@nongnu.org; Wed, 26 Feb 2003 19:21:17 -0500
Received: from raz (chris.home.digitalcraze.nl [192.168.0.1])
	h1QJaW1Q009559
	for <unity-irc3@nongnu.org>; Wed, 26 Feb 2003 20:36:32 +0100
Message-ID: <000401c2ddce$4fd8e090$0100a8c0@raz>
From: "C.W.L. Hoogenboezem" <root@digitalcraze.nl>
To: <unity-irc3@nongnu.org>
Date: Wed, 26 Feb 2003 13:11:38 +0100
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0098_01C2DD98.98C574C0"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Subject: [Unity-irc3] My 2 cents
X-BeenThere: unity-irc3@nongnu.org
X-Mailman-Version: 2.1b5
Precedence: list
Reply-To: "irc3 \(Unity\) public discussion" <unity-irc3@nongnu.org>
List-Id: irc3 (Unity) public discussion <unity-irc3.nongnu.org>
List-Help: <mailto:unity-irc3-request@nongnu.org?subject=help>
List-Post: <mailto:unity-irc3@nongnu.org>
List-Subscribe: <http://mail.nongnu.org/mailman/listinfo/unity-irc3>,
	<mailto:unity-irc3-request@nongnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/unity-irc3>
List-Unsubscribe: <http://mail.nongnu.org/mailman/listinfo/unity-irc3>,
	<mailto:unity-irc3-request@nongnu.org?subject=unsubscribe>
X-List-Received-Date: Thu, 27 Feb 2003 00:22:39 -0000

This is a multi-part message in MIME format.

------=_NextPart_000_0098_01C2DD98.98C574C0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hay,

I have a couple of suggestions that may be useful for the project.

Exception masks for bans
_________________________________

Until now, most bans have been enforced with a specific target or =
specific targets ("*!*@193.114.10.*", or "*!*@*.quackweb.org"). Now =
imagine a lamer (or lamers) which is/are able to use a class c subnet =
minus one, thus able to use 253 different ip's. What if -one- cool guy =
who you -really- need in your channel is in that subnet? There was no =
way to let him in, unless you specifically ban 193.114.10.1, =
193.114.10.2, and so on, excluding the cool guy's ip. Most servers =
prohibit such excessive usage of banrecords, so this probably wouldn't =
be a useful option.

My idea about this is that we could implement some form of banexception, =
or even set a list of allowed users in the channel. I think we should =
work with two different tables then, one for the bans, and one for the =
exceptions. We might even work with regular expressions, but I don't =
think that's going to work out. Small overview:

+     Channel #quack @ Quackweb (the channel and network)
|
|_    Ban:     *!*@help.quakenet.org (we don't want no help lamerz)
|_    !Ban:    aegis!aegis@help.quakenet.org (we do want aegis. ..... .. =
.. .. .  .............. *slap_self*)

That would force all of the help.quakenet.org people to stay out, and =
allow aegis!aegis@help.quakenet.org to enter without any hassle. I think =
this would be a good addition in comparison to irc2.

Channelbans
_________________________________

The bans won't be very different in irc3, if you ask me. Regular =
nickname!ident@host.or.ip bans should be implemented. I don't know if =
the "?" character is valid in a banmask in irc2, if not, we could =
implement that into irc3... "*!bot1???@*".

Blacklistcommitee's
_________________________________

This would probably be a good idea, yeah. Almost every network =
consisting of 5 servers or more have commitee's for nearly everything. =
Trustcommitee's, webdevelopmentcommitee's, securitycommitee's, =
seXorcommitee's, it's all in the game nowadays. We should have some =
blacklist commitee that is able to do the following:

- Enforce serverbans to either specific sauth-servers or just prevent it =
from connecting to any server in the whole wide network

This is the only thing I could come up with, really. Placing =
superglobal, networkwide bans on users may result in massive argues and =
fights. This would aswell make the server admin's feel a bit downgraded, =
since there's someone they might not even know just banning people from =
his server. I think the enforcing of networkwide bans should be scrapped =
totally. I trust serveradmins to decide for themselves whether they want =
a user or not; thus leaving the decision at the serveradmin's side -- =
not some kind of higher authority. I think I share this point of view =
with Pingu.

ASN/BGP bans
_________________________________

Why not implement something like an ASN number global ban? Imagine a =
lamer having 500 usable ip's, all with different hostmasks. However, =
they are all belonging to the same ISP. Glining all his ip's/hostmasks =
would be a terrible job -- glining his ISP's ASN number would be pretty =
easy. Think about this thoroughly! Note that this would require some =
extra datatraffic... upon every connection attempt made, the hostmask/ip =
should be looked up in an ASN database.

Some other things
_________________________________

Well I guess these are my two cents for the moment... I really think we =
should put down down-to-earth summaries (or even RFC-like documents) to =
make some progress. We are going too indepth on certain things which =
could be done in a way later stage. I think we should focus on the core =
aspects of IRC first, like routing and such. Now my wishlist:

- Jast: would it be possible to archive the messages being posted in the =
irc3-* lists? Preferrably web-based, for later reference.
- *: Is uuuppzz now officially part of the irc3 project team?
- *: Is raphidae now officially part of the irc3 project team?

My own personal tasklist is to get into the creation of RFC papers. =
Since I'm a bad coder, it would be a good thing to make texta, I figured =
:p
I aswell am going to focus on making -summaries- of the discussions =
we've had on both mailinglists and irc, just to get things straight and =
clear. I made a subdomain (http://irc3.digitalcraze.nl) on which I will =
post these summaries. Please do comment/criticise these documents, I =
don't want to put up wrong stuff/not yet decided stuff!

Regards,

Chris Hoogenboezem
CSG OH - www.oudehoven.nl

------=_NextPart_000_0098_01C2DD98.98C574C0
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=3D"text/html; charset=3Diso-8859-1" =
http-equiv=3DContent-Type>
<META content=3D"MSHTML 5.00.3502.5390" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DCourier size=3D2>Hay,</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DCourier size=3D2>I have a couple of suggestions that =
may be useful=20
for the project.</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DCourier size=3D2>Exception masks for bans</FONT></DIV>
<DIV><FONT face=3DCourier =
size=3D2>_________________________________</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DCourier size=3D2>Until now, most bans have been =
enforced with a=20
specific target or specific targets ("*!*@193.114.10.*", or=20
"*!*@*.quackweb.org"). Now imagine a lamer (or lamers) which is/are able =
to use=20
a class c subnet minus one, thus able to use 253 different ip's. What if =
-one-=20
cool guy&nbsp;who you -really- need in your channel is in that subnet? =
There was=20
no way to let him in, unless you specifically ban 193.114.10.1, =
193.114.10.2,=20
and so on, excluding the cool guy's ip. Most servers prohibit such =
excessive=20
usage of banrecords, so this probably wouldn't be a useful =
option.</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DCourier size=3D2>My idea about this is that we could=20
implement&nbsp;some form of banexception, or even set a list of allowed =
users in=20
the channel. I think we should work with two different tables then, one =
for the=20
bans, and one for the exceptions. We might even work with regular =
expressions,=20
but I don't think that's going to work out. Small overview:</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DCourier size=3D2>+ &nbsp;&nbsp;&nbsp; Channel #quack @ =
Quackweb=20
(the channel and network)</FONT></DIV>
<DIV><FONT face=3DCourier size=3D2>|</FONT></DIV>
<DIV><FONT face=3DCourier size=3D2>|_&nbsp;&nbsp;&nbsp; Ban: =
&nbsp;&nbsp;&nbsp;=20
*!*@help.quakenet.org (we don't want no help lamerz)</FONT></DIV>
<DIV><FONT face=3DCourier size=3D2>|_&nbsp;&nbsp;&nbsp; =
!Ban:&nbsp;&nbsp;&nbsp;=20
aegis!<A =
href=3D"mailto:aegis@help.quakenet.org">aegis@help.quakenet.org</A> (we=20
do want aegis. ..... .. .. .. .&nbsp; .............. =
*slap_self*)</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DCourier size=3D2>That would force all of the =
help.quakenet.org=20
people to stay out, and allow aegis!<A=20
href=3D"mailto:aegis@help.quakenet.org">aegis@help.quakenet.org</A> to =
enter=20
without any hassle. I think this would be a good addition in comparison =
to=20
irc2.</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DCourier size=3D2>Channelbans</FONT></DIV>
<DIV><FONT face=3DCourier size=3D2><FONT face=3DCourier=20
size=3D2>_________________________________</FONT></FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DCourier size=3D2>The bans won't be very different in =
irc3, if you=20
ask me. Regular nickname!<A =
href=3D"mailto:ident@host.or.ip">ident@host.or.ip</A>=20
bans should be implemented. I don't know if the "?" character is valid =
in a=20
banmask in irc2, if not, we could implement that into irc3...=20
"*!bot1???@*".</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DCourier size=3D2>Blacklistcommitee's</FONT></DIV>
<DIV><FONT face=3DCourier size=3D2><FONT face=3DCourier=20
size=3D2>_________________________________</FONT></FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DCourier size=3D2>This would probably be a good idea, =
yeah. Almost=20
every network consisting of 5 servers or more have commitee's for nearly =

everything. Trustcommitee's, webdevelopmentcommitee's, =
securitycommitee's,=20
seXorcommitee's, it's all in the game nowadays. We should have some =
blacklist=20
commitee that is able to do the following:</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DCourier size=3D2>- Enforce serverbans to either =
specific=20
sauth-servers or just prevent it from connecting to any server in the =
whole wide=20
network</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DCourier size=3D2>This is the only thing I could come =
up with,=20
really. Placing superglobal, networkwide bans on users may result in =
massive=20
argues and fights. This would aswell make the server admin's feel a bit=20
downgraded, since there's someone they might not even know just banning =
people=20
from his server. I think the enforcing of networkwide bans should be =
scrapped=20
totally. I trust serveradmins&nbsp;to decide for themselves whether they =
want a=20
user or not; thus leaving the decision at the serveradmin's side -- not =
some=20
kind of higher authority. I think I share this point of view with=20
Pingu.</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DCourier size=3D2>ASN/BGP bans</FONT></DIV>
<DIV><FONT face=3DCourier size=3D2>
<DIV><FONT face=3DCourier size=3D2><FONT face=3DCourier=20
size=3D2>_________________________________</FONT></FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV>Why not implement something like an ASN number global ban? Imagine =
a lamer=20
having&nbsp;500 usable ip's, all with different hostmasks. However, they =
are all=20
belonging to the same ISP. Glining all his ip's/hostmasks would be a =
terrible=20
job -- glining his ISP's ASN number would be pretty easy. Think about =
this=20
thoroughly! Note that this would require some extra datatraffic... upon =
every=20
connection attempt made, the hostmask/ip should be looked up in an ASN=20
database.</DIV></FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DCourier size=3D2>Some other things</FONT></DIV>
<DIV><FONT face=3DCourier size=3D2><FONT face=3DCourier=20
size=3D2>_________________________________</FONT></FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DCourier size=3D2>Well I guess these are my two cents =
for the=20
moment... I really think we should put down down-to-earth summaries (or =
even=20
RFC-like documents) to make some progress. We are going too indepth on =
certain=20
things which could be done in a way later stage. I think we should focus =
on the=20
core aspects of IRC first, like routing and such. Now my =
wishlist:</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DCourier size=3D2>- Jast: would it be possible to =
archive the=20
messages being posted in the irc3-* lists? Preferrably web-based, for =
later=20
reference.</FONT></DIV>
<DIV><FONT face=3DCourier size=3D2>-&nbsp;*: Is uuuppzz now officially =
part of the=20
irc3 project team?</FONT></DIV>
<DIV><FONT face=3DCourier size=3D2>- *: Is raphidae now officially part =
of the irc3=20
project team?</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DCourier size=3D2>My own personal tasklist is to get =
into the=20
creation of RFC papers. Since I'm a bad coder, it would be a good thing =
to make=20
texta, I figured :p</FONT></DIV>
<DIV><FONT face=3DCourier size=3D2>I aswell am going to focus on making =
-summaries-=20
of the discussions we've had on both mailinglists and irc, just to get =
things=20
straight and clear. I made a subdomain (<A=20
href=3D"http://irc3.digitalcraze.nl">http://irc3.digitalcraze.nl</A>) on =
which I=20
will post these summaries. Please do comment/criticise these documents, =
I don't=20
want to put up wrong stuff/not yet decided stuff!</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DCourier size=3D2>Regards,</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DCourier size=3D2>Chris Hoogenboezem</FONT></DIV>
<DIV><FONT face=3DCourier size=3D2>CSG OH - <A=20
href=3D"http://www.oudehoven.nl">www.oudehoven.nl</A></FONT></DIV></BODY>=
</HTML>

------=_NextPart_000_0098_01C2DD98.98C574C0--




From MAILER-DAEMON Wed Feb 26 19:35:32 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18oC0m-0002zv-00
	for mharc-unity-irc3@gnu.org; Wed, 26 Feb 2003 19:34:56 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18oC0X-0002aJ-00
	for unity-irc3@nongnu.org; Wed, 26 Feb 2003 19:34:41 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18oC0Q-0002MK-00
	for unity-irc3@nongnu.org; Wed, 26 Feb 2003 19:34:38 -0500
Received: from ms-1.rz.rwth-aachen.de ([134.130.3.130]
	helo=ms-dienst.rz.rwth-aachen.de)
	by monty-python.gnu.org with esmtp (Exim 4.10.13)	id 18oBzp-0001l2-00
	for unity-irc3@nongnu.org; Wed, 26 Feb 2003 19:33:57 -0500
Received: from ms-2 (ms-2 [134.130.3.131]) by ms-dienst.rz.rwth-aachen.de
 (iPlanet Messaging Server 5.2 Patch 1 (built Aug 19 2002))
 with ESMTP id <0HAX0039EYWGQ1@ms-dienst.rz.rwth-aachen.de> for
 unity-irc3@nongnu.org; Thu, 27 Feb 2003 01:33:53 +0100 (MET)
Received: from r220-1.rz.RWTH-Aachen.DE ([134.130.3.31])
	by ms-2 (MailMonitor for SMTP v1.2.2 ) ;
	Thu, 27 Feb 2003 01:33:52 +0100 (MET)
Received: from neuron (jast@p508DB6D2.dip.t-dialin.net [80.141.182.210])
	h1R0XfOp027156	for
	<unity-irc3@nongnu.org>; Thu, 27 Feb 2003 01:33:41 +0100 (MET)
Date: Thu, 27 Feb 2003 01:34:10 +0100
From: Jan Krueger <jan.krueger@rwth-aachen.de>
Subject: Re: [Unity-irc3] Hail
In-reply-to: <000201c2ddce$4fcb24f0$0100a8c0@raz>
To: "irc3 (Unity) public discussion" <unity-irc3@nongnu.org>
Message-id: <20030227013410.1d8da724.jan.krueger@rwth-aachen.de>
MIME-version: 1.0
X-Mailer: Sylpheed version 0.8.10claws (GTK+ 1.2.10; i686-pc-linux-gnu)
Content-type: text/plain; charset=ISO-8859-1
Content-transfer-encoding: quoted-printable
References: <000201c2ddce$4fcb24f0$0100a8c0@raz>
X-BeenThere: unity-irc3@nongnu.org
X-Mailman-Version: 2.1b5
Precedence: list
Reply-To: "irc3 \(Unity\) public discussion" <unity-irc3@nongnu.org>
List-Id: irc3 (Unity) public discussion <unity-irc3.nongnu.org>
List-Help: <mailto:unity-irc3-request@nongnu.org?subject=help>
List-Post: <mailto:unity-irc3@nongnu.org>
List-Subscribe: <http://mail.nongnu.org/mailman/listinfo/unity-irc3>,
	<mailto:unity-irc3-request@nongnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/unity-irc3>
List-Unsubscribe: <http://mail.nongnu.org/mailman/listinfo/unity-irc3>,
	<mailto:unity-irc3-request@nongnu.org?subject=unsubscribe>
X-List-Received-Date: Thu, 27 Feb 2003 00:34:54 -0000

Hi,

> (http://crap.digitalcraze.nl - this doesnt apply to you, Janx0r)
Anyway, I'll be delighted to see it once it gets online. ;)


> my inactivity. I'm planning to get fully involved in the next couple of
> days/weeks, so you can expect me to give my own input to the project soon.
> I'm reading all mails and I'm gonna put up a summarized version online as
> soon as possible, either for myself or for the rest of the people involved
> in irc3. I'll pass on the url as soon as I am finished.
Hay, we have a central homepage with HTML CVS space, why not put everything
there? :)
By the way, I've started summarizing, it's on the website already.

--=20
regards,
Jan Kr=FCger
http://www.jast-dev.net.tc




From MAILER-DAEMON Wed Feb 26 19:49:19 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18oCDF-0007oh-00
	for mharc-unity-irc3@gnu.org; Wed, 26 Feb 2003 19:47:49 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18oCCe-0006vq-00
	for unity-irc3@nongnu.org; Wed, 26 Feb 2003 19:47:12 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18oCBR-000627-00
	for unity-irc3@nongnu.org; Wed, 26 Feb 2003 19:45:58 -0500
Received: from ms-1.rz.rwth-aachen.de ([134.130.3.130]
	helo=ms-dienst.rz.rwth-aachen.de)
	by monty-python.gnu.org with esmtp (Exim 4.10.13)	id 18oCB5-0005sJ-00
	for unity-irc3@nongnu.org; Wed, 26 Feb 2003 19:45:36 -0500
Received: from ms-2 (ms-2 [134.130.3.131]) by ms-dienst.rz.rwth-aachen.de
 (iPlanet Messaging Server 5.2 Patch 1 (built Aug 19 2002))
 with ESMTP id <0HAX003WAZFTQ1@ms-dienst.rz.rwth-aachen.de> for
 unity-irc3@nongnu.org; Thu, 27 Feb 2003 01:45:29 +0100 (MET)
Received: from r220-1.rz.RWTH-Aachen.DE ([134.130.3.31])
	by ms-2 (MailMonitor for SMTP v1.2.2 ) ;
	Thu, 27 Feb 2003 01:45:29 +0100 (MET)
Received: from neuron (jast@p508DB6D2.dip.t-dialin.net [80.141.182.210])
	h1R0jIOp028106	for
	<unity-irc3@nongnu.org>; Thu, 27 Feb 2003 01:45:18 +0100 (MET)
Date: Thu, 27 Feb 2003 01:45:49 +0100
From: Jan Krueger <jan.krueger@rwth-aachen.de>
Subject: Re: [Unity-irc3] My 2 cents
In-reply-to: <000401c2ddce$4fd8e090$0100a8c0@raz>
To: "irc3 (Unity) public discussion" <unity-irc3@nongnu.org>
Message-id: <20030227014549.1c596e14.jan.krueger@rwth-aachen.de>
MIME-version: 1.0
X-Mailer: Sylpheed version 0.8.10claws (GTK+ 1.2.10; i686-pc-linux-gnu)
Content-type: text/plain; charset=ISO-8859-1
Content-transfer-encoding: quoted-printable
References: <000401c2ddce$4fd8e090$0100a8c0@raz>
X-BeenThere: unity-irc3@nongnu.org
X-Mailman-Version: 2.1b5
Precedence: list
Reply-To: "irc3 \(Unity\) public discussion" <unity-irc3@nongnu.org>
List-Id: irc3 (Unity) public discussion <unity-irc3.nongnu.org>
List-Help: <mailto:unity-irc3-request@nongnu.org?subject=help>
List-Post: <mailto:unity-irc3@nongnu.org>
List-Subscribe: <http://mail.nongnu.org/mailman/listinfo/unity-irc3>,
	<mailto:unity-irc3-request@nongnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/unity-irc3>
List-Unsubscribe: <http://mail.nongnu.org/mailman/listinfo/unity-irc3>,
	<mailto:unity-irc3-request@nongnu.org?subject=unsubscribe>
X-List-Received-Date: Thu, 27 Feb 2003 00:47:40 -0000

Evening.

> Exception masks for bans
Well known concept, supported by lots of ircds already. :P
Anyway, useful for sure, I agree on that. Rises another interesting questio=
ns
by the way, I'll start another thread for that.

> |_    Ban:     *!*@help.quakenet.org (we don't want no help lamerz)
Heh, easy. We're trying to be serious here. ;)


> The bans won't be very different in irc3, if you ask me. Regular
> nickname!ident@host.or.ip bans should be implemented. I don't know if the
> "?" character is valid in a banmask in irc2, if not, we could implement t=
hat
> into irc3... "*!bot1???@*".
"?" is in irc2, yeah. Agree on the rest, though we might want to put in some
partial cloaking of hosts to prevent DoS on users. See thread I'm going to
open.


> I trust
> serveradmins to decide for themselves whether they want a user or not; th=
us
> leaving the decision at the serveradmin's side -- not some kind of higher
> authority. I think I share this point of view with Pingu.
Sure. There's one problem though - imagine some flooder who takes turns in
getting banned from all individual servers. Until he catches teh-kill
somewhere, he can go on spamming people every time. That's why I made the
suggestion of global bans that only get active when a certain amount of
servers have someone banned.
Anyway, let's open another thread for this as well.


> Why not implement something like an ASN number global ban? Imagine a lamer
> having 500 usable ip's, all with different hostmasks. However, they are a=
ll
> belonging to the same ISP. Glining all his ip's/hostmasks would be a
> terrible job -- glining his ISP's ASN number would be pretty easy. Think
> about this thoroughly! Note that this would require some extra
> datatraffic... upon every connection attempt made, the hostmask/ip should=
 be
> looked up in an ASN database.
We could make the software cache bits of the ASN database.
Another thought - most ISPs only have a small amount of IP subnets. For
example, German Telekom has some 217.* and some 80.* IP addresses for their
customers. Wouldn't IP subnet bans be enough for a start?


> Well I guess these are my two cents for the moment... I really think we
> should put down down-to-earth summaries (or even RFC-like documents) to m=
ake
> some progress. We are going too indepth on certain things which could be
> done in a way later stage. I think we should focus on the core aspects of
> IRC first, like routing and such.
Absolutely. I'm trying to write something user-friendly about what we're all
doing, see website. And that in-depth thing is something I've been saying a=
ll
the time - let's keep everything that's not directly related to the protocol
out for now (except for perhaps discussing whether things are technically
possible/sensible).


> - Jast: would it be possible to archive the messages being posted in the
> irc3-* lists? Preferrably web-based, for later reference.
Check the website. ;)

> - *: Is uuuppzz now officially part of the irc3 project team?
> - *: Is raphidae now officially part of the irc3 project team?
No. No. Official members are listed on our savannah project page.


> My own personal tasklist is to get into the creation of RFC papers. Since
> I'm a bad coder, it would be a good thing to make texta, I figured :p I
> aswell am going to focus on making -summaries- of the discussions we've h=
ad
> on both mailinglists and irc, just to get things straight and clear. I ma=
de
> a subdomain (http://irc3.digitalcraze.nl) on which I will post these
> summaries. Please do comment/criticise these documents, I don't want to p=
ut
> up wrong stuff/not yet decided stuff!
I think it's better to use our website's CVS. Let's keep everything in one
place. If you want, create your own directory and put your stuff in it, or
something.

--=20
regards,
Jan Kr=FCger
http://www.jast-dev.net.tc




