]> jfr.im git - irc.git/blob - software/RELEASES/ircservices/achurch.org/services/lists/ircservices/2002/003072.html
rename -> *.git
[irc.git] / software / RELEASES / ircservices / achurch.org / services / lists / ircservices / 2002 / 003072.html
1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
2 <HTML>
3 <HEAD>
4 <TITLE> [IRCServices] Is there a timeline in the future for supporting ircd2.9 or greater
5 </TITLE>
6 <LINK REL="Index" HREF="index.html" >
7 <LINK REL="made" HREF="mailto:ircservices%40ircservices.za.net?Subject=%5BIRCServices%5D%20Is%20there%20a%20timeline%20in%20the%20future%20for%20supporting%20ircd2.9%20or%20greater&In-Reply-To=3d624220.15460%40achurch.org">
8 <META NAME="robots" CONTENT="index,nofollow">
9 <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
10 <LINK REL="Previous" HREF="003071.html">
11 <LINK REL="Next" HREF="003075.html">
12 </HEAD>
13 <BODY BGCOLOR="#ffffff">
14 <H1>[IRCServices] Is there a timeline in the future for supporting ircd2.9 or greater</H1>
15 <B>Trevor Talbot</B>
16 <A HREF="mailto:ircservices%40ircservices.za.net?Subject=%5BIRCServices%5D%20Is%20there%20a%20timeline%20in%20the%20future%20for%20supporting%20ircd2.9%20or%20greater&In-Reply-To=3d624220.15460%40achurch.org"
17 TITLE="[IRCServices] Is there a timeline in the future for supporting ircd2.9 or greater">quension at softhome.net
18 </A><BR>
19 <I>Tue Aug 20 16:42:00 PDT 2002</I>
20 <P><UL>
21 <LI>Previous message: <A HREF="003071.html">[IRCServices] Is there a timeline in the future for supporting ircd2.9 or greater
22 </A></li>
23 <LI>Next message: <A HREF="003075.html">[IRCServices] hum
24 </A></li>
25 <LI> <B>Messages sorted by:</B>
26 <a href="date.html#3072">[ date ]</a>
27 <a href="thread.html#3072">[ thread ]</a>
28 <a href="subject.html#3072">[ subject ]</a>
29 <a href="author.html#3072">[ author ]</a>
30 </LI>
31 </UL>
32 <HR>
33 <!--beginarticle-->
34 <PRE>On Tuesday, August 20, 2002, at 06:16 AM, Andrew Church wrote:
35
36 &gt;&gt;&gt;<i> The WHY still remains the same, IETF-RFC should be the standard.
37 </I>&gt;&gt;<i>
38 </I>&gt;&gt;<i> Guess who wrote those RFCs? IRCnet. Guess who pays attention to
39 </I>&gt;&gt;<i> them? no one.
40 </I>&gt;<i>
41 </I>&gt;<i> Oh, was the message referring to the new RFCs? I don't
42 </I>&gt;<i> consider them
43 </I>&gt;<i> &quot;standards&quot; documents, though I have to admit it's nice they
44 </I>&gt;<i> took the time
45 </I>&gt;<i> to actually document their modifications, unlike most other
46 </I>&gt;<i> implementors.
47 </I>&gt;<i> (For those who were unaware, RFC1459, the original IRC
48 </I>&gt;<i> specification, is
49 </I>&gt;<i> classed as an &quot;experimental&quot; protocol, so using the word &quot;standard&quot; to
50 </I>&gt;<i> refer to it is incorrect, but I think it's beyond question that
51 </I>&gt;<i> RFC1459 is
52 </I>&gt;<i> more &quot;standard&quot; than the implementation of the day.)
53 </I>
54 RFCs 2810 - 2813 are merely &quot;informational&quot;, though they update RFC1459.
55
56 There was an attempt to hash out a standard for &quot;IRC 3&quot;, but that didn't
57 get very far. Unfortunately, IRC has no standard...
58
59 -- Quension
60
61
62 </PRE>
63
64 <!--endarticle-->
65 <HR>
66 <P><UL>
67 <!--threads-->
68 <LI>Previous message: <A HREF="003071.html">[IRCServices] Is there a timeline in the future for supporting ircd2.9 or greater
69 </A></li>
70 <LI>Next message: <A HREF="003075.html">[IRCServices] hum
71 </A></li>
72 <LI> <B>Messages sorted by:</B>
73 <a href="date.html#3072">[ date ]</a>
74 <a href="thread.html#3072">[ thread ]</a>
75 <a href="subject.html#3072">[ subject ]</a>
76 <a href="author.html#3072">[ author ]</a>
77 </LI>
78 </UL>
79
80 </body></html>