diff --git a/draft-ymbk-9092update.xml b/draft-ymbk-9092update.xml
index 636d519..5b7d356 100644
--- a/draft-ymbk-9092update.xml
+++ b/draft-ymbk-9092update.xml
@@ -8,7 +8,7 @@
 <?rfc compact="yes"?>
 <?rfc subcompact="no"?>
 
-<rfc category="std" docName="draft-ymbk-sidrops-9092-update-01"
+<rfc category="std" docName="draft-ymbk-opsawg-9092-update-00"
      submissionType="IETF" consensus="true" ipr="trust200902"
      obsoletes="9092" >
 
@@ -82,7 +82,7 @@
         This document specifies how to augment the Routing Policy
         Specification Language inetnum: class to refer specifically to
         geofeed data files and describes an optional scheme that uses
-        the Routing Public Key Infrastructure to authenticate the
+        the Resource Public Key Infrastructure to authenticate the
         geofeed datafiles.
       </t>
 </abstract>
@@ -643,8 +643,14 @@
       <name>Security Considerations</name>
       <t>
         It is generally prudent for a consumer of geofeed data to also
-        use other sources to cross validate the data.  All the security
-        considerations of <xref target="RFC8805" format="default"/> apply here as well.
+        use other sources to cross-validate the data.  All the security
+        considerations of <xref target="RFC8805" format="default"/>
+        apply here as well.
+      </t>
+      <t>
+	The consumer of geofeed data SHOULD fetch and process the data
+	themselves.  Importing datasets produced and/or processed by a
+	third-party places ill-advised trust in the third-party.
       </t>
       <t>
         As mentioned in <xref target="auth" format="default"/>, many RPSL
@@ -653,8 +659,6 @@
         target="auth" format="default"/> suggests an unfortunately complex
         method for stronger authentication based on the RPKI.
       </t>
-
-
       <t>
         For example, if an inetnum: for a wide address range (e.g., a
         /16) points to an RPKI-signed geofeed file, a customer or
@@ -677,29 +681,8 @@
     <section anchor="iana" numbered="true" toc="default">
       <name>IANA Considerations</name>
       <t>
-        The IANA is requested to modify the References of the object
-        identifier for the content type in the "SMI Security for S/MIME
-        CMS Content Type (1.2.840.113549.1.9.16.1)" registry to the
-        following:
+	There are no new actions needed by the IANA.
       </t>
-
-<table anchor="iana_table">
-  <thead>
-    <tr>
-      <th>Decimal</th>  
-      <th>Description</th>
-      <th>References</th>
-    </tr>
-  </thead>
-  <tbody>        
-    <tr>
-      <td>47</td>
-      <td>id-ct-geofeedCSVwithCRLF</td>
-      <td>RFC8805</td>
-    </tr>
-  </tbody>
-</table>
-      
     </section>
   </middle>
   <back>