draft-ietf-rtcweb-security-arch-19.txt   draft-ietf-rtcweb-security-arch-20.txt 
RTCWEB E. Rescorla RTCWEB E. Rescorla
Internet-Draft RTFM, Inc. Internet-Draft RTFM, Inc.
Intended status: Standards Track July 7, 2019 Intended status: Standards Track July 21, 2019
Expires: January 8, 2020 Expires: January 22, 2020
WebRTC Security Architecture WebRTC Security Architecture
draft-ietf-rtcweb-security-arch-19 draft-ietf-rtcweb-security-arch-20
Abstract Abstract
This document defines the security architecture for WebRTC, a This document defines the security architecture for WebRTC, a
protocol suite intended for use with real-time applications that can protocol suite intended for use with real-time applications that can
be deployed in browsers - "real time communication on the Web". be deployed in browsers - "real time communication on the Web".
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
skipping to change at page 1, line 32 skipping to change at page 1, line 32
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/. Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on January 8, 2020. This Internet-Draft will expire on January 22, 2020.
Copyright Notice Copyright Notice
Copyright (c) 2019 IETF Trust and the persons identified as the Copyright (c) 2019 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of (https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 13, line 41 skipping to change at page 13, line 41
The identity-assertion value is a JSON [RFC8259] encoded string. The The identity-assertion value is a JSON [RFC8259] encoded string. The
JSON object contains two keys: "assertion" and "idp". The JSON object contains two keys: "assertion" and "idp". The
"assertion" key value contains an opaque string that is consumed by "assertion" key value contains an opaque string that is consumed by
the IdP. The "idp" key value contains a dictionary with one or two the IdP. The "idp" key value contains a dictionary with one or two
further values that identify the IdP. See Section 7.6 for more further values that identify the IdP. See Section 7.6 for more
details. details.
5.1. Offer/Answer Considerations 5.1. Offer/Answer Considerations
This section defines the SDP Offer/Answer [RFC6454] considerations This section defines the SDP Offer/Answer [RFC3264] considerations
for the SDP 'identity' attribute. for the SDP 'identity' attribute.
Within this section, 'initial offer' refers to the first offer in the Within this section, 'initial offer' refers to the first offer in the
SDP session that contains an SDP "identity" attribute. SDP session that contains an SDP "identity" attribute.
5.1.1. Generating the Initial SDP Offer 5.1.1. Generating the Initial SDP Offer
When an offerer sends an offer, in order to provide its identity When an offerer sends an offer, in order to provide its identity
assertion to the peer, it includes an 'identity' attribute in the assertion to the peer, it includes an 'identity' attribute in the
offer. In addition, the offerer includes one or more SDP offer. In addition, the offerer includes one or more SDP
skipping to change at page 39, line 18 skipping to change at page 39, line 18
13.1. Normative References 13.1. Normative References
[FIPS186] National Institute of Standards and Technology (NIST), [FIPS186] National Institute of Standards and Technology (NIST),
"Digital Signature Standard (DSS)", NIST PUB 186-4 , July "Digital Signature Standard (DSS)", NIST PUB 186-4 , July
2013. 2013.
[I-D.ietf-mmusic-sdp-uks] [I-D.ietf-mmusic-sdp-uks]
Thomson, M. and E. Rescorla, "Unknown Key Share Attacks on Thomson, M. and E. Rescorla, "Unknown Key Share Attacks on
uses of TLS with the Session Description Protocol (SDP)", uses of TLS with the Session Description Protocol (SDP)",
draft-ietf-mmusic-sdp-uks-05 (work in progress), June draft-ietf-mmusic-sdp-uks-06 (work in progress), July
2019. 2019.
[I-D.ietf-rtcweb-jsep] [I-D.ietf-rtcweb-jsep]
Uberti, J., Jennings, C., and E. Rescorla, "JavaScript Uberti, J., Jennings, C., and E. Rescorla, "JavaScript
Session Establishment Protocol", draft-ietf-rtcweb-jsep-26 Session Establishment Protocol", draft-ietf-rtcweb-jsep-26
(work in progress), February 2019. (work in progress), February 2019.
[I-D.ietf-rtcweb-overview] [I-D.ietf-rtcweb-overview]
Alvestrand, H., "Overview: Real Time Protocols for Alvestrand, H., "Overview: Real Time Protocols for
Browser-based Applications", draft-ietf-rtcweb-overview-19 Browser-based Applications", draft-ietf-rtcweb-overview-19
skipping to change at page 40, line 5 skipping to change at page 40, line 5
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997, DOI 10.17487/RFC2119, March 1997,
<https://www.rfc-editor.org/info/rfc2119>. <https://www.rfc-editor.org/info/rfc2119>.
[RFC2818] Rescorla, E., "HTTP Over TLS", RFC 2818, [RFC2818] Rescorla, E., "HTTP Over TLS", RFC 2818,
DOI 10.17487/RFC2818, May 2000, DOI 10.17487/RFC2818, May 2000,
<https://www.rfc-editor.org/info/rfc2818>. <https://www.rfc-editor.org/info/rfc2818>.
[RFC3264] Rosenberg, J. and H. Schulzrinne, "An Offer/Answer Model
with Session Description Protocol (SDP)", RFC 3264,
DOI 10.17487/RFC3264, June 2002,
<https://www.rfc-editor.org/info/rfc3264>.
[RFC3711] Baugher, M., McGrew, D., Naslund, M., Carrara, E., and K. [RFC3711] Baugher, M., McGrew, D., Naslund, M., Carrara, E., and K.
Norrman, "The Secure Real-time Transport Protocol (SRTP)", Norrman, "The Secure Real-time Transport Protocol (SRTP)",
RFC 3711, DOI 10.17487/RFC3711, March 2004, RFC 3711, DOI 10.17487/RFC3711, March 2004,
<https://www.rfc-editor.org/info/rfc3711>. <https://www.rfc-editor.org/info/rfc3711>.
[RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform [RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform
Resource Identifier (URI): Generic Syntax", STD 66, Resource Identifier (URI): Generic Syntax", STD 66,
RFC 3986, DOI 10.17487/RFC3986, January 2005, RFC 3986, DOI 10.17487/RFC3986, January 2005,
<https://www.rfc-editor.org/info/rfc3986>. <https://www.rfc-editor.org/info/rfc3986>.
 End of changes. 6 change blocks. 
6 lines changed or deleted 11 lines changed or added

This html diff was produced by rfcdiff 1.47. The latest version is available from http://tools.ietf.org/tools/rfcdiff/