conformance.docs 33.5 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
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>
<a href="#3325">RFC 3325</a> <br>
<a href="#3327">RFC 3327</a> <br>
25
</td><td>
26 27 28 29 30 31
<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>
32
<a href="#3581">RFC 3581</a> <br>
33 34 35 36 37 38
<a href="#3608">RFC 3608</a> <br>
<a href="#3680">RFC 3680</a> <br>
<a href="#3824">RFC 3824</a> <br>
<a href="#3840">RFC 3840</a> <br>
<a href="#3841">RFC 3841</a> <br>
<a href="#3842">RFC 3842</a> <br>
39
</td><td>
40 41 42
<a href="#3856">RFC 3856</a> <br>
<a href="#3857">RFC 3857</a> <br>
<a href="#3858">RFC 3858</a> <br>
43 44
<a href="#3859">RFC 3859</a> <br>
<a href="#3860">RFC 3860</a> <br>
45 46 47 48
<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>
49
<a href="#4168">RFC 4168</a> <br>
50
<a href="#4320">RFC 4320</a> <br>
51
<a href="#4488">RFC 4488</a> <br>
52
</td><td>
53
<a href="#4566">RFC 4566</a> <br>
54 55 56 57 58 59 60
<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>
61
<a href="#3551">RFC 3551</a> <br>
62 63 64 65 66 67
<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
68 69 70 71
<table border=1 cellpadding=4 cellspacing=0>
<tr>
   <th>Feature</th>
   <th>Supported</td>
Pekka Pessi's avatar
Pekka Pessi committed
72
   <th>Notes</td>
Pekka Pessi's avatar
Pekka Pessi committed
73 74
</tr>

75
<a name="3261"></a>
Pekka Pessi's avatar
Pekka Pessi committed
76 77 78 79 80 81
<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
82
	application to operate as a SIP UA, SIP proxy or a redirect server
Pekka Pessi's avatar
Pekka Pessi committed
83 84
	according to the @RFC3261.

85 86 87 88
	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
89
	-# transaction user (UAS and UAC cores, proxy core)
90 91
	-# SIP elements: <a href="nua/index.html">user agent</a>
           client and server, proxies,
Pekka Pessi's avatar
Pekka Pessi committed
92 93 94
	   registrars
    </td>
    <td>
Pekka Pessi's avatar
Pekka Pessi committed
95
        &nbsp;
Pekka Pessi's avatar
Pekka Pessi committed
96 97 98
    </td>
</tr>

99
<a name="3261.19"></a> <a name="3261.20"></a>
Pekka Pessi's avatar
Pekka Pessi committed
100 101
<tr valign=top>
    <th align="left">
Pekka Pessi's avatar
Pekka Pessi committed
102
	@RFC3261 Sections&nbsp;19&nbsp;and&nbsp;20:<br>
Pekka Pessi's avatar
Pekka Pessi committed
103 104 105 106
	Syntax and encoding
    </td>
    <td>
	The supported @RFC3261 methods are: @b REGISTER, @b OPTIONS, @b
107
	INVITE, @b ACK, @b CANCEL, @b BYE, as well as extension methods
108 109 110 111 112 113 114 115 116 117 118 119 120
	<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
121 122 123 124

	@ref sip_accept "Accept",
	@ref sip_accept_encoding "Accept-Encoding",
	@ref sip_accept_language "Accept-Language",
125
	@ref sip_alert_info "Alert-Info" (extension in @VERSION_1_12_7),
Pekka Pessi's avatar
Pekka Pessi committed
126 127
	@ref sip_allow "Allow",
	@ref sip_authentication_info "Authentication-Info",
128
	@ref sip_authorization "Authorization",
129
	@ref sip_call_id "Call-ID" ("i"),
Pekka Pessi's avatar
Pekka Pessi committed
130
	@ref sip_call_info "Call-Info",
131
	@ref sip_contact "Contact" ("m"),
Pekka Pessi's avatar
Pekka Pessi committed
132
	@ref sip_content_disposition "Content-Disposition",
133
        @ref sip_content_encoding "Content-Encoding" ("e"),
Pekka Pessi's avatar
Pekka Pessi committed
134
	@ref sip_content_language "Content-Language",
135 136
	@ref sip_content_length "Content-Length" ("l"),
	@ref sip_content_type "Content-Type" ("c"),
Pekka Pessi's avatar
Pekka Pessi committed
137 138 139 140
	@ref sip_cseq "CSeq",
	@ref sip_date "Date",
	@ref sip_error_info "Error-Info",
	@ref sip_expires "Expires",
141
	@ref sip_from "From" ("f"),
Pekka Pessi's avatar
Pekka Pessi committed
142 143 144 145 146
	@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",
147 148 149 150
	@ref sip_p_asserted_identity "P-Asserted-Identity" 
        (extension in @VERSION_1_12_7),
	@ref sip_p_preferred_identity "P-Preferred-Identity" 
        (extension in @VERSION_1_12_7),
Pekka Pessi's avatar
Pekka Pessi committed
151
	@ref sip_priority "Priority",
152 153
	@ref sip_proxy_authenticate "Proxy-Authenticate",
	@ref sip_proxy_authorization "Proxy-Authorization",
