- ipv6-wg - mailman.ripe.net

Call for agenda items for RIPE 64 in Ljubljana
by Marco Hogewoning 28 Feb '12

28 Feb '12

Dear colleagues, You guessed it, it is that time of the year again that we get busy to prepare for another RIPE Meeting., the 64th already. This one will take place from 16 till 20 April in Ljubljana, Slovenia. For this meeting we even have arranged for two sessions of the IPv6 Working Group. Both are scheduled on Thursday, starting after the coffee break at 11:00 and continuing after lunch until 15:30. This means we have a total of three hours to fill with topics you think are interesting when it comes to the adoption and deployment of IPv6. So please if you would like to share anything, wether it are thoughts about how to progress IPv6 deployment or showing your latest IPv6 project, please drop us a line at ipv6-wg-chairs (at) ripe (dot) net. Please include a short bio, a synopsis and if available a copy of the (draft) slides you intend to use. Hope to see you all in Ljubljana and of course if you can't make it the sessions will be broadcasted with the option of remote participation. Greetings, The IPv6 WG chairs collective, Marco, David and Shane

1 0

Policy proposal 2011-02: "Removal of Multihomed Requirement for IPv6 PI" Implemented
by Kjell Leknes 22 Feb '12

22 Feb '12

[Apologies for duplicate emails] Dear colleagues, We are pleased to announce that RIPE Policy Proposal 2011-02, "Removal of Multihomed Requirement for IPv6 PI", has been implemented. The RIPE NCC is now ready to accept requests for IPv6 PI assignments without multihoming being a requirement. The full proposal can be found at: http://www.ripe.net/ripe/policies/proposals/2011-02 The revised version of the IPv6 policy was published on 23 January 2012: http://www.ripe.net/ripe/docs/ripe-545 The new request form template for IPv6 PI assignments can be found at: https://www.ripe.net/ripe/docs/ripe-546/ The new supporting notes can be found at: https://www.ripe.net/ripe/docs/ripe-547/ Kind regards --- Kjell Leknes RIPE NCC

1 0

RIPE-501 replacement draft, version 7
by Jan Zorz ＠ go6.si 15 Feb '12

15 Feb '12

Fellow IPv6 working group... It is time to put out another version of RIPE-501 replacement draft document, and this time we are aiming for Last Call, if WG chairs decides so. We've been babysitting this doc for quite some time now, and many of latest changes and modifications are described in this post: http://go6.si/en/2012/02/ripe-501-replacement-ready/ Doc itself can be found in .pdf on http://go6.si/ripe501bis/ , find 7th revision (the last one). We'll also ask RIPE-NCC staff (Chris, actually) to HTML-ify it and put into documents store as a draft. It's time for 501 replacement. There is a long list of entities, that are waiting for this to move forward. We'll start collecting more suggestions and ideas for new work shortly, but I think the authors team needs some time off now ;) So, if chairs agree, let's try and ask, if there is consensus to move this draft in BCP status. Merike, Sander and Jan, authors

1 0

Fwd: RA-Guard: Advice on the implementation (feedback requested)
by Fernando Gont 02 Feb '12

02 Feb '12

Folks, You've proabably read about this a few times -- still, most implementations remain broken. If you care to get this fixed, please provide feedback about this I-D on the IETF *v6ops* mailing-list <v6ops(a)ietf.org>, and CC me if possible. Thanks! Best regards, Fernando -------- Original Message -------- Subject: RA-Guard: Advice on the implementation (feedback requested) Date: Wed, 01 Feb 2012 21:44:29 -0300 From: Fernando Gont <fgont(a)si6networks.com> Organization: SI6 Networks To: IPv6 Operations <v6ops(a)ietf.org> Folks, We have just published a revision of our I-D "Implementation Advice for IPv6 Router Advertisement Guard (RA-Guard)" <http://tools.ietf.org/id/draft-gont-v6ops-ra-guard-implementation-01.txt>. In essence, this is the problem statement, and what this I-D is about: * RA-Guard is essential to have feature parity with IPv4. * Most (all?) existing RA-Guard implementations can be trivially evaded: if the attacker includes extension headers in his packets, the RA-Guard devices fail to identify the Router Advertisement messages. -- For instance, THC's "IPv6 attack suite" (<http://www.thc.org/thc-ipv6/>) contains tools that can evade RA-Guard as indicated. * The I-D discusses this problem, and provides advice on how to implement RA-Guard, such that the aforementioned vulnerabilities are eliminated, we have an effective RA-Guard device, and hence feature-parity with IPv4. We'd like feedback on this I-D, including high-level comments on whether you support the proposal in this I-D. Thanks! Best regards, -- Fernando Gont SI6 Networks e-mail: fgont(a)si6networks.com PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492

1 0

Draft minutes of RIPE63
by Marco Hogewoning 31 Jan '12

31 Jan '12

Dear colleagues, Attached are the draft minutes of our working group session in Vienna at the RIPE63 Meeting. Please review them and if you have any corrections or comments, please post them to this list before Friday the 27th of January COB. If we haven't received any comments or corrections by that date, we will assume consensus and will ask the RIPE NCC to publish these as final. Again many thanks to the RIPE NCC for their support in scribing the session. Marco Hogewoning RIPE 63 Scribe: Mirjam Kuehne WG chairs: David Kessens, Shane Kerr, Marco Hogewoning Date: 1 November 2011, 16:00 - 17:30 IPv6 WG meeting (first session) Marco Hogewoning opens the IPv6-WG 1. Administrivia: - Minutes of RIPE 61 have been circulated - There was no IPv6-WG session at RIPE 62 - Thanks to the RIPE NCC for taking minutes at RIPE 63 2. Renumbering IPv6 - IETF 6RENUM WG (Tim Chown, Wes George; presented by Shane Kerr) The Address Policy WG asked the IPv6-WG for some advice about renumbering. Trying to avoid renumbering could be a reason for organisations to request PI space. Renumbering is considered to be difficult. But if renumbering would be very easy, then this wouldn't be a good reason for PI space (there might be others however). The IETF 6RENUM WG is working on this topic. It was formed after a BoF at IETF 81. There was some previous work done on IPv6 renumbering (see RFC 4192, RFC 5887 and draft-chown-v6ops-renumber-thinkabout-05). The current work of the 6RENUM WG is focused on renumbering for enterprise networks, not ISP networks. But enterprises all get their Internet connectivity from somewhere - from ISPs. Many of them are in the RIPE community. Tim Chown is looking for feedback from this community. The first 6RENUM WG draft documents internal triggers to renumber. There is also a document providing a gap analysis. Q&A: James Blessing commented that IF you design your network properly in the first place, renumbering is fairly straightforward - it is still work, but it's straightforward. Marco was wondering if it would help if this group would come up with a BCP about network design. Shane thought this would be a good idea (people usually appreciate RIPE BCPs). Gert Doering (Spacenet and IPv6 user for many years) agreed with James: A large part of the pain can be avoided with a good network design. Don't hardcode IP addresses etc. A BCP document listing the dos and don'ts would be useful. On the other hand, we don't want to overlap with the IETF WG (would have to check that this is not part of their charter). Marco emphasised that the IETF 6RENUM WG is mostly focused on enterprise networks. He suggested that the RIPE IPv6-WG could fill the gap and provide some documentation for ISPs. Gert said he obviously thought about this also, because it is related to address policy. Gert said he spent some thought on that as well, because obviously touches on Address Policy. Like I if he’s a small ISP and not multi‑homed yet but wants independent addresses and why not just renumber if you change upstream and? One of the really painful things about renumbering an ISP network is you have to renumber your customers and that works for end users that are fully automated provisioned, like prefix delegation and stuff so there is no boxes to be touched and the box auto configures everything on connection anyway but it doesn't work at all for business ISPs where you have many configured firewalls and everything, so renumbering an ISP with business customers is nearly impossible. Gert said he’s done it two times and that it's nearly impossible. So this might be the reason why they have excluded ISPs from this scope. On the other hand, some parts of the ISPs are just an enterprise network, like server housing, DNS servers, firewalls and stuff, so there is overlap again. Shane said there was a couple of different things going on, one being able to provide recommendations to people who are doing network design, maybe even in the case where you have customers perhaps recommending prefix delegation or whatever. But the other issue is the recommendations on the policy space, maybe clarifying in which cases PI space makes sense, for instance a small ISP with downstream customers or something like that. Gert said that better defining the problem space, would certainly help making appropriate policy. Documenting different use cases could be helpful. James commented that according to current policy, having PI IPv6 address space stops you from giving addresses to customers. Gert said that this is correct and that it's an artefact of the history of PI address space policy. This will be discussed more in the Address Policy WG. Maksym Tulyuk (AMS-IX) reported that at AMS-IX they renumbered from PI to PA IPv6 space and that this was not a big problem. Marco clarified that this was a migration of a service network, not a customer network. Benedikt Stockebrand said that when it comes to renumbering, the biggest problem is all the legacy equipment and configurations. You need to figure out first what the network is supposed to be doing before you renumber it. Shane asked the audience if IPv6 provides any benefits at all when it comes to renumbering? Benedikt said it is important that people realise how to pay for this in the long run. Aaron Hughes (6connect) reported that in the ARIN region, a best current operational practices track was started. The first document described subnetting IPv6 for ISPs. We also said that they'd be happy to work on documentation for enterprises as well. These topics are discussed on the following mailing list: bcp-discuss at bind.com <mailto:bcp-discuss at bind.com > Aaron said he’d send more information to the RIPE IPv6-WG mailing list. Jan Zorz wondered why the IETF created the 6RENUM WG. Shane responded that it might be a little early to present their work since the WG has just started. Gert responded to Shane's earlier question that renumbering in IPv6 is easier, because all stacks know how to handle multiple addresses at the same time. But from a planning point of view, it is the same. ACTION WG chair: to send mail to the mailing list asking if there are volunteers to start on a renumbering BCP for ISPs and if people know if there is already work being done in this area. 3. Replacing ripe-501 (Jan Zorz, Sander Steffann) See "Requirements for IPv6 in ICT Equipment": http://www.ripe.net/ripe/docs/ripe-501 ripe-501 was published a year ago and has already been translated into ten languages.Since then many requests for changes were received. The document was a great success, but of course things can always be improved. New devices were added to the document. Specifications about load balancers were added. The compliance criteria were also simplified. There was a good discussion on the mailing list. The document is currently in last call. Note that the document is meant as a template, don't just cut and paste bits and pieces. Jan and Sander thanked Merike Kaeo for providing a lot of useful input. Randy Bush (IIJ) had a question about the CPE diagram in the document. Jan explained that the RFC written by Ole Troan was included as a mandatory requirement. The idea was not to duplicate Ole's work. If a CPE does not support this RFC, it should not be taken into account in the process. Sander asked people to send comments to the mailing lists to specify if this comment should be included right now (which means extending the last call) or if it is OK to include it in the next version. The Last Call for the current version of the document ends next week, 10 November 2011. Tahar Schaa (consultant supporting German government) asked what their plans were to include source address validation improvements. Sander confirmed that it would be included in the document. But it is up to the tender initiator to ask for this requirement or not. 4. Horses for courses - like IPv6 profiles for German Administration (Constanze Buerger, Bundesministerium des Inneren, Germany) The prepsentation is available at: http://ripe63.ripe.net/presentations/74-2011_RIPE_63_de.government_Constanz… Maksym asked if the files Constanze mentioned in her presentation are publicly available. Constance said this has not yet been decided. Alexander Isavnin from Russia wondered how much this process is costing the German taxpayers? Constance responded that they are just coordinating the IPv6 address space allocated to them and the deployment to all federal governments and institutions. But it will take a long time until this is finished. Alexander asked if each department has its own budget. Constance confirmed that this is the case. She also explained that it is not so easy to convince people to cooperate. Every municipality can do their own thing. That means she and her team have to do a lot of convincing, but they cannot force the others to cooperate. Jan Zorz thanked Constanze for considering ripe-501 as a basis for her work and mentioned that there will be a new version (and a new number). He asked that Constanze and Tahar make their own adjustments in their documentation when the new version comes out. Tahar clarified that ripe-501 goes into the same direction as their work is going already anyway. So yes, a few adjustments will have to be made, but it's not that difficult, because they are aware of the changes. Jan asked if Constanze or Tahar are aware of any other governments following the German example. Tahar said he believed that Spain is following a similar process. Martin Levy (Hurricane Electric) thought it would be better to rephrase the earlier question: “What would this cost if you were to ignore IPv6?”. Constance explained that they tried to analyse the costs so that they can put some pressure on the leadership. But it turned out to be very difficult, because the government and the network is so heterogeneous. In the end they had to stop the process analysing the costs. Tahar added that Germany, due to its constitution, is a complex country. The costs are held and managed in each state and each municipality. All that can be done really is to provide the first steps and some supporting documentation. He saw two main motivations to deploy IPv6: 1. Address renumbering (there is a long history of using IPv4 address, mostly private, which means that there is now a horrible network of cascading NAT layers. Some of the networks have been renumbered up to four times and this is very costly. Deploying IPv6 will solve these problems. 2. If one wants to set up a telephone infrastructure in Germany today, it is only possible to buy VoIP telephony. What about one office wants to call another and the addresses clash? You can better start using public (IPv6) addresses. In conclusion, the question is not: What does it cost to do it, but what does it cost not to do it? Constance said yes, just do it. 4. Status of ADSL Deployment in the XS4All network (Timo Hilbrink, XS4All) The presentation is available at: http://ripe63.ripe.net/presentations/75-th-ipv6-ripe63-20111101.pdf Maksym asked why the MTU on one of the slides was set to 1452, why it was so low and whether it was part of his implementation. Timo said yes. Gert applaud Timo and XS4All on this. He said it was great to see one mass-market provider go forward with this. He said he hopes that there will also be more users in Germany any time soon. Andy Davidson (Hurricane Electric) asked if Timo knew the retail prices of the new CPEs that include IPv6. Timo said they were around EUR 100. Andy concluded that that price is coming down all the time, which is great. 5. Lightning Talks 5.1. Results of the 2011 Global IPv6 Deployment Monitoring Survey (Chris Buckridge for Maarten Botemann) The presentation is available at: http://ripe63.ripe.net/presentations/114-ipv6-survey-BUCKRIDGE.pdf 5.2. Effects of Capacity Building on IPv6 Adoption and Deployment (Marco Hogewoning, RIPE NCC) The presentation is available at: http://ripe63.ripe.net/presentations/66-MH-RIPE63-Capacity-LT.pdf 5.3. Stateless IPv4 over IPv6 in 5 minutes (Ole Troan, Cisco) The presentation is available at: http://ripe63.ripe.net/presentations/40-RIPE63-MAP-lightning.pdf Jan, as a member of the MAP (A+P) architecture team, asked attendees if they felt that well-known ports must never be allocated to a user or if the user should have the opportunity to use well-known ports. Ole responded that you could give users that are not happy with the default setting a full IPv4 address. Benedikt explained that users shouldn't need low ports. He wondered if prolonging IPv4 is really worth the effort. The majority of people don't want to run a server at home. For those who want to, they will switch to IPv6 shortly. Those who use an IPv4 server at home will get some IPv4 addresses from somewhere. It's not something you want to provision for mass customer products. Jan said he believed stateless A+P is worthwhile because we don't want CGNs. Benedikt disagreed and said he wants CGN and wants it to hurt that much that people will use native IPv6 in the end. Jari Arkko (Eriksson) pointed out that there are trade-offs: If you are doing port division per customer on an static basis for customers, the power user and a small user get the same service, which neither of them will be happy with; we will pay in any case. 6. IANA Reserved IPv4 prefixes for shared CGN space (David Kessens) The presentation is available at: http://ripe63.ripe.net/presentations/84-201111012011-ripe63-vienna-sharedad… < http://ripe63.ripe.net/presentations/84-201111012011-ripe63-vienna-sharedad… > Gert wondered which address space they were going to use. David agreed that this is of course an issue. However, since this proposal was well received in the ARIN region, it was suggested to use a /10 out of ARINs' address space. Jari reported that he was one of the IESG members who reviewed this document and said he had a couple of concerns. Apart from the policy issues that are down to the RIR communities to decide, there are some issues with this particular proposal. What's the affect on the ISP ("My device works well now, but does it have negative affects on other parts of the network?"). He urged people to participate in this discussion and check if this would break anything. Kurtis Lindquist commented that this whole process seemed a little weird (between one RIR and the IAB and the IESG). Martin Levy said it is interesting that they were talking about IPv4 and CGNs a lot instead of about IPv6. ACTION: It was decided to defer the topic of draft-weil-shared-transition-space-request to the mailing list. 7. IPv6 Speed Dating Marco asked the audience how many people in the room have deployed IPv6 (about half of the room). The other half is busy deploying it. He further asked those who are busy deploying it, what the biggest challenge is they face in the process? A speaker from the audience said that the biggest challenge is to convince the management. The management thinks it is too expensive. Marco asked those who deployed IPv6 how they passed that hurdle. Andy said to just do it anyways. Jan Zorz responded that he gave a 45 minute presentation earlier explaining how to convince the management. Benedikt suggested to ask the management: "What's the business case of an earth quake?" The same applies to IPv6: by trying to safe money, you might lose customers and money in the end. Timo suggested to explain to the management what they would lose if they didn't do it. Jen Linkova (Google) explained that from an operational perspective they are still discovering bugs now and that they have to test almost everything again for IPv6. Therefore her advice is to test everything twice from the start, don't expect things to works out of the box. Marco pointed out that this community and especially this IPv6 WG is a great pool of resources on IPv6 deployment. Dave Wilson (HEAnet) responded to the question of what problem he had to solve and how he convinced his boss. He said he solved this in his case by providing a business case. But that might be different in other environments. A speaker from the audience said that after convincing your boss, the main problem is organisational: all departments in your company (networks, IT, service, marketing etc.) have to work together. That is not always easy. Andy added to his earlier comment that even if people don't have official mandate, he would advise them to skill-up anyways, so they can be prepared for the deployment phase. The working group co-chairs thanked attendees and closed the session. Summary of Action Points – IPv6 WG RIPE 63 ACTION WG chair: to send mail to the mailing list asking if there are volunteers to start on a renumbering BCP for ISPs and if people know if there is already work being done in this area. ACTION: It was decided to defer the topic of draft-weil-shared-transition-space-request to the mailing list.

1 1

RIPE-501 replacement document - IPsec question to community - we need your input.
by Jan Zorz ＠ go6.si 27 Jan '12

27 Jan '12

Dear IPv6 community. (copy/paste from our internal discussion) The authors of RIPE-501 are finalizing the last comments from previous last call and would like community input for what to do with IPsec. All authors feel that IPsec should be a mandatory requirement for all devices although due to technical limitations, for mobile devices it will be optional. We are aware that RFC6434 made IPsec support a SHOULD rather than a MUST. From RFC 2119: SHOULD This word, or the adjective "RECOMMENDED", mean that there may exist valid reasons in particular circumstances to ignore a particular item, but the full implications must be understood and carefully weighed before choosing a different course. The change was largely due to limitations found in low power devices and therefore we still feel the community is best served by requiring mandatory IPsec support in all other devices (hosts, routers or layer-3 switches, network security devices, load balancers) If we get this input from you this year, there is a great chance that we could put out the new/final draft out for discussion and/or maybe last-last-call before new year. For RIPE-501 authors group, Jan P.S: wishing happy new year, merry xmass, happiness, IPv6 and all that stuff in at least next year :)

16 35

More IPv6 on mobile networks testing...
by Jan Zorz ＠ go6.si 18 Jan '12

18 Jan '12

Hi, I suspect some of you could find this interesting. Excuse to others for filling their mailboxes ;) http://go6.si/en/2012/01/nokia-usb-modem-21m02-ii/ Nokia USB "Internet stick" with PDPv4, PDPv6 and PDPv4v6 capability test. Cheers, Jan

3 2

IPv6 Launch Day
by Marco Hogewoning 17 Jan '12

17 Jan '12

The follow up on World IPv6 Day has just been announced. Marco http://www.worldipv6launch.org/press/20120117-2/ World IPv6 Launch Solidifies Global Support for New Internet Protocol Top websites, Internet service providers, and home networking equipment manufacturers commit to largest transition in the Internet’s history [Washington, D.C., USA and Geneva, Switzerland] – 17 January 2012 – Major Internet service providers (ISPs), home networking equipment manufacturers, and web companies around the world are coming together to permanently enable IPv6 for their products and services by 6 June 2012. Organized by the Internet Society, and building on the successful one-day World IPv6 Day event held on 8 June 2011, World IPv6 Launch represents a major milestone in the global deployment of IPv6. As the successor to the current Internet Protocol, IPv4, IPv6 is critical to the Internet’s continued growth as a platform for innovation and economic development. “The fact that leading companies across several industries are making significant commitments to participate in World IPv6 Launch is yet another indication that IPv6 is no longer a lab experiment; it’s here and is an important next step in the Internet’s evolution,” commented Leslie Daigle, the Internet Society’s Chief Internet Technology Officer. “And, as there are more IPv6 services, it becomes increasingly important for companies to accelerate their own deployment plans.” ISPs participating in World IPv6 Launch will enable IPv6 for enough users so that at least 1% of their wireline residential subscribers who visit participating websites will do so using IPv6 by 6 June 2012. These ISPs have committed that IPv6 will be available automatically as the normal course of business for a significant portion of their subscribers. Committed ISPs are: ● AT&T ● Comcast ● Free Telecom ● Internode ● KDDI ● Time Warner Cable ● XS4ALL Participating home networking equipment manufacturers will enable IPv6 by default through the range of their home router products by 6 June 2012. Committed equipment manufacturers are: ● Cisco ● D-Link Web companies participating in World IPv6 Launch will enable IPv6 on their main websites permanently beginning 6 June 2012. Inaugural participants are: ● Facebook (www.facebook.com) ● Google (www.google.com) ● Microsoft Bing (www.bing.com) ● Yahoo! (www.yahoo.com) Content delivery network providers Akamai and Limelight will be enabling their customers to join this list of participating websites by enabling IPv6 throughout their infrastructure. As IPv4 addresses become increasingly scarce, every segment of the industry must act quickly to accelerate full IPv6 adoption or risk increased costs and limited functionality online for Internet users everywhere. World IPv6 Launch participants are leading the way in this effort. For more information about World IPv6 Launch, products, and services covered, as well as links to useful information for users and information about how other companies may participate, visit: http://www.worldipv6launch.org About the need for IPv6 IPv4 has approximately four billion IP addresses (the sequence of numbers assigned to each Internet-connected device). The explosion in the number of people, devices, and web services on the Internet means that IPv4 is running out of space. IPv6, the next-generation Internet protocol which provides more than 340 trillion, trillion, trillion addresses, will connect the billions of people not connected today and will help ensure the Internet can continue its current growth rate indefinitely. About the Internet Society The Internet Society is the world’s trusted independent source of leadership for Internet policy, technology standards and future development. Based on its principled vision and substantial technological foundation, the Internet Society works with its members and Chapters around the world to promote the continued evolution and growth of the open Internet through dialog among companies, governments, and other organizations around the world. For more information, see: www.internetsociety.org Akamai Technologies, Inc. Jeff Young AT&T Jenny Bridges Cisco Marc Musgrove Comcast Jorge Alberni D-Link Denise Keddy Facebook Nisha Gulati Google Inc. Internet Society Wende Cover Internode John Harris Limelight Networks Microsoft Bing Bill Hankes Time Warner Cable Justin Venech Yahoo! Christina Scharrenberg

1 0

v6 World Connectivity To v4 World
by Matthew Walster 14 Jan '12

14 Jan '12

Apologies if this would be more suitable for IETF v6ops rather than IPv6-WG, I'm not overly familiar with the v6 development community. As is painfully apparent, most of the world if v4 only at the moment - and the various DNS ALGs etc for getting v4 connectivity onto v6 only connections seem "hackish" at best, and have real problems when it comes to things such as 1500-byte v4 packets needing fragmenting to travel over v6 nets. While playing with my local ssh daemon, I was reminded that inside my ssh client is a SOCKS5 server - I can connect to it by just setting my global SOCKS setting to use the localhost and all the traffic is forwarded down the tunnel to the remote host for processing. I was wondering whether anyone had any experience in setting a SOCKS proxy on a v6-only host, where the DNS/SOCKS proxies have both v4 and v6 addressing, and whether they can then access v4 services like web sites, mail servers, gaming applications etc. The basic idea is that you would use the v6 internet where possible, and go through your ISPs v4 SOCKS gateway for anything that didn't return a AAAA record. Is that idea right, and if so, is it sustainable? Assuming for the moment that I've made a correct assumption, is there a way we can make the process easier? Back in v4 world, there's DHCP option 252 which allows you to configure a WPAD file that would be downloaded and parsed by your web browser, setting HTTP proxies etc for certain classes of service - non-local traffic etc. Is it feasible to add an option to DHCPv6 so that a "v4 compatibility" string could be set, whereby a fall-back SOCKS server is used for non-v6 connections? Thinking off the top of my head, it would work as follows for the "no-clue" home user: User's router talks to ISP via DHCPv6: gets response detailing address to use also gets prefix delegation for local LAN usage also gets v4 compatibility string, which it stores for relaying to clients User's router listens for DHCPv6 requests, issues clients on local LAN public v6 addresses: sets option for v4-compatibility for clients User's computer turns on, asks for addressing information: gets v6 address via DHCPv6 gets v4-compatibility string and sets global SOCKS proxy variable, if not manually configured gets other string - DNS servers, routes etc. I stress that this idea is for v6/v4 co-existence, and isn't designed for "islands of v4" or "islands of v6", it would of course assume that v4 availability is restricted and a real effort to move to v6 was made. It's a transition mechanism that should be easy to turn off once most of the services have been migrated (hopefully transparently to the end customer). If there is a major flaw in my idea, I'd greatly appreciate constructive criticism and feedback! Matthew Walster

1 0

Latest 6::gle phone Nexus supports IPv6 on 3G
by Jan Zorz ＠ go6.si 02 Jan '12

02 Jan '12

All good in new year, the year of IPv6 :) In Go6Lab we tested new 6::gle phone with Android 4 and good news is, that it supports IPv6 PDP context over 3G. With Cameron from T-Mobile USA we are compiling list of apps, that are not working in IPv6-only environment, but for now we can live with it in everyday life :) The list will be published and compiled later. Short first report with snapshots: http://go6.si/en/2011/12/samsung-galaxy-nexus-nov-google-phone-podpira-tudi… Good news for start of new year. Cheers, Jan Zorz Go6 Institute Slovenia, CEO

1 0

Usenix: Google deploys IPv6 for internal network
by Carsten Schiefner 19 Dec '11

19 Dec '11

Dear all - maybe this: https://www.networkworld.com/news/2011/120911-usenix-google-deploys-ipv6-fo… is an interesting read-up for at least some of you... Best, -C.

2 2

Update in the RIPE document for IPv6 Allocation and Assignment policies
by Emilio Madaio 07 Dec '11

07 Dec '11

Dear colleagues, An editorial correction has been made to ripe-523 "IPv6 Address Allocation and Assignment Policy". The updated document has been renumbered to ripe-538. It is available at: http://www.ripe.net/ripe/docs/ripe-538 There was a mismatch between the policy text and the index title for section 5.4.2. This mismatch occurred between the updates from ripe-421 to ripe-450. Apologies for any inconvenience caused. Kind regards, Emilio Madaio Policy Development Officer RIPE NCC

1 0

on RIPE-523 IPv6 Address Allocation and Assignment Policy
by Jac Kloots 05 Dec '11

05 Dec '11

While I was reading RIPE-523 I noticed a mismatch between titles in the indexand the paragraph itself. The index for 5.4.2 says: Assignments shorter than a /48 to a single End Site While the paragraph title is: Assignment of multiple /48s to a single End Site Any change on getting this in line? Regards, Jac -- Jac Kloots Network Services SURFnet bv

1 0

New on RIPE Labs: Hampered Eyeballs
by Mirjam Kuehne 30 Nov '11

30 Nov '11

Dear colleagues, Please see a new article by Emile Aben on RIPE Labs: "Hampered Eyeballs - Observations on Two "Happy Eyeballs" Implementations" https://labs.ripe.net/Members/emileaben/hampered-eyeballs Kind Regards, Mirjam Kuehne RIPE NCC

1 1

New IPv6 related article on RIPE Labs
by Mirjam Kuehne 22 Nov '11

22 Nov '11

Dear colleagues, Please see a new article on RIPE Labs submitted by Emile Aben. It contains interesting treegraphs showing IPv6 deployment in correlation with the an LIR's size: https://labs.ripe.net/Members/emileaben/interesting-graph-ipv6-per-lir Kind regards, Mirjam Kuehne RIPE NCC

1 0

Announcement: RIPE NCC Training Courses
by Training Mailbox 21 Nov '11

21 Nov '11

