[IRT.RegDataPolicy] IRT Liaison report on Rec7 during the 20Aug2020 GNSO Council Meeting

[Rubens Kuhl]

> On 13 Sep 2020, at 17:45, Alex Deacon <alex at colevalleyconsulting.com> wrote:
> 
> 
> Hi Rubens,
> 
> OK, but clearly policy that includes mandatory obligations on CPs that are enforceable by ICANN Compliance plus a procedure for handling conflicts is very different from a policy that gives the CP the discretion to do something with no review/input from ICANN.   If contractual obligations are voluntary we don't need ICANN at all.
> 
> Also, if the choice of OneDoc language results in a situation where the conflict procedure is no longer required or relevant, we are right back where we were.  e.g. The IRT language is amending policy recommendations adopted by the GNSO Council and the ICANN Board - and we don't have the power to do that.

Alex,

What you try referring as IRT amending policy would actually be IRT trying to follow policy adopted by GNSO Council and ICANN Board, the EPDP Phase 1 policy. It's curious you try arguing it as not amending policy when it's exactly what's being tried.




Rubens


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/irt.regdatapolicy/attachments/20200913/aaa6b188/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 529 bytes
Desc: Message signed with OpenPGP
URL: <http://mm.icann.org/pipermail/irt.regdatapolicy/attachments/20200913/aaa6b188/signature.asc>