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] @EXT: RE: working in new version of 2019-04 (Validation of "abuse-mailbox")
- Previous message (by thread): [anti-abuse-wg] @EXT: RE: working in new version of 2019-04 (Validation of "abuse-mailbox")
- Next message (by thread): [anti-abuse-wg] @EXT: RE: working in new version of 2019-04 (Validation of "abuse-mailbox")
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Elvis Daniel Velea
elvis at velea.eu
Fri Jan 17 08:35:55 CET 2020
Hi, On 1/16/20 09:14, Volker Greimann wrote: > Clearly you have never looked at what normal end users put in the Org > fields. In our experience, they put anything in there, not just org > names. There simply is no good way to identify which org field shows > personal information which must be protected and which does not. You could make a bit of an effort and override that field with the data from the registration documents used to register the domain (if the data inserted by the end user is not right). > As I said, we'd be happy to publish non-personal information, if we > can be sure it is that. Ask RIPE NCC how they are doing it... as far as I know, all (*) organisation org-name: attributes are maintained by the RIPE NCC *all those that have any kind or resource assigned or allocated by the RIPE NCC /elvis
- Previous message (by thread): [anti-abuse-wg] @EXT: RE: working in new version of 2019-04 (Validation of "abuse-mailbox")
- Next message (by thread): [anti-abuse-wg] @EXT: RE: working in new version of 2019-04 (Validation of "abuse-mailbox")
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]