July 2016 - Test - lists.nanog.org

Re: cloudflare hosting a ddos service?
by Steve Atkins 26 Jul '16

26 Jul '16

> On Jul 26, 2016, at 7:58 PM, Justin Paine <justin(a)cloudflare.com> wrote: > > Folks, > > "For a long time their abuse@ alias was (literally) routed to /dev/null. I'm not > sure whether that's still the case or whether they now ignore reports manually." > > @Steve It (literally) never was. :) Yes, it was. The smiley doesn't make your statement true. > The team I manage processes > reports all day > long. If you have a report to file certainly do so, > https://www.cloudflare.com/abuse I gave up on doing that in late 2014 after reporting thousands of pieces of spam advertising websites hosted by Cloudflare, with no action taken, no reply received, no ticket created, *nothing*. Not in response to mail sent to abuse@cloudflare, not in response to backchannel reports, not in response to mentions in person to staff at conferences. (This was mostly people selling lists of credit card numbers rather than booters, but it's the same sort of issue). Just to see what had changed, I went back to look at the sites I reported to Cloudflare in 2014. The couple I spot-checked are still hosted by Cloudflare. Given that you (Cloudflare, rather than you personally) haven't changed your policy of never terminating abusive websites you host then continuing to report them to you seems fairly pointless. > > > On the topic of booters: > > Short version -- As someone already mentioned, CloudFlare continues > not to be a hosting provider. That's untrue, of course. You terminate the http connection; you're hosting the website; you're hiding the identity of any other operators involved; you continue to serve the website even when the backing server has been terminated. Adding an interstitial for sites hosting malware is nice and all, but the problematic customers are the ones that are selling access to those malware compromised machines. You are taking sole responsibility by your actions, while denying all responsibility in your public statements. > > Our CEO has broadly covered this topic several times. > https://blog.cloudflare.com/thoughts-on-abuse/ > > Even if we removed our service the website does not go away,it > doesn't solve the problem if we temporarily stop providing DNS to the > domain(s). An often overlooked but extremely important note: there are > some situations where law > enforcement has required that we *not* terminate service to certain > websites. In those situations we are of course not allowed to discuss > specifics. Cheers, Steve

1 0

Re: cloudflare hosting a ddos service?
by Paras Jha 26 Jul '16

26 Jul '16

