Hi Robert, Thank you for the information, is it just anchor hosts or also probe hosts out of interest?
Personally I don't think this is an issue as long as the DB team has something to document all other use cases of the handles within the other parts of the RIPE NCC or RIPE. I think not needing to provide the role data in multiple places is a good thing as it helps with reducing the amount of places the data would need to be updated in. (and as such I assume would help make the data more up to date) Denis, I think an NWI would be really good for this as it could help to come up with the best solution. -Cynthia On Mon, Feb 1, 2021 at 9:49 AM Robert Kisteleki via db-wg <db-wg@ripe.net> wrote: > Hello, > > On 2021-01-28 19:37, denis walker via db-wg wrote: > > Hi Will > > > > I wasn't aware that the RIPE Atlas system/service had any reliance on > > objects in the RIPE Database. Maybe Robert can elaborate more on this? > > Anchor hosts can, if they wish to do so, add their contact details (ie. > a RIPE DB role) as a reference to their anchor; this is displayed on the > RIPE Atlas UI. This is convenience feature only, no operation depends on > it. The DB side is probably unaware of this as it's just an incoming link. > > This behaviour of course can be changed and we appreciate any community > guidance on it. > > Regards, > Robert > >
