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] centralized abuse whois
- Previous message (by thread): [anti-abuse-wg] centralized abuse whois
- Next message (by thread): [anti-abuse-wg] centralized abuse whois
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Leo Vegoda
leo.vegoda at icann.org
Thu Jun 20 15:33:59 CEST 2013
Hi Frank, Frank Gadegast wrote: [...] > > We could implement an active referral service if there was strong > > demand > > for it. > > The problem is how to estimate a demand for people, that are no "pros" > and have no idea, that they would probably like this central service. I wonder whether asking end users to report abuse is the right way to go. Would it not be more effective for the user to inform their service provider that a message or event is abuse and rely on the service provider to do the right thing. After all, most people ask a mechanic to service their car rather than learn how to do that. [...] > > However, I wonder whether taping lots of whois servers together > > with web interfaces and scripting is the right way to go. As I > > understand > > it, the protocol being developed by the IETF's WEIRDS WG "SHOULD be > > able > > to deliver a reply that is effectively a referral or redirect to > > another > > server" as well as supporting internationalised addresses and so > > forth. > > URL ? The requirements are here: http://tools.ietf.org/id/draft-kucherawy-weirds-requirements-04.txt and the charter is here: http://tools.ietf.org/wg/weirds/charters [...] > And involving groups and standards and all the like would end up > in an interface so complicated, that it isnt usefull for normal > people anymore, it will be full of options, explanations, dos > and donts, funny APIs based on pretty seldom standards and the like ... I believe that one of the requirements is that the protocols is simple and lightweight. > The more easy way would probably be: > - IANA tells the RIRs to implement a whois like the "whois -b" from RIPE > only reachable from IANAs servers (lets say until August ;o) > - IANA creates the new whois under abuse.iana.org, and referres the > queries and standarizes the output In this bottom-up world the policies and requirements are given to ICANN as the IANA functions operator. ICANN doesn't command the RIRs to perform specific tasks. If you want to place a requirement on ICANN and the RIRs along the lines above, you could go down the Global Policy route and ask the ASO AC to start a global policy process. Details here: http://archive.icann.org/en/aso/aso-mou-attachmentA-29oct04.htm Regards, Leo Vegoda -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 5475 bytes Desc: not available URL: </ripe/mail/archives/anti-abuse-wg/attachments/20130620/385e3a0c/attachment.p7s>
- Previous message (by thread): [anti-abuse-wg] centralized abuse whois
- Next message (by thread): [anti-abuse-wg] centralized abuse whois
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]