Justin, The only problem with that statement is that it's not true: if you did terminate service to them, the websites would go away. Maybe not today, but eventually. "Network stresser" owners are notorious for trying to take out the competition. Cloudflare provides free protection for these services to stay online. Most other ISPs wouldn't tolerate such shenanigans, whether it be for facilitating illegal activities or being on the receiving end of DDoS attacks, and would kick them off. On Tue, Jul 26, 2016 at 10:58 PM, Justin Paine <justin(a)cloudflare.com> wrote: > Folks, > > "For a long time their abuse@ alias was (literally) routed to /dev/null. > I'm not > sure whether that's still the case or whether they now ignore reports > manually." > > @Steve It (literally) never was. :) The team I manage processes > reports all day > long. If you have a report to file certainly do so, > https://www.cloudflare.com/abuse > > > On the topic of booters: > > Short version -- As someone already mentioned, CloudFlare continues > not to be a hosting provider. > > Our CEO has broadly covered this topic several times. > https://blog.cloudflare.com/thoughts-on-abuse/ > > Even if we removed our service the website does not go away, it > doesn't solve the problem if we temporarily stop providing DNS to the > domain(s). An often overlooked but extremely important note: there are > some situations where law > enforcement has required that we *not* terminate service to certain > websites. In those situations we are of course not allowed to discuss > specifics. > > ____________ > Justin Paine > Head of Trust & Safety > CloudFlare Inc. > PGP: BBAA 6BCE 3305 7FD6 6452 7115 57B6 0114 DE0B 314D > > > On Tue, Jul 26, 2016 at 7:42 PM, Paras Jha <paras(a)protrafsolutions.com> > wrote: > > A five minute Google search revealed this, which is just the tip of the > > iceberg > > > > booter.xyz > > exitus.to > > zstress.net > > critical-boot.com > > instress.club > > webstresser.co > > anonymousstresser.com > > rawdos.com > > kronosbooter.com > > alphastress.com > > synergy.so > > str3ssed.me > > layer7.pw > > > > There are probably hundreds > > > > > > > > On Tue, Jul 26, 2016 at 10:33 PM, Paras Jha <paras(a)protrafsolutions.com> > > wrote: > > > >> This is quite common, almost all of the DDoS-for-hire services are > hosted > >> behind CloudFlare, and a great majority of them take PayPal. Another one > >> had even managed to secure an EV SSL cert. > >> > >> On Tue, Jul 26, 2016 at 10:24 PM, Dovid Bender <dovid(a)telecurve.com> > >> wrote: > >> > >>> I used to have a boss that was convinced that MCafee was writing > viruses > >>> to stay in business.... > >>> > >>> Regards, > >>> > >>> Dovid > >>> > >>> -----Original Message----- > >>> From: Phil Rosenthal <pr(a)isprime.com> > >>> Sender: "NANOG" <nanog-bounces(a)nanog.org>Date: Tue, 26 Jul 2016 > 22:17:53 > >>> To: jim deleskie<deleskie(a)gmail.com> > >>> Cc: NANOG list<nanog(a)nanog.org> > >>> Subject: Re: cloudflare hosting a ddos service? > >>> > >>> Plus, it’s good for business! > >>> > >>> -Phil > >>> > >>> > On Jul 26, 2016, at 10:14 PM, jim deleskie <deleskie(a)gmail.com> > wrote: > >>> > > >>> > sigh... > >>> > > >>> > On Tue, Jul 26, 2016 at 10:55 PM, Patrick W. Gilmore < > patrick(a)ianai.net > >>> > > >>> > wrote: > >>> > > >>> >> CloudFlare will claim they are not hosting the problem. They are > just > >>> >> hosting the web page that lets you pay for or points at or otherwise > >>> >> directs you to the problem. > >>> >> > >>> >> The actual source of packets is some other IP address. Therefore, > they > >>> can > >>> >> keep hosting the web page. It is not sending the actual > >>> >> [spam|DDoS|hack|etc.], right? So stop asking them to do something > >>> about it! > >>> >> > >>> >> Whether you think that is the proper way to provide service on the > >>> >> Internet is left as an exercise to the reader. > >>> >> > >>> >> -- > >>> >> TTFN, > >>> >> patrick > >>> >> > >>> >>> On Jul 26, 2016, at 9:49 PM, Mike <mike-nanog(a)tiedyenetworks.com> > >>> wrote: > >>> >>> > >>> >>> Hi, > >>> >>> > >>> >>> So vbooter.org's dns and web is hosted by cloudflare? > >>> >>> > >>> >>> "Using vBooter you can take down home internet connections, > websites > >>> and > >>> >> game servers such us Minecraft, XBOX Live, PSN and many more." > >>> >>> > >>> >>> dig -t ns vbooter.org > >>> >>> > >>> >>> ; <<>> DiG 9.9.5-3ubuntu0.8-Ubuntu <<>> -t ns vbooter.org > >>> >>> ;; global options: +cmd > >>> >>> ;; Got answer: > >>> >>> ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 62177 > >>> >>> ;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: > 1 > >>> >>> > >>> >>> ;; OPT PSEUDOSECTION: > >>> >>> ; EDNS: version: 0, flags:; udp: 512 > >>> >>> ;; QUESTION SECTION: > >>> >>> ;vbooter.org. IN NS > >>> >>> > >>> >>> ;; ANSWER SECTION: > >>> >>> vbooter.org. 21599 IN NS rick.ns.cloudflare.com. > >>> >>> vbooter.org. 21599 IN NS amy.ns.cloudflare.com. > >>> >>> > >>> >>> dig -t a www.vbooter.org > >>> >>> > >>> >>> ; <<>> DiG 9.9.5-3ubuntu0.8-Ubuntu <<>> -t a www.vbooter.org > >>> >>> ;; global options: +cmd > >>> >>> ;; Got answer: > >>> >>> ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 34920 > >>> >>> ;; flags: qr rd ra; QUERY: 1, ANSWER: 3, AUTHORITY: 0, ADDITIONAL: > 1 > >>> >>> > >>> >>> ;; OPT PSEUDOSECTION: > >>> >>> ; EDNS: version: 0, flags:; udp: 512 > >>> >>> ;; QUESTION SECTION: > >>> >>> ;www.vbooter.org. IN A > >>> >>> > >>> >>> ;; ANSWER SECTION: > >>> >>> www.vbooter.org. 299 IN CNAME vbooter.org. > >>> >>> vbooter.org. 299 IN A 104.28.13.7 > >>> >>> vbooter.org. 299 IN A 104.28.12.7 > >>> >>> > >>> >>> > >>> >>> Can anyone from cloudflare answer me why this fits with your > >>> business > >>> >> model? > >>> >>> > >>> >>> Mike- > >>> >> > >>> >> > >>> > >>> > >> > >> > >> -- > >> Regards, > >> Paras > >> > >> President > >> ProTraf Solutions, LLC > >> Enterprise DDoS Mitigation > >> > > > > > > > > -- > > Regards, > > Paras > > > > President > > ProTraf Solutions, LLC > > Enterprise DDoS Mitigation > -- Regards, Paras President ProTraf Solutions, LLC Enterprise DDoS Mitigation

