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-ietf-opsawg-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-anima-brski-discovery-13

- Reviewer: Xiao Min

- Review Date: Jul 17, 2026

- Intended Status: Standards Track

---

## Summary 

I have some minor concerns about this document that I think should be resolved before publication.

## General Operational Comments Alignment with RFC 5706bis 

I think this document needs a standalone Operational Considerations section as required by rfc5706bis, although some kinds of operation 
and management considerations have been mentioned in a few sections, e.g., Section 3.5.1.1 discusses operational aspects on DNS and 
DNS-SD libraries and Section 3.5.1.3 provides management guidance on how to create and construct a service instance name.

## Major Issues 

None. 

---

## Minor Issues 

This document specifies three BRSKI discovery mechanisms including DNS-SD, GRASP, and CORE-LF. I didn't dive into details of the three 
mechanisms, however from an operational perspective I believe at least the following questions should be answered by this document.

* Do the three mechanisms have a priority order for different scenarios?

* If a system supports two or three of the mechanisms, is there a default one?

* Do we need a negotiation mechanism to select an effective discovery mechanism?

---

## Nits 

Abstract, it should say this document updates draft-ietf-anima-brski-prm, rfc6690, and rfc9733.

Sections 1 and 2, suggest to switch Section 1 and Section 2 to make Introduction first.

Section 3.1, if convenient suggest to modify the section title, because "Data Model" made me try to find a YANG Model.

Section 3.1.9, if possible please put all IANA registry relevant contents into IANA considerations section.

---