9. IANA Considerations
Diese Seite fasst den entsprechenden Abschnitt von RFC 9989 zusammen und bewahrt DMARC-Tags, DNS-Namen, ABNF und IANA-Werte.
The IANA updates from Section 9 are preserved below, including method/property entries for dmarc, result codes fail, none, pass, permerror, and temperror, active and historic DMARC tags, afrf, and _dmarc TXT.
9. IANA Considerations
This section describes actions completed by IANA.
9.1. Email Authentication Methods Registry Update
The properties of an email message to be evaluated by an email
authentication method have been registered by IANA in the "Email
Authentication Methods" registry within the "Email Authentication
Parameters" registry group.
Each registration includes the authentication method; the
specification that defines the authentication method; the property
type (ptype), which is one of the ptype values from the entries in
the "Email Authentication Property Types" registry in this same
registry group; the property; the value for that property; the status
of the property, which is one of "active" or "deprecated"; and its
version. The designated expert needs to confirm that the provided
specification adequately describes the property and the method for
its evaluation and clearly presents how they would be used within the
DMARC context by Domain Owners and Mail Receivers.
IANA has changed the registration procedure from Expert Review to
Specification Required [RFC8126] and has listed this document as an
additional reference for the registry. IANA has updated the registry
as follows:
+======+============+======+========+===============+======+=======+
|Method| Definition |ptype |Property| Value |Status|Version|
+======+============+======+========+===============+======+=======+
|dmarc | RFC 9989 |header|from | The domain |active|1 |
| | | | | portion of | | |
| | | | | the | | |
| | | | | RFC5322.From | | |
| | | | | header field | | |
+------+------------+------+--------+---------------+------+-------+
|dmarc | RFC 9989 |policy|dmarc | The evaluated |active|1 |
| | | | | DMARC policy | | |
| | | | | applied / to | | |
| | | | | be applied | | |
| | | | | after policy | | |
| | | | | options have | | |
| | | | | been | | |
| | | | | processed. | | |
| | | | | Must be | | |
| | | | | "none", | | |
| | | | | "quarantine", | | |
| | | | | or "reject". | | |
+------+------------+------+--------+---------------+------+-------+
Table 3: Email Authentication Methods Registry Update
9.2. Email Authentication Result Names Registry Update
Result codes for DMARC are registered with IANA in the "Email
Authentication Result Names" registry within "Email Authentication
Parameters" registry group.
Each registration includes the auth method; the code; the
specification that defines the code; and the code's status, which is
one of "active" or "deprecated". Note that the "Description" field
is included here solely for the reader's reference and does not
appear in the IANA registry. The designated expert needs to confirm
that the provided specification adequately describes the result code
and clearly presents how it would be used within the DMARC context by
Domain Owners and Mail Receivers.
IANA has changed the registration procedure from Expert Review to
Specification Required [RFC8126] and has listed this document as an
additional reference for the registry. IANA has updated the registry
as follows, replacing references to [RFC7489] with references to this
document:
+===========+===========+===============+========+==================+
| Auth | Code | Specification | Status | Description |
| Method(s) | | | | |
+===========+===========+===============+========+==================+
| dmarc | fail | RFC 9989 | active | A DMARC Policy |
| | | | | Record exists |
| | | | | for the Author |
| | | | | Domain, but no |
| | | | | Authenticated |
| | | | | Identifier with |
| | | | | Identifier |
| | | | | Alignment |
| | | | | exists |
+-----------+-----------+---------------+--------+------------------+
| dmarc | none | RFC 9989 | active | No DMARC Policy |
| | | | | Record exists |
| | | | | for the Author |
| | | | | Domain |
+-----------+-----------+---------------+--------+------------------+
| dmarc | pass | RFC 9989 | active | A DMARC Policy |
| | | | | Record exists |
| | | | | for the Author |
| | | | | Domain, and an |
| | | | | Authenticated |
| | | | | Identifier with |
| | | | | Identifier |
| | | | | Alignment |
| | | | | exists |
+-----------+-----------+---------------+--------+------------------+
| dmarc | permerror | RFC 9989 | active | An error |
| | | | | occurred during |
| | | | | DMARC |
| | | | | evaluation that |
| | | | | is |
| | | | | unrecoverable, |
| | | | | such as the |
| | | | | retrieval of an |
| | | | | improperly |
| | | | | formatted DMARC |
| | | | | Policy Record. |
| | | | | A later attempt |
| | | | | is unlikely to |
| | | | | produce a final |
| | | | | result |
+-----------+-----------+---------------+--------+------------------+
| dmarc | temperror | RFC 9989 | active | An error |
| | | | | occurred during |
| | | | | DMARC |
| | | | | evaluation that |
| | | | | is likely |
| | | | | transient in |
| | | | | nature, such as |
| | | | | a DNS server |
| | | | | being |
| | | | | temporarily |
| | | | | unreachable. A |
| | | | | later attempt |
| | | | | might produce a |
| | | | | final result |
+-----------+-----------+---------------+--------+------------------+
Table 4: Email Authentication Result Names Registry Update
9.3. DMARC Tags Registry Update
Names of tags used in DMARC Policy Records as part of "tag-value"
pairs are registered with IANA in the "DMARC Tags" registry within
the "Domain-based Message Authentication, Reporting, and Conformance
(DMARC)" registry group.
Entries are assigned only for values that have been documented in a
manner that satisfies the terms of Specification Required, per
[RFC8126]. Each registration includes the tag name, the
specification that defines the tag, the status of the tag, and a
brief description of the tag. The designated expert needs to confirm
that the provided specification adequately describes the tag and
clearly presents how it would be used within the DMARC context by
Domain Owners and Mail Receivers. The "status" column is one of the
following:
* "active", meaning the tag is in use in current implementations,
and its specifications is expected to be stable
* "experimental", meaning the tag is relatively new and may be in
use in some current implementations but not in others, and its
specification is not expected to be stable
* "historic", meaning the tag is considered deprecated and is not
expected to be in use in any current implementation
To avoid version compatibility issues, tags added to the DMARC
specification are to avoid changing the semantics of existing records
when processed by implementations conforming to prior specifications.
IANA has listed this document (rather than [RFC7489]) as the
reference for the registry. IANA has updated the registry as
follows, including the addition of the new "t" registration:
+=======+===========+==========+====================================+
| Tag | Reference | Status | Description |
| Name | | | |
+=======+===========+==========+====================================+
| adkim | RFC 9989 | active | DKIM Identifier Alignment |
| | | | mode |
+-------+-----------+----------+------------------------------------+
| aspf | RFC 9989 | active | SPF Identifier Alignment |
| | | | mode |
+-------+-----------+----------+------------------------------------+
| fo | RFC 9989 | active | Failure reporting options |
+-------+-----------+----------+------------------------------------+
| np | RFC 9989 | active | Requested Domain Owner |
| | | | Assessment Policy for non- |
| | | | existent subdomains |
+-------+-----------+----------+------------------------------------+
| p | RFC 9989 | active | Requested Domain Owner |
| | | | Assessment Policy |
+-------+-----------+----------+------------------------------------+
| pct | [RFC7489] | historic | Sampling rate |
+-------+-----------+----------+------------------------------------+
| psd | RFC 9989 | active | Indicates whether the DMARC |
| | | | Policy Record is published |
| | | | by a Public Suffix Domain |
+-------+-----------+----------+------------------------------------+
| rf | [RFC7489] | historic | Failure reporting format(s) |
+-------+-----------+----------+------------------------------------+
| ri | [RFC7489] | historic | Aggregate Reporting |
| | | | interval |
+-------+-----------+----------+------------------------------------+
| rua | RFC 9989 | active | Reporting URI(s) for DMARC |
| | | | aggregate feedback reports |
+-------+-----------+----------+------------------------------------+
| ruf | RFC 9989 | active | Reporting URI(s) for |
| | | | message-specific DMARC |
| | | | failure reports |
+-------+-----------+----------+------------------------------------+
| sp | RFC 9989 | active | Requested Domain Owner |
| | | | Assessment Policy for |
| | | | subdomains |
+-------+-----------+----------+------------------------------------+
| t | RFC 9989 | active | DMARC policy test mode |
+-------+-----------+----------+------------------------------------+
| v | RFC 9989 | active | DMARC specification version |
+-------+-----------+----------+------------------------------------+
Table 5: DMARC Tags Registry Update
9.4. DMARC Report Formats Registry Update
Names of DMARC failure reporting formats are registered with IANA in
the "DMARC Report Formats" registry within the "Domain-based Message
Authentication, Reporting, and Conformance (DMARC)" registry group.
Entries are assigned only for values that have been documented in a
manner that satisfies the terms of Specification Required, per
[RFC8126]. In addition to a reference to a permanent specification,
each registration includes the format name, the format's status, and
a brief description of the format. The designated expert needs to
confirm that the provided specification adequately describes the
report format and clearly presents how it would be used within the
DMARC context by Domain Owners and Mail Receivers. The "status"
column is one of the following:
* "active", meaning the format is in use in current implementations,
and its specifications is expected to be stable
* "experimental", meaning the format is relatively new and may be in
use in some current implementations but not in others, and its
specification is not expected to be stable
* "historic", meaning the format is considered deprecated and is not
expected to be in use in any current implementation
IANA has listed this document (rather than [RFC7489]) as the
reference for the registry. IANA has updated the registry as
follows:
+========+===========+========+==================================+
| Format | Reference | Status | Description |
| Name | | | |
+========+===========+========+==================================+
| afrf | RFC 9989 | active | Authentication Failure Reporting |
| | | | Format (see [RFC6591]) |
+--------+-----------+--------+----------------------------------+
Table 6: DMARC Report Formats Registry Update
9.5. Underscored and Globally Scoped DNS Node Names Registry Update
The names of DNS Resource Records (RRs) beginning with an underscore
character that are globally scoped (as per [RFC8552]) are registered
with IANA in the "Underscored and Globally Scoped DNS Node Names"
registry within the "Domain Name System (DNS) Parameters" registry
group.
In addition to a reference to a permanent specification, each
registration contains the DNS RR type and Node Name. The designated
expert needs to confirm that the provided specification adequately
describes the Node Name and clearly presents how it would be used
within the DMARC context by Domain Owners and Mail Receivers.
IANA has updated the reference for following entry to point to this
document (instead of [RFC7489]):
+=========+============+===========+
| RR Type | _NODE NAME | Reference |
+=========+============+===========+
| TXT | _dmarc | RFC 9989 |
+---------+------------+-----------+
Table 7: Underscored and
Globally Scoped DNS Node Names
Registry Update