Opened 8 years ago

Closed 14 months ago

#6 closed defect (fixed)

Fuzzy normative language around filenames

Reported by: superuser@… Owned by: alex_brotman@…
Priority: major Milestone: Deliverable #3 (changes to DMARC base spec + DMARC Usage Guide
Component: dmarc-aggregate-reporting Version:
Severity: - Keywords:
Cc:

Description

Message-ID: <54AB056C.2090101@…>
Date: Mon, 05 Jan 2015 13:43:08 -0800
From: Jim Fenton <fenton@…>
To: "dmarc@…" <dmarc@…>
Subject: [dmarc-ietf] Comments on dmarc-base-09

[...]
Section 6.2.1.1, "The filename is typically constructed..." Again, this
is fuzzy normative language; it sounds like it's trying to say, "The
filename MAY be constructed..."
[...]

Change History (6)

comment:1 Changed 5 years ago by kboth+ietf@…

  • Component set to dmarc-future-notes

comment:2 Changed 19 months ago by todd.herr@…

  • Component changed from dmarc-future-notes to dmarc-aggregate-reporting

Issue references Section 6.2.1.1 from dmarc-base-09; language in question actually appears in Section 7.2.1.1 in RFC 7489.

comment:3 Changed 19 months ago by alex_brotman@…

  • Owner set to alex_brotman@…
  • Status changed from new to assigned

comment:5 Changed 17 months ago by mail@…

Nit:
move unique-id down the list and place it between end-timestamp and extension.

comment:6 Changed 14 months ago by alex_brotman@…

  • Resolution set to fixed
  • Status changed from assigned to closed

Changed to MUST

Note: See TracTickets for help on using tickets.