WebRTC Dependencies
draft-jennings-rtcweb-deps-27
|
| Document |
Type |
|
Active Internet-Draft (individual)
|
|
Author |
|
Cullen Jennings
|
|
Last updated |
|
2021-01-21
|
|
Stream |
|
(None)
|
|
Intended RFC status |
|
(None)
|
|
Formats |
|
plain text
pdf
htmlized (tools)
htmlized
bibtex
|
| Stream |
Stream state |
|
(No stream defined) |
|
Consensus Boilerplate |
|
Unknown
|
|
RFC Editor Note |
|
(None)
|
| IESG |
IESG state |
|
I-D Exists
|
|
Telechat date |
|
|
|
Responsible AD |
|
(None)
|
|
Send notices to |
|
(None)
|
Network Working Group C. Jennings
Internet-Draft cisco
Intended status: Informational 21 January 2021
Expires: 25 July 2021
WebRTC Dependencies
draft-jennings-rtcweb-deps-27
Abstract
This draft will never be published as an RFC and is meant purely to
help track the IETF dependencies from the W3C WebRTC documents.
Status of This Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
This Internet-Draft will expire on 25 July 2021.
Copyright Notice
Copyright (c) 2021 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents (https://trustee.ietf.org/
license-info) in effect on the date of publication of this document.
Please review these documents carefully, as they describe your rights
and restrictions with respect to this document. Code Components
extracted from this document must include Simplified BSD License text
as described in Section 4.e of the Trust Legal Provisions and are
provided without warranty as described in the Simplified BSD License.
Table of Contents
1. Dependencies . . . . . . . . . . . . . . . . . . . . . . . . 2
Jennings Expires 25 July 2021 [Page 1]
Internet-Draft WebRTC Dependencies January 2021
1.1. Dependency Details . . . . . . . . . . . . . . . . . . . 2
1.2. Status . . . . . . . . . . . . . . . . . . . . . . . . . 2
1.3. RFCs . . . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Normative References . . . . . . . . . . . . . . . . . . . . 8
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 21
1. Dependencies
The key IETF drafts that the W3C WebRTC specification normatively
depended on are:
1.1. Dependency Details
The drafts that are normative dependencies of drafts WebRTC depends
on are:
1.2. Status
1.3. RFCs
The key RFC that the W3C WebRTC specification normatively depended on
are:
[RFC3550] [RFC3890] [RFC4566] [RFC4572] [RFC5285] [RFC5389] [RFC5506]
[RFC5761] [RFC5888] [RFC6464] [RFC6465] [RFC6544] [RFC6749] [RFC7064]
[RFC7065] [RFC7515] [RFC7635] [RFC7675] [RFC8826] [RFC8829] [RFC8831]
[RFC8832] [RFC8834] [RFC8835] [RFC8837] [RFC8838] [RFC8841] [RFC8843]
[RFC8851] [RFC8853]
The following drafts and RFC are normative dependencies of WebRTC.
This list excludes many common specs outside of WebRTC such as UDP
and TCP that are also needed.
RFC3711 normatively depends on [RFC3550] [RFC3551]
RFC4571 normatively depends on [RFC3264] [RFC3550] [RFC3551]
[RFC3556]
RFC4961 normatively depends on
RFC5061 normatively depends on [RFC4895]
RFC5104 normatively depends on [RFC3264] [RFC3550] [RFC4566]
[RFC4585]
RFC5245 normatively depends on [RFC3264] [RFC3556] [RFC4566]
[RFC5389] [RFC5766] [RFC5768]
Jennings Expires 25 July 2021 [Page 2]
Internet-Draft WebRTC Dependencies January 2021
RFC5285 normatively depends on [RFC3550] [RFC3711] [RFC4566]
RFC5389 normatively depends on
RFC5506 normatively depends on [RFC3550] [RFC3551] [RFC4585]
[RFC5124]
RFC5576 normatively depends on [RFC3264] [RFC3388] [RFC3550]
[RFC4566] [RFC4756]
RFC5583 normatively depends on [RFC3388] [RFC3550] [RFC3551]
[RFC3711] [RFC4566]
RFC5705 normatively depends on
RFC5763 normatively depends on [RFC3264] [RFC3550] [RFC4145]
[RFC4566] [RFC4572] [RFC5389]
RFC5764 normatively depends on [RFC3711] [RFC4961] [RFC5705]
[RFC5761]
RFC5766 normatively depends on [RFC5389]
RFC5768 normatively depends on [RFC3264] [RFC4566] [RFC5245]
RFC5888 normatively depends on [RFC3264] [RFC4566]
RFC5928 normatively depends on [RFC5389] [RFC5766]
RFC5956 normatively depends on [RFC3264] [RFC3550] [RFC4566]
[RFC5576] [RFC5888]
RFC6051 normatively depends on [RFC3550] [RFC4585] [RFC5285]
[RFC5506] [RFC5583]
RFC6062 normatively depends on [RFC5389] [RFC5766]
RFC6096 normatively depends on [RFC3758] [RFC4820] [RFC4895]
[RFC5061]
RFC6188 normatively depends on [RFC3550] [RFC3711]
Show full document text