1

Roaming II-NNI support

entire present specification

Yes

Option items in clauses C.3.1 and C.3.2.

Applicability of "Roaming Architecture for Voice over IMS with Local Breakout" (Clause 19).

If "Roaming Architecture for Voice over IMS with Local Breakout" is applicable:

+ option items in clause C.3.3; and

+ the default TRF address to use when not included in the "g.3gpp.trf" feature-capability indicator.

No

2

Non-roaming II-NNI support

entire present specification

Yes

Option items in clauses C.3.1 and C.3.3.

No

1

INFO method

table 6.1/5A

table 6.1/5B

Yes

Info package name to use.

No

2

MESSAGE method

table 6.1/9A

table 6.1/9B

Yes

Inside or outside existing dialog, and content of MESSAGE request.

No

3

REFER method

table 6.1/16

table 6.1/17

Yes

Inside or outside existing dialog.

No

1

SIP overload control

table 6.1.3.1/106

clause 21.1

Yes

Mechanisms to be used.

Whether to exempt MPS from SIP overload controls.

No

2

Feedback control

table 6.1.3.1/107

clause 21.2

Yes

Algorithm to be used if not default (see clause 21.2).

No

3

Event control

table 6.1.3.1/108

clause 21.3

Yes

Addresses to targets that can be supervised.

No

1

Negotiation of resource reservation

(precondition)

table 6.1.3.1/20

Yes

No

1

SIP session timer

(timer)

table 6.1.3.1/45

Yes

Use conditions (Possible restriction on range of times and whether SIP session timer is applied in all sessions).

1

Replacing of SIP dialogs

(replaces)

table 6.1.3.1/47

Yes

No

1

Session participation

(join)

table 6.1.3.1/48

Yes

No

1

Conveying capabilities of UE

table 6.1.3.1/49

Yes

No

1

Authorization of early media

table 6.1.3.1/69

Yes

Whether to use authorization request of early media generated by the entity outside the IMS network.

No

1

Managing the indication of the asserted service

(P-Asserted-Service header field)

table 6.1.3.1/77

Yes

Service identifier values to use.

No

1

Overlap signalling

In-dialog method

clause 6.1.1.5

Yes

No

Multiple-INVITE method

Yes

No

1

MIME type

clause 6.1.4

Yes

MIME types to use.

Applicable characteristics of the SIP message body MIMEs (i.e. the value(s) of Content-Disposition header field and Content-Language header field) if necessary.

1

Limitation on maximum length of a SIP message body

clause 6.1.4

Yes

Maximum length accepted.

No

1

TCP

clause 6.2

Yes

Use conditions (e.g. port number to accept, number of simultaneous connections in case of reuse of the existing connections).

No

2

UDP

clause 6.2

Yes

Use conditions (e.g. port number to accept).

No

3

SCTP

clause 6.2

Yes

Use conditions (e.g. port number to accept).

No

1

Speech media (m=audio)

clause 7.1

Yes

Names of speech codecs to use. (NOTE 1, NOTE 2)

2

Video media (m=video)

clause 7.1

Yes

Names of video codecs to use. (NOTE 1, NOTE 2)

No

3

Other media

clause 7.1

Yes

Media type (m=line of SDP) to use (e.g. application, image, message).

No

4

RTP/AVPF

clause 7.2

Yes

Media type (m=line of SDP) that uses the protocol.

No

5

Transmission Control Protocol

clause 6.1.2.1

clause 7.2

Yes

Media type (m=line of SDP) that uses the protocol.

No

6

Other user plane protocols

clause 7.2

Yes

Protocols to use (e.g. udptl, TCP/MSRP) and media types (m=line of SDP) that describe the protocols.

No

NOTE 1: Codecs which are included in the applicable codec list made by inter-operator agreements are guaranteed to be supported at the II-NNI by the peer operators.

NOTE 2: Whether it is allowed to offer codecs which are not included in the applicable codec list made by inter-operator agreements over the II-NNI is also determined by the inter-operator agreement if necessary.

1

DTMF transport

"telephone-event" based DTMF transport

clause 7.1

table 6.1/5A

table 6.1/5B

clause 12.14

clause 12.15

Yes

Sampling rate to use.

No

The SIP INFO mechanism

Yes

No

1

IPv4

clause 9

Yes

Use conditions (e.g. for control plane, for user plane).

No

2

IPv6

clause 9

