Re: [apps-discuss] [Technical Errata Reported] RFC1459 (3938)
t.petch <ietfc@btconnect.com> Fri, 20 June 2014 13:43 UTC
Return-Path: <ietfc@btconnect.com>
X-Original-To: apps-discuss@ietfa.amsl.com
Delivered-To: apps-discuss@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EA70D1A039C for <apps-discuss@ietfa.amsl.com>; Fri, 20 Jun 2014 06:43:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level:
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mlva4StVqqTp for <apps-discuss@ietfa.amsl.com>; Fri, 20 Jun 2014 06:43:03 -0700 (PDT)
Received: from emea01-am1-obe.outbound.protection.outlook.com (mail-am1lp0015.outbound.protection.outlook.com [213.199.154.15]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1E4CE1A039A for <apps-discuss@ietf.org>; Fri, 20 Jun 2014 06:43:03 -0700 (PDT)
Received: from AMXPRD0310HT004.eurprd03.prod.outlook.com (157.56.248.133) by AMXPR07MB055.eurprd07.prod.outlook.com (10.242.67.149) with Microsoft SMTP Server (TLS) id 15.0.969.15; Fri, 20 Jun 2014 13:43:01 +0000
Message-ID: <043201cf8c8d$194d2fc0$4001a8c0@gateway.2wire.net>
From: "t.petch" <ietfc@btconnect.com>
To: Barry Leiba <barryleiba@computer.org>, Apps Discuss <apps-discuss@ietf.org>
References: <20140328105940.ADCCF7FC2CB@rfc-editor.org> <CALaySJLvh9iuYYCkzDgPD7hTW+sZTSd6XvcrJgkCu=cDM7pFzg@mail.gmail.com>
Date: Fri, 20 Jun 2014 14:32:14 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
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
X-Originating-IP: [157.56.248.133]
X-ClientProxiedBy: AMSPR07CA010.eurprd07.prod.outlook.com (10.242.77.178) To AMXPR07MB055.eurprd07.prod.outlook.com (10.242.67.149)
X-Microsoft-Antispam: BCL:0;PCL:0;RULEID:
X-Forefront-PRVS: 024847EE92
X-Forefront-Antispam-Report: SFV:NSPM; SFS:(6009001)(428001)(189002)(199002)(51704005)(24454002)(13464003)(377454003)(51444003)(33646001)(79102001)(77982001)(62236002)(44716002)(15188155005)(19580405001)(84392001)(31966008)(16799955002)(87286001)(104166001)(102836001)(15975445006)(87976001)(64706001)(89996001)(81342001)(76482001)(77156001)(88136002)(81542001)(92566001)(93916002)(92726001)(86362001)(15202345003)(80022001)(50226001)(85852003)(46102001)(83072002)(66066001)(20776003)(47776003)(50466002)(83322001)(19580395003)(99396002)(106356001)(105586002)(23756003)(81686999)(14496001)(76176999)(50986999)(81816999)(101416001)(4396001)(551544002)(77096002)(21056001)(44736004)(74662001)(74502001)(85306003)(62966002)(95666004)(42186005)(61296003)(74416001)(7726001); DIR:OUT; SFP:; SCL:1; SRVR:AMXPR07MB055; H:AMXPRD0310HT004.eurprd03.prod.outlook.com; FPR:; MLV:sfv; PTR:InfoNoRecords; MX:1; A:0; LANG:en;
Received-SPF: None (: btconnect.com does not designate permitted sender hosts)
Authentication-Results: spf=none (sender IP is ) smtp.mailfrom=ietfc@btconnect.com;
X-OriginatorOrg: btconnect.com
Archived-At: http://mailarchive.ietf.org/arch/msg/apps-discuss/TqkSZeMRL1tpJUl7QZvcWMLR_E8
Cc: Myunggyun Jonathan Aldo Seo <tki@tki.so>
Subject: Re: [apps-discuss] [Technical Errata Reported] RFC1459 (3938)
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss/>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 20 Jun 2014 13:43:11 -0000
Barry RFC1459 s4.2.3.1 is updated by RFC2812 s3.2.3 and, in part, by RFC2811 s4. Comparing those two last with RFC1459, I think it clear that a page has been missed, giving the Numeric Replies and Examples. The equivalent to the truncated sentence, "When using the 'o' and 'b' options, a restriction on a total of three per mode command has been imposed. That is, any combination of 'o' and" is now " Note that there is a maximum limit of three (3) changes per command for modes that take a parameter." I think that the erratum should point out that RFC1459 has been updated - Obsoleted I would call it - and that a comprehensive description can be found in the RFC281x. Trying to reconstruct the missing page seems unproductive. I am curious whether or not the raiser of this was aware of the later RFC, which seem to me to resolve any issues. Tom Petch ----- Original Message ----- From: "Barry Leiba" <barryleiba@computer.org> To: "Apps Discuss" <apps-discuss@ietf.org> Cc: "Myunggyun Jonathan Aldo Seo" <tki@tki.so> Sent: Wednesday, April 16, 2014 4:56 PM > Myunggyun Jonathan Aldo Seo has reported the errata below, on RFC > 1459, the IRC protocol. He's correct that the last paragraph of > Section 4.2.3.1 has clearly been truncated. But, as this is a > more-than-20-year-old document, it's likely hard to know what the text > was intended to say. > > Here's Section 4.2.3.1 in its entirety: > > ------------------------------------- > 4.2.3.1 Channel modes > > Parameters: <channel> {[+|-]|o|p|s|i|t|n|b|v} [<limit>] [<user>] > [<ban mask>] > > The MODE command is provided so that channel operators may change the > characteristics of `their' channel. It is also required that servers > be able to change channel modes so that channel operators may be > created. > > The various modes available for channels are as follows: > > o - give/take channel operator privileges; > p - private channel flag; > s - secret channel flag; > i - invite-only channel flag; > t - topic settable by channel operator only flag; > n - no messages to channel from clients on the outside; > m - moderated channel; > l - set the user limit to channel; > b - set a ban mask to keep users out; > v - give/take the ability to speak on a moderated channel; > k - set a channel key (password). > > When using the 'o' and 'b' options, a restriction on a total of three > per mode command has been imposed. That is, any combination of 'o' > and > ------------------------------------- > > I would like to mark the errata report as Verified, but it would be > nice to be able to suggest correct text in the report. Can anyone > help figure out what was supposed to be there? If not, I'll likely > mark it "Held For Document Update" instead. > > Barry > > On Fri, Mar 28, 2014 at 6:59 AM, RFC Errata System > <rfc-editor@rfc-editor.org> wrote: > > The following errata report has been submitted for RFC1459, > > "Internet Relay Chat Protocol". > > > > -------------------------------------- > > You may review the report below and at: > > http://www.rfc-editor.org/errata_search.php?rfc=1459&eid=3938 > > > > -------------------------------------- > > Type: Technical > > Reported by: Myunggyun Jonathan Aldo Seo <tki@tki.so> > > > > Section: 4.2.3.1 > > > > Original Text > > ------------- > > When using the 'o' and 'b' options, a restriction on a total of three > > per mode command has been imposed. That is, any combination of 'o' > > and > > > > Corrected Text > > -------------- > > > > > > Notes > > ----- > > The sentence lacks the last part and does not explain what it expected to. > > > > Instructions: > > ------------- > > This errata is currently posted as "Reported". If necessary, please > > use "Reply All" to discuss whether it should be verified or > > rejected. When a decision is reached, the verifying party (IESG) > > can log in to change the status and edit the report, if necessary. > > > > -------------------------------------- > > RFC1459 (no draft string recorded) > > -------------------------------------- > > Title : Internet Relay Chat Protocol > > Publication Date : May 1993 > > Author(s) : J. Oikarinen, D. Reed > > Category : EXPERIMENTAL > > Source : Legacy > > Area : Legacy > > Stream : IETF > > Verifying Party : IESG > > > > _______________________________________________ > apps-discuss mailing list > apps-discuss@ietf.org > https://www.ietf.org/mailman/listinfo/apps-discuss