Hello PeeringDB users / hello SwiNOG,
the PeeringDB Product Committee (PC, ) is charged with steering the
future product development and running the market outreach efforts to
continuously improve the value that PeeringDB delivers to the networks
registered with PeeringDB, and the broader community.
We're looking for feedback and input from the community on our charter
proposal. Please take this short survey . Your input and comments are
email: arnold(a)nipper.de phone: +49 6224 5593407 2
mobile: +49 172 2650958 fax: +49 6224 5593407 9
18 coming, cool!
Get yourself registered now: http://swinog.be/
Cheers, have a great weekend!
From: Emanuel Kleindienst [mailto:firstname.lastname@example.org]
Sent: Freitag, 2. September 2016 14:30
Subject: Joined SwissIX - SwiNOG-BE159 - Beer Event 159 @ Erzbierschof Zurich, Monday, 2016-09-26
Dear SwissIXers & SwiNOGers,
JOINED SwiNOG & SwissIX Beering
Let's have some Beer & Food at Erzbierschof - an new location AGAIN!!!
Upcoming events for rest of 2016:
> SwiNOG-BE160: Mo, 24.10.16
> SwiNOG-BE161: Mo, 28.11.16
> SwiNOG-BE162: Mo, 12.12.16 (Christmas dinner)
Looking forward seeing you!
Emanuel, mobile +41 79 382 73 77, Email emanuel(a)vshn.ch
Details for the next event:
Event: Joined SwissIX - SwiNOG-BE159 - Beer Event 159
When? Monday, 26th September 2016 18:30
Freischuetzgasse 10, 8004 Zurich
(GoogleMaps Link: http://https://goo.gl/maps/va7vLZkHngy)
Places available? 35
!! Please sign up if you're really coming - because the seats are limited! !!
Start: Friday, 2nd September 2016 - 14:20
Stop: Monday, 26th September 2016 - 17:00
Since we have to make reservations, I need to know who's coming and who not.
If you can't attend and you're registered please inform me ASAP (+41 79 382 73 77).
Hi Roger, can you text me? I've no time to kill the swinog inbox :(
+41 79 370 41 57
Gesendet mit meinem HTC
----- Nachricht beantworten -----
Von: "Roger" <roger(a)mgz.ch>
Betreff: [swinog] ping
Datum: Do., Sep. 22, 2016 15:07
swinog mailing list
As there is an upcoming SwiNOG.... lets throw some people under the bus
before they arrive. Or at least allow them time to come up with more
Some quotes from Swiss ISPs from the Call Your ISP page:
"Currently, as demand for IPv6 is very low, we have no plans to
introduce IPv6 native.
"No plans to support IPv6 for our private and SoHo clients"
"The plan is to move everyone on DSLite."
"Provider info: IPv6 is "planned" and soon should get a priority status.
When that "soon" will be is not yet known."
"They know what IPV6 is, eventually they will provide it"
Come on folks, it is 2016! IPv6 is *20 years* old...
Even Sky.uk was able to get it working.
Oh and note: Dual-stack IPv4 + IPv6, along with a /56 per user.
It is not that hard to get right.... and yeah, you kinda had 20 years
already to 'plan' for this....
--- rainer(a)ultra-secure.de wrote:
From: Rainer Duffner <rainer(a)ultra-secure.de>
> Am 18.09.2016 um 08:11 schrieb Fredy Kuenzler <kuenzler(a)init7.net>:
> Friday night we observed several Brocade MLXe linecards rebooting
> (several locations, i.e. Amsterdam, Frankfurt, Geneva), which
> caused network instability due to flapping iBGP etc.
"Take Down the Internet"
"it feels like a large nation state...China or Russia"
"I am unable to give details"
"It feels like a nation's military cybercommand"
Seems like FUD to get viewers. 'The sky's going to fall and I can't
tell you why or when, but I know it is. Trust me.' Where's the
technical details so we can make an informed decision, rather than
"it feels like..."
swinog mailing list
Friday night we observed several Brocade MLXe linecards rebooting (several locations, i.e. Amsterdam, Frankfurt, Geneva), which caused network instability due to flapping iBGP etc.
As of now we know that iWay and nine.ch suffered from similar issues in the same time window, and we believe that they use also Brocade MLXe.
Tonight around 4 a.m. symptoms occurred again, on a lesser degree. nine.ch reports it too.
For reference the tickets:
Did anyone else observed similar symptoms?
Since these routers operate in various locations and ASNs but are the same make/model I suppose it's a software security issue. Can malicious packets force a linecard reboot?
Init7 (Switzerland) Ltd.
A little reminder to everyone who has not cast their vote yet:
On September 25, the Swiss citizens will decide whether to accept or refuse
the new NDG/LRens/LAIn/LSI/ISA (Nachrichtendienstgesetz/Loi fédérale sur le
renseignement/Legge federale sulle attività informative/Lescha federala davart
il servetsch d'infurmaziun/Intelligence Service Act):
Please don't forget to vote!
Dear SwiNOG supporter,
this is the official Call for Paper email. Please send your proposal to
swinog-core (at) swinog.ch or directly to me.
The 30th meeting of the Swiss Network Operators Group (SwiNOG) will be held
in Berne on top of the Gurten on November 4th 2016.
Important Dates for SwiNOG#30
17.08.2016 Announcement of Meeting
05.09.2016 Registration opens
14.09.2016 Call for Papers
16.10.2016 Call for Papers closing
23.10.2016 Final publication of agenda
27.10.2016 Registration closes
01.11.2016 Deadline for all slides
04.11.2016 Meeting day
Topics for Presentations/Talks
The number and length of presentations per session is not fixed, although
due to time constraints we would prefer the length of the presentations to
be between 5 to 45 minutes.
Here is a non-exhaustive list of typical SwiNOG meeting topics:
- Security - DDOS Mitigation - AntiSpam
- Open Source tools
- International view of the internet (incidents, outages, measurements)
- Server applications (DNS, Web, etc.)
- Legal issues (BÜPF, etc.)
- Telecommunication politics (Net Neutrality, Incumbent monopoly, etc.)
-> PLEASE feel free to talk to us about any kind of topic and
You can always start a discussion on the list - I'm sure people join in.
Language of Slides and Talks
The whole day will be held in English, therefore we kindly ask you to
produce your presentation in English.
All submissions must have a strong technical bias and must not be solely
promotional for your employer.
Please remember that your presentations should be suitable for a target
audience of technicians from varied backgrounds, working for companies whose
sizes may vary considerably.
To submit a proposal for a presentation, we request that you provide the
following information to <swinog-core at swinog.ch>:
* the name of the presenter (and if applicable your affiliation)
* a working email address
* the name and number of the topic which will contain the presentation
* the title of the presentation
* its expected length (in minutes)
* a short abstract of the presentation (so we know what it is about)
We also welcome suggestions for specific presentations which you feel would
be valuable to the SwiNOG community.
Please be aware that your presentation will be published on the SwiNOG
website after the event. We can publish modified slides if requested - it
might be that some confidential data will be presented by you which are not
intended for publication on the internet.
SwiNOG Core Team
General Information (SwiNOG Community)
The Swiss Network Operators Group (SwiNOG) is an informal group of people
who are concerned with engineering and operation of the Swiss Internet.
SwiNOG exists to enhance the quality of Internet services available in
Switzerland. It does this by fostering the free exchange of technical ideas
and information between different companies and organisations.
SwiNOG is a community for professionals who are operating, designing or
researching the Internet. It provides a technical forum where those working
on, with and for the Internet can come together to solve problems with every
aspect of their (net)work.
The meeting is designed to provide an opportunity for the exchange of
information among network operators, engineers, researchers and other
professionals close to the network community.
More information about SwiNOG can be found at http://www.swinog.ch/,
Information about the meeting will be published at
General Information (SwiNOG Organisation)
The SwiNOG Organisation Association is a non-profit association under
article 60 and further of the swiss civil law. It manages the SwiNOG
community ressources (domain, web, mailing-lists, etc..) and organises
Five years ago PCH conducted the first, and to date only, comprehensive survey characterizing Internet peering agreements.
The document that resulted can be found here: https://www.pch.net/resources/Papers/peering-survey/PCH-Peering-Survey-2011… <https://www.pch.net/resources/Papers/peering-survey/PCH-Peering-Survey-2011…>
That document was one of the principal inputs to an important document that the OECD publishes every five years, one that recommends communications regulatory policy to OECD member nations: http://www.oecd.org/officialdocuments/publicdisplaydocumentpdf/?cote=DSTI/I… <http://www.oecd.org/officialdocuments/publicdisplaydocumentpdf/?cote=DSTI/I…>
The survey had several useful findings which hadn’t previously been established as fact—most notably the portion of peering relationships that are “handshake” agreements, without written contract. These findings have improved the regulatory environments in which many of us operate our networks.
At the time of the 2011 survey, we committed to repeating the survey every five years, so as to provide an ongoing indication of the direction peering trends take. It’s now five years later, so we’re repeating the survey.
The survey is global in scope, and our goal is to reflect the diversity of peering agreements in the world; we’re interested in large ISPs and small ISPs, ISPs in Afghanistan and in Zimbabwe, bilateral agreements and multilateral, private and public. Our intent is to be as comprehensive as possible. In 2011, the responses we received represented 86% of all of the world’s ISPs and 96 countries. We would like to be at least as inclusive this time.
In 2011, we promised to collect the smallest set of data necessary to answer the questions, to perform the analysis immediately, and not to retain the data after the analysis was accomplished. In that way, we ensured that the privacy of respondents was fully protected. We did as we said, no data was leaked, and the whole community benefited from the trust that was extended to us. We ask for your trust again now as we make the same commitment to protect the privacy of all respondents, using the same process as last time. We are asking for no more data than is absolutely necessary. We will perform the analysis immediately upon receiving all of the data. We will delete the data once the analysis has been performed.
We would like to know the following five pieces of information relative to each Autonomous System you peer with:
• Your ASN
• Your peer’s ASN (peers only, not upstream transit providers or downstream customers)
• Whether a written and signed peering agreement exists (the alternative being a less formal arrangement, such as a "handshake agreement")
• Whether the terms are roughly symmetric (the alternative being that they describe an agreement with different terms for each of the two parties, such as one compensating the other, or one receiving more or fewer than full customer routes)
• Whether a jurisdiction of governing law is defined
• Whether IPv6 routes are being exchanged (this year, we’ll still assume that IPv4 are)
The easiest way for us to receive the information is as a tab-text or CSV file or an Excel spreadsheet, consisting of rows with the following columns:
Your ASN: Integer
Peer ASN: Integer
Written agreement: Boolean
Governing Law: ISO 3166 two-digit country-code, or empty
IPv6 Routes: Boolean
42 <tab> 715 <tab> false <tab> true <tab> us <tab> true <cr>
42 <tab> 3856 <tab> true <tab> true <tab> us <tab> true <cr>
We are asking for the ASNs only so we can avoid double-counting a single pair of peers when we hear from both of them, and so that when we hear about a relationship in responses from both peers we can see how closely the two responses match, an important check on the quality of the survey. As soon as we've collated the data, we'll strip the ASNs to protect privacy, and only the final aggregate statistics will be published. We will never disclose any ASN or any information about any ASN. We already have more than 8,000 ASN-pair relationships documented, and we hope to receive as many more as possible. We'd like to finish collecting data by the end of September, about two weeks from now.
If you’re peering with an MLPA route-server, you’re welcome to include just the route-server’s ASN, if that’s easiest, rather than trying to include each of the peer ASNs on the other side of the route-server. Either way is fine.
If all of your sessions have the same characteristics, you can just tell us what those characteristics are once, your own ASN once, and give us a simple list of your peer ASNs.
If your number of peers is small enough to be pasted or typed into an email, rather than attached as a file, and that’s simpler, just go ahead and do that.
If you have written peering agreements that are covered by non-disclosure agreements, or if your organizational policy precludes disclosing your peers, but you’d still like to participate in the survey, please let us know, and we’ll work with whatever information you’re able to give us and try to ensure that your practices are statistically represented in our results.
If you're able to help us, please email me the data in whatever form you can. If you need a non-disclosure, we're happy to sign one.
Finally, if there are any other questions you’d like to see answered in the future, please let us know so that we can consider addressing them in the 2021 survey. The question about IPv6 routing in this year’s survey is there because quite a few of the 2011 respondents asked us to include it this time.
Please respond by replying to this email, before the end of September.
Thank you for considering participating. We very much appreciate it, and we look forward to returning the results to the community.
Packet Clearing House