Questions 1, 2, 3, 5, 21/16 (WP1/16)
Report Documents
|
File |
Q |
Title |
Source |
|
All |
Report of WP1/16 |
WP1 Chair |
|
|
All |
Outgoing liaison statements produced by WP1/16 |
WP1 Chair |
Output Documents
|
File |
Q |
Title |
Source |
|
2 |
End-to-end session identifier for H.323 systems |
Editor |
|
|
3 |
Gateway control protocol: IP domain connection package |
Editor |
|
|
3 |
Gateway control protocol: NAT traversal toolkit packages |
Editor |
|
|
3 |
Packages for RTSP and H.248 interworking |
Editor |
|
|
3 |
Media resource control enhancement packages |
Editor |
|
|
3 |
Gateway control protocol: Secure real-time transport protocol (SRTP) package and procedures |
Editor |
|
|
3 |
Gateway control protocol: Bearer-level message backhauling and application level gateway |
Editor |
|
|
3 |
Gateway control protocol: Web-based real-time communication services - H.248 protocol support and profile guidelines |
Editor |
|
|
3 |
Gateway Control Protocol: H.248 support for RTP multiplexing |
Editor |
|
|
3 |
Gateway Control Protocol: H.248 Stream grouping and aggregation |
Editor |
|
|
3 |
Gateway control protocol: H.248 support for control of SCTP bearer connections |
Editor |
|
|
3 |
Gateway control protocol: Support of remote media pause and resume |
Editor |
|
|
3 |
Gateway control protocol: Cloudification of packet gateways |
Editor |
|
|
3 |
Gateway control protocol: Profiling codec configurations via SDP in H.248 profiles – Guidelines and examples |
Editor |
|
|
3 |
H.248 Sub-series Implementors’ Guide |
Editor |
|
|
3 |
Gateway control protocol: H.248 support for traffic shaping |
Editor |
|
|
3 |
Gateway control protocol: Profile guidelines for H.248 supported SIP-based Media Recording |
Editor |
|
|
3 |
H.248.x sub-series packages guide – Release 16 |
Editor |
|
|
3 |
Gateway control protocol: Common ITU-T H.248 terminology – Release 2 |
Editor |
|
|
3 |
Gateway Control Protocol: Alternate IP connectivity support by H.248 gateway control protocol |
Editor |
|
|
3 |
Gateway Control Protocol: Protocol evaluation of OpenFlow versus ITU-T H.248 |
Editor |