Home › Entities › request_for_comments › RFC 3552: Guidelines for Writing RFC Text on Security Considerations

RFC 3552: Guidelines for Writing RFC Text on Security Considerations

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

RFC 3552: Guidelines for Writing RFC Text on Security Considerations

Summary

RFC 3552: Guidelines for Writing RFC Text on Security Considerations is a Request for Comments[1].

Key Facts

  • RFC 3552: Guidelines for Writing RFC Text on Security Considerations authored Guidelines for Writing RFC Text on Security Considerations — author (P50): Eric Rescorla[2].
  • RFC 3552: Guidelines for Writing RFC Text on Security Considerations's instance of is recorded as Guidelines for Writing RFC Text on Security Considerations — instance of (P31): Request for Comments[3].
  • RFC 3552: Guidelines for Writing RFC Text on Security Considerations's publisher is recorded as Guidelines for Writing RFC Text on Security Considerations — publisher (P123): Internet Engineering Task Force[4].
  • RFC 3552: Guidelines for Writing RFC Text on Security Considerations's DOI is recorded as 10.17487/RFC3552[5].
  • RFC 3552: Guidelines for Writing RFC Text on Security Considerations's language of work or name is recorded as Guidelines for Writing RFC Text on Security Considerations — language of work or name (P407): English[6].
  • RFC 3552: Guidelines for Writing RFC Text on Security Considerations's publication date is recorded as +2003-07-01T00:00:00Z[7].
  • RFC 3552: Guidelines for Writing RFC Text on Security Considerations's RfC ID is recorded as 3552[8].
  • RFC 3552: Guidelines for Writing RFC Text on Security Considerations's main subject is recorded as Guidelines for Writing RFC Text on Security Considerations — main subject (P921): Request for Comments[9].
  • RFC 3552: Guidelines for Writing RFC Text on Security Considerations's work available at URL is recorded as https://tools.ietf.org/html/rfc3552[10].
  • RFC 3552: Guidelines for Writing RFC Text on Security Considerations's work available at URL is recorded as https://tools.ietf.org/rfc/rfc3552.txt[11].
  • RFC 3552: Guidelines for Writing RFC Text on Security Considerations's work available at URL is recorded as https://www.rfc-editor.org/rfc/rfc3552.txt[12].
  • RFC 3552: Guidelines for Writing RFC Text on Security Considerations's work available at URL is recorded as https://www.rfc-editor.org/pdfrfc/rfc3552.txt.pdf[13].
  • RFC 3552: Guidelines for Writing RFC Text on Security Considerations's number of pages is recorded as {'unit': '1', 'amount': '+44'}[14].
  • RFC 3552: Guidelines for Writing RFC Text on Security Considerations's title is recorded as Guidelines for Writing RFC Text on Security Considerations[15].
  • RFC 3552: Guidelines for Writing RFC Text on Security Considerations's author name string is recorded as B. Korver[16].
  • RFC 3552: Guidelines for Writing RFC Text on Security Considerations's amended by is recorded as Guidelines for Writing RFC Text on Security Considerations — amended by (P2567): RFC 8996: Deprecating TLS 1.0 and TLS 1.1[17].
  • RFC 3552: Guidelines for Writing RFC Text on Security Considerations's amended by is recorded as Guidelines for Writing RFC Text on Security Considerations — amended by (P2567): RFC 9416: Security Considerations for Transient Numeric Identifiers Employed in Network Protocols[18].
  • RFC 3552: Guidelines for Writing RFC Text on Security Considerations's cites work is recorded as Guidelines for Writing RFC Text on Security Considerations — cites work (P2860): RFC 2402: IP Authentication Header[19].
  • RFC 3552: Guidelines for Writing RFC Text on Security Considerations's cites work is recorded as Guidelines for Writing RFC Text on Security Considerations — cites work (P2860): RFC 2535: Domain Name System Security Extensions[20].
  • RFC 3552: Guidelines for Writing RFC Text on Security Considerations's cites work is recorded as Guidelines for Writing RFC Text on Security Considerations — cites work (P2860): RFC 2946: Telnet Data Encryption Option[21].
  • RFC 3552: Guidelines for Writing RFC Text on Security Considerations's cites work is recorded as Guidelines for Writing RFC Text on Security Considerations — cites work (P2860): RFC 2406: IP Encapsulating Security Payload (ESP)[22].
  • RFC 3552: Guidelines for Writing RFC Text on Security Considerations's cites work is recorded as Guidelines for Writing RFC Text on Security Considerations — cites work (P2860): RFC 2743: Generic Security Service Application Program Interface Version 2, Update 1[23].
  • RFC 3552: Guidelines for Writing RFC Text on Security Considerations's cites work is recorded as Guidelines for Writing RFC Text on Security Considerations — cites work (P2860): RFC 2616: Hypertext Transfer Protocol -- HTTP/1.1[24].
  • RFC 3552: Guidelines for Writing RFC Text on Security Considerations's cites work is recorded as Guidelines for Writing RFC Text on Security Considerations — cites work (P2860): RFC 2818: HTTP Over TLS[25].
  • RFC 3552: Guidelines for Writing RFC Text on Security Considerations's cites work is recorded as Guidelines for Writing RFC Text on Security Considerations — cites work (P2860): RFC 2403: The Use of HMAC-MD5-96 within ESP and AH[26].

