RIPE 48 Meeting Report
The RIPE 48 Meeting was held from 3 - 7 May 2004 at the Grand Hotel
Krasnapolsky, Amsterdam, the Netherlands. There were a total of 267
attendees comprised of the RIPE NCC membership, the RIPE community and
government representatives. Attendees also included representatives from
APNIC, ARIN, AfriNIC, LACNIC and ICANN.
HIGHLIGHTS
Highlights of RIPE 48 included an update on the Number Resource
Organization from Axel Pawlik, Managing Director, RIPE NCC; an open
discussion on the proposed Memorandum of Understanding (MoU) between the
Number Resource Organization and ICANN; the community consensus to create
an ENUM Working Group.
J. Scott Marcus, Transatlantic Fellow, The German Marshall Fund of the
United States, gave a presentation on the deployment challenges involved
with evolving the core of the Internet.
This presentation can be viewed at:
http://www.ripe.net/ripe/meetings/ripe-48/presentations/ripe48-plenary-marcus.pdf
The European Operators Forum (EOF) featured presentations on lawful
interception of IP traffic, managing a DoS attack, stable BGP routing,
strategies for IP traffic engineering, analysing the Internet Routing
Registries, IP Address Space and AS Number hijacking and applications of
Bidirectional Forwarding Detection (BFD).
EOF presentations can be viewed at:
http://www.ripe.net/ripe/meetings/ripe-48/presentations/index.html#eof
The RIPE NCC, FLAG Telecom, Amsterdam Internet Exchange and Interoute are
thanked for the support they provided to the meeting. Global Voice
Networks are thanked for the provision of the meeting Internet connectivity.
SUMMARY
ADDRESS POLICY WORKING GROUP
-
It was agreed that the issue of worldwide "shopping" for address space
needs to be carefully considered before adopting different IPv4 additional
allocation procedures (i.e. HD Ratio) in each region.
There were calls for the clarification and review of the initial
allocation criteria for IPv6 allocations. The RIPE NCC will propose a
rewrite of the IPv6 policy after the issue has been discussed in more
detail on the mailing list.
Address Policy Working Group presentations can be viewed at:
http://www.ripe.net/ripe/meetings/ripe-48/presentations/index.html#ap
DATABASE WORKING GROUP
It was agreed that the 'country:' attribute should be either removed or
be optional.
It was decided that the default behaviour of the RIPE Database will be
changed to return the Incident Response Team (IRT) object if available, in
order to make it easier for users to find relevant security contact
information.
Database Working Group presentations can be viewed at:
http://www.ripe.net/ripe/meetings/ripe-48/presentations/index.html#db
TEST TRAFFIC MEASUREMENT (TTM) WORKING GROUP
-
Three presentations were given by Test Box users that offered useful
tutorial information for all Test Box owners.
-
The Working Group Chair encouraged the RIPE NCC to investigate moving measurements
into the O/S kernel and/or to hardware.
-
It was noted that the RIPE NCC has lowered the annual TTM service fee
to 1000 euro/year for the first box, 500 euro/year for the second
to ninth
boxes and that a large company has offered to sponsor hardware for
non-profit, research institutes.
Test Traffic Working Group presentations can be viewed at:
http://www.ripe.net/ripe/meetings/ripe-48/presentations/index.html#tt
ANTI-SPAM WORKING GROUP
-
The community was asked to look at the Anti-Spam Working Group charter
and to suggest how it should be changed.
-
Fearghas McKay reported on the sender-pays stream and specifically on
the 'camram' proposal which uses a well-documented system for generating
cryptographic
signatures ('hashcash').
-
There was a proposal to establish a top level domain 'mail.' to be used
as a type of DNS white-listing service.
IPv6 WORKING GROUP
-
It was agreed that the Working Group Chair will seek consensus from
the Working Group on whether the Minimum Technical IPv6 Peering
Requirements (MIPP) document should become a RIPE document.
-
The community was asked to provide feedback on larger than default IPv6
allocations.
-
Pim van Pelt asked for members of the community who would like to run
public 6to4 relays.
IPv6 Working Group presentations can be viewed at:
http://www.ripe.net/ripe/meetings/ripe-48/presentations/index.html#ipv6
EIX WORKING GROUP
-
Kurtis Lindqvist presented his view from the IXP Customer View workshop.
-
Bijal Sanghani gave a presentation on the expectation an ISP has for
an IXP.
-
European IXPs gave an update about the latest developments,
including a
presentation on the shared experience of engineers when they migrated
their customers from one switch to another.
EIX Working Group presentations can be viewed at:
http://www.ripe.net/ripe/meetings/ripe-48/presentations/index.html#eix
DNS WORKING GROUP
-
It was agreed that the RIPE NCC will review the zone checks done
by the
reverse delegation robot.
-
DNS MODA was proposed by Jim Reid as a not-for-profit body
to work on
DNS protocol issues.
-
It was noted that the expansion of IPv6 makes the streamlining
of IPv6
direct and reverse DNS even more necessary.
DNS Working Group presentations can be viewed at:
http://www.ripe.net/ripe/meetings/ripe-48/presentations/index.html#dns ROUTING WORKING GROUP
-
It was agreed that the RIPE NCC should publish an IRR Toolset
maintenance schedule.
-
There was a presentation on some of the technical issues of
high-speed global roaming (flying an 802.11b wireless hot-spot at
around 900 km/hr
at
altitudes around 10km).
-
There was a presentation on BGPlay, a tool that visualises
Internet routing activity.
Routing Working Group presentations can be viewed at:
http://www.ripe.net/ripe/meetings/ripe-48/presentations/index.html#routing
RIPE NCC SERVICES WORKING GROUP
RIPE NCC Services Working Group presentations can be viewed at:
http://www.ripe.net/ripe/meetings/ripe-48/presentations/index.html#ncc-services
TECHNICAL SECURITY WORKING GROUP
-
There was a presentation on security aware resolvers
and discussion on
the requirements for them.
-
There was discussion on 'server-side' protocol bits
and the feeling that they are solid and ready for deployment;
it was noted that
validator/application communication and key-management issues need
work.
Technical Security Working Group presentations can be viewed at:
http://www.ripe.net/ripe/meetings/ripe-48/presentations/index.html#techsec
TUTORIALS
The RIPE NCC Training Team presented the RIPE NCC IP Request Tutorial.
It
explained address space assignment and allocation procedures in
the RIPE
NCC region:
http://www.ripe.net/ripe/meetings/ripe-48/tutorials/ip-request/index.html
RIPE 48 WEBCASTING AND ARCHIVES
During RIPE 48, the RIPE NCC held trials in collecting feedback
from
participants watching the webcast. The mediums used for this were
IRC and
Jabber.
Archives of presentations, webcasts and IRC/Jabber feedback from
RIPE 48
are available at:
http://www.ripe.net/ripe/meetings/ripe-48/sessions-archive.html
HOSTMASTER CONSULTATION CENTRE (HCC)
The RIPE NCC Hostmaster Consultation Centre was open at RIPE
48, allowing
RIPE NCC Members to discuss issues relating to their business directly
with RIPE NCC Hostmasters.
RIPE 48 REFERENCE PAGE
A complete list of RIPE 48 sessions, tutorials and presentations
can be
found at:
http://www.ripe.net/ripe/meetings/ripe-48/index.html
"
MEET & GREET"
The RIPE NCC's "Meet & Greet" was available for first-time
RIPE Meeting
attendees at RIPE 48. "Meet & Greet" introduces newcomers
to the meetings,
to key attendees from the RIPE community and to social events throughout
the week. More information can be obtained by contacting:
<meet-greet@ripe.net>.
RIPE 49
RIPE 49 will be held in Manchester, the United Kingdom, from 20
- 24
September 2004.
Information on RIPE 49 will soon be made available at:
http://www.ripe.net/ripe/meetings/ripe-49/
NEW LOCAL INTERNET REGISTRIES (LIRs)
Please note: New LIRs are entitled to two (2) free tickets to
attend a
RIPE Meeting. The tickets cover the meeting fee only and do not
apply to
the RIPE dinner, travel or hotel accommodation. More information
on the
new LIR tickets can be found at:
http://www.ripe.net/ripe/meetings/new-lir.html
For more information, contact <meeting@ripe.net>.
|