Yes

Use conditions (e.g. for control plane, for user plane).

No

1

Malicious Communication IDentification (MCID)

clause 12.2

Yes

Minimum information exchanged over the II-NNI.

No

2

Originating Identification Presentation (OIP) and Originating Identification Restriction (OIR)

clause 12.3

Yes

No

3

Terminating Identification Presentation (TIP) and Terminating Identification Restriction (TIR)

clause 12.4

Yes

No

4

Anonymous Communication Rejection (ACR)

clause 12.5

Yes

No

5

Communication DIVersion (CDIV)

clause 12.6

Yes

No

6

Communication Waiting (CW)

clause 12.7

Yes

No

7

Communication HOLD (HOLD)

clause 12.8

Yes

No

8

Message Waiting Indication (MWI)

clause 12.9

Yes

No

9

Incoming Communication Barring (ICB)

clause 12.10.1

Yes

No

10

Completion of Communications to Busy Subscriber (CCBS)

clause 12.11

Yes

No

11

Completion of Communications by No Reply (CCNR)

clause 12.12

Yes

No

12

Explicit Communication Transfer (ECT)

clause 12.13

Yes

Type of explicit communication transfer to support.

No

13

Customized Alerting Tone (CAT)

clause 12.14

Yes

CAT model to use (Gateway model, forking model and early session model).

Media type (m=line of SDP) applicable to CAT.

No

14

Customized Ringing Signal (CRS)

clause 12.15

Yes

No

15

Closed User Group (CUG)

clause 12.16

Yes

No

16

Personal Network Management (PNM)

clause 12.17

Yes

No

17

Three-Party (3PTY)

clause 12.18

Yes

No

18

Conference (CONF)

clause 12.19

Yes

No

19

Flexible Alerting (FA)

clause 12.20

Yes

No

20

Announcements

During the establishment of a session

clause 12.21.2

Yes

Methods for sending announcement.

No

During an established communication session

clause 12.21.3

Yes

Methods for sending announcement.

No

Providing announcements when communication request is rejected

clause 12.21.4

Yes

Methods for sending announcement.

No

21

Advice Of Charge (AOC)

clause 12.22

Yes

No

22

Completion of Communications on Not Logged-in (CCNL)

clause 12.23

Yes

No

23

Presence service

clause 15

Yes

Presence services to use (TS 24.141 [132], OMA 1.1 [142] or OMA 2.0 [138]).

No

24

Messaging service

Page-mode messaging

clause 16.2

Yes

No

Session-mode messaging

clause 16.4

Yes

No

Session-mode messaging conferences

clause 16.5

Yes

No

24A

Delivery of original destination identity

clause 22

Yes

Services to apply the function.

No

24B

Service access number translation

table 6.1.3.1/52A

clause 27

Yes

No

25

Other additional service using other SIP extensions

clause 6.1.1.3.2

clause 12.6

Yes

The SIP extensions to use and the service that uses the extensions.

No

26

Multi-Identity (MiD)

clause 6.1.1.3.1

table 6.1.3.1/126

clause 12.26.2

Yes

Types of non-native identities to support. (NOTE)

No

NOTE: The non-native identities, as defined in 3GPP TS 24.174 [218] are:
an alternative identity, an external alternative identity and a virtual identity.

1

Optimal Media Routeing

clause 17

Yes

No

2

Applying forking (NOTE 1)

table 6.1.3.1/5

Yes

Usage of Request-Disposition header field with value "no-fork". (NOTE 3)

No

(NOTE 2)

3

Transfer of IP multimedia service tariff information

clause 11.3

Yes

The value of the Content-Disposition header field.

No

4

Telepresence using IMS

clause 23

Yes

The value of "+sip.clue" media feature tag in Contact header field.

No

5

Dynamic services interactions

table 6.1.3.1/125

Yes

The identities of the services in the Service-Interact-Info header field.

No

6

MTSI Data channel

clause 33

Yes

The value "webrtc-datachannel" of "+sip.app-subtype" media feature tag in Contact header field.

No

NOTE 1: Support of handling of several responses due to forking and of the Request-Disposition header field, is mandated on the II-NNI.

NOTE 2: In case the operator interconnects with IMS non-compliant networks, and wishes to use the II-NNI anyway, then the operators might want to negotiate if the forking procedures are applicable.

NOTE 3: The Request-Disposition header field with value "no-fork" can be used to suppress that forking occurs. However, a peer operator might require the usage of forking e.g. to implement certain services.

2

b=line

clause 6.1.2

Yes

Used bandwidth modifier types.

3

a=line

clause 6.1.2

Yes

Used attributes.

For the "rtpmap" attribute, used "encoding names".

1

Support of the "iotl" SIP URI parameter indicating the II-NNI traversal scenario

table 6.1.3.1/112

clause 5.3

Yes

No

1

Support of Mission critical services

clause 28.2.2

Yes

MBMS transmission usage and location procedures support.

No

1

Calling number verification using signature verification and attestation information

table 6.1.3.1/119

table 6.1.3.1/120

table 6.1.3.1/123

table 6.1.3.1/124

clause 29

Yes

No

1

Calling number verification using signature verification and attestation information

table 6.1.3.1/119

table 6.1.3.1/120

table 6.1.3.1/123

table 6.1.3.1/124

clause 34.2

Yes

Support for emergency, emergency callback and/or priority IMS sessions.

No

2

Priority verification using assertion of priority information

table 6.1.3.1/73

table 6.1.3.1/110

table 6.1.3.1/119

table 6.1.3.1/128

clause 34.3

Yes

Support for emergency, emergency callback and/or priority IMS sessions.

No

1

IMS AKA plus Ipsec ESP

table 6.1.3.1/7

Yes

No

2

SIP digest plus check of IP association

table 6.1.3.1/7

Yes

No

3

SIP digest plus Proxy Authentication

table 6.1.3.1/7

Yes

No

4

SIP digest with TLS

table 6.1.3.1/7

Yes

No

1

Inter-operator accounting

table 6.1.3.1/38

clause 11.2

Yes

Operator network identifiers populated in the type 1 "orig-ioi" and "term-ioi" header field parameters of the P-Charging-Vector header field.

2

Inter-operator accounting for the transit scenario

clause 11.2

Yes

Operator network identifiers populated in the "transit-ioi" header field parameters of the P-Charging-Vector header field.

No

1

The key of service profile for HSS query (P-Profile-Key header field)

table 6.1.3.1/59

Yes

No

1

Dial string

("user=dialstring" SIP URI parameter)

table 6.1.3.1/67

Yes

No

2

Barring of premium numbers ("premium-rate" tel URI parameter)

clause 8.1,

clause 24

Yes

No

2

Unstructured Supplementary Service Data

clause 12.24

Yes

No

3

Enhanced Calling Name

clause 12.25

Yes

No

1

IMS Centralized Services (ICS)

clause 13

Yes

No

2

PS to CS Single Radio Voice Call Continuity (SRVCC)

clause 14

Yes

Additional use conditions (PS to CS SRVCC for calls in alerting phase, support of ATCF architecture, PS to CS SRVCC for calls in pre-alerting phase and PS to CS SRVCC with the MSC server assisted mid-call feature).

If the ATCF architecture applies, the URIs of SCC ASs authorised to provide PS to CS SRVCC information in the MESSAGE request.

No

3

Single Radio Video Call Continuity (vSRVCC)

clause 14

Yes

Additional use condition (transfer in alerting phase).

No

4

Inter UE Transfer (IUT)

clause 18

Yes

No

5

CS to PS Single Radio Voice Call Continuity (SRVCC)

clause 14.5

Yes

The URIs of SCC ASs authorised to provide CS to PS SRVCC information in the MESSAGE request.

Additional use conditions (support of CS to PS SRVCC for calls in alerting phase and support of CS to PS SRVCC with the assisted mid-call feature).

No

6

PS to CS Dual Radio Voice Call Continuity (DRVCC)

clause 14.6

Yes

Additional use conditions (PS to CS DRVCC for calls in alerting phase, PS to CS DRVCC for originating calls in pre-alerting phase, PS to CS DRVCC with the MSC server assisted mid-call feature and the use of IMS Centralized Services (ICS) and the tel URI in STN).

No

7

CS to PS Dual Radio Voice Call Continuity (DRVCC)

clause 14.7

Yes

Additional use conditions (CS to PS DRVCC for calls in alerting phase, CS to PS DRVCC for originating calls in pre-alerting phase, CS to PS DRVCC with the MSC server assisted mid-call feature) and the use of IMS Centralized Services (ICS).

No

1

Registration of bulk number contacts

table 6.1.3.1/104

