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

Add azimuth.network and arvo.network #812

Merged
merged 3 commits into from
May 24, 2019
Merged

Add azimuth.network and arvo.network #812

merged 3 commits into from
May 24, 2019

Conversation

Fang-
Copy link
Contributor

@Fang- Fang- commented May 7, 2019

  • Description of Organization
  • Reason for PSL Inclusion
  • DNS verification via dig
  • Run Syntax Checker (make test)

Description of Organization

Organization Website: https://urbit.org

I am Mark Staarink, engineer at Tlon, the company working on Urbit. It comprises several separate components, which include Azimuth (decentralized identity) and Arvo (personal server).

Reason for PSL Inclusion

Azimuth and Arvo will provide identity owners with their own subdomain under azimuth.network and arvo.network respectively. For example, palfun-foslup.arvo.network.

In the case of Azimuth, the identity subdomain will serve as a unique log-on point for that specific identity.
In the case of Arvo, the identity subdomain will point to the owner's personal server, which can serve arbitrary content.

DNS Verification via dig

> dig +short TXT _psl.azimuth.network
"https://github.com/publicsuffix/list/pull/812"

> dig +short TXT _psl.arvo.network
"https://github.com/publicsuffix/list/pull/812"

make test

make test sees all tests pass.

@Fang- Fang- marked this pull request as ready for review May 7, 2019 20:55
@sleevi sleevi added the waiting-followup Blocked for need of follow-up label May 24, 2019
@sleevi
Copy link
Contributor

sleevi commented May 24, 2019

Please place these in a single section for your organization.

@Fang-
Copy link
Contributor Author

Fang- commented May 24, 2019

@sleevi Fair! Let me know if you need anything else.

@sleevi sleevi merged commit c3a44bf into publicsuffix:master May 24, 2019
@sleevi sleevi added h=sleevi (historical) Marked as approved and ready to merge by @sleevi and removed waiting-followup Blocked for need of follow-up labels May 24, 2019
@sleevi sleevi self-requested a review May 24, 2019 10:42
@dnsguru
Copy link
Member

dnsguru commented Nov 6, 2020

@Fang- will azimuth.network be renewing?

@Fang-
Copy link
Contributor Author

Fang- commented Nov 6, 2020

@dnsguru I'm not sure I understand the question. If you're asking whether we want to keep these domains on the PSL, the answer is yes. Do we need to explicitly flag this somewhere?

@dnsguru
Copy link
Member

dnsguru commented Nov 7, 2020

@Fang glad to hear you are renewing vs deleting. Encourage >1 year renewal when you do

we have been getting a lot of 'set and forget' inclusions into the PSL that subsequently do not renew the domain name and we have a discussion around planning for this to be automated to delete entries where the domain name does not hold a renewal term of >1 year. In a manual review, I noticed that your domain name has a very short term left in its registration (see #1119) and want to determine if we can delete the entry if you're not renewing it, or encourage you to renew the domain name for >1 year when you do in order to not get flagged by the automation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
h=sleevi (historical) Marked as approved and ready to merge by @sleevi
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants