
From javi@trajano.us.es  Tue Nov  1 04:37:21 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 1E1F921F8EFC for <megaco@ietfa.amsl.com>; Tue,  1 Nov 2011 04:37:21 -0700 (PDT)
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=[AWL=0.300,  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 xWVKc5TAxuVq for <megaco@ietfa.amsl.com>; Tue,  1 Nov 2011 04:37:20 -0700 (PDT)
Received: from mail.us.es (mail.us.es [193.147.175.20]) by ietfa.amsl.com (Postfix) with ESMTP id 204CD21F8EC7 for <megaco@ietf.org>; Tue,  1 Nov 2011 04:37:12 -0700 (PDT)
Received: (qmail 32129 invoked from network); 1 Nov 2011 12:37:10 +0100
Received: from unknown (HELO us.es) (192.168.2.11) by us.es with SMTP; 1 Nov 2011 12:37:10 +0100
Received: (qmail 18662 invoked by uid 507); 1 Nov 2011 11:37:05 -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/13874.   Clear:RC:1(127.0.0.1):.  Processed in 0.038902 secs); 01 Nov 2011 11:37:05 -0000
Received: from unknown (HELO antivirus1) (127.0.0.1) by us.es with SMTP; 1 Nov 2011 11:37:05 -0000
Received: from 192.168.1.13 (192.168.1.13) by antivirus1 (F-Secure/fsigk_smtp/406/antivirus1); Tue, 01 Nov 2011 12:37:05 +0100 (CET)
X-Virus-Status: clean(F-Secure/fsigk_smtp/406/antivirus1)
Received: (qmail 13373 invoked from network); 1 Nov 2011 12:37:05 +0100
Received: from trajano.us.es (193.147.162.130) by us.es with AES256-SHA encrypted SMTP; 1 Nov 2011 12:37:05 +0100
Received: from [127.0.0.1] (237.pool85-56-126.dynamic.orange.es [85.56.126.237]) (authenticated bits=0) by trajano.us.es (8.13.8/8.13.8/Debian-3) with ESMTP id pA1Bb2T9012563 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NOT); Tue, 1 Nov 2011 12:37:04 +0100
Message-ID: <4EAFD9D8.9010801@trajano.us.es>
Date: Tue, 01 Nov 2011 12:36:56 +0100
From: Javi <javi@trajano.us.es>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; es-ES; rv:1.9.2.23) Gecko/20110920 Thunderbird/3.1.15
MIME-Version: 1.0
To: "megaco@ietf.org" <megaco@ietf.org>
References: <4E980EF1.4020407@trajano.us.es>	<BLU0-SMTP5B76027A65AB404533C34D8E70@phx.gbl>	<4E9C185E.1090902@trajano.us.es>	<4E9D5509.4040105@trajano.us.es> <4E9FDE1A.4050207@trajano.us.es> <4E9FE5EF.6070907@nteczone.com> <4E9FEA09.3080900@trajano.us.es> <4EA62075.3060404@nteczone.com> <4EA6A2D4.2050903@trajano.us.es> <4EAA0413.5040007@nteczone.com> <4EAA7E0C.50807@trajano.us.es> <4EADDD8C.30509@nteczone.com> <4EAE763F.3020502@trajano.us.es> <4EAF4252.60403@nteczone.com>
In-Reply-To: <4EAF4252.60403@nteczone.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [Megaco] Multiple Streams and mutiplex terminations
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, 01 Nov 2011 11:37:21 -0000

Hello Christian,

Please see my comments below.

Regards,  Javi

>
>
>> b) "ISDNTerm/BA17/[TEI 1]" may be transported on HDLCPW1 but 
>> ""ISDNTerm/BA18/[TEI 1]" may be transported on HDLCPW2. How would you 
>> model this?. You would need to indicate the termination name in the 
>> properties:
>>
>> ISDNTerm/BA17
>> StreamID=1(TEI=[1,6],SAPI=16)\
>>                               \   ---- HDLCPW1
>> ISDNTerm/BA18                  \ /     StreamID=1 
>> (TEI=[1-ISDNTerm/BA17,9-ISDNTerm/BA19],SAPI=16)
>> StreamID=1(TEI=[1],SAPI=16) ----*
>>                                / \
>> ISDNTerm/BA19                 /   ---- HDLCPW2
>> StreamID=1(TEI=[9],SAPI=16)  /         StreamID=1 
>> (TEI=[6-ISDNTerm/BA17,1-ISDNTerm/BA18],SAPI=16)
>>
> [CNG] I suspected we'd end up at this case. It sounds like you're 
> trying to turn a single Context into an entire router to get around 
> the fact that you can't have a single physical termination in multiple 
> contexts. Have a look at H.248.64 to see how we handled that for an IP 
> router. How many more Terminations do you envisage in a Context?
>
> You could add TerminationID to the TEI parameter, but if you're having 
> lots of Termination it may quickly become complicated.

[Javi] Each MG may have over 50000 interfaces/terminations.

>>
>>
>> [CNG] Yes, so why do you propose a single Termination? Why not add 
>> the interfaces via multiple Terminations to the Context?
>>
>> [Javi] Yes. Indeed, this woud be my solution to the problem: Create 
>> an ephemeral termination for each flow, including flows of HDLCPWs:
>>
>> ISDNTerm/BA17/D/SAPI16,TEI1 --- * --- HDLCPW1/BA17/D/SAPI16,TEI1
>>
>> ISDNTerm/BA17/D/SAPI16,TEI6 --- * --- HDLCPW2/BA17/D/SAPI16,TEI6
>>
>> ISDNTerm/BA18/D/SAPI16,TEI1 --- * --- HDLCPW2/BA18/D/SAPI16,TEI1
>>
>> ISDNTerm/BA19/D/SAPI16,TEI9 --- * --- HDLCPW1/BA19/D/SAPI16,TEI9
>>
>>
>> I think this is possible.
> [CNG] A ephemeral Termination for an ISDN termination? These are 
> typically physical terminations.

[Javi] Really, for each interface I would create:

+ A physical termination maintained in the null context: to notify new 
packet calls to the MGC.

+ An ephemeral termination for each packet flow on the interface.

ISDNTerm/BA17/D [null context]

ISDNTerm/BA17/D/SAPI16,TEI1 --- * --- HDLCPW1/BA17/D/SAPI16,TEI1

ISDNTerm/BA17/D/SAPI16,TEI6 --- * --- HDLCPW2/BA17/D/SAPI16,TEI6

ISDNTerm/BA18/D [null context]

ISDNTerm/BA18/D/SAPI16,TEI1 --- * --- HDLCPW2/BA18/D/SAPI16,TEI1

ISDNTerm/BA19/D [null context]

ISDNTerm/BA19/D/SAPI16,TEI9 --- * --- HDLCPW1/BA19/D/SAPI16,TEI9

It was discussed at the forum the possibilty of creating more than one 
termination for each physical interface, and concluded that it was possible.

From Christian.Groves@nteczone.com  Tue Nov  1 16:48:59 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 C7FBA1F0C91 for <megaco@ietfa.amsl.com>; Tue,  1 Nov 2011 16:48:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.418
X-Spam-Level: 
X-Spam-Status: No, score=-2.418 tagged_above=-999 required=5 tests=[AWL=0.181,  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 0R8EeemJoLpw for <megaco@ietfa.amsl.com>; Tue,  1 Nov 2011 16:48:58 -0700 (PDT)
Received: from ipmail05.adl6.internode.on.net (ipmail05.adl6.internode.on.net [150.101.137.143]) by ietfa.amsl.com (Postfix) with ESMTP id 54C891F0C55 for <megaco@ietf.org>; Tue,  1 Nov 2011 16:48:56 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: ArQBANeBsE520S1T/2dsb2JhbAAMN6cxhQ8BAQEEOBsmEAsYCSUPAkYGDQEHAQEXvTSJBwSmAg
Received: from ppp118-209-45-83.lns20.mel4.internode.on.net (HELO [127.0.0.1]) ([118.209.45.83]) by ipmail05.adl6.internode.on.net with ESMTP; 02 Nov 2011 10:18:54 +1030
Message-ID: <4EB08561.90208@nteczone.com>
Date: Wed, 02 Nov 2011 10:48:49 +1100
From: Christian Groves <Christian.Groves@nteczone.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:7.0.1) Gecko/20110929 Thunderbird/7.0.1
MIME-Version: 1.0
To: Javi <javi@trajano.us.es>
References: <4E980EF1.4020407@trajano.us.es>	<BLU0-SMTP5B76027A65AB404533C34D8E70@phx.gbl>	<4E9C185E.1090902@trajano.us.es>	<4E9D5509.4040105@trajano.us.es> <4E9FDE1A.4050207@trajano.us.es> <4E9FE5EF.6070907@nteczone.com> <4E9FEA09.3080900@trajano.us.es> <4EA62075.3060404@nteczone.com> <4EA6A2D4.2050903@trajano.us.es> <4EAA0413.5040007@nteczone.com> <4EAA7E0C.50807@trajano.us.es> <4EADDD8C.30509@nteczone.com> <4EAE763F.3020502@trajano.us.es> <4EAF4252.60403@nteczone.com> <4EAFD9D8.9010801@trajano.us.es>
In-Reply-To: <4EAFD9D8.9010801@trajano.us.es>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "megaco@ietf.org" <megaco@ietf.org>
Subject: Re: [Megaco] Multiple Streams and mutiplex terminations
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, 01 Nov 2011 23:48:59 -0000

Hello Javi,

Which forum is this being discussed in?

Regards,
Christian

On 1/11/2011 10:36 PM, Javi wrote:
> Hello Christian,
>
> Please see my comments below.
>
> Regards,  Javi
>
>>
>>
>>> b) "ISDNTerm/BA17/[TEI 1]" may be transported on HDLCPW1 but 
>>> ""ISDNTerm/BA18/[TEI 1]" may be transported on HDLCPW2. How would 
>>> you model this?. You would need to indicate the termination name in 
>>> the properties:
>>>
>>> ISDNTerm/BA17
>>> StreamID=1(TEI=[1,6],SAPI=16)\
>>>                               \   ---- HDLCPW1
>>> ISDNTerm/BA18                  \ /     StreamID=1 
>>> (TEI=[1-ISDNTerm/BA17,9-ISDNTerm/BA19],SAPI=16)
>>> StreamID=1(TEI=[1],SAPI=16) ----*
>>>                                / \
>>> ISDNTerm/BA19                 /   ---- HDLCPW2
>>> StreamID=1(TEI=[9],SAPI=16)  /         StreamID=1 
>>> (TEI=[6-ISDNTerm/BA17,1-ISDNTerm/BA18],SAPI=16)
>>>
>> [CNG] I suspected we'd end up at this case. It sounds like you're 
>> trying to turn a single Context into an entire router to get around 
>> the fact that you can't have a single physical termination in 
>> multiple contexts. Have a look at H.248.64 to see how we handled that 
>> for an IP router. How many more Terminations do you envisage in a 
>> Context?
>>
>> You could add TerminationID to the TEI parameter, but if you're 
>> having lots of Termination it may quickly become complicated.
>
> [Javi] Each MG may have over 50000 interfaces/terminations.
>
>>>
>>>
>>> [CNG] Yes, so why do you propose a single Termination? Why not add 
>>> the interfaces via multiple Terminations to the Context?
>>>
>>> [Javi] Yes. Indeed, this woud be my solution to the problem: Create 
>>> an ephemeral termination for each flow, including flows of HDLCPWs:
>>>
>>> ISDNTerm/BA17/D/SAPI16,TEI1 --- * --- HDLCPW1/BA17/D/SAPI16,TEI1
>>>
>>> ISDNTerm/BA17/D/SAPI16,TEI6 --- * --- HDLCPW2/BA17/D/SAPI16,TEI6
>>>
>>> ISDNTerm/BA18/D/SAPI16,TEI1 --- * --- HDLCPW2/BA18/D/SAPI16,TEI1
>>>
>>> ISDNTerm/BA19/D/SAPI16,TEI9 --- * --- HDLCPW1/BA19/D/SAPI16,TEI9
>>>
>>>
>>> I think this is possible.
>> [CNG] A ephemeral Termination for an ISDN termination? These are 
>> typically physical terminations.
>
> [Javi] Really, for each interface I would create:
>
> + A physical termination maintained in the null context: to notify new 
> packet calls to the MGC.
>
> + An ephemeral termination for each packet flow on the interface.
>
> ISDNTerm/BA17/D [null context]
>
> ISDNTerm/BA17/D/SAPI16,TEI1 --- * --- HDLCPW1/BA17/D/SAPI16,TEI1
>
> ISDNTerm/BA17/D/SAPI16,TEI6 --- * --- HDLCPW2/BA17/D/SAPI16,TEI6
>
> ISDNTerm/BA18/D [null context]
>
> ISDNTerm/BA18/D/SAPI16,TEI1 --- * --- HDLCPW2/BA18/D/SAPI16,TEI1
>
> ISDNTerm/BA19/D [null context]
>
> ISDNTerm/BA19/D/SAPI16,TEI9 --- * --- HDLCPW1/BA19/D/SAPI16,TEI9
>
> It was discussed at the forum the possibilty of creating more than one 
> termination for each physical interface, and concluded that it was 
> possible.
>

