- ripe-list - mailman.ripe.net

[members-discuss] [ncc-announce] Mark Your Calendar: RIPE NCC Regional Meeting/Eurasia Network Operators' Group (ENOG)
by Paul Rendek 20 Jan '11

20 Jan '11

Dear Colleagues, The RIPE NCC Regional Meeting/Eurasia Network Operators' Group (ENOG) will take place in Moscow from 6-8 June 2011. This will be the first ever combined RIPE NCC Regional Meeting/ENOG Meeting. We are also happy to announce that a second meeting is to be scheduled for later this year. At the Moscow RIPE NCC Regional Meeting in September 2010, attendees decided to further their cooperation by proposing the creation of a regional forum in which the region’s Internet experts could collaborate on issues unique to the Russian Federation, the Commonwealth of Independent States (CIS), Eastern Europe and other interested parties. This forum is now established as ENOG, and the RIPE NCC is dedicated to actively support and facilitate this newly formed operators' group. The RIPE NCC Regional Meeting/ENOG is a forum for open dialogue, and it's available for all interested parties to attend. This is where network operators can meet their peers and learn from international and local Internet experts. Operational content will be a central part of the agenda. Topics will cover challenges, tools, experiences and best practices in areas such as DNS, peering, routing, IPv6 and more. For the first time at a RIPE NCC Regional Meeting, a day will be dedicated to RIPE activities, where RIPE Policies will be presented and openly discussed. We're already looking forward to an exciting and productive meeting. We're very much looking forward to welcoming you to participate at the meeting in Moscow in June, together making this another successful event. Regards, Paul Rendek Head of External Relations and Communications RIPE NCC on behalf of the RIPE NCC Regional Meeting/ENOG Organising Committee ---- If you don't want to receive mails from the RIPE NCC Members Discuss list, please log in to your LIR Portal account at: http://lirportal.ripe.net/ First click on General and then click on Edit. At the bottom of the Page you can add or remove addresses.

1 0

RIPE Document ripe-508 published
by Axel Pawlik 13 Jan '11

13 Jan '11

Dear colleagues, A new RIPE Document defining the history and purpose of the RIPE Registry has been published. RIPE Document ripe-508, "The RIPE Registry", can be found online at: http://www.ripe.net/ripe/docs/ripe-508.html This document establishes a clear definition of the RIPE Registry that can be referenced by the RIPE community. We encourage you to read this document. Kind regards, Axel Pawlik Managing Director RIPE NCC

1 0

RIPE NCC Resource Certification Service Launch
by Alex Band 03 Jan '11

03 Jan '11

Dear colleagues, The RIPE NCC is proud to announce the production launch of the RIPE NCC resource certification service. With the support of the RIPE community, we have worked very hard to create a service that will help to make our registry more robust and provide a vital element in making Internet routing more secure. Now, more than ever, it is important to be sure who is the legitimate holder of a block of IP addresses. As a first step, the RIPE NCC (in coordination with the other four RIRs) has created a hosted platform. This means that all LIRs will be able to generate a certificate of holdership that will be held in a repository maintained by the RIPE NCC. The feature set is, as it stands, very limited: the certificate will only cover Provider Aggregatable address space, and it is not yet possible to run your own Certificate Authority or generate "child" certificates to create a chain of trust. All of these capabilities will be rolled out over the course of 2011, based on the wishes and input of the RIPE community. This brings me to an important point. While the technology is now in place, the policy describing the details of the certification system has not yet passed the RIPE Policy Development Process. We have decided, however, to launch the system with the most limited feature set possible, so that the membership can try it out. Our hope is that this will make resource certification more tangible, and assist the community in making an informed decision about what the system should offer, now and in the future. I invite and encourage you to discuss this on the RIPE NCC Services Working Group mailing list: http://www.ripe.net/ripe/wg/ncc-services/index.html Ongoing development of the RIPE NCC certification service will, of course, be planned in accordance with the certification policy that is agreed on by the RIPE community. For more information, please visit: http://ripe.net/certification If you have any questions or comments, please email <certification(a)ripe.net >. Best regards, Alex Band Product Manager, RIPE NCC

1 0

RIPE NCC closed on Friday 24 December 2010
by Saskia van Gorp 23 Dec '10

23 Dec '10

Dear Colleagues, Our offices will be closed on Friday 24 December 2010 due to Christmas Eve. Normal office hours will resume on Monday, 27 December 2010. The RIPE NCC wishes you Happy Holidays and all the best for 2011. Regards, Saskia van Gorp Facilities, Administration and Reception Manager RIPE NCC

1 0

RIPE NCC Resource Certification System: Initial Deployment 1 January 2011
by Alex Band 01 Dec '10

01 Dec '10

Dear colleagues, With just seven IPv4 address blocks available in the IANA pool, we are hurtling towards the end of an era. With this prospect, the registry function of the five Regional Internet Registries (RIRs) is going to be crucial to the Internet community. More than ever, it is important to know who is the legitimate holder of a block of IP addresses. With this as a primary driver, the RIPE NCC (in coordination with the other four RIRs) is planning to deploy a system that attaches digital certificates to Internet number resources (IP address blocks and Autonomous System (AS) Numbers). A more complete description of the benefits of resource certification can be found at: http://www.ripe.net/certification/ The RIPE NCC has had a beta platform for certification up and running for several months now. More than 100 RIPE NCC members have enabled certification under this pilot program, providing the RIPE NCC with valuable feedback. On 1 January 2011, the RIPE NCC will launch a hosted production system, which will allow all LIRs to generate a certificate of holdership, which will be held in a repository maintained by the RIPE NCC. Network operators will also be able to start making routing decisions based on the system as of this date. Further iterations of this system will be deployed over the coming 12 months, including the option for LIRs to host their own Certificate Authority and generate certificates for their own customers. Digital certificates have helped make business on the Internet more secure. Now we are using resource certificates to make the Internet itself more secure. For more information, please visit: http://ripe.net/certification If you have any questions or comments, please email <ncc(a)ripe.net>. Best regards, Alex Band Product Manager, RIPE NCC

3 2

Four /8s Allocated to RIRs; 2.73% Remains
by Axel Pawlik 01 Dec '10

01 Dec '10

Dear colleagues, Today, 30 November 2010, the Internet Assigned Numbers Authority (IANA) distributed four of the remaining eleven /8s to the Regional Internet Registries (RIRs): 5/8 and 37/8 to the RIPE NCC and 23/8 and 100/8 to ARIN. The IANA free pool of IPv4 addresses now stands at seven /8s, or 2.73% of the total IPv4 address pool. When only five /8s remain, the IANA will simultaneously distribute these equally among five RIRs, in accordance with global policy: http://www.icann.org/en/general/allocation-remaining-ipv4-space.htm There are now only two IPv4 blocks available under the normal distribution method. If you have not already adopted the next generation of Internet Protocol, IPv6, I strongly urge you to act now. For more information on IPv6 adoption, visit: http://www.ipv6actnow.org/ If you have any questions or comments, please email <ncc(a)ripe.net>. Kind regards, Axel Pawlik Managing Director, RIPE NCC

1 0

RIPE 61: Another record meeting
by RIPE NCC Meeting Coordinator 25 Nov '10

25 Nov '10

Dear Colleagues, RIPE 61 took place last week from 15-19 November 2010. More than 430 people attended, making it the the most well-attended RIPE Meeting to date. RIPE 61 Meeting Report ---------------------- The full RIPE 61 Meeting Report is now available at: www.ripe.net/news/2010-ripe61-report.html Sessions Archive ----------------- Presentations from the week can be found at: http://ripe61.ripe.net/programme/presentations/ Webcasts, chat logs and stenography transcripts can be found at: http://ripe61.ripe.net/archives/ Thanks ------ We would like to thank everyone who participated at RIPE 61 - onsite and remotely - who helped to make this such a successful meeting. We would also like to thank the RIPE 61 sponsors: AMS-IX, Colt, Consortium GARR, TINET, Telecom Italia Sparkle and Unidata And special thanks goes to the local hosts of this meeting, Nautilus Mediterranean eXchange Point (NaMeX) and CASPUR. Next Meeting ------------ RIPE 62 will take place in Amsterdam, the Netherlands from 2-6 May 2011. We hope to see you there. Your Opinion ------------ As always we appreciate your feedback. You can either send an email to <meeting(a)ripe.net> or fill in the anonymous feedback form at: http://ripe61.ripe.net/help/feedback/ Best regards, The RIPE Meeting Team

1 0

installing ripe db software failed
by Eduardo 25 Nov '10

25 Nov '10

