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] RIPE 73 DB-WG agenda V1 (and IRR Homing)
- Previous message (by thread): [db-wg] RIPE 73 DB-WG agenda V1 (and IRR Homing)
- Next message (by thread): [db-wg] RIPE 73 DB-WG agenda V1 (and IRR Homing)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Daniel Shaw
daniel at afrinic.net
Thu Oct 27 09:03:38 CEST 2016
> On 27 Oct 2016, at 10:54 AM, Tim Bruijnzeels <tim at ripe.net> wrote: > > Hi Daniel, > >> On 27 Oct 2016, at 08:20, Daniel Shaw <daniel at afrinic.net> wrote: >> >> Their default behaviour to their operator customers is “create objects in RIPE DB”, up until either the customer or AFRINIC gets in touch and says “no, and here’s why”. Usually thereafter all is good. :-) > > Do you think this will be fixed by the proposed communication/outreach phase in which we were (all, not just Afrinic and RIPE NCC but operators too - *NOG meetings etc) supposed to communicate the intent to all stakeholders,then followed by a phase where creating new such objects in the RIPE Database would be disallowed - with a friendly error message essentially saying "Please use the Afrinic IRR for creating this object, read more details here [link]”? Hi Tim, WG, I do. Well I think it’s on the way to being fixed already and would get fixed *eventually* anyway. But I strongly feel that a unified and organised outreach as proposed will vastly accelerate this, yes. And I think that’s a good thing obviously :) Regards, Daniel
- Previous message (by thread): [db-wg] RIPE 73 DB-WG agenda V1 (and IRR Homing)
- Next message (by thread): [db-wg] RIPE 73 DB-WG agenda V1 (and IRR Homing)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]