|
| 23.981 | 0006 | 1 | F | 6.3.0 | Rel-6 | P-CSCF address format when configured via DM |
S2-052336
| agreed | SA2#48 | |
SP-050476
| approved | SA#29 | Orange | 6.4.0 | IMS2 |
|
|
| 23.981 | 0006 | - | F | 6.3.0 | Rel-6 | P-CSCF address format when configured via DM |
S2-052183
| revised | SA2#48 | |
| | | Orange | | IMS2 |
|
|
| 23.981 | 0005 | 1 | F | 6.2.0 | Rel-6 | P-CSCF discovery |
S2-050395
| agreed | SA2#44 | |
SP-050115
| approved | SA#27 | Ericsson | 6.3.0 | |
|
|
| 23.981 | 0005 | - | F | 6.0.0 | Rel-6 | P-CSCF discovery |
S2-050284
| revised | SA2#44 | |
| | | Ericsson | | |
|
|
| 23.981 | 0004 | 1 | F | 6.1.0 | Rel-6 | Clarification to the Interworking support in dual stack IM CN subsystem |
S2-043315
| agreed | SA2#42 | |
SP-040761
| approved | SA#26 | Huawei, China Mobile | 6.2.0 | |
|
|
| 23.981 | 0004 | - | F | 6.1.0 | Rel-6 | Clarification to the Interworking support in dual stack IM CN subsystem |
S2-043215
| revised | SA2#42 | |
| | | Huawei, China Mobile | | |
|
|
| 23.981 | 0003 | 1 | F | 6.0.0 | Rel-6 | Corrections to scenario – IPv4 visited and IPv6 home |
S2-042889
| agreed | SA2#41 | |
SP-040530
| approved | SA#25 | S2 | 6.1.0 | IPv4IMS |
|
|
| 23.981 | 0003 | - | F | 6.0.0 | Rel-6 | Corrections to scenario – IPv4 visited and IPv6 home |
S2-042736
| revised | SA2#41 | |
| | | S2 | | IPv4IMS |
|
|
| 23.981 | 0002 | 1 | B | 6.0.0 | Rel-5 | Creating a Rel-5 version of TR 23.981 |
S2-042890
| agreed | SA2#41 | |
SP-040530
| approved | SA#25 | S2 | 5.0.0 | IPv4IMS |
|
|
| 23.981 | 0002 | - | B | 6.0.0 | Rel-5 | Creating a Rel-5 version of TR 23.981 |
S2-042694
| revised | SA2#41 | |
| | | S2 | | IPv4IMS |
|
|
| 23.981 | 0001 | - | F | 6.0.0 | Rel-6 | IPv4 access to multimedia services and Mb reference point |
S2-042683
| agreed | SA2#41 | |
SP-040530
| approved | SA#25 | S2 | 6.1.0 | IPv4IMS |
|