Hi Folks, Sorry if this is not the right list .... I am trying to install the latest ripe db on my Freebsd 7.3 server and got these errors below ... I was wondering if it should work or am I supposed to install on linux ... in which case I´d ask which flavor/version should I use ? (I did install all the requirements first). thanks in advance for any help, -Ed. # perl Install.PL --verbose --debug --for-development --all --start-daemon --prefix=/usr/local/whois --sqlpass=xxxx --dbname=whois Use of uninitialized value in string eq at Install.PL line 80. Running 'sh ./autogen.sh'=============================== Automake v1.5 is used for building. Your version is 1.9.6. If configuration fails, keep this in mind :) =============================== Running libtoolize libtoolize: putting auxiliary files in `.'. libtoolize: copying file `./ltmain.sh' libtoolize: You should add the contents of the following files to `aclocal.m4': libtoolize: `/usr/local/share/aclocal/libtool.m4' libtoolize: `/usr/local/share/aclocal/ltoptions.m4' libtoolize: `/usr/local/share/aclocal/ltversion.m4' libtoolize: `/usr/local/share/aclocal/ltsugar.m4' libtoolize: `/usr/local/share/aclocal/lt~obsolete.m4' libtoolize: Consider adding `AC_CONFIG_MACRO_DIR([m4])' to configure.ac and libtoolize: rerunning libtoolize, to keep the correct libtool macros in-tree. libtoolize: Consider adding `-I m4' to ACLOCAL_AMFLAGS in Makefile.am. libtoolize: `AC_PROG_RANLIB' is rendered obsolete by `LT_INIT' Running aclocal m4/ripe_opl_only.m4:4: warning: underquoted definition of RIPE_OPL_ONLY run info '(automake)Extending aclocal' or see http://sources.redhat.com/automake/automake.html#Extending-aclocal m4/ripe_check_rpsl_variant.m4:6: warning: underquoted definition of RIPE_SET_RPSL_VARIANT m4/ripe_check_rdns.m4:4: warning: underquoted definition of RIPE_CHECK_RDNS m4/ripe_check_libxslt.m4:6: warning: underquoted definition of RIPE_CHECK_LIBXSLT m4/ripe_check_libxml.m4:6: warning: underquoted definition of RIPE_CHECK_LIBXML m4/ripe_check_cclient.m4:5: warning: underquoted definition of RIPE_CHECK_CCLIENT m4/lf_set_warnings.m4:7: warning: underquoted definition of LF_SET_WARNINGS m4/lf_set_warnings.m4:39: warning: underquoted definition of LF_CHECK_CXX_FLAG m4/lf_check_cc_flag.m4:9: warning: underquoted definition of LF_CHECK_CC_FLAG m4/ac_library_net.m4:35: warning: underquoted definition of AC_LIBRARY_NET configure.ac:250: warning: AC_LANG_CONFTEST: no AC_LANG_SOURCE call detected in body ../../lib/autoconf/lang.m4:194: AC_LANG_CONFTEST is expanded from... ../../lib/autoconf/general.m4:2662: _AC_LINK_IFELSE is expanded from... ../../lib/autoconf/general.m4:2679: AC_LINK_IFELSE is expanded from... /usr/local/share/aclocal/libtool.m4:1084: _LT_SYS_MODULE_PATH_AIX is expanded from... /usr/local/share/aclocal/libtool.m4:4207: _LT_LINKER_SHLIBS is expanded from... /usr/local/share/aclocal/libtool.m4:5339: _LT_LANG_C_CONFIG is expanded from... /usr/local/share/aclocal/libtool.m4:143: _LT_SETUP is expanded from... /usr/local/share/aclocal/libtool.m4:69: LT_INIT is expanded from... /usr/local/share/aclocal/libtool.m4:107: AC_PROG_LIBTOOL is expanded from... configure.ac:250: the top level configure.ac:250: warning: AC_LANG_CONFTEST: no AC_LANG_SOURCE call detected in body ../../lib/autoconf/lang.m4:194: AC_LANG_CONFTEST is expanded from... ../../lib/autoconf/general.m4:2662: _AC_LINK_IFELSE is expanded from... ../../lib/autoconf/general.m4:2679: AC_LINK_IFELSE is expanded from... /usr/local/share/aclocal/libtool.m4:4207: _LT_LINKER_SHLIBS is expanded from... /usr/local/share/aclocal/libtool.m4:5339: _LT_LANG_C_CONFIG is expanded from... /usr/local/share/aclocal/libtool.m4:143: _LT_SETUP is expanded from... /usr/local/share/aclocal/libtool.m4:69: LT_INIT is expanded from... /usr/local/share/aclocal/libtool.m4:107: AC_PROG_LIBTOOL is expanded from... configure.ac:250: the top level configure.ac:266: warning: AC_LANG_CONFTEST: no AC_LANG_SOURCE call detected in body ../../lib/autoconf/lang.m4:194: AC_LANG_CONFTEST is expanded from... ../../lib/autoconf/general.m4:2662: _AC_LINK_IFELSE is expanded from... ../../lib/autoconf/general.m4:2679: AC_LINK_IFELSE is expanded from... /usr/local/share/aclocal/libtool.m4:1084: _LT_SYS_MODULE_PATH_AIX is expanded from... /usr/local/share/aclocal/libtool.m4:4207: _LT_LINKER_SHLIBS is expanded from... /usr/local/share/aclocal/libtool.m4:6934: _LT_LANG_GCJ_CONFIG is expanded from... /usr/local/share/aclocal/libtool.m4:816: _LT_LANG is expanded from... /usr/local/share/aclocal/libtool.m4:799: LT_LANG is expanded from... configure.ac:266: the top level configure.ac:266: warning: AC_LANG_CONFTEST: no AC_LANG_SOURCE call detected in body ../../lib/autoconf/lang.m4:194: AC_LANG_CONFTEST is expanded from... ../../lib/autoconf/general.m4:2662: _AC_LINK_IFELSE is expanded from... ../../lib/autoconf/general.m4:2679: AC_LINK_IFELSE is expanded from... /usr/local/share/aclocal/libtool.m4:4207: _LT_LINKER_SHLIBS is expanded from... /usr/local/share/aclocal/libtool.m4:6934: _LT_LANG_GCJ_CONFIG is expanded from... /usr/local/share/aclocal/libtool.m4:816: _LT_LANG is expanded from... /usr/local/share/aclocal/libtool.m4:799: LT_LANG is expanded from... configure.ac:266: the top level Running autoheader configure.ac:250: warning: AC_LANG_CONFTEST: no AC_LANG_SOURCE call detected in body ../../lib/autoconf/lang.m4:194: AC_LANG_CONFTEST is expanded from... ../../lib/autoconf/general.m4:2662: _AC_LINK_IFELSE is expanded from... ../../lib/autoconf/general.m4:2679: AC_LINK_IFELSE is expanded from... aclocal.m4:1091: _LT_SYS_MODULE_PATH_AIX is expanded from... aclocal.m4:4214: _LT_LINKER_SHLIBS is expanded from... aclocal.m4:5346: _LT_LANG_C_CONFIG is expanded from... aclocal.m4:156: _LT_SETUP is expanded from... aclocal.m4:82: LT_INIT is expanded from... aclocal.m4:120: AC_PROG_LIBTOOL is expanded from... configure.ac:250: the top level configure.ac:250: warning: AC_LANG_CONFTEST: no AC_LANG_SOURCE call detected in body ../../lib/autoconf/lang.m4:194: AC_LANG_CONFTEST is expanded from... ../../lib/autoconf/general.m4:2662: _AC_LINK_IFELSE is expanded from... ../../lib/autoconf/general.m4:2679: AC_LINK_IFELSE is expanded from... aclocal.m4:4214: _LT_LINKER_SHLIBS is expanded from... aclocal.m4:5346: _LT_LANG_C_CONFIG is expanded from... aclocal.m4:156: _LT_SETUP is expanded from... aclocal.m4:82: LT_INIT is expanded from... aclocal.m4:120: AC_PROG_LIBTOOL is expanded from... configure.ac:250: the top level configure.ac:266: warning: AC_LANG_CONFTEST: no AC_LANG_SOURCE call detected in body ../../lib/autoconf/lang.m4:194: AC_LANG_CONFTEST is expanded from... ../../lib/autoconf/general.m4:2662: _AC_LINK_IFELSE is expanded from... ../../lib/autoconf/general.m4:2679: AC_LINK_IFELSE is expanded from... aclocal.m4:1091: _LT_SYS_MODULE_PATH_AIX is expanded from... aclocal.m4:4214: _LT_LINKER_SHLIBS is expanded from... aclocal.m4:6937: _LT_LANG_GCJ_CONFIG is expanded from... aclocal.m4:823: _LT_LANG is expanded from... aclocal.m4:806: LT_LANG is expanded from... configure.ac:266: the top level configure.ac:266: warning: AC_LANG_CONFTEST: no AC_LANG_SOURCE call detected in body ../../lib/autoconf/lang.m4:194: AC_LANG_CONFTEST is expanded from... ../../lib/autoconf/general.m4:2662: _AC_LINK_IFELSE is expanded from... ../../lib/autoconf/general.m4:2679: AC_LINK_IFELSE is expanded from... aclocal.m4:4214: _LT_LINKER_SHLIBS is expanded from... aclocal.m4:6937: _LT_LANG_GCJ_CONFIG is expanded from... aclocal.m4:823: _LT_LANG is expanded from... aclocal.m4:806: LT_LANG is expanded from... configure.ac:266: the top level Running automake configure.ac:250: warning: AC_LANG_CONFTEST: no AC_LANG_SOURCE call detected in body ../../lib/autoconf/lang.m4:194: AC_LANG_CONFTEST is expanded from... ../../lib/autoconf/general.m4:2662: _AC_LINK_IFELSE is expanded from... ../../lib/autoconf/general.m4:2679: AC_LINK_IFELSE is expanded from... aclocal.m4:1091: _LT_SYS_MODULE_PATH_AIX is expanded from... aclocal.m4:4214: _LT_LINKER_SHLIBS is expanded from... aclocal.m4:5346: _LT_LANG_C_CONFIG is expanded from... aclocal.m4:156: _LT_SETUP is expanded from... aclocal.m4:82: LT_INIT is expanded from... aclocal.m4:120: AC_PROG_LIBTOOL is expanded from... configure.ac:250: the top level configure.ac:250: warning: AC_LANG_CONFTEST: no AC_LANG_SOURCE call detected in body ../../lib/autoconf/lang.m4:194: AC_LANG_CONFTEST is expanded from... ../../lib/autoconf/general.m4:2662: _AC_LINK_IFELSE is expanded from... ../../lib/autoconf/general.m4:2679: AC_LINK_IFELSE is expanded from... aclocal.m4:4214: _LT_LINKER_SHLIBS is expanded from... aclocal.m4:5346: _LT_LANG_C_CONFIG is expanded from... aclocal.m4:156: _LT_SETUP is expanded from... aclocal.m4:82: LT_INIT is expanded from... aclocal.m4:120: AC_PROG_LIBTOOL is expanded from... configure.ac:250: the top level configure.ac:266: warning: AC_LANG_CONFTEST: no AC_LANG_SOURCE call detected in body ../../lib/autoconf/lang.m4:194: AC_LANG_CONFTEST is expanded from... ../../lib/autoconf/general.m4:2662: _AC_LINK_IFELSE is expanded from... ../../lib/autoconf/general.m4:2679: AC_LINK_IFELSE is expanded from... aclocal.m4:1091: _LT_SYS_MODULE_PATH_AIX is expanded from... aclocal.m4:4214: _LT_LINKER_SHLIBS is expanded from... aclocal.m4:6937: _LT_LANG_GCJ_CONFIG is expanded from... aclocal.m4:823: _LT_LANG is expanded from... aclocal.m4:806: LT_LANG is expanded from... configure.ac:266: the top level configure.ac:266: warning: AC_LANG_CONFTEST: no AC_LANG_SOURCE call detected in body ../../lib/autoconf/lang.m4:194: AC_LANG_CONFTEST is expanded from... ../../lib/autoconf/general.m4:2662: _AC_LINK_IFELSE is expanded from... ../../lib/autoconf/general.m4:2679: AC_LINK_IFELSE is expanded from... aclocal.m4:4214: _LT_LINKER_SHLIBS is expanded from... aclocal.m4:6937: _LT_LANG_GCJ_CONFIG is expanded from... aclocal.m4:823: _LT_LANG is expanded from... aclocal.m4:806: LT_LANG is expanded from... configure.ac:266: the top level configure.ac: installing `./missing' src/Makefile.am: installing `./depcomp' configure.ac:34: installing `./config.guess' configure.ac:34: installing `./config.sub' Running autoconf configure.ac:250: warning: AC_LANG_CONFTEST: no AC_LANG_SOURCE call detected in body ../../lib/autoconf/lang.m4:194: AC_LANG_CONFTEST is expanded from... ../../lib/autoconf/general.m4:2662: _AC_LINK_IFELSE is expanded from... ../../lib/autoconf/general.m4:2679: AC_LINK_IFELSE is expanded from... aclocal.m4:1091: _LT_SYS_MODULE_PATH_AIX is expanded from... aclocal.m4:4214: _LT_LINKER_SHLIBS is expanded from... aclocal.m4:5346: _LT_LANG_C_CONFIG is expanded from... aclocal.m4:156: _LT_SETUP is expanded from... aclocal.m4:82: LT_INIT is expanded from... aclocal.m4:120: AC_PROG_LIBTOOL is expanded from... configure.ac:250: the top level configure.ac:250: warning: AC_LANG_CONFTEST: no AC_LANG_SOURCE call detected in body ../../lib/autoconf/lang.m4:194: AC_LANG_CONFTEST is expanded from... ../../lib/autoconf/general.m4:2662: _AC_LINK_IFELSE is expanded from... ../../lib/autoconf/general.m4:2679: AC_LINK_IFELSE is expanded from... aclocal.m4:4214: _LT_LINKER_SHLIBS is expanded from... aclocal.m4:5346: _LT_LANG_C_CONFIG is expanded from... aclocal.m4:156: _LT_SETUP is expanded from... aclocal.m4:82: LT_INIT is expanded from... aclocal.m4:120: AC_PROG_LIBTOOL is expanded from... configure.ac:250: the top level configure.ac:266: warning: AC_LANG_CONFTEST: no AC_LANG_SOURCE call detected in body ../../lib/autoconf/lang.m4:194: AC_LANG_CONFTEST is expanded from... ../../lib/autoconf/general.m4:2662: _AC_LINK_IFELSE is expanded from... ../../lib/autoconf/general.m4:2679: AC_LINK_IFELSE is expanded from... aclocal.m4:1091: _LT_SYS_MODULE_PATH_AIX is expanded from... aclocal.m4:4214: _LT_LINKER_SHLIBS is expanded from... aclocal.m4:6937: _LT_LANG_GCJ_CONFIG is expanded from... aclocal.m4:823: _LT_LANG is expanded from... aclocal.m4:806: LT_LANG is expanded from... configure.ac:266: the top level configure.ac:266: warning: AC_LANG_CONFTEST: no AC_LANG_SOURCE call detected in body ../../lib/autoconf/lang.m4:194: AC_LANG_CONFTEST is expanded from... ../../lib/autoconf/general.m4:2662: _AC_LINK_IFELSE is expanded from... ../../lib/autoconf/general.m4:2679: AC_LINK_IFELSE is expanded from... aclocal.m4:4214: _LT_LINKER_SHLIBS is expanded from... aclocal.m4:6937: _LT_LANG_GCJ_CONFIG is expanded from... aclocal.m4:823: _LT_LANG is expanded from... aclocal.m4:806: LT_LANG is expanded from... configure.ac:266: the top level configure.ac:142: error: possibly undefined macro: AC_CHECK_CTIME_R If this token and others are legitimate, please use m4_pattern_allow. See the Autoconf documentation. autoconf failed 256 at Install.PL line 423.

