<div dir="auto"><div><div data-smartmail="gmail_signature">Sent from my mobile<br>Kindly excuse brevity and typos</div><div class="gmail_extra"><br><div class="gmail_quote">On Aug 2, 2017 8:35 AM, "Nigel Roberts" <<a href="mailto:nigel@channelisles.net">nigel@channelisles.net</a>> wrote:<br type="attribution"><blockquote class="quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Seun<br>
<br>
There's a difference between an informal briefing from a lawyer, and a formal, written Opinion.<br></blockquote></div></div></div><div dir="auto"><br></div><div dir="auto">SO: Am clear on that. However does that mean informal briefing can't be written down (with appropriate disclaimer included if necessary)?</div><div dir="auto"><div class="gmail_extra"><div class="gmail_quote"><blockquote class="quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
Informal briefings can, to some extent, skate over the detail and technicalities (though I wouldn't expect them to miss the important points).<br></blockquote></div></div></div><div dir="auto"><br></div><div dir="auto">SO: This is all that I believe is important for now. We should get informal response to all the "unique" questions raised and then look at which of the responses require/warrants more formal response.</div><div dir="auto"><br></div><div dir="auto">Regards</div><div dir="auto"><br></div><div dir="auto"><div class="gmail_extra"><div class="gmail_quote"><blockquote class="quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
A written opinion, however, must be carefully considered, and must be comprehensive. That is to say, many billable hours = costly.<br>
<br>
Now, it really is worth doing this where there is a specific, well drawn "qualified question" to be answered.<br>
<br>
But a widely drawn brief is a recipe for a result that is<br>
<br>
(a) confusing additionally or alternatively confused; and<br>
(b) extremely expensive.<br>
<br>
I'm as keen as Kavouss and Paul to have a briefing on how ICANN-PTI's obligations have changed since transition, both in law (I suspect not at all ) and de facto (which clearly has changed, from changes in the way existing policy is being interpreted).<br>
<br>
But let's have focus.<div class="quoted-text"><br>
<br>
<br>
On 02/08/17 07:10, Seun Ojedeji wrote:<br>
</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="quoted-text">
Hello,<br>
<br>
I was not on the call and have not had to bandwidth to look at the<br>
recordings. If this is about Sam's response to the questions Greg was<br>
asking us to provide.<br>
<br>
Then I think the ideal thing is to document the responses side by side<br>
with the questions.<br>
<br>
A verbal response whether captioned or not should not be applicable<br>
after all the responses must have been documented somewhere before it<br>
was being read out by Sam, so why not just share the document and let's<br>
end this seemingly trivial matter.<br>
<br>
Regards<br>
Sent from my mobile<br>
Kindly excuse brevity and typos<br>
<br>
On Aug 2, 2017 4:45 AM, "avri doria" <<a href="mailto:avri@apc.org" target="_blank">avri@apc.org</a><br></div><div class="quoted-text">
<mailto:<a href="mailto:avri@apc.org" target="_blank">avri@apc.org</a>>> wrote:<br>
<br>
Hi,<br>
<br>
With captioning, don't we already have an equivalent to written answers?<br>
<br>
avri<br>
<br>
<br>
<br>
On 01-Aug-17 15:55, Greg Shatan wrote:<br>
> Kavouss,<br>
><br>
> Kindly direct your request to the Subgroup, and not to Sam. This is a<br>
> matter for the Subgroup to consider, rather than any individual<br>
> participant. The Subgroup can take up your request and decide whether<br>
> to ask for written responses to questions (and if so, which<br>
> questions). Thank you.<br>
><br>
> Best regards,<br>
><br>
> Greg<br>
><br>
> On Tue, Aug 1, 2017 at 10:15 AM, Kavouss Arasteh<br>
> <<a href="mailto:kavouss.arasteh@gmail.com" target="_blank">kavouss.arasteh@gmail.com</a> <mailto:<a href="mailto:kavouss.arasteh@gmail.com" target="_blank">kavouss.arasteh@gmail.<wbr>com</a>><br></div>
<mailto:<a href="mailto:kavouss.arasteh@gmail.com" target="_blank">kavouss.arasteh@gmail.<wbr>com</a><div class="quoted-text"><br>
<mailto:<a href="mailto:kavouss.arasteh@gmail.com" target="_blank">kavouss.arasteh@gmail.<wbr>com</a>>>> wrote:<br>
><br>
> Dear Sam, With tks to your presentation, pls kindly note that I<br>
> nned written answers to the questions raised before the meeting<br>
> and those during the meeing either as intervention or in the chat.<br>
> Regards<br>
> Kavouss<br>
><br>
><br>
><br>
><br>
> ______________________________<wbr>_________________<br>
> Ws2-jurisdiction mailing list<br></div>
> <a href="mailto:Ws2-jurisdiction@icann.org" target="_blank">Ws2-jurisdiction@icann.org</a> <mailto:<a href="mailto:Ws2-jurisdiction@icann.org" target="_blank">Ws2-jurisdiction@icann<wbr>.org</a>><br>
> <a href="https://mm.icann.org/mailman/listinfo/ws2-jurisdiction" rel="noreferrer" target="_blank">https://mm.icann.org/mailman/l<wbr>istinfo/ws2-jurisdiction</a><div class="quoted-text"><br>
<<a href="https://mm.icann.org/mailman/listinfo/ws2-jurisdiction" rel="noreferrer" target="_blank">https://mm.icann.org/mailman/<wbr>listinfo/ws2-jurisdiction</a>><br>
<br>
<br>
---<br>
This email has been checked for viruses by Avast antivirus software.<br></div>
<a href="https://www.avast.com/antivirus" rel="noreferrer" target="_blank">https://www.avast.com/antiviru<wbr>s</a> <<a href="https://www.avast.com/antivirus" rel="noreferrer" target="_blank">https://www.avast.com/antivir<wbr>us</a>><br>
<br>
______________________________<wbr>_________________<br>
Ws2-jurisdiction mailing list<br>
<a href="mailto:Ws2-jurisdiction@icann.org" target="_blank">Ws2-jurisdiction@icann.org</a> <mailto:<a href="mailto:Ws2-jurisdiction@icann.org" target="_blank">Ws2-jurisdiction@icann<wbr>.org</a>><br>
<a href="https://mm.icann.org/mailman/listinfo/ws2-jurisdiction" rel="noreferrer" target="_blank">https://mm.icann.org/mailman/l<wbr>istinfo/ws2-jurisdiction</a><br>
<<a href="https://mm.icann.org/mailman/listinfo/ws2-jurisdiction" rel="noreferrer" target="_blank">https://mm.icann.org/mailman/<wbr>listinfo/ws2-jurisdiction</a>><div class="quoted-text"><br>
<br>
<br>
<br>
______________________________<wbr>_________________<br>
Ws2-jurisdiction mailing list<br>
<a href="mailto:Ws2-jurisdiction@icann.org" target="_blank">Ws2-jurisdiction@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/ws2-jurisdiction" rel="noreferrer" target="_blank">https://mm.icann.org/mailman/l<wbr>istinfo/ws2-jurisdiction</a><br>
<br>
</div></blockquote><div class="elided-text">
______________________________<wbr>_________________<br>
Ws2-jurisdiction mailing list<br>
<a href="mailto:Ws2-jurisdiction@icann.org" target="_blank">Ws2-jurisdiction@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/ws2-jurisdiction" rel="noreferrer" target="_blank">https://mm.icann.org/mailman/l<wbr>istinfo/ws2-jurisdiction</a><br>
</div></blockquote></div><br></div></div></div>