Yes

No

2

HSS or UDM/HSS based P-CSCF restoration

clause 25.3

Yes

No

1

NOTIFY method

table 6.1/10

table 6.1/11

Yes

Event package name to use.

No

2

SUBSCRIBE method

table 6.1/20

table 6.1/21

Yes

Event package name to use.

No

3

PUBLISH method

table 6.1/15A

table 6.1/15B

Yes

Event package name to use.

No

1

Inter-operator accounting

table 6.1.3.1/38

clause 11.2

Yes

Operator network identifiers populated in the type 2 "orig-ioi" and "term-ioi" header field parameters of the P-Charging-Vector header field.

No

2

Inter-operator accounting for the transit scenario

clause 11.2

Yes

Operator network identifiers populated in the "transit-ioi" header field parameters of the P-Charging-Vector header field.

No

1

Globally Routable User Agent URIs

(gruu)

table 6.1.3.1/56

Yes

No

1

Media feature tags

table 6.1.3.1/76

clause 12

clause 13

clause 14

clause 16

clause 18

Yes

Names of media feature tags to use.

No

1

User to User Call Control Information in SIP for ISDN Interworking (uui)

table 6.1.3.1/79

Yes

No

1

Private network traffic

(P-Private-Network-Indication header field)

table 6.1.3.1/80

Yes

No

1

Number Portability Routing Number

("rn" and "npdi" tel URI parameters)

clause 8.1

Yes

No

2

Calling Party’s Category

("cpc" tel URI parameter)

clause 8.1

Yes

cpc-values to use.

No

3

Originating Line Information

("oli" tel URI parameter)

clause 8.1

Yes

oli-values to use.

No

NOTE: The option item is only for the non-roaming II-NNI.

1

Support of out-of-dialog OPTIONS method

table 6.1/12

table 6.1/13

Yes

The purpose of the method.

No

1

IMS emergency session traversal scenario

table 6.1.3.1/55

clause 30.1

clause 30.2

Yes

The emergency service URN(s) to use.

The PSAP URI to use in the Route header field, if applicable.

No

2

Next-Generation Pan-European eCall emergency service

clause 30.3

Yes

No

Date

TSG #

TSG Doc.

CR

Rev

Subject/Comment

Old

New

03/2015

CT-67

CP-150129

736

1

Addition of an optional capability regarding a new cause-param value for service number translation

12.7.0

13.0.0

03/2015

CT-67

CP-150130

719

Correction of a minor error in subclause C.3.1

12.7.0

13.0.0

03/2015

CT-67

CP-150130

723

Annex A corrections

12.7.0

13.0.0

03/2015

CT-67

CP-150130

726

3

Applying drafting rules

12.7.0

13.0.0

03/2015

CT-67

CP-150130

729

1

Adding missing abbreviations

12.7.0

13.0.0

06/2015

CT-68

CP-150339

0741

–

Reference Update: RFC 7462 (alert-info urns)

13.0.0

13.1.0

06/2015

CT-68

CP-150341

0746

–

Condition on usage of Refer-Sub header field

13.0.0

13.1.0

06/2015

CT-68

CP-150356

0747

3

Introducing resource sharing

13.0.0

13.1.0

06/2015

CT-68

CP-150346

0749

1

Correcting errors in annex B

13.0.0

13.1.0

06/2015

CT-68

CP-150347

0751

–

draft-holmberg-dispatch-iotl-parameter-04 updated to RFC 7549

13.0.0

13.1.0

06/2015

CT-68

CP-150350

0753

1

Additional RFC 6665 related IETF drafts added

13.0.0

13.1.0

06/2015

CT-68

CP-150357

0754

1

Correcting inconsistencies in the major capability table

13.0.0

13.1.0

06/2015

CT-68

CP-150364

0756

1

Correction of Record-Route header field applicability in annex B

13.0.0

13.1.0

06/2015

CT-68

CP-150364

0758

–

Correction of applicable SIP status code for SIP header fields in PUBLISH response in annex B

13.0.0

13.1.0

06/2015

CT-68

CP-150364

0760

–

Addition of missing text referring to an option item table in annex C

13.0.0

13.1.0

06/2015

CT-68

CP-150364

0762

1

Correction of the P-Charging-Vector header field in annex B

13.0.0

13.1.0

06/2015

CT-68

CP-150364

0763

1

