Skip to content

Instantly share code, notes, and snippets.

Show Gist options
  • Save seitsu/7de30413df0240d28acfe81b79fd6c0e to your computer and use it in GitHub Desktop.
Save seitsu/7de30413df0240d28acfe81b79fd6c0e to your computer and use it in GitHub Desktop.
Machine-readable Registry Maintenance Notification RSS Feed
Machine-readable registry maintenance notifications as RSS 2.0 feeds (https://validator.w3.org/feed/docs/rss2.html) on port 443:
GET https://status.registry.tld/maintenance-production.rss
GET https://status.registry.tld/maintenance-test.rss
GET https://status.registry.tld/maintenance-staging.rss
GET https://status.registry.tld/maintenance-all.rss
Response for maintenance-production.rss:
HTTP Response Code 200 (RFC 7231)
content-type: application/rss+xml
<?xml version="1.0" encoding="UTF-8" ?>
<rss version="2.0">
<channel>
<title>Registry Maintenance Notification</title>
<link>https://portal.registry.tld</link>
<description>Maintenance Notification for the next 3 months</description>
<item>
<title>epp.registry.tld</title>
<pubDate>Sun, 30 Apr 2017 06:00:00 +0000</pubDate>
<category>planned maintenance</category>
<description>blackout</description>
<guid>https://portal.registry.tld/maintenance-description-april-2017</guid>
<comments>barfoo, foobar</comments>
</item>
<item>
<title>epp.registry.tld, whois.registry.tld, https://portal.registry.tld</title>
<pubDate>Thu, 15 Jun 2017 04:30:00 +0000</pubDate>
<category>planned maintenance</category>
<description>partial, partial, blackout</description>
<guid>https://portal.registry.tld/maintenance-description-june-2017</guid>
<comments>foobar</comments>
</item>
</channel>
</rss>
Explanation of RSS response elements
- title [required] (string) affected maintained systems
- pubDate [required] (string) start date according RFC 822 (ddd, dd MMM yyyy HH:mm:ss zzzz)
- category [required] (string) 'planned maintenance' or 'emergency maintenance'
- description [required] (string) impact level of affected systems; values are 'partial' or 'blackout'; order by affected systems
- guid [required] (string) URL to detailed maintenance description must be unique within the RSS feed
- comments [required] (string) affected top-level domains
Remarks
- How do we specify the end date?
- Dates in the future throw warnings "Implausible date"
- Comments throw warnings "comments must be a full and valid URL"
- Affected Systems (title) and impact level (description) is provided as string and needs to be parsed or we would need to add more items for each affected system
- Intervention 'yes' or 'no' should be specified somehow
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment