RFC 1847: Security Multiparts for MIME: Multipart/Signed and Multipart/Encrypted
0 sources
RFC 1847: Security Multiparts for MIME: Multipart/Signed and Multipart/Encrypted
Summary
RFC 1847: Security Multiparts for MIME: Multipart/Signed and Multipart/Encrypted is a Request for Comments[1].
Key Facts
- RFC 1847: Security Multiparts for MIME: Multipart/Signed and Multipart/Encrypted authored Security Multiparts for MIME: Multipart/Signed and Multipart/Encrypted — author (P50): Steve Crocker[2].
- RFC 1847: Security Multiparts for MIME: Multipart/Signed and Multipart/Encrypted authored Security Multiparts for MIME: Multipart/Signed and Multipart/Encrypted — author (P50): Ned Freed[3].
- RFC 1847: Security Multiparts for MIME: Multipart/Signed and Multipart/Encrypted authored Security Multiparts for MIME: Multipart/Signed and Multipart/Encrypted — author (P50): Sandy Murphy[4].
- RFC 1847: Security Multiparts for MIME: Multipart/Signed and Multipart/Encrypted's instance of is recorded as Security Multiparts for MIME: Multipart/Signed and Multipart/Encrypted — instance of (P31): Request for Comments[5].
- RFC 1847: Security Multiparts for MIME: Multipart/Signed and Multipart/Encrypted's publisher is recorded as Security Multiparts for MIME: Multipart/Signed and Multipart/Encrypted — publisher (P123): Internet Engineering Task Force[6].
- RFC 1847: Security Multiparts for MIME: Multipart/Signed and Multipart/Encrypted's DOI is recorded as 10.17487/RFC1847[7].
- RFC 1847: Security Multiparts for MIME: Multipart/Signed and Multipart/Encrypted's language of work or name is recorded as Security Multiparts for MIME: Multipart/Signed and Multipart/Encrypted — language of work or name (P407): English[8].
- RFC 1847: Security Multiparts for MIME: Multipart/Signed and Multipart/Encrypted's publication date is recorded as +1995-10-01T00:00:00Z[9].
- RFC 1847: Security Multiparts for MIME: Multipart/Signed and Multipart/Encrypted's RfC ID is recorded as 1847[10].
- RFC 1847: Security Multiparts for MIME: Multipart/Signed and Multipart/Encrypted's work available at URL is recorded as https://tools.ietf.org/html/rfc1847[11].
- RFC 1847: Security Multiparts for MIME: Multipart/Signed and Multipart/Encrypted's work available at URL is recorded as https://tools.ietf.org/rfc/rfc1847.txt[12].
- RFC 1847: Security Multiparts for MIME: Multipart/Signed and Multipart/Encrypted's work available at URL is recorded as https://www.rfc-editor.org/rfc/rfc1847.txt[13].
- RFC 1847: Security Multiparts for MIME: Multipart/Signed and Multipart/Encrypted's work available at URL is recorded as https://www.rfc-editor.org/pdfrfc/rfc1847.txt.pdf[14].
- RFC 1847: Security Multiparts for MIME: Multipart/Signed and Multipart/Encrypted's number of pages is recorded as {'unit': '1', 'amount': '+11'}[15].
- RFC 1847: Security Multiparts for MIME: Multipart/Signed and Multipart/Encrypted's title is recorded as Security Multiparts for MIME: Multipart/Signed and Multipart/Encrypted[16].
- RFC 1847: Security Multiparts for MIME: Multipart/Signed and Multipart/Encrypted's author name string is recorded as J. Galvin[17].
- RFC 1847: Security Multiparts for MIME: Multipart/Signed and Multipart/Encrypted's DBLP publication ID is recorded as journals/rfc/rfc1847[18].
Body
Designation and Status
RFC 1847: Security Multiparts for MIME: Multipart/Signed and Multipart/Encrypted's instance of is recorded as Security Multiparts for MIME: Multipart/Signed and Multipart/Encrypted — instance of (P31): Request for Comments[5].