[Apologies for duplicate e-mails] Dear Colleagues, The RIPE NCC invites you to register for one of our upcoming training courses: - The LIR Training Course This course teaches LIRs how to request Internet number resources and interact with the RIPE NCC. A course outline is available at: http://www.ripe.net/lir-services/training/courses/lir/outline/ - The Routing Registry Training Course This course teaches LIRs how to use the RIPE Database for routing. A course outline is available at: http://www.ripe.net/lir-services/training/courses/rr/ - The IPv6 Training Course This course teaches LIRs about the need for IPv6 and includes basic information on how to plan your deployment. A course outline is available at: http://www.ripe.net/training/ipv6/outline.html To see the location of upcoming courses and to register, please use the LIR Portal or complete the registration form on our website at: RIPE NCC Upcoming Courses List& Registration https://lirportal.ripe.net/training/courses If you have any questions, please do not hesitate to contact us at <training(a)ripe.net>. Kind regards, Rumy Spratley-Kanis Training Services Manager RIPE NCC

1 0

Last call on the replacement of ripe-501 "Requirements for IPv6 in ICT equipment"
by Marco Hogewoning 15 Nov '11

15 Nov '11

Dear colleagues, Following up on feedback received from the community during and after the publication of the ripe-501. The authors have worked on a replacement document, incorporating suggestions made by the community and clarifying some of the requirements. Prior draft versions of this document have been posted to this mailing list in the past months. The resulting final draft document is now published on the website and reachable via https://www.ripe.net/ripe/docs/other-documents/requirements-for-ipv6-in-ict… We would like the community to review this document. Although this is not a formal policy proposal, we would like to issue a 4 week working group last call on this draft before publication. Minor changes like typos or formatting can be sent to the authors or to me directly. Please raise any questions or comments on the content to this list. Unless blocking issues are found on this text, it is our intent to publish this draft as a RIPE Document and to change the status of the current document ripe-501 to obsolete, with a reference to the new document. The authors will also present on this draft during the IPv6 working group session at the Vienna meeting. Please send any comments before Thursday November 10 2011, which is 4 weeks from now. Regards, Marco Hogewoning on behalf of the IPv6 Working Group chairs

7 10

IPv6 RIPEness - Sorted by LIR's Age and Size
by Mirjam Kuehne 09 Nov '11

09 Nov '11

Dear colleagues, We just published a new article on RIPE Labs that looks at IPv6 RIPEness from a slightly different perspective - relative to the age and size of LIRs: https://labs.ripe.net/Members/wilhelm/ipv6-ripeness-sorted-by-lirs-age-and-… Kind Regards, Mirjam Kuehne RIPE NCC

1 0

IPv6 security (slides and training)
by Fernando Gont 09 Nov '11

09 Nov '11

Folks, We have uploaded the slides of my IPv6 Security presentation at H2HC 2011. -- The slides are available at: <http://www.si6networks.com/presentations/h2hc2011/fgont-h2hc2011-ipv6-secur…>. That aside, on November 15-16 I'll be teaching a two-day IPv6 security training at the DEEPSEC 2011 conference (http://www.deepsec.net) in Vienna (Austria). Anybody interested please check out the details at: <http://www.deepsec.net/speaker.html#WSLOT40>. and/or e-mail me off-list. Thanks! Best regards, -- Fernando Gont SI6 Networks e-mail: fgont(a)si6networks.com PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492

1 0

IPv6 & privacy issues @ RIPE63
by Vesna Manojlovic 04 Nov '11

04 Nov '11

Hi all, Benjamin Erhart will have a whole session on the RIPE63 in Vienna dedicated to the discussion about privacy concerns with IPv6 adoption: http://ripe63.ripe.net/programme/meeting-plan/bof/ Thursday, 3.November 2011, 17:45 There is the remote participation possibility: webcast & jabber: http://ripe63.ripe.net/live/ Please help him by spreading the word, or commenting already in advance on his topics, or in some other way you think of :) Thanks, Vesna (Internet Citizen) (text version, for quoting in the reply message) BoF (Birds of a Feather) Thursday, 3 November, 17:45 – 19:00 AK Vorrat’s position on IPv6 privacy issues Benjamin Erhart, Arbeitskreis Vorratsdatenspeicherung Germany IPv6 recently came into the focus of the German NGO Arbeitskreis Vorratsdatenspeicherung (Working Group on Data Retention). Since then, the working group has developed a position on how user privacy should be supported by ISPs and software/hardware vendors. To mitigate privacy issues with potentially life-long IP addresses for every user, users should be empowered to choose what’s best for them. Join Benjamin at this BoF to offer your input on this and discuss, among other topics, how: - The introduction of IPv6 influences data retention laws - Your MAC address is used as part of an IPv6 host address - Privacy concerns in Germany are going to influence ISPs’ IPv6 assignment practices

2 1

2nd CfP: ICCGI 2012 || June 24-29, 2012 - Venice, Italy
by Cristina Pascual 03 Nov '11

03 Nov '11

