[pim] Re: draft-ietf-pim-mofrr-tilfa
linchangwang <linchangwang.04414@h3c.com> Tue, 22 July 2025 13:26 UTC
Return-Path: <linchangwang.04414@h3c.com>
X-Original-To: pim@mail2.ietf.org
Delivered-To: pim@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id 88E8B48736A2 for <pim@mail2.ietf.org>; Tue, 22 Jul 2025 06:26:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: 0.803
X-Spam-Level:
X-Spam-Status: No, score=0.803 tagged_above=-999 required=5 tests=[BAYES_50=0.8, HTML_MESSAGE=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, RCVD_IN_VALIDITY_SAFE_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail2.ietf.org ([166.84.6.31]) by localhost (mail2.ietf.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HEGfw9G6kph2 for <pim@mail2.ietf.org>; Tue, 22 Jul 2025 06:26:03 -0700 (PDT)
Received: from h3cspam02-ex.h3c.com (smtp.h3c.com [60.191.123.50]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id 87204487357B for <pim@ietf.org>; Tue, 22 Jul 2025 06:25:57 -0700 (PDT)
Received: from h3cspam02-ex.h3c.com (localhost [127.0.0.2] (may be forged)) by h3cspam02-ex.h3c.com with ESMTP id 56MBkVOI015354; Tue, 22 Jul 2025 19:46:31 +0800 (+08) (envelope-from linchangwang.04414@h3c.com)
Received: from mail.maildlp.com ([172.25.15.154]) by h3cspam02-ex.h3c.com with ESMTP id 56MBkH5K014804; Tue, 22 Jul 2025 19:46:17 +0800 (+08) (envelope-from linchangwang.04414@h3c.com)
Received: from DAG6EX10-BJD.srv.huawei-3com.com (unknown [10.153.34.12]) by mail.maildlp.com (Postfix) with ESMTP id CFEA320045C1; Tue, 22 Jul 2025 19:51:37 +0800 (CST)
Received: from DAG6EX08-BJD.srv.huawei-3com.com (10.153.34.10) by DAG6EX10-BJD.srv.huawei-3com.com (10.153.34.12) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.1258.27; Tue, 22 Jul 2025 19:46:19 +0800
Received: from DAG6EX08-BJD.srv.huawei-3com.com ([fe80::5d6c:b52b:478f:2738]) by DAG6EX08-BJD.srv.huawei-3com.com ([fe80::5d6c:b52b:478f:2738%17]) with mapi id 15.02.1258.027; Tue, 22 Jul 2025 19:46:19 +0800
From: linchangwang <linchangwang.04414@h3c.com>
To: "guillaume.gryszata@orange.com" <guillaume.gryszata@orange.com>, "draft-liu-pim-mofrr-tilfa@ietf.org" <draft-liu-pim-mofrr-tilfa@ietf.org>
Thread-Topic: [pim] draft-ietf-pim-mofrr-tilfa
Thread-Index: Adv6/jTnGS/6un+IQ1WL7Fqtq+M2hA==
Date: Tue, 22 Jul 2025 11:46:19 +0000
Message-ID: <1edefd927e2941f297bb4a90a8f77b5a@h3c.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
msip_labels: MSIP_Label_e6c818a6-e1a0-4a6e-a969-20d857c5dc62_Enabled=True;MSIP_Label_e6c818a6-e1a0-4a6e-a969-20d857c5dc62_SiteId=90c7a20a-f34b-40bf-bc48-b9253b6f5d20;MSIP_Label_e6c818a6-e1a0-4a6e-a969-20d857c5dc62_SetDate=2025-07-22T09:57:56.0000000Z;MSIP_Label_e6c818a6-e1a0-4a6e-a969-20d857c5dc62_Name=Orange_restricted_internal.2;MSIP_Label_e6c818a6-e1a0-4a6e-a969-20d857c5dc62_ContentBits=3;MSIP_Label_e6c818a6-e1a0-4a6e-a969-20d857c5dc62_Method=Standard
x-originating-ip: [10.142.193.222]
x-sender-location: DAG2
Content-Type: multipart/alternative; boundary="_000_1edefd927e2941f297bb4a90a8f77b5ah3ccom_"
MIME-Version: 1.0
X-DNSRBL:
X-SPAM-SOURCE-CHECK: pass
X-MAIL: h3cspam02-ex.h3c.com 56MBkVOI015354
Message-ID-Hash: DHIJUQJ5I7VCYGRM2RGP34X6DHHT3BYK
X-Message-ID-Hash: DHIJUQJ5I7VCYGRM2RGP34X6DHHT3BYK
X-MailFrom: linchangwang.04414@h3c.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-pim.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: "pim@ietf.org" <pim@ietf.org>
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [pim] Re: draft-ietf-pim-mofrr-tilfa
List-Id: Protocol Independent Multicast <pim.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/pim/JfVzPg8rIjf4UCtbKNIcDvbJPhg>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pim>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Owner: <mailto:pim-owner@ietf.org>
List-Post: <mailto:pim@ietf.org>
List-Subscribe: <mailto:pim-join@ietf.org>
List-Unsubscribe: <mailto:pim-leave@ietf.org>
Hi Guillaume, Thank you for your detailed review and comments. During IESG review, see: https://mailarchive.ietf.org/arch/msg/pim/fU5_Iq2ZkdubaCZGnnxUtkdkE8o/ The conflict scenarios are suggested to be separated, as they are not suitable for the original document, hence they are spun out. Link:https://datatracker.ietf.org/doc/draft-liu-pim-rpf-vector-conflict-resolution/ The conflict scenarios will be presented at the IETF-123 PIM meeting. If interested, you are also welcome to join this document. Thank you. The specific document and presentation materials are as follows: 1. https://datatracker.ietf.org/doc/draft-liu-pim-rpf-vector-conflict-resolution/ 2. https://datatracker.ietf.org/meeting/123/materials/slides-123-pim-pim-reverse-path-forwarding-rpf-vetor-conflict-resolution-00 Thanks, Changwang 发件人: guillaume.gryszata@orange.com <guillaume.gryszata@orange.com> 发送时间: 2025年7月22日 18:23 收件人: draft-liu-pim-mofrr-tilfa@ietf.org 抄送: pim@ietf.org 主题: [pim] draft-ietf-pim-mofrr-tilfa 温馨提示: 此邮件来自公司外部,请核实发件人信息,慎点链接与附件。This is an external email. Please verify the sender's information and proceed with caution when clicking links or downloading attachments. Hello everyone, Regarding the “draft-ietf-pim-mofrr-tilfa”, I raised the following PIM JOIN rpf-vector-conflict : https://mailarchive.ietf.org/arch/msg/pim/vL5AxMbOS-xPoqoZCfglGM76VbA/ This point has been taken into account in https://datatracker.ietf.org/doc/draft-ietf-pim-mofrr-tilfa/09/ section “Join Conflict Considerations”. But this section is no longer present in the current draft version (v14). Could you please tell me what is the reason ? BTW and still regarding this point, I have since identified other scenarios that should be considered. I can provide more details if you wish. Regards, Guillaume Gryszata Orange Restricted ____________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you. ------------------------------------------------------------------------------------------------------------------------------------- 本邮件及其附件含有新华三集团的保密信息,仅限于发送给上面地址中列出 的个人或群组。禁止任何其他人以任何形式使用(包括但不限于全部或部分地泄露、复制、 或散发)本邮件中的信息。如果您错收了本邮件,请您立即电话或邮件通知发件人并删除本 邮件! This e-mail and its attachments contain confidential information from New H3C, which is intended only for the person or entity whose address is listed above. Any use of the information contained herein in any way (including, but not limited to, total or partial disclosure, reproduction, or dissemination) by persons other than the intended recipient(s) is prohibited. If you receive this e-mail in error, please notify the sender by phone or email immediately and delete it!
- [pim] draft-ietf-pim-mofrr-tilfa guillaume.gryszata
- [pim] Re: draft-ietf-pim-mofrr-tilfa linchangwang
- [pim] Re: draft-ietf-pim-mofrr-tilfa guillaume.gryszata
- [pim] draft-ietf-pim-mofrr-tilfa guillaume.gryszata