<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<font face="Candara">All,<br>
<br>
Following up on issues raised in the CJK meeting in London today.<br>
<br>
XML format and RFC 3743.<br>
<br>
The XML format should allow to express some policies that are
going beyond the root policies that are assumed in the
"Procedure". Therefore, the format should be able to capture the
full RFC 3743.<br>
<br>
I would appreciate if someone knowledgeable in RFC 3743 could look
over the latest spec as well as the "Variant Rules" document in
the LGR project wiki to let me know if there are any limitations
of the XML format.<br>
<br>
Variant Rules<br>
<a class="moz-txt-link-freetext" href="https://community.icann.org/download/attachments/43989034/Variant%20Rules.pdf?version=1&modificationDate=1396991883000&api=v2">https://community.icann.org/download/attachments/43989034/Variant%20Rules.pdf?version=1&modificationDate=1396991883000&api=v2</a><br>
<br>
Latest XML spec:<br>
<a class="moz-txt-link-freetext" href="http://tools.ietf.org/html/draft-davies-idntables-07">http://tools.ietf.org/html/draft-davies-idntables-07</a><br>
<br>
A separate issue related to the question of possible
inconsistencies between 2nd level and root. The root is a shared
resource, which leads to some constraints not relevant for the
second level. Such constraints might be called "necessary". What I
would be interested in is examples (even hypothetical/imaginary
ones) of "unnecessary" or "random" differences between the levels.<br>
<br>
A./<br>
</font>
</body>
</html>