From javi@trajano.us.es  Wed Nov  2 02:38:03 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 01F1711E80F9 for <megaco@ietfa.amsl.com>; Wed,  2 Nov 2011 02:38:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[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 m9tgY89b+tjw for <megaco@ietfa.amsl.com>; Wed,  2 Nov 2011 02:38:02 -0700 (PDT)
Received: from mail.us.es (mail.us.es [193.147.175.20]) by ietfa.amsl.com (Postfix) with ESMTP id D53DB11E80D9 for <megaco@ietf.org>; Wed,  2 Nov 2011 02:38:01 -0700 (PDT)
Received: (qmail 4408 invoked from network); 2 Nov 2011 10:37:59 +0100
Received: from unknown (HELO us.es) (192.168.2.13) by us.es with SMTP; 2 Nov 2011 10:37:59 +0100
Received: (qmail 31613 invoked by uid 507); 2 Nov 2011 09:37:58 -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/13879.   Clear:RC:1(127.0.0.1):.  Processed in 0.048444 secs); 02 Nov 2011 09:37:58 -0000
Received: from unknown (HELO antivirus3) (127.0.0.1) by us.es with SMTP; 2 Nov 2011 09:37:57 -0000
Received: from 192.168.1.13 (192.168.1.13) by antivirus3 (F-Secure/fsigk_smtp/406/antivirus3); Wed, 02 Nov 2011 10:37:57 +0100 (CET)
X-Virus-Status: clean(F-Secure/fsigk_smtp/406/antivirus3)
Received: (qmail 12496 invoked from network); 2 Nov 2011 10:37:57 +0100
Received: from trajano.us.es (193.147.162.130) by us.es with AES256-SHA encrypted SMTP; 2 Nov 2011 10:37:57 +0100
Received: from [127.0.0.1] (107.104.20.95.dynamic.jazztel.es [95.20.104.107]) (authenticated bits=0) by trajano.us.es (8.13.8/8.13.8/Debian-3) with ESMTP id pA29bqP3027044 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NOT); Wed, 2 Nov 2011 10:37:53 +0100
Message-ID: <4EB10F6F.9000201@trajano.us.es>
Date: Wed, 02 Nov 2011 10:37:51 +0100
From: Javi <javi@trajano.us.es>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; es-ES; rv:1.9.2.23) Gecko/20110920 Thunderbird/3.1.15
MIME-Version: 1.0
To: "megaco@ietf.org" <megaco@ietf.org>
References: <4E980EF1.4020407@trajano.us.es>	<BLU0-SMTP5B76027A65AB404533C34D8E70@phx.gbl>	<4E9C185E.1090902@trajano.us.es>	<4E9D5509.4040105@trajano.us.es> <4E9FDE1A.4050207@trajano.us.es> <4E9FE5EF.6070907@nteczone.com> <4E9FEA09.3080900@trajano.us.es> <4EA62075.3060404@nteczone.com> <4EA6A2D4.2050903@trajano.us.es> <4EAA0413.5040007@nteczone.com> <4EAA7E0C.50807@trajano.us.es> <4EADDD8C.30509@nteczone.com> <4EAE763F.3020502@trajano.us.es> <4EAF4252.60403@nteczone.com> <4EAFD9D8.9010801@trajano.us.es> <4EB08561.90208@nteczone.com>
In-Reply-To: <4EB08561.90208@nteczone.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
Subject: Re: [Megaco] Multiple Streams and mutiplex terminations
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, 02 Nov 2011 09:38:03 -0000

Hello Christian,

http://www.ietf.org/mail-archive/web/megaco/current/msg08470.html

Regards,

Javi


El 02/11/2011 0:48, Christian Groves escribió:
> Hello Javi,
>
> Which forum is this being discussed in?
>
> Regards,
> Christian
>
> On 1/11/2011 10:36 PM, Javi wrote:
>> Hello Christian,
>>
>> Please see my comments below.
>>
>> Regards,  Javi
>>
>>>
>>>
>>>> b) "ISDNTerm/BA17/[TEI 1]" may be transported on HDLCPW1 but 
>>>> ""ISDNTerm/BA18/[TEI 1]" may be transported on HDLCPW2. How would 
>>>> you model this?. You would need to indicate the termination name in 
>>>> the properties:
>>>>
>>>> ISDNTerm/BA17
>>>> StreamID=1(TEI=[1,6],SAPI=16)\
>>>>                               \   ---- HDLCPW1
>>>> ISDNTerm/BA18                  \ /     StreamID=1 
>>>> (TEI=[1-ISDNTerm/BA17,9-ISDNTerm/BA19],SAPI=16)
>>>> StreamID=1(TEI=[1],SAPI=16) ----*
>>>>                                / \
>>>> ISDNTerm/BA19                 /   ---- HDLCPW2
>>>> StreamID=1(TEI=[9],SAPI=16)  /         StreamID=1 
>>>> (TEI=[6-ISDNTerm/BA17,1-ISDNTerm/BA18],SAPI=16)
>>>>
>>> [CNG] I suspected we'd end up at this case. It sounds like you're 
>>> trying to turn a single Context into an entire router to get around 
>>> the fact that you can't have a single physical termination in 
>>> multiple contexts. Have a look at H.248.64 to see how we handled 
>>> that for an IP router. How many more Terminations do you envisage in 
>>> a Context?
>>>
>>> You could add TerminationID to the TEI parameter, but if you're 
>>> having lots of Termination it may quickly become complicated.
>>
>> [Javi] Each MG may have over 50000 interfaces/terminations.
>>
>>>>
>>>>
>>>> [CNG] Yes, so why do you propose a single Termination? Why not add 
>>>> the interfaces via multiple Terminations to the Context?
>>>>
>>>> [Javi] Yes. Indeed, this woud be my solution to the problem: Create 
>>>> an ephemeral termination for each flow, including flows of HDLCPWs:
>>>>
>>>> ISDNTerm/BA17/D/SAPI16,TEI1 --- * --- HDLCPW1/BA17/D/SAPI16,TEI1
>>>>
>>>> ISDNTerm/BA17/D/SAPI16,TEI6 --- * --- HDLCPW2/BA17/D/SAPI16,TEI6
>>>>
>>>> ISDNTerm/BA18/D/SAPI16,TEI1 --- * --- HDLCPW2/BA18/D/SAPI16,TEI1
>>>>
>>>> ISDNTerm/BA19/D/SAPI16,TEI9 --- * --- HDLCPW1/BA19/D/SAPI16,TEI9
>>>>
>>>>
>>>> I think this is possible.
>>> [CNG] A ephemeral Termination for an ISDN termination? These are 
>>> typically physical terminations.
>>
>> [Javi] Really, for each interface I would create:
>>
>> + A physical termination maintained in the null context: to notify 
>> new packet calls to the MGC.
>>
>> + An ephemeral termination for each packet flow on the interface.
>>
>> ISDNTerm/BA17/D [null context]
>>
>> ISDNTerm/BA17/D/SAPI16,TEI1 --- * --- HDLCPW1/BA17/D/SAPI16,TEI1
>>
>> ISDNTerm/BA17/D/SAPI16,TEI6 --- * --- HDLCPW2/BA17/D/SAPI16,TEI6
>>
>> ISDNTerm/BA18/D [null context]
>>
>> ISDNTerm/BA18/D/SAPI16,TEI1 --- * --- HDLCPW2/BA18/D/SAPI16,TEI1
>>
>> ISDNTerm/BA19/D [null context]
>>
>> ISDNTerm/BA19/D/SAPI16,TEI9 --- * --- HDLCPW1/BA19/D/SAPI16,TEI9
>>
>> It was discussed at the forum the possibilty of creating more than 
>> one termination for each physical interface, and concluded that it 
>> was possible.
>>
>


From Raphael.Tryster@Teledata-Networks.com  Sun Nov  6 04:52:11 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 5E11421F8484 for <megaco@ietfa.amsl.com>; Sun,  6 Nov 2011 04:52:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.05
X-Spam-Level: *
X-Spam-Status: No, score=1.05 tagged_above=-999 required=5 tests=[BAYES_05=-1.11, 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 390MY4fIAVMT for <megaco@ietfa.amsl.com>; Sun,  6 Nov 2011 04:52:10 -0800 (PST)
Received: from teledata-networks.com (mail.teledata-networks.com [81.218.12.242]) by ietfa.amsl.com (Postfix) with ESMTP id EB95C21F8480 for <megaco@ietf.org>; Sun,  6 Nov 2011 04:52:08 -0800 (PST)
Received: from Internal Mail-Server by Mail-SeCure (envelope-from Raphael.Tryster@Teledata-Networks.com) with SMTP; 6 Nov 2011 14:45:56 +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: Sun, 6 Nov 2011 14:52:02 +0200
Message-ID: <D6FAAE89E48C5B488B41BEBBDCD746CD07AB2C7D@tndcmail.Teledata.Local>
In-Reply-To: <ABA227A15B80D511BD1A00508BF93A1C0C8307F0@zrtpd0jq.us.nortel.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Fwd: FW: [MEGACO] Can a gateway drop active calls?]
Thread-Index: AcOkg/nVtnd2KbbVQBiqwV+T4LzLu5Hv/YHw
From: "Raphael Tryster" <Raphael.Tryster@Teledata-Networks.com>
To: <megaco@ietf.org>
Subject: Re: [Megaco] [Fwd: FW: [MEGACO] Can a gateway drop active calls?]
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, 06 Nov 2011 12:52:11 -0000

Hi Kevin,

Could you please point me to the reference containing the prohibition in
your middle paragraph in this old email?

Regards,
Raphael


-----Original Message-----
From: Kevin Boyle [mailto:kboyle@nortelnetworks.com]=20
Sent: Thursday, 6 November 2003 6:37 PM
To: Kalleitner Franz; megaco@ietf.org
Subject: RE: [Fwd: FW: [MEGACO] Can a gateway drop active calls?]

The MGC could figure out that the MG has gone, but remember that the MGC
cannot establish control associations.  So, this means that the MGC has
to
wait for the MG to make the next contact, not the other way around.  For
the
primary MGC, this will be via a SC Disconnected.

The MG is specifically prohibited from altering terminations or contexts
without MGC direction.  Because of this prohibition, the MGC MUST
intervene
to clean up any contexts that existed at the time of communications
loss.
The only exception to this is if the MG undergoes a Cold Boot, at which
time
the MGC can assume that all state is lost and the MG is in a newly
started
state.

Also note that there is no such thing as an endpoint in H.248.  H.248
operates on terminations.  Terminations and endpoints are two different
concepts.

Kevin

-----Original Message-----
From: Kalleitner Franz [mailto:franz.kalleitner@siemens.com]=20
Sent: Thursday, November 06, 2003 8:27 AM
To: megaco@ietf.org
Subject: AW: [Fwd: FW: [MEGACO] Can a gateway drop active calls?]

I would say, MGC would also detect that the MG is not accessable. If no
other possibility can be triggered to access the MG. MGC would start to
release the calls on signaling level.=20
The end point would stop transferring user payload or start a bearer
release
depending on the chosen L2/L3 protocol used for the connection.

ciao
Franz


-----Ursprungliche Nachricht-----
Von: Kevin Boyle [mailto:kboyle@nortelnetworks.com]
Gesendet: Mittwoch, 05. November 2003 15:17
An: megaco@ietf.org
Betreff: RE: [Fwd: FW: [MEGACO] Can a gateway drop active calls?]


Comments inline. [KJBII]

Kevin

-----Original Message-----
From: Taylor, Tom-PT [CAR:5N00:EXCH]
Sent: Wednesday, November 05, 2003 8:14 AM
To: megaco@ietf.org
Subject: [Fwd: FW: [MEGACO] Can a gateway drop active calls?]



-------- Original Message --------
Subject: 	FW: [MEGACO] Can a gateway drop active calls?
Date: 	Wed, 5 Nov 2003 14:58:11 +0200
From: 	Nurit Shenhar <NuritS@audiocodes.com>
To: 	Taylor, Tom-PT [CAR:5N00:EXCH]<taylor@americasm01.nt.com>



Tom



Again, it didn't reach the list...



Nurit



-----Original Message-----
*From:* Nurit Shenhar
*Sent:* Wednesday, November 05, 2003 9:00 AM
*To:* 'megaco@ietf.org'
*Subject:* [MEGACO] Can a gateway drop active calls?



Hi



Assuming the following scenario:

    1. GW is active with open calls.
    2. Connection with the MGC is lost, and reconnection to all possible
       MGC is not successful. This state goes on for a long time
       (minutes, hours).



Is it legitimate for the GW in this state to drop the active calls?

[KJBII] Technically no.  However, if the MG is unable to connect to any
MGCs, how would the MGCs know the MG didn't undergo a cold boot?  Be
very
careful here, though -- subscribers tend to complain a lot to their
providers when calls are dropped.  I think that if an MG wants to drop
calls, it better have a very good reason -- that is, it should cold
reboot.

*/ /*

*/Nurit Shenhar/*

*/H.248 Prime/*



**

E-Mail: nurit.shenhar@audiocodes.com

Fax.    +972-3-5394223

www.audiocodes.com <http://www.audiocodes.com/>






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

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

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

_______________________________________________
Megaco mailing list
Megaco@ietf.org
https://www1.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  Sun Nov 13 21:31:58 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 B205611E8118 for <megaco@ietfa.amsl.com>; Sun, 13 Nov 2011 21:31:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.452
X-Spam-Level: 
X-Spam-Status: No, score=-2.452 tagged_above=-999 required=5 tests=[AWL=0.147,  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 zu+A4Q45pzRF for <megaco@ietfa.amsl.com>; Sun, 13 Nov 2011 21:31:57 -0800 (PST)
Received: from ipmail05.adl6.internode.on.net (ipmail05.adl6.internode.on.net [150.101.137.143]) by ietfa.amsl.com (Postfix) with ESMTP id 82F1411E8124 for <megaco@ietf.org>; Sun, 13 Nov 2011 21:31:56 -0800 (PST)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: ApMBAN6kwE520aTE/2dsb2JhbAAMNqx0AQEBAwEyAQUbJQEQCxgJFg8JAwIBAgFFBg0BBwEBBRKHZwi2S4l/BKY7
Received: from ppp118-209-164-196.lns20.mel6.internode.on.net (HELO [127.0.0.1]) ([118.209.164.196]) by ipmail05.adl6.internode.on.net with ESMTP; 14 Nov 2011 16:01:53 +1030
Message-ID: <4EC0A7C7.9090201@nteczone.com>
Date: Mon, 14 Nov 2011 16:31:51 +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: Javi <javi@trajano.us.es>
References: <4E980EF1.4020407@trajano.us.es>	<BLU0-SMTP5B76027A65AB404533C34D8E70@phx.gbl>	<4E9C185E.1090902@trajano.us.es>	<4E9D5509.4040105@trajano.us.es> <4E9FDE1A.4050207@trajano.us.es> <4E9FE5EF.6070907@nteczone.com> <4E9FEA09.3080900@trajano.us.es> <4EA62075.3060404@nteczone.com> <4EA6A2D4.2050903@trajano.us.es> <4EAA0413.5040007@nteczone.com> <4EAA7E0C.50807@trajano.us.es> <4EADDD8C.30509@nteczone.com> <4EAE763F.3020502@trajano.us.es> <4EAF4252.60403@nteczone.com> <4EAFD9D8.9010801@trajano.us.es> <4EB08561.90208@nteczone.com> <4EB10F6F.9000201@trajano.us.es>
In-Reply-To: <4EB10F6F.9000201@trajano.us.es>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
Cc: "megaco@ietf.org" <megaco@ietf.org>
Subject: Re: [Megaco] Multiple Streams and mutiplex terminations
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, 14 Nov 2011 05:31:58 -0000

Hell Javi,

Please see ny responses below marked [CNG].

Regards, Christian

On 2/11/2011 8:37 PM, Javi wrote:
> Hello Christian,
>
> http://www.ietf.org/mail-archive/web/megaco/current/msg08470.html

[CNG] OK I thought you meant somewhere other than the Megaco list.

>
> Regards,
>
> Javi
>
>
> El 02/11/2011 0:48, Christian Groves escribió:
>> Hello Javi,
>>
>> Which forum is this being discussed in?
>>
>> Regards,
>> Christian
>>
>> On 1/11/2011 10:36 PM, Javi wrote:
>>> Hello Christian,
>>>
>>> Please see my comments below.
>>>
>>> Regards,  Javi
>>>
>>>>
>>>>
>>>>> b) "ISDNTerm/BA17/[TEI 1]" may be transported on HDLCPW1 but 
>>>>> ""ISDNTerm/BA18/[TEI 1]" may be transported on HDLCPW2. How would 
>>>>> you model this?. You would need to indicate the termination name 
>>>>> in the properties:
>>>>>
>>>>> ISDNTerm/BA17
>>>>> StreamID=1(TEI=[1,6],SAPI=16)\
>>>>>                               \   ---- HDLCPW1
>>>>> ISDNTerm/BA18                  \ /     StreamID=1 
>>>>> (TEI=[1-ISDNTerm/BA17,9-ISDNTerm/BA19],SAPI=16)
>>>>> StreamID=1(TEI=[1],SAPI=16) ----*
>>>>>                                / \
>>>>> ISDNTerm/BA19                 /   ---- HDLCPW2
>>>>> StreamID=1(TEI=[9],SAPI=16)  /         StreamID=1 
>>>>> (TEI=[6-ISDNTerm/BA17,1-ISDNTerm/BA18],SAPI=16)
>>>>>
>>>> [CNG] I suspected we'd end up at this case. It sounds like you're 
>>>> trying to turn a single Context into an entire router to get around 
>>>> the fact that you can't have a single physical termination in 
>>>> multiple contexts. Have a look at H.248.64 to see how we handled 
>>>> that for an IP router. How many more Terminations do you envisage 
>>>> in a Context?
>>>>
>>>> You could add TerminationID to the TEI parameter, but if you're 
>>>> having lots of Termination it may quickly become complicated.
>>>
>>> [Javi] Each MG may have over 50000 interfaces/terminations.
>>>
>>>>>
>>>>>
>>>>> [CNG] Yes, so why do you propose a single Termination? Why not add 
>>>>> the interfaces via multiple Terminations to the Context?
>>>>>
>>>>> [Javi] Yes. Indeed, this woud be my solution to the problem: 
>>>>> Create an ephemeral termination for each flow, including flows of 
>>>>> HDLCPWs:
>>>>>
>>>>> ISDNTerm/BA17/D/SAPI16,TEI1 --- * --- HDLCPW1/BA17/D/SAPI16,TEI1
>>>>>
>>>>> ISDNTerm/BA17/D/SAPI16,TEI6 --- * --- HDLCPW2/BA17/D/SAPI16,TEI6
>>>>>
>>>>> ISDNTerm/BA18/D/SAPI16,TEI1 --- * --- HDLCPW2/BA18/D/SAPI16,TEI1
>>>>>
>>>>> ISDNTerm/BA19/D/SAPI16,TEI9 --- * --- HDLCPW1/BA19/D/SAPI16,TEI9
>>>>>
>>>>>
>>>>> I think this is possible.
>>>> [CNG] A ephemeral Termination for an ISDN termination? These are 
>>>> typically physical terminations.
>>>
>>> [Javi] Really, for each interface I would create:
>>>
>>> + A physical termination maintained in the null context: to notify 
>>> new packet calls to the MGC.
>>>
>>> + An ephemeral termination for each packet flow on the interface.
>>>
>>> ISDNTerm/BA17/D [null context]
>>>
>>> ISDNTerm/BA17/D/SAPI16,TEI1 --- * --- HDLCPW1/BA17/D/SAPI16,TEI1
>>>
>>> ISDNTerm/BA17/D/SAPI16,TEI6 --- * --- HDLCPW2/BA17/D/SAPI16,TEI6
>>>
>>> ISDNTerm/BA18/D [null context]
>>>
>>> ISDNTerm/BA18/D/SAPI16,TEI1 --- * --- HDLCPW2/BA18/D/SAPI16,TEI1
>>>
>>> ISDNTerm/BA19/D [null context]
>>>
>>> ISDNTerm/BA19/D/SAPI16,TEI9 --- * --- HDLCPW1/BA19/D/SAPI16,TEI9
>>>
>>> It was discussed at the forum the possibilty of creating more than 
>>> one termination for each physical interface, and concluded that it 
>>> was possible.
>>>
[CNG] I think there is only ever one physical termination. There can be 
empheral terminations to describe the connection topology. Something 
like the above would be possible although you would need to work on your 
naming conventions to ensure they are valid.
>>
>
>

From javi@trajano.us.es  Mon Nov 14 02:02:15 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 36FBA21F8DE5 for <megaco@ietfa.amsl.com>; Mon, 14 Nov 2011 02:01:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.239
X-Spam-Level: 
X-Spam-Status: No, score=-6.239 tagged_above=-999 required=5 tests=[AWL=0.060,  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 j5o6zI1g2E3a for <megaco@ietfa.amsl.com>; Mon, 14 Nov 2011 02:01:57 -0800 (PST)
Received: from mail.us.es (mail.us.es [193.147.175.20]) by ietfa.amsl.com (Postfix) with ESMTP id 1AF6321F8D3F for <megaco@ietf.org>; Mon, 14 Nov 2011 01:57:07 -0800 (PST)
Received: (qmail 15569 invoked from network); 14 Nov 2011 10:57:04 +0100
Received: from unknown (HELO us.es) (192.168.2.11) by us.es with SMTP; 14 Nov 2011 10:57:04 +0100
Received: (qmail 22400 invoked by uid 507); 14 Nov 2011 09:57:03 -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/13939.   Clear:RC:1(127.0.0.1):.  Processed in 0.081975 secs); 14 Nov 2011 09:57:03 -0000
Received: from unknown (HELO antivirus1) (127.0.0.1) by us.es with SMTP; 14 Nov 2011 09:57:03 -0000
Received: from 192.168.1.13 (192.168.1.13) by antivirus1 (F-Secure/fsigk_smtp/406/antivirus1); Mon, 14 Nov 2011 10:57:03 +0100 (CET)
X-Virus-Status: clean(F-Secure/fsigk_smtp/406/antivirus1)
Received: (qmail 16031 invoked from network); 14 Nov 2011 10:57:02 +0100
Received: from trajano.us.es (193.147.162.130) by us.es with AES256-SHA encrypted SMTP; 14 Nov 2011 10:57:02 +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 pAE9v1wb023169 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NOT); Mon, 14 Nov 2011 10:57:02 +0100
Message-ID: <4EC0E5FC.7050803@trajano.us.es>
Date: Mon, 14 Nov 2011 10:57:16 +0100
From: =?windows-1252?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: <4E980EF1.4020407@trajano.us.es>	<BLU0-SMTP5B76027A65AB404533C34D8E70@phx.gbl>	<4E9C185E.1090902@trajano.us.es>	<4E9D5509.4040105@trajano.us.es> <4E9FDE1A.4050207@trajano.us.es> <4E9FE5EF.6070907@nteczone.com> <4E9FEA09.3080900@trajano.us.es> <4EA62075.3060404@nteczone.com> <4EA6A2D4.2050903@trajano.us.es> <4EAA0413.5040007@nteczone.com> <4EAA7E0C.50807@trajano.us.es> <4EADDD8C.30509@nteczone.com> <4EAE763F.3020502@trajano.us.es> <4EAF4252.60403@nteczone.com> <4EAFD9D8.9010801@trajano.us.es> <4EB08561.90208@nteczone.com> <4EB10F6F.9000201@trajano.us.es> <4EC0A7C7.9090201@nteczone.com>
In-Reply-To: <4EC0A7C7.9090201@nteczone.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [Megaco] Multiple Streams and mutiplex terminations
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, 14 Nov 2011 10:02:15 -0000

Hello Christian,
>>>> ISDNTerm/BA17/D [null context]
>>>>
>>>> ISDNTerm/BA17/D/SAPI16-TEI1 --- * --- HDLCPW1/BA17/D/SAPI16-TEI1
>>>>
>>>> ISDNTerm/BA17/D/SAPI16-TEI6 --- * --- HDLCPW2/BA17/D/SAPI16-TEI6
> [CNG] I think there is only ever one physical termination. There can 
> be empheral terminations to describe the connection topology. 
> Something like the above would be possible 

I agree.

> although you would need to work on your naming conventions to ensure 
> they are valid.

I think this naming convention is valid:

* Physical termination:     ISDNTerm/BA17/D

* Ephemeral terminations: ISDNTerm/BA17/D/SAPI16/TEI23


Do you think it has any problem?

Regards,

Javi

From Christian.Groves@nteczone.com  Mon Nov 14 14:35: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 9E6E211E81C7 for <megaco@ietfa.amsl.com>; Mon, 14 Nov 2011 14:35:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.468
X-Spam-Level: 
X-Spam-Status: No, score=-2.468 tagged_above=-999 required=5 tests=[AWL=0.131,  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 u+gwVwrFw93r for <megaco@ietfa.amsl.com>; Mon, 14 Nov 2011 14:35:50 -0800 (PST)
Received: from ipmail05.adl6.internode.on.net (ipmail05.adl6.internode.on.net [150.101.137.143]) by ietfa.amsl.com (Postfix) with ESMTP id C557911E817C for <megaco@ietf.org>; Mon, 14 Nov 2011 14:35:49 -0800 (PST)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: ApMBAC6UwU520cP+/2dsb2JhbAAMN6xfAQEBBAEBAS8BBRsbChELGAkWDwkDAgECARUwEwYCAQGIBrk3BIZqgxUEpjs
Received: from ppp118-209-195-254.lns20.mel6.internode.on.net (HELO [127.0.0.1]) ([118.209.195.254]) by ipmail05.adl6.internode.on.net with ESMTP; 15 Nov 2011 09:05:48 +1030
Message-ID: <4EC197C2.7070702@nteczone.com>
Date: Tue, 15 Nov 2011 09:35:46 +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: <4E980EF1.4020407@trajano.us.es>	<BLU0-SMTP5B76027A65AB404533C34D8E70@phx.gbl>	<4E9C185E.1090902@trajano.us.es>	<4E9D5509.4040105@trajano.us.es> <4E9FDE1A.4050207@trajano.us.es> <4E9FE5EF.6070907@nteczone.com> <4E9FEA09.3080900@trajano.us.es> <4EA62075.3060404@nteczone.com> <4EA6A2D4.2050903@trajano.us.es> <4EAA0413.5040007@nteczone.com> <4EAA7E0C.50807@trajano.us.es> <4EADDD8C.30509@nteczone.com> <4EAE763F.3020502@trajano.us.es> <4EAF4252.60403@nteczone.com> <4EAFD9D8.9010801@trajano.us.es> <4EB08561.90208@nteczone.com> <4EB10F6F.9000201@trajano.us.es> <4EC0A7C7.9090201@nteczone.com> <4EC0E5FC.7050803@trajano.us.es>
In-Reply-To: <4EC0E5FC.7050803@trajano.us.es>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Subject: Re: [Megaco] Multiple Streams and mutiplex terminations
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, 14 Nov 2011 22:35:50 -0000

Hello Javi,

I think you may need a different top level for the Physical and 
Ephemeral terminations to avoid any unwanted protocol problems..
i.e. What would happen if you do a Subtract(ISDN/Term/*)? The MG would 
try to subtract Termination in the NULL context which is not allowed.

Regards, Christian

On 14/11/2011 8:57 PM, Javi Muñoz wrote:
> Hello Christian,
>>>>> ISDNTerm/BA17/D [null context]
>>>>>
>>>>> ISDNTerm/BA17/D/SAPI16-TEI1 --- * --- HDLCPW1/BA17/D/SAPI16-TEI1
>>>>>
>>>>> ISDNTerm/BA17/D/SAPI16-TEI6 --- * --- HDLCPW2/BA17/D/SAPI16-TEI6
>> [CNG] I think there is only ever one physical termination. There can 
>> be empheral terminations to describe the connection topology. 
>> Something like the above would be possible 
>
> I agree.
>
>> although you would need to work on your naming conventions to ensure 
>> they are valid.
>
> I think this naming convention is valid:
>
> * Physical termination:     ISDNTerm/BA17/D
>
> * Ephemeral terminations: ISDNTerm/BA17/D/SAPI16/TEI23
>
>
> Do you think it has any problem?
>
> Regards,
>
> Javi
> _______________________________________________
> Megaco mailing list
> Megaco@ietf.org
> https://www.ietf.org/mailman/listinfo/megaco
>

From javi@trajano.us.es  Tue Nov 15 02:14:50 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 2C27B11E81B0 for <megaco@ietfa.amsl.com>; Tue, 15 Nov 2011 02:14:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.244
X-Spam-Level: 
X-Spam-Status: No, score=-6.244 tagged_above=-999 required=5 tests=[AWL=0.055,  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 42sbsiTkBtg1 for <megaco@ietfa.amsl.com>; Tue, 15 Nov 2011 02:14:49 -0800 (PST)
Received: from mail.us.es (mail.us.es [193.147.175.20]) by ietfa.amsl.com (Postfix) with ESMTP id 1B34211E81AE for <megaco@ietf.org>; Tue, 15 Nov 2011 02:14:48 -0800 (PST)
Received: (qmail 28897 invoked from network); 15 Nov 2011 11:14:45 +0100
Received: from unknown (HELO us.es) (192.168.2.12) by us.es with SMTP; 15 Nov 2011 11:14:45 +0100
Received: (qmail 16358 invoked by uid 507); 15 Nov 2011 10:14:40 -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/13948.   Clear:RC:1(127.0.0.1):.  Processed in 0.04869 secs); 15 Nov 2011 10:14:40 -0000
Received: from unknown (HELO antivirus2) (127.0.0.1) by us.es with SMTP; 15 Nov 2011 10:14:40 -0000
Received: from 192.168.1.13 (192.168.1.13) by antivirus2 (F-Secure/fsigk_smtp/406/antivirus2); Tue, 15 Nov 2011 11:14:40 +0100 (CET)
X-Virus-Status: clean(F-Secure/fsigk_smtp/406/antivirus2)
Received: (qmail 30285 invoked from network); 15 Nov 2011 11:14:40 +0100
Received: from trajano.us.es (193.147.162.130) by us.es with AES256-SHA encrypted SMTP; 15 Nov 2011 11:14:40 +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 pAFAEcB7011926 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NOT); Tue, 15 Nov 2011 11:14:39 +0100
Message-ID: <4EC23BA0.6000106@trajano.us.es>
Date: Tue, 15 Nov 2011 11:14:56 +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: <4E980EF1.4020407@trajano.us.es>	<BLU0-SMTP5B76027A65AB404533C34D8E70@phx.gbl>	<4E9C185E.1090902@trajano.us.es>	<4E9D5509.4040105@trajano.us.es>	<4E9FDE1A.4050207@trajano.us.es> <4E9FE5EF.6070907@nteczone.com>	<4E9FEA09.3080900@trajano.us.es> <4EA62075.3060404@nteczone.com>	<4EA6A2D4.2050903@trajano.us.es>	<4EAA0413.5040007@nteczone.com> <4EAA7E0C.50807@trajano.us.es>	<4EADDD8C.30509@nteczone.com> <4EAE763F.3020502@trajano.us.es>	<4EAF4252.60403@nteczone.com> <4EAFD9D8.9010801@trajano.us.es>	<4EB08561.90208@nteczone.com> <4EB10F6F.9000201@trajano.us.es>	<4EC0A7C7.9090201@nteczone.com> <4EC0E5FC.7050803@trajano.us.es> <4EC197C2.7070702@nteczone.com>
In-Reply-To: <4EC197C2.7070702@nteczone.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Subject: Re: [Megaco] Multiple Streams and mutiplex terminations
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, 15 Nov 2011 10:14:50 -0000

Hello Christian,
>
> I think you may need a different top level for the Physical and 
> Ephemeral terminations to avoid any unwanted protocol problems..
> i.e. What would happen if you do a Subtract(ISDN/Term/*)? The MG would 
> try to subtract Termination in the NULL context which is not allowed.

May we use  Subtract(ISDNTerm/*/D/*)  ?

Regards,

Javi

>
> Regards, Christian
>
> On 14/11/2011 8:57 PM, Javi Muñoz wrote:
>> Hello Christian,
>>>>>> ISDNTerm/BA17/D [null context]
>>>>>>
>>>>>> ISDNTerm/BA17/D/SAPI16-TEI1 --- * --- HDLCPW1/BA17/D/SAPI16-TEI1
>>>>>>
>>>>>> ISDNTerm/BA17/D/SAPI16-TEI6 --- * --- HDLCPW2/BA17/D/SAPI16-TEI6
>>> [CNG] I think there is only ever one physical termination. There can 
>>> be empheral terminations to describe the connection topology. 
>>> Something like the above would be possible 
>>
>> I agree.
>>
>>> although you would need to work on your naming conventions to ensure 
>>> they are valid.
>>
>> I think this naming convention is valid:
>>
>> * Physical termination:     ISDNTerm/BA17/D
>>
>> * Ephemeral terminations: ISDNTerm/BA17/D/SAPI16/TEI23
>>
>>
>> Do you think it has any problem?
>>
>> 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 Christian.Groves@nteczone.com  Tue Nov 15 14:16: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 6E20A11E80C3 for <megaco@ietfa.amsl.com>; Tue, 15 Nov 2011 14:16:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.332
X-Spam-Level: 
X-Spam-Status: No, score=-2.332 tagged_above=-999 required=5 tests=[AWL=-0.032, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
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 oWkqLQ78kKcv for <megaco@ietfa.amsl.com>; Tue, 15 Nov 2011 14:16:46 -0800 (PST)
Received: from ipmail07.adl2.internode.on.net (ipmail07.adl2.internode.on.net [150.101.137.131]) by ietfa.amsl.com (Postfix) with ESMTP id 13C9611E80CC for <megaco@ietf.org>; Tue, 15 Nov 2011 14:16:43 -0800 (PST)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: ApMBANfhwk520ckv/2dsb2JhbAAMNqxlAQEBBAEBAS8BBRsbCxALGAklDwIWMAYNAQUCAQGIBrhrBIoRBKZA
Received: from ppp118-209-201-47.lns20.mel6.internode.on.net (HELO [127.0.0.1]) ([118.209.201.47]) by ipmail07.adl2.internode.on.net with ESMTP; 16 Nov 2011 08:46:43 +1030
Message-ID: <4EC2E4C7.30007@nteczone.com>
Date: Wed, 16 Nov 2011 09:16:39 +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: =?ISO-8859-1?Q?Javi_Mu=F1oz?= <javi@trajano.us.es>
References: <4E980EF1.4020407@trajano.us.es>	<BLU0-SMTP5B76027A65AB404533C34D8E70@phx.gbl>	<4E9C185E.1090902@trajano.us.es>	<4E9D5509.4040105@trajano.us.es>	<4E9FDE1A.4050207@trajano.us.es> <4E9FE5EF.6070907@nteczone.com>	<4E9FEA09.3080900@trajano.us.es> <4EA62075.3060404@nteczone.com>	<4EA6A2D4.2050903@trajano.us.es>	<4EAA0413.5040007@nteczone.com> <4EAA7E0C.50807@trajano.us.es>	<4EADDD8C.30509@nteczone.com> <4EAE763F.3020502@trajano.us.es>	<4EAF4252.60403@nteczone.com> <4EAFD9D8.9010801@trajano.us.es>	<4EB08561.90208@nteczone.com> <4EB10F6F.9000201@trajano.us.es>	<4EC0A7C7.9090201@nteczone.com> <4EC0E5FC.7050803@trajano.us.es> <4EC197C2.7070702@nteczone.com> <4EC23BA0.6000106@trajano.us.es>
In-Reply-To: <4EC23BA0.6000106@trajano.us.es>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Cc: "megaco@ietf.org" <megaco@ietf.org>
Subject: Re: [Megaco] Multiple Streams and mutiplex terminations
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, 15 Nov 2011 22:16:50 -0000

Hello Javi,

H.248 allows wildcarding at different levels of a TerminationID. So you 
could use a subtract like below. However its not unambigious, would 
../D/* still match ISDNTerm/*/D? As I've mentioned previously I think 
its good practise to separate ephemeral and physical terminations at the 
highest level in the heirarchy. 3GPP do this in their naming scheme, ie. 
see TS 29.232 etc.

Regards, Christian

On 15/11/2011 9:14 PM, Javi Muñoz wrote:
> Hello Christian,
>>
>> I think you may need a different top level for the Physical and 
>> Ephemeral terminations to avoid any unwanted protocol problems..
>> i.e. What would happen if you do a Subtract(ISDN/Term/*)? The MG 
>> would try to subtract Termination in the NULL context which is not 
>> allowed.
>
> May we use  Subtract(ISDNTerm/*/D/*)  ?
>
> Regards,
>
> Javi
>
>>
>> Regards, Christian
>>
>> On 14/11/2011 8:57 PM, Javi Muñoz wrote:
>>> Hello Christian,
>>>>>>> ISDNTerm/BA17/D [null context]
>>>>>>>
>>>>>>> ISDNTerm/BA17/D/SAPI16-TEI1 --- * --- HDLCPW1/BA17/D/SAPI16-TEI1
>>>>>>>
>>>>>>> ISDNTerm/BA17/D/SAPI16-TEI6 --- * --- HDLCPW2/BA17/D/SAPI16-TEI6
>>>> [CNG] I think there is only ever one physical termination. There 
>>>> can be empheral terminations to describe the connection topology. 
>>>> Something like the above would be possible 
>>>
>>> I agree.
>>>
>>>> although you would need to work on your naming conventions to 
>>>> ensure they are valid.
>>>
>>> I think this naming convention is valid:
>>>
>>> * Physical termination:     ISDNTerm/BA17/D
>>>
>>> * Ephemeral terminations: ISDNTerm/BA17/D/SAPI16/TEI23
>>>
>>>
>>> Do you think it has any problem?
>>>
>>> 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  Tue Nov 15 15:52: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 992A121F84FC for <megaco@ietfa.amsl.com>; Tue, 15 Nov 2011 15:52:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.449
X-Spam-Level: 
X-Spam-Status: No, score=-6.449 tagged_above=-999 required=5 tests=[AWL=0.150,  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 y4VAHtQ2ySGN for <megaco@ietfa.amsl.com>; Tue, 15 Nov 2011 15:52:53 -0800 (PST)
Received: from mail.us.es (mail.us.es [193.147.175.20]) by ietfa.amsl.com (Postfix) with ESMTP id 80A6F21F84FB for <megaco@ietf.org>; Tue, 15 Nov 2011 15:52:51 -0800 (PST)
Received: (qmail 1597 invoked from network); 16 Nov 2011 00:52:50 +0100
Received: from unknown (HELO us.es) (192.168.2.12) by us.es with SMTP; 16 Nov 2011 00:52:50 +0100
Received: (qmail 28799 invoked by uid 507); 15 Nov 2011 23:52:49 -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/13951.   Clear:RC:1(127.0.0.1):.  Processed in 0.050758 secs); 15 Nov 2011 23:52:49 -0000
Received: from unknown (HELO antivirus2) (127.0.0.1) by us.es with SMTP; 15 Nov 2011 23:52:49 -0000
Received: from 192.168.1.13 (192.168.1.13) by antivirus2 (F-Secure/fsigk_smtp/406/antivirus2); Wed, 16 Nov 2011 00:52:49 +0100 (CET)
X-Virus-Status: clean(F-Secure/fsigk_smtp/406/antivirus2)
Received: (qmail 11044 invoked from network); 16 Nov 2011 00:52:49 +0100
Received: from trajano.us.es (193.147.162.130) by us.es with AES256-SHA encrypted SMTP; 16 Nov 2011 00:52: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 pAFNqi6k022979 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NOT) for <megaco@ietf.org>; Wed, 16 Nov 2011 00:52:48 +0100
Message-ID: <4EC2FB4C.30108@trajano.us.es>
Date: Wed, 16 Nov 2011 00:52:44 +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: <4E980EF1.4020407@trajano.us.es>	<BLU0-SMTP5B76027A65AB404533C34D8E70@phx.gbl>	<4E9C185E.1090902@trajano.us.es>	<4E9D5509.4040105@trajano.us.es>	<4E9FDE1A.4050207@trajano.us.es> <4E9FE5EF.6070907@nteczone.com>	<4E9FEA09.3080900@trajano.us.es> <4EA62075.3060404@nteczone.com>	<4EA6A2D4.2050903@trajano.us.es>	<4EAA0413.5040007@nteczone.com> <4EAA7E0C.50807@trajano.us.es>	<4EADDD8C.30509@nteczone.com> <4EAE763F.3020502@trajano.us.es>	<4EAF4252.60403@nteczone.com> <4EAFD9D8.9010801@trajano.us.es>	<4EB08561.90208@nteczone.com> <4EB10F6F.9000201@trajano.us.es>	<4EC0A7C7.9090201@nteczone.com> <4EC0E5FC.7050803@trajano.us.es> <4EC197C2.7070702@nteczone.com> <4EC23BA0.6000106@trajano.us.es> <4EC2E4C7.30007@nteczone.com>
In-Reply-To: <4EC2E4C7.30007@nteczone.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Subject: Re: [Megaco] Multiple Streams and mutiplex terminations
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, 15 Nov 2011 23:52:53 -0000

Hello Christian,

You're right.

I think it's better the next names:

* Physical termination:     ISDNTerm/BA17/D

* Ephemeral terminations: ISDNTerm/BA17/Eph/D/SAPI16/TEI23


Do you see any problem now?

Regards,

Javi


El 15/11/2011 23:16, Christian Groves escribió:
> Hello Javi,
>
> H.248 allows wildcarding at different levels of a TerminationID. So
> you could use a subtract like below. However its not unambigious,
> would ../D/* still match ISDNTerm/*/D? As I've mentioned previously I
> think its good practise to separate ephemeral and physical
> terminations at the highest level in the heirarchy. 3GPP do this in
> their naming scheme, ie. see TS 29.232 etc.
>
> Regards, Christian
>
> On 15/11/2011 9:14 PM, Javi Muñoz wrote:
>> Hello Christian,
>>>
>>> I think you may need a different top level for the Physical and
>>> Ephemeral terminations to avoid any unwanted protocol problems..
>>> i.e. What would happen if you do a Subtract(ISDN/Term/*)? The MG
>>> would try to subtract Termination in the NULL context which is not
>>> allowed.
>>
>> May we use  Subtract(ISDNTerm/*/D/*)  ?
>>
>> Regards,
>>
>> Javi
>>
>>>
>>> Regards, Christian
>>>
>>> On 14/11/2011 8:57 PM, Javi Muñoz wrote:
>>>> Hello Christian,
>>>>>>>> ISDNTerm/BA17/D [null context]
>>>>>>>>
>>>>>>>> ISDNTerm/BA17/D/SAPI16-TEI1 --- * --- HDLCPW1/BA17/D/SAPI16-TEI1
>>>>>>>>
>>>>>>>> ISDNTerm/BA17/D/SAPI16-TEI6 --- * --- HDLCPW2/BA17/D/SAPI16-TEI6
>>>>> [CNG] I think there is only ever one physical termination. There
>>>>> can be empheral terminations to describe the connection topology.
>>>>> Something like the above would be possible
>>>>
>>>> I agree.
>>>>
>>>>> although you would need to work on your naming conventions to
>>>>> ensure they are valid.
>>>>
>>>> I think this naming convention is valid:
>>>>
>>>> * Physical termination:     ISDNTerm/BA17/D
>>>>
>>>> * Ephemeral terminations: ISDNTerm/BA17/D/SAPI16/TEI23
>>>>
>>>>
>>>> Do you think it has any problem?
>>>>
>>>> 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  Tue Nov 15 15:59:44 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 353C611E8137 for <megaco@ietfa.amsl.com>; Tue, 15 Nov 2011 15:59:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.499
X-Spam-Level: 
X-Spam-Status: No, score=-6.499 tagged_above=-999 required=5 tests=[AWL=0.100,  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 Ky-P7tUK22xN for <megaco@ietfa.amsl.com>; Tue, 15 Nov 2011 15:59:43 -0800 (PST)
Received: from mail.us.es (mail.us.es [193.147.175.20]) by ietfa.amsl.com (Postfix) with ESMTP id 48A5311E8119 for <megaco@ietf.org>; Tue, 15 Nov 2011 15:59:39 -0800 (PST)
Received: (qmail 4146 invoked from network); 16 Nov 2011 00:59:37 +0100
Received: from unknown (HELO us.es) (192.168.2.11) by us.es with SMTP; 16 Nov 2011 00:59:37 +0100
Received: (qmail 6573 invoked by uid 507); 15 Nov 2011 23:59:35 -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/13951.   Clear:RC:1(127.0.0.1):.  Processed in 0.043652 secs); 15 Nov 2011 23:59:35 -0000
Received: from unknown (HELO antivirus1) (127.0.0.1) by us.es with SMTP; 15 Nov 2011 23:59:35 -0000
Received: from 192.168.1.13 (192.168.1.13) by antivirus1 (F-Secure/fsigk_smtp/406/antivirus1); Wed, 16 Nov 2011 00:59:35 +0100 (CET)
X-Virus-Status: clean(F-Secure/fsigk_smtp/406/antivirus1)
Received: (qmail 15017 invoked from network); 16 Nov 2011 00:59:35 +0100
Received: from trajano.us.es (193.147.162.130) by us.es with AES256-SHA encrypted SMTP; 16 Nov 2011 00:59:35 +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 pAFNxYAC023028 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NOT); Wed, 16 Nov 2011 00:59:35 +0100
Message-ID: <4EC2FCE6.6080106@trajano.us.es>
Date: Wed, 16 Nov 2011 00:59:34 +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: <4E980EF1.4020407@trajano.us.es>	<BLU0-SMTP5B76027A65AB404533C34D8E70@phx.gbl>	<4E9C185E.1090902@trajano.us.es>	<4E9D5509.4040105@trajano.us.es>	<4E9FDE1A.4050207@trajano.us.es> <4E9FE5EF.6070907@nteczone.com>	<4E9FEA09.3080900@trajano.us.es> <4EA62075.3060404@nteczone.com>	<4EA6A2D4.2050903@trajano.us.es>	<4EAA0413.5040007@nteczone.com> <4EAA7E0C.50807@trajano.us.es>	<4EADDD8C.30509@nteczone.com> <4EAE763F.3020502@trajano.us.es>	<4EAF4252.60403@nteczone.com> <4EAFD9D8.9010801@trajano.us.es>	<4EB08561.90208@nteczone.com> <4EB10F6F.9000201@trajano.us.es>	<4EC0A7C7.9090201@nteczone.com> <4EC0E5FC.7050803@trajano.us.es> <4EC197C2.7070702@nteczone.com> <4EC23BA0.6000106@trajano.us.es> <4EC2E4C7.30007@nteczone.com>
In-Reply-To: <4EC2E4C7.30007@nteczone.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Subject: Re: [Megaco] Multiple Streams and mutiplex terminations
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, 15 Nov 2011 23:59:44 -0000

Or would it be better?

* Physical termination:   ISDNTerm/BA17/D

* Ephemeral terminations: Eph/ISDNTerm/BA17/D/SAPI16/TEI23


Regards,

Javi


El 15/11/2011 23:16, Christian Groves escribió:
> Hello Javi,
>
> H.248 allows wildcarding at different levels of a TerminationID. So
> you could use a subtract like below. However its not unambigious,
> would ../D/* still match ISDNTerm/*/D? As I've mentioned previously I
> think its good practise to separate ephemeral and physical
> terminations at the highest level in the heirarchy. 3GPP do this in
> their naming scheme, ie. see TS 29.232 etc.
>
> Regards, Christian
>
> On 15/11/2011 9:14 PM, Javi Muñoz wrote:
>> Hello Christian,
>>>
>>> I think you may need a different top level for the Physical and
>>> Ephemeral terminations to avoid any unwanted protocol problems..
>>> i.e. What would happen if you do a Subtract(ISDN/Term/*)? The MG
>>> would try to subtract Termination in the NULL context which is not
>>> allowed.
>>
>> May we use  Subtract(ISDNTerm/*/D/*)  ?
>>
>> Regards,
>>
>> Javi
>>
>>>
>>> Regards, Christian
>>>
>>> On 14/11/2011 8:57 PM, Javi Muñoz wrote:
>>>> Hello Christian,
>>>>>>>> ISDNTerm/BA17/D [null context]
>>>>>>>>
>>>>>>>> ISDNTerm/BA17/D/SAPI16-TEI1 --- * --- HDLCPW1/BA17/D/SAPI16-TEI1
>>>>>>>>
>>>>>>>> ISDNTerm/BA17/D/SAPI16-TEI6 --- * --- HDLCPW2/BA17/D/SAPI16-TEI6
>>>>> [CNG] I think there is only ever one physical termination. There
>>>>> can be empheral terminations to describe the connection topology.
>>>>> Something like the above would be possible
>>>>
>>>> I agree.
>>>>
>>>>> although you would need to work on your naming conventions to
>>>>> ensure they are valid.
>>>>
>>>> I think this naming convention is valid:
>>>>
>>>> * Physical termination:     ISDNTerm/BA17/D
>>>>
>>>> * Ephemeral terminations: ISDNTerm/BA17/D/SAPI16/TEI23
>>>>
>>>>
>>>> Do you think it has any problem?
>>>>
>>>> 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  Fri Nov 18 02:28:23 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 0EF4921F8A56 for <megaco@ietfa.amsl.com>; Fri, 18 Nov 2011 02:28:23 -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=[AWL=0.050,  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 A7AV01RYRj1W for <megaco@ietfa.amsl.com>; Fri, 18 Nov 2011 02:28:22 -0800 (PST)
Received: from mail.us.es (mail.us.es [193.147.175.20]) by ietfa.amsl.com (Postfix) with ESMTP id E539D21F8A35 for <megaco@ietf.org>; Fri, 18 Nov 2011 02:28:21 -0800 (PST)
Received: (qmail 15367 invoked from network); 18 Nov 2011 11:28:20 +0100
Received: from unknown (HELO us.es) (192.168.2.12) by us.es with SMTP; 18 Nov 2011 11:28:20 +0100
Received: (qmail 25407 invoked by uid 507); 18 Nov 2011 10:28:16 -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/13962.   Clear:RC:1(127.0.0.1):.  Processed in 0.042163 secs); 18 Nov 2011 10:28:16 -0000
Received: from unknown (HELO antivirus2) (127.0.0.1) by us.es with SMTP; 18 Nov 2011 10:28:16 -0000
Received: from 192.168.1.13 (192.168.1.13) by antivirus2 (F-Secure/fsigk_smtp/406/antivirus2); Fri, 18 Nov 2011 11:28:16 +0100 (CET)
X-Virus-Status: clean(F-Secure/fsigk_smtp/406/antivirus2)
Received: (qmail 21671 invoked from network); 18 Nov 2011 11:28:16 +0100
Received: from trajano.us.es (193.147.162.130) by us.es with AES256-SHA encrypted SMTP; 18 Nov 2011 11:28:16 +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 pAIASFgk004712 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NOT); Fri, 18 Nov 2011 11:28:15 +0100
Message-ID: <4EC6335E.30705@trajano.us.es>
Date: Fri, 18 Nov 2011 11:28: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>
References: <4E980EF1.4020407@trajano.us.es>	<BLU0-SMTP5B76027A65AB404533C34D8E70@phx.gbl>	<4E9C185E.1090902@trajano.us.es>	<4E9D5509.4040105@trajano.us.es>	<4E9FDE1A.4050207@trajano.us.es> <4E9FE5EF.6070907@nteczone.com>	<4E9FEA09.3080900@trajano.us.es> <4EA62075.3060404@nteczone.com>	<4EA6A2D4.2050903@trajano.us.es>	<4EAA0413.5040007@nteczone.com> <4EAA7E0C.50807@trajano.us.es>	<4EADDD8C.30509@nteczone.com> <4EAE763F.3020502@trajano.us.es>	<4EAF4252.60403@nteczone.com> <4EAFD9D8.9010801@trajano.us.es>	<4EB08561.90208@nteczone.com> <4EB10F6F.9000201@trajano.us.es>	<4EC0A7C7.9090201@nteczone.com> <4EC0E5FC.7050803@trajano.us.es> <4EC197C2.7070702@nteczone.com> <4EC23BA0.6000106@trajano.us.es> <4EC2E4C7.30007@nteczone.com> <4EC2FB31.4080307@trajano.us.es> <4EC30A7F.7060305@nteczone.com>
In-Reply-To: <4EC30A7F.7060305@nteczone.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Subject: Re: [Megaco] Multiple Streams and mutiplex terminations
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, 18 Nov 2011 10:28:23 -0000

Heloo Christian,

I agree, I'll use that name.

Thank you very much for everything.

Regards,

Javi


El 16/11/2011 1:57, Christian Groves escribió:
> Hello Javi,
>
> I was suggesting some more like: EphISDNTerm/BA17/D/SAPI16/TEI23 for 
> the ephemeral terminations. That way if you want to clear all 
> ephemeral termination you can simply issue: Subtract(EphISDNTerm/*). 
> Otherwise you'll end up with a very convoluted way to do this as you'd 
> have to do multiple groups.
>
> Regards, Christian
>
> On 16/11/2011 10:52 AM, Javi wrote:
>> Hello Christian,
>>
>> You're right.
>>
>> I think it's better the next names:
>>
>> * Physical termination:     ISDNTerm/BA17/D
>>
>> * Ephemeral terminations: ISDNTerm/BA17/Eph/D/SAPI16/TEI23
>>
>>
>> Do you see any problem now?
>>
>> Regards,
>>
>> Javi
>>
>>
>> El 15/11/2011 23:16, Christian Groves escribió:
>>> Hello Javi,
>>>
>>> H.248 allows wildcarding at different levels of a TerminationID. So 
>>> you could use a subtract like below. However its not unambigious, 
>>> would ../D/* still match ISDNTerm/*/D? As I've mentioned previously 
>>> I think its good practise to separate ephemeral and physical 
>>> terminations at the highest level in the heirarchy. 3GPP do this in 
>>> their naming scheme, ie. see TS 29.232 etc.
>>>
>>> Regards, Christian
>>>
>>> On 15/11/2011 9:14 PM, Javi Muñoz wrote:
>>>> Hello Christian,
>>>>>
>>>>> I think you may need a different top level for the Physical and 
>>>>> Ephemeral terminations to avoid any unwanted protocol problems..
>>>>> i.e. What would happen if you do a Subtract(ISDN/Term/*)? The MG 
>>>>> would try to subtract Termination in the NULL context which is not 
>>>>> allowed.
>>>>
>>>> May we use  Subtract(ISDNTerm/*/D/*)  ?
>>>>
>>>> Regards,
>>>>
>>>> Javi
>>>>
>>>>>
>>>>> Regards, Christian
>>>>>
>>>>> On 14/11/2011 8:57 PM, Javi Muñoz wrote:
>>>>>> Hello Christian,
>>>>>>>>>> ISDNTerm/BA17/D [null context]
>>>>>>>>>>
>>>>>>>>>> ISDNTerm/BA17/D/SAPI16-TEI1 --- * --- HDLCPW1/BA17/D/SAPI16-TEI1
>>>>>>>>>>
>>>>>>>>>> ISDNTerm/BA17/D/SAPI16-TEI6 --- * --- HDLCPW2/BA17/D/SAPI16-TEI6
>>>>>>> [CNG] I think there is only ever one physical termination. There 
>>>>>>> can be empheral terminations to describe the connection 
>>>>>>> topology. Something like the above would be possible 
>>>>>>
>>>>>> I agree.
>>>>>>
>>>>>>> although you would need to work on your naming conventions to 
>>>>>>> ensure they are valid.
>>>>>>
>>>>>> I think this naming convention is valid:
>>>>>>
>>>>>> * Physical termination:     ISDNTerm/BA17/D
>>>>>>
>>>>>> * Ephemeral terminations: ISDNTerm/BA17/D/SAPI16/TEI23
>>>>>>
>>>>>>
>>>>>> Do you think it has any problem?
>>>>>>
>>>>>> 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  Tue Nov 29 03:32:24 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 33FF921F8B3A; Tue, 29 Nov 2011 03:32:24 -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 0cuhG3Wr0M6y; Tue, 29 Nov 2011 03:32:23 -0800 (PST)
Received: from smail2.alcatel.fr (smail2.alcatel.fr [64.208.49.57]) by ietfa.amsl.com (Postfix) with ESMTP id 4AC1E21F8B30; Tue, 29 Nov 2011 03:32:22 -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 pATBWIte002676 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Tue, 29 Nov 2011 12:32:21 +0100
Received: from FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com ([135.120.45.52]) by FRMRSSXCHHUB02.dc-m.alcatel-lucent.com ([135.120.45.62]) with mapi; Tue, 29 Nov 2011 12:31:56 +0100
From: "Schwarz, Albrecht (Albrecht)" <albrecht.schwarz@alcatel-lucent.com>
To: "avt@ietf.org" <avt@ietf.org>
Date: Tue, 29 Nov 2011 12:32:46 +0100
Thread-Topic: Types of monitoring architectures; RE: [AVTCORE] I-D Action: draft-ietf-avtcore-monarch-08.txt
Thread-Index: AcyubGYHPa88O0vWQYK5qbTx0sZ/ngAF1k3A
Message-ID: <5F7BCCF5541B7444830A2288ABBEBC96216190051A@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com>
References: <20111129075613.12419.4377.idtracker@ietfa.amsl.com>
In-Reply-To: <20111129075613.12419.4377.idtracker@ietfa.amsl.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: [Megaco] Types of monitoring architectures; RE: [AVTCORE] 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, 29 Nov 2011 11:32:24 -0000

Dear All,

there are different types of monitoring architectures, particularily from p=
erspective of QoE related performance parameters.=20
Let's recall QoE (e.g., ITU-T P.10 Amendment 2):

Quality of Experience (QoE):=20
	The overall acceptability of an application or service, as perceived subje=
ctively by the end-user. =20
	NOTE 1 - Quality of experience includes the complete end-to-end system eff=
ects (client, terminal, network, services infrastructure, etc.).=20
	NOTE 2 - Overall acceptability may be influenced by user expectations and =
context.=20
=20
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" entit=
ies are equal to a terminal/user equipment (UE). This would be an end-to-en=
d IP network scenario.

However, the "RTP Sender" and "RTP Receiver" entities may be also located a=
t the edge of an IP network, e.g. in a gateway for IP-to-non-IP interworkin=
g, i.e. an UE located in the non-IP network part.=20
Note: such scenarios are considered by MEGACO gateways (I've Cc'd megaco li=
st).

An RTP Sender/Receiver located NOT in the UE would question the value of RT=
P/RTCP QoE related performance measurements (because the UE is located outs=
ide the RTP domain).=20

Conclusions:
- the set of meaningful performance metrics may be dependent on the locatio=
n 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 meanin=
gful 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 Q=
oE 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?

Regards,
Albrecht

=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 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=20
> of all those
>    parameters of concern to a specific application.  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 example, for all
>    of voice, streaming audio and video.
>=20
>=20
> A URL for this Internet-Draft is:
> 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:
> 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
> =

From javi@trajano.us.es  Tue Nov 29 09:39: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 82EAF21F8B73 for <megaco@ietfa.amsl.com>; Tue, 29 Nov 2011 09:39:53 -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 I0KlpZVHj2LJ for <megaco@ietfa.amsl.com>; Tue, 29 Nov 2011 09:39:53 -0800 (PST)
Received: from mail.us.es (mail.us.es [193.147.175.20]) by ietfa.amsl.com (Postfix) with ESMTP id 8094C21F8B27 for <megaco@ietf.org>; Tue, 29 Nov 2011 09:39:52 -0800 (PST)
Received: (qmail 14665 invoked from network); 29 Nov 2011 18:39:49 +0100
Received: from unknown (HELO us.es) (192.168.2.12) by us.es with SMTP; 29 Nov 2011 18:39:49 +0100
Received: (qmail 24401 invoked by uid 507); 29 Nov 2011 17:39:47 -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/14025.   Clear:RC:1(127.0.0.1):.  Processed in 0.030193 secs); 29 Nov 2011 17:39:47 -0000
Received: from unknown (HELO antivirus2) (127.0.0.1) by us.es with SMTP; 29 Nov 2011 17:39:47 -0000
Received: from 192.168.1.13 (192.168.1.13) by antivirus2 (F-Secure/fsigk_smtp/406/antivirus2); Tue, 29 Nov 2011 18:39:47 +0100 (CET)
X-Virus-Status: clean(F-Secure/fsigk_smtp/406/antivirus2)
Received: (qmail 20676 invoked from network); 29 Nov 2011 18:39:47 +0100
Received: from trajano.us.es (193.147.162.130) by us.es with AES256-SHA encrypted SMTP; 29 Nov 2011 18:39:47 +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 pATHdlrp010585 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NOT); Tue, 29 Nov 2011 18:39:47 +0100
Message-ID: <4ED518F6.4020201@trajano.us.es>
Date: Tue, 29 Nov 2011 18:40:06 +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] 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: Tue, 29 Nov 2011 17:39:53 -0000

For the ISDN UDI-TA capability, [ETSI TS 183 036] proposes to describe 
the media at MG using the next SDP description in the Local/Remote 
descriptors:

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


MG must use the codec:

* CLEARMODE: in the phase of the call of information transfer.

* Audio Code G.711-u/A: in the phase of the call of establishment/release.


The phase of the call is known by the MGC (using signalling Q.931, not 
visible to the MG). But, with that SDP description, how may MGC indicate 
to the MG which codec may use at each instant?

Regards,

Javi

From albrecht.schwarz@alcatel-lucent.com  Tue Nov 29 23:33:24 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 896B311E8089 for <megaco@ietfa.amsl.com>; Tue, 29 Nov 2011 23:33:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.499
X-Spam-Level: 
X-Spam-Status: No, score=-5.499 tagged_above=-999 required=5 tests=[AWL=-0.750, BAYES_00=-2.599, HELO_EQ_FR=0.35, J_CHICKENPOX_15=0.6, 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 KAwHvF5+RHNQ for <megaco@ietfa.amsl.com>; Tue, 29 Nov 2011 23:33:23 -0800 (PST)
Received: from smail3.alcatel.fr (smail3.alcatel.fr [64.208.49.56]) by ietfa.amsl.com (Postfix) with ESMTP id 4B35E11E8073 for <megaco@ietf.org>; Tue, 29 Nov 2011 23:33:22 -0800 (PST)
Received: from FRMRSSXCHHUB03.dc-m.alcatel-lucent.com (FRMRSSXCHHUB03.dc-m.alcatel-lucent.com [135.120.45.63]) by smail3.alcatel.fr (8.14.3/8.14.3/ICT) with ESMTP id pAU7X4OW026357 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Wed, 30 Nov 2011 08:33:21 +0100
Received: from FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com ([135.120.45.52]) by FRMRSSXCHHUB03.dc-m.alcatel-lucent.com ([135.120.45.63]) with mapi; Wed, 30 Nov 2011 08:33:11 +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: Wed, 30 Nov 2011 08:34:03 +0100
Thread-Topic: [Megaco] Selection of media (m=) at MG
Thread-Index: AcyuvfFv7plefsOhRAmXxWGX/DXw+QAclfXg
Message-ID: <5F7BCCF5541B7444830A2288ABBEBC962161900622@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com>
References: <4ED518F6.4020201@trajano.us.es>
In-Reply-To: <4ED518F6.4020201@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: 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: Wed, 30 Nov 2011 07:33:24 -0000

I'm not familiar with the ISDN/SIP interwork spec [ETSI TS 183 036], but I =
guess that this could be the emulation of ISDN bearer service "UDI with sup=
port of tones/announcements" [ITU-T I.231.x].
The (optional?) capability of tones/announcements is just required during t=
he call establishment phase, - before the communication phase.

1st Dependency on MG type
	a) TGW: no impact, because tone/announcement inserted by ISDN local exchan=
ge (terminating Q.931); TGW needs just clearmode support
	b) RGW/AGW [ETSI 183 002]: ... call-dependent procedures for specifying th=
e details of the emulation service


2nd H.248 RGW/AGW profile [ETSI 183 002]
You don't find correspondent call dependent procedures, also due to histori=
cal reasons because this was the very first profile defined before the "ITU=
-T H.248 profile template" was developed.
On the other side, it could be transparent for the MG as you said.

E.g., MGC
-> call establishment phase: IF tones/announcements THEN H.248 Command.req =
for tone/announcement control plus media configuration with voice codec
-> after: H.248 Command.req for modification of the media configuration tow=
ards CLEARMODE

Thus, two media configurations in time series.

Regards
Albrecht

PS
My experience: the condition "IF tones/announcements" AND "ISDN bearer serv=
ice UDI" seems to be very, very rare, thus just starting UDI bearer service=
 emulation in CLEARMODE ...

=20

> -----Original Message-----
> From: megaco-bounces@ietf.org=20
> [mailto:megaco-bounces@ietf.org] On Behalf Of Javi Mu=F1oz
> Sent: Dienstag, 29. November 2011 18:40
> To: megaco@ietf.org
> Subject: [Megaco] Selection of media (m=3D) at MG
>=20
> For the ISDN UDI-TA capability, [ETSI TS 183 036] proposes to=20
> describe the media at MG using the next SDP description in=20
> the Local/Remote
> descriptors:
>=20
> m=3Daudio <puerto> RTP/AVP <Dynamic_PT> 0 [8]=20
> a=3Drtpmap:<Dynamic_PT> CLEARMODE/8000
>=20
>=20
> MG must use the codec:
>=20
> * CLEARMODE: in the phase of the call of information transfer.
>=20
> * Audio Code G.711-u/A: in the phase of the call of=20
> establishment/release.
>=20
>=20
> The phase of the call is known by the MGC (using signalling=20
> Q.931, not visible to the MG). But, with that SDP=20
> description, how may MGC indicate to the MG which codec may=20
> use at each instant?
>=20
> Regards,
>=20
> Javi
> _______________________________________________
> Megaco mailing list
> Megaco@ietf.org
> https://www.ietf.org/mailman/listinfo/megaco
> =

From javi@trajano.us.es  Wed Nov 30 02:25: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 CF78721F8B01 for <megaco@ietfa.amsl.com>; Wed, 30 Nov 2011 02:25:18 -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, 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 zSIcXUsAjVY2 for <megaco@ietfa.amsl.com>; Wed, 30 Nov 2011 02:25:18 -0800 (PST)
Received: from mail.us.es (mail.us.es [193.147.175.20]) by ietfa.amsl.com (Postfix) with ESMTP id AC85621F8B14 for <megaco@ietf.org>; Wed, 30 Nov 2011 02:25:17 -0800 (PST)
Received: (qmail 10000 invoked from network); 30 Nov 2011 11:25:15 +0100
Received: from unknown (HELO us.es) (192.168.2.12) by us.es with SMTP; 30 Nov 2011 11:25:15 +0100
Received: (qmail 6827 invoked by uid 507); 30 Nov 2011 10:25:15 -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/14041.   Clear:RC:1(127.0.0.1):.  Processed in 0.037507 secs); 30 Nov 2011 10:25:15 -0000
Received: from unknown (HELO antivirus2) (127.0.0.1) by us.es with SMTP; 30 Nov 2011 10:25:14 -0000
Received: from 192.168.1.13 (192.168.1.13) by antivirus2 (F-Secure/fsigk_smtp/406/antivirus2); Wed, 30 Nov 2011 11:25:14 +0100 (CET)
X-Virus-Status: clean(F-Secure/fsigk_smtp/406/antivirus2)
Received: (qmail 5641 invoked from network); 30 Nov 2011 11:25:14 +0100
Received: from trajano.us.es (193.147.162.130) by us.es with AES256-SHA encrypted SMTP; 30 Nov 2011 11:25: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 pAUAPE6T022140 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NOT); Wed, 30 Nov 2011 11:25:14 +0100
Message-ID: <4ED604A0.2000402@trajano.us.es>
Date: Wed, 30 Nov 2011 11:25:36 +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>
In-Reply-To: <5F7BCCF5541B7444830A2288ABBEBC962161900622@FRMRSSXCHMBSD2.dc-m.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: Wed, 30 Nov 2011 10:25:18 -0000

Hello Albrecht,

I agree in general.

However, I have a doubt about ISDN/SIP interwork spec [ETSI TS 183 036]. 
This spec. proposes that in the Q.931/SIP interworking, some EIs Q.931 
are codec to SDP and/or inserted in the SIP body as a PSTN XML element.

Under what criteria, an Q.931 EI should be?:

(a) Codec to SDP

AND / OR  (this is also important)

(b) Inserted in the SIP body as a PSTN XML element

or

(c) None (only interpreted by the AGW, without being carried over SIP)

Regards,

Javi



El 30/11/2011 8:34, Schwarz, Albrecht (Albrecht) escribió:
> I'm not familiar with the ISDN/SIP interwork spec [ETSI TS 183 036], but I guess that this could be the emulation of ISDN bearer service "UDI with support of tones/announcements" [ITU-T I.231.x].
> The (optional?) capability of tones/announcements is just required during the call establishment phase, - before the communication phase.
>
> 1st Dependency on MG type
> 	a) TGW: no impact, because tone/announcement inserted by ISDN local exchange (terminating Q.931); TGW needs just clearmode support
> 	b) RGW/AGW [ETSI 183 002]: ... call-dependent procedures for specifying the details of the emulation service
>
>
> 2nd H.248 RGW/AGW profile [ETSI 183 002]
> You don't find correspondent call dependent procedures, also due to historical reasons because this was the very first profile defined before the "ITU-T H.248 profile template" was developed.
> On the other side, it could be transparent for the MG as you said.
>
> E.g., MGC
> ->  call establishment phase: IF tones/announcements THEN H.248 Command.req for tone/announcement control plus media configuration with voice codec
> ->  after: H.248 Command.req for modification of the media configuration towards CLEARMODE
>
> Thus, two media configurations in time series.
>
> Regards
> Albrecht
>
> PS
> My experience: the condition "IF tones/announcements" AND "ISDN bearer service UDI" seems to be very, very rare, thus just starting UDI bearer service emulation in CLEARMODE ...
>
>
>
>> -----Original Message-----
>> From: megaco-bounces@ietf.org
>> [mailto:megaco-bounces@ietf.org] On Behalf Of Javi Muñoz
>> Sent: Dienstag, 29. November 2011 18:40
>> To: megaco@ietf.org
>> Subject: [Megaco] Selection of media (m=) at MG
>>
>> For the ISDN UDI-TA capability, [ETSI TS 183 036] proposes to
>> describe the media at MG using the next SDP description in
>> the Local/Remote
>> descriptors:
>>
>> m=audio<puerto>  RTP/AVP<Dynamic_PT>  0 [8]
>> a=rtpmap:<Dynamic_PT>  CLEARMODE/8000
>>
>>
>> MG must use the codec:
>>
>> * CLEARMODE: in the phase of the call of information transfer.
>>
>> * Audio Code G.711-u/A: in the phase of the call of
>> establishment/release.
>>
>>
>> The phase of the call is known by the MGC (using signalling
>> Q.931, not visible to the MG). But, with that SDP
>> description, how may MGC indicate to the MG which codec may
>> use at each instant?
>>
>> Regards,
>>
>> Javi
>> _______________________________________________
>> Megaco mailing list
>> Megaco@ietf.org
>> https://www.ietf.org/mailman/listinfo/megaco
>>


From bill.wu@huawei.com  Tue Nov 29 19:51:50 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 D783B21F86A5; Tue, 29 Nov 2011 19:51:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.182
X-Spam-Level: 
X-Spam-Status: No, score=-6.182 tagged_above=-999 required=5 tests=[AWL=0.417,  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 PpVfRKvVj791; Tue, 29 Nov 2011 19:51:49 -0800 (PST)
Received: from szxga03-in.huawei.com (szxga03-in.huawei.com [119.145.14.66]) by ietfa.amsl.com (Postfix) with ESMTP id B0EFC21F86A4; Tue, 29 Nov 2011 19:51:48 -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 <0LVG003AHG0VSB@szxga03-in.huawei.com>; Wed, 30 Nov 2011 11:50:55 +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 <0LVG0017WG0UHZ@szxga03-in.huawei.com>; Wed, 30 Nov 2011 11:50:54 +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 AFI56187; Wed, 30 Nov 2011 11:50:54 +0800
Received: from SZXEML401-HUB.china.huawei.com (10.82.67.31) by szxeml203-edg.china.huawei.com (172.24.2.55) with Microsoft SMTP Server (TLS) id 14.1.323.3; Wed, 30 Nov 2011 11:50:48 +0800
Received: from w53375q (10.138.41.130) by szxeml401-hub.china.huawei.com (10.82.67.31) with Microsoft SMTP Server (TLS) id 14.1.323.3; Wed, 30 Nov 2011 11:50:42 +0800
Date: Wed, 30 Nov 2011 11:50:41 +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: <EAC481B4D8034C38AC54E1217F8D875D@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>
X-Mailman-Approved-At: Wed, 30 Nov 2011 08:29:26 -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: Wed, 30 Nov 2011 03:51:50 -0000

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.

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.
 
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.

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

> 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  Wed Nov 30 09:12:23 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 5A07C21F8BC3 for <megaco@ietfa.amsl.com>; Wed, 30 Nov 2011 09:12:23 -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 pJ2ymuNQPGmS for <megaco@ietfa.amsl.com>; Wed, 30 Nov 2011 09:12:22 -0800 (PST)
Received: from mail.us.es (mail.us.es [193.147.175.20]) by ietfa.amsl.com (Postfix) with ESMTP id 3BA0C21F8BBD for <megaco@ietf.org>; Wed, 30 Nov 2011 09:12:22 -0800 (PST)
Received: (qmail 9210 invoked from network); 30 Nov 2011 18:12:20 +0100
Received: from unknown (HELO us.es) (192.168.2.13) by us.es with SMTP; 30 Nov 2011 18:12:20 +0100
Received: (qmail 15603 invoked by uid 507); 30 Nov 2011 17:12:19 -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/14041.   Clear:RC:1(127.0.0.1):.  Processed in 0.037919 secs); 30 Nov 2011 17:12:19 -0000
Received: from unknown (HELO antivirus3) (127.0.0.1) by us.es with SMTP; 30 Nov 2011 17:12:19 -0000
Received: from 192.168.1.13 (192.168.1.13) by antivirus3 (F-Secure/fsigk_smtp/406/antivirus3); Wed, 30 Nov 2011 18:12:19 +0100 (CET)
X-Virus-Status: clean(F-Secure/fsigk_smtp/406/antivirus3)
Received: (qmail 32031 invoked from network); 30 Nov 2011 18:12:18 +0100
Received: from trajano.us.es (193.147.162.130) by us.es with AES256-SHA encrypted SMTP; 30 Nov 2011 18:12:18 +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 pAUHCIZ6029035 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NOT); Wed, 30 Nov 2011 18:12:18 +0100
Message-ID: <4ED6640A.9030508@trajano.us.es>
Date: Wed, 30 Nov 2011 18:12:42 +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
References: <4ED518F6.4020201@trajano.us.es>	<5F7BCCF5541B7444830A2288ABBEBC962161900622@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com> <4ED604A0.2000402@trajano.us.es>
In-Reply-To: <4ED604A0.2000402@trajano.us.es>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
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: Wed, 30 Nov 2011 17:12:23 -0000

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 albrecht.schwarz@alcatel-lucent.com  Wed Nov 30 09:23: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 3268921F8C0F; Wed, 30 Nov 2011 09:23:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.874
X-Spam-Level: 
X-Spam-Status: No, score=-5.874 tagged_above=-999 required=5 tests=[AWL=0.375,  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 QsLxkmovJtox; Wed, 30 Nov 2011 09:23:34 -0800 (PST)
Received: from smail2.alcatel.fr (smail2.alcatel.fr [64.208.49.57]) by ietfa.amsl.com (Postfix) with ESMTP id F189A21F8C06; Wed, 30 Nov 2011 09:23:33 -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 pAUHNPi4007339 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Wed, 30 Nov 2011 18:23:25 +0100
Received: from FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com ([135.120.45.52]) by FRMRSSXCHHUB02.dc-m.alcatel-lucent.com ([135.120.45.62]) with mapi; Wed, 30 Nov 2011 18:23: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, 30 Nov 2011 18:24:16 +0100
Thread-Topic: [AVTCORE] Types of monitoring architectures; RE:  I-D Action: draft-ietf-avtcore-monarch-08.txt
Thread-Index: AcyvE2HylSLOa+J4RfiROAbrd6oriAAbsNGQ
Message-ID: <5F7BCCF5541B7444830A2288ABBEBC96216190077F@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>
In-Reply-To: <EAC481B4D8034C38AC54E1217F8D875D@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, 30 Nov 2011 17:23:35 -0000

My replies below inline,
Albrecht=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 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.

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

>=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.

[ABS] I would disagree. At least your statement should be conditional, sth =
like=20
"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), beca=
use QoE performance metrics are tightly coupled to the point of view of a '=
user'.
... IF NOT, then ..."

> =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.

[ABS] I don't got any problems to talk about architectural framework for mo=
nitoring in this document. Such information is required and this is the onl=
y 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 entiti=
es (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 (li=
ke 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


>=20
> But as the author of this document, I am interested and open=20
> 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 cap=
abilities (here: measurement services, reporting services on top of basic R=
TP services).
Such an overlay concept is nothing new: e.g., the MultiService Forum did de=
fine a "Performance Measurement & Monitoring (PMM)" overlay network, or IET=
F RMON may be also considered as such.

>=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
> 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 albrecht.schwarz@alcatel-lucent.com  Wed Nov 30 09:27:00 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 5AB8621F8B07 for <megaco@ietfa.amsl.com>; Wed, 30 Nov 2011 09:27:00 -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 daW7TtUnZvtG for <megaco@ietfa.amsl.com>; Wed, 30 Nov 2011 09:27:00 -0800 (PST)
Received: from smail3.alcatel.fr (smail3.alcatel.fr [64.208.49.56]) by ietfa.amsl.com (Postfix) with ESMTP id A752321F8AB9 for <megaco@ietf.org>; Wed, 30 Nov 2011 09:26:59 -0800 (PST)
Received: from FRMRSSXCHHUB04.dc-m.alcatel-lucent.com (FRMRSSXCHHUB04.dc-m.alcatel-lucent.com [135.120.45.64]) by smail3.alcatel.fr (8.14.3/8.14.3/ICT) with ESMTP id pAUHQsEp023024 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Wed, 30 Nov 2011 18:26:56 +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; Wed, 30 Nov 2011 18:26:53 +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: Wed, 30 Nov 2011 18:27:45 +0100
Thread-Topic: [Megaco] Selection of media (m=) at MG
Thread-Index: Acyvgz+LYFaJhxQsQ7m+2TUOiDUKdAAAcPWw
Message-ID: <5F7BCCF5541B7444830A2288ABBEBC962161900780@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>
In-Reply-To: <4ED6640A.9030508@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: 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: Wed, 30 Nov 2011 17:27:00 -0000

well spotted, thus just a single media configuration ('Clearmode') would be=
 already sufficient to emulate that ISDN bearer service

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.=20

> -----Original Message-----
> From: Javi Mu=F1oz [mailto:javi@trajano.us.es]=20
> 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
>=20
> A second comment,
>=20
> If:
> >>     a) TGW: no impact, because tone/announcement inserted by ISDN=20
> >> local exchange (terminating Q.931); TGW needs just=20
> clearmode support
>=20
> (I agree)
>=20
> then, why?
> >> E.g., MGC
> >> ->  call establishment phase: IF tones/announcements THEN H.248
> >> Command.req for tone/announcement control plus media configuration=20
> >> with voice codec
>=20
> That "media configuration with voice codec" (G.711) would be=20
> done at the MeGaCo termination of the IP side of the MG, not=20
> at the termination of the ISDN side. If tone/announcement is=20
> inserted (in the UNI ISDN) by this MG, the termination of the=20
> IP side of the MG would not be used, so that "voice codec"=20
> would not be relevant (no media would be transported over the=20
> IP network).
>=20
> am I wrong?
>=20
> Regards,
>=20
> Javi
> =

From javi@trajano.us.es  Wed Nov 30 09:44:21 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 AA3C821F8B94 for <megaco@ietfa.amsl.com>; Wed, 30 Nov 2011 09:44:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.799
X-Spam-Level: 
X-Spam-Status: No, score=-5.799 tagged_above=-999 required=5 tests=[AWL=-0.100, 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 JTErv-h917BW for <megaco@ietfa.amsl.com>; Wed, 30 Nov 2011 09:44:21 -0800 (PST)
Received: from mail.us.es (mail.us.es [193.147.175.20]) by ietfa.amsl.com (Postfix) with ESMTP id 98B7C21F8B92 for <megaco@ietf.org>; Wed, 30 Nov 2011 09:44:20 -0800 (PST)
Received: (qmail 29655 invoked from network); 30 Nov 2011 18:44:19 +0100
Received: from unknown (HELO us.es) (192.168.2.13) by us.es with SMTP; 30 Nov 2011 18:44:19 +0100
Received: (qmail 7805 invoked by uid 507); 30 Nov 2011 17:44:17 -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/14042.   Clear:RC:1(127.0.0.1):.  Processed in 0.043961 secs); 30 Nov 2011 17:44:17 -0000
Received: from unknown (HELO antivirus3) (127.0.0.1) by us.es with SMTP; 30 Nov 2011 17:44:17 -0000
Received: from 192.168.1.13 (192.168.1.13) by antivirus3 (F-Secure/fsigk_smtp/406/antivirus3); Wed, 30 Nov 2011 18:44:17 +0100 (CET)
X-Virus-Status: clean(F-Secure/fsigk_smtp/406/antivirus3)
Received: (qmail 18121 invoked from network); 30 Nov 2011 18:44:17 +0100
Received: from trajano.us.es (193.147.162.130) by us.es with AES256-SHA encrypted SMTP; 30 Nov 2011 18:44:17 +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 pAUHiF2Q029537 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NOT); Wed, 30 Nov 2011 18:44:16 +0100
Message-ID: <4ED66B87.7050907@trajano.us.es>
Date: Wed, 30 Nov 2011 18:44:39 +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>
In-Reply-To: <5F7BCCF5541B7444830A2288ABBEBC962161900780@FRMRSSXCHMBSD2.dc-m.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: Wed, 30 Nov 2011 17:44:21 -0000

> 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  Wed Nov 30 10:31:09 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 CCE9221F8B70 for <megaco@ietfa.amsl.com>; Wed, 30 Nov 2011 10:31:09 -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 d2F7cTOQHW+B for <megaco@ietfa.amsl.com>; Wed, 30 Nov 2011 10:31:09 -0800 (PST)
Received: from mail.us.es (mail.us.es [193.147.175.20]) by ietfa.amsl.com (Postfix) with ESMTP id A6DB821F88B7 for <megaco@ietf.org>; Wed, 30 Nov 2011 10:31:08 -0800 (PST)
Received: (qmail 28885 invoked from network); 30 Nov 2011 19:31:06 +0100
Received: from unknown (HELO us.es) (192.168.2.13) by us.es with SMTP; 30 Nov 2011 19:31:06 +0100
Received: (qmail 13621 invoked by uid 507); 30 Nov 2011 18:31:03 -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/14044.   Clear:RC:1(127.0.0.1):.  Processed in 0.052653 secs); 30 Nov 2011 18:31:03 -0000
Received: from unknown (HELO antivirus3) (127.0.0.1) by us.es with SMTP; 30 Nov 2011 18:31:03 -0000
Received: from 192.168.1.13 (192.168.1.13) by antivirus3 (F-Secure/fsigk_smtp/406/antivirus3); Wed, 30 Nov 2011 19:31:03 +0100 (CET)
X-Virus-Status: clean(F-Secure/fsigk_smtp/406/antivirus3)
Received: (qmail 26194 invoked from network); 30 Nov 2011 19:31:02 +0100
Received: from trajano.us.es (193.147.162.130) by us.es with AES256-SHA encrypted SMTP; 30 Nov 2011 19:31:02 +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 pAUIV1Qk030241 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NOT); Wed, 30 Nov 2011 19:31:02 +0100
Message-ID: <4ED6767D.7070109@trajano.us.es>
Date: Wed, 30 Nov 2011 19:31:25 +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
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: Wed, 30 Nov 2011 18:31:09 -0000

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
>


From arindam.bhattacharjee@alcatel-lucent.com  Wed Nov 30 12:20:49 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 45B701F0C5F for <megaco@ietfa.amsl.com>; Wed, 30 Nov 2011 12:20:49 -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 Wr0VVxNR9RNZ for <megaco@ietfa.amsl.com>; Wed, 30 Nov 2011 12:20:48 -0800 (PST)
Received: from ihemail4.lucent.com (ihemail4.lucent.com [135.245.0.39]) by ietfa.amsl.com (Postfix) with ESMTP id 3F5751F0C58 for <megaco@ietf.org>; Wed, 30 Nov 2011 12:20:48 -0800 (PST)
Received: from usnavsmail1.ndc.alcatel-lucent.com (usnavsmail1.ndc.alcatel-lucent.com [135.3.39.9]) by ihemail4.lucent.com (8.13.8/IER-o) with ESMTP id pAUKKhcQ017489 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 30 Nov 2011 14:20:43 -0600 (CST)
Received: from USNAVSXCHHUB03.ndc.alcatel-lucent.com (usnavsxchhub03.ndc.alcatel-lucent.com [135.3.39.112]) by usnavsmail1.ndc.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id pAUKKSJJ014369 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Wed, 30 Nov 2011 14:20:43 -0600
Received: from USNAVSXCHMBSA2.ndc.alcatel-lucent.com ([135.3.39.126]) by USNAVSXCHHUB03.ndc.alcatel-lucent.com ([135.3.39.112]) with mapi; Wed, 30 Nov 2011 14:20:28 -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: Wed, 30 Nov 2011 14:20:24 -0600
Thread-Topic: [Megaco] Selection of media (m=) at MG
Thread-Index: Acyvjj0XGCIlvmHrQnmrkPzBymtpZAACqnKw
Message-ID: <703C56B521385C4C9091299BE82357B7EF26034C@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>
In-Reply-To: <4ED6767D.7070109@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.9
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: Wed, 30 Nov 2011 20:20:49 -0000

Hi Javi,
+ call establishment phase: H.248 Command.req for tone/announcement=20
control plus media configuration with voice codec
> You can do that by using reservevalue =3DON 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 cl=
earmode.

+ information phase: H.248 Command.req for modification of the media=20
configuration towards CLEARMODE
> in this phase MGC may send reservevalue =3DOFF with SDP ClearMode only, r=
eleasing G711 resource.

-Arindam=20

-----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=20
control plus media configuration with voice codec
+ information phase: H.248 Command.req for modification of the media=20
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=
=20
does not support the CLEARMODE due to insufficient resources (MGC may=20
audit the MG before the call to check it supports CLEARMODE, but MGC can=20
not know how its resources will change during the call).

In that case, it would not be possible to continue a call that has=20
already begun, which should not happen. The SDP description should=20
ensure to the MGC that the MG reserves the resources needed by the call=20
prior to the establishment of it.

If this is true, it would not be valid to use the modify command between=20
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')=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=20
> MG?: would it be necessary to create a context, or would it 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 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 should not=20
> be involved in its Megaco context?
>
> Regards,
>
>
>
>> PS
>> Your previous email was related to ISDN-to-SIP interworking at call=20
>> control level, a subject which is out of scope of MEGACO.
>> Thus, something for SIPPING, SIP-IMPLEMENTERS, ... (or TISPAN WG3=20
>> 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
