Non-RIPE INRs in an Example returned by RIPE Whois DB Query Service
Dear DB-WG, Hopefully this email finds you in good health! While exploring some RIPE Whois DB classes [1], i discovered some examples, i thought to be inappropriate [3]. ...i would like to draw to your attention, on the presence of some INRs [2] managed [3] by an other RIR, which appear in content returned when the RIPE Database is queried [2]. __ [1]: <paste1> cacty@shalom:~$ whois -h whois.ripe.net -t route | grep --regexp="^holes" --after-context=0 holes: [optional] [multiple] [ ] </paste1> [2]: <paste2> cacty@shalom:~$ whois -h whois.ripe.net -v route | grep --regexp="^holes$" --after-context=11 holes Lists the component address prefixes that are not reachable through the aggregate route(perhaps that part of the address space is unallocated). An address prefix is represented as an IPv4 address followed by the character slash "/" followed by an integer in the range from 0 to 32. The following are valid address prefixes: 128.9.128.5/32, 128.9.0.0/16, 0.0.0.0/0; and the following address prefixes are invalid: 0/0, 128.9/16 since 0 or 128.9 are not strings containing four integers. </paste2> [3]: <https://www.iana.org/assignments/ipv4-address-space/> Maybe it's the only description which contains such non-RIPE INRs; other than of RFC 5737 [4]... __ [4]: <https://www.iana.org/assignments/iana-ipv4-special-registry/> ...but perhaps someone, from the Staff, should check? Thanks. Shalom, --sb. -- Best Regards ! baya.sylvain [AT cmNOG DOT cm] |cmNOG's Structure <https://www.cmnog.cm/dokuwiki/Structure>|cmNOG's Surveys <https://survey2.cmnog.cm/> Subscribe to the cmNOG's Mailing List <https://lists.cmnog.cm/mailman/listinfo/cmnog/> __ *#LASAINTEBIBLE|#Romains15:33«*Que LE #DIEU de #Paix soit avec vous tous! #Amen!*»#MaPrière est que tu naisses de nouveau. #Chrétiennement«*Comme une biche soupire après des courants d’eau, ainsi mon âme soupire après TOI, ô DIEU!*» (#Psaumes42:2)*
Hi Sylvain, Is your issue simply with using 128.9.0.0/16 and 128.9.128.5/32 as examples rather than a prefix reserved for documentation or something like 192.168.0.0/16? (there is no /16 for documentation purposes afaik) It is a bit difficult for me to understand what you mean so please correct me if I misunderstood. I assume INR means Internet Number Resource? -Cynthia On Fri, Jul 8, 2022 at 10:37 PM Sylvain Baya via db-wg <db-wg@ripe.net> wrote:
Dear DB-WG,
Hopefully this email finds you in good health!
While exploring some RIPE Whois DB classes [1], i discovered some examples, i thought to be inappropriate [3].
...i would like to draw to your attention, on the presence of some INRs [2] managed [3] by an other RIR, which appear in content returned when the RIPE Database is queried [2]. __ [1]: <paste1> cacty@shalom:~$ whois -h whois.ripe.net -t route | grep --regexp="^holes" --after-context=0 holes: [optional] [multiple] [ ] </paste1> [2]: <paste2> cacty@shalom:~$ whois -h whois.ripe.net -v route | grep --regexp="^holes$" --after-context=11 holes
Lists the component address prefixes that are not reachable through the aggregate route(perhaps that part of the address space is unallocated).
An address prefix is represented as an IPv4 address followed by the character slash "/" followed by an integer in the range from 0 to 32. The following are valid address prefixes: 128.9.128.5/32, 128.9.0.0/16, 0.0.0.0/0; and the following address prefixes are invalid: 0/0, 128.9/16 since 0 or 128.9 are not strings containing four integers. </paste2> [3]: <https://www.iana.org/assignments/ipv4-address-space/>
Maybe it's the only description which contains such non-RIPE INRs; other than of RFC 5737 [4]... __ [4]: <https://www.iana.org/assignments/iana-ipv4-special-registry/>
...but perhaps someone, from the Staff, should check?
Thanks.
Shalom, --sb.
--
Best Regards ! baya.sylvain [AT cmNOG DOT cm] |cmNOG's Structure|cmNOG's Surveys Subscribe to the cmNOG's Mailing List __ #LASAINTEBIBLE|#Romains15:33«*Que LE #DIEU de #Paix soit avec vous tous! #Amen!*» #MaPrière est que tu naisses de nouveau. #Chrétiennement «*Comme une biche soupire après des courants d’eau, ainsi mon âme soupire après TOI, ô DIEU!*» (#Psaumes42:2) --
To unsubscribe from this mailing list, get a password reminder, or change your subscription options, please visit: https://lists.ripe.net/mailman/listinfo/db-wg
Dear RIPE DB-WG, ...comments below, inline, please. Thanks. Le samedi 9 juillet 2022, Cynthia Revström <me@cynthia.re> a écrit :
Hi Sylvain,
Hi Cynthia, Thanks for you email, sister.
Is your issue simply with using 128.9.0.0/16 and 128.9.128.5/32 as examples rather than a prefix reserved for documentation or something like 192.168.0.0/16?
No! as i have tried to say, it's about using an active prefix, as an example of unreachable network's prefix. ...i understand that it's out there well before it became reachable; but imho there is no reason to keep using it for such usecase :-/
(there is no /16 for documentation purposes afaik)
Right! though :-) ...remark! please, it's not about documentation, but it's rather a need of example of global unreachable network. And, you can find at least one prefix, to satisfy the need, here [*]. __ [*]: <https://www.iana.org/assignments/iana-ipv4-special-registry/>
It is a bit difficult for me to understand what you mean so please correct me if I misunderstood.
...please see above. But, in case i'm the one, i stand to be corrected too :-)
I assume INR means Internet Number Resource?
You are right, dear! i apology for have not stated it clearly. Hope this clarifies something! Remain blessed. Shalom, --sb
-Cynthia
On Fri, Jul 8, 2022 at 10:37 PM Sylvain Baya via db-wg <db-wg@ripe.net> wrote:
[...]
-- Best Regards ! __ baya.sylvain[AT cmNOG DOT cm]|<https://cmnog.cm/dokuwiki/Structure> Subscribe to Mailing List: <https://lists.cmnog.cm/mailman/listinfo/cmnog/> __ #LASAINTEBIBLE|#Romains15:33«Que LE #DIEU de #Paix soit avec vous tous! #Amen!» #MaPrière est que tu naisses de nouveau. #Chrétiennement «Comme une biche soupire après des courants d’eau, ainsi mon âme soupire après TOI, ô DIEU!»(#Psaumes42:2)
Hello Sylvain, Colleagues,
On 9 Jul 2022, at 22:52, Sylvain Baya via db-wg <db-wg@ripe.net> wrote: ...
Is your issue simply with using 128.9.0.0/16 <http://128.9.0.0/16> and 128.9.128.5/32 <http://128.9.128.5/32> as examples rather than a prefix reserved for documentation or something like 192.168.0.0/16 <http://192.168.0.0/16>?
No! as i have tried to say, it's about using an active prefix, as an example of unreachable network's prefix.
...i understand that it's out there well before it became reachable; but imho there is no reason to keep using it for such usecase :-/
Thank you for pointing this out. The paragraph following the "holes:" attribute definition is intended to describe the format of an address prefix, and the prefixes listed are not examples of holes. I will replace the examples with prefixes reserved for documentation from RFC 5737. Regards Ed Shryane RIPE NCC
Dear RIPE DB-WG, Please find my comments below, inline... Thanks! Le lun. 11 juil. 2022 à 10:39, Edward Shryane <eshryane@ripe.net> a écrit :
Hello Sylvain, Colleagues,
Hi Edward, Thanks for your email, brother :-)
On 9 Jul 2022, at 22:52, Sylvain Baya via db-wg <db-wg@ripe.net> wrote: ...
Is your issue simply with using 128.9.0.0/16 and 128.9.128.5/32 as examples rather than a prefix reserved for documentation or something like 192.168.0.0/16?
No! as i have tried to say, it's about using an active prefix, as an example of unreachable network's prefix.
...i understand that it's out there well before it became reachable; but imho there is no reason to keep using it for such usecase :-/
Thank you for pointing this out.
The paragraph following the "holes:" attribute definition is intended to describe the format of an address prefix, and the prefixes listed are not examples of holes.
That's why Cynthya (i apologize!), rightly, asked me to clarify :'-( ...thanks! i think, i got it now ; having read (!) it finally :-)
I will replace the examples with prefixes reserved for documentation from RFC 5737.
Thanks! btw, now, have you considered the issue raised by Cynthia? ...i can see the progress here [1]. __ [1]: Use documentation prefix 192.0.2.0/24 from RFC 5737 instead of live network prefix from non-RIPE region. (#1044) https://github.com/RIPE-NCC/whois/commit/4a83cc67df45223b5623ac85bc9fa08ac6c... Shalom, --sb.
Regards
Ed Shryane RIPE NCC
-- Best Regards ! baya.sylvain [AT cmNOG DOT cm] |cmNOG's Structure <https://www.cmnog.cm/dokuwiki/Structure>|cmNOG's Surveys <https://survey2.cmnog.cm/> Subscribe to the cmNOG's Mailing List <https://lists.cmnog.cm/mailman/listinfo/cmnog/> __ *#LASAINTEBIBLE|#Romains15:33«*Que LE #DIEU de #Paix soit avec vous tous! #Amen!*»#MaPrière est que tu naisses de nouveau. #Chrétiennement«*Comme une biche soupire après des courants d’eau, ainsi mon âme soupire après TOI, ô DIEU!*» (#Psaumes42:2)*
Hi Sylvain,
On 11 Jul 2022, at 19:48, Sylvain Baya <abscoco@gmail.com> wrote:
Dear RIPE DB-WG,
Please find my comments below, inline... Thanks!
...
btw, now, have you considered the issue raised by Cynthia?
Can you clarify please? Do you mean Cynthia's comment, "there is no /16 for documentation purposes afaik" ? I'm using the documentation /24's as examples of valid and invalid prefixes, not as examples of holes. Regards Ed Shryane RIPE NCC
I don't think I really made any big comment so I am guessing it was that but if a /16 wasn't needed for demonstration purposes, I prefer using the documentation specific prefixes (as you mentioned) of course. -Cynthia On Mon, Jul 11, 2022 at 11:09 PM Edward Shryane via db-wg <db-wg@ripe.net> wrote:
Hi Sylvain,
On 11 Jul 2022, at 19:48, Sylvain Baya <abscoco@gmail.com> wrote:
Dear RIPE DB-WG,
Please find my comments below, inline... Thanks!
...
btw, now, have you considered the issue raised by Cynthia?
Can you clarify please? Do you mean Cynthia's comment, "there is no /16 for documentation purposes afaik" ?
I'm using the documentation /24's as examples of valid and invalid prefixes, not as examples of holes.
Regards Ed Shryane RIPE NCC
--
To unsubscribe from this mailing list, get a password reminder, or change your subscription options, please visit: https://lists.ripe.net/mailman/listinfo/db-wg
participants (3)
-
Cynthia Revström -
Edward Shryane -
Sylvain Baya