opsawg

Summary

The opsawg meeting at IETF 118 covered several topics, including updates on RFC publications, adopted working group documents, and presentations on drafts related to IPFIX extensions, policy-based network control, data manifests, network packet loss mitigation, incident management, data provenance, and telemetry data storage. The meeting also featured discussion of side meetings and a reminder to provide feedback for the nomcom process.

Key Discussion Points

RFC Status: Several new RFCs have been published, and multiple documents are nearing completion for final publication, including SRv6 and related drafts.
Document Shepherd Role: Announcement of the opportunity to become a document shepherd for adopted working group documents.
IPFIX Extensions: Presentation on IPFIX extension drafts, including TCP and UDP options, with a discussion of out-of-scope considerations like routing options.
Policy-Based Network Control: Update on the YANG data model for policy-based network control and extensions, including a discussion of endpoint group IDs and integration with schedule YANG.
Data Manifest: Presentation and discussion of the data manifest draft, focusing on metadata for telemetry data, and handling of absent values.
Network Packet Loss Mitigation: Discussion of a draft focusing on minimizing network packet loss by automating remediation and identifying root causes. The draft proposes a classification scheme for packet discards.
Incident Management: Presentation on the incident management draft, including use cases and model design, aiming to reduce duplicate troubleshooting tickets.
Data Provenance: Update on the data provenance draft, focusing on ensuring the origin and integrity of YANG data sets using COSE signatures.
Telemetry Data Storage: Discussion of mapping YANG-based telemetry data to time-series databases and challenges related to data scale and database selection.
Side Meetings: Announcement of various ops-related side meetings during IETF 118.
Nomcom Feedback: Reminder to provide feedback for the nomcom process for selecting ops area directors.

Decisions and Action Items

IPFIX Extensions: The working group agreed to leave routing options and destination options out of scope for the IPFIX extension drafts.
IPFIX Extensions: Working group last call was requested for all three IPFIX related documents.
Incident Management: There was interest expressed in adopting the incident management draft.
Side Meetings: Chiu Phang and Chen requested to share the side meeting information on the mailing list.

Next Steps

Send the side meeting information to the mailing list.
Discuss incident management adoption on the mailing list.
Authors of drafts to address feedback received during the meeting.
Continue work on the common schedule, YANG data model.

Session Date/Time: 08 Nov 2023 12:00

opsawg

Summary

The opsawg meeting covered several draft proposals related to sustainability insights, exposure of compute and communication information, digital map modeling, alternate marking information, and automation of OAM tests. Discussions focused on the scope and applicability of the drafts, their relationship to existing work within the IETF and other standards bodies, and potential next steps for development and standardization. A key point was determining the appropriate working group for the sustainability insights work, with a show of hands indicating interest within opsawg.

Key Discussion Points

Sustainability Insights:
- Motivation for focusing on power consumption as a key aspect of sustainability.
- Challenges in obtaining consistent and accurate power consumption data from network equipment.
- Relationship to existing work in IV (Inventory) and the need to coordinate efforts.
- A poll was taken to assess interest in working on this topic within opsawg.
- Concerns about expanding the scope to include full lifecycle carbon footprint analysis.
Exposure of Compute and Communication Information:
- The need for a common set of compute metrics for service deployment and selection.
- The potential overlap with work being done in the Katz working group.
- Different needs for metrics at different layers and applications.
Modeling Digital Map:
- Experiences with implementing a digital map based on RFC 8345.
- Limitations identified when modeling ISIS and OSPF topologies.
- Discussion of potential solutions, including augmentation and changes to existing RFCs.
- Desire for a generic solution applicable to various use cases.
Alternate Marking Information:
- Presentation of a draft defining IPFIX extensions for reporting alternate marking information.
- Discussion of related work on young extensions.
Automation of OAM Tests:
- Proposal for automating OAM tests to assess network health.
- Definitions of OAM unitary tests and test sequences.
- Use cases including troubleshooting, service validation, proactive supervision, and performance-based path routing.
- Suggestion to consider a general scheduler model in YANG for these types of tasks.
Network Topology Modeling:
- Discussed using the topology model as a base for network planning tools.
- Highlighted the use of existing IDF Technologies, and topology models.

Decisions and Action Items

Sustainability Insights: Continue discussion on the mailing list and decide whether to adopt the draft in opsawg or move it to another working group.
Exposure of Compute and Communication Information: Further discussion on the mailing list and a side meeting to gather feedback and determine the best venue for this work. The authors need to decide on the scope.
Modeling Digital Map: Further discussions will be needed on the mailing list.
Alternate Marking Information: The authors will need to promote the work on the mailing list to get more engagement.
All presenters: Promote discussion on the mailing lists.

Next Steps

The authors of all presented drafts should actively engage with the opsawg mailing list to solicit feedback and advance their proposals.
Further evaluation of the existing work is required to determine their applicability and relation to the proposed ideas.
It was also suggested to reach out to the relevant routing area working groups.