<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-family: Calibri, sans-serif;">
<div>
<div>
<div>FYI</div>
</div>
</div>
<div><br>
</div>
<span id="OLK_SRC_BODY_SECTION">
<div>
<div>On 7/18/15, 8:31 AM, "Marc Blanchet" <<a href="mailto:marc.blanchet@viagenie.ca">marc.blanchet@viagenie.ca</a>> wrote:</div>
</div>
<div><br>
</div>
<blockquote id="MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style="BORDER-LEFT: #b5c4df 5 solid; PADDING:0 0 0 5; MARGIN:0 0 0 5;">
<div>
<div>
<div class="markdown">
<p dir="auto">Hello,<br>
a new IETF working group has been formed recently, named: lager (Label Generation Rules). Charter listed below FYI. This work has impact to any software that checks if domains (especially tlds and 2nd level) are valid for a registry, for various use cases:
registration, domain check, etc… Valid not in the IDNA2008 sense, but the « file format » defines the restricted set of code points and related rules (variants for example) accepted by a registry.</p>
<p dir="auto">since the wg was formed after the deadline to submit meeting requests for Prague, we do not have a formal meeting session. But Scott and I, co-chairs, would like to arrange some informal talks (Scott company will pay the lager…) to start the work.
</p>
<p dir="auto">Could anyone interested in attending that informal meeting send me+scott an email so we can doodle a meeting time during the Prague IETF week.</p>
<p dir="auto">Regards, Marc.</p>
<h1>Lager Charter ( <a href="http://datatracker.ietf.org/wg/lager/charter/">http://datatracker.ietf.org/wg/lager/charter/</a>)</h1>
<p dir="auto">Domain registries, particularly those implementing IDNA (RFC 5890 <br>
et.al), usually maintain a set of criteria (or "ruleset") that governs <br>
permissible labels allowed for registration, such as [IANAIDNTABLES]. <br>
These rulesets are commonly a mixture of eligible code points along <br>
with contextual criteria that must be met concerning the positioning of <br>
certain code points. Some registries also specify rules regarding <br>
variant labels and how they are to be handled. Domain registries <br>
commonly need to share these rules, but there is no interoperable format <br>
that can be used that can support many common use cases. This group <br>
seeks to produce such a format, which will enable re-use and sharing of<br>
existing rulesets, and simpler implementation of new rulesets in registries.</p>
<p dir="auto">A comprehensive format specification has been developed, named Label<br>
Generation Rules, primarily to support the rules to be used for the <br>
DNS Root Zone [Davies]. This group will use this specification as a <br>
starting point to develop a common XML language that provides a superset <br>
of functionality of current specifications<br>
[RFC 3743, RFC 4290, et.al], along with other known use cases. This <br>
single format is expected to supersede existing formats, and form the <br>
basis for future rulesets used at different levels of the DNS hierarchy.</p>
<p dir="auto">Work items:<br>
- Standard Track Specification of the Label Generation Rules</p>
<p dir="auto">References:<br>
[Davies] <a href="https://datatracker.ietf.org/doc/draft-davies-idntables/">https://datatracker.ietf.org/doc/draft-davies-idntables/</a><br>
[IANAIDNTABLES] <a href="https://www.iana.org/domains/idn-tables">https://www.iana.org/domains/idn-tables</a></p>
</div>
</div>
</div>
</blockquote>
</span>
</body>
</html>