Hi Kaelin,
I agree to publish the document. Thank you for your help with improving the document. Best Regards Yisong ----邮件原文---- 发件人：Kaelin Foody <[email protected]> 收件人：linchangwang <[email protected]> 抄 送: "[email protected]" <[email protected]>,"[email protected]" <[email protected]>,"[email protected]" <[email protected]>,"[email protected]" <[email protected]>,"[email protected]" <[email protected]>,"[email protected]" <[email protected]>,"[email protected]" <[email protected]>,"[email protected]" <[email protected]>,"[email protected]" <[email protected]>,"[email protected]" <[email protected]> 发送时间：2025-09-19 04:49:06 主题：Re: AUTH48: RFC-to-be 9860 <draft-ietf-pim-mofrr-tilfa-14> for yourreview Hi Changwang, Thank you for your reply. We have updated the document accordingly. We will await approvals from each of the parties listed on the AUTH48 status page prior to moving forward with publication. The AUTH48 status page for this document is available here: https://www.rfc-editor.org/auth48/rfc9860 Please review the document carefully to ensure satisfaction as we do not make changes once it has been published as an RFC. — FILES (please refresh): — The updated files have been posted here: https://www.rfc-editor.org/authors/rfc9860.txt https://www.rfc-editor.org/authors/rfc9860.pdf https://www.rfc-editor.org/authors/rfc9860.html https://www.rfc-editor.org/authors/rfc9860.xml The relevant diff files have been posted here: https://www.rfc-editor.org/authors/rfc9860-auth48diff.html (AUTH48 changes only) https://www.rfc-editor.org/authors/rfc9860-auth48rfcdiff.html (AUTH 48 changes side by side) https://www.rfc-editor.org/authors/rfc9860-diff.html (all changes) https://www.rfc-editor.org/authors/rfc9860-rfcdiff.html (all changes side by side) Thank you, Kaelin Foody RFC Production Center > On Sep 16, 2025, at 11:44AM, linchangwang wrote: > > Hi Kaelin & Alanna, > > Thanks for your help with this document. > Please check inline below for responses. > > Thanks, > Changwang (on behalf of co-authors) > > > > 发件人: [email protected] > 发送时间: 2025年9月16日 5:57 > 收件人: [email protected] [email protected] > [email protected] [email protected] linchangwang (RD) > 抄送: [email protected] [email protected] [email protected] > [email protected] [email protected] [email protected] > 主题: Re: AUTH48: RFC-to-be 9860 for your review > > > Authors, > > While reviewing this document during AUTH48, please resolve (as necessary) > the following questions, which are also in the source file. > > 1) > > Changwang > I would like it alphabetized. > > > 2) > > Changwang > PIM、MoFRR、LFA、TI-LFA、SR-MPLS、SRv6、RPF Vector、Join attribute > > 3) > Changwang > Ack > > > 4) > Changwang > Ack > > 5) > Changwang > Use "Node SID" and " segment list ". > > > 6) > Changwang > ACK > > > 7) > Changwang> This mechanism is applicable to PIM networks, including cases > where PIM > operates directly over IP in Segment Routing (SR) networks. > > > b) In addition, please consider whether "tradition" should be updated for > clarity. > While the NIST website > > indicates that this term is potentially biased, it is also ambiguous. > "Tradition" is a subjective term, as it is not the same for everyone: > > However, the traditional LFA does not function properly for the secondary > path because the shortest path to R2 from R5 (or from R4) still traverses > the R6-R2 link. > --> > > Changwang > However, the conventional LFA does not function properly for the > secondary > path because the shortest path to R2 from R5 (or from R4) still traverses > the R6-R2 link. > > > Thank you. > > Kaelin Foody and Alanna Paloma > RFC Production Center > > > On Sep 15, 2025, at 2:55PM, [email protected] wrote: > > *****IMPORTANT***** > > Updated 2025/09/15 > > RFC Author(s): > -------------- > > Instructions for Completing AUTH48 > > Your document has now entered AUTH48. Once it has been reviewed and approved > by you and all coauthors, it will be published as an RFC. > If an author is no longer available, there are several remedies available as > listed in the FAQ (https://www.rfc-editor.org/faq/). > > You and you coauthors are responsible for engaging other parties (e.g., > Contributors or Working Group) as necessary before providing your approval. > > Planning your review > --------------------- > > Please review the following aspects of your document: > > * RFC Editor questions > > Please review and resolve any questions raised by the RFC Editor > that have been included in the XML file as comments marked as > follows: > > > > These questions will also be sent in a subsequent email. > > * Changes submitted by coauthors > > Please ensure that you review any changes submitted by your > coauthors. We assume that if you do not speak up that you > agree to changes submitted by your coauthors. > > * Content > > Please review the full content of the document, as this cannot > change once the RFC is published. Please pay particular attention to: > - IANA considerations updates (if applicable) > - contact information > - references > > * Copyright notices and legends > > Please review the copyright notice and legends as defined in > RFC 5378 and the Trust Legal Provisions > (TLP – https://trustee.ietf.org/license-info). > > * Semantic markup > > Please review the markup in the XML file to ensure that elements of > content are correctly tagged. For example, ensure that > and are set correctly. See details at > . > > * Formatted output > > Please review the PDF, HTML, and TXT files to ensure that the > formatted output, as generated from the markup in the XML file, is > reasonable. Please note that the TXT will have formatting > limitations compared to the PDF and HTML. > > > Submitting changes > ------------------ > > To submit changes, please reply to this email using ‘REPLY ALL’ as all the > parties CCed on this message need to see your changes. The parties > include: > > * your coauthors > > * [email protected] (the RPC team) > > * other document participants, depending on the stream (e.g., > IETF Stream participants are your working group chairs, the > responsible ADs, and the document shepherd). > > * [email protected], which is a new archival mailing list > to preserve AUTH48 conversations it is not an active discussion > list: > > * More info: > https://mailarchive.ietf.org/arch/msg/ietf-announce/yb6lpIGh-4Q9l2USxIAe6P8O4Zc > > * The archive itself: > https://mailarchive.ietf.org/arch/browse/auth48archive/ > > * Note: If only absolutely necessary, you may temporarily opt out > of the archiving of messages (e.g., to discuss a sensitive matter). > If needed, please add a note at the top of the message that you > have dropped the address. When the discussion is concluded, > [email protected] will be re-added to the CC list and > its addition will be noted at the top of the message. > > You may submit your changes in one of two ways: > > An update to the provided XML file > — OR — > An explicit list of changes in this format > > Section # (or indicate Global) > > OLD: > old text > > NEW: > new text > > You do not need to reply with both an updated XML file and an explicit list > of changes, as either form is sufficient. > > We will ask a stream manager to review and approve any changes that seem > beyond editorial in nature, e.g., addition of new text, deletion of text, and > technical changes. Information about stream managers can be found in the FAQ. > Editorial changes do not require approval from a stream manager. > > > Approving for publication > -------------------------- > > To approve your RFC for publication, please reply to this email stating that > you approve this RFC for publication. Please use ‘REPLY ALL’, as all the > parties CCed on this message need to see your approval. > > > Files > ----- > > The files are available here: > https://www.rfc-editor.org/authors/rfc9860.xml > https://www.rfc-editor.org/authors/rfc9860.html > https://www.rfc-editor.org/authors/rfc9860.pdf > https://www.rfc-editor.org/authors/rfc9860.txt > > Diff file of the text: > https://www.rfc-editor.org/authors/rfc9860-diff.html > https://www.rfc-editor.org/authors/rfc9860-rfcdiff.html (side by side) > > Diff of the XML: > https://www.rfc-editor.org/authors/rfc9860-xmldiff1.html > > > Tracking progress > ----------------- > > The details of the AUTH48 status of your document are here: > https://www.rfc-editor.org/auth48/rfc9860 > > Please let us know if you have any questions. > > Thank you for your cooperation, > > RFC Editor > > -------------------------------------- > RFC9860 (draft-ietf-pim-mofrr-tilfa-14) > > Title : Multicast-only Fast Reroute Based on Topology Independent Loop-free > Alternate (TI-LFA) Fast Reroute > Author(s) : Y. Liu, M. McBride, Z. Zhang, J. Xie, C. Lin > WG Chair(s) : Stig Venaas, Mike McBride > > Area Director(s) : Jim Guichard, Ketan Talaulikar, Gunter Van de Velde > > > ------------------------------------------------------------------------------------------------------------------------------------- > 本邮件及其附件含有新华三集团的保密信息，仅限于发送给上面地址中列出 > 的个人或群组。禁止任何其他人以任何形式使用（包括但不限于全部或部分地泄露、复制、 > 或散发）本邮件中的信息。如果您错收了本邮件，请您立即电话或邮件通知发件人并删除本 > 邮件！ > 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!
-- auth48archive mailing list -- [email protected] To unsubscribe send an email to [email protected]
