<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:DengXian;
panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:"\@DengXian";
panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0in;
font-size:10.0pt;
font-family:"Courier New";}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:"Consolas",serif;}
span.EmailStyle22
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style>
</head>
<body lang="EN-US" link="blue" vlink="purple" style="word-wrap:break-word;zoom: 0%">
<div class="WordSection1">
<p class="MsoNormal">And this is the question I post to this group. Do we need to always have a label designated as “primary”, and if so, what function will it serve?<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">My current thinking is that the primary label serves its purpose to determine the set of ALL variant labels — allocatable and blocked. Beyond this point the set is established (disposition values are captured), and so, I would argue, a
“primary” label no longer have utility (other than a data point to indicate how the set was formed, and/or potential re-calculation due to rz-lgr changes). Each applied-for/delegated label should have equal standing in the set, IMO. But perhaps I am missing
something.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Dennis<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal" style="margin-left:.5in"><b><span style="font-size:12.0pt;color:black">From:
</span></b><span style="font-size:12.0pt;color:black">Gnso-epdp-idn-team <gnso-epdp-idn-team-bounces@icann.org> on behalf of Maxim Alzoba <m.alzoba@gmail.com><br>
<b>Date: </b>Tuesday, July 26, 2022 at 3:54 AM<br>
<b>To: </b>Michael Bauland <Michael.Bauland@knipp.de><br>
<b>Cc: </b>"gnso-epdp-idn-team@icann.org" <gnso-epdp-idn-team@icann.org><br>
<b>Subject: </b>[EXTERNAL] Re: [Gnso-epdp-idn-team] primary labels and consequences of retiring them<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><o:p> </o:p></p>
</div>
<table class="MsoNormalTable" border="0" cellpadding="0" width="1185" style="width:888.75pt;margin-left:.5in;background:#F5ECCE">
<tbody>
<tr>
<td width="1181" style="width:885.75pt;padding:.75pt .75pt .75pt .75pt">
<p><strong><span style="font-family:"Calibri",sans-serif;color:#993300">Caution:</span></strong><span style="color:#993300"> </span><span style="color:black">This email originated from outside the organization. Do not click links or open attachments unless
you recognize the sender and know the content is safe. </span><o:p></o:p></p>
</td>
</tr>
</tbody>
</table>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:12.0pt;margin-left:.5in">
I think the procedure of the retirement needs to have a check for the existence of the primary and if not - election of the new one.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">Maxim Alzoba<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">On Jul 26, 2022, at 09:42, Michael Bauland <<a href="mailto:michael.bauland@knipp.de" target="_blank">michael.bauland@knipp.de</a>> wrote:
<o:p></o:p></p>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in">
<pre style="margin-left:.5in">Hi Dennis,<br><br>On 25.07.2022 21:46, Tan Tanaka, Dennis via Gnso-epdp-idn-team wrote:<o:p></o:p></pre>
<blockquote style="border:none;border-left:solid #729FCF 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in;margin-bottom:6.0pt">
<pre style="margin-left:.5in"> A few additional comments on 2.3 re: use of “primary label”<br> <br> * Some questions I reckon we will face throughout: what is the<br> “primary” label? what function does it serve? should we use such<br> nomenclature? … some background notes:<br> * When we talk about variants in a set, it is important to note which<br> of all labels is the source for variant label calculation, or as we<br> have adopted: the primary label. As a way of context, first, the<br> variant relationship between two code points must satisfy the<br> symmetrical property (there are other properties, but not relevant<br> to this topic). This means, if ‘A’ is a variant of ‘B’, then ‘B’ is<br> a variant of ‘A’. Second, any variant relationship is also assigned<br> a disposition value: allocatable or blocked. The disposition value<br> is unidirectional. Which means, a variant relationship could yield<br> an ‘allocatable’ variant in one direction (e.g., AàB: allocatable),<br> but a ‘blocked’ variant in the other direction (e.g., BàA: blocked).<br> These rules are encoded in the LGR.<br> * As we progress in our deliberations about the lifecycle of gTLDs it<br> is important to understand (and remember) how the various variant<br> labels and disposition values came to be (to discern which ones are<br> allocatable/withheld or blocked). However, I believe we need to<br> remain open (or at least give thoughtful consideration) to cases<br> where one TLD label in the set needs to be handled separately e.g.,<br> retirement, and the implications of this one change applies to the<br> rest of the labels in the set. For instance, what if the registry<br> operator wants to retire the “primary” label and continue to operate<br> the rest of variants. In this case, it would be unwise, perhaps, to<br> re-assign the attribute of “primary” to another label in the set,<br> because that might change the profile of the set as a whole (of<br> course, this would depend what “primary” means and how it is used).<o:p></o:p></pre>
</blockquote>
<pre style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:12.0pt;margin-left:.5in"><br>This is a very good point. Especially with asymmetric disposition we <br>have a real problem if a primary label is retired and the other variants <br>are kept. There might arise a situation in which none of the remaining <br>variants can be made primary, because it would entail one of the other <br>existing variants to become blocked instead of allocatable.<br><br>The question would then be<br>* Do we allow a variant set to exist without a primary label?<br>* Will retiring a primary label require the registry to select another <br>primary label and thereby possibly force them to retire other variants <br>together with the former primary label?<br><br>Take the following quite simple example.<br>Applied for primary label: bıß<br>Allocatable Variants: biß, bıss, biss<br><br>So, someone might have all four labels in the Root zone at some point.<br><br>If they now retire the primary label bıß, the other three labels could <br>not exist at the time (without bıß also existing).<br><br>Case 1:<br>biß is made new primary<br>Consequence: bıss becomes a blocked variant.<br><br>Case 2:<br>bıss is made new primary<br>Consequence: biß becomes a blocked variant.<br><br>Case 3:<br>biss is made a new primary<br>Consequence: both bıss and biß become blocked variants.<br><br><br>Even though the example is not very likely, it's certainly possible and <br>in other scripts might be similar examples that are more likely.<br><br><br>So, to summarise my points:<br>* Initially, we need a primary label to determine the disposition value <br>of all variants.<br>* Retiring a primary label may cause problems and we need to decide how <br>to deal with these problems.<br><br>Best regards,<br><br>Michael<o:p></o:p></pre>
</blockquote>
</div>
</div>
</body>
</html>