Many ISPs need the kinds of quality shaping cake can do
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: libreqos <libreqos@lists.bufferbloat.net>,
	 Frantisek Borsik <frantisek.borsik@gmail.com>
Subject: [LibreQoS] Fwd: Call for Presentations EPF 2023, Prage, Czech Republic // NANOG
Date: Fri, 4 Aug 2023 15:41:30 -0700	[thread overview]
Message-ID: <CAA93jw7FbKq3TTRsw8HgPGgO7Q9Mspjxu8fUmKo-xm=khTe1wA@mail.gmail.com> (raw)
In-Reply-To: <1f0cbf1b-6bd1-7aa0-6c94-3d492d5f288a@nipper.de>

[-- Attachment #1: Type: text/plain, Size: 2331 bytes --]

---------- Forwarded message ---------
From: Arnold Nipper via NANOG <nanog@nanog.org>
Date: Sun, Apr 23, 2023 at 8:15 AM
Subject: Call for Presentations EPF 2023, Prage, Czech Republic // NANOG
To: <nanog@nanog.org>


Dear all,

this is the Call for Presentations for the European Peering Forum 2023.

AMS-IX, DE-CIX, LINX, NETNOD and guest IXP NIX.CZ, are happy to host the
European Peering Forum (EPF) 2023 from Sunday the 10th to Wednesday 13th
September 2023 in Prague, Czech Republic.

The event will welcome peering managers and coordinators from networks
connected to the host and guest Internet exchanges.

Besides some interesting topical agenda, the three-day event
accommodates room for attendees to meet on a one-to-one basis to discuss
bilateral peering business opportunities.

The programme committee will be looking for presentations and related to
peering and technical topics of interconnection. Your presentation
should address:

* Interconnection Automation
* Regional Peering
* Interconnection / Peering Internet Governance and Regulatory Topics
* Economic and Product Trends
* Peering / Interconnection strategies
* Interesting findings about Peering / Interconnection
* 400GE and beyond
* Any other hot topic related to Interconnection / Peering


Submissions
===========

Presentations must be of a non-commercial nature. Product or marketing
heavy talks are strongly discouraged.

Submissions of presentations should be made to the programme committee
<epf-pc@peering-forum.eu>. Please include:

* Author's name and e-mail address
* Presentation title
* Abstract
* Slides (if available)
* Time requested (max. 30 minutes incl. Q&A)


Deadlines
=========

Please send in your presentation asap. We decide on a first come first
serve basis. The latest date for submission is July 30th, 2023.

More information about the event and other activities around EPF16 may
be found at

* https://peering-forum.eu/2023/

* https://www.facebook.com/groups/1486607564933665/


On behalf of EPF,

Best regards,

AMS-IX, DE-CIX, LINX and NETNOD
--
Keep calm, keep distance, keep connected!

Arnold Nipper
email: arnold@nipper.de
mobile: +49 172 2650958


-- 
Podcast: https://www.youtube.com/watch?v=bxmoBr4cBKg
Dave Täht CSO, LibreQos

[-- Attachment #2: OpenPGP_signature --]
[-- Type: application/pgp-signature, Size: 209 bytes --]

           reply	other threads:[~2023-08-04 22:41 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <1f0cbf1b-6bd1-7aa0-6c94-3d492d5f288a@nipper.de>]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://lists.bufferbloat.net/postorius/lists/libreqos.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAA93jw7FbKq3TTRsw8HgPGgO7Q9Mspjxu8fUmKo-xm=khTe1wA@mail.gmail.com' \
    --to=dave.taht@gmail.com \
    --cc=frantisek.borsik@gmail.com \
    --cc=libreqos@lists.bufferbloat.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox