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

RFC Errata System <rfc-editor@rfc-editor.org> Tue, 09 August 2011 10:23 UTC

Return-Path: <wwwrun@rfc-editor.org>
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 EAB0621F8ACE for <pim@ietfa.amsl.com>; Tue, 9 Aug 2011 03:23:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.25
X-Spam-Level:
X-Spam-Status: No, score=-102.25 tagged_above=-999 required=5 tests=[AWL=-0.250, BAYES_00=-2.599, J_CHICKENPOX_61=0.6, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
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 tC+F7iYx9fMd for <pim@ietfa.amsl.com>; Tue, 9 Aug 2011 03:23:17 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:123a::1:2f]) by ietfa.amsl.com (Postfix) with ESMTP id 84CD821F8AAC for <pim@ietf.org>; Tue, 9 Aug 2011 03:23:17 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id D1BDE98C4F9; Tue, 9 Aug 2011 03:23:45 -0700 (PDT)
To: 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
From: RFC Errata System <rfc-editor@rfc-editor.org>
Message-Id: <20110809102345.D1BDE98C4F9@rfc-editor.org>
Date: Tue, 09 Aug 2011 03:23:45 -0700
X-Mailman-Approved-At: Tue, 09 Aug 2011 09:24:41 -0700
Cc: wcang@sfc.wide.ad.jp, pim@ietf.org, rfc-editor@rfc-editor.org
Subject: [pim] [Technical Errata Reported] RFC4601 (2927)
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
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 10:23:18 -0000

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