- ipv6-wg - mailman.ripe.net

[ipv6-wg@ripe.net] Call for Papers - Next Global IPv6 Summit in Spain
by JORDI PALET MARTINEZ 07 Feb '05

07 Feb '05

Hi all, As indicated in the email below, the next Global IPv6 Summit in Spain, the bigger IPv6 European event, in its 4th edition (after a very successful organization and broad international attendance in 2001, 2002 and 2003), will be organized this time in Barcelona, next June 2005, with a expected audience over 2.600 key decisions makers from ICT sectors. The main target of the event is business oriented talks, as well as talks oriented to policy makers, information/knowledge society, education and public sectors. This Call for Papers doesn't require that you submit a complete paper (which is welcome also), but instead, a short plain text abstract of your presentation topic, by email. Talks regarding deployment experiences, new services and applications will be of key interest for the expected attendance, and hence highly encouraged. We believe that key topics will be also those regarding: 1) IPv6 and business 2) IPv6 and Broadband 3) New IPv6-based services and applications 4) IPv6 and the Digital Home 5) IPv6 and Multimedia, Voice/Video applications 6) IPv6, Mobility, Wireless and 3G 7) IPv6 and Ambient Intelligence/Ubiquitous Computing/Distributed Systems 8) IPv6 and GRIDs 9) IPv6 and logistics, transport and eSafety 10) IPv6 for eHealth, eGoverment, eLearning and other "e-whatever" 11) IPv6 and gamming 12) IPv6 and peer-to-peer 13) IPv6 and security 14) IPv6 and Open Source 15) IPv6 and marketing/branding Also topics regarding Standards, Research, Development and Innovation experiences are welcome, including R&D projects results. The Agenda will be drafted early in March, so the dead-line for submitting your topic is only until 25th February, but as said only a short abstract is required. If you're interested in participating, or you have any special idea, even if your topic is not in the list above, please don't hesitate to contact me (jordi.palet(a)consulintel.es) ASAP, so we can work out any options. Regards, Jordi PS: Please, feel free to circulate this email among your contacts. ------ Mensaje reenviado De: JORDI PALET MARTINEZ <jordi.palet(a)consulintel.es> Responder a: <jordi.palet(a)consulintel.es> Fecha: Mon, 07 Feb 2005 18:25:42 +0100 Para: "members(a)ipv6forum.com" <members(a)ipv6forum.com>, <tf-sc(a)ipv6tf.org> Asunto: Next Global IPv6 Summit in Spain Hi all, As I already informed a few weeks ago, the next Global IPv6 Summit in Spain will be held this time in Barcelona next June (instead of Madrid in March as previously forecasted). This will happen starting on June 6th, with a tutorial in the morning, the opening ceremony in the afternoon, with some keynotes and then 2-3 days of IPv6 conference, depending on the success of the call for papers. If required we can extend our event up to Friday 10th (total 4 days, plus opening ceremony, plus half day tutorial). In this occasion, we will try a completely new model, integrating the IPv6 conference in a bigger event, more business oriented, even when technical sessions will be still present. The "umbrella" event is Internet Global Congress (IGC), with has been organized in Barcelona already during the 6 previous years. The Internet Global Congress, the leading Internet and New Technologies congress in Spain, is organized by the Fundació Barcelona Digital, a non-profit organization, which also provides space for exhibition and delivers the IGC awards for Digital Innovation (aimed to students and professionals with embryonic Internet projects, aims to be a launch platform for all those people involved in research and innovation in the field of Internet and the New Technologies). IGC provides us all the infrastructure for organizing the Global IPv6 Summit track, and we only need to manage our own agenda, and consequently our own call for papers (see next email). They also they care about all the issues related to registration, proceedings and publicity, at no cost for us. We expect that this will be the bigger IPv6 event in Europe during 2005, with an expected attendance over 2.600 people, which of course, will be able to attend not just to the IPv6 track but also to other IT tracks (already depicted at http://www.igcweb.net, then click at Program). The attendance is mainly CTOs, CEOs and other key decision makers related to ICT, so its a very nice opportunity for IPv6 in Europe to meet a large audience which probably has not been in touch with IPv6 until now. I count with the support from all of you, and please do not hesitate to let me know any ideas that you may have to make an even more successful event that what for sure we will have in a so nice city as Barcelona. More information will be soon available at http://www.ipv6-es.com and http://www.igcweb.net. Regards, Jordi ********************************** Madrid 2003 Global IPv6 Summit Presentations and videos on line at: http://www.ipv6-es.com This electronic message contains information which may be privileged or confidential. The information is intended to be for the use of the individual(s) named above. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, including attached files, is prohibited.

