APRICOT 2027 Call for Presentations is open now

The APRICOT 2027 Program Committee (PC) is seeking proposals for presentations and tutorials for APRICOT 2027, taking place in Hong Kong SAR, China, from 24 February to 4 March 2027.

The PC is looking for presenters who can:

• Offer a technical tutorial on an appropriate topic
• Participate in the technical conference sessions as a speaker
• Convene and chair panel sessions on relevant topics
• Lead informal Birds of Feather (BoF) breakout sessions

APRICOT does not permit remote presentations, as the Summit is intended as an in-person networking opportunity for all participants.

Conference milestones

Please note, slots are filled on a first-come, first-served basis, regardless of published deadlines.

Program content

The APRICOT conference program comprises three parts - tutorials, the Peering Forum, and conference sessions. The conference dates for the APRICOT 2027 Summit are Monday, 1 to Wednesday, 3 March 2027 inclusive, and program content will be scheduled on these three days.

Topics proposed must be relevant to Internet operations and technologies:

• IPv4 / IPv6 routing and operations
• Routing security, including RPKI and MANRS
• Internet backbone operations
• Peering, interconnects, and IXPs
• Content Distribution Network (CDN) technology and operations
• Data centre design, operations, and scaling
• Research on Internet operations and deployment, supported by use case or operational deployment
• Network virtualization
• Network automation / programming
• Network infrastructure security
• IPv6 deployment on fixed and wireless / cellular networks
• DNS, DNSSEC, and KINDNS
• Access and transport technologies
• LEO and GEO technologies
• AI: DCI design, operations, scaling
• Content and service delivery and 'cloud computing'
• 400G / 800G / 1.6T ZR, ZR+ and OIF, OpenZR, OpenROADM, and OpenXR
• OpenRAN
• Submarine cables

Peering Forum

Peering Personal submissions must be a single slide listing the operator's PeeringDB entry. Please refer to the APRICOT 2027 Peering Personals page for information on how to create a successful Peering Personal presentation.

Call for Presentations (CfP) submission

Draft slides for both tutorials and conference sessions MUST be provided with CfP submissions in presentation format; otherwise, the submission will be rejected immediately. For work in progress, the most current information available at the time of submission is acceptable.

All draft and complete slides must be submitted in PDF format only. Slides must be the author's original work, with all company confidential marks removed.

Any product, marketing, sales, and vendor proprietary content in a presentation is against the spirit of APRICOT and is strictly prohibited.

Note that proper credit must be given for all content taken from other sources. Evidence of plagiarism is grounds for rejection. Presentations must be the author's original work; content generated by machine learning algorithms is not permitted, or, if required to demonstrate a point, must clearly state so.

Final slides are to be provided by the specified deadline for publication on the APRICOT 2027 website.

Prospective presenters should note that most speaking slots will be filled well before the final submission deadline. The PC may, at their discretion, retain a limited number of slots up to the final submission deadline for presentations that are exceptionally timely, important, or of critical operational importance. Every year we turn away submissions because all available program slots are filled before the deadline. Presenters should try to get material into the PC chairs sooner rather than later.

Any questions or concerns should be addressed to the PC by email. Full details, including the Call for Presentations FAQ, are on the APRICOT 2027 Call for Presentations page.

We look forward to receiving your presentation proposals.

Mark Duffell is a member of the APRICOT 2027 PC and of the APNOG Board.

The views expressed by the authors of this blog are their own and do not necessarily reflect the views of APNIC. Please note a Code of Conduct applies to this blog.