Tobias, all,
> I suggest going through a typical policy text step by step and as warm
> up starting with the "Summary of Proposal", the "Summary of a current
> problem" and the situation on other RIRs.
i think this was a good wake-up call, but not the ideal way to get to
a deliverable text.
> Currently within the RIPE region, the biggest problem for network
> operators is to know the best place to publish abuse contact information
> (irt, "abuse-mailbox:", "remark-fields:", and in addition to that, in
> which object they should publish them?). On the other hand abuse
> reporting parties having a huge problem with finding a correct abuse
> contact in the variety of possibilities.
I disagree with this part of the problem statement, at least i consider it
vastly exaggerated. A (non-representative) poll among a large number of
German (speaking) CSIRTs did not confirm that they felt any problems
making them selves known as "in charge" for their constituency.
We need to frame the different target audiences to justify the proposal
and gain support (and, actually, to design it well in the first place).
With that, we need to differentiate between the means of the DB itself,
which is DB objects, attributes, and rules and methods for links between
these as well as ways to frame queries and deliver responses.
> This proposal will help to stop uncontrolled growth and solves the above
> mentioned problems.
... and we should refrain from too ambitious promises.
-Peter

The RIPE NCC uses cookies. Some of these cookies may have been set already. More information about our cookies can be found in our privacypolicy. You can accept our cookies either by clicking here or by continuing to use the site.