[RTP stream pause & resume]: middleboxes (ITU-T H.248.PAURES)
"Schwarz, Albrecht (Albrecht)" <[email protected]> Wed, 22 Apr 2015 08:35:49 +0000
| Newsgroups | gmane.ietf.megaco |
|---|---|
| Message-ID | <786615F3A85DF44AA2A76164A71FE1AC7AD725D6@FR711WXCHMBA03.zeu.alcatel-lucent.com> |
--===============0626568000471842422==
Content-Language: en-US
Content-Type: multipart/alternative;
boundary="_000_786615F3A85DF44AA2A76164A71FE1AC7AD725D6FR711WXCHMBA03z_"
--_000_786615F3A85DF44AA2A76164A71FE1AC7AD725D6FR711WXCHMBA03z_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
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 medi=
a 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 endp=
oints of the RTP sender and RTP receiver entities, then we ended always in =
state models, which essentially allow to concentrate the entire specificati=
on "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, supposi=
ng 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
--_000_786615F3A85DF44AA2A76164A71FE1AC7AD725D6FR711WXCHMBA03z_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 12 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
{mso-style-priority:99;
mso-style-link:"Plain Text Char";
margin:0cm;
margin-bottom:.0001pt;
font-size:10.5pt;
font-family:Consolas;}
span.EmailStyle17
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.PlainTextChar
{mso-style-name:"Plain Text Char";
mso-style-priority:99;
mso-style-link:"Plain Text";
font-family:Consolas;}
.MsoChpDefault
{mso-style-type:export-only;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-GB" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoPlainText"><span lang=3D"DE">Hello Christian,<o:p></o:p></sp=
an></p>
<p class=3D"MsoPlainText">perhaps you noticed already that we’ve subm=
itted early contributions based on a review and consideration of specific u=
se cases for H.248 IP-to-IP media gateways (besides the obvious primary sce=
narios for H.248 media servers).<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p> </o:p></p>
<p class=3D"MsoPlainText"><span lang=3D"DE"><a href=3D"http://wftp3.itu.int=
/av-arch/avc-site/2013-2016/1506_Che/1506_Che.html">http://wftp3.itu.int/av=
-arch/avc-site/2013-2016/1506_Che/1506_Che.html</a>
<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"DE"><o:p> </o:p></span></p>
<table class=3D"MsoNormalTable" border=3D"0" cellspacing=3D"0" cellpadding=
=3D"0" width=3D"85%" style=3D"width:85.66%;border-collapse:collapse">
<tbody>
<tr>
<td width=3D"96" valign=3D"top" style=3D"width:72.0pt;border:solid #0066CC =
1.0pt;border-top:none;padding:0cm 5.4pt 0cm 5.4pt">
<p class=3D"MsoPlainText"><a href=3D"http://wftp3.itu.int/av-arch/avc-site/=
2013-2016/1506_Che/AVD-4695.zip">AVD-4695</a><o:p></o:p></p>
</td>
<td width=3D"45" valign=3D"top" style=3D"width:33.95pt;border-top:none;bord=
er-left:none;border-bottom:solid #0066CC 1.0pt;border-right:solid #0066CC 1=
.0pt;padding:0cm 5.4pt 0cm 5.4pt">
<p class=3D"MsoPlainText">3<o:p></o:p></p>
</td>
<td width=3D"605" valign=3D"top" style=3D"width:16.0cm;border-top:none;bord=
er-left:none;border-bottom:solid #0066CC 1.0pt;border-right:solid #0066CC 1=
.0pt;padding:0cm 5.4pt 0cm 5.4pt">
<p class=3D"MsoPlainText">H.248.PAURES: H.248 use cases and design consider=
ations (clauses 1 to 7)<o:p></o:p></p>
</td>
<td width=3D"151" valign=3D"top" style=3D"width:113.1pt;border-top:none;bor=
der-left:none;border-bottom:solid #0066CC 1.0pt;border-right:solid #0066CC =
1.0pt;padding:0cm 5.4pt 0cm 5.4pt">
<p class=3D"MsoPlainText">Alcatel-Lucent<o:p></o:p></p>
</td>
</tr>
<tr>
<td width=3D"96" valign=3D"top" style=3D"width:72.0pt;border:solid #0066CC =
1.0pt;border-top:none;padding:0cm 5.4pt 0cm 5.4pt">
<p class=3D"MsoPlainText"><a href=3D"http://wftp3.itu.int/av-arch/avc-site/=
2013-2016/1506_Che/AVD-4696.zip">AVD-4696</a><o:p></o:p></p>
</td>
<td width=3D"45" valign=3D"top" style=3D"width:33.95pt;border-top:none;bord=
er-left:none;border-bottom:solid #0066CC 1.0pt;border-right:solid #0066CC 1=
.0pt;padding:0cm 5.4pt 0cm 5.4pt">
<p class=3D"MsoPlainText">3<o:p></o:p></p>
</td>
<td width=3D"605" valign=3D"top" style=3D"width:16.0cm;border-top:none;bord=
er-left:none;border-bottom:solid #0066CC 1.0pt;border-right:solid #0066CC 1=
.0pt;padding:0cm 5.4pt 0cm 5.4pt">
<p class=3D"MsoPlainText">H.248.PAURES: Part II – Package review<o:p>=
</o:p></p>
</td>
<td width=3D"151" valign=3D"top" style=3D"width:113.1pt;border-top:none;bor=
der-left:none;border-bottom:solid #0066CC 1.0pt;border-right:solid #0066CC =
1.0pt;padding:0cm 5.4pt 0cm 5.4pt">
<p class=3D"MsoPlainText">Alcatel-Lucent<o:p></o:p></p>
</td>
</tr>
<tr>
<td width=3D"96" valign=3D"top" style=3D"width:72.0pt;border:solid #0066CC =
1.0pt;border-top:none;padding:0cm 5.4pt 0cm 5.4pt">
<p class=3D"MsoPlainText"><a href=3D"http://wftp3.itu.int/av-arch/avc-site/=
2013-2016/1506_Che/AVD-4697.zip">AVD-4697</a><o:p></o:p></p>
</td>
<td width=3D"45" valign=3D"top" style=3D"width:33.95pt;border-top:none;bord=
er-left:none;border-bottom:solid #0066CC 1.0pt;border-right:solid #0066CC 1=
.0pt;padding:0cm 5.4pt 0cm 5.4pt">
<p class=3D"MsoPlainText">3<o:p></o:p></p>
</td>
<td width=3D"605" valign=3D"top" style=3D"width:16.0cm;border-top:none;bord=
er-left:none;border-bottom:solid #0066CC 1.0pt;border-right:solid #0066CC 1=
.0pt;padding:0cm 5.4pt 0cm 5.4pt">
<p class=3D"MsoPlainText">H.248.PAURES: Part III – Possible interacti=
ons with RTP topologies<o:p></o:p></p>
</td>
<td width=3D"151" valign=3D"top" style=3D"width:113.1pt;border-top:none;bor=
der-left:none;border-bottom:solid #0066CC 1.0pt;border-right:solid #0066CC =
1.0pt;padding:0cm 5.4pt 0cm 5.4pt">
<p class=3D"MsoPlainText">Alcatel-Lucent<o:p></o:p></p>
</td>
</tr>
</tbody>
</table>
<p class=3D"MsoPlainText"><span lang=3D"DE"><o:p> </o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"DE"><o:p> </o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"DE">Hello Bo & Azam,<o:p></o:p>=
</span></p>
<p class=3D"MsoPlainText">when trying to figure out the exact protocol beha=
viour in the protocol endpoints of the RTP sender and RTP receiver entities=
, then we ended always in state models, which essentially allow to concentr=
ate the entire specification “in a
single place” (which is so far distribute over clauses 5, 6 and 8).<=
o:p></o:p></p>
<p class=3D"MsoPlainText">Thus, Fig. 4 “RTP pause states” is th=
e key part at RTP sender side.<o:p></o:p></p>
<p class=3D"MsoPlainText">Two comments/questions:<o:p></o:p></p>
<p class=3D"MsoPlainText">1) the RTP sender state model seems to be not ful=
ly complete, thus, supposing that the Fig. just highlights the major state =
transitions, right?<o:p></o:p></p>
<p class=3D"MsoPlainText">2) a RTP receiver state model is missing, - why?<=
o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p> </o:p></p>
<p class=3D"MsoPlainText">FYI: above contribution AVD-4696 provides a new p=
roposed Appendix for ITU-T H.248.PAURES related to state modeling and above=
questions.<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p> </o:p></p>
<p class=3D"MsoPlainText">Regards,<o:p></o:p></p>
<p class=3D"MsoPlainText">Albrecht<o:p></o:p></p>
</div>
</body>
</html>
--_000_786615F3A85DF44AA2A76164A71FE1AC7AD725D6FR711WXCHMBA03z_--
--===============0626568000471842422==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
_______________________________________________
Megaco mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/megaco
--===============0626568000471842422==--