From brian.nisbet at heanet.ie Tue Jul 5 18:25:32 2011 From: brian.nisbet at heanet.ie (Brian Nisbet) Date: Tue, 05 Jul 2011 17:25:32 +0100 Subject: [acm-tf] Mailing list archives? In-Reply-To: <4E00C51D.6020708@heanet.ie> References: <4DFA4007.4080504@tana.it> <4E00C51D.6020708@heanet.ie> Message-ID: <4E133AFC.5030404@heanet.ie> Colleagues, "Brian Nisbet" wrote the following on 21/06/2011 17:21: > "Alessandro Vesely" wrote the following on 16/06/2011 18:40: >> There seems to be no archive page for this list in >> http://www.ripe.net/ripe/maillists/archives/. > > The mailing list archives will be made public, but the lovely NCC Ops > folk tell me that it will take a while, so I don't have an estimated > completion time just yet. The archives are now online here: http://www.ripe.net/ripe/maillists/archives/acm-tf/ Regards, Brian. From vesely at tana.it Wed Jul 6 11:18:34 2011 From: vesely at tana.it (Alessandro Vesely) Date: Wed, 06 Jul 2011 11:18:34 +0200 Subject: [acm-tf] Mailing list archives? Thanks! In-Reply-To: <4E133AFC.5030404@heanet.ie> References: <4DFA4007.4080504@tana.it> <4E00C51D.6020708@heanet.ie> <4E133AFC.5030404@heanet.ie> Message-ID: <4E14286A.2080807@tana.it> On 05/Jul/11 18:25, Brian Nisbet wrote: > > The archives are now online here: > > http://www.ripe.net/ripe/maillists/archives/acm-tf/ Great! The archive comprehensively starts from msg00000 that you wrote on Tue, 08 Mar 2011 10:05:36 +0000. Many thanks to you and the operators who did it! From vesely at tana.it Fri Jul 15 20:01:23 2011 From: vesely at tana.it (Alessandro Vesely) Date: Fri, 15 Jul 2011 20:01:23 +0200 Subject: [acm-tf] Whois-related work: WEIRDS Message-ID: <4E208073.7020004@tana.it> Hi all, let me just signal the existence of this mailing list, which may become a IETF WG. They seem to discuss about functionality of WHOIS, possibly through XML or JSON tools. They cover rate limiting along with authentication, access control, and more, including schemata. These seem to be pretty close to the topic we are discussing. I think we should evaluate the possibility of coordinating with them. It may be interesting to browse their documents: Requirements For Internet Registry Services http://tools.ietf.org/html/draft-kucherawy-weirds-requirements The RIPE Database REST API http://tools.ietf.org/html/draft-fiorelli-weirds-rws ARIN's RESTful Web Service for Whois Data http://tools.ietf.org/html/draft-newton-weirds-arin-whoisrws A RESTful Web Service for Domain Name Registration Data (RWS-DNRD) http://tools.ietf.org/html/draft-sheng-weirds-icann-rws-dnrd and their mailing list archives: http://www.ietf.org/mail-archive/web/weirds/ From denis at ripe.net Tue Jul 19 13:08:06 2011 From: denis at ripe.net (Denis Walker) Date: Tue, 19 Jul 2011 13:08:06 +0200 Subject: [acm-tf] Fwd: [arin-announce] Abuse Contact to be Mandatory per Policy 2010-14 Message-ID: <4E256596.5020907@ripe.net> Hi all This may be of interest. Regards Denis Walker Business Analyst RIPE NCC Database Group -------- Original Message -------- Subject: Fwd: [arin-announce] Abuse Contact to be Mandatory per Policy 2010-14 Date: Mon, 18 Jul 2011 18:13:39 +0000 From: John Curran To: nanog at nanog.org References: <4E2451E1.8070904 at arin.net> This is a significant change that all NANOG folks should be aware of... FYI, /John Begin forwarded message: From: ARIN > Date: July 18, 2011 11:31:45 AM EDT To: arin-announce at arin.net Subject: [arin-announce] Abuse Contact to be Mandatory per Policy 2010-14 ARIN is preparing to implement Policy 2010-14: Standardize IP Reassignment Registration Requirements. Once this policy is implemented, all new Organization registration records (Org IDs) will need to include an Abuse POC (in addition to the already required Admin and Tech). ARIN Online, REST, and templates are all being modified to enforce this new policy requirement Existing Org IDs will also need to comply with this rule. If an existing Org ID does not have an Abuse POC already listed, the existing Tech POC (s) will also become the Abuse POC(s) by default. This policy will be implemented no later than 30 September 2011. We strongly urge all customers to review and update their organization information data, and to add an Abuse POC if one is not currently listed. Again, if a new Abuse POC is not added to the record, the existing Tech POC (s) will also become the Abuse POC(s) by default. If there are any questions, please contact the Registration Services department at hostmaster at arin.net. Regards, Leslie Nobile Director, Registration Services American Registry for Internet Numbers _______________________________________________ ARIN-Announce You are receiving this message because you are subscribed to the ARIN Announce Mailing List (ARIN-announce at arin.net). Unsubscribe or manage your mailing list subscription at: http://lists.arin.net/mailman/listinfo/arin-announce Please contact info at arin.net if you experience any issues. _____ NANOG mailing list NANOG at nanog.org https://mailman.nanog.org/mailman/listinfo/nanog From tk at abusix.com Wed Jul 20 14:55:13 2011 From: tk at abusix.com (Tobias Knecht) Date: Wed, 20 Jul 2011 14:55:13 +0200 Subject: [acm-tf] Fwd: [arin-announce] Abuse Contact to be Mandatory per Policy 2010-14 In-Reply-To: <4E256596.5020907@ripe.net> References: <4E256596.5020907@ripe.net> Message-ID: <4E26D031.4020007@abusix.com> That is interesting. Thanks for sharing. Tobias Am 19.07.11 13:08, schrieb Denis Walker: > Hi all > > This may be of interest. > > Regards > Denis Walker > Business Analyst > RIPE NCC Database Group > > -------- Original Message -------- > Subject: Fwd: [arin-announce] Abuse Contact to be Mandatory per Policy > 2010-14 > Date: Mon, 18 Jul 2011 18:13:39 +0000 > From: John Curran > To: nanog at nanog.org > References: <4E2451E1.8070904 at arin.net> > > This is a significant change that all NANOG folks should be aware of... > > FYI, > /John > > Begin forwarded message: > > From: ARIN > > Date: July 18, 2011 11:31:45 AM EDT > To: > arin-announce at arin.net > Subject: [arin-announce] Abuse Contact to be Mandatory per Policy 2010-14 > > ARIN is preparing to implement Policy 2010-14: Standardize IP > Reassignment Registration Requirements. > > Once this policy is implemented, all new Organization registration > records (Org IDs) will need to include an Abuse POC (in addition to the > already required Admin and Tech). ARIN Online, REST, and templates are > all being modified to enforce this new policy requirement > > Existing Org IDs will also need to comply with this rule. If an existing > Org ID does not have an Abuse POC already listed, the existing Tech POC > (s) will also become the Abuse POC(s) by default. > > This policy will be implemented no later than 30 September 2011. We > strongly urge all customers to review and update their organization > information data, and to add an Abuse POC if one is not currently > listed. Again, if a new Abuse POC is not added to the record, the > existing Tech POC (s) will also become the Abuse POC(s) by default. > > If there are any questions, please contact the Registration Services > department at hostmaster at arin.net. > > Regards, > > Leslie Nobile > Director, Registration Services > American Registry for Internet Numbers > > > > _______________________________________________ > ARIN-Announce > You are receiving this message because you are subscribed to > the ARIN Announce Mailing List > (ARIN-announce at arin.net). > Unsubscribe or manage your mailing list subscription at: > http://lists.arin.net/mailman/listinfo/arin-announce > Please contact info at arin.net if you experience any > issues. > _____ > NANOG mailing list > NANOG at nanog.org > https://mailman.nanog.org/mailman/listinfo/nanog > > -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 267 bytes Desc: OpenPGP digital signature URL: From vesely at tana.it Fri Jul 29 11:59:04 2011 From: vesely at tana.it (Alessandro Vesely) Date: Fri, 29 Jul 2011 11:59:04 +0200 Subject: [acm-tf] Fwd: [arin-announce] Abuse Contact to be Mandatory per Policy 2010-14 In-Reply-To: <4E26D031.4020007@abusix.com> References: <4E256596.5020907@ripe.net> <4E26D031.4020007@abusix.com> Message-ID: <4E328468.7030502@tana.it> On 20/Jul/11 14:55, Tobias Knecht wrote: > That is interesting. Thanks for sharing. >> -------- Original Message -------- >> Subject: Fwd: [arin-announce] Abuse Contact to be Mandatory per Policy 2010-14 >> >> Existing Org IDs will also need to comply with this rule. If an existing >> Org ID does not have an Abuse POC already listed, the existing Tech POC >> (s) will also become the Abuse POC(s) by default. The only advantage I can see of making this POC mandatory is for automating outgoing abuse reports. The same advantage can also be achieved at the level of a RIPE-hosted tool for retrieving such POC, without the accompanying disadvantage of inserting spurious data into the database. For a provoking example, when the POC-retrieval tool finds no abuse POC in the database, it could instead return the string RIPE-missing-abuse-POCs at anti-abuse-volunteers.org Complaints reaching such mailbox would just get suitably counted, sorted, and checked. Statistical results might as well be made publicly available. I don't think finding volunteers to run such job would be much of a problem, if RIPE NCC didn't want to do it itself. jm2c