Pekka Pessi's avatar
Pekka Pessi committed
154 155
	@ref sip_proxy_require "Proxy-Require",
	@ref sip_record_route "Record-Route",
156 157 158
	@ref sip_refer_sub "Refer-Sub" (@VERSION_1_12_5),
	@ref sip_remote_party_id "Remote-Party-ID" (extension in @VERSION_1_12_7),
	@ref sip_reply_to "Reply-To" (extension in @VERSION_1_12_7),
Pekka Pessi's avatar
Pekka Pessi committed
159 160 161 162
	@ref sip_require "Require",
	@ref sip_retry_after "Retry-After",
	@ref sip_route "Route",
	@ref sip_server "Server",
163 164
	@ref sip_subject "Subject" ("s"),
	@ref sip_supported "Supported" ("k"),
Pekka Pessi's avatar
Pekka Pessi committed
165
	@ref sip_timestamp "Timestamp",
166
	@ref sip_to "To" ("t"),
Pekka Pessi's avatar
Pekka Pessi committed
167 168
	@ref sip_unsupported "Unsupported",
	@ref sip_user_agent "User-Agent",
169
	@ref sip_via "Via" ("v"),
Pekka Pessi's avatar
Pekka Pessi committed
170 171 172
	@ref sip_warning "Warning", and
	@ref sip_www_authenticate "WWW-Authenticate".

Pekka Pessi's avatar
Pekka Pessi committed
173 174
	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
175

Pekka Pessi's avatar
Pekka Pessi committed
176 177
	It is possible to extend SIP parser in run-time with header-specific
        parsers.
Pekka Pessi's avatar
Pekka Pessi committed
178 179
    </td>
    <td>
180 181
	- Automatic escaping of reserved characters has not been
	  implemented.
182
	- Using NUL (zero byte) in double-quoted strings has not been implemented
Pekka Pessi's avatar
Pekka Pessi committed
183 184 185
   </td>
</tr>

186
<a name="3261.18"></a>
Pekka Pessi's avatar
Pekka Pessi committed
187 188
<tr valign=top>
    <th align="left">
Pekka Pessi's avatar
Pekka Pessi committed
189 190
	@RFC3261 Section 18:<br>
	UDP and TCP transports
Pekka Pessi's avatar
Pekka Pessi committed
191 192
    </th>
    <td>
193 194 195 196 197 198
        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
199 200

	TCP connections are reused by client. However, server closes
201 202 203
	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
204

205 206
	Server tries to use same TCP connection to return response as the
	request was received.
Pekka Pessi's avatar
Pekka Pessi committed
207 208 209 210

	Only one SIP message is accepted per UDP message, as per @RFC3261.
    </td>
    <td>
211
	There is <a href="#4168">experimental support for SCTP</a>, too.
Pekka Pessi's avatar
Pekka Pessi committed
212 213 214
    </td>
</tr>

215
<a name="3261.17"></a>
Pekka Pessi's avatar
Pekka Pessi committed
216 217
<tr valign=top>
    <th align="left">
Pekka Pessi's avatar
Pekka Pessi committed
218
	@RFC3261 Section 17:<br> Transactions
Pekka Pessi's avatar
Pekka Pessi committed
219 220 221
    </th>
    <td>
        Transaction state engines function as specified in @RFC3261 section
222
	17. There is special handling of methods @b INVITE, @b ACK, and @b
Pekka Pessi's avatar
Pekka Pessi committed
223 224 225 226
	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
227
	values for T1, T1x64, T2 and T4 can be changed via
228
        configuration tags defined in <sofia-sip/nta_tag.h>.
229 230 231 232

	The SIP timer C is implemented from @VERSION_1_12_7. Also, its value
	can be changed via configuration tag NTATAG_TIMER_C() defined in
	<sofia-sip/nta_tag.h>.
Pekka Pessi's avatar
Pekka Pessi committed
233 234
    </td>
    <td>
235
	&nbsp;
Pekka Pessi's avatar
Pekka Pessi committed
236 237 238 239
    </td>
</tr>


240
<a name="3261.26"></a>
Pekka Pessi's avatar
Pekka Pessi committed
241 242
<tr valign=top>
    <th align="left">
243
	@RFC3261 Section 26:<br> Security
Pekka Pessi's avatar
Pekka Pessi committed
244 245 246 247 248 249 250
    </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
251
	Missing:
252
	- Authorizing connections with TLS certificates
Pekka Pessi's avatar
Pekka Pessi committed
253 254 255 256
	- S/MIME
    </td>
</tr>

257
<a name="2617"></a>
Pekka Pessi's avatar
Pekka Pessi committed
258 259
<tr valign=top>
    <th align="left">
Pekka Pessi's avatar
Pekka Pessi committed
260
	@RFC2617: HTTP Digest Authentication
Pekka Pessi's avatar
Pekka Pessi committed
261 262
    </th>
    <td>
263 264
	Sofia-SIP includes authentication client and server modules
	implementing HTTP Digest authentication.
Pekka Pessi's avatar
Pekka Pessi committed
265 266

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

271 272 273 274 275
        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
276 277

	The SIP authentication headers supported (generating, parsing and
278 279
	syntax checking) are:
	@ref sip_authorization "Authorization",
Pekka Pessi's avatar
Pekka Pessi committed
280
	@ref sip_authentication_info "Authentication-Info",
281
	@ref sip_proxy_authenticate "Proxy-Authenticate",
Pekka Pessi's avatar
Pekka Pessi committed
282 283 284
	@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
285 286 287 288

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

289 290 291 292
	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
293 294
    </td>
    <td>
Pekka Pessi's avatar
Pekka Pessi committed
295
	Missing:
296
        - Using nextnonce
Pekka Pessi's avatar
Pekka Pessi committed
297 298 299 300
	- Mutual authentication
    </td>
</tr>

301
<a name="3262"></a>
Pekka Pessi's avatar
Pekka Pessi committed
302 303
<tr valign=top>
    <th align="left">
304
	@RFC3262: PRACK and 100rel
Pekka Pessi's avatar
Pekka Pessi committed
305 306
    </th>
    <td>
307 308 309 310 311 312 313 314 315 316
	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
317 318
    </td>
    <td>
319
	&nbsp;
Pekka Pessi's avatar
Pekka Pessi committed
320 321 322
    </td>
</tr>

323
<a name="3263"></a>
Pekka Pessi's avatar
Pekka Pessi committed
324 325
<tr valign=top>
    <th align="left">
326
	@RFC3263: Locating SIP Servers
Pekka Pessi's avatar
Pekka Pessi committed
327 328
    </th>
    <td>
329 330
	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
331 332
    </td>
    <td>
333 334
	- Resolving any other types of URIs than SIP or SIPS URIs, e.g., IM:
	or PRES: URIs.
Pekka Pessi's avatar
Pekka Pessi committed
335 336 337
    </td>
</tr>

338
<a name="3265"></a>
Pekka Pessi's avatar
Pekka Pessi committed
339 340
<tr valign=top>
    <th align="left">
341
	@RFC3265: SIP Event Notifications
Pekka Pessi's avatar
Pekka Pessi committed
342 343
    </th>
    <td>
344 345
	SIP extensions for subscribing and processing asynchronous event
	notifications as defined in @RFC3265.
Pekka Pessi's avatar
Pekka Pessi committed
346

347 348 349 350 351
	Includes dialog level support for sending and refreshing SUBSCRIBE
	and receiving NOTIFY messages.

	The SIP headers explicitly supported (generating, parsing and
	syntax checking) are
352
        @ref sip_event "Event" ("o"),
353 354 355 356
	@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
357 358
    </td>
    <td>
359 360 361
	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
362 363 364
    </td>
</tr>

365
<a name="2806"></a>
Pekka Pessi's avatar
Pekka Pessi committed
366 367
<tr valign=top>
    <th align="left">
368
	@RFC2806: tel URI
Pekka Pessi's avatar
Pekka Pessi committed
369 370
    </th>
    <td>
371 372
	Sofia-SIP supports handling of any URI type. Sofia-SIP parses tel:
        URIs.
Pekka Pessi's avatar
Pekka Pessi committed
373 374
    </td>
    <td>
Pekka Pessi's avatar
Pekka Pessi committed
375
	Missing:
376
	- Resolving the tel: URIs
Pekka Pessi's avatar
Pekka Pessi committed
377 378 379
    </td>
</tr>

380
<a name="2976"></a>
Pekka Pessi's avatar
Pekka Pessi committed
381 382
<tr valign=top>
    <th align="left">
383
	@RFC2976: INFO
Pekka Pessi's avatar
Pekka Pessi committed
384 385
    </th>
    <td>
386
	INFO method is supported within a dialog natively.
Pekka Pessi's avatar
Pekka Pessi committed
387 388
    </td>
    <td>
389 390
	Not implemented:
	- Generating or processing contents of INFO requests
Pekka Pessi's avatar
Pekka Pessi committed
391 392 393
    </td>
</tr>

394

395
<a name="3311"></a>
Pekka Pessi's avatar
Pekka Pessi committed
396 397
<tr valign=top>
    <th align="left">
398
	@RFC3311: UPDATE
Pekka Pessi's avatar
Pekka Pessi committed
399 400
    </th>
    <td>
401 402 403
	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
404

405
	Offer-Answer negotiation with UPDATE is implemented in nua.
Pekka Pessi's avatar
Pekka Pessi committed
406 407
    </td>
    <td>
408 409
	Application must take care of:
        - Initiating UPDATE requests
Pekka Pessi's avatar
Pekka Pessi committed
410 411 412
    </td>
</tr>

413

414
<a name="3313"></a>
Pekka Pessi's avatar
Pekka Pessi committed
415 416
<tr valign=top>
    <th align="left">
417
	@RFC3313: Media Authentication
Pekka Pessi's avatar
Pekka Pessi committed
418 419
    </th>
    <td>
420 421 422
	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
423 424
    </td>
    <td>
425 426
        Application must take care of:
	- Passing the authorization token to QoS reservation request
Pekka Pessi's avatar
Pekka Pessi committed
427 428 429
    </td>
</tr>

Pekka Pessi's avatar
Pekka Pessi committed
430

431
<a name="3323"></a>
Pekka Pessi's avatar
Pekka Pessi committed
432 433
<tr valign=top>
    <th align="left">
434
	@RFC3323: Privacy
Pekka Pessi's avatar
Pekka Pessi committed
435 436
    </th>
    <td>
437 438
	@ref sip_privacy "Privacy" header is supported (generating, parsing
        and syntax checking).
Pekka Pessi's avatar
Pekka Pessi committed
439

440 441 442 443
	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
444

445 446
	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
447 448
    </td>
    <td>
449 450 451 452 453 454
        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
455 456 457
    </td>
</tr>

Pekka Pessi's avatar
Pekka Pessi committed
458

459
<a name="3326"></a>
Pekka Pessi's avatar
Pekka Pessi committed
460 461
<tr valign=top>
    <th align="left">
462
	@RFC3326: Reason
Pekka Pessi's avatar
Pekka Pessi committed
463 464
    </th>
    <td>
465 466
	Sofia-SIP supports @ref sip_reason "Reason" header (generating,
	parsing and syntax checking).
Pekka Pessi's avatar
Pekka Pessi committed
467 468
    </td>
    <td>
469 470
        Application must take care of:
	- Generating or processing Reason headers
Pekka Pessi's avatar
Pekka Pessi committed
471 472 473
    </td>
</tr>

474

475
<a name="3325"></a>
Pekka Pessi's avatar
Pekka Pessi committed
476
<tr valign=top>
Pekka Pessi's avatar
Pekka Pessi committed
477
    <th align="left">
478
	@RFC3325: Asserted Identity
Pekka Pessi's avatar
Pekka Pessi committed
479
    </th>
Pekka Pessi's avatar
Pekka Pessi committed
480
    <td>
481 482 483 484 485 486 487
	Sofia-SIP supports 
	@ref sip_p_asserted_identity "P-Asserted-Identity" and
	@ref sip_p_preferred_identity "P-Preferred-Identity" headers
        (generating, parsing and syntax checking). Also the non-standard
        header @ref sip_remote_party_id "Remote-Party-ID" is supported.

        @NEW_1_12_7.
Pekka Pessi's avatar
Pekka Pessi committed
488 489
    </td>
    <td>
490 491 492 493
	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
494 495 496
    </td>
</tr>

497
<a name="3327"></a>
Pekka Pessi's avatar
Pekka Pessi committed
498 499
<tr valign=top>
    <th align="left">
500
	@RFC3327: Path
Pekka Pessi's avatar
Pekka Pessi committed
501 502
    </th>
    <td>
503 504 505 506 507
	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
508 509
    </td>
    <td>
510
	&nbsp;
Pekka Pessi's avatar
Pekka Pessi committed
511 512 513
    </td>
</tr>

514
<a name="3329"></a>
Pekka Pessi's avatar
Pekka Pessi committed
515
<tr valign=top>
516 517 518
    <th align="left">
	@RFC3329:
	Security Agreement
Pekka Pessi's avatar
Pekka Pessi committed
519 520
    </th>
    <td>
521 522 523
	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
524

525 526 527 528 529
	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
530

531
	Security-mechanism supported is "digest".
Pekka Pessi's avatar
Pekka Pessi committed
532 533
    </td>
    <td>
534
	Correct @e d-ver value is not calculated.
Pekka Pessi's avatar
Pekka Pessi committed
535 536 537
    </td>
</tr>

538
<a name="3361"></a>
Pekka Pessi's avatar
Pekka Pessi committed
539 540
<tr valign=top>
    <th align="left">
541
	@RFC3361: DHCPv4 option for locating SIP servers.
Pekka Pessi's avatar
Pekka Pessi committed
542 543
    </th>
    <td>
544
	Sofia-SIP supports outbound proxy.
Pekka Pessi's avatar
Pekka Pessi committed
545 546
    </td>
    <td>
547 548 549
	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
550 551 552
    </td>
</tr>

553
<a name="3420"></a>
Pekka Pessi's avatar
Pekka Pessi committed
554 555
<tr valign=top>
    <th align="left">
556
	@RFC3420: message/sipfrag
Pekka Pessi's avatar
Pekka Pessi committed
557 558
    </th>
    <td>
559 560
	Sofia-SIP passes the received SIP message headers to application
	which can create a message/sipfrag payload.
Pekka Pessi's avatar
Pekka Pessi committed
561 562
    </td>
    <td>
563 564
        Application must take care of:
	- processing the SIP message fragments
Pekka Pessi's avatar
Pekka Pessi committed
565 566 567
    </td>
</tr>

568
<a name="3428"></a>
Pekka Pessi's avatar
Pekka Pessi committed
569 570
<tr valign=top>
    <th align="left">
571
	@RFC3428: MESSAGE
Pekka Pessi's avatar
Pekka Pessi committed
572 573
    </th>
    <td>
574
	MESSAGE method is supported natively.
Pekka Pessi's avatar
Pekka Pessi committed
575 576
    </td>
    <td>
Pekka Pessi's avatar
Pekka Pessi committed
577
	&nbsp;
Pekka Pessi's avatar
Pekka Pessi committed
578 579 580
    </td>
</tr>

581
<a name="3486"></a>
Pekka Pessi's avatar
Pekka Pessi committed
582 583
<tr valign=top>
    <th align="left">
584
	@RFC3486: Compressing SIP
Pekka Pessi's avatar
Pekka Pessi committed
585 586
    </th>
    <td>
587 588 589
	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
590 591
    </td>
    <td>
592
	SigComp itself is not supported.
Pekka Pessi's avatar
Pekka Pessi committed
593 594 595
    </td>
</tr>

596
<a name="3515"></a>
Pekka Pessi's avatar
Pekka Pessi committed
597 598
<tr valign=top>
    <th align="left">
599
	@RFC3515: REFER
Pekka Pessi's avatar
Pekka Pessi committed
600 601
    </th>
    <td>
602 603 604 605 606 607 608 609
	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
610
	checking) @ref sip_refer_to "Refer-To" ("r") SIP header.
611 612 613 614

	See also support for
	<a href="#3891">RFC 3891</a> and
        <a href="#3892">RFC 3892</a>.
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="3608"></a>
Pekka Pessi's avatar
Pekka Pessi committed
622 623
<tr valign=top>
    <th align="left">
624
	@RFC3608: Service-Route
Pekka Pessi's avatar
Pekka Pessi committed
625 626
    </th>
    <td>
627 628 629 630 631 632 633
	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
634 635
    </td>
    <td>
636
	&nbsp;
Pekka Pessi's avatar
Pekka Pessi committed
637 638 639
    </td>
</tr>

640
<a name="3680"></a>
Pekka Pessi's avatar
Pekka Pessi committed
641 642
<tr valign=top>
    <th align="left">
643
	@RFC3680: "reg" event
Pekka Pessi's avatar
Pekka Pessi committed
644 645
    </th>
    <td>
646 647 648 649 650 651 652 653 654
	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
655 656
    </td>
    <td>
657 658 659 660
	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
661 662 663
    </td>
</tr>

664
<a name="3824"></a>
Pekka Pessi's avatar
Pekka Pessi committed
665 666
<tr valign=top>
    <th align="left">
667
	@RFC3824: ENUM
Pekka Pessi's avatar
Pekka Pessi committed
668 669
    </th>
    <td>
670 671 672
	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
673 674
    </td>
    <td>
675 676
	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
677 678 679
    </td>
</tr>

680
<a name="3840"></a>
Pekka Pessi's avatar
Pekka Pessi committed
681 682
<tr valign=top>
    <th align="left">
683
	@RFC3840: Callee Capabilities
Pekka Pessi's avatar
Pekka Pessi committed
684 685
    </th>
    <td>
686 687 688 689 690 691 692 693
	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
694 695
    </td>
    <td>
696 697
	Application must take care of:
        - Processing the feature parameters received in the Contact header
Pekka Pessi's avatar
Pekka Pessi committed
698 699 700
    </td>
</tr>

701

702
<a name="3841"></a>
Pekka Pessi's avatar
Pekka Pessi committed
703 704
<tr valign=top>
    <th align="left">
705
	@RFC3841: Caller Preferences
Pekka Pessi's avatar
Pekka Pessi committed
706 707
    </th>
    <td>
708 709 710 711 712 713 714 715 716 717 718 719 720 721 722
	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:
723 724 725
	@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
726 727
    </td>
    <td>
728 729
	Application must take care of:
        - UAS processing incoming Accept-Contact or Reject-Contact headers
Pekka Pessi's avatar
Pekka Pessi committed
730 731 732
    </td>
</tr>

733
<a name="3842"></a>
Pekka Pessi's avatar
Pekka Pessi committed
734 735
<tr valign=top>
    <th align="left">
736
	@RFC3842: Message waiting event
Pekka Pessi's avatar
Pekka Pessi committed
737 738
    </th>
    <td>
739 740 741 742 743
	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
744 745
    </td>
    <td>
746 747 748 749 750 751
	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
752 753 754
    </td>
</tr>

755
<a name="3856"></a><a name="3859"></a>
Pekka Pessi's avatar
Pekka Pessi committed
756 757
<tr valign=top>
    <th align="left">
758 759
	@RFC3856: Presence <br />
	@RFC3859: Common Profile for Presence
Pekka Pessi's avatar
Pekka Pessi committed
760 761
    </th>
    <td>
762 763 764 765 766 767 768 769 770
	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
771 772
    </td>
    <td>
773 774 775 776 777 778
	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
779 780 781
    </td>
</tr>

782
<a name="3857"></a> <a name="3858"></a>
Pekka Pessi's avatar
Pekka Pessi committed
783 784
<tr valign=top>
    <th align="left">
785 786
	@RFC3857: "winfo" event template package<br>
	@RFC3858: winfo format
Pekka Pessi's avatar
Pekka Pessi committed
787 788
    </th>
    <td>
789 790
	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
791
	Subscriptions are refreshed before expiration when needed and
792 793
	subscriptions are terminated on request. Sofia-SIP takes care of
        notified subscription states.
Pekka Pessi's avatar
Pekka Pessi committed
794 795 796
    </td>
    <td>
        Application must take care of:
797 798 799 800
	- 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:
801 802 803 804 805 806 807 808 809 810 811 812 813 814 815 816
	  - Processing watcherinfo XML documents
    </td>
</tr>

<a name="3860"></a>
<tr valign=top>
    <th align="left">
	@RFC3860: Common Profile for IM
    </th>
    <td>
	Sofia-SIP supports handling of any URI type. Sofia-SIP parses "im:"
        URIs.
    </td>
    <td>
        Application must take care of:
	- resolving the "im:" URI
Pekka Pessi's avatar
Pekka Pessi committed
817 818 819
    </td>
</tr>

820
<a name="3891"></a>
Pekka Pessi's avatar
Pekka Pessi committed
821 822
<tr valign=top>
    <th align="left">
823
	@RFC3891: Replaces
Pekka Pessi's avatar
Pekka Pessi committed
824 825
    </th>
    <td>
826 827
	@ref sip_replaces "Replaces" header is explicitly supported
	(generating, parsing and syntax checking).
Pekka Pessi's avatar
Pekka Pessi committed
828 829 830
    </td>
    <td>
        Application must take care of:
831 832
	- 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
833 834 835
    </td>
</tr>

836
<a name="3892"></a>
Pekka Pessi's avatar
Pekka Pessi committed
837 838 839 840 841
<tr valign=top>
    <th align="left">
	@RFC3892: Referred-By
    </th>
    <td>
Pekka Pessi's avatar
Pekka Pessi committed
842 843
	@ref sip_referred_by "Referred-By" header is explicitly supported
	(generating, parsing and syntax checking).
844

Pekka Pessi's avatar
Pekka Pessi committed
845 846 847 848
	Referred-by token can be sent and received in
	text-based SIP message body.
    </td>
    <td>
Pekka Pessi's avatar
Pekka Pessi committed
849 850
        Application must take care of:
	- Generating or processing @ref sip_referred_by "Referred-By" headers
Pekka Pessi's avatar
Pekka Pessi committed
851 852 853 854 855
	- Generating (and encrypting) or verifying (and decrypting) of
	  Referred-by tokens
    </td>
</tr>

856
<a name="3903"></a>
Pekka Pessi's avatar
Pekka Pessi committed
857 858
<tr valign=top>
    <th align="left">
859
	@RFC3903: PUBLISH
Pekka Pessi's avatar
Pekka Pessi committed
860 861
    </th>
    <td>
862 863 864
	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
865

866 867
	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
868 869
    </td>
    <td>
870 871
        Application must take care of:
        - Including correct @ref sip_event "Event" in the request
872
        - Permanently storing @SIPETag
Pekka Pessi's avatar
Pekka Pessi committed
873 874
    </td>
</tr>
Pekka Pessi's avatar
Pekka Pessi committed
875

876
<a name="4028"></a>
Pekka Pessi's avatar
Pekka Pessi committed
877 878
<tr valign=top>
    <th align="left">
879
	@RFC4028: Session Timers
Pekka Pessi's avatar
Pekka Pessi committed
880 881
    </th>
    <td>
882 883 884 885 886
	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
887 888 889 890 891
	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.
892 893

        The SIP headers explicitly supported (generating, parsing and
894
	syntax checking) are @ref sip_session_expires "Session-Expires" ("x") and
895
	@ref sip_min_se "Min-SE".
Pekka Pessi's avatar
Pekka Pessi committed
896 897
    </td>
    <td>
Pekka Pessi's avatar
Pekka Pessi committed
898
	&nbsp;
Pekka Pessi's avatar
Pekka Pessi committed
899 900
    </td>
</tr>
901

902 903 904 905 906 907 908 909 910 911 912 913 914 915 916 917 918 919 920 921
<a name="4168"></a>
<tr valign=top>
    <th align="left">
	@RFC4168: SCTP as Transport for SIP
    </th>
    <td>
	The transport=sctp URI parameter is supported. The SCTP transport
	protocol is supported as experimental. It is enabled with
	configure script argument --enable-sctp.

	The framing of SIP messages over SCTP is not specified clearly in
	@RFC4168. It is possible to send SIP messages smaller than 64K over
	SCTP.
    </td>
    <td>
	&nbsp;
    </td>
</tr>


922
<a name="4320"></a>
923 924 925 926 927 928 929 930 931 932 933 934 935 936 937 938 939 940 941 942 943
<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>

944 945 946 947 948 949 950 951 952 953 954 955 956 957 958 959 960 961 962 963 964 965
<a name="4488"></a>
<tr valign=top>
    <th align="left">
	@RFC4488: Suppression of REFER Implicit Subscription
    </th>
    <td>
	Sofia-SIP supports @ref sip_refer_sub "Refer-Sub" header
	(generating, parsing and syntax checking).

        The implicit subscription is suppressed by @nua, if the @ReferSub:
        true header is included in the REFER 
	request (@ref nua_refer "on server side") or
	response (@ref nua_i_refer "on client side").

	@NEW_1_12_5
    </td>
    <td>
        The REFER client application must include SIPTAG_REFER_SUB_STR("true")
	in the nua_refer() tags.
    </td>
</tr>

966 967 968 969 970 971 972 973
</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
974

975 976 977
<a name="4566"></a>
<a name="2327"></a>
<a name="3266"></a>
Pekka Pessi's avatar
Pekka Pessi committed
978
<tr valign=top>
979
    <th align="left" align="left">
980
	@RFC4566: SDP: Session Description Protocol
Pekka Pessi's avatar
Pekka Pessi committed
981 982
    </th>
    <td>
983 984 985 986 987 988 989 990 991 992 993 994 995 996 997 998 999 1000
	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.

1001
	The implementation partially implements @RFC4566. Note that
1002
	definition of 'token' was updated in @RFC4566 and the parser has not
1003
	been updated yet.
Pekka Pessi's avatar
Pekka Pessi committed
1004 1005
    </td>
    <td>
1006 1007 1008
      @RFC4566 obsoletes
      - @RFC2327: SDP (Session Description Protocol)
      - @RFC3266: IP6 in SDP
Pekka Pessi's avatar
Pekka Pessi committed
1009 1010 1011
    </td>
</tr>

1012
<a name="3264"></a>
Pekka Pessi's avatar
Pekka Pessi committed
1013 1014
<tr valign=top>
    <th align="left">
1015
	@RFC3264: SDP Offer/Answer Negotiation
Pekka Pessi's avatar
Pekka Pessi committed
1016 1017
    </th>
    <td>
1018
	Generating and processing offers or answers.
Pekka Pessi's avatar
Pekka Pessi committed
1019 1020
    </td>
    <td>
1021 1022
	- "a=fmtp" parameters are not taken into account
          when generating or processing answer
Pekka Pessi's avatar
Pekka Pessi committed
1023 1024 1025
    </td>
</tr>

1026
<a name="3312"></a>
Pekka Pessi's avatar
Pekka Pessi committed
1027 1028
<tr valign=top>
    <th align="left">
1029
	@RFC3312: Preconditions
Pekka Pessi's avatar
Pekka Pessi committed
1030 1031
    </th>
    <td>
1032 1033 1034 1035 1036 1037
	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",
1038
        @ref sip_supported "Supported" ("k"),
1039 1040
        and
        @ref sip_unsupported "Unsupported" header.
Pekka Pessi's avatar
Pekka Pessi committed
1041 1042
    </td>
    <td>
1043 1044 1045
	Application must take care of:
	- Semantics and handling of preconditions
	- Reservation of resources
Pekka Pessi's avatar
Pekka Pessi committed
1046 1047 1048
    </td>
</tr>

1049
<a name="3388"></a>
Pekka Pessi's avatar
Pekka Pessi committed
1050 1051
<tr valign=top>
    <th align="left">
1052
	@RFC3388: Grouping of Media Lines
Pekka Pessi's avatar
Pekka Pessi committed
1053 1054
    </th>
    <td>
1055 1056 1057 1058
	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
1059 1060 1061
	used within attribute line
    </td>
    <td>
1062
        Application must take care of:
Pekka Pessi's avatar
Pekka Pessi committed
1063 1064 1065 1066 1067 1068
	- Generating or processing the attribute lines
	- Grouping the media for transport accordingly
    </td>
</tr>


1069
<a name="3407"></a>
Pekka Pessi's avatar
Pekka Pessi committed
1070 1071
<tr valign=top>
    <th align="left">
1072
	@RFC3407: Capability Declaration
Pekka Pessi's avatar
Pekka Pessi committed
1073 1074
    </th>
    <td>
1075 1076
	Sofia-SIP provides <a href="#2616">generic support</a> for attribute
	lines that conform to SDP syntax.
Pekka Pessi's avatar
Pekka Pessi committed
1077 1078
    </td>
    <td>
1079 1080 1081 1082
        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
1083 1084 1085 1086
    </td>
</tr>


1087
<a name="3524"></a>
Pekka Pessi's avatar
Pekka Pessi committed
1088 1089
<tr valign=top>
    <th align="left">
1090
	@RFC3524: SRF
Pekka Pessi's avatar
Pekka Pessi committed
1091 1092
    </th>
    <td>
1093 1094
	Sofia-SIP provides <a href="#2616">generic support</a> for attribute
	lines that conform to SDP syntax.
Pekka Pessi's avatar
Pekka Pessi committed
1095 1096
    </td>
    <td>
1097 1098 1099
        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
1100 1101 1102
    </td>
</tr>

1103 1104 1105 1106 1107 1108 1109 1110 1111 1112 1113 1114 1115 1116 1117 1118 1119

<a name="3551"></a>
<tr valign=top>
    <th align="left">
	@RFC3551: RTP/AVP
    </th>
    <td>
	Sofia-SIP recognizes the RTP payload types for well-known audio and
	video codecs defined in @RFC3551.
    </td>
    <td>
        Application must take care of:
	- Audio or video processing
        - Generating a=rtpmap or a=fmtp lines when needed 
    </td>
</tr>

1120
<a name="3556"></a>
Pekka Pessi's avatar
Pekka Pessi committed
1121 1122
<tr valign=top>
    <th align="left">
1123
	@RFC3556: Bandwidth
Pekka Pessi's avatar
Pekka Pessi committed
1124 1125
    </th>
    <td>
1126 1127
	Sofia-SIP provides <a href="#2616">generic support</a> for attribute
	lines that conform to SDP syntax.
Pekka Pessi's avatar
Pekka Pessi committed
1128 1129
    </td>
    <td>
1130 1131 1132
        Application must take care of:
	- Generating or processing RS and RR bandwidth modifiers
	- Semantics of bandwidth allocation
Pekka Pessi's avatar
Pekka Pessi committed
1133 1134 1135
    </td>
</tr>

1136
<a name="3605"></a>
Pekka Pessi's avatar
Pekka Pessi committed
1137 1138
<tr valign=top>
    <th align="left">
1139
	@RFC3605: RTCP attribute
Pekka Pessi's avatar
Pekka Pessi committed
1140 1141
    </th>
    <td>
1142 1143
	Sofia-SIP provides <a href="#2616">generic support</a> for attribute
	lines that conform to SDP syntax.
Pekka Pessi's avatar
Pekka Pessi committed
1144 1145
    </td>
    <td>
1146 1147 1148
        Application must take care of:
	- Discovering port numbers
	- Generating or processing the RTCP attribute lines
Pekka Pessi's avatar
Pekka Pessi committed
1149 1150 1151
    </td>
</tr>

1152
<a name="3890"></a>
Pekka Pessi's avatar
Pekka Pessi committed
1153 1154
<tr valign=top>
    <th align="left">
1155
	@RFC3890: TIAS
Pekka Pessi's avatar
Pekka Pessi committed
1156 1157
    </th>
    <td>
1158 1159
	Sofia-SIP provides <a href="#2616">generic support</a> for attribute
	lines that conform to SDP syntax.
Pekka Pessi's avatar
Pekka Pessi committed
1160 1161
    </td>
    <td>
1162 1163 1164
        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
1165 1166 1167
    </td>
</tr>

1168 1169 1170 1171 1172 1173 1174 1175
</table>


*/

/* Overflow:

<a name="4566"></a>
1176 1177 1178 1179 1180 1181 1182 1183 1184 1185 1186 1187
<tr valign=top>
    <th align="left">
	@RFC4566: SDP: Session Description Protocol
    </th>
    <td>
    Obsoletes RFC2327 and RFC3266.
    </td>
    <td>
	&nbsp;
    </td>
</tr>

1188

1189
<a name="3320"></a>
Pekka Pessi's avatar
Pekka Pessi committed
1190 1191
<tr valign=top>
    <th align="left">
1192
	@RFC3320: SigComp
Pekka Pessi's avatar
Pekka Pessi committed
1193 1194
    </th>
    <td>
1195 1196 1197
    	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
1198

1199
	Decompression using UDVM
Pekka Pessi's avatar
Pekka Pessi committed
1200 1201
    </td>
    <td>
Pekka Pessi's avatar
Pekka Pessi committed
1202
	&nbsp;
Pekka Pessi's avatar
Pekka Pessi committed
1203 1204 1205
    </td>
</tr>

1206
<a name="3321"></a>
Pekka Pessi's avatar
Pekka Pessi committed
1207 1208
<tr valign=top>
    <th align="left">
1209
	@RFC3321: SigComp Extended operations
Pekka Pessi's avatar
Pekka Pessi committed
1210 1211
    </th>
    <td>
1212
	Support for SigComp extended operations.
Pekka Pessi's avatar
Pekka Pessi committed
1213 1214
    </td>
    <td>
1215 1216 1217 1218
	- Explicit Acknowledgment Scheme
	- Shared Compression
	- Checkpoint State
	- Implicit Deletion for Dictionary Update
Pekka Pessi's avatar
Pekka Pessi committed
1219 1220
    </td>
</tr>
Pekka Pessi's avatar
Pekka Pessi committed
1221

1222
<a name="3325"></a>
Pekka Pessi's avatar
Pekka Pessi committed
1223 1224
<tr valign=top>
    <th align="left">
1225
	@RFC3325: Asserted Identity
Pekka Pessi's avatar
Pekka Pessi committed
1226 1227
    </th>
    <td>
1228 1229
	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
1230 1231
    </td>
    <td>
1232 1233
	- Recognizing trust domains and enforcing handling of headers
	  based on those
Pekka Pessi's avatar
Pekka Pessi committed
1234 1235 1236
    </td>
</tr>

1237
<a name="3485"></a>
Pekka Pessi's avatar
Pekka Pessi committed
1238 1239
<tr valign=top>
    <th align="left">
1240
	@RFC3485: SIP/SDP Dictionary
Pekka Pessi's avatar
Pekka Pessi committed
1241 1242
    </th>
    <td>
1243 1244
	Support for SigComp static compression using SIP/SDP
	dictionary.
Pekka Pessi's avatar
Pekka Pessi committed
1245 1246
    </td>
    <td>
1247
	&nbsp;
Pekka Pessi's avatar
Pekka Pessi committed
1248 1249 1250
    </td>
</tr>

1251 1252 1253 1254 1255



	- Implicitly registered user identities

1256
<a name="3959"></a>
Pekka Pessi's avatar
Pekka Pessi committed
1257 1258 1259 1260 1261 1262 1263 1264 1265 1266 1267 1268 1269 1270 1271
<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>

*/