RFC 5242 on A Generalized Unified Character Code: Western European and CJK Sections
rfc-editor@rfc-editor.org Tue, 01 April 2008 16:58 UTC
Return-Path: <ietf-announce-bounces@ietf.org>
X-Original-To: ietf-announce-archive@megatron.ietf.org
Delivered-To: ietfarch-ietf-announce-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B4F3328C158; Tue, 1 Apr 2008 09:58:12 -0700 (PDT)
X-Original-To: ietf-announce@core3.amsl.com
Delivered-To: ietf-announce@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 093DC28C4CD for <ietf-announce@core3.amsl.com>; Tue, 1 Apr 2008 09:58:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -16.997
X-Spam-Level:
X-Spam-Status: No, score=-16.997 tagged_above=-999 required=5 tests=[AWL=0.602, BAYES_00=-2.599, USER_IN_DEF_WHITELIST=-15]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5WXbsa2PWXtJ for <ietf-announce@core3.amsl.com>; Tue, 1 Apr 2008 09:58:09 -0700 (PDT)
Received: from bosco.isi.edu (bosco.isi.edu [128.9.168.207]) by core3.amsl.com (Postfix) with ESMTP id 1518028C29E for <ietf-announce@ietf.org>; Tue, 1 Apr 2008 09:58:09 -0700 (PDT)
Received: by bosco.isi.edu (Postfix, from userid 70) id 16F38121FAE; Tue, 1 Apr 2008 09:58:08 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 5242 on A Generalized Unified Character Code: Western European and CJK Sections
From: rfc-editor@rfc-editor.org
Message-Id: <20080401165808.16F38121FAE@bosco.isi.edu>
Date: Tue, 01 Apr 2008 09:58:08 -0700
Cc: rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF Announcements <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ietf-announce-bounces@ietf.org
Errors-To: ietf-announce-bounces@ietf.org
A new Request for Comments is now available in online RFC libraries.
RFC 5242
Title: A Generalized Unified Character Code:
Western European and CJK Sections
Author: J. Klensin, H. Alvestrand
Status: Informational
Date: 1 April 2008
Mailbox: john+ietf@jck.com,
harald@alvestrand.no
Pages: 14
Characters: 31314
Updates/Obsoletes/SeeAlso: None
URL: http://www.rfc-editor.org/rfc/rfc5242.txt
Many issues have been identified with the use of general-purpose
character sets for internationalized domain names and similar
purposes. This memo describes a fully unified coded character set
for scripts based on Latin, Greek, Cyrillic, and Chinese (CJK)
characters. It is not a complete specification of that character
set. This memo provides information for the Internet community.
INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution of
this memo is unlimited.
This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@IETF.ORG. Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.
Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body
help: ways_to_get_rfcs. For example:
To: rfc-info@RFC-EDITOR.ORG
Subject: getting rfcs
help: ways_to_get_rfcs
Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC
Authors, for further information.
The RFC Editor Team
USC/Information Sciences Institute
...
_______________________________________________
IETF-Announce mailing list
IETF-Announce@ietf.org
https://www.ietf.org/mailman/listinfo/ietf-announce