Re: [Lager] Remaining Work Items

Kim Davies <kim.davies@icann.org> Mon, 04 January 2016 22:29 UTC

Return-Path: <kim.davies@icann.org>
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 D58941AC427 for <lager@ietfa.amsl.com>; Mon, 4 Jan 2016 14:29:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.532
X-Spam-Level:
X-Spam-Status: No, score=-1.532 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_NEUTRAL=0.779, T_RP_MATCHES_RCVD=-0.01] 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 IaXGgI9ut3Pc for <lager@ietfa.amsl.com>; Mon, 4 Jan 2016 14:29:10 -0800 (PST)
Received: from out.west.pexch112.icann.org (pfe112-ca-2.pexch112.icann.org [64.78.40.10]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3AB201A1A7B for <lager@ietf.org>; Mon, 4 Jan 2016 14:29:10 -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.1044.25; Mon, 4 Jan 2016 14:29:08 -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.1044.021; Mon, 4 Jan 2016 14:29:08 -0800
From: Kim Davies <kim.davies@icann.org>
To: "Hollenbeck, Scott" <shollenbeck@verisign.com>
Thread-Topic: [Lager] Remaining Work Items
Thread-Index: AdFG9pU7vXrWFZSdT+O8QYqozk+afgAi8qiA
Date: Mon, 04 Jan 2016 22:29:06 +0000
Message-ID: <7E5B4D89-249D-43FE-A0DF-D9EB42DB3EFF@icann.org>
References: <831693C2CDA2E849A7D7A712B24E257F4A123C6D@BRN1WNEXMBX01.vcorp.ad.vrsn.com>
In-Reply-To: <831693C2CDA2E849A7D7A712B24E257F4A123C6D@BRN1WNEXMBX01.vcorp.ad.vrsn.com>
Accept-Language: en-AU, en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [192.0.35.2]
Content-Type: multipart/signed; boundary="Apple-Mail=_9B5D8549-ED4D-4FF2-BBC8-E8F9387221C8"; protocol="application/pkcs7-signature"; micalg="sha1"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/lager/hRVFkda9GKFTYeBcmK2Ge9OdvoA>
Cc: "lager WG (lager@ietf.org)" <lager@ietf.org>
Subject: Re: [Lager] Remaining Work Items
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, 04 Jan 2016 22:29:12 -0000

Hi Scott, Hi all,

> We have three issues open in the datatracker:
> 
> https://trac.tools.ietf.org/wg/lager/trac/report/1
> 
> These all look to be relatively simple to address, so let's get them done ASAP. Document authors, is there anything holding you up?

For ticket 21, the only outstanding issue is who should be the Change Controller in section 10.1, which is the media type registration form. One interpretation of RFC 7303 could be that it should be the World Wide Web Consortium as that stakes out their responsibility given it has a “+xml” suffix. Specifically, section 4.2 reads that when using the suffix, “… the change controller has been changed to be the World Wide Web Consortium (W3C)”. An alternative conclusion would be the change controller should be the IESG given this is a Standards Track document. The latter seems more logical to me given the W3C has had no role in this specification, but I am not sure what the purpose of the language in RFC 7303 is intending to serve. Hopefully there is someone we can consult with to seek clarification on this item, but that is the issue at hand.

For ticket 29, Asmus has proposed changing some references to the Unicode specification to remove multiple different ways Unicode properties could be expressed, to have a single canonical long- and short-form way of representing them. I think this is a good idea and Wil seems to have concurred. It needs some new text to be put in the next edition.

For ticket 30, Asmus posted about this to the list just prior to the holiday break. I am not sure I’ve wrapped my head around the pros and cons of adding “valid” as an additional core disposition. I think it would be good to have some discussion about this on the list before making a call on it.

I think that’s it. With some additional feedback and a little work hopefully we can turn around a new draft with no known issues in the coming days.

kim