From meeting at ripe.net Mon Mar 5 09:51:54 2012 From: meeting at ripe.net (RIPE NCC Meeting Coordinator) Date: Mon, 05 Mar 2012 09:51:54 +0100 Subject: RIPE 64 Draft Plenary Agenda Message-ID: <4F547EAA.6060709@ripe.net> Dear colleague, It's six weeks to go until RIPE 64! We've just posted a preliminary list of talks, tutorials and BoFs: http://ripe64.ripe.net/programme/list-of-talks/ Please check back regularly for updates. Registration, meeting fees, and hotel information can be found at: http://ripe64.ripe.net/ Kind regards, RIPE Meeting team RIPE NCC From tmu at google.com Tue Mar 6 14:54:13 2012 From: tmu at google.com (Todd Underwood) Date: Tue, 6 Mar 2012 08:54:13 -0500 Subject: RIPE 64 Draft Agenda Published Message-ID: All, The RIPE Programme Committee is pleased to announce a first draft of the Plenary Agenda for the upcoming RIPE64 conference. It is available at: http://ripe64.ripe.net/programme/list-of-talks/ The draft agenda is intended to enable people who require travel approval in order to attende RIPE conferences to have some indication of the content that will be presented. It is not at all a final list of presentations for the conference. Approximately half of the plenary presentation slots remain unfilled. If you have a draft of a presentation that you wish to submit for for consideration for one of these slots, please submit it at: https://meetings.ripe.net/pc/ The Programme Committee will publish a final list of presentations shortly before the conference. If you have questions about the process for presenting, please contact the Committee at pc at ripe.net. Looking forward to seeing you all in Ljubljana in April. cheers, -- Todd Underwood for the RIPE Programme Committee tmu at google.com From randy at psg.com Fri Mar 9 07:52:08 2012 From: randy at psg.com (Randy Bush) Date: Fri, 09 Mar 2012 15:52:08 +0900 Subject: defending at layer seven against layer nine attacks Message-ID: yesterday, a few friends asked if someone files in court against your customer and gets a judgment telling the rir to revoke your bgp-speaking customer's certs and roas[0], what the heck happens to your responsibility and/or sla to your customer? what can you do to keep them flying? i believe this is a legitimate concern. one classic example is a russian isp being attacked by a dutch court. of course it could be a canadian being attacked by a virginia court. note that, traditionally, the sla describes a level of service between you and your customer, and its all best effort to the rest of the intertubes. first, the rirs, no matter how well-meaning, can do nothing to help, any thought thereof is a joke. they will not stand up to court orders and people with guns, end of story. and the same goes for well-intentioned schemes where arin backs up ripe's members' rpki data. american (dns) registries have already been used, through us courts, to attack overseas sites. but, note that the decisions routers make are not burned in. by design, they are local policy configured by the operator. rpki- based origin validation merely marks a received bgp announcement as valid, notfound, or invalid. it is up to operator-configured policy to decide how to treat the received announcement based on the validity marking and anything else the operator chooses. so we will use local knowledge of who your customers are to make a local policy decision that you're going to route them no matter what some third party says about them. let's assume you have a prefix filter list for my customer's prefixes (the customer themself, not their bgp speaking customer cone). you do have prefix lists for your customers, don't you [1]? so, your programatically generated template for a customer peering could be something such as the following pretty strict policy: if p in custs-pfxs community add ExportToPeersCustsAndUpstreams if p is marked valid set local-pref 120 elif p is marked notfound set local-pref 100 elif p is marked invalid # layer nine attack set local-pref 120 # maintain g-r fantasy an even more paranoid approach might begin if p in custs-pfxs if p comes from or through an as not my customer's drop it on the floor ... as you surely have customer specific prefix filters in place, you do not risk allowing in invalid attacks sourced by your customer. that this is all supported in the design and in current code from J&C is not an accident. but beware of occasional vendor do-gooder knobs which default to applying policy for you. also check out draft-ietf-sidr-ltamgmt. it explains how to use the rpki tools and tool-sets (i.e. nothing new needed) to have your own view of the world, overriding the iana/rir-based rpki data. this view could include copies of your customers' rpki data. it would also be really helpful to have a seventh registry of good reputation situated in a much less vulnerable jurisdiction, e.g. iceland. we could all use the ltamgt hack to use them as a safety net. otoh, i would also hope that the goons at layers 8-10 would realize that a lot of attacks against the rpki would jeopardize everyone's, including their own, routing security as folk will start to shy away from using it. --- [0] - or forces the rir to create a roa for as 0 [1] - you can construct one from the rpki data, all the roas with the customer's as. if they did not register, then all this makes no difference, their prefixes are always notfound. From no-reply at ripe.net Wed Mar 14 17:28:13 2012 From: no-reply at ripe.net (Axel Pawlik) Date: Wed, 14 Mar 2012 17:28:13 +0100 Subject: Return of Legacy Space Message-ID: <4F60C71D.9080003@ripe.net> Dear colleagues, In preparation for the ratification of "Global Policy for Post Exhaustion IPv4 Allocation Mechanisms by the IANA" (GPP-IPv4-2011) by the ICANN Board of Directors, we will remove from the available pool of IPv4 address space the IPv4 legacy space that has been returned to the RIPE NCC by various members. 1,368,576 IPv4 addresses were removed from the available pool of IPv4 address space on 14 March, 2012. It is intended that any IPv4 legacy space returned to the RIPE NCC will be placed in IANA's Recovered IPv4 Pool. Until now, legacy space returned to the RIPE NCC has been returned to the RIPE NCC's IPv4 available pool but is not re-distributed. By removing the legacy space from the RIPE NCC's IPv4 available pool, a more accurate overview of the actual space that can be distributed can be seen. As legacy space was distributed before the RIR system was introduced, the RIPE NCC does not have any policy governing the re-distribution of returned legacy space. We believe that placing this legacy space in the IANA's Recovered IPv4 Pool for redistribution to the RIRs will contribute to the future well-being of the Internet. The Global Policy can be found at: http://www.ripe.net/ripe/docs/ripe-529 More information about the policy and the ratification process can be found at: http://www.icann.org/en/announcements/announcement-26apr11-en.htm The total amount of available IPv4 space that the RIPE NCC holds can be found at: http://www.ripe.net/internet-coordination/ipv4-exhaustion/ipv4-available-pool-graph Regards, Axel Pawlik Managing Director RIPE NCC From Niall.oReilly at ucd.ie Wed Mar 14 18:01:15 2012 From: Niall.oReilly at ucd.ie (Niall O'Reilly) Date: Wed, 14 Mar 2012 17:01:15 +0000 Subject: Return of Legacy Space In-Reply-To: <4F60C71D.9080003@ripe.net> References: <4F60C71D.9080003@ripe.net> Message-ID: Thanks for this announcement, Axel. I welcome it and have some comments, made in a personal capacity and specifically not to be taken as representing or prejudicing the position of my employer, either actual or future. On 14 Mar 2012, at 16:28, Axel Pawlik wrote: > 1,368,576 IPv4 addresses were removed from the available pool of IPv4 address space on 14 March, 2012. May I suggest announcing the prefixes involved on ripe-list at ripe.net. This would not only achieve a reasonable approximation to full disclosure, but also provide protection against any error which might cause trouble. > It is intended that any IPv4 legacy space returned to the RIPE NCC will be placed in IANA's Recovered IPv4 Pool. Fine. > Until now, legacy space returned to the RIPE NCC has been returned to the RIPE NCC's IPv4 available pool but is not re-distributed. Good to know (or be reminded of). > By removing the legacy space from the RIPE NCC's IPv4 available pool, a more accurate overview of the actual space that can be distributed can be seen. This improved accuracy is much to be desired, I think. > As legacy space was distributed before the RIR system was introduced, > the RIPE NCC does not have any policy governing the re-distribution of > returned legacy space. We believe that placing this legacy space in the IANA's Recovered IPv4 Pool for redistribution to the RIRs will contribute to the future well-being of the Internet. Makes sense to me. Best regards, Niall O'Reilly From no-reply at ripe.net Thu Mar 15 09:56:19 2012 From: no-reply at ripe.net (RIPE Meeting) Date: Thu, 15 Mar 2012 09:56:19 +0100 Subject: RIPE 64 Updates: Hotel Discount Expires, Meeting Programme Online, Social Events and RIPE NCC's 20th Anniversary In-Reply-To: <4F609E5E.9000205@ripe.net> References: <4F609E5E.9000205@ripe.net> Message-ID: <4F61AEB3.4020907@ripe.net> Dear colleagues, RIPE 64 is just over four weeks away. We'd like to share the following news with you: ========================== Hotel Room Discount Expires Tomorrow ========================== If you'd like to take advantage of the early bird room discount offered by the meeting venue hotel, please book your room by Friday, 16 March: http://ripe64.ripe.net/venue/meeting-venue/ ======================== Meeting Programme Online ======================== You can view the meeting programme at: http://ripe64.ripe.net/programme/meeting-plan/ A preliminary list of talks, tutorials and BoFs is available at: http://ripe64.ripe.net/programme/list-of-talks/ ======================== Social Events Posted ======================== RIPE 64 social event sponsors have organised excellent socials for RIPE 64 attendees including a cave tour and a RIPE Dinner in Ljubljana Castle. More details about RIPE 64 social events are available at: http://ripe64.ripe.net/programme/social-events/ ======================== Celebrate RIPE NCC's 20th Anniversary ======================== The RIPE NCC turns 20 this year and we'll be marking this special occasion at RIPE 64 with special presentations in the Plenary and at the RIPE Dinner. We hope you like cake! We look forward to seeing you in Ljubljana. Kind regards, The RIPE Meeting Team RIPE NCC From nick at ripe.net Thu Mar 15 11:07:19 2012 From: nick at ripe.net (Nick Hyrka) Date: Thu, 15 Mar 2012 11:07:19 +0100 Subject: [coms] Return of Legacy Space In-Reply-To: References: <4F60C71D.9080003@ripe.net> Message-ID: <4F61BF57.7080106@ripe.net> Hello Niall, Thank you for your feedback. Here is the list of prefixes involved: 128.201.0.0/16 131.196.0.0/16 137.59.0.0/16 139.26.0.0/16 139.28.0.0/16 139.5.0.0/16 144.168.0.0/16 147.78.0.0/16 149.248.0.0/16 150.107.0.0/16 150.129.0.0/16 150.242.0.0/16 152.89.0.0/16 154.16.0.0/16 161.123.0.0/16 192.140.1.0-192.144.73.255 192.144.78.0-192.145.230.255 Regards, Nick Hyrka Communications Manager RIPE NCC On 3/14/12 6:01 PM, Niall O'Reilly wrote: > Thanks for this announcement, Axel. > > I welcome it and have some comments, made in a personal capacity and > specifically not to be taken as representing or prejudicing the > position of my employer, either actual or future. > > On 14 Mar 2012, at 16:28, Axel Pawlik wrote: > >> 1,368,576 IPv4 addresses were removed from the available pool of IPv4 address space on 14 March, 2012. > > May I suggest announcing the prefixes involved on ripe-list at ripe.net. > This would not only achieve a reasonable approximation to full disclosure, > but also provide protection against any error which might cause trouble. > >> It is intended that any IPv4 legacy space returned to the RIPE NCC will be placed in IANA's Recovered IPv4 Pool. > > Fine. > >> Until now, legacy space returned to the RIPE NCC has been returned to the RIPE NCC's IPv4 available pool but is not re-distributed. > > Good to know (or be reminded of). > >> By removing the legacy space from the RIPE NCC's IPv4 available pool, a more accurate overview of the actual space that can be distributed can be seen. > > This improved accuracy is much to be desired, I think. > >> As legacy space was distributed before the RIR system was introduced, >> the RIPE NCC does not have any policy governing the re-distribution of >> returned legacy space. We believe that placing this legacy space in the IANA's Recovered IPv4 Pool for redistribution to the RIRs will contribute to the future well-being of the Internet. > > Makes sense to me. > > > Best regards, > Niall O'Reilly > > > > From tore.anderson at redpill-linpro.com Fri Mar 16 08:54:01 2012 From: tore.anderson at redpill-linpro.com (Tore Anderson) Date: Fri, 16 Mar 2012 08:54:01 +0100 Subject: Return of Legacy Space In-Reply-To: <4F60C71D.9080003@ripe.net> References: <4F60C71D.9080003@ripe.net> Message-ID: <4F62F199.3040007@redpill-linpro.com> * Axel Pawlik > Until now, legacy space returned to the RIPE NCC has been returned to > the RIPE NCC's IPv4 available pool but is not re-distributed. By > removing the legacy space from the RIPE NCC's IPv4 available pool, a > more accurate overview of the actual space that can be distributed can > be seen. > The total amount of available IPv4 space that the RIPE NCC holds can be > found at: > http://www.ripe.net/internet-coordination/ipv4-exhaustion/ipv4-available-pool-graph Thanks, having accurate data published is a good thing. That said, the page linked to says: The number of IPv4 addresses shown includes the 8.45 million IPv4 addresses temporarily set aside for the De-Bogonising New Address Blocks project. Which blocks are those, specifically? I could only locate delegations accounting for about half of them (185/10, 128/16, and 84.205.64/19). Best regards, -- Tore Anderson Redpill Linpro AS - http://www.redpill-linpro.com From robachevsky at isoc.org Mon Mar 19 11:04:29 2012 From: robachevsky at isoc.org (Andrei Robachevsky) Date: Mon, 19 Mar 2012 11:04:29 +0100 Subject: Fwd: [ENOG PC] ENOG3 Call for Presentations In-Reply-To: <4F4F1999.4090805@isoc.org> References: <4F4F1999.4090805@isoc.org> Message-ID: <4F6704AD.8030503@isoc.org> Colleagues, This is FYI. If you have an interesting topic to present at ENOG 3 (Euroasia Network Operators' Group) that will take place in Odessa, Ukraine 22-23 May 2012, please be aware that the deadline for full consideration of submitted talks is approaching. Below is a Call for Presentations. Regards, Andrei Robachevsky on behalf of the ENOG3 PC -------- Original Message -------- Dear colleague, Would you like to suggest a presentation topic for ENOG 3? The ENOG Programme Committee is now calling for presentation proposals from the community. The key themes for ENOG 3 are peering, interconnection and collaboration between Internet service providers (ISPs). We?ll cover challenges, tools, experiences and best practices in the following areas: * Peering and Internet Exchange Points * Network Operations and Security * IPv6 deployment * Internet development trends * Internet governance and regulatory practices * Content delivery *How to propose* If you?d like to suggest a presentation for the ENOG 3 agenda, then please submit your talk at: http://www.enog.org/meetings/enog-3/submit-a-topic/ If you are aware of a good presentation and would like to recommend the speaker - please contact the Programme Committee at pc at enog.org. Please submit your talk, including the abstract and draft version of the slides before *26 March 2012* for full consideration. As the conference is bi-lingual, your proposal can be submitted in English or Russian. Presentations can also be given in English or Russian as we use simultaneous translation. Please note that marketing and commercial content will not be accepted. Kind regards, Andrei Robachevsky Chair ENOG 3 Programme Commitee From meeting at ripe.net Thu Mar 22 15:26:08 2012 From: meeting at ripe.net (RIPE NCC Meeting Coordinator) Date: Thu, 22 Mar 2012 15:26:08 +0100 Subject: RIPE 64: Plenary agenda posted Message-ID: <4F6B3680.4010009@ripe.net> Dear colleagues, RIPE 64 is just over three weeks away! ======================== Meeting Programme Updates ======================== We've published the latest information about plenary, tutorials and Bird of a Feather (BoF) sessions. The draft plenary schedule has been posted at: http://ripe64.ripe.net/programme/meeting-plan/plenary The meeting plan has been updated at: http://ripe64.ripe.net/programme/meeting-plan/ ======================== Social Events ======================== Sign up for the foosball tournament, and check out the rest of the socials programme for RIPE 64 attendees at: http://ripe64.ripe.net/programme/social-events/ ========================== Hotel Room Discount Extended to 26 March ========================== If you haven't booked already, and would like to take advantage of the early bird room discount offered by the meeting venue hotel, please book your room before Monday, 26 March: http://ripe64.ripe.net/venue/meeting-venue/ You can also take a look at the alternative hotels listed. We look forward to seeing you in Ljubljana! Kind regards, The RIPE Meeting Team RIPE NCC From noreply at ripe.net Fri Mar 23 16:59:13 2012 From: noreply at ripe.net (Axel Pawlik) Date: Fri, 23 Mar 2012 16:59:13 +0100 Subject: NRO Welcomes Public Comments on the ASO Review Report Message-ID: <5F207BE7-94AC-45EE-AF63-06AEC4C12889@ripe.net> Dear colleagues, Under the Internet Corporation for Assigned Names and Numbers (ICANN) Bylaws, the Number Resource Organization (NRO) undertakes independent periodic reviews of the Address Supporting Organization (ASO). ITEMS International, a consultancy engaged by the NRO to conduct this current review, has delivered its report. The report is open for public comment and is available here: http://www.nro.net/wp-content/uploads/ASO-Review-Report-2012.pdf The NRO encourages the ICANN, RIR, and wider Internet communities to provide comments on this report, to inform the NRO and ICANN on the further steps required by the review process. Public comments can be submitted to . This comment period closes on Friday, 6 April 12012 at 23:59 (UTC). To review the current comments, please see: http://forum.icann.org/lists/aso-review The NRO will submit its conclusions and recommendations by Monday, 30 April 2012 at 23:59 (UTC). For more information, please see: http://www.icann.org/en/news/public-comment/aso-review-16mar12-en.htm Best regards Axel Pawlik Managing Director, RIPE NCC From cris.pascual.gonzalez at gmail.com Sat Mar 24 19:44:26 2012 From: cris.pascual.gonzalez at gmail.com (Cristina Pascual) Date: Sat, 24 Mar 2012 19:44:26 +0100 Subject: New deadline, April 16 || CfP: MESH 2012 || August 19-24, 2012 - Rome, Italy Message-ID: <201203241844.q2OIiPTw001254@smtp.upv.es> INVITATION: ================= Please consider to contribute to and/or forward to the appropriate groups the following opportunity to submit and publish original scientific results to MESH 2012. The submission deadline is set to April 16, 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 ================= ============== MESH 2012 | Call for Papers =============== CALL FOR PAPERS, TUTORIALS, PANELS MESH 2012: The Fifth International Conference on Advances in Mesh Networks August 19-24, 2012 - Rome, Italy General page: http://www.iaria.org/conferences2012/MESH12.html Call for Papers: http://www.iaria.org/conferences2012/CfPMESH12.html - regular papers - short papers (work in progress) - posters Submission page: http://www.iaria.org/conferences2012/SubmitMESH12.html Submission deadline: April 16, 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 MESH 2012 Topics (topics and submission details: see CfP on the site) Architectures and algorithms Frameworks; Wireless interference models; Topology models; Large-scale networks; Real-time and non-real-time communications; Channel assignment schemes; Resource allocation; Centralized and distributed scheduling; Performance; Static/mobile scenarios; Access control; Service differentiation; Security, Privacy, and Trust Protocols Protocol interference models; Access and routing protocols; Single-channel multihop / multi-channel routing; Joint routing and scheduling; Routing metrics; Multichannel routing; Quality of Services routing; Multimedia-centric routing; Fast-link quality metrics; Bandwidth estimation; Cross-layer multicast routing; QoS-based access protocols for mesh networks; Multi-channel access protocols Applications Multimedia services; Home IPTV; WiMax; Broadband home networking communications; Emergency/disaster; Telemedicine and e-health; Smart buildings; Broadband Internet access ==================== ------------------------------ IARIA Publicity Board From meeting at ripe.net Thu Mar 29 14:29:46 2012 From: meeting at ripe.net (RIPE NCC Meeting Coordinator) Date: Thu, 29 Mar 2012 14:29:46 +0200 Subject: RIPE 64: Agenda Updates Message-ID: <4F7455BA.6000301@ripe.net> Dear colleagues, It's less than three weeks to go until RIPE 64, on 16-20 April 2012 at the Grand Union hotel in Ljubljana. The RIPE 64 Plenary agenda and several RIPE Working Group agendas have been updated and posted at: https://ripe64.ripe.net/programme/meeting-plan/ If you haven't already, you can register online at: https://ripe64.ripe.net/register See you soon in Ljubljana! Kind regards, the RIPE Meeting team RIPE NCC