RFC 5016: Requirements for a DomainKeys Identified Mail (DKIM) Signing Practices Protocol
0 sources
RFC 5016: Requirements for a DomainKeys Identified Mail (DKIM) Signing Practices Protocol
Summary
RFC 5016: Requirements for a DomainKeys Identified Mail (DKIM) Signing Practices Protocol is a Request for Comments[1].
Key Facts
- RFC 5016: Requirements for a DomainKeys Identified Mail (DKIM) Signing Practices Protocol's instance of is recorded as Requirements for a DomainKeys Identified Mail (DKIM) Signing Practices Protocol — instance of (P31): Request for Comments[2].
- RFC 5016: Requirements for a DomainKeys Identified Mail (DKIM) Signing Practices Protocol's publisher is recorded as Requirements for a DomainKeys Identified Mail (DKIM) Signing Practices Protocol — publisher (P123): Internet Engineering Task Force[3].
- RFC 5016: Requirements for a DomainKeys Identified Mail (DKIM) Signing Practices Protocol's DOI is recorded as 10.17487/RFC5016[4].
- RFC 5016: Requirements for a DomainKeys Identified Mail (DKIM) Signing Practices Protocol's language of work or name is recorded as Requirements for a DomainKeys Identified Mail (DKIM) Signing Practices Protocol — language of work or name (P407): English[5].
- RFC 5016: Requirements for a DomainKeys Identified Mail (DKIM) Signing Practices Protocol's publication date is recorded as +2007-10-01T00:00:00Z[6].
- RFC 5016: Requirements for a DomainKeys Identified Mail (DKIM) Signing Practices Protocol's RfC ID is recorded as 5016[7].
- RFC 5016: Requirements for a DomainKeys Identified Mail (DKIM) Signing Practices Protocol's main subject is recorded as Requirements for a DomainKeys Identified Mail (DKIM) Signing Practices Protocol — main subject (P921): DomainKeys Identified Mail[8].
- RFC 5016: Requirements for a DomainKeys Identified Mail (DKIM) Signing Practices Protocol's work available at URL is recorded as https://tools.ietf.org/html/rfc5016[9].
- RFC 5016: Requirements for a DomainKeys Identified Mail (DKIM) Signing Practices Protocol's work available at URL is recorded as https://tools.ietf.org/rfc/rfc5016.txt[10].
- RFC 5016: Requirements for a DomainKeys Identified Mail (DKIM) Signing Practices Protocol's work available at URL is recorded as https://www.rfc-editor.org/rfc/rfc5016.txt[11].
- RFC 5016: Requirements for a DomainKeys Identified Mail (DKIM) Signing Practices Protocol's work available at URL is recorded as https://www.rfc-editor.org/pdfrfc/rfc5016.txt.pdf[12].
- RFC 5016: Requirements for a DomainKeys Identified Mail (DKIM) Signing Practices Protocol's number of pages is recorded as {'unit': '1', 'amount': '+15'}[13].
- RFC 5016: Requirements for a DomainKeys Identified Mail (DKIM) Signing Practices Protocol's title is recorded as Requirements for a DomainKeys Identified Mail (DKIM) Signing Practices Protocol[14].
- RFC 5016: Requirements for a DomainKeys Identified Mail (DKIM) Signing Practices Protocol's author name string is recorded as M. Thomas[15].
- RFC 5016: Requirements for a DomainKeys Identified Mail (DKIM) Signing Practices Protocol's DBLP publication ID is recorded as journals/rfc/rfc5016[16].
Body
Designation and Status
RFC 5016: Requirements for a DomainKeys Identified Mail (DKIM) Signing Practices Protocol's instance of is recorded as Requirements for a DomainKeys Identified Mail (DKIM) Signing Practices Protocol — instance of (P31): Request for Comments[2].