Don't claim that only one abuse contact is allowed#3173
Conversation
nowhere in the RFCs does it say that only one contact is allowed, and indeed there are many situations where it's actually an array of contacts. We have a bunch of registrars that already have multiple abuse contacts. I'm not sure why the comment originally claimed this, but it's from years and years ago. b/534931561
There was a problem hiding this comment.
Digging into this further:
• Original implementation and single-contact frontend override (May 6, 2017):
commit 2846f9c ("This CL include changes in the registrar console that makes it possible to designate an abuse contact in domain WHOIS record, per ICANN's CL&D requirement")
• Initial introduction of the WHOIS abuse field (May 4, 2017):
commit 7a3852b ("Add visibleInWhoisAsAbuse field in RegistrarContact")
• Related ICANN CL&D WHOIS policy formatting changes:
commit 8892656 ("Make WHOIS domain query return conform to ICANN CL&D policy")
commit e8eabe0 ("Update WHOIS output format to reflect CL&D and PDT requirements")
• Renaming from WHOIS to RDAP across the console (PR #2863):
commit dee132d ("Rename visibleInWhois fields to visibleInRdap")
It seems like the restriction was originally required for WHOIS as per CL&D (linked from one of those commits), but isn't relevant in RDAP (which I assume is the RFC you're referring to), as RDAP does indeed allow multiple RDDS abuse contacts per domain.
So at least that answers the question of why the comment originally claimed it -- because it was true for WHOIS!
@CydeWeys made 1 comment.
Reviewable status: 0 of 2 files reviewed, all discussions resolved.
gbrodman
left a comment
gbrodman
left a comment
There was a problem hiding this comment.
That makes a lot of sense! Well fortunately it's definitely not the case in RDAP any more.
@gbrodman made 1 comment.
Reviewable status: 0 of 2 files reviewed, all discussions resolved.
|
Can you synthesize those findings about the why and include them in the commit description? Then we're good-to-go. |
CydeWeys
left a comment
CydeWeys
left a comment
There was a problem hiding this comment.
@CydeWeys made 1 comment.
Reviewable status: 0 of 2 files reviewed, all discussions resolved.
2 participants
nowhere in the RFCs does it say that only one contact is allowed, and indeed there are many situations where it's actually an array of contacts. We have a bunch of registrars that already have multiple abuse contacts. I'm not sure why the comment originally claimed this, but it's from years and years ago.
more details after ben's investigation:
https://www.icann.org/en/contracted-parties/consensus-policies/registry-registration-data-directory-services-consistent-labeling-and-display-policy/registry-registration-data-directory-services-consistent-labeling-and-display-policy-01-02-2017-en is the ICANN WHOIS data display policy. This basically says that there's precisely one abuse contact per registrar. With the advent of RDAP, this WHOIS restriction is no longer relevant. https://datatracker.ietf.org/doc/rfc9083/ removes these limits and we can include more than one if we wish.
b/534931561
This change is