On Wed, Aug 12, 2015 at 08:43:50PM +0200, denis wrote:
Another point just crossed my mind. The "descr:" attribute is mandatory in the following object types: inetnum inet6num aut-num route route6 various set objects
Was the first "descr:" attribute in all these object types constrained to represent the organisation?
From the above list only in inetnum, inet6num, aut-num. In route and route6 it can be whatever you want but the presence of the 'descr:' attribute is mandatory.
If not which ones was it constrained in, which ones are you going to make it optional in and which are going to be 'cleaned up'?
As I understood 'option B' the clean-up would happen for "descr:" lines which were/are enforced, if they aren't enforced then we can assume the data is what the End User wants it to be, and there would be no need to touch such lines.
As for what does a description mean in any/each of these object types I will leave that to the more operationally minded people in the community. But I think it would be good to clarify what it does mean in each object type as this has never been defined before.
For me as operator, I think I'd like "descr:" to be a one-line description what the object is about. If an organisation has many aut-nums, it would be beneficial if there is one line which describes the differences between all those aut-nums by providing a one-line summary. Because of "org:" I can programmatically follow which organisation it belongs to, but some more meta-data might be useful. Thoughts? Kind regards, Job