Technical Steering Committee (TSC) Public Meeting Agenda & Minutes: Feb 27, 2026

[tiswanso]

AGNTCY TSC Meeting: Feb 27, 2026

Attendees:

• John Cardente (Dell)
• John Parello (Cisco)
• Marcelo Yannuzzi (Cisco)
• Luca Muscariello (Cisco) - absent
  • represented by: Laszlo Gecse (Cisco)
• Michael Clifford (Red Hat) - absent
• Todd Segal (Google) - absent
  • represented by: Junjie Bu (Google)
• Egor Pushkin (Oracle) - absent
• Tim Swanson (Cisco OSPO) – moderator
• Natali Vlatko (Cisco OSPO) – moderator

Public attendees:

• Mauro Sardara (Cisco)
• Michele Papalini (Cisco)
• Carole Reynaud (Cisco)

see AGNTCY calendar to join

Proposed Agenda

NOTES added inline per meeting discussions

• Public Meeting Intro
• Project / Component Updates
  • Dir v1.0 released; blog
  • Dir federation:
    • Ongoing – meeting with interested parties (Dell) on Thurs
    • Blog started
  • AGNTCY member access to Public Dir instance
    • Existing dir records: Imported MCP servers into it; custom agent records;
      • Looking to review list and groom
        • There are already verified quality MCP servers in there
        • Webex team needs more in the directory
      • coffeeAgntcy looking to add capabilities for policy type functionalities: accessing signed/unsigned
  • SLIM:
    • v1.2 being prep’d – .NET, kotlin lang bindings; slimctl updates (go => rust)
    • Planning v1.3
      • Due to desire for public SLIM rendezvous point (server)
        • Gaps need to be addressed to enable
        • Target in March
        • Support federation (accessible/open)
        • coffeeAgntcy team: would like to be ready to enable examples
    • Exploring creation A2A extension – officially pending A2A community voting
      • Multi-party comm
  • Identity
    • Going as expected
    • Auth0 & Okta presented – generated active discussions & items to focus on for actionable work
    • Cisco IETF reps sync – agntcy team submitted draft & making it into working-group discussions
      • Multiple topics above what made it into MCP draft
• Update and Discuss: adoption scarf for project adoption metrics (SDK usage specifically)
  • https://github.com/orgs/agntcy/discussions/64
  • https://docs.scarf.sh/package-analytics/
  • Suggestion:
    • Adopt for 1 component/WG first
      • E.g. coffeeAgntcy/app-sdk
      • Action:
        • TimS setup project with scarf; work with coffeeAgntcy team to activate
• Learning labs available from https://courses.outshift.com/
  • AI Lab UX = instances setup with temporary LLM service access
  • Do we want to promote this
  • NOTEs:
    • Continue fleshing out work with LLM access
    • Wait for non-Cisco TSC attendees to be able to chime in
• AGNTCY core WG members participating in Agent-Card/ai-card definition. Objective is to get rough consensus on AI card
  • spec: post-meeting converged AI Card profile proposal Agent-Card/ai-card#18
  • NOTEs
    • Ongoing discussions
    • Common layer for identity & trust
    • General alignment is good & effort breaking into smaller PRs
    • Focusing on more than agents that support 1 specific protocol ; agent multi-protocol support
    • Key ask
      • repo and issues are public so if interested now is a good time to participate!
• AGNTCY Calendar Ops: Confirm AGNTCY maintainers/WG-leads should move to using zoom-lfx for AGNTCY meeting calendar: https://zoom-lfx.platform.linuxfoundation.org/meetings/agntcy?view=week
  • Core WG already using – zoom went very well
    • Question: host role delegation? (PTOs)
      • Do we need to have delegated members be PCC meeting coordinators?
      • Action: Tim Swanson to investigate
  • Other WGs?
    • John P. – opinion is to be unified so moving to zoom is fine
      • Also Google docs is not great due to restrictions; use git
      • Need multiple hosts
  • Action:
    • Tim / Natali work with WG leads to get into PCC

Q/A From attendees

• Proposed discussion topic for Q/A from attendees section: discuss AGNTCY blog agntcy/blogs#51 (comment)
  • NOTEs:
    • Technical blog v. social media – there’s desire for creating blogs entries for content that isn’t pure agntcy content. Social media doesn’t cut it for the content type. What is the delineation on AGNTCY blog content?
      • Comments:
        • Pure open source type integration content
          • Maybe we create separate space
            • Integration / Adoption oriented
        • Action:
          • Proposal for organizing – blogs.agntcy
          • Proposal Organizing - youtube
        • Other example shared: https://developer.webex.com/blog/webex-leverages-agntcy-directory-and-identity-for-agentic-apps
    • Same issues for Videos as well
      • Youtube content should be organized similarly
        • Tags or channels methods should be clarified & approved

[lttucker23]

Proposed discussion topic for Q/A from attendees section: discuss AGNTCY blog agntcy/blogs#51 (comment)

[tiswanso]

AGNTCY Calendar Ops

Confirm AGNTCY maintainers/WG-leads should move to using zoom-lfx for AGNTCY meeting calendar: https://zoom-lfx.platform.linuxfoundation.org/meetings/agntcy?view=week

Action

• Need working group leads' linuxfoundation.org user IDs (email) to get PCC (project command center) permissions to create meetings

[tiswanso]

We discussed this in TSC and the sentiment is to work to move WGs' meetings to zoom-LF. I'll reach out to WGs to get "meeting organizer" LF IDs to add.

Note adding users is not totally self service for the linuxfoundation project control center so one of us admins will be sending requests to our LF support team.

[91pavan]

Hi @tiswanso, sorry for the late reply. Here's my LF ID: pavansudheendra91

[tiswanso]

Good meeting to those who attended! Apologies if I missed any public attendees in the list!