![]() ![]() ![]() To match the current states of these specifications.From eID we offer KYC (Know Your Customer), customer onboarding and digital identity solutions and services that help our customers to provide theirs a unique, simple, frictionless, high-security experience that meets the highest standards required in international regulations. Registries and their contents and specifies the process by whichĮntries are added or updated. Refer to the specifications listed above. There exist registries for tokens used within this header field that Discussion regarding moving it to Historic status is Specification (Experimental) is no longer supported by Note that at the time of publication of this document the Sender ID O Author Domain Signing Practices (Historic) This framework but have since become obsolete: The following Historic specifications were previously supported by O Require-Recipient-Valid-Since Header Field and SMTP Service O reverse IP address name validation ("iprev", defined in Section 3) O Domain-based Message Authentication, Reporting, and Conformance O SMTP Service Extension for Authentication Render those results, as these are local policy and/or user interfaceĭesign questions that are not appropriate for this document.Īt the time of publication of this document, the following are Such as what filtering decisions are appropriate or how an MUA might However, it does notĭiscuss how the data contained in the header field ought to be used, The implications of its presence or absence. This document specifies the format of this header field and discusses ![]() That will then use such data or render it in a human-usable form. This header field is intended for consumption by programs Message's origin and possibly the safety and integrity of itsĮnd users are not expected to be direct consumers of this headerįield. When message authentication mechanisms are in use so that a Mail UserĪgent (MUA) and downstream filters can make filtering decisionsĪnd/or provide a recommendation to the user as to the validity of the Intent of the header field is to create a place to collect such data Message authentication effort in a machine-readable format. Results" for electronic mail messages that presents the results of a This document describes a header field called "Authentication. RFC 8601 Authentication-Results Header Field May 2019 1. Operational Considerations about MessageĪuthentication. Service Provided, Multi-tiered Authentication Done. Service Provided, Several Authentications Done, Different Service Provided, Several Authentications Done, Single Nearly Trivial Case: Service Provided, but NoĪuthentication Done. Reverse IP Query Denial-of-Service Attacks. "Email Authentication Result Names" Registry Update. "Email Authentication Result Names" Registry Description. "Email Authentication Property Types" Registry Update. "Email Authentication Property Types" Registryĭescription. "Email Authentication Methods" Registry Update. "Email Authentication Methods" Registry Description. RFC 8601 Authentication-Results Header Field May 2019 5. Header Field Position and Interpretation. Definition and Format of the Header Field. The Trust Legal Provisions and are provided without warranty asġ. Include Simplified BSD License text as described in Section 4.e of Code Components extracted from this document must Please review these documentsĬarefully, as they describe your rights and restrictions with respect This document is subject to BCP 78 and the IETF Trust's Legal RFC 8601 Authentication-Results Header Field May 2019Ĭopyright (c) 2019 IETF Trust and the persons identified as the Information about the current status of this document, any errata,Īnd how to provide feedback on it may be obtained at Internet Standards is available in Section 2 of RFC 7841. Internet Engineering Steering Group (IESG). Received public review and has been approved for publication by the It represents the consensus of the IETF community. This document is a product of the Internet Engineering Task Force This is an Internet Standards Track document. (MUAs), can use this header field to relay that information in aĬonvenient and meaningful way to users or to make sorting and Receiver-side software, such as mail filters or Mail User Agents Indicate the results of message authentication efforts. "Authentication-Results" for use with electronic mail messages to This document specifies a message header field called Message Header Field for Indicating Message Authentication Status Internet Engineering Task Force (IETF) M. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |