fix jgs's 192.0.2.0/12 catch
This commit is contained in:
parent
9e910bf4ed
commit
dcb5a9bffb
1 changed files with 3 additions and 3 deletions
|
|
@ -373,7 +373,7 @@
|
||||||
geofeed file. For example, if the fetching party finds
|
geofeed file. For example, if the fetching party finds
|
||||||
the following inetnum: objects:
|
the following inetnum: objects:
|
||||||
<sourcecode type="rpsl"> <![CDATA[
|
<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
|
remarks: Geofeed https://example.com/geofeed_1
|
||||||
|
|
||||||
inetnum: 192.0.2.0/24 # example
|
inetnum: 192.0.2.0/24 # example
|
||||||
|
|
@ -501,8 +501,8 @@
|
||||||
remembered when the validated public key was used to validate a
|
remembered when the validated public key was used to validate a
|
||||||
signature on a CMS object. Having to remember things from
|
signature on a CMS object. Having to remember things from
|
||||||
certification path validation for use with CMS object processing
|
certification path validation for use with CMS object processing
|
||||||
is too hard. And, the certificates do not get that much bigger
|
would be quite complex and error prone. And, the certificates
|
||||||
by repeating the information.
|
do not get that much bigger by repeating the information.
|
||||||
</t>
|
</t>
|
||||||
|
|
||||||
<t>
|
<t>
|
||||||
|
|
|
||||||
Loading…
Add table
Add a link
Reference in a new issue