RFC 4870: Domain-Based Email Authentication Using Public Keys Advertised in the DNS (DomainKeys)
0 sources
RFC 4870: Domain-Based Email Authentication Using Public Keys Advertised in the DNS (DomainKeys)
Summary
RFC 4870: Domain-Based Email Authentication Using Public Keys Advertised in the DNS (DomainKeys) is a Request for Comments[1].
Key Facts
- RFC 4870: Domain-Based Email Authentication Using Public Keys Advertised in the DNS (DomainKeys)'s instance of is recorded as Domain-Based Email Authentication Using Public Keys Advertised in the DNS (DomainKeys) — instance of (P31): Request for Comments[2].
- RFC 4870: Domain-Based Email Authentication Using Public Keys Advertised in the DNS (DomainKeys)'s publisher is recorded as Domain-Based Email Authentication Using Public Keys Advertised in the DNS (DomainKeys) — publisher (P123): Internet Engineering Task Force[3].
- RFC 4870: Domain-Based Email Authentication Using Public Keys Advertised in the DNS (DomainKeys)'s DOI is recorded as 10.17487/RFC4870[4].
- RFC 4870: Domain-Based Email Authentication Using Public Keys Advertised in the DNS (DomainKeys)'s language of work or name is recorded as Domain-Based Email Authentication Using Public Keys Advertised in the DNS (DomainKeys) — language of work or name (P407): English[5].
- RFC 4870: Domain-Based Email Authentication Using Public Keys Advertised in the DNS (DomainKeys)'s publication date is recorded as +2007-05-01T00:00:00Z[6].
- RFC 4870: Domain-Based Email Authentication Using Public Keys Advertised in the DNS (DomainKeys)'s RfC ID is recorded as 4870[7].
- RFC 4870: Domain-Based Email Authentication Using Public Keys Advertised in the DNS (DomainKeys)'s main subject is recorded as Domain-Based Email Authentication Using Public Keys Advertised in the DNS (DomainKeys) — main subject (P921): DomainKeys[8].
- RFC 4870: Domain-Based Email Authentication Using Public Keys Advertised in the DNS (DomainKeys)'s work available at URL is recorded as https://tools.ietf.org/html/rfc4870[9].
- RFC 4870: Domain-Based Email Authentication Using Public Keys Advertised in the DNS (DomainKeys)'s work available at URL is recorded as https://tools.ietf.org/rfc/rfc4870.txt[10].
- RFC 4870: Domain-Based Email Authentication Using Public Keys Advertised in the DNS (DomainKeys)'s work available at URL is recorded as https://www.rfc-editor.org/rfc/rfc4870.txt[11].
- RFC 4870: Domain-Based Email Authentication Using Public Keys Advertised in the DNS (DomainKeys)'s work available at URL is recorded as https://www.rfc-editor.org/pdfrfc/rfc4870.txt.pdf[12].
- RFC 4870: Domain-Based Email Authentication Using Public Keys Advertised in the DNS (DomainKeys)'s number of pages is recorded as {'unit': '1', 'amount': '+41'}[13].
- RFC 4870: Domain-Based Email Authentication Using Public Keys Advertised in the DNS (DomainKeys)'s replaced by is recorded as Domain-Based Email Authentication Using Public Keys Advertised in the DNS (DomainKeys) — replaced by (P1366): RFC 4871: DomainKeys Identified Mail (DKIM) Signatures[14].
- RFC 4870: Domain-Based Email Authentication Using Public Keys Advertised in the DNS (DomainKeys)'s title is recorded as Domain-Based Email Authentication Using Public Keys Advertised in the DNS (DomainKeys)[15].
- RFC 4870: Domain-Based Email Authentication Using Public Keys Advertised in the DNS (DomainKeys)'s author name string is recorded as M. Delany[16].
- RFC 4870: Domain-Based Email Authentication Using Public Keys Advertised in the DNS (DomainKeys)'s DBLP publication ID is recorded as journals/rfc/rfc4870[17].
Body
Designation and Status
RFC 4870: Domain-Based Email Authentication Using Public Keys Advertised in the DNS (DomainKeys)'s instance of is recorded as Domain-Based Email Authentication Using Public Keys Advertised in the DNS (DomainKeys) — instance of (P31): Request for Comments[2].