[pim] Re: Mohamed Boucadair's No Objection on draft-ietf-pim-mofrr-tilfa-09: (with COMMENT)

linchangwang <linchangwang.04414@h3c.com> Tue, 01 April 2025 06:08 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 33B9D1598E55; Mon, 31 Mar 2025 23:08:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 9IezThXtrIum; Mon, 31 Mar 2025 23:08:10 -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 C73411598E4F; Mon, 31 Mar 2025 23:08:08 -0700 (PDT)
Received: from mail.maildlp.com ([172.25.15.154]) by h3cspam02-ex.h3c.com with ESMTP id 53167jUS046365; Tue, 1 Apr 2025 14:07:45 +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 E040420045AD; Tue, 1 Apr 2025 14:10:26 +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, 1 Apr 2025 14:07:43 +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, 1 Apr 2025 14:07:43 +0800
From: linchangwang <linchangwang.04414@h3c.com>
To: "mohamed.boucadair@orange.com" <mohamed.boucadair@orange.com>, The IESG <iesg@ietf.org>
Thread-Topic: Mohamed Boucadair's No Objection on draft-ietf-pim-mofrr-tilfa-09: (with COMMENT)
Thread-Index: Aduiy9n+0CcfAQJRScG7eecmz5iY0Q==
Date: Tue, 01 Apr 2025 06:07:43 +0000
Message-ID: <16c7b48e7ddc44e3bf7a7428a64a6f18@h3c.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
msip_labels: MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_ActionId=3bcfc434-4a8e-4816-a7c5-fc6d6e692bd8;MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_ContentBits=0;MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_Enabled=true;MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_Method=Privileged;MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_Name=unrestricted_parent.2;MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_SetDate=2025-03-31T17:00:44Z;MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_SiteId=90c7a20a-f34b-40bf-bc48-b9253b6f5d20;MSIP_Label_f47c794b-e3ab-43f0-9e0f-29fc3e503192_ContentBits=0;MSIP_Label_f47c794b-e3ab-43f0-9e0f-29fc3e503192_Enabled=true;MSIP_Label_f47c794b-e3ab-43f0-9e0f-29fc3e503192_Method=Standard;
x-originating-ip: [10.142.193.222]
x-sender-location: DAG2
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-DNSRBL:
X-SPAM-SOURCE-CHECK: pass
X-MAIL: h3cspam02-ex.h3c.com 53167jUS046365
Message-ID-Hash: MIMO26MJFNZRV6LNNVKOCQJVDAW2PCAZ
X-Message-ID-Hash: MIMO26MJFNZRV6LNNVKOCQJVDAW2PCAZ
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: "draft-ietf-pim-mofrr-tilfa@ietf.org" <draft-ietf-pim-mofrr-tilfa@ietf.org>, "pim-chairs@ietf.org" <pim-chairs@ietf.org>, "pim@ietf.org" <pim@ietf.org>, "ops-dir@ietf.org" <ops-dir@ietf.org>
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [pim] Re: Mohamed Boucadair's No Objection on draft-ietf-pim-mofrr-tilfa-09: (with COMMENT)
List-Id: Protocol Independent Multicast <pim.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/pim/1dZqIq8YU9j2lSi7hPhF8mCUYY8>
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 Med,

Thank you for your thoughtful comments and suggestions.

All your new comments have been addressed in latest version.

https://datatracker.ietf.org/doc/draft-ietf-pim-mofrr-tilfa/12/

Pls check and let us know if there are any further comments.

Thanks,
Changwang



-----邮件原件-----
发件人: mohamed.boucadair@orange.com <mohamed.boucadair@orange.com> 
发送时间: 2025年4月1日 1:01
收件人: linchangwang (RD) <linchangwang.04414@h3c.com>; The IESG <iesg@ietf.org>
抄送: draft-ietf-pim-mofrr-tilfa@ietf.org; pim-chairs@ietf.org; pim@ietf.org; stig@venaas.com; ops-dir@ietf.org
主题: RE: Mohamed Boucadair's No Objection on draft-ietf-pim-mofrr-tilfa-09: (with COMMENT)

