
From javi@trajano.us.es  Thu Dec  1 02:02:52 2011
Return-Path: <javi@trajano.us.es>
X-Original-To: megaco@ietfa.amsl.com
Delivered-To: megaco@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F286321F867F for <megaco@ietfa.amsl.com>; Thu,  1 Dec 2011 02:02:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.828
X-Spam-Level: 
X-Spam-Status: No, score=-5.828 tagged_above=-999 required=5 tests=[AWL=-0.129, BAYES_00=-2.599, J_CHICKENPOX_73=0.6, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RjMw+7Uv4CTV for <megaco@ietfa.amsl.com>; Thu,  1 Dec 2011 02:02:51 -0800 (PST)
Received: from mail.us.es (mail.us.es [193.147.175.20]) by ietfa.amsl.com (Postfix) with ESMTP id 5D13A21F8562 for <megaco@ietf.org>; Thu,  1 Dec 2011 02:02:49 -0800 (PST)
Received: (qmail 29579 invoked from network); 1 Dec 2011 11:02:45 +0100
Received: from unknown (HELO us.es) (192.168.2.11) by us.es with SMTP; 1 Dec 2011 11:02:45 +0100
Received: (qmail 32525 invoked by uid 507); 1 Dec 2011 10:02:37 -0000
Received: from 127.0.0.1 by antivirus1 (envelope-from <javi@trajano.us.es>, uid 501) with qmail-scanner-2.08 (clamdscan: 0.97.3/14048.   Clear:RC:1(127.0.0.1):.  Processed in 0.11073 secs); 01 Dec 2011 10:02:36 -0000
Received: from unknown (HELO antivirus1) (127.0.0.1) by us.es with SMTP; 1 Dec 2011 10:02:36 -0000
Received: from 192.168.1.13 (192.168.1.13) by antivirus1 (F-Secure/fsigk_smtp/406/antivirus1); Thu, 01 Dec 2011 11:02:36 +0100 (CET)
X-Virus-Status: clean(F-Secure/fsigk_smtp/406/antivirus1)
Received: (qmail 18684 invoked from network); 1 Dec 2011 11:02:36 +0100
Received: from trajano.us.es (193.147.162.130) by us.es with AES256-SHA encrypted SMTP; 1 Dec 2011 11:02:36 +0100
Received: from [193.147.162.138] (adriano.us.es [193.147.162.138]) (authenticated bits=0) by trajano.us.es (8.13.8/8.13.8/Debian-3) with ESMTP id pB1A2ZbG008190 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NOT); Thu, 1 Dec 2011 11:02:36 +0100
Message-ID: <4ED750D6.9000608@trajano.us.es>
Date: Thu, 01 Dec 2011 11:03:02 +0100
From: =?ISO-8859-1?Q?Javi_Mu=F1oz?= <javi@trajano.us.es>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; es-ES; rv:1.9.2.24) Gecko/20111103 Thunderbird/3.1.16
MIME-Version: 1.0
To: "megaco@ietf.org" <megaco@ietf.org>
References: <4ED518F6.4020201@trajano.us.es>	<5F7BCCF5541B7444830A2288ABBEBC962161900622@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com>	<4ED604A0.2000402@trajano.us.es>	<4ED6640A.9030508@trajano.us.es>	<5F7BCCF5541B7444830A2288ABBEBC962161900780@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com>	<4ED66B87.7050907@trajano.us.es> <4ED6767D.7070109@trajano.us.es> <703C56B521385C4C9091299BE82357B7EF26034C@USNAVSXCHMBSA2.ndc.alcatel-lucent.com>
In-Reply-To: <703C56B521385C4C9091299BE82357B7EF26034C@USNAVSXCHMBSA2.ndc.alcatel-lucent.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Cc: "Bhattacharjee, Arindam \(Arindam\)" <arindam.bhattacharjee@alcatel-lucent.com>
Subject: Re: [Megaco] Selection of media (m=) at MG
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.1.12
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: Thu, 01 Dec 2011 10:02:52 -0000

Hello Arindam,


El 30/11/2011 21:20, Bhattacharjee, Arindam (Arindam) escribió:
> Hi Javi,
> + call establishment phase: H.248 Command.req for tone/announcement
> control plus media configuration with voice codec
>> You can do that by using reservevalue =ON in Local control and send SDP offer for both G711 and ClearMode.
>> Thus AGW should be able to encode/decode g711 and reserves resource for clearmode.

I understand you mean that I use:

m=audio <puerto> RTP/AVP <PT_dinámico> 0 [8]
a=rtpmap:<PT_dinámico> CLEARMODE/8000


But, how may we indicate to the MG that it uses G.711, and it only 
reserves resources for the CLEARMODE?

Regards,

Javi

> + information phase: H.248 Command.req for modification of the media
> configuration towards CLEARMODE
>> in this phase MGC may send reservevalue =OFF with SDP ClearMode only, releasing G711 resource.
> -Arindam
>
> -----Original Message-----
> From: megaco-bounces@ietf.org [mailto:megaco-bounces@ietf.org] On Behalf Of Javi Muñoz
> Sent: Wednesday, November 30, 2011 1:31 PM
> To: megaco@ietf.org
> Subject: Re: [Megaco] Selection of media (m=) at MG
>
> An aditional comment,
>
> if, as we said, we admit the following behavior:
>
> + call establishment phase: H.248 Command.req for tone/announcement
> control plus media configuration with voice codec
> + information phase: H.248 Command.req for modification of the media
> configuration towards CLEARMODE
>
>
> The following could happen:
>
> 1º Call starts and command.req for tone/announcement is applied.
>
> 2º When MGC needs to change to the information phase, the MG responds it
> does not support the CLEARMODE due to insufficient resources (MGC may
> audit the MG before the call to check it supports CLEARMODE, but MGC can
> not know how its resources will change during the call).
>
> In that case, it would not be possible to continue a call that has
> already begun, which should not happen. The SDP description should
> ensure to the MGC that the MG reserves the resources needed by the call
> prior to the establishment of it.
>
> If this is true, it would not be valid to use the modify command between
> the establishment and information phases.
>
> Regards,
>
> Javi
>
>
> El 30/11/2011 18:44, Javi Muñoz escribió:
>>> well spotted, thus just a single media configuration ('Clearmode')
>>> would be already sufficient to emulate that ISDN bearer service
>> However, two comments:
>>
>> (a) In the "call establishment phase": what must be created at the
>> MG?: would it be necessary to create a context, or would it be enough
>> to create only an ISDN termination in the null context (which would
>> generate that tone/announcement, and then, MGC would apply a modify
>> command to create the context for the information phase)?
>>
>> (b) I believe, the announcement do not necessarily have to be recorded
>> in AGW, but that may come from an announcement server (I guess this
>> would also be possible for DTMF tones). Could this justify the
>> creation of such IP termination with voice codec G.711 in the
>> establishment phase, or that communication with the announcement
>> server does not belong to the ISDN call and, therefore, it should not
>> be involved in its Megaco context?
>>
>> Regards,
>>
>>
>>
>>> PS
>>> Your previous email was related to ISDN-to-SIP interworking at call
>>> control level, a subject which is out of scope of MEGACO.
>>> Thus, something for SIPPING, SIP-IMPLEMENTERS, ... (or TISPAN WG3
>>> list) in my understanding.
>>>
>>>> -----Original Message-----
>>>> From: Javi Muñoz [mailto:javi@trajano.us.es]
>>>> Sent: Mittwoch, 30. November 2011 18:13
>>>> To: megaco@ietf.org
>>>> Cc: Schwarz, Albrecht (Albrecht)
>>>> Subject: Re: [Megaco] Selection of media (m=) at MG
>>>>
>>>> A second comment,
>>>>
>>>> If:
>>>>>>       a) TGW: no impact, because tone/announcement inserted by ISDN
>>>>>> local exchange (terminating Q.931); TGW needs just
>>>> clearmode support
>>>>
>>>> (I agree)
>>>>
>>>> then, why?
>>>>>> E.g., MGC
>>>>>> ->    call establishment phase: IF tones/announcements THEN H.248
>>>>>> Command.req for tone/announcement control plus media configuration
>>>>>> with voice codec
>>>> That "media configuration with voice codec" (G.711) would be
>>>> done at the MeGaCo termination of the IP side of the MG, not
>>>> at the termination of the ISDN side. If tone/announcement is
>>>> inserted (in the UNI ISDN) by this MG, the termination of the
>>>> IP side of the MG would not be used, so that "voice codec"
>>>> would not be relevant (no media would be transported over the
>>>> IP network).
>>>>
>>>> am I wrong?
>>>>
>>>> Regards,
>>>>
>>>> Javi
>>>>
>> _______________________________________________
>> Megaco mailing list
>> Megaco@ietf.org
>> https://www.ietf.org/mailman/listinfo/megaco
>>
> _______________________________________________
> Megaco mailing list
> Megaco@ietf.org
> https://www.ietf.org/mailman/listinfo/megaco
>


From arindam.bhattacharjee@alcatel-lucent.com  Thu Dec  1 06:23:05 2011
Return-Path: <arindam.bhattacharjee@alcatel-lucent.com>
X-Original-To: megaco@ietfa.amsl.com
Delivered-To: megaco@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 15A7811E839A for <megaco@ietfa.amsl.com>; Thu,  1 Dec 2011 06:23:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.699
X-Spam-Level: 
X-Spam-Status: No, score=-5.699 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_73=0.6, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id K-X9sG3PUZ9u for <megaco@ietfa.amsl.com>; Thu,  1 Dec 2011 06:23:02 -0800 (PST)
Received: from ihemail3.lucent.com (ihemail3.lucent.com [135.245.0.37]) by ietfa.amsl.com (Postfix) with ESMTP id 2E36011E8392 for <megaco@ietf.org>; Thu,  1 Dec 2011 06:23:02 -0800 (PST)
Received: from usnavsmail4.ndc.alcatel-lucent.com (usnavsmail4.ndc.alcatel-lucent.com [135.3.39.12]) by ihemail3.lucent.com (8.13.8/IER-o) with ESMTP id pB1EN0OO028860 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 1 Dec 2011 08:23:00 -0600 (CST)
Received: from USNAVSXCHHUB01.ndc.alcatel-lucent.com (usnavsxchhub01.ndc.alcatel-lucent.com [135.3.39.110]) by usnavsmail4.ndc.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id pB1EMxmb014280 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Thu, 1 Dec 2011 08:23:00 -0600
Received: from USNAVSXCHMBSA2.ndc.alcatel-lucent.com ([135.3.39.126]) by USNAVSXCHHUB01.ndc.alcatel-lucent.com ([135.3.39.110]) with mapi; Thu, 1 Dec 2011 08:22:59 -0600
From: "Bhattacharjee, Arindam (Arindam)" <arindam.bhattacharjee@alcatel-lucent.com>
To: =?iso-8859-1?Q?Javi_Mu=F1oz?= <javi@trajano.us.es>, "megaco@ietf.org" <megaco@ietf.org>
Date: Thu, 1 Dec 2011 08:22:56 -0600
Thread-Topic: [Megaco] Selection of media (m=) at MG
Thread-Index: AcywEF/Z9qIOmr6iRrq4OqHvnIojQAAIlU6A
Message-ID: <703C56B521385C4C9091299BE82357B7EF2605BE@USNAVSXCHMBSA2.ndc.alcatel-lucent.com>
References: <4ED518F6.4020201@trajano.us.es> <5F7BCCF5541B7444830A2288ABBEBC962161900622@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com> <4ED604A0.2000402@trajano.us.es>	<4ED6640A.9030508@trajano.us.es> <5F7BCCF5541B7444830A2288ABBEBC962161900780@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com> <4ED66B87.7050907@trajano.us.es> <4ED6767D.7070109@trajano.us.es> <703C56B521385C4C9091299BE82357B7EF26034C@USNAVSXCHMBSA2.ndc.alcatel-lucent.com> <4ED750D6.9000608@trajano.us.es>
In-Reply-To: <4ED750D6.9000608@trajano.us.es>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.37
X-Scanned-By: MIMEDefang 2.64 on 135.3.39.12
Subject: Re: [Megaco] Selection of media (m=) at MG
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.1.12
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: Thu, 01 Dec 2011 14:23:05 -0000

Hi Javi,
MG will resereve both resources and be able to decode both the codecs. Now =
if in the remote end the announcement server only uses g711 to send pkts th=
en MG will decode only g711 pkts, but will send g711 pkts since remote sdp =
is g711 only.
So in this case, phase 1:  local SDP will have both clearmode and g711 and =
remote SDP will have only G711. Of course MG should make sure that Clearmod=
e DSP resourse is reserved for both encoder/decoder, which is normally impl=
icit in this case.=20
In case of phase 2  both local and remote will have Clearmode with reserve =
value =3Doff.

More elaborate implementation of this scenario is under discussion now on H=
.248.80. Albrecht will know more about the status of that document.

-Arindam=20

-----Original Message-----
From: Javi Mu=F1oz [mailto:javi@trajano.us.es]=20
Sent: Thursday, December 01, 2011 5:03 AM
To: megaco@ietf.org
Cc: Bhattacharjee, Arindam (Arindam)
Subject: Re: [Megaco] Selection of media (m=3D) at MG

Hello Arindam,


El 30/11/2011 21:20, Bhattacharjee, Arindam (Arindam) escribi=F3:
> Hi Javi,
> + call establishment phase: H.248 Command.req for tone/announcement
> control plus media configuration with voice codec
>> You can do that by using reservevalue =3DON in Local control and send SD=
P offer for both G711 and ClearMode.
>> Thus AGW should be able to encode/decode g711 and reserves resource for =
clearmode.

I understand you mean that I use:

m=3Daudio <puerto> RTP/AVP <PT_din=E1mico> 0 [8]
a=3Drtpmap:<PT_din=E1mico> CLEARMODE/8000


But, how may we indicate to the MG that it uses G.711, and it only=20
reserves resources for the CLEARMODE?

Regards,

Javi

> + information phase: H.248 Command.req for modification of the media
> configuration towards CLEARMODE
>> in this phase MGC may send reservevalue =3DOFF with SDP ClearMode only, =
releasing G711 resource.
> -Arindam
>
> -----Original Message-----
> From: megaco-bounces@ietf.org [mailto:megaco-bounces@ietf.org] On Behalf =
Of Javi Mu=F1oz
> Sent: Wednesday, November 30, 2011 1:31 PM
> To: megaco@ietf.org
> Subject: Re: [Megaco] Selection of media (m=3D) at MG
>
> An aditional comment,
>
> if, as we said, we admit the following behavior:
>
> + call establishment phase: H.248 Command.req for tone/announcement
> control plus media configuration with voice codec
> + information phase: H.248 Command.req for modification of the media
> configuration towards CLEARMODE
>
>
> The following could happen:
>
> 1=BA Call starts and command.req for tone/announcement is applied.
>
> 2=BA When MGC needs to change to the information phase, the MG responds i=
t
> does not support the CLEARMODE due to insufficient resources (MGC may
> audit the MG before the call to check it supports CLEARMODE, but MGC can
> not know how its resources will change during the call).
>
> In that case, it would not be possible to continue a call that has
> already begun, which should not happen. The SDP description should
> ensure to the MGC that the MG reserves the resources needed by the call
> prior to the establishment of it.
>
> If this is true, it would not be valid to use the modify command between
> the establishment and information phases.
>
> Regards,
>
> Javi
>
>
> El 30/11/2011 18:44, Javi Mu=F1oz escribi=F3:
>>> well spotted, thus just a single media configuration ('Clearmode')
>>> would be already sufficient to emulate that ISDN bearer service
>> However, two comments:
>>
>> (a) In the "call establishment phase": what must be created at the
>> MG?: would it be necessary to create a context, or would it be enough
>> to create only an ISDN termination in the null context (which would
>> generate that tone/announcement, and then, MGC would apply a modify
>> command to create the context for the information phase)?
>>
>> (b) I believe, the announcement do not necessarily have to be recorded
>> in AGW, but that may come from an announcement server (I guess this
>> would also be possible for DTMF tones). Could this justify the
>> creation of such IP termination with voice codec G.711 in the
>> establishment phase, or that communication with the announcement
>> server does not belong to the ISDN call and, therefore, it should not
>> be involved in its Megaco context?
>>
>> Regards,
>>
>>
>>
>>> PS
>>> Your previous email was related to ISDN-to-SIP interworking at call
>>> control level, a subject which is out of scope of MEGACO.
>>> Thus, something for SIPPING, SIP-IMPLEMENTERS, ... (or TISPAN WG3
>>> list) in my understanding.
>>>
>>>> -----Original Message-----
>>>> From: Javi Mu=F1oz [mailto:javi@trajano.us.es]
>>>> Sent: Mittwoch, 30. November 2011 18:13
>>>> To: megaco@ietf.org
>>>> Cc: Schwarz, Albrecht (Albrecht)
>>>> Subject: Re: [Megaco] Selection of media (m=3D) at MG
>>>>
>>>> A second comment,
>>>>
>>>> If:
>>>>>>       a) TGW: no impact, because tone/announcement inserted by ISDN
>>>>>> local exchange (terminating Q.931); TGW needs just
>>>> clearmode support
>>>>
>>>> (I agree)
>>>>
>>>> then, why?
>>>>>> E.g., MGC
>>>>>> ->    call establishment phase: IF tones/announcements THEN H.248
>>>>>> Command.req for tone/announcement control plus media configuration
>>>>>> with voice codec
>>>> That "media configuration with voice codec" (G.711) would be
>>>> done at the MeGaCo termination of the IP side of the MG, not
>>>> at the termination of the ISDN side. If tone/announcement is
>>>> inserted (in the UNI ISDN) by this MG, the termination of the
>>>> IP side of the MG would not be used, so that "voice codec"
>>>> would not be relevant (no media would be transported over the
>>>> IP network).
>>>>
>>>> am I wrong?
>>>>
>>>> Regards,
>>>>
>>>> Javi
>>>>
>> _______________________________________________
>> Megaco mailing list
>> Megaco@ietf.org
>> https://www.ietf.org/mailman/listinfo/megaco
>>
> _______________________________________________
> Megaco mailing list
> Megaco@ietf.org
> https://www.ietf.org/mailman/listinfo/megaco
>


From albrecht.schwarz@alcatel-lucent.com  Thu Dec  1 08:21:01 2011
Return-Path: <albrecht.schwarz@alcatel-lucent.com>
X-Original-To: megaco@ietfa.amsl.com
Delivered-To: megaco@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3A66811E81A6; Thu,  1 Dec 2011 08:21:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.649
X-Spam-Level: 
X-Spam-Status: No, score=-5.649 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_FR=0.35, J_CHICKENPOX_14=0.6, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oZwPwX1ajkX9; Thu,  1 Dec 2011 08:20:59 -0800 (PST)
Received: from smail2.alcatel.fr (smail2.alcatel.fr [64.208.49.57]) by ietfa.amsl.com (Postfix) with ESMTP id 5689711E8121; Thu,  1 Dec 2011 08:20:59 -0800 (PST)
Received: from FRMRSSXCHHUB04.dc-m.alcatel-lucent.com (FRMRSSXCHHUB04.dc-m.alcatel-lucent.com [135.120.45.64]) by smail2.alcatel.fr (8.14.3/8.14.3/ICT) with ESMTP id pB1GKnuP032699 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Thu, 1 Dec 2011 17:20:51 +0100
Received: from FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com ([135.120.45.52]) by FRMRSSXCHHUB04.dc-m.alcatel-lucent.com ([135.120.45.64]) with mapi; Thu, 1 Dec 2011 17:20:30 +0100
From: "Schwarz, Albrecht (Albrecht)" <albrecht.schwarz@alcatel-lucent.com>
To: Qin Wu <bill.wu@huawei.com>, "avt@ietf.org" <avt@ietf.org>
Date: Thu, 1 Dec 2011 17:20:28 +0100
Thread-Topic: [AVTCORE] Types of monitoring architectures; RE:  I-D Action: draft-ietf-avtcore-monarch-08.txt
Thread-Index: AcyvyohSZB7NCXKAQDOWghJkAac7vwAdnG+g
Message-ID: <5F7BCCF5541B7444830A2288ABBEBC962161900908@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com>
References: <20111129075613.12419.4377.idtracker@ietfa.amsl.com> <5F7BCCF5541B7444830A2288ABBEBC96216190051A@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com> <EAC481B4D8034C38AC54E1217F8D875D@china.huawei.com> <5F7BCCF5541B7444830A2288ABBEBC96216190077F@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com> <B527BAFA038842A8939A8C2D558074CD@china.huawei.com>
In-Reply-To: <B527BAFA038842A8939A8C2D558074CD@china.huawei.com>
Accept-Language: de-DE, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: de-DE, en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.69 on 155.132.188.80
Cc: "megaco@ietf.org" <megaco@ietf.org>
Subject: Re: [Megaco] [AVTCORE] Types of monitoring architectures; RE:  I-D Action: draft-ietf-avtcore-monarch-08.txt
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.1.12
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: Thu, 01 Dec 2011 16:21:01 -0000

My replies below ...
-Albrecht=20

> -----Original Message-----
> From: Qin Wu [mailto:bill.wu@huawei.com]=20
> Sent: Donnerstag, 1. Dezember 2011 02:42
> To: Schwarz, Albrecht (Albrecht); avt@ietf.org
> Cc: megaco@ietf.org
> Subject: Re: [AVTCORE] Types of monitoring architectures; RE:=20
> I-D Action: draft-ietf-avtcore-monarch-08.txt
>=20
> Hi,
> ----- Original Message -----
> From: "Schwarz, Albrecht (Albrecht)"=20
> <albrecht.schwarz@alcatel-lucent.com>
> To: "Qin Wu" <bill.wu@huawei.com>; <avt@ietf.org>
> Cc: <megaco@ietf.org>
> Sent: Thursday, December 01, 2011 1:24 AM
> Subject: RE: [AVTCORE] Types of monitoring architectures; RE:=20
> I-D Action: draft-ietf-avtcore-monarch-08.txt
>=20
>=20
> My replies below inline,
> Albrecht=20
>=20
> > -----Original Message-----
> > From: Qin Wu [mailto:bill.wu@huawei.com]=20
> > Sent: Mittwoch, 30. November 2011 04:51
> > To: Schwarz, Albrecht (Albrecht); avt@ietf.org
> > Cc: megaco@ietf.org
> > Subject: Re: [AVTCORE] Types of monitoring architectures; RE:=20
> > I-D Action: draft-ietf-avtcore-monarch-08.txt
> >=20
> > Hi,
> > ----- Original Message -----
> > From: "Schwarz, Albrecht (Albrecht)"=20
> > <albrecht.schwarz@alcatel-lucent.com>
> > To: <avt@ietf.org>
> > Cc: <megaco@ietf.org>
> > Sent: Tuesday, November 29, 2011 7:32 PM
> > Subject: [AVTCORE] Types of monitoring architectures; RE: I-D=20
> > Action: draft-ietf-avtcore-monarch-08.txt
> >=20
> >=20
> > > Dear All,
> > >=20
> > > there are different types of monitoring architectures,=20
> > particularily from perspective of QoE related performance=20
> parameters.=20
> > > Let's recall QoE (e.g., ITU-T P.10 Amendment 2):
> > >=20
> > > Quality of Experience (QoE):=20
> > > The overall acceptability of an application or service, as=20
> > perceived subjectively by the end-user. =20
> > > NOTE 1 - Quality of experience includes the complete=20
> > end-to-end system effects (client, terminal, network,=20
> > services infrastructure, etc.).=20
> > > NOTE 2 - Overall acceptability may be influenced by user=20
> > expectations and context.=20
> > >=20
> > > Important for MONARCH:
> > > 1st ... perceived by end-user
> > > 2nd QoE includes the complete end-to-end sytem effects ...
> > >=20
> > > That said, present RTP monitoring architecture in MONARCH=20
> > according clause 3 is not specific on the type of monitoring=20
> > architecture. For instance, Fig. 1, it is possibly supposed=20
> > that the "RTP Sender" and "RTP Receiver" entities are equal=20
> > to a terminal/user equipment (UE). This would be an=20
> > end-to-end IP network scenario.
> > >=20
> > > However, the "RTP Sender" and "RTP Receiver" entities may=20
> > be also located at the edge of an IP network, e.g. in a=20
> > gateway for IP-to-non-IP interworking, i.e. an UE located in=20
> > the non-IP network part.=20
> > > Note: such scenarios are considered by MEGACO gateways=20
> > (I've Cc'd megaco list).
> > >=20
> > > An RTP Sender/Receiver located NOT in the UE would question=20
> > the value of RTP/RTCP QoE related performance measurements=20
> > (because the UE is located outside the RTP domain).=20
> > >=20
> > > Conclusions:
> > > - the set of meaningful performance metrics may be=20
> > dependent on the location of the RTP Sender/Receiver, e.g.=20
> > whether in a UE, gateway, ...
> > > - don't see any impact on transport level metrics
> > > - ... but the set of meaningful application level metrics
> > >=20
> > > Proposal for MONARCH:
> > > #1: insert sub-clause title "3.1 End-to-end IP network=20
> > architecture" below clause 3
> > >=20
> > > #2: add a sub-clause 3.2 at the end of clause 3, sth like
> > >=20
> > > "3.2 RTP Sender/Receiver entities located in network nodes
> > > The location of the RTP Sender/Receiver entity may impact=20
> > the set of meaningful metrics.
> > > For instance: application level metrics for QoE related=20
> > performance metrics are questionable (or doesn't really make=20
> > sense at all) when measured in a network node (terminating=20
> > the RTP) instead of the user equipment."
> > >=20
> > > Something like this would help to avoid confusion.
> > > I even believe that a QoE measurement in a network node=20
> > would violate the QoE definition. Would be rather something=20
> > like QoE* ("remote QoE"):-(
> > >=20
> > > Such information would improve the MONARCH doc in my opinion.
> > > Sorry for that late comment.
> > > Any views?
> >=20
> > [Qin]:=20
> > Albrrecht, if you follow ealry list discussion on=20
> > draft-hunt-avt-monarch-01, you will see the rough consensus=20
> > to position this document was=20
> > this daft should focus on guidelines for defining reporting=20
> > blocks. That is to say the main purpose of MONARCH draft is how to=20
> > provide guidelines for the development of new RTCP XR block=20
> > types in XRBlock working group.
>=20
> [ABS] ... then the title "monitoring architectures" is misleading.
> Proposal: keep title, revise scope section on focus
>=20
> [Qin]: No, the title is *RTP* monitoring architecture, we can=20
> not expand scope into IP monitoring architecture.

[ABS] That's wasn't the intent! Did just focus on the key word.

>=20
> >=20
> > Therefore how and where to collect the metric from RTP=20
> > endpoint is not scope of this document, in my opinion. since=20
> > you may have many ways to do this and different vendors have=20
> > their different appoaches. It will be better to leave this=20
> > beyond the scope. But you are right, it will be more=20
> > reasonable to measure QoE related performance metric at the=20
> > RTP receiver.
>=20
> [ABS] I would disagree. At least your statement should be=20
> conditional, sth like=20
> "QoE related performance metrics may be measured in a RTP=20
> receiver, IF the RTP receiver function is located in user=20
> equipment (e.g. IP terminal), because QoE performance metrics=20
> are tightly coupled to the point of view of a 'user'.
> ... IF NOT, then ..."
>=20
> [Qin]: I am not sure user equipment or IP terminal is the=20
> right term from RTP perspective.
>=20
> Also if you read P.NAMS, P.NAMS model for calculating QoE=20
> related metric can be placed either at the network or at the client.
> So I disagree with what you said.

[ABS] Not convinced at all.
Guess you are referring to the "mid-point" models, right?
The usage of such that models depends on "prior knowledge ..." information.
Thus, the applicability is conditional. You may not make such a general sta=
tement.


>=20
> Also as I said, how and where to collect the metric from RTP=20
>  endpoint is not scope of this document. It depends on the=20
> model you are choosing, e.g., four operation modes specified=20
> in P.NAMS.
> Apparently this should not be specified again in RTP=20
> monitoring architecture document.
>=20
> > =20
> > Another point is it is not clear to me how RTP monitoring has=20
> > to do with architectureend to end IP network architecture .
> > this draft mostly focus on discussing RTP level stuff.=20
> > Therefore I am quite doubt that we should describe anything=20
> > in this document like how
> > RTP entties is mapped into network entities/nodes at the IP layer.
>=20
> [ABS] I don't got any problems to talk about architectural=20
> framework for monitoring in this document. Such information=20
> is required and this is the only IETF AVT doc about it.
> The solution to this issue is rather simple to me:
> - split the MONARCH "monitoring architecture" in
> 1) a functional monitoring architecture (let's call it 'FMA') and
> 2) a physical monitoring architecture (... 'PMA').
>=20
> - the present MONARCH doc would describe the FMA at the level=20
> of RTP entities (i.e., Fig. 1 entities, incl. all the RTP=20
> topology components according RFC 5117)
>=20
> - there are many options of functional-to-physical mappings,=20
> i.e. how a FMA would be mapped on a PMA
> - the mapping is typically dependent on considered network=20
> architecture (like SIP, H.323, MGCP, IMS, wireless, etc networks)
>=20
> - the present MONARCH doc would describe the FMA-to-PMA=20
> mapping IF all RTP receiver/sender entities would be located=20
> in physical IP terminals (UEs)
> - etc
>=20
> [Qin]: I can understand your point, but you can not do that.=20
> Since this document is only focus on *RTP* monitoring=20
> architecture, that is what it said in AVTCore milestone:
> "
>=20
> Goals and Milestones:
>=20
>   Feb 2011 - Submit Monitoring Architecture for RTP for Informational
>=20
> "

[ABS] If you go back to my first email on this subject, and if you look at =
my proposal: that's not a lot, nothing which violates the charter, goals an=
d milestones.


> Also if you really don't see how to map FMA to PMA, you may=20
> look at the P.NAMS models specifed in ITU-T P.NAMS.=20
> As for how to use RTP monitoring architecture or RTP XR=20
> Report in the IMS network architecture, you may look at:
> http://tools.ietf.org/html/rfc6035

[ABS] That's the SIP reporting interface, i.e., applicable primarily for ph=
ysical IP user equipment with embedded RTP sender/receiver function and SIP=
 UA function.
However, the applicability of RFC 6035 is limited for a SIP-to-PSTN gateway=
 (because the RTP sender/receiver would be located NOT in user equipment. A=
lso the P.NAMS mid-point model fails for such a scenario.

> ITU-T H.248.48.
> But I haven't check the current status of H.248.48.

[ABS] Work is finalized, see http://www.itu.int/md/meetingdoc.asp?lang=3Den=
&parent=3DT09-SG16-111121-TD-PLEN-0419

>=20
> >=20
> > But as the author of this document, I am interested and open=20
> > to other opinions.:-)
>=20
> [ABS] Like to add a further aspect: a "functional monitoring=20
> architecture" may be considered as a network overlay,=20
> something which adds additional capabilities (here:=20
> measurement services, reporting services on top of basic RTP=20
> services).
> Such an overlay concept is nothing new: e.g., the=20
> MultiService Forum did define a "Performance Measurement &=20
> Monitoring (PMM)" overlay network, or IETF RMON may be also=20
> considered as such.
>=20
> >=20
> > > Regards,
> > > Albrecht
> > >=20
> > >=20
> > >=20
> > >=20
> > >> -----Original Message-----
> > >> From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On=20
> > >> Behalf Of internet-drafts@ietf.org
> > >> Sent: Dienstag, 29. November 2011 08:56
> > >> To: i-d-announce@ietf.org
> > >> Cc: avt@ietf.org
> > >> Subject: [AVTCORE] I-D Action: draft-ietf-avtcore-monarch-08.txt
> > >>=20
> > >>=20
> > >> A New Internet-Draft is available from the on-line=20
> > >> Internet-Drafts directories. This draft is a work item of the=20
> > >> Audio/Video Transport Core Maintenance Working Group of the IETF.
> > >>=20
> > >> Title           : Monitoring Architectures for RTP
> > >> Author(s)       : Qin Wu
> > >>                           Geoff Hunt
> > >>                           Philip Arden
> > >> Filename        : draft-ietf-avtcore-monarch-08.txt
> > >> Pages           : 25
> > >> Date            : 2011-11-28
> > >>=20
> > >>    This memo proposes an architecture for extending RTCP with=20
> > >> a new RTCP
> > >>    XR (RFC3611) block type to report new metrics regarding media
> > >>    transmission or reception quality, following RTCP guideline
> > >>    established in RFC5968.  This memo suggests that a new=20
> > block should
> > >>    contain a single metric or a small number of metrics=20
> > relevant to a
> > >>    single parameter of interest or concern, rather than=20
> > containing a
> > >>    number of metrics which attempt to provide full coverage=20
> > >> of all those
> > >>    parameters of concern to a specific application. =20
> > Applications may
> > >>    then "mix and match" to create a set of blocks which=20
> > >> covers their set
> > >>    of concerns.  Where possible, a specific block should be=20
> > >> designed to
> > >>    be re-usable across more than one application, for=20
> > example, for all
> > >>    of voice, streaming audio and video.
> > >>=20
> > >>=20
> > >> A URL for this Internet-Draft is:
> > >>=20
> >=20
> http://www.ietf.org/internet-drafts/draft-ietf-avtcore-monarch-08.txt
> > >>=20
> > >> Internet-Drafts are also available by anonymous FTP at:
> > >> ftp://ftp.ietf.org/internet-drafts/
> > >>=20
> > >> This Internet-Draft can be retrieved at:
> > >>=20
> > ftp://ftp.ietf.org/internet-drafts/draft-ietf-avtcore-monarch-08.txt
> > >>=20
> > >> _______________________________________________
> > >> Audio/Video Transport Core Maintenance
> > >> avt@ietf.org
> > >> https://www.ietf.org/mailman/listinfo/avt
> > >>=20
> > > _______________________________________________
> > > Audio/Video Transport Core Maintenance
> > > avt@ietf.org
> > > https://www.ietf.org/mailman/listinfo/avt
> >
> =

From bill.wu@huawei.com  Wed Nov 30 17:42:54 2011
Return-Path: <bill.wu@huawei.com>
X-Original-To: megaco@ietfa.amsl.com
Delivered-To: megaco@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1FDC711E809D; Wed, 30 Nov 2011 17:42:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.091
X-Spam-Level: 
X-Spam-Status: No, score=-6.091 tagged_above=-999 required=5 tests=[AWL=-0.092, BAYES_00=-2.599, J_CHICKENPOX_14=0.6, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id J3aYhqlYIMLA; Wed, 30 Nov 2011 17:42:53 -0800 (PST)
Received: from szxga01-in.huawei.com (szxga01-in.huawei.com [119.145.14.64]) by ietfa.amsl.com (Postfix) with ESMTP id C58B411E8099; Wed, 30 Nov 2011 17:42:52 -0800 (PST)
Received: from huawei.com (szxga05-in [172.24.2.49]) by szxga05-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LVI00GIU4R8AB@szxga05-in.huawei.com>; Thu, 01 Dec 2011 09:42:44 +0800 (CST)
Received: from szxrg01-dlp.huawei.com ([172.24.2.119]) by szxga05-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LVI005MK4R6Z6@szxga05-in.huawei.com>; Thu, 01 Dec 2011 09:42:44 +0800 (CST)
Received: from szxeml208-edg.china.huawei.com ([172.24.2.119]) by szxrg01-dlp.huawei.com (MOS 4.1.9-GA)	with ESMTP id AFL62318; Thu, 01 Dec 2011 09:42:10 +0800
Received: from SZXEML403-HUB.china.huawei.com (10.82.67.35) by szxeml208-edg.china.huawei.com (172.24.2.60) with Microsoft SMTP Server (TLS) id 14.1.323.3; Thu, 01 Dec 2011 09:42:05 +0800
Received: from w53375q (10.138.41.130) by szxeml403-hub.china.huawei.com (10.82.67.35) with Microsoft SMTP Server (TLS) id 14.1.323.3; Thu, 01 Dec 2011 09:42:01 +0800
Date: Thu, 01 Dec 2011 09:42:00 +0800
From: Qin Wu <bill.wu@huawei.com>
X-Originating-IP: [10.138.41.130]
To: "Schwarz, Albrecht (Albrecht)" <albrecht.schwarz@alcatel-lucent.com>, avt@ietf.org
Message-id: <B527BAFA038842A8939A8C2D558074CD@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.6109
X-Mailer: Microsoft Outlook Express 6.00.2900.5931
Content-type: text/plain; charset=iso-8859-1
Content-transfer-encoding: 7BIT
X-Priority: 3
X-MSMail-priority: Normal
X-CFilter-Loop: Reflected
References: <20111129075613.12419.4377.idtracker@ietfa.amsl.com> <5F7BCCF5541B7444830A2288ABBEBC96216190051A@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com> <EAC481B4D8034C38AC54E1217F8D875D@china.huawei.com> <5F7BCCF5541B7444830A2288ABBEBC96216190077F@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com>
X-Mailman-Approved-At: Thu, 01 Dec 2011 08:35:23 -0800
Cc: megaco@ietf.org
Subject: Re: [Megaco] [AVTCORE] Types of monitoring architectures; RE:  I-D Action: draft-ietf-avtcore-monarch-08.txt
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.1.12
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: Thu, 01 Dec 2011 01:42:54 -0000

Hi,
----- Original Message ----- 
From: "Schwarz, Albrecht (Albrecht)" <albrecht.schwarz@alcatel-lucent.com>
To: "Qin Wu" <bill.wu@huawei.com>; <avt@ietf.org>
Cc: <megaco@ietf.org>
Sent: Thursday, December 01, 2011 1:24 AM
Subject: RE: [AVTCORE] Types of monitoring architectures; RE: I-D Action: draft-ietf-avtcore-monarch-08.txt


My replies below inline,
Albrecht 

> -----Original Message-----
> From: Qin Wu [mailto:bill.wu@huawei.com] 
> Sent: Mittwoch, 30. November 2011 04:51
> To: Schwarz, Albrecht (Albrecht); avt@ietf.org
> Cc: megaco@ietf.org
> Subject: Re: [AVTCORE] Types of monitoring architectures; RE: 
> I-D Action: draft-ietf-avtcore-monarch-08.txt
> 
> Hi,
> ----- Original Message -----
> From: "Schwarz, Albrecht (Albrecht)" 
> <albrecht.schwarz@alcatel-lucent.com>
> To: <avt@ietf.org>
> Cc: <megaco@ietf.org>
> Sent: Tuesday, November 29, 2011 7:32 PM
> Subject: [AVTCORE] Types of monitoring architectures; RE: I-D 
> Action: draft-ietf-avtcore-monarch-08.txt
> 
> 
> > Dear All,
> > 
> > there are different types of monitoring architectures, 
> particularily from perspective of QoE related performance parameters. 
> > Let's recall QoE (e.g., ITU-T P.10 Amendment 2):
> > 
> > Quality of Experience (QoE): 
> > The overall acceptability of an application or service, as 
> perceived subjectively by the end-user.  
> > NOTE 1 - Quality of experience includes the complete 
> end-to-end system effects (client, terminal, network, 
> services infrastructure, etc.). 
> > NOTE 2 - Overall acceptability may be influenced by user 
> expectations and context. 
> > 
> > Important for MONARCH:
> > 1st ... perceived by end-user
> > 2nd QoE includes the complete end-to-end sytem effects ...
> > 
> > That said, present RTP monitoring architecture in MONARCH 
> according clause 3 is not specific on the type of monitoring 
> architecture. For instance, Fig. 1, it is possibly supposed 
> that the "RTP Sender" and "RTP Receiver" entities are equal 
> to a terminal/user equipment (UE). This would be an 
> end-to-end IP network scenario.
> > 
> > However, the "RTP Sender" and "RTP Receiver" entities may 
> be also located at the edge of an IP network, e.g. in a 
> gateway for IP-to-non-IP interworking, i.e. an UE located in 
> the non-IP network part. 
> > Note: such scenarios are considered by MEGACO gateways 
> (I've Cc'd megaco list).
> > 
> > An RTP Sender/Receiver located NOT in the UE would question 
> the value of RTP/RTCP QoE related performance measurements 
> (because the UE is located outside the RTP domain). 
> > 
> > Conclusions:
> > - the set of meaningful performance metrics may be 
> dependent on the location of the RTP Sender/Receiver, e.g. 
> whether in a UE, gateway, ...
> > - don't see any impact on transport level metrics
> > - ... but the set of meaningful application level metrics
> > 
> > Proposal for MONARCH:
> > #1: insert sub-clause title "3.1 End-to-end IP network 
> architecture" below clause 3
> > 
> > #2: add a sub-clause 3.2 at the end of clause 3, sth like
> > 
> > "3.2 RTP Sender/Receiver entities located in network nodes
> > The location of the RTP Sender/Receiver entity may impact 
> the set of meaningful metrics.
> > For instance: application level metrics for QoE related 
> performance metrics are questionable (or doesn't really make 
> sense at all) when measured in a network node (terminating 
> the RTP) instead of the user equipment."
> > 
> > Something like this would help to avoid confusion.
> > I even believe that a QoE measurement in a network node 
> would violate the QoE definition. Would be rather something 
> like QoE* ("remote QoE"):-(
> > 
> > Such information would improve the MONARCH doc in my opinion.
> > Sorry for that late comment.
> > Any views?
> 
> [Qin]: 
> Albrrecht, if you follow ealry list discussion on 
> draft-hunt-avt-monarch-01, you will see the rough consensus 
> to position this document was 
> this daft should focus on guidelines for defining reporting 
> blocks. That is to say the main purpose of MONARCH draft is how to 
> provide guidelines for the development of new RTCP XR block 
> types in XRBlock working group.

[ABS] ... then the title "monitoring architectures" is misleading.
Proposal: keep title, revise scope section on focus

[Qin]: No, the title is *RTP* monitoring architecture, we can not expand scope into IP monitoring architecture.

> 
> Therefore how and where to collect the metric from RTP 
> endpoint is not scope of this document, in my opinion. since 
> you may have many ways to do this and different vendors have 
> their different appoaches. It will be better to leave this 
> beyond the scope. But you are right, it will be more 
> reasonable to measure QoE related performance metric at the 
> RTP receiver.

[ABS] I would disagree. At least your statement should be conditional, sth like 
"QoE related performance metrics may be measured in a RTP receiver, IF the RTP receiver function is located in user equipment (e.g. IP terminal), because QoE performance metrics are tightly coupled to the point of view of a 'user'.
... IF NOT, then ..."

[Qin]: I am not sure user equipment or IP terminal is the right term from RTP perspective.

Also if you read P.NAMS, P.NAMS model for calculating QoE related metric can be placed either at the network or at the client.
So I disagree with what you said.

Also as I said, how and where to collect the metric from RTP 
 endpoint is not scope of this document. It depends on the model you are choosing, e.g., four operation modes specified in P.NAMS.
Apparently this should not be specified again in RTP monitoring architecture document.

>  
> Another point is it is not clear to me how RTP monitoring has 
> to do with architectureend to end IP network architecture .
> this draft mostly focus on discussing RTP level stuff. 
> Therefore I am quite doubt that we should describe anything 
> in this document like how
> RTP entties is mapped into network entities/nodes at the IP layer.

[ABS] I don't got any problems to talk about architectural framework for monitoring in this document. Such information is required and this is the only IETF AVT doc about it.
The solution to this issue is rather simple to me:
- split the MONARCH "monitoring architecture" in
1) a functional monitoring architecture (let's call it 'FMA') and
2) a physical monitoring architecture (... 'PMA').

- the present MONARCH doc would describe the FMA at the level of RTP entities (i.e., Fig. 1 entities, incl. all the RTP topology components according RFC 5117)

- there are many options of functional-to-physical mappings, i.e. how a FMA would be mapped on a PMA
- the mapping is typically dependent on considered network architecture (like SIP, H.323, MGCP, IMS, wireless, etc networks)

- the present MONARCH doc would describe the FMA-to-PMA mapping IF all RTP receiver/sender entities would be located in physical IP terminals (UEs)
- etc

[Qin]: I can understand your point, but you can not do that. Since this document is only focus on *RTP* monitoring architecture, that is what it said in AVTCore milestone:
"

Goals and Milestones:

  Feb 2011 - Submit Monitoring Architecture for RTP for Informational

"
Also if you really don't see how to map FMA to PMA, you may look at the P.NAMS models specifed in ITU-T P.NAMS. 
As for how to use RTP monitoring architecture or RTP XR Report in the IMS network architecture, you may look at:
http://tools.ietf.org/html/rfc6035
ITU-T H.248.48.
But I haven't check the current status of H.248.48.

> 
> But as the author of this document, I am interested and open 
> to other opinions.:-)

[ABS] Like to add a further aspect: a "functional monitoring architecture" may be considered as a network overlay, something which adds additional capabilities (here: measurement services, reporting services on top of basic RTP services).
Such an overlay concept is nothing new: e.g., the MultiService Forum did define a "Performance Measurement & Monitoring (PMM)" overlay network, or IETF RMON may be also considered as such.

> 
> > Regards,
> > Albrecht
> > 
> > 
> > 
> > 
> >> -----Original Message-----
> >> From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On 
> >> Behalf Of internet-drafts@ietf.org
> >> Sent: Dienstag, 29. November 2011 08:56
> >> To: i-d-announce@ietf.org
> >> Cc: avt@ietf.org
> >> Subject: [AVTCORE] I-D Action: draft-ietf-avtcore-monarch-08.txt
> >> 
> >> 
> >> A New Internet-Draft is available from the on-line 
> >> Internet-Drafts directories. This draft is a work item of the 
> >> Audio/Video Transport Core Maintenance Working Group of the IETF.
> >> 
> >> Title           : Monitoring Architectures for RTP
> >> Author(s)       : Qin Wu
> >>                           Geoff Hunt
> >>                           Philip Arden
> >> Filename        : draft-ietf-avtcore-monarch-08.txt
> >> Pages           : 25
> >> Date            : 2011-11-28
> >> 
> >>    This memo proposes an architecture for extending RTCP with 
> >> a new RTCP
> >>    XR (RFC3611) block type to report new metrics regarding media
> >>    transmission or reception quality, following RTCP guideline
> >>    established in RFC5968.  This memo suggests that a new 
> block should
> >>    contain a single metric or a small number of metrics 
> relevant to a
> >>    single parameter of interest or concern, rather than 
> containing a
> >>    number of metrics which attempt to provide full coverage 
> >> of all those
> >>    parameters of concern to a specific application.  
> Applications may
> >>    then "mix and match" to create a set of blocks which 
> >> covers their set
> >>    of concerns.  Where possible, a specific block should be 
> >> designed to
> >>    be re-usable across more than one application, for 
> example, for all
> >>    of voice, streaming audio and video.
> >> 
> >> 
> >> A URL for this Internet-Draft is:
> >> 
> http://www.ietf.org/internet-drafts/draft-ietf-avtcore-monarch-08.txt
> >> 
> >> Internet-Drafts are also available by anonymous FTP at:
> >> ftp://ftp.ietf.org/internet-drafts/
> >> 
> >> This Internet-Draft can be retrieved at:
> >> 
> ftp://ftp.ietf.org/internet-drafts/draft-ietf-avtcore-monarch-08.txt
> >> 
> >> _______________________________________________
> >> Audio/Video Transport Core Maintenance
> >> avt@ietf.org
> >> https://www.ietf.org/mailman/listinfo/avt
> >> 
> > _______________________________________________
> > Audio/Video Transport Core Maintenance
> > avt@ietf.org
> > https://www.ietf.org/mailman/listinfo/avt
>

From javi@trajano.us.es  Thu Dec  1 08:49:35 2011
Return-Path: <javi@trajano.us.es>
X-Original-To: megaco@ietfa.amsl.com
Delivered-To: megaco@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 704FF11E8262 for <megaco@ietfa.amsl.com>; Thu,  1 Dec 2011 08:49:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.849
X-Spam-Level: 
X-Spam-Status: No, score=-5.849 tagged_above=-999 required=5 tests=[AWL=-0.150, BAYES_00=-2.599, J_CHICKENPOX_73=0.6, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JMsG7w5OQCwE for <megaco@ietfa.amsl.com>; Thu,  1 Dec 2011 08:49:34 -0800 (PST)
Received: from mail.us.es (mail.us.es [193.147.175.20]) by ietfa.amsl.com (Postfix) with ESMTP id F163511E8176 for <megaco@ietf.org>; Thu,  1 Dec 2011 08:49:33 -0800 (PST)
Received: (qmail 4319 invoked from network); 1 Dec 2011 17:49:33 +0100
Received: from unknown (HELO us.es) (192.168.2.12) by us.es with SMTP; 1 Dec 2011 17:49:33 +0100
Received: (qmail 28544 invoked by uid 507); 1 Dec 2011 16:49:31 -0000
Received: from 127.0.0.1 by antivirus2 (envelope-from <javi@trajano.us.es>, uid 501) with qmail-scanner-2.08 (clamdscan: 0.97.3/14056.   Clear:RC:1(127.0.0.1):.  Processed in 0.060973 secs); 01 Dec 2011 16:49:31 -0000
Received: from unknown (HELO antivirus2) (127.0.0.1) by us.es with SMTP; 1 Dec 2011 16:49:31 -0000
Received: from 192.168.1.13 (192.168.1.13) by antivirus2 (F-Secure/fsigk_smtp/406/antivirus2); Thu, 01 Dec 2011 17:49:31 +0100 (CET)
X-Virus-Status: clean(F-Secure/fsigk_smtp/406/antivirus2)
Received: (qmail 16092 invoked from network); 1 Dec 2011 17:49:31 +0100
Received: from trajano.us.es (193.147.162.130) by us.es with AES256-SHA encrypted SMTP; 1 Dec 2011 17:49:31 +0100
Received: from [193.147.162.138] (adriano.us.es [193.147.162.138]) (authenticated bits=0) by trajano.us.es (8.13.8/8.13.8/Debian-3) with ESMTP id pB1GnVrX015305 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NOT); Thu, 1 Dec 2011 17:49:31 +0100
Message-ID: <4ED7B036.4000103@trajano.us.es>
Date: Thu, 01 Dec 2011 17:49:58 +0100
From: =?ISO-8859-1?Q?Javi_Mu=F1oz?= <javi@trajano.us.es>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; es-ES; rv:1.9.2.24) Gecko/20111103 Thunderbird/3.1.16
MIME-Version: 1.0
To: "megaco@ietf.org" <megaco@ietf.org>
References: <4ED518F6.4020201@trajano.us.es>	<5F7BCCF5541B7444830A2288ABBEBC962161900622@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com>	<4ED604A0.2000402@trajano.us.es>	<4ED6640A.9030508@trajano.us.es>	<5F7BCCF5541B7444830A2288ABBEBC962161900780@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com>	<4ED66B87.7050907@trajano.us.es> <4ED6767D.7070109@trajano.us.es> <703C56B521385C4C9091299BE82357B7EF26034C@USNAVSXCHMBSA2.ndc.alcatel-lucent.com> <4ED750D6.9000608@trajano.us.es> <703C56B521385C4C9091299BE82357B7EF2605BE@USNAVSXCHMBSA2.ndc.alcatel-lucent.com>
In-Reply-To: <703C56B521385C4C9091299BE82357B7EF2605BE@USNAVSXCHMBSA2.ndc.alcatel-lucent.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Cc: "Bhattacharjee, Arindam \(Arindam\)" <arindam.bhattacharjee@alcatel-lucent.com>
Subject: Re: [Megaco] Selection of media (m=) at MG
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.1.12
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: Thu, 01 Dec 2011 16:49:35 -0000

El 01/12/2011 15:22, Bhattacharjee, Arindam (Arindam) escribió:
> Hi Javi,
> MG will resereve both resources and be able to decode both the codecs. Now if in the remote end the announcement server only uses g711 to send pkts then MG will decode only g711 pkts, but will send g711 pkts since remote sdp is g711 only.
> So in this case, phase 1:  local SDP will have both clearmode and g711 and remote SDP will have only G711. Of course MG should make sure that Clearmode DSP resourse is reserved for both encoder/decoder, which is normally implicit in this case.

You mean that if we indicate a codec (such as "Clearmode") in the Local 
descriptor (decoder), MG must reserve resources for decoder and encoder 
(although that codec is not specified in the Remote descriptor).

Is that so specified by [H.248.1] or is it part of the Recommendation 
[H.248.80]?

regards,

Javi
> In case of phase 2  both local and remote will have Clearmode with reserve value =off.
>
> More elaborate implementation of this scenario is under discussion now on H.248.80. Albrecht will know more about the status of that document.
>
> -Arindam
>
> -----Original Message-----
> From: Javi Muñoz [mailto:javi@trajano.us.es]
> Sent: Thursday, December 01, 2011 5:03 AM
> To: megaco@ietf.org
> Cc: Bhattacharjee, Arindam (Arindam)
> Subject: Re: [Megaco] Selection of media (m=) at MG
>
> Hello Arindam,
>
>
> El 30/11/2011 21:20, Bhattacharjee, Arindam (Arindam) escribió:
>> Hi Javi,
>> + call establishment phase: H.248 Command.req for tone/announcement
>> control plus media configuration with voice codec
>>> You can do that by using reservevalue =ON in Local control and send SDP offer for both G711 and ClearMode.
>>> Thus AGW should be able to encode/decode g711 and reserves resource for clearmode.
> I understand you mean that I use:
>
> m=audio<puerto>  RTP/AVP<PT_dinámico>  0 [8]
> a=rtpmap:<PT_dinámico>  CLEARMODE/8000
>
>
> But, how may we indicate to the MG that it uses G.711, and it only
> reserves resources for the CLEARMODE?
>
> Regards,
>
> Javi
>
>> + information phase: H.248 Command.req for modification of the media
>> configuration towards CLEARMODE
>>> in this phase MGC may send reservevalue =OFF with SDP ClearMode only, releasing G711 resource.
>> -Arindam
>>
>> -----Original Message-----
>> From: megaco-bounces@ietf.org [mailto:megaco-bounces@ietf.org] On Behalf Of Javi Muñoz
>> Sent: Wednesday, November 30, 2011 1:31 PM
>> To: megaco@ietf.org
>> Subject: Re: [Megaco] Selection of media (m=) at MG
>>
>> An aditional comment,
>>
>> if, as we said, we admit the following behavior:
>>
>> + call establishment phase: H.248 Command.req for tone/announcement
>> control plus media configuration with voice codec
>> + information phase: H.248 Command.req for modification of the media
>> configuration towards CLEARMODE
>>
>>
>> The following could happen:
>>
>> 1º Call starts and command.req for tone/announcement is applied.
>>
>> 2º When MGC needs to change to the information phase, the MG responds it
>> does not support the CLEARMODE due to insufficient resources (MGC may
>> audit the MG before the call to check it supports CLEARMODE, but MGC can
>> not know how its resources will change during the call).
>>
>> In that case, it would not be possible to continue a call that has
>> already begun, which should not happen. The SDP description should
>> ensure to the MGC that the MG reserves the resources needed by the call
>> prior to the establishment of it.
>>
>> If this is true, it would not be valid to use the modify command between
>> the establishment and information phases.
>>
>> Regards,
>>
>> Javi
>>
>>
>> El 30/11/2011 18:44, Javi Muñoz escribió:
>>>> well spotted, thus just a single media configuration ('Clearmode')
>>>> would be already sufficient to emulate that ISDN bearer service
>>> However, two comments:
>>>
>>> (a) In the "call establishment phase": what must be created at the
>>> MG?: would it be necessary to create a context, or would it be enough
>>> to create only an ISDN termination in the null context (which would
>>> generate that tone/announcement, and then, MGC would apply a modify
>>> command to create the context for the information phase)?
>>>
>>> (b) I believe, the announcement do not necessarily have to be recorded
>>> in AGW, but that may come from an announcement server (I guess this
>>> would also be possible for DTMF tones). Could this justify the
>>> creation of such IP termination with voice codec G.711 in the
>>> establishment phase, or that communication with the announcement
>>> server does not belong to the ISDN call and, therefore, it should not
>>> be involved in its Megaco context?
>>>
>>> Regards,
>>>
>>>
>>>
>>>> PS
>>>> Your previous email was related to ISDN-to-SIP interworking at call
>>>> control level, a subject which is out of scope of MEGACO.
>>>> Thus, something for SIPPING, SIP-IMPLEMENTERS, ... (or TISPAN WG3
>>>> list) in my understanding.
>>>>
>>>>> -----Original Message-----
>>>>> From: Javi Muñoz [mailto:javi@trajano.us.es]
>>>>> Sent: Mittwoch, 30. November 2011 18:13
>>>>> To: megaco@ietf.org
>>>>> Cc: Schwarz, Albrecht (Albrecht)
>>>>> Subject: Re: [Megaco] Selection of media (m=) at MG
>>>>>
>>>>> A second comment,
>>>>>
>>>>> If:
>>>>>>>        a) TGW: no impact, because tone/announcement inserted by ISDN
>>>>>>> local exchange (terminating Q.931); TGW needs just
>>>>> clearmode support
>>>>>
>>>>> (I agree)
>>>>>
>>>>> then, why?
>>>>>>> E.g., MGC
>>>>>>> ->     call establishment phase: IF tones/announcements THEN H.248
>>>>>>> Command.req for tone/announcement control plus media configuration
>>>>>>> with voice codec
>>>>> That "media configuration with voice codec" (G.711) would be
>>>>> done at the MeGaCo termination of the IP side of the MG, not
>>>>> at the termination of the ISDN side. If tone/announcement is
>>>>> inserted (in the UNI ISDN) by this MG, the termination of the
>>>>> IP side of the MG would not be used, so that "voice codec"
>>>>> would not be relevant (no media would be transported over the
>>>>> IP network).
>>>>>
>>>>> am I wrong?
>>>>>
>>>>> Regards,
>>>>>
>>>>> Javi
>>>>>
>>> _______________________________________________
>>> Megaco mailing list
>>> Megaco@ietf.org
>>> https://www.ietf.org/mailman/listinfo/megaco
>>>
>> _______________________________________________
>> Megaco mailing list
>> Megaco@ietf.org
>> https://www.ietf.org/mailman/listinfo/megaco
>>
>


From arindam.bhattacharjee@alcatel-lucent.com  Thu Dec  1 10:28:05 2011
Return-Path: <arindam.bhattacharjee@alcatel-lucent.com>
X-Original-To: megaco@ietfa.amsl.com
Delivered-To: megaco@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 972ED11E80CA for <megaco@ietfa.amsl.com>; Thu,  1 Dec 2011 10:28:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.699
X-Spam-Level: 
X-Spam-Status: No, score=-5.699 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_73=0.6, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qQrnCAwIuTER for <megaco@ietfa.amsl.com>; Thu,  1 Dec 2011 10:28:04 -0800 (PST)
Received: from ihemail2.lucent.com (ihemail2.lucent.com [135.245.0.35]) by ietfa.amsl.com (Postfix) with ESMTP id ADCCD11E8073 for <megaco@ietf.org>; Thu,  1 Dec 2011 10:28:04 -0800 (PST)
Received: from usnavsmail4.ndc.alcatel-lucent.com (usnavsmail4.ndc.alcatel-lucent.com [135.3.39.12]) by ihemail2.lucent.com (8.13.8/IER-o) with ESMTP id pB1IS3pr020498 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 1 Dec 2011 12:28:03 -0600 (CST)
Received: from USNAVSXCHHUB02.ndc.alcatel-lucent.com (usnavsxchhub02.ndc.alcatel-lucent.com [135.3.39.111]) by usnavsmail4.ndc.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id pB1IS1lg023887 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Thu, 1 Dec 2011 12:28:03 -0600
Received: from USNAVSXCHMBSA2.ndc.alcatel-lucent.com ([135.3.39.126]) by USNAVSXCHHUB02.ndc.alcatel-lucent.com ([135.3.39.111]) with mapi; Thu, 1 Dec 2011 12:28:01 -0600
From: "Bhattacharjee, Arindam (Arindam)" <arindam.bhattacharjee@alcatel-lucent.com>
To: =?iso-8859-1?Q?Javi_Mu=F1oz?= <javi@trajano.us.es>, "megaco@ietf.org" <megaco@ietf.org>
Date: Thu, 1 Dec 2011 12:27:59 -0600
Thread-Topic: [Megaco] Selection of media (m=) at MG
Thread-Index: AcywSThjNFhxf4uBSMSnrtLmEfR+QAAAChIQ
Message-ID: <703C56B521385C4C9091299BE82357B7EF2607C5@USNAVSXCHMBSA2.ndc.alcatel-lucent.com>
References: <4ED518F6.4020201@trajano.us.es> <5F7BCCF5541B7444830A2288ABBEBC962161900622@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com> <4ED604A0.2000402@trajano.us.es>	<4ED6640A.9030508@trajano.us.es> <5F7BCCF5541B7444830A2288ABBEBC962161900780@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com> <4ED66B87.7050907@trajano.us.es>	<4ED6767D.7070109@trajano.us.es> <703C56B521385C4C9091299BE82357B7EF26034C@USNAVSXCHMBSA2.ndc.alcatel-lucent.com> <4ED750D6.9000608@trajano.us.es> <703C56B521385C4C9091299BE82357B7EF2605BE@USNAVSXCHMBSA2.ndc.alcatel-lucent.com> <4ED7B036.4000103@trajano.us.es>
In-Reply-To: <4ED7B036.4000103@trajano.us.es>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.35
X-Scanned-By: MIMEDefang 2.64 on 135.3.39.12
Subject: Re: [Megaco] Selection of media (m=) at MG
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.1.12
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: Thu, 01 Dec 2011 18:28:05 -0000

> You mean that if we indicate a codec (such as "Clearmode") in the Local=20
descriptor (decoder), MG must reserve resources for decoder and encoder=20
(although that codec is not specified in the Remote descriptor).
Yes, and this is as per H.248.1: when local descriptor has both codecs g711=
 and clearmode and g711 in remote MG needs to add only decoders for both an=
d encoder for g711 only, but in practice normally both decoder and encoder =
is reserved for all the codecs.

You can use another option: have reserve value on and use both g711 and Cle=
armode on both remote and local SDP and MG will send in g711 only because t=
hat has higher preference when G711 appears before CLearMode codec in the l=
ist as follows:

 m=3Daudio<puerto>  RTP/AVP 0 [8] <PT_din=E1mico> =20
 a=3Drtpmap:<PT_din=E1mico>  CLEARMODE/8000

In H.248.80 is based on draft-ietf-mmusic-sdp-capability-negotiation-12.txt=
 and uses potential and latent configuration, but that's still under discus=
sion, so you have to use those two options for now.
-Arindam  =20

-----Original Message-----
From: megaco-bounces@ietf.org [mailto:megaco-bounces@ietf.org] On Behalf Of=
 Javi Mu=F1oz
Sent: Thursday, December 01, 2011 11:50 AM
To: megaco@ietf.org
Cc: Bhattacharjee, Arindam (Arindam)
Subject: Re: [Megaco] Selection of media (m=3D) at MG

El 01/12/2011 15:22, Bhattacharjee, Arindam (Arindam) escribi=F3:
> Hi Javi,
> MG will resereve both resources and be able to decode both the codecs. No=
w if in the remote end the announcement server only uses g711 to send pkts =
then MG will decode only g711 pkts, but will send g711 pkts since remote sd=
p is g711 only.
> So in this case, phase 1:  local SDP will have both clearmode and g711 an=
d remote SDP will have only G711. Of course MG should make sure that Clearm=
ode DSP resourse is reserved for both encoder/decoder, which is normally im=
plicit in this case.

You mean that if we indicate a codec (such as "Clearmode") in the Local=20
descriptor (decoder), MG must reserve resources for decoder and encoder=20
(although that codec is not specified in the Remote descriptor).

Is that so specified by [H.248.1] or is it part of the Recommendation=20
[H.248.80]?

regards,

Javi
> In case of phase 2  both local and remote will have Clearmode with reserv=
e value =3Doff.
>
> More elaborate implementation of this scenario is under discussion now on=
 H.248.80. Albrecht will know more about the status of that document.
>
> -Arindam
>
> -----Original Message-----
> From: Javi Mu=F1oz [mailto:javi@trajano.us.es]
> Sent: Thursday, December 01, 2011 5:03 AM
> To: megaco@ietf.org
> Cc: Bhattacharjee, Arindam (Arindam)
> Subject: Re: [Megaco] Selection of media (m=3D) at MG
>
> Hello Arindam,
>
>
> El 30/11/2011 21:20, Bhattacharjee, Arindam (Arindam) escribi=F3:
>> Hi Javi,
>> + call establishment phase: H.248 Command.req for tone/announcement
>> control plus media configuration with voice codec
>>> You can do that by using reservevalue =3DON in Local control and send S=
DP offer for both G711 and ClearMode.
>>> Thus AGW should be able to encode/decode g711 and reserves resource for=
 clearmode.
> I understand you mean that I use:
>
> m=3Daudio<puerto>  RTP/AVP<PT_din=E1mico>  0 [8]
> a=3Drtpmap:<PT_din=E1mico>  CLEARMODE/8000
>
>
> But, how may we indicate to the MG that it uses G.711, and it only
> reserves resources for the CLEARMODE?
>
> Regards,
>
> Javi
>
>> + information phase: H.248 Command.req for modification of the media
>> configuration towards CLEARMODE
>>> in this phase MGC may send reservevalue =3DOFF with SDP ClearMode only,=
 releasing G711 resource.
>> -Arindam
>>
>> -----Original Message-----
>> From: megaco-bounces@ietf.org [mailto:megaco-bounces@ietf.org] On Behalf=
 Of Javi Mu=F1oz
>> Sent: Wednesday, November 30, 2011 1:31 PM
>> To: megaco@ietf.org
>> Subject: Re: [Megaco] Selection of media (m=3D) at MG
>>
>> An aditional comment,
>>
>> if, as we said, we admit the following behavior:
>>
>> + call establishment phase: H.248 Command.req for tone/announcement
>> control plus media configuration with voice codec
>> + information phase: H.248 Command.req for modification of the media
>> configuration towards CLEARMODE
>>
>>
>> The following could happen:
>>
>> 1=BA Call starts and command.req for tone/announcement is applied.
>>
>> 2=BA When MGC needs to change to the information phase, the MG responds =
it
>> does not support the CLEARMODE due to insufficient resources (MGC may
>> audit the MG before the call to check it supports CLEARMODE, but MGC can
>> not know how its resources will change during the call).
>>
>> In that case, it would not be possible to continue a call that has
>> already begun, which should not happen. The SDP description should
>> ensure to the MGC that the MG reserves the resources needed by the call
>> prior to the establishment of it.
>>
>> If this is true, it would not be valid to use the modify command between
>> the establishment and information phases.
>>
>> Regards,
>>
>> Javi
>>
>>
>> El 30/11/2011 18:44, Javi Mu=F1oz escribi=F3:
>>>> well spotted, thus just a single media configuration ('Clearmode')
>>>> would be already sufficient to emulate that ISDN bearer service
>>> However, two comments:
>>>
>>> (a) In the "call establishment phase": what must be created at the
>>> MG?: would it be necessary to create a context, or would it be enough
>>> to create only an ISDN termination in the null context (which would
>>> generate that tone/announcement, and then, MGC would apply a modify
>>> command to create the context for the information phase)?
>>>
>>> (b) I believe, the announcement do not necessarily have to be recorded
>>> in AGW, but that may come from an announcement server (I guess this
>>> would also be possible for DTMF tones). Could this justify the
>>> creation of such IP termination with voice codec G.711 in the
>>> establishment phase, or that communication with the announcement
>>> server does not belong to the ISDN call and, therefore, it should not
>>> be involved in its Megaco context?
>>>
>>> Regards,
>>>
>>>
>>>
>>>> PS
>>>> Your previous email was related to ISDN-to-SIP interworking at call
>>>> control level, a subject which is out of scope of MEGACO.
>>>> Thus, something for SIPPING, SIP-IMPLEMENTERS, ... (or TISPAN WG3
>>>> list) in my understanding.
>>>>
>>>>> -----Original Message-----
>>>>> From: Javi Mu=F1oz [mailto:javi@trajano.us.es]
>>>>> Sent: Mittwoch, 30. November 2011 18:13
>>>>> To: megaco@ietf.org
>>>>> Cc: Schwarz, Albrecht (Albrecht)
>>>>> Subject: Re: [Megaco] Selection of media (m=3D) at MG
>>>>>
>>>>> A second comment,
>>>>>
>>>>> If:
>>>>>>>        a) TGW: no impact, because tone/announcement inserted by ISD=
N
>>>>>>> local exchange (terminating Q.931); TGW needs just
>>>>> clearmode support
>>>>>
>>>>> (I agree)
>>>>>
>>>>> then, why?
>>>>>>> E.g., MGC
>>>>>>> ->     call establishment phase: IF tones/announcements THEN H.248
>>>>>>> Command.req for tone/announcement control plus media configuration
>>>>>>> with voice codec
>>>>> That "media configuration with voice codec" (G.711) would be
>>>>> done at the MeGaCo termination of the IP side of the MG, not
>>>>> at the termination of the ISDN side. If tone/announcement is
>>>>> inserted (in the UNI ISDN) by this MG, the termination of the
>>>>> IP side of the MG would not be used, so that "voice codec"
>>>>> would not be relevant (no media would be transported over the
>>>>> IP network).
>>>>>
>>>>> am I wrong?
>>>>>
>>>>> Regards,
>>>>>
>>>>> Javi
>>>>>
>>> _______________________________________________
>>> Megaco mailing list
>>> Megaco@ietf.org
>>> https://www.ietf.org/mailman/listinfo/megaco
>>>
>> _______________________________________________
>> Megaco mailing list
>> Megaco@ietf.org
>> https://www.ietf.org/mailman/listinfo/megaco
>>
>

_______________________________________________
Megaco mailing list
Megaco@ietf.org
https://www.ietf.org/mailman/listinfo/megaco

From javi@trajano.us.es  Thu Dec  1 10:42:18 2011
Return-Path: <javi@trajano.us.es>
X-Original-To: megaco@ietfa.amsl.com
Delivered-To: megaco@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 664EE11E808A for <megaco@ietfa.amsl.com>; Thu,  1 Dec 2011 10:42:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.135
X-Spam-Level: 
X-Spam-Status: No, score=-6.135 tagged_above=-999 required=5 tests=[AWL=0.164,  BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id APMeeBalCw3H for <megaco@ietfa.amsl.com>; Thu,  1 Dec 2011 10:42:18 -0800 (PST)
Received: from mail.us.es (mail.us.es [193.147.175.20]) by ietfa.amsl.com (Postfix) with ESMTP id 71BEE11E8082 for <megaco@ietf.org>; Thu,  1 Dec 2011 10:42:17 -0800 (PST)
Received: (qmail 19032 invoked from network); 1 Dec 2011 19:42:16 +0100
Received: from unknown (HELO us.es) (192.168.2.13) by us.es with SMTP; 1 Dec 2011 19:42:16 +0100
Received: (qmail 10166 invoked by uid 507); 1 Dec 2011 18:42:14 -0000
Received: from 127.0.0.1 by antivirus3 (envelope-from <javi@trajano.us.es>, uid 501) with qmail-scanner-2.08 (clamdscan: 0.97.3/14058.   Clear:RC:1(127.0.0.1):.  Processed in 0.036617 secs); 01 Dec 2011 18:42:14 -0000
Received: from unknown (HELO antivirus3) (127.0.0.1) by us.es with SMTP; 1 Dec 2011 18:42:14 -0000
Received: from 192.168.1.13 (192.168.1.13) by antivirus3 (F-Secure/fsigk_smtp/406/antivirus3); Thu, 01 Dec 2011 19:42:14 +0100 (CET)
X-Virus-Status: clean(F-Secure/fsigk_smtp/406/antivirus3)
Received: (qmail 29067 invoked from network); 1 Dec 2011 19:42:14 +0100
Received: from trajano.us.es (193.147.162.130) by us.es with AES256-SHA encrypted SMTP; 1 Dec 2011 19:42:14 +0100
Received: from [193.147.162.138] (adriano.us.es [193.147.162.138]) (authenticated bits=0) by trajano.us.es (8.13.8/8.13.8/Debian-3) with ESMTP id pB1IgD8J017464 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NOT); Thu, 1 Dec 2011 19:42:13 +0100
Message-ID: <4ED7CAA1.3020902@trajano.us.es>
Date: Thu, 01 Dec 2011 19:42:41 +0100
From: =?ISO-8859-1?Q?Javi_Mu=F1oz?= <javi@trajano.us.es>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; es-ES; rv:1.9.2.24) Gecko/20111103 Thunderbird/3.1.16
MIME-Version: 1.0
To: "megaco@ietf.org" <megaco@ietf.org>
References: <4ED518F6.4020201@trajano.us.es>	<5F7BCCF5541B7444830A2288ABBEBC962161900622@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com>	<4ED604A0.2000402@trajano.us.es>	<4ED6640A.9030508@trajano.us.es>	<5F7BCCF5541B7444830A2288ABBEBC962161900780@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com>	<4ED66B87.7050907@trajano.us.es>	<4ED6767D.7070109@trajano.us.es>	<703C56B521385C4C9091299BE82357B7EF26034C@USNAVSXCHMBSA2.ndc.alcatel-lucent.com>	<4ED750D6.9000608@trajano.us.es>	<703C56B521385C4C9091299BE82357B7EF2605BE@USNAVSXCHMBSA2.ndc.alcatel-lucent.com> <4ED7B036.4000103@trajano.us.es> <703C56B521385C4C9091299BE82357B7EF2607C5@USNAVSXCHMBSA2.ndc.alcatel-lucent.com>
In-Reply-To: <703C56B521385C4C9091299BE82357B7EF2607C5@USNAVSXCHMBSA2.ndc.alcatel-lucent.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Cc: "Bhattacharjee, Arindam \(Arindam\)" <arindam.bhattacharjee@alcatel-lucent.com>
Subject: Re: [Megaco] Selection of media (m=) at MG
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.1.12
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: Thu, 01 Dec 2011 18:42:18 -0000

Arindam,

> You can use another option: have reserve value on and use both g711 and Clearmode on both remote and local SDP and MG will send in g711 only because that has higher preference when G711 appears before CLearMode codec in the list as follows:
>
>   m=audio<puerto>   RTP/AVP 0 [8]<PT_dinámico>
>   a=rtpmap:<PT_dinámico>   CLEARMODE/8000

When the Remote descriptor has several audio codecs in the line "m=":

  m=audio<puerto>   RTP/AVP 0 [8]<PT_dinámico>   


I understand that:

1º First codec in the line is used if it is possible.

2º In case that codec may not be used (for an error, for example), the 
second codec would be tried (I understand this is the reaseon why the 
Remote descriptor may have several audio codecs in the same line "m=).


If it is so, and we use:

  m=audio<puerto>   RTP/AVP 0 [8]<PT_dinámico>   


What would happen if when MG needs to send the tone/ann., the codecs "0" 
and "8" may not be used?. MG would try to send the tone/ann. to the 
terminal using CLEARMODE, when terminal is not ready to receive that.

Javi

From Raju.Makaraju@alcatel-lucent.com  Thu Dec  1 14:15:16 2011
Return-Path: <Raju.Makaraju@alcatel-lucent.com>
X-Original-To: megaco@ietfa.amsl.com
Delivered-To: megaco@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 99C5221F934F for <megaco@ietfa.amsl.com>; Thu,  1 Dec 2011 14:15:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.299
X-Spam-Level: 
X-Spam-Status: No, score=-6.299 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id caMjUazj+ZQq for <megaco@ietfa.amsl.com>; Thu,  1 Dec 2011 14:15:16 -0800 (PST)
Received: from ihemail4.lucent.com (ihemail4.lucent.com [135.245.0.39]) by ietfa.amsl.com (Postfix) with ESMTP id F184C21F934D for <megaco@ietf.org>; Thu,  1 Dec 2011 14:15:15 -0800 (PST)
Received: from usnavsmail2.ndc.alcatel-lucent.com (usnavsmail2.ndc.alcatel-lucent.com [135.3.39.10]) by ihemail4.lucent.com (8.13.8/IER-o) with ESMTP id pB1MFCXB018786 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 1 Dec 2011 16:15:12 -0600 (CST)
Received: from USNAVSXCHHUB03.ndc.alcatel-lucent.com (usnavsxchhub03.ndc.alcatel-lucent.com [135.3.39.112]) by usnavsmail2.ndc.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id pB1MFBWJ011909 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Thu, 1 Dec 2011 16:15:12 -0600
Received: from USNAVSXCHMBSD3.ndc.alcatel-lucent.com ([135.3.39.154]) by USNAVSXCHHUB03.ndc.alcatel-lucent.com ([135.3.39.112]) with mapi; Thu, 1 Dec 2011 16:15:11 -0600
From: "Makaraju, Maridi Raju (Raju)" <Raju.Makaraju@alcatel-lucent.com>
To: =?iso-8859-1?Q?Javi_Mu=F1oz?= <javi@trajano.us.es>, "megaco@ietf.org" <megaco@ietf.org>
Date: Thu, 1 Dec 2011 16:15:04 -0600
Thread-Topic: [Megaco] Selection of media (m=) at MG
Thread-Index: AcywWPWnJqWf1TFsSgq9ik7YhC41IgAGtZSg
Message-ID: <31939CE9629A7F46885A9F97CEA9BF577BFE78B4@USNAVSXCHMBSD3.ndc.alcatel-lucent.com>
References: <4ED518F6.4020201@trajano.us.es> <5F7BCCF5541B7444830A2288ABBEBC962161900622@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com> <4ED604A0.2000402@trajano.us.es>	<4ED6640A.9030508@trajano.us.es> <5F7BCCF5541B7444830A2288ABBEBC962161900780@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com> <4ED66B87.7050907@trajano.us.es>	<4ED6767D.7070109@trajano.us.es> <703C56B521385C4C9091299BE82357B7EF26034C@USNAVSXCHMBSA2.ndc.alcatel-lucent.com> <4ED750D6.9000608@trajano.us.es> <703C56B521385C4C9091299BE82357B7EF2605BE@USNAVSXCHMBSA2.ndc.alcatel-lucent.com> <4ED7B036.4000103@trajano.us.es> <703C56B521385C4C9091299BE82357B7EF2607C5@USNAVSXCHMBSA2.ndc.alcatel-lucent.com> <4ED7CAA1.3020902@trajano.us.es>
In-Reply-To: <4ED7CAA1.3020902@trajano.us.es>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.39
X-Scanned-By: MIMEDefang 2.64 on 135.3.39.10
Cc: "Bhattacharjee, Arindam \(Arindam\)" <arindam.bhattacharjee@alcatel-lucent.com>
Subject: Re: [Megaco] Selection of media (m=) at MG
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.1.12
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: Thu, 01 Dec 2011 22:15:16 -0000

=20
> 2=BA In case that codec may not be used (for an error, for=20
> example), the=20
> second codec would be tried (I understand this is the reaseon why the=20
> Remote descriptor may have several audio codecs in the same line "m=3D).
>=20
>=20
> If it is so, and we use:
>=20
>   m=3Daudio<puerto>   RTP/AVP 0 [8]<PT_din=E1mico>  =20
>=20
>=20
> What would happen if when MG needs to send the tone/annc., the=20
> codecs "0"=20
> and "8" may not be used?. MG would try to send the tone/annc. to the=20
> terminal using CLEARMODE, when terminal is not ready to receive that.

The codec used on IP term side do not impact the data format sent on ISDN t=
erm.
(but it impacts the content due to use of lossy or lossless codec on IP).

CLEARMODE only tells the GW to turn off any encoding/decoding/echo-cancella=
tion/DTMF etc.
and send the received data as is on either side.=20

In fact, when a signal (tone/annc) is played on one termination (signal goi=
ng outside of the context),
the termination is temporarily "disconnected oneway" (so it won't receive a=
ny data, but can send) from=20
the other terminations (as if the termination has "oneway" topology to othe=
rs).

-Raju


> -----Original Message-----
> From: megaco-bounces@ietf.org=20
> [mailto:megaco-bounces@ietf.org] On Behalf Of Javi Mu=F1oz
> Sent: Thursday, December 01, 2011 12:43 PM
> To: megaco@ietf.org
> Cc: Bhattacharjee, Arindam (Arindam)
> Subject: Re: [Megaco] Selection of media (m=3D) at MG
>=20
> Arindam,
>=20
> > You can use another option: have reserve value on and use=20
> both g711 and Clearmode on both remote and local SDP and MG=20
> will send in g711 only because that has higher preference=20
> when G711 appears before CLearMode codec in the list as follows:
> >
> >   m=3Daudio<puerto>   RTP/AVP 0 [8]<PT_din=E1mico>
> >   a=3Drtpmap:<PT_din=E1mico>   CLEARMODE/8000
>=20
> When the Remote descriptor has several audio codecs in the line "m=3D":
>=20
>   m=3Daudio<puerto>   RTP/AVP 0 [8]<PT_din=E1mico>  =20
>=20
>=20
> I understand that:
>=20
> 1=BA First codec in the line is used if it is possible.
>=20
> 2=BA In case that codec may not be used (for an error, for=20
> example), the=20
> second codec would be tried (I understand this is the reaseon why the=20
> Remote descriptor may have several audio codecs in the same line "m=3D).
>=20
>=20
> If it is so, and we use:
>=20
>   m=3Daudio<puerto>   RTP/AVP 0 [8]<PT_din=E1mico>  =20
>=20
>=20
> What would happen if when MG needs to send the tone/ann., the=20
> codecs "0"=20
> and "8" may not be used?. MG would try to send the tone/ann. to the=20
> terminal using CLEARMODE, when terminal is not ready to receive that.
>=20
> Javi
> _______________________________________________
> Megaco mailing list
> Megaco@ietf.org
> https://www.ietf.org/mailman/listinfo/megaco
> =

From albrecht.schwarz@alcatel-lucent.com  Fri Dec  2 01:50:21 2011
Return-Path: <albrecht.schwarz@alcatel-lucent.com>
X-Original-To: megaco@ietfa.amsl.com
Delivered-To: megaco@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 25C6E21F9946 for <megaco@ietfa.amsl.com>; Fri,  2 Dec 2011 01:50:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.949
X-Spam-Level: 
X-Spam-Status: No, score=-5.949 tagged_above=-999 required=5 tests=[AWL=0.300,  BAYES_00=-2.599, HELO_EQ_FR=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LAEkUhdxq5Qb for <megaco@ietfa.amsl.com>; Fri,  2 Dec 2011 01:50:20 -0800 (PST)
Received: from smail3.alcatel.fr (smail3.alcatel.fr [64.208.49.56]) by ietfa.amsl.com (Postfix) with ESMTP id 6033621F93A1 for <megaco@ietf.org>; Fri,  2 Dec 2011 01:50:20 -0800 (PST)
Received: from FRMRSSXCHHUB01.dc-m.alcatel-lucent.com (FRMRSSXCHHUB01.dc-m.alcatel-lucent.com [135.120.45.61]) by smail3.alcatel.fr (8.14.3/8.14.3/ICT) with ESMTP id pB29kh0V029822 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Fri, 2 Dec 2011 10:50:08 +0100
Received: from FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com ([135.120.45.52]) by FRMRSSXCHHUB01.dc-m.alcatel-lucent.com ([135.120.45.61]) with mapi; Fri, 2 Dec 2011 10:49:56 +0100
From: "Schwarz, Albrecht (Albrecht)" <albrecht.schwarz@alcatel-lucent.com>
To: CHATRAS Bruno RD-CORE-ISS <bruno.chatras@orange-ft.com>
Date: Fri, 2 Dec 2011 10:49:54 +0100
Thread-Topic: H.248.64 vs ForCES vs OpenFlow; FW: I-D Action: draft-wang-forces-compare-openflow-forces-00.txt
Thread-Index: Acyw0b1mZgB+i5MASuuh3y0fTiEWmQABaSFg
Message-ID: <5F7BCCF5541B7444830A2288ABBEBC9621619009A9@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com>
Accept-Language: de-DE, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: de-DE, en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.69 on 155.132.188.83
Cc: "megaco@ietf.org" <megaco@ietf.org>
Subject: [Megaco] H.248.64 vs ForCES vs OpenFlow; FW: I-D Action: draft-wang-forces-compare-openflow-forces-00.txt
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.1.12
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: Fri, 02 Dec 2011 09:50:21 -0000

Bruno, fyi, a first analysis appears, comparison could be extended for H.24=
8.64 ...
=20

-----Original Message-----
From: i-d-announce-bounces@ietf.org [mailto:i-d-announce-bounces@ietf.org] =
On Behalf Of internet-drafts@ietf.org
Sent: Freitag, 2. Dezember 2011 10:07
To: i-d-announce@ietf.org
Subject: I-D Action: draft-wang-forces-compare-openflow-forces-00.txt


A New Internet-Draft is available from the on-line Internet-Drafts director=
ies.

	Title           : Analysis of Comparisons between OpenFlow and ForCES
	Author(s)       : Zhiliang Wang
                          Tina Tsou
                          Jing Huang
                          Xingang Shi
                          Xia Yin
	Filename        : draft-wang-forces-compare-openflow-forces-00.txt
	Pages           : 12
	Date            : 2011-12-02

   While both ForCES and OpenFlow follow the basic idea of separations
   of forwarding plane and control plane in network elements, they are
   technically very different. This document analyzes the differences
   between OpenFlow and ForCES technically from the aspects of goals,
   architecture, forwarding model and protocol interface. The two
   techniques can learn much from each other in their standardization
   process.


A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-wang-forces-compare-openflow-forc=
es-00.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

This Internet-Draft can be retrieved at:
ftp://ftp.ietf.org/internet-drafts/draft-wang-forces-compare-openflow-force=
s-00.txt

_______________________________________________
I-D-Announce mailing list
I-D-Announce@ietf.org
https://www.ietf.org/mailman/listinfo/i-d-announce
Internet-Draft directories: http://www.ietf.org/shadow.html or ftp://ftp.ie=
tf.org/ietf/1shadow-sites.txt

From bruno.chatras@orange.com  Fri Dec  2 02:27:33 2011
Return-Path: <bruno.chatras@orange.com>
X-Original-To: megaco@ietfa.amsl.com
Delivered-To: megaco@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 106DA21F9938 for <megaco@ietfa.amsl.com>; Fri,  2 Dec 2011 02:27:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.249
X-Spam-Level: 
X-Spam-Status: No, score=-6.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_FR=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aF+G8VUHp+PH for <megaco@ietfa.amsl.com>; Fri,  2 Dec 2011 02:27:32 -0800 (PST)
Received: from p-mail1.rd.francetelecom.com (p-mail1.rd.francetelecom.com [195.101.245.15]) by ietfa.amsl.com (Postfix) with ESMTP id 388F221F9377 for <megaco@ietf.org>; Fri,  2 Dec 2011 02:27:32 -0800 (PST)
Received: from p-mail1.rd.francetelecom.com (localhost.localdomain [127.0.0.1]) by localhost (Postfix) with SMTP id 02F0C8B8004; Fri,  2 Dec 2011 11:28:36 +0100 (CET)
Received: from ftrdsmtp2.rd.francetelecom.fr (unknown [10.192.128.47]) by p-mail1.rd.francetelecom.com (Postfix) with ESMTP id ED9038B8001; Fri,  2 Dec 2011 11:28:35 +0100 (CET)
Received: from ftrdmel0.rd.francetelecom.fr ([10.192.128.56]) by ftrdsmtp2.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.4675);  Fri, 2 Dec 2011 11:27:29 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Fri, 2 Dec 2011 11:27:28 +0100
Message-ID: <9ECCF01B52E7AB408A7EB85352642141038D4128@ftrdmel0.rd.francetelecom.fr>
In-Reply-To: <5F7BCCF5541B7444830A2288ABBEBC9621619009A9@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Megaco] H.248.64 vs ForCES vs OpenFlow; FW: I-D Action: draft-wang-forces-compare-openflow-forces-00.txt
Thread-Index: Acyw0b1mZgB+i5MASuuh3y0fTiEWmQABaSFgAAEimXA=
References: <5F7BCCF5541B7444830A2288ABBEBC9621619009A9@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com>
From: <bruno.chatras@orange.com>
To: <albrecht.schwarz@alcatel-lucent.com>
X-OriginalArrivalTime: 02 Dec 2011 10:27:29.0778 (UTC) FILETIME=[FE9B3520:01CCB0DC]
Cc: megaco@ietf.org
Subject: Re: [Megaco] H.248.64 vs ForCES vs OpenFlow; FW: I-D Action: draft-wang-forces-compare-openflow-forces-00.txt
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.1.12
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: Fri, 02 Dec 2011 10:27:33 -0000

Yes indeed it would be useful to draft something about H.248 vs. =
OF/ForCES

BTW, reading H.248.64 once more, a new question stroked me! H.248.64 =
specifies that an incoming packet whose DA does not match the local =
space is forwarded to an IPR context. I believe that there are cases =
where the B2BIH mode can be used although the DA does not match the =
local space. The configuration I have in mind is one where the MGC =
creates a context with two terminations and set explicitly the LD and RD =
on both sides (i.e. no wildcard).

BC

> -----Message d'origine-----
> De=A0: megaco-bounces@ietf.org [mailto:megaco-bounces@ietf.org] De la
> part de Schwarz, Albrecht (Albrecht)
> Envoy=E9=A0: vendredi 2 d=E9cembre 2011 10:50
> =C0=A0: CHATRAS Bruno RD-CORE-ISS
> Cc=A0: megaco@ietf.org
> Objet=A0: [Megaco] H.248.64 vs ForCES vs OpenFlow; FW: I-D Action: =
draft-
> wang-forces-compare-openflow-forces-00.txt
>=20
> Bruno, fyi, a first analysis appears, comparison could be extended for
> H.248.64 ...
>=20
>=20
> -----Original Message-----
> From: i-d-announce-bounces@ietf.org [mailto:i-d-announce-
> bounces@ietf.org] On Behalf Of internet-drafts@ietf.org
> Sent: Freitag, 2. Dezember 2011 10:07
> To: i-d-announce@ietf.org
> Subject: I-D Action: draft-wang-forces-compare-openflow-forces-00.txt
>=20
>=20
> A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
>=20
> 	Title           : Analysis of Comparisons between OpenFlow and
> ForCES
> 	Author(s)       : Zhiliang Wang
>                           Tina Tsou
>                           Jing Huang
>                           Xingang Shi
>                           Xia Yin
> 	Filename        : draft-wang-forces-compare-openflow-forces-
> 00.txt
> 	Pages           : 12
> 	Date            : 2011-12-02
>=20
>    While both ForCES and OpenFlow follow the basic idea of separations
>    of forwarding plane and control plane in network elements, they are
>    technically very different. This document analyzes the differences
>    between OpenFlow and ForCES technically from the aspects of goals,
>    architecture, forwarding model and protocol interface. The two
>    techniques can learn much from each other in their standardization
>    process.
>=20
>=20
> A URL for this Internet-Draft is:
> =
http://www.ietf.org/internet-drafts/draft-wang-forces-compare-openflow-
> forces-00.txt
>=20
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>=20
> This Internet-Draft can be retrieved at:
> ftp://ftp.ietf.org/internet-drafts/draft-wang-forces-compare-openflow-
> forces-00.txt
>=20
> _______________________________________________
> I-D-Announce mailing list
> I-D-Announce@ietf.org
> https://www.ietf.org/mailman/listinfo/i-d-announce
> Internet-Draft directories: http://www.ietf.org/shadow.html or
> ftp://ftp.ietf.org/ietf/1shadow-sites.txt
> _______________________________________________
> Megaco mailing list
> Megaco@ietf.org
> https://www.ietf.org/mailman/listinfo/megaco

From javi@trajano.us.es  Fri Dec  2 04:09:01 2011
Return-Path: <javi@trajano.us.es>
X-Original-To: megaco@ietfa.amsl.com
Delivered-To: megaco@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 44BEC21F991A for <megaco@ietfa.amsl.com>; Fri,  2 Dec 2011 04:09:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.849
X-Spam-Level: 
X-Spam-Status: No, score=-5.849 tagged_above=-999 required=5 tests=[AWL=-0.150, BAYES_00=-2.599, J_CHICKENPOX_73=0.6, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BdjWcFukNB4a for <megaco@ietfa.amsl.com>; Fri,  2 Dec 2011 04:09:00 -0800 (PST)
Received: from mail.us.es (mail.us.es [193.147.175.20]) by ietfa.amsl.com (Postfix) with ESMTP id 3039421F9924 for <megaco@ietf.org>; Fri,  2 Dec 2011 04:08:58 -0800 (PST)
Received: (qmail 21231 invoked from network); 2 Dec 2011 13:08:57 +0100
Received: from unknown (HELO us.es) (192.168.2.12) by us.es with SMTP; 2 Dec 2011 13:08:57 +0100
Received: (qmail 16250 invoked by uid 507); 2 Dec 2011 12:08:55 -0000
Received: from 127.0.0.1 by antivirus2 (envelope-from <javi@trajano.us.es>, uid 501) with qmail-scanner-2.08 (clamdscan: 0.97.3/14062.   Clear:RC:1(127.0.0.1):.  Processed in 0.043463 secs); 02 Dec 2011 12:08:55 -0000
Received: from unknown (HELO antivirus2) (127.0.0.1) by us.es with SMTP; 2 Dec 2011 12:08:55 -0000
Received: from 192.168.1.13 (192.168.1.13) by antivirus2 (F-Secure/fsigk_smtp/406/antivirus2); Fri, 02 Dec 2011 13:08:55 +0100 (CET)
X-Virus-Status: clean(F-Secure/fsigk_smtp/406/antivirus2)
Received: (qmail 17627 invoked from network); 2 Dec 2011 13:08:55 +0100
Received: from trajano.us.es (193.147.162.130) by us.es with AES256-SHA encrypted SMTP; 2 Dec 2011 13:08:55 +0100
Received: from [193.147.162.138] (adriano.us.es [193.147.162.138]) (authenticated bits=0) by trajano.us.es (8.13.8/8.13.8/Debian-3) with ESMTP id pB2C8sFo031361 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NOT); Fri, 2 Dec 2011 13:08:54 +0100
Message-ID: <4ED8BFD6.6040306@trajano.us.es>
Date: Fri, 02 Dec 2011 13:08:54 +0100
From: =?ISO-8859-1?Q?Javi_Mu=F1oz?= <javi@trajano.us.es>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; es-ES; rv:1.9.2.24) Gecko/20111103 Thunderbird/3.1.16
MIME-Version: 1.0
To: "megaco@ietf.org" <megaco@ietf.org>
References: <4ED518F6.4020201@trajano.us.es>	<5F7BCCF5541B7444830A2288ABBEBC962161900622@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com> <4ED604A0.2000402@trajano.us.es> <4ED6640A.9030508@trajano.us.es> <5F7BCCF5541B7444830A2288ABBEBC962161900780@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com> <4ED66B87.7050907@trajano.us.es>
In-Reply-To: <4ED66B87.7050907@trajano.us.es>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Subject: Re: [Megaco] Selection of media (m=) at MG
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.1.12
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: Fri, 02 Dec 2011 12:09:01 -0000

Albrecht,

I complete my comment "(b)":

[ETSI TS 183 002 Clause 7.1.4]
Access Gateways may be able to store recorded announcements and shall 
support the generic announcement package. Generic Announcement (ITU-T 
Rec. H.248.7 [18]): mandatory if local announcements are available.
When the announcement to be delivered is not available in the gateway 
and cannot be autonomously retrieved by the gateway from a remote 
repository, the MGC shall initiate a connection to an external 
announcement machine, by temporarily adding a termination into the 
context. Instructions to play announcements are sent directly from the 
MGC to the server. The announcement server may itself be implemented as 
an MG, controlled using the H.248 protocol. However, this interface is 
outside the scope of the present document. In an originating MG, the 
context topology and the termination modes shall be configured in such a 
way that in-band information can be received from the remote side before 
the called party's answer. This setting shall occur not later than the 
receipt of the ACO message (or an equivalent message from another 
signalling protocol that ISUP).

Regards,

Javi
>
>> well spotted, thus just a single media configuration ('Clearmode') 
>> would be already sufficient to emulate that ISDN bearer service
> However, two comments:
>
> (a) In the "call establishment phase": what must be created at the 
> MG?: would it be necessary to create a context, or would it be enough 
> to create only an ISDN termination in the null context (which would 
> generate that tone/announcement, and then, MGC would apply a modify 
> command to create the context for the information phase)?
>
> (b) I believe, the announcement do not necessarily have to be recorded 
> in AGW, but that may come from an announcement server (I guess this 
> would also be possible for DTMF tones). Could this justify the 
> creation of such IP termination with voice codec G.711 in the 
> establishment phase, or that communication with the announcement 
> server does not belong to the ISDN call and, therefore, it should not 
> be involved in its Megaco context?
>
> Regards,
>
>
>
>> PS
>> Your previous email was related to ISDN-to-SIP interworking at call 
>> control level, a subject which is out of scope of MEGACO.
>> Thus, something for SIPPING, SIP-IMPLEMENTERS, ... (or TISPAN WG3 
>> list) in my understanding.
>>
>>> -----Original Message-----
>>> From: Javi Muñoz [mailto:javi@trajano.us.es]
>>> Sent: Mittwoch, 30. November 2011 18:13
>>> To: megaco@ietf.org
>>> Cc: Schwarz, Albrecht (Albrecht)
>>> Subject: Re: [Megaco] Selection of media (m=) at MG
>>>
>>> A second comment,
>>>
>>> If:
>>>>>      a) TGW: no impact, because tone/announcement inserted by ISDN
>>>>> local exchange (terminating Q.931); TGW needs just
>>> clearmode support
>>>
>>> (I agree)
>>>
>>> then, why?
>>>>> E.g., MGC
>>>>> ->   call establishment phase: IF tones/announcements THEN H.248
>>>>> Command.req for tone/announcement control plus media configuration
>>>>> with voice codec
>>> That "media configuration with voice codec" (G.711) would be
>>> done at the MeGaCo termination of the IP side of the MG, not
>>> at the termination of the ISDN side. If tone/announcement is
>>> inserted (in the UNI ISDN) by this MG, the termination of the
>>> IP side of the MG would not be used, so that "voice codec"
>>> would not be relevant (no media would be transported over the
>>> IP network).
>>>
>>> am I wrong?
>>>
>>> Regards,
>>>
>>> Javi
>>>
>


From javi@trajano.us.es  Fri Dec  2 04:17:49 2011
Return-Path: <javi@trajano.us.es>
X-Original-To: megaco@ietfa.amsl.com
Delivered-To: megaco@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3396921F993A for <megaco@ietfa.amsl.com>; Fri,  2 Dec 2011 04:17:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.137
X-Spam-Level: 
X-Spam-Status: No, score=-6.137 tagged_above=-999 required=5 tests=[AWL=0.162,  BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id o+D-kT4DbEFC for <megaco@ietfa.amsl.com>; Fri,  2 Dec 2011 04:17:48 -0800 (PST)
Received: from mail.us.es (mail.us.es [193.147.175.20]) by ietfa.amsl.com (Postfix) with ESMTP id 338BC21F9934 for <megaco@ietf.org>; Fri,  2 Dec 2011 04:17:48 -0800 (PST)
Received: (qmail 661 invoked from network); 2 Dec 2011 13:17:47 +0100
Received: from unknown (HELO us.es) (192.168.2.11) by us.es with SMTP; 2 Dec 2011 13:17:47 +0100
Received: (qmail 11291 invoked by uid 507); 2 Dec 2011 12:17:46 -0000
Received: from 127.0.0.1 by antivirus1 (envelope-from <javi@trajano.us.es>, uid 501) with qmail-scanner-2.08 (clamdscan: 0.97.3/14062.   Clear:RC:1(127.0.0.1):.  Processed in 0.031115 secs); 02 Dec 2011 12:17:46 -0000
Received: from unknown (HELO antivirus1) (127.0.0.1) by us.es with SMTP; 2 Dec 2011 12:17:46 -0000
Received: from 192.168.1.13 (192.168.1.13) by antivirus1 (F-Secure/fsigk_smtp/406/antivirus1); Fri, 02 Dec 2011 13:17:46 +0100 (CET)
X-Virus-Status: clean(F-Secure/fsigk_smtp/406/antivirus1)
Received: (qmail 10144 invoked from network); 2 Dec 2011 13:17:46 +0100
Received: from trajano.us.es (193.147.162.130) by us.es with AES256-SHA encrypted SMTP; 2 Dec 2011 13:17:46 +0100
Received: from [193.147.162.138] (adriano.us.es [193.147.162.138]) (authenticated bits=0) by trajano.us.es (8.13.8/8.13.8/Debian-3) with ESMTP id pB2CHjFJ031576 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NOT) for <megaco@ietf.org>; Fri, 2 Dec 2011 13:17:45 +0100
Message-ID: <4ED8C1EA.2050609@trajano.us.es>
Date: Fri, 02 Dec 2011 13:17:46 +0100
From: =?ISO-8859-1?Q?Javi_Mu=F1oz?= <javi@trajano.us.es>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; es-ES; rv:1.9.2.24) Gecko/20111103 Thunderbird/3.1.16
MIME-Version: 1.0
To: "megaco@ietf.org" <megaco@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: [Megaco] One Ephemeral termination in a context
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.1.12
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: Fri, 02 Dec 2011 12:17:49 -0000

If we have a context with 2 ephemeral terminations:

T1 -- * -- T2

and we applied "subtract(T2)", What happens with the T1 termination?, is 
it also subtracted or it is manteined alone in the context?

Regards,

Javi

From ronald.behar_aldana@alcatel-lucent.com  Fri Dec  2 04:27:06 2011
Return-Path: <ronald.behar_aldana@alcatel-lucent.com>
X-Original-To: megaco@ietfa.amsl.com
Delivered-To: megaco@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4CD0421F9930 for <megaco@ietfa.amsl.com>; Fri,  2 Dec 2011 04:27:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.949
X-Spam-Level: 
X-Spam-Status: No, score=-5.949 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_FR=0.35, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZJ6SRjWHDriF for <megaco@ietfa.amsl.com>; Fri,  2 Dec 2011 04:27:05 -0800 (PST)
Received: from smail6.alcatel.fr (smail6.alcatel.fr [62.23.212.42]) by ietfa.amsl.com (Postfix) with ESMTP id 7A9A121F992C for <megaco@ietf.org>; Fri,  2 Dec 2011 04:27:04 -0800 (PST)
Received: from FRMRSSXCHHUB02.dc-m.alcatel-lucent.com (FRMRSSXCHHUB02.dc-m.alcatel-lucent.com [135.120.45.62]) by smail6.alcatel.fr (8.14.3/8.14.3/ICT) with ESMTP id pB2CQ32Q026689 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Fri, 2 Dec 2011 13:27:02 +0100
Received: from FRMRSSXCHMBSB3.dc-m.alcatel-lucent.com ([135.120.45.41]) by FRMRSSXCHHUB02.dc-m.alcatel-lucent.com ([135.120.45.62]) with mapi; Fri, 2 Dec 2011 13:26:42 +0100
From: "Behar Aldana, Ronald (Ronald)" <ronald.behar_aldana@alcatel-lucent.com>
To: =?iso-8859-1?Q?Javi_Mu=F1oz?= <javi@trajano.us.es>, "megaco@ietf.org" <megaco@ietf.org>
Date: Fri, 2 Dec 2011 13:26:41 +0100
Thread-Topic: [Megaco] One Ephemeral termination in a context
Thread-Index: Acyw7HEDWs5y3wLnQ9SjFJfMmrOnIAAAQsgw
Message-ID: <F1BF3BAC885159479F9D8F6165BD53791B28F3F1@FRMRSSXCHMBSB3.dc-m.alcatel-lucent.com>
References: <4ED8C1EA.2050609@trajano.us.es>
In-Reply-To: <4ED8C1EA.2050609@trajano.us.es>
Accept-Language: es-ES, en-US
Content-Language: es-ES
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: es-ES, en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.69 on 155.132.188.84
Subject: Re: [Megaco] One Ephemeral termination in a context
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.1.12
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: Fri, 02 Dec 2011 12:27:06 -0000

The termination remains in the context until it is subtracted, so T1 must r=
emain in the context. To remove all terminations from a context you must su=
btract with eh wildcard termination "*".

Ronald Behar Aldana
Trial Delivery, Lead Technical Project Manager
Central American & Caribbean

-----Mensaje original-----
De: megaco-bounces@ietf.org [mailto:megaco-bounces@ietf.org] En nombre de J=
avi Mu=F1oz
Enviado el: viernes, 02 de diciembre de 2011 13:18
Para: megaco@ietf.org
Asunto: [Megaco] One Ephemeral termination in a context

If we have a context with 2 ephemeral terminations:

T1 -- * -- T2

and we applied "subtract(T2)", What happens with the T1 termination?, is=20
it also subtracted or it is manteined alone in the context?

Regards,

Javi
_______________________________________________
Megaco mailing list
Megaco@ietf.org
https://www.ietf.org/mailman/listinfo/megaco

From bill.wu@huawei.com  Thu Dec  1 17:54:55 2011
Return-Path: <bill.wu@huawei.com>
X-Original-To: megaco@ietfa.amsl.com
Delivered-To: megaco@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A11201F0C5F; Thu,  1 Dec 2011 17:54:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.137
X-Spam-Level: 
X-Spam-Status: No, score=-6.137 tagged_above=-999 required=5 tests=[AWL=-0.138, BAYES_00=-2.599, J_CHICKENPOX_14=0.6, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PrgrVu4hrOVP; Thu,  1 Dec 2011 17:54:54 -0800 (PST)
Received: from szxga04-in.huawei.com (szxga04-in.huawei.com [119.145.14.67]) by ietfa.amsl.com (Postfix) with ESMTP id D14471F0C5E; Thu,  1 Dec 2011 17:54:53 -0800 (PST)
Received: from huawei.com (szxga04-in [172.24.2.12]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LVJ00ARRZZAG9@szxga04-in.huawei.com>; Fri, 02 Dec 2011 09:54:46 +0800 (CST)
Received: from szxrg01-dlp.huawei.com ([172.24.2.119]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LVJ00I4TZZ98A@szxga04-in.huawei.com>; Fri, 02 Dec 2011 09:54:45 +0800 (CST)
Received: from szxeml205-edg.china.huawei.com ([172.24.2.119]) by szxrg01-dlp.huawei.com (MOS 4.1.9-GA)	with ESMTP id AFM49517; Fri, 02 Dec 2011 09:54:43 +0800
Received: from SZXEML420-HUB.china.huawei.com (10.82.67.159) by szxeml205-edg.china.huawei.com (172.24.2.57) with Microsoft SMTP Server (TLS) id 14.1.323.3; Fri, 02 Dec 2011 09:54:38 +0800
Received: from w53375q (10.138.41.130) by szxeml420-hub.china.huawei.com (10.82.67.159) with Microsoft SMTP Server (TLS) id 14.1.323.3; Fri, 02 Dec 2011 09:54:34 +0800
Date: Fri, 02 Dec 2011 09:54:33 +0800
From: Qin Wu <bill.wu@huawei.com>
X-Originating-IP: [10.138.41.130]
To: "Schwarz, Albrecht (Albrecht)" <albrecht.schwarz@alcatel-lucent.com>, avt@ietf.org
Message-id: <9FF9B04A84E64AD7ABCCC4F2ACC1E19A@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.6109
X-Mailer: Microsoft Outlook Express 6.00.2900.5931
Content-type: text/plain; charset=iso-8859-1
Content-transfer-encoding: 7BIT
X-Priority: 3
X-MSMail-priority: Normal
X-CFilter-Loop: Reflected
References: <20111129075613.12419.4377.idtracker@ietfa.amsl.com> <5F7BCCF5541B7444830A2288ABBEBC96216190051A@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com> <EAC481B4D8034C38AC54E1217F8D875D@china.huawei.com> <5F7BCCF5541B7444830A2288ABBEBC96216190077F@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com> <B527BAFA038842A8939A8C2D558074CD@china.huawei.com> <5F7BCCF5541B7444830A2288ABBEBC962161900908@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com>
X-Mailman-Approved-At: Fri, 02 Dec 2011 09:18:03 -0800
Cc: megaco@ietf.org
Subject: Re: [Megaco] [AVTCORE] Types of monitoring architectures; RE:  I-D Action: draft-ietf-avtcore-monarch-08.txt
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.1.12
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: Fri, 02 Dec 2011 01:54:55 -0000

Hi, Albrecht:
No offence, I am not really convinced with your proposal on physical monitoring architecture.
 my counterquestion is what does physical monitoring architecture looks like in your mind?
How many components do we have in such physical monitroing architecture? what are they?
Take IMS network architecture as a example, they may have P-CSCF,S-CSCF, SIP PBX, SBC,
why do you believe monitor described in draft-ietf-avtcore-monarch is mapped into P-CSCF,
S-CSCF, SBC, Media Gateway, Media Gateway Controller should be in the scope of IETF RTP 
monitoring archtiecture draft?

Monitor described in  draft-ietf-avtcore-monarch is well defined in the section 3 of RFC3550 as follows:
"

   Monitor: An application that receives RTCP packets sent by
      participants in an RTP session, in particular the reception
      reports, and estimates the current quality of service for
      distribution monitoring, fault diagnosis and long-term statistics.
      The monitor function is likely to be built into the application(s)
      participating in the session, but may also be a separate
      application that does not otherwise participate and does not send
      or receive the RTP data packets (since they are on a separate
      port).  These are called third-party monitors.  It is also
      acceptable for a third-party monitor to receive the RTP data
      packets but not send RTCP packets or otherwise be counted in the
      session.

"
Isn't how to implent monitor into IMS netowork archtiecture a implentation specific issue?
If this issue are really interesting, isn't it a good idea to produce another new document to talk about this?
One good example for this motivation is this draft I like to share with you:
http://tools.ietf.org/html/draft-kaplan-dispatch-b2bua-taxonomy-00#section-4.6

Regards!
-Qin
----- Original Message ----- 
From: "Schwarz, Albrecht (Albrecht)" <albrecht.schwarz@alcatel-lucent.com>
To: "Qin Wu" <bill.wu@huawei.com>; <avt@ietf.org>
Cc: <megaco@ietf.org>
Sent: Friday, December 02, 2011 12:20 AM
Subject: RE: [AVTCORE] Types of monitoring architectures; RE: I-D Action: draft-ietf-avtcore-monarch-08.txt


My replies below ...
-Albrecht 

> -----Original Message-----
> From: Qin Wu [mailto:bill.wu@huawei.com] 
> Sent: Donnerstag, 1. Dezember 2011 02:42
> To: Schwarz, Albrecht (Albrecht); avt@ietf.org
> Cc: megaco@ietf.org
> Subject: Re: [AVTCORE] Types of monitoring architectures; RE: 
> I-D Action: draft-ietf-avtcore-monarch-08.txt
> 
> Hi,
> ----- Original Message -----
> From: "Schwarz, Albrecht (Albrecht)" 
> <albrecht.schwarz@alcatel-lucent.com>
> To: "Qin Wu" <bill.wu@huawei.com>; <avt@ietf.org>
> Cc: <megaco@ietf.org>
> Sent: Thursday, December 01, 2011 1:24 AM
> Subject: RE: [AVTCORE] Types of monitoring architectures; RE: 
> I-D Action: draft-ietf-avtcore-monarch-08.txt
> 
> 
> My replies below inline,
> Albrecht 
> 
> > -----Original Message-----
> > From: Qin Wu [mailto:bill.wu@huawei.com] 
> > Sent: Mittwoch, 30. November 2011 04:51
> > To: Schwarz, Albrecht (Albrecht); avt@ietf.org
> > Cc: megaco@ietf.org
> > Subject: Re: [AVTCORE] Types of monitoring architectures; RE: 
> > I-D Action: draft-ietf-avtcore-monarch-08.txt
> > 
> > Hi,
> > ----- Original Message -----
> > From: "Schwarz, Albrecht (Albrecht)" 
> > <albrecht.schwarz@alcatel-lucent.com>
> > To: <avt@ietf.org>
> > Cc: <megaco@ietf.org>
> > Sent: Tuesday, November 29, 2011 7:32 PM
> > Subject: [AVTCORE] Types of monitoring architectures; RE: I-D 
> > Action: draft-ietf-avtcore-monarch-08.txt
> > 
> > 
> > > Dear All,
> > > 
> > > there are different types of monitoring architectures, 
> > particularily from perspective of QoE related performance 
> parameters. 
> > > Let's recall QoE (e.g., ITU-T P.10 Amendment 2):
> > > 
> > > Quality of Experience (QoE): 
> > > The overall acceptability of an application or service, as 
> > perceived subjectively by the end-user.  
> > > NOTE 1 - Quality of experience includes the complete 
> > end-to-end system effects (client, terminal, network, 
> > services infrastructure, etc.). 
> > > NOTE 2 - Overall acceptability may be influenced by user 
> > expectations and context. 
> > > 
> > > Important for MONARCH:
> > > 1st ... perceived by end-user
> > > 2nd QoE includes the complete end-to-end sytem effects ...
> > > 
> > > That said, present RTP monitoring architecture in MONARCH 
> > according clause 3 is not specific on the type of monitoring 
> > architecture. For instance, Fig. 1, it is possibly supposed 
> > that the "RTP Sender" and "RTP Receiver" entities are equal 
> > to a terminal/user equipment (UE). This would be an 
> > end-to-end IP network scenario.
> > > 
> > > However, the "RTP Sender" and "RTP Receiver" entities may 
> > be also located at the edge of an IP network, e.g. in a 
> > gateway for IP-to-non-IP interworking, i.e. an UE located in 
> > the non-IP network part. 
> > > Note: such scenarios are considered by MEGACO gateways 
> > (I've Cc'd megaco list).
> > > 
> > > An RTP Sender/Receiver located NOT in the UE would question 
> > the value of RTP/RTCP QoE related performance measurements 
> > (because the UE is located outside the RTP domain). 
> > > 
> > > Conclusions:
> > > - the set of meaningful performance metrics may be 
> > dependent on the location of the RTP Sender/Receiver, e.g. 
> > whether in a UE, gateway, ...
> > > - don't see any impact on transport level metrics
> > > - ... but the set of meaningful application level metrics
> > > 
> > > Proposal for MONARCH:
> > > #1: insert sub-clause title "3.1 End-to-end IP network 
> > architecture" below clause 3
> > > 
> > > #2: add a sub-clause 3.2 at the end of clause 3, sth like
> > > 
> > > "3.2 RTP Sender/Receiver entities located in network nodes
> > > The location of the RTP Sender/Receiver entity may impact 
> > the set of meaningful metrics.
> > > For instance: application level metrics for QoE related 
> > performance metrics are questionable (or doesn't really make 
> > sense at all) when measured in a network node (terminating 
> > the RTP) instead of the user equipment."
> > > 
> > > Something like this would help to avoid confusion.
> > > I even believe that a QoE measurement in a network node 
> > would violate the QoE definition. Would be rather something 
> > like QoE* ("remote QoE"):-(
> > > 
> > > Such information would improve the MONARCH doc in my opinion.
> > > Sorry for that late comment.
> > > Any views?
> > 
> > [Qin]: 
> > Albrrecht, if you follow ealry list discussion on 
> > draft-hunt-avt-monarch-01, you will see the rough consensus 
> > to position this document was 
> > this daft should focus on guidelines for defining reporting 
> > blocks. That is to say the main purpose of MONARCH draft is how to 
> > provide guidelines for the development of new RTCP XR block 
> > types in XRBlock working group.
> 
> [ABS] ... then the title "monitoring architectures" is misleading.
> Proposal: keep title, revise scope section on focus
> 
> [Qin]: No, the title is *RTP* monitoring architecture, we can 
> not expand scope into IP monitoring architecture.

[ABS] That's wasn't the intent! Did just focus on the key word.

> 
> > 
> > Therefore how and where to collect the metric from RTP 
> > endpoint is not scope of this document, in my opinion. since 
> > you may have many ways to do this and different vendors have 
> > their different appoaches. It will be better to leave this 
> > beyond the scope. But you are right, it will be more 
> > reasonable to measure QoE related performance metric at the 
> > RTP receiver.
> 
> [ABS] I would disagree. At least your statement should be 
> conditional, sth like 
> "QoE related performance metrics may be measured in a RTP 
> receiver, IF the RTP receiver function is located in user 
> equipment (e.g. IP terminal), because QoE performance metrics 
> are tightly coupled to the point of view of a 'user'.
> ... IF NOT, then ..."
> 
> [Qin]: I am not sure user equipment or IP terminal is the 
> right term from RTP perspective.
> 
> Also if you read P.NAMS, P.NAMS model for calculating QoE 
> related metric can be placed either at the network or at the client.
> So I disagree with what you said.

[ABS] Not convinced at all.
Guess you are referring to the "mid-point" models, right?
The usage of such that models depends on "prior knowledge ..." information.
Thus, the applicability is conditional. You may not make such a general statement.


> 
> Also as I said, how and where to collect the metric from RTP 
>  endpoint is not scope of this document. It depends on the 
> model you are choosing, e.g., four operation modes specified 
> in P.NAMS.
> Apparently this should not be specified again in RTP 
> monitoring architecture document.
> 
> >  
> > Another point is it is not clear to me how RTP monitoring has 
> > to do with architectureend to end IP network architecture .
> > this draft mostly focus on discussing RTP level stuff. 
> > Therefore I am quite doubt that we should describe anything 
> > in this document like how
> > RTP entties is mapped into network entities/nodes at the IP layer.
> 
> [ABS] I don't got any problems to talk about architectural 
> framework for monitoring in this document. Such information 
> is required and this is the only IETF AVT doc about it.
> The solution to this issue is rather simple to me:
> - split the MONARCH "monitoring architecture" in
> 1) a functional monitoring architecture (let's call it 'FMA') and
> 2) a physical monitoring architecture (... 'PMA').
> 
> - the present MONARCH doc would describe the FMA at the level 
> of RTP entities (i.e., Fig. 1 entities, incl. all the RTP 
> topology components according RFC 5117)
> 
> - there are many options of functional-to-physical mappings, 
> i.e. how a FMA would be mapped on a PMA
> - the mapping is typically dependent on considered network 
> architecture (like SIP, H.323, MGCP, IMS, wireless, etc networks)
> 
> - the present MONARCH doc would describe the FMA-to-PMA 
> mapping IF all RTP receiver/sender entities would be located 
> in physical IP terminals (UEs)
> - etc
> 
> [Qin]: I can understand your point, but you can not do that. 
> Since this document is only focus on *RTP* monitoring 
> architecture, that is what it said in AVTCore milestone:
> "
> 
> Goals and Milestones:
> 
>   Feb 2011 - Submit Monitoring Architecture for RTP for Informational
> 
> "

[ABS] If you go back to my first email on this subject, and if you look at my proposal: that's not a lot, nothing which violates the charter, goals and milestones.


> Also if you really don't see how to map FMA to PMA, you may 
> look at the P.NAMS models specifed in ITU-T P.NAMS. 
> As for how to use RTP monitoring architecture or RTP XR 
> Report in the IMS network architecture, you may look at:
> http://tools.ietf.org/html/rfc6035

[ABS] That's the SIP reporting interface, i.e., applicable primarily for physical IP user equipment with embedded RTP sender/receiver function and SIP UA function.
However, the applicability of RFC 6035 is limited for a SIP-to-PSTN gateway (because the RTP sender/receiver would be located NOT in user equipment. Also the P.NAMS mid-point model fails for such a scenario.

> ITU-T H.248.48.
> But I haven't check the current status of H.248.48.

[ABS] Work is finalized, see http://www.itu.int/md/meetingdoc.asp?lang=en&parent=T09-SG16-111121-TD-PLEN-0419

> 
> > 
> > But as the author of this document, I am interested and open 
> > to other opinions.:-)
> 
> [ABS] Like to add a further aspect: a "functional monitoring 
> architecture" may be considered as a network overlay, 
> something which adds additional capabilities (here: 
> measurement services, reporting services on top of basic RTP 
> services).
> Such an overlay concept is nothing new: e.g., the 
> MultiService Forum did define a "Performance Measurement & 
> Monitoring (PMM)" overlay network, or IETF RMON may be also 
> considered as such.
> 
> > 
> > > Regards,
> > > Albrecht
> > > 
> > > 
> > > 
> > > 
> > >> -----Original Message-----
> > >> From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On 
> > >> Behalf Of internet-drafts@ietf.org
> > >> Sent: Dienstag, 29. November 2011 08:56
> > >> To: i-d-announce@ietf.org
> > >> Cc: avt@ietf.org
> > >> Subject: [AVTCORE] I-D Action: draft-ietf-avtcore-monarch-08.txt
> > >> 
> > >> 
> > >> A New Internet-Draft is available from the on-line 
> > >> Internet-Drafts directories. This draft is a work item of the 
> > >> Audio/Video Transport Core Maintenance Working Group of the IETF.
> > >> 
> > >> Title           : Monitoring Architectures for RTP
> > >> Author(s)       : Qin Wu
> > >>                           Geoff Hunt
> > >>                           Philip Arden
> > >> Filename        : draft-ietf-avtcore-monarch-08.txt
> > >> Pages           : 25
> > >> Date            : 2011-11-28
> > >> 
> > >>    This memo proposes an architecture for extending RTCP with 
> > >> a new RTCP
> > >>    XR (RFC3611) block type to report new metrics regarding media
> > >>    transmission or reception quality, following RTCP guideline
> > >>    established in RFC5968.  This memo suggests that a new 
> > block should
> > >>    contain a single metric or a small number of metrics 
> > relevant to a
> > >>    single parameter of interest or concern, rather than 
> > containing a
> > >>    number of metrics which attempt to provide full coverage 
> > >> of all those
> > >>    parameters of concern to a specific application.  
> > Applications may
> > >>    then "mix and match" to create a set of blocks which 
> > >> covers their set
> > >>    of concerns.  Where possible, a specific block should be 
> > >> designed to
> > >>    be re-usable across more than one application, for 
> > example, for all
> > >>    of voice, streaming audio and video.
> > >> 
> > >> 
> > >> A URL for this Internet-Draft is:
> > >> 
> > 
> http://www.ietf.org/internet-drafts/draft-ietf-avtcore-monarch-08.txt
> > >> 
> > >> Internet-Drafts are also available by anonymous FTP at:
> > >> ftp://ftp.ietf.org/internet-drafts/
> > >> 
> > >> This Internet-Draft can be retrieved at:
> > >> 
> > ftp://ftp.ietf.org/internet-drafts/draft-ietf-avtcore-monarch-08.txt
> > >> 
> > >> _______________________________________________
> > >> Audio/Video Transport Core Maintenance
> > >> avt@ietf.org
> > >> https://www.ietf.org/mailman/listinfo/avt
> > >> 
> > > _______________________________________________
> > > Audio/Video Transport Core Maintenance
> > > avt@ietf.org
> > > https://www.ietf.org/mailman/listinfo/avt
> >
> =

From albrecht.schwarz@alcatel-lucent.com  Sat Dec  3 01:08:35 2011
Return-Path: <albrecht.schwarz@alcatel-lucent.com>
X-Original-To: megaco@ietfa.amsl.com
Delivered-To: megaco@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E89FF21F8F5D for <megaco@ietfa.amsl.com>; Sat,  3 Dec 2011 01:08:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.549
X-Spam-Level: 
X-Spam-Status: No, score=-5.549 tagged_above=-999 required=5 tests=[AWL=-0.200, BAYES_00=-2.599, HELO_EQ_FR=0.35, J_CHICKENPOX_73=0.6, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LkyQ24Vx0K1V for <megaco@ietfa.amsl.com>; Sat,  3 Dec 2011 01:08:35 -0800 (PST)
Received: from smail3.alcatel.fr (smail3.alcatel.fr [64.208.49.56]) by ietfa.amsl.com (Postfix) with ESMTP id E9FE121F8EEC for <megaco@ietf.org>; Sat,  3 Dec 2011 01:08:33 -0800 (PST)
Received: from FRMRSSXCHHUB02.dc-m.alcatel-lucent.com (FRMRSSXCHHUB02.dc-m.alcatel-lucent.com [135.120.45.62]) by smail3.alcatel.fr (8.14.3/8.14.3/ICT) with ESMTP id pB398PSP019700 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Sat, 3 Dec 2011 10:08:29 +0100
Received: from FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com ([135.120.45.50]) by FRMRSSXCHHUB02.dc-m.alcatel-lucent.com ([135.120.45.62]) with mapi; Sat, 3 Dec 2011 10:08:15 +0100
From: "Schwarz, Albrecht (Albrecht)" <albrecht.schwarz@alcatel-lucent.com>
To: =?iso-8859-1?Q?Javi_Mu=F1oz?= <javi@trajano.us.es>, "megaco@ietf.org" <megaco@ietf.org>
Date: Sat, 3 Dec 2011 10:09:10 +0100
Thread-Topic: Media server; RE: [Megaco] Selection of media (m=) at MG
Thread-Index: Acyw60MoXt6PWtAWTUCnMf38H/E/1gAr6nJQ
Message-ID: <5F7BCCF5541B7444830A2288ABBEBC9621620F4992@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com>
References: <4ED518F6.4020201@trajano.us.es> <5F7BCCF5541B7444830A2288ABBEBC962161900622@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com> <4ED604A0.2000402@trajano.us.es> <4ED6640A.9030508@trajano.us.es> <5F7BCCF5541B7444830A2288ABBEBC962161900780@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com> <4ED66B87.7050907@trajano.us.es> <4ED8BFD6.6040306@trajano.us.es>
In-Reply-To: <4ED8BFD6.6040306@trajano.us.es>
Accept-Language: de-DE, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: de-DE, en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.69 on 155.132.188.83
Subject: [Megaco] Media server; RE:  Selection of media (m=) at MG
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.1.12
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: Sat, 03 Dec 2011 09:08:36 -0000

yes, (b) is the media server scenario.
E.g. an IMS media server, called MRFP, control via "H.248 Mp profile" (3GPP=
 29.333)
=20

> -----Original Message-----
> From: Javi Mu=F1oz [mailto:javi@trajano.us.es]=20
> Sent: Freitag, 2. Dezember 2011 13:09
> To: megaco@ietf.org
> Cc: Schwarz, Albrecht (Albrecht)
> Subject: Re: [Megaco] Selection of media (m=3D) at MG
>=20
> Albrecht,
>=20
> I complete my comment "(b)":
>=20
> [ETSI TS 183 002 Clause 7.1.4]
> Access Gateways may be able to store recorded announcements=20
> and shall support the generic announcement package. Generic=20
> Announcement (ITU-T Rec. H.248.7 [18]): mandatory if local=20
> announcements are available.
> When the announcement to be delivered is not available in the=20
> gateway and cannot be autonomously retrieved by the gateway=20
> from a remote repository, the MGC shall initiate a connection=20
> to an external announcement machine, by temporarily adding a=20
> termination into the context. Instructions to play=20
> announcements are sent directly from the MGC to the server.=20
> The announcement server may itself be implemented as an MG,=20
> controlled using the H.248 protocol. However, this interface=20
> is outside the scope of the present document. In an=20
> originating MG, the context topology and the termination=20
> modes shall be configured in such a way that in-band=20
> information can be received from the remote side before the=20
> called party's answer. This setting shall occur not later=20
> than the receipt of the ACO message (or an equivalent message=20
> from another signalling protocol that ISUP).
>=20
> Regards,
>=20
> Javi
> >
> >> well spotted, thus just a single media configuration ('Clearmode')=20
> >> would be already sufficient to emulate that ISDN bearer service
> > However, two comments:
> >
> > (a) In the "call establishment phase": what must be created at the
> > MG?: would it be necessary to create a context, or would it=20
> be enough=20
> > to create only an ISDN termination in the null context (which would=20
> > generate that tone/announcement, and then, MGC would apply a modify=20
> > command to create the context for the information phase)?
> >
> > (b) I believe, the announcement do not necessarily have to=20
> be recorded=20
> > in AGW, but that may come from an announcement server (I guess this=20
> > would also be possible for DTMF tones). Could this justify the=20
> > creation of such IP termination with voice codec G.711 in the=20
> > establishment phase, or that communication with the announcement=20
> > server does not belong to the ISDN call and, therefore, it=20
> should not=20
> > be involved in its Megaco context?
> >
> > Regards,
> >
> >
> >
> >> PS
> >> Your previous email was related to ISDN-to-SIP=20
> interworking at call=20
> >> control level, a subject which is out of scope of MEGACO.
> >> Thus, something for SIPPING, SIP-IMPLEMENTERS, ... (or TISPAN WG3
> >> list) in my understanding.
> >>
> >>> -----Original Message-----
> >>> From: Javi Mu=F1oz [mailto:javi@trajano.us.es]
> >>> Sent: Mittwoch, 30. November 2011 18:13
> >>> To: megaco@ietf.org
> >>> Cc: Schwarz, Albrecht (Albrecht)
> >>> Subject: Re: [Megaco] Selection of media (m=3D) at MG
> >>>
> >>> A second comment,
> >>>
> >>> If:
> >>>>>      a) TGW: no impact, because tone/announcement=20
> inserted by ISDN=20
> >>>>> local exchange (terminating Q.931); TGW needs just
> >>> clearmode support
> >>>
> >>> (I agree)
> >>>
> >>> then, why?
> >>>>> E.g., MGC
> >>>>> ->   call establishment phase: IF tones/announcements THEN H.248
> >>>>> Command.req for tone/announcement control plus media=20
> configuration=20
> >>>>> with voice codec
> >>> That "media configuration with voice codec" (G.711) would=20
> be done at=20
> >>> the MeGaCo termination of the IP side of the MG, not at the=20
> >>> termination of the ISDN side. If tone/announcement is=20
> inserted (in=20
> >>> the UNI ISDN) by this MG, the termination of the IP side=20
> of the MG=20
> >>> would not be used, so that "voice codec"
> >>> would not be relevant (no media would be transported over the IP=20
> >>> network).
> >>>
> >>> am I wrong?
> >>>
> >>> Regards,
> >>>
> >>> Javi
> >>>
> >
>=20
> =

From albrecht.schwarz@alcatel-lucent.com  Mon Dec  5 06:49:26 2011
Return-Path: <albrecht.schwarz@alcatel-lucent.com>
X-Original-To: megaco@ietfa.amsl.com
Delivered-To: megaco@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 124A821F8B5A; Mon,  5 Dec 2011 06:49:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.67
X-Spam-Level: 
X-Spam-Status: No, score=-5.67 tagged_above=-999 required=5 tests=[AWL=-0.021,  BAYES_00=-2.599, HELO_EQ_FR=0.35, J_CHICKENPOX_14=0.6, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QS7QNRGv0+tE; Mon,  5 Dec 2011 06:49:24 -0800 (PST)
Received: from smail2.alcatel.fr (smail2.alcatel.fr [64.208.49.57]) by ietfa.amsl.com (Postfix) with ESMTP id BCFCF21F8B1D; Mon,  5 Dec 2011 06:49:23 -0800 (PST)
Received: from FRMRSSXCHHUB02.dc-m.alcatel-lucent.com (FRMRSSXCHHUB02.dc-m.alcatel-lucent.com [135.120.45.62]) by smail2.alcatel.fr (8.14.3/8.14.3/ICT) with ESMTP id pB5ElIGZ022638 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Mon, 5 Dec 2011 15:49:03 +0100
Received: from FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com ([135.120.45.50]) by FRMRSSXCHHUB02.dc-m.alcatel-lucent.com ([135.120.45.62]) with mapi; Mon, 5 Dec 2011 15:48:36 +0100
From: "Schwarz, Albrecht (Albrecht)" <albrecht.schwarz@alcatel-lucent.com>
To: Qin Wu <bill.wu@huawei.com>, "avt@ietf.org" <avt@ietf.org>
Date: Mon, 5 Dec 2011 15:48:35 +0100
Thread-Topic: [AVTCORE] Types of monitoring architectures; RE:  I-D Action: draft-ietf-avtcore-monarch-08.txt
Thread-Index: AcywlWaLArPPa4UIQ9evRggexGLeFQCxJy3A
Message-ID: <5F7BCCF5541B7444830A2288ABBEBC9621620F4AF5@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com>
References: <20111129075613.12419.4377.idtracker@ietfa.amsl.com> <5F7BCCF5541B7444830A2288ABBEBC96216190051A@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com> <EAC481B4D8034C38AC54E1217F8D875D@china.huawei.com> <5F7BCCF5541B7444830A2288ABBEBC96216190077F@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com> <B527BAFA038842A8939A8C2D558074CD@china.huawei.com> <5F7BCCF5541B7444830A2288ABBEBC962161900908@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com> <9FF9B04A84E64AD7ABCCC4F2ACC1E19A@china.huawei.com>
In-Reply-To: <9FF9B04A84E64AD7ABCCC4F2ACC1E19A@china.huawei.com>
Accept-Language: de-DE, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: de-DE, en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.69 on 155.132.188.80
Cc: "megaco@ietf.org" <megaco@ietf.org>
Subject: Re: [Megaco] [AVTCORE] Types of monitoring architectures; RE:  I-D Action: draft-ietf-avtcore-monarch-08.txt
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.1.12
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: Mon, 05 Dec 2011 14:49:26 -0000

Hello Qin,

to 1) Physical monitoring architecture
Of course consideration of generic physical entities (PE), not specific to =
any network reference architectures defined by SDOs (like your refered enti=
ties).
There would be just a few PE types ("given by the limited set of RTP topolo=
gy components (RFC 5117)").

to 2) (RFC 3550) Monitor function
Right, that's a functional entity. The applicability of a monitor may be li=
mited, dependent on ... (like in P.NAMS).

to 3) your IMS network example
Don't see the need to refer from MONARCH to a specific network architecture=
 like IMS.
Please also note that IMS is a functional architecture, not a physical arch=
itecture.

Regards,
Albrecht

PS
There are multiple options for adding the "RTP monitoring architecture" to =
a functional/physical network architecture:
a) integrated approach: extension of existing functional entities or/and ad=
dition of RTP monitoring architectural components, extension or/and additio=
n of signalling/management interfaces for control and configuration of RTP =
monitoring services, and reporting interfaces for measurement data ...
b) overlay approach: separate specification to ...


PSS
BTW: there's a discussion paper with regards to the location of a monitor f=
unction in an IMS H.248 gateway entity:
Measurements and statistics in IMS - Use Cases
http://www.3gpp.org/ftp/tsg_ct/WG3_interworking_ex-CN3/TSGC3_58_Kyoto_Japan=
/Docs/C3-100469.zip
This is just fyi.



> -----Original Message-----
> From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On
> Behalf Of Qin Wu
> Sent: Freitag, 2. Dezember 2011 02:55
> To: Schwarz, Albrecht (Albrecht); avt@ietf.org
> Cc: megaco@ietf.org
> Subject: Re: [AVTCORE] Types of monitoring architectures; RE:
> I-D Action: draft-ietf-avtcore-monarch-08.txt
>
> Hi, Albrecht:
> No offence, I am not really convinced with your proposal on
> physical monitoring architecture.
>  my counterquestion is what does physical monitoring
> architecture looks like in your mind?
> How many components do we have in such physical monitroing
> architecture? what are they?
> Take IMS network architecture as a example, they may have
> P-CSCF,S-CSCF, SIP PBX, SBC, why do you believe monitor
> described in draft-ietf-avtcore-monarch is mapped into
> P-CSCF, S-CSCF, SBC, Media Gateway, Media Gateway Controller
> should be in the scope of IETF RTP monitoring archtiecture draft?
>
> Monitor described in  draft-ietf-avtcore-monarch is well
> defined in the section 3 of RFC3550 as follows:
> "
>
>    Monitor: An application that receives RTCP packets sent by
>       participants in an RTP session, in particular the reception
>       reports, and estimates the current quality of service for
>       distribution monitoring, fault diagnosis and long-term
> statistics.
>       The monitor function is likely to be built into the
> application(s)
>       participating in the session, but may also be a separate
>       application that does not otherwise participate and
> does not send
>       or receive the RTP data packets (since they are on a separate
>       port).  These are called third-party monitors.  It is also
>       acceptable for a third-party monitor to receive the RTP data
>       packets but not send RTCP packets or otherwise be counted in the
>       session.
>
> "
> Isn't how to implent monitor into IMS netowork archtiecture a
> implentation specific issue?
> If this issue are really interesting, isn't it a good idea to
> produce another new document to talk about this?
> One good example for this motivation is this draft I like to
> share with you:
> http://tools.ietf.org/html/draft-kaplan-dispatch-b2bua-taxonom
> y-00#section-4.6
>
> Regards!
> -Qin
> ----- Original Message -----
> From: "Schwarz, Albrecht (Albrecht)"
> <albrecht.schwarz@alcatel-lucent.com>
> To: "Qin Wu" <bill.wu@huawei.com>; <avt@ietf.org>
> Cc: <megaco@ietf.org>
> Sent: Friday, December 02, 2011 12:20 AM
> Subject: RE: [AVTCORE] Types of monitoring architectures; RE:
> I-D Action: draft-ietf-avtcore-monarch-08.txt
>
>
> My replies below ...
> -Albrecht
>
> > -----Original Message-----
> > From: Qin Wu [mailto:bill.wu@huawei.com]
> > Sent: Donnerstag, 1. Dezember 2011 02:42
> > To: Schwarz, Albrecht (Albrecht); avt@ietf.org
> > Cc: megaco@ietf.org
> > Subject: Re: [AVTCORE] Types of monitoring architectures; RE:
> > I-D Action: draft-ietf-avtcore-monarch-08.txt
> >
> > Hi,
> > ----- Original Message -----
> > From: "Schwarz, Albrecht (Albrecht)"
> > <albrecht.schwarz@alcatel-lucent.com>
> > To: "Qin Wu" <bill.wu@huawei.com>; <avt@ietf.org>
> > Cc: <megaco@ietf.org>
> > Sent: Thursday, December 01, 2011 1:24 AM
> > Subject: RE: [AVTCORE] Types of monitoring architectures; RE:
> > I-D Action: draft-ietf-avtcore-monarch-08.txt
> >
> >
> > My replies below inline,
> > Albrecht
> >
> > > -----Original Message-----
> > > From: Qin Wu [mailto:bill.wu@huawei.com]
> > > Sent: Mittwoch, 30. November 2011 04:51
> > > To: Schwarz, Albrecht (Albrecht); avt@ietf.org
> > > Cc: megaco@ietf.org
> > > Subject: Re: [AVTCORE] Types of monitoring architectures; RE:
> > > I-D Action: draft-ietf-avtcore-monarch-08.txt
> > >
> > > Hi,
> > > ----- Original Message -----
> > > From: "Schwarz, Albrecht (Albrecht)"
> > > <albrecht.schwarz@alcatel-lucent.com>
> > > To: <avt@ietf.org>
> > > Cc: <megaco@ietf.org>
> > > Sent: Tuesday, November 29, 2011 7:32 PM
> > > Subject: [AVTCORE] Types of monitoring architectures; RE: I-D
> > > Action: draft-ietf-avtcore-monarch-08.txt
> > >
> > >
> > > > Dear All,
> > > >
> > > > there are different types of monitoring architectures,
> > > particularily from perspective of QoE related performance
> > parameters.
> > > > Let's recall QoE (e.g., ITU-T P.10 Amendment 2):
> > > >
> > > > Quality of Experience (QoE):
> > > > The overall acceptability of an application or service, as
> > > perceived subjectively by the end-user.
> > > > NOTE 1 - Quality of experience includes the complete
> > > end-to-end system effects (client, terminal, network,
> > > services infrastructure, etc.).
> > > > NOTE 2 - Overall acceptability may be influenced by user
> > > expectations and context.
> > > >
> > > > Important for MONARCH:
> > > > 1st ... perceived by end-user
> > > > 2nd QoE includes the complete end-to-end sytem effects ...
> > > >
> > > > That said, present RTP monitoring architecture in MONARCH
> > > according clause 3 is not specific on the type of monitoring
> > > architecture. For instance, Fig. 1, it is possibly supposed
> > > that the "RTP Sender" and "RTP Receiver" entities are equal
> > > to a terminal/user equipment (UE). This would be an
> > > end-to-end IP network scenario.
> > > >
> > > > However, the "RTP Sender" and "RTP Receiver" entities may
> > > be also located at the edge of an IP network, e.g. in a
> > > gateway for IP-to-non-IP interworking, i.e. an UE located in
> > > the non-IP network part.
> > > > Note: such scenarios are considered by MEGACO gateways
> > > (I've Cc'd megaco list).
> > > >
> > > > An RTP Sender/Receiver located NOT in the UE would question
> > > the value of RTP/RTCP QoE related performance measurements
> > > (because the UE is located outside the RTP domain).
> > > >
> > > > Conclusions:
> > > > - the set of meaningful performance metrics may be
> > > dependent on the location of the RTP Sender/Receiver, e.g.
> > > whether in a UE, gateway, ...
> > > > - don't see any impact on transport level metrics
> > > > - ... but the set of meaningful application level metrics
> > > >
> > > > Proposal for MONARCH:
> > > > #1: insert sub-clause title "3.1 End-to-end IP network
> > > architecture" below clause 3
> > > >
> > > > #2: add a sub-clause 3.2 at the end of clause 3, sth like
> > > >
> > > > "3.2 RTP Sender/Receiver entities located in network nodes
> > > > The location of the RTP Sender/Receiver entity may impact
> > > the set of meaningful metrics.
> > > > For instance: application level metrics for QoE related
> > > performance metrics are questionable (or doesn't really make
> > > sense at all) when measured in a network node (terminating
> > > the RTP) instead of the user equipment."
> > > >
> > > > Something like this would help to avoid confusion.
> > > > I even believe that a QoE measurement in a network node
> > > would violate the QoE definition. Would be rather something
> > > like QoE* ("remote QoE"):-(
> > > >
> > > > Such information would improve the MONARCH doc in my opinion.
> > > > Sorry for that late comment.
> > > > Any views?
> > >
> > > [Qin]:
> > > Albrrecht, if you follow ealry list discussion on
> > > draft-hunt-avt-monarch-01, you will see the rough consensus
> > > to position this document was
> > > this daft should focus on guidelines for defining reporting
> > > blocks. That is to say the main purpose of MONARCH draft
> is how to
> > > provide guidelines for the development of new RTCP XR block
> > > types in XRBlock working group.
> >
> > [ABS] ... then the title "monitoring architectures" is misleading.
> > Proposal: keep title, revise scope section on focus
> >
> > [Qin]: No, the title is *RTP* monitoring architecture, we can
> > not expand scope into IP monitoring architecture.
>
> [ABS] That's wasn't the intent! Did just focus on the key word.
>
> >
> > >
> > > Therefore how and where to collect the metric from RTP
> > > endpoint is not scope of this document, in my opinion. since
> > > you may have many ways to do this and different vendors have
> > > their different appoaches. It will be better to leave this
> > > beyond the scope. But you are right, it will be more
> > > reasonable to measure QoE related performance metric at the
> > > RTP receiver.
> >
> > [ABS] I would disagree. At least your statement should be
> > conditional, sth like
> > "QoE related performance metrics may be measured in a RTP
> > receiver, IF the RTP receiver function is located in user
> > equipment (e.g. IP terminal), because QoE performance metrics
> > are tightly coupled to the point of view of a 'user'.
> > ... IF NOT, then ..."
> >
> > [Qin]: I am not sure user equipment or IP terminal is the
> > right term from RTP perspective.
> >
> > Also if you read P.NAMS, P.NAMS model for calculating QoE
> > related metric can be placed either at the network or at the client.
> > So I disagree with what you said.
>
> [ABS] Not convinced at all.
> Guess you are referring to the "mid-point" models, right?
> The usage of such that models depends on "prior knowledge
> ..." information.
> Thus, the applicability is conditional. You may not make such
> a general statement.
>
>
> >
> > Also as I said, how and where to collect the metric from RTP
> >  endpoint is not scope of this document. It depends on the
> > model you are choosing, e.g., four operation modes specified
> > in P.NAMS.
> > Apparently this should not be specified again in RTP
> > monitoring architecture document.
> >
> > >
> > > Another point is it is not clear to me how RTP monitoring has
> > > to do with architectureend to end IP network architecture .
> > > this draft mostly focus on discussing RTP level stuff.
> > > Therefore I am quite doubt that we should describe anything
> > > in this document like how
> > > RTP entties is mapped into network entities/nodes at the IP layer.
> >
> > [ABS] I don't got any problems to talk about architectural
> > framework for monitoring in this document. Such information
> > is required and this is the only IETF AVT doc about it.
> > The solution to this issue is rather simple to me:
> > - split the MONARCH "monitoring architecture" in
> > 1) a functional monitoring architecture (let's call it 'FMA') and
> > 2) a physical monitoring architecture (... 'PMA').
> >
> > - the present MONARCH doc would describe the FMA at the level
> > of RTP entities (i.e., Fig. 1 entities, incl. all the RTP
> > topology components according RFC 5117)
> >
> > - there are many options of functional-to-physical mappings,
> > i.e. how a FMA would be mapped on a PMA
> > - the mapping is typically dependent on considered network
> > architecture (like SIP, H.323, MGCP, IMS, wireless, etc networks)
> >
> > - the present MONARCH doc would describe the FMA-to-PMA
> > mapping IF all RTP receiver/sender entities would be located
> > in physical IP terminals (UEs)
> > - etc
> >
> > [Qin]: I can understand your point, but you can not do that.
> > Since this document is only focus on *RTP* monitoring
> > architecture, that is what it said in AVTCore milestone:
> > "
> >
> > Goals and Milestones:
> >
> >   Feb 2011 - Submit Monitoring Architecture for RTP for
> Informational
> >
> > "
>
> [ABS] If you go back to my first email on this subject, and
> if you look at my proposal: that's not a lot, nothing which
> violates the charter, goals and milestones.
>
>
> > Also if you really don't see how to map FMA to PMA, you may
> > look at the P.NAMS models specifed in ITU-T P.NAMS.
> > As for how to use RTP monitoring architecture or RTP XR
> > Report in the IMS network architecture, you may look at:
> > http://tools.ietf.org/html/rfc6035
>
> [ABS] That's the SIP reporting interface, i.e., applicable
> primarily for physical IP user equipment with embedded RTP
> sender/receiver function and SIP UA function.
> However, the applicability of RFC 6035 is limited for a
> SIP-to-PSTN gateway (because the RTP sender/receiver would be
> located NOT in user equipment. Also the P.NAMS mid-point
> model fails for such a scenario.
>
> > ITU-T H.248.48.
> > But I haven't check the current status of H.248.48.
>
> [ABS] Work is finalized, see
> http://www.itu.int/md/meetingdoc.asp?lang=3Den&parent=3DT09-SG16-1
> 11121-TD-PLEN-0419
>
> >
> > >
> > > But as the author of this document, I am interested and open
> > > to other opinions.:-)
> >
> > [ABS] Like to add a further aspect: a "functional monitoring
> > architecture" may be considered as a network overlay,
> > something which adds additional capabilities (here:
> > measurement services, reporting services on top of basic RTP
> > services).
> > Such an overlay concept is nothing new: e.g., the
> > MultiService Forum did define a "Performance Measurement &
> > Monitoring (PMM)" overlay network, or IETF RMON may be also
> > considered as such.
> >
> > >
> > > > Regards,
> > > > Albrecht
> > > >
> > > >
> > > >
> > > >
> > > >> -----Original Message-----
> > > >> From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On
> > > >> Behalf Of internet-drafts@ietf.org
> > > >> Sent: Dienstag, 29. November 2011 08:56
> > > >> To: i-d-announce@ietf.org
> > > >> Cc: avt@ietf.org
> > > >> Subject: [AVTCORE] I-D Action:
> draft-ietf-avtcore-monarch-08.txt
> > > >>
> > > >>
> > > >> A New Internet-Draft is available from the on-line
> > > >> Internet-Drafts directories. This draft is a work item of the
> > > >> Audio/Video Transport Core Maintenance Working Group
> of the IETF.
> > > >>
> > > >> Title           : Monitoring Architectures for RTP
> > > >> Author(s)       : Qin Wu
> > > >>                           Geoff Hunt
> > > >>                           Philip Arden
> > > >> Filename        : draft-ietf-avtcore-monarch-08.txt
> > > >> Pages           : 25
> > > >> Date            : 2011-11-28
> > > >>
> > > >>    This memo proposes an architecture for extending RTCP with
> > > >> a new RTCP
> > > >>    XR (RFC3611) block type to report new metrics
> regarding media
> > > >>    transmission or reception quality, following RTCP guideline
> > > >>    established in RFC5968.  This memo suggests that a new
> > > block should
> > > >>    contain a single metric or a small number of metrics
> > > relevant to a
> > > >>    single parameter of interest or concern, rather than
> > > containing a
> > > >>    number of metrics which attempt to provide full coverage
> > > >> of all those
> > > >>    parameters of concern to a specific application.
> > > Applications may
> > > >>    then "mix and match" to create a set of blocks which
> > > >> covers their set
> > > >>    of concerns.  Where possible, a specific block should be
> > > >> designed to
> > > >>    be re-usable across more than one application, for
> > > example, for all
> > > >>    of voice, streaming audio and video.
> > > >>
> > > >>
> > > >> A URL for this Internet-Draft is:
> > > >>
> > >
> >
> http://www.ietf.org/internet-drafts/draft-ietf-avtcore-monarch-08.txt
> > > >>
> > > >> Internet-Drafts are also available by anonymous FTP at:
> > > >> ftp://ftp.ietf.org/internet-drafts/
> > > >>
> > > >> This Internet-Draft can be retrieved at:
> > > >>
> > >
> ftp://ftp.ietf.org/internet-drafts/draft-ietf-avtcore-monarch-08.txt
> > > >>
> > > >> _______________________________________________
> > > >> Audio/Video Transport Core Maintenance
> > > >> avt@ietf.org
> > > >> https://www.ietf.org/mailman/listinfo/avt
> > > >>
> > > > _______________________________________________
> > > > Audio/Video Transport Core Maintenance
> > > > avt@ietf.org
> > > > https://www.ietf.org/mailman/listinfo/avt
> > >
> > =3D
> _______________________________________________
> Audio/Video Transport Core Maintenance
> avt@ietf.org
> https://www.ietf.org/mailman/listinfo/avt
>

From bill.wu@huawei.com  Mon Dec  5 22:17:45 2011
Return-Path: <bill.wu@huawei.com>
X-Original-To: megaco@ietfa.amsl.com
Delivered-To: megaco@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 92B0321F87FC; Mon,  5 Dec 2011 22:17:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.14
X-Spam-Level: 
X-Spam-Status: No, score=-6.14 tagged_above=-999 required=5 tests=[AWL=-0.141,  BAYES_00=-2.599, J_CHICKENPOX_14=0.6, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GvHvdSBA+N8v; Mon,  5 Dec 2011 22:17:43 -0800 (PST)
Received: from szxga03-in.huawei.com (szxga03-in.huawei.com [119.145.14.66]) by ietfa.amsl.com (Postfix) with ESMTP id 176DE21F87E2; Mon,  5 Dec 2011 22:17:43 -0800 (PST)
Received: from huawei.com (szxga03-in [172.24.2.9]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LVR004KCQMZ7K@szxga03-in.huawei.com>; Tue, 06 Dec 2011 14:13:47 +0800 (CST)
Received: from szxrg02-dlp.huawei.com ([172.24.2.119]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LVR005TTQMYM4@szxga03-in.huawei.com>; Tue, 06 Dec 2011 14:13:47 +0800 (CST)
Received: from szxeml203-edg.china.huawei.com ([172.24.2.119]) by szxrg02-dlp.huawei.com (MOS 4.1.9-GA)	with ESMTP id AFK93955; Tue, 06 Dec 2011 14:13:23 +0800
Received: from SZXEML414-HUB.china.huawei.com (10.82.67.153) by szxeml203-edg.china.huawei.com (172.24.2.55) with Microsoft SMTP Server (TLS) id 14.1.323.3; Tue, 06 Dec 2011 14:13:20 +0800
Received: from w53375q (10.138.41.130) by SZXEML414-HUB.china.huawei.com (10.82.67.153) with Microsoft SMTP Server (TLS) id 14.1.323.3; Tue, 06 Dec 2011 14:13:18 +0800
Date: Tue, 06 Dec 2011 14:13:17 +0800
From: Qin Wu <bill.wu@huawei.com>
X-Originating-IP: [10.138.41.130]
To: "Schwarz, Albrecht (Albrecht)" <albrecht.schwarz@alcatel-lucent.com>, avt@ietf.org
Message-id: <D44A4820E0D24DD79F6F5A4B7507D0D6@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.6109
X-Mailer: Microsoft Outlook Express 6.00.2900.5931
Content-type: text/plain; charset=iso-8859-1
Content-transfer-encoding: 7BIT
X-Priority: 3
X-MSMail-priority: Normal
X-CFilter-Loop: Reflected
References: <20111129075613.12419.4377.idtracker@ietfa.amsl.com> <5F7BCCF5541B7444830A2288ABBEBC96216190051A@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com> <EAC481B4D8034C38AC54E1217F8D875D@china.huawei.com> <5F7BCCF5541B7444830A2288ABBEBC96216190077F@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com> <B527BAFA038842A8939A8C2D558074CD@china.huawei.com> <5F7BCCF5541B7444830A2288ABBEBC962161900908@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com> <9FF9B04A84E64AD7ABCCC4F2ACC1E19A@china.huawei.com> <5F7BCCF5541B7444830A2288ABBEBC9621620F4AF5@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com>
Cc: megaco@ietf.org
Subject: Re: [Megaco] [AVTCORE] Types of monitoring architectures; RE:  I-D Action: draft-ietf-avtcore-monarch-08.txt
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.1.12
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: Tue, 06 Dec 2011 06:17:45 -0000

If you talk about existing RFC5117 RTP topology components, this has already been covered by the current version of draft-ietf-avtcore-monarch.
In most cases, an RTP system using RTCP XR is architecturally no different from an RTP system which does not use RTCP XR.

Regards!
-Qin
----- Original Message ----- 
From: "Schwarz, Albrecht (Albrecht)" <albrecht.schwarz@alcatel-lucent.com>
To: "Qin Wu" <bill.wu@huawei.com>; <avt@ietf.org>
Cc: <megaco@ietf.org>
Sent: Monday, December 05, 2011 10:48 PM
Subject: RE: [AVTCORE] Types of monitoring architectures; RE: I-D Action: draft-ietf-avtcore-monarch-08.txt


Hello Qin,

to 1) Physical monitoring architecture
Of course consideration of generic physical entities (PE), not specific to any network reference architectures defined by SDOs (like your refered entities).
There would be just a few PE types ("given by the limited set of RTP topology components (RFC 5117)").

to 2) (RFC 3550) Monitor function
Right, that's a functional entity. The applicability of a monitor may be limited, dependent on ... (like in P.NAMS).

to 3) your IMS network example
Don't see the need to refer from MONARCH to a specific network architecture like IMS.
Please also note that IMS is a functional architecture, not a physical architecture.

Regards,
Albrecht

PS
There are multiple options for adding the "RTP monitoring architecture" to a functional/physical network architecture:
a) integrated approach: extension of existing functional entities or/and addition of RTP monitoring architectural components, extension or/and addition of signalling/management interfaces for control and configuration of RTP monitoring services, and reporting interfaces for measurement data ...
b) overlay approach: separate specification to ...


PSS
BTW: there's a discussion paper with regards to the location of a monitor function in an IMS H.248 gateway entity:
Measurements and statistics in IMS - Use Cases
http://www.3gpp.org/ftp/tsg_ct/WG3_interworking_ex-CN3/TSGC3_58_Kyoto_Japan/Docs/C3-100469.zip
This is just fyi.



> -----Original Message-----
> From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On
> Behalf Of Qin Wu
> Sent: Freitag, 2. Dezember 2011 02:55
> To: Schwarz, Albrecht (Albrecht); avt@ietf.org
> Cc: megaco@ietf.org
> Subject: Re: [AVTCORE] Types of monitoring architectures; RE:
> I-D Action: draft-ietf-avtcore-monarch-08.txt
>
> Hi, Albrecht:
> No offence, I am not really convinced with your proposal on
> physical monitoring architecture.
>  my counterquestion is what does physical monitoring
> architecture looks like in your mind?
> How many components do we have in such physical monitroing
> architecture? what are they?
> Take IMS network architecture as a example, they may have
> P-CSCF,S-CSCF, SIP PBX, SBC, why do you believe monitor
> described in draft-ietf-avtcore-monarch is mapped into
> P-CSCF, S-CSCF, SBC, Media Gateway, Media Gateway Controller
> should be in the scope of IETF RTP monitoring archtiecture draft?
>
> Monitor described in  draft-ietf-avtcore-monarch is well
> defined in the section 3 of RFC3550 as follows:
> "
>
>    Monitor: An application that receives RTCP packets sent by
>       participants in an RTP session, in particular the reception
>       reports, and estimates the current quality of service for
>       distribution monitoring, fault diagnosis and long-term
> statistics.
>       The monitor function is likely to be built into the
> application(s)
>       participating in the session, but may also be a separate
>       application that does not otherwise participate and
> does not send
>       or receive the RTP data packets (since they are on a separate
>       port).  These are called third-party monitors.  It is also
>       acceptable for a third-party monitor to receive the RTP data
>       packets but not send RTCP packets or otherwise be counted in the
>       session.
>
> "
> Isn't how to implent monitor into IMS netowork archtiecture a
> implentation specific issue?
> If this issue are really interesting, isn't it a good idea to
> produce another new document to talk about this?
> One good example for this motivation is this draft I like to
> share with you:
> http://tools.ietf.org/html/draft-kaplan-dispatch-b2bua-taxonom
> y-00#section-4.6
>
> Regards!
> -Qin
> ----- Original Message -----
> From: "Schwarz, Albrecht (Albrecht)"
> <albrecht.schwarz@alcatel-lucent.com>
> To: "Qin Wu" <bill.wu@huawei.com>; <avt@ietf.org>
> Cc: <megaco@ietf.org>
> Sent: Friday, December 02, 2011 12:20 AM
> Subject: RE: [AVTCORE] Types of monitoring architectures; RE:
> I-D Action: draft-ietf-avtcore-monarch-08.txt
>
>
> My replies below ...
> -Albrecht
>
> > -----Original Message-----
> > From: Qin Wu [mailto:bill.wu@huawei.com]
> > Sent: Donnerstag, 1. Dezember 2011 02:42
> > To: Schwarz, Albrecht (Albrecht); avt@ietf.org
> > Cc: megaco@ietf.org
> > Subject: Re: [AVTCORE] Types of monitoring architectures; RE:
> > I-D Action: draft-ietf-avtcore-monarch-08.txt
> >
> > Hi,
> > ----- Original Message -----
> > From: "Schwarz, Albrecht (Albrecht)"
> > <albrecht.schwarz@alcatel-lucent.com>
> > To: "Qin Wu" <bill.wu@huawei.com>; <avt@ietf.org>
> > Cc: <megaco@ietf.org>
> > Sent: Thursday, December 01, 2011 1:24 AM
> > Subject: RE: [AVTCORE] Types of monitoring architectures; RE:
> > I-D Action: draft-ietf-avtcore-monarch-08.txt
> >
> >
> > My replies below inline,
> > Albrecht
> >
> > > -----Original Message-----
> > > From: Qin Wu [mailto:bill.wu@huawei.com]
> > > Sent: Mittwoch, 30. November 2011 04:51
> > > To: Schwarz, Albrecht (Albrecht); avt@ietf.org
> > > Cc: megaco@ietf.org
> > > Subject: Re: [AVTCORE] Types of monitoring architectures; RE:
> > > I-D Action: draft-ietf-avtcore-monarch-08.txt
> > >
> > > Hi,
> > > ----- Original Message -----
> > > From: "Schwarz, Albrecht (Albrecht)"
> > > <albrecht.schwarz@alcatel-lucent.com>
> > > To: <avt@ietf.org>
> > > Cc: <megaco@ietf.org>
> > > Sent: Tuesday, November 29, 2011 7:32 PM
> > > Subject: [AVTCORE] Types of monitoring architectures; RE: I-D
> > > Action: draft-ietf-avtcore-monarch-08.txt
> > >
> > >
> > > > Dear All,
> > > >
> > > > there are different types of monitoring architectures,
> > > particularily from perspective of QoE related performance
> > parameters.
> > > > Let's recall QoE (e.g., ITU-T P.10 Amendment 2):
> > > >
> > > > Quality of Experience (QoE):
> > > > The overall acceptability of an application or service, as
> > > perceived subjectively by the end-user.
> > > > NOTE 1 - Quality of experience includes the complete
> > > end-to-end system effects (client, terminal, network,
> > > services infrastructure, etc.).
> > > > NOTE 2 - Overall acceptability may be influenced by user
> > > expectations and context.
> > > >
> > > > Important for MONARCH:
> > > > 1st ... perceived by end-user
> > > > 2nd QoE includes the complete end-to-end sytem effects ...
> > > >
> > > > That said, present RTP monitoring architecture in MONARCH
> > > according clause 3 is not specific on the type of monitoring
> > > architecture. For instance, Fig. 1, it is possibly supposed
> > > that the "RTP Sender" and "RTP Receiver" entities are equal
> > > to a terminal/user equipment (UE). This would be an
> > > end-to-end IP network scenario.
> > > >
> > > > However, the "RTP Sender" and "RTP Receiver" entities may
> > > be also located at the edge of an IP network, e.g. in a
> > > gateway for IP-to-non-IP interworking, i.e. an UE located in
> > > the non-IP network part.
> > > > Note: such scenarios are considered by MEGACO gateways
> > > (I've Cc'd megaco list).
> > > >
> > > > An RTP Sender/Receiver located NOT in the UE would question
> > > the value of RTP/RTCP QoE related performance measurements
> > > (because the UE is located outside the RTP domain).
> > > >
> > > > Conclusions:
> > > > - the set of meaningful performance metrics may be
> > > dependent on the location of the RTP Sender/Receiver, e.g.
> > > whether in a UE, gateway, ...
> > > > - don't see any impact on transport level metrics
> > > > - ... but the set of meaningful application level metrics
> > > >
> > > > Proposal for MONARCH:
> > > > #1: insert sub-clause title "3.1 End-to-end IP network
> > > architecture" below clause 3
> > > >
> > > > #2: add a sub-clause 3.2 at the end of clause 3, sth like
> > > >
> > > > "3.2 RTP Sender/Receiver entities located in network nodes
> > > > The location of the RTP Sender/Receiver entity may impact
> > > the set of meaningful metrics.
> > > > For instance: application level metrics for QoE related
> > > performance metrics are questionable (or doesn't really make
> > > sense at all) when measured in a network node (terminating
> > > the RTP) instead of the user equipment."
> > > >
> > > > Something like this would help to avoid confusion.
> > > > I even believe that a QoE measurement in a network node
> > > would violate the QoE definition. Would be rather something
> > > like QoE* ("remote QoE"):-(
> > > >
> > > > Such information would improve the MONARCH doc in my opinion.
> > > > Sorry for that late comment.
> > > > Any views?
> > >
> > > [Qin]:
> > > Albrrecht, if you follow ealry list discussion on
> > > draft-hunt-avt-monarch-01, you will see the rough consensus
> > > to position this document was
> > > this daft should focus on guidelines for defining reporting
> > > blocks. That is to say the main purpose of MONARCH draft
> is how to
> > > provide guidelines for the development of new RTCP XR block
> > > types in XRBlock working group.
> >
> > [ABS] ... then the title "monitoring architectures" is misleading.
> > Proposal: keep title, revise scope section on focus
> >
> > [Qin]: No, the title is *RTP* monitoring architecture, we can
> > not expand scope into IP monitoring architecture.
>
> [ABS] That's wasn't the intent! Did just focus on the key word.
>
> >
> > >
> > > Therefore how and where to collect the metric from RTP
> > > endpoint is not scope of this document, in my opinion. since
> > > you may have many ways to do this and different vendors have
> > > their different appoaches. It will be better to leave this
> > > beyond the scope. But you are right, it will be more
> > > reasonable to measure QoE related performance metric at the
> > > RTP receiver.
> >
> > [ABS] I would disagree. At least your statement should be
> > conditional, sth like
> > "QoE related performance metrics may be measured in a RTP
> > receiver, IF the RTP receiver function is located in user
> > equipment (e.g. IP terminal), because QoE performance metrics
> > are tightly coupled to the point of view of a 'user'.
> > ... IF NOT, then ..."
> >
> > [Qin]: I am not sure user equipment or IP terminal is the
> > right term from RTP perspective.
> >
> > Also if you read P.NAMS, P.NAMS model for calculating QoE
> > related metric can be placed either at the network or at the client.
> > So I disagree with what you said.
>
> [ABS] Not convinced at all.
> Guess you are referring to the "mid-point" models, right?
> The usage of such that models depends on "prior knowledge
> ..." information.
> Thus, the applicability is conditional. You may not make such
> a general statement.
>
>
> >
> > Also as I said, how and where to collect the metric from RTP
> >  endpoint is not scope of this document. It depends on the
> > model you are choosing, e.g., four operation modes specified
> > in P.NAMS.
> > Apparently this should not be specified again in RTP
> > monitoring architecture document.
> >
> > >
> > > Another point is it is not clear to me how RTP monitoring has
> > > to do with architectureend to end IP network architecture .
> > > this draft mostly focus on discussing RTP level stuff.
> > > Therefore I am quite doubt that we should describe anything
> > > in this document like how
> > > RTP entties is mapped into network entities/nodes at the IP layer.
> >
> > [ABS] I don't got any problems to talk about architectural
> > framework for monitoring in this document. Such information
> > is required and this is the only IETF AVT doc about it.
> > The solution to this issue is rather simple to me:
> > - split the MONARCH "monitoring architecture" in
> > 1) a functional monitoring architecture (let's call it 'FMA') and
> > 2) a physical monitoring architecture (... 'PMA').
> >
> > - the present MONARCH doc would describe the FMA at the level
> > of RTP entities (i.e., Fig. 1 entities, incl. all the RTP
> > topology components according RFC 5117)
> >
> > - there are many options of functional-to-physical mappings,
> > i.e. how a FMA would be mapped on a PMA
> > - the mapping is typically dependent on considered network
> > architecture (like SIP, H.323, MGCP, IMS, wireless, etc networks)
> >
> > - the present MONARCH doc would describe the FMA-to-PMA
> > mapping IF all RTP receiver/sender entities would be located
> > in physical IP terminals (UEs)
> > - etc
> >
> > [Qin]: I can understand your point, but you can not do that.
> > Since this document is only focus on *RTP* monitoring
> > architecture, that is what it said in AVTCore milestone:
> > "
> >
> > Goals and Milestones:
> >
> >   Feb 2011 - Submit Monitoring Architecture for RTP for
> Informational
> >
> > "
>
> [ABS] If you go back to my first email on this subject, and
> if you look at my proposal: that's not a lot, nothing which
> violates the charter, goals and milestones.
>
>
> > Also if you really don't see how to map FMA to PMA, you may
> > look at the P.NAMS models specifed in ITU-T P.NAMS.
> > As for how to use RTP monitoring architecture or RTP XR
> > Report in the IMS network architecture, you may look at:
> > http://tools.ietf.org/html/rfc6035
>
> [ABS] That's the SIP reporting interface, i.e., applicable
> primarily for physical IP user equipment with embedded RTP
> sender/receiver function and SIP UA function.
> However, the applicability of RFC 6035 is limited for a
> SIP-to-PSTN gateway (because the RTP sender/receiver would be
> located NOT in user equipment. Also the P.NAMS mid-point
> model fails for such a scenario.
>
> > ITU-T H.248.48.
> > But I haven't check the current status of H.248.48.
>
> [ABS] Work is finalized, see
> http://www.itu.int/md/meetingdoc.asp?lang=en&parent=T09-SG16-1
> 11121-TD-PLEN-0419
>
> >
> > >
> > > But as the author of this document, I am interested and open
> > > to other opinions.:-)
> >
> > [ABS] Like to add a further aspect: a "functional monitoring
> > architecture" may be considered as a network overlay,
> > something which adds additional capabilities (here:
> > measurement services, reporting services on top of basic RTP
> > services).
> > Such an overlay concept is nothing new: e.g., the
> > MultiService Forum did define a "Performance Measurement &
> > Monitoring (PMM)" overlay network, or IETF RMON may be also
> > considered as such.
> >
> > >
> > > > Regards,
> > > > Albrecht
> > > >
> > > >
> > > >
> > > >
> > > >> -----Original Message-----
> > > >> From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On
> > > >> Behalf Of internet-drafts@ietf.org
> > > >> Sent: Dienstag, 29. November 2011 08:56
> > > >> To: i-d-announce@ietf.org
> > > >> Cc: avt@ietf.org
> > > >> Subject: [AVTCORE] I-D Action:
> draft-ietf-avtcore-monarch-08.txt
> > > >>
> > > >>
> > > >> A New Internet-Draft is available from the on-line
> > > >> Internet-Drafts directories. This draft is a work item of the
> > > >> Audio/Video Transport Core Maintenance Working Group
> of the IETF.
> > > >>
> > > >> Title           : Monitoring Architectures for RTP
> > > >> Author(s)       : Qin Wu
> > > >>                           Geoff Hunt
> > > >>                           Philip Arden
> > > >> Filename        : draft-ietf-avtcore-monarch-08.txt
> > > >> Pages           : 25
> > > >> Date            : 2011-11-28
> > > >>
> > > >>    This memo proposes an architecture for extending RTCP with
> > > >> a new RTCP
> > > >>    XR (RFC3611) block type to report new metrics
> regarding media
> > > >>    transmission or reception quality, following RTCP guideline
> > > >>    established in RFC5968.  This memo suggests that a new
> > > block should
> > > >>    contain a single metric or a small number of metrics
> > > relevant to a
> > > >>    single parameter of interest or concern, rather than
> > > containing a
> > > >>    number of metrics which attempt to provide full coverage
> > > >> of all those
> > > >>    parameters of concern to a specific application.
> > > Applications may
> > > >>    then "mix and match" to create a set of blocks which
> > > >> covers their set
> > > >>    of concerns.  Where possible, a specific block should be
> > > >> designed to
> > > >>    be re-usable across more than one application, for
> > > example, for all
> > > >>    of voice, streaming audio and video.
> > > >>
> > > >>
> > > >> A URL for this Internet-Draft is:
> > > >>
> > >
> >
> http://www.ietf.org/internet-drafts/draft-ietf-avtcore-monarch-08.txt
> > > >>
> > > >> Internet-Drafts are also available by anonymous FTP at:
> > > >> ftp://ftp.ietf.org/internet-drafts/
> > > >>
> > > >> This Internet-Draft can be retrieved at:
> > > >>
> > >
> ftp://ftp.ietf.org/internet-drafts/draft-ietf-avtcore-monarch-08.txt
> > > >>
> > > >> _______________________________________________
> > > >> Audio/Video Transport Core Maintenance
> > > >> avt@ietf.org
> > > >> https://www.ietf.org/mailman/listinfo/avt
> > > >>
> > > > _______________________________________________
> > > > Audio/Video Transport Core Maintenance
> > > > avt@ietf.org
> > > > https://www.ietf.org/mailman/listinfo/avt
> > >
> > =
> _______________________________________________
> Audio/Video Transport Core Maintenance
> avt@ietf.org
> https://www.ietf.org/mailman/listinfo/avt
>

From albrecht.schwarz@alcatel-lucent.com  Wed Dec  7 08:25:01 2011
Return-Path: <albrecht.schwarz@alcatel-lucent.com>
X-Original-To: megaco@ietfa.amsl.com
Delivered-To: megaco@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 561E321F8C7A; Wed,  7 Dec 2011 08:25:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.668
X-Spam-Level: 
X-Spam-Status: No, score=-5.668 tagged_above=-999 required=5 tests=[AWL=-0.019, BAYES_00=-2.599, HELO_EQ_FR=0.35, J_CHICKENPOX_14=0.6, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KJPYPjNh14u9; Wed,  7 Dec 2011 08:24:59 -0800 (PST)
Received: from smail2.alcatel.fr (smail2.alcatel.fr [64.208.49.57]) by ietfa.amsl.com (Postfix) with ESMTP id 2AAC221F8C51; Wed,  7 Dec 2011 08:24:58 -0800 (PST)
Received: from FRMRSSXCHHUB03.dc-m.alcatel-lucent.com (FRMRSSXCHHUB03.dc-m.alcatel-lucent.com [135.120.45.63]) by smail2.alcatel.fr (8.14.3/8.14.3/ICT) with ESMTP id pB7GOJ4v023844 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Wed, 7 Dec 2011 17:24:27 +0100
Received: from FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com ([135.120.45.50]) by FRMRSSXCHHUB03.dc-m.alcatel-lucent.com ([135.120.45.63]) with mapi; Wed, 7 Dec 2011 17:24:25 +0100
From: "Schwarz, Albrecht (Albrecht)" <albrecht.schwarz@alcatel-lucent.com>
To: Qin Wu <bill.wu@huawei.com>, "avt@ietf.org" <avt@ietf.org>
Date: Wed, 7 Dec 2011 17:24:24 +0100
Thread-Topic: [AVTCORE] Types of monitoring architectures; RE:  I-D Action: draft-ietf-avtcore-monarch-08.txt
Thread-Index: Acyz3rfKeCMWWyKTRsuT81eZDiECHgBHEUng
Message-ID: <5F7BCCF5541B7444830A2288ABBEBC9621620F4ED2@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com>
References: <20111129075613.12419.4377.idtracker@ietfa.amsl.com> <5F7BCCF5541B7444830A2288ABBEBC96216190051A@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com> <EAC481B4D8034C38AC54E1217F8D875D@china.huawei.com> <5F7BCCF5541B7444830A2288ABBEBC96216190077F@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com> <B527BAFA038842A8939A8C2D558074CD@china.huawei.com> <5F7BCCF5541B7444830A2288ABBEBC962161900908@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com> <9FF9B04A84E64AD7ABCCC4F2ACC1E19A@china.huawei.com> <5F7BCCF5541B7444830A2288ABBEBC9621620F4AF5@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com> <D44A4820E0D24DD79F6F5A4B7507D0D6@china.huawei.com>
In-Reply-To: <D44A4820E0D24DD79F6F5A4B7507D0D6@china.huawei.com>
Accept-Language: de-DE, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: de-DE, en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.69 on 155.132.188.80
Cc: "megaco@ietf.org" <megaco@ietf.org>
Subject: Re: [Megaco] [AVTCORE] Types of monitoring architectures; RE:  I-D Action: draft-ietf-avtcore-monarch-08.txt
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.1.12
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, 07 Dec 2011 16:25:01 -0000

Qin,
that's NOT the point.

All RFC 3550 and RFC 5117 RTP components are FUNCTIONAL ENTITIES (FE).
e.g.,
- the RTP Monitor or RTP receiver FE may be located in different PHYSICAL E=
NTITIES (PE), e.g.
        a1) a user equipment
        a2) a RTP-to-PSTN gateway
        a3) an IP-to-IP session border gateway (in a back-to-back RTP endsy=
stem topology)
        a3) ...

- the RTP Monitor may be associated to an RTP transport translator ...
        b1) an IP-to-IP session border gateway

The "RTP monitoring architecture" is IMPACTED by each functional-to-physica=
l mapping because e.g.
* QoE related metrics are questionable in case of a2 ("despite the fact of =
a RTP receiver function")
* application level metrics at the location of a RTP transport translator a=
re a contradiction in itself
* ...

Again, it's not really changing the MONARCH draft because in the very major=
ity of scenarios it is correct. However, there are few cases where the MONA=
RCH description would be "too high level", "not fully correct", "lead to po=
ssible wrong expectations", ...

Regards,
Albrecht



> -----Original Message-----
> From: Qin Wu [mailto:bill.wu@huawei.com]
> Sent: Dienstag, 6. Dezember 2011 07:13
> To: Schwarz, Albrecht (Albrecht); avt@ietf.org
> Cc: megaco@ietf.org
> Subject: Re: [AVTCORE] Types of monitoring architectures; RE:
> I-D Action: draft-ietf-avtcore-monarch-08.txt
>
> If you talk about existing RFC5117 RTP topology components,
> this has already been covered by the current version of
> draft-ietf-avtcore-monarch.
> In most cases, an RTP system using RTCP XR is architecturally
> no different from an RTP system which does not use RTCP XR.
>
> Regards!
> -Qin
> ----- Original Message -----
> From: "Schwarz, Albrecht (Albrecht)"
> <albrecht.schwarz@alcatel-lucent.com>
> To: "Qin Wu" <bill.wu@huawei.com>; <avt@ietf.org>
> Cc: <megaco@ietf.org>
> Sent: Monday, December 05, 2011 10:48 PM
> Subject: RE: [AVTCORE] Types of monitoring architectures; RE:
> I-D Action: draft-ietf-avtcore-monarch-08.txt
>
>
> Hello Qin,
>
> to 1) Physical monitoring architecture
> Of course consideration of generic physical entities (PE),
> not specific to any network reference architectures defined
> by SDOs (like your refered entities).
> There would be just a few PE types ("given by the limited set
> of RTP topology components (RFC 5117)").
>
> to 2) (RFC 3550) Monitor function
> Right, that's a functional entity. The applicability of a
> monitor may be limited, dependent on ... (like in P.NAMS).
>
> to 3) your IMS network example
> Don't see the need to refer from MONARCH to a specific
> network architecture like IMS.
> Please also note that IMS is a functional architecture, not a
> physical architecture.
>
> Regards,
> Albrecht
>
> PS
> There are multiple options for adding the "RTP monitoring
> architecture" to a functional/physical network architecture:
> a) integrated approach: extension of existing functional
> entities or/and addition of RTP monitoring architectural
> components, extension or/and addition of
> signalling/management interfaces for control and
> configuration of RTP monitoring services, and reporting
> interfaces for measurement data ...
> b) overlay approach: separate specification to ...
>
>
> PSS
> BTW: there's a discussion paper with regards to the location
> of a monitor function in an IMS H.248 gateway entity:
> Measurements and statistics in IMS - Use Cases
> http://www.3gpp.org/ftp/tsg_ct/WG3_interworking_ex-CN3/TSGC3_5
> 8_Kyoto_Japan/Docs/C3-100469.zip
> This is just fyi.
>
>
>
> > -----Original Message-----
> > From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On
> > Behalf Of Qin Wu
> > Sent: Freitag, 2. Dezember 2011 02:55
> > To: Schwarz, Albrecht (Albrecht); avt@ietf.org
> > Cc: megaco@ietf.org
> > Subject: Re: [AVTCORE] Types of monitoring architectures; RE:
> > I-D Action: draft-ietf-avtcore-monarch-08.txt
> >
> > Hi, Albrecht:
> > No offence, I am not really convinced with your proposal on
> > physical monitoring architecture.
> >  my counterquestion is what does physical monitoring
> > architecture looks like in your mind?
> > How many components do we have in such physical monitroing
> > architecture? what are they?
> > Take IMS network architecture as a example, they may have
> > P-CSCF,S-CSCF, SIP PBX, SBC, why do you believe monitor
> > described in draft-ietf-avtcore-monarch is mapped into
> > P-CSCF, S-CSCF, SBC, Media Gateway, Media Gateway Controller
> > should be in the scope of IETF RTP monitoring archtiecture draft?
> >
> > Monitor described in  draft-ietf-avtcore-monarch is well
> > defined in the section 3 of RFC3550 as follows:
> > "
> >
> >    Monitor: An application that receives RTCP packets sent by
> >       participants in an RTP session, in particular the reception
> >       reports, and estimates the current quality of service for
> >       distribution monitoring, fault diagnosis and long-term
> > statistics.
> >       The monitor function is likely to be built into the
> > application(s)
> >       participating in the session, but may also be a separate
> >       application that does not otherwise participate and
> > does not send
> >       or receive the RTP data packets (since they are on a separate
> >       port).  These are called third-party monitors.  It is also
> >       acceptable for a third-party monitor to receive the RTP data
> >       packets but not send RTCP packets or otherwise be
> counted in the
> >       session.
> >
> > "
> > Isn't how to implent monitor into IMS netowork archtiecture a
> > implentation specific issue?
> > If this issue are really interesting, isn't it a good idea to
> > produce another new document to talk about this?
> > One good example for this motivation is this draft I like to
> > share with you:
> > http://tools.ietf.org/html/draft-kaplan-dispatch-b2bua-taxonom
> > y-00#section-4.6
> >
> > Regards!
> > -Qin
> > ----- Original Message -----
> > From: "Schwarz, Albrecht (Albrecht)"
> > <albrecht.schwarz@alcatel-lucent.com>
> > To: "Qin Wu" <bill.wu@huawei.com>; <avt@ietf.org>
> > Cc: <megaco@ietf.org>
> > Sent: Friday, December 02, 2011 12:20 AM
> > Subject: RE: [AVTCORE] Types of monitoring architectures; RE:
> > I-D Action: draft-ietf-avtcore-monarch-08.txt
> >
> >
> > My replies below ...
> > -Albrecht
> >
> > > -----Original Message-----
> > > From: Qin Wu [mailto:bill.wu@huawei.com]
> > > Sent: Donnerstag, 1. Dezember 2011 02:42
> > > To: Schwarz, Albrecht (Albrecht); avt@ietf.org
> > > Cc: megaco@ietf.org
> > > Subject: Re: [AVTCORE] Types of monitoring architectures; RE:
> > > I-D Action: draft-ietf-avtcore-monarch-08.txt
> > >
> > > Hi,
> > > ----- Original Message -----
> > > From: "Schwarz, Albrecht (Albrecht)"
> > > <albrecht.schwarz@alcatel-lucent.com>
> > > To: "Qin Wu" <bill.wu@huawei.com>; <avt@ietf.org>
> > > Cc: <megaco@ietf.org>
> > > Sent: Thursday, December 01, 2011 1:24 AM
> > > Subject: RE: [AVTCORE] Types of monitoring architectures; RE:
> > > I-D Action: draft-ietf-avtcore-monarch-08.txt
> > >
> > >
> > > My replies below inline,
> > > Albrecht
> > >
> > > > -----Original Message-----
> > > > From: Qin Wu [mailto:bill.wu@huawei.com]
> > > > Sent: Mittwoch, 30. November 2011 04:51
> > > > To: Schwarz, Albrecht (Albrecht); avt@ietf.org
> > > > Cc: megaco@ietf.org
> > > > Subject: Re: [AVTCORE] Types of monitoring architectures; RE:
> > > > I-D Action: draft-ietf-avtcore-monarch-08.txt
> > > >
> > > > Hi,
> > > > ----- Original Message -----
> > > > From: "Schwarz, Albrecht (Albrecht)"
> > > > <albrecht.schwarz@alcatel-lucent.com>
> > > > To: <avt@ietf.org>
> > > > Cc: <megaco@ietf.org>
> > > > Sent: Tuesday, November 29, 2011 7:32 PM
> > > > Subject: [AVTCORE] Types of monitoring architectures; RE: I-D
> > > > Action: draft-ietf-avtcore-monarch-08.txt
> > > >
> > > >
> > > > > Dear All,
> > > > >
> > > > > there are different types of monitoring architectures,
> > > > particularily from perspective of QoE related performance
> > > parameters.
> > > > > Let's recall QoE (e.g., ITU-T P.10 Amendment 2):
> > > > >
> > > > > Quality of Experience (QoE):
> > > > > The overall acceptability of an application or service, as
> > > > perceived subjectively by the end-user.
> > > > > NOTE 1 - Quality of experience includes the complete
> > > > end-to-end system effects (client, terminal, network,
> > > > services infrastructure, etc.).
> > > > > NOTE 2 - Overall acceptability may be influenced by user
> > > > expectations and context.
> > > > >
> > > > > Important for MONARCH:
> > > > > 1st ... perceived by end-user
> > > > > 2nd QoE includes the complete end-to-end sytem effects ...
> > > > >
> > > > > That said, present RTP monitoring architecture in MONARCH
> > > > according clause 3 is not specific on the type of monitoring
> > > > architecture. For instance, Fig. 1, it is possibly supposed
> > > > that the "RTP Sender" and "RTP Receiver" entities are equal
> > > > to a terminal/user equipment (UE). This would be an
> > > > end-to-end IP network scenario.
> > > > >
> > > > > However, the "RTP Sender" and "RTP Receiver" entities may
> > > > be also located at the edge of an IP network, e.g. in a
> > > > gateway for IP-to-non-IP interworking, i.e. an UE located in
> > > > the non-IP network part.
> > > > > Note: such scenarios are considered by MEGACO gateways
> > > > (I've Cc'd megaco list).
> > > > >
> > > > > An RTP Sender/Receiver located NOT in the UE would question
> > > > the value of RTP/RTCP QoE related performance measurements
> > > > (because the UE is located outside the RTP domain).
> > > > >
> > > > > Conclusions:
> > > > > - the set of meaningful performance metrics may be
> > > > dependent on the location of the RTP Sender/Receiver, e.g.
> > > > whether in a UE, gateway, ...
> > > > > - don't see any impact on transport level metrics
> > > > > - ... but the set of meaningful application level metrics
> > > > >
> > > > > Proposal for MONARCH:
> > > > > #1: insert sub-clause title "3.1 End-to-end IP network
> > > > architecture" below clause 3
> > > > >
> > > > > #2: add a sub-clause 3.2 at the end of clause 3, sth like
> > > > >
> > > > > "3.2 RTP Sender/Receiver entities located in network nodes
> > > > > The location of the RTP Sender/Receiver entity may impact
> > > > the set of meaningful metrics.
> > > > > For instance: application level metrics for QoE related
> > > > performance metrics are questionable (or doesn't really make
> > > > sense at all) when measured in a network node (terminating
> > > > the RTP) instead of the user equipment."
> > > > >
> > > > > Something like this would help to avoid confusion.
> > > > > I even believe that a QoE measurement in a network node
> > > > would violate the QoE definition. Would be rather something
> > > > like QoE* ("remote QoE"):-(
> > > > >
> > > > > Such information would improve the MONARCH doc in my opinion.
> > > > > Sorry for that late comment.
> > > > > Any views?
> > > >
> > > > [Qin]:
> > > > Albrrecht, if you follow ealry list discussion on
> > > > draft-hunt-avt-monarch-01, you will see the rough consensus
> > > > to position this document was
> > > > this daft should focus on guidelines for defining reporting
> > > > blocks. That is to say the main purpose of MONARCH draft
> > is how to
> > > > provide guidelines for the development of new RTCP XR block
> > > > types in XRBlock working group.
> > >
> > > [ABS] ... then the title "monitoring architectures" is misleading.
> > > Proposal: keep title, revise scope section on focus
> > >
> > > [Qin]: No, the title is *RTP* monitoring architecture, we can
> > > not expand scope into IP monitoring architecture.
> >
> > [ABS] That's wasn't the intent! Did just focus on the key word.
> >
> > >
> > > >
> > > > Therefore how and where to collect the metric from RTP
> > > > endpoint is not scope of this document, in my opinion. since
> > > > you may have many ways to do this and different vendors have
> > > > their different appoaches. It will be better to leave this
> > > > beyond the scope. But you are right, it will be more
> > > > reasonable to measure QoE related performance metric at the
> > > > RTP receiver.
> > >
> > > [ABS] I would disagree. At least your statement should be
> > > conditional, sth like
> > > "QoE related performance metrics may be measured in a RTP
> > > receiver, IF the RTP receiver function is located in user
> > > equipment (e.g. IP terminal), because QoE performance metrics
> > > are tightly coupled to the point of view of a 'user'.
> > > ... IF NOT, then ..."
> > >
> > > [Qin]: I am not sure user equipment or IP terminal is the
> > > right term from RTP perspective.
> > >
> > > Also if you read P.NAMS, P.NAMS model for calculating QoE
> > > related metric can be placed either at the network or at
> the client.
> > > So I disagree with what you said.
> >
> > [ABS] Not convinced at all.
> > Guess you are referring to the "mid-point" models, right?
> > The usage of such that models depends on "prior knowledge
> > ..." information.
> > Thus, the applicability is conditional. You may not make such
> > a general statement.
> >
> >
> > >
> > > Also as I said, how and where to collect the metric from RTP
> > >  endpoint is not scope of this document. It depends on the
> > > model you are choosing, e.g., four operation modes specified
> > > in P.NAMS.
> > > Apparently this should not be specified again in RTP
> > > monitoring architecture document.
> > >
> > > >
> > > > Another point is it is not clear to me how RTP monitoring has
> > > > to do with architectureend to end IP network architecture .
> > > > this draft mostly focus on discussing RTP level stuff.
> > > > Therefore I am quite doubt that we should describe anything
> > > > in this document like how
> > > > RTP entties is mapped into network entities/nodes at
> the IP layer.
> > >
> > > [ABS] I don't got any problems to talk about architectural
> > > framework for monitoring in this document. Such information
> > > is required and this is the only IETF AVT doc about it.
> > > The solution to this issue is rather simple to me:
> > > - split the MONARCH "monitoring architecture" in
> > > 1) a functional monitoring architecture (let's call it 'FMA') and
> > > 2) a physical monitoring architecture (... 'PMA').
> > >
> > > - the present MONARCH doc would describe the FMA at the level
> > > of RTP entities (i.e., Fig. 1 entities, incl. all the RTP
> > > topology components according RFC 5117)
> > >
> > > - there are many options of functional-to-physical mappings,
> > > i.e. how a FMA would be mapped on a PMA
> > > - the mapping is typically dependent on considered network
> > > architecture (like SIP, H.323, MGCP, IMS, wireless, etc networks)
> > >
> > > - the present MONARCH doc would describe the FMA-to-PMA
> > > mapping IF all RTP receiver/sender entities would be located
> > > in physical IP terminals (UEs)
> > > - etc
> > >
> > > [Qin]: I can understand your point, but you can not do that.
> > > Since this document is only focus on *RTP* monitoring
> > > architecture, that is what it said in AVTCore milestone:
> > > "
> > >
> > > Goals and Milestones:
> > >
> > >   Feb 2011 - Submit Monitoring Architecture for RTP for
> > Informational
> > >
> > > "
> >
> > [ABS] If you go back to my first email on this subject, and
> > if you look at my proposal: that's not a lot, nothing which
> > violates the charter, goals and milestones.
> >
> >
> > > Also if you really don't see how to map FMA to PMA, you may
> > > look at the P.NAMS models specifed in ITU-T P.NAMS.
> > > As for how to use RTP monitoring architecture or RTP XR
> > > Report in the IMS network architecture, you may look at:
> > > http://tools.ietf.org/html/rfc6035
> >
> > [ABS] That's the SIP reporting interface, i.e., applicable
> > primarily for physical IP user equipment with embedded RTP
> > sender/receiver function and SIP UA function.
> > However, the applicability of RFC 6035 is limited for a
> > SIP-to-PSTN gateway (because the RTP sender/receiver would be
> > located NOT in user equipment. Also the P.NAMS mid-point
> > model fails for such a scenario.
> >
> > > ITU-T H.248.48.
> > > But I haven't check the current status of H.248.48.
> >
> > [ABS] Work is finalized, see
> > http://www.itu.int/md/meetingdoc.asp?lang=3Den&parent=3DT09-SG16-1
> > 11121-TD-PLEN-0419
> >
> > >
> > > >
> > > > But as the author of this document, I am interested and open
> > > > to other opinions.:-)
> > >
> > > [ABS] Like to add a further aspect: a "functional monitoring
> > > architecture" may be considered as a network overlay,
> > > something which adds additional capabilities (here:
> > > measurement services, reporting services on top of basic RTP
> > > services).
> > > Such an overlay concept is nothing new: e.g., the
> > > MultiService Forum did define a "Performance Measurement &
> > > Monitoring (PMM)" overlay network, or IETF RMON may be also
> > > considered as such.
> > >
> > > >
> > > > > Regards,
> > > > > Albrecht
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >> -----Original Message-----
> > > > >> From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On
> > > > >> Behalf Of internet-drafts@ietf.org
> > > > >> Sent: Dienstag, 29. November 2011 08:56
> > > > >> To: i-d-announce@ietf.org
> > > > >> Cc: avt@ietf.org
> > > > >> Subject: [AVTCORE] I-D Action:
> > draft-ietf-avtcore-monarch-08.txt
> > > > >>
> > > > >>
> > > > >> A New Internet-Draft is available from the on-line
> > > > >> Internet-Drafts directories. This draft is a work item of the
> > > > >> Audio/Video Transport Core Maintenance Working Group
> > of the IETF.
> > > > >>
> > > > >> Title           : Monitoring Architectures for RTP
> > > > >> Author(s)       : Qin Wu
> > > > >>                           Geoff Hunt
> > > > >>                           Philip Arden
> > > > >> Filename        : draft-ietf-avtcore-monarch-08.txt
> > > > >> Pages           : 25
> > > > >> Date            : 2011-11-28
> > > > >>
> > > > >>    This memo proposes an architecture for extending RTCP with
> > > > >> a new RTCP
> > > > >>    XR (RFC3611) block type to report new metrics
> > regarding media
> > > > >>    transmission or reception quality, following RTCP
> guideline
> > > > >>    established in RFC5968.  This memo suggests that a new
> > > > block should
> > > > >>    contain a single metric or a small number of metrics
> > > > relevant to a
> > > > >>    single parameter of interest or concern, rather than
> > > > containing a
> > > > >>    number of metrics which attempt to provide full coverage
> > > > >> of all those
> > > > >>    parameters of concern to a specific application.
> > > > Applications may
> > > > >>    then "mix and match" to create a set of blocks which
> > > > >> covers their set
> > > > >>    of concerns.  Where possible, a specific block should be
> > > > >> designed to
> > > > >>    be re-usable across more than one application, for
> > > > example, for all
> > > > >>    of voice, streaming audio and video.
> > > > >>
> > > > >>
> > > > >> A URL for this Internet-Draft is:
> > > > >>
> > > >
> > >
> >
> http://www.ietf.org/internet-drafts/draft-ietf-avtcore-monarch-08.txt
> > > > >>
> > > > >> Internet-Drafts are also available by anonymous FTP at:
> > > > >> ftp://ftp.ietf.org/internet-drafts/
> > > > >>
> > > > >> This Internet-Draft can be retrieved at:
> > > > >>
> > > >
> > ftp://ftp.ietf.org/internet-drafts/draft-ietf-avtcore-monarch-08.txt
> > > > >>
> > > > >> _______________________________________________
> > > > >> Audio/Video Transport Core Maintenance
> > > > >> avt@ietf.org
> > > > >> https://www.ietf.org/mailman/listinfo/avt
> > > > >>
> > > > > _______________________________________________
> > > > > Audio/Video Transport Core Maintenance
> > > > > avt@ietf.org
> > > > > https://www.ietf.org/mailman/listinfo/avt
> > > >
> > > =3D
> > _______________________________________________
> > Audio/Video Transport Core Maintenance
> > avt@ietf.org
> > https://www.ietf.org/mailman/listinfo/avt
> >
>

From bill.wu@huawei.com  Wed Dec  7 18:27:46 2011
Return-Path: <bill.wu@huawei.com>
X-Original-To: megaco@ietfa.amsl.com
Delivered-To: megaco@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6909811E8099; Wed,  7 Dec 2011 18:27:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.08
X-Spam-Level: 
X-Spam-Status: No, score=-6.08 tagged_above=-999 required=5 tests=[AWL=-0.081,  BAYES_00=-2.599, J_CHICKENPOX_14=0.6, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6M-rCTwlbIpp; Wed,  7 Dec 2011 18:27:44 -0800 (PST)
Received: from szxga03-in.huawei.com (szxga03-in.huawei.com [119.145.14.66]) by ietfa.amsl.com (Postfix) with ESMTP id 0907C11E80B4; Wed,  7 Dec 2011 18:27:44 -0800 (PST)
Received: from huawei.com (szxga03-in [172.24.2.9]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LVV00EXG5FCZJ@szxga03-in.huawei.com>; Thu, 08 Dec 2011 10:26:00 +0800 (CST)
Received: from szxrg01-dlp.huawei.com ([172.24.2.119]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LVV00BK25FCZ0@szxga03-in.huawei.com>; Thu, 08 Dec 2011 10:26:00 +0800 (CST)
Received: from szxeml207-edg.china.huawei.com ([172.24.2.119]) by szxrg01-dlp.huawei.com (MOS 4.1.9-GA)	with ESMTP id AFQ35216; Thu, 08 Dec 2011 10:26:00 +0800
Received: from SZXEML408-HUB.china.huawei.com (10.82.67.95) by szxeml207-edg.china.huawei.com (172.24.2.59) with Microsoft SMTP Server (TLS) id 14.1.323.3; Thu, 08 Dec 2011 10:25:54 +0800
Received: from w53375q (10.138.41.130) by szxeml408-hub.china.huawei.com (10.82.67.95) with Microsoft SMTP Server (TLS) id 14.1.323.3; Thu, 08 Dec 2011 10:25:55 +0800
Date: Thu, 08 Dec 2011 10:25:54 +0800
From: Qin Wu <bill.wu@huawei.com>
X-Originating-IP: [10.138.41.130]
To: "Schwarz, Albrecht (Albrecht)" <albrecht.schwarz@alcatel-lucent.com>, avt@ietf.org
Message-id: <71112008FBA94D35B07FA6B4916075B6@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.6109
X-Mailer: Microsoft Outlook Express 6.00.2900.5931
Content-type: text/plain; charset=ISO-8859-1
Content-transfer-encoding: 7BIT
X-Priority: 3
X-MSMail-priority: Normal
X-CFilter-Loop: Reflected
References: <20111129075613.12419.4377.idtracker@ietfa.amsl.com> <5F7BCCF5541B7444830A2288ABBEBC96216190051A@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com> <EAC481B4D8034C38AC54E1217F8D875D@china.huawei.com> <5F7BCCF5541B7444830A2288ABBEBC96216190077F@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com> <B527BAFA038842A8939A8C2D558074CD@china.huawei.com> <5F7BCCF5541B7444830A2288ABBEBC962161900908@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com> <9FF9B04A84E64AD7ABCCC4F2ACC1E19A@china.huawei.com> <5F7BCCF5541B7444830A2288ABBEBC9621620F4AF5@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com> <D44A4820E0D24DD79F6F5A4B7507D0D6@china.huawei.com> <5F7BCCF5541B7444830A2288ABBEBC9621620F4ED2@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com>
Cc: megaco@ietf.org
Subject: Re: [Megaco] [AVTCORE] Types of monitoring architectures; RE:  I-D Action: draft-ietf-avtcore-monarch-08.txt
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.1.12
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: Thu, 08 Dec 2011 02:27:46 -0000

You reiterate what you propose for physical entities in the early email.
I am still not convicing with that.

Since we have RTP components like RTP end system, RTP mixer, RTP media translator, RTP transport translator,
RTP monitor specified in RFC3550 can be built into these component as a application. also monitor can be disjointed 
from these RTP components as a third party monitor. why we need to specify how to map RTP end system into user equipment,
RTP translator or RTP mixer can be mapped into RTP-PSTN gateway, or IP to IP border gateway since we have already mapped monitor
into different RTP components. 
How many PE types you can enumerate? why they should be scope of RTP monitoring architecture?

Also as specified in MONARCH draft, we have end sytem metrics, transport level metric, transport level metric, they can be measured and collected from the different RTP
comoponents specified in RFC3550, RFC5117. Apparently end system metric can only be collected from RTP end system.
transport metric is collected from any RTP system in the RTP monitoring architecture, 
regarding application level metric, apparently they should be measured at the application layer and can not be collected from RTP transport translator, Also RTP transport translator is still 
a functional entity rather than a physical entity. I am not convincing with what you said about "contradiction", "lead to possible wrong expectations".

Regards!
-Qin
----- Original Message ----- 
From: "Schwarz, Albrecht (Albrecht)" <albrecht.schwarz@alcatel-lucent.com>
To: "Qin Wu" <bill.wu@huawei.com>; <avt@ietf.org>
Cc: <megaco@ietf.org>
Sent: Thursday, December 08, 2011 12:24 AM
Subject: RE: [AVTCORE] Types of monitoring architectures; RE: I-D Action: draft-ietf-avtcore-monarch-08.txt


Qin,
that's NOT the point.

All RFC 3550 and RFC 5117 RTP components are FUNCTIONAL ENTITIES (FE).
e.g.,
- the RTP Monitor or RTP receiver FE may be located in different PHYSICAL ENTITIES (PE), e.g.
        a1) a user equipment
        a2) a RTP-to-PSTN gateway
        a3) an IP-to-IP session border gateway (in a back-to-back RTP endsystem topology)
        a3) ...

- the RTP Monitor may be associated to an RTP transport translator ...
        b1) an IP-to-IP session border gateway

The "RTP monitoring architecture" is IMPACTED by each functional-to-physical mapping because e.g.
* QoE related metrics are questionable in case of a2 ("despite the fact of a RTP receiver function")
* application level metrics at the location of a RTP transport translator are a contradiction in itself
* ...

Again, it's not really changing the MONARCH draft because in the very majority of scenarios it is correct. However, there are few cases where the MONARCH description would be "too high level", "not fully correct", "lead to possible wrong expectations", ...

Regards,
Albrecht



> -----Original Message-----
> From: Qin Wu [mailto:bill.wu@huawei.com]
> Sent: Dienstag, 6. Dezember 2011 07:13
> To: Schwarz, Albrecht (Albrecht); avt@ietf.org
> Cc: megaco@ietf.org
> Subject: Re: [AVTCORE] Types of monitoring architectures; RE:
> I-D Action: draft-ietf-avtcore-monarch-08.txt
>
> If you talk about existing RFC5117 RTP topology components,
> this has already been covered by the current version of
> draft-ietf-avtcore-monarch.
> In most cases, an RTP system using RTCP XR is architecturally
> no different from an RTP system which does not use RTCP XR.
>
> Regards!
> -Qin
> ----- Original Message -----
> From: "Schwarz, Albrecht (Albrecht)"
> <albrecht.schwarz@alcatel-lucent.com>
> To: "Qin Wu" <bill.wu@huawei.com>; <avt@ietf.org>
> Cc: <megaco@ietf.org>
> Sent: Monday, December 05, 2011 10:48 PM
> Subject: RE: [AVTCORE] Types of monitoring architectures; RE:
> I-D Action: draft-ietf-avtcore-monarch-08.txt
>
>
> Hello Qin,
>
> to 1) Physical monitoring architecture
> Of course consideration of generic physical entities (PE),
> not specific to any network reference architectures defined
> by SDOs (like your refered entities).
> There would be just a few PE types ("given by the limited set
> of RTP topology components (RFC 5117)").
>
> to 2) (RFC 3550) Monitor function
> Right, that's a functional entity. The applicability of a
> monitor may be limited, dependent on ... (like in P.NAMS).
>
> to 3) your IMS network example
> Don't see the need to refer from MONARCH to a specific
> network architecture like IMS.
> Please also note that IMS is a functional architecture, not a
> physical architecture.
>
> Regards,
> Albrecht
>
> PS
> There are multiple options for adding the "RTP monitoring
> architecture" to a functional/physical network architecture:
> a) integrated approach: extension of existing functional
> entities or/and addition of RTP monitoring architectural
> components, extension or/and addition of
> signalling/management interfaces for control and
> configuration of RTP monitoring services, and reporting
> interfaces for measurement data ...
> b) overlay approach: separate specification to ...
>
>
> PSS
> BTW: there's a discussion paper with regards to the location
> of a monitor function in an IMS H.248 gateway entity:
> Measurements and statistics in IMS - Use Cases
> http://www.3gpp.org/ftp/tsg_ct/WG3_interworking_ex-CN3/TSGC3_5
> 8_Kyoto_Japan/Docs/C3-100469.zip
> This is just fyi.
>
>
>
> > -----Original Message-----
> > From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On
> > Behalf Of Qin Wu
> > Sent: Freitag, 2. Dezember 2011 02:55
> > To: Schwarz, Albrecht (Albrecht); avt@ietf.org
> > Cc: megaco@ietf.org
> > Subject: Re: [AVTCORE] Types of monitoring architectures; RE:
> > I-D Action: draft-ietf-avtcore-monarch-08.txt
> >
> > Hi, Albrecht:
> > No offence, I am not really convinced with your proposal on
> > physical monitoring architecture.
> >  my counterquestion is what does physical monitoring
> > architecture looks like in your mind?
> > How many components do we have in such physical monitroing
> > architecture? what are they?
> > Take IMS network architecture as a example, they may have
> > P-CSCF,S-CSCF, SIP PBX, SBC, why do you believe monitor
> > described in draft-ietf-avtcore-monarch is mapped into
> > P-CSCF, S-CSCF, SBC, Media Gateway, Media Gateway Controller
> > should be in the scope of IETF RTP monitoring archtiecture draft?
> >
> > Monitor described in  draft-ietf-avtcore-monarch is well
> > defined in the section 3 of RFC3550 as follows:
> > "
> >
> >    Monitor: An application that receives RTCP packets sent by
> >       participants in an RTP session, in particular the reception
> >       reports, and estimates the current quality of service for
> >       distribution monitoring, fault diagnosis and long-term
> > statistics.
> >       The monitor function is likely to be built into the
> > application(s)
> >       participating in the session, but may also be a separate
> >       application that does not otherwise participate and
> > does not send
> >       or receive the RTP data packets (since they are on a separate
> >       port).  These are called third-party monitors.  It is also
> >       acceptable for a third-party monitor to receive the RTP data
> >       packets but not send RTCP packets or otherwise be
> counted in the
> >       session.
> >
> > "
> > Isn't how to implent monitor into IMS netowork archtiecture a
> > implentation specific issue?
> > If this issue are really interesting, isn't it a good idea to
> > produce another new document to talk about this?
> > One good example for this motivation is this draft I like to
> > share with you:
> > http://tools.ietf.org/html/draft-kaplan-dispatch-b2bua-taxonom
> > y-00#section-4.6
> >
> > Regards!
> > -Qin
> > ----- Original Message -----
> > From: "Schwarz, Albrecht (Albrecht)"
> > <albrecht.schwarz@alcatel-lucent.com>
> > To: "Qin Wu" <bill.wu@huawei.com>; <avt@ietf.org>
> > Cc: <megaco@ietf.org>
> > Sent: Friday, December 02, 2011 12:20 AM
> > Subject: RE: [AVTCORE] Types of monitoring architectures; RE:
> > I-D Action: draft-ietf-avtcore-monarch-08.txt
> >
> >
> > My replies below ...
> > -Albrecht
> >
> > > -----Original Message-----
> > > From: Qin Wu [mailto:bill.wu@huawei.com]
> > > Sent: Donnerstag, 1. Dezember 2011 02:42
> > > To: Schwarz, Albrecht (Albrecht); avt@ietf.org
> > > Cc: megaco@ietf.org
> > > Subject: Re: [AVTCORE] Types of monitoring architectures; RE:
> > > I-D Action: draft-ietf-avtcore-monarch-08.txt
> > >
> > > Hi,
> > > ----- Original Message -----
> > > From: "Schwarz, Albrecht (Albrecht)"
> > > <albrecht.schwarz@alcatel-lucent.com>
> > > To: "Qin Wu" <bill.wu@huawei.com>; <avt@ietf.org>
> > > Cc: <megaco@ietf.org>
> > > Sent: Thursday, December 01, 2011 1:24 AM
> > > Subject: RE: [AVTCORE] Types of monitoring architectures; RE:
> > > I-D Action: draft-ietf-avtcore-monarch-08.txt
> > >
> > >
> > > My replies below inline,
> > > Albrecht
> > >
> > > > -----Original Message-----
> > > > From: Qin Wu [mailto:bill.wu@huawei.com]
> > > > Sent: Mittwoch, 30. November 2011 04:51
> > > > To: Schwarz, Albrecht (Albrecht); avt@ietf.org
> > > > Cc: megaco@ietf.org
> > > > Subject: Re: [AVTCORE] Types of monitoring architectures; RE:
> > > > I-D Action: draft-ietf-avtcore-monarch-08.txt
> > > >
> > > > Hi,
> > > > ----- Original Message -----
> > > > From: "Schwarz, Albrecht (Albrecht)"
> > > > <albrecht.schwarz@alcatel-lucent.com>
> > > > To: <avt@ietf.org>
> > > > Cc: <megaco@ietf.org>
> > > > Sent: Tuesday, November 29, 2011 7:32 PM
> > > > Subject: [AVTCORE] Types of monitoring architectures; RE: I-D
> > > > Action: draft-ietf-avtcore-monarch-08.txt
> > > >
> > > >
> > > > > Dear All,
> > > > >
> > > > > there are different types of monitoring architectures,
> > > > particularily from perspective of QoE related performance
> > > parameters.
> > > > > Let's recall QoE (e.g., ITU-T P.10 Amendment 2):
> > > > >
> > > > > Quality of Experience (QoE):
> > > > > The overall acceptability of an application or service, as
> > > > perceived subjectively by the end-user.
> > > > > NOTE 1 - Quality of experience includes the complete
> > > > end-to-end system effects (client, terminal, network,
> > > > services infrastructure, etc.).
> > > > > NOTE 2 - Overall acceptability may be influenced by user
> > > > expectations and context.
> > > > >
> > > > > Important for MONARCH:
> > > > > 1st ... perceived by end-user
> > > > > 2nd QoE includes the complete end-to-end sytem effects ...
> > > > >
> > > > > That said, present RTP monitoring architecture in MONARCH
> > > > according clause 3 is not specific on the type of monitoring
> > > > architecture. For instance, Fig. 1, it is possibly supposed
> > > > that the "RTP Sender" and "RTP Receiver" entities are equal
> > > > to a terminal/user equipment (UE). This would be an
> > > > end-to-end IP network scenario.
> > > > >
> > > > > However, the "RTP Sender" and "RTP Receiver" entities may
> > > > be also located at the edge of an IP network, e.g. in a
> > > > gateway for IP-to-non-IP interworking, i.e. an UE located in
> > > > the non-IP network part.
> > > > > Note: such scenarios are considered by MEGACO gateways
> > > > (I've Cc'd megaco list).
> > > > >
> > > > > An RTP Sender/Receiver located NOT in the UE would question
> > > > the value of RTP/RTCP QoE related performance measurements
> > > > (because the UE is located outside the RTP domain).
> > > > >
> > > > > Conclusions:
> > > > > - the set of meaningful performance metrics may be
> > > > dependent on the location of the RTP Sender/Receiver, e.g.
> > > > whether in a UE, gateway, ...
> > > > > - don't see any impact on transport level metrics
> > > > > - ... but the set of meaningful application level metrics
> > > > >
> > > > > Proposal for MONARCH:
> > > > > #1: insert sub-clause title "3.1 End-to-end IP network
> > > > architecture" below clause 3
> > > > >
> > > > > #2: add a sub-clause 3.2 at the end of clause 3, sth like
> > > > >
> > > > > "3.2 RTP Sender/Receiver entities located in network nodes
> > > > > The location of the RTP Sender/Receiver entity may impact
> > > > the set of meaningful metrics.
> > > > > For instance: application level metrics for QoE related
> > > > performance metrics are questionable (or doesn't really make
> > > > sense at all) when measured in a network node (terminating
> > > > the RTP) instead of the user equipment."
> > > > >
> > > > > Something like this would help to avoid confusion.
> > > > > I even believe that a QoE measurement in a network node
> > > > would violate the QoE definition. Would be rather something
> > > > like QoE* ("remote QoE"):-(
> > > > >
> > > > > Such information would improve the MONARCH doc in my opinion.
> > > > > Sorry for that late comment.
> > > > > Any views?
> > > >
> > > > [Qin]:
> > > > Albrrecht, if you follow ealry list discussion on
> > > > draft-hunt-avt-monarch-01, you will see the rough consensus
> > > > to position this document was
> > > > this daft should focus on guidelines for defining reporting
> > > > blocks. That is to say the main purpose of MONARCH draft
> > is how to
> > > > provide guidelines for the development of new RTCP XR block
> > > > types in XRBlock working group.
> > >
> > > [ABS] ... then the title "monitoring architectures" is misleading.
> > > Proposal: keep title, revise scope section on focus
> > >
> > > [Qin]: No, the title is *RTP* monitoring architecture, we can
> > > not expand scope into IP monitoring architecture.
> >
> > [ABS] That's wasn't the intent! Did just focus on the key word.
> >
> > >
> > > >
> > > > Therefore how and where to collect the metric from RTP
> > > > endpoint is not scope of this document, in my opinion. since
> > > > you may have many ways to do this and different vendors have
> > > > their different appoaches. It will be better to leave this
> > > > beyond the scope. But you are right, it will be more
> > > > reasonable to measure QoE related performance metric at the
> > > > RTP receiver.
> > >
> > > [ABS] I would disagree. At least your statement should be
> > > conditional, sth like
> > > "QoE related performance metrics may be measured in a RTP
> > > receiver, IF the RTP receiver function is located in user
> > > equipment (e.g. IP terminal), because QoE performance metrics
> > > are tightly coupled to the point of view of a 'user'.
> > > ... IF NOT, then ..."
> > >
> > > [Qin]: I am not sure user equipment or IP terminal is the
> > > right term from RTP perspective.
> > >
> > > Also if you read P.NAMS, P.NAMS model for calculating QoE
> > > related metric can be placed either at the network or at
> the client.
> > > So I disagree with what you said.
> >
> > [ABS] Not convinced at all.
> > Guess you are referring to the "mid-point" models, right?
> > The usage of such that models depends on "prior knowledge
> > ..." information.
> > Thus, the applicability is conditional. You may not make such
> > a general statement.
> >
> >
> > >
> > > Also as I said, how and where to collect the metric from RTP
> > >  endpoint is not scope of this document. It depends on the
> > > model you are choosing, e.g., four operation modes specified
> > > in P.NAMS.
> > > Apparently this should not be specified again in RTP
> > > monitoring architecture document.
> > >
> > > >
> > > > Another point is it is not clear to me how RTP monitoring has
> > > > to do with architectureend to end IP network architecture .
> > > > this draft mostly focus on discussing RTP level stuff.
> > > > Therefore I am quite doubt that we should describe anything
> > > > in this document like how
> > > > RTP entties is mapped into network entities/nodes at
> the IP layer.
> > >
> > > [ABS] I don't got any problems to talk about architectural
> > > framework for monitoring in this document. Such information
> > > is required and this is the only IETF AVT doc about it.
> > > The solution to this issue is rather simple to me:
> > > - split the MONARCH "monitoring architecture" in
> > > 1) a functional monitoring architecture (let's call it 'FMA') and
> > > 2) a physical monitoring architecture (... 'PMA').
> > >
> > > - the present MONARCH doc would describe the FMA at the level
> > > of RTP entities (i.e., Fig. 1 entities, incl. all the RTP
> > > topology components according RFC 5117)
> > >
> > > - there are many options of functional-to-physical mappings,
> > > i.e. how a FMA would be mapped on a PMA
> > > - the mapping is typically dependent on considered network
> > > architecture (like SIP, H.323, MGCP, IMS, wireless, etc networks)
> > >
> > > - the present MONARCH doc would describe the FMA-to-PMA
> > > mapping IF all RTP receiver/sender entities would be located
> > > in physical IP terminals (UEs)
> > > - etc
> > >
> > > [Qin]: I can understand your point, but you can not do that.
> > > Since this document is only focus on *RTP* monitoring
> > > architecture, that is what it said in AVTCore milestone:
> > > "
> > >
> > > Goals and Milestones:
> > >
> > >   Feb 2011 - Submit Monitoring Architecture for RTP for
> > Informational
> > >
> > > "
> >
> > [ABS] If you go back to my first email on this subject, and
> > if you look at my proposal: that's not a lot, nothing which
> > violates the charter, goals and milestones.
> >
> >
> > > Also if you really don't see how to map FMA to PMA, you may
> > > look at the P.NAMS models specifed in ITU-T P.NAMS.
> > > As for how to use RTP monitoring architecture or RTP XR
> > > Report in the IMS network architecture, you may look at:
> > > http://tools.ietf.org/html/rfc6035
> >
> > [ABS] That's the SIP reporting interface, i.e., applicable
> > primarily for physical IP user equipment with embedded RTP
> > sender/receiver function and SIP UA function.
> > However, the applicability of RFC 6035 is limited for a
> > SIP-to-PSTN gateway (because the RTP sender/receiver would be
> > located NOT in user equipment. Also the P.NAMS mid-point
> > model fails for such a scenario.
> >
> > > ITU-T H.248.48.
> > > But I haven't check the current status of H.248.48.
> >
> > [ABS] Work is finalized, see
> > http://www.itu.int/md/meetingdoc.asp?lang=en&parent=T09-SG16-1
> > 11121-TD-PLEN-0419
> >
> > >
> > > >
> > > > But as the author of this document, I am interested and open
> > > > to other opinions.:-)
> > >
> > > [ABS] Like to add a further aspect: a "functional monitoring
> > > architecture" may be considered as a network overlay,
> > > something which adds additional capabilities (here:
> > > measurement services, reporting services on top of basic RTP
> > > services).
> > > Such an overlay concept is nothing new: e.g., the
> > > MultiService Forum did define a "Performance Measurement &
> > > Monitoring (PMM)" overlay network, or IETF RMON may be also
> > > considered as such.
> > >
> > > >
> > > > > Regards,
> > > > > Albrecht
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >> -----Original Message-----
> > > > >> From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On
> > > > >> Behalf Of internet-drafts@ietf.org
> > > > >> Sent: Dienstag, 29. November 2011 08:56
> > > > >> To: i-d-announce@ietf.org
> > > > >> Cc: avt@ietf.org
> > > > >> Subject: [AVTCORE] I-D Action:
> > draft-ietf-avtcore-monarch-08.txt
> > > > >>
> > > > >>
> > > > >> A New Internet-Draft is available from the on-line
> > > > >> Internet-Drafts directories. This draft is a work item of the
> > > > >> Audio/Video Transport Core Maintenance Working Group
> > of the IETF.
> > > > >>
> > > > >> Title           : Monitoring Architectures for RTP
> > > > >> Author(s)       : Qin Wu
> > > > >>                           Geoff Hunt
> > > > >>                           Philip Arden
> > > > >> Filename        : draft-ietf-avtcore-monarch-08.txt
> > > > >> Pages           : 25
> > > > >> Date            : 2011-11-28
> > > > >>
> > > > >>    This memo proposes an architecture for extending RTCP with
> > > > >> a new RTCP
> > > > >>    XR (RFC3611) block type to report new metrics
> > regarding media
> > > > >>    transmission or reception quality, following RTCP
> guideline
> > > > >>    established in RFC5968.  This memo suggests that a new
> > > > block should
> > > > >>    contain a single metric or a small number of metrics
> > > > relevant to a
> > > > >>    single parameter of interest or concern, rather than
> > > > containing a
> > > > >>    number of metrics which attempt to provide full coverage
> > > > >> of all those
> > > > >>    parameters of concern to a specific application.
> > > > Applications may
> > > > >>    then "mix and match" to create a set of blocks which
> > > > >> covers their set
> > > > >>    of concerns.  Where possible, a specific block should be
> > > > >> designed to
> > > > >>    be re-usable across more than one application, for
> > > > example, for all
> > > > >>    of voice, streaming audio and video.
> > > > >>
> > > > >>
> > > > >> A URL for this Internet-Draft is:
> > > > >>
> > > >
> > >
> >
> http://www.ietf.org/internet-drafts/draft-ietf-avtcore-monarch-08.txt
> > > > >>
> > > > >> Internet-Drafts are also available by anonymous FTP at:
> > > > >> ftp://ftp.ietf.org/internet-drafts/
> > > > >>
> > > > >> This Internet-Draft can be retrieved at:
> > > > >>
> > > >
> > ftp://ftp.ietf.org/internet-drafts/draft-ietf-avtcore-monarch-08.txt
> > > > >>
> > > > >> _______________________________________________
> > > > >> Audio/Video Transport Core Maintenance
> > > > >> avt@ietf.org
> > > > >> https://www.ietf.org/mailman/listinfo/avt
> > > > >>
> > > > > _______________________________________________
> > > > > Audio/Video Transport Core Maintenance
> > > > > avt@ietf.org
> > > > > https://www.ietf.org/mailman/listinfo/avt
> > > >
> > > =
> > _______________________________________________
> > Audio/Video Transport Core Maintenance
> > avt@ietf.org
> > https://www.ietf.org/mailman/listinfo/avt
> >
>

From albrecht.schwarz@alcatel-lucent.com  Fri Dec  9 08:01:56 2011
Return-Path: <albrecht.schwarz@alcatel-lucent.com>
X-Original-To: megaco@ietfa.amsl.com
Delivered-To: megaco@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 23E0C21F85FF; Fri,  9 Dec 2011 08:01:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.666
X-Spam-Level: 
X-Spam-Status: No, score=-5.666 tagged_above=-999 required=5 tests=[AWL=-0.017, BAYES_00=-2.599, HELO_EQ_FR=0.35, J_CHICKENPOX_14=0.6, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nyn4gaUzR8V5; Fri,  9 Dec 2011 08:01:43 -0800 (PST)
Received: from smail6.alcatel.fr (smail6.alcatel.fr [64.208.49.42]) by ietfa.amsl.com (Postfix) with ESMTP id 526BD21F853E; Fri,  9 Dec 2011 08:01:43 -0800 (PST)
Received: from FRMRSSXCHHUB04.dc-m.alcatel-lucent.com (FRMRSSXCHHUB04.dc-m.alcatel-lucent.com [135.120.45.64]) by smail6.alcatel.fr (8.14.3/8.14.3/ICT) with ESMTP id pB9G14Mi011957 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Fri, 9 Dec 2011 17:01:04 +0100
Received: from FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com ([135.120.45.50]) by FRMRSSXCHHUB04.dc-m.alcatel-lucent.com ([135.120.45.64]) with mapi; Fri, 9 Dec 2011 17:01:01 +0100
From: "Schwarz, Albrecht (Albrecht)" <albrecht.schwarz@alcatel-lucent.com>
To: Qin Wu <bill.wu@huawei.com>, "avt@ietf.org" <avt@ietf.org>
Date: Fri, 9 Dec 2011 17:01:00 +0100
Thread-Topic: [AVTCORE] Types of monitoring architectures; RE:  I-D Action: draft-ietf-avtcore-monarch-08.txt
Thread-Index: Acy1UPbzvzXcgax2QjiudJv83KCy2gBOijCg
Message-ID: <5F7BCCF5541B7444830A2288ABBEBC9621620F5258@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com>
References: <20111129075613.12419.4377.idtracker@ietfa.amsl.com> <5F7BCCF5541B7444830A2288ABBEBC96216190051A@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com> <EAC481B4D8034C38AC54E1217F8D875D@china.huawei.com> <5F7BCCF5541B7444830A2288ABBEBC96216190077F@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com> <B527BAFA038842A8939A8C2D558074CD@china.huawei.com> <5F7BCCF5541B7444830A2288ABBEBC962161900908@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com> <9FF9B04A84E64AD7ABCCC4F2ACC1E19A@china.huawei.com> <5F7BCCF5541B7444830A2288ABBEBC9621620F4AF5@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com> <D44A4820E0D24DD79F6F5A4B7507D0D6@china.huawei.com> <5F7BCCF5541B7444830A2288ABBEBC9621620F4ED2@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com> <71112008FBA94D35B07FA6B4916075B6@china.huawei.com>
In-Reply-To: <71112008FBA94D35B07FA6B4916075B6@china.huawei.com>
Accept-Language: de-DE, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: de-DE, en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.69 on 155.132.188.84
Cc: "megaco@ietf.org" <megaco@ietf.org>
Subject: Re: [Megaco] [AVTCORE] Types of monitoring architectures; RE:  I-D Action: draft-ietf-avtcore-monarch-08.txt
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.1.12
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: Fri, 09 Dec 2011 16:01:56 -0000

How do you explain to a network operator the value of QoE measurements by a=
n RTP receiver / RTP monitor component located in an RTP-to-PSTN gateway?

This would be a monitoring scenario inline with MONARCH, but with valueless=
 QoE results, right?


> -----Original Message-----
> From: Qin Wu [mailto:bill.wu@huawei.com]
> Sent: Donnerstag, 8. Dezember 2011 03:26
> To: Schwarz, Albrecht (Albrecht); avt@ietf.org
> Cc: megaco@ietf.org
> Subject: Re: [AVTCORE] Types of monitoring architectures; RE:
> I-D Action: draft-ietf-avtcore-monarch-08.txt
>
> You reiterate what you propose for physical entities in the
> early email.
> I am still not convicing with that.
>
> Since we have RTP components like RTP end system, RTP mixer,
> RTP media translator, RTP transport translator, RTP monitor
> specified in RFC3550 can be built into these component as a
> application. also monitor can be disjointed from these RTP
> components as a third party monitor. why we need to specify
> how to map RTP end system into user equipment, RTP translator
> or RTP mixer can be mapped into RTP-PSTN gateway, or IP to IP
> border gateway since we have already mapped monitor into
> different RTP components.
> How many PE types you can enumerate? why they should be scope
> of RTP monitoring architecture?
>
> Also as specified in MONARCH draft, we have end sytem
> metrics, transport level metric, transport level metric, they
> can be measured and collected from the different RTP
> comoponents specified in RFC3550, RFC5117. Apparently end
> system metric can only be collected from RTP end system.
> transport metric is collected from any RTP system in the RTP
> monitoring architecture, regarding application level metric,
> apparently they should be measured at the application layer
> and can not be collected from RTP transport translator, Also
> RTP transport translator is still a functional entity rather
> than a physical entity. I am not convincing with what you
> said about "contradiction", "lead to possible wrong expectations".
>
> Regards!
> -Qin
> ----- Original Message -----
> From: "Schwarz, Albrecht (Albrecht)"
> <albrecht.schwarz@alcatel-lucent.com>
> To: "Qin Wu" <bill.wu@huawei.com>; <avt@ietf.org>
> Cc: <megaco@ietf.org>
> Sent: Thursday, December 08, 2011 12:24 AM
> Subject: RE: [AVTCORE] Types of monitoring architectures; RE:
> I-D Action: draft-ietf-avtcore-monarch-08.txt
>
>
> Qin,
> that's NOT the point.
>
> All RFC 3550 and RFC 5117 RTP components are FUNCTIONAL ENTITIES (FE).
> e.g.,
> - the RTP Monitor or RTP receiver FE may be located in
> different PHYSICAL ENTITIES (PE), e.g.
>         a1) a user equipment
>         a2) a RTP-to-PSTN gateway
>         a3) an IP-to-IP session border gateway (in a
> back-to-back RTP endsystem topology)
>         a3) ...
>
> - the RTP Monitor may be associated to an RTP transport translator ...
>         b1) an IP-to-IP session border gateway
>
> The "RTP monitoring architecture" is IMPACTED by each
> functional-to-physical mapping because e.g.
> * QoE related metrics are questionable in case of a2
> ("despite the fact of a RTP receiver function")
> * application level metrics at the location of a RTP
> transport translator are a contradiction in itself
> * ...
>
> Again, it's not really changing the MONARCH draft because in
> the very majority of scenarios it is correct. However, there
> are few cases where the MONARCH description would be "too
> high level", "not fully correct", "lead to possible wrong
> expectations", ...
>
> Regards,
> Albrecht
>
>
>
> > -----Original Message-----
> > From: Qin Wu [mailto:bill.wu@huawei.com]
> > Sent: Dienstag, 6. Dezember 2011 07:13
> > To: Schwarz, Albrecht (Albrecht); avt@ietf.org
> > Cc: megaco@ietf.org
> > Subject: Re: [AVTCORE] Types of monitoring architectures; RE:
> > I-D Action: draft-ietf-avtcore-monarch-08.txt
> >
> > If you talk about existing RFC5117 RTP topology components,
> > this has already been covered by the current version of
> > draft-ietf-avtcore-monarch.
> > In most cases, an RTP system using RTCP XR is architecturally
> > no different from an RTP system which does not use RTCP XR.
> >
> > Regards!
> > -Qin
> > ----- Original Message -----
> > From: "Schwarz, Albrecht (Albrecht)"
> > <albrecht.schwarz@alcatel-lucent.com>
> > To: "Qin Wu" <bill.wu@huawei.com>; <avt@ietf.org>
> > Cc: <megaco@ietf.org>
> > Sent: Monday, December 05, 2011 10:48 PM
> > Subject: RE: [AVTCORE] Types of monitoring architectures; RE:
> > I-D Action: draft-ietf-avtcore-monarch-08.txt
> >
> >
> > Hello Qin,
> >
> > to 1) Physical monitoring architecture
> > Of course consideration of generic physical entities (PE),
> > not specific to any network reference architectures defined
> > by SDOs (like your refered entities).
> > There would be just a few PE types ("given by the limited set
> > of RTP topology components (RFC 5117)").
> >
> > to 2) (RFC 3550) Monitor function
> > Right, that's a functional entity. The applicability of a
> > monitor may be limited, dependent on ... (like in P.NAMS).
> >
> > to 3) your IMS network example
> > Don't see the need to refer from MONARCH to a specific
> > network architecture like IMS.
> > Please also note that IMS is a functional architecture, not a
> > physical architecture.
> >
> > Regards,
> > Albrecht
> >
> > PS
> > There are multiple options for adding the "RTP monitoring
> > architecture" to a functional/physical network architecture:
> > a) integrated approach: extension of existing functional
> > entities or/and addition of RTP monitoring architectural
> > components, extension or/and addition of
> > signalling/management interfaces for control and
> > configuration of RTP monitoring services, and reporting
> > interfaces for measurement data ...
> > b) overlay approach: separate specification to ...
> >
> >
> > PSS
> > BTW: there's a discussion paper with regards to the location
> > of a monitor function in an IMS H.248 gateway entity:
> > Measurements and statistics in IMS - Use Cases
> > http://www.3gpp.org/ftp/tsg_ct/WG3_interworking_ex-CN3/TSGC3_5
> > 8_Kyoto_Japan/Docs/C3-100469.zip
> > This is just fyi.
> >
> >
> >
> > > -----Original Message-----
> > > From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On
> > > Behalf Of Qin Wu
> > > Sent: Freitag, 2. Dezember 2011 02:55
> > > To: Schwarz, Albrecht (Albrecht); avt@ietf.org
> > > Cc: megaco@ietf.org
> > > Subject: Re: [AVTCORE] Types of monitoring architectures; RE:
> > > I-D Action: draft-ietf-avtcore-monarch-08.txt
> > >
> > > Hi, Albrecht:
> > > No offence, I am not really convinced with your proposal on
> > > physical monitoring architecture.
> > >  my counterquestion is what does physical monitoring
> > > architecture looks like in your mind?
> > > How many components do we have in such physical monitroing
> > > architecture? what are they?
> > > Take IMS network architecture as a example, they may have
> > > P-CSCF,S-CSCF, SIP PBX, SBC, why do you believe monitor
> > > described in draft-ietf-avtcore-monarch is mapped into
> > > P-CSCF, S-CSCF, SBC, Media Gateway, Media Gateway Controller
> > > should be in the scope of IETF RTP monitoring archtiecture draft?
> > >
> > > Monitor described in  draft-ietf-avtcore-monarch is well
> > > defined in the section 3 of RFC3550 as follows:
> > > "
> > >
> > >    Monitor: An application that receives RTCP packets sent by
> > >       participants in an RTP session, in particular the reception
> > >       reports, and estimates the current quality of service for
> > >       distribution monitoring, fault diagnosis and long-term
> > > statistics.
> > >       The monitor function is likely to be built into the
> > > application(s)
> > >       participating in the session, but may also be a separate
> > >       application that does not otherwise participate and
> > > does not send
> > >       or receive the RTP data packets (since they are on
> a separate
> > >       port).  These are called third-party monitors.  It is also
> > >       acceptable for a third-party monitor to receive the RTP data
> > >       packets but not send RTCP packets or otherwise be
> > counted in the
> > >       session.
> > >
> > > "
> > > Isn't how to implent monitor into IMS netowork archtiecture a
> > > implentation specific issue?
> > > If this issue are really interesting, isn't it a good idea to
> > > produce another new document to talk about this?
> > > One good example for this motivation is this draft I like to
> > > share with you:
> > > http://tools.ietf.org/html/draft-kaplan-dispatch-b2bua-taxonom
> > > y-00#section-4.6
> > >
> > > Regards!
> > > -Qin
> > > ----- Original Message -----
> > > From: "Schwarz, Albrecht (Albrecht)"
> > > <albrecht.schwarz@alcatel-lucent.com>
> > > To: "Qin Wu" <bill.wu@huawei.com>; <avt@ietf.org>
> > > Cc: <megaco@ietf.org>
> > > Sent: Friday, December 02, 2011 12:20 AM
> > > Subject: RE: [AVTCORE] Types of monitoring architectures; RE:
> > > I-D Action: draft-ietf-avtcore-monarch-08.txt
> > >
> > >
> > > My replies below ...
> > > -Albrecht
> > >
> > > > -----Original Message-----
> > > > From: Qin Wu [mailto:bill.wu@huawei.com]
> > > > Sent: Donnerstag, 1. Dezember 2011 02:42
> > > > To: Schwarz, Albrecht (Albrecht); avt@ietf.org
> > > > Cc: megaco@ietf.org
> > > > Subject: Re: [AVTCORE] Types of monitoring architectures; RE:
> > > > I-D Action: draft-ietf-avtcore-monarch-08.txt
> > > >
> > > > Hi,
> > > > ----- Original Message -----
> > > > From: "Schwarz, Albrecht (Albrecht)"
> > > > <albrecht.schwarz@alcatel-lucent.com>
> > > > To: "Qin Wu" <bill.wu@huawei.com>; <avt@ietf.org>
> > > > Cc: <megaco@ietf.org>
> > > > Sent: Thursday, December 01, 2011 1:24 AM
> > > > Subject: RE: [AVTCORE] Types of monitoring architectures; RE:
> > > > I-D Action: draft-ietf-avtcore-monarch-08.txt
> > > >
> > > >
> > > > My replies below inline,
> > > > Albrecht
> > > >
> > > > > -----Original Message-----
> > > > > From: Qin Wu [mailto:bill.wu@huawei.com]
> > > > > Sent: Mittwoch, 30. November 2011 04:51
> > > > > To: Schwarz, Albrecht (Albrecht); avt@ietf.org
> > > > > Cc: megaco@ietf.org
> > > > > Subject: Re: [AVTCORE] Types of monitoring architectures; RE:
> > > > > I-D Action: draft-ietf-avtcore-monarch-08.txt
> > > > >
> > > > > Hi,
> > > > > ----- Original Message -----
> > > > > From: "Schwarz, Albrecht (Albrecht)"
> > > > > <albrecht.schwarz@alcatel-lucent.com>
> > > > > To: <avt@ietf.org>
> > > > > Cc: <megaco@ietf.org>
> > > > > Sent: Tuesday, November 29, 2011 7:32 PM
> > > > > Subject: [AVTCORE] Types of monitoring architectures; RE: I-D
> > > > > Action: draft-ietf-avtcore-monarch-08.txt
> > > > >
> > > > >
> > > > > > Dear All,
> > > > > >
> > > > > > there are different types of monitoring architectures,
> > > > > particularily from perspective of QoE related performance
> > > > parameters.
> > > > > > Let's recall QoE (e.g., ITU-T P.10 Amendment 2):
> > > > > >
> > > > > > Quality of Experience (QoE):
> > > > > > The overall acceptability of an application or service, as
> > > > > perceived subjectively by the end-user.
> > > > > > NOTE 1 - Quality of experience includes the complete
> > > > > end-to-end system effects (client, terminal, network,
> > > > > services infrastructure, etc.).
> > > > > > NOTE 2 - Overall acceptability may be influenced by user
> > > > > expectations and context.
> > > > > >
> > > > > > Important for MONARCH:
> > > > > > 1st ... perceived by end-user
> > > > > > 2nd QoE includes the complete end-to-end sytem effects ...
> > > > > >
> > > > > > That said, present RTP monitoring architecture in MONARCH
> > > > > according clause 3 is not specific on the type of monitoring
> > > > > architecture. For instance, Fig. 1, it is possibly supposed
> > > > > that the "RTP Sender" and "RTP Receiver" entities are equal
> > > > > to a terminal/user equipment (UE). This would be an
> > > > > end-to-end IP network scenario.
> > > > > >
> > > > > > However, the "RTP Sender" and "RTP Receiver" entities may
> > > > > be also located at the edge of an IP network, e.g. in a
> > > > > gateway for IP-to-non-IP interworking, i.e. an UE located in
> > > > > the non-IP network part.
> > > > > > Note: such scenarios are considered by MEGACO gateways
> > > > > (I've Cc'd megaco list).
> > > > > >
> > > > > > An RTP Sender/Receiver located NOT in the UE would question
> > > > > the value of RTP/RTCP QoE related performance measurements
> > > > > (because the UE is located outside the RTP domain).
> > > > > >
> > > > > > Conclusions:
> > > > > > - the set of meaningful performance metrics may be
> > > > > dependent on the location of the RTP Sender/Receiver, e.g.
> > > > > whether in a UE, gateway, ...
> > > > > > - don't see any impact on transport level metrics
> > > > > > - ... but the set of meaningful application level metrics
> > > > > >
> > > > > > Proposal for MONARCH:
> > > > > > #1: insert sub-clause title "3.1 End-to-end IP network
> > > > > architecture" below clause 3
> > > > > >
> > > > > > #2: add a sub-clause 3.2 at the end of clause 3, sth like
> > > > > >
> > > > > > "3.2 RTP Sender/Receiver entities located in network nodes
> > > > > > The location of the RTP Sender/Receiver entity may impact
> > > > > the set of meaningful metrics.
> > > > > > For instance: application level metrics for QoE related
> > > > > performance metrics are questionable (or doesn't really make
> > > > > sense at all) when measured in a network node (terminating
> > > > > the RTP) instead of the user equipment."
> > > > > >
> > > > > > Something like this would help to avoid confusion.
> > > > > > I even believe that a QoE measurement in a network node
> > > > > would violate the QoE definition. Would be rather something
> > > > > like QoE* ("remote QoE"):-(
> > > > > >
> > > > > > Such information would improve the MONARCH doc in
> my opinion.
> > > > > > Sorry for that late comment.
> > > > > > Any views?
> > > > >
> > > > > [Qin]:
> > > > > Albrrecht, if you follow ealry list discussion on
> > > > > draft-hunt-avt-monarch-01, you will see the rough consensus
> > > > > to position this document was
> > > > > this daft should focus on guidelines for defining reporting
> > > > > blocks. That is to say the main purpose of MONARCH draft
> > > is how to
> > > > > provide guidelines for the development of new RTCP XR block
> > > > > types in XRBlock working group.
> > > >
> > > > [ABS] ... then the title "monitoring architectures" is
> misleading.
> > > > Proposal: keep title, revise scope section on focus
> > > >
> > > > [Qin]: No, the title is *RTP* monitoring architecture, we can
> > > > not expand scope into IP monitoring architecture.
> > >
> > > [ABS] That's wasn't the intent! Did just focus on the key word.
> > >
> > > >
> > > > >
> > > > > Therefore how and where to collect the metric from RTP
> > > > > endpoint is not scope of this document, in my opinion. since
> > > > > you may have many ways to do this and different vendors have
> > > > > their different appoaches. It will be better to leave this
> > > > > beyond the scope. But you are right, it will be more
> > > > > reasonable to measure QoE related performance metric at the
> > > > > RTP receiver.
> > > >
> > > > [ABS] I would disagree. At least your statement should be
> > > > conditional, sth like
> > > > "QoE related performance metrics may be measured in a RTP
> > > > receiver, IF the RTP receiver function is located in user
> > > > equipment (e.g. IP terminal), because QoE performance metrics
> > > > are tightly coupled to the point of view of a 'user'.
> > > > ... IF NOT, then ..."
> > > >
> > > > [Qin]: I am not sure user equipment or IP terminal is the
> > > > right term from RTP perspective.
> > > >
> > > > Also if you read P.NAMS, P.NAMS model for calculating QoE
> > > > related metric can be placed either at the network or at
> > the client.
> > > > So I disagree with what you said.
> > >
> > > [ABS] Not convinced at all.
> > > Guess you are referring to the "mid-point" models, right?
> > > The usage of such that models depends on "prior knowledge
> > > ..." information.
> > > Thus, the applicability is conditional. You may not make such
> > > a general statement.
> > >
> > >
> > > >
> > > > Also as I said, how and where to collect the metric from RTP
> > > >  endpoint is not scope of this document. It depends on the
> > > > model you are choosing, e.g., four operation modes specified
> > > > in P.NAMS.
> > > > Apparently this should not be specified again in RTP
> > > > monitoring architecture document.
> > > >
> > > > >
> > > > > Another point is it is not clear to me how RTP monitoring has
> > > > > to do with architectureend to end IP network architecture .
> > > > > this draft mostly focus on discussing RTP level stuff.
> > > > > Therefore I am quite doubt that we should describe anything
> > > > > in this document like how
> > > > > RTP entties is mapped into network entities/nodes at
> > the IP layer.
> > > >
> > > > [ABS] I don't got any problems to talk about architectural
> > > > framework for monitoring in this document. Such information
> > > > is required and this is the only IETF AVT doc about it.
> > > > The solution to this issue is rather simple to me:
> > > > - split the MONARCH "monitoring architecture" in
> > > > 1) a functional monitoring architecture (let's call it
> 'FMA') and
> > > > 2) a physical monitoring architecture (... 'PMA').
> > > >
> > > > - the present MONARCH doc would describe the FMA at the level
> > > > of RTP entities (i.e., Fig. 1 entities, incl. all the RTP
> > > > topology components according RFC 5117)
> > > >
> > > > - there are many options of functional-to-physical mappings,
> > > > i.e. how a FMA would be mapped on a PMA
> > > > - the mapping is typically dependent on considered network
> > > > architecture (like SIP, H.323, MGCP, IMS, wireless, etc
> networks)
> > > >
> > > > - the present MONARCH doc would describe the FMA-to-PMA
> > > > mapping IF all RTP receiver/sender entities would be located
> > > > in physical IP terminals (UEs)
> > > > - etc
> > > >
> > > > [Qin]: I can understand your point, but you can not do that.
> > > > Since this document is only focus on *RTP* monitoring
> > > > architecture, that is what it said in AVTCore milestone:
> > > > "
> > > >
> > > > Goals and Milestones:
> > > >
> > > >   Feb 2011 - Submit Monitoring Architecture for RTP for
> > > Informational
> > > >
> > > > "
> > >
> > > [ABS] If you go back to my first email on this subject, and
> > > if you look at my proposal: that's not a lot, nothing which
> > > violates the charter, goals and milestones.
> > >
> > >
> > > > Also if you really don't see how to map FMA to PMA, you may
> > > > look at the P.NAMS models specifed in ITU-T P.NAMS.
> > > > As for how to use RTP monitoring architecture or RTP XR
> > > > Report in the IMS network architecture, you may look at:
> > > > http://tools.ietf.org/html/rfc6035
> > >
> > > [ABS] That's the SIP reporting interface, i.e., applicable
> > > primarily for physical IP user equipment with embedded RTP
> > > sender/receiver function and SIP UA function.
> > > However, the applicability of RFC 6035 is limited for a
> > > SIP-to-PSTN gateway (because the RTP sender/receiver would be
> > > located NOT in user equipment. Also the P.NAMS mid-point
> > > model fails for such a scenario.
> > >
> > > > ITU-T H.248.48.
> > > > But I haven't check the current status of H.248.48.
> > >
> > > [ABS] Work is finalized, see
> > > http://www.itu.int/md/meetingdoc.asp?lang=3Den&parent=3DT09-SG16-1
> > > 11121-TD-PLEN-0419
> > >
> > > >
> > > > >
> > > > > But as the author of this document, I am interested and open
> > > > > to other opinions.:-)
> > > >
> > > > [ABS] Like to add a further aspect: a "functional monitoring
> > > > architecture" may be considered as a network overlay,
> > > > something which adds additional capabilities (here:
> > > > measurement services, reporting services on top of basic RTP
> > > > services).
> > > > Such an overlay concept is nothing new: e.g., the
> > > > MultiService Forum did define a "Performance Measurement &
> > > > Monitoring (PMM)" overlay network, or IETF RMON may be also
> > > > considered as such.
> > > >
> > > > >
> > > > > > Regards,
> > > > > > Albrecht
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > >> -----Original Message-----
> > > > > >> From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On
> > > > > >> Behalf Of internet-drafts@ietf.org
> > > > > >> Sent: Dienstag, 29. November 2011 08:56
> > > > > >> To: i-d-announce@ietf.org
> > > > > >> Cc: avt@ietf.org
> > > > > >> Subject: [AVTCORE] I-D Action:
> > > draft-ietf-avtcore-monarch-08.txt
> > > > > >>
> > > > > >>
> > > > > >> A New Internet-Draft is available from the on-line
> > > > > >> Internet-Drafts directories. This draft is a work
> item of the
> > > > > >> Audio/Video Transport Core Maintenance Working Group
> > > of the IETF.
> > > > > >>
> > > > > >> Title           : Monitoring Architectures for RTP
> > > > > >> Author(s)       : Qin Wu
> > > > > >>                           Geoff Hunt
> > > > > >>                           Philip Arden
> > > > > >> Filename        : draft-ietf-avtcore-monarch-08.txt
> > > > > >> Pages           : 25
> > > > > >> Date            : 2011-11-28
> > > > > >>
> > > > > >>    This memo proposes an architecture for
> extending RTCP with
> > > > > >> a new RTCP
> > > > > >>    XR (RFC3611) block type to report new metrics
> > > regarding media
> > > > > >>    transmission or reception quality, following RTCP
> > guideline
> > > > > >>    established in RFC5968.  This memo suggests that a new
> > > > > block should
> > > > > >>    contain a single metric or a small number of metrics
> > > > > relevant to a
> > > > > >>    single parameter of interest or concern, rather than
> > > > > containing a
> > > > > >>    number of metrics which attempt to provide full coverage
> > > > > >> of all those
> > > > > >>    parameters of concern to a specific application.
> > > > > Applications may
> > > > > >>    then "mix and match" to create a set of blocks which
> > > > > >> covers their set
> > > > > >>    of concerns.  Where possible, a specific block should be
> > > > > >> designed to
> > > > > >>    be re-usable across more than one application, for
> > > > > example, for all
> > > > > >>    of voice, streaming audio and video.
> > > > > >>
> > > > > >>
> > > > > >> A URL for this Internet-Draft is:
> > > > > >>
> > > > >
> > > >
> > >
> >
> http://www.ietf.org/internet-drafts/draft-ietf-avtcore-monarch-08.txt
> > > > > >>
> > > > > >> Internet-Drafts are also available by anonymous FTP at:
> > > > > >> ftp://ftp.ietf.org/internet-drafts/
> > > > > >>
> > > > > >> This Internet-Draft can be retrieved at:
> > > > > >>
> > > > >
> > >
> ftp://ftp.ietf.org/internet-drafts/draft-ietf-avtcore-monarch-08.txt
> > > > > >>
> > > > > >> _______________________________________________
> > > > > >> Audio/Video Transport Core Maintenance
> > > > > >> avt@ietf.org
> > > > > >> https://www.ietf.org/mailman/listinfo/avt
> > > > > >>
> > > > > > _______________________________________________
> > > > > > Audio/Video Transport Core Maintenance
> > > > > > avt@ietf.org
> > > > > > https://www.ietf.org/mailman/listinfo/avt
> > > > >
> > > > =3D
> > > _______________________________________________
> > > Audio/Video Transport Core Maintenance
> > > avt@ietf.org
> > > https://www.ietf.org/mailman/listinfo/avt
> > >
> >
>

From javi@trajano.us.es  Fri Dec  9 10:06:58 2011
Return-Path: <javi@trajano.us.es>
X-Original-To: megaco@ietfa.amsl.com
Delivered-To: megaco@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AAA0B21F8558 for <megaco@ietfa.amsl.com>; Fri,  9 Dec 2011 10:06:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.398
X-Spam-Level: 
X-Spam-Status: No, score=-5.398 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_12=0.6, J_CHICKENPOX_15=0.6, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Mz066sYQYmCK for <megaco@ietfa.amsl.com>; Fri,  9 Dec 2011 10:06:57 -0800 (PST)
Received: from mail.us.es (mail.us.es [193.147.175.20]) by ietfa.amsl.com (Postfix) with ESMTP id 293EC21F852E for <megaco@ietf.org>; Fri,  9 Dec 2011 10:06:56 -0800 (PST)
Received: (qmail 6959 invoked from network); 9 Dec 2011 19:06:53 +0100
Received: from unknown (HELO us.es) (192.168.2.13) by us.es with SMTP; 9 Dec 2011 19:06:53 +0100
Received: (qmail 13815 invoked by uid 507); 9 Dec 2011 18:06:39 -0000
Received: from 127.0.0.1 by antivirus3 (envelope-from <javi@trajano.us.es>, uid 501) with qmail-scanner-2.08 (clamdscan: 0.97.3/14103.   Clear:RC:1(127.0.0.1):.  Processed in 0.037733 secs); 09 Dec 2011 18:06:39 -0000
Received: from unknown (HELO antivirus3) (127.0.0.1) by us.es with SMTP; 9 Dec 2011 18:06:39 -0000
Received: from 192.168.1.13 (192.168.1.13) by antivirus3 (F-Secure/fsigk_smtp/406/antivirus3); Fri, 09 Dec 2011 19:06:39 +0100 (CET)
X-Virus-Status: clean(F-Secure/fsigk_smtp/406/antivirus3)
Received: (qmail 21670 invoked from network); 9 Dec 2011 19:06:39 +0100
Received: from trajano.us.es (193.147.162.130) by us.es with AES256-SHA encrypted SMTP; 9 Dec 2011 19:06:39 +0100
Received: from [127.0.0.1] (112.pool85-56-79.dynamic.orange.es [85.56.79.112]) (authenticated bits=0) by trajano.us.es (8.13.8/8.13.8/Debian-3) with ESMTP id pB9I6cXo018360 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NOT); Fri, 9 Dec 2011 19:06:39 +0100
Message-ID: <4EE24E2C.9070504@trajano.us.es>
Date: Fri, 09 Dec 2011 19:06:36 +0100
From: Javi <javi@trajano.us.es>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; es-ES; rv:1.9.2.24) Gecko/20111103 Thunderbird/3.1.16
MIME-Version: 1.0
To: "megaco@ietf.org" <megaco@ietf.org>
Content-Type: multipart/alternative; boundary="------------050906070603060301050707"
Subject: [Megaco] Several SDP session in a Local or Remote Descriptor
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.1.12
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: Fri, 09 Dec 2011 18:06:58 -0000

This is a multi-part message in MIME format.
--------------050906070603060301050707
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

In a call, which is the difference between these two options (UDP port 
and IP address are the same in both?

Case A):

LocalControl {
    ReservedValue = true
},
Local {
    v=0
    c=IN IP4 adrressX
    m=audio portA RTP/AVP*2 8*
}


Case B):

LocalControl {
    ReservedGroup = true
},
Local {
    v=0
    c=IN IP4 $
    m=audio portA RTP/AVP *2*

    v=0
    c=IN IP4 $
    m=audio portA RTP/AVP *8*
}


Regards,

Javi






--------------050906070603060301050707
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
  <head>

    <meta http-equiv="content-type" content="text/html; charset=ISO-8859-1">
  </head>
  <body bgcolor="#ffffff" text="#000000">
    In a call, which is the difference between <span id="result_box"
      class="short_text" lang="en"><span class="hps">these</span> <span
        class="hps">two options (UDP port and IP address are the same in
        both?<br>
        <br>
        Case A):</span></span><br>
    <pre>LocalControl {
   ReservedValue = true
},
Local {
   v=0
   c=IN IP4 adrressX
   m=audio portA RTP/AVP <font color="#cc0000"><b>2 8</b></font>
}

<span id="result_box" class="short_text" lang="en"><span class="hps"></span></span></pre>
    <span id="result_box" class="short_text" lang="en"><span class="hps">Case
        B):<br>
        <br>
      </span></span><tt>LocalControl {<br>
      &nbsp;&nbsp; ReservedGroup = true<br>
      },<br>
      Local {<br>
      &nbsp;&nbsp; v=0<br>
      &nbsp;&nbsp; c=IN IP4 $<br>
      &nbsp;&nbsp; m=audio portA RTP/AVP <font color="#cc0000"><b>2</b></font><br>
      <br>
      &nbsp;&nbsp; v=0<br>
      &nbsp;&nbsp; c=IN IP4 $<br>
      &nbsp;&nbsp; m=audio portA RTP/AVP <font color="#cc0000"><b>8</b></font><br>
      }</tt><br>
    <br>
    <br>
    Regards,<br>
    <br>
    Javi<br>
    <br>
    <br>
    <br>
    <br>
    <br>
  </body>
</html>

--------------050906070603060301050707--

From Raju.Makaraju@alcatel-lucent.com  Fri Dec  9 10:21:55 2011
Return-Path: <Raju.Makaraju@alcatel-lucent.com>
X-Original-To: megaco@ietfa.amsl.com
Delivered-To: megaco@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3A71E21F88B6 for <megaco@ietfa.amsl.com>; Fri,  9 Dec 2011 10:21:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.549
X-Spam-Level: 
X-Spam-Status: No, score=-5.549 tagged_above=-999 required=5 tests=[AWL=-0.751, BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_12=0.6, J_CHICKENPOX_15=0.6, J_CHICKENPOX_32=0.6, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xWkexEg-yMhs for <megaco@ietfa.amsl.com>; Fri,  9 Dec 2011 10:21:54 -0800 (PST)
Received: from ihemail1.lucent.com (ihemail1.lucent.com [135.245.0.33]) by ietfa.amsl.com (Postfix) with ESMTP id 272D121F86C3 for <megaco@ietf.org>; Fri,  9 Dec 2011 10:21:53 -0800 (PST)
Received: from usnavsmail4.ndc.alcatel-lucent.com (usnavsmail4.ndc.alcatel-lucent.com [135.3.39.12]) by ihemail1.lucent.com (8.13.8/IER-o) with ESMTP id pB9ILqaL008775 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 9 Dec 2011 12:21:52 -0600 (CST)
Received: from USNAVSXCHHUB01.ndc.alcatel-lucent.com (usnavsxchhub01.ndc.alcatel-lucent.com [135.3.39.110]) by usnavsmail4.ndc.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id pB9ILqnX022243 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Fri, 9 Dec 2011 12:21:52 -0600
Received: from USNAVSXCHMBSD3.ndc.alcatel-lucent.com ([135.3.39.148]) by USNAVSXCHHUB01.ndc.alcatel-lucent.com ([135.3.39.110]) with mapi; Fri, 9 Dec 2011 12:21:52 -0600
From: "Makaraju, Maridi Raju (Raju)" <Raju.Makaraju@alcatel-lucent.com>
To: Javi <javi@trajano.us.es>, "megaco@ietf.org" <megaco@ietf.org>
Date: Fri, 9 Dec 2011 12:21:49 -0600
Thread-Topic: [Megaco] Several SDP session in a Local or Remote Descriptor
Thread-Index: Acy2nVo1S/wfR3dERiyyY0aT61ggIwAAPL7w
Message-ID: <31939CE9629A7F46885A9F97CEA9BF577C79C597@USNAVSXCHMBSD3.ndc.alcatel-lucent.com>
References: <4EE24E2C.9070504@trajano.us.es>
In-Reply-To: <4EE24E2C.9070504@trajano.us.es>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_31939CE9629A7F46885A9F97CEA9BF577C79C597USNAVSXCHMBSD3n_"
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.33
X-Scanned-By: MIMEDefang 2.64 on 135.3.39.12
Subject: Re: [Megaco] Several SDP session in a Local or Remote Descriptor
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.1.12
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: Fri, 09 Dec 2011 18:21:55 -0000

--_000_31939CE9629A7F46885A9F97CEA9BF577C79C597USNAVSXCHMBSD3n_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Javi,

For Case A with ReservedValue, MGW only reserves one RTP+ip. So, only one m=
edia session can be carried over, but the session
can use either payload formats 2 or 8.

For case B ReservedGroup, MGW reserves and returns 2 different RTP+IP addre=
sses (if resources are available), one for each group.
There could be 2 simultaneous media sessions carried using payload formats =
2 and 8 respectively, until reservedGroup is set to false.
Please note that reservedGroup can be kept ON until the termination is Subt=
racted.

Regards
Raju
________________________________
From: megaco-bounces@ietf.org [mailto:megaco-bounces@ietf.org] On Behalf Of=
 Javi
Sent: Friday, December 09, 2011 12:07 PM
To: megaco@ietf.org
Subject: [Megaco] Several SDP session in a Local or Remote Descriptor

In a call, which is the difference between these two options (UDP port and =
IP address are the same in both?

Case A):

LocalControl {
   ReservedValue =3D true
},
Local {
   v=3D0
   c=3DIN IP4 adrressX
   m=3Daudio portA RTP/AVP 2 8
}



Case B):

LocalControl {
   ReservedGroup =3D true
},
Local {
   v=3D0
   c=3DIN IP4 $
   m=3Daudio portA RTP/AVP 2

   v=3D0
   c=3DIN IP4 $
   m=3Daudio portA RTP/AVP 8
}


Regards,

Javi






--_000_31939CE9629A7F46885A9F97CEA9BF577C79C597USNAVSXCHMBSD3n_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=3D"text/html; charset=3Dus-ascii" http-equiv=3DContent-Type>
<META name=3DGENERATOR content=3D"MSHTML 8.00.6001.19154"></HEAD>
<BODY bgColor=3D#ffffff text=3D#000000>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D343501318-09122011><FONT color=3D=
#0000ff=20
size=3D2 face=3DArial>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D343501318-09122011><FONT color=3D=
#0000ff=20
size=3D2 face=3DArial>Javi,</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D343501318-09122011></SPAN>&nbsp;<=
/DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D343501318-09122011><FONT color=3D=
#0000ff=20
size=3D2 face=3DArial>For Case A with ReservedValue,&nbsp;MGW only reserves=
 one=20
RTP+ip. So, only one media session can be carried over, but the=20
session</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D343501318-09122011><FONT color=3D=
#0000ff=20
size=3D2 face=3DArial>can use either payload formats 2 or=20
8.</FONT></SPAN></DIV><BR></FONT></SPAN><SPAN class=3D343501318-09122011><F=
ONT=20
color=3D#0000ff size=3D2 face=3DArial>For&nbsp;case B ReservedGroup, MGW re=
serves and=20
returns 2 different RTP+IP addresses (if resources are available), one for =
each=20
group.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D343501318-09122011><FONT color=3D=
#0000ff=20
size=3D2 face=3DArial>There could be 2 simultaneous media sessions carried =
using=20
payload formats 2 and 8 respectively,&nbsp;until reservedGroup=20
</FONT></SPAN><SPAN class=3D343501318-09122011><FONT color=3D#0000ff size=
=3D2=20
face=3DArial>is set to false. </FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D343501318-09122011><FONT color=3D=
#0000ff=20
size=3D2 face=3DArial>Please note that reservedGroup can be kept ON until t=
he=20
termination is Subtracted.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D343501318-09122011><FONT color=3D=
#0000ff=20
size=3D2 face=3DArial></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D343501318-09122011><FONT color=3D=
#0000ff=20
size=3D2 face=3DArial>Regards</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D343501318-09122011><FONT color=3D=
#0000ff=20
size=3D2 face=3DArial>Raju</FONT></SPAN></DIV>
<BLOCKQUOTE=20
style=3D"BORDER-LEFT: #0000ff 2px solid; PADDING-LEFT: 5px; MARGIN-LEFT: 5p=
x; MARGIN-RIGHT: 0px">
  <DIV dir=3Dltr lang=3Den-us class=3DOutlookMessageHeader align=3Dleft>
  <HR tabIndex=3D-1>
  <FONT size=3D2 face=3DTahoma><B>From:</B> megaco-bounces@ietf.org=20
  [mailto:megaco-bounces@ietf.org] <B>On Behalf Of </B>Javi<BR><B>Sent:</B>=
=20
  Friday, December 09, 2011 12:07 PM<BR><B>To:</B>=20
  megaco@ietf.org<BR><B>Subject:</B> [Megaco] Several SDP session in a Loca=
l or=20
  Remote Descriptor<BR></FONT><BR></DIV>
  <DIV></DIV>In a call, which is the difference between <SPAN id=3Dresult_b=
ox=20
  lang=3Den class=3Dshort_text><SPAN class=3Dhps>these</SPAN> <SPAN class=
=3Dhps>two=20
  options (UDP port and IP address are the same in both?<BR><BR>Case=20
  A):</SPAN></SPAN><BR><PRE>LocalControl {
   ReservedValue =3D true
},
Local {
   v=3D0
   c=3DIN IP4 adrressX
   m=3Daudio portA RTP/AVP <FONT color=3D#cc0000><B>2 8</B></FONT>
}

<SPAN id=3Dresult_box lang=3Den class=3Dshort_text><SPAN class=3Dhps></SPAN=
></SPAN></PRE><SPAN=20
  id=3Dresult_box lang=3Den class=3Dshort_text><SPAN class=3Dhps>Case=20
  B):<BR><BR></SPAN></SPAN><TT>LocalControl {<BR>&nbsp;&nbsp; ReservedGroup=
 =3D=20
  true<BR>},<BR>Local {<BR>&nbsp;&nbsp; v=3D0<BR>&nbsp;&nbsp; c=3DIN IP4=20
  $<BR>&nbsp;&nbsp; m=3Daudio portA RTP/AVP <FONT=20
  color=3D#cc0000><B>2</B></FONT><BR><BR>&nbsp;&nbsp; v=3D0<BR>&nbsp;&nbsp;=
 c=3DIN IP4=20
  $<BR>&nbsp;&nbsp; m=3Daudio portA RTP/AVP <FONT=20
  color=3D#cc0000><B>8</B></FONT><BR>}</TT><BR><BR><BR>Regards,<BR><BR>Javi=
<BR><BR><BR><BR><BR><BR></BLOCKQUOTE></BODY></HTML>

--_000_31939CE9629A7F46885A9F97CEA9BF577C79C597USNAVSXCHMBSD3n_--

From javi@trajano.us.es  Fri Dec  9 10:41:12 2011
Return-Path: <javi@trajano.us.es>
X-Original-To: megaco@ietfa.amsl.com
Delivered-To: megaco@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A6FD521F84F9 for <megaco@ietfa.amsl.com>; Fri,  9 Dec 2011 10:41:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.098
X-Spam-Level: 
X-Spam-Status: No, score=-5.098 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_12=0.6, J_CHICKENPOX_15=0.6, J_CHICKENPOX_32=0.6, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Yv3dEMqCTCh4 for <megaco@ietfa.amsl.com>; Fri,  9 Dec 2011 10:41:12 -0800 (PST)
Received: from mail.us.es (mail.us.es [193.147.175.20]) by ietfa.amsl.com (Postfix) with ESMTP id 545DB21F8509 for <megaco@ietf.org>; Fri,  9 Dec 2011 10:41:11 -0800 (PST)
Received: (qmail 20325 invoked from network); 9 Dec 2011 19:41:09 +0100
Received: from unknown (HELO us.es) (192.168.2.13) by us.es with SMTP; 9 Dec 2011 19:41:09 +0100
Received: (qmail 31457 invoked by uid 507); 9 Dec 2011 18:41:08 -0000
Received: from 127.0.0.1 by antivirus3 (envelope-from <javi@trajano.us.es>, uid 501) with qmail-scanner-2.08 (clamdscan: 0.97.3/14103.   Clear:RC:1(127.0.0.1):.  Processed in 0.06089 secs); 09 Dec 2011 18:41:08 -0000
Received: from unknown (HELO antivirus3) (127.0.0.1) by us.es with SMTP; 9 Dec 2011 18:41:08 -0000
Received: from 192.168.1.13 (192.168.1.13) by antivirus3 (F-Secure/fsigk_smtp/406/antivirus3); Fri, 09 Dec 2011 19:41:08 +0100 (CET)
X-Virus-Status: clean(F-Secure/fsigk_smtp/406/antivirus3)
Received: (qmail 555 invoked from network); 9 Dec 2011 19:41:08 +0100
Received: from trajano.us.es (193.147.162.130) by us.es with AES256-SHA encrypted SMTP; 9 Dec 2011 19:41:08 +0100
Received: from [127.0.0.1] (112.pool85-56-79.dynamic.orange.es [85.56.79.112]) (authenticated bits=0) by trajano.us.es (8.13.8/8.13.8/Debian-3) with ESMTP id pB9If6I8018847 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NOT); Fri, 9 Dec 2011 19:41:07 +0100
Message-ID: <4EE25640.5000601@trajano.us.es>
Date: Fri, 09 Dec 2011 19:41:04 +0100
From: Javi <javi@trajano.us.es>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; es-ES; rv:1.9.2.24) Gecko/20111103 Thunderbird/3.1.16
MIME-Version: 1.0
To: "megaco@ietf.org" <megaco@ietf.org>
References: <4EE24E2C.9070504@trajano.us.es> <31939CE9629A7F46885A9F97CEA9BF577C79C597@USNAVSXCHMBSD3.ndc.alcatel-lucent.com>
In-Reply-To: <31939CE9629A7F46885A9F97CEA9BF577C79C597@USNAVSXCHMBSD3.ndc.alcatel-lucent.com>
Content-Type: multipart/alternative; boundary="------------050106050406070101030307"
Subject: Re: [Megaco] Several SDP session in a Local or Remote Descriptor
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.1.12
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: Fri, 09 Dec 2011 18:41:12 -0000

This is a multi-part message in MIME format.
--------------050106050406070101030307
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit

Raju,

But if IP address (and UDP port) is the same in both SDP sessions:

LocalControl {
    ReservedGroup = true
},
Local {
    v=0
    c=IN IP4 adrressX
    m=audio portA RTP/AVP *2*

    v=0
    c=IN IP4 adrressX
    m=audio portA RTP/AVP *8*
}

then there could not be 2 simultaneous media sessions. In that caso, 
would there be any differnce with?:

LocalControl {
    ReservedValue = true
},
Local {
    v=0
    c=IN IP4 adrressX
    m=audio portA RTP/AVP*2 8*
}



El 09/12/2011 19:21, Makaraju, Maridi Raju (Raju) escribió:
> Javi,
> For Case A with ReservedValue, MGW only reserves one RTP+ip. So, only 
> one media session can be carried over, but the session
> can use either payload formats 2 or 8.
>
> For case B ReservedGroup, MGW reserves and returns 2 different RTP+IP 
> addresses (if resources are available), one for each group.
> There could be 2 simultaneous media sessions carried using payload 
> formats 2 and 8 respectively, until reservedGroup is set to false.
> Please note that reservedGroup can be kept ON until the termination is 
> Subtracted.

> Regards
> Raju
>
>     ------------------------------------------------------------------------
>     *From:* megaco-bounces@ietf.org [mailto:megaco-bounces@ietf.org]
>     *On Behalf Of *Javi
>     *Sent:* Friday, December 09, 2011 12:07 PM
>     *To:* megaco@ietf.org
>     *Subject:* [Megaco] Several SDP session in a Local or Remote
>     Descriptor
>
>     In a call, which is the difference between these two options (UDP
>     port and IP address are the same in both?
>
>     Case A):
>
>     LocalControl {
>         ReservedValue = true
>     },
>     Local {
>         v=0
>         c=IN IP4 adrressX
>         m=audio portA RTP/AVP*2 8*
>     }
>
>
>     Case B):
>
>     LocalControl {
>        ReservedGroup = true
>     },
>     Local {
>        v=0
>        c=IN IP4 $
>        m=audio portA RTP/AVP *2*
>
>        v=0
>        c=IN IP4 $
>        m=audio portA RTP/AVP *8*
>     }
>
>
>     Regards,
>
>     Javi
>
>
>
>
>


--------------050106050406070101030307
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#ffffff" text="#000000">
    Raju,<br>
    <br>
    But if IP address (and UDP port) is the same in both SDP sessions:<br>
    <br>
    <tt>LocalControl {<br>
      &nbsp;&nbsp; ReservedGroup = true<br>
      },<br>
      Local {<br>
      &nbsp;&nbsp; v=0<br>
      &nbsp;&nbsp; c=IN IP4 adrressX<br>
      &nbsp;&nbsp; m=audio portA RTP/AVP <font color="#cc0000"><b>2</b></font><br>
      <br>
      &nbsp;&nbsp; v=0<br>
      &nbsp;&nbsp; c=IN IP4 adrressX<br>
      &nbsp;&nbsp; m=audio portA RTP/AVP <font color="#cc0000"><b>8</b></font><br>
      }</tt><br>
    <br>
    then there could not be 2 simultaneous media sessions. In that caso,
    would there be any differnce with?:<br>
    <br>
    <pre>LocalControl {
   ReservedValue = true
},
Local {
   v=0
   c=IN IP4 adrressX
   m=audio portA RTP/AVP <font color="#cc0000"><b>2 8</b></font>
}
</pre>
    <br>
    <br>
    El 09/12/2011 19:21, Makaraju, Maridi Raju (Raju) escribi&oacute;:<br>
    <blockquote
cite="mid:31939CE9629A7F46885A9F97CEA9BF577C79C597@USNAVSXCHMBSD3.ndc.alcatel-lucent.com"
      type="cite">
      <meta content="text/html; charset=ISO-8859-1"
        http-equiv="Content-Type">
      <meta name="GENERATOR" content="MSHTML 8.00.6001.19154">
      <div dir="ltr" align="left"><span class="343501318-09122011"><font
            size="2" color="#0000ff" face="Arial">
            <div dir="ltr" align="left"><span class="343501318-09122011"><font
                  size="2" color="#0000ff" face="Arial">Javi,</font></span></div>
            <div dir="ltr" align="left"><span class="343501318-09122011"></span>&nbsp;</div>
            <div dir="ltr" align="left"><span class="343501318-09122011"><font
                  size="2" color="#0000ff" face="Arial">For Case A with
                  ReservedValue,&nbsp;MGW only reserves one RTP+ip. So, only
                  one media session can be carried over, but the session</font></span></div>
            <div dir="ltr" align="left"><span class="343501318-09122011"><font
                  size="2" color="#0000ff" face="Arial">can use either
                  payload formats 2 or 8.</font></span></div>
            <br>
          </font></span><span class="343501318-09122011"><font size="2"
            color="#0000ff" face="Arial">For&nbsp;case B ReservedGroup, MGW
            reserves and returns 2 different RTP+IP addresses (if
            resources are available), one for each group.</font></span></div>
      <div dir="ltr" align="left"><span class="343501318-09122011"><font
            size="2" color="#0000ff" face="Arial">There could be 2
            simultaneous media sessions carried using payload formats 2
            and 8 respectively,&nbsp;until reservedGroup </font></span><span
          class="343501318-09122011"><font size="2" color="#0000ff"
            face="Arial">is set to false. </font></span></div>
      <div dir="ltr" align="left"><span class="343501318-09122011"><font
            size="2" color="#0000ff" face="Arial">Please note that
            reservedGroup can be kept ON until the termination is
            Subtracted.</font></span></div>
    </blockquote>
    <br>
    <blockquote
cite="mid:31939CE9629A7F46885A9F97CEA9BF577C79C597@USNAVSXCHMBSD3.ndc.alcatel-lucent.com"
      type="cite">
      <div dir="ltr" align="left"><span class="343501318-09122011"></span>&nbsp;</div>
      <div dir="ltr" align="left"><span class="343501318-09122011"><font
            size="2" color="#0000ff" face="Arial">Regards</font></span></div>
      <div dir="ltr" align="left"><span class="343501318-09122011"><font
            size="2" color="#0000ff" face="Arial">Raju</font></span></div>
      <blockquote style="border-left: 2px solid rgb(0, 0, 255);
        padding-left: 5px; margin-left: 5px; margin-right: 0px;">
        <div dir="ltr" class="OutlookMessageHeader" align="left"
          lang="en-us">
          <hr tabindex="-1"> <font size="2" face="Tahoma"><b>From:</b>
            <a class="moz-txt-link-abbreviated" href="mailto:megaco-bounces@ietf.org">megaco-bounces@ietf.org</a> [<a class="moz-txt-link-freetext" href="mailto:megaco-bounces@ietf.org">mailto:megaco-bounces@ietf.org</a>] <b>On
              Behalf Of </b>Javi<br>
            <b>Sent:</b> Friday, December 09, 2011 12:07 PM<br>
            <b>To:</b> <a class="moz-txt-link-abbreviated" href="mailto:megaco@ietf.org">megaco@ietf.org</a><br>
            <b>Subject:</b> [Megaco] Several SDP session in a Local or
            Remote Descriptor<br>
          </font><br>
        </div>
        In a call, which is the difference between <span
          id="result_box" class="short_text" lang="en"><span class="hps">these</span>
          <span class="hps">two options (UDP port and IP address are the
            same in both?<br>
            <br>
            Case A):</span></span><br>
        <pre>LocalControl {
   ReservedValue = true
},
Local {
   v=0
   c=IN IP4 adrressX
   m=audio portA RTP/AVP <font color="#cc0000"><b>2 8</b></font>
}

<span id="result_box" class="short_text" lang="en"><span class="hps"></span></span></pre>
        <span id="result_box" class="short_text" lang="en"><span
            class="hps">Case B):<br>
            <br>
          </span></span><tt>LocalControl {<br>
          &nbsp;&nbsp; ReservedGroup = true<br>
          },<br>
          Local {<br>
          &nbsp;&nbsp; v=0<br>
          &nbsp;&nbsp; c=IN IP4 $<br>
          &nbsp;&nbsp; m=audio portA RTP/AVP <font color="#cc0000"><b>2</b></font><br>
          <br>
          &nbsp;&nbsp; v=0<br>
          &nbsp;&nbsp; c=IN IP4 $<br>
          &nbsp;&nbsp; m=audio portA RTP/AVP <font color="#cc0000"><b>8</b></font><br>
          }</tt><br>
        <br>
        <br>
        Regards,<br>
        <br>
        Javi<br>
        <br>
        <br>
        <br>
        <br>
        <br>
      </blockquote>
    </blockquote>
    <br>
  </body>
</html>

--------------050106050406070101030307--

From Raju.Makaraju@alcatel-lucent.com  Fri Dec  9 13:52:50 2011
Return-Path: <Raju.Makaraju@alcatel-lucent.com>
X-Original-To: megaco@ietfa.amsl.com
Delivered-To: megaco@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 63C1F21F8A96 for <megaco@ietfa.amsl.com>; Fri,  9 Dec 2011 13:52:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.873
X-Spam-Level: 
X-Spam-Status: No, score=-4.873 tagged_above=-999 required=5 tests=[AWL=-0.675, BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_12=0.6, J_CHICKENPOX_15=0.6, J_CHICKENPOX_24=0.6, J_CHICKENPOX_32=0.6, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YaGm6bE0PVuQ for <megaco@ietfa.amsl.com>; Fri,  9 Dec 2011 13:52:49 -0800 (PST)
Received: from ihemail2.lucent.com (ihemail2.lucent.com [135.245.0.35]) by ietfa.amsl.com (Postfix) with ESMTP id 9F79F21F8A91 for <megaco@ietf.org>; Fri,  9 Dec 2011 13:52:49 -0800 (PST)
Received: from usnavsmail1.ndc.alcatel-lucent.com (usnavsmail1.ndc.alcatel-lucent.com [135.3.39.9]) by ihemail2.lucent.com (8.13.8/IER-o) with ESMTP id pB9LqljJ017589 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 9 Dec 2011 15:52:48 -0600 (CST)
Received: from USNAVSXCHHUB02.ndc.alcatel-lucent.com (usnavsxchhub02.ndc.alcatel-lucent.com [135.3.39.111]) by usnavsmail1.ndc.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id pB9LqkCZ013750 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Fri, 9 Dec 2011 15:52:47 -0600
Received: from USNAVSXCHMBSD3.ndc.alcatel-lucent.com ([135.3.39.148]) by USNAVSXCHHUB02.ndc.alcatel-lucent.com ([135.3.39.111]) with mapi; Fri, 9 Dec 2011 15:52:46 -0600
From: "Makaraju, Maridi Raju (Raju)" <Raju.Makaraju@alcatel-lucent.com>
To: Javi <javi@trajano.us.es>, "megaco@ietf.org" <megaco@ietf.org>
Date: Fri, 9 Dec 2011 15:52:37 -0600
Thread-Topic: [Megaco] Several SDP session in a Local or Remote Descriptor
Thread-Index: Acy2oiVnLdTMAvlrT6SQ0CtMirbtIQAGW7aw
Message-ID: <31939CE9629A7F46885A9F97CEA9BF577C79C5E2@USNAVSXCHMBSD3.ndc.alcatel-lucent.com>
References: <4EE24E2C.9070504@trajano.us.es> <31939CE9629A7F46885A9F97CEA9BF577C79C597@USNAVSXCHMBSD3.ndc.alcatel-lucent.com> <4EE25640.5000601@trajano.us.es>
In-Reply-To: <4EE25640.5000601@trajano.us.es>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_31939CE9629A7F46885A9F97CEA9BF577C79C5E2USNAVSXCHMBSD3n_"
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.35
X-Scanned-By: MIMEDefang 2.64 on 135.3.39.9
Subject: Re: [Megaco] Several SDP session in a Local or Remote Descriptor
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.1.12
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: Fri, 09 Dec 2011 21:52:50 -0000

--_000_31939CE9629A7F46885A9F97CEA9BF577C79C5E2USNAVSXCHMBSD3n_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Javi,

First of all, having same IP+port for both the groups will be an issue as M=
GW will receive bearer packets with
both payloads 2 and 8 at once single ip+port. If that is what really needed=
 then it would be preferred
to use ReservedValue.

To answer your question directly...
They are different: In group case the MGW may allocate 2 different resource=
s each handling formats 2,8 respectively.
But in value case MGW allocates just one resource handling both 2 and 8.
So, they are tightly coupled wrt MGW resource allocation and ip+port is ass=
ignment directly linked to resource allocation.

Regards
Raju

________________________________
From: Javi [mailto:javi@trajano.us.es]
Sent: Friday, December 09, 2011 12:41 PM
To: megaco@ietf.org
Subject: Re: [Megaco] Several SDP session in a Local or Remote Descriptor

Raju,

But if IP address (and UDP port) is the same in both SDP sessions:

LocalControl {
   ReservedGroup =3D true
},
Local {
   v=3D0
   c=3DIN IP4 adrressX
   m=3Daudio portA RTP/AVP 2

   v=3D0
   c=3DIN IP4 adrressX
   m=3Daudio portA RTP/AVP 8
}

then there could not be 2 simultaneous media sessions. In that caso, would =
there be any differnce with?:


LocalControl {
   ReservedValue =3D true
},
Local {
   v=3D0
   c=3DIN IP4 adrressX
   m=3Daudio portA RTP/AVP 2 8
}



El 09/12/2011 19:21, Makaraju, Maridi Raju (Raju) escribi=F3:
Javi,

For Case A with ReservedValue, MGW only reserves one RTP+ip. So, only one m=
edia session can be carried over, but the session
can use either payload formats 2 or 8.

For case B ReservedGroup, MGW reserves and returns 2 different RTP+IP addre=
sses (if resources are available), one for each group.
There could be 2 simultaneous media sessions carried using payload formats =
2 and 8 respectively, until reservedGroup is set to false.
Please note that reservedGroup can be kept ON until the termination is Subt=
racted.


Regards
Raju
________________________________
From: megaco-bounces@ietf.org<mailto:megaco-bounces@ietf.org> [mailto:megac=
o-bounces@ietf.org] On Behalf Of Javi
Sent: Friday, December 09, 2011 12:07 PM
To: megaco@ietf.org<mailto:megaco@ietf.org>
Subject: [Megaco] Several SDP session in a Local or Remote Descriptor

In a call, which is the difference between these two options (UDP port and =
IP address are the same in both?

Case A):

LocalControl {
   ReservedValue =3D true
},
Local {
   v=3D0
   c=3DIN IP4 adrressX
   m=3Daudio portA RTP/AVP 2 8
}



Case B):

LocalControl {
   ReservedGroup =3D true
},
Local {
   v=3D0
   c=3DIN IP4 $
   m=3Daudio portA RTP/AVP 2

   v=3D0
   c=3DIN IP4 $
   m=3Daudio portA RTP/AVP 8
}


Regards,

Javi







--_000_31939CE9629A7F46885A9F97CEA9BF577C79C5E2USNAVSXCHMBSD3n_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=3D"text/html; charset=3DISO-8859-1" http-equiv=3DContent-Type=
>
<META name=3DGENERATOR content=3D"MSHTML 8.00.6001.19154"></HEAD>
<BODY bgColor=3D#ffffff text=3D#000000>
<DIV dir=3Dltr align=3Dleft><FONT color=3D#0000ff size=3D2 face=3DArial><SP=
AN=20
class=3D049254321-09122011>Javi,</SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT color=3D#0000ff size=3D2 face=3DArial><SP=
AN=20
class=3D049254321-09122011></SPAN></FONT>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><FONT color=3D#0000ff size=3D2 face=3DArial><SP=
AN=20
class=3D049254321-09122011>First of all, having same IP+port for both the g=
roups=20
will be an issue as MGW will receive bearer packets with </SPAN></FONT></DI=
V>
<DIV dir=3Dltr align=3Dleft><FONT color=3D#0000ff size=3D2 face=3DArial><SP=
AN=20
class=3D049254321-09122011>both payloads 2 and 8 at once single ip+port. If=
 that=20
is what really needed then it would be preferred</SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT color=3D#0000ff size=3D2 face=3DArial><SP=
AN=20
class=3D049254321-09122011>to use ReservedValue.</SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT color=3D#0000ff size=3D2 face=3DArial><SP=
AN=20
class=3D049254321-09122011></SPAN></FONT>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><FONT color=3D#0000ff size=3D2 face=3DArial><SP=
AN=20
class=3D049254321-09122011>To answer your question directly...</SPAN></FONT=
></DIV>
<DIV dir=3Dltr align=3Dleft><FONT color=3D#0000ff size=3D2 face=3DArial><SP=
AN=20
class=3D049254321-09122011>They are different: In group case the MGW may al=
locate=20
2 different resources each handling formats 2,8=20
respectively.</SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT color=3D#0000ff size=3D2 face=3DArial><SP=
AN=20
class=3D049254321-09122011>But in value case MGW allocates just one resourc=
e=20
handling both 2 and 8.</SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT color=3D#0000ff size=3D2 face=3DArial><SP=
AN=20
class=3D049254321-09122011>So, they are tightly coupled wrt MGW resource=20
allocation and ip+port is assignment directly linked to resource=20
allocation.</SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT color=3D#0000ff size=3D2 face=3DArial><SP=
AN=20
class=3D049254321-09122011></SPAN></FONT>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><FONT color=3D#0000ff size=3D2 face=3DArial><SP=
AN=20
class=3D049254321-09122011>Regards</SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT color=3D#0000ff size=3D2 face=3DArial><SP=
AN=20
class=3D049254321-09122011></SPAN></FONT><FONT color=3D#0000ff size=3D2=20
face=3DArial><SPAN class=3D049254321-09122011>Raju</SPAN></FONT></DIV><BR>
<BLOCKQUOTE=20
style=3D"BORDER-LEFT: #0000ff 2px solid; PADDING-LEFT: 5px; MARGIN-LEFT: 5p=
x; MARGIN-RIGHT: 0px">
  <DIV dir=3Dltr lang=3Den-us class=3DOutlookMessageHeader align=3Dleft>
  <HR tabIndex=3D-1>
  <FONT size=3D2 face=3DTahoma><B>From:</B> Javi [mailto:javi@trajano.us.es=
]=20
  <BR><B>Sent:</B> Friday, December 09, 2011 12:41 PM<BR><B>To:</B>=20
  megaco@ietf.org<BR><B>Subject:</B> Re: [Megaco] Several SDP session in a =
Local=20
  or Remote Descriptor<BR></FONT><BR></DIV>
  <DIV></DIV>Raju,<BR><BR>But if IP address (and UDP port) is the same in b=
oth=20
  SDP sessions:<BR><BR><TT>LocalControl {<BR>&nbsp;&nbsp; ReservedGroup =3D=
=20
  true<BR>},<BR>Local {<BR>&nbsp;&nbsp; v=3D0<BR>&nbsp;&nbsp; c=3DIN IP4=20
  adrressX<BR>&nbsp;&nbsp; m=3Daudio portA RTP/AVP <FONT=20
  color=3D#cc0000><B>2</B></FONT><BR><BR>&nbsp;&nbsp; v=3D0<BR>&nbsp;&nbsp;=
 c=3DIN IP4=20
  adrressX<BR>&nbsp;&nbsp; m=3Daudio portA RTP/AVP <FONT=20
  color=3D#cc0000><B>8</B></FONT><BR>}</TT><BR><BR>then there could not be =
2=20
  simultaneous media sessions. In that caso, would there be any differnce=20
  with?:<BR><BR><PRE>LocalControl {
   ReservedValue =3D true
},
Local {
   v=3D0
   c=3DIN IP4 adrressX
   m=3Daudio portA RTP/AVP <FONT color=3D#cc0000><B>2 8</B></FONT>
}
</PRE><BR><BR>El 09/12/2011 19:21, Makaraju, Maridi Raju (Raju) escribi=F3:=
<BR>
  <BLOCKQUOTE=20
  cite=3Dmid:31939CE9629A7F46885A9F97CEA9BF577C79C597@USNAVSXCHMBSD3.ndc.al=
catel-lucent.com=20
  type=3D"cite">
    <META name=3DGENERATOR content=3D"MSHTML 8.00.6001.19154">
    <DIV dir=3Dltr align=3Dleft><SPAN class=3D343501318-09122011><FONT colo=
r=3D#0000ff=20
    size=3D2 face=3DArial>
    <DIV dir=3Dltr align=3Dleft><SPAN class=3D343501318-09122011><FONT colo=
r=3D#0000ff=20
    size=3D2 face=3DArial>Javi,</FONT></SPAN></DIV>
    <DIV dir=3Dltr align=3Dleft><SPAN class=3D343501318-09122011></SPAN>&nb=
sp;</DIV>
    <DIV dir=3Dltr align=3Dleft><SPAN class=3D343501318-09122011><FONT colo=
r=3D#0000ff=20
    size=3D2 face=3DArial>For Case A with ReservedValue,&nbsp;MGW only rese=
rves one=20
    RTP+ip. So, only one media session can be carried over, but the=20
    session</FONT></SPAN></DIV>
    <DIV dir=3Dltr align=3Dleft><SPAN class=3D343501318-09122011><FONT colo=
r=3D#0000ff=20
    size=3D2 face=3DArial>can use either payload formats 2 or=20
    8.</FONT></SPAN></DIV><BR></FONT></SPAN><SPAN class=3D343501318-0912201=
1><FONT=20
    color=3D#0000ff size=3D2 face=3DArial>For&nbsp;case B ReservedGroup, MG=
W reserves=20
    and returns 2 different RTP+IP addresses (if resources are available), =
one=20
    for each group.</FONT></SPAN></DIV>
    <DIV dir=3Dltr align=3Dleft><SPAN class=3D343501318-09122011><FONT colo=
r=3D#0000ff=20
    size=3D2 face=3DArial>There could be 2 simultaneous media sessions carr=
ied using=20
    payload formats 2 and 8 respectively,&nbsp;until reservedGroup=20
    </FONT></SPAN><SPAN class=3D343501318-09122011><FONT color=3D#0000ff si=
ze=3D2=20
    face=3DArial>is set to false. </FONT></SPAN></DIV>
    <DIV dir=3Dltr align=3Dleft><SPAN class=3D343501318-09122011><FONT colo=
r=3D#0000ff=20
    size=3D2 face=3DArial>Please note that reservedGroup can be kept ON unt=
il the=20
    termination is Subtracted.</FONT></SPAN></DIV></BLOCKQUOTE><BR>
  <BLOCKQUOTE=20
  cite=3Dmid:31939CE9629A7F46885A9F97CEA9BF577C79C597@USNAVSXCHMBSD3.ndc.al=
catel-lucent.com=20
  type=3D"cite">
    <DIV dir=3Dltr align=3Dleft><SPAN class=3D343501318-09122011></SPAN>&nb=
sp;</DIV>
    <DIV dir=3Dltr align=3Dleft><SPAN class=3D343501318-09122011><FONT colo=
r=3D#0000ff=20
    size=3D2 face=3DArial>Regards</FONT></SPAN></DIV>
    <DIV dir=3Dltr align=3Dleft><SPAN class=3D343501318-09122011><FONT colo=
r=3D#0000ff=20
    size=3D2 face=3DArial>Raju</FONT></SPAN></DIV>
    <BLOCKQUOTE=20
    style=3D"BORDER-LEFT: rgb(0,0,255) 2px solid; PADDING-LEFT: 5px; MARGIN=
-LEFT: 5px; MARGIN-RIGHT: 0px">
      <DIV dir=3Dltr lang=3Den-us class=3DOutlookMessageHeader align=3Dleft=
>
      <HR tabIndex=3D-1>
      <FONT size=3D2 face=3DTahoma><B>From:</B> <A class=3Dmoz-txt-link-abb=
reviated=20
      href=3D"mailto:megaco-bounces@ietf.org">megaco-bounces@ietf.org</A> [=
<A=20
      class=3Dmoz-txt-link-freetext=20
      href=3D"mailto:megaco-bounces@ietf.org">mailto:megaco-bounces@ietf.or=
g</A>]=20
      <B>On Behalf Of </B>Javi<BR><B>Sent:</B> Friday, December 09, 2011 12=
:07=20
      PM<BR><B>To:</B> <A class=3Dmoz-txt-link-abbreviated=20
      href=3D"mailto:megaco@ietf.org">megaco@ietf.org</A><BR><B>Subject:</B=
>=20
      [Megaco] Several SDP session in a Local or Remote=20
      Descriptor<BR></FONT><BR></DIV>In a call, which is the difference bet=
ween=20
      <SPAN id=3Dresult_box lang=3Den class=3Dshort_text><SPAN class=3Dhps>=
these</SPAN>=20
      <SPAN class=3Dhps>two options (UDP port and IP address are the same i=
n=20
      both?<BR><BR>Case A):</SPAN></SPAN><BR><PRE>LocalControl {
   ReservedValue =3D true
},
Local {
   v=3D0
   c=3DIN IP4 adrressX
   m=3Daudio portA RTP/AVP <FONT color=3D#cc0000><B>2 8</B></FONT>
}

<SPAN id=3Dresult_box lang=3Den class=3Dshort_text><SPAN class=3Dhps></SPAN=
></SPAN></PRE><SPAN=20
      id=3Dresult_box lang=3Den class=3Dshort_text><SPAN class=3Dhps>Case=20
      B):<BR><BR></SPAN></SPAN><TT>LocalControl {<BR>&nbsp;&nbsp; ReservedG=
roup=20
      =3D true<BR>},<BR>Local {<BR>&nbsp;&nbsp; v=3D0<BR>&nbsp;&nbsp; c=3DI=
N IP4=20
      $<BR>&nbsp;&nbsp; m=3Daudio portA RTP/AVP <FONT=20
      color=3D#cc0000><B>2</B></FONT><BR><BR>&nbsp;&nbsp; v=3D0<BR>&nbsp;&n=
bsp; c=3DIN=20
      IP4 $<BR>&nbsp;&nbsp; m=3Daudio portA RTP/AVP <FONT=20
      color=3D#cc0000><B>8</B></FONT><BR>}</TT><BR><BR><BR>Regards,<BR><BR>=
Javi<BR><BR><BR><BR><BR><BR></BLOCKQUOTE></BLOCKQUOTE><BR></BLOCKQUOTE></BO=
DY></HTML>

--_000_31939CE9629A7F46885A9F97CEA9BF577C79C5E2USNAVSXCHMBSD3n_--

From javi@trajano.us.es  Sat Dec 10 04:44:53 2011
Return-Path: <javi@trajano.us.es>
X-Original-To: megaco@ietfa.amsl.com
Delivered-To: megaco@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5AD7021F8B2E for <megaco@ietfa.amsl.com>; Sat, 10 Dec 2011 04:44:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.848
X-Spam-Level: 
X-Spam-Status: No, score=-5.848 tagged_above=-999 required=5 tests=[AWL=0.750,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LMQLU96CcNxF for <megaco@ietfa.amsl.com>; Sat, 10 Dec 2011 04:44:52 -0800 (PST)
Received: from mail.us.es (mail.us.es [193.147.175.20]) by ietfa.amsl.com (Postfix) with ESMTP id 531B121F8AF4 for <megaco@ietf.org>; Sat, 10 Dec 2011 04:44:51 -0800 (PST)
Received: (qmail 733 invoked from network); 10 Dec 2011 13:44:50 +0100
Received: from unknown (HELO us.es) (192.168.2.12) by us.es with SMTP; 10 Dec 2011 13:44:50 +0100
Received: (qmail 2548 invoked by uid 507); 10 Dec 2011 12:44:50 -0000
Received: from 127.0.0.1 by antivirus2 (envelope-from <javi@trajano.us.es>, uid 501) with qmail-scanner-2.08 (clamdscan: 0.97.3/14108.   Clear:RC:1(127.0.0.1):.  Processed in 0.036466 secs); 10 Dec 2011 12:44:50 -0000
Received: from unknown (HELO antivirus2) (127.0.0.1) by us.es with SMTP; 10 Dec 2011 12:44:49 -0000
Received: from 192.168.1.13 (192.168.1.13) by antivirus2 (F-Secure/fsigk_smtp/406/antivirus2); Sat, 10 Dec 2011 13:44:49 +0100 (CET)
X-Virus-Status: clean(F-Secure/fsigk_smtp/406/antivirus2)
Received: (qmail 15737 invoked from network); 10 Dec 2011 13:44:49 +0100
Received: from trajano.us.es (193.147.162.130) by us.es with AES256-SHA encrypted SMTP; 10 Dec 2011 13:44:49 +0100
Received: from [127.0.0.1] (112.pool85-56-79.dynamic.orange.es [85.56.79.112]) (authenticated bits=0) by trajano.us.es (8.13.8/8.13.8/Debian-3) with ESMTP id pBACimGh029301 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NOT) for <megaco@ietf.org>; Sat, 10 Dec 2011 13:44:49 +0100
Message-ID: <4EE3543D.8000301@trajano.us.es>
Date: Sat, 10 Dec 2011 13:44:45 +0100
From: Javi <javi@trajano.us.es>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; es-ES; rv:1.9.2.24) Gecko/20111103 Thunderbird/3.1.16
MIME-Version: 1.0
To: "megaco@ietf.org" <megaco@ietf.org>
Content-Type: multipart/alternative; boundary="------------040101050904020402030209"
Subject: [Megaco] OutOfService vs Inactive
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.1.12
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: Sat, 10 Dec 2011 12:44:53 -0000

This is a multi-part message in MIME format.
--------------040101050904020402030209
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

In a termination *with**a single stream*, which is the differencebetween?:

(a) TerminationState{ServiceStates=OutOfService}

(b) Media{ LocalControl { StreamMode=Inactive } }

Regards,

Javi

--------------040101050904020402030209
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
  <head>

    <meta http-equiv="content-type" content="text/html; charset=ISO-8859-1">
  </head>
  <body bgcolor="#ffffff" text="#000000">
    <span id="result_box" class="" lang="en"><span class="hps">In a</span>
      <span class="hps">termination <b>with</b></span><b> <span
          class="hps">a single stream</span></b><span>, which is</span>
      <span class="hps">the difference</span><span class=""> between?:<br>
        <br>
        (a) TerminationState{ServiceStates=OutOfService}<br>
        <br>
        (b) Media{ LocalControl { StreamMode=Inactive } }<br>
        <br>
        Regards,<br>
        <br>
        Javi<br>
      </span></span>
  </body>
</html>

--------------040101050904020402030209--

From javi@trajano.us.es  Sat Dec 10 04:44:54 2011
Return-Path: <javi@trajano.us.es>
X-Original-To: megaco@ietfa.amsl.com
Delivered-To: megaco@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1097D21F8AF4 for <megaco@ietfa.amsl.com>; Sat, 10 Dec 2011 04:44:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.898
X-Spam-Level: 
X-Spam-Status: No, score=-4.898 tagged_above=-999 required=5 tests=[AWL=-0.700, BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_12=0.6, J_CHICKENPOX_15=0.6, J_CHICKENPOX_24=0.6, J_CHICKENPOX_32=0.6, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yT8rnS1ncFpz for <megaco@ietfa.amsl.com>; Sat, 10 Dec 2011 04:44:53 -0800 (PST)
Received: from mail.us.es (mail.us.es [193.147.175.20]) by ietfa.amsl.com (Postfix) with ESMTP id 530F721F84B1 for <megaco@ietf.org>; Sat, 10 Dec 2011 04:44:51 -0800 (PST)
Received: (qmail 724 invoked from network); 10 Dec 2011 13:44:48 +0100
Received: from unknown (HELO us.es) (192.168.2.13) by us.es with SMTP; 10 Dec 2011 13:44:48 +0100
Received: (qmail 30283 invoked by uid 507); 10 Dec 2011 12:44:45 -0000
Received: from 127.0.0.1 by antivirus3 (envelope-from <javi@trajano.us.es>, uid 501) with qmail-scanner-2.08 (clamdscan: 0.97.3/14108.   Clear:RC:1(127.0.0.1):.  Processed in 0.064102 secs); 10 Dec 2011 12:44:45 -0000
Received: from unknown (HELO antivirus3) (127.0.0.1) by us.es with SMTP; 10 Dec 2011 12:44:44 -0000
Received: from 192.168.1.13 (192.168.1.13) by antivirus3 (F-Secure/fsigk_smtp/406/antivirus3); Sat, 10 Dec 2011 13:44:44 +0100 (CET)
X-Virus-Status: clean(F-Secure/fsigk_smtp/406/antivirus3)
Received: (qmail 15691 invoked from network); 10 Dec 2011 13:44:44 +0100
Received: from trajano.us.es (193.147.162.130) by us.es with AES256-SHA encrypted SMTP; 10 Dec 2011 13:44:44 +0100
Received: from [127.0.0.1] (112.pool85-56-79.dynamic.orange.es [85.56.79.112]) (authenticated bits=0) by trajano.us.es (8.13.8/8.13.8/Debian-3) with ESMTP id pBACigWT029297 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NOT); Sat, 10 Dec 2011 13:44:43 +0100
Message-ID: <4EE35436.50708@trajano.us.es>
Date: Sat, 10 Dec 2011 13:44:38 +0100
From: Javi <javi@trajano.us.es>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; es-ES; rv:1.9.2.24) Gecko/20111103 Thunderbird/3.1.16
MIME-Version: 1.0
To: "megaco@ietf.org" <megaco@ietf.org>
References: <4EE24E2C.9070504@trajano.us.es> <31939CE9629A7F46885A9F97CEA9BF577C79C597@USNAVSXCHMBSD3.ndc.alcatel-lucent.com> <4EE25640.5000601@trajano.us.es> <31939CE9629A7F46885A9F97CEA9BF577C79C5E2@USNAVSXCHMBSD3.ndc.alcatel-lucent.com>
In-Reply-To: <31939CE9629A7F46885A9F97CEA9BF577C79C5E2@USNAVSXCHMBSD3.ndc.alcatel-lucent.com>
Content-Type: multipart/alternative; boundary="------------010504080808000808080006"
Subject: Re: [Megaco] Several SDP session in a Local or Remote Descriptor
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.1.12
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: Sat, 10 Dec 2011 12:44:54 -0000

This is a multi-part message in MIME format.
--------------010504080808000808080006
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit

Raju,

Thanks for the clarification.

Regards,

Javi

El 09/12/2011 22:52, Makaraju, Maridi Raju (Raju) escribió:
> Javi,
> First of all, having same IP+port for both the groups will be an issue 
> as MGW will receive bearer packets with
> both payloads 2 and 8 at once single ip+port. If that is what really 
> needed then it would be preferred
> to use ReservedValue.
> To answer your question directly...
> They are different: In group case the MGW may allocate 2 different 
> resources each handling formats 2,8 respectively.
> But in value case MGW allocates just one resource handling both 2 and 8.
> So, they are tightly coupled wrt MGW resource allocation and ip+port 
> is assignment directly linked to resource allocation.
> Regards
> Raju
>
>     ------------------------------------------------------------------------
>     *From:* Javi [mailto:javi@trajano.us.es]
>     *Sent:* Friday, December 09, 2011 12:41 PM
>     *To:* megaco@ietf.org
>     *Subject:* Re: [Megaco] Several SDP session in a Local or Remote
>     Descriptor
>
>     Raju,
>
>     But if IP address (and UDP port) is the same in both SDP sessions:
>
>     LocalControl {
>        ReservedGroup = true
>     },
>     Local {
>        v=0
>        c=IN IP4 adrressX
>        m=audio portA RTP/AVP *2*
>
>        v=0
>        c=IN IP4 adrressX
>        m=audio portA RTP/AVP *8*
>     }
>
>     then there could not be 2 simultaneous media sessions. In that
>     caso, would there be any differnce with?:
>
>     LocalControl {
>         ReservedValue = true
>     },
>     Local {
>         v=0
>         c=IN IP4 adrressX
>         m=audio portA RTP/AVP*2 8*
>     }
>
>
>
>     El 09/12/2011 19:21, Makaraju, Maridi Raju (Raju) escribió:
>>     Javi,
>>     For Case A with ReservedValue, MGW only reserves one RTP+ip. So,
>>     only one media session can be carried over, but the session
>>     can use either payload formats 2 or 8.
>>
>>     For case B ReservedGroup, MGW reserves and returns 2 different
>>     RTP+IP addresses (if resources are available), one for each group.
>>     There could be 2 simultaneous media sessions carried using
>>     payload formats 2 and 8 respectively, until reservedGroup is set
>>     to false.
>>     Please note that reservedGroup can be kept ON until the
>>     termination is Subtracted.
>
>>     Regards
>>     Raju
>>
>>         ------------------------------------------------------------------------
>>         *From:* megaco-bounces@ietf.org
>>         [mailto:megaco-bounces@ietf.org] *On Behalf Of *Javi
>>         *Sent:* Friday, December 09, 2011 12:07 PM
>>         *To:* megaco@ietf.org
>>         *Subject:* [Megaco] Several SDP session in a Local or Remote
>>         Descriptor
>>
>>         In a call, which is the difference between these two options
>>         (UDP port and IP address are the same in both?
>>
>>         Case A):
>>
>>         LocalControl {
>>             ReservedValue = true
>>         },
>>         Local {
>>             v=0
>>             c=IN IP4 adrressX
>>             m=audio portA RTP/AVP*2 8*
>>         }
>>
>>
>>         Case B):
>>
>>         LocalControl {
>>            ReservedGroup = true
>>         },
>>         Local {
>>            v=0
>>            c=IN IP4 $
>>            m=audio portA RTP/AVP *2*
>>
>>            v=0
>>            c=IN IP4 $
>>            m=audio portA RTP/AVP *8*
>>         }
>>
>>
>>         Regards,
>>
>>         Javi
>>
>>
>>
>>
>>
>


--------------010504080808000808080006
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
    <title></title>
  </head>
  <body bgcolor="#ffffff" text="#000000">
    Raju,<br>
    <br>
    <span id="result_box" class="short_text" lang="en"><span class="hps">Thanks</span>
      <span class="hps">for the clarification.<br>
        <br>
        Regards,<br>
        <br>
        Javi<br>
      </span></span><br>
    El 09/12/2011 22:52, Makaraju, Maridi Raju (Raju) escribi&oacute;:
    <blockquote
cite="mid:31939CE9629A7F46885A9F97CEA9BF577C79C5E2@USNAVSXCHMBSD3.ndc.alcatel-lucent.com"
      type="cite">
      <meta content="text/html; charset=ISO-8859-1"
        http-equiv="Content-Type">
      <meta name="GENERATOR" content="MSHTML 8.00.6001.19154">
      <div dir="ltr" align="left"><font size="2" color="#0000ff"
          face="Arial"><span class="049254321-09122011">Javi,</span></font></div>
      <div dir="ltr" align="left"><font size="2" color="#0000ff"
          face="Arial"><span class="049254321-09122011"></span></font>&nbsp;</div>
      <div dir="ltr" align="left"><font size="2" color="#0000ff"
          face="Arial"><span class="049254321-09122011">First of all,
            having same IP+port for both the groups will be an issue as
            MGW will receive bearer packets with </span></font></div>
      <div dir="ltr" align="left"><font size="2" color="#0000ff"
          face="Arial"><span class="049254321-09122011">both payloads 2
            and 8 at once single ip+port. If that is what really needed
            then it would be preferred</span></font></div>
      <div dir="ltr" align="left"><font size="2" color="#0000ff"
          face="Arial"><span class="049254321-09122011">to use
            ReservedValue.</span></font></div>
      <div dir="ltr" align="left"><font size="2" color="#0000ff"
          face="Arial"><span class="049254321-09122011"></span></font>&nbsp;</div>
      <div dir="ltr" align="left"><font size="2" color="#0000ff"
          face="Arial"><span class="049254321-09122011">To answer your
            question directly...</span></font></div>
      <div dir="ltr" align="left"><font size="2" color="#0000ff"
          face="Arial"><span class="049254321-09122011">They are
            different: In group case the MGW may allocate 2 different
            resources each handling formats 2,8 respectively.</span></font></div>
      <div dir="ltr" align="left"><font size="2" color="#0000ff"
          face="Arial"><span class="049254321-09122011">But in value
            case MGW allocates just one resource handling both 2 and 8.</span></font></div>
      <div dir="ltr" align="left"><font size="2" color="#0000ff"
          face="Arial"><span class="049254321-09122011">So, they are
            tightly coupled wrt MGW resource allocation and ip+port is
            assignment directly linked to resource allocation.</span></font></div>
      <div dir="ltr" align="left"><font size="2" color="#0000ff"
          face="Arial"><span class="049254321-09122011"></span></font>&nbsp;</div>
      <div dir="ltr" align="left"><font size="2" color="#0000ff"
          face="Arial"><span class="049254321-09122011">Regards</span></font></div>
      <div dir="ltr" align="left"><font size="2" color="#0000ff"
          face="Arial"><span class="049254321-09122011"></span></font><font
          size="2" color="#0000ff" face="Arial"><span
            class="049254321-09122011">Raju</span></font></div>
      <br>
      <blockquote style="border-left: 2px solid rgb(0, 0, 255);
        padding-left: 5px; margin-left: 5px; margin-right: 0px;">
        <div dir="ltr" class="OutlookMessageHeader" align="left"
          lang="en-us">
          <hr tabindex="-1"> <font size="2" face="Tahoma"><b>From:</b>
            Javi [<a class="moz-txt-link-freetext" href="mailto:javi@trajano.us.es">mailto:javi@trajano.us.es</a>] <br>
            <b>Sent:</b> Friday, December 09, 2011 12:41 PM<br>
            <b>To:</b> <a class="moz-txt-link-abbreviated" href="mailto:megaco@ietf.org">megaco@ietf.org</a><br>
            <b>Subject:</b> Re: [Megaco] Several SDP session in a Local
            or Remote Descriptor<br>
          </font><br>
        </div>
        Raju,<br>
        <br>
        But if IP address (and UDP port) is the same in both SDP
        sessions:<br>
        <br>
        <tt>LocalControl {<br>
          &nbsp;&nbsp; ReservedGroup = true<br>
          },<br>
          Local {<br>
          &nbsp;&nbsp; v=0<br>
          &nbsp;&nbsp; c=IN IP4 adrressX<br>
          &nbsp;&nbsp; m=audio portA RTP/AVP <font color="#cc0000"><b>2</b></font><br>
          <br>
          &nbsp;&nbsp; v=0<br>
          &nbsp;&nbsp; c=IN IP4 adrressX<br>
          &nbsp;&nbsp; m=audio portA RTP/AVP <font color="#cc0000"><b>8</b></font><br>
          }</tt><br>
        <br>
        then there could not be 2 simultaneous media sessions. In that
        caso, would there be any differnce with?:<br>
        <br>
        <pre>LocalControl {
   ReservedValue = true
},
Local {
   v=0
   c=IN IP4 adrressX
   m=audio portA RTP/AVP <font color="#cc0000"><b>2 8</b></font>
}
</pre>
        <br>
        <br>
        El 09/12/2011 19:21, Makaraju, Maridi Raju (Raju) escribi&oacute;:<br>
        <blockquote
cite="mid:31939CE9629A7F46885A9F97CEA9BF577C79C597@USNAVSXCHMBSD3.ndc.alcatel-lucent.com"
          type="cite">
          <meta name="GENERATOR" content="MSHTML 8.00.6001.19154">
          <div dir="ltr" align="left"><span class="343501318-09122011"><font
                size="2" color="#0000ff" face="Arial">
                <div dir="ltr" align="left"><span
                    class="343501318-09122011"><font size="2"
                      color="#0000ff" face="Arial">Javi,</font></span></div>
                <div dir="ltr" align="left"><span
                    class="343501318-09122011"></span>&nbsp;</div>
                <div dir="ltr" align="left"><span
                    class="343501318-09122011"><font size="2"
                      color="#0000ff" face="Arial">For Case A with
                      ReservedValue,&nbsp;MGW only reserves one RTP+ip. So,
                      only one media session can be carried over, but
                      the session</font></span></div>
                <div dir="ltr" align="left"><span
                    class="343501318-09122011"><font size="2"
                      color="#0000ff" face="Arial">can use either
                      payload formats 2 or 8.</font></span></div>
                <br>
              </font></span><span class="343501318-09122011"><font
                size="2" color="#0000ff" face="Arial">For&nbsp;case B
                ReservedGroup, MGW reserves and returns 2 different
                RTP+IP addresses (if resources are available), one for
                each group.</font></span></div>
          <div dir="ltr" align="left"><span class="343501318-09122011"><font
                size="2" color="#0000ff" face="Arial">There could be 2
                simultaneous media sessions carried using payload
                formats 2 and 8 respectively,&nbsp;until reservedGroup </font></span><span
              class="343501318-09122011"><font size="2" color="#0000ff"
                face="Arial">is set to false. </font></span></div>
          <div dir="ltr" align="left"><span class="343501318-09122011"><font
                size="2" color="#0000ff" face="Arial">Please note that
                reservedGroup can be kept ON until the termination is
                Subtracted.</font></span></div>
        </blockquote>
        <br>
        <blockquote
cite="mid:31939CE9629A7F46885A9F97CEA9BF577C79C597@USNAVSXCHMBSD3.ndc.alcatel-lucent.com"
          type="cite">
          <div dir="ltr" align="left"><span class="343501318-09122011"></span>&nbsp;</div>
          <div dir="ltr" align="left"><span class="343501318-09122011"><font
                size="2" color="#0000ff" face="Arial">Regards</font></span></div>
          <div dir="ltr" align="left"><span class="343501318-09122011"><font
                size="2" color="#0000ff" face="Arial">Raju</font></span></div>
          <blockquote style="border-left: 2px solid rgb(0, 0, 255);
            padding-left: 5px; margin-left: 5px; margin-right: 0px;">
            <div dir="ltr" class="OutlookMessageHeader" align="left"
              lang="en-us">
              <hr tabindex="-1"> <font size="2" face="Tahoma"><b>From:</b>
                <a moz-do-not-send="true"
                  class="moz-txt-link-abbreviated"
                  href="mailto:megaco-bounces@ietf.org">megaco-bounces@ietf.org</a>
                [<a moz-do-not-send="true" class="moz-txt-link-freetext"
                  href="mailto:megaco-bounces@ietf.org">mailto:megaco-bounces@ietf.org</a>]
                <b>On Behalf Of </b>Javi<br>
                <b>Sent:</b> Friday, December 09, 2011 12:07 PM<br>
                <b>To:</b> <a moz-do-not-send="true"
                  class="moz-txt-link-abbreviated"
                  href="mailto:megaco@ietf.org">megaco@ietf.org</a><br>
                <b>Subject:</b> [Megaco] Several SDP session in a Local
                or Remote Descriptor<br>
              </font><br>
            </div>
            In a call, which is the difference between <span
              id="result_box" class="short_text" lang="en"><span
                class="hps">these</span> <span class="hps">two options
                (UDP port and IP address are the same in both?<br>
                <br>
                Case A):</span></span><br>
            <pre>LocalControl {
   ReservedValue = true
},
Local {
   v=0
   c=IN IP4 adrressX
   m=audio portA RTP/AVP <font color="#cc0000"><b>2 8</b></font>
}

<span id="result_box" class="short_text" lang="en"><span class="hps"></span></span></pre>
            <span id="result_box" class="short_text" lang="en"><span
                class="hps">Case B):<br>
                <br>
              </span></span><tt>LocalControl {<br>
              &nbsp;&nbsp; ReservedGroup = true<br>
              },<br>
              Local {<br>
              &nbsp;&nbsp; v=0<br>
              &nbsp;&nbsp; c=IN IP4 $<br>
              &nbsp;&nbsp; m=audio portA RTP/AVP <font color="#cc0000"><b>2</b></font><br>
              <br>
              &nbsp;&nbsp; v=0<br>
              &nbsp;&nbsp; c=IN IP4 $<br>
              &nbsp;&nbsp; m=audio portA RTP/AVP <font color="#cc0000"><b>8</b></font><br>
              }</tt><br>
            <br>
            <br>
            Regards,<br>
            <br>
            Javi<br>
            <br>
            <br>
            <br>
            <br>
            <br>
          </blockquote>
        </blockquote>
        <br>
      </blockquote>
    </blockquote>
    <br>
  </body>
</html>

--------------010504080808000808080006--

From javi@trajano.us.es  Sat Dec 10 05:03:42 2011
Return-Path: <javi@trajano.us.es>
X-Original-To: megaco@ietfa.amsl.com
Delivered-To: megaco@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1166321F84DD for <megaco@ietfa.amsl.com>; Sat, 10 Dec 2011 05:03:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.324
X-Spam-Level: 
X-Spam-Status: No, score=-5.324 tagged_above=-999 required=5 tests=[AWL=0.075,  BAYES_00=-2.599, J_CHICKENPOX_12=0.6, J_CHICKENPOX_15=0.6, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id d8R7oDlJq2av for <megaco@ietfa.amsl.com>; Sat, 10 Dec 2011 05:03:41 -0800 (PST)
Received: from mail.us.es (mail.us.es [193.147.175.20]) by ietfa.amsl.com (Postfix) with ESMTP id 05C7821F84D7 for <megaco@ietf.org>; Sat, 10 Dec 2011 05:03:40 -0800 (PST)
Received: (qmail 6423 invoked from network); 10 Dec 2011 14:03:39 +0100
Received: from unknown (HELO us.es) (192.168.2.13) by us.es with SMTP; 10 Dec 2011 14:03:39 +0100
Received: (qmail 12250 invoked by uid 507); 10 Dec 2011 13:03:39 -0000
Received: from 127.0.0.1 by antivirus3 (envelope-from <javi@trajano.us.es>, uid 501) with qmail-scanner-2.08 (clamdscan: 0.97.3/14108.   Clear:RC:1(127.0.0.1):.  Processed in 0.033223 secs); 10 Dec 2011 13:03:39 -0000
Received: from unknown (HELO antivirus3) (127.0.0.1) by us.es with SMTP; 10 Dec 2011 13:03:38 -0000
Received: from 192.168.1.13 (192.168.1.13) by antivirus3 (F-Secure/fsigk_smtp/406/antivirus3); Sat, 10 Dec 2011 14:03:38 +0100 (CET)
X-Virus-Status: clean(F-Secure/fsigk_smtp/406/antivirus3)
Received: (qmail 32362 invoked from network); 10 Dec 2011 14:03:38 +0100
Received: from trajano.us.es (193.147.162.130) by us.es with AES256-SHA encrypted SMTP; 10 Dec 2011 14:03:38 +0100
Received: from [127.0.0.1] (112.pool85-56-79.dynamic.orange.es [85.56.79.112]) (authenticated bits=0) by trajano.us.es (8.13.8/8.13.8/Debian-3) with ESMTP id pBAD3bPR029515 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NOT) for <megaco@ietf.org>; Sat, 10 Dec 2011 14:03:37 +0100
Message-ID: <4EE358A5.2040408@trajano.us.es>
Date: Sat, 10 Dec 2011 14:03:33 +0100
From: Javi <javi@trajano.us.es>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; es-ES; rv:1.9.2.24) Gecko/20111103 Thunderbird/3.1.16
MIME-Version: 1.0
To: "megaco@ietf.org" <megaco@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: [Megaco] Allocation resources for a call
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.1.12
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: Sat, 10 Dec 2011 13:03:42 -0000

I have a callwith the following 3 phases:

A) Phase A: MG may carry media to a equipment A using the codec x.

B) Phase B: MG may carry media to a equipment B using the codec y.

C) Phase C: again, MG may carry media to the equipment A using the codec x.


In that case, what is the most appropriate way to model the call on the 
gateway to ensure that once the call starts the gateway will have the 
necessary resources for all phases?

(i) 2 terminations (in the same or different context?) using the 
property "StreamMode=Inactive":

* Termination 1 with:
     v=0
     c=IN IP4 IP_A
     m=audio port_A  RTP/AVP codec_x

* Termination 2 with:
     v=0
     c=IN IP4 IP_B
     m=audio port_B  RTP/AVP codec_y

In phase:
     (A, C) Termination 1 with StreamMode=SendRecv; Termination 2 with 
StreamMode=Inactive
     (B) Termination 1 with StreamMode=Inactive; Termination 2 with 
StreamMode=SendRecv

===

(ii) 1 termination with 2 session descriptions with ReserveGroup=true:

In Phase A:
LocalControl {
ReserveGroup = True},
Local/Remote {
     v=0
     c=IN IP4 IP_A
     m=audio port_A  RTP/AVP codec_x
     v=0
     c=IN IP4 IP_B
     m=audio port_B  RTP/AVP codec_y
}

In Phase B:
LocalControl {
ReserveGroup = True},
Local/Remote {
     v=0
     c=IN IP4 IP_B
     m=audio port_B  RTP/AVP codec_y
     v=0
     c=IN IP4 IP_A
     m=audio port_A  RTP/AVP codec_x
}

In Phase C:
Local/Remote {
     v=0
     c=IN IP4 IP_A
     m=audio port_A  RTP/AVP codec_x
}

===

(iii) 1 termination with 1 session descriptions with ReserveValue=true 
to allocate the resources:

Phase A)
LocalControl {
ReserveValue = True},
Local/Remote {
     v=0
     c=IN IP4 IP_A
     m=audio port_A  RTP/AVP codec_x  codec_y
}

Phase B)
LocalControl {
ReserveValue = True},
Local/Remote {
     v=0
     c=IN IP4 IP_B
     m=audio port_B  RTP/AVP codec_y  codec_x
}

Phase C)
Local/Remote {
     v=0
     c=IN IP4 IP_A
     m=audio port_A  RTP/AVP codec_x
}



Regards,

Javi


From Christian.Groves@nteczone.com  Sun Dec 11 14:51:34 2011
Return-Path: <Christian.Groves@nteczone.com>
X-Original-To: megaco@ietfa.amsl.com
Delivered-To: megaco@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 259FE21F84AC for <megaco@ietfa.amsl.com>; Sun, 11 Dec 2011 14:51:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id J5ceFk9iX0Me for <megaco@ietfa.amsl.com>; Sun, 11 Dec 2011 14:51:32 -0800 (PST)
Received: from ipmail06.adl2.internode.on.net (ipmail06.adl2.internode.on.net [150.101.137.129]) by ietfa.amsl.com (Postfix) with ESMTP id 4856021F84AA for <megaco@ietf.org>; Sun, 11 Dec 2011 14:51:30 -0800 (PST)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: ApMBAI0y5U520fqM/2dsb2JhbAAMN61qAQEBBAEBATUbGwoRCxgJFg8JAwIBAgEVMBMGAgEBiAyzVASIU4MaBKcs
Received: from ppp118-209-250-140.lns20.mel6.internode.on.net (HELO [127.0.0.1]) ([118.209.250.140]) by ipmail06.adl2.internode.on.net with ESMTP; 12 Dec 2011 09:21:28 +1030
Message-ID: <4EE533ED.8030006@nteczone.com>
Date: Mon, 12 Dec 2011 09:51:25 +1100
From: Christian Groves <Christian.Groves@nteczone.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:8.0) Gecko/20111105 Thunderbird/8.0
MIME-Version: 1.0
To: megaco@ietf.org
References: <4EE3543D.8000301@trajano.us.es>
In-Reply-To: <4EE3543D.8000301@trajano.us.es>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [Megaco] OutOfService vs Inactive
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.1.12
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: Sun, 11 Dec 2011 22:51:34 -0000

Hello Javi,

ServiceState and Streammode are fundamentally different things. 
Streammode is related to activity on the bearer. ServiceState is related 
to MG internal "readiness". Also the Streammode can be controlled by the 
MGC. i.e. it can change Inactive to Send/Receive.
ServiceState is largely controlled by the MG. i.e. the MGC can't change 
OutOfService to InService.

Regards, Christian

On 10/12/2011 11:44 PM, Javi wrote:
> In a termination *with**a single stream*, which is the differencebetween?:
>
> (a) TerminationState{ServiceStates=OutOfService}
>
> (b) Media{ LocalControl { StreamMode=Inactive } }
>
> Regards,
>
> Javi
>
>
> _______________________________________________
> Megaco mailing list
> Megaco@ietf.org
> https://www.ietf.org/mailman/listinfo/megaco

From Christian.Groves@nteczone.com  Sun Dec 11 14:56:17 2011
Return-Path: <Christian.Groves@nteczone.com>
X-Original-To: megaco@ietfa.amsl.com
Delivered-To: megaco@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8DB6021F84A1 for <megaco@ietfa.amsl.com>; Sun, 11 Dec 2011 14:56:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[AWL=-0.600, BAYES_00=-2.599, J_CHICKENPOX_12=0.6, J_CHICKENPOX_15=0.6]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xfkFHnjduR42 for <megaco@ietfa.amsl.com>; Sun, 11 Dec 2011 14:56:17 -0800 (PST)
Received: from ipmail06.adl2.internode.on.net (ipmail06.adl2.internode.on.net [150.101.137.129]) by ietfa.amsl.com (Postfix) with ESMTP id 9A94421F849E for <megaco@ietf.org>; Sun, 11 Dec 2011 14:56:16 -0800 (PST)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: ApMBAI0y5U520fqM/2dsb2JhbAAMN61qAQEBBAEBATUbGwoRCxgJFg8JAwIBAgEVMBMGAgEBiAyzVASIU4MaBKcs
Received: from ppp118-209-250-140.lns20.mel6.internode.on.net (HELO [127.0.0.1]) ([118.209.250.140]) by ipmail06.adl2.internode.on.net with ESMTP; 12 Dec 2011 09:26:15 +1030
Message-ID: <4EE5350C.2070109@nteczone.com>
Date: Mon, 12 Dec 2011 09:56:12 +1100
From: Christian Groves <Christian.Groves@nteczone.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:8.0) Gecko/20111105 Thunderbird/8.0
MIME-Version: 1.0
To: megaco@ietf.org
References: <4EE358A5.2040408@trajano.us.es>
In-Reply-To: <4EE358A5.2040408@trajano.us.es>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [Megaco] Allocation resources for a call
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.1.12
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: Sun, 11 Dec 2011 22:56:17 -0000

HEllo Javi,

I'm not sure what the issue is? This just sounds like a normal 
transcoding case.
i.e. For Termination connection to equipment A set codec X, for the 
Termination connected to equipment B set codec Y. The MG simply 
transcodes the codec format when sending a A or B.

Regards, Christian

On 11/12/2011 12:03 AM, Javi wrote:
> I have a callwith the following 3 phases:
>
> A) Phase A: MG may carry media to a equipment A using the codec x.
>
> B) Phase B: MG may carry media to a equipment B using the codec y.
>
> C) Phase C: again, MG may carry media to the equipment A using the 
> codec x.
>
>
> In that case, what is the most appropriate way to model the call on 
> the gateway to ensure that once the call starts the gateway will have 
> the necessary resources for all phases?
>
> (i) 2 terminations (in the same or different context?) using the 
> property "StreamMode=Inactive":
>
> * Termination 1 with:
>     v=0
>     c=IN IP4 IP_A
>     m=audio port_A  RTP/AVP codec_x
>
> * Termination 2 with:
>     v=0
>     c=IN IP4 IP_B
>     m=audio port_B  RTP/AVP codec_y
>
> In phase:
>     (A, C) Termination 1 with StreamMode=SendRecv; Termination 2 with 
> StreamMode=Inactive
>     (B) Termination 1 with StreamMode=Inactive; Termination 2 with 
> StreamMode=SendRecv
>
> ===
>
> (ii) 1 termination with 2 session descriptions with ReserveGroup=true:
>
> In Phase A:
> LocalControl {
> ReserveGroup = True},
> Local/Remote {
>     v=0
>     c=IN IP4 IP_A
>     m=audio port_A  RTP/AVP codec_x
>     v=0
>     c=IN IP4 IP_B
>     m=audio port_B  RTP/AVP codec_y
> }
>
> In Phase B:
> LocalControl {
> ReserveGroup = True},
> Local/Remote {
>     v=0
>     c=IN IP4 IP_B
>     m=audio port_B  RTP/AVP codec_y
>     v=0
>     c=IN IP4 IP_A
>     m=audio port_A  RTP/AVP codec_x
> }
>
> In Phase C:
> Local/Remote {
>     v=0
>     c=IN IP4 IP_A
>     m=audio port_A  RTP/AVP codec_x
> }
>
> ===
>
> (iii) 1 termination with 1 session descriptions with ReserveValue=true 
> to allocate the resources:
>
> Phase A)
> LocalControl {
> ReserveValue = True},
> Local/Remote {
>     v=0
>     c=IN IP4 IP_A
>     m=audio port_A  RTP/AVP codec_x  codec_y
> }
>
> Phase B)
> LocalControl {
> ReserveValue = True},
> Local/Remote {
>     v=0
>     c=IN IP4 IP_B
>     m=audio port_B  RTP/AVP codec_y  codec_x
> }
>
> Phase C)
> Local/Remote {
>     v=0
>     c=IN IP4 IP_A
>     m=audio port_A  RTP/AVP codec_x
> }
>
>
>
> Regards,
>
> Javi
>
> _______________________________________________
> Megaco mailing list
> Megaco@ietf.org
> https://www.ietf.org/mailman/listinfo/megaco
>

From bill.wu@huawei.com  Sun Dec 11 20:06:31 2011
Return-Path: <bill.wu@huawei.com>
X-Original-To: megaco@ietfa.amsl.com
Delivered-To: megaco@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 93CFC21F86B3; Sun, 11 Dec 2011 20:06:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.716
X-Spam-Level: 
X-Spam-Status: No, score=-5.716 tagged_above=-999 required=5 tests=[AWL=-0.317, BAYES_00=-2.599, J_CHICKENPOX_14=0.6, J_CHICKENPOX_74=0.6, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Rwb6WCmJzFUS; Sun, 11 Dec 2011 20:06:29 -0800 (PST)
Received: from szxga01-in.huawei.com (szxga01-in.huawei.com [119.145.14.64]) by ietfa.amsl.com (Postfix) with ESMTP id 2F07521F8672; Sun, 11 Dec 2011 20:06:29 -0800 (PST)
Received: from huawei.com (szxga05-in [172.24.2.49]) by szxga05-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LW200KRCONNCG@szxga05-in.huawei.com>; Mon, 12 Dec 2011 12:04:35 +0800 (CST)
Received: from szxrg01-dlp.huawei.com ([172.24.2.119]) by szxga05-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LW200KF5ONKL4@szxga05-in.huawei.com>; Mon, 12 Dec 2011 12:04:35 +0800 (CST)
Received: from szxeml207-edg.china.huawei.com ([172.24.2.119]) by szxrg01-dlp.huawei.com (MOS 4.1.9-GA)	with ESMTP id AFT71892; Mon, 12 Dec 2011 12:04:35 +0800
Received: from SZXEML412-HUB.china.huawei.com (10.82.67.91) by szxeml207-edg.china.huawei.com (172.24.2.59) with Microsoft SMTP Server (TLS) id 14.1.323.3; Mon, 12 Dec 2011 12:04:34 +0800
Received: from w53375q (10.138.41.130) by szxeml412-hub.china.huawei.com (10.82.67.91) with Microsoft SMTP Server (TLS) id 14.1.323.3; Mon, 12 Dec 2011 12:04:32 +0800
Date: Mon, 12 Dec 2011 12:04:31 +0800
From: Qin Wu <bill.wu@huawei.com>
X-Originating-IP: [10.138.41.130]
To: "Schwarz, Albrecht (Albrecht)" <albrecht.schwarz@alcatel-lucent.com>, avt@ietf.org
Message-id: <6C618D1EA52146A781429C6B08C4A4FC@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.6109
X-Mailer: Microsoft Outlook Express 6.00.2900.5931
Content-type: text/plain; charset=ISO-8859-1
Content-transfer-encoding: 7BIT
X-Priority: 3
X-MSMail-priority: Normal
X-CFilter-Loop: Reflected
References: <20111129075613.12419.4377.idtracker@ietfa.amsl.com> <5F7BCCF5541B7444830A2288ABBEBC96216190051A@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com> <EAC481B4D8034C38AC54E1217F8D875D@china.huawei.com> <5F7BCCF5541B7444830A2288ABBEBC96216190077F@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com> <B527BAFA038842A8939A8C2D558074CD@china.huawei.com> <5F7BCCF5541B7444830A2288ABBEBC962161900908@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com> <9FF9B04A84E64AD7ABCCC4F2ACC1E19A@china.huawei.com> <5F7BCCF5541B7444830A2288ABBEBC9621620F4AF5@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com> <D44A4820E0D24DD79F6F5A4B7507D0D6@china.huawei.com> <5F7BCCF5541B7444830A2288ABBEBC9621620F4ED2@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com> <71112008FBA94D35B07FA6B4916075B6@china.huawei.com> <5F7BCCF5541B7444830A2288ABBEBC9621620F5258@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com>
Cc: megaco@ietf.org
Subject: Re: [Megaco] [AVTCORE] Types of monitoring architectures; RE:  I-D Action: draft-ietf-avtcore-monarch-08.txt
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.1.12
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: Mon, 12 Dec 2011 04:06:31 -0000

Hi, Albrecht:
My understanding to QoE measurment is:
The factors that influence the QoE metric include encoding system, transport network, access network,home network and end device.
If the customer(e.g., network operator) doesn't know the original content, the QoE metric should be usually measured at the user device.
If the customer knows the original content, the QoE metric can be measured either in the network or at the user device.
Given the growing popularity of connected devices, these devices may have different capability corresponding to CPU load, processing overhead, storage, batteries.
If the cusomer want to measure QoE without considering connected devices with various capability , the QoE metric can be measured at the point between
access network and home network.

Regarding the monitoring scenario you mentioned, I am not familiar with such scenario with RTP-to-PSTN gateway deployed.
But I am aware that there are scenarios with SIP to PSTN gateway or SIP to H.323 gateway widely deployed,  RFC6035 defines a new SIP event package, vq-rtcpxr
that enable the collection and  reporting of metrics that measure quality for RTP sessions. In such cases, RTCP XR VOIP metric with QoE metric included is measured  
at the user device and mapped into the equivalent SIP vq-rtcpxr parameter since SIP session call is established end to end and RTP media stream is exchanged directly between
one endpoint and the other endpoint.

Regards!
-Qin
----- Original Message ----- 
From: "Schwarz, Albrecht (Albrecht)" <albrecht.schwarz@alcatel-lucent.com>
To: "Qin Wu" <bill.wu@huawei.com>; <avt@ietf.org>
Cc: <megaco@ietf.org>
Sent: Saturday, December 10, 2011 12:01 AM
Subject: RE: [AVTCORE] Types of monitoring architectures; RE: I-D Action: draft-ietf-avtcore-monarch-08.txt


How do you explain to a network operator the value of QoE measurements by an RTP receiver / RTP monitor component located in an RTP-to-PSTN gateway?

This would be a monitoring scenario inline with MONARCH, but with valueless QoE results, right?


> -----Original Message-----
> From: Qin Wu [mailto:bill.wu@huawei.com]
> Sent: Donnerstag, 8. Dezember 2011 03:26
> To: Schwarz, Albrecht (Albrecht); avt@ietf.org
> Cc: megaco@ietf.org
> Subject: Re: [AVTCORE] Types of monitoring architectures; RE:
> I-D Action: draft-ietf-avtcore-monarch-08.txt
>
> You reiterate what you propose for physical entities in the
> early email.
> I am still not convicing with that.
>
> Since we have RTP components like RTP end system, RTP mixer,
> RTP media translator, RTP transport translator, RTP monitor
> specified in RFC3550 can be built into these component as a
> application. also monitor can be disjointed from these RTP
> components as a third party monitor. why we need to specify
> how to map RTP end system into user equipment, RTP translator
> or RTP mixer can be mapped into RTP-PSTN gateway, or IP to IP
> border gateway since we have already mapped monitor into
> different RTP components.
> How many PE types you can enumerate? why they should be scope
> of RTP monitoring architecture?
>
> Also as specified in MONARCH draft, we have end sytem
> metrics, transport level metric, transport level metric, they
> can be measured and collected from the different RTP
> comoponents specified in RFC3550, RFC5117. Apparently end
> system metric can only be collected from RTP end system.
> transport metric is collected from any RTP system in the RTP
> monitoring architecture, regarding application level metric,
> apparently they should be measured at the application layer
> and can not be collected from RTP transport translator, Also
> RTP transport translator is still a functional entity rather
> than a physical entity. I am not convincing with what you
> said about "contradiction", "lead to possible wrong expectations".
>
> Regards!
> -Qin
> ----- Original Message -----
> From: "Schwarz, Albrecht (Albrecht)"
> <albrecht.schwarz@alcatel-lucent.com>
> To: "Qin Wu" <bill.wu@huawei.com>; <avt@ietf.org>
> Cc: <megaco@ietf.org>
> Sent: Thursday, December 08, 2011 12:24 AM
> Subject: RE: [AVTCORE] Types of monitoring architectures; RE:
> I-D Action: draft-ietf-avtcore-monarch-08.txt
>
>
> Qin,
> that's NOT the point.
>
> All RFC 3550 and RFC 5117 RTP components are FUNCTIONAL ENTITIES (FE).
> e.g.,
> - the RTP Monitor or RTP receiver FE may be located in
> different PHYSICAL ENTITIES (PE), e.g.
>         a1) a user equipment
>         a2) a RTP-to-PSTN gateway
>         a3) an IP-to-IP session border gateway (in a
> back-to-back RTP endsystem topology)
>         a3) ...
>
> - the RTP Monitor may be associated to an RTP transport translator ...
>         b1) an IP-to-IP session border gateway
>
> The "RTP monitoring architecture" is IMPACTED by each
> functional-to-physical mapping because e.g.
> * QoE related metrics are questionable in case of a2
> ("despite the fact of a RTP receiver function")
> * application level metrics at the location of a RTP
> transport translator are a contradiction in itself
> * ...
>
> Again, it's not really changing the MONARCH draft because in
> the very majority of scenarios it is correct. However, there
> are few cases where the MONARCH description would be "too
> high level", "not fully correct", "lead to possible wrong
> expectations", ...
>
> Regards,
> Albrecht
>
>
>
> > -----Original Message-----
> > From: Qin Wu [mailto:bill.wu@huawei.com]
> > Sent: Dienstag, 6. Dezember 2011 07:13
> > To: Schwarz, Albrecht (Albrecht); avt@ietf.org
> > Cc: megaco@ietf.org
> > Subject: Re: [AVTCORE] Types of monitoring architectures; RE:
> > I-D Action: draft-ietf-avtcore-monarch-08.txt
> >
> > If you talk about existing RFC5117 RTP topology components,
> > this has already been covered by the current version of
> > draft-ietf-avtcore-monarch.
> > In most cases, an RTP system using RTCP XR is architecturally
> > no different from an RTP system which does not use RTCP XR.
> >
> > Regards!
> > -Qin
> > ----- Original Message -----
> > From: "Schwarz, Albrecht (Albrecht)"
> > <albrecht.schwarz@alcatel-lucent.com>
> > To: "Qin Wu" <bill.wu@huawei.com>; <avt@ietf.org>
> > Cc: <megaco@ietf.org>
> > Sent: Monday, December 05, 2011 10:48 PM
> > Subject: RE: [AVTCORE] Types of monitoring architectures; RE:
> > I-D Action: draft-ietf-avtcore-monarch-08.txt
> >
> >
> > Hello Qin,
> >
> > to 1) Physical monitoring architecture
> > Of course consideration of generic physical entities (PE),
> > not specific to any network reference architectures defined
> > by SDOs (like your refered entities).
> > There would be just a few PE types ("given by the limited set
> > of RTP topology components (RFC 5117)").
> >
> > to 2) (RFC 3550) Monitor function
> > Right, that's a functional entity. The applicability of a
> > monitor may be limited, dependent on ... (like in P.NAMS).
> >
> > to 3) your IMS network example
> > Don't see the need to refer from MONARCH to a specific
> > network architecture like IMS.
> > Please also note that IMS is a functional architecture, not a
> > physical architecture.
> >
> > Regards,
> > Albrecht
> >
> > PS
> > There are multiple options for adding the "RTP monitoring
> > architecture" to a functional/physical network architecture:
> > a) integrated approach: extension of existing functional
> > entities or/and addition of RTP monitoring architectural
> > components, extension or/and addition of
> > signalling/management interfaces for control and
> > configuration of RTP monitoring services, and reporting
> > interfaces for measurement data ...
> > b) overlay approach: separate specification to ...
> >
> >
> > PSS
> > BTW: there's a discussion paper with regards to the location
> > of a monitor function in an IMS H.248 gateway entity:
> > Measurements and statistics in IMS - Use Cases
> > http://www.3gpp.org/ftp/tsg_ct/WG3_interworking_ex-CN3/TSGC3_5
> > 8_Kyoto_Japan/Docs/C3-100469.zip
> > This is just fyi.
> >
> >
> >
> > > -----Original Message-----
> > > From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On
> > > Behalf Of Qin Wu
> > > Sent: Freitag, 2. Dezember 2011 02:55
> > > To: Schwarz, Albrecht (Albrecht); avt@ietf.org
> > > Cc: megaco@ietf.org
> > > Subject: Re: [AVTCORE] Types of monitoring architectures; RE:
> > > I-D Action: draft-ietf-avtcore-monarch-08.txt
> > >
> > > Hi, Albrecht:
> > > No offence, I am not really convinced with your proposal on
> > > physical monitoring architecture.
> > >  my counterquestion is what does physical monitoring
> > > architecture looks like in your mind?
> > > How many components do we have in such physical monitroing
> > > architecture? what are they?
> > > Take IMS network architecture as a example, they may have
> > > P-CSCF,S-CSCF, SIP PBX, SBC, why do you believe monitor
> > > described in draft-ietf-avtcore-monarch is mapped into
> > > P-CSCF, S-CSCF, SBC, Media Gateway, Media Gateway Controller
> > > should be in the scope of IETF RTP monitoring archtiecture draft?
> > >
> > > Monitor described in  draft-ietf-avtcore-monarch is well
> > > defined in the section 3 of RFC3550 as follows:
> > > "
> > >
> > >    Monitor: An application that receives RTCP packets sent by
> > >       participants in an RTP session, in particular the reception
> > >       reports, and estimates the current quality of service for
> > >       distribution monitoring, fault diagnosis and long-term
> > > statistics.
> > >       The monitor function is likely to be built into the
> > > application(s)
> > >       participating in the session, but may also be a separate
> > >       application that does not otherwise participate and
> > > does not send
> > >       or receive the RTP data packets (since they are on
> a separate
> > >       port).  These are called third-party monitors.  It is also
> > >       acceptable for a third-party monitor to receive the RTP data
> > >       packets but not send RTCP packets or otherwise be
> > counted in the
> > >       session.
> > >
> > > "
> > > Isn't how to implent monitor into IMS netowork archtiecture a
> > > implentation specific issue?
> > > If this issue are really interesting, isn't it a good idea to
> > > produce another new document to talk about this?
> > > One good example for this motivation is this draft I like to
> > > share with you:
> > > http://tools.ietf.org/html/draft-kaplan-dispatch-b2bua-taxonom
> > > y-00#section-4.6
> > >
> > > Regards!
> > > -Qin
> > > ----- Original Message -----
> > > From: "Schwarz, Albrecht (Albrecht)"
> > > <albrecht.schwarz@alcatel-lucent.com>
> > > To: "Qin Wu" <bill.wu@huawei.com>; <avt@ietf.org>
> > > Cc: <megaco@ietf.org>
> > > Sent: Friday, December 02, 2011 12:20 AM
> > > Subject: RE: [AVTCORE] Types of monitoring architectures; RE:
> > > I-D Action: draft-ietf-avtcore-monarch-08.txt
> > >
> > >
> > > My replies below ...
> > > -Albrecht
> > >
> > > > -----Original Message-----
> > > > From: Qin Wu [mailto:bill.wu@huawei.com]
> > > > Sent: Donnerstag, 1. Dezember 2011 02:42
> > > > To: Schwarz, Albrecht (Albrecht); avt@ietf.org
> > > > Cc: megaco@ietf.org
> > > > Subject: Re: [AVTCORE] Types of monitoring architectures; RE:
> > > > I-D Action: draft-ietf-avtcore-monarch-08.txt
> > > >
> > > > Hi,
> > > > ----- Original Message -----
> > > > From: "Schwarz, Albrecht (Albrecht)"
> > > > <albrecht.schwarz@alcatel-lucent.com>
> > > > To: "Qin Wu" <bill.wu@huawei.com>; <avt@ietf.org>
> > > > Cc: <megaco@ietf.org>
> > > > Sent: Thursday, December 01, 2011 1:24 AM
> > > > Subject: RE: [AVTCORE] Types of monitoring architectures; RE:
> > > > I-D Action: draft-ietf-avtcore-monarch-08.txt
> > > >
> > > >
> > > > My replies below inline,
> > > > Albrecht
> > > >
> > > > > -----Original Message-----
> > > > > From: Qin Wu [mailto:bill.wu@huawei.com]
> > > > > Sent: Mittwoch, 30. November 2011 04:51
> > > > > To: Schwarz, Albrecht (Albrecht); avt@ietf.org
> > > > > Cc: megaco@ietf.org
> > > > > Subject: Re: [AVTCORE] Types of monitoring architectures; RE:
> > > > > I-D Action: draft-ietf-avtcore-monarch-08.txt
> > > > >
> > > > > Hi,
> > > > > ----- Original Message -----
> > > > > From: "Schwarz, Albrecht (Albrecht)"
> > > > > <albrecht.schwarz@alcatel-lucent.com>
> > > > > To: <avt@ietf.org>
> > > > > Cc: <megaco@ietf.org>
> > > > > Sent: Tuesday, November 29, 2011 7:32 PM
> > > > > Subject: [AVTCORE] Types of monitoring architectures; RE: I-D
> > > > > Action: draft-ietf-avtcore-monarch-08.txt
> > > > >
> > > > >
> > > > > > Dear All,
> > > > > >
> > > > > > there are different types of monitoring architectures,
> > > > > particularily from perspective of QoE related performance
> > > > parameters.
> > > > > > Let's recall QoE (e.g., ITU-T P.10 Amendment 2):
> > > > > >
> > > > > > Quality of Experience (QoE):
> > > > > > The overall acceptability of an application or service, as
> > > > > perceived subjectively by the end-user.
> > > > > > NOTE 1 - Quality of experience includes the complete
> > > > > end-to-end system effects (client, terminal, network,
> > > > > services infrastructure, etc.).
> > > > > > NOTE 2 - Overall acceptability may be influenced by user
> > > > > expectations and context.
> > > > > >
> > > > > > Important for MONARCH:
> > > > > > 1st ... perceived by end-user
> > > > > > 2nd QoE includes the complete end-to-end sytem effects ...
> > > > > >
> > > > > > That said, present RTP monitoring architecture in MONARCH
> > > > > according clause 3 is not specific on the type of monitoring
> > > > > architecture. For instance, Fig. 1, it is possibly supposed
> > > > > that the "RTP Sender" and "RTP Receiver" entities are equal
> > > > > to a terminal/user equipment (UE). This would be an
> > > > > end-to-end IP network scenario.
> > > > > >
> > > > > > However, the "RTP Sender" and "RTP Receiver" entities may
> > > > > be also located at the edge of an IP network, e.g. in a
> > > > > gateway for IP-to-non-IP interworking, i.e. an UE located in
> > > > > the non-IP network part.
> > > > > > Note: such scenarios are considered by MEGACO gateways
> > > > > (I've Cc'd megaco list).
> > > > > >
> > > > > > An RTP Sender/Receiver located NOT in the UE would question
> > > > > the value of RTP/RTCP QoE related performance measurements
> > > > > (because the UE is located outside the RTP domain).
> > > > > >
> > > > > > Conclusions:
> > > > > > - the set of meaningful performance metrics may be
> > > > > dependent on the location of the RTP Sender/Receiver, e.g.
> > > > > whether in a UE, gateway, ...
> > > > > > - don't see any impact on transport level metrics
> > > > > > - ... but the set of meaningful application level metrics
> > > > > >
> > > > > > Proposal for MONARCH:
> > > > > > #1: insert sub-clause title "3.1 End-to-end IP network
> > > > > architecture" below clause 3
> > > > > >
> > > > > > #2: add a sub-clause 3.2 at the end of clause 3, sth like
> > > > > >
> > > > > > "3.2 RTP Sender/Receiver entities located in network nodes
> > > > > > The location of the RTP Sender/Receiver entity may impact
> > > > > the set of meaningful metrics.
> > > > > > For instance: application level metrics for QoE related
> > > > > performance metrics are questionable (or doesn't really make
> > > > > sense at all) when measured in a network node (terminating
> > > > > the RTP) instead of the user equipment."
> > > > > >
> > > > > > Something like this would help to avoid confusion.
> > > > > > I even believe that a QoE measurement in a network node
> > > > > would violate the QoE definition. Would be rather something
> > > > > like QoE* ("remote QoE"):-(
> > > > > >
> > > > > > Such information would improve the MONARCH doc in
> my opinion.
> > > > > > Sorry for that late comment.
> > > > > > Any views?
> > > > >
> > > > > [Qin]:
> > > > > Albrrecht, if you follow ealry list discussion on
> > > > > draft-hunt-avt-monarch-01, you will see the rough consensus
> > > > > to position this document was
> > > > > this daft should focus on guidelines for defining reporting
> > > > > blocks. That is to say the main purpose of MONARCH draft
> > > is how to
> > > > > provide guidelines for the development of new RTCP XR block
> > > > > types in XRBlock working group.
> > > >
> > > > [ABS] ... then the title "monitoring architectures" is
> misleading.
> > > > Proposal: keep title, revise scope section on focus
> > > >
> > > > [Qin]: No, the title is *RTP* monitoring architecture, we can
> > > > not expand scope into IP monitoring architecture.
> > >
> > > [ABS] That's wasn't the intent! Did just focus on the key word.
> > >
> > > >
> > > > >
> > > > > Therefore how and where to collect the metric from RTP
> > > > > endpoint is not scope of this document, in my opinion. since
> > > > > you may have many ways to do this and different vendors have
> > > > > their different appoaches. It will be better to leave this
> > > > > beyond the scope. But you are right, it will be more
> > > > > reasonable to measure QoE related performance metric at the
> > > > > RTP receiver.
> > > >
> > > > [ABS] I would disagree. At least your statement should be
> > > > conditional, sth like
> > > > "QoE related performance metrics may be measured in a RTP
> > > > receiver, IF the RTP receiver function is located in user
> > > > equipment (e.g. IP terminal), because QoE performance metrics
> > > > are tightly coupled to the point of view of a 'user'.
> > > > ... IF NOT, then ..."
> > > >
> > > > [Qin]: I am not sure user equipment or IP terminal is the
> > > > right term from RTP perspective.
> > > >
> > > > Also if you read P.NAMS, P.NAMS model for calculating QoE
> > > > related metric can be placed either at the network or at
> > the client.
> > > > So I disagree with what you said.
> > >
> > > [ABS] Not convinced at all.
> > > Guess you are referring to the "mid-point" models, right?
> > > The usage of such that models depends on "prior knowledge
> > > ..." information.
> > > Thus, the applicability is conditional. You may not make such
> > > a general statement.
> > >
> > >
> > > >
> > > > Also as I said, how and where to collect the metric from RTP
> > > >  endpoint is not scope of this document. It depends on the
> > > > model you are choosing, e.g., four operation modes specified
> > > > in P.NAMS.
> > > > Apparently this should not be specified again in RTP
> > > > monitoring architecture document.
> > > >
> > > > >
> > > > > Another point is it is not clear to me how RTP monitoring has
> > > > > to do with architectureend to end IP network architecture .
> > > > > this draft mostly focus on discussing RTP level stuff.
> > > > > Therefore I am quite doubt that we should describe anything
> > > > > in this document like how
> > > > > RTP entties is mapped into network entities/nodes at
> > the IP layer.
> > > >
> > > > [ABS] I don't got any problems to talk about architectural
> > > > framework for monitoring in this document. Such information
> > > > is required and this is the only IETF AVT doc about it.
> > > > The solution to this issue is rather simple to me:
> > > > - split the MONARCH "monitoring architecture" in
> > > > 1) a functional monitoring architecture (let's call it
> 'FMA') and
> > > > 2) a physical monitoring architecture (... 'PMA').
> > > >
> > > > - the present MONARCH doc would describe the FMA at the level
> > > > of RTP entities (i.e., Fig. 1 entities, incl. all the RTP
> > > > topology components according RFC 5117)
> > > >
> > > > - there are many options of functional-to-physical mappings,
> > > > i.e. how a FMA would be mapped on a PMA
> > > > - the mapping is typically dependent on considered network
> > > > architecture (like SIP, H.323, MGCP, IMS, wireless, etc
> networks)
> > > >
> > > > - the present MONARCH doc would describe the FMA-to-PMA
> > > > mapping IF all RTP receiver/sender entities would be located
> > > > in physical IP terminals (UEs)
> > > > - etc
> > > >
> > > > [Qin]: I can understand your point, but you can not do that.
> > > > Since this document is only focus on *RTP* monitoring
> > > > architecture, that is what it said in AVTCore milestone:
> > > > "
> > > >
> > > > Goals and Milestones:
> > > >
> > > >   Feb 2011 - Submit Monitoring Architecture for RTP for
> > > Informational
> > > >
> > > > "
> > >
> > > [ABS] If you go back to my first email on this subject, and
> > > if you look at my proposal: that's not a lot, nothing which
> > > violates the charter, goals and milestones.
> > >
> > >
> > > > Also if you really don't see how to map FMA to PMA, you may
> > > > look at the P.NAMS models specifed in ITU-T P.NAMS.
> > > > As for how to use RTP monitoring architecture or RTP XR
> > > > Report in the IMS network architecture, you may look at:
> > > > http://tools.ietf.org/html/rfc6035
> > >
> > > [ABS] That's the SIP reporting interface, i.e., applicable
> > > primarily for physical IP user equipment with embedded RTP
> > > sender/receiver function and SIP UA function.
> > > However, the applicability of RFC 6035 is limited for a
> > > SIP-to-PSTN gateway (because the RTP sender/receiver would be
> > > located NOT in user equipment. Also the P.NAMS mid-point
> > > model fails for such a scenario.
> > >
> > > > ITU-T H.248.48.
> > > > But I haven't check the current status of H.248.48.
> > >
> > > [ABS] Work is finalized, see
> > > http://www.itu.int/md/meetingdoc.asp?lang=en&parent=T09-SG16-1
> > > 11121-TD-PLEN-0419
> > >
> > > >
> > > > >
> > > > > But as the author of this document, I am interested and open
> > > > > to other opinions.:-)
> > > >
> > > > [ABS] Like to add a further aspect: a "functional monitoring
> > > > architecture" may be considered as a network overlay,
> > > > something which adds additional capabilities (here:
> > > > measurement services, reporting services on top of basic RTP
> > > > services).
> > > > Such an overlay concept is nothing new: e.g., the
> > > > MultiService Forum did define a "Performance Measurement &
> > > > Monitoring (PMM)" overlay network, or IETF RMON may be also
> > > > considered as such.
> > > >
> > > > >
> > > > > > Regards,
> > > > > > Albrecht
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > >> -----Original Message-----
> > > > > >> From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On
> > > > > >> Behalf Of internet-drafts@ietf.org
> > > > > >> Sent: Dienstag, 29. November 2011 08:56
> > > > > >> To: i-d-announce@ietf.org
> > > > > >> Cc: avt@ietf.org
> > > > > >> Subject: [AVTCORE] I-D Action:
> > > draft-ietf-avtcore-monarch-08.txt
> > > > > >>
> > > > > >>
> > > > > >> A New Internet-Draft is available from the on-line
> > > > > >> Internet-Drafts directories. This draft is a work
> item of the
> > > > > >> Audio/Video Transport Core Maintenance Working Group
> > > of the IETF.
> > > > > >>
> > > > > >> Title           : Monitoring Architectures for RTP
> > > > > >> Author(s)       : Qin Wu
> > > > > >>                           Geoff Hunt
> > > > > >>                           Philip Arden
> > > > > >> Filename        : draft-ietf-avtcore-monarch-08.txt
> > > > > >> Pages           : 25
> > > > > >> Date            : 2011-11-28
> > > > > >>
> > > > > >>    This memo proposes an architecture for
> extending RTCP with
> > > > > >> a new RTCP
> > > > > >>    XR (RFC3611) block type to report new metrics
> > > regarding media
> > > > > >>    transmission or reception quality, following RTCP
> > guideline
> > > > > >>    established in RFC5968.  This memo suggests that a new
> > > > > block should
> > > > > >>    contain a single metric or a small number of metrics
> > > > > relevant to a
> > > > > >>    single parameter of interest or concern, rather than
> > > > > containing a
> > > > > >>    number of metrics which attempt to provide full coverage
> > > > > >> of all those
> > > > > >>    parameters of concern to a specific application.
> > > > > Applications may
> > > > > >>    then "mix and match" to create a set of blocks which
> > > > > >> covers their set
> > > > > >>    of concerns.  Where possible, a specific block should be
> > > > > >> designed to
> > > > > >>    be re-usable across more than one application, for
> > > > > example, for all
> > > > > >>    of voice, streaming audio and video.
> > > > > >>
> > > > > >>
> > > > > >> A URL for this Internet-Draft is:
> > > > > >>
> > > > >
> > > >
> > >
> >
> http://www.ietf.org/internet-drafts/draft-ietf-avtcore-monarch-08.txt
> > > > > >>
> > > > > >> Internet-Drafts are also available by anonymous FTP at:
> > > > > >> ftp://ftp.ietf.org/internet-drafts/
> > > > > >>
> > > > > >> This Internet-Draft can be retrieved at:
> > > > > >>
> > > > >
> > >
> ftp://ftp.ietf.org/internet-drafts/draft-ietf-avtcore-monarch-08.txt
> > > > > >>
> > > > > >> _______________________________________________
> > > > > >> Audio/Video Transport Core Maintenance
> > > > > >> avt@ietf.org
> > > > > >> https://www.ietf.org/mailman/listinfo/avt
> > > > > >>
> > > > > > _______________________________________________
> > > > > > Audio/Video Transport Core Maintenance
> > > > > > avt@ietf.org
> > > > > > https://www.ietf.org/mailman/listinfo/avt
> > > > >
> > > > =
> > > _______________________________________________
> > > Audio/Video Transport Core Maintenance
> > > avt@ietf.org
> > > https://www.ietf.org/mailman/listinfo/avt
> > >
> >
>

From Raphael.Tryster@Teledata-Networks.com  Sun Dec 11 21:54:02 2011
Return-Path: <Raphael.Tryster@Teledata-Networks.com>
X-Original-To: megaco@ietfa.amsl.com
Delivered-To: megaco@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 677E521F85F2 for <megaco@ietfa.amsl.com>; Sun, 11 Dec 2011 21:54:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.114
X-Spam-Level: 
X-Spam-Status: No, score=0.114 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_MISMATCH_COM=0.553, MIME_QP_LONG_LINE=1.396, SARE_RECV_BEZEQINT_B=0.763, UNPARSEABLE_RELAY=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Hku3InZqPJwM for <megaco@ietfa.amsl.com>; Sun, 11 Dec 2011 21:54:01 -0800 (PST)
Received: from teledata-networks.com (mail.teledata-networks.COM [81.218.12.242]) by ietfa.amsl.com (Postfix) with ESMTP id EBAFE21F8494 for <megaco@ietf.org>; Sun, 11 Dec 2011 21:53:59 -0800 (PST)
Received: from Internal Mail-Server by Mail-SeCure (envelope-from Raphael.Tryster@Teledata-Networks.com) with SMTP; 12 Dec 2011 07:39:27 +0000
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Mon, 12 Dec 2011 07:54:03 +0200
Message-ID: <D6FAAE89E48C5B488B41BEBBDCD746CD07AB2D41@tndcmail.Teledata.Local>
In-Reply-To: <4EE533ED.8030006@nteczone.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Megaco] OutOfService vs Inactive
Thread-Index: Acy4V3/FIcRUDQF2RB6Gvb+DZ6zXqwAOtTQg
References: <4EE3543D.8000301@trajano.us.es> <4EE533ED.8030006@nteczone.com>
From: "Raphael Tryster" <Raphael.Tryster@Teledata-Networks.com>
To: "Christian Groves" <Christian.Groves@nteczone.com>, <megaco@ietf.org>
Subject: Re: [Megaco] OutOfService vs Inactive
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.1.12
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: Mon, 12 Dec 2011 05:54:02 -0000

"the MGC can't change OutOfService to InService"

But some MGCs sure as hell try.

-----Original Message-----
From: megaco-bounces@ietf.org [mailto:megaco-bounces@ietf.org] On Behalf
Of Christian Groves
Sent: Monday, 12 December 2011 12:51 AM
To: megaco@ietf.org
Subject: Re: [Megaco] OutOfService vs Inactive

Hello Javi,

ServiceState and Streammode are fundamentally different things.=20
Streammode is related to activity on the bearer. ServiceState is related

to MG internal "readiness". Also the Streammode can be controlled by the

MGC. i.e. it can change Inactive to Send/Receive.
ServiceState is largely controlled by the MG. i.e. the MGC can't change=20
OutOfService to InService.

Regards, Christian

On 10/12/2011 11:44 PM, Javi wrote:
> In a termination *with**a single stream*, which is the
differencebetween?:
>
> (a) TerminationState{ServiceStates=3DOutOfService}
>
> (b) Media{ LocalControl { StreamMode=3DInactive } }
>
> Regards,
>
> Javi
>
>
> _______________________________________________
> Megaco mailing list
> Megaco@ietf.org
> https://www.ietf.org/mailman/listinfo/megaco
_______________________________________________
Megaco mailing list
Megaco@ietf.org
https://www.ietf.org/mailman/listinfo/megaco

NOTICE: This email and any files transmitted with it are Enablence and Teledata-Networks confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the sender. This message contains Enablence and Teledata-Networks confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. If you are not the intended recipient you are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited.



From albrecht.schwarz@alcatel-lucent.com  Mon Dec 12 02:33:27 2011
Return-Path: <albrecht.schwarz@alcatel-lucent.com>
X-Original-To: megaco@ietfa.amsl.com
Delivered-To: megaco@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 438D321F8A62; Mon, 12 Dec 2011 02:33:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.364
X-Spam-Level: 
X-Spam-Status: No, score=-5.364 tagged_above=-999 required=5 tests=[AWL=-0.315, BAYES_00=-2.599, HELO_EQ_FR=0.35, J_CHICKENPOX_14=0.6, J_CHICKENPOX_74=0.6, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id q72NSNBJa6Uv; Mon, 12 Dec 2011 02:33:25 -0800 (PST)
Received: from smail2.alcatel.fr (smail2.alcatel.fr [64.208.49.57]) by ietfa.amsl.com (Postfix) with ESMTP id 6862921F8888; Mon, 12 Dec 2011 02:33:24 -0800 (PST)
Received: from FRMRSSXCHHUB03.dc-m.alcatel-lucent.com (FRMRSSXCHHUB03.dc-m.alcatel-lucent.com [135.120.45.63]) by smail2.alcatel.fr (8.14.3/8.14.3/ICT) with ESMTP id pBCAX3Om022291 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Mon, 12 Dec 2011 11:33:15 +0100
Received: from FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com ([135.120.45.50]) by FRMRSSXCHHUB03.dc-m.alcatel-lucent.com ([135.120.45.63]) with mapi; Mon, 12 Dec 2011 11:33:09 +0100
From: "Schwarz, Albrecht (Albrecht)" <albrecht.schwarz@alcatel-lucent.com>
To: Qin Wu <bill.wu@huawei.com>, "avt@ietf.org" <avt@ietf.org>
Date: Mon, 12 Dec 2011 11:33:08 +0100
Thread-Topic: [AVTCORE] Types of monitoring architectures; RE:  I-D Action: draft-ietf-avtcore-monarch-08.txt
Thread-Index: Acy4g3DuLm8Zu4LZQuq8wu6FtEozXgAM063A
Message-ID: <5F7BCCF5541B7444830A2288ABBEBC9621620F5330@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com>
References: <20111129075613.12419.4377.idtracker@ietfa.amsl.com> <5F7BCCF5541B7444830A2288ABBEBC96216190051A@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com> <EAC481B4D8034C38AC54E1217F8D875D@china.huawei.com> <5F7BCCF5541B7444830A2288ABBEBC96216190077F@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com> <B527BAFA038842A8939A8C2D558074CD@china.huawei.com> <5F7BCCF5541B7444830A2288ABBEBC962161900908@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com> <9FF9B04A84E64AD7ABCCC4F2ACC1E19A@china.huawei.com> <5F7BCCF5541B7444830A2288ABBEBC9621620F4AF5@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com> <D44A4820E0D24DD79F6F5A4B7507D0D6@china.huawei.com> <5F7BCCF5541B7444830A2288ABBEBC9621620F4ED2@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com> <71112008FBA94D35B07FA6B4916075B6@china.huawei.com> <5F7BCCF5541B7444830A2288ABBEBC9621620F5258@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com> <6C618D1EA52146A781429C6B08C4A4FC@china.huawei.com>
In-Reply-To: <6C618D1EA52146A781429C6B08C4A4FC@china.huawei.com>
Accept-Language: de-DE, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: de-DE, en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.69 on 155.132.188.80
Cc: "megaco@ietf.org" <megaco@ietf.org>
Subject: Re: [Megaco] [AVTCORE] Types of monitoring architectures; RE:  I-D Action: draft-ietf-avtcore-monarch-08.txt
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.1.12
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: Mon, 12 Dec 2011 10:33:27 -0000

Hi Qin,

I'm very aware about all that.
It looks like that you are now agreeing that QoE measurements are CONDITION=
AL ("you got a number of IF statements, there might be even more ...").

MONARCH is not talking about such conditions, thus some readers may got the=
 impression that the metrics related to RTP traffic are UNCONDITIONAL (whic=
h is not true as you confirmed).

If you go back to my very first email: I did just propose to indicate the c=
onditional aspect. Don't understand why such kind of valuable info would be=
 not in scope of MONARCH. Hm?

Regards,
Albrecht

PS
I did use the notion of a control plane agnostic "RTP-to-PSTN gateway". You=
 did indicate control plane specific gateway types like SIP-to-PSTN or SIP-=
to-H.323. Now issue to use such signalling protocol specific examples, but =
it doesn't change the underlying issue.
The SIP side reporting capability based on RFC 6035 allows to report the ou=
tlined measurements, but the RFC itself does not specify whether the report=
ed information is meaningful (which is OK because this is not subject of a =
reporting interface spec, it is rather subject of a network monitoring doc =
like MONARCH).
QoE measurements would be conditional in both gateway types (because such a=
 gateway is NOT a user device despite the fact of an embedded SIP user agen=
t entity).
Actually I would even question here the condition of "customer knows the or=
iginal content" in many real network scenarios.



> -----Original Message-----
> From: Qin Wu [mailto:bill.wu@huawei.com]
> Sent: Montag, 12. Dezember 2011 05:05
> To: Schwarz, Albrecht (Albrecht); avt@ietf.org
> Cc: megaco@ietf.org
> Subject: Re: [AVTCORE] Types of monitoring architectures; RE:
> I-D Action: draft-ietf-avtcore-monarch-08.txt
>
> Hi, Albrecht:
> My understanding to QoE measurment is:
> The factors that influence the QoE metric include encoding
> system, transport network, access network,home network and end device.
> If the customer(e.g., network operator) doesn't know the
> original content, the QoE metric should be usually measured
> at the user device.
> If the customer knows the original content, the QoE metric
> can be measured either in the network or at the user device.
> Given the growing popularity of connected devices, these
> devices may have different capability corresponding to CPU
> load, processing overhead, storage, batteries.
> If the cusomer want to measure QoE without considering
> connected devices with various capability , the QoE metric
> can be measured at the point between access network and home network.
>
> Regarding the monitoring scenario you mentioned, I am not
> familiar with such scenario with RTP-to-PSTN gateway deployed.
> But I am aware that there are scenarios with SIP to PSTN
> gateway or SIP to H.323 gateway widely deployed,  RFC6035
> defines a new SIP event package, vq-rtcpxr that enable the
> collection and  reporting of metrics that measure quality for
> RTP sessions. In such cases, RTCP XR VOIP metric with QoE
> metric included is measured at the user device and mapped
> into the equivalent SIP vq-rtcpxr parameter since SIP session
> call is established end to end and RTP media stream is
> exchanged directly between one endpoint and the other endpoint.
>
> Regards!
> -Qin
> ----- Original Message -----
> From: "Schwarz, Albrecht (Albrecht)"
> <albrecht.schwarz@alcatel-lucent.com>
> To: "Qin Wu" <bill.wu@huawei.com>; <avt@ietf.org>
> Cc: <megaco@ietf.org>
> Sent: Saturday, December 10, 2011 12:01 AM
> Subject: RE: [AVTCORE] Types of monitoring architectures; RE:
> I-D Action: draft-ietf-avtcore-monarch-08.txt
>
>
> How do you explain to a network operator the value of QoE
> measurements by an RTP receiver / RTP monitor component
> located in an RTP-to-PSTN gateway?
>
> This would be a monitoring scenario inline with MONARCH, but
> with valueless QoE results, right?
>
>
> > -----Original Message-----
> > From: Qin Wu [mailto:bill.wu@huawei.com]
> > Sent: Donnerstag, 8. Dezember 2011 03:26
> > To: Schwarz, Albrecht (Albrecht); avt@ietf.org
> > Cc: megaco@ietf.org
> > Subject: Re: [AVTCORE] Types of monitoring architectures; RE:
> > I-D Action: draft-ietf-avtcore-monarch-08.txt
> >
> > You reiterate what you propose for physical entities in the
> > early email.
> > I am still not convicing with that.
> >
> > Since we have RTP components like RTP end system, RTP mixer,
> > RTP media translator, RTP transport translator, RTP monitor
> > specified in RFC3550 can be built into these component as a
> > application. also monitor can be disjointed from these RTP
> > components as a third party monitor. why we need to specify
> > how to map RTP end system into user equipment, RTP translator
> > or RTP mixer can be mapped into RTP-PSTN gateway, or IP to IP
> > border gateway since we have already mapped monitor into
> > different RTP components.
> > How many PE types you can enumerate? why they should be scope
> > of RTP monitoring architecture?
> >
> > Also as specified in MONARCH draft, we have end sytem
> > metrics, transport level metric, transport level metric, they
> > can be measured and collected from the different RTP
> > comoponents specified in RFC3550, RFC5117. Apparently end
> > system metric can only be collected from RTP end system.
> > transport metric is collected from any RTP system in the RTP
> > monitoring architecture, regarding application level metric,
> > apparently they should be measured at the application layer
> > and can not be collected from RTP transport translator, Also
> > RTP transport translator is still a functional entity rather
> > than a physical entity. I am not convincing with what you
> > said about "contradiction", "lead to possible wrong expectations".
> >
> > Regards!
> > -Qin
> > ----- Original Message -----
> > From: "Schwarz, Albrecht (Albrecht)"
> > <albrecht.schwarz@alcatel-lucent.com>
> > To: "Qin Wu" <bill.wu@huawei.com>; <avt@ietf.org>
> > Cc: <megaco@ietf.org>
> > Sent: Thursday, December 08, 2011 12:24 AM
> > Subject: RE: [AVTCORE] Types of monitoring architectures; RE:
> > I-D Action: draft-ietf-avtcore-monarch-08.txt
> >
> >
> > Qin,
> > that's NOT the point.
> >
> > All RFC 3550 and RFC 5117 RTP components are FUNCTIONAL
> ENTITIES (FE).
> > e.g.,
> > - the RTP Monitor or RTP receiver FE may be located in
> > different PHYSICAL ENTITIES (PE), e.g.
> >         a1) a user equipment
> >         a2) a RTP-to-PSTN gateway
> >         a3) an IP-to-IP session border gateway (in a
> > back-to-back RTP endsystem topology)
> >         a3) ...
> >
> > - the RTP Monitor may be associated to an RTP transport
> translator ...
> >         b1) an IP-to-IP session border gateway
> >
> > The "RTP monitoring architecture" is IMPACTED by each
> > functional-to-physical mapping because e.g.
> > * QoE related metrics are questionable in case of a2
> > ("despite the fact of a RTP receiver function")
> > * application level metrics at the location of a RTP
> > transport translator are a contradiction in itself
> > * ...
> >
> > Again, it's not really changing the MONARCH draft because in
> > the very majority of scenarios it is correct. However, there
> > are few cases where the MONARCH description would be "too
> > high level", "not fully correct", "lead to possible wrong
> > expectations", ...
> >
> > Regards,
> > Albrecht
> >
> >
> >
> > > -----Original Message-----
> > > From: Qin Wu [mailto:bill.wu@huawei.com]
> > > Sent: Dienstag, 6. Dezember 2011 07:13
> > > To: Schwarz, Albrecht (Albrecht); avt@ietf.org
> > > Cc: megaco@ietf.org
> > > Subject: Re: [AVTCORE] Types of monitoring architectures; RE:
> > > I-D Action: draft-ietf-avtcore-monarch-08.txt
> > >
> > > If you talk about existing RFC5117 RTP topology components,
> > > this has already been covered by the current version of
> > > draft-ietf-avtcore-monarch.
> > > In most cases, an RTP system using RTCP XR is architecturally
> > > no different from an RTP system which does not use RTCP XR.
> > >
> > > Regards!
> > > -Qin
> > > ----- Original Message -----
> > > From: "Schwarz, Albrecht (Albrecht)"
> > > <albrecht.schwarz@alcatel-lucent.com>
> > > To: "Qin Wu" <bill.wu@huawei.com>; <avt@ietf.org>
> > > Cc: <megaco@ietf.org>
> > > Sent: Monday, December 05, 2011 10:48 PM
> > > Subject: RE: [AVTCORE] Types of monitoring architectures; RE:
> > > I-D Action: draft-ietf-avtcore-monarch-08.txt
> > >
> > >
> > > Hello Qin,
> > >
> > > to 1) Physical monitoring architecture
> > > Of course consideration of generic physical entities (PE),
> > > not specific to any network reference architectures defined
> > > by SDOs (like your refered entities).
> > > There would be just a few PE types ("given by the limited set
> > > of RTP topology components (RFC 5117)").
> > >
> > > to 2) (RFC 3550) Monitor function
> > > Right, that's a functional entity. The applicability of a
> > > monitor may be limited, dependent on ... (like in P.NAMS).
> > >
> > > to 3) your IMS network example
> > > Don't see the need to refer from MONARCH to a specific
> > > network architecture like IMS.
> > > Please also note that IMS is a functional architecture, not a
> > > physical architecture.
> > >
> > > Regards,
> > > Albrecht
> > >
> > > PS
> > > There are multiple options for adding the "RTP monitoring
> > > architecture" to a functional/physical network architecture:
> > > a) integrated approach: extension of existing functional
> > > entities or/and addition of RTP monitoring architectural
> > > components, extension or/and addition of
> > > signalling/management interfaces for control and
> > > configuration of RTP monitoring services, and reporting
> > > interfaces for measurement data ...
> > > b) overlay approach: separate specification to ...
> > >
> > >
> > > PSS
> > > BTW: there's a discussion paper with regards to the location
> > > of a monitor function in an IMS H.248 gateway entity:
> > > Measurements and statistics in IMS - Use Cases
> > > http://www.3gpp.org/ftp/tsg_ct/WG3_interworking_ex-CN3/TSGC3_5
> > > 8_Kyoto_Japan/Docs/C3-100469.zip
> > > This is just fyi.
> > >
> > >
> > >
> > > > -----Original Message-----
> > > > From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On
> > > > Behalf Of Qin Wu
> > > > Sent: Freitag, 2. Dezember 2011 02:55
> > > > To: Schwarz, Albrecht (Albrecht); avt@ietf.org
> > > > Cc: megaco@ietf.org
> > > > Subject: Re: [AVTCORE] Types of monitoring architectures; RE:
> > > > I-D Action: draft-ietf-avtcore-monarch-08.txt
> > > >
> > > > Hi, Albrecht:
> > > > No offence, I am not really convinced with your proposal on
> > > > physical monitoring architecture.
> > > >  my counterquestion is what does physical monitoring
> > > > architecture looks like in your mind?
> > > > How many components do we have in such physical monitroing
> > > > architecture? what are they?
> > > > Take IMS network architecture as a example, they may have
> > > > P-CSCF,S-CSCF, SIP PBX, SBC, why do you believe monitor
> > > > described in draft-ietf-avtcore-monarch is mapped into
> > > > P-CSCF, S-CSCF, SBC, Media Gateway, Media Gateway Controller
> > > > should be in the scope of IETF RTP monitoring
> archtiecture draft?
> > > >
> > > > Monitor described in  draft-ietf-avtcore-monarch is well
> > > > defined in the section 3 of RFC3550 as follows:
> > > > "
> > > >
> > > >    Monitor: An application that receives RTCP packets sent by
> > > >       participants in an RTP session, in particular the
> reception
> > > >       reports, and estimates the current quality of service for
> > > >       distribution monitoring, fault diagnosis and long-term
> > > > statistics.
> > > >       The monitor function is likely to be built into the
> > > > application(s)
> > > >       participating in the session, but may also be a separate
> > > >       application that does not otherwise participate and
> > > > does not send
> > > >       or receive the RTP data packets (since they are on
> > a separate
> > > >       port).  These are called third-party monitors.  It is also
> > > >       acceptable for a third-party monitor to receive
> the RTP data
> > > >       packets but not send RTCP packets or otherwise be
> > > counted in the
> > > >       session.
> > > >
> > > > "
> > > > Isn't how to implent monitor into IMS netowork archtiecture a
> > > > implentation specific issue?
> > > > If this issue are really interesting, isn't it a good idea to
> > > > produce another new document to talk about this?
> > > > One good example for this motivation is this draft I like to
> > > > share with you:
> > > > http://tools.ietf.org/html/draft-kaplan-dispatch-b2bua-taxonom
> > > > y-00#section-4.6
> > > >
> > > > Regards!
> > > > -Qin
> > > > ----- Original Message -----
> > > > From: "Schwarz, Albrecht (Albrecht)"
> > > > <albrecht.schwarz@alcatel-lucent.com>
> > > > To: "Qin Wu" <bill.wu@huawei.com>; <avt@ietf.org>
> > > > Cc: <megaco@ietf.org>
> > > > Sent: Friday, December 02, 2011 12:20 AM
> > > > Subject: RE: [AVTCORE] Types of monitoring architectures; RE:
> > > > I-D Action: draft-ietf-avtcore-monarch-08.txt
> > > >
> > > >
> > > > My replies below ...
> > > > -Albrecht
> > > >
> > > > > -----Original Message-----
> > > > > From: Qin Wu [mailto:bill.wu@huawei.com]
> > > > > Sent: Donnerstag, 1. Dezember 2011 02:42
> > > > > To: Schwarz, Albrecht (Albrecht); avt@ietf.org
> > > > > Cc: megaco@ietf.org
> > > > > Subject: Re: [AVTCORE] Types of monitoring architectures; RE:
> > > > > I-D Action: draft-ietf-avtcore-monarch-08.txt
> > > > >
> > > > > Hi,
> > > > > ----- Original Message -----
> > > > > From: "Schwarz, Albrecht (Albrecht)"
> > > > > <albrecht.schwarz@alcatel-lucent.com>
> > > > > To: "Qin Wu" <bill.wu@huawei.com>; <avt@ietf.org>
> > > > > Cc: <megaco@ietf.org>
> > > > > Sent: Thursday, December 01, 2011 1:24 AM
> > > > > Subject: RE: [AVTCORE] Types of monitoring architectures; RE:
> > > > > I-D Action: draft-ietf-avtcore-monarch-08.txt
> > > > >
> > > > >
> > > > > My replies below inline,
> > > > > Albrecht
> > > > >
> > > > > > -----Original Message-----
> > > > > > From: Qin Wu [mailto:bill.wu@huawei.com]
> > > > > > Sent: Mittwoch, 30. November 2011 04:51
> > > > > > To: Schwarz, Albrecht (Albrecht); avt@ietf.org
> > > > > > Cc: megaco@ietf.org
> > > > > > Subject: Re: [AVTCORE] Types of monitoring
> architectures; RE:
> > > > > > I-D Action: draft-ietf-avtcore-monarch-08.txt
> > > > > >
> > > > > > Hi,
> > > > > > ----- Original Message -----
> > > > > > From: "Schwarz, Albrecht (Albrecht)"
> > > > > > <albrecht.schwarz@alcatel-lucent.com>
> > > > > > To: <avt@ietf.org>
> > > > > > Cc: <megaco@ietf.org>
> > > > > > Sent: Tuesday, November 29, 2011 7:32 PM
> > > > > > Subject: [AVTCORE] Types of monitoring
> architectures; RE: I-D
> > > > > > Action: draft-ietf-avtcore-monarch-08.txt
> > > > > >
> > > > > >
> > > > > > > Dear All,
> > > > > > >
> > > > > > > there are different types of monitoring architectures,
> > > > > > particularily from perspective of QoE related performance
> > > > > parameters.
> > > > > > > Let's recall QoE (e.g., ITU-T P.10 Amendment 2):
> > > > > > >
> > > > > > > Quality of Experience (QoE):
> > > > > > > The overall acceptability of an application or service, as
> > > > > > perceived subjectively by the end-user.
> > > > > > > NOTE 1 - Quality of experience includes the complete
> > > > > > end-to-end system effects (client, terminal, network,
> > > > > > services infrastructure, etc.).
> > > > > > > NOTE 2 - Overall acceptability may be influenced by user
> > > > > > expectations and context.
> > > > > > >
> > > > > > > Important for MONARCH:
> > > > > > > 1st ... perceived by end-user
> > > > > > > 2nd QoE includes the complete end-to-end sytem effects ...
> > > > > > >
> > > > > > > That said, present RTP monitoring architecture in MONARCH
> > > > > > according clause 3 is not specific on the type of monitoring
> > > > > > architecture. For instance, Fig. 1, it is possibly supposed
> > > > > > that the "RTP Sender" and "RTP Receiver" entities are equal
> > > > > > to a terminal/user equipment (UE). This would be an
> > > > > > end-to-end IP network scenario.
> > > > > > >
> > > > > > > However, the "RTP Sender" and "RTP Receiver" entities may
> > > > > > be also located at the edge of an IP network, e.g. in a
> > > > > > gateway for IP-to-non-IP interworking, i.e. an UE located in
> > > > > > the non-IP network part.
> > > > > > > Note: such scenarios are considered by MEGACO gateways
> > > > > > (I've Cc'd megaco list).
> > > > > > >
> > > > > > > An RTP Sender/Receiver located NOT in the UE
> would question
> > > > > > the value of RTP/RTCP QoE related performance measurements
> > > > > > (because the UE is located outside the RTP domain).
> > > > > > >
> > > > > > > Conclusions:
> > > > > > > - the set of meaningful performance metrics may be
> > > > > > dependent on the location of the RTP Sender/Receiver, e.g.
> > > > > > whether in a UE, gateway, ...
> > > > > > > - don't see any impact on transport level metrics
> > > > > > > - ... but the set of meaningful application level metrics
> > > > > > >
> > > > > > > Proposal for MONARCH:
> > > > > > > #1: insert sub-clause title "3.1 End-to-end IP network
> > > > > > architecture" below clause 3
> > > > > > >
> > > > > > > #2: add a sub-clause 3.2 at the end of clause 3, sth like
> > > > > > >
> > > > > > > "3.2 RTP Sender/Receiver entities located in network nodes
> > > > > > > The location of the RTP Sender/Receiver entity may impact
> > > > > > the set of meaningful metrics.
> > > > > > > For instance: application level metrics for QoE related
> > > > > > performance metrics are questionable (or doesn't really make
> > > > > > sense at all) when measured in a network node (terminating
> > > > > > the RTP) instead of the user equipment."
> > > > > > >
> > > > > > > Something like this would help to avoid confusion.
> > > > > > > I even believe that a QoE measurement in a network node
> > > > > > would violate the QoE definition. Would be rather something
> > > > > > like QoE* ("remote QoE"):-(
> > > > > > >
> > > > > > > Such information would improve the MONARCH doc in
> > my opinion.
> > > > > > > Sorry for that late comment.
> > > > > > > Any views?
> > > > > >
> > > > > > [Qin]:
> > > > > > Albrrecht, if you follow ealry list discussion on
> > > > > > draft-hunt-avt-monarch-01, you will see the rough consensus
> > > > > > to position this document was
> > > > > > this daft should focus on guidelines for defining reporting
> > > > > > blocks. That is to say the main purpose of MONARCH draft
> > > > is how to
> > > > > > provide guidelines for the development of new RTCP XR block
> > > > > > types in XRBlock working group.
> > > > >
> > > > > [ABS] ... then the title "monitoring architectures" is
> > misleading.
> > > > > Proposal: keep title, revise scope section on focus
> > > > >
> > > > > [Qin]: No, the title is *RTP* monitoring architecture, we can
> > > > > not expand scope into IP monitoring architecture.
> > > >
> > > > [ABS] That's wasn't the intent! Did just focus on the key word.
> > > >
> > > > >
> > > > > >
> > > > > > Therefore how and where to collect the metric from RTP
> > > > > > endpoint is not scope of this document, in my opinion. since
> > > > > > you may have many ways to do this and different vendors have
> > > > > > their different appoaches. It will be better to leave this
> > > > > > beyond the scope. But you are right, it will be more
> > > > > > reasonable to measure QoE related performance metric at the
> > > > > > RTP receiver.
> > > > >
> > > > > [ABS] I would disagree. At least your statement should be
> > > > > conditional, sth like
> > > > > "QoE related performance metrics may be measured in a RTP
> > > > > receiver, IF the RTP receiver function is located in user
> > > > > equipment (e.g. IP terminal), because QoE performance metrics
> > > > > are tightly coupled to the point of view of a 'user'.
> > > > > ... IF NOT, then ..."
> > > > >
> > > > > [Qin]: I am not sure user equipment or IP terminal is the
> > > > > right term from RTP perspective.
> > > > >
> > > > > Also if you read P.NAMS, P.NAMS model for calculating QoE
> > > > > related metric can be placed either at the network or at
> > > the client.
> > > > > So I disagree with what you said.
> > > >
> > > > [ABS] Not convinced at all.
> > > > Guess you are referring to the "mid-point" models, right?
> > > > The usage of such that models depends on "prior knowledge
> > > > ..." information.
> > > > Thus, the applicability is conditional. You may not make such
> > > > a general statement.
> > > >
> > > >
> > > > >
> > > > > Also as I said, how and where to collect the metric from RTP
> > > > >  endpoint is not scope of this document. It depends on the
> > > > > model you are choosing, e.g., four operation modes specified
> > > > > in P.NAMS.
> > > > > Apparently this should not be specified again in RTP
> > > > > monitoring architecture document.
> > > > >
> > > > > >
> > > > > > Another point is it is not clear to me how RTP
> monitoring has
> > > > > > to do with architectureend to end IP network architecture .
> > > > > > this draft mostly focus on discussing RTP level stuff.
> > > > > > Therefore I am quite doubt that we should describe anything
> > > > > > in this document like how
> > > > > > RTP entties is mapped into network entities/nodes at
> > > the IP layer.
> > > > >
> > > > > [ABS] I don't got any problems to talk about architectural
> > > > > framework for monitoring in this document. Such information
> > > > > is required and this is the only IETF AVT doc about it.
> > > > > The solution to this issue is rather simple to me:
> > > > > - split the MONARCH "monitoring architecture" in
> > > > > 1) a functional monitoring architecture (let's call it
> > 'FMA') and
> > > > > 2) a physical monitoring architecture (... 'PMA').
> > > > >
> > > > > - the present MONARCH doc would describe the FMA at the level
> > > > > of RTP entities (i.e., Fig. 1 entities, incl. all the RTP
> > > > > topology components according RFC 5117)
> > > > >
> > > > > - there are many options of functional-to-physical mappings,
> > > > > i.e. how a FMA would be mapped on a PMA
> > > > > - the mapping is typically dependent on considered network
> > > > > architecture (like SIP, H.323, MGCP, IMS, wireless, etc
> > networks)
> > > > >
> > > > > - the present MONARCH doc would describe the FMA-to-PMA
> > > > > mapping IF all RTP receiver/sender entities would be located
> > > > > in physical IP terminals (UEs)
> > > > > - etc
> > > > >
> > > > > [Qin]: I can understand your point, but you can not do that.
> > > > > Since this document is only focus on *RTP* monitoring
> > > > > architecture, that is what it said in AVTCore milestone:
> > > > > "
> > > > >
> > > > > Goals and Milestones:
> > > > >
> > > > >   Feb 2011 - Submit Monitoring Architecture for RTP for
> > > > Informational
> > > > >
> > > > > "
> > > >
> > > > [ABS] If you go back to my first email on this subject, and
> > > > if you look at my proposal: that's not a lot, nothing which
> > > > violates the charter, goals and milestones.
> > > >
> > > >
> > > > > Also if you really don't see how to map FMA to PMA, you may
> > > > > look at the P.NAMS models specifed in ITU-T P.NAMS.
> > > > > As for how to use RTP monitoring architecture or RTP XR
> > > > > Report in the IMS network architecture, you may look at:
> > > > > http://tools.ietf.org/html/rfc6035
> > > >
> > > > [ABS] That's the SIP reporting interface, i.e., applicable
> > > > primarily for physical IP user equipment with embedded RTP
> > > > sender/receiver function and SIP UA function.
> > > > However, the applicability of RFC 6035 is limited for a
> > > > SIP-to-PSTN gateway (because the RTP sender/receiver would be
> > > > located NOT in user equipment. Also the P.NAMS mid-point
> > > > model fails for such a scenario.
> > > >
> > > > > ITU-T H.248.48.
> > > > > But I haven't check the current status of H.248.48.
> > > >
> > > > [ABS] Work is finalized, see
> > > > http://www.itu.int/md/meetingdoc.asp?lang=3Den&parent=3DT09-SG16-1
> > > > 11121-TD-PLEN-0419
> > > >
> > > > >
> > > > > >
> > > > > > But as the author of this document, I am interested and open
> > > > > > to other opinions.:-)
> > > > >
> > > > > [ABS] Like to add a further aspect: a "functional monitoring
> > > > > architecture" may be considered as a network overlay,
> > > > > something which adds additional capabilities (here:
> > > > > measurement services, reporting services on top of basic RTP
> > > > > services).
> > > > > Such an overlay concept is nothing new: e.g., the
> > > > > MultiService Forum did define a "Performance Measurement &
> > > > > Monitoring (PMM)" overlay network, or IETF RMON may be also
> > > > > considered as such.
> > > > >
> > > > > >
> > > > > > > Regards,
> > > > > > > Albrecht
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >> -----Original Message-----
> > > > > > >> From: avt-bounces@ietf.org
> [mailto:avt-bounces@ietf.org] On
> > > > > > >> Behalf Of internet-drafts@ietf.org
> > > > > > >> Sent: Dienstag, 29. November 2011 08:56
> > > > > > >> To: i-d-announce@ietf.org
> > > > > > >> Cc: avt@ietf.org
> > > > > > >> Subject: [AVTCORE] I-D Action:
> > > > draft-ietf-avtcore-monarch-08.txt
> > > > > > >>
> > > > > > >>
> > > > > > >> A New Internet-Draft is available from the on-line
> > > > > > >> Internet-Drafts directories. This draft is a work
> > item of the
> > > > > > >> Audio/Video Transport Core Maintenance Working Group
> > > > of the IETF.
> > > > > > >>
> > > > > > >> Title           : Monitoring Architectures for RTP
> > > > > > >> Author(s)       : Qin Wu
> > > > > > >>                           Geoff Hunt
> > > > > > >>                           Philip Arden
> > > > > > >> Filename        : draft-ietf-avtcore-monarch-08.txt
> > > > > > >> Pages           : 25
> > > > > > >> Date            : 2011-11-28
> > > > > > >>
> > > > > > >>    This memo proposes an architecture for
> > extending RTCP with
> > > > > > >> a new RTCP
> > > > > > >>    XR (RFC3611) block type to report new metrics
> > > > regarding media
> > > > > > >>    transmission or reception quality, following RTCP
> > > guideline
> > > > > > >>    established in RFC5968.  This memo suggests that a new
> > > > > > block should
> > > > > > >>    contain a single metric or a small number of metrics
> > > > > > relevant to a
> > > > > > >>    single parameter of interest or concern, rather than
> > > > > > containing a
> > > > > > >>    number of metrics which attempt to provide
> full coverage
> > > > > > >> of all those
> > > > > > >>    parameters of concern to a specific application.
> > > > > > Applications may
> > > > > > >>    then "mix and match" to create a set of blocks which
> > > > > > >> covers their set
> > > > > > >>    of concerns.  Where possible, a specific
> block should be
> > > > > > >> designed to
> > > > > > >>    be re-usable across more than one application, for
> > > > > > example, for all
> > > > > > >>    of voice, streaming audio and video.
> > > > > > >>
> > > > > > >>
> > > > > > >> A URL for this Internet-Draft is:
> > > > > > >>
> > > > > >
> > > > >
> > > >
> > >
> >
> http://www.ietf.org/internet-drafts/draft-ietf-avtcore-monarch-08.txt
> > > > > > >>
> > > > > > >> Internet-Drafts are also available by anonymous FTP at:
> > > > > > >> ftp://ftp.ietf.org/internet-drafts/
> > > > > > >>
> > > > > > >> This Internet-Draft can be retrieved at:
> > > > > > >>
> > > > > >
> > > >
> > ftp://ftp.ietf.org/internet-drafts/draft-ietf-avtcore-monarch-08.txt
> > > > > > >>
> > > > > > >> _______________________________________________
> > > > > > >> Audio/Video Transport Core Maintenance
> > > > > > >> avt@ietf.org
> > > > > > >> https://www.ietf.org/mailman/listinfo/avt
> > > > > > >>
> > > > > > > _______________________________________________
> > > > > > > Audio/Video Transport Core Maintenance
> > > > > > > avt@ietf.org
> > > > > > > https://www.ietf.org/mailman/listinfo/avt
> > > > > >
> > > > > =3D
> > > > _______________________________________________
> > > > Audio/Video Transport Core Maintenance
> > > > avt@ietf.org
> > > > https://www.ietf.org/mailman/listinfo/avt
> > > >
> > >
> >
>

From javi@trajano.us.es  Mon Dec 12 02:59:48 2011
Return-Path: <javi@trajano.us.es>
X-Original-To: megaco@ietfa.amsl.com
Delivered-To: megaco@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 647C321F8B3D for <megaco@ietfa.amsl.com>; Mon, 12 Dec 2011 02:59:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.139
X-Spam-Level: 
X-Spam-Status: No, score=-6.139 tagged_above=-999 required=5 tests=[AWL=0.160,  BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7lmfMZ35W-Kk for <megaco@ietfa.amsl.com>; Mon, 12 Dec 2011 02:59:47 -0800 (PST)
Received: from mail.us.es (mail.us.es [193.147.175.20]) by ietfa.amsl.com (Postfix) with ESMTP id 554A221F8B3A for <megaco@ietf.org>; Mon, 12 Dec 2011 02:59:46 -0800 (PST)
Received: (qmail 19933 invoked from network); 12 Dec 2011 11:59:44 +0100
Received: from unknown (HELO us.es) (192.168.2.12) by us.es with SMTP; 12 Dec 2011 11:59:44 +0100
Received: (qmail 13439 invoked by uid 507); 12 Dec 2011 10:59:31 -0000
Received: from 127.0.0.1 by antivirus2 (envelope-from <javi@trajano.us.es>, uid 501) with qmail-scanner-2.08 (clamdscan: 0.97.3/14116.   Clear:RC:1(127.0.0.1):.  Processed in 0.038723 secs); 12 Dec 2011 10:59:31 -0000
Received: from unknown (HELO antivirus2) (127.0.0.1) by us.es with SMTP; 12 Dec 2011 10:59:31 -0000
Received: from 192.168.1.13 (192.168.1.13) by antivirus2 (F-Secure/fsigk_smtp/406/antivirus2); Mon, 12 Dec 2011 11:59:31 +0100 (CET)
X-Virus-Status: clean(F-Secure/fsigk_smtp/406/antivirus2)
Received: (qmail 10480 invoked from network); 12 Dec 2011 11:59:31 +0100
Received: from trajano.us.es (193.147.162.130) by us.es with AES256-SHA encrypted SMTP; 12 Dec 2011 11:59:31 +0100
Received: from [193.147.162.138] (adriano.us.es [193.147.162.138]) (authenticated bits=0) by trajano.us.es (8.13.8/8.13.8/Debian-3) with ESMTP id pBCAxUHj024990 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NOT); Mon, 12 Dec 2011 11:59:30 +0100
Message-ID: <4EE5DEA0.7040402@trajano.us.es>
Date: Mon, 12 Dec 2011 11:59:44 +0100
From: =?ISO-8859-1?Q?Javi_Mu=F1oz?= <javi@trajano.us.es>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; es-ES; rv:1.9.2.24) Gecko/20111103 Thunderbird/3.1.16
MIME-Version: 1.0
To: "megaco@ietf.org" <megaco@ietf.org>
References: <4EE3543D.8000301@trajano.us.es> <4EE533ED.8030006@nteczone.com>
In-Reply-To: <4EE533ED.8030006@nteczone.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [Megaco] OutOfService vs Inactive
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.1.12
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: Mon, 12 Dec 2011 10:59:48 -0000

Christian,
> the MGC can't change OutOfService to InService.

When MGC  sends to MG a serviceChange command with method Forced or 
Graceful and reason 905 (Out Of Service), MGC requests to MG to put out 
of service the indicated terminations. Is not it?

Regards,

Javi

>
> Regards, Christian
>
> On 10/12/2011 11:44 PM, Javi wrote:
>> In a termination *with**a single stream*, which is the 
>> differencebetween?:
>>
>> (a) TerminationState{ServiceStates=OutOfService}
>>
>> (b) Media{ LocalControl { StreamMode=Inactive } }
>>
>> Regards,
>>
>> Javi
>>
>>
>> _______________________________________________
>> Megaco mailing list
>> Megaco@ietf.org
>> https://www.ietf.org/mailman/listinfo/megaco
> _______________________________________________
> Megaco mailing list
> Megaco@ietf.org
> https://www.ietf.org/mailman/listinfo/megaco
>


From javi@trajano.us.es  Mon Dec 12 03:11:16 2011
Return-Path: <javi@trajano.us.es>
X-Original-To: megaco@ietfa.amsl.com
Delivered-To: megaco@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D852A21F8B1C for <megaco@ietfa.amsl.com>; Mon, 12 Dec 2011 03:11:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.549
X-Spam-Level: 
X-Spam-Status: No, score=-5.549 tagged_above=-999 required=5 tests=[AWL=-0.450, BAYES_00=-2.599, J_CHICKENPOX_12=0.6, J_CHICKENPOX_15=0.6, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SiQiXPJKXwrr for <megaco@ietfa.amsl.com>; Mon, 12 Dec 2011 03:11:16 -0800 (PST)
Received: from mail.us.es (mail.us.es [193.147.175.20]) by ietfa.amsl.com (Postfix) with ESMTP id B9C7421F8B17 for <megaco@ietf.org>; Mon, 12 Dec 2011 03:11:15 -0800 (PST)
Received: (qmail 6071 invoked from network); 12 Dec 2011 12:11:12 +0100
Received: from unknown (HELO us.es) (192.168.2.13) by us.es with SMTP; 12 Dec 2011 12:11:12 +0100
Received: (qmail 17486 invoked by uid 507); 12 Dec 2011 11:11:11 -0000
Received: from 127.0.0.1 by antivirus3 (envelope-from <javi@trajano.us.es>, uid 501) with qmail-scanner-2.08 (clamdscan: 0.97.3/14116.   Clear:RC:1(127.0.0.1):.  Processed in 0.043079 secs); 12 Dec 2011 11:11:11 -0000
Received: from unknown (HELO antivirus3) (127.0.0.1) by us.es with SMTP; 12 Dec 2011 11:11:11 -0000
Received: from 192.168.1.13 (192.168.1.13) by antivirus3 (F-Secure/fsigk_smtp/406/antivirus3); Mon, 12 Dec 2011 12:11:10 +0100 (CET)
X-Virus-Status: clean(F-Secure/fsigk_smtp/406/antivirus3)
Received: (qmail 17542 invoked from network); 12 Dec 2011 12:11:10 +0100
Received: from trajano.us.es (193.147.162.130) by us.es with AES256-SHA encrypted SMTP; 12 Dec 2011 12:11:10 +0100
Received: from [193.147.162.138] (adriano.us.es [193.147.162.138]) (authenticated bits=0) by trajano.us.es (8.13.8/8.13.8/Debian-3) with ESMTP id pBCBB0Ol025180 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NOT); Mon, 12 Dec 2011 12:11:10 +0100
Message-ID: <4EE5E152.20107@trajano.us.es>
Date: Mon, 12 Dec 2011 12:11:14 +0100
From: =?ISO-8859-1?Q?Javi_Mu=F1oz?= <javi@trajano.us.es>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; es-ES; rv:1.9.2.24) Gecko/20111103 Thunderbird/3.1.16
MIME-Version: 1.0
To: "megaco@ietf.org" <megaco@ietf.org>
References: <4EE358A5.2040408@trajano.us.es> <4EE5350C.2070109@nteczone.com>
In-Reply-To: <4EE5350C.2070109@nteczone.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Subject: Re: [Megaco] Allocation resources for a call
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.1.12
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: Mon, 12 Dec 2011 11:11:17 -0000

Christian,

El 11/12/2011 23:56, Christian Groves escribió:
> HEllo Javi,
>
> I'm not sure what the issue is? This just sounds like a normal 
> transcoding case.
> i.e. For Termination connection to equipment A set codec X, for the 
> Termination connected to equipment B set codec Y. The MG simply 
> transcodes the codec format when sending a A or B.

The problem is that the connection with A and B is performed within the 
same call. Thus, in phase A, MG sends to equipment A with codec X, but 
also should allocate the resources needed for Phase B.

Otherwise, the call can start and, to change to Phase B, the MG may not 
have the resources to communicate with equipment B with the codecY, 
needing to release the call. Thus, the objective is to prevent this 
happening, ensuring that once the call begins, MG will have reserved all 
resources required for that call.

Javi
>
> Regards, Christian
>
> On 11/12/2011 12:03 AM, Javi wrote:
>> I have a callwith the following 3 phases:
>>
>> A) Phase A: MG may carry media to a equipment A using the codec x.
>>
>> B) Phase B: MG may carry media to a equipment B using the codec y.
>>
>> C) Phase C: again, MG may carry media to the equipment A using the 
>> codec x.
>>
>>
>> In that case, what is the most appropriate way to model the call on 
>> the gateway to ensure that once the call starts the gateway will have 
>> the necessary resources for all phases?
>>
>> (i) 2 terminations (in the same or different context?) using the 
>> property "StreamMode=Inactive":
>>
>> * Termination 1 with:
>>     v=0
>>     c=IN IP4 IP_A
>>     m=audio port_A  RTP/AVP codec_x
>>
>> * Termination 2 with:
>>     v=0
>>     c=IN IP4 IP_B
>>     m=audio port_B  RTP/AVP codec_y
>>
>> In phase:
>>     (A, C) Termination 1 with StreamMode=SendRecv; Termination 2 with 
>> StreamMode=Inactive
>>     (B) Termination 1 with StreamMode=Inactive; Termination 2 with 
>> StreamMode=SendRecv
>>
>> ===
>>
>> (ii) 1 termination with 2 session descriptions with ReserveGroup=true:
>>
>> In Phase A:
>> LocalControl {
>> ReserveGroup = True},
>> Local/Remote {
>>     v=0
>>     c=IN IP4 IP_A
>>     m=audio port_A  RTP/AVP codec_x
>>     v=0
>>     c=IN IP4 IP_B
>>     m=audio port_B  RTP/AVP codec_y
>> }
>>
>> In Phase B:
>> LocalControl {
>> ReserveGroup = True},
>> Local/Remote {
>>     v=0
>>     c=IN IP4 IP_B
>>     m=audio port_B  RTP/AVP codec_y
>>     v=0
>>     c=IN IP4 IP_A
>>     m=audio port_A  RTP/AVP codec_x
>> }
>>
>> In Phase C:
>> Local/Remote {
>>     v=0
>>     c=IN IP4 IP_A
>>     m=audio port_A  RTP/AVP codec_x
>> }
>>
>> ===
>>
>> (iii) 1 termination with 1 session descriptions with 
>> ReserveValue=true to allocate the resources:
>>
>> Phase A)
>> LocalControl {
>> ReserveValue = True},
>> Local/Remote {
>>     v=0
>>     c=IN IP4 IP_A
>>     m=audio port_A  RTP/AVP codec_x  codec_y
>> }
>>
>> Phase B)
>> LocalControl {
>> ReserveValue = True},
>> Local/Remote {
>>     v=0
>>     c=IN IP4 IP_B
>>     m=audio port_B  RTP/AVP codec_y  codec_x
>> }
>>
>> Phase C)
>> Local/Remote {
>>     v=0
>>     c=IN IP4 IP_A
>>     m=audio port_A  RTP/AVP codec_x
>> }
>>
>>
>>
>> Regards,
>>
>> Javi
>>
>> _______________________________________________
>> Megaco mailing list
>> Megaco@ietf.org
>> https://www.ietf.org/mailman/listinfo/megaco
>>
> _______________________________________________
> Megaco mailing list
> Megaco@ietf.org
> https://www.ietf.org/mailman/listinfo/megaco
>


From javi@trajano.us.es  Mon Dec 12 03:31:38 2011
Return-Path: <javi@trajano.us.es>
X-Original-To: megaco@ietfa.amsl.com
Delivered-To: megaco@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 879B721F8B3B for <megaco@ietfa.amsl.com>; Mon, 12 Dec 2011 03:31:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.123
X-Spam-Level: 
X-Spam-Status: No, score=-6.123 tagged_above=-999 required=5 tests=[AWL=0.176,  BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5F8gXmQ8Bdo5 for <megaco@ietfa.amsl.com>; Mon, 12 Dec 2011 03:31:37 -0800 (PST)
Received: from mail.us.es (mail.us.es [193.147.175.20]) by ietfa.amsl.com (Postfix) with ESMTP id 5579821F8B3A for <megaco@ietf.org>; Mon, 12 Dec 2011 03:31:37 -0800 (PST)
Received: (qmail 1513 invoked from network); 12 Dec 2011 12:31:35 +0100
Received: from unknown (HELO us.es) (192.168.2.11) by us.es with SMTP; 12 Dec 2011 12:31:35 +0100
Received: (qmail 15252 invoked by uid 507); 12 Dec 2011 11:31:24 -0000
Received: from 127.0.0.1 by antivirus1 (envelope-from <javi@trajano.us.es>, uid 501) with qmail-scanner-2.08 (clamdscan: 0.97.3/14116.   Clear:RC:1(127.0.0.1):.  Processed in 0.045074 secs); 12 Dec 2011 11:31:24 -0000
Received: from unknown (HELO antivirus1) (127.0.0.1) by us.es with SMTP; 12 Dec 2011 11:31:24 -0000
Received: from 192.168.1.13 (192.168.1.13) by antivirus1 (F-Secure/fsigk_smtp/406/antivirus1); Mon, 12 Dec 2011 12:31:24 +0100 (CET)
X-Virus-Status: clean(F-Secure/fsigk_smtp/406/antivirus1)
Received: (qmail 19990 invoked from network); 12 Dec 2011 12:31:24 +0100
Received: from trajano.us.es (193.147.162.130) by us.es with AES256-SHA encrypted SMTP; 12 Dec 2011 12:31:24 +0100
Received: from [193.147.162.138] (adriano.us.es [193.147.162.138]) (authenticated bits=0) by trajano.us.es (8.13.8/8.13.8/Debian-3) with ESMTP id pBCBVNUT025701 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NOT); Mon, 12 Dec 2011 12:31:23 +0100
Message-ID: <4EE5E619.4050506@trajano.us.es>
Date: Mon, 12 Dec 2011 12:31:37 +0100
From: =?ISO-8859-1?Q?Javi_Mu=F1oz?= <javi@trajano.us.es>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; es-ES; rv:1.9.2.24) Gecko/20111103 Thunderbird/3.1.16
MIME-Version: 1.0
To: "megaco@ietf.org" <megaco@ietf.org>
References: <4ED518F6.4020201@trajano.us.es>	<5F7BCCF5541B7444830A2288ABBEBC962161900622@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com>	<4ED604A0.2000402@trajano.us.es>	<4ED6640A.9030508@trajano.us.es>	<5F7BCCF5541B7444830A2288ABBEBC962161900780@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com>	<4ED66B87.7050907@trajano.us.es>	<4ED6767D.7070109@trajano.us.es>	<703C56B521385C4C9091299BE82357B7EF26034C@USNAVSXCHMBSA2.ndc.alcatel-lucent.com>	<4ED750D6.9000608@trajano.us.es>	<703C56B521385C4C9091299BE82357B7EF2605BE@USNAVSXCHMBSA2.ndc.alcatel-lucent.com>	<4ED7B036.4000103@trajano.us.es>	<703C56B521385C4C9091299BE82357B7EF2607C5@USNAVSXCHMBSA2.ndc.alcatel-lucent.com> <4ED7CAA1.3020902@trajano.us.es> <31939CE9629A7F46885A9F97CEA9BF577BFE78B4@USNAVSXCHMBSD3.ndc.alcatel-lucent.com>
In-Reply-To: <31939CE9629A7F46885A9F97CEA9BF577BFE78B4@USNAVSXCHMBSD3.ndc.alcatel-lucent.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Subject: Re: [Megaco] Selection of media (m=) at MG
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.1.12
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: Mon, 12 Dec 2011 11:31:38 -0000

Raju,
> In fact, when a signal (tone/annc) is played on one termination (signal going outside of the context),
> the termination is temporarily "disconnected oneway" (so it won't receive any data, but can send) from
> the other terminations (as if the termination has "oneway" topology to others).
>
>
When a signal is played by the MG, does the MG automatically applied 
that "oneway" topology, or it should be explicitly indicated by the MGC 
in the configuration of the termination?(it would be on the Stream, 
rather than on the termination, since it migth be a multistream termination)

Javi
>
>> -----Original Message-----
>> From: megaco-bounces@ietf.org
>> [mailto:megaco-bounces@ietf.org] On Behalf Of Javi Muñoz
>> Sent: Thursday, December 01, 2011 12:43 PM
>> To: megaco@ietf.org
>> Cc: Bhattacharjee, Arindam (Arindam)
>> Subject: Re: [Megaco] Selection of media (m=) at MG
>>
>> Arindam,
>>
>>> You can use another option: have reserve value on and use
>> both g711 and Clearmode on both remote and local SDP and MG
>> will send in g711 only because that has higher preference
>> when G711 appears before CLearMode codec in the list as follows:
>>>    m=audio<puerto>    RTP/AVP 0 [8]<PT_dinámico>
>>>    a=rtpmap:<PT_dinámico>    CLEARMODE/8000
>> When the Remote descriptor has several audio codecs in the line "m=":
>>
>>    m=audio<puerto>    RTP/AVP 0 [8]<PT_dinámico>
>>
>>
>> I understand that:
>>
>> 1º First codec in the line is used if it is possible.
>>
>> 2º In case that codec may not be used (for an error, for
>> example), the
>> second codec would be tried (I understand this is the reaseon why the
>> Remote descriptor may have several audio codecs in the same line "m=).
>>
>>
>> If it is so, and we use:
>>
>>    m=audio<puerto>    RTP/AVP 0 [8]<PT_dinámico>
>>
>>
>> What would happen if when MG needs to send the tone/ann., the
>> codecs "0"
>> and "8" may not be used?. MG would try to send the tone/ann. to the
>> terminal using CLEARMODE, when terminal is not ready to receive that.
>>
>> Javi
>> _______________________________________________
>> Megaco mailing list
>> Megaco@ietf.org
>> https://www.ietf.org/mailman/listinfo/megaco
>>


From javi@trajano.us.es  Mon Dec 12 04:11:08 2011
Return-Path: <javi@trajano.us.es>
X-Original-To: megaco@ietfa.amsl.com
Delivered-To: megaco@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E707021F8AF4 for <megaco@ietfa.amsl.com>; Mon, 12 Dec 2011 04:11:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.132
X-Spam-Level: 
X-Spam-Status: No, score=-6.132 tagged_above=-999 required=5 tests=[AWL=0.167,  BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nkkEUkKZ4s1p for <megaco@ietfa.amsl.com>; Mon, 12 Dec 2011 04:10:54 -0800 (PST)
Received: from mail.us.es (mail.us.es [193.147.175.20]) by ietfa.amsl.com (Postfix) with ESMTP id C2AEF21F8AD8 for <megaco@ietf.org>; Mon, 12 Dec 2011 04:10:53 -0800 (PST)
Received: (qmail 28388 invoked from network); 12 Dec 2011 13:10:52 +0100
Received: from unknown (HELO us.es) (192.168.2.11) by us.es with SMTP; 12 Dec 2011 13:10:52 +0100
Received: (qmail 18719 invoked by uid 507); 12 Dec 2011 12:10:49 -0000
Received: from 127.0.0.1 by antivirus1 (envelope-from <javi@trajano.us.es>, uid 501) with qmail-scanner-2.08 (clamdscan: 0.97.3/14116.   Clear:RC:1(127.0.0.1):.  Processed in 0.051107 secs); 12 Dec 2011 12:10:49 -0000
Received: from unknown (HELO antivirus1) (127.0.0.1) by us.es with SMTP; 12 Dec 2011 12:10:49 -0000
Received: from 192.168.1.13 (192.168.1.13) by antivirus1 (F-Secure/fsigk_smtp/406/antivirus1); Mon, 12 Dec 2011 13:10:49 +0100 (CET)
X-Virus-Status: clean(F-Secure/fsigk_smtp/406/antivirus1)
Received: (qmail 23281 invoked from network); 12 Dec 2011 13:10:49 +0100
Received: from trajano.us.es (193.147.162.130) by us.es with AES256-SHA encrypted SMTP; 12 Dec 2011 13:10:49 +0100
Received: from [193.147.162.138] (adriano.us.es [193.147.162.138]) (authenticated bits=0) by trajano.us.es (8.13.8/8.13.8/Debian-3) with ESMTP id pBCCAnlR026632 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NOT); Mon, 12 Dec 2011 13:10:49 +0100
Message-ID: <4EE5EF57.6010706@trajano.us.es>
Date: Mon, 12 Dec 2011 13:11:03 +0100
From: =?ISO-8859-1?Q?Javi_Mu=F1oz?= <javi@trajano.us.es>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; es-ES; rv:1.9.2.24) Gecko/20111103 Thunderbird/3.1.16
MIME-Version: 1.0
To: "megaco@ietf.org" <megaco@ietf.org>
References: <4ED518F6.4020201@trajano.us.es>	<5F7BCCF5541B7444830A2288ABBEBC962161900622@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com>	<4ED604A0.2000402@trajano.us.es>	<4ED6640A.9030508@trajano.us.es>	<5F7BCCF5541B7444830A2288ABBEBC962161900780@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com>	<4ED66B87.7050907@trajano.us.es>	<4ED6767D.7070109@trajano.us.es>	<703C56B521385C4C9091299BE82357B7EF26034C@USNAVSXCHMBSA2.ndc.alcatel-lucent.com>	<4ED750D6.9000608@trajano.us.es>	<703C56B521385C4C9091299BE82357B7EF2605BE@USNAVSXCHMBSA2.ndc.alcatel-lucent.com>	<4ED7B036.4000103@trajano.us.es>	<703C56B521385C4C9091299BE82357B7EF2607C5@USNAVSXCHMBSA2.ndc.alcatel-lucent.com>	<4ED7CAA1.3020902@trajano.us.es>	<31939CE9629A7F46885A9F97CEA9BF577BFE78B4@USNAVSXCHMBSD3.ndc.alcatel-lucent.com> <4EE5E619.4050506@trajano.us.es>
In-Reply-To: <4EE5E619.4050506@trajano.us.es>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Subject: Re: [Megaco] Selection of media (m=) at MG
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.1.12
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: Mon, 12 Dec 2011 12:11:08 -0000

Raju,

In addition, [TS 183 002/Clause 7.1.4] indicates that if announcement 
are remote to MG, "the MGC shall initiate a connection to an external 
announcement machine (MRF), by
temporarily adding a termination into the context.".

I understand that this context should be the same that contains the 
termination play announcements. For example, in:

TE <--->  MG <--->  MRF


MG must ge the announcements from MRF and play them to TE. For that, I 
understand MGC must create the next contexto in the MG:

TE <-- [Termination A (codec PCMU)] -- *  -- [Termination B (codec 
PCMU)] --> MRF

So, termination B is used to get the announcements, and termination A is 
used to play them.

But, if "when a signal (tone/annc) is played on one termination, the 
termination is temporarily disconnected oneway", then while termination 
A playing a announcement, it can not continue to receive announcement 
that continue to get the termination B.

Javi


El 12/12/2011 12:31, Javi Muñoz escribió:
> Raju,
>> In fact, when a signal (tone/annc) is played on one termination 
>> (signal going outside of the context),
>> the termination is temporarily "disconnected oneway" (so it won't 
>> receive any data, but can send) from
>> the other terminations (as if the termination has "oneway" topology 
>> to others).
>>
>>
> When a signal is played by the MG, does the MG automatically applied 
> that "oneway" topology, or it should be explicitly indicated by the 
> MGC in the configuration of the termination?(it would be on the 
> Stream, rather than on the termination, since it migth be a 
> multistream termination)
>
> Javi
>>
>>> -----Original Message-----
>>> From: megaco-bounces@ietf.org
>>> [mailto:megaco-bounces@ietf.org] On Behalf Of Javi Muñoz
>>> Sent: Thursday, December 01, 2011 12:43 PM
>>> To: megaco@ietf.org
>>> Cc: Bhattacharjee, Arindam (Arindam)
>>> Subject: Re: [Megaco] Selection of media (m=) at MG
>>>
>>> Arindam,
>>>
>>>> You can use another option: have reserve value on and use
>>> both g711 and Clearmode on both remote and local SDP and MG
>>> will send in g711 only because that has higher preference
>>> when G711 appears before CLearMode codec in the list as follows:
>>>>    m=audio<puerto>    RTP/AVP 0 [8]<PT_dinámico>
>>>>    a=rtpmap:<PT_dinámico>    CLEARMODE/8000
>>> When the Remote descriptor has several audio codecs in the line "m=":
>>>
>>>    m=audio<puerto>    RTP/AVP 0 [8]<PT_dinámico>
>>>
>>>
>>> I understand that:
>>>
>>> 1º First codec in the line is used if it is possible.
>>>
>>> 2º In case that codec may not be used (for an error, for
>>> example), the
>>> second codec would be tried (I understand this is the reaseon why the
>>> Remote descriptor may have several audio codecs in the same line "m=).
>>>
>>>
>>> If it is so, and we use:
>>>
>>>    m=audio<puerto>    RTP/AVP 0 [8]<PT_dinámico>
>>>
>>>
>>> What would happen if when MG needs to send the tone/ann., the
>>> codecs "0"
>>> and "8" may not be used?. MG would try to send the tone/ann. to the
>>> terminal using CLEARMODE, when terminal is not ready to receive that.
>>>
>>> Javi
>>> _______________________________________________
>>> Megaco mailing list
>>> Megaco@ietf.org
>>> https://www.ietf.org/mailman/listinfo/megaco
>>>
>
> _______________________________________________
> Megaco mailing list
> Megaco@ietf.org
> https://www.ietf.org/mailman/listinfo/megaco
>


From javi@trajano.us.es  Mon Dec 12 09:40:38 2011
Return-Path: <javi@trajano.us.es>
X-Original-To: megaco@ietfa.amsl.com
Delivered-To: megaco@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6696B21F8B75 for <megaco@ietfa.amsl.com>; Mon, 12 Dec 2011 09:40:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.163
X-Spam-Level: 
X-Spam-Status: No, score=-6.163 tagged_above=-999 required=5 tests=[AWL=0.136,  BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PfBK17lsJKxG for <megaco@ietfa.amsl.com>; Mon, 12 Dec 2011 09:40:37 -0800 (PST)
Received: from mail.us.es (mail.us.es [193.147.175.20]) by ietfa.amsl.com (Postfix) with ESMTP id 3FC2A21F8B55 for <megaco@ietf.org>; Mon, 12 Dec 2011 09:40:37 -0800 (PST)
Received: (qmail 24047 invoked from network); 12 Dec 2011 18:40:36 +0100
Received: from unknown (HELO us.es) (192.168.2.12) by us.es with SMTP; 12 Dec 2011 18:40:36 +0100
Received: (qmail 14963 invoked by uid 507); 12 Dec 2011 17:40:35 -0000
Received: from 127.0.0.1 by antivirus2 (envelope-from <javi@trajano.us.es>, uid 501) with qmail-scanner-2.08 (clamdscan: 0.97.3/14118.   Clear:RC:1(127.0.0.1):.  Processed in 0.048175 secs); 12 Dec 2011 17:40:35 -0000
Received: from unknown (HELO antivirus2) (127.0.0.1) by us.es with SMTP; 12 Dec 2011 17:40:35 -0000
Received: from 192.168.1.13 (192.168.1.13) by antivirus2 (F-Secure/fsigk_smtp/406/antivirus2); Mon, 12 Dec 2011 18:40:35 +0100 (CET)
X-Virus-Status: clean(F-Secure/fsigk_smtp/406/antivirus2)
Received: (qmail 28069 invoked from network); 12 Dec 2011 18:40:35 +0100
Received: from trajano.us.es (193.147.162.130) by us.es with AES256-SHA encrypted SMTP; 12 Dec 2011 18:40:35 +0100
Received: from [193.147.162.138] (adriano.us.es [193.147.162.138]) (authenticated bits=0) by trajano.us.es (8.13.8/8.13.8/Debian-3) with ESMTP id pBCHeYJu032078 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NOT); Mon, 12 Dec 2011 18:40:35 +0100
Message-ID: <4EE63CA2.6040000@trajano.us.es>
Date: Mon, 12 Dec 2011 18:40:50 +0100
From: =?ISO-8859-1?Q?Javi_Mu=F1oz?= <javi@trajano.us.es>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; es-ES; rv:1.9.2.24) Gecko/20111103 Thunderbird/3.1.16
MIME-Version: 1.0
To: "megaco@ietf.org" <megaco@ietf.org>
References: <4ED518F6.4020201@trajano.us.es>	<5F7BCCF5541B7444830A2288ABBEBC962161900622@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com>	<4ED604A0.2000402@trajano.us.es>	<4ED6640A.9030508@trajano.us.es>	<5F7BCCF5541B7444830A2288ABBEBC962161900780@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com>	<4ED66B87.7050907@trajano.us.es>	<4ED6767D.7070109@trajano.us.es>	<703C56B521385C4C9091299BE82357B7EF26034C@USNAVSXCHMBSA2.ndc.alcatel-lucent.com>	<4ED750D6.9000608@trajano.us.es>	<703C56B521385C4C9091299BE82357B7EF2605BE@USNAVSXCHMBSA2.ndc.alcatel-lucent.com>	<4ED7B036.4000103@trajano.us.es>	<703C56B521385C4C9091299BE82357B7EF2607C5@USNAVSXCHMBSA2.ndc.alcatel-lucent.com>	<4ED7CAA1.3020902@trajano.us.es>	<31939CE9629A7F46885A9F97CEA9BF577BFE78B4@USNAVSXCHMBSD3.ndc.alcatel-lucent.com> <4EE5E619.4050506@trajano.us.es>
In-Reply-To: <4EE5E619.4050506@trajano.us.es>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Subject: Re: [Megaco] Selection of media (m=) at MG
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.1.12
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: Mon, 12 Dec 2011 17:40:38 -0000

Raju,
> In fact, when a signal (tone/annc) is played on one termination 
> (signal going outside of the context),
> the termination is temporarily "disconnected oneway" (so it won't 
> receive any data, but can send) from
> the other terminations (as if the termination has "oneway" topology to 
> others).
>>
A more.

What document or Recommendation defines exactly this behavior of a 
termination for sending tones / announcements?

Regards,

Javi

>>> -----Original Message-----
>>> From: megaco-bounces@ietf.org
>>> [mailto:megaco-bounces@ietf.org] On Behalf Of Javi Muñoz
>>> Sent: Thursday, December 01, 2011 12:43 PM
>>> To: megaco@ietf.org
>>> Cc: Bhattacharjee, Arindam (Arindam)
>>> Subject: Re: [Megaco] Selection of media (m=) at MG
>>>
>>> Arindam,
>>>
>>>> You can use another option: have reserve value on and use
>>> both g711 and Clearmode on both remote and local SDP and MG
>>> will send in g711 only because that has higher preference
>>> when G711 appears before CLearMode codec in the list as follows:
>>>>    m=audio<puerto>    RTP/AVP 0 [8]<PT_dinámico>
>>>>    a=rtpmap:<PT_dinámico>    CLEARMODE/8000
>>> When the Remote descriptor has several audio codecs in the line "m=":
>>>
>>>    m=audio<puerto>    RTP/AVP 0 [8]<PT_dinámico>
>>>
>>>
>>> I understand that:
>>>
>>> 1º First codec in the line is used if it is possible.
>>>
>>> 2º In case that codec may not be used (for an error, for
>>> example), the
>>> second codec would be tried (I understand this is the reaseon why the
>>> Remote descriptor may have several audio codecs in the same line "m=).
>>>
>>>
>>> If it is so, and we use:
>>>
>>>    m=audio<puerto>    RTP/AVP 0 [8]<PT_dinámico>
>>>
>>>
>>> What would happen if when MG needs to send the tone/ann., the
>>> codecs "0"
>>> and "8" may not be used?. MG would try to send the tone/ann. to the
>>> terminal using CLEARMODE, when terminal is not ready to receive that.
>>>
>>> Javi
>>> _______________________________________________
>>> Megaco mailing list
>>> Megaco@ietf.org
>>> https://www.ietf.org/mailman/listinfo/megaco
>>>
>
> _______________________________________________
> Megaco mailing list
> Megaco@ietf.org
> https://www.ietf.org/mailman/listinfo/megaco
>


From tom111.taylor@bell.net  Mon Dec 12 10:23:51 2011
Return-Path: <tom111.taylor@bell.net>
X-Original-To: megaco@ietfa.amsl.com
Delivered-To: megaco@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E0F6021F85FF for <megaco@ietfa.amsl.com>; Mon, 12 Dec 2011 10:23:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.653
X-Spam-Level: 
X-Spam-Status: No, score=-99.653 tagged_above=-999 required=5 tests=[AWL=-0.457, BAYES_50=0.001, MSGID_FROM_MTA_HEADER=0.803, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Z4Ye2AqxzRnB for <megaco@ietfa.amsl.com>; Mon, 12 Dec 2011 10:23:51 -0800 (PST)
Received: from blu0-omc2-s29.blu0.hotmail.com (blu0-omc2-s29.blu0.hotmail.com [65.55.111.104]) by ietfa.amsl.com (Postfix) with ESMTP id 4CABF21F85A8 for <megaco@ietf.org>; Mon, 12 Dec 2011 10:23:51 -0800 (PST)
Received: from BLU0-SMTP29 ([65.55.111.71]) by blu0-omc2-s29.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675);  Mon, 12 Dec 2011 10:23:50 -0800
X-Originating-IP: [76.70.77.190]
X-Originating-Email: [tom111.taylor@bell.net]
Message-ID: <BLU0-SMTP299EE7397835F48D5568E3D8BC0@phx.gbl>
Received: from [192.168.2.17] ([76.70.77.190]) by BLU0-SMTP29.phx.gbl over TLS secured channel with Microsoft SMTPSVC(6.0.3790.4675);  Mon, 12 Dec 2011 10:23:50 -0800
Date: Mon, 12 Dec 2011 13:23:52 -0500
From: Tom Taylor <tom111.taylor@bell.net>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:8.0) Gecko/20111105 Thunderbird/8.0
MIME-Version: 1.0
To: "megaco@ietf.org" <megaco@ietf.org>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 12 Dec 2011 18:23:50.0674 (UTC) FILETIME=[32475720:01CCB8FB]
Subject: [Megaco] MONARCH text proposal
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.1.12
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: Mon, 12 Dec 2011 18:23:52 -0000

Albrecht sent a text proposal for updating the MONARCH text. Since his 
attachment was so much larger than the ordinary limit for IETF E-mails, 
it required administrative approval to proceed. I only let it through on 
the AVTCore list, in deference to the load on the IETF servers. I 
suggest the conversation continue on that list without further 
cross-posting.

Tom Taylor

From Raju.Makaraju@alcatel-lucent.com  Mon Dec 12 14:32:28 2011
Return-Path: <Raju.Makaraju@alcatel-lucent.com>
X-Original-To: megaco@ietfa.amsl.com
Delivered-To: megaco@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8D36A21F87E2 for <megaco@ietfa.amsl.com>; Mon, 12 Dec 2011 14:32:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.699
X-Spam-Level: 
X-Spam-Status: No, score=-5.699 tagged_above=-999 required=5 tests=[AWL=0.600,  BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cwX3aGt4X5Nk for <megaco@ietfa.amsl.com>; Mon, 12 Dec 2011 14:32:28 -0800 (PST)
Received: from ihemail3.lucent.com (ihemail3.lucent.com [135.245.0.37]) by ietfa.amsl.com (Postfix) with ESMTP id EA70421F87C5 for <megaco@ietf.org>; Mon, 12 Dec 2011 14:32:27 -0800 (PST)
Received: from usnavsmail4.ndc.alcatel-lucent.com (usnavsmail4.ndc.alcatel-lucent.com [135.3.39.12]) by ihemail3.lucent.com (8.13.8/IER-o) with ESMTP id pBCMWPUi028559 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 12 Dec 2011 16:32:26 -0600 (CST)
Received: from USNAVSXCHHUB02.ndc.alcatel-lucent.com (usnavsxchhub02.ndc.alcatel-lucent.com [135.3.39.111]) by usnavsmail4.ndc.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id pBCMWOue025712 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Mon, 12 Dec 2011 16:32:25 -0600
Received: from USNAVSXCHMBSD3.ndc.alcatel-lucent.com ([135.3.39.148]) by USNAVSXCHHUB02.ndc.alcatel-lucent.com ([135.3.39.111]) with mapi; Mon, 12 Dec 2011 16:32:24 -0600
From: "Makaraju, Maridi Raju (Raju)" <Raju.Makaraju@alcatel-lucent.com>
To: =?iso-8859-1?Q?Javi_Mu=F1oz?= <javi@trajano.us.es>, "megaco@ietf.org" <megaco@ietf.org>
Date: Mon, 12 Dec 2011 16:32:15 -0600
Thread-Topic: [Megaco] Selection of media (m=) at MG
Thread-Index: Acy4wZ9wvQt0whPZQG2F4CsnKpqqHAAW5p1g
Message-ID: <31939CE9629A7F46885A9F97CEA9BF577C79C6EB@USNAVSXCHMBSD3.ndc.alcatel-lucent.com>
References: <4ED518F6.4020201@trajano.us.es> <5F7BCCF5541B7444830A2288ABBEBC962161900622@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com> <4ED604A0.2000402@trajano.us.es>	<4ED6640A.9030508@trajano.us.es> <5F7BCCF5541B7444830A2288ABBEBC962161900780@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com> <4ED66B87.7050907@trajano.us.es>	<4ED6767D.7070109@trajano.us.es> <703C56B521385C4C9091299BE82357B7EF26034C@USNAVSXCHMBSA2.ndc.alcatel-lucent.com> <4ED750D6.9000608@trajano.us.es> <703C56B521385C4C9091299BE82357B7EF2605BE@USNAVSXCHMBSA2.ndc.alcatel-lucent.com> <4ED7B036.4000103@trajano.us.es> <703C56B521385C4C9091299BE82357B7EF2607C5@USNAVSXCHMBSA2.ndc.alcatel-lucent.com> <4ED7CAA1.3020902@trajano.us.es> <31939CE9629A7F46885A9F97CEA9BF577BFE78B4@USNAVSXCHMBSD3.ndc.alcatel-lucent.com> <4EE5E619.4050506@trajano.us.es>
In-Reply-To: <4EE5E619.4050506@trajano.us.es>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.37
X-Scanned-By: MIMEDefang 2.64 on 135.3.39.12
Subject: Re: [Megaco] Selection of media (m=) at MG
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.1.12
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: Mon, 12 Dec 2011 22:32:28 -0000

Javi,

> Raju,
> > In fact, when a signal (tone/annc) is played on one=20
> termination (signal going outside of the context),
> > the termination is temporarily "disconnected oneway" (so it=20
> won't receive any data, but can send) from
> > the other terminations (as if the termination has "oneway"=20
> topology to others).
> >
> >
> When a signal is played by the MG, does the MG automatically applied=20
> that "oneway" topology, or it should be explicitly indicated=20
> by the MGC=20
> in the configuration of the termination?(it would be on the Stream,=20
> rather than on the termination, since it migth be a=20
> multistream termination)
[Raju] I just gave "topology" example to make it clear.
MGC won't include such a topology while playing a signal.
On MG it is implicit that when it is playing a signal, which
actually sends data on a termination, any other data that needs to=20
be sent to be stopped/dropped temporarily until signal is completed
(else MG has to mix the two data together.. Which won't work
always due to the special nature of signals. For example
when MG is playing a DTMF tone signal, other voice data can't be mixed
with DTMF).

Regards
Raju

>=20
> Javi
> >
> >> -----Original Message-----
> >> From: megaco-bounces@ietf.org
> >> [mailto:megaco-bounces@ietf.org] On Behalf Of Javi Mu=F1oz
> >> Sent: Thursday, December 01, 2011 12:43 PM
> >> To: megaco@ietf.org
> >> Cc: Bhattacharjee, Arindam (Arindam)
> >> Subject: Re: [Megaco] Selection of media (m=3D) at MG
> >>
> >> Arindam,
> >>
> >>> You can use another option: have reserve value on and use
> >> both g711 and Clearmode on both remote and local SDP and MG
> >> will send in g711 only because that has higher preference
> >> when G711 appears before CLearMode codec in the list as follows:
> >>>    m=3Daudio<puerto>    RTP/AVP 0 [8]<PT_din=E1mico>
> >>>    a=3Drtpmap:<PT_din=E1mico>    CLEARMODE/8000
> >> When the Remote descriptor has several audio codecs in the=20
> line "m=3D":
> >>
> >>    m=3Daudio<puerto>    RTP/AVP 0 [8]<PT_din=E1mico>
> >>
> >>
> >> I understand that:
> >>
> >> 1=BA First codec in the line is used if it is possible.
> >>
> >> 2=BA In case that codec may not be used (for an error, for
> >> example), the
> >> second codec would be tried (I understand this is the=20
> reaseon why the
> >> Remote descriptor may have several audio codecs in the=20
> same line "m=3D).
> >>
> >>
> >> If it is so, and we use:
> >>
> >>    m=3Daudio<puerto>    RTP/AVP 0 [8]<PT_din=E1mico>
> >>
> >>
> >> What would happen if when MG needs to send the tone/ann., the
> >> codecs "0"
> >> and "8" may not be used?. MG would try to send the tone/ann. to the
> >> terminal using CLEARMODE, when terminal is not ready to=20
> receive that.
> >>
> >> Javi
> >> _______________________________________________
> >> Megaco mailing list
> >> Megaco@ietf.org
> >> https://www.ietf.org/mailman/listinfo/megaco
> >>
>=20
> =

From Raju.Makaraju@alcatel-lucent.com  Mon Dec 12 14:42:53 2011
Return-Path: <Raju.Makaraju@alcatel-lucent.com>
X-Original-To: megaco@ietfa.amsl.com
Delivered-To: megaco@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 036ED21F8A4B for <megaco@ietfa.amsl.com>; Mon, 12 Dec 2011 14:42:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.849
X-Spam-Level: 
X-Spam-Status: No, score=-5.849 tagged_above=-999 required=5 tests=[AWL=0.450,  BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id laiK1uLNQIwU for <megaco@ietfa.amsl.com>; Mon, 12 Dec 2011 14:42:52 -0800 (PST)
Received: from ihemail2.lucent.com (ihemail2.lucent.com [135.245.0.35]) by ietfa.amsl.com (Postfix) with ESMTP id 252F021F8A35 for <megaco@ietf.org>; Mon, 12 Dec 2011 14:42:52 -0800 (PST)
Received: from usnavsmail3.ndc.alcatel-lucent.com (usnavsmail3.ndc.alcatel-lucent.com [135.3.39.11]) by ihemail2.lucent.com (8.13.8/IER-o) with ESMTP id pBCMgp6S001105 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 12 Dec 2011 16:42:51 -0600 (CST)
Received: from USNAVSXCHHUB02.ndc.alcatel-lucent.com (usnavsxchhub02.ndc.alcatel-lucent.com [135.3.39.111]) by usnavsmail3.ndc.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id pBCMgoJv006648 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Mon, 12 Dec 2011 16:42:50 -0600
Received: from USNAVSXCHMBSD3.ndc.alcatel-lucent.com ([135.3.39.148]) by USNAVSXCHHUB02.ndc.alcatel-lucent.com ([135.3.39.111]) with mapi; Mon, 12 Dec 2011 16:42:50 -0600
From: "Makaraju, Maridi Raju (Raju)" <Raju.Makaraju@alcatel-lucent.com>
To: =?iso-8859-1?Q?Javi_Mu=F1oz?= <javi@trajano.us.es>, "megaco@ietf.org" <megaco@ietf.org>
Date: Mon, 12 Dec 2011 16:42:49 -0600
Thread-Topic: [Megaco] Selection of media (m=) at MG
Thread-Index: Acy49SzsnriwYZpTREe8wbga94rh+AAKQXDQ
Message-ID: <31939CE9629A7F46885A9F97CEA9BF577C79C6F2@USNAVSXCHMBSD3.ndc.alcatel-lucent.com>
References: <4ED518F6.4020201@trajano.us.es> <5F7BCCF5541B7444830A2288ABBEBC962161900622@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com> <4ED604A0.2000402@trajano.us.es>	<4ED6640A.9030508@trajano.us.es> <5F7BCCF5541B7444830A2288ABBEBC962161900780@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com> <4ED66B87.7050907@trajano.us.es>	<4ED6767D.7070109@trajano.us.es> <703C56B521385C4C9091299BE82357B7EF26034C@USNAVSXCHMBSA2.ndc.alcatel-lucent.com> <4ED750D6.9000608@trajano.us.es> <703C56B521385C4C9091299BE82357B7EF2605BE@USNAVSXCHMBSA2.ndc.alcatel-lucent.com> <4ED7B036.4000103@trajano.us.es> <703C56B521385C4C9091299BE82357B7EF2607C5@USNAVSXCHMBSA2.ndc.alcatel-lucent.com> <4ED7CAA1.3020902@trajano.us.es> <31939CE9629A7F46885A9F97CEA9BF577BFE78B4@USNAVSXCHMBSD3.ndc.alcatel-lucent.com> <4EE5E619.4050506@trajano.us.es> <4EE63CA2.6040000@trajano.us.es>
In-Reply-To: <4EE63CA2.6040000@trajano.us.es>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.35
X-Scanned-By: MIMEDefang 2.64 on 135.3.39.11
Subject: Re: [Megaco] Selection of media (m=) at MG
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.1.12
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: Mon, 12 Dec 2011 22:42:53 -0000

Javi,
=20
> Raju,
> > In fact, when a signal (tone/annc) is played on one termination=20
> > (signal going outside of the context),
> > the termination is temporarily "disconnected oneway" (so it won't=20
> > receive any data, but can send) from
> > the other terminations (as if the termination has "oneway"=20
> topology to=20
> > others).
> >>
> A more.
>=20
> What document or Recommendation defines exactly this behavior of a=20
> termination for sending tones / announcements?
[Raju] I could not find any explicit mention of such procedure in H.248.1.
As I explained in other mail, I believe it is implicit by "playing the
signal (no mixing)" we just want the signal to be delivered to the
termination (if the signal is of nature which actually sends, like tone/ann=
c,
data to the termination as opposed to some signals, like ipnapt/latch signa=
l which
won't send any data to the termination).

You may search MEGACO lists or implementers guide to find relevant discussi=
ons.
http://www.itu.int/rec/T-REC-H.Imp248-201007-I/en

Regards
Raju

>=20
> Regards,
>=20
> Javi
>=20
> >>> -----Original Message-----
> >>> From: megaco-bounces@ietf.org
> >>> [mailto:megaco-bounces@ietf.org] On Behalf Of Javi Mu=F1oz
> >>> Sent: Thursday, December 01, 2011 12:43 PM
> >>> To: megaco@ietf.org
> >>> Cc: Bhattacharjee, Arindam (Arindam)
> >>> Subject: Re: [Megaco] Selection of media (m=3D) at MG
> >>>
> >>> Arindam,
> >>>
> >>>> You can use another option: have reserve value on and use
> >>> both g711 and Clearmode on both remote and local SDP and MG
> >>> will send in g711 only because that has higher preference
> >>> when G711 appears before CLearMode codec in the list as follows:
> >>>>    m=3Daudio<puerto>    RTP/AVP 0 [8]<PT_din=E1mico>
> >>>>    a=3Drtpmap:<PT_din=E1mico>    CLEARMODE/8000
> >>> When the Remote descriptor has several audio codecs in=20
> the line "m=3D":
> >>>
> >>>    m=3Daudio<puerto>    RTP/AVP 0 [8]<PT_din=E1mico>
> >>>
> >>>
> >>> I understand that:
> >>>
> >>> 1=BA First codec in the line is used if it is possible.
> >>>
> >>> 2=BA In case that codec may not be used (for an error, for
> >>> example), the
> >>> second codec would be tried (I understand this is the=20
> reaseon why the
> >>> Remote descriptor may have several audio codecs in the=20
> same line "m=3D).
> >>>
> >>>
> >>> If it is so, and we use:
> >>>
> >>>    m=3Daudio<puerto>    RTP/AVP 0 [8]<PT_din=E1mico>
> >>>
> >>>
> >>> What would happen if when MG needs to send the tone/ann., the
> >>> codecs "0"
> >>> and "8" may not be used?. MG would try to send the=20
> tone/ann. to the
> >>> terminal using CLEARMODE, when terminal is not ready to=20
> receive that.
> >>>
> >>> Javi
> >>> _______________________________________________
> >>> Megaco mailing list
> >>> Megaco@ietf.org
> >>> https://www.ietf.org/mailman/listinfo/megaco
> >>>
> >
> > _______________________________________________
> > Megaco mailing list
> > Megaco@ietf.org
> > https://www.ietf.org/mailman/listinfo/megaco
> >
>=20
> =

From Raju.Makaraju@alcatel-lucent.com  Mon Dec 12 14:47:32 2011
Return-Path: <Raju.Makaraju@alcatel-lucent.com>
X-Original-To: megaco@ietfa.amsl.com
Delivered-To: megaco@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5858421F8880 for <megaco@ietfa.amsl.com>; Mon, 12 Dec 2011 14:47:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.939
X-Spam-Level: 
X-Spam-Status: No, score=-5.939 tagged_above=-999 required=5 tests=[AWL=0.360,  BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yUJ2qbDYtBnl for <megaco@ietfa.amsl.com>; Mon, 12 Dec 2011 14:47:31 -0800 (PST)
Received: from ihemail2.lucent.com (ihemail2.lucent.com [135.245.0.35]) by ietfa.amsl.com (Postfix) with ESMTP id 8937421F8888 for <megaco@ietf.org>; Mon, 12 Dec 2011 14:47:31 -0800 (PST)
Received: from usnavsmail3.ndc.alcatel-lucent.com (usnavsmail3.ndc.alcatel-lucent.com [135.3.39.11]) by ihemail2.lucent.com (8.13.8/IER-o) with ESMTP id pBCMlUrX001973 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 12 Dec 2011 16:47:31 -0600 (CST)
Received: from USNAVSXCHHUB03.ndc.alcatel-lucent.com (usnavsxchhub03.ndc.alcatel-lucent.com [135.3.39.112]) by usnavsmail3.ndc.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id pBCMlUh7008038 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Mon, 12 Dec 2011 16:47:30 -0600
Received: from USNAVSXCHMBSD3.ndc.alcatel-lucent.com ([135.3.39.148]) by USNAVSXCHHUB03.ndc.alcatel-lucent.com ([135.3.39.112]) with mapi; Mon, 12 Dec 2011 16:47:30 -0600
From: "Makaraju, Maridi Raju (Raju)" <Raju.Makaraju@alcatel-lucent.com>
To: =?iso-8859-1?Q?Javi_Mu=F1oz?= <javi@trajano.us.es>, "megaco@ietf.org" <megaco@ietf.org>
Date: Mon, 12 Dec 2011 16:46:45 -0600
Thread-Topic: [Megaco] Selection of media (m=) at MG
Thread-Index: Acy4xxocxfe+TljsQbywU5GYmMvPewAWG2Cg
Message-ID: <31939CE9629A7F46885A9F97CEA9BF577C79C6F9@USNAVSXCHMBSD3.ndc.alcatel-lucent.com>
References: <4ED518F6.4020201@trajano.us.es> <5F7BCCF5541B7444830A2288ABBEBC962161900622@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com> <4ED604A0.2000402@trajano.us.es>	<4ED6640A.9030508@trajano.us.es> <5F7BCCF5541B7444830A2288ABBEBC962161900780@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com> <4ED66B87.7050907@trajano.us.es>	<4ED6767D.7070109@trajano.us.es> <703C56B521385C4C9091299BE82357B7EF26034C@USNAVSXCHMBSA2.ndc.alcatel-lucent.com> <4ED750D6.9000608@trajano.us.es> <703C56B521385C4C9091299BE82357B7EF2605BE@USNAVSXCHMBSA2.ndc.alcatel-lucent.com> <4ED7B036.4000103@trajano.us.es> <703C56B521385C4C9091299BE82357B7EF2607C5@USNAVSXCHMBSA2.ndc.alcatel-lucent.com> <4ED7CAA1.3020902@trajano.us.es> <31939CE9629A7F46885A9F97CEA9BF577BFE78B4@USNAVSXCHMBSD3.ndc.alcatel-lucent.com> <4EE5E619.4050506@trajano.us.es> <4EE5EF57.6010706@trajano.us.es>
In-Reply-To: <4EE5EF57.6010706@trajano.us.es>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.35
X-Scanned-By: MIMEDefang 2.64 on 135.3.39.11
Subject: Re: [Megaco] Selection of media (m=) at MG
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.1.12
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: Mon, 12 Dec 2011 22:47:32 -0000

Javi,

> Raju,
>=20
> In addition, [TS 183 002/Clause 7.1.4] indicates that if announcement=20
> are remote to MG, "the MGC shall initiate a connection to an external=20
> announcement machine (MRF), by
> temporarily adding a termination into the context.".
>=20
> I understand that this context should be the same that contains the=20
> termination play announcements. For example, in:
>=20
> TE <--->  MG <--->  MRF
>=20
>=20
> MG must ge the announcements from MRF and play them to TE.=20
> For that, I=20
> understand MGC must create the next contexto in the MG:
>=20
> TE <-- [Termination A (codec PCMU)] -- *  -- [Termination B (codec=20
> PCMU)] --> MRF
>=20
> So, termination B is used to get the announcements, and=20
> termination A is=20
> used to play them.
>=20
> But, if "when a signal (tone/annc) is played on one termination, the=20
> termination is temporarily disconnected oneway", then while=20
> termination=20
> A playing a announcement, it can not continue to receive announcement=20
> that continue to get the termination B.
[Raju] In this case where MRF is playing announcement, there is no signal
played either on Termination A or B. MRF sends the announcement RTP bearer
packets to termination B which in turn forwards them to A and then to UE.
Terminations A and B are not aware of the actual contents of the bearer,
it could be a tone, announcement or a some other media.

Regards
raju

>=20
> Javi
>=20
>=20
> El 12/12/2011 12:31, Javi Mu=F1oz escribi=F3:
> > Raju,
> >> In fact, when a signal (tone/annc) is played on one termination=20
> >> (signal going outside of the context),
> >> the termination is temporarily "disconnected oneway" (so it won't=20
> >> receive any data, but can send) from
> >> the other terminations (as if the termination has "oneway"=20
> topology=20
> >> to others).
> >>
> >>
> > When a signal is played by the MG, does the MG=20
> automatically applied=20
> > that "oneway" topology, or it should be explicitly indicated by the=20
> > MGC in the configuration of the termination?(it would be on the=20
> > Stream, rather than on the termination, since it migth be a=20
> > multistream termination)
> >
> > Javi
> >>
> >>> -----Original Message-----
> >>> From: megaco-bounces@ietf.org
> >>> [mailto:megaco-bounces@ietf.org] On Behalf Of Javi Mu=F1oz
> >>> Sent: Thursday, December 01, 2011 12:43 PM
> >>> To: megaco@ietf.org
> >>> Cc: Bhattacharjee, Arindam (Arindam)
> >>> Subject: Re: [Megaco] Selection of media (m=3D) at MG
> >>>
> >>> Arindam,
> >>>
> >>>> You can use another option: have reserve value on and use
> >>> both g711 and Clearmode on both remote and local SDP and MG
> >>> will send in g711 only because that has higher preference
> >>> when G711 appears before CLearMode codec in the list as follows:
> >>>>    m=3Daudio<puerto>    RTP/AVP 0 [8]<PT_din=E1mico>
> >>>>    a=3Drtpmap:<PT_din=E1mico>    CLEARMODE/8000
> >>> When the Remote descriptor has several audio codecs in=20
> the line "m=3D":
> >>>
> >>>    m=3Daudio<puerto>    RTP/AVP 0 [8]<PT_din=E1mico>
> >>>
> >>>
> >>> I understand that:
> >>>
> >>> 1=BA First codec in the line is used if it is possible.
> >>>
> >>> 2=BA In case that codec may not be used (for an error, for
> >>> example), the
> >>> second codec would be tried (I understand this is the=20
> reaseon why the
> >>> Remote descriptor may have several audio codecs in the=20
> same line "m=3D).
> >>>
> >>>
> >>> If it is so, and we use:
> >>>
> >>>    m=3Daudio<puerto>    RTP/AVP 0 [8]<PT_din=E1mico>
> >>>
> >>>
> >>> What would happen if when MG needs to send the tone/ann., the
> >>> codecs "0"
> >>> and "8" may not be used?. MG would try to send the=20
> tone/ann. to the
> >>> terminal using CLEARMODE, when terminal is not ready to=20
> receive that.
> >>>
> >>> Javi
> >>> _______________________________________________
> >>> Megaco mailing list
> >>> Megaco@ietf.org
> >>> https://www.ietf.org/mailman/listinfo/megaco
> >>>
> >
> > _______________________________________________
> > Megaco mailing list
> > Megaco@ietf.org
> > https://www.ietf.org/mailman/listinfo/megaco
> >
>=20
> =

From Raju.Makaraju@alcatel-lucent.com  Mon Dec 12 14:59:40 2011
Return-Path: <Raju.Makaraju@alcatel-lucent.com>
X-Original-To: megaco@ietfa.amsl.com
Delivered-To: megaco@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D3C4C21F8A57 for <megaco@ietfa.amsl.com>; Mon, 12 Dec 2011 14:59:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.999
X-Spam-Level: 
X-Spam-Status: No, score=-5.999 tagged_above=-999 required=5 tests=[AWL=0.300,  BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WTQKzy6dyALu for <megaco@ietfa.amsl.com>; Mon, 12 Dec 2011 14:59:40 -0800 (PST)
Received: from ihemail3.lucent.com (ihemail3.lucent.com [135.245.0.37]) by ietfa.amsl.com (Postfix) with ESMTP id 184A121F8A35 for <megaco@ietf.org>; Mon, 12 Dec 2011 14:59:40 -0800 (PST)
Received: from usnavsmail3.ndc.alcatel-lucent.com (usnavsmail3.ndc.alcatel-lucent.com [135.3.39.11]) by ihemail3.lucent.com (8.13.8/IER-o) with ESMTP id pBCMxco4011851 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 12 Dec 2011 16:59:39 -0600 (CST)
Received: from USNAVSXCHHUB01.ndc.alcatel-lucent.com (usnavsxchhub01.ndc.alcatel-lucent.com [135.3.39.110]) by usnavsmail3.ndc.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id pBCMxcZP011556 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Mon, 12 Dec 2011 16:59:38 -0600
Received: from USNAVSXCHMBSD3.ndc.alcatel-lucent.com ([135.3.39.148]) by USNAVSXCHHUB01.ndc.alcatel-lucent.com ([135.3.39.110]) with mapi; Mon, 12 Dec 2011 16:59:38 -0600
From: "Makaraju, Maridi Raju (Raju)" <Raju.Makaraju@alcatel-lucent.com>
To: =?iso-8859-1?Q?Javi_Mu=F1oz?= <javi@trajano.us.es>, "megaco@ietf.org" <megaco@ietf.org>
Date: Mon, 12 Dec 2011 16:59:00 -0600
Thread-Topic: [Megaco] OutOfService vs Inactive
Thread-Index: Acy4vS0vZmjWik56Q16couVDssq6EQAYwz9Q
Message-ID: <31939CE9629A7F46885A9F97CEA9BF577C79C6FF@USNAVSXCHMBSD3.ndc.alcatel-lucent.com>
References: <4EE3543D.8000301@trajano.us.es> <4EE533ED.8030006@nteczone.com> <4EE5DEA0.7040402@trajano.us.es>
In-Reply-To: <4EE5DEA0.7040402@trajano.us.es>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.37
X-Scanned-By: MIMEDefang 2.64 on 135.3.39.11
Subject: Re: [Megaco] OutOfService vs Inactive
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.1.12
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: Mon, 12 Dec 2011 22:59:40 -0000

Javi,

> Christian,
> > the MGC can't change OutOfService to InService.
>=20
> When MGC  sends to MG a serviceChange command with method Forced or=20
> Graceful and reason 905 (Out Of Service), MGC requests to MG=20
> to put out=20
> of service the indicated terminations. Is not it?
[Raju]
Right. There are several reasons why a termination can be out of service(OO=
S).
Take a look at "H.248.8 : Gateway control protocol: Error code and service =
change reason description"
http://www.itu.int/rec/T-REC-H.248.8-200708-I/en

Following are some of the relevant ones:

        904 Termination malfunctioning
        905 Termination taken out of service
        906 Loss of lower layer connectivity (e.g. downstream sync)
        907 Transmission Failure

MGC can put a termination OOS and bring it back INS later.
Please see "F.4.1.2 ServiceChange Method Behaviour on Physical Terminations=
" of:
http://www.itu.int/rec/T-REC-H.248.1-200509-I/en


However, if the termination is OOS due to 904/906/907 reason codes then MGC=
=20
obviously can't bring it INS.

Regards
Raju

>=20
> Regards,
>=20
> Javi
>=20
> >
> > Regards, Christian
> >
> > On 10/12/2011 11:44 PM, Javi wrote:
> >> In a termination *with**a single stream*, which is the=20
> >> differencebetween?:
> >>
> >> (a) TerminationState{ServiceStates=3DOutOfService}
> >>
> >> (b) Media{ LocalControl { StreamMode=3DInactive } }
> >>
> >> Regards,
> >>
> >> Javi
> >>
> >>
> >> _______________________________________________
> >> Megaco mailing list
> >> Megaco@ietf.org
> >> https://www.ietf.org/mailman/listinfo/megaco
> > _______________________________________________
> > Megaco mailing list
> > Megaco@ietf.org
> > https://www.ietf.org/mailman/listinfo/megaco
> >
>=20
> _______________________________________________
> Megaco mailing list
> Megaco@ietf.org
> https://www.ietf.org/mailman/listinfo/megaco
> =

From Raju.Makaraju@alcatel-lucent.com  Mon Dec 12 15:09:17 2011
Return-Path: <Raju.Makaraju@alcatel-lucent.com>
X-Original-To: megaco@ietfa.amsl.com
Delivered-To: megaco@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A212A21F850B for <megaco@ietfa.amsl.com>; Mon, 12 Dec 2011 15:09:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.842
X-Spam-Level: 
X-Spam-Status: No, score=-4.842 tagged_above=-999 required=5 tests=[AWL=-0.943, BAYES_00=-2.599, J_CHICKENPOX_12=0.6, J_CHICKENPOX_15=0.6, J_CHICKENPOX_24=0.6, J_CHICKENPOX_25=0.6, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9DL8aSrLkIUa for <megaco@ietfa.amsl.com>; Mon, 12 Dec 2011 15:09:17 -0800 (PST)
Received: from ihemail1.lucent.com (ihemail1.lucent.com [135.245.0.33]) by ietfa.amsl.com (Postfix) with ESMTP id DA9A921F8500 for <megaco@ietf.org>; Mon, 12 Dec 2011 15:09:16 -0800 (PST)
Received: from usnavsmail2.ndc.alcatel-lucent.com (usnavsmail2.ndc.alcatel-lucent.com [135.3.39.10]) by ihemail1.lucent.com (8.13.8/IER-o) with ESMTP id pBCN9GDT005143 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 12 Dec 2011 17:09:16 -0600 (CST)
Received: from USNAVSXCHHUB01.ndc.alcatel-lucent.com (usnavsxchhub01.ndc.alcatel-lucent.com [135.3.39.110]) by usnavsmail2.ndc.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id pBCN9Fm5011443 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Mon, 12 Dec 2011 17:09:15 -0600
Received: from USNAVSXCHMBSD3.ndc.alcatel-lucent.com ([135.3.39.148]) by USNAVSXCHHUB01.ndc.alcatel-lucent.com ([135.3.39.110]) with mapi; Mon, 12 Dec 2011 17:09:15 -0600
From: "Makaraju, Maridi Raju (Raju)" <Raju.Makaraju@alcatel-lucent.com>
To: =?iso-8859-1?Q?Javi_Mu=F1oz?= <javi@trajano.us.es>, "megaco@ietf.org" <megaco@ietf.org>
Date: Mon, 12 Dec 2011 17:08:24 -0600
Thread-Topic: [Megaco] Allocation resources for a call
Thread-Index: Acy4vscUfPs+qUXzS46RQ3b351ZnWAAYz7mQ
Message-ID: <31939CE9629A7F46885A9F97CEA9BF577C79C704@USNAVSXCHMBSD3.ndc.alcatel-lucent.com>
References: <4EE358A5.2040408@trajano.us.es> <4EE5350C.2070109@nteczone.com> <4EE5E152.20107@trajano.us.es>
In-Reply-To: <4EE5E152.20107@trajano.us.es>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.33
X-Scanned-By: MIMEDefang 2.64 on 135.3.39.10
Subject: Re: [Megaco] Allocation resources for a call
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.1.12
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: Mon, 12 Dec 2011 23:09:17 -0000

Javi,

I would think in this case (iii) is more appropriate.=20
However...

> >> (iii) 1 termination with 1 session descriptions with=20
> >> ReserveValue=3Dtrue to allocate the resources:
> >>
> >> Phase A)
> >> LocalControl {
> >> ReserveValue =3D True},
> >> Local/Remote {
> >>     v=3D0
> >>     c=3DIN IP4 IP_A
> >>     m=3Daudio port_A  RTP/AVP codec_x  codec_y
> >> }
> >>
> >> Phase B)
> >> LocalControl {
> >> ReserveValue =3D True},
> >> Local/Remote {
> >>     v=3D0
> >>     c=3DIN IP4 IP_B
> >>     m=3Daudio port_B  RTP/AVP codec_y  codec_x
[Raju] You have to be careful with Local Descriptor (LD).
The ip+port in LD can only be selected by GW. So, changing
from IP_A to IP_B is not implicit.. MGC has to specify
a choose("$") wildcard in phase B so that it can select
a new local ip+port.
In phase C, again "$" has to be specified, but MG certainly
not obligated to give back Port_A.

If 2 sets of IP+ports are needed then you may want to consider:
- ReservedGroup - 2 groups
- OR multiple streams -2 streams

> >> }
> >>
> >> Phase C)
> >> Local/Remote {
> >>     v=3D0
> >>     c=3DIN IP4 IP_A
> >>     m=3Daudio port_A  RTP/AVP codec_x
> >> }
> >>


Regards
Raju


> -----Original Message-----
> From: megaco-bounces@ietf.org=20
> [mailto:megaco-bounces@ietf.org] On Behalf Of Javi Mu=F1oz
> Sent: Monday, December 12, 2011 5:11 AM
> To: megaco@ietf.org
> Subject: Re: [Megaco] Allocation resources for a call
>=20
> Christian,
>=20
> El 11/12/2011 23:56, Christian Groves escribi=F3:
> > HEllo Javi,
> >
> > I'm not sure what the issue is? This just sounds like a normal=20
> > transcoding case.
> > i.e. For Termination connection to equipment A set codec X, for the=20
> > Termination connected to equipment B set codec Y. The MG simply=20
> > transcodes the codec format when sending a A or B.
>=20
> The problem is that the connection with A and B is performed=20
> within the=20
> same call. Thus, in phase A, MG sends to equipment A with=20
> codec X, but=20
> also should allocate the resources needed for Phase B.
>=20
> Otherwise, the call can start and, to change to Phase B, the=20
> MG may not=20
> have the resources to communicate with equipment B with the codecY,=20
> needing to release the call. Thus, the objective is to prevent this=20
> happening, ensuring that once the call begins, MG will have=20
> reserved all=20
> resources required for that call.
>=20
> Javi
> >
> > Regards, Christian
> >
> > On 11/12/2011 12:03 AM, Javi wrote:
> >> I have a callwith the following 3 phases:
> >>
> >> A) Phase A: MG may carry media to a equipment A using the codec x.
> >>
> >> B) Phase B: MG may carry media to a equipment B using the codec y.
> >>
> >> C) Phase C: again, MG may carry media to the equipment A using the=20
> >> codec x.
> >>
> >>
> >> In that case, what is the most appropriate way to model=20
> the call on=20
> >> the gateway to ensure that once the call starts the=20
> gateway will have=20
> >> the necessary resources for all phases?
> >>
> >> (i) 2 terminations (in the same or different context?) using the=20
> >> property "StreamMode=3DInactive":
> >>
> >> * Termination 1 with:
> >>     v=3D0
> >>     c=3DIN IP4 IP_A
> >>     m=3Daudio port_A  RTP/AVP codec_x
> >>
> >> * Termination 2 with:
> >>     v=3D0
> >>     c=3DIN IP4 IP_B
> >>     m=3Daudio port_B  RTP/AVP codec_y
> >>
> >> In phase:
> >>     (A, C) Termination 1 with StreamMode=3DSendRecv;=20
> Termination 2 with=20
> >> StreamMode=3DInactive
> >>     (B) Termination 1 with StreamMode=3DInactive; Termination 2 with=20
> >> StreamMode=3DSendRecv
> >>
> >> =3D=3D=3D
> >>
> >> (ii) 1 termination with 2 session descriptions with=20
> ReserveGroup=3Dtrue:
> >>
> >> In Phase A:
> >> LocalControl {
> >> ReserveGroup =3D True},
> >> Local/Remote {
> >>     v=3D0
> >>     c=3DIN IP4 IP_A
> >>     m=3Daudio port_A  RTP/AVP codec_x
> >>     v=3D0
> >>     c=3DIN IP4 IP_B
> >>     m=3Daudio port_B  RTP/AVP codec_y
> >> }
> >>
> >> In Phase B:
> >> LocalControl {
> >> ReserveGroup =3D True},
> >> Local/Remote {
> >>     v=3D0
> >>     c=3DIN IP4 IP_B
> >>     m=3Daudio port_B  RTP/AVP codec_y
> >>     v=3D0
> >>     c=3DIN IP4 IP_A
> >>     m=3Daudio port_A  RTP/AVP codec_x
> >> }
> >>
> >> In Phase C:
> >> Local/Remote {
> >>     v=3D0
> >>     c=3DIN IP4 IP_A
> >>     m=3Daudio port_A  RTP/AVP codec_x
> >> }
> >>
> >> =3D=3D=3D
> >>
> >> (iii) 1 termination with 1 session descriptions with=20
> >> ReserveValue=3Dtrue to allocate the resources:
> >>
> >> Phase A)
> >> LocalControl {
> >> ReserveValue =3D True},
> >> Local/Remote {
> >>     v=3D0
> >>     c=3DIN IP4 IP_A
> >>     m=3Daudio port_A  RTP/AVP codec_x  codec_y
> >> }
> >>
> >> Phase B)
> >> LocalControl {
> >> ReserveValue =3D True},
> >> Local/Remote {
> >>     v=3D0
> >>     c=3DIN IP4 IP_B
> >>     m=3Daudio port_B  RTP/AVP codec_y  codec_x
> >> }
> >>
> >> Phase C)
> >> Local/Remote {
> >>     v=3D0
> >>     c=3DIN IP4 IP_A
> >>     m=3Daudio port_A  RTP/AVP codec_x
> >> }
> >>
> >>
> >>
> >> Regards,
> >>
> >> Javi
> >>
> >> _______________________________________________
> >> Megaco mailing list
> >> Megaco@ietf.org
> >> https://www.ietf.org/mailman/listinfo/megaco
> >>
> > _______________________________________________
> > Megaco mailing list
> > Megaco@ietf.org
> > https://www.ietf.org/mailman/listinfo/megaco
> >
>=20
> _______________________________________________
> Megaco mailing list
> Megaco@ietf.org
> https://www.ietf.org/mailman/listinfo/megaco
> =

From Christian.Groves@nteczone.com  Mon Dec 12 15:21:50 2011
Return-Path: <Christian.Groves@nteczone.com>
X-Original-To: megaco@ietfa.amsl.com
Delivered-To: megaco@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D233221F85FF for <megaco@ietfa.amsl.com>; Mon, 12 Dec 2011 15:21:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.299
X-Spam-Level: 
X-Spam-Status: No, score=-2.299 tagged_above=-999 required=5 tests=[AWL=0.300,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id B3xs8duERym5 for <megaco@ietfa.amsl.com>; Mon, 12 Dec 2011 15:21:50 -0800 (PST)
Received: from ipmail04.adl6.internode.on.net (ipmail04.adl6.internode.on.net [150.101.137.141]) by ietfa.amsl.com (Postfix) with ESMTP id B329A21F8AAC for <megaco@ietf.org>; Mon, 12 Dec 2011 15:21:49 -0800 (PST)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AjEAAH6L5k520XPt/2dsb2JhbAAMN5pCkz0BAQEEAQEBLwEFGxsKDQQLEQQBAQEJFggHCQMCAQIBFR8JCBMGAgEBiAy1N4ttBKcs
Received: from ppp118-209-115-237.lns20.mel4.internode.on.net (HELO [127.0.0.1]) ([118.209.115.237]) by ipmail04.adl6.internode.on.net with ESMTP; 13 Dec 2011 09:51:47 +1030
Message-ID: <4EE68C84.6090507@nteczone.com>
Date: Tue, 13 Dec 2011 10:21:40 +1100
From: Christian Groves <Christian.Groves@nteczone.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:8.0) Gecko/20111105 Thunderbird/8.0
MIME-Version: 1.0
To: megaco@ietf.org
References: <4ED518F6.4020201@trajano.us.es> <5F7BCCF5541B7444830A2288ABBEBC962161900622@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com> <4ED604A0.2000402@trajano.us.es>	<4ED6640A.9030508@trajano.us.es> <5F7BCCF5541B7444830A2288ABBEBC962161900780@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com> <4ED66B87.7050907@trajano.us.es>	<4ED6767D.7070109@trajano.us.es> <703C56B521385C4C9091299BE82357B7EF26034C@USNAVSXCHMBSA2.ndc.alcatel-lucent.com> <4ED750D6.9000608@trajano.us.es> <703C56B521385C4C9091299BE82357B7EF2605BE@USNAVSXCHMBSA2.ndc.alcatel-lucent.com> <4ED7B036.4000103@trajano.us.es> <703C56B521385C4C9091299BE82357B7EF2607C5@USNAVSXCHMBSA2.ndc.alcatel-lucent.com> <4ED7CAA1.3020902@trajano.us.es> <31939CE9629A7F46885A9F97CEA9BF577BFE78B4@USNAVSXCHMBSD3.ndc.alcatel-lucent.com> <4EE5E619.4050506@trajano.us.es> <4EE63CA2.6040000@trajano.us.es> <31939CE9629A7F46885A9F97CEA9BF577C79C6F2@USNAVSXCHMBSD3.ndc.alcatel-lucent.com>
In-Reply-To: <31939CE9629A7F46885A9F97CEA9BF577C79C6F2@USNAVSXCHMBSD3.ndc.alcatel-lucent.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Subject: Re: [Megaco] Selection of media (m=) at MG
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.1.12
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: Mon, 12 Dec 2011 23:21:50 -0000

Hello Javi and Raju,

The sending of signals is defined in H.248.1 clause 7.1.11. i.e. 
"Signals are defined as proceeding from the termination towards the 
exterior of the context unless otherwise specified."

Tones/Announcements are just one type of signal.

With regards to "disconnected oneway", there isn't any change in the 
Streammode or Topology descriptor as a result of a signal.

Regards, Christian

On 13/12/2011 9:42 AM, Makaraju, Maridi Raju (Raju) wrote:
> Javi,
>
>> Raju,
>>> In fact, when a signal (tone/annc) is played on one termination
>>> (signal going outside of the context),
>>> the termination is temporarily "disconnected oneway" (so it won't
>>> receive any data, but can send) from
>>> the other terminations (as if the termination has "oneway"
>> topology to
>>> others).
>> A more.
>>
>> What document or Recommendation defines exactly this behavior of a
>> termination for sending tones / announcements?
> [Raju] I could not find any explicit mention of such procedure in H.248.1.
> As I explained in other mail, I believe it is implicit by "playing the
> signal (no mixing)" we just want the signal to be delivered to the
> termination (if the signal is of nature which actually sends, like tone/annc,
> data to the termination as opposed to some signals, like ipnapt/latch signal which
> won't send any data to the termination).
>
> You may search MEGACO lists or implementers guide to find relevant discussions.
> http://www.itu.int/rec/T-REC-H.Imp248-201007-I/en
>
> Regards
> Raju
>
>> Regards,
>>
>> Javi
>>
>>>>> -----Original Message-----
>>>>> From: megaco-bounces@ietf.org
>>>>> [mailto:megaco-bounces@ietf.org] On Behalf Of Javi Muñoz
>>>>> Sent: Thursday, December 01, 2011 12:43 PM
>>>>> To: megaco@ietf.org
>>>>> Cc: Bhattacharjee, Arindam (Arindam)
>>>>> Subject: Re: [Megaco] Selection of media (m=) at MG
>>>>>
>>>>> Arindam,
>>>>>
>>>>>> You can use another option: have reserve value on and use
>>>>> both g711 and Clearmode on both remote and local SDP and MG
>>>>> will send in g711 only because that has higher preference
>>>>> when G711 appears before CLearMode codec in the list as follows:
>>>>>>     m=audio<puerto>     RTP/AVP 0 [8]<PT_dinámico>
>>>>>>     a=rtpmap:<PT_dinámico>     CLEARMODE/8000
>>>>> When the Remote descriptor has several audio codecs in
>> the line "m=":
>>>>>     m=audio<puerto>     RTP/AVP 0 [8]<PT_dinámico>
>>>>>
>>>>>
>>>>> I understand that:
>>>>>
>>>>> 1º First codec in the line is used if it is possible.
>>>>>
>>>>> 2º In case that codec may not be used (for an error, for
>>>>> example), the
>>>>> second codec would be tried (I understand this is the
>> reaseon why the
>>>>> Remote descriptor may have several audio codecs in the
>> same line "m=).
>>>>>
>>>>> If it is so, and we use:
>>>>>
>>>>>     m=audio<puerto>     RTP/AVP 0 [8]<PT_dinámico>
>>>>>
>>>>>
>>>>> What would happen if when MG needs to send the tone/ann., the
>>>>> codecs "0"
>>>>> and "8" may not be used?. MG would try to send the
>> tone/ann. to the
>>>>> terminal using CLEARMODE, when terminal is not ready to
>> receive that.
>>>>> Javi
>>>>> _______________________________________________
>>>>> Megaco mailing list
>>>>> Megaco@ietf.org
>>>>> https://www.ietf.org/mailman/listinfo/megaco
>>>>>
>>> _______________________________________________
>>> Megaco mailing list
>>> Megaco@ietf.org
>>> https://www.ietf.org/mailman/listinfo/megaco
>>>
>>
> _______________________________________________
> Megaco mailing list
> Megaco@ietf.org
> https://www.ietf.org/mailman/listinfo/megaco
>

From Christian.Groves@nteczone.com  Mon Dec 12 15:23:15 2011
Return-Path: <Christian.Groves@nteczone.com>
X-Original-To: megaco@ietfa.amsl.com
Delivered-To: megaco@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D69A021F8ACE for <megaco@ietfa.amsl.com>; Mon, 12 Dec 2011 15:23:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.399
X-Spam-Level: 
X-Spam-Status: No, score=-2.399 tagged_above=-999 required=5 tests=[AWL=0.200,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pXqP2XpE1xIn for <megaco@ietfa.amsl.com>; Mon, 12 Dec 2011 15:23:14 -0800 (PST)
Received: from ipmail04.adl6.internode.on.net (ipmail04.adl6.internode.on.net [150.101.137.141]) by ietfa.amsl.com (Postfix) with ESMTP id 7A2D021F85A7 for <megaco@ietf.org>; Mon, 12 Dec 2011 15:23:14 -0800 (PST)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: ApMBAH6L5k520XPt/2dsb2JhbAAMN61/AQEBBAEBATUbGwsMBAsRBAEBAQkeBw8CFh8JCAYNAQUCAQGIDLUzBIttBKcs
Received: from ppp118-209-115-237.lns20.mel4.internode.on.net (HELO [127.0.0.1]) ([118.209.115.237]) by ipmail04.adl6.internode.on.net with ESMTP; 13 Dec 2011 09:53:11 +1030
Message-ID: <4EE68CDB.402@nteczone.com>
Date: Tue, 13 Dec 2011 10:23:07 +1100
From: Christian Groves <Christian.Groves@nteczone.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:8.0) Gecko/20111105 Thunderbird/8.0
MIME-Version: 1.0
To: Raphael Tryster <Raphael.Tryster@Teledata-Networks.com>
References: <4EE3543D.8000301@trajano.us.es> <4EE533ED.8030006@nteczone.com> <D6FAAE89E48C5B488B41BEBBDCD746CD07AB2D41@tndcmail.Teledata.Local>
In-Reply-To: <D6FAAE89E48C5B488B41BEBBDCD746CD07AB2D41@tndcmail.Teledata.Local>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: megaco@ietf.org
Subject: Re: [Megaco] OutOfService vs Inactive
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.1.12
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: Mon, 12 Dec 2011 23:23:16 -0000

Hello Raphael,

I try lots of things doesn't mean I'm always successful :-). Guess its 
no different for MGCs...

Regards, Christian

On 12/12/2011 4:54 PM, Raphael Tryster wrote:
> "the MGC can't change OutOfService to InService"
>
> But some MGCs sure as hell try.
>
> -----Original Message-----
> From: megaco-bounces@ietf.org [mailto:megaco-bounces@ietf.org] On Behalf
> Of Christian Groves
> Sent: Monday, 12 December 2011 12:51 AM
> To: megaco@ietf.org
> Subject: Re: [Megaco] OutOfService vs Inactive
>
> Hello Javi,
>
> ServiceState and Streammode are fundamentally different things.
> Streammode is related to activity on the bearer. ServiceState is related
>
> to MG internal "readiness". Also the Streammode can be controlled by the
>
> MGC. i.e. it can change Inactive to Send/Receive.
> ServiceState is largely controlled by the MG. i.e. the MGC can't change
> OutOfService to InService.
>
> Regards, Christian
>
> On 10/12/2011 11:44 PM, Javi wrote:
>> In a termination *with**a single stream*, which is the
> differencebetween?:
>> (a) TerminationState{ServiceStates=OutOfService}
>>
>> (b) Media{ LocalControl { StreamMode=Inactive } }
>>
>> Regards,
>>
>> Javi
>>
>>
>> _______________________________________________
>> Megaco mailing list
>> Megaco@ietf.org
>> https://www.ietf.org/mailman/listinfo/megaco
> _______________________________________________
> Megaco mailing list
> Megaco@ietf.org
> https://www.ietf.org/mailman/listinfo/megaco
>
> NOTICE: This email and any files transmitted with it are Enablence and Teledata-Networks confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the sender. This message contains Enablence and Teledata-Networks confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. If you are not the intended recipient you are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited.
>
>
>

From Christian.Groves@nteczone.com  Mon Dec 12 15:38:13 2011
Return-Path: <Christian.Groves@nteczone.com>
X-Original-To: megaco@ietfa.amsl.com
Delivered-To: megaco@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8ADA111E8080 for <megaco@ietfa.amsl.com>; Mon, 12 Dec 2011 15:38:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.449
X-Spam-Level: 
X-Spam-Status: No, score=-2.449 tagged_above=-999 required=5 tests=[AWL=0.150,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 09Y6FJibrQed for <megaco@ietfa.amsl.com>; Mon, 12 Dec 2011 15:38:12 -0800 (PST)
Received: from ipmail04.adl6.internode.on.net (ipmail04.adl6.internode.on.net [150.101.137.141]) by ietfa.amsl.com (Postfix) with ESMTP id 53E7411E807F for <megaco@ietf.org>; Mon, 12 Dec 2011 15:38:12 -0800 (PST)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: ApMBAAyP5k520XPt/2dsb2JhbAAMN61/AQEBBAEBATUbGwoRCxgJFg8JAwIBAgEVMBMGAgEBiAy1O4hTgxoEpyw
Received: from ppp118-209-115-237.lns20.mel4.internode.on.net (HELO [127.0.0.1]) ([118.209.115.237]) by ipmail04.adl6.internode.on.net with ESMTP; 13 Dec 2011 10:08:11 +1030
Message-ID: <4EE6905E.6060406@nteczone.com>
Date: Tue, 13 Dec 2011 10:38:06 +1100
From: Christian Groves <Christian.Groves@nteczone.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:8.0) Gecko/20111105 Thunderbird/8.0
MIME-Version: 1.0
To: megaco@ietf.org
References: <4EE3543D.8000301@trajano.us.es> <4EE533ED.8030006@nteczone.com> <4EE5DEA0.7040402@trajano.us.es> <31939CE9629A7F46885A9F97CEA9BF577C79C6FF@USNAVSXCHMBSD3.ndc.alcatel-lucent.com>
In-Reply-To: <31939CE9629A7F46885A9F97CEA9BF577C79C6FF@USNAVSXCHMBSD3.ndc.alcatel-lucent.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [Megaco] OutOfService vs Inactive
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.1.12
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: Mon, 12 Dec 2011 23:38:13 -0000

Hello Javi and Raju,

I was referring to the example provided by Javi, i.e.
(a) TerminationState{ServiceStates=OutOfService}

The MGC can't use the TerminationState descriptor to change the 
servicestate.

The MGC can use Servicechange to change the ServiceState.

Regards, Christian

On 13/12/2011 9:59 AM, Makaraju, Maridi Raju (Raju) wrote:
> Javi,
>
>> Christian,
>>> the MGC can't change OutOfService to InService.
>> When MGC  sends to MG a serviceChange command with method Forced or
>> Graceful and reason 905 (Out Of Service), MGC requests to MG
>> to put out
>> of service the indicated terminations. Is not it?
> [Raju]
> Right. There are several reasons why a termination can be out of service(OOS).
> Take a look at "H.248.8 : Gateway control protocol: Error code and service change reason description"
> http://www.itu.int/rec/T-REC-H.248.8-200708-I/en
>
> Following are some of the relevant ones:
>
>          904 Termination malfunctioning
>          905 Termination taken out of service
>          906 Loss of lower layer connectivity (e.g. downstream sync)
>          907 Transmission Failure
>
> MGC can put a termination OOS and bring it back INS later.
> Please see "F.4.1.2 ServiceChange Method Behaviour on Physical Terminations" of:
> http://www.itu.int/rec/T-REC-H.248.1-200509-I/en
>
>
> However, if the termination is OOS due to 904/906/907 reason codes then MGC
> obviously can't bring it INS.
>
> Regards
> Raju
>
>> Regards,
>>
>> Javi
>>
>>> Regards, Christian
>>>
>>> On 10/12/2011 11:44 PM, Javi wrote:
>>>> In a termination *with**a single stream*, which is the
>>>> differencebetween?:
>>>>
>>>> (a) TerminationState{ServiceStates=OutOfService}
>>>>
>>>> (b) Media{ LocalControl { StreamMode=Inactive } }
>>>>
>>>> Regards,
>>>>
>>>> Javi
>>>>
>>>>
>>>> _______________________________________________
>>>> Megaco mailing list
>>>> Megaco@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/megaco
>>> _______________________________________________
>>> Megaco mailing list
>>> Megaco@ietf.org
>>> https://www.ietf.org/mailman/listinfo/megaco
>>>
>> _______________________________________________
>> Megaco mailing list
>> Megaco@ietf.org
>> https://www.ietf.org/mailman/listinfo/megaco
>>
> _______________________________________________
> Megaco mailing list
> Megaco@ietf.org
> https://www.ietf.org/mailman/listinfo/megaco
>

From Raju.Makaraju@alcatel-lucent.com  Mon Dec 12 15:41:31 2011
Return-Path: <Raju.Makaraju@alcatel-lucent.com>
X-Original-To: megaco@ietfa.amsl.com
Delivered-To: megaco@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AA8BB11E808A for <megaco@ietfa.amsl.com>; Mon, 12 Dec 2011 15:41:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.074
X-Spam-Level: 
X-Spam-Status: No, score=-6.074 tagged_above=-999 required=5 tests=[AWL=0.525,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ctpn-TaBb2Rz for <megaco@ietfa.amsl.com>; Mon, 12 Dec 2011 15:41:30 -0800 (PST)
Received: from ihemail3.lucent.com (ihemail3.lucent.com [135.245.0.37]) by ietfa.amsl.com (Postfix) with ESMTP id BBFEE11E808B for <megaco@ietf.org>; Mon, 12 Dec 2011 15:41:30 -0800 (PST)
Received: from usnavsmail4.ndc.alcatel-lucent.com (usnavsmail4.ndc.alcatel-lucent.com [135.3.39.12]) by ihemail3.lucent.com (8.13.8/IER-o) with ESMTP id pBCNfTT9000231 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 12 Dec 2011 17:41:29 -0600 (CST)
Received: from USNAVSXCHHUB01.ndc.alcatel-lucent.com (usnavsxchhub01.ndc.alcatel-lucent.com [135.3.39.110]) by usnavsmail4.ndc.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id pBCNfSQC020505 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Mon, 12 Dec 2011 17:41:28 -0600
Received: from USNAVSXCHMBSD3.ndc.alcatel-lucent.com ([135.3.39.148]) by USNAVSXCHHUB01.ndc.alcatel-lucent.com ([135.3.39.110]) with mapi; Mon, 12 Dec 2011 17:41:28 -0600
From: "Makaraju, Maridi Raju (Raju)" <Raju.Makaraju@alcatel-lucent.com>
To: Christian Groves <Christian.Groves@nteczone.com>, Raphael Tryster <Raphael.Tryster@Teledata-Networks.com>
Date: Mon, 12 Dec 2011 17:41:24 -0600
Thread-Topic: [Megaco] OutOfService vs Inactive
Thread-Index: Acy5JQm/MVkO30iRT9KCK/a0Z+fDhgAAbBzw
Message-ID: <31939CE9629A7F46885A9F97CEA9BF577C79C70C@USNAVSXCHMBSD3.ndc.alcatel-lucent.com>
References: <4EE3543D.8000301@trajano.us.es> <4EE533ED.8030006@nteczone.com> <D6FAAE89E48C5B488B41BEBBDCD746CD07AB2D41@tndcmail.Teledata.Local> <4EE68CDB.402@nteczone.com>
In-Reply-To: <4EE68CDB.402@nteczone.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.37
X-Scanned-By: MIMEDefang 2.64 on 135.3.39.12
Cc: "megaco@ietf.org" <megaco@ietf.org>
Subject: Re: [Megaco] OutOfService vs Inactive
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.1.12
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: Mon, 12 Dec 2011 23:41:31 -0000

Christian, Raphael,
=20
> > "the MGC can't change OutOfService to InService"
[Raju] If MGC puts a termination OOS administratively (905 Termination take=
n out of service)
then it can put it "inService".=20
Yes, it is NOT guaranteed that the termination will actually come INS as
the termination could be having hardware related issue and in such a case M=
G would have
notified MGC with any of the following ServiceChange reason codes.

        904 Termination malfunctioning
        906 Loss of lower layer connectivity (e.g. downstream sync)
        907 Transmission Failure

Text in "F.4.1.2 ServiceChange Method Behaviour on Physical Terminations" o=
f H.248.1
clearly supports MGC putting termination OOS and INS.
http://www.itu.int/rec/T-REC-H.248.1-200509-I/en

Regards
Raju

> -----Original Message-----
> From: megaco-bounces@ietf.org=20
> [mailto:megaco-bounces@ietf.org] On Behalf Of Christian Groves
> Sent: Monday, December 12, 2011 5:23 PM
> To: Raphael Tryster
> Cc: megaco@ietf.org
> Subject: Re: [Megaco] OutOfService vs Inactive
>=20
> Hello Raphael,
>=20
> I try lots of things doesn't mean I'm always successful :-).=20
> Guess its=20
> no different for MGCs...
>=20
> Regards, Christian
>=20
> On 12/12/2011 4:54 PM, Raphael Tryster wrote:
> > "the MGC can't change OutOfService to InService"
> >
> > But some MGCs sure as hell try.
> >
> > -----Original Message-----
> > From: megaco-bounces@ietf.org=20
> [mailto:megaco-bounces@ietf.org] On Behalf
> > Of Christian Groves
> > Sent: Monday, 12 December 2011 12:51 AM
> > To: megaco@ietf.org
> > Subject: Re: [Megaco] OutOfService vs Inactive
> >
> > Hello Javi,
> >
> > ServiceState and Streammode are fundamentally different things.
> > Streammode is related to activity on the bearer.=20
> ServiceState is related
> >
> > to MG internal "readiness". Also the Streammode can be=20
> controlled by the
> >
> > MGC. i.e. it can change Inactive to Send/Receive.
> > ServiceState is largely controlled by the MG. i.e. the MGC=20
> can't change
> > OutOfService to InService.
> >
> > Regards, Christian
> >
> > On 10/12/2011 11:44 PM, Javi wrote:
> >> In a termination *with**a single stream*, which is the
> > differencebetween?:
> >> (a) TerminationState{ServiceStates=3DOutOfService}
> >>
> >> (b) Media{ LocalControl { StreamMode=3DInactive } }
> >>
> >> Regards,
> >>
> >> Javi
> >>
> >>
> >> _______________________________________________
> >> Megaco mailing list
> >> Megaco@ietf.org
> >> https://www.ietf.org/mailman/listinfo/megaco
> > _______________________________________________
> > Megaco mailing list
> > Megaco@ietf.org
> > https://www.ietf.org/mailman/listinfo/megaco
> >
> > NOTICE: This email and any files transmitted with it are=20
> Enablence and Teledata-Networks confidential and intended=20
> solely for the use of the individual or entity to whom they=20
> are addressed. If you have received this email in error=20
> please notify the sender. This message contains Enablence and=20
> Teledata-Networks confidential information and is intended=20
> only for the individual named. If you are not the named=20
> addressee you should not disseminate, distribute or copy this=20
> e-mail. Please notify the sender immediately by e-mail if you=20
> have received this e-mail by mistake and delete this e-mail=20
> from your system. If you are not the intended recipient you=20
> are notified that disclosing, copying, distributing or taking=20
> any action in reliance on the contents of this information is=20
> strictly prohibited.
> >
> >
> >
> _______________________________________________
> Megaco mailing list
> Megaco@ietf.org
> https://www.ietf.org/mailman/listinfo/megaco
> =

From bill.wu@huawei.com  Mon Dec 12 17:55:36 2011
Return-Path: <bill.wu@huawei.com>
X-Original-To: megaco@ietfa.amsl.com
Delivered-To: megaco@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D28FE21F8A4B; Mon, 12 Dec 2011 17:55:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.726
X-Spam-Level: 
X-Spam-Status: No, score=-5.726 tagged_above=-999 required=5 tests=[AWL=-0.327, BAYES_00=-2.599, J_CHICKENPOX_14=0.6, J_CHICKENPOX_74=0.6, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1atruK9p+hQh; Mon, 12 Dec 2011 17:55:34 -0800 (PST)
Received: from szxga03-in.huawei.com (szxga03-in.huawei.com [119.145.14.66]) by ietfa.amsl.com (Postfix) with ESMTP id 0863121F899D; Mon, 12 Dec 2011 17:55:34 -0800 (PST)
Received: from huawei.com (szxga03-in [172.24.2.9]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LW400034DCIG7@szxga03-in.huawei.com>; Tue, 13 Dec 2011 09:55:30 +0800 (CST)
Received: from szxrg02-dlp.huawei.com ([172.24.2.119]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LW40064FDCB4G@szxga03-in.huawei.com>; Tue, 13 Dec 2011 09:55:30 +0800 (CST)
Received: from szxeml208-edg.china.huawei.com ([172.24.2.119]) by szxrg02-dlp.huawei.com (MOS 4.1.9-GA)	with ESMTP id AFQ00493; Tue, 13 Dec 2011 09:55:18 +0800
Received: from SZXEML418-HUB.china.huawei.com (10.82.67.157) by szxeml208-edg.china.huawei.com (172.24.2.60) with Microsoft SMTP Server (TLS) id 14.1.323.3; Tue, 13 Dec 2011 09:55:16 +0800
Received: from w53375q (10.138.41.130) by szxeml418-hub.china.huawei.com (10.82.67.157) with Microsoft SMTP Server (TLS) id 14.1.323.3; Tue, 13 Dec 2011 09:55:18 +0800
Date: Tue, 13 Dec 2011 09:55:17 +0800
From: Qin Wu <bill.wu@huawei.com>
X-Originating-IP: [10.138.41.130]
To: "Schwarz, Albrecht (Albrecht)" <albrecht.schwarz@alcatel-lucent.com>, avt@ietf.org
Message-id: <F0B2A75386B84E639161CACF1AD401B0@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.6109
X-Mailer: Microsoft Outlook Express 6.00.2900.5931
Content-type: text/plain; charset=ISO-8859-1
Content-transfer-encoding: 7BIT
X-Priority: 3
X-MSMail-priority: Normal
X-CFilter-Loop: Reflected
References: <20111129075613.12419.4377.idtracker@ietfa.amsl.com> <5F7BCCF5541B7444830A2288ABBEBC96216190051A@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com> <EAC481B4D8034C38AC54E1217F8D875D@china.huawei.com> <5F7BCCF5541B7444830A2288ABBEBC96216190077F@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com> <B527BAFA038842A8939A8C2D558074CD@china.huawei.com> <5F7BCCF5541B7444830A2288ABBEBC962161900908@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com> <9FF9B04A84E64AD7ABCCC4F2ACC1E19A@china.huawei.com> <5F7BCCF5541B7444830A2288ABBEBC9621620F4AF5@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com> <D44A4820E0D24DD79F6F5A4B7507D0D6@china.huawei.com> <5F7BCCF5541B7444830A2288ABBEBC9621620F4ED2@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com> <71112008FBA94D35B07FA6B4916075B6@china.huawei.com> <5F7BCCF5541B7444830A2288ABBEBC9621620F5258@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com> <6C618D1EA52146A781429C6B08C4A4FC@china.huawei.com> <5F7BCCF5541B7444830A2288ABBEBC9621620F5330@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com>
Cc: megaco@ietf.org
Subject: Re: [Megaco] [AVTCORE] Types of monitoring architectures; RE:  I-D Action: draft-ietf-avtcore-monarch-08.txt
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.1.12
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: Tue, 13 Dec 2011 01:55:37 -0000

I am just a little doubt whether mapping RTP component into specific network node is the scope of MONARCH draft
since it was agreed early that the focus of monarch draft is to provide guideline on how to define XRBlock.
But I am fine if nobody has objection to your proposal, i.e., wide scope a little bit to talk about how to map RTP 
monitoring architecture to the network nodes.

Regards!
-Qin
----- Original Message ----- 
From: "Schwarz, Albrecht (Albrecht)" <albrecht.schwarz@alcatel-lucent.com>
To: "Qin Wu" <bill.wu@huawei.com>; <avt@ietf.org>
Cc: <megaco@ietf.org>
Sent: Monday, December 12, 2011 6:33 PM
Subject: RE: [AVTCORE] Types of monitoring architectures; RE: I-D Action: draft-ietf-avtcore-monarch-08.txt


Hi Qin,

I'm very aware about all that.
It looks like that you are now agreeing that QoE measurements are CONDITIONAL ("you got a number of IF statements, there might be even more ...").

MONARCH is not talking about such conditions, thus some readers may got the impression that the metrics related to RTP traffic are UNCONDITIONAL (which is not true as you confirmed).

If you go back to my very first email: I did just propose to indicate the conditional aspect. Don't understand why such kind of valuable info would be not in scope of MONARCH. Hm?

Regards,
Albrecht

PS
I did use the notion of a control plane agnostic "RTP-to-PSTN gateway". You did indicate control plane specific gateway types like SIP-to-PSTN or SIP-to-H.323. Now issue to use such signalling protocol specific examples, but it doesn't change the underlying issue.
The SIP side reporting capability based on RFC 6035 allows to report the outlined measurements, but the RFC itself does not specify whether the reported information is meaningful (which is OK because this is not subject of a reporting interface spec, it is rather subject of a network monitoring doc like MONARCH).
QoE measurements would be conditional in both gateway types (because such a gateway is NOT a user device despite the fact of an embedded SIP user agent entity).
Actually I would even question here the condition of "customer knows the original content" in many real network scenarios.



> -----Original Message-----
> From: Qin Wu [mailto:bill.wu@huawei.com]
> Sent: Montag, 12. Dezember 2011 05:05
> To: Schwarz, Albrecht (Albrecht); avt@ietf.org
> Cc: megaco@ietf.org
> Subject: Re: [AVTCORE] Types of monitoring architectures; RE:
> I-D Action: draft-ietf-avtcore-monarch-08.txt
>
> Hi, Albrecht:
> My understanding to QoE measurment is:
> The factors that influence the QoE metric include encoding
> system, transport network, access network,home network and end device.
> If the customer(e.g., network operator) doesn't know the
> original content, the QoE metric should be usually measured
> at the user device.
> If the customer knows the original content, the QoE metric
> can be measured either in the network or at the user device.
> Given the growing popularity of connected devices, these
> devices may have different capability corresponding to CPU
> load, processing overhead, storage, batteries.
> If the cusomer want to measure QoE without considering
> connected devices with various capability , the QoE metric
> can be measured at the point between access network and home network.
>
> Regarding the monitoring scenario you mentioned, I am not
> familiar with such scenario with RTP-to-PSTN gateway deployed.
> But I am aware that there are scenarios with SIP to PSTN
> gateway or SIP to H.323 gateway widely deployed,  RFC6035
> defines a new SIP event package, vq-rtcpxr that enable the
> collection and  reporting of metrics that measure quality for
> RTP sessions. In such cases, RTCP XR VOIP metric with QoE
> metric included is measured at the user device and mapped
> into the equivalent SIP vq-rtcpxr parameter since SIP session
> call is established end to end and RTP media stream is
> exchanged directly between one endpoint and the other endpoint.
>
> Regards!
> -Qin
> ----- Original Message -----
> From: "Schwarz, Albrecht (Albrecht)"
> <albrecht.schwarz@alcatel-lucent.com>
> To: "Qin Wu" <bill.wu@huawei.com>; <avt@ietf.org>
> Cc: <megaco@ietf.org>
> Sent: Saturday, December 10, 2011 12:01 AM
> Subject: RE: [AVTCORE] Types of monitoring architectures; RE:
> I-D Action: draft-ietf-avtcore-monarch-08.txt
>
>
> How do you explain to a network operator the value of QoE
> measurements by an RTP receiver / RTP monitor component
> located in an RTP-to-PSTN gateway?
>
> This would be a monitoring scenario inline with MONARCH, but
> with valueless QoE results, right?
>
>
> > -----Original Message-----
> > From: Qin Wu [mailto:bill.wu@huawei.com]
> > Sent: Donnerstag, 8. Dezember 2011 03:26
> > To: Schwarz, Albrecht (Albrecht); avt@ietf.org
> > Cc: megaco@ietf.org
> > Subject: Re: [AVTCORE] Types of monitoring architectures; RE:
> > I-D Action: draft-ietf-avtcore-monarch-08.txt
> >
> > You reiterate what you propose for physical entities in the
> > early email.
> > I am still not convicing with that.
> >
> > Since we have RTP components like RTP end system, RTP mixer,
> > RTP media translator, RTP transport translator, RTP monitor
> > specified in RFC3550 can be built into these component as a
> > application. also monitor can be disjointed from these RTP
> > components as a third party monitor. why we need to specify
> > how to map RTP end system into user equipment, RTP translator
> > or RTP mixer can be mapped into RTP-PSTN gateway, or IP to IP
> > border gateway since we have already mapped monitor into
> > different RTP components.
> > How many PE types you can enumerate? why they should be scope
> > of RTP monitoring architecture?
> >
> > Also as specified in MONARCH draft, we have end sytem
> > metrics, transport level metric, transport level metric, they
> > can be measured and collected from the different RTP
> > comoponents specified in RFC3550, RFC5117. Apparently end
> > system metric can only be collected from RTP end system.
> > transport metric is collected from any RTP system in the RTP
> > monitoring architecture, regarding application level metric,
> > apparently they should be measured at the application layer
> > and can not be collected from RTP transport translator, Also
> > RTP transport translator is still a functional entity rather
> > than a physical entity. I am not convincing with what you
> > said about "contradiction", "lead to possible wrong expectations".
> >
> > Regards!
> > -Qin
> > ----- Original Message -----
> > From: "Schwarz, Albrecht (Albrecht)"
> > <albrecht.schwarz@alcatel-lucent.com>
> > To: "Qin Wu" <bill.wu@huawei.com>; <avt@ietf.org>
> > Cc: <megaco@ietf.org>
> > Sent: Thursday, December 08, 2011 12:24 AM
> > Subject: RE: [AVTCORE] Types of monitoring architectures; RE:
> > I-D Action: draft-ietf-avtcore-monarch-08.txt
> >
> >
> > Qin,
> > that's NOT the point.
> >
> > All RFC 3550 and RFC 5117 RTP components are FUNCTIONAL
> ENTITIES (FE).
> > e.g.,
> > - the RTP Monitor or RTP receiver FE may be located in
> > different PHYSICAL ENTITIES (PE), e.g.
> >         a1) a user equipment
> >         a2) a RTP-to-PSTN gateway
> >         a3) an IP-to-IP session border gateway (in a
> > back-to-back RTP endsystem topology)
> >         a3) ...
> >
> > - the RTP Monitor may be associated to an RTP transport
> translator ...
> >         b1) an IP-to-IP session border gateway
> >
> > The "RTP monitoring architecture" is IMPACTED by each
> > functional-to-physical mapping because e.g.
> > * QoE related metrics are questionable in case of a2
> > ("despite the fact of a RTP receiver function")
> > * application level metrics at the location of a RTP
> > transport translator are a contradiction in itself
> > * ...
> >
> > Again, it's not really changing the MONARCH draft because in
> > the very majority of scenarios it is correct. However, there
> > are few cases where the MONARCH description would be "too
> > high level", "not fully correct", "lead to possible wrong
> > expectations", ...
> >
> > Regards,
> > Albrecht
> >
> >
> >
> > > -----Original Message-----
> > > From: Qin Wu [mailto:bill.wu@huawei.com]
> > > Sent: Dienstag, 6. Dezember 2011 07:13
> > > To: Schwarz, Albrecht (Albrecht); avt@ietf.org
> > > Cc: megaco@ietf.org
> > > Subject: Re: [AVTCORE] Types of monitoring architectures; RE:
> > > I-D Action: draft-ietf-avtcore-monarch-08.txt
> > >
> > > If you talk about existing RFC5117 RTP topology components,
> > > this has already been covered by the current version of
> > > draft-ietf-avtcore-monarch.
> > > In most cases, an RTP system using RTCP XR is architecturally
> > > no different from an RTP system which does not use RTCP XR.
> > >
> > > Regards!
> > > -Qin
> > > ----- Original Message -----
> > > From: "Schwarz, Albrecht (Albrecht)"
> > > <albrecht.schwarz@alcatel-lucent.com>
> > > To: "Qin Wu" <bill.wu@huawei.com>; <avt@ietf.org>
> > > Cc: <megaco@ietf.org>
> > > Sent: Monday, December 05, 2011 10:48 PM
> > > Subject: RE: [AVTCORE] Types of monitoring architectures; RE:
> > > I-D Action: draft-ietf-avtcore-monarch-08.txt
> > >
> > >
> > > Hello Qin,
> > >
> > > to 1) Physical monitoring architecture
> > > Of course consideration of generic physical entities (PE),
> > > not specific to any network reference architectures defined
> > > by SDOs (like your refered entities).
> > > There would be just a few PE types ("given by the limited set
> > > of RTP topology components (RFC 5117)").
> > >
> > > to 2) (RFC 3550) Monitor function
> > > Right, that's a functional entity. The applicability of a
> > > monitor may be limited, dependent on ... (like in P.NAMS).
> > >
> > > to 3) your IMS network example
> > > Don't see the need to refer from MONARCH to a specific
> > > network architecture like IMS.
> > > Please also note that IMS is a functional architecture, not a
> > > physical architecture.
> > >
> > > Regards,
> > > Albrecht
> > >
> > > PS
> > > There are multiple options for adding the "RTP monitoring
> > > architecture" to a functional/physical network architecture:
> > > a) integrated approach: extension of existing functional
> > > entities or/and addition of RTP monitoring architectural
> > > components, extension or/and addition of
> > > signalling/management interfaces for control and
> > > configuration of RTP monitoring services, and reporting
> > > interfaces for measurement data ...
> > > b) overlay approach: separate specification to ...
> > >
> > >
> > > PSS
> > > BTW: there's a discussion paper with regards to the location
> > > of a monitor function in an IMS H.248 gateway entity:
> > > Measurements and statistics in IMS - Use Cases
> > > http://www.3gpp.org/ftp/tsg_ct/WG3_interworking_ex-CN3/TSGC3_5
> > > 8_Kyoto_Japan/Docs/C3-100469.zip
> > > This is just fyi.
> > >
> > >
> > >
> > > > -----Original Message-----
> > > > From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On
> > > > Behalf Of Qin Wu
> > > > Sent: Freitag, 2. Dezember 2011 02:55
> > > > To: Schwarz, Albrecht (Albrecht); avt@ietf.org
> > > > Cc: megaco@ietf.org
> > > > Subject: Re: [AVTCORE] Types of monitoring architectures; RE:
> > > > I-D Action: draft-ietf-avtcore-monarch-08.txt
> > > >
> > > > Hi, Albrecht:
> > > > No offence, I am not really convinced with your proposal on
> > > > physical monitoring architecture.
> > > >  my counterquestion is what does physical monitoring
> > > > architecture looks like in your mind?
> > > > How many components do we have in such physical monitroing
> > > > architecture? what are they?
> > > > Take IMS network architecture as a example, they may have
> > > > P-CSCF,S-CSCF, SIP PBX, SBC, why do you believe monitor
> > > > described in draft-ietf-avtcore-monarch is mapped into
> > > > P-CSCF, S-CSCF, SBC, Media Gateway, Media Gateway Controller
> > > > should be in the scope of IETF RTP monitoring
> archtiecture draft?
> > > >
> > > > Monitor described in  draft-ietf-avtcore-monarch is well
> > > > defined in the section 3 of RFC3550 as follows:
> > > > "
> > > >
> > > >    Monitor: An application that receives RTCP packets sent by
> > > >       participants in an RTP session, in particular the
> reception
> > > >       reports, and estimates the current quality of service for
> > > >       distribution monitoring, fault diagnosis and long-term
> > > > statistics.
> > > >       The monitor function is likely to be built into the
> > > > application(s)
> > > >       participating in the session, but may also be a separate
> > > >       application that does not otherwise participate and
> > > > does not send
> > > >       or receive the RTP data packets (since they are on
> > a separate
> > > >       port).  These are called third-party monitors.  It is also
> > > >       acceptable for a third-party monitor to receive
> the RTP data
> > > >       packets but not send RTCP packets or otherwise be
> > > counted in the
> > > >       session.
> > > >
> > > > "
> > > > Isn't how to implent monitor into IMS netowork archtiecture a
> > > > implentation specific issue?
> > > > If this issue are really interesting, isn't it a good idea to
> > > > produce another new document to talk about this?
> > > > One good example for this motivation is this draft I like to
> > > > share with you:
> > > > http://tools.ietf.org/html/draft-kaplan-dispatch-b2bua-taxonom
> > > > y-00#section-4.6
> > > >
> > > > Regards!
> > > > -Qin
> > > > ----- Original Message -----
> > > > From: "Schwarz, Albrecht (Albrecht)"
> > > > <albrecht.schwarz@alcatel-lucent.com>
> > > > To: "Qin Wu" <bill.wu@huawei.com>; <avt@ietf.org>
> > > > Cc: <megaco@ietf.org>
> > > > Sent: Friday, December 02, 2011 12:20 AM
> > > > Subject: RE: [AVTCORE] Types of monitoring architectures; RE:
> > > > I-D Action: draft-ietf-avtcore-monarch-08.txt
> > > >
> > > >
> > > > My replies below ...
> > > > -Albrecht
> > > >
> > > > > -----Original Message-----
> > > > > From: Qin Wu [mailto:bill.wu@huawei.com]
> > > > > Sent: Donnerstag, 1. Dezember 2011 02:42
> > > > > To: Schwarz, Albrecht (Albrecht); avt@ietf.org
> > > > > Cc: megaco@ietf.org
> > > > > Subject: Re: [AVTCORE] Types of monitoring architectures; RE:
> > > > > I-D Action: draft-ietf-avtcore-monarch-08.txt
> > > > >
> > > > > Hi,
> > > > > ----- Original Message -----
> > > > > From: "Schwarz, Albrecht (Albrecht)"
> > > > > <albrecht.schwarz@alcatel-lucent.com>
> > > > > To: "Qin Wu" <bill.wu@huawei.com>; <avt@ietf.org>
> > > > > Cc: <megaco@ietf.org>
> > > > > Sent: Thursday, December 01, 2011 1:24 AM
> > > > > Subject: RE: [AVTCORE] Types of monitoring architectures; RE:
> > > > > I-D Action: draft-ietf-avtcore-monarch-08.txt
> > > > >
> > > > >
> > > > > My replies below inline,
> > > > > Albrecht
> > > > >
> > > > > > -----Original Message-----
> > > > > > From: Qin Wu [mailto:bill.wu@huawei.com]
> > > > > > Sent: Mittwoch, 30. November 2011 04:51
> > > > > > To: Schwarz, Albrecht (Albrecht); avt@ietf.org
> > > > > > Cc: megaco@ietf.org
> > > > > > Subject: Re: [AVTCORE] Types of monitoring
> architectures; RE:
> > > > > > I-D Action: draft-ietf-avtcore-monarch-08.txt
> > > > > >
> > > > > > Hi,
> > > > > > ----- Original Message -----
> > > > > > From: "Schwarz, Albrecht (Albrecht)"
> > > > > > <albrecht.schwarz@alcatel-lucent.com>
> > > > > > To: <avt@ietf.org>
> > > > > > Cc: <megaco@ietf.org>
> > > > > > Sent: Tuesday, November 29, 2011 7:32 PM
> > > > > > Subject: [AVTCORE] Types of monitoring
> architectures; RE: I-D
> > > > > > Action: draft-ietf-avtcore-monarch-08.txt
> > > > > >
> > > > > >
> > > > > > > Dear All,
> > > > > > >
> > > > > > > there are different types of monitoring architectures,
> > > > > > particularily from perspective of QoE related performance
> > > > > parameters.
> > > > > > > Let's recall QoE (e.g., ITU-T P.10 Amendment 2):
> > > > > > >
> > > > > > > Quality of Experience (QoE):
> > > > > > > The overall acceptability of an application or service, as
> > > > > > perceived subjectively by the end-user.
> > > > > > > NOTE 1 - Quality of experience includes the complete
> > > > > > end-to-end system effects (client, terminal, network,
> > > > > > services infrastructure, etc.).
> > > > > > > NOTE 2 - Overall acceptability may be influenced by user
> > > > > > expectations and context.
> > > > > > >
> > > > > > > Important for MONARCH:
> > > > > > > 1st ... perceived by end-user
> > > > > > > 2nd QoE includes the complete end-to-end sytem effects ...
> > > > > > >
> > > > > > > That said, present RTP monitoring architecture in MONARCH
> > > > > > according clause 3 is not specific on the type of monitoring
> > > > > > architecture. For instance, Fig. 1, it is possibly supposed
> > > > > > that the "RTP Sender" and "RTP Receiver" entities are equal
> > > > > > to a terminal/user equipment (UE). This would be an
> > > > > > end-to-end IP network scenario.
> > > > > > >
> > > > > > > However, the "RTP Sender" and "RTP Receiver" entities may
> > > > > > be also located at the edge of an IP network, e.g. in a
> > > > > > gateway for IP-to-non-IP interworking, i.e. an UE located in
> > > > > > the non-IP network part.
> > > > > > > Note: such scenarios are considered by MEGACO gateways
> > > > > > (I've Cc'd megaco list).
> > > > > > >
> > > > > > > An RTP Sender/Receiver located NOT in the UE
> would question
> > > > > > the value of RTP/RTCP QoE related performance measurements
> > > > > > (because the UE is located outside the RTP domain).
> > > > > > >
> > > > > > > Conclusions:
> > > > > > > - the set of meaningful performance metrics may be
> > > > > > dependent on the location of the RTP Sender/Receiver, e.g.
> > > > > > whether in a UE, gateway, ...
> > > > > > > - don't see any impact on transport level metrics
> > > > > > > - ... but the set of meaningful application level metrics
> > > > > > >
> > > > > > > Proposal for MONARCH:
> > > > > > > #1: insert sub-clause title "3.1 End-to-end IP network
> > > > > > architecture" below clause 3
> > > > > > >
> > > > > > > #2: add a sub-clause 3.2 at the end of clause 3, sth like
> > > > > > >
> > > > > > > "3.2 RTP Sender/Receiver entities located in network nodes
> > > > > > > The location of the RTP Sender/Receiver entity may impact
> > > > > > the set of meaningful metrics.
> > > > > > > For instance: application level metrics for QoE related
> > > > > > performance metrics are questionable (or doesn't really make
> > > > > > sense at all) when measured in a network node (terminating
> > > > > > the RTP) instead of the user equipment."
> > > > > > >
> > > > > > > Something like this would help to avoid confusion.
> > > > > > > I even believe that a QoE measurement in a network node
> > > > > > would violate the QoE definition. Would be rather something
> > > > > > like QoE* ("remote QoE"):-(
> > > > > > >
> > > > > > > Such information would improve the MONARCH doc in
> > my opinion.
> > > > > > > Sorry for that late comment.
> > > > > > > Any views?
> > > > > >
> > > > > > [Qin]:
> > > > > > Albrrecht, if you follow ealry list discussion on
> > > > > > draft-hunt-avt-monarch-01, you will see the rough consensus
> > > > > > to position this document was
> > > > > > this daft should focus on guidelines for defining reporting
> > > > > > blocks. That is to say the main purpose of MONARCH draft
> > > > is how to
> > > > > > provide guidelines for the development of new RTCP XR block
> > > > > > types in XRBlock working group.
> > > > >
> > > > > [ABS] ... then the title "monitoring architectures" is
> > misleading.
> > > > > Proposal: keep title, revise scope section on focus
> > > > >
> > > > > [Qin]: No, the title is *RTP* monitoring architecture, we can
> > > > > not expand scope into IP monitoring architecture.
> > > >
> > > > [ABS] That's wasn't the intent! Did just focus on the key word.
> > > >
> > > > >
> > > > > >
> > > > > > Therefore how and where to collect the metric from RTP
> > > > > > endpoint is not scope of this document, in my opinion. since
> > > > > > you may have many ways to do this and different vendors have
> > > > > > their different appoaches. It will be better to leave this
> > > > > > beyond the scope. But you are right, it will be more
> > > > > > reasonable to measure QoE related performance metric at the
> > > > > > RTP receiver.
> > > > >
> > > > > [ABS] I would disagree. At least your statement should be
> > > > > conditional, sth like
> > > > > "QoE related performance metrics may be measured in a RTP
> > > > > receiver, IF the RTP receiver function is located in user
> > > > > equipment (e.g. IP terminal), because QoE performance metrics
> > > > > are tightly coupled to the point of view of a 'user'.
> > > > > ... IF NOT, then ..."
> > > > >
> > > > > [Qin]: I am not sure user equipment or IP terminal is the
> > > > > right term from RTP perspective.
> > > > >
> > > > > Also if you read P.NAMS, P.NAMS model for calculating QoE
> > > > > related metric can be placed either at the network or at
> > > the client.
> > > > > So I disagree with what you said.
> > > >
> > > > [ABS] Not convinced at all.
> > > > Guess you are referring to the "mid-point" models, right?
> > > > The usage of such that models depends on "prior knowledge
> > > > ..." information.
> > > > Thus, the applicability is conditional. You may not make such
> > > > a general statement.
> > > >
> > > >
> > > > >
> > > > > Also as I said, how and where to collect the metric from RTP
> > > > >  endpoint is not scope of this document. It depends on the
> > > > > model you are choosing, e.g., four operation modes specified
> > > > > in P.NAMS.
> > > > > Apparently this should not be specified again in RTP
> > > > > monitoring architecture document.
> > > > >
> > > > > >
> > > > > > Another point is it is not clear to me how RTP
> monitoring has
> > > > > > to do with architectureend to end IP network architecture .
> > > > > > this draft mostly focus on discussing RTP level stuff.
> > > > > > Therefore I am quite doubt that we should describe anything
> > > > > > in this document like how
> > > > > > RTP entties is mapped into network entities/nodes at
> > > the IP layer.
> > > > >
> > > > > [ABS] I don't got any problems to talk about architectural
> > > > > framework for monitoring in this document. Such information
> > > > > is required and this is the only IETF AVT doc about it.
> > > > > The solution to this issue is rather simple to me:
> > > > > - split the MONARCH "monitoring architecture" in
> > > > > 1) a functional monitoring architecture (let's call it
> > 'FMA') and
> > > > > 2) a physical monitoring architecture (... 'PMA').
> > > > >
> > > > > - the present MONARCH doc would describe the FMA at the level
> > > > > of RTP entities (i.e., Fig. 1 entities, incl. all the RTP
> > > > > topology components according RFC 5117)
> > > > >
> > > > > - there are many options of functional-to-physical mappings,
> > > > > i.e. how a FMA would be mapped on a PMA
> > > > > - the mapping is typically dependent on considered network
> > > > > architecture (like SIP, H.323, MGCP, IMS, wireless, etc
> > networks)
> > > > >
> > > > > - the present MONARCH doc would describe the FMA-to-PMA
> > > > > mapping IF all RTP receiver/sender entities would be located
> > > > > in physical IP terminals (UEs)
> > > > > - etc
> > > > >
> > > > > [Qin]: I can understand your point, but you can not do that.
> > > > > Since this document is only focus on *RTP* monitoring
> > > > > architecture, that is what it said in AVTCore milestone:
> > > > > "
> > > > >
> > > > > Goals and Milestones:
> > > > >
> > > > >   Feb 2011 - Submit Monitoring Architecture for RTP for
> > > > Informational
> > > > >
> > > > > "
> > > >
> > > > [ABS] If you go back to my first email on this subject, and
> > > > if you look at my proposal: that's not a lot, nothing which
> > > > violates the charter, goals and milestones.
> > > >
> > > >
> > > > > Also if you really don't see how to map FMA to PMA, you may
> > > > > look at the P.NAMS models specifed in ITU-T P.NAMS.
> > > > > As for how to use RTP monitoring architecture or RTP XR
> > > > > Report in the IMS network architecture, you may look at:
> > > > > http://tools.ietf.org/html/rfc6035
> > > >
> > > > [ABS] That's the SIP reporting interface, i.e., applicable
> > > > primarily for physical IP user equipment with embedded RTP
> > > > sender/receiver function and SIP UA function.
> > > > However, the applicability of RFC 6035 is limited for a
> > > > SIP-to-PSTN gateway (because the RTP sender/receiver would be
> > > > located NOT in user equipment. Also the P.NAMS mid-point
> > > > model fails for such a scenario.
> > > >
> > > > > ITU-T H.248.48.
> > > > > But I haven't check the current status of H.248.48.
> > > >
> > > > [ABS] Work is finalized, see
> > > > http://www.itu.int/md/meetingdoc.asp?lang=en&parent=T09-SG16-1
> > > > 11121-TD-PLEN-0419
> > > >
> > > > >
> > > > > >
> > > > > > But as the author of this document, I am interested and open
> > > > > > to other opinions.:-)
> > > > >
> > > > > [ABS] Like to add a further aspect: a "functional monitoring
> > > > > architecture" may be considered as a network overlay,
> > > > > something which adds additional capabilities (here:
> > > > > measurement services, reporting services on top of basic RTP
> > > > > services).
> > > > > Such an overlay concept is nothing new: e.g., the
> > > > > MultiService Forum did define a "Performance Measurement &
> > > > > Monitoring (PMM)" overlay network, or IETF RMON may be also
> > > > > considered as such.
> > > > >
> > > > > >
> > > > > > > Regards,
> > > > > > > Albrecht
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >> -----Original Message-----
> > > > > > >> From: avt-bounces@ietf.org
> [mailto:avt-bounces@ietf.org] On
> > > > > > >> Behalf Of internet-drafts@ietf.org
> > > > > > >> Sent: Dienstag, 29. November 2011 08:56
> > > > > > >> To: i-d-announce@ietf.org
> > > > > > >> Cc: avt@ietf.org
> > > > > > >> Subject: [AVTCORE] I-D Action:
> > > > draft-ietf-avtcore-monarch-08.txt
> > > > > > >>
> > > > > > >>
> > > > > > >> A New Internet-Draft is available from the on-line
> > > > > > >> Internet-Drafts directories. This draft is a work
> > item of the
> > > > > > >> Audio/Video Transport Core Maintenance Working Group
> > > > of the IETF.
> > > > > > >>
> > > > > > >> Title           : Monitoring Architectures for RTP
> > > > > > >> Author(s)       : Qin Wu
> > > > > > >>                           Geoff Hunt
> > > > > > >>                           Philip Arden
> > > > > > >> Filename        : draft-ietf-avtcore-monarch-08.txt
> > > > > > >> Pages           : 25
> > > > > > >> Date            : 2011-11-28
> > > > > > >>
> > > > > > >>    This memo proposes an architecture for
> > extending RTCP with
> > > > > > >> a new RTCP
> > > > > > >>    XR (RFC3611) block type to report new metrics
> > > > regarding media
> > > > > > >>    transmission or reception quality, following RTCP
> > > guideline
> > > > > > >>    established in RFC5968.  This memo suggests that a new
> > > > > > block should
> > > > > > >>    contain a single metric or a small number of metrics
> > > > > > relevant to a
> > > > > > >>    single parameter of interest or concern, rather than
> > > > > > containing a
> > > > > > >>    number of metrics which attempt to provide
> full coverage
> > > > > > >> of all those
> > > > > > >>    parameters of concern to a specific application.
> > > > > > Applications may
> > > > > > >>    then "mix and match" to create a set of blocks which
> > > > > > >> covers their set
> > > > > > >>    of concerns.  Where possible, a specific
> block should be
> > > > > > >> designed to
> > > > > > >>    be re-usable across more than one application, for
> > > > > > example, for all
> > > > > > >>    of voice, streaming audio and video.
> > > > > > >>
> > > > > > >>
> > > > > > >> A URL for this Internet-Draft is:
> > > > > > >>
> > > > > >
> > > > >
> > > >
> > >
> >
> http://www.ietf.org/internet-drafts/draft-ietf-avtcore-monarch-08.txt
> > > > > > >>
> > > > > > >> Internet-Drafts are also available by anonymous FTP at:
> > > > > > >> ftp://ftp.ietf.org/internet-drafts/
> > > > > > >>
> > > > > > >> This Internet-Draft can be retrieved at:
> > > > > > >>
> > > > > >
> > > >
> > ftp://ftp.ietf.org/internet-drafts/draft-ietf-avtcore-monarch-08.txt
> > > > > > >>
> > > > > > >> _______________________________________________
> > > > > > >> Audio/Video Transport Core Maintenance
> > > > > > >> avt@ietf.org
> > > > > > >> https://www.ietf.org/mailman/listinfo/avt
> > > > > > >>
> > > > > > > _______________________________________________
> > > > > > > Audio/Video Transport Core Maintenance
> > > > > > > avt@ietf.org
> > > > > > > https://www.ietf.org/mailman/listinfo/avt
> > > > > >
> > > > > =
> > > > _______________________________________________
> > > > Audio/Video Transport Core Maintenance
> > > > avt@ietf.org
> > > > https://www.ietf.org/mailman/listinfo/avt
> > > >
> > >
> >
>

From bill.wu@huawei.com  Mon Dec 12 18:00:30 2011
Return-Path: <bill.wu@huawei.com>
X-Original-To: megaco@ietfa.amsl.com
Delivered-To: megaco@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 583091F0C47; Mon, 12 Dec 2011 18:00:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.714
X-Spam-Level: 
X-Spam-Status: No, score=-5.714 tagged_above=-999 required=5 tests=[AWL=-0.315, BAYES_00=-2.599, J_CHICKENPOX_14=0.6, J_CHICKENPOX_74=0.6, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vVcDY9CrYn4E; Mon, 12 Dec 2011 18:00:28 -0800 (PST)
Received: from szxga03-in.huawei.com (szxga03-in.huawei.com [119.145.14.66]) by ietfa.amsl.com (Postfix) with ESMTP id 989D71F0C35; Mon, 12 Dec 2011 18:00:27 -0800 (PST)
Received: from huawei.com (szxga03-in [172.24.2.9]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LW4009E6DKP1E@szxga03-in.huawei.com>; Tue, 13 Dec 2011 10:00:25 +0800 (CST)
Received: from szxrg01-dlp.huawei.com ([172.24.2.119]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LW4000O8DKOTH@szxga03-in.huawei.com>; Tue, 13 Dec 2011 10:00:25 +0800 (CST)
Received: from szxeml207-edg.china.huawei.com ([172.24.2.119]) by szxrg01-dlp.huawei.com (MOS 4.1.9-GA)	with ESMTP id AFU21489; Tue, 13 Dec 2011 10:00:24 +0800
Received: from SZXEML418-HUB.china.huawei.com (10.82.67.157) by szxeml207-edg.china.huawei.com (172.24.2.59) with Microsoft SMTP Server (TLS) id 14.1.323.3; Tue, 13 Dec 2011 10:00:22 +0800
Received: from w53375q (10.138.41.130) by szxeml418-hub.china.huawei.com (10.82.67.157) with Microsoft SMTP Server (TLS) id 14.1.323.3; Tue, 13 Dec 2011 10:00:20 +0800
Date: Tue, 13 Dec 2011 10:00:19 +0800
From: Qin Wu <bill.wu@huawei.com>
X-Originating-IP: [10.138.41.130]
To: "Schwarz, Albrecht (Albrecht)" <albrecht.schwarz@alcatel-lucent.com>, avt@ietf.org
Message-id: <FC7C5040B6114522BE1117B6F79D160A@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.6109
X-Mailer: Microsoft Outlook Express 6.00.2900.5931
Content-type: text/plain; charset=ISO-8859-1
Content-transfer-encoding: 7BIT
X-Priority: 3
X-MSMail-priority: Normal
X-CFilter-Loop: Reflected
References: <5F7BCCF5541B7444830A2288ABBEBC9621620F5330@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com> <5F7BCCF5541B7444830A2288ABBEBC9621620F5344@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com>
Cc: megaco@ietf.org
Subject: Re: [Megaco] Update proposal; RE:  [AVTCORE] Types of monitoring architectures; RE:  I-D Action: draft-ietf-avtcore-monarch-08.txt
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.1.12
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: Tue, 13 Dec 2011 02:00:30 -0000

Hi, Albrecht:
Thank for your proposal. I will how your proposed text can fit into RTP monitoring architecture
and reflect them in the new update. Thanks again.

Regards!
-Qin
----- Original Message ----- 
From: "Schwarz, Albrecht (Albrecht)" <albrecht.schwarz@alcatel-lucent.com>
To: "Qin Wu" <bill.wu@huawei.com>; <avt@ietf.org>
Cc: <megaco@ietf.org>
Sent: Monday, December 12, 2011 6:55 PM
Subject: Update proposal; RE: [Megaco] [AVTCORE] Types of monitoring architectures; RE: I-D Action: draft-ietf-avtcore-monarch-08.txt



Might be more effective by continuing the discussion with a concrete text proposal, see attachments.
Any comments?
Albrecht

> -----Original Message-----
> From: megaco-bounces@ietf.org
> [mailto:megaco-bounces@ietf.org] On Behalf Of Schwarz,
> Albrecht (Albrecht)
> Sent: Montag, 12. Dezember 2011 11:33
> To: Qin Wu; avt@ietf.org
> Cc: megaco@ietf.org
> Subject: Re: [Megaco] [AVTCORE] Types of monitoring
> architectures; RE: I-D Action: draft-ietf-avtcore-monarch-08.txt
>
> Hi Qin,
>
> I'm very aware about all that.
> It looks like that you are now agreeing that QoE measurements
> are CONDITIONAL ("you got a number of IF statements, there
> might be even more ...").
>
> MONARCH is not talking about such conditions, thus some
> readers may got the impression that the metrics related to
> RTP traffic are UNCONDITIONAL (which is not true as you confirmed).
>
> If you go back to my very first email: I did just propose to
> indicate the conditional aspect. Don't understand why such
> kind of valuable info would be not in scope of MONARCH. Hm?
>
> Regards,
> Albrecht
>
> PS
> I did use the notion of a control plane agnostic "RTP-to-PSTN
> gateway". You did indicate control plane specific gateway
> types like SIP-to-PSTN or SIP-to-H.323. Now issue to use such
> signalling protocol specific examples, but it doesn't change
> the underlying issue.
> The SIP side reporting capability based on RFC 6035 allows to
> report the outlined measurements, but the RFC itself does not
> specify whether the reported information is meaningful (which
> is OK because this is not subject of a reporting interface
> spec, it is rather subject of a network monitoring doc like MONARCH).
> QoE measurements would be conditional in both gateway types
> (because such a gateway is NOT a user device despite the fact
> of an embedded SIP user agent entity).
> Actually I would even question here the condition of
> "customer knows the original content" in many real network scenarios.
>
>
>
> > -----Original Message-----
> > From: Qin Wu [mailto:bill.wu@huawei.com]
> > Sent: Montag, 12. Dezember 2011 05:05
> > To: Schwarz, Albrecht (Albrecht); avt@ietf.org
> > Cc: megaco@ietf.org
> > Subject: Re: [AVTCORE] Types of monitoring architectures; RE:
> > I-D Action: draft-ietf-avtcore-monarch-08.txt
> >
> > Hi, Albrecht:
> > My understanding to QoE measurment is:
> > The factors that influence the QoE metric include encoding system,
> > transport network, access network,home network and end device.
> > If the customer(e.g., network operator) doesn't know the original
> > content, the QoE metric should be usually measured at the
> user device.
> > If the customer knows the original content, the QoE metric can be
> > measured either in the network or at the user device.
> > Given the growing popularity of connected devices, these
> devices may
> > have different capability corresponding to CPU load, processing
> > overhead, storage, batteries.
> > If the cusomer want to measure QoE without considering connected
> > devices with various capability , the QoE metric can be measured at
> > the point between access network and home network.
> >
> > Regarding the monitoring scenario you mentioned, I am not familiar
> > with such scenario with RTP-to-PSTN gateway deployed.
> > But I am aware that there are scenarios with SIP to PSTN gateway or
> > SIP to H.323 gateway widely deployed,  RFC6035 defines a
> new SIP event
> > package, vq-rtcpxr that enable the collection and  reporting of
> > metrics that measure quality for RTP sessions. In such
> cases, RTCP XR
> > VOIP metric with QoE metric included is measured at the user device
> > and mapped into the equivalent SIP vq-rtcpxr parameter since SIP
> > session call is established end to end and RTP media stream is
> > exchanged directly between one endpoint and the other endpoint.
> >
> > Regards!
> > -Qin
> > ----- Original Message -----
> > From: "Schwarz, Albrecht (Albrecht)"
> > <albrecht.schwarz@alcatel-lucent.com>
> > To: "Qin Wu" <bill.wu@huawei.com>; <avt@ietf.org>
> > Cc: <megaco@ietf.org>
> > Sent: Saturday, December 10, 2011 12:01 AM
> > Subject: RE: [AVTCORE] Types of monitoring architectures; RE:
> > I-D Action: draft-ietf-avtcore-monarch-08.txt
> >
> >
> > How do you explain to a network operator the value of QoE
> measurements
> > by an RTP receiver / RTP monitor component located in an
> RTP-to-PSTN
> > gateway?
> >
> > This would be a monitoring scenario inline with MONARCH, but with
> > valueless QoE results, right?
> >
> >
> > > -----Original Message-----
> > > From: Qin Wu [mailto:bill.wu@huawei.com]
> > > Sent: Donnerstag, 8. Dezember 2011 03:26
> > > To: Schwarz, Albrecht (Albrecht); avt@ietf.org
> > > Cc: megaco@ietf.org
> > > Subject: Re: [AVTCORE] Types of monitoring architectures; RE:
> > > I-D Action: draft-ietf-avtcore-monarch-08.txt
> > >
> > > You reiterate what you propose for physical entities in the early
> > > email.
> > > I am still not convicing with that.
> > >
> > > Since we have RTP components like RTP end system, RTP mixer, RTP
> > > media translator, RTP transport translator, RTP monitor
> specified in
> > > RFC3550 can be built into these component as a application. also
> > > monitor can be disjointed from these RTP components as a
> third party
> > > monitor. why we need to specify how to map RTP end system
> into user
> > > equipment, RTP translator or RTP mixer can be mapped into
> RTP-PSTN
> > > gateway, or IP to IP border gateway since we have already mapped
> > > monitor into different RTP components.
> > > How many PE types you can enumerate? why they should be
> scope of RTP
> > > monitoring architecture?
> > >
> > > Also as specified in MONARCH draft, we have end sytem metrics,
> > > transport level metric, transport level metric, they can
> be measured
> > > and collected from the different RTP comoponents specified in
> > > RFC3550, RFC5117. Apparently end system metric can only
> be collected
> > > from RTP end system.
> > > transport metric is collected from any RTP system in the RTP
> > > monitoring architecture, regarding application level metric,
> > > apparently they should be measured at the application
> layer and can
> > > not be collected from RTP transport translator, Also RTP
> transport
> > > translator is still a functional entity rather than a physical
> > > entity. I am not convincing with what you said about
> > > "contradiction", "lead to possible wrong expectations".
> > >
> > > Regards!
> > > -Qin
> > > ----- Original Message -----
> > > From: "Schwarz, Albrecht (Albrecht)"
> > > <albrecht.schwarz@alcatel-lucent.com>
> > > To: "Qin Wu" <bill.wu@huawei.com>; <avt@ietf.org>
> > > Cc: <megaco@ietf.org>
> > > Sent: Thursday, December 08, 2011 12:24 AM
> > > Subject: RE: [AVTCORE] Types of monitoring architectures; RE:
> > > I-D Action: draft-ietf-avtcore-monarch-08.txt
> > >
> > >
> > > Qin,
> > > that's NOT the point.
> > >
> > > All RFC 3550 and RFC 5117 RTP components are FUNCTIONAL
> > ENTITIES (FE).
> > > e.g.,
> > > - the RTP Monitor or RTP receiver FE may be located in different
> > > PHYSICAL ENTITIES (PE), e.g.
> > >         a1) a user equipment
> > >         a2) a RTP-to-PSTN gateway
> > >         a3) an IP-to-IP session border gateway (in a back-to-back
> > > RTP endsystem topology)
> > >         a3) ...
> > >
> > > - the RTP Monitor may be associated to an RTP transport
> > translator ...
> > >         b1) an IP-to-IP session border gateway
> > >
> > > The "RTP monitoring architecture" is IMPACTED by each
> > > functional-to-physical mapping because e.g.
> > > * QoE related metrics are questionable in case of a2
> ("despite the
> > > fact of a RTP receiver function")
> > > * application level metrics at the location of a RTP transport
> > > translator are a contradiction in itself
> > > * ...
> > >
> > > Again, it's not really changing the MONARCH draft because in the
> > > very majority of scenarios it is correct. However, there are few
> > > cases where the MONARCH description would be "too high
> level", "not
> > > fully correct", "lead to possible wrong expectations", ...
> > >
> > > Regards,
> > > Albrecht
> > >
> > >
> > >
> > > > -----Original Message-----
> > > > From: Qin Wu [mailto:bill.wu@huawei.com]
> > > > Sent: Dienstag, 6. Dezember 2011 07:13
> > > > To: Schwarz, Albrecht (Albrecht); avt@ietf.org
> > > > Cc: megaco@ietf.org
> > > > Subject: Re: [AVTCORE] Types of monitoring architectures; RE:
> > > > I-D Action: draft-ietf-avtcore-monarch-08.txt
> > > >
> > > > If you talk about existing RFC5117 RTP topology
> components, this
> > > > has already been covered by the current version of
> > > > draft-ietf-avtcore-monarch.
> > > > In most cases, an RTP system using RTCP XR is
> architecturally no
> > > > different from an RTP system which does not use RTCP XR.
> > > >
> > > > Regards!
> > > > -Qin
> > > > ----- Original Message -----
> > > > From: "Schwarz, Albrecht (Albrecht)"
> > > > <albrecht.schwarz@alcatel-lucent.com>
> > > > To: "Qin Wu" <bill.wu@huawei.com>; <avt@ietf.org>
> > > > Cc: <megaco@ietf.org>
> > > > Sent: Monday, December 05, 2011 10:48 PM
> > > > Subject: RE: [AVTCORE] Types of monitoring architectures; RE:
> > > > I-D Action: draft-ietf-avtcore-monarch-08.txt
> > > >
> > > >
> > > > Hello Qin,
> > > >
> > > > to 1) Physical monitoring architecture Of course
> consideration of
> > > > generic physical entities (PE), not specific to any network
> > > > reference architectures defined by SDOs (like your refered
> > > > entities).
> > > > There would be just a few PE types ("given by the
> limited set of
> > > > RTP topology components (RFC 5117)").
> > > >
> > > > to 2) (RFC 3550) Monitor function
> > > > Right, that's a functional entity. The applicability of
> a monitor
> > > > may be limited, dependent on ... (like in P.NAMS).
> > > >
> > > > to 3) your IMS network example
> > > > Don't see the need to refer from MONARCH to a specific network
> > > > architecture like IMS.
> > > > Please also note that IMS is a functional architecture, not a
> > > > physical architecture.
> > > >
> > > > Regards,
> > > > Albrecht
> > > >
> > > > PS
> > > > There are multiple options for adding the "RTP monitoring
> > > > architecture" to a functional/physical network architecture:
> > > > a) integrated approach: extension of existing
> functional entities
> > > > or/and addition of RTP monitoring architectural components,
> > > > extension or/and addition of signalling/management
> interfaces for
> > > > control and configuration of RTP monitoring services, and
> > > > reporting interfaces for measurement data ...
> > > > b) overlay approach: separate specification to ...
> > > >
> > > >
> > > > PSS
> > > > BTW: there's a discussion paper with regards to the
> location of a
> > > > monitor function in an IMS H.248 gateway entity:
> > > > Measurements and statistics in IMS - Use Cases
> > > > http://www.3gpp.org/ftp/tsg_ct/WG3_interworking_ex-CN3/TSGC3_5
> > > > 8_Kyoto_Japan/Docs/C3-100469.zip
> > > > This is just fyi.
> > > >
> > > >
> > > >
> > > > > -----Original Message-----
> > > > > From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On
> > > > > Behalf Of Qin Wu
> > > > > Sent: Freitag, 2. Dezember 2011 02:55
> > > > > To: Schwarz, Albrecht (Albrecht); avt@ietf.org
> > > > > Cc: megaco@ietf.org
> > > > > Subject: Re: [AVTCORE] Types of monitoring architectures; RE:
> > > > > I-D Action: draft-ietf-avtcore-monarch-08.txt
> > > > >
> > > > > Hi, Albrecht:
> > > > > No offence, I am not really convinced with your proposal on
> > > > > physical monitoring architecture.
> > > > >  my counterquestion is what does physical monitoring
> > > > > architecture looks like in your mind?
> > > > > How many components do we have in such physical monitroing
> > > > > architecture? what are they?
> > > > > Take IMS network architecture as a example, they may have
> > > > > P-CSCF,S-CSCF, SIP PBX, SBC, why do you believe monitor
> > > > > described in draft-ietf-avtcore-monarch is mapped
> into P-CSCF,
> > > > > S-CSCF, SBC, Media Gateway, Media Gateway Controller
> should be
> > > > > in the scope of IETF RTP monitoring
> > archtiecture draft?
> > > > >
> > > > > Monitor described in  draft-ietf-avtcore-monarch is
> well defined
> > > > > in the section 3 of RFC3550 as follows:
> > > > > "
> > > > >
> > > > >    Monitor: An application that receives RTCP packets sent by
> > > > >       participants in an RTP session, in particular the
> > reception
> > > > >       reports, and estimates the current quality of
> service for
> > > > >       distribution monitoring, fault diagnosis and long-term
> > > > > statistics.
> > > > >       The monitor function is likely to be built into the
> > > > > application(s)
> > > > >       participating in the session, but may also be a separate
> > > > >       application that does not otherwise participate
> and does
> > > > > not send
> > > > >       or receive the RTP data packets (since they are on
> > > a separate
> > > > >       port).  These are called third-party monitors.
> It is also
> > > > >       acceptable for a third-party monitor to receive
> > the RTP data
> > > > >       packets but not send RTCP packets or otherwise be
> > > > counted in the
> > > > >       session.
> > > > >
> > > > > "
> > > > > Isn't how to implent monitor into IMS netowork archtiecture a
> > > > > implentation specific issue?
> > > > > If this issue are really interesting, isn't it a good idea to
> > > > > produce another new document to talk about this?
> > > > > One good example for this motivation is this draft I like to
> > > > > share with you:
> > > > > http://tools.ietf.org/html/draft-kaplan-dispatch-b2bua-taxonom
> > > > > y-00#section-4.6
> > > > >
> > > > > Regards!
> > > > > -Qin
> > > > > ----- Original Message -----
> > > > > From: "Schwarz, Albrecht (Albrecht)"
> > > > > <albrecht.schwarz@alcatel-lucent.com>
> > > > > To: "Qin Wu" <bill.wu@huawei.com>; <avt@ietf.org>
> > > > > Cc: <megaco@ietf.org>
> > > > > Sent: Friday, December 02, 2011 12:20 AM
> > > > > Subject: RE: [AVTCORE] Types of monitoring architectures; RE:
> > > > > I-D Action: draft-ietf-avtcore-monarch-08.txt
> > > > >
> > > > >
> > > > > My replies below ...
> > > > > -Albrecht
> > > > >
> > > > > > -----Original Message-----
> > > > > > From: Qin Wu [mailto:bill.wu@huawei.com]
> > > > > > Sent: Donnerstag, 1. Dezember 2011 02:42
> > > > > > To: Schwarz, Albrecht (Albrecht); avt@ietf.org
> > > > > > Cc: megaco@ietf.org
> > > > > > Subject: Re: [AVTCORE] Types of monitoring
> architectures; RE:
> > > > > > I-D Action: draft-ietf-avtcore-monarch-08.txt
> > > > > >
> > > > > > Hi,
> > > > > > ----- Original Message -----
> > > > > > From: "Schwarz, Albrecht (Albrecht)"
> > > > > > <albrecht.schwarz@alcatel-lucent.com>
> > > > > > To: "Qin Wu" <bill.wu@huawei.com>; <avt@ietf.org>
> > > > > > Cc: <megaco@ietf.org>
> > > > > > Sent: Thursday, December 01, 2011 1:24 AM
> > > > > > Subject: RE: [AVTCORE] Types of monitoring
> architectures; RE:
> > > > > > I-D Action: draft-ietf-avtcore-monarch-08.txt
> > > > > >
> > > > > >
> > > > > > My replies below inline,
> > > > > > Albrecht
> > > > > >
> > > > > > > -----Original Message-----
> > > > > > > From: Qin Wu [mailto:bill.wu@huawei.com]
> > > > > > > Sent: Mittwoch, 30. November 2011 04:51
> > > > > > > To: Schwarz, Albrecht (Albrecht); avt@ietf.org
> > > > > > > Cc: megaco@ietf.org
> > > > > > > Subject: Re: [AVTCORE] Types of monitoring
> > architectures; RE:
> > > > > > > I-D Action: draft-ietf-avtcore-monarch-08.txt
> > > > > > >
> > > > > > > Hi,
> > > > > > > ----- Original Message -----
> > > > > > > From: "Schwarz, Albrecht (Albrecht)"
> > > > > > > <albrecht.schwarz@alcatel-lucent.com>
> > > > > > > To: <avt@ietf.org>
> > > > > > > Cc: <megaco@ietf.org>
> > > > > > > Sent: Tuesday, November 29, 2011 7:32 PM
> > > > > > > Subject: [AVTCORE] Types of monitoring
> > architectures; RE: I-D
> > > > > > > Action: draft-ietf-avtcore-monarch-08.txt
> > > > > > >
> > > > > > >
> > > > > > > > Dear All,
> > > > > > > >
> > > > > > > > there are different types of monitoring architectures,
> > > > > > > particularily from perspective of QoE related performance
> > > > > > parameters.
> > > > > > > > Let's recall QoE (e.g., ITU-T P.10 Amendment 2):
> > > > > > > >
> > > > > > > > Quality of Experience (QoE):
> > > > > > > > The overall acceptability of an application or
> service, as
> > > > > > > perceived subjectively by the end-user.
> > > > > > > > NOTE 1 - Quality of experience includes the complete
> > > > > > > end-to-end system effects (client, terminal, network,
> > > > > > > services infrastructure, etc.).
> > > > > > > > NOTE 2 - Overall acceptability may be influenced by user
> > > > > > > expectations and context.
> > > > > > > >
> > > > > > > > Important for MONARCH:
> > > > > > > > 1st ... perceived by end-user 2nd QoE includes the
> > > > > > > > complete end-to-end sytem effects ...
> > > > > > > >
> > > > > > > > That said, present RTP monitoring architecture
> in MONARCH
> > > > > > > according clause 3 is not specific on the type of
> monitoring
> > > > > > > architecture. For instance, Fig. 1, it is
> possibly supposed
> > > > > > > that the "RTP Sender" and "RTP Receiver" entities
> are equal
> > > > > > > to a terminal/user equipment (UE). This would be an
> > > > > > > end-to-end IP network scenario.
> > > > > > > >
> > > > > > > > However, the "RTP Sender" and "RTP Receiver"
> entities may
> > > > > > > be also located at the edge of an IP network, e.g. in a
> > > > > > > gateway for IP-to-non-IP interworking, i.e. an UE
> located in
> > > > > > > the non-IP network part.
> > > > > > > > Note: such scenarios are considered by MEGACO gateways
> > > > > > > (I've Cc'd megaco list).
> > > > > > > >
> > > > > > > > An RTP Sender/Receiver located NOT in the UE
> > would question
> > > > > > > the value of RTP/RTCP QoE related performance
> measurements
> > > > > > > (because the UE is located outside the RTP domain).
> > > > > > > >
> > > > > > > > Conclusions:
> > > > > > > > - the set of meaningful performance metrics may be
> > > > > > > dependent on the location of the RTP Sender/Receiver, e.g.
> > > > > > > whether in a UE, gateway, ...
> > > > > > > > - don't see any impact on transport level metrics
> > > > > > > > - ... but the set of meaningful application
> level metrics
> > > > > > > >
> > > > > > > > Proposal for MONARCH:
> > > > > > > > #1: insert sub-clause title "3.1 End-to-end IP network
> > > > > > > architecture" below clause 3
> > > > > > > >
> > > > > > > > #2: add a sub-clause 3.2 at the end of clause
> 3, sth like
> > > > > > > >
> > > > > > > > "3.2 RTP Sender/Receiver entities located in
> network nodes
> > > > > > > > The location of the RTP Sender/Receiver entity
> may impact
> > > > > > > the set of meaningful metrics.
> > > > > > > > For instance: application level metrics for QoE related
> > > > > > > performance metrics are questionable (or doesn't
> really make
> > > > > > > sense at all) when measured in a network node
> (terminating
> > > > > > > the RTP) instead of the user equipment."
> > > > > > > >
> > > > > > > > Something like this would help to avoid confusion.
> > > > > > > > I even believe that a QoE measurement in a network node
> > > > > > > would violate the QoE definition. Would be rather
> something
> > > > > > > like QoE* ("remote QoE"):-(
> > > > > > > >
> > > > > > > > Such information would improve the MONARCH doc in
> > > my opinion.
> > > > > > > > Sorry for that late comment.
> > > > > > > > Any views?
> > > > > > >
> > > > > > > [Qin]:
> > > > > > > Albrrecht, if you follow ealry list discussion on
> > > > > > > draft-hunt-avt-monarch-01, you will see the rough
> consensus
> > > > > > > to position this document was this daft should focus on
> > > > > > > guidelines for defining reporting blocks. That is
> to say the
> > > > > > > main purpose of MONARCH draft
> > > > > is how to
> > > > > > > provide guidelines for the development of new
> RTCP XR block
> > > > > > > types in XRBlock working group.
> > > > > >
> > > > > > [ABS] ... then the title "monitoring architectures" is
> > > misleading.
> > > > > > Proposal: keep title, revise scope section on focus
> > > > > >
> > > > > > [Qin]: No, the title is *RTP* monitoring
> architecture, we can
> > > > > > not expand scope into IP monitoring architecture.
> > > > >
> > > > > [ABS] That's wasn't the intent! Did just focus on the
> key word.
> > > > >
> > > > > >
> > > > > > >
> > > > > > > Therefore how and where to collect the metric from RTP
> > > > > > > endpoint is not scope of this document, in my
> opinion. since
> > > > > > > you may have many ways to do this and different
> vendors have
> > > > > > > their different appoaches. It will be better to
> leave this
> > > > > > > beyond the scope. But you are right, it will be more
> > > > > > > reasonable to measure QoE related performance
> metric at the
> > > > > > > RTP receiver.
> > > > > >
> > > > > > [ABS] I would disagree. At least your statement should be
> > > > > > conditional, sth like "QoE related performance
> metrics may be
> > > > > > measured in a RTP receiver, IF the RTP receiver function is
> > > > > > located in user equipment (e.g. IP terminal), because QoE
> > > > > > performance metrics are tightly coupled to the
> point of view
> > > > > > of a 'user'.
> > > > > > ... IF NOT, then ..."
> > > > > >
> > > > > > [Qin]: I am not sure user equipment or IP terminal is the
> > > > > > right term from RTP perspective.
> > > > > >
> > > > > > Also if you read P.NAMS, P.NAMS model for calculating QoE
> > > > > > related metric can be placed either at the network or at
> > > > the client.
> > > > > > So I disagree with what you said.
> > > > >
> > > > > [ABS] Not convinced at all.
> > > > > Guess you are referring to the "mid-point" models, right?
> > > > > The usage of such that models depends on "prior
> knowledge ..."
> > > > > information.
> > > > > Thus, the applicability is conditional. You may not
> make such a
> > > > > general statement.
> > > > >
> > > > >
> > > > > >
> > > > > > Also as I said, how and where to collect the metric
> from RTP
> > > > > > endpoint is not scope of this document. It depends on the
> > > > > > model you are choosing, e.g., four operation modes
> specified
> > > > > > in P.NAMS.
> > > > > > Apparently this should not be specified again in RTP
> > > > > > monitoring architecture document.
> > > > > >
> > > > > > >
> > > > > > > Another point is it is not clear to me how RTP
> > monitoring has
> > > > > > > to do with architectureend to end IP network
> architecture .
> > > > > > > this draft mostly focus on discussing RTP level stuff.
> > > > > > > Therefore I am quite doubt that we should
> describe anything
> > > > > > > in this document like how RTP entties is mapped
> into network
> > > > > > > entities/nodes at
> > > > the IP layer.
> > > > > >
> > > > > > [ABS] I don't got any problems to talk about architectural
> > > > > > framework for monitoring in this document. Such
> information is
> > > > > > required and this is the only IETF AVT doc about it.
> > > > > > The solution to this issue is rather simple to me:
> > > > > > - split the MONARCH "monitoring architecture" in
> > > > > > 1) a functional monitoring architecture (let's call it
> > > 'FMA') and
> > > > > > 2) a physical monitoring architecture (... 'PMA').
> > > > > >
> > > > > > - the present MONARCH doc would describe the FMA at
> the level
> > > > > > of RTP entities (i.e., Fig. 1 entities, incl. all the RTP
> > > > > > topology components according RFC 5117)
> > > > > >
> > > > > > - there are many options of functional-to-physical
> mappings,
> > > > > > i.e. how a FMA would be mapped on a PMA
> > > > > > - the mapping is typically dependent on considered network
> > > > > > architecture (like SIP, H.323, MGCP, IMS, wireless, etc
> > > networks)
> > > > > >
> > > > > > - the present MONARCH doc would describe the FMA-to-PMA
> > > > > > mapping IF all RTP receiver/sender entities would
> be located
> > > > > > in physical IP terminals (UEs)
> > > > > > - etc
> > > > > >
> > > > > > [Qin]: I can understand your point, but you can not do that.
> > > > > > Since this document is only focus on *RTP* monitoring
> > > > > > architecture, that is what it said in AVTCore milestone:
> > > > > > "
> > > > > >
> > > > > > Goals and Milestones:
> > > > > >
> > > > > >   Feb 2011 - Submit Monitoring Architecture for RTP for
> > > > > Informational
> > > > > >
> > > > > > "
> > > > >
> > > > > [ABS] If you go back to my first email on this
> subject, and if
> > > > > you look at my proposal: that's not a lot, nothing which
> > > > > violates the charter, goals and milestones.
> > > > >
> > > > >
> > > > > > Also if you really don't see how to map FMA to PMA, you may
> > > > > > look at the P.NAMS models specifed in ITU-T P.NAMS.
> > > > > > As for how to use RTP monitoring architecture or
> RTP XR Report
> > > > > > in the IMS network architecture, you may look at:
> > > > > > http://tools.ietf.org/html/rfc6035
> > > > >
> > > > > [ABS] That's the SIP reporting interface, i.e., applicable
> > > > > primarily for physical IP user equipment with embedded RTP
> > > > > sender/receiver function and SIP UA function.
> > > > > However, the applicability of RFC 6035 is limited for a
> > > > > SIP-to-PSTN gateway (because the RTP sender/receiver would be
> > > > > located NOT in user equipment. Also the P.NAMS
> mid-point model
> > > > > fails for such a scenario.
> > > > >
> > > > > > ITU-T H.248.48.
> > > > > > But I haven't check the current status of H.248.48.
> > > > >
> > > > > [ABS] Work is finalized, see
> > > > > http://www.itu.int/md/meetingdoc.asp?lang=en&parent=T09-SG16-1
> > > > > 11121-TD-PLEN-0419
> > > > >
> > > > > >
> > > > > > >
> > > > > > > But as the author of this document, I am
> interested and open
> > > > > > > to other opinions.:-)
> > > > > >
> > > > > > [ABS] Like to add a further aspect: a "functional
> monitoring
> > > > > > architecture" may be considered as a network overlay,
> > > > > > something which adds additional capabilities (here:
> > > > > > measurement services, reporting services on top of
> basic RTP
> > > > > > services).
> > > > > > Such an overlay concept is nothing new: e.g., the
> MultiService
> > > > > > Forum did define a "Performance Measurement & Monitoring
> > > > > > (PMM)" overlay network, or IETF RMON may be also
> considered as
> > > > > > such.
> > > > > >
> > > > > > >
> > > > > > > > Regards,
> > > > > > > > Albrecht
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > >> -----Original Message-----
> > > > > > > >> From: avt-bounces@ietf.org
> > [mailto:avt-bounces@ietf.org] On
> > > > > > > >> Behalf Of internet-drafts@ietf.org
> > > > > > > >> Sent: Dienstag, 29. November 2011 08:56
> > > > > > > >> To: i-d-announce@ietf.org
> > > > > > > >> Cc: avt@ietf.org
> > > > > > > >> Subject: [AVTCORE] I-D Action:
> > > > > draft-ietf-avtcore-monarch-08.txt
> > > > > > > >>
> > > > > > > >>
> > > > > > > >> A New Internet-Draft is available from the on-line
> > > > > > > >> Internet-Drafts directories. This draft is a work
> > > item of the
> > > > > > > >> Audio/Video Transport Core Maintenance Working Group
> > > > > of the IETF.
> > > > > > > >>
> > > > > > > >> Title           : Monitoring Architectures for RTP
> > > > > > > >> Author(s)       : Qin Wu
> > > > > > > >>                           Geoff Hunt
> > > > > > > >>                           Philip Arden
> > > > > > > >> Filename        : draft-ietf-avtcore-monarch-08.txt
> > > > > > > >> Pages           : 25
> > > > > > > >> Date            : 2011-11-28
> > > > > > > >>
> > > > > > > >>    This memo proposes an architecture for
> > > extending RTCP with
> > > > > > > >> a new RTCP
> > > > > > > >>    XR (RFC3611) block type to report new metrics
> > > > > regarding media
> > > > > > > >>    transmission or reception quality, following RTCP
> > > > guideline
> > > > > > > >>    established in RFC5968.  This memo suggests
> that a new
> > > > > > > block should
> > > > > > > >>    contain a single metric or a small number of metrics
> > > > > > > relevant to a
> > > > > > > >>    single parameter of interest or concern, rather than
> > > > > > > containing a
> > > > > > > >>    number of metrics which attempt to provide
> > full coverage
> > > > > > > >> of all those
> > > > > > > >>    parameters of concern to a specific application.
> > > > > > > Applications may
> > > > > > > >>    then "mix and match" to create a set of
> blocks which
> > > > > > > >> covers their set
> > > > > > > >>    of concerns.  Where possible, a specific
> > block should be
> > > > > > > >> designed to
> > > > > > > >>    be re-usable across more than one application, for
> > > > > > > example, for all
> > > > > > > >>    of voice, streaming audio and video.
> > > > > > > >>
> > > > > > > >>
> > > > > > > >> A URL for this Internet-Draft is:
> > > > > > > >>
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> http://www.ietf.org/internet-drafts/draft-ietf-avtcore-monarch-08.txt
> > > > > > > >>
> > > > > > > >> Internet-Drafts are also available by anonymous FTP at:
> > > > > > > >> ftp://ftp.ietf.org/internet-drafts/
> > > > > > > >>
> > > > > > > >> This Internet-Draft can be retrieved at:
> > > > > > > >>
> > > > > > >
> > > > >
> > >
> ftp://ftp.ietf.org/internet-drafts/draft-ietf-avtcore-monarch-08.txt
> > > > > > > >>
> > > > > > > >> _______________________________________________
> > > > > > > >> Audio/Video Transport Core Maintenance avt@ietf.org
> > > > > > > >> https://www.ietf.org/mailman/listinfo/avt
> > > > > > > >>
> > > > > > > > _______________________________________________
> > > > > > > > Audio/Video Transport Core Maintenance avt@ietf.org
> > > > > > > > https://www.ietf.org/mailman/listinfo/avt
> > > > > > >
> > > > > > =
> > > > > _______________________________________________
> > > > > Audio/Video Transport Core Maintenance avt@ietf.org
> > > > > https://www.ietf.org/mailman/listinfo/avt
> > > > >
> > > >
> > >
> >
> _______________________________________________
> Megaco mailing list
> Megaco@ietf.org
> https://www.ietf.org/mailman/listinfo/megaco
>

From bill.wu@huawei.com  Mon Dec 12 18:15:35 2011
Return-Path: <bill.wu@huawei.com>
X-Original-To: megaco@ietfa.amsl.com
Delivered-To: megaco@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C3C1821F8508; Mon, 12 Dec 2011 18:15:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.702
X-Spam-Level: 
X-Spam-Status: No, score=-5.702 tagged_above=-999 required=5 tests=[AWL=-0.303, BAYES_00=-2.599, J_CHICKENPOX_14=0.6, J_CHICKENPOX_74=0.6, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8QIy35A5A1Uw; Mon, 12 Dec 2011 18:15:33 -0800 (PST)
Received: from szxga01-in.huawei.com (szxga01-in.huawei.com [119.145.14.64]) by ietfa.amsl.com (Postfix) with ESMTP id 0F0F621F8507; Mon, 12 Dec 2011 18:15:33 -0800 (PST)
Received: from huawei.com (szxga05-in [172.24.2.49]) by szxga05-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LW400CNUE9P8P@szxga05-in.huawei.com>; Tue, 13 Dec 2011 10:15:25 +0800 (CST)
Received: from szxrg02-dlp.huawei.com ([172.24.2.119]) by szxga05-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LW4005S8E8B13@szxga05-in.huawei.com>; Tue, 13 Dec 2011 10:15:25 +0800 (CST)
Received: from szxeml203-edg.china.huawei.com ([172.24.2.119]) by szxrg02-dlp.huawei.com (MOS 4.1.9-GA)	with ESMTP id AFQ02550; Tue, 13 Dec 2011 10:15:24 +0800
Received: from SZXEML408-HUB.china.huawei.com (10.82.67.95) by szxeml203-edg.china.huawei.com (172.24.2.55) with Microsoft SMTP Server (TLS) id 14.1.323.3; Tue, 13 Dec 2011 10:15:21 +0800
Received: from w53375q (10.138.41.130) by szxeml408-hub.china.huawei.com (10.82.67.95) with Microsoft SMTP Server (TLS) id 14.1.323.3; Tue, 13 Dec 2011 10:15:18 +0800
Date: Tue, 13 Dec 2011 10:15:17 +0800
From: Qin Wu <bill.wu@huawei.com>
X-Originating-IP: [10.138.41.130]
To: Colin Perkins <csp@csperkins.org>, "Schwarz, Albrecht (Albrecht)" <albrecht.schwarz@alcatel-lucent.com>
Message-id: <CFFAC080E70043A5BD4536349C34EFDB@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.6109
X-Mailer: Microsoft Outlook Express 6.00.2900.5931
Content-type: text/plain; charset=ISO-8859-1
Content-transfer-encoding: 7BIT
X-Priority: 3
X-MSMail-priority: Normal
X-CFilter-Loop: Reflected
References: <20111129075613.12419.4377.idtracker@ietfa.amsl.com> <EAC481B4D8034C38AC54E1217F8D875D@china.huawei.com> <5F7BCCF5541B7444830A2288ABBEBC96216190077F@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com> <B527BAFA038842A8939A8C2D558074CD@china.huawei.com> <5F7BCCF5541B7444830A2288ABBEBC962161900908@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com> <9FF9B04A84E64AD7ABCCC4F2ACC1E19A@china.huawei.com> <5F7BCCF5541B7444830A2288ABBEBC9621620F4AF5@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com> <D44A4820E0D24DD79F6F5A4B7507D0D6@china.huawei.com> <5F7BCCF5541B7444830A2288ABBEBC9621620F4ED2@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com> <71112008FBA94D35B07FA6B4916075B6@china.huawei.com> <5F7BCCF5541B7444830A2288ABBEBC9621620F5258@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com> <6C618D1EA52146A781429C6B08C4A4FC@china.huawei.com> <5F7BCCF5541B7444830A2288ABBEBC9621620F5330@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com> <2BEF8708-58B8-4AEB-B3A6-702F46E58C12@csperkins.org>
Cc: megaco@ietf.org, avt@ietf.org
Subject: Re: [Megaco] [AVTCORE] Types of monitoring architectures; RE:  I-D Action: draft-ietf-avtcore-monarch-08.txt
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.1.12
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: Tue, 13 Dec 2011 02:15:35 -0000

Hi, Colin:
Thank for your suggestion. Besides Albrecht's proposed text, my additional proposal is to fix application level metric defintion in section 2
OLD text:
"
   Application level metrics

      Metrics relating to QoE related parameters.  These metrics are
      measured at the application level and focus on quality of content
      rather than network parameters. 
"
New text
"
   Application level metrics
 
      Metrics relating to application specific parameters or QoE related parameters. 
     Application specific parameters  are measured at the application level and focus
     on quality of content rather than network performance.  QoE related parameters
     reflect the end-to-end performance at the services level and is ususally measured
     at the user endpoint.
"

Regards!
-Qin
----- Original Message ----- 
From: "Colin Perkins" <csp@csperkins.org>
To: "Schwarz, Albrecht (Albrecht)" <albrecht.schwarz@alcatel-lucent.com>
Cc: "Qin Wu" <bill.wu@huawei.com>; <avt@ietf.org>; <megaco@ietf.org>
Sent: Tuesday, December 13, 2011 12:56 AM
Subject: Re: [AVTCORE] Types of monitoring architectures; RE: I-D Action: draft-ietf-avtcore-monarch-08.txt


Albrecht, Qin,

It doesn't seem controversial that some metrics are only meaningful in some scenarios, or when measured at certain points in a system. I don't see how adding a statement to the monarch draft to recognise that could be problematic. Is there anything else being suggested here?

Colin


On 12 Dec 2011, at 10:33, Schwarz, Albrecht (Albrecht) wrote:
> Hi Qin,
> 
> I'm very aware about all that.
> It looks like that you are now agreeing that QoE measurements are CONDITIONAL ("you got a number of IF statements, there might be even more ...").
> 
> MONARCH is not talking about such conditions, thus some readers may got the impression that the metrics related to RTP traffic are UNCONDITIONAL (which is not true as you confirmed).
> 
> If you go back to my very first email: I did just propose to indicate the conditional aspect. Don't understand why such kind of valuable info would be not in scope of MONARCH. Hm?
> 
> Regards,
> Albrecht
> 
> PS
> I did use the notion of a control plane agnostic "RTP-to-PSTN gateway". You did indicate control plane specific gateway types like SIP-to-PSTN or SIP-to-H.323. Now issue to use such signalling protocol specific examples, but it doesn't change the underlying issue.
> The SIP side reporting capability based on RFC 6035 allows to report the outlined measurements, but the RFC itself does not specify whether the reported information is meaningful (which is OK because this is not subject of a reporting interface spec, it is rather subject of a network monitoring doc like MONARCH).
> QoE measurements would be conditional in both gateway types (because such a gateway is NOT a user device despite the fact of an embedded SIP user agent entity).
> Actually I would even question here the condition of "customer knows the original content" in many real network scenarios.
> 
> 
> 
>> -----Original Message-----
>> From: Qin Wu [mailto:bill.wu@huawei.com]
>> Sent: Montag, 12. Dezember 2011 05:05
>> To: Schwarz, Albrecht (Albrecht); avt@ietf.org
>> Cc: megaco@ietf.org
>> Subject: Re: [AVTCORE] Types of monitoring architectures; RE:
>> I-D Action: draft-ietf-avtcore-monarch-08.txt
>> 
>> Hi, Albrecht:
>> My understanding to QoE measurment is:
>> The factors that influence the QoE metric include encoding
>> system, transport network, access network,home network and end device.
>> If the customer(e.g., network operator) doesn't know the
>> original content, the QoE metric should be usually measured
>> at the user device.
>> If the customer knows the original content, the QoE metric
>> can be measured either in the network or at the user device.
>> Given the growing popularity of connected devices, these
>> devices may have different capability corresponding to CPU
>> load, processing overhead, storage, batteries.
>> If the cusomer want to measure QoE without considering
>> connected devices with various capability , the QoE metric
>> can be measured at the point between access network and home network.
>> 
>> Regarding the monitoring scenario you mentioned, I am not
>> familiar with such scenario with RTP-to-PSTN gateway deployed.
>> But I am aware that there are scenarios with SIP to PSTN
>> gateway or SIP to H.323 gateway widely deployed,  RFC6035
>> defines a new SIP event package, vq-rtcpxr that enable the
>> collection and  reporting of metrics that measure quality for
>> RTP sessions. In such cases, RTCP XR VOIP metric with QoE
>> metric included is measured at the user device and mapped
>> into the equivalent SIP vq-rtcpxr parameter since SIP session
>> call is established end to end and RTP media stream is
>> exchanged directly between one endpoint and the other endpoint.
>> 
>> Regards!
>> -Qin
>> ----- Original Message -----
>> From: "Schwarz, Albrecht (Albrecht)"
>> <albrecht.schwarz@alcatel-lucent.com>
>> To: "Qin Wu" <bill.wu@huawei.com>; <avt@ietf.org>
>> Cc: <megaco@ietf.org>
>> Sent: Saturday, December 10, 2011 12:01 AM
>> Subject: RE: [AVTCORE] Types of monitoring architectures; RE:
>> I-D Action: draft-ietf-avtcore-monarch-08.txt
>> 
>> 
>> How do you explain to a network operator the value of QoE
>> measurements by an RTP receiver / RTP monitor component
>> located in an RTP-to-PSTN gateway?
>> 
>> This would be a monitoring scenario inline with MONARCH, but
>> with valueless QoE results, right?
>> 
>> 
>>> -----Original Message-----
>>> From: Qin Wu [mailto:bill.wu@huawei.com]
>>> Sent: Donnerstag, 8. Dezember 2011 03:26
>>> To: Schwarz, Albrecht (Albrecht); avt@ietf.org
>>> Cc: megaco@ietf.org
>>> Subject: Re: [AVTCORE] Types of monitoring architectures; RE:
>>> I-D Action: draft-ietf-avtcore-monarch-08.txt
>>> 
>>> You reiterate what you propose for physical entities in the
>>> early email.
>>> I am still not convicing with that.
>>> 
>>> Since we have RTP components like RTP end system, RTP mixer,
>>> RTP media translator, RTP transport translator, RTP monitor
>>> specified in RFC3550 can be built into these component as a
>>> application. also monitor can be disjointed from these RTP
>>> components as a third party monitor. why we need to specify
>>> how to map RTP end system into user equipment, RTP translator
>>> or RTP mixer can be mapped into RTP-PSTN gateway, or IP to IP
>>> border gateway since we have already mapped monitor into
>>> different RTP components.
>>> How many PE types you can enumerate? why they should be scope
>>> of RTP monitoring architecture?
>>> 
>>> Also as specified in MONARCH draft, we have end sytem
>>> metrics, transport level metric, transport level metric, they
>>> can be measured and collected from the different RTP
>>> comoponents specified in RFC3550, RFC5117. Apparently end
>>> system metric can only be collected from RTP end system.
>>> transport metric is collected from any RTP system in the RTP
>>> monitoring architecture, regarding application level metric,
>>> apparently they should be measured at the application layer
>>> and can not be collected from RTP transport translator, Also
>>> RTP transport translator is still a functional entity rather
>>> than a physical entity. I am not convincing with what you
>>> said about "contradiction", "lead to possible wrong expectations".
>>> 
>>> Regards!
>>> -Qin
>>> ----- Original Message -----
>>> From: "Schwarz, Albrecht (Albrecht)"
>>> <albrecht.schwarz@alcatel-lucent.com>
>>> To: "Qin Wu" <bill.wu@huawei.com>; <avt@ietf.org>
>>> Cc: <megaco@ietf.org>
>>> Sent: Thursday, December 08, 2011 12:24 AM
>>> Subject: RE: [AVTCORE] Types of monitoring architectures; RE:
>>> I-D Action: draft-ietf-avtcore-monarch-08.txt
>>> 
>>> 
>>> Qin,
>>> that's NOT the point.
>>> 
>>> All RFC 3550 and RFC 5117 RTP components are FUNCTIONAL
>> ENTITIES (FE).
>>> e.g.,
>>> - the RTP Monitor or RTP receiver FE may be located in
>>> different PHYSICAL ENTITIES (PE), e.g.
>>>        a1) a user equipment
>>>        a2) a RTP-to-PSTN gateway
>>>        a3) an IP-to-IP session border gateway (in a
>>> back-to-back RTP endsystem topology)
>>>        a3) ...
>>> 
>>> - the RTP Monitor may be associated to an RTP transport
>> translator ...
>>>        b1) an IP-to-IP session border gateway
>>> 
>>> The "RTP monitoring architecture" is IMPACTED by each
>>> functional-to-physical mapping because e.g.
>>> * QoE related metrics are questionable in case of a2
>>> ("despite the fact of a RTP receiver function")
>>> * application level metrics at the location of a RTP
>>> transport translator are a contradiction in itself
>>> * ...
>>> 
>>> Again, it's not really changing the MONARCH draft because in
>>> the very majority of scenarios it is correct. However, there
>>> are few cases where the MONARCH description would be "too
>>> high level", "not fully correct", "lead to possible wrong
>>> expectations", ...
>>> 
>>> Regards,
>>> Albrecht
>>> 
>>> 
>>> 
>>>> -----Original Message-----
>>>> From: Qin Wu [mailto:bill.wu@huawei.com]
>>>> Sent: Dienstag, 6. Dezember 2011 07:13
>>>> To: Schwarz, Albrecht (Albrecht); avt@ietf.org
>>>> Cc: megaco@ietf.org
>>>> Subject: Re: [AVTCORE] Types of monitoring architectures; RE:
>>>> I-D Action: draft-ietf-avtcore-monarch-08.txt
>>>> 
>>>> If you talk about existing RFC5117 RTP topology components,
>>>> this has already been covered by the current version of
>>>> draft-ietf-avtcore-monarch.
>>>> In most cases, an RTP system using RTCP XR is architecturally
>>>> no different from an RTP system which does not use RTCP XR.
>>>> 
>>>> Regards!
>>>> -Qin
>>>> ----- Original Message -----
>>>> From: "Schwarz, Albrecht (Albrecht)"
>>>> <albrecht.schwarz@alcatel-lucent.com>
>>>> To: "Qin Wu" <bill.wu@huawei.com>; <avt@ietf.org>
>>>> Cc: <megaco@ietf.org>
>>>> Sent: Monday, December 05, 2011 10:48 PM
>>>> Subject: RE: [AVTCORE] Types of monitoring architectures; RE:
>>>> I-D Action: draft-ietf-avtcore-monarch-08.txt
>>>> 
>>>> 
>>>> Hello Qin,
>>>> 
>>>> to 1) Physical monitoring architecture
>>>> Of course consideration of generic physical entities (PE),
>>>> not specific to any network reference architectures defined
>>>> by SDOs (like your refered entities).
>>>> There would be just a few PE types ("given by the limited set
>>>> of RTP topology components (RFC 5117)").
>>>> 
>>>> to 2) (RFC 3550) Monitor function
>>>> Right, that's a functional entity. The applicability of a
>>>> monitor may be limited, dependent on ... (like in P.NAMS).
>>>> 
>>>> to 3) your IMS network example
>>>> Don't see the need to refer from MONARCH to a specific
>>>> network architecture like IMS.
>>>> Please also note that IMS is a functional architecture, not a
>>>> physical architecture.
>>>> 
>>>> Regards,
>>>> Albrecht
>>>> 
>>>> PS
>>>> There are multiple options for adding the "RTP monitoring
>>>> architecture" to a functional/physical network architecture:
>>>> a) integrated approach: extension of existing functional
>>>> entities or/and addition of RTP monitoring architectural
>>>> components, extension or/and addition of
>>>> signalling/management interfaces for control and
>>>> configuration of RTP monitoring services, and reporting
>>>> interfaces for measurement data ...
>>>> b) overlay approach: separate specification to ...
>>>> 
>>>> 
>>>> PSS
>>>> BTW: there's a discussion paper with regards to the location
>>>> of a monitor function in an IMS H.248 gateway entity:
>>>> Measurements and statistics in IMS - Use Cases
>>>> http://www.3gpp.org/ftp/tsg_ct/WG3_interworking_ex-CN3/TSGC3_5
>>>> 8_Kyoto_Japan/Docs/C3-100469.zip
>>>> This is just fyi.
>>>> 
>>>> 
>>>> 
>>>>> -----Original Message-----
>>>>> From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On
>>>>> Behalf Of Qin Wu
>>>>> Sent: Freitag, 2. Dezember 2011 02:55
>>>>> To: Schwarz, Albrecht (Albrecht); avt@ietf.org
>>>>> Cc: megaco@ietf.org
>>>>> Subject: Re: [AVTCORE] Types of monitoring architectures; RE:
>>>>> I-D Action: draft-ietf-avtcore-monarch-08.txt
>>>>> 
>>>>> Hi, Albrecht:
>>>>> No offence, I am not really convinced with your proposal on
>>>>> physical monitoring architecture.
>>>>> my counterquestion is what does physical monitoring
>>>>> architecture looks like in your mind?
>>>>> How many components do we have in such physical monitroing
>>>>> architecture? what are they?
>>>>> Take IMS network architecture as a example, they may have
>>>>> P-CSCF,S-CSCF, SIP PBX, SBC, why do you believe monitor
>>>>> described in draft-ietf-avtcore-monarch is mapped into
>>>>> P-CSCF, S-CSCF, SBC, Media Gateway, Media Gateway Controller
>>>>> should be in the scope of IETF RTP monitoring
>> archtiecture draft?
>>>>> 
>>>>> Monitor described in  draft-ietf-avtcore-monarch is well
>>>>> defined in the section 3 of RFC3550 as follows:
>>>>> "
>>>>> 
>>>>>   Monitor: An application that receives RTCP packets sent by
>>>>>      participants in an RTP session, in particular the
>> reception
>>>>>      reports, and estimates the current quality of service for
>>>>>      distribution monitoring, fault diagnosis and long-term
>>>>> statistics.
>>>>>      The monitor function is likely to be built into the
>>>>> application(s)
>>>>>      participating in the session, but may also be a separate
>>>>>      application that does not otherwise participate and
>>>>> does not send
>>>>>      or receive the RTP data packets (since they are on
>>> a separate
>>>>>      port).  These are called third-party monitors.  It is also
>>>>>      acceptable for a third-party monitor to receive
>> the RTP data
>>>>>      packets but not send RTCP packets or otherwise be
>>>> counted in the
>>>>>      session.
>>>>> 
>>>>> "
>>>>> Isn't how to implent monitor into IMS netowork archtiecture a
>>>>> implentation specific issue?
>>>>> If this issue are really interesting, isn't it a good idea to
>>>>> produce another new document to talk about this?
>>>>> One good example for this motivation is this draft I like to
>>>>> share with you:
>>>>> http://tools.ietf.org/html/draft-kaplan-dispatch-b2bua-taxonom
>>>>> y-00#section-4.6
>>>>> 
>>>>> Regards!
>>>>> -Qin
>>>>> ----- Original Message -----
>>>>> From: "Schwarz, Albrecht (Albrecht)"
>>>>> <albrecht.schwarz@alcatel-lucent.com>
>>>>> To: "Qin Wu" <bill.wu@huawei.com>; <avt@ietf.org>
>>>>> Cc: <megaco@ietf.org>
>>>>> Sent: Friday, December 02, 2011 12:20 AM
>>>>> Subject: RE: [AVTCORE] Types of monitoring architectures; RE:
>>>>> I-D Action: draft-ietf-avtcore-monarch-08.txt
>>>>> 
>>>>> 
>>>>> My replies below ...
>>>>> -Albrecht
>>>>> 
>>>>>> -----Original Message-----
>>>>>> From: Qin Wu [mailto:bill.wu@huawei.com]
>>>>>> Sent: Donnerstag, 1. Dezember 2011 02:42
>>>>>> To: Schwarz, Albrecht (Albrecht); avt@ietf.org
>>>>>> Cc: megaco@ietf.org
>>>>>> Subject: Re: [AVTCORE] Types of monitoring architectures; RE:
>>>>>> I-D Action: draft-ietf-avtcore-monarch-08.txt
>>>>>> 
>>>>>> Hi,
>>>>>> ----- Original Message -----
>>>>>> From: "Schwarz, Albrecht (Albrecht)"
>>>>>> <albrecht.schwarz@alcatel-lucent.com>
>>>>>> To: "Qin Wu" <bill.wu@huawei.com>; <avt@ietf.org>
>>>>>> Cc: <megaco@ietf.org>
>>>>>> Sent: Thursday, December 01, 2011 1:24 AM
>>>>>> Subject: RE: [AVTCORE] Types of monitoring architectures; RE:
>>>>>> I-D Action: draft-ietf-avtcore-monarch-08.txt
>>>>>> 
>>>>>> 
>>>>>> My replies below inline,
>>>>>> Albrecht
>>>>>> 
>>>>>>> -----Original Message-----
>>>>>>> From: Qin Wu [mailto:bill.wu@huawei.com]
>>>>>>> Sent: Mittwoch, 30. November 2011 04:51
>>>>>>> To: Schwarz, Albrecht (Albrecht); avt@ietf.org
>>>>>>> Cc: megaco@ietf.org
>>>>>>> Subject: Re: [AVTCORE] Types of monitoring
>> architectures; RE:
>>>>>>> I-D Action: draft-ietf-avtcore-monarch-08.txt
>>>>>>> 
>>>>>>> Hi,
>>>>>>> ----- Original Message -----
>>>>>>> From: "Schwarz, Albrecht (Albrecht)"
>>>>>>> <albrecht.schwarz@alcatel-lucent.com>
>>>>>>> To: <avt@ietf.org>
>>>>>>> Cc: <megaco@ietf.org>
>>>>>>> Sent: Tuesday, November 29, 2011 7:32 PM
>>>>>>> Subject: [AVTCORE] Types of monitoring
>> architectures; RE: I-D
>>>>>>> Action: draft-ietf-avtcore-monarch-08.txt
>>>>>>> 
>>>>>>> 
>>>>>>>> Dear All,
>>>>>>>> 
>>>>>>>> there are different types of monitoring architectures,
>>>>>>> particularily from perspective of QoE related performance
>>>>>> parameters.
>>>>>>>> Let's recall QoE (e.g., ITU-T P.10 Amendment 2):
>>>>>>>> 
>>>>>>>> Quality of Experience (QoE):
>>>>>>>> The overall acceptability of an application or service, as
>>>>>>> perceived subjectively by the end-user.
>>>>>>>> NOTE 1 - Quality of experience includes the complete
>>>>>>> end-to-end system effects (client, terminal, network,
>>>>>>> services infrastructure, etc.).
>>>>>>>> NOTE 2 - Overall acceptability may be influenced by user
>>>>>>> expectations and context.
>>>>>>>> 
>>>>>>>> Important for MONARCH:
>>>>>>>> 1st ... perceived by end-user
>>>>>>>> 2nd QoE includes the complete end-to-end sytem effects ...
>>>>>>>> 
>>>>>>>> That said, present RTP monitoring architecture in MONARCH
>>>>>>> according clause 3 is not specific on the type of monitoring
>>>>>>> architecture. For instance, Fig. 1, it is possibly supposed
>>>>>>> that the "RTP Sender" and "RTP Receiver" entities are equal
>>>>>>> to a terminal/user equipment (UE). This would be an
>>>>>>> end-to-end IP network scenario.
>>>>>>>> 
>>>>>>>> However, the "RTP Sender" and "RTP Receiver" entities may
>>>>>>> be also located at the edge of an IP network, e.g. in a
>>>>>>> gateway for IP-to-non-IP interworking, i.e. an UE located in
>>>>>>> the non-IP network part.
>>>>>>>> Note: such scenarios are considered by MEGACO gateways
>>>>>>> (I've Cc'd megaco list).
>>>>>>>> 
>>>>>>>> An RTP Sender/Receiver located NOT in the UE
>> would question
>>>>>>> the value of RTP/RTCP QoE related performance measurements
>>>>>>> (because the UE is located outside the RTP domain).
>>>>>>>> 
>>>>>>>> Conclusions:
>>>>>>>> - the set of meaningful performance metrics may be
>>>>>>> dependent on the location of the RTP Sender/Receiver, e.g.
>>>>>>> whether in a UE, gateway, ...
>>>>>>>> - don't see any impact on transport level metrics
>>>>>>>> - ... but the set of meaningful application level metrics
>>>>>>>> 
>>>>>>>> Proposal for MONARCH:
>>>>>>>> #1: insert sub-clause title "3.1 End-to-end IP network
>>>>>>> architecture" below clause 3
>>>>>>>> 
>>>>>>>> #2: add a sub-clause 3.2 at the end of clause 3, sth like
>>>>>>>> 
>>>>>>>> "3.2 RTP Sender/Receiver entities located in network nodes
>>>>>>>> The location of the RTP Sender/Receiver entity may impact
>>>>>>> the set of meaningful metrics.
>>>>>>>> For instance: application level metrics for QoE related
>>>>>>> performance metrics are questionable (or doesn't really make
>>>>>>> sense at all) when measured in a network node (terminating
>>>>>>> the RTP) instead of the user equipment."
>>>>>>>> 
>>>>>>>> Something like this would help to avoid confusion.
>>>>>>>> I even believe that a QoE measurement in a network node
>>>>>>> would violate the QoE definition. Would be rather something
>>>>>>> like QoE* ("remote QoE"):-(
>>>>>>>> 
>>>>>>>> Such information would improve the MONARCH doc in
>>> my opinion.
>>>>>>>> Sorry for that late comment.
>>>>>>>> Any views?
>>>>>>> 
>>>>>>> [Qin]:
>>>>>>> Albrrecht, if you follow ealry list discussion on
>>>>>>> draft-hunt-avt-monarch-01, you will see the rough consensus
>>>>>>> to position this document was
>>>>>>> this daft should focus on guidelines for defining reporting
>>>>>>> blocks. That is to say the main purpose of MONARCH draft
>>>>> is how to
>>>>>>> provide guidelines for the development of new RTCP XR block
>>>>>>> types in XRBlock working group.
>>>>>> 
>>>>>> [ABS] ... then the title "monitoring architectures" is
>>> misleading.
>>>>>> Proposal: keep title, revise scope section on focus
>>>>>> 
>>>>>> [Qin]: No, the title is *RTP* monitoring architecture, we can
>>>>>> not expand scope into IP monitoring architecture.
>>>>> 
>>>>> [ABS] That's wasn't the intent! Did just focus on the key word.
>>>>> 
>>>>>> 
>>>>>>> 
>>>>>>> Therefore how and where to collect the metric from RTP
>>>>>>> endpoint is not scope of this document, in my opinion. since
>>>>>>> you may have many ways to do this and different vendors have
>>>>>>> their different appoaches. It will be better to leave this
>>>>>>> beyond the scope. But you are right, it will be more
>>>>>>> reasonable to measure QoE related performance metric at the
>>>>>>> RTP receiver.
>>>>>> 
>>>>>> [ABS] I would disagree. At least your statement should be
>>>>>> conditional, sth like
>>>>>> "QoE related performance metrics may be measured in a RTP
>>>>>> receiver, IF the RTP receiver function is located in user
>>>>>> equipment (e.g. IP terminal), because QoE performance metrics
>>>>>> are tightly coupled to the point of view of a 'user'.
>>>>>> ... IF NOT, then ..."
>>>>>> 
>>>>>> [Qin]: I am not sure user equipment or IP terminal is the
>>>>>> right term from RTP perspective.
>>>>>> 
>>>>>> Also if you read P.NAMS, P.NAMS model for calculating QoE
>>>>>> related metric can be placed either at the network or at
>>>> the client.
>>>>>> So I disagree with what you said.
>>>>> 
>>>>> [ABS] Not convinced at all.
>>>>> Guess you are referring to the "mid-point" models, right?
>>>>> The usage of such that models depends on "prior knowledge
>>>>> ..." information.
>>>>> Thus, the applicability is conditional. You may not make such
>>>>> a general statement.
>>>>> 
>>>>> 
>>>>>> 
>>>>>> Also as I said, how and where to collect the metric from RTP
>>>>>> endpoint is not scope of this document. It depends on the
>>>>>> model you are choosing, e.g., four operation modes specified
>>>>>> in P.NAMS.
>>>>>> Apparently this should not be specified again in RTP
>>>>>> monitoring architecture document.
>>>>>> 
>>>>>>> 
>>>>>>> Another point is it is not clear to me how RTP
>> monitoring has
>>>>>>> to do with architectureend to end IP network architecture .
>>>>>>> this draft mostly focus on discussing RTP level stuff.
>>>>>>> Therefore I am quite doubt that we should describe anything
>>>>>>> in this document like how
>>>>>>> RTP entties is mapped into network entities/nodes at
>>>> the IP layer.
>>>>>> 
>>>>>> [ABS] I don't got any problems to talk about architectural
>>>>>> framework for monitoring in this document. Such information
>>>>>> is required and this is the only IETF AVT doc about it.
>>>>>> The solution to this issue is rather simple to me:
>>>>>> - split the MONARCH "monitoring architecture" in
>>>>>> 1) a functional monitoring architecture (let's call it
>>> 'FMA') and
>>>>>> 2) a physical monitoring architecture (... 'PMA').
>>>>>> 
>>>>>> - the present MONARCH doc would describe the FMA at the level
>>>>>> of RTP entities (i.e., Fig. 1 entities, incl. all the RTP
>>>>>> topology components according RFC 5117)
>>>>>> 
>>>>>> - there are many options of functional-to-physical mappings,
>>>>>> i.e. how a FMA would be mapped on a PMA
>>>>>> - the mapping is typically dependent on considered network
>>>>>> architecture (like SIP, H.323, MGCP, IMS, wireless, etc
>>> networks)
>>>>>> 
>>>>>> - the present MONARCH doc would describe the FMA-to-PMA
>>>>>> mapping IF all RTP receiver/sender entities would be located
>>>>>> in physical IP terminals (UEs)
>>>>>> - etc
>>>>>> 
>>>>>> [Qin]: I can understand your point, but you can not do that.
>>>>>> Since this document is only focus on *RTP* monitoring
>>>>>> architecture, that is what it said in AVTCore milestone:
>>>>>> "
>>>>>> 
>>>>>> Goals and Milestones:
>>>>>> 
>>>>>>  Feb 2011 - Submit Monitoring Architecture for RTP for
>>>>> Informational
>>>>>> 
>>>>>> "
>>>>> 
>>>>> [ABS] If you go back to my first email on this subject, and
>>>>> if you look at my proposal: that's not a lot, nothing which
>>>>> violates the charter, goals and milestones.
>>>>> 
>>>>> 
>>>>>> Also if you really don't see how to map FMA to PMA, you may
>>>>>> look at the P.NAMS models specifed in ITU-T P.NAMS.
>>>>>> As for how to use RTP monitoring architecture or RTP XR
>>>>>> Report in the IMS network architecture, you may look at:
>>>>>> http://tools.ietf.org/html/rfc6035
>>>>> 
>>>>> [ABS] That's the SIP reporting interface, i.e., applicable
>>>>> primarily for physical IP user equipment with embedded RTP
>>>>> sender/receiver function and SIP UA function.
>>>>> However, the applicability of RFC 6035 is limited for a
>>>>> SIP-to-PSTN gateway (because the RTP sender/receiver would be
>>>>> located NOT in user equipment. Also the P.NAMS mid-point
>>>>> model fails for such a scenario.
>>>>> 
>>>>>> ITU-T H.248.48.
>>>>>> But I haven't check the current status of H.248.48.
>>>>> 
>>>>> [ABS] Work is finalized, see
>>>>> http://www.itu.int/md/meetingdoc.asp?lang=en&parent=T09-SG16-1
>>>>> 11121-TD-PLEN-0419
>>>>> 
>>>>>> 
>>>>>>> 
>>>>>>> But as the author of this document, I am interested and open
>>>>>>> to other opinions.:-)
>>>>>> 
>>>>>> [ABS] Like to add a further aspect: a "functional monitoring
>>>>>> architecture" may be considered as a network overlay,
>>>>>> something which adds additional capabilities (here:
>>>>>> measurement services, reporting services on top of basic RTP
>>>>>> services).
>>>>>> Such an overlay concept is nothing new: e.g., the
>>>>>> MultiService Forum did define a "Performance Measurement &
>>>>>> Monitoring (PMM)" overlay network, or IETF RMON may be also
>>>>>> considered as such.
>>>>>> 
>>>>>>> 
>>>>>>>> Regards,
>>>>>>>> Albrecht
>>>>>>>> 
>>>>>>>> 
>>>>>>>> 
>>>>>>>> 
>>>>>>>>> -----Original Message-----
>>>>>>>>> From: avt-bounces@ietf.org
>> [mailto:avt-bounces@ietf.org] On
>>>>>>>>> Behalf Of internet-drafts@ietf.org
>>>>>>>>> Sent: Dienstag, 29. November 2011 08:56
>>>>>>>>> To: i-d-announce@ietf.org
>>>>>>>>> Cc: avt@ietf.org
>>>>>>>>> Subject: [AVTCORE] I-D Action:
>>>>> draft-ietf-avtcore-monarch-08.txt
>>>>>>>>> 
>>>>>>>>> 
>>>>>>>>> A New Internet-Draft is available from the on-line
>>>>>>>>> Internet-Drafts directories. This draft is a work
>>> item of the
>>>>>>>>> Audio/Video Transport Core Maintenance Working Group
>>>>> of the IETF.
>>>>>>>>> 
>>>>>>>>> Title           : Monitoring Architectures for RTP
>>>>>>>>> Author(s)       : Qin Wu
>>>>>>>>>                          Geoff Hunt
>>>>>>>>>                          Philip Arden
>>>>>>>>> Filename        : draft-ietf-avtcore-monarch-08.txt
>>>>>>>>> Pages           : 25
>>>>>>>>> Date            : 2011-11-28
>>>>>>>>> 
>>>>>>>>>   This memo proposes an architecture for
>>> extending RTCP with
>>>>>>>>> a new RTCP
>>>>>>>>>   XR (RFC3611) block type to report new metrics
>>>>> regarding media
>>>>>>>>>   transmission or reception quality, following RTCP
>>>> guideline
>>>>>>>>>   established in RFC5968.  This memo suggests that a new
>>>>>>> block should
>>>>>>>>>   contain a single metric or a small number of metrics
>>>>>>> relevant to a
>>>>>>>>>   single parameter of interest or concern, rather than
>>>>>>> containing a
>>>>>>>>>   number of metrics which attempt to provide
>> full coverage
>>>>>>>>> of all those
>>>>>>>>>   parameters of concern to a specific application.
>>>>>>> Applications may
>>>>>>>>>   then "mix and match" to create a set of blocks which
>>>>>>>>> covers their set
>>>>>>>>>   of concerns.  Where possible, a specific
>> block should be
>>>>>>>>> designed to
>>>>>>>>>   be re-usable across more than one application, for
>>>>>>> example, for all
>>>>>>>>>   of voice, streaming audio and video.
>>>>>>>>> 
>>>>>>>>> 
>>>>>>>>> A URL for this Internet-Draft is:
>>>>>>>>> 
>>>>>>> 
>>>>>> 
>>>>> 
>>>> 
>>> 
>> http://www.ietf.org/internet-drafts/draft-ietf-avtcore-monarch-08.txt
>>>>>>>>> 
>>>>>>>>> Internet-Drafts are also available by anonymous FTP at:
>>>>>>>>> ftp://ftp.ietf.org/internet-drafts/
>>>>>>>>> 
>>>>>>>>> This Internet-Draft can be retrieved at:
>>>>>>>>> 
>>>>>>> 
>>>>> 
>>> ftp://ftp.ietf.org/internet-drafts/draft-ietf-avtcore-monarch-08.txt
>>>>>>>>> 
>>>>>>>>> _______________________________________________
>>>>>>>>> Audio/Video Transport Core Maintenance
>>>>>>>>> avt@ietf.org
>>>>>>>>> https://www.ietf.org/mailman/listinfo/avt
>>>>>>>>> 
>>>>>>>> _______________________________________________
>>>>>>>> Audio/Video Transport Core Maintenance
>>>>>>>> avt@ietf.org
>>>>>>>> https://www.ietf.org/mailman/listinfo/avt
>>>>>>> 
>>>>>> =
>>>>> _______________________________________________
>>>>> Audio/Video Transport Core Maintenance
>>>>> avt@ietf.org
>>>>> https://www.ietf.org/mailman/listinfo/avt
>>>>> 
>>>> 
>>> 
>> 
> _______________________________________________
> Audio/Video Transport Core Maintenance
> avt@ietf.org
> https://www.ietf.org/mailman/listinfo/avt



-- 
Colin Perkins
http://csperkins.org/




From albrecht.schwarz@alcatel-lucent.com  Tue Dec 13 03:16:48 2011
Return-Path: <albrecht.schwarz@alcatel-lucent.com>
X-Original-To: megaco@ietfa.amsl.com
Delivered-To: megaco@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B28AD21F8876; Tue, 13 Dec 2011 03:16:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.335
X-Spam-Level: 
X-Spam-Status: No, score=-5.335 tagged_above=-999 required=5 tests=[AWL=-0.286, BAYES_00=-2.599, HELO_EQ_FR=0.35, J_CHICKENPOX_14=0.6, J_CHICKENPOX_74=0.6, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XHWgToCgBwmR; Tue, 13 Dec 2011 03:16:46 -0800 (PST)
Received: from smail2.alcatel.fr (smail2.alcatel.fr [64.208.49.57]) by ietfa.amsl.com (Postfix) with ESMTP id C1D0F21F85FF; Tue, 13 Dec 2011 03:16:45 -0800 (PST)
Received: from FRMRSSXCHHUB03.dc-m.alcatel-lucent.com (FRMRSSXCHHUB03.dc-m.alcatel-lucent.com [135.120.45.63]) by smail2.alcatel.fr (8.14.3/8.14.3/ICT) with ESMTP id pBDBGWPK026461 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Tue, 13 Dec 2011 12:16:32 +0100
Received: from FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com ([135.120.45.50]) by FRMRSSXCHHUB03.dc-m.alcatel-lucent.com ([135.120.45.63]) with mapi; Tue, 13 Dec 2011 12:16:32 +0100
From: "Schwarz, Albrecht (Albrecht)" <albrecht.schwarz@alcatel-lucent.com>
To: Qin Wu <bill.wu@huawei.com>, Colin Perkins <csp@csperkins.org>
Date: Tue, 13 Dec 2011 12:16:31 +0100
Thread-Topic: [AVTCORE] Types of monitoring architectures; RE:  I-D Action: draft-ietf-avtcore-monarch-08.txt
Thread-Index: Acy5PRkYFRCRYXF7SU232NZnMDRe1gAS1e7g
Message-ID: <5F7BCCF5541B7444830A2288ABBEBC9621620F54B6@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com>
References: <20111129075613.12419.4377.idtracker@ietfa.amsl.com> <EAC481B4D8034C38AC54E1217F8D875D@china.huawei.com> <5F7BCCF5541B7444830A2288ABBEBC96216190077F@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com> <B527BAFA038842A8939A8C2D558074CD@china.huawei.com> <5F7BCCF5541B7444830A2288ABBEBC962161900908@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com> <9FF9B04A84E64AD7ABCCC4F2ACC1E19A@china.huawei.com> <5F7BCCF5541B7444830A2288ABBEBC9621620F4AF5@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com> <D44A4820E0D24DD79F6F5A4B7507D0D6@china.huawei.com> <5F7BCCF5541B7444830A2288ABBEBC9621620F4ED2@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com> <71112008FBA94D35B07FA6B4916075B6@china.huawei.com> <5F7BCCF5541B7444830A2288ABBEBC9621620F5258@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com> <6C618D1EA52146A781429C6B08C4A4FC@china.huawei.com> <5F7BCCF5541B7444830A2288ABBEBC9621620F5330@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com> <2BEF8708-58B8-4AEB-B3A6-702F46E58C12@csperkins.org> <CFFAC080E70043A5BD4536349C34EFDB@china.huawei.com>
In-Reply-To: <CFFAC080E70043A5BD4536349C34EFDB@china.huawei.com>
Accept-Language: de-DE, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: de-DE, en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.69 on 155.132.188.80
Cc: "megaco@ietf.org" <megaco@ietf.org>, "avt@ietf.org" <avt@ietf.org>
Subject: Re: [Megaco] [AVTCORE] Types of monitoring architectures; RE:  I-D Action: draft-ietf-avtcore-monarch-08.txt
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.1.12
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: Tue, 13 Dec 2011 11:16:48 -0000

> Albrecht, Qin,
>
> It doesn't seem controversial that some metrics are only
> meaningful in some scenarios, or when measured at certain
> points in a system. I don't see how adding a statement to the
> monarch draft to recognise that could be problematic. Is
> there anything else being suggested here?
>
> Colin

Right.
No, nothing else is suggested.
(Send yesterday also an update proposal with initial text.)

Albrecht



> -----Original Message-----
> From: Qin Wu [mailto:bill.wu@huawei.com]
> Sent: Dienstag, 13. Dezember 2011 03:15
> To: Colin Perkins; Schwarz, Albrecht (Albrecht)
> Cc: avt@ietf.org; megaco@ietf.org
> Subject: Re: [AVTCORE] Types of monitoring architectures; RE:
> I-D Action: draft-ietf-avtcore-monarch-08.txt
>
> Hi, Colin:
> Thank for your suggestion. Besides Albrecht's proposed text,
> my additional proposal is to fix application level metric
> defintion in section 2 OLD text:
> "
>    Application level metrics
>
>       Metrics relating to QoE related parameters.  These metrics are
>       measured at the application level and focus on quality
> of content
>       rather than network parameters.
> "
> New text
> "
>    Application level metrics
>
>       Metrics relating to application specific parameters or
> QoE related parameters.
>      Application specific parameters  are measured at the
> application level and focus
>      on quality of content rather than network performance.
> QoE related parameters
>      reflect the end-to-end performance at the services level
> and is ususally measured
>      at the user endpoint.
> "
>
> Regards!
> -Qin
> ----- Original Message -----
> From: "Colin Perkins" <csp@csperkins.org>
> To: "Schwarz, Albrecht (Albrecht)"
> <albrecht.schwarz@alcatel-lucent.com>
> Cc: "Qin Wu" <bill.wu@huawei.com>; <avt@ietf.org>; <megaco@ietf.org>
> Sent: Tuesday, December 13, 2011 12:56 AM
> Subject: Re: [AVTCORE] Types of monitoring architectures; RE:
> I-D Action: draft-ietf-avtcore-monarch-08.txt
>
>
> Albrecht, Qin,
>
> It doesn't seem controversial that some metrics are only
> meaningful in some scenarios, or when measured at certain
> points in a system. I don't see how adding a statement to the
> monarch draft to recognise that could be problematic. Is
> there anything else being suggested here?
>
> Colin
>
>
> On 12 Dec 2011, at 10:33, Schwarz, Albrecht (Albrecht) wrote:
> > Hi Qin,
> >
> > I'm very aware about all that.
> > It looks like that you are now agreeing that QoE
> measurements are CONDITIONAL ("you got a number of IF
> statements, there might be even more ...").
> >
> > MONARCH is not talking about such conditions, thus some
> readers may got the impression that the metrics related to
> RTP traffic are UNCONDITIONAL (which is not true as you confirmed).
> >
> > If you go back to my very first email: I did just propose
> to indicate the conditional aspect. Don't understand why such
> kind of valuable info would be not in scope of MONARCH. Hm?
> >
> > Regards,
> > Albrecht
> >
> > PS
> > I did use the notion of a control plane agnostic
> "RTP-to-PSTN gateway". You did indicate control plane
> specific gateway types like SIP-to-PSTN or SIP-to-H.323. Now
> issue to use such signalling protocol specific examples, but
> it doesn't change the underlying issue.
> > The SIP side reporting capability based on RFC 6035 allows
> to report the outlined measurements, but the RFC itself does
> not specify whether the reported information is meaningful
> (which is OK because this is not subject of a reporting
> interface spec, it is rather subject of a network monitoring
> doc like MONARCH).
> > QoE measurements would be conditional in both gateway types
> (because such a gateway is NOT a user device despite the fact
> of an embedded SIP user agent entity).
> > Actually I would even question here the condition of
> "customer knows the original content" in many real network scenarios.
> >
> >
> >
> >> -----Original Message-----
> >> From: Qin Wu [mailto:bill.wu@huawei.com]
> >> Sent: Montag, 12. Dezember 2011 05:05
> >> To: Schwarz, Albrecht (Albrecht); avt@ietf.org
> >> Cc: megaco@ietf.org
> >> Subject: Re: [AVTCORE] Types of monitoring architectures; RE:
> >> I-D Action: draft-ietf-avtcore-monarch-08.txt
> >>
> >> Hi, Albrecht:
> >> My understanding to QoE measurment is:
> >> The factors that influence the QoE metric include encoding
> >> system, transport network, access network,home network and
> end device.
> >> If the customer(e.g., network operator) doesn't know the
> >> original content, the QoE metric should be usually measured
> >> at the user device.
> >> If the customer knows the original content, the QoE metric
> >> can be measured either in the network or at the user device.
> >> Given the growing popularity of connected devices, these
> >> devices may have different capability corresponding to CPU
> >> load, processing overhead, storage, batteries.
> >> If the cusomer want to measure QoE without considering
> >> connected devices with various capability , the QoE metric
> >> can be measured at the point between access network and
> home network.
> >>
> >> Regarding the monitoring scenario you mentioned, I am not
> >> familiar with such scenario with RTP-to-PSTN gateway deployed.
> >> But I am aware that there are scenarios with SIP to PSTN
> >> gateway or SIP to H.323 gateway widely deployed,  RFC6035
> >> defines a new SIP event package, vq-rtcpxr that enable the
> >> collection and  reporting of metrics that measure quality for
> >> RTP sessions. In such cases, RTCP XR VOIP metric with QoE
> >> metric included is measured at the user device and mapped
> >> into the equivalent SIP vq-rtcpxr parameter since SIP session
> >> call is established end to end and RTP media stream is
> >> exchanged directly between one endpoint and the other endpoint.
> >>
> >> Regards!
> >> -Qin
> >> ----- Original Message -----
> >> From: "Schwarz, Albrecht (Albrecht)"
> >> <albrecht.schwarz@alcatel-lucent.com>
> >> To: "Qin Wu" <bill.wu@huawei.com>; <avt@ietf.org>
> >> Cc: <megaco@ietf.org>
> >> Sent: Saturday, December 10, 2011 12:01 AM
> >> Subject: RE: [AVTCORE] Types of monitoring architectures; RE:
> >> I-D Action: draft-ietf-avtcore-monarch-08.txt
> >>
> >>
> >> How do you explain to a network operator the value of QoE
> >> measurements by an RTP receiver / RTP monitor component
> >> located in an RTP-to-PSTN gateway?
> >>
> >> This would be a monitoring scenario inline with MONARCH, but
> >> with valueless QoE results, right?
> >>
> >>
> >>> -----Original Message-----
> >>> From: Qin Wu [mailto:bill.wu@huawei.com]
> >>> Sent: Donnerstag, 8. Dezember 2011 03:26
> >>> To: Schwarz, Albrecht (Albrecht); avt@ietf.org
> >>> Cc: megaco@ietf.org
> >>> Subject: Re: [AVTCORE] Types of monitoring architectures; RE:
> >>> I-D Action: draft-ietf-avtcore-monarch-08.txt
> >>>
> >>> You reiterate what you propose for physical entities in the
> >>> early email.
> >>> I am still not convicing with that.
> >>>
> >>> Since we have RTP components like RTP end system, RTP mixer,
> >>> RTP media translator, RTP transport translator, RTP monitor
> >>> specified in RFC3550 can be built into these component as a
> >>> application. also monitor can be disjointed from these RTP
> >>> components as a third party monitor. why we need to specify
> >>> how to map RTP end system into user equipment, RTP translator
> >>> or RTP mixer can be mapped into RTP-PSTN gateway, or IP to IP
> >>> border gateway since we have already mapped monitor into
> >>> different RTP components.
> >>> How many PE types you can enumerate? why they should be scope
> >>> of RTP monitoring architecture?
> >>>
> >>> Also as specified in MONARCH draft, we have end sytem
> >>> metrics, transport level metric, transport level metric, they
> >>> can be measured and collected from the different RTP
> >>> comoponents specified in RFC3550, RFC5117. Apparently end
> >>> system metric can only be collected from RTP end system.
> >>> transport metric is collected from any RTP system in the RTP
> >>> monitoring architecture, regarding application level metric,
> >>> apparently they should be measured at the application layer
> >>> and can not be collected from RTP transport translator, Also
> >>> RTP transport translator is still a functional entity rather
> >>> than a physical entity. I am not convincing with what you
> >>> said about "contradiction", "lead to possible wrong expectations".
> >>>
> >>> Regards!
> >>> -Qin
> >>> ----- Original Message -----
> >>> From: "Schwarz, Albrecht (Albrecht)"
> >>> <albrecht.schwarz@alcatel-lucent.com>
> >>> To: "Qin Wu" <bill.wu@huawei.com>; <avt@ietf.org>
> >>> Cc: <megaco@ietf.org>
> >>> Sent: Thursday, December 08, 2011 12:24 AM
> >>> Subject: RE: [AVTCORE] Types of monitoring architectures; RE:
> >>> I-D Action: draft-ietf-avtcore-monarch-08.txt
> >>>
> >>>
> >>> Qin,
> >>> that's NOT the point.
> >>>
> >>> All RFC 3550 and RFC 5117 RTP components are FUNCTIONAL
> >> ENTITIES (FE).
> >>> e.g.,
> >>> - the RTP Monitor or RTP receiver FE may be located in
> >>> different PHYSICAL ENTITIES (PE), e.g.
> >>>        a1) a user equipment
> >>>        a2) a RTP-to-PSTN gateway
> >>>        a3) an IP-to-IP session border gateway (in a
> >>> back-to-back RTP endsystem topology)
> >>>        a3) ...
> >>>
> >>> - the RTP Monitor may be associated to an RTP transport
> >> translator ...
> >>>        b1) an IP-to-IP session border gateway
> >>>
> >>> The "RTP monitoring architecture" is IMPACTED by each
> >>> functional-to-physical mapping because e.g.
> >>> * QoE related metrics are questionable in case of a2
> >>> ("despite the fact of a RTP receiver function")
> >>> * application level metrics at the location of a RTP
> >>> transport translator are a contradiction in itself
> >>> * ...
> >>>
> >>> Again, it's not really changing the MONARCH draft because in
> >>> the very majority of scenarios it is correct. However, there
> >>> are few cases where the MONARCH description would be "too
> >>> high level", "not fully correct", "lead to possible wrong
> >>> expectations", ...
> >>>
> >>> Regards,
> >>> Albrecht
> >>>
> >>>
> >>>
> >>>> -----Original Message-----
> >>>> From: Qin Wu [mailto:bill.wu@huawei.com]
> >>>> Sent: Dienstag, 6. Dezember 2011 07:13
> >>>> To: Schwarz, Albrecht (Albrecht); avt@ietf.org
> >>>> Cc: megaco@ietf.org
> >>>> Subject: Re: [AVTCORE] Types of monitoring architectures; RE:
> >>>> I-D Action: draft-ietf-avtcore-monarch-08.txt
> >>>>
> >>>> If you talk about existing RFC5117 RTP topology components,
> >>>> this has already been covered by the current version of
> >>>> draft-ietf-avtcore-monarch.
> >>>> In most cases, an RTP system using RTCP XR is architecturally
> >>>> no different from an RTP system which does not use RTCP XR.
> >>>>
> >>>> Regards!
> >>>> -Qin
> >>>> ----- Original Message -----
> >>>> From: "Schwarz, Albrecht (Albrecht)"
> >>>> <albrecht.schwarz@alcatel-lucent.com>
> >>>> To: "Qin Wu" <bill.wu@huawei.com>; <avt@ietf.org>
> >>>> Cc: <megaco@ietf.org>
> >>>> Sent: Monday, December 05, 2011 10:48 PM
> >>>> Subject: RE: [AVTCORE] Types of monitoring architectures; RE:
> >>>> I-D Action: draft-ietf-avtcore-monarch-08.txt
> >>>>
> >>>>
> >>>> Hello Qin,
> >>>>
> >>>> to 1) Physical monitoring architecture
> >>>> Of course consideration of generic physical entities (PE),
> >>>> not specific to any network reference architectures defined
> >>>> by SDOs (like your refered entities).
> >>>> There would be just a few PE types ("given by the limited set
> >>>> of RTP topology components (RFC 5117)").
> >>>>
> >>>> to 2) (RFC 3550) Monitor function
> >>>> Right, that's a functional entity. The applicability of a
> >>>> monitor may be limited, dependent on ... (like in P.NAMS).
> >>>>
> >>>> to 3) your IMS network example
> >>>> Don't see the need to refer from MONARCH to a specific
> >>>> network architecture like IMS.
> >>>> Please also note that IMS is a functional architecture, not a
> >>>> physical architecture.
> >>>>
> >>>> Regards,
> >>>> Albrecht
> >>>>
> >>>> PS
> >>>> There are multiple options for adding the "RTP monitoring
> >>>> architecture" to a functional/physical network architecture:
> >>>> a) integrated approach: extension of existing functional
> >>>> entities or/and addition of RTP monitoring architectural
> >>>> components, extension or/and addition of
> >>>> signalling/management interfaces for control and
> >>>> configuration of RTP monitoring services, and reporting
> >>>> interfaces for measurement data ...
> >>>> b) overlay approach: separate specification to ...
> >>>>
> >>>>
> >>>> PSS
> >>>> BTW: there's a discussion paper with regards to the location
> >>>> of a monitor function in an IMS H.248 gateway entity:
> >>>> Measurements and statistics in IMS - Use Cases
> >>>> http://www.3gpp.org/ftp/tsg_ct/WG3_interworking_ex-CN3/TSGC3_5
> >>>> 8_Kyoto_Japan/Docs/C3-100469.zip
> >>>> This is just fyi.
> >>>>
> >>>>
> >>>>
> >>>>> -----Original Message-----
> >>>>> From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On
> >>>>> Behalf Of Qin Wu
> >>>>> Sent: Freitag, 2. Dezember 2011 02:55
> >>>>> To: Schwarz, Albrecht (Albrecht); avt@ietf.org
> >>>>> Cc: megaco@ietf.org
> >>>>> Subject: Re: [AVTCORE] Types of monitoring architectures; RE:
> >>>>> I-D Action: draft-ietf-avtcore-monarch-08.txt
> >>>>>
> >>>>> Hi, Albrecht:
> >>>>> No offence, I am not really convinced with your proposal on
> >>>>> physical monitoring architecture.
> >>>>> my counterquestion is what does physical monitoring
> >>>>> architecture looks like in your mind?
> >>>>> How many components do we have in such physical monitroing
> >>>>> architecture? what are they?
> >>>>> Take IMS network architecture as a example, they may have
> >>>>> P-CSCF,S-CSCF, SIP PBX, SBC, why do you believe monitor
> >>>>> described in draft-ietf-avtcore-monarch is mapped into
> >>>>> P-CSCF, S-CSCF, SBC, Media Gateway, Media Gateway Controller
> >>>>> should be in the scope of IETF RTP monitoring
> >> archtiecture draft?
> >>>>>
> >>>>> Monitor described in  draft-ietf-avtcore-monarch is well
> >>>>> defined in the section 3 of RFC3550 as follows:
> >>>>> "
> >>>>>
> >>>>>   Monitor: An application that receives RTCP packets sent by
> >>>>>      participants in an RTP session, in particular the
> >> reception
> >>>>>      reports, and estimates the current quality of service for
> >>>>>      distribution monitoring, fault diagnosis and long-term
> >>>>> statistics.
> >>>>>      The monitor function is likely to be built into the
> >>>>> application(s)
> >>>>>      participating in the session, but may also be a separate
> >>>>>      application that does not otherwise participate and
> >>>>> does not send
> >>>>>      or receive the RTP data packets (since they are on
> >>> a separate
> >>>>>      port).  These are called third-party monitors.  It is also
> >>>>>      acceptable for a third-party monitor to receive
> >> the RTP data
> >>>>>      packets but not send RTCP packets or otherwise be
> >>>> counted in the
> >>>>>      session.
> >>>>>
> >>>>> "
> >>>>> Isn't how to implent monitor into IMS netowork archtiecture a
> >>>>> implentation specific issue?
> >>>>> If this issue are really interesting, isn't it a good idea to
> >>>>> produce another new document to talk about this?
> >>>>> One good example for this motivation is this draft I like to
> >>>>> share with you:
> >>>>> http://tools.ietf.org/html/draft-kaplan-dispatch-b2bua-taxonom
> >>>>> y-00#section-4.6
> >>>>>
> >>>>> Regards!
> >>>>> -Qin
> >>>>> ----- Original Message -----
> >>>>> From: "Schwarz, Albrecht (Albrecht)"
> >>>>> <albrecht.schwarz@alcatel-lucent.com>
> >>>>> To: "Qin Wu" <bill.wu@huawei.com>; <avt@ietf.org>
> >>>>> Cc: <megaco@ietf.org>
> >>>>> Sent: Friday, December 02, 2011 12:20 AM
> >>>>> Subject: RE: [AVTCORE] Types of monitoring architectures; RE:
> >>>>> I-D Action: draft-ietf-avtcore-monarch-08.txt
> >>>>>
> >>>>>
> >>>>> My replies below ...
> >>>>> -Albrecht
> >>>>>
> >>>>>> -----Original Message-----
> >>>>>> From: Qin Wu [mailto:bill.wu@huawei.com]
> >>>>>> Sent: Donnerstag, 1. Dezember 2011 02:42
> >>>>>> To: Schwarz, Albrecht (Albrecht); avt@ietf.org
> >>>>>> Cc: megaco@ietf.org
> >>>>>> Subject: Re: [AVTCORE] Types of monitoring architectures; RE:
> >>>>>> I-D Action: draft-ietf-avtcore-monarch-08.txt
> >>>>>>
> >>>>>> Hi,
> >>>>>> ----- Original Message -----
> >>>>>> From: "Schwarz, Albrecht (Albrecht)"
> >>>>>> <albrecht.schwarz@alcatel-lucent.com>
> >>>>>> To: "Qin Wu" <bill.wu@huawei.com>; <avt@ietf.org>
> >>>>>> Cc: <megaco@ietf.org>
> >>>>>> Sent: Thursday, December 01, 2011 1:24 AM
> >>>>>> Subject: RE: [AVTCORE] Types of monitoring architectures; RE:
> >>>>>> I-D Action: draft-ietf-avtcore-monarch-08.txt
> >>>>>>
> >>>>>>
> >>>>>> My replies below inline,
> >>>>>> Albrecht
> >>>>>>
> >>>>>>> -----Original Message-----
> >>>>>>> From: Qin Wu [mailto:bill.wu@huawei.com]
> >>>>>>> Sent: Mittwoch, 30. November 2011 04:51
> >>>>>>> To: Schwarz, Albrecht (Albrecht); avt@ietf.org
> >>>>>>> Cc: megaco@ietf.org
> >>>>>>> Subject: Re: [AVTCORE] Types of monitoring
> >> architectures; RE:
> >>>>>>> I-D Action: draft-ietf-avtcore-monarch-08.txt
> >>>>>>>
> >>>>>>> Hi,
> >>>>>>> ----- Original Message -----
> >>>>>>> From: "Schwarz, Albrecht (Albrecht)"
> >>>>>>> <albrecht.schwarz@alcatel-lucent.com>
> >>>>>>> To: <avt@ietf.org>
> >>>>>>> Cc: <megaco@ietf.org>
> >>>>>>> Sent: Tuesday, November 29, 2011 7:32 PM
> >>>>>>> Subject: [AVTCORE] Types of monitoring
> >> architectures; RE: I-D
> >>>>>>> Action: draft-ietf-avtcore-monarch-08.txt
> >>>>>>>
> >>>>>>>
> >>>>>>>> Dear All,
> >>>>>>>>
> >>>>>>>> there are different types of monitoring architectures,
> >>>>>>> particularily from perspective of QoE related performance
> >>>>>> parameters.
> >>>>>>>> Let's recall QoE (e.g., ITU-T P.10 Amendment 2):
> >>>>>>>>
> >>>>>>>> Quality of Experience (QoE):
> >>>>>>>> The overall acceptability of an application or service, as
> >>>>>>> perceived subjectively by the end-user.
> >>>>>>>> NOTE 1 - Quality of experience includes the complete
> >>>>>>> end-to-end system effects (client, terminal, network,
> >>>>>>> services infrastructure, etc.).
> >>>>>>>> NOTE 2 - Overall acceptability may be influenced by user
> >>>>>>> expectations and context.
> >>>>>>>>
> >>>>>>>> Important for MONARCH:
> >>>>>>>> 1st ... perceived by end-user
> >>>>>>>> 2nd QoE includes the complete end-to-end sytem effects ...
> >>>>>>>>
> >>>>>>>> That said, present RTP monitoring architecture in MONARCH
> >>>>>>> according clause 3 is not specific on the type of monitoring
> >>>>>>> architecture. For instance, Fig. 1, it is possibly supposed
> >>>>>>> that the "RTP Sender" and "RTP Receiver" entities are equal
> >>>>>>> to a terminal/user equipment (UE). This would be an
> >>>>>>> end-to-end IP network scenario.
> >>>>>>>>
> >>>>>>>> However, the "RTP Sender" and "RTP Receiver" entities may
> >>>>>>> be also located at the edge of an IP network, e.g. in a
> >>>>>>> gateway for IP-to-non-IP interworking, i.e. an UE located in
> >>>>>>> the non-IP network part.
> >>>>>>>> Note: such scenarios are considered by MEGACO gateways
> >>>>>>> (I've Cc'd megaco list).
> >>>>>>>>
> >>>>>>>> An RTP Sender/Receiver located NOT in the UE
> >> would question
> >>>>>>> the value of RTP/RTCP QoE related performance measurements
> >>>>>>> (because the UE is located outside the RTP domain).
> >>>>>>>>
> >>>>>>>> Conclusions:
> >>>>>>>> - the set of meaningful performance metrics may be
> >>>>>>> dependent on the location of the RTP Sender/Receiver, e.g.
> >>>>>>> whether in a UE, gateway, ...
> >>>>>>>> - don't see any impact on transport level metrics
> >>>>>>>> - ... but the set of meaningful application level metrics
> >>>>>>>>
> >>>>>>>> Proposal for MONARCH:
> >>>>>>>> #1: insert sub-clause title "3.1 End-to-end IP network
> >>>>>>> architecture" below clause 3
> >>>>>>>>
> >>>>>>>> #2: add a sub-clause 3.2 at the end of clause 3, sth like
> >>>>>>>>
> >>>>>>>> "3.2 RTP Sender/Receiver entities located in network nodes
> >>>>>>>> The location of the RTP Sender/Receiver entity may impact
> >>>>>>> the set of meaningful metrics.
> >>>>>>>> For instance: application level metrics for QoE related
> >>>>>>> performance metrics are questionable (or doesn't really make
> >>>>>>> sense at all) when measured in a network node (terminating
> >>>>>>> the RTP) instead of the user equipment."
> >>>>>>>>
> >>>>>>>> Something like this would help to avoid confusion.
> >>>>>>>> I even believe that a QoE measurement in a network node
> >>>>>>> would violate the QoE definition. Would be rather something
> >>>>>>> like QoE* ("remote QoE"):-(
> >>>>>>>>
> >>>>>>>> Such information would improve the MONARCH doc in
> >>> my opinion.
> >>>>>>>> Sorry for that late comment.
> >>>>>>>> Any views?
> >>>>>>>
> >>>>>>> [Qin]:
> >>>>>>> Albrrecht, if you follow ealry list discussion on
> >>>>>>> draft-hunt-avt-monarch-01, you will see the rough consensus
> >>>>>>> to position this document was
> >>>>>>> this daft should focus on guidelines for defining reporting
> >>>>>>> blocks. That is to say the main purpose of MONARCH draft
> >>>>> is how to
> >>>>>>> provide guidelines for the development of new RTCP XR block
> >>>>>>> types in XRBlock working group.
> >>>>>>
> >>>>>> [ABS] ... then the title "monitoring architectures" is
> >>> misleading.
> >>>>>> Proposal: keep title, revise scope section on focus
> >>>>>>
> >>>>>> [Qin]: No, the title is *RTP* monitoring architecture, we can
> >>>>>> not expand scope into IP monitoring architecture.
> >>>>>
> >>>>> [ABS] That's wasn't the intent! Did just focus on the key word.
> >>>>>
> >>>>>>
> >>>>>>>
> >>>>>>> Therefore how and where to collect the metric from RTP
> >>>>>>> endpoint is not scope of this document, in my opinion. since
> >>>>>>> you may have many ways to do this and different vendors have
> >>>>>>> their different appoaches. It will be better to leave this
> >>>>>>> beyond the scope. But you are right, it will be more
> >>>>>>> reasonable to measure QoE related performance metric at the
> >>>>>>> RTP receiver.
> >>>>>>
> >>>>>> [ABS] I would disagree. At least your statement should be
> >>>>>> conditional, sth like
> >>>>>> "QoE related performance metrics may be measured in a RTP
> >>>>>> receiver, IF the RTP receiver function is located in user
> >>>>>> equipment (e.g. IP terminal), because QoE performance metrics
> >>>>>> are tightly coupled to the point of view of a 'user'.
> >>>>>> ... IF NOT, then ..."
> >>>>>>
> >>>>>> [Qin]: I am not sure user equipment or IP terminal is the
> >>>>>> right term from RTP perspective.
> >>>>>>
> >>>>>> Also if you read P.NAMS, P.NAMS model for calculating QoE
> >>>>>> related metric can be placed either at the network or at
> >>>> the client.
> >>>>>> So I disagree with what you said.
> >>>>>
> >>>>> [ABS] Not convinced at all.
> >>>>> Guess you are referring to the "mid-point" models, right?
> >>>>> The usage of such that models depends on "prior knowledge
> >>>>> ..." information.
> >>>>> Thus, the applicability is conditional. You may not make such
> >>>>> a general statement.
> >>>>>
> >>>>>
> >>>>>>
> >>>>>> Also as I said, how and where to collect the metric from RTP
> >>>>>> endpoint is not scope of this document. It depends on the
> >>>>>> model you are choosing, e.g., four operation modes specified
> >>>>>> in P.NAMS.
> >>>>>> Apparently this should not be specified again in RTP
> >>>>>> monitoring architecture document.
> >>>>>>
> >>>>>>>
> >>>>>>> Another point is it is not clear to me how RTP
> >> monitoring has
> >>>>>>> to do with architectureend to end IP network architecture .
> >>>>>>> this draft mostly focus on discussing RTP level stuff.
> >>>>>>> Therefore I am quite doubt that we should describe anything
> >>>>>>> in this document like how
> >>>>>>> RTP entties is mapped into network entities/nodes at
> >>>> the IP layer.
> >>>>>>
> >>>>>> [ABS] I don't got any problems to talk about architectural
> >>>>>> framework for monitoring in this document. Such information
> >>>>>> is required and this is the only IETF AVT doc about it.
> >>>>>> The solution to this issue is rather simple to me:
> >>>>>> - split the MONARCH "monitoring architecture" in
> >>>>>> 1) a functional monitoring architecture (let's call it
> >>> 'FMA') and
> >>>>>> 2) a physical monitoring architecture (... 'PMA').
> >>>>>>
> >>>>>> - the present MONARCH doc would describe the FMA at the level
> >>>>>> of RTP entities (i.e., Fig. 1 entities, incl. all the RTP
> >>>>>> topology components according RFC 5117)
> >>>>>>
> >>>>>> - there are many options of functional-to-physical mappings,
> >>>>>> i.e. how a FMA would be mapped on a PMA
> >>>>>> - the mapping is typically dependent on considered network
> >>>>>> architecture (like SIP, H.323, MGCP, IMS, wireless, etc
> >>> networks)
> >>>>>>
> >>>>>> - the present MONARCH doc would describe the FMA-to-PMA
> >>>>>> mapping IF all RTP receiver/sender entities would be located
> >>>>>> in physical IP terminals (UEs)
> >>>>>> - etc
> >>>>>>
> >>>>>> [Qin]: I can understand your point, but you can not do that.
> >>>>>> Since this document is only focus on *RTP* monitoring
> >>>>>> architecture, that is what it said in AVTCore milestone:
> >>>>>> "
> >>>>>>
> >>>>>> Goals and Milestones:
> >>>>>>
> >>>>>>  Feb 2011 - Submit Monitoring Architecture for RTP for
> >>>>> Informational
> >>>>>>
> >>>>>> "
> >>>>>
> >>>>> [ABS] If you go back to my first email on this subject, and
> >>>>> if you look at my proposal: that's not a lot, nothing which
> >>>>> violates the charter, goals and milestones.
> >>>>>
> >>>>>
> >>>>>> Also if you really don't see how to map FMA to PMA, you may
> >>>>>> look at the P.NAMS models specifed in ITU-T P.NAMS.
> >>>>>> As for how to use RTP monitoring architecture or RTP XR
> >>>>>> Report in the IMS network architecture, you may look at:
> >>>>>> http://tools.ietf.org/html/rfc6035
> >>>>>
> >>>>> [ABS] That's the SIP reporting interface, i.e., applicable
> >>>>> primarily for physical IP user equipment with embedded RTP
> >>>>> sender/receiver function and SIP UA function.
> >>>>> However, the applicability of RFC 6035 is limited for a
> >>>>> SIP-to-PSTN gateway (because the RTP sender/receiver would be
> >>>>> located NOT in user equipment. Also the P.NAMS mid-point
> >>>>> model fails for such a scenario.
> >>>>>
> >>>>>> ITU-T H.248.48.
> >>>>>> But I haven't check the current status of H.248.48.
> >>>>>
> >>>>> [ABS] Work is finalized, see
> >>>>> http://www.itu.int/md/meetingdoc.asp?lang=3Den&parent=3DT09-SG16-1
> >>>>> 11121-TD-PLEN-0419
> >>>>>
> >>>>>>
> >>>>>>>
> >>>>>>> But as the author of this document, I am interested and open
> >>>>>>> to other opinions.:-)
> >>>>>>
> >>>>>> [ABS] Like to add a further aspect: a "functional monitoring
> >>>>>> architecture" may be considered as a network overlay,
> >>>>>> something which adds additional capabilities (here:
> >>>>>> measurement services, reporting services on top of basic RTP
> >>>>>> services).
> >>>>>> Such an overlay concept is nothing new: e.g., the
> >>>>>> MultiService Forum did define a "Performance Measurement &
> >>>>>> Monitoring (PMM)" overlay network, or IETF RMON may be also
> >>>>>> considered as such.
> >>>>>>
> >>>>>>>
> >>>>>>>> Regards,
> >>>>>>>> Albrecht
> >>>>>>>>
> >>>>>>>>
> >>>>>>>>
> >>>>>>>>
> >>>>>>>>> -----Original Message-----
> >>>>>>>>> From: avt-bounces@ietf.org
> >> [mailto:avt-bounces@ietf.org] On
> >>>>>>>>> Behalf Of internet-drafts@ietf.org
> >>>>>>>>> Sent: Dienstag, 29. November 2011 08:56
> >>>>>>>>> To: i-d-announce@ietf.org
> >>>>>>>>> Cc: avt@ietf.org
> >>>>>>>>> Subject: [AVTCORE] I-D Action:
> >>>>> draft-ietf-avtcore-monarch-08.txt
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>> A New Internet-Draft is available from the on-line
> >>>>>>>>> Internet-Drafts directories. This draft is a work
> >>> item of the
> >>>>>>>>> Audio/Video Transport Core Maintenance Working Group
> >>>>> of the IETF.
> >>>>>>>>>
> >>>>>>>>> Title           : Monitoring Architectures for RTP
> >>>>>>>>> Author(s)       : Qin Wu
> >>>>>>>>>                          Geoff Hunt
> >>>>>>>>>                          Philip Arden
> >>>>>>>>> Filename        : draft-ietf-avtcore-monarch-08.txt
> >>>>>>>>> Pages           : 25
> >>>>>>>>> Date            : 2011-11-28
> >>>>>>>>>
> >>>>>>>>>   This memo proposes an architecture for
> >>> extending RTCP with
> >>>>>>>>> a new RTCP
> >>>>>>>>>   XR (RFC3611) block type to report new metrics
> >>>>> regarding media
> >>>>>>>>>   transmission or reception quality, following RTCP
> >>>> guideline
> >>>>>>>>>   established in RFC5968.  This memo suggests that a new
> >>>>>>> block should
> >>>>>>>>>   contain a single metric or a small number of metrics
> >>>>>>> relevant to a
> >>>>>>>>>   single parameter of interest or concern, rather than
> >>>>>>> containing a
> >>>>>>>>>   number of metrics which attempt to provide
> >> full coverage
> >>>>>>>>> of all those
> >>>>>>>>>   parameters of concern to a specific application.
> >>>>>>> Applications may
> >>>>>>>>>   then "mix and match" to create a set of blocks which
> >>>>>>>>> covers their set
> >>>>>>>>>   of concerns.  Where possible, a specific
> >> block should be
> >>>>>>>>> designed to
> >>>>>>>>>   be re-usable across more than one application, for
> >>>>>>> example, for all
> >>>>>>>>>   of voice, streaming audio and video.
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>> A URL for this Internet-Draft is:
> >>>>>>>>>
> >>>>>>>
> >>>>>>
> >>>>>
> >>>>
> >>>
> >>
> http://www.ietf.org/internet-drafts/draft-ietf-avtcore-monarch-08.txt
> >>>>>>>>>
> >>>>>>>>> Internet-Drafts are also available by anonymous FTP at:
> >>>>>>>>> ftp://ftp.ietf.org/internet-drafts/
> >>>>>>>>>
> >>>>>>>>> This Internet-Draft can be retrieved at:
> >>>>>>>>>
> >>>>>>>
> >>>>>
> >>>
> ftp://ftp.ietf.org/internet-drafts/draft-ietf-avtcore-monarch-08.txt
> >>>>>>>>>
> >>>>>>>>> _______________________________________________
> >>>>>>>>> Audio/Video Transport Core Maintenance
> >>>>>>>>> avt@ietf.org
> >>>>>>>>> https://www.ietf.org/mailman/listinfo/avt
> >>>>>>>>>
> >>>>>>>> _______________________________________________
> >>>>>>>> Audio/Video Transport Core Maintenance
> >>>>>>>> avt@ietf.org
> >>>>>>>> https://www.ietf.org/mailman/listinfo/avt
> >>>>>>>
> >>>>>> =3D
> >>>>> _______________________________________________
> >>>>> Audio/Video Transport Core Maintenance
> >>>>> avt@ietf.org
> >>>>> https://www.ietf.org/mailman/listinfo/avt
> >>>>>
> >>>>
> >>>
> >>
> > _______________________________________________
> > Audio/Video Transport Core Maintenance
> > avt@ietf.org
> > https://www.ietf.org/mailman/listinfo/avt
>
>
>
> --
> Colin Perkins
> http://csperkins.org/
>
>
>
>

From csp@csperkins.org  Mon Dec 12 08:57:15 2011
Return-Path: <csp@csperkins.org>
X-Original-To: megaco@ietfa.amsl.com
Delivered-To: megaco@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 35D5D21F8B7E; Mon, 12 Dec 2011 08:57:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.593
X-Spam-Level: 
X-Spam-Status: No, score=-102.593 tagged_above=-999 required=5 tests=[AWL=-0.194, BAYES_00=-2.599, J_CHICKENPOX_14=0.6, J_CHICKENPOX_74=0.6, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EmFtfnF00tWr; Mon, 12 Dec 2011 08:57:13 -0800 (PST)
Received: from lon1-msapost-1.mail.demon.net (lon1-msapost-1.mail.demon.net [195.173.77.180]) by ietfa.amsl.com (Postfix) with ESMTP id CC84021F8B75; Mon, 12 Dec 2011 08:57:12 -0800 (PST)
Received: from mangole.dcs.gla.ac.uk ([130.209.247.112]) by lon1-post-1.mail.demon.net with esmtpsa (AUTH csperkins-dwh) (TLSv1:AES128-SHA:128) (Exim 4.69) id 1Ra9Bf-0004n0-Xj; Mon, 12 Dec 2011 16:57:11 +0000
Mime-Version: 1.0 (Apple Message framework v1251.1)
Content-Type: text/plain; charset=us-ascii
From: Colin Perkins <csp@csperkins.org>
In-Reply-To: <5F7BCCF5541B7444830A2288ABBEBC9621620F5330@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com>
Date: Mon, 12 Dec 2011 16:56:57 +0000
Content-Transfer-Encoding: quoted-printable
Message-Id: <2BEF8708-58B8-4AEB-B3A6-702F46E58C12@csperkins.org>
References: <20111129075613.12419.4377.idtracker@ietfa.amsl.com> <5F7BCCF5541B7444830A2288ABBEBC96216190051A@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com> <EAC481B4D8034C38AC54E1217F8D875D@china.huawei.com> <5F7BCCF5541B7444830A2288ABBEBC96216190077F@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com> <B527BAFA038842A8939A8C2D558074CD@china.huawei.com> <5F7BCCF5541B7444830A2288ABBEBC962161900908@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com> <9FF9B04A84E64AD7ABCCC4F2ACC1E19A@china.huawei.com> <5F7BCCF5541B7444830A2288ABBEBC9621620F4AF5@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com> <D44A4820E0D24DD79F6F5A4B7507D0D6@china.huawei.com> <5F7BCCF5541B7444830A2288ABBEBC9621620F4ED2@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com> <71112008FBA94D35B07FA6B4916075B6@china.huawei.com> <5F7BCCF5541B7444830A2288ABBEBC9621620F5258@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com> <6C618D1EA52146A781429C6B08C4A4FC@china.huawei.com> <5F7BCCF5541B7444830A2288ABBEBC9621620F5330@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com>
To: "Schwarz, Albrecht (Albrecht)" <albrecht.schwarz@alcatel-lucent.com>
X-Mailer: Apple Mail (2.1251.1)
X-Mailman-Approved-At: Tue, 13 Dec 2011 10:49:37 -0800
Cc: "megaco@ietf.org" <megaco@ietf.org>, Qin Wu <bill.wu@huawei.com>, "avt@ietf.org" <avt@ietf.org>
Subject: Re: [Megaco] [AVTCORE] Types of monitoring architectures; RE:  I-D Action: draft-ietf-avtcore-monarch-08.txt
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.1.12
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: Mon, 12 Dec 2011 16:57:15 -0000

Albrecht, Qin,

It doesn't seem controversial that some metrics are only meaningful in =
some scenarios, or when measured at certain points in a system. I don't =
see how adding a statement to the monarch draft to recognise that could =
be problematic. Is there anything else being suggested here?

Colin


On 12 Dec 2011, at 10:33, Schwarz, Albrecht (Albrecht) wrote:
> Hi Qin,
>=20
> I'm very aware about all that.
> It looks like that you are now agreeing that QoE measurements are =
CONDITIONAL ("you got a number of IF statements, there might be even =
more ...").
>=20
> MONARCH is not talking about such conditions, thus some readers may =
got the impression that the metrics related to RTP traffic are =
UNCONDITIONAL (which is not true as you confirmed).
>=20
> If you go back to my very first email: I did just propose to indicate =
the conditional aspect. Don't understand why such kind of valuable info =
would be not in scope of MONARCH. Hm?
>=20
> Regards,
> Albrecht
>=20
> PS
> I did use the notion of a control plane agnostic "RTP-to-PSTN =
gateway". You did indicate control plane specific gateway types like =
SIP-to-PSTN or SIP-to-H.323. Now issue to use such signalling protocol =
specific examples, but it doesn't change the underlying issue.
> The SIP side reporting capability based on RFC 6035 allows to report =
the outlined measurements, but the RFC itself does not specify whether =
the reported information is meaningful (which is OK because this is not =
subject of a reporting interface spec, it is rather subject of a network =
monitoring doc like MONARCH).
> QoE measurements would be conditional in both gateway types (because =
such a gateway is NOT a user device despite the fact of an embedded SIP =
user agent entity).
> Actually I would even question here the condition of "customer knows =
the original content" in many real network scenarios.
>=20
>=20
>=20
>> -----Original Message-----
>> From: Qin Wu [mailto:bill.wu@huawei.com]
>> Sent: Montag, 12. Dezember 2011 05:05
>> To: Schwarz, Albrecht (Albrecht); avt@ietf.org
>> Cc: megaco@ietf.org
>> Subject: Re: [AVTCORE] Types of monitoring architectures; RE:
>> I-D Action: draft-ietf-avtcore-monarch-08.txt
>>=20
>> Hi, Albrecht:
>> My understanding to QoE measurment is:
>> The factors that influence the QoE metric include encoding
>> system, transport network, access network,home network and end =
device.
>> If the customer(e.g., network operator) doesn't know the
>> original content, the QoE metric should be usually measured
>> at the user device.
>> If the customer knows the original content, the QoE metric
>> can be measured either in the network or at the user device.
>> Given the growing popularity of connected devices, these
>> devices may have different capability corresponding to CPU
>> load, processing overhead, storage, batteries.
>> If the cusomer want to measure QoE without considering
>> connected devices with various capability , the QoE metric
>> can be measured at the point between access network and home network.
>>=20
>> Regarding the monitoring scenario you mentioned, I am not
>> familiar with such scenario with RTP-to-PSTN gateway deployed.
>> But I am aware that there are scenarios with SIP to PSTN
>> gateway or SIP to H.323 gateway widely deployed,  RFC6035
>> defines a new SIP event package, vq-rtcpxr that enable the
>> collection and  reporting of metrics that measure quality for
>> RTP sessions. In such cases, RTCP XR VOIP metric with QoE
>> metric included is measured at the user device and mapped
>> into the equivalent SIP vq-rtcpxr parameter since SIP session
>> call is established end to end and RTP media stream is
>> exchanged directly between one endpoint and the other endpoint.
>>=20
>> Regards!
>> -Qin
>> ----- Original Message -----
>> From: "Schwarz, Albrecht (Albrecht)"
>> <albrecht.schwarz@alcatel-lucent.com>
>> To: "Qin Wu" <bill.wu@huawei.com>; <avt@ietf.org>
>> Cc: <megaco@ietf.org>
>> Sent: Saturday, December 10, 2011 12:01 AM
>> Subject: RE: [AVTCORE] Types of monitoring architectures; RE:
>> I-D Action: draft-ietf-avtcore-monarch-08.txt
>>=20
>>=20
>> How do you explain to a network operator the value of QoE
>> measurements by an RTP receiver / RTP monitor component
>> located in an RTP-to-PSTN gateway?
>>=20
>> This would be a monitoring scenario inline with MONARCH, but
>> with valueless QoE results, right?
>>=20
>>=20
>>> -----Original Message-----
>>> From: Qin Wu [mailto:bill.wu@huawei.com]
>>> Sent: Donnerstag, 8. Dezember 2011 03:26
>>> To: Schwarz, Albrecht (Albrecht); avt@ietf.org
>>> Cc: megaco@ietf.org
>>> Subject: Re: [AVTCORE] Types of monitoring architectures; RE:
>>> I-D Action: draft-ietf-avtcore-monarch-08.txt
>>>=20
>>> You reiterate what you propose for physical entities in the
>>> early email.
>>> I am still not convicing with that.
>>>=20
>>> Since we have RTP components like RTP end system, RTP mixer,
>>> RTP media translator, RTP transport translator, RTP monitor
>>> specified in RFC3550 can be built into these component as a
>>> application. also monitor can be disjointed from these RTP
>>> components as a third party monitor. why we need to specify
>>> how to map RTP end system into user equipment, RTP translator
>>> or RTP mixer can be mapped into RTP-PSTN gateway, or IP to IP
>>> border gateway since we have already mapped monitor into
>>> different RTP components.
>>> How many PE types you can enumerate? why they should be scope
>>> of RTP monitoring architecture?
>>>=20
>>> Also as specified in MONARCH draft, we have end sytem
>>> metrics, transport level metric, transport level metric, they
>>> can be measured and collected from the different RTP
>>> comoponents specified in RFC3550, RFC5117. Apparently end
>>> system metric can only be collected from RTP end system.
>>> transport metric is collected from any RTP system in the RTP
>>> monitoring architecture, regarding application level metric,
>>> apparently they should be measured at the application layer
>>> and can not be collected from RTP transport translator, Also
>>> RTP transport translator is still a functional entity rather
>>> than a physical entity. I am not convincing with what you
>>> said about "contradiction", "lead to possible wrong expectations".
>>>=20
>>> Regards!
>>> -Qin
>>> ----- Original Message -----
>>> From: "Schwarz, Albrecht (Albrecht)"
>>> <albrecht.schwarz@alcatel-lucent.com>
>>> To: "Qin Wu" <bill.wu@huawei.com>; <avt@ietf.org>
>>> Cc: <megaco@ietf.org>
>>> Sent: Thursday, December 08, 2011 12:24 AM
>>> Subject: RE: [AVTCORE] Types of monitoring architectures; RE:
>>> I-D Action: draft-ietf-avtcore-monarch-08.txt
>>>=20
>>>=20
>>> Qin,
>>> that's NOT the point.
>>>=20
>>> All RFC 3550 and RFC 5117 RTP components are FUNCTIONAL
>> ENTITIES (FE).
>>> e.g.,
>>> - the RTP Monitor or RTP receiver FE may be located in
>>> different PHYSICAL ENTITIES (PE), e.g.
>>>        a1) a user equipment
>>>        a2) a RTP-to-PSTN gateway
>>>        a3) an IP-to-IP session border gateway (in a
>>> back-to-back RTP endsystem topology)
>>>        a3) ...
>>>=20
>>> - the RTP Monitor may be associated to an RTP transport
>> translator ...
>>>        b1) an IP-to-IP session border gateway
>>>=20
>>> The "RTP monitoring architecture" is IMPACTED by each
>>> functional-to-physical mapping because e.g.
>>> * QoE related metrics are questionable in case of a2
>>> ("despite the fact of a RTP receiver function")
>>> * application level metrics at the location of a RTP
>>> transport translator are a contradiction in itself
>>> * ...
>>>=20
>>> Again, it's not really changing the MONARCH draft because in
>>> the very majority of scenarios it is correct. However, there
>>> are few cases where the MONARCH description would be "too
>>> high level", "not fully correct", "lead to possible wrong
>>> expectations", ...
>>>=20
>>> Regards,
>>> Albrecht
>>>=20
>>>=20
>>>=20
>>>> -----Original Message-----
>>>> From: Qin Wu [mailto:bill.wu@huawei.com]
>>>> Sent: Dienstag, 6. Dezember 2011 07:13
>>>> To: Schwarz, Albrecht (Albrecht); avt@ietf.org
>>>> Cc: megaco@ietf.org
>>>> Subject: Re: [AVTCORE] Types of monitoring architectures; RE:
>>>> I-D Action: draft-ietf-avtcore-monarch-08.txt
>>>>=20
>>>> If you talk about existing RFC5117 RTP topology components,
>>>> this has already been covered by the current version of
>>>> draft-ietf-avtcore-monarch.
>>>> In most cases, an RTP system using RTCP XR is architecturally
>>>> no different from an RTP system which does not use RTCP XR.
>>>>=20
>>>> Regards!
>>>> -Qin
>>>> ----- Original Message -----
>>>> From: "Schwarz, Albrecht (Albrecht)"
>>>> <albrecht.schwarz@alcatel-lucent.com>
>>>> To: "Qin Wu" <bill.wu@huawei.com>; <avt@ietf.org>
>>>> Cc: <megaco@ietf.org>
>>>> Sent: Monday, December 05, 2011 10:48 PM
>>>> Subject: RE: [AVTCORE] Types of monitoring architectures; RE:
>>>> I-D Action: draft-ietf-avtcore-monarch-08.txt
>>>>=20
>>>>=20
>>>> Hello Qin,
>>>>=20
>>>> to 1) Physical monitoring architecture
>>>> Of course consideration of generic physical entities (PE),
>>>> not specific to any network reference architectures defined
>>>> by SDOs (like your refered entities).
>>>> There would be just a few PE types ("given by the limited set
>>>> of RTP topology components (RFC 5117)").
>>>>=20
>>>> to 2) (RFC 3550) Monitor function
>>>> Right, that's a functional entity. The applicability of a
>>>> monitor may be limited, dependent on ... (like in P.NAMS).
>>>>=20
>>>> to 3) your IMS network example
>>>> Don't see the need to refer from MONARCH to a specific
>>>> network architecture like IMS.
>>>> Please also note that IMS is a functional architecture, not a
>>>> physical architecture.
>>>>=20
>>>> Regards,
>>>> Albrecht
>>>>=20
>>>> PS
>>>> There are multiple options for adding the "RTP monitoring
>>>> architecture" to a functional/physical network architecture:
>>>> a) integrated approach: extension of existing functional
>>>> entities or/and addition of RTP monitoring architectural
>>>> components, extension or/and addition of
>>>> signalling/management interfaces for control and
>>>> configuration of RTP monitoring services, and reporting
>>>> interfaces for measurement data ...
>>>> b) overlay approach: separate specification to ...
>>>>=20
>>>>=20
>>>> PSS
>>>> BTW: there's a discussion paper with regards to the location
>>>> of a monitor function in an IMS H.248 gateway entity:
>>>> Measurements and statistics in IMS - Use Cases
>>>> http://www.3gpp.org/ftp/tsg_ct/WG3_interworking_ex-CN3/TSGC3_5
>>>> 8_Kyoto_Japan/Docs/C3-100469.zip
>>>> This is just fyi.
>>>>=20
>>>>=20
>>>>=20
>>>>> -----Original Message-----
>>>>> From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On
>>>>> Behalf Of Qin Wu
>>>>> Sent: Freitag, 2. Dezember 2011 02:55
>>>>> To: Schwarz, Albrecht (Albrecht); avt@ietf.org
>>>>> Cc: megaco@ietf.org
>>>>> Subject: Re: [AVTCORE] Types of monitoring architectures; RE:
>>>>> I-D Action: draft-ietf-avtcore-monarch-08.txt
>>>>>=20
>>>>> Hi, Albrecht:
>>>>> No offence, I am not really convinced with your proposal on
>>>>> physical monitoring architecture.
>>>>> my counterquestion is what does physical monitoring
>>>>> architecture looks like in your mind?
>>>>> How many components do we have in such physical monitroing
>>>>> architecture? what are they?
>>>>> Take IMS network architecture as a example, they may have
>>>>> P-CSCF,S-CSCF, SIP PBX, SBC, why do you believe monitor
>>>>> described in draft-ietf-avtcore-monarch is mapped into
>>>>> P-CSCF, S-CSCF, SBC, Media Gateway, Media Gateway Controller
>>>>> should be in the scope of IETF RTP monitoring
>> archtiecture draft?
>>>>>=20
>>>>> Monitor described in  draft-ietf-avtcore-monarch is well
>>>>> defined in the section 3 of RFC3550 as follows:
>>>>> "
>>>>>=20
>>>>>   Monitor: An application that receives RTCP packets sent by
>>>>>      participants in an RTP session, in particular the
>> reception
>>>>>      reports, and estimates the current quality of service for
>>>>>      distribution monitoring, fault diagnosis and long-term
>>>>> statistics.
>>>>>      The monitor function is likely to be built into the
>>>>> application(s)
>>>>>      participating in the session, but may also be a separate
>>>>>      application that does not otherwise participate and
>>>>> does not send
>>>>>      or receive the RTP data packets (since they are on
>>> a separate
>>>>>      port).  These are called third-party monitors.  It is also
>>>>>      acceptable for a third-party monitor to receive
>> the RTP data
>>>>>      packets but not send RTCP packets or otherwise be
>>>> counted in the
>>>>>      session.
>>>>>=20
>>>>> "
>>>>> Isn't how to implent monitor into IMS netowork archtiecture a
>>>>> implentation specific issue?
>>>>> If this issue are really interesting, isn't it a good idea to
>>>>> produce another new document to talk about this?
>>>>> One good example for this motivation is this draft I like to
>>>>> share with you:
>>>>> http://tools.ietf.org/html/draft-kaplan-dispatch-b2bua-taxonom
>>>>> y-00#section-4.6
>>>>>=20
>>>>> Regards!
>>>>> -Qin
>>>>> ----- Original Message -----
>>>>> From: "Schwarz, Albrecht (Albrecht)"
>>>>> <albrecht.schwarz@alcatel-lucent.com>
>>>>> To: "Qin Wu" <bill.wu@huawei.com>; <avt@ietf.org>
>>>>> Cc: <megaco@ietf.org>
>>>>> Sent: Friday, December 02, 2011 12:20 AM
>>>>> Subject: RE: [AVTCORE] Types of monitoring architectures; RE:
>>>>> I-D Action: draft-ietf-avtcore-monarch-08.txt
>>>>>=20
>>>>>=20
>>>>> My replies below ...
>>>>> -Albrecht
>>>>>=20
>>>>>> -----Original Message-----
>>>>>> From: Qin Wu [mailto:bill.wu@huawei.com]
>>>>>> Sent: Donnerstag, 1. Dezember 2011 02:42
>>>>>> To: Schwarz, Albrecht (Albrecht); avt@ietf.org
>>>>>> Cc: megaco@ietf.org
>>>>>> Subject: Re: [AVTCORE] Types of monitoring architectures; RE:
>>>>>> I-D Action: draft-ietf-avtcore-monarch-08.txt
>>>>>>=20
>>>>>> Hi,
>>>>>> ----- Original Message -----
>>>>>> From: "Schwarz, Albrecht (Albrecht)"
>>>>>> <albrecht.schwarz@alcatel-lucent.com>
>>>>>> To: "Qin Wu" <bill.wu@huawei.com>; <avt@ietf.org>
>>>>>> Cc: <megaco@ietf.org>
>>>>>> Sent: Thursday, December 01, 2011 1:24 AM
>>>>>> Subject: RE: [AVTCORE] Types of monitoring architectures; RE:
>>>>>> I-D Action: draft-ietf-avtcore-monarch-08.txt
>>>>>>=20
>>>>>>=20
>>>>>> My replies below inline,
>>>>>> Albrecht
>>>>>>=20
>>>>>>> -----Original Message-----
>>>>>>> From: Qin Wu [mailto:bill.wu@huawei.com]
>>>>>>> Sent: Mittwoch, 30. November 2011 04:51
>>>>>>> To: Schwarz, Albrecht (Albrecht); avt@ietf.org
>>>>>>> Cc: megaco@ietf.org
>>>>>>> Subject: Re: [AVTCORE] Types of monitoring
>> architectures; RE:
>>>>>>> I-D Action: draft-ietf-avtcore-monarch-08.txt
>>>>>>>=20
>>>>>>> Hi,
>>>>>>> ----- Original Message -----
>>>>>>> From: "Schwarz, Albrecht (Albrecht)"
>>>>>>> <albrecht.schwarz@alcatel-lucent.com>
>>>>>>> To: <avt@ietf.org>
>>>>>>> Cc: <megaco@ietf.org>
>>>>>>> Sent: Tuesday, November 29, 2011 7:32 PM
>>>>>>> Subject: [AVTCORE] Types of monitoring
>> architectures; RE: I-D
>>>>>>> Action: draft-ietf-avtcore-monarch-08.txt
>>>>>>>=20
>>>>>>>=20
>>>>>>>> Dear All,
>>>>>>>>=20
>>>>>>>> there are different types of monitoring architectures,
>>>>>>> particularily from perspective of QoE related performance
>>>>>> parameters.
>>>>>>>> Let's recall QoE (e.g., ITU-T P.10 Amendment 2):
>>>>>>>>=20
>>>>>>>> Quality of Experience (QoE):
>>>>>>>> The overall acceptability of an application or service, as
>>>>>>> perceived subjectively by the end-user.
>>>>>>>> NOTE 1 - Quality of experience includes the complete
>>>>>>> end-to-end system effects (client, terminal, network,
>>>>>>> services infrastructure, etc.).
>>>>>>>> NOTE 2 - Overall acceptability may be influenced by user
>>>>>>> expectations and context.
>>>>>>>>=20
>>>>>>>> Important for MONARCH:
>>>>>>>> 1st ... perceived by end-user
>>>>>>>> 2nd QoE includes the complete end-to-end sytem effects ...
>>>>>>>>=20
>>>>>>>> That said, present RTP monitoring architecture in MONARCH
>>>>>>> according clause 3 is not specific on the type of monitoring
>>>>>>> architecture. For instance, Fig. 1, it is possibly supposed
>>>>>>> that the "RTP Sender" and "RTP Receiver" entities are equal
>>>>>>> to a terminal/user equipment (UE). This would be an
>>>>>>> end-to-end IP network scenario.
>>>>>>>>=20
>>>>>>>> However, the "RTP Sender" and "RTP Receiver" entities may
>>>>>>> be also located at the edge of an IP network, e.g. in a
>>>>>>> gateway for IP-to-non-IP interworking, i.e. an UE located in
>>>>>>> the non-IP network part.
>>>>>>>> Note: such scenarios are considered by MEGACO gateways
>>>>>>> (I've Cc'd megaco list).
>>>>>>>>=20
>>>>>>>> An RTP Sender/Receiver located NOT in the UE
>> would question
>>>>>>> the value of RTP/RTCP QoE related performance measurements
>>>>>>> (because the UE is located outside the RTP domain).
>>>>>>>>=20
>>>>>>>> Conclusions:
>>>>>>>> - the set of meaningful performance metrics may be
>>>>>>> dependent on the location of the RTP Sender/Receiver, e.g.
>>>>>>> whether in a UE, gateway, ...
>>>>>>>> - don't see any impact on transport level metrics
>>>>>>>> - ... but the set of meaningful application level metrics
>>>>>>>>=20
>>>>>>>> Proposal for MONARCH:
>>>>>>>> #1: insert sub-clause title "3.1 End-to-end IP network
>>>>>>> architecture" below clause 3
>>>>>>>>=20
>>>>>>>> #2: add a sub-clause 3.2 at the end of clause 3, sth like
>>>>>>>>=20
>>>>>>>> "3.2 RTP Sender/Receiver entities located in network nodes
>>>>>>>> The location of the RTP Sender/Receiver entity may impact
>>>>>>> the set of meaningful metrics.
>>>>>>>> For instance: application level metrics for QoE related
>>>>>>> performance metrics are questionable (or doesn't really make
>>>>>>> sense at all) when measured in a network node (terminating
>>>>>>> the RTP) instead of the user equipment."
>>>>>>>>=20
>>>>>>>> Something like this would help to avoid confusion.
>>>>>>>> I even believe that a QoE measurement in a network node
>>>>>>> would violate the QoE definition. Would be rather something
>>>>>>> like QoE* ("remote QoE"):-(
>>>>>>>>=20
>>>>>>>> Such information would improve the MONARCH doc in
>>> my opinion.
>>>>>>>> Sorry for that late comment.
>>>>>>>> Any views?
>>>>>>>=20
>>>>>>> [Qin]:
>>>>>>> Albrrecht, if you follow ealry list discussion on
>>>>>>> draft-hunt-avt-monarch-01, you will see the rough consensus
>>>>>>> to position this document was
>>>>>>> this daft should focus on guidelines for defining reporting
>>>>>>> blocks. That is to say the main purpose of MONARCH draft
>>>>> is how to
>>>>>>> provide guidelines for the development of new RTCP XR block
>>>>>>> types in XRBlock working group.
>>>>>>=20
>>>>>> [ABS] ... then the title "monitoring architectures" is
>>> misleading.
>>>>>> Proposal: keep title, revise scope section on focus
>>>>>>=20
>>>>>> [Qin]: No, the title is *RTP* monitoring architecture, we can
>>>>>> not expand scope into IP monitoring architecture.
>>>>>=20
>>>>> [ABS] That's wasn't the intent! Did just focus on the key word.
>>>>>=20
>>>>>>=20
>>>>>>>=20
>>>>>>> Therefore how and where to collect the metric from RTP
>>>>>>> endpoint is not scope of this document, in my opinion. since
>>>>>>> you may have many ways to do this and different vendors have
>>>>>>> their different appoaches. It will be better to leave this
>>>>>>> beyond the scope. But you are right, it will be more
>>>>>>> reasonable to measure QoE related performance metric at the
>>>>>>> RTP receiver.
>>>>>>=20
>>>>>> [ABS] I would disagree. At least your statement should be
>>>>>> conditional, sth like
>>>>>> "QoE related performance metrics may be measured in a RTP
>>>>>> receiver, IF the RTP receiver function is located in user
>>>>>> equipment (e.g. IP terminal), because QoE performance metrics
>>>>>> are tightly coupled to the point of view of a 'user'.
>>>>>> ... IF NOT, then ..."
>>>>>>=20
>>>>>> [Qin]: I am not sure user equipment or IP terminal is the
>>>>>> right term from RTP perspective.
>>>>>>=20
>>>>>> Also if you read P.NAMS, P.NAMS model for calculating QoE
>>>>>> related metric can be placed either at the network or at
>>>> the client.
>>>>>> So I disagree with what you said.
>>>>>=20
>>>>> [ABS] Not convinced at all.
>>>>> Guess you are referring to the "mid-point" models, right?
>>>>> The usage of such that models depends on "prior knowledge
>>>>> ..." information.
>>>>> Thus, the applicability is conditional. You may not make such
>>>>> a general statement.
>>>>>=20
>>>>>=20
>>>>>>=20
>>>>>> Also as I said, how and where to collect the metric from RTP
>>>>>> endpoint is not scope of this document. It depends on the
>>>>>> model you are choosing, e.g., four operation modes specified
>>>>>> in P.NAMS.
>>>>>> Apparently this should not be specified again in RTP
>>>>>> monitoring architecture document.
>>>>>>=20
>>>>>>>=20
>>>>>>> Another point is it is not clear to me how RTP
>> monitoring has
>>>>>>> to do with architectureend to end IP network architecture .
>>>>>>> this draft mostly focus on discussing RTP level stuff.
>>>>>>> Therefore I am quite doubt that we should describe anything
>>>>>>> in this document like how
>>>>>>> RTP entties is mapped into network entities/nodes at
>>>> the IP layer.
>>>>>>=20
>>>>>> [ABS] I don't got any problems to talk about architectural
>>>>>> framework for monitoring in this document. Such information
>>>>>> is required and this is the only IETF AVT doc about it.
>>>>>> The solution to this issue is rather simple to me:
>>>>>> - split the MONARCH "monitoring architecture" in
>>>>>> 1) a functional monitoring architecture (let's call it
>>> 'FMA') and
>>>>>> 2) a physical monitoring architecture (... 'PMA').
>>>>>>=20
>>>>>> - the present MONARCH doc would describe the FMA at the level
>>>>>> of RTP entities (i.e., Fig. 1 entities, incl. all the RTP
>>>>>> topology components according RFC 5117)
>>>>>>=20
>>>>>> - there are many options of functional-to-physical mappings,
>>>>>> i.e. how a FMA would be mapped on a PMA
>>>>>> - the mapping is typically dependent on considered network
>>>>>> architecture (like SIP, H.323, MGCP, IMS, wireless, etc
>>> networks)
>>>>>>=20
>>>>>> - the present MONARCH doc would describe the FMA-to-PMA
>>>>>> mapping IF all RTP receiver/sender entities would be located
>>>>>> in physical IP terminals (UEs)
>>>>>> - etc
>>>>>>=20
>>>>>> [Qin]: I can understand your point, but you can not do that.
>>>>>> Since this document is only focus on *RTP* monitoring
>>>>>> architecture, that is what it said in AVTCore milestone:
>>>>>> "
>>>>>>=20
>>>>>> Goals and Milestones:
>>>>>>=20
>>>>>>  Feb 2011 - Submit Monitoring Architecture for RTP for
>>>>> Informational
>>>>>>=20
>>>>>> "
>>>>>=20
>>>>> [ABS] If you go back to my first email on this subject, and
>>>>> if you look at my proposal: that's not a lot, nothing which
>>>>> violates the charter, goals and milestones.
>>>>>=20
>>>>>=20
>>>>>> Also if you really don't see how to map FMA to PMA, you may
>>>>>> look at the P.NAMS models specifed in ITU-T P.NAMS.
>>>>>> As for how to use RTP monitoring architecture or RTP XR
>>>>>> Report in the IMS network architecture, you may look at:
>>>>>> http://tools.ietf.org/html/rfc6035
>>>>>=20
>>>>> [ABS] That's the SIP reporting interface, i.e., applicable
>>>>> primarily for physical IP user equipment with embedded RTP
>>>>> sender/receiver function and SIP UA function.
>>>>> However, the applicability of RFC 6035 is limited for a
>>>>> SIP-to-PSTN gateway (because the RTP sender/receiver would be
>>>>> located NOT in user equipment. Also the P.NAMS mid-point
>>>>> model fails for such a scenario.
>>>>>=20
>>>>>> ITU-T H.248.48.
>>>>>> But I haven't check the current status of H.248.48.
>>>>>=20
>>>>> [ABS] Work is finalized, see
>>>>> http://www.itu.int/md/meetingdoc.asp?lang=3Den&parent=3DT09-SG16-1
>>>>> 11121-TD-PLEN-0419
>>>>>=20
>>>>>>=20
>>>>>>>=20
>>>>>>> But as the author of this document, I am interested and open
>>>>>>> to other opinions.:-)
>>>>>>=20
>>>>>> [ABS] Like to add a further aspect: a "functional monitoring
>>>>>> architecture" may be considered as a network overlay,
>>>>>> something which adds additional capabilities (here:
>>>>>> measurement services, reporting services on top of basic RTP
>>>>>> services).
>>>>>> Such an overlay concept is nothing new: e.g., the
>>>>>> MultiService Forum did define a "Performance Measurement &
>>>>>> Monitoring (PMM)" overlay network, or IETF RMON may be also
>>>>>> considered as such.
>>>>>>=20
>>>>>>>=20
>>>>>>>> Regards,
>>>>>>>> Albrecht
>>>>>>>>=20
>>>>>>>>=20
>>>>>>>>=20
>>>>>>>>=20
>>>>>>>>> -----Original Message-----
>>>>>>>>> From: avt-bounces@ietf.org
>> [mailto:avt-bounces@ietf.org] On
>>>>>>>>> Behalf Of internet-drafts@ietf.org
>>>>>>>>> Sent: Dienstag, 29. November 2011 08:56
>>>>>>>>> To: i-d-announce@ietf.org
>>>>>>>>> Cc: avt@ietf.org
>>>>>>>>> Subject: [AVTCORE] I-D Action:
>>>>> draft-ietf-avtcore-monarch-08.txt
>>>>>>>>>=20
>>>>>>>>>=20
>>>>>>>>> A New Internet-Draft is available from the on-line
>>>>>>>>> Internet-Drafts directories. This draft is a work
>>> item of the
>>>>>>>>> Audio/Video Transport Core Maintenance Working Group
>>>>> of the IETF.
>>>>>>>>>=20
>>>>>>>>> Title           : Monitoring Architectures for RTP
>>>>>>>>> Author(s)       : Qin Wu
>>>>>>>>>                          Geoff Hunt
>>>>>>>>>                          Philip Arden
>>>>>>>>> Filename        : draft-ietf-avtcore-monarch-08.txt
>>>>>>>>> Pages           : 25
>>>>>>>>> Date            : 2011-11-28
>>>>>>>>>=20
>>>>>>>>>   This memo proposes an architecture for
>>> extending RTCP with
>>>>>>>>> a new RTCP
>>>>>>>>>   XR (RFC3611) block type to report new metrics
>>>>> regarding media
>>>>>>>>>   transmission or reception quality, following RTCP
>>>> guideline
>>>>>>>>>   established in RFC5968.  This memo suggests that a new
>>>>>>> block should
>>>>>>>>>   contain a single metric or a small number of metrics
>>>>>>> relevant to a
>>>>>>>>>   single parameter of interest or concern, rather than
>>>>>>> containing a
>>>>>>>>>   number of metrics which attempt to provide
>> full coverage
>>>>>>>>> of all those
>>>>>>>>>   parameters of concern to a specific application.
>>>>>>> Applications may
>>>>>>>>>   then "mix and match" to create a set of blocks which
>>>>>>>>> covers their set
>>>>>>>>>   of concerns.  Where possible, a specific
>> block should be
>>>>>>>>> designed to
>>>>>>>>>   be re-usable across more than one application, for
>>>>>>> example, for all
>>>>>>>>>   of voice, streaming audio and video.
>>>>>>>>>=20
>>>>>>>>>=20
>>>>>>>>> A URL for this Internet-Draft is:
>>>>>>>>>=20
>>>>>>>=20
>>>>>>=20
>>>>>=20
>>>>=20
>>>=20
>> http://www.ietf.org/internet-drafts/draft-ietf-avtcore-monarch-08.txt
>>>>>>>>>=20
>>>>>>>>> Internet-Drafts are also available by anonymous FTP at:
>>>>>>>>> ftp://ftp.ietf.org/internet-drafts/
>>>>>>>>>=20
>>>>>>>>> This Internet-Draft can be retrieved at:
>>>>>>>>>=20
>>>>>>>=20
>>>>>=20
>>> ftp://ftp.ietf.org/internet-drafts/draft-ietf-avtcore-monarch-08.txt
>>>>>>>>>=20
>>>>>>>>> _______________________________________________
>>>>>>>>> Audio/Video Transport Core Maintenance
>>>>>>>>> avt@ietf.org
>>>>>>>>> https://www.ietf.org/mailman/listinfo/avt
>>>>>>>>>=20
>>>>>>>> _______________________________________________
>>>>>>>> Audio/Video Transport Core Maintenance
>>>>>>>> avt@ietf.org
>>>>>>>> https://www.ietf.org/mailman/listinfo/avt
>>>>>>>=20
>>>>>> =3D
>>>>> _______________________________________________
>>>>> Audio/Video Transport Core Maintenance
>>>>> avt@ietf.org
>>>>> https://www.ietf.org/mailman/listinfo/avt
>>>>>=20
>>>>=20
>>>=20
>>=20
> _______________________________________________
> Audio/Video Transport Core Maintenance
> avt@ietf.org
> https://www.ietf.org/mailman/listinfo/avt



--=20
Colin Perkins
http://csperkins.org/




From bill.wu@huawei.com  Wed Dec 14 00:00:42 2011
Return-Path: <bill.wu@huawei.com>
X-Original-To: megaco@ietfa.amsl.com
Delivered-To: megaco@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4185D21F84B6; Wed, 14 Dec 2011 00:00:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.625
X-Spam-Level: 
X-Spam-Status: No, score=-5.625 tagged_above=-999 required=5 tests=[AWL=-0.226, BAYES_00=-2.599, J_CHICKENPOX_14=0.6, J_CHICKENPOX_74=0.6, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hSnBNaoK4IVQ; Wed, 14 Dec 2011 00:00:39 -0800 (PST)
Received: from szxga01-in.huawei.com (szxga01-in.huawei.com [119.145.14.64]) by ietfa.amsl.com (Postfix) with ESMTP id EAD6321F8511; Wed, 14 Dec 2011 00:00:38 -0800 (PST)
Received: from huawei.com (szxga05-in [172.24.2.49]) by szxga05-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LW600L4ZORPYA@szxga05-in.huawei.com>; Wed, 14 Dec 2011 15:57:26 +0800 (CST)
Received: from szxrg01-dlp.huawei.com ([172.24.2.119]) by szxga05-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LW600KDUOQIOJ@szxga05-in.huawei.com>; Wed, 14 Dec 2011 15:57:25 +0800 (CST)
Received: from szxeml202-edg.china.huawei.com ([172.24.2.119]) by szxrg01-dlp.huawei.com (MOS 4.1.9-GA)	with ESMTP id AFV01231; Wed, 14 Dec 2011 15:57:24 +0800
Received: from SZXEML418-HUB.china.huawei.com (10.82.67.157) by szxeml202-edg.china.huawei.com (172.24.2.42) with Microsoft SMTP Server (TLS) id 14.1.323.3; Wed, 14 Dec 2011 15:57:17 +0800
Received: from w53375q (10.138.41.130) by szxeml418-hub.china.huawei.com (10.82.67.157) with Microsoft SMTP Server (TLS) id 14.1.323.3; Wed, 14 Dec 2011 15:57:21 +0800
Date: Wed, 14 Dec 2011 15:57:20 +0800
From: Qin Wu <bill.wu@huawei.com>
X-Originating-IP: [10.138.41.130]
To: Colin Perkins <csp@csperkins.org>
Message-id: <D1B876207D0042219876F70FD85D3C1B@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.6109
X-Mailer: Microsoft Outlook Express 6.00.2900.5931
Content-type: text/plain; charset=ISO-8859-1
Content-transfer-encoding: 7BIT
X-Priority: 3
X-MSMail-priority: Normal
X-CFilter-Loop: Reflected
References: <1815848C-FE4C-48A0-8889-565198BEEC74@csperkins.org>
Cc: megaco@ietf.org, avt@ietf.org
Subject: Re: [Megaco] [AVTCORE] Types of monitoring architectures; RE:  I-D Action: draft-ietf-avtcore-monarch-08.txt
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.1.12
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, 14 Dec 2011 08:00:42 -0000

Okay, thanks.
----- Original Message ----- 
From: "Colin Perkins" <csp@csperkins.org>
To: "Qin Wu" <bill.wu@huawei.com>
Cc: <megaco@ietf.org>; <avt@ietf.org>; "Schwarz, Albrecht (Albrecht)" <albrecht.schwarz@alcatel-lucent.com>
Sent: Wednesday, December 14, 2011 6:54 AM
Subject: Re: [AVTCORE] Types of monitoring architectures;RE: I-D Action: draft-ietf-avtcore-monarch-08.txt


> Qin,
> 
> Both this, and Albrecht's suggested additions, look reasonable to me.
> 
> Colin
> 
> 
> 
> On 13 Dec 2011, at 02:15, Qin Wu wrote:
>> Hi, Colin:
>> Thank for your suggestion. Besides Albrecht's proposed text, my additional proposal is to fix application level metric defintion in section 2
>> OLD text:
>> "
>>   Application level metrics
>> 
>>      Metrics relating to QoE related parameters.  These metrics are
>>      measured at the application level and focus on quality of content
>>      rather than network parameters. 
>> "
>> New text
>> "
>>   Application level metrics
>> 
>>      Metrics relating to application specific parameters or QoE related parameters. 
>>     Application specific parameters  are measured at the application level and focus
>>     on quality of content rather than network performance.  QoE related parameters
>>     reflect the end-to-end performance at the services level and is ususally measured
>>     at the user endpoint.
>> "
>> 
>> Regards!
>> -Qin
>> ----- Original Message ----- 
>> From: "Colin Perkins" <csp@csperkins.org>
>> To: "Schwarz, Albrecht (Albrecht)" <albrecht.schwarz@alcatel-lucent.com>
>> Cc: "Qin Wu" <bill.wu@huawei.com>; <avt@ietf.org>; <megaco@ietf.org>
>> Sent: Tuesday, December 13, 2011 12:56 AM
>> Subject: Re: [AVTCORE] Types of monitoring architectures; RE: I-D Action: draft-ietf-avtcore-monarch-08.txt
>> 
>> 
>> Albrecht, Qin,
>> 
>> It doesn't seem controversial that some metrics are only meaningful in some scenarios, or when measured at certain points in a system. I don't see how adding a statement to the monarch draft to recognise that could be problematic. Is there anything else being suggested here?
>> 
>> Colin
>> 
>> 
>> On 12 Dec 2011, at 10:33, Schwarz, Albrecht (Albrecht) wrote:
>>> Hi Qin,
>>> 
>>> I'm very aware about all that.
>>> It looks like that you are now agreeing that QoE measurements are CONDITIONAL ("you got a number of IF statements, there might be even more ...").
>>> 
>>> MONARCH is not talking about such conditions, thus some readers may got the impression that the metrics related to RTP traffic are UNCONDITIONAL (which is not true as you confirmed).
>>> 
>>> If you go back to my very first email: I did just propose to indicate the conditional aspect. Don't understand why such kind of valuable info would be not in scope of MONARCH. Hm?
>>> 
>>> Regards,
>>> Albrecht
>>> 
>>> PS
>>> I did use the notion of a control plane agnostic "RTP-to-PSTN gateway". You did indicate control plane specific gateway types like SIP-to-PSTN or SIP-to-H.323. Now issue to use such signalling protocol specific examples, but it doesn't change the underlying issue.
>>> The SIP side reporting capability based on RFC 6035 allows to report the outlined measurements, but the RFC itself does not specify whether the reported information is meaningful (which is OK because this is not subject of a reporting interface spec, it is rather subject of a network monitoring doc like MONARCH).
>>> QoE measurements would be conditional in both gateway types (because such a gateway is NOT a user device despite the fact of an embedded SIP user agent entity).
>>> Actually I would even question here the condition of "customer knows the original content" in many real network scenarios.
>>> 
>>> 
>>> 
>>>> -----Original Message-----
>>>> From: Qin Wu [mailto:bill.wu@huawei.com]
>>>> Sent: Montag, 12. Dezember 2011 05:05
>>>> To: Schwarz, Albrecht (Albrecht); avt@ietf.org
>>>> Cc: megaco@ietf.org
>>>> Subject: Re: [AVTCORE] Types of monitoring architectures; RE:
>>>> I-D Action: draft-ietf-avtcore-monarch-08.txt
>>>> 
>>>> Hi, Albrecht:
>>>> My understanding to QoE measurment is:
>>>> The factors that influence the QoE metric include encoding
>>>> system, transport network, access network,home network and end device.
>>>> If the customer(e.g., network operator) doesn't know the
>>>> original content, the QoE metric should be usually measured
>>>> at the user device.
>>>> If the customer knows the original content, the QoE metric
>>>> can be measured either in the network or at the user device.
>>>> Given the growing popularity of connected devices, these
>>>> devices may have different capability corresponding to CPU
>>>> load, processing overhead, storage, batteries.
>>>> If the cusomer want to measure QoE without considering
>>>> connected devices with various capability , the QoE metric
>>>> can be measured at the point between access network and home network.
>>>> 
>>>> Regarding the monitoring scenario you mentioned, I am not
>>>> familiar with such scenario with RTP-to-PSTN gateway deployed.
>>>> But I am aware that there are scenarios with SIP to PSTN
>>>> gateway or SIP to H.323 gateway widely deployed,  RFC6035
>>>> defines a new SIP event package, vq-rtcpxr that enable the
>>>> collection and  reporting of metrics that measure quality for
>>>> RTP sessions. In such cases, RTCP XR VOIP metric with QoE
>>>> metric included is measured at the user device and mapped
>>>> into the equivalent SIP vq-rtcpxr parameter since SIP session
>>>> call is established end to end and RTP media stream is
>>>> exchanged directly between one endpoint and the other endpoint.
>>>> 
>>>> Regards!
>>>> -Qin
>>>> ----- Original Message -----
>>>> From: "Schwarz, Albrecht (Albrecht)"
>>>> <albrecht.schwarz@alcatel-lucent.com>
>>>> To: "Qin Wu" <bill.wu@huawei.com>; <avt@ietf.org>
>>>> Cc: <megaco@ietf.org>
>>>> Sent: Saturday, December 10, 2011 12:01 AM
>>>> Subject: RE: [AVTCORE] Types of monitoring architectures; RE:
>>>> I-D Action: draft-ietf-avtcore-monarch-08.txt
>>>> 
>>>> 
>>>> How do you explain to a network operator the value of QoE
>>>> measurements by an RTP receiver / RTP monitor component
>>>> located in an RTP-to-PSTN gateway?
>>>> 
>>>> This would be a monitoring scenario inline with MONARCH, but
>>>> with valueless QoE results, right?
>>>> 
>>>> 
>>>>> -----Original Message-----
>>>>> From: Qin Wu [mailto:bill.wu@huawei.com]
>>>>> Sent: Donnerstag, 8. Dezember 2011 03:26
>>>>> To: Schwarz, Albrecht (Albrecht); avt@ietf.org
>>>>> Cc: megaco@ietf.org
>>>>> Subject: Re: [AVTCORE] Types of monitoring architectures; RE:
>>>>> I-D Action: draft-ietf-avtcore-monarch-08.txt
>>>>> 
>>>>> You reiterate what you propose for physical entities in the
>>>>> early email.
>>>>> I am still not convicing with that.
>>>>> 
>>>>> Since we have RTP components like RTP end system, RTP mixer,
>>>>> RTP media translator, RTP transport translator, RTP monitor
>>>>> specified in RFC3550 can be built into these component as a
>>>>> application. also monitor can be disjointed from these RTP
>>>>> components as a third party monitor. why we need to specify
>>>>> how to map RTP end system into user equipment, RTP translator
>>>>> or RTP mixer can be mapped into RTP-PSTN gateway, or IP to IP
>>>>> border gateway since we have already mapped monitor into
>>>>> different RTP components.
>>>>> How many PE types you can enumerate? why they should be scope
>>>>> of RTP monitoring architecture?
>>>>> 
>>>>> Also as specified in MONARCH draft, we have end sytem
>>>>> metrics, transport level metric, transport level metric, they
>>>>> can be measured and collected from the different RTP
>>>>> comoponents specified in RFC3550, RFC5117. Apparently end
>>>>> system metric can only be collected from RTP end system.
>>>>> transport metric is collected from any RTP system in the RTP
>>>>> monitoring architecture, regarding application level metric,
>>>>> apparently they should be measured at the application layer
>>>>> and can not be collected from RTP transport translator, Also
>>>>> RTP transport translator is still a functional entity rather
>>>>> than a physical entity. I am not convincing with what you
>>>>> said about "contradiction", "lead to possible wrong expectations".
>>>>> 
>>>>> Regards!
>>>>> -Qin
>>>>> ----- Original Message -----
>>>>> From: "Schwarz, Albrecht (Albrecht)"
>>>>> <albrecht.schwarz@alcatel-lucent.com>
>>>>> To: "Qin Wu" <bill.wu@huawei.com>; <avt@ietf.org>
>>>>> Cc: <megaco@ietf.org>
>>>>> Sent: Thursday, December 08, 2011 12:24 AM
>>>>> Subject: RE: [AVTCORE] Types of monitoring architectures; RE:
>>>>> I-D Action: draft-ietf-avtcore-monarch-08.txt
>>>>> 
>>>>> 
>>>>> Qin,
>>>>> that's NOT the point.
>>>>> 
>>>>> All RFC 3550 and RFC 5117 RTP components are FUNCTIONAL
>>>> ENTITIES (FE).
>>>>> e.g.,
>>>>> - the RTP Monitor or RTP receiver FE may be located in
>>>>> different PHYSICAL ENTITIES (PE), e.g.
>>>>>       a1) a user equipment
>>>>>       a2) a RTP-to-PSTN gateway
>>>>>       a3) an IP-to-IP session border gateway (in a
>>>>> back-to-back RTP endsystem topology)
>>>>>       a3) ...
>>>>> 
>>>>> - the RTP Monitor may be associated to an RTP transport
>>>> translator ...
>>>>>       b1) an IP-to-IP session border gateway
>>>>> 
>>>>> The "RTP monitoring architecture" is IMPACTED by each
>>>>> functional-to-physical mapping because e.g.
>>>>> * QoE related metrics are questionable in case of a2
>>>>> ("despite the fact of a RTP receiver function")
>>>>> * application level metrics at the location of a RTP
>>>>> transport translator are a contradiction in itself
>>>>> * ...
>>>>> 
>>>>> Again, it's not really changing the MONARCH draft because in
>>>>> the very majority of scenarios it is correct. However, there
>>>>> are few cases where the MONARCH description would be "too
>>>>> high level", "not fully correct", "lead to possible wrong
>>>>> expectations", ...
>>>>> 
>>>>> Regards,
>>>>> Albrecht
>>>>> 
>>>>> 
>>>>> 
>>>>>> -----Original Message-----
>>>>>> From: Qin Wu [mailto:bill.wu@huawei.com]
>>>>>> Sent: Dienstag, 6. Dezember 2011 07:13
>>>>>> To: Schwarz, Albrecht (Albrecht); avt@ietf.org
>>>>>> Cc: megaco@ietf.org
>>>>>> Subject: Re: [AVTCORE] Types of monitoring architectures; RE:
>>>>>> I-D Action: draft-ietf-avtcore-monarch-08.txt
>>>>>> 
>>>>>> If you talk about existing RFC5117 RTP topology components,
>>>>>> this has already been covered by the current version of
>>>>>> draft-ietf-avtcore-monarch.
>>>>>> In most cases, an RTP system using RTCP XR is architecturally
>>>>>> no different from an RTP system which does not use RTCP XR.
>>>>>> 
>>>>>> Regards!
>>>>>> -Qin
>>>>>> ----- Original Message -----
>>>>>> From: "Schwarz, Albrecht (Albrecht)"
>>>>>> <albrecht.schwarz@alcatel-lucent.com>
>>>>>> To: "Qin Wu" <bill.wu@huawei.com>; <avt@ietf.org>
>>>>>> Cc: <megaco@ietf.org>
>>>>>> Sent: Monday, December 05, 2011 10:48 PM
>>>>>> Subject: RE: [AVTCORE] Types of monitoring architectures; RE:
>>>>>> I-D Action: draft-ietf-avtcore-monarch-08.txt
>>>>>> 
>>>>>> 
>>>>>> Hello Qin,
>>>>>> 
>>>>>> to 1) Physical monitoring architecture
>>>>>> Of course consideration of generic physical entities (PE),
>>>>>> not specific to any network reference architectures defined
>>>>>> by SDOs (like your refered entities).
>>>>>> There would be just a few PE types ("given by the limited set
>>>>>> of RTP topology components (RFC 5117)").
>>>>>> 
>>>>>> to 2) (RFC 3550) Monitor function
>>>>>> Right, that's a functional entity. The applicability of a
>>>>>> monitor may be limited, dependent on ... (like in P.NAMS).
>>>>>> 
>>>>>> to 3) your IMS network example
>>>>>> Don't see the need to refer from MONARCH to a specific
>>>>>> network architecture like IMS.
>>>>>> Please also note that IMS is a functional architecture, not a
>>>>>> physical architecture.
>>>>>> 
>>>>>> Regards,
>>>>>> Albrecht
>>>>>> 
>>>>>> PS
>>>>>> There are multiple options for adding the "RTP monitoring
>>>>>> architecture" to a functional/physical network architecture:
>>>>>> a) integrated approach: extension of existing functional
>>>>>> entities or/and addition of RTP monitoring architectural
>>>>>> components, extension or/and addition of
>>>>>> signalling/management interfaces for control and
>>>>>> configuration of RTP monitoring services, and reporting
>>>>>> interfaces for measurement data ...
>>>>>> b) overlay approach: separate specification to ...
>>>>>> 
>>>>>> 
>>>>>> PSS
>>>>>> BTW: there's a discussion paper with regards to the location
>>>>>> of a monitor function in an IMS H.248 gateway entity:
>>>>>> Measurements and statistics in IMS - Use Cases
>>>>>> http://www.3gpp.org/ftp/tsg_ct/WG3_interworking_ex-CN3/TSGC3_5
>>>>>> 8_Kyoto_Japan/Docs/C3-100469.zip
>>>>>> This is just fyi.
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>>> -----Original Message-----
>>>>>>> From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On
>>>>>>> Behalf Of Qin Wu
>>>>>>> Sent: Freitag, 2. Dezember 2011 02:55
>>>>>>> To: Schwarz, Albrecht (Albrecht); avt@ietf.org
>>>>>>> Cc: megaco@ietf.org
>>>>>>> Subject: Re: [AVTCORE] Types of monitoring architectures; RE:
>>>>>>> I-D Action: draft-ietf-avtcore-monarch-08.txt
>>>>>>> 
>>>>>>> Hi, Albrecht:
>>>>>>> No offence, I am not really convinced with your proposal on
>>>>>>> physical monitoring architecture.
>>>>>>> my counterquestion is what does physical monitoring
>>>>>>> architecture looks like in your mind?
>>>>>>> How many components do we have in such physical monitroing
>>>>>>> architecture? what are they?
>>>>>>> Take IMS network architecture as a example, they may have
>>>>>>> P-CSCF,S-CSCF, SIP PBX, SBC, why do you believe monitor
>>>>>>> described in draft-ietf-avtcore-monarch is mapped into
>>>>>>> P-CSCF, S-CSCF, SBC, Media Gateway, Media Gateway Controller
>>>>>>> should be in the scope of IETF RTP monitoring
>>>> archtiecture draft?
>>>>>>> 
>>>>>>> Monitor described in  draft-ietf-avtcore-monarch is well
>>>>>>> defined in the section 3 of RFC3550 as follows:
>>>>>>> "
>>>>>>> 
>>>>>>>  Monitor: An application that receives RTCP packets sent by
>>>>>>>     participants in an RTP session, in particular the
>>>> reception
>>>>>>>     reports, and estimates the current quality of service for
>>>>>>>     distribution monitoring, fault diagnosis and long-term
>>>>>>> statistics.
>>>>>>>     The monitor function is likely to be built into the
>>>>>>> application(s)
>>>>>>>     participating in the session, but may also be a separate
>>>>>>>     application that does not otherwise participate and
>>>>>>> does not send
>>>>>>>     or receive the RTP data packets (since they are on
>>>>> a separate
>>>>>>>     port).  These are called third-party monitors.  It is also
>>>>>>>     acceptable for a third-party monitor to receive
>>>> the RTP data
>>>>>>>     packets but not send RTCP packets or otherwise be
>>>>>> counted in the
>>>>>>>     session.
>>>>>>> 
>>>>>>> "
>>>>>>> Isn't how to implent monitor into IMS netowork archtiecture a
>>>>>>> implentation specific issue?
>>>>>>> If this issue are really interesting, isn't it a good idea to
>>>>>>> produce another new document to talk about this?
>>>>>>> One good example for this motivation is this draft I like to
>>>>>>> share with you:
>>>>>>> http://tools.ietf.org/html/draft-kaplan-dispatch-b2bua-taxonom
>>>>>>> y-00#section-4.6
>>>>>>> 
>>>>>>> Regards!
>>>>>>> -Qin
>>>>>>> ----- Original Message -----
>>>>>>> From: "Schwarz, Albrecht (Albrecht)"
>>>>>>> <albrecht.schwarz@alcatel-lucent.com>
>>>>>>> To: "Qin Wu" <bill.wu@huawei.com>; <avt@ietf.org>
>>>>>>> Cc: <megaco@ietf.org>
>>>>>>> Sent: Friday, December 02, 2011 12:20 AM
>>>>>>> Subject: RE: [AVTCORE] Types of monitoring architectures; RE:
>>>>>>> I-D Action: draft-ietf-avtcore-monarch-08.txt
>>>>>>> 
>>>>>>> 
>>>>>>> My replies below ...
>>>>>>> -Albrecht
>>>>>>> 
>>>>>>>> -----Original Message-----
>>>>>>>> From: Qin Wu [mailto:bill.wu@huawei.com]
>>>>>>>> Sent: Donnerstag, 1. Dezember 2011 02:42
>>>>>>>> To: Schwarz, Albrecht (Albrecht); avt@ietf.org
>>>>>>>> Cc: megaco@ietf.org
>>>>>>>> Subject: Re: [AVTCORE] Types of monitoring architectures; RE:
>>>>>>>> I-D Action: draft-ietf-avtcore-monarch-08.txt
>>>>>>>> 
>>>>>>>> Hi,
>>>>>>>> ----- Original Message -----
>>>>>>>> From: "Schwarz, Albrecht (Albrecht)"
>>>>>>>> <albrecht.schwarz@alcatel-lucent.com>
>>>>>>>> To: "Qin Wu" <bill.wu@huawei.com>; <avt@ietf.org>
>>>>>>>> Cc: <megaco@ietf.org>
>>>>>>>> Sent: Thursday, December 01, 2011 1:24 AM
>>>>>>>> Subject: RE: [AVTCORE] Types of monitoring architectures; RE:
>>>>>>>> I-D Action: draft-ietf-avtcore-monarch-08.txt
>>>>>>>> 
>>>>>>>> 
>>>>>>>> My replies below inline,
>>>>>>>> Albrecht
>>>>>>>> 
>>>>>>>>> -----Original Message-----
>>>>>>>>> From: Qin Wu [mailto:bill.wu@huawei.com]
>>>>>>>>> Sent: Mittwoch, 30. November 2011 04:51
>>>>>>>>> To: Schwarz, Albrecht (Albrecht); avt@ietf.org
>>>>>>>>> Cc: megaco@ietf.org
>>>>>>>>> Subject: Re: [AVTCORE] Types of monitoring
>>>> architectures; RE:
>>>>>>>>> I-D Action: draft-ietf-avtcore-monarch-08.txt
>>>>>>>>> 
>>>>>>>>> Hi,
>>>>>>>>> ----- Original Message -----
>>>>>>>>> From: "Schwarz, Albrecht (Albrecht)"
>>>>>>>>> <albrecht.schwarz@alcatel-lucent.com>
>>>>>>>>> To: <avt@ietf.org>
>>>>>>>>> Cc: <megaco@ietf.org>
>>>>>>>>> Sent: Tuesday, November 29, 2011 7:32 PM
>>>>>>>>> Subject: [AVTCORE] Types of monitoring
>>>> architectures; RE: I-D
>>>>>>>>> Action: draft-ietf-avtcore-monarch-08.txt
>>>>>>>>> 
>>>>>>>>> 
>>>>>>>>>> Dear All,
>>>>>>>>>> 
>>>>>>>>>> there are different types of monitoring architectures,
>>>>>>>>> particularily from perspective of QoE related performance
>>>>>>>> parameters.
>>>>>>>>>> Let's recall QoE (e.g., ITU-T P.10 Amendment 2):
>>>>>>>>>> 
>>>>>>>>>> Quality of Experience (QoE):
>>>>>>>>>> The overall acceptability of an application or service, as
>>>>>>>>> perceived subjectively by the end-user.
>>>>>>>>>> NOTE 1 - Quality of experience includes the complete
>>>>>>>>> end-to-end system effects (client, terminal, network,
>>>>>>>>> services infrastructure, etc.).
>>>>>>>>>> NOTE 2 - Overall acceptability may be influenced by user
>>>>>>>>> expectations and context.
>>>>>>>>>> 
>>>>>>>>>> Important for MONARCH:
>>>>>>>>>> 1st ... perceived by end-user
>>>>>>>>>> 2nd QoE includes the complete end-to-end sytem effects ...
>>>>>>>>>> 
>>>>>>>>>> That said, present RTP monitoring architecture in MONARCH
>>>>>>>>> according clause 3 is not specific on the type of monitoring
>>>>>>>>> architecture. For instance, Fig. 1, it is possibly supposed
>>>>>>>>> that the "RTP Sender" and "RTP Receiver" entities are equal
>>>>>>>>> to a terminal/user equipment (UE). This would be an
>>>>>>>>> end-to-end IP network scenario.
>>>>>>>>>> 
>>>>>>>>>> However, the "RTP Sender" and "RTP Receiver" entities may
>>>>>>>>> be also located at the edge of an IP network, e.g. in a
>>>>>>>>> gateway for IP-to-non-IP interworking, i.e. an UE located in
>>>>>>>>> the non-IP network part.
>>>>>>>>>> Note: such scenarios are considered by MEGACO gateways
>>>>>>>>> (I've Cc'd megaco list).
>>>>>>>>>> 
>>>>>>>>>> An RTP Sender/Receiver located NOT in the UE
>>>> would question
>>>>>>>>> the value of RTP/RTCP QoE related performance measurements
>>>>>>>>> (because the UE is located outside the RTP domain).
>>>>>>>>>> 
>>>>>>>>>> Conclusions:
>>>>>>>>>> - the set of meaningful performance metrics may be
>>>>>>>>> dependent on the location of the RTP Sender/Receiver, e.g.
>>>>>>>>> whether in a UE, gateway, ...
>>>>>>>>>> - don't see any impact on transport level metrics
>>>>>>>>>> - ... but the set of meaningful application level metrics
>>>>>>>>>> 
>>>>>>>>>> Proposal for MONARCH:
>>>>>>>>>> #1: insert sub-clause title "3.1 End-to-end IP network
>>>>>>>>> architecture" below clause 3
>>>>>>>>>> 
>>>>>>>>>> #2: add a sub-clause 3.2 at the end of clause 3, sth like
>>>>>>>>>> 
>>>>>>>>>> "3.2 RTP Sender/Receiver entities located in network nodes
>>>>>>>>>> The location of the RTP Sender/Receiver entity may impact
>>>>>>>>> the set of meaningful metrics.
>>>>>>>>>> For instance: application level metrics for QoE related
>>>>>>>>> performance metrics are questionable (or doesn't really make
>>>>>>>>> sense at all) when measured in a network node (terminating
>>>>>>>>> the RTP) instead of the user equipment."
>>>>>>>>>> 
>>>>>>>>>> Something like this would help to avoid confusion.
>>>>>>>>>> I even believe that a QoE measurement in a network node
>>>>>>>>> would violate the QoE definition. Would be rather something
>>>>>>>>> like QoE* ("remote QoE"):-(
>>>>>>>>>> 
>>>>>>>>>> Such information would improve the MONARCH doc in
>>>>> my opinion.
>>>>>>>>>> Sorry for that late comment.
>>>>>>>>>> Any views?
>>>>>>>>> 
>>>>>>>>> [Qin]:
>>>>>>>>> Albrrecht, if you follow ealry list discussion on
>>>>>>>>> draft-hunt-avt-monarch-01, you will see the rough consensus
>>>>>>>>> to position this document was
>>>>>>>>> this daft should focus on guidelines for defining reporting
>>>>>>>>> blocks. That is to say the main purpose of MONARCH draft
>>>>>>> is how to
>>>>>>>>> provide guidelines for the development of new RTCP XR block
>>>>>>>>> types in XRBlock working group.
>>>>>>>> 
>>>>>>>> [ABS] ... then the title "monitoring architectures" is
>>>>> misleading.
>>>>>>>> Proposal: keep title, revise scope section on focus
>>>>>>>> 
>>>>>>>> [Qin]: No, the title is *RTP* monitoring architecture, we can
>>>>>>>> not expand scope into IP monitoring architecture.
>>>>>>> 
>>>>>>> [ABS] That's wasn't the intent! Did just focus on the key word.
>>>>>>> 
>>>>>>>> 
>>>>>>>>> 
>>>>>>>>> Therefore how and where to collect the metric from RTP
>>>>>>>>> endpoint is not scope of this document, in my opinion. since
>>>>>>>>> you may have many ways to do this and different vendors have
>>>>>>>>> their different appoaches. It will be better to leave this
>>>>>>>>> beyond the scope. But you are right, it will be more
>>>>>>>>> reasonable to measure QoE related performance metric at the
>>>>>>>>> RTP receiver.
>>>>>>>> 
>>>>>>>> [ABS] I would disagree. At least your statement should be
>>>>>>>> conditional, sth like
>>>>>>>> "QoE related performance metrics may be measured in a RTP
>>>>>>>> receiver, IF the RTP receiver function is located in user
>>>>>>>> equipment (e.g. IP terminal), because QoE performance metrics
>>>>>>>> are tightly coupled to the point of view of a 'user'.
>>>>>>>> ... IF NOT, then ..."
>>>>>>>> 
>>>>>>>> [Qin]: I am not sure user equipment or IP terminal is the
>>>>>>>> right term from RTP perspective.
>>>>>>>> 
>>>>>>>> Also if you read P.NAMS, P.NAMS model for calculating QoE
>>>>>>>> related metric can be placed either at the network or at
>>>>>> the client.
>>>>>>>> So I disagree with what you said.
>>>>>>> 
>>>>>>> [ABS] Not convinced at all.
>>>>>>> Guess you are referring to the "mid-point" models, right?
>>>>>>> The usage of such that models depends on "prior knowledge
>>>>>>> ..." information.
>>>>>>> Thus, the applicability is conditional. You may not make such
>>>>>>> a general statement.
>>>>>>> 
>>>>>>> 
>>>>>>>> 
>>>>>>>> Also as I said, how and where to collect the metric from RTP
>>>>>>>> endpoint is not scope of this document. It depends on the
>>>>>>>> model you are choosing, e.g., four operation modes specified
>>>>>>>> in P.NAMS.
>>>>>>>> Apparently this should not be specified again in RTP
>>>>>>>> monitoring architecture document.
>>>>>>>> 
>>>>>>>>> 
>>>>>>>>> Another point is it is not clear to me how RTP
>>>> monitoring has
>>>>>>>>> to do with architectureend to end IP network architecture .
>>>>>>>>> this draft mostly focus on discussing RTP level stuff.
>>>>>>>>> Therefore I am quite doubt that we should describe anything
>>>>>>>>> in this document like how
>>>>>>>>> RTP entties is mapped into network entities/nodes at
>>>>>> the IP layer.
>>>>>>>> 
>>>>>>>> [ABS] I don't got any problems to talk about architectural
>>>>>>>> framework for monitoring in this document. Such information
>>>>>>>> is required and this is the only IETF AVT doc about it.
>>>>>>>> The solution to this issue is rather simple to me:
>>>>>>>> - split the MONARCH "monitoring architecture" in
>>>>>>>> 1) a functional monitoring architecture (let's call it
>>>>> 'FMA') and
>>>>>>>> 2) a physical monitoring architecture (... 'PMA').
>>>>>>>> 
>>>>>>>> - the present MONARCH doc would describe the FMA at the level
>>>>>>>> of RTP entities (i.e., Fig. 1 entities, incl. all the RTP
>>>>>>>> topology components according RFC 5117)
>>>>>>>> 
>>>>>>>> - there are many options of functional-to-physical mappings,
>>>>>>>> i.e. how a FMA would be mapped on a PMA
>>>>>>>> - the mapping is typically dependent on considered network
>>>>>>>> architecture (like SIP, H.323, MGCP, IMS, wireless, etc
>>>>> networks)
>>>>>>>> 
>>>>>>>> - the present MONARCH doc would describe the FMA-to-PMA
>>>>>>>> mapping IF all RTP receiver/sender entities would be located
>>>>>>>> in physical IP terminals (UEs)
>>>>>>>> - etc
>>>>>>>> 
>>>>>>>> [Qin]: I can understand your point, but you can not do that.
>>>>>>>> Since this document is only focus on *RTP* monitoring
>>>>>>>> architecture, that is what it said in AVTCore milestone:
>>>>>>>> "
>>>>>>>> 
>>>>>>>> Goals and Milestones:
>>>>>>>> 
>>>>>>>> Feb 2011 - Submit Monitoring Architecture for RTP for
>>>>>>> Informational
>>>>>>>> 
>>>>>>>> "
>>>>>>> 
>>>>>>> [ABS] If you go back to my first email on this subject, and
>>>>>>> if you look at my proposal: that's not a lot, nothing which
>>>>>>> violates the charter, goals and milestones.
>>>>>>> 
>>>>>>> 
>>>>>>>> Also if you really don't see how to map FMA to PMA, you may
>>>>>>>> look at the P.NAMS models specifed in ITU-T P.NAMS.
>>>>>>>> As for how to use RTP monitoring architecture or RTP XR
>>>>>>>> Report in the IMS network architecture, you may look at:
>>>>>>>> http://tools.ietf.org/html/rfc6035
>>>>>>> 
>>>>>>> [ABS] That's the SIP reporting interface, i.e., applicable
>>>>>>> primarily for physical IP user equipment with embedded RTP
>>>>>>> sender/receiver function and SIP UA function.
>>>>>>> However, the applicability of RFC 6035 is limited for a
>>>>>>> SIP-to-PSTN gateway (because the RTP sender/receiver would be
>>>>>>> located NOT in user equipment. Also the P.NAMS mid-point
>>>>>>> model fails for such a scenario.
>>>>>>> 
>>>>>>>> ITU-T H.248.48.
>>>>>>>> But I haven't check the current status of H.248.48.
>>>>>>> 
>>>>>>> [ABS] Work is finalized, see
>>>>>>> http://www.itu.int/md/meetingdoc.asp?lang=en&parent=T09-SG16-1
>>>>>>> 11121-TD-PLEN-0419
>>>>>>> 
>>>>>>>> 
>>>>>>>>> 
>>>>>>>>> But as the author of this document, I am interested and open
>>>>>>>>> to other opinions.:-)
>>>>>>>> 
>>>>>>>> [ABS] Like to add a further aspect: a "functional monitoring
>>>>>>>> architecture" may be considered as a network overlay,
>>>>>>>> something which adds additional capabilities (here:
>>>>>>>> measurement services, reporting services on top of basic RTP
>>>>>>>> services).
>>>>>>>> Such an overlay concept is nothing new: e.g., the
>>>>>>>> MultiService Forum did define a "Performance Measurement &
>>>>>>>> Monitoring (PMM)" overlay network, or IETF RMON may be also
>>>>>>>> considered as such.
>>>>>>>> 
>>>>>>>>> 
>>>>>>>>>> Regards,
>>>>>>>>>> Albrecht
>>>>>>>>>> 
>>>>>>>>>> 
>>>>>>>>>> 
>>>>>>>>>> 
>>>>>>>>>>> -----Original Message-----
>>>>>>>>>>> From: avt-bounces@ietf.org
>>>> [mailto:avt-bounces@ietf.org] On
>>>>>>>>>>> Behalf Of internet-drafts@ietf.org
>>>>>>>>>>> Sent: Dienstag, 29. November 2011 08:56
>>>>>>>>>>> To: i-d-announce@ietf.org
>>>>>>>>>>> Cc: avt@ietf.org
>>>>>>>>>>> Subject: [AVTCORE] I-D Action:
>>>>>>> draft-ietf-avtcore-monarch-08.txt
>>>>>>>>>>> 
>>>>>>>>>>> 
>>>>>>>>>>> A New Internet-Draft is available from the on-line
>>>>>>>>>>> Internet-Drafts directories. This draft is a work
>>>>> item of the
>>>>>>>>>>> Audio/Video Transport Core Maintenance Working Group
>>>>>>> of the IETF.
>>>>>>>>>>> 
>>>>>>>>>>> Title           : Monitoring Architectures for RTP
>>>>>>>>>>> Author(s)       : Qin Wu
>>>>>>>>>>>                         Geoff Hunt
>>>>>>>>>>>                         Philip Arden
>>>>>>>>>>> Filename        : draft-ietf-avtcore-monarch-08.txt
>>>>>>>>>>> Pages           : 25
>>>>>>>>>>> Date            : 2011-11-28
>>>>>>>>>>> 
>>>>>>>>>>>  This memo proposes an architecture for
>>>>> extending RTCP with
>>>>>>>>>>> a new RTCP
>>>>>>>>>>>  XR (RFC3611) block type to report new metrics
>>>>>>> regarding media
>>>>>>>>>>>  transmission or reception quality, following RTCP
>>>>>> guideline
>>>>>>>>>>>  established in RFC5968.  This memo suggests that a new
>>>>>>>>> block should
>>>>>>>>>>>  contain a single metric or a small number of metrics
>>>>>>>>> relevant to a
>>>>>>>>>>>  single parameter of interest or concern, rather than
>>>>>>>>> containing a
>>>>>>>>>>>  number of metrics which attempt to provide
>>>> full coverage
>>>>>>>>>>> of all those
>>>>>>>>>>>  parameters of concern to a specific application.
>>>>>>>>> Applications may
>>>>>>>>>>>  then "mix and match" to create a set of blocks which
>>>>>>>>>>> covers their set
>>>>>>>>>>>  of concerns.  Where possible, a specific
>>>> block should be
>>>>>>>>>>> designed to
>>>>>>>>>>>  be re-usable across more than one application, for
>>>>>>>>> example, for all
>>>>>>>>>>>  of voice, streaming audio and video.
>>>>>>>>>>> 
>>>>>>>>>>> 
>>>>>>>>>>> A URL for this Internet-Draft is:
>>>>>>>>>>> 
>>>>>>>>> 
>>>>>>>> 
>>>>>>> 
>>>>>> 
>>>>> 
>>>> http://www.ietf.org/internet-drafts/draft-ietf-avtcore-monarch-08.txt
>>>>>>>>>>> 
>>>>>>>>>>> Internet-Drafts are also available by anonymous FTP at:
>>>>>>>>>>> ftp://ftp.ietf.org/internet-drafts/
>>>>>>>>>>> 
>>>>>>>>>>> This Internet-Draft can be retrieved at:
>>>>>>>>>>> 
>>>>>>>>> 
>>>>>>> 
>>>>> ftp://ftp.ietf.org/internet-drafts/draft-ietf-avtcore-monarch-08.txt
>>>>>>>>>>> 
>>>>>>>>>>> _______________________________________________
>>>>>>>>>>> Audio/Video Transport Core Maintenance
>>>>>>>>>>> avt@ietf.org
>>>>>>>>>>> https://www.ietf.org/mailman/listinfo/avt
>>>>>>>>>>> 
>>>>>>>>>> _______________________________________________
>>>>>>>>>> Audio/Video Transport Core Maintenance
>>>>>>>>>> avt@ietf.org
>>>>>>>>>> https://www.ietf.org/mailman/listinfo/avt
>>>>>>>>> 
>>>>>>>> =
>>>>>>> _______________________________________________
>>>>>>> Audio/Video Transport Core Maintenance
>>>>>>> avt@ietf.org
>>>>>>> https://www.ietf.org/mailman/listinfo/avt
>>>>>>> 
>>>>>> 
>>>>> 
>>>> 
>>> _______________________________________________
>>> Audio/Video Transport Core Maintenance
>>> avt@ietf.org
>>> https://www.ietf.org/mailman/listinfo/avt
>> 
>> 
>> 
>> -- 
>> Colin Perkins
>> http://csperkins.org/
>> 
>> 
>> 
>> _______________________________________________
>> Audio/Video Transport Core Maintenance
>> avt@ietf.org
>> https://www.ietf.org/mailman/listinfo/avt
> 
> 
> 
> -- 
> Colin Perkins
> http://csperkins.org/
> 
> 
> 
> _______________________________________________
> Audio/Video Transport Core Maintenance
> avt@ietf.org
> https://www.ietf.org/mailman/listinfo/avt

From csp@csperkins.org  Tue Dec 13 14:54:48 2011
Return-Path: <csp@csperkins.org>
X-Original-To: megaco@ietfa.amsl.com
Delivered-To: megaco@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8275511E80AE; Tue, 13 Dec 2011 14:54:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.224
X-Spam-Level: 
X-Spam-Status: No, score=-101.224 tagged_above=-999 required=5 tests=[AWL=1.175, BAYES_00=-2.599, J_CHICKENPOX_14=0.6, J_CHICKENPOX_74=0.6, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rMtwPJha7Mmt; Tue, 13 Dec 2011 14:54:46 -0800 (PST)
Received: from lon1-msapost-3.mail.demon.net (lon1-msapost-3.mail.demon.net [195.173.77.182]) by ietfa.amsl.com (Postfix) with ESMTP id 3971211E809B; Tue, 13 Dec 2011 14:54:46 -0800 (PST)
Received: from starkperkins.demon.co.uk ([80.176.158.71] helo=[192.168.0.30]) by lon1-post-3.mail.demon.net with esmtpsa (AUTH csperkins-dwh) (TLSv1:AES128-SHA:128) (Exim 4.69) id 1RabFD-0003iy-cz; Tue, 13 Dec 2011 22:54:45 +0000
Mime-Version: 1.0 (Apple Message framework v1251.1)
Content-Type: text/plain; charset=us-ascii
From: Colin Perkins <csp@csperkins.org>
X-Priority: 3
In-Reply-To: <CFFAC080E70043A5BD4536349C34EFDB@china.huawei.com>
Date: Tue, 13 Dec 2011 22:54:26 +0000
Content-Transfer-Encoding: quoted-printable
Message-Id: <1815848C-FE4C-48A0-8889-565198BEEC74@csperkins.org>
References: <20111129075613.12419.4377.idtracker@ietfa.amsl.com> <EAC481B4D8034C38AC54E1217F8D875D@china.huawei.com> <5F7BCCF5541B7444830A2288ABBEBC96216190077F@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com> <B527BAFA038842A8939A8C2D558074CD@china.huawei.com> <5F7BCCF5541B7444830A2288ABBEBC962161900908@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com> <9FF9B04A84E64AD7ABCCC4F2ACC1E19A@china.huawei.com> <5F7BCCF5541B7444830A2288ABBEBC9621620F4AF5@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com> <D44A4820E0D24DD79F6F5A4B7507D0D6@china.huawei.com> <5F7BCCF5541B7444830A2288ABBEBC9621620F4ED2@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com> <71112008FBA94D35B07FA6B4916075B6@china.huawei.com> <5F7BCCF5541B7444830A2288ABBEBC9621620F5258@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com> <6C618D1EA52146A781429C6B08C4A4FC@china.huawei.com> <5F7BCCF5541B7444830A2288ABBEBC9621620F5330@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com> <2BEF8708-58B8-4AEB-B3A6-702F46E58C12@csperkins.org> <CFFAC080E70043A5BD4536349C34EFDB@china.huawei.com>
To: Qin Wu <bill.wu@huawei.com>
X-Mailer: Apple Mail (2.1251.1)
X-Mailman-Approved-At: Wed, 14 Dec 2011 08:04:34 -0800
Cc: megaco@ietf.org, avt@ietf.org
Subject: Re: [Megaco] [AVTCORE] Types of monitoring architectures; RE:  I-D Action: draft-ietf-avtcore-monarch-08.txt
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.1.12
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: Tue, 13 Dec 2011 22:54:48 -0000

Qin,

Both this, and Albrecht's suggested additions, look reasonable to me.

Colin



On 13 Dec 2011, at 02:15, Qin Wu wrote:
> Hi, Colin:
> Thank for your suggestion. Besides Albrecht's proposed text, my =
additional proposal is to fix application level metric defintion in =
section 2
> OLD text:
> "
>   Application level metrics
>=20
>      Metrics relating to QoE related parameters.  These metrics are
>      measured at the application level and focus on quality of content
>      rather than network parameters.=20
> "
> New text
> "
>   Application level metrics
>=20
>      Metrics relating to application specific parameters or QoE =
related parameters.=20
>     Application specific parameters  are measured at the application =
level and focus
>     on quality of content rather than network performance.  QoE =
related parameters
>     reflect the end-to-end performance at the services level and is =
ususally measured
>     at the user endpoint.
> "
>=20
> Regards!
> -Qin
> ----- Original Message -----=20
> From: "Colin Perkins" <csp@csperkins.org>
> To: "Schwarz, Albrecht (Albrecht)" =
<albrecht.schwarz@alcatel-lucent.com>
> Cc: "Qin Wu" <bill.wu@huawei.com>; <avt@ietf.org>; <megaco@ietf.org>
> Sent: Tuesday, December 13, 2011 12:56 AM
> Subject: Re: [AVTCORE] Types of monitoring architectures; RE: I-D =
Action: draft-ietf-avtcore-monarch-08.txt
>=20
>=20
> Albrecht, Qin,
>=20
> It doesn't seem controversial that some metrics are only meaningful in =
some scenarios, or when measured at certain points in a system. I don't =
see how adding a statement to the monarch draft to recognise that could =
be problematic. Is there anything else being suggested here?
>=20
> Colin
>=20
>=20
> On 12 Dec 2011, at 10:33, Schwarz, Albrecht (Albrecht) wrote:
>> Hi Qin,
>>=20
>> I'm very aware about all that.
>> It looks like that you are now agreeing that QoE measurements are =
CONDITIONAL ("you got a number of IF statements, there might be even =
more ...").
>>=20
>> MONARCH is not talking about such conditions, thus some readers may =
got the impression that the metrics related to RTP traffic are =
UNCONDITIONAL (which is not true as you confirmed).
>>=20
>> If you go back to my very first email: I did just propose to indicate =
the conditional aspect. Don't understand why such kind of valuable info =
would be not in scope of MONARCH. Hm?
>>=20
>> Regards,
>> Albrecht
>>=20
>> PS
>> I did use the notion of a control plane agnostic "RTP-to-PSTN =
gateway". You did indicate control plane specific gateway types like =
SIP-to-PSTN or SIP-to-H.323. Now issue to use such signalling protocol =
specific examples, but it doesn't change the underlying issue.
>> The SIP side reporting capability based on RFC 6035 allows to report =
the outlined measurements, but the RFC itself does not specify whether =
the reported information is meaningful (which is OK because this is not =
subject of a reporting interface spec, it is rather subject of a network =
monitoring doc like MONARCH).
>> QoE measurements would be conditional in both gateway types (because =
such a gateway is NOT a user device despite the fact of an embedded SIP =
user agent entity).
>> Actually I would even question here the condition of "customer knows =
the original content" in many real network scenarios.
>>=20
>>=20
>>=20
>>> -----Original Message-----
>>> From: Qin Wu [mailto:bill.wu@huawei.com]
>>> Sent: Montag, 12. Dezember 2011 05:05
>>> To: Schwarz, Albrecht (Albrecht); avt@ietf.org
>>> Cc: megaco@ietf.org
>>> Subject: Re: [AVTCORE] Types of monitoring architectures; RE:
>>> I-D Action: draft-ietf-avtcore-monarch-08.txt
>>>=20
>>> Hi, Albrecht:
>>> My understanding to QoE measurment is:
>>> The factors that influence the QoE metric include encoding
>>> system, transport network, access network,home network and end =
device.
>>> If the customer(e.g., network operator) doesn't know the
>>> original content, the QoE metric should be usually measured
>>> at the user device.
>>> If the customer knows the original content, the QoE metric
>>> can be measured either in the network or at the user device.
>>> Given the growing popularity of connected devices, these
>>> devices may have different capability corresponding to CPU
>>> load, processing overhead, storage, batteries.
>>> If the cusomer want to measure QoE without considering
>>> connected devices with various capability , the QoE metric
>>> can be measured at the point between access network and home =
network.
>>>=20
>>> Regarding the monitoring scenario you mentioned, I am not
>>> familiar with such scenario with RTP-to-PSTN gateway deployed.
>>> But I am aware that there are scenarios with SIP to PSTN
>>> gateway or SIP to H.323 gateway widely deployed,  RFC6035
>>> defines a new SIP event package, vq-rtcpxr that enable the
>>> collection and  reporting of metrics that measure quality for
>>> RTP sessions. In such cases, RTCP XR VOIP metric with QoE
>>> metric included is measured at the user device and mapped
>>> into the equivalent SIP vq-rtcpxr parameter since SIP session
>>> call is established end to end and RTP media stream is
>>> exchanged directly between one endpoint and the other endpoint.
>>>=20
>>> Regards!
>>> -Qin
>>> ----- Original Message -----
>>> From: "Schwarz, Albrecht (Albrecht)"
>>> <albrecht.schwarz@alcatel-lucent.com>
>>> To: "Qin Wu" <bill.wu@huawei.com>; <avt@ietf.org>
>>> Cc: <megaco@ietf.org>
>>> Sent: Saturday, December 10, 2011 12:01 AM
>>> Subject: RE: [AVTCORE] Types of monitoring architectures; RE:
>>> I-D Action: draft-ietf-avtcore-monarch-08.txt
>>>=20
>>>=20
>>> How do you explain to a network operator the value of QoE
>>> measurements by an RTP receiver / RTP monitor component
>>> located in an RTP-to-PSTN gateway?
>>>=20
>>> This would be a monitoring scenario inline with MONARCH, but
>>> with valueless QoE results, right?
>>>=20
>>>=20
>>>> -----Original Message-----
>>>> From: Qin Wu [mailto:bill.wu@huawei.com]
>>>> Sent: Donnerstag, 8. Dezember 2011 03:26
>>>> To: Schwarz, Albrecht (Albrecht); avt@ietf.org
>>>> Cc: megaco@ietf.org
>>>> Subject: Re: [AVTCORE] Types of monitoring architectures; RE:
>>>> I-D Action: draft-ietf-avtcore-monarch-08.txt
>>>>=20
>>>> You reiterate what you propose for physical entities in the
>>>> early email.
>>>> I am still not convicing with that.
>>>>=20
>>>> Since we have RTP components like RTP end system, RTP mixer,
>>>> RTP media translator, RTP transport translator, RTP monitor
>>>> specified in RFC3550 can be built into these component as a
>>>> application. also monitor can be disjointed from these RTP
>>>> components as a third party monitor. why we need to specify
>>>> how to map RTP end system into user equipment, RTP translator
>>>> or RTP mixer can be mapped into RTP-PSTN gateway, or IP to IP
>>>> border gateway since we have already mapped monitor into
>>>> different RTP components.
>>>> How many PE types you can enumerate? why they should be scope
>>>> of RTP monitoring architecture?
>>>>=20
>>>> Also as specified in MONARCH draft, we have end sytem
>>>> metrics, transport level metric, transport level metric, they
>>>> can be measured and collected from the different RTP
>>>> comoponents specified in RFC3550, RFC5117. Apparently end
>>>> system metric can only be collected from RTP end system.
>>>> transport metric is collected from any RTP system in the RTP
>>>> monitoring architecture, regarding application level metric,
>>>> apparently they should be measured at the application layer
>>>> and can not be collected from RTP transport translator, Also
>>>> RTP transport translator is still a functional entity rather
>>>> than a physical entity. I am not convincing with what you
>>>> said about "contradiction", "lead to possible wrong expectations".
>>>>=20
>>>> Regards!
>>>> -Qin
>>>> ----- Original Message -----
>>>> From: "Schwarz, Albrecht (Albrecht)"
>>>> <albrecht.schwarz@alcatel-lucent.com>
>>>> To: "Qin Wu" <bill.wu@huawei.com>; <avt@ietf.org>
>>>> Cc: <megaco@ietf.org>
>>>> Sent: Thursday, December 08, 2011 12:24 AM
>>>> Subject: RE: [AVTCORE] Types of monitoring architectures; RE:
>>>> I-D Action: draft-ietf-avtcore-monarch-08.txt
>>>>=20
>>>>=20
>>>> Qin,
>>>> that's NOT the point.
>>>>=20
>>>> All RFC 3550 and RFC 5117 RTP components are FUNCTIONAL
>>> ENTITIES (FE).
>>>> e.g.,
>>>> - the RTP Monitor or RTP receiver FE may be located in
>>>> different PHYSICAL ENTITIES (PE), e.g.
>>>>       a1) a user equipment
>>>>       a2) a RTP-to-PSTN gateway
>>>>       a3) an IP-to-IP session border gateway (in a
>>>> back-to-back RTP endsystem topology)
>>>>       a3) ...
>>>>=20
>>>> - the RTP Monitor may be associated to an RTP transport
>>> translator ...
>>>>       b1) an IP-to-IP session border gateway
>>>>=20
>>>> The "RTP monitoring architecture" is IMPACTED by each
>>>> functional-to-physical mapping because e.g.
>>>> * QoE related metrics are questionable in case of a2
>>>> ("despite the fact of a RTP receiver function")
>>>> * application level metrics at the location of a RTP
>>>> transport translator are a contradiction in itself
>>>> * ...
>>>>=20
>>>> Again, it's not really changing the MONARCH draft because in
>>>> the very majority of scenarios it is correct. However, there
>>>> are few cases where the MONARCH description would be "too
>>>> high level", "not fully correct", "lead to possible wrong
>>>> expectations", ...
>>>>=20
>>>> Regards,
>>>> Albrecht
>>>>=20
>>>>=20
>>>>=20
>>>>> -----Original Message-----
>>>>> From: Qin Wu [mailto:bill.wu@huawei.com]
>>>>> Sent: Dienstag, 6. Dezember 2011 07:13
>>>>> To: Schwarz, Albrecht (Albrecht); avt@ietf.org
>>>>> Cc: megaco@ietf.org
>>>>> Subject: Re: [AVTCORE] Types of monitoring architectures; RE:
>>>>> I-D Action: draft-ietf-avtcore-monarch-08.txt
>>>>>=20
>>>>> If you talk about existing RFC5117 RTP topology components,
>>>>> this has already been covered by the current version of
>>>>> draft-ietf-avtcore-monarch.
>>>>> In most cases, an RTP system using RTCP XR is architecturally
>>>>> no different from an RTP system which does not use RTCP XR.
>>>>>=20
>>>>> Regards!
>>>>> -Qin
>>>>> ----- Original Message -----
>>>>> From: "Schwarz, Albrecht (Albrecht)"
>>>>> <albrecht.schwarz@alcatel-lucent.com>
>>>>> To: "Qin Wu" <bill.wu@huawei.com>; <avt@ietf.org>
>>>>> Cc: <megaco@ietf.org>
>>>>> Sent: Monday, December 05, 2011 10:48 PM
>>>>> Subject: RE: [AVTCORE] Types of monitoring architectures; RE:
>>>>> I-D Action: draft-ietf-avtcore-monarch-08.txt
>>>>>=20
>>>>>=20
>>>>> Hello Qin,
>>>>>=20
>>>>> to 1) Physical monitoring architecture
>>>>> Of course consideration of generic physical entities (PE),
>>>>> not specific to any network reference architectures defined
>>>>> by SDOs (like your refered entities).
>>>>> There would be just a few PE types ("given by the limited set
>>>>> of RTP topology components (RFC 5117)").
>>>>>=20
>>>>> to 2) (RFC 3550) Monitor function
>>>>> Right, that's a functional entity. The applicability of a
>>>>> monitor may be limited, dependent on ... (like in P.NAMS).
>>>>>=20
>>>>> to 3) your IMS network example
>>>>> Don't see the need to refer from MONARCH to a specific
>>>>> network architecture like IMS.
>>>>> Please also note that IMS is a functional architecture, not a
>>>>> physical architecture.
>>>>>=20
>>>>> Regards,
>>>>> Albrecht
>>>>>=20
>>>>> PS
>>>>> There are multiple options for adding the "RTP monitoring
>>>>> architecture" to a functional/physical network architecture:
>>>>> a) integrated approach: extension of existing functional
>>>>> entities or/and addition of RTP monitoring architectural
>>>>> components, extension or/and addition of
>>>>> signalling/management interfaces for control and
>>>>> configuration of RTP monitoring services, and reporting
>>>>> interfaces for measurement data ...
>>>>> b) overlay approach: separate specification to ...
>>>>>=20
>>>>>=20
>>>>> PSS
>>>>> BTW: there's a discussion paper with regards to the location
>>>>> of a monitor function in an IMS H.248 gateway entity:
>>>>> Measurements and statistics in IMS - Use Cases
>>>>> http://www.3gpp.org/ftp/tsg_ct/WG3_interworking_ex-CN3/TSGC3_5
>>>>> 8_Kyoto_Japan/Docs/C3-100469.zip
>>>>> This is just fyi.
>>>>>=20
>>>>>=20
>>>>>=20
>>>>>> -----Original Message-----
>>>>>> From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On
>>>>>> Behalf Of Qin Wu
>>>>>> Sent: Freitag, 2. Dezember 2011 02:55
>>>>>> To: Schwarz, Albrecht (Albrecht); avt@ietf.org
>>>>>> Cc: megaco@ietf.org
>>>>>> Subject: Re: [AVTCORE] Types of monitoring architectures; RE:
>>>>>> I-D Action: draft-ietf-avtcore-monarch-08.txt
>>>>>>=20
>>>>>> Hi, Albrecht:
>>>>>> No offence, I am not really convinced with your proposal on
>>>>>> physical monitoring architecture.
>>>>>> my counterquestion is what does physical monitoring
>>>>>> architecture looks like in your mind?
>>>>>> How many components do we have in such physical monitroing
>>>>>> architecture? what are they?
>>>>>> Take IMS network architecture as a example, they may have
>>>>>> P-CSCF,S-CSCF, SIP PBX, SBC, why do you believe monitor
>>>>>> described in draft-ietf-avtcore-monarch is mapped into
>>>>>> P-CSCF, S-CSCF, SBC, Media Gateway, Media Gateway Controller
>>>>>> should be in the scope of IETF RTP monitoring
>>> archtiecture draft?
>>>>>>=20
>>>>>> Monitor described in  draft-ietf-avtcore-monarch is well
>>>>>> defined in the section 3 of RFC3550 as follows:
>>>>>> "
>>>>>>=20
>>>>>>  Monitor: An application that receives RTCP packets sent by
>>>>>>     participants in an RTP session, in particular the
>>> reception
>>>>>>     reports, and estimates the current quality of service for
>>>>>>     distribution monitoring, fault diagnosis and long-term
>>>>>> statistics.
>>>>>>     The monitor function is likely to be built into the
>>>>>> application(s)
>>>>>>     participating in the session, but may also be a separate
>>>>>>     application that does not otherwise participate and
>>>>>> does not send
>>>>>>     or receive the RTP data packets (since they are on
>>>> a separate
>>>>>>     port).  These are called third-party monitors.  It is also
>>>>>>     acceptable for a third-party monitor to receive
>>> the RTP data
>>>>>>     packets but not send RTCP packets or otherwise be
>>>>> counted in the
>>>>>>     session.
>>>>>>=20
>>>>>> "
>>>>>> Isn't how to implent monitor into IMS netowork archtiecture a
>>>>>> implentation specific issue?
>>>>>> If this issue are really interesting, isn't it a good idea to
>>>>>> produce another new document to talk about this?
>>>>>> One good example for this motivation is this draft I like to
>>>>>> share with you:
>>>>>> http://tools.ietf.org/html/draft-kaplan-dispatch-b2bua-taxonom
>>>>>> y-00#section-4.6
>>>>>>=20
>>>>>> Regards!
>>>>>> -Qin
>>>>>> ----- Original Message -----
>>>>>> From: "Schwarz, Albrecht (Albrecht)"
>>>>>> <albrecht.schwarz@alcatel-lucent.com>
>>>>>> To: "Qin Wu" <bill.wu@huawei.com>; <avt@ietf.org>
>>>>>> Cc: <megaco@ietf.org>
>>>>>> Sent: Friday, December 02, 2011 12:20 AM
>>>>>> Subject: RE: [AVTCORE] Types of monitoring architectures; RE:
>>>>>> I-D Action: draft-ietf-avtcore-monarch-08.txt
>>>>>>=20
>>>>>>=20
>>>>>> My replies below ...
>>>>>> -Albrecht
>>>>>>=20
>>>>>>> -----Original Message-----
>>>>>>> From: Qin Wu [mailto:bill.wu@huawei.com]
>>>>>>> Sent: Donnerstag, 1. Dezember 2011 02:42
>>>>>>> To: Schwarz, Albrecht (Albrecht); avt@ietf.org
>>>>>>> Cc: megaco@ietf.org
>>>>>>> Subject: Re: [AVTCORE] Types of monitoring architectures; RE:
>>>>>>> I-D Action: draft-ietf-avtcore-monarch-08.txt
>>>>>>>=20
>>>>>>> Hi,
>>>>>>> ----- Original Message -----
>>>>>>> From: "Schwarz, Albrecht (Albrecht)"
>>>>>>> <albrecht.schwarz@alcatel-lucent.com>
>>>>>>> To: "Qin Wu" <bill.wu@huawei.com>; <avt@ietf.org>
>>>>>>> Cc: <megaco@ietf.org>
>>>>>>> Sent: Thursday, December 01, 2011 1:24 AM
>>>>>>> Subject: RE: [AVTCORE] Types of monitoring architectures; RE:
>>>>>>> I-D Action: draft-ietf-avtcore-monarch-08.txt
>>>>>>>=20
>>>>>>>=20
>>>>>>> My replies below inline,
>>>>>>> Albrecht
>>>>>>>=20
>>>>>>>> -----Original Message-----
>>>>>>>> From: Qin Wu [mailto:bill.wu@huawei.com]
>>>>>>>> Sent: Mittwoch, 30. November 2011 04:51
>>>>>>>> To: Schwarz, Albrecht (Albrecht); avt@ietf.org
>>>>>>>> Cc: megaco@ietf.org
>>>>>>>> Subject: Re: [AVTCORE] Types of monitoring
>>> architectures; RE:
>>>>>>>> I-D Action: draft-ietf-avtcore-monarch-08.txt
>>>>>>>>=20
>>>>>>>> Hi,
>>>>>>>> ----- Original Message -----
>>>>>>>> From: "Schwarz, Albrecht (Albrecht)"
>>>>>>>> <albrecht.schwarz@alcatel-lucent.com>
>>>>>>>> To: <avt@ietf.org>
>>>>>>>> Cc: <megaco@ietf.org>
>>>>>>>> Sent: Tuesday, November 29, 2011 7:32 PM
>>>>>>>> Subject: [AVTCORE] Types of monitoring
>>> architectures; RE: I-D
>>>>>>>> Action: draft-ietf-avtcore-monarch-08.txt
>>>>>>>>=20
>>>>>>>>=20
>>>>>>>>> Dear All,
>>>>>>>>>=20
>>>>>>>>> there are different types of monitoring architectures,
>>>>>>>> particularily from perspective of QoE related performance
>>>>>>> parameters.
>>>>>>>>> Let's recall QoE (e.g., ITU-T P.10 Amendment 2):
>>>>>>>>>=20
>>>>>>>>> Quality of Experience (QoE):
>>>>>>>>> The overall acceptability of an application or service, as
>>>>>>>> perceived subjectively by the end-user.
>>>>>>>>> NOTE 1 - Quality of experience includes the complete
>>>>>>>> end-to-end system effects (client, terminal, network,
>>>>>>>> services infrastructure, etc.).
>>>>>>>>> NOTE 2 - Overall acceptability may be influenced by user
>>>>>>>> expectations and context.
>>>>>>>>>=20
>>>>>>>>> Important for MONARCH:
>>>>>>>>> 1st ... perceived by end-user
>>>>>>>>> 2nd QoE includes the complete end-to-end sytem effects ...
>>>>>>>>>=20
>>>>>>>>> That said, present RTP monitoring architecture in MONARCH
>>>>>>>> according clause 3 is not specific on the type of monitoring
>>>>>>>> architecture. For instance, Fig. 1, it is possibly supposed
>>>>>>>> that the "RTP Sender" and "RTP Receiver" entities are equal
>>>>>>>> to a terminal/user equipment (UE). This would be an
>>>>>>>> end-to-end IP network scenario.
>>>>>>>>>=20
>>>>>>>>> However, the "RTP Sender" and "RTP Receiver" entities may
>>>>>>>> be also located at the edge of an IP network, e.g. in a
>>>>>>>> gateway for IP-to-non-IP interworking, i.e. an UE located in
>>>>>>>> the non-IP network part.
>>>>>>>>> Note: such scenarios are considered by MEGACO gateways
>>>>>>>> (I've Cc'd megaco list).
>>>>>>>>>=20
>>>>>>>>> An RTP Sender/Receiver located NOT in the UE
>>> would question
>>>>>>>> the value of RTP/RTCP QoE related performance measurements
>>>>>>>> (because the UE is located outside the RTP domain).
>>>>>>>>>=20
>>>>>>>>> Conclusions:
>>>>>>>>> - the set of meaningful performance metrics may be
>>>>>>>> dependent on the location of the RTP Sender/Receiver, e.g.
>>>>>>>> whether in a UE, gateway, ...
>>>>>>>>> - don't see any impact on transport level metrics
>>>>>>>>> - ... but the set of meaningful application level metrics
>>>>>>>>>=20
>>>>>>>>> Proposal for MONARCH:
>>>>>>>>> #1: insert sub-clause title "3.1 End-to-end IP network
>>>>>>>> architecture" below clause 3
>>>>>>>>>=20
>>>>>>>>> #2: add a sub-clause 3.2 at the end of clause 3, sth like
>>>>>>>>>=20
>>>>>>>>> "3.2 RTP Sender/Receiver entities located in network nodes
>>>>>>>>> The location of the RTP Sender/Receiver entity may impact
>>>>>>>> the set of meaningful metrics.
>>>>>>>>> For instance: application level metrics for QoE related
>>>>>>>> performance metrics are questionable (or doesn't really make
>>>>>>>> sense at all) when measured in a network node (terminating
>>>>>>>> the RTP) instead of the user equipment."
>>>>>>>>>=20
>>>>>>>>> Something like this would help to avoid confusion.
>>>>>>>>> I even believe that a QoE measurement in a network node
>>>>>>>> would violate the QoE definition. Would be rather something
>>>>>>>> like QoE* ("remote QoE"):-(
>>>>>>>>>=20
>>>>>>>>> Such information would improve the MONARCH doc in
>>>> my opinion.
>>>>>>>>> Sorry for that late comment.
>>>>>>>>> Any views?
>>>>>>>>=20
>>>>>>>> [Qin]:
>>>>>>>> Albrrecht, if you follow ealry list discussion on
>>>>>>>> draft-hunt-avt-monarch-01, you will see the rough consensus
>>>>>>>> to position this document was
>>>>>>>> this daft should focus on guidelines for defining reporting
>>>>>>>> blocks. That is to say the main purpose of MONARCH draft
>>>>>> is how to
>>>>>>>> provide guidelines for the development of new RTCP XR block
>>>>>>>> types in XRBlock working group.
>>>>>>>=20
>>>>>>> [ABS] ... then the title "monitoring architectures" is
>>>> misleading.
>>>>>>> Proposal: keep title, revise scope section on focus
>>>>>>>=20
>>>>>>> [Qin]: No, the title is *RTP* monitoring architecture, we can
>>>>>>> not expand scope into IP monitoring architecture.
>>>>>>=20
>>>>>> [ABS] That's wasn't the intent! Did just focus on the key word.
>>>>>>=20
>>>>>>>=20
>>>>>>>>=20
>>>>>>>> Therefore how and where to collect the metric from RTP
>>>>>>>> endpoint is not scope of this document, in my opinion. since
>>>>>>>> you may have many ways to do this and different vendors have
>>>>>>>> their different appoaches. It will be better to leave this
>>>>>>>> beyond the scope. But you are right, it will be more
>>>>>>>> reasonable to measure QoE related performance metric at the
>>>>>>>> RTP receiver.
>>>>>>>=20
>>>>>>> [ABS] I would disagree. At least your statement should be
>>>>>>> conditional, sth like
>>>>>>> "QoE related performance metrics may be measured in a RTP
>>>>>>> receiver, IF the RTP receiver function is located in user
>>>>>>> equipment (e.g. IP terminal), because QoE performance metrics
>>>>>>> are tightly coupled to the point of view of a 'user'.
>>>>>>> ... IF NOT, then ..."
>>>>>>>=20
>>>>>>> [Qin]: I am not sure user equipment or IP terminal is the
>>>>>>> right term from RTP perspective.
>>>>>>>=20
>>>>>>> Also if you read P.NAMS, P.NAMS model for calculating QoE
>>>>>>> related metric can be placed either at the network or at
>>>>> the client.
>>>>>>> So I disagree with what you said.
>>>>>>=20
>>>>>> [ABS] Not convinced at all.
>>>>>> Guess you are referring to the "mid-point" models, right?
>>>>>> The usage of such that models depends on "prior knowledge
>>>>>> ..." information.
>>>>>> Thus, the applicability is conditional. You may not make such
>>>>>> a general statement.
>>>>>>=20
>>>>>>=20
>>>>>>>=20
>>>>>>> Also as I said, how and where to collect the metric from RTP
>>>>>>> endpoint is not scope of this document. It depends on the
>>>>>>> model you are choosing, e.g., four operation modes specified
>>>>>>> in P.NAMS.
>>>>>>> Apparently this should not be specified again in RTP
>>>>>>> monitoring architecture document.
>>>>>>>=20
>>>>>>>>=20
>>>>>>>> Another point is it is not clear to me how RTP
>>> monitoring has
>>>>>>>> to do with architectureend to end IP network architecture .
>>>>>>>> this draft mostly focus on discussing RTP level stuff.
>>>>>>>> Therefore I am quite doubt that we should describe anything
>>>>>>>> in this document like how
>>>>>>>> RTP entties is mapped into network entities/nodes at
>>>>> the IP layer.
>>>>>>>=20
>>>>>>> [ABS] I don't got any problems to talk about architectural
>>>>>>> framework for monitoring in this document. Such information
>>>>>>> is required and this is the only IETF AVT doc about it.
>>>>>>> The solution to this issue is rather simple to me:
>>>>>>> - split the MONARCH "monitoring architecture" in
>>>>>>> 1) a functional monitoring architecture (let's call it
>>>> 'FMA') and
>>>>>>> 2) a physical monitoring architecture (... 'PMA').
>>>>>>>=20
>>>>>>> - the present MONARCH doc would describe the FMA at the level
>>>>>>> of RTP entities (i.e., Fig. 1 entities, incl. all the RTP
>>>>>>> topology components according RFC 5117)
>>>>>>>=20
>>>>>>> - there are many options of functional-to-physical mappings,
>>>>>>> i.e. how a FMA would be mapped on a PMA
>>>>>>> - the mapping is typically dependent on considered network
>>>>>>> architecture (like SIP, H.323, MGCP, IMS, wireless, etc
>>>> networks)
>>>>>>>=20
>>>>>>> - the present MONARCH doc would describe the FMA-to-PMA
>>>>>>> mapping IF all RTP receiver/sender entities would be located
>>>>>>> in physical IP terminals (UEs)
>>>>>>> - etc
>>>>>>>=20
>>>>>>> [Qin]: I can understand your point, but you can not do that.
>>>>>>> Since this document is only focus on *RTP* monitoring
>>>>>>> architecture, that is what it said in AVTCore milestone:
>>>>>>> "
>>>>>>>=20
>>>>>>> Goals and Milestones:
>>>>>>>=20
>>>>>>> Feb 2011 - Submit Monitoring Architecture for RTP for
>>>>>> Informational
>>>>>>>=20
>>>>>>> "
>>>>>>=20
>>>>>> [ABS] If you go back to my first email on this subject, and
>>>>>> if you look at my proposal: that's not a lot, nothing which
>>>>>> violates the charter, goals and milestones.
>>>>>>=20
>>>>>>=20
>>>>>>> Also if you really don't see how to map FMA to PMA, you may
>>>>>>> look at the P.NAMS models specifed in ITU-T P.NAMS.
>>>>>>> As for how to use RTP monitoring architecture or RTP XR
>>>>>>> Report in the IMS network architecture, you may look at:
>>>>>>> http://tools.ietf.org/html/rfc6035
>>>>>>=20
>>>>>> [ABS] That's the SIP reporting interface, i.e., applicable
>>>>>> primarily for physical IP user equipment with embedded RTP
>>>>>> sender/receiver function and SIP UA function.
>>>>>> However, the applicability of RFC 6035 is limited for a
>>>>>> SIP-to-PSTN gateway (because the RTP sender/receiver would be
>>>>>> located NOT in user equipment. Also the P.NAMS mid-point
>>>>>> model fails for such a scenario.
>>>>>>=20
>>>>>>> ITU-T H.248.48.
>>>>>>> But I haven't check the current status of H.248.48.
>>>>>>=20
>>>>>> [ABS] Work is finalized, see
>>>>>> http://www.itu.int/md/meetingdoc.asp?lang=3Den&parent=3DT09-SG16-1
>>>>>> 11121-TD-PLEN-0419
>>>>>>=20
>>>>>>>=20
>>>>>>>>=20
>>>>>>>> But as the author of this document, I am interested and open
>>>>>>>> to other opinions.:-)
>>>>>>>=20
>>>>>>> [ABS] Like to add a further aspect: a "functional monitoring
>>>>>>> architecture" may be considered as a network overlay,
>>>>>>> something which adds additional capabilities (here:
>>>>>>> measurement services, reporting services on top of basic RTP
>>>>>>> services).
>>>>>>> Such an overlay concept is nothing new: e.g., the
>>>>>>> MultiService Forum did define a "Performance Measurement &
>>>>>>> Monitoring (PMM)" overlay network, or IETF RMON may be also
>>>>>>> considered as such.
>>>>>>>=20
>>>>>>>>=20
>>>>>>>>> Regards,
>>>>>>>>> Albrecht
>>>>>>>>>=20
>>>>>>>>>=20
>>>>>>>>>=20
>>>>>>>>>=20
>>>>>>>>>> -----Original Message-----
>>>>>>>>>> From: avt-bounces@ietf.org
>>> [mailto:avt-bounces@ietf.org] On
>>>>>>>>>> Behalf Of internet-drafts@ietf.org
>>>>>>>>>> Sent: Dienstag, 29. November 2011 08:56
>>>>>>>>>> To: i-d-announce@ietf.org
>>>>>>>>>> Cc: avt@ietf.org
>>>>>>>>>> Subject: [AVTCORE] I-D Action:
>>>>>> draft-ietf-avtcore-monarch-08.txt
>>>>>>>>>>=20
>>>>>>>>>>=20
>>>>>>>>>> A New Internet-Draft is available from the on-line
>>>>>>>>>> Internet-Drafts directories. This draft is a work
>>>> item of the
>>>>>>>>>> Audio/Video Transport Core Maintenance Working Group
>>>>>> of the IETF.
>>>>>>>>>>=20
>>>>>>>>>> Title           : Monitoring Architectures for RTP
>>>>>>>>>> Author(s)       : Qin Wu
>>>>>>>>>>                         Geoff Hunt
>>>>>>>>>>                         Philip Arden
>>>>>>>>>> Filename        : draft-ietf-avtcore-monarch-08.txt
>>>>>>>>>> Pages           : 25
>>>>>>>>>> Date            : 2011-11-28
>>>>>>>>>>=20
>>>>>>>>>>  This memo proposes an architecture for
>>>> extending RTCP with
>>>>>>>>>> a new RTCP
>>>>>>>>>>  XR (RFC3611) block type to report new metrics
>>>>>> regarding media
>>>>>>>>>>  transmission or reception quality, following RTCP
>>>>> guideline
>>>>>>>>>>  established in RFC5968.  This memo suggests that a new
>>>>>>>> block should
>>>>>>>>>>  contain a single metric or a small number of metrics
>>>>>>>> relevant to a
>>>>>>>>>>  single parameter of interest or concern, rather than
>>>>>>>> containing a
>>>>>>>>>>  number of metrics which attempt to provide
>>> full coverage
>>>>>>>>>> of all those
>>>>>>>>>>  parameters of concern to a specific application.
>>>>>>>> Applications may
>>>>>>>>>>  then "mix and match" to create a set of blocks which
>>>>>>>>>> covers their set
>>>>>>>>>>  of concerns.  Where possible, a specific
>>> block should be
>>>>>>>>>> designed to
>>>>>>>>>>  be re-usable across more than one application, for
>>>>>>>> example, for all
>>>>>>>>>>  of voice, streaming audio and video.
>>>>>>>>>>=20
>>>>>>>>>>=20
>>>>>>>>>> A URL for this Internet-Draft is:
>>>>>>>>>>=20
>>>>>>>>=20
>>>>>>>=20
>>>>>>=20
>>>>>=20
>>>>=20
>>> =
http://www.ietf.org/internet-drafts/draft-ietf-avtcore-monarch-08.txt
>>>>>>>>>>=20
>>>>>>>>>> Internet-Drafts are also available by anonymous FTP at:
>>>>>>>>>> ftp://ftp.ietf.org/internet-drafts/
>>>>>>>>>>=20
>>>>>>>>>> This Internet-Draft can be retrieved at:
>>>>>>>>>>=20
>>>>>>>>=20
>>>>>>=20
>>>> =
ftp://ftp.ietf.org/internet-drafts/draft-ietf-avtcore-monarch-08.txt
>>>>>>>>>>=20
>>>>>>>>>> _______________________________________________
>>>>>>>>>> Audio/Video Transport Core Maintenance
>>>>>>>>>> avt@ietf.org
>>>>>>>>>> https://www.ietf.org/mailman/listinfo/avt
>>>>>>>>>>=20
>>>>>>>>> _______________________________________________
>>>>>>>>> Audio/Video Transport Core Maintenance
>>>>>>>>> avt@ietf.org
>>>>>>>>> https://www.ietf.org/mailman/listinfo/avt
>>>>>>>>=20
>>>>>>> =3D
>>>>>> _______________________________________________
>>>>>> Audio/Video Transport Core Maintenance
>>>>>> avt@ietf.org
>>>>>> https://www.ietf.org/mailman/listinfo/avt
>>>>>>=20
>>>>>=20
>>>>=20
>>>=20
>> _______________________________________________
>> Audio/Video Transport Core Maintenance
>> avt@ietf.org
>> https://www.ietf.org/mailman/listinfo/avt
>=20
>=20
>=20
> --=20
> Colin Perkins
> http://csperkins.org/
>=20
>=20
>=20
> _______________________________________________
> Audio/Video Transport Core Maintenance
> avt@ietf.org
> https://www.ietf.org/mailman/listinfo/avt



--=20
Colin Perkins
http://csperkins.org/



