From david.kessens at nokia.com Wed Jun 1 05:38:02 2005 From: david.kessens at nokia.com (David Kessens) Date: Tue, 31 May 2005 20:38:02 -0700 Subject: [ipv6-wg@ripe.net] Minutes from IPv6 WG - RIPE 49 Message-ID: <20050601033802.GC12141@nokia.com> Please see below for the final minutes of our session during RIPE 49. The minutes are mostly the same as the v1 draft minutes that were posted earlier. Only differences are a typo fix and an improved summary of Jordi's presentation on 'Guidelines for ISPs on IPv6 Assignments to Customers'. I will sent out the draft minutes for our meeting during RIPE 50 in a couple of minutes. David Kessens --- Minutes from IPv6 WG - RIPE 49 RIPE 49 Manchester IPv6 Working Group Wednesday 22 September 2004 WG Chair David Kessens Scribe Adrian Bedford (RIPE NCC) Attendees: 121 Administration and Agenda Presented by David Kessens Adrian Bedford of the RIPE NCC was appointed scribe. Agenda was agreed Minutes from both RIPE 47 and 48 were approved. Update from the RIPE NCC Presented by Andrei Robachevsky, RIPE NCC As of August, k-root is IPv6 enabled The new version of the RIPE website (to be launched shortly) will also be IPv6 enabled. An Overview of the Global IPv6 Routing Table Presented by Gert Doering (Spacenet) A number of anomalies have been observed in the Global IPv6 Routing table, though in most cases these could be explained by traffic engineering, internal transitions and in one case a prefix leak. One person used the Jabber Remote Feedback system to ask why IXPs are announcing /48s with no export. It was explained that, for example, AMSIX doesn't want it's neighbors to make it's prefix globally visible. It remains a contentious issue as to whether something should be globally visible. What are the Deployment Plans Behind the Larger IPv6 Allocations? Presented by: Mikael Lind (TeliaSonera) David Kessens asked whether there were plans to allocate /64s for mobile use. Mikael confirmed that this was likely and that TeliaSonera was also looking at /48s for this use. Kurtis Lindqvist asked whether TeliaSonera has been talking with vendors to co-ordinate hardware and equipment. Mikael explained that this has not yet happened, as they feel right now there is little incentive to do so. David asked if Mikael would consider returning to a future RIPE Meeting to provide an update when TeliaSonera is further along in the development and deployment process, Mikael indicated that he would be happy to do so. Deployment Plans Behind Larger IPv6 Allocations Presented by Jordi Palet (Consulintel) Jordi will continue to keep the Working Group posted on feedback. He will also encourage non-respondents to contribute. Geant IPv6 Presented by Jordi Palet (Consulintel) Guidelines for ISPs on IPv6 Assignments to Customers Presented by Jordi Palet (Consulintel) This presentation provided an initial attempt on creating guidelines on how to interpret the official ipv6 assignment policy in practical terms. < BREAK > IPv6 Glue for the Root Nameservers Presented by Johan Ihr?n (Autonomica) Iljitsch van Beijnum asked how long the process is likely to take. Johan commented that it would depend on who was prepared to take on the task, Johan is willing to do this, though added that nothing is root server specific, if people argue that we need v6 glue now, then they should step up and offer to help out. There is no specific target date for this to happen, since testing needs to be completed. Randy Bush asked that since we tend to assume that we should upgrade when something breaks, how is he to know when something has in fact broken. How, as an operator will he actually know there is something wrong? Johan agreed with Randy, there needs to be an agreed process. This could mean that things may not happen universally at the same time. Much will depend on the level of ambition of those involved - the tasks could be more or less complex. Gert Doering commented that as we see ccTLDs adding v6 glue, they might already know some of the issues that could arise. He suggested that someone speak to the ccTLD Operators and find someone who is willing to help with testing. It was also suggested that prudence might be a good idea. If a ccTLD Operator decides to deploy v6 transitions to their nameservers, in the end it will be their own decision. A question was asked about whether anything could be done to improve I-root connectivity to Europe. Johan commented that this would fall into his domain and promised to provide more feedback on this by RIPE 50. Bill Manning commented that the group appeared to be talking as if testing had not in fact started, whereas people are doing tests, ccTLD Operators at already looking at the impacts of these tests. A timeframe was agreed at the last ISOC meeting to finish testing before their next report at the end of the year, enabling a report to made to ICANN. One obstacle here is that the last report to the ICANN board took six months to have approved. Doug Barton of ICANN commented that the process has been streamlined and lessons learned, it is felt that any such future report would receive a far quicker response. David Kessens asked if all root servers planned to have IPv6 connectivity at the same time. Johan replied that he thought it unlikely that everyone would approach this in the same way, adding that he felt diversity was not a bad thing. It would, he said, be likely that we would see some TLDs using basic glue with others holding off during the early phases. The day when we will see the v6 glue globally is still somewhere in the distant future as there are no specific plans at this point to co-ordinate such a deployment. To date eight have basic glue in place. David asked if this community could help and Johan said he felt it certainly could. There was discussion about asking the RIPE NCC for help, though Johan this was not necessary at this stage. From his point of view he did not feel the issue was who did this, rather thought needed to be given to identifying which tests are relevant. Time would need to be taken over inventory to find out what code is already out there. David rounded up the discussion by saying that volunteers would be welcomed, though this was not be taken as a specific action point. An Update on Multihoming in IPv6 Presented by Geoff Huston (APNIC) A comment was made that the slide detailing issues appeared to not consider the update rates for bindings and third party referrals. Geoff said that design decisions should avoid relying on DNS. Randy Bush commented that there had been some mission drift from multi-homing to mobility. A comment was made that if an opportunistic solution does not meet all the needs in the architecture, you are forced to use a structured identifier. Such an identifier would have to be unique to avoid collisions. This could give rise to a very complex registration infrastructure, which might be painful to administer. Geoff replied that uniqueness never comes cheap and needs enormous effort at a global level. This lead to a suggestion that it may be preferable to choose opportunistic styles. Geoff felt that this was down to personal taste; there were certainly benefits in avoiding global costs if set up problems could be avoided. A suggestion was made that we should consider developing a whole new protocol that could handle routing table growth, Geoff replied that it would be ideal to think that we could do both, groups do exist with experience in both fields. The IETF have working groups that work together to engineer solutions and ensure routing tables do not become too complex. Geoff agreed that many people do feel routing could provide a better answer Kuris Lindqvist pointed to work that had been done during an interim meeting in Santa Monica in June 2004, this looked at the architectural work done by Geoff and the 30-40 drafts submitted. The drafts were split into four or five categories and based upon these; a simple poll was carried out. In some categories, the authors withdrew their proposals and in others, there was little support. The consensus was that the architecture proposed by Geoff was the way the group wished to move forward at the moment. A speaker announced that he had prepared a draft on the use of PI to reduce pressures on routing tables, intended as a compromise and is accepting comments on this. A speaker added that during his presentation Geoff dismissed mobile IP for security and state management reasons. The IETF has already addressed security and state management could throw up more problems. He felt that having two solutions for these issues problem was unwise and we need to work towards a single solution for what seem like related problems. He felt that using security, as a reason to reject the architecture draft was a red herring. Geoff pointed out that this is not yet in the draft, though will be in the next version. Geoff agreed that some of the assumptions we made previously in mobile IPv6 now seem less secure. Security locators assume a stable home base - if it fails, everything else fails. Multi6 looks at the ?homeless vagrants? of the world that do not have a home all of the time and the home is not reachable. It then assumes that there is not a home locator that can always be contacted. The Multi6 team looked at the other approaches and aimed to learn from them. He remains unsure if this kind of binding works in mobile environments, it is far too early to make this assessment. David Kessens asked whether the group found updates from Multi6 useful, Kurtis suggested that it would be nice to have Geoff make a similar presentation in future Address Policy Working Group Sessions too. Gert Doering suggested that as co-chair of the Address Policy Working Group, he would like to see the drafts on PI Addressing discussed through the Address Policy Mailing List. Moonv6 Update Presented by Jim Bound Kurtis Lindqvist asked whether security testing had been carried out in an isolated test environment. Jim clarified that filters had only been tested on IPv6 ports, addresses and protocols. He added that it showed there was confusion. Just because dual stack is not a security problem, IPv6 in itself is not an insecure protocol. Intrusion detection needs to be included into work. Kurtis asked what stage of the evolution process the project had reached. Jim replied that in this respect, research was still quite basic. Deploying 5,000 IPv6 Sites - XTEC Presented by Jordi Palet (Consulintel) Input to RIPE NCC Activity Plan Presented by David Kessens David asked if the group had any items to include in the 2005 RIPE NCC Activity Plan. There was no response. From david.kessens at nokia.com Wed Jun 1 05:42:40 2005 From: david.kessens at nokia.com (David Kessens) Date: Tue, 31 May 2005 20:42:40 -0700 Subject: [ipv6-wg@ripe.net] Draft Minutes (v1) IPv6 WG RIPE 50 Message-ID: <20050601034240.GD12141@nokia.com> Please see below for our first cut of the minutes for our working group session during RIPE 50. Please let me know if you have any comments or corrections. The minutes will be declared final by Friday, June 10, 2005 if no significant changes (other than typo fixes and minor editorial issues) are found. David Kessens --- Draft Minutes (v1) IPv6 WG RIPE 50 When: Friday, 6 May 2005, 09:00 - 10:30 Where: C58, Clarion Hotel, Stockholm, SE Minute Taker: Adrian Bedford Quick Update from the RIPE NCC Regarding IPv6 Services (Ruud de Kooter - RIPE NCC) After the presentation, Ruud was asked if there were plans to integrate the IPv6 whois interface with the main whois. Currently the proxy cannot talk to the interface and this hampers some functionality (such as rate limiting). Ruud asked Shane Kerr to answer this. Shane explained that the RIPE NCC has a v6 proxy running over a v4 database backend. The RIPE NCC has been looking at how people use the database for two years and patterns suggest that now would be a good time to integrate native IPv6 into the server using /48 as a client identifier. Discussion on: Global IPv6 Routing Table Status (Gert Doering, Spacenet) Gert indicated that the Routing Working Group was discussing best practices for BGP filters. The overall thrust of the presentation was that v6 is growing smoothly with no big disasters so far. A question was asked about ratio comparison between the numbers of Autonomous Systems (AS) announced by IPv6 networks as opposed to v4. The current data suggests that there are 1.419 announced entries per originating AS for v6 and 10.308 for v4. A point was made that Deutsche Telecom (DT), who have one of the largest v6 allocations made to date would not announce their block as one AS, they would be more likely to split this and allocate blocks to different service providers for political reasons. Someone from DT commented that the company has the right to do this, though denied that the move was in any way politically motivated. Renumbering IPv6 Networks (Stig Venaas, Uninett & Tim Chown, University of Southampton) After the presentation, it was mentioned that we are assuming that customers of service providers will keep their space, yet ten years ago major providers did force renumbering onto customers. It was agreed that renumbering of IPv6 is, at least in principal, no different to what happened with v4. Developments/Initiatives Regarding IPv6 in the RIPE Region and Beyond - Francis Dupont: Point6 (http://www.point6.net/ - Gert Doering: A new maillist for discussion of ipv6 operational issues was started: http://lists.cluenet.de/mailman/listinfo/ipv6-ops/ After the announcement of the list, it was agreed that having a publicly available archive of this new list would be a good idea. Although it exists on the site that hosts the list, this is a personal website and for stability purposes, maybe a copy of the archive should be placed elsewhere. It was felt that the RIPE website was unsuitable for this. - Carlos Friacas: o IPv6 - Advanced Network Developments's first year in Portugal o 9K IPv6 Schools' Network Initiative o About the IPv6 Steering Committee Revisiting the /48 recommendation There was a lengthy discussion around RFC 3177. It was made clear that the discussion was not intended to reach final consensus on all the issues involved, but merely to serve as a way to get an idea about the general direction on where the community would like to go to make it possible to write up an initial proposal. Many agreed that the /48 is too much for many users for now and in the future. A discussion followed about how we should define a site with the suggestion that we need to accept that this can remain a grey area, which is not at all well defined right now. Discussion is needed around this topic, though the group tended to accept that it might not be easy to put down limits in black and white. Most people in the room felt that RFC3177 needs a revision. Most people felt that the /48 limit itself doesn't need to be changed, but most agreed that there is a need for a new category that falls somewhere between /48 and /64 for users that have a need for subnetting but for which a /48 seems excessive. This category would fit the mass consumermarket or (very) small office market, however, it was noted that we should base the category on technical needs of the user, not in economic terms like mass consumer market. It is exepected that an Internet Draft will be written that can be discussed at RIPE 51. From leo at ripe.net Wed Jun 1 07:49:51 2005 From: leo at ripe.net (leo vegoda) Date: Wed, 1 Jun 2005 07:49:51 +0200 Subject: [ipv6-wg@ripe.net] documenting RIPE critical infrastructure/micro allocations In-Reply-To: References: Message-ID: <9BF97610-ADF1-4168-9ACA-2455FC7407DE@ripe.net> Hi, On May 31, 2005, at 11:28 am, Bjoern A. Zeeb wrote: [...] > For RIPE Gert's page is talking about 2001:7F8::/29 and the DB entry. > > | http://www.ripe.net/whois?searchtext=EU-ZZ-2001-07F8 > | http://www.ripe.net/ripe/docs/ipv6-policy-ixp.html > > Could someone add documentation/web page stating that RIPE is > doing /48 assignments from this Block for critical infrastructure > (read: IXPs)? All the assignments we make to IXPs come from 2001:7f8::/32. For the time being, the easiest way to get a complete list of the assignments we have made is to go here: http://www.ripe.net/whois?-rm+2001%3A7f8%3A%3A%2F32 or do a query like this: $ whois -h whois.ripe.net -rm 2001:7f8::/32 | grep ^inet6num (note that we've made one /64 assignment) We have also made assignments to two root DNS server operators ('K' 2001:07FD::/32 & 'I' 2001:07FE::/32). I'm sure that we can add this information to this document (or something similar): https://www.ripe.net/ripe/docs/smallest-alloc-sizes.html if it would be useful to people. > Perhaps also giving a list of which prefixes got assigned already as > these won't show up in delegated-ripencc-latest. That's something that should change later in the year. We're working on improvements in this area at the moment. Regards, -- leo vegoda Registration Services Manager RIPE NCC From sabt at sabt.net Wed Jun 1 11:15:43 2005 From: sabt at sabt.net (Sebastian Abt) Date: Wed, 1 Jun 2005 11:15:43 +0200 Subject: [ipv6-wg@ripe.net] documenting RIPE critical infrastructure/micro allocations In-Reply-To: <9BF97610-ADF1-4168-9ACA-2455FC7407DE@ripe.net> References: <9BF97610-ADF1-4168-9ACA-2455FC7407DE@ripe.net> Message-ID: <20050601091543.GC887@shiva.sabt.net> Hi, * leo vegoda wrote: > >Could someone add documentation/web page stating that RIPE is > >doing /48 assignments from this Block for critical infrastructure > >(read: IXPs)? [..] > I'm sure that we can add this information to this document (or > something similar): > > https://www.ripe.net/ripe/docs/smallest-alloc-sizes.html > > if it would be useful to people. I'd also appreciate having such a listing of critical infrastructure assingments / micro-allocations somewhere on the RIPE website, as it would simplify building/updating/justifying own filters. regards, sebastian -- SABT-RIPE PGPKEY-D008DA9C From leo at ripe.net Wed Jun 1 21:05:27 2005 From: leo at ripe.net (leo vegoda) Date: Wed, 1 Jun 2005 21:05:27 +0200 Subject: [ipv6-wg@ripe.net] documenting RIPE critical infrastructure/micro allocations In-Reply-To: <429D8CFE.8080909@cc.univie.ac.at> References: <9BF97610-ADF1-4168-9ACA-2455FC7407DE@ripe.net> <20050601091543.GC887@shiva.sabt.net> <429D8CFE.8080909@cc.univie.ac.at> Message-ID: <74F39279-99B8-4FD8-82CE-F7115C291DA6@ripe.net> On Jun 1, 2005, at 12:25 pm, Wilfried Woeber, UniVie/ACOnet wrote: [...] >>> I'm sure that we can add this information to this document (or >>> something similar): >>> >>> https://www.ripe.net/ripe/docs/smallest-alloc-sizes.html >>> >>> if it would be useful to people. >>> >> I'd also appreciate having such a listing of critical infrastructure >> assingments / micro-allocations somewhere on the RIPE website, as it >> would simplify building/updating/justifying own filters. >> regards, >> sebastian > > Either the list (dynamically generated!) or just a hint or link to > a whois DB search URL like the one(s) proposed by Leo? Links to a search mechanism can be published quickly. It will take a little more time to develop a mechanism for dynamic reporting. I'm not sure what sort of dynamic data people would want and I'm not sure if people need a web page or something else. Regards, -- leo vegoda Registration Services Manager RIPE NCC -------------- next part -------------- An HTML attachment was scrubbed... URL: From woeber at cc.univie.ac.at Wed Jun 1 12:25:02 2005 From: woeber at cc.univie.ac.at (Wilfried Woeber, UniVie/ACOnet) Date: Wed, 01 Jun 2005 10:25:02 +0000 Subject: [ipv6-wg@ripe.net] documenting RIPE critical infrastructure/micro allocations In-Reply-To: <20050601091543.GC887@shiva.sabt.net> References: <9BF97610-ADF1-4168-9ACA-2455FC7407DE@ripe.net> <20050601091543.GC887@shiva.sabt.net> Message-ID: <429D8CFE.8080909@cc.univie.ac.at> Sebastian Abt wrote: > Hi, > > * leo vegoda wrote: [...] > [..] > >>I'm sure that we can add this information to this document (or >>something similar): >> >>https://www.ripe.net/ripe/docs/smallest-alloc-sizes.html >> >>if it would be useful to people. > > > I'd also appreciate having such a listing of critical infrastructure > assingments / micro-allocations somewhere on the RIPE website, as it > would simplify building/updating/justifying own filters. > > regards, > sebastian Either the list (dynamically generated!) or just a hint or link to a whois DB search URL like the one(s) proposed by Leo? A static document or web page is maybe less adequate here - unless the HostMasters can or prefer to integrate updating the document/page as part of performing an assignment? Wilfried. From gert at space.net Thu Jun 2 11:14:45 2005 From: gert at space.net (Gert Doering) Date: Thu, 2 Jun 2005 11:14:45 +0200 Subject: [ipv6-wg@ripe.net] documenting RIPE critical infrastructure/micro allocations In-Reply-To: <9BF97610-ADF1-4168-9ACA-2455FC7407DE@ripe.net> References: <9BF97610-ADF1-4168-9ACA-2455FC7407DE@ripe.net> Message-ID: <20050602091445.GV84850@Space.Net> Hi, On Wed, Jun 01, 2005 at 07:49:51AM +0200, leo vegoda wrote: > I'm sure that we can add this information to this document (or > something similar): > > https://www.ripe.net/ripe/docs/smallest-alloc-sizes.html > > if it would be useful to people. Yes. Please do so. Gert Doering -- NetMaster -- Total number of prefixes smaller than registry allocations: 71007 (66629) SpaceNet AG Mail: netmaster at Space.Net Joseph-Dollinger-Bogen 14 Tel : +49-89-32356-0 D- 80807 Muenchen Fax : +49-89-32356-234 From iljitsch at muada.com Thu Jun 2 18:12:23 2005 From: iljitsch at muada.com (Iljitsch van Beijnum) Date: Thu, 2 Jun 2005 18:12:23 +0200 Subject: [ipv6-wg@ripe.net] documenting RIPE critical infrastructure/micro allocations In-Reply-To: <429D8CFE.8080909@cc.univie.ac.at> References: <9BF97610-ADF1-4168-9ACA-2455FC7407DE@ripe.net> <20050601091543.GC887@shiva.sabt.net> <429D8CFE.8080909@cc.univie.ac.at> Message-ID: On 1-jun-2005, at 12:25, Wilfried Woeber, UniVie/ACOnet wrote: >> I'd also appreciate having such a listing of critical infrastructure >> assingments / micro-allocations somewhere on the RIPE website, as it >> would simplify building/updating/justifying own filters. > Either the list (dynamically generated!) or just a hint or link to > a whois DB search URL like the one(s) proposed by Leo? The microallocations are easily generated from the allocations files: http://www.bgpexpert.com/v6micro.php However, this doesn't include any information on criticalness. Also note that there appear to be no RIPE microallocations currently. From leo at ripe.net Thu Jun 2 18:33:52 2005 From: leo at ripe.net (leo vegoda) Date: Thu, 2 Jun 2005 18:33:52 +0200 Subject: [ipv6-wg@ripe.net] documenting RIPE critical infrastructure/micro allocations In-Reply-To: References: <9BF97610-ADF1-4168-9ACA-2455FC7407DE@ripe.net> <20050601091543.GC887@shiva.sabt.net> <429D8CFE.8080909@cc.univie.ac.at> Message-ID: <38F2093B-1185-4B53-AF39-DB33C523FE26@ripe.net> On Jun 2, 2005, at 6:12 pm, Iljitsch van Beijnum wrote: [...] > The microallocations are easily generated from the allocations files: > > http://www.bgpexpert.com/v6micro.php > > However, this doesn't include any information on criticalness. > > Also note that there appear to be no RIPE microallocations currently. We don't tend to use the term micro-allocations. We have made 51 assignments to IXPs: 50 were /48 and one was /64. Regards, -- leo vegoda Registration Services Manager RIPE NCC From iljitsch at muada.com Thu Jun 2 18:46:17 2005 From: iljitsch at muada.com (Iljitsch van Beijnum) Date: Thu, 2 Jun 2005 18:46:17 +0200 Subject: [ipv6-wg@ripe.net] documenting RIPE critical infrastructure/micro allocations In-Reply-To: <38F2093B-1185-4B53-AF39-DB33C523FE26@ripe.net> References: <9BF97610-ADF1-4168-9ACA-2455FC7407DE@ripe.net> <20050601091543.GC887@shiva.sabt.net> <429D8CFE.8080909@cc.univie.ac.at> <38F2093B-1185-4B53-AF39-DB33C523FE26@ripe.net> Message-ID: <44304B93-1CD0-4045-BF32-BD941E02D630@muada.com> On 2-jun-2005, at 18:33, leo vegoda wrote: >> Also note that there appear to be no RIPE microallocations currently. > We don't tend to use the term micro-allocations. We have made 51 > assignments to IXPs: 50 were /48 and one was /64. There are no /48s or /64s in ftp://ftp.ripe.net/ripe/stats/delegated- ripencc-latest From david.kessens at nokia.com Sat Jun 18 04:26:09 2005 From: david.kessens at nokia.com (David Kessens) Date: Fri, 17 Jun 2005 19:26:09 -0700 Subject: [ipv6-wg@ripe.net] Minutes IPv6 WG RIPE 50 Message-ID: <20050618022609.GA8274@nokia.com> I did not receive any comments on the draft minutes (v1) by June 10. Therefore, the draft minutes (v1) are now the official minutes of our session during RIPE 50 except for one typo that I found myself, in the last sentence, please replace 'exepected' by 'expected'. Thanks, David Kessens --- ----- Forwarded message from David Kessens ----- Date: Tue, 31 May 2005 20:42:40 -0700 From: David Kessens To: ipv6-wg at ripe.net Cc: meeting at ripe.net Please see below for our first cut of the minutes for our working group session during RIPE 50. Please let me know if you have any comments or corrections. The minutes will be declared final by Friday, June 10, 2005 if no significant changes (other than typo fixes and minor editorial issues) are found. David Kessens --- Draft Minutes (v1) IPv6 WG RIPE 50 When: Friday, 6 May 2005, 09:00 - 10:30 Where: C58, Clarion Hotel, Stockholm, SE Minute Taker: Adrian Bedford Quick Update from the RIPE NCC Regarding IPv6 Services (Ruud de Kooter - RIPE NCC) After the presentation, Ruud was asked if there were plans to integrate the IPv6 whois interface with the main whois. Currently the proxy cannot talk to the interface and this hampers some functionality (such as rate limiting). Ruud asked Shane Kerr to answer this. Shane explained that the RIPE NCC has a v6 proxy running over a v4 database backend. The RIPE NCC has been looking at how people use the database for two years and patterns suggest that now would be a good time to integrate native IPv6 into the server using /48 as a client identifier. Discussion on: Global IPv6 Routing Table Status (Gert Doering, Spacenet) Gert indicated that the Routing Working Group was discussing best practices for BGP filters. The overall thrust of the presentation was that v6 is growing smoothly with no big disasters so far. A question was asked about ratio comparison between the numbers of Autonomous Systems (AS) announced by IPv6 networks as opposed to v4. The current data suggests that there are 1.419 announced entries per originating AS for v6 and 10.308 for v4. A point was made that Deutsche Telecom (DT), who have one of the largest v6 allocations made to date would not announce their block as one AS, they would be more likely to split this and allocate blocks to different service providers for political reasons. Someone from DT commented that the company has the right to do this, though denied that the move was in any way politically motivated. Renumbering IPv6 Networks (Stig Venaas, Uninett & Tim Chown, University of Southampton) After the presentation, it was mentioned that we are assuming that customers of service providers will keep their space, yet ten years ago major providers did force renumbering onto customers. It was agreed that renumbering of IPv6 is, at least in principal, no different to what happened with v4. Developments/Initiatives Regarding IPv6 in the RIPE Region and Beyond - Francis Dupont: Point6 (http://www.point6.net/ - Gert Doering: A new maillist for discussion of ipv6 operational issues was started: http://lists.cluenet.de/mailman/listinfo/ipv6-ops/ After the announcement of the list, it was agreed that having a publicly available archive of this new list would be a good idea. Although it exists on the site that hosts the list, this is a personal website and for stability purposes, maybe a copy of the archive should be placed elsewhere. It was felt that the RIPE website was unsuitable for this. - Carlos Friacas: o IPv6 - Advanced Network Developments's first year in Portugal o 9K IPv6 Schools' Network Initiative o About the IPv6 Steering Committee Revisiting the /48 recommendation There was a lengthy discussion around RFC 3177. It was made clear that the discussion was not intended to reach final consensus on all the issues involved, but merely to serve as a way to get an idea about the general direction on where the community would like to go to make it possible to write up an initial proposal. Many agreed that the /48 is too much for many users for now and in the future. A discussion followed about how we should define a site with the suggestion that we need to accept that this can remain a grey area, which is not at all well defined right now. Discussion is needed around this topic, though the group tended to accept that it might not be easy to put down limits in black and white. Most people in the room felt that RFC3177 needs a revision. Most people felt that the /48 limit itself doesn't need to be changed, but most agreed that there is a need for a new category that falls somewhere between /48 and /64 for users that have a need for subnetting but for which a /48 seems excessive. This category would fit the mass consumermarket or (very) small office market, however, it was noted that we should base the category on technical needs of the user, not in economic terms like mass consumer market. It is exepected that an Internet Draft will be written that can be discussed at RIPE 51. ----- End forwarded message -----