[precis] RFC 7700 on Preparation, Enforcement, and Comparison of Internationalized Strings Representing Nicknames

rfc-editor@rfc-editor.org Tue, 15 December 2015 05:07 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: precis@ietfa.amsl.com
Delivered-To: precis@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 60C411B2AE9; Mon, 14 Dec 2015 21:07:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.912
X-Spam-Level:
X-Spam-Status: No, score=-101.912 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OJh-NCTswCMY; Mon, 14 Dec 2015 21:07:49 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1900:3001:11::31]) by ietfa.amsl.com (Postfix) with ESMTP id B7DB31B2AE5; Mon, 14 Dec 2015 21:07:49 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 26773181EAD; Mon, 14 Dec 2015 21:05:27 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20151215050527.26773181EAD@rfc-editor.org>
Date: Mon, 14 Dec 2015 21:05:27 -0800
Archived-At: <http://mailarchive.ietf.org/arch/msg/precis/-bBFBU_rEai2IjTJ-mJCkHk8cmQ>
Cc: drafts-update-ref@iana.org, precis@ietf.org, rfc-editor@rfc-editor.org
Subject: [precis] RFC 7700 on Preparation, Enforcement, and Comparison of Internationalized Strings Representing Nicknames
X-BeenThere: precis@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Preparation and Comparison of Internationalized Strings <precis.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/precis>, <mailto:precis-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/precis/>
List-Post: <mailto:precis@ietf.org>
List-Help: <mailto:precis-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/precis>, <mailto:precis-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Dec 2015 05:07:51 -0000

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

        
        RFC 7700

        Title:      Preparation, Enforcement, and Comparison of 
                    Internationalized Strings Representing Nicknames 
        Author:     P. Saint-Andre
        Status:     Standards Track
        Stream:     IETF
        Date:       December 2015
        Mailbox:    peter@andyet.com
        Pages:      11
        Characters: 22898
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-precis-nickname-19.txt

        URL:        https://www.rfc-editor.org/info/rfc7700

        DOI:        http://dx.doi.org/10.17487/RFC7700

This document describes methods for handling Unicode strings
representing memorable, human-friendly names (called "nicknames",
"display names", or "petnames") for people, devices, accounts,
websites, and other entities.

This document is a product of the Preparation and Comparison of Internationalized Strings Working Group of the IETF.

This is now a Proposed Standard.

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 Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the 
standardization state and status of this protocol.  Distribution of this 
memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/rfc.html

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC