ietf-wg-dmarc / draft-ietf-dmarc-dmarcbis

7 stars 4 forks source link

DMARCbis WGLC Issue - Clean Up rua and ruf tag descriptions #124

Closed toddherr closed 8 months ago

toddherr commented 8 months ago

Current text from 5.3, General Record Format, reads:

`rua: : Addresses to which aggregate feedback is to be sent (comma-separated plain-text list of DMARC URIs; OPTIONAL). [@!I-D.ietf-dmarc-aggregate-reporting] discusses considerations that apply when the domain name of a URI differs from that of the domain advertising the policy. See (#external-report-addresses) for additional considerations. Any valid URI can be specified. A Mail Receiver MUST implement support for a "mailto:" URI, i.e., the ability to send a DMARC report via electronic mail. If the tag is not provided, Mail Receivers MUST NOT generate aggregate feedback reports for the domain. URIs not supported by Mail Receivers MUST be ignored. The aggregate feedback report format is described in [@!I-D.ietf-dmarc-aggregate-reporting].

ruf: : Addresses to which message-specific failure information is to be reported (comma-separated plain-text list of DMARC URIs; OPTIONAL). If present, the Domain Owner is requesting Mail Receivers to send detailed failure reports about messages that fail the DMARC evaluation in specific ways (see the "fo" tag above). [@!I-D.ietf-dmarc-aggregate-reporting] discusses considerations that apply when the domain name of a URI differs from that of the domain advertising the policy. A Mail Receiver MUST implement support for a "mailto:" URI, i.e., the ability to send a DMARC report via electronic mail. If the tag is not provided, Mail Receivers MUST NOT generate failure reports for the domain. See (#external-report-addresses) for additional considerations.`

These should be cleaned up a bit to be more consistent. Proposed text to follow in a subsequent comment.

toddherr commented 8 months ago

The following text was proposed on-list on March 1:

PROPOSED REPLACEMENT TEXT: ========================= cut here ========================== rua: : Addresses to which aggregate feedback reports are to be sent (comma-separated plain-text list of DMARC URIs; OPTIONAL). If present, the Domain Owner is requesting Mail Receivers to send aggregate feedback reports about results of authentication checks performed on mail using the domain for which the DMARC policy record is published. [@!I-D.ietf-dmarc-aggregate-reporting] discusses considerations that apply when the domain name of a URI differs from that of the domain advertising the policy. See (#external-report-addresses) for additional considerations. Any valid URI can be specified. A Mail Receiver MUST implement support for a "mailto:" URI, i.e., the ability to send a DMARC report via electronic mail. If the tag is not provided, Mail Receivers MUST NOT generate aggregate feedback reports for the domain. URIs not supported by Mail Receivers MUST be ignored. The aggregate feedback report format is described in [@!I-D.ietf-dmarc-aggregate-reporting].

ruf: : Addresses to which message-specific failure information is to be reported (comma-separated plain-text list of DMARC URIs; OPTIONAL). If present, the Domain Owner is requesting Mail Receivers to send detailed failure reports about messages that fail the DMARC evaluation in specific ways (see the "fo" tag above). [@!I-D.ietf-dmarc-aggregate-reporting] discusses considerations that apply when the domain name of a URI differs from that of the domain advertising the policy. See (#external-report-addresses) for additional considerations. A Mail Receiver MUST implement support for a "mailto:" URI, i.e., the ability to send a DMARC report via electronic mail. If the tag is not provided, Mail Receivers MUST NOT generate failure reports for the domain. URIs not supported by Mail Receivers MUST be ignored. The format for message-specific failure reporting is described in [@!I-D.ietf-dmarc-failure-reporting]. ========================= cut here ==========================

toddherr commented 8 months ago

More cleanup of text in committed branch (rev-31):

rua: Addresses to which aggregate feedback reports are to be sent (comma-separated plain-text list of DMARC URIs; OPTIONAL). If present, the Domain Owner is requesting Mail Receivers to send aggregate feedback reports about results of authentication checks performed on mail using the domain for which the DMARC policy record is published. [I-D.ietf-dmarc-aggregate-reporting] discusses considerations that apply when the domain name of a URI differs from that of the domain advertising the policy. See Section 11.6 for additional considerations. Any valid URI can be specified. A Mail Receiver MUST implement support for a "mailto:" URI, i.e., the ability to send a DMARC report via electronic mail. If the tag is not provided, Mail Receivers MUST NOT generate aggregate feedback reports for the domain. URIs not supported by Mail Receivers MUST be ignored. The aggregate feedback report format is described in [I-D.ietf-dmarc-aggregate-reporting].

ruf: Addresses to which message-specific failure information is to be reported (comma-separated plain-text list of DMARC URIs; OPTIONAL). If present, the Domain Owner is requesting Mail Receivers to send detailed failure reports about messages that fail the DMARC evaluation in specific ways (see the "fo" tag above). [I-D.ietf-dmarc-aggregate-reporting] discusses considerations that apply when the domain name of a URI differs from that of the domain advertising the policy. See Section 11.6 for additional considerations. Any valid URI can be specified. A Mail Receiver MUST implement support for a "mailto:" URI, i.e., the ability to send message-specific failure information via electronic mail. If the tag is not provided, Mail Receivers MUST NOT generate failure reports for the domain. URIs not supported by Mail Receivers MUST be ignored. The format for message-specific failure reporting is described in [I-D.ietf-dmarc-failure-reporting].

toddherr commented 8 months ago

Text has been updated and checked in to working branch.