randy/draft-9092update
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

s/currently/at the time of publishing .../

Browse source
This commit is contained in:
Randy Bush 2024-02-01 10:11:34 -08:00
parent 34d45b6252
commit ac73a023b9
1 changed files with 20 additions and 19 deletions
Download patch file Download diff file Expand all files Collapse all files

39
draft-ietf-opsawg-9092-update.xml
View file

@ -223,8 +223,8 @@
target="RFC4012" format="default"/>. Since then, it has been
modified and extensively enhanced in the Regional Internet
Registry (RIR) community, mostly by RIPE <xref target="RIPE-DB"
format="default"/>. Currently, change control effectively lies
in the operator community.
format="default"/>. At the time of publishing this document,
change control effectively lies in the operator community.
</t>
<t>
@ -679,14 +679,14 @@
target="auth"/>.
</t>
<t>
Currently, geolocation providers have bulk WHOIS data access at
all the RIRs. An anonymized version of such data is openly
available for all RIRs except ARIN, which requires an
authorization. However, for users without such authorization,
the same result can be achieved with extra RDAP effort. There is
open-source code to pass over such data across all RIRs, collect
all geofeed references, and process them <xref
target="GEOFEED-FINDER" format="default"/>.
At the time of publishing this document, geolocation providers
have bulk WHOIS data access at all the RIRs. An anonymized
version of such data is openly available for all RIRs except
ARIN, which requires an authorization. However, for users
without such authorization, the same result can be achieved with
extra RDAP effort. There is open-source code to pass over such
data across all RIRs, collect all geofeed references, and
process them <xref target="GEOFEED-FINDER" format="default"/>.
</t>
<t>
@ -732,8 +732,9 @@
<name>Implementation Status</name>
<t>
Currently, the geofeed: attribute in inetnum objects has
been implemented in the RIPE and APNIC databases.
At the time of publishing this document, the geofeed: attribute
in inetnum objects has been implemented in the RIPE and APNIC
databases.
</t>
<t>
@ -742,13 +743,13 @@
</t>
<t>
Currently, the registry data published by ARIN are not the same
RPSL as that of the other registries (see <xref target="RFC7485"
format="default"/> for a survey of the WHOIS Tower of Babel);
therefore, when fetching from ARIN via FTP <xref
target="RFC0959" format="default"/>, WHOIS <xref
target="RFC3912" format="default"/>, the Registration Data
Access Protocol (RDAP) <xref target="RFC9082"
At the time of publishing this document, the registry data
published by ARIN are not the same RPSL as that of the other
registries (see <xref target="RFC7485" format="default"/> for a
survey of the WHOIS Tower of Babel); therefore, when fetching
from ARIN via FTP <xref target="RFC0959" format="default"/>,
WHOIS <xref target="RFC3912" format="default"/>, the
Registration Data Access Protocol (RDAP) <xref target="RFC9082"
format="default"/>, etc., the "NetRange" attribute/key must be
treated as "inetnum", and the "Comment" attribute must be
treated as "remarks".