
From nobody Tue Mar  1 03:55:55 2016
Return-Path: <shollenbeck@verisign.com>
X-Original-To: lager@ietfa.amsl.com
Delivered-To: lager@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 62E5B1A1B46 for <lager@ietfa.amsl.com>; Tue,  1 Mar 2016 03:55:54 -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, DKIM_SIGNED=0.1, DKIM_VALID=-0.1] 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 EbZk0xy44EYb for <lager@ietfa.amsl.com>; Tue,  1 Mar 2016 03:55:52 -0800 (PST)
Received: from mail-oi0-x264.google.com (mail-oi0-x264.google.com [IPv6:2607:f8b0:4003:c06::264]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BD84D1A6F9B for <lager@ietf.org>; Tue,  1 Mar 2016 03:55:46 -0800 (PST)
Received: by mail-oi0-x264.google.com with SMTP id d205so2642936oia.1 for <lager@ietf.org>; Tue, 01 Mar 2016 03:55:46 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=verisign-com.20150623.gappssmtp.com; s=20150623; h=from:to:subject:thread-topic:thread-index:date:message-id :references:in-reply-to:accept-language:content-language :content-transfer-encoding:mime-version; bh=h4x05oFd4UT9wps4hp8YmD+ktnr9k/klafJNkCSUOHA=; b=T10HCZl7qwVwVKS36z8SiOMJLDXJPPmwS55fRmrfTTmFFy9F4h8o+YdmXM5rTVrm4a 3pG3y1f+pg3scq2wiqGbZ78rG/a0F81/O3qwcYpIYG8D8jG2R8v7cw5Rxqv5/rSXSg7z +b/dDLhhy+YO3Oe2VpW4xG30AUdOB1MJDbTJ7GNWsA+Xmlc1c+8KSTNseZW5YSFSBseV wzgZyY25/ccJPU9CJLr3k8Mab2MyBfmR+TPjiTPSShq55sQetpi1qCdUTtAgdboP6uaU exZhLffNEvMQR0oCwl3ngAnebhZtAtDLr95jopFkjFBuwDJD2ql1sjTCUGTHoyLVEFqA DELA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:to:subject:thread-topic:thread-index:date :message-id:references:in-reply-to:accept-language:content-language :content-transfer-encoding:mime-version; bh=h4x05oFd4UT9wps4hp8YmD+ktnr9k/klafJNkCSUOHA=; b=LSBfl/RDrUgK0bZ1NBD7qaV9DkprWa/rhtCnI4uzt8WBAMfgJKvhPrnPJ2jurCIZWE weR8Fu12089yFgfCi/JCN6WJfa+7sEdARWXa3m1hshMtT7OFyrnzZok1uwoFxRkzXbGb aLOqiaar0e03DO4dzb4/yLRC3neLUPi0KaEQBsn9e9RMt6DRDfoAwyGkQGifGkMchIZq +f6vzT0qaO8Fgke30tTO3Zze/YflXBwDwBwLpG4IbLGGagL2OZp0XZUGHVMH9W03CQkc 2ShVfxhGUqslF4q68gJMv0iHn+1hxaHGZAJ+yEtr4vHEnUALLJc7Iaayxy2UUi7EctlE BB5w==
X-Gm-Message-State: AD7BkJKwLleoGT/FO/mIBqXt7l/oARKQ61UJudInpjseO/jXzMIcAATs4lHJbNdIRmEuNNIETlnqUaFAY63YLEF4yuE1KXu0
X-Received: by 10.140.16.225 with SMTP id 88mr26145952qgb.96.1456833346122; Tue, 01 Mar 2016 03:55:46 -0800 (PST)
Received: from brn1lxmailout02.verisign.com (brn1lxmailout02.verisign.com. [72.13.63.42]) by smtp-relay.gmail.com with ESMTPS id g133sm4443447qkb.1.2016.03.01.03.55.45 (version=TLS1 cipher=AES128-SHA bits=128/128); Tue, 01 Mar 2016 03:55:46 -0800 (PST)
X-Relaying-Domain: verisign.com
Received: from brn1wnexcas02.vcorp.ad.vrsn.com (brn1wnexcas02 [10.173.152.206]) by brn1lxmailout02.verisign.com (8.13.8/8.13.8) with ESMTP id u21BtjI9026216 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Tue, 1 Mar 2016 06:55:45 -0500
Received: from BRN1WNEXMBX02.vcorp.ad.vrsn.com ([::1]) by brn1wnexcas02.vcorp.ad.vrsn.com ([::1]) with mapi id 14.03.0174.001; Tue, 1 Mar 2016 06:55:44 -0500
From: "Hollenbeck, Scott" <shollenbeck@verisign.com>
To: Audric Schiltknecht <audric.schiltknecht@viagenie.ca>, "lager@ietf.org" <lager@ietf.org>
Thread-Topic: [Lager] Document Shepherd Volunteer Needed
Thread-Index: AdFegar7PV3B+X5cSwiN0P/41n4tYAANAhEABT7DcHA=
Date: Tue, 1 Mar 2016 11:55:44 +0000
Message-ID: <831693C2CDA2E849A7D7A712B24E257F4A37B0A3@BRN1WNEXMBX02.vcorp.ad.vrsn.com>
References: <831693C2CDA2E849A7D7A712B24E257F4A150E06@BRN1WNEXMBX01.vcorp.ad.vrsn.com> <56B208EA.8090902@viagenie.ca>
In-Reply-To: <56B208EA.8090902@viagenie.ca>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.173.152.4]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/lager/R4StSOdbAJ84xBicWExrvu9qmdQ>
Subject: Re: [Lager] Document Shepherd Volunteer Needed
X-BeenThere: lager@ietf.org
X-Mailman-Version: 2.1.15
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: Tue, 01 Mar 2016 11:55:54 -0000

> -----Original Message-----
> From: Lager [mailto:lager-bounces@ietf.org] On Behalf Of Audric
> Schiltknecht
> Sent: Wednesday, February 03, 2016 9:04 AM
> To: lager@ietf.org
> Subject: Re: [Lager] Document Shepherd Volunteer Needed
>=20
> Le 2016-02-03 07:51, Hollenbeck, Scott a =E9crit :
> > (Trying to get a head of an administrative issue...)
> >
> > We're going to need a document shepherd when the time comes to submit
> draft-ietf-lager-specification to the IESG. Is anyone willing to
> volunteer? The role is described here:
>=20
> I'm willing ot give it a try!
>=20
> Audric
>=20
> >
> > https://www.ietf.org/iesg/statement/document-shepherds.html

Audric, with the WG last call complete and the document updated, we can sta=
rt preparing the document shepherd writeup. There's more info here:

https://www.ietf.org/iesg/template/doc-writeup.html

I'll start a conversation with Barry to see if he has a preference for a fo=
rmat.

Scott


From nobody Tue Mar  1 10:39:54 2016
Return-Path: <marc.blanchet@viagenie.ca>
X-Original-To: lager@ietfa.amsl.com
Delivered-To: lager@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0F0801B3F97; Tue,  1 Mar 2016 10:39:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.907
X-Spam-Level: 
X-Spam-Status: No, score=-1.907 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.006, SPF_PASS=-0.001] 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 bwb4EBh-UXHm; Tue,  1 Mar 2016 10:39:51 -0800 (PST)
Received: from jazz.viagenie.ca (jazz.viagenie.ca [IPv6:2620:0:230:8000::2]) by ietfa.amsl.com (Postfix) with ESMTP id BB2791B38D3; Tue,  1 Mar 2016 10:39:51 -0800 (PST)
Received: from [206.123.31.194] (h194.viagenie.ca [206.123.31.194]) by jazz.viagenie.ca (Postfix) with ESMTPSA id 29B5C476C3; Tue,  1 Mar 2016 13:39:51 -0500 (EST)
From: "Marc Blanchet" <marc.blanchet@viagenie.ca>
To: media-types@iana.org
Date: Tue, 01 Mar 2016 13:39:50 -0500
Message-ID: <A70C83D7-B170-4486-92AD-43BED221916C@viagenie.ca>
MIME-Version: 1.0
Content-Type: text/plain; format=flowed
X-Mailer: MailMate (1.9.3r5187)
Archived-At: <http://mailarchive.ietf.org/arch/msg/lager/WEWXtEsAQEIOrwwFj2NZsnZZEiI>
Cc: draft-ietf-lager-specification@ietf.org, lager WG <lager@ietf.org>
Subject: [Lager] media-type registration request review
X-BeenThere: lager@ietf.org
X-Mailman-Version: 2.1.15
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: Tue, 01 Mar 2016 18:39:53 -0000

Hello,
  draft-ietf-lager-specification requests the registration of a new 
media-type. The document has passed WGLC and we would like to have a 
review of the request. Herein the extract of the media-type form from 
the draft. Thanks in advance for the review

Marc, lager wg co-chair

<extract>
11.1.  Media Type Registration

    The media type "application/lgr+xml" should be registered to denote
    transmission of label generation rulesets that are compliant with
    this specification, in accordance with [RFC6838].

    Type name: application

    Subtype name: lgr+xml

    Required parameters: None.

    Optional parameters: charset (as for application/xml per [RFC7303])

    Security considerations: As for application/xml per [RFC7303]

    Interoperability considerations: As for application/xml per 
[RFC7303]

    Published specification: This document.

    Applications which use this media type: Software using label
    generation rulesets, including registry applications and client
    validators.

    Additional information: None.

    Magic number: None.

    File extension: .lgr or .xml

    Macintosh file-type code: None.

    Object Identifiers: None.

    Intended Usage: Common

    Personal and email address for further information: See the Authors
    of this document.

    Change Controller: IESG
</extract>


From nobody Fri Mar  4 11:44:11 2016
Return-Path: <asmusf@ix.netcom.com>
X-Original-To: lager@ietfa.amsl.com
Delivered-To: lager@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D95851A88C7; Fri,  4 Mar 2016 11:44:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 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] 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 q08gYjymuCEi; Fri,  4 Mar 2016 11:44:07 -0800 (PST)
Received: from elasmtp-junco.atl.sa.earthlink.net (elasmtp-junco.atl.sa.earthlink.net [209.86.89.63]) by ietfa.amsl.com (Postfix) with ESMTP id 59D681A88C2; Fri,  4 Mar 2016 11:44:07 -0800 (PST)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=ix.netcom.com; b=UseGiLDa3OkNN+ShtNL9w6lrGpYEK7yhEA1VGF1KoqCaDNY3UOaO8NCVlve6ab41; h=Received:Subject:To:References:Cc:From:Message-ID:Date:User-Agent:MIME-Version:In-Reply-To:Content-Type:Content-Transfer-Encoding:X-ELNK-Trace:X-Originating-IP;
Received: from [71.35.115.182] (helo=[192.168.1.104]) by elasmtp-junco.atl.sa.earthlink.net with esmtpa (Exim 4.67) (envelope-from <asmusf@ix.netcom.com>) id 1abvdJ-0003wI-TK; Fri, 04 Mar 2016 14:43:29 -0500
To: Mark Baker <distobj@acm.org>, Marc Blanchet <marc.blanchet@viagenie.ca>
References: <A70C83D7-B170-4486-92AD-43BED221916C@viagenie.ca> <CALcoZiodFagzBk9QyhzUuqb=VZc62vGxY=560oweaNopdSRgfQ@mail.gmail.com>
From: Asmus Freytag <asmusf@ix.netcom.com>
Message-ID: <56D9E56E.1090301@ix.netcom.com>
Date: Fri, 4 Mar 2016 11:43:42 -0800
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.6.0
MIME-Version: 1.0
In-Reply-To: <CALcoZiodFagzBk9QyhzUuqb=VZc62vGxY=560oweaNopdSRgfQ@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
X-ELNK-Trace: 464f085de979d7246f36dc87813833b2857e9f10d2205ddc6075354744af6abe3217137c15219439350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 71.35.115.182
Archived-At: <http://mailarchive.ietf.org/arch/msg/lager/Ah-C025TWxCLQv4tRTRXZN-iTPA>
Cc: draft-ietf-lager-specification@ietf.org, media-types@iana.org, lager WG <lager@ietf.org>
Subject: Re: [Lager] [media-types] media-type registration request review
X-BeenThere: lager@ietf.org
X-Mailman-Version: 2.1.15
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: Fri, 04 Mar 2016 19:44:09 -0000

On 3/4/2016 11:23 AM, Mark Baker wrote:
> Hi,
>
> On Tue, Mar 1, 2016 at 1:39 PM, Marc Blanchet <marc.blanchet@viagenie.ca> wrote:
>> Hello,
>>   draft-ietf-lager-specification requests the registration of a new
>> media-type. The document has passed WGLC and we would like to have a review
>> of the request. Herein the extract of the media-type form from the draft.
>> Thanks in advance for the review
>>
>> Marc, lager wg co-chair
>>
>> <extract>
>> 11.1.  Media Type Registration
>>
>>     The media type "application/lgr+xml" should be registered to denote
>>     transmission of label generation rulesets that are compliant with
>>     this specification, in accordance with [RFC6838].
>>
>>     Type name: application
>>
>>     Subtype name: lgr+xml
>>
>>     Required parameters: None.
>>
>>     Optional parameters: charset (as for application/xml per [RFC7303])
>>
>>     Security considerations: As for application/xml per [RFC7303]
> I suggesting moving section 12 of the draft here.
>
>>     Interoperability considerations: As for application/xml per [RFC7303]
>>
>>     Published specification: This document.
>>
>>     Applications which use this media type: Software using label
>>     generation rulesets, including registry applications and client
>>     validators.
> Can you be more specific, as the registry information will be stored
> and viewed out of the context of the LAGER WG. Maybe "Software using
> IDNA label generation rulesets"? That's just a guess on my part, as
> I'm not very familiar with nomenclature in that space.

The label generation rulesets specification is not limited to IDNA.

Software using label generation rulesets for internationalized 
identifiers, such IDNs, including...


>
>>     Additional information: None.
>>
>>     Magic number: None.
>>
>>     File extension: .lgr or .xml
> .xml is associated with application/xml so I'd just stick with .lgr.

Apparently there are some other media types that use .xml., so what are 
the conventions?

A./
>
> Looks good otherwise.
>


From nobody Sun Mar  6 21:07:21 2016
Return-Path: <duerst@it.aoyama.ac.jp>
X-Original-To: lager@ietfa.amsl.com
Delivered-To: lager@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 501A41A8AB9; Sun,  6 Mar 2016 21:07:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.202
X-Spam-Level: 
X-Spam-Status: No, score=-0.202 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=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 aurAoNxl9gDZ; Sun,  6 Mar 2016 21:07:15 -0800 (PST)
Received: from APC01-PU1-obe.outbound.protection.outlook.com (mail-pu1apc01on0108.outbound.protection.outlook.com [104.47.126.108]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C28F21A8AB8; Sun,  6 Mar 2016 21:07:14 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=itaoyama.onmicrosoft.com; s=selector1-it-aoyama-ac-jp; h=From:To:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=/nkYa2bmI28qT+duxWRhLP9lPb9BH9fE3ebhiHMtez8=; b=k6RR0dRBD7ive7+2l9Zxf5tjWVXTnGC+P7KNGdZXxkh/QYDKD8cYQde6oshCAgp0234uK5xoaJWZQRCz11yTNSbBxhDGA2Z814lYk1o7UMkRZrJd2Myh0SgwKaAUH2ZfwkkFMKXpDZwSX/nnHjN/zPYatOlC2scL9X/2rKDhx8o=
Authentication-Results: ietf.org; dkim=none (message not signed) header.d=none;ietf.org; dmarc=none action=none header.from=it.aoyama.ac.jp;
Received: from [133.2.210.64] (133.2.210.64) by TY1PR01MB0142.jpnprd01.prod.outlook.com (10.161.134.14) with Microsoft SMTP Server (TLS) id 15.1.415.20; Mon, 7 Mar 2016 05:07:10 +0000
To: Mark Baker <distobj@acm.org>, Marc Blanchet <marc.blanchet@viagenie.ca>
References: <A70C83D7-B170-4486-92AD-43BED221916C@viagenie.ca> <CALcoZiodFagzBk9QyhzUuqb=VZc62vGxY=560oweaNopdSRgfQ@mail.gmail.com>
From: =?UTF-8?Q?Martin_J._D=c3=bcrst?= <duerst@it.aoyama.ac.jp>
Organization: Aoyama Gakuin University
Message-ID: <56DD0C7C.20102@it.aoyama.ac.jp>
Date: Mon, 7 Mar 2016 14:07:08 +0900
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.6.0
MIME-Version: 1.0
In-Reply-To: <CALcoZiodFagzBk9QyhzUuqb=VZc62vGxY=560oweaNopdSRgfQ@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"; format=flowed
Content-Transfer-Encoding: 7bit
X-Originating-IP: [133.2.210.64]
X-ClientProxiedBy: KAWPR01CA0015.jpnprd01.prod.outlook.com (25.161.24.25) To TY1PR01MB0142.jpnprd01.prod.outlook.com (25.161.134.14)
X-Microsoft-Exchange-Diagnostics: 1; TY1PR01MB0142; 2:4itS8CMI6E0bZQfuTydiJBvsGS7vXnFtYfQbn+UBGpteUKGXmmNRXb5/IiK3fKXTSg2N/iev9qd+PwXGfP01so8Ry75fwt/eBFoAT5ysxKwyaCNIKXLyBnidtVkn96JgULaxJBXEx83es8egLD4C5w==; 3:acfst1pmYS0iH+nhpKHjxiCM2grXCKHHHwBzyD7w/ys4e7rSPZQUsgM8lZv6Xg/2zQ/jq9uJ+ULRzy4UJfAOuZzxGnFTpqm0qsDdvgdZVM5v5hJOI8aGG/ba0ZL7ktqa; 25:qGZWjRNVv2kGETx0rfRh1ShFoeeFhliqNkJDu64rORHlt9NRGbhEijPuO0Alc56d2O2/irEvaeh9lva8i0GHpeKtEwabHk3pMmHxVMqdwRRKsLxz6zO0uvHVd9HkxV5uXxU8I47U5zlhl3Pvg7OACNigdDYaf/qLBqb9d8M4AQps6tK4srz1zOPmdjv2VI19X1nUQXhhA77aCroQBoyfk7U+Mb3xZnaBlw4eRd2TZA1rAubX7Y/nGSdnWsdtGHu2EkxRFWSP7R6HZBDX979soFRb+7xqYlnBdVoZes2dbIwdw7Xwa7meoCM2GqBs4HxdyfpzkoshpwW4hxv1xEdprQ==
X-Microsoft-Antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:TY1PR01MB0142;
X-MS-Office365-Filtering-Correlation-Id: 4fd214d6-041a-48c3-6006-08d346465697
X-Microsoft-Antispam-PRVS: <TY1PR01MB0142A05698BBCEAEB7A95469CAB10@TY1PR01MB0142.jpnprd01.prod.outlook.com>
X-Exchange-Antispam-Report-Test: UriScan:;
X-Exchange-Antispam-Report-CFA-Test: BCL:0; PCL:0; RULEID:(2401047)(5005006)(8121501046)(3002001)(10201501046); SRVR:TY1PR01MB0142; BCL:0; PCL:0; RULEID:; SRVR:TY1PR01MB0142; 
X-Microsoft-Exchange-Diagnostics: 1; TY1PR01MB0142; 4:Nn6SAA2XNiXnFz7SUv9eD6fJ606w84Vb06OpD1eDWazyn5gNTS1RZ08SfOhlfebOhqz5SIj7obwh4Rdxx+uJ5XuxbiUeHyXniopECglcsW8UWVO6PhpBzt/ShSXbJHCNst4B6WzBTDNknc6QTwEV36300bWd1KfyhZyh22wzvxavwH90rV5fAS0RUOOb2ItrvTGHV71XsMXh8m8HXpTwrvrB0JULnIy3k+pMUu9yES7sT/iuHcoR99j8ROUc7rSGUBBdkgKmFf9orEqkPX+zcnVgK4bXcgAP42TBOul4Hl0OA2H0ZvIbL+vg+8xr+xECzJD4T5/wvFFH5xKdcITF1iaXCzNqLdipq+aO3QEifz0=
X-Forefront-PRVS: 087474FBFA
X-Forefront-Antispam-Report: SFV:NSPM; SFS:(10019020)(4630300001)(6009001)(6049001)(479174004)(377454003)(24454002)(51874003)(230700001)(23676002)(15975445007)(77096005)(42186005)(50466002)(5008740100001)(74482002)(19580395003)(19580405001)(5001770100001)(83506001)(122386002)(86362001)(81166005)(4001350100001)(54356999)(50986999)(76176999)(65816999)(33656002)(87976001)(92566002)(4326007)(47776003)(65806001)(2950100001)(40100003)(65956001)(189998001)(66066001)(6116002)(3846002)(586003)(1096002)(64126003)(2906002)(5004730100002)(3940600001); DIR:OUT; SFP:1102; SCL:1; SRVR:TY1PR01MB0142; H:[133.2.210.64]; FPR:; SPF:None; MLV:sfv; LANG:en; 
X-Microsoft-Exchange-Diagnostics: =?utf-8?B?MTtUWTFQUjAxTUIwMTQyOzIzOjZyR3FoMkZuVzFmY1hTcnFTelRPbjJISWhR?= =?utf-8?B?MHBlT1AwRTRXRTFBOUdTZ1o2emowdkNNcGZYWnkwekswc0FXRGVHRklwUG1i?= =?utf-8?B?Nlh5cVNKN1V4ZU1hdTd0ZldvZTFIMnh1T0V3Qm81aWF0bml3VHFwaWFBeGJD?= =?utf-8?B?VjVqWHFCeEdmTHFNbGJKaGR6eGNCZ2VBUG10ZW4zT1lPMDNMTDZtellNUTA3?= =?utf-8?B?YlErRk1Hd1ZlMHVtWTQ5QlhXQVlxM1poNlpFM2M5clpweDBmL2Jpc1N5bk4y?= =?utf-8?B?MXdFRVA3ZjJacTYwUXVzY1hRaXhCUmdBOVh1d05lc1dQK0h1bzFCcXIyZW5P?= =?utf-8?B?SXJrZE04amJKajlEYWtrV2dxdkowaWdFU2xDZ3I1eC9oUHJmSjRVdzB6dmRM?= =?utf-8?B?OTRlM2RlMXZhbThWbWpsaTFwZUdtTmlBV0VrdG9nUnRTQ202eFVsSjNib3hC?= =?utf-8?B?VTUwUzJlNFVGR0lMU0ZRcy90L1NxSmtWS3NVMGpLR2dEZXl6TmpMMEJFcnlk?= =?utf-8?B?SU0yYnJyWXlnZFQrOXVKclZ0S29sWHk2L2xqVzNERGM3SHZGZmdXaXdxa0tS?= =?utf-8?B?VlBGU3FEYnJuT21HallYUzdJcHc2WjNCbVdZWHV0VmEweUFwNHFWdmNZL2sw?= =?utf-8?B?d1Z4anNod1h4dUw0N21mdUswZURwZ3hpRnZtaTVkSktROWdKODdKMHlxOFht?= =?utf-8?B?OWJyaVd1eGk4MjhVMXQrNVNrYzY1aURxNlVUTFVnK05qbktZdXQxV0FXaE95?= =?utf-8?B?M3NHRklGdDlFOTJJMkI3YytidHNvOHNSeXNCT3p2cnZBQVI5MW5JVVoySWE3?= =?utf-8?B?TzVRZWRBdHZHalBpTkpxTGxSdDRIbjF4RXNnWkpIc0Y3Z3pZZVdzTFVwMEJR?= =?utf-8?B?T1RTK2hvVkk1dlV1dkVKQmNqODEybnJDTDUzdStFaG90aVlFZ0hhdkRYNzZI?= =?utf-8?B?VUN6ajRnV2F1d0tKMW9CNnFNTmNOcXVCVlhZNDFVOWpHd3htTFhudnZKN0RS?= =?utf-8?B?SkFodGcyUDJpb2lWV0cyUnhteTdOcExidUgzVnZoTFgyaUVDWjVxOFVZWVh3?= =?utf-8?B?VkUrVTJSUVZWY3Z4UkMrQlc4d1dEM2FrSUF5enk0YVN3ZjRFa0ZOVERhODZo?= =?utf-8?B?Z28rVFhjamtYbmMvR3c2eW92ZUJZUEdjNEJBem55K2lwVGFDcXo1MTdWY3do?= =?utf-8?B?Uk1HeWV2bzJOODRtVk9ScnpEOEQzdE9DazI0ZXBMcE90M0hXcVQ5NlFJY0pr?= =?utf-8?B?WDZlbTBZay9udDhWdisvNVRreHFoTjBlUDBOdloreVRUR3EvVWZHNklkcUtS?= =?utf-8?B?WDVDQ2Frb2FGL1lYckkvYmJoZ2FhSXI2WXp5YmM3cGlWaEtMd2lVREExZWRv?= =?utf-8?B?ZTBHZmhiRW5kUk0rbksrUy8wcnBuclFzeFdiaVIzVWJPaGdVL3VpbGZRSEcz?= =?utf-8?B?VThhbTV2QlI5SmdzOEc3V2hzRmFEbURGRlZ1R01YTlNLOEdoZnJ1ZTBvYUZy?= =?utf-8?B?S3MxdHV4aEk0SFQxR21VV3Jvc1NKTGNDOFNqYWZxV1RVbU9odG14Rm83WHhZ?= =?utf-8?B?NE9yTEFneUc3YklDd0p2bnNsd1ZXVjlWK0JENDRuVGxwK1AvOTdBUW8zaytr?= =?utf-8?Q?7PDO+CFNVuRihWY+lvwu?=
X-Microsoft-Exchange-Diagnostics: 1; TY1PR01MB0142; 5:bwv4Po4lP+J8ZOpHJLTxmCPVqD1z9VfBQssEXgK+DYuer/+pBRAwRc8NkXNlauFK/3V72ZYm4hRK0x7fUsgK64Sgn5uHQxq525wZVQUrVt9VvuxqLPnnV3XdbDtmktlmsPaa/peWekZKOanRvYtaZw==; 24:nMRI+vJY91p0zbZCtPn+N0C4ffjE2ckCFqvxFqaCKkNMmvidP8UxfeuAKiv4w5volaH6JDJ1gH+trgcmzVuAXKB4nFbOw23aRTOa4rLZ46A=
SpamDiagnosticOutput: 1:23
SpamDiagnosticMetadata: NSPM
X-OriginatorOrg: it.aoyama.ac.jp
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 07 Mar 2016 05:07:10.1600 (UTC)
X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted
X-MS-Exchange-Transport-CrossTenantHeadersStamped: TY1PR01MB0142
Archived-At: <http://mailarchive.ietf.org/arch/msg/lager/zOvPzlKcdtImAj8mGidMUhE-CsY>
Cc: draft-ietf-lager-specification@ietf.org, media-types@iana.org, lager WG <lager@ietf.org>
Subject: Re: [Lager] [media-types] media-type registration request review
X-BeenThere: lager@ietf.org
X-Mailman-Version: 2.1.15
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: Mon, 07 Mar 2016 05:07:20 -0000

On 2016/03/05 04:23, Mark Baker wrote:
> Hi,
>
> On Tue, Mar 1, 2016 at 1:39 PM, Marc Blanchet <marc.blanchet@viagenie.ca> wrote:
>> Hello,
>>   draft-ietf-lager-specification requests the registration of a new
>> media-type. The document has passed WGLC and we would like to have a review
>> of the request. Herein the extract of the media-type form from the draft.
>> Thanks in advance for the review
>>
>> Marc, lager wg co-chair
>>
>> <extract>
>> 11.1.  Media Type Registration
>>
>>     The media type "application/lgr+xml" should be registered to denote
>>     transmission of label generation rulesets that are compliant with
>>     this specification, in accordance with [RFC6838].
>>
>>     Type name: application
>>
>>     Subtype name: lgr+xml
>>
>>     Required parameters: None.
>>
>>     Optional parameters: charset (as for application/xml per [RFC7303])
>>
>>     Security considerations: As for application/xml per [RFC7303]
>
> I suggesting moving section 12 of the draft here.

I don't think that's necessary, and it would remove the "Security 
Considerations" section that's needed in every RFC. I'd suggest to 
replace "As for application/xml per [RFC7303]" with something such as
"See the security considerations for application/xml in [RFC7303] and 
the specific security considerations for Label Generation Rulesets in 
XML in RFC XXXX (RFC Editor/IANA, please replace XXXX with the final 
number of this document)".

>>     Interoperability considerations: As for application/xml per [RFC7303]
>>
>>     Published specification: This document.

The template will be stored independently of the containing RFC, so 
instead of "This document", use something like "RFC XXXX (RFC 
Editor/IANA, please replace XXXX with the final number of this document)

Regards,   Martin.

>>     Applications which use this media type: Software using label
>>     generation rulesets, including registry applications and client
>>     validators.
>
> Can you be more specific, as the registry information will be stored
> and viewed out of the context of the LAGER WG. Maybe "Software using
> IDNA label generation rulesets"? That's just a guess on my part, as
> I'm not very familiar with nomenclature in that space.
>
>>     Additional information: None.
>>
>>     Magic number: None.
>>
>>     File extension: .lgr or .xml
>
> .xml is associated with application/xml so I'd just stick with .lgr.
>
> Looks good otherwise.
>
> _______________________________________________
> media-types mailing list
> media-types@ietf.org
> https://www.ietf.org/mailman/listinfo/media-types
> .
>


From nobody Tue Mar  8 02:55:22 2016
Return-Path: <internet-drafts@ietf.org>
X-Original-To: lager@ietf.org
Delivered-To: lager@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 8E49812D60C; Tue,  8 Mar 2016 02:55:20 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.15.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20160308105520.14085.28098.idtracker@ietfa.amsl.com>
Date: Tue, 08 Mar 2016 02:55:20 -0800
Archived-At: <http://mailarchive.ietf.org/arch/msg/lager/3aJlanYhz-7Zb8b9Oas6EYBum5E>
Cc: lager@ietf.org
Subject: [Lager] I-D Action: draft-ietf-lager-specification-10.txt
X-BeenThere: lager@ietf.org
X-Mailman-Version: 2.1.17
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: Tue, 08 Mar 2016 10:55:20 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Label Generation Rules of the IETF.

        Title           : Representing Label Generation Rulesets using XML
        Authors         : Kim Davies
                          Asmus Freytag
	Filename        : draft-ietf-lager-specification-10.txt
	Pages           : 76
	Date            : 2016-03-08

Abstract:
   This document describes a method of representing rules for validating
   identifier labels and alternate representations of those labels using
   Extensible Markup Language (XML).  These policies, known as "Label
   Generation Rulesets" (LGRs), are used for the implementation of
   Internationalized Domain Names (IDNs), for example.  The rulesets are
   used to implement and share that aspect of policy defining which
   labels and Unicode code points are permitted for registrations, which
   alternative code points are considered variants, and what actions may
   be performed on labels containing those variants.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-lager-specification/

