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/anti-abuse-wg@ripe.net/
[anti-abuse-wg] 2011-06 Discussion Period extended until 7 May 2012 (Abuse Contact Management in the RIPE NCC Database)
- Previous message (by thread): [anti-abuse-wg] 2011-06 Discussion Period extended until 7 May 2012 (Abuse Contact Management in the RIPE NCC Database)
- Next message (by thread): [anti-abuse-wg] 2011-06 Discussion Period extended until 7 May 2012 (Abuse Contact Management in the RIPE NCC Database)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Frank Gadegast
ripe-anti-spam-wg at powerweb.de
Mon Apr 16 15:57:52 CEST 2012
Marco Schmidt wrote: > Dear colleagues, Hello, I like to recommend the following change, from "The "abuse-mailbox:" attribute must be available in an unrestricted way via whois, APIs and future techniques." to "The "abuse-mailbox:" attribute for a given object must be available in an unrestricted way via whois, APIs and future techniques with a single request". because its not clear how the right abuse-mailbox field could be found for example via whois. It will be no help, if there is a first request needed to find the abuse-c and a second request to read the abuse-mailbox field. This could lead to reach limits, if either the access to the abuse-c field is limited or if there is no other method (like a new whois flag) to directly request the abuse-mailbox field from the abuse-c Somebody at the RIPE NCC told me last week, that they intend to integrate the abuse-finder-tool (wich will surely return the abuse-mailbox-field from the abuse-c in a preferred manner) into whois with a new option, if the proposal gets through, but it should be clearer in the proposal, that its intention is, to receive the value of the abuse-mailbox field with simply one request. Kind regards, Frank > > The text of RIPE Policy Proposal 2011-06, "Abuse Contact Management in > the RIPE NCC Database", has been revised based on community feedback > received on the mailing list. > > We published the new version (version 2.0) today, 16 April. As a result, > a new Discussion Phase is set for the proposal. > > Changes in version 2.0 include: > > - Overall rewording > - Description of the use of "abuse-c:" and "abuse-mailbox:" on differing > RIPE Database objects > - Removal of references to a transition period > > You can find the full proposal at: > https://www.ripe.net/ripe/policies/proposals/2011-06 > > We encourage you to review this RIPE Policy Proposal and send your > comments to<anti-abuse-wg at ripe.net> by 7 May 2012. > > Regards > > Marco Schmidt > on behalf of the Policy Development Office > RIPE NCC > > > > -- Mit freundlichen Gruessen, -- MOTD: "have you enabled SSL on a website or mailbox today ?" -- PHADE Software - PowerWeb http://www.powerweb.de Inh. Dipl.-Inform. Frank Gadegast mailto:frank at powerweb.de Schinkelstrasse 17 fon: +49 33200 52920 14558 Nuthetal OT Rehbruecke, Germany fax: +49 33200 52921 ======================================================================
- Previous message (by thread): [anti-abuse-wg] 2011-06 Discussion Period extended until 7 May 2012 (Abuse Contact Management in the RIPE NCC Database)
- Next message (by thread): [anti-abuse-wg] 2011-06 Discussion Period extended until 7 May 2012 (Abuse Contact Management in the RIPE NCC Database)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]