[rfc-i] Fwd: New Version Notification for draft-iab-rfc-nonascii-02.txt

[rse at rfc-editor.org (Heather Flanagan (RFC Series Editor))]

A revised draft has been posted. I believe this incorporates the final
comments received during the community comment period.

Thanks for your input!

Heather Flanagan


-------- Forwarded Message --------
Subject: 	New Version Notification for draft-iab-rfc-nonascii-02.txt
Date: 	Wed, 27 Apr 2016 09:06:26 -0700
From: 	internet-drafts at ietf.org
To: 	Heather Flanagan <rse at rfc-editor.org>



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:            https://www.ietf.org/internet-drafts/draft-iab-rfc-nonascii-02.txt
Status:         https://datatracker.ietf.org/doc/draft-iab-rfc-nonascii/
Htmlized:       https://tools.ietf.org/html/draft-iab-rfc-nonascii-02
Diff:           https://www.ietf.org/rfcdiff?url2=draft-iab-rfc-nonascii-02

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

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.rfc-editor.org/pipermail/rfc-interest/attachments/20160427/4d584824/attachment.html>