<br><tt><font size=2>Cooperation Working Group<br>
Thursday, 30 October 2008, Dubai<br>
<br>
A. Administrative Matters<br>
Patrik Fältström introduced himself as Chair for this meeting, as the <br>
two official Co-Chairs were unable to attend RIPE 57.<br>
<br>
He also noted some confusion about the name of the Jabber room.<br>
<br>
Two items were added to the agenda, under the A.O.B. item. These were <br>
presentations by Daniel Karrenberg and Jim Reid, and were added under <br>
A.O.B. as the Co-Chairs had already approved the existing agenda.<br>
<br>
Malcolm Hutty noted the closure of the Enhanced Cooperation Task <br>
Force, and its instruction for the Cooperation Working Group to <br>
maintain the document produced by the task force. Discussion of this <br>
matter was added as a third item under A.O.B.<br>
<br>
The participants in the room introduced themselves over the microphone.<br>
<br>
B. Open Comment/Review of Working Group Charter<br>
The Chair read out the charter in its current form.<br>
<br>
The participants endorsed the charter.<br>
<br>
C. Addressing the Rise of Criminal Service Providers - Paul Hoare, <br>
Serious Organised Crime Agency (SOCA)<br>
The speaker discussed the issue of criminal activity by Internet <br>
Service Providers and how it might be policed.<br>
<br>
Jim Reid raise a question about whether criminal ISPs could have <br>
their RIPE NCC membership terminated as a form of sanction, and how <br>
effective this would be as a deterrence, given that the ISP would <br>
already have the IP resources. Paul agreed that there remain issues, <br>
but that the RIPE NCC could remove reverse DNS services, and the <br>
ranges could be handed to a group such as a white-hat organisation <br>
who could also announce the ranges, which would degrade the <br>
connectivity of the criminal ISP. Jim also noted that there the <br>
routing database and the deployment of routing security could be a <br>
two-way street, in that the original holder (the criminal ISP) might <br>
have a certificate associated with those resources, making it <br>
difficult to disrupt their connectivity. Paul agreed that there were <br>
many issues, and encouraged anyone with further suggestions to <br>
contact him, noting that the RIPE NCC could provide his contact <br>
details. He also noted that if the Internet community could regulate <br>
this area successfully, it might remove the need or temptation for <br>
government to step in and regulate.<br>
<br>
Daniel Karrenberg noted the term "crime caused by the Internet",
and <br>
the danger of thinking that by fixing the Internet we can fix crime, <br>
whereas the Internet is simply a tool for certain crimes because it <br>
has enormous reach, it can rapidly disseminate material throughout <br>
the world and because it transcends jurisdictions. Technical <br>
solutions can only be a small part of a larger strategy in fighting <br>
crime. Paul agreed, noting that the Internet, like any technological <br>
development, presents new opportunities to criminals and we should <br>
try to restrict these opportunities.<br>
<br>
Daniel noted that the RIPE NCC's power is limited in terms of <br>
physically preventing criminal ISPs from using the Internet, but that <br>
this forum should be used to reach out to all ISPs, who collectively <br>
have the means to disable these rogue ISPs. He also noted that the <br>
RIPE NCC cannot be judge and executioner at the same time, but noted <br>
that SOCA is working with the Dutch law enforcement community in <br>
sorting this out. He emphasised that there should not be a focus on <br>
the RIPE NCC as the head of a hierarchical structure. Paul agreed and <br>
reiterated that he is primarily seeking suggestions and solutions.<br>
<br>
Jaap Akerhuis noted that in the domain name business there are also <br>
moves to have registries take down rogue sites, but that there is not <br>
a lot that can be done. Paul noted the large number of countries in <br>
the RIPE community and that gaining consensus from all these <br>
countries is difficult. There are issues of where free speech ends <br>
and crime begins. He reiterated the problems of cross-jurisdictional <br>
crime, though there are some crimes, such as pedophilia, that are <br>
widely accepted. He noted that there is no final solution to remove <br>
crime from the Internet, but that slowing them down is still an <br>
important goal.<br>
<br>
Malcolm Hutty noted that, supposing RIPE NCC could knock an ISP off <br>
the network, what kind of cooperation and approval would be necessary <br>
to obtain from national authorities in the relevant territory. He <br>
noted that several years ago UK CEOs were being arrested in the USA <br>
for gambling sites that were situated in the UK, and that there would <br>
be similar issues between countries within the RIPE region. Paul <br>
noted that in many cases SOCA would simply work with authorities in <br>
the relevant country, by approaching them and asking them to do <br>
something themselves.<br>
<br>
D. Update on RIPE NCC Outreach Activities<br>
RIPE NCC Government Roundtable Meeting, ICANN GAC and IGF 2008 <br>
preparations.<br>
<br>
There was no discussion.<br>
<br>
E. IPv6: What Should Governments Do? Patrik Fältström<br>
Patrik noted that the current deployment of IPv6 is not going well, <br>
what can be done about this and the role that government can play in <br>
that.<br>
<br>
There was no discussion.<br>
<br>
Z. A.O.B./Q&A Session<br>
<br>
Daniel Karrenberg – Presentation from the Address Policy Working <br>
Group on Address Depletion Scenarios<br>
Daniel pointed the WG to some work being done in the Address Policy <br>
WG on policies about the end of IPv4. He asked whether governments <br>
were concerned about the scenarios that were raised in his presentation.<br>
<br>
Jim Reid noted that in terms of "perceived unfairness", some
<br>
governments in the region are actually saying that there is already <br>
unfairness in the distribution of IP addresses.<br>
<br>
Nurani Nimpuno noted that there are policy proposals in the works <br>
that address these issues in various ways, and that governments <br>
should be aware that this is not an issue that is being neglected. <br>
Daniel agreed that there are proposals that address part of this <br>
issue, but not all of it.<br>
<br>
Jim Reid - NTIA Open Consultation About Signing of the Root - Report <br>
on Work Being Done in the DNS Working Group<br>
Jim noted that the US Department of Commerce has asked for comments <br>
about signing the DNS root zone, and the DNS Working Group is <br>
preparing a statement, as they have in the past pushed for this. The <br>
WG has nearly completed this statement, and hopes to present it at <br>
the Closing Plenary, and that this can then be accepted as a RIPE <br>
community statement. It states basically that this is about the <br>
authenticity of the data in the DNS root, not about some overt form <br>
of control.<br>
<br>
There was no discussion.<br>
<br>
Enhanced Cooperation Task Force Document – What To Do?<br>
Malcolm noted that the document created by the Enhanced Cooperation <br>
Task Force (EC TF) consists of two parts, one recommending the <br>
establishment of this Working Group, the other explaining how the <br>
RIPE community works, what bottom-up governance is and why we have <br>
these processes in place. It is essentially a communications <br>
document. It was decided that a statement from the RIPE community to <br>
this effect would be useful to underpin the current system. It is now <br>
hoped that this document could go through the appropriate RIPE PDP <br>
steps to become a RIPE Document.<br>
<br>
Rob Bokzijl noted that there is no need for any further formalities <br>
as the document has gone through the appropriate RIPE Task Force <br>
steps. Paul Rendek noted that any revisions should be showcased in <br>
this Working Group.<br>
<br>
Action point: The RIPE NCC is directed to create a new RIPE Document <br>
and place it on the WG website. Malcolm is appointed as the contact <br>
for any final edits.<br>
<br>
<br>
Meeting closed.<br>
</font></tt>
<br>
<br>
<br><font size=2 face="sans-serif">/Maria</font>