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]/
[db-wg] Sideline --template [was: Certain sponsored? ASNs without sponsoring-org]
- Previous message (by thread): [db-wg] Sideline --template [was: Certain sponsored? ASNs without sponsoring-org]
- Next message (by thread): [db-wg] Sideline --template [was: Certain sponsored? ASNs without sponsoring-org]
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Cynthia Revström
me at cynthia.re
Mon Jan 7 14:56:12 CET 2019
Hi Wilfried, Well it does have an org attribute but the organization that is specified is of type "OTHER" and since the ASN is not legacy it would need a sponsoring-org attribute if the organization was of type "OTHER". I have attached a flowchart to help visualize it, I may be wrong but from my understanding, this is how it is. Kind regards, Cynthia Revström On 2019-01-07 14:47, Wilfried Wöber wrote: > Hm, I am a tad puzzled, because AS200358 *does* have an org: reference, > although it claims to be a "Registrar" (BoltN Hosting Limited (Registrar Services)). > > So I would assume that AS200358 is a sponsored AS#? > > As I am not aware that we use the "Registrar" term or model in the IP registry, > I tried to follow up on the org-type: OTHER by an attempt to get a listing of the > possible values for org-type: by using the template flag of whois. > > Unfortunately, neither the short format -t nor the --template syntax is accepted > by the whois web interface. "ERROR:111: invalid option supplied" > > So, the primary Q is: which values are accepted or used in the org-type: attribute? > > Secondly, are there other flags which cannot be used in the web interface (and why?) > > All the best for a smooth start into ++(2018), > best regards, > Wilfried > > On 07/01/2019 11:38, Cynthia Revström via db-wg wrote: >> Just realized I made a mistake while writing the last message, ASNs without sponsoring-org attribute and without LEGACY status, and ORG that is of type other are unsponsored. >> >> Kind regards, >> Cynthia Revström >> >> On 2019-01-07 11:34, Cynthia Revström via db-wg wrote: >>> Just an update: Laurens Hoogendoorn from the NCC contacted me and did indeed confirm that ASNs without LEGACY status with an ORG that is OTHER are indeed unsponsored, and that you can look at stat.ripe.net historical whois to find out for how long. >>> >>> I do still think that it should be more obvious than this. >>> >>> Kind regards, >>> Cynthia Revström >>> >>> On 2019-01-07 10:57, Cynthia Revström via db-wg wrote: >>>> So I have now run across several ASNs in which the org is of type "OTHER" yet there is no sponsoring-org, could this please be clarified? >>>> >>>> Example ASNs: AS200358, AS204842 >>>> >>>> If it is like I think it is, it must be that they have lost their sponsors but if that is the case, I would like to see a remark that is an "RIPE NCC managed value" saying something like "This ASN does not have any sponsor since YYYY-MM-DD". >>>> >>>> I am not entirely sure on this but something to clarify what is going on. >>>> >>>> Kind regards, >>>> Cynthia Revström >>>> >>>> -------------- next part -------------- A non-text attachment was scrubbed... Name: ripe_asn.png Type: image/png Size: 13559 bytes Desc: not available URL: </ripe/mail/archives/db-wg/attachments/20190107/506e5aac/attachment.png>
- Previous message (by thread): [db-wg] Sideline --template [was: Certain sponsored? ASNs without sponsoring-org]
- Next message (by thread): [db-wg] Sideline --template [was: Certain sponsored? ASNs without sponsoring-org]
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]