INVITATION: ================= Please, consider to contribute to and/or forward to the appropriate groups the following opportunity to submit and publish original scientific results to ICCGI 2012. The submission deadline is set to February 5, 2012. In addition, authors of selected papers will be invited to submit extended article versions to one of the IARIA Journals: http://www.iariajournals.org ================= ============== ICCGI 2012 | Call for Papers =============== CALL FOR PAPERS, TUTORIALS, PANELS ICCGI 2012, The Seventh International Multi-Conference on Computing in the Global Information Technology June 24-29, 2012 - Venice, Italy General page: http://www.iaria.org/conferences2012/ICCGI12.html Call for Papers: http://www.iaria.org/conferences2012/CfPICCGI12.html - regular papers - short papers (work in progress) - posters - ideas Submission page: http://www.iaria.org/conferences2012/SubmitICCGI12.html Submission deadline: February 5, 2012 Sponsored by IARIA, www.iaria.org Extended versions of selected papers will be published in IARIA Journals: http://www.iariajournals.org Please note the Poster and Work in Progress options. The topics suggested by the conference can be discussed in term of concepts, state of the art, research, standards, implementations, running experiments, applications, and industrial case studies. Authors are invited to submit complete unpublished papers, which are not under review in any other conference or journal in the following, but not limited to, topic areas. All tracks are open to both research and industry contributions, in terms of Regular papers, Posters, Work in progress, Technical/marketing/business presentations, Demos, Tutorials, and Panels. Before submission, please check and comply with the Editorial rules: http://www.iaria.org/editorialrules.html ICCGI 2012 Topics (topics and submission details: see CfP on the site) Industrial systems Control theory and systems; Fault-tolerance and reliability; Data engineering; Enterprise computing and evaluation; Electrical and electronics engineering; Economic decisions and information systems; Advanced robotics; Virtual reality systems; Industrial systems and applications; Industrial and financial systems; Industrial control electronics; Industrial IT solutions Evolutionary computation Algorithms, procedures, mechanisms and applications; Computer architecture and systems; Computational sciences; Computation in complex systems; Computer and communication systems; Computer networks; Computer science theory; Computation and computer security; Computer simulation; Digital telecommunications; Distributed and parallel computing; Computation in embedded and real-time systems; Soft computing; User-centric computation Autonomic and autonomous systems Automation and autonomous systems; Theory of Computing; Autonomic computing; Autonomic networking; Network computing; Protecting computing; Theories of agency and autonomy; Multi-agent evolution, adaptation and learning; Adjustable and self-adjustable autonomy; Pervasive systems and computation; Computing with locality principles; GRID networking and services; Pervasive computing; Cluster computing and performance; Artificial intelligence Computational linguistics; Cognitive technologies; Decision making; Evolutionary computation; Expert systems; Computational biology Bio-technologies Models and techniques for biometric technologies; Bioinformatics; Biometric security; Computer graphics and visualization; Computer vision and image processing; Computational biochemistry; Finger, facial, iris, voice, and skin biometrics; Signature recognition; Multimodal biometrics; Verification and identification techniques; Accuracy of biometric technologies; Authentication smart cards and biometric metrics; Performance and assurance testing; Limitations of biometric technologies; Biometric card technologies; Biometric wireless technologies; Biometric software and hardware; Biometric standards Knowledge data systems Data mining and Web mining; Knowledge databases and systems; Data warehouse and applications; Data warehousing and information systems; Database performance evaluation; Semantic and temporal databases; Database systems Databases and information retrieval; Digital library design; Meta-data modeling Mobile and distance education Human computer interaction; Educational technologies; Computer in education; Distance learning; E-learning; Mobile learning Cognitive support for learning; Internet-based education; Impact of ICT on education and society; Group decision making and software; Habitual domain and information technology; Computer-mediated communications; Immersing authoring; Contextual and cultural challenges in user mobility Intelligent techniques, logics, and systems Intelligent agent technologies; Intelligent and fuzzy information processing; Intelligent computing and knowledge management; Intelligent systems and robotics; Fault-tolerance and reliability; Fuzzy logic & systems; Genetic algorithms; Haptic phenomena; Graphic recognition; Neural networks; Symbolic and algebraic computation; Modeling, simulation and analysis of business processes and systems Knowledge processing Knowledge representation models; Knowledge languages; Cognitive science; Knowledge acquisition; Knowledge engineering; Knowledge processing under uncertainty; Machine intelligence; Machine learning; Making decision through Internet; Networking knowledge plan Information technologies Information technology and organizational behavior; Agents, data mining and ontologies; Information retrieval systems; Information and network security; Information ethics and legal evaluations; Optimization and information technology; Organizational information systems; Information fusion; Information management systems; Information overload; Information policy making; Information security; Information systems; Information discovery Internet and web technologies Internet and WWW-based computing; Web and Grid computing; Internet service and training; IT and society; IT in education and health; Management information systems; Visualization and group decision making; Web based language development; Web search and decision making; Web service ontologies; Scientific web intelligence; Online business and decision making; Business rule language; E-Business; E-Commerce; Online and collaborative work; Social eco-systems and social networking; Social decisions on Internet; Computer ethics Digital information processing Mechatronics; Natural language processing; Medical imaging; Image processing; Signal processing; Speech processing; Video processing; Pattern recognition; Pattern recognition models; Graphics & computer vision; Medical systems and computing Cognitive science and knowledge agent-based systems Cognitive support for e-learning and mobile learning; Agents and cognitive models; Agents & complex systems; computational ecosystems; Agent architectures, perception, action & planning in agents; Agent communication: languages, semantics, pragmatics & protocols; Agent-based electronic commerce and trading systems Multi-agent constraint satisfaction; Agent programming languages, development environments and testbeds; Computational complexity in autonomous agents; Multi-agent planning and cooperation; Logics and formal models of for agency verification; Nomadic agents; Negotiation, auctions, persuasion; Privacy and security issues in multi-agent systems Mobility and multimedia systems Mobile communications; Multimedia and visual programming; Multimedia and decision making; Multimedia systems; Mobile multimedia systems; User-centered mobile applications; Designing for the mobile devices; Contextual user mobility; Mobile strategies for global market; Interactive television and mobile commerce Systems performance Performance evaluation; Performance modeling; Performance of parallel computing; Reasoning under uncertainty; Reliability and fault-tolerance; Performance instrumentation; Performance monitoring and corrections; Performance in entity-dependable systems; Real-time performance and near-real time performance evaluation; Performance in software systems; Performance and hybrid systems; Measuring performance in embedded systems Networking and telecommunications Telecommunication and Networking; Telecommunication Systems and Evaluation; Multiple Criteria Decision Making in Information Technology; Network and Decision Making; Networks and Security; Communications protocols (SIP/H323/MPLS/IP); Specialized networks (GRID/P2P/Overlay/Ad hoc/Sensor); Advanced services (VoIP/IPTV/Video-on-Demand; Network and system monitoring and management; Feature interaction detection and resolution; Policy-based monitoring and managements systems; Traffic modeling and monitoring; Traffic engineering and management; Self-monitoring, self-healing and self-management systems; Man-in-the-loop management paradigm Software development and deployment Software requirements engineering; Software design, frameworks, and architectures; Software interactive design; Formal methods for software development, verification and validation; Neural networks and performance; Patterns/Anti-patterns/Artifacts/Frameworks; Agile/Generic/Agent-oriented programming; Empirical software evaluation metrics; Software vulnerabilities; Reverse engineering; Software reuse; Software security, reliability and safety; Software economics; Software testing and debugging; Tracking defects in the OO design; Distributed and parallel software; Programming languages; Declarative programming; Real-time and embedded software; Open source software development methodologies; Software tools and deployment environments; Software Intelligence; Software Performance and Evaluation Knowledge virtualization Modeling techniques, tools, methodologies, languages; Model-driven architectures (MDA); Service-oriented architectures (SOA); Utility computing frameworks and fundamentals; Enabled applications through virtualization; Small-scale virtualization methodologies and techniques; Resource containers, physical resource multiplexing, and segmentation; Large-scale virtualization methodologies and techniques; Management of virtualized systems; Platforms, tools, environments, and case studies; Making virtualization real; On-demand utilities Adaptive enterprise; Managing utility-based systems; Development environments, tools, prototypes Systems and networks on the chip Microtechnology and nanotechnology; Real-time embedded systems; Programming embedded systems; Controlling embedded systems; High speed embedded systems; Designing methodologies for embedded systems; Performance on embedded systems; Updating embedded systems; Wireless/wired design of systems-on-the-chip; Testing embedded systems; Technologies for systems processors; Migration to single-chip systems Context-aware systems Context-aware autonomous entities; Context-aware fundamental concepts, mechanisms, and applications; Modeling context-aware systems; Specification and implementation of awareness behavioral contexts; Development and deployment of large-scale context-aware systems and subsystems; User awareness requirements Design techniques for interfaces and systems; Methodologies, metrics, tools, and experiments for specifying context-aware systems; Tools evaluations, Experiment evaluations Networking technologies Next generation networking; Network, control and service architectures; Network signalling, pricing and billing; Network middleware; Telecommunication networks architectures; On-demand networks, utility computing architectures; Next generation networks [NGN] principles; Storage area networks [SAN]; Access and home networks; High-speed networks; Optical networks; Peer-to-peer and overlay networking; Mobile networking and systems; MPLS-VPN, IPSec-VPN networks; GRID networks; Broadband networks Security in network, systems, and applications IT in national and global security; Formal aspects of security; Systems and network security; Security and cryptography; Applied cryptography; Cryptographic protocols; Key management; Access control; Anonymity and pseudonymity management; Security management; Trust management; Protection management; Certification and accreditation; Virii, worms, attacks, spam; Intrusion prevention and detection; Information hiding; Legal and regulatory issues Knowledge for global defense Business continuity and availability; Risk assessment; Aerospace computing technologies; Systems and networks vulnerabilities; Developing trust in Internet commerce; Performance in networks, systems, and applications; Disaster prevention and recovery; IT for anti-terrorist technology innovations (ATTI); Networks and applications emergency services; Privacy and trust in pervasive communications; Digital rights management; User safety and protection Information Systems [IS] Management Information Systems; Decision Support Systems; Innovation and IS; Enterprise Application Integration; Enterprise Resource Planning; Business Process Change; Design and Development Methodologies and Frameworks; Iterative and Incremental Methodologies; Agile Methodologies; IS Standards and Compliance Issues; Risk Management in IS Design and Development; Research Core Theories; Conceptualizations and Paradigms in IS; Research Ontological Assumptions in IS Research; IS Research Constraints, Limitations and Opportunities; IS vs Computer Science Research; IS vs Business Studies IPv6 Today - Technology and deployment IP Upgrade - An Engineering Exercise or a Necessity?; Worldwide IPv6 Adoption - Trends and Policies; IPv6 Programs, from Research to Knowledge Dissemination; IPv6 Technology - Practical Information; Advanced Topics and Latest Developments in IPv6; IPv6 Deployment Experiences and Case Studies; IPv6 Enabled Applications and Devices Modeling Continuous and Discrete Models; Optimal Models; Complex System Modeling; Individual-Based Models; Modeling Uncertainty; Compact Fuzzy Models; Modeling Languages; Real-time modeling; Performance modeling Optimization Multicriteria Optimization; Multilervel Optimization; Goal Programming; Optimization and Efficiency; Optimization-based decisions; Evolutionary Optimization; Self-Optimization; Extreme Optimization; Combinatorial Optimization; Discrete Optimization; Fuzzy Optimization; Lipschitzian Optimization; Non-Convex Optimization; Convexity; Continuous Optimization; Interior point methods; Semi-definite and Conic Programming Complexity Complexity Analysis; Computational Complexity; Complexity Reduction; Optimizing Model Complexity; Communication Complexity; Managing Complexity; Modeling Complexity in Social Systems; Low-complexity Global Optimization; Software Development for Modeling and Optimization; Industrial applications ------------------------------ Committee:http://www.iaria.org/conferences2012/ComICCGI12.html ====================