1 0

Re: [ipv6-wg@ripe.net] Re: New IPv6 Address Block Allocated to RIPE NCC
by Wilfried Woeber, UniVie/ACOnet 19 Jan '05

19 Jan '05

>"ICANN folly that we're in the process of changing" >(and this has taken far too long already). I propose to suggest the phrase "this has taken far too long already" as the new trademark for IANA/ICANN operations... >Gert Doering > -- NetMaster Sorry, couldn't resist... Wilfried ( https://cert.aco.net/ ) [ not wearing any hat for this message, just typing as a regular network citizen] _________________________________:_____________________________________ Wilfried Woeber : e-mail: Woeber(a)CC.UniVie.ac.at UniVie Computer Center - ACOnet : Tel: +43 1 4277 - 140 33 Universitaetsstrasse 7 : Fax: +43 1 4277 - 9 140 A-1010 Vienna, Austria, Europe : RIPE-DB: WW144, PGP keyID 0xF0ACB369 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~:~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ...there's no place like 127.0.0.1 (or ::1/128 ?)

2 1

[ipv6-wg@ripe.net] New IPv6 Address Block Allocated to RIPE NCC
by leo vegoda 17 Jan '05

17 Jan '05

Dear Colleagues, The RIPE NCC received the IPv6 address range 2003:0000::/18 from the IANA in January 2005. You may wish to adjust any filters you have in place accordingly. More information on the IP space administered by the RIPE NCC can be found on our web site at: <https://www.ripe.net/ripe/docs/smallest-alloc-sizes.html> Regards, -- leo vegoda Registration Services Manager RIPE NCC

5 6

[ipv6-wg@ripe.net] Announcement: Policy Development Process in RIPE
by Rob Blokzijl 21 Dec '04

21 Dec '04

To the RIPE Community, later today I will publish a draft document that describes the policy making process in RIPE. It is draft, so your input is requested in order to come to a generally accepted final document. Logistics: - deadline for comments on the first draft: 1 Februari 2005 - discussion takes place on ripe-list(a)ripe.net - if you are not subscribed to ripe-list(a)ripe.net yet, go to http://www.ripe.net/mailman/listinfo/ripe-list#subscribers - for any questions, don't hesitate to contact chair(a)ripe.net As always, apologies for receiving multiple copies of this announcement. Best regards, Rob Blokzijl RIPE Chairman

2 1

[ipv6-wg@ripe.net] RPSLng in the RIPE Whois Database
by Shane Kerr 21 Dec '04

21 Dec '04

Dear Colleagues, Beginning Wednesday 29 December 2004, the RIPE Database will support RPSLng. RPSLng extends the Routing Policy Specification Language (RPSL) allowing description of IPv6 and multicast routing policies. It includes a new object type, ROUTE6, and new attributes, such as "mp-import:" and "mp-export:". RPSLng was submitted to the IETF to become an RFC. You can read the most recent draft at: http://www.radb.net/rpslng-08.html This change will not affect the current contents of the database. It is optional for any objects you maintain. The main differences for query users are as follows: - Currently a query for an IPv4 address or network may return INETNUM, ROUTE, and INET-RTR objects. A query for an IPv6 address or network can only return an INET6NUM object. After we put RPSLng into production, IPv6 queries will start to also return ROUTE6 and INET-RTR objects, if they are in the database. - Currently an inverse query (using the "-i" flag) for AUT-NUM objects may return ROUTE objects. After we put RPSLng into production, a query will return both ROUTE and ROUTE6 objects. If you want to limit your query, you can use the "-T" flag. For example, if you only want ROUTE objects returned to an inverse query, you can type: whois -h whois.ripe.net -T route -i origin AS3333 Please change your scripts if necessary. We will not move the contents of the RPSLng prototype Whois server to the RIPE Whois Database. You will have to create any objects that define your routing policy in the production RIPE Whois Database. You can update the RPSLng prototype Whois server until the start of January 2005. The query interface will be available until the end of January 2005. -- Shane Kerr Software Manager RIPE NCC

