Amsterdam, 13 September 2000
Agenda:
A Administrative stuff
- appointment of scribe
(Vesna Manojlovic)
- list of attendees
- agenda bashing
B Status of 6bone
(David Kessens)
http://www.kessens.com/~david/presentations/
C RPSL & IPv6
(Joachim Schmitz, routing-wg chair)
There is a need to include ipv6 in the routing registries on the
functional level. In the routing-wg , ipv6 is being looked into. There
is still a question of whether we need separate ipv6 Routing Registry.
There are specific issues to be dealt with. There is RPSL, but it is
developed for IPv4. It is suited to describe routing policies and
protocols. We designed a proposal for RIPE NCC activity plan to take
care of RR for IPv6. Central and structured approach with RPSL are
some of the requirements. Proposal includes development of RPSL
definitions and needs to include them into RIPE database. I would like
to invite you to take part in it.
Q: Was the document sent to the list?
A: Not, so far. I do not see any reason not to do it.
D IP Transition Strategies
(Alain Durand, co-chair of the IETF NGtrans WG)
http://www.ripe.net/ripe/meetings/archive/ripe-37/presentations/RIPE37/index.html
Toolbox for transition mechanisms is developed:
- networks
1. ipv6 as layer3 protocol
2. ipv6 over ipv4
3. tunnels (automatic, 60ver4, configured, tunnel broker, 6to4)
- stacks
hybrid, not dual
- applications
- some interoperability is needed
- tools (translators, DSTM)
E News from IPv6 Forum
(Juergen Rauschenbach)
http://www.ripe.net/ripe/meetings/archive/ripe-37/presentations/jr-IPv6ripe37/index.html
F Addressing plan of the real world
F1: IPv6 address plan at DFN
(Juergen Rauschenbach)
http://www.ripe.net/ripe/meetings/archive/ripe-37/presentations/dfn-v6-adr/index.html
Q: As a private person, can I participate in the dial-up part of it?
A: We have contractual partners, but for the testing purposes we may
discus it - to allow you to take part.
Q: Native or tunnels?
A: Initially - tunnels, just for universities to try out.
Q: What kind of routing equipment?
A: cisco, and [...] but we want to go for cisco-based solutions.
F2: Deploying a IPv6 Backbone
(Bernard Tuy, Renater)
Q: Why did you use /126 for tunnel?
A: Cisco.
Q: Question to RIPE NCC: are you going to implement the ipv6 root
name server?
Wilfried Woeber: group of people is working on making one of the
name servers ipv6 "compatible".. There are still problems with
resolver libraries, clients.. lost capability to use ipv6 transport
for DNS. There is no resolver in bind9.
We have subTLAs. We want them in the real world. We do need routing
registry.
G IPv6 connectivity in the terminal room
(Monica Cortes, RIPE NCC)
If you have IPv6 configured on your laptop, and are connected to LAN
here, you can use IPv6.
In September 99 we had tunnel to 6bone. (surfnet) January: Intel,
bsdi, tunnel - straightforward. applications not smooth. May: In
Budapest, moving the box - Solaris 8 , intel; tunnel to ncc, from
there to surfnet. there was a tutorial there, showing the setup of
tunnel. there was an ipv6 only box, able to connect to the internet
through that tunnel.
Next time we will have a nameserver. Now we have a web server...
H v6 native exchange points
- INXS (Muenich)
- AIX
from october 2000
- LINX
plans to provide ipv6 exchange in 2000
I European developments, initiatives...
(input from the audience)
no input this time
J Future plans for the working group
(input from the audience)
Chair: 6over4, 6to4... a lecture
Would people appreciate that? Little tutorial?
Bernard Tuy - very good idea.
Chair: OK, one volunteer?!?
People who did IPv6 tutorial last time want to do it next time, too
& v6 demo setup in terminal room
Bernard: 50-60 people were attending, and nobody at demo. Disappointing.
Chair: we need more publicity, to let people know what is going on.
Any more topics?
Wilfried Woeber: v6 DNS.
Z AOB
nothing