[APRALO-Policy] Call for Comments to Preliminary Issue Report on a Policy Development Process to Review the Transfer Policy (12 Oct - 30 Nov 2020)

Tue Nov 10 04:59:51 UTC 2020

All,

This Call for Comments to Preliminary Issue Report on a Policy Development
Process to Review the Transfer Policy has last week been identified as
something for CPWG to consider - I had hoped that pre-empting this through
the APRALO Policy Forum might have given our members here a little head
start in understanding the issues raised in the accompanying public comment
documentation.

At this juncture, you are welcomed to continue using this Googledoc
<https://docs.google.com/document/d/16gXn8QWJge_9ktpetiJ1Tfafvk2KhhGkfJe9tN1_L3k/edit?usp=sharing>
to
post comments, *or if you prefer, you can raise your comments directly
through the CPWG mail list or CPWG weekly calls*.

Kind regards,
Justine

*APRALO Policy Forum
<https://community.icann.org/display/APRALO/APRALO+Policy+Forum>*

On Tue, 3 Nov 2020 at 17:53, Justine Chew <justine.chew.icann at gmail.com>
wrote:

> Hi Holly,
>
> Is there ever an easy topic for people to get their head around? :)
>
> But sure, any diagram or information you believe will help bring clarity
> to the issues raised for comments is most welcomed. I think much of the
> information is presented already, except that they are all in text form.
>
> The APRALO Policy Forum is meant to be a regional list that considers if
> there's anything of significance to raise at CPWG.
>
> Kind regards,
> Justine
>
> *APRALO Policy Forum
> <https://community.icann.org/display/APRALO/APRALO+Policy+Forum>*
>
>
> On Tue, 3 Nov 2020 at 17:33, Holly Raiche <h.raiche at internode.on.net>
> wrote:
>
>> Hi Justine
>>
>> My first comment - this is not an easy topic for people to get there head
>> around.
>>
>> What I was looking for - but now can’t find - was a diagram showing in
>> simple terms what has to happen in the three situations outlined in the
>> paper - where the registrant wants to transfer, where the registrar wants
>> to transfer and when the registry wants to initiate the transfer.  The
>> reason for the need to review the IRTP is the GDPR - information used in
>> authentication of parties is no longer available. Therefore,  a revised
>> policy needs to reflect what information is available post GDPR to
>> authenticate all of the parties.
>>
>> The best way in would be the diagram I was looking for (I may ask James
>> Bladel if he can find it) and then highlight what has changed - so we
>> understand what authentication is possible (and necessary) so that
>> transfers can continue with necessary safeguards to ensure the request for
>> transfer is authenticate, and that the losing and gaining registrars are
>> both satisfied of the authenticity of the request and all of the parties
>> are who they way they are.
>>
>> That said, I am not clear why this is not also on the ALAC policy page,
>> but on the APRALO Policy Forum - is this an issue just for APRALO, or are
>> we participating in a wider ALAC process?
>>
>> (I will email James - it will really help people to visualize the process
>> and better understand both what used to be authenticated before GDPR - and
>> what information is still available so that the transfer can proceed.
>>
>> Holly
>>
>>
>>
>>
>> On Nov 3, 2020, at 6:19 PM, Justine Chew <justine.chew.icann at gmail.com>
>> wrote:
>>
>> All,
>>
>> I have made a start on examining key documents for this Call for Comments
>> and have posted some notes at this Googledoc
>> <https://docs.google.com/document/d/16gXn8QWJge_9ktpetiJ1Tfafvk2KhhGkfJe9tN1_L3k/edit?usp=sharing>
>>
>> Would anyone else like to offer to help? See email below if you would
>> like to do so, thanks.
>>
>> Kind regards,
>> Justine
>>
>> *APRALO Policy Forum
>> <https://community.icann.org/display/APRALO/APRALO+Policy+Forum>*
>>
>>
>> On Mon, 19 Oct 2020 at 16:29, Justine Chew <justine.chew.icann at gmail.com>
>> wrote:
>>
>>> All,
>>>
>>> Thank you to some of you for already having volunteered to help examine
>>> the Preliminary Issue Report on a PDP to Review the Transfer Policy.
>>>
>>> If you have been wanting to get involved in policy development work but
>>> have not yet found an in-road, you may want to consider participating in
>>> this one to do with domain name portability. I would encourage you to do so
>>> especially if you have an interest in registrant issues.
>>>
>>> *After all, more hands make light work!*
>>>
>>>
>>> Here is a Googledoc *(set to comment mode)* to help kick off capturing
>>> of comments etc :
>>> https://docs.google.com/document/d/16gXn8QWJge_9ktpetiJ1Tfafvk2KhhGkfJe9tN1_L3k/edit?usp=sharing
>>> <https://docs.google.com/document/d/16gXn8QWJge_9ktpetiJ1Tfafvk2KhhGkfJe9tN1_L3k/edit?usp=sharing>
>>> Given the voluminous documentation involved, perhaps you might wish to
>>> adopt the following steps:
>>>
>>> Step 1: Choose to focus on one or more topic(s) that interest or concern
>>> you the most, out of the following:
>>>
>>>    1. Gaining & Losing Registrar Form of Authorization ("FOA")
>>>    2. Auth Code Management
>>>    3. Change of Registrant
>>>    4. Transfer Emergency Action Contact ("TEAC")
>>>    5. Transfer Dispute Resolution Policy ("TDRP")
>>>    6. Reversing/NACKing Transfers
>>>    7. ICANN-Approved Transfers
>>>    8. EPDP Rec. 27
>>>    9. Draft Charter - WG Mission & Scope, especially Data & Metrics
>>>    Requirement, and WG Model Structure, Membership Structure & Criteria etc
>>>
>>>
>>> Step 2: Zoom in on the page references under the topic(s) of your
>>> choice, just read those and fill in the accompanying table(s).
>>>
>>> Use the left-menu to navigate between topics. While suggestions on the
>>> format of consultation is not unwelcomed, it is likely better of your time
>>> to focus on content than form.
>>>
>>> Kind regards,
>>> Justine
>>>
>>> *APRALO Policy Forum
>>> <https://community.icann.org/display/APRALO/APRALO+Policy+Forum>*
>>>
>>>
>>> On Wed, 14 Oct 2020 at 11:41, Justine Chew <justine.chew.icann at gmail.com>
>>> wrote:
>>>
>>>> Thanks, Maureen, Holly.
>>>>
>>>> I'm hoping we have a few more expressions of interest to review the
>>>> Issue Report collaboratively.
>>>>
>>>> Will look at setting up a "tool" or "tools" for this later, and will
>>>> see how to best to capture Holly's insights from her earlier review and the
>>>> ALAC statements in respect of the EPDP Final Report.
>>>>
>>>> Kind regards,
>>>> Justine
>>>>
>>>> *APRALO Policy Forum
>>>> <https://community.icann.org/display/APRALO/APRALO+Policy+Forum>*
>>>>
>>>>
>>>> On Wed, 14 Oct 2020 at 11:32, Holly Raiche <h.raiche at internode.on.net>
>>>> wrote:
>>>>
>>>>> Folks
>>>>>
>>>>> While this may well have implications for Net4India, this review was
>>>>> always going to take place because the GDPR provisions  impact on what
>>>>> information can be publicly available/available in what contexts - to
>>>>> verify the actual request and parties to a transfer (and how the GDPR
>>>>> impacts on the agreed processed)
>>>>>
>>>>> Depending on when this review actually starts, I’d be happy to be
>>>>> involved (having sat through the earlier review of the IRTP )
>>>>>
>>>>> Holly
>>>>>
>>>>> On Oct 14, 2020, at 1:58 PM, Maureen Hilyard <
>>>>> maureen.hilyard at gmail.com> wrote:
>>>>>
>>>>> Justine
>>>>>
>>>>> Is discussion of this policy relevant to what is happening in India at
>>>>> the moment where registrants are unable to access their domains so that
>>>>> they can transfer them? A real life situation? What are the implications of
>>>>> this policy?
>>>>>
>>>>> On Tue, 13 Oct 2020, 4:53 pm Justine Chew, <
>>>>> justine.chew.icann at gmail.com> wrote:
>>>>>
>>>>>> All,
>>>>>>
>>>>>> This is an opportunity to examine the adequacy of ICANN's domain name
>>>>>> registration transfer policy.
>>>>>>
>>>>>> COMMENT *Call for Comments to Preliminary Issue Report on a Policy
>>>>>> Development Process to Review the Transfer Policy
>>>>>> <https://www.icann.org/public-comments/transfer-policy-pdp-review-2020-10-12-en> (12
>>>>>> Oct - 30 Nov 2020)*
>>>>>>
>>>>>> *Purpose:* This Public Comment proceeding seeks to obtain community
>>>>>> input on the Preliminary Issue Report on a Policy Development Process to
>>>>>> Review the Transfer Policy.
>>>>>>
>>>>>> *Current Status:* In accordance with the GNSO Policy Development
>>>>>> Process (PDP) rules, ICANN org is publishing the Preliminary Issue Report
>>>>>> for Public Comment to allow for community input on additional information,
>>>>>> or the correction or updating of any information provided so far. ICANN org
>>>>>> is seeking in particular input on the draft policy questions proposed in
>>>>>> Section 3.2.2 of this Preliminary Issue Report, as well as the text
>>>>>> provided in the draft Preliminary Charter in Annex A.
>>>>>>
>>>>>> *Excerpt: Description and Explanation*
>>>>>> At its meeting on 24 June 2020, the GNSO Council voted to request the
>>>>>> preparation of a Preliminary Issue Report on the issues identified in the
>>>>>> Transfer Policy Initial Scoping Paper, to assist in determining whether a
>>>>>> PDP or series of PDPs should be initiated regarding changes to the Transfer
>>>>>> Policy.
>>>>>>
>>>>>> This Preliminary Issue Report on a Policy Development Process to
>>>>>> Review the Transfer Policy examines, et.al, the issues identified in
>>>>>> the Transfer Policy Initial Scoping Paper and includes:
>>>>>>
>>>>>>    1. Gaining & Losing Registrar Form of Authorization ("FOA")
>>>>>>    2. Auth Code Management
>>>>>>    3. Change of Registrant
>>>>>>    4. Transfer Emergency Action Contact ("TEAC")
>>>>>>    5. Transfer Dispute Resolution Policy ("TDRP")
>>>>>>    6. Reversing/NACKing Transfers
>>>>>>    7. ICANN-Approved Transfers
>>>>>>    8. EPDP Rec. 27
>>>>>>
>>>>>> Section 3 of this Report explores the above-referenced issues
>>>>>> individually and provides references to documents and processes that could
>>>>>> inform future policy work.
>>>>>>
>>>>>> *Next Steps: *Following review of the Public Comments received,
>>>>>> ICANN org will update the Preliminary Issue Report and submit a summary of
>>>>>> the comments received together with the Final Issue Report to the GNSO
>>>>>> Council for its consideration and potential action.
>>>>>>
>>>>>> *To Comment:* Please reply in this email thread (comments can be
>>>>>> moved to a workspace subsequently if needed).
>>>>>>
>>>>>> Kind regards,
>>>>>> Justine
>>>>>>
>>>>>> *APRALO Policy Forum
>>>>>> <https://community.icann.org/display/APRALO/APRALO+Policy+Forum>*
>>>>>> _______________________________________________
>>>>>> Apralo-policy mailing list
>>>>>> Apralo-policy at icann.org
>>>>>> https://mm.icann.org/mailman/listinfo/apralo-policy
>>>>>>
>>>>>> _______________________________________________
>>>>>> 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.
>>>>>
>>>>> _______________________________________________
>>>>> Apralo-policy mailing list
>>>>> Apralo-policy at icann.org
>>>>> https://mm.icann.org/mailman/listinfo/apralo-policy
>>>>>
>>>>> _______________________________________________
>>>>> 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.
>>>>>
>>>>>
>>>>>
>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/apralo-policy/attachments/20201110/af4b7de5/attachment-0001.html>