Document: draft-ietf-spring-cs-sr-policy Title: Circuit Style Segment Routing Policy Reviewer: Luigi Iannone Review result: Clarification Needed
Hi, I have been selected as the Operational Directorate (opsdir) reviewer for this Internet-Draft. The Operational Directorate reviews all operational and management-related Internet-Drafts to ensure alignment with operational best practices and that adequate operational considerations are covered. A complete set of _"Guidelines for Considering Operations and Management in IETF Specifications"_ can be found at https://datatracker.ietf.org/doc/draft-opsarea-rfc5706bis/. While these comments are primarily for the Operations and Management Area Directors (Ops ADs), the authors should consider them alongside other feedback received. - Document: draft-ietf-spring-cs-sr-policy-13 - Reviewer: Luigi Iannone - Review Date: 08 January 2025 - Intended Status: Informational --- ## Summary Choose one: - Has Issues: I have some minor concerns about this document that I think should be resolved before publication. ## General Operational Comments Alignment with RFC 5706bis Provide an overview of the draft’s operational feasibility, readability, and alignment with RFC5706bis guidelines. Example: This document describes how to use Segment Routing policies to create a circuit-style policy, meaning two co-routed unidirectional SR policies that satisfy requirement like bandwidth, delay, etc. The document is informational as it does not introduce any new mechanism, but rather describe how to use existing (or proposed) mechanisms to create the circuit-style policy. As such the whole document can be considered an operational guideline. The document explicitly discuss operational issues like Fault Management, Configuration Management, and Performance Monitoring, verification of correct operation. ## Major Issues - No major issues found. --- ## Minor Issues The security section should be improved. Listing the security sections of the underlying technology is not enough. The specific usage may change the impact of certain security risks, even amplifying some consequences. A more extensive discussion should be added. While the document covers basic operations, manageability would enjoy more discussion from a viewpoint that goes beyond a single circuit-style policy, but rather from a large network operator perspective having to manage many such policies. --- _______________________________________________ spring mailing list -- [email protected] To unsubscribe send an email to [email protected]
