Hi Yunbin, Thank you for your reply. We have marked your approval on the AUTH48 status page for this document (see https://www.rfc-editor.org/auth48/rfc9730).
We will await approvals from the remaining parties listed at the AUTH48 status page prior to moving this document forward in the publication process. Thank you, RFC Editor/st > On Feb 19, 2025, at 7:03 PM, xuyun...@caict.ac.cn > <xuyunbin=40caict.ac...@dmarc.ietf.org> wrote: > > Dear RFC editors, > > As one of the authors, I approve the publication of this draft. Please also > mark my approval on the AUTH48 status page. > > Thanks > > -------------------------------------------------------------------------------- > Yunbin Xu 徐云斌 宽带网络研究部 > 中国信息通信研究院（工业与信息化部电信研究院）技术与标准研究所 > Research Institute of Telecommunications Transmission (RITT), > China Academy of Information Communications Technology(CAICT), MIIT > TEL: 86-18601328841，86-10-62300112 > E-mail: xuyun...@caict.ac.cn -------------------------------------- > From: rfc-editor > Date: 2025-01-30 07:06 > To: zhenghaomian; xuyunbin; zhaoyangyjy; Dieter.Beller; yi.lin > CC: rfc-editor; teas-ads; teas-chairs; vbeeram; james.n.guichard; > auth48archive > Subject: AUTH48: RFC-to-be 9730 > <draft-ietf-teas-gmpls-controller-inter-work-17> for your review > *****IMPORTANT***** > Updated 2025/01/29 > 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/rfc9730.xml > https://www.rfc-editor.org/authors/rfc9730.html > https://www.rfc-editor.org/authors/rfc9730.pdf > https://www.rfc-editor.org/authors/rfc9730.txt > Diff file of the text: > https://www.rfc-editor.org/authors/rfc9730-diff.html > https://www.rfc-editor.org/authors/rfc9730-rfcdiff.html (side by side) > Diff of the XML: https://www.rfc-editor.org/authors/rfc9730-xmldiff1.html > Tracking progress > ----------------- > The details of the AUTH48 status of your document are here: > https://www.rfc-editor.org/auth48/rfc9730 > Please let us know if you have any questions. Thank you for your > cooperation, > RFC Editor > -------------------------------------- > RFC9730 (draft-ietf-teas-gmpls-controller-inter-work-17) > Title : Interworking of GMPLS Control and Centralized Controller > Systems > Author(s) : H. Zheng, Y. Xu, Y. Zhao, D. Beller, Y. Lin > WG Chair(s) : Oscar Gonzalez de Dios, Vishnu Pavan Beeram, Lou Berger > 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
