Re: [apps-discuss] [Technical Errata Reported] RFC1459 (3938)
Dave Thaler <dthaler@microsoft.com> Wed, 16 April 2014 16:53 UTC
Return-Path: <dthaler@microsoft.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 C15681A023D for <apps-discuss@ietfa.amsl.com>; Wed, 16 Apr 2014 09:53:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.902
X-Spam-Level:
X-Spam-Status: No, score=-101.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] 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 zCdRH8IlH3qn for <apps-discuss@ietfa.amsl.com>; Wed, 16 Apr 2014 09:53:21 -0700 (PDT)
Received: from na01-bn1-obe.outbound.protection.outlook.com (mail-bn1lp0145.outbound.protection.outlook.com [207.46.163.145]) by ietfa.amsl.com (Postfix) with ESMTP id 856451A025A for <apps-discuss@ietf.org>; Wed, 16 Apr 2014 09:53:21 -0700 (PDT)
Received: from BY2PR03MB412.namprd03.prod.outlook.com (10.141.141.25) by BY2PR03MB411.namprd03.prod.outlook.com (10.141.141.22) with Microsoft SMTP Server (TLS) id 15.0.918.8; Wed, 16 Apr 2014 16:53:17 +0000
Received: from BY2PR03MB412.namprd03.prod.outlook.com ([10.141.141.25]) by BY2PR03MB412.namprd03.prod.outlook.com ([10.141.141.25]) with mapi id 15.00.0918.000; Wed, 16 Apr 2014 16:53:16 +0000
From: Dave Thaler <dthaler@microsoft.com>
To: Barry Leiba <barryleiba@computer.org>, Apps Discuss <apps-discuss@ietf.org>
Thread-Topic: [apps-discuss] [Technical Errata Reported] RFC1459 (3938)
Thread-Index: AQHPWYx4AbyHkJrmUUmL6CfObdfh4psUdHNg
Date: Wed, 16 Apr 2014 16:53:15 +0000
Message-ID: <b5d4dde241a84c5fb5a042b634e4a28b@BY2PR03MB412.namprd03.prod.outlook.com>
References: <20140328105940.ADCCF7FC2CB@rfc-editor.org> <CALaySJLvh9iuYYCkzDgPD7hTW+sZTSd6XvcrJgkCu=cDM7pFzg@mail.gmail.com>
In-Reply-To: <CALaySJLvh9iuYYCkzDgPD7hTW+sZTSd6XvcrJgkCu=cDM7pFzg@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [50.135.4.20]
x-forefront-prvs: 01834E39B7
x-forefront-antispam-report: SFV:NSPM; SFS:(10009001)(6009001)(428001)(189002)(199002)(13464003)(24454002)(377454003)(51704005)(46102001)(4396001)(50986999)(87936001)(2656002)(76576001)(31966008)(74502001)(99396002)(99286001)(76176999)(77096999)(54356999)(77982001)(81342001)(79102001)(81542001)(74316001)(33646001)(74662001)(85852003)(16799955002)(15202345003)(86362001)(83072002)(92566001)(19580405001)(83322001)(19580395003)(551544002)(15188155005)(76482001)(80022001)(66066001)(86612001)(20776003)(80976001)(15975445006)(24736002); DIR:OUT; SFP:1101; SCL:1; SRVR:BY2PR03MB411; H:BY2PR03MB412.namprd03.prod.outlook.com; FPR:EE6FF17E.AFE2D2E0.B9C33EBB.CAE5AD6F.20443; MLV:sfv; PTR:InfoNoRecords; MX:1; A:1; LANG:en;
received-spf: None (: microsoft.com does not designate permitted sender hosts)
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: microsoft.onmicrosoft.com
Archived-At: http://mailarchive.ietf.org/arch/msg/apps-discuss/lU02mYSwFo6Zgybt_JnAG4h1j2M
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: Wed, 16 Apr 2014 16:53:30 -0000
I observe that several sources that derive text from this RFC simply drop the truncated sentence: http://www.cs.cmu.edu/~srini/15-441/S05/assignments/project1/rfc-html/print.html http://www.iternet.biz/Knowledge/Indy9/007493.html -Dave > -----Original Message----- > From: apps-discuss [mailto:apps-discuss-bounces@ietf.org] On Behalf Of > Barry Leiba > Sent: Wednesday, April 16, 2014 8:57 AM > To: Apps Discuss > Cc: Myunggyun Jonathan Aldo Seo > Subject: Re: [apps-discuss] [Technical Errata Reported] RFC1459 (3938) > > 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