Correction of the P-Early-Media header field within the PRACK response in annex B

13.0.0

13.1.0

06/2015

CT-68

CP-150364

0765

–

Correction of the Server header field within the SUBSCRIBE response in annex B

13.0.0

13.1.0

06/2015

CT-68

CP-150364

0766

–

Correction of the Allow header field in annex B

13.0.0

13.1.0

06/2015

CT-68

CP-150364

0767

–

Clarifications on NNI impacts due to CAT service

13.0.0

13.1.0

06/2015

–

–

–

–

MCC Correction of implementation of CR0765

13.1.0

13.1.1

09/2015

CT-69

CP-150486

0768

3

The privacy level "session" and "critical" are not used in OIP/OIR

13.1.1

13.2.0

09/2015

CT-69

CP-150479

0769

1

Service access number translation

13.1.1

13.2.0

09/2015

CT-69

CP-150471

0771

1

Reference update: draft-ietf-mmusic-sctp-sdp

13.1.1

13.2.0

09/2015

CT-69

CP-150475

0773

–

Missing SIP request in HSS based P-CSCF restoration

13.1.1

13.2.0

09/2015

CT-69

CP-150479

0774

–

draft-mohali-dispatch-cause-for-service-number updated to latest version

13.1.1

13.2.0

09/2015

CT-69

CP-150486

0775

1

The Service-Interact-Info header field

13.1.1

13.2.0

09/2015

CT-69

CP-150478

0776

1

Plain text message body missing in table 6.1.4.1

13.1.1

13.2.0

09/2015

CT-69

CP-150478

0777

1

application/x-www-form-url encoded missing in table 6.1.4.1

13.1.1

13.2.0

09/2015

CT-69

CP-150486

0778

1

application/vnd.3gpp.crs+xml MIME body missing in CRS

13.1.1

13.2.0

09/2015

CT-69

CP-150478

0779

–

message/sip MIME body missing in table 6.1.4.1

13.1.1

13.2.0

09/2015

CT-69

CP-150478

0780

–

Applicability of SIP header fields on a roaming II-NNI

13.1.1

13.2.0

09/2015

CT-69

CP-150469

0783

–

Reference update: RFC 7415

13.1.1

13.2.0

09/2015

CT-69

CP-150465

0787

1

Correction for the II-NNI conditions

13.1.1

13.2.0

12/2015

CT-70

CP-150796

0790

2

Clarification on the II-NNI specifications of announcement

13.2.0

13.3.0

12/2015

CT-70

CP-150796

0791

2

Updating for annex B

13.2.0

13.3.0

12/2015

CT-70

CP-150654

0795

–

Telepresence IETF draft update

13.2.0

13.3.0

12/2015

CT-70

CP-150659

0796

3

Introducing MCPTT

13.2.0

13.3.0

12/2015

CT-70

CP-150657

0797

2

Reference update of draft-mohali-dispatch-cause-for-service-number

13.2.0

13.3.0

12/2015

CT-70

CP-150664

0800

2

Adding the "loopback-indication" to RAVEL

13.2.0

13.3.0

12/2015

CT-70

CP-150731

0804

1

ICS and the conference service

13.2.0

13.3.0

12/2015

CT-70

CP-150660

0805

–

SRVCC and subscription to conference package

13.2.0

13.3.0

12/2015

CT-70

CP-150660

0806

1

ICS and subscription to conference package

13.2.0

13.3.0

12/2015

CT-70

CP-150656

0807

1

Clarification of applicable URI formats for public user identity

13.2.0

13.3.0

12/2015

CT-70

CP-150796

0808

–

Miscellaneous editorial modification

13.2.0

13.3.0

12/2015

CT-70

CP-150671

0810

1

Update of UP6665 references

13.2.0

13.3.0

12/2015

CT-70

CP-150662

0812

1

P-CSCF restoration corrections

13.2.0

13.3.0

Date

TSG #

TSG Doc.

CR

Rev

Cat

Subject/Comment

New

2016-03

CT#71

CP-160088

0813

2

B

Adding MBMS usage info and location info procedure

13.4.0

2016-03

CT#71

CP-160088

0814

2

F

Adding "application/vnd.3gpp.mcptt-info" MIME body

13.4.0

2016-03

CT#71

CP-160088

0815

2

B

Adding MCPTT as option item in annex C

13.4.0

2016-03

CT#71

CP-160088

0816

1

B

