draft-ietf-rtcweb-gateways-01.txt   draft-ietf-rtcweb-gateways-02.txt 
RTCWeb Working Group H. Alvestrand RTCWeb Working Group H. Alvestrand
Internet-Draft Google Internet-Draft Google
Intended status: Standards Track U. Rauschenbach Intended status: Standards Track U. Rauschenbach
Expires: January 7, 2016 Nokia Networks Expires: July 24, 2016 Nokia Networks
July 6, 2015 January 21, 2016
WebRTC Gateways WebRTC Gateways
draft-ietf-rtcweb-gateways-01 draft-ietf-rtcweb-gateways-02
Abstract Abstract
This document describes interoperability considerations for a class This document describes interoperability considerations for a class
of WebRTC-compatible endpoints called "WebRTC gateways", which of WebRTC-compatible endpoints called "WebRTC gateways", which
interconnect between WebRTC endpoints and devices that are not WebRTC interconnect between WebRTC endpoints and devices that are not WebRTC
endpoints. endpoints.
Requirements Language Requirements Language
skipping to change at page 1, line 40 skipping to change at page 1, line 40
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 http://datatracker.ietf.org/drafts/current/. Drafts is at http://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 7, 2016. This Internet-Draft will expire on July 24, 2016.
Copyright Notice Copyright Notice
Copyright (c) 2015 IETF Trust and the persons identified as the Copyright (c) 2016 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
(http://trustee.ietf.org/license-info) in effect on the date of (http://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 page 2, line 23 skipping to change at page 2, line 23
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1. Implications of the gateway environment . . . . . . . . . 3 1.1. Implications of the gateway environment . . . . . . . . . 3
1.2. Signalling model . . . . . . . . . . . . . . . . . . . . 3 1.2. Signalling model . . . . . . . . . . . . . . . . . . . . 3
2. WebRTC non-browser requirements that can be relaxed . . . . . 4 2. WebRTC non-browser requirements that can be relaxed . . . . . 4
3. Additional WebRTC gateway requirements . . . . . . . . . . . 4 3. Additional WebRTC gateway requirements . . . . . . . . . . . 4
4. Considerations for SDP-using networks . . . . . . . . . . . . 5 4. Considerations for SDP-using networks . . . . . . . . . . . . 5
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5
6. Security Considerations . . . . . . . . . . . . . . . . . . . 5 6. Security Considerations . . . . . . . . . . . . . . . . . . . 5
7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 6 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 6
8. Change history . . . . . . . . . . . . . . . . . . . . . . . 6 8. Change history . . . . . . . . . . . . . . . . . . . . . . . 6
9. References . . . . . . . . . . . . . . . . . . . . . . . . . 6 9. References . . . . . . . . . . . . . . . . . . . . . . . . . 7
9.1. Normative References . . . . . . . . . . . . . . . . . . 7 9.1. Normative References . . . . . . . . . . . . . . . . . . 7
9.2. Informative References . . . . . . . . . . . . . . . . . 7 9.2. Informative References . . . . . . . . . . . . . . . . . 7
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 7 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 7
1. Introduction 1. Introduction
The WebRTC model described in [I-D.ietf-rtcweb-overview] is focused The WebRTC model described in [I-D.ietf-rtcweb-overview] is focused
on direct browser to browser communication as its primary use case. on direct browser to browser communication as its primary use case.
Nevertheless, it is clearly interesting to have WebRTC endpoints Nevertheless, it is clearly interesting to have WebRTC endpoints
connect to other types of devices, including but not limited to SIP connect to other types of devices, including but not limited to SIP
skipping to change at page 6, line 48 skipping to change at page 6, line 48
o Addressed a comment from Andrew Hutton that deployment in open o Addressed a comment from Andrew Hutton that deployment in open
internet is an option, not a fact. internet is an option, not a fact.
Changes from draft-ietf-rtcweb-gateways-00 Changes from draft-ietf-rtcweb-gateways-00
o Added note about impllications of non-support of BUNDLE o Added note about impllications of non-support of BUNDLE
o Added "Considerations for SDP-using networks" section o Added "Considerations for SDP-using networks" section
Changes from draft-ietf-rtcweb-gateways-01: None, this is a keepalive
update.
9. References 9. References
9.1. Normative References 9.1. Normative References
[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-09 Session Establishment Protocol", draft-ietf-rtcweb-jsep-09
(work in progress), March 2015. (work in progress), March 2015.
[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-13 Browser-based Applications", draft-ietf-rtcweb-overview-13
 End of changes. 7 change blocks. 
6 lines changed or deleted 10 lines changed or added

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