Hi Job
Good point and I agree.
cheers
denis
co-chair DB WG
On 25 October 2017 at 14:13, Job Snijders wrote:
> Dear Denis,
>
> On Wed, Oct 25, 2017 at 2:08 PM, den is via db-wg wrote:
>> Putting together several points from today:
>>
>> -dropping ASN auth for ROUTE c
Hi all
Putting together several points from today:
-dropping ASN auth for ROUTE creation
-wanting to know as precisely as possible who made a change
-updating MNTNER objects by email
-previous discussions on personal auth (which was also mentioned today)
maybe we could do a wider review on the a
Colleagues
The draft problem definition can be found here:
https://www.ripe.net/ripe/mail/archives/db-wg/2016-May/005240.html
cheers
denis
co-chair DB WG
On 19 October 2017 at 18:12, den is wrote:
> Colleagues
>
> The DB WG co-chairs would now like to address this issue. There was
> some discus
Colleagues
The DB WG co-chairs would now like to address this issue. There was
some discussion on the mailing list in May to July of 2016.
In brief the issue is that the current history mechanism has an
arbitrary design constraint that only the history of currently
existing objects can be seen. T
Hi Colleagues
Rob is correct, option 1 has been proposed before and it was opposed.
Whilst neither supporting nor opposing anyone's views let me ask a
couple of questions. I think these questions need addressing even if
it is just to quote some historic facts and dismiss them. It's always
good to
--- Begin Message ---
3) Consider possible, simple options to allow non RIPE resource
holders to 'approve' (if not authorise) the creation of a foreign
ROUTE object.
cheers
denis
co-chair DB WG
On 17 October 2017 at 01:23, William Sylvester via db-wg wrote:
>
>
> -- Forwarded message --