3 2

[ipv6-wg@ripe.net] New IPv6 Address Block Allocated to RIPE NCC
by leo vegoda 16 Dec '04

16 Dec '04

Dear Colleagues, The RIPE NCC received the IPv6 address range 2001:4C00::/23 from the IANA in December 2004. You may wish to adjust any filters you have in place accordingly. More information on the IP space administered by the RIPE NCC can be found on our web site at: <https://www.ripe.net/ripe/docs/smallest-alloc-sizes.html> Regards, -- leo vegoda Registration Services Manager RIPE NCC

1 0

[ipv6-wg@ripe.net] rootzone -> .com and .net in place :-)
by Carlos Friacas 29 Oct '04

29 Oct '04

Hi, Anybody noticed this? Connectivity still not that good to 2001:503:..., however, happy to have it in place :-) They "IPv6-ized" A and B (2 out of 13 servers). -------------------- ; <<>> DiG 8.3 <<>> @192.5.5.241 com ns ; (1 server found) ;; res options: init recurs defnam dnsrch ;; got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 6 ;; flags: qr rd; QUERY: 1, ANSWER: 0, AUTHORITY: 13, ADDITIONAL: 15 ;; QUERY SECTION: ;; com, type = NS, class = IN ;; AUTHORITY SECTION: com. 2D IN NS C.GTLD-SERVERS.NET. com. 2D IN NS D.GTLD-SERVERS.NET. com. 2D IN NS E.GTLD-SERVERS.NET. com. 2D IN NS F.GTLD-SERVERS.NET. com. 2D IN NS G.GTLD-SERVERS.NET. com. 2D IN NS H.GTLD-SERVERS.NET. com. 2D IN NS I.GTLD-SERVERS.NET. com. 2D IN NS J.GTLD-SERVERS.NET. com. 2D IN NS K.GTLD-SERVERS.NET. com. 2D IN NS L.GTLD-SERVERS.NET. com. 2D IN NS M.GTLD-SERVERS.NET. com. 2D IN NS A.GTLD-SERVERS.NET. com. 2D IN NS B.GTLD-SERVERS.NET. ;; ADDITIONAL SECTION: A.GTLD-SERVERS.NET. 2D IN A 192.5.6.30 A.GTLD-SERVERS.NET. 2D IN AAAA 2001:503:a83e::2:30 B.GTLD-SERVERS.NET. 2D IN A 192.33.14.30 B.GTLD-SERVERS.NET. 2D IN AAAA 2001:503:231d::2:30 C.GTLD-SERVERS.NET. 2D IN A 192.26.92.30 D.GTLD-SERVERS.NET. 2D IN A 192.31.80.30 E.GTLD-SERVERS.NET. 2D IN A 192.12.94.30 F.GTLD-SERVERS.NET. 2D IN A 192.35.51.30 G.GTLD-SERVERS.NET. 2D IN A 192.42.93.30 H.GTLD-SERVERS.NET. 2D IN A 192.54.112.30 I.GTLD-SERVERS.NET. 2D IN A 192.43.172.30 J.GTLD-SERVERS.NET. 2D IN A 192.48.79.30 K.GTLD-SERVERS.NET. 2D IN A 192.52.178.30 L.GTLD-SERVERS.NET. 2D IN A 192.41.162.30 M.GTLD-SERVERS.NET. 2D IN A 192.55.83.30 ;; Total query time: 12 msec ;; FROM: atlas.fccn.pt to SERVER: 192.5.5.241 ;; WHEN: Fri Oct 29 16:16:43 2004 ;; MSG SIZE sent: 21 rcvd: 509 ; <<>> DiG 8.3 <<>> @192.5.5.241 net ns ; (1 server found) ;; res options: init recurs defnam dnsrch ;; got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 6 ;; flags: qr rd; QUERY: 1, ANSWER: 0, AUTHORITY: 13, ADDITIONAL: 15 ;; QUERY SECTION: ;; net, type = NS, class = IN ;; AUTHORITY SECTION: net. 2D IN NS J.GTLD-SERVERS.net. net. 2D IN NS K.GTLD-SERVERS.net. net. 2D IN NS L.GTLD-SERVERS.net. net. 2D IN NS M.GTLD-SERVERS.net. net. 2D IN NS A.GTLD-SERVERS.net. net. 2D IN NS B.GTLD-SERVERS.net. net. 2D IN NS C.GTLD-SERVERS.net. net. 2D IN NS D.GTLD-SERVERS.net. net. 2D IN NS E.GTLD-SERVERS.net. net. 2D IN NS F.GTLD-SERVERS.net. net. 2D IN NS G.GTLD-SERVERS.net. net. 2D IN NS H.GTLD-SERVERS.net. net. 2D IN NS I.GTLD-SERVERS.net. ;; ADDITIONAL SECTION: A.GTLD-SERVERS.net. 2D IN A 192.5.6.30 A.GTLD-SERVERS.net. 2D IN AAAA 2001:503:a83e::2:30 B.GTLD-SERVERS.net. 2D IN A 192.33.14.30 B.GTLD-SERVERS.net. 2D IN AAAA 2001:503:231d::2:30 C.GTLD-SERVERS.net. 2D IN A 192.26.92.30 D.GTLD-SERVERS.net. 2D IN A 192.31.80.30 E.GTLD-SERVERS.net. 2D IN A 192.12.94.30 F.GTLD-SERVERS.net. 2D IN A 192.35.51.30 G.GTLD-SERVERS.net. 2D IN A 192.42.93.30 H.GTLD-SERVERS.net. 2D IN A 192.54.112.30 I.GTLD-SERVERS.net. 2D IN A 192.43.172.30 J.GTLD-SERVERS.net. 2D IN A 192.48.79.30 K.GTLD-SERVERS.net. 2D IN A 192.52.178.30 L.GTLD-SERVERS.net. 2D IN A 192.41.162.30 M.GTLD-SERVERS.net. 2D IN A 192.55.83.30 ;; Total query time: 8 msec ;; FROM: atlas.fccn.pt to SERVER: 192.5.5.241 ;; WHEN: Fri Oct 29 16:18:33 2004 ;; MSG SIZE sent: 21 rcvd: 506 ./Carlos -------------- http://www.ip6.fccn.pt/nativeRCTS2.html Wide Area Network (WAN) Workgroup, CMF8-RIPE, CF596-ARIN FCCN - Fundacao para a Computacao Cientifica Nacional http://www.fccn.pt "Internet is just routes (140068/465), naming (millions) and... people!"

