[ipv6-wg at ripe.net] Draft (v1) IPv6 WG minutes RIPE 48

Please see below for the draft minutes of RIPE 48. The minutes will be
declared final at the next meeting if no substantial comments that
require a revision of the minutes are received before next working
group session at RIPE 49.

I hope this helps,

David Kessens
---

Draft (v1) IPv6 Working Group Minutes RIPE48 

When:   14:00 - 18:00, Wednesday May 5, 2004
Where:  Grand Ballroom, Hotel Krasnapolsky, Amsterdam

A. Administrative stuff
   - appointment of scribe: Timothy Lowe, RIPE NCC
   - agenda bashing
   
   ACTIONS
   
   - Chair, ask the mailing list if this document should
     become a RIPE document
     http://ip6.de.easynet.net/ipv6-minimum-peering.txt
   
   - Community, provide feedback update on larger then default v6
     allocations
   
   - Pim van Pelt (BIT BV) is looking for people who would
     like to run public 6to4 relays 
     e-mail:       pim at bit.nl or pim at ipng.nl

   
B. Global IPv6 routing table status
   (Gert Doering, SPACENET)
   <http://www.space.net/~gert/RIPE/R48-v6-table/>

   The rate of growth in IPv6 allocations is tapering off.

   There is public data available on the difference between allocated
   IPv4 space and BGP routed IPv4 space here:

   <http://bgp.potaroo.net/index-ale.html>

   This site contains a number of reports on the status of the IPv4
   address space, together with some observations about its trends in
   consumption of this resource.


C. "per country view" about IPv6 allocation on the RIPE/NCC   
   (Carlos Friacas, FCCN)
   <http://www.ip6.fccn.pt/v6top.html>


D. Report(s) about *actual* v6 traffic volume as compared to v4?
   *what's real* out there, not what's on powerpoint?
      (input from the audience)
   
   Questions: Pim van Pelt, BIT BV - 
                          6to4 public relays are at 80 Mbs
			  sustained. We would like people who
			  want to run public 6to4 relays to
			  
			  contact us: pim at bit.nl or pim at ipng.nl


E. Raising RPSLng Awareness
   (Carlos Friacas, Simon Leinen and Joao Damas, ISC)

   The RPSLng protocol draft is nearing completion
   (http://www.radb.net/rpslng.html)


F. Discussion of:
   http://ip6.de.easynet.net/ipv6-minimum-peering.txt

   Should this document become a RIPE document?
   ACTION on Chair - to take this to the mailing list


H. Latest IPv6 Land Speed Record
   (Edoardo Martelli, CERN)
   <http://www.ripe.net/ripe/meetings/ripe-48/presentations/ripe48-ipvy-lsr.pdf>- 15:08


G. IETF multi6 update
   (Kurtis Erik Lindqvist, Netnod Internet Exchange)

   There are two main camps in this discussion:
   Dividing the Identifier and addressing functions of the IP by 
   a.) Using identifier tokens
   b.) Lightweight version without ID token distribution


I. What are the deployment plans behind the larger then
   default ipv6 allocations
   (Jordi  Palet Martinez as a liaison for Vodafoon)

   ACTION on Chair 	- keep this agenda point as an ongoing action.
   ACTION on community 	- send feedback for next RIPE meeting


J. IPv6 home automation
   (Palet Jordi, Consulintel)

   There is a commercial powerline connectivity service operating in
   Zaragoza Spain. Currently in IPv4 but possibly in IPv6 in future.


K. (brief) update from the RIPE NCC on ipv6 enabled services
   (Andrei Robachevsky, RIPE NCC)

   Verbal: These services are IPv6 enabled: DNS, whois, ttm, plan, new
   webserver, K root.


N. Input for the RIPE NCC Activity Plan
   (input from the audience)
   NONE


M. Developments/initiatives regarding IPv6 in the RIPE region and beyond
   (input from the audience)
   NONE


L. IPv6 network management - IETF MIBs status, NetFlow v9, SNMPv6, and
   monitoring tools
   (Bernard Tuy - RENATER)


K. AOB

   Skidder ip mapping tool for topology research. Trying to do this in
   v6 www.caida.org/~mjl/