From dcb5a9bffbdba8776c6df587ce91b91b6d394e6d Mon Sep 17 00:00:00 2001
From: Randy Bush <randy@psg.com>
Date: Tue, 13 Feb 2024 13:51:42 -0800
Subject: [PATCH] fix jgs's 192.0.2.0/12 catch

---
 draft-ietf-opsawg-9092-update.xml | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/draft-ietf-opsawg-9092-update.xml b/draft-ietf-opsawg-9092-update.xml
index be72e74..f72cc00 100644
--- a/draft-ietf-opsawg-9092-update.xml
+++ b/draft-ietf-opsawg-9092-update.xml
@@ -373,7 +373,7 @@
         geofeed file.  For example, if the fetching party finds
         the following inetnum: objects:
 <sourcecode type="rpsl">      <![CDATA[
-    inetnum: 192.0.2.0/12 # example
+    inetnum: 192.0.0.0/22 # example
     remarks: Geofeed https://example.com/geofeed_1
 
     inetnum: 192.0.2.0/24 # example
@@ -501,8 +501,8 @@
         remembered when the validated public key was used to validate a
         signature on a CMS object.  Having to remember things from
         certification path validation for use with CMS object processing
-        is too hard.  And, the certificates do not get that much bigger
-        by repeating the information.
+        would be quite complex and error prone.  And, the certificates
+        do not get that much bigger by repeating the information.
       </t>
 
       <t>