广西11选5开奖记录:WebRTC DSCP Control API

W3C First Public Working Draft,

This version:
//www.0b5fq.cn/TR/2018/WD-webrtc-dscp-20180703/
Latest published version:
//www.0b5fq.cn/TR/webrtc-dscp/
Editor's Draft:
https://w3c.github.io/webrtc-dscp-exp/
Feedback:
[email protected] with subject line “[webrtc-dscp] … message topic …” (archives)
Editor:
(Google Inc.)

Abstract

This API defines a control surface for manipulating the network control bits (DSCP bits) of outgoing WebRTC packets.

Status of this document

This section describes the status of this document at the time of its publication. Other documents may supersede this document. A list of current W3C publications and the latest revision of this technical report can be found in the W3C technical reports index at //www.0b5fq.cn/TR/.

This document was published by the Web Real-Time Communications Working Group as a Working Draft. This document is intended to become a W3C Recommendation.

If you wish to make comments regarding this document, please send them to [email protected] (subscribe, archives). When sending e-mail, please put the text “webrtc-dscp” in the subject, preferably like this: “[webrtc-dscp] …summary of comment…”. All comments are welcome.

This document is a First Public Working Draft.

Publication as a First Public Working Draft does not imply endorsement by the W3C Membership. This is a draft document and may be updated, replaced or obsoleted by other documents at any time. It is inappropriate to cite this document as other than work in progress.

This document was produced by a group operating under the W3C Patent Policy. W3C maintains a public list of any patent disclosures made in connection with the deliverables of the group; that page also includes instructions for disclosing a patent. An individual who has actual knowledge of a patent which the individual believes contains Essential Claim(s) must disclose the information in accordance with section 6 of the W3C Patent Policy.

This document is governed by the 1 February 2018 W3C Process Document.

1. Introduction

The [WEBRTC] spec defines a "priority" field as part of its RTCRtpEncodingParameters structure, with the possible values "very-low", "low", "medium" and "high".

This specification adds a field to RTCRtpEncodingParameters that allows control over the DSCP markings without affecting local prioritization.

2. IDL specification

partial dictionary RTCRtpEncodingParameters {
    RTCPriorityType networkPriority;  // Note: No default
};

2.1. networkPriority definition

networkPriority has the same effect as priority, except that it only affects the DSCP markings of the generated packets, as described in [RTCWEB-TRANSPORT] section 4.2.

If networkPriority is unset, the DSCP markings of the generated packets are controlled by the priority member.

Conformance

Conformance requirements are expressed with a combination of descriptive assertions and RFC 2119 terminology. The key words “MUST”, “MUST NOT”, “REQUIRED”, “SHALL”, “SHALL NOT”, “SHOULD”, “SHOULD NOT”, “RECOMMENDED”, “MAY”, and “OPTIONAL” in the normative parts of this document are to be interpreted as described in RFC 2119. However, for readability, these words do not appear in all uppercase letters in this specification.

All of the text of this specification is normative except sections explicitly marked as non-normative, examples, and notes. [RFC2119]

Examples in this specification are introduced with the words “for example” or are set apart from the normative text with class="example", like this:

This is an example of an informative example.

Informative notes begin with the word “Note” and are set apart from the normative text with class="note", like this:

Note, this is an informative note.

Index

Terms defined by this specification

Terms defined by reference

References

Normative References

[RFC2119]
S. Bradner. Key words for use in RFCs to Indicate Requirement Levels. March 1997. Best Current Practice. URL: https://tools.ietf.org/html/rfc2119
[WEBRTC]
Adam Bergkvist; et al. WebRTC 1.0: Real-time Communication Between Browsers. 21 June 2018. CR. URL: //www.0b5fq.cn/TR/webrtc/

Informative References

[RTCWEB-TRANSPORT]
H. Alvestrand. Transports for RTCWEB. 31 October 2016. Active Internet-Draft. URL: https://tools.ietf.org/html/draft-ietf-rtcweb-transports

IDL Index

partial dictionary RTCRtpEncodingParameters {
    RTCPriorityType networkPriority;  // Note: No default
};

  • 一年见两次  男孩火车站帮爸爸拔白发 2019-04-16
  • 董明珠代表:建立保护企业人才机制 遏制“恶意挖人”现象 2019-04-16
  • 女子痴迷鹿晗 商场门口对人形立牌拭泪亲吻 2019-04-05
  • 宝鸡现罕见宣统德寿碑 或为沈钧儒叔父沈卫书丹 2019-03-30
  • 《舌尖上的中国》陈晓卿新作《风味人间》即将登场 2019-03-29
  • “黑市”依旧,身份证失效系统推广要加速 2019-03-27
  • “港独”没出路!“梁天琦们”该醒醒了 2019-03-27
  • 公有制结束、高效益之下、就会大量的国有企事业单位的冗员进入社会生产一线。社会运作进入正轨。 2019-03-24
  • 人民日报为人民,70年办报不容易,办报人付出了心血和汗水,记录了中国的发展过程,祝愿办得越来越好! 2019-03-24
  • 【重庆天气】最新重庆今天天气,实时提供重庆气温、空气质量、24小时天气预报、生活指数查询 2019-03-14
  • Netflix欲大力拓展线下业务 考虑收购电影院 2019-03-14
  • 【理上网来喜迎十九大】推动中国经济乘风破浪行稳致远 2019-03-11
  • 我国首部军民融合专业期刊创刊发行 2019-03-07
  • “善款资助副局长儿子留学”真相须尽快落地 2019-03-07
  • 其实逻辑跟简单:小萌们如果能把自己计划好又何至于悲催到要通过混淆所有制形式把别人的钱偷到自己口袋里? 2019-03-06