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/members-discuss@ripe.net/
[members-discuss] NCC changing descr fields
- Previous message (by thread): [members-discuss] NCC changing descr fields
- Next message (by thread): [members-discuss] NCC changing descr fields
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Paul Civati
paul at racksense.com
Wed Jun 3 14:52:34 CEST 2015
On 3 Jun 2015, at 13:32, Daniel Stolpe wrote: > What causes confusion is probably that it used to be mandatory to have the "descr:" field be exactly the org name of the holder, until the NCC very recently realised that since the "org:" pointer is now mandatory, demanding the same date in "descr:" was not needed any more. > > So be patient, and you should be able to put whatever you like there. Hopefully. So I have since found out.. The object in question, has been like this for ~10 years though, and only now they are proposing changing it for a reason that is due to be shortly phased out. Bizarre! At any rate, this confusion would have been avoided if they hadn't sent out such a vague communication. A sentence or two might have covered it. Regards, Paul. -- Paul Civati <paul(at)racksense.com> 0870 321 2855 Rack Sense Ltd - Managed Service Provider - www.racksense.com
- Previous message (by thread): [members-discuss] NCC changing descr fields
- Next message (by thread): [members-discuss] NCC changing descr fields
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]