There's also a htmlized version available at:
https://tools.ietf.org/html/draft-ietf-lager-specification-10

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-lager-specification-10


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.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From nobody Tue Mar  8 03:09:23 2016
Return-Path: <kim.davies@icann.org>
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 080D912D65D for <lager@ietfa.amsl.com>; Tue,  8 Mar 2016 03:09:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.202
X-Spam-Level: 
X-Spam-Status: No, score=-4.202 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([127.0.0.1]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dauxO0ughzNP for <lager@ietfa.amsl.com>; Tue,  8 Mar 2016 03:09:18 -0800 (PST)
Received: from out.west.pexch112.icann.org (pfe112-ca-1.pexch112.icann.org [64.78.40.7]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2632A12D660 for <lager@ietf.org>; Tue,  8 Mar 2016 03:09:18 -0800 (PST)
Received: from PMBX112-W1-CA-1.pexch112.icann.org (64.78.40.21) by PMBX112-W1-CA-1.pexch112.icann.org (64.78.40.21) with Microsoft SMTP Server (TLS) id 15.0.1130.7; Tue, 8 Mar 2016 03:09:15 -0800
Received: from PMBX112-W1-CA-1.pexch112.icann.org ([64.78.40.21]) by PMBX112-W1-CA-1.PEXCH112.ICANN.ORG ([64.78.40.21]) with mapi id 15.00.1130.005; Tue, 8 Mar 2016 03:09:15 -0800
From: Kim Davies <kim.davies@icann.org>
To: "lager WG (lager@ietf.org)" <lager@ietf.org>
Thread-Topic: [Lager] I-D Action: draft-ietf-lager-specification-10.txt
Thread-Index: AQHReSkRtn3Z+sze7EyKGBeSAIMOeJ9P6a8A
Date: Tue, 8 Mar 2016 11:09:15 +0000
Message-ID: <06DC8073-406B-4308-BF4B-0ADBBBB36C94@icann.org>
References: <20160308105520.14085.28098.idtracker@ietfa.amsl.com>
In-Reply-To: <20160308105520.14085.28098.idtracker@ietfa.amsl.com>
Accept-Language: en-AU, en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [192.0.32.234]
Content-Type: multipart/signed; boundary="Apple-Mail=_C2B12F4F-43C7-42EB-9DBE-C857D1E557BA"; protocol="application/pkcs7-signature"; micalg=sha1
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/lager/4Ht7-jzNQ_dSyqFg5JBguJS4qxw>
Subject: Re: [Lager] I-D Action: draft-ietf-lager-specification-10.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: Tue, 08 Mar 2016 11:09:20 -0000

--Apple-Mail=_C2B12F4F-43C7-42EB-9DBE-C857D1E557BA
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Colleagues,

This new version makes some minor changes to fix some issues Audric =
relayed from the id-nits tool, add a couple of missing links from the =
references, and also implement suggestions from thread on reviewing the =
media type request contained within.

kim

> On Mar 8, 2016, at 10:55 AM, internet-drafts@ietf.org wrote:
>=20
>=20
> A New Internet-Draft is available from the on-line Internet-Drafts =
directories.
> This draft is a work item of the Label Generation Rules of the IETF.
>=20
>        Title           : Representing Label Generation Rulesets using =
XML
>        Authors         : Kim Davies
>                          Asmus Freytag
> 	Filename        : draft-ietf-lager-specification-10.txt
> 	Pages           : 76
> 	Date            : 2016-03-08
>=20
> Abstract:
>   This document describes a method of representing rules for =
validating
>   identifier labels and alternate representations of those labels =
using
>   Extensible Markup Language (XML).  These policies, known as "Label
>   Generation Rulesets" (LGRs), are used for the implementation of
>   Internationalized Domain Names (IDNs), for example.  The rulesets =
are
>   used to implement and share that aspect of policy defining which
>   labels and Unicode code points are permitted for registrations, =
which
>   alternative code points are considered variants, and what actions =
may
>   be performed on labels containing those variants.
>=20
>=20
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-lager-specification/
>=20
> There's also a htmlized version available at:
> https://tools.ietf.org/html/draft-ietf-lager-specification-10
>=20
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-lager-specification-10
>=20
>=20
> 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.
>=20
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>=20
> _______________________________________________
> Lager mailing list
> Lager@ietf.org
> https://www.ietf.org/mailman/listinfo/lager


--Apple-Mail=_C2B12F4F-43C7-42EB-9DBE-C857D1E557BA
Content-Disposition: attachment; filename="smime.p7s"
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIILwDCCBWow
ggRSoAMCAQICEAM3/aZ67iMUNwpbj+veFrowDQYJKoZIhvcNAQELBQAwZTELMAkGA1UEBhMCVVMx
FTATBgNVBAoTDERpZ2lDZXJ0IEluYzEZMBcGA1UECxMQd3d3LmRpZ2ljZXJ0LmNvbTEkMCIGA1UE
AxMbRGlnaUNlcnQgU0hBMiBBc3N1cmVkIElEIENBMB4XDTE1MDMzMTAwMDAwMFoXDTE4MDMzMTEy
MDAwMFowgYsxCzAJBgNVBAYTAlVTMRMwEQYDVQQIEwpDYWxpZm9ybmlhMRQwEgYDVQQHEwtMb3Mg
QW5nZWxlczE8MDoGA1UEChMzSW50ZXJuZXQgQ29ycG9yYXRpb24gZm9yIEFzc2lnbmVkIE5hbWVz
IGFuZCBOdW1iZXJzMRMwEQYDVQQDEwpLaW0gRGF2aWVzMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8A
MIIBCgKCAQEAp0mVGngM3EAPrsiqD1RgMJfuk7PzpwaER7Th8+di8A6FLY7M1XNYYe2d5zVjHZ24
gATERV3ZSrw4Oy+UG/RUrHlGxaYlIkTA8ZB4HOFrYHaBTf2BVFZqsMecBzH0/+kZ0Rdc7odU+48i
oi5NjpPNv7eOmSQlhQNOHRKm49htzKNlTons4LDv7Qkxzs2JBj1TzlEmXIhHmHPFLqqW64kFLWeW
olwSoaJiZ3GsFLCwEKdGpIKAK5FFL3Uje0kmsUu+dbSk5yQzCf4NVr3HSp9ym97E7SctvzWyK9QD
J0P6Ed88mt7qN1ntGyMyePTT2Xi69NOymtd16Qh/LZvGu+jfHQIDAQABo4IB7TCCAekwHwYDVR0j
BBgwFoAU5wIjgABP2Ne8lAvZP3Q5STI8inkwHQYDVR0OBBYEFHkeueu4UvC0be3qjbA4tsMzoHWb
MAwGA1UdEwEB/wQCMAAwHwYDVR0RBBgwFoEUa2ltLmRhdmllc0BpY2Fubi5vcmcwDgYDVR0PAQH/
BAQDAgWgMB0GA1UdJQQWMBQGCCsGAQUFBwMCBggrBgEFBQcDBDBDBgNVHSAEPDA6MDgGCmCGSAGG
/WwEAQIwKjAoBggrBgEFBQcCARYcaHR0cHM6Ly93d3cuZGlnaWNlcnQuY29tL0NQUzCBiAYDVR0f
BIGAMH4wPaA7oDmGN2h0dHA6Ly9jcmwzLmRpZ2ljZXJ0LmNvbS9EaWdpQ2VydFNIQTJBc3N1cmVk
SURDQS1nMS5jcmwwPaA7oDmGN2h0dHA6Ly9jcmw0LmRpZ2ljZXJ0LmNvbS9EaWdpQ2VydFNIQTJB
c3N1cmVkSURDQS1nMS5jcmwweQYIKwYBBQUHAQEEbTBrMCQGCCsGAQUFBzABhhhodHRwOi8vb2Nz
cC5kaWdpY2VydC5jb20wQwYIKwYBBQUHMAKGN2h0dHA6Ly9jYWNlcnRzLmRpZ2ljZXJ0LmNvbS9E
aWdpQ2VydFNIQTJBc3N1cmVkSURDQS5jcnQwDQYJKoZIhvcNAQELBQADggEBAJASl9oxRIgNxmHA
RyAYkZWY17Hv02f09iA9AXhylr0eOEqZ96Cs/VWY+CZp8eDnyhokGYoXhv8rRFjV+vX1JS72a6kE
mAhXy4h/aCq9KgzTpvoDW7uClk3iHYs56RN9pCidgq7G4m2a5JxVAeIep1iYDx5qE0GGtqqFHHZ2
iUvdKD19mc52cVcOKhmn4P0rl2oz7jSNjBqADpdS11mh3sgEQM/cAVmQecGV5cUlfRwEdA4DDhbz
5+ga8XXJUZy+Xm8yZXpqATzTamM7EXGuqW1DPqLSu748ZmQYjNFDdAMRwO267EXCRTyLIWb2BxzJ
JknVXjSiAYXvJL0IMIvRGSAwggZOMIIFNqADAgECAhAErnlgZmaQGrnFf6ZsW9zNMA0GCSqGSIb3
DQEBCwUAMGUxCzAJBgNVBAYTAlVTMRUwEwYDVQQKEwxEaWdpQ2VydCBJbmMxGTAXBgNVBAsTEHd3
dy5kaWdpY2VydC5jb20xJDAiBgNVBAMTG0RpZ2lDZXJ0IEFzc3VyZWQgSUQgUm9vdCBDQTAeFw0x
MzExMDUxMjAwMDBaFw0yODExMDUxMjAwMDBaMGUxCzAJBgNVBAYTAlVTMRUwEwYDVQQKEwxEaWdp
Q2VydCBJbmMxGTAXBgNVBAsTEHd3dy5kaWdpY2VydC5jb20xJDAiBgNVBAMTG0RpZ2lDZXJ0IFNI
QTIgQXNzdXJlZCBJRCBDQTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBANz4ESM/arXv
wCd5Gy0Fh6IQQzHfDtQVG093pCLOPoxw8L4Hjt0nKrwBHbYsCsrdaVgfQe1qBR/aY3hZHiIsK/i6
fsk1O1bxH3xCfiWwIxnGRTjXPUT5IHxgrhywWhgEvo8796nwlJqmDGNJtkEXU0AyvU/mUHpQHyVF
6PGJr83/Xv9Q8/AXEf+9xYn1vWK52PuORQSFbZnNxUhN/SarAjZF6jbXX2riGoJBCtzp2fWRF47G
Ia04PBPmHn9mnNVN2Uba9s9Sp307JMO0wVE1xpvr1O9+5HsD4US9egs34E/LgooNcRjkpuCJLBvz
snM8wbCSnhh9vat9xX0IoSzCn3MCAwEAAaOCAvgwggL0MBIGA1UdEwEB/wQIMAYBAf8CAQAwDgYD
VR0PAQH/BAQDAgGGMDQGCCsGAQUFBwEBBCgwJjAkBggrBgEFBQcwAYYYaHR0cDovL29jc3AuZGln
aWNlcnQuY29tMIGBBgNVHR8EejB4MDqgOKA2hjRodHRwOi8vY3JsNC5kaWdpY2VydC5jb20vRGln
aUNlcnRBc3N1cmVkSURSb290Q0EuY3JsMDqgOKA2hjRodHRwOi8vY3JsMy5kaWdpY2VydC5jb20v
RGlnaUNlcnRBc3N1cmVkSURSb290Q0EuY3JsMB0GA1UdJQQWMBQGCCsGAQUFBwMCBggrBgEFBQcD
BDCCAbMGA1UdIASCAaowggGmMIIBogYKYIZIAYb9bAACBDCCAZIwKAYIKwYBBQUHAgEWHGh0dHBz
Oi8vd3d3LmRpZ2ljZXJ0LmNvbS9DUFMwggFkBggrBgEFBQcCAjCCAVYeggFSAEEAbgB5ACAAdQBz
AGUAIABvAGYAIAB0AGgAaQBzACAAQwBlAHIAdABpAGYAaQBjAGEAdABlACAAYwBvAG4AcwB0AGkA
dAB1AHQAZQBzACAAYQBjAGMAZQBwAHQAYQBuAGMAZQAgAG8AZgAgAHQAaABlACAARABpAGcAaQBD
AGUAcgB0ACAAQwBQAC8AQwBQAFMAIABhAG4AZAAgAHQAaABlACAAUgBlAGwAeQBpAG4AZwAgAFAA
YQByAHQAeQAgAEEAZwByAGUAZQBtAGUAbgB0ACAAdwBoAGkAYwBoACAAbABpAG0AaQB0ACAAbABp
AGEAYgBpAGwAaQB0AHkAIABhAG4AZAAgAGEAcgBlACAAaQBuAGMAbwByAHAAbwByAGEAdABlAGQA
IABoAGUAcgBlAGkAbgAgAGIAeQAgAHIAZQBmAGUAcgBlAG4AYwBlAC4wHQYDVR0OBBYEFOcCI4AA
T9jXvJQL2T90OUkyPIp5MB8GA1UdIwQYMBaAFEXroq/0ksuCMS1Ri6enIZ3zbcgPMA0GCSqGSIb3
DQEBCwUAA4IBAQBO1Iknuf0dh3d+DygFkPEKL8k7Pr2TnJDGr/qRUYcyVGvoysFxUVyZjrX64GIZ
maYHmnwTJ9vlAqKEEtkV9gpEV8Q0j21zHzrWoAE93uOC5EVrsusl/YBeHTmQvltC9s6RYOP5oFYM
SBDOM2h7zZOr8GrLT1gPuXtdGwSBnqci4ldJJ+6Skwi+aQhTAjouXcgZ9FCATgLZsF2RtJOH+ZaW
gVVAjmbtgti7KF/tTGHtBlgoGVMRRLxHICmyBGzYiVSZO3XbZ3gsHpJ4xlU9WBIRMm69QwxNNNt7
xkLb7L6rm2FMBpLjjt8hKlBXBMBgojXVJJ5mNwlJz9X4ZbPg4m7CMYIDGTCCAxUCAQEweTBlMQsw
CQYDVQQGEwJVUzEVMBMGA1UEChMMRGlnaUNlcnQgSW5jMRkwFwYDVQQLExB3d3cuZGlnaWNlcnQu
Y29tMSQwIgYDVQQDExtEaWdpQ2VydCBTSEEyIEFzc3VyZWQgSUQgQ0ECEAM3/aZ67iMUNwpbj+ve
FrowCQYFKw4DAhoFAKCCAXUwGAYJKoZIhvcNAQkDMQsGCSqGSIb3DQEHATAcBgkqhkiG9w0BCQUx
DxcNMTYwMzA4MTEwOTE0WjAjBgkqhkiG9w0BCQQxFgQUlSHC7dckt0vUc0yXUgkbvbaWwCYwgYgG
CSsGAQQBgjcQBDF7MHkwZTELMAkGA1UEBhMCVVMxFTATBgNVBAoTDERpZ2lDZXJ0IEluYzEZMBcG
A1UECxMQd3d3LmRpZ2ljZXJ0LmNvbTEkMCIGA1UEAxMbRGlnaUNlcnQgU0hBMiBBc3N1cmVkIElE
IENBAhADN/2meu4jFDcKW4/r3ha6MIGKBgsqhkiG9w0BCRACCzF7oHkwZTELMAkGA1UEBhMCVVMx
FTATBgNVBAoTDERpZ2lDZXJ0IEluYzEZMBcGA1UECxMQd3d3LmRpZ2ljZXJ0LmNvbTEkMCIGA1UE
AxMbRGlnaUNlcnQgU0hBMiBBc3N1cmVkIElEIENBAhADN/2meu4jFDcKW4/r3ha6MA0GCSqGSIb3
DQEBAQUABIIBAE9lqRjbzRxqZByH7U2w7cSte15MlBtieTZr1tTxPrXO7H6Gbu6RD5WbjcLsrjcf
pCyAAna4HvsT5oYBB3l5VItrp8P7z9RBlyPNds5uS/Re3kGUpHiDeH2vpvndj7/RAB8NwCZJN8lb
5eEFzvradP9SLmcCf/oAj0EqOBtEUazYYTWuk3qk0eONYq3gaQWChUnKYchEpotCq7mBKG3tiwCk
OFKYzIdWQti/XLcmOgzXsXyJDgycJCjvVVV3bEs5U1TrmVRhG1mXThY+ltdntyou7PF8avlnwvv0
cdHVVIly4GBKcVmncf0vRxYe9Fd7TuMwHW1tb7IP6uHyRNQbmdEAAAAAAAA=

--Apple-Mail=_C2B12F4F-43C7-42EB-9DBE-C857D1E557BA--


From nobody Tue Mar  8 08:06:28 2016
Return-Path: <marc.blanchet@viagenie.ca>
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 D15FA12D7CD for <lager@ietfa.amsl.com>; Tue,  8 Mar 2016 08:06:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Received: from mail.ietf.org ([127.0.0.1]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iNhr_-rBdcfq for <lager@ietfa.amsl.com>; Tue,  8 Mar 2016 08:06:26 -0800 (PST)
Received: from jazz.viagenie.ca (jazz.viagenie.ca [IPv6:2620:0:230:8000::2]) by ietfa.amsl.com (Postfix) with ESMTP id AD31112D7AB for <lager@ietf.org>; Tue,  8 Mar 2016 07:57:31 -0800 (PST)
Received: from [206.123.31.198] (h198.viagenie.ca [206.123.31.198]) by jazz.viagenie.ca (Postfix) with ESMTPSA id 19EC847683 for <lager@ietf.org>; Tue,  8 Mar 2016 10:57:30 -0500 (EST)
From: "Marc Blanchet" <marc.blanchet@viagenie.ca>
To: "lager WG" <lager@ietf.org>
Date: Tue, 08 Mar 2016 15:57:29 +0000
Message-ID: <24D90A7E-081E-4D0D-A384-B99514CCCB5D@viagenie.ca>
References: <20160308155351.25465.62107.idtracker@ietfa.amsl.com>
MIME-Version: 1.0
Content-Type: text/plain; format=flowed
X-Mailer: MailMate (1.9.3r5187)
Archived-At: <http://mailarchive.ietf.org/arch/msg/lager/dXLmromu9LUBtROyYKdZe55XCGc>
Subject: [Lager] Fwd: Publication has been requested for draft-ietf-lager-specification-10
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: Tue, 08 Mar 2016 16:06:27 -0000

FYI,
- shepherd writeup uploaded. Thanks Audric.
- request for publication sent to IESG.

Regards, Marc.

Forwarded message:

> From: Marc Blanchet <Marc.Blanchet@viagenie.ca>
> To: barryleiba@gmail.com
> Cc: audric.schiltknecht@viagenie.ca, iesg-secretary@ietf.org, 
> lager-chairs@ietf.org, Audric Schiltknecht 
> <audric.schiltknecht@viagenie.ca>
> Subject: Publication has been requested for 
> draft-ietf-lager-specification-10
> Date: Tue, 08 Mar 2016 07:53:51 -0800
>
> Marc Blanchet has requested publication of 
> draft-ietf-lager-specification-10 as Proposed Standard on behalf of 
> the LAGER working group.
>
> Please verify the document's state at 
> https://datatracker.ietf.org/doc/draft-ietf-lager-specification/


From nobody Thu Mar 10 05:48:05 2016
Return-Path: <barryleiba@gmail.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 0E6E512D824 for <lager@ietfa.amsl.com>; Thu, 10 Mar 2016 05:45:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.35
X-Spam-Level: 
X-Spam-Status: No, score=-2.35 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.249, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 Zjh8nCrA3vL9 for <lager@ietfa.amsl.com>; Thu, 10 Mar 2016 05:45:21 -0800 (PST)
Received: from mail-yw0-x235.google.com (mail-yw0-x235.google.com [IPv6:2607:f8b0:4002:c05::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E86E912D7A3 for <lager@ietf.org>; Thu, 10 Mar 2016 05:41:59 -0800 (PST)
Received: by mail-yw0-x235.google.com with SMTP id d65so67611871ywb.0 for <lager@ietf.org>; Thu, 10 Mar 2016 05:41:59 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:sender:date:message-id:subject:from:to; bh=KlAIzlZ7RmXqUIXQQNN/BE6h5NFdPonBSWZVjWe7Djw=; b=WbxO5L4m+xAV5PKE5AlrwGLcmeFDPxnSVXsjzpTIvW9orALWqnj8yD5R4tM10xQLHW VG0GbGjYOEIBoC2aAXRoSmvkv/EUhRimpRFSdUFHLrbei2SDUAduenXSNjQ5r9/48aDZ XpGj4R8cvgSlDHUzBKvGzGHuxsE+m1Nbi8LZEJoLKUlt95VpHbDjcAf4pfPLd1Ol62pA ukxOyUb/YiVXBT5lGniKFUIoJ0EBlE8417HFnVxCmqh2lrguGZm0V1Nq2ZLdmw+ob+Bf WZo6rp8ENVM20eE7QayYUWHNmr6zRCwITtTBnR5u158IX3SK2VSNnIblsm1nJFciX8M3 eevQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:date:message-id:subject:from :to; bh=KlAIzlZ7RmXqUIXQQNN/BE6h5NFdPonBSWZVjWe7Djw=; b=PWVBX45a/79tVeGaXy91usri2xenWqah2e7cBdfIjZIiIAJ9GP4RSXkCQ+vlHuwF/W SUcT9LMqFpMzFE97HU3WNVeFf+GmLX5zUByhGtgdHkY5kJRWmJzBWLIN/KV4B+JjMtjz gh3FHNPTmcrgLaSUQ4ONtEhUA3wrdHjQ3j2M5s2w0M3YYd4DYwMduOwC/VEzg0Ke7guK tCBEaeloJjVfgthbrBlUxU9Y0JLkGe09r9e2F1E6EO/l0gHB9OtPaxJkTxZyH77brccW h1sli0OWWP1Q8jd1Khtmbs/335Ad2dCCrRAG61JHNpU+bBV5TvRVqSL2gbYV0r4Fss4B pxoQ==
X-Gm-Message-State: AD7BkJLhF3JaUz7QiCOzjHRFsWAx9JZjL/HFOxsgbKky3g2T1GJuDC+itGrgw4VB5kaDpwhGfjbnw8AnlbNFFA==
MIME-Version: 1.0
X-Received: by 10.129.48.77 with SMTP id w74mr2008253yww.147.1457617319163; Thu, 10 Mar 2016 05:41:59 -0800 (PST)
Sender: barryleiba@gmail.com
Received: by 10.83.78.193 with HTTP; Thu, 10 Mar 2016 05:41:59 -0800 (PST)
Date: Thu, 10 Mar 2016 13:41:59 +0000
X-Google-Sender-Auth: U7Nt7aU2jCwsOuLvl4hucNQTfHI
Message-ID: <CALaySJKTRFUCHrsNFv0ZU_zsBKEHE8MQwH0yQzMKcuZUTu6ybw@mail.gmail.com>
From: Barry Leiba <barryleiba@computer.org>
To: lager@ietf.org
Content-Type: text/plain; charset=UTF-8
Archived-At: <http://mailarchive.ietf.org/arch/msg/lager/9QUr1d98kS_iMHEn5jLnLg1h2dI>
X-Mailman-Approved-At: Thu, 10 Mar 2016 05:48:03 -0800
Subject: Re: [Lager] Publication has been requested for draft-ietf-lager-specification-10
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, 10 Mar 2016 13:45:23 -0000

I've received the publication request for the lager spec, and I plan
to do my AD review on my flights home from ICANN on Friday/Saturday.

Last call will be started after any issues I raise in my AD review
have been addressed, and I expect that to happen next week, so last
call should normally end just before the Buenos Aires meeting.  I
think I'll extend the last call to end after the meeting, just to give
extra time, as there isn't an IESG telechat until 21 April, so we have
time.  I expect the document to be on that agenda, and approved on 21
April.

There'll be an AD changeover in the middle of that, of course, as
Alexey takes over from me, so he will be the one to see the document
through the telechat, approval, and AUTH48.

Barry, ART Director


From nobody Fri Mar 11 10:14:18 2016
Return-Path: <marc.blanchet@viagenie.ca>
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 2A45112D8DC for <lager@ietfa.amsl.com>; Fri, 11 Mar 2016 10:14:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001, 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 3APOqozica6f for <lager@ietfa.amsl.com>; Fri, 11 Mar 2016 10:14:13 -0800 (PST)
Received: from jazz.viagenie.ca (jazz.viagenie.ca [IPv6:2620:0:230:8000::2]) by ietfa.amsl.com (Postfix) with ESMTP id 6769312D6A8 for <lager@ietf.org>; Fri, 11 Mar 2016 10:14:13 -0800 (PST)
Received: from [10.255.255.227] (unknown [207.164.2.174]) by jazz.viagenie.ca (Postfix) with ESMTPSA id E7566403D2 for <lager@ietf.org>; Fri, 11 Mar 2016 13:14:12 -0500 (EST)
From: "Marc Blanchet" <marc.blanchet@viagenie.ca>
To: "lager WG" <lager@ietf.org>
Date: Fri, 11 Mar 2016 13:14:12 -0500
Message-ID: <44802C8E-38D2-4CFA-B292-E2EB52F2DEC1@viagenie.ca>
References: <20160311104527.13444.14623.idtracker@ietfa.amsl.com>
MIME-Version: 1.0
Content-Type: text/plain; format=flowed
X-Mailer: MailMate (1.9.3r5187)
Archived-At: <http://mailarchive.ietf.org/arch/msg/lager/8ieTUnGOaANKU7bREZwQwOwfUko>
Subject: [Lager] Fwd: Telechat update notice: <draft-ietf-lager-specification-10.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: Fri, 11 Mar 2016 18:14:16 -0000

FYI. Marc.

Forwarded message:

> From: IETF Secretariat <ietf-secretariat-reply@ietf.org>
> To: draft-ietf-lager-specification@ietf.org, lager-chairs@ietf.org, 
> audric.schiltknecht@viagenie.ca, iesg-secretary@ietf.org, Audric 
> Schiltknecht <audric.schiltknecht@viagenie.ca>, The IESG 
> <iesg@ietf.org>
> Subject: Telechat update notice: 
> <draft-ietf-lager-specification-10.txt>
> Date: Fri, 11 Mar 2016 02:45:27 -0800
>
> Placed on agenda for telechat - 2016-04-21
> ID Tracker URL: 
> https://datatracker.ietf.org/doc/draft-ietf-lager-specification/


From nobody Sun Mar 13 07:57:20 2016
Return-Path: <barryleiba@gmail.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 0111712D64C; Sun, 13 Mar 2016 07:57:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.35
X-Spam-Level: 
X-Spam-Status: No, score=-2.35 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.249, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 8X_xf8DI-j-T; Sun, 13 Mar 2016 07:57:16 -0700 (PDT)
Received: from mail-yw0-x235.google.com (mail-yw0-x235.google.com [IPv6:2607:f8b0:4002:c05::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9B73612D64B; Sun, 13 Mar 2016 07:57:16 -0700 (PDT)
Received: by mail-yw0-x235.google.com with SMTP id h129so140998405ywb.1; Sun, 13 Mar 2016 07:57:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:sender:date:message-id:subject:from:to:cc; bh=a7sVq+YzqduOM2tKQPiIAOjgizrFfs/NkeblQutqiRU=; b=PXmu6Rutw9jJBa1VzJZRTdZZ+wNyw+OrqLeHoJtIySrEvumwAqe0VDmTk7Ck9zPtcB i5AosXX8Xzlmn+M5BlpglBLJFno/4ZMjJoB9onTKi0/KrwvGYwqWkKTxOMvd9vxhnwnD ITKsXhZ1cQKC+bJ2odHS2tIpA+bsfuA+azZ4F8I5TVDh2NayFC30eBxakFdwqjEf9vo+ GEwKseho8LSlIPFsNxU1ThhPVsgiNcQVsduu04mu4YpBsVZIYOZ0DP5NIK8bPtLqZDuG u+DrazpomViwVmXuO7/XI7NV/rc0+2NjhC0mZtb7LmOpPAfem/XKceZSlefOfmAFYFJH E04Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:date:message-id:subject:from :to:cc; bh=a7sVq+YzqduOM2tKQPiIAOjgizrFfs/NkeblQutqiRU=; b=IJmHF6wXbAz+S6KN1OkIdOd83oB0equfd70KAXmOGQsJmNtKxTmBAwdt9M9hR0rOwH CR8ExBpqj/I+nDxycpI5y44Ye7pE9zAoxmPKS8jH0XycVV59eWP3LzfNrW+moZ08QueA dqSmniWHwyz2McaC9o4McIW8515aslXWjGs8W4w/Pa4sI5JoP1otL1A2D+eAi/2zejQ4 n7202MIYQ3R+4lYaV3ftKzuUxjbtIGWQZJPAMHek/36OkZBUSGNdyh3V6UlwsCXqdlqh 7MYdKXAqP9vYYKl/HKnRr3nr4UL206xgykeO3VjE6pTNV7iZdFZ6VPdVP5NQ8jg5lFQ+ svtg==
X-Gm-Message-State: AD7BkJLNx7Cu7nfVEk+6yd5ioNSstdDJJb7binbPBwajoqMKRr9UvPAskGOjzlg/zd/skLErPbjMilOCGu941g==
MIME-Version: 1.0
X-Received: by 10.129.0.65 with SMTP id 62mr9657590ywa.199.1457881035888; Sun, 13 Mar 2016 07:57:15 -0700 (PDT)
Sender: barryleiba@gmail.com
Received: by 10.83.78.193 with HTTP; Sun, 13 Mar 2016 07:57:15 -0700 (PDT)
Date: Sun, 13 Mar 2016 14:57:15 +0000
X-Google-Sender-Auth: 4DvR2GZRwdRI9DhHAir0D1IvGdg
Message-ID: <CALaySJJP0deDOxCs8YSPr72pfyRUsbZBVE9XO=_4d2AvEhVEtQ@mail.gmail.com>
From: Barry Leiba <barryleiba@computer.org>
To: draft-ietf-lager-specification@ietf.org
Content-Type: text/plain; charset=UTF-8
Archived-At: <http://mailarchive.ietf.org/arch/msg/lager/whczAPI2hNOnKOWD5kScczlYNPE>
Cc: lager@ietf.org
Subject: [Lager] AD review of draft-ietf-lager-specification-10
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: Sun, 13 Mar 2016 14:57:20 -0000

Hi, authors, shepherd, and working group.
Here's my AD review of draft-ietf-lager-specification-10.

I have a lot of comments, but most are just editorial things that I'd
like you to consider, but that won't delay last call.  I'm putting the
few substantive questions up here, and I'd like them answered before
we do last call.  Any other comments you can address before last call,
or in parallel with it.

------------------------

These are the questions/comments that I'd like addressed now:

-- Section 5.3.5 --

   Two contexts may be complementary, as in the following example, which
   shows ARABIC LETTER TEH MARBUTA (U+0629) as a variant of ARABIC
   LETTER ALEF MAKSURA (U+0649), but with two different types.

       <char cp="0647" >
         <var cp="0629" not-when="arabic-final" type="blocked" />
         <var cp="0629" when="arabic-final" type="allocatable" />
       </char>

There's an error here: the text says "ALEF MAKSURA (U+0649)", but the
example says "<char cp="0647" >"

-- Section 6.2.5 --
Am I the only one who doesn't understand the distinction between
"difference" and "symmetric difference"?  I had assumed that
"difference" contained all those in one or the other, but not both...
but that seems to be what "symmetric difference" is (you say it's
xor).  Please explain (to me and in the document).

-- Section 6.3.9 --
I'm confused here, so maybe you can help me understand:
It seems to me that in this example, the ranges are defined in terms
of the "mixed-digits" rule, and that the rule is defined in terms of
the ranges.  How does such a self-referential thing work?

-- Section 8.5 --

   Because of symmetry and transitivity, all variant mappings form
   disjoint sets in which each of them is a variant of all other
   members.

I can't sort this one out.  "Each of them" appears to refer to each
set, and I don't know how a set can be a variant of a member.  But if
I instead assume that "each of them" is meant to refer to "all variant
mappings", then I don't understand what the sets have to do with
anything.  I'm also not following how the disjoint sets are formed in
the first place.  Can you explain/clarify?

-- Section 11.1 --
I'm amazed at how many drafts cite RFC 6838, but have not updated
their registration template to conform with it.  Please see RFC 6838,
Section 5.6, and make sure your template includes everything from
there.  Please also post the updated template and draft name to the
<media-types@ietf.org> list for review (this can be done in parallel
with last call, and doesn't have to delay things, but I'd like it to
be done).

-- Section 11.3 --
For Private Dispositions, what is the registration policy?  First Come
First Served?  You need to say.

-- Section 12 --

   If a system that is querying an identifier list (such as a domain
   zone) that uses the rules in this memo, and those rules are not
   implemented correctly, and that system is relying on the rules being
   applied, the system might fail if the rules are not applied in a
   predictable fashion.  This could cause security problems for the
   querying system.

First, I think you have an extra "that" after the parentheses.
Second, can you be more specific than "This could cause security
problems"?  What sort of problems?  How can they be mitigated?  This
needs to be something more than "bad implementations can result in bad
things."

------------------------

These are the editorial things that can wait:

There are a number of number-agreement errors in the document (for
example, "A conditional context rules is a specialized form of WLE").
The RFC Editor will fix these, so I didn't call them out, but you
should be alert to that and fix them when you run into them.

Also throughout the document, you RECOMMEND listing things in
increasing order.  Remembering that RECOMMEND is synonymous with
SHOULD, which means that implementors need to understnd the
consequences of choosing not to abide by what you say, it's usually
best to explain.  In this case, I presume it's to minimize errors such
as duplication that can occur when things aren't sorted.  I suggest
explaining that once, early in the document somewhere.

-- Section 1 --

   This memo describes a method of using Extensible Markup Language
   (XML) to describe the algorithm used to determine whether a given
   identifier label is permitted, and under which conditions, based on
   the code points it contains and their context.

Total nit: Using "describe" twice in the same sentence is awkward, and
"describes a method ... to describe an algorithm ... to determine
whether ..." also feels awkward.  I'd split the sentence, but you can
take this suggestion or leave it, as you see best (I also prefer
"document" to "memo"):

REPLACEMENT PARAGRAPH
   This document specifies a method of using Extensible Markup Language
   (XML) to describe Label Generation Rulesets (LGRs).  LGRs are
   algorithms used to determine whether, and under what conditions, a
   given identifier label is permitted, based on the code points it
   contains and their context.  These algorithms comprise a list of
   permissible code points, variant code point mappings, and a set of
   rules that act on the code points and mappings.  LGRs form part of
   an administrator's policies.  In deploying internationalized domain
   names (IDNs), they have also been known as IDN tables or variant
   tables.
END

-- Section 2 --
I'm rather a stickler for parallel lists.  The format of this list is
set as "<noun> <has this attribute>", but item four is not parallel
("Provide the ability...").  Can you rephrase it so it is?

-- Section 4.2 --
You say that the "meta" and "rules" elements are optional, and we
assume that "data" is required because you don't say it's optional.
It's easy and clearer to say << This is followed by a required "data"
element ...>>

   A document MUST contain exactly one "lgr" element.  Each "lgr"
   element MUST contain zero or one "meta" element, contain exactly one
   "data" element, and contain zero or one "rules" element; and these
   three elements MUST be in that order.

Another total nit, with no response needed: In the second sentence, I
would remove the second and third "contain".

A minor question: Why are you making the order significant?  Why is
that important?

-- Section 4.3 --

   The "meta" element is RECOMMENDED to express metadata associated
   within the LGR.

This can be read two ways: that the presence of "meta" is recommended,
or that it is recommended that "meta" express something.  I think
you're aiming for the former.  I don't think "within" works here, and
I think you mean "with".  Also, the next section title introduces an
element that wasn't previously mentioned, and I have to look at the
section nesting to realize that it's meant to be a sub-element of
"meta".  I suggest this, with a pargraph break after it:

NEW
   The "meta" element expresses metadata associated with the LGR,
   and the element SHOULD be included.  The following subsections
   describe elements that may appear within the "meta" element.
END

I suggest that you put the element names in quotes in the sub-section titles.

-- Section 4.3.5 --

   The attribute SHOULD be a valid MIME
   type.

You correctly call it a "media type" in the first sentence of the
paragraph; we're trying not to use "MIME type" any more.  Please
change this to "The attribute SHOULD be a valid media type from the
IANA Media Types registry."  (You can optionally include a URL for
that: http://www.iana.org/assignments/media-types )

-- Section 4.3.6 --

   The "validity-start" and "validity-end" elements are OPTIONAL
   elements that describe the time period from which the contents of the
   LGR become valid (i.e. are used in registry policy), and the contents
   of the LGR cease to be used.

You're missing something here:

NEW
   The "validity-start" and "validity-end" elements are OPTIONAL
   elements that describe the time period from which the contents of the
   LGR become valid (are used in registry policy), and time when the
   contents of the LGR cease to be used, respectively.
END

One thing I'm unsure of, and that you might want to carify: When I
read "validity-end", I assume that it's the last valid date, and that
the LGR is valid on that date.  But the description says "the time
when the contents of the LGR cease to be used," which implies that
they are NOT valid on that date.  Which is it?

-- Section 4.3.7 --
Are there global "Unicode properties", or are we always talking about
properties of a specific Unicode character?  You use "character
properties" and "Unicode properties" apparently interchangably.
Please pick one throughout the document (I think "character
properties" is better) and use it consistently, lest people think
you're talking about two different things.

There's a spurious "in" in the first sentence of the second paragraph.

-- Section 5 --

   Discrete permissible code points or code point sequences are declared
   with a "char" element, e.g.

You neither show nor explain how code point sequences are declared
with a "char" element.  I suggest a forward reference, so readers
don't wonder, as I did:

NEW
   Discrete permissible code points or code point sequences are declared
   with a "char" element.  See Section 5.1 for the description of
   sequences.  A single code point example:
END

Or maybe you like this better?:

NEW
   Discrete permissible code points or code point sequences (see Section
   5.1) are declared with a "char" element.  A single code point example:
END

Also, you say that 'A "range" element has no child elements,' but you
say nothing about "char" elements.  Maybe add 'A "char" element may
have cild elements; see the subsections below for further
information.' ?

   Code points must be expressed in uppercase, hexadecimal, and zero
   padded to a minimum of 4 digits.  In other words, they are
   represented according to the standard Unicode convention but without
   the prefix "U+".

I think you kind of bury the lede here, and I would reverse the order
of the description (and, as it's a protocol requirement, I'd use
"MUST"):

NEW
   Code points MUST be represented according to the standard
   Unicode convention but without the prefix "U+": they are
   expressed in uppercase hexadecimal, and are zero-padded
   to a minimum of 4 digits.
END

-- Section 5.1 --

   In addition, doing so allows the choice of
   either specifying a prohibited or a required context.

You need to factor out "specifying" (or repeat it):

NEW
   In addition, doing so allows the choice of
   specifying either a prohibited or a required context.
END

The last paragraph doesn't belong in this section (it has nothing to
do with sequences).  Please move it up to the end of Section 5.

-- Section 5.2 --

May I suggest this?:

OLD
   The content condition is met when
   the rule specified in the "when" attribute is matched.
   Alternatively, a "not-when" attribute may be used for a rule that
   must not be matched.
NEW
   The content condition is met when
   the rule specified in the "when" attribute is matched or when
   the rule specified in the "not-when" attribute fails to match.
END

   In the following example no digit from either range must
   occur in a label that mixes digits from both ranges

"no digit must occur" is hard to parse; please make it "may occur", or
"is allowed" (and I'd put a comma after "ecample").

   If a contextual condition is not satisfied for any code point in a
   label, the label is invalid, see Section 7.5.

This is ambiguous: it can be read to mean that all code points have to
fail in order to make the label invalid (if there is no code point in
the label for which the contextual condition is satisfied).  Let's
rephrase to eliminate the ambiguity:

NEW
   If a label contains one or more core points that fail to satisfy
   a contextual condition, the label is invalid (see Section 7.5).
END

-- Section 5.3.2 --

   Making this relation explicit allows a generalization of the "type"
   attribute from directly reflecting dispositions to a more
   differentiated intermediate value that used in the resolution of
   label disposition.

Is there a missing or extra word around "value that used"?

-- Section 5.3.5 --

   While only a single "when" or "not-when" attribute MUST be applied to
   any "var" element, multiple "var" elements using the same mapping,
   but different "when" or "not-when" attributes MAY be specified.  The
   combination of mapping and conditional context defines a unique
   variant.

I don't think you mean the MUST the way it seems here.  You're not
saying that every "var" MUST have a "when" or a "not-when".  Rather,
you've phrased a MUST NOT as a MUST.  Let's turn it back into MUST
NOT:

NEW
   While a "var" element MUST NOT contain multiple conditions (it
   is only allowed a single "when" or "not-when" attribute), multiple
   "var" elements using the same mapping MAY be specified with
   different "when" or "not-when" attributes.  The combination of
   mapping and conditional context defines a unique variant.
END

-- Section 5.5 --

   Formally, it MUST correspond to
   the XML 1.0 Nmtoken (Name token) production.

Because conforming to Nmtoken is a requirement, it would be good to
have a citation to where in the XML spec Nmtoken is defined.

-- Section 6.2.5 --
I don't understand why "intersection" is limited to two classes: the
intersection of more than two sets is as well defined as the union is.
Please explain (at least to me).

-- Section 6.3 --
Pet peeve (sorry): Correct use of "comprises" is as a symonym of "is
composed of"... so "is comprised of" is, in correct usage, wrong and
nonsensical.  I know this is a lost battle, but I'd feel oh, so much
better if you would change "is comprised of" in Sections 6.3 and
Appendix A to "comprises", so "Each rule is comprised of a series of
matching operators..."

-- Section 7 and subsections --
This was a real slog to get through, and I'm quite sure I didn't
follow a lot of it.  I have to take your word that people who are
actually doing this stuff can follow it and get it right, including
all the variant stuff, including the reflexive variants and the
any-variant vs only-variants vs everything else.  I just can't imagine
needing to do anything complicated with this and actually getting it
right.  (This is just a comment; there's nothing actionable here.)

-- Section 9 --
Nit: in the first sentence, it's "cater to", not "cater for".

The second paragraph is confusing because of the "these" and "those"
and "this", and even the first paragraph suffers from a "these".  The
problem is this: does "these formats" refer to the ones in the cited
RFCs or the ones in this document?  See what I mean?

How about this (and did I get this right?):

NEW
   Both [RFC3743] and [RFC4290] provide different grammars for IDN
   tables.  The formats in those documents are unable to fully cater
   to the increased requirements of contemporary IDN variant policies.

   This specification provides a superset of the functionality
   provided by the older IDN table formats, so any table expressed
   in those formats can be expressed in this new format.  Automated
   conversion can be conducted between tables conformant with the
   grammar specified in each document.
END

-- Section 10 --
Transmission is not transmitted.  The LGR is.

OLD
   Transmission of a well-formed LGR in accordance with this
   specification SHOULD be transmitted with a media type of
   "application/lgr+xml".
NEW
   Well-formed LGRs that comply with this specification SHOULD be
   transmitted with a media type of "application/lgr+xml".
END

-- Section 11.1 --

   The media type "application/lgr+xml" should be registered to denote
   transmission of label generation rulesets that are compliant with
   this specification, in accordance with [RFC6838].

The last phrase is another dangling modifier: to what does it refer?
Put it closer to that:

NEW
   The media type "application/lgr+xml" should be registered in
   accordance with [RFC6838] as the type for transmission of label
   generation rulesets that are compliant with this specification.
END

-- Appendix A --

   In practice, any LGR that includes the hyphen might also contain
   rules invalidating any labels beginning, ending, and containing a
   hyphen in the third and fourth positions as required by [RFC5891].

Mm, then why didn't you put those in the example?  It seems to me that
getting the rules right is the hard part, and that using real-world
examples when you can would be helpful.

-- 
Barry, ART Director


From nobody Sun Mar 13 12:46:07 2016
Return-Path: <marc.blanchet@viagenie.ca>
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 C8CFE12D7C2; Sun, 13 Mar 2016 12:46:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.002
X-Spam-Level: 
X-Spam-Status: No, score=-0.002 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.001, 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 bjJDT915z4pd; Sun, 13 Mar 2016 12:46:05 -0700 (PDT)
Received: from jazz.viagenie.ca (jazz.viagenie.ca [IPv6:2620:0:230:8000::2]) by ietfa.amsl.com (Postfix) with ESMTP id 57A7E12D7C3; Sun, 13 Mar 2016 12:46:03 -0700 (PDT)
Received: from [192.168.1.111] (modemcable093.65-160-184.mc.videotron.ca [184.160.65.93]) by jazz.viagenie.ca (Postfix) with ESMTPSA id 93D7140434; Sun, 13 Mar 2016 15:46:02 -0400 (EDT)
From: "Marc Blanchet" <marc.blanchet@viagenie.ca>
To: "Barry Leiba" <barryleiba@computer.org>
Date: Sun, 13 Mar 2016 15:46:02 -0400
Message-ID: <FAF1B09B-D402-41A9-BFA1-20D45C97809A@viagenie.ca>
In-Reply-To: <CALaySJJP0deDOxCs8YSPr72pfyRUsbZBVE9XO=_4d2AvEhVEtQ@mail.gmail.com>
References: <CALaySJJP0deDOxCs8YSPr72pfyRUsbZBVE9XO=_4d2AvEhVEtQ@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="=_MailMate_3BA3E2A4-9F85-4C1B-AD75-47A2B8B1AC5F_="
Content-Transfer-Encoding: 8bit
X-Mailer: MailMate (1.9.3r5187)
Archived-At: <http://mailarchive.ietf.org/arch/msg/lager/bLKcFRrmRoUWk-5QzVWve2cmsk8>
Cc: draft-ietf-lager-specification@ietf.org, lager@ietf.org
Subject: Re: [Lager] AD review of draft-ietf-lager-specification-10
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: Sun, 13 Mar 2016 19:46:07 -0000

--=_MailMate_3BA3E2A4-9F85-4C1B-AD75-47A2B8B1AC5F_=
Content-Type: text/plain; charset=utf-8; format=flowed; markup=markdown
Content-Transfer-Encoding: 8bit


On 13 Mar 2016, at 10:57, Barry Leiba wrote:

> Hi, authors, shepherd, and working group.
> Here's my AD review of draft-ietf-lager-specification-10.
>
> I have a lot of comments, but most are just editorial things that I'd
> like you to consider, but that won't delay last call.  I'm putting the
> few substantive questions up here, and I'd like them answered before
> we do last call.  Any other comments you can address before last call,
> or in parallel with it.
>
> ------------------------
>
> These are the questions/comments that I'd like addressed now:

responding to one of them.

…
> -- Section 11.1 --
> I'm amazed at how many drafts cite RFC 6838, but have not updated
> their registration template to conform with it.  Please see RFC 6838,
> Section 5.6, and make sure your template includes everything from
> there.  Please also post the updated template and draft name to the
> <media-types@ietf.org>

already done. got some comments. comments incorporated in this version 
of the draft.


Marc.
--=_MailMate_3BA3E2A4-9F85-4C1B-AD75-47A2B8B1AC5F_=
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: quoted-printable

<div class=3D"markdown">
<p dir=3D"auto">On 13 Mar 2016, at 10:57, Barry Leiba wrote:</p>

<blockquote>
<p dir=3D"auto">Hi, authors, shepherd, and working group.<br>
Here's my AD review of draft-ietf-lager-specification-10.</p>

<p dir=3D"auto">I have a lot of comments, but most are just editorial thi=
ngs that I'd<br>
like you to consider, but that won't delay last call.  I'm putting the<br=
>
few substantive questions up here, and I'd like them answered before<br>
we do last call.  Any other comments you can address before last call,<br=
>
or in parallel with it.</p>

<hr>

<p dir=3D"auto">These are the questions/comments that I'd like addressed =
now:</p>
</blockquote>

<p dir=3D"auto">responding to one of them.</p>

<p dir=3D"auto">=E2=80=A6</p>

<blockquote>
<p dir=3D"auto">-- Section 11.1 --<br>
I'm amazed at how many drafts cite RFC 6838, but have not updated<br>
their registration template to conform with it.  Please see RFC 6838,<br>=

Section 5.6, and make sure your template includes everything from<br>
there.  Please also post the updated template and draft name to the<br>
<a href=3D"mailto:media-types@ietf.org">media-types@ietf.org</a></p>
</blockquote>

<p dir=3D"auto">already done. got some comments. comments incorporated in=
 this version of the draft.</p>

<p dir=3D"auto">Marc.</p>

</div>
--=_MailMate_3BA3E2A4-9F85-4C1B-AD75-47A2B8B1AC5F_=--


From nobody Sun Mar 13 20:09:23 2016
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 6D74E12D820; Sun, 13 Mar 2016 20:09:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.719
X-Spam-Level: 
X-Spam-Status: No, score=-2.719 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, 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 foCEFVt-qksJ; Sun, 13 Mar 2016 20:09:20 -0700 (PDT)
Received: from elasmtp-kukur.atl.sa.earthlink.net (elasmtp-kukur.atl.sa.earthlink.net [209.86.89.65]) by ietfa.amsl.com (Postfix) with ESMTP id 07FE012D92E; Sun, 13 Mar 2016 20:09:19 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=ix.netcom.com; b=ma9AngjLPzPMbupxgR0iijXbRo4HdIcI3C5lw9ARIE+7IoDfqGcuLdl3l3Ixejx0; h=Received:From:Subject:To:References:Cc:Message-ID:Date:User-Agent:MIME-Version:In-Reply-To:Content-Type:X-ELNK-Trace:X-Originating-IP;
Received: from [71.35.115.182] (helo=[192.168.1.104]) by elasmtp-kukur.atl.sa.earthlink.net with esmtpa (Exim 4.67) (envelope-from <asmusf@ix.netcom.com>) id 1afIsM-0003MD-Sl; Sun, 13 Mar 2016 23:08:59 -0400
From: Asmus Freytag <asmusf@ix.netcom.com>
To: Barry Leiba <barryleiba@computer.org>, draft-ietf-lager-specification@ietf.org
References: <CALaySJJP0deDOxCs8YSPr72pfyRUsbZBVE9XO=_4d2AvEhVEtQ@mail.gmail.com>
Message-ID: <56E62B63.90805@ix.netcom.com>
Date: Sun, 13 Mar 2016 20:09:23 -0700
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.6.0
MIME-Version: 1.0
In-Reply-To: <CALaySJJP0deDOxCs8YSPr72pfyRUsbZBVE9XO=_4d2AvEhVEtQ@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------020808080405030300090409"
X-ELNK-Trace: 464f085de979d7246f36dc87813833b2857e9f10d2205ddc9c5b621a1aad7e69293993dd2acab7c5350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 71.35.115.182
Archived-At: <http://mailarchive.ietf.org/arch/msg/lager/gIOxiIuZ1uBlzOqTTaE3TeQ505g>
Cc: lager@ietf.org
Subject: Re: [Lager] AD review of draft-ietf-lager-specification-10
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: Mon, 14 Mar 2016 03:09:22 -0000

This is a multi-part message in MIME format.
--------------020808080405030300090409
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit

Barry,

most of your comments are straightforward, and as far as they cover my 
contributions to the text, I'll be happy to make the required tweaks. A 
few were worthy of some comment, in some cases asking whether a proposed 
fix would seem sufficient to you.

On 3/13/2016 7:57 AM, Barry Leiba wrote:
> -- Section 6.2.5 --
> Am I the only one who doesn't understand the distinction between
> "difference" and "symmetric difference"?  I had assumed that
> "difference" contained all those in one or the other, but not both...
> but that seems to be what "symmetric difference" is (you say it's
> xor).  Please explain (to me and in the document).


I have no opinion on whether you are the only one, but the term 
"symmetric-difference" defines what you think of as "difference", while 
the latter term means simply "subtract all the elements of one of the 
sets from their union" (normally you'd expect to see "from the other 
set", but that leaves unspecified how to subtract something that's not 
in a set to begin with).

As these terms can be looked up in Wikipedia, with beautiful Venn 
diagrams, I'm not sure that we should spend time on defining them further.

However, perhaps a simple "(subtraction)" after "difference" will put 
the reader on the right track?

> -- Section 6.3.9 --
> I'm confused here, so maybe you can help me understand:
> It seems to me that in this example, the ranges are defined in terms
> of the "mixed-digits" rule, and that the rule is defined in terms of
> the ranges.  How does such a self-referential thing work?


My guess is that you are thinking the "when" attribute "defines" a range 
in some absolute way.

That is not the case. A when attribute relates to whether a label 
containing a code point from the range will be invalid.

If you think of a range like a procedure declaration, then this 
declaration exists and is independent of the nature of the "when" 
attribute. However, when you evaluate the procedure, the result could be 
a no-op (if the context defined in the when attribute is not met).
(Not-when attributes just use an inverse sense of matching, but 
otherwise there is no difference).

The presence of the when attribute does not affect the association of 
tags to code points, which is part of the declaration.

Hence, the later definition of the context rule ("no-mix..") can refer 
to the tag values without being self-referential.

You are correct, that context rule names are used before the rules are 
declared.

Looking at the text: I think section 5.3.9 is really an example of a 
context rule. So we should move it past 5.4, which covers the context 
rule explicitly for section 5. The text of Section 5.4 could be tweaked 
very slightly to make clear(er) that "action" and "disposition" refer to 
labels that contain a code point with a context rule.

Section 5.3.9 would become new section 5.4.1 and retitled "Example of a 
context rule..."

While we are touching this, mention should be made that rules (without 
anchors) could be used both as context rules and as ordinary rules - in 
principle even in the same LGR; I'm thinking that mention could come in 
either 5.4 or the new 5.4.2 as part of the edits needed to reflect the 
new flow.

> -- Section 8.5 --
>
>     Because of symmetry and transitivity, all variant mappings form
>     disjoint sets in which each of them is a variant of all other
>     members.
>
> I can't sort this one out.  "Each of them" appears to refer to each
> set, and I don't know how a set can be a variant of a member.  But if
> I instead assume that "each of them" is meant to refer to "all variant
> mappings", then I don't understand what the sets have to do with
> anything.  I'm also not following how the disjoint sets are formed in
> the first place.  Can you explain/clarify?


Good catch. Intended was:

    "Because of symmetry and transitivity, all variant mappings form
    disjoint sets. In each of these
    sets, the source and target of each mapping are also variants of the
    sources and targets of all the other mappings. "

The use of "and" is deliberate, otherwise you could get a chain, instead 
of an n (n-1) set of crosswise and reciprocal mappings.

By using "source" and "target" I also avoid having to use "code point or 
sequence".

If I make that change, would it fix your problem, or do we need to touch 
more of the discussion in that section?

> -- Section 4.2 --
>
> A minor question: Why are you making the order significant?  Why is
> that important?


This is perhaps not (entirely) editorial.

There is one strong order dependency in the Schema, which is that 
<action> elements are evaluated in order.
There are several weak order dependencies in the schema that are 
necessary to prevent recursive definitions.
Named rules and classes must be defined before being referenced via 
by-ref, but within that constraint they can be reordered.

There are additional order dependencies that simplify validation 
(logical validation, not schema validation).
Rules referenced in actions (via "match") must be defined; the Unicode 
version must be defined before creating classes based on properties 
(which are version dependent). In a few places, additional 
define-before-use constraints might have been nice but could not be 
implemented. You found the one affecting when rules.

Allowing a more "random" ordering of elements would have been possible, 
but there seems to be no use case for it. Conversely, I'm convinced that 
there's a cost in usability. LGR files that stick to a somewhat 
conventional order can also be processed by general tools, for example, 
to view differences, and not just by special-purpose software.

> -- Section 7 and subsections --
> This was a real slog to get through, and I'm quite sure I didn't
> follow a lot of it.  I have to take your word that people who are
> actually doing this stuff can follow it and get it right, including
> all the variant stuff, including the reflexive variants and the
> any-variant vs only-variants vs everything else.  I just can't imagine
> needing to do anything complicated with this and actually getting it
> right.  (This is just a comment; there's nothing actionable here.)


The complications are very necessary but (primarily) relevant to CJK 
tables, where the full scheme has been in use for a while. It is 
difficult and in fact probably the hardest part of the spec. Took me 
forever to get it all sorted out. :)

> -- Appendix A --
>
>     In practice, any LGR that includes the hyphen might also contain
>     rules invalidating any labels beginning, ending, and containing a
>     hyphen in the third and fourth positions as required by [RFC5891].
>
> Mm, then why didn't you put those in the example?  It seems to me that
> getting the rules right is the hard part, and that using real-world
> examples when you can would be helpful.

I now have access to a worked example of this from a different project, so I may just stick it in.

A./




--------------020808080405030300090409
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta content="text/html; charset=utf-8" http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <div class="moz-cite-prefix">Barry,<br>
      <br>
      most of your comments are straightforward, and as far as they
      cover my contributions to the text, I'll be happy to make the
      required tweaks. A few were worthy of some comment, in some cases
      asking whether a proposed fix would seem sufficient to you.<br>
      <br>
      On 3/13/2016 7:57 AM, Barry Leiba wrote:<br>
    </div>
    <blockquote
cite="mid:CALaySJJP0deDOxCs8YSPr72pfyRUsbZBVE9XO=_4d2AvEhVEtQ@mail.gmail.com"
      type="cite">
      <pre wrap="">-- Section 6.2.5 --
Am I the only one who doesn't understand the distinction between
"difference" and "symmetric difference"?  I had assumed that
"difference" contained all those in one or the other, but not both...
but that seems to be what "symmetric difference" is (you say it's
xor).  Please explain (to me and in the document).</pre>
    </blockquote>
    <font face="Candara"><br>
      <br>
      I have no opinion on whether you are the only one, but the term
      "symmetric-difference" defines what you think of as "difference",
      while the latter term means simply "subtract all the elements of
      one of the sets from their union" (normally you'd expect to see
      "from the other set", but that leaves unspecified how to subtract
      something that's not in a set to begin with).<br>
      <br>
      As these terms can be looked up in Wikipedia, with beautiful Venn
      diagrams, I'm not sure that we should spend time on defining them
      further. <br>
      <br>
      However, perhaps a simple "(subtraction)" after "difference" will
      put the reader on the right track?<br>
    </font><br>
    <pre wrap=""><blockquote type="cite"><pre wrap="">-- Section 6.3.9 --
I'm confused here, so maybe you can help me understand:
It seems to me that in this example, the ranges are defined in terms
of the "mixed-digits" rule, and that the rule is defined in terms of
the ranges.  How does such a self-referential thing work?</pre></blockquote></pre>
    <font face="Candara"><br>
      My guess is that you are thinking the "when" attribute "defines" a
      range in some absolute way.<br>
      <br>
      That is not the case. A when attribute relates to whether a label
      containing a code point from the range will be invalid.<br>
      <br>
      If you think of a range like a procedure declaration, then this
      declaration exists and is independent of the nature of the "when"
      attribute. However, when you evaluate the procedure, the result
      could be a no-op (if the context defined in the when attribute is
      not met).<br>
      (Not-when attributes just use an inverse sense of matching, but
      otherwise there is no difference).<br>
      <br>
      The presence of the when attribute does not affect the association
      of tags to code points, which is part of the declaration.<br>
      <br>
      Hence, the later definition of the context rule ("no-mix..") can
      refer to the tag values without being self-referential.<br>
      <br>
      You are correct, that context rule names are used before the rules
      are declared.<br>
      <br>
      Looking at the text: I think section 5.3.9 is really an example of
      a context rule. So we should move it past 5.4, which covers the
      context rule explicitly for section 5. The text of Section 5.4
      could be tweaked very slightly to make clear(er) that "action" and
      "disposition" refer to labels that contain a code point with a
      context rule.<br>
      <br>
      Section 5.3.9 would become new section 5.4.1 and retitled "Example
      of a context rule..."<br>
      <br>
      While we are touching this, mention should be made that rules
      (without anchors) could be used both as context rules and as
      ordinary rules - in principle even in the same LGR; I'm thinking
      that mention could come in either 5.4 or the new 5.4.2 as part of
      the edits needed to reflect the new flow.</font><br>
    <pre wrap=""><blockquote type="cite"><pre wrap="">-- Section 8.5 --

   Because of symmetry and transitivity, all variant mappings form
   disjoint sets in which each of them is a variant of all other
   members.

I can't sort this one out.  "Each of them" appears to refer to each
set, and I don't know how a set can be a variant of a member.  But if
I instead assume that "each of them" is meant to refer to "all variant
mappings", then I don't understand what the sets have to do with
anything.  I'm also not following how the disjoint sets are formed in
the first place.  Can you explain/clarify?</pre></blockquote></pre>
    <font face="Candara"><br>
      Good catch. Intended was:  <br>
      <br>
    </font>
    <blockquote><font face="Candara">"</font>Because of symmetry and
      transitivity, all variant mappings form disjoint sets. In each of
      these<br>
      sets, the source and target of each mapping are also variants of
      the sources and targets of all the other mappings. <font
        face="Candara">"<br>
        <br>
      </font></blockquote>
    <font face="Candara">The use of "and" is deliberate, otherwise you
      could get a chain, instead of an n (n-1) set of crosswise and
      reciprocal mappings. <br>
      <br>
      By using "source" and "target" I also avoid having to use "code
      point or sequence".<br>
    </font><br>
    If I make that change, would it fix your problem, or do we need to
    touch more of the discussion in that section?<br>
    <br>
    <pre wrap=""><blockquote type="cite"><pre wrap="">-- Section 4.2 --

A minor question: Why are you making the order significant?  Why is
that important?</pre></blockquote></pre>
    <br>
    This is perhaps not (entirely) editorial.<br>
    <font face="Candara"><br>
      There is one strong order dependency in the Schema, which is that
      &lt;action&gt; elements are evaluated in order.<br>
      There are several weak order dependencies in the schema that are
      necessary to prevent recursive definitions.<br>
      Named rules and classes must be defined before being referenced
      via by-ref, but within that constraint they can be reordered.<br>
      <br>
      There are additional order dependencies that simplify validation
      (logical validation, not schema validation).<br>
      Rules referenced in actions (via "match") must be defined; the
      Unicode version must be defined before creating classes based on
      properties (which are version dependent). In a few places,
      additional define-before-use constraints might have been nice but
      could not be implemented. You found the one affecting when rules.<br>
      <br>
      Allowing a more "random" ordering of elements would have been
      possible, but there seems to be no use case for it. Conversely,
      I'm convinced that there's a cost in usability. LGR files that
      stick to a somewhat conventional order can also be processed by
      general tools, for example, to view differences, and not just by
      special-purpose software.<br>
      <br>
    </font>
    <pre wrap=""><blockquote type="cite"><pre wrap="">-- Section 7 and subsections --
This was a real slog to get through, and I'm quite sure I didn't
follow a lot of it.  I have to take your word that people who are
actually doing this stuff can follow it and get it right, including
all the variant stuff, including the reflexive variants and the
any-variant vs only-variants vs everything else.  I just can't imagine
needing to do anything complicated with this and actually getting it
right.  (This is just a comment; there's nothing actionable here.)</pre></blockquote></pre>
    <br>
    The complications are very necessary but (primarily) relevant to CJK
    tables, where the full scheme has been in use for a while. It is
    difficult and in fact probably the hardest part of the spec. Took me
    forever to get it all sorted out. :)<br>
    <br>
    <blockquote type="cite">
      <pre wrap="">-- Appendix A --

   In practice, any LGR that includes the hyphen might also contain
   rules invalidating any labels beginning, ending, and containing a
   hyphen in the third and fourth positions as required by [RFC5891].

Mm, then why didn't you put those in the example?  It seems to me that
getting the rules right is the hard part, and that using real-world
examples when you can would be helpful.</pre>
    </blockquote>
    <pre wrap="">I now have access to a worked example of this from a different project, so I may just stick it in.

</pre>
    A./<br>
    <br>
    <br>
    <br>
  </body>
</html>

--------------020808080405030300090409--


From nobody Sun Mar 13 23:35:37 2016
Return-Path: <duerst@it.aoyama.ac.jp>
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 DF03212D4FF; Sun, 13 Mar 2016 23:35:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.922
X-Spam-Level: 
X-Spam-Status: No, score=-1.922 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=itaoyama.onmicrosoft.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 Mw83jBA5CuGy; Sun, 13 Mar 2016 23:35:32 -0700 (PDT)
Received: from APC01-SG2-obe.outbound.protection.outlook.com (mail-sg2apc01on0119.outbound.protection.outlook.com [104.47.125.119]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5F13012D691; Sun, 13 Mar 2016 23:35:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=itaoyama.onmicrosoft.com; s=selector1-it-aoyama-ac-jp; h=From:To:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=nqBmBPTeg9PH+HWCQbUL8WYeLs8+QyRwgznTY+d/+xA=; b=iN4+8OjkpL+MUj5tMWj0K76XIMpFEo2uHYwOjlr1/alozhjgUr6/ROmerrxMhy5KHeksuhVOAy0PutBKeHb1J1IDOc3jVSiD+6k/3AOFjeWP5mCkYGUT31YWZXA6YZts14MHl76GQPpVnmfiO2ifS/4io33oks2dS2wqAbuiKuc=
Authentication-Results: ietf.org; dkim=none (message not signed) header.d=none;ietf.org; dmarc=none action=none header.from=it.aoyama.ac.jp;
Received: from [133.2.210.64] (133.2.210.64) by TY1PR01MB0921.jpnprd01.prod.outlook.com (10.167.156.151) with Microsoft SMTP Server (TLS) id 15.1.434.11; Mon, 14 Mar 2016 06:35:28 +0000
From: =?UTF-8?Q?Martin_J._D=c3=bcrst?= <duerst@it.aoyama.ac.jp>
To: Asmus Freytag <asmusf@ix.netcom.com>, Barry Leiba <barryleiba@computer.org>, <draft-ietf-lager-specification@ietf.org>
References: <CALaySJJP0deDOxCs8YSPr72pfyRUsbZBVE9XO=_4d2AvEhVEtQ@mail.gmail.com> <56E62B63.90805@ix.netcom.com>
Organization: Aoyama Gakuin University
Message-ID: <56E65BAC.1080008@it.aoyama.ac.jp>
Date: Mon, 14 Mar 2016 15:35:24 +0900
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.6.0
MIME-Version: 1.0
In-Reply-To: <56E62B63.90805@ix.netcom.com>
Content-Type: text/plain; charset="utf-8"; format=flowed
Content-Transfer-Encoding: 8bit
X-Originating-IP: [133.2.210.64]
X-ClientProxiedBy: TY1PR01CA0007.jpnprd01.prod.outlook.com (25.161.131.145) To TY1PR01MB0921.jpnprd01.prod.outlook.com (25.167.156.151)
X-MS-Office365-Filtering-Correlation-Id: af34f8f5-3673-43fd-37b6-08d34bd2d55a
X-Microsoft-Exchange-Diagnostics: 1; TY1PR01MB0921; 2:kzFM5EXFMJ6oZ44DYUWRW7zcWsZVgqyjtBItuMbAZcJ88J/x7WsP56Zs9p5LqPhxXOKCy+J6alnmMFBQBiEOrXCiHp96jexLu93gjGnlBJwAhoNpCLkUbn346jBlHFOO0OrQ8lfh/qU1Zn/iLmmDZXqII1nM+8Nn5LH1jXzCF0AiGN1OO7VrhfPPnKvc/gwk; 3:6oYJMpqZqlSPo5ZVZRPvCrHOC/fvWi0abrEAPyqovHquq/fhh8XDVBPQ9gaBPVrysPJ8cZ8BVcg2ToOiS4ZAQLtEIsie2xZCDaYzm7qIXaucfvEV4H4rPOgSwR19EZxf; 25:wi/aH22x+CO8LH92dObzBe8hg4r/l+WPX6GQDGgBnPCL/ZE0zQY2uis4qsVW4Kk1deA6Qc9gvSkqVAahoyZvF2zt9a9I5Upy7JiG5a0XMzgK5OWBjTpKR19xPwTYBJSjwOpqWWBStimd/CO1iaVX565cc/b15vGVIUBDPHhhInCHUZtDsQPbNdUesLkqI8IsvhV43OpxgGscm4RkbKHRAniVyaqZ1nkyMbQC3GVsEjxjLpJwTFSd+b2lyY84TU3TS928KxHtgsEOTMPd10mC3o/tXd8vAm+2NoXROMhn2rF3zQk9ahp9Y9DT9bbHi+KEkv8T/Y9dEIO+4wpNIJuMiQ==
X-Microsoft-Antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:TY1PR01MB0921;
X-Microsoft-Antispam-PRVS: <TY1PR01MB0921B28B878D8E6528FEA7F1CA880@TY1PR01MB0921.jpnprd01.prod.outlook.com>
X-Exchange-Antispam-Report-Test: UriScan:;
X-Exchange-Antispam-Report-CFA-Test: BCL:0; PCL:0; RULEID:(2401047)(5005006)(8121501046)(10201501046)(3002001); SRVR:TY1PR01MB0921; BCL:0; PCL:0; RULEID:; SRVR:TY1PR01MB0921; 
X-Microsoft-Exchange-Diagnostics: 1; TY1PR01MB0921; 4:Jq0sDn/wDBRDSYM4xIm8ErkQJ+luBmDWbPYfGSCAbM1oYl3lQQ/6beUfmge9zRQyddev3qNsO7f2Xo0fpVrCYRbLoL9V6by9lqE0W4NWjc7Jh24Rwiuv9QkHnhVExPT3B9yT2lD5OlrjJYoeW/bhqTckav01g8i6KzQ0h50R+d6dPHhetS93ovoj/kzeglUQcnbBsSx+IpLJPO8/FbltFg2g9NBN9IP9zo9aI5YivKqyGRb8Rd+WhHXw2jdJn0exVc5fS0JXVzMDSAU9mN0KbjnrrsdwEUC4/2f1auJkpEdgFgdtfVJyLK2PQNRkqdTnUvk6hETl2SFI0AwoiWHk72k+R9aoKJ6hTBpox4Obf4A=
X-Forefront-PRVS: 0881A7A935
X-Forefront-Antispam-Report: SFV:NSPM; SFS:(10019020)(4630300001)(6049001)(6009001)(76104003)(377454003)(24454002)(479174004)(47776003)(2870700001)(81166005)(86362001)(80316001)(77096005)(19580395003)(33656002)(50466002)(65956001)(4326007)(189998001)(6116002)(83506001)(42186005)(66066001)(23676002)(64126003)(3846002)(2950100001)(59896002)(15975445007)(5008740100001)(230783001)(50986999)(76176999)(87266999)(2906002)(5001770100001)(4001350100001)(586003)(65806001)(74482002)(54356999)(1096002)(92566002)(7059030)(3940600001); DIR:OUT; SFP:1102; SCL:1; SRVR:TY1PR01MB0921; H:[133.2.210.64]; FPR:; SPF:None; MLV:sfv; LANG:en; 
X-Microsoft-Exchange-Diagnostics: =?utf-8?B?MTtUWTFQUjAxTUIwOTIxOzIzOlFaSVRqakNpUVRFR2R5czdSRlNGaktMSlc1?= =?utf-8?B?Z1U4QWhmclFKL3ZqSkVTYW5pZFNBNk9VQ0FyMklZSG1nWlNnT29lSFkxTjhN?= =?utf-8?B?UmQrbzREai9lNTVDMm9BdlFMR0pIbE9wcDVNN0RxcFd0UktaMlFTelIxZmsv?= =?utf-8?B?WFpLNVlQNTVmb0o3R1UvdjgwZVpZdk1YR21razROY0lkaEU0QXdlRWtLZXJ6?= =?utf-8?B?eTVUbEUvNndwSmxVdXJ2REl5N1IxTUIvN3NVSDlwcEtTK25JK25NNnZBekRh?= =?utf-8?B?TTQ2QW1LSXhXT2ZXa1pnbTl2QmJiTk45N1lQb2p1NXd3aFNlVG43ZWNHdUhF?= =?utf-8?B?RFZXbEh5VHZWQXNJRzk5T056cjN4TlJPSE9KS25ncXVpdHZDOEtVYTljQmEw?= =?utf-8?B?cTdVOU5NRkVjbEE5elpBMTUyQ3MzejRvQXVRVHlBN1hESVhJbW9ObG5EUXFz?= =?utf-8?B?dzNYOWtObkViVHFDemNEVVlJY0lwOG0wdjkwd3Nwc1hoQ1QrTGpmS1NXREc0?= =?utf-8?B?dEc4N2RwZGFDeGdqTHYrYk1sdnBKQ094Z2RONURJSkMxQXBLQmwxVzB4OVU3?= =?utf-8?B?OGNPbDE5TFBxbHJRM3RYaDM3Z2NOT0RwUWZyU0NtakxIM3R6aGdvYnNlR3F0?= =?utf-8?B?ZHQvZDIvSjJQNzNRUE01SGtFRGJNVnNOTEh1QzE4YXJLRFpCZzZQWDJZbUhL?= =?utf-8?B?bHJMZU91Z0ZCOXQwMXBMYlU0ZEJLRjgrU2RpZGNxUm90eHkvTERLSkF3ZkRZ?= =?utf-8?B?L0xOWmcrQXdldXc1RTBoL3BmYTIxQ0ZqdkFiUTJpOThnTkxvWUI5bUdhU1Nm?= =?utf-8?B?U0tGSkEvSWI4dVlVVFJFa2M1MDRzRGVPNFJSVGV4SHZzdnVmTmphbVU5WjFh?= =?utf-8?B?dnNkZWxoRnQ4eEU0TmJrR0NJMEV6M2wxNGRRcXRKdGtvZ1BZNGp1Vm1IVENk?= =?utf-8?B?eGNocmZYM1lLbjJiMDBZOTVKemdpRTAxR3NWbWRRODZFcUtCNFlBZmVKNkxy?= =?utf-8?B?TEFNMVNWTHVuRXpqcW1JbnV1OG00Z1FPWkdJMU0rbThwM05zVm9wbzdxVk5w?= =?utf-8?B?bllGQVZjQmdiK29xeGNQMFEvNFF6ZjBkMEZEQjQ1OGZzb2VqQUdmbzBkNUpx?= =?utf-8?B?Y0MyNitXdVN0MDlFbk41MWNKWkx6ZVFSRFZBdTl5VVlUSVFCNnBVMFBFc2RV?= =?utf-8?B?ZlhUbmxUanRTRXo5NVJyUCt2TTdVNXNPZ1FmR1ZVemxUd2NVbFlDNDFmWlo1?= =?utf-8?B?cVNnV1I0UnhUaEJUN0lDRmdWQ0ZtVkd2REQxZHZMZXRxdHpVaXNmVk9xeE4w?= =?utf-8?B?YVBET0tMT2pKaldCL0V5UityRzd3Y2NWVDhaMmRhd3BqczhMN2pjTEF1MHVC?= =?utf-8?B?NGNyZE83U1Y0aVF5QWZRSHpmMEptVk1oL0JHeUQ1MDZvOTRxYWZBUmExdkxQ?= =?utf-8?B?VjdQYWZ0SXJvZUNqaWIvdm96Sm9QS2pWaSs5VXU1NFkxalMvRmRsaXFaYWJx?= =?utf-8?B?VmNTQzduR3dpYWl6dmZKWXhrVXV0UHordnFoNFJpVkd6YmtDandjWURIeTNF?= =?utf-8?Q?ekhdMNgtfsCosaI01in/CpSqTZg5QQS20BuQobXPcAlY=3D?=
X-Microsoft-Exchange-Diagnostics: 1; TY1PR01MB0921; 5:NatnGUPp8dHUtrBKx3UdhR8TFguCNsvumSEbUpcwmmoENA1rZSDySSD23c0L19cUDu+JlqQWietKfZMuGI+6BNhix1SUp9TvxoH146XpAesaG3nAtS+DJfWbPrUErL1o8/O4FtcUz5Vh506oe8VwGg==; 24:zJclkaA8zDY/PrJCf7dJgqMLDhT7XC0xNENr8tMZWa055kTY77owIP0VHvqysgRitB53Eee+Q29ZoYEFEQIOQHros94O5UK7ENStZ3XpXYs=
SpamDiagnosticOutput: 1:23
SpamDiagnosticMetadata: NSPM
X-OriginatorOrg: it.aoyama.ac.jp
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 14 Mar 2016 06:35:28.2015 (UTC)
X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted
X-MS-Exchange-Transport-CrossTenantHeadersStamped: TY1PR01MB0921
Archived-At: <http://mailarchive.ietf.org/arch/msg/lager/CmER1fHoHDwl4LfPOhlaK7_sDpU>
Cc: lager@ietf.org
Subject: Re: [Lager] AD review of draft-ietf-lager-specification-10
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: Mon, 14 Mar 2016 06:35:35 -0000

Hello Barry, others,

On 2016/03/14 12:09, Asmus Freytag wrote:

> On 3/13/2016 7:57 AM, Barry Leiba wrote:
>> -- Section 6.2.5 --
>> Am I the only one who doesn't understand the distinction between
>> "difference" and "symmetric difference"?  I had assumed that
>> "difference" contained all those in one or the other, but not both...
>> but that seems to be what "symmetric difference" is (you say it's
>> xor).  Please explain (to me and in the document).

A difference is by its basic meaning never symmetric, because if A is 
*bigger* than B, then B is *smaller* than A, and so on.

> I have no opinion on whether you are the only one,

Me neither. I teach this stuff to undergrads, so I'd definitely have to 
be counted as 'biased'.

> but the term
> "symmetric-difference" defines what you think of as "difference", while
> the latter term means simply "subtract all the elements of one of the
> sets from their union" (normally you'd expect to see "from the other
> set", but that leaves unspecified how to subtract something that's not
> in a set to begin with).

Another way to explain it is that the difference between set A and set B 
is defined as all the elements in A that are not in B.
Formally: A \ B = { x | x∈A ∧ x∉B }
That's a direct definition which avoids to construct the union first.


> As these terms can be looked up in Wikipedia, with beautiful Venn
> diagrams, I'm not sure that we should spend time on defining them further.

Yes indeed, please see https://en.wikipedia.org/wiki/Set_(mathematics).

> However, perhaps a simple "(subtraction)" after "difference" will put
> the reader on the right track?

I suggest "set difference", or "set-theoretic difference". The operation 
is called "subtraction", the result "difference".

Regards,   Martin.


From nobody Mon Mar 14 00:35:19 2016
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 2D7FA12D96C; Mon, 14 Mar 2016 00:35:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.719
X-Spam-Level: 
X-Spam-Status: No, score=-2.719 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, 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 ZBdmOPPz-qnP; Mon, 14 Mar 2016 00:35:13 -0700 (PDT)
Received: from elasmtp-mealy.atl.sa.earthlink.net (elasmtp-mealy.atl.sa.earthlink.net [209.86.89.69]) by ietfa.amsl.com (Postfix) with ESMTP id CDDFC12D939; Mon, 14 Mar 2016 00:35:12 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=ix.netcom.com; b=O0IkQeueC2zCFBpd7ckfqIPw+AkID7txWq5Z/lJzMUm7nIQlc6jOWly/nComfdNV; h=Received:Subject:References:From:To:X-Forwarded-Message-Id:Message-ID:Date:User-Agent:MIME-Version:In-Reply-To:Content-Type:X-ELNK-Trace:X-Originating-IP;
Received: from [71.35.115.182] (helo=[192.168.1.104]) by elasmtp-mealy.atl.sa.earthlink.net with esmtpa (Exim 4.67) (envelope-from <asmusf@ix.netcom.com>) id 1afN1c-0006gp-V8; Mon, 14 Mar 2016 03:34:49 -0400
References: <CALaySJJP0deDOxCs8YSPr72pfyRUsbZBVE9XO=_4d2AvEhVEtQ@mail.gmail.com>
From: Asmus Freytag <asmusf@ix.netcom.com>
To: lager WG <lager@ietf.org>, Barry Leiba <barryleiba@computer.org>, draft-ietf-lager-specification@ietf.org
X-Forwarded-Message-Id: <CALaySJJP0deDOxCs8YSPr72pfyRUsbZBVE9XO=_4d2AvEhVEtQ@mail.gmail.com>
Message-ID: <56E669B1.5090108@ix.netcom.com>
Date: Mon, 14 Mar 2016 00:35:13 -0700
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.6.0
MIME-Version: 1.0
In-Reply-To: <CALaySJJP0deDOxCs8YSPr72pfyRUsbZBVE9XO=_4d2AvEhVEtQ@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------030003020505080800040806"
X-ELNK-Trace: 464f085de979d7246f36dc87813833b2857e9f10d2205ddce1e5a427878d8e70117822dd40f9afdd350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 71.35.115.182
Archived-At: <http://mailarchive.ietf.org/arch/msg/lager/KnXJP-377JmCyL3-hhL7Rz0nY3g>
Subject: [Lager] Fwd:  AD review of draft-ietf-lager-specification-10
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: Mon, 14 Mar 2016 07:35:17 -0000

This is a multi-part message in MIME format.
--------------030003020505080800040806
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit

All,

here are my notes describing the changes in response to the AD review

They do not cover all points raised by Barry - (I've left alone most of 
the ones that involved sections that Kim wrote, except for some minor 
editorial fixes).

The result is uploaded to the GitHub site for Kim to review and add his 
own changes.

A./


-------- Forwarded Message --------
Subject: 	[Lager] AD review of draft-ietf-lager-specification-10
Date: 	Sun, 13 Mar 2016 14:57:15 +0000
From: 	Barry Leiba <barryleiba@computer.org>
To: 	draft-ietf-lager-specification@ietf.org
CC: 	lager@ietf.org



Hi, authors, shepherd, and working group.
Here's my AD review of draft-ietf-lager-specification-10.

I have a lot of comments, but most are just editorial things that I'd
like you to consider, but that won't delay last call.  I'm putting the
few substantive questions up here, and I'd like them answered before
we do last call.  Any other comments you can address before last call,
or in parallel with it.

------------------------

These are the questions/comments that I'd like addressed now:

-- Section 5.3.5 --

    Two contexts may be complementary, as in the following example, which
    shows ARABIC LETTER TEH MARBUTA (U+0629) as a variant of ARABIC
    LETTER ALEF MAKSURA (U+0649), but with two different types.

        <char cp="0647" >
          <var cp="0629" not-when="arabic-final" type="blocked" />
          <var cp="0629" when="arabic-final" type="allocatable" />
        </char>

There's an error here: the text says "ALEF MAKSURA (U+0649)", but the
example says "<char cp="0647" >"

==> changed 0649 to 0647

  -- Section 6.2.5 --
Am I the only one who doesn't understand the distinction between
"difference" and "symmetric difference"?  I had assumed that
"difference" contained all those in one or the other, but not both...
but that seems to be what "symmetric difference" is (you say it's
xor).  Please explain (to me and in the document).

==> added (subtraction) after "difference"

  -- Section 6.3.9 --
I'm confused here, so maybe you can help me understand:
It seems to me that in this example, the ranges are defined in terms
of the "mixed-digits" rule, and that the rule is defined in terms of
the ranges.  How does such a self-referential thing work?

==> Moved 6.3.9 in before section 6.4.1. Touched surrounding text
     to make it flow and added further clarification.
     Also distinguishing "context rule" (anything invoked via "when")
     from parametrized context rule (anything using "anchor")
   
     Affected: sections 6.4, new 6.4.1 (old 6.3.9), new 6.4.2 (old 6.4.1)


  -- Section 8.5 --

    Because of symmetry and transitivity, all variant mappings form
    disjoint sets in which each of them is a variant of all other
    members.

I can't sort this one out.  "Each of them" appears to refer to each
set, and I don't know how a set can be a variant of a member.  But if
I instead assume that "each of them" is meant to refer to "all variant
mappings", then I don't understand what the sets have to do with
anything.  I'm also not following how the disjoint sets are formed in
the first place.  Can you explain/clarify?

==> Because of symmetry and transitivity, all variant mappings form
      disjoint sets. In each of these sets, the source and target of
      each mapping are also variants of
      the sources and targets of all the other mappings. "

(and some rewording of the remainder)



------------------------

These are the editorial things that can wait:

There are a number of number-agreement errors in the document (for
example, "A conditional context rules is a specialized form of WLE").
The RFC Editor will fix these, so I didn't call them out, but you
should be alert to that and fix them when you run into them.

==> fixed the one mentioned

  Also throughout the document, you RECOMMEND listing things in
increasing order.  Remembering that RECOMMEND is synonymous with
SHOULD, which means that implementors need to understnd the
consequences of choosing not to abide by what you say, it's usually
best to explain.  In this case, I presume it's to minimize errors such
as duplication that can occur when things aren't sorted.  I suggest
explaining that once, early in the document somewhere.

==> added that for the recommendation to list class elements in order

-- Section 1 --

    This memo describes a method of using Extensible Markup Language
  (XML) to describe the algorithm used to determine whether a given
    identifier label is permitted, and under which conditions, based on
    the code points it contains and their context.

Total nit: Using "describe" twice in the same sentence is awkward, and
"describes a method ... to describe an algorithm ... to determine
whether ..." also feels awkward.  I'd split the sentence, but you can
take this suggestion or leave it, as you see best (I also prefer
"document" to "memo"):

  REPLACEMENT PARAGRAPH
    This document specifies a method of using Extensible Markup Language
    (XML) to describe Label Generation Rulesets (LGRs).  LGRs are
    algorithms used to determine whether, and under what conditions, a
    given identifier label is permitted, based on the code points it
    contains and their context.  These algorithms comprise a list of
    permissible code points, variant code point mappings, and a set of
    rules that act on the code points and mappings.  LGRs form part of
    an administrator's policies.  In deploying internationalized domain
    names (IDNs), they have also been known as IDN tables or variant
    tables.
END

==> incorporated as is.

-- Section 2 --
I'm rather a stickler for parallel lists.  The format of this list is
set as "<noun> <has this attribute>", but item four is not parallel
("Provide the ability...").  Can you rephrase it so it is?

==> matched preceding "An LGR needs to .." Not super elegant, but parallel.

  -- Section 4.2 --
You say that the "meta" and "rules" elements are optional, and we
assume that "data" is required because you don't say it's optional.
It's easy and clearer to say << This is followed by a required "data"
element ...>>

==> while we state that everything is required unless noted, in this
     case noting the required nature of <data> seems fine.

  A document MUST contain exactly one "lgr" element.  Each "lgr"
    element MUST contain zero or one "meta" element, contain exactly one
    "data" element, and contain zero or one "rules" element; and these
    three elements MUST be in that order.

Another total nit, with no response needed: In the second sentence, I
would remove the second and third "contain".

==> done

A minor question: Why are you making the order significant?  Why is
that important?

==> see discussion - no text changes so far.

  -- Section 4.3 --

    The "meta" element is RECOMMENDED to express metadata associated
    within the LGR.

This can be read two ways: that the presence of "meta" is recommended,
or that it is recommended that "meta" express something.  I think
you're aiming for the former.  I don't think "within" works here, and
I think you mean "with".

==> "within" --> "part of" and associated changes. I also added the
     note: Metadata allow the LGR document to become fully self-documenting,
     for example if rendered in a human readable format by an appropriate tool.

    (I have written such a tool for LGR presentation and by picking up
     the metadata it can eliminate the need secondary documents for all but
     the most complex LGRs)


Also, the next section title introduces an
element that wasn't previously mentioned, and I have to look at the
section nesting to realize that it's meant to be a sub-element of
"meta".  I suggest this, with a pargraph break after it:

NEW
    The "meta" element expresses metadata associated with the LGR,
    and the element SHOULD be included.  The following subsections
    describe elements that may appear within the "meta" element.
END

==> incorporated

  I suggest that you put the element names in quotes in the sub-section titles.

==> not done - we played with "decorating" the section headers but abandoned that.

    My personal preference was to have all <elements> and "attributes"
    decorated as shown in this sentence.



-- Section 4.3.7 --
Are there global "Unicode properties", or are we always talking about
properties of a specific Unicode character?

==> The Unicode standard may drop "character" because in its
      context this is understood, likewise, when it drops the qualifier
      "Unicode" in its context it may be understood.



  You use "character
properties" and "Unicode properties" apparently interchangably.
Please pick one throughout the document (I think "character
properties" is better) and use it consistently, lest people think
you're talking about two different things.

==> There are not that many instances so, for the avoidance of doubt,
     I resolved all of them to "Unicode character properties" except
     if the source (Unicode Standard) appears in the same sentence.

     We want to be very specific that any other source of character
     properties cannot be used with the "property" attribute.

  There's a spurious "in" in the first sentence of the second paragraph.

==> fixed

  -- Section 5 --

    Discrete permissible code points or code point sequences are declared
    with a "char" element, e.g.

You neither show nor explain how code point sequences are declared
with a "char" element.  I suggest a forward reference, so readers
don't wonder, as I did:

NEW
    Discrete permissible code points or code point sequences are declared
    with a "char" element.  See Section 5.1 for the description of
    sequences.  A single code point example:
END

Or maybe you like this better?:

NEW
    Discrete permissible code points or code point sequences (see Section
    5.1) are declared with a "char" element.  A single code point example:
END

==> good suggestion.

  Also, you say that 'A "range" element has no child elements,' but you
say nothing about "char" elements.  Maybe add 'A "char" element may
have cild elements; see the subsections below for further
information.' ?

    Code points must be expressed in uppercase, hexadecimal, and zero
    padded to a minimum of 4 digits.  In other words, they are
    represented according to the standard Unicode convention but without
    the prefix "U+".

I think you kind of bury the lede here, and I would reverse the order
of the description (and, as it's a protocol requirement, I'd use
"MUST"):

NEW
    Code points MUST be represented according to the standard
    Unicode convention but without the prefix "U+": they are
    expressed in uppercase hexadecimal, and are zero-padded
    to a minimum of 4 digits.
END

==>OK

==>Also added language why we recommend ordering the Char entries.

-- Section 5.1 --

    In addition, doing so allows the choice of
    either specifying a prohibited or a required context.

You need to factor out "specifying" (or repeat it):

NEW
    In addition, doing so allows the choice of
    specifying either a prohibited or a required context.
END

==> OK

  The last paragraph doesn't belong in this section (it has nothing to
do with sequences).  Please move it up to the end of Section 5.

==>moved.

  -- Section 5.2 --

May I suggest this?:

OLD
    The content condition is met when
    the rule specified in the "when" attribute is matched.
    Alternatively, a "not-when" attribute may be used for a rule that
    must not be matched.
NEW
    The content condition is met when
    the rule specified in the "when" attribute is matched or when
    the rule specified in the "not-when" attribute fails to match.
END

    In the following example no digit from either range must
    occur in a label that mixes digits from both ranges

"no digit must occur" is hard to parse; please make it "may occur", or
"is allowed" (and I'd put a comma after "ecample").

    If a contextual condition is not satisfied for any code point in a
    label, the label is invalid, see Section 7.5.

This is ambiguous: it can be read to mean that all code points have to
fail in order to make the label invalid (if there is no code point in
the label for which the contextual condition is satisfied).  Let's
rephrase to eliminate the ambiguity:

NEW
    If a label contains one or more core points that fail to satisfy
    a contextual condition, the label is invalid (see Section 7.5).
END

==>OK

-- Section 5.3.2 --

    Making this relation explicit allows a generalization of the "type"
    attribute from directly reflecting dispositions to a more
    differentiated intermediate value that used in the resolution of
    label disposition.

Is there a missing or extra word around "value that used"?

==> yep. Found a few spare ones and put them in.

  -- Section 5.3.5 --

    While only a single "when" or "not-when" attribute MUST be applied to
    any "var" element, multiple "var" elements using the same mapping,
    but different "when" or "not-when" attributes MAY be specified.  The
    combination of mapping and conditional context defines a unique
    variant.

I don't think you mean the MUST the way it seems here.  You're not
saying that every "var" MUST have a "when" or a "not-when".  Rather,
you've phrased a MUST NOT as a MUST.  Let's turn it back into MUST
NOT:

NEW
    While a "var" element MUST NOT contain multiple conditions (it
    is only allowed a single "when" or "not-when" attribute), multiple
    "var" elements using the same mapping MAY be specified with
    different "when" or "not-when" attributes.  The combination of
    mapping and conditional context defines a unique variant.
END

==>OK

-- Section 5.5 --

    Formally, it MUST correspond to
    the XML 1.0 Nmtoken (Name token) production.

Because conforming to Nmtoken is a requirement, it would be good to
have a citation to where in the XML spec Nmtoken is defined.

==> not done - could use help locating

  -- Section 6.2.5 --
I don't understand why "intersection" is limited to two classes: the
intersection of more than two sets is as well defined as the union is.
Please explain (at least to me).

==> we started out allowing only binary (or unary) operators. Unions
     from more than two sets proved a rather common case, so we dropped that
     restriction. However, internally in my tool, for example, I simply record
     that as a fully parenthesized expression involving pairs of classes.

     In over a year of using this schema for writing 40 or so LGRs, I've
     made only very limited use of any other operator. So the use case
     seems to not be there. (And I don't think I've used intersection at all)

     What I observe is that the situation where you define "consonants"
     and "vowels" is more common, than defining "letters" and then
     subtracting the consonants to get the vowels.

     But, having intersection, even if only pairwise, means that if some
     language needs it, any type of set operation can be composed, so
     if that language is notationally a bit more complex, it's not
     crippling.


  -- Section 6.3 --
Pet peeve (sorry): Correct use of "comprises" is as a symonym of "is
composed of"... so "is comprised of" is, in correct usage, wrong and
nonsensical.  I know this is a lost battle, but I'd feel oh, so much
better if you would change "is comprised of" in Sections 6.3 and
Appendix A to "comprises", so "Each rule is comprised of a series of
matching operators..."

==> hope you feel better now

-- Section 7 and subsections --
This was a real slog to get through, and I'm quite sure I didn't
follow a lot of it.  I have to take your word that people who are
actually doing this stuff can follow it and get it right, including
all the variant stuff, including the reflexive variants and the
any-variant vs only-variants vs everything else.  I just can't imagine
needing to do anything complicated with this and actually getting it
right.  (This is just a comment; there's nothing actionable here.)

-- Section 9 --
Nit: in the first sentence, it's "cater to", not "cater for".

==> there seem to be regional differences in prepositions, I changed the verb

  The second paragraph is confusing because of the "these" and "those"
and "this", and even the first paragraph suffers from a "these".  The
problem is this: does "these formats" refer to the ones in the cited
RFCs or the ones in this document?  See what I mean?

How about this (and did I get this right?):

NEW
    Both [RFC3743] and [RFC4290] provide different grammars for IDN
    tables.  The formats in those documents are unable to fully cater
    to the increased requirements of contemporary IDN variant policies.

    This specification provides a superset of the functionality
    provided by the older IDN table formats, so any table expressed
    in those formats can be expressed in this new format.  Automated
    conversion can be conducted between tables conformant with the
    grammar specified in each document.
END

==> OK

  -- Section 10 --
Transmission is not transmitted.  The LGR is.

OLD
    Transmission of a well-formed LGR in accordance with this
    specification SHOULD be transmitted with a media type of
    "application/lgr+xml".
NEW
    Well-formed LGRs that comply with this specification SHOULD be
    transmitted with a media type of "application/lgr+xml".
END


==> OK


-- Appendix A --

    In practice, any LGR that includes the hyphen might also contain
    rules invalidating any labels beginning, ending, and containing a
    hyphen in the third and fourth positions as required by [RFC5891].

Mm, then why didn't you put those in the example?  It seems to me that
getting the rules right is the hard part, and that using real-world
examples when you can would be helpful.

==> because it's supremely ugly :), but I've put it in.

  --
Barry, ART Director

_______________________________________________
Lager mailing list
Lager@ietf.org
https://www.ietf.org/mailman/listinfo/lager




--------------030003020505080800040806
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 8bit

<html>
  <head>

    <meta http-equiv="content-type" content="text/html; charset=utf-8">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    All,<br>
    <br>
    here are my notes describing the changes in response to the AD
    review<br>
    <br>
    They do not cover all points raised by Barry - (I've left alone most
    of the ones that involved sections that Kim wrote, except for some
    minor editorial fixes).<br>
    <br>
    The result is uploaded to the GitHub site for Kim to review and add
    his own changes.<br>
    <br>
    A./<br>
    <div class="moz-forward-container"><br>
      <br>
      -------- Forwarded Message --------
      <table class="moz-email-headers-table" border="0" cellpadding="0"
        cellspacing="0">
        <tbody>
          <tr>
            <th align="RIGHT" nowrap="nowrap" valign="BASELINE">Subject:
            </th>
            <td>[Lager] AD review of draft-ietf-lager-specification-10</td>
          </tr>
          <tr>
            <th align="RIGHT" nowrap="nowrap" valign="BASELINE">Date: </th>
            <td>Sun, 13 Mar 2016 14:57:15 +0000</td>
          </tr>
          <tr>
            <th align="RIGHT" nowrap="nowrap" valign="BASELINE">From: </th>
            <td>Barry Leiba <a class="moz-txt-link-rfc2396E" href="mailto:barryleiba@computer.org">&lt;barryleiba@computer.org&gt;</a></td>
          </tr>
          <tr>
            <th align="RIGHT" nowrap="nowrap" valign="BASELINE">To: </th>
            <td><a class="moz-txt-link-abbreviated" href="mailto:draft-ietf-lager-specification@ietf.org">draft-ietf-lager-specification@ietf.org</a></td>
          </tr>
          <tr>
            <th align="RIGHT" nowrap="nowrap" valign="BASELINE">CC: </th>
            <td><a class="moz-txt-link-abbreviated" href="mailto:lager@ietf.org">lager@ietf.org</a></td>
          </tr>
        </tbody>
      </table>
      <br>
      <br>
      <pre>Hi, authors, shepherd, and working group.
Here's my AD review of draft-ietf-lager-specification-10.

I have a lot of comments, but most are just editorial things that I'd
like you to consider, but that won't delay last call.  I'm putting the
few substantive questions up here, and I'd like them answered before
we do last call.  Any other comments you can address before last call,
or in parallel with it.

------------------------

These are the questions/comments that I'd like addressed now:

-- Section 5.3.5 --

   Two contexts may be complementary, as in the following example, which
   shows ARABIC LETTER TEH MARBUTA (U+0629) as a variant of ARABIC
   LETTER ALEF MAKSURA (U+0649), but with two different types.

       &lt;char cp="0647" &gt;
         &lt;var cp="0629" not-when="arabic-final" type="blocked" /&gt;
         &lt;var cp="0629" when="arabic-final" type="allocatable" /&gt;
       &lt;/char&gt;

There's an error here: the text says "ALEF MAKSURA (U+0649)", but the
example says "&lt;char cp="0647" &gt;"

==&gt; changed 0649 to 0647

 -- Section 6.2.5 --
Am I the only one who doesn't understand the distinction between
"difference" and "symmetric difference"?  I had assumed that
"difference" contained all those in one or the other, but not both...
but that seems to be what "symmetric difference" is (you say it's
xor).  Please explain (to me and in the document).

==&gt; added (subtraction) after "difference"

 -- Section 6.3.9 --
I'm confused here, so maybe you can help me understand:
It seems to me that in this example, the ranges are defined in terms
of the "mixed-digits" rule, and that the rule is defined in terms of
the ranges.  How does such a self-referential thing work?

==&gt; Moved 6.3.9 in before section 6.4.1. Touched surrounding text 
    to make it flow and added further clarification.
    Also distinguishing "context rule" (anything invoked via "when")
    from parametrized context rule (anything using "anchor")
  
    Affected: sections 6.4, new 6.4.1 (old 6.3.9), new 6.4.2 (old 6.4.1)


 -- Section 8.5 --

   Because of symmetry and transitivity, all variant mappings form
   disjoint sets in which each of them is a variant of all other
   members.

I can't sort this one out.  "Each of them" appears to refer to each
set, and I don't know how a set can be a variant of a member.  But if
I instead assume that "each of them" is meant to refer to "all variant
mappings", then I don't understand what the sets have to do with
anything.  I'm also not following how the disjoint sets are formed in
the first place.  Can you explain/clarify?

==&gt; Because of symmetry and transitivity, all variant mappings form 
     disjoint sets. In each of these sets, the source and target of 
     each mapping are also variants of
     the sources and targets of all the other mappings. "

(and some rewording of the remainder)



------------------------

These are the editorial things that can wait:

There are a number of number-agreement errors in the document (for
example, "A conditional context rules is a specialized form of WLE").
The RFC Editor will fix these, so I didn't call them out, but you
should be alert to that and fix them when you run into them.

==&gt; fixed the one mentioned

 Also throughout the document, you RECOMMEND listing things in
increasing order.  Remembering that RECOMMEND is synonymous with
SHOULD, which means that implementors need to understnd the
consequences of choosing not to abide by what you say, it's usually
best to explain.  In this case, I presume it's to minimize errors such
as duplication that can occur when things aren't sorted.  I suggest
explaining that once, early in the document somewhere.

==&gt; added that for the recommendation to list class elements in order

-- Section 1 --

   This memo describes a method of using Extensible Markup Language
 (XML) to describe the algorithm used to determine whether a given
   identifier label is permitted, and under which conditions, based on
   the code points it contains and their context.

Total nit: Using "describe" twice in the same sentence is awkward, and
"describes a method ... to describe an algorithm ... to determine
whether ..." also feels awkward.  I'd split the sentence, but you can
take this suggestion or leave it, as you see best (I also prefer
"document" to "memo"):

 REPLACEMENT PARAGRAPH
   This document specifies a method of using Extensible Markup Language
   (XML) to describe Label Generation Rulesets (LGRs).  LGRs are
   algorithms used to determine whether, and under what conditions, a
   given identifier label is permitted, based on the code points it
   contains and their context.  These algorithms comprise a list of
   permissible code points, variant code point mappings, and a set of
   rules that act on the code points and mappings.  LGRs form part of
   an administrator's policies.  In deploying internationalized domain
   names (IDNs), they have also been known as IDN tables or variant
   tables.
END

==&gt; incorporated as is. 

-- Section 2 --
I'm rather a stickler for parallel lists.  The format of this list is
set as "&lt;noun&gt; &lt;has this attribute&gt;", but item four is not parallel
("Provide the ability...").  Can you rephrase it so it is?

==&gt; matched preceding "An LGR needs to .." Not super elegant, but parallel.

 -- Section 4.2 --
You say that the "meta" and "rules" elements are optional, and we
assume that "data" is required because you don't say it's optional.
It's easy and clearer to say &lt;&lt; This is followed by a required "data"
element ...&gt;&gt;

==&gt; while we state that everything is required unless noted, in this
    case noting the required nature of &lt;data&gt; seems fine.

 A document MUST contain exactly one "lgr" element.  Each "lgr"
   element MUST contain zero or one "meta" element, contain exactly one
   "data" element, and contain zero or one "rules" element; and these
   three elements MUST be in that order.

Another total nit, with no response needed: In the second sentence, I
would remove the second and third "contain".

==&gt; done

A minor question: Why are you making the order significant?  Why is
that important?

==&gt; see discussion - no text changes so far.

 -- Section 4.3 --

   The "meta" element is RECOMMENDED to express metadata associated
   within the LGR.

This can be read two ways: that the presence of "meta" is recommended,
or that it is recommended that "meta" express something.  I think
you're aiming for the former.  I don't think "within" works here, and
I think you mean "with".  

==&gt; "within" --&gt; "part of" and associated changes. I also added the
    note: Metadata allow the LGR document to become fully self-documenting,
    for example if rendered in a human readable format by an appropriate tool.

   (I have written such a tool for LGR presentation and by picking up
    the metadata it can eliminate the need secondary documents for all but
    the most complex LGRs)


Also, the next section title introduces an
element that wasn't previously mentioned, and I have to look at the
section nesting to realize that it's meant to be a sub-element of
"meta".  I suggest this, with a pargraph break after it:

NEW
   The "meta" element expresses metadata associated with the LGR,
   and the element SHOULD be included.  The following subsections
   describe elements that may appear within the "meta" element.
END

==&gt; incorporated

 I suggest that you put the element names in quotes in the sub-section titles.

==&gt; not done - we played with "decorating" the section headers but abandoned that.

   My personal preference was to have all &lt;elements&gt; and "attributes" 
   decorated as shown in this sentence.



-- Section 4.3.7 --
Are there global "Unicode properties", or are we always talking about
properties of a specific Unicode character?

==&gt; The Unicode standard may drop "character" because in its 
     context this is understood, likewise, when it drops the qualifier 
     "Unicode" in its context it may be understood.



 You use "character
properties" and "Unicode properties" apparently interchangably.
Please pick one throughout the document (I think "character
properties" is better) and use it consistently, lest people think
you're talking about two different things.

==&gt; There are not that many instances so, for the avoidance of doubt,
    I resolved all of them to "Unicode character properties" except
    if the source (Unicode Standard) appears in the same sentence.

    We want to be very specific that any other source of character
    properties cannot be used with the "property" attribute.

 There's a spurious "in" in the first sentence of the second paragraph.

==&gt; fixed

 -- Section 5 --

   Discrete permissible code points or code point sequences are declared
   with a "char" element, e.g.

You neither show nor explain how code point sequences are declared
with a "char" element.  I suggest a forward reference, so readers
don't wonder, as I did:

NEW
   Discrete permissible code points or code point sequences are declared
   with a "char" element.  See Section 5.1 for the description of
   sequences.  A single code point example:
END

Or maybe you like this better?:

NEW
   Discrete permissible code points or code point sequences (see Section
   5.1) are declared with a "char" element.  A single code point example:
END

==&gt; good suggestion.

 Also, you say that 'A "range" element has no child elements,' but you
say nothing about "char" elements.  Maybe add 'A "char" element may
have cild elements; see the subsections below for further
information.' ?

   Code points must be expressed in uppercase, hexadecimal, and zero
   padded to a minimum of 4 digits.  In other words, they are
   represented according to the standard Unicode convention but without
   the prefix "U+".

I think you kind of bury the lede here, and I would reverse the order
of the description (and, as it's a protocol requirement, I'd use
"MUST"):

NEW
   Code points MUST be represented according to the standard
   Unicode convention but without the prefix "U+": they are
   expressed in uppercase hexadecimal, and are zero-padded
   to a minimum of 4 digits.
END

==&gt;OK

==&gt;Also added language why we recommend ordering the Char entries.

-- Section 5.1 --

   In addition, doing so allows the choice of
   either specifying a prohibited or a required context.

You need to factor out "specifying" (or repeat it):

NEW
   In addition, doing so allows the choice of
   specifying either a prohibited or a required context.
END

==&gt; OK

 The last paragraph doesn't belong in this section (it has nothing to
do with sequences).  Please move it up to the end of Section 5.

==&gt;moved.

 -- Section 5.2 --

May I suggest this?:

OLD
   The content condition is met when
   the rule specified in the "when" attribute is matched.
   Alternatively, a "not-when" attribute may be used for a rule that
   must not be matched.
NEW
   The content condition is met when
   the rule specified in the "when" attribute is matched or when
   the rule specified in the "not-when" attribute fails to match.
END

   In the following example no digit from either range must
   occur in a label that mixes digits from both ranges

"no digit must occur" is hard to parse; please make it "may occur", or
"is allowed" (and I'd put a comma after "ecample").

   If a contextual condition is not satisfied for any code point in a
   label, the label is invalid, see Section 7.5.

This is ambiguous: it can be read to mean that all code points have to
fail in order to make the label invalid (if there is no code point in
the label for which the contextual condition is satisfied).  Let's
rephrase to eliminate the ambiguity:

NEW
   If a label contains one or more core points that fail to satisfy
   a contextual condition, the label is invalid (see Section 7.5).
END

==&gt;OK

-- Section 5.3.2 --

   Making this relation explicit allows a generalization of the "type"
   attribute from directly reflecting dispositions to a more
   differentiated intermediate value that used in the resolution of
   label disposition.

Is there a missing or extra word around "value that used"?

==&gt; yep. Found a few spare ones and put them in.

 -- Section 5.3.5 --

   While only a single "when" or "not-when" attribute MUST be applied to
   any "var" element, multiple "var" elements using the same mapping,
   but different "when" or "not-when" attributes MAY be specified.  The
   combination of mapping and conditional context defines a unique
   variant.

I don't think you mean the MUST the way it seems here.  You're not
saying that every "var" MUST have a "when" or a "not-when".  Rather,
you've phrased a MUST NOT as a MUST.  Let's turn it back into MUST
NOT:

NEW
   While a "var" element MUST NOT contain multiple conditions (it
   is only allowed a single "when" or "not-when" attribute), multiple
   "var" elements using the same mapping MAY be specified with
   different "when" or "not-when" attributes.  The combination of
   mapping and conditional context defines a unique variant.
END

==&gt;OK

-- Section 5.5 --

   Formally, it MUST correspond to
   the XML 1.0 Nmtoken (Name token) production.

Because conforming to Nmtoken is a requirement, it would be good to
have a citation to where in the XML spec Nmtoken is defined.

==&gt; not done - could use help locating

 -- Section 6.2.5 --
I don't understand why "intersection" is limited to two classes: the
intersection of more than two sets is as well defined as the union is.
Please explain (at least to me).

==&gt; we started out allowing only binary (or unary) operators. Unions 
    from more than two sets proved a rather common case, so we dropped that
    restriction. However, internally in my tool, for example, I simply record
    that as a fully parenthesized expression involving pairs of classes.

    In over a year of using this schema for writing 40 or so LGRs, I've 
    made only very limited use of any other operator. So the use case 
    seems to not be there. (And I don't think I've used intersection at all)

    What I observe is that the situation where you define "consonants"
    and "vowels" is more common, than defining "letters" and then 
    subtracting the consonants to get the vowels.

    But, having intersection, even if only pairwise, means that if some
    language needs it, any type of set operation can be composed, so 
    if that language is notationally a bit more complex, it's not
    crippling.


 -- Section 6.3 --
Pet peeve (sorry): Correct use of "comprises" is as a symonym of "is
composed of"... so "is comprised of" is, in correct usage, wrong and
nonsensical.  I know this is a lost battle, but I'd feel oh, so much
better if you would change "is comprised of" in Sections 6.3 and
Appendix A to "comprises", so "Each rule is comprised of a series of
matching operators..."

==&gt; hope you feel better now

-- Section 7 and subsections --
This was a real slog to get through, and I'm quite sure I didn't
follow a lot of it.  I have to take your word that people who are
actually doing this stuff can follow it and get it right, including
all the variant stuff, including the reflexive variants and the
any-variant vs only-variants vs everything else.  I just can't imagine
needing to do anything complicated with this and actually getting it
right.  (This is just a comment; there's nothing actionable here.)

-- Section 9 --
Nit: in the first sentence, it's "cater to", not "cater for".

==&gt; there seem to be regional differences in prepositions, I changed the verb

 The second paragraph is confusing because of the "these" and "those"
and "this", and even the first paragraph suffers from a "these".  The
problem is this: does "these formats" refer to the ones in the cited
RFCs or the ones in this document?  See what I mean?

How about this (and did I get this right?):

NEW
   Both [RFC3743] and [RFC4290] provide different grammars for IDN
   tables.  The formats in those documents are unable to fully cater
   to the increased requirements of contemporary IDN variant policies.

   This specification provides a superset of the functionality
   provided by the older IDN table formats, so any table expressed
   in those formats can be expressed in this new format.  Automated
   conversion can be conducted between tables conformant with the
   grammar specified in each document.
END

==&gt; OK

 -- Section 10 --
Transmission is not transmitted.  The LGR is.

OLD
   Transmission of a well-formed LGR in accordance with this
   specification SHOULD be transmitted with a media type of
   "application/lgr+xml".
NEW
   Well-formed LGRs that comply with this specification SHOULD be
   transmitted with a media type of "application/lgr+xml".
END


==&gt; OK


-- Appendix A --

   In practice, any LGR that includes the hyphen might also contain
   rules invalidating any labels beginning, ending, and containing a
   hyphen in the third and fourth positions as required by [RFC5891].

Mm, then why didn't you put those in the example?  It seems to me that
getting the rules right is the hard part, and that using real-world
examples when you can would be helpful.

==&gt; because it's supremely ugly :), but I've put it in.

 -- 
Barry, ART Director

_______________________________________________
Lager mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Lager@ietf.org">Lager@ietf.org</a>
<a class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/lager">https://www.ietf.org/mailman/listinfo/lager</a>

</pre>
      <br>
    </div>
    <br>
  </body>
</html>

--------------030003020505080800040806--


From nobody Mon Mar 14 10:52:24 2016
Return-Path: <barryleiba@gmail.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 29FF812D6A7; Mon, 14 Mar 2016 10:52:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.35
X-Spam-Level: 
X-Spam-Status: No, score=-2.35 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.249, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 v7k0r-QinHHw; Mon, 14 Mar 2016 10:52:21 -0700 (PDT)
Received: from mail-yw0-x229.google.com (mail-yw0-x229.google.com [IPv6:2607:f8b0:4002:c05::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 78D9512DC4D; Mon, 14 Mar 2016 10:52:18 -0700 (PDT)
Received: by mail-yw0-x229.google.com with SMTP id h129so177424872ywb.1; Mon, 14 Mar 2016 10:52:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc; bh=+YtunaSMgB8sx0qjiuUM3+MRh6GVNU8ACc/FxB1xtac=; b=yoz6dOQofx/ztMjn0tZgCPA2XyHXRjgUC+9Jj74xw4y8QHLzE6gVVsgsHmhROntzTK OZ3835g1l2a9Lo5ZaQ6CYTcLtEenOnbra+/ZFDc9zm/w8l1rYg4EIvKbz7NG8LRiXjdm OccuvFwFP2a7Q14rvnxEq5UhwV4QR4KoQKOXu/vk/mJNEpcV79Y4lOeCoK3TNaPHVjoN ONwpCyaZ/yu6JAa0ZR/q5JJI7zAvbh7M7D/TvzdlCKf3xWOnJpUPKQEXsHR/XZ0n65CV lY/gDmgGTfluNYNZtqv6LmeQkZniyg5DC7B9WMUIOWYD8V4r914IYGCROQAMyIwIdFaf esiQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:date :message-id:subject:from:to:cc; bh=+YtunaSMgB8sx0qjiuUM3+MRh6GVNU8ACc/FxB1xtac=; b=Sd5VMfdwWQSsVlgH1r8+iNnqiYJPKUyZpgx8r9WiHRv5LdDeeaKiyPGmrT5gISAhfS 3arKAB5A6T3P44q5CS9oBuvP6NwwXV0wQuaoJHZ8ZII8IixnkB44O1HLfX0tJsw9q7OK qh1De462q8KdZ2C20n5VFW48LnIsg0xxz21kepzCVxphK276Jw3F7iI6ig7zOjd1GQgc uOob1Woik9kZHk6UuH9sokQYAd2wclZEyz1FwKpj1DtF+B5240kBwPZiU0y7B2PWu+zQ fUvPtDsRbrQ/J7CAiYpBtX2nyZjQi17Sy3MfOuizIatdS9Mhgi0F0/pvK+2FdTOWUWPN GxAA==
X-Gm-Message-State: AD7BkJITSRRzDZwd38L8rp3Gf4w4sGDkBtQw1fSjqt4jRbhq3qa2CgW638eP/uTQIuBiha9VFIyHvohIQvBvaQ==
MIME-Version: 1.0
X-Received: by 10.129.48.77 with SMTP id w74mr14343228yww.147.1457977937607; Mon, 14 Mar 2016 10:52:17 -0700 (PDT)
Sender: barryleiba@gmail.com
Received: by 10.83.78.193 with HTTP; Mon, 14 Mar 2016 10:52:17 -0700 (PDT)
In-Reply-To: <56E6253A.9040605@ix.netcom.com>
References: <CALaySJJP0deDOxCs8YSPr72pfyRUsbZBVE9XO=_4d2AvEhVEtQ@mail.gmail.com> <56E6253A.9040605@ix.netcom.com>
Date: Mon, 14 Mar 2016 17:52:17 +0000
X-Google-Sender-Auth: oyty_-AaQZdGsP20dxshWU4hD5U
Message-ID: <CALaySJ+ULx1=dHTaeyheCaf25TQ=evR3tD3AW_chavDk7V4gQQ@mail.gmail.com>
From: Barry Leiba <barryleiba@computer.org>
To: "Asmus Freytag (t)" <asmus-inc@ix.netcom.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: <http://mailarchive.ietf.org/arch/msg/lager/RqL53WXFfCTHg4sAeWnscqL-NvY>
Cc: draft-ietf-lager-specification@ietf.org, lager@ietf.org
Subject: Re: [Lager] AD review of draft-ietf-lager-specification-10
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: Mon, 14 Mar 2016 17:52:23 -0000

Hi, Asmus, and thanks for the quick response.  I'm only leaving things
below that I think need my further response.  Summary: we're good
here.

>> Am I the only one who doesn't understand the distinction between
>> "difference" and "symmetric difference"?  I had assumed that
>> "difference" contained all those in one or the other, but not both...
>> but that seems to be what "symmetric difference" is (you say it's
>> xor).  Please explain (to me and in the document).
>
> I have no opinion on whether you are the only one, but the term
> "symmetric-difference" defines what you think of as "difference", while the
> latter term means simply "subtract all the elements of one of the sets from
> their union" (normally you'd expect to see "from the other set", but that
> leaves unspecified how to subtract something that's not in a set to begin
> with).

Ah, I see... my confusion was in forgetting that the order of the
elements is significant, so that it's well defined.  You can probably
leave it as it is, though I'll suggest an update anyway:

OLD
   Classes may be combined using operators for set complement, union,
   intersection, difference and symmetric difference (exclusive-or).
NEW
   Classes may be combined using operators for set complement, union,
   intersection, difference (elements of the first class that are not in the
  second) and symmetric difference (elements in either class, but not
   both).
END

>> -- Section 6.3.9 --
>> I'm confused here, so maybe you can help me understand:
>> It seems to me that in this example, the ranges are defined in terms
>> of the "mixed-digits" rule, and that the rule is defined in terms of
>> the ranges.  How does such a self-referential thing work?
>
> My guess is that you are thinking the "when" attribute "defines" a range in
> some absolute way.

Yes, I was.

> That is not the case. A when attribute relates to whether a label containing
> a code point from the range will be invalid.
...
> The presence of the when attribute does not affect the association of tags
> to code points, which is part of the declaration.

OK, understood.
Your other comments about moving some text around sound right, but
you've answered my question here, and I think we're fine.

>> -- Section 8.5 --
>>
>>    Because of symmetry and transitivity, all variant mappings form
>>    disjoint sets in which each of them is a variant of all other
>>    members.
>>
>> I can't sort this one out.  "Each of them" appears to refer to each
>> set, and I don't know how a set can be a variant of a member.  But if
>> I instead assume that "each of them" is meant to refer to "all variant
>> mappings", then I don't understand what the sets have to do with
>> anything.  I'm also not following how the disjoint sets are formed in
>> the first place.  Can you explain/clarify?
>
> Good catch. Intended was:
>
> "Because of symmetry and transitivity, all variant mappings form disjoint
> sets. In each of these
> sets, the source and target of each mapping are also variants of the sources
> and targets of all the other mappings. "
>
> The use of "and" is deliberate, otherwise you could get a chain, instead of
> an n (n-1) set of crosswise and reciprocal mappings.
>
> By using "source" and "target" I also avoid having to use "code point or
> sequence".
>
> If I make that change, would it fix your problem, or do we need to touch
> more of the discussion in that section?

Yes, I think your suggested change works.

>> -- Section 4.2 --
>>
>> A minor question: Why are you making the order significant?  Why is
>> that important?
>
> This is perhaps not (entirely) editorial.
>
> There is one strong order dependency in the Schema, which is that <action>
> elements are evaluated in order.
> There are several weak order dependencies in the schema that are necessary
> to prevent recursive definitions.
> Named rules and classes must be defined before being referenced via by-ref,
> but within that constraint they can be reordered.
>
> There are additional order dependencies that simplify validation (logical
> validation, not schema validation).
...
> Allowing a more "random" ordering of elements would have been possible, but
> there seems to be no use case for it. Conversely, I'm convinced that there's
> a cost in usability. LGR files that stick to a somewhat conventional order
> can also be processed by general tools, for example, to view differences,
> and not just by special-purpose software.

Thanks for the explanation, and I'm quite convinced.  No change here.

Barry


From nobody Mon Mar 14 11:13:47 2016
Return-Path: <barryleiba@gmail.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 12EBC12D68C; Mon, 14 Mar 2016 11:13:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.35
X-Spam-Level: 
X-Spam-Status: No, score=-2.35 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.249, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 spbJPPdKU9jB; Mon, 14 Mar 2016 11:13:44 -0700 (PDT)
Received: from mail-yw0-x22e.google.com (mail-yw0-x22e.google.com [IPv6:2607:f8b0:4002:c05::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8C72C12D6DC; Mon, 14 Mar 2016 11:05:16 -0700 (PDT)
Received: by mail-yw0-x22e.google.com with SMTP id h129so177917835ywb.1; Mon, 14 Mar 2016 11:05:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc; bh=Oz3p6W8ub3zMuiItha/9WD+EJPZWWAjPy5G3dVGlnzU=; b=YWQharUIHZk7mHqvgyocOF+SyIDO42MbfpFilGEhDCL4p5rAB/gGmh2eRmo6GUG0Nn ZI3sFOBlJ2bqelW2O3Bfv8M4leIx/OETG4J7YFh+iPfB4E8/n7Gc+JXtcwhZgOCcF/ZZ ufyFkxWRb0B55pdhTd8U/mGxJU6gcZMA8yp81/nYRlpgg46vhDlj8ZnGM92I9zylfxcN 92q891aa+5lrD1t3w8VBVTK2QxhsPvmZjhuoBrPDuFVYf0yKUdCywCF3eyaAImzU93KT h898Mlc8c+UHExkXfBUL+EQMziAXPeP9Zt2FHkbghic8TxET9jYSgXSNzv3VZ057iBeS tO+Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:date :message-id:subject:from:to:cc; bh=Oz3p6W8ub3zMuiItha/9WD+EJPZWWAjPy5G3dVGlnzU=; b=WTGzCx+TkP0yQXaR6o/vh7BSsg75ILqC9tK8nSrvSVOOTqb4aUAoUilqOj6u54w338 PlP4TO0tpofc22w2uXhA8wxMC0OPxzqbxJRBWknn+GLjvFdQRwJwZbHc+m7He/E54d6E x4wcLPEjVKVxMeuj2nbNZ0MMVoWGpyxLj/u+EMtzI00OOBKH18C2E3OZb5OWLOul9f+B 1NFxWwKkaV2TI5XU9JeFUVAD3w4VVjNYf8yZDgeLbE13NBqEwMTRc6HpfqC2F8E5Q1W+ oGB2mnTH8bEYr4PYs4gFXXRt7N/C/foIsRFd0QW0JF2A0RFXc+APBv+oZVbMCWjuNkcu KQgg==
X-Gm-Message-State: AD7BkJLOuVlfx91dXTeBmgp9RXYk4/R1jEuJFPrfZow/V6rv6zyHKJXdwgHpR1zwkKxDzAxg02UZtdGuWLEbpA==
MIME-Version: 1.0
X-Received: by 10.37.20.195 with SMTP id 186mr13726250ybu.60.1457978715742; Mon, 14 Mar 2016 11:05:15 -0700 (PDT)
Sender: barryleiba@gmail.com
Received: by 10.83.78.193 with HTTP; Mon, 14 Mar 2016 11:05:15 -0700 (PDT)
In-Reply-To: <56E669B1.5090108@ix.netcom.com>
References: <CALaySJJP0deDOxCs8YSPr72pfyRUsbZBVE9XO=_4d2AvEhVEtQ@mail.gmail.com> <56E669B1.5090108@ix.netcom.com>
Date: Mon, 14 Mar 2016 18:05:15 +0000
X-Google-Sender-Auth: 7KhYyKxr-sW0c1LorUpYYzBNRk0
Message-ID: <CALaySJ+23n0RxvHNE7jCx4Msy5-2m0t=Z=GiPuw3wMPaX7xpjw@mail.gmail.com>
From: Barry Leiba <barryleiba@computer.org>
To: Asmus Freytag <asmusf@ix.netcom.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: <http://mailarchive.ietf.org/arch/msg/lager/lcQwR4An_MynE9JkAhil5dlrdPk>
Cc: draft-ietf-lager-specification@ietf.org, lager WG <lager@ietf.org>
Subject: Re: [Lager] AD review of draft-ietf-lager-specification-10
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: Mon, 14 Mar 2016 18:13:46 -0000

> -- Section 5.3.5 --
>
>    Two contexts may be complementary, as in the following example, which
>    shows ARABIC LETTER TEH MARBUTA (U+0629) as a variant of ARABIC
>    LETTER ALEF MAKSURA (U+0649), but with two different types.
>
>        <char cp="0647" >
>          <var cp="0629" not-when="arabic-final" type="blocked" />
>          <var cp="0629" when="arabic-final" type="allocatable" />
>        </char>
>
> There's an error here: the text says "ALEF MAKSURA (U+0649)", but the
> example says "<char cp="0647" >"
>
> ==> changed 0649 to 0647

Is that the right direction?  Unicode says that U+0647 is ARABIC
LETTER HEH, and that U+0649 is ARABIC LETTER ALEF MAKSURA.

>  I suggest that you put the element names in quotes in the sub-section titles.
>
> ==> not done - we played with "decorating" the section headers but abandoned that.

OK.

> Is there a missing or extra word around "value that used"?
>
> ==> yep. Found a few spare ones and put them in.

:-)

> -- Section 5.5 --
>
>    Formally, it MUST correspond to
>    the XML 1.0 Nmtoken (Name token) production.
>
> Because conforming to Nmtoken is a requirement, it would be good to
> have a citation to where in the XML spec Nmtoken is defined.
>
> ==> not done - could use help locating

Sure:
NEW
   Formally, it MUST correspond to the XML 1.0 Nmtoken (Name token)
   production (see [XML] Section 2.3).
END

>  -- Section 6.2.5 --
> I don't understand why "intersection" is limited to two classes: the
> intersection of more than two sets is as well defined as the union is.
> Please explain (at least to me).

Your explanation works for me; no change here.

>  -- Section 6.3 --
> Pet peeve (sorry): Correct use of "comprises" [...]
...
> ==> hope you feel better now

Much, and I'm ever grateful.

Barry


From nobody Mon Mar 14 13:59:50 2016
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 CA96412D714; Mon, 14 Mar 2016 13:59:48 -0700 (PDT)
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 uXk59pLD4n_g; Mon, 14 Mar 2016 13:59:47 -0700 (PDT)
Received: from elasmtp-masked.atl.sa.earthlink.net (elasmtp-masked.atl.sa.earthlink.net [209.86.89.68]) by ietfa.amsl.com (Postfix) with ESMTP id 2B5F612D6C4; Mon, 14 Mar 2016 13:59:47 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=ix.netcom.com; b=Kb2QUjMEn0GUYd2+vizdncLmMHKoKy0RyaAqQcXltjlZyd9ulhSaQWpg1p3JNs5s; h=Received:Subject:To:References:Cc:From:Message-ID:Date:User-Agent:MIME-Version:In-Reply-To:Content-Type:Content-Transfer-Encoding:X-ELNK-Trace:X-Originating-IP;
Received: from [4.35.247.19] (helo=[172.31.99.19]) by elasmtp-masked.atl.sa.earthlink.net with esmtpa (Exim 4.67) (envelope-from <asmusf@ix.netcom.com>) id 1afZaG-0005a2-5U; Mon, 14 Mar 2016 16:59:24 -0400
To: Barry Leiba <barryleiba@computer.org>
References: <CALaySJJP0deDOxCs8YSPr72pfyRUsbZBVE9XO=_4d2AvEhVEtQ@mail.gmail.com> <56E669B1.5090108@ix.netcom.com> <CALaySJ+23n0RxvHNE7jCx4Msy5-2m0t=Z=GiPuw3wMPaX7xpjw@mail.gmail.com>
From: Asmus Freytag <asmusf@ix.netcom.com>
Message-ID: <56E72646.9080607@ix.netcom.com>
Date: Mon, 14 Mar 2016 13:59:50 -0700
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.6.0
MIME-Version: 1.0
In-Reply-To: <CALaySJ+23n0RxvHNE7jCx4Msy5-2m0t=Z=GiPuw3wMPaX7xpjw@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
X-ELNK-Trace: 464f085de979d7246f36dc87813833b2857e9f10d2205ddc8dab008232ce03bcc285eb9adc178b4a350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 4.35.247.19
Archived-At: <http://mailarchive.ietf.org/arch/msg/lager/rv0uUeR2cPw7ZUiXdh9c3TiVmco>
Cc: draft-ietf-lager-specification@ietf.org, lager WG <lager@ietf.org>
Subject: Re: [Lager] AD review of draft-ietf-lager-specification-10
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: Mon, 14 Mar 2016 20:59:49 -0000

Kim,

two items I am passing to you:

On 3/14/2016 11:05 AM, Barry Leiba wrote:
>> -- Section 5.3.5 --
>> >
>> >    Two contexts may be complementary, as in the following example, which
>> >    shows ARABIC LETTER TEH MARBUTA (U+0629) as a variant of ARABIC
>> >    LETTER ALEF MAKSURA (U+0649), but with two different types.
>> >
>> >        <char cp="0647" >
>> >          <var cp="0629" not-when="arabic-final" type="blocked" />
>> >          <var cp="0629" when="arabic-final" type="allocatable" />
>> >        </char>
>> >
>> >There's an error here: the text says "ALEF MAKSURA (U+0649)", but the
>> >example says "<char cp="0647" >"
>> >
>> >==> changed 0649 to 0647
> Is that the right direction?  Unicode says that U+0647 is ARABIC
> LETTER HEH, and that U+0649 is ARABIC LETTER ALEF MAKSURA.

 From the Root zone LGR:

  <char cp="0629" tag="sc:Arab" ref="0 100">
       <var cp="0647" type="allocatable" comment="In the Arabic 
language, U+0647 HEH may be substituted for U+0629 TEH MARBUTA. [RFC 
6365]" />

so it should be U+0647 and  ARABIC LETTER HEH...I missed fixing the name.

Kim, can you make this change?

(aside: the root zone LGR gave up on this kind of mutually-exclusive 
conditional context for positional variants because we found the task of 
verifying them mechanically to be intractable in the general case - 
however, there are different types of contexts in other scripts that are 
much more straightforward and that aren't as problematic, hence the 
warning instead of a request to remove the feature.)
>
>> >-- Section 5.5 --
>> >
>> >    Formally, it MUST correspond to
>> >    the XML 1.0 Nmtoken (Name token) production.
>> >
>> >Because conforming to Nmtoken is a requirement, it would be good to
>> >have a citation to where in the XML spec Nmtoken is defined.
>> >
>> >==> not done - could use help locating
> Sure:
> NEW
>     Formally, it MUST correspond to the XML 1.0 Nmtoken (Name token)
>     production (see [XML] Section 2.3).
> END
Kim, can you make that change?

A./


From nobody Sun Mar 20 13:57:59 2016
Return-Path: <kim.davies@icann.org>
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 A167D12D515; Sun, 20 Mar 2016 13:57:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.202
X-Spam-Level: 
X-Spam-Status: No, score=-4.202 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, 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 NcZ-PILbjoTb; Sun, 20 Mar 2016 13:57:57 -0700 (PDT)
Received: from out.west.pexch112.icann.org (pfe112-ca-2.pexch112.icann.org [64.78.40.10]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 391C012D67D; Sun, 20 Mar 2016 13:57:57 -0700 (PDT)
Received: from PMBX112-W1-CA-1.pexch112.icann.org (64.78.40.21) by PMBX112-W1-CA-1.pexch112.icann.org (64.78.40.21) with Microsoft SMTP Server (TLS) id 15.0.1130.7; Sun, 20 Mar 2016 13:57:54 -0700
Received: from PMBX112-W1-CA-1.pexch112.icann.org ([64.78.40.21]) by PMBX112-W1-CA-1.PEXCH112.ICANN.ORG ([64.78.40.21]) with mapi id 15.00.1130.005; Sun, 20 Mar 2016 13:57:54 -0700
From: Kim Davies <kim.davies@icann.org>
To: Barry Leiba <barryleiba@computer.org>, "draft-ietf-lager-specification@ietf.org" <draft-ietf-lager-specification@ietf.org>
Thread-Topic: AD review of draft-ietf-lager-specification-10
Thread-Index: AQHRfTiyomeU8bg86U2xZ0g25xsim59i2+YA
Date: Sun, 20 Mar 2016 20:57:54 +0000
Message-ID: <6B052A27-0C6C-4B2A-807D-41D7FDCFB537@icann.org>
References: <CALaySJJP0deDOxCs8YSPr72pfyRUsbZBVE9XO=_4d2AvEhVEtQ@mail.gmail.com>
In-Reply-To: <CALaySJJP0deDOxCs8YSPr72pfyRUsbZBVE9XO=_4d2AvEhVEtQ@mail.gmail.com>
Accept-Language: en-AU, en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/0.0.0.160212
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [192.0.32.234]
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha256; boundary="B_3541327074_1656648188"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/lager/kveiaRqPEiDZTYakaYOzv7Xxw6Y>
Cc: "lager@ietf.org" <lager@ietf.org>
Subject: Re: [Lager] AD review of draft-ietf-lager-specification-10
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: Sun, 20 Mar 2016 20:57:58 -0000

--B_3541327074_1656648188
Content-type: text/plain;
	charset="UTF-8"
Content-transfer-encoding: 7bit

Hi Barry, Hi all,

On 3/13/16, 7:57 AM, "barryleiba@gmail.com on behalf of Barry Leiba" <barryleiba@gmail.com on behalf of barryleiba@computer.org> wrote:

>Hi, authors, shepherd, and working group.
>Here's my AD review of draft-ietf-lager-specification-10.

Asmus and I have implemented this feedback into a revised -11 draft that
is ready to post, except for one outstanding issue:

>-- Section 12 --
>
>   If a system that is querying an identifier list (such as a domain
>   zone) that uses the rules in this memo, and those rules are not
>   implemented correctly, and that system is relying on the rules being
>   applied, the system might fail if the rules are not applied in a
>   predictable fashion.  This could cause security problems for the
>   querying system.
>
>First, I think you have an extra "that" after the parentheses.
>Second, can you be more specific than "This could cause security
>problems"?  What sort of problems?  How can they be mitigated?  This
>needs to be something more than "bad implementations can result in bad
>things."

I agree this paragraph essentially means bad implementations can result in
bad things. I don't have a proposed approach on how to mitigate this general
situation other than to follow the specification. Perhaps it makes the most
sense simply to strike this entire paragraph unless anyone has suggestions
on alternative wording.

kim
--B_3541327074_1656648188
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"

MIIRxgYJKoZIhvcNAQcCoIIRtzCCEbMCAQExDzANBglghkgBZQMEAgEFADALBgkqhkiG9w0B
BwGggg97MIIFajCCBFKgAwIBAgIQAzf9pnruIxQ3CluP694WujANBgkqhkiG9w0BAQsFADBl
MQswCQYDVQQGEwJVUzEVMBMGA1UEChMMRGlnaUNlcnQgSW5jMRkwFwYDVQQLExB3d3cuZGln
aWNlcnQuY29tMSQwIgYDVQQDExtEaWdpQ2VydCBTSEEyIEFzc3VyZWQgSUQgQ0EwHhcNMTUw
MzMxMDAwMDAwWhcNMTgwMzMxMTIwMDAwWjCBizELMAkGA1UEBhMCVVMxEzARBgNVBAgTCkNh
bGlmb3JuaWExFDASBgNVBAcTC0xvcyBBbmdlbGVzMTwwOgYDVQQKEzNJbnRlcm5ldCBDb3Jw
b3JhdGlvbiBmb3IgQXNzaWduZWQgTmFtZXMgYW5kIE51bWJlcnMxEzARBgNVBAMTCktpbSBE
YXZpZXMwggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQCnSZUaeAzcQA+uyKoPVGAw
l+6Ts/OnBoRHtOHz52LwDoUtjszVc1hh7Z3nNWMdnbiABMRFXdlKvDg7L5Qb9FSseUbFpiUi
RMDxkHgc4WtgdoFN/YFUVmqwx5wHMfT/6RnRF1zuh1T7jyKiLk2Ok82/t46ZJCWFA04dEqbj
2G3Mo2VOiezgsO/tCTHOzYkGPVPOUSZciEeYc8UuqpbriQUtZ5aiXBKhomJncawUsLAQp0ak
goArkUUvdSN7SSaxS751tKTnJDMJ/g1WvcdKn3Kb3sTtJy2/NbIr1AMnQ/oR3zya3uo3We0b
IzJ49NPZeLr007Ka13XpCH8tm8a76N8dAgMBAAGjggHtMIIB6TAfBgNVHSMEGDAWgBTnAiOA
AE/Y17yUC9k/dDlJMjyKeTAdBgNVHQ4EFgQUeR6567hS8LRt7eqNsDi2wzOgdZswDAYDVR0T
AQH/BAIwADAfBgNVHREEGDAWgRRraW0uZGF2aWVzQGljYW5uLm9yZzAOBgNVHQ8BAf8EBAMC
BaAwHQYDVR0lBBYwFAYIKwYBBQUHAwIGCCsGAQUFBwMEMEMGA1UdIAQ8MDowOAYKYIZIAYb9
bAQBAjAqMCgGCCsGAQUFBwIBFhxodHRwczovL3d3dy5kaWdpY2VydC5jb20vQ1BTMIGIBgNV
HR8EgYAwfjA9oDugOYY3aHR0cDovL2NybDMuZGlnaWNlcnQuY29tL0RpZ2lDZXJ0U0hBMkFz
c3VyZWRJRENBLWcxLmNybDA9oDugOYY3aHR0cDovL2NybDQuZGlnaWNlcnQuY29tL0RpZ2lD
ZXJ0U0hBMkFzc3VyZWRJRENBLWcxLmNybDB5BggrBgEFBQcBAQRtMGswJAYIKwYBBQUHMAGG
GGh0dHA6Ly9vY3NwLmRpZ2ljZXJ0LmNvbTBDBggrBgEFBQcwAoY3aHR0cDovL2NhY2VydHMu
ZGlnaWNlcnQuY29tL0RpZ2lDZXJ0U0hBMkFzc3VyZWRJRENBLmNydDANBgkqhkiG9w0BAQsF
AAOCAQEAkBKX2jFEiA3GYcBHIBiRlZjXse/TZ/T2ID0BeHKWvR44Spn3oKz9VZj4Jmnx4OfK
GiQZiheG/ytEWNX69fUlLvZrqQSYCFfLiH9oKr0qDNOm+gNbu4KWTeIdiznpE32kKJ2Crsbi
bZrknFUB4h6nWJgPHmoTQYa2qoUcdnaJS90oPX2ZznZxVw4qGafg/SuXajPuNI2MGoAOl1LX
WaHeyARAz9wBWZB5wZXlxSV9HAR0DgMOFvPn6BrxdclRnL5ebzJlemoBPNNqYzsRca6pbUM+
otK7vjxmZBiM0UN0AxHA7brsRcJFPIshZvYHHMkmSdVeNKIBhe8kvQgwi9EZIDCCBk4wggU2
oAMCAQICEASueWBmZpAaucV/pmxb3M0wDQYJKoZIhvcNAQELBQAwZTELMAkGA1UEBhMCVVMx
FTATBgNVBAoTDERpZ2lDZXJ0IEluYzEZMBcGA1UECxMQd3d3LmRpZ2ljZXJ0LmNvbTEkMCIG
A1UEAxMbRGlnaUNlcnQgQXNzdXJlZCBJRCBSb290IENBMB4XDTEzMTEwNTEyMDAwMFoXDTI4
MTEwNTEyMDAwMFowZTELMAkGA1UEBhMCVVMxFTATBgNVBAoTDERpZ2lDZXJ0IEluYzEZMBcG
A1UECxMQd3d3LmRpZ2ljZXJ0LmNvbTEkMCIGA1UEAxMbRGlnaUNlcnQgU0hBMiBBc3N1cmVk
IElEIENBMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA3PgRIz9qte/AJ3kbLQWH
ohBDMd8O1BUbT3ekIs4+jHDwvgeO3ScqvAEdtiwKyt1pWB9B7WoFH9pjeFkeIiwr+Lp+yTU7
VvEffEJ+JbAjGcZFONc9RPkgfGCuHLBaGAS+jzv3qfCUmqYMY0m2QRdTQDK9T+ZQelAfJUXo
8Ymvzf9e/1Dz8BcR/73FifW9YrnY+45FBIVtmc3FSE39JqsCNkXqNtdfauIagkEK3OnZ9ZEX
jsYhrTg8E+Yef2ac1U3ZRtr2z1KnfTskw7TBUTXGm+vU737kewPhRL16CzfgT8uCig1xGOSm
4IksG/OyczzBsJKeGH29q33FfQihLMKfcwIDAQABo4IC+DCCAvQwEgYDVR0TAQH/BAgwBgEB
/wIBADAOBgNVHQ8BAf8EBAMCAYYwNAYIKwYBBQUHAQEEKDAmMCQGCCsGAQUFBzABhhhodHRw
Oi8vb2NzcC5kaWdpY2VydC5jb20wgYEGA1UdHwR6MHgwOqA4oDaGNGh0dHA6Ly9jcmw0LmRp
Z2ljZXJ0LmNvbS9EaWdpQ2VydEFzc3VyZWRJRFJvb3RDQS5jcmwwOqA4oDaGNGh0dHA6Ly9j
cmwzLmRpZ2ljZXJ0LmNvbS9EaWdpQ2VydEFzc3VyZWRJRFJvb3RDQS5jcmwwHQYDVR0lBBYw
FAYIKwYBBQUHAwIGCCsGAQUFBwMEMIIBswYDVR0gBIIBqjCCAaYwggGiBgpghkgBhv1sAAIE
MIIBkjAoBggrBgEFBQcCARYcaHR0cHM6Ly93d3cuZGlnaWNlcnQuY29tL0NQUzCCAWQGCCsG
AQUFBwICMIIBVh6CAVIAQQBuAHkAIAB1AHMAZQAgAG8AZgAgAHQAaABpAHMAIABDAGUAcgB0
AGkAZgBpAGMAYQB0AGUAIABjAG8AbgBzAHQAaQB0AHUAdABlAHMAIABhAGMAYwBlAHAAdABh
AG4AYwBlACAAbwBmACAAdABoAGUAIABEAGkAZwBpAEMAZQByAHQAIABDAFAALwBDAFAAUwAg
AGEAbgBkACAAdABoAGUAIABSAGUAbAB5AGkAbgBnACAAUABhAHIAdAB5ACAAQQBnAHIAZQBl
AG0AZQBuAHQAIAB3AGgAaQBjAGgAIABsAGkAbQBpAHQAIABsAGkAYQBiAGkAbABpAHQAeQAg
AGEAbgBkACAAYQByAGUAIABpAG4AYwBvAHIAcABvAHIAYQB0AGUAZAAgAGgAZQByAGUAaQBu
ACAAYgB5ACAAcgBlAGYAZQByAGUAbgBjAGUALjAdBgNVHQ4EFgQU5wIjgABP2Ne8lAvZP3Q5
STI8inkwHwYDVR0jBBgwFoAUReuir/SSy4IxLVGLp6chnfNtyA8wDQYJKoZIhvcNAQELBQAD
ggEBAE7UiSe5/R2Hd34PKAWQ8QovyTs+vZOckMav+pFRhzJUa+jKwXFRXJmOtfrgYhmZpgea
fBMn2+UCooQS2RX2CkRXxDSPbXMfOtagAT3e44LkRWuy6yX9gF4dOZC+W0L2zpFg4/mgVgxI
EM4zaHvNk6vwastPWA+5e10bBIGepyLiV0kn7pKTCL5pCFMCOi5dyBn0UIBOAtmwXZG0k4f5
lpaBVUCOZu2C2LsoX+1MYe0GWCgZUxFEvEcgKbIEbNiJVJk7ddtneCweknjGVT1YEhEybr1D
DE0023vGQtvsvqubYUwGkuOO3yEqUFcEwGCiNdUknmY3CUnP1fhls+DibsIwggO3MIICn6AD
AgECAhAM5+DlF9hG/o/lYPwb8DA5MA0GCSqGSIb3DQEBBQUAMGUxCzAJBgNVBAYTAlVTMRUw
EwYDVQQKEwxEaWdpQ2VydCBJbmMxGTAXBgNVBAsTEHd3dy5kaWdpY2VydC5jb20xJDAiBgNV
BAMTG0RpZ2lDZXJ0IEFzc3VyZWQgSUQgUm9vdCBDQTAeFw0wNjExMTAwMDAwMDBaFw0zMTEx
MTAwMDAwMDBaMGUxCzAJBgNVBAYTAlVTMRUwEwYDVQQKEwxEaWdpQ2VydCBJbmMxGTAXBgNV
BAsTEHd3dy5kaWdpY2VydC5jb20xJDAiBgNVBAMTG0RpZ2lDZXJ0IEFzc3VyZWQgSUQgUm9v
dCBDQTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAK0OFc7kQ4BcsYfzt2D5cRKl
rtwmlIiq9M71IDkoWGAM+IDaqRWVMmE8tbEohIqK3J8KDIMXeo+QrIrneVNcMYQq9g+YMjZ2
zN7dPKii72r7IfJSYd+fINcf4rHZ/hhk0hJbX/lYGDW8R82hNvlrf9SwOD7BG8OMM9nYLxj+
KA+zp4PWw25EwGE1lhb+WZyLdm3X8aJLDSv/C3LanmDQjpA1xnhVhyChz+VtCshJfDGYM2wi
6YfQMlqiuhOCEe05F52ZOnKh5vqk2dUXMXWuhX0irj8BRob2KHnIsdrkVxfEfhwOsLSSplaz
vbKX7aqn8LfFqD+VFtD/oZbrCF8Yd08CAwEAAaNjMGEwDgYDVR0PAQH/BAQDAgGGMA8GA1Ud
EwEB/wQFMAMBAf8wHQYDVR0OBBYEFEXroq/0ksuCMS1Ri6enIZ3zbcgPMB8GA1UdIwQYMBaA
FEXroq/0ksuCMS1Ri6enIZ3zbcgPMA0GCSqGSIb3DQEBBQUAA4IBAQCiDrzf4u3w43JzemSU
v/dyZtgy5EJ1Yq6H6/LV2d5Ws5/MzhQouQ2XYFwSTFjk0z2DSUVYlzVpGqhH6lbGeasS2GeB
hN9/CTyU5rgmLCC9PbMoifdf/yLil4Qf6WXvh+DfwWdJs13rsgkq6ybteL59PyvztyY1bV+J
AbZJW58BBZurPSXBzLZ/wvFvhsb6ZGjrgS2U60K3+owe3WLxvlBnt2y98/Efaww2BxZ/N3yp
W2168RJGYIPXJwS+S86XvsNnKmgR34DnDDNmvxMNFG7zfx9jEB76jRslbWyPpbdhAbHSoyah
EHGdreLD+cOZUbcrBwjOLuZQsqf6CkUvovDyMYICDzCCAgsCAQEweTBlMQswCQYDVQQGEwJV
UzEVMBMGA1UEChMMRGlnaUNlcnQgSW5jMRkwFwYDVQQLExB3d3cuZGlnaWNlcnQuY29tMSQw
IgYDVQQDExtEaWdpQ2VydCBTSEEyIEFzc3VyZWQgSUQgQ0ECEAM3/aZ67iMUNwpbj+veFrow
DQYJYIZIAWUDBAIBBQCgaTAvBgkqhkiG9w0BCQQxIgQgHSti131GBwLnx0wX0CTLIkb6k6d/
4d6DC3vEFa1HTUowGAYJKoZIhvcNAQkDMQsGCSqGSIb3DQEHATAcBgkqhkiG9w0BCQUxDxcN
MTYwMzIwMjA1NzU0WjANBgkqhkiG9w0BAQEFAASCAQCXxl3ZbxGBICN2L5hY0NdlPwDM/x/6
ljrjtu7LKhfXPqBqrhLRlxC7W5qhwNDIjvawoB8LRbZGySVAxLBBOHFY3ulNExl2tId30rCH
qlS4skqjTnXjl5M1IoSINDQzScixyuJMFDN0CPLQzE7SfFJf3cIvTduHA7XsJyZUQm5QLl+o
F0x5Xwmeepxs3S6PmT5p8+MrlEyt5ptvf9VEvf7i9rYUIurlbVgqwMEbNstoucdctFsWzrQn
11P7PuzUbPvlh2gAk4Ca9dFT/Gud5kYAZz7S/gd03KgrpCf02IXxv6cnv8NkybuQf3gHZSwi
JLC4WQuumLsp9ArH9IIlarY0

--B_3541327074_1656648188--


From nobody Sun Mar 20 14:06:20 2016
Return-Path: <marc.blanchet@viagenie.ca>
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 72B5F12D67D; Sun, 20 Mar 2016 14:06:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001, 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 XlRlealE5V2w; Sun, 20 Mar 2016 14:06:16 -0700 (PDT)
Received: from jazz.viagenie.ca (jazz.viagenie.ca [IPv6:2620:0:230:8000::2]) by ietfa.amsl.com (Postfix) with ESMTP id B982612D52E; Sun, 20 Mar 2016 14:06:16 -0700 (PDT)
Received: from [192.168.1.111] (modemcable093.65-160-184.mc.videotron.ca [184.160.65.93]) by jazz.viagenie.ca (Postfix) with ESMTPSA id 29C5D476D6; Sun, 20 Mar 2016 17:06:16 -0400 (EDT)
From: "Marc Blanchet" <marc.blanchet@viagenie.ca>
To: "Kim Davies" <kim.davies@icann.org>
Date: Sun, 20 Mar 2016 17:06:15 -0400
Message-ID: <259A5E05-A478-4B16-9CEE-ABBF552A7B53@viagenie.ca>
In-Reply-To: <6B052A27-0C6C-4B2A-807D-41D7FDCFB537@icann.org>
References: <CALaySJJP0deDOxCs8YSPr72pfyRUsbZBVE9XO=_4d2AvEhVEtQ@mail.gmail.com> <6B052A27-0C6C-4B2A-807D-41D7FDCFB537@icann.org>
MIME-Version: 1.0
Content-Type: text/plain; format=flowed
X-Mailer: MailMate (1.9.4r5234)
Archived-At: <http://mailarchive.ietf.org/arch/msg/lager/1xhtsVL7od5TwjyqrxnSSUjRLlc>
Cc: "draft-ietf-lager-specification@ietf.org" <draft-ietf-lager-specification@ietf.org>, Barry Leiba <barryleiba@computer.org>, "lager@ietf.org" <lager@ietf.org>
Subject: Re: [Lager] AD review of draft-ietf-lager-specification-10
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: Sun, 20 Mar 2016 21:06:18 -0000

On 20 Mar 2016, at 16:57, Kim Davies wrote:

> Hi Barry, Hi all,
>
> On 3/13/16, 7:57 AM, "barryleiba@gmail.com on behalf of Barry Leiba" 
> <barryleiba@gmail.com on behalf of barryleiba@computer.org> wrote:
>
>> Hi, authors, shepherd, and working group.
>> Here's my AD review of draft-ietf-lager-specification-10.
>
> Asmus and I have implemented this feedback into a revised -11 draft 
> that
> is ready to post, except for one outstanding issue:
>
>> -- Section 12 --
>>
>>   If a system that is querying an identifier list (such as a domain
>>   zone) that uses the rules in this memo, and those rules are not
>>   implemented correctly, and that system is relying on the rules 
>> being
>>   applied, the system might fail if the rules are not applied in a
>>   predictable fashion.  This could cause security problems for the
>>   querying system.
>>
>> First, I think you have an extra "that" after the parentheses.
>> Second, can you be more specific than "This could cause security
>> problems"?  What sort of problems?  How can they be mitigated?  This
>> needs to be something more than "bad implementations can result in 
>> bad
>> things."
>
> I agree this paragraph essentially means bad implementations can 
> result in
> bad things. I don't have a proposed approach on how to mitigate this 
> general
> situation other than to follow the specification. Perhaps it makes the 
> most
> sense simply to strike this entire paragraph unless anyone has 
> suggestions
> on alternative wording.

I would vote to just strike the paragraph, since reading it does not 
help me really.

Marc.

>
> kim_______________________________________________
> Lager mailing list
> Lager@ietf.org
> https://www.ietf.org/mailman/listinfo/lager


From nobody Sun Mar 20 17:59:46 2016
Return-Path: <internet-drafts@ietf.org>
X-Original-To: lager@ietf.org
Delivered-To: lager@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id C50CF12D7FB; Sun, 20 Mar 2016 17:59:45 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.17.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20160321005945.8921.78483.idtracker@ietfa.amsl.com>
Date: Sun, 20 Mar 2016 17:59:45 -0700
Archived-At: <http://mailarchive.ietf.org/arch/msg/lager/QMz5uefNvJ-2KwflO8rmvrlEImw>
Cc: lager@ietf.org
Subject: [Lager] I-D Action: draft-ietf-lager-specification-11.txt
X-BeenThere: lager@ietf.org
X-Mailman-Version: 2.1.17
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: Mon, 21 Mar 2016 00:59:46 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Label Generation Rules of the IETF.

        Title           : Representing Label Generation Rulesets using XML
        Authors         : Kim Davies
                          Asmus Freytag
	Filename        : draft-ietf-lager-specification-11.txt
	Pages           : 78
	Date            : 2016-03-20

Abstract:
   This document describes a method of representing rules for validating
   identifier labels and alternate representations of those labels using
   Extensible Markup Language (XML).  These policies, known as "Label
   Generation Rulesets" (LGRs), are used for the implementation of
   Internationalized Domain Names (IDNs), for example.  The rulesets are
   used to implement and share that aspect of policy defining which
   labels and Unicode code points are permitted for registrations, which
   alternative code points are considered variants, and what actions may
   be performed on labels containing those variants.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-lager-specification/

There's also a htmlized version available at:
https://tools.ietf.org/html/draft-ietf-lager-specification-11

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-lager-specification-11


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.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From nobody Mon Mar 21 07:42:54 2016
Return-Path: <iesg-secretary@ietf.org>
X-Original-To: lager@ietf.org
Delivered-To: lager@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 211FF12D760; Mon, 21 Mar 2016 07:42:48 -0700 (PDT)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: "IETF-Announce" <ietf-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.17.0
Auto-Submitted: auto-generated
Precedence: bulk
Sender: <iesg-secretary@ietf.org>
Message-ID: <20160321144248.31961.37487.idtracker@ietfa.amsl.com>
Date: Mon, 21 Mar 2016 07:42:48 -0700
Archived-At: <http://mailarchive.ietf.org/arch/msg/lager/i3yf4nbkgQ9AZgx2sOegF978GiI>
Cc: Audric Schiltknecht <audric.schiltknecht@viagenie.ca>, draft-ietf-lager-specification@ietf.org, lager-chairs@ietf.org, barryleiba@gmail.com, lager@ietf.org
Subject: [Lager] Last Call: <draft-ietf-lager-specification-11.txt> (Representing Label Generation Rulesets using XML) to Proposed Standard
X-BeenThere: lager@ietf.org
X-Mailman-Version: 2.1.17
Reply-To: ietf@ietf.org
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: Mon, 21 Mar 2016 14:42:48 -0000

The IESG has received a request from the Label Generation Rules WG
(lager) to consider the following document:
- 'Representing Label Generation Rulesets using XML'
  <draft-ietf-lager-specification-11.txt> as Proposed Standard

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action. Please send substantive comments to the
ietf@ietf.org mailing lists by 2016-04-11. Exceptionally, comments may be
sent to iesg@ietf.org instead. In either case, please retain the
beginning of the Subject line to allow automated sorting.

Abstract

   This document describes a method of representing rules for validating
   identifier labels and alternate representations of those labels using
   Extensible Markup Language (XML).  These policies, known as "Label
   Generation Rulesets" (LGRs), are used for the implementation of
   Internationalized Domain Names (IDNs), for example.  The rulesets are
   used to implement and share that aspect of policy defining which
   labels and Unicode code points are permitted for registrations, which
   alternative code points are considered variants, and what actions may
   be performed on labels containing those variants.


The file can be obtained via
https://datatracker.ietf.org/doc/draft-ietf-lager-specification/

When IESG discussion begins, it can be tracked via
https://datatracker.ietf.org/doc/draft-ietf-lager-specification/ballot/

No IPR declarations have been submitted directly on this I-D.


From nobody Mon Mar 21 14:22:58 2016
Return-Path: <audric.schiltknecht@viagenie.ca>
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 84A5212DB60 for <lager@ietfa.amsl.com>; Mon, 21 Mar 2016 14:22:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001, 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 OFigu8be0qp2 for <lager@ietfa.amsl.com>; Mon, 21 Mar 2016 14:22:54 -0700 (PDT)
Received: from jazz.viagenie.ca (jazz.viagenie.ca [IPv6:2620:0:230:8000::2]) by ietfa.amsl.com (Postfix) with ESMTP id D9FC312DB55 for <lager@ietf.org>; Mon, 21 Mar 2016 14:22:54 -0700 (PDT)
Received: from [IPv6:2620:0:230:c000:3e97:eff:fe95:5451] (unknown [IPv6:2620:0:230:c000:3e97:eff:fe95:5451]) by jazz.viagenie.ca (Postfix) with ESMTPSA id 637DF4759E for <lager@ietf.org>; Mon, 21 Mar 2016 17:22:54 -0400 (EDT)
References: <20160321211756.12203.30019.idtracker@ietfa.amsl.com>
To: "lager WG (lager@ietf.org)" <lager@ietf.org>
From: Audric Schiltknecht <audric.schiltknecht@viagenie.ca>
Organization: =?UTF-8?B?VmlhZ8Opbmll?=
X-Forwarded-Message-Id: <20160321211756.12203.30019.idtracker@ietfa.amsl.com>
Message-ID: <56F0662D.1020604@viagenie.ca>
Date: Mon, 21 Mar 2016 17:22:53 -0400
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.5.1
MIME-Version: 1.0
In-Reply-To: <20160321211756.12203.30019.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/lager/t4cj9Zivg21qJM9KbvygyVY9_fk>
Subject: [Lager] Fwd: New Version Notification for draft-schiltknecht-lager-json-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: Mon, 21 Mar 2016 21:22:56 -0000

I've re-submitted the expired draft that has been mentioned in the potential next steps for the WG,
as starting point for comments and discussions.

Audric


-------- Message transféré --------
Sujet : New Version Notification for draft-schiltknecht-lager-json-00.txt
Date : Mon, 21 Mar 2016 14:17:56 -0700
De : internet-drafts@ietf.org
Pour : Audric Schiltknecht <audric.schiltknecht@viagenie.ca>


A new version of I-D, draft-schiltknecht-lager-json-00.txt
has been successfully submitted by Audric Schiltknecht and posted to the
IETF repository.

Name:		draft-schiltknecht-lager-json
Revision:	00
Title:		A JSON format for LGR files
Document date:	2016-03-21
Group:		Individual Submission
Pages:		12
URL:            https://www.ietf.org/internet-drafts/draft-schiltknecht-lager-json-00.txt
Status:         https://datatracker.ietf.org/doc/draft-schiltknecht-lager-json/
Htmlized:       https://tools.ietf.org/html/draft-schiltknecht-lager-json-00


Abstract:
   This document defines a JSON format for LGRs (Label Generation
   Rules).  LGRs are used to represent rules for validating identifier
   labels and their alternate representations.  These LGRs are expressed
   in XML as defined in [I-D.ietf-lager-specification].




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 Mon Mar 21 15:19:08 2016
Return-Path: <aamelnikov@fastmail.fm>
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 1DCF512D0EA for <lager@ietfa.amsl.com>; Mon, 21 Mar 2016 15:19:07 -0700 (PDT)
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, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=fastmail.fm header.b=hb+KtnO/; dkim=pass (1024-bit key) header.d=messagingengine.com header.b=ZmUvvO5i
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 rI3RQ_Dl-RFq for <lager@ietfa.amsl.com>; Mon, 21 Mar 2016 15:19:04 -0700 (PDT)
Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 37C0A12D0BF for <lager@ietf.org>; Mon, 21 Mar 2016 15:18:45 -0700 (PDT)
Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id 977E5207DF for <lager@ietf.org>; Mon, 21 Mar 2016 18:18:44 -0400 (EDT)
Received: from frontend2 ([10.202.2.161]) by compute6.internal (MEProxy); Mon, 21 Mar 2016 18:18:44 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=fastmail.fm; h=cc :content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-sasl-enc :x-sasl-enc; s=mesmtp; bh=Zl2mX3d/kAxQ0OvLflA02cgvu2Y=; b=hb+Ktn O/z22N3OF69Wp/T6c1coCKd2lAgD3lU3nUoBlTO4ZVSFjUTIje329+elBEkFkgLc PbOgi43zCr9A3r0XKbENAlODmLvzisamiTpPcxem+XvruuVqHNwewdqSA10JubWT 5JsDxY/kp1mlplc58M4NOPmY1ywFBGYlk1wXY=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-sasl-enc:x-sasl-enc; s=smtpout; bh=Zl2mX3d/kAxQ0Ov LflA02cgvu2Y=; b=ZmUvvO5iAzcWwJcm5FQ/t6VAXBk6XobWtIyvuRwNNy0/nBS DqvEoFN1pnA1OczmpQ9xTdAY3TNyHpL1opXNmRO1DGjU8EHjTL5p29vNxxd/b8Fv pufB+YM4/gIwrHK92h5fYATVnfTJQ5Hv1FMYzyEf9Qri1ZyRK2cx/MkIjj8E=
X-Sasl-enc: TMYHHFIw4wz4gxFK8hVsAivy566J5EjBiO+65YZ/bf0F 1458598724
Received: from [10.2.215.180] (unknown [85.255.235.8]) by mail.messagingengine.com (Postfix) with ESMTPA id 3B5B2680206; Mon, 21 Mar 2016 18:18:44 -0400 (EDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (1.0)
From: Alexey Melnikov <aamelnikov@fastmail.fm>
X-Mailer: iPhone Mail (13D15)
In-Reply-To: <FAF1B09B-D402-41A9-BFA1-20D45C97809A@viagenie.ca>
Date: Mon, 21 Mar 2016 22:21:21 +0000
Content-Transfer-Encoding: quoted-printable
Message-Id: <712BFACC-754B-4900-A83C-60C83A7629B4@fastmail.fm>
References: <CALaySJJP0deDOxCs8YSPr72pfyRUsbZBVE9XO=_4d2AvEhVEtQ@mail.gmail.com> <FAF1B09B-D402-41A9-BFA1-20D45C97809A@viagenie.ca>
To: lager@ietf.org
Archived-At: <http://mailarchive.ietf.org/arch/msg/lager/5_zHxM-zupfhXRu2K_l-bmKwabY>
Cc: Barry Leiba <barryleiba@computer.org>
Subject: Re: [Lager] AD review of draft-ietf-lager-specification-10
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: Mon, 21 Mar 2016 22:19:07 -0000

Just a heads-up: as the incoming responsible AD for this WG, I am also revie=
wing the draft and will send my comments within a week or two. So far I foun=
d mostly nits.=20
I am glad to see Barry's comments addressed!=


From nobody Thu Mar 24 10:46:23 2016
Return-Path: <aamelnikov@fastmail.fm>
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 696C112D663 for <lager@ietfa.amsl.com>; Thu, 24 Mar 2016 10:46:22 -0700 (PDT)
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, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=fastmail.fm header.b=DIemWpFQ; dkim=pass (1024-bit key) header.d=messagingengine.com header.b=W846LvBv
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 6pB9l2nrlMnc for <lager@ietfa.amsl.com>; Thu, 24 Mar 2016 10:46:20 -0700 (PDT)
Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8DE2412D5DE for <lager@ietf.org>; Thu, 24 Mar 2016 10:46:20 -0700 (PDT)
Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.nyi.internal (Postfix) with ESMTP id F065C214A5 for <lager@ietf.org>; Thu, 24 Mar 2016 13:46:19 -0400 (EDT)
Received: from web5 ([10.202.2.215]) by compute3.internal (MEProxy); Thu, 24 Mar 2016 13:46:19 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=fastmail.fm; h= content-transfer-encoding:content-type:date:from:message-id :mime-version:subject:to:x-sasl-enc:x-sasl-enc; s=mesmtp; bh=IFT R2xtcwTLoxTvntZdPT1UtAAk=; b=DIemWpFQgQusFaYLCLd3FOGHrmOp7FZaI+4 LKGIgLQKiP+1Rwxujn0yQbABxS68WSyiJQWebcLJfLQe2F4VoP3kNWzem5MJNgt5 Gjv51U0K2xxDRvRjb7CrjOvlQxllhOmU+yw61H9N/eDZnNLSDuhLmb6tp46w0YBm 5dPu7jWQ=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:message-id:mime-version:subject:to:x-sasl-enc :x-sasl-enc; s=smtpout; bh=IFTR2xtcwTLoxTvntZdPT1UtAAk=; b=W846L vBv5c4vpTzLdAyag1R3GX+9gEvET5zbgAQVA0Htch1wgIGFXC+xYixRLSEiNsDLv dNSna8JWh8AH5h27WyJofHQ6x/51lshf233RQoVsXhUVU1yUSDcEl6nDF8ETHQjc XJ6/EhRwrRbLTc49dl9I76lpf4Ga3WA7S7mpq8=
Received: by web5.nyi.internal (Postfix, from userid 99) id B8805A66AEE; Thu, 24 Mar 2016 13:46:19 -0400 (EDT)
Message-Id: <1458841579.4011697.558814722.09946B62@webmail.messagingengine.com>
X-Sasl-Enc: joFA+bCWesE+WnCTSVA7L0qn+dIBQb8O0xf6s02klZ1J 1458841579
From: Alexey Melnikov <aamelnikov@fastmail.fm>
To: lager@ietf.org
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain
X-Mailer: MessagingEngine.com Webmail Interface - ajax-eaa4717d
Date: Thu, 24 Mar 2016 17:46:19 +0000
Archived-At: <http://mailarchive.ietf.org/arch/msg/lager/EcutkiPxpwI0i7gcDNpLd4KXv-Q>
Subject: [Lager] Incoming AD review on draft-ietf-lager-specification-11.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, 24 Mar 2016 17:46:22 -0000

Hi,

This is a well written document which was generally a pleasure to read.
And thank you for addressing Barry's comments, as some of the issues he
raised got me confused as well.

I do have several minor comments/nits that I would like to be
addressed/discussed:


In Section 4.3.5

The first mention of "media type" needs a normative reference to RFC
2045. This would save developers time with trying to find out what
syntax to support and where to find registered media types.

In 6.1:

>A rule MAY contain the following as child elements:

Nit: This is an invalid use of MAY, because it is not an implementation
choice. I don't think you meant here that implementations don't have to
support any of the listed child elements?

In 7.6:

> If no actions are defined for the standard disposition values of
> "invalid", "blocked", "allocatable", "activated", then the following
> implicitly defined default actions are evaluated.

Are default actions defined if none of the actions for recommended
standard dispositions is defined or if any of them is not defined? For
example, I was thinking whether it would be Ok to just automatically
(and unconditionally) append these default actions to any LGR file for
purposes of evaluation? If any action for standard disposition value is
already defined and it would take precedence, so the corresponding
default action would be ignored.

In 11.3:

I think this section needs a bit of work. Firstly, it might be better to
say that Standard Dispositions MUST NOT contain ":" character in order
to prevent clashes with private dispositions.

Also, saying that registered values are lowercase ASCII (for example)
would be a good idea. If you want to only allow ASCII, but not to limit
values to lowercase letters, then you need to say whether values in the
registry are case-sensitive or not.

> Private Dispositions - This registry shall list dispositions that
> have been registered on a first-come first-served basis by third parties
> with the IANA. Such dispositions must take the form "entity:disposition"
> where the entity is a prefix that uniquely identifies the private user
> of the namespace. For example, "acme:reserved" could be a private extension
> used by the organization ACME to denote a disposition relating to reserved
> labels.

I think "entity" should be better specified. Which characters are
allowed? I would recommend either use domain names to describe ownerhip
(I can suggest some text) or use values from the PEN IANA registry
<https://www.iana.org/assignments/enterprise-numbers/enterprise-numbers>?

Please let me know if my comments are unclear.

Best Regards,
Alexey


From nobody Thu Mar 24 16:44:56 2016
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 2148A12DA29 for <lager@ietfa.amsl.com>; Thu, 24 Mar 2016 16:44:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.719
X-Spam-Level: 
X-Spam-Status: No, score=-2.719 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, 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 bK8Kmqaxyjwn for <lager@ietfa.amsl.com>; Thu, 24 Mar 2016 16:44:52 -0700 (PDT)
Received: from elasmtp-dupuy.atl.sa.earthlink.net (elasmtp-dupuy.atl.sa.earthlink.net [209.86.89.62]) by ietfa.amsl.com (Postfix) with ESMTP id 2705112D83D for <lager@ietf.org>; Thu, 24 Mar 2016 16:44:52 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=ix.netcom.com; b=BQ3q7j7jOqB+PT03uXZcaZWBDpX1UNM/UBd4QRheLJqSwv6VL06xmS0Q0VO2YLJu; h=Received:From:Subject:To:References:Message-ID:Date:User-Agent:MIME-Version:In-Reply-To:Content-Type:X-ELNK-Trace:X-Originating-IP;
Received: from [71.35.115.182] (helo=[192.168.1.103]) by elasmtp-dupuy.atl.sa.earthlink.net with esmtpa (Exim 4.67) (envelope-from <asmusf@ix.netcom.com>) id 1ajEv7-0003m0-BF; Thu, 24 Mar 2016 19:44:05 -0400
From: Asmus Freytag <asmusf@ix.netcom.com>
To: Alexey Melnikov <aamelnikov@fastmail.fm>, lager@ietf.org
References: <1458841579.4011697.558814722.09946B62@webmail.messagingengine.com>
Message-ID: <56F47BC4.1050801@ix.netcom.com>
Date: Thu, 24 Mar 2016 16:44:04 -0700
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.6.0
MIME-Version: 1.0
In-Reply-To: <1458841579.4011697.558814722.09946B62@webmail.messagingengine.com>
Content-Type: multipart/alternative; boundary="------------020005080901040408020303"
X-ELNK-Trace: 464f085de979d7246f36dc87813833b2857e9f10d2205ddc34c0d2446e34311174e98a0a7e4ea97c350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 71.35.115.182
Archived-At: <http://mailarchive.ietf.org/arch/msg/lager/N8C5WVFN5LrG25ZlKD-SBr8qotM>
Subject: Re: [Lager] Incoming AD review on draft-ietf-lager-specification-11.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, 24 Mar 2016 23:44:54 -0000

This is a multi-part message in MIME format.
--------------020005080901040408020303
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit

I'll let Kim address the issues with 4.3.5 and 11.3 (media type and 
registration).

Here some comments on the issues raised against 6.1 and 7.6.

A./

On 3/24/2016 10:46 AM, Alexey Melnikov wrote:
> In 6.1:
>
>> >A rule MAY contain the following as child elements:
> Nit: This is an invalid use of MAY, because it is not an implementation
> choice. I don't think you meant here that implementations don't have to
> support any of the listed child elements?

What is the specification aimed at? It's a file format. That means, 
there are different levels of requirements for authors (of what may be a 
single LGR document, which does not have to include all possible 
features) and implementations (that we would expect of being able to 
interpret any well-formed LGR document). It seems to me:

  * Implementations (readers, parsers, validators) MUST support all
    features, including OPTIONAL ones.
  * Authors MAY supply any features, except those that MUST NOT be
    present, and MUST supply all required features.

In that context, MAY or not MAY in the above example?

Aside from that, would it have been better to write:

"A rule may contain the following OPTIONAL child elements"

> In 7.6:
>
>> >If no actions are defined for the standard disposition values of
>> >"invalid", "blocked", "allocatable", "activated", then the following
>> >implicitly defined default actions are evaluated.
> Are default actions defined if none of the actions for recommended
> standard dispositions is defined or if any of them is not defined? For
> example, I was thinking whether it would be Ok to just automatically
> (and unconditionally) append these default actions to any LGR file for
> purposes of evaluation? If any action for standard disposition value is
> already defined and it would take precedence, so the corresponding
> default action would be ignored.
Yes, this can be improved.

I think it would be cleanest to describe the "implicitly defined default 
actions" as a block of <action> elements that is added (virtually) 
beyond the last of the user-supplied actions. Any label not processed by 
the user-supplied actions would be processed by these "implicitly 
defined default actions" as if they were present in the file. As the 
last one is a "catch-all", all processing is guaranteed to end with a 
definite disposition for the label.

Note that the phrase used in the existing description ("standard 
disposition values") is potentially misleading, because we now make the 
distinction between "types" (on variant mappings) and "dispositions" (as 
result of processing labels). We didn't use to and this wording may be a 
holdover.

I'll look at suggested wording.

A./

--------------020005080901040408020303
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 7bit

<html>
  <head>
    <meta content="text/html; charset=utf-8" http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <div class="moz-cite-prefix">I'll let Kim address the issues with
      4.3.5 and 11.3 (media type and registration).<br>
      <br>
      Here some comments on the issues raised against 6.1 and 7.6.<br>
      <br>
      A./<br>
      <br>
      On 3/24/2016 10:46 AM, Alexey Melnikov wrote:<br>
    </div>
    <blockquote
cite="mid:1458841579.4011697.558814722.09946B62@webmail.messagingengine.com"
      type="cite">
      <pre wrap="">In 6.1:

</pre>
      <blockquote type="cite" style="font-size: large; color: #3333FF;">
        <pre wrap=""><span class="moz-txt-citetags">&gt;</span>A rule MAY contain the following as child elements:
</pre>
      </blockquote>
      <pre wrap="">Nit: This is an invalid use of MAY, because it is not an implementation
choice. I don't think you meant here that implementations don't have to
support any of the listed child elements?</pre>
    </blockquote>
    <br>
    What is the specification aimed at? It's a file format. That means,
    there are different levels of requirements for authors (of what may
    be a single LGR document, which does not have to include all
    possible features) and implementations (that we would expect of
    being able to interpret any well-formed LGR document). It seems to
    me:<br>
    <br>
    <ul>
      <li>Implementations (readers, parsers, validators) MUST support
        all features, including OPTIONAL ones.</li>
      <li>Authors MAY supply any features, except those that MUST NOT be
        present, and MUST supply all required features.</li>
    </ul>
    In that context, MAY or not MAY in the above example?<br>
    <br>
    Aside from that, would it have been better to write:<br>
    <br>
    "A rule may contain the following OPTIONAL child elements"<br>
    <br>
    <blockquote
cite="mid:1458841579.4011697.558814722.09946B62@webmail.messagingengine.com"
      type="cite">
      <pre wrap="">
In 7.6:

</pre>
      <blockquote type="cite" style="font-size: large; color: #3333FF;">
        <pre wrap=""><span class="moz-txt-citetags">&gt; </span>If no actions are defined for the standard disposition values of
<span class="moz-txt-citetags">&gt; </span>"invalid", "blocked", "allocatable", "activated", then the following
<span class="moz-txt-citetags">&gt; </span>implicitly defined default actions are evaluated.
</pre>
      </blockquote>
      <pre wrap="">Are default actions defined if none of the actions for recommended
standard dispositions is defined or if any of them is not defined? For
example, I was thinking whether it would be Ok to just automatically
(and unconditionally) append these default actions to any LGR file for
purposes of evaluation? If any action for standard disposition value is
already defined and it would take precedence, so the corresponding
default action would be ignored.</pre>
    </blockquote>
    Yes, this can be improved.<br>
    <br>
    I think it would be cleanest to describe the "implicitly defined
    default actions" as a block of &lt;action&gt; elements that is added
    (virtually) beyond the last of the user-supplied actions. Any label
    not processed by the user-supplied actions would be processed by
    these "implicitly defined default actions" as if they were present
    in the file. As the last one is a "catch-all", all processing is
    guaranteed to end with a definite disposition for the label.<br>
    <br>
    Note that the phrase used in the existing description ("standard
    disposition values") is potentially misleading, because we now make
    the distinction between "types" (on variant mappings) and
    "dispositions" (as result of processing labels). We didn't use to
    and this wording may be a holdover.<br>
    <br>
    I'll look at suggested wording.<br>
    <br>
    A./<br>
  </body>
</html>

--------------020005080901040408020303--


From nobody Fri Mar 25 01:11:23 2016
Return-Path: <aamelnikov@fastmail.fm>
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 92D4512DBE2 for <lager@ietfa.amsl.com>; Fri, 25 Mar 2016 01:11:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.719
X-Spam-Level: 
X-Spam-Status: No, score=-2.719 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=fastmail.fm header.b=LqXWQCcE; dkim=pass (1024-bit key) header.d=messagingengine.com header.b=UWO6/s1w
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 VNBq2-UMLOJG for <lager@ietfa.amsl.com>; Fri, 25 Mar 2016 01:11:19 -0700 (PDT)
Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9681112D610 for <lager@ietf.org>; Fri, 25 Mar 2016 01:11:19 -0700 (PDT)
Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id B8C52208E0 for <lager@ietf.org>; Fri, 25 Mar 2016 04:11:18 -0400 (EDT)
Received: from frontend2 ([10.202.2.161]) by compute1.internal (MEProxy); Fri, 25 Mar 2016 04:11:18 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=fastmail.fm; h=cc :content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-sasl-enc :x-sasl-enc; s=mesmtp; bh=bsC9b8L7xxF8U+6FQjJt0M/XX4k=; b=LqXWQC cEG1N4rfJ4tLFjptoBDDgspwkJ4K1s0aNzQhma1c7yq6hmtIRKazDLQml7kXFfba GvnQEOKyhmYShM6whjkcOXsEblr4gGC7+oEAKFQKK6yTBcwOFvi0jSM45Ff/RkR2 RJW5rkEm2C2TevF4D0hMTN6XToKjcLcA6q3og=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-sasl-enc:x-sasl-enc; s=smtpout; bh=bsC9b8L7xxF8U+6 FQjJt0M/XX4k=; b=UWO6/s1wUXlMiRG96erWy0WDdWvROvWlwwGbjdJkvZ3qOr0 9jaM5nzBjH3JFMr9GGKtlfTo+rc+6miVWdvkZf/sADqK3dOHjEHGY3WoMQ13gJ9q tyAL8dsG8LmilYbiQYBW5bW2nQaQh3v+sWEGX1Rq/PpYlh37fUmedDzmqVw8=
X-Sasl-enc: PGtCYruLkqPd4J/fUTVbXQ/DhP20LEU9RZpGKJ1dYd1w 1458893478
Received: from [10.14.138.209] (unknown [85.255.232.206]) by mail.messagingengine.com (Postfix) with ESMTPA id 1A3006801BB; Fri, 25 Mar 2016 04:11:18 -0400 (EDT)
Content-Type: multipart/alternative; boundary=Apple-Mail-72036B27-062C-46C6-9683-C20EBB94329B
Mime-Version: 1.0 (1.0)
From: Alexey Melnikov <aamelnikov@fastmail.fm>
X-Mailer: iPhone Mail (13D15)
In-Reply-To: <56F47849.6050607@ix.netcom.com>
Date: Fri, 25 Mar 2016 08:14:07 +0000
Content-Transfer-Encoding: 7bit
Message-Id: <9E846AF5-6043-4715-8FD4-341D49EA9A17@fastmail.fm>
References: <1458841579.4011697.558814722.09946B62@webmail.messagingengine.com> <56F47849.6050607@ix.netcom.com>
To: "Asmus Freytag (t)" <asmus-inc@ix.netcom.com>
Archived-At: <http://mailarchive.ietf.org/arch/msg/lager/7HYm7zAQMClC91d1kPiYQr2t-OU>
Cc: lager@ietf.org
Subject: Re: [Lager] Incoming AD review on draft-ietf-lager-specification-11.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: Fri, 25 Mar 2016 08:11:21 -0000

--Apple-Mail-72036B27-062C-46C6-9683-C20EBB94329B
Content-Type: text/plain;
	charset=us-ascii
Content-Transfer-Encoding: quoted-printable

Hi Asmus,

> On 24 Mar 2016, at 23:29, Asmus Freytag (t) <asmus-inc@ix.netcom.com> wrot=
e:
>=20
> I'll let Kim address the issues with 4.3.5 and 11.3 (media type and regist=
ration).
>=20
> Here some comments on the issues raised against 6.1 and 7.6.
>=20
> A./
>=20
>> On 3/24/2016 10:46 AM, Alexey Melnikov wrote:
>> In 6.1:
>>=20
>>> >A rule MAY contain the following as child elements:
>> Nit: This is an invalid use of MAY, because it is not an implementation
>> choice. I don't think you meant here that implementations don't have to
>> support any of the listed child elements?
>=20
> What is the specification aimed at? It's a file format. That means, there a=
re different levels of requirements for authors (of what may be a single LGR=
 document, which does not have to include all possible features)

Ok, but isn't that true for pretty much all the features in the format? Why i=
s this one special?

> and implementations (that we would expect of being able to interpret any w=
ell-formed LGR document). It seems to me:
>=20
> Implementations (readers, parsers, validators) MUST support all features, i=
ncluding OPTIONAL ones.

I thought your document was mostly targeting implementations. If not, having=
 a separate section that covers authors might be a good idea.
> Authors MAY supply any features, except those that MUST NOT be present, an=
d MUST supply all required features.
> In that context, MAY or not MAY in the above example?
>=20
> Aside from that, would it have been better to write:
>=20
> "A rule may contain the following OPTIONAL child elements"

INHO, this is no better, because you are not telling who are they optional f=
or.
>> In 7.6:
>>=20
>>> > If no actions are defined for the standard disposition values of
>>> > "invalid", "blocked", "allocatable", "activated", then the following
>>> > implicitly defined default actions are evaluated.
>> Are default actions defined if none of the actions for recommended
>> standard dispositions is defined or if any of them is not defined? For
>> example, I was thinking whether it would be Ok to just automatically
>> (and unconditionally) append these default actions to any LGR file for
>> purposes of evaluation? If any action for standard disposition value is
>> already defined and it would take precedence, so the corresponding
>> default action would be ignored.
> Yes, this can be improved.
>=20
> I think it would be cleanest to describe the "implicitly defined default a=
ctions" as a block of <action> elements that is added (virtually) beyond the=
 last of the user-supplied actions. Any label not processed by the user-supp=
lied actions would be processed by these "implicitly defined default actions=
" as if they were present in the file. As the last one is a "catch-all", all=
 processing is guaranteed to end with a definite disposition for the label.

Right, this is what I thought.
>=20
> Note that the phrase used in the existing description ("standard dispositi=
on values") is potentially misleading, because we now make the distinction b=
etween "types" (on variant mappings) and "dispositions" (as result of proces=
sing labels). We didn't use to and this wording may be a holdover.
>=20
> I'll look at suggested wording.

That would be great, thank you.


--Apple-Mail-72036B27-062C-46C6-9683-C20EBB94329B
Content-Type: text/html;
	charset=utf-8
Content-Transfer-Encoding: 7bit

<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div>Hi Asmus,<br></div><div><br>On 24 Mar 2016, at 23:29, Asmus Freytag (t) &lt;<a href="mailto:asmus-inc@ix.netcom.com">asmus-inc@ix.netcom.com</a>&gt; wrote:<br><br></div><blockquote type="cite"><div>
  
    <meta content="text/html; charset=utf-8" http-equiv="Content-Type">
  
  
    <div class="moz-cite-prefix">I'll let Kim address the issues with
      4.3.5 and 11.3 (media type and registration).<br>
      <br>
      Here some comments on the issues raised against 6.1 and 7.6.<br>
      <br>
      A./<br>
      <br>
      On 3/24/2016 10:46 AM, Alexey Melnikov wrote:<br>
    </div>
    <blockquote cite="mid:1458841579.4011697.558814722.09946B62@webmail.messagingengine.com" type="cite">
      <pre wrap="">In 6.1:

</pre>
      <blockquote type="cite" style="font-size: large; color: #3333FF;">
        <pre wrap=""><span class="moz-txt-citetags">&gt;</span>A rule MAY contain the following as child elements:
</pre>
      </blockquote>
      <pre wrap="">Nit: This is an invalid use of MAY, because it is not an implementation
choice. I don't think you meant here that implementations don't have to
support any of the listed child elements?</pre>
    </blockquote>
    <br>
    What is the specification aimed at? It's a file format. That means,
    there are different levels of requirements for authors (of what may
    be a single LGR document, which does not have to include all
    possible features) </div></blockquote><div><br></div>Ok, but isn't that true for pretty much all the features in the format? Why is this one special?<div><br></div><div><blockquote type="cite"><div>and implementations (that we would expect of
    being able to interpret any well-formed LGR document). It seems to
    me:<br>
    <br>
    <ul>
      <li>Implementations (readers, parsers, validators) MUST support
        all features, including OPTIONAL ones.</li></ul></div></blockquote><div><br></div>I thought your document was mostly targeting implementations. If not, having a separate section that covers authors might be a good idea.<br><blockquote type="cite"><div><ul>
      <li>Authors MAY supply any features, except those that MUST NOT be
        present, and MUST supply all required features.</li>
    </ul>
    In that context, MAY or not MAY in the above example?<br>
    <br>
    Aside from that, would it have been better to write:<br>
    <br>
    "A rule may contain the following OPTIONAL child elements"<br></div></blockquote><div><br></div>INHO, this is no better, because you are not telling who are they optional for.<br><blockquote type="cite"><div>
    
    <blockquote cite="mid:1458841579.4011697.558814722.09946B62@webmail.messagingengine.com" type="cite">
      <pre wrap="">In 7.6:

</pre>
      <blockquote type="cite" style="font-size: large; color: #3333FF;">
        <pre wrap=""><span class="moz-txt-citetags">&gt; </span>If no actions are defined for the standard disposition values of
<span class="moz-txt-citetags">&gt; </span>"invalid", "blocked", "allocatable", "activated", then the following
<span class="moz-txt-citetags">&gt; </span>implicitly defined default actions are evaluated.
</pre>
      </blockquote>
      <pre wrap="">Are default actions defined if none of the actions for recommended
standard dispositions is defined or if any of them is not defined? For
example, I was thinking whether it would be Ok to just automatically
(and unconditionally) append these default actions to any LGR file for
purposes of evaluation? If any action for standard disposition value is
already defined and it would take precedence, so the corresponding
default action would be ignored.</pre>
    </blockquote>
    Yes, this can be improved.<br>
    <br>
    I think it would be cleanest to describe the "implicitly defined
    default actions" as a block of &lt;action&gt; elements that is added
    (virtually) beyond the last of the user-supplied actions. Any label
    not processed by the user-supplied actions would be processed by
    these "implicitly defined default actions" as if they were present
    in the file. As the last one is a "catch-all", all processing is
    guaranteed to end with a definite disposition for the label.<br></div></blockquote><div><br></div>Right, this is what I thought.<br><blockquote type="cite"><div>
    <br>
    Note that the phrase used in the existing description ("standard
    disposition values") is potentially misleading, because we now make
    the distinction between "types" (on variant mappings) and
    "dispositions" (as result of processing labels). We didn't use to
    and this wording may be a holdover.<br>
    <br>
    I'll look at suggested wording.<br></div></blockquote><div><br></div>That would be great, thank you.<br></div><div><br></div></body></html>
--Apple-Mail-72036B27-062C-46C6-9683-C20EBB94329B--


From nobody Fri Mar 25 08:24:17 2016
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 F074912DBB0 for <lager@ietfa.amsl.com>; Fri, 25 Mar 2016 08:24:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level: 
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7] 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 iKVpew69x-T1 for <lager@ietfa.amsl.com>; Fri, 25 Mar 2016 08:24:08 -0700 (PDT)
Received: from elasmtp-junco.atl.sa.earthlink.net (elasmtp-junco.atl.sa.earthlink.net [209.86.89.63]) by ietfa.amsl.com (Postfix) with ESMTP id E954412DB22 for <lager@ietf.org>; Fri, 25 Mar 2016 08:24:07 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=ix.netcom.com; b=pFpv7E9q9qPeu9mXN9AfMJzVYJio3AA2c24sBHvVS9D+hFmbLL7j1+Vtj/KP6LxT; h=Received:From:Subject:To:References:Message-ID:Date:User-Agent:MIME-Version:In-Reply-To:Content-Type:X-ELNK-Trace:X-Originating-IP;
Received: from [71.35.115.182] (helo=[192.168.1.103]) by elasmtp-junco.atl.sa.earthlink.net with esmtpa (Exim 4.67) (envelope-from <asmusf@ix.netcom.com>) id 1ajTak-0002Ph-Ma for lager@ietf.org; Fri, 25 Mar 2016 10:24:02 -0500
From: Asmus Freytag <asmusf@ix.netcom.com>
To: lager@ietf.org
References: <1458841579.4011697.558814722.09946B62@webmail.messagingengine.com> <56F47849.6050607@ix.netcom.com> <9E846AF5-6043-4715-8FD4-341D49EA9A17@fastmail.fm>
Message-ID: <56F55811.8070602@ix.netcom.com>
Date: Fri, 25 Mar 2016 08:24:01 -0700
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.6.0
MIME-Version: 1.0
In-Reply-To: <9E846AF5-6043-4715-8FD4-341D49EA9A17@fastmail.fm>
Content-Type: multipart/alternative; boundary="------------070608000706080404020806"
X-ELNK-Trace: 464f085de979d7246f36dc87813833b2857e9f10d2205ddc288c7cbbbe49b2f6e3961a3287cb983b350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 71.35.115.182
Archived-At: <http://mailarchive.ietf.org/arch/msg/lager/AOFD0KVPSJzj1lfb9Quu-Ao3caY>
Subject: Re: [Lager] Incoming AD review on draft-ietf-lager-specification-11.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: Fri, 25 Mar 2016 15:24:16 -0000

This is a multi-part message in MIME format.
--------------070608000706080404020806
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit

On 3/25/2016 1:14 AM, Alexey Melnikov wrote:
> Hi Asmus,
>
> On 24 Mar 2016, at 23:29, Asmus Freytag (t) <asmus-inc@ix.netcom.com> 
> wrote:
>
>> I'll let Kim address the issues with 4.3.5 and 11.3 (media type and 
>> registration).
>>
>> Here some comments on the issues raised against 6.1 and 7.6.
>>
>> A./
>>
>> On 3/24/2016 10:46 AM, Alexey Melnikov wrote:
>>> In 6.1:
>>>
>>>> >A rule MAY contain the following as child elements:
>>> Nit: This is an invalid use of MAY, because it is not an implementation
>>> choice. I don't think you meant here that implementations don't have to
>>> support any of the listed child elements?
>>
>> What is the specification aimed at? It's a file format. That means, 
>> there are different levels of requirements for authors (of what may 
>> be a single LGR document, which does not have to include all possible 
>> features)
>
> Ok, but isn't that true for pretty much all the features in the 
> format? Why is this one special?
>
>> and implementations (that we would expect of being able to interpret 
>> any well-formed LGR document). It seems to me:
>>
>>   * Implementations (readers, parsers, validators) MUST support all
>>     features, including OPTIONAL ones.
>>
>
> I thought your document was mostly targeting implementations. If not, 
> having a separate section that covers authors might be a good idea.
>>
>>   * Authors MAY supply any features, except those that MUST NOT be
>>     present, and MUST supply all required features.
>>
>> In that context, MAY or not MAY in the above example?
>>
>> Aside from that, would it have been better to write:
>>
>> "A rule may contain the following OPTIONAL child elements"
>
> INHO, this is no better, because you are not telling who are they 
> optional for.

Looked at the text in context. MAY ---> may is fine anyway, because the 
passage is somewhat introductory.
>>> In 7.6:
>>>
>>>> >If no actions are defined for the standard disposition values of
>>>> >"invalid", "blocked", "allocatable", "activated", then the following
>>>> >implicitly defined default actions are evaluated.
>>> Are default actions defined if none of the actions for recommended
>>> standard dispositions is defined or if any of them is not defined? For
>>> example, I was thinking whether it would be Ok to just automatically
>>> (and unconditionally) append these default actions to any LGR file for
>>> purposes of evaluation? If any action for standard disposition value is
>>> already defined and it would take precedence, so the corresponding
>>> default action would be ignored.
>> Yes, this can be improved.
>>
>> I think it would be cleanest to describe the "implicitly defined 
>> default actions" as a block of <action> elements that is added 
>> (virtually) beyond the last of the user-supplied actions. Any label 
>> not processed by the user-supplied actions would be processed by 
>> these "implicitly defined default actions" as if they were present in 
>> the file. As the last one is a "catch-all", all processing is 
>> guaranteed to end with a definite disposition for the label.
>
> Right, this is what I thought.
>>
>> Note that the phrase used in the existing description ("standard 
>> disposition values") is potentially misleading, because we now make 
>> the distinction between "types" (on variant mappings) and 
>> "dispositions" (as result of processing labels). We didn't use to and 
>> this wording may be a holdover.
>>
>> I'll look at suggested wording.
>
> That would be great, thank you.

I cleaned up the passage and added a note that makes the point about 
default actions being treated as if added past the last user defined 
action.  (See below).

A./


  7.6 Default Actions <#default_actions>

If a label does not trigger any of the actions defined explicitly in the 
LGR, the following implicitly defined default actions are evaluated. 
They are shown below in their relative order of precedence (seeSection 
7.4 <#precedence>). Default actions have a lower order of precedence 
than explicit actions (seeSection 8.3 <#determining_dispositions>).

The default actions for variant labels are defined as follows. The first 
set is triggered based on the standard variant type values of "invalid", 
"blocked", "allocatable", "activated":

     <action disp="invalid" any-variant="invalid"/>
     <action disp="blocked" any-variant="blocked"/>
     <action disp="allocatable" any-variant="allocatable"/>
     <action disp="activated" all-variants="activated"/>

A final default action sets the disposition to "valid" for any label 
matching the repertoire for which no other action has been triggered. 
This "catch-all" action also matches all remaining variant labels from 
variants that do not have a type value.

     <action disp="valid" comment="Catch-all if other rules not met"/>

Conceptually, the implicitly defined default actions act just like a 
block of action elements that is added (virtually) beyond the last of 
the user-supplied actions. Any label not processed by the user-supplied 
actions would thus be processed by the default actions as if they were 
present in the LGR. As the last default action is a "catch-all", all 
processing is guaranteed to end with a definite disposition for the label.


>
>
>
> _______________________________________________
> Lager mailing list
> Lager@ietf.org
> https://www.ietf.org/mailman/listinfo/lager


--------------070608000706080404020806
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta content="text/html; charset=utf-8" http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <div class="moz-cite-prefix">On 3/25/2016 1:14 AM, Alexey Melnikov
      wrote:<br>
    </div>
    <blockquote
      cite="mid:9E846AF5-6043-4715-8FD4-341D49EA9A17@fastmail.fm"
      type="cite">
      <meta http-equiv="content-type" content="text/html; charset=utf-8">
      <div>Hi Asmus,<br>
      </div>
      <div><br>
        On 24 Mar 2016, at 23:29, Asmus Freytag (t) &lt;<a
          class="moz-txt-link-abbreviated"
          href="mailto:asmus-inc@ix.netcom.com"><a class="moz-txt-link-abbreviated" href="mailto:asmus-inc@ix.netcom.com">asmus-inc@ix.netcom.com</a></a>&gt;

        wrote:<br>
        <br>
      </div>
      <blockquote type="cite">
        <div>
          <meta content="text/html; charset=utf-8"
            http-equiv="Content-Type">
          <div class="moz-cite-prefix">I'll let Kim address the issues
            with 4.3.5 and 11.3 (media type and registration).<br>
            <br>
            Here some comments on the issues raised against 6.1 and 7.6.<br>
            <br>
            A./<br>
            <br>
            On 3/24/2016 10:46 AM, Alexey Melnikov wrote:<br>
          </div>
          <blockquote
cite="mid:1458841579.4011697.558814722.09946B62@webmail.messagingengine.com"
            type="cite">
            <pre wrap="">In 6.1:

</pre>
            <blockquote type="cite" style="font-size: large; color:
              #3333FF;">
              <pre wrap=""><span class="moz-txt-citetags">&gt;</span>A rule MAY contain the following as child elements:
</pre>
            </blockquote>
            <pre wrap="">Nit: This is an invalid use of MAY, because it is not an implementation
choice. I don't think you meant here that implementations don't have to
support any of the listed child elements?</pre>
          </blockquote>
          <br>
          What is the specification aimed at? It's a file format. That
          means, there are different levels of requirements for authors
          (of what may be a single LGR document, which does not have to
          include all possible features) </div>
      </blockquote>
      <div><br>
      </div>
      Ok, but isn't that true for pretty much all the features in the
      format? Why is this one special?
      <div><br>
      </div>
      <div>
        <blockquote type="cite">
          <div>and implementations (that we would expect of being able
            to interpret any well-formed LGR document). It seems to me:<br>
            <br>
            <ul>
              <li>Implementations (readers, parsers, validators) MUST
                support all features, including OPTIONAL ones.</li>
            </ul>
          </div>
        </blockquote>
        <div><br>
        </div>
        I thought your document was mostly targeting implementations. If
        not, having a separate section that covers authors might be a
        good idea.<br>
        <blockquote type="cite">
          <div>
            <ul>
              <li>Authors MAY supply any features, except those that
                MUST NOT be present, and MUST supply all required
                features.</li>
            </ul>
            In that context, MAY or not MAY in the above example?<br>
            <br>
            Aside from that, would it have been better to write:<br>
            <br>
            "A rule may contain the following OPTIONAL child elements"<br>
          </div>
        </blockquote>
        <div><br>
        </div>
        INHO, this is no better, because you are not telling who are
        they optional for.<br>
      </div>
    </blockquote>
    <br>
    Looked at the text in context. MAY ---&gt; may is fine anyway,
    because the passage is somewhat introductory.<br>
    <blockquote
      cite="mid:9E846AF5-6043-4715-8FD4-341D49EA9A17@fastmail.fm"
      type="cite">
      <div>
        <blockquote type="cite">
          <div>
            <blockquote
cite="mid:1458841579.4011697.558814722.09946B62@webmail.messagingengine.com"
              type="cite">
              <pre wrap="">In 7.6:

</pre>
              <blockquote type="cite" style="font-size: large; color:
                #3333FF;">
                <pre wrap=""><span class="moz-txt-citetags">&gt; </span>If no actions are defined for the standard disposition values of
<span class="moz-txt-citetags">&gt; </span>"invalid", "blocked", "allocatable", "activated", then the following
<span class="moz-txt-citetags">&gt; </span>implicitly defined default actions are evaluated.
</pre>
              </blockquote>
              <pre wrap="">Are default actions defined if none of the actions for recommended
standard dispositions is defined or if any of them is not defined? For
example, I was thinking whether it would be Ok to just automatically
(and unconditionally) append these default actions to any LGR file for
purposes of evaluation? If any action for standard disposition value is
already defined and it would take precedence, so the corresponding
default action would be ignored.</pre>
            </blockquote>
            Yes, this can be improved.<br>
            <br>
            I think it would be cleanest to describe the "implicitly
            defined default actions" as a block of &lt;action&gt;
            elements that is added (virtually) beyond the last of the
            user-supplied actions. Any label not processed by the
            user-supplied actions would be processed by these
            "implicitly defined default actions" as if they were present
            in the file. As the last one is a "catch-all", all
            processing is guaranteed to end with a definite disposition
            for the label.<br>
          </div>
        </blockquote>
        <div><br>
        </div>
        Right, this is what I thought.<br>
        <blockquote type="cite">
          <div> <br>
            Note that the phrase used in the existing description
            ("standard disposition values") is potentially misleading,
            because we now make the distinction between "types" (on
            variant mappings) and "dispositions" (as result of
            processing labels). We didn't use to and this wording may be
            a holdover.<br>
            <br>
            I'll look at suggested wording.<br>
          </div>
        </blockquote>
        <div><br>
        </div>
        That would be great, thank you.<br>
      </div>
    </blockquote>
    <br>
    I cleaned up the passage and added a note that makes the point about
    default actions being treated as if added past the last user defined
    action.  (See below).<br>
    <br>
    A./<br>
    <br>
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
    <span class="Apple-style-span" style="border-collapse: separate;
      color: rgb(0, 0, 0); font-family: Arial; font-style: normal;
      font-variant: normal; font-weight: normal; letter-spacing: normal;
      line-height: normal; orphans: 2; text-align: auto; text-indent:
      0px; text-transform: none; white-space: normal; widows: 2;
      word-spacing: 0px; -webkit-border-horizontal-spacing: 0px;
      -webkit-border-vertical-spacing: 0px;
      -webkit-text-decorations-in-effect: none;
      -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px;
      font-size: medium; "><span class="Apple-style-span"
        style="font-family: verdana, helvetica, arial, sans-serif;
        font-size: 13px; ">
        <h1 id="rfc.section.7.6" style="font-size: 14pt; line-height:
          21pt; page-break-after: avoid; "><a href="#default_actions"
            id="default_actions" style="text-decoration: none; color:
            rgb(51, 51, 51); ">7.6 Default Actions</a></h1>
        <p id="rfc.section.7.6.p.1" style="margin-left: 2em;
          margin-right: 2em; ">If a label does not trigger any of the
          actions defined explicitly in the LGR, the following
          implicitly defined default actions are evaluated. They are
          shown below in their relative order of precedence (see<span
            class="Apple-converted-space"> </span><a href="#precedence"
            style="text-decoration: none; ">Section 7.4</a>). Default
          actions have a lower order of precedence than explicit actions
          (see<span class="Apple-converted-space"> </span><a
            href="#determining_dispositions" style="text-decoration:
            none; ">Section 8.3</a>).</p>
        <p id="rfc.section.7.6.p.2" style="margin-left: 2em;
          margin-right: 2em; ">The default actions for variant labels
          are defined as follows. The first set is triggered based on
          the standard variant type values of "invalid", "blocked",
          "allocatable", "activated":</p>
        <pre style="margin-left: 3em; background-color: rgb(255, 255, 224); padding-top: 0.25em; padding-right: 0.25em; padding-bottom: 0.25em; padding-left: 0.25em; ">    &lt;action disp="invalid" any-variant="invalid"/&gt;
    &lt;action disp="blocked" any-variant="blocked"/&gt;
    &lt;action disp="allocatable" any-variant="allocatable"/&gt;
    &lt;action disp="activated" all-variants="activated"/&gt;</pre>
        <p id="rfc.section.7.6.p.4" style="margin-left: 2em;
          margin-right: 2em; ">A final default action sets the
          disposition to "valid" for any label matching the repertoire
          for which no other action has been triggered. This "catch-all"
          action also matches all remaining variant labels from variants
          that do not have a type value.</p>
        <pre style="margin-left: 3em; background-color: rgb(255, 255, 224); padding-top: 0.25em; padding-right: 0.25em; padding-bottom: 0.25em; padding-left: 0.25em; ">    &lt;action disp="valid" comment="Catch-all if other rules not met"/&gt;</pre>
        <p id="rfc.section.7.6.p.6" style="margin-left: 2em;
          margin-right: 2em; ">Conceptually, the implicitly defined
          default actions act just like a block of action elements that
          is added (virtually) beyond the last of the user-supplied
          actions. Any label not processed by the user-supplied actions
          would thus be processed by the default actions as if they were
          present in the LGR. As the last default action is a
          "catch-all", all processing is guaranteed to end with a
          definite disposition for the label.</p>
      </span></span><br>
    <blockquote
      cite="mid:9E846AF5-6043-4715-8FD4-341D49EA9A17@fastmail.fm"
      type="cite">
      <div><br>
      </div>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap="">_______________________________________________
Lager mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Lager@ietf.org">Lager@ietf.org</a>
<a class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/lager">https://www.ietf.org/mailman/listinfo/lager</a>
</pre>
    </blockquote>
    <br>
  </body>
</html>

--------------070608000706080404020806--


From nobody Fri Mar 25 09:48:50 2016
Return-Path: <aamelnikov@fastmail.fm>
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 78FC612D1A0 for <lager@ietfa.amsl.com>; Fri, 25 Mar 2016 09:48:48 -0700 (PDT)
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, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=fastmail.fm header.b=pymlCBCL; dkim=pass (1024-bit key) header.d=messagingengine.com header.b=RbGvcas5
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 kZthgHDvVBye for <lager@ietfa.amsl.com>; Fri, 25 Mar 2016 09:48:47 -0700 (PDT)
Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1D38B12D15F for <lager@ietf.org>; Fri, 25 Mar 2016 09:48:47 -0700 (PDT)
Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.nyi.internal (Postfix) with ESMTP id 82305204A6 for <lager@ietf.org>; Fri, 25 Mar 2016 12:48:46 -0400 (EDT)
Received: from frontend2 ([10.202.2.161]) by compute3.internal (MEProxy); Fri, 25 Mar 2016 12:48:46 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=fastmail.fm; h=cc :content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-sasl-enc :x-sasl-enc; s=mesmtp; bh=nO0sdQQigvaMUVFtXE484tUjYjc=; b=pymlCB CLZImOocNhipMmUW98g3hZB6bCz5M1glWWGZQPb1SwIn6pGTN+iYW+S/t0y4P1So AlJGTsjzAJDgeE9aZRQDHnG1K6QS129GPdMyYadR8bboeEKe+n2eaxI6KOc5oQ7r yM/CHnA0kdJCDlPL9geTbCkY/v3f75DXxM3+w=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-sasl-enc:x-sasl-enc; s=smtpout; bh=nO0sdQQigvaMUVF tXE484tUjYjc=; b=RbGvcas5AQ0bO+rYSVrh7GM1iV+AvWsulsXlv/b0NkDcOnv 0W+twzLpK24Vw/a2XdwRh26uuhTL6nfptZLcM4e5t/iNflg6EpCLlB71wuKOPMAD NDbQnQEBHqwWxxFpfOfzVAmnIGjZgI6OI6qb7R31UGqK1MtoycJaBv61MTJc=
X-Sasl-enc: 78489jgywIbm/CDjYYaiDMJySHQcK4kcMwL+hXcSGLwH 1458924525
Received: from [10.13.96.154] (unknown [85.255.235.167]) by mail.messagingengine.com (Postfix) with ESMTPA id E721D680233; Fri, 25 Mar 2016 12:48:45 -0400 (EDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (1.0)
From: Alexey Melnikov <aamelnikov@fastmail.fm>
X-Mailer: iPhone Mail (13D15)
In-Reply-To: <56F55811.8070602@ix.netcom.com>
Date: Fri, 25 Mar 2016 16:51:36 +0000
Content-Transfer-Encoding: 7bit
Message-Id: <23236EE7-EA0C-45E7-822B-1D0976146E9F@fastmail.fm>
References: <1458841579.4011697.558814722.09946B62@webmail.messagingengine.com> <56F47849.6050607@ix.netcom.com> <9E846AF5-6043-4715-8FD4-341D49EA9A17@fastmail.fm> <56F55811.8070602@ix.netcom.com>
To: Asmus Freytag <asmusf@ix.netcom.com>
Archived-At: <http://mailarchive.ietf.org/arch/msg/lager/5P_IzTmXlq67Cag5FAEAV3--tgU>
Cc: lager@ietf.org
Subject: Re: [Lager] Incoming AD review on draft-ietf-lager-specification-11.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: Fri, 25 Mar 2016 16:48:48 -0000

All your suggestions look good, thank you!


From nobody Wed Mar 30 15:47:37 2016
Return-Path: <kim.davies@icann.org>
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 7861212D10E for <lager@ietfa.amsl.com>; Wed, 30 Mar 2016 15:47:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.211
X-Spam-Level: 
X-Spam-Status: No, score=-4.211 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 U0RsdVcHTHkx for <lager@ietfa.amsl.com>; Wed, 30 Mar 2016 15:47:34 -0700 (PDT)
Received: from out.west.pexch112.icann.org (pfe112-ca-2.pexch112.icann.org [64.78.40.10]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7C79F12D0FF for <lager@ietf.org>; Wed, 30 Mar 2016 15:47:34 -0700 (PDT)
Received: from PMBX112-W1-CA-1.pexch112.icann.org (64.78.40.21) by PMBX112-W1-CA-2.pexch112.icann.org (64.78.40.23) with Microsoft SMTP Server (TLS) id 15.0.1130.7; Wed, 30 Mar 2016 15:47:32 -0700
Received: from PMBX112-W1-CA-1.pexch112.icann.org ([64.78.40.21]) by PMBX112-W1-CA-1.PEXCH112.ICANN.ORG ([64.78.40.21]) with mapi id 15.00.1130.005; Wed, 30 Mar 2016 15:47:31 -0700
From: Kim Davies <kim.davies@icann.org>
To: Alexey Melnikov <aamelnikov@fastmail.fm>, "lager@ietf.org" <lager@ietf.org>
Thread-Topic: [Lager] Incoming AD review on draft-ietf-lager-specification-11.txt
Thread-Index: AQHRhfUkjK6RsULYYUKzlcmOVS3cHp9yoF0A
Date: Wed, 30 Mar 2016 22:47:31 +0000
Message-ID: <D1EC5ECF-CBA6-4D02-A202-77D41DAD3A9A@icann.org>
References: <1458841579.4011697.558814722.09946B62@webmail.messagingengine.com>
In-Reply-To: <1458841579.4011697.558814722.09946B62@webmail.messagingengine.com>
Accept-Language: en-AU, en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/0.0.0.160212
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [192.0.32.234]
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha256; boundary="B_3542197650_1159111204"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/lager/v35Zqj-apILgPD3qJ4B0QzOiRxc>
Subject: Re: [Lager] Incoming AD review on draft-ietf-lager-specification-11.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: Wed, 30 Mar 2016 22:47:36 -0000

--B_3542197650_1159111204
Content-type: text/plain;
	charset="UTF-8"
Content-transfer-encoding: 7bit

Hi Alexey, Hi all,

On 3/24/16, 10:46 AM, "Lager on behalf of Alexey Melnikov" <lager-bounces@ietf.org on behalf of aamelnikov@fastmail.fm> wrote:




>
>In Section 4.3.5
>
>The first mention of "media type" needs a normative reference to RFC
>2045. This would save developers time with trying to find out what
>syntax to support and where to find registered media types.

OK, will add.

>In 11.3:
>
>I think this section needs a bit of work. Firstly, it might be better to
>say that Standard Dispositions MUST NOT contain ":" character in order
>to prevent clashes with private dispositions.

OK.

>Also, saying that registered values are lowercase ASCII (for example)
>would be a good idea. If you want to only allow ASCII, but not to limit
>values to lowercase letters, then you need to say whether values in the
>registry are case-sensitive or not.

I imagine this observation can be made more generally across the specification.
I can make this change but wonder if the case-sensitivity needs to
be explicit in other aspects of the specification for the same reason?

>> Private Dispositions - This registry shall list dispositions that
>> have been registered on a first-come first-served basis by third parties
>> with the IANA. Such dispositions must take the form "entity:disposition"
>> where the entity is a prefix that uniquely identifies the private user
>> of the namespace. For example, "acme:reserved" could be a private extension
>> used by the organization ACME to denote a disposition relating to reserved
>> labels.
>
>I think "entity" should be better specified. Which characters are
>allowed? I would recommend either use domain names to describe ownerhip
>(I can suggest some text) or use values from the PEN IANA registry
><https://www.iana.org/assignments/enterprise-numbers/enterprise-numbers>?

Given it sounds like you have a clear concept in your mind, I would appreciate
suggested text on how to use domain names or PENs to namespace the private
dispositions. A domain name based approach may be the simplest option here
given that PENs may be an unfamiliar concept to typical authors of these tables,
and are not used elsewhere in the document.

kim
--B_3542197650_1159111204
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"

MIIRxgYJKoZIhvcNAQcCoIIRtzCCEbMCAQExDzANBglghkgBZQMEAgEFADALBgkqhkiG9w0B
BwGggg97MIIFajCCBFKgAwIBAgIQAzf9pnruIxQ3CluP694WujANBgkqhkiG9w0BAQsFADBl
MQswCQYDVQQGEwJVUzEVMBMGA1UEChMMRGlnaUNlcnQgSW5jMRkwFwYDVQQLExB3d3cuZGln
aWNlcnQuY29tMSQwIgYDVQQDExtEaWdpQ2VydCBTSEEyIEFzc3VyZWQgSUQgQ0EwHhcNMTUw
MzMxMDAwMDAwWhcNMTgwMzMxMTIwMDAwWjCBizELMAkGA1UEBhMCVVMxEzARBgNVBAgTCkNh
bGlmb3JuaWExFDASBgNVBAcTC0xvcyBBbmdlbGVzMTwwOgYDVQQKEzNJbnRlcm5ldCBDb3Jw
b3JhdGlvbiBmb3IgQXNzaWduZWQgTmFtZXMgYW5kIE51bWJlcnMxEzARBgNVBAMTCktpbSBE
YXZpZXMwggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQCnSZUaeAzcQA+uyKoPVGAw
l+6Ts/OnBoRHtOHz52LwDoUtjszVc1hh7Z3nNWMdnbiABMRFXdlKvDg7L5Qb9FSseUbFpiUi
RMDxkHgc4WtgdoFN/YFUVmqwx5wHMfT/6RnRF1zuh1T7jyKiLk2Ok82/t46ZJCWFA04dEqbj
2G3Mo2VOiezgsO/tCTHOzYkGPVPOUSZciEeYc8UuqpbriQUtZ5aiXBKhomJncawUsLAQp0ak
goArkUUvdSN7SSaxS751tKTnJDMJ/g1WvcdKn3Kb3sTtJy2/NbIr1AMnQ/oR3zya3uo3We0b
IzJ49NPZeLr007Ka13XpCH8tm8a76N8dAgMBAAGjggHtMIIB6TAfBgNVHSMEGDAWgBTnAiOA
AE/Y17yUC9k/dDlJMjyKeTAdBgNVHQ4EFgQUeR6567hS8LRt7eqNsDi2wzOgdZswDAYDVR0T
AQH/BAIwADAfBgNVHREEGDAWgRRraW0uZGF2aWVzQGljYW5uLm9yZzAOBgNVHQ8BAf8EBAMC
BaAwHQYDVR0lBBYwFAYIKwYBBQUHAwIGCCsGAQUFBwMEMEMGA1UdIAQ8MDowOAYKYIZIAYb9
bAQBAjAqMCgGCCsGAQUFBwIBFhxodHRwczovL3d3dy5kaWdpY2VydC5jb20vQ1BTMIGIBgNV
HR8EgYAwfjA9oDugOYY3aHR0cDovL2NybDMuZGlnaWNlcnQuY29tL0RpZ2lDZXJ0U0hBMkFz
c3VyZWRJRENBLWcxLmNybDA9oDugOYY3aHR0cDovL2NybDQuZGlnaWNlcnQuY29tL0RpZ2lD
ZXJ0U0hBMkFzc3VyZWRJRENBLWcxLmNybDB5BggrBgEFBQcBAQRtMGswJAYIKwYBBQUHMAGG
GGh0dHA6Ly9vY3NwLmRpZ2ljZXJ0LmNvbTBDBggrBgEFBQcwAoY3aHR0cDovL2NhY2VydHMu
ZGlnaWNlcnQuY29tL0RpZ2lDZXJ0U0hBMkFzc3VyZWRJRENBLmNydDANBgkqhkiG9w0BAQsF
AAOCAQEAkBKX2jFEiA3GYcBHIBiRlZjXse/TZ/T2ID0BeHKWvR44Spn3oKz9VZj4Jmnx4OfK
GiQZiheG/ytEWNX69fUlLvZrqQSYCFfLiH9oKr0qDNOm+gNbu4KWTeIdiznpE32kKJ2Crsbi
bZrknFUB4h6nWJgPHmoTQYa2qoUcdnaJS90oPX2ZznZxVw4qGafg/SuXajPuNI2MGoAOl1LX
WaHeyARAz9wBWZB5wZXlxSV9HAR0DgMOFvPn6BrxdclRnL5ebzJlemoBPNNqYzsRca6pbUM+
otK7vjxmZBiM0UN0AxHA7brsRcJFPIshZvYHHMkmSdVeNKIBhe8kvQgwi9EZIDCCBk4wggU2
oAMCAQICEASueWBmZpAaucV/pmxb3M0wDQYJKoZIhvcNAQELBQAwZTELMAkGA1UEBhMCVVMx
FTATBgNVBAoTDERpZ2lDZXJ0IEluYzEZMBcGA1UECxMQd3d3LmRpZ2ljZXJ0LmNvbTEkMCIG
A1UEAxMbRGlnaUNlcnQgQXNzdXJlZCBJRCBSb290IENBMB4XDTEzMTEwNTEyMDAwMFoXDTI4
MTEwNTEyMDAwMFowZTELMAkGA1UEBhMCVVMxFTATBgNVBAoTDERpZ2lDZXJ0IEluYzEZMBcG
A1UECxMQd3d3LmRpZ2ljZXJ0LmNvbTEkMCIGA1UEAxMbRGlnaUNlcnQgU0hBMiBBc3N1cmVk
IElEIENBMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA3PgRIz9qte/AJ3kbLQWH
ohBDMd8O1BUbT3ekIs4+jHDwvgeO3ScqvAEdtiwKyt1pWB9B7WoFH9pjeFkeIiwr+Lp+yTU7
VvEffEJ+JbAjGcZFONc9RPkgfGCuHLBaGAS+jzv3qfCUmqYMY0m2QRdTQDK9T+ZQelAfJUXo
8Ymvzf9e/1Dz8BcR/73FifW9YrnY+45FBIVtmc3FSE39JqsCNkXqNtdfauIagkEK3OnZ9ZEX
jsYhrTg8E+Yef2ac1U3ZRtr2z1KnfTskw7TBUTXGm+vU737kewPhRL16CzfgT8uCig1xGOSm
4IksG/OyczzBsJKeGH29q33FfQihLMKfcwIDAQABo4IC+DCCAvQwEgYDVR0TAQH/BAgwBgEB
/wIBADAOBgNVHQ8BAf8EBAMCAYYwNAYIKwYBBQUHAQEEKDAmMCQGCCsGAQUFBzABhhhodHRw
Oi8vb2NzcC5kaWdpY2VydC5jb20wgYEGA1UdHwR6MHgwOqA4oDaGNGh0dHA6Ly9jcmw0LmRp
Z2ljZXJ0LmNvbS9EaWdpQ2VydEFzc3VyZWRJRFJvb3RDQS5jcmwwOqA4oDaGNGh0dHA6Ly9j
cmwzLmRpZ2ljZXJ0LmNvbS9EaWdpQ2VydEFzc3VyZWRJRFJvb3RDQS5jcmwwHQYDVR0lBBYw
FAYIKwYBBQUHAwIGCCsGAQUFBwMEMIIBswYDVR0gBIIBqjCCAaYwggGiBgpghkgBhv1sAAIE
MIIBkjAoBggrBgEFBQcCARYcaHR0cHM6Ly93d3cuZGlnaWNlcnQuY29tL0NQUzCCAWQGCCsG
AQUFBwICMIIBVh6CAVIAQQBuAHkAIAB1AHMAZQAgAG8AZgAgAHQAaABpAHMAIABDAGUAcgB0
AGkAZgBpAGMAYQB0AGUAIABjAG8AbgBzAHQAaQB0AHUAdABlAHMAIABhAGMAYwBlAHAAdABh
AG4AYwBlACAAbwBmACAAdABoAGUAIABEAGkAZwBpAEMAZQByAHQAIABDAFAALwBDAFAAUwAg
AGEAbgBkACAAdABoAGUAIABSAGUAbAB5AGkAbgBnACAAUABhAHIAdAB5ACAAQQBnAHIAZQBl
AG0AZQBuAHQAIAB3AGgAaQBjAGgAIABsAGkAbQBpAHQAIABsAGkAYQBiAGkAbABpAHQAeQAg
AGEAbgBkACAAYQByAGUAIABpAG4AYwBvAHIAcABvAHIAYQB0AGUAZAAgAGgAZQByAGUAaQBu
ACAAYgB5ACAAcgBlAGYAZQByAGUAbgBjAGUALjAdBgNVHQ4EFgQU5wIjgABP2Ne8lAvZP3Q5
STI8inkwHwYDVR0jBBgwFoAUReuir/SSy4IxLVGLp6chnfNtyA8wDQYJKoZIhvcNAQELBQAD
ggEBAE7UiSe5/R2Hd34PKAWQ8QovyTs+vZOckMav+pFRhzJUa+jKwXFRXJmOtfrgYhmZpgea
fBMn2+UCooQS2RX2CkRXxDSPbXMfOtagAT3e44LkRWuy6yX9gF4dOZC+W0L2zpFg4/mgVgxI
EM4zaHvNk6vwastPWA+5e10bBIGepyLiV0kn7pKTCL5pCFMCOi5dyBn0UIBOAtmwXZG0k4f5
lpaBVUCOZu2C2LsoX+1MYe0GWCgZUxFEvEcgKbIEbNiJVJk7ddtneCweknjGVT1YEhEybr1D
DE0023vGQtvsvqubYUwGkuOO3yEqUFcEwGCiNdUknmY3CUnP1fhls+DibsIwggO3MIICn6AD
AgECAhAM5+DlF9hG/o/lYPwb8DA5MA0GCSqGSIb3DQEBBQUAMGUxCzAJBgNVBAYTAlVTMRUw
EwYDVQQKEwxEaWdpQ2VydCBJbmMxGTAXBgNVBAsTEHd3dy5kaWdpY2VydC5jb20xJDAiBgNV
BAMTG0RpZ2lDZXJ0IEFzc3VyZWQgSUQgUm9vdCBDQTAeFw0wNjExMTAwMDAwMDBaFw0zMTEx
MTAwMDAwMDBaMGUxCzAJBgNVBAYTAlVTMRUwEwYDVQQKEwxEaWdpQ2VydCBJbmMxGTAXBgNV
BAsTEHd3dy5kaWdpY2VydC5jb20xJDAiBgNVBAMTG0RpZ2lDZXJ0IEFzc3VyZWQgSUQgUm9v
dCBDQTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAK0OFc7kQ4BcsYfzt2D5cRKl
rtwmlIiq9M71IDkoWGAM+IDaqRWVMmE8tbEohIqK3J8KDIMXeo+QrIrneVNcMYQq9g+YMjZ2
zN7dPKii72r7IfJSYd+fINcf4rHZ/hhk0hJbX/lYGDW8R82hNvlrf9SwOD7BG8OMM9nYLxj+
KA+zp4PWw25EwGE1lhb+WZyLdm3X8aJLDSv/C3LanmDQjpA1xnhVhyChz+VtCshJfDGYM2wi
6YfQMlqiuhOCEe05F52ZOnKh5vqk2dUXMXWuhX0irj8BRob2KHnIsdrkVxfEfhwOsLSSplaz
vbKX7aqn8LfFqD+VFtD/oZbrCF8Yd08CAwEAAaNjMGEwDgYDVR0PAQH/BAQDAgGGMA8GA1Ud
EwEB/wQFMAMBAf8wHQYDVR0OBBYEFEXroq/0ksuCMS1Ri6enIZ3zbcgPMB8GA1UdIwQYMBaA
FEXroq/0ksuCMS1Ri6enIZ3zbcgPMA0GCSqGSIb3DQEBBQUAA4IBAQCiDrzf4u3w43JzemSU
v/dyZtgy5EJ1Yq6H6/LV2d5Ws5/MzhQouQ2XYFwSTFjk0z2DSUVYlzVpGqhH6lbGeasS2GeB
hN9/CTyU5rgmLCC9PbMoifdf/yLil4Qf6WXvh+DfwWdJs13rsgkq6ybteL59PyvztyY1bV+J
AbZJW58BBZurPSXBzLZ/wvFvhsb6ZGjrgS2U60K3+owe3WLxvlBnt2y98/Efaww2BxZ/N3yp
W2168RJGYIPXJwS+S86XvsNnKmgR34DnDDNmvxMNFG7zfx9jEB76jRslbWyPpbdhAbHSoyah
EHGdreLD+cOZUbcrBwjOLuZQsqf6CkUvovDyMYICDzCCAgsCAQEweTBlMQswCQYDVQQGEwJV
UzEVMBMGA1UEChMMRGlnaUNlcnQgSW5jMRkwFwYDVQQLExB3d3cuZGlnaWNlcnQuY29tMSQw
IgYDVQQDExtEaWdpQ2VydCBTSEEyIEFzc3VyZWQgSUQgQ0ECEAM3/aZ67iMUNwpbj+veFrow
DQYJYIZIAWUDBAIBBQCgaTAvBgkqhkiG9w0BCQQxIgQgmKEfQptyGLak3EZ7ql1b4kBHhIFs
O1gF0/r24ydYTtUwGAYJKoZIhvcNAQkDMQsGCSqGSIb3DQEHATAcBgkqhkiG9w0BCQUxDxcN
MTYwMzMwMjI0NzMwWjANBgkqhkiG9w0BAQEFAASCAQCZ0y2iBEJ0XwfgD6s6l+zulGUwOSkf
Ct+DRhhdEm4wmWXLuL+iyGSxio6GnvqZ27kyYFDsaPdACvHsEqfEYTEFcggIGvvMO9EyQDGG
LdTuPAKvfEvngeot4xZ2vu5nbRf4/y3JerE6rEr5J/x05lPYwc3zWYxzHkZZp7zVNHJzuuDY
msKpsRn+mbydN+rNaGkA3+pDlvPBPbCSX/aOxbYI3hj0TexDfOaEoekNQsZXLpzy20Hst57D
WNenn5qRnAfbFJnvH1t7Wcw/eVMbHsKqmONPNuhU3l3x4PJ2GM8BGqpljUddy0xxfcdlZ2rJ
ZyW8iXdF2vb4IQu2Z3TuFrpA

--B_3542197650_1159111204--


From nobody Wed Mar 30 16:08:34 2016
Return-Path: <marc.blanchet@viagenie.ca>
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 A4DD912D0FF for <lager@ietfa.amsl.com>; Wed, 30 Mar 2016 16:08:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.911
X-Spam-Level: 
X-Spam-Status: No, score=-1.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 sFMPK7AnxXxB for <lager@ietfa.amsl.com>; Wed, 30 Mar 2016 16:08:31 -0700 (PDT)
Received: from jazz.viagenie.ca (jazz.viagenie.ca [IPv6:2620:0:230:8000::2]) by ietfa.amsl.com (Postfix) with ESMTP id 909A912D0E1 for <lager@ietf.org>; Wed, 30 Mar 2016 16:08:31 -0700 (PDT)
Received: from [192.168.1.111] (modemcable093.65-160-184.mc.videotron.ca [184.160.65.93]) by jazz.viagenie.ca (Postfix) with ESMTPSA id E1B5A47694; Wed, 30 Mar 2016 19:08:30 -0400 (EDT)
From: "Marc Blanchet" <marc.blanchet@viagenie.ca>
To: "Kim Davies" <kim.davies@icann.org>
Date: Wed, 30 Mar 2016 19:08:30 -0400
Message-ID: <FABCB9CF-03A8-4C25-A622-47204C39D84C@viagenie.ca>
In-Reply-To: <D1EC5ECF-CBA6-4D02-A202-77D41DAD3A9A@icann.org>
References: <1458841579.4011697.558814722.09946B62@webmail.messagingengine.com> <D1EC5ECF-CBA6-4D02-A202-77D41DAD3A9A@icann.org>
MIME-Version: 1.0
Content-Type: text/plain; format=flowed
X-Mailer: MailMate (1.9.4r5234)
Archived-At: <http://mailarchive.ietf.org/arch/msg/lager/QQP3-rUeFeAofsL_O2fMB8GzbWM>
Cc: "lager@ietf.org" <lager@ietf.org>, Alexey Melnikov <aamelnikov@fastmail.fm>
Subject: Re: [Lager] Incoming AD review on draft-ietf-lager-specification-11.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: Wed, 30 Mar 2016 23:08:33 -0000

On 30 Mar 2016, at 18:47, Kim Davies wrote:

> Hi Alexey, Hi all,
>
> On 3/24/16, 10:46 AM, "Lager on behalf of Alexey Melnikov" 
> <lager-bounces@ietf.org on behalf of aamelnikov@fastmail.fm> wrote:
>
>
>
>
>>
>> In Section 4.3.5
>>
>> The first mention of "media type" needs a normative reference to RFC
>> 2045. This would save developers time with trying to find out what
>> syntax to support and where to find registered media types.
>
> OK, will add.
>
>> In 11.3:
>>
>> I think this section needs a bit of work. Firstly, it might be better 
>> to
>> say that Standard Dispositions MUST NOT contain ":" character in 
>> order
>> to prevent clashes with private dispositions.
>
> OK.
>
>> Also, saying that registered values are lowercase ASCII (for example)
>> would be a good idea. If you want to only allow ASCII, but not to 
>> limit
>> values to lowercase letters, then you need to say whether values in 
>> the
>> registry are case-sensitive or not.
>
> I imagine this observation can be made more generally across the 
> specification.
> I can make this change but wonder if the case-sensitivity needs to
> be explicit in other aspects of the specification for the same reason?
>
>>> Private Dispositions - This registry shall list dispositions that
>>> have been registered on a first-come first-served basis by third 
>>> parties
>>> with the IANA. Such dispositions must take the form 
>>> "entity:disposition"
>>> where the entity is a prefix that uniquely identifies the private 
>>> user
>>> of the namespace. For example, "acme:reserved" could be a private 
>>> extension
>>> used by the organization ACME to denote a disposition relating to 
>>> reserved
>>> labels.
>>
>> I think "entity" should be better specified. Which characters are
>> allowed? I would recommend either use domain names to describe 
>> ownerhip
>> (I can suggest some text) or use values from the PEN IANA registry
>> <https://www.iana.org/assignments/enterprise-numbers/enterprise-numbers>?
>
> Given it sounds like you have a clear concept in your mind, I would 
> appreciate
> suggested text on how to use domain names or PENs to namespace the 
> private
> dispositions. A domain name based approach may be the simplest option 
> here
> given that PENs may be an unfamiliar concept to typical authors of 
> these tables,
> and are not used elsewhere in the document.

FYI, we used PEN for vCard4 private namespace. Having said that, the set 
of organisations for developing extensions of vCards is pretty small and 
well known and have 99% of chance of 1. having a PEN 2. large 
corporations with engineering staff that may find easy.  On the other 
hand, LGR editors could be linguistic experts which have no clue of the 
PEN and may not relate to PEN registration (even if it is FCFS). So I 
think domain names are probably better in this case.

Marc.


>
> kim_______________________________________________
> Lager mailing list
> Lager@ietf.org
> https://www.ietf.org/mailman/listinfo/lager


From nobody Wed Mar 30 20:41:25 2016
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 A8FEF12D524 for <lager@ietfa.amsl.com>; Wed, 30 Mar 2016 20:41:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.719
X-Spam-Level: 
X-Spam-Status: No, score=-2.719 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, 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 eAftnNrcAup0 for <lager@ietfa.amsl.com>; Wed, 30 Mar 2016 20:41:16 -0700 (PDT)
Received: from elasmtp-spurfowl.atl.sa.earthlink.net (elasmtp-spurfowl.atl.sa.earthlink.net [209.86.89.66]) by ietfa.amsl.com (Postfix) with ESMTP id 0ED8312D0E6 for <lager@ietf.org>; Wed, 30 Mar 2016 20:41:15 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=ix.netcom.com; b=twvOwdSnfiC2KuCpeO/FWrzb+qK0J6Gr0PSOzK9hEcKrqEUzgas1QnRbD3i9X1w5; h=Received:Subject:To:References:From:Message-ID:Date:User-Agent:MIME-Version:In-Reply-To:Content-Type:X-ELNK-Trace:X-Originating-IP;
Received: from [71.35.115.182] (helo=[192.168.1.103]) by elasmtp-spurfowl.atl.sa.earthlink.net with esmtpa (Exim 4.67) (envelope-from <asmusf@ix.netcom.com>) id 1alTTm-0003DS-SI for lager@ietf.org; Wed, 30 Mar 2016 23:41:07 -0400
To: lager@ietf.org
References: <1458841579.4011697.558814722.09946B62@webmail.messagingengine.com> <D1EC5ECF-CBA6-4D02-A202-77D41DAD3A9A@icann.org>
From: "Asmus Freytag (c)" <asmusf@ix.netcom.com>
Message-ID: <56FC9C52.2090501@ix.netcom.com>
Date: Wed, 30 Mar 2016 20:41:06 -0700
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.7.1
MIME-Version: 1.0
In-Reply-To: <D1EC5ECF-CBA6-4D02-A202-77D41DAD3A9A@icann.org>
Content-Type: multipart/alternative; boundary="------------080502040607090100080300"
X-ELNK-Trace: 464f085de979d7246f36dc87813833b2857e9f10d2205ddc09aa0fe54e167dfb47c2016363dea2d6350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 71.35.115.182
Archived-At: <http://mailarchive.ietf.org/arch/msg/lager/qXcvR0zAyASaZXHncfIkY80gF2o>
Subject: Re: [Lager] Incoming AD review on draft-ietf-lager-specification-11.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, 31 Mar 2016 03:41:19 -0000

This is a multi-part message in MIME format.
--------------080502040607090100080300
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit

On 3/30/2016 3:47 PM, Kim Davies wrote:
> Hi Alexey, Hi all,
>
> On 3/24/16, 10:46 AM, "Lager on behalf of Alexey Melnikov" <lager-bounces@ietf.org on behalf of aamelnikov@fastmail.fm> wrote:
>
>
>
>> In 11.3:
>>
>> I think this section needs a bit of work. Firstly, it might be better to
>> say that Standard Dispositions MUST NOT contain ":" character in order
>> to prevent clashes with private dispositions.
> OK.
>
>> Also, saying that registered values are lowercase ASCII (for example)
>> would be a good idea. If you want to only allow ASCII, but not to limit
>> values to lowercase letters, then you need to say whether values in the
>> registry are case-sensitive or not.
> I imagine this observation can be made more generally across the specification.
> I can make this change but wonder if the case-sensitivity needs to
> be explicit in other aspects of the specification for the same reason?

We have the following  names / id's in the spec:

language (*) - rfc5646
scope (*)
reference id
tag value
variant type
class name
rule name
property name(*) - uax42
disposition (*)

The ones marked with a * are externally visible. For some, we are 
referencing an external specification which settles the issue (noted 
following the "-"). For scope, we are specifying that type="domain" 
contains a domain name, so casing rules for domain names apply. For 
other uses we require an IETF spec or a different namespace, all casing 
rules would thus be external.

While we recommend the use of integers as reference IDs, we allow 
uppercase letters, but not lowercase ones.

For the other internally visible id values, such as tag, variant type, 
class and rule names, the simplest thing would be to make them case 
sensitive. (Especially for tag values, some mixed-case use has become 
the norm for the root zone LGR project, for example.) There's no benefit 
of allowing case-insensitive matching.

Changes needed:
5.3.2 "containing spaces. This value is" --> "containing spaces. This 
value is case-sensitive and is".
6.2.1 "single, identifier" --> "single, case-sensitive identifier"
6.2.2. "space separated tag values" --> "space separated and 
case-sensitive tag values"
6.3.4 "a unique "name" attribute, and all" --> "a "name" attribute 
containing a single case-sensitive identifier not containing spaces. 
Names for rules must be unique. All"

Leaves the disposition values. These are not used internal to the spec, 
but are the output values. For the IETF defined ones, I think we intend 
to use the exact strings (case sensitive), and for externally supplied 
ones, again that is up to anyone registering values.

A./
>
>>> Private Dispositions - This registry shall list dispositions that
>>> have been registered on a first-come first-served basis by third parties
>>> with the IANA. Such dispositions must take the form "entity:disposition"
>>> where the entity is a prefix that uniquely identifies the private user
>>> of the namespace. For example, "acme:reserved" could be a private extension
>>> used by the organization ACME to denote a disposition relating to reserved
>>> labels.
>> I think "entity" should be better specified. Which characters are
>> allowed? I would recommend either use domain names to describe ownerhip
>> (I can suggest some text) or use values from the PEN IANA registry
>> <https://www.iana.org/assignments/enterprise-numbers/enterprise-numbers>?
> Given it sounds like you have a clear concept in your mind, I would appreciate
> suggested text on how to use domain names or PENs to namespace the private
> dispositions. A domain name based approach may be the simplest option here
> given that PENs may be an unfamiliar concept to typical authors of these tables,
> and are not used elsewhere in the document.
>
> kim
>
>
> _______________________________________________
> Lager mailing list
> Lager@ietf.org
> https://www.ietf.org/mailman/listinfo/lager


--------------080502040607090100080300
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta content="text/html; charset=utf-8" http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <div class="moz-cite-prefix">On 3/30/2016 3:47 PM, Kim Davies wrote:<br>
    </div>
    <blockquote
      cite="mid:D1EC5ECF-CBA6-4D02-A202-77D41DAD3A9A@icann.org"
      type="cite">
      <pre wrap="">Hi Alexey, Hi all,

On 3/24/16, 10:46 AM, "Lager on behalf of Alexey Melnikov" <a class="moz-txt-link-rfc2396E" href="mailto:lager-bounces@ietf.orgonbehalfofaamelnikov@fastmail.fm">&lt;lager-bounces@ietf.org on behalf of aamelnikov@fastmail.fm&gt;</a> wrote:



</pre>
      <blockquote type="cite">
        <pre wrap="">In 11.3:

I think this section needs a bit of work. Firstly, it might be better to
say that Standard Dispositions MUST NOT contain ":" character in order
to prevent clashes with private dispositions.
</pre>
      </blockquote>
      <pre wrap="">
OK.

</pre>
      <blockquote type="cite">
        <pre wrap="">Also, saying that registered values are lowercase ASCII (for example)
would be a good idea. If you want to only allow ASCII, but not to limit
values to lowercase letters, then you need to say whether values in the
registry are case-sensitive or not.
</pre>
      </blockquote>
      <pre wrap="">
I imagine this observation can be made more generally across the specification.
I can make this change but wonder if the case-sensitivity needs to
be explicit in other aspects of the specification for the same reason?</pre>
    </blockquote>
    <br>
    We have the following  names / id's in the spec:<br>
    <br>
    language (*) - rfc5646<br>
    scope (*)<br>
    reference id<br>
    tag value<br>
    variant type<br>
    class name<br>
    rule name<br>
    property name(*) - uax42<br>
    disposition (*)<br>
    <br>
    The ones marked with a * are externally visible. For some, we are
    referencing an external specification which settles the issue (noted
    following the "-"). For scope, we are specifying that type="domain"
    contains a domain name, so casing rules for domain names apply. For
    other uses we require an IETF spec or a different namespace, all
    casing rules would thus be external.<br>
    <br>
    While we recommend the use of integers as reference IDs, we allow
    uppercase letters, but not lowercase ones. <br>
    <br>
    For the other internally visible id values, such as tag, variant
    type, class and rule names, the simplest thing would be to make them
    case sensitive. (Especially for tag values, some mixed-case use has
    become the norm for the root zone LGR project, for example.) There's
    no benefit of allowing case-insensitive matching.<br>
    <br>
    Changes needed: <br>
    5.3.2 "containing spaces. This value is" --&gt; "containing spaces.
    This value is case-sensitive and is".<br>
    6.2.1 "single, identifier" --&gt; "single, case-sensitive
    identifier"<br>
    6.2.2. <font face="Candara">"space separated tag values" --&gt; "space
      separated and case-sensitive tag values"<br>
      6.3.4 "a unique "name" attribute, and all" --&gt; "a "name"
      attribute containing a single case-sensitive identifier not
      containing spaces. Names for rules must be unique. All"<br>
      <br>
    </font>Leaves the disposition values. These are not used internal to
    the spec, but are the output values. For the IETF defined ones, I
    think we intend to use the exact strings (case sensitive), and for
    externally supplied ones, again that is up to anyone registering
    values.<br>
    <br>
    A./<br>
    <blockquote
      cite="mid:D1EC5ECF-CBA6-4D02-A202-77D41DAD3A9A@icann.org"
      type="cite">
      <pre wrap="">

</pre>
      <blockquote type="cite">
        <blockquote type="cite">
          <pre wrap="">Private Dispositions - This registry shall list dispositions that
have been registered on a first-come first-served basis by third parties
with the IANA. Such dispositions must take the form "entity:disposition"
where the entity is a prefix that uniquely identifies the private user
of the namespace. For example, "acme:reserved" could be a private extension
used by the organization ACME to denote a disposition relating to reserved
labels.
</pre>
        </blockquote>
        <pre wrap="">
I think "entity" should be better specified. Which characters are
allowed? I would recommend either use domain names to describe ownerhip
(I can suggest some text) or use values from the PEN IANA registry
<a class="moz-txt-link-rfc2396E" href="https://www.iana.org/assignments/enterprise-numbers/enterprise-numbers">&lt;https://www.iana.org/assignments/enterprise-numbers/enterprise-numbers&gt;</a>?
</pre>
      </blockquote>
      <pre wrap="">
Given it sounds like you have a clear concept in your mind, I would appreciate
suggested text on how to use domain names or PENs to namespace the private
dispositions. A domain name based approach may be the simplest option here
given that PENs may be an unfamiliar concept to typical authors of these tables,
and are not used elsewhere in the document.

kim</pre>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap="">_______________________________________________
Lager mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Lager@ietf.org">Lager@ietf.org</a>
<a class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/lager">https://www.ietf.org/mailman/listinfo/lager</a>
</pre>
    </blockquote>
    <br>
  </body>
</html>

--------------080502040607090100080300--


From nobody Thu Mar 31 01:56:56 2016
Return-Path: <aamelnikov@fastmail.fm>
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 059DD12D098 for <lager@ietfa.amsl.com>; Thu, 31 Mar 2016 01:56:55 -0700 (PDT)
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, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=fastmail.fm header.b=JecFLLUs; dkim=pass (1024-bit key) header.d=messagingengine.com header.b=VhqMOhOM
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 4FYEeXetOan6 for <lager@ietfa.amsl.com>; Thu, 31 Mar 2016 01:56:53 -0700 (PDT)
Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EEDBC12D0F2 for <lager@ietf.org>; Thu, 31 Mar 2016 01:56:52 -0700 (PDT)
Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id 4E69C224BE for <lager@ietf.org>; Thu, 31 Mar 2016 04:56:52 -0400 (EDT)
Received: from frontend2 ([10.202.2.161]) by compute4.internal (MEProxy); Thu, 31 Mar 2016 04:56:52 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=fastmail.fm; h=cc :content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-sasl-enc :x-sasl-enc; s=mesmtp; bh=TEdG94GPonsfQp93qfjG2jRu2l8=; b=JecFLL UsIlc/cgaguk6cmEIIJNJjwy5wBhR1Pq3aih+CbTxuxGMiDisKXsAFk1JmzcyLNM V2zsUmDOwQEdAJNN+rgDPp7tXxlIHdNNn3zJOLPtlBbDFxKAckOPdCDac4mIRvpd FVDzzfb7g6QMZy+ovIATCu3cyZfTqM+FCmMto=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-sasl-enc:x-sasl-enc; s=smtpout; bh=TEdG94GPonsfQp9 3qfjG2jRu2l8=; b=VhqMOhOM3DNjutRC3r20OtuL/6+rLDEw0MEOB1eNocW/IgG /Q0QsvLNXaMxIGw4c4Tcn/qcGQza8uuCbBlCuZmqCT8cGpz0IaCwXJuqN3BoYShT qTQ46s8HXGAtev+0RwHKF75+/ADyL2sEIVwW+REWCRJBV8qnrD6KyAy8OgWA=
X-Sasl-enc: perwRAQPTyOmbWkoz93qq45Zum7WF8l8WXQ8xLyXEjhB 1459414611
Received: from [10.235.57.94] (unknown [212.183.128.238]) by mail.messagingengine.com (Postfix) with ESMTPA id E3AF9680137; Thu, 31 Mar 2016 04:56:51 -0400 (EDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (1.0)
From: Alexey Melnikov <aamelnikov@fastmail.fm>
X-Mailer: iPhone Mail (13D15)
In-Reply-To: <56FC9C52.2090501@ix.netcom.com>
Date: Thu, 31 Mar 2016 09:59:40 +0100
Content-Transfer-Encoding: 7bit
Message-Id: <B333A477-C672-40AD-9DEC-CFE6D683633E@fastmail.fm>
References: <1458841579.4011697.558814722.09946B62@webmail.messagingengine.com> <D1EC5ECF-CBA6-4D02-A202-77D41DAD3A9A@icann.org> <56FC9C52.2090501@ix.netcom.com>
To: "Asmus Freytag (c)" <asmusf@ix.netcom.com>
Archived-At: <http://mailarchive.ietf.org/arch/msg/lager/I6wbMMfs8E5ZVrSVidOrXpdTUuE>
Cc: lager@ietf.org
Subject: Re: [Lager] Incoming AD review on draft-ietf-lager-specification-11.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, 31 Mar 2016 08:56:55 -0000

Your proposal looks reasonable to me.


From nobody Thu Mar 31 01:58:54 2016
Return-Path: <aamelnikov@fastmail.fm>
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 CA57612D0F2 for <lager@ietfa.amsl.com>; Thu, 31 Mar 2016 01:58:52 -0700 (PDT)
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, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=fastmail.fm header.b=VuO+Ewa5; dkim=pass (1024-bit key) header.d=messagingengine.com header.b=B1E4xF1B
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 DXsdvA33Pxb6 for <lager@ietfa.amsl.com>; Thu, 31 Mar 2016 01:58:51 -0700 (PDT)
Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E14C212D098 for <lager@ietf.org>; Thu, 31 Mar 2016 01:58:50 -0700 (PDT)
Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailout.nyi.internal (Postfix) with ESMTP id 503F921FF2 for <lager@ietf.org>; Thu, 31 Mar 2016 04:58:50 -0400 (EDT)
Received: from frontend2 ([10.202.2.161]) by compute5.internal (MEProxy); Thu, 31 Mar 2016 04:58:50 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=fastmail.fm; h=cc :content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-sasl-enc :x-sasl-enc; s=mesmtp; bh=hMJjx018pswLwj9ZQ5F+ghBd034=; b=VuO+Ew a5525IfeHuwHMzxU8CcYoR3YC5cmhnjWpxoHFO8Mp4R/fvpaee3Tjsqi8Tgx5HH9 RI/euEOjaEQE8GWktPXmOHJTl5pEd1335sLTuLBh1StUGTM0kdWX5LBIAJMX81D5 RXwIy4Hj95Ad4BENSyqhZ4SPBrHavbZ9vMwE0=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-sasl-enc:x-sasl-enc; s=smtpout; bh=hMJjx018pswLwj9 ZQ5F+ghBd034=; b=B1E4xF1BnivVxzKGuSUTv6cvzDOzpTcCsALDSpTaj/dzDsT KBNDQ4eKCjA7gYlagGh6QSUe/MhIGXK4f4EeOIYtzYWrVbYu3wsflpoJhjOa8/mY 5cD/yynNcxF1aU41XRbRRzql3yNZyC6Mn694h/YrjG4BBUbptXiBW3r3S4UA=
X-Sasl-enc: L/NRuXBpUBg2tfQf1W1Tn8XNdbJ36bRuisQg8EGUh+zn 1459414729
Received: from [10.235.57.94] (unknown [212.183.128.238]) by mail.messagingengine.com (Postfix) with ESMTPA id B5BF6680128; Thu, 31 Mar 2016 04:58:49 -0400 (EDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (1.0)
From: Alexey Melnikov <aamelnikov@fastmail.fm>
X-Mailer: iPhone Mail (13D15)
In-Reply-To: <D1EC5ECF-CBA6-4D02-A202-77D41DAD3A9A@icann.org>
Date: Thu, 31 Mar 2016 10:01:30 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <DC0A9163-4746-4E67-BC8E-C6BFC317714D@fastmail.fm>
References: <1458841579.4011697.558814722.09946B62@webmail.messagingengine.com> <D1EC5ECF-CBA6-4D02-A202-77D41DAD3A9A@icann.org>
To: Kim Davies <kim.davies@icann.org>
Archived-At: <http://mailarchive.ietf.org/arch/msg/lager/yf4tTrYnx23p-cG5M51lf9q4sBA>
Cc: "lager@ietf.org" <lager@ietf.org>
Subject: Re: [Lager] Incoming AD review on draft-ietf-lager-specification-11.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, 31 Mar 2016 08:58:53 -0000

Hi Kim,

> On 30 Mar 2016, at 23:47, Kim Davies <kim.davies@icann.org> wrote:
>=20
> Hi Alexey, Hi all,
>=20
> On 3/24/16, 10:46 AM, "Lager on behalf of Alexey Melnikov" <lager-bounces@=
ietf.org on behalf of aamelnikov@fastmail.fm> wrote:
>=20
>>=20
>> In Section 4.3.5
>>=20
>> The first mention of "media type" needs a normative reference to RFC
>> 2045. This would save developers time with trying to find out what
>> syntax to support and where to find registered media types.
>=20
> OK, will add.
>=20
>> In 11.3:
>>=20
>> I think this section needs a bit of work. Firstly, it might be better to
>> say that Standard Dispositions MUST NOT contain ":" character in order
>> to prevent clashes with private dispositions.
>=20
> OK.
>=20
>> Also, saying that registered values are lowercase ASCII (for example)
>> would be a good idea. If you want to only allow ASCII, but not to limit
>> values to lowercase letters, then you need to say whether values in the
>> registry are case-sensitive or not.
>=20
> I imagine this observation can be made more generally across the specifica=
tion.
> I can make this change but wonder if the case-sensitivity needs to
> be explicit in other aspects of the specification for the same reason?

Yes, reviewing this generally in sensible.
>=20
>>> Private Dispositions - This registry shall list dispositions that
>>> have been registered on a first-come first-served basis by third parties=

>>> with the IANA. Such dispositions must take the form "entity:disposition"=

>>> where the entity is a prefix that uniquely identifies the private user
>>> of the namespace. For example, "acme:reserved" could be a private extens=
ion
>>> used by the organization ACME to denote a disposition relating to reserv=
ed
>>> labels.
>>=20
>> I think "entity" should be better specified. Which characters are
>> allowed? I would recommend either use domain names to describe ownerhip
>> (I can suggest some text) or use values from the PEN IANA registry
>> <https://www.iana.org/assignments/enterprise-numbers/enterprise-numbers>?=

>=20
> Given it sounds like you have a clear concept in your mind, I would apprec=
iate
> suggested text on how to use domain names or PENs to namespace the private=

> dispositions. A domain name based approach may be the simplest option here=

> given that PENs may be an unfamiliar concept to typical authors of these t=
ables,
> and are not used elsewhere in the document.

I think I would go with Marc's suggestion to use domain names.

