It seems like the only true outstanding issue is the thread from the PRs from 
Ale.  They’re minor points I believe.  I would think we’re safe to schedule it?

--
Alex Brotman
Sr. Engineer, Anti-Abuse & Messaging Policy
Comcast

From: Murray S. Kucherawy <[email protected]>
Sent: Thursday, January 16, 2025 10:18 AM
To: [email protected]
Subject: [dmarc-ietf] Re: I-D Action: 
draft-ietf-dmarc-aggregate-reporting-25.txt

Hi,

On Sun, Jan 12, 2025 at 6:19 PM 
<[email protected]<mailto:[email protected]>> wrote:
Internet-Draft draft-ietf-dmarc-aggregate-reporting-25.txt is now available.
It is a work item of the Domain-based Message Authentication, Reporting &
Conformance (DMARC) WG of the IETF.

   Title:   Domain-based Message Authentication, Reporting, and Conformance 
(DMARC) Aggregate Reporting
   Author:  Alex Brotman
   Name:    draft-ietf-dmarc-aggregate-reporting-25.txt
   Pages:   36
   Dates:   2025-01-12

Abstract:

   Domain-based Message Authentication, Reporting, and Conformance
   (DMARC) allows for Domain Owners to request aggregate reports from
   receivers.  This report is an XML document, and contains extensible
   elements that allow for other types of data to be specified later.
   The aggregate reports can be submitted to the Domain Owner's
   specified destination as supported by the receiver.

Please make a decision ASAP regarding whether you want this one to go to the 
IESG now or you want to keep debating it.  This document is 36 pages, and the 
current pre-122 telechat story is:

January 23: 9 pages left, so it won't fit here
February 6: over-full by 5 pages (but dmarcbis is here)
February 20: 267 pages left
March 6: currently empty

... and we just heard that there are multiple other large documents now 
competing for the space remaining.  Outgoing ADs' documents have priority, but 
I wouldn't rely on that forever.  We need to get this scheduled.

-MSK
_______________________________________________
dmarc mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to