From ac73a023b996e0097149bea0690bd3f15331e7b0 Mon Sep 17 00:00:00 2001
From: Randy Bush <randy@psg.com>
Date: Thu, 1 Feb 2024 10:11:34 -0800
Subject: [PATCH] s/currently/at the time of publishing .../

---
 draft-ietf-opsawg-9092-update.xml | 39 ++++++++++++++++---------------
 1 file changed, 20 insertions(+), 19 deletions(-)

diff --git a/draft-ietf-opsawg-9092-update.xml b/draft-ietf-opsawg-9092-update.xml
index 9a5d1ed..2b9ee50 100644
--- a/draft-ietf-opsawg-9092-update.xml
+++ b/draft-ietf-opsawg-9092-update.xml
@@ -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".