- NANOG - lists.nanog.org

Microsoft - list of Azure DNS servers
by Ryan Finnesey 24 Aug '18

24 Aug '18

I am looking for someone from Microsoft to contact me off list. I am looking for a complete list of Azure DNS servers. Cheers Ryan

1 0

IPv6 Management
by Justin Wilson 23 Aug '18

23 Aug '18

We were having an interesting debate on IPV6 management on layer2 devices. Does anyone have a best practice document they have seen for utilizing v6 Management addresses? I know Cisco has some extensive documentation on using v6 on their wireless products. I know everyone has thoughts so am interested in any best practices which have been presented to the community. I haven’t worried about management access on layer2 devices, as long as the layer2 devices can pass any cast, multicast, and other things v6 needs. However, I could see why you would want v6 management addresses. And go…. Justin Wilson j2sw(a)mtin.net www.mtin.net www.midwest-ix.com

4 3

Re: Hurricane Lane: Catagory 5 storm forecast to sideswipe Hawaii
by Scott Weeks 22 Aug '18

22 Aug '18

--- sean(a)donelan.com wrote: From: Sean Donelan <sean(a)donelan.com> Hurricane warnings have been issued for Hurricane Lane, which strengthened to a catagory 5 storm on Tuesday. The forecast cone of uncertainity shows the path sideswiping Hawaii on Thursday. ------------------------------------------- Yep, this one's closer than the other 2-3 weeks ago. I thought about sending another 'dust off your DR plan' for those networks doing business in the AP region that have stuff here, but if they didn't on the last one they wouldn't on this one, either. :-) It's an M (>110 MPH) until the Big Island on Thur and then goes down to a regular hurricane Friday when it hits Maui and Oahu Friday. http://www.prh.noaa.gov/cphc/tcpages/?product=5day_cone_with_line_and_wind&… http://weather.hawaii.edu/satellite/jsanim.cgi?res=4km&chnl=ir&domain=nep&p… scott

1 0

Hurricane Lane: Catagory 5 storm forecast to sideswipe Hawaii
by Sean Donelan 22 Aug '18

22 Aug '18

Hurricane warnings have been issued for Hurricane Lane, which strengthened to a catagory 5 storm on Tuesday. The forecast cone of uncertainity shows the path sideswiping Hawaii on Thursday.

1 0

Re: NANOG Digest, Vol 127, Issue 16
by Saymon Araújo 22 Aug '18

22 Aug '18

