RFC 8228 on Guidance on Designing Label Generation Rulesets (LGRs) Supporting Variant Labels
rfc-editor@rfc-editor.org Tue, 22 August 2017 21:39 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9CD80132A7E for <ietf-announce@ietfa.amsl.com>; Tue, 22 Aug 2017 14:39:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=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 3Ip3yJpUb62a for <ietf-announce@ietfa.amsl.com>; Tue, 22 Aug 2017 14:39: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 EDFD3132A8A for <ietf-announce@ietf.org>; Tue, 22 Aug 2017 14:39:00 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id D9725B80EB4; Tue, 22 Aug 2017 14:38:32 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 8228 on Guidance on Designing Label Generation Rulesets (LGRs) Supporting Variant Labels
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
Message-Id: <20170822213832.D9725B80EB4@rfc-editor.org>
Date: Tue, 22 Aug 2017 14:38:32 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/FYAceXHzkUt3yIAQrykZfpD0DEA>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce/>
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>
X-List-Received-Date: Tue, 22 Aug 2017 21:39:09 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 8228
Title: Guidance on Designing Label Generation
Rulesets (LGRs) Supporting Variant Labels
Author: A. Freytag
Status: Informational
Stream: IETF
Date: August 2017
Mailbox: asmus@unicode.org
Pages: 24
Characters: 50900
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-freytag-lager-variant-rules-06.txt
URL: https://www.rfc-editor.org/info/rfc8228
DOI: 10.17487/RFC8228
Rules for validating identifier labels and alternate representations
of those labels (variants) are known as Label Generation Rulesets
(LGRs); they are used for the implementation of identifier systems
such as Internationalized Domain Names (IDNs). This document
describes ways to design LGRs to support variant labels. In
designing LGRs, it is important to ensure that the label generation
rules are consistent and well behaved in the presence of variants.
The design decisions can then be expressed using the XML
representation of LGRs that is defined in RFC 7940.
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-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