
From nobody Wed Apr 22 01:36:34 2015
Return-Path: <albrecht.schwarz@alcatel-lucent.com>
X-Original-To: megaco@ietfa.amsl.com
Delivered-To: megaco@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5E6DF1B2AA6; Wed, 22 Apr 2015 01:36:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.909
X-Spam-Level: 
X-Spam-Status: No, score=-6.909 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id snoGOv5jRcWU; Wed, 22 Apr 2015 01:36:31 -0700 (PDT)
Received: from smtp-fr.alcatel-lucent.com (fr-hpgre-esg-01.alcatel-lucent.com [135.245.210.22]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2B0A61B2E36; Wed, 22 Apr 2015 01:35:53 -0700 (PDT)
Received: from fr711usmtp1.zeu.alcatel-lucent.com (unknown [135.239.2.122]) by Websense Email Security Gateway with ESMTPS id 3FE4F7BA0BA11; Wed, 22 Apr 2015 08:35:50 +0000 (GMT)
Received: from FR711WXCHHUB01.zeu.alcatel-lucent.com (fr711wxchhub01.zeu.alcatel-lucent.com [135.239.2.111]) by fr711usmtp1.zeu.alcatel-lucent.com (GMO) with ESMTP id t3M8Zn1C021499 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 22 Apr 2015 10:35:51 +0200
Received: from FR711WXCHMBA03.zeu.alcatel-lucent.com ([169.254.3.123]) by FR711WXCHHUB01.zeu.alcatel-lucent.com ([135.239.2.111]) with mapi id 14.03.0195.001; Wed, 22 Apr 2015 10:35:49 +0200
From: "Schwarz, Albrecht (Albrecht)" <albrecht.schwarz@alcatel-lucent.com>
To: "megaco@ietf.org" <megaco@ietf.org>, Christian Groves <Christian.Groves@nteczone.com>, "Yangweiwei (Tommy)" <tommy@huawei.com>
Thread-Topic: [RTP stream pause & resume]: middleboxes (ITU-T H.248.PAURES)
Thread-Index: AdB811TRB4197gUtSO2jI6ZzZli3Aw==
Date: Wed, 22 Apr 2015 08:35:49 +0000
Message-ID: <786615F3A85DF44AA2A76164A71FE1AC7AD725D6@FR711WXCHMBA03.zeu.alcatel-lucent.com>
Accept-Language: de-DE, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [135.239.27.41]
Content-Type: multipart/alternative; boundary="_000_786615F3A85DF44AA2A76164A71FE1AC7AD725D6FR711WXCHMBA03z_"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/megaco/tstfbonYwHFrk3_fgBEc93t-HZc>
Cc: "avtext@ietf.org" <avtext@ietf.org>
Subject: [Megaco] [RTP stream pause & resume]: middleboxes (ITU-T H.248.PAURES)
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Media Gateway Control <megaco.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/megaco>, <mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/megaco/>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/megaco>, <mailto:megaco-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Apr 2015 08:36:33 -0000

--_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&#8217;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>&nbsp;</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>&nbsp;</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 &#8211; 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 &#8211; 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>&nbsp;</o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"DE"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"DE">Hello Bo &amp; 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 &#8220;in a
 single place&#8221; (which is so far distribute over clauses 5, 6 and 8).<=
o:p></o:p></p>
<p class=3D"MsoPlainText">Thus, Fig. 4 &#8220;RTP pause states&#8221; 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>&nbsp;</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>&nbsp;</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_--

