Subject: [Megaco] [RTP stream pause & resume]: middleboxes (ITU-T H.248.PAURES)

From: "Schwarz, Albrecht (Albrecht)" <[email-masked]>
Date: Wed, 22 Apr 2015 08:35:49 +0000

Hello Christian,

perhaps you noticed already that we've submitted early contributions based on a review and consideration of specific use cases for H.248 IP-to-IP media gateways (besides the obvious primary scenarios for H.248 media servers).

http://wftp3.itu.int/av-arch/avc-site/2013-2016/1506_Che/1506_Che.html

AVD-4695<http://wftp3.itu.int/av-arch/avc-site/2013-2016/1506_Che/AVD-4695.zip>

3

H.248.PAURES: H.248 use cases and design considerations (clauses 1 to 7)

Alcatel-Lucent

AVD-4696<http://wftp3.itu.int/av-arch/avc-site/2013-2016/1506_Che/AVD-4696.zip>

3

H.248.PAURES: Part II - Package review

Alcatel-Lucent

AVD-4697<http://wftp3.itu.int/av-arch/avc-site/2013-2016/1506_Che/AVD-4697.zip>

3

H.248.PAURES: Part III - Possible interactions with RTP topologies

Alcatel-Lucent

Hello Bo & Azam,

when trying to figure out the exact protocol behaviour in the protocol endpoints of the RTP sender and RTP receiver entities, then we ended always in state models, which essentially allow to concentrate the entire specification "in a single place" (which is so far distribute over clauses 5, 6 and 8).

Thus, Fig. 4 "RTP pause states" is the key part at RTP sender side.

Two comments/questions:

1) the RTP sender state model seems to be not fully complete, thus, supposing that the Fig. just highlights the major state transitions, right?

2) a RTP receiver state model is missing, - why?

FYI: above contribution AVD-4696 provides a new proposed Appendix for ITU-T H.248.PAURES related to state modeling and above questions.

Regards,

Albrecht