Dear GNA-G Community Members,
We’re excited to invite submissions for the 13th Annual International Workshop on Innovating the Network for Data-Intensive Science (INDIS 2026), held with SC26 in Chicago this November.
This year’s theme is:
“Connected Science: Bridging Research and Industry”, reflecting not only the role of networking in connecting scientific infrastructure, but also the collaborations across academia, industry, and government that continue to advance data-intensive science.
INDIS welcomes submissions from the HPC, networking, distributed systems, and data-intensive science communities.
Important Deadlines
*
Student Track (NEW): June 10,2026
*
Regular Paper Track: July 25, 2026
The new Student Track includes 2-page extended abstracts and lightning talk opportunities for students at any level.
Please see the attached CFP and visit the workshop website for submission details, topics of interest, and formatting guidelines:
https://scinet.supercomputing.org/community/indis/indis2026/ [scinet.supercomputing.org]<https://urldefense.com/v3/__https://scinet.supercomputing.org/community/ind…>
We would greatly appreciate you sharing this with colleagues, students, collaborators, and relevant communities.
Hope to see your work at INDIS 2026!
Best,
Kara, Akbar
Advanced Architectures | Global R&D
External Research and R&E Networks
M | +1 214-392-2717 | Dallas, Texas
[Ciena AN Logo]<https://www.ciena.com/?src=emailsig>
Ciena.com<https://www.ciena.com/?src=emailsig> | LinkedIn<https://www.linkedin.com/company/ciena/> | YouTube<http://www.youtube.com/@CienaCorp>
🤝book-a-zoom-meeting<https://scheduler.zoom.us/ak-ccie/huddle>🤝
Hi everyone,
Over the past weeks, we’ve been advancing the GREN Map and preparing a demo for TNC26.
As the map evolves, one question keeps coming up and we’d really value your input: how should we consistently represent the different types of networks and initiatives in our ecosystem?
While working on the current version, we’ve identified some challenges, for example:
- How to distinguish between NRENs, regional backbones, and intercontinental connectivity initiatives;
- How to better represent initiatives/systems/consortiums like AmLight or BELLA without “breaking” the map structure;
- How to reflect the relationships between national, regional, and global infrastructures.
As a starting point, we are exploring a simple classification such as:
- NRENs (e.g., RNP, GARR, etc.);
- Regional/backbone networks (e.g., GÉANT);
- Intercontinental connectivity initiatives (e.g., RedCLARA?);
- Consortia/projects (e.g., BELLA, AmLight).
But this is still work in progress and likely incomplete, that's why we would really appreciate your thoughts:
- Does this classification make sense?
- What are we missing?
- How would you represent initiatives that don’t neatly fit into one category?
To facilitate the progress of this initiative, we are organizing an online meeting on June 3 at 11 a.m. BRT (2 p.m. GMT) to discuss this topic and share our plans for presenting at TNC26.
Meeting link here: https://teams.microsoft.com/meet/229131862133689?p=NzR8eFN1H2zxHgIh1L
If you have quick thoughts, feel free to reply directly to this thread.
Even brief comments would already be very helpful.
Looking forward to your feedback.
Best regards,
--
Lucas Bondan, Ph.D.
R&D Coordinator - RNP<https://www.rnp.br/>
Invited Researcher - UnB<https://unb.br/>
lbondan.wordpress.com<http://lbondan.wordpress.com>
Greetings,
Internet2 and CAIDA have released several ROOTBEER tools to help the
global Research and Education community better understand routing policy
across the R&E ecosystem.
The tools are available here:
https://rootbeer.internet2.edu
One of the tools, the R&E Topology Report, depicts the routing topology
visible from networks that peer with Internet2, AS11537. It is built
from the full set of routes Internet2 receives across its peering
sessions, including routes that are not selected as best paths. This
gives the report a broader view than a conventional forwarding-path or
best-path-only analysis.
The report also includes routes rejected by Internet2’s routing
policy, including routes rejected because they are RPKI Invalid, have an
AS path containing a peer-lock AS, exceed prefix-length limits, or fail
other policy checks.
This pre-policy view is especially useful because it shows not only the
routes Internet2 uses, but also the routes Internet2 sees and rejects.
Below are several examples of insights the report can provide.
We would like to extend this detailed pre-policy view to other R&E
networks.
During TNC26, we will hold the BoF “Coordinating BGP Policy and
Tooling Across the Global R&E Infrastructure” on Thursday,
9:00–10:30 a.m. We will demonstrate progress on the ROOTBEER tools,
invite input on future features, and discuss how data from other R&E
networks could be incorporated to improve coverage and utility across
the community.
After TNC26, we will organize a follow-up meeting to review what we
heard and provide an opportunity for those who could not attend TNC26 to
share their input and discuss ways to expand the reach of these tools.
Later today, I will also be demonstrating two ROOTBEER tools during
ESnet’s CI Engineering Talk:
2pm ET. Steve Wallace from Internet2 will be talking about "Deep dive
into two ROOTBEER tools, the Local Preference Probe and the R&E Global
LPP report". The talks are always recorded. To join live you can use
this link: https://ESnet.zoom.us/j/804696793
Here are some examples of what the RE Topology Report shows, with data
from other networks; this can be expanded.
steve
Here’s a partial graph of how Internet2 received routes to ESnet.
You can see it directly in the tool via:
https://rootbeer.internet2.edu/re-topology-report/#asn=293

You select to see only the best path to see the paths Internet2 is using
by selecting “Best paths only”. Details about each AS and its routes
appear when you click on an AS.
Here’s ESnet with best paths only selected:
https://rootbeer.internet2.edu/re-topology-report/#asn=293&best=1

A few others of interest:
CERN
https://rootbeer.internet2.edu/re-topology-report/#asn=513

SINET
https://rootbeer.internet2.edu/re-topology-report/#asn=2907

Steven Wallace
Director - Routing Integrity
Internet2
ssw(a)internet2.edu