1 0

Some comments on 501bis
by Jari Arkko 03 Nov '11

03 Nov '11

Based on the discussion in the group today, I made a quick read of the beginning parts of 501bis today at: https://www.ripe.net/ripe/docs/other-documents/requirements-for-ipv6-in-ict… And I have some comments: > Some parts of this section are loosely based on the NIST/USGv6 profile developed by the US government: > > http <http://www.antd.nist.gov/usgv6/>:// <http://www.antd.nist.gov/usgv6/>www <http://www.antd.nist.gov/usgv6/>. <http://www.antd.nist.gov/usgv6/>antd <http://www.antd.nist.gov/usgv6/>. <http://www.antd.nist.gov/usgv6/>nist <http://www.antd.nist.gov/usgv6/>. <http://www.antd.nist.gov/usgv6/>gov <http://www.antd.nist.gov/usgv6/>/ <http://www.antd.nist.gov/usgv6/>usgv <http://www.antd.nist.gov/usgv6/>6/ <http://www.antd.nist.gov/usgv6/> > There's a DoD *and* USG recommendation, you might want to mention both. I think it would also be useful to point people to the IETF node requirements RFC, as that defines the formal conformance requirements from a standards perspective (but of course does that only for general nodes, so the more specific rules for different device types in 501 and the NIST documents is very useful). The RFC is about to come out, the -bis version is replacing the RFC that was years old. > > Lists of Required RFC /3GPP Standards for Different Type of Hardware > > ... Required RFCs and 3GPP Technical Specifications ... > > Requirements for Host Equipment > > *Mandatory support:* > I'm comparing this to draft-ietf-6man-node-req-bis, and there are some obvious differences. I think it would have been useful to point to this doc for the list of interface-type specific RFCs that are needed (RFC 2464 for Ethernet, for instance). > Optional support: > Revised ICMPv6 [RFC 5095] * This seems wrong. Its not a revised ICMP spec, it is deprecation of RH0. Draft-ietf-6man-node-req-bis marks its as mandatory, and I think you should too. > /*Mobile node:*/In the context of this document a mobile node is a device that connects via some 3GPP specification (such as 3G, GPRS/UMTS or LTE). In situations where the network logic is being provided solely by a dedicated device (A) connected to another device (B), the specification refers to device A and not to device B. If the protocol logic is distributed (for example, a computer with an external Ethernet interface that performs TCP checksum offloading), the aggregate system is being referred to. There's probably a 3GPP specification and testing requirements etc that defines exactly what the rules for a terminal device like this are. You should reference that and ensure that you're not saying something different. (The expertise on the matter seems to be mostly in 3GPP, so you want to be careful in saying something unless merely referring to existing specs. Maybe you are already doing this, I did not get that far in the spec.) > * > > Neighbor Discovery [RFC 4861] * > > * > > > Updated also by RFC 5942, as noted in draft-ietf-6man-node-req-bis RFC 4311 and 4191 are missing from the list of optional supports. * > > *Mandatory support:* > > * > > MLDv2 snooping [RFC 4541] > * This seems like an overkill for a consumer grade equipment (but I do support it for the other types of switches) I have to go to the social event now, will look at more things later. But my overall conclusion is that the document still needs more review... Jari

6 6

501bis and some comments
by jouni korhonen 02 Nov '11

02 Nov '11

Folks, I got a brief look at 501bis on some parts, specifically what comes to Mobile Node (3GPP) parts. It would be good to make a check against TS29.061 on the actually supported & required RFC.. or draft-ietf-v6ops-3gpp-eps-08, which takes quite a detailed but condensed peek into 3GPP IPv6 aspects. Quick comments on DHCPv6. The DHCPv6 support for Mobile Node is only for IPv6 parameter configuration via stateless DHCPv6 RFC3736, stateful address configuration (for the Mobile Node) is not supported at all. I also have concerns on IKE and IPsec 'mandatory support' text for Mobile Nodes as that is not the case in today's 3GPP standards as far as I remember. Furthermore, listing both rfc3041 and rfc4941 is not needed as the latter obsoletes the former. On the references part I do not understand why also 3GPP2 is included. Earlier in the document and in the definition part it was made quite clear "Mobile Node" refers only to 3GPP. These are just comments that could be taken into account in some future revision of 501bis. I can actually help crafting the text ;) - Jouni -- Jouni Korhonen Nokia Siemens Networks

1 0

IPv6 RIPEness - Production & Updates
by Mirjam Kuehne 01 Nov '11

01 Nov '11

[apologies for duplicates] Dear colleagues, Following your feedback, we decided to make IPv6 RIPEness a production service. Please find a short update on RIPE Labs: http://labs.ripe.net/Members/becha/ipv6-ripeness-production-updates We are currently also working on some new features. Stay tuned. Kind Regards, Mirjam Kuehne RIPE NCC

1 0

Deadline Extension: ICNS 2012 || March 25-29, 2012 - St. Maarten, The Netherlands Antilles
by Jaime Lloret Mauri 31 Oct '11

31 Oct '11

