-01 published
This commit is contained in:
parent
fd3d04e848
commit
bc9f0d26bf
1 changed files with 6 additions and 11 deletions
|
|
@ -617,13 +617,15 @@
|
|||
</t>
|
||||
|
||||
<t>
|
||||
Geofeed data are orthogonal to geographic attributes in the
|
||||
inetnum:. Attributes such as country: tend to be
|
||||
Hints in inetnum:s such as country:, geoloc:, etc. tend to be
|
||||
administrative, and not deployment specific. Consider large,
|
||||
possibly global, providers with headquarters very far from most
|
||||
of their deployments.
|
||||
of their deployments. Therefore, if geofeed data are specified,
|
||||
either as a geofeed: attribute or in a geofeed remarks:
|
||||
attribute, other geographic hints such as country:, geoloc:, DNS
|
||||
geoloc RRsets, etc., for that address range MUST be ignored.
|
||||
</t>
|
||||
|
||||
|
||||
<t>
|
||||
To prevent undue load on RPSL and geofeed servers,
|
||||
entity-fetching geofeed data using these mechanisms <bcp14>MUST
|
||||
|
|
@ -639,13 +641,6 @@
|
|||
likely to do the same.
|
||||
</t>
|
||||
|
||||
<t>
|
||||
If geofeed data are specified, either as a geofeed: attribute or
|
||||
in a geofeed remarks: attribute, other geographic hints such as
|
||||
country:, DNS geoloc RRsets, etc., for that address range should
|
||||
be ignored.
|
||||
</t>
|
||||
|
||||
</section>
|
||||
|
||||
<section anchor="privacy" numbered="true" toc="default">
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue