[pim] Question about SR P2MP Policy Ping

"Xiejingrong (Jingrong)" <xiejingrong@huawei.com> Fri, 30 July 2021 23:47 UTC

Return-Path: <xiejingrong@huawei.com>
X-Original-To: pim@ietfa.amsl.com
Delivered-To: pim@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 2072F3A176F for <pim@ietfa.amsl.com>; Fri, 30 Jul 2021 16:47:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.197
X-Spam-Status: No, score=-4.197 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id yaRT67hvaAC0 for <pim@ietfa.amsl.com>; Fri, 30 Jul 2021 16:47:33 -0700 (PDT)
Received: from frasgout.his.huawei.com (frasgout.his.huawei.com []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DEE9E3A1781 for <pim@ietf.org>; Fri, 30 Jul 2021 16:47:32 -0700 (PDT)
Received: from fraeml715-chm.china.huawei.com (unknown []) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4Gc3b454nnz6BB2X for <pim@ietf.org>; Sat, 31 Jul 2021 07:32:16 +0800 (CST)
Received: from kwepeml500003.china.huawei.com ( by fraeml715-chm.china.huawei.com ( with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2176.2; Sat, 31 Jul 2021 01:47:29 +0200
Received: from kwepeml500002.china.huawei.com ( by kwepeml500003.china.huawei.com ( with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2176.2; Sat, 31 Jul 2021 07:47:27 +0800
Received: from kwepeml500002.china.huawei.com ([]) by kwepeml500002.china.huawei.com ([]) with mapi id 15.01.2176.012; Sat, 31 Jul 2021 07:47:27 +0800
From: "Xiejingrong (Jingrong)" <xiejingrong@huawei.com>
To: "pim@ietf.org" <pim@ietf.org>
Thread-Topic: Question about SR P2MP Policy Ping
Thread-Index: AdeFnRdF5+ajXwNuS4qFU1J0YgZG8A==
Date: Fri, 30 Jul 2021 23:47:27 +0000
Message-ID: <c63965a4940349fabddb6aa6b1a44817@huawei.com>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
x-originating-ip: []
Content-Type: multipart/alternative; boundary="_000_c63965a4940349fabddb6aa6b1a44817huaweicom_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/pim/1Dfoe6fcGtgXNC6x1ml4xRodO88>
Subject: [pim] Question about SR P2MP Policy Ping
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: Fri, 30 Jul 2021 23:47:38 -0000

Following up the comment in IETF111 PIM WG online, my question is this.
Ping procedure needs some kind of encapsulation of Echo Request and Echo Reply as in RFC4379, first an UDP encapsulation, and then an IP encapsulation, and lastly the tunnel header encapsulation of MPLS/P2MP and I guess the same for SR-P2MP-policy.
The UDP encapsulation need an UDP port, and the IP encapsulation need src/dst IP or IPv6 addresses.
Are these UDP/src/dst the same as RFC4379 or have some different ones ?