2 1

[ipv6-wg@ripe.net] RPSLng database deployment?
by Bernhard Schmidt 20 Oct '04

20 Oct '04

Dear all, having missed the last RIPE meeting I'm unfortunately somewhat out of date regarding this, but could someone please enlighten me about the current plans for deployment of RPSLng in the regular RIPE database? I am using rpslng.ripe.net, but unfortunately almost noone else does. Running a network without any sustainable prefix authorization sucks quite hard, it is a real pain to have to contact your upstream by mail if you have a new prefix (besides other things). Are there any problems with RPSLng currently? Thanks Bernhard

9 13

[ipv6-wg@ripe.net] New IPv6 Address Block Allocated to RIPE NCC
by Filiz Yilmaz 18 Oct '04

18 Oct '04

Dear Colleagues, The RIPE NCC received the IPv6 address range 2001:4A00::/23 from the IANA in October 2004. You may wish to adjust any filters you have in place accordingly. More information on the IP space administered by the RIPE NCC can be found on our web site at: <https://www.ripe.net/ripe/docs/smallest-alloc-sizes.html> Regards, -- Filiz Yilmaz RIPE NCC

1 0

[ipv6-wg@ripe.net] IPv6 wg minutes RIPE48
by David Kessens 16 Oct '04

16 Oct '04

Please see below for the minutes of RIPE 48 as approved during the working group session in Manchester. Only a few minor typographical corrections were made compared to the draft minutes as posted earlier. I hope this helps, David Kessens --- 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(a)bit.nl or pim(a)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(a)bit.nl or pim(a)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 Vodafone, TeliaSonera and others) ACTION on Chair - keep this agenda point as an ongoing action. ACTION on community - send feedback for next RIPE meeting J. IPv6 home automation (Jordi Palet Martinez, Consulintel) There is a commercial powerline connectivity service operating in Spain, and other countries, which started with a big trial (3.000) in Zaragoza. Currently in IPv4 but possibly in IPv6 in future (some customers are using IPv6 but on experimental basis for the 6POWER project). 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/

1 0