- PRTG, it's realy easy to configure. Most of the senssors are SNMP of: traffic/ping/cpu/memory and some senssors for servers like DNS and Radius, etc. - Zabbix, there's 2 things that made us use Zabbix, the first one it's Zabbix Proxy, since the network it's geographical distribuited we need a tool that provides us monitoring from another places with a low price. And LLD that i use for monitoring BGP/OSPF sessions and prefix. - Elastiflow - For Syslog we use Graylog, that i recomend, it's a excelente tool for monitoring syslog messages and there's a lot of features such as extractors, streams and alerts. I think that PRTG it's kind expensive solution ( if you buy the license ), but provides a easy way to monitor a lot of things. Just one thing, if your license expires your are no able to update your software and if you want to buy the license for upgrade, the days without the license counts as negative days, i never seen that before, like, if you don't update the license for 1 year and bought the 3 years lisence, you will got 2 years of support and upgrade. Atenciosamente, Em sex, 17 de ago de 2018 às 09:00, <nanog-request(a)nanog.org> escreveu: > Send NANOG mailing list submissions to > nanog(a)nanog.org > > To subscribe or unsubscribe via the World Wide Web, visit > https://mailman.nanog.org/mailman/listinfo/nanog > or, via email, send a message with subject or body 'help' to > nanog-request(a)nanog.org > > You can reach the person managing the list at > nanog-owner(a)nanog.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of NANOG digest..." > > > Today's Topics: > > 1. Re: What NMS do you use and why? (Nick Peelman) > 2. Re: What NMS do you use and why? (Joe Loiacono) > 3. RE: What NMS do you use and why? (Stan Ouchakov) > 4. Re: What NMS do you use and why? (Nick Peelman) > 5. Re: What NMS do you use and why? (Kushal) > 6. RE: What NMS do you use and why? (Michael Braun (michbrau)) > 7. Re: What NMS do you use and why? (Nick W) > 8. Akamia Contact (Romeo Czumbil) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Wed, 15 Aug 2018 23:14:32 +0000 > From: Nick Peelman <npeelman(a)ETC1.net> > To: Colton Conor <colton.conor(a)gmail.com> > Cc: NANOG <nanog(a)nanog.org> > Subject: Re: What NMS do you use and why? > Message-ID: <D0CDB355-16C7-49E1-9FD6-EDFFB618CC70(a)ETC1.net> > Content-Type: text/plain; charset="Windows-1252" > > I think anybody looking for a be-all-end-all solution will find nothing > but heartburn. > > different suites have different strong suits, and deciding you are going > to pursue one and ignore all others may mean living without a feature or > set of features you may find really useful or eventually necessary. but > maintaining multiple complete NMSes isn’t really tenable either. > > all of that said, we use a combination of a couple. Nagios/Icinga because > it’s been around forever (both in the world and in our network), and the > power of script based checks, being able to write your own handlers and > pretty much just leverage it as a framework you can shove questions into > and get regular answers from is invaluable. > > LibreNMS gives us the best pretty pictures, letting us monitor much much > more than just interface traffic, out of the box. much more than cacti is > capable of without a ton of work (i.e. down to the tx/rx power and > temperature readings of individual SFPs). it scales relatively well; at > least in theory. i will be able to tell you for sure later this year as we > are near the limits of what we can monitor with a single polling device. > alerting out of Libre into Slack has proven quite fantastic. we can spawn > threads attached to anything from a BGP peer dropping or a CPU alert as we > move to triage and solve, even if we are in the field or meetings or > whatever. > > we also still have cacti around for random one-offs. as great as Libre is, > its poller can be a bit intense for some devices; so in those cases it’s > safer for us to just have cacti graph the one or two OIDs we need > specifically, without trolling all the other available sensors. > > we ran OpenNMS for a bit, but it proved way to dumb to maintain a large > (and growing) complex network, without dedicating at least one or two > people to the care and feeding of it. > > -nick > > — > Nick Peelman > Network Engineer | Enhanced Telecommunications Corp. > 812-222-0169<tel:812-222-0169> | npeelman(a)etc1.net<mailto: > npeelman(a)etc1.net> | www.etczone.com<http://www.etczone.com/> > > Sent from my iPhone > > On Aug 15, 2018, at 09:49, Colton Conor <colton.conor(a)gmail.com<mailto: > colton.conor(a)gmail.com>> wrote: > > We are looking for a new network monitoring system. Since there are so > many operators on this list, I would like to know which NMS do you use and > why? Is there one that you really like, and others that you hate? > > For free options (opensouce), LibreNMS and NetXMS come highly recommended > by many wireless ISPs on low budgets. However, I am not sure the commercial > options available nor their price points. > > > > > ------------------------------ > > Message: 2 > Date: Wed, 15 Aug 2018 20:31:13 -0400 (EDT) > From: Joe Loiacono <jloiacon(a)gmail.com> > To: William Herrin <bill(a)herrin.us> > Cc: NANOG <nanog(a)nanog.org>, Colton Conor <colton.conor(a)gmail.com> > Subject: Re: What NMS do you use and why? > Message-ID: > <593335944.184.1534379472982.JavaMail.jloia@DESKTOP-FDMC6S8> > Content-Type: text/plain; charset=utf-8 > > Consider also open-source FlowViewer for netflow capture and analysis. A > lot of very useful netflow based analytical tools in an easy UI. Sits on > top of a robust set of Carnegie-Mellon's high-capacity SiLK netflow tools. > > https://sourceforge.net/projects/flowviewer/ > > Joe > > > > ----- Original Message ----- > From: "William Herrin" <bill(a)herrin.us> > To: "Colton Conor" <colton.conor(a)gmail.com> > Cc: "NANOG" <nanog(a)nanog.org> > Sent: Wednesday, August 15, 2018 3:25:48 PM > Subject: Re: What NMS do you use and why? > > On Wed, Aug 15, 2018 at 9:49 AM, Colton Conor <colton.conor(a)gmail.com> > wrote: > > We are looking for a new network monitoring system. Since there are so > many > > operators on this list, I would like to know which NMS do you use and > why? > > Is there one that you really like, and others that you hate? > > I still use a tool I wrote in perl nearly 20 years ago called > "MrPing." MrPing handles multi-dependency graphs. > > Consider: > > A is reachable via either B or C. > > If A and B are down but C is up, A being down is a separate failure > from B being down. I need to know about both. > > If B and C are both down, A is unreachable. I don't want to receive > alerts about A because they'll distract me from the root cause of the > problem: that both B and C are down. The NMS should record that A is > unreachable but it should also tell me that A being unreachable is a > dependent failure that I can ignore until I fix the failures it > depends on. > > > The NMSes I've paid attention to either don't support dependencies > well at all or support only simple hierarchical dependencies. > Resilient, professional networks simply aren't built that way. > > Regards, > Bill Herrin > > > -- > William Herrin ................ herrin(a)dirtside.com bill(a)herrin.us > Dirtside Systems ......... Web: <http://www.dirtside.com/> > > > ------------------------------ > > Message: 3 > Date: Thu, 16 Aug 2018 15:39:52 +0000 > From: Stan Ouchakov <stano(a)imaginesoftware.com> > To: Joe Loiacono <jloiacon(a)gmail.com>, William Herrin <bill(a)herrin.us> > Cc: NANOG <nanog(a)nanog.org> > Subject: RE: What NMS do you use and why? > Message-ID: <e12e489f5c6c4837bd2cee6efe9cb3e0(a)imaginesoftware.com> > Content-Type: text/plain; charset="utf-8" > > Regarding netflow/sflow/ipfix monitoring, we had recently started using > elastiflow by Robert Cowart. Scales very well with pretty visualizations. > Cannot imagine what paid / supported version has to offer :) > > https://github.com/robcowart/elastiflow > > > > -----Original Message----- > From: NANOG <nanog-bounces(a)nanog.org> On Behalf Of Joe Loiacono > Sent: Wednesday, August 15, 2018 8:31 PM > To: William Herrin <bill(a)herrin.us> > Cc: NANOG <nanog(a)nanog.org> > Subject: Re: What NMS do you use and why? > > Consider also open-source FlowViewer for netflow capture and analysis. A > lot of very useful netflow based analytical tools in an easy UI. Sits on > top of a robust set of Carnegie-Mellon's high-capacity SiLK netflow tools. > > https://sourceforge.net/projects/flowviewer/ > > Joe > > > > ----- Original Message ----- > From: "William Herrin" <bill(a)herrin.us> > To: "Colton Conor" <colton.conor(a)gmail.com> > Cc: "NANOG" <nanog(a)nanog.org> > Sent: Wednesday, August 15, 2018 3:25:48 PM > Subject: Re: What NMS do you use and why? > > On Wed, Aug 15, 2018 at 9:49 AM, Colton Conor <colton.conor(a)gmail.com> > wrote: > > We are looking for a new network monitoring system. Since there are so > > many operators on this list, I would like to know which NMS do you use > and why? > > Is there one that you really like, and others that you hate? > > I still use a tool I wrote in perl nearly 20 years ago called "MrPing." > MrPing handles multi-dependency graphs. > > Consider: > > A is reachable via either B or C. > > If A and B are down but C is up, A being down is a separate failure from B > being down. I need to know about both. > > If B and C are both down, A is unreachable. I don't want to receive alerts > about A because they'll distract me from the root cause of the > problem: that both B and C are down. The NMS should record that A is > unreachable but it should also tell me that A being unreachable is a > dependent failure that I can ignore until I fix the failures it depends on. > > > The NMSes I've paid attention to either don't support dependencies well at > all or support only simple hierarchical dependencies. > Resilient, professional networks simply aren't built that way. > > Regards, > Bill Herrin > > > -- > William Herrin ................ herrin(a)dirtside.com bill(a)herrin.us > Dirtside Systems ......... Web: <http://www.dirtside.com/> > > ------------------------------ > > Message: 4 > Date: Thu, 16 Aug 2018 15:42:44 +0000 > From: Nick Peelman <npeelman(a)ETC1.net> > To: Stan Ouchakov <stano(a)imaginesoftware.com> > Cc: Joe Loiacono <jloiacon(a)gmail.com>, William Herrin > <bill(a)herrin.us>, NANOG <nanog(a)nanog.org> > Subject: Re: What NMS do you use and why? > Message-ID: <61BD4D17-F5EB-46AC-BEE2-5D289FECDDBD(a)ETC1.net> > Content-Type: text/plain; charset="Windows-1252" > > seconded. the pains of maintaining ELK are made worthwhile by this alone. > > -nick > > — > Nick Peelman > Network Engineer | Enhanced Telecommunications Corp. > 812-222-0169<tel:812-222-0169> | npeelman(a)etc1.net<mailto: > npeelman(a)etc1.net> | www.etczone.com<http://www.etczone.com/> > > Sent from my iPhone > > On Aug 16, 2018, at 11:41, Stan Ouchakov <stano(a)imaginesoftware.com > <mailto:stano@imaginesoftware.com>> wrote: > > Regarding netflow/sflow/ipfix monitoring, we had recently started using > elastiflow by Robert Cowart. Scales very well with pretty visualizations. > Cannot imagine what paid / supported version has to offer :) > > https://github.com/robcowart/elastiflow > > > > -----Original Message----- > From: NANOG <nanog-bounces(a)nanog.org<mailto:nanog-bounces@nanog.org>> On > Behalf Of Joe Loiacono > Sent: Wednesday, August 15, 2018 8:31 PM > To: William Herrin <bill(a)herrin.us<mailto:bill@herrin.us>> > Cc: NANOG <nanog(a)nanog.org<mailto:nanog@nanog.org>> > Subject: Re: What NMS do you use and why? > > Consider also open-source FlowViewer for netflow capture and analysis. A > lot of very useful netflow based analytical tools in an easy UI. Sits on > top of a robust set of Carnegie-Mellon's high-capacity SiLK netflow tools. > > https://sourceforge.net/projects/flowviewer/ > > Joe > > > > ----- Original Message ----- > From: "William Herrin" <bill(a)herrin.us<mailto:bill@herrin.us>> > To: "Colton Conor" <colton.conor(a)gmail.com<mailto:colton.conor@gmail.com>> > Cc: "NANOG" <nanog(a)nanog.org<mailto:nanog@nanog.org>> > Sent: Wednesday, August 15, 2018 3:25:48 PM > Subject: Re: What NMS do you use and why? > > On Wed, Aug 15, 2018 at 9:49 AM, Colton Conor <colton.conor(a)gmail.com > <mailto:colton.conor@gmail.com>> wrote: > We are looking for a new network monitoring system. Since there are so > many operators on this list, I would like to know which NMS do you use and > why? > Is there one that you really like, and others that you hate? > > I still use a tool I wrote in perl nearly 20 years ago called "MrPing." > MrPing handles multi-dependency graphs. > > Consider: > > A is reachable via either B or C. > > If A and B are down but C is up, A being down is a separate failure from B > being down. I need to know about both. > > If B and C are both down, A is unreachable. I don't want to receive alerts > about A because they'll distract me from the root cause of the > problem: that both B and C are down. The NMS should record that A is > unreachable but it should also tell me that A being unreachable is a > dependent failure that I can ignore until I fix the failures it depends on. > > > The NMSes I've paid attention to either don't support dependencies well at > all or support only simple hierarchical dependencies. > Resilient, professional networks simply aren't built that way. > > Regards, > Bill Herrin > > > -- > William Herrin ................ herrin(a)dirtside.com<mailto: > herrin(a)dirtside.com> bill(a)herrin.us<mailto:bill@herrin.us> Dirtside > Systems ......... Web: <http://www.dirtside.com/> > > > ------------------------------ > > Message: 5 > Date: Thu, 16 Aug 2018 22:19:35 +0530 > From: Kushal <kushal.r(a)h4g.co> > To: Stan Ouchakov <stano(a)imaginesoftware.com>, Nick Peelman > <npeelman(a)etc1.net> > Cc: NANOG <nanog(a)nanog.org> > Subject: Re: What NMS do you use and why? > Message-ID: <etPan.5b75ab1f.dbb654b.3ad(a)h4g.co> > Content-Type: text/plain; charset="utf-8" > > Being a small business we like to use a mostly free and open source tools. > Our networking monitoring stack presently looks like: > > Simple Reachability Monitoring (Ping) - uptimerobot.com > > Just $4.5 per month for 50 monitors with 1 minute intervals (free if you > are find with 5 minutes monitoring intervals). This is connected to our > slack channel and also sends SMS when something goes offline. > > Traffic & Device Monitoring - LibreNMS > > A fork of Observium but adds the much needed alerting feature that > observing only offers with it's paid plans. We use it to monitor switch > port traffic, BGP sessions, device health, etc. > > Packet Inspection or Flow Monitoring we use FastNetMon ( > https://fastnetmon.com/features/) the free edition is good for our needs. > > > On August 16, 2018 at 9:16:42 PM, Nick Peelman (npeelman(a)etc1.net) wrote: > > seconded. the pains of maintaining ELK are made worthwhile by this alone. > > -nick > > — > Nick Peelman > Network Engineer | Enhanced Telecommunications Corp. > 812-222-0169<tel:812-222-0169> | npeelman(a)etc1.net<mailto: > npeelman(a)etc1.net> | www.etczone.com<http://www.etczone.com/> > > Sent from my iPhone > > On Aug 16, 2018, at 11:41, Stan Ouchakov <stano(a)imaginesoftware.com > <mailto:stano@imaginesoftware.com>> wrote: > > Regarding netflow/sflow/ipfix monitoring, we had recently started using > elastiflow by Robert Cowart. Scales very well with pretty visualizations. > Cannot imagine what paid / supported version has to offer :) > > https://github.com/robcowart/elastiflow > > > > -----Original Message----- > From: NANOG <nanog-bounces(a)nanog.org<mailto:nanog-bounces@nanog.org>> On > Behalf Of Joe Loiacono > Sent: Wednesday, August 15, 2018 8:31 PM > To: William Herrin <bill(a)herrin.us<mailto:bill@herrin.us>> > Cc: NANOG <nanog(a)nanog.org<mailto:nanog@nanog.org>> > Subject: Re: What NMS do you use and why? > > Consider also open-source FlowViewer for netflow capture and analysis. A > lot of very useful netflow based analytical tools in an easy UI. Sits on > top of a robust set of Carnegie-Mellon's high-capacity SiLK netflow tools. > > https://sourceforge.net/projects/flowviewer/ > > Joe > > > > ----- Original Message ----- > From: "William Herrin" <bill(a)herrin.us<mailto:bill@herrin.us>> > To: "Colton Conor" <colton.conor(a)gmail.com<mailto:colton.conor@gmail.com>> > > Cc: "NANOG" <nanog(a)nanog.org<mailto:nanog@nanog.org>> > Sent: Wednesday, August 15, 2018 3:25:48 PM > Subject: Re: What NMS do you use and why? > > On Wed, Aug 15, 2018 at 9:49 AM, Colton Conor <colton.conor(a)gmail.com > <mailto:colton.conor@gmail.com>> wrote: > We are looking for a new network monitoring system. Since there are so > many operators on this list, I would like to know which NMS do you use and > why? > Is there one that you really like, and others that you hate? > > I still use a tool I wrote in perl nearly 20 years ago called "MrPing." > MrPing handles multi-dependency graphs. > > Consider: > > A is reachable via either B or C. > > If A and B are down but C is up, A being down is a separate failure from B > being down. I need to know about both. > > If B and C are both down, A is unreachable. I don't want to receive alerts > about A because they'll distract me from the root cause of the > problem: that both B and C are down. The NMS should record that A is > unreachable but it should also tell me that A being unreachable is a > dependent failure that I can ignore until I fix the failures it depends > on. > > > The NMSes I've paid attention to either don't support dependencies well at > all or support only simple hierarchical dependencies. > Resilient, professional networks simply aren't built that way. > > Regards, > Bill Herrin > > > -- > William Herrin ................ herrin(a)dirtside.com<mailto: > herrin(a)dirtside.com> bill(a)herrin.us<mailto:bill@herrin.us> Dirtside > Systems ......... Web: <http://www.dirtside.com/> >

