[precis] RFC 8265 on Preparation, Enforcement, and Comparison of Internationalized Strings Representing Usernames and Passwords
rfc-editor@rfc-editor.org Thu, 05 October 2017 20:54 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: precis@ietfa.amsl.com
Delivered-To: precis@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2336C134457; Thu, 5 Oct 2017 13:54:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 1m28SEIQ56cx; Thu, 5 Oct 2017 13:54:02 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B2635134453; Thu, 5 Oct 2017 13:53:47 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 3E414B80D9C; Thu, 5 Oct 2017 13:53:41 -0700 (PDT)
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
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, precis@ietf.org
Message-Id: <20171005205341.3E414B80D9C@rfc-editor.org>
Date: Thu, 05 Oct 2017 13:53:41 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/precis/sPrKvITk7lJcEQ-A6yB7fYqdR4s>
Subject: [precis] RFC 8265 on Preparation, Enforcement, and Comparison of Internationalized Strings Representing Usernames and Passwords
X-BeenThere: precis@ietf.org
X-Mailman-Version: 2.1.22
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: Thu, 05 Oct 2017 20:54:04 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 8265
Title: Preparation, Enforcement, and Comparison of
Internationalized Strings Representing Usernames
and Passwords
Author: P. Saint-Andre,
A. Melnikov
Status: Standards Track
Stream: IETF
Date: October 2017
Mailbox: stpeter@jabber.org,
alexey.melnikov@isode.com
Pages: 26
Characters: 62557
Obsoletes: RFC 7613
I-D Tag: draft-ietf-precis-7613bis-11.txt
URL: https://www.rfc-editor.org/info/rfc8265
DOI: 10.17487/RFC8265
This document describes updated methods for handling Unicode strings
representing usernames and passwords. The previous approach was
known as SASLprep (RFC 4013) and was based on Stringprep (RFC 3454).
The methods specified in this document provide a more sustainable
approach to the handling of internationalized usernames and
passwords. This document obsoletes RFC 7613.
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/retrieve/bulk
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