Hello DASH Open Source Community – happy to see all of you in the New Year!
In summary, last session we:
For brevity’s sake this week, I’ll only list the Completed
items in our table further below (as our work items list is quite large).
I’m still looking to leverage the Linux Foundation lists more to manage communications. If you could please take the time to enter your info here, I can initiate deletion of the sonic-dash@googlegroups list we used when we began the project.
For Complete Details, please see the “Full DASH Community Notes” near the end of this communication.
In Summary (full list below), since the last Community call we have:
32 PRs Completed (+20)
11 in To Do (+/- 0 )
6 in Draft (- 3)
41 in Progress (-2)
13 Awaiting Review (-2)

Just a reminder that we would encourage/invite Community members to present to the Community (test runs or progress, new scenarios, etc…), just ‘r’ to let me know, or generate a PR in the repo.
The DASH
channel
link is here to
subscribe / access WG content (and click the bell to receive notifications).
Thank you for your time/contributions – see you on 1/14/2026
Meeting Title: SONiC-DASH-Workgroup Community Meeting #167
Attendees (17):
DASH Group to join: https://groups.google.com/g/sonic-dash
Linux Foundation list: https://lists.sonicfoundation.dev/g/SONiC-Dash
|
Abdul Rouff - Nvidia |
Gagan Punathil Ellath - Nvidia |
murali Venkateshaiah (muraliv) - Cisco |
Selvarajan, Arunachalam - AMD |
|
Bud Grise - XSightLabs |
Kristina Moore - MSFT |
Prince Sunny - MSFT |
Swaminathan Balasubramanian - Keysight |
|
Deven Jagasia - MSFT |
Michael Aronovici (aronovic) - Cisco |
Ramesh Raghupathy (ram) - Cisco |
Ted Weatherford - XSightLabs |
|
Don Ewald - Cisco |
Mircea Dan Gheorghe - Keysight |
Sasha (Oleksandr) Ivantsiv - Nvidia |
Vasundhara Volam - MSFT |
|
Veerappan, Senthilnathan - AMD |


