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/[email protected]/
[anti-abuse-wg] the mandatory abuse field
- Previous message (by thread): [anti-abuse-wg] the mandatory abuse field
- Next message (by thread): [anti-abuse-wg] the mandatory abuse field
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
lists at help.org
lists at help.org
Mon Jul 30 07:51:53 CEST 2012
I think you need to first develop 2 tables (working with other groups/RIR's). Across the top is the RIR's. The first tables should list the data fields and the second table list the queries and what data elements they return. Then you can see what the RIR's all have in common and explain the differences/reasons in the elements of the table. Then look at what is common among the RIR's and come up with a standard. Then you can focus on the individual elements and decide what to do with the eventual goal being a common standard among all RIR's. To get over the opt-in/opt-out law differences you could consider allowing "private" instead the real data, allow a link to a form web page rather than a contact person, or demand an opt-in agreement when the data is collected, etc.
- Previous message (by thread): [anti-abuse-wg] the mandatory abuse field
- Next message (by thread): [anti-abuse-wg] the mandatory abuse field
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]