Opened 2 years ago

Closed 2 years ago

Last modified 2 years ago

#49 closed defect (fixed)

p= placement requirement should be removed

Reported by: seth@… Owned by:
Priority: major Milestone: Deliverable #3 (changes to DMARC base spec + DMARC Usage Guide
Component: dmarc-bis Version:
Severity: - Keywords: nit tag-update
Cc:

Description

Normatively, p= must be the second tag (after v=) or the record is invalid; no one enforces this in the real world and it doesn't matter. This normative requirement should be stricken.

Change History (5)

comment:1 Changed 2 years ago by seth@…

  • Component changed from rfc7601bis to dmarc-bis
  • Owner draft-ietf-dmarc-rfc7601bis@… deleted
  • Status changed from new to assigned

comment:3 Changed 2 years ago by seth@…

The consensus of the working group is to remove this normative constraint.

There were no objections to this, but some people wanted to go further. Those tangents gained no momentum beyond the original authors.

comment:4 Changed 2 years ago by seth@…

  • Resolution set to fixed
  • Status changed from assigned to closed
Note: See TracTickets for help on using tickets.