-
Notifications
You must be signed in to change notification settings - Fork 46
Meeting Minutes: March 29, 2018
Mukesh Hira edited this page Apr 1, 2018
·
3 revisions
10 am to 11:30 am PDT (GMT - 7), Barefoot Networks, 4750 Patrick Henry Dr, Santa Clara, CA 95054
AT&T: Shyam Parekh
Barefoot Networks: Arkadiy Shapiro, Jeongkeun Lee, Mickey Spiegel, Xiaozhou Li
Cisco Systems: Mario Baldi
Dell : Anoop Ghanwani
IXIA: Chris Sommers
Marvell: Tal Mizrahi
Netcope: Petr Kastovsky
VMware - Mukesh Hira
- Using an IPv4 option to indicate presence of INT metadata will be addressed after version 1.0
- Opaque reports / Extension reports will be handled after version 1.0
Following changes were reviewed and approved for inclusion in version 1.0:
- Mickey Spiegel proposed removal of details, examples of destination type reports and piggybacked metadata as this was not defined clearly in the specification. The proposal was to consider these in a later version and define these clearly based on use cases. The data plane specification continues to define two types of INT headers, hop-by-hop headers and destination type headers. But details of destination type headers have been left to a later version.
- JK Lee proposed removal of congestion status metadata as it was considered somewhat redundant, given that queue occupancy metadata reports similar information. Congestion state was deemed to be not useful in real-world use cases.
- Mukesh Hira proposed editorial changes with clarifications, clearer definitions in some parts of the specification.
Xiaozhou Li presented a novel application of programmable data planes: Netcache, a high performance in-network key-value cache. Presentation slides can be found here
- Above changes to the data plane specification will be merged and version 1.0 candidates of INT data plane and report format specification will be announced on the mailing list over the next few days.
- The next working group meeting has been pushed out by a week to April 19, 2018. We shall resume the bi-weekly cadence from April 19. Location and detailed agenda will be announced on the mailing list closer to the meeting date.