Re: [Lager] Fwd: New Version Notification for draft-freytag-lager-variant-rules-00.txt

Asmus Freytag <asmusf@ix.netcom.com> Thu, 29 December 2016 04:25 UTC

Return-Path: <asmusf@ix.netcom.com>
X-Original-To: lager@ietfa.amsl.com
Delivered-To: lager@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B1D72129522 for <lager@ietfa.amsl.com>; Wed, 28 Dec 2016 20:25:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.72
X-Spam-Level:
X-Spam-Status: No, score=-2.72 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); domainkeys=pass (384-bit key) header.from=asmusf@ix.netcom.com header.d=ix.netcom.com
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 gI2A4zhXEFH5 for <lager@ietfa.amsl.com>; Wed, 28 Dec 2016 20:25:08 -0800 (PST)
Received: from elasmtp-spurfowl.atl.sa.earthlink.net (elasmtp-spurfowl.atl.sa.earthlink.net [209.86.89.66]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 144F2129413 for <lager@ietf.org>; Wed, 28 Dec 2016 20:25:07 -0800 (PST)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=ix.netcom.com; b=Id1jGPidpvRf+K+7oP9pYb7FciJ9OLVG4Y70TTP7dX08pm7l2A8QtufP+V2E4K9A; h=Received:Subject:To:References:From:Message-ID:Date:User-Agent:MIME-Version:In-Reply-To:Content-Type:Content-Transfer-Encoding:X-ELNK-Trace:X-Originating-IP;
Received: from [75.165.33.149] (helo=[192.168.0.4]) by elasmtp-spurfowl.atl.sa.earthlink.net with esmtpa (Exim 4.67) (envelope-from <asmusf@ix.netcom.com>) id 1cMSGx-00046D-40 for lager@ietf.org; Wed, 28 Dec 2016 23:24:59 -0500
To: lager@ietf.org
References: <148286515400.14213.14254128523603431274.idtracker@ietfa.amsl.com> <a337657d-01c9-f176-8fd5-8607d776cba1@unicode.org> <20161229033202.GC3304@mx2.yitter.info>
From: Asmus Freytag <asmusf@ix.netcom.com>
Message-ID: <0b0e748d-99e6-55db-afd6-4b727fc75621@ix.netcom.com>
Date: Wed, 28 Dec 2016 20:25:02 -0800
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.5.1
MIME-Version: 1.0
In-Reply-To: <20161229033202.GC3304@mx2.yitter.info>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 7bit
X-ELNK-Trace: 464f085de979d7246f36dc87813833b2b92c5f0aecc81b51cf548901a360f7c5e9fa7d7b26b3dbf9350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 75.165.33.149
Archived-At: <https://mailarchive.ietf.org/arch/msg/lager/QUF8MW94vOLRsNbFymPYDH0pDNk>
Subject: Re: [Lager] Fwd: New Version Notification for draft-freytag-lager-variant-rules-00.txt
X-BeenThere: lager@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Label Generation Rules <lager.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/lager>, <mailto:lager-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/lager/>
List-Post: <mailto:lager@ietf.org>
List-Help: <mailto:lager-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/lager>, <mailto:lager-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 29 Dec 2016 04:25:09 -0000

On 12/28/2016 7:32 PM, Andrew Sullivan wrote:
> On Tue, Dec 27, 2016 at 11:14:10AM -0800, Asmus Freytag wrote:
>> Never expected the subject of variants to be as complicated when I started
>> out in this.
> I think it worth noting that some of your colleagues were more
> pessimistic .  On the other hand, you are most determined.  So good on
> you, and many happy returns!
Thanks, Andrew.

 From a purely practical point of view, I think there's something that 
you could
call "best practice" for LGR development and I believe the combined 
efforts of
the community and my colleagues on the Integration Panel are helping to
discover what works and what doesn't in that respect.

The document represents my attempt to capture what we've learned when it
comes to the mechanics of defining variants.

A./
>> I'm hoping this will present some needed guidance beyond what is in RFC
>> 7940.
>>
>> A./
>>
>>
>>
>> -------- Forwarded Message --------
>> Subject: 	New Version Notification for
>> draft-freytag-lager-variant-rules-00.txt
>> Date: 	Tue, 27 Dec 2016 10:59:14 -0800
>> From: 	internet-drafts@ietf.org
>> To: 	Asmus Freytag <asmus@unicode.org>
>>
>>
>>
>> A new version of I-D, draft-freytag-lager-variant-rules-00.txt
>> has been successfully submitted by Asmus Freytag and posted to the
>> IETF repository.
>>
>> Name:		draft-freytag-lager-variant-rules
>> Revision:	00
>> Title:		Variant Rules
>> Document date:	2016-12-27
>> Group:		Individual Submission
>> Pages:		18
>> URL:            https://www.ietf.org/internet-drafts/draft-freytag-lager-variant-rules-00.txt
>> Status:         https://datatracker.ietf.org/doc/draft-freytag-lager-variant-rules/
>> Htmlized:       https://tools.ietf.org/html/draft-freytag-lager-variant-rules-00
>>
>>
>> Abstract:
>>     This document gives guidance on designing well-behaved Label
>>     Generation Rulesets (LGRs) that support variant labels.  Typical
>>     examples of labels and LGRs are IDNs and zone registration policies
>>     defining permissible IDN labels.  Variant labels are labels that are
>>     either visually or semantically indistinguishable from an applied for
>>     label and are typically delegated together with the applied-for
>>     label, or permanently reserved.  While [RFC7940] defines the
>>     syntactical requirements for specifying the label generation rules
>>     for variant labels, additional considerations apply that ensure that
>>     the label generation rules are consistent and well-behaved in the
>>     presence of variants.
>>
>>
>>
>> Please note that it may take a couple of minutes from the time of submission
>> until the htmlized version and diff are available at tools.ietf.org.
>>
>> The IETF Secretariat
>>
>>