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-dmarc-failure-reporting

**Reviewer**: Tim Wicinski

**Review Date**: 2025-11-28

**Intended Status**: Standards Track

 
---

## **Summary** 


This document describes "failure reports," which provide details about individual messages that 
failed to authenticate according to the DMARC mechanism.

The document is ready with some minor nits. 

The IDNits that Marco Tiloca raised in the ARTART review need to  be addressed:
https://datatracker.ietf.org/doc/review-ietf-dmarc-failure-reporting-20-artart-lc-tiloca-2025-11-26/


The document describes the operational mechanisms, however, in order to deploy the failure reports requires reading of draft-ietf-dmarc-dmarcbis, but both portions are well written. 


---

## **Minor Issues** 

## Terminology

The Terminology section references DMARC-bis document, which is useful.  But there are a number of definitions in "Reporting Format Update" section that mentions looking in RFC6591.  I would suggest you also add this reference to the Terminology Section.

 
---

## **Nits** 

Optional editorial suggestions (e.g., acronym expansions or grammar fixes). 

- **Example**: 

 > *Abstract*: Expand "NFV" on first use. 

 > Section 3.1: "it’s" -> "its".* 

Wording Nit:

### Introduction

s/can use to/can be used/

### IANA Considerations

s/""Messaging Abuse Reporting Format"/"Messaging Abuse Reporting Format"/