[IRT.RegDataPolicy] IRT Task 249: Registry Escrow for Registrar Abuse Contact Email and Phone

Mon Mar 25 17:38:05 UTC 2024

Hi Steve,

I’m am also good with discussing the task below as proposed by Dennis. 

I am not sure how the items you want to know the status of have anything to do with this IRT. The first item is 100% checked by ICANN Compliance as part of the their audits and other compliance monitoring. The other monitoring requests might be something that ICANN does, but these are well outside of the scope of this IRT, so I do not think it is appropriate for us to discuss these items. 

Regards,

Owen

> On Mar 23, 2024, at 07:47, Steve Crocker via IRT.RegDataPolicy <irt.regdatapolicy at icann.org> wrote:
> 
> CAUTION: This email originated from outside the organization. Do not click links unless you can confirm the sender and know the content is safe.
> I'm in agreement with the proposal presented in the slide deck.
> 
> The proposal covers the very specific details of how to submit abuse contact details to the escrow system.
> 
> What is the status of:
> Testing whether the abuse contacts work.
> Monitoring whether those who need to know and use the abuse contacts do indeed know and use them?
> Monitoring whether the abuse contacts are used by people who should not be using them?
> Reporting all of the above to the community.
> Thanks,
> 
> Steve
> 
> On Fri, Mar 22, 2024 at 8:04 AM Dennis Chang via IRT.RegDataPolicy <irt.regdatapolicy at icann.org <mailto:irt.regdatapolicy at icann.org>> wrote:
>> Dear IRT,
>> 
>>  
>> 
>> Here it is.  #249 IRT Task.  
>> 
>> This should provide more info on what I was referring to in my earlier email below.
>> 
>>  
>> 
>> Please review to prepare to discuss at the next IRT meeting.
>> 
>> 249
>> 
>> Registry Escrow for Registrar Abuse Contacts  <https://community.icann.org/display/RDPIRT/RegDataPolicy+Implementation+Resource+Documents?preview=/124847947/320012442/Registration%20Data%20Policy%20-%20Registry%20Escrow%20Of%20Registrar%E2%80%99s%20Abuse%20Contact%20Information%20.pdf>	
>> 20240326
>> 
>>  
>> 
>> Thanks,
>> 
>> Dennis Chang 
>> 
>>  
>> 
>> From: "IRT.RegDataPolicy" <irt.regdatapolicy-bounces at icann.org <mailto:irt.regdatapolicy-bounces at icann.org>> on behalf of "Dennis Chang via IRT.RegDataPolicy" <irt.regdatapolicy at icann.org <mailto:irt.regdatapolicy at icann.org>>
>> Reply-To: Dennis Chang <dennis.chang at icann.org <mailto:dennis.chang at icann.org>>
>> Date: Monday, March 18, 2024 at 2:45 PM
>> To: "Dennis Chang via IRT.RegDataPolicy" <irt.regdatapolicy at icann.org <mailto:irt.regdatapolicy at icann.org>>
>> Subject: [IRT.RegDataPolicy] IRT Meeting on 27 March Agenda: Registry Escrow for Registrar Abuse Contact Email and Phone
>> 
>>  
>> 
>> Dear IRT,
>> 
>>  
>> 
>> How’s everyone post-ICANN79?  
>> 
>> It was nice seeing you in person in Puerto Rico,
>> 
>>  
>> 
>> As you’ve advised, we will keep the IRT meetings going for policy related items and implementation details that warrants broader awareness.
>> 
>>  
>> 
>> For the next meeting, we have one topic regarding Registry Escrow for Registrar Abuse Contacts.
>> 
>>  
>> 
>> Registry Data Policy Section 8.4 covers what Registry Operator MUST submit to escrow agent.
>> . . .
>> 
>> 8.4.8   Registrar Abuse Contact Email
>> 
>> 8.4.9   Registrar Abuse Contact Phone
>> 
>>  
>> 
>> We’ like to discuss with the IRT on how we propose to handle these two data items in a consistent clear way for implementation.
>> 
>> We are putting together a few slides to provide the information in advance of the meeting and will discuss the details and answer questions at the meeting.
>> 
>>  
>> 
>> I’ll be following up with the slide deck this week but wanted to first let you know what the meeting will be about.
>> 
>>  
>> 
>> Stay tuned,
>> 
>> -- 
>> 
>> Kind Regards,
>> 
>> Dennis S. Chang
>> 
>> GDD Programs Director
>> 
>> Phone: +1 213 293 7889
>> 
>> Sykpe: dennisSchang
>> 
>> www.icann.org <http://www.icann.org/>  One World – One Internet
>> 
>>  
>> 
>> _______________________________________________
>> IRT.RegDataPolicy mailing list
>> IRT.RegDataPolicy at icann.org <mailto:IRT.RegDataPolicy at icann.org>
>> https://mm.icann.org/mailman/listinfo/irt.regdatapolicy
>> 
>> _______________________________________________
>> 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.
> 
> 
> -- 
>  <https://wallet.unumid.co/authenticate?referralCode=tcp16fM4W47y>********************
> CAUTION:
> This email originated from outside the organization. Do not click
> links unless you can confirm the sender and know the content is safe.
> ********************
> 
> _______________________________________________
> IRT.RegDataPolicy mailing list
> IRT.RegDataPolicy at icann.org
> https://mm.icann.org/mailman/listinfo/irt.regdatapolicy
> 
> _______________________________________________
> 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: <https://mm.icann.org/pipermail/irt.regdatapolicy/attachments/20240325/36d8b62f/attachment-0001.html>