Adding affiliation

13.4.0

2016-03

CT#71

CP-160098

0817

1

F

Adding "Timer N" in the timer table

13.4.0

2016-03

CT#71

CP-160096

0819

1

A

Updating "Details for operator choice" in DRVCC to include the STN

13.4.0

2016-03

CT#71

CP-160088

0821

1

F

Addressed MCPTT SIP interfaces

13.4.0

2016-06

CT#72

CP-160262

0822

2

F

Some error corrections and removing an editor’s note

13.5.0

2016-06

CT#72

CP-160262

0823

2

F

Group regrouping

13.5.0

2016-06

CT#72

CP-160262

0824

1

F

Conference event package subscription

13.5.0

2016-06

CT#72

CP-160262

0825

1

F

MCPTT service settings

13.5.0

2016-06

CT#72

CP-160262

0826

–

F

Clarifying the Accept-Contact header field in MBMS usage info

13.5.0

2016-06

CT#72

CP-160262

0827

2

F

The affiliation procedure update

13.5.0

2016-06

CT#72

CP-160259

0828

1

F

Adding the Cellular-Network-Info header field

13.5.0

2016-06

CT#72

CP-160258

0834

1

A

Adding draft-mohali-dispatch-originating-cdiv-parameter

13.5.0

2016-06

CT#72

CP-160258

0840

1

A

Updates to RFC 7315 P-header extensions usage in SIP requests/responses

13.5.0

2016-06

CT#72

CP-160258

0843

1

A

P-Access-Network-Info ABNF Update

13.5.0

2016-06

CT#72

CP-160261

0844

1

F

Update ref to draft-mohali-dispatch-cause-for-service-number-06

13.5.0

2016-06

CT#72

CP-160273

0830

1

F

Clarification of the note about forking

14.0.0

2016-06

CT#72

CP-160273

0831

–

F

Changing content type to correct terminology

14.0.0

2016-06

CT#72

CP-160273

0835

1

F

Clarification of Public Service Identitiy at II-NNI

14.0.0

2016-06

CT#72

CP-160273

0836

1

F

Correcting the subscription to the conference package for CONF and the session-mode messaging service

14.0.0

2016-06

CT#72

CP-160273

0837

1

F

Clarification on the applicability of P-Early-Media header field and early media over the II-NNI

14.0.0

2016-09

CT#73

CP-160446

0846

1

A

Usage of the Resource-Share header field

14.1.0

2016-09

CT#73

CP-160447

0852

1

A

Reference update: RFC 7913

14.1.0

2016-09

CT#73

CP-160449

0855

1

A

Updated ref to draft-mohali-dispatch-cause-for-service-number-07

14.1.0

2016-12

CT#74

CP-160624

0857

1

A

Updated ref to draft-mohali-dispatch-cause-for-service-number-09

14.2.0

2016-12

CT#74

CP-160620

0861

1

A

Updated ref to draft-mohali-dispatch-originating-cdiv-parameter-02

14.2.0

2016-12

CT#74

CP-160620

0865

–

A

Reference update: RFC 7976

14.2.0

2016-12

CT#74

CP-160621

0875

–

A

Reference update: RFC 7989

14.2.0

2016-12

CT#74

CP-160623

0877

2

A

Missing support of priority sharing

14.2.0

2016-12

CT#74

CP-160631

0878

–

F

Additional routeing functionality at the IBCF

14.2.0

2017-03

CT#75

CP-170087

0882

1

A

Correction on PSAP callback indicator option item

14.3.0

2017-03

CT#75

CP-170087

0883

1

A

Correction on the architecture diagram of II-NNI

14.3.0

2017-03

CT#75

CP-170087

0884

1

A

Addition of application/call-completion MIME Type

14.3.0

2017-03

CT#75

CP-170080

0886

1

A

Update ref to draft-mohali-dispatch-cause-for-service-number

14.3.0

2017-03

CT#75

CP-170078

0890

2

A

Update ref to draft-mohali-dispatch-originating-cdiv-parameter

14.3.0

2017-03

CT#75

CP-170079

0894

–

A

Reference update: RFC 8055

14.3.0

2017-03

CT#75

CP-170077

0896

–

A

Applicability of Resource-Share header field

14.3.0

2017-03

CT#75

CP-170085

0897

1

B

Support of "Calling number verification"

14.3.0

2017-06

CT#76

CP-171134

