Dear APNIC Talk Community,
As chairs of the APNIC Routing Security SIG, we are pleased to invite you to 
submit presentations for the APRICOT 2026 Routing Security SIG session.
We encourage all community members working on routing security topics to share 
their expertise and insights.
Conference Details:

Dates: February 9-11, 2026
Important Note: Please note that APRICOT 2026 will be held earlier than usual

Submission Information:

Submit your presentations at: 
https://2026.apricot.net/programme/callforpresentations
Early submissions encouraged - The sooner you submit, the greater the chance of 
inclusion in the final program agenda

We welcome routing security presentations including:

RPKI deployment experiences and case studies
BGP security implementations (ROV, ASPA, etc.)
Route leak detection and mitigation techniques
New routing security research and standards development
Operational challenges and solutions in routing security
Policy developments affecting routing security
Regional routing security initiatives and coordination

Submission Process: When submitting your presentation at the link above, please:

Select "APRICOT Conference" from the Track dropdown
Select "APNIC Routing Security SIG" from the Session dropdown
Provide a clear abstract highlighting the routing security focus
Include any links to relevant data or case study details

The Routing Security SIG session provides an excellent opportunity to engage 
with network operators, researchers, and security professionals specifically 
focused on securing Internet routing infrastructure across the Asia-Pacific 
region.
For questions about submissions or the conference program, please don't 
hesitate to reach out to the Program Committee.
We look forward to your valuable contributions to the APRICOT 2026 Routing 
Security SIG session!
Best regards,Terry & TaijiAPNIC Routing Security SIG Chairs
_______________________________________________
APNIC-talk - https://mailman.apnic.net/[email protected]/
To unsubscribe send an email to [email protected]

Reply via email to