From bc9f0d26bf17421de99caee76916b6428956d2cb Mon Sep 17 00:00:00 2001 From: Randy Bush Date: Mon, 26 Jun 2023 14:21:24 -0700 Subject: [PATCH] -01 published --- draft-ymbk-9092update.xml | 17 ++++++----------- 1 file changed, 6 insertions(+), 11 deletions(-) diff --git a/draft-ymbk-9092update.xml b/draft-ymbk-9092update.xml index 1ce7c9e..74d80da 100644 --- a/draft-ymbk-9092update.xml +++ b/draft-ymbk-9092update.xml @@ -617,13 +617,15 @@ - 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. - + To prevent undue load on RPSL and geofeed servers, entity-fetching geofeed data using these mechanisms MUST @@ -639,13 +641,6 @@ likely to do the same. - - 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. - -