Hello All, I apologize for my silence but I have been buried in GDPR hell. I have taken a break from GDPR stuff and I am in Bangkok this week for the soft launch of the .SPORT top level domain at a sporting convention. It appears that there are some resolution issues involving the domain which just completed its controlled interruption late last week. Based on my initial analysis it appears that it may be browser based. I would greatly appreciate it if the list could help me in some trouble shooting by sharing to me your results involving trying to resolve the following 3 domain names which are the only ones in the zone file at this time ALL.SPORT GDPR.SPORT and NIC.SPORT. The only domain that should resolve content is NIC.SPORT, the other two domain names should provide a pop-up asking for user credentials. The Registry Operator for .SPORT also ran into problems seeking to use letsencrypt.org to obtain an X.509 certificate for the domains. Letsencrypt and they said they used publicsuffix.org and .SPORT does not appear on their list, see https://publicsuffix.org/list/public_suffix_list.dat This may or may not be involved with the resolution problem which appears to be more of a Mac/Safari browser issue. I also found some discussion on this topic which may also be impacting .LLC as well, see https://github.com/publicsuffix/list/issues/639 Any help or guidance would be greatly appreciated. Best regards, Michael
It is likely directly related. The public suffix list is not always in-sync. We did identify this issue in the UA007 document: https://uasg.tech/wp-content/uploads/2016/05/UASG007-version-9-2017-02-02.pd... (page 22) Public Suffix List The Public Suffix List (PSL), managed by volunteers of the Mozilla Foundation, provides an accurate list of domain name suffixes. This list is a set of DNS names or wildcards concatenated with dots and encoded using UTF-8. If you need to use the PSL as an authoritative source for domain names, your software must regularly receive PSL updates. Do not bake static copies of the PSL into your software with no update mechanism. You can use the link below to make your app download an updated list periodically. The list gets updated once per day from Github: • https://publicsuffix.org/list/public_suffix_list.dat This may also be useful: https://uasg.tech/wp-content/uploads/2017/06/UA001-v2015040-UA-Knowledge-Bas... As you try to outreach to browsers specifically. Edmon -----Original Message----- From: UA-discuss [mailto:ua-discuss-bounces@icann.org] On Behalf Of Michael Palage Sent: Tuesday, April 17, 2018 12:07 PM To: 'ua-discuss' <UA-discuss@icann.org> Subject: [UA-discuss] UA Issue - Need some help Hello All, I apologize for my silence but I have been buried in GDPR hell. I have taken a break from GDPR stuff and I am in Bangkok this week for the soft launch of the .SPORT top level domain at a sporting convention. It appears that there are some resolution issues involving the domain which just completed its controlled interruption late last week. Based on my initial analysis it appears that it may be browser based. I would greatly appreciate it if the list could help me in some trouble shooting by sharing to me your results involving trying to resolve the following 3 domain names which are the only ones in the zone file at this time ALL.SPORT GDPR.SPORT and NIC.SPORT. The only domain that should resolve content is NIC.SPORT, the other two domain names should provide a pop-up asking for user credentials. The Registry Operator for .SPORT also ran into problems seeking to use letsencrypt.org to obtain an X.509 certificate for the domains. Letsencrypt and they said they used publicsuffix.org and .SPORT does not appear on their list, see https://publicsuffix.org/list/public_suffix_list.dat This may or may not be involved with the resolution problem which appears to be more of a Mac/Safari browser issue. I also found some discussion on this topic which may also be impacting .LLC as well, see https://github.com/publicsuffix/list/issues/639 Any help or guidance would be greatly appreciated. Best regards, Michael
Hi- I saw this came from THE Michael Palage and expedited it ... This is now escalated within the team. I see an issue submitted but not a patch - I'll discuss this with the core group there to expedite it. The main volunteer, Gerv Markham has critical health issue and has transitioned the project of maintaining the PSL over to github where there new 'owner' who leads the project. I reviewed the delta between PSL and contracted TLDs and between my efforts and those of another volunteer we found five that needed attention, as well as a missking Kashmiri IDN ccTLD for India to add. I am in touch with the other volunteers with commit privileges about adding patches for .招聘, .charity, .inc, .llc and .sport and have updated the ticket accordingly. Still, Edmon pointed out that despite the UASG recommendations, there are some downline users such as Apple and some of the other authors of browsers or software incorporate a static copy of TLD lists into their own releases, and as such, once these hit the PSL it takes time to trickle out into their updates and patches. -J On Mon, Apr 16, 2018, 21:33 Edmon <edmon@registry.asia> wrote:
It is likely directly related. The public suffix list is not always in-sync.
We did identify this issue in the UA007 document: https://uasg.tech/wp-content/uploads/2016/05/UASG007-version -9-2017-02-02.pdf (page 22) Public Suffix List The Public Suffix List (PSL), managed by volunteers of the Mozilla Foundation, provides an accurate list of domain name suffixes. This list is a set of DNS names or wildcards concatenated with dots and encoded using UTF-8. If you need to use the PSL as an authoritative source for domain names, your software must regularly receive PSL updates. Do not bake static copies of the PSL into your software with no update mechanism. You can use the link below to make your app download an updated list periodically. The list gets updated once per day from Github: • https://publicsuffix.org/list/public_suffix_list.dat
This may also be useful: https://uasg.tech/wp-content/uploads/2017/06/UA001-v2015040- UA-Knowledge-Base.pdf
As you try to outreach to browsers specifically.
Edmon
-----Original Message----- From: UA-discuss [mailto:ua-discuss-bounces@icann.org] On Behalf Of Michael Palage Sent: Tuesday, April 17, 2018 12:07 PM To: 'ua-discuss' <UA-discuss@icann.org> Subject: [UA-discuss] UA Issue - Need some help
Hello All,
I apologize for my silence but I have been buried in GDPR hell.
I have taken a break from GDPR stuff and I am in Bangkok this week for the soft launch of the .SPORT top level domain at a sporting convention. It appears that there are some resolution issues involving the domain which just completed its controlled interruption late last week. Based on my initial analysis it appears that it may be browser based.
I would greatly appreciate it if the list could help me in some trouble shooting by sharing to me your results involving trying to resolve the following 3 domain names which are the only ones in the zone file at this time ALL.SPORT GDPR.SPORT and NIC.SPORT. The only domain that should resolve content is NIC.SPORT, the other two domain names should provide a pop-up asking for user credentials.
The Registry Operator for .SPORT also ran into problems seeking to use letsencrypt.org to obtain an X.509 certificate for the domains. Letsencrypt and they said they used publicsuffix.org and .SPORT does not appear on their list, see https://publicsuffix.org/list/ public_suffix_list.dat
This may or may not be involved with the resolution problem which appears to be more of a Mac/Safari browser issue.
I also found some discussion on this topic which may also be impacting .LLC as well, see https://github.com/publicsuffix/list/issues/639
Any help or guidance would be greatly appreciated.
Best regards,
Michael
On 4/17/18 12:52 AM, Jothan Frakes wrote:
Hi-
I saw this came from THE Michael Palage and expedited it ...
This is now escalated within the team.
I see an issue submitted but not a patch - I'll discuss this with the core group there to expedite it.
Thanks.
The main volunteer, Gerv Markham has critical health issue and has transitioned the project of maintaining the PSL over to github where there new 'owner' who leads the project.
I'm not sure why you used quotes around the word owner. Note that Ryan Sleevi actually works on Chrome, not Firefox. This is a true community effort. Naturally, Gerv's leadership is missed, but others have stepped into the breach - and he was never the primary contributor to the GitHub repository: https://github.com/publicsuffix/list/graphs/contributors
I reviewed the delta between PSL and contracted TLDs and between my efforts and those of another volunteer we found five that needed attention, as well as a missking Kashmiri IDN ccTLD for India to add.
I am in touch with the other volunteers with commit privileges about adding patches for .招聘, .charity, .inc, .llc and .sport and have updated the ticket accordingly.
This issue is indeed closed: https://github.com/publicsuffix/list/issues/639 So things are working as designed. :-) There's no magic here requiring special access to a core group, just the usual open-source processes: file issues, provide pull requests, etc. Peter
there new 'owner' who leads the project.
I'm not sure why you used quotes around the word owner.
I did the quotes to indicate, as you point out, that there is not really any owner, really, beacause many of the folks in registry-land are used to there being a CEO or chairman.
Jothan, Thanks - drinks on me in Panama. Best regards, Michael From: Jothan Frakes <jothan@jothan.com> Sent: Tuesday, April 17, 2018 2:53 AM To: Michael Palage <michael@palage.com> Cc: Universal Acceptance <UA-discuss@icann.org>; edmon <edmon@registry.asia> Subject: Re: [UA-discuss] UA Issue - Need some help Hi- I saw this came from THE Michael Palage and expedited it ... This is now escalated within the team. I see an issue submitted but not a patch - I'll discuss this with the core group there to expedite it. The main volunteer, Gerv Markham has critical health issue and has transitioned the project of maintaining the PSL over to github where there new 'owner' who leads the project. I reviewed the delta between PSL and contracted TLDs and between my efforts and those of another volunteer we found five that needed attention, as well as a missking Kashmiri IDN ccTLD for India to add. I am in touch with the other volunteers with commit privileges about adding patches for .招聘, .charity, .inc, .llc and .sport and have updated the ticket accordingly. Still, Edmon pointed out that despite the UASG recommendations, there are some downline users such as Apple and some of the other authors of browsers or software incorporate a static copy of TLD lists into their own releases, and as such, once these hit the PSL it takes time to trickle out into their updates and patches. -J On Mon, Apr 16, 2018, 21:33 Edmon <edmon@registry.asia <mailto:edmon@registry.asia> > wrote: It is likely directly related. The public suffix list is not always in-sync. We did identify this issue in the UA007 document: https://uasg.tech/wp-content/uploads/2016/05/UASG007-version-9-2017-02-02.pd... (page 22) Public Suffix List The Public Suffix List (PSL), managed by volunteers of the Mozilla Foundation, provides an accurate list of domain name suffixes. This list is a set of DNS names or wildcards concatenated with dots and encoded using UTF-8. If you need to use the PSL as an authoritative source for domain names, your software must regularly receive PSL updates. Do not bake static copies of the PSL into your software with no update mechanism. You can use the link below to make your app download an updated list periodically. The list gets updated once per day from Github: • https://publicsuffix.org/list/public_suffix_list.dat This may also be useful: https://uasg.tech/wp-content/uploads/2017/06/UA001-v2015040-UA-Knowledge-Bas... As you try to outreach to browsers specifically. Edmon -----Original Message----- From: UA-discuss [mailto:ua-discuss-bounces@icann.org <mailto:ua-discuss-bounces@icann.org> ] On Behalf Of Michael Palage Sent: Tuesday, April 17, 2018 12:07 PM To: 'ua-discuss' <UA-discuss@icann.org <mailto:UA-discuss@icann.org> > Subject: [UA-discuss] UA Issue - Need some help Hello All, I apologize for my silence but I have been buried in GDPR hell. I have taken a break from GDPR stuff and I am in Bangkok this week for the soft launch of the .SPORT top level domain at a sporting convention. It appears that there are some resolution issues involving the domain which just completed its controlled interruption late last week. Based on my initial analysis it appears that it may be browser based. I would greatly appreciate it if the list could help me in some trouble shooting by sharing to me your results involving trying to resolve the following 3 domain names which are the only ones in the zone file at this time ALL.SPORT GDPR.SPORT and NIC.SPORT. The only domain that should resolve content is NIC.SPORT, the other two domain names should provide a pop-up asking for user credentials. The Registry Operator for .SPORT also ran into problems seeking to use letsencrypt.org <http://letsencrypt.org> to obtain an X.509 certificate for the domains. Letsencrypt and they said they used publicsuffix.org <http://publicsuffix.org> and .SPORT does not appear on their list, see https://publicsuffix.org/list/public_suffix_list.dat This may or may not be involved with the resolution problem which appears to be more of a Mac/Safari browser issue. I also found some discussion on this topic which may also be impacting .LLC as well, see https://github.com/publicsuffix/list/issues/639 Any help or guidance would be greatly appreciated. Best regards, Michael
Would be an honor but it is not necessary - just glad it worked out. Maybe come speak at MERGE.SHOW in September ...? -Jothan On Tue, Apr 17, 2018, 18:15 Michael Palage <michael@palage.com> wrote:
Jothan,
Thanks - drinks on me in Panama.
Best regards,
Michael
*From:* Jothan Frakes <jothan@jothan.com> *Sent:* Tuesday, April 17, 2018 2:53 AM *To:* Michael Palage <michael@palage.com> *Cc:* Universal Acceptance <UA-discuss@icann.org>; edmon < edmon@registry.asia> *Subject:* Re: [UA-discuss] UA Issue - Need some help
Hi-
I saw this came from THE Michael Palage and expedited it ...
This is now escalated within the team.
I see an issue submitted but not a patch - I'll discuss this with the core group there to expedite it.
The main volunteer, Gerv Markham has critical health issue and has transitioned the project of maintaining the PSL over to github where there new 'owner' who leads the project.
I reviewed the delta between PSL and contracted TLDs and between my efforts and those of another volunteer we found five that needed attention, as well as a missking Kashmiri IDN ccTLD for India to add.
I am in touch with the other volunteers with commit privileges about adding patches for .招聘, .charity, .inc, .llc and .sport and have updated the ticket accordingly.
Still, Edmon pointed out that despite the UASG recommendations, there are some downline users such as Apple and some of the other authors of browsers or software incorporate a static copy of TLD lists into their own releases, and as such, once these hit the PSL it takes time to trickle out into their updates and patches.
-J
On Mon, Apr 16, 2018, 21:33 Edmon <edmon@registry.asia> wrote:
It is likely directly related. The public suffix list is not always in-sync.
We did identify this issue in the UA007 document: https://uasg.tech/wp-content/uploads/2016/05/UASG007- version-9-2017-02-02.pdf (page 22) Public Suffix List The Public Suffix List (PSL), managed by volunteers of the Mozilla Foundation, provides an accurate list of domain name suffixes. This list is a set of DNS names or wildcards concatenated with dots and encoded using UTF-8. If you need to use the PSL as an authoritative source for domain names, your software must regularly receive PSL updates. Do not bake static copies of the PSL into your software with no update mechanism. You can use the link below to make your app download an updated list periodically. The list gets updated once per day from Github: • https://publicsuffix.org/list/public_suffix_list.dat
This may also be useful: https://uasg.tech/wp-content/uploads/2017/06/UA001- v2015040-UA-Knowledge-Base.pdf
As you try to outreach to browsers specifically.
Edmon
-----Original Message----- From: UA-discuss [mailto:ua-discuss-bounces@icann.org] On Behalf Of Michael Palage Sent: Tuesday, April 17, 2018 12:07 PM To: 'ua-discuss' <UA-discuss@icann.org> Subject: [UA-discuss] UA Issue - Need some help
Hello All,
I apologize for my silence but I have been buried in GDPR hell.
I have taken a break from GDPR stuff and I am in Bangkok this week for the soft launch of the .SPORT top level domain at a sporting convention. It appears that there are some resolution issues involving the domain which just completed its controlled interruption late last week. Based on my initial analysis it appears that it may be browser based.
I would greatly appreciate it if the list could help me in some trouble shooting by sharing to me your results involving trying to resolve the following 3 domain names which are the only ones in the zone file at this time ALL.SPORT GDPR.SPORT and NIC.SPORT. The only domain that should resolve content is NIC.SPORT, the other two domain names should provide a pop-up asking for user credentials.
The Registry Operator for .SPORT also ran into problems seeking to use letsencrypt.org to obtain an X.509 certificate for the domains. Letsencrypt and they said they used publicsuffix.org and .SPORT does not appear on their list, see https://publicsuffix.org/list/ public_suffix_list.dat
This may or may not be involved with the resolution problem which appears to be more of a Mac/Safari browser issue.
I also found some discussion on this topic which may also be impacting .LLC as well, see https://github.com/publicsuffix/list/issues/639
Any help or guidance would be greatly appreciated.
Best regards,
Michael
Michael, As others mentioned, once .SPORT gets into PSL, that triggers a chain of events that eventually leads to full client devices acceptance. I haven't found a way to expedite it, but it usually takes one to three version upgrades for Apple to fix Safari and Mobile Safari, which happens independently. If you have AppleCare for a Mac or an iPhone, you can raise that issue as a software bug, but this doesn't seem to impact the release cycle. But since you mentioned controlled interruption, you might to warn them to turn off the wildcard record, as the results below should be mutually exclusive: host all.sport all.sport has address 83.166.138.31 all.sport mail is handled by 1 mail.all.sport. host esdasjewq.sport esdasjewq.sport has address 127.0.53.53 esdasjewq.sport mail is handled by 10 your-dns-needs-immediate-attention.sport. Rubens
On 17 Apr 2018, at 01:07, Michael Palage <Michael@palage.com> wrote:
Hello All,
I apologize for my silence but I have been buried in GDPR hell.
I have taken a break from GDPR stuff and I am in Bangkok this week for the soft launch of the .SPORT top level domain at a sporting convention. It appears that there are some resolution issues involving the domain which just completed its controlled interruption late last week. Based on my initial analysis it appears that it may be browser based.
I would greatly appreciate it if the list could help me in some trouble shooting by sharing to me your results involving trying to resolve the following 3 domain names which are the only ones in the zone file at this time ALL.SPORT GDPR.SPORT and NIC.SPORT. The only domain that should resolve content is NIC.SPORT, the other two domain names should provide a pop-up asking for user credentials.
The Registry Operator for .SPORT also ran into problems seeking to use letsencrypt.org to obtain an X.509 certificate for the domains. Letsencrypt and they said they used publicsuffix.org and .SPORT does not appear on their list, see https://publicsuffix.org/list/public_suffix_list.dat
This may or may not be involved with the resolution problem which appears to be more of a Mac/Safari browser issue.
I also found some discussion on this topic which may also be impacting .LLC as well, see https://github.com/publicsuffix/list/issues/639
Any help or guidance would be greatly appreciated.
Best regards,
Michael
participants (5)
-
Edmon -
Jothan Frakes -
Michael Palage -
Peter Saint-Andre -
Rubens Kuhl