Body

Designation and Status

RFC 3552: Guidelines for Writing RFC Text on Security Considerations's instance of is recorded as Guidelines for Writing RFC Text on Security Considerations — instance of (P31): Request for Comments[3].

References

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

Direct Wikidata claims

  1. [3] ↑ . RFC Index. Retrieved . wikidata.org.
  2. [2] ↑ . 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] ↑ . RFC Index. Retrieved . wikidata.org.
  8. [9] ↑ . 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] ↑ . RFC Index. Retrieved . wikidata.org.
  17. [18] ↑ . RFC Index. Retrieved . wikidata.org.
  18. [19] ↑ . wikidata.org.
  19. [20] ↑ . wikidata.org.
  20. [21] ↑ . wikidata.org.
  21. [22] ↑ . wikidata.org.
  22. [23] ↑ . wikidata.org.
  23. [24] ↑ . wikidata.org.
  24. [25] ↑ . wikidata.org.
  25. [26] ↑ . 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 3552: Guidelines for Writing RFC Text on Security Considerations. Retrieved May 3, 2026, from https://4ort.xyz/entity/rfc-3552-guidelines-for-writing-rfc-text-on-security-considerations
MLA “RFC 3552: Guidelines for Writing RFC Text on Security Considerations.” 4ort.xyz Knowledge Graph, 4ort.xyz, 3 May. 2026, https://4ort.xyz/entity/rfc-3552-guidelines-for-writing-rfc-text-on-security-considerations.
BibTeX @misc{4ortxyz_rfc-3552-guidelines-for-writing-rfc-text-on-security-considerations_2026, author = {{4ort.xyz Knowledge Graph}}, title = {{RFC 3552: Guidelines for Writing RFC Text on Security Considerations}}, year = {2026}, url = {https://4ort.xyz/entity/rfc-3552-guidelines-for-writing-rfc-text-on-security-considerations}, note = {Accessed: 2026-05-03}}
LLM prompt According to 4ort.xyz Knowledge Graph (aggregator of Wikidata, Wikipedia, and authoritative open-data sources): RFC 3552: Guidelines for Writing RFC Text on Security Considerations — https://4ort.xyz/entity/rfc-3552-guidelines-for-writing-rfc-text-on-security-considerations (retrieved 2026-05-03)

Canonical URL: https://4ort.xyz/entity/rfc-3552-guidelines-for-writing-rfc-text-on-security-considerations · Last refreshed: