Correction: RFC 8850 on Controlling Multiple Streams for Telepresence (CLUE) Protocol Data Channel
[Year corrected to "2021" below.] A new Request for Comments is now available in online RFC libraries. RFC 8850 Title: Controlling Multiple Streams for Telepresence (CLUE) Protocol Data Channel Author: C. Holmberg Status: Experimental Stream: IETF Date: January 2021 Mailbox:christer.holmb...@ericsson.com Pages: 9 Updates/Obsoletes/SeeAlso: None I-D Tag:draft-ietf-clue-datachannel-18.txt URL:https://www.rfc-editor.org/info/rfc8850 DOI:10.17487/RFC8850 This document defines how to use the WebRTC data channel mechanism to realize a data channel, referred to as a Controlling Multiple Streams for Telepresence (CLUE) data channel, for transporting CLUE protocol messages between two CLUE entities. This document is a product of the ControLling mUltiple streams for tElepresence Working Group of the IETF. EXPERIMENTAL: This memo defines an Experimental Protocol for the Internet community. It does not specify an Internet standard of any kind. Discussion and suggestions for improvement are requested. Distribution of this memo is unlimited. This announcement is sent to the IETF-Announce and rfc-dist lists. To subscribe or unsubscribe, see https://www.ietf.org/mailman/listinfo/ietf-announce https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see https://www.rfc-editor.org/search For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk Requests for special distribution should be addressed to either the author of the RFC in question, or to rfc-edi...@rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team Association Management Solutions, LLC ___ IETF-Announce mailing list IETF-Announce@ietf.org https://www.ietf.org/mailman/listinfo/ietf-announce
Correction: RFC 8849 on Mapping RTP Streams to Controlling Multiple Streams for Telepresence (CLUE) Media Captures
[Year corrected to "2021" below.] A new Request for Comments is now available in online RFC libraries. RFC 8849 Title: Mapping RTP Streams to Controlling Multiple Streams for Telepresence (CLUE) Media Captures Author: R. Even, J. Lennox Status: Standards Track Stream: IETF Date: January 2021 Mailbox:ron.even@gmail.com, jonathan.len...@8x8.com Pages: 12 Updates/Obsoletes/SeeAlso: None I-D Tag:draft-ietf-clue-rtp-mapping-14.txt URL:https://www.rfc-editor.org/info/rfc8849 DOI:10.17487/RFC8849 This document describes how the Real-time Transport Protocol (RTP) is used in the context of the Controlling Multiple Streams for Telepresence (CLUE) protocol. It also describes the mechanisms and recommended practice for mapping RTP media streams, as defined in the Session Description Protocol (SDP), to CLUE Media Captures and defines a new RTP header extension (CaptureID). This document is a product of the ControLling mUltiple streams for tElepresence Working Group of the IETF. This is now a Proposed Standard. STANDARDS TRACK: This document specifies an Internet Standards Track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the Official Internet Protocol Standards (https://www.rfc-editor.org/standards) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF-Announce and rfc-dist lists. To subscribe or unsubscribe, see https://www.ietf.org/mailman/listinfo/ietf-announce https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see https://www.rfc-editor.org/search For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk Requests for special distribution should be addressed to either the author of the RFC in question, or to rfc-edi...@rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team Association Management Solutions, LLC ___ IETF-Announce mailing list IETF-Announce@ietf.org https://www.ietf.org/mailman/listinfo/ietf-announce
Correction: RFC 8848 on Session Signaling for Controlling Multiple Streams for Telepresence (CLUE)
[Year corrected to "2021" below.] A new Request for Comments is now available in online RFC libraries. RFC 8848 Title: Session Signaling for Controlling Multiple Streams for Telepresence (CLUE) Author: R. Hanton, P. Kyzivat, L. Xiao, C. Groves Status: Experimental Stream: IETF Date: January 2021 Mailbox:rohan...@cisco.com, pkyzi...@alum.mit.edu, lennard.x...@outlook.com, cngroves@gmail.com Pages: 29 Updates/Obsoletes/SeeAlso: None I-D Tag:draft-ietf-clue-signaling-15.txt URL:https://www.rfc-editor.org/info/rfc8848 DOI:10.17487/RFC8848 This document is about Controlling Multiple Streams for Telepresence (CLUE) signaling. It specifies how the CLUE protocol and the CLUE data channel are used in conjunction with each other and with existing signaling mechanisms, such as SIP and the Session Description Protocol (SDP), to produce a telepresence call. This document is a product of the ControLling mUltiple streams for tElepresence Working Group of the IETF. EXPERIMENTAL: This memo defines an Experimental Protocol for the Internet community. It does not specify an Internet standard of any kind. Discussion and suggestions for improvement are requested. Distribution of this memo is unlimited. This announcement is sent to the IETF-Announce and rfc-dist lists. To subscribe or unsubscribe, see https://www.ietf.org/mailman/listinfo/ietf-announce https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see https://www.rfc-editor.org/search For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk Requests for special distribution should be addressed to either the author of the RFC in question, or to rfc-edi...@rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team Association Management Solutions, LLC ___ IETF-Announce mailing list IETF-Announce@ietf.org https://www.ietf.org/mailman/listinfo/ietf-announce
Correction: RFC 8847 on Protocol for Controlling Multiple Streams for Telepresence (CLUE)
[Year corrected to "2021" below.]
A new Request for Comments is now available in online RFC libraries.
RFC 8847
Title: Protocol for Controlling Multiple Streams
for Telepresence (CLUE)
Author: R. Presta,
S P. Romano
Status: Experimental
Stream: IETF
Date: January 2021
Mailbox:roberta.pre...@unina.it,
sprom...@unina.it
Pages: 62
Updates/Obsoletes/SeeAlso: None
I-D Tag:draft-ietf-clue-protocol-19.txt
URL:https://www.rfc-editor.org/info/rfc8847
DOI:10.17487/RFC8847
The Controlling Multiple Streams for Telepresence (CLUE) protocol is
an application protocol conceived for the description and negotiation
of a telepresence session. The design of the CLUE protocol takes
into account the requirements and the framework defined within the
IETF CLUE Working Group. A companion document, RFC 8848, delves into
CLUE signaling details as well as the SIP / Session Description
Protocol (SDP) session establishment phase. CLUE messages flow over
the CLUE data channel, based on reliable and ordered SCTP-over-DTLS
transport. ("SCTP" stands for "Stream Control Transmission
Protocol".) Message details, together with the behavior of CLUE
Participants acting as Media Providers and/or Media Consumers, are
herein discussed.
This document is a product of the ControLling mUltiple streams for tElepresence
Working Group of the IETF.
EXPERIMENTAL: This memo defines an Experimental Protocol for the
Internet community. It does not specify an Internet standard of any
kind. Discussion and suggestions for improvement are requested.
Distribution of this memo is unlimited.
This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
https://www.ietf.org/mailman/listinfo/ietf-announce
https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk
Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-edi...@rfc-editor.org. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
The RFC Editor Team
Association Management Solutions, LLC
___
IETF-Announce mailing list
IETF-Announce@ietf.org
https://www.ietf.org/mailman/listinfo/ietf-announce
Correction: RFC 8846 on An XML Schema for the Controlling Multiple Streams for Telepresence (CLUE) Data Model
[Year corrected to "2021" below.] A new Request for Comments is now available in online RFC libraries. RFC 8846 Title: An XML Schema for the Controlling Multiple Streams for Telepresence (CLUE) Data Model Author: R. Presta, S P. Romano Status: Standards Track Stream: IETF Date: January 2021 Mailbox:roberta.pre...@unina.it, sprom...@unina.it Pages: 66 Updates/Obsoletes/SeeAlso: None I-D Tag:draft-ietf-clue-data-model-schema-17.txt URL:https://www.rfc-editor.org/info/rfc8846 DOI:10.17487/RFC8846 This document provides an XML schema file for the definition of CLUE data model types. The term "CLUE" stands for "Controlling Multiple Streams for Telepresence" and is the name of the IETF working group in which this document, as well as other companion documents, has been developed. The document defines a coherent structure for information associated with the description of a telepresence scenario. This document is a product of the ControLling mUltiple streams for tElepresence Working Group of the IETF. This is now a Proposed Standard. STANDARDS TRACK: This document specifies an Internet Standards Track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the Official Internet Protocol Standards (https://www.rfc-editor.org/standards) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF-Announce and rfc-dist lists. To subscribe or unsubscribe, see https://www.ietf.org/mailman/listinfo/ietf-announce https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see https://www.rfc-editor.org/search For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk Requests for special distribution should be addressed to either the author of the RFC in question, or to rfc-edi...@rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team Association Management Solutions, LLC ___ IETF-Announce mailing list IETF-Announce@ietf.org https://www.ietf.org/mailman/listinfo/ietf-announce
Correction: RFC 8845 on Framework for Telepresence Multi-Streams
[Year corrected to "2021" below.] A new Request for Comments is now available in online RFC libraries. RFC 8845 Title: Framework for Telepresence Multi-Streams Author: M. Duckworth, Ed., A. Pepperell, S. Wenger Status: Standards Track Stream: IETF Date: January 2021 Mailbox:mrduck...@outlook.com, apepp...@gmail.com, st...@stewe.org Pages: 61 Updates/Obsoletes/SeeAlso: None I-D Tag:draft-ietf-clue-framework-25.txt URL:https://www.rfc-editor.org/info/rfc8845 DOI:10.17487/RFC8845 This document defines a framework for a protocol to enable devices in a telepresence conference to interoperate. The protocol enables communication of information about multiple media streams so a sending system and receiving system can make reasonable decisions about transmitting, selecting, and rendering the media streams. This protocol is used in addition to SIP signaling and Session Description Protocol (SDP) negotiation for setting up a telepresence session. This document is a product of the ControLling mUltiple streams for tElepresence Working Group of the IETF. This is now a Proposed Standard. STANDARDS TRACK: This document specifies an Internet Standards Track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the Official Internet Protocol Standards (https://www.rfc-editor.org/standards) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF-Announce and rfc-dist lists. To subscribe or unsubscribe, see https://www.ietf.org/mailman/listinfo/ietf-announce https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see https://www.rfc-editor.org/search For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk Requests for special distribution should be addressed to either the author of the RFC in question, or to rfc-edi...@rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team Association Management Solutions, LLC ___ IETF-Announce mailing list IETF-Announce@ietf.org https://www.ietf.org/mailman/listinfo/ietf-announce
Correction: RFC 8844 on Unknown Key-Share Attacks on Uses of TLS with the Session Description Protocol (SDP)
[Year corrected to "2021" below.] A new Request for Comments is now available in online RFC libraries. RFC 8844 Title: Unknown Key-Share Attacks on Uses of TLS with the Session Description Protocol (SDP) Author: M. Thomson, E. Rescorla Status: Standards Track Stream: IETF Date: January 2021 Mailbox:m...@lowentropy.net, e...@rtfm.com Pages: 17 Updates:RFC 8122 I-D Tag:draft-ietf-mmusic-sdp-uks-07.txt URL:https://www.rfc-editor.org/info/rfc8844 DOI:10.17487/RFC8844 This document describes unknown key-share attacks on the use of Datagram Transport Layer Security for the Secure Real-Time Transport Protocol (DTLS-SRTP). Similar attacks are described on the use of DTLS-SRTP with the identity bindings used in Web Real-Time Communications (WebRTC) and SIP identity. These attacks are difficult to mount, but they cause a victim to be misled about the identity of a communicating peer. This document defines mitigation techniques that implementations of RFC 8122 are encouraged to deploy. This document is a product of the Multiparty Multimedia Session Control Working Group of the IETF. This is now a Proposed Standard. STANDARDS TRACK: This document specifies an Internet Standards Track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the Official Internet Protocol Standards (https://www.rfc-editor.org/standards) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF-Announce and rfc-dist lists. To subscribe or unsubscribe, see https://www.ietf.org/mailman/listinfo/ietf-announce https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see https://www.rfc-editor.org/search For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk Requests for special distribution should be addressed to either the author of the RFC in question, or to rfc-edi...@rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team Association Management Solutions, LLC ___ IETF-Announce mailing list IETF-Announce@ietf.org https://www.ietf.org/mailman/listinfo/ietf-announce
Correction: RFC 8842 on Session Description Protocol (SDP) Offer/Answer Considerations for Datagram Transport Layer Security (DTLS) and Transport Layer Security (TLS)
[Year corrected to "2021" below.] A new Request for Comments is now available in online RFC libraries. RFC 8842 Title: Session Description Protocol (SDP) Offer/Answer Considerations for Datagram Transport Layer Security (DTLS) and Transport Layer Security (TLS) Author: C. Holmberg, R. Shpount Status: Standards Track Stream: IETF Date: January 2021 Mailbox:christer.holmb...@ericsson.com, rshpo...@turbobridge.com Pages: 19 Updates:RFC 5763, RFC 7345 I-D Tag:draft-ietf-mmusic-dtls-sdp-32.txt URL:https://www.rfc-editor.org/info/rfc8842 DOI:10.17487/RFC8842 This document defines the Session Description Protocol (SDP) offer/answer procedures for negotiating and establishing a Datagram Transport Layer Security (DTLS) association. The document also defines the criteria for when a new DTLS association must be established. The document updates RFCs 5763 and 7345 by replacing common SDP offer/answer procedures with a reference to this specification. This document defines a new SDP media-level attribute, "tls-id". This document also defines how the "tls-id" attribute can be used for negotiating and establishing a Transport Layer Security (TLS) connection, in conjunction with the procedures in RFCs 4145 and 8122. This document is a product of the Multiparty Multimedia Session Control Working Group of the IETF. This is now a Proposed Standard. STANDARDS TRACK: This document specifies an Internet Standards Track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the Official Internet Protocol Standards (https://www.rfc-editor.org/standards) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF-Announce and rfc-dist lists. To subscribe or unsubscribe, see https://www.ietf.org/mailman/listinfo/ietf-announce https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see https://www.rfc-editor.org/search For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk Requests for special distribution should be addressed to either the author of the RFC in question, or to rfc-edi...@rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team Association Management Solutions, LLC ___ IETF-Announce mailing list IETF-Announce@ietf.org https://www.ietf.org/mailman/listinfo/ietf-announce
Correction: RFC 8841 on Session Description Protocol (SDP) Offer/Answer Procedures for Stream Control Transmission Protocol (SCTP) over Datagram Transport Layer Security (DTLS) Transport
[Year corrected to "2021" below.] A new Request for Comments is now available in online RFC libraries. RFC 8841 Title: Session Description Protocol (SDP) Offer/Answer Procedures for Stream Control Transmission Protocol (SCTP) over Datagram Transport Layer Security (DTLS) Transport Author: C. Holmberg, R. Shpount, S. Loreto, G. Camarillo Status: Standards Track Stream: IETF Date: January 2021 Mailbox:christer.holmb...@ericsson.com, rshpo...@turbobridge.com, salvatore.lor...@ericsson.com, gonzalo.camari...@ericsson.com Pages: 21 Updates/Obsoletes/SeeAlso: None I-D Tag:draft-ietf-mmusic-sctp-sdp-26.txt URL:https://www.rfc-editor.org/info/rfc8841 DOI:10.17487/RFC8841 The Stream Control Transmission Protocol (SCTP) is a transport protocol used to establish associations between two endpoints. RFC 8261 specifies how SCTP can be used on top of the Datagram Transport Layer Security (DTLS) protocol, which is referred to as SCTP-over-DTLS. This specification defines the following new Session Description Protocol (SDP) protocol identifiers (proto values): "UDP/DTLS/SCTP" and "TCP/DTLS/SCTP". This specification also specifies how to use the new proto values with the SDP offer/answer mechanism for negotiating SCTP-over-DTLS associations. This document is a product of the Multiparty Multimedia Session Control Working Group of the IETF. This is now a Proposed Standard. STANDARDS TRACK: This document specifies an Internet Standards Track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the Official Internet Protocol Standards (https://www.rfc-editor.org/standards) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF-Announce and rfc-dist lists. To subscribe or unsubscribe, see https://www.ietf.org/mailman/listinfo/ietf-announce https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see https://www.rfc-editor.org/search For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk Requests for special distribution should be addressed to either the author of the RFC in question, or to rfc-edi...@rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team Association Management Solutions, LLC ___ IETF-Announce mailing list IETF-Announce@ietf.org https://www.ietf.org/mailman/listinfo/ietf-announce
Correction: RFC 8840 on A Session Initiation Protocol (SIP) Usage for Incremental Provisioning of Candidates for the Interactive Connectivity Establishment (Trickle ICE)
[Year corrected to "2021" below.] A new Request for Comments is now available in online RFC libraries. RFC 8840 Title: A Session Initiation Protocol (SIP) Usage for Incremental Provisioning of Candidates for the Interactive Connectivity Establishment (Trickle ICE) Author: E. Ivov, T. Stach, E. Marocco, C. Holmberg Status: Standards Track Stream: IETF Date: January 2021 Mailbox:em...@jitsi.org, thomass.st...@gmail.com, enrico.maro...@telecomitalia.it, christer.holmb...@ericsson.com Pages: 34 Updates/Obsoletes/SeeAlso: None I-D Tag:draft-ietf-mmusic-trickle-ice-sip-18.txt URL:https://www.rfc-editor.org/info/rfc8840 DOI:10.17487/RFC8840 The Interactive Connectivity Establishment (ICE) protocol describes a Network Address Translator (NAT) traversal mechanism for UDP-based multimedia sessions established with the Offer/Answer model. The ICE extension for Incremental Provisioning of Candidates (Trickle ICE) defines a mechanism that allows ICE Agents to shorten session establishment delays by making the candidate gathering and connectivity checking phases of ICE non-blocking and by executing them in parallel. This document defines usage semantics for Trickle ICE with the Session Initiation Protocol (SIP). The document also defines a new SIP Info Package to support this usage together with the corresponding media type. Additionally, a new Session Description Protocol (SDP) "end-of-candidates" attribute and a new SIP option tag "trickle-ice" are defined. This document is a product of the Multiparty Multimedia Session Control Working Group of the IETF. This is now a Proposed Standard. STANDARDS TRACK: This document specifies an Internet Standards Track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the Official Internet Protocol Standards (https://www.rfc-editor.org/standards) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF-Announce and rfc-dist lists. To subscribe or unsubscribe, see https://www.ietf.org/mailman/listinfo/ietf-announce https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see https://www.rfc-editor.org/search For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk Requests for special distribution should be addressed to either the author of the RFC in question, or to rfc-edi...@rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team Association Management Solutions, LLC ___ IETF-Announce mailing list IETF-Announce@ietf.org https://www.ietf.org/mailman/listinfo/ietf-announce
Correction: RFC 8839 on Session Description Protocol (SDP) Offer/Answer Procedures for Interactive Connectivity Establishment (ICE)
[Year corrected to "2021" below.] A new Request for Comments is now available in online RFC libraries. RFC 8839 Title: Session Description Protocol (SDP) Offer/Answer Procedures for Interactive Connectivity Establishment (ICE) Author: M. Petit-Huguenin, S. Nandakumar, C. Holmberg, A. Keränen, R. Shpount Status: Standards Track Stream: IETF Date: January 2021 Mailbox:m...@petit-huguenin.org, snand...@cisco.com, christer.holmb...@ericsson.com, ari.kera...@ericsson.com, rshpo...@turbobridge.com Pages: 38 Obsoletes: RFC 5245, RFC 6336 I-D Tag:draft-ietf-mmusic-ice-sip-sdp-39.txt URL:https://www.rfc-editor.org/info/rfc8839 DOI:10.17487/RFC8839 This document describes Session Description Protocol (SDP) Offer/Answer procedures for carrying out Interactive Connectivity Establishment (ICE) between the agents. This document obsoletes RFCs 5245 and 6336. This document is a product of the Multiparty Multimedia Session Control Working Group of the IETF. This is now a Proposed Standard. STANDARDS TRACK: This document specifies an Internet Standards Track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the Official Internet Protocol Standards (https://www.rfc-editor.org/standards) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF-Announce and rfc-dist lists. To subscribe or unsubscribe, see https://www.ietf.org/mailman/listinfo/ietf-announce https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see https://www.rfc-editor.org/search For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk Requests for special distribution should be addressed to either the author of the RFC in question, or to rfc-edi...@rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team Association Management Solutions, LLC ___ IETF-Announce mailing list IETF-Announce@ietf.org https://www.ietf.org/mailman/listinfo/ietf-announce
Correction: RFC 8838 on Trickle ICE: Incremental Provisioning of Candidates for the Interactive Connectivity Establishment (ICE) Protocol
[Year corrected to "2021" below.] A new Request for Comments is now available in online RFC libraries. RFC 8838 Title: Trickle ICE: Incremental Provisioning of Candidates for the Interactive Connectivity Establishment (ICE) Protocol Author: E. Ivov, J. Uberti, P. Saint-Andre Status: Standards Track Stream: IETF Date: January 2021 Mailbox:em...@jitsi.org, jus...@uberti.name, stpe...@mozilla.com Pages: 22 Updates/Obsoletes/SeeAlso: None I-D Tag:draft-ietf-ice-trickle-21.txt URL:https://www.rfc-editor.org/info/rfc8838 DOI:10.17487/RFC8838 This document describes "Trickle ICE", an extension to the Interactive Connectivity Establishment (ICE) protocol that enables ICE agents to begin connectivity checks while they are still gathering candidates, by incrementally exchanging candidates over time instead of all at once. This method can considerably accelerate the process of establishing a communication session. This document is a product of the Interactive Connectivity Establishment Working Group of the IETF. This is now a Proposed Standard. STANDARDS TRACK: This document specifies an Internet Standards Track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the Official Internet Protocol Standards (https://www.rfc-editor.org/standards) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF-Announce and rfc-dist lists. To subscribe or unsubscribe, see https://www.ietf.org/mailman/listinfo/ietf-announce https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see https://www.rfc-editor.org/search For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk Requests for special distribution should be addressed to either the author of the RFC in question, or to rfc-edi...@rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team Association Management Solutions, LLC ___ IETF-Announce mailing list IETF-Announce@ietf.org https://www.ietf.org/mailman/listinfo/ietf-announce
RFC 8873 on Message Session Relay Protocol (MSRP) over Data Channels
A new Request for Comments is now available in online RFC libraries. RFC 8873 Title: Message Session Relay Protocol (MSRP) over Data Channels Author: JM. Recio, Ed., C. Holmberg Status: Standards Track Stream: IETF Date: January 2021 Mailbox:j...@ch3m4.com, christer.holmb...@ericsson.com Pages: 17 Updates:RFC 4975 I-D Tag:draft-ietf-mmusic-msrp-usage-data-channel-24.txt URL:https://www.rfc-editor.org/info/rfc8873 DOI:10.17487/RFC8873 This document specifies how a Web Real-Time Communication (WebRTC) data channel can be used as a transport mechanism for the Message Session Relay Protocol (MSRP) and how the Session Description Protocol (SDP) offer/answer mechanism can be used to negotiate such a data channel, referred to as an MSRP data channel. Two network configurations are supported: the connection of two MSRP data channel endpoints; and a gateway configuration, which connects an MSRP data channel endpoint with an MSRP endpoint that uses either TCP or TLS. This document updates RFC 4975. This document is a product of the Multiparty Multimedia Session Control Working Group of the IETF. This is now a Proposed Standard. STANDARDS TRACK: This document specifies an Internet Standards Track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the Official Internet Protocol Standards (https://www.rfc-editor.org/standards) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF-Announce and rfc-dist lists. To subscribe or unsubscribe, see https://www.ietf.org/mailman/listinfo/ietf-announce https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see https://www.rfc-editor.org/search For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk Requests for special distribution should be addressed to either the author of the RFC in question, or to rfc-edi...@rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team Association Management Solutions, LLC ___ IETF-Announce mailing list IETF-Announce@ietf.org https://www.ietf.org/mailman/listinfo/ietf-announce
RFC 8872 on Guidelines for Using the Multiplexing Features of RTP to Support Multiple Media Streams
A new Request for Comments is now available in online RFC libraries. RFC 8872 Title: Guidelines for Using the Multiplexing Features of RTP to Support Multiple Media Streams Author: M. Westerlund, B. Burman, C. Perkins, H. Alvestrand, R. Even Status: Informational Stream: IETF Date: January 2021 Mailbox:magnus.westerl...@ericsson.com, bo.bur...@ericsson.com, c...@csperkins.org, har...@alvestrand.no, ron.even@gmail.com Pages: 36 Updates/Obsoletes/SeeAlso: None I-D Tag:draft-ietf-avtcore-multiplex-guidelines-12.txt URL:https://www.rfc-editor.org/info/rfc8872 DOI:10.17487/RFC8872 The Real-time Transport Protocol (RTP) is a flexible protocol that can be used in a wide range of applications, networks, and system topologies. That flexibility makes for wide applicability but can complicate the application design process. One particular design question that has received much attention is how to support multiple media streams in RTP. This memo discusses the available options and design trade-offs, and provides guidelines on how to use the multiplexing features of RTP to support multiple media streams. This document is a product of the Audio/Video Transport Core Maintenance Working Group of the IETF. INFORMATIONAL: This memo provides information for the Internet community. It does not specify an Internet standard of any kind. Distribution of this memo is unlimited. This announcement is sent to the IETF-Announce and rfc-dist lists. To subscribe or unsubscribe, see https://www.ietf.org/mailman/listinfo/ietf-announce https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see https://www.rfc-editor.org/search For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk Requests for special distribution should be addressed to either the author of the RFC in question, or to rfc-edi...@rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team Association Management Solutions, LLC ___ IETF-Announce mailing list IETF-Announce@ietf.org https://www.ietf.org/mailman/listinfo/ietf-announce
RFC 8871 on A Solution Framework for Private Media in Privacy-Enhanced RTP Conferencing (PERC)
A new Request for Comments is now available in online RFC libraries. RFC 8871 Title: A Solution Framework for Private Media in Privacy-Enhanced RTP Conferencing (PERC) Author: P. Jones, D. Benham, C. Groves Status: Standards Track Stream: IETF Date: January 2021 Mailbox:pau...@packetizer.com, daben...@gmail.com, cngroves@gmail.com Pages: 23 Updates/Obsoletes/SeeAlso: None I-D Tag:draft-ietf-perc-private-media-framework-12.txt URL:https://www.rfc-editor.org/info/rfc8871 DOI:10.17487/RFC8871 This document describes a solution framework for ensuring that media confidentiality and integrity are maintained end to end within the context of a switched conferencing environment where Media Distributors are not trusted with the end-to-end media encryption keys. The solution builds upon existing security mechanisms defined for the Real-time Transport Protocol (RTP). This document is a product of the Privacy Enhanced RTP Conferencing Working Group of the IETF. This is now a Proposed Standard. STANDARDS TRACK: This document specifies an Internet Standards Track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the Official Internet Protocol Standards (https://www.rfc-editor.org/standards) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF-Announce and rfc-dist lists. To subscribe or unsubscribe, see https://www.ietf.org/mailman/listinfo/ietf-announce https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see https://www.rfc-editor.org/search For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk Requests for special distribution should be addressed to either the author of the RFC in question, or to rfc-edi...@rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team Association Management Solutions, LLC ___ IETF-Announce mailing list IETF-Announce@ietf.org https://www.ietf.org/mailman/listinfo/ietf-announce
RFC 8870 on Encrypted Key Transport for DTLS and Secure RTP
A new Request for Comments is now available in online RFC libraries. RFC 8870 Title: Encrypted Key Transport for DTLS and Secure RTP Author: C. Jennings, J. Mattsson, D. McGrew, D. Wing, F. Andreasen Status: Standards Track Stream: IETF Date: January 2021 Mailbox:flu...@iii.ca, john.matts...@ericsson.com, mcg...@cisco.com, dwing-i...@fuggles.com, fandr...@cisco.com Pages: 22 Updates/Obsoletes/SeeAlso: None I-D Tag:draft-ietf-perc-srtp-ekt-diet-13.txt URL:https://www.rfc-editor.org/info/rfc8870 DOI:10.17487/RFC8870 Encrypted Key Transport (EKT) is an extension to DTLS (Datagram Transport Layer Security) and the Secure Real-time Transport Protocol (SRTP) that provides for the secure transport of SRTP master keys, rollover counters, and other information within SRTP. This facility enables SRTP for decentralized conferences by distributing a common key to all of the conference endpoints. This document is a product of the Privacy Enhanced RTP Conferencing Working Group of the IETF. This is now a Proposed Standard. STANDARDS TRACK: This document specifies an Internet Standards Track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the Official Internet Protocol Standards (https://www.rfc-editor.org/standards) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF-Announce and rfc-dist lists. To subscribe or unsubscribe, see https://www.ietf.org/mailman/listinfo/ietf-announce https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see https://www.rfc-editor.org/search For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk Requests for special distribution should be addressed to either the author of the RFC in question, or to rfc-edi...@rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team Association Management Solutions, LLC ___ IETF-Announce mailing list IETF-Announce@ietf.org https://www.ietf.org/mailman/listinfo/ietf-announce
RFC 8869 on Evaluation Test Cases for Interactive Real-Time Media over Wireless Networks
A new Request for Comments is now available in online RFC libraries. RFC 8869 Title: Evaluation Test Cases for Interactive Real-Time Media over Wireless Networks Author: Z. Sarker, X. Zhu, J. Fu Status: Informational Stream: IETF Date: January 2021 Mailbox:zaheduzzaman.sar...@ericsson.com, xiaoq...@cisco.com, jia...@cisco.com Pages: 19 Updates/Obsoletes/SeeAlso: None I-D Tag:draft-ietf-rmcat-wireless-tests-11.txt URL:https://www.rfc-editor.org/info/rfc8869 DOI:10.17487/RFC8869 The Real-time Transport Protocol (RTP) is a common transport choice for interactive multimedia communication applications. The performance of these applications typically depends on a well-functioning congestion control algorithm. To ensure a seamless and robust user experience, a well-designed RTP-based congestion control algorithm should work well across all access network types. This document describes test cases for evaluating performances of candidate congestion control algorithms over cellular and Wi-Fi networks. This document is a product of the RTP Media Congestion Avoidance Techniques Working Group of the IETF. INFORMATIONAL: This memo provides information for the Internet community. It does not specify an Internet standard of any kind. Distribution of this memo is unlimited. This announcement is sent to the IETF-Announce and rfc-dist lists. To subscribe or unsubscribe, see https://www.ietf.org/mailman/listinfo/ietf-announce https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see https://www.rfc-editor.org/search For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk Requests for special distribution should be addressed to either the author of the RFC in question, or to rfc-edi...@rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team Association Management Solutions, LLC ___ IETF-Announce mailing list IETF-Announce@ietf.org https://www.ietf.org/mailman/listinfo/ietf-announce
RFC 8863 on Interactive Connectivity Establishment Patiently Awaiting Connectivity (ICE PAC)
A new Request for Comments is now available in online RFC libraries. RFC 8863 Title: Interactive Connectivity Establishment Patiently Awaiting Connectivity (ICE PAC) Author: C. Holmberg, J. Uberti Status: Standards Track Stream: IETF Date: January 2021 Mailbox:christer.holmb...@ericsson.com, jus...@uberti.name Pages: 6 Updates:RFC 8445, RFC 8838 I-D Tag:draft-ietf-ice-pac-06.txt URL:https://www.rfc-editor.org/info/rfc8863 DOI:10.17487/RFC8863 During the process of establishing peer-to-peer connectivity, Interactive Connectivity Establishment (ICE) agents can encounter situations where they have no candidate pairs to check, and, as a result, conclude that ICE processing has failed. However, because additional candidate pairs can be discovered during ICE processing, declaring failure at this point may be premature. This document discusses when these situations can occur. This document updates RFCs 8445 and 8838 by requiring that an ICE agent wait a minimum amount of time before declaring ICE failure, even if there are no candidate pairs left to check. This document is a product of the Interactive Connectivity Establishment Working Group of the IETF. This is now a Proposed Standard. STANDARDS TRACK: This document specifies an Internet Standards Track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the Official Internet Protocol Standards (https://www.rfc-editor.org/standards) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF-Announce and rfc-dist lists. To subscribe or unsubscribe, see https://www.ietf.org/mailman/listinfo/ietf-announce https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see https://www.rfc-editor.org/search For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk Requests for special distribution should be addressed to either the author of the RFC in question, or to rfc-edi...@rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team Association Management Solutions, LLC ___ IETF-Announce mailing list IETF-Announce@ietf.org https://www.ietf.org/mailman/listinfo/ietf-announce
BCP 228, RFC 8862 on Best Practices for Securing RTP Media Signaled with SIP
A new Request for Comments is now available in online RFC libraries. BCP 228 RFC 8862 Title: Best Practices for Securing RTP Media Signaled with SIP Author: J. Peterson, R. Barnes, R. Housley Status: Best Current Practice Stream: IETF Date: January 2021 Mailbox:jon.peterson@team.neustar, r...@ipv.sx, hous...@vigilsec.com Pages: 12 See Also: BCP 228 I-D Tag:draft-ietf-sipbrandy-rtpsec-08.txt URL:https://www.rfc-editor.org/info/rfc8862 DOI:10.17487/RFC8862 Although the Session Initiation Protocol (SIP) includes a suite of security services that has been expanded by numerous specifications over the years, there is no single place that explains how to use SIP to establish confidential media sessions. Additionally, existing mechanisms have some feature gaps that need to be identified and resolved in order for them to address the pervasive monitoring threat model. This specification describes best practices for negotiating confidential media with SIP, including a comprehensive protection solution that binds the media layer to SIP layer identities. This document is a product of the SIP Best-practice Recommendations Against Network Dangers to privacY Working Group of the IETF. BCP: This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. Distribution of this memo is unlimited. This announcement is sent to the IETF-Announce and rfc-dist lists. To subscribe or unsubscribe, see https://www.ietf.org/mailman/listinfo/ietf-announce https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see https://www.rfc-editor.org/search For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk Requests for special distribution should be addressed to either the author of the RFC in question, or to rfc-edi...@rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team Association Management Solutions, LLC ___ IETF-Announce mailing list IETF-Announce@ietf.org https://www.ietf.org/mailman/listinfo/ietf-announce
RFC 8861 on Sending Multiple RTP Streams in a Single RTP Session: Grouping RTP Control Protocol (RTCP) Reception Statistics and Other Feedback
A new Request for Comments is now available in online RFC libraries. RFC 8861 Title: Sending Multiple RTP Streams in a Single RTP Session: Grouping RTP Control Protocol (RTCP) Reception Statistics and Other Feedback Author: J. Lennox, M. Westerlund, Q. Wu, C. Perkins Status: Standards Track Stream: IETF Date: January 2021 Mailbox:jonathan.len...@8x8.com, magnus.westerl...@ericsson.com, bill...@huawei.com, c...@csperkins.org Pages: 16 Updates/Obsoletes/SeeAlso: None I-D Tag:draft-ietf-avtcore-rtp-multi-stream-optimisation-12.txt URL:https://www.rfc-editor.org/info/rfc8861 DOI:10.17487/RFC8861 RTP allows multiple RTP streams to be sent in a single session but requires each Synchronization Source (SSRC) to send RTP Control Protocol (RTCP) reception quality reports for every other SSRC visible in the session. This causes the number of RTCP reception reports to grow with the number of SSRCs, rather than the number of endpoints. In many cases, most of these RTCP reception reports are unnecessary, since all SSRCs of an endpoint are normally co-located and see the same reception quality. This memo defines a Reporting Group extension to RTCP to reduce the reporting overhead in such scenarios. This document is a product of the Audio/Video Transport Core Maintenance Working Group of the IETF. This is now a Proposed Standard. STANDARDS TRACK: This document specifies an Internet Standards Track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the Official Internet Protocol Standards (https://www.rfc-editor.org/standards) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF-Announce and rfc-dist lists. To subscribe or unsubscribe, see https://www.ietf.org/mailman/listinfo/ietf-announce https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see https://www.rfc-editor.org/search For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk Requests for special distribution should be addressed to either the author of the RFC in question, or to rfc-edi...@rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team Association Management Solutions, LLC ___ IETF-Announce mailing list IETF-Announce@ietf.org https://www.ietf.org/mailman/listinfo/ietf-announce
RFC 8860 on Sending Multiple Types of Media in a Single RTP Session
A new Request for Comments is now available in online RFC libraries. RFC 8860 Title: Sending Multiple Types of Media in a Single RTP Session Author: M. Westerlund, C. Perkins, J. Lennox Status: Standards Track Stream: IETF Date: January 2021 Mailbox:magnus.westerl...@ericsson.com, c...@csperkins.org, jonathan.len...@8x8.com Pages: 15 Updates:RFC 3550, RFC 3551 I-D Tag:draft-ietf-avtcore-multi-media-rtp-session-13.txt URL:https://www.rfc-editor.org/info/rfc8860 DOI:10.17487/RFC8860 This document specifies how an RTP session can contain RTP streams with media from multiple media types such as audio, video, and text. This has been restricted by the RTP specifications (RFCs 3550 and 3551), and thus this document updates RFCs 3550 and 3551 to enable this behaviour for applications that satisfy the applicability for using multiple media types in a single RTP session. This document is a product of the Audio/Video Transport Core Maintenance Working Group of the IETF. This is now a Proposed Standard. STANDARDS TRACK: This document specifies an Internet Standards Track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the Official Internet Protocol Standards (https://www.rfc-editor.org/standards) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF-Announce and rfc-dist lists. To subscribe or unsubscribe, see https://www.ietf.org/mailman/listinfo/ietf-announce https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see https://www.rfc-editor.org/search For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk Requests for special distribution should be addressed to either the author of the RFC in question, or to rfc-edi...@rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team Association Management Solutions, LLC ___ IETF-Announce mailing list IETF-Announce@ietf.org https://www.ietf.org/mailman/listinfo/ietf-announce
RFC 8859 on A Framework for Session Description Protocol (SDP) Attributes When Multiplexing
A new Request for Comments is now available in online RFC libraries. RFC 8859 Title: A Framework for Session Description Protocol (SDP) Attributes When Multiplexing Author: S. Nandakumar Status: Standards Track Stream: IETF Date: January 2021 Mailbox:snand...@cisco.com Pages: 82 Updates/Obsoletes/SeeAlso: None I-D Tag:draft-ietf-mmusic-sdp-mux-attributes-19.txt URL:https://www.rfc-editor.org/info/rfc8859 DOI:10.17487/RFC8859 The purpose of this specification is to provide a framework for analyzing the multiplexing characteristics of Session Description Protocol (SDP) attributes when SDP is used to negotiate the usage of a single 5-tuple for sending and receiving media associated with multiple media descriptions. This specification also categorizes the existing SDP attributes based on the framework described herein. This document is a product of the Multiparty Multimedia Session Control Working Group of the IETF. This is now a Proposed Standard. STANDARDS TRACK: This document specifies an Internet Standards Track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the Official Internet Protocol Standards (https://www.rfc-editor.org/standards) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF-Announce and rfc-dist lists. To subscribe or unsubscribe, see https://www.ietf.org/mailman/listinfo/ietf-announce https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see https://www.rfc-editor.org/search For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk Requests for special distribution should be addressed to either the author of the RFC in question, or to rfc-edi...@rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team Association Management Solutions, LLC ___ IETF-Announce mailing list IETF-Announce@ietf.org https://www.ietf.org/mailman/listinfo/ietf-announce
RFC 8858 on Indicating Exclusive Support of RTP and RTP Control Protocol (RTCP) Multiplexing Using the Session Description Protocol (SDP)
A new Request for Comments is now available in online RFC libraries. RFC 8858 Title: Indicating Exclusive Support of RTP and RTP Control Protocol (RTCP) Multiplexing Using the Session Description Protocol (SDP) Author: C. Holmberg Status: Standards Track Stream: IETF Date: January 2021 Mailbox:christer.holmb...@ericsson.com Pages: 9 Updates:RFC 5761 I-D Tag:draft-ietf-mmusic-mux-exclusive-12.txt URL:https://www.rfc-editor.org/info/rfc8858 DOI:10.17487/RFC8858 This document defines a new Session Description Protocol (SDP) media-level attribute, 'rtcp-mux-only', that can be used by an endpoint to indicate exclusive support of RTP and RTP Control Protocol (RTCP) multiplexing. The document also updates RFC 5761 by clarifying that an offerer can use a mechanism to indicate that it is not able to send and receive RTCP on separate ports. This document is a product of the Multiparty Multimedia Session Control Working Group of the IETF. This is now a Proposed Standard. STANDARDS TRACK: This document specifies an Internet Standards Track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the Official Internet Protocol Standards (https://www.rfc-editor.org/standards) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF-Announce and rfc-dist lists. To subscribe or unsubscribe, see https://www.ietf.org/mailman/listinfo/ietf-announce https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see https://www.rfc-editor.org/search For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk Requests for special distribution should be addressed to either the author of the RFC in question, or to rfc-edi...@rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team Association Management Solutions, LLC ___ IETF-Announce mailing list IETF-Announce@ietf.org https://www.ietf.org/mailman/listinfo/ietf-announce
RFC 8827 on WebRTC Security Architecture
A new Request for Comments is now available in online RFC libraries. RFC 8827 Title: WebRTC Security Architecture Author: E. Rescorla Status: Standards Track Stream: IETF Date: January 2021 Mailbox:e...@rtfm.com Pages: 35 Updates/Obsoletes/SeeAlso: None I-D Tag:draft-ietf-rtcweb-security-arch-20.txt URL:https://www.rfc-editor.org/info/rfc8827 DOI:10.17487/RFC8827 This document defines the security architecture for WebRTC, a protocol suite intended for use with real-time applications that can be deployed in browsers -- "real-time communication on the Web". This document is a product of the Real-Time Communication in WEB-browsers Working Group of the IETF. This is now a Proposed Standard. STANDARDS TRACK: This document specifies an Internet Standards Track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the Official Internet Protocol Standards (https://www.rfc-editor.org/standards) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF-Announce and rfc-dist lists. To subscribe or unsubscribe, see https://www.ietf.org/mailman/listinfo/ietf-announce https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see https://www.rfc-editor.org/search For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk Requests for special distribution should be addressed to either the author of the RFC in question, or to rfc-edi...@rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team Association Management Solutions, LLC ___ IETF-Announce mailing list IETF-Announce@ietf.org https://www.ietf.org/mailman/listinfo/ietf-announce
RFC 8837 on Differentiated Services Code Point (DSCP) Packet Markings for WebRTC QoS
A new Request for Comments is now available in online RFC libraries. RFC 8837 Title: Differentiated Services Code Point (DSCP) Packet Markings for WebRTC QoS Author: P. Jones, S. Dhesikan, C. Jennings, D. Druta Status: Standards Track Stream: IETF Date: January 2021 Mailbox:pau...@packetizer.com, sdhesi...@gmail.com, flu...@cisco.com, dd5...@att.com Pages: 9 Updates/Obsoletes/SeeAlso: None I-D Tag:draft-ietf-tsvwg-rtcweb-qos-18.txt URL:https://www.rfc-editor.org/info/rfc8837 DOI:10.17487/RFC8837 Networks can provide different forwarding treatments for individual packets based on Differentiated Services Code Point (DSCP) values on a per-hop basis. This document provides the recommended DSCP values for web browsers to use for various classes of Web Real-Time Communication (WebRTC) traffic. This document is a product of the Transport Area Working Group Working Group of the IETF. This is now a Proposed Standard. STANDARDS TRACK: This document specifies an Internet Standards Track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the Official Internet Protocol Standards (https://www.rfc-editor.org/standards) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF-Announce and rfc-dist lists. To subscribe or unsubscribe, see https://www.ietf.org/mailman/listinfo/ietf-announce https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see https://www.rfc-editor.org/search For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk Requests for special distribution should be addressed to either the author of the RFC in question, or to rfc-edi...@rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team Association Management Solutions, LLC ___ IETF-Announce mailing list IETF-Announce@ietf.org https://www.ietf.org/mailman/listinfo/ietf-announce
RFC 8836 on Congestion Control Requirements for Interactive Real-Time Media
A new Request for Comments is now available in online RFC libraries. RFC 8836 Title: Congestion Control Requirements for Interactive Real-Time Media Author: R. Jesup, Z. Sarker, Ed. Status: Informational Stream: IETF Date: January 2021 Mailbox:randell-i...@jesup.org, zaheduzzaman.sar...@ericsson.com Pages: 10 Updates/Obsoletes/SeeAlso: None I-D Tag:draft-ietf-rmcat-cc-requirements-09.txt URL:https://www.rfc-editor.org/info/rfc8836 DOI:10.17487/RFC8836 Congestion control is needed for all data transported across the Internet, in order to promote fair usage and prevent congestion collapse. The requirements for interactive, point-to-point real-time multimedia, which needs low-delay, semi-reliable data delivery, are different from the requirements for bulk transfer like FTP or bursty transfers like web pages. Due to an increasing amount of RTP-based real-time media traffic on the Internet (e.g., with the introduction of the Web Real-Time Communication (WebRTC)), it is especially important to ensure that this kind of traffic is congestion controlled. This document describes a set of requirements that can be used to evaluate other congestion control mechanisms in order to figure out their fitness for this purpose, and in particular to provide a set of possible requirements for a real-time media congestion avoidance technique. This document is a product of the RTP Media Congestion Avoidance Techniques Working Group of the IETF. INFORMATIONAL: This memo provides information for the Internet community. It does not specify an Internet standard of any kind. Distribution of this memo is unlimited. This announcement is sent to the IETF-Announce and rfc-dist lists. To subscribe or unsubscribe, see https://www.ietf.org/mailman/listinfo/ietf-announce https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see https://www.rfc-editor.org/search For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk Requests for special distribution should be addressed to either the author of the RFC in question, or to rfc-edi...@rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team Association Management Solutions, LLC ___ IETF-Announce mailing list IETF-Announce@ietf.org https://www.ietf.org/mailman/listinfo/ietf-announce
RFC 8835 on Transports for WebRTC
A new Request for Comments is now available in online RFC libraries. RFC 8835 Title: Transports for WebRTC Author: H. Alvestrand Status: Standards Track Stream: IETF Date: January 2021 Mailbox:har...@alvestrand.no Pages: 13 Updates/Obsoletes/SeeAlso: None I-D Tag:draft-ietf-rtcweb-transports-17.txt URL:https://www.rfc-editor.org/info/rfc8835 DOI:10.17487/RFC8835 This document describes the data transport protocols used by Web Real-Time Communication (WebRTC), including the protocols used for interaction with intermediate boxes such as firewalls, relays, and NAT boxes. This document is a product of the Real-Time Communication in WEB-browsers Working Group of the IETF. This is now a Proposed Standard. STANDARDS TRACK: This document specifies an Internet Standards Track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the Official Internet Protocol Standards (https://www.rfc-editor.org/standards) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF-Announce and rfc-dist lists. To subscribe or unsubscribe, see https://www.ietf.org/mailman/listinfo/ietf-announce https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see https://www.rfc-editor.org/search For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk Requests for special distribution should be addressed to either the author of the RFC in question, or to rfc-edi...@rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team Association Management Solutions, LLC ___ IETF-Announce mailing list IETF-Announce@ietf.org https://www.ietf.org/mailman/listinfo/ietf-announce
RFC 8834 on Media Transport and Use of RTP in WebRTC
A new Request for Comments is now available in online RFC libraries. RFC 8834 Title: Media Transport and Use of RTP in WebRTC Author: C. Perkins, M. Westerlund, J. Ott Status: Standards Track Stream: IETF Date: January 2021 Mailbox:c...@csperkins.org, magnus.westerl...@ericsson.com, o...@in.tum.de Pages: 39 Updates/Obsoletes/SeeAlso: None I-D Tag:draft-ietf-rtcweb-rtp-usage-26.txt URL:https://www.rfc-editor.org/info/rfc8834 DOI:10.17487/RFC8834 The framework for Web Real-Time Communication (WebRTC) provides support for direct interactive rich communication using audio, video, text, collaboration, games, etc. between two peers' web browsers. This memo describes the media transport aspects of the WebRTC framework. It specifies how the Real-time Transport Protocol (RTP) is used in the WebRTC context and gives requirements for which RTP features, profiles, and extensions need to be supported. This document is a product of the Real-Time Communication in WEB-browsers Working Group of the IETF. This is now a Proposed Standard. STANDARDS TRACK: This document specifies an Internet Standards Track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the Official Internet Protocol Standards (https://www.rfc-editor.org/standards) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF-Announce and rfc-dist lists. To subscribe or unsubscribe, see https://www.ietf.org/mailman/listinfo/ietf-announce https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see https://www.rfc-editor.org/search For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk Requests for special distribution should be addressed to either the author of the RFC in question, or to rfc-edi...@rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team Association Management Solutions, LLC ___ IETF-Announce mailing list IETF-Announce@ietf.org https://www.ietf.org/mailman/listinfo/ietf-announce
RFC 8833 on Application-Layer Protocol Negotiation (ALPN) for WebRTC
A new Request for Comments is now available in online RFC libraries. RFC 8833 Title: Application-Layer Protocol Negotiation (ALPN) for WebRTC Author: M. Thomson Status: Standards Track Stream: IETF Date: January 2021 Mailbox:martin.thom...@gmail.com Pages: 6 Updates/Obsoletes/SeeAlso: None I-D Tag:draft-ietf-rtcweb-alpn-04.txt URL:https://www.rfc-editor.org/info/rfc8833 DOI:10.17487/RFC8833 This document specifies two Application-Layer Protocol Negotiation (ALPN) labels for use with Web Real-Time Communication (WebRTC). The "webrtc" label identifies regular WebRTC: a DTLS session that is used to establish keys for the Secure Real-time Transport Protocol (SRTP) or to establish data channels using the Stream Control Transmission Protocol (SCTP) over DTLS. The "c-webrtc" label describes the same protocol, but the peers also agree to maintain the confidentiality of the media by not sharing it with other applications. This document is a product of the Real-Time Communication in WEB-browsers Working Group of the IETF. This is now a Proposed Standard. STANDARDS TRACK: This document specifies an Internet Standards Track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the Official Internet Protocol Standards (https://www.rfc-editor.org/standards) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF-Announce and rfc-dist lists. To subscribe or unsubscribe, see https://www.ietf.org/mailman/listinfo/ietf-announce https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see https://www.rfc-editor.org/search For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk Requests for special distribution should be addressed to either the author of the RFC in question, or to rfc-edi...@rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team Association Management Solutions, LLC ___ IETF-Announce mailing list IETF-Announce@ietf.org https://www.ietf.org/mailman/listinfo/ietf-announce
RFC 8832 on WebRTC Data Channel Establishment Protocol
A new Request for Comments is now available in online RFC libraries. RFC 8832 Title: WebRTC Data Channel Establishment Protocol Author: R. Jesup, S. Loreto, M. Tüxen Status: Standards Track Stream: IETF Date: January 2021 Mailbox:randell-i...@jesup.org, salvatore.lor...@ericsson.com, tue...@fh-muenster.de Pages: 12 Updates/Obsoletes/SeeAlso: None I-D Tag:draft-ietf-rtcweb-data-protocol-09.txt URL:https://www.rfc-editor.org/info/rfc8832 DOI:10.17487/RFC8832 The WebRTC framework specifies protocol support for direct interactive rich communication using audio, video, and data between two peers' web browsers. This document specifies a simple protocol for establishing symmetric data channels between the peers. It uses a two-way handshake and allows sending of user data without waiting for the handshake to complete. This document is a product of the Real-Time Communication in WEB-browsers Working Group of the IETF. This is now a Proposed Standard. STANDARDS TRACK: This document specifies an Internet Standards Track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the Official Internet Protocol Standards (https://www.rfc-editor.org/standards) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF-Announce and rfc-dist lists. To subscribe or unsubscribe, see https://www.ietf.org/mailman/listinfo/ietf-announce https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see https://www.rfc-editor.org/search For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk Requests for special distribution should be addressed to either the author of the RFC in question, or to rfc-edi...@rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team Association Management Solutions, LLC ___ IETF-Announce mailing list IETF-Announce@ietf.org https://www.ietf.org/mailman/listinfo/ietf-announce
RFC 8831 on WebRTC Data Channels
A new Request for Comments is now available in online RFC libraries. RFC 8831 Title: WebRTC Data Channels Author: R. Jesup, S. Loreto, M. Tüxen Status: Standards Track Stream: IETF Date: January 2021 Mailbox:randell-i...@jesup.org, salvatore.lor...@ericsson.com, tue...@fh-muenster.de Pages: 14 Updates/Obsoletes/SeeAlso: None I-D Tag:draft-ietf-rtcweb-data-channel-13.txt URL:https://www.rfc-editor.org/info/rfc8831 DOI:10.17487/RFC8831 The WebRTC framework specifies protocol support for direct, interactive, rich communication using audio, video, and data between two peers' web browsers. This document specifies the non-media data transport aspects of the WebRTC framework. It provides an architectural overview of how the Stream Control Transmission Protocol (SCTP) is used in the WebRTC context as a generic transport service that allows web browsers to exchange generic data from peer to peer. This document is a product of the Real-Time Communication in WEB-browsers Working Group of the IETF. This is now a Proposed Standard. STANDARDS TRACK: This document specifies an Internet Standards Track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the Official Internet Protocol Standards (https://www.rfc-editor.org/standards) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF-Announce and rfc-dist lists. To subscribe or unsubscribe, see https://www.ietf.org/mailman/listinfo/ietf-announce https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see https://www.rfc-editor.org/search For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk Requests for special distribution should be addressed to either the author of the RFC in question, or to rfc-edi...@rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team Association Management Solutions, LLC ___ IETF-Announce mailing list IETF-Announce@ietf.org https://www.ietf.org/mailman/listinfo/ietf-announce
RFC 8830 on WebRTC MediaStream Identification in the Session Description Protocol
A new Request for Comments is now available in online RFC libraries. RFC 8830 Title: WebRTC MediaStream Identification in the Session Description Protocol Author: H. Alvestrand Status: Standards Track Stream: IETF Date: January 2021 Mailbox:har...@alvestrand.no Pages: 12 Updates/Obsoletes/SeeAlso: None I-D Tag:draft-ietf-mmusic-msid-17.txt URL:https://www.rfc-editor.org/info/rfc8830 DOI:10.17487/RFC8830 This document specifies a Session Description Protocol (SDP) grouping mechanism for RTP media streams that can be used to specify relations between media streams. This mechanism is used to signal the association between the SDP concept of "media description" and the Web Real-Time Communication (WebRTC) concept of MediaStream/MediaStreamTrack using SDP signaling. This document is a product of the Multiparty Multimedia Session Control Working Group of the IETF. This is now a Proposed Standard. STANDARDS TRACK: This document specifies an Internet Standards Track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the Official Internet Protocol Standards (https://www.rfc-editor.org/standards) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF-Announce and rfc-dist lists. To subscribe or unsubscribe, see https://www.ietf.org/mailman/listinfo/ietf-announce https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see https://www.rfc-editor.org/search For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk Requests for special distribution should be addressed to either the author of the RFC in question, or to rfc-edi...@rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team Association Management Solutions, LLC ___ IETF-Announce mailing list IETF-Announce@ietf.org https://www.ietf.org/mailman/listinfo/ietf-announce
RFC 8828 on WebRTC IP Address Handling Requirements
A new Request for Comments is now available in online RFC libraries. RFC 8828 Title: WebRTC IP Address Handling Requirements Author: J. Uberti, G. Shieh Status: Standards Track Stream: IETF Date: January 2021 Mailbox:jus...@uberti.name, guow...@gmail.com Pages: 9 Updates/Obsoletes/SeeAlso: None I-D Tag:draft-ietf-rtcweb-ip-handling-12.txt URL:https://www.rfc-editor.org/info/rfc8828 DOI:10.17487/RFC8828 This document provides information and requirements for how IP addresses should be handled by Web Real-Time Communication (WebRTC) implementations. This document is a product of the Real-Time Communication in WEB-browsers Working Group of the IETF. This is now a Proposed Standard. STANDARDS TRACK: This document specifies an Internet Standards Track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the Official Internet Protocol Standards (https://www.rfc-editor.org/standards) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF-Announce and rfc-dist lists. To subscribe or unsubscribe, see https://www.ietf.org/mailman/listinfo/ietf-announce https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see https://www.rfc-editor.org/search For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk Requests for special distribution should be addressed to either the author of the RFC in question, or to rfc-edi...@rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team Association Management Solutions, LLC ___ IETF-Announce mailing list IETF-Announce@ietf.org https://www.ietf.org/mailman/listinfo/ietf-announce
RFC 8826 on Security Considerations for WebRTC
A new Request for Comments is now available in online RFC libraries. RFC 8826 Title: Security Considerations for WebRTC Author: E. Rescorla Status: Standards Track Stream: IETF Date: January 2021 Mailbox:e...@rtfm.com Pages: 21 Updates/Obsoletes/SeeAlso: None I-D Tag:draft-ietf-rtcweb-security-12.txt URL:https://www.rfc-editor.org/info/rfc8826 DOI:10.17487/RFC8826 WebRTC is a protocol suite for use with real-time applications that can be deployed in browsers -- "real-time communication on the Web". This document defines the WebRTC threat model and analyzes the security threats of WebRTC in that model. This document is a product of the Real-Time Communication in WEB-browsers Working Group of the IETF. This is now a Proposed Standard. STANDARDS TRACK: This document specifies an Internet Standards Track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the Official Internet Protocol Standards (https://www.rfc-editor.org/standards) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF-Announce and rfc-dist lists. To subscribe or unsubscribe, see https://www.ietf.org/mailman/listinfo/ietf-announce https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see https://www.rfc-editor.org/search For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk Requests for special distribution should be addressed to either the author of the RFC in question, or to rfc-edi...@rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team Association Management Solutions, LLC ___ IETF-Announce mailing list IETF-Announce@ietf.org https://www.ietf.org/mailman/listinfo/ietf-announce
RFC 8825 on Overview: Real-Time Protocols for Browser-Based Applications
A new Request for Comments is now available in online RFC libraries. RFC 8825 Title: Overview: Real-Time Protocols for Browser-Based Applications Author: H. Alvestrand Status: Standards Track Stream: IETF Date: January 2021 Mailbox:har...@alvestrand.no Pages: 17 Updates/Obsoletes/SeeAlso: None I-D Tag:draft-ietf-rtcweb-overview-19.txt URL:https://www.rfc-editor.org/info/rfc8825 DOI:10.17487/RFC8825 This document gives an overview and context of a protocol suite intended for use with real-time applications that can be deployed in browsers -- "real-time communication on the Web". It intends to serve as a starting and coordination point to make sure that (1) all the parts that are needed to achieve this goal are findable and (2) the parts that belong in the Internet protocol suite are fully specified and on the right publication track. This document is an applicability statement -- it does not itself specify any protocol, but it specifies which other specifications implementations are supposed to follow to be compliant with Web Real-Time Communication (WebRTC). This document is a product of the Real-Time Communication in WEB-browsers Working Group of the IETF. This is now a Proposed Standard. STANDARDS TRACK: This document specifies an Internet Standards Track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the Official Internet Protocol Standards (https://www.rfc-editor.org/standards) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF-Announce and rfc-dist lists. To subscribe or unsubscribe, see https://www.ietf.org/mailman/listinfo/ietf-announce https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see https://www.rfc-editor.org/search For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk Requests for special distribution should be addressed to either the author of the RFC in question, or to rfc-edi...@rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team Association Management Solutions, LLC ___ IETF-Announce mailing list IETF-Announce@ietf.org https://www.ietf.org/mailman/listinfo/ietf-announce
RFC 8850 on Controlling Multiple Streams for Telepresence (CLUE) Protocol Data Channel
A new Request for Comments is now available in online RFC libraries. RFC 8850 Title: Controlling Multiple Streams for Telepresence (CLUE) Protocol Data Channel Author: C. Holmberg Status: Experimental Stream: IETF Date: January 2020 Mailbox:christer.holmb...@ericsson.com Pages: 9 Updates/Obsoletes/SeeAlso: None I-D Tag:draft-ietf-clue-datachannel-18.txt URL:https://www.rfc-editor.org/info/rfc8850 DOI:10.17487/RFC8850 This document defines how to use the WebRTC data channel mechanism to realize a data channel, referred to as a Controlling Multiple Streams for Telepresence (CLUE) data channel, for transporting CLUE protocol messages between two CLUE entities. This document is a product of the ControLling mUltiple streams for tElepresence Working Group of the IETF. EXPERIMENTAL: This memo defines an Experimental Protocol for the Internet community. It does not specify an Internet standard of any kind. Discussion and suggestions for improvement are requested. Distribution of this memo is unlimited. This announcement is sent to the IETF-Announce and rfc-dist lists. To subscribe or unsubscribe, see https://www.ietf.org/mailman/listinfo/ietf-announce https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see https://www.rfc-editor.org/search For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk Requests for special distribution should be addressed to either the author of the RFC in question, or to rfc-edi...@rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team Association Management Solutions, LLC ___ IETF-Announce mailing list IETF-Announce@ietf.org https://www.ietf.org/mailman/listinfo/ietf-announce
RFC 8849 on Mapping RTP Streams to Controlling Multiple Streams for Telepresence (CLUE) Media Captures
A new Request for Comments is now available in online RFC libraries. RFC 8849 Title: Mapping RTP Streams to Controlling Multiple Streams for Telepresence (CLUE) Media Captures Author: R. Even, J. Lennox Status: Standards Track Stream: IETF Date: January 2020 Mailbox:ron.even@gmail.com, jonathan.len...@8x8.com Pages: 12 Updates/Obsoletes/SeeAlso: None I-D Tag:draft-ietf-clue-rtp-mapping-14.txt URL:https://www.rfc-editor.org/info/rfc8849 DOI:10.17487/RFC8849 This document describes how the Real-time Transport Protocol (RTP) is used in the context of the Controlling Multiple Streams for Telepresence (CLUE) protocol. It also describes the mechanisms and recommended practice for mapping RTP media streams, as defined in the Session Description Protocol (SDP), to CLUE Media Captures and defines a new RTP header extension (CaptureID). This document is a product of the ControLling mUltiple streams for tElepresence Working Group of the IETF. This is now a Proposed Standard. STANDARDS TRACK: This document specifies an Internet Standards Track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the Official Internet Protocol Standards (https://www.rfc-editor.org/standards) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF-Announce and rfc-dist lists. To subscribe or unsubscribe, see https://www.ietf.org/mailman/listinfo/ietf-announce https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see https://www.rfc-editor.org/search For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk Requests for special distribution should be addressed to either the author of the RFC in question, or to rfc-edi...@rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team Association Management Solutions, LLC ___ IETF-Announce mailing list IETF-Announce@ietf.org https://www.ietf.org/mailman/listinfo/ietf-announce
RFC 8848 on Session Signaling for Controlling Multiple Streams for Telepresence (CLUE)
A new Request for Comments is now available in online RFC libraries. RFC 8848 Title: Session Signaling for Controlling Multiple Streams for Telepresence (CLUE) Author: R. Hanton, P. Kyzivat, L. Xiao, C. Groves Status: Experimental Stream: IETF Date: January 2020 Mailbox:rohan...@cisco.com, pkyzi...@alum.mit.edu, lennard.x...@outlook.com, cngroves@gmail.com Pages: 29 Updates/Obsoletes/SeeAlso: None I-D Tag:draft-ietf-clue-signaling-15.txt URL:https://www.rfc-editor.org/info/rfc8848 DOI:10.17487/RFC8848 This document is about Controlling Multiple Streams for Telepresence (CLUE) signaling. It specifies how the CLUE protocol and the CLUE data channel are used in conjunction with each other and with existing signaling mechanisms, such as SIP and the Session Description Protocol (SDP), to produce a telepresence call. This document is a product of the ControLling mUltiple streams for tElepresence Working Group of the IETF. EXPERIMENTAL: This memo defines an Experimental Protocol for the Internet community. It does not specify an Internet standard of any kind. Discussion and suggestions for improvement are requested. Distribution of this memo is unlimited. This announcement is sent to the IETF-Announce and rfc-dist lists. To subscribe or unsubscribe, see https://www.ietf.org/mailman/listinfo/ietf-announce https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see https://www.rfc-editor.org/search For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk Requests for special distribution should be addressed to either the author of the RFC in question, or to rfc-edi...@rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team Association Management Solutions, LLC ___ IETF-Announce mailing list IETF-Announce@ietf.org https://www.ietf.org/mailman/listinfo/ietf-announce
RFC 8847 on Protocol for Controlling Multiple Streams for Telepresence (CLUE)
A new Request for Comments is now available in online RFC libraries.
RFC 8847
Title: Protocol for Controlling Multiple Streams
for Telepresence (CLUE)
Author: R. Presta,
S P. Romano
Status: Experimental
Stream: IETF
Date: January 2020
Mailbox:roberta.pre...@unina.it,
sprom...@unina.it
Pages: 62
Updates/Obsoletes/SeeAlso: None
I-D Tag:draft-ietf-clue-protocol-19.txt
URL:https://www.rfc-editor.org/info/rfc8847
DOI:10.17487/RFC8847
The Controlling Multiple Streams for Telepresence (CLUE) protocol is
an application protocol conceived for the description and negotiation
of a telepresence session. The design of the CLUE protocol takes
into account the requirements and the framework defined within the
IETF CLUE Working Group. A companion document, RFC 8848, delves into
CLUE signaling details as well as the SIP / Session Description
Protocol (SDP) session establishment phase. CLUE messages flow over
the CLUE data channel, based on reliable and ordered SCTP-over-DTLS
transport. ("SCTP" stands for "Stream Control Transmission
Protocol".) Message details, together with the behavior of CLUE
Participants acting as Media Providers and/or Media Consumers, are
herein discussed.
This document is a product of the ControLling mUltiple streams for tElepresence
Working Group of the IETF.
EXPERIMENTAL: This memo defines an Experimental Protocol for the
Internet community. It does not specify an Internet standard of any
kind. Discussion and suggestions for improvement are requested.
Distribution of this memo is unlimited.
This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
https://www.ietf.org/mailman/listinfo/ietf-announce
https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk
Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-edi...@rfc-editor.org. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
The RFC Editor Team
Association Management Solutions, LLC
___
IETF-Announce mailing list
IETF-Announce@ietf.org
https://www.ietf.org/mailman/listinfo/ietf-announce
RFC 8846 on An XML Schema for the Controlling Multiple Streams for Telepresence (CLUE) Data Model
A new Request for Comments is now available in online RFC libraries. RFC 8846 Title: An XML Schema for the Controlling Multiple Streams for Telepresence (CLUE) Data Model Author: R. Presta, S P. Romano Status: Standards Track Stream: IETF Date: January 2020 Mailbox:roberta.pre...@unina.it, sprom...@unina.it Pages: 66 Updates/Obsoletes/SeeAlso: None I-D Tag:draft-ietf-clue-data-model-schema-17.txt URL:https://www.rfc-editor.org/info/rfc8846 DOI:10.17487/RFC8846 This document provides an XML schema file for the definition of CLUE data model types. The term "CLUE" stands for "Controlling Multiple Streams for Telepresence" and is the name of the IETF working group in which this document, as well as other companion documents, has been developed. The document defines a coherent structure for information associated with the description of a telepresence scenario. This document is a product of the ControLling mUltiple streams for tElepresence Working Group of the IETF. This is now a Proposed Standard. STANDARDS TRACK: This document specifies an Internet Standards Track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the Official Internet Protocol Standards (https://www.rfc-editor.org/standards) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF-Announce and rfc-dist lists. To subscribe or unsubscribe, see https://www.ietf.org/mailman/listinfo/ietf-announce https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see https://www.rfc-editor.org/search For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk Requests for special distribution should be addressed to either the author of the RFC in question, or to rfc-edi...@rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team Association Management Solutions, LLC ___ IETF-Announce mailing list IETF-Announce@ietf.org https://www.ietf.org/mailman/listinfo/ietf-announce
RFC 8845 on Framework for Telepresence Multi-Streams
A new Request for Comments is now available in online RFC libraries. RFC 8845 Title: Framework for Telepresence Multi-Streams Author: M. Duckworth, Ed., A. Pepperell, S. Wenger Status: Standards Track Stream: IETF Date: January 2020 Mailbox:mrduck...@outlook.com, apepp...@gmail.com, st...@stewe.org Pages: 61 Updates/Obsoletes/SeeAlso: None I-D Tag:draft-ietf-clue-framework-25.txt URL:https://www.rfc-editor.org/info/rfc8845 DOI:10.17487/RFC8845 This document defines a framework for a protocol to enable devices in a telepresence conference to interoperate. The protocol enables communication of information about multiple media streams so a sending system and receiving system can make reasonable decisions about transmitting, selecting, and rendering the media streams. This protocol is used in addition to SIP signaling and Session Description Protocol (SDP) negotiation for setting up a telepresence session. This document is a product of the ControLling mUltiple streams for tElepresence Working Group of the IETF. This is now a Proposed Standard. STANDARDS TRACK: This document specifies an Internet Standards Track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the Official Internet Protocol Standards (https://www.rfc-editor.org/standards) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF-Announce and rfc-dist lists. To subscribe or unsubscribe, see https://www.ietf.org/mailman/listinfo/ietf-announce https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see https://www.rfc-editor.org/search For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk Requests for special distribution should be addressed to either the author of the RFC in question, or to rfc-edi...@rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team Association Management Solutions, LLC ___ IETF-Announce mailing list IETF-Announce@ietf.org https://www.ietf.org/mailman/listinfo/ietf-announce
RFC 8844 on Unknown Key-Share Attacks on Uses of TLS with the Session Description Protocol (SDP)
A new Request for Comments is now available in online RFC libraries. RFC 8844 Title: Unknown Key-Share Attacks on Uses of TLS with the Session Description Protocol (SDP) Author: M. Thomson, E. Rescorla Status: Standards Track Stream: IETF Date: January 2020 Mailbox:m...@lowentropy.net, e...@rtfm.com Pages: 17 Updates:RFC 8122 I-D Tag:draft-ietf-mmusic-sdp-uks-07.txt URL:https://www.rfc-editor.org/info/rfc8844 DOI:10.17487/RFC8844 This document describes unknown key-share attacks on the use of Datagram Transport Layer Security for the Secure Real-Time Transport Protocol (DTLS-SRTP). Similar attacks are described on the use of DTLS-SRTP with the identity bindings used in Web Real-Time Communications (WebRTC) and SIP identity. These attacks are difficult to mount, but they cause a victim to be misled about the identity of a communicating peer. This document defines mitigation techniques that implementations of RFC 8122 are encouraged to deploy. This document is a product of the Multiparty Multimedia Session Control Working Group of the IETF. This is now a Proposed Standard. STANDARDS TRACK: This document specifies an Internet Standards Track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the Official Internet Protocol Standards (https://www.rfc-editor.org/standards) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF-Announce and rfc-dist lists. To subscribe or unsubscribe, see https://www.ietf.org/mailman/listinfo/ietf-announce https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see https://www.rfc-editor.org/search For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk Requests for special distribution should be addressed to either the author of the RFC in question, or to rfc-edi...@rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team Association Management Solutions, LLC ___ IETF-Announce mailing list IETF-Announce@ietf.org https://www.ietf.org/mailman/listinfo/ietf-announce
RFC 8842 on Session Description Protocol (SDP) Offer/Answer Considerations for Datagram Transport Layer Security (DTLS) and Transport Layer Security (TLS)
A new Request for Comments is now available in online RFC libraries. RFC 8842 Title: Session Description Protocol (SDP) Offer/Answer Considerations for Datagram Transport Layer Security (DTLS) and Transport Layer Security (TLS) Author: C. Holmberg, R. Shpount Status: Standards Track Stream: IETF Date: January 2020 Mailbox:christer.holmb...@ericsson.com, rshpo...@turbobridge.com Pages: 19 Updates:RFC 5763, RFC 7345 I-D Tag:draft-ietf-mmusic-dtls-sdp-32.txt URL:https://www.rfc-editor.org/info/rfc8842 DOI:10.17487/RFC8842 This document defines the Session Description Protocol (SDP) offer/answer procedures for negotiating and establishing a Datagram Transport Layer Security (DTLS) association. The document also defines the criteria for when a new DTLS association must be established. The document updates RFCs 5763 and 7345 by replacing common SDP offer/answer procedures with a reference to this specification. This document defines a new SDP media-level attribute, "tls-id". This document also defines how the "tls-id" attribute can be used for negotiating and establishing a Transport Layer Security (TLS) connection, in conjunction with the procedures in RFCs 4145 and 8122. This document is a product of the Multiparty Multimedia Session Control Working Group of the IETF. This is now a Proposed Standard. STANDARDS TRACK: This document specifies an Internet Standards Track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the Official Internet Protocol Standards (https://www.rfc-editor.org/standards) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF-Announce and rfc-dist lists. To subscribe or unsubscribe, see https://www.ietf.org/mailman/listinfo/ietf-announce https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see https://www.rfc-editor.org/search For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk Requests for special distribution should be addressed to either the author of the RFC in question, or to rfc-edi...@rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team Association Management Solutions, LLC ___ IETF-Announce mailing list IETF-Announce@ietf.org https://www.ietf.org/mailman/listinfo/ietf-announce
RFC 8841 on Session Description Protocol (SDP) Offer/Answer Procedures for Stream Control Transmission Protocol (SCTP) over Datagram Transport Layer Security (DTLS) Transport
A new Request for Comments is now available in online RFC libraries. RFC 8841 Title: Session Description Protocol (SDP) Offer/Answer Procedures for Stream Control Transmission Protocol (SCTP) over Datagram Transport Layer Security (DTLS) Transport Author: C. Holmberg, R. Shpount, S. Loreto, G. Camarillo Status: Standards Track Stream: IETF Date: January 2020 Mailbox:christer.holmb...@ericsson.com, rshpo...@turbobridge.com, salvatore.lor...@ericsson.com, gonzalo.camari...@ericsson.com Pages: 21 Updates/Obsoletes/SeeAlso: None I-D Tag:draft-ietf-mmusic-sctp-sdp-26.txt URL:https://www.rfc-editor.org/info/rfc8841 DOI:10.17487/RFC8841 The Stream Control Transmission Protocol (SCTP) is a transport protocol used to establish associations between two endpoints. RFC 8261 specifies how SCTP can be used on top of the Datagram Transport Layer Security (DTLS) protocol, which is referred to as SCTP-over-DTLS. This specification defines the following new Session Description Protocol (SDP) protocol identifiers (proto values): "UDP/DTLS/SCTP" and "TCP/DTLS/SCTP". This specification also specifies how to use the new proto values with the SDP offer/answer mechanism for negotiating SCTP-over-DTLS associations. This document is a product of the Multiparty Multimedia Session Control Working Group of the IETF. This is now a Proposed Standard. STANDARDS TRACK: This document specifies an Internet Standards Track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the Official Internet Protocol Standards (https://www.rfc-editor.org/standards) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF-Announce and rfc-dist lists. To subscribe or unsubscribe, see https://www.ietf.org/mailman/listinfo/ietf-announce https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see https://www.rfc-editor.org/search For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk Requests for special distribution should be addressed to either the author of the RFC in question, or to rfc-edi...@rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team Association Management Solutions, LLC ___ IETF-Announce mailing list IETF-Announce@ietf.org https://www.ietf.org/mailman/listinfo/ietf-announce
RFC 8840 on A Session Initiation Protocol (SIP) Usage for Incremental Provisioning of Candidates for the Interactive Connectivity Establishment (Trickle ICE)
A new Request for Comments is now available in online RFC libraries. RFC 8840 Title: A Session Initiation Protocol (SIP) Usage for Incremental Provisioning of Candidates for the Interactive Connectivity Establishment (Trickle ICE) Author: E. Ivov, T. Stach, E. Marocco, C. Holmberg Status: Standards Track Stream: IETF Date: January 2020 Mailbox:em...@jitsi.org, thomass.st...@gmail.com, enrico.maro...@telecomitalia.it, christer.holmb...@ericsson.com Pages: 34 Updates/Obsoletes/SeeAlso: None I-D Tag:draft-ietf-mmusic-trickle-ice-sip-18.txt URL:https://www.rfc-editor.org/info/rfc8840 DOI:10.17487/RFC8840 The Interactive Connectivity Establishment (ICE) protocol describes a Network Address Translator (NAT) traversal mechanism for UDP-based multimedia sessions established with the Offer/Answer model. The ICE extension for Incremental Provisioning of Candidates (Trickle ICE) defines a mechanism that allows ICE Agents to shorten session establishment delays by making the candidate gathering and connectivity checking phases of ICE non-blocking and by executing them in parallel. This document defines usage semantics for Trickle ICE with the Session Initiation Protocol (SIP). The document also defines a new SIP Info Package to support this usage together with the corresponding media type. Additionally, a new Session Description Protocol (SDP) "end-of-candidates" attribute and a new SIP option tag "trickle-ice" are defined. This document is a product of the Multiparty Multimedia Session Control Working Group of the IETF. This is now a Proposed Standard. STANDARDS TRACK: This document specifies an Internet Standards Track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the Official Internet Protocol Standards (https://www.rfc-editor.org/standards) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF-Announce and rfc-dist lists. To subscribe or unsubscribe, see https://www.ietf.org/mailman/listinfo/ietf-announce https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see https://www.rfc-editor.org/search For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk Requests for special distribution should be addressed to either the author of the RFC in question, or to rfc-edi...@rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team Association Management Solutions, LLC ___ IETF-Announce mailing list IETF-Announce@ietf.org https://www.ietf.org/mailman/listinfo/ietf-announce
RFC 8839 on Session Description Protocol (SDP) Offer/Answer Procedures for Interactive Connectivity Establishment (ICE)
A new Request for Comments is now available in online RFC libraries. RFC 8839 Title: Session Description Protocol (SDP) Offer/Answer Procedures for Interactive Connectivity Establishment (ICE) Author: M. Petit-Huguenin, S. Nandakumar, C. Holmberg, A. Keränen, R. Shpount Status: Standards Track Stream: IETF Date: January 2020 Mailbox:m...@petit-huguenin.org, snand...@cisco.com, christer.holmb...@ericsson.com, ari.kera...@ericsson.com, rshpo...@turbobridge.com Pages: 38 Obsoletes: RFC 5245, RFC 6336 I-D Tag:draft-ietf-mmusic-ice-sip-sdp-39.txt URL:https://www.rfc-editor.org/info/rfc8839 DOI:10.17487/RFC8839 This document describes Session Description Protocol (SDP) Offer/Answer procedures for carrying out Interactive Connectivity Establishment (ICE) between the agents. This document obsoletes RFCs 5245 and 6336. This document is a product of the Multiparty Multimedia Session Control Working Group of the IETF. This is now a Proposed Standard. STANDARDS TRACK: This document specifies an Internet Standards Track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the Official Internet Protocol Standards (https://www.rfc-editor.org/standards) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF-Announce and rfc-dist lists. To subscribe or unsubscribe, see https://www.ietf.org/mailman/listinfo/ietf-announce https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see https://www.rfc-editor.org/search For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk Requests for special distribution should be addressed to either the author of the RFC in question, or to rfc-edi...@rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team Association Management Solutions, LLC ___ IETF-Announce mailing list IETF-Announce@ietf.org https://www.ietf.org/mailman/listinfo/ietf-announce
RFC 8838 on Trickle ICE: Incremental Provisioning of Candidates for the Interactive Connectivity Establishment (ICE) Protocol
A new Request for Comments is now available in online RFC libraries. RFC 8838 Title: Trickle ICE: Incremental Provisioning of Candidates for the Interactive Connectivity Establishment (ICE) Protocol Author: E. Ivov, J. Uberti, P. Saint-Andre Status: Standards Track Stream: IETF Date: January 2020 Mailbox:em...@jitsi.org, jus...@uberti.name, stpe...@mozilla.com Pages: 22 Updates/Obsoletes/SeeAlso: None I-D Tag:draft-ietf-ice-trickle-21.txt URL:https://www.rfc-editor.org/info/rfc8838 DOI:10.17487/RFC8838 This document describes "Trickle ICE", an extension to the Interactive Connectivity Establishment (ICE) protocol that enables ICE agents to begin connectivity checks while they are still gathering candidates, by incrementally exchanging candidates over time instead of all at once. This method can considerably accelerate the process of establishing a communication session. This document is a product of the Interactive Connectivity Establishment Working Group of the IETF. This is now a Proposed Standard. STANDARDS TRACK: This document specifies an Internet Standards Track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the Official Internet Protocol Standards (https://www.rfc-editor.org/standards) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF-Announce and rfc-dist lists. To subscribe or unsubscribe, see https://www.ietf.org/mailman/listinfo/ietf-announce https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see https://www.rfc-editor.org/search For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk Requests for special distribution should be addressed to either the author of the RFC in question, or to rfc-edi...@rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team Association Management Solutions, LLC ___ IETF-Announce mailing list IETF-Announce@ietf.org https://www.ietf.org/mailman/listinfo/ietf-announce
IETF 110 Online: Early Bird Registration Ends Today!
IETF 110 Online March 08-12, 2021 1. Registration 2. Fee Waivers 3. IETF 110 Meeting T-Shirts 4. Hackathon 1. Registration Early Bird Deadline: The early bird deadline for registration is today, Monday, January 18th. Be sure to register and pay before the deadline passes! Register online at: https://registration.ietf.org/110/ NOTE: Payment is required at the time of registration. The Early Bird registration fee is $230 USD until Monday, January 18th at UTC 23:59. After January 18th at UTC 23:59 the registration fee will be $280 USD until the next registration deadline on February 22nd, at which time the registration fee will become $330 USD. 2. Fee Waivers: We understand that not everyone can afford the IETF 110 registration fee for a variety of reasons, including issues with income, employment status and employer support, and we do not want any of these to be a barrier to participation. If you cannot afford the registration fee then please take this fee waiver option to ensure that you can participate: https://www.ietf.org/forms/110-registration-fee-waiver/. 3. IETF 110 Meeting T-Shirts: After you register you will be able to choose if you want to receive a IETF 110 t-shirt delivered to you at no additional expense. You must take action to request a t-shirt: it is not part of the meeting registration form. To reserve your t-shirt, visit your personal meeting dashboard (i.e. https://registration.ietf.org/110/attendee-dashboard/YOURREGISTRATION#/). Direct link to your dashboard is also available in your confirmation email. Limited quantities are available, on a first-come-first-served basis with a limit of one per registration. 4. Hackathon: The IETF is holding a Hackathon to encourage developers to discuss, collaborate and develop utilities, ideas, sample code and solutions that show practical implementations of IETF standards. When: Monday, March 1 through Friday, March 5, 2021 Signup for the Hackathon: https://registration.ietf.org/110/new/hackathon/ More information can be found here: https://www.ietf.org/how/runningcode/hackathons/110-hackathon/ Keep up to date by subscribing to: https://www.ietf.org/mailman/listinfo/hackathon The Hackathon is free to attend and open to all. Extend the invitation to colleagues outside the IETF! Descriptions and information regarding the technologies for the hackathon are located on the IETF 110 Meeting Wiki: https://trac.ietf.org/trac/ietf/meeting/wiki/110hackathon Don’t see anything that interests you? Feel free to add your preferred technology to the list, sign up as its Champion and show up to work on it. Note: you must login to the wiki to add content. If you do add a new technology, we strongly suggest that you send an email to hackat...@ietf.org to let others know. You may generate interest in your technology, and find other people who want to contribute to it. ___ IETF-Announce mailing list IETF-Announce@ietf.org https://www.ietf.org/mailman/listinfo/ietf-announce
