Billing Contact Council Vote
Dear collagues, this is just to let you know that the GNSO Council just voted with the required majority to fix the billing contact inconsistency. Only the IPC voted against the motion. I am happy we could resolve this without additional formal hurdles in a pragmatic way. Best, Thomas
The larger issue, which remains unaddressed, is that there is no definition and hence no meaning to the Billing Contact. It clearly cannot be related to the billing for the domain name because the Account Holder is responsible for that. Perhaps it was once intended to be the person to contact regarding payment to the entity that has the domain name for whatever services that entity is offering to the public. But I'm just guessing. The same defect applies to the Admin and Tech contacts. Some registrars assign a specific role to the Admin contact, but, as best I can tell, there is no common definition of these roles. For a role to have meaning, the following have to exist: - There would be a formal requirement that the person named in that role would be notified of their appointment, that person would have to agree, and there has to be a record. (Compare with the designation of the Registrant, which does have these requirements.) - There would be clear documentation of the authority and obligations associated with that role. The authority speaks to what the person is permitted to do, and the obligations speak to what the person is required to do. - The above requirements would have to be documented and publicly available. (The above would not necessarily require that access to the contact data be publicly available as long as keeping access limited would not be inconsistent with carrying out the role.) Steve On Thu, Apr 10, 2025 at 5:36 PM Thomas Rickert | rickert.law via IRT.RegDataPolicy <irt.regdatapolicy@icann.org> wrote:
Dear collagues,
this is just to let you know that the GNSO Council just voted with the required majority to fix the billing contact inconsistency. Only the IPC voted against the motion.
I am happy we could resolve this without additional formal hurdles in a pragmatic way.
Best,
Thomas _______________________________________________ IRT.RegDataPolicy mailing list -- irt.regdatapolicy@icann.org To unsubscribe send an email to irt.regdatapolicy-leave@icann.org
_______________________________________________ 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.
-- Sent by a Verified sender
participants (2)
-
Steve Crocker -
Thomas Rickert | rickert.law