Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 4.0



 

ISSUE:  A.9

Staff to draft registrar code of conduct if registrars fail to do so by certain time

 

Priority:

RAA Final Report (Medium Priority Item)

 

Issue/Request

RAA -DT:
Recommendations/Options
RAA-DT:
1) Establish a Code and require registrar compliance
2) If a Registrar Code of Practice is developed, some issues for possible inclusion:
• Requirement on registrars to cancel a registration if inaccurate or unreliable WHOIS information is not corrected
• Prominently display contact information. ICANN SAC also recently advised that Registrars should have a 24/7 contact number that connects to a person technically able to deal with abuse notification
• Use commercially available verification systems to provide time of registration validations
• Prohibitions (or stronger prohibitions) on front running, cyber squatting
• Have stronger action by registrars on breaches by resellers

Source: 
RAA-DT Final Report
 

Notes

Additional information regarding requests:  N/A

Source: 

Discussion Points

Description

Date Discussed

 

Discussed process for approving Code of Conduct under RAA – requiring consensus of registrars

Discussed the benefit of including provisions into the RAA rather than a Code of Conduct;

Consideration of Code of Conduct approach as a short-term solution of having all new negotiated amendments apply to registrars at the same time

18 Nov 2011


18 Nov 2011

5 Jan 2012

Proposed Text

 Open

 

Status/Outcome

Under Discussion

 

Explanation

Open

 

COMMENTS:

Comments may be submitted using the “Add Comment” feature below.