This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/[email protected]/
[address-policy-wg] 62.222.0.0/15
- Previous message (by thread): [address-policy-wg] 62.222.0.0/15
- Next message (by thread): [address-policy-wg] 62.222.0.0/15
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Ronald F. Guilmette
rfg at tristatelogic.com
Wed Oct 9 07:37:34 CEST 2019
In message <CAFV686eC55sR4vd4iB_ykRmf9ddgm1=pOxsNGSVqji+fD08VtQ at mail.gmail.com>, Jacob Slater <jacob at rezero.org> wrote: >According to >https://www.ripe.net/manage-ips-and-asns/resource-transfers-and-mergers/transfer-statistics/within-ripe-ncc-service-region/ipv4-transfer-statistics, >this appears to have been a transfer, not a new allocation. I guess that I will have to speak to my friends in the DB working group about that, because there is *no* indication of this whatsoever in either the current -or- the historical records for the 62.222.0.0/15 block, specifically. The only historical record on file for this block is as follows: ======================================================================== % Version 1 (current version) of object "62.222.0.0 - 62.223.255.255" % This version was a UPDATE operation on 2019-08-20 13:55 inetnum: 62.222.0.0 - 62.223.255.255 netname: IE-COOLWAVE-20010321 country: IE org: ORG-CCL78-RIPE status: ALLOCATED PA mnt-by: mnt-ie-coolwave-1 mnt-by: RIPE-NCC-HM-MNT created: 2019-08-20T11:55:01Z last-modified: 2019-08-20T11:55:01Z source: RIPE
- Previous message (by thread): [address-policy-wg] 62.222.0.0/15
- Next message (by thread): [address-policy-wg] 62.222.0.0/15
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]