0872

5

F

Clarification of II-NNI for IMS emergency session

14.4.0

2017-06

CT#76

CP-171130

0898

2

B

Addition of the location parameter

14.4.0

2017-06

CT#76

CP-171128

0900

–

A

MIME body types used by MCPTT

14.4.0

2017-06

CT#76

CP-171126

0901

–

F

Modifying references to align with rel-14 MCPTT stage 1 and stage 2 restructuring

14.4.0

2017-06

CT#76

CP-171134

0902

1

F

Missing support of Response-Source header field

14.4.0

2017-06

CT#76

CP-171124

0904

1

A

Reference Update RFC8119

14.4.0

2017-06

CT#76

CP-171123

0908

1

A

Update ref to new naming of draft-mohali-sipcore-originating-cdiv-parameter

14.4.0

2017-06

CT#76

CP-171131

0909

2

F

Support of feature capability indicator "sip.607"

14.4.0

2017-06

CT#76

CP-171122

0913

–

A

Reference update: draft-ietf-mmusic-sctp-sdp

14.4.0

2017-06

CT#76

CP-171131

0914

–

F

Reference update: draft-ietf-stir-rfc4474bis

14.4.0

2017-06

CT#76

CP-171125

0915

3

B

IMS Trace (ISAT) Procedures

14.4.0

2017-06

CT#76

CP-171127

0916

3

B

Adding other Mission Critical services

14.4.0

2017-06

CT#76

CP-171135

0910

1

F

Added unspecified abbreviations

15.0.0

2017-06

CT#76

CP-171135

0918

2

F

Misalignment regarding transcoding between TS 24.229 and TS 29.165

15.0.0

2017-06

CT#76

Editorial changes by MCC

15.0.1

2017-09

CT#77

CP-172049

0919

1

A

Added the profile status in proxy role regarding “A SIP Response Code for Unwanted Calls”

15.1.0

2017-09

CT#77

CP-172040

0920

1

B

Support of IETF draft-ietf-sipcore-content-id

15.1.0

2017-09

CT#77

CP-172045

0922

1

A

Reference Update for the ISUP location parameter

15.1.0

2017-09

CT#77

CP-172049

0925

–

A

Reference update from draft-ietf-sipcore-status-unwanted-06 to RFC 8197

15.1.0

2017-12

CT#78

CP-173099

0928

1

A

Reference Update for the ISUP location parameter

15.2.0

2017-12

CT#78

CP-173091

0933

1

A

Update draft ref for Originating-CDIV param in P-Served-User

15.2.0

2017-12

CT#78

CP-173090

0934

–

D

Editorial modification

15.2.0

2017-12

CT#78

CP-173095

0935

1

A

Adding MCData related MIME bodies

15.2.0

2017-12

CT#78

CP-173098

0938

1

A

Correction of II-NNI condition related to P-Early-Media header field

15.2.0

2017-12

CT#78

CP-173102

0940

–

A

Correction of II-NNI condition related to P-Early-Media header field for the UPDATE request

15.2.0

2017-12

CT#78

CP-173096

0943

–

A

Addition of sign XML MIME body

15.2.0

2017-12

CT#78

CP-173092

0945

–

F

Reference update: RFC 8262

15.2.0

2018-03

CT#79

CP-180038

0946

1

B

Support of "Enhanced calling name" service

15.3.0

2018-03

CT#79

CP-180048

0947

–

F

bSRVCC-MT NNI

15.3.0

2018-03

CT#79

CP-180048

0948

1

F

Operator choice of DTMF sampling rate

15.3.0

2018-03

CT#79

CP-180042

0950

–

A

Reference Update for the ISUP location parameter

15.3.0

2018-03

CT#79

CP-180048

0951

–

F

Updating the title of referenced TS 22.179

15.3.0

2018-03

CT#79

CP-180044

0953

–

A

Reference update: RFC 8224

15.3.0

2018-03

CT#79

CP-180048

0955

–

F

Correction on the terminology of non-global number

15.3.0

2018-03

CT#79

CP-180048

0956

–

F

Correction of the option item name for Calling number verification

15.3.0

2018-03

CT#79

CP-180048

0957

1

F

Operator choice of CAT media type

15.3.0

2018-06

CT#80

CP-181022

0958

1

F

Missing explanation of abbreviation "5xx"

15.4.0

2018-06

CT#80

CP-181016

0959

1

B

Calling number verification using signature verification and attestation information

15.4.0

2018-06

CT#80

CP-181170

0960

4

F

MBMS transmission and location procedures for MCVideo service

15.4.0

2018-09

CT#81

CP-182021

0961

1

B

Functional Alias Management over II-NNI

15.5.0

2018-09

CT#81

CP-182020

0966

1

A

Update draft ref for Originating-CDIV param in P-Served-User

15.5.0

2018-09

CT#81

CP-182018

0967

1

F

Correction of NOTE numbering for trust relationship

15.5.0

2018-09

CT#81

CP-182024

0969

–

A

Reference Update for the ISUP Q.850 location parameter

15.5.0

2018-12

CT#82

CP-183113

0974

2

A

Update draft ref for Originating-CDIV param in P-Served-User

15.6.0

2018-12

CT#82

CP-183114

0977

1

A

Removal of editor’s note on Service-Interact-Info

15.6.0

2018-12

CT#82

CP-183111

0978

–

F

Support of Origination-Id in INVITE and MESSAGE methods

15.6.0

2019-03

CT#83

CP-190124

0980

2

A

References update for ISAT after related RFC completed in IETF

15.7.0

2019-03

CT#83

CP-190126

0982

2

A

Reference Update for the ISUP Cause Location Parameter Draft

15.7.0

2019-03

CT#83

CP-190123

0988

1

A

P-Served-User case orig-cdiv is now RFC 8498

15.7.0

2019-06

CT#84

CP-191094

0989

–

A

Reference Update for the ISUP Cause Location Parameter Draft

15.8.0

2019-09

CT#85

CP-192166

0992

1

A

Reference Update RFC8606

15.9.0

2019-09

CT#85

CP-192174

0990

3

F

Clarification of the usage restriction of P-Asserted-Identity header field over the II-NNI.

16.0.0

2019-09

CT#85

CP-192162

0993

1

B

Support of "Multi-Device" and "Multi-Identity" services

16.0.0

2019-12

CT#86

CP-193190

0995

2

A

P-CSCF restoration in 5GS

16.1.0

2019-12

CT#86

CP-193205

0996

B

Additional-Identity header in REFER request

16.1.0

2019-12

CT#86

CP-193207

1004

1

A

Correction for setting condition of the Contact header field

16.1.0

2020-03

CT#87e

CP-200229

1005

2

F

Clarification of the scope

16.2.0

2020-06

CT#88e

CP-201329

1006

F

Corrections on the II-NNI specifications on the P-Charging-Vector header field

16.3.0

2020-06

CT#88e

CP-201240

1007

1

F

Re-structure of subclause for MuD/MiD service

16.3.0

2020-06

CT#88e

CP-201242

1008

1

F

Adding the RLOS requirements over the II-NNI

16.3.0

2020-09

CT#89e

CP-202076

1011

1

A

Addition of missing capability

16.4.0

2020-09

CT#89e

CP-202075

1015

–

A

Support of P-Charging-Vector header field in BYE and PRACK

16.4.0

2020-12

CT#90e

CP-203145

1016

2

F

Adding the description of Ix reference point.

17.0.0

2021-03

CT#91e

CP-210213

1017

1

F

Correction of the dynamic view status for History-Info header field.

17.1.0

2021-03

CT#91e

CP-210242

1023

–

A

Reference update: RFC 8841

17.1.0

2021-06

CT#92e

CP-211236

1024

3

A

IMS data channel at the II-NNI

17.2.0

2021-06

CT#92e

CP-211222

1028

–

A

Correction on Calling number verification using signature verification and attestation information

17.2.0

2021-06

CT#92e

CP-211258

1029

1

B

Support for signed attestation for emergency and priority IMS sessions

17.2.0

2021-09

CT#93e

CP-212227

1030

1

B

IBCF RPH signing for MPS

17.3.0

2022-09

CT#97e

CP-222124

1032

2

F

Support of Reason header for handling of Identity header errors

17.4.0

2022-12

CT#98e

CP-223195

1033

F

Capability alignment: Identity Header Error Handling

17.5.0

2022-12

CT#98e

CP-223195

1034

1

F

Reference update: draft-ietf-stir-identity-header-errors-handling

17.5.0

2022-12

CT#98e

CP-223182

1035

B

Support of IETF draft-ietf-sipcore-multiple-reasons

18.0.0