1 1

cloudflare hosting a ddos service?
by Mike 26 Jul '16

26 Jul '16

Hi, So vbooter.org's dns and web is hosted by cloudflare? "Using vBooter you can take down home internet connections, websites and game servers such us Minecraft, XBOX Live, PSN and many more." dig -t ns vbooter.org ; <<>> DiG 9.9.5-3ubuntu0.8-Ubuntu <<>> -t ns vbooter.org ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 62177 ;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 512 ;; QUESTION SECTION: ;vbooter.org. IN NS ;; ANSWER SECTION: vbooter.org. 21599 IN NS rick.ns.cloudflare.com. vbooter.org. 21599 IN NS amy.ns.cloudflare.com. dig -t a www.vbooter.org ; <<>> DiG 9.9.5-3ubuntu0.8-Ubuntu <<>> -t a www.vbooter.org ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 34920 ;; flags: qr rd ra; QUERY: 1, ANSWER: 3, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 512 ;; QUESTION SECTION: ;www.vbooter.org. IN A ;; ANSWER SECTION: www.vbooter.org. 299 IN CNAME vbooter.org. vbooter.org. 299 IN A 104.28.13.7 vbooter.org. 299 IN A 104.28.12.7 Can anyone from cloudflare answer me why this fits with your business model? Mike-

11 13

Speedtest.net not accessible in Chrome due to deceptive ads
by Janusz Jezowicz 26 Jul '16

26 Jul '16

Since this morning Speedtest.net is not accessible in Chrome Reason: https://www.google.com/transparencyreport/safebrowsing/diagnostic/#url=c.sp… For any ISPs/content providers linking to speedtest.net you may want to swap links to a different website or host your own speed test. e.g. Netflix at http://fast.com Regards, Janusz Jezowicz *Speedchecker Ltd* *email*: janusz(a)speedchecker.xyz *skype*: jezowicz *phone*: +442032863573 *web*: www.speedchecker.xyz The Black Church, St. Mary’s Place, Dublin 7, D07 P4AX, Ireland

16 22

Notice about project to roll the root zone KSK
by Matt Larson 26 Jul '16

26 Jul '16

