Authors' Final Review (AUTH48)


AUTH48 is the last chance to make changes to an RFC-to-be. Once the document is published as an RFC, we will not make changes. The general instructions for completing AUTH48 is described below; they are similar to what you will receive via email when your document enters AUTH48 state. If your document is in AUTH48 state, we recommend referring to the email you received.

  • Instructions for Completing AUTH48 (no XML file)
  • Instructions for Completing AUTH48 in XML
  • Additional resources:


    AUTH48

    1. Review the edited document completely. The files are available here:
      • http://www.rfc-editor.org/authors/rfcXXXX.txt
      • http://www.rfc-editor.org/authors/rfcXXXX-diff.html
      • where XXXX is the number assigned to your RFC-to-be.

    2. Review and resolve (as necessary) any questions raised by the RFC Editor. The questions (if any) will be sent in a subsequent AUTH48 email.
    3. Send us your changes or respond with your approval for publication. Please use 'REPLY ALL' so that rfc-editor@rfc-editor.org and the parties CC'ed on this message receive your response. Note that your document will not move forward until we have received approvals from each of the authors listed on the front page.

      If sending changes, please provide us with an explicit list of changes via email. Please send the changes in this format:

         Section # (or indicate Global)
      
            OLD:
            old text
         
            NEW:
            new text
      

      Be sure to pay particular attention to these areas of the document:

      • IANA Considerations updates (if applicable)
      • Contact information
      • Copyright notice and legends (see item 6 for more details)

    4. Send a list of suitable keywords for this document (beyond those that appear in the title) for use on http://www.rfc-editor.org/search/rfc_search.php .
    5. Before or after you send your approval of the document as a whole, there may be changes sent by your coauthors. Assuming you have already sent us your approval of the document, it still stands unless you notify us otherwise. Note that any changes that are beyond editorial will be sent to the relevant body for approval.
    6. Review the copyright notice and legends as defined in RFC 5378 and the Trust Legal Provisions (TLP - http://trustee.ietf.org/license-info/).

      If your document was approved for publication with a pre-RFC-5378 copyright notice, we have applied the text from section 6.c.iii of the TLP. Please consider whether this text is required (note that the 6.c.iii text is not applicable to Alternate Stream RFCs). See item 4.5 of the "Copyright FAQ" at http://trustee.ietf.org/faqs.html for guidance on whether this text applies to your document.

    7. Please reply, as the document will not be published until we receive approvals from each author. The details of the AUTH48 status of your document are here:
        http://www.rfc-editor.org/auth48/rfcXXXX

    AUTH48 in XML

    1. Review the edited document completely. The files are available here:
      • http://www.rfc-editor.org/authors/rfcXXXX.txt
      • http://www.rfc-editor.org/authors/rfcXXXX-diff.html
      • where XXXX is the number assigned to your RFC-to-be.

      We recommend reviewing the entire document, not just the diff file. FYI, http://tools.ietf.org/rfcdiff provides tools to make various kinds of diff files.

      If you submitted an XML file, page breaks will be handled during the final stages of publication (typically post-xml2rfc processing).

    2. Review and resolve (as necessary) any questions raised by the RFC Editor. The questions (if any) have been included in the XML file as comments marked <!-- [rfced] ... --> and will be sent in a subsequent email.

      Retrieve the edited XML file here:

        http://www.rfc-editor.org/authors/rfcXXXX.xml

      Note that you may need to view the page source to save the file.

    3. Send us your changes or respond with your approval for publication. Please use 'REPLY ALL' so that the RFC Editor and the parties CC'ed on the message receive your response. Note that your document will not move forward until we have received approvals from each of the authors listed on the front page.

      If sending changes, please do one of the following:

        a. Update the provided XML file, then email us the revised XML file. You may use any filename for the revised file; we will rename it before posting it.
      -- OR --
        b. Provide us with an explicit list of changes in this format.
         Section # (or indicate Global)
        
             OLD:
             old text 
        
             NEW:
             new text  
             

      Be sure to pay particular attention to these areas of the document:

      • IANA Considerations updates (if applicable)
      • Contact information
      • Copyright notice and legends (see item 5 for more details)

    4. Before or after you send your approval of the document as a whole, there may be changes sent by your coauthors. Assuming you have already sent us your approval of the document, it still stands unless you notify us otherwise. Note that any changes that are beyond editorial will be sent to the relevant body for approval.
    5. Review the copyright notice and legends as defined in RFC 5378 and the Trust Legal Provisions (TLP - http://trustee.ietf.org/license-info/).

      If your document was approved for publication with a pre-RFC-5378 copyright notice, we have applied the text from section 6.c.iii of the TLP. Please consider whether this text is required (note that the 6.c.iii text is not applicable to Alternate Stream RFCs). See item 4.5 of the "Copyright FAQ" at http://trustee.ietf.org/faqs.html for guidance on whether this text applies to your document.

    6. Please reply, as the document will not be published until we receive approvals from each author. The details of the AUTH48 status of your document are here:
        http://www.rfc-editor.org/auth48/rfcXXXX