**Session Date/Time:** 26 Aug 2025 14:00

# [SPRING](../wg/spring.html)

## Summary

This interim meeting focused on the `SRv6 Security Considerations` document, specifically to review recent updates and discuss the path to Working Group Last Call (WGLC). The co-chairs and authors noted the document's progress, including being ahead of schedule on some deliverables. A strong consensus emerged to aggressively push for the start and even completion of WGLC *before* the next IETF meeting. Key discussion points included the scope of the document, the completeness of the management plane security analysis, and the document's relationship to existing SRv6 RFCs, particularly RFC 8402.

## Key Discussion Points

*   **Document Status and Updates:** The authors reported that the `SRv6 Security Considerations` document has undergone incremental updates since the last IETF meeting, including clarifications to OAM details and a PCC update. They believe the document is now well-rounded, with minimal recent comments. Work on the management plane threat model, attacks, and mitigations was completed ahead of schedule.
*   **Target for Working Group Last Call (WGLC):** The authors initially aimed for WGLC readiness by the next IETF meeting. The co-chairs challenged the working group to aim for starting and potentially *finishing* WGLC before the November IETF meeting, with the goal of handing the document to the IESG prior to the meeting.
*   **Review Focus for WGLC:**
    *   Authors plan an internal review.
    *   Working Group members were encouraged to review for overall readability, flow, and to specifically verify that the deliverables addressed in the last 2-3 diffs are correctly incorporated.
    *   Specific attention was requested for the management section and the clarification of control plane and management plane separation.
*   **Section 11 - Topics for Further Consideration:** The authors acknowledged that most items in Section 11 have likely been addressed. A review of this section is planned to remove outdated items and reconsider any remaining ones.
*   **Document Scope - Published RFCs:** It was reiterated that the document's scope covers security considerations for all *published* SRv6 RFCs up to and including the SRv6 Compression RFC (which is now published). The working group agreed to avoid expanding the scope further to ensure timely publication.
*   **Management Plane Attacks:**
    *   The authors believe the current text for management plane attacks is largely complete, as many SRv6 management plane considerations overlap with general routing protocols.
    *   Concern was raised that the current text is very generic and might miss SRv6-specific aspects, such as network programmability via YANG or the ability for intermediate routers to manipulate SID lists.
    *   It was suggested that while normative references to the `ietf-spring-srv6-yang` draft should be avoided here, a high-level statement in this document pointing to the YANG draft for specific details could be beneficial.
*   **Relationship to RFC 8402 and other SRv6 RFCs:**
    *   Many SRv6 RFCs have security considerations that point back to RFC 8402.
    *   Discussion focused on how this document relates to RFC 8402 and other base SRv6 specifications. It was agreed that this document provides *additional* security considerations.
    *   The working group decided against using the "updates" metadata tag, as it could be misleading. Instead, the document text, particularly in Section 2 (Scope), should be enhanced to clearly explain this relationship.

## Decisions and Action Items

*   **Decision:** The working group will target starting and potentially completing the Working Group Last Call (WGLC) for the `SRv6 Security Considerations` document *before* the next IETF meeting in November, aiming to pass it to the IESG beforehand.
*   **Action Item (Authors - Nick, Tal):** Review Section 11 ("Topics for Further Consideration") of the draft, remove items that have already been addressed, and rethink any remaining ones. This is a high priority for the coming weeks.
*   **Action Item (Authors - Nick, Tal):** Enhance the text in the document, particularly in Section 2 (Scope), to clearly articulate its relationship to RFC 8402 and other base SRv6 specifications, emphasizing that it provides *additional* security considerations rather than updating existing ones.
*   **Action Item (Working Group Members):** Review the document for readability, flow, and to ensure that the deliverables from the last 2-3 diffs are accurately incorporated. Provide specific feedback via email to the mailing list, especially concerning the management plane section and control/management plane separation.
*   **Action Item (Safar - Document Shepherd):** Perform a comprehensive shepherd's review of the document and begin preparing the shepherd write-up to facilitate a smooth WGLC process.
*   **Action Item (Authors - Nick, Tal):** Engage in an offline discussion with Duv and Drew to determine the minimal, high-level text to add to the management section regarding SRv6-specific network programmability and its relation to the `ietf-spring-srv6-yang` document, without making normative references.

## Next Steps

*   Authors will integrate feedback from the internal review and the discussion points raised during this interim meeting.
*   Working Group members are encouraged to provide final technical reviews based on the identified focus areas.
*   The document shepherd will proceed with their review and write-up.
*   The co-chairs will prepare to initiate the Working Group Last Call as soon as the document is deemed ready.