Hi Hyunsik, I'm doing well and hope you are too.
Thank you for your reply. Sincerely, Sarah Tarrant RFC Production Center > On Jan 21, 2026, at 8:44 AM, Hyunsik Yang <[email protected]> > wrote: > > Hello Sarah, > How are you? > > You can see my comments below. > > Thanks. > Best regards, > > -----Original Message----- > From: Sarah Tarrant <[email protected]> > Sent: Tuesday, January 20, 2026 5:16 PM > To: Hyunsik Yang <[email protected]>; Xavier De Foy > <[email protected]> > Cc: [email protected]; [email protected]; > [email protected] > Subject: Document intake questions about <draft-ietf-avtcore-rtp-haptics-13> > > Author(s), > > Congratulations, your document has been successfully added to the RFC Editor > queue! > The team at the RFC Production Center (RPC) is looking forward to working > with you as your document moves forward toward publication. To help reduce > processing time and improve editing accuracy, please respond to the questions > below. Please confer with your coauthors (or authors of other documents if > your document is in a > cluster) as necessary prior to taking action in order to streamline > communication. > If your document has multiple authors, only one author needs to reply to this > message. > > As you read through the rest of this email: > > * If you need/want to make updates to your document, we encourage you to make > those changes and resubmit to the Datatracker. This allows for the easy > creation of diffs, which facilitates review by interested parties (e.g., > authors, ADs, doc shepherds). > * If you feel no updates to the document are necessary, please reply with any > applicable rationale/comments. > > > Please note that the RPC team will not work on your document until we hear > from you (that is, your document will remain in AUTH state until we receive a > reply). Even if you don't have guidance or don't feel that you need to make > any updates to the document, you need to let us know. After we hear from you, > your document will start moving through the queue. You will be able to review > and approve our updates during AUTH48. > > Please feel free to contact us with any questions you may have at > [email protected]. > > Thank you! > The RPC Team > > -- > > 1) As there may have been multiple updates made to the document during Last > Call, please review the current version of the document: > > * Is the text in the Abstract still accurate? > * Are the Authors' Addresses, Contributors, and Acknowledgments sections > current? > > > [HY] Yes, all the information is up to date. > > 2) Please share any style information that could help us with editing your > document. For example: > > * Is your document's format or its terminology based on another document? > If so, please provide a pointer to that document (e.g., this document's > terminology should match DNS terminology in RFC 9499). > * Is there a pattern of capitalization or formatting of terms? (e.g., field > names > should have initial capitalization; parameter names should be in double > quotes; > <tt/> should be used for token names; etc.) > > [HY] > This document is based on the MPEG Haptics specification (ISO/IEC 23090-31). > No special rules have been defined. > If you need a copy of ISO/IEC 23090-31, please contact Stephan Wenger > [email protected], who is IETF/MPEG liaison officer and can make a copy > available to IETF reviewers. > > 3) Please review the entries in the References section carefully with > the following in mind. Note that we will update as follows unless we > hear otherwise at this time: > > * References to obsoleted RFCs will be updated to point to the current > RFC on the topic in accordance with Section 4.8.6 of RFC 7322 > (RFC Style Guide). > > * References to I-Ds that have been replaced by another I-D will be > updated to point to the replacement I-D. > > * References to documents from other organizations that have been > superseded will be updated to their superseding version. > > Note: To check for outdated RFC and I-D references, you can use > idnits <https://author-tools.ietf.org/idnits>. You can also help the > IETF Tools Team by testing idnits3 <https://author-tools.ietf.org/idnits3/> > with your document and reporting any issues to them. > > [HY] We used the two checking tools to check revision -13 and got no issue, > other than the copyright year that needs to be updated. We did not get any > issue when running the checks against a new (unpublished) test revision. > > 4) Is there any text that requires special handling? For example: > *Are there any sections that were contentious when the document was drafted? > *Are any sections that need to be removed before publication marked as such > (e.g., Implementation Status sections (per RFC 7942)). > *Are there any instances of repeated text/sections that should be edited > the same way? > > [HY] There is nothing in particular. > > 5) This document contains SVG. What tool did you use to make the svg? > > The RPC cannot update SVG diagrams, so please ensure that: > > * the SVG figures match the ASCII art used in the text output as closely as > possible, and > * the figures fit on the pages of the PDF output. > > [HY] The SVG was created using options within the Markdown file and get XML > file in the web tool https://author-tools.ietf.org/. > > 6) Would you like to participate in the RPC Pilot Test for editing in > kramdown-rfc? > If so, please let us know and provide a self-contained kramdown-rfc file. For > more > information about this experiment, see: > https://www.rfc-editor.org/rpc/wiki/doku.php?id=pilot_test_kramdown_rfc. > > [HY] Yes. The existing document has already been written in an MD file. I > have attached the file. > > 7) Is there anything else that the RPC should be aware of while editing this > document? > > [HY] Nothing comes to mind at this time. > >> On Jan 20, 2026, at 4:09 PM, [email protected] wrote: >> >> Author(s), >> >> Your document draft-ietf-avtcore-rtp-haptics-13, which has been approved for >> publication as >> an RFC, has been added to the RFC Editor queue >> <https://www.rfc-editor.org/current_queue.php>. >> >> If your XML file was submitted using the I-D submission tool >> <https://datatracker.ietf.org/submit/>, we have already retrieved it >> and have started working on it. >> >> If you did not submit the file via the I-D submission tool, or >> if you have an updated version (e.g., updated contact information), >> please send us the file at this time by attaching it >> in your reply to this message and specifying any differences >> between the approved I-D and the file that you are providing. >> >> You will receive a separate message from us asking for style input. >> Please respond to that message. When we have received your response, >> your document will then move through the queue. The first step that >> we take as your document moves through the queue is converting it to >> RFCXML (if it is not already in RFCXML) and applying the formatting >> steps listed at <https://www.rfc-editor.org/pubprocess/how-we-update/>. >> Next, we will edit for clarity and apply the style guide >> (<https://www.rfc-editor.org/styleguide/>). >> >> You can check the status of your document at >> <https://www.rfc-editor.org/current_queue.php>. >> >> You will receive automatic notifications as your document changes >> queue state (for more information about these states, please see >> <https://www.rfc-editor.org/about/queue/>). When we have completed >> our edits, we will move your document to AUTH48 state and ask you >> to perform a final review of the document. >> >> Please let us know if you have any questions. >> >> Thank you. >> >> The RFC Editor Team >> > > [Banner] > > [Banner]<https://www.interdigital.com/white_papers/streaming-live-sports-where-opportunity-meets-complexity?utm_source=signature&utm_medium=banner&utm_campaign=video> > > Streaming Live Sports: Where Opportunity Meets > Complexity<https://www.interdigital.com/white_papers/streaming-live-sports-where-opportunity-meets-complexity?utm_source=signature&utm_medium=banner&utm_campaign=video> > This e-mail is intended only for the use of the individual or entity to which > it is addressed, and may contain information that is privileged, confidential > and/or otherwise protected from disclosure to anyone other than its intended > recipient. Unintended transmission shall not constitute waiver of any > privilege or confidentiality obligation. If you received this communication > in error, please do not review, copy or distribute it, notify me immediately > by email, and delete the original message and any attachments. Unless > expressly stated in this e-mail, nothing in this message or any attachment > should be construed as a digital or electronic signature. > <draft-ietf-avtcore-rtp-haptics-13.md> -- auth48archive mailing list -- [email protected] To unsubscribe send an email to [email protected]
