Summary

  • Internet2 says a June TNC26 demonstration connected a SURF agent to named Internet2 diagnostic skills for an Atlantic circuit; the exchange took about five minutes.
  • The operating question is access: each network can expose a short list of diagnostics without opening its whole tool stack.

The network had crossed an ocean. The diagnosis crossed an organizational boundary. In Internet2’s account, that second crossing took about five minutes—and the engineers still thought it felt slow.

At TNC26 in June, Internet2 and SURF stood up a transatlantic circuit. SURF’s system asked about it. When it needed information from the Internet2 side, it called Internet2’s troubleshooting agent. The exchange took about five minutes, according to Internet2’s 14 October report. That is the sort of delay that sounds comically long in a conference demo and impressively short beside a chain of tickets moving between teams on different continents.

The interesting part is the door. Internet2 says its agent exposed named skills such as interface status, interface statistics and circuit status to another organization’s agent, without exposing the rest of its stack. This is a design choice with operational consequences: the receiving network can ask a precise question, while the network that owns the equipment chooses which answers leave its boundary.

The five-minute handoff

Internet2 calls its troubleshooting system HAWAT, short for Heuristic Analysis With Adaptive Troubleshooting. Its 14 October account says HAWAT is live against the Internet2 production network and available for its engineers to test. Inside Internet2, purpose-built agents reach systems including a distributed looking glass, a configuration database, time-series telemetry and circuit provisioning through MCP servers. The tools are read-only by default, the organization says.

Inside HAWAT, MCP servers reach Internet2’s own operational systems. Across the SURF boundary, the proof of concept opened a narrower door: a few named diagnostic actions for a trusted remote agent, while the rest of Internet2’s stack stayed inside its boundary.

That matters because a slow path rarely respects organizational charts. A researcher’s transfer can cross a campus, a regional network, a national backbone and an overseas partner. Each team sees a slice. A ticket handoff asks a human to translate the same circuit, interface and time window yet again. A bounded agent interface can carry the question to the next network while leaving the answer under that network’s control.

A demo with a real boundary

Internet2 reports five minutes for one June demonstration. Its October roadmap puts more work ahead: hardening the MCP server suite, moving an early troubleshooting assistant toward full production use, then adding ticket intake, model evaluation, authentication and observability.

Internet2’s midyear update places the experiment inside its Trusted Infrastructure Program and describes a broader federated Periscope direction. Regional networks could run their own instances and connect them so diagnostic visibility follows traffic across domains. The page also says a Periscope pilot was under way, with Utah Education and Telehealth Network and OSHEAN running early looking-glass functions. That pilot and the June cross-agent demo occupy separate stages in Internet2’s timeline.

The practical breakthrough is therefore modest and useful. One network can publish a few carefully chosen questions another network may ask. The next challenge is deciding who the asking agent is, how long its permission lasts, what the answer records, and who owns the incident when two operators are looking at the same circuit. Those are the details that turn a clever five-minute exchange into an operating habit.

Sources