2 1

New document available: RIPE-501 Requirements For IPv6 in ICT Equipment
by Marco Hogewoning 24 Nov '10

24 Nov '10

Dear community, A new ripe document, RIPE-501, has been published "Requirements For IPv6 in ICT Equipment". This document aims to be a guide of what to ask for exactly when IPv6 is a requirement in a tender or some contract and lists the various applicable RFCs for specific kinds of ICT equipment. The document is available on http://www.ripe.net/ripe/docs/ripe-501.html Please note that when using this document as a reference, as with any RIPE document, it might get superseded by new versions in the future. Many thanks to the authors and everybody who helped with proof reading, translation and feedback. Marco, David & Shane, co-chairs of the IPv6 working group

1 0

RIPE BoF - Thursday 18th November 2010 - RIPE 61 Activity
by Andy Davidson 18 Nov '10

18 Nov '10

Dear colleagues, We are really happy to announce that on Thursday 18th November (During RIPE 61) between 5.45pm and 6.45pm, we shall host the first ever RIPE BoF session. This is an informal gathering, where you are invited to talk about any operational issues that you want to raise or that simply don't fit in anywhere else.. Its a time for people to get together share ideas in an open friendly manner. You can suggest topics about any area of operational practice. This is the perfect opportunity to fix your bugs, discover the best practice, and learn about new tools. Please tell us the topics you would like to discuss, the most popular will be selected. If you have any suggestions you can offer them here - http://ripe61.ripe.net/programme/bofs/ripe-bof/ The BoF is part of RIPE 61 and open to everyone registered for the meeting. A

2 2