A.2.1.4 PDU parameters

24.2293GPPIP multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP)Release 18Stage 3TS

A.2.1.4.1 Status-codes

Table A.6: Supported status-codes

Item

Header

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

1

100 (Trying)

[26] 21.1.1

c21

c21

[26] 21.1.1

c11

c11

101

1xx response

[26] 21.1

p21

p21

[26] 21.1

p21

p21

101A

18x response

[26] 21.1

p21

p21

[26] 21.1

p21

p21

2

180 (Ringing)

[26] 21.1.2

c2

c2

[26] 21.1.2

c1

c1

3

181 (Call Is Being Forwarded)

[26] 21.1.3

c2

c2

[26] 21.1.3

c1

c1

4

182 (Queued)

[26] 21.1.4

c2

c2

[26] 21.1.4

c1

c1

5

183 (Session Progress)

[26] 21.1.5

c34

c34

[26] 21.1.5

c1

c1

5A

199 (Early Dialog Terminated)

[142] 11.1

c32

c32

[142] 11.1

c32

c32

102

2xx response

[26] 21.2

p22

p22

[26] 21.1

p22

p22

6

200 (OK)

[26] 21.2.1

m

m

[26] 21.2.1

m

m

7

202 (Accepted)

[28] 8.3.1

c36

c36

[28] 8.3.1

c37

c37

103

3xx response

[26] 21.3

p23

p23

[26] 21.1

p23

p23

8

300 (Multiple Choices)

[26] 21.3.1

m

m

[26] 21.3.1

m

m

9

301 (Moved Permanently)

[26] 21.3.2

m

m

[26] 21.3.2

m

m

10

302 (Moved Temporarily)

[26] 21.3.3

m

m

[26] 21.3.3

m

m

11

305 (Use Proxy)

[26] 21.3.4

m

m

[26] 21.3.4

m

m

12

380 (Alternative Service)

[26] 21.3.5

m

m

[26] 21.3.5

m

m

104

4xx response

[26] 21.4

p24

p24

[26] 21.4

p24

p24

13

400 (Bad Request)

[26] 21.4.1

m

m

[26] 21.4.1

m

m

14

401 (Unauthorized)

[26] 21.4.2

o

c12

[26] 21.4.2

m

m

15

402 (Payment Required)

[26] 21.4.3

n/a

n/a

[26] 21.4.3

n/a

n/a

16

403 (Forbidden)

[26] 21.4.4

m

m

[26] 21.4.4

m

m

17

404 (Not Found)

[26] 21.4.5

m

m

[26] 21.4.5

m

m

18

405 (Method Not Allowed)

[26] 21.4.6

m

m

[26] 21.4.6

m

m

19

406 (Not Acceptable)

[26] 21.4.7

m

m

[26] 21.4.7

m

m

20

407 (Proxy Authentication Required)

[26] 21.4.8

o

o

[26] 21.4.8

m

m

21

408 (Request Timeout)

[26] 21.4.9

c2

c2

[26] 21.4.9

m

m

22

410 (Gone)

[26] 21.4.10

m

m

[26] 21.4.10

m

m

22A

412 (Conditional Request Failed)

[70] 11.2.1

c20

c20

[70] 11.2.1

c20

c20

23

413 (Request Entity Too Large)

[26] 21.4.11

m

m

[26] 21.4.11

m

m

24

414 (Request-URI Too Large)

[26] 21.4.12

m

m

[26] 21.4.12

m

m

25

415 (Unsupported Media Type)

[26] 21.4.13

m

m

[26] 21.4.13

m

m

26

416 (Unsupported URI Scheme)

[26] 21.4.14

m

m

[26] 21.4.14

m

m

26A

417 (Unknown Resource Priority)

[116] 4.6.2

c24

c24

[116] 4.6.2

c24

c24

27

420 (Bad Extension)

[26] 21.4.15

m

c13

[26] 21.4.15

m

m

28

421 (Extension Required)

[26] 21.4.16

o

o

[26] 21.4.16

i

i

28A

422 (Session Interval Too Small)

[58] 6

c7

c7

[58] 6

c7

c7

29

423 (Interval Too Brief)

[26] 21.4.17

c4

c4

[26] 21.4.17

m

m

29A

424 (Bad Location Information)

[89] 4.2

c23

c23

[89] 4.2

c23

c23

29AA

428 Use Identity Header

[252] 6.2.2

c40

c40

[252] 6.2.2

c40

c40

29B

429 (Provide Referrer Identity)

[59] 5

c8

c8

[59] 5

c9

c9

29C

430 (Flow Failed)

[92] 11

n/a

n/a

[92] 11

c22

c22

29D

433 (Anonymity Disallowed)

[67] 4

c14

c14

[67] 4

c14

c14

29DA

436 Bad Identity Info

[252] 6.2.2

c40

c40

[252] 6.2.2

c40

c40

29DB

437 Unsupported Credential

[252] 6.2.2

c40

c40

[252] 6.2.2

c40

c40

29DC

438 Invalid Identity Header

[252] 6.2.2

c40

c40

[252] 6.2.2

c40

c40

29E

439 (First Hop Lacks Outbound Support)

[92] 11

c28

c28

[92] 11

c29

c29

29F

440 (Max Breadth Exceeded)

[117] 5

n/a

c30

[117] 5

c31

c31

29G

469 (Bad INFO Package)

[25] 4.2

c33

c33

[25] 4.2

c33

c33

29H

470 (Consent Needed)

[125] 5.9.2

c26

c26

[125] 5.9.2

c27

c27

30

480 (Temporarily Unavailable)

[26] 21.4.18

m

m

[26] 21.4.18

m

m

31

481 (Call/Transaction Does Not Exist)

[26] 21.4.19

m

m

[26] 21.4.19

m

m

32

482 (Loop Detected)

[26] 21.4.20

m

m

[26] 21.4.20

m

m

33

483 (Too Many Hops)

[26] 21.4.21

m

m

[26] 21.4.21

m

m

34

484 (Address Incomplete)

[26] 21.4.22

o

o

[26] 21.4.22

m

m

35

485 (Ambiguous)

[26] 21.4.23

o

o

[26] 21.4.23

m

m

36

486 (Busy Here)

[26] 21.4.24

m

m

[26] 21.4.24

m

m

37

487 (Request Terminated)

[26] 21.4.25

m

m

[26] 21.4.25

m

m

38

488 (Not Acceptable Here)

[26] 21.4.26

m

m

[26] 21.4.26

m

m

39

489 (Bad Event)

[28] 8.3.2

c3

c3

[28] 8.3.2

c3

c3

40

491 (Request Pending)

[26] 21.4.27

m

m

[26] 21.4.27

m

m

41

493 (Undecipherable)

[26] 21.4.28

m

m

[26] 21.4.28

m

m

41A

494 (Security Agreement Required)

[48] 2

c5

c5

[48] 2

c6

c6

105

5xx response

[26] 21.5

p25

p25

[26] 21.5

p25

p25

42

500 (Internal Server Error)

[26] 21.5.1

m

m

[26] 21.5.1

m

m

43

501 (Not Implemented)

[26] 21.5.2

m

m

[26] 21.5.2

m

m

44

502 (Bad Gateway)

[26] 21.5.3

o

o

[26] 21.5.3

m

m

45

503 (Service Unavailable)

[26] 21.5.4

m

m

[26] 21.5.4

m

m

46

504 (Server Time-out)

[26] 21.5.5

m

m

[26] 21.5.5

m

m

47

505 (Version not supported)

[26] 21.5.6

m

m

[26] 21.5.6

m

m

48

513 (Message Too Large)

[26] 21.5.7

m

m

[26] 21.5.7

m

m

49

580 (Precondition Failure)

[30] 8

c35

c35

[30] 8

c35

c35

106

6xx response

[26] 21.6

p26

p26

[26] 21.6

p26

p26

50

600 (Busy Everywhere)

[26] 21.6.1

m

m

[26] 21.6.1

m

m

51

603 (Decline)

[26] 21.6.2

c10

c10

[26] 21.6.2

m

m

52

604 (Does Not Exist Anywhere)

[26] 21.6.3

m

m

[26] 21.6.3

m

m

53

606 (Not Acceptable)

[26] 21.6.4

m

m

[26] 21.6.4

m

m

54

607 (Unwanted)

[254]

o

c38

[254]

o

c39

c1: IF A.5/9 THEN m ELSE n/a – – INVITE response.

c2: IF A.5/9 THEN o ELSE n/a – – INVITE response.

c3: IF A.4/20 THEN m ELSE n/a – – SIP specific event notification extension.

c4: IF A.5/19 OR A.5/21 THEN m ELSE n/a – – REGISTER response or SUBSCRIBE response.

c5: IF A.4/37 THEN m ELSE n/a – – security mechanism agreement for the session initiation protocol.

c6: IF A.4/37 THEN m ELSE n/a – – security mechanism agreement for the session initiation protocol.

c7: IF A.4/42 AND (A.5/9 OR A.5/23) THEN m ELSE n/a – – the SIP session timer AND (INVITE response OR UPDATE response).

c8: IF A.4/43 AND A.5/17 THEN o ELSE n/a – – the SIP Referred-By mechanism and REFER response.

c9: IF A.4/43 AND A.5/17 THEN m ELSE n/a – – the SIP Referred-By mechanism and REFER response.

c10: IF A.4/44 THEN m ELSE o – – the Session Inititation Protocol (SIP) "Replaces" header.

c11: IF A.5/3 OR A.5/9 OR A.5/9B OR A.5/11OR A.5/13 OR A.5/15 OR A.5/15B OR A.5/17 OR A.5/19 OR A.5/21 OR A.5/23 THEN m ELSE n/a – – BYE response or INVITE response or MESSAGE response or NOTIFY response or OPTIONS response or PRACK response or PUBLISH response or REFER response or REGISTER response or SUBSCRIBE response or UPDATE response.

c12: IF A.3/4 THEN m ELSE o – – S-CSCF.

c13: IF A.3/1 OR A.3/2 OR A.3/4 THEN m ELSE o – – UE, P-CSCF, S-CSCF.

c14: IF A.4/48 THEN m ELSE n/a – – rejecting anonymous requests in the session initiation protocol.

c20: IF A.4/41 THEN m ELSE n/a – – an event state publication extension to the session initiation protocol.

c21: IF A.5/3 OR A.5/9 OR A.5/9B OR A.5/11 or A.5/13 OR A.5/15 OR A.5/15B OR A.5/17 OR A.5/19 OR A.5/21 OR A.5/23 THEN o ELSE n/a – – BYE response or INVITE response or MESSAGE response or NOTIFY response or OPTIONS response or PRACK response or PUBLISH response or REFER response or REGISTER response or SUBSCRIBE response or UPDATE response.

c22: IF A.4/57 THEN m ELSE n/a – – managing client initiated connections in SIP.

c23: IF A.4/60 THEN m ELSE n/a – – SIP location conveyance.

c24: IF A.4/70 THEN m ELSE n/a – – communications resource priority for the session initiation protocol.

c26: IF A.4/75B THEN m ELSE n/a – – a recipient within the framework for consent-based communications in SIP.

c27: IF A.4/75A THEN m ELSE n/a – – a relay within the framework for consent-based communications in SIP.

c28: IF A.4/2 AND A.4/57 THEN m ELSE n/a – – registrar, managing client initiated connections in SIP.

c29: IF A.4/1 AND A.4/57 THEN m ELSE n/a – – client behaviour for registration, managing client initiated connections in SIP.

c30: IF A.4/71 AND (A.3/9B OR A.3/9C OR A.3/13B OR A.3/13C) THEN m ELSE n/a – – addressing an amplification vulnerability in session initiation protocol forking proxies, IBCF (IMS-ALG), IBCF (Screening of SIP signalling), ISC gateway function (IMS-ALG), ISC gateway function (Screening of SIP signalling).

c31: IF A.4/71 THEN m ELSE n/a – – addressing an amplification vulnerability in session initiation protocol forking proxies.

c32: IF A.5/9 AND A.4/81 THEN m ELSE n/a – – INVITE response and 199 (Early Dialog Terminated) response.

c33: IF A.4/13 THEN m ELSE n/a – – SIP INFO method and package framework.

c34: IF A.4/16 OR A.3/6 THEN m ELSE IF A.5/9 THEN o ELSE n/a – – initiating a session which require local and/or remote resource reservation, MGCF, INVITE response.

c35: IF A.4/16 THEN m ELSE n/a – – integration of resource management and SIP.

c36: IF A.5/9B THEN m ELSE n/a – – MESSAGE response.

c37: IF A.4/20 OR OR A.5/9B OR A.5/17 THEN m ELSE n/a – – SIP specific event notification extension or MESSAGE response or the REFER response.

c.38: IF A.4/117 THEN o ELSE n/a – – a SIP response code for unwanted calls extension.

c.39: IF A.4/117 THEN m ELSE n/a – – a SIP response code for unwanted calls extension.

c.40 IF A.4/116 THEN m ELSE n/a – authenticated identity management in the Session Initiation Protocol

p21: A.6/2 OR A.6/3 OR A.6/4 OR A.6/5 OR A.6/5A – – 1xx response.

p22: A.6/6 OR A.6/7 – – 2xx response.

p23: A.6/8 OR A.6/9 OR A.6/10 OR A.6/11 OR A.6/12 – – 3xx response.

p24: A.6/13 OR A.6/14 OR A.6/15 OR A.6/16 OR A.6/17 OR A.6/18 OR A.6/19 OR A.6/20 OR A.6/21 OR A.6/22 OR A.6/22A OR A.6/23 OR A.6/24 OR A.6/25 OR A.6/26 OR A.6/26A OR A.6/27 OR A.6/28 OR A.6/28A OR A.6/29 OR A.6/29A OR A.6/29B OR A.6/29C OR A.6/29D OR A.6/29E OR A.6/29F OR A.6/29G OR A.6/29H OR A.6/30 OR A.6/31 OR A.6/32 OR A.6/33 OR A.6/34 OR A.6/35 OR A.6/36 OR A.6/436 OR A.6/38 OR A.6/39 OR A.6/40 OR A.6/41 OR A.6/41A. – 4xx response.

p25: A.6/42 OR A.6/43 OR A.6/44 OR A.6/45 OR A.6/46 OR A.6/47 OR A.6/48 OR A.6/49 – – 5xx response

p26: A.6/50 OR A.6/51 OR A.6/52 OR A.6/53 – – 6xx response.

A.2.1.4.2 ACK method

Prerequisite A.5/1 – ACK request

Table A.7: Supported header fields within the ACK request

Item

Header field

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

1

Accept-Contact

[56B] 9.2

c9

c9

[56B] 9.2

c10

c10

2

Allow-Events

[28] 8.2.2

c1

c1

[28] 8.2.2

c2

c2

3

Authorization

[26] 20.7

c3

c3

[26] 20.7

c3

c3

4

Call-ID

[26] 20.8

m

m

[26] 20.8

m

m

5

Cellular-Network-Info

7.2.15

n/a

c26

7.2.15

n/a

c27

6

Content-Disposition

[26] 20.11

o

o

[26] 20.11

m

m

7

Content-Encoding

[26] 20.12

o

o

[26] 20.12

m

m

7A

Content-ID

[256] 3.2

o

c29

[256] 3.2

m

c30

8

Content-Language

[26] 20.13

o

o

[26] 20.13

m

m

9

Content-Length

[26] 20.14

m

m

[26] 20.14

m

m

10

Content-Type

[26] 20.15

m

m

[26] 20.15

m

m

11

CSeq

[26] 20.16

m

m

[26] 20.16

m

m

12

Date

[26] 20.17

c4

c4

[26] 20.17

m

m

13

From

[26] 20.20

m

m

[26] 20.20

m

m

13A

Max-Breadth

[117] 5.8

n/a

c14

[117] 5.8

c15

c15

14

Max-Forwards

[26] 20.22

m

m

[26] 20.22

n/a

c16

15

MIME-Version

[26] 20.24

o

o

[26] 20.24

m

m

15A

P-Access-Network-Info

[52] 4.4, [52A] 4, [234] 2

c19

c20

[52] 4.4, [52A] 4, [234] 2

c19

c21

15C

Privacy

[33] 4.2

c6

n/a

[33] 4.2

c6

n/a

15D

P-Charging-Vector

[52] 4.6, [52A] 4

c22

c23

[52] 4.6, [52A] 4

c22

c23

15E

Priority-Share

Subclause 7.2.16

n/a

c28

Subclause 7.2.16

n/a

c28

16

Proxy-Authorization

[26] 20.28

c5

c5

[26] 20.28

n/a

n/a

17

Proxy-Require

[26] 20.29

o

n/a

[26] 20.29

n/a

n/a

17A

Reason

[34A] 2

c8

c8

[34A] 2

c8

c8

17B

Record-Route

[26] 20.30

n/a

c16

[26] 20.30

n/a

c16

17C

Recv-Info

[25] 5.2.3

c17

c17

[25] 5.2.3

c17

c17

17D

Reject-Contact

[56B] 9.2

c9

c9

[56B] 9.2

c10

c10

17E

Relayed-Charge

7.2.12

n/a

c24

7.2.12

n/a

c24

17F

Request-Disposition

[56B] 9.1

c9

c9

[56B] 9.1

c10

c10

18

Require

[26] 20.32

n/a

n/a

[26] 20.32

n/a

n/a

18A

Resource-Priority

[116] 3.1

c11

c11

[116] 3.1

c11

c11

18B

Resource-Share

Subclause 7.2.13

n/a

c25

Subclause 7.2.13

n/a

c25

19

Route

[26] 20.34

m

m

[26] 20.34

n/a

c16

19A

Session-ID

[162]

o

c18

[162]

o

c18

20

Timestamp

[26] 20.38

c7

c7

[26] 20.38

m

m

21

To

[26] 20.39

m

m

[26] 20.39

m

m

22

User-Agent

[26] 20.41

o

o

[26] 20.41

m

m

23

Via

[26] 20.42

m

m

[26] 20.42

m

m

c1: IF A.4/22 THEN o ELSE n/a – – acting as the notifier of event information.

c2: IF A.4/23 THEN m ELSE n/a – – acting as the subscriber to event information.

c3: IF A.4/7 THEN m ELSE n/a – – authentication between UA and UA.

c4: IF A.4/11 THEN o ELSE n/a – – insertion of date in requests and responses.

c5: IF A.4/8A THEN m ELSE n/a – – authentication between UA and proxy.

c6: IF A.4/26 THEN o ELSE n/a – – a privacy mechanism for the Session Initiation Protocol (SIP).

c7: IF A.4/6 THEN o ELSE n/a – – timestamping of requests.

c8: IF A.4/38 THEN o ELSE n/a – – the Reason header field for the session initiation protocol.

c9: IF A.4/40 THEN o ELSE n/a – – caller preferences for the session initiation protocol.

c10: IF A.4/40 THEN m ELSE n/a – – caller preferences for the session initiation protocol.

c11: IF A.4/70 THEN m ELSE n/a – – communications resource priority for the session initiation protocol.

c14: IF A.4/71 AND (A.3/9B OR A.3/9C OR A.3/13B OR A.3/13C) THEN m ELSE n/a – – addressing an amplification vulnerability in session initiation protocol forking proxies, IBCF (IMS-ALG), IBCF (Screening of SIP signalling), ISC gateway function (IMS-ALG), ISC gateway function (Screening of SIP signalling).

c15: IF A.4/71 THEN m ELSE n/a – – addressing an amplification vulnerability in session initiation protocol forking proxies.

c16: IF A.3/1 AND NOT A.3C/1 THEN n/a ELSE o – – UE, UE performing the functions of an external attached network.

c17: IF A.4/13 THEN m ELSE IF A.4/13A THEN m ELSE n/a – – SIP INFO method and package framework, legacy INFO usage.

c18: IF A.4/91 THEN m ELSE n/a – – the Session-ID header.

c19: IF A.4/34 THEN o ELSE n/a – – the P-Access-Network-Info header extension.

c20: IF A.4/34 AND A.3/1 OR A.3/2A OR A.3/7 OR A.3A/81 OR A.3A/81A OR A.3A/81B THEN o ELSE n/a – – the P-Access-Network-Info header extension and UE, P-CSCF (IMS-ALG), AS, MSC Server enhanced for ICS, MSC server enhanced for SRVCC using SIP interface, MSC server enhanced for DRVCC using SIP interface.

c21: IF A.4/34 AND A.3/1 OR A.3/7 THEN m ELSE n/a – – the P-Access-Network-Info header extension and UE, AS.

c22: IF A.4/36 THEN o ELSE n/a – – the P-Charging-Vector header extension.

c23: IF A.4/36 THEN m ELSE n/a – – the P-Charging-Vector header extension.

c24: IF A.4/111 THEN m ELSE n/a – – the Relayed-Charge header field extension.

c25: IF A.4/112 THEN o ELSE n/a – – resource sharing.

c26: IF A.4/113 AND A.3/1 OR A.3/2A OR A.3/7 THEN o ELSE n/a – – the Cellular-Network-Info header extension and UE, P-CSCF (IMS-ALG), AS.

c27: IF A.4/113 AND A.3/7 THEN m ELSE n/a – – the Cellular-Network-Info header extension and AS.

c28: IF A.4/114 THEN o ELSE n/a – – priority sharing.

c29: IF A.4/119 THEN o ELSE n/a – – Content-ID header field in Session Initiation Protocol (SIP).

c30: IF A.4/119 THEN m ELSE n/a – – Content-ID header field in Session Initiation Protocol (SIP).

Prerequisite A.5/1 – ACK request

Table A.8: Supported message bodies within the ACK request

Item

Header

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

1

A.2.1.4.3 BYE method

Prerequisite A.5/2 – – BYE request

Table A.9: Supported header fields within the BYE request

Item

Header field

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

1

Accept

[26] 20.1

o

o

[26] 20.1

m

m

1A

Accept-Contact

[56B] 9.2

c18

c18

[56B] 9.2

c22

c22

2

Accept-Encoding

[26] 20.2

o

o

[26] 20.2

m

m

3

Accept-Language

[26] 20.3

o

o

[26] 20.3

m

m

3A

Allow

[26] 20.5

o

o

[26] 20.5

m

m

4

Allow-Events

[28] 8.2.2

c1

c1

[28] 8.2.2

c2

c2

5

Authorization

[26] 20.7

c3

c3

[26] 20.7

c3

c3

6

Call-ID

[26] 20.8

m

m

[26] 20.8

m

m

6A

Cellular-Network-Info

7.2.15

n/a

c35

7.2.15

n/a

c36

7

Content-Disposition

[26] 20.11

o

o

[26] 20.11

m

m

8

Content-Encoding

[26] 20.12

o

o

[26] 20.12

m

m

8A

Content-ID

[256] 3.2

o

c37

[256] 3.2

m

c38

9

Content-Language

[26] 20.13

o

o

[26] 20.13

m

m

10

Content-Length

[26] 20.14

m

m

[26] 20.14

m

m

11

Content-Type

[26] 20.15

m

m

[26] 20.15

m

m

12

CSeq

[26] 20.16

m

m

[26] 20.16

m

m

13

Date

[26] 20.17

c4

c4

[26] 20.17

m

m

14

From

[26] 20.20

m

m

[26] 20.20

m

m

14A

Geolocation

[89] 4.1

c23

c23

[89] 4.1

c23

c23

14B

Geolocation-Routing

[89] 4.2

c23

c23

[89] 4.2

c23

c23

14C

Max-Breadth

[117] 5.8

n/a

c29

[117] 5.8

c30

c30

15

Max-Forwards

[26] 20.22

m

m

[26] 20.22

n/a

c31

16

MIME-Version

[26] 20.24

o

o

[26] 20.24

m

m

16A

P-Access-Network-Info

[52] 4.4, [234] 2

c9

c10

[52] 4.4, [234] 2

c9

c11

16B

P-Asserted-Identity

[34] 9.1

n/a

n/a

[34] 9.1

c6

c6

16C

P-Charging-Function-Addresses

[52] 4.5

c13

c14

[52] 4.5

c13

c14

16D

P-Charging-Vector

[52] 4.6

c12

c34

[52] 4.6

c12

c34

16F

P-Preferred-Identity

[34] 9.2

c6

x

[34] 9.2

n/a

n/a

16G

Privacy

[33] 4.2

c7

n/a

[33] 4.2

c7

c7

17

Proxy-Authorization

[26] 20.28

c5

c5

[26] 20.28

n/a

n/a

18

Proxy-Require

[26] 20.29

o

n/a

[26] 20.29

n/a

n/a

18A

Reason

[34A] 2

c17

c21

[34A] 2

c24

c24

19

Record-Route

[26] 20.30

n/a

c31

[26] 20.30

n/a

c31

19A

Referred-By

[59] 3

c19

c19

[59] 3

c20

c20

19B

Reject-Contact

[56B] 9.2

c18

c18

[56B] 9.2

c22

c22

19C

Relayed-Charge

7.2.12

n/a

c33

7.2.12

n/a

c33

19D

Request-Disposition

[56B] 9.1

c18

c18

[56B] 9.1

c22

c22

20

Require

[26] 20.32

m

m

[26] 20.32

m

m

20A

Resource-Priority

[116] 3.1

c25

c25

[116] 3.1

c25

c25

21

Route

[26] 20.34

m

m

[26] 20.34

n/a

c31

21A

Security-Client

[48] 2.3.1

c15

c15

[48] 2.3.1

n/a

n/a

21B

Security-Verify

[48] 2.3.1

c16

c16

[48] 2.3.1

n/a

n/a

21C

Session-ID

[162]

o

c32

[162]

o

c32

22

Supported

[26] 20.37

o

o

[26] 20.37

m

m

23

Timestamp

[26] 20.38

c8

c8

[26] 20.38

m

m

24

To

[26] 20.39

m

m

[26] 20.39

m

m

25

User-Agent

[26] 20.41

o

o

[26] 20.41

o

o

25A

User-to-User

[126] 7

c26

c26

[126] 7

c26

c26

26

Via

[26] 20.42

m

m

[20] 20.42

m

m

c1: IF A.4/22 THEN o ELSE n/a – – acting as the notifier of event information.

c2: IF A.4/23 THEN m ELSE n/a – – acting as the subscriber to event information.

c3: IF A.4/7 THEN m ELSE n/a – – authentication between UA and UA.

c4: IF A.4/11 THEN o ELSE n/a – – insertion of date in requests and responses.

c5: IF A.4/8A THEN m ELSE n/a – – authentication between UA and proxy.

c6: IF A.4/25 THEN o ELSE n/a – – private extensions to the Session Initiation Protocol (SIP) for asserted identity within trusted networks.

c7: IF A.4/26 THEN o ELSE n/a – – a privacy mechanism for the Session Initiation Protocol (SIP).

c8: IF A.4/6 THEN o ELSE n/a – – timestamping of requests.

c9: IF A.4/34 THEN o ELSE n/a – – the P-Access-Network-Info header extension.

c10: IF A.4/34 AND (A.3/1 OR A.3/2A OR A.3/7) THEN m ELSE n/a – – the P-Access-Network-Info header extension and UE, P-CSCF (IMS-ALG) or AS.

c11: IF A.4/34 AND (A.3/2A OR A.3/7A OR A.3/7D OR A3A/84) THEN m ELSE n/a – – the P-Access-Network-Info header extension and P-CSCF (IMS-ALG), AS acting as terminating UA, AS acting as third-party call controller or EATF.

c12: IF A.4/36 THEN o ELSE n/a – – the P-Charging-Vector header extension.

c13: IF A.4/35 THEN o ELSE n/a – – the P-Charging-Function-Addresses header extension.

c14: IF A.4/35 THEN m ELSE n/a – – the P-Charging-Function-Addresses header extension.

c15: IF A.4/37 OR A.4/37A THEN o ELSE n/a – – security mechanism agreement for the session initiation protocol or mediasec header field parameter for marking security mechanisms related to media (note).

c16: IF A.4/37 OR A.4/37A THEN m ELSE n/a – – security mechanism agreement for the session initiation protocol or mediasec header field parameter for marking security mechanisms related to media.

c17: IF A.4/38 THEN o ELSE n/a – – the Reason header field for the session initiation protocol.

c18: IF A.4/40 THEN o ELSE n/a – – caller preferences for the session initiation protocol.

c19: IF A.4/43 THEN m ELSE n/a – – the SIP Referred-By mechanism.

c20: IF A.4/43 THEN o ELSE n/a – – the SIP Referred-By mechanism.

c21: IF A.3/2 THEN m ELSE IF A.4/38 THEN o ELSE n/a – – P-CSCF, the Reason header field for the session initiation protocol.

c22: IF A.4/40 THEN m ELSE n/a – – caller preferences for the session initiation protocol.

c23: IF A.4/60 THEN m ELSE n/a – – SIP location conveyance.

c24: IF A.4/38 THEN m ELSE n/a – – the Reason header field for the session initiation protocol.

c25: IF A.4/70B THEN m ELSE n/a – – inclusion of CANCEL, BYE, REGISTER and PUBLISH in communications resource priority for the session initiation protocol.

c26: IF A.4/76 THEN o ELSE n/a – – transporting user to user information for call centers using SIP.

c29: IF A.4/71 AND (A.3/9B OR A.3/9C OR A.3/13B OR A.3/13C) THEN m ELSE IF A.3/1 AND NOT A.3C/1 THEN n/a ELSE o – – addressing an amplification vulnerability in session initiation protocol forking proxies, IBCF (IMS-ALG), IBCF (Screening of SIP signalling), ISC gateway function (IMS-ALG), ISC gateway function (Screening of SIP signalling), UE, UE performing the functions of an external attached network.

c30: IF A.4/71 THEN m ELSE n/a – – addressing an amplification vulnerability in session initiation protocol forking proxies.

c31: IF A.3/1 AND NOT A.3C/1 THEN n/a ELSE o – – UE, UE performing the functions of an external attached network.

c32: IF A.4/91 THEN m ELSE n/a – – the Session-ID header.

c33: IF A.4/111 THEN m ELSE n/a – – the Relayed-Charge header field extension.

c34: IF A.4/36 THEN m ELSE n/a – – the P-Charging-Vector header extension.

c35: IF A.4/113 AND (A.3/1 OR A.3/2A OR A.3/7) THEN m ELSE n/a – – the Cellular-Network-Info header extension and UE, P-CSCF (IMS-ALG) or AS.

c36: IF A.4/113 AND (A.3/2A OR A.3/7A OR A.3/7D OR A3A/84) THEN m ELSE n/a – – the Cellular-Network-Info header extension and P-CSCF (IMS-ALG), AS acting as terminating UA, AS acting as third-party call controller or EATF.

c37: IF A.4/119 THEN o ELSE n/a – – Content-ID header field in Session Initiation Protocol (SIP).

c38: IF A.4/119 THEN m ELSE n/a – – Content-ID header field in Session Initiation Protocol (SIP).

NOTE: Support of this header in this method is dependent on the security mechanism and the security architecture which is implemented. Use of this header in this method is not appropriate to the security mechanism defined by 3GPP TS 33.203 [19].

Prerequisite A.5/2 – – BYE request

Table A.10: Supported message bodies within the BYE request

Item

Header

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

1

XML Schema for PSTN

[11B]

n/a

c1

[11B]

n/a

c1

2

VoiceXML expr / namelist data

[145] 4.2

m

c2

[145] 4.2

m

c2

3

application/vnd.3gpp.ussd

[8W]

n/a

c3

[8W]

n/a

c4

4

application/sdp

[30] 8

o

c5

[30] 8

m

c6

5

application/vnd.etsi.aoc+xml

[8N] 4.7.2

n/a

c7

[8N] 4.7.2

n/a

c8

c1: IF A.3/6 OR A.3/7A OR A.3/7B OR A.3/7D OR A.3/9B OR A.3/13B THEN o ELSE n/a – – MGCF, AS acting as terminating UA, or redirect server, AS acting as originating UA, AS performing 3rd party call control, IBCF (IMS-ALG), ISC gateway function (IMS-ALG).

c2: IF A.4/84 THEN m ELSE n/a – – SIP Interface to VoiceXML Media Services.

c3: IF A.3A/93 OR A.3/9 OR A.3/2 OR A.3A/89 THEN m ELSE n/a – – USSI AS, IBCF, P-CSCF, ATCF (UA).

c4: IF A.3A/92 OR A.3/9 OR A.3/2 OR A.3A/89 THEN m ELSE n/a – – USSI UE, IBCF, P-CSCF, ATCF (UA).

c5: IF A.4/16 THEN o ELSE n/a – – integration of resource management and SIP.

c6: IF A.4/16 THEN m ELSE n/a – – integration of resource management and SIP.

c7 IF A.3A/53 THEN m ELSE n/a – – Advice of charge application server.

c8 IF A.3A/54 THEN m ELSE n/a – – Advice of charge UA client.

TableA.11: Void

Prerequisite A.5/3 – – BYE response

Prerequisite: A.6/1 – – Additional for 100 (Trying) response

Table A.11A: Supported header fields within the BYE response

Item

Header field

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

1

Call-ID

[26] 20.8

m

m

[26] 20.8

m

m

2

Content-Length

[26] 20.14

m

m

[26] 20.14

m

m

3

CSeq

[26] 20.16

m

m

[26] 20.16

m

m

4

Date

[26] 20.17

c1

c1

[26] 20.17

m

m

5

From

[26] 20.20

m

m

[26] 20.20

m

m

6

To

[26] 20.39

m

m

[26] 20.39

m

m

7

Via

[26] 20.42

m

m

[26] 20.42

m

m

c1: IF A.4/11 THEN o ELSE n/a – – insertion of date in requests and responses.

Prerequisite A.5/3 – – BYE response for all remaining status-codes

Table A.12: Supported header fields within the BYE response

Item

Header field

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

0A

Allow

[26] 20.5

c11

c11

[26] 20.5

m

m

1

Call-ID

[26] 20.8

m

m

[26] 20.8

m

m

1A

Cellular-Network-Info

7.2.15

n/a

c19

7.2.15

n/a

c20

2

Content-Disposition

[26] 20.11

o

o

[26] 20.11

m

m

3

Content-Encoding

[26] 20.12

o

o

[26] 20.12

m

m

3A

Content-ID

[256] 3.2

o

c21

[256] 3.2

m

c22

4

Content-Language

[26] 20.13

o

o

[26] 20.13

m

m

5

Content-Length

[26] 20.14

m

m

[26] 20.14

m

m

6

Content-Type

[26] 20.15

m

m

[26] 20.15

m

m

7

CSeq

[26] 20.16

m

m

[26] 20.16

m

m

8

Date

[26] 20.17

c1

c1

[26] 20.17

m

m

9

From

[26] 20.20

m

m

[26] 20.20

m

m

9A

Geolocation-Error

[89] 4.3

c12

c12

[89] 4.3

c12

c12

10

MIME-Version

[26] 20.24

o

o

[26] 20.24

m

m

10A

P-Access-Network-Info

[52] 4.4, [52A] 4, [234] 2

c5

c6

[52] 4.4, [52A] 4, [234] 2

c5

c7

10B

P-Asserted-Identity

[34] 9.1

n/a

n/a

[34] 9.1

c3

c3

10C

P-Charging-Function-Addresses

[52] 4.5, [52A] 4

c9

c10

[52] 4.5, [52A] 4

c9

c10

10D

P-Charging-Vector

[52] 4.6, [52A] 4

c8

c18

[52] 4.6, [52A] 4

c8

c18

10F

P-Preferred-Identity

[34] 9.2

c3

x

[34] 9.2

n/a

n/a

10G

Privacy

[33] 4.2

c4

n/a

[33] 4.2

c4

c4

10H

Relayed-Charge

7.2.12

n/a

c17

7.2.12

n/a

c17

10I

Require

[26] 20.32

m

m

[26] 20.32

m

m

10J

Server

[26] 20.35

o

o

[26] 20.35

o

o

10K

Session-ID

[162]

o

c16

[162]

o

c16

11

Timestamp

[26] 20.38

m

m

[26] 20.38

c2

c2

12

To

[26] 20.39

m

m

[26] 20.39

m

m

12A

User-Agent

[26] 20.41

o

o

[26] 20.41

o

o

12B

User-to-User

[126] 7

c13

c13

[126] 7

c13

c13

13

Via

[26] 20.42

m

m

[26] 20.42

m

m

14

Warning

[26] 20.43

o (note)

o (note)

[26] 20.43

o

o

c1: IF A.4/11 THEN o ELSE n/a – – insertion of date in requests and responses.

c2: IF A.4/6 THEN m ELSE n/a – – timestamping of requests.

c3: IF A.4/25 THEN o ELSE n/a – – private extensions to the Session Initiation Protocol (SIP) for asserted identity within trusted networks.

c4: IF A.4/26 THEN o ELSE n/a – – a privacy mechanism for the Session Initiation Protocol (SIP).

c5: IF A.4/34 THEN o ELSE n/a – – the P-Access-Network-Info header extension.

c6: IF A.4/34 AND (A.3/1 OR A.3/2A ORA.3/7) THEN m ELSE n/a – – the P-Access-Network-Info header extension and UE, P-CSCF (IMS-ALG), or AS.

c7: IF A.4/34 AND (A.3/2A OR A.3/7A OR A.3/7D OR A3A/84) THEN m ELSE n/a – – the P-Access-Network-Info header extension and P-CSCF (IMS-ALG), AS acting as terminating UA, AS acting as third-party call controller or EATF.

c8: IF A.4/36 THEN o ELSE n/a – – the P-Charging-Vector header extension.

c9: IF A.4/35 THEN o ELSE n/a – – the P-Charging-Function-Addresses header extension.

c10: IF A.4/35 THEN m ELSE n/a – – the P-Charging-Function-Addresses header extension.

c11: IF A.6/18 THEN m ELSE o – – 405 (Method Not Allowed).

c12: IF A.4/60 THEN m ELSE n/a – – SIP location conveyance.

c13: IF A.4/76 THEN o ELSE n/a – – transporting user to user information for call centers using SIP.

c16: IF A.4/91 THEN m ELSE n/a – – the Session-ID header.

c17: IF A.4/111 THEN m ELSE n/a – – the Relayed-Charge header field extension.

c18: IF A.4/36 THEN m ELSE n/a – – the P-Charging-Vector header extension.

c19: IF A.4/113 AND (A.3/1 OR A.3/2A OR A.3/7) THEN m ELSE n/a – – the Cellular-Network-Info header extension and UE, P-CSCF (IMS-ALG), or AS.

c20: IF A.4/113 AND (A.3/2A OR A.3/7A OR A.3/7D OR A3A/84) THEN m ELSE n/a – – the Cellular-Network-Info header extension and P-CSCF (IMS-ALG), AS acting as terminating UA, AS acting as third-party call controller or EATF.

c21: IF A.4/119 THEN o ELSE n/a – – Content-ID header field in Session Initiation Protocol (SIP).

c22: IF A.4/119 THEN m ELSE n/a – – Content-ID header field in Session Initiation Protocol (SIP).

NOTE: For a 488 (Not Acceptable Here) response, RFC 3261 [26] gives the status of this header as SHOULD rather than OPTIONAL.

Prerequisite A.5/3 – – BYE response

Prerequisite: A.6/102 – – Additional for 2xx response

Table A.13: Supported header fields within the BYE response

Item

Header field

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

0A

Accept-Resource-Priority

[116] 3.2

c5

c5

[116] 3.2

c5

c5

0B

Allow-Events

[28] 8.2.2

c3

c3

[28] 8.2.2

c4

c4

1

Authentication-Info

[26] 20.6

c1

c1

[26] 20.6

c2

c2

4

Supported

[26] 20.37

o

m

[26] 20.37

m

m

c1: IF A.4/7 THEN o ELSE n/a – – authentication between UA and UA.

c2: IF A.4/7 THEN m ELSE n/a – – authentication between UA and UA.

c3: IF A.4/22 THEN o ELSE n/a – – acting as the notifier of event information.

c4: IF A.4/23 THEN m ELSE n/a – – acting as the subscriber to event information.

c5: IF A.4/70B THEN m ELSE n/a – – inclusion of CANCEL, BYE, REGISTER and PUBLISH in communications resource priority for the session initiation protocol.

Prerequisite A.5/3 – – BYE response

Prerequisite: A.6/103 OR A.6/104 OR A.6/105 OR A.6/106 – – Additional for 3xx – 6xx response

Table A.13A: Supported header fields within the BYE response

Item

Header field

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

1

Error-Info

[26] 20.18

o

o

[26] 20.18

o

o

2

Response-Source

7.2.17

n/a

c1

7.2.17

n/a

c1

c1: IF A.4/115 THEN o ELSE n/a – – use of the Response-Source header field in SIP error responses?

Prerequisite A.5/3 – – BYE response

Prerequisite: A.6/103 OR A.6/35 – – Additional for 3xx or 485 (Ambiguous) response

Table A.14: Supported header fields within the BYE response

Item

Header field

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

0B

Contact

[26] 20.10

o (note)

o

[26] 20.10

m

m

NOTE: RFC 3261 [26] gives the status of this header as SHOULD rather than OPTIONAL.

Prerequisite A.5/3 – – BYE response

Prerequisite: A.6/14 – – Additional for 401 (Unauthorized) response

Table A.15: Supported header fields within the BYE response

Item

Header field

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

2

Proxy-Authenticate

[26] 20.27

c1

c1

[26] 20.27

c1

c1

8

WWW-Authenticate

[26] 20.44

m

m

[26] 20.44

m

m

c1: IF A.4/7 THEN m ELSE n/a – – support of authentication between UA and UA.

Prerequisite A.5/3 – – BYE response

Prerequisite: A.6/17 OR A.6/23 OR A.6/30 OR A.6/36 OR A.6/42 OR A.6/45 OR A.6/50 OR A.6/51 – – Additional for 404 (Not Found), 413 (Request Entity Too Large), 480(Temporarily not available), 486 (Busy Here), 500 (Internal Server Error), 503 (Service Unavailable), 600 (Busy Everywhere), 603 (Decline) response

Table A.16: Supported header fields within the BYE response

Item

Header field

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

3

Retry-After

[26] 20.33

o

o

[26] 20.33

o

o

Table A.17: Void

Prerequisite A.5/3 – – BYE response

Prerequisite: A.6/19 – – Additional for 407 (Proxy Authentication Required) response

Table A.18: Supported header fields within the BYE response

Item

Header field

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

2

Proxy-Authenticate

[26] 20.27

c1

c1

[26] 20.27

c1

c1

6

WWW-Authenticate

[26] 20.44

o

o

[26] 20.44

o

o

c1: IF A.4/7 THEN m ELSE n/a – – support of authentication between UA and UA.

Prerequisite A.5/3 – – BYE response

Prerequisite A.6/25 – – Additional for 415 (Unsupported Media Type) response

Table A.19: Supported header fields within the BYE response

Item

Header field

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

1

Accept

[26] 20.1

o.1

o.1

[26] 20.1

m

m

2

Accept-Encoding

[26] 20.2

o.1

o.1

[26] 20.2

m

m

3

Accept-Language

[26] 20.3

o.1

o.1

[26] 20.3

m

m

o.1 At least one of these capabilities is supported.

Prerequisite A.5/3 – – BYE response

Prerequisite: A.6/26A – – Additional for 417 (Unknown Resource-Priority) response

Table A.19A: Supported header fields within the BYE response

Item

Header field

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

1

Accept-Resource-Priority

[116] 3.2

c1

c1

[116] 3.2

c1

c1

c1: IF A.4/70B THEN m ELSE n/a – – inclusion of CANCEL, BYE, REGISTER and PUBLISH in communications resource priority for the session initiation protocol.

Prerequisite A.5/3 – – BYE response

Prerequisite: A.6/27 – – Additional for 420 (Bad Extension) response

Table A.20: Supported header fields within the BYE response

Item

Header field

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

5

Unsupported

[26] 20.40

m

m

[26] 20.40

m

m

Prerequisite A.5/3 – – BYE response

Prerequisite: A.6/28 OR A.6/41A – – Additional for 421 (Extension Required), 494 (Security Agreement Required) response

Table A.20A: Supported header fields within the BYE response

Item

Header field

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

3

Security-Server

[48] 2

x

x

[48] 2

c1

c1

c1: IF A.4/37 THEN m ELSE n/a – – security mechanism agreement for the session initiation protocol.

Table A.21: Void

Prerequisite A.5/3 – – BYE response

Prerequisite: A.6/6 – – Additional for 200 (OK) response

Table A.22: Supported message bodies within the BYE response

Item

Header

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

1

VoiceXML expr / namelist data

[145] 4.2

o

c1

[145] 4.2

o

c1

2

application/vnd.etsi.aoc+xml

[8N] 4.7.2

n/a

c2

[8N] 4.7.2

n/a

c3

c1: IF A.4/84 THEN o ELSE n/a – – SIP Interface to VoiceXML Media Services.

c2 IF A.3A/53 THEN m ELSE n/a – – Advice of charge application server.

c3 IF A.3A/54 THEN m ELSE n/a – – Advice of charge UA client.

A.2.1.4.4 CANCEL method

Prerequisite A.5/4 – – CANCEL request

Table A.23: Supported header fields within the CANCEL request

Item

Header field

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

1

Accept-Contact

[56B] 9.2

c9

c9

[56B] 9.2

c11

c11

5

Authorization

[26] 20.7

c3

c3

[26] 20.7

c3

c3

6

Call-ID

[26] 20.8

m

m

[26] 20.8

m

m

8

Content-Length

[26] 20.14

m

m

[26] 20.14

m

m

8A

Content-Type

[26] 20.15

c22

c22

[26] 20.15

o

o

9

CSeq

[26] 20.16

m

m

[26] 20.16

m

m

10

Date

[26] 20.17

c4

c4

[26] 20.17

m

m

11

From

[26] 20.20

m

m

[26] 20.20

m

m

11A

Max-Breadth

[117] 5.8

n/a

c16

[117] 5.8

c17

c17

12

Max-Forwards

[26] 20.22

m

m

[26] 20.22

n/a

c18

14

Privacy

[33] 4.2

c6

n/a

[33] 4.2

c6

n/a

15

Reason

[34A] 2

c7

c10

[34A] 2

c12

c12

16

Record-Route

[26] 20.30

n/a

c18

[26] 20.30

n/a

c18

17

Reject-Contact

[56B] 9.2

c9

c9

[56B] 9.2

c11

c11

17A

Relayed-Charge

7.2.12

n/a

c21

7.2.12

n/a

c21

17B

Request-Disposition

[56B] 9.1

c9

c9

[56B] 9.1

c11

c11

17C

Resource-Priority

[116] 3.1

c13

c13

[116] 3.1

c13

c13

18

Route

[26] 20.34

m

m

[26] 20.34

n/a

c18

18A

Session-ID

[162]

o

c19

[162]

o

c19

19

Supported

[26] 20.37

o

o

[26] 20.37

m

m

20

Timestamp

[26] 20.38

c8

c8

[26] 20.38

m

m

21

To

[26] 20.39

m

m

[26] 20.39

m

m

22

User-Agent

[26] 20.41

o

o

[26] 20.41

o

o

23

Via

[26] 20.42

m

m

[26] 20.42

m

m

c3: IF A.4/7 THEN m ELSE n/a – – authentication between UA and UA.

c4: IF A.4/11 THEN o ELSE n/a – – insertion of date in requests and responses.

c6: IF A.4/26 THEN o ELSE n/a – – a privacy mechanism for the Session Initiation Protocol (SIP).

c7: IF A.4/38 THEN o ELSE n/a – – the Reason header field for the session initiation protocol.

c8: IF A.4/6 THEN o ELSE n/a – – timestamping of requests.

c9: IF A.4/40 THEN o ELSE n/a – – caller preferences for the session initiation protocol.

c10: IF A.3/2 THEN m ELSE IF A.4/38 THEN o ELSE n/a – – P-CSCF, the Reason header field for the session initiation protocol.

c11: IF A.4/40 THEN m ELSE n/a – – caller preferences for the session initiation protocol.

c12: IF A.4/38 THEN m ELSE n/a – – the Reason header field for the session initiation protocol.

c13: IF A.4/70B THEN m ELSE n/a – – inclusion of CANCEL, BYE, REGISTER and PUBLISH in communications resource priority for the session initiation protocol.

c16: IF A.4/71 AND (A.3/9B OR A.3/9C OR A.3/13B OR A.3/13C) THEN m ELSE IF A.3/1 AND NOT A.3C/1 THEN n/a ELSE o – – addressing an amplification vulnerability in session initiation protocol forking proxies, IBCF (IMS-ALG), IBCF (Screening of SIP signalling), ISC gateway function (IMS-ALG), ISC gateway function (Screening of SIP signalling), UE, UE performing the functions of an external attached network..

c17: IF A.4/71 THEN m ELSE n/a – – addressing an amplification vulnerability in session initiation protocol forking proxies.

c18: IF A.3/1 AND NOT A.3C/1 THEN n/a ELSE o – – UE, UE performing the functions of an external attached network.

c19: IF A.4/91 THEN m ELSE n/a – – the Session-ID header.

c21: IF A.4/111 THEN m ELSE n/a – – the Relayed-Charge header field extension.

c22: IF A.4/16 OR A.24/1 THEN m ELSE o – – integration of resource management and SIP or XML Schema for PSTN.

Prerequisite A.5/4 – – CANCEL request

Table A.24: Supported message bodies within the CANCEL request

Item

Header

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

1

XML Schema for PSTN

[11B]

c1

[11B]

c1

2

application/sdp

[30] 8

o

c2

[30] 8

m

c3

c1: IF A.3/6 OR A.3/7A OR A.3/7B OR A.3/7D OR A.3/9B OR A.3/13B THEN o ELSE n/a – – MGCF, AS acting as terminating UA, or redirect server, AS acting as originating UA, AS performing 3rd party call control, IBCF (IMS-ALG), ISC gateway function (IMS-ALG).

c2: IF A.4/16 THEN o ELSE n/a – – integration of resource management and SIP.

c3: IF A.4/16 THEN m ELSE n/a – – integration of resource management and SIP.

Prerequisite A.5/5 – – CANCEL response for all status-codes

Table A.25: Supported header fields within the CANCEL response

Item

Header field

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

1

Call-ID

[26] 20.8

m

m

[26] 20.8

m

m

2

Content-Length

[26] 20.14

m

m

[26] 20.14

m

m

3

CSeq

[26] 20.16

m

m

[26] 20.16

m

m

4

Date

[26] 20.17

c1

c1

[26] 20.17

m

m

5

From

[26] 20.20

m

m

[26] 20.20

m

m

5C

Privacy

[33] 4.2

c3

n/a

[33] 4.2

c3

n/a

5D

Relayed-Charge

7.2.12

n/a

c8

7.2.12

n/a

c8

5E

Session-ID

[162]

o

c6

[162]

o

c6

6

Timestamp

[26] 20.38

m

m

[26] 20.38

c2

c2

7

To

[26] 20.39

m

m

[26] 20.39

m

m

7A

User-Agent

[26] 20.41

o

o

[26] 20.41

o

o

8

Via

[26] 20.42

m

m

[26] 20.42

m

m

9

Warning

[26] 20.43

o (note)

o

[26] 20.43

o

o

c1: IF A.4/11 THEN o ELSE n/a – – insertion of date in requests and responses.

c2: IF A.4/6 THEN m ELSE n/a – – timestamping of requests.

c3: IF A.4/26 THEN o ELSE n/a – – a privacy mechanism for the Session Initiation Protocol (SIP).

c6: IF A.4/91 THEN m ELSE n/a – – the Session-ID header.

c8: IF A.4/111 THEN m ELSE n/a – – the Relayed-Charge header field extension.

NOTE: For a 488 (Not Acceptable Here) response, RFC 3261 [26] gives the status of this header as SHOULD rather than OPTIONAL.

Prerequisite A.5/5 – – CANCEL response

Prerequisite: A.6/102 – – Additional for 2xx response

Table A.26: Supported header fields within the CANCEL response

Item

Header field

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

1

Accept-Resource-Priority

[116] 3.2

c1

c1

[116] 3.2

c1

c1

4

Supported

[26] 20.37

o

m

[26] 20.37

m

m

c1: IF A.4/70B THEN m ELSE n/a – – inclusion of CANCEL, BYE, REGISTER and PUBLISH in communications resource priority for the session initiation protocol.

Prerequisite A.5/5 – – CANCEL response

Prerequisite: A.6/103 OR A.6/104 OR A.6/105 OR A.6/106 – – Additional for 3xx – 6xx response

Table A.26A: Supported header fields within the CANCEL response

Item

Header

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

1

Error-Info

[26] 20.18

o

o

[26] 20.18

o

O

2

Response-Source

7.2.17

n/a

c1

7.2.17

n/a

c1

c1: IF A.4/115 THEN o ELSE n/a – – use of the Response-Source header field in SIP error responses?

Table A.27: Void

Prerequisite A.5/5 – – CANCEL response

Prerequisite: A.6/17 OR A.6/23 OR A.6/30 OR A.6/36 OR A.6/42 OR A.6/45 OR A.6/50 OR A.6/51 – – Additional for 404 (Not Found), 413 (Request Entity Too Large), 480(Temporarily not available), 486 (Busy Here), 500 (Internal Server Error), 503 (Service Unavailable), 600 (Busy Everywhere), 603 (Decline) response

Table A.28: Supported header fields within the CANCEL response

Item

Header field

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

4

Retry-After

[26] 20.33

o

o

[26] 20.33

o

o

Table A.29: Void

Table A.30: Void

Prerequisite A.5/5 – – CANCEL response

Prerequisite: A.6/26A – – Additional for 417 (Unknown Resource-Priority) response

Table A.30A: Supported header fields within the CANCEL response

Item

Header field

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

1

Accept-Resource-Priority

[116] 3.2

c1

c1

[116] 3.2

c1

c1

c1: IF A.4/70B THEN m ELSE n/a – – inclusion of CANCEL, BYE, REGISTER and PUBLISH in communications resource priority for the session initiation protocol.

Prerequisite A.5/5 – – CANCEL response

Table A.31: Supported message bodies within the CANCEL response

Item

Header

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

1

A.2.1.4.5 Void

A.2.1.4.6 INFO method

Prerequisite A.5/6 – – INFO request

Table A.32: Supported header fields within the INFO request

Item

Header field

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

1

Accept

[26] 20.1

o

o

[26] 20.1

m

m

2

Accept-Encoding

[26] 20.2

o

o

[26] 20.2

m

m

3

Accept-Language

[26] 20.3

o

o

[26] 20.3

m

m

4

Allow

[26] 20.5

o

o

[26] 20.5

m

m

5

Allow-Events

[28] 8.2.2

c1

c1

[28] 8.2.2

c2

c2

6

Authorization

[26] 20.7

c3

c3

[26] 20.7

c3

c3

7

Call-ID

[26] 20.8

m

m

[26] 20.8

m

m

7A

Call-Info

[26] 20.9

o

o

[26] 20.9

o

o

8

Cellular-Network-Info

7.2.15

n/a

c45

7.2.15

n/a

c46

9

Content-Disposition

[26] 20.11

o

o

[26] 20.11

m

m

10

Content-Encoding

[26] 20.12

o

o

[26] 20.12

m

m

10A

Content-ID

[256] 3.2

o

c47

[256] 3.2

m

c48

11

Content-Language

[26] 20.13

o

o

[26] 20.13

m

m

12

Content-Length

[26] 20.14

m

m

[26] 20.14

m

m

13

Content-Type

[26] 20.15

m

m

[26] 29.15

m

m

14

CSeq

[26] 20.16

m

m

[26] 20.16

m

m

15

Date

[26] 20.17

c4

c4

[26] 20.17

m

m

16

From

[26] 20.20

m

m

[26] 20.20

m

m

17

Geolocation

[89] 4.1

c29

c29

[89] 4.1

c29

c29

17A

Geolocation-Routing

[89] 4.2

c29

c29

[89] 4.2

c29

c29

18

Info-Package

[25] 7.2

c42

c42

[25] 7.2

c42

c42

19

Max-Breadth

[117] 5.8

n/a

c39

[117] 5.8

c40

c40

20

Max-Forwards

[26] 20.22

m

m

[26] 20.22

n/a

c41

21

MIME-Version

[26] 20.24

o

o

[26] 20.24

m

m

22

P-Access-Network-Info

[52] 4.4, [234] 2

c15

c16

[52] 4.4, [234] 2

c15

c17

23

P-Charging-Function-Addresses

[52] 4.5

c20

c21

[52] 4.5

c20

c21

24

P-Charging-Vector

[52] 4.6

c18

c19

[52] 4.6

c18

c19

26

Privacy

[33] 4.2

c12

c12

[33] 4.2

c12

c12

27

Proxy-Authorization

[26] 20.28

c5

c5

[26] 20.28

n/a

n/a

28

Proxy-Require

[26] 20.29

o

n/a

[26] 20.29

n/a

n/a

29

Reason

[34A] 2

c6

c6

[34A] 2

c6

c6

30

Record-Route

[26] 20.30

n/a

c41

[26] 20.30

n/a

c41

31

Referred-By

[59] 3

c25

c25

[59] 3

c26

c26

32

Relayed-Charge

7.2.12

n/a

c44

7.2.12

n/a

c44

33

Request-Disposition

[56B] 9.1

c24

c24

[56B] 9.1

c28

c28

34

Require

[26] 20.32

m

m

[26] 20.32

m

m

35

Resource-Priority

[116] 3.1

c30

c30

[116] 3.1

c30

c30

36

Route

[26] 20.34

m

m

[26] 20.34

n/a

c41

37

Security-Client

[48] 2.3.1

c22

c22

[48] 2.3.1

n/a

n/a

38

Security-Verify

[48] 2.3.1

c23

c23

[48] 2.3.1

n/a

n/a

38A

Session-ID

[162]

o

c43

[162]

o

c43

39

Subject

[26] 20.35

o

o

[26] 20.36

o

o

40

Supported

[26] 20.37

m

m

[26] 20.37

m

m

41

Timestamp

[26] 20.38

c10

c10

[26] 20.38

m

m

42

To

[26] 20.39

m

m

[26] 20.39

m

m

43

User-Agent

[26] 20.41

o

o

[26] 20.41

o

o

44

Via

[26] 20.42

m

m

[26] 20.42

m

m

c1: IF A.4/22 THEN o ELSE n/a – – acting as the notifier of event information.

c2: IF A.4/23 THEN m ELSE n/a – – acting as the subscriber to event information.

c3: IF A.4/7 THEN m ELSE n/a – – authentication between UA and UA.

c4: IF A.4/11 THEN o ELSE n/a – – insertion of date in requests and responses.

c5: IF A.4/8A THEN m ELSE n/a – – authentication between UA and proxy.

c6: IF A.4/38 THEN o ELSE n/a – – the Reason header field for the session initiation protocol.

c10: IF A.4/6 THEN o ELSE n/a – – timestamping of requests.

c12: IF A.4/26 THEN o ELSE n/a – – a privacy mechanism for the Session Initiation Protocol (SIP).

c15: IF A.4/34 THEN o ELSE n/a – – the P-Access-Network-Info header extension.

c16: IF A.4/34 AND A.3/1 THEN m ELSE n/a – – the P-Access-Network-Info header extension and UE.

c17: IF A.4/34 AND (A.3/7A OR A.3/7D) THEN m ELSE n/a – – the P-Access-Network-Info header extension and AS acting as terminating UA or AS acting as third-party call controller.

c18: IF A.4/36 THEN o ELSE n/a – – the P-Charging-Vector header extension.

c19: IF A.4/36 THEN m ELSE n/a – – the P-Charging-Vector header extension.

c20: IF A.4/35 THEN o ELSE n/a – – the P-Charging-Function-Addresses header extension.

c21: IF A.4/35 THEN m ELSE n/a – – the P-Charging-Function-Addresses header extension.

c22: IF A.4/37 OR A.4/37A THEN o ELSE n/a – – security mechanism agreement for the session initiation protocol or mediasec header field parameter for marking security mechanisms related to media? (note 2).

c23: IF A.4/37 OR A.4/37A THEN m ELSE n/a – – security mechanism agreement for the session initiation protocol or mediasec header field parameter for marking security mechanisms related to media.

c24 IF A.4/40 THEN o ELSE n/a – – caller preferences for the session initiation protocol.

c25: IF A.4/43 THEN m ELSE n/a – – the SIP Referred-By mechanism.

c26: IF A.4/43 THEN o ELSE n/a – – the SIP Referred-By mechanism.

c28: IF A.4/40 THEN m ELSE n/a – – caller preferences for the session initiation protocol.

c29: IF A.4/60 THEN m ELSE n/a – – SIP location conveyance.

c30: IF A.4/70A THEN m ELSE n/a – – inclusion of INFO, SUBSCRIBE, NOTIFY in communications resource priority for the session initiation protocol.

c39: IF A.4/71 AND (A.3/9B OR A.3/9C OR A.3/13B OR A.3/13C) THEN m ELSE IF A.3/1 AND NOT A.3C/1 THEN n/a ELSE o – – addressing an amplification vulnerability in session initiation protocol forking proxies, IBCF (IMS-ALG), IBCF (Screening of SIP signalling), ISC gateway function (IMS-ALG), ISC gateway function (Screening of SIP signalling), UE, UE performing the functions of an external attached network.

c40: IF A.4/71 THEN m ELSE n/a – – addressing an amplification vulnerability in session initiation protocol forking proxies.

c41: IF A.3/1 AND NOT A.3C/1 THEN n/a ELSE o – – UE, UE performing the functions of an external attached network.

c42: IF A.4/13A THEN n/a ELSE m – – legacy INFO usage.

c43: IF A.4/91 THEN m ELSE n/a – – the Session-ID header.

c44: IF A.4/111 THEN m ELSE n/a – – the Relayed-Charge header field extension.

c45: IF A.4/113 AND A.3/1 THEN m ELSE n/a – – the Cellular-Network-Info header extension and UE.

c46: IF A.4/113 AND (A.3/7A OR A.3/7D) THEN m ELSE n/a – – the Cellular-Network-Info header extension and AS acting as terminating UA or AS acting as third-party call controller.

c47: IF A.4/119 THEN o ELSE n/a – – Content-ID header field in Session Initiation Protocol (SIP).

c48: IF A.4/119 THEN m ELSE n/a – – Content-ID header field in Session Initiation Protocol (SIP).

NOTE 2: Support of this header field in this method is dependent on the security mechanism and the security architecture which is implemented. Use of this header field in this method is not appropriate to the security mechanism defined by 3GPP TS 33.203 [19].

Prerequisite A.5/6 – – INFO request

Table A.33: Supported message bodies within the INFO request

Item

Header

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

1

Info-Package

[25]

m

m

[25]

m

m

2

application/vnd.etsi.aoc+xml

[8N] 4.7.2

n/a

c1

[8N] 4.7.2

n/a

c2

3

application/EmergencyCallData.eCall.MSD

[244] 14.3

m

c3

[244] 14.3

m

c4

4

application/EmergencyCallData.Control+xml

[244] 14.4

m

c3

[244] 14.4

m

c3

c1: IF A.3A/53 THEN m ELSE n/a – – Advice of charge application server.

c2: IF A.3A/54 THEN m ELSE n/a – – Advice of charge UA client.

c3: IF (A.3/1 AND A.4/120) THEN m ELSE IF ((A.3/2A OR A.3/11A OR A.3A/84) AND A.4/120) THEN i ELSE n/a – – UE, Next-Generation Pan-European eCall emergency service, P-CSCF (IMS-ALG), E-CSCF acting as UA, EATF.

c4: IF ((A.3/2A OR A.3/11A OR A.3A/84) AND A.4/120) THEN i ELSE n/a – – P-CSCF (IMS-ALG), E-CSCF acting as UA, EATF, Next-Generation Pan-European eCall emergency service.

Prerequisite A.5/7 – – INFO response

Prerequisite: A.6/1 – – Additional for 100 (Trying) response

Table A.34: Supported header fields within the INFO response

Item

Header field

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

1

Call-ID

[26] 20.8

m

m

[26] 20.8

m

m

2

Content-Length

[26] 20.14

m

m

[26] 20.14

m

m

3

CSeq

[26] 20.16

m

m

[26] 20.16

m

m

4

Date

[26] 20.17

c1

c1

[26] 20.17

m

m

5

From

[26] 20.20

m

m

[26] 20.20

m

m

6

To

[26] 20.39

m

m

[26] 20.39

m

m

7

Via

[26] 20.42

m

m

[26] 20.42

m

m

c1: IF A.4/11 THEN o ELSE n/a – – insertion of date in requests and responses.

Prerequisite A.5/7 – – INFO response for all remaining status-codes

Table A.35: Supported header fields within the INFO response

Item

Header field

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

0A

Allow

[26] 20.5

c12

c12

[26] 20.5

m

m

1

Call-ID

[26] 20.8

m

m

[26] 20.8

m

m

2

Call-Info

[26] 20.9

o

o

[26] 20.9

o

o

2A

Cellular-Network-Info

7.2.15

n/a

c19

7.2.15

n/a

c20

3

Content-Disposition

[26] 20.11

o

o

[26] 20.11

m

m

4

Content-Encoding

[26] 20.12

o

o

[26] 20.12

m

m

4A

Content-ID

[256] 3.2

o

c21

[256] 3.2

m

c22

5

Content-Language

[26] 20.13

o

o

[26] 20.13

m

m

6

Content-Length

[26] 20.14

m

m

[26] 20.14

m

m

7

Content-Type

[26] 20.15

m

m

[26] 20.15

m

m

8

CSeq

[26] 20.16

m

m

[26] 20.16

m

m

9

Date

[26] 20.17

c1

c1

[26] 20.17

m

m

10

From

[26] 20.20

m

m

[26] 20.20

m

m

11

Geolocation-Error

[89] 4.3

c14

c14

[89] 4.3

c14

c14

12

MIME-Version

[26] 20.24

o

o

[26] 20.24

m

m

13

Organization

[26] 20.25

o

o

[26] 20.25

o

o

14

P-Access-Network-Info

[52] 4.4, [52A] 4, [234] 2

c5

c6

[52] 4.4, [52A] 4, [234] 2

c5

c7

15

P-Charging-Function-Addresses

[52] 4.5, [52A] 4

c10

c11

[52] 4.5, [52A] 4

c10

c11

16

P-Charging-Vector

[52] 4.6, [52A] 4

c8

c9

[52] 4.6, [52A] 4

c8

c9

18

Privacy

[33] 4.2

c4

c4

[33] 4.2

c4

c4

18A

Relayed-Charge

7.2.12

n/a

c18

7.2.12

n/a

c18

19

Require

[26] 20.32

m

m

[26] 20.32

m

m

20

Server

[26] 20.35

o

o

[26] 20.35

o

o

20A

Session-ID

[162]

o

c17

[162]

o

c17

21

Timestamp

[26] 20.38

m

m

[26] 20.38

c2

c2

22

To

[26] 20.39

m

m

[26] 20.39

m

m

23

User-Agent

[26] 20.41

o

o

[26] 20.41

o

o

24

Via

[26] 20.42

m

m

[26] 20.42

m

m

25

Warning

[26] 20.43

o

o

[26] 20.43

o

o

c1: IF A.4/11 THEN o ELSE n/a – – insertion of date in requests and responses.

c2: IF A.4/6 THEN m ELSE n/a – – timestamping of requests.

c4: IF A.4/26 THEN o ELSE n/a – – a privacy mechanism for the Session Initiation Protocol (SIP).

c5: IF A.4/34 THEN o ELSE n/a – – the P-Access-Network-Info header extension.

c6: IF A.4/34 AND A.3/1 THEN m ELSE n/a – – the P-Access-Network-Info header extension and UE.

c7: IF A.4/34 AND (A.3/7A OR A.3/7D) THEN m ELSE n/a – – the P-Access-Network-Info header extension and AS acting as terminating UA or AS acting as third-party call controller.

c8: IF A.4/36 THEN o ELSE n/a – – the P-Charging-Vector header extension.

c9: IF A.4/36 THEN m ELSE n/a – – the P-Charging-Vector header extension.

c10: IF A.4/35 THEN o ELSE n/a – – the P-Charging-Function-Addresses header extension.

c11: IF A.4/35 THEN m ELSE n/a – – the P-Charging-Function-Addresses header extension.

c12: IF A.6/18 THEN m ELSE o – – 405 (Method Not Allowed).

c14: IF A.4/60 THEN m ELSE n/a – – SIP location conveyance.

c17: IF A.4/91 THEN m ELSE n/a – – the Session-ID header.

c18: IF A.4/111 THEN m ELSE n/a – – the Relayed-Charge header field extension.

c19: IF A.4/113 AND A.3/1 THEN m ELSE n/a – – the Cellular-Network-Info header extension and UE.

c20: IF A.4/113 AND (A.3/7A OR A.3/7D) THEN m ELSE n/a – – the Cellular-Network-Info header extension and AS acting as terminating UA or AS acting as third-party call controller.

c21: IF A.4/119 THEN o ELSE n/a – – Content-ID header field in Session Initiation Protocol (SIP).

c22: IF A.4/119 THEN m ELSE n/a – – Content-ID header field in Session Initiation Protocol (SIP).

Prerequisite A.5/7 – – INFO response

Prerequisite: A.6/102 – – Additional for 2xx response

Table A.36: Supported header fields within the INFO response

Item

Header field

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

1

Accept

[26] 20.1

o

o

[26] 20.1

m

m

2

Accept-Encoding

[26] 20.2

o

o

[26] 20.2

m

m

3

Accept-Language

[26] 20.3

o

o

[26] 20.3

m

m

4

Accept-Resource-Priority

[116] 3.2

c5

c5

[116] 3.2

c5

c5

5

Allow-Events

[28] 8.2.2

c3

c3

[28] 8.2.2

c4

c4

6

Authentication-Info

[26] 20.6

c1

c1

[26] 20.6

c2

c2

9

Supported

[26] 20.37

o

o

[26] 20.37

m

m

c1: IF A.4/7 THEN o ELSE n/a – – authentication between UA and UA.

c2: IF A.4/7 THEN m ELSE n/a – – authentication between UA and UA.

c3: IF A.4/22 THEN o ELSE n/a – – acting as the notifier of event information.

c4: IF A.4/23 THEN m ELSE n/a – – acting as the subscriber to event information.

c5: IF A.4/70A THEN m ELSE n/a – – inclusion of INFO, SUBSCRIBE, NOTIFY in communications resource priority for the session initiation protocol.

Prerequisite A.5/7 – – INFO response

Prerequisite: A.6/103 OR A.6/104 OR A.6/105 OR A.6/106 – – Additional for 3xx – 6xx response

Table A.37: Supported header fields within the INFO response

Item

Header field

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

1

Error-Info

[26] 20.18

o

o

[26] 20.18

o

o

2

Response-Source

7.2.17

n/a

c1

7.2.17

n/a

c1

c1: IF A.4/115 THEN o ELSE n/a – – use of the Response-Source header field in SIP error responses?

Prerequisite A.5/7 – – INFO response

Prerequisite: A.6/103 – – Additional for 3xx or 485 (Ambiguous) response

Table A.37A: Void

Prerequisite A.5/7 – – INFO response

Prerequisite: A.6/14 – – Additional for 401 (Unauthorized) response

Table A.38: Supported header fields within the INFO response

Item

Header field

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

3

Proxy-Authenticate

[26] 20.27

c1

c1

[26] 20.27

c1

c1

6

WWW-Authenticate

[26] 20.44

m

m

[26] 20.44

m

m

c1: IF A.4/7 THEN m ELSE n/a – – support of authentication between UA and UA.

Prerequisite A.5/7 – – INFO response

Prerequisite: A.6/17 OR A.6/23 OR A.6/30 OR A.6/36 OR A.6/42 OR A.6/45 OR A.6/50 OR A.6/51 – – Additional for 404 (Not Found), 413 (Request Entity Too Large), 480 (Temporarily not available), 486 (Busy Here), 500 (Internal Server Error), 503 (Service Unavailable), 600 (Busy Everywhere), 603 (Decline) response

Table A.39: Supported header fields within the INFO response

Item

Header field

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

4

Retry-After

[26] 20.33

o

o

[26] 20.33

o

o

Table A.40: Void

Prerequisite A.5/7 – – INFO response

Prerequisite: A.6/25 – – Additional for 415 (Unsupported Media Type) response

Table A.41: Supported header fields within the INFO response

Item

Header field

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

1

Accept

[26] 20.1

o.1

o.1

[26] 20.1

m

m

2

Accept-Encoding

[26] 20.2

o.1

o.1

[26] 20.2

m

m

3

Accept-Language

[26] 20.3

o.1

o.1

[26] 20.3

m

m

o.1 At least one of these capabilities is supported.

Prerequisite A.5/7 – – INFO response

Prerequisite: A.6/26A – – Additional for 417 (Unknown Resource-Priority) response

Table A.41A: Supported header fields within the INFO response

Item

Header field

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

1

Accept-Resource-Priority

[116] 3.2

c1

c1

[116] 3.2

c1

c1

c1: IF A.4/70A THEN m ELSE n/a – – inclusion of INFO, SUBSCRIBE, NOTIFY in communications resource priority for the session initiation protocol.

Prerequisite A.5/7 – – INFO response

Prerequisite: A.6/27 – – Additional for 420 (Bad Extension) response

Table A.42: Supported header fields within the INFO response

Item

Header field

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

5

Unsupported

[26] 20.40

m

m

[26] 20.40

m

m

Prerequisite A.5/7 – – INFO response

Prerequisite: A.6/28 OR A.6/41A – – Additional for 421 (Extension Required), 494 (Security Agreement Required) response

Table A.42A: Supported header fields within the INFO response

Item

Header field

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

3

Security-Server

[48] 2

x

x

[48] 2

c1

c1

c1: IF A.4/37 THEN m ELSE n/a – – security mechanism agreement for the session initiation protocol.

Table A.43: Void

Table A.44: Void

Prerequisite A.5/7 – – INFO response

Table A.45: Supported message bodies within the INFO response

Item

Header field

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

1

A.2.1.4.7 INVITE method

Prerequisite A.5/8 – – INVITE request

Table A.46: Supported header fields within the INVITE request

Item

Header field

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

1

Accept

[26] 20.1

o

c47

[26] 20.1

m

m

1A

Accept-Contact

[56B] 9.2

c24

c24

[56B] 9.2

c32

c32

2

Accept-Encoding

[26] 20.2

o

o

[26] 20.2

m

m

3

Accept-Language

[26] 20.3

o

o

[26] 20.3

m

m

3A

Additional-Identity

7.2.20

n/a

c75

7.2.20

n/a

c76

4

Alert-Info

[26] 20.4

o

o

[26] 20.4

c1

c1

5

Allow

[26] 20.5, [26] 5.1

o (note 1)

o

[26] 20.5, [26] 5.1

m

m

6

Allow-Events

[28] 8.2.2

c2

c2

[28] 8.2.2

c53

c53

6A

Attestation-Info

7.2.18

n/a

c71

7.2.18

n/a

c71

7

Answer-Mode

[158]

c49

c49

[158]

c50

c50

8

Authorization

[26] 20.7

c3

c3

[26] 20.7

c3

c3

9

Call-ID

[26] 20.8

m

m

[26] 20.8

m

m

10

Call-Info

[26] 20.9

o

o

[26] 20.9

o

o

10A

Cellular-Network-Info

7.2.15

n/a

c63

7.2.15

n/a

c64

11

Contact

[26] 20.10

m

m

[26] 20.10

m

m

12

Content-Disposition

[26] 20.11

o

o

[26] 20.11

m

m

13

Content-Encoding

[26] 20.12

o

o

[26] 20.12

m

m

13A

Content-ID

[256] 3.2

o

c69

[256] 3.2

m

c70

14

Content-Language

[26] 20.13

o

o

[26] 20.13

m

m

15

Content-Length

[26] 20.14

m

m

[26] 20.14

m

m

16

Content-Type

[26] 20.15

m

m

[26] 20.15

m

m

17

CSeq

[26] 20.16

m

m

[26] 20.16

m

m

18

Date

[26] 20.17

c4

c4

[26] 20.17

m

m

19

Expires

[26] 20.19

o

o

[26] 20.19

o

o

19A

Feature-Caps

[190]

c59

c59

[190]

c58

c58

20

From

[26] 20.20

m

m

[26] 20.20

m

m

20A

Geolocation

[89] 4.1

c33

c33

[89] 4.1

c33

c33

20B

Geolocation-Routing

[89] 4.2

c33

c33

[89] 4.2

c33

c33

20C

History-Info

[66] 4.1

c31

c31

[66] 4.1

c31

c31

20D

Identity

[252] 4

c68

c68

[252] 4

c68

c68

21

In-Reply-To

[26] 20.21

o

o

[26] 20.21

o

o

21A

Join

[61] 7.1

c30

c30

[61] 7.1

c30

c30

21B

Max-Breadth

[117] 5.8

n/a

c45

[117] 5.8

c46

c46

22

Max-Forwards

[26] 20.22

m

m

[26] 20.22

n/a

c52

23

MIME-Version

[26] 20.24

o

o

[26] 20.24

m

m

23A

Min-SE

[58] 5

c26

c26

[58] 5

c25

c25

24

Organization

[26] 20.25

o

o

[26] 20.25

o

o

24AA

Origination-Id

7.2.19

n/a

c72

7.2.19

n/a

c72

24A

P-Access-Network-Info

[52] 4.4, [234] 2

c15

c16

[52] 4.4, [234] 2

c15

c17

24B

P-Asserted-Identity

[34] 9.1

n/a

c65

[34] 9.1

c7

c7

24C

P-Asserted-Service

[121] 4.1

n/a

c67

[121] 4.1

c38

c38

24D

P-Called-Party-ID

[52] 4.2

x

x

[52] 4.2

c13

c13

24E

P-Charging-Function-Addresses

[52] 4.5

c20

c21

[52] 4.5

c20

c21

24F

P-Charging-Vector

[52] 4.6

c18

c19

[52] 4.6

c18

c19

24H

P-Early-Media

[109] 8

c34

c34

[109] 8

c34

c34

25

P-Media-Authorization

[31] 5.1

n/a

n/a

[31] 5.1

c11

c12

25A

P-Preferred-Identity

[34] 9.2

c7

c5

[34] 9.2

n/a

n/a

25B

P-Preferred-Service

[121] 4.2

c37

c36

[121] 4.2

n/a

n/a

25C

P-Private-Network-Indication

[134]

c42

c42

[134]

c42

c42

25D

P-Profile-Key

[97] 5

n/a

n/a

[97] 5

n/a

n/a

25E

P-Served-User

[133] 6

c51

c51

[133] 6

c51

c51

25F

P-User-Database

[82] 4

n/a

n/a

[82] 4

n/a

n/a

25G

P-Visited-Network-ID

[52] 4.3

x (note 3)

x

[52] 4.3

c14

n/a

26

Priority

[26] 20.26

o

o

[26] 20.26

o

o

26AA

Priority-Share

Subclause 7.2.16

n/a

c66

Subclause 7.2.16

n/a

c66

26AB

Priority-Verstat

Subclause 7.2.21

n/a

c77

Subclause 7.2.21

n/a

c78

26A

Privacy

[33] 4.2

c9

c9

[33] 4.2

c9

c9

26B

Priv-Answer-Mode

[158]

c49

c49

[158]

c50

c50

27

Proxy-Authorization

[26] 20.28

c6

c6

[26] 20.28

n/a

n/a

28

Proxy-Require

[26] 20.29

o (note 2)

o (note 2)

[26] 20.29

n/a

n/a

28A

Reason

[34A] 2

c8

c8

[34A] 2

c8

c55

29

Record-Route

[26] 20.30

n/a

c52

[26] 20.30

m

m

29A

Recv-Info

[25] 5.2.3

c48

c48

[25] 5.2.3

c48

c48

30

Referred-By

[59] 3

c27

c27

[59] 3

c28

c28

31

Reject-Contact

[56B] 9.2

c24

c24

[56B] 9.2

c32

c32

31A

Relayed-Charge

7.2.12

n/a

c61

7.2.12

n/a

c61

31B

Replaces

[60] 6.1

c29

c29

[60] 6.1

c29

c29

31C

Reply-To

[26] 20.31

o

o

[26] 20.31

o

o

31D

Request-Disposition

[56B] 9.1

c24

c24

[56B] 9.1

c32

c32

32

Require

[26] 20.32

m

m

[26] 20.32

m

m

32A

Resource-Priority

[116] 3.1

c35

c35

[116] 3.1

c35

c35

32B

Restoration-Info

Subclause 7.2.11

n/a

n/a

Subclause 7.2.11

n/a

c60

32C

Resource-Share

Subclause 7.2.13

n/a

c62

Subclause 7.2.13

n/a

c62

33

Route

[26] 20.34

m

m

[26] 20.34

n/a

c52

33A

Security-Client

[48] 2.3.1

c22

c22

[48] 2.3.1

n/a

n/a

33B

Security-Verify

[48] 2.3.1

c23

c23

[48] 2.3.1

n/a

n/a

33DA

Service-Interact-Info

Subclause 7.2.14

n/a

c73

Subclause 7.2.14

n/a

c74

33D

Session-Expires

[58] 4

c25

c25

[58] 4

c25

c25

33E

Session-ID

[162]

o

c54

[162]

o

c54

34

Subject

[26] 20.36

o

o

[26] 20.36

o

o

35

Supported

[26] 20.37

m

m

[26] 20.37

m

m

35A

Target-Dialog

[184] 7

c56

c56

[184] 7

c57

c57

36

Timestamp

[26] 20.38

c10

c10

[26] 20.38

m

m

37

To

[26] 20.39

m

m

[26] 20.39

m

m

37A

Trigger-Consent

[125] 5.11.2

c39

c39

[125] 5.11.2

c40

c40

38

User-Agent

[26] 20.41

o

o

[26] 20.41

o

o

38A

User-to-User

[126] 7

c41

c41

[126] 7

c41

c41

39

Via

[26] 20.42

m

m

[26] 20.42

m

m

c1: IF A.4/12 THEN m ELSE n/a – – downloading of alerting information.

c2: IF A.4/22 THEN m ELSE n/a – – acting as the notifier of event information.

c3: IF A.4/7 THEN m ELSE n/a – – authentication between UA and UA.

c4: IF A.4/11 THEN o ELSE n/a – – insertion of date in requests and responses.

c5: IF A.3/1 AND A.4/25 THEN o ELSE n/a – – UE and private extensions to the Session Initiation Protocol (SIP) for asserted identity within trusted networks.

c6: IF A.4/8A THEN m ELSE n/a – – authentication between UA and proxy.

c7: IF A.4/25 THEN o ELSE n/a – – private extensions to the Session Initiation Protocol (SIP) for asserted identity within trusted networks.

c8: IF A.4/38 THEN o ELSE n/a – – the Reason header field for the session initiation protocol.

c9: IF A.4/26 THEN o ELSE n/a – – a privacy mechanism for the Session Initiation Protocol (SIP).

c10: IF A.4/6 THEN o ELSE n/a – – timestamping of requests.

c11: IF A.4/19 THEN m ELSE n/a – – SIP extensions for media authorization.

c12: IF A.3/1 AND A.4/19 THEN m ELSE n/a – – UE, SIP extensions for media authorization.

c13: IF A.4/32 THEN o ELSE n/a – – the P-Called-Party-ID extension.

c14: IF A.4/33 THEN o ELSE n/a – – the P-Visited-Network-ID extension.

c15: IF A.4/34 THEN o ELSE n/a – – the P-Access-Network-Info header extension.

c16: IF A.4/34 AND (A.3/1 OR A.3/2A OR A.3/7 OR A.3A/81 OR A.3A/81A OR A.3A/81B OR A.3/6) THEN m ELSE n/a – – the P-Access-Network-Info header extension and UE, P-CSCF (IMS-ALG), the AS, the MSC server enhanced for ICS, MSC server enhanced for SRVCC using SIP interface, MSC server enhanced for DRVCC using SIP interface or MGCF.

c17: IF A.4/34 AND (A.3/2A OR A.3A/81 OR A.3/7A OR A.3/7D OR A3A/84 OR A.3/6) THEN m ELSE n/a – – the P-Access-Network-Info header extension and P-CSCF (IMS-ALG), the MSC server enhanced for ICS, AS acting as terminating UA, AS acting as third-party call controller, EATF or MGCF.

c18: IF A.4/36 THEN o ELSE n/a – – the P-Charging-Vector header extension.

c19: IF A.4/36 THEN m ELSE n/a – – the P-Charging-Vector header extension.

c20: IF A.4/35 THEN o ELSE n/a – – the P-Charging-Function-Addresses header extension.

c21: IF A.4/35 THEN m ELSE n/a – – the P-Charging-Function-Addresses header extension.

c22: IF A.4/37 OR A.4/37A THEN o ELSE n/a – – security mechanism agreement for the session initiation protocol or mediasec header field parameter for marking security mechanisms related to media (note 4).

c23: IF A.4/37 OR A.4/37A THEN m ELSE n/a – – security mechanism agreement for the session initiation protocol or mediasec header field parameter for marking security mechanisms related to media.

c24: IF A.4/40 THEN o ELSE n/a – – caller preferences for the session initiation protocol.

c25: IF A.4/42 THEN m ELSE n/a – – the SIP session timer.

c26: IF A.4/42 THEN o ELSE n/a – – the SIP session timer.

c27: IF A.4/43 THEN m ELSE n/a – – the SIP Referred-By mechanism.

c28: IF A.4/43 THEN o ELSE n/a – – the SIP Referred-By mechanism.

c29: IF A.4/44 THEN m ELSE n/a – – the Session Inititation Protocol (SIP) "Replaces" header.

c30: IF A.4/45 THEN m ELSE n/a – – the Session Inititation Protocol (SIP) "Join" header.

c31: IF A.4/47 THEN m ELSE n/a – – an extension to the session initiation protocol for request history information.

c32: IF A.4/40 THEN m ELSE n/a – – caller preferences for the session initiation protocol.

c33: IF A.4/60 THEN m ELSE n/a – – SIP location conveyance.

c34: IF A.4/66 THEN m ELSE n/a – – The SIP P-Early-Media private header extension for authorization of early media.

c35: IF A.4/70 THEN m ELSE n/a – – communications resource priority for the session initiation protocol.

c36: IF (A.3/1 OR A.3A/81 OR A.3A/81A OR A.3A/81B) AND A.4/74 THEN o ELSE n/a – – UE, MSC Server enhanced for ICS, MSC server enhanced for SRVCC using SIP interface, MSC server enhanced for DRVCC using SIP interface and SIP extension for the identification of services.

c37: IF A.4/74 THEN o ELSE n/a – – SIP extension for the identification of services.

c38: IF A.4/74 THEN m ELSE n/a – – SIP extension for the identification of services.

c39: IF A.4/75A THEN m ELSE n/a – – a relay within the framework for consent-based communications in SIP.

c40: IF A.4/75B THEN m ELSE n/a – – a recipient within the framework for consent-based communications in SIP.

c41: IF A.4/76 THEN o ELSE n/a – – transporting user to user information for call centers using SIP.

c42: IF A.4/77 THEN m ELSE n/a – – the SIP P-Private-Network-Indication private-header (P-Header).

c45: IF A.4/71 AND (A.3/9B OR A.3/9C OR A.3/13B OR A.3/13C) THEN m ELSE IF A.3/1 AND NOT A.3C/1 THEN n/a ELSE o – – addressing an amplification vulnerability in session initiation protocol forking proxies, IBCF (IMS-ALG), IBCF (Screening of SIP signalling), ISC gateway function (IMS-ALG), ISC gateway function (Screening of SIP signalling), UE, UE performing the functions of an external attached network.

c46: IF A.4/71 THEN m ELSE n/a – – addressing an amplification vulnerability in session initiation protocol forking proxies.

c47: IF A.3/1 AND A.4/2B THEN m ELSE o – – UE and initiating a session.

c48: IF A.4/13 THEN m ELSE IF A.4/13A THEN m ELSE n/a – – SIP INFO method and package framework, legacy INFO usage.

c49: IF A.4/87 THEN o ELSE n/a – – requesting answering modes for SIP.

c50: IF A.4/87 THEN m ELSE n/a – – requesting answering modes for SIP.

c51: IF A.4/78 THEN m ELSE n/a – – the SIP P-Served-User private header.

c52: IF A.3/1 AND NOT A.3C/1 THEN n/a ELSE o – – UE, UE performing the functions of an external attached network.

c53: IF A.4/23 THEN m ELSE n/a – – acting as the subscriber to event information.

c54: IF A.4/91 THEN m ELSE n/a – – the Session-ID header.

c55: IF A.4/38 THEN IF A.3A/83 THEN m ELSE o ELSE n/a – – the Reason header field for the session initiation protocol, SCC application server.

c56: IF A.4/99 THEN o ELSE n/a – – request authorization through dialog Identification in the session initiation protocol.

c57: IF A.4/99 THEN m ELSE n/a – – request authorization through dialog Identification in the session initiation protocol.

c58: IF A.4/100 THEN m ELSE n/a – – indication of features supported by proxy.

c59: IF A.4/100 AND A.3/1 AND NOT A.3C/1 THEN n/a ELSE IF A.4/100 THEN m ELSE n/a – – indication of features supported by proxy, UE, UE performing the functions of an external attached network.

c60: IF A. 4/109 THEN o ELSE n/a – – PCRF based P-CSCF restoration.

c61: IF A.4/111 THEN m ELSE n/a – – the Relayed-Charge header field extension.

c62: IF A.4/112 THEN o ELSE n/a – – resource sharing.

c63: IF A.4/113 AND (A.3/1 OR A.3/2A OR A.3/7) THEN m ELSE n/a – – the Cellular-Network-Info header extension and UE, P-CSCF (IMS-ALG) or the AS.

c64: IF A.4/113 AND (A.3/2A OR A.3/7A OR A.3/7D OR A3A/84) THEN m ELSE IF A.4/113 AND A.3/6 THEN o ELSE n/a – – the Cellular-Network-Info header extension and P-CSCF (IMS-ALG), AS acting as terminating UA or AS acting as third-party call controller, EATF or MGCF.

c65: IF A.4/25 AND (A.3/6 OR A.3/7B OR A.3/8 OR A.3A/81 OR A.3A/81A OR A.3A/81B OR A.3A/83 OR A.3A/89) THEN o ELSE n/a – – private extensions to the Session Initiation Protocol (SIP) for asserted identity within trusted networks and MGCF, AS acting as originating UA, MRFC, MSC Server enhanced for ICS, MSC server enhanced for SRVCC using SIP interface, MSC server enhanced for DRVCC using SIP interface, SCC application server, ATCF (UA).

c66: IF A.4/114 THEN o ELSE n/a – – priority sharing.

c67: IF A.4/74 AND A.3/7B THEN o ELSE n/a – – SIP extension for the identification of services and AS acting as originating UA.

c68: IF A.4/116 AND (A.3/7 OR A.3/9) THEN m ELSE n/a – – authenticated identity management in the Session Initiation Protocol, AS, IBCF.

c69: IF A.4/119 THEN o ELSE n/a – – Content-ID header field in Session Initiation Protocol (SIP).

c70: IF A.4/119 THEN m ELSE n/a – – Content-ID header field in Session Initiation Protocol (SIP).

c71: IF A.4/121 AND (A.3/6 OR A.3/7 OR A.3/9) THEN m ELSE n/a – – the Attestation-Info header field extension, MGCF, AS, IBCF.

c72: IF A.4/122 AND (A.3/6 OR A.3/7 OR A.3/9) THEN m ELSE n/a – – the Origination-Id header field extension, MGCF, AS, IBCF.

c73: IF A.4/123 AND (A.3/7 OR A.3/9) THEN m ELSE n/a – – Dynamic services interactions, AS, IBCF.

c74: IF A.4/123 AND (A.3/2 OR A.3/7 OR A.3/9) THEN m ELSE n/a – – Dynamic services interactions, P-CSCF, AS, IBCF.

c75: IF A.4/124 THEN o ELSE n/a – – the Additional-Identity header field extension.

c76: IF A.4/124 THEN m ELSE n/a – – the Additional-Identity header field extension.

c77: IF A.4/70 AND A.4/126 AND A.3/9 THEN m ELSE n/a – – communications resource priority for the session initiation protocol, the Priority-Verstat header field extension, IBCF.

c78: IF A.4/70 AND A.4/126 THEN o ELSE n/a – – communications resource priority for the session initiation protocol, the Priority-Verstat header field extension.

o.1: At least one of these shall be supported.

NOTE 1: RFC 3261 [26] gives the status of this header as SHOULD rather than OPTIONAL.

NOTE 2: No distinction has been made in these tables between first use of a request on a From/To/Call-ID combination, and the usage in a subsequent one. Therefore the use of "o" etc. above has been included from a viewpoint of first usage.

NOTE 3: The strength of this requirement in RFC 7315 [52] is SHOULD NOT, rather than MUST NOT.

NOTE 4: Support of this header in this method is dependent on the security mechanism and the security architecture which is implemented. Use of this header in this method is not appropriate to the security mechanism defined by 3GPP TS 33.203 [19].

Prerequisite A.5/8 – – INVITE request

Table A.47: Supported message bodies within the INVITE request

Item

Header

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

1

XML Schema for PSTN

[11B]

c1

[11B]

c1

2

application/vnd.3gpp.ussd

[8W]

c2

[8W]

c3

3

application/vnd.3gpp.mcptt-info+xml

[8ZE]

n/a

c4

[8ZE]

n/a

c4

4

application/vnd.etsi.aoc+xml

[8N] 4.7.2

n/a

c5

[8N] 4.7.2

n/a

c6

5

application/EmergencyCallData.eCall.MSD

[244] 14.3

m

c7

[244] 14.3

m

c8

c1: IF A.3/6 OR A.3/7A OR A.3/7B OR A.3/7D OR A.3/9B OR A.3/13B THEN o ELSE n/a – – MGCF, AS acting as terminating UA, or redirect server, AS acting as originating UA, AS performing 3rd party call control, IBCF (IMS-ALG), ISC gateway function (IMS-ALG).

c2: IF A.3A/92A OR A.3A/93B OR A.3/9 OR A.3/2 OR A.3A/89 THEN m ELSE n/a – – USSI UE supporting user-initiated USSD operations, USSI AS supporting network-initiated USSD operations, IBCF, P-CSCF, ATCF (UA).

c3: IF A.3A/93A OR A.3A/92B OR A.3/9 OR A.3/2 OR A.3A/89 THEN m ELSE n/a – – USSI AS supporting user-initiated USSD operations, USSI UE supporting network-initiated USSD operations, IBCF, P-CSCF, ATCF (UA).

c4: IF A.3A/102 OR A.3A/103 THEN m ELSE n/a – – MCPTT client, MCPTT server.

c5 IF A.3A/53 THEN m ELSE n/a – – Advice of charge application server.

c6 IF A.3A/54 THEN m ELSE n/a – – Advice of charge UA client.

c7: IF (A.3/1 AND A.4/120) THEN m ELSE IF ((A.3/2A OR A.3/11A OR A.3A/84) AND A.4/120) THEN i ELSE n/a – – UE, Next-Generation Pan-European eCall emergency service, P-CSCF (IMS-ALG), E-CSCF acting as UA, EATF.

c8: IF ((A.3/2A OR A.3/11A OR A.3A/84 OR A.3/12) AND A.4/120) THEN i ELSE n/a – – P-CSCF (IMS-ALG), E-CSCF acting as UA, EATF, LRF, Next-Generation Pan-European eCall emergency service.

Prerequisite A.5/9 – – INVITE response

Prerequisite: A.6/1 – – Additional for 100 (Trying) response

Table A.48: Supported header fields within the INVITE response

Item

Header field

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

1

Call-ID

[26] 20.8

m

m

[26] 20.8

m

m

2

Content-Length

[26] 20.14

m

m

[26] 20.14

m

m

3

CSeq

[26] 20.16

m

m

[26] 20.16

m

m

4

Date

[26] 20.17

c1

c1

[26] 20.17

m

m

5

From

[26] 20.20

m

m

[26] 20.20

m

m

6

To

[26] 20.39

m

m

[26] 20.39

m

m

7

Via

[26] 20.42

m

m

[26] 20.42

m

m

c1: IF A.4/11 THEN o ELSE n/a – – insertion of date in requests and responses.

Prerequisite A.5/9 – – INVITE response for all remaining status-codes

Table A.49: Supported header fields within the INVITE response

Item

Header field

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

0A

Allow

[26] 20.5

c12

c12

[26] 20.5

m

m

1

Call-ID

[26] 20.8

m

m

[26] 20.8

m

m

1A

Call-Info

[26] 20.9

o

o

[26] 20.9

o

o

1B

Cellular-Network-Info

7.2.15

n/a

c20

7.2.15

n/a

c21

2

Content-Disposition

[26] 20.11

o

o

[26] 20.11

m

m

3

Content-Encoding

[26] 20.12

o

o

[26] 20.12

m

m

3A

Content-ID

[256] 3.2

o

c23

[256] 3.2

m

c24

4

Content-Language

[26] 20.13

o

o

[26] 20.13

m

m

5

Content-Length

[26] 20.14

m

m

[26] 20.14

m

m

6

Content-Type

[26] 20.15

m

m

[26] 20.15

m

m

7

CSeq

[26] 20.16

m

m

[26] 20.16

m

m

8

Date

[26] 20.17

c1

c1

[26] 20.17

m

m

Expires

[26] 20.19

o

o

[26] 20.19

o

o

9

From

[26] 20.20

m

m

[26] 20.20

m

m

9A

Geolocation-Error

[89] 4.3

c14

c14

[89] 4.3

c14

c14

9B

History-Info

[66] 4.1

c13

c13

[66] 4.1

c13

c13

10

MIME-Version

[26] 20.24

o

o

[26] 20.24

m

m

11

Organization

[26] 20.25

o

o

[26] 20.25

o

o

11A

P-Access-Network-Info

[52] 4.4, [52A] 4, [234] 2

c5

c6

[52] 4.4, [52A] 4, [234] 2

c5

c7

11B

P-Asserted-Identity

[34] 9.1

n/a

c22

[34] 9.1

c3

c3

11C

P-Charging-Function-Addresses

[52] 4.5, [52A] 4

c10

c11

[52] 4.5, [52A] 4

c11

c11

11D

P-Charging-Vector

[52] 4.6, [52A] 4

c8

c9

[52] 4.6, [52A] 4

c8

c9

11F

P-Preferred-Identity

[34] 9.2

c3

x

[34] 9.2

n/a

n/a

11G

Privacy

[33] 4.2

c4

c4

[33] 4.2

c4

c4

11H

Relayed-Charge

7.2.12

n/a

c19

7.2.12

n/a

c19

11I

Reply-To

[26] 20.31

o

o

[26] 20.31

o

o

11J

Require

[26] 20.32

m

m

[26] 20.32

m

m

11K

Server

[26] 20.35

o

o

[26] 20.35

o

o

11LA

Service-Interact-Info

Subclause 7.2.14

n/a

c25

Subclause 7.2.14

n/a

c26

11L

Session-ID

[162]

o

c18

[162]

o

c18

12

Timestamp

[26] 20.38

m

m

[26] 20.38

c2

c2

13

To

[26] 20.39

m

m

[26] 20.39

m

m

13A

User-Agent

[26] 20.41

o

o

[26] 20.41

o

o

13B

User-to-User

[126] 7

c15

c15

[126] 7

c15

c15

14

Via

[26] 20.42

m

m

[26] 20.42

m

m

15

Warning

[26] 20.43

o (note)

o

[26] 20.43

o

o

c1: IF A.4/11 THEN o ELSE n/a – – insertion of date in requests and responses.

c2: IF A.4/6 THEN m ELSE n/a – – timestamping of requests.

c3: IF A.4/25 THEN o ELSE n/a – – private extensions to the Session Initiation Protocol (SIP) for asserted identity within trusted networks.

c4: IF A.4/26 THEN o ELSE n/a – – a privacy mechanism for the Session Initiation Protocol (SIP).

c5: IF A.4/34 THEN o ELSE n/a – – the P-Access-Network-Info header extension.

c6: IF A.4/34 AND (A.3/1 OR A.3/2A OR A.3/7 OR A.3A/81 OR A.3/81A OR A.3A/81B) THEN m ELSE n/a – – the P-Access-Network-Info header extension and UE, P-CSCF (IMS-ALG), AS or MSC server enhanced for ICS or MSC Server enhanced for SRVCC using SIP interface, MSC server enhanced for DRVCC using SIP interface.

c7: IF A.4/34 AND (A.3/2A OR A.3A/81 OR A.3/7A OR A.3/7D OR A3A/84) THEN m ELSE n/a – – the P-Access-Network-Info header extension and P-CSCF (IMS-ALG), MSC server enhanced for ICS, AS acting as terminating UA, AS acting as third-party call controller or EATF.

c8: IF A.4/36 THEN o ELSE n/a – – the P-Charging-Vector header extension.

c9: IF A.4/36 THEN m ELSE n/a – – the P-Charging-Vector header extension.

c10: IF A.4/35 THEN o ELSE n/a – – the P-Charging-Function-Addresses header extension.

c11: IF A.4/35 THEN m ELSE n/a – – the P-Charging-Function-Addresses header extension.

c12: IF A.6/102 OR A.6/18 THEN m ELSE o – – 2xx response, 405 (Method Not Allowed).

c13: IF A.4/47 THEN m ELSE n/a – – an extension to the session initiation protocol for request history information.

c14: IF A.4/60 THEN m ELSE n/a – – SIP location conveyance.

c15: IF A.4/76 THEN o ELSE n/a – – transporting user to user information for call centers using SIP.

c18: IF A.4/91 THEN m ELSE n/a – – the Session-ID header.

c19: IF A.4/111 THEN m ELSE n/a – – the Relayed-Charge header field extension.

c20: IF A.4/113 AND (A.3/1 OR A.3/2A OR A.3/7) THEN m ELSE n/a – – the Cellular-Network-Info header extension and UE, P-CSCF (IMS-ALG) or AS.

c21: IF A.4/113 AND (A.3/2A OR A.3/7A OR A.3/7D OR A3A/84) THEN m ELSE n/a – – the Cellular-Network-Info header extension and P-CSCF (IMS-ALG), AS acting as terminating UA, AS acting as third-party call controller or EATF.

c22: IF A.4/25 AND (A.3/6 OR A.3/7B OR A.3/8 OR A.3A/81 OR A.3A/81A OR A.3A/81B OR A.3A/83 OR A.3A/89) THEN o ELSE n/a – – private extensions to the Session Initiation Protocol (SIP) for asserted identity within trusted networks and MGCF, AS acting as originating UA, MRFC, MSC Server enhanced for ICS, MSC server enhanced for SRVCC using SIP interface, MSC server enhanced for DRVCC using SIP interface, SCC application server, ATCF (UA).

c23: IF A.4/119 THEN o ELSE n/a – – Content-ID header field in Session Initiation Protocol (SIP).

c24: IF A.4/119 THEN m ELSE n/a – – Content-ID header field in Session Initiation Protocol (SIP).

c25: IF A.4/123 AND (A.3/7 OR A.3/9) THEN m ELSE n/a – – Dynamic services interactions, AS, IBCF.

c26: IF A.4/123 AND (A.3/2 OR A.3/7 OR A.3/9) THEN m ELSE n/a – – Dynamic services interactions, P-CSCF, AS, IBCF.

NOTE: For a 488 (Not Acceptable Here) response, RFC 3261 [26] gives the status of this header as SHOULD rather than OPTIONAL.

Prerequisite A.5/9 – – INVITE response

Prerequisite: A.6/101A – – Additional for 18x response

Table A.50: Supported header fields within the INVITE response

Item

Header field

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

4

Contact

[26] 20.10

o

m

[26] 20.10

m

m

4A

Feature-Caps

[190]

c17

c17

[190]

c16

c16

5

P-Answer-State

[111]

c13

c13

[111]

c13

c13

5A

P-Early-Media

[109] 8

c14

c14

[109] 8

c14

c14

6

P-Media-Authorization

[31] 5.1

n/a

n/a

[31] 5.1

c11

c12

6AA

Priority-Share

Subclause 7.2.16

n/a

c19

Subclause 7.2.16

n/a

c19

6A

Reason

[130], [294]

o

c15

[130], [294]

o

c15

7

Record-Route

[26] 20.30

o

m

[26] 20.30

m

m

8

Recv-Info

[25] 5.2.3

c4

c4

[25] 5.2.3

c4

c4

8A

Resource-Share

Subclause 7.2.13

n/a

c18

Subclause 7.2.13

n/a

c18

9

RSeq

[27] 7.1

c2

m

[27] 7.1

c3

m

c2: IF A.4/14 THEN o ELSE n/a – – reliability of provisional responses in SIP.

c3: IF A.4/14 THEN m ELSE n/a – – reliability of provisional responses in SIP.

c4: IF A.4/13 THEN m ELSE IF A.4/13A THEN m ELSE n/a – – SIP INFO method and package framework, legacy INFO usage.

c11: IF A.4/19 THEN m ELSE n/a – – SIP extensions for media authorization.

c12: IF A.3/1 AND A.4/19 THEN m ELSE n/a – – UE, SIP extensions for media authorization.

c13: IF A.4/65 THEN m ELSE n/a – – the P-Answer-State header extension to the session initiation protocol for the open mobile alliance push to talk over cellular.

c14: IF A.4/66 THEN m ELSE n/a – – the SIP P-Early-Media private header extension for authorization of early media.

c15: IF A.4/38A OR A.4/38C THEN o ELSE n/a – – use of the Reason header field in Session Initiation Protocol (SIP) responses (carrying Q.850 or STIR codes).

c16: IF A.4/100 THEN m ELSE n/a – – indication of features supported by proxy.

c17: IF A.4/100 AND A.3/1 AND NOT A.3C/1 THEN n/a ELSE IF A.4/100 THEN m ELSE n/a – – indication of features supported by proxy, UE, UE performing the functions of an external attached network.

c18: IF A.4/112 THEN o ELSE n/a – – resource sharing.

c19: IF A.4/114THEN o ELSE n/a – – priority sharing.

Prerequisite A.5/9 – – INVITE response

Prerequisite: A.6/2 – – Additional for 180 (Ringing) response

Table A.50A: Supported header fields within the INVITE response

Item

Header field

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

1

Alert-Info

[26] 20.4

o

c1

[26] 20.4

o

c1

c1: IF A.4/96 THEN m ELSE o – – Alert-Info URNs for the Session Initiation Protocol.

Prerequisite A.5/9 – – INVITE response

Prerequisite: A.6/5A – – Additional for 199 (Early Dialog Terminated) response

Table A.50B: Supported header fields within the INVITE response

Item

Header field

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

4

Contact

[26] 20.10

o

m

[26] 20.10

m

m

5

Reason

[130], [294]

o

c5

[130], [294]

o

c5

7

Record-Route

[26] 20.30

o

m

[26] 20.30

m

m

8

Recv-Info

[25] 5.2.3

c4

c4

[25] 5.2.3

c4

c4

9

RSeq

[27] 7.1

c2

m

[27] 7.1

c3

m

c2: IF A.4/14 THEN o ELSE n/a – – reliability of provisional responses in SIP.

c3: IF A.4/14 THEN m ELSE n/a – – reliability of provisional responses in SIP.

c4: IF A.4/13 THEN m ELSE IF A.4/13A THEN m ELSE n/a – – SIP INFO method and package framework, legacy INFO usage.

c5: IF A.4/38A OR A.4/38C THEN o ELSE n/a – – use of the Reason header field in Session Initiation Protocol (SIP) responses (carrying Q.850 or STIR codes).

Prerequisite A.5/9 – – INVITE response

Prerequisite: A.6/102 – – Additional for 2xx response

Table A.51: Supported header fields within the INVITE response

Item

Header field

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

1

Accept

[26] 20.1

o

o

[26] 20.1

m

m

1A

Accept-Encoding

[26] 20.2

o

o

[26] 20.2

m

m

1B

Accept-Language

[26] 20.3

o

o

[26] 20.3

m

m

1C

Accept-Resource-Priority

[116] 3.2

c15

c15

[116] 3.2

c15

c15

2

Allow-Events

[28] 8.2.2

c3

c3

[28] 8.2.2

c4

c4

3

Answer-Mode

[158]

c6

c6

[158]

c7

c7

4

Authentication-Info

[26] 20.6

c1

c1

[26] 20.6

c2

c2

6

Contact

[26] 20.10

m

m

[26] 20.10

m

m

6A

Feature-Caps

[190]

c18

c18

[190]

c17

c17

7

P-Answer-State

[111]

c14

c14

[111]

c14

c14

8

P-Media-Authorization

[31] 5.1

n/a

n/a

[31] 5.1

c11

c12

8AA

Priority-Share

Subclause 7.2.16

n/a

c20

Subclause 7.2.16

n/a

c20

8A

Priv-Answer-Mode

[158]

c6

c6

[158]

c7

c7

8B

Reason

[294]

o

c21

[294]

o

c21

9

Record-Route

[26] 20.30

m

m

[26] 20.30

m

m

9A

Recv-Info

[25] 5.2.3

c5

c5

[25] 5.2.3

c5

c5

9B

Resource-Share

Subclause 7.2.13

n/a

c19

Subclause 7.2.13

n/a

c19

10

Session-Expires

[58] 4

c13

c13

[58] 4

c13

c13

13

Supported

[26] 20.37

m

m

[26] 20.37

m

m

c1: IF A.4/7 THEN o ELSE n/a – – authentication between UA and UA.

c2: IF A.4/7 THEN m ELSE n/a – – authentication between UA and UA.

c3: IF A.4/22 THEN o ELSE n/a – – acting as the notifier of event information.

c4: IF A.4/23 THEN m ELSE n/a – – acting as the subscriber to event information.

c5: IF A.4/13 THEN m ELSE IF A.4/13A THEN m ELSE n/a – – SIP INFO method and package framework, legacy INFO usage.

c6 IF A.4/87 THEN o ELSE n/a – – requesting answering modes for SIP.

c7 IF A.4/87 THEN m ELSE n/a – – requesting answering modes for SIP.

c11: IF A.4/19 THEN m ELSE n/a – – SIP extensions for media authorization.

c12: IF A.3/1 AND A.4/19 THEN m ELSE n/a – – UE, SIP extensions for media authorization.

c13: IF A.4/42 THEN m ELSE n/a – – the SIP session timer.

c14: IF A.4/65 THEN m ELSE n/a – – the P-Answer-State header extension to the session initiation protocol for the open mobile alliance push to talk over cellular.

c15: IF A.4/70 THEN m ELSE n/a – – communications resource priority for the session initiation protocol.

c17: IF A.4/100 THEN m ELSE n/a – – indication of features supported by proxy.

c18: IF A.4/100 AND A.3/1 AND NOT A.3C/1 THEN n/a ELSE IF A.4/100 THEN m ELSE n/a – – indication of features supported by proxy, UE, UE performing the functions of an external attached network.

c19: IF A.4/112 THEN m ELSE n/a – – resource sharing.

c20: IF A.4/114THEN o ELSE n/a – – priority sharing.

c21: IF A.4/38C THEN o ELSE n/a – – use of the Reason header field in Session Initiation Protocol (SIP) responses (carrying STIR codes).

Prerequisite A.5/9 – – INVITE response

Prerequisite: A.6/103 OR A.6/104 OR A.6/105 OR A.6/106 – – Additional for 3xx – 6xx response

Table A.51A: Supported header fields within the INVITE response

Item

Header field

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

1

Error-Info

[26] 20.18

o

o

[26] 20.18

o

o

2

Reason

[130], [294]

o

c1

[130], [294]

o

c1

3

Response-Source

7.2.17

n/a

c2

7.2.17

n/a

c2

c1: IF A.4/38A OR A.4/38C THEN o ELSE n/a – – use of the Reason header field in Session Initiation Protocol (SIP) responses (carrying Q.850 or STIR codes).

c2: IF A.4/115 THEN o ELSE n/a – – use of the Response-Source header field in SIP error responses?

Prerequisite A.5/9 – – INVITE response

Prerequisite: A.6/103 OR A.6/35 – – Additional for 3xx or 485 (Ambiguous) response

Table A.52: Supported header fields within the INVITE response

Item

Header field

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

4

Contact

[26] 20.10

o (note 1)

o

[26] 20.10

m

m

NOTE: The strength of this requirement is RECOMMENDED rather than OPTIONAL.

Prerequisite A.5/9 – – INVITE response

Prerequisite: A.6/14 – – Additional for 401 (Unauthorized) response

Table A.53: Supported header fields within the INVITE response

Item

Header field

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

6

Proxy-Authenticate

[26] 20.27

c3

c3

[26] 20.27

c3

c3

13

WWW-Authenticate

[26] 20.44

m

m

[26] 20.44

m

m

c1: IF A.4/11 THEN o ELSE n/a – – insertion of date in requests and responses.

c2: IF A.4/6 THEN m ELSE n/a – – timestamping of requests.

c3: IF A.4/7 THEN m ELSE n/a – – support of authentication between UA and UA.

Prerequisite A.5/9 – – INVITE response

Prerequisite: A.6/16 – – Additional for 403 (Forbidden) response

Table A.53A: Supported header fields within the INVITE response

Item

Header field

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

1

P-Refused-URI-List

[183]

c1

c1

[183]

c1

c1

c1: IF A.4/98 THEN m ELSE n/a — The SIP P-Refused-URI-List private-header.

Prerequisite A.5/9 – – INVITE response

Prerequisite: A.6/17 OR A.6/23 OR A.6/30 OR A.6/36 OR A.6/50 OR A.6/51 – – Additional for 404 (Not Found), 413 (Request Entity Too Large), 480(Temporarily not available), 486 (Busy Here), 500 (Internal Server Error), 600 (Busy Everywhere), 603 (Decline) response

Table A.54: Supported header fields within the INVITE response

Item

Header field

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

8

Retry-After

[26] 20.33

o

o

[26] 20.33

o

o

Table A.55: Void

Prerequisite A.5/9 – – INVITE response

Prerequisite: A.6/20 – – Additional for 407 (Proxy Authentication Required) response

Table A.56: Supported header fields within the INVITE response

Item

Header field

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

6

Proxy-Authenticate

[26] 20.27

c1

c1

[26] 20.27

c1

c1

11

WWW-Authenticate

[26] 20.44

o

o

[26] 20.44

o

o

c1: IF A.4/7 THEN m ELSE n/a – – support of authentication between UA and UA.

Prerequisite A.5/9 – – INVITE response

Prerequisite: A.6/21 – – Additional for 408 (Request timeout) response

Table A.56A: Supported header fields within the INVITE response

Item

Header field

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

1

Restoration-Info

subclause 7.2.11

n/a

c1

subclause 7.2.11

n/a

n/a

c1: IF A.4/110 THEN o ELSE n/a – – HSS based P-CSCF restoration.

Prerequisite A.5/9 – – INVITE response

Prerequisite: A.6/25 – – Additional for 415 (Unsupported Media Type) response

Table A.57: Supported header fields within the INVITE response

Item

Header field

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

1

Accept

[26] 20.1

o.1

o.1

[26] 20.1

m

m

2

Accept-Encoding

[26] 20.2

o.1

o.1

[26] 20.2

m

m

3

Accept-Language

[26] 20.3

o.1

o.1

[26] 20.3

m

m

o.1 At least one of these capabilities is supported.

Prerequisite A.5/9 – – INVITE response

Prerequisite: A.6/26A – – Additional for 417 (Unknown Resource-Priority) response

Table A.57A: Supported header fields within the INVITE response

Item

Header field

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

1

Accept-Resource-Priority

[116] 3.2

c1

c1

[116] 3.2

c1

c1

c1: IF A.4/70 THEN m ELSE n/a – – communications resource priority for the session initiation protocol.

Prerequisite A.5/9 – – INVITE response

Prerequisite: A.6/27 – – Additional for 420 (Bad Extension) response

Table A.58: Supported header fields within the INVITE response

Item

Header field

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

10

Unsupported

[26] 20.40

m

m

[26] 20.40

m

m

Prerequisite A.5/9 – – INVITE response

Prerequisite: A.6/28 OR A.6/41A – – Additional for 421 (Extension Required), 494 (Security Agreement Required) response

Table A.58A: Supported header fields within the INVITE response

Item

Header field

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

3

Security-Server

[48] 2

x

x

[48] 2

c1

c1

c1: IF A.4/37 THEN m ELSE n/a – – security mechanism agreement for the session initiation protocol.

Prerequisite A.5/9 – – INVITE response

Prerequisite: A.6/28A – – Additional for 422 (Session Interval Too Small) response

Table A.58B: Supported header fields within the INVITE response

Item

Header field

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

1

Min-SE

[58] 5

c1

c1

[58] 5

c1

c1

c1: IF A.4/42 THEN o ELSE n/a – – the SIP session timer.

Table A.59: Void

Table A.60: Void

Prerequisite A.5/9 – – INVITE response

Prerequisite: A.6/29H – – Additional for 470 (Consent Needed) response

Table A.60A: Supported header fields within the INVITE response

Item

Header field

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

1

Permission-Missing

[125] 5.9.3

m

m

[125] 5.9.3

m

m

Prerequisite A.5/9 – – INVITE response

Prerequisite: A.6/45 – – 503 (Service Unavailable)

Table A.61: Supported header fields within the INVITE response

Item

Header field

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

8

Retry-After

[26] 20.33

o

o

[26] 20.33

o

m

Table A.61A: Void

Prerequisite A.5/9 – – INVITE response

Table A.62: Supported message bodies within the INVITE response

Item

Header

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

1

XML Schema for PSTN

[11B]

c1

[11B]

c1

2

Recipient list

[183]

c2

c2

[183]

c2

c2

3

3GPP IM CN subsystem XML body

subclause 7.6

n/a

c3

subclause 7.6

n/a

c4 (note)

4

application/vnd.3gpp.mcptt-info+xml

[8ZE]

n/a

c5

[8ZE]

n/a

c5

5

application/vnd.etsi.aoc+xml

[8N] 4.7.2

n/a

c6

[8N] 4.7.2

n/a

c7

6

application/EmergencyCallData.Control+xml

[244] 14.4

m

c8

[244] 14.4

m

c9

c1: IF A.3/6 OR A.3/7A OR A.3/7B OR A.3/7D OR A.3/9B OR A.3/13B THEN o ELSE n/a – – MGCF, AS acting as terminating UA, or redirect server, AS acting as originating UA, AS performing 3rd party call control, IBCF (IMS-ALG), ISC gateway function (IMS-ALG).

c2: IF A.3/9B OR A.3/13B THEN m ELSE IF A.3/7A OR A.3/7B OR A.3/7D THEN o ELSE n/a – – IBCF (IMS-ALG), ISC gateway function (IMS-ALG), AS acting as terminating UA, AS acting as originating UA, AS performing 3rd party call control.

c3: IF A.3/9B OR A.3/9C OR A.3/13B OR A.3/13C OR (A.4/103 AND A.3/2) OR (A.4/103 AND A.3/4) THEN m ELSE n/a – – IBCF (IMS-ALG), IBCF (Screening of SIP signalling), ISC gateway function (IMS-ALG), ISC gateway function (Screening of SIP signalling), S-CSCF restoration procedures, P-CSCF, S-CSCF.

c4: IF A.3/1 OR A.3/2 OR A.3/9B OR A.3/9C OR A.3/13B OR A.3/13C THEN m ELSE IF A.3/4 THEN o ELSE n/a – – UE, P-CSCF, IBCF (IMS-ALG), IBCF (Screening of SIP signalling), ISC gateway function (IMS-ALG), S-CSCF.

c5: IF A.3A/102 OR A.3A/103 THEN M ELSE n/a – – MCPTT client, MCPTT server.

c6 IF A.3A/53 THEN m ELSE n/a – – Advice of charge application server.

c7 IF A.3A/54 THEN m ELSE n/a – – Advice of charge UA client.

c8: IF ((A.3/2A OR A.3/11A OR A.3A/84) AND A.4/120) THEN i ELSE n/a – – P-CSCF (IMS-ALG), E-CSCF acting as UA, EATF, Next-Generation Pan-European eCall emergency service.

c9: IF (A.3/1 AND A.4/120) THEN m ELSE IF ((A.3/2A OR A.3/11A OR A.3A/84) AND A.4/120) THEN i ELSE n/a – – UE, Next-Generation Pan-European eCall emergency service, P-CSCF (IMS-ALG), E-CSCF acting as UA, EATF.

NOTE: If a IBCF (IMS-ALG) or a IBCF (Screening of SIP signalling) is unable to receive a 3GPP IM CN subsystem XML body from a S-CSCF in a serving network then the IBCF (IMS-ALG) or the IBCF (Screening of SIP signalling) support can be "o" instead of "m". Examples include an S-CSCF supporting S-CSCF restoration procedures.

A.2.1.4.7A MESSAGE method

Prerequisite A.5/9A – – MESSAGE request

Table A.62A: Supported header fields within the MESSAGE request

Item

Header field

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

1

Accept-Contact

[56B] 9.2

c24

c24

[56B] 9.2

c28

c28

1AA

Additional-Identity

7.2.20

n/a

c58

7.2.20

n/a

c59

1A

Allow

[26] 20.5

o

o

[26] 20.5

m

m

2

Allow-Events

[28] 8.2.2

c1

c1

[28] 8.2.2

c2

c2

2A

Attestation-Info

7.2.18

n/a

c54

7.2.18

n/a

c54

3

Authorization

[26] 20.7

c3

c3

[26] 20.7

c3

c3

4

Call-ID

[26] 20.8

m

m

[26] 20.8

m

m

5

Call-Info

[26] 20.9

o

o

[26] 20.9

o

o

5A

Cellular-Network-Info

7.2.15

n/a

c47

7.2.15

n/a

c48

6

Content-Disposition

[26] 20.11

o

o

[26] 20.11

m

m

7

Content-Encoding

[26] 20.12

o

o

[26] 20.12

m

m

7A

Content-ID

[256] 3.2

o

c52

[256] 3.2

m

c53

8

Content-Language

[26] 20.13

o

o

[26] 20.13

m

m

9

Content-Length

[26] 20.14

m

m

[26] 20.14

m

m

10

Content-Type

[26] 20.15

m

m

[26] 29.15

m

m

11

CSeq

[26] 20.16

m

m

[26] 20.16

m

m

12

Date

[26] 20.17

c4

c4

[26] 20.17

m

m

13

Expires

[26] 20.19

o

o

[26] 20.19

o

o

13A

Feature-Caps

[190]

c45

c45

[190]

c44

c44

14

From

[26] 20.20

m

m

[26] 20.20

m

m

14A

Geolocation

[89] 4.1

c29

c29

[89] 4.1

c29

c29

14B

Geolocation-Routing

[89] 4.2

c29

c29

[89] 4.2

c29

c29

14C

History-Info

[66] 4.1

c27

c27

[66] 4.1

c27

c27

14D

Identity

[252] 4

c51

c51

[252] 4

c51

c51

15

In-Reply-To

[26] 20.21

o

o

[26] 20.21

o

o

15A

Max-Breadth

[117] 5.8

n/a

c39

[117] 5.8

c40

c40

16

Max-Forwards

[26] 20.22

m

m

[26] 20.22

n/a

c42

17

MIME-Version

[26] 20.24

o

o

[26] 20.24

m

m

18

Organization

[26] 20.25

o

o

[26] 20.25

o

o

18AA

Origination-Id

7.2.19

n/a

c55

7.2.19

n/a

c55

18A

P-Access-Network-Info

[52] 4.4, [234] 2

c15

c16

[52] 4.4, [234] 2

c15

c16

18B

P-Asserted-Identity

[34] 9.1

n/a

c49

[34] 9.1

c11

c11

18C

P-Asserted-Service

[121] 4.1

n/a

c50

[121] 4.1

c33

c33

18D

P-Called-Party-ID

[52] 4.2

x

x

[52] 4.2

c13

c13

18E

P-Charging-Function-Addresses

[52] 4.5

c20

c21

[52] 4.5

c20

c21

18F

P-Charging-Vector

[52] 4.6

c18

c19

[52] 4.6

c18

c19

18H

P-Preferred-Identity

[34] 9.2

c11

c7

[34] 9.2

n/a

n/a

18I

P-Preferred-Service

[121] 4.2

c32

c31

[121] 4.2

n/a

n/a

18J

P-Private-Network-Indication

[134]

c36

c36

[134]

c36

c36

18K

P-Profile-Key

[97] 5

n/a

n/a

[97] 5

n/a

n/a

18L

P-Served-User

[133] 6

c41

c41

[133] 6

c41

c41

18M

P-User-Database

[82] 4

n/a

n/a

[82] 4

n/a

n/a

18N

P-Visited-Network-ID

[52] 4.3

x (note 1)

x

[52] 4.3

c14

n/a

19

Priority

[26] 20.26

o

o

[26] 20.26

o

o

19A

Privacy

[33] 4.2

c12

c12

[33] 4.2

c12

c12

20

Proxy-Authorization

[26] 20.28

c5

c5

[26] 20.28

n/a

n/a

21

Proxy-Require

[26] 20.29

o

n/a

[26] 20.29

n/a

n/a

21A

Reason

[34A] 2

c6

c6

[34A] 2

c6

c6

22A

Referred-By

[59] 3

c25

c25

[59] 3

c26

c26

23

Reject-Contact

[56B] 9.2

c24

c24

[56B] 9.2

c28

c28

23A

Relayed-Charge

7.2.12

n/a

c46

7.2.12

n/a

c46

23B

Reply-To

[26] 20.31

o

o

[26] 20.31

o

o

23C

Request-Disposition

[56B] 9.1

c24

c24

[56B] 9.1

c28

c28

24

Require

[26] 20.32

m

m

[26] 20.32

m

m

24A

Resource-Priority

[116] 3.1

c30

c30

[116] 3.1

c30

c30

25

Route

[26] 20.34

m

m

[26] 20.34

n/a

n/a

25A

Security-Client

[48] 2.3.1

c22

c22

[48] 2.3.1

n/a

n/a

25B

Security-Verify

[48] 2.3.1

c23

c23

[48] 2.3.1

n/a

n/a

25CA

Service-Interact-Info

Subclause 7.2.14

n/a

c56

Subclause 7.2.14

n/a

c57

25C

Session-ID

[162]

o

c43

[162]

o

c43

26

Subject

[26] 20.35

o

o

[26] 20.36

o

o

27

Supported

[26] 20.37

c9

m

[26] 20.37

m

m

28

Timestamp

[26] 20.38

c10

c10

[26] 20.38

m

m

29

To

[26] 20.39

m

m

[26] 20.39

m

m

29A

Trigger-Consent

[125] 5.11.2

c34

c34

[125] 5.11.2

c35

c35

30

User-Agent

[26] 20.41

o

o

[26] 20.41

o

o

31

Via

[26] 20.42

m

m

[26] 20.42

m

m

c1: IF A.4/22 THEN o ELSE n/a – – acting as the notifier of event information.

c2: IF A.4/23 THEN m ELSE n/a – – acting as the subscriber to event information.

c3: IF A.4/7 THEN m ELSE n/a – – authentication between UA and UA.

c4: IF A.4/11 THEN o ELSE n/a – – insertion of date in requests and responses.

c5: IF A.4/8A THEN m ELSE n/a – – authentication between UA and proxy.

c6: IF A.4/38 THEN o ELSE n/a – – the Reason header field for the session initiation protocol.

c7: IF A.3/1 AND A.4/25 THEN o ELSE n/a – – UE and private extensions to the Session Initiation Protocol (SIP) for asserted identity within trusted networks.

c9: IF A.4/14 THEN m ELSE o – – support of reliable transport.

c10: IF A.4/6 THEN o ELSE n/a – – timestamping of requests.

c11: IF A.4/25 THEN o ELSE n/a – – private extensions to the Session Initiation Protocol (SIP) for asserted identity within trusted networks.

c12: IF A.4/26 THEN o ELSE n/a – – a privacy mechanism for the Session Initiation Protocol (SIP).

c13: IF A.4/32 THEN o ELSE n/a – – the P-Called-Party-ID extension.

c14: IF A.4/33 THEN o ELSE n/a – – the P-Visited-Network-ID extension.

c15: IF A.4/34 THEN o ELSE n/a – – the P-Access-Network-Info header extension.

c16: IF A.4/34 AND A.3/1 THEN m ELSE n/a – – the P-Access-Network-Info header extension and UE.

c17: IF A.4/34 AND (A.3/7A OR A.3/7D) THEN m ELSE n/a – – the P-Access-Network-Info header extension and AS acting as terminating UA or AS acting as third-party call controller.

c18: IF A.4/36 THEN o ELSE n/a – – the P-Charging-Vector header extension.

c19: IF A.4/36 THEN m ELSE n/a – – the P-Charging-Vector header extension.

c20: IF A.4/35 THEN o ELSE n/a – – the P-Charging-Function-Addresses header extension.

c21: IF A.4/35 THEN m ELSE n/a – – the P-Charging-Function-Addresses header extension.

c22: IF A.4/37 OR A.4/37A THEN o ELSE n/a – – security mechanism agreement for the session initiation protocol or mediasec header field parameter for marking security mechanisms related to media (note 2).

c23: IF A.4/37 OR A.4/37A THEN m ELSE n/a – – security mechanism agreement for the session initiation protocol or mediasec header field parameter for marking security mechanisms related to media.

c24: IF A.4/40 THEN o ELSE n/a – – caller preferences for the session initiation protocol.

c25: IF A.4/43 THEN m ELSE n/a – – the SIP Referred-By mechanism.

c26: IF A.4/43 THEN o ELSE n/a – – the SIP Referred-By mechanism.

c27: IF A.4/47 THEN m ELSE n/a – – an extension to the session initiation protocol for request history information.

c28: IF A.4/40 THEN m ELSE n/a – – caller preferences for the session initiation protocol.

c29: IF A.4/60 THEN m ELSE n/a – – SIP location conveyance.

c30: IF A.4/70A THEN m ELSE n/a – – inclusion of MESSAGE, SUBSCRIBE, NOTIFY in communications resource priority for the session initiation protocol.

c31: IF A.3/1 AND A.4/74 THEN o ELSE n/a – – UE and SIP extension for the identification of services.

c32: IF A.4/74 THEN o ELSE n/a – – SIP extension for the identification of services.

c33: IF A.4/74 THEN m ELSE n/a – – SIP extension for the identification of services.

c34: IF A.4/75A THEN m ELSE n/a – – a relay within the framework for consent-based communications in SIP.

c35: IF A.4/75B THEN m ELSE n/a – – a recipient within the framework for consent-based communications in SIP.

c36: IF A.4/77 THEN m ELSE n/a – – the SIP P-Private-Network-Indication private-header (P-Header).

c39: IF A.4/71 AND (A.3/9B OR A.3/9C OR A.3/13B OR A.3/13C) THEN m ELSE IF A.3/1 AND NOT A.3C/1 THEN n/a ELSE o – – addressing an amplification vulnerability in session initiation protocol forking proxies, IBCF (IMS-ALG), IBCF (Screening of SIP signalling), ISC gateway function (IMS-ALG), ISC gateway function (Screening of SIP signalling), UE, UE performing the functions of an external attached network.

c40: IF A.4/71 THEN m ELSE n/a – – addressing an amplification vulnerability in session initiation protocol forking proxies.

c41: IF A.4/78 THEN m ELSE n/a – – the SIP P-Served-User private header.

c42: IF A.3/1 AND NOT A.3C/1 THEN n/a ELSE o – – UE, UE performing the functions of an external attached network.

c43: IF A.4/91 THEN m ELSE n/a – – the Session-ID header.

c44: IF A.4/100 THEN m ELSE n/a – – indication of features supported by proxy.

c45: IF A.4/100 AND A.3/1 AND NOT A.3C/1 THEN n/a ELSE IF A.4/100 THEN m ELSE n/a – – indication of features supported by proxy, UE, UE performing the functions of an external attached network.

c46: IF A.4/111 THEN m ELSE n/a – – the Relayed-Charge header field extension.

c47: IF A.4/113 AND A.3/1 THEN m ELSE n/a – – the Cellular-Network-Info header extension and UE.

c48: IF A.4/113 AND (A.3/7A OR A.3/7D) THEN m ELSE n/a – – the Cellular-Network-Info header extension and AS acting as terminating UA or AS acting as third-party call controller.

c49: IF A.4/25 AND (A.3/7B OR A.3/8) THEN o ELSE n/a – – private extensions to the Session Initiation Protocol (SIP) for asserted identity within trusted networks and AS acting as originating UA, MRFC.

c50: IF A.4/74 AND A.3/7B THEN o ELSE n/a – – SIP extension for the identification of services and AS acting as originating UA.

c51: IF A.4/116 AND (A.3/7 OR A.3/9) THEN m ELSE n/a – – authenticated identity management in the Session Initiation Protocol, AS, IBCF.

c52: IF A.4/119 THEN o ELSE n/a – – Content-ID header field in Session Initiation Protocol (SIP).

c53: IF A.4/119 THEN m ELSE n/a – – Content-ID header field in Session Initiation Protocol (SIP).

c54: IF A.4/121 AND (A.3/6 OR A.3/7 OR A.3/9) THEN m ELSE n/a – – the Attestation-Info header field extension, MGCF, AS, IBCF.

c55: IF A.4/122 AND (A.3/6 OR A.3/7 OR A.3/9) THEN m ELSE n/a – – the Origination-Id header field extension, MGCF, AS, IBCF.

c56: IF A.4/123 AND (A.3/7 OR A.3/9) THEN m ELSE n/a – – Dynamic services interactions, AS, IBCF.

c57: IF A.4/123 AND (A.3/2 OR A.3/7 OR A.3/9) THEN m ELSE n/a – – Dynamic services interactions, P-CSCF, AS, IBCF.

c58: IF A.4/124 THEN o ELSE n/a – – the Additional-Identity header field extension.

c59: IF A.4/124 THEN m ELSE n/a – – the Additional-Identity header field extension.

NOTE 1: The strength of this requirement in RFC 7315 [52] is SHOULD NOT, rather than MUST NOT.

NOTE 2: Support of this header in this method is dependent on the security mechanism and the security architecture which is implemented. Use of this header in this method is not appropriate to the security mechanism defined by 3GPP TS 33.203 [19].

Prerequisite A.5/9A – – MESSAGE request

Table A.62B: Supported message bodies within the MESSAGE request

Item

Header

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

1

permission document

[125] 5.4

c1

c1

[125] 5.4

c2

c2

2

application/vnd.3gpp.sms

[4D]

c3

c3

[4D]

c3

c3

3

message/cpim

[151]

c4

c4

[151]

c4

c4

4

message/imdn+xml

[157]

c5

c5

[157]

c5

c5

5

application/vnd.3gpp.mcptt-info+xml

[8ZE]

n/a

c6

[8ZE]

n/a

c6

6

application/vnd.3gpp.mcptt-mbms-usage-info+xml

[8ZE]

n/a

c6

[8ZE]

n/a

c6

7

application/vnd.3gpp.mcptt-location-info+xml

[8ZE]

n/a

c6

[8ZE]

n/a

c6

8

application/vnd.3gpp.mcptt-floor-request+xml

[8ZE]

n/a

c7

[8ZE]

n/a

c7

9

application/vnd.3gpp.mcptt-affiliation-command+xml

[8ZE]

n/a

c6

[8ZE]

n/a

c6

c1: IF A.4/75A THEN m ELSE n/a – – a relay within the framework for consent-based communications in SIP.

c2: IF A.4/75B THEN m ELSE n/a – – a recipient within the framework for consent-based communications in SIP.

c3: IF A.3A/61 OR A.3A/62 OR A.3A/63 THEN m ELSE o – – an SM-over-IP sender or an SM-over-IP receiver or an IP-SM-GW for SMS over IP.

c4: IF A.3A/71 AND A.4/85 THEN m ELSE n/a – – common presence and instant messaging (CPIM): message format.

c5: IF A.3A/71 AND A.4/86 THEN m ELSE n/a – – instant message disposition notification.

c6: IF A.3A/102 OR A.3A/103 THEN m ELSE n/a – – MCPTT client, MCPTT server.

c7: IF A.3A/103 THEN m ELSE n/a – – MCPTT server.

Prerequisite A.5/9B – – MESSAGE response

Prerequisite: A.6/1 – – Additional for 100 (Trying) response

Table A.62BA: Supported header fields within the MESSAGE response

Item

Header field

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

1

Call-ID

[26] 20.8

m

m

[26] 20.8

m

m

2

Content-Length

[26] 20.14

m

m

[26] 20.14

m

m

3

CSeq

[26] 20.16

m

m

[26] 20.16

m

m

4

Date

[26] 20.17

c1

c1

[26] 20.17

m

m

5

From

[26] 20.20

m

m

[26] 20.20

m

m

6

To

[26] 20.39

m

m

[26] 20.39

m

m

7

Via

[26] 20.42

m

m

[26] 20.42

m

m

c1: IF A.4/11 THEN o ELSE n/a – – insertion of date in requests and responses.

Prerequisite A.5/9B – – MESSAGE response for all remaining status-codes

Table A.62C: Supported header fields within the MESSAGE response

Item

Header field

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

0A

Allow

[26] 20.5

c12

c12

[26] 20.5

m

m

1

Call-ID

[26] 20.8

m

m

[26] 20.8

m

m

2

Call-Info

[26] 20.9

o

o

[26] 20.9

o

o

2A

Cellular-Network-Info

7.2.15

n/a

c19

7.2.15

n/a

c20

3

Content-Disposition

[26] 20.11

o (note 1)

o (note 1)

[26] 20.11

m (note 1)

m (note 1)

4

Content-Encoding

[26] 20.12

o (note 1)

o (note 1)

[26] 20.12

m (note 1)

m (note 1)

4A

Content-ID

[256] 3.2

o

c22

[256] 3.2

m

c23

5

Content-Language

[26] 20.13

o (note 1)

o (note 1)

[26] 20.13

m (note 1)

m (note 1)

6

Content-Length

[26] 20.14

m (note 1)

m (note 1)

[26] 20.14

m (note 1)

m (note 1)

7

Content-Type

[26] 20.15

m (note 1)

m (note 1)

[26] 20.15

m (note 1)

m (note 1)

8

CSeq

[26] 20.16

m

m

[26] 20.16

m

m

9

Date

[26] 20.17

c1

c1

[26] 20.17

m

m

9A

Expires

[26] 20.19

o

o

[26] 20.19

o

o

10

From

[26] 20.20

m

m

[26] 20.20

m

m

10A

Geolocation-Error

[89] 4.3

c14

c14

[89] 4.3

c14

c14

10B

History-Info

[66] 4.1

c13

c13

[66] 4.1

c13

c13

11

MIME-Version

[26] 20.24

o (note 1)

o (note 1)

[26] 20.24

m (note 1)

m (note 1)

12

Organization

[26] 20.25

o

o

[26] 20.25

o

o

12A

P-Access-Network-Info

[52] 4.4, [52A] 4, [234] 2

c5

c6

[52] 4.4, [52A] 4, [234] 2

c5

c7

12B

P-Asserted-Identity

[34] 9.1

n/a

c21

[34] 9.1

c3

c3

12C

P-Charging-Function-Addresses

[52] 4.5, [52A] 4

c10

c11

[52] 4.5, [52A] 4

c10

c11

12D

P-Charging-Vector

[52] 4.6, [52A] 4

c8

c9

[52] 4.6, [52A] 4

c8

c9

12F

P-Preferred-Identity

[34] 9.2

c3

x

[34] 9.2

n/a

n/a

12G

Privacy

[33] 4.2

c4

c4

[33] 4.2

c4

c4

12H

Relayed-Charge

7.2.12

n/a

c18

7.2.12

n/a

c18

12I

Reply-To

[26] 20.31

o

o

[26] 20.31

o

o

12J

Require

[26] 20.32

m

m

[26] 20.32

m

m

13

Server

[26] 20.35

o

o

[26] 20.35

o

o

13AA

Service-Interact-Info

Subclause 7.2.14

n/a

c24

Subclause 7.2.14

n/a

c25

13A

Session-ID

[162]

o

c17

[162]

o

c17

14

Timestamp

[26] 20.38

m

m

[26] 20.38

c2

c2

15

To

[26] 20.39

m

m

[26] 20.39

m

m

16

User-Agent

[26] 20.41

o

o

[26] 20.41

o

o

17

Via

[26] 20.42

m

m

[26] 20.42

m

m

18

Warning

[26] 20.43

o

o

[26] 20.43

o

o

c1: IF A.4/11 THEN o ELSE n/a – – insertion of date in requests and responses.

c2: IF A.4/6 THEN m ELSE n/a – – timestamping of requests.

c3: IF A.4/25 THEN o ELSE n/a – – private extensions to the Session Initiation Protocol (SIP) for asserted identity within trusted networks.

c4: IF A.4/26 THEN o ELSE n/a – – a privacy mechanism for the Session Initiation Protocol (SIP).

c5: IF A.4/34 THEN o ELSE n/a – – the P-Access-Network-Info header extension.

c6: IF A.4/34 AND A.3/1 THEN m ELSE n/a – – the P-Access-Network-Info header extension and UE.

c7: IF A.4/34 AND (A.3/7A OR A.3/7D) THEN m ELSE n/a – – the P-Access-Network-Info header extension and AS acting as terminating UA or AS acting as third-party call controller.

c8: IF A.4/36 THEN o ELSE n/a – – the P-Charging-Vector header extension.

c9: IF A.4/36 THEN m ELSE n/a – – the P-Charging-Vector header extension.

c10: IF A.4/35 THEN o ELSE n/a – – the P-Charging-Function-Addresses header extension.

c11: IF A.4/35 THEN m ELSE n/a – – the P-Charging-Function-Addresses header extension.

c12: IF A.6/18 THEN m ELSE o – – 405 (Method Not Allowed).

c13: IF A.4/47 THEN m ELSE n/a – – an extension to the session initiation protocol for request history information.

c14: IF A.4/60 THEN m ELSE n/a – – SIP location conveyance.

c17: IF A.4/91 THEN m ELSE n/a – – the Session-ID header.

c18: IF A.4/111 THEN m ELSE n/a – – the Relayed-Charge header field extension.

c19: IF A.4/113 AND A.3/1 THEN m ELSE n/a – – the Cellular-Network-Info header extension and UE.

c20: IF A.4/113 AND (A.3/7A OR A.3/7D) THEN m ELSE n/a – – the Cellular-Network-Info header extension and AS acting as terminating UA or AS acting as third-party call controller.

c21: IF A.4/25 AND (A.3/7B OR A.3/8 OR A.3A/83 OR A.3A/89) THEN o ELSE n/a – – private extensions to the Session Initiation Protocol (SIP) for asserted identity within trusted networks and AS acting as originating UA, MRFC, SCC application server, ATCF (UA).

c22: IF A.4/119 THEN o ELSE n/a – – Content-ID header field in Session Initiation Protocol (SIP).

c23: IF A.4/119 THEN m ELSE n/a – – Content-ID header field in Session Initiation Protocol (SIP).

c24: IF A.4/123 AND (A.3/7 OR A.3/9) THEN m ELSE n/a – – Dynamic services interactions, AS, IBCF.

c25: IF A.4/123 AND (A.3/2 OR A.3/7 OR A.3/9) THEN m ELSE n/a – – Dynamic services interactions, P-CSCF, AS, IBCF.

NOTE 1: RFC 3428 [50] clause 7 states that all 2xx class responses to a MESSAGE request must not include any body, therefore for 2xx responses to the MESSAGE request the values on Sending side for "RFC status" and "Profile status" are "x", the values for Receiving side for "RFC status" and "Profile Status" are "n/a". RFC 3261 [26] subclause 7.4 states that all responses may contain bodies, therefore for all responses to the MESSAGE request other than 2xx responses, the values on Sending side for "RFC status" and "Profile status" are "o", the values for Receiving side for "RFC status" and "Profile Status" are "m".

Prerequisite A.5/9B – – MESSAGE response

Prerequisite: A.6/102 – – Additional for 2xx response

Table A.62D: Supported header fields within the MESSAGE response

Item

Header field

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

0A

Accept-Resource-Priority

[116] 3.2

c5

c5

[116] 3.2

c5

c5

1

Allow-Events

[28] 8.2.2

c3

c3

[28] 8.2.2

c4

c4

2

Authentication-Info

[26] 20.6

c1

c1

[26] 20.6

c2

c2

3

Feature-Caps

[190]

c8

c8

[190]

c7

c7

3A

Reason

[294]

o

c9

[294]

o

c9

6

Supported

[26] 20.37

o

o

[26] 20.37

m

m

c1: IF A.4/7 THEN o ELSE n/a – – authentication between UA and UA.

c2: IF A.4/7 THEN m ELSE n/a – – authentication between UA and UA.

c3: IF A.4/22 THEN o ELSE n/a – – acting as the notifier of event information.

c4: IF A.4/23 THEN m ELSE n/a – – acting as the subscriber to event information.

c5: IF A.4/70A THEN m ELSE n/a – – inclusion of MESSAGE, SUBSCRIBE, NOTIFY in communications resource priority for the session initiation protocol.

c7: IF A.4/100 THEN m ELSE n/a – – indication of features supported by proxy.

c8: IF A.4/100 AND A.3/1 AND NOT A.3C/1 THEN n/a ELSE IF A.4/100 THEN m ELSE n/a – – indication of features supported by proxy, UE, UE performing the functions of an external attached network.

c9: IF A.4/38C THEN o ELSE n/a – – use of the Reason header field in Session Initiation Protocol (SIP) responses (carrying STIR codes).

Prerequisite A.5/9B – – MESSAGE response

Prerequisite: A.6/103 OR A.6/104 OR A.6/105 OR A.6/106 – – Additional for 3xx – 6xx response

Table A.62DA: Supported header fields within the MESSAGE response

Item

Header field

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

1

Error-Info

[26] 20.18

o

o

[26] 20.18

o

o

1A

Reason

[294]

o

c2

[294]

o

c2

2

Response-Source

7.2.17

n/a

c1

7.2.17

n/a

c1

c1: IF A.4/115 THEN o ELSE n/a – – use of the Response-Source header field in SIP error responses?

c2: IF A.4/38C THEN o ELSE n/a – – use of the Reason header field in Session Initiation Protocol (SIP) responses (carrying STIR codes).

Prerequisite A.5/9B – – MESSAGE response

Prerequisite: A.6/103 – – Additional for 3xx or 485 (Ambiguous) response

Table A.62E: Supported header fields within the MESSAGE response

Item

Header field

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

2

Contact

[26] 20.10

o (note)

o

[26] 20.10

m

m

NOTE: The strength of this requirement is RECOMMENDED rather than OPTIONAL.

Prerequisite A.5/9B – – MESSAGE response

Prerequisite: A.6/14 – – Additional for 401 (Unauthorized) response

Table A.62F: Supported header fields within the MESSAGE response

Item

Header field

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

3

Proxy-Authenticate

[26] 20.27

c1

c1

[26] 20.27

c1

c1

6

WWW-Authenticate

[26] 20.44

m

m

[26] 20.44

m

m

c1: IF A.4/7 THEN m ELSE n/a – – support of authentication between UA and UA.

Prerequisite A.5/9B – – MESSAGE response

Prerequisite: A.6/17 OR A.6/23 OR A.6/30 OR A.6/36 OR A.6/42 OR A.6/45 OR A.6/50 OR A.6/51 – – Additional for 404 (Not Found), 413 (Request Entity Too Large), 480(Temporarily not available), 486 (Busy Here), 500 (Internal Server Error), 503 (Service Unavailable), 600 (Busy Everywhere), 603 (Decline) response

Table A.62G: Supported header fields within the MESSAGE response

Item

Header field

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

4

Retry-After

[26] 20.33

o

o

[26] 20.33

o

o

Table A.62H: Void

Prerequisite A.5/9B – – MESSAGE response

Prerequisite: A.6/20 – – Additional for 407 (Proxy Authentication Required) response

Table A.62I: Supported header fields within the MESSAGE response

Item

Header field

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

3

Proxy-Authenticate

[26] 20.27

c1

c1

[26] 20.27

c1

c1

6

WWW-Authenticate

[26] 20.44

o

o

[26] 20.44

o

o

c1: IF A.4/7 THEN m ELSE n/a – – support of authentication between UA and UA.

Table A.62IA: Void

Prerequisite A.5/9B – – MESSAGE response

Prerequisite: A.6/25 – – Additional for 415 (Unsupported Media Type) response

Table A.62J: Supported header fields within the MESSAGE response

Item

Header field

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

1

Accept

[26] 20.1

o.1

o.1

[26] 20.1

m

m

2

Accept-Encoding

[26] 20.2

o.1

o.1

[26] 20.2

m

m

3

Accept-Language

[26] 20.3

o.1

o.1

[26] 20.3

m

m

o.1 At least one of these capabilities is supported.

Prerequisite A.5/9B – – MESSAGE response

Prerequisite: A.6/26A – – Additional for 417 (Unknown Resource-Priority) response

Table A.62JA: Supported header fields within the MESSAGE response

Item

Header field

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

1

Accept-Resource-Priority

[116] 3.2

c1

c1

[116] 3.2

c1

c1

c1: IF A.4/70A THEN m ELSE n/a – – inclusion of MESSAGE, SUBSCRIBE, NOTIFY in communications resource priority for the session initiation protocol.

Prerequisite A.5/9B – – MESSAGE response

Prerequisite: A.6/27 – – Additional for 420 (Bad Extension) response

Table A.62K: Supported header fields within the MESSAGE response

Item

Header field

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

5

Unsupported

[26] 20.40

m

m

[26] 20.40

m

m

Prerequisite A.5/9B – – MESSAGE response

Prerequisite: A.6/28 OR A.6/41A – – Additional for 421 (Extension Required), 494 (Security Agreement Required) response

Table A.62L: Supported header fields within the MESSAGE response

Item

Header field

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

3

Security-Server

[48] 2

x

x

[48] 2

c1

c1

c1: IF A.4/37 THEN m ELSE n/a – – security mechanism agreement for the session initiation protocol.

Table A.62M: Void

Prerequisite A.5/9B – – MESSAGE response

Prerequisite: A.6/29H – – Additional for 470 (Consent Needed) response

Table A.62MA: Supported header fields within the MESSAGE response

Item

Header field

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

1

Permission-Missing

[125] 5.9.3

m

m

[125] 5.9.3

m

m

Prerequisite A.5/9B – – MESSAGE response

Prerequisite: A.6/46 – – Additional for 504 (Server Time-out) response

Table A.62MB: Supported header fields within the MESSAGE response

Item

Header field

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

1

Restoration-Info

subclause 7.2.11

n/a

c1

subclause 7.2.11

n/a

n/a

c1: IF A.4/110 THEN o ELSE n/a – – HSS based P-CSCF restoration.

Prerequisite A.5/9B – – MESSAGE response

Table A.62N: Supported message bodies within the MESSAGE response

Item

Header

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

1

A.2.1.4.8 NOTIFY method

Prerequisite A.5/10 – – NOTIFY request

Table A.63: Supported header fields within the NOTIFY request

Item

Header field

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

1

Accept

[26] 20.1

o

o

[26] 20.1

m

m

1A

Accept-Contact

[56B] 9.2

c19

c19

[56B] 9.2

c23

c23

2

Accept-Encoding

[26] 20.2

o

o

[26] 20.2

m

m

3

Accept-Language

[26] 20.3

o

o

[26] 20.3

m

m

3A

Allow

[26] 20.5

o

o

[26] 20.5

m

m

4

Allow-Events

[28] 8.2.2

c1

c1

[28] 8.2.2

c2

c2

5

Authorization

[26] 20.7

c3

c3

[26] 20.7

c3

c3

6

Call-ID

[26] 20.8

m

m

[26] 20.8

m

m

6A

Call-Info

[26] 20.9

o

o

[26] 20.9

c25

c25

6B

Cellular-Network-Info

7.2.15

n/a

c38

7.2.15

n/a

c39

6C

Contact

[26] 20.10

m

m

[26] 20.10

m

m

7

Content-Disposition

[26] 20.11

o

o

[26] 20.11

m

m

8

Content-Encoding

[26] 20.12

o

o

[26] 20.12

m

m

8A

Content-ID

[256] 3.2

o

c41

[256] 3.2

m

c42

9

Content-Language

[26] 20.13

o

o

[26] 20.13

m

m

10

Content-Length

[26] 20.14

m

m

[26] 20.14

m

m

11

Content-Type

[26] 20.15

m

m

[26] 20.15

m

m

12

CSeq

[26] 20.16

m

m

[26] 20.16

m

m

13

Date

[26] 20.17

c4

c4

[26] 20.17

m

m

14

Event

[28] 8.2.1

m

m

[28] 8.2.1

m

m

14A

Feature-Caps

[190]

c35

c35

[190]

c34

c34

15

From

[26] 20.20

m

m

[26] 20.20

m

m

15A

Geolocation

[89] 4.1

c24

c24

[89] 4.1

c24

c24

15B

Geolocation-Routing

[89] 4.2

c24

c24

[89] 4.2

c24

c24

15C

History-Info

[66] 4.1

c22

c22

[66] 4.1

c22

c22

15D

Max-Breadth

[117] 5.8

n/a

c26

[117] 5.8

c27

c27

16

Max-Forwards

[26] 20.22

m

m

[26] 20.22

n/a

c32

17

MIME-Version

[26] 20.24

o

o

[26] 20.24

m

m

17A

P-Access-Network-Info

[52] 4.4, [234] 2

c10

c11

[52] 4.4, [234] 2

c10

c12

17B

P-Asserted-Identity

[34] 9.1

n/a

c40

[34] 9.1

c6

c6

17C

P-Charging-Function-Addresses

[52] 4.5

c14

c15

[52] 4.5

c14

c15

17D

P-Charging-Vector

[52] 4.6

c13

c36

[52] 4.6

c13

c36

17F

P-Preferred-Identity

[34] 9.2

c6

x

[34] 9.2

n/a

n/a

17G

Privacy

[33] 4.2

c7

n/a

[33] 4.2

c7

c7

18

Proxy-Authorization

[26] 20.28

c5

c5

[26] 20.28

n/a

n/a

19

Proxy-Require

[26] 20.29

o

n/a

[26] 20.29

n/a

n/a

19A

Reason

[34A] 2

c18

c18

[34A] 2

c18

c18

20

Record-Route

[26] 20.30

n/a

c32

[26] 20.30

c9

c9

20A

Referred-By

[59] 3

c20

c20

[59] 3

c21

c21

20B

Reject-Contact

[56B] 9.2

c19

c19

[56B] 9.2

c23

c23

20C

Relayed-Charge

7.2.12

n/a

c37

7.2.12

n/a

c37

20D

Request-Disposition

[56B] 9.1

c19

c19

[56B] 9.1

c23

c23

21

Require

[26] 20.32

m

m

[26] 20.32

m

m

22A

Resource-Priority

[116] 3.1

c29

c29

[116] 3.1

c29

c29

22B

Security-Client

[48] 2.3.1

c16

c16

[48] 2.3.1

n/a

n/a

22C

Security-Verify

[48] 2.3.1

c17

c17

[48] 2.3.1

n/a

n/a

22D

Session-ID

[162]

o

c33

[162]

o

c33

22

Route

[26] 20.34

m

m

[26] 20.34

n/a

c32

23

Subscription-State

[28] 8.2.3

m

m

[28] 8.2.3

m

m

24

Supported

[26] 20.37

o

o

[26] 20.37

m

m

25

Timestamp

[26] 20.38

c8

c8

[26] 20.38

m

m

26

To

[26] 20.39

m

m

[26] 20.39

m

m

27

User-Agent

[26] 20.41

o

o

[26] 20.41

o

o

28

Via

[26] 20.42

m

m

[26] 20.42

m

m

29

Warning

[26] 20.43

o

o

[26] 20.43

o

o

c1: IF A.4/20 THEN o ELSE n/a – – SIP specific event notification extension.

c2: IF A.4/20 THEN m ELSE n/a – – SIP specific event notification extension.

c3: IF A.4/7 THEN m ELSE n/a – – authentication between UA and UA.

c4: IF A.4/11 THEN o ELSE n/a – – insertion of date in requests and responses.

c5: IF A.4/8A THEN m ELSE n/a – – authentication between UA and proxy.

c6: IF A.4/25 THEN o ELSE n/a – – private extensions to the Session Initiation Protocol (SIP) for asserted identity within trusted networks.

c7: IF A.4/26 THEN o ELSE n/a – – a privacy mechanism for the Session Initiation Protocol (SIP).

c8: IF A.4/6 THEN o ELSE n/a – – timestamping of requests.

c9: IF A.4/15 OR A.4/20 THEN m ELSE n/a – – the REFER method extension or SIP specific event notification extension.

c10: IF A.4/34 THEN o ELSE n/a – – the P-Access-Network-Info header extension.

c11: IF A.4/34 AND A.3/1 THEN m ELSE n/a – – the P-Access-Network-Info header extension and UE.

c12: IF A.4/34 AND (A.3/7A OR A.3/7D) THEN m ELSE n/a – – the P-Access-Network-Info header extension and AS acting as terminating UA or AS acting as third-party call controller.

c13: IF A.4/36 THEN o ELSE n/a – – the P-Charging-Vector header extension.

c14: IF A.4/35 THEN o ELSE n/a – – the P-Charging-Function-Addresses header extension.

c15: IF A.4/35 THEN m ELSE n/a – – the P-Charging-Function-Addresses header extension.

c16: IF A.4/37 OR A.4/37A THEN o ELSE n/a – – security mechanism agreement for the session initiation protocol or mediasec header field parameter for marking security mechanisms related to media (note).

c17: IF A.4/37 OR A.4/37A THEN m ELSE n/a – – security mechanism agreement for the session initiation protocol or mediasec header field parameter for marking security mechanisms related to media.

c18: IF A.4/38 THEN o ELSE n/a – – the Reason header field for the session initiation protocol.

c19: IF A.4/40 THEN o ELSE n/a – – caller preferences for the session initiation protocol.

c20: IF A.4/43 THEN m ELSE n/a – – the SIP Referred-By mechanism.

c21: IF A.4/43 THEN o ELSE n/a – – the SIP Referred-By mechanism.

c22: IF A.4/47 THEN m ELSE n/a – – an extension to the session initiation protocol for request history information.

c23: IF A.4/40 THEN m ELSE n/a – – caller preferences for the session initiation protocol.

c24: IF A.4/60 THEN m ELSE n/a – – SIP location conveyance.

c25: IF A.4/63 THEN m ELSE o – – subscriptions to request-contained resource lists in the session initiation protocol.

c26: IF A.4/71 AND (A.3/9B OR A.3/9C OR A.3/13B OR A.3/13C) THEN m ELSE IF A.3/1 AND NOT A.3C/1 THEN n/a ELSE o – – addressing an amplification vulnerability in session initiation protocol forking proxies, IBCF (IMS-ALG), IBCF (Screening of SIP signalling), ISC gateway function (IMS-ALG), ISC gateway function (Screening of SIP signalling), UE, UE performing the functions of an external attached network.

c27: IF A.4/71 THEN m ELSE n/a – – addressing an amplification vulnerability in session initiation protocol forking proxies.

c29: IF A.4/70A THEN m ELSE n/a – – inclusion of MESSAGE, SUBSCRIBE, NOTIFY in communications resource priority for the session initiation protocol.

c32:: IF A.3/1 AND NOT A.3C/1 THEN n/a ELSE o – – UE, UE performing the functions of an external attached network.

c33: IF A.4/91 THEN m ELSE n/a – – the Session-ID header.

c34: IF A.4/100 THEN m ELSE n/a – – indication of features supported by proxy.

c35: IF A.4/100 AND A.3/1 AND NOT A.3C/1 THEN n/a ELSE IF A.4/100 THEN m ELSE n/a – – indication of features supported by proxy, UE, UE performing the functions of an external attached network.

c36: IF A.4/36 THEN m ELSE n/a – – the P-Charging-Vector header extension.

c37: IF A.4/111 THEN m ELSE n/a – – the Relayed-Charge header field extension.

c38: IF A.4/113 AND A.3/1 THEN m ELSE n/a – – the Cellular-Network-Info header extension and UE.

c39: IF A.4/113 AND (A.3/7A OR A.3/7D) THEN m ELSE n/a – – the Cellular-Network-Info header extension and AS acting as terminating UA or AS acting as third-party call controller.

c40: IF A.4/25 AND (A.3/7B OR A.3/8) THEN o ELSE n/a – – private extensions to the Session Initiation Protocol (SIP) for asserted identity within trusted networks and AS acting as originating UA, MRFC.

c41: IF A.4/119 THEN o ELSE n/a – – Content-ID header field in Session Initiation Protocol (SIP).

c42: IF A.4/119 THEN m ELSE n/a – – Content-ID header field in Session Initiation Protocol (SIP).

NOTE: Support of this header in this method is dependent on the security mechanism and the security architecture which is implemented. Use of this header in this method is not appropriate to the security mechanism defined by 3GPP TS 33.203 [19].

Prerequisite A.5/10 – – NOTIFY request

Table A.64: Supported message bodies within the NOTIFY request

Item

Header

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

1

sipfrag

[37] 2

c1

c1

[37]

c1

c1

2

event package (see NOTE)

[28]

m

m

[28]

m

m

c1: IF A.4/15 THEN m ELSE o – – the REFER method extension

NOTE: The appropriate body specified for the supported event package (see table A.4A) is supported.

Prerequisite A.5/11 – – NOTIFY response

Prerequisite: A.6/1 – – Additional for 100 (Trying) response

Table A.64A: Supported header fields within the NOTIFY response

Item

Header field

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

1

Call-ID

[26] 20.8

m

m

[26] 20.8

m

m

2

Content-Length

[26] 20.14

m

m

[26] 20.14

m

m

3

CSeq

[26] 20.16

m

m

[26] 20.16

m

m

4

Date

[26] 20.17

c1

c1

[26] 20.17

m

m

5

From

[26] 20.20

m

m

[26] 20.20

m

m

6

To

[26] 20.39

m

m

[26] 20.39

m

m

7

Via

[26] 20.42

m

m

[26] 20.42

m

m

c1: IF A.4/11 THEN o ELSE n/a – – insertion of date in requests and responses.

Prerequisite A.5/11 – – NOTIFY response for all remaining status-codes

Table A.65: Supported header fields within the NOTIFY response

Item

Header field

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

0A

Allow

[26] 20.5

c11

c11

[26] 20.5

m

m

1

Call-ID

[26] 20.8

m

m

[26] 20.8

m

m

1A

Cellular-Network-Info

7.2.15

n/a

c18

7.2.15

n/a

c19

2

Content-Disposition

[26] 20.11

o

o

[26] 20.11

m

m

3

Content-Encoding

[26] 20.12

o

o

[26] 20.12

m

m

3A

Content-ID

[256] 3.2

o

c21

[256] 3.2

m

c22

4

Content-Language

[26] 20.13

o

o

[26] 20.13

m

m

5

Content-Length

[26] 20.14

m

m

[26] 20.14

m

m

6

Content-Type

[26] 20.15

m

m

[26] 20.15

m

m

7

CSeq

[26] 20.16

m

m

[26] 20.16

m

m

8

Date

[26] 20.17

c1

c1

[26] 20.17

m

m

9

From

[26] 20.20

m

m

[26] 20.20

m

m

9A

Geolocation-Error

[89] 4.3

c12

c12

[89] 4.3

c12

c12

10

MIME-Version

[26] 20.24

o

o

[26] 20.24

m

m

10A

P-Access-Network-Info

[52] 4.4, [52A] 4, [234] 2

c5

c6

[52] 4.4, [52A] 4, [234] 2

c5

c7

10B

P-Asserted-Identity

[34] 9.1

n/a

c20

[34] 9.1

c3

c3

10C

P-Charging-Function-Addresses

[52] 4.5, [52A] 4

c9

c10

[52] 4.5, [52A] 4

c9

c10

10D

P-Charging-Vector

[52] 4.6, [52A] 4

c8

c16

[52] 4.6, [52A] 4

c8

c16

10F

P-Preferred-Identity

[34] 9.2

c3

x

[34] 9.2

n/a

n/a

10G

Privacy

[33] 4.2

c4

n/a

[33] 4.2

c4

c4

10H

Relayed-Charge

7.2.12

n/a

c17

7.2.12

n/a

c17

10I

Require

[26] 20.32

m

m

[26] 20.32

m

m

10J

Server

[26] 20.35

o

o

[26] 20.35

o

o

10K

Session-ID

[162]

o

c15

[162]

o

c15

11

Timestamp

[26] 20.38

m

m

[26] 20.38

c2

c2

12

To

[26] 20.39

m

m

[26] 20.39

m

m

12A

User-Agent

[26] 20.41

o

o

[26] 20.41

o

o

13

Via

[26] 20.42

m

m

[26] 20.42

m

m

14

Warning

[26] 20.43

o (note)

o

[26] 20.43

o

o

c1: IF A.4/11 THEN o ELSE n/a – – insertion of date in requests and responses.

c2: IF A.4/6 THEN m ELSE n/a – – timestamping of requests.

c3: IF A.4/25 THEN o ELSE n/a – – private extensions to the Session Initiation Protocol (SIP) for asserted identity within trusted networks.

c4: IF A.4/26 THEN o ELSE n/a – – a privacy mechanism for the Session Initiation Protocol (SIP).

c5: IF A.4/34 THEN o ELSE n/a – – the P-Access-Network-Info header extension.

c6: IF A.4/34 AND A.3/1 THEN m ELSE n/a – – the P-Access-Network-Info header extension and UE.

c7: IF A.4/34 AND (A.3/7A OR A.3/7D) THEN m ELSE n/a – – the P-Access-Network-Info header extension and AS acting as terminating UA or AS acting as third-party call controller.

c8: IF A.4/36 THEN o ELSE n/a – – the P-Charging-Vector header extension.

c9: IF A.4/35 THEN o ELSE n/a – – the P-Charging-Function-Addresses header extension.

c10: IF A.4/35 THEN m ELSE n/a – – the P-Charging-Function-Addresses header extension.

c11: IF A.6/18 THEN m ELSE o – – 405 (Method Not Allowed).

c12: IF A.4/60 THEN m ELSE n/a – – SIP location conveyance.

c15: IF A.4/91 THEN m ELSE n/a – – the Session-ID header.

c16: IF A.4/36 THEN m ELSE n/a – – the P-Charging-Vector header extension.

c17: IF A.4/111 THEN m ELSE n/a – – the Relayed-Charge header field extension.

c18: IF A.4/113 AND A.3/1 THEN m ELSE n/a – – the Cellular-Network-Info header extension and UE.

c19: IF A.4/113 AND (A.3/7A OR A.3/7D) THEN m ELSE n/a – – the Cellular-Network-Info header extension and AS acting as terminating UA or AS acting as third-party call controller.

c20: IF A.4/25 AND (A.3/7B OR A.3/8) THEN o ELSE n/a – – private extensions to the Session Initiation Protocol (SIP) for asserted identity within trusted networks and AS acting as originating UA, MRFC.

c21: IF A.4/119 THEN o ELSE n/a – – Content-ID header field in Session Initiation Protocol (SIP).

c22: IF A.4/119 THEN m ELSE n/a – – Content-ID header field in Session Initiation Protocol (SIP).

NOTE: RFC 3261 [26] gives the status of this header as SHOULD rather than OPTIONAL.

Prerequisite A.5/11 – – NOTIFY response

Prerequisite: A.6/102 – – Additional for 2xx response

Table A.66: Supported header fields within the NOTIFY response

Item

Header field

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

0A

Accept-Resource-Priority

[116] 3.2

c6

c6

[116] 3.2

c6

c6

0B

Allow-Events

[28] 8.2.2

c4

c4

[28] 8.2.2

c5

c5

1

Authentication-Info

[26] 20.6

c1

c1

[26] 20.6

c2

c2

1A

Contact

[26] 20.10

o

o

[26] 20.10

m

m

1B

Feature-Caps

[190]

c8

c8

[190]

c8

c8

2

Record-Route

[26] 20.30

c3

c3

[26] 20.30

c3

c3

5

Supported

[26] 20.37

m

m

[26] 20.37

m

m

c1: IF A.4/7 THEN o ELSE n/a – – authentication between UA and UA.

c2: IF A.4/7 THEN m ELSE n/a – – authentication between UA and UA.

c3: IF A.4/15 OR A.4/20 THEN m ELSE n/a – – the REFER method extension or SIP specific event notification extension.

c4: IF A.4/20 THEN o ELSE n/a – – SIP specific event notification extension.

c5: IF A.4/20 THEN m ELSE n/a – – SIP specific event notification extension.

c6: IF A.4/70A THEN m ELSE n/a – – inclusion of MESSAGE, SUBSCRIBE, NOTIFY in communications resource priority for the session initiation protocol.

c8: IF A.4/100 THEN m ELSE n/a – – indication of features supported by proxy.

Prerequisite A.5/11 – – NOTIFY response

Prerequisite: A.6/103 OR A.6/104 OR A.6/105 OR A.6/106 – – Additional for 3xx – 6xx response

Table A.66A: Supported header fields within the NOTIFY response

Item

Header field

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

1

Error-Info

[26] 20.18

o

o

[26] 20.18

o

o

2

Response-Source

7.2.17

n/a

c1

7.2.17

n/a

c1

c1: IF A.4/115 THEN o ELSE n/a – – use of the Response-Source header field in SIP error responses?

Prerequisite A.5/11 – – NOTIFY response

Prerequisite: A.6/103 – – Additional for 3xx response

Table A.67: Supported header fields within the NOTIFY response

Item

Header field

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

1

Contact

[26] 20.10

m

m

[26] 20.10

m

m

Prerequisite A.5/11 – – NOTIFY response

Prerequisite: A.6/14 – – Additional for 401 (Unauthorized) response

Table A.68: Supported header fields within the NOTIFY response

Item

Header field

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

2

Proxy-Authenticate

[26] 20.27

c1

c1

[26] 20.27

c1

c1

8

WWW-Authenticate

[26] 20.44

m

m

[26] 20.44

m

m

c1: IF A.4/7 THEN m ELSE n/a – – support of authentication between UA and UA.

Prerequisite A.5/11 – – NOTIFY response

Prerequisite: A.6/17 OR A.6/23 OR A.6/30 OR A.6/36 OR A.6/42 OR A.6/45 OR A.6/50 OR A.6/51 – – Additional for 404 (Not Found), 413 (Request Entity Too Large), 480(Temporarily not available), 486 (Busy Here), 500 (Internal Server Error), 503 (Service Unavailable), 600 (Busy Everywhere), 603 (Decline) response

Table A.69: Supported header fields within the NOTIFY response

Item

Header field

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

3

Retry-After

[26] 20.33

o

o

[26] 20.33

o

o

Table A.70: Void

Table A.71: Void

Prerequisite A.5/11 – – NOTIFY response

Prerequisite: A.6/21 – – Additional for 408 (Request timeout) response

Table A.71A: Supported header fields within the NOTIFY response

Item

Header field

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

1

Restoration-Info

subclause 7.2.11

n/a

c1

subclause 7.2.11

n/a

n/a

c1: IF A.4/110 THEN o ELSE n/a – – HSS based P-CSCF restoration.

Prerequisite A.5/11 – – NOTIFY response

Prerequisite A.6/25 – – Additional for 415 (Unsupported Media Type) response

Table A.72: Supported header fields within the NOTIFY response

Item

Header field

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

1

Accept

[26] 20.1

o.1

o.1

[26] 20.1

m

m

2

Accept-Encoding

[26] 20.2

o.1

o.1

[26] 20.2

m

m

3

Accept-Language

[26] 20.3

o.1

o.1

[26] 20.3

m

m

o.1 At least one of these capabilities is supported.

Prerequisite A.5/11 – – NOTIFY response

Prerequisite: A.6/26A – – Additional for 417 (Unknown Resource-Priority) response

Table A.72A: Supported header fields within the NOTIFY response

Item

Header field

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

1

Accept-Resource-Priority

[116] 3.2

c1

c1

[116] 3.2

c1

c1

c1: IF A.4/70A THEN m ELSE n/a – – inclusion of MESSAGE, SUBSCRIBE, NOTIFY in communications resource priority for the session initiation protocol.

Prerequisite A.5/11 – – NOTIFY response

Prerequisite: A.6/27 – – Addition for 420 (Bad Extension) response

Table A.73: Supported header fields within the NOTIFY response

Item

Header field

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

5

Unsupported

[26] 20.40

m

m

[26] 20.40

m

m

Prerequisite A.5/11 – – NOTIFY response

Prerequisite: A.6/28 OR A.6/41A – – Additional for 421 (Extension Required), 494 (Security Agreement Required) response

Table A.73A: Supported header fields within the NOTIFY response

Item

Header field

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

3

Security-Server

[48] 2

x

x

[48] 2

c1

c1

c1: IF A.4/37 THEN m ELSE n/a – – security mechanism agreement for the session initiation protocol.

Table A.74: Void

Prerequisite A.5/11 – – NOTIFY response

Prerequisite: A.6/35 – – Additional for 485 (Ambigious) response

Table A.74A: Supported header fields within the NOTIFY response

Item

Header field

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

1

Contact

[26] 20.10

o

o

[26] 20.10

m

m

Prerequisite A.5/11 – – NOTIFY response

Prerequisite: A.6/39 – – Additional for 489 (Bad Event) response

Table A.75: Supported header fields within the NOTIFY response

Item

Header field

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

1

Allow-Events

[28] 8.2.2

m

m

[28] 8.2.2

m

m

Prerequisite A.5/11 – – NOTIFY response

Prerequisite: A.6/46 – – Additional for 504 (Server Time-out) response

Table A.75A: Supported header fields within the NOTIFY response

Item

Header field

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

1

Restoration-Info

subclause 7.2.11

n/a

c1

subclause 7.2.11

n/a

n/a

c1: IF A.4/110 THEN o ELSE n/a – – HSS based P-CSCF restoration.

Prerequisite A.5/11 – – NOTIFY response

Table A.76: Supported message bodies within the NOTIFY response

Item

Header

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

1

A.2.1.4.9 OPTIONS method

Prerequisite A.5/12 – – OPTIONS request

Table A.77: Supported header fields within the OPTIONS request

Item

Header field

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

1

Accept

[26] 20.1

m

m

[26] 20.1

m

m

1A

Accept-Contact

[56B] 9.2

c21

c21

[56B] 9.2

c26

c26

2

Accept-Encoding

[26] 20.2

m

m

[26] 20.2

m

m

3

Accept-Language

[26] 20.3

m

m

[26] 20.3

m

m

3A

Allow

[26] 20.5

o

o

[26] 20.5

m

m

4

Allow-Events

[28] 8.2.2

c24

c24

[28] 8.2.2

c1

c1

5

Authorization

[26] 20.7

c2

c2

[26] 20.7

c2

c2

6

Call-ID

[26] 20.8

m

m

[26] 20.8

m

m

7

Call-Info

[26] 20.9

o

o

[26] 20.9

o

o

7A

Cellular-Network-Info

7.2.15

n/a

c44

7.2.15

n/a

c45

8

Contact

[26] 20.10

o

o

[26] 20.10

o

o

9

Content-Disposition

[26] 20.11

o

o

[26] 20.11

m

m

10

Content-Encoding

[26] 20.12

o

o

[26] 20.12

m

m

10A

Content-ID

[256] 3.2

o

c48

[256] 3.2

m

c49

11

Content-Language

[26] 20.13

o

o

[26] 20.13

m

m

12

Content-Length

[26] 20.14

m

m

[26] 20.14

m

m

13

Content-Type

[26] 20.15

m

m

[26] 20.15

m

m

14

CSeq

[26] 20.16

m

m

[26] 20.16

m

m

15

Date

[26] 20.17

c3

c3

[26] 20.17

m

m

15A

Feature-Caps

[190]

c42

c42

[190]

c41

c41

16

From

[26] 20.20

m

m

[26] 20.20

m

m

16A

Geolocation

[89] 4.1

c27

c27

[89] 4.1

c27

c27

16B

Geolocation-Routing

[89] 4.2

c27

c27

[89] 4.2

c27

c27

16C

History-Info

[66] 4.1

c25

c25

[66] 4.1

c25

c25

16D

Max-Breadth

[117] 5.8

n/a

c31

[117] 5.8

c32

c32

17

Max-Forwards

[26] 20.22

m

m

[26] 20.22

n/a

c39

18

MIME-Version

[26] 20.24

o

o

[26] 20.24

m

m

19

Organization

[26] 20.25

o

o

[26] 20.25

o

o

19A

P-Access-Network-Info

[52] 4.4, [234] 2

c11

c12

[52] 4.4, [234] 2

c11

c13

19B

P-Asserted-Identity

[34] 9.1

n/a

c46

[34] 9.1

c6

c6

19C

P-Asserted-Service

[121] 4.1

n/a

c47

[121] 4.1

c30

c30

19D

P-Called-Party-ID

[52] 4.2

x

x

[52] 4.2

c9

c9

19E

P-Charging-Function-Addresses

[52] 4.5

c16

c17

[52] 4.5

c16

c17

19F

P-Charging-Vector

[52] 4.6

c14

c15

[52] 4.6

c14

c15

19H

P-Preferred-Identity

[34] 9.2

c6

c4

[34] 9.2

n/a

n/a

19I

P-Preferred-Service

[121] 4.2

c29

c28

[121] 4.2

n/a

n/a

19J

P-Private-Network-Indication

[134]

c34

c34

[134]

c34

c34

19K

P-Profile-Key

[97] 5

n/a

n/a

[97] 5

n/a

n/a

19L

P-Served-User

[133] 6

c38

c38

[133] 6

c38

c38

19M

P-User-Database

[82] 4

n/a

n/a

[82] 4

n/a

n/a

19N

P-Visited-Network-ID

[52] 4.3

x (note 2)

x

[52] 4.3

c10

n/a

19O

Privacy

[33] 4.2

c8

c8

[33] 4.2

c8

c8

20

Proxy-Authorization

[26] 20.28

c5

c5

[26] 20.28

n/a

n/a

21

Proxy-Require

[26] 20.29

o

o (note 1)

[26] 20.29

n/a

n/a

21A

Reason

[34A] 2

c20

c20

[34A] 2

c20

c20

22

Record-Route

[26] 20.30

n/a

c39

[26] 20.30

n/a

c39

22A

Recv-Info

[25] 5.2.3

c37

c37

[25] 5.2.3

c37

c37

22B

Referred-By

[59] 3

c22

c22

[59] 3

c23

c23

22C

Reject-Contact

[56B] 9.2

c21

c21

[56B] 9.2

c26

c26

22D

Relayed-Charge

7.2.12

n/a

c43

7.2.12

n/a

c43

22E

Request-Disposition

[56B] 9.1

c21

c21

[56B] 9.1

c26

c26

23

Require

[26] 20.32

m

m

[26] 20.32

m

m

23A

Resource-Priority

[116] 3.1

c33

c33

[116] 3.1

c33

c33

24

Route

[26] 20.34

m

m

[26] 20.34

n/a

n/a

24A

Security-Client

[48] 2.3.1

c18

c18

[48] 2.3.1

n/a

n/a

24B

Security-Verify

[48] 2.3.1

c19

c19

[48] 2.3.1

n/a

n/a

24C

Session-ID

[162]

o

c40

[162]

o

c40

25

Supported

[26] 20.37

c6

c6

[26] 20.37

m

m

26

Timestamp

[26] 20.38

c7

c7

[26] 20.38

m

m

27

To

[26] 20.39

m

m

[26] 20.39

m

m

28

User-Agent

[26] 20.41

o

o

[26] 20.41

o

o

29

Via

[26] 20.42

m

m

[26] 20.42

m

m

c1: IF A.4/23 THEN m ELSE n/a – – acting as the subscriber to event information.

c2: IF A.4/7 THEN m ELSE n/a – – authentication between UA and UA.

c3: IF A.4/11 THEN o ELSE n/a – – insertion of date in requests and responses.

c4: IF A.3/1 AND A.4/25 THEN o ELSE n/a – – UE and private extensions to the Session Initiation Protocol (SIP) for asserted identity within trusted networks.

c5: IF A.4/8A THEN m ELSE n/a – – authentication between UA and proxy.

c6: IF A.4/25 THEN o ELSE n/a – – private extensions to the Session Initiation Protocol (SIP) for asserted identity within trusted networks.

c7: IF A.4/6 THEN o ELSE n/a – – timestamping of requests.

c8: IF A.4/26 THEN o ELSE n/a – – a privacy mechanism for the Session Initiation Protocol (SIP).

c9: IF A.4/32 THEN o ELSE n/a – – the P-Called-Party-ID extension.

c10: IF A.4/33 THEN o ELSE n/a – – the P-Visited-Network-ID extension.

c11: IF A.4/34 THEN o ELSE n/a – – the P-Access-Network-Info header extension.

c12: IF A.4/34 AND A.3/1 THEN m ELSE n/a – – the P-Access-Network-Info header extension and UE.

c13: IF A.4/34 AND (A.3/7A OR A.3/7D OR A3A/84) THEN m ELSE n/a – – the P-Access-Network-Info header extension and AS acting as terminating UA, AS acting as third-party call controller or EATF.

c14: IF A.4/36 THEN o ELSE n/a – – the P-Charging-Vector header extension.

c15: IF A.4/36 THEN m ELSE n/a – – the P-Charging-Vector header extension.

c16: IF A.4/35 THEN o ELSE n/a – – the P-Charging-Function-Addresses header extension.

c17: IF A.4/35 THEN m ELSE n/a – – the P-Charging-Function-Addresses header extension.

c18: IF A.4/37 OR A.4/37A THEN o ELSE n/a – – security mechanism agreement for the session initiation protocol or mediasec header field parameter for marking security mechanisms related to media (note 3).

c19: IF A.4/37 OR A.4/37A THEN m ELSE n/a – – security mechanism agreement for the session initiation protocol or mediasec header field parameter for marking security mechanisms related to media.

c20: IF A.4/38 THEN o ELSE n/a – – the Reason header field for the session initiation protocol.

c21: IF A.4/40 THEN o ELSE n/a – – caller preferences for the session initiation protocol.

c22: IF A.4/43 THEN m ELSE n/a – – the SIP Referred-By mechanism.

c23: IF A.4/43 THEN o ELSE n/a – – the SIP Referred-By mechanism.

c24: IF A.4/22 THEN o ELSE n/a – – acting as the notifier of event information.

c25: IF A.4/47 THEN m ELSE n/a – – an extension to the session initiation protocol for request history information.

c26: IF A.4/40 THEN m ELSE n/a – – caller preferences for the session initiation protocol.

c27: IF A.4/60 THEN m ELSE n/a – – SIP location conveyance.

c28: IF (A.3/1 OR A.3A/81) AND A.4/74 THEN o ELSE n/a – – UE, MSC Server enhanced for ICS and SIP extension for the identification of services.

c29: IF A.4/74 THEN o ELSE n/a – – SIP extension for the identification of services.

c30: IF A.4/74 THEN m ELSE n/a – – SIP extension for the identification of services.

c31: IF A.4/71 AND (A.3/9B OR A.3/9C OR A.3/13B OR A.3/13) THEN m ELSE IF A.3/1 AND NOT A.3C/1 – – addressing an amplification vulnerability in session initiation protocol forking proxies, IBCF (IMS-ALG), IBCF (Screening of SIP signalling), ISC gateway function (IMS-ALG), ISC gateway function (Screening of SIP signalling), UE, UE performing the functions of an external attached network.

c32: IF A.4/71 THEN m ELSE n/a – – addressing an amplification vulnerability in session initiation protocol forking proxies.

c33: IF A.4/70 THEN m ELSE n/a – – communications resource priority for the session initiation protocol.

c34: IF A.4/77 THEN m ELSE n/a – – the SIP P-Private-Network-Indication private-header (P-Header).

c37: IF A.4/13 THEN m ELSE IF A.4/13A THEN m ELSE n/a – – SIP INFO method and package framework, legacy INFO usage.

c38: IF A.4/78 THEN m ELSE n/a – – the SIP P-Served-User private header.

c39: IF A.3/1 AND NOT A.3C/1 THEN n/a ELSE o – – UE, UE performing the functions of an external attached network.

c40: IF A.4/91 THEN m ELSE n/a – – the Session-ID header.

c41: IF A.4/100 THEN m ELSE n/a – – indication of features supported by proxy.

c42: IF A.4/100 AND A.3/1 AND NOT A.3C/1 THEN n/a ELSE IF A.4/100 THEN m ELSE n/a – – indication of features supported by proxy, UE, UE performing the functions of an external attached network.

c43: IF A.4/111 THEN m ELSE n/a – – the Relayed-Charge header field extension.

c44: IF A.4/113 AND A.3/1 THEN m ELSE n/a – – the Cellular-Network-Info header extension and UE.

c45: IF A.4/113 AND (A.3/7A OR A.3/7D OR A3A/84) THEN m ELSE n/a – – the Cellular-Network-Info header extension and AS acting as terminating UA, AS acting as third-party call controller or EATF.

c46: IF A.4/25 AND (A.3/7B OR A.3/8 OR A.3A/81A) THEN o ELSE n/a – – private extensions to the Session Initiation Protocol (SIP) for asserted identity within trusted networks and AS acting as originating UA, MRFC, MSC server enhanced for SRVCC using SIP interface.

c47: IF A.4/74 AND A.3/7B THEN o ELSE n/a – – SIP extension for the identification of services and AS acting as originating UA.

c48: IF A.4/119 THEN o ELSE n/a – – Content-ID header field in Session Initiation Protocol (SIP).

c49: IF A.4/119 THEN m ELSE n/a – – Content-ID header field in Session Initiation Protocol (SIP).

NOTE 1: No distinction has been made in these tables between first use of a request on a From/To/Call-ID combination, and the usage in a subsequent one. Therefore the use of "o" etc. above has been included from a viewpoint of first usage.

NOTE 2: The strength of this requirement in RFC 7315 [52] is SHOULD NOT, rather than MUST NOT.

NOTE 3: Support of this header in this method is dependent on the security mechanism and the security architecture which is implemented. Use of this header in this method is not appropriate to the security mechanism defined by 3GPP TS 33.203 [19].

Prerequisite A.5/12 – – OPTIONS request

Table A.78: Supported message bodies within the OPTIONS request

Item

Header

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

1

Table A.79: Void

Prerequisite A.5/13 – – OPTIONS response

Prerequisite: A.6/1 – – Additional for 100 (Trying) response

Table A.79A: Supported header fields within the OPTIONS response

Item

Header field

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

1

Call-ID

[26] 20.8

m

m

[26] 20.8

m

m

2

Content-Length

[26] 20.14

m

m

[26] 20.14

m

m

3

CSeq

[26] 20.16

m

m

[26] 20.16

m

m

4

Date

[26] 20.17

c1

c1

[26] 20.17

m

m

5

From

[26] 20.20

m

m

[26] 20.20

m

m

6

To

[26] 20.39

m

m

[26] 20.39

m

m

7

Via

[26] 20.42

m

m

[26] 20.42

m

m

c1: IF A.4/11 THEN o ELSE n/a – – insertion of date in requests and responses.

Prerequisite A.5/13 – – OPTIONS response for all remaining status-codes

Table A.80: Supported header fields within the OPTIONS response

Item

Header field

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

0A

Allow

[26] 20.5

c12

c12

[26] 20.5

m

m

1

Call-ID

[26] 20.8

m

m

[26] 20.8

m

m

1A

Call-Info

[26] 20.9

o

o

[26] 20.9

o

o

1B

Cellular-Network-Info

7.2.15

n/a

c20

7.2.15

n/a

c21

2

Content-Disposition

[26] 20.11

o

o

[26] 20.11

m

m

3

Content-Encoding

[26] 20.12

o

o

[26] 20.12

m

m

3A

Content-ID

[256] 3.2

o

c23

[256] 3.2

m

c24

4

Content-Language

[26] 20.13

o

o

[26] 20.13

m

m

5

Content-Length

[26] 20.14

m

m

[26] 20.14

m

m

6

Content-Type

[26] 20.15

m

m

[26] 20.15

m

m

7

CSeq

[26] 20.16

m

m

[26] 20.16

m

m

8

Date

[26] 20.17

c1

c1

[26] 20.17

m

m

9

From

[26] 20.20

m

m

[26] 20.20

m

m

9A

Geolocation-Error

[89] 4.3

c14

c14

[89] 4.3

c14

c14

9B

History-Info

[66] 4.1

c13

c13

[66] 4.1

c13

c13

10

MIME-Version

[26] 20.24

o

o

[26] 20.24

m

m

11

Organization

[26] 20.25

o

o

[26] 20.25

o

o

11A

P-Access-Network-Info

[52] 4.4, [52A] 4, [234] 2

c5

c6

[52] 4.4, [52A] 4, [234] 2

c5

c7

11B

P-Asserted-Identity

[34] 9.1

n/a

c22

[34] 9.1

c3

c3

11C

P-Charging-Function-Addresses

[52] 4.5, [52A] 4

c10

c11

[52] 4.5, [52A] 4

c10

c11

11D

P-Charging-Vector

[52] 4.6, [52A] 4

c8

c9

[52] 4.6, [52A] 4

c8

c9

11F

P-Preferred-Identity

[34] 9.2

c3

x

[34] 9.2

n/a

n/a

11G

Privacy

[33] 4.2

c4

c4

[33] 4.2

c4

c4

11H

Recv-Info

[25] 5.2.3

c17

c17

[25] 5.2.3

c17

c17

11I

Relayed-Charge

7.2.12

n/a

c19

7.2.12

n/a

c19

11J

Require

[26] 20.32

m

m

[26] 20.32

m

m

11K

Server

[26] 20.35

o

o

[26] 20.35

o

o

11L

Session-ID

[162]

o

c18

[162]

o

c18

12

Timestamp

[26] 20.38

m

m

[26] 20.38

c2

c2

13

To

[26] 20.39

m

m

[26] 20.39

m

m

13A

User-Agent

[26] 20.41

o

o

[26] 20.41

o

o

14

Via

[26] 20.42

m

m

[26] 20.42

m

m

15

Warning

[26] 20.43

o (note)

o

[26] 20.43

o

o

c1: IF A.4/11 THEN o ELSE n/a – – insertion of date in requests and responses.

c2: IF A.4/6 THEN m ELSE n/a – – timestamping of requests.

c3: IF A.4/25 THEN o ELSE n/a – – private extensions to the Session Initiation Protocol (SIP) for asserted identity within trusted networks.

c4: IF A.4/26 THEN o ELSE n/a – – a privacy mechanism for the Session Initiation Protocol (SIP).

c5: IF A.4/34 THEN o ELSE n/a – – the P-Access-Network-Info header extension.

c6: IF A.4/34 AND A.3/1 THEN m ELSE n/a – – the P-Access-Network-Info header extension and UE.

c7: IF A.4/34 AND (A.3/7A OR A.3/7D OR A3A/84) THEN m ELSE n/a – – the P-Access-Network-Info header extension and AS acting as terminating UA, AS acting as third-party call controller, or EATF.

c8: IF A.4/36 THEN o ELSE n/a – – the P-Charging-Vector header extension.

c9: IF A.4/36 THEN m ELSE n/a – – the P-Charging-Vector header extension.

c10: IF A.4/35 THEN o ELSE n/a – – the P-Charging-Function-Addresses header extension.

c11: IF A.4/35 THEN m ELSE n/a – – the P-Charging-Function-Addresses header extension.

c12: IF A.6/102 OR A.6/18 THEN m ELSE o – – 2xx response, 405 (Method Not Allowed).

c13: IF A.4/47 THEN m ELSE n/a – – an extension to the session initiation protocol for request history information.

c14: IF A.4/60 THEN m ELSE n/a – – SIP location conveyance.

c17: IF A.4/13 THEN m ELSE IF A.4/13A THEN m ELSE n/a – – SIP INFO method and package framework, legacy INFO usage.

c18: IF A.4/91 THEN m ELSE n/a – – the Session-ID header.

c19: IF A.4/111 THEN m ELSE n/a – – the Relayed-Charge header field extension.

c20: IF A.4/113 AND A.3/1 THEN m ELSE n/a – – the Cellular-Network-Info header extension and UE.

c21: IF A.4/113 AND (A.3/7A OR A.3/7D OR A3A/84) THEN m ELSE n/a – – the Cellular-Network-Info header extension and AS acting as terminating UA or AS acting as third-party call controller, or EATF.

c22: IF A.4/25 AND (A.3/7B OR A.3/8) THEN o ELSE n/a – – private extensions to the Session Initiation Protocol (SIP) for asserted identity within trusted networks and AS acting as originating UA, MRFC.

c23: IF A.4/119 THEN o ELSE n/a – – Content-ID header field in Session Initiation Protocol (SIP).

c24: IF A.4/119 THEN m ELSE n/a – – Content-ID header field in Session Initiation Protocol (SIP).

NOTE: RFC 3261 [26] gives the status of this header as SHOULD rather than OPTIONAL.

Prerequisite A.5/13 – – OPTIONS response

Prerequisite: A.6/102 – – Additional for 2xx response

Table A.81: Supported header fields within the OPTIONS response

Item

Header field

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

1

Accept

[26] 20.1

m

m

[26] 20.1

m

m

1A

Accept-Encoding

[26] 20.2

m

m

[26] 20.2

m

m

1B

Accept-Language

[26] 20.3

m

m

[26] 20.3

m

m

1C

Accept-Resource-Priority

[116] 3.2

c14

c14

[116] 3.2

c14

c14

2

Allow-Events

[28] 8.2.2

c3

c3

[28] 8.2.2

c4

c4

3

Authentication-Info

[26] 20.6

c1

c1

[26] 20.6

c2

c2

5

Contact

[26] 20.10

o

o

[26] 20.10

o

o

6

Feature-Caps

[190]

c16

c16

[190]

c15

c15

7

Recv-Info

[25] 5.2.3

c6

c6

[25] 5.2.3

c6

c6

12

Supported

[26] 20.37

m

m

[26] 20.37

m

m

c1: IF A.4/7 THEN o ELSE n/a – – authentication between UA and UA.

c2: IF A.4/7 THEN m ELSE n/a – – authentication between UA and UA.

c3: IF A.4/22 THEN o ELSE n/a – – acting as the notifier of event information.

c4: IF A.4/23 THEN m ELSE n/a – – acting as the subscriber to event information.

c6: IF A.4/13 THEN m ELSE n/a – – SIP INFO method and package framework.

c14: IF A.4/70 THEN m ELSE n/a – – communications resource priority for the session initiation protocol.

c15: IF A.4/100 THEN m ELSE n/a – – indication of features supported by proxy.

c16: IF A.4/100 AND A.3/1 AND NOT A.3C/1 THEN n/a ELSE IF A.4/100 THEN m ELSE n/a – – indication of features supported by proxy, UE, UE performing the functions of an external attached network.

Prerequisite A.5/13 – – OPTIONS response

Prerequisite: A.6/103 OR A.6/104 OR A.6/105 OR A.6/106 – – Additional for 3xx – 6xx response

Table A.81A: Supported header fields within the OPTIONS response

Item

Header field

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

1

Error-Info

[26] 20.18

o

o

[26] 20.18

o

o

2

Response-Source

7.2.17

n/a

c1

7.2.17

n/a

c1

c1: IF A.4/115 THEN o ELSE n/a – – use of the Response-Source header field in SIP error responses?

Prerequisite A.5/13 – – OPTIONS response

Prerequisite: A.6/103 OR A.6/35 – – Additional for 3xx or 485 (Ambiguous) response

Table A.82: Supported header fields within the OPTIONS response

Item

Header field

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

3

Contact

[26] 20.10

o (note)

o

[26] 20.10

m

m

NOTE: RFC 3261 [26] gives the status of this header as SHOULD rather than OPTIONAL.

Prerequisite A.5/13 – – OPTIONS response

Prerequisite: A.6/14 – – Additional for 401 (Unauthorized) response

Table A.83: Supported header fields within the OPTIONS response

Item

Header field

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

4

Proxy-Authenticate

[26] 20.27

c1

c1

[26] 20.27

c1

c1

10

WWW-Authenticate

[26] 20.44

o

o

[26] 20.44

o

o

c1: IF A.4/7 THEN m ELSE n/a – – support of authentication between UA and UA.

Prerequisite A.5/13 – – OPTIONS response

Prerequisite: A.6/17 OR A.6/23 OR A.6/30 OR A.6/36 OR A.6/42 OR A.6/45 OR A.6/50 OR A.6/51 – – Additional for 404 (Not Found), 413 (Request Entity Too Large), 480(Temporarily not available), 486 (Busy Here), 500 (Internal Server Error), 503 (Service Unavailable), 600 (Busy Everywhere), 603 (Decline) response.

Table A.84: Supported header fields within the OPTIONS response

Item

Header field

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

5

Retry-After

[26] 20.33

o

o

[26] 20.33

o

o

Table A.85: Void

Prerequisite A.5/13 – – OPTIONS response

Prerequisite: A.6/20 – – Additional for 407 (Proxy Authentication Required) response

Table A.86: Supported header fields within the OPTIONS response

Item

Header field

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

4

Proxy-Authenticate

[26] 20.27

c1

c1

[26] 20.27

c1

c1

8

WWW-Authenticate

[26] 20.44

o

o

[26] 20.44

o

o

c1: IF A.4/7 THEN m ELSE n/a – – support of authentication between UA and UA.

Table A.86A: Void

Prerequisite A.5/13 – – OPTIONS response

Prerequisite: A.6/25 – – Additional for 415 (Unsupported Media Type) response

Table A.87: Supported header fields within the OPTIONS response

Item

Header field

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

1

Accept

[26] 20.1

o.1

o.1

[26] 20.1

m

m

2

Accept-Encoding

[26] 20.2

o.1

o.1

[26] 20.2

m

m

3

Accept-Language

[26] 20.3

o.1

o.1

[26] 20.3

m

m

o.1 At least one of these capabilities is supported.

Prerequisite A.5/13 – – OPTIONS response

Prerequisite: A.6/26A – – Additional for 417 (Unknown Resource-Priority) response

Table A.87A: Supported header fields within the OPTIONS response

Item

Header field

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

1

Accept-Resource-Priority

[116] 3.2

c1

c1

[116] 3.2

c1

c1

c1: IF A.4/70 THEN m ELSE n/a – – communications resource priority for the session initiation protocol.

Prerequisite A.5/13 – – OPTIONS response

Prerequisite: A.6/27 – – Additional for 420 (Bad Extension) response

Table A.88: Supported header fields within the OPTIONS response

Item

Header field

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

7

Unsupported

[26] 20.40

m

m

[26] 20.40

m

m

Prerequisite A.5/13 – – OPTIONS response

Prerequisite: A.6/28 OR A.6/41A – – Additional 421 (Extension Required), 494 (Security Agreement Required) response

Table A.88A: Supported header fields within the OPTIONS response

Item

Header field

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

3

Security-Server

[48] 2

x

x

[48] 2

c1

c1

c1: IF A.4/37 THEN m ELSE n/a – – security mechanism agreement for the session initiation protocol.

Table A.89: Void

Prerequisite A.5/13 – – OPTIONS response

Prerequisite: A.6/46 – – Additional for 504 (Server Time-out) response

Table A.89A: Supported header fields within the OPTIONS response

Item

Header field

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

1

Restoration-Info

subclause 7.2.11

n/a

c1

subclause 7.2.11

n/a

n/a

c1: IF A.4/110 THEN o ELSE n/a – – HSS based P-CSCF restoration.

Prerequisite A.5/13 – – OPTIONS response

Table A.90: Supported message bodies within the OPTIONS response

Item

Header

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

1

application/cccex

[9B]

n/a

c1

[9B]

n/a

c2

c1: IF A.3A/12 THEN o ELSE n/a – – conference participant.

c2: IF A.3A/11 THEN o ELSE n/a – – conference focus.

A.2.1.4.10 PRACK method

Prerequisite A.5/14 – – PRACK request

Table A.91: Supported header fields within the PRACK request

Item

Header field

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

1

Accept

[26] 20.1

o

o

[26] 20.1

m

m

1A

Accept-Contact

[56B] 9.2

c15

c15

[56B] 9.2

c18

c18

2

Accept-Encoding

[26] 20.2

o

o

[26] 20.2

m

m

3

Accept-Language

[26] 20.3

o

o

[26] 20.3

m

m

3A

Allow

[26] 20.5

o

o

[26] 20.5

m

m

4

Allow-Events

[28] 8.2.2

c1

c1

[28] 8.2.2

c2

c2

5

Authorization

[26] 20.7

c3

c3

[26] 20.7

c3

c3

6

Call-ID

[26] 20.8

m

m

[26] 20.8

m

m

6A

Cellular-Network-Info

7.2.15

n/a

c41

7.2.15

n/a

c42

7

Content-Disposition

[26] 20.11

o

o

[26] 20.11

m

m

8

Content-Encoding

[26] 20.12

o

o

[26] 20.12

m

m

8A

Content-ID

[256] 3.2

o

c44

[256] 3.2

m

c45

9

Content-Language

[26] 20.13

o

o

[26] 20.13

m

m

10

Content-Length

[26] 20.14

m

m

[26] 20.14

m

m

11

Content-Type

[26] 20.15

m

m

[26] 20.15

m

m

12

CSeq

[26] 20.16

m

m

[26] 20.16

m

m

13

Date

[26] 20.17

c4

c4

[26] 20.17

m

m

14

From

[26] 20.20

m

m

[26] 20.20

m

m

14A

Max-Breadth

[117] 5.8

n/a

c21

[117] 5.8

c22

c22

15

Max-Forwards

[26] 20.22

m

m

[26] 20.22

n/a

c34

16

MIME-Version

[26] 20.24

o

o

[26] 20.24

m

m

16A

P-Access-Network-Info

[52] 4.4, [234] 2

c9

c10

[52] 4.4, [234] 2

c9

c11

16B

P-Charging-Function-Addresses

[52] 4.5

c13

c14

[52] 4.5

c13

c14

16C

P-Charging-Vector

[52] 4.6

c12

c40

[52] 4.6

c12

c40

16E

P-Early-Media

[109] 8

c39

c39

[109] 8

c39

c39

16EA

Priority-Share

Subclause 7.2.16

n/a

c43

Subclause 7.2.16

n/a

c43

16F

Privacy

[33] 4.2

c6

n/a

[33] 4.2

c6

n/a

17

Proxy-Authorization

[26] 20.28

c5

c5

[26] 20.28

n/a

n/a

18

Proxy-Require

[26] 20.29

o

n/a

[26] 20.29

n/a

n/a

19

RAck

[27] 7.2

m

m

[27] 7.2

m

m

19A

Reason

[34A] 2

c7

c7

[34A] 2

c7

c7

20

Record-Route

[26] 20.30

n/a

c34

[26] 20.30

n/a

c34

20A

Recv-Info

[25] 5.2.3

c35

c35

[25] 5.2.3

c35

c35

20B

Referred-By

[59] 3

c16

c16

[59] 3

c17

c17

20C

Reject-Contact

[56B] 9.2

c15

c15

[56B] 9.2

c18

c18

20D

Relayed-Charge

7.2.12

n/a

c37

7.2.12

n/a

c37

20E

Request-Disposition

[56B] 9.1

c15

c15

[56B] 9.1

c18

c18

21

Require

[26] 20.32

m

m

[26] 20.32

m

m

21A

Resource-Priority

[116] 3.1

c33

c33

[116] 3.1

c33

c33

21B

Resource-Share

Subclause 7.2.13

n/a

c38

Subclause 7.2.13

n/a

c38

22

Route

[26] 20.34

m

m

[26] 20.34

n/a

c34

22A

Session-ID

[162]

o

c36

[162]

o

c36

23

Supported

[26] 20.37

o

o

[26] 20.37

m

m

24

Timestamp

[26] 20.38

c8

c8

[26] 20.38

m

m

25

To

[26] 20.39

m

m

[26] 20.39

m

m

26

User-Agent

[26] 20.41

o

o

[26] 20.41

o

o

27

Via

[26] 20.42

m

m

[26] 20.42

m

m

c1: IF A.4/22 THEN o ELSE n/a – – acting as the notifier of event information.

c2: IF A.4/23 THEN m ELSE n/a – – acting as the subscriber to event information.

c3: IF A.4/7 THEN m ELSE n/a – – authentication between UA and UA.

c4: IF A.4/11 THEN o ELSE n/a – – insertion of date in requests and responses.

c5: IF A.4/8A THEN m ELSE n/a – – authentication between UA and proxy.

c6: IF A.4/26 THEN o ELSE n/a – – a privacy mechanism for the Session Initiation Protocol (SIP).

c7: IF A.4/38 THEN o ELSE n/a – – the Reason header field for the session initiation protocol.

c8: IF A.4/6 THEN o ELSE n/a – – timestamping of requests.

c9: IF A.4/34 THEN o ELSE n/a – – the P-Access-Network-Info header extension.

c10: IF A.4/34 AND (A.3/1 OR A.3/2A OR A.3/7 OR A.3A/81) THEN m ELSE n/a – – the P-Access-Network-Info header extension and UE, P-CSCF (IMS-ALG), AS or MSC server enhanced for ICS.

c11: IF A.4/34 AND (A.3/2A OR A.3A/81 OR A.3/7A OR A.3/7D OR A3A/84) THEN m ELSE n/a – – the P-Access-Network-Info header extension and P-CSCF (IMS-ALG), MSC server enhanced for ICS, AS acting as terminating UA, AS acting as third-party call controller or EATF.

c12: IF A.4/36 THEN o ELSE n/a – – the P-Charging-Vector header extension.

c13: IF A.4/35 THEN o ELSE n/a – – the P-Charging-Function-Addresses header extension.

c14: IF A.4/35 THEN m ELSE n/a – – the P-Charging-Function-Addresses header extension.

c15: IF A.4/40 THEN o ELSE n/a – – caller preferences for the session initiation protocol.

c16: IF A.4/43 THEN m ELSE n/a – – the SIP Referred-By mechanism.

c17: IF A.4/43 THEN o ELSE n/a – – the SIP Referred-By mechanism.

c18: IF A.4/40 THEN m ELSE n/a – – caller preferences for the session initiation protocol.

c21: IF A.4/71 AND (A.3/9B OR A.3/9C OR A.3/13B OR A.3/13C) THEN m ELSE IF A.3/1 AND NOT A.3C/1 THEN n/a ELSE o – – addressing an amplification vulnerability in session initiation protocol forking proxies, IBCF (IMS-ALG), IBCF (Screening of SIP signalling), ISC gateway function (IMS-ALG), ISC gateway function (Screening of SIP signalling), UE, UE performing the functions of an external attached network.

c22: IF A.4/71 THEN m ELSE n/a – – addressing an amplification vulnerability in session initiation protocol forking proxies.

c33: IF A.4/70 THEN m ELSE n/a – – communications resource priority for the session initiation protocol.

c34: IF A.3/1 AND NOT A.3C/1 THEN n/a ELSE o – – UE, UE performing the functions of an external attached network.

c35: IF A.4/13 THEN m ELSE IF A.4/13A THEN m ELSE n/a – – SIP INFO method and package framework, legacy INFO usage.

c36: IF A.4/91 THEN m ELSE n/a – – the Session-ID header.

c37: IF A.4/111 THEN m ELSE n/a – – the Relayed-Charge header field extension.

c38 IF A.4/112 THEN o ELSE n/a – – resource sharing.

c39: IF A.4/66 THEN m ELSE n/a – – The SIP P-Early-Media private header extension for authorization of early media.

c40: IF A.4/36 THEN m ELSE n/a – – the P-Charging-Vector header extension.

c41: IF A.4/113 AND (A.3/1 OR A.3/2A OR A.3/7) THEN m ELSE n/a – – the Cellular-Network-Info header extension and UE, P-CSCF (IMS-ALG) or AS.

c42: IF A.4/113 AND (A.3/2A OR A.3/7A OR A.3/7D OR A3A/84) THEN m ELSE n/a – – the Cellular-Network-Info header extension and P-CSCF (IMS-ALG), AS acting as terminating UA or AS acting as third-party call controller or EATF.

c43: IF A.4/114 THEN o ELSE n/a – – priority sharing.

c44: IF A.4/119 THEN o ELSE n/a – – Content-ID header field in Session Initiation Protocol (SIP).

c45: IF A.4/119 THEN m ELSE n/a – – Content-ID header field in Session Initiation Protocol (SIP).

Prerequisite A.5/14 – – PRACK request

Table A.92: Supported message bodies within the PRACK request

Item

Header

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

1

Table A.93: Void

Prerequisite A.5/15 – – PRACK response

Prerequisite: A.6/1 – – Additional for 100 (Trying) response

Table A.93A: Supported header fields within the PRACK response

Item

Header field

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

1

Call-ID

[26] 20.8

m

m

[26] 20.8

m

m

2

Content-Length

[26] 20.14

m

m

[26] 20.14

m

m

3

CSeq

[26] 20.16

m

m

[26] 20.16

m

m

4

Date

[26] 20.17

c1

c1

[26] 20.17

m

m

5

From

[26] 20.20

m

m

[26] 20.20

m

m

6

To

[26] 20.39

m

m

[26] 20.39

m

m

7

Via

[26] 20.42

m

m

[26] 20.42

m

m

c1: IF A.4/11 THEN o ELSE n/a – – insertion of date in requests and responses.

Prerequisite A.5/15 – – PRACK response for all remaining status-codes

Table A.94: Supported header fields within the PRACK response

Item

Header field

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

0A

Allow

[26] 20.5

c9

c9

[26] 20.5

m

m

1

Call-ID

[26] 20.8

m

m

[26] 20.8

m

m

1A

Cellular-Network-Info

7.2.15

n/a

c17

7.2.15

n/a

c18

2

Content-Disposition

[26] 20.11

o

o

[26] 20.11

m

m

3

Content-Encoding

[26] 20.12

o

o

[26] 20.12

m

m

3A

Content-ID

[256] 3.2

o

c19

[256] 3.2

m

c20

4

Content-Language

[26] 20.13

o

o

[26] 20.13

m

m

5

Content-Length

[26] 20.14

m

m

[26] 20.14

m

m

6

Content-Type

[26] 20.15

m

m

[26] 20.15

m

m

7

CSeq

[26] 20.16

m

m

[26] 20.16

m

m

8

Date

[26] 20.17

c1

c1

[26] 20.17

m

m

9

From

[26] 20.20

m

m

[26] 20.20

m

m

10

MIME-Version

[26] 20.24

o

o

[26] 20.24

m

m

10A

P-Access-Network-Info

[52] 4.4, [52A] 4, [234] 2

c3

c4

[52] 4.4, [52A] 4, [234] 2

c3

c5

10B

P-Charging-Function-Addresses

[52] 4.5, [52A] 4

c7

c8

[52] 4.5, [52A] 4

c7

c8

10C

P-Charging-Vector

[52] 4.6, [52A] 4

c6

c16

[52] 4.6, [52A] 4

c6

c16

10F

Privacy

[33] 4.2

c2

n/a

[33] 4.2

c2

n/a

10G

Recv-Info

[25] 5.2.3

c13

c13

[25] 5.2.3

c13

c13

10H

Relayed-Charge

7.2.12

n/a

c15

7.2.12

n/a

c15

10I

Require

[26] 20.32

m

m

[26] 20.32

m

m

10J

Server

[26] 20.35

o

o

[26] 20.35

o

o

10K

Session-ID

[162]

o

c14

[162]

o

c14

11

Timestamp

[26] 20.38

m

m

[26] 20.38

c2

c2

12

To

[26] 20.39

m

m

[26] 20.39

m

m

12A

User-Agent

[26] 20.41

o

o

[26] 20.41

o

o

13

Via

[26] 20.42

m

m

[26] 20.42

m

m

14

Warning

[26] 20.43

o (note)

o

[26] 20.43

o

o

c1: IF A.4/11 THEN o ELSE n/a – – insertion of date in requests and responses.

c2: IF A.4/26 THEN o ELSE n/a – – a privacy mechanism for the Session Initiation Protocol (SIP).

c3: IF A.4/34 THEN o ELSE n/a – – the P-Access-Network-Info header extension.

c4: IF A.4/34 AND A.3/1 THEN m ELSE n/a – – the P-Access-Network-Info header extension and UE.

c5: IF A.4/34 AND (A.3/7A OR A.3/7D OR A3A/84) THEN m ELSE n/a – – the P-Access-Network-Info header extension and AS acting as terminating UA, AS acting as third-party call controller or EATF.

c6: IF A.4/36 THEN o ELSE n/a – – the P-Charging-Vector header extension.

c7: IF A.4/35 THEN o ELSE n/a – – the P-Charging-Function-Addresses header extension.

c8: IF A.4/35 THEN m ELSE n/a – – the P-Charging-Function-Addresses header extension.

c9: IF A.6/18 THEN m ELSE o – – 405 (Method Not Allowed)

c13: IF A.4/13 THEN m ELSE IF A.4/13A THEN m ELSE n/a – – SIP INFO method and package framework, legacy INFO usage.

c14: IF A.4/91 THEN m ELSE n/a – – the Session-ID header.

c15: IF A.4/111 THEN m ELSE n/a – – the Relayed-Charge header field extension.

c16: IF A.4/36 THEN m ELSE n/a – – the P-Charging-Vector header extension.

c17: IF A.4/113 AND A.3/1 THEN m ELSE n/a – – the Cellular-Network-Info header extension and UE.

c18: IF A.4/113 AND (A.3/7A OR A.3/7D OR A3A/84) THEN m ELSE n/a – – the Cellular-Network-Info header extension and AS acting as terminating UA or AS acting as third-party call controller or EATF.

c19: IF A.4/119 THEN o ELSE n/a – – Content-ID header field in Session Initiation Protocol (SIP).

c20: IF A.4/119 THEN m ELSE n/a – – Content-ID header field in Session Initiation Protocol (SIP).

NOTE: RFC 3261 [26] gives the status of this header as SHOULD rather than OPTIONAL.

Prerequisite A.5/15 – – PRACK response

Prerequisite: A.6/102 – – Additional for 2xx response

Table A.95: Supported header fields within the PRACK response

Item

Header field

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

0A

Accept-Resource-Priority

[116] 3.2

c14

c14

[116] 3.2

c14

c14

0B

Allow-Events

[28] 8.2.2

c3

c3

[28] 8.2.2

c4

c4

0C

Authentication-Info

[26] 20.6

c1

c1

[26] 20.6

c2

c2

0D

P-Early-Media

[109] 8

c5

c5

[109] 8

c5

c5

1

Priority-Share

Subclause 7.2.16

n/a

c16

Subclause 7.2.16

n/a

c16

2A

Resource-Share

Subclause 7.2.13

n/a

c15

Subclause 7.2.13

n/a

c15

3

Supported

[26] 20.37

m

m

[26] 20.37

m

m

c1: IF A.4/7 THEN o ELSE n/a – – authentication between UA and UA.

c2: IF A.4/7 THEN m ELSE n/a – – authentication between UA and UA.

c3: IF A.4/22 THEN o ELSE n/a – – acting as the notifier of event information.

c4: IF A.4/23 THEN m ELSE n/a – – acting as the subscriber to event information.

c5: IF A.4/66 THEN m ELSE n/a – – the SIP P-Early-Media private header extension for authorization of early media.

c14: IF A.4/70 THEN m ELSE n/a – – communications resource priority for the session initiation protocol.

c15: IF A.4/112 THEN o ELSE n/a – – resource sharing.

c16: IF A.4/114 THEN o ELSE n/a – – priority sharing.

Prerequisite A.5/15 – – PRACK response

Prerequisite: A.6/103 OR A.6/104 OR A.6/105 OR A.6/106 – – Additional for 3xx – 6xx response

Table A.95A: Supported header fields within the PRACK response

Item

Header field

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

1

Error-Info

[26] 20.18

o

o

[26] 20.18

o

o

2

Response-Source

7.2.17

n/a

c1

7.2.17

n/a

c1

c1: IF A.4/115 THEN o ELSE n/a – – use of the Response-Source header field in SIP error responses?

Prerequisite A.5/15 – – PRACK response

Prerequisite: A.6/103 OR A.6/35 – – Additional for 3xx or 485 (Ambiguous) response

Table A.96: Supported header fields within the PRACK response

Item

Header field

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

1

Contact

[26] 20.10

o (note)

o

[26] 20.10

m

m

NOTE: RFC 3261 [26] gives the status of this header field as SHOULD rather than OPTIONAL.

Prerequisite A.5/15 – – PRACK response

Prerequisite: A.6/14 – – Additional for 401 (Unauthorized) response

Table A.97: Supported header fields within the PRACK response

Item

Header field

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

2

Proxy-Authenticate

[26] 20.27

c1

c1

[26] 20.27

c1

c1

8

WWW-Authenticate

[26] 20.44

m

m

[26] 20.44

m

m

c1: IF A.4/7 THEN m ELSE n/a – – support of authentication between UA and UA.

Prerequisite A.5/15 – – PRACK response

Prerequisite: A.6/17 OR A.6/23 OR A.6/30 OR A.6/36 OR A.6/42 OR A.6/45 OR A.6/50 OR A.6/51 – – Additional for 404 (Not Found), 413 (Request Entity Too Large), 480(Temporarily not available), 486 (Busy Here), 500 (Internal Server Error), 503 (Service Unavailable), 600 (Busy Everywhere), 603 (Decline) response.

Table A.98: Supported header fields within the PRACK response

Item

Header field

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

3

Retry-After

[26] 20.33

o

o

[26] 20.33

o

o

Table A.99: Void

Prerequisite A.5/15 – – PRACK response

Prerequisite: A.6/20 – – Additional for 407 (Proxy Authentication Required) response

Table A.100: Supported header fields within the PRACK response

Item

Header field

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

2

Proxy-Authenticate

[26] 20.27

c1

c1

[26] 20.27

c1

c1

6

WWW-Authenticate

[26] 20.44

o

o

[26] 20.44

o

o

c1: IF A.4/7 THEN m ELSE n/a – – support of authentication between UA and UA.

Prerequisite A.5/15 – – PRACK response

Prerequisite: A.6/25 – – Additional for 415 (Unsupported Media Type) response

Table A.101: Supported header fields within the PRACK response

Item

Header field

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

1

Accept

[26] 20.1

o.1

o.1

[26] 20.1

m

m

2

Accept-Encoding

[26] 20.2

o.1

o.1

[26] 20.2

m

m

3

Accept-Language

[26] 20.3

o.1

o.1

[26] 20.3

m

m

Prerequisite A.5/15 – – PRACK response

Prerequisite: A.6/26A – – Additional for 417 (Unknown Resource-Priority) response

Table A.101A: Supported header fields within the PRACK response

Item

Header field

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

1

Accept-Resource-Priority

[116] 3.2

c1

c1

[116] 3.2

c1

c1

c1: IF A.4/70 THEN m ELSE n/a – – communications resource priority for the session initiation protocol.

Prerequisite A.5/15 – – PRACK response

Prerequisite: A.6/27 – – Additional for 420 (Bad Extension) response

Table A.102: Supported header fields within the PRACK response

Item

Header field

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

5

Unsupported

[26] 20.40

m

m

[26] 20.40

m

m

Prerequisite A.5/15 – – PRACK response

Prerequisite: A.6/28 OR A.6/41A – – Additional for 421 (Extension Required), 494 (Security Agreement Required) response

Table A.102A: Supported header fields within the PRACK response

Item

Header field

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

3

Security-Server

[48] 2

x

x

[48] 2

c1

c1

c1: IF A.4/37 THEN m ELSE n/a – – security mechanism agreement for the session initiation protocol.

Table A.103: Void

Prerequisite A.5/15 – – PRACK response

Table A.104: Supported message bodies within the PRACK response

Item

Header

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

1

A.2.1.4.10A PUBLISH method

Prerequisite A.5/15A – PUBLISH request

Table A.104A: Supported header fields within the PUBLISH request

Item

Header field

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

1

Accept-Contact

[56B] 9.2

c22

c22

[56B] 9.2

c28

c28

2

Allow

[26] 20.5

o

o

[26] 20.5

m

m

3

Allow-Events

[28] 8.2.2

c1

c1

[28] 8.2.2

c2

c2

4

Authorization

[26] 20.7

c3

c3

[26] 20.7

c3

c3

5

Call-ID

[26] 20.8

m

m

[26] 20.8

m

m

6

Call-Info

[26] 20.9

o

o

[26] 20.9

o

o

6A

Cellular-Network-Info

7.2.15

n/a

c43

7.2.15

n/a

c44

6B

Contact

[70] 4

o

o

[70] 6

n/a

n/a

7

Content-Disposition

[26] 20.11

o

o

[26] 20.11

m

m

8

Content-Encoding

[26] 20.12

o

o

[26] 20.12

m

m

8A

Content-ID

[256] 3.2

o

c47

[256] 3.2

m

c48

9

Content-Language

[26] 20.13

o

o

[26] 20.13

m

m

10

Content-Length

[26] 20.14

m

m

[26] 20.14

m

m

11

Content-Type

[26] 20.15

m

m

[26] 20.15

m

m

12

CSeq

[26] 20.16

m

m

[26] 20.16

m

m

13

Date

[26] 20.17

c4

c4

[26] 20.17

m

m

14

Event

[70] 4, 6

m

m

[70] 4, 6

m

m

15

Expires

[26] 20.19, [70] 4, 5, 6

o

o

[26] 20.19, [70] 4, 5, 6

m

m

15A

Feature-Caps

[190]

c41

c41

[190]

c40

c40

16

From

[26] 20.20

m

m

[26] 20.20

m

m

16A

Geolocation

[89] 4.1

c38

c38

[89] 4.1

c38

c38

16B

Geolocation-Routing

[89] 4.2

c38

c38

[89] 4.2

c38

c38

16C

History-Info

[66] 4.1

c27

c27

[66] 4.1

c27

c27

17

In-Reply-To

[26] 20.21

o

o

[26] 20.21

o

o

17A

Max-Breadth

[117] 5.8

n/a

c23

[117] 5.8

c24

c24

18

Max-Forwards

[26] 20.22

m

m

[26] 20.22

n/a

c37

19

MIME-Version

[26] 20.24

o

o

[26] 20.24

m

m

20

Organization

[26] 20.25

o

o

[26] 20.25

o

o

21

P-Access-Network-Info

[52] 4.4, [234] 2

c15

c16

[52] 4.4, [234] 2

c15

c17

22

P-Asserted-Identity

[34] 9.1

n/a

c45

[34] 9.1

c11

c11

22A

P-Asserted-Service

[121] 4.1

n/a

c46

[121] 4.1

c31

c31

23

P-Called-Party-ID

[52] 4.2

x

x

[52] 4.2

c13

c13

24

P-Charging-Function-Addresses

[52] 4.5

c20

c21

[52] 4.5

c20

c21

25

P-Charging-Vector

[52] 4.6

c18

c19

[52] 4.6

c18

c19

26

P-Preferred-Identity

[34] 9.2

c11

c7

[34] 9.2

n/a

n/a

26A

P-Preferred-Service

[121] 4.2

c31

c30

[121] 4.2

n/a

n/a

26B

P-Private-Network-Indication

[134]

c33

c33

[134]

c33

c33

26C

P-Profile-Key

[97] 5

n/a

n/a

[97] 5

n/a

n/a

26D

P-Served-User

[133] 6

c36

c36

[133] 6

c36

c36

26E

P-User-Database

[82] 4

n/a

n/a

[82] 4

n/a

n/a

27

P-Visited-Network-ID

[52] 4.3

x (note 3)

x

[52] 4.3

c14

n/a

28

Priority

[26] 20.26

o

o

[26] 20.26

o

o

29

Privacy

[33] 4.2

c12

c12

[33] 4.2

c12

c12

30

Proxy-Authorization

[26] 20.28

c5

c5

[26] 20.28

n/a

n/a

31

Proxy-Require

[26] 20.29

o

n/a

[26] 20.29

n/a

n/a

32

Reason

[34A] 2

c8

c8

[34A] 2

c8

c8

33A

Referred-By

[59] 3

c25

c25

[59] 3

c26

c26

34

Reject-Contact

[56B] 9.2

c22

c22

[56B] 9.2

c28

c28

34A

Relayed-Charge

7.2.12

n/a

c42

7.2.12

n/a

c42

34B

Reply-To

[26] 20.31

o

o

[26] 20.31

o

o

35

Request-Disposition

[56B] 9.1

c22

c22

[56B] 9.1

c28

c28

36

Require

[26] 20.32

m

m

[26] 20.32

m

m

36A

Resource-Priority

[116] 3.1

c29

c29

[116] 3.1

c29

c29

37

Route

[26] 20.34

m

m

[26] 20.34

n/a

c37

38

Security-Client

[48] 2.3.1

c9

c9

[48] 2.3.1

n/a

n/a

39

Security-Verify

[48] 2.3.1

c10

c10

[48] 2.3.1

n/a

n/a

39A

Session-ID

[162]

o

c39

[162]

o

c39

40

SIP-If-Match

[70] 11.3.2

o

o

[70] 11.3.2

m

m

41

Subject

[26] 20.36

o

o

[26] 20.36

o

o

42

Supported

[26] 20.37, [26] 7.1

o

o

[26] 20.37, [26] 7.1

m

m

43

Timestamp

[26] 20.38

c6

c6

[26] 20.38

m

m

44

To

[26] 20.39

m

m

[26] 20.39

m

m

45

User-Agent

[26] 20.41

o

o

[26] 20.41

o

o

46

Via

[26] 20.42

m

m

[26] 20.42

m

m

c1: IF A.4/22 THEN o ELSE n/a – – acting as the notifier of event information.

c2: IF A.4/23 THEN m ELSE n/a – – acting as the subscriber to event information.

c3: IF A.4/7 THEN m ELSE n/a – – authentication between UA and UA.

c4: IF A.4/11 THEN o ELSE n/a – – insertion of date in requests and responses.

c5: IF A.4/8A THEN m ELSE n/a – – authentication between UA and proxy.

c6: IF A.4/6 THEN o ELSE n/a – – timestamping of requests.

c7: IF A.3/1 AND A.4/25 THEN o ELSE n/a – – UE and private extensions to the Session Initiation Protocol (SIP) for asserted identity within trusted networks.

c8: IF A.4/38 THEN o ELSE n/a – – the Reason header field for the session initiation protocol.

c9: IF A.4/37 OR A.4/37A THEN o ELSE n/a – – security mechanism agreement for the session initiation protocol or mediasec header field parameter for marking security mechanisms related to media (note 1).

c10: IF A.4/37 OR A.4/37A THEN m ELSE n/a – – security mechanism agreement for the session initiation protocol or mediasec header field parameter for marking security mechanisms related to media.

c11: IF A.4/25 THEN o ELSE n/a – – private extensions to the Session Initiation Protocol (SIP) for asserted identity within trusted networks.

c12: IF A.4/26 THEN o ELSE n/a – – a privacy mechanism for the Session Initiation Protocol (SIP).

c13: IF A.4/32 THEN o ELSE n/a – – the P-Called-Party-ID extension.

c14: IF A.4/33 THEN o ELSE n/a – – the P-Visited-Network-ID extension.

c15: IF A.4/34 THEN o ELSE n/a – – the P-Access-Network-Info header extension.

c16: IF A.4/34 AND A.3/1 THEN m ELSE n/a – – the P-Access-Network-Info header extension and UE.

c17: IF A.4/34 AND (A.3/7A OR A.3/7D) THEN m ELSE n/a – – the P-Access-Network-Info header extension and AS acting as terminating UA or AS acting as third-party call controller.

c18: IF A.4/36 THEN o ELSE n/a – – the P-Charging-Vector header extension.

c19: IF A.4/36 THEN m ELSE n/a – – the P-Charging-Vector header extension.

c20: IF A.4/35 THEN o ELSE n/a – – the P-Charging-Function-Addresses header extension.

c21: IF A.4/35 THEN m ELSE n/a – – the P-Charging-Function-Addresses header extension.

c22: IF A.4/40 THEN o ELSE n/a – – caller preferences for the session initiation protocol.

c23: IF A.4/71 AND (A.3/9B OR A.3/9C OR A.3/13B OR A.3/13C) THEN m ELSE IF A.3/1 AND NOT A.3C/1 THEN n/a ELSE o – – addressing an amplification vulnerability in session initiation protocol forking proxies, IBCF (IMS-ALG), IBCF (Screening of SIP signalling), ISC gateway function (IMS-ALG), ISC gateway function (Screening of SIP signalling), UE, UE performing the functions of an external attached network.

c24: IF A.4/71 THEN m ELSE n/a – – addressing an amplification vulnerability in session initiation protocol forking proxies.

c25: IF A.4/43 THEN m ELSE n/a – – the SIP Referred-By mechanism.

c26: IF A.4/43 THEN o ELSE n/a – – the SIP Referred-By mechanism.

c27: IF A.4/47 THEN m ELSE n/a – – an extension to the session initiation protocol for request history information.

c28: IF A.4/40 THEN m ELSE n/a – – caller preferences for the session initiation protocol.

c29: IF A.4/70B THEN m ELSE n/a – – inclusion of CANCEL, BYE, REGISTER and PUBLISH in communications resource priority for the session initiation protocol.

c30: IF (A.3/1 OR A.3A/81) AND A.4/74 THEN o ELSE n/a – – UE, MSC Server enhanced for ICS and SIP extension for the identification of services.

c31: IF A.4/74 THEN o ELSE n/a – – SIP extension for the identification of services.

c32: IF A.4/74 THEN m ELSE n/a – – SIP extension for the identification of services.

c33: IF A.4/77 THEN m ELSE n/a – – the SIP P-Private-Network-Indication private-header (P-Header).

c36: IF A.4/78 THEN m ELSE n/a – – the SIP P-Served-User private header.

c37: IF A.3/1 AND NOT A.3C/1 THEN n/a ELSE o – – UE, UE performing the functions of an external attached network.

c38: IF A.4/60 THEN m ELSE n/a – – SIP location conveyance.

c39: IF A.4/91 THEN m ELSE n/a – – the Session-ID header.

c40: IF A.4/100 THEN m ELSE n/a – – indication of features supported by proxy.

c41: IF A.4/100 AND A.3/1 AND NOT A.3C/1 THEN n/a ELSE IF A.4/100 THEN m ELSE n/a – – indication of features supported by proxy, UE, UE performing the functions of an external attached network.

c42: IF A.4/111 THEN m ELSE n/a – – the Relayed-Charge header field extension.

c43: IF A.4/113 AND A.3/1 THEN m ELSE n/a – – the Cellular-Network-Info header extension and UE.

c44: IF A.4/113 AND (A.3/7A OR A.3/7D) THEN m ELSE n/a – – the Cellular-Network-Info header extension and AS acting as terminating UA or AS acting as third-party call controller.

c45: IF A.4/25 AND (A.3/7B OR A.3/8) THEN o ELSE n/a – – private extensions to the Session Initiation Protocol (SIP) for asserted identity within trusted networks and AS acting as originating UA, MRFC.

c46: IF A.4/74 AND A.3/7B THEN o ELSE n/a – – SIP extension for the identification of services and AS acting as originating UA.

c47: IF A.4/119 THEN o ELSE n/a – – Content-ID header field in Session Initiation Protocol (SIP).

c48: IF A.4/119 THEN m ELSE n/a – – Content-ID header field in Session Initiation Protocol (SIP).

NOTE 1: Support of this header in this method is dependent on the security mechanism and the security architecture which is implemented.

NOTE 2: The strength of this requirement in RFC 7315 [52] is SHOULD NOT, rather than MUST NOT.

Prerequisite A.5/15A – – PUBLISH request

Table A.104B: Supported message bodies within the PUBLISH request

Item

Header

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

1

application/vnd.3gpp.mcptt-info+xml

[8ZE]

n/a

c1

[8ZE]

n/a

c1

2

application/poc-settings+xml

[110]

o

c2

[110]

o

c3

3

application/pidf+xml (NOTE)

[242]

o

c1

[242]

o

c3

c1: IF A.3A/102 OR A.3A/103 THEN m ELSE n/a – – MCPTT client, MCPTT server.

c2: IF A.3A/102 THEN m ELSE n/a – – MCPTT client.

c3: IF A.3A/103 THEN m ELSE n/a – – MCPTT server.

NOTE: The application/pidf+xml is extended by 3GPP TS 24.379 [8ZE].

Prerequisite A.5/15B – – PUBLISH response

Prerequisite: A.6/1 – – Additional for 100 (Trying) response

Table A.104BA: Supported header fields within the PUBLISH response

Item

Header field

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

1

Call-ID

[26] 20.8

m

m

[26] 20.8

m

m

2

Content-Length

[26] 20.14

m

m

[26] 20.14

m

m

3

CSeq

[26] 20.16

m

m

[26] 20.16

m

m

4

Date

[26] 20.17

c1

c1

[26] 20.17

m

m

5

From

[26] 20.20

m

m

[26] 20.20

m

m

6

To

[26] 20.39

m

m

[26] 20.39

m

m

7

Via

[26] 20.42

m

m

[26] 20.42

m

m

c1: IF A.4/11 THEN o ELSE n/a – – insertion of date in requests and responses.

Prerequisite A.5/15B – – PUBLISH response for all remaining status-codes

Table A.104C: Supported header fields within the PUBLISH response

Item

Header field

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

0A

Allow

[26] 20.5

c12

c12

[26] 20.5

m

m

1

Call-ID

[26] 20.8

m

m

[26] 20.8

m

m

2

Call-Info

[26] 24.9

o

o

[26] 24.9

m

m

2A

Cellular-Network-Info

7.2.15

n/a

c19

7.2.15

n/a

c20

3

Content-Disposition

[26] 20.11

o

o

[26] 20.11

m

m

4

Content-Encoding

[26] 20.12

o

o

[26] 20.12

m

m

4A

Content-ID

[256] 3.2

o

c22

[256] 3.2

m

c23

5

Content-Language

[26] 20.13

o

o

[26] 20.13

m

m

6

Content-Length

[26] 20.14

m

m

[26] 20.14

m

m

7

Content-Type

[26] 20.15

m

m

[26] 20.15

m

m

8

CSeq

[26] 20.16

m

m

[26] 20.16

m

m

9

Date

[26] 20.17

c1

c1

[26] 20.17

m

m

9A

Expires

[26] 20.19

[70] 4, 5, 6

o

o

[26] 20.19

[70] 4, 5, 6

o

o

10

From

[26] 20.20

m

m

[26] 20.20

m

m

10A

Geolocation-Error

[89] 4.3

c16

c16

[89] 4.3

c16

c16

10B

History-Info

[66] 4.1

c13

c13

[66] 4.1

c13

c13

11

MIME-Version

[26] 20.24

o

o

[26] 20.24

m

m

12

Organization

[26] 20.25

o

o

[26] 20.25

o

o

13

P-Access-Network-Info

[52] 4.4, [52A] 4, [234] 2

c5

c6

[52] 4.4, [52A] 4, [234] 2

c5

c7

14

P-Asserted-Identity

[34] 9.1

n/a

c21

[34] 9.1

c3

c3

15

P-Charging-Function-Addresses

[52] 4.5, [52A] 4

c10

c11

[52] 4.5, [52A] 4

c10

c11

16

P-Charging-Vector

[52] 4.6, [52A] 4

c8

c9

[52] 4.6, [52A] 4

c8

c9

17

P-Preferred-Identity

[34] 9.2

c3

x

[34] 9.2

n/a

n/a

18

Privacy

[33] 4.2

c4

c4

[33] 4.2

c4

c4

18A

Relayed-Charge

7.2.12

n/a

c18

7.2.12

n/a

c18

19

Require

[26] 20.32

m

m

[26] 20.32

m

m

20

Server

[26] 20.35

o

o

[26] 20.35

o

o

20A

Session-ID

[162]

o

c17

[162]

o

c17

21

Timestamp

[26] 20.38

m

m

[26] 20.38

c2

c2

22

To

[26] 20.39

m

m

[26] 20.39

m

m

23

User-Agent

[26] 20.41

o

o

[26] 20.41

o

o

24

Via

[26] 20.42

m

m

[26] 20.42

m

m

25

Warning

[26] 20.43

o

o

[26] 20.43

o

o

c1: IF A.4/11 THEN o ELSE n/a – – insertion of date in requests and responses.

c2: IF A.4/6 THEN m ELSE n/a – – timestamping of requests.

c3: IF A.4/25 THEN o ELSE n/a – – private extensions to the Session Initiation Protocol (SIP) for asserted identity within trusted networks.

c4: IF A.4/26 THEN o ELSE n/a – – a privacy mechanism for the Session Initiation Protocol (SIP).

c5: IF A.4/34 THEN o ELSE n/a – – the P-Access-Network-Info header extension.

c6: IF A.4/34 AND A.3/1 THEN m ELSE n/a – – the P-Access-Network-Info header extension and UE.

c7: IF A.4/34 AND (A.3/7A OR A.3/7D) THEN m ELSE n/a – – the P-Access-Network-Info header extension and AS acting as terminating UA or AS acting as third-party call controller.

c8: IF A.4/36 THEN o ELSE n/a – – the P-Charging-Vector header extension.

c9: IF A.4/36 THEN m ELSE n/a – – the P-Charging-Vector header extension.

c10: IF A.4/35 THEN o ELSE n/a – – the P-Charging-Function-Addresses header extension.

c11: IF A.4/35 THEN m ELSE n/a – – the P-Charging-Function-Addresses header extension.

c12: IF A.6/18 THEN m ELSE o – – 405 (Method Not Allowed).

c13: IF A.4/47 THEN m ELSE n/a – – an extension to the session initiation protocol for request history information.

c16: IF A.4/60 THEN m ELSE n/a – – SIP location conveyance.

c17: IF A.4/91 THEN m ELSE n/a – – the Session-ID header.

c18: IF A.4/111 THEN m ELSE n/a – – the Relayed-Charge header field extension.

c19: IF A.4/113 AND A.3/1 THEN m ELSE n/a – – the Cellular-Network-Info header extension and UE.

c20: IF A.4/113 AND (A.3/7A OR A.3/7D) THEN m ELSE n/a – – the Cellular-Network-Info header extension and AS acting as terminating UA or AS acting as third-party call controller.

c21: IF A.4/25 AND (A.3/7B OR A.3/8) THEN o ELSE n/a – – private extensions to the Session Initiation Protocol (SIP) for asserted identity within trusted networks and AS acting as originating UA, MRFC.

c22: IF A.4/119 THEN o ELSE n/a – – Content-ID header field in Session Initiation Protocol (SIP).

c23: IF A.4/119 THEN m ELSE n/a – – Content-ID header field in Session Initiation Protocol (SIP).

NOTE: For a 488 (Not Acceptable Here) response, RFC 3261 [26] gives the status of this header field as SHOULD rather than OPTIONAL.

Prerequisite A.5/15B – – PUBLISH response

Prerequisite: A.6/102 – – Additional for 2xx response

Table A.104D: Supported header fields within the PUBLISH response

Item

Header field

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

2

Authentication-Info

[26] 20.6

c1

c1

[26] 20.6

c2

c2

3

Expires

[26] 20.19, [70] 4, 5, 6

m

m

[26] 20.19, [70] 4, 5, 6

m

m

3A

Feature-Caps

[190]

c8

c8

[190]

c7

c7

4

SIP-Etag

[70] 11.3.1

m

m

[70] 11.3.1

m

m

5

Supported

[26] 20.37

m

m

[26] 20.37

m

m

c1: IF A.4/7 THEN o ELSE n/a – – authentication between UA and UA.

c2: IF A.4/7 THEN m ELSE n/a – – authentication between UA and UA.

c7: IF A.4/100 THEN m ELSE n/a – – indication of features supported by proxy.

c8: IF A.4/100 AND A.3/1 AND NOT A.3C/1 THEN n/a ELSE IF A.4/100 THEN m ELSE n/a – – indication of features supported by proxy, UE, UE performing the functions of an external attached network.

Prerequisite A.5/15B – – PUBLISH response

Prerequisite: A.6/6 – – Additional for 200 (OK) response

Table A.104DAA: Supported header fields within the PUBLISH response

Item

Header field

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

1

Accept-Resource-Priority

[116] 3.2

c1

c1

[116] 3.2

c1

c1

c1: IF A.4/70B THEN m ELSE n/a – – inclusion of CANCEL, BYE, REGISTER and PUBLISH in communications resource priority for the session initiation protocol.

Prerequisite A.5/15B – – PUBLISH response

Prerequisite: A.6/103 OR A.6/104 OR A.6/105 OR A.6/106 – – Additional for 3xx – 6xx response

Table A.104DA: Supported header fields within the PUBLISH response

Item

Header field

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

1

Error-Info

[26] 20.18

o

o

[26] 20.18

o

o

2

Response-Source

7.2.17

n/a

c1

7.2.17

n/a

c1

c1: IF A.4/115 THEN o ELSE n/a – – use of the Response-Source header field in SIP error responses?

Prerequisite A.5/15B – – PUBLISH response

Prerequisite: A.6/103 OR A.6/35 – – Additional for 3xx or 485 (Ambiguous) response

Table A.104E: Supported header fields within the PUBLISH response

Item

Header field

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

2

Contact

[26] 20.10

o

o

[26] 20.10

m

m

Prerequisite A.5/15B – – PUBLISH response

Prerequisite: A.6/8 OR A.6/9 OR A.6/10 OR A.6/11OR A.6/12 – Additional for 401 (Unauthorized) response

Table A.104F: Supported header fields within the PUBLISH response

Item

Header field

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

3

Proxy-Authenticate

[26] 20.27

c1

c1

[26] 20.27

c1

c1

5

WWW-Authenticate

[26] 20.44

m

m

[26] 20.44

m

m

c1: IF A.4/7 THEN m ELSE n/a – – support of authentication between UA and UA.

Prerequisite A.5/15B – – PUBLISH response

Prerequisite: A.6/17 OR A.6/23 OR A.6/30 OR A.6/36 OR A.6/42 OR A.6/45 OR A.6/50 OR A.6/51 – – Additional for 404 (Not Found), 413 (Request Entity Too Large), 480(Temporarily not available), 486 (Busy Here), 500 (Internal Server Error), 503 (Service Unavailable), 600 (Busy Everywhere), 603 (Decline) response

Table A.104G: Supported header fields within the PUBLISH response

Item

Header field

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

3

Retry-After

[26] 20.33

o

o

[26] 20.33

o

o

Table A.104H: Void

Prerequisite A.5/15B – – PUBLISH response

Prerequisite: A.6/20 – – Additional for 407 (Proxy Authentication Required) response

Table A.104I: Supported header fields within the PUBLISH response

Item

Header field

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

3

Proxy-Authenticate

[26] 20.27

c1

c1

[26] 20.27

c1

c1

5

WWW-Authenticate

[26] 20.44

o

o

[26] 20.44

o

o

c1: IF A.4/7 THEN m ELSE n/a – – support of authentication between UA and UA.

Table A.104IA: Void

Prerequisite A.5/15B – – PUBLISH response

Prerequisite: A.6/25 – – Additional for 415 (Unsupported Media Type) response

Table A.104J: Supported header fields within the PUBLISH response

Item

Header field

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

1

Accept

[26] 20.1

o.1

o.1

[26] 20.1

m

m

2

Accept-Encoding

[26] 20.2

o.1

o.1

[26] 20.2

m

m

3

Accept-Language

[26] 20.3

o.1

o.1

[26] 20.3

m

m

o.1 At least one of these capabilities is supported.

Prerequisite A.5/15B – – PUBLISH response

Prerequisite: A.6/26A – – Additional for 417 (Unknown Resource-Priority) response

Table A.104JA: Supported header fields within the PUBLISH response

Item

Header field

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

1

Accept-Resource-Priority

[116] 3.2

c1

c1

[116] 3.2

c1

c1

c1: IF A.4/70B THEN m ELSE n/a – – inclusion of CANCEL, BYE, REGISTER and PUBLISH in communications resource priority for the session initiation protocol.

Prerequisite A.5/15B – – PUBLISH response

Prerequisite: A.6/27 – – Additional for 420 (Bad Extension) response

Table A.104K: Supported header fields within the PUBLISH response

Item

Header field

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

4

Unsupported

[26] 20.40

m

m

[26] 20.40

m

m

Prerequisite A.5/15B – – PUBLISH response

Prerequisite: A.6/28 OR A.6/41A – – Additional for 421 (Extension Required), 494 (Security Agreement Required) response

Table A.104L: Supported header fields within the PUBLISH response

Item

Header field

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

3

Security-Server

[48] 2

x

x

[48] 2

c1

c1

c1: IF A.4/37 THEN m ELSE n/a – – security mechanism agreement for the session initiation protocol.

Prerequisite A.5/15B – – PUBLISH response

Prerequisite: A.6/29 – – Additional for 423 (Interval Too Brief) response

Table A.104M: Supported header fields within the PUBLISH response

Item

Header field

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

3

Min-Expires

[26] 20.23, [70] 5, 6

m

m

[26] 20.23, [70] 5, 6

m

m

Table A.104N: Void

Prerequisite A.5/15B – – PUBLISH response

Prerequisite: A.6/39 – – Additional for 489 (Bad Event) response

Table A.104O: Supported header fields within the PUBLISH response

Item

Header field

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

2

Allow-Events

[28] 8.2.2

m

m

[28] 8.2.2

m

m

Prerequisite A.5/15B – – PUBLISH response

Prerequisite: A.6/46 – – Additional for 504 (Server Time-out) response

Table A.104OA: Supported header fields within the PUBLISH response

Item

Header field

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

1

Restoration-Info

subclause 7.2.11

n/a

c1

subclause 7.2.11

n/a

n/a

c1: IF A.4/110 THEN o ELSE n/a – – HSS based P-CSCF restoration.

Prerequisite A.5/15B – – PUBLISH response

Table A.104P: Supported message bodies within the PUBLISH response

Item

Header

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

1

A.2.1.4.11 REFER method

Prerequisite A.5/16 – – REFER request

Table A.105: Supported header fields within the REFER request

Item

Header field

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

0A

Accept

[26] 20.1

o

o

[26] 20.1

m

m

0B

Accept-Contact

[56B] 9.2

c22

c22

[56B] 9.2

c25

c25

0C

Accept-Encoding

[26] 20.2

o

o

[26] 20.2

m

m

1

Accept-Language

[26] 20.3

o

o

[26] 20.3

m

m

1AA

Additional-Identity

7.2.20

n/a

c54

7.2.20

n/a

c55

1A

Allow

[26] 20.5

o

o

[26] 20.5

m

m

2

Allow-Events

[28] 8.2.2

c1

c1

[28] 8.2.2

c2

c2

3

Authorization

[26] 20.7

c3

c3

[26] 20.7

c3

c3

4

Call-ID

[26] 20.8

m

m

[26] 20.8

m

m

4A

Cellular-Network-Info

7.2.15

n/a

c48

7.2.15

n/a

c49

5

Contact

[26] 20.10

m

m

[26] 20.10

m

m

5A

Content-Disposition

[26] 20.11

o

o

[26] 20.11

m

m

5B

Content-Encoding

[26] 20.12

o

o

[26] 20.12

m

m

5BA

Content-ID

[256] 3.2

o

c52

[256] 3.2

m

c53

5C

Content-Language

[26] 20.13

o

o

[26] 20.13

m

m

6

Content-Length

[26] 20.14

m

m

[26] 20.14

m

m

7

Content-Type

[26] 20.15

m

m

[26] 20.15

m

m

8

CSeq

[26] 20.16

m

m

[26] 20.16

m

m

9

Date

[26] 20.17

c4

c4

[26] 20.17

m

m

10

Expires

[26] 20.19

o

o

[26] 20.19

o

o

10A

Feature-Caps

[190]

c46

c46

[190]

c45

c45

11

From

[26] 20.20

m

m

[26] 20.20

m

m

11A

Geolocation

[89] 4.1

c26

c26

[89] 4.1

c26

c26

11B

Geolocation-Routing

[89] 4.2

c26

c26

[89] 4.2

c26

c26

11C

History-Info

[66] 4.1

c24

c24

[66] 4.1

c24

c24

11D

Max-Breadth

[117] 5.8

n/a

c30

[117] 5.8

c31

c31

12

Max-Forwards

[26] 20.22

m

m

[26] 20.22

n/a

c39

13

MIME-Version

[26] 20.24

o

o

[26] 20.24

m

m

14

Organization

[26] 20.25

o

o

[26] 20.25

o

o

14A

P-Access-Network-Info

[52] 4.4, [234] 2

c12

c13

[52] 4.4, [234] 2

c12

c14

14B

P-Asserted-Identity

[34] 9.1

n/a

c50

[34] 9.1

c8

c8

14C

P-Asserted-Service

[121] 4.1

n/a

c51

[121] 4.1

c29

c29

14D

P-Called-Party-ID

[52] 4.2, [52A] 4

x

x

[52] 4.2, [52A] 4

c10

c10

14E

P-Charging-Function-Addresses

[52] 4.5

c17

c18

[52] 4.5

c17

c18

14F

P-Charging-Vector

[52] 4.6

c15

c16

[52] 4.6

c15

c16

14H

P-Preferred-Identity

[34] 9.2

c8

c7

[34] 9.2

n/a

n/a

14I

P-Preferred-Service

[121] 4.2

c28

c27

[121] 4.2

n/a

n/a

14J

P-Private-Network-Indication

[134]

c36

c36

[134]

c36

c36

14K

P-Profile-Key

[97] 5

n/a

n/a

[97] 5

n/a

n/a

14L

P-Served-User

[133] 6

c41

c41

[133] 6

c41

c41

14M

P-User-Database

[82] 4

n/a

n/a

[82] 4

n/a

n/a

14N

P-Visited-Network-ID

[52] 4.3

x (note 1)

x

[52] 4.3

c11

n/a

14O

Privacy

[33] 4.2

c9

c9

[33] 4.2

c9

c9

15

Proxy-Authorization

[26] 20.28

c5

c5

[26] 20.28

n/a

n/a

16

Proxy-Require

[26] 20.29

o

n/a

[26] 20.29

n/a

n/a

16A

Reason

[34A] 2

c21

c21

[34A] 2

c21

c21

17

Record-Route

[26] 20.30

n/a

c39

[26] 20.30

m

m

17A

Refer-Sub

[173] 4

c40

c40

[173] 4

c40

c40

18

Refer-To

[36] 3

m

m

[36] 3

m

m

18A

Referred-By

[59] 3

c23

c23

[59] 3

c23

c23

18B

Reject-Contact

[56B] 9.2

c22

c22

[56B] 9.2

c25

c25

18C

Relayed-Charge

7.2.12

n/a

c47

7.2.12

n/a

c47

18D

Request-Disposition

[56B] 9.1

c22

c22

[56B] 9.1

c25

c25

19

Require

[26] 20.32

m

m

[26] 20.32

m

m

19A

Resource-Priority

[116] 3.1

c33

c33

[116] 3.1

c33

c33

20

Route

[26] 20.34

m

m

[26] 20.34

n/a

c39

20A

Security-Client

[48] 2.3.1

c19

c19

[48] 2.3.1

n/a

n/a

20B

Security-Verify

[48] 2.3.1

c20

c20

[48] 2.3.1

n/a

n/a

20C

Session-ID

[162]

o

c42

[162]

o

c42

21

Supported

[26] 20.37, [26] 7.1

o

o

[26] 20.37, [26] 7.1

m

m

21A

Target-Dialog

[184] 7

c43

c43

[184] 7

c44

c44

22

Timestamp

[26] 20.38

c6

c6

[26] 20.38

m

m

23

To

[26] 20.39

m

m

[26] 20.39

m

m

23A

Trigger-Consent

[125] 5.11.2

c34

c34

[125] 5.11.2

c35

c35

24

User-Agent

[26] 20.41

o

o

[26] 20.41

o

o

25

Via

[26] 20.42

m

m

[26] 20.42

m

m

c1: IF A.4/22 THEN o ELSE n/a – – acting as the notifier of event information.

c2: IF A.4/23 THEN m ELSE n/a – – acting as the subscriber to event information.

c3: IF A.4/7 THEN m ELSE n/a – – authentication between UA and UA.

c4: IF A.4/11 THEN o ELSE n/a – – insertion of date in requests and responses.

c5: IF A.4/8A THEN m ELSE n/a – – authentication between UA and proxy.

c6: IF A.4/6 THEN o ELSE n/a – – timestamping of requests.

c7: IF A.3/1 AND A.4/25 THEN o ELSE n/a – – UE and private extensions to the Session Initiation Protocol (SIP) for asserted identity within trusted networks.

c8: IF A.4/25 THEN o ELSE n/a – – private extensions to the Session Initiation Protocol (SIP) for asserted identity within trusted networks.

c9: IF A.4/26 THEN o ELSE n/a – – a privacy mechanism for the Session Initiation Protocol (SIP).

c10: IF A.4/32 THEN o ELSE n/a – – the P-Called-Party-ID extension.

c11: IF A.4/33 THEN o ELSE n/a – – the P-Visited-Network-ID extension.

c12: IF A.4/34 THEN o ELSE n/a – – the P-Access-Network-Info header extension.

c13: IF A.4/34 AND A.3/1 THEN m ELSE n/a – – the P-Access-Network-Info header extension and UE.

c14: IF A.4/34 AND (A.3/7A OR A.3/7D) THEN m ELSE n/a – – the P-Access-Network-Info header extension and AS acting as terminating UA or AS acting as third-party call controller.

c15: IF A.4/36 THEN o ELSE n/a – – the P-Charging-Vector header extension.

c16: IF A.4/36 THEN m ELSE n/a – – the P-Charging-Vector header extension.

c17: IF A.4/35 THEN o ELSE n/a – – the P-Charging-Function-Addresses header extension.

c18: IF A.4/35 THEN m ELSE n/a – – the P-Charging-Function-Addresses header extension.

c19: IF A.4/37 OR A.4/37A THEN o ELSE n/a – – security mechanism agreement for the session initiation protocol or mediasec header field parameter for marking security mechanisms related to media (note 2).

c20: IF A.4/37 OR A.4/37A THEN m ELSE n/a – – security mechanism agreement for the session initiation protocol or mediasec header field parameter for marking security mechanisms related to media.

c21: IF A.4/38 THEN o ELSE n/a – – the Reason header field for the session initiation protocol.

c22: IF A.4/40 THEN o ELSE n/a – – caller preferences for the session initiation protocol.

c23: IF A.4/43 THEN m ELSE n/a – – the SIP Referred-By Mechanism.

c24: IF A.4/47 THEN m ELSE n/a – – an extension to the session initiation protocol for request history information.

c25: IF A.4/40 THEN m ELSE n/a – – caller preferences for the session initiation protocol.

c26: IF A.4/60 THEN m ELSE n/a – – SIP location conveyance.

c27: IF (A.3/1 OR A.3A/81) AND A.4/74 THEN o ELSE n/a – – UE, MSC Server enhanced for ICS and SIP extension for the identification of services.

c28: IF A.4/74 THEN o ELSE n/a – – SIP extension for the identification of services.

c29: IF A.4/74 THEN m ELSE n/a – – SIP extension for the identification of services.

c30: IF A.4/71 AND (A.3/9B OR A.3/9C OR A.3/13B OR A.3/13C) THEN m ELSE IF A.3/1 AND NOT A.3C/1 THEN n/a ELSE o – – addressing an amplification vulnerability in session initiation protocol forking proxies, IBCF (IMS-ALG), IBCF (Screening of SIP signalling), ISC gateway function (IMS-ALG), ISC gateway function (Screening of SIP signalling), UE, UE performing the functions of an external attached network.

c31: IF A.4/71 THEN m ELSE n/a – – addressing an amplification vulnerability in session initiation protocol forking proxies.

c33: IF A.4/70 THEN m ELSE n/a – – communications resource priority for the session initiation protocol.

c34: IF A.4/75A THEN m ELSE n/a – – a relay within the framework for consent-based communications in SIP.

c35: IF A.4/75B THEN m ELSE n/a – – a recipient within the framework for consent-based communications in SIP.

c36: IF A.4/77 THEN m ELSE n/a – – the SIP P-Private-Network-Indication private-header (P-Header).

c39: IF A.3/1 AND NOT A.3C/1 THEN n/a ELSE o – – UE, UE performing the functions of an external attached network.

c40: IF A.4/95 THEN m ELSE n/a – – suppression of session initiation protocol REFER method implicit subscription.

c41: IF A.4/78 THEN m ELSE n/a – – the SIP P-Served-User private header.

c42: IF A.4/91 THEN m ELSE n/a – – the Session-ID header.

c43: IF A.4/99 THEN o ELSE n/a – – request authorization through dialog Identification in the session initiation protocol.

c44: IF A.4/99 THEN m ELSE n/a – – request authorization through dialog Identification in the session initiation protocol.

c45: IF A.4/100 THEN m ELSE n/a – – indication of features supported by proxy.

c46: IF A.4/100 AND A.3/1 AND NOT A.3C/1 THEN n/a ELSE IF A.4/100 THEN m ELSE n/a – – indication of features supported by proxy, UE, UE performing the functions of an external attached network.

c47: IF A.4/111 THEN m ELSE n/a – – the Relayed-Charge header field extension.

c48: IF A.4/113 AND A.3/1 THEN m ELSE n/a – – the Cellular-Network-Info header extension and UE.

c49: IF A.4/113 AND (A.3/7A OR A.3/7D) THEN m ELSE n/a – – the Cellular-Network-Info header extension and AS acting as terminating UA or AS acting as third-party call controller.

c50: IF A.4/25 AND (A.3/7B OR A.3/8) THEN o ELSE n/a – – private extensions to the Session Initiation Protocol (SIP) for asserted identity within trusted networks and AS acting as originating UA, MRFC.

c51: IF A.4/74 AND A.3/7B THEN o ELSE n/a – – SIP extension for the identification of services and AS acting as originating UA.

c52: IF A.4/119 THEN o ELSE n/a – – Content-ID header field in Session Initiation Protocol (SIP).

c53: IF A.4/119 THEN m ELSE n/a – – Content-ID header field in Session Initiation Protocol (SIP).

c54: IF A.4/124 THEN o ELSE n/a – – the Additional-Identity header field extension.

c55: IF A.4/124 THEN m ELSE n/a – – the Additional-Identity header field extension.

NOTE 1: The strength of this requirement in RFC 7315 [52] is SHOULD NOT, rather than MUST NOT.

NOTE 2: Support of this header field in this method is dependent on the security mechanism and the security architecture which is implemented. Use of this header field in this method is not appropriate to the security mechanism defined by 3GPP TS 33.203 [19].

Prerequisite A.5/16 – – REFER request

Table A.106: Supported message bodies within the REFER request

Item

Header

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

1

application/vnd.3gpp.mid-call+xml

[8M] D

n/a

o

[8M] D

n/a

o

2

application/vnd.3gpp.mcptt-info+xml

[8ZE]

n/a

c1

[8ZE]

n/a

c1

c1: IF A.3A/102 OR A.3A/103 THEN m ELSE n/a – – MCPTT client, MCPTT server.

Table A.107: Void

Prerequisite A.5/17 – – REFER response

Prerequisite: A.6/1 – – Additional for 100 (Trying) response

Table A.107A: Supported header fields within the REFER response

Item

Header field

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

1

Call-ID

[26] 20.8

m

m

[26] 20.8

m

m

2

Content-Length

[26] 20.14

m

m

[26] 20.14

m

m

3

CSeq

[26] 20.16

m

m

[26] 20.16

m

m

4

Date

[26] 20.17

c1

c1

[26] 20.17

m

m

5

From

[26] 20.20

m

m

[26] 20.20

m

m

6

To

[26] 20.39

m

m

[26] 20.39

m

m

7

Via

[26] 20.42

m

m

[26] 20.42

m

m

c1: IF A.4/11 THEN o ELSE n/a – – insertion of date in requests and responses.

Prerequisite A.5/17 – – REFER response for all remaining status-codes

Table A.108: Supported header fields within the REFER response

Item

Header field

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

0A

Allow

[26] 20.5

c12

c12

[26] 20.5

m

m

1

Call-ID

[26] 20.8

m

m

[26] 20.8

m

m

1A

Cellular-Network-Info

7.2.15

n/a

c20

7.2.15

n/a

c21

1B

Content-Disposition

[26] 20.11

o

o

[26] 20.11

m

m

2

Content-Encoding

[26] 20.12

o

o

[26] 20.12

m

m

2A

Content-ID

[256] 3.2

o

c23

[256] 3.2

m

c24

3

Content-Language

[26] 20.13

o

o

[26] 20.13

m

m

4

Content-Length

[26] 20.14

m

m

[26] 20.14

m

m

5

Content-Type

[26] 20.15

m

m

[26] 20.15

m

m

6

CSeq

[26] 20.16

m

m

[26] 20.16

m

m

7

Date

[26] 20.17

c1

c1

[26] 20.17

m

m

8

From

[26] 20.20

m

m

[26] 20.20

m

m

8A

Geolocation-Error

[89] 4.3

c15

c15

[89] 4.3

c15

c15

8B

History-Info

[66] 4.1

c14

c14

[66] 4.1

c14

c14

9

MIME-Version

[26] 20.24

o

o

[26] 20.24

m

m

10

Organization

[26] 20.25

o

o

[26] 20.25

o

o

10A

P-Access-Network-Info

[52] 4.4, [52A] 4, [234] 2

c5

c6

[52] 4.4, [52A] 4, [234] 2

c5

c7

10B

P-Asserted-Identity

[34] 9.1

n/a

c22

[34] 9.1

c3

c3

10C

P-Charging-Function-Addresses

[52] 4.5, [52A] 4

c10

c11

[52] 4.5, [52A] 4

c10

c11

10D

P-Charging-Vector

[52] 4.6, [52A] 4

c8

c9

[52] 4.6, [52A] 4

c8

c9

10F

P-Preferred-Identity

[34] 9.2

c3

x

[34] 9.2

n/a

n/a

10G

Privacy

[33] 4.2

c4

c4

[33] 4.2

c4

c4

10H

Relayed-Charge

7.2.12

n/a

c19

7.2.12

n/a

c19

10I

Require

[26] 20.32

m

m

[26] 20.32

m

m

10J

Server

[26] 20.35

o

o

[26] 20.35

o

o

10K

Session-ID

[162]

o

c18

[162]

o

c18

11

Timestamp

[26] 20.38

m

m

[26] 20.38

c2

c2

12

To

[26] 20.39

m

m

[26] 20.39

m

m

12A

User-Agent

[26] 20.41

o

o

[26] 20.41

o

o

13

Via

[26] 20.42

m

m

[26] 20.42

m

m

14

Warning

[26] 20.43

o (note)

o

[26] 20.43

o

o

c1: IF A.4/11 THEN o ELSE n/a – – insertion of date in requests and responses.

c2: IF A.4/6 THEN m ELSE n/a – – timestamping of requests.

c3: IF A.4/25 THEN o ELSE n/a – – private extensions to the Session Initiation Protocol (SIP) for asserted identity within trusted networks.

c4: IF A.4/26 THEN o ELSE n/a – – a privacy mechanism for the Session Initiation Protocol (SIP).

c5: IF A.4/34 THEN o ELSE n/a – – the P-Access-Network-Info header extension.

c6: IF A.4/34 AND A.3/1 THEN m ELSE n/a – – the P-Access-Network-Info header extension and UE.

c7: IF A.4/34 AND (A.3/7A OR A.3/7D) THEN m ELSE n/a – – the P-Access-Network-Info header extension and AS acting as terminating UA or AS acting as third-party call controller.

c8: IF A.4/36 THEN o ELSE n/a – – the P-Charging-Vector header extension.

c9: IF A.4/36 THEN m ELSE n/a – – the P-Charging-Vector header extension.

c10: IF A.4/35 THEN o ELSE n/a – – the P-Charging-Function-Addresses header extension.

c11: IF A.4/35 THEN m ELSE n/a – – the P-Charging-Function-Addresses header extension.

c12: IF A.6/18 THEN m ELSE o – – 405 (Method Not Allowed)

c14: IF A.4/47 THEN m ELSE n/a – – an extension to the session initiation protocol for request history information.

c15: IF A.4/60 THEN m ELSE n/a – – SIP location conveyance.

c18: IF A.4/91 THEN m ELSE n/a – – the Session-ID header.

c19: IF A.4/111 THEN m ELSE n/a – – the Relayed-Charge header field extension.

c20: IF A.4/113 AND A.3/1 THEN m ELSE n/a – – the Cellular-Network-Info extension and UE.

c21: IF A.4/113 AND (A.3/7A OR A.3/7D) THEN m ELSE n/a – – the Cellular-Network-Info header extension and AS acting as terminating UA or AS acting as third-party call controller.

c22: IF A.4/25 AND (A.3/7B OR A.3/8) THEN o ELSE n/a – – private extensions to the Session Initiation Protocol (SIP) for asserted identity within trusted networks and AS acting as originating UA, MRFC.

c23: IF A.4/119 THEN o ELSE n/a – – Content-ID header field in Session Initiation Protocol (SIP).

c24: IF A.4/119 THEN m ELSE n/a – – Content-ID header field in Session Initiation Protocol (SIP).

NOTE: For a 488 (Not Acceptable Here) response, RFC 3261 [26] gives the status of this header field as SHOULD rather than OPTIONAL.

Prerequisite A.5/17 – – REFER response

Prerequisite: A.6/102 – – Additional for 2xx response

Table A.109: Supported header fields within the REFER response

Item

Header field

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

0A

Accept-Resource-Priority

[116] 3.2

c12

c12

[116] 3.2

c12

c12

1

Allow-Events

[28] 8.2.2

c3

c3

[28] 8.2.2

c4

c4

2

Authentication-Info

[26] 20.6

c1

c1

[26] 20.6

c2

c2

2A

Contact

[26] 20.10

m

m

[26] 20.10

m

m

3

Feature-Caps

[190]

c15

c15

[190]

c14

c14

5

Record-Route

[26] 20.30

m

m

[26] 20.30

m

m

6

Refer-Sub

[173] 4

c13

c13

[173] 4

c13

c13

8

Supported

[26] 20.37

m

m

[26] 20.37

m

m

c1: IF A.4/7 THEN o ELSE n/a – – authentication between UA and UA.

c2: IF A.4/7 THEN m ELSE n/a – – authentication between UA and UA.

c3: IF A.4/22 THEN o ELSE n/a – – acting as the notifier of event information.

c4: IF A.4/23 THEN m ELSE n/a – – acting as the subscriber to event information.

c12: IF A.4/70 THEN m ELSE n/a – – communications resource priority for the session initiation protocol.

c13: IF A.4/95 THEN m ELSE n/a – – suppression of session initiation protocol REFER method implicit subscription.

c14: IF A.4/100 THEN m ELSE n/a – – indication of features supported by proxy.

c15: IF A.4/100 AND A.3/1 AND NOT A.3C/1 THEN n/a ELSE IF A.4/100 THEN m ELSE n/a – – indication of features supported by proxy, UE, UE performing the functions of an external attached network.

Prerequisite A.5/17 – – REFER response

Prerequisite: A.6/103 OR A.6/104 OR A.6/105 OR A.6/106 – – Additional for 3xx – 6xx response

Table A.109A: Supported header fields within the REFER response

Item

Header field

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

0

Contact

[26] 20.10

o

o

[26] 20.10

m

m

1

Error-Info

[26] 20.18

o

o

[26] 20.18

o

o

2

Response-Source

7.2.17

n/a

c1

7.2.17

n/a

c1

c1: IF A.4/115 THEN o ELSE n/a – – use of the Response-Source header field in SIP error responses?

Table A.110: Void

Prerequisite A.5/17 – – REFER response

Prerequisite: A.6/14 – – Additional for 401 (Unauthorized) response

Table A.111: Supported header fields within the REFER response

Item

Header field

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

4

Proxy-Authenticate

[26] 20.27

c1

c1

[26] 20.27

c1

c1

10

WWW-Authenticate

[26] 20.44

m

m

[26] 20.44

m

m

c1: IF A.4/7 THEN m ELSE n/a – – support of authentication between UA and UA.

Prerequisite A.5/17 – – REFER response

Prerequisite: A.6/17 OR A.6/23 OR A.6/30 OR A.6/36 OR A.6/42 OR A.6/45 OR A.6/50 OR A.6/51 – – Additional for 404 (Not Found), 413 (Request Entity Too Large), 480(Temporarily not available), 486 (Busy Here), 500 (Internal Server Error), 503 (Service Unavailable), 600 (Busy Everywhere), 603 (Decline) response

Table A.112: Supported header fields within the REFER response

Item

Header field

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

6

Retry-After

[26] 20.33

o

o

[26] 20.33

o

o

Table A.113: Void

Prerequisite A.5/17 – – REFER response

Prerequisite: A.6/20 – – Additional for 407 (Proxy Authentication Required) response

Table A.114: Supported header fields within the REFER response

Item

Header field

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

4

Proxy-Authenticate

[26] 20.27

c1

c1

[26] 20.27

c1

c1

8

WWW-Authenticate

[26] 20.44

o

o

[26] 20.44

o

o

c1: IF A.4/7 THEN m ELSE n/a – – support of authentication between UA and UA.

Table A.114A: Void

Prerequisite A.5/17 – – REFER response

Prerequisite: A.6/25 – – Additional for 415 (Unsupported Media Type) response

Table A.115: Supported header fields within the REFER response

Item

Header field

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

1

Accept

[26] 20.1

o.1

o.1

[26] 20.1

m

m

2

Accept-Encoding

[26] 20.2

o.1

o.1

[26] 20.2

m

m

3

Accept-Language

[26] 20.3

o.1

o.1

[26] 20.3

m

m

o.1 At least one of these capabilities is supported.

Prerequisite A.5/17 – – REFER response

Prerequisite: A.6/26A – – Additional for 417 (Unknown Resource-Priority) response

Table A.115A: Supported header fields within the REFER response

Item

Header field

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

1

Accept-Resource-Priority

[116] 3.2

c1

c1

[116] 3.2

c1

c1

c1: IF A.4/70 THEN m ELSE n/a – – communications resource priority for the session initiation protocol.

Prerequisite A.5/17 – – REFER response

Prerequisite: A.6/27 – – Additional for 420 (Bad Extension) response

Table A.116: Supported header fields within the REFER response

Item

Header field

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

8

Unsupported

[26] 20.40

m

m

[26] 20.40

m

m

Prerequisite A.5/17 – – REFER response

Prerequisite: A.6/28 OR A.6/41A – – Additional for 421 (Extension Required), 494 (Security Agreement Required) response

Table A.116A: Supported header fields within the REFER response

Item

Header field

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

3

Security-Server

[48] 2

x

x

[48] 2

c1

c1

c1: IF A.4/37 THEN m ELSE n/a – – security mechanism agreement for the session initiation protocol.

Table A.117: Void

Prerequisite A.5/17 – – REFER response

Prerequisite: A.6/29H – – Additional for 470 (Consent Needed) response

Table A.117A: Supported header fields within the REFER response

Item

Header field

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

1

Permission-Missing

[125] 5.9.3

m

m

[125] 5.9.3

m

m

Prerequisite A.5/17 – – REFER response

Prerequisite: A.6/46 – – Additional for 504 (Server Time-out) response

Table A.117B: Supported header fields within the REFER response

Item

Header field

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

1

Restoration-Info

subclause 7.2.11

n/a

c1

subclause 7.2.11

n/a

n/a

c1: IF A.4/110 THEN o ELSE n/a – – HSS based P-CSCF restoration.

Prerequisite A.5/17 – – REFER response

Table A.118: Supported message bodies within the REFER response

Item

Header

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

1

A.2.1.4.12 REGISTER method

Prerequisite A.5/18 – – REGISTER request

Table A.119: Supported header fields within the REGISTER request

Item

Header field

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

1

Accept

[26] 20.1

o

o

[26] 20.1

m

m

2

Accept-Encoding

[26] 20.2

o

o

[26] 20.2

m

m

3

Accept-Language

[26] 20.3

o

o

[26] 20.3

m

m

3A

Allow

[26] 20.5

o

o

[26] 20.5

m

m

4

Allow-Events

[28] 8.2.2

c27

c27

[28] 8.2.2

c1

c1

5

Authorization

[26] 20.7, [49]

c2

c29

[26] 20.7, [49]

m

c22

6

Call-ID

[26] 20.8

m

m

[26] 20.8

m

m

7

Call-Info

[26] 20.9

o

o

[26] 20.9

o

o

7A

Cellular-Network-Info

7.2.15

n/a

c43

7.2.15

n/a

c44

8

Contact

[26] 20.10

o

m

[26] 20.10

m

m

9

Content-Disposition

[26] 20.11

o

o

[26] 20.11

m

m

10

Content-Encoding

[26] 20.12

o

o

[26] 20.12

m

m

10A

Content-ID

[256] 3.2

o

c45

[256] 3.2

m

c46

11

Content-Language

[26] 20.13

o

o

[26] 20.13

m

m

12

Content-Length

[26] 20.14

m

m

[26] 20.14

m

m

13

Content-Type

[26] 20.15

m

m

[26] 20.15

m

m

14

CSeq

[26] 20.16

m

m

[26] 20.16

m

m

15

Date

[26] 20.17

c3

c3

[26] 20.17

m

m

16

Expires

[26] 20.19

o

o

[26] 20.19

m

m

16A

Feature-Caps

[190]

c40

c40

[190]

c39

c39

17

From

[26] 20.20

m

m

[26] 20.20

m

m

17A

Geolocation

[89] 4.1

c31

c31

[89] 4.1

c31

c31

17B

Geolocation-Routing

[89] 4.2

c31

c31

[89] 4.2

c31

c31

17C

History-Info

[66] 4.1

c28

c28

[66] 4.1

c28

c28

17D

Max-Breadth

[117] 5.8

n/a

c35

[117] 5.8

c36

c36

18

Max-Forwards

[26] 20.22

m

m

[26] 20.22

n/a

n/a

19

MIME-Version

[26] 20.24

o

o

[26] 20.24

m

m

20

Organization

[26] 20.25

o

o

[26] 20.25

o

o

20A

P-Access-Network-Info

[52] 4.4, [234] 2

c12

c13

[52] 4.4, [234] 2

c12

c14

20B

P-Charging-Function-Addresses

[52] 4.5

c17

c18

[52] 4.5

c17

c18

20C

P-Charging-Vector

[52] 4.6

c15

c16

[52] 4.6

c15

c16

20E

P-User-Database

[82] 4

n/a

n/a

[82] 4

c30

c30

20F

P-Visited-Network-ID

[52] 4.3

x (note 2)

x

[52] 4.3

c10

c11

20G

Path

[35] 4

c4

c5

[35] 4

m

c6

20H

Privacy

[33] 4.2

c9

n/a

[33] 4.2

c9

n/a

21

Proxy-Authorization

[26] 20.28

c8

c8

[26] 20.28

n/a

n/a

22

Proxy-Require

[26] 20.29

o

o (note 1)

[26] 20.29

n/a

n/a

22A

Reason

[34A] 2

c23

c23

[34A] 2

c23

c23

22B

Recv-Info

[25] 5.2.3

c37

c37

[25] 5.2.3

c37

c37

22C

Referred-By

[59] 3

c25

c25

[59] 3

c26

c26

22D

Relayed-Charge

7.2.12

n/a

c41

7.2.12

n/a

c41

22E

Request-Disposition

[56B] 9.1

c24

c24

[56B] 9.1

n/a

n/a

23

Require

[26] 20.32

m

m

[26] 20.32

m

m

23A

Resource-Priority

[116] 3.1

c32

c32

[116] 3.1

c32

c32

23B

Resource-Share

Subclause 7.2.13

n/a

c42

Subclause 7.2.13

n/a

c42

24

Route

[26] 20.34

o

x

[26] 20.34

n/a

n/a

24A

Security-Client

[48] 2.3.1

c19

c20

[48] 2.3.1

n/a

n/a

24B

Security-Verify

[48] 2.3.1

c20

c20

[48] 2.3.1

c21

n/a

24C

Session-ID

[162]

o

c38

[162]

o

c38

25

Supported

[26] 20.37

o

c29

[26] 20.37

m

m

26

Timestamp

[26] 20.38

c7

c7

[26] 20.38

c7

c7

27

To

[26] 20.39

m

m

[26] 20.39

m

m

28

User-Agent

[26] 20.41

o

o

[26] 20.41

o

o

29

Via

[26] 20.42

m

m

[26] 20.42

m

m

c1: IF A.4/23 THEN m ELSE n/a – – acting as the subscriber to event information.

c2: IF A.4/8 THEN m ELSE n/a – – authentication between UA and registrar.

c3: IF A.4/11 THEN o ELSE n/a – – insertion of date in requests and responses.

c4: IF A.4/24 THEN o ELSE n/a – – session initiation protocol extension header field for registering non-adjacent contacts.

c5: IF A.4/24 THEN x ELSE n/a – – session initiation protocol extension header field for registering non-adjacent contacts.

c6: IF A.3/4 THEN m ELSE n/a. – – S-CSCF.

c7: IF A.4/6 THEN m ELSE n/a – – timestamping of requests.

c8: IF A.4/8A THEN m ELSE n/a – – authentication between UA and proxy.

c9: IF A.4/26 THEN o ELSE n/a – – a privacy mechanism for the Session Initiation Protocol (SIP).

c10: IF A.4/33 THEN o ELSE n/a – – the P-Visited-Network-ID extension.

c11: IF A.4/33 THEN m ELSE n/a – – the P-Visited-Network-ID extension.

c12: IF A.4/34 THEN o ELSE n/a – – the P-Access-Network-Info header extension.

c13: IF A.4/34 AND (A.3/1 OR A.3/4) THEN o ELSE n/a – – the P-Access-Network-Info header extension and UE or S-CSCF.

c14: IF A.4/34 AND (A.3/4 OR A.3/7A) THEN m ELSE n/a – – the P-Access-Network-Info header extension and S-CSCF or AS acting as terminating UA.

c15: IF A.4/36 THEN o ELSE n/a – – the P-Charging-Vector header extension.

c16: IF A.4/36 OR A.3/4 THEN m ELSE n/a – – the P-Charging-Vector header extension (including S-CSCF as registrar).

c17: IF A.4/35 THEN o ELSE n/a – – the P-Charging-Function-Addresses header extension.

c18: IF A.4/35 OR A.3/4 THEN m ELSE n/a – – the P-Charging-Function-Addresses header extension (including S-CSCF as registrar).

c19: IF A.4/37 OR A.4/37A THEN o ELSE n/a – – security mechanism agreement for the session initiation protocol or mediasec header field parameter for marking security mechanisms related to media (note 3).

c20: IF A.4/37 OR A.4/37A THEN m ELSE n/a – – security mechanism agreement for the session initiation protocol or mediasec header field parameter for marking security mechanisms related to media.

c21: IF A.4/37 AND A.4/2 THEN m ELSE n/a – – security mechanism agreement for the session initiation protocol and registrar.

c22: IF A.3/4 THEN m ELSE n/a – – S-CSCF.

c23: IF A.4/38 THEN o ELSE n/a – – the Reason header field for the session initiation protocol.

c24: IF A.4/40 THEN o ELSE n/a – – caller preferences for the session initiation protocol.

c25: IF A.4/43 THEN m ELSE n/a – – the SIP Referred-By mechanism.

c26: IF A.4/43 THEN o ELSE n/a – – the SIP Referred-By mechanism.

c27: IF A.4/22 THEN o ELSE n/a – – acting as the notifier of event information.

c28: IF A.4/47 THEN m ELSE n/a – – an extension to the session initiation protocol for request history information.

c29: IF (A.3/1 OR A.3A/81) THEN m ELSE o – – UE, MSC Server enhanced for ICS.

c30: IF A.4/48 THEN m ELSE n/a – – the P-User-Database private header extension.

c31: IF A.4/60 THEN m ELSE n/a – – SIP location conveyance.

c32: IF A.4/70B THEN m ELSE n/a – – inclusion of CANCEL, BYE, REGISTER and PUBLISH in communications resource priority for the session initiation protocol.

c35: IF A.4/71 AND (A.3/9B OR A.3/9C OR A.3/13B OR A.3/13C) THEN m ELSE n/a – – IF A.4/71 AND (A.3/9B OR A.3/9C) THEN m ELSE n/a – – addressing an amplification vulnerability in session initiation protocol forking proxies, IBCF (IMS-ALG), IBCF (Screening of SIP signalling), ISC gateway function (IMS-ALG), ISC gateway function (Screening of SIP signalling).

c36: IF A.4/71 THEN m ELSE n/a – – addressing an amplification vulnerability in session initiation protocol forking proxies.

c37: IF A.4/13 THEN m ELSE IF A.4/13A THEN m ELSE n/a – – SIP INFO method and package framework, legacy INFO usage.

c38: IF A.4/91 THEN m ELSE n/a – – the Session-ID header.

c39: IF A.4/100 THEN m ELSE n/a – – indication of features supported by proxy.

c40: IF A.4/100 AND A.3/1 AND NOT A.3C/1 THEN n/a ELSE IF A.4/100 THEN m ELSE n/a – – indication of features supported by proxy, UE, UE performing the functions of an external attached network.

c41: IF A.4/111 THEN m ELSE n/a – – the Relayed-Charge header field extension.

c42: IF A.4/112 AND A.3/2 THEN o ELSE n/a – – resource sharing, AS.

c43: IF A.4/113 AND (A.3/1 OR A.3/4) THEN m ELSE n/a – – the Cellular-Network-Info header extension and UE or S-CSCF.

c44: IF A.4/113 AND (A.3/4 OR A.3/7A) THEN m ELSE n/a – – the Cellular-Network-Info header extension and S-CSCF or AS acting as terminating UA.

c45: IF A.4/119 THEN o ELSE n/a – – Content-ID header field in Session Initiation Protocol (SIP).

c46: IF A.4/119 THEN m ELSE n/a – – Content-ID header field in Session Initiation Protocol (SIP).

NOTE 1: No distinction has been made in these tables between first use of a request on a From/To/Call-ID combination, and the usage in a subsequent one. Therefore the use of "o" etc. above has been included from a viewpoint of first usage.

NOTE 2: The strength of this requirement in RFC 7315 [52] is SHOULD NOT, rather than MUST NOT.

NOTE 3: Support of this header field in this method is dependent on the security mechanism and the security architecture which is implemented.

Prerequisite A.5/18 – – REGISTER request

Table A.120: Supported message bodies within the REGISTER request

Item

Header

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

1

message/sip

[26] 27.5

n/a

c1

[26] 27.5

n/a

c2

2

3GPP IM CN subsystem XML body

subclause 7.6

n/a

c1

subclause 7.6

n/a

c2

3

application/vnd.3gpp.mcptt-info+xml

[8ZE]

n/a

c3

[8ZE]

n/a

c3

c1: IF A.3/4 THEN o ELSE n/a – – S-CSCF.

c2: IF A.3/7 THEN o ELSE n/a – – AS.

c3: IF A.3A/102 OR A.3A/103 THEN m ELSE n/a – – MCPTT client, MCPTT server.

Table A.121: Void

Prerequisite A.5/19 – – REGISTER response

Prerequisite: A.6/1 – – Additional for 100 (Trying) response

Table A.121A: Supported header fields within the REGISTER response

Item

Header field

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

1

Call-ID

[26] 20.8

m

m

[26] 20.8

m

m

2

Content-Length

[26] 20.14

m

m

[26] 20.14

m

m

3

CSeq

[26] 20.16

m

m

[26] 20.16

m

m

4

Date

[26] 20.17

c1

c1

[26] 20.17

m

m

5

From

[26] 20.20

m

m

[26] 20.20

m

m

6

To

[26] 20.39

m

m

[26] 20.39

m

m

7

Via

[26] 20.42

m

m

[26] 20.42

m

m

c1: IF A.4/11 THEN o ELSE n/a – – insertion of date in requests and responses.

Prerequisite A.5/19 – – REGISTER response for all remaining status-codes

Table A.122: Supported header fields within the REGISTER response

Item

Header field

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

0A

Allow

[26] 20.5

c8

c8

[26] 20.5

m

m

1

Call-ID

[26] 20.8

m

m

[26] 20.8

m

m

1A

Call-Info

[26] 20.9

o

o

[26] 20.9

o

o

2

Content-Disposition

[26] 20.11

o

o

[26] 20.11

m

m

3

Content-Encoding

[26] 20.12

o

o

[26] 20.12

m

m

3A

Content-ID

[256] 3.2

o

c15

[256] 3.2

m

c16

4

Content-Language

[26] 20.13

o

o

[26] 20.13

m

m

5

Content-Length

[26] 20.14

m

m

[26] 20.14

m

m

6

Content-Type

[26] 20.15

m

m

[26] 20.15

m

m

7

CSeq

[26] 20.16

m

m

[26] 20.16

m

m

8

Date

[26] 20.17

c1

c1

[26] 20.17

m

m

9

From

[26] 20.20

m

m

[26] 20.20

m

m

9A

Geolocation-Error

[89] 4.3

c10

c10

[89] 4.3

c10

c10

9B

History-Info

[66] 4.1

c9

c9

[66] 4.1

c9

c9

10

MIME-Version

[26] 20.24

o

o

[26] 20.24

m

m

11

Organization

[26] 20.25

o

o

[26] 20.25

o

o

11A

P-Access-Network-Info

[52] 4.4, [52A] 4, [234] 2

c3

n/a

[52] 4.4, [52A] 4, [234] 2

c3

n/a

11B

P-Charging-Function-Addresses

[52] 4.5, [52A] 4

c6

c7

[52] 4.5, [52A] 4

c6

c7

11C

P-Charging-Vector

[52] 4.6, [52A] 4

c4

c5

[52] 4.6, [52A] 4

c4

c5

11E

Privacy

[33] 4.2

c2

n/a

[33] 4.2

c2

n/a

11F

Relayed-Charge

7.2.12

n/a

c14

7.2.12

n/a

c14

11G

Require

[26] 20.32

m

m

[26] 20.32

m

m

11H

Server

[26] 20.35

o

o

[26] 20.35

o

o

11I

Session-ID

[162]

o

c13

[162]

o

c13

12

Timestamp

[26] 20.38

c2

c2

[26] 20.38

m

m

13

To

[26] 20.39

m

m

[26] 20.39

m

m

13A

User-Agent

[26] 20.41

o

o

[26] 20.41

o

o

14

Via

[26] 20.42

m

m

[26] 20.42

m

m

15

Warning

[26] 20.43

o (note)

o

[26] 20.43

o

o

c1: IF A.4/11 THEN o ELSE n/a – – insertion of date in requests and responses.

c2: IF A.4/26 THEN o ELSE n/a – – a privacy mechanism for the Session Initiation Protocol (SIP).

c3: IF A.4/34 THEN o ELSE n/a – – the P-Access-Network-Info header extension.

c4: IF A.4/36 THEN o ELSE n/a – – the P-Charging-Vector header extension.

c5: IF A.4/36 OR A.3/4 THEN m ELSE n/a – – the P-Charging-Vector header extension (including S-CSCF as registrar).

c6: IF A.4/35 THEN o ELSE n/a – – the P-Charging-Function-Addresses header extension.

c7: IF A.4/35 OR A.3/4 THEN m ELSE n/a – – the P-Charging-Function-Addresses header extension (including S-CSCF as registrar).

c8: IF A.6/18 THEN m ELSE o – – 405 (Method Not Allowed).

c9: IF A.4/47 THEN m ELSE n/a – – an extension to the session initiation protocol for request history information.

c10: IF A.4/60 THEN m ELSE n/a – – SIP location conveyance.

c13: IF A.4/91 THEN m ELSE n/a – – the Session-ID header.

c14: IF A.4/111 THEN m ELSE n/a – – the Relayed-Charge header field extension.

c15: IF A.4/119 THEN o ELSE n/a – – Content-ID header field in Session Initiation Protocol (SIP).

c16: IF A.4/119 THEN m ELSE n/a – – Content-ID header field in Session Initiation Protocol (SIP).

NOTE: For a 488 (Not Acceptable Here) response, RFC 3261 [26] gives the status of this header field as SHOULD rather than OPTIONAL.

Prerequisite A.5/19 – – REGISTER response

Prerequisite: A.6/102 – – Additional for 2xx response

Table A.123: Supported header fields within the REGISTER response

Item

Header field

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

1

Accept

[26] 20.1

o

o

[26] 20.1

o

o

1A

Accept-Encoding

[26] 20.2

o

o

[26] 20.2

m

m

1B

Accept-Language

[26] 20.3

o

o

[26] 20.3

m

m

1C

Accept-Resource-Priority

[116] 3.2

c14

c14

[116] 3.2

c14

c14

2

Allow-Events

[28] 8.2.2

c12

c12

[28] 8.2.2

c13

c13

3

Authentication-Info

[26] 20.6

c6

c6

[26] 20.6

c7

c7

5

Contact

[26] 20.10

o

o

[26] 20.10

m

m

5A

Feature-Caps

[190]

c18

c18

[190]

c17

c17

5B

Flow-Timer

[92] 11

c15

c15

[92] 11

c15

c15

5C

P-Associated-URI

[52] 4.1

c8

c9

[52] 4.1

c10

c11

6

Path

[35] 4

c3

c3

[35] 4

c4

c4

7

Security-Server

Subclause 7.2A.7

n/a

x

Subclause 7.2A.7

n/a

c16

8

Service-Route

[38] 5

c5

c5

[38] 5

c5

c5

9

Supported

[26] 20.37

m

m

[26] 20.37

m

m

c1: IF (A.3/4 AND A.4/2) THEN m ELSE n/a. – – S-CSCF acting as registrar.

c2: IF A.3/4 OR A.3/1 THEN m ELSE n/a. – – S-CSCF or UE.

c3: IF A.4/24 THEN m ELSE n/a – – session initiation protocol extension header field for registering non-adjacent contacts.

c4: IF A.4/24 THEN o ELSE n/a – – session initiation protocol extension header field for registering non-adjacent contacts.

c5: IF A.4/28 THEN m ELSE n/a – – session initiation protocol extension header field for service route discovery during registration.

c6: IF A.4/8 THEN o ELSE n/a – – authentication between UA and registrar.

c7: IF A.4/8 THEN m ELSE n/a – – authentication between UA and registrar.

c8: IF A.4/2 AND A.4/31 THEN m ELSE n/a – – P-Associated-URI header extension and registrar.

c9: IF A.3/1 AND A.4/31 THEN m ELSE n/a – – P-Associated-URI header extension and S-CSCF.

c10: IF A.4/31 THEN o ELSE n/a – – P-Associated-URI header extension.

c11: IF A.4/31 AND A.3/1 THEN m ELSE n/a – – P-Associated-URI header extension and UE.

c12: IF A.4/22 THEN o ELSE n/a – – acting as the notifier of event information.

c13: IF A.4/23 THEN m ELSE n/a – – acting as the subscriber to event information.

c14: IF A.4/70B THEN m ELSE n/a – – inclusion of CANCEL, BYE, REGISTER and PUBLISH in communications resource priority for the session initiation protocol.

c15: IF A.4/57 THEN m ELSE n/a – – managing client initiated connections in SIP.

c16: IF A.4/37A THEN m ELSE n/a – – mediasec header field parameter for marking security mechanisms related to media.

c17: IF A.4/100 THEN m ELSE n/a – – indication of features supported by proxy.

c18: IF A.4/100 AND A.3/1 AND NOT A.3C/1 THEN n/a ELSE IF A.4/100 THEN m ELSE n/a – – indication of features supported by proxy, UE, UE performing the functions of an external attached network.

Prerequisite A.5/19 – – REGISTER response

Prerequisite: A.6/103 OR A.6/104 OR A.6/105 OR A.6/106 – – Additional for 3xx – 6xx response

Table A.123A: Supported header fields within the REGISTER response

Item

Header field

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

1

Error-Info

[26] 20.18

o

o

[26] 20.18

o

o

2

Response-Source

7.2.17

n/a

c1

7.2.17

n/a

c1

c1: IF A.4/115 THEN o ELSE n/a – – use of the Response-Source header field in SIP error responses?

Prerequisite A.5/19 – – REGISTER response

Prerequisite: A.6/103 OR A.6/35 – – Additional for 3xx or 485 (Ambiguous) response

Table A.124: Supported header fields within the REGISTER response

Item

Header field

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

3

Contact

[26] 20.10

o (note)

o

[26] 20.10

m

m

Prerequisite A.5/19 – – REGISTER response

Prerequisite: A.6/14 – – Additional for 401 (Unauthorized) response

Table A.125: Supported header fields within the REGISTER response

Item

Header field

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

4

Proxy-Authenticate

[26] 20.27

c1

x

[26] 20.27

c1

x

6

Security-Server

[48] 2

x

x

[48] 2

n/a

c2

10

WWW-Authenticate

[26] 20.44

m

m

[26] 20.44

m

m

c1: IF A.4/8 THEN m ELSE n/a – – support of authentication between UA and registrar.

c2: IF A.4/37 THEN m ELSE n/a – – security mechanism agreement for the session initiation protocol.

Prerequisite A.5/19 – – REGISTER response

Prerequisite: A.6/17 OR A.6/23 OR A.6/30 OR A.6/36 OR A.6/42 OR A.6/45 OR A.6/50 OR A.6/51 – – Additional for 404 (Not Found), 413 (Request Entity Too Large), 480(Temporarily not available), 486 (Busy Here), 500 (Internal Server Error), 503 (Service Unavailable), 600 (Busy Everywhere), 603 (Decline) response

Table A.126: Supported header fields within the REGISTER response

Item

Header field

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

6

Retry-After

[26] 20.33

o

o

[26] 20.33

o

o

Table A.127: Void

Prerequisite A.5/19 – – REGISTER response

Prerequisite: A.6/20 – – Additional for 407 (Proxy Authentication Required) response

Table A.128: Supported header fields within the REGISTER response

Item

Header field

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

5

Proxy-Authenticate

[26] 20.27

c1

x

[26] 20.27

c1

x

9

WWW-Authenticate

[26] 20.44

o

o

[26] 20.44

o

o

c1: IF A.4/8 THEN m ELSE n/a – – support of authentication between UA and registrar.

Prerequisite A.5/19 – – REGISTER response

Prerequisite: A.6/25 – – Additional for 415 (Unsupported Media Type) response

Table A.129: Supported header fields within the REGISTER response

Item

Header field

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

1

Accept

[26] 20.1

o.1

o.1

[26] 20.1

m

m

2

Accept-Encoding

[26] 20.2

o.1

o.1

[26] 20.2

m

m

3

Accept-Language

[26] 20.3

o.1

o.1

[26] 20.3

m

m

o.1 At least one of these capabilities is supported.

Prerequisite A.5/19 – – REGISTER response

Prerequisite: A.6/26A – – Additional for 417 (Unknown Resource-Priority) response

Table A.129A: Supported header fields within the REGISTER response

Item

Header field

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

1

Accept-Resource-Priority

[116] 3.2

c1

c1

[116] 3.2

c1

c1

c1: IF A.4/70B THEN m ELSE n/a – – inclusion of CANCEL, BYE, REGISTER and PUBLISH in communications resource priority for the session initiation protocol.

Prerequisite A.5/19 – – REGISTER response

Prerequisite: A.6/27 – – Additional for 420 (Bad Extension) response

Table A.130: Supported header fields within the REGISTER response

Item

Header field

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

8

Unsupported

[26] 20.40

m

m

[26] 20.40

m

m

Prerequisite A.5/19 – – REGISTER response

Prerequisite: A.6/28 OR A.6/41A – – Additional for 421 (Extension Required), 494 (Security Agreement Required) response

Table A.130A: Supported header fields within the REGISTER response

Item

Header field

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

3

Security-Server

[48] 2

c2

c2

[48] 2

c1

c1

c1: IF A.4/37 THEN m ELSE n/a – – security mechanism agreement for the session initiation protocol.

c2: IF A.4/37 AND A.4/2 THEN m ELSE n/a – – security mechanism agreement for the session initiation protocol and registrar.

Prerequisite A.5/19 – – REGISTER response

Prerequisite: A.6/29 – – Additional for 423 (Interval Too Brief) response

Table A.131: Supported header fields within the REGISTER response

Item

Header field

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

5

Min-Expires

[26] 20.23

m

m

[26] 20.23

m

m

Table A.132: Void

Prerequisite A.5/19 – – REGISTER response

Table A.133: Supported message bodies within the REGISTER response

Item

Header

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

1

A.2.1.4.13 SUBSCRIBE method

Prerequisite A.5/20 – – SUBSCRIBE request

Table A.134: Supported header fields within the SUBSCRIBE request

Item

Header field

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

1

Accept

[26] 20.1

o

o

[26] 20.1

m

m

1A

Accept-Contact

[56B] 9.2

c22

c22

[56B] 9.2

c26

c26

2

Accept-Encoding

[26] 20.2

o

o

[26] 20.2

m

m

3

Accept-Language

[26] 20.3

o

o

[26] 20.3

m

m

3A

Allow

[26] 20.5

o

o

[26] 20.5

m

m

4

Allow-Events

[28] 8.2.2

o

o

[28] 8.2.2

m

m

5

Authorization

[26] 20.7

c3

c3

[26] 20.7

c3

c3

6

Call-ID

[26] 20.8

m

m

[26] 20.8

m

m

6A

Call-Info

[26] 20.9

o

o

[26] 20.9

o

o

6B

Cellular-Network-Info

7.2.15

n/a

c48

7.2.15

n/a

c49

6C

Contact

[26] 20.10

m

m

[26] 20.10

m

m

7

Content-Disposition

[26] 20.11

o

o

[26] 20.11

m

m

8

Content-Encoding

[26] 20.12

o

o

[26] 20.12

m

m

8A

Content-ID

[256] 3.2

o

c52

[256] 3.2

m

c53

9

Content-Language

[26] 20.13

o

o

[26] 20.13

m

m

10

Content-Length

[26] 20.14

m

m

[26] 20.14

m

m

11

Content-Type

[26] 20.15

m

m

[26] 20.15

m

m

12

CSeq

[26] 20.16

m

m

[26] 20.16

m

m

13

Date

[26] 20.17

c4

c4

[26] 20.17

m

m

14

Event

[28] 8.2.1

m

m

[28] 8.2.1

m

m

15

Expires

[26] 20.19

o (note 1)

o (note 1)

[26] 20.19

m

m

15A

Feature-Caps

[190]

c46

c46

[190]

c45

c45

16

From

[26] 20.20

m

m

[26] 20.20

m

m

16A

Geolocation

[89] 4.1

c27

c27

[89] 4.1

c27

c27

16B

Geolocation-Routing

[89] 4.2

c27

c27

[89] 4.2

c27

c27

16C

History-Info

[66] 4.1

c25

c25

[66] 4.1

c25

c25

16D

Max-Breadth

[117] 5.8

n/a

c38

[117] 5.8

c39

c39

17

Max-Forwards

[26] 20.22

m

m

[26] 20.22

n/a

c41

18

MIME-Version

[26] 20.24

o

o

[26] 20.24

m

m

18A

Organization

[26] 20.25

o

o

[26] 20.25

o

o

18B

P-Access-Network-Info

[52] 4.4, [234] 2

c12

c13

[52] 4.4, [234] 2

c12

c14

18C

P-Asserted-Identity

[34] 9.1

n/a

c50

[34] 9.1

c6

c6

18D

P-Asserted-Service

[121] 4.1

n/a

c51

[121] 4.1

c32

c32

18E

P-Called-Party-ID

[52] 4.2

x

x

[52] 4.2

c10

c10

18F

P-Charging-Function-Addresses

[52] 4.5

c17

c18

[52] 4.5

c17

c18

18G

P-Charging-Vector

[52] 4.6

c15

c16

[52] 4.6

c15

c16

18I

P-Preferred-Identity

[34] 9.2

c6

c7

[34] 9.2

n/a

n/a

18J

P-Preferred-Service

[121] 4.2

c31

c30

[121] 4.2

n/a

n/a

18K

P-Private-Network-Indication

[134]

c35

c35

[134]

c35

c35

18L

P-Profile-Key

[97] 5

n/a

n/a

[97] 5

n/a

n/a

18M

P-Served-User

[133] 6

c40

c40

[133] 6

c40

c40

18N

P-User-Database

[82] 4

n/a

n/a

[82] 4

n/a

n/a

18O

P-Visited-Network-ID

[52] 4.3

x (note 2)

x

[52] 4.3

c11

n/a

18P

Priority

[26] 20.26

o

o

[26] 20.26

o

o

18Q

Privacy

[33] 4.2

c9

c9

[33] 4.2

c9

c9

19

Proxy-Authorization

[26] 20.28

c5

c5

[26] 20.28

n/a

n/a

20

Proxy-Require

[26] 20.29

o

n/a

[26] 20.29

n/a

n/a

20A

Reason

[34A] 2

c21

c21

[34A] 2

c21

c21

21

Record-Route

[26] 20.30

n/a

c41

[26] 20.30

m

m

21A

Referred-By

[59] 3

c23

c23

[59] 3

c24

c24

21B

Reject-Contact

[56B] 9.2

c22

c22

[56B] 9.2

c26

c26

21C

Relayed-Charge

7.2.12

n/a

c47

7.2.12

n/a

c47

21D

Request-Disposition

[56B] 9.1

c22

c22

[56B] 9.1

c26

c26

22

Require

[26] 20.32

m

m

[26] 20.32

m

m

22A

Resource-Priority

[116] 3.1

c29

c29

[116] 3.1

c29

c29

23

Route

[26] 20.34

m

m

[26] 20.34

n/a

c41

23A

Security-Client

[48] 2.3.1

c19

c19

[48] 2.3.1

n/a

n/a

23B

Security-Verify

[48] 2.3.1

c20

c20

[48] 2.3.1

n/a

n/a

23C

Session-ID

[162]

o

c42

[162]

o

c42

24

Supported

[26] 20.37

o

o

[26] 20.37

m

m

24A

Target-Dialog

[184] 7

c43

c43

[184] 7

c44

c44

25

Timestamp

[26] 20.38

c8

c8

[26] 20.38

m

m

26

To

[26] 20.39

m

m

[26] 20.39

m

m

26A

Trigger-Consent

[125] 5.11.2

c33

c33

[125] 5.11.2

c34

c34

27

User-Agent

[26] 20.41

o

o

[26] 20.41

o

o

28

Via

[26] 20.42

m

m

[26] 20.42

m

m

c3: IF A.4/7 THEN m ELSE n/a – – authentication between UA and UA.

c4: IF A.4/11 THEN o ELSE n/a – – insertion of date in requests and responses.

c5: IF A.4/8A THEN m ELSE n/a – – authentication between UA and proxy.

c6: IF A.4/25 THEN o ELSE n/a – – private extensions to the Session Initiation Protocol (SIP) for asserted identity within trusted networks.

c7: IF A.3/1 AND A.4/25 THEN o ELSE n/a – – UE and private extensions to the Session Initiation Protocol (SIP) for asserted identity within trusted networks.

c8: IF A.4/6 THEN o ELSE n/a – – timestamping of requests.

c9: IF A.4/26 THEN o ELSE n/a – – a privacy mechanism for the Session Initiation Protocol (SIP).

c10: IF A.4/32 THEN o ELSE n/a – – the P-Called-Party-ID extension.

c11: IF A.4/33 THEN o ELSE n/a – – the P-Visited-Network-ID extension.

c12: IF A.4/34 THEN o ELSE n/a – – the P-Access-Network-Info header extension.

c13: IF A.4/34 AND A.3/1 THEN m ELSE n/a – – the P-Access-Network-Info header extension and UE.

c14: IF A.4/34 AND (A.3/7A OR A.3/7D) THEN m ELSE n/a – – the P-Access-Network-Info header extension and AS acting as terminating UA or AS acting as third-party call controller.

c15: IF A.4/36 THEN o ELSE n/a – – the P-Charging-Vector header extension.

c16: IF A.4/36 THEN m ELSE n/a – – the P-Charging-Vector header extension.

c17: IF A.4/35 THEN o ELSE n/a – – the P-Charging-Function-Addresses header extension.

c18: IF A.4/35 THEN m ELSE n/a – – the P-Charging-Function-Addresses header extension.

c19: IF A.4/37 OR A.4/37A THEN o ELSE n/a – – security mechanism agreement for the session initiation protocol or mediasec header field parameter for marking security mechanisms related to media (note 3).

c20: IF A.4/37 OR A.4/37A THEN m ELSE n/a – – security mechanism agreement for the session initiation protocol or mediasec header field parameter for marking security mechanisms related to media.

c21: IF A.4/38 THEN o ELSE n/a – – the Reason header field for the session initiation protocol.

c22: IF A.4/40 THEN o ELSE n/a – – caller preferences for the session initiation protocol.

c23: IF A.4/43 THEN m ELSE n/a – – the SIP Referred-By mechanism.

c24: IF A.4/43 THEN o ELSE n/a – – the SIP Referred-By mechanism.

c25: IF A.4/47 THEN m ELSE n/a – – an extension to the session initiation protocol for request history information.

c26: IF A.4/40 THEN m ELSE n/a – – caller preferences for the session initiation protocol.

c27: IF A.4/60 THEN m ELSE n/a – – SIP location conveyance.

c29: IF A.4/70A THEN m ELSE n/a – – inclusion of MESSAGE, SUBSCRIBE, NOTIFY in communications resource priority for the session initiation protocol.

c30: IF (A.3/1 OR A.3A/81) AND A.4/74 THEN o ELSE n/a – – UE, MSC Server enhanced for ICS and SIP extension for the identification of services.

c31: IF A.4/74 THEN o ELSE n/a – – SIP extension for the identification of services.

c32: IF A.4/74 THEN m ELSE n/a – – SIP extension for the identification of services.

c33: IF A.4/75A THEN m ELSE n/a – – a relay within the framework for consent-based communications in SIP.

c34: IF A.4/75B THEN m ELSE n/a – – a recipient within the framework for consent-based communications in SIP.

c35: IF A.4/77 THEN m ELSE n/a – – the SIP P-Private-Network-Indication private-header (P-Header).

c38: IF A.4/71 AND (A.3/9B OR A.3/9C OR A.3/13B OR A.3/13C) THEN m ELSE IF A.3/1 AND NOT A.3C/1 THEN n/a ELSE o – – addressing an amplification vulnerability in session initiation protocol forking proxies, IBCF (IMS-ALG), IBCF (Screening of SIP signalling), ISC gateway function (IMS-ALG), ISC gateway function (Screening of SIP signalling), UE, UE performing the functions of an external attached network.

c39: IF A.4/71 THEN m ELSE n/a – – addressing an amplification vulnerability in session initiation protocol forking proxies.

c40: IF A.4/78 THEN m ELSE n/a – – the SIP P-Served-User private header.

c41: IF A.3/1 AND NOT A.3C/1 THEN n/a ELSE o – – UE, UE performing the functions of an external attached network.

c42: IF A.4/91 THEN m ELSE n/a – – the Session-ID header.

c43: IF A.4/99 THEN o ELSE n/a – – request authorization through dialog Identification in the session initiation protocol.

c44: IF A.4/99 THEN m ELSE n/a – – request authorization through dialog Identification in the session initiation protocol.

c45: IF A.4/100 THEN m ELSE n/a – – indication of features supported by proxy.

c46: IF A.4/100 AND A.3/1 AND NOT A.3C/1 THEN n/a ELSE IF A.4/100 THEN m ELSE n/a – – indication of features supported by proxy, UE, UE performing the functions of an external attached network.

c47: IF A.4/111 THEN m ELSE n/a – – the Relayed-Charge header field extension.

c48: IF A.4/113 AND A.3/1 THEN m ELSE n/a – – the Cellular-Network-Info header extension and UE.

c49: IF A.4/113 AND (A.3/7A OR A.3/7D) THEN m ELSE n/a – – the Cellular-Network-Info header extension and AS acting as terminating UA or AS acting as third-party call controller.

c50: IF A.4/25 AND (A.3/7B OR A.3/8 OR A.3A/81) THEN o ELSE n/a – – private extensions to the Session Initiation Protocol (SIP) for asserted identity within trusted networks and AS acting as originating UA, MRFC, MSC Server enhanced for ICS.

c51: IF A.4/74 AND A.3/7B THEN o ELSE n/a – – SIP extension for the identification of services and AS acting as originating UA.

c52: IF A.4/119 THEN o ELSE n/a – – Content-ID header field in Session Initiation Protocol (SIP).

c53: IF A.4/119 THEN m ELSE n/a – – Content-ID header field in Session Initiation Protocol (SIP).

NOTE 1: The strength of this requirement is RECOMMENDED rather than OPTIONAL.

NOTE 2: The strength of this requirement in RFC 7315 [52] is SHOULD NOT, rather than MUST NOT.

NOTE 3: Support of this header field in this method is dependent on the security mechanism and the security architecture which is implemented. Use of this header field in this method is not appropriate to the security mechanism defined by 3GPP TS 33.203 [19].

Prerequisite A.5/20 – – SUBSCRIBE request

Table A.135: Supported message bodies within the SUBSCRIBE request

Item

Header

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

1

application/vnd.3gpp.mcptt-info+xml

[8ZE]

n/a

c1

[8ZE]

n/a

c1

2

application/simple-filter+xml

[243]

o

c1

[243]

n/a

c1

c1 IF A.3A/102 OR A.3A/103 THEN m ELSE n/a – – MCPTT client, MCPTT server.

Prerequisite A.5/21 – – SUBSCRIBE response

Prerequisite: A.6/1 – – Additional for 100 (Trying) response

Table A.135A: Supported header fields within the SUBSCRIBE response

Item

Header field

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

1

Call-ID

[26] 20.8

m

m

[26] 20.8

m

m

2

Content-Length

[26] 20.14

m

m

[26] 20.14

m

m

3

CSeq

[26] 20.16

m

m

[26] 20.16

m

m

4

Date

[26] 20.17

c1

c1

[26] 20.17

m

m

5

From

[26] 20.20

m

m

[26] 20.20

m

m

6

To

[26] 20.39

m

m

[26] 20.39

m

m

7

Via

[26] 20.42

m

m

[26] 20.42

m

m

c1: IF A.4/11 THEN o ELSE n/a – – insertion of date in requests and responses.

Prerequisite A.5/21 – – SUBSCRIBE response for all remaining status-codes

Table A.136: Supported header fields within the SUBSCRIBE response

Item

Header field

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

0A

Allow

[26] 20.5

c12

c12

[26] 20.5

m

m

1

Call-ID

[26] 20.8

m

m

[26] 20.8

m

m

1A

Call-Info

[26] 20.9

o

o

[26] 20.9

o

o

1B

Cellular-Network-Info

7.2.15

n/a

c19

7.2.15

n/a

c20

2

Content-Disposition

[26] 20.11

o

o

[26] 20.11

m

m

3

Content-Encoding

[26] 20.12

o

o

[26] 20.12

m

m

3A

Content-ID

[256] 3.2

o

c22

[256] 3.2

m

c23

4

Content-Language

[26] 20.13

o

o

[26] 20.13

m

m

5

Content-Length

[26] 20.14

m

m

[26] 20.14

m

m

6

Content-Type

[26] 20.15

m

m

[26] 20.15

m

m

7

CSeq

[26] 20.16

m

m

[26] 20.16

m

m

8

Date

[26] 20.17

c1

c1

[26] 20.17

m

m

9

From

[26] 20.20

m

m

[26] 20.20

m

m

9A

Geolocation-Error

[89] 4.3

c14

c14

[89] 4.3

c14

c14

9B

History-Info

[66] 4.1

c13

c13

[66] 4.1

c13

c13

10

MIME-Version

[26] 20.24

o

o

[26] 20.24

m

m

10A

Organization

[26] 20.25

o

o

[26] 20.25

o

o

10B

P-Access-Network-Info

[52] 4.4, [52A] 4, [234] 2

c5

c6

[52] 4.4, [52A] 4, [234] 2

c5

c7

10C

P-Asserted-Identity

[34] 9.1

n/a

c21

[34] 9.1

c3

c3

10D

P-Charging-Function-Addresses

[52] 4.5, [52A] 4

c10

c11

[52] 4.5, [52A] 4

c10

c11

10E

P-Charging-Vector

[52] 4.6, [52A] 4

c8

c9

[52] 4.6, [52A] 4

c8

c9

10G

P-Preferred-Identity

[34] 9.2

c3

x

[34] 9.2

n/a

n/a

10H

Privacy

[33] 4.2

c4

c4

[33] 4.2

c4

c4

10I

Relayed-Charge

7.2.12

n/a

c18

7.2.12

n/a

c18

10J

Require

[26] 20.32

m

m

[26] 20.32

m

m

10K

Server

[26] 20.35

o

o

[26] 20.35

o

o

10L

Session-ID

[162]

o

c17

[162]

o

c17

11

Timestamp

[26] 20.38

m

m

[26] 20.38

c2

c2

12

To

[26] 20.39

m

m

[26] 20.39

m

m

12A

User-Agent

[26] 20.41

o

o

[26] 20.41

o

o

13

Via

[26] 20.42

m

m

[26] 20.42

m

m

14

Warning

[26] 20.43

o (note)

o

[26] 20.43

o

o

c1: IF A.4/11 THEN o ELSE n/a – – insertion of date in requests and responses.

c2: IF A.4/6 THEN m ELSE n/a – – timestamping of requests.

c3: IF A.4/25 THEN o ELSE n/a – – private extensions to the Session Initiation Protocol (SIP) for asserted identity within trusted networks.

c4: IF A.4/26 THEN o ELSE n/a – – a privacy mechanism for the Session Initiation Protocol (SIP).

c5: IF A.4/34 THEN o ELSE n/a – – the P-Access-Network-Info header extension.

c6: IF A.4/34 AND A.3/1 THEN m ELSE n/a – – the P-Access-Network-Info header extension and UE.

c7: IF A.4/34 AND (A.3/7A OR A.3/7D) THEN m ELSE n/a – – the P-Access-Network-Info header extension and AS acting as terminating UA or AS acting as third-party call controller.

c8: IF A.4/36 THEN o ELSE n/a – – the P-Charging-Vector header extension.

c9: IF A.4/36 THEN m ELSE n/a – – the P-Charging-Vector header extension.

c10: IF A.4/35 THEN o ELSE n/a – – the P-Charging-Function-Addresses header extension.

c11: IF A.4/35 THEN m ELSE n/a – – the P-Charging-Function-Addresses header extension.

c12: IF A.6/18 THEN m ELSE o – – 405 (Method Not Allowed).

c13: IF A.4/47 THEN m ELSE n/a – – an extension to the session initiation protocol for request history information.

c14: IF A.4/60 THEN m ELSE n/a – – SIP location conveyance.

c17: IF A.4/91 THEN m ELSE n/a – – the Session-ID header.

c18: IF A.4/111 THEN m ELSE n/a – – the Relayed-Charge header field extension.

c19: IF A.4/113 AND A.3/1 THEN m ELSE n/a – – the Cellular-Network-Info extension and UE.

c20: IF A.4/113 AND (A.3/7A OR A.3/7D) THEN m ELSE n/a – – the Cellular-Network-Info header extension and AS acting as terminating UA or AS acting as third-party call controller.

c21: IF A.4/25 AND (A.3/7B OR A.3/8) THEN o ELSE n/a – – private extensions to the Session Initiation Protocol (SIP) for asserted identity within trusted networks and AS acting as originating UA, MRFC.

c22: IF A.4/119 THEN o ELSE n/a – – Content-ID header field in Session Initiation Protocol (SIP).

c23: IF A.4/119 THEN m ELSE n/a – – Content-ID header field in Session Initiation Protocol (SIP).

NOTE: For a 488 (Not Acceptable Here) response, RFC 3261 [26] gives the status of this header field as SHOULD rather than OPTIONAL.

Prerequisite A.5/21 – – SUBSCRIBE response

Prerequisite: A.6/102 – – Additional for 2xx response

Table A.137: Supported header fields within the SUBSCRIBE response

Item

Header field

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

0A

Accept-Resource-Priority

[116] 3.2

c5

c5

[116] 3.2

c5

c5

0B

Allow-Events

[28] 8.2.2

o

o

[28] 8.2.2

m

m

1

Authentication-Info

[26] 20.6

c1

c1

[26] 20.6

c2

c2

1A

Contact

[26] 20.10

m

m

[26] 20.10

m

m

2

Expires

[26] 20.19

m

m

[26] 20.19

m

m

2A

Feature-Caps

[190]

c8

c8

[190]

c7

c7

3

Record-Route

[26] 20.30

m

m

[26] 20.30

m

m

6

Supported

[26] 20.37

m

m

[26] 20.37

m

m

c1: IF A.4/7 THEN o ELSE n/a – – authentication between UA and UA.

c2: IF A.4/7 THEN m ELSE n/a – – authentication between UA and UA.

c5: IF A.4/70A THEN m ELSE n/a – – inclusion of MESSAGE, SUBSCRIBE, NOTIFY in communications resource priority for the session initiation protocol.

c7: IF A.4/100 THEN m ELSE n/a – – indication of features supported by proxy.

c8: IF A.4/100 AND A.3/1 AND NOT A.3C/1 THEN n/a ELSE IF A.4/100 THEN m ELSE n/a – – indication of features supported by proxy, UE, UE performing the functions of an external attached network.

Prerequisite A.5/21 – – SUBSCRIBE response

Prerequisite: A.6/103 OR A.6/104 OR A.6/105 OR A.6/106 – – Additional for 3xx – 6xx response

Table A.137A: Supported header fields within the SUBSCRIBE response

Item

Header field

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

1

Error-Info

[26] 20.18

o

o

[26] 20.18

o

o

2

Response-Source

7.2.17

n/a

c1

7.2.17

n/a

c1

c1: IF A.4/115 THEN o ELSE n/a – – use of the Response-Source header field in SIP error responses?

Prerequisite A.5/21 – – SUBSCRIBE response

Prerequisite: A.6/103 OR A.6/35 – – Additional for 3xx or 485 (Ambiguous) response

Table A.138: Supported header fields within the SUBSCRIBE response

Item

Header field

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

1

Contact

[26] 20.10

m (note)

m

[26] 20.10

m

m

NOTE: The strength of this requirement is RECOMMENDED rather than MANDATORY for a 485 response.

Prerequisite A.5/21 – – SUBSCRIBE response

Prerequisite: A.6/14 – – Additional for 401 (Unauthorized) response

Table A.139: Supported header fields within the SUBSCRIBE response

Item

Header field

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

2

Proxy-Authenticate

[26] 20.27

c1

c1

[26] 20.27

c1

c1

8

WWW-Authenticate

[26] 20.44

m

m

[26] 20.44

m

m

c1: IF A.4/7 THEN m ELSE n/a – – support of authentication between UA and UA.

Prerequisite A.5/21 – – SUBSCRIBE response

Prerequisite: A.6/17 OR A.6/23 OR A.6/30 OR A.6/36 OR A.6/42 OR A.6/45 OR A.6/50 OR A.6/51 – – Additional for 404 (Not Found), 413 (Request Entity Too Large), 480 (Temporarily not available), 486 (Busy Here), 500 (Internal Server Error), 503 (Service Unavailable), 600 (Busy Everywhere), 603 (Decline) response

Table A.140: Supported header fields within the SUBSCRIBE response

Item

Header field

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

3

Retry-After

[26] 20.33

o

o

[26] 20.33

o

o

Table A.141: Void

Prerequisite A.5/21 – – SUBSCRIBE response

Prerequisite: A.6/20 – – Additional for 407 (Proxy Authentication Required) response

Table A.142: Supported header fields within the SUBSCRIBE response

Item

Header field

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

2

Proxy-Authenticate

[26] 20.27

c1

c1

[26] 20.27

c1

c1

6

WWW-Authenticate

[26] 20.44

o

o

[26] 20.44

o

o

c1: IF A.4/7 THEN m ELSE n/a – – support of authentication between UA and UA.

Table A.142A: Void

Prerequisite A.5/21 – – SUBSCRIBE response

Prerequisite A.6/25 – – Additional for 415 (Unsupported Media Type) response

Table A.143: Supported header fields within the SUBSCRIBE response

Item

Header field

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

1

Accept

[26] 20.1

o.1

o.1

[26] 20.1

m

m

2

Accept-Encoding

[26] 20.2

o.1

o.1

[26] 20.2

m

m

3

Accept-Language

[26] 20.3

o.1

o.1

[26] 20.3

m

m

o.1 At least one of these capabilities is supported.

Prerequisite A.5/21 – – SUBSCRIBE response

Prerequisite: A.6/26A – – Additional for 417 (Unknown Resource-Priority) response

Table A.143A: Supported header fields within the SUBSCRIBE response

Item

Header field

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

1

Accept-Resource-Priority

[116] 3.2

c1

c1

[116] 3.2

c1

c1

c1: IF A.4/70A THEN m ELSE n/a – – inclusion of MESSAGE, SUBSCRIBE, NOTIFY in communications resource priority for the session initiation protocol.

Prerequisite A.5/21 – – SUBSCRIBE response

Prerequisite: A.6/27 – – Additional for 420 (Bad Extension) response

Table A.144: Supported header fields within the SUBSCRIBE response

Item

Header field

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

5

Unsupported

[26] 20.40

m

m

[26] 20.40

m

m

Prerequisite A.5/21 – – SUBSCRIBE response

Prerequisite: A.6/28 OR A.6/41A – – Additional for 421 (Extension Required), 494 (Security Agreement Required) response

Table A.144A: Supported header fields within the SUBSCRIBE response

Item

Header field

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

3

Security-Server

[48] 2

x

x

[48] 2

c1

c1

c1: IF A.4/37 THEN m ELSE n/a – – security mechanism agreement for the session initiation protocol.

Prerequisite A.5/21 – – SUBSCRIBE response

Prerequisite: A.6/29 – – Additional for 423 (Interval Too Brief) response

Table A.145: Supported header fields within the SUBSCRIBE response

Item

Header field

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

2

Min-Expires

[26] 20.23

m

m

[26] 20.23

m

m

Table A.146: Void

Prerequisite A.5/21 – – SUBSCRIBE response

Prerequisite: A.6/29H – – Additional for 470 (Consent Needed) response

Table A.146A: Supported header fields within the SUBSCRIBE response

Item

Header field

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

1

Permission-Missing

[125] 5.9.3

m

m

[125] 5.9.3

m

m

Prerequisite A.5/21 – – SUBSCRIBE response

Prerequisite: A.6/39 – – Additional for 489 (Bad Event) response

Table A.147: Supported header fields within the SUBSCRIBE response

Item

Header field

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

1

Allow-Events

[28] 8.2.2

m

m

[28] 8.2.2

m

m

Table A.148: Void

Prerequisite A.5/21 – – SUBSCRIBE response

Prerequisite: A.6/46 – – Additional for 504 (Server Time-out) response

Table A.148A: Supported header fields within the SUBSCRIBE response

Item

Header field

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

1

Restoration-Info

subclause 7.2.11

n/a

c1

subclause 7.2.11

n/a

n/a

c1: IF A.4/110 THEN o ELSE n/a – – HSS based P-CSCF restoration.

Prerequisite A.5/21 – – SUBSCRIBE response

Table A.149: Supported message bodies within the SUBSCRIBE response

Item

Header

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

1

A.2.1.4.14 UPDATE method

Prerequisite A.5/22 – – UPDATE request

Table A.150: Supported header fields within the UPDATE request

Item

Header field

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

1

Accept

[26] 20.1

o

o

[26] 20.1

m

m

1A

Accept-Contact

[56B] 9.2

c20

c20

[56B] 9.2

c24

c24

2

Accept-Encoding

[26] 20.2

o

o

[26] 20.2

m

m

3

Accept-Language

[26] 20.3

o

o

[26] 20.3

m

m

4

Allow

[26] 20.5

o

o

[26] 20.5

m

m

5

Allow-Events

[28] 8.2.2

c2

c2

[28] 8.2.2

c3

c3

6

Authorization

[26] 20.7

c4

c4

[26] 20.7

c4

c4

7

Call-ID

[26] 20.8

m

m

[26] 20.8

m

m

8

Call-Info

[26] 20.9

o

o

[26] 20.9

o

o

8A

Cellular-Network-Info

7.2.15

n/a

c40

7.2.15

n/a

c41

9

Contact

[26] 20.10

m

m

[26] 20.10

m

m

10

Content-Disposition

[26] 20.11

o

o

[26] 20.11

m

m

11

Content-Encoding

[26] 20.12

o

o

[26] 20.12

m

m

11A

Content-ID

[256] 3.2

o

c43

[256] 3.2

m

c44

12

Content-Language

[26] 20.13

o

o

[26] 20.13

m

m

13

Content-Length

[26] 20.14

m

m

[26] 20.14

m

m

14

Content-Type

[26] 20.15

m

m

[26] 20.15

m

m

15

CSeq

[26] 20.16

m

m

[26] 20.16

m

m

16

Date

[26] 20.17

c5

c5

[26] 20.17

m

m

16A

Feature-Caps

[190]

c37

c37

[190]

c36

c36

17

From

[26] 20.20

m

m

[26] 20.20

m

m

17A

Geolocation

[89] 4.1

c25

c25

[89] 4.1

c25

c25

17B

Geolocation-Routing

[89] 4.2

c25

c25

[89] 4.2

c25

c25

17C

Max-Breadth

[117] 5.8

n/a

c29

[117] 5.8

c30

c30

18

Max-Forwards

[26] 20.22

m

m

[26] 20.22

n/a

c31

19

MIME-Version

[26] 20.24

o

o

[26] 20.24

m

m

19A

Min-SE

[58] 5

c21

c21

[58] 5

c21

c21

20

Organization

[26] 20.25

o

o

[26] 20.25

o

o

20A

P-Access-Network-Info

[52] 4.4, [234] 2

c11

c12

[52] 4.4, [234] 2

c11

c13

20B

P-Charging-Function-Addresses

[52] 4.5

c16

c17

[52] 4.5

c16

c17

20C

P-Charging-Vector

[52] 4.6

c14

c15

[52] 4.6

c14

c15

20E

P-Early-Media

[109] 8

c26

c26

[109] 8

c26

c26

20EA

Priority-Share

Subclause 7.2.16

n/a

c42

Subclause 7.2.16

n/a

c42

20F

Privacy

[33] 4.2

c6

n/a

[33] 4.2

c6

n/a

21

Proxy-Authorization

[26] 20.28

c10

c10

[26] 20.28

n/a

n/a

22

Proxy-Require

[26] 20.29

o

n/a

[26] 20.29

n/a

n/a

22A

Reason

[34A] 2

c8

c8

[34A] 2

c8

c8

23

Record-Route

[26] 20.30

n/a

c31

[26] 20.30

n/a

c31

23A

Recv-Info

[25] 5.2.3

c34

c34

[25] 5.2.3

c34

c34

23B

Referred-By

[59] 3

c22

c22

[59] 3

c23

c23

23C

Reject-Contact

[56B] 9.2

c20

c20

[56B] 9.2

c24

c24

23D

Relayed-Charge

7.2.12

n/a

c38

7.2.12

n/a

c38

23E

Request-Disposition

[56B] 9.1

c20

c20

[56B] 9.1

c24

c24

24

Require

[26] 20.32

m

m

[26] 20.32

m

m

24A

Resource-Priority

[116] 3.1

c33

c33

[116] 3.1

c33

c33

24B

Resource-Share

Subclause 7.2.13

n/a

c39

Subclause 7.2.13

n/a

c39

25

Route

[26] 20.34

m

m

[26] 20.34

n/a

c31

25A

Security-Client

[48] 2.3.1

c18

c18

[48] 2.3.1

n/a

n/a

25B

Security-Verify

[48] 2.3.1

c19

c19

[48] 2.3.1

n/a

n/a

25C

Session-Expires

[58] 4

c21

c21

[58] 4

c21

c21

25D

Session-ID

[162]

o

c35

[162]

o

c35

26

Supported

[26] 20.37

o

o

[26] 20.37

m

m

27

Timestamp

[26] 20.38

c9

c9

[26] 20.38

m

m

28

To

[26] 20.39

m

m

[26] 20.39

m

m

29

User-Agent

[26] 20.41

o

o

[26] 20.41

o

o

30

Via

[26] 20.42

m

m

[26] 20.42

m

m

c2: IF A.4/22 THEN o ELSE n/a – – acting as the notifier of event information.

c3: IF A.4/23 THEN m ELSE n/a – – acting as the subscriber to event information.

c4: IF A.4/7 THEN m ELSE n/a – – authentication between UA and UA.

c5: IF A.4/11 THEN o ELSE n/a – – insertion of date in requests and responses.

c6: IF A.4/26 THEN o ELSE n/a – – a privacy mechanism for the Session Initiation Protocol (SIP).

c8: IF A.4/38 THEN o ELSE n/a – – the Reason header field for the session initiation protocol.

c9: IF A.4/6 THEN o ELSE n/a – – timestamping of requests.

c10: IF A.4/8A THEN m ELSE n/a – – authentication between UA and proxy.

c11: IF A.4/34 THEN o ELSE n/a – – the P-Access-Network-Info header extension.

c12: IF A.4/34 AND A.3/1 THEN m ELSE n/a – – the P-Access-Network-Info header extension and UE.

c13: IF A.4/34 AND (A.3/7A OR A.3/7D OR A3A/84) THEN m ELSE n/a – – the P-Access-Network-Info header extension and AS acting as terminating UA, AS acting as third-party call controller or EATF.

c14: IF A.4/36 THEN o ELSE n/a – – the P-Charging-Vector header extension.

c15: IF A.4/36 THEN m ELSE n/a – – the P-Charging-Vector header extension.

c16: IF A.4/35 THEN o ELSE n/a – – the P-Charging-Function-Addresses header extension.

c17: IF A.4/35 THEN m ELSE n/a – – the P-Charging-Function-Addresses header extension.

c18: IF A.4/37 OR A.4/37A THEN o ELSE n/a – – security mechanism agreement for the session initiation protocol or mediasec header field parameter for marking security mechanisms related to media (note).

c19: IF A.4/37 OR A.4/37A THEN m ELSE n/a – – security mechanism agreement for the session initiation protocol or mediasec header field parameter for marking security mechanisms related to media.

c20: IF A.4/40 THEN o ELSE n/a – – caller preferences for the session initiation protocol.

c21: IF A.4/42 THEN m ELSE n/a – – the SIP session timer.

c22: IF A.4/43 THEN m ELSE n/a – – the SIP Referred-By mechanism.

c23: IF A.4/43 THEN o ELSE n/a – – the SIP Referred-By mechanism.

c24: IF A.4/40 THEN m ELSE n/a – – caller preferences for the session initiation protocol.

c25: IF A.4/60 THEN m ELSE n/a – – SIP location conveyance.

c26: IF A.4/66 THEN m ELSE n/a – – the SIP P-Early-Media private header extension for authorization of early media.

c29: IF A.4/71 AND (A.3/9B OR A.3/9C OR A.3/13B OR A.3/13C) THEN m ELSE IF A.3/1 AND NOT A.3C/1 THEN n/a ELSE o – – addressing an amplification vulnerability in session initiation protocol forking proxies, IBCF (IMS-ALG), IBCF (Screening of SIP signalling), ISC gateway function (IMS-ALG), ISC gateway function (Screening of SIP signalling), UE, UE performing the functions of an external attached network.

c30: IF A.4/71 THEN m ELSE n/a – – addressing an amplification vulnerability in session initiation protocol forking proxies.

c31: IF A.3/1 AND NOT A.3C/1 THEN n/a ELSE o – – UE, UE performing the functions of an external attached network.

c33: IF A.4/70 THEN m ELSE n/a – – communications resource priority for the session initiation protocol.

c34: IF A.4/13 THEN m ELSE IF A.4/13A THEN m ELSE n/a – – SIP INFO method and package framework, legacy INFO usage.

c35: IF A.4/91 THEN m ELSE n/a – – the Session-ID header.

c36: IF A.4/100 THEN m ELSE n/a – – indication of features supported by proxy.

c37: IF A.4/100 AND A.3/1 AND NOT A.3C/1 THEN n/a ELSE IF A.4/100 THEN m ELSE n/a – – indication of features supported by proxy, UE, UE performing the functions of an external attached network.

c38: IF A.4/111 THEN m ELSE n/a – – the Relayed-Charge header field extension.

c39: IF A.4/112 THEN o ELSE n/a – – resource sharing.

c40: IF A.4/113 AND A.3/1 THEN m ELSE n/a – – the Cellular-Network-Info header extension and UE.

c41: IF A.4/113 AND (A.3/7A OR A.3/7D OR A3A/84) THEN m ELSE n/a – – the Cellular-Network-Info header extension and AS acting as terminating UA or AS acting as third-party call controller or EATF.

c42: IF A.4/114 THEN o ELSE n/a – – priority sharing.

c43: IF A.4/119 THEN o ELSE n/a – – Content-ID header field in Session Initiation Protocol (SIP).

c44: IF A.4/119 THEN m ELSE n/a – – Content-ID header field in Session Initiation Protocol (SIP).

NOTE: Support of this header field in this method is dependent on the security mechanism and the security architecture which is implemented. Use of this header field in this method is not appropriate to the security mechanism defined by 3GPP TS 33.203 [19].

Prerequisite A.5/22 – – UPDATE request

Table A.151: Supported message bodies within the UPDATE request

Item

Header

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

1

Prerequisite A.5/23 – – UPDATE response

Prerequisite: A.6/1 – – Additional for 100 (Trying) response

Table A.151A: Supported header fields within the UPDATE response

Item

Header field

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

1

Call-ID

[26] 20.8

m

m

[26] 20.8

m

m

2

Content-Length

[26] 20.14

m

m

[26] 20.14

m

m

3

CSeq

[26] 20.16

m

m

[26] 20.16

m

m

4

Date

[26] 20.17

c1

c1

[26] 20.17

m

m

5

From

[26] 20.20

m

m

[26] 20.20

m

m

6

To

[26] 20.39

m

m

[26] 20.39

m

m

7

Via

[26] 20.42

m

m

[26] 20.42

m

m

c1: IF A.4/11 THEN o ELSE n/a – – insertion of date in requests and responses.

Prerequisite A.5/23 – – UPDATE response for all remaining status-codes

Table A.152: Supported header fields within the UPDATE response

Item

Header field

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

0A

Allow

[26] 20.5

c11

c11

[26] 20.5

m

m

1

Call-ID

[26] 20.8

m

m

[26] 20.8

m

m

1A

Call-Info

[26] 20.9

o

o

[26] 20.9

o

o

1B

Cellular-Network-Info

7.2.15

n/a

c19

7.2.15

n/a

c20

1C

Contact

[26] 20.10

o

o

[26] 20.10

o

o

2

Content-Disposition

[26] 20.11

o

o

[26] 20.11

m

m

3

Content-Encoding

[26] 20.12

o

o

[26] 20.12

m

m

3A

Content-ID

[256] 3.2

o

c21

[256] 3.2

m

c22

4

Content-Language

[26] 20.13

o

o

[26] 20.13

m

m

5

Content-Length

[26] 20.14

m

m

[26] 20.14

m

m

6

Content-Type

[26] 20.15

m

m

[26] 20.15

m

m

7

CSeq

[26] 20.16

m

m

[26] 20.16

m

m

8

Date

[26] 20.17

c1

c1

[26] 20.17

m

m

9

From

[26] 20.20

m

m

[26] 20.20

m

m

9A

Geolocation-Error

[89] 4.3

c13

c13

[89] 4.3

c13

c13

10

MIME-Version

[26] 20.24

o

o

[26] 20.24

m

m

10A

Organization

[26] 20.25

o

o

[26] 20.25

o

o

10B

P-Access-Network-Info

[52] 4.4, [52A] 4, [234] 2

c4

c5

[52] 4.4, [52A] 4, [234] 2

c4

c6

10C

P-Charging-Function-Addresses

[52] 4.5, [52A] 4

c9

c10

[52] 4.5, [52A] 4

c9

c10

10D

P-Charging-Vector

[52] 4.6, [52A] 4

c7

c8

[52] 4.6, [52A] 4

c7

c8

10F

Privacy

[33] 4.2

c3

n/a

[33] 4.2

c3

n/a

10G

Recv-Info

[25] 5.2.3

c16

c16

[25] 5.2.3

c16

c16

10H

Relayed-Charge

7.2.12

n/a

c18

7.2.12

n/a

c18

10I

Require

[26] 20.31

m

m

[26] 20.31

m

m

10J

Server

[26] 20.35

o

o

[26] 20.35

o

o

10K

Session-ID

[162]

o

c17

[162]

o

c17

11

Timestamp

[26] 20.38

c12

c12

[26] 20.38

c2

c2

12

To

[26] 20.39

m

m

[26] 20.39

m

m

12A

User-Agent

[26] 20.41

o

o

[26] 20.41

o

o

13

Via

[26] 20.42

m

m

[26] 20.42

m

m

14

Warning

[26] 20.43

o (note)

o

[26] 20.43

o

o

c1: IF A.4/11 THEN o ELSE n/a – – insertion of date in requests and responses.

c2: IF A.4/6 THEN m ELSE n/a – – timestamping of requests.

c3: IF A.4/26 THEN o ELSE n/a – – a privacy mechanism for the Session Initiation Protocol (SIP).

c4: IF A.4/34 THEN o ELSE n/a – – the P-Access-Network-Info header extension.

c5: IF A.4/34 AND A.3/1 THEN m ELSE n/a – – the P-Access-Network-Info header extension and UE.

c6: IF A.4/34 AND (A.3/7A OR A.3/7D OR A3A/84) THEN m ELSE n/a – – the P-Access-Network-Info header extension and AS acting as terminating UA, AS acting as third-party call controller or EATF.

c7: IF A.4/36 THEN o ELSE n/a – – the P-Charging-Vector header extension.

c8: IF A.4/36 THEN m ELSE n/a – – the P-Charging-Vector header extension.

c9: IF A.4/35 THEN o ELSE n/a – – the P-Charging-Function-Addresses header extension.

c10: IF A.4/35 THEN m ELSE n/a – – the P-Charging-Function-Addresses header extension.

c11: IF A.6/18 THEN m ELSE o – – 405 (Method Not Allowed)

c12: IF A.4/6 THEN o ELSE n/a – – timestamping of requests.

c13: IF A.4/60 THEN m ELSE n/a – – SIP location conveyance.

c16: IF A.4/13 THEN m ELSE IF A.4/13A THEN m ELSE n/a – – SIP INFO method and package framework, legacy INFO usage.

c17: IF A.4/91 THEN m ELSE n/a – – the Session-ID header.

c18: IF A.4/111 THEN m ELSE n/a – – the Relayed-Charge header field extension.

c19: IF A.4/113 AND A.3/1 THEN m ELSE n/a – – the Cellular-Network-Info header extension and UE.

c20: IF A.4/113 AND (A.3/7A OR A.3/7D OR A3A/84) THEN m ELSE n/a – – the Cellular-Network-Info header extension and AS acting as terminating UA or AS acting as third-party call controller or EATF.

c21: IF A.4/119 THEN o ELSE n/a – – Content-ID header field in Session Initiation Protocol (SIP).

c22: IF A.4/119 THEN m ELSE n/a – – Content-ID header field in Session Initiation Protocol (SIP).

NOTE: For a 488 (Not Acceptable Here) response, RFC 3261 [26] gives the status of this header field as SHOULD rather than OPTIONAL.

Prerequisite A.5/23 – – UPDATE response

Prerequisite: A.6/102 – – Additional for 2xx response

Table A.153: Supported header fields within the UPDATE response

Item

Header field

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

0A

Accept

[26] 20.1

o

o

[26] 20.1

m

m

0B

Accept-Encoding

[26] 20.2

o

o

[26] 20.2

m

m

0C

Accept-Language

[26] 20.3

o

o

[26] 20.3

m

m

0D

Accept-Resource-Priority

[116] 3.2

c14

c14

[116] 3.2

c14

c14

1

Allow-Events

[28] 8.2.2

c4

c4

[28] 8.2.2

c5

c5

2

Authentication-Info

[26] 20.6

c1

c1

[26] 20.6

c2

c2

3

Contact

[26] 20.10

m

m

[26] 20.10

m

m

3A

Feature-Caps

[190]

c16

c16

[190]

c16

c16

3B

P-Early-Media

[109] 8

c6

c6

[109] 8

c6

c6

3C

Priority-Share

Subclause 7.2.16

n/a

c18

Subclause 7.2.16

n/a

c18

3E

Resource-Share

Subclause 7.2.13

n/a

c17

Subclause 7.2.13

n/a

c17

4

Session-Expires

[58]

c3

c3

[58]

c3

c3

6

Supported

[26] 20.37

m

m

[26] 20.37

m

m

c1: IF A.4/7 THEN o ELSE n/a – – authentication between UA and UA.

c2: IF A.4/7 THEN m ELSE n/a – – authentication between UA and UA.

c3: IF A.4/42 THEN m ELSE n/a – – the SIP session timer

c4: IF A.4/22 THEN o ELSE n/a – – acting as the notifier of event information.

c5: IF A.4/23 THEN m ELSE n/a – – acting as the subscriber to event information.

c6: IF A.4/66 THEN m ELSE n/a – – the SIP P-Early-Media private header extension for authorization of early media.

c14: IF A.4/70 THEN m ELSE n/a – – communications resource priority for the session initiation protocol.

c16: IF A.4/100 THEN m ELSE n/a – – indication of features supported by proxy.

c17: IF A.4/112 THEN o ELSE n/a – – resource sharing.

c18: IF A.4/114 THEN o ELSE n/a – – priority sharing.

Prerequisite A.5/23 – – UPDATE response

Prerequisite: A.6/103 OR A.6/104 OR A.6/105 OR A.6/106 – – Additional for 3xx – 6xx response

Table A.153A: Supported header fields within the UPDATE response

Item

Header field

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

1

Error-Info

[26] 20.18

o

o

[26] 20.18

o

o

2

Response-Source

7.2.17

n/a

c1

7.2.17

n/a

c1

c1: IF A.4/115 THEN o ELSE n/a – – use of the Response-Source header field in SIP error responses?

Prerequisite A.5/23 – – UPDATE response

Prerequisite: A.6/103 OR A.6/35 – – Additional for 3xx, 485 (Ambiguous) response

Table A.154: Supported header fields within the UPDATE response

Item

Header field

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

2

Contact

[26] 20.10

o

o

[26] 20.10

o

o

Prerequisite A.5/23 – – UPDATE response

Prerequisite: A.6/14 – – Additional for 401 (Unauthorized) response

Table A.154A: Supported header fields within the UPDATE response

Item

Header field

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

3

Proxy-Authenticate

[26] 20.27

c1

c1

[26] 20.27

c1

c1

6

WWW-Authenticate

[26] 20.44

m

m

[26] 20.44

m

m

c1: IF A.4/7 THEN m ELSE n/a – – support of authentication between UA and UA.

Prerequisite A.5/23 – – UPDATE response

Prerequisite: A.6/17 OR A.6/23 OR A.6/30 OR A.6/36 OR A.6/42 OR A.6/45 OR A.6/50 OR A.6/51 – – Additional for 404 (Not Found), 413 (Request Entity Too Large), 480(Temporarily not available), 486 (Busy Here), 500 (Internal Server Error), 503 (Service Unavailable), 600 (Busy Everywhere), 603 (Decline) response

Table A.155: Supported header fields within the UPDATE response

Item

Header field

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

5

Retry-After

[26] 20.33

o

o

[26] 20.33

o

o

Table A.156: Void

Prerequisite A.5/23 – – UPDATE response

Prerequisite: A.6/20 – – Additional for 407 (Proxy Authentication Required) response

Table A.157: Supported header fields within the UPDATE response

Item

Header field

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

4

Proxy-Authenticate

[26] 20.27

c1

c1

[26] 20.27

c1

c1

8

WWW-Authenticate

[26] 20.44

o

o

[26] 20.44

o

o

c1: IF A.4/7 THEN m ELSE n/a – – support of authentication between UA and UA.

Prerequisite A.5/23 – – UPDATE response

Prerequisite: A.6/25 – – Additional for 415 (Unsupported Media Type) response

Table A.158: Supported header fields within the UPDATE response

Item

Header field

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

1

Accept

[26] 20.1

o.1

o.1

[26] 20.1

m

m

2

Accept-Encoding

[26] 20.2

o.1

o.1

[26] 20.2

m

m

3

Accept-Language

[26] 20.3

o.1

o.1

[26] 20.3

m

m

o.1 At least one of these capabilities is supported.

Prerequisite A.5/23 – – UPDATE response

Prerequisite: A.6/26A – – Additional for 417 (Unknown Resource-Priority) response

Table A.158A: Supported header fields within the UPDATE response

Item

Header field

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

1

Accept-Resource-Priority

[116] 3.2

c1

c1

[116] 3.2

c1

c1

c1: IF A.4/70 THEN m ELSE n/a – – communications resource priority for the session initiation protocol.

Prerequisite A.5/23 – – UPDATE response

Prerequisite: A.6/27 – – Additional for 420 (Bad Extension) response

Table A.159: Supported header fields within the UPDATE response

Item

Header field

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

7

Unsupported

[26] 20.40

m

m

[26] 20.40

m

m

Prerequisite A.5/23 – – UPDATE response

Prerequisite: A.6/28 OR A.6/41A – – Additional for 421 (Extension Required), 494 (Security Agreement Required) response

Table A.159A: Supported header fields within the UPDATE response

Item

Header field

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

3

Security-Server

[48] 2

x

x

[48] 2

c1

c1

c1: IF A.4/37 THEN m ELSE n/a – – security mechanism agreement for the session initiation protocol.

Prerequisite A.5/23 – – UPDATE response

Prerequisite: A.6/28A – – Additional for 422 (Session Interval Too Small) response

Table A.159B: Supported header fields within the UPDATE response

Item

Header field

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

1

Min-SE

[58] 5

c1

c1

[58] 5

c1

c1

c1: IF A.4/42 THEN m ELSE n/a – – the SIP session timer.

Table A.160: Void

Prerequisite A.5/23 – – UPDATE response

Table A.161: Supported message bodies within the UPDATE response

Item

Header

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

1