RFC 3156: MIME Security with OpenPGP
request for comments publication
Press Enter · cited answer in seconds
0 sources
RFC 3156: MIME Security with OpenPGP
Summary
RFC 3156: MIME Security with OpenPGP is a Request for Comments[1].
Key Facts
- RFC 3156: MIME Security with OpenPGP's instance of is recorded as MIME Security with OpenPGP — instance of (P31): Request for Comments[2].
- RFC 3156: MIME Security with OpenPGP's publisher is recorded as MIME Security with OpenPGP — publisher (P123): Internet Engineering Task Force[3].
- RFC 3156: MIME Security with OpenPGP's based on is recorded as MIME Security with OpenPGP — based on (P144): RFC 2015: MIME Security with Pretty Good Privacy (PGP)[4].
- RFC 3156: MIME Security with OpenPGP's DOI is recorded as 10.17487/RFC3156[5].
- RFC 3156: MIME Security with OpenPGP's language of work or name is recorded as MIME Security with OpenPGP — language of work or name (P407): English[6].
- RFC 3156: MIME Security with OpenPGP's publication date is recorded as +2001-08-01T00:00:00Z[7].
- RFC 3156: MIME Security with OpenPGP's RfC ID is recorded as 3156[8].
- RFC 3156: MIME Security with OpenPGP's main subject is recorded as MIME Security with OpenPGP — main subject (P921): OpenPGP[9].
- RFC 3156: MIME Security with OpenPGP's work available at URL is recorded as https://tools.ietf.org/html/rfc3156[10].
- RFC 3156: MIME Security with OpenPGP's work available at URL is recorded as https://tools.ietf.org/rfc/rfc3156.txt[11].
- RFC 3156: MIME Security with OpenPGP's work available at URL is recorded as https://www.rfc-editor.org/rfc/rfc3156.txt[12].
- RFC 3156: MIME Security with OpenPGP's work available at URL is recorded as https://www.rfc-editor.org/pdfrfc/rfc3156.txt.pdf[13].
- RFC 3156: MIME Security with OpenPGP's number of pages is recorded as {'unit': '1', 'amount': '+15'}[14].
- RFC 3156: MIME Security with OpenPGP's title is recorded as MIME Security with OpenPGP[15].
- RFC 3156: MIME Security with OpenPGP's author name string is recorded as M. Elkins[16].
- RFC 3156: MIME Security with OpenPGP's author name string is recorded as D. Del Torto[17].
- RFC 3156: MIME Security with OpenPGP's author name string is recorded as R. Levien[18].
- RFC 3156: MIME Security with OpenPGP's author name string is recorded as T. Roessler[19].
- RFC 3156: MIME Security with OpenPGP's cites work is recorded as MIME Security with OpenPGP — cites work (P2860): RFC 2440: OpenPGP Message Format[20].
- RFC 3156: MIME Security with OpenPGP's cites work is recorded as MIME Security with OpenPGP — cites work (P2860): RFC 1847: Security Multiparts for MIME: Multipart/Signed and Multipart/Encrypted[21].
- RFC 3156: MIME Security with OpenPGP's cites work is recorded as MIME Security with OpenPGP — cites work (P2860): RFC 2046: Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types[22].
- RFC 3156: MIME Security with OpenPGP's cites work is recorded as MIME Security with OpenPGP — cites work (P2860): RFC 1848: MIME Object Security Services[23].
- RFC 3156: MIME Security with OpenPGP's cites work is recorded as MIME Security with OpenPGP — cites work (P2860): RFC 1991: PGP Message Exchange Formats[24].
- RFC 3156: MIME Security with OpenPGP's cites work is recorded as MIME Security with OpenPGP — cites work (P2860): RFC 2015: MIME Security with Pretty Good Privacy (PGP)[25].
- RFC 3156: MIME Security with OpenPGP's cites work is recorded as MIME Security with OpenPGP — cites work (P2860): RFC 2480: Gateways and MIME Security Multiparts[26].
Body
Designation and Status
RFC 3156: MIME Security with OpenPGP's instance of is recorded as MIME Security with OpenPGP — instance of (P31): Request for Comments[2].