Re: [apps-discuss] [Technical Errata Reported] RFC1459 (3938)

Tki April <tki@tki.so> Fri, 20 June 2014 15:37 UTC

Return-Path: <tki@tki.so>
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 139101B281C for <apps-discuss@ietfa.amsl.com>; Fri, 20 Jun 2014 08:37:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_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 Iy46ULynzcH7 for <apps-discuss@ietfa.amsl.com>; Fri, 20 Jun 2014 08:37:45 -0700 (PDT)
Received: from SNT004-OMC4S37.hotmail.com (snt004-omc4s37.hotmail.com [65.55.90.240]) (using TLSv1.2 with cipher AES128-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B4C7B1B2833 for <apps-discuss@ietf.org>; Fri, 20 Jun 2014 08:37:36 -0700 (PDT)
Received: from SNT153-W39 ([65.55.90.199]) by SNT004-OMC4S37.hotmail.com with Microsoft SMTPSVC(7.5.7601.22701); Fri, 20 Jun 2014 08:37:35 -0700
X-TMN: [DtoDM2OWVlL5sdYFE/Ie/XMazphoeJBs]
X-Originating-Email: [tki@tki.so]
Message-ID: <SNT153-W3963F91F6DB11758E84F5FC8120@phx.gbl>
Content-Type: multipart/alternative; boundary="_d1714cfc-50ec-4821-874b-b56bb98885e2_"
From: Tki April <tki@tki.so>
To: "t.petch" <ietfc@btconnect.com>, Barry Leiba <barryleiba@computer.org>, Apps Discuss <apps-discuss@ietf.org>
Date: Fri, 20 Jun 2014 08:37:35 -0700
Importance: Normal
In-Reply-To: <043201cf8c8d$194d2fc0$4001a8c0@gateway.2wire.net>
References: <20140328105940.ADCCF7FC2CB@rfc-editor.org> <CALaySJLvh9iuYYCkzDgPD7hTW+sZTSd6XvcrJgkCu=cDM7pFzg@mail.gmail.com>, <043201cf8c8d$194d2fc0$4001a8c0@gateway.2wire.net>
MIME-Version: 1.0
X-OriginalArrivalTime: 20 Jun 2014 15:37:35.0981 (UTC) FILETIME=[8F59B9D0:01CF8C9D]
Archived-At: http://mailarchive.ietf.org/arch/msg/apps-discuss/8gDqgqNWOasKHgVrmMDC9roqYkw
X-Mailman-Approved-At: Sat, 21 Jun 2014 21:28:11 -0700
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 15:45:10 -0000

When I reported this erratum, I recognized that RFC 1459 was updatedby RFC2810-2813, but was curious to find out that no one had pointedout the clearly missing sentence. I do understand that it is not a criticalmatter.
ThanksMyunggyun Seo
> From: ietfc@btconnect.com
> To: barryleiba@computer.org; apps-discuss@ietf.org
> CC: tki@tki.so
> Subject: Re: [apps-discuss] [Technical Errata Reported] RFC1459 (3938)
> Date: Fri, 20 Jun 2014 14:32:14 +0100
> 
> 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
>