1 0

optical circulator as a bidirectional one fiber solution
by Baldur Norddahl 22 Aug '18

22 Aug '18

Hello There is a lack of bidirectional one fiber (BIDI) options for 40G and 100G optics. Usually BIDI is implemented using two CWDM wavelengths, one for tx and one for rx. However there is also a lack of CWDM and DWDM options for 40G and 100G. Would it be possible to use an optical circulator like this one (customized to 1310 nm)? https://www.fs.com/de/en/products/33364.html Combined with a traditional two fiber 1310 nm 10 km 40G QSFP module like this: https://www.fs.com/de/en/products/24422.html The link distance would be 5 km. The optical circulator separates tx and rx by the direction the light travels in. It would work even though both directions use the same wavelength. There will likely be some reflection but hopefully attenuated enough that it is regarded as background noise. Has anyone done this? Any reason it would not work? Regards, Baldur

8 10

Pybatfish - Open source network validation SDK
by Ratul Mahajan 22 Aug '18

22 Aug '18

Hey, folks - Since many of you build and use tools for network validation, I wanted to share a quick announcement. We just released Pybatfish <http://github.com/batfish/pybatfish>, a Python SDK for Batfish. As you may know, Batfish is an open source framework for deep (semantic) validation in multi-vendor networks (which we presented at NANOG65 <https://www.youtube.com/watch?v=sKApcGY6MxQ>). Pybatfish will make it easy for you to leverage the power of Batfish and to embed validation in your testing/automation pipeline. Getting started is easy: Check out the Jupyter notebooks on our github page (or corresponding videos <https://www.youtube.com/channel/UCA-OUW_3IOt9U_s60KvmJYA>), or ping us on Slack <https://join.slack.com/t/batfish-org/shared_invite/enQtMzA0Nzg2OTAzNzQ1LTUx…> . Cheers.

