Hi Sandy, Thank you for your quick reply! We have noted your approval on the AUTH48 status page (please see https://www.rfc-editor.org/auth48/rfc9719).
Once we receive approvals from all parties listed on the AUTH48 status page (as well as a response to our queries), we will move this document forward in the publication process. Thank you! RFC Editor/mc > On Jan 16, 2025, at 12:26 AM, <zhang.zh...@zte.com.cn> > <zhang.zh...@zte.com.cn> wrote: > > Hi, > Sorry, just found that the "Acknowledgement" section was moved to the end of > the document. > I am OK with that. > Thank you！ > Best regards, > Sandy > > Original > From: 张征00007940 > To: rfc-edi...@rfc-editor.org <rfc-edi...@rfc-editor.org>; > Cc: 魏月华00019655;mashao...@gmail.com > <mashao...@gmail.com>;xufeng.liu.i...@gmail.com > <xufeng.liu.i...@gmail.com>;brunorijs...@gmail.com > <brunorijs...@gmail.com>;rfc-edi...@rfc-editor.org > <rfc-edi...@rfc-editor.org>;rift-...@ietf.org > <rift-...@ietf.org>;rift-cha...@ietf.org > <rift-cha...@ietf.org>;jh...@juniper.net > <jh...@juniper.net>;james.n.guich...@futurewei.com > <james.n.guich...@futurewei.com>;auth48archive@rfc-editor.org > <auth48archive@rfc-editor.org>; > Date: 2025年01月16日 11:22 > Subject: Re: AUTH48: RFC-to-be 9719 <draft-ietf-rift-yang-17> for your review > Hi, > thank you very much for your work! > I agree with the revision and approve it. > BTW: "Acknowledgement" seems to be missing in the revised version, is it > deleted by mistake or for some other reason? > Thank you! > Best regards, > Sandy > > > > From: rfc-edi...@rfc-editor.org <rfc-edi...@rfc-editor.org> > To: 张征00007940;魏月华00019655;mashao...@gmail.com > <mashao...@gmail.com>;xufeng.liu.i...@gmail.com > <xufeng.liu.i...@gmail.com>;brunorijs...@gmail.com <brunorijs...@gmail.com>; > Cc: rfc-edi...@rfc-editor.org <rfc-edi...@rfc-editor.org>;rift-...@ietf.org > <rift-...@ietf.org>;rift-cha...@ietf.org > <rift-cha...@ietf.org>;jh...@juniper.net > <jh...@juniper.net>;james.n.guich...@futurewei.com > <james.n.guich...@futurewei.com>;auth48archive@rfc-editor.org > <auth48archive@rfc-editor.org>; > Date: 2025年01月16日 10:13 > Subject: AUTH48: RFC-to-be 9719 <draft-ietf-rift-yang-17> for your > review*****IMPORTANT***** > > Updated 2025/01/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: > > <!-- [rfced] ... --> > > 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 <sourcecode> > and <artwork> are set correctly. See details at > <https://authors.ietf.org/rfcxml-vocabulary>. > > * 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 > > * rfc-edi...@rfc-editor.org (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). > > * auth48archive@rfc-editor.org, 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, > auth48archive@rfc-editor.org 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/rfc9719.xml > https://www.rfc-editor.org/authors/rfc9719.html > https://www.rfc-editor.org/authors/rfc9719.pdf > https://www.rfc-editor.org/authors/rfc9719.txt > > Diff file of the text: > https://www.rfc-editor.org/authors/rfc9719-diff.html > https://www.rfc-editor.org/authors/rfc9719-rfcdiff.html (side by side) > > Diff of the XML: > https://www.rfc-editor.org/authors/rfc9719-xmldiff1.html > > > Tracking progress > ----------------- > > The details of the AUTH48 status of your document are here: > https://www.rfc-editor.org/auth48/rfc9719 > > Please let us know if you have any questions. > > Thank you for your cooperation, > > RFC Editor > > -------------------------------------- > RFC9719 (draft-ietf-rift-yang-17) > > Title : YANG Data Model for Routing in Fat Trees (RIFT) > Author(s) : Z. Zhang, Y. Wei, S. Ma, X. Liu, B. Rijsman > WG Chair(s) : Zhaohui (Jeffrey) Zhang, Jeff Tantsura > Area Director(s) : Jim Guichard, John Scudder, Gunter Van de Velde > -- auth48archive mailing list -- auth48archive@rfc-editor.org To unsubscribe send an email to auth48archive-le...@rfc-editor.org
