draft-ietf-rum-rue-00.txt   draft-ietf-rum-rue-01.txt 
rum B. Rosen rum B. Rosen
Internet-Draft 24 September 2019 Internet-Draft 4 November 2019
Intended status: Standards Track Intended status: Standards Track
Expires: 27 March 2020 Expires: 7 May 2020
Interoperability Profile for Relay User Equipment Interoperability Profile for Relay User Equipment
draft-ietf-rum-rue-00 draft-ietf-rum-rue-01
Abstract Abstract
Video Relay Service (VRS) is a term used to describe a method by Video Relay Service (VRS) is a term used to describe a method by
which a hearing persons can communicate with deaf/Hard of Hearing which a hearing persons can communicate with deaf/Hard of Hearing
user using an interpreter ("Communications Assistant") connected via user using an interpreter ("Communications Assistant") connected via
a videophone to the deaf/HoH user and an audio telephone call to the a videophone to the deaf/HoH user and an audio telephone call to the
hearing user. The CA interprets using sign language on the hearing user. The CA interprets using sign language on the
videophone link and voice on the telephone link. Often the videophone link and voice on the telephone link. Often the
interpreters may be supplied by a company or agency termed a interpreters may be supplied by a company or agency termed a
skipping to change at page 1, line 43 skipping to change at page 1, line 43
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 27 March 2020. This Internet-Draft will expire on 7 May 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 (https://trustee.ietf.org/ Provisions Relating to IETF Documents (https://trustee.ietf.org/
license-info) in effect on the date of publication of this document. license-info) in effect on the date of publication of this document.
Please review these documents carefully, as they describe your rights Please review these documents carefully, as they describe your rights
skipping to change at page 2, line 36 skipping to change at page 2, line 36
5.2.4. Incoming Calls . . . . . . . . . . . . . . . . . . . 10 5.2.4. Incoming Calls . . . . . . . . . . . . . . . . . . . 10
5.2.5. Emergency Calls . . . . . . . . . . . . . . . . . . . 10 5.2.5. Emergency Calls . . . . . . . . . . . . . . . . . . . 10
5.3. Mid Call Signaling . . . . . . . . . . . . . . . . . . . 11 5.3. Mid Call Signaling . . . . . . . . . . . . . . . . . . . 11
5.4. URI Representation of Phone Numbers . . . . . . . . . . . 11 5.4. URI Representation of Phone Numbers . . . . . . . . . . . 11
5.5. Transport . . . . . . . . . . . . . . . . . . . . . . . . 11 5.5. Transport . . . . . . . . . . . . . . . . . . . . . . . . 11
6. Media . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 6. Media . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
6.1. SRTP and SRTCP . . . . . . . . . . . . . . . . . . . . . 12 6.1. SRTP and SRTCP . . . . . . . . . . . . . . . . . . . . . 12
6.2. Text-Based Communication . . . . . . . . . . . . . . . . 12 6.2. Text-Based Communication . . . . . . . . . . . . . . . . 12
6.3. Video . . . . . . . . . . . . . . . . . . . . . . . . . . 12 6.3. Video . . . . . . . . . . . . . . . . . . . . . . . . . . 12
6.4. Audio . . . . . . . . . . . . . . . . . . . . . . . . . . 12 6.4. Audio . . . . . . . . . . . . . . . . . . . . . . . . . . 12
6.5. DTMF Digits . . . . . . . . . . . . . . . . . . . . . . . 12 6.5. DTMF Digits . . . . . . . . . . . . . . . . . . . . . . . 13
6.6. Session Description Protocol . . . . . . . . . . . . . . 13 6.6. Session Description Protocol . . . . . . . . . . . . . . 13
6.7. Privacy . . . . . . . . . . . . . . . . . . . . . . . . . 13 6.7. Privacy . . . . . . . . . . . . . . . . . . . . . . . . . 13
6.8. Negative Acknowledgment, Packet Loss Indicator, and 6.8. Negative Acknowledgment, Packet Loss Indicator, and
Full Intraframe Request Features . . . . . . . . . . . . 13 Full Intraframe Request Features . . . . . . . . . . . . 13
7. Contacts . . . . . . . . . . . . . . . . . . . . . . . . . . 13 7. Contacts . . . . . . . . . . . . . . . . . . . . . . . . . . 13
7.1. CardDAV Login and Synchronization . . . . . . . . . . . . 13 7.1. CardDAV Login and Synchronization . . . . . . . . . . . . 13
7.2. Contacts Import/Export Service . . . . . . . . . . . . . 14 7.2. Contacts Import/Export Service . . . . . . . . . . . . . 14
8. Mail Waiting Indicator (MWI) . . . . . . . . . . . . . . . . 14 8. Mail Waiting Indicator (MWI) . . . . . . . . . . . . . . . . 14
9. Provisioning and Provider Selection . . . . . . . . . . . . . 14 9. Provisioning and Provider Selection . . . . . . . . . . . . . 14
9.1. RUE Provider Selection . . . . . . . . . . . . . . . . . 14 9.1. RUE Provider Selection . . . . . . . . . . . . . . . . . 14
9.2. RUE Configuration Service . . . . . . . . . . . . . . . . 15 9.2. RUE Configuration Service . . . . . . . . . . . . . . . . 16
9.3. Schemas . . . . . . . . . . . . . . . . . . . . . . . . . 19 9.3. Schemas . . . . . . . . . . . . . . . . . . . . . . . . . 19
10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 22 10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 22
11. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 22 11. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 22
12. Security Considerations . . . . . . . . . . . . . . . . . . . 22 12. Security Considerations . . . . . . . . . . . . . . . . . . . 22
13. Normative References . . . . . . . . . . . . . . . . . . . . 22 13. Normative References . . . . . . . . . . . . . . . . . . . . 22
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 28 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 28
1. Introduction 1. Introduction
Video Relay Service (VRS) is a form of Telecommunications Relay Video Relay Service (VRS) is a form of Telecommunications Relay
skipping to change at page 12, line 12 skipping to change at page 12, line 12
The RUE and providers MUST support SIP outbound [RFC5626] (please The RUE and providers MUST support SIP outbound [RFC5626] (please
also refer to Section 5.1). also refer to Section 5.1).
6. Media 6. Media
This specification adopts the media specifications for WebRTC This specification adopts the media specifications for WebRTC
([I-D.ietf-rtcweb-overview]). Where WebRTC defines how interactive ([I-D.ietf-rtcweb-overview]). Where WebRTC defines how interactive
media communications may be established using a browser as a client, media communications may be established using a browser as a client,
this specification assumes a normal SIP call. The RTP, RTCP, SDP and this specification assumes a normal SIP call. The RTP, RTCP, SDP and
specific media requirements specified for WebRTC are adopted for this specific media requirements specified for WebRTC are adopted for this
document. The following sections specify the WebRTC documents to document. The RUE is a WebRTC non-browser" endpoint, except as noted
which conformance is required. expressly below.
The following sections specify the WebRTC documents to which
conformance is required. "Mandatory to Implement" means a conforming
implementation must implement the specified capability. It does not
mean that the capabity must be used in every session. For example,
OPUS is a mandatory to implement audio codec, and all conforming
implementations must support OPUS. However, a call that originates
in the Public Switched Telephone Network, which only offers G.711
audio does not need to include the OPUS codec in the offer, since it
cannot be used with that call.
6.1. SRTP and SRTCP 6.1. SRTP and SRTCP
The RUE and Providers MUST support [I-D.ietf-rtcweb-rtp-usage] with The RUE and Providers MUST support [I-D.ietf-rtcweb-rtp-usage] with
the understanding that RUE does not specify an API and therefore the understanding that RUE does not specify an API and therefore
MediaStreamTracks are not used. Implementations MUST conform to MediaStreamTracks are not used. Implementations MUST conform to
Section 6.4 of [I-D.ietf-rtcweb-security-arch]. Section 6.4 of [I-D.ietf-rtcweb-security-arch].
6.2. Text-Based Communication 6.2. Text-Based Communication
skipping to change at page 13, line 18 skipping to change at page 13, line 25
the understanding that the RUE uses SIP transport for SDP. the understanding that the RUE uses SIP transport for SDP.
6.7. Privacy 6.7. Privacy
The RUE MUST be able to control privacy of the user by implementing a The RUE MUST be able to control privacy of the user by implementing a
one-way mute of audio and or video, without signaling, locally, but one-way mute of audio and or video, without signaling, locally, but
MUST maintain any NAT bindings by periodically sending media packets MUST maintain any NAT bindings by periodically sending media packets
on all active media sessions containing silence/comfort noise/black on all active media sessions containing silence/comfort noise/black
screen/etc. per [RFC6263]. screen/etc. per [RFC6263].
6.8. Negative Acknowledgment, Packet Loss Indicator, and Full Intraframe 6.8. Negative Acknowledgment, Packet Loss Indicator, and Full
Request Features Intraframe Request Features
NACK SHOULD be used when negotiated and conditions warrant its use. NACK SHOULD be used when negotiated and conditions warrant its use.
Signaling picture losses as Packet Loss Indicator (PLI) SHOULD be Signaling picture losses as Packet Loss Indicator (PLI) SHOULD be
preferred, as described in [RFC5104]. preferred, as described in [RFC5104].
FIR SHOULD be used only in situations where not sending a decoder FIR SHOULD be used only in situations where not sending a decoder
refresh point would render the video unusable for the users, as per refresh point would render the video unusable for the users, as per
RFC5104 subsection 4.3.1.2. RFC5104 subsection 4.3.1.2.
For backwards compatibility with calling devices that do not support For backwards compatibility with calling devices that do not support
skipping to change at page 22, line 32 skipping to change at page 22, line 32
it is necessary for the RUE to function on a corporate or other it is necessary for the RUE to function on a corporate or other
network that operates a default-deny firewall between the RUE and network that operates a default-deny firewall between the RUE and
these services, the user must arrange with their network manager for these services, the user must arrange with their network manager for
passage of traffic through such a firewall in accordance with the passage of traffic through such a firewall in accordance with the
protocols and associated SRV records as exposed by the Provider. protocols and associated SRV records as exposed by the Provider.
Because VRS providers may use different ports for different services, Because VRS providers may use different ports for different services,
these port numbers may differ from Provider to Provider. these port numbers may differ from Provider to Provider.
13. Normative References 13. Normative References
[I-D.ietf-rtcweb-jsep]
Uberti, J., Jennings, C., and E. Rescorla, "JavaScript
Session Establishment Protocol", Internet-Draft, draft-
ietf-rtcweb-jsep-26, 27 February 2019,
<http://www.ietf.org/internet-drafts/draft-ietf-rtcweb-
jsep-26.txt>.
[I-D.ietf-rtcweb-overview]
Alvestrand, H., "Overview: Real Time Protocols for
Browser-based Applications", Internet-Draft, draft-ietf-
rtcweb-overview-19, 11 November 2017,
<http://www.ietf.org/internet-drafts/draft-ietf-rtcweb-
overview-19.txt>.
[I-D.ietf-rtcweb-rtp-usage]
Perkins, C., Westerlund, M., and J. Ott, "Web Real-Time
Communication (WebRTC): Media Transport and Use of RTP",
Internet-Draft, draft-ietf-rtcweb-rtp-usage-26, 17 March
2016,
<http://www.ietf.org/internet-drafts/draft-ietf-rtcweb-
rtp-usage-26.txt>.
[I-D.ietf-rtcweb-security-arch]
Rescorla, E., "WebRTC Security Architecture", Internet-
Draft, draft-ietf-rtcweb-security-arch-20, 22 July 2019,
<http://www.ietf.org/internet-drafts/draft-ietf-rtcweb-
security-arch-20.txt>.
[I-D.ietf-rtcweb-transports]
Alvestrand, H., "Transports for WebRTC", Internet-Draft,
draft-ietf-rtcweb-transports-17, 26 October 2016,
<http://www.ietf.org/internet-drafts/draft-ietf-rtcweb-
transports-17.txt>.
[I-D.yusef-sipcore-digest-scheme]
Shekh-Yusef, R., "The Session Initiation Protocol (SIP)
Digest Authentication Scheme", Internet-Draft, draft-
yusef-sipcore-digest-scheme-07, 1 April 2019,
<http://www.ietf.org/internet-drafts/draft-yusef-sipcore-
digest-scheme-07.txt>.
[pip] SIPForum, "VRS US Providers Profile TWG-6-1.0", 2015,
<https://www.sipforum.org/download/vrs-us-providers-
profile-twg-6-1-0-pdf/#>.
[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>.
[RFC2392] Levinson, E., "Content-ID and Message-ID Uniform Resource [RFC8446] Rescorla, E., "The Transport Layer Security (TLS) Protocol
Locators", RFC 2392, DOI 10.17487/RFC2392, August 1998, Version 1.3", RFC 8446, DOI 10.17487/RFC8446, August 2018,
<https://www.rfc-editor.org/info/rfc2392>. <https://www.rfc-editor.org/info/rfc8446>.
[RFC3261] Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston, [RFC3261] Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston,
A., Peterson, J., Sparks, R., Handley, M., and E. A., Peterson, J., Sparks, R., Handley, M., and E.
Schooler, "SIP: Session Initiation Protocol", RFC 3261, Schooler, "SIP: Session Initiation Protocol", RFC 3261,
DOI 10.17487/RFC3261, June 2002, DOI 10.17487/RFC3261, June 2002,
<https://www.rfc-editor.org/info/rfc3261>. <https://www.rfc-editor.org/info/rfc3261>.
[RFC3263] Rosenberg, J. and H. Schulzrinne, "Session Initiation [RFC3263] Rosenberg, J. and H. Schulzrinne, "Session Initiation
Protocol (SIP): Locating SIP Servers", RFC 3263, Protocol (SIP): Locating SIP Servers", RFC 3263,
DOI 10.17487/RFC3263, June 2002, DOI 10.17487/RFC3263, June 2002,
<https://www.rfc-editor.org/info/rfc3263>. <https://www.rfc-editor.org/info/rfc3263>.
[RFC3264] Rosenberg, J. and H. Schulzrinne, "An Offer/Answer Model [RFC3264] Rosenberg, J. and H. Schulzrinne, "An Offer/Answer Model
with Session Description Protocol (SDP)", RFC 3264, with Session Description Protocol (SDP)", RFC 3264,
DOI 10.17487/RFC3264, June 2002, DOI 10.17487/RFC3264, June 2002,
<https://www.rfc-editor.org/info/rfc3264>. <https://www.rfc-editor.org/info/rfc3264>.
[RFC3311] Rosenberg, J., "The Session Initiation Protocol (SIP) [RFC3840] Rosenberg, J., Schulzrinne, H., and P. Kyzivat,
UPDATE Method", RFC 3311, DOI 10.17487/RFC3311, October "Indicating User Agent Capabilities in the Session
2002, <https://www.rfc-editor.org/info/rfc3311>. Initiation Protocol (SIP)", RFC 3840,
DOI 10.17487/RFC3840, August 2004,
<https://www.rfc-editor.org/info/rfc3840>.
[RFC5626] Jennings, C., Ed., Mahy, R., Ed., and F. Audet, Ed.,
"Managing Client-Initiated Connections in the Session
Initiation Protocol (SIP)", RFC 5626,
DOI 10.17487/RFC5626, October 2009,
<https://www.rfc-editor.org/info/rfc5626>.
[RFC4566] Handley, M., Jacobson, V., and C. Perkins, "SDP: Session
Description Protocol", RFC 4566, DOI 10.17487/RFC4566,
July 2006, <https://www.rfc-editor.org/info/rfc4566>.
[RFC3323] Peterson, J., "A Privacy Mechanism for the Session [RFC3323] Peterson, J., "A Privacy Mechanism for the Session
Initiation Protocol (SIP)", RFC 3323, Initiation Protocol (SIP)", RFC 3323,
DOI 10.17487/RFC3323, November 2002, DOI 10.17487/RFC3323, November 2002,
<https://www.rfc-editor.org/info/rfc3323>. <https://www.rfc-editor.org/info/rfc3323>.
[RFC3326] Schulzrinne, H., Oran, D., and G. Camarillo, "The Reason [RFC3605] Huitema, C., "Real Time Control Protocol (RTCP) attribute
Header Field for the Session Initiation Protocol (SIP)", in Session Description Protocol (SDP)", RFC 3605,
RFC 3326, DOI 10.17487/RFC3326, December 2002, DOI 10.17487/RFC3605, October 2003,
<https://www.rfc-editor.org/info/rfc3326>. <https://www.rfc-editor.org/info/rfc3605>.
[RFC6665] Roach, A.B., "SIP-Specific Event Notification", RFC 6665,
DOI 10.17487/RFC6665, July 2012,
<https://www.rfc-editor.org/info/rfc6665>.
[RFC3311] Rosenberg, J., "The Session Initiation Protocol (SIP)
UPDATE Method", RFC 3311, DOI 10.17487/RFC3311, October
2002, <https://www.rfc-editor.org/info/rfc3311>.
[RFC5393] Sparks, R., Ed., Lawrence, S., Hawrylyshen, A., and B.
Campen, "Addressing an Amplification Vulnerability in
Session Initiation Protocol (SIP) Forking Proxies",
RFC 5393, DOI 10.17487/RFC5393, December 2008,
<https://www.rfc-editor.org/info/rfc5393>.
[RFC5658] Froment, T., Lebel, C., and B. Bonnaerens, "Addressing
Record-Route Issues in the Session Initiation Protocol
(SIP)", RFC 5658, DOI 10.17487/RFC5658, October 2009,
<https://www.rfc-editor.org/info/rfc5658>.
[RFC5954] Gurbani, V., Ed., Carpenter, B., Ed., and B. Tate, Ed.,
"Essential Correction for IPv6 ABNF and URI Comparison in
RFC 3261", RFC 5954, DOI 10.17487/RFC5954, August 2010,
<https://www.rfc-editor.org/info/rfc5954>.
[RFC3960] Camarillo, G. and H. Schulzrinne, "Early Media and Ringing
Tone Generation in the Session Initiation Protocol (SIP)",
RFC 3960, DOI 10.17487/RFC3960, December 2004,
<https://www.rfc-editor.org/info/rfc3960>.
[RFC6442] Polk, J., Rosen, B., and J. Peterson, "Location Conveyance
for the Session Initiation Protocol", RFC 6442,
DOI 10.17487/RFC6442, December 2011,
<https://www.rfc-editor.org/info/rfc6442>.
[RFC3327] Willis, D. and B. Hoeneisen, "Session Initiation Protocol [RFC3327] Willis, D. and B. Hoeneisen, "Session Initiation Protocol
(SIP) Extension Header Field for Registering Non-Adjacent (SIP) Extension Header Field for Registering Non-Adjacent
Contacts", RFC 3327, DOI 10.17487/RFC3327, December 2002, Contacts", RFC 3327, DOI 10.17487/RFC3327, December 2002,
<https://www.rfc-editor.org/info/rfc3327>. <https://www.rfc-editor.org/info/rfc3327>.
[RFC3458] Burger, E., Candell, E., Eliot, C., and G. Klyne, "Message [RFC5245] Rosenberg, J., "Interactive Connectivity Establishment
Context for Internet Mail", RFC 3458, (ICE): A Protocol for Network Address Translator (NAT)
DOI 10.17487/RFC3458, January 2003, Traversal for Offer/Answer Protocols", RFC 5245,
<https://www.rfc-editor.org/info/rfc3458>. DOI 10.17487/RFC5245, April 2010,
<https://www.rfc-editor.org/info/rfc5245>.
[RFC3326] Schulzrinne, H., Oran, D., and G. Camarillo, "The Reason
Header Field for the Session Initiation Protocol (SIP)",
RFC 3326, DOI 10.17487/RFC3326, December 2002,
<https://www.rfc-editor.org/info/rfc3326>.
[RFC3515] Sparks, R., "The Session Initiation Protocol (SIP) Refer [RFC3515] Sparks, R., "The Session Initiation Protocol (SIP) Refer
Method", RFC 3515, DOI 10.17487/RFC3515, April 2003, Method", RFC 3515, DOI 10.17487/RFC3515, April 2003,
<https://www.rfc-editor.org/info/rfc3515>. <https://www.rfc-editor.org/info/rfc3515>.
[RFC3605] Huitema, C., "Real Time Control Protocol (RTCP) attribute [RFC4488] Levin, O., "Suppression of Session Initiation Protocol
in Session Description Protocol (SDP)", RFC 3605, (SIP) REFER Method Implicit Subscription", RFC 4488,
DOI 10.17487/RFC3605, October 2003, DOI 10.17487/RFC4488, May 2006,
<https://www.rfc-editor.org/info/rfc3605>. <https://www.rfc-editor.org/info/rfc4488>.
[RFC3665] Johnston, A., Donovan, S., Sparks, R., Cunningham, C., and
K. Summers, "Session Initiation Protocol (SIP) Basic Call
Flow Examples", BCP 75, RFC 3665, DOI 10.17487/RFC3665,
December 2003, <https://www.rfc-editor.org/info/rfc3665>.
[RFC3840] Rosenberg, J., Schulzrinne, H., and P. Kyzivat,
"Indicating User Agent Capabilities in the Session
Initiation Protocol (SIP)", RFC 3840,
DOI 10.17487/RFC3840, August 2004,
<https://www.rfc-editor.org/info/rfc3840>.
[RFC3842] Mahy, R., "A Message Summary and Message Waiting [RFC7647] Sparks, R. and A.B. Roach, "Clarifications for the Use of
Indication Event Package for the Session Initiation REFER with RFC 6665", RFC 7647, DOI 10.17487/RFC7647,
Protocol (SIP)", RFC 3842, DOI 10.17487/RFC3842, August September 2015, <https://www.rfc-editor.org/info/rfc7647>.
2004, <https://www.rfc-editor.org/info/rfc3842>.
[RFC3891] Mahy, R., Biggs, B., and R. Dean, "The Session Initiation [RFC3891] Mahy, R., Biggs, B., and R. Dean, "The Session Initiation
Protocol (SIP) "Replaces" Header", RFC 3891, Protocol (SIP) "Replaces" Header", RFC 3891,
DOI 10.17487/RFC3891, September 2004, DOI 10.17487/RFC3891, September 2004,
<https://www.rfc-editor.org/info/rfc3891>. <https://www.rfc-editor.org/info/rfc3891>.
[RFC3892] Sparks, R., "The Session Initiation Protocol (SIP) [RFC3892] Sparks, R., "The Session Initiation Protocol (SIP)
Referred-By Mechanism", RFC 3892, DOI 10.17487/RFC3892, Referred-By Mechanism", RFC 3892, DOI 10.17487/RFC3892,
September 2004, <https://www.rfc-editor.org/info/rfc3892>. September 2004, <https://www.rfc-editor.org/info/rfc3892>.
[RFC3960] Camarillo, G. and H. Schulzrinne, "Early Media and Ringing [RFC3665] Johnston, A., Donovan, S., Sparks, R., Cunningham, C., and
Tone Generation in the Session Initiation Protocol (SIP)", K. Summers, "Session Initiation Protocol (SIP) Basic Call
RFC 3960, DOI 10.17487/RFC3960, December 2004, Flow Examples", BCP 75, RFC 3665, DOI 10.17487/RFC3665,
<https://www.rfc-editor.org/info/rfc3960>. December 2003, <https://www.rfc-editor.org/info/rfc3665>.
[RFC2392] Levinson, E., "Content-ID and Message-ID Uniform Resource
Locators", RFC 2392, DOI 10.17487/RFC2392, August 1998,
<https://www.rfc-editor.org/info/rfc2392>.
[RFC3966] Schulzrinne, H., "The tel URI for Telephone Numbers", [RFC3966] Schulzrinne, H., "The tel URI for Telephone Numbers",
RFC 3966, DOI 10.17487/RFC3966, December 2004, RFC 3966, DOI 10.17487/RFC3966, December 2004,
<https://www.rfc-editor.org/info/rfc3966>. <https://www.rfc-editor.org/info/rfc3966>.
[RFC4967] Rosen, B., "Dial String Parameter for the Session
Initiation Protocol Uniform Resource Identifier",
RFC 4967, DOI 10.17487/RFC4967, July 2007,
<https://www.rfc-editor.org/info/rfc4967>.
[RFC4102] Jones, P., "Registration of the text/red MIME Sub-Type", [RFC4102] Jones, P., "Registration of the text/red MIME Sub-Type",
RFC 4102, DOI 10.17487/RFC4102, June 2005, RFC 4102, DOI 10.17487/RFC4102, June 2005,
<https://www.rfc-editor.org/info/rfc4102>. <https://www.rfc-editor.org/info/rfc4102>.
[RFC4103] Hellstrom, G. and P. Jones, "RTP Payload for Text [RFC4103] Hellstrom, G. and P. Jones, "RTP Payload for Text
Conversation", RFC 4103, DOI 10.17487/RFC4103, June 2005, Conversation", RFC 4103, DOI 10.17487/RFC4103, June 2005,
<https://www.rfc-editor.org/info/rfc4103>. <https://www.rfc-editor.org/info/rfc4103>.
[RFC4488] Levin, O., "Suppression of Session Initiation Protocol
(SIP) REFER Method Implicit Subscription", RFC 4488,
DOI 10.17487/RFC4488, May 2006,
<https://www.rfc-editor.org/info/rfc4488>.
[RFC4566] Handley, M., Jacobson, V., and C. Perkins, "SDP: Session
Description Protocol", RFC 4566, DOI 10.17487/RFC4566,
July 2006, <https://www.rfc-editor.org/info/rfc4566>.
[RFC4733] Schulzrinne, H. and T. Taylor, "RTP Payload for DTMF [RFC4733] Schulzrinne, H. and T. Taylor, "RTP Payload for DTMF
Digits, Telephony Tones, and Telephony Signals", RFC 4733, Digits, Telephony Tones, and Telephony Signals", RFC 4733,
DOI 10.17487/RFC4733, December 2006, DOI 10.17487/RFC4733, December 2006,
<https://www.rfc-editor.org/info/rfc4733>. <https://www.rfc-editor.org/info/rfc4733>.
[RFC4967] Rosen, B., "Dial String Parameter for the Session [RFC6263] Marjou, X. and A. Sollaud, "Application Mechanism for
Initiation Protocol Uniform Resource Identifier", Keeping Alive the NAT Mappings Associated with RTP / RTP
RFC 4967, DOI 10.17487/RFC4967, July 2007, Control Protocol (RTCP) Flows", RFC 6263,
<https://www.rfc-editor.org/info/rfc4967>. DOI 10.17487/RFC6263, June 2011,
<https://www.rfc-editor.org/info/rfc6263>.
[RFC5104] Wenger, S., Chandra, U., Westerlund, M., and B. Burman, [RFC5104] Wenger, S., Chandra, U., Westerlund, M., and B. Burman,
"Codec Control Messages in the RTP Audio-Visual Profile "Codec Control Messages in the RTP Audio-Visual Profile
with Feedback (AVPF)", RFC 5104, DOI 10.17487/RFC5104, with Feedback (AVPF)", RFC 5104, DOI 10.17487/RFC5104,
February 2008, <https://www.rfc-editor.org/info/rfc5104>. February 2008, <https://www.rfc-editor.org/info/rfc5104>.
[RFC5168] Levin, O., Even, R., and P. Hagendorf, "XML Schema for [RFC5168] Levin, O., Even, R., and P. Hagendorf, "XML Schema for
Media Control", RFC 5168, DOI 10.17487/RFC5168, March Media Control", RFC 5168, DOI 10.17487/RFC5168, March
2008, <https://www.rfc-editor.org/info/rfc5168>. 2008, <https://www.rfc-editor.org/info/rfc5168>.
[RFC5245] Rosenberg, J., "Interactive Connectivity Establishment
(ICE): A Protocol for Network Address Translator (NAT)
Traversal for Offer/Answer Protocols", RFC 5245,
DOI 10.17487/RFC5245, April 2010,
<https://www.rfc-editor.org/info/rfc5245>.
[RFC5393] Sparks, R., Ed., Lawrence, S., Hawrylyshen, A., and B.
Campen, "Addressing an Amplification Vulnerability in
Session Initiation Protocol (SIP) Forking Proxies",
RFC 5393, DOI 10.17487/RFC5393, December 2008,
<https://www.rfc-editor.org/info/rfc5393>.
[RFC5626] Jennings, C., Ed., Mahy, R., Ed., and F. Audet, Ed.,
"Managing Client-Initiated Connections in the Session
Initiation Protocol (SIP)", RFC 5626,
DOI 10.17487/RFC5626, October 2009,
<https://www.rfc-editor.org/info/rfc5626>.
[RFC5658] Froment, T., Lebel, C., and B. Bonnaerens, "Addressing
Record-Route Issues in the Session Initiation Protocol
(SIP)", RFC 5658, DOI 10.17487/RFC5658, October 2009,
<https://www.rfc-editor.org/info/rfc5658>.
[RFC5954] Gurbani, V., Ed., Carpenter, B., Ed., and B. Tate, Ed.,
"Essential Correction for IPv6 ABNF and URI Comparison in
RFC 3261", RFC 5954, DOI 10.17487/RFC5954, August 2010,
<https://www.rfc-editor.org/info/rfc5954>.
[RFC6263] Marjou, X. and A. Sollaud, "Application Mechanism for
Keeping Alive the NAT Mappings Associated with RTP / RTP
Control Protocol (RTCP) Flows", RFC 6263,
DOI 10.17487/RFC6263, June 2011,
<https://www.rfc-editor.org/info/rfc6263>.
[RFC6351] Perreault, S., "xCard: vCard XML Representation",
RFC 6351, DOI 10.17487/RFC6351, August 2011,
<https://www.rfc-editor.org/info/rfc6351>.
[RFC6352] Daboo, C., "CardDAV: vCard Extensions to Web Distributed [RFC6352] Daboo, C., "CardDAV: vCard Extensions to Web Distributed
Authoring and Versioning (WebDAV)", RFC 6352, Authoring and Versioning (WebDAV)", RFC 6352,
DOI 10.17487/RFC6352, August 2011, DOI 10.17487/RFC6352, August 2011,
<https://www.rfc-editor.org/info/rfc6352>. <https://www.rfc-editor.org/info/rfc6352>.
[RFC6442] Polk, J., Rosen, B., and J. Peterson, "Location Conveyance
for the Session Initiation Protocol", RFC 6442,
DOI 10.17487/RFC6442, December 2011,
<https://www.rfc-editor.org/info/rfc6442>.
[RFC6665] Roach, A.B., "SIP-Specific Event Notification", RFC 6665,
DOI 10.17487/RFC6665, July 2012,
<https://www.rfc-editor.org/info/rfc6665>.
[RFC6764] Daboo, C., "Locating Services for Calendaring Extensions [RFC6764] Daboo, C., "Locating Services for Calendaring Extensions
to WebDAV (CalDAV) and vCard Extensions to WebDAV to WebDAV (CalDAV) and vCard Extensions to WebDAV
(CardDAV)", RFC 6764, DOI 10.17487/RFC6764, February 2013, (CardDAV)", RFC 6764, DOI 10.17487/RFC6764, February 2013,
<https://www.rfc-editor.org/info/rfc6764>. <https://www.rfc-editor.org/info/rfc6764>.
[RFC6881] Rosen, B. and J. Polk, "Best Current Practice for [RFC6351] Perreault, S., "xCard: vCard XML Representation",
Communications Services in Support of Emergency Calling", RFC 6351, DOI 10.17487/RFC6351, August 2011,
BCP 181, RFC 6881, DOI 10.17487/RFC6881, March 2013, <https://www.rfc-editor.org/info/rfc6351>.
<https://www.rfc-editor.org/info/rfc6881>.
[RFC3842] Mahy, R., "A Message Summary and Message Waiting
Indication Event Package for the Session Initiation
Protocol (SIP)", RFC 3842, DOI 10.17487/RFC3842, August
2004, <https://www.rfc-editor.org/info/rfc3842>.
[RFC3458] Burger, E., Candell, E., Eliot, C., and G. Klyne, "Message
Context for Internet Mail", RFC 3458,
DOI 10.17487/RFC3458, January 2003,
<https://www.rfc-editor.org/info/rfc3458>.
[RFC7159] Bray, T., Ed., "The JavaScript Object Notation (JSON) Data [RFC7159] Bray, T., Ed., "The JavaScript Object Notation (JSON) Data
Interchange Format", RFC 7159, DOI 10.17487/RFC7159, March Interchange Format", RFC 7159, DOI 10.17487/RFC7159, March
2014, <https://www.rfc-editor.org/info/rfc7159>. 2014, <https://www.rfc-editor.org/info/rfc7159>.
[RFC7525] Sheffer, Y., Holz, R., and P. Saint-Andre, [RFC7525] Sheffer, Y., Holz, R., and P. Saint-Andre,
"Recommendations for Secure Use of Transport Layer "Recommendations for Secure Use of Transport Layer
Security (TLS) and Datagram Transport Layer Security Security (TLS) and Datagram Transport Layer Security
(DTLS)", BCP 195, RFC 7525, DOI 10.17487/RFC7525, May (DTLS)", BCP 195, RFC 7525, DOI 10.17487/RFC7525, May
2015, <https://www.rfc-editor.org/info/rfc7525>. 2015, <https://www.rfc-editor.org/info/rfc7525>.
[RFC7647] Sparks, R. and A.B. Roach, "Clarifications for the Use of [RFC6881] Rosen, B. and J. Polk, "Best Current Practice for
REFER with RFC 6665", RFC 7647, DOI 10.17487/RFC7647, Communications Services in Support of Emergency Calling",
September 2015, <https://www.rfc-editor.org/info/rfc7647>. BCP 181, RFC 6881, DOI 10.17487/RFC6881, March 2013,
<https://www.rfc-editor.org/info/rfc6881>.
[RFC7742] Roach, A.B., "WebRTC Video Processing and Codec [I-D.ietf-rtcweb-overview]
Requirements", RFC 7742, DOI 10.17487/RFC7742, March 2016, Alvestrand, H., "Overview: Real Time Protocols for
<https://www.rfc-editor.org/info/rfc7742>. Browser-based Applications", Work in Progress, Internet-
Draft, draft-ietf-rtcweb-overview-19, 11 November 2017,
<http://www.ietf.org/internet-drafts/draft-ietf-rtcweb-
overview-19.txt>.
[I-D.ietf-rtcweb-rtp-usage]
Perkins, C., Westerlund, M., and J. Ott, "Web Real-Time
Communication (WebRTC): Media Transport and Use of RTP",
Work in Progress, Internet-Draft, draft-ietf-rtcweb-rtp-
usage-26, 17 March 2016, <http://www.ietf.org/internet-
drafts/draft-ietf-rtcweb-rtp-usage-26.txt>.
[I-D.ietf-rtcweb-jsep]
Uberti, J., Jennings, C., and E. Rescorla, "JavaScript
Session Establishment Protocol", Work in Progress,
Internet-Draft, draft-ietf-rtcweb-jsep-26, 27 February
2019, <http://www.ietf.org/internet-drafts/draft-ietf-
rtcweb-jsep-26.txt>.
[RFC7874] Valin, JM. and C. Bran, "WebRTC Audio Codec and Processing [RFC7874] Valin, JM. and C. Bran, "WebRTC Audio Codec and Processing
Requirements", RFC 7874, DOI 10.17487/RFC7874, May 2016, Requirements", RFC 7874, DOI 10.17487/RFC7874, May 2016,
<https://www.rfc-editor.org/info/rfc7874>. <https://www.rfc-editor.org/info/rfc7874>.
[RFC8446] Rescorla, E., "The Transport Layer Security (TLS) Protocol [RFC7742] Roach, A.B., "WebRTC Video Processing and Codec
Version 1.3", RFC 8446, DOI 10.17487/RFC8446, August 2018, Requirements", RFC 7742, DOI 10.17487/RFC7742, March 2016,
<https://www.rfc-editor.org/info/rfc8446>. <https://www.rfc-editor.org/info/rfc7742>.
[I-D.ietf-rtcweb-transports]
Alvestrand, H., "Transports for WebRTC", Work in Progress,
Internet-Draft, draft-ietf-rtcweb-transports-17, 26
October 2016, <http://www.ietf.org/internet-drafts/draft-
ietf-rtcweb-transports-17.txt>.
[I-D.ietf-rtcweb-security-arch]
Rescorla, E., "WebRTC Security Architecture", Work in
Progress, Internet-Draft, draft-ietf-rtcweb-security-arch-
20, 22 July 2019, <http://www.ietf.org/internet-drafts/
draft-ietf-rtcweb-security-arch-20.txt>.
[I-D.yusef-sipcore-digest-scheme]
Shekh-Yusef, R., "The Session Initiation Protocol (SIP)
Digest Authentication Scheme", Work in Progress, Internet-
Draft, draft-yusef-sipcore-digest-scheme-07, 1 April 2019,
<http://www.ietf.org/internet-drafts/draft-yusef-sipcore-
digest-scheme-07.txt>.
[pip] SIPForum, "VRS US Providers Profile TWG-6-1.0", 2015,
<https://www.sipforum.org/download/vrs-us-providers-
profile-twg-6-1-0-pdf/#>.
Author's Address Author's Address
Brian Rosen Brian Rosen
470 Conrad Dr 470 Conrad Dr
Mars, PA 16046 Mars, PA 16046
United States of America United States of America
Phone: +1 724 382 1051 Phone: +1 724 382 1051
Email: br@brianrosen.net Email: br@brianrosen.net
 End of changes. 25 change blocks. 
165 lines changed or deleted 174 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/