Authors, While reviewing this document during AUTH48, please resolve (as necessary) the following questions, which are also in the XML file.
1) <!--[rfced] Regarding the term "UTF8-quoted": We note this term was also used in RFC 6855, which is the only RFC where this term has appeared in this form. Does it refer to the ABNF rule 'utf8-quoted' as defined in RFC 5738 (which is obsolete), or to another concept? Should it be replaced with 'utf8-quoted' or should the concept be written in prose? Original: All IMAP servers that support "UTF8=ACCEPT" SHOULD accept UTF-8 in mailbox names, and those that also support the Mailbox International Naming Convention described in RFC 3501, Section 5.1.3, MUST accept UTF8-quoted mailbox names and convert them to the appropriate internal format. --> 2) <!-- [rfced] There is one Verified Technical errata report for RFC 6855: https://www.rfc-editor.org/errata/eid4029 This document contains the old text from Section 3 mentioned in that report. Please review whether any updates are needed for this document. --> 3) <!--[rfced] Here, does "UTF8-related" mean related to the UTF8 data item or related to the UTF-8 character encoding? If the former, may the sentence be updated as follows? Original: This document removes APPEND's UTF8 data item, making the UTF8-related syntax compatible with IMAP4rev2 ... Perhaps: This document removes APPEND's UTF8 data item, making the syntax related to that data item compatible with IMAP4rev2 ... --> 4) <!--[rfced] Please clarify the "/" in "IMAP4rev1/2" here. Is the intended meaning "and" or "or" or otherwise? Original: As of today, an IMAP client cannot learn whether a particular message was stored using the UTF8 data item, nor would it be able to trust that information even if IMAP4rev1/2 were extended to provide that information. Perhaps: ... even if IMAP4rev1 and 2 were extended to provide that information. --> 5) <!--[rfced] In general in RFCs, the term "MIME type" should be "media type". Please review whether these updates convey the intended meaning. a new MIME type -> a new media type the MIME structure of a message -> the media type of the body of a message --> 6) <!--[rfced] Pete, would you like to provide an abbreviated organization name, which would appear in the first-page header? This is optional. Current: Internet Engineering Task Force (IETF) P. Resnick Request for Comments: 9755 Episteme Technology Consulting LLC Obsoletes: 6855 J. Yao Category: Standards Track CNNIC ISSN: 2070-1721 A. Gulbrandsen ICANN February 2025 --> 7) <!-- [rfced] Please review the "Inclusive Language" portion of the online Style Guide <https://www.rfc-editor.org/styleguide/part2/#inclusive_language> and let us know if any changes are needed. Updates of this nature typically result in more precise language, which is helpful for readers. Note that our script did not flag any words in particular, but this should still be reviewed as a best practice. --> Thank you. RFC Editor/ar On Feb 9, 2025, rfc-edi...@rfc-editor.org wrote: *****IMPORTANT***** Updated 2025/02/09 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/rfc9755.xml https://www.rfc-editor.org/authors/rfc9755.html https://www.rfc-editor.org/authors/rfc9755.pdf https://www.rfc-editor.org/authors/rfc9755.txt Diff file of the text: https://www.rfc-editor.org/authors/rfc9755-diff.html https://www.rfc-editor.org/authors/rfc9755-rfcdiff.html (side by side) Diff of the XML: https://www.rfc-editor.org/authors/rfc9755-xmldiff1.html Tracking progress ----------------- The details of the AUTH48 status of your document are here: https://www.rfc-editor.org/auth48/rfc9755 Please let us know if you have any questions. Thank you for your cooperation, RFC Editor -------------------------------------- RFC9755 (draft-ietf-extra-6855bis-04) Title : IMAP Support for UTF-8 Author(s) : P. Resnick, J. Yao, A. Gulbrandsen WG Chair(s) : Jiankang Yao, Bron Gondwana Area Director(s) : Murray Kucherawy, Orie Steele -- auth48archive mailing list -- auth48archive@rfc-editor.org To unsubscribe send an email to auth48archive-le...@rfc-editor.org