1 0

New AS Number Block allocated to the RIPE NCC
by Ingrid Wijte 21 Aug '18

21 Aug '18

Dear Colleagues, The RIPE NCC has received the following AS Number Blocks from the IANA on 20 August 2018: 207260-208283 208284-209307 209308-210331 You may want to update your records accordingly. Best regards, Ingrid Wijte Registration Services Assistant Manager and Policy Development RIPE NCC

1 0

Re: Web UI DHCP Option 82
by daveb 20 Aug '18

20 Aug '18

There's no GUI but I'll second the Kea recommendation. At 09:36 AM 8/18/2018, Colton Conor wrote: >Mike, I am looking for the same thing. Does >Mikrotik have the ability to do what you are requesting?Â > >On Fri, Aug 17, 2018 at 5:11 PM Ryan Hamel ><<mailto:Ryan.Hamel@quadranet.com>Ryan.Hamel(a)quadranet.com> wrote: > >Mike, > >Take a look into Kea from ISC. The config is >JSON based, which allows for nearly any >scripting language to make changes, or you can >dig into how it works with MySQL for dynamic >operation >(<https://kea.isc.org/wiki/HostReservationsHowTo>https://kea.isc.org/wiki/HostReservationsHowTo) > >Â > >Ryan > >Â > >From: NANOG ><<mailto:nanog-bounces@nanog.org>nanog-bounces(a)nanog.org> >On Behalf Of Mike Hammett >Sent: Friday, August 17, 2018 1:51 PM >To: <mailto:nanog@nanog.org>nanog(a)nanog.org list ><<mailto:nanog@nanog.org>nanog(a)nanog.org> >Subject: Web UI DHCP Option 82 > >Â > >Are there any web interfaces out there for DHCP >servers that accommodate management of DHCP >option 82 configs? Neither webmin nor Glass seem >to handle ISC'sÂ agent.circuit-id outside of >presenting the raw config file. I can do that >just fine in nano, but I'm looking at something >more user-friendly so I'm not the only one that can work on it. > >I'm also cheap, so not looking at Infoblox or anything like that. > > > >----- >Mike Hammett >Intelligent Computing Solutions ><http://www.ics-il.com>http://www.ics-il.com > >Midwest-IX ><http://www.midwest-ix.com>http://www.midwest-ix.com

3 2

2nd call for presentations RIPE 77
by Benno Overeinder 20 Aug '18

20 Aug '18

Dear colleagues, Please note the approaching deadline of *26 August 2018* for RIPE 77 plenary programme submissions. You can find the CFP for RIPE 77 below or at https://ripe77.ripe.net/submit-topic/cfp/, for your proposals for plenary session presentations, tutorials, workshops, BoFs (Birds of a Feather sessions) and lightning talks. Please also note that speakers do not receive any extra reduction or funding towards the meeting fee at the RIPE Meetings, see the "Speakers" paragraph in CFP for more information. Kind regards, Benno Overeinder RIPE PC Chair https://ripe77.ripe.net/ripe-pc/ -------------------->>><<<-------------------- Call for Presentations A RIPE Meeting is an open event where Internet Service Providers, network operators and other interested parties get together. Although the meeting is mostly technical, it is also a chance for people to meet and network with others in their field. *RIPE 77 will take place from 15-19 October in Amsterdam, The Netherlands* The RIPE Programme Committee (PC) is now seeking content proposals from the RIPE community for the plenary sessions, BoFs (Birds of a Feather sessions), panels, workshops, tutorials and lightning talks at RIPE 77. See the full descriptions of the different presentation formats: https://ripe77.ripe.net/submit-topic/presentation-formats/ Proposals for plenary sessions, BoFs, panels, workshops and tutorials must be submitted for full consideration no later than *26 August 2018*. Proposals submitted after this date will be considered depending on the slots still available in the programme. The PC is looking for presentations covering the topics of network engineering and operations, including but not limited to: - IPv6 deployment - Managing IPv4 scarcity - Data centre technologies - Network and DNS operations - Internet governance and regulatory practices - Network and routing security - Content delivery - Internet peering and mobile data exchange - Connected Things (aka. Internet of Things - IoT) ---- Speakers ---- Presenters, RIPE Working Group Chairs and the RIPE Programme Committee are required to cover their own costs to attend a RIPE Meeting (meeting ticket, travel and accommodation). We have various ticket options available depending on your needs. In extraordinary circumstances, the RIPE Chair can waive the meeting fee for presenters. These requests are dealt with on a case-by-case basis via pc(a)ripe.net. Also note that, on an individual basis, participants can apply for a RIPE Fellowship or RACI to develop their professional or academic career. For more information, please visit: https://www.ripe.net/participate/ripe/ripe-fellowship https://www.ripe.net/participate/ripe/raci ---- Submissions ---- Presenters should be clear on whether they wish to submit a presentation for a plenary or working group (WG) session. At present, most working groups will solicit policy proposals, discussion points or other content directly via their mailing lists. If you’re not sure what kind of session you should be presenting at, please visit: https://ripe77.ripe.net/plenary-or-wg/ RIPE Meeting attendees are quite sensitive to keeping presentations non-commercial, and product marketing talks are strongly discouraged. Repeated audience feedback shows that the most successful talks focus on operational experience, research results, or case studies. For example, presenters wishing to describe a commercial solution should focus on the underlying technology and should not attempt a product demonstration. Presenters should indicate how much time they will require. In general, the time allocated for the different presentation formats is as follows: - Plenary presentations: 20-25 minutes presentation with 5-10 minutes discussion - Tutorials: up to two hours (Monday morning) - Workshops: one hour (during evening sessions) to two hours (Monday morning) - BoFs: approximately one hour (during evening sessions) - Lightning talks: 10 minutes in total for both the presentation and any discussion The following general requirements apply: - Proposals must be submitted using the meeting submission system, https://ripe77.ripe.net/submit-topic/ - Lightning talks should also be submitted using the meeting submission system (https://ripe77.ripe.net/submit-topic/) and can be submitted any time up to and including the meeting week. The allocation of lightning talks will be announced on short notice, in some cases on the same day but often one day prior to the time slot allocated. - Presenters who propose a panel or BoF are encouraged to include speakers from several (perhaps even competing) companies and/or a neutral facilitator. - All presentation proposals will only be considered by the PC if they contain at least draft presentation slides (slides may be updated later on). For panels, proposals must contain a clear description, as well as the names of invited panellists, presenters and moderators. ---- Diversity and Inclusion - On-Site Childcare and the RIPE Meeting Code of Conduct ---- Did you know that RIPE Meetings now have on-site childcare? You can reserve a spot for your child (age 6 months – 10 years) during the registration process for the meeting. Registrations for RIPE 77 will open mid-July. Childcare places are limited, so please be quick to reserve a spot for your child! Read about the experiences of our next generation of engineers at: https://labs.ripe.net/Members/agowland/ripe-meeting-diversity-efforts-on-si… Ensuring that RIPE Meeting values are upheld and that attendees experience a professional, respectful and safe meeting is a priority. Please do read the RIPE Meeting Code of Conduct: https://www.ripe.net/participate/meetings/ripe-meetings/ripe-meeting-code-o… --- If you have any questions or requests concerning content submissions, please email pc(a)ripe.net.

1 0