[pim] comments about draft-hb-pim-light

zhang.zheng@zte.com.cn Wed, 17 November 2021 02:09 UTC

Return-Path: <zhang.zheng@zte.com.cn>
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 CA6413A0AA2 for <pim@ietfa.amsl.com>; Tue, 16 Nov 2021 18:09:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.107
X-Spam-Level:
X-Spam-Status: No, score=-1.107 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H2=-0.001, RDNS_NONE=0.793, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=no autolearn_force=no
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 Ci9u41clj1yd for <pim@ietfa.amsl.com>; Tue, 16 Nov 2021 18:09:20 -0800 (PST)
Received: from mxhk.zte.com.cn (unknown [63.217.80.70]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 264FF3A08F2 for <pim@ietf.org>; Tue, 16 Nov 2021 18:09:06 -0800 (PST)
Received: from mse-fl1.zte.com.cn (unknown [10.30.14.238]) by Forcepoint Email with ESMTPS id 1FC8720F522CCD6AB6E6; Wed, 17 Nov 2021 10:09:03 +0800 (CST)
Received: from njxapp03.zte.com.cn ([10.41.132.202]) by mse-fl1.zte.com.cn with SMTP id 1AH28oSN047143; Wed, 17 Nov 2021 10:08:51 +0800 (GMT-8) (envelope-from zhang.zheng@zte.com.cn)
Received: from mapi (njxapp02[null]) by mapi (Zmail) with MAPI id mid203; Wed, 17 Nov 2021 10:08:50 +0800 (CST)
Date: Wed, 17 Nov 2021 10:08:50 +0800
X-Zmail-TransId: 2afa61946432a6c6f45d
X-Mailer: Zmail v1.0
Message-ID: <202111171008508051787@zte.com.cn>
Mime-Version: 1.0
From: zhang.zheng@zte.com.cn
To: hooman.bidgoli@nokia.com, stig@cisco.com, mankamis@cisco.com, zzhang@juniper.com, michael.mcbride@futurewei.com
Cc: pim@ietf.org
Content-Type: text/plain; charset="UTF-8"
X-MAIL: mse-fl1.zte.com.cn 1AH28oSN047143
Archived-At: <https://mailarchive.ietf.org/arch/msg/pim/zn1yo1TDAT9URHe90d5VJPRvx-c>
Subject: [pim] comments about draft-hb-pim-light
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: Wed, 17 Nov 2021 02:09:27 -0000

Hi Hooman and co-author, 
After reading draft-hb-pim-light, IMO this is a WG work we should do. But many details need to be added for specification and clarification. 
1. The affection for states on the interface needs to be specified, such as (*, G), (S, G), and so on. 
2. The affection for BSM (RFC5059) needs to be specified. 
3. Though I know this draft is used for PIM-SM, not PIM-DM, the clarification is still needed since the title of this draft is PIM light, not PIM-SM light. 
4. If this function can still be used in case of some of the ingress/egress nodes don't support it. 
5. White list or other something is needed for the source verification, only the j/p packet comes from the BGP neighbors (For MVPN, GTM, etc.), or the static configured neighbors, can be accepted. 
6. Since there is no hello packet any more, the DR election is not necessary, so if there is no DR at all?
7. PIM overlay permits different IBBR to select different EBBR, does PIM light permit it? If PIM light permit it, if assert message is unnecessary? What's the use case of keeping assert message in PIM light? 
>From my personal perspective, "PIM-SM light interface" is better for titling. 
BTW, if the reference for draft-hfa-bier-pim-signaling should be draft-ietf-bier-pim-signaling? And seems like there should be no IANA registry.
Thanks,
Sandy