-----Original Message----- From: gtld-tech <gtld-tech-bounces@icann.org> On Behalf Of Gavin Brown Sent: Wednesday, February 27, 2019 4:41 AM To: gtld-tech@icann.org Subject: [EXTERNAL] [gtld-tech] EPDP recommendations and EPP
Hi all,
The EPDP final report says that, if a domain name has a technical contact (whose information is different from the registrant's), the only data that registrars should send to registries are the technical contact's name, email address, and phone number (if any).
Assuming that technical contacts should still be created and managed as RFC 5733 contact objects, and also assuming that this recommendation is adopted without change, it poses a challenge, because the RFC requires all contact objects to have <city> and <cc> elements.
I've been thinking about how this could be resolved, here are some ideas (in descending order of nastiness):
* write a new RFC which updates RFC 5733 to make the <city> and <cc> elements optional
* write a new EPP extension which makes the technical contact's name, email address, and phone number directly attributes of the the domain name rather than a contact object
* define a "convention" that allows the <city> and <cc> elements to contain placeholder values, such as: <city>-</city> and <cc>XX</cc> which pose no data protection issues.
Any thoughts?
I tend to prefer the last option. It doesn't have any dependencies on pushing documents through the IETF, and it doesn't get us into developing policy-specific specifications. Scott