Full DASH Community Notes 😊
· Review of Recent PRs and Work Items: led a review of the recent pull requests and work items completed over the past few weeks, highlighting contributions from Vasundhara and others, and mentioning ongoing queue management and platform-related improvements.
· Completed PRs Overview: summarized the completion of several pull requests over the last 15 days, including platform-related improvements such as graceful shutdown and startup, and test enhancements to handle HA service conditions.
· Platform and Test Enhancements: Vasundhara was acknowledged for closing platform-related items, specifically around graceful shutdown and startup
· Ongoing Queue Management: even without weekly meetings, the team has maintained steady progress on work items and queue management, ensuring continued development momentum.
· Unified Chassis DB Address Initiative: Vasundhara provided context on the initiative to unify the chassis DB address across platforms, with input from Sasha, Prince, and Gagan, explaining the move towards a vendor-agnostic approach and technical considerations for implementation.
· Vendor-Agnostic Chassis DB Address: Vasundhara explained that the initiative, prompted by Guohan and implemented by Judy, aims to make the chassis DB address independent of vendor specifics, supporting both chassis and smart switch platforms.
· Technical Implementation Details: The team discussed that the new chassis DB address will be provided through a configuration file, potentially outside of the main config DB, to avoid startup dependency issues, as highlighted by Sasha and Prince.
· Platform-Specific Handling: Vasundhara clarified that while the smart switch will retain the same address, the chassis will use a different one, and the solution is being verified across platforms.
· Community Review and Next Steps: Prince and Sasha raised questions about configuration and startup order, with consensus that the address should be available on the file system, and Vasundhara confirmed ongoing verification and parameterization for customer use.
· Telemetry Counter Standardization and Sai Integration: discussed the ongoing effort to standardize telemetry counters, review SAI integration, and coordinate next steps for community validation and implementation, with action items for further review and prioritization.
· Counter Proposal Review: confirmed that the AMD team and Arun had reviewed and finalized the table, with Kristina noting ongoing internal meetings to address additional entries.
· SAI Attribute Gaps and Ownership: debated who should take ownership of defining and requesting the missing pieces.
· Next Steps and Prioritization: The group agreed on the need for Michal's sign-off, further review by NVIDIA and AMD.
· Community Feedback and Implementation Plan: Kristina and Prince outlined the process for community feedback, mapping out missing counters, and planning for a two-week review period before finalizing the SAI definitions, with further input expected from Marian and Oleksandr.
· NAT64 and IPv6 Feature Follow-Ups: Kristina mentioned upcoming follow-ups with Michal regarding NAT64 and IPv6 features, indicating that further discussions and deep-dives are planned for later in January.
· Dream Big Semiconductor PR Status: Kristina noted the need to check with Prince on the merge status of a PR by Dream Big Semiconductor, reflecting ongoing coordination on contributions.
· Connection Tracking State Handling Questions: Kristina referenced questions from Farhan in the chat regarding connection tracking state handling in the data plane app, noting resource constraints and the availability of the discussion in the chat window.
Follow-up tasks:
· NAT 6 to 4 and V6 Feature Coordination: Ping Michael later in January regarding the features around NAT 6 to 4 and V6. (Kristina)
· Dream Big Semiconductor PR Status: Check with Prince to confirm if the Dream Big Semiconductor PR was merged. (Kristina)
· Unified Chassis DB Address Implementation: Continue verifying the vendor-agnostic chassis DB address implementation across platforms and update on progress. (Vasundhara)
· Counter Proposal Review and Updates: Meet with Abdul and other internal teams to review and potentially add extra counter entries, and update the counter proposal accordingly. (Kristina, Abdul)
· Counter Proposal Feedback Collection: Collect feedback from Marian and Oleksandr on the counter proposal this week
|
Sticky for Links/Reference: |
|
|
|
DASH Groups to join to receive Invites, Meeting Notes, and Comms |
DASH: https://groups.google.com/g/sonic-dash DASH-Test-Workgroup Group: https://groups.google.com/g/sonic-dash-test-workgroup Linux Foundation list: https://lists.sonicfoundation.dev/g/SONiC-Dash |
If anyone knows potentially interested people who would like info re: our community, please have them joins these groups for receive Comms, etc… |
|
Recordings |
Teams: DASH Community
|
1/7/2026 DASH Community Call; please request access via the link if you are not able to view/listen |
|
Azure DASH GitHub Repo: |
|
|
|
|
https://github.com/sonic-net/DASH/blob/main/test/docs/dash-test-workflow-saithrift.md |
Ideal test workflow is here, converted to .md |
|
SAI Thrift |
Client server needed for testing |
|
|
P4 |
https://opennetworking.org/p4/ and https://p4.org/working-groups/ |
Open source, domain-specific programming language for network devices, specifying packet processing for data plane devices (switches, routers, NICs, filters, etc.) |
|
PINS |
|
|
|
PNA consortium spec |
An architecture describing the structure and common capabilities of network interface controller (NIC) devices which process packets transiting one or more interfaces and a host system. |
|
|
IPDK |
IPDK is an open source, vendor agnostic framework of drivers and APIs for infrastructure offload and management which runs on a CPU, IPU, DPU or switch. IPDK runs in Linux and uses a set of well-established tools such as DPDK and P4 to enable network virtualization. |
|
|
bmv2 |
The second version of the reference P4 software switch, nicknamed bmv2 (for behavioral model version 2). The software switch is written in C++11. It takes as input a JSON file generated from your P4 program by a P4 compiler and interprets it to implement the packet-processing behavior specified by that P4 program |
|
|
DPDK |
DPDK is the Data Plane Development Kit which consists of libraries to accelerate packet processing workloads running on a wide variety of CPU architectures. |
|
|
Linux Foundation SmartSwitch |
https://lists.sonicfoundation.dev/g/sonic-smartswitch/calendar |
|
Thank you again for your participation…
Kristina Moore MBA,
M.S., CISSP - Azure Core Principal PM / DASH & SmartSwitch
Office: 425-722-7720 Mobile: 425-876-2040 Email: kri...@microsoft.com
DASH Group to join:
https://groups.google.com/g/sonic-dash
Linux Foundation: https://lists.sonicfoundation.dev/g/SONiC-Dash
![]()
![]()
![]()
![]()
![]()
![]()