1 / 7

Ripe Meeting Task-Force Update

Ripe Meeting Task-Force Update. _____________________________________ Andy Davidson < adavidson@he.net > Hurricane Electric RIPE62, 2 nd May 2011. Additional Special Thanks to… .

Télécharger la présentation

Ripe Meeting Task-Force Update

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.


Presentation Transcript

  1. Ripe Meeting Task-Force Update _____________________________________ Andy Davidson <adavidson@he.net> Hurricane Electric RIPE62, 2nd May 2011

  2. Additional Special Thanks to… • BijalSanghani • Brian Nisbet • Christian Kaufmann • Jim Reid • Joao Damas • Rob Evans • Sander Steffann

  3. Thinking back to RIPE61…. • New content format • BOF • Tutorial • Survey • What must not change? • What can be improved?

  4. Survey • ~300 Responses, and clear trends emerging • Largest representative groups: • Network Practitioner • Engineering Manager / Leader • Largely working in ISP & Carrier organisations

  5. “What must not change” • Focus must remain technical • Meeting frequency/duration is about right • Social events very important • RIPE meeting fee is fair • Meeting logistics are excellent

  6. “What can be improved” • More Tutorial Content (87% of respondents come to the RIPE meeting to learn) • A fifth of respondents want to get more involved with the meeting content • Ad-hoc BoFspopular with all respondents • Outreach to ccNOGsfor knowledge sharing • “Bleeding edge” technology and research • More technical/operational content

  7. Program Committee • To ensure Plenary, Tutorial, and BoFcontent is in tune with attendee needs • Four Community representatives elected @ meetings • Liaison representatives from wg-chairs, MENOG PC, ENOG PC • One recommended by the local host • Co-opted members with specialist subject knowledge • Open and Transparent • NOT involved with working group content • This wont be a badge, it will be a lot of work!

More Related