Re: [pim] [Technical Errata Reported] RFC4601 (2927)

"Adrian Farrel" <adrian@olddog.co.uk> Tue, 09 August 2011 21:48 UTC

Return-Path: <adrian@olddog.co.uk>
X-Original-To: pim@ietfa.amsl.com
Delivered-To: pim@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D0EE521F8C6C for <pim@ietfa.amsl.com>; Tue, 9 Aug 2011 14:48:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.291
X-Spam-Level:
X-Spam-Status: No, score=-2.291 tagged_above=-999 required=5 tests=[AWL=-0.292, BAYES_00=-2.599, J_CHICKENPOX_61=0.6]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id u5+i9bV7WbUF for <pim@ietfa.amsl.com>; Tue, 9 Aug 2011 14:48:58 -0700 (PDT)
Received: from asmtp2.iomartmail.com (asmtp2.iomartmail.com [62.128.201.249]) by ietfa.amsl.com (Postfix) with ESMTP id 1409521F8C63 for <pim@ietf.org>; Tue, 9 Aug 2011 14:48:57 -0700 (PDT)
Received: from asmtp2.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp2.iomartmail.com (8.13.8/8.13.8) with ESMTP id p79LnFYt008924; Tue, 9 Aug 2011 22:49:15 +0100
Received: from 950129200 (dsl-sp-81-140-15-32.in-addr.broadbandscope.com [81.140.15.32]) (authenticated bits=0) by asmtp2.iomartmail.com (8.13.8/8.13.8) with ESMTP id p79LnCKW008918 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 9 Aug 2011 22:49:14 +0100
From: Adrian Farrel <adrian@olddog.co.uk>
To: 'Ang Way Chuang' <wcang@sfc.wide.ad.jp>, 'RFC Errata System' <rfc-editor@rfc-editor.org>
References: <20110809102345.D1BDE98C4F9@rfc-editor.org> <4E41489C.6040505@sfc.wide.ad.jp>
In-Reply-To: <4E41489C.6040505@sfc.wide.ad.jp>
Date: Tue, 09 Aug 2011 22:49:12 +0100
Message-ID: <02bf01cc56de$2e3c1640$8ab442c0$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQJDyoDrm2TcN8Ni8VcNbn4ARXOPtgGl88BYlBj2PdA=
Content-Language: en-gb
X-Mailman-Approved-At: Wed, 10 Aug 2011 09:35:45 -0700
Cc: kouvelas@cisco.com, fenner@research.att.com, holbrook@arastra.com, mmcbride7@gmail.com, M.Handley@cs.ucl.ac.uk, pim@ietf.org
Subject: Re: [pim] [Technical Errata Reported] RFC4601 (2927)
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: adrian@olddog.co.uk
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pim>, <mailto:pim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pim>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pim>, <mailto:pim-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Aug 2011 21:48:58 -0000

How nice to hear someone say "blimey." I think my grandfather used to say it -
he was born in East London - but it is not in wide use :-)

I updated the type to Editorial. Thanks for coming back on the point.

Cheers,
Adrian

> -----Original Message-----
> From: Ang Way Chuang [mailto:wcang@sfc.wide.ad.jp]
> Sent: 09 August 2011 15:48
> To: RFC Errata System
> Cc: fenner@research.att.com; M.Handley@cs.ucl.ac.uk; holbrook@arastra.com;
> kouvelas@cisco.com; stbryant@cisco.com; adrian@olddog.co.uk;
> mmcbride7@gmail.com; stig@venaas.com; pim@ietf.org
> Subject: Re: [Technical Errata Reported] RFC4601 (2927)
> 
> blimey, the type should be editorial not technical.
> 
> On 09/08/11 19:23, RFC Errata System wrote:
> > The following errata report has been submitted for RFC4601,
> > "Protocol Independent Multicast - Sparse Mode (PIM-SM): Protocol
> Specification (Revised)".
> >
> > --------------------------------------
> > You may review the report below and at:
> > http://www.rfc-editor.org/errata_search.php?rfc=4601&eid=2927
> >
> > --------------------------------------
> > Type: Technical
> > Reported by: Ang Way Chuang<wcang@sfc.wide.ad.jp>
> >
> > Section: 4.2.2
> >
> > Original Text
> > -------------
> >       void
> >
> >       Update_SPTbit(S,G,iif) {
> >
> >         if ( iif == RPF_interface(S)
> >
> >               AND JoinDesired(S,G) == TRUE
> >
> >               AND ( DirectlyConnected(S) == TRUE
> >
> >                     OR RPF_interface(S) != RPF_interface(RP(G))
> >
> >                     OR inherited_olist(S,G,rpt) == NULL
> >
> >                     OR ( ( RPF'(S,G) == RPF'(*,G) ) AND
> >
> >                          ( RPF'(S,G) != NULL ) )
> >
> >                     OR ( I_Am_Assert_Loser(S,G,iif) ) {
> >
> >            Set SPTbit(S,G) to TRUE
> >
> >         }
> >
> >       }
> >
> > Corrected Text
> > --------------
> >       void
> >
> >       Update_SPTbit(S,G,iif) {
> >
> >         if ( iif == RPF_interface(S)
> >
> >               AND JoinDesired(S,G) == TRUE
> >
> >               AND ( DirectlyConnected(S) == TRUE
> >
> >                     OR RPF_interface(S) != RPF_interface(RP(G))
> >
> >                     OR inherited_olist(S,G,rpt) == NULL
> >
> >                     OR ( ( RPF'(S,G) == RPF'(*,G) ) AND
> >
> >                          ( RPF'(S,G) != NULL ) )
> >
> >                     OR ( I_Am_Assert_Loser(S,G,iif) ) ) ) {
> >
> >            Set SPTbit(S,G) to TRUE
> >
> >         }
> >
> >       }
> >
> > Notes
> > -----
> > The logical evaluation is not properly enclosed. The RFC also doesn't
mention
> the reason for the extra checking on the RPF'(S,G) != NULL. It is non-obvious
to
> me. If the check on iif == RPF_interface(S) passes, how would there be any
> condition where RPF'(S,G) == NULL?
> >
> > 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.
> >
> > --------------------------------------
> > RFC4601 (draft-ietf-pim-sm-v2-new-12)
> > --------------------------------------
> > Title               : Protocol Independent Multicast - Sparse Mode (PIM-SM):
Protocol
> Specification (Revised)
> > Publication Date    : August 2006
> > Author(s)           : B. Fenner, M. Handley, H. Holbrook, I. Kouvelas
> > Category            : PROPOSED STANDARD
> > Source              : Protocol Independent Multicast
> > Area                : Routing
> > Stream              : IETF
> > Verifying Party     : IESG
> >