<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;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.EmailStyle18
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle19
{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="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoNormal">I have a more nuanced view; our analysis and views can be independent that of IP’s so long they don’t conflict with the LGR Procedure. IMHO, we have crossed that line in some proposed cases and IP is making this observation.<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">Latingp <latingp-bounces@icann.org> on behalf of Mirjana Tasić <Mirjana.Tasic@rnids.rs><br>
<b>Date: </b>Thursday, October 31, 2019 at 5:53 AM<br>
<b>To: </b>Meikal Mumin <meikal@mumin.de>, "latingp@icann.org" <latingp@icann.org>, Michael Bauland <Michael.Bauland@knipp.de><br>
<b>Subject: </b>[EXTERNAL] Re: [Latingp] Missing In-Script Cases<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><o:p> </o:p></p>
</div>
<p class="MsoNormal" style="margin-left:.5in"><span style="mso-fareast-language:EN-US">Dear Colleagues,</span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="mso-fareast-language:EN-US"> </span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="mso-fareast-language:EN-US">I agree with Meikal’s view. First item of our agenda for the next telephone call will be discussion about IP’s paper and our conversation with them during ICANN66.</span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="mso-fareast-language:EN-US"> </span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="mso-fareast-language:EN-US">Regards Mirjana</span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="mso-fareast-language:EN-US"> </span><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">Latin GP <latingp-bounces@icann.org> on behalf of Meikal Mumin <meikal@mumin.de><br>
<b>Date: </b>Wednesday, 30 October 2019 at 18:00<br>
<b>To: </b>Latin GP <latingp@icann.org>, Michael Bauland <Michael.Bauland@knipp.de><br>
<b>Subject: </b>Re: [Latingp] Missing In-Script Cases</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"> <o:p></o:p></p>
</div>
<div name="messageBodySection">
<div>
<p class="MsoNormal" style="margin-left:.5in">Dear colleagues, <o:p></o:p></p>
<div>
<p class="MsoNormal" style="margin-left:.5in"> <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">I don’t see any issue in putting this on-hold until after having a meeting with IP, but I also believe that IP has misunderstood some of the analysis based on a quick look at their response, and our analysis and
views should be independent of IPs.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"> <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">So even if we hold this off for now, we should continue with a unified and coherent approach to the variant analysis and modify it only where we see a need, instead of arbitrarily omitting individual cases.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"> <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">Let IP judge on the final product featuring all of our own evidence and rationale for each actual variant case instead of speculating and discarding cases without having a clear understanding of the situation. Currently
this simply remains unfinished.<o:p></o:p></p>
</div>
</div>
</div>
<div name="messageSignatureSection">
<p class="MsoNormal" style="margin-left:.5in"> <o:p></o:p></p>
<div>
<p class="MsoNormal" style="margin-left:.5in">Best wishes,<br>
<br>
Meikal<o:p></o:p></p>
</div>
</div>
<div name="messageReplySection">
<p class="MsoNormal" style="margin-left:.5in">Am 30. Okt. 2019, 14:50 +0100 schrieb Michael Bauland <Michael.Bauland@knipp.de>:<br>
<br>
<br>
<o:p></o:p></p>
<blockquote style="border:none;border-left:solid #1ABC9C 1.0pt;padding:0in 0in 0in 8.0pt;margin-left:3.75pt;margin-top:3.75pt;margin-right:3.75pt;margin-bottom:3.75pt">
<p class="MsoNormal" style="margin-left:.5in">Hi all,<br>
<br>
On 30.10.2019 14:37, Tan Tanaka, Dennis via Latingp wrote:<br>
<br>
<br>
<o:p></o:p></p>
<blockquote style="border:none;border-left:solid #E67E22 1.0pt;padding:0in 0in 0in 8.0pt;margin-left:3.75pt;margin-top:3.75pt;margin-right:3.75pt;margin-bottom:3.75pt">
<p class="MsoNormal" style="margin-left:.5in">Should we put this on-hold in light of IP’s preliminary feedback and<br>
pending comments from our meeting with them next week?<o:p></o:p></p>
</blockquote>
<p class="MsoNormal" style="margin-left:.5in"><br>
I agree with Dennis. We should discuss this with IP and then internally<br>
first before continuing.<br>
<br>
See you next week,<br>
<br>
Michael<br>
<br>
--<br>
____________________________________________________________________<br>
| |<br>
| knipp | Knipp Medien und Kommunikation GmbH<br>
------- Technologiepark<br>
Martin-Schmeisser-Weg 9<br>
44227 Dortmund<br>
Germany<br>
<br>
Dipl.-Informatiker Fon: +49 231 9703-0<br>
Fax: +49 231 9703-200<br>
Dr. Michael Bauland SIP: Michael.Bauland@knipp.de<br>
Software Development E-mail: Michael.Bauland@knipp.de<br>
<br>
Register Court:<br>
Amtsgericht Dortmund, HRB 13728<br>
<br>
Chief Executive Officers:<br>
Dietmar Knipp, Elmar Knipp<br>
_______________________________________________<br>
Latingp mailing list<br>
Latingp@icann.org<br>
https://mm.icann.org/mailman/listinfo/latingp<br>
<br>
_______________________________________________<br>
By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (https://www.icann.org/privacy/policy) and the website Terms of Service (https://www.icann.org/privacy/tos).
You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on.<o:p></o:p></p>
</blockquote>
</div>
</div>
</body>
</html>