<html>
  <head>

    <meta http-equiv="content-type" content="text/html; charset=utf-8">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <p>A revised draft has been posted. I believe this incorporates the
      final comments received during the community comment period.</p>
    <p>Thanks for your input!</p>
    <p>Heather Flanagan<br>
    </p>
    <div class="moz-forward-container"><br>
      -------- Forwarded Message --------
      <table class="moz-email-headers-table" border="0" cellpadding="0"
        cellspacing="0">
        <tbody>
          <tr>
            <th align="RIGHT" valign="BASELINE" nowrap="nowrap">Subject:
            </th>
            <td>New Version Notification for
              draft-iab-rfc-nonascii-02.txt</td>
          </tr>
          <tr>
            <th align="RIGHT" valign="BASELINE" nowrap="nowrap">Date: </th>
            <td>Wed, 27 Apr 2016 09:06:26 -0700</td>
          </tr>
          <tr>
            <th align="RIGHT" valign="BASELINE" nowrap="nowrap">From: </th>
            <td><a class="moz-txt-link-abbreviated" href="mailto:internet-drafts@ietf.org">internet-drafts@ietf.org</a></td>
          </tr>
          <tr>
            <th align="RIGHT" valign="BASELINE" nowrap="nowrap">To: </th>
            <td>Heather Flanagan <a class="moz-txt-link-rfc2396E" href="mailto:rse@rfc-editor.org"><rse@rfc-editor.org></a></td>
          </tr>
        </tbody>
      </table>
      <br>
      <br>
      <pre>A new version of I-D, draft-iab-rfc-nonascii-02.txt
has been successfully submitted by Heather Flanagan and posted to the
IETF repository.

Name:           draft-iab-rfc-nonascii
Revision:       02
Title:          The Use of Non-ASCII Characters in RFCs
Document date:  2016-04-25
Group:          Individual Submission
Pages:          14
URL:            <a class="moz-txt-link-freetext" href="https://www.ietf.org/internet-drafts/draft-iab-rfc-nonascii-02.txt">https://www.ietf.org/internet-drafts/draft-iab-rfc-nonascii-02.txt</a>
Status:         <a class="moz-txt-link-freetext" href="https://datatracker.ietf.org/doc/draft-iab-rfc-nonascii/">https://datatracker.ietf.org/doc/draft-iab-rfc-nonascii/</a>
Htmlized:       <a class="moz-txt-link-freetext" href="https://tools.ietf.org/html/draft-iab-rfc-nonascii-02">https://tools.ietf.org/html/draft-iab-rfc-nonascii-02</a>
Diff:           <a class="moz-txt-link-freetext" href="https://www.ietf.org/rfcdiff?url2=draft-iab-rfc-nonascii-02">https://www.ietf.org/rfcdiff?url2=draft-iab-rfc-nonascii-02</a>

Abstract:
   In order to support the internationalization of protocols and a more
   diverse Internet community, the RFC Series must evolve to allow for
   the use of non-ASCII characters in RFCs.  While English remains the
   required language of the Series, the encoding of future RFCs will be
   in UTF-8, allowing for a broader range of characters than typically
   used in the English language.  This document describes the RFC Editor
   requirements and guidance regarding the use of non-ASCII characters
   in RFCs.

   This document updates RFC 7322.  Please review the PDF version of
   this draft.

                                                                                  


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

The IETF Secretariat

</pre>
    </div>
  </body>
</html>