Re: [pim] [Editorial Errata Reported] RFC3376 (5562)

"Mankamana Mishra (mankamis)" <mankamis@cisco.com> Tue, 27 November 2018 20:41 UTC

Return-Path: <mankamis@cisco.com>
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 28555127133 for <pim@ietfa.amsl.com>; Tue, 27 Nov 2018 12:41:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.96
X-Spam-Level:
X-Spam-Status: No, score=-15.96 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-1.46, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
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 SxG-mVu0kpVP for <pim@ietfa.amsl.com>; Tue, 27 Nov 2018 12:41:42 -0800 (PST)
Received: from rcdn-iport-4.cisco.com (rcdn-iport-4.cisco.com [173.37.86.75]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 73956124D68 for <pim@ietf.org>; Tue, 27 Nov 2018 12:41:42 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=25008; q=dns/txt; s=iport; t=1543351302; x=1544560902; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=hDD97vwtVau/SHNwkhuTzf01s+j0nhSgwTsP3zU/Ybo=; b=aAyiJhAk2TVCtTO8m6bW4I/H/xSiOGmluNPCHbjnjyObGU7VExiqKag9 jepPd0v/KKBNOMKvw65jourVswhny95/pE4pBkIq8tIsTBqoHSlw9UUT9 Ji4eb+pFPdasDijRb1edBwZPKbRHVho4o7lacO6ZhitZZQlx1yxA8Lyhe g=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0AEAADOq/1b/5ldJa1jGgEBAQEBAgEBAQEHAgEBAQGBUQUBAQEBCwGBDUguZoECJwqDb4gYjAiLHI4xFIFmCwEBGAEKhEkCF4MBIjQJDQEDAQECAQECbRwMhT0CAQMBASFLCxACAQYCDjEDAgICHwYLFBECBA4FgyEBgR1MAxUPikObUIEvhUCCTA2CHIwNF4FAP4ERJx+CTIFBgRZHAQGBKYM8MYImAoknJoU8gVyEWoofLgkCjgKDLBIGgVmFC4onjlCJQAIRFIEnHziBVXAVGiEqAYJBCYIqiGmFP0ExAYxtgR8BAQ
X-IronPort-AV: E=Sophos;i="5.56,287,1539648000"; d="scan'208,217";a="488605902"
Received: from rcdn-core-2.cisco.com ([173.37.93.153]) by rcdn-iport-4.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 27 Nov 2018 20:41:18 +0000
Received: from XCH-RCD-009.cisco.com (xch-rcd-009.cisco.com [173.37.102.19]) by rcdn-core-2.cisco.com (8.15.2/8.15.2) with ESMTPS id wARKfIIa022218 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Tue, 27 Nov 2018 20:41:19 GMT
Received: from xch-rcd-008.cisco.com (173.37.102.18) by XCH-RCD-009.cisco.com (173.37.102.19) with Microsoft SMTP Server (TLS) id 15.0.1395.4; Tue, 27 Nov 2018 14:41:17 -0600
Received: from xch-rcd-008.cisco.com ([173.37.102.18]) by XCH-RCD-008.cisco.com ([173.37.102.18]) with mapi id 15.00.1395.000; Tue, 27 Nov 2018 14:41:17 -0600
From: "Mankamana Mishra (mankamis)" <mankamis@cisco.com>
To: Alvaro Retana <aretana.ietf@gmail.com>
CC: "pim@ietf.org" <pim@ietf.org>, "wim.1.de_smet@nokia-sbell.com" <wim.1.de_smet@nokia-sbell.com>
Thread-Topic: [pim] [Editorial Errata Reported] RFC3376 (5562)
Thread-Index: AQHUhpAYtfbpygmW9kKxGnSAwH+jU6VkeoyA
Date: Tue, 27 Nov 2018 20:41:17 +0000
Message-ID: <E15133C8-569B-4A7C-AA7E-A065E705C122@cisco.com>
References: <20181126063603.3816FB814A1@rfc-editor.org> <CAMMESsy-Lmd=+1n1W3zQcCTWHEHzZ-he1bJFEigFLfjPE4qrOg@mail.gmail.com>
In-Reply-To: <CAMMESsy-Lmd=+1n1W3zQcCTWHEHzZ-he1bJFEigFLfjPE4qrOg@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.154.160.76]
Content-Type: multipart/alternative; boundary="_000_E15133C8569B4A7CAA7EA065E705C122ciscocom_"
MIME-Version: 1.0
X-Outbound-SMTP-Client: 173.37.102.19, xch-rcd-009.cisco.com
X-Outbound-Node: rcdn-core-2.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/pim/U1jV4e1b32InA7Bob99CYAcWxVE>
Subject: Re: [pim] [Editorial Errata Reported] RFC3376 (5562)
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.29
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: <https://mailarchive.ietf.org/arch/browse/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, 27 Nov 2018 20:41:45 -0000