INVITATION: ================= Please, consider to contribute to and/or forward to the appropriate groups the following opportunity to submit and publish original scientific results to ICNS 2012. The submission deadline is extended to November 16, 2011. In addition, authors of selected papers will be invited to submit extended article versions to one of the IARIA Journals: http://www.iariajournals.org ================= ============== ICNS 2012 | Call for Papers =============== CALL FOR PAPERS, TUTORIALS, PANELS ICNS 2012, The Eighth International Conference on Networking and Services March 25-29, 2012 - St. Maarten, The Netherlands Antilles General page: http://www.iaria.org/conferences2012/ICNS12.html Call for Papers: http://www.iaria.org/conferences2012/CfPICNS12.html - regular papers - short papers (work in progress) - posters - ideas Submission page: http://www.iaria.org/conferences2012/SubmitICNS12.html Submission deadline: November 16, 2011 Sponsored by IARIA, www.iaria.org Extended versions of selected papers will be published in IARIA Journals: http://www.iariajournals.org Please, note the Poster and Work in Progress options. The topics suggested by the conference can be discussed in term of concepts, state of the art, research, standards, implementations, running experiments, applications, and industrial case studies. Authors are invited to submit complete unpublished papers, which are not under review in any other conference or journal in the following, but not limited to, topic areas. All tracks are open to both research and industry contributions, in terms of Regular papers, Posters, Work in progress, Technical/marketing/business presentations, Demos, Tutorials, and Panels. Before submission, please check and conform with the Editorial rules: http://www.iaria.org/editorialrules.html ICNS 2012 Topics (topics and submission details: see CfP on the site) ENCOT: Emerging Network Communications and Technologies Access and home networks; Ad hoc networks; Application-specific networks (e.g. SANs); Autonomic Networks; Delay-tolerant Networking; Distributed communications systems & applications; Energy-efficient networking; High-speed & optical networks; Mobile networking and systems; MPLS-VPN & IPSec-VPN networks; Multimedia and multicast communications; Networking Communication theory; Network modeling & simulation; Network monitoring techniques; Network security; Next Generation Networks (NGN); Overlay networks; Peer-to-peer networking; Programmable and Active Networks; Sensor networks; Switching and routing; Wireless and Satellite Networks COMAN: Network Control and Management Network, control and service architectures; Network signaling, pricing and billing; Network middleware; Network management, monitoring and control; Network resource scheduling; Networks policy-based management; Management of autonomic networks and systems; Telecommunication networks architectures; On-demand networks, utility computing architectures; Applications and case studies SERVI: Multi-technology service deployment and assurance Service-oriented architectures; Service definition, creation, bundling, deployment; Service reuse, composition and service feature interaction; Service orchestration and federation; Inter-provider service dependency; Intra-provider service dependency and service interaction; Service middleware and service development platforms (SDPs); Service open architecture (SOA); Profiling and service adaptation; Service privacy and security; Quality of service, service level agreement [QoS/SLA]; Service agreement violations; Mobile services and service migration; Reliability, availability, serviceability [RAS]; Service performance metrics; Traffic engineering, metering, monitoring; Voice over IP services; IP Multimedia services; Real-time/not-real-rime services; real-time services over IP/IPv6; Service performance evaluation, tools, simulation NGNUS: Next Generation Networks and Ubiquitous Services Methodologies, development support, and tools for NGN and converging services; NGN and convergence of ubiquitous services; NGN frameworks, architectures, and concepts; NGN technologies and mechanisms; QoS/SLA, traffic in NGN; NGN transport/service layered capabilities and operations; NGN concepts for active, ad hoc, mobile, and wireless networks; 3G and 4G Mobile networks; Fixed/mobile networks integration and internetworking; Services and service differentiation over NGN; Managing ubiquitous services in NGN; NGN interworking, non-NGN interoperability, migration; Regulatory services in NGN and standard activities; NGN device instrumentation; NGN policy-based control; Next Generation Internet MPQSI: Multi Provider QoS/SLA Internetworking Architectures, frameworks, mechanisms for admission control and measurement; QoS in multi-provider and multi-technology networks; Service classes and multi-provider service class discovery; Service level agreement and service assurance in multi-provider environments; Carrier-class end-to-end SLA and QoS monitoring and management; Multi provider accounting/billing/cost sharing; Management, monitoring, and measurements in multi-provider networks; End-to-end QoS/SLA advanced network services in multi-provider networks; End-to-end QoS/SLA for multimedia applications and services in multi-provider networks; Security issues in multi-service provider networks; Business models for multi-providers under QoS/SLA constraints; Standards and fora activities GRIDNS: Grid Networks and Services GRID theory, frameworks, methodologies, architecture, ontology; GRID infrastructure and technologies; GRID middleware; GRID protocols and networking; GRID computing, utility computing, autonomic computing, metacomputing; Programmable GRID; Data GRID; Context ontology and management in GRIDs; Distributed decisions in GRID networks; GRID services and applications; Virtualization, modeling, and metadata in GRID; Resource management, scheduling, and scalability in GRID; GRID monitoring, control, and management; Traffic and load balancing in GRID; User profiles and priorities in GRID; Performance and security in GRID systems; Fault tolerance, resilience, survivability, robustness in GRID; QoS/SLA in GRID networks; GRID fora, standards, development, evolution; GRID case studies, validation testbeds, prototypes, and lessons learned EDNA: Emergency Services and Disaster Recovery of Networks and Applications Theory on disaster-tolerant robust networks; Recovery by disruption resource procedures; Security issues with emergency services and disaster recovery; Networks resiliency methods; Formal methods for safety-critical systems; Networks emergency services; Public safety, reliable emergency communications, and applications; Response to the networks emergency services; Disaster prevention and recovery; Fighting mechanisms for disaster of networks and applications; Notifications and recovery in various network technologies; Customer protection and serviceability perception; Cost models and business impact; Cultural and legal aspects; Future advanced network development and evolution; Standards and guidelines; Lawful interception and defense strategies; IPv6DFI: Deploying the Future Infrastructure IP Upgrade - An Engineering Exercise or a Necessity?; Worldwide IPv6 Adoption - Trends and Policies; National Strategies in Stimulating IPv6 Adoption; IPv6 in Government Infrastructures - Specific Requirements; IPv6 Infrastructures for Emergency Response and Law Enforcement - MetroNet6; Communications Equipment Certification for IPv6 Support; IPv6 in Broadband Networks; IPv6 Programs, from Research to Knowledge Dissemination; IPv6 Technology - Practical Information; Advanced Topics and Latest Developments in IPv6; IPv6 Deployment Experiences and Case Studies; IPv6 Enabled Applications and Devices IPDy: Internet Packet Dynamics Measurement of stream characteristics (reordering, delay, losses, jitter, etc.); Measurement and estimation of network characteristics; Tools, metrics and benchmarks; End-to-end packet dynamics; Timing aspects in packet dynamics; Impact of load balancing, parallelism within nodes, etc. on packet dynamics; QoS mechanisms and their impact on packet dynamics; Models (e.g., relating protocols, resources and architectures to packet dynamics); Mitigation of adverse effects of reordering, jitter, etc.; Traffic engineering; Impact of packet dynamics on application performance GOBS: GRID over Optical Burst Switching Networks Terabit burst switching; Burst assembly for IP DiffServ over optical burst switching networks; Optical network infrastructure for Grid; Synchronous stream optical burst switching; Optical burst switching based GRID architecture; Reliable optical burst switching for next-generation Grid networks; Throughput for Grid optical burst switching Grid networks; Resiliency paths over the optical Grid networks; Consumer oriented Grids using optical burst switching; Protocols for optical burst switched Grid networks; Hybrid optical switching for data-intensive media Grid; Anycast routing in optical burst switched Grid networks; Optical burst switching for IP-over-WDM/DWDM; Customizable Grid-to-optical network; Ultra high capacity optical networks; Hybrid optical burst/circuit switched for Grid-enabled optical networks; Job scheduling in optical burst switching Grid networks; Architecture and middleware for Grid-Over-OBS ---------------------------------- Committee: http://www.iaria.org/conferences2012/ComICNS12.html ====================

1 0