RFC 4790 on Internet Application Protocol Collation Registry

rfc-editor@rfc-editor.org Thu, 15 March 2007 21:51 UTC

Return-path: <ietf-announce-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HRxr2-00017i-Ox; Thu, 15 Mar 2007 17:51:24 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HRxr1-00017c-55 for ietf-announce@ietf.org; Thu, 15 Mar 2007 17:51:23 -0400
Received: from nit.isi.edu ([128.9.160.116]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HRxqz-0006gF-Pi for ietf-announce@ietf.org; Thu, 15 Mar 2007 17:51:23 -0400
Received: from nit.isi.edu (loopback [127.0.0.1]) by nit.isi.edu (8.12.11.20060308/8.12.11) with ESMTP id l2FLpIHO009949; Thu, 15 Mar 2007 13:51:18 -0800
Received: (from apache@localhost) by nit.isi.edu (8.12.11.20060308/8.12.11/Submit) id l2FLpIuM009948; Thu, 15 Mar 2007 14:51:18 -0700
Date: Thu, 15 Mar 2007 14:51:18 -0700
Message-Id: <200703152151.l2FLpIuM009948@nit.isi.edu>
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
X-Spam-Score: -14.8 (--------------)
X-Scan-Signature: fb6060cb60c0cea16e3f7219e40a0a81
Cc: rfc-editor@rfc-editor.org
Subject: RFC 4790 on Internet Application Protocol Collation Registry
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: ietf-announce.ietf.org
List-Unsubscribe: <https://www1.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://www1.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
Errors-To: ietf-announce-bounces@ietf.org

A new Request for Comments is now available in online RFC libraries.

        
        RFC 4790

        Title:      Internet Application Protocol Collation Registry 
        Author:     C. Newman, M. Duerst,
                    A. Gulbrandsen
        Status:     Standards Track
        Date:       March 2007
        Mailbox:    chris.newman@sun.com, 
                    duerst@it.aoyama.ac.jp,
                    arnt@oryx.com
        Pages:      26
        Characters: 55591
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-newman-i18n-comparator-14.txt

        URL:        http://www.rfc-editor.org/rfc/rfc4790.txt

Many Internet application protocols include string-based lookup,
searching, or sorting operations.  However, the problem space for
searching and sorting international strings is large, not fully
explored, and is outside the area of expertise for the Internet
Engineering Task Force (IETF).  Rather than attempt to solve such a
large problem, this specification creates an abstraction framework so
that application protocols can precisely identify a comparison
function, and the repertoire of comparison functions can be extended
in the future.  [STANDARDS TRACK]

This is now a Proposed Standard Protocol.

STANDARDS TRACK: This document specifies an Internet standards track
protocol for the Internet community,and requests discussion and 
suggestions for improvements.Please refer to the current edition of the 
Internet Official Protocol Standards (STD 1) for the standardization 
state and status of this protocol.  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://www1.ietf.org/mailman/listinfo/ietf-announce