I realize DNS operational content isn't the usual NANOG fare, but rolling the root zone KSK for the first time is a significant-enough event that I wanted to send to this list anyway. TL;DR: The root zone KSK is changing on October 11, 2017 (yes, over a year away). If you're doing DNSSEC validation, you should care. If you're not the DNS person in your organization, please pass this notice on to that person. If the topic interests you, more information is below. Matt -- Matt Larson VP of Research Office of the CTO, ICANN > Begin forwarded message: > > From: Matt Larson <matt.larson(a)icann.org> > Subject: Plan documents for root KSK roll project now available > Date: July 26, 2016 at 8:59:45 AM EDT > To: <ksk-rollover(a)icann.org> > > On Friday, July 22, in the interests of transparency and to notify the DNS operational community, ICANN posted plans <https://www.icann.org/resources/pages/ksk-rollover#operational-plans> to roll the root zone key signing key (KSK). These plans were developed by the Root Zone Management Partners: ICANN in its role as the IANA Functions Operator, Verisign acting as the Root Zone Maintainer, and the U.S. Department of Commerce's National Telecommunications and Information Administration (NTIA) as the Root Zone Administrator. The plans incorporate the March 2016 recommendations <https://www.iana.org/reports/2016/root-ksk-rollover-design-20160307.pdf> of the Root Zone KSK Rollover Design Team, after it sought and considered public comment <https://www.icann.org/news/announcement-2013-03-08-en> on a proposed rollover process. > > The process of creating a new key, using it to sign the root DNSKEY RRset and securely destroying the old key will start in Q4 2016 and last until Q3 2016, though the portions resulting in visible changes in DNS occur between Q3 2016 and Q1 2017. The important milestones in the project are: > > - October 26, 2016: The new KSK is generated in ICANN's U.S. East Coast key management facility (KMF). > - February, 2017: The new KSK is copied to ICANN's U.S. West Coast KMF and is considered operationally ready, and ICANN publishes the new key at https://data.iana.org/root-anchors/root-anchors.xml <https://data.iana.org/root-anchors/root-anchors.xml>. (The exact date is dependent on the timing of the Q1 2017 key ceremony, which has not yet been scheduled.) > - July 11, 2017: The new KSK appears in the root DNSKEY RRset for the first time. > - October 11, 2017: The new KSK signs the root DNSKEY RRset (and the old KSK no longer signs). This date is the actual KSK rollover. > - January 11, 2018: The old KSK is published as revoked (per RFC 5011, "Automated Updates of DNS Security"). > > What you need to do > > If you operate any software performing DNSSEC validation (such as a security-aware recursive name server) that implements the RFC 5011 automated trust anchor update protocol and this functionality is enabled, you have no action: your software will notice the new KSK (authenticated by the old KSK) and update its trust anchor store accordingly. > > If you operate any software performing DNSSEC validation that does not implement RFC 5011 or if you don't use the RFC 5011 protocol, you will need to update your software's trust anchor configuration manually to add the new KSK before October 11, 2017. You can obtain the new KSK in February, 2017, using one of the methods described in the "Trust Anchor Publication" section of 2017 KSK Rollover Operational Implementation Plan <https://www.icann.org/en/system/files/files/ksk-rollover-operational-implem…> (one of the aforementioned recently published plans). > > If you write, package or distribute software that performs DNSSEC validation and you hard code the root KSK (e.g., in code or configuration files), you should update your software with the new KSK when it becomes available in February, 2017. > > Staying informed > > ICANN will post occasional notices to various operational forums to keep the community informed of this project's progress, but we strongly suggest that anyone with an interest subscribe to the root KSK rollover mailing list <https://mm.icann.org/mailman/listinfo/ksk-rollover> operated by ICANN (ksk-rollover(a)icann.org <mailto:ksk-rollover@icann.org>). The list is extremely low volume. > > The ICANN staff supporting and implementing the root KSK rollover project welcome your questions and comments: please direct them to the ksk-rollover(a)icann.org <mailto:ksk-rollover@icann.org> list. > > Matt > -- > Matt Larson > VP of Research > Office of the CTO, ICANN >

1 0

Clueful BGP from TW-Telecom/L3
by Scott Morris 25 Jul '16

25 Jul '16

Is there per chance anyone hanging on here who is clueful about BGP working with TW-Telecom and the recent integration with Level3???? I have a client that I consult with whose route is not getting sent from TW to L3 and the techs on the case are convinced we need to put different BGP communities in (both to TW link and other provider link) which of course we are putting in to satisfy them, but magically it is not working. This SHOULD be an easy thing to figure out using the Looking Glass servers within both TW and Level3, but this concept is lost on techs we are dealing with. Anyone internal there who can contact me off-list would be greatly appreciated! Scott swm(a)emanon.com

1 0

Google captcha problem on newly rented subnet
by abuse.anmaxx＠yahoo.com 25 Jul '16

25 Jul '16

We'rehaving some problems with a newly rented /24 subnet in context with Google.Google always asksfor entering a captcha code three times in a row.The reason for thatcan't be a misconfiguration of the server, because we have more than 40different servers all around the world configured exactly the same way where this problem doesn't appear. It could be due to the history of the subnet. Can any representativeof Google please contact us via E-Mail, in order to tell him/her which subnetis affected by the problems and solve the issue by removing those permanent queries? Anders Philip Temsvåg

2 1

Akamai IPv6 contact needed
by Yang Yu 25 Jul '16

25 Jul '16

