Home › Entities › request_for_comments › RFC 9700: Best Current Practice for OAuth 2.0 Security

RFC 9700: Best Current Practice for OAuth 2.0 Security

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

RFC 9700: Best Current Practice for OAuth 2.0 Security

Summary

RFC 9700: Best Current Practice for OAuth 2.0 Security is a Request for Comments[1].

Key Facts

  • RFC 9700: Best Current Practice for OAuth 2.0 Security's instance of is recorded as Best Current Practice for OAuth 2.0 Security — instance of (P31): Request for Comments[2].
  • RFC 9700: Best Current Practice for OAuth 2.0 Security's publisher is recorded as Best Current Practice for OAuth 2.0 Security — publisher (P123): Internet Engineering Task Force[3].
  • RFC 9700: Best Current Practice for OAuth 2.0 Security's based on is recorded as Best Current Practice for OAuth 2.0 Security — based on (P144): RFC 6749: The OAuth 2.0 Authorization Framework[4].
  • RFC 9700: Best Current Practice for OAuth 2.0 Security's based on is recorded as Best Current Practice for OAuth 2.0 Security — based on (P144): RFC 6750: The OAuth 2.0 Authorization Framework: Bearer Token Usage[5].
  • RFC 9700: Best Current Practice for OAuth 2.0 Security's based on is recorded as Best Current Practice for OAuth 2.0 Security — based on (P144): RFC 6819: OAuth 2.0 Threat Model and Security Considerations[6].
  • RFC 9700: Best Current Practice for OAuth 2.0 Security's DOI is recorded as 10.17487/RFC9700[7].
  • RFC 9700: Best Current Practice for OAuth 2.0 Security's language of work or name is recorded as Best Current Practice for OAuth 2.0 Security — language of work or name (P407): English[8].
  • RFC 9700: Best Current Practice for OAuth 2.0 Security's publication date is recorded as +2025-01-01T00:00:00Z[9].
  • RFC 9700: Best Current Practice for OAuth 2.0 Security's RfC ID is recorded as 9700[10].
  • RFC 9700: Best Current Practice for OAuth 2.0 Security's work available at URL is recorded as https://tools.ietf.org/html/rfc9700[11].
  • RFC 9700: Best Current Practice for OAuth 2.0 Security's title is recorded as Best Current Practice for OAuth 2.0 Security[12].
  • RFC 9700: Best Current Practice for OAuth 2.0 Security's author name string is recorded as T. Lodderstedt[13].
  • RFC 9700: Best Current Practice for OAuth 2.0 Security's author name string is recorded as J. Bradley[14].
  • RFC 9700: Best Current Practice for OAuth 2.0 Security's author name string is recorded as A. Labunets[15].
  • RFC 9700: Best Current Practice for OAuth 2.0 Security's author name string is recorded as D. Fett[16].

Body

Designation and Status

RFC 9700: Best Current Practice for OAuth 2.0 Security's instance of is recorded as Best Current Practice for OAuth 2.0 Security — 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] ↑ . RFC Index. Retrieved . 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.

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 9700: Best Current Practice for OAuth 2.0 Security. Retrieved May 3, 2026, from https://4ort.xyz/entity/rfc-9700-best-current-practice-for-oauth-2-0-security
MLA “RFC 9700: Best Current Practice for OAuth 2.0 Security.” 4ort.xyz Knowledge Graph, 4ort.xyz, 3 May. 2026, https://4ort.xyz/entity/rfc-9700-best-current-practice-for-oauth-2-0-security.
BibTeX @misc{4ortxyz_rfc-9700-best-current-practice-for-oauth-2-0-security_2026, author = {{4ort.xyz Knowledge Graph}}, title = {{RFC 9700: Best Current Practice for OAuth 2.0 Security}}, year = {2026}, url = {https://4ort.xyz/entity/rfc-9700-best-current-practice-for-oauth-2-0-security}, note = {Accessed: 2026-05-03}}
LLM prompt According to 4ort.xyz Knowledge Graph (aggregator of Wikidata, Wikipedia, and authoritative open-data sources): RFC 9700: Best Current Practice for OAuth 2.0 Security — https://4ort.xyz/entity/rfc-9700-best-current-practice-for-oauth-2-0-security (retrieved 2026-05-03)

Canonical URL: https://4ort.xyz/entity/rfc-9700-best-current-practice-for-oauth-2-0-security · Last refreshed: