| 1 |
<pre>Internet Engineering Task Force (IETF) D. Hanes |
| 2 |
Request for Comments: 6913 G. Salgueiro |
| 3 |
Category: Standards Track Cisco Systems |
| 4 |
ISSN: 2070-1721 K. Fleming |
| 5 |
Digium, Inc. |
| 6 |
March 2013 |
| 7 |
|
| 8 |
|
| 9 |
<span class="h1">Indicating Fax over IP Capability</span> |
| 10 |
<span class="h1">in the Session Initiation Protocol (SIP)</span> |
| 11 |
|
| 12 |
Abstract |
| 13 |
|
| 14 |
This document defines and registers with IANA the new "fax" media |
| 15 |
feature tag for use with the Session Initiation Protocol (SIP). |
| 16 |
Currently, fax calls are indistinguishable from voice calls at call |
| 17 |
initiation. Consequently, fax calls can be routed to SIP user agents |
| 18 |
that are not fax capable. A "fax" media feature tag implemented in |
| 19 |
conjunction with caller preferences allows for more accurate fax call |
| 20 |
routing. |
| 21 |
|
| 22 |
Status of This Memo |
| 23 |
|
| 24 |
This is an Internet Standards Track document. |
| 25 |
|
| 26 |
This document is a product of the Internet Engineering Task Force |
| 27 |
(IETF). It represents the consensus of the IETF community. It has |
| 28 |
received public review and has been approved for publication by the |
| 29 |
Internet Engineering Steering Group (IESG). Further information on |
| 30 |
Internet Standards is available in <a href="./rfc5741#section-2">Section 2 of RFC 5741</a>. |
| 31 |
|
| 32 |
Information about the current status of this document, any errata, |
| 33 |
and how to provide feedback on it may be obtained at |
| 34 |
<a href="http://www.rfc-editor.org/info/rfc6913">http://www.rfc-editor.org/info/rfc6913</a>. |
| 35 |
|
| 36 |
|
| 37 |
|
| 38 |
|
| 39 |
|
| 40 |
|
| 41 |
|
| 42 |
|
| 43 |
|
| 44 |
|
| 45 |
|
| 46 |
|
| 47 |
|
| 48 |
|
| 49 |
|
| 50 |
|
| 51 |
|
| 52 |
<span class="grey">Hanes, et al. Standards Track [Page 1]</span></pre> |
| 53 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span> |
| 54 |
<span class="grey"><a href="./rfc6913">RFC 6913</a> Fax Media Feature Tag March 2013</span> |
| 55 |
|
| 56 |
|
| 57 |
Copyright Notice |
| 58 |
|
| 59 |
Copyright (c) 2013 IETF Trust and the persons identified as the |
| 60 |
document authors. All rights reserved. |
| 61 |
|
| 62 |
This document is subject to <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and the IETF Trust's Legal |
| 63 |
Provisions Relating to IETF Documents |
| 64 |
(<a href="http://trustee.ietf.org/license-info">http://trustee.ietf.org/license-info</a>) in effect on the date of |
| 65 |
publication of this document. Please review these documents |
| 66 |
carefully, as they describe your rights and restrictions with respect |
| 67 |
to this document. Code Components extracted from this document must |
| 68 |
include Simplified BSD License text as described in Section 4.e of |
| 69 |
the Trust Legal Provisions and are provided without warranty as |
| 70 |
described in the Simplified BSD License. |
| 71 |
|
| 72 |
Table of Contents |
| 73 |
|
| 74 |
<a href="#section-1">1</a>. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-2">2</a> |
| 75 |
<a href="#section-2">2</a>. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-3">3</a> |
| 76 |
<a href="#section-3">3</a>. Motivation . . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-3">3</a> |
| 77 |
<a href="#section-4">4</a>. Usage of the "sip.fax" Parameter . . . . . . . . . . . . . . . <a href="#page-4">4</a> |
| 78 |
<a href="#section-5">5</a>. Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-5">5</a> |
| 79 |
<a href="#section-6">6</a>. Security Considerations . . . . . . . . . . . . . . . . . . . . <a href="#page-6">6</a> |
| 80 |
<a href="#section-7">7</a>. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . <a href="#page-6">6</a> |
| 81 |
<a href="#section-8">8</a>. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-7">7</a> |
| 82 |
<a href="#section-9">9</a>. References . . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-7">7</a> |
| 83 |
<a href="#section-9.1">9.1</a>. Normative References . . . . . . . . . . . . . . . . . . . <a href="#page-7">7</a> |
| 84 |
<a href="#section-9.2">9.2</a>. Informative References . . . . . . . . . . . . . . . . . . <a href="#page-8">8</a> |
| 85 |
|
| 86 |
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span> |
| 87 |
|
| 88 |
Fax communications in the Session Initiation Protocol (SIP) [<a href="./rfc3261" title=""SIP: Session Initiation Protocol"">RFC3261</a>] |
| 89 |
are handled in a "voice first" manner. Indications that a user |
| 90 |
desires to use a fax transport protocol, such as ITU-T T.38 [<a href="#ref-T38" title=""Procedures for real-time Group 3 facsimile communication over IP Networks"">T38</a>], to |
| 91 |
send a fax are not known when the initial INVITE message is sent. |
| 92 |
The call is set up as a voice call first, and then, only after it is |
| 93 |
connected, does a switchover to the T.38 [<a href="#ref-T38" title=""Procedures for real-time Group 3 facsimile communication over IP Networks"">T38</a>] protocol occur. This |
| 94 |
is problematic in that fax calls can be routed inadvertently to SIP |
| 95 |
user agents (UAs) that are not fax capable. |
| 96 |
|
| 97 |
To ensure that fax calls are routed to fax-capable SIP UAs, an |
| 98 |
implementation of caller preferences defined in <a href="./rfc3841">RFC 3841</a> [<a href="./rfc3841" title=""Caller Preferences for the Session Initiation Protocol (SIP)"">RFC3841</a>] |
| 99 |
can be used. Feature preferences are a part of <a href="./rfc3841">RFC 3841</a> [<a href="./rfc3841" title=""Caller Preferences for the Session Initiation Protocol (SIP)"">RFC3841</a>] |
| 100 |
that would allow UAs to express their preference for receiving fax |
| 101 |
communications. Subsequently, SIP servers take these preferences |
| 102 |
into account to increase the likelihood that fax calls are routed to |
| 103 |
fax-capable SIP UAs. |
| 104 |
|
| 105 |
|
| 106 |
|
| 107 |
|
| 108 |
<span class="grey">Hanes, et al. Standards Track [Page 2]</span></pre> |
| 109 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span> |
| 110 |
<span class="grey"><a href="./rfc6913">RFC 6913</a> Fax Media Feature Tag March 2013</span> |
| 111 |
|
| 112 |
|
| 113 |
This document defines the "fax" media feature tag for use in the SIP |
| 114 |
tree, as per <a href="./rfc3840#section-12.1">Section 12.1 of RFC 3840</a> [<a href="./rfc3840" title=""Indicating User Agent Capabilities in the Session Initiation Protocol (SIP)"">RFC3840</a>]. This feature tag |
| 115 |
will be applied per <a href="./rfc3841">RFC 3841</a> [<a href="./rfc3841" title=""Caller Preferences for the Session Initiation Protocol (SIP)"">RFC3841</a>] as a feature preference for |
| 116 |
fax-capable UAs. |
| 117 |
|
| 118 |
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Terminology</span> |
| 119 |
|
| 120 |
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", |
| 121 |
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this |
| 122 |
document are to be interpreted as described in <a href="./rfc2119">RFC 2119</a> [<a href="./rfc2119" title=""Key words for use in RFCs to Indicate Requirement Levels"">RFC2119</a>]. |
| 123 |
|
| 124 |
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Motivation</span> |
| 125 |
|
| 126 |
In the majority of circumstances, it is preferred that capabilities |
| 127 |
be handled in the Session Description Protocol (SDP) portion of the |
| 128 |
SIP [<a href="./rfc3261" title=""SIP: Session Initiation Protocol"">RFC3261</a>] communication. However, fax is somewhat unique in that |
| 129 |
the ultimate intention of the call is not accurately signaled in the |
| 130 |
initial SDP exchange. Specifically, indications of T.38 [<a href="#ref-T38" title=""Procedures for real-time Group 3 facsimile communication over IP Networks"">T38</a>] or any |
| 131 |
other fax transport protocol in the call are not known when the call |
| 132 |
is initiated by an INVITE message. Fax calls are always considered |
| 133 |
voice calls until after they are connected. This results in the |
| 134 |
possibility of fax calls being received by SIP UAs that are not |
| 135 |
capable of handling fax transmissions. |
| 136 |
|
| 137 |
For example, Alice wants to send a fax to Bob. Bob has registered |
| 138 |
two SIP UAs. The first SIP UA is not fax capable, but the second one |
| 139 |
supports the T.38 [<a href="#ref-T38" title=""Procedures for real-time Group 3 facsimile communication over IP Networks"">T38</a>] fax protocol. Currently, SIP servers are |
| 140 |
unable to know at the time that the call starts that Alice prefers a |
| 141 |
fax-capable SIP UA to handle her call. Additionally, the SIP servers |
| 142 |
are also not aware of which of Bob's SIP UAs are fax capable. |
| 143 |
|
| 144 |
To resolve this issue of calls not arriving at a UA that supports |
| 145 |
fax, this document defines a new media feature tag specific to fax, |
| 146 |
per <a href="./rfc3840">RFC 3840</a> [<a href="./rfc3840" title=""Indicating User Agent Capabilities in the Session Initiation Protocol (SIP)"">RFC3840</a>]. Caller preferences, as defined in <a href="./rfc3841">RFC 3841</a> |
| 147 |
[<a href="./rfc3841" title=""Caller Preferences for the Session Initiation Protocol (SIP)"">RFC3841</a>], can then be used for registering UAs that support fax and |
| 148 |
for routing fax calls to these UAs. Thus, Alice can express up front |
| 149 |
that she prefers a T.38 [<a href="#ref-T38" title=""Procedures for real-time Group 3 facsimile communication over IP Networks"">T38</a>] fax-capable SIP UA for this call. At |
| 150 |
the same time, Bob's SIP UAs have expressed their fax capabilities as |
| 151 |
well during registration. Now, when Alice places a fax call to Bob, |
| 152 |
the call is appropriately routed to Bob's fax-capable SIP UA. |
| 153 |
|
| 154 |
|
| 155 |
|
| 156 |
|
| 157 |
|
| 158 |
|
| 159 |
|
| 160 |
|
| 161 |
|
| 162 |
|
| 163 |
|
| 164 |
<span class="grey">Hanes, et al. Standards Track [Page 3]</span></pre> |
| 165 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span> |
| 166 |
<span class="grey"><a href="./rfc6913">RFC 6913</a> Fax Media Feature Tag March 2013</span> |
| 167 |
|
| 168 |
|
| 169 |
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Usage of the "sip.fax" Parameter</span> |
| 170 |
|
| 171 |
The "sip.fax" media feature tag is a new string parameter, defined in |
| 172 |
this document, that allows a call to indicate a fax preference. A |
| 173 |
receiving UA includes the "sip.fax" media feature tag in the Contact |
| 174 |
header field of REGISTER messages to indicate that it is fax capable, |
| 175 |
and a SIP Registrar includes this tag in the Contact header field of |
| 176 |
its 200 OK response to confirm the registration of this preference, |
| 177 |
all as per <a href="./rfc3840">RFC 3840</a> [<a href="./rfc3840" title=""Indicating User Agent Capabilities in the Session Initiation Protocol (SIP)"">RFC3840</a>]. |
| 178 |
|
| 179 |
A calling UA SHOULD include the "sip.fax" media feature tag in the |
| 180 |
Accept-Contact header of an INVITE request in order to express its |
| 181 |
desire for a call to be routed to a fax-capable UA. Otherwise, |
| 182 |
without this tag, fax call determination is not possible until after |
| 183 |
the call is connected. If a calling UA includes the "sip.fax" tag |
| 184 |
and the SIP network elements that process the call (including the |
| 185 |
called UAs) implement the procedures of <a href="./rfc3840">RFC 3840</a> and <a href="./rfc3841">RFC 3841</a>, the |
| 186 |
call will be preferentially routed to UAs that have advertised their |
| 187 |
support for this feature (by including it in the Contact header of |
| 188 |
their REGISTER requests, as documented above). |
| 189 |
|
| 190 |
It is possible for the calling UA to utilize additional procedures |
| 191 |
defined in <a href="./rfc3840">RFC 3840</a> and <a href="./rfc3841">RFC 3841</a> to express a requirement (instead of |
| 192 |
a preference) that its call be delivered to fax-capable UAs. |
| 193 |
However, the calling UA SHOULD NOT require the "sip.fax" media type. |
| 194 |
Doing so could result in call failure for a number of reasons, not |
| 195 |
only because there may not be any receiving UAs registered that have |
| 196 |
advertised their support for this feature, but also because one or |
| 197 |
more SIP network elements that process the call may not support the |
| 198 |
processing defined in <a href="./rfc3840">RFC 3840</a> and <a href="./rfc3841">RFC 3841</a>. A calling UA that |
| 199 |
wishes to express this requirement should be prepared to relax it to |
| 200 |
a preference if it receives a failure response indicating that the |
| 201 |
requirement mechanism itself is not supported by the called UAs, |
| 202 |
their proxies, or other SIP network elements. |
| 203 |
|
| 204 |
When calls do connect through the use of "sip.fax" either as a |
| 205 |
preference or a requirement, UAs should follow standard fax |
| 206 |
negotiation procedures documented in ITU-T T.38 [<a href="#ref-T38" title=""Procedures for real-time Group 3 facsimile communication over IP Networks"">T38</a>] for T.38 fax |
| 207 |
calls and ITU-T G.711 [<a href="#ref-G711" title=""Pulse Code Modulation (PCM) of Voice Frequencies"">G711</a>] and ITU-T V.152 [<a href="#ref-V152" title=""Procedures for supporting voice-band data over IP networks"">V152</a>], Sections <a href="#section-6">6</a> and |
| 208 |
6.1, for fax passthrough calls. Subsequently, the "sip.fax" feature |
| 209 |
tag has two allowed values: "t38" and "passthrough". The "t38" value |
| 210 |
indicates that the impending call will utilize the ITU-T T.38 [<a href="#ref-T38" title=""Procedures for real-time Group 3 facsimile communication over IP Networks"">T38</a>] |
| 211 |
protocol for the fax transmission. The "passthrough" value indicates |
| 212 |
that the ITU-T G.711 [<a href="#ref-G711" title=""Pulse Code Modulation (PCM) of Voice Frequencies"">G711</a>] codec will be used to transport the fax |
| 213 |
call. |
| 214 |
|
| 215 |
|
| 216 |
|
| 217 |
|
| 218 |
|
| 219 |
|
| 220 |
<span class="grey">Hanes, et al. Standards Track [Page 4]</span></pre> |
| 221 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span> |
| 222 |
<span class="grey"><a href="./rfc6913">RFC 6913</a> Fax Media Feature Tag March 2013</span> |
| 223 |
|
| 224 |
|
| 225 |
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Example</span> |
| 226 |
|
| 227 |
Bob registers with the fax media feature tag. The message flow is |
| 228 |
shown in Figure 1: |
| 229 |
|
| 230 |
SIP Registrar Bob's SIP UA |
| 231 |
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |
| 232 |
| | |
| 233 |
| REGISTER F1 | |
| 234 |
|<------------------------------| |
| 235 |
| | |
| 236 |
| 200 OK F2 | |
| 237 |
|------------------------------>| |
| 238 |
| | |
| 239 |
|
| 240 |
Figure 1: Fax Media Feature Tag SIP Registration Example |
| 241 |
|
| 242 |
|
| 243 |
F1 REGISTER Bob -> Registrar |
| 244 |
|
| 245 |
REGISTER sip:example.com SIP/2.0 |
| 246 |
Via: SIP/2.0/TCP bob-TP.example.com:5060;branch=z9hG4bK309475a2 |
| 247 |
From: <sip:[email protected]>;tag=a6c85cf |
| 248 |
To: <sip:[email protected]> |
| 249 |
Call-ID: a84b4c76e66710 |
| 250 |
Max-Forwards: 70 |
| 251 |
CSeq: 116 REGISTER |
| 252 |
Contact: <sip:[email protected];transport=tcp>;+sip.fax="t38" |
| 253 |
Expires: 3600 |
| 254 |
|
| 255 |
The registrar responds with a 200 OK: |
| 256 |
|
| 257 |
F2 200 OK Registrar -> Bob |
| 258 |
|
| 259 |
SIP/2.0 200 OK |
| 260 |
From: <sip:[email protected]>;tag=a6c85cf |
| 261 |
To: <sip:[email protected]>;tag=1263390604 |
| 262 |
Contact: <sip:[email protected];transport=tcp>;+sip.fax="t38" |
| 263 |
Expires: 120 |
| 264 |
Call-ID: a84b4c76e66710 |
| 265 |
Via: SIP/2.0/TCP bob-TP.example.com:5060;branch=z9hG4bK309475a2 |
| 266 |
CSeq: 116 REGISTER |
| 267 |
Expires: 3600 |
| 268 |
|
| 269 |
Callers desiring to express a preference for fax will include the |
| 270 |
"sip.fax" media feature tag in the Accept-Contact header of their |
| 271 |
INVITE. |
| 272 |
|
| 273 |
|
| 274 |
|
| 275 |
|
| 276 |
<span class="grey">Hanes, et al. Standards Track [Page 5]</span></pre> |
| 277 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span> |
| 278 |
<span class="grey"><a href="./rfc6913">RFC 6913</a> Fax Media Feature Tag March 2013</span> |
| 279 |
|
| 280 |
|
| 281 |
INVITE sip:[email protected] SIP/2.0 |
| 282 |
Via: SIP/2.0/TCP client.atlanta.example.com:5060;branch=z9hG4bK74b43 |
| 283 |
Max-Forwards: 70 |
| 284 |
From: Alice <sip:[email protected]>;tag=9fxced76sl |
| 285 |
To: Bob <sip:[email protected]> |
| 286 |
Accept-Contact: *;+sip.fax="t38" |
| 287 |
Call-ID: [email protected] |
| 288 |
CSeq: 1 INVITE |
| 289 |
Contact: <sip:[email protected];transport=tcp> |
| 290 |
Content-Type: application/sdp |
| 291 |
Content-Length: 151 |
| 292 |
|
| 293 |
<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. Security Considerations</span> |
| 294 |
|
| 295 |
The security considerations related to the use of media feature tags |
| 296 |
from <a href="./rfc3840#section-11.1">Section 11.1 of RFC 3840</a> [<a href="./rfc3840" title=""Indicating User Agent Capabilities in the Session Initiation Protocol (SIP)"">RFC3840</a>] apply. |
| 297 |
|
| 298 |
<span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. IANA Considerations</span> |
| 299 |
|
| 300 |
This specification adds a new media feature tag to the SIP Media |
| 301 |
Feature Tag Registration Tree per the procedures defined in <a href="./rfc2506">RFC 2506</a> |
| 302 |
[<a href="./rfc2506" title=""Media Feature Tag Registration Procedure"">RFC2506</a>] and <a href="./rfc3840">RFC 3840</a> [<a href="./rfc3840" title=""Indicating User Agent Capabilities in the Session Initiation Protocol (SIP)"">RFC3840</a>]. |
| 303 |
|
| 304 |
Media feature tag name: sip.fax |
| 305 |
|
| 306 |
ASN.1 Identifier: 1.3.6.1.8.4.25 |
| 307 |
|
| 308 |
Summary of the media feature indicated by this tag: This feature tag |
| 309 |
indicates whether a communications device supports the ITU-T T.38 |
| 310 |
[<a href="#ref-T38" title=""Procedures for real-time Group 3 facsimile communication over IP Networks"">T38</a>] fax protocol ("t38") or the passthrough method of fax |
| 311 |
transmission using the ITU-T G.711 [<a href="#ref-G711" title=""Pulse Code Modulation (PCM) of Voice Frequencies"">G711</a>] audio codec |
| 312 |
("passthrough"). |
| 313 |
|
| 314 |
Values appropriate for use with this feature tag: Token with an |
| 315 |
equality relationship. Values are: |
| 316 |
|
| 317 |
t38: The device supports the "image/t38" media type [<a href="./rfc3326" title=""The Reason Header Field for the Session Initiation Protocol (SIP)"">RFC3326</a>] and |
| 318 |
implements ITU-T T.38 [<a href="#ref-T38" title=""Procedures for real-time Group 3 facsimile communication over IP Networks"">T38</a>] for transporting the ITU-T T.30 |
| 319 |
[<a href="#ref-T30" title=""Procedures for document facsimile transmission in the general switched telephone network"">T30</a>] and ITU-T T.4 [<a href="#ref-T4" title=""Standardization of Group 3 facsimile terminals for document transmission"">T4</a>] fax data over IP. |
| 320 |
|
| 321 |
passthrough: The device supports the "audio/pcmu" and "audio/ |
| 322 |
pcma" media types [<a href="./rfc4856" title=""Media Type Registration of Payload Formats in the RTP Profile for Audio and Video Conferences"">RFC4856</a>] for transporting ITU-T T.30 [<a href="#ref-T30" title=""Procedures for document facsimile transmission in the general switched telephone network"">T30</a>] |
| 323 |
and ITU-T T.4 [<a href="#ref-T4" title=""Standardization of Group 3 facsimile terminals for document transmission"">T4</a>] fax data using the ITU-T G.711 [<a href="#ref-G711" title=""Pulse Code Modulation (PCM) of Voice Frequencies"">G711</a>] audio |
| 324 |
codec. Additional implementation recommendations are in ITU-T |
| 325 |
V.152 [<a href="#ref-V152" title=""Procedures for supporting voice-band data over IP networks"">V152</a>], Sections <a href="#section-6">6</a> and <a href="#section-6.1">6.1</a>. |
| 326 |
|
| 327 |
|
| 328 |
|
| 329 |
|
| 330 |
|
| 331 |
|
| 332 |
<span class="grey">Hanes, et al. Standards Track [Page 6]</span></pre> |
| 333 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span> |
| 334 |
<span class="grey"><a href="./rfc6913">RFC 6913</a> Fax Media Feature Tag March 2013</span> |
| 335 |
|
| 336 |
|
| 337 |
The feature tag is intended primarily for use in the following |
| 338 |
applications, protocols, services, or negotiation mechanisms: |
| 339 |
This feature tag is most useful in a communications application |
| 340 |
for the early identification of a Fax over IP (FoIP) call. |
| 341 |
|
| 342 |
Examples of typical use: Ensuring a fax call is routed to a fax |
| 343 |
capable SIP UA. |
| 344 |
|
| 345 |
Related standards or documents: <a href="./rfc6913">RFC 6913</a> |
| 346 |
|
| 347 |
Security Considerations: The security considerations related to the |
| 348 |
use of media feature tags from <a href="./rfc3840#section-11.1">Section 11.1 of RFC 3840</a> [<a href="./rfc3840" title=""Indicating User Agent Capabilities in the Session Initiation Protocol (SIP)"">RFC3840</a>] |
| 349 |
apply. |
| 350 |
|
| 351 |
<span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>. Acknowledgements</span> |
| 352 |
|
| 353 |
This document is a result of the unique cooperation between the SIP |
| 354 |
Forum and the i3 Forum, who embarked on a groundbreaking |
| 355 |
international test program for FoIP to improve the interoperability |
| 356 |
and reliability of fax communications over IP networks, especially |
| 357 |
tandem networks. The authors would like to acknowledge the effort |
| 358 |
and dedication of all the members of the Fax-over-IP (FoIP) Task |
| 359 |
Group in the SIP Forum and the communications carriers of the I3 |
| 360 |
Forum who contributed to this global effort. |
| 361 |
|
| 362 |
This memo has benefited from the discussion and review of the |
| 363 |
DISPATCH working group, especially the detailed and thoughtful |
| 364 |
comments and corrections of Dan Wing, Paul Kyzivat, Christer |
| 365 |
Holmberg, Charles Eckel, Hadriel Kaplan, Tom Yu, Dale Worley, Adrian |
| 366 |
Farrel, and Pete Resnick. |
| 367 |
|
| 368 |
The authors also thank Gonzalo Camarillo for his review and AD |
| 369 |
sponsorship of this draft and DISPATCH WG chair, Mary Barnes, for her |
| 370 |
review and support. |
| 371 |
|
| 372 |
<span class="h2"><a class="selflink" id="section-9" href="#section-9">9</a>. References</span> |
| 373 |
|
| 374 |
<span class="h3"><a class="selflink" id="section-9.1" href="#section-9.1">9.1</a>. Normative References</span> |
| 375 |
|
| 376 |
[<a id="ref-RFC2119">RFC2119</a>] Bradner, S., "Key words for use in RFCs to Indicate |
| 377 |
Requirement Levels", <a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a>, <a href="./rfc2119">RFC 2119</a>, March 1997. |
| 378 |
|
| 379 |
[<a id="ref-RFC3261">RFC3261</a>] Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston, |
| 380 |
A., Peterson, J., Sparks, R., Handley, M., and E. |
| 381 |
Schooler, "SIP: Session Initiation Protocol", <a href="./rfc3261">RFC 3261</a>, |
| 382 |
June 2002. |
| 383 |
|
| 384 |
|
| 385 |
|
| 386 |
|
| 387 |
|
| 388 |
<span class="grey">Hanes, et al. Standards Track [Page 7]</span></pre> |
| 389 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span> |
| 390 |
<span class="grey"><a href="./rfc6913">RFC 6913</a> Fax Media Feature Tag March 2013</span> |
| 391 |
|
| 392 |
|
| 393 |
[<a id="ref-RFC3840">RFC3840</a>] Rosenberg, J., Schulzrinne, H., and P. Kyzivat, |
| 394 |
"Indicating User Agent Capabilities in the Session |
| 395 |
Initiation Protocol (SIP)", <a href="./rfc3840">RFC 3840</a>, August 2004. |
| 396 |
|
| 397 |
[<a id="ref-RFC3841">RFC3841</a>] Rosenberg, J., Schulzrinne, H., and P. Kyzivat, "Caller |
| 398 |
Preferences for the Session Initiation Protocol (SIP)", |
| 399 |
<a href="./rfc3841">RFC 3841</a>, August 2004. |
| 400 |
|
| 401 |
[<a id="ref-T38">T38</a>] International Telecommunication Union, "Procedures for |
| 402 |
real-time Group 3 facsimile communication over IP |
| 403 |
Networks", ITU-T Recommendation T.38, October 2010. |
| 404 |
|
| 405 |
<span class="h3"><a class="selflink" id="section-9.2" href="#section-9.2">9.2</a>. Informative References</span> |
| 406 |
|
| 407 |
[<a id="ref-G711">G711</a>] International Telephone and Telegraph Consultative |
| 408 |
Committee, "Pulse Code Modulation (PCM) of Voice |
| 409 |
Frequencies", CCITT Recommendation G.711, 1972. |
| 410 |
|
| 411 |
[<a id="ref-RFC2506">RFC2506</a>] Holtman, K., Mutz, A., and T. Hardie, "Media Feature Tag |
| 412 |
Registration Procedure", <a href="https://www.rfc-editor.org/bcp/bcp31">BCP 31</a>, <a href="./rfc2506">RFC 2506</a>, March 1999. |
| 413 |
|
| 414 |
[<a id="ref-RFC3326">RFC3326</a>] Schulzrinne, H., Oran, D., and G. Camarillo, "The Reason |
| 415 |
Header Field for the Session Initiation Protocol (SIP)", |
| 416 |
<a href="./rfc3326">RFC 3326</a>, December 2002. |
| 417 |
|
| 418 |
[<a id="ref-RFC4856">RFC4856</a>] Casner, S., "Media Type Registration of Payload Formats in |
| 419 |
the RTP Profile for Audio and Video Conferences", |
| 420 |
<a href="./rfc4856">RFC 4856</a>, February 2007. |
| 421 |
|
| 422 |
[<a id="ref-T30">T30</a>] International Telecommunication Union, "Procedures for |
| 423 |
document facsimile transmission in the general switched |
| 424 |
telephone network", ITU-T Recommendation T.30, September |
| 425 |
2005. |
| 426 |
|
| 427 |
[<a id="ref-T4">T4</a>] International Telecommunication Union, "Standardization of |
| 428 |
Group 3 facsimile terminals for document transmission", |
| 429 |
ITU-T Recommendation T.4, July 2003. |
| 430 |
|
| 431 |
[<a id="ref-V152">V152</a>] International Telecommunication Union, "Procedures for |
| 432 |
supporting voice-band data over IP networks", ITU-T |
| 433 |
Recommendation V.152, September 2010. |
| 434 |
|
| 435 |
|
| 436 |
|
| 437 |
|
| 438 |
|
| 439 |
|
| 440 |
|
| 441 |
|
| 442 |
|
| 443 |
|
| 444 |
<span class="grey">Hanes, et al. Standards Track [Page 8]</span></pre> |
| 445 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span> |
| 446 |
<span class="grey"><a href="./rfc6913">RFC 6913</a> Fax Media Feature Tag March 2013</span> |
| 447 |
|
| 448 |
|
| 449 |
Authors' Addresses |
| 450 |
|
| 451 |
David Hanes |
| 452 |
Cisco Systems |
| 453 |
7200-10 Kit Creek Road |
| 454 |
Research Triangle Park, NC 27709 |
| 455 |
US |
| 456 |
|
| 457 |
EMail: [email protected] |
| 458 |
|
| 459 |
|
| 460 |
Gonzalo Salgueiro |
| 461 |
Cisco Systems |
| 462 |
7200-12 Kit Creek Road |
| 463 |
Research Triangle Park, NC 27709 |
| 464 |
US |
| 465 |
|
| 466 |
EMail: [email protected] |
| 467 |
|
| 468 |
|
| 469 |
Kevin P. Fleming |
| 470 |
Digium, Inc. |
| 471 |
445 Jan Davis Drive NW |
| 472 |
Huntsville, AL 35806 |
| 473 |
US |
| 474 |
|
| 475 |
EMail: [email protected] |
| 476 |
|
| 477 |
|
| 478 |
|
| 479 |
|
| 480 |
|
| 481 |
|
| 482 |
|
| 483 |
|
| 484 |
|
| 485 |
|
| 486 |
|
| 487 |
|
| 488 |
|
| 489 |
|
| 490 |
|
| 491 |
|
| 492 |
|
| 493 |
|
| 494 |
|
| 495 |
|
| 496 |
|
| 497 |
|
| 498 |
|
| 499 |
|
| 500 |
Hanes, et al. Standards Track [Page 9] |
| 501 |
</pre> |