Re: irc: [was: New URN suggestion ]
Harald.T.Alvestrand@uninett.no Mon, 19 August 1996 08:30 UTC
Received: from ietf.org by ietf.org id aa28622; 19 Aug 96 4:30 EDT
Received: from cnri by ietf.org id aa28618; 19 Aug 96 4:30 EDT
Received: from services.Bunyip.COM by CNRI.Reston.VA.US id aa03482;
19 Aug 96 4:30 EDT
Received: (from daemon@localhost) by services.bunyip.com (8.6.10/8.6.9) id
EAA18254 for uri-out; Mon, 19 Aug 1996 04:12:26 -0400
Received: from mocha.bunyip.com (mocha.Bunyip.Com [192.197.208.1]) by
services.bunyip.com (8.6.10/8.6.9) with SMTP id EAA18228 for
<uri@services.bunyip.com>; Mon, 19 Aug 1996 04:11:49 -0400
Sender: ietf-archive-request@ietf.org
From: Harald.T.Alvestrand@uninett.no
Received: from domen.uninett.no by mocha.bunyip.com with SMTP
(5.65a/IDA-1.4.2b/CC-Guru-2b)
id AA03435 (mail destined for uri@services.bunyip.com);
Mon, 19 Aug 96 04:11:49 -0400
Received: from domen.uninett.no by domen.uninett.no with SMTP (PP)
id <09493-0@domen.uninett.no>; Mon, 19 Aug 1996 10:11:30 +0200
X-Mailer: exmh version 1.6.7 5/3/96
To: Mandar Mirashi <mandar@kiowa.wildstar.net>
Cc: Larry Masinter <masinter@parc.xerox.com>, connolly@w3.org,
uri@bunyip.com, PICS-ask@w3.org
Subject: Re: irc: [was: New URN suggestion ]
In-Reply-To: Your message of "Mon, 19 Aug 1996 00:18:48 CDT."
<Pine.LNX.3.93.960819000735.13319A-100000@kiowa.wildstar.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Mon, 19 Aug 1996 10:11:23 +0200
Message-Id: <9488.840442283@domen.uninett.no>
X-Orig-Sender: owner-uri@bunyip.com
Precedence: bulk
Mandar, the document looks nice. You might want to check out http://www.apps.ietf.org/apps/url-schemes.html for questions I will want to raise about it once you ask the IESG to consider it for Proposed Standard. (By fiat of the Applications ADs, new URL schemes must be standards-track documents.) My comments so far: <port> (optional) The port number to connect to. If :<port> is omitted, the port defaults to 6667. This may change in the future to default to the IANA assigned IRC port 194, as it gains widespread use amongst IRC servers. This won't work. You MAY get away with "connect to 194, if it fails, you may try connecting to 6667", but this language changes the meaning of an URL over time, and that simply doesn't work at ALL. Questions based on my knowledge of IRC: - Do you have any thought of naming NETWORKS rather than servers? It would be distasteful to me to experience the pain of connecting to us.undernet.org when the network distance to no.undernet.org is close to zero (slowest speed link is 2 Mbit/sec, and lightly loaded). Of course, names are a pain to match up.... - Do you have any thought of controlling in the URL any other parameter of the session than the channel name to join? - Do you see any advantage to having an URL for IRC nicknames? Have fun! Harald A
- Re: irc: [was: New URN suggestion ] Mandar Mirashi
- Re: irc: [was: New URN suggestion ] Harald.T.Alvestrand