rfc8828v2.txt | rfc8828.txt | |||
---|---|---|---|---|
Internet Engineering Task Force (IETF) J. Uberti | Internet Engineering Task Force (IETF) J. Uberti | |||
Request for Comments: 8828 Google | Request for Comments: 8828 Google | |||
Category: Standards Track July 2020 | Category: Standards Track G. Shieh | |||
ISSN: 2070-1721 | ISSN: 2070-1721 January 2021 | |||
WebRTC IP Address Handling Requirements | WebRTC IP Address Handling Requirements | |||
Abstract | Abstract | |||
This document provides information and requirements for how IP | This document provides information and requirements for how IP | |||
addresses should be handled by Web Real-Time Communication (WebRTC) | addresses should be handled by Web Real-Time Communication (WebRTC) | |||
implementations. | implementations. | |||
Status of This Memo | Status of This Memo | |||
skipping to change at line 31 ¶ | skipping to change at line 31 ¶ | |||
received public review and has been approved for publication by the | received public review and has been approved for publication by the | |||
Internet Engineering Steering Group (IESG). Further information on | Internet Engineering Steering Group (IESG). Further information on | |||
Internet Standards is available in Section 2 of RFC 7841. | Internet Standards is available in Section 2 of RFC 7841. | |||
Information about the current status of this document, any errata, | Information about the current status of this document, any errata, | |||
and how to provide feedback on it may be obtained at | and how to provide feedback on it may be obtained at | |||
https://www.rfc-editor.org/info/rfc8828. | https://www.rfc-editor.org/info/rfc8828. | |||
Copyright Notice | Copyright Notice | |||
Copyright (c) 2020 IETF Trust and the persons identified as the | Copyright (c) 2021 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 | |||
carefully, as they describe your rights and restrictions with respect | carefully, as they describe your rights and restrictions with respect | |||
to this document. Code Components extracted from this document must | to this document. Code Components extracted from this document must | |||
include Simplified BSD License text as described in Section 4.e of | include Simplified BSD License text as described in Section 4.e of | |||
the Trust Legal Provisions and are provided without warranty as | the Trust Legal Provisions and are provided without warranty as | |||
skipping to change at line 63 ¶ | skipping to change at line 63 ¶ | |||
6. Implementation Guidance | 6. Implementation Guidance | |||
6.1. Ensuring Normal Routing | 6.1. Ensuring Normal Routing | |||
6.2. Determining Associated Local Addresses | 6.2. Determining Associated Local Addresses | |||
7. Application Guidance | 7. Application Guidance | |||
8. Security Considerations | 8. Security Considerations | |||
9. IANA Considerations | 9. IANA Considerations | |||
10. References | 10. References | |||
10.1. Normative References | 10.1. Normative References | |||
10.2. Informative References | 10.2. Informative References | |||
Acknowledgements | Acknowledgements | |||
Author's Address | Authors' Addresses | |||
1. Introduction | 1. Introduction | |||
One of WebRTC's key features is its support of peer-to-peer | One of WebRTC's key features is its support of peer-to-peer | |||
connections. However, when establishing such a connection, which | connections. However, when establishing such a connection, which | |||
involves connection attempts from various IP addresses, WebRTC may | involves connection attempts from various IP addresses, WebRTC may | |||
allow a web application to learn additional information about the | allow a web application to learn additional information about the | |||
user compared to an application that only uses the Hypertext Transfer | user compared to an application that only uses the Hypertext Transfer | |||
Protocol (HTTP) [RFC7230]. This may be problematic in certain cases. | Protocol (HTTP) [RFC7230]. This may be problematic in certain cases. | |||
This document summarizes the concerns and makes recommendations on | This document summarizes the concerns and makes recommendations on | |||
skipping to change at line 440 ¶ | skipping to change at line 440 ¶ | |||
Protocol (HTTP/1.1): Message Syntax and Routing", | Protocol (HTTP/1.1): Message Syntax and Routing", | |||
RFC 7230, DOI 10.17487/RFC7230, June 2014, | RFC 7230, DOI 10.17487/RFC7230, June 2014, | |||
<https://www.rfc-editor.org/info/rfc7230>. | <https://www.rfc-editor.org/info/rfc7230>. | |||
[RFC7478] Holmberg, C., Hakansson, S., and G. Eriksson, "Web Real- | [RFC7478] Holmberg, C., Hakansson, S., and G. Eriksson, "Web Real- | |||
Time Communication Use Cases and Requirements", RFC 7478, | Time Communication Use Cases and Requirements", RFC 7478, | |||
DOI 10.17487/RFC7478, March 2015, | DOI 10.17487/RFC7478, March 2015, | |||
<https://www.rfc-editor.org/info/rfc7478>. | <https://www.rfc-editor.org/info/rfc7478>. | |||
[RFC8827] Rescorla, E., "WebRTC Security Architecture", RFC 8827, | [RFC8827] Rescorla, E., "WebRTC Security Architecture", RFC 8827, | |||
DOI 10.17487/RFC8827, July 2020, | DOI 10.17487/RFC8827, January 2021, | |||
<https://www.rfc-editor.org/info/rfc8827>. | <https://www.rfc-editor.org/info/rfc8827>. | |||
[RFC8835] Alvestrand, H., "Transports for WebRTC", RFC 8835, | [RFC8835] Alvestrand, H., "Transports for WebRTC", RFC 8835, | |||
DOI 10.17487/RFC8835, July 2020, | DOI 10.17487/RFC8835, January 2021, | |||
<https://www.rfc-editor.org/info/rfc8835>. | <https://www.rfc-editor.org/info/rfc8835>. | |||
Acknowledgements | Acknowledgements | |||
Several people provided input into this document, including Bernard | Several people provided input into this document, including Bernard | |||
Aboba, Harald Alvestrand, Youenn Fablet, Ted Hardie, Matthew | Aboba, Harald Alvestrand, Youenn Fablet, Ted Hardie, Matthew | |||
Kaufmann, Eric Rescorla, Adam Roach, and Martin Thomson. | Kaufmann, Eric Rescorla, Adam Roach, and Martin Thomson. | |||
Author's Address | Authors' Addresses | |||
Justin Uberti | Justin Uberti | |||
747 6th St S | 747 6th St S | |||
Kirkland, WA 98033 | Kirkland, WA 98033 | |||
United States of America | United States of America | |||
Email: justin@uberti.name | Email: justin@uberti.name | |||
Guo-wei Shieh | ||||
333 Elliott Ave W #500 | ||||
Seattle, WA 98119 | ||||
United States of America | ||||
Email: guoweis@gmail.com | ||||
End of changes. 7 change blocks. | ||||
7 lines changed or deleted | 7 lines changed or added | |||
This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/ |