
datatracker.ietf.org/doc/html/rfc8805
Preview meta tags from the datatracker.ietf.org website.
Linked Hostnames
11- 28 links towww.rfc-editor.org
- 22 links todatatracker.ietf.org
- 3 links towww.iso.org
- 1 link tocode.google.com
- 1 link togithub.com
- 1 link tomeeting-services.icann.org
- 1 link tomeetings.ripe.net
- 1 link tonoc.ietf.org
Search Engine Appearance
https://datatracker.ietf.org/doc/html/rfc8805
RFC 8805: A Format for Self-Published IP Geolocation Feeds
A Format for Self-Published IP Geolocation Feeds (RFC 8805, )
Bing
RFC 8805: A Format for Self-Published IP Geolocation Feeds
https://datatracker.ietf.org/doc/html/rfc8805
A Format for Self-Published IP Geolocation Feeds (RFC 8805, )
DuckDuckGo

RFC 8805: A Format for Self-Published IP Geolocation Feeds
A Format for Self-Published IP Geolocation Feeds (RFC 8805, )
General Meta Tags
13- titleRFC 8805 - A Format for Self-Published IP Geolocation Feeds
- charsetutf-8
- X-UA-CompatibleIE=edge
- viewportwidth=device-width, initial-scale=1
- descriptionA Format for Self-Published IP Geolocation Feeds (RFC 8805, )
Open Graph Meta Tags
5- og:titleRFC 8805: A Format for Self-Published IP Geolocation Feeds
- og:urlhttps://datatracker.ietf.org/doc/html/rfc8805
- og:site_nameIETF Datatracker
- og:descriptionThis document records a format whereby a network operator can publish a mapping of IP address prefixes to simplified geolocation information, colloquially termed a "geolocation feed". Interested parties can poll and parse these feeds to update or merge with other geolocation data sources and procedures. This format intentionally only allows specifying coarse-level location. Some technical organizations operating networks that move from one conference location to the next have already experimentally published small geolocation feeds. This document describes a currently deployed format. At least one consumer (Google) has incorporated these feeds into a geolocation data pipeline, and a significant number of ISPs are using it to inform them where their prefixes should be geolocated.
- og:typearticle
Link Tags
13- alternate/feed/document-changes/rfc8805/
- apple-touch-iconhttps://static.ietf.org/dt/12.43.1/ietf/images/ietf-logo-nor-180.png
- canonicalhttps://datatracker.ietf.org/doc/html/rfc8805
- iconhttps://static.ietf.org/dt/12.43.1/ietf/images/ietf-logo-nor-32.png
- iconhttps://static.ietf.org/dt/12.43.1/ietf/images/ietf-logo-nor-16.png
Emails
11- ek.ietf%40gmail.com
- kduleba%40google.com
- zszami%40google.com
- smoser%40google.com
- warren%40kumari.net
Links
61- http://www.iso.org/iso/home/standards/country_codes.htm#2012_iso3166-2
- http://www.iso.org/iso/home/standards/country_codes/iso-3166-1_decoding_table.htm
- http://www.w3.org/TR/2008/REC-xml-20081126
- https://code.google.com/p/ipaddr-py
- https://datatracker.ietf.org/doc/draft-google-self-published-geofeeds/09