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/ncc-services-wg@ripe.net/
[ncc-services-wg] Re: [db-wg] "referral-by:" attribute
- Previous message (by thread): [ncc-services-wg] Re: [db-wg] "referral-by:" attribute
- Next message (by thread): [ncc-services-wg] Re: [db-wg] "referral-by:" attribute
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Andy Davidson
andy at nosignal.org
Wed Jun 9 10:56:21 CEST 2010
On 8 Jun 2010, at 15:55, Wilfried Woeber, UniVie/ACOnet wrote: > Shane Kerr wrote: >> On Tue, 2010-06-08 at 12:37 +0200, Denis Walker wrote: >>> If we make it optional now, although it is still in the RPSL definition, >>> it can be completely ignored. Does anyone have any strong views on this >>> either way? >> I'd actually suggest going further, and getting rid of it completely. > If it doesn't dere a purpose any longer, yes, I agree. I agree, let's do this. [...] > IIRC, the "usual" approach was to deal with such a change in phases, like > issue a warning for a while, then refuse an update if it violates the > acceptable schema, and eventually cleaning up old objects that haven't been > touched for a looong time. > > I'm sure the DB guys can refresh our memory regarding the specifics. This sounds like the way forward with regards to implementation too. Andy
- Previous message (by thread): [ncc-services-wg] Re: [db-wg] "referral-by:" attribute
- Next message (by thread): [ncc-services-wg] Re: [db-wg] "referral-by:" attribute
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]