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/db-wg@ripe.net/
[db-wg] Source GRS vs RIPE
- Previous message (by thread): [db-wg] Source GRS vs RIPE
- Next message (by thread): [db-wg] Source GRS vs RIPE
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Sandra Murphy
sandy at tislabs.com
Fri Jul 13 01:41:27 CEST 2018
RIPE’s stat page https://stat.ripe.net/AS8945#tabId=routing shows that 188.64.224.0/24 was announced by AS8945 from late 2009 to the end of Sep 2015. From early Dec 2015 - now, various more specifics in 188.64.224.0/21 have been consistently announced by AS13414. No other consistent originators of parts of 188.64.224.0/21 are shown. AS8945 is still evidently an actively maintained AS in the RIPE database, last updated in Jan 2018. It just doesn’t announce any routes (zero) and has not announced anything for a long time. It is still keeping its membership active - the organization was updated this week. The AS is still on the list of members for Equinix Paris. The RIPE database lists the AS as “Heron SAS”, which I can’t find as a commercial concern. The maintainer email is @scanandtarget.com (a charming name, yes?). The historical RIPE stat files Geoff pointed to show the /21 as allocated in Jul 2009, and that same line shows up in the stat files since then. Until yesterday. Until the stat file for 20180711, when it switches from “allocated” to “reserved”. (Coincidence?) According to the NRO explanation of the stat file format, “reserved” could mean many things, one of the most likely being returns that are not yet available for reassignment. I can’t guess what that means about who returned the space. Or about twitter continued use going forward. —Sandy > On Jul 12, 2018, at 7:59 AM, Christoffer Hansen via db-wg <db-wg at ripe.net> wrote: > > On Thu, 12 Jul 2018 at 13:45, Aftab Siddiqui <aftab.siddiqui at gmail.com> wrote: >> >> Yup sending an email to support (RIPE) for clarification. > > I would be happy if you could share a summarized edit of the response > you get back. > >> But Twitter NOC is adamant that they are not doing the wrong thing (advertising unallocated address space) because it shows in RADB-GRS via RIPE Whois > > The routing policy (NOT assignment!) shows up in RIPE Whois. Because > RIPE mirrors objects in RADB. > Where Twitter themself have registeret only route policy objects for > both 188.64.224.0/21 and smaller /23 and /24 prefixes inside the main > /21 prefix. > > ~ > whois -h whois.radb.net 188.64.224.0/21 > route: 188.64.224.0/21 > descr: Twitter Route > origin: AS13414 > admin-c: NETWO3685-ARIN > tech-c: NETWO3685-ARIN > notify: noc at twitter.com > mnt-by: MAINT-AS13414 > changed: frehoie at twitter.com 20160112 #15:43:10Z > source: RADB > > http://www.radb.net/ > "Merit RADb is a public registry of network routing information that > assists with the transfer of data over the Internet. > For over 20 years, Merit RADb has been serving the Internet community. > Thousands of organizations that operate networks have registered their > routing policies in Merit RADb to facilitate the operation of the > Internet, including Internet service providers, universities, and > businesses. The information in Merit RADb enables organizations to > troubleshoot routing problems, automatically configure backbone > routers, generate access lists, and perform network planning. > Any organization with an autonomous system number (ASN) may register > in Merit RADb for an annual fee of $495 (U.S. Dollars). Non-profit > organizations may register annually for $395." > > And seeing as RADB is a commercial entity advertising themself with > the line "organizations that operate networks have registered their > routing policies in Merit RADb". > I read it as RADB is only a DB for advertising routing policies. NOT > for holding INETNUM assignments. > > Which concludes I am in agreement with you. > > I am not sure Twitter is doing the right thing of advertising unallocated space.
- Previous message (by thread): [db-wg] Source GRS vs RIPE
- Next message (by thread): [db-wg] Source GRS vs RIPE
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]