RFC 5672: RFC 4871 DomainKeys Identified Mail (DKIM) Signatures -- Update
0 sources
RFC 5672: RFC 4871 DomainKeys Identified Mail (DKIM) Signatures -- Update
Summary
RFC 5672: RFC 4871 DomainKeys Identified Mail (DKIM) Signatures -- Update is a Request for Comments[1].
Key Facts
- RFC 5672: RFC 4871 DomainKeys Identified Mail (DKIM) Signatures -- Update authored RFC 4871 DomainKeys Identified Mail (DKIM) Signatures -- Update — author (P50): Steve Crocker[2].
- RFC 5672: RFC 4871 DomainKeys Identified Mail (DKIM) Signatures -- Update's instance of is recorded as RFC 4871 DomainKeys Identified Mail (DKIM) Signatures -- Update — instance of (P31): Request for Comments[3].
- RFC 5672: RFC 4871 DomainKeys Identified Mail (DKIM) Signatures -- Update's publisher is recorded as RFC 4871 DomainKeys Identified Mail (DKIM) Signatures -- Update — publisher (P123): Internet Engineering Task Force[4].
- RFC 5672: RFC 4871 DomainKeys Identified Mail (DKIM) Signatures -- Update's based on is recorded as RFC 4871 DomainKeys Identified Mail (DKIM) Signatures -- Update — based on (P144): RFC 4871: DomainKeys Identified Mail (DKIM) Signatures[5].
- RFC 5672: RFC 4871 DomainKeys Identified Mail (DKIM) Signatures -- Update's DOI is recorded as 10.17487/RFC5672[6].
- RFC 5672: RFC 4871 DomainKeys Identified Mail (DKIM) Signatures -- Update's language of work or name is recorded as RFC 4871 DomainKeys Identified Mail (DKIM) Signatures -- Update — language of work or name (P407): English[7].
- RFC 5672: RFC 4871 DomainKeys Identified Mail (DKIM) Signatures -- Update's publication date is recorded as +2009-08-01T00:00:00Z[8].
- RFC 5672: RFC 4871 DomainKeys Identified Mail (DKIM) Signatures -- Update's RfC ID is recorded as 5672[9].
- RFC 5672: RFC 4871 DomainKeys Identified Mail (DKIM) Signatures -- Update's main subject is recorded as RFC 4871 DomainKeys Identified Mail (DKIM) Signatures -- Update — main subject (P921): DomainKeys Identified Mail[10].
- RFC 5672: RFC 4871 DomainKeys Identified Mail (DKIM) Signatures -- Update's work available at URL is recorded as https://tools.ietf.org/html/rfc5672[11].
- RFC 5672: RFC 4871 DomainKeys Identified Mail (DKIM) Signatures -- Update's work available at URL is recorded as https://tools.ietf.org/rfc/rfc5672.txt[12].
- RFC 5672: RFC 4871 DomainKeys Identified Mail (DKIM) Signatures -- Update's work available at URL is recorded as https://www.rfc-editor.org/rfc/rfc5672.txt[13].
- RFC 5672: RFC 4871 DomainKeys Identified Mail (DKIM) Signatures -- Update's work available at URL is recorded as https://www.rfc-editor.org/pdfrfc/rfc5672.txt.pdf[14].
- RFC 5672: RFC 4871 DomainKeys Identified Mail (DKIM) Signatures -- Update's number of pages is recorded as {'unit': '1', 'amount': '+14'}[15].
- RFC 5672: RFC 4871 DomainKeys Identified Mail (DKIM) Signatures -- Update's replaced by is recorded as RFC 4871 DomainKeys Identified Mail (DKIM) Signatures -- Update — replaced by (P1366): RFC 6376: DomainKeys Identified Mail (DKIM) Signatures[16].
- RFC 5672: RFC 4871 DomainKeys Identified Mail (DKIM) Signatures -- Update's title is recorded as RFC 4871 DomainKeys Identified Mail (DKIM) Signatures -- Update[17].
- RFC 5672: RFC 4871 DomainKeys Identified Mail (DKIM) Signatures -- Update's DBLP publication ID is recorded as journals/rfc/rfc5672[18].
Body
Designation and Status
RFC 5672: RFC 4871 DomainKeys Identified Mail (DKIM) Signatures -- Update's instance of is recorded as RFC 4871 DomainKeys Identified Mail (DKIM) Signatures -- Update — instance of (P31): Request for Comments[3].