WebRTC Dependencies
draft-jennings-rtcweb-deps-08

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 http://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 August 28, 2016.

Copyright Notice

Copyright (c) 2016 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 (http://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.

1. Dependencies

The key IETF specifications that the W3C GetUserMedia specification normatively depends on is: [I-D.ietf-rtcweb-security-arch] and [RFC2119].

The key IETF specifications that the W3C WebRTC specification normatively depended on are: [I-D.ietf-rtcweb-alpn], [I-D.ietf-rtcweb-audio], [I-D.ietf-rtcweb-data-channel], [I-D.ietf-rtcweb-data-protocol], [I-D.ietf-rtcweb-jsep], [I-D.ietf-rtcweb-rtp-usage], [I-D.ietf-rtcweb-security-arch], [I-D.ietf-rtcweb-transports], [I-D.ietf-rtcweb-video], [I-D.ietf-tram-turn-third-party-authz], [I-D.ietf-tsvwg-rtcweb-qos], [RFC2119], [RFC4566], [RFC5389], [RFC5888], [RFC6236], [RFC6464], [RFC6465], [RFC6544], [RFC7064], [RFC7065] [RFC3264], [RFC5245], and informatively depends on [I-D.ietf-rtcweb-overview], [I-D.ietf-rtcweb-security], [I-D.shieh-rtcweb-ip-handling], and [I-D.ietf-mmusic-trickle-ice].

In addition 3GPP work normatively depends on [I-D.ietf-rtcweb-gateways].

These IETF drafts in turn normatively depend on the following drafts: (Note this list is out of date) [I-D.ietf-avtcore-multi-media-rtp-session], [I-D.ietf-avtcore-rtp-circuit-breakers], [I-D.ietf-avtcore-rtp-multi-stream-optimisation], [I-D.ietf-avtcore-rtp-multi-stream], [I-D.ietf-ice-dualstack-fairness], [I-D.ietf-jose-json-web-algorithms]. [I-D.ietf-mmusic-msid], [I-D.ietf-mmusic-proto-iana-registration], [I-D.ietf-mmusic-sctp-sdp], [I-D.ietf-mmusic-sdp-bundle-negotiation], [I-D.ietf-mmusic-sdp-mux-attributes], [I-D.ietf-mmusic-trickle-ice], [I-D.ietf-payload-flexible-fec-scheme], [I-D.ietf-payload-rtp-opus], [I-D.ietf-payload-vp8], [I-D.ietf-rtcweb-alpn], [I-D.ietf-rtcweb-data-protocol], [I-D.ietf-rtcweb-fec], [I-D.ietf-rtcweb-security], [I-D.ietf-rtcweb-stun-consent-freshness], [I-D.ietf-tls-applayerprotoneg], [I-D.ietf-tram-alpn], [I-D.ietf-tsvwg-rtcweb-qos], [I-D.ietf-tsvwg-sctp-dtls-encaps], [I-D.ietf-tsvwg-sctp-ndata], and [I-D.ietf-tsvwg-sctp-prpolicies].

Right now security normatively depends on [I-D.ietf-rtcweb-overview].

The drafts webrtc currently normatively depends on that are not WG drafts are: [I-D.shieh-rtcweb-ip-handling]

A few key drafts that the work informatively depends on: [I-D.alvestrand-rtcweb-gateways], [I-D.hutton-rtcweb-nat-firewall-considerations], [I-D.ietf-avtcore-multiplex-guidelines], [I-D.ietf-avtcore-rtp-topologies-update], [I-D.ietf-avtcore-srtp-ekt], [I-D.ietf-avtext-rtp-grouping-taxonomy], [I-D.ietf-dart-dscp-rtp], [I-D.ietf-mmusic-trickle-ice], [I-D.ietf-rmcat-cc-requirements], [I-D.ietf-rtcweb-use-cases-and-requirements], [I-D.kaufman-rtcweb-security-ui], [I-D.lennox-payload-ulp-ssrc-mux], [I-D.ietf-rtcweb-sdp], [I-D.roach-mmusic-unified-plan], [I-D.ietf-rtcweb-audio-codecs-for-interop], [I-D.westerlund-avtcore-multiplex-architecture].

1.1. Time Estimates

The following table has some very rough estimates of when the draft will become an RFC. Historically these dates have often taken much longer than the estimates so take this with a large dose of salt.

Last updated Feb 25, 2016.

2. References

2.1. Normative References

2.2. Informative References

Author's Address

Table of Contents

• 1. Dependencies
• 1.1. Time Estimates
• 2. References
• 2.1. Normative References
• 2.2. Informative References
• Author's Address