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] Broken RDAP response
- Previous message (by thread): [db-wg] Broken RDAP response
- Next message (by thread): [db-wg] The Ongoing Summer of Hijacks: MNT-SERVERSGET / dnsget.top
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Theodoros Polychniatis
tpolychnia at ripe.net
Mon Aug 13 15:45:42 CEST 2018
Dear Tore/all, When the RIR Engineering Coordination Group (ECG) met during the last IETF, there was a lot of discussion on the inconsistencies surrounding the RDAP implementations between the RIRs - including this multiple country issue. Our plan is to identify a list of issues and create a shared backlog of work items. We will then prioritise these and start working to address them in Q4 2018. PS. Note that Tim is no longer working at the RIPE NCC - Thiago da Cruz Pereira has taken over many of his duties and was at the ECG meeting. Kind regards, Theodoros Polychniatis, Manager Software Engineering, RIPE NCC On 09/08/2018 20:24, Tore Anderson via db-wg wrote: > * Brian Rak via db-wg > >> It is interesting that RDAP cannot represent what's apparently a valid database entry though! > Yeah, the standards are unfortunately not in sync. > > Tim Bruijnzeels said he was going to bring up the issue at an > IETF meeting. I don't know if anything came out of it. > > https://github.com/arineng/nicinfo/issues/21#issuecomment-258860529 > > Tore >
- Previous message (by thread): [db-wg] Broken RDAP response
- Next message (by thread): [db-wg] The Ongoing Summer of Hijacks: MNT-SERVERSGET / dnsget.top
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]