Hi Changwang, 

This looks better. Thanks.

I guess:

* s/The all nodes on the backup/All nodes on the backup
* s/As the administrator is manually/If an administrator is manually
* s/Explicit Vector/Explicit RPF Vector?
* s/mtrace/mtrace [RFC8487]

Cheers,
Med

> -----Message d'origine-----
> De : linchangwang <linchangwang.04414@h3c.com> Envoyé : lundi 31 mars 
> 2025 18:47 À : BOUCADAIR Mohamed INNOV/NET 
> <mohamed.boucadair@orange.com>; The IESG <iesg@ietf.org> Cc : 
> draft-ietf-pim-mofrr-tilfa@ietf.org; pim-chairs@ietf.org; 
> pim@ietf.org; stig@venaas.com; ops-dir@ietf.org Objet : Re: Mohamed 
> Boucadair's No Objection on draft-ietf-pim-
> mofrr-tilfa-09: (with COMMENT)
> 
> 
> Hi Med,
> 
> I submitted version-11 to address the following comments:
> 
> Link:
> https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2F
> datatracker.ietf.org%2Fdoc%2Fdraft-ietf-pim-mofrr-
> tilfa%2F11%2F&data=05%7C02%7Cmohamed.boucadair%40orange.com%7C8ea1
> daf1905a4b2ef3c408dd7073ac96%7C90c7a20af34b40bfbc48b9253b6f5d20%7C
> 0%7C0%7C638790364324503400%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGk
> iOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUI
> joyfQ%3D%3D%7C0%7C%7C%7C&sdata=kiQIDH%2Bg%2Bzffur3kbaXnHxjud4%2FUP
> eOClGuvYTUV2%2Bs%3D&reserved=0
> 
> Please see inline...
> 
> Thanks,
> Changwang
> 
> -----邮件原件-----
> 发件人: mohamed.boucadair@orange.com <mohamed.boucadair@orange.com>
> 发送时间: 2025年3月30日 17:10
> 收件人: linchangwang (RD) <linchangwang.04414@h3c.com>; The IESG 
> <iesg@ietf.org>
> 抄送: draft-ietf-pim-mofrr-tilfa@ietf.org; pim-chairs@ietf.org; 
> pim@ietf.org; stig@venaas.com; ops-dir@ietf.org
> 主题: RE: Mohamed Boucadair's No Objection on draft-ietf-pim-mofrr-
> tilfa-09: (with COMMENT)
> 
> Hi Changwang,
> 
> Thank you for taking care of the review.
> 
> (1) This version addresses all my comments, except on the "operational 
> considerations". I understand that removing the mention can be seen as 
> a fix, but I was actually hoping we elaborate more on these matters 
> :-)
> 
> For example, I would appreciate if we can consider adding some text to 
> answer the few questions raised by Jürgen in his opsdir review of -05 
> (pointing to 7916 when appropriate would be sufficient, though):
> 
>   "How is this extension deployed? Can it be deployed incrementally or 
> do
>    all multicast routers have to understand the RPF Vector Attributes 
> in
>    the PIM Join packet to work properly? And are there any further
>    recommendations about debuggingoperational or deployment errors, 
> are
>    there procedures to verify that the calculated alternative routes 
> or
>    is thisno different than with other fast multicast reroute
>    mechanisms?"
> 
> [Changwang]: Version-11 adds Section 6: Management and Operational 
> Considerations, to see if it resolves this issue.
> 
> (2) If you keep the current wording, then I'm afraid that we will need 
> to remove RFC7916 from being listed as Normative and list it as 
> Informative.
> 
> [Changwang]: Version-11 adds Section 6: Management and Operational 
> Considerations, to see if it resolves this issue.
> 
> (3) (nitty nit), please replace all PIM join mentions with PIM Join.
> 
> [Changwang]: thanks, Modified in version-11.
> 
> 
> Thank you.
> 
> Cheers,
> Med
> 
> > -----Message d'origine-----
> > De : linchangwang <linchangwang.04414@h3c.com> Envoyé : samedi
> 29 mars
> > 2025 12:39 À : BOUCADAIR Mohamed INNOV/NET 
> > <mohamed.boucadair@orange.com>; The IESG <iesg@ietf.org> Cc :
> > draft-ietf-pim-mofrr-tilfa@ietf.org; pim-chairs@ietf.org; 
> > pim@ietf.org; stig@venaas.com Objet : Re: Mohamed Boucadair's No 
> > Objection on draft-ietf-pim-mofrr-
> > tilfa-09: (with COMMENT)
> >
> >
> > Hi Med,
> >
> > Thank you for your review.
> > We appreciate your thoughtful comments and suggestions.
> >
> > All your comments have been addressed in latest version.
> >
> https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2F
> data
> >
> %2F&data=05%7C02%7Cmohamed.boucadair%40orange.com%7C8ea1daf1905a4b
> 2ef3
> >
> c408dd7073ac96%7C90c7a20af34b40bfbc48b9253b6f5d20%7C0%7C0%7C638790
> 3643
> >
> 24519120%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwL
> jAuM
> >
> DAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%
> 7C&s
> > data=IeozBLg5flMQPrMGHeXABn30z4wq8NANdi1U6SFJwWE%3D&reserved=0
> > tracker.ietf.org%2Fdoc%2Fdraft-ietf-pim-mofrr-
> >
> tilfa%2F10%2F&data=05%7C02%7Cmohamed.boucadair%40orange.com%7Cbb23
> 8f3c
> >
> e102488fc62e08dd6eb66a80%7C90c7a20af34b40bfbc48b9253b6f5d20%7C0%7C
> 0%7C
> >
> 638788451947102724%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWU
> sIlY
> >
> iOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%
> 7C0%
> >
> 7C%7C%7C&sdata=9Lhaj4F%2BfqoGj0FzWzzPHVwfyC0x2AaGDJLnmoTCDtQ%3D&re
> serv
> > ed=0
> >
> > Pls check and let us know if there are any further comments.
> >
> >
> > Thanks,
> > Changwang
> >
> >
> >
> > -----邮件原件-----
> > 发件人: Mohamed Boucadair via Datatracker <noreply@ietf.org>
> > 发送时间: 2025年3月24日 21:30
> > 收件人: The IESG <iesg@ietf.org>
> > 抄送: draft-ietf-pim-mofrr-tilfa@ietf.org; pim-chairs@ietf.org; 
> > pim@ietf.org; stig@venaas.com; stig@venaas.com
> > 主题: Mohamed Boucadair's No Objection on draft-ietf-pim-mofrr-
> tilfa-
> > 09: (with COMMENT)
> >
> > Mohamed Boucadair has entered the following ballot position for
> > draft-ietf-pim-mofrr-tilfa-09: No Objection
> >
> > When responding, please keep the subject line intact and reply
> to all
> > email addresses included in the To and CC lines. (Feel free to
> cut
> > this introductory paragraph, however.)
> >
> >
> > Please refer to
> >
> https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2F
> www%2F&data=05%7C02%7Cmohamed.boucadair%40orange.com%7C8ea1daf1905
> a4b2ef3c408dd7073ac96%7C90c7a20af34b40bfbc48b9253b6f5d20%7C0%7C0%7
> C638790364324527229%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydW
> UsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3
> D%3D%7C0%7C%7C%7C&sdata=kNA1abnxkuQJaBi2GSZr0gcIsGXIUDV0iJST2iqMT9
> c%3D&reserved=0.
> > ietf.org%2Fabout%2Fgroups%2Fiesg%2Fstatements%2Fhandling-ballot-
> >
> positions%2F&data=05%7C02%7Cmohamed.boucadair%40orange.com%7Cbb238
> f3ce
> >
> 102488fc62e08dd6eb66a80%7C90c7a20af34b40bfbc48b9253b6f5d20%7C0%7C0
> %7C6
> >
> 38788451947118271%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUs
> IlYi
> >
> OiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7
> C0%7
> >
> C%7C%7C&sdata=ZsErxC8k9trf6cT9UcXzCF7YxBsPsVLGdUPDL59nipA%3D&reser
> ved=
> > 0
> > for more information about how to handle DISCUSS and COMMENT 
> > positions.
> >
> >
> > The document, along with other ballot positions, can be found
> here:
> >
> https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2F
> data
> >
> %2F&data=05%7C02%7Cmohamed.boucadair%40orange.com%7C8ea1daf1905a4b
> 2ef3
> >
> c408dd7073ac96%7C90c7a20af34b40bfbc48b9253b6f5d20%7C0%7C0%7C638790
> 3643
> >
> 24535631%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwL
> jAuM
> >
> DAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%
> 7C&s
> > data=QMR7Qza6hbB2MK57NNFcoNC8z3%2BCmuSJs32D3uQvEYw%3D&reserved=0
> > tracker.ietf.org%2Fdoc%2Fdraft-ietf-pim-mofrr-
> >
> tilfa%2F&data=05%7C02%7Cmohamed.boucadair%40orange.com%7Cbb238f3ce
> 1024
> >
> 88fc62e08dd6eb66a80%7C90c7a20af34b40bfbc48b9253b6f5d20%7C0%7C0%7C6
> 3878
> >
> 8451947126595%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYi
> OiIw
> >
> LjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7
> C%7C
> >
> %7C&sdata=71NjLz6HzKLcKcQEbAemaTt%2FGxIhFZDXZVOM%2BhJfpEo%3D&reser
> ved=
> > 0
> >
> >
> >
> > ----------------------------------------------------------------
> ------
> > COMMENT:
> > ----------------------------------------------------------------
> ------
> >
> > Hi Yisong, Mike, Zheng, Jingrong, and Changwang,
> >
> > Thank you for the effort put into this specification.
> >
> > Please find below some comments:
> >
> > # Abstract
> >
> > CURRENT:
> >
> >    The
> >    document outlines the necessary protocol extensions and
> operational
> >    considerations to implement TI-LFA in conjunction with MoFRR
> for
> > PIM,
> >    ensuring that multicast traffic is rapidly rerouted in the
> event of
> > a
> >    failure.
> >
> > ## On “protocol extensions”: Seems conflicting with the intended
> Info
> > status and also the clarification note included in the intro and 
> > another section.
> >
> > ## On “operational considerations” or lack of
> >
> > (1) Which part of the document are you referring to?
> > (2) I was expecting to see at least RFC8102 referenced in the
> main
> > body on the manageability aspects (3) Also, is the approach
> immune
> > against micro loops? If not a concern, can we explicit that in
> the
> > doc?
> >
> > # Introduction:
> >
> > (1)
> >
> > CURRENT:
> >    The increasing deployment of video services has heightened
> the
> >    importance for network operators to implement solutions that 
> > minimize
> >    service disruptions caused by faults in the IP networks ...
> >
> > One would argue that the increase is related to unicast
> delivery,
> > mainly.
> > Deleting this sentence and starting with the sentence right
> after
> > would be fine. No need to over motivate the need ;-)
> >
> > (2)
> >
> > CURRENT:
> >    fast reroute defined in [RFC7431], has limitations in certain
> >    multicast deployment scenarios.
> >
> > Can we call these limitations out or point to the section where
> this
> > is discussed?
> >
> > (3)
> >
> > CURRENT:
> >     The
> >    applicability of this mechanism extends to PIM networks,
> including
> >    scenarios where PIM operates over native IP, as well as
> public
> >    network multicast trees established by PIM .  Additionally,
> this
> >    document addresses scenarios involving Multicast Distribution
> Tree
> >    (MDT) SAFI for Multicast VPN (MVPN) in [RFC6037] and
> [RFC6514],..
> >
> > * “public network multicast trees”: Do you mean inter-domain? If
> so,
> > some discussion on the implications/deployment considerations
> are
> > needed. * “[RFC6037] and [RFC6514]”: Why is this cited? Why this 
> > specific flavor? What about RFC6513? If you maintain this
> mention, can
> > we have an example to illustrate the use?
> >
> > # Section 2.1
> >
> > * “For multicast source S1, …”: The receiver should be mentioned
> also.
> > * Better to include the metrics directly in the graph as this
> eases
> > following the example. * Mention that all link metrics are 
> > bidirectional?
> >
> > # Section 2.2
> >
> > “is neither on the path from the source node to node N”: The
> source
> > node should be clarified to avoid confusion with multicast
> source.
> >
> > # Section 5
> >
> > CURRENT:
> >    This document specifies an optional approach for backup join
> paths,
> >    intended to enhance the protection scope of existing
> multicast
> >    systems.  It is fully compatible with existing protocol
> >    implementations and does not require changes to protocols or
> >    forwarding functions on intermediate nodes.  In the event of
> PIM
> > Join
> >    conflicts, Join messages without the RPF Vector attribute are 
> > prioritized to
> >    ensure that the original PIM forwarding functionality remains
> >    unaffected.
> >
> > Already mentioned in the introduction. Any reason this text
> repeated?
> > I would delete it.
> >
> > # Full review
> >
> > More comments, edits, nits, etc. can be found here:
> >
> > * pdf:
> >
> https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2F
> gith
> >
> %2F&data=05%7C02%7Cmohamed.boucadair%40orange.com%7C8ea1daf1905a4b
> 2ef3
> >
> c408dd7073ac96%7C90c7a20af34b40bfbc48b9253b6f5d20%7C0%7C0%7C638790
> 3643
> >
> 24544123%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwL
> jAuM
> >
> DAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%
> 7C&s
> > data=3fKqdENMzzexjeRwD0AOmad7DfnPGYY8c6%2B6STenqYg%3D&reserved=0
> > ub.com%2Fboucadair%2FIETF-Drafts-
> > Reviews%2Fblob%2Fmaster%2F2025%2Fdraft-ietf-pim-mofrr-tilfa-09-
> >
> rev%2520Med.pdf&data=05%7C02%7Cmohamed.boucadair%40orange.com%7Cbb
> 238f
> >
> 3ce102488fc62e08dd6eb66a80%7C90c7a20af34b40bfbc48b9253b6f5d20%7C0%
> 7C0%
> >
> 7C638788451947134610%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRyd
> WUsI
> >
> lYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3
> D%7C
> >
> 0%7C%7C%7C&sdata=%2B1Vhynpy%2Brfcvx55larQzAhAM87KRftPw3SxCznbf4c%3
> D&re
> > served=0
> > * doc:
> >
> https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2F
> gith
> >
> %2F&data=05%7C02%7Cmohamed.boucadair%40orange.com%7C8ea1daf1905a4b
> 2ef3
> >
> c408dd7073ac96%7C90c7a20af34b40bfbc48b9253b6f5d20%7C0%7C0%7C638790
> 3643
> >
> 24552283%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwL
> jAuM
> >
> DAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%
> 7C&s
> >
> data=JDVkAp0e7vorDuOTdCzbZ6sV%2FQ%2Bbx703IAD0XmYZveI%3D&reserved=0
> > ub.com%2Fboucadair%2FIETF-Drafts-
> > Reviews%2Fblob%2Fmaster%2F2025%2Fdraft-ietf-pim-mofrr-tilfa-09-
> >
> rev%2520Med.doc&data=05%7C02%7Cmohamed.boucadair%40orange.com%7Cbb
> 238f
> >
> 3ce102488fc62e08dd6eb66a80%7C90c7a20af34b40bfbc48b9253b6f5d20%7C0%
> 7C0%
> >
> 7C638788451947142818%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRyd
> WUsI
> >
> lYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3
> D%7C
> >
> 0%7C%7C%7C&sdata=AKR5Y%2BErDHkcT9oRXEp8%2B44ZBmQSq5C7EeItAQwYtkg%3
> D&re
> > served=0
> >
> >
> __________________________________________________________________
> __________________________________________
> 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!
____________________________________________________________________________________________________________
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.