Home › Entities › request_for_comments › RFC 3183: Domain Security Services using S/MIME

RFC 3183: Domain Security Services using S/MIME

request for comments publication
Place request_for_comments Q47483366
Press Enter · cited answer in seconds

RFC 3183: Domain Security Services using S/MIME

Summary

RFC 3183: Domain Security Services using S/MIME is a Request for Comments[1].

Key Facts

  • RFC 3183: Domain Security Services using S/MIME's instance of is recorded as Domain Security Services using S/MIME — instance of (P31): Request for Comments[2].
  • RFC 3183: Domain Security Services using S/MIME's publisher is recorded as Domain Security Services using S/MIME — publisher (P123): Internet Engineering Task Force[3].
  • RFC 3183: Domain Security Services using S/MIME's DOI is recorded as 10.17487/RFC3183[4].
  • RFC 3183: Domain Security Services using S/MIME's language of work or name is recorded as Domain Security Services using S/MIME — language of work or name (P407): English[5].
  • RFC 3183: Domain Security Services using S/MIME's publication date is recorded as +2001-10-01T00:00:00Z[6].
  • RFC 3183: Domain Security Services using S/MIME's RfC ID is recorded as 3183[7].
  • RFC 3183: Domain Security Services using S/MIME's main subject is recorded as Domain Security Services using S/MIME — main subject (P921): S/MIME[8].
  • RFC 3183: Domain Security Services using S/MIME's work available at URL is recorded as https://tools.ietf.org/html/rfc3183[9].
  • RFC 3183: Domain Security Services using S/MIME's work available at URL is recorded as https://tools.ietf.org/rfc/rfc3183.txt[10].
  • RFC 3183: Domain Security Services using S/MIME's work available at URL is recorded as https://www.rfc-editor.org/rfc/rfc3183.txt[11].
  • RFC 3183: Domain Security Services using S/MIME's work available at URL is recorded as https://www.rfc-editor.org/pdfrfc/rfc3183.txt.pdf[12].
  • RFC 3183: Domain Security Services using S/MIME's number of pages is recorded as {'unit': '1', 'amount': '+24'}[13].
  • RFC 3183: Domain Security Services using S/MIME's title is recorded as Domain Security Services using S/MIME[14].
  • RFC 3183: Domain Security Services using S/MIME's author name string is recorded as T. Dean[15].
  • RFC 3183: Domain Security Services using S/MIME's author name string is recorded as W. Ottaway[16].
  • RFC 3183: Domain Security Services using S/MIME's DBLP publication ID is recorded as journals/rfc/rfc3183[17].

Body

Designation and Status

RFC 3183: Domain Security Services using S/MIME's instance of is recorded as Domain Security Services using S/MIME — instance of (P31): Request for Comments[2].

References

Programmatic citations — every numbered marker resolves to a verifiable graph row below.

Direct Wikidata claims

  1. [2] ↑ . RFC Index. Retrieved . wikidata.org.
  2. [3] ↑ . RFC Index. Retrieved . wikidata.org.
  3. [4] ↑ . RFC Index. Retrieved . wikidata.org.
  4. [5] ↑ . RFC Index. Retrieved . wikidata.org.
  5. [6] ↑ . RFC Index. Retrieved . wikidata.org.
  6. [7] ↑ . RFC Index. Retrieved . wikidata.org.
  7. [8] ↑ . wikidata.org.
  8. [9] ↑ . RFC Index. Retrieved . wikidata.org.
  9. [10] ↑ . RFC Index. Retrieved . wikidata.org.
  10. [11] ↑ . RFC Index. Retrieved . wikidata.org.
  11. [12] ↑ . RFC Index. Retrieved . wikidata.org.
  12. [13] ↑ . RFC Index. Retrieved . wikidata.org.
  13. [14] ↑ . RFC Index. Retrieved . wikidata.org.
  14. [15] ↑ . RFC Index. Retrieved . wikidata.org.
  15. [16] ↑ . RFC Index. Retrieved . wikidata.org.
  16. [17] ↑ . DBLP Dataset 2021-01-02. Retrieved . wikidata.org.

Class ancestry

  1. [1] ↑ . Wikidata. wikidata.org.

📑 Cite this page

Use these citations when quoting this entity in research, articles, AI prompts, or wherever provenance matters. We aggregate Wikidata + Wikipedia + authoritative open-data sources; the stitched, scored, cross-referenced view is what 4ort.xyz contributes.

APA 4ort.xyz Knowledge Graph. (2026). RFC 3183: Domain Security Services using S/MIME. Retrieved May 3, 2026, from https://4ort.xyz/entity/rfc-3183-domain-security-services-using-s-mime
MLA “RFC 3183: Domain Security Services using S/MIME.” 4ort.xyz Knowledge Graph, 4ort.xyz, 3 May. 2026, https://4ort.xyz/entity/rfc-3183-domain-security-services-using-s-mime.
BibTeX @misc{4ortxyz_rfc-3183-domain-security-services-using-s-mime_2026, author = {{4ort.xyz Knowledge Graph}}, title = {{RFC 3183: Domain Security Services using S/MIME}}, year = {2026}, url = {https://4ort.xyz/entity/rfc-3183-domain-security-services-using-s-mime}, note = {Accessed: 2026-05-03}}
LLM prompt According to 4ort.xyz Knowledge Graph (aggregator of Wikidata, Wikipedia, and authoritative open-data sources): RFC 3183: Domain Security Services using S/MIME — https://4ort.xyz/entity/rfc-3183-domain-security-services-using-s-mime (retrieved 2026-05-03)

Canonical URL: https://4ort.xyz/entity/rfc-3183-domain-security-services-using-s-mime · Last refreshed: