conformance.docs 30.9 KB
Newer Older
Pekka Pessi's avatar
Pekka Pessi committed
1 2 3
/*  -*- html -*- */
/**

Pekka Pessi's avatar
Pekka Pessi committed
4
@page sofia_sip_conformance SIP and SDP Protocol Features in Sofia-SIP
Pekka Pessi's avatar
Pekka Pessi committed
5

6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45
This document describes how Sofia-SIP stack supports specifications listed
below.

<table border=0>
<tr valign="top">
<td>
<a href="#3261">RFC 3261</a> <br>
<a href="#2617">RFC 2617</a> <br>
<a href="#3262">RFC 3262</a> <br>
<a href="#3263">RFC 3263</a> <br>
<a href="#3265">RFC 3265</a> <br>
<a href="#2806">RFC 2806</a> <br>
<a href="#2976">RFC 2976</a> <br>
<a href="#3311">RFC 3311</a> <br>
<a href="#3313">RFC 3313</a> <br>
<a href="#3323">RFC 3323</a> <br>
<a href="#3326">RFC 3326</a> <br>
</td><td>
<a href="#3325">RFC 3325</a> <br>
<a href="#3327">RFC 3327</a> <br>
<a href="#3329">RFC 3329</a> <br>
<a href="#3361">RFC 3361</a> <br>
<a href="#3420">RFC 3420</a> <br>
<a href="#3428">RFC 3428</a> <br>
<a href="#3486">RFC 3486</a> <br>
<a href="#3515">RFC 3515</a> <br>
<a href="#3608">RFC 3608</a> <br>
<a href="#3680">RFC 3680</a> <br>
<a href="#3824">RFC 3824</a> <br>
</td><td>
<a href="#3840">RFC 3840</a> <br>
<a href="#3841">RFC 3841</a> <br>
<a href="#3842">RFC 3842</a> <br>
<a href="#3856">RFC 3856</a> <br>
<a href="#3857">RFC 3857</a> <br>
<a href="#3858">RFC 3858</a> <br>
<a href="#3891">RFC 3891</a> <br>
<a href="#3892">RFC 3892</a> <br>
<a href="#3903">RFC 3903</a> <br>
<a href="#4028">RFC 4028</a> <br>
46
<a href="#4320">RFC 4320</a> <br>
47
<a href="#4566">RFC 4566</a> <br>
48 49 50 51 52 53 54 55 56 57 58 59 60 61
</td><td>
<a href="#2327">RFC 2327</a> <br>
<a href="#3264">RFC 3264</a> <br>
<a href="#3266">RFC 3266</a> <br>
<a href="#3312">RFC 3312</a> <br>
<a href="#3388">RFC 3388</a> <br>
<a href="#3407">RFC 3407</a> <br>
<a href="#3524">RFC 3524</a> <br>
<a href="#3556">RFC 3556</a> <br>
<a href="#3605">RFC 3605</a> <br>
<a href="#3890">RFC 3890</a> <br>
</td></tr>
</table>

Pekka Pessi's avatar
Pekka Pessi committed
62 63 64 65
<table border=1 cellpadding=4 cellspacing=0>
<tr>
   <th>Feature</th>
   <th>Supported</td>
Pekka Pessi's avatar
Pekka Pessi committed
66
   <th>Notes</td>
Pekka Pessi's avatar
Pekka Pessi committed
67 68
</tr>

69
<a name="3261"></a>
Pekka Pessi's avatar
Pekka Pessi committed
70 71 72 73 74 75
<tr valign=top>
    <th align="left">
	@RFC3261: Basic SIP Protocol
    </th>
    <td>
	The SIP registration and dialog level implementation enables the
Pekka Pessi's avatar
Pekka Pessi committed
76
	application to operate as a SIP UA, SIP proxy or a redirect server
Pekka Pessi's avatar
Pekka Pessi committed
77 78
	according to the @RFC3261.

79 80 81 82
	The @RFC3261 functionality is divided into five layers:
	-# <a href="sip/index.html">message syntax and encoding</a>
	-# <a href="tport/index.html">transport</a>
	-# <a href="nta/index.html">transaction</a>
Pekka Pessi's avatar
Pekka Pessi committed
83
	-# transaction user (UAS and UAC cores, proxy core)
84 85
	-# SIP elements: <a href="nua/index.html">user agent</a>
           client and server, proxies,
Pekka Pessi's avatar
Pekka Pessi committed
86 87 88
	   registrars
    </td>
    <td>
Pekka Pessi's avatar
Pekka Pessi committed
89
        &nbsp;
Pekka Pessi's avatar
Pekka Pessi committed
90 91 92
    </td>
</tr>

93
<a name="3261.19"></a> <a name="3261.20"></a>
Pekka Pessi's avatar
Pekka Pessi committed
94 95
<tr valign=top>
    <th align="left">
Pekka Pessi's avatar
Pekka Pessi committed
96
	@RFC3261 Sections&nbsp;19&nbsp;and&nbsp;20:<br>
Pekka Pessi's avatar
Pekka Pessi committed
97 98 99 100
	Syntax and encoding
    </td>
    <td>
	The supported @RFC3261 methods are: @b REGISTER, @b OPTIONS, @b
101 102 103 104 105 106 107 108 109 110 111 112 113 114
	INVITE, @b ACK, @b CANCEL, @b BYE, as well as methods
	<a href="#2976"><b>INFO</b></a>,
	<a href="#3262"><b>PRACK</b></a>,
        <a href="#3265"><b>SUBSCRIBE</b></a>,
        <a href="#3265"><b>NOTIFY</b></a>,
        <a href="#3311"><b>UPDATE</b></a>,
        <a href="#3428"><b>MESSAGE</b></a>,
        <a href="#3515"><b>REFER</b></a>,
	and
	<a href="#3903"><b>PUBLISH</b></a>.

	Sofia-SIP supports the following SIP headers as specified in
        @RFC3261 or its extensions (generating, parsing and syntax
        checking):
Pekka Pessi's avatar
Pekka Pessi committed
115 116 117 118

	@ref sip_accept "Accept",
	@ref sip_accept_encoding "Accept-Encoding",
	@ref sip_accept_language "Accept-Language",
119
	@ref sip_alert_info "Alert-Info" (@VERSION_1_12_7),
Pekka Pessi's avatar
Pekka Pessi committed
120 121
	@ref sip_allow "Allow",
	@ref sip_authentication_info "Authentication-Info",
122
	@ref sip_authorization "Authorization",
123
	@ref sip_call_id "Call-ID" ("i"),
Pekka Pessi's avatar
Pekka Pessi committed
124
	@ref sip_call_info "Call-Info",
125
	@ref sip_contact "Contact" ("m"),
Pekka Pessi's avatar
Pekka Pessi committed
126
	@ref sip_content_disposition "Content-Disposition",
127
        @ref sip_content_encoding "Content-Encoding" ("e"),
Pekka Pessi's avatar
Pekka Pessi committed
128
	@ref sip_content_language "Content-Language",
129 130
	@ref sip_content_length "Content-Length" ("l"),
	@ref sip_content_type "Content-Type" ("c"),
Pekka Pessi's avatar
Pekka Pessi committed
131 132 133 134
	@ref sip_cseq "CSeq",
	@ref sip_date "Date",
	@ref sip_error_info "Error-Info",
	@ref sip_expires "Expires",
135
	@ref sip_from "From" ("f"),
Pekka Pessi's avatar
Pekka Pessi committed
136 137 138 139 140 141
	@ref sip_in_reply_to "In-Reply-To",
	@ref sip_max_forwards "Max-Forwards",
	@ref sip_min_expires "Min-Expires",
	@ref sip_mime_version "MIME-Version",
	@ref sip_organization "Organization",
	@ref sip_priority "Priority",
142 143
	@ref sip_proxy_authenticate "Proxy-Authenticate",
	@ref sip_proxy_authorization "Proxy-Authorization",
Pekka Pessi's avatar
Pekka Pessi committed
144 145
	@ref sip_proxy_require "Proxy-Require",
	@ref sip_record_route "Record-Route",
146
	@ref sip_reply_to "Reply-To" (@VERSION_1_12_7),
Pekka Pessi's avatar
Pekka Pessi committed
147 148 149 150
	@ref sip_require "Require",
	@ref sip_retry_after "Retry-After",
	@ref sip_route "Route",
	@ref sip_server "Server",
151 152
	@ref sip_subject "Subject" ("s"),
	@ref sip_supported "Supported" ("k"),
Pekka Pessi's avatar
Pekka Pessi committed
153
	@ref sip_timestamp "Timestamp",
154
	@ref sip_to "To" ("t"),
Pekka Pessi's avatar
Pekka Pessi committed
155 156
	@ref sip_unsupported "Unsupported",
	@ref sip_user_agent "User-Agent",
157
	@ref sip_via "Via" ("v"),
Pekka Pessi's avatar
Pekka Pessi committed
158 159 160
	@ref sip_warning "Warning", and
	@ref sip_www_authenticate "WWW-Authenticate".

Pekka Pessi's avatar
Pekka Pessi committed
161 162
	Unknown headers (extension headers) are supported and can be passed
	to/received from application as name-value pairs.
Pekka Pessi's avatar
Pekka Pessi committed
163

Pekka Pessi's avatar
Pekka Pessi committed
164 165
	It is possible to extend SIP parser in run-time with header-specific
        parsers.
Pekka Pessi's avatar
Pekka Pessi committed
166 167
    </td>
    <td>
168 169 170
	- Automatic escaping of reserved characters has not been
	  implemented.
	- Using NUL (zero byte) in doublequoted strings has not been implemented
Pekka Pessi's avatar
Pekka Pessi committed
171 172 173
   </td>
</tr>

174
<a name="3261.18"></a>
Pekka Pessi's avatar
Pekka Pessi committed
175 176
<tr valign=top>
    <th align="left">
Pekka Pessi's avatar
Pekka Pessi committed
177 178
	@RFC3261 Section 18:<br>
	UDP and TCP transports
Pekka Pessi's avatar
Pekka Pessi committed
179 180
    </th>
    <td>
181 182 183 184 185 186
        UDP and TCP on both IP4 and IP6 are supported.

        The UDP size limit of 1300 bytes is enforced by default. If limit is
        exceeded, TCP is tried instead. If TCP connection is refused, UDP is
        tried if message size is less than 64 kilobytes. Limit is adjustable
        via parameter NTATAG_UDP_MTU().
Pekka Pessi's avatar
Pekka Pessi committed
187 188

	TCP connections are reused by client. However, server closes
189 190 191
	connections after idle time of 30 minutes (by default). The idle
	time limit is adjustable with TPTAG_IDLE() (given as argument to
	nta_agent_add_tport() or nta_agent_create()).
Pekka Pessi's avatar
Pekka Pessi committed
192

193 194
	Server tries to use same TCP connection to return response as the
	request was received.
Pekka Pessi's avatar
Pekka Pessi committed
195 196 197 198

	Only one SIP message is accepted per UDP message, as per @RFC3261.
    </td>
    <td>
199
	There is experimental support for SCTP, too.
Pekka Pessi's avatar
Pekka Pessi committed
200 201 202
    </td>
</tr>

203
<a name="3261.17"></a>
Pekka Pessi's avatar
Pekka Pessi committed
204 205
<tr valign=top>
    <th align="left">
Pekka Pessi's avatar
Pekka Pessi committed
206
	@RFC3261 Section 17:<br> Transactions
Pekka Pessi's avatar
Pekka Pessi committed
207 208 209
    </th>
    <td>
        Transaction state engines function as specified in @RFC3261 section
210
	17. There is special handling of methods @b INVITE, @b ACK, and @b
Pekka Pessi's avatar
Pekka Pessi committed
211 212 213 214
	CANCEL. There are two modes for transaction state engines,
	User-Agent and Proxy modes.

	Default values for SIP timers are those specified by @RFC3261. The
215
	defaults for T1, T1x64, T2 and T4 can be changed via
216
        configuration tags defined in <sofia-sip/nta_tag.h>.
Pekka Pessi's avatar
Pekka Pessi committed
217 218
    </td>
    <td>
219
	&nbsp;
Pekka Pessi's avatar
Pekka Pessi committed
220 221 222 223
    </td>
</tr>


224
<a name="3261.26"></a>
Pekka Pessi's avatar
Pekka Pessi committed
225 226
<tr valign=top>
    <th align="left">
227
	@RFC3261 Section 26:<br> Security
Pekka Pessi's avatar
Pekka Pessi committed
228 229 230 231 232 233 234
    </th>
    <td>
        TLS and SIPS URIs has been implemented. Currently, TLS does not
	require certificate from client nor it does check it if one is
	provided.
    </td>
    <td>
Pekka Pessi's avatar
Pekka Pessi committed
235
	Missing:
236
	- Authorizing connections with TLS certificates
Pekka Pessi's avatar
Pekka Pessi committed
237 238 239 240
	- S/MIME
    </td>
</tr>

241
<a name="2617"></a>
Pekka Pessi's avatar
Pekka Pessi committed
242 243
<tr valign=top>
    <th align="left">
Pekka Pessi's avatar
Pekka Pessi committed
244
	@RFC2617: HTTP Digest Authentication
Pekka Pessi's avatar
Pekka Pessi committed
245 246
    </th>
    <td>
247 248
	Sofia-SIP includes authentication client and server modules
	implementing HTTP Digest authentication.
Pekka Pessi's avatar
Pekka Pessi committed
249 250

	HTTP Digest is a simple challenge-response authentication
Pekka Pessi's avatar
Pekka Pessi committed
251
	scheme defined in @RFC2617 based on the UA sending a checksum
Pekka Pessi's avatar
Pekka Pessi committed
252 253
	calculated over specific values in response to a challenge sent by
	the server (proxy or UA).
Pekka Pessi's avatar
Pekka Pessi committed
254

255 256 257 258 259
        Checksum calculation supports MD5 (@RFC1321). The algorithm for
        calculating MD5 digest hash can be MD5, MD5sess or be
        @RFC2069-compatible algorithm. The quality-of-protection (qop)
        parameters "auth", "auth-int" and none (missing) are supported. The
        "opaque" parameter is supported.
Pekka Pessi's avatar
Pekka Pessi committed
260 261

	The SIP authentication headers supported (generating, parsing and
262 263
	syntax checking) are:
	@ref sip_authorization "Authorization",
Pekka Pessi's avatar
Pekka Pessi committed
264
	@ref sip_authentication_info "Authentication-Info",
265
	@ref sip_proxy_authenticate "Proxy-Authenticate",
Pekka Pessi's avatar
Pekka Pessi committed
266 267 268
	@ref sip_proxy_authentication_info "Proxy-Authentication-Info",
	@ref sip_proxy_authorization "Proxy-Authorization", and
	@ref sip_www_authenticate "WWW-Authenticate".
Pekka Pessi's avatar
Pekka Pessi committed
269 270 271 272

	SIP interface to the modules is implemented as defined in @RFC3261
	(sections 8.1.3.5, 22.2, 22.3, 22.4).

273 274 275 276
	An @RFC2617 header
	@ref sip_proxy_authentication_info "Proxy-Authentication-Info"
        is not listed in @RFC3261 but it is nevertheless supported by
        Sofia-SIP.
Pekka Pessi's avatar
Pekka Pessi committed
277 278
    </td>
    <td>
Pekka Pessi's avatar
Pekka Pessi committed
279
	Missing:
280
        - Using nextnonce
Pekka Pessi's avatar
Pekka Pessi committed
281 282 283 284
	- Mutual authentication
    </td>
</tr>

285
<a name="3262"></a>
Pekka Pessi's avatar
Pekka Pessi committed
286 287
<tr valign=top>
    <th align="left">
288
	@RFC3262: PRACK and 100rel
Pekka Pessi's avatar
Pekka Pessi committed
289 290
    </th>
    <td>
291 292 293 294 295 296 297 298 299 300
	PRACK method is supported within dialog as defined in RFC3262.
        Semantics of reliable provisional responses are supported:
        - including 100rel Required header in provisional responses if
          request had 100rel
	- generation of PRACK based on 100rel option tag in Require header of
	  a provisional response, and
        - automatic re-transmission of provisional responses.

	The SIP headers supported (generating, parsing and syntax checking)
	are @ref sip_rseq "RSeq" and @ref sip_rack "RAck".
Pekka Pessi's avatar
Pekka Pessi committed
301 302
    </td>
    <td>
303
	&nbsp;
Pekka Pessi's avatar
Pekka Pessi committed
304 305 306
    </td>
</tr>

307
<a name="3263"></a>
Pekka Pessi's avatar
Pekka Pessi committed
308 309
<tr valign=top>
    <th align="left">
310
	@RFC3263: Locating SIP Servers
Pekka Pessi's avatar
Pekka Pessi committed
311 312
    </th>
    <td>
313 314
	Support for SIP server address resolution from SIP or SIPS URI using
	NAPTR, SRV, A or AAAA records in DNS as defined in @RFC3263.
Pekka Pessi's avatar
Pekka Pessi committed
315 316
    </td>
    <td>
317 318
	- Resolving any other types of URIs than SIP or SIPS URIs, e.g., IM:
	or PRES: URIs.
Pekka Pessi's avatar
Pekka Pessi committed
319 320 321
    </td>
</tr>

322
<a name="3265"></a>
Pekka Pessi's avatar
Pekka Pessi committed
323 324
<tr valign=top>
    <th align="left">
325
	@RFC3265: SIP Event Notifications
Pekka Pessi's avatar
Pekka Pessi committed
326 327
    </th>
    <td>
328 329
	SIP extensions for subscribing and processing asynchronous event
	notifications as defined in @RFC3265.
Pekka Pessi's avatar
Pekka Pessi committed
330

331 332 333 334 335
	Includes dialog level support for sending and refreshing SUBSCRIBE
	and receiving NOTIFY messages.

	The SIP headers explicitly supported (generating, parsing and
	syntax checking) are
336
        @ref sip_event "Event" ("o"),
337 338 339 340
	@ref sip_allow_events "Allow-Events", and
        @ref sip_subscription_state "Subscription-State"

	Note: currently there is no support for forked SUBSCRIBE requests.
Pekka Pessi's avatar
Pekka Pessi committed
341 342
    </td>
    <td>
343 344 345
	Application must take care of:
	- Subscribing, generating or processing specific event types
          and interpreting the content of event data is up to application
Pekka Pessi's avatar
Pekka Pessi committed
346 347 348
    </td>
</tr>

349
<a name="2806"></a>
Pekka Pessi's avatar
Pekka Pessi committed
350 351
<tr valign=top>
    <th align="left">
352
	@RFC2806: tel URI
Pekka Pessi's avatar
Pekka Pessi committed
353 354
    </th>
    <td>
355 356
	Sofia-SIP supports handling of any URI type. Sofia-SIP parses tel:
        URIs.
Pekka Pessi's avatar
Pekka Pessi committed
357 358
    </td>
    <td>
Pekka Pessi's avatar
Pekka Pessi committed
359
	Missing:
360
	- Resolving the tel: URIs
Pekka Pessi's avatar
Pekka Pessi committed
361 362 363
    </td>
</tr>

364
<a name="2976"></a>
Pekka Pessi's avatar
Pekka Pessi committed
365 366
<tr valign=top>
    <th align="left">
367
	@RFC2976: INFO
Pekka Pessi's avatar
Pekka Pessi committed
368 369
    </th>
    <td>
370
	INFO method is supported within a dialog natively.
Pekka Pessi's avatar
Pekka Pessi committed
371 372
    </td>
    <td>
373 374
	Not implemented:
	- Generating or processing contents of INFO requests
Pekka Pessi's avatar
Pekka Pessi committed
375 376 377
    </td>
</tr>

378

379
<a name="3311"></a>
Pekka Pessi's avatar
Pekka Pessi committed
380 381
<tr valign=top>
    <th align="left">
382
	@RFC3311: UPDATE
Pekka Pessi's avatar
Pekka Pessi committed
383 384
    </th>
    <td>
385 386 387
	UPDATE method as defined in RFC3311. UPDATE allows a client to
	update parameters of a session (such as the set of media streams and
	their codecs) even within early dialogs.
Pekka Pessi's avatar
Pekka Pessi committed
388

389
	Offer-Answer negotiation with UPDATE is implemented in nua.
Pekka Pessi's avatar
Pekka Pessi committed
390 391
    </td>
    <td>
392 393
	Application must take care of:
        - Initiating UPDATE requests
Pekka Pessi's avatar
Pekka Pessi committed
394 395 396
    </td>
</tr>

397

398
<a name="3313"></a>
Pekka Pessi's avatar
Pekka Pessi committed
399 400
<tr valign=top>
    <th align="left">
401
	@RFC3313: Media Authentication
Pekka Pessi's avatar
Pekka Pessi committed
402 403
    </th>
    <td>
404 405 406
	Sofia-SIP provides <a href="#3261.19">generic support</a> for
	extension headers and parameters. P-Media-Authorization header is
	supported as an @ref sip_unknown "extension header".
Pekka Pessi's avatar
Pekka Pessi committed
407 408
    </td>
    <td>
409 410
        Application must take care of:
	- Passing the authorization token to QoS reservation request
Pekka Pessi's avatar
Pekka Pessi committed
411 412 413
    </td>
</tr>

Pekka Pessi's avatar
Pekka Pessi committed
414

415
<a name="3323"></a>
Pekka Pessi's avatar
Pekka Pessi committed
416 417
<tr valign=top>
    <th align="left">
418
	@RFC3323: Privacy
Pekka Pessi's avatar
Pekka Pessi committed
419 420
    </th>
    <td>
421 422
	@ref sip_privacy "Privacy" header is supported (generating, parsing
        and syntax checking).
Pekka Pessi's avatar
Pekka Pessi committed
423

424 425 426 427
	Call-Id header is generated from cryptographically random id without
	host name or IP address. By default, @ref sip_contact "Contact" and
	@ref sip_via "Via" headers contain only IP address that can be
	dynamically allocated.
Pekka Pessi's avatar
Pekka Pessi committed
428

429 430
	Application can enter any SIP URI and display name to From header,
	e.g., @code Anonymous <sip:anonymous@example.org> @endcode.
Pekka Pessi's avatar
Pekka Pessi committed
431 432
    </td>
    <td>
433 434 435 436 437 438
        Application must take care of:
	- Properly populating the URIs and display names within SIP headers
	- Not including any optional headers that could reveal identity
	- Generating of Privacy header with appropriate values
	- Generating of Proxy-Require: privacy
	- Using anonymous callback URIs etc.
Pekka Pessi's avatar
Pekka Pessi committed
439 440 441
    </td>
</tr>

Pekka Pessi's avatar
Pekka Pessi committed
442

443
<a name="3326"></a>
Pekka Pessi's avatar
Pekka Pessi committed
444 445
<tr valign=top>
    <th align="left">
446
	@RFC3326: Reason
Pekka Pessi's avatar
Pekka Pessi committed
447 448
    </th>
    <td>
449 450
	Sofia-SIP supports @ref sip_reason "Reason" header (generating,
	parsing and syntax checking).
Pekka Pessi's avatar
Pekka Pessi committed
451 452
    </td>
    <td>
453 454
        Application must take care of:
	- Generating or processing Reason headers
Pekka Pessi's avatar
Pekka Pessi committed
455 456 457
    </td>
</tr>

458

459
<a name="3325"></a>
Pekka Pessi's avatar
Pekka Pessi committed
460
<tr valign=top>
Pekka Pessi's avatar
Pekka Pessi committed
461
    <th align="left">
462
	@RFC3325: Asserted Identity
Pekka Pessi's avatar
Pekka Pessi committed
463
    </th>
Pekka Pessi's avatar
Pekka Pessi committed
464
    <td>
465 466 467 468
	Sofia-SIP provides <a href="#3261.19">generic support</a> for
	extension headers and parameters. P-Asserted-Identity and
	P-Preferred-Identity are supported as supported as @ref
	sip_unknown "extension headers".
Pekka Pessi's avatar
Pekka Pessi committed
469 470
    </td>
    <td>
471 472 473 474
	Not implemented:
        - <a href="#3323">id privacy</a>
	- Recognizing trust domains and enforcing handling of headers
	  based on those
Pekka Pessi's avatar
Pekka Pessi committed
475 476 477
    </td>
</tr>

478
<a name="3327"></a>
Pekka Pessi's avatar
Pekka Pessi committed
479 480
<tr valign=top>
    <th align="left">
481
	@RFC3327: Path
Pekka Pessi's avatar
Pekka Pessi committed
482 483
    </th>
    <td>
484 485 486 487 488
	User-agent engine can add "path" option tag to Supported header of
	REGISTER requests.

	Sofia-SIP explicitly supports @ref sip_path "Path" header
	(generating, parsing and syntax checking).
Pekka Pessi's avatar
Pekka Pessi committed
489 490
    </td>
    <td>
491
	&nbsp;
Pekka Pessi's avatar
Pekka Pessi committed
492 493 494
    </td>
</tr>

495
<a name="3329"></a>
Pekka Pessi's avatar
Pekka Pessi committed
496
<tr valign=top>
497 498 499
    <th align="left">
	@RFC3329:
	Security Agreement
Pekka Pessi's avatar
Pekka Pessi committed
500 501
    </th>
    <td>
502 503 504
	Some support of the SIP Security Mechanism Agreement procedures. The
	client is able to insert Security-Client and Security-Verify header
	with fake @e d-ver value.
Pekka Pessi's avatar
Pekka Pessi committed
505

506 507 508 509 510
	Sofia-SIP explicitly supports (generating, parsing
	and syntax checking)
	@ref sip_security_client "Security-Client",
	@ref sip_security_server "Security-Server", and
	@ref sip_security_verify "Security-Verify" headers.
Pekka Pessi's avatar
Pekka Pessi committed
511

512
	Security-mechanism supported is "digest".
Pekka Pessi's avatar
Pekka Pessi committed
513 514
    </td>
    <td>
515
	Correct @e d-ver value is not calculated.
Pekka Pessi's avatar
Pekka Pessi committed
516 517 518
    </td>
</tr>

519
<a name="3361"></a>
Pekka Pessi's avatar
Pekka Pessi committed
520 521
<tr valign=top>
    <th align="left">
522
	@RFC3361: DHCPv4 option for locating SIP servers.
Pekka Pessi's avatar
Pekka Pessi committed
523 524
    </th>
    <td>
525
	Sofia-SIP supports outbound proxy.
Pekka Pessi's avatar
Pekka Pessi committed
526 527
    </td>
    <td>
528 529 530
	Application must take care of:
	- passing outbound proxy name or address from DHCP client
          to Sofia-SIP stack.
Pekka Pessi's avatar
Pekka Pessi committed
531 532 533
    </td>
</tr>

534
<a name="3420"></a>
Pekka Pessi's avatar
Pekka Pessi committed
535 536
<tr valign=top>
    <th align="left">
537
	@RFC3420: message/sipfrag
Pekka Pessi's avatar
Pekka Pessi committed
538 539
    </th>
    <td>
540 541
	Sofia-SIP passes the received SIP message headers to application
	which can create a message/sipfrag payload.
Pekka Pessi's avatar
Pekka Pessi committed
542 543
    </td>
    <td>
544 545
        Application must take care of:
	- processing the SIP message fragments
Pekka Pessi's avatar
Pekka Pessi committed
546 547 548
    </td>
</tr>

549
<a name="3428"></a>
Pekka Pessi's avatar
Pekka Pessi committed
550 551
<tr valign=top>
    <th align="left">
552
	@RFC3428: MESSAGE
Pekka Pessi's avatar
Pekka Pessi committed
553 554
    </th>
    <td>
555
	MESSAGE method is supported natively.
Pekka Pessi's avatar
Pekka Pessi committed
556 557
    </td>
    <td>
Pekka Pessi's avatar
Pekka Pessi committed
558
	&nbsp;
Pekka Pessi's avatar
Pekka Pessi committed
559 560 561
    </td>
</tr>

562
<a name="3486"></a>
Pekka Pessi's avatar
Pekka Pessi committed
563 564
<tr valign=top>
    <th align="left">
565
	@RFC3486: Compressing SIP
Pekka Pessi's avatar
Pekka Pessi committed
566 567
    </th>
    <td>
568 569 570
	Sofia-SIP provides support for using comp=sigcomp parameters in @ref
	sip_via "Via" header and @ref url_t "SIP URIs", indicating
	support for compression.
Pekka Pessi's avatar
Pekka Pessi committed
571 572
    </td>
    <td>
573
	SigComp itself is not supported.
Pekka Pessi's avatar
Pekka Pessi committed
574 575 576
    </td>
</tr>

577
<a name="3515"></a>
Pekka Pessi's avatar
Pekka Pessi committed
578 579
<tr valign=top>
    <th align="left">
580
	@RFC3515: REFER
Pekka Pessi's avatar
Pekka Pessi committed
581 582
    </th>
    <td>
583 584 585 586 587 588 589 590
	REFER method is supported natively. Sofia-SIP processes incoming
        REFER requests and generates NOTIFY with correct
	@ref sip_event "Event" header automatically.

	Further notifications can be automatically generated actions when
	nua_invite() is given referrer's nua handle in NUTAG_NOTIFY_REFER().

	Sofia-SIP explicitly supports (generating, parsing and syntax
591
	checking) @ref sip_refer_to "Refer-To" ("r") SIP header.
592 593 594 595

	See also support for
	<a href="#3891">RFC 3891</a> and
        <a href="#3892">RFC 3892</a>.
Pekka Pessi's avatar
Pekka Pessi committed
596 597
    </td>
    <td>
598
        &nbsp;
Pekka Pessi's avatar
Pekka Pessi committed
599 600 601
    </td>
</tr>

602
<a name="3608"></a>
Pekka Pessi's avatar
Pekka Pessi committed
603 604
<tr valign=top>
    <th align="left">
605
	@RFC3608: Service-Route
Pekka Pessi's avatar
Pekka Pessi committed
606 607
    </th>
    <td>
608 609 610 611 612 613 614
	Sofia-SIP supports @ref sip_service_route "Service-Route" that can
	be used to provide a mechanism by which a registrar may inform a
	registering UA of a service route. User-Agent will optionally use
	the route provided in @ref sip_service_route "Service-Route" header.

	The SIP header explicitly supported (generating, parsing and
	syntax checking) is @ref sip_service_route "Service-Route".
Pekka Pessi's avatar
Pekka Pessi committed
615 616
    </td>
    <td>
617
	&nbsp;
Pekka Pessi's avatar
Pekka Pessi committed
618 619 620
    </td>
</tr>

621
<a name="3680"></a>
Pekka Pessi's avatar
Pekka Pessi committed
622 623
<tr valign=top>
    <th align="left">
624
	@RFC3680: "reg" event
Pekka Pessi's avatar
Pekka Pessi committed
625 626
    </th>
    <td>
627 628 629 630 631 632 633 634 635
	Sofia-SIP supports <a href="#3265">generic SIP event support</a> for
	subscribing SIP event packages and receiving notifications for them.
	Subscriptions are refreshed before expiration when needed and
	subscriptions are terminated on request. Sofia-SIP takes care of
        notified subscription states.

	UA can SUBSCRIBE to a registration state event package after sending
	initial REGISTER to, e.g., 3GPP network and use it to follow its
        registration status.
Pekka Pessi's avatar
Pekka Pessi committed
636 637
    </td>
    <td>
638 639 640 641
	Application must take care of:
	- Generating subscriptions for "reg" event
	- Processing notifications for "reg" event
	  - Handling of XML document in notifications
Pekka Pessi's avatar
Pekka Pessi committed
642 643 644
    </td>
</tr>

645
<a name="3824"></a>
Pekka Pessi's avatar
Pekka Pessi committed
646 647
<tr valign=top>
    <th align="left">
648
	@RFC3824: ENUM
Pekka Pessi's avatar
Pekka Pessi committed
649 650
    </th>
    <td>
651 652 653
	Tel URIs are supported in any headers including URI parameters,
	e.g., To, From, Contact headers, and Request-URI of the outgoing SIP
	request provided that the next hop is given as SIP or SIPS URI.
Pekka Pessi's avatar
Pekka Pessi committed
654 655
    </td>
    <td>
656 657
	Stack can not resolve E.164 number to address of next
	hop. A proxy in the network must resolve E.164 numbers with ENUM.
Pekka Pessi's avatar
Pekka Pessi committed
658 659 660
    </td>
</tr>

661
<a name="3840"></a>
Pekka Pessi's avatar
Pekka Pessi committed
662 663
<tr valign=top>
    <th align="left">
664
	@RFC3840: Callee Capabilities
Pekka Pessi's avatar
Pekka Pessi committed
665 666
    </th>
    <td>
667 668 669 670 671 672 673 674
	Feature parameters can be added to SIP profiles and sent within
	Contact header of REGISTER request as header parameters.

	UAC can optionally generate media tags for Contact header using
	local media profile.

	Feature parameters can also be sent within any other SIP request as
	extension parameters of Contact header.
Pekka Pessi's avatar
Pekka Pessi committed
675 676
    </td>
    <td>
677 678
	Application must take care of:
        - Processing the feature parameters received in the Contact header
Pekka Pessi's avatar
Pekka Pessi committed
679 680 681
    </td>
</tr>

682

683
<a name="3841"></a>
Pekka Pessi's avatar
Pekka Pessi committed
684 685
<tr valign=top>
    <th align="left">
686
	@RFC3841: Caller Preferences
Pekka Pessi's avatar
Pekka Pessi committed
687 688
    </th>
    <td>
689 690 691 692 693 694 695 696 697 698 699 700 701 702 703
	Built-in support for user-agent behavior.

	UAC can optionally generate Accept-Contact header using local media
	profile.

	SIP parser parses the Accept-Contact and Reject-Contact headers.

        ACK and CANCEL request messages sent have same values
	for Accept-Contact/Reject-Contact or Request-Disposition
	headers as the original request had.

	There are functions for calculating score for contacts.

	The SIP headers explicitly supported (generating,
	parsing and syntax checking) are:
704 705 706
	@ref sip_request_disposition "Request-Disposition" ("d"),
	@ref sip_accept_contact "Accept-Contact" ("a"),
	@ref sip_reject_contact "Reject-Contact" ("j"),
Pekka Pessi's avatar
Pekka Pessi committed
707 708
    </td>
    <td>
709 710
	Application must take care of:
        - UAS processing incoming Accept-Contact or Reject-Contact headers
Pekka Pessi's avatar
Pekka Pessi committed
711 712 713
    </td>
</tr>

714
<a name="3842"></a>
Pekka Pessi's avatar
Pekka Pessi committed
715 716
<tr valign=top>
    <th align="left">
717
	@RFC3842: Message waiting event
Pekka Pessi's avatar
Pekka Pessi committed
718 719
    </th>
    <td>
720 721 722 723 724
	Sofia-SIP supports <a href="#3265">generic SIP event support</a> for
	subscribing SIP event packages and receiving notifications for them.
	Subscriptions are refreshed before expiration when needed and
	subscriptions are terminated on request. Sofia-SIP takes care of
        notified subscription states.
Pekka Pessi's avatar
Pekka Pessi committed
725 726
    </td>
    <td>
727 728 729 730 731 732
	Application must take care of:
	- Generating subscriptions for "message-summary" event
          - Including correct @ref sip_event "Event" and
            @ref sip_accept "Accept" headers in the request (if needed)
	- Processing notifications for "message-summary" event
	  - Handling of summary information in notifications
Pekka Pessi's avatar
Pekka Pessi committed
733 734 735
    </td>
</tr>

736
<a name="3856"></a>
Pekka Pessi's avatar
Pekka Pessi committed
737 738
<tr valign=top>
    <th align="left">
739
	@RFC3856: Presence
Pekka Pessi's avatar
Pekka Pessi committed
740 741
    </th>
    <td>
742 743 744 745 746 747 748 749 750
	Sofia-SIP supports <a href="#3265">generic SIP event support</a> for
	subscribing SIP event packages and receiving notifications for them.
	Subscriptions are refreshed before expiration when needed and
	subscriptions are terminated on request. Sofia-SIP takes care of
        notified subscription states.

	Note: Usage of pres: URI is supported only if the next hop URI to
	where to send SUBSCRIBE is a SIP URI (e.g. of outbound proxy).
	Resolving of pres: URIs by DNS is not supported.
Pekka Pessi's avatar
Pekka Pessi committed
751 752
    </td>
    <td>
753 754 755 756 757 758
	Application must take care of:
	- Generating subscriptions for "presence" event
          - Including correct @ref sip_event "Event" and
            @ref sip_accept "Accept" headers in the request (if needed)
	- Processing notifications for "presence" event
	  - Handling of presence information in notifications
Pekka Pessi's avatar
Pekka Pessi committed
759 760 761
    </td>
</tr>

762
<a name="3857"></a> <a name="3858"></a>
Pekka Pessi's avatar
Pekka Pessi committed
763 764
<tr valign=top>
    <th align="left">
765 766
	@RFC3857: "winfo" event template package<br>
	@RFC3858: winfo format
Pekka Pessi's avatar
Pekka Pessi committed
767 768
    </th>
    <td>
769 770
	Sofia-SIP supports <a href="#3265">generic SIP event support</a> for
	subscribing SIP event packages and receiving notifications for them.
Pekka Pessi's avatar
Pekka Pessi committed
771
	Subscriptions are refreshed before expiration when needed and
772 773
	subscriptions are terminated on request. Sofia-SIP takes care of
        notified subscription states.
Pekka Pessi's avatar
Pekka Pessi committed
774 775 776
    </td>
    <td>
        Application must take care of:
777 778 779 780 781
	- Generating subscriptions for winfo events
          - Including correct @ref sip_event "Event" and
            @ref sip_accept "Accept" headers in the request (if needed)
	- Processing notifications for winfo events:
	  - Processing watcherxinfo XML documents
Pekka Pessi's avatar
Pekka Pessi committed
782 783 784
    </td>
</tr>

785
<a name="3891"></a>
Pekka Pessi's avatar
Pekka Pessi committed
786 787
<tr valign=top>
    <th align="left">
788
	@RFC3891: Replaces
Pekka Pessi's avatar
Pekka Pessi committed
789 790
    </th>
    <td>
791 792
	@ref sip_replaces "Replaces" header is explicitly supported
	(generating, parsing and syntax checking).
Pekka Pessi's avatar
Pekka Pessi committed
793 794 795
    </td>
    <td>
        Application must take care of:
796 797
	- generating @ref sip_replaces "Replaces" header from a dialog and
          matching a dialog with a Replaces header received
Pekka Pessi's avatar
Pekka Pessi committed
798 799 800
    </td>
</tr>

801
<a name="3892"></a>
Pekka Pessi's avatar
Pekka Pessi committed
802 803 804 805 806
<tr valign=top>
    <th align="left">
	@RFC3892: Referred-By
    </th>
    <td>
Pekka Pessi's avatar
Pekka Pessi committed
807 808
	@ref sip_referred_by "Referred-By" header is explicitly supported
	(generating, parsing and syntax checking).
809

Pekka Pessi's avatar
Pekka Pessi committed
810 811 812 813
	Referred-by token can be sent and received in
	text-based SIP message body.
    </td>
    <td>
Pekka Pessi's avatar
Pekka Pessi committed
814 815
        Application must take care of:
	- Generating or processing @ref sip_referred_by "Referred-By" headers
Pekka Pessi's avatar
Pekka Pessi committed
816 817 818 819 820
	- Generating (and encrypting) or verifying (and decrypting) of
	  Referred-by tokens
    </td>
</tr>

821
<a name="3903"></a>
Pekka Pessi's avatar
Pekka Pessi committed
822 823
<tr valign=top>
    <th align="left">
824
	@RFC3903: PUBLISH
Pekka Pessi's avatar
Pekka Pessi committed
825 826
    </th>
    <td>
827 828 829
	PUBLISH method is supported natively. The SIP headers
	explicitly supported (generating, parsing and syntax checking) are
	@ref sip_etag "SIP-ETag" and @ref sip_if_match "SIP-If-Match".
Pekka Pessi's avatar
Pekka Pessi committed
830

831 832
	The <a href="nua/index.html">user-agent engine</a> keep published
	data refreshed until nua_unpublish() is called.
Pekka Pessi's avatar
Pekka Pessi committed
833 834
    </td>
    <td>
835 836 837
        Application must take care of:
        - Including correct @ref sip_event "Event" in the request
        - Permanently storing SIP-ETag
Pekka Pessi's avatar
Pekka Pessi committed
838 839
    </td>
</tr>
Pekka Pessi's avatar
Pekka Pessi committed
840

841
<a name="4028"></a>
Pekka Pessi's avatar
Pekka Pessi committed
842 843
<tr valign=top>
    <th align="left">
844
	@RFC4028: Session Timers
Pekka Pessi's avatar
Pekka Pessi committed
845 846
    </th>
    <td>
847 848 849 850 851
	The SIP session-timer ("timer") extension is supported.

        The session-expires value and refreshing party is negotiated in
	<a href="nua/index.html">user-agent engine</a>. When user-agent
	engine is responsible for refreshes, it will initiate re-INVITE or
852 853 854 855 856
	UPDATE transaction at regular intervals.

	If there has been no SIP activity in session during the refresh
	period, it will try to automatically terminate the call by sending a
	@b BYE request.
857 858

        The SIP headers explicitly supported (generating, parsing and
859
	syntax checking) are @ref sip_session_expires "Session-Expires" ("x") and
860
	@ref sip_min_se "Min-SE".
Pekka Pessi's avatar
Pekka Pessi committed
861 862
    </td>
    <td>
Pekka Pessi's avatar
Pekka Pessi committed
863
	&nbsp;
Pekka Pessi's avatar
Pekka Pessi committed
864 865
    </td>
</tr>
866

867
<a name="4320"></a>
868 869 870 871 872 873 874 875 876 877 878 879 880 881 882 883 884 885 886 887 888
<tr valign=top>
    <th align="left">
	@RFC4320: Actions Addressing Identified Issues with SIP's Non-INVITE Transaction
    </th>
    <td>
	The action 1 (make the best use of provisional responses) is
	supported when NTATAG_EXTRA_100(1) is used with nua_create() or
	nta_agent_create(). The 100 Trying provisional response is sent
	after T2 is expired or when a retransmission is received after T2/2
        after the initial request.

	The action 2 (remove the useless late-response storm) is supported
	by default. The 408 timeout response is not forwarded by default (it's
	forwarding can be enabled with NTATAG_PASS_408(1), however).
    </td>
    <td>
        Application must include NTATAG_EXTRA_100(1) with nua_create() or
	nta_agent_create() tags.
    </td>
</tr>

889 890 891 892 893 894 895 896
</table>

<table border=1 cellpadding=4 cellspacing=0>
<tr>
   <th>Feature</th>
   <th>Supported</td>
   <th>Notes</td>
</tr>
Pekka Pessi's avatar
Pekka Pessi committed
897

898 899 900
<a name="4566"></a>
<a name="2327"></a>
<a name="3266"></a>
Pekka Pessi's avatar
Pekka Pessi committed
901
<tr valign=top>
902
    <th align="left" align="left">
903
	@RFC4566: SDP: Session Description Protocol
Pekka Pessi's avatar
Pekka Pessi committed
904 905
    </th>
    <td>
906 907 908 909 910 911 912 913 914 915 916 917 918 919 920 921 922 923
	Generic support (generating, parsing and syntax checking) for SDP.
	The SDP
        @ref sdp_version_t "v=",
        @ref sdp_origin_t "o=",
	@ref sdp_connection_t "c=",
	@ref sdp_bandwidth_t "b=",
	@ref sdp_time_t "t=",
	@ref sdp_repeat_t "r=",
	@ref sdp_zone_t "z=",
	@ref sdp_key_t "k=",
	@ref sdp_attribute_t "a=", and
	@ref sdp_media_t "m="
        lines are separated and parsed. The "e=", "p=", "s=", and "i=" lines
	are separated.

	The attributes "a=sendrecv", "a=sendonly", "a=recvonly",
	"a=inactive", @ref sdp_rtpmap_s "a=rtpmap", and "a=fmtp" are parsed.

924 925 926
	The implementation partially implements @RFC4566. Note that
	definiton of 'token' was updated in @RFC4566 and the parser has not
	been updated yet.
Pekka Pessi's avatar
Pekka Pessi committed
927 928
    </td>
    <td>
929 930 931
      @RFC4566 obsoletes
      - @RFC2327: SDP (Session Description Protocol)
      - @RFC3266: IP6 in SDP
Pekka Pessi's avatar
Pekka Pessi committed
932 933 934
    </td>
</tr>

935
<a name="3264"></a>
Pekka Pessi's avatar
Pekka Pessi committed
936 937
<tr valign=top>
    <th align="left">
938
	@RFC3264: SDP Offer/Answer Negotiation
Pekka Pessi's avatar
Pekka Pessi committed
939 940
    </th>
    <td>
941
	Generating and processing offers or answers.
Pekka Pessi's avatar
Pekka Pessi committed
942 943
    </td>
    <td>
944 945
	- "a=fmtp" parameters are not taken into account
          when generating or processing answer
Pekka Pessi's avatar
Pekka Pessi committed
946 947 948
    </td>
</tr>

949
<a name="3312"></a>
Pekka Pessi's avatar
Pekka Pessi committed
950 951
<tr valign=top>
    <th align="left">
952
	@RFC3312: Preconditions
Pekka Pessi's avatar
Pekka Pessi committed
953 954
    </th>
    <td>
955 956 957 958 959 960
	Sofia-SIP provides <a href="#2616">generic support</a> for attribute
	lines that conform to SDP syntax.

        Sofia-SIP supports handling SIP feature tags in
	@ref sip_proxy_require "Proxy-Require",
        @ref sip_require "Require",
961
        @ref sip_supported "Supported" ("k"),
962 963
        and
        @ref sip_unsupported "Unsupported" header.
Pekka Pessi's avatar
Pekka Pessi committed
964 965
    </td>
    <td>
966 967 968
	Application must take care of:
	- Semantics and handling of preconditions
	- Reservation of resources
Pekka Pessi's avatar
Pekka Pessi committed
969 970 971
    </td>
</tr>

972
<a name="3388"></a>
Pekka Pessi's avatar
Pekka Pessi committed
973 974
<tr valign=top>
    <th align="left">
975
	@RFC3388: Grouping of Media Lines
Pekka Pessi's avatar
Pekka Pessi committed
976 977
    </th>
    <td>
978 979 980 981
	Sofia-SIP provides <a href="#2616">generic support</a> for attribute
	lines that conform to SDP syntax.

	@RFC3388 defines mid, group, LS and FID are predefined strings to be
Pekka Pessi's avatar
Pekka Pessi committed
982 983 984
	used within attribute line
    </td>
    <td>
985
        Application must take care of:
Pekka Pessi's avatar
Pekka Pessi committed
986 987 988 989 990 991
	- Generating or processing the attribute lines
	- Grouping the media for transport accordingly
    </td>
</tr>


992
<a name="3407"></a>
Pekka Pessi's avatar
Pekka Pessi committed
993 994
<tr valign=top>
    <th align="left">
995
	@RFC3407: Capability Declaration
Pekka Pessi's avatar
Pekka Pessi committed
996 997
    </th>
    <td>
998 999
	Sofia-SIP provides <a href="#2616">generic support</a> for attribute
	lines that conform to SDP syntax.
Pekka Pessi's avatar
Pekka Pessi committed
1000 1001
    </td>
    <td>
1002 1003 1004 1005
        Application must take care of:
	- Defining sqn, cdsc, cpar etc. strings needed in a= line
	- Generating or processing the attribute lines
	- Capability negotiation itself
Pekka Pessi's avatar
Pekka Pessi committed
1006 1007 1008 1009
    </td>
</tr>


1010
<a name="3524"></a>
Pekka Pessi's avatar
Pekka Pessi committed
1011 1012
<tr valign=top>
    <th align="left">
1013
	@RFC3524: SRF
Pekka Pessi's avatar
Pekka Pessi committed
1014 1015
    </th>
    <td>
1016 1017
	Sofia-SIP provides <a href="#2616">generic support</a> for attribute
	lines that conform to SDP syntax.
Pekka Pessi's avatar
Pekka Pessi committed
1018 1019
    </td>
    <td>
1020 1021 1022
        Application must take care of:
	- Defining SRF string needed in a= line
	- Generating or processing the attribute lines
Pekka Pessi's avatar
Pekka Pessi committed
1023 1024 1025
    </td>
</tr>

1026
<a name="3556"></a>
Pekka Pessi's avatar
Pekka Pessi committed
1027 1028
<tr valign=top>
    <th align="left">
1029
	@RFC3556: Bandwidth
Pekka Pessi's avatar
Pekka Pessi committed
1030 1031
    </th>
    <td>
1032 1033
	Sofia-SIP provides <a href="#2616">generic support</a> for attribute
	lines that conform to SDP syntax.
Pekka Pessi's avatar
Pekka Pessi committed
1034 1035
    </td>
    <td>
1036 1037 1038
        Application must take care of:
	- Generating or processing RS and RR bandwidth modifiers
	- Semantics of bandwidth allocation
Pekka Pessi's avatar
Pekka Pessi committed
1039 1040 1041
    </td>
</tr>

1042
<a name="3605"></a>
Pekka Pessi's avatar
Pekka Pessi committed
1043 1044
<tr valign=top>
    <th align="left">
1045
	@RFC3605: RTCP attribute
Pekka Pessi's avatar
Pekka Pessi committed
1046 1047
    </th>
    <td>
1048 1049
	Sofia-SIP provides <a href="#2616">generic support</a> for attribute
	lines that conform to SDP syntax.
Pekka Pessi's avatar
Pekka Pessi committed
1050 1051
    </td>
    <td>
1052 1053 1054
        Application must take care of:
	- Discovering port numbers
	- Generating or processing the RTCP attribute lines
Pekka Pessi's avatar
Pekka Pessi committed
1055 1056 1057
    </td>
</tr>

1058
<a name="3890"></a>
Pekka Pessi's avatar
Pekka Pessi committed
1059 1060
<tr valign=top>
    <th align="left">
1061
	@RFC3890: TIAS
Pekka Pessi's avatar
Pekka Pessi committed
1062 1063
    </th>
    <td>
1064 1065
	Sofia-SIP provides <a href="#2616">generic support</a> for attribute
	lines that conform to SDP syntax.
Pekka Pessi's avatar
Pekka Pessi committed
1066 1067
    </td>
    <td>
1068 1069 1070
        Application must take care of:
	- Generating or processing TIAS bandwidth modifiers
	- Generating or processing the maxprate attribute lines
Pekka Pessi's avatar
Pekka Pessi committed
1071 1072 1073
    </td>
</tr>

1074 1075 1076 1077 1078 1079 1080 1081
</table>


*/

