|
Author Domain Signing Practices
In computing, Author Domain Signing Practices (ADSP) is an optional extension to the DKIM E-mail authentication scheme, whereby a domain can publish the signing practices it adopts when relaying mail on behalf of associated authors. ADSP was adopted as a standards track RFC 5617 in August 2009, but declared "Historic" in November 2013 after "...almost no deployment and use in the 4 years since...". Concepts Author address The ''author address'' is the one specified in the header field defined in RFC 5322. In the unusual cases where more than one address is defined in that field, RFC 5322 provides for a field to be used instead. The domains in 5322-''From'' addresses are not necessarily the same as in the more elaborated ''Purported Responsible Address'' covered by Sender ID specified in RFC 4407. The domain in a 5322-''From'' address is also not necessarily the same as in the ''envelope sender'' address defined in RFC 5321, also known as SMTP MAIL FROM, envelope-''From'', ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
DomainKeys
DomainKeys (informally ''DK'') is a deprecated e-mail authentication system designed by Yahoo to verify the domain name of an e-mail sender and the message integrity. Aspects of DomainKeys, along with parts of Identified Internet Mail, were combined to create DomainKeys Identified Mail (DKIM),Delany, Mark (May 22, 2007)"One small step for email, one giant leap for Internet safety" Yahoo! corporate blog. Delany is credited as Chief Architect, inventor of DomainKeys. which is now widely used. Both DomainKeys and DKIM were published in May 2007, DomainKeys as an "historical" protocol, and DKIM as its standards-track replacement. See also * Sender ID * Author Domain Signing Practices * Sender Policy Framework Sender Policy Framework (SPF) is an email authentication method designed to detect forging sender addresses during the delivery of the email. SPF alone, though, is limited to detecting a forged sender claim in the envelope of the email, which is ... (SPF) References Externa ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
IETF
The Internet Engineering Task Force (IETF) is a standards organization for the Internet and is responsible for the technical standards that make up the Internet protocol suite (TCP/IP). It has no formal membership roster or requirements and all its participants are volunteers. Their work is usually funded by employers or other sponsors. The IETF was initially supported by the federal government of the United States but since 1993 has operated under the auspices of the Internet Society, an international non-profit organization. Organization The IETF is organized into a large number of working groups and birds of a feather informal discussion groups, each dealing with a specific topic. The IETF operates in a bottom-up task creation mode, largely driven by these working groups. Each working group has an appointed chairperson (or sometimes several co-chairs); a charter that describes its focus; and what it is expected to produce, and when. It is open to all who want to particip ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
Sender ID
Sender ID is an historic anti- spoofing proposal from the former MARID IETF working group that tried to join Sender Policy Framework (SPF) and Caller ID. Sender ID is defined primarily in Experimental RFC 4406, but there are additional parts in RFC 4405, RFC 4407 and RFC 4408. Principles of operation Sender ID is heavily based on SPF, with only a few additions. Sender ID tries to improve on SPF: SPF does not verify the header addresses (of which there can be more than one) that indicate the claimed sending party. One of these header addresses is typically displayed to the user and may be used to reply to emails. These header addresses can be different from the address that SPF tries to verify; that is, SPF verifies only the "MAIL FROM" address, also called the envelope sender. However, there are many similar email header fields that all contain sending party information; therefore Sender ID defines in RFC 4407 a Purported Responsible Address (PRA) as well as a set of heuristi ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |