From asmus@unicode.org Tue Dec 27 11:15:15 2016 Return-Path: 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 75084129ADC for ; Tue, 27 Dec 2016 11:15:15 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.84 X-Spam-Level: X-Spam-Status: No, score=-1.84 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_NEUTRAL=0.779] 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 T-Iu3KzA2vSx for ; Tue, 27 Dec 2016 11:15:13 -0800 (PST) Received: from elasmtp-galgo.atl.sa.earthlink.net (elasmtp-galgo.atl.sa.earthlink.net [209.86.89.61]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AE5381293FE for ; Tue, 27 Dec 2016 11:15:13 -0800 (PST) Received: from [75.165.33.149] (helo=[192.168.1.101]) by elasmtp-galgo.atl.sa.earthlink.net with esmtpa (Exim 4.67) (envelope-from ) id 1cLxCQ-0000WM-CX; Tue, 27 Dec 2016 14:14:14 -0500 References: <148286515400.14213.14254128523603431274.idtracker@ietfa.amsl.com> To: Kim Davies , Andrew Sullivan , John C Klensin , Paul Hoffman , =?UTF-8?B?UGF0cmlrIEbDpGx0c3Ryw7Zt?= , Yoshiro YONEYA , Marc Blanchet , Alexey Melnikov , lager WG From: Asmus Freytag X-Forwarded-Message-Id: <148286515400.14213.14254128523603431274.idtracker@ietfa.amsl.com> Message-ID: Date: Tue, 27 Dec 2016 11:14:10 -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: <148286515400.14213.14254128523603431274.idtracker@ietfa.amsl.com> Content-Type: multipart/alternative; boundary="------------6B4F24E1B40B4C8BC954D49C" X-ELNK-Trace: 464f085de979d7246f36dc87813833b2b92c5f0aecc81b5103a59cfb2b77ca4433f4cec73b7a597e350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c X-Originating-IP: 75.165.33.149 Archived-At: Subject: [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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Dec 2016 23:31:59 -0000 This is a multi-part message in MIME format. --------------6B4F24E1B40B4C8BC954D49C Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Never expected the subject of variants to be as complicated when I started out in this. 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 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 --------------6B4F24E1B40B4C8BC954D49C Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 7bit

Never expected the subject of variants to be as complicated when I started out in this.

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


--------------6B4F24E1B40B4C8BC954D49C-- From nobody Wed Dec 28 19:32:10 2016 Return-Path: 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 3A231129534 for ; Wed, 28 Dec 2016 19:32:09 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.9 X-Spam-Level: X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] 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 LEi9j3nPTZZ7 for ; Wed, 28 Dec 2016 19:32:07 -0800 (PST) Received: from mx2.yitter.info (mx2.yitter.info [50.116.54.116]) by ietfa.amsl.com (Postfix) with ESMTP id 10B93129546 for ; Wed, 28 Dec 2016 19:32:06 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by mx2.yitter.info (Postfix) with ESMTP id D1CE911446; Thu, 29 Dec 2016 03:32:07 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at crankycanuck.ca Received: from mx2.yitter.info ([127.0.0.1]) by localhost (mx2.yitter.info [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RXcJEie67Yjt; Thu, 29 Dec 2016 03:32:06 +0000 (UTC) Received: from mx2.yitter.info (192-0-220-231.cpe.teksavvy.com [192.0.220.231]) by mx2.yitter.info (Postfix) with ESMTPSA id 566AB1047F; Thu, 29 Dec 2016 03:32:06 +0000 (UTC) Date: Wed, 28 Dec 2016 22:32:02 -0500 From: Andrew Sullivan To: Asmus Freytag Message-ID: <20161229033202.GC3304@mx2.yitter.info> References: <148286515400.14213.14254128523603431274.idtracker@ietfa.amsl.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.24 (2015-08-30) Archived-At: Cc: Kim Davies , Alexey Melnikov , Paul Hoffman , Patrik =?utf-8?B?RsOkbHRzdHLDtm0=?= , Marc Blanchet , John C Klensin , lager WG , Yoshiro YONEYA 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 Dec 2016 03:32:09 -0000 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! > > 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 > > > > 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 > > -- Andrew Sullivan ajs@anvilwalrusden.com From nobody Wed Dec 28 20:25:11 2016 Return-Path: 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 ; 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 ; 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 ; 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 ) 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> <20161229033202.GC3304@mx2.yitter.info> From: Asmus Freytag 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: 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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 >> >> >> >> 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 >> >> From nobody Wed Dec 28 23:01:11 2016 Return-Path: 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 511871299B3 for ; Wed, 28 Dec 2016 23:01:09 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -5.801 X-Spam-Level: X-Spam-Status: No, score=-5.801 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, RP_MATCHES_RCVD=-3.1, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=frobbit.se 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 yOs63xAU3n2o for ; Wed, 28 Dec 2016 23:01:08 -0800 (PST) Received: from mail.frobbit.se (mail.frobbit.se [IPv6:2a02:80:3ffe::176]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0EA4E129976 for ; Wed, 28 Dec 2016 22:51:13 -0800 (PST) Received: from [2.65.181.172] (2.65.181.172.mobile.tre.se [2.65.181.172]) by mail.frobbit.se (Postfix) with ESMTPSA id E244122B39; Thu, 29 Dec 2016 07:51:09 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=frobbit.se; s=mail; t=1482994270; bh=uN8J1Gu7k2bAm3A2BSm0ZX4ivLxqU5Au1NkGAQTNeVI=; h=Subject:From:In-Reply-To:Date:Cc:References:To:From; b=jnW73J80u2fCXz+37UpxrfQuT20FNdY9453Ek4XT6mEjRb3OQqCHLipdSbH9nXZrr OFgbMYnEyGcw4EN0BGC31yvUHd4+F4febiJFF9BXfkiP0ic7diLj2gxJeZFEtLF6Lb EAlmYvde1RN2yljopK69uqbA+WoWGd3/C00wtZZ4= Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (1.0) From: =?utf-8?Q?Patrik_F=C3=A4ltstr=C3=B6m?= X-Mailer: iPhone Mail (14C92) In-Reply-To: <20161229033202.GC3304@mx2.yitter.info> Date: Thu, 29 Dec 2016 07:51:10 +0100 Content-Transfer-Encoding: quoted-printable Message-Id: <53C8E494-6E41-43BC-A00B-46DC829A96FF@frobbit.se> References: <148286515400.14213.14254128523603431274.idtracker@ietfa.amsl.com> <20161229033202.GC3304@mx2.yitter.info> To: Andrew Sullivan Archived-At: Cc: Kim Davies , Alexey Melnikov , Paul Hoffman , Marc Blanchet , John C Klensin , lager WG , Asmus Freytag , Yoshiro YONEYA Subject: Re: [Lager] 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 Dec 2016 07:01:09 -0000 > On 29 Dec 2016, at 04:32, Andrew Sullivan wrote: >=20 >> 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 starte= d >> out in this. >=20 > 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! +1 Patrik >=20 >>=20 >> I'm hoping this will present some needed guidance beyond what is in RFC >> 7940. >>=20 >> A./ >>=20 >>=20 >>=20 >> -------- 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 >>=20 >>=20 >>=20 >> 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. >>=20 >> 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-vari= ant-rules/ >> Htmlized: https://tools.ietf.org/html/draft-freytag-lager-variant-r= ules-00 >>=20 >>=20 >> 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. >>=20 >>=20 >>=20 >> Please note that it may take a couple of minutes from the time of submiss= ion >> until the htmlized version and diff are available at tools.ietf.org. >>=20 >> The IETF Secretariat >>=20 >>=20 >=20 > --=20 > Andrew Sullivan > ajs@anvilwalrusden.com