May be "first set" would be good to use if we plan to edit.

 But without even change, is it not clear enough that we are talking about 2nd set in EXCLUDE mode which would be INCLUDE mode list ?

Mankamana

On Nov 27, 2018, at 12:30 PM, Alvaro Retana <aretana.ietf@gmail.com<mailto:aretana.ietf@gmail.com>> wrote:

Dear WG:

Any thoughts?

At first glance, it looks like there may be an editorial error.  Do you agree?  If so, which should it be: “…two different sets…” or “…the first set…”?

Thanks!

Alvaro.


On November 26, 2018 at 1:36:38 AM, RFC Errata System (rfc-editor@rfc-editor.org<mailto:rfc-editor@rfc-editor.org>) wrote:

The following errata report has been submitted for RFC3376,
"Internet Group Management Protocol, Version 3".

--------------------------------------
You may review the report below and at:
http://www.rfc-editor.org/errata/eid5562

--------------------------------------
Type: Editorial
Reported by: Wim De Smet <wim.1.de_smet@nokia-sbell.com<mailto:wim.1.de_smet@nokia-sbell.com>>

Section: 6.2.1

Original Text
-------------

When a router filter-mode for a group is EXCLUDE, the source record
list contains two types of sources. The first type is the set which
represents conflicts in the desired reception state; this set must be
forwarded by some router on the network. The second type is the set
of sources which hosts have requested to not be forwarded. Appendix
A describes the reasons for keeping this second set when in EXCLUDE
mode.

Corrected Text
--------------
[see note]

Notes
-----
Appendix A.3 contains the following:
One of the ways to accomplish this is for routers to keep track of
all sources desired by hosts that are in INCLUDE mode even though the
router itself is in EXCLUDE mode.

Appendix A.3 makes clear that in EXCLUDE mode we need to keep track of the set of hosts that *are* desired (i.e. set A in section 6.4 or the "first type" in this paragraph). The second set (set B in section 6.4) is the set that will be reported to upstream routers, it is not the set which is needed for smooth switching to INCLUDE mode (the behavior described in appendix A). I believe that the intended description may have been "Appendix A describes the reasons for keeping two different sets when in EXCLUDE mode". At the very least, it appears to be set A (the "first set") which is intended in appendix A.

Instructions:
-------------
This erratum 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
can log in to change the status and edit the report, if necessary.

--------------------------------------
RFC3376 (draft-ietf-idmr-igmp-v3-11)
--------------------------------------
Title : Internet Group Management Protocol, Version 3
Publication Date : October 2002
Author(s) : B. Cain, S. Deering, I. Kouvelas, B. Fenner, A. Thyagarajan
Category : PROPOSED STANDARD
Source : Inter-Domain Multicast Routing
Area : Routing
Stream : IETF
Verifying Party : IESG
_______________________________________________
pim mailing list
pim@ietf.org<mailto:pim@ietf.org>
https://www.ietf.org/mailman/listinfo/pim