You see the year mentioned in the netname generated during the transfer
by RIPE (always using original date) IE-COOLWAVE-20010321 and in
RIPEstat: First ever seen announced by AS8918
<https://stat.ripe.net/AS8918>, on *2001-03-24 00:00:00 UTC*.
Kind regards
On 09/10/2019 10:22, Piotr Strzyzewski via address-policy-wg wrote:
On Wed, Oct 09, 2019 at 12:14:23AM -0700, Ronald F. Guilmette wrote:
Regardless of what that other non-authoritative source of information
may say, may I ask you to please tell me what *you* see when *you* perform
the following two commands?
whois -h whois.ripe.net -- "--list-versions 62.222.0.0/15"
whois -h whois.ripe.net -- "--show-version 1 62.222.0.0/15"
Maybe I need new glasses, but I'm not seeing the year 2002 mentioned in
the outputs of these two commands.
Maybe I'm just doing it wrong. Do I need to try using negative numbers
as arguments to the --show-version option?
Does that option accept imaginary numbers as arguments?
Start from reading some documentation.
https://www.ripe.net/manage-ips-and-asns/db/support/documentation/ripe-database-documentation/types-of-queries/16-12-historical-queries
"It is possible to query the history of operational data objects that
still exist."
It has been already pointed out that this /15 could have been part of
something bigger or, quite contrary, part of two separate /16 or even
something completely different, which means that the original object
could be non-existent. Checking this out is left as an exercise for the
reader.
Piotr
--
Thomas BRENAC
https://www.brenac.eu
+33686263575
Certified IPv4 Broker by RIPE NCC, ARIN, APNIC and LACNIC
The content of this email is confidential and intended for the recipient
specified in message only. It is strictly forbidden to share any part of this
message with any third party, without a written consent of the sender. If you
received this message by mistake, please reply to this message and follow with
its deletion, so that we can ensure such a mistake does not occur in the future.
This message has been sent as a part of discussion between BRENAC EURL and the
addressee whose name is specified above. Should you receive this message by
mistake, we would be most grateful if you informed us that the message has been
sent to you. In this case, we also ask that you delete this message from your
mailbox, and do not forward it or any part of it to anyone else. Thank you for
your cooperation and understanding.
We puts the security of the client at a high priority. Therefore, we have put
efforts into ensuring that the message is error and virus-free. Unfortunately,
full security of the email cannot be ensured as, despite our efforts, the data
included in emails could be infected, intercepted, or corrupted. Therefore, the
recipient should check the email for threats with proper software, as the
sender does not accept liability for any damage inflicted by viewing the
content of this email.
The views and opinions included in this email belong to their author and do not
necessarily mirror the views and opinions of the company. Our employees are
obliged not to make any defamatory clauses, infringe, or authorize infringement
of any legal right. Therefore, the company will not take any liability for such
statements included in emails. In case of any damages or other liabilities
arising, employees are fully responsible for the content of their emails.
