Inactive Mailing Lists
Mailing List Search
The RIPE Accountability Task Force was formed in October 2016 following a presentation at RIPE 73. The Task Force examined the structures, documentation and processes of the RIPE community to ensure they provided high levels of accountability.
The Abuse Contact Management (ACM) Task Force proposes policies and procedures to maintain the accuracy of abuse contact information in the RIPE Database. To post a message to the list, email [email protected]
This was the Mailing List of the RIPE Anti-Spam Working Group.
At RIPE 52 in Istanbul, RIPE established a task force that promotes deployment of ingress filtering at the network edge by raising awareness and provide indirect incentives for deployment.
This now-obsolete list was for public discussion of the principles, structure, and implementation plan of the Address Supporting Organisation (ASO) of ICANN.
Since 2007, the RIPE NCC has been working on a community-driven system that will issue digital certificates along with the assignment or allocation of Internet number resources. This effort has been driven by the work being done by the RIPE Certification Task Force. Discussions about Resource Certification software and tools are held on this list.
A task force was established at RIPE 53 in Amsterdam to advise, review, and provide feedback about a certification system
This mailing list was created for the interconnection community after the discontinuation of the European Internet Exchange (EIX) Working Group. The aim is to create a charter for a new working group that will replace the EIX Working Group. Anyone can join this mailing list. The list has been archived since October 2013. Please note that only subscribers can post messages.
This was the mailing list of the RIPE Connectivity Working Group. This group is no longer active.
The db-beta mailing list was used to exchange information about the beta release of the RIPE Database software. The list membership is closed to beta testers. The list is archived since October 1993.
At the RIPE 52 Meeting in Istanbul, RIPE established a task force to work with the RIPE NCC Data Protection Team. The intention was to create procedures, modify policies (if required) and review documents that address data protection issues.
Announcements related to the RIPE Database.
The Database Help mailing list was for experienced users of the RIPE Database to assist others by sharing their knowledge and expertise.
A now inactive list created to discuss the migration of the RIPE Database in 2000.
The DNSMON Contact mailing list was for communicating issues to technical contacts of the TLD Administrators. All DNS-related issues should now be discussed on the DNS Working Group Mailing List at [email protected]
This was the mailing list for users of the DNSMON service. All DNS-related issues should now be discussed on the DNS Working Group Mailing List at [email protected]
The European Internet Exchange (EIX) Working Group provided a way for the RIPE community to follow the status and activities of Internet Exchange Points in the region. It was discontinued at the RIPE 67 Meeting in Athens in October 2013. The Connect BoF was established to discuss a charter for a potential new working group that would serve the needs of the interconnection community. These pages are maintained for archive purposes.
This was the mailing list of the RIPE European Operators Forum. This group is no longer active.
At RIPE 54 in Tallinn, the RIPE Task Force on Enhanced Cooperation was formed to advise on issues of enhanced cooperation between the RIPE community and relevant stakeholders, particularly governments and regulators.
The ENUM Request mailing list was previously used for for requests by organisations applying for an ENUM delegation. This list is no longer active and is an archive only.
The enum-trials mailing list has been replaced by the ENUM Working Group mailing list.
This was the Mailing List of the RIPE ENUM Working Group
This mailing list was for the RIPE community to send their comments on the ICANN Strategic Plan.
This list carried comments on the NRO Response to an ITU Proposal on IP number distribution.
The mailing list of the IRRTOOLSET has moved to < irrtoolset @ isc.org >. Existing subscribers have been moved to the new list.
This archived mailing list previously discussed development of the RIPE NCC LIR Portal and associated tools. This discussion now takes place on a number of other mailing lists, including the RIPE NCC Services Working Group.
The LIR Working Group mailing list was replaced by the RIPE Address Policy Working Group.
This was the mailing list of the RIPE MBONE Working Group. This is the RIPE mailing list for mbone operational matters.
A list that carried discussion and information about the now discontinued RIPE NCC MyASN service.
he NetNews working group coordinated news traffic to decrease the load on the backbones.
The RIPE Database Requirements Task Force shall develop a RIPE document listing requirements for the RIPE DB and their rationales.
This mailing list was a forum for participants of the RIPE NCC Regional Meeting, Middle East, Dubai,7 - 9 December 2003 and the RIPE NCC membership to discuss Internet recource allocation and Internet management issues in the Middle East. It has been replaced by the ncc-regional-middle-east mailing list.
This mailing list was previously for discussion of topics relating to RIPE NCC Middle East Regional Meetings. The list merged with the MENOG Discuss mailing list in 2011.
This mailing list was a forum for participants of the RIPE NCC Regional Meeting, Moscow, Russia, 16-18 June 2004 and the RIPE NCC membership to discuss Internet recource allocation and Internet management issues in the region. If you encounter problems with viewing the messages, try to select cyrillic font encoding in your browser. Go to view -> (character) encoding and select Cyrillic KOI-8R.
This mailing list was a forum for participants of the RIPE NCC Regional Meeting, Nairobi, Kenya, 28-30 July 2004 and the RIPE NCC membership to discuss Internet resource allocation and the Internet management issues in the region.
This list provided a forum for continued discussion of topics related to the RIPE NCC Regional Meeting in Qatar, January 2006. The list has been replaced by the ncc-regional-middle-east mailing list.
This mailing list was previously for discussion of topics related to RIPE NCC Russian Regional Meetings and is no longer active. The list merged with the ENOG Discuss mailing list in 2011.
This archived mailing list was for discussion of issues relating to the Ukrainian region and is no longer active. These discussions now take place on the ENOG Discuss mailing list.
This public mailing list was used for discussions in and input gathered by the editorial committee of the new policy draft document. This mailing list is no longer active.
A list that managed discussions around the set up of a RIS Route Collector at the London Internet Exchange.
This mailing list was aimed at discussion of the extensions to RPSL related to IPv6 and multicast. This mailing list was requested by the RIPE community during the IPv6 Working Group session at ripe-40
This was the mailing list of the Technical Security Working Group. This group is no longer active.
This now inactive list existed to discuss the early development of the RIPE NCC Test Traffic Measurement Service. It has been replaced since. First by the Test Traffic Working Group and in 2010 by the MAT Working Group.
The [email protected] list was intended for discussions related to the Test-Traffic Working Group.
The mailing list of the Top-Level-Domain (TLD) Working Group. The TLD Working Group has been replaced by the DNR Forum which has been merged with the DNS Working Group
This was the mailing list of the Tools Working Group. The Tools Working Group has been replaced by the RIPE NCC Services Working Group. This group is no longer active.
During RIPE 19, Stefan Biesbroeck initiated a BOF on Trouble Ticket Systems. This now inactive list was set up to manage discussions.
A short-lived and now inactive list created to discuss details of Whois software development.