Technical Steering Committee (TSC) Public Meeting Agenda & Minutes: May 22, 2026

[tiswanso]

AGNTCY TSC Meeting: May 22, 2026

Public Link: https://zoom-lfx.platform.linuxfoundation.org/meeting/91973330720?password=1974411c-0ab7-4802-a73b-e036edcc4135

TSC Attendees:

• John Parello (Cisco)
• Luca Muscariello (Cisco)
• Anant Patel (Oracle)
• John Cardente (Dell)
• Marcelo Yannuzzi (Cisco)
• Tim Swanson (Cisco OSPO) – moderator

TSC Absentees:

• Michael Clifford (Red Hat)
• Natali Vlatko (Cisco OSPO) – moderator
• Todd Segal (Google)

Public attendees:

• Kevin Cogan (proposed new TSC member)
• Laszlo Gecse (Cisco)
• Sujata Tiberwal (Cisco)
• Carole Reynaud (Cisco)

Proposed Agenda

• Round Table Updates
• Luca:
  • Create open non-TSC members process to join testbed
    • Requirements:
      • Identification of contributor
    • We could use maintainer process
    • Current process is via dir-staging repo PR
      • Self manage credentials of individual dir server
      • If we decline (say no) we should have a closure reason for denial
      • Evaluate every PR as they come in and give a response with decision.
      • Gitops repo (`dir-staging`) maintainer is requirement so we should make a criteria for becoming maintainer level on dir-staging
      • Could use PR template (.github/) as application to join with the required details. Need to avoid anonymous submissions!
      • TSC should be able to review and revoke
        • Must copy TSC on PR
        • TSC can revoke
    • Action: Luca to propose new process and TSC will have distributed vote to accept the process change
• Vote: Allow Akamai into the dir-staging testbed
  • Approved: Unanimous for all attending members
• Proposed New TSC members:
  • Hema Seshadri – Akamai (still waiting on Akamai authorization)
    • Original: Ask for being able to participate in AGNTCY testbed (currently only allowed for TSC)
      • Couple months old PR pending to join testbed
    • Vote: Accepted – unanimous
  • Michael’s replacement – Kevin Cogan, @kevincogan (Red Hat) (email: kcogan@redhat.com)
    • Vote: Accepted – unanimous
• [TimS proposed items]
  • SLIM v1.4.0 released
  • CSIT status & dashboard: https://agntcy.github.io/csit/ (source: Ramiz P)
  • A2A over SLIMRPC multicast spec proposal: docs: add SLIMRPC multicast RPC spec a2aproject/experimental-cpb-slimrpc#2
  • AAIF – LF announced 43 new companies (4 Gold)
    • IETF draft for Agent Name Service (ANS) – Some Cisco AI Defense folks as part of OWASP collaborated with GoDaddy and Infoblox:
    • https://genai.owasp.org/resource/agent-name-service-ans-for-secure-al-agent-discovery-v1-0/
    • https://www.godaddy.com/ans
    • https://aboutus.godaddy.net/newsroom/news-releases/press-release-details/2026/Infoblox-and-GoDaddy-Support-Open-Standards-for-AI-Agent-Discovery-Identity-and-Verification-2026-0acKMntvOC/default.aspx
    • Luca pointed to https://aaif.io/blog/the-missing-layer-in-ai-interoperability-discovery/
      • Roadmap epic for dir integration with AI Catalog: [EPIC]: Enable AI Catalog/AgentFinder specification through DIR dir#1531
  • CFP deadlines approaching (would be good to encourage folks to submit talk ideas!):
    • KubeCon | CloudNativeCon: North America, Nov 9-12, Salt Lake City, UT | May 31
    • AGNTCon + MCPCon NA, Oct 22-23, San Jose, CA | June 7
    • AGNTCon + MCPCon Europe, Sept 17-18, Amsterdam, NE | June 8
• [Laszlo G]
  • APP SDK: there's confusion from potential adopters and concerns about the active maintenance and lagging on latest slim features, etc. This confusion is potentially damaging the project credibility. Could we message better and possibly transition to a clearer and better preferred solution?
    • John P:
      • Need to enumerate the lag
      • Need to enumerate confusion
      • Prior TSC discussions 2/13/26

        • Resolved
          https://github.com/agntcy/app-sdk/blob/main/README.md
          “It is intended as an integration and learning surface primarily used in coffeeAgntcy, not as a canonical or prescriptive SDK for AGNTCY subsystems. Standards and reference guidance remain the responsibility of the working groups. Please see the respective components for their latest SDK or interfaces.”

        • Python only

      • Several companies involved with using already
        • Example Presidio: working sessions, testing and usage discussions,
    • Luca: Dell team working with SLIM had some issues.

      • John P would like to get those enumerated

      • John C: would like to find out who get looped in so he can understand who’s working with AGNTCY efforts, especially if there’s issues

      • Laszlo G: worked with Dell team and wanted to share experience of some issues

    • Clarification:
      • SLIM SDK v. AppSDK compatibility – some folks start with one and get exposure to the other but there’s some questions/issues that come up and the existing team
      • Example:
        • Way to insert A2A
          • Consumes A2A via lang bindings via SLIM SDK through the official A2A SDKs
            • If we have another SDK, that isn’t maintained via A2A/SLIM SDKs then it’s difficult
      • A2A is core component for AGNTCY
        • SLIM is consumed via A2A SDK APIs
    • Ongoing Actions: bring up issues on app-sdk slack
      • Work within the app-sdk & slim working groups to improve getting started docs
  • Directory federation public: there are many companies opening PRs to join our federation. It'd be nice to allow them to have an automated self join process, so we could grow adoption easier.
    • Companies like AnroIT, MeetLoyd, but also MIT showed interest to join the Directory federation: https://github.com/agntcy/dir-staging/pulls
    • Closure: Covered earlier in meeting

[tiswanso]

Received feedback from @lgecse requesting to add 2 items to the agenda:

1. APP SDK: there's confusion from potential adopters and concerns about the active maintenance and lagging on latest slim features, etc. This confusion is potentially damaging the project credibility. Could we message better and possibly transition to a clearer and better preferred solution?
2. Directory federation public: there are many companies opening PRs to join our federation. It'd be nice to allow them to have an automated self join process, so we could grow adoption easier.

[lgecse]

Companies like AnroIT, MeetLoyd, but also MIT showed interest to join the Directory federation: https://github.com/agntcy/dir-staging/pulls