Some servers are not serving content over IPv6 HTTPS. It fails in such a way that most applications can't fall back to IPv4. tcp/443 is open but RST as soon as client sends TLS 1.2 client hello. It has been this way for 24+ hours. >>> $ telnet 2600:1404:18::17d7:fbc 443 Trying 2600:1404:18::17d7:fbc... Connected to 2600:1404:18::17d7:fbc. Escape character is '^]'. Connection closed by foreign host > ncat -6 --ssl -v 2600:1404:18::17d7:fac 443 Ncat: Version 7.00SVN ( https://nmap.org/ncat ) Ncat: Input/output error. >>> www.apple.com. 681 IN CNAME www.apple.com.edgekey.net. www.apple.com.edgekey.net. 11306 IN CNAME www.apple.com.edgekey.net.globalredir.akadns.net. www.apple.com.edgekey.net.globalredir.akadns.net. 1664 IN CNAME e6858.dscc.akamaiedge.net. e6858.dscc.akamaiedge.net. 5 IN AAAA 2600:1404:18::17d7:fac e6858.dscc.akamaiedge.net. 5 IN AAAA 2600:1404:18::17d7:fbc > 2600:1404:18::17d7:0/112 serves www.apple.com, download.microsoft.com etc. >>> HTTP does work $ wget http://www.apple.com --2016-07-25 03:09:17-- http://www.apple.com/ Resolving www.apple.com (www.apple.com) 2600:1404:18::17d7:fbc, 2600:1404:18::17d7:fac, 23.11.55.206 Connecting to www.apple.com (www.apple.com)|2600:1404:18::17d7:fbc|:80... connected. HTTP request sent, awaiting response... 200 OK >>> $ dig whoami.akamai.com +short whoami.akamai.net. 72.183.81.39 Thanks. Yang

2 1

students questions
by sam 25 Jul '16

25 Jul '16

Hello if this is not appropriate for this list please excuse me and disregard this email. I thought of no better place than this place however if there is a better place for this email please advise and I will direct the email and the student to the questions. I received an email form a student this morning asking the following questions. 1. Are there any email providers that market to professional but offer a student rate or are of good quality but inexpensive etc.. 2. I have looked at the Microsoft exchange server in the cloud while it looks promising it does not seems to fit my cost ratio 3. I would mainly like to be able to have a professional email address so when I apply for jobs and other business of that sort I can be seen as a professional and to gather my email from various sources i.e. Gmail, Hotmail etc. and to present a more professional appearance to my work and school work etc.. I responded that he should look at google apps, however his questions got me thinking and I google around for an answer to give him, however I am not as well versed as I should be in the cloud besides for backup service and active directory management. I would like to know if you guys have any places I own give the student. Thanks Samual Office of technology education Please excuse grammar and spelling errors as this was typed on a smartphone. -----BEGIN PGP MESSAGE----- Version: GnuPG v2 owFdVAtsFEUYbqkQvPQoGgpUHo5FzEHKUcqr2FCoILY8pFCQR1Jlbnf2brndnXVm t9fjFSOCFtBUimjBNtJCI5AIFOQhFbSgxAgURQIo8rKIaUTTVBERxH9274rlcpfb 2fn/b77/+79/yr1JCV0TScLQ81mX05oSv24JJMxZP+ZGPtE0ilQFWSGVI/ga1ELY NBk1mYotghTK3D1N5RYyNYI5QaRUsuFPJwgbMpJVzkgQM9kNJDpWNT8qgBW1gyEL UQVQUYBYFmGAgCUCW9hwo911iEZICew6RAgjggnumNJOxMGPM8FyicpdGgUoomoa sGFEsgRMLFLsiRW3bJkYsEOd5cs24ZZKDe73egoQ5BC1hMgQHUuD83Tg0J4ljtYp M1QjiDAPiz8Bo1AQMCJW9wGR1zPMj5xPHiOxirARjVNntESVCeNCBgvpmIWJQws2 FMI5YGANBWyhnAL13yfBREdABwx4oGqQUhmOxZpqRZ141SClJjE4VIKIJfmvvlLn 9WTFqBSgEIb3GqVhUacr0TRVYpRTxRI9haYEQSfCnFYYToCkUVtGkZCqQVMsJ5sL orrKRdHwSqbEtQ0nROeiDgXe6lEkUe5QVikIMrydRYTamgxVq4YWBVeFiUgJgEAB zXl0WOKOYsQ6KcsMXiFOgRAxAAucCiDCGgtpgDutpkJuUAPoiViquCpzyixIkKC/ AVEjpGP+4DGOVSgKYgdDjzdMgXJRCWYqtcXhNpOgYtVP/Og5sZ+B8qnlBArN4yAm UBU9w8I15IFzTJNghg3JKRjOiVAWdhK5FKJUc9cCDcyJkPsTJuUmNWQiuyUJT4cc MUVXREfBEEEQEeB5RvtMCeO2exNCLDG3Vuizo6rhuNidnXgqozashaKgFDZ4BBCE JMJSIVW/Dwvi6+5twVEEbhEEL7kwFoetGC9QuoONAoSD8bkDH8BS2DYdt6mSO8FY ssQx7gRTFgWTGDhIdJDR326cuGPCBo2I+yJKbRS0ozzmG5gy574QLGjEcIn/b/z9 MTVngdnByV5PEdZhguBhuqIIIsIwRAoZVKNBMIBsS8LBRiytsMMFGGRYh/F1O2eC CEJPwhiF2cbcvTMi4iFqgjIAAqMM8ZYZogZxmJR16vtQQmLXhC6dO4nrOMHzcPf4 HX1lZMrtpMXDM+ftvL7Oc7V7y5oF/sNjKk+l7Mr9nQQWdvlW2pmknlp+7vGc5rsZ plKfdP3MrDtZ4S8b7/0yUL634+OKtwu9F36aNzmw+c3GwP59Y+f6sof+NWtagnW6 fvvKaxNHlc2+lH/+yfU/D/lg8Onvvqqvz1g9s7ri2dTK6ak1ZxsSq349M6P12PSj Ff7RV7In59+yW58YtfiN6hHW9/4iVsX63t1mp51U01O+aPCkKgPeinqtCbt6k9oP UZ8B/RXfp59sKn5q0I4Zrd0KG7VFM7f3qBh7zB52ee+2C1OSD2x5/XgZe/Usa/ot reGdjNGh4p2Dt/zQduxE9b8NzX2Ti1bU7Njwnpl2boRP2tP0uS/vwv6LgTGD0s+Y f+fW6X/glpu9D437qLJ1LV7X3OtmwchFvjvrtFUvZC1flpgdJs3+rav6VfXvZmS3 bFx6Ut2aeevA8dZ/LvqkouKNNT2u8aljlz82aUVb79bnB/65enxyy5L9RnmS52DO o20r26bOn1t46GDpKPvI3vpb41bMTrd6NY+P1r2WenjRxEsvLqC1czOz5uyaXz0n r8f5JRs2bV3ax/dS3chlJ2xf9e5Ma3TnnH63NynXOl2sThzx7pArFXTg7mGD/Pt6 BtdWPpNXUj6pLP3p67Wh9xP31BypOlc8M6u0TfXmTkuxa298M6E0+Ui/NRWb0xt7 7mnKrWPlRWkHShf/+EjOlP8A =cNlY -----END PGP MESSAGE-----

9 8

Call for presentations RIPE 73
by Benno Overeinder 25 Jul '16

25 Jul '16

Dear colleagues, Please find the CFP for RIPE 73 below or at https://ripe73.ripe.net/submit-topic/cfp/. The deadline for submissions is 28 August 2016. Please also note that speakers do not receive any extra reduction or funding towards the meeting fee at the RIPE Meetings. Kind regards, Benno Overeinder RIPE PC Chair https://www.ripe.net/participate/meetings/ripe-meetings/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 73 will take place from 24-28 October 2016 in Madrid, Spain. 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 73. See the full descriptions of the different presentation formats, https://ripe73.ripe.net/submit-topic/presentation-formats/. Proposals for plenary sessions, BoFs, panels, workshops and tutorials must be submitted for full consideration no later than 28 August 2016. Proposals submitted after this date will be considered depending on the remaining available space in the programme. The PC is looking for presentations covering topics of network engineering and operations, including but not limited to: - IPv6 deployment - Managing IPv4 scarcity in operations - Commercial transactions of IPv4 addresses - Data centre technologies - Network and DNS operations - Internet governance and regulatory practices - Network and routing security - Content delivery - Internet peering and mobile data exchange - Internet of Things (IoT) Submissions 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 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 - Lightning talks: 10 minutes The following general requirements apply: - Proposals must be submitted using the meeting submission system, https://ripe73.ripe.net/submit-topic/submission-form/. - Lightning talks should also be submitted using the meeting submission system (https://ripe73.ripe.net/submit-topic/submission-form/) 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. - Due to potential technical issues, presenters/panellists should be physically present at the RIPE Meeting. If you have any questions or requests concerning content submissions, please email pc [at] ripe [dot] net. -- Benno J. Overeinder NLnet Labs http://www.nlnetlabs.nl/

1 0