[gnso-irtpd] Happy new year and Š Monday's agenda

[Lars Hoffmann <lars.hoffmann@xxxxxxxxx>]

Dear all,

First, let me wish you a very happy, healthy and successful 2014! I hope you 
were able to wind down during the holiday period and had the chance to recharge 
those batteries for the challenges ahead.

Speaking of … Please find below the agenda for Monday's IRTP Part D PDP WG 
meeting.

Many thanks and see you all on Monday!
Best wishes,
Lars


Proposed Agenda

IRTP Part D PDP Working Group Meeting, 6 January 2014, 16.00 UTC, for local 
times see http://tinyurl.com/oo2gmtv

1. Roll Call / SOI Updates

2. Discussion on circulated view of ICANN Compliance  on TDRP (see below)

3. If time: Revisit Work Plan

4. Next steps / confirm next meeting


----

>From an ICANN Compliance point of view
Scenarios (under IRTP as it stands) in which ICANN Compliance has the authority 
to act:

Regarding the loosing registrar:

Auth-code related:
- the registrant was not able to retrieve the auth code from the control panel, 
then the registrant requested the registrar to send it but it was not sent 
within the required 5 days ----- (the breach in this case is when both 
conditions are present)
- the means provided by the registrar for the registrant to retrieve the auth 
code are more restrictive than the means provided for the registrant to update 
its contact or name server information
- the registrar sends the Auth Code to someone  who is not the registered name 
holder
- the registrar does not even send it at all

FOA related:
- the registrar does not send the FOA
- sends it to someone who is not a Transfer Contact

Unlocking of the domain name:
- the registrant did not have the means provided by the registrar to unlock the 
domain name, then the registrant requested the registrar to unlock the domains 
and the registrar did not unlock them within the five days ----- (the breach in 
this case is when both conditions are present)

Regarding the gaining registrar:

Auth-code related:
- the registrar allows the transfer without receiving the Auth-code - which 
would be technically impossible but can theoretically happen (in a scenario 
also involving registry error)

FOA related:
- the registrar does not send the FOA
- the registrar sends the FOA to someone who is not a Transfer Contact
- the registrar allows the transfer without receiving confirmation after 
sending the FOA