[db-wg] NCC still enforcing descr: content
- Previous message (by thread): [db-wg] NCC still enforcing descr: content
- Next message (by thread): [db-wg] NCC still enforcing descr: content
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Job Snijders
job at ntt.net
Wed Jul 29 10:35:53 CEST 2015
On Tue, Jul 28, 2015 at 06:01:29PM +0200, Tim Bruijnzeels wrote: > > On Jul 27, 2015, at 6:41 PM, Jan Saner <jan at trick77.com> wrote: > > Since the NCC still seems to heavy-handedly revert changes to descr: > > in AUT-NUM, INETNUM and INETNUM6 I’m wondering what the current > > status of the implementation mentioned by Tim in a post to this list > > from February is: > > > > https://www.ripe.net/ripe/mail/archives/db-wg/2015-February/004496.html > > Well, in short I misjudged the effort needed for this, and since then > I presented an update on this at the RIPE meeting, see slide 4 here: > https://ripe70.ripe.net/wp-content/uploads/presentations/164-ripe70-db-wg-new-functionality.pdf > > We are *nearly* done. We have a bit over 100 aut-num objects to work > on (as compared to 2000 in May). > > When this is fully done, we can present an implementation plan for > this soon, within a few weeks. Before we do so, I would like to ask > the working group for direction on the following. Because sadly, > stopping enforcing this is not as trivial as it might seem. > > Option a: Leave existing cases, "descr:" mandatory, update request forms > ======================================================================== Option A sounds simplest to me, I am confident people will continue to update the "descr:" to align it with reality in a meaningful way. Kind regards, Job
- Previous message (by thread): [db-wg] NCC still enforcing descr: content
- Next message (by thread): [db-wg] NCC still enforcing descr: content
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]