/* Overflow:

<a name="4566"></a>
1082 1083 1084 1085 1086 1087 1088 1089 1090 1091 1092 1093
<tr valign=top>
    <th align="left">
	@RFC4566: SDP: Session Description Protocol
    </th>
    <td>
    Obsoletes RFC2327 and RFC3266.
    </td>
    <td>
	&nbsp;
    </td>
</tr>

1094

1095
<a name="3320"></a>
Pekka Pessi's avatar
Pekka Pessi committed
1096 1097
<tr valign=top>
    <th align="left">
1098
	@RFC3320: SigComp
Pekka Pessi's avatar
Pekka Pessi committed
1099 1100
    </th>
    <td>
1101 1102 1103
    	Support for using SigComp for compression and
	decompression of SIP/SDP messages. By default, dynamic
	compression is used.
Pekka Pessi's avatar
Pekka Pessi committed
1104

1105
	Decompression using UDVM
Pekka Pessi's avatar
Pekka Pessi committed
1106 1107
    </td>
    <td>
Pekka Pessi's avatar
Pekka Pessi committed
1108
	&nbsp;
Pekka Pessi's avatar
Pekka Pessi committed
1109 1110 1111
    </td>
</tr>

1112
<a name="3321"></a>
Pekka Pessi's avatar
Pekka Pessi committed
1113 1114
<tr valign=top>
    <th align="left">
1115
	@RFC3321: SigComp Extended operations
Pekka Pessi's avatar
Pekka Pessi committed
1116 1117
    </th>
    <td>
1118
	Support for SigComp extended operations.
Pekka Pessi's avatar
Pekka Pessi committed
1119 1120
    </td>
    <td>
1121 1122 1123 1124
	- Explicit Acknowledgment Scheme
	- Shared Compression
	- Checkpoint State
	- Implicit Deletion for Dictionary Update
Pekka Pessi's avatar
Pekka Pessi committed
1125 1126
    </td>
</tr>
Pekka Pessi's avatar
Pekka Pessi committed
1127

1128
<a name="3325"></a>
Pekka Pessi's avatar
Pekka Pessi committed
1129 1130
<tr valign=top>
    <th align="left">
1131
	@RFC3325: Asserted Identity
Pekka Pessi's avatar
Pekka Pessi committed
1132 1133
    </th>
    <td>
1134 1135
	Explicit support (generating, parsing and syntax checking) for the
	following SIP headers: P-Asserted-Identity, P-Preferred-Identity
Pekka Pessi's avatar
Pekka Pessi committed
1136 1137
    </td>
    <td>
1138 1139
	- Recognizing trust domains and enforcing handling of headers
	  based on those
Pekka Pessi's avatar
Pekka Pessi committed
1140 1141 1142
    </td>
</tr>

1143
<a name="3485"></a>
Pekka Pessi's avatar
Pekka Pessi committed
1144 1145
<tr valign=top>
    <th align="left">
1146
	@RFC3485: SIP/SDP Dictionary
Pekka Pessi's avatar
Pekka Pessi committed
1147 1148
    </th>
    <td>
1149 1150
	Support for SigComp static compression using SIP/SDP
	dictionary.
Pekka Pessi's avatar
Pekka Pessi committed
1151 1152
    </td>
    <td>
1153
	&nbsp;
Pekka Pessi's avatar
Pekka Pessi committed
1154 1155 1156
    </td>
</tr>

1157 1158 1159 1160 1161



	- Implicitly registered user identities

1162
<a name="3959"></a>
Pekka Pessi's avatar
Pekka Pessi committed
1163 1164 1165 1166 1167 1168 1169 1170 1171 1172 1173 1174 1175 1176 1177
<tr valign=top>
    <th align="left">
	@RFC3959: early-session
    </th>
    <td>
	Early-session value can be used within Content-Disposition,
	Supported and Require headers.
    </td>
    <td>
	- Generating of Content-Disposition, Supported and Require
	- Handling of multipart bodies with early and session SDP
    </td>
</tr>

*/