RFC 8825: Overview: Real-Time Protocols for Browser-Based Applications

Publisher

IETF / RFC Editor

URL

https://www.rfc-editor.org/rfc/rfc8825.html

Published

2021-01-01

Updated

unknown

Accessed

2026-09-24

HTTP status

200

License

IETF Trust Legal Provisions; no-redistribution; short excerpts and locators only

Source notes citing this source

• RFC 8825 defines a WebRTC non-browser endpoint as one that implements the WebRTC protocols but not the JavaScript API, distinct from a WebRTC browser that implements both. in context
• RFC 8825 is an applicability statement: it does not itself specify a protocol but names the specifications a WebRTC implementation must follow. in context
• RFC 8825's list of required specifications names RFC 8829 for JSEP, which RFC 9429 has since obsoleted, so a reader following RFC 8825 literally lands on a superseded JSEP. inferred in context
• The choice of client-server and inter-server signaling protocols, and the translation between them, is outside the scope of the WebRTC protocol suite. in context

Cite this source record

APA

WarmTransfer. (2021, January 1). RFC 8825: Overview: Real-Time Protocols for Browser-Based Applications. WarmTransfer. https://warmtransfer.net/knowledge/sources/rfc-8825-webrtc-overview

BibTeX

@misc{warmtransfer-rfc-8825-webrtc-overview,
  title  = {RFC 8825: Overview: Real-Time Protocols for Browser-Based Applications},
  author = {{WarmTransfer}},
  year   = {2021},
  url    = {https://warmtransfer.net/knowledge/sources/rfc-8825-webrtc-overview},
  note   = {IETF / RFC Editor, accessed 2026-09-24}
}