Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove outdated asterisk for Yemeni suffix #897

Closed
wants to merge 1 commit into from
Closed

Remove outdated asterisk for Yemeni suffix #897

wants to merge 1 commit into from

Conversation

bsolomon1124
Copy link

The use of an asterisk before *.ye suggests that this suffix does
does not allow domain names to be registered directly under the suffix,
but instead must be registered as a third level name.

There is ample empirical evidence that this is outdated; the
page http://althawrah.ye/archives/597366 is 200-OK as of
Thu Oct 17 11:31:44 EDT 2019, and althawrah is the actual domain,
not second-level domain or part of the suffix.

Related discussion:

https://stackoverflow.com/q/58434990/7954504

The use of an asterisk before *.ye suggests that this suffix does
does not allow domain names to be registered directly under the suffix,
but instead must be registered as a third level name.

There is ample empirical evidence that this is outdated;  the
page http://althawrah.ye/archives/597366 is 200-OK as of
Thu Oct 17 11:31:44 EDT 2019, and althawrah is the actual domain,
not second-level domain or part of the suffix.

Related discussion:

> https://stackoverflow.com/q/58434990/7954504
@sleevi
Copy link
Contributor

sleevi commented Oct 17, 2019

@bsolomon1124 Thanks for opening this.

For ccTLDs, we only accept PRs from the ccTLD Registry Operator or by pointing to evidence of public policies documented by the ccTLD Registry Operator. Do you represent the Registry? Alternatively, can you point to policies published by the Registry Operator (i.e. explicit policies, not implicit results)

@bsolomon1124
Copy link
Author

@sleevi No, I do not represent TeleYemen in any capacity.

However, from the existing page (http://www.y.net.ye/services/domain_name.htm) linked from public_suffix_list.dat (e.g. prior to this commit):

  1. This page makes no mention of needing to use a third-level domain. It begs the question of why the asterisk was used in the first place.
  2. The same page displays this headline prominently:

Screen Shot 2019-10-17 at 1 56 13 PM

Would you consider this a policy? If not, what would you propose?

@sleevi
Copy link
Contributor

sleevi commented Oct 17, 2019

The answer on that related Stack Overflow is correct. In general, contacting the ccTLD Operator (e.g. https://www.iana.org/domains/root/db/ye.html ) and requesting they submit a correction and/or document their registration policies is a potential path forward.

@sleevi
Copy link
Contributor

sleevi commented Oct 17, 2019

@weppos @dnsguru if y'all aren't auto-watching issues and might have contacts with TeleYemen from ICANN engagements.

@weppos
Copy link
Member

weppos commented Oct 22, 2019

@weppos @dnsguru if y'all aren't auto-watching issues and might have contacts with TeleYemen from ICANN engagements.

Unfortunately, I don't.

@bsolomon1124
Copy link
Author

bsolomon1124 commented Oct 22, 2019

Okay, I'm going to give it a shot and email the technical contact listed for TeleYemen. Can't hurt to ask...

@sleevi Is there a contact point they can use if they prefer not to file through GitHub or do not have a GitHub account?

@bsolomon1124
Copy link
Author

I messaged the technical contact listed on IANA db ([email protected]) on 10/24/19 but have not heard back as of 11/12/19.

@sleevi
Copy link
Contributor

sleevi commented Dec 5, 2019

Any updates? I appreciate you trying :)

@bsolomon1124
Copy link
Author

Have not heard back but a next step could be to look for other contact info there.

@dnsguru
Copy link
Member

dnsguru commented Dec 23, 2019

Have been tracking; reached out to POC for .ye in October but no reply. Agree they would be the appropriate party to submit this change

@dnsguru
Copy link
Member

dnsguru commented Dec 23, 2019

I messaged the technical contact listed on IANA db ([email protected]) on 10/24/19 but have not heard back as of 11/12/19.

We get this a lot, and I suspect that the admin emails get a lot of spam due to public listing at IANA, which have valid requests like yours or ours lost in the noise.

@dnsguru
Copy link
Member

dnsguru commented Mar 3, 2020

@bsolomon1124
The time you took to make this is appreciated.

I and some of the other volunteers here have invested some time in validation of this submission and were unable to confirm.

Unfortunately, it was not possible to verify the list change through the available information or a verifiable source, and we're also unable to run the DNS _psl TXT record here, so we'll have to close this for now.

I have reached out subsequently to find out about .YE and have not had a response.

@dnsguru dnsguru closed this Mar 3, 2020
@bsolomon1124 bsolomon1124 deleted the fix-ye-suffix branch March 28, 2020 22:01
@bsolomon1124
Copy link
Author

@dnsguru @sleevi I know this convo is from a while back, but resurfacing it because I received just this morning an email from the domain teleyemen.com.ye regarding updating the suffic list for .ye. This is the body of the email:

Please be advised that we represent the ccTLD registry: TeleYemen (me and my manager- listed in CC- who is also listed in IANA page as admin contact for the .ye ccTLD).

I am sending you, requesting to update the .ye in the suffix list as follows:

// ye : Confirmed by registry [email protected]
ye
com.ye
edu.ye
gov.ye
net.ye
mil.ye
org.ye

If you need a further confirmation from my manager himself, please let me know and I shall report to him to send you from his mail box.

I realize just copy-pasting here does little to verify the authenticity to you, but I also do not want to unnecessarily disclose the full email address or name.

If having a copy of this email would be sufficient, what would be the best way to get that to one of the maintainers of this repo?

@dnsguru
Copy link
Member

dnsguru commented Jan 13, 2021

Hi @bsolomon1124 they would need to add a dns record for each string in order to indicate their administration can be validated.

We need to be able to issue the command
nslookup -type=txt _psl.com.ye
and get an answer of the URL of this Pull Request. This allows us to validate a round-trip and verify the request comes from an authoritative source that is in administrative control of the zone(s).

We should be able to query 1.1.1.1 or 8.8.8.8 and get these answered.

Here is what they'll need in zones:

_psl.ye IN TXT https://github.com/publicsuffix/list/pull/897
_psl.com.ye IN TXT https://github.com/publicsuffix/list/pull/897
_psl.edu.ye IN TXT https://github.com/publicsuffix/list/pull/897
_psl.gov.ye IN TXT https://github.com/publicsuffix/list/pull/897
_psl.net.ye IN TXT https://github.com/publicsuffix/list/pull/897
_psl.mil.ye IN TXT https://github.com/publicsuffix/list/pull/897
_psl.org.ye IN TXT https://github.com/publicsuffix/list/pull/897

@dnsguru dnsguru self-assigned this Jan 13, 2021
@dnsguru dnsguru added the 🩺 pending-validation Something needs to be validated label Jan 13, 2021
@dnsguru
Copy link
Member

dnsguru commented Jan 13, 2021

Also, the PSL file has undergone significant revisions since this initial PR was submitted, so we're going to need you to re-base it - can be done in this PR or if you (or their administrative contact) create another new PR, reference this in the comments by putting #897 in it

@dnsguru
Copy link
Member

dnsguru commented Jan 14, 2021

Unable to re-open for #1182 - new pull request must be created

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🩺 pending-validation Something needs to be validated waiting-followup Blocked for need of follow-up
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants