
From loa@pi.nu  Thu Dec  1 01:35:09 2011
Return-Path: <loa@pi.nu>
X-Original-To: pwe3@ietfa.amsl.com
Delivered-To: pwe3@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 27CD821F8C31; Thu,  1 Dec 2011 01:35:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xwLfGcYdGb8A; Thu,  1 Dec 2011 01:35:08 -0800 (PST)
Received: from mail.pi.nu (mail.pi.nu [194.71.127.148]) by ietfa.amsl.com (Postfix) with ESMTP id 8293621F8669; Thu,  1 Dec 2011 01:35:08 -0800 (PST)
Received: from [192.168.1.64] (81-236-221-144-no93.tbcn.telia.com [81.236.221.144]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: loa@pi.nu) by mail.pi.nu (Postfix) with ESMTPSA id 858712A8004; Thu,  1 Dec 2011 10:35:06 +0100 (CET)
Message-ID: <4ED74A49.3070709@pi.nu>
Date: Thu, 01 Dec 2011 10:35:05 +0100
From: Loa Andersson <loa@pi.nu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:8.0) Gecko/20111105 Thunderbird/8.0
MIME-Version: 1.0
To: "mpls@ietf.org" <mpls@ietf.org>,  MPLS-TP ad hoc team <ahmpls-tp@lists.itu.int>, "mpls-chairs@tools.ietf.org" <mpls-chairs@tools.ietf.org>, pwe3@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: [PWE3] Poll on draft-farrel-mpls-tp-mip-mep-map
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pwe3>, <mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pwe3>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 01 Dec 2011 09:35:09 -0000

Working Group,

this is to start a two week poll to see if there is support to make
draft-farrel-mpls-tp-mip-mep-map-05 an mpls working group draft.

Pleased send your comments to the mpls working group mailing list
(mpls@ietf.org).

This poll ends Dec 15, 2011.

/Loa

for the mpls wg chairs
-- 


Loa Andersson                         email: loa.andersson@ericsson.com
Sr Strategy and Standards Manager            loa@pi.nu
Ericsson Inc                          phone: +46 10 717 52 13
                                              +46 767 72 92 13

From hideki.endo.es@hitachi.com  Thu Dec  1 02:27:50 2011
Return-Path: <hideki.endo.es@hitachi.com>
X-Original-To: pwe3@ietfa.amsl.com
Delivered-To: pwe3@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E1DAF21F8BEB; Thu,  1 Dec 2011 02:27:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.09
X-Spam-Level: 
X-Spam-Status: No, score=-1.09 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, RCVD_IN_DNSWL_LOW=-1]
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 H+9m1Ogaq2Tf; Thu,  1 Dec 2011 02:27:50 -0800 (PST)
Received: from mail7.hitachi.co.jp (mail7.hitachi.co.jp [133.145.228.42]) by ietfa.amsl.com (Postfix) with ESMTP id 700A421F8BE7; Thu,  1 Dec 2011 02:27:50 -0800 (PST)
Received: from mlsv5.hitachi.co.jp (unknown [133.144.234.166]) by mail7.hitachi.co.jp (Postfix) with ESMTP id 92F9437AC3; Thu,  1 Dec 2011 19:27:49 +0900 (JST)
Received: from mfilter05.hitachi.co.jp by mlsv5.hitachi.co.jp (8.13.1/8.13.1) id pB1ARnaa018423; Thu, 1 Dec 2011 19:27:49 +0900
Received: from vshuts4.hitachi.co.jp (vshuts4.hitachi.co.jp [10.201.6.80]) by mfilter05.hitachi.co.jp (Switch-3.3.4/Switch-3.3.4) with ESMTP id pB1ARmtq012579; Thu, 1 Dec 2011 19:27:49 +0900
X-AuditID: b753bd60-999c5ba000003356-0e-4ed756a409b3
Received: from gmml25.itg.hitachi.co.jp (unknown [158.213.165.145]) by vshuts4.hitachi.co.jp (Symantec Mail Security) with ESMTP id 61018204364; Thu,  1 Dec 2011 19:27:48 +0900 (JST)
Received: from [127.0.0.1] by gmml25.itg.hitachi.co.jp (AIX5.2/8.11.6p2/8.11.0) id pB1ARma15405230; Thu, 1 Dec 2011 19:27:48 +0900
Message-Type: Multiple Part
MIME-Version: 1.0
Message-ID: <XNM1$7$0$0$$6$1$2$A$5002330U4ed75670@hitachi.com>
Content-Type: text/plain; charset=us-ascii
To: <mpls@ietf.org>
From: <hideki.endo.es@hitachi.com>
Date: Thu, 1 Dec 2011 19:27:27 +0900
References: <4ED74A49.3070709@pi.nu>
Priority: normal
Importance: normal
X400-Content-Identifier: X4ED7567000000M
X400-MTS-Identifier: [/C=JP/ADMD=HITNET/PRMD=HITACHI/;gmml281112011926564HR]
Content-Transfer-Encoding: 7bit
X-Brightmail-Tracker: AAAAAA==
Cc: mpls-chairs@tools.ietf.org, ahmpls-tp@lists.itu.int, pwe3@ietf.org
Subject: Re: [PWE3] Poll on draft-farrel-mpls-tp-mip-mep-map
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pwe3>, <mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pwe3>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 01 Dec 2011 10:27:51 -0000

Support.
The solution on this draft has already been considered in RFC6426.

BR,
Hideki


>Working Group,
>
>this is to start a two week poll to see if there is support to make
>draft-farrel-mpls-tp-mip-mep-map-05 an mpls working group draft.
>
>Pleased send your comments to the mpls working group mailing list
>(mpls@ietf.org).
>
>This poll ends Dec 15, 2011.
>
>/Loa
>
>for the mpls wg chairs
>-- 
>
>
>Loa Andersson                         email: loa.andersson@ericsson.com
>Sr Strategy and Standards Manager            loa@pi.nu
>Ericsson Inc                          phone: +46 10 717 52 13
>                                              +46 767 72 92 13
>_______________________________________________
>pwe3 mailing list
>pwe3@ietf.org
>https://www.ietf.org/mailman/listinfo/pwe3
>

From javi@trajano.us.es  Thu Dec  1 08:37:07 2011
Return-Path: <javi@trajano.us.es>
X-Original-To: pwe3@ietfa.amsl.com
Delivered-To: pwe3@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9DC3A11E8280 for <pwe3@ietfa.amsl.com>; Thu,  1 Dec 2011 08:37:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.112
X-Spam-Level: 
X-Spam-Status: No, score=-6.112 tagged_above=-999 required=5 tests=[AWL=0.188,  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 uKCR3g490AUj for <pwe3@ietfa.amsl.com>; Thu,  1 Dec 2011 08:37:06 -0800 (PST)
Received: from mail.us.es (mail.us.es [193.147.175.20]) by ietfa.amsl.com (Postfix) with ESMTP id 3AFBA11E81DF for <pwe3@ietf.org>; Thu,  1 Dec 2011 08:37:05 -0800 (PST)
Received: (qmail 28482 invoked from network); 1 Dec 2011 17:37:04 +0100
Received: from unknown (HELO us.es) (192.168.2.13) by us.es with SMTP; 1 Dec 2011 17:37:04 +0100
Received: (qmail 4402 invoked by uid 507); 1 Dec 2011 16:36:59 -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/14056.   Clear:RC:1(127.0.0.1):.  Processed in 0.034022 secs); 01 Dec 2011 16:36:59 -0000
Received: from unknown (HELO antivirus3) (127.0.0.1) by us.es with SMTP; 1 Dec 2011 16:36:59 -0000
Received: from 192.168.1.13 (192.168.1.13) by antivirus3 (F-Secure/fsigk_smtp/406/antivirus3); Thu, 01 Dec 2011 17:36:59 +0100 (CET)
X-Virus-Status: clean(F-Secure/fsigk_smtp/406/antivirus3)
Received: (qmail 26479 invoked from network); 1 Dec 2011 17:36:59 +0100
Received: from trajano.us.es (193.147.162.130) by us.es with AES256-SHA encrypted SMTP; 1 Dec 2011 17:36:59 +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 pB1GawWF015079 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NOT) for <pwe3@ietf.org>; Thu, 1 Dec 2011 17:36:59 +0100
Message-ID: <4ED7AD46.7040106@trajano.us.es>
Date: Thu, 01 Dec 2011 17:37:26 +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: "pwe3@ietf.org" <pwe3@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: [PWE3] Payload needs to align with a 32-bit boundary
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pwe3>, <mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pwe3>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 01 Dec 2011 16:37:07 -0000

The requeriment "PW payload must be an integer number of 4 octets" 
affects to:

* Any PW:
     + TDMPWs (any type -SAToP, CESoPSN, TDMoIP AA1/AAL2-  and 
with/without RTP header)
     + HDLCPWs
     + FRPWs, ...

* and for any PSN:
     + L2TPv3
     + MPLS
     + UDP/IP
     + Ethernet


or only some of them?

Regards,

Javi


From Alexander.Vainshtein@ecitele.com  Thu Dec  1 09:07:58 2011
Return-Path: <Alexander.Vainshtein@ecitele.com>
X-Original-To: pwe3@ietfa.amsl.com
Delivered-To: pwe3@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 09B981F0C80 for <pwe3@ietfa.amsl.com>; Thu,  1 Dec 2011 09:07:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.303
X-Spam-Level: 
X-Spam-Status: No, score=-4.303 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_22=0.6, MIME_8BIT_HEADER=0.3, MIME_QP_LONG_LINE=1.396, 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 UqPpjW5byemb for <pwe3@ietfa.amsl.com>; Thu,  1 Dec 2011 09:07:57 -0800 (PST)
Received: from mail21.messagelabs.com (mail21.messagelabs.com [85.158.143.35]) by ietfa.amsl.com (Postfix) with SMTP id 1CFA31F0C7F for <pwe3@ietf.org>; Thu,  1 Dec 2011 09:07:56 -0800 (PST)
X-Env-Sender: Alexander.Vainshtein@ecitele.com
X-Msg-Ref: server-9.tower-21.messagelabs.com!1322759273!315148!1
X-Originating-IP: [147.234.242.235]
X-StarScan-Version: 6.4.1; banners=-,-,-
Received: (qmail 23561 invoked from network); 1 Dec 2011 17:07:54 -0000
Received: from ilptbmg02-out.ecitele.com (HELO ilptbmg02.ecitele.com) (147.234.242.235) by server-9.tower-21.messagelabs.com with SMTP; 1 Dec 2011 17:07:54 -0000
X-AuditID: 93eaf2e8-b7f276d000000ac3-7a-4ed7b583a364
Received: from ILPTEXCH02.ecitele.com ( [147.234.245.181]) by ilptbmg02.ecitele.com (Symantec Messaging Gateway) with SMTP id 6F.0B.02755.385B7DE4; Thu,  1 Dec 2011 19:12:36 +0200 (IST)
Received: from ILPTMAIL02.ecitele.com ([147.234.244.213]) by ILPTEXCH02.ecitele.com ([147.234.245.181]) with mapi; Thu, 1 Dec 2011 19:07:52 +0200
From: Alexander Vainshtein <Alexander.Vainshtein@ecitele.com>
To: =?iso-8859-1?Q?Javi_Mu=F1oz?= <javi@trajano.us.es>
Date: Thu, 1 Dec 2011 19:07:51 +0200
Thread-Topic: [PWE3] Payload needs to align with a 32-bit boundary
Thread-Index: AcywR3wEvSu6dEXSRKe2HwqEuErhBAAAgrzw
Message-ID: <A3C5DF08D38B6049839A6F553B331C7601120438B0AF@ILPTMAIL02.ecitele.com>
References: <4ED7AD46.7040106@trajano.us.es>
In-Reply-To: <4ED7AD46.7040106@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-CFilter-Loop: Reflected
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrAJsWRmVeSWpSXmKPExsUy+dWnL7otW6/7Gcw5y2HxfdpzNou+T1tY LD50/WB1YPZYsuQnk8ektWkeV1blBjBHNTDaJObl5ZcklqQqpKQWJ9sqBRRlliUmVyopZKbY KhkqKRTkJCan5qbmldgqJRYUpOalKNlx2QAFM/MUUvOS81My89JtlTyD/XUtLEwtdQ2V7NSU DY2tuUIyMosVUnVzEzNzFHJTi4sT01MVgCIgl+alpKYopOUXKZRkpCoUJUxmzui7tZml4Dpf xYorX5kbGFdydzFycEgImEhMPZrWxcgJZIpJXLi3nq2LkYtDSGA3o8T+V5OZIZypjBKzX+5i BaliE7CV2LT6LhuILSJgJvFv4WwWEJtZIFpi1t4bjCA2i4CKxJyJs5lAbGEBR4nmj99ZIeqd JGavfQVlG0lM+dUDVs8rECix/OMGsJlCAjoSUyeuBpvJKaAr8fpDK1icEei676fWMEHsEpe4 9WQ+E8TVAhJL9pxnhrBFJV4+/scKUS8qcad9PSNEvZ7EjalT2CBsbYllC18zQ+wVlDg58wkL RK+kxMEVN1gmMIrPQrJiFpL2WUjaZyFpX8DIsopRMjOnoCQpN93ASDe/tEQvNTmzJDUnVS85 P3cTIyS9vNjBePuM5iFGAQ5GJR7eD/3X/IRYE8uKK3MPMUpyMCmJ8p7ddN1PiC8pP6UyI7E4 I76oNCe1+BCjBAezkgjv+qlAOd6UxMqq1KJ8mJQFMKQnMktxJ+eD4rsk3tjAAIWjJM7bnfzG V0ggHZjwslNTC1KLYFplODiUJHj7NwNNFSxKTU+tSMvMKUFIM3FwgmzmAdrcCVLDW1yQmFuc mQ6RP8Woy7Hn86QzjEIsefl5qVLivMtBigRAijJK8+DmgDJK/f///18xigP9LMzbDFLFA0yc cJNeAS1hAlrSPvkKyBJgBoFLSTUwmk8NVj3o1cLwaP8j9xXcCSyRXxc/DL0s3Bfw0nqF9XK3 nHXZ9jO1ar61y6pNeML9+M1KH/+br8INxAs9DuUnPdLodH98tu3fl5V+0jet7xjuMS08qGck dmCm1oFthepzvfYr3wnsf/Vw7ZlQzTIv3/VO1Smr5i2ok5I5MuUXf3X5eTXLiNfTlViKMxIN tZiLihMBp++6yAMEAAA=
Cc: "Yaakov Stein \(yaakov_s@rad.com\)" <yaakov_s@rad.com>, "pwe3@ietf.org" <pwe3@ietf.org>
Subject: Re: [PWE3] Payload needs to align with a 32-bit boundary
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pwe3>, <mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pwe3>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 01 Dec 2011 17:07:58 -0000

Javi,
RFC 4448 does not add any padding to Ethernet frames (comprising the payload=
 of Ethernet PWs), nor does it provide for removing such padding. And since=
 Ethernet frames can be of any length starting from 64 octets and up to the=
 MTU, there is clearly no requirement for the alignment of you're asking abo=
ut.
The same applies to HDLC and FR PWs.

For ATM PWs carrying cells in N:1 mode the payload size would be a multiple=
 of 52 and hence a multiple of 4.  But the rest of the ATM modes would not i=
mpose any "alignment" restrictions on the payload size.

With TDMoIP in AAL1 mode (Yaakov, please correct me if I am missing somethin=
g) the payload of a PW packet is comprised by several AAL1 PDUs, and hence i=
ts size is a multiple of 48. I am not sure about TDMoIP in AAL2 mode.

Last but not least, RFC 4553 (SAToP) does not place any limitations on the p=
ayload size. With CESoPSN, the payload size must be a multiple of the number=
 of timeslots a given CESoPSN PW carries, bit no other restrictions exist.


Regards,
     Sasha


> -----Original Message-----
> From: pwe3-bounces@ietf.org [mailto:pwe3-bounces@ietf.org] On Behalf
> Of Javi Mu?oz
> Sent: Thursday, December 01, 2011 6:37 PM
> To: pwe3@ietf.org
> Subject: [PWE3] Payload needs to align with a 32-bit boundary
> 
> The requeriment "PW payload must be an integer number of 4 octets"
> affects to:
> 
> * Any PW:
>      + TDMPWs (any type -SAToP, CESoPSN, TDMoIP AA1/AAL2-  and
> with/without RTP header)
>      + HDLCPWs
>      + FRPWs, ...
> 
> * and for any PSN:
>      + L2TPv3
>      + MPLS
>      + UDP/IP
>      + Ethernet
> 
> 
> or only some of them?
> 
> Regards,
> 
> Javi
> 
> _______________________________________________
> pwe3 mailing list
> pwe3@ietf.org
> https://www.ietf.org/mailman/listinfo/pwe3


This e-mail message is intended for the recipient only and contains informat=
ion which is CONFIDENTIAL and which may be proprietary to ECI Telecom. If yo=
u have received this transmission in error, please inform us by e-mail, phon=
e or fax, and then delete the original and all copies thereof.


From ryoo@etri.re.kr  Thu Dec  1 16:44:04 2011
Return-Path: <ryoo@etri.re.kr>
X-Original-To: pwe3@ietfa.amsl.com
Delivered-To: pwe3@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E517721F984D for <pwe3@ietfa.amsl.com>; Thu,  1 Dec 2011 16:44:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -98.632
X-Spam-Level: 
X-Spam-Status: No, score=-98.632 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_MISMATCH_INFO=1.448, HTML_IMAGE_ONLY_32=1.778, HTML_MESSAGE=0.001, MIME_HTML_MOSTLY=0.001, MPART_ALT_DIFF=0.739, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2QtkTCA3FNa3 for <pwe3@ietfa.amsl.com>; Thu,  1 Dec 2011 16:44:04 -0800 (PST)
Received: from email1.etri.info (email1.etri.re.kr [129.254.16.131]) by ietfa.amsl.com (Postfix) with ESMTP id 355EE21F984A for <pwe3@ietf.org>; Thu,  1 Dec 2011 16:44:04 -0800 (PST)
Received: from mail pickup service by email1.etri.info with Microsoft SMTPSVC; Fri, 2 Dec 2011 09:44:01 +0900
priority: normal
X-ReadCheckName: pwe3%40ietf.org
Thread-Topic: [mpls] Poll on draft-farrel-mpls-tp-mip-mep-map
X-ReadCheckMessageID: <fe5bce91-8940-4933-be0c-26c532490c65@etri.re.kr>
thread-index: Acywi3vtGdXugoTXQs6P6hrkBDTkPA==
Content-Transfer-Encoding: 7bit
From: "Ryoo, Jeong-dong" <ryoo@etri.re.kr>
To: "Loa Andersson" <loa@pi.nu>, <mpls@ietf.org>, "MPLS-TP ad hoc team" <ahmpls-tp@lists.itu.int>, <mpls-chairs@tools.ietf.org>, <pwe3@ietf.org>
Date: Fri, 2 Dec 2011 09:44:01 +0900
Comment: ??, ???, 
Message-ID: <7D56FA242633409C9B46CDC6B7B300D8@etri.info>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_17E8_01CCB0D6.EBD77E40"
X-Mailer: Microsoft CDO for Exchange 2000
Content-Class: urn:content-classes:message
Importance: normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.4133
X-OriginalArrivalTime: 02 Dec 2011 00:44:01.0581 (UTC) FILETIME=[7C1845D0:01CCB08B]
Subject: Re: [PWE3] [mpls] Poll on draft-farrel-mpls-tp-mip-mep-map
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: "Ryoo, Jeong-dong" <ryoo@etri.re.kr>
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pwe3>, <mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pwe3>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Dec 2011 00:44:05 -0000

This is a multi-part message in MIME format.

------=_NextPart_000_17E8_01CCB0D6.EBD77E40
Content-Type: text/plain;
	charset="utf-8"
Content-Transfer-Encoding: base64


------=_NextPart_000_17E8_01CCB0D6.EBD77E40
Content-Type: text/html;
	charset="utf-8"
Content-Transfer-Encoding: base64

PERJViBzdHlsZT0iRk9OVC1GQU1JTFk6IEFyaWFsOyBGT05ULVNJWkU6IDEwcHQiIGlkPW1zZ2Jv
ZHk+DQo8RElWPlllcy9TdXBwb3J0PC9ESVY+DQo8RElWPjxCUj4mbmJzcDs8L0RJVj4NCjxESVYg
c3R5bGU9IkZPTlQtRkFNSUxZOiA7IFdPUkQtQlJFQUs6IGJyZWFrLWFsbCI+DQo8RElWPg0KPERJ
ViBzdHlsZT0iRk9OVC1GQU1JTFk6ICI+DQo8RElWPg0KPERJViBzdHlsZT0iRk9OVC1GQU1JTFk6
ICI+DQo8RElWPg0KPERJViBzdHlsZT0iRk9OVC1GQU1JTFk6ICI+DQo8RElWPjxGT05UIHNpemU9
MiBmYWNlPUFyaWFsPj09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09
PT08QlI+SmVvbmctZG9uZyBSeW9vLCBQaC5ELjxCUj5QcmluY2lwYWwgTWVtYmVyIG9mIFJlc2Vh
cmNoIFN0YWZmPEJSPk5ldHdvcmsgUmVzZWFyY2ggRGVwYXJ0bWVudDxCUj5FbGVjdHJvbmljcyBh
bmQgVGVsZWNvbW11bmljYXRpb25zIFJlc2VhcmNoIEluc3RpdHV0ZSAoRVRSSSkgPEJSPlBob25l
OiArODItNDItODYwLTUzODQsIEZheDogKzgyLTQyLTg2MC02MzQyPC9GT05UPjxGT05UIHNpemU9
MiBmYWNlPUFyaWFsPjxCUj5FbWFpbDogPC9GT05UPjxBIGhyZWY9Im1haWx0bzpyeW9vQGV0cmku
cmUua3IiIHRhcmdldD1fYmxhbms+PEZPTlQgc2l6ZT0yIGZhY2U9QXJpYWw+cnlvb0BldHJpLnJl
LmtyPC9GT05UPjwvQT48QlI+PEZPTlQgc2l6ZT0yIGZhY2U9QXJpYWw+PT09PT09PT09PT09PT09
PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PTwvRk9OVD48L0RJVj48L0RJVj48L0RJVj48
L0RJVj48L0RJVj48L0RJVj48L0RJVj48L0RJVj4NCjxESVY+PEJSPi0tLS0tT3JpZ2luYWwgTWVz
c2FnZS0tLS0tPEJSPjxCPkZyb206PC9CPiAiTG9hIEFuZGVyc3NvbiIgJmx0O2xvYUBwaS5udSZn
dDs8QlI+PEI+RnJvbSBEYXRlOjwvQj4gMjAxMS0xMi0wMSBQTSA2OjM1OjA1PEJSPjxCPlRvOjwv
Qj4gIm1wbHNAaWV0Zi5vcmciICZsdDttcGxzQGlldGYub3JnJmd0OywgIk1QTFMtVFAgYWQgaG9j
IHRlYW0iICZsdDthaG1wbHMtdHBAbGlzdHMuaXR1LmludCZndDssICJtcGxzLWNoYWlyc0B0b29s
cy5pZXRmLm9yZyIgJmx0O21wbHMtY2hhaXJzQHRvb2xzLmlldGYub3JnJmd0OywgInB3ZTNAaWV0
Zi5vcmciICZsdDtwd2UzQGlldGYub3JnJmd0OzxCUj48Qj5DYzo8L0I+IDxCUj48Qj5TdWJqZWN0
OjwvQj4gW21wbHNdIFBvbGwgb24gZHJhZnQtZmFycmVsLW1wbHMtdHAtbWlwLW1lcC1tYXA8QlI+
PEJSPjwvRElWPg0KPERJVj48IS0tIENvbnZlcnRlZCBmcm9tIHRleHQvcGxhaW4gZm9ybWF0IC0t
PjxCUj4NCjxQPjxGT05UIHNpemU9Mj5Xb3JraW5nIEdyb3VwLDxCUj48QlI+dGhpcyBpcyB0byBz
dGFydCBhIHR3byB3ZWVrIHBvbGwgdG8gc2VlIGlmIHRoZXJlIGlzIHN1cHBvcnQgdG8gbWFrZTxC
Uj5kcmFmdC1mYXJyZWwtbXBscy10cC1taXAtbWVwLW1hcC0wNSBhbiBtcGxzIHdvcmtpbmcgZ3Jv
dXAgZHJhZnQuPEJSPjxCUj5QbGVhc2VkIHNlbmQgeW91ciBjb21tZW50cyB0byB0aGUgbXBscyB3
b3JraW5nIGdyb3VwIG1haWxpbmcgbGlzdDxCUj4obXBsc0BpZXRmLm9yZykuPEJSPjxCUj5UaGlz
IHBvbGwgZW5kcyBEZWMgMTUsIDIwMTEuPEJSPjxCUj4vTG9hPEJSPjxCUj5mb3IgdGhlIG1wbHMg
d2cgY2hhaXJzPEJSPi0tPEJSPjxCUj48QlI+TG9hIEFuZGVyc3NvbiZuYnNwOyZuYnNwOyZuYnNw
OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZu
YnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNw
OyZuYnNwOyZuYnNwOyBlbWFpbDogbG9hLmFuZGVyc3NvbkBlcmljc3Nvbi5jb208QlI+U3IgU3Ry
YXRlZ3kgYW5kIFN0YW5kYXJkcyBNYW5hZ2VyJm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7
Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7IGxvYUBwaS5udTxCUj5Fcmljc3Nv
biBJbmMmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJz
cDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsm
bmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsgcGhvbmU6ICs0NiAxMCA3
MTcgNTIgMTM8QlI+Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5i
c3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7
Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5i
c3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7
Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7ICs0
NiA3NjcgNzIgOTIgMTM8QlI+X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX188QlI+bXBscyBtYWlsaW5nIGxpc3Q8QlI+bXBsc0BpZXRmLm9yZzxCUj48QSBocmVm
PSJodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL21wbHMiIHRhcmdldD1fYmxh
bms+aHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9tcGxzPC9BPjxCUj48L0ZP
TlQ+PC9QPjwvRElWPjwvRElWPjxpbWcgc3R5bGU9ImRpc3BsYXk6bm9uZSIgd2lkdGg9MCBoZWln
aHQ9MCBzcmM9Imh0dHA6Ly91bWFpbC5ldHJpLnJlLmtyL0V4dGVybmFsX1JlYWRDaGVjay5hc3B4
P2VtYWlsPXB3ZTNAaWV0Zi5vcmcmbmFtZT1wd2UzJTQwaWV0Zi5vcmcmZnJvbWVtYWlsPXJ5b29A
ZXRyaS5yZS5rciZtZXNzYWdlaWQ9JTNDZmU1YmNlOTEtODk0MC00OTMzLWJlMGMtMjZjNTMyNDkw
YzY1QGV0cmkucmUua3IlM0UiPg==

------=_NextPart_000_17E8_01CCB0D6.EBD77E40--

From c-sai@bx.jp.nec.com  Thu Dec  1 23:41:11 2011
Return-Path: <c-sai@bx.jp.nec.com>
X-Original-To: pwe3@ietfa.amsl.com
Delivered-To: pwe3@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7D27721F8C83; Thu,  1 Dec 2011 23:41:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.09
X-Spam-Level: 
X-Spam-Status: No, score=-0.09 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265]
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 vWKhOAia-W6W; Thu,  1 Dec 2011 23:41:10 -0800 (PST)
Received: from tyo201.gate.nec.co.jp (TYO201.gate.nec.co.jp [202.32.8.193]) by ietfa.amsl.com (Postfix) with ESMTP id 9889C21F8B4C; Thu,  1 Dec 2011 23:41:08 -0800 (PST)
Received: from mailgate3.nec.co.jp ([10.7.69.193]) by tyo201.gate.nec.co.jp (8.13.8/8.13.4) with ESMTP id pB27f6mh016834;  Fri, 2 Dec 2011 16:41:06 +0900 (JST)
Received: (from root@localhost) by mailgate3.nec.co.jp (8.11.7/3.7W-MAILGATE-NEC) id pB27f6K03039; Fri, 2 Dec 2011 16:41:06 +0900 (JST)
Received: from mail01b.kamome.nec.co.jp (mail01b.kamome.nec.co.jp [10.25.43.2]) by mailsv3.nec.co.jp (8.13.8/8.13.4) with ESMTP id pB27f6pV006838; Fri, 2 Dec 2011 16:41:06 +0900 (JST)
Received: from kaishu.jp.nec.com ([10.26.220.5] [10.26.220.5]) by mail01b.kamome.nec.co.jp with ESMTP id BT-MMP-1238682; Fri, 2 Dec 2011 16:23:58 +0900
Received: from vpcja157 ([10.38.16.157] [10.38.16.157]) by mail.jp.nec.com with ESMTP; Fri, 2 Dec 2011 16:23:27 +0900
From: "Zhenlong Cui" <c-sai@bx.jp.nec.com>
To: <mpls@ietf.org>, "'MPLS-TP ad hoc team'" <ahmpls-tp@lists.itu.int>, <mpls-chairs@tools.ietf.org>, <pwe3@ietf.org>
References: <4ED74A49.3070709@pi.nu>
Date: Fri, 2 Dec 2011 16:23:27 +0900
Message-ID: <ADE10BC7469E446B9B21254FEB162B87@nsl.ad.nec.co.jp>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
In-reply-to: <4ED74A49.3070709@pi.nu>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5931
thread-index: AcywDIXu1B31GwVsSDqR4P9HhWsxQAAtmeyg
Subject: Re: [PWE3] [mpls] Poll on draft-farrel-mpls-tp-mip-mep-map
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pwe3>, <mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pwe3>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Dec 2011 07:41:11 -0000

Yes/Support.

Regards,
Zhenlong

> -----Original Message-----
> From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf Of Loa Andersson
> Sent: Thursday, December 01, 2011 6:35 PM
> To: mpls@ietf.org; MPLS-TP ad hoc team; mpls-chairs@tools.ietf.org; pwe3@ietf.org
> Subject: [mpls] Poll on draft-farrel-mpls-tp-mip-mep-map
> 
> Working Group,
> 
> this is to start a two week poll to see if there is support to make
> draft-farrel-mpls-tp-mip-mep-map-05 an mpls working group draft.
> 
> Pleased send your comments to the mpls working group mailing list
> (mpls@ietf.org).
> 
> This poll ends Dec 15, 2011.
> 
> /Loa
> 
> for the mpls wg chairs
> --
> 
> 
> Loa Andersson                         email: loa.andersson@ericsson.com
> Sr Strategy and Standards Manager            loa@pi.nu
> Ericsson Inc                          phone: +46 10 717 52 13
>                                               +46 767 72 92 13
> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls


From javi@trajano.us.es  Mon Dec  5 01:36:48 2011
Return-Path: <javi@trajano.us.es>
X-Original-To: pwe3@ietfa.amsl.com
Delivered-To: pwe3@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0013021F8AF4 for <pwe3@ietfa.amsl.com>; Mon,  5 Dec 2011 01:36:47 -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_22=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 pVjgtFw8bG0j for <pwe3@ietfa.amsl.com>; Mon,  5 Dec 2011 01:36:47 -0800 (PST)
Received: from mail.us.es (mail.us.es [193.147.175.20]) by ietfa.amsl.com (Postfix) with ESMTP id 82A0621F8A67 for <pwe3@ietf.org>; Mon,  5 Dec 2011 01:36:46 -0800 (PST)
Received: (qmail 25579 invoked from network); 5 Dec 2011 10:36:44 +0100
Received: from unknown (HELO us.es) (192.168.2.12) by us.es with SMTP; 5 Dec 2011 10:36:44 +0100
Received: (qmail 18951 invoked by uid 507); 5 Dec 2011 09:36:43 -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/14072.   Clear:RC:1(127.0.0.1):.  Processed in 0.043779 secs); 05 Dec 2011 09:36:43 -0000
Received: from unknown (HELO antivirus2) (127.0.0.1) by us.es with SMTP; 5 Dec 2011 09:36:43 -0000
Received: from 192.168.1.13 (192.168.1.13) by antivirus2 (F-Secure/fsigk_smtp/406/antivirus2); Mon, 05 Dec 2011 10:36:43 +0100 (CET)
X-Virus-Status: clean(F-Secure/fsigk_smtp/406/antivirus2)
Received: (qmail 19198 invoked from network); 5 Dec 2011 10:36:42 +0100
Received: from trajano.us.es (193.147.162.130) by us.es with AES256-SHA encrypted SMTP; 5 Dec 2011 10:36:42 +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 pB59aeNN006131 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NOT); Mon, 5 Dec 2011 10:36:42 +0100
Message-ID: <4EDC90B6.2000302@trajano.us.es>
Date: Mon, 05 Dec 2011 10:36:54 +0100
From: =?ISO-8859-1?Q?Javi_Mu=F1oz?= <javi@trajano.us.es>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; es-ES; rv:1.9.2.24) Gecko/20111103 Thunderbird/3.1.16
MIME-Version: 1.0
To: Alexander Vainshtein <Alexander.Vainshtein@ecitele.com>
References: <4ED7AD46.7040106@trajano.us.es> <A3C5DF08D38B6049839A6F553B331C7601120438B0AF@ILPTMAIL02.ecitele.com>
In-Reply-To: <A3C5DF08D38B6049839A6F553B331C7601120438B0AF@ILPTMAIL02.ecitele.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Cc: "Yaakov Stein \(yaakov_s@rad.com\)" <yaakov_s@rad.com>, "pwe3@ietf.org" <pwe3@ietf.org>
Subject: Re: [PWE3] Payload needs to align with a 32-bit boundary
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pwe3>, <mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pwe3>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 05 Dec 2011 09:36:48 -0000

Sasha,

Thanks, I agree.

We had an internal discussion in our working group. I just wanted to 
confirm my opinion.

Regards,

PD: With TDMoIP in AAL2 mode, the payload of a PW packet is comprised by 
several mini-cells, each 4 to 67 bytes.

Javi



El 01/12/2011 18:07, Alexander Vainshtein escribió:
> Javi,
> RFC 4448 does not add any padding to Ethernet frames (comprising the payload of Ethernet PWs), nor does it provide for removing such padding. And since Ethernet frames can be of any length starting from 64 octets and up to the MTU, there is clearly no requirement for the alignment of you're asking about.
> The same applies to HDLC and FR PWs.
>
> For ATM PWs carrying cells in N:1 mode the payload size would be a multiple of 52 and hence a multiple of 4.  But the rest of the ATM modes would not impose any "alignment" restrictions on the payload size.
>
> With TDMoIP in AAL1 mode (Yaakov, please correct me if I am missing something) the payload of a PW packet is comprised by several AAL1 PDUs, and hence its size is a multiple of 48. I am not sure about TDMoIP in AAL2 mode.
>
> Last but not least, RFC 4553 (SAToP) does not place any limitations on the payload size. With CESoPSN, the payload size must be a multiple of the number of timeslots a given CESoPSN PW carries, bit no other restrictions exist.
>
>
> Regards,
>       Sasha
>
>
>> -----Original Message-----
>> From: pwe3-bounces@ietf.org [mailto:pwe3-bounces@ietf.org] On Behalf
>> Of Javi Mu?oz
>> Sent: Thursday, December 01, 2011 6:37 PM
>> To: pwe3@ietf.org
>> Subject: [PWE3] Payload needs to align with a 32-bit boundary
>>
>> The requeriment "PW payload must be an integer number of 4 octets"
>> affects to:
>>
>> * Any PW:
>>       + TDMPWs (any type -SAToP, CESoPSN, TDMoIP AA1/AAL2-  and
>> with/without RTP header)
>>       + HDLCPWs
>>       + FRPWs, ...
>>
>> * and for any PSN:
>>       + L2TPv3
>>       + MPLS
>>       + UDP/IP
>>       + Ethernet
>>
>>
>> or only some of them?
>>
>> Regards,
>>
>> Javi
>>
>> _______________________________________________
>> pwe3 mailing list
>> pwe3@ietf.org
>> https://www.ietf.org/mailman/listinfo/pwe3
>
> This e-mail message is intended for the recipient only and contains information which is CONFIDENTIAL and which may be proprietary to ECI Telecom. If you have received this transmission in error, please inform us by e-mail, phone or fax, and then delete the original and all copies thereof.
>
>


From javi@trajano.us.es  Mon Dec 12 09:27:19 2011
Return-Path: <javi@trajano.us.es>
X-Original-To: pwe3@ietfa.amsl.com
Delivered-To: pwe3@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3D49521F8B54 for <pwe3@ietfa.amsl.com>; Mon, 12 Dec 2011 09:27:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.141
X-Spam-Level: 
X-Spam-Status: No, score=-6.141 tagged_above=-999 required=5 tests=[AWL=0.158,  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 dOWsAjmN0gVH for <pwe3@ietfa.amsl.com>; Mon, 12 Dec 2011 09:27:18 -0800 (PST)
Received: from mail.us.es (mail.us.es [193.147.175.20]) by ietfa.amsl.com (Postfix) with ESMTP id 0BD7921F8B55 for <pwe3@ietf.org>; Mon, 12 Dec 2011 09:27:17 -0800 (PST)
Received: (qmail 15070 invoked from network); 12 Dec 2011 18:27:16 +0100
Received: from unknown (HELO us.es) (192.168.2.12) by us.es with SMTP; 12 Dec 2011 18:27:16 +0100
Received: (qmail 3842 invoked by uid 507); 12 Dec 2011 17:27: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/14118.   Clear:RC:1(127.0.0.1):.  Processed in 0.033779 secs); 12 Dec 2011 17:27:15 -0000
Received: from unknown (HELO antivirus2) (127.0.0.1) by us.es with SMTP; 12 Dec 2011 17:27:15 -0000
Received: from 192.168.1.13 (192.168.1.13) by antivirus2 (F-Secure/fsigk_smtp/406/antivirus2); Mon, 12 Dec 2011 18:27:15 +0100 (CET)
X-Virus-Status: clean(F-Secure/fsigk_smtp/406/antivirus2)
Received: (qmail 1577 invoked from network); 12 Dec 2011 18:27:15 +0100
Received: from trajano.us.es (193.147.162.130) by us.es with AES256-SHA encrypted SMTP; 12 Dec 2011 18:27:15 +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 pBCHRFEe031798 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NOT) for <pwe3@ietf.org>; Mon, 12 Dec 2011 18:27:15 +0100
Message-ID: <4EE63982.7020403@trajano.us.es>
Date: Mon, 12 Dec 2011 18:27:30 +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: "pwe3@ietf.org" <pwe3@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: [PWE3] Different manipulation of channels in a Nx64 service
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pwe3>, <mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pwe3>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 12 Dec 2011 17:27:19 -0000

I have the next situation:

ISDN TE_A1 <---> [        ]       [        ] <---> ISDN TE_A2
ISDN TE_B1 <---> [        ]       [        ] <---> ISDN TE_B2
ISDN TE_C1 <---> [AGW(PE1)] <---> [AGW(PE2)] <---> ISDN TE_C2
...              [        ]       [        ]
ISDN TE_D1 <---> [        ]       [        ] <---> ISDN TE_D2


Each AGW finishes several ISDN interfaces (then, several TDM circuits).

* ISDN_TE_A1 has stablished a 64kbps call with ISDN_TE_A2 using the RTP 
codec CLEARMODE.
* ISDN_TE_B1 has stablished a 64kbps call with ISDN_TE_B2 using the RTP 
codec G.711-u without VAD
* ISDN_TE_C1 has stablished a 64kbps call with ISDN_TE_C2 using the RTP 
codec G.711-u with VAD
...
* ISDN_TE_D1 has stablished a 64kbps call with ISDN_TE_D2 using the RTP 
codec G.711-u without VAD

(the codec to use for each call would be indicated by an external 
signalling to the TDMPWs, such as Megaco)

Is it possible to use a single TDMoPW TDMoIP AAL2 to emulate all these 
calls?

If this is not possible to use different codec, at least, would it be 
possible to use a single TDMoPW TDMoIP AAL2 to emulate all calls with 
the same type of codec and media manipulation (i.e. calls "ISDN_TE_B1 - 
ISDN_TE_B2" and "ISDN_TE_D1 - ISDN_TE_D2").

NOTE: I propose directly AAL2, and not CESoPSN or TDMoIP AAL2, due to 
they are different calls, so that it is necessary to dynamically modify 
the number of channels, which is only supported by AAL2.


Regards,

Javi






From javi@trajano.us.es  Mon Dec 12 09:28:36 2011
Return-Path: <javi@trajano.us.es>
X-Original-To: pwe3@ietfa.amsl.com
Delivered-To: pwe3@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 09F3421F84ED for <pwe3@ietfa.amsl.com>; Mon, 12 Dec 2011 09:28:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.141
X-Spam-Level: 
X-Spam-Status: No, score=-6.141 tagged_above=-999 required=5 tests=[AWL=0.158,  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 owPRmqB8zgBT for <pwe3@ietfa.amsl.com>; Mon, 12 Dec 2011 09:28:35 -0800 (PST)
Received: from mail.us.es (mail.us.es [193.147.175.20]) by ietfa.amsl.com (Postfix) with ESMTP id 0F6AA21F8A62 for <pwe3@ietf.org>; Mon, 12 Dec 2011 09:28:34 -0800 (PST)
Received: (qmail 15822 invoked from network); 12 Dec 2011 18:28:34 +0100
Received: from unknown (HELO us.es) (192.168.2.13) by us.es with SMTP; 12 Dec 2011 18:28:34 +0100
Received: (qmail 17358 invoked by uid 507); 12 Dec 2011 17:27:59 -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/14118.   Clear:RC:1(127.0.0.1):.  Processed in 0.034173 secs); 12 Dec 2011 17:27:59 -0000
Received: from unknown (HELO antivirus3) (127.0.0.1) by us.es with SMTP; 12 Dec 2011 17:27:58 -0000
Received: from 192.168.1.13 (192.168.1.13) by antivirus3 (F-Secure/fsigk_smtp/406/antivirus3); Mon, 12 Dec 2011 18:27:58 +0100 (CET)
X-Virus-Status: clean(F-Secure/fsigk_smtp/406/antivirus3)
Received: (qmail 3027 invoked from network); 12 Dec 2011 18:27:58 +0100
Received: from trajano.us.es (193.147.162.130) by us.es with AES256-SHA encrypted SMTP; 12 Dec 2011 18:27:58 +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 pBCHRwtw031829 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NOT) for <pwe3@ietf.org>; Mon, 12 Dec 2011 18:27:58 +0100
Message-ID: <4EE639AD.4060009@trajano.us.es>
Date: Mon, 12 Dec 2011 18:28:13 +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: "pwe3@ietf.org" <pwe3@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: [PWE3] Different manipulation of channels in a Nx64 service
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pwe3>, <mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pwe3>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 12 Dec 2011 17:28:36 -0000

I have the next situation:

ISDN TE_A1 <---> [        ]       [        ] <---> ISDN TE_A2
ISDN TE_B1 <---> [        ]       [        ] <---> ISDN TE_B2
ISDN TE_C1 <---> [AGW(PE1)] <---> [AGW(PE2)] <---> ISDN TE_C2
...              [        ]       [        ]
ISDN TE_D1 <---> [        ]       [        ] <---> ISDN TE_D2


Each AGW finishes several ISDN interfaces (then, several TDM circuits).

* ISDN_TE_A1 has stablished a 64kbps call with ISDN_TE_A2 using the RTP 
codec CLEARMODE.
* ISDN_TE_B1 has stablished a 64kbps call with ISDN_TE_B2 using the RTP 
codec G.711-u without VAD
* ISDN_TE_C1 has stablished a 64kbps call with ISDN_TE_C2 using the RTP 
codec G.711-u with VAD
...
* ISDN_TE_D1 has stablished a 64kbps call with ISDN_TE_D2 using the RTP 
codec G.711-u without VAD

(the codec to use for each call would be indicated by an external 
signalling to the TDMPWs, such as Megaco)

Is it possible to use a single TDMoPW TDMoIP AAL2 to emulate all these 
calls?

If this is not possible to use different codec, at least, would it be 
possible to use a single TDMoPW TDMoIP AAL2 to emulate all calls with 
the same type of codec and media manipulation (i.e. calls "ISDN_TE_B1 - 
ISDN_TE_B2" and "ISDN_TE_D1 - ISDN_TE_D2").

NOTE: I propose directly AAL2, and not CESoPSN or TDMoIP AAL2, due to 
they are different calls, so that it is necessary to dynamically modify 
the number of channels, which is only supported by AAL2.


Regards,

Javi






From javi@trajano.us.es  Mon Dec 12 09:34:41 2011
Return-Path: <javi@trajano.us.es>
X-Original-To: pwe3@ietfa.amsl.com
Delivered-To: pwe3@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1BF1821F8B70 for <pwe3@ietfa.amsl.com>; Mon, 12 Dec 2011 09:34:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.156
X-Spam-Level: 
X-Spam-Status: No, score=-6.156 tagged_above=-999 required=5 tests=[AWL=0.143,  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 cQb2ZyG9uPNl for <pwe3@ietfa.amsl.com>; Mon, 12 Dec 2011 09:34:40 -0800 (PST)
Received: from mail.us.es (mail.us.es [193.147.175.20]) by ietfa.amsl.com (Postfix) with ESMTP id EAEA521F8B6D for <pwe3@ietf.org>; Mon, 12 Dec 2011 09:34:39 -0800 (PST)
Received: (qmail 15485 invoked from network); 12 Dec 2011 18:27:59 +0100
Received: from unknown (HELO us.es) (192.168.2.11) by us.es with SMTP; 12 Dec 2011 18:27:59 +0100
Received: (qmail 13311 invoked by uid 507); 12 Dec 2011 17:27:53 -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/14118.   Clear:RC:1(127.0.0.1):.  Processed in 0.08909 secs); 12 Dec 2011 17:27:53 -0000
Received: from unknown (HELO antivirus1) (127.0.0.1) by us.es with SMTP; 12 Dec 2011 17:27:53 -0000
Received: from 192.168.1.13 (192.168.1.13) by antivirus1 (F-Secure/fsigk_smtp/406/antivirus1); Mon, 12 Dec 2011 18:27:53 +0100 (CET)
X-Virus-Status: clean(F-Secure/fsigk_smtp/406/antivirus1)
Received: (qmail 2860 invoked from network); 12 Dec 2011 18:27:53 +0100
Received: from trajano.us.es (193.147.162.130) by us.es with AES256-SHA encrypted SMTP; 12 Dec 2011 18:27:53 +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 pBCHRrUw031821 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NOT) for <pwe3@ietf.org>; Mon, 12 Dec 2011 18:27:53 +0100
Message-ID: <4EE639A8.8000908@trajano.us.es>
Date: Mon, 12 Dec 2011 18:28:08 +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: "pwe3@ietf.org" <pwe3@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: [PWE3] Different manipulation of channels in a Nx64 service
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pwe3>, <mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pwe3>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 12 Dec 2011 17:34:41 -0000

I have the next situation:

ISDN TE_A1 <---> [        ]       [        ] <---> ISDN TE_A2
ISDN TE_B1 <---> [        ]       [        ] <---> ISDN TE_B2
ISDN TE_C1 <---> [AGW(PE1)] <---> [AGW(PE2)] <---> ISDN TE_C2
...              [        ]       [        ]
ISDN TE_D1 <---> [        ]       [        ] <---> ISDN TE_D2


Each AGW finishes several ISDN interfaces (then, several TDM circuits).

* ISDN_TE_A1 has stablished a 64kbps call with ISDN_TE_A2 using the RTP 
codec CLEARMODE.
* ISDN_TE_B1 has stablished a 64kbps call with ISDN_TE_B2 using the RTP 
codec G.711-u without VAD
* ISDN_TE_C1 has stablished a 64kbps call with ISDN_TE_C2 using the RTP 
codec G.711-u with VAD
...
* ISDN_TE_D1 has stablished a 64kbps call with ISDN_TE_D2 using the RTP 
codec G.711-u without VAD

(the codec to use for each call would be indicated by an external 
signalling to the TDMPWs, such as Megaco)

Is it possible to use a single TDMoPW TDMoIP AAL2 to emulate all these 
calls?

If this is not possible to use different codec, at least, would it be 
possible to use a single TDMoPW TDMoIP AAL2 to emulate all calls with 
the same type of codec and media manipulation (i.e. calls "ISDN_TE_B1 - 
ISDN_TE_B2" and "ISDN_TE_D1 - ISDN_TE_D2").

NOTE: I propose directly AAL2, and not CESoPSN or TDMoIP AAL1, due to 
they are different calls, so that it is necessary to dynamically modify 
the number of channels, which is only supported by AAL2.


Regards,

Javi






From javi@trajano.us.es  Mon Dec 12 10:33:54 2011
Return-Path: <javi@trajano.us.es>
X-Original-To: pwe3@ietfa.amsl.com
Delivered-To: pwe3@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 049D321F8AFA for <pwe3@ietfa.amsl.com>; Mon, 12 Dec 2011 10:33:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.174
X-Spam-Level: 
X-Spam-Status: No, score=-6.174 tagged_above=-999 required=5 tests=[AWL=0.125,  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 xMIB-JSVayOE for <pwe3@ietfa.amsl.com>; Mon, 12 Dec 2011 10:33:53 -0800 (PST)
Received: from mail.us.es (mail.us.es [193.147.175.20]) by ietfa.amsl.com (Postfix) with ESMTP id F140F21F8AD8 for <pwe3@ietf.org>; Mon, 12 Dec 2011 10:33:52 -0800 (PST)
Received: (qmail 30330 invoked from network); 12 Dec 2011 19:33:52 +0100
Received: from unknown (HELO us.es) (192.168.2.13) by us.es with SMTP; 12 Dec 2011 19:33:52 +0100
Received: (qmail 7031 invoked by uid 507); 12 Dec 2011 18:33:51 -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/14118.   Clear:RC:1(127.0.0.1):.  Processed in 0.029739 secs); 12 Dec 2011 18:33:51 -0000
Received: from unknown (HELO antivirus3) (127.0.0.1) by us.es with SMTP; 12 Dec 2011 18:33:50 -0000
Received: from 192.168.1.13 (192.168.1.13) by antivirus3 (F-Secure/fsigk_smtp/406/antivirus3); Mon, 12 Dec 2011 19:33:50 +0100 (CET)
X-Virus-Status: clean(F-Secure/fsigk_smtp/406/antivirus3)
Received: (qmail 27636 invoked from network); 12 Dec 2011 19:33:50 +0100
Received: from trajano.us.es (193.147.162.130) by us.es with AES256-SHA encrypted SMTP; 12 Dec 2011 19:33:50 +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 pBCIXob4032645 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NOT) for <pwe3@ietf.org>; Mon, 12 Dec 2011 19:33:50 +0100
Message-ID: <4EE6491E.6090409@trajano.us.es>
Date: Mon, 12 Dec 2011 19:34: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: "pwe3@ietf.org" <pwe3@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: [PWE3] PWs in the NGN network
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pwe3>, <mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pwe3>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 12 Dec 2011 18:33:54 -0000

In the ETSI or ITU-T NGN, is it possible the communication between two 
NGN TEs using a TDMPW?

TE NGN <---> PE <--  [NGN network]  --> PE <--> TE NGN


What NGN functional entity should be the PE (Provider Edge which 
terminates the PW)?

Regards,

Javi

From yaakov_s@rad.com  Tue Dec 13 00:26:17 2011
Return-Path: <yaakov_s@rad.com>
X-Original-To: pwe3@ietfa.amsl.com
Delivered-To: pwe3@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7774321F8548 for <pwe3@ietfa.amsl.com>; Tue, 13 Dec 2011 00:26:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.115
X-Spam-Level: 
X-Spam-Status: No, score=-102.115 tagged_above=-999 required=5 tests=[AWL=-0.417, BAYES_00=-2.599, J_CHICKENPOX_22=0.6, MIME_8BIT_HEADER=0.3, UNPARSEABLE_RELAY=0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pTKTn7m79Y3O for <pwe3@ietfa.amsl.com>; Tue, 13 Dec 2011 00:26:16 -0800 (PST)
Received: from rad.co.il (mailrelay02.rad.co.il [62.0.23.237]) by ietfa.amsl.com (Postfix) with ESMTP id DED7A21F8481 for <pwe3@ietf.org>; Tue, 13 Dec 2011 00:26:13 -0800 (PST)
Received: from Internal Mail-Server by MailRelay02 (envelope-from yaakov?s@rad.com) with AES128-SHA encrypted SMTP; 13 Dec 2011 10:04:54 +0200
Received: from EXRAD5.ad.rad.co.il ([192.114.24.28]) by EXRAD5.ad.rad.co.il ([192.114.24.28]) with mapi id 14.01.0323.003; Tue, 13 Dec 2011 10:26:10 +0200
From: Yaakov Stein <yaakov_s@rad.com>
To: =?Windows-1252?Q?Javi_Mu=F1oz?= <javi@trajano.us.es>, "pwe3@ietf.org" <pwe3@ietf.org>
Thread-Topic: [PWE3] Different manipulation of channels in a Nx64 service
Thread-Index: AQHMuPNTu2lISxaldki9+sQRHKsxRZXZaO7Q
Date: Tue, 13 Dec 2011 08:26:09 +0000
Message-ID: <07F7D7DED63154409F13298786A2ADC90427FBB4@EXRAD5.ad.rad.co.il>
References: <4EE63982.7020403@trajano.us.es>
In-Reply-To: <4EE63982.7020403@trajano.us.es>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.115.243.62]
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [PWE3] Different manipulation of channels in a Nx64 service
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pwe3>, <mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pwe3>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 13 Dec 2011 08:26:17 -0000

Javi

If I understand you question, you are asking whether an AAL2 TDMoIP PW can =
mix channels that=20
1) originated from different TDM trunks,  and=20
2) that are encoded with different coding systems (A-law, u-law, VAD, etc. =
etc.)

The answer to the first part is a strong affirmative.
One of the advantages of "loop emulation" (AAL2) as opposed to "circuit emu=
lation"
is that you break the timing relationship between the ingress and egress ch=
annels.
Put more formally, the TDM trunk (e.g., E1) is terminated and the individua=
l channel ("loop")
is extracted and optionally manipulated. Thus there is no requirement for t=
he
channels muxed in the PW to come from the same TDM trunk.
Were we to try to do this using circuit emulation, we would have to allow f=
or different clocks,
as is done in PDH and SDH systems. Note that TDM itself (E1 and T1) require=
s its clients
to be of precisely the same frequency and phase.

Please note, however, that the precise mapping of channels to trunks+timesl=
ots
would need to be configured by a management system as the TDM control proto=
col extensions=20
in RFC 5287 define an optional "mapping base" which only supports the singl=
e-trunk case.

The answer to the second part is not very different.
Since the channels are completely independent, they can carry anything you =
want.
I have been involved in cases where some of the CIDs were data (clear chann=
el)
perhaps even from >1 timeslot, while others were voice with VAD,
or even compressed voice.
However, the AAL2 control protocol extensions are woefully insufficient to =
describe
what is needed here. They indeed contain a VAD indicator and encoding field=
,
but only for the entire PW, not for individual CIDs.
It would be a trivial exercise to extend the TLV, but it would become very =
bulky.

If you absolutely can not configure and need to recognize the channel type =
automatically,
I can think of two alternatives.
First, you could rely on the native AAL2 UUI codepoint differentiation defi=
ned in I.366.
Second, you could use the method described in Y.1452 for multiplexing RTP s=
treams
(at the price of additional overhead).

Y(J)S






-----Original Message-----
From: pwe3-bounces@ietf.org [mailto:pwe3-bounces@ietf.org] On Behalf Of Jav=
i Mu?oz
Sent: Monday, December 12, 2011 19:28
To: pwe3@ietf.org
Subject: [PWE3] Different manipulation of channels in a Nx64 service

I have the next situation:

ISDN TE_A1 <---> [        ]       [        ] <---> ISDN TE_A2
ISDN TE_B1 <---> [        ]       [        ] <---> ISDN TE_B2
ISDN TE_C1 <---> [AGW(PE1)] <---> [AGW(PE2)] <---> ISDN TE_C2
...              [        ]       [        ]
ISDN TE_D1 <---> [        ]       [        ] <---> ISDN TE_D2


Each AGW finishes several ISDN interfaces (then, several TDM circuits).

* ISDN_TE_A1 has stablished a 64kbps call with ISDN_TE_A2 using the RTP=20
codec CLEARMODE.
* ISDN_TE_B1 has stablished a 64kbps call with ISDN_TE_B2 using the RTP=20
codec G.711-u without VAD
* ISDN_TE_C1 has stablished a 64kbps call with ISDN_TE_C2 using the RTP=20
codec G.711-u with VAD
...
* ISDN_TE_D1 has stablished a 64kbps call with ISDN_TE_D2 using the RTP=20
codec G.711-u without VAD

(the codec to use for each call would be indicated by an external=20
signalling to the TDMPWs, such as Megaco)

Is it possible to use a single TDMoPW TDMoIP AAL2 to emulate all these=20
calls?

If this is not possible to use different codec, at least, would it be=20
possible to use a single TDMoPW TDMoIP AAL2 to emulate all calls with=20
the same type of codec and media manipulation (i.e. calls "ISDN_TE_B1 -=20
ISDN_TE_B2" and "ISDN_TE_D1 - ISDN_TE_D2").

NOTE: I propose directly AAL2, and not CESoPSN or TDMoIP AAL2, due to=20
they are different calls, so that it is necessary to dynamically modify=20
the number of channels, which is only supported by AAL2.


Regards,

Javi





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

From javi@trajano.us.es  Tue Dec 13 03:25:26 2011
Return-Path: <javi@trajano.us.es>
X-Original-To: pwe3@ietfa.amsl.com
Delivered-To: pwe3@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2A7EE21F88AB for <pwe3@ietfa.amsl.com>; Tue, 13 Dec 2011 03:25:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.579
X-Spam-Level: 
X-Spam-Status: No, score=-5.579 tagged_above=-999 required=5 tests=[AWL=-0.480, BAYES_00=-2.599, J_CHICKENPOX_22=0.6, J_CHICKENPOX_63=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 IHo7yDfRVciZ for <pwe3@ietfa.amsl.com>; Tue, 13 Dec 2011 03:25:25 -0800 (PST)
Received: from mail.us.es (mail.us.es [193.147.175.20]) by ietfa.amsl.com (Postfix) with ESMTP id D7B2421F85A7 for <pwe3@ietf.org>; Tue, 13 Dec 2011 03:25:24 -0800 (PST)
Received: (qmail 28305 invoked from network); 13 Dec 2011 12:25:22 +0100
Received: from unknown (HELO us.es) (192.168.2.12) by us.es with SMTP; 13 Dec 2011 12:25:22 +0100
Received: (qmail 21889 invoked by uid 507); 13 Dec 2011 11:25:21 -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/14121.   Clear:RC:1(127.0.0.1):.  Processed in 0.047732 secs); 13 Dec 2011 11:25:21 -0000
Received: from unknown (HELO antivirus2) (127.0.0.1) by us.es with SMTP; 13 Dec 2011 11:25:21 -0000
Received: from 192.168.1.13 (192.168.1.13) by antivirus2 (F-Secure/fsigk_smtp/406/antivirus2); Tue, 13 Dec 2011 12:25:21 +0100 (CET)
X-Virus-Status: clean(F-Secure/fsigk_smtp/406/antivirus2)
Received: (qmail 11710 invoked from network); 13 Dec 2011 12:25:21 +0100
Received: from trajano.us.es (193.147.162.130) by us.es with AES256-SHA encrypted SMTP; 13 Dec 2011 12:25:21 +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 pBDBPKPY002705 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NOT); Tue, 13 Dec 2011 12:25:21 +0100
Message-ID: <4EE73621.1090802@trajano.us.es>
Date: Tue, 13 Dec 2011 12:25:21 +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: "pwe3@ietf.org" <pwe3@ietf.org>
References: <4EE63982.7020403@trajano.us.es> <07F7D7DED63154409F13298786A2ADC90427FBB4@EXRAD5.ad.rad.co.il>
In-Reply-To: <07F7D7DED63154409F13298786A2ADC90427FBB4@EXRAD5.ad.rad.co.il>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Yaakov Stein <yaakov_s@rad.com>
Subject: Re: [PWE3] Different manipulation of channels in a Nx64 service
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pwe3>, <mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pwe3>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 13 Dec 2011 11:25:26 -0000

Yaakov,
> Javi
>
> If I understand you question, you are asking whether an AAL2 TDMoIP PW can mix channels that
> 1) originated from different TDM trunks,  and
I assumed that this part was possible (we had already discussed in 
previous post).
> 2) that are encoded with different coding systems (A-law, u-law, VAD, etc. etc.)
This was my question.
> Please note, however, that the precise mapping of channels to trunks+timeslots
> would need to be configured by a management system as the TDM control protocol extensions
> in RFC 5287 define an optional "mapping base" which only supports the single-trunk case.
As we have already spoken on other occasions, my intention is to use 
Megaco for this mapping of channels to trunks+timeslots.

> Since the channels are completely independent, they can carry anything you want.
>
> However, the AAL2 control protocol extensions are woefully insufficient to describe
> what is needed here. They indeed contain a VAD indicator and encoding field,
> but only for the entire PW, not for individual CIDs.
What extensiones do you mean exactly?

> It would be a trivial exercise to extend the TLV, but it would become very bulky.
>
> If you absolutely can not configure and need to recognize the channel type automatically,
My intention was also to use MeGaCo(The node that finishes Q.931/SIP 
signaling know the type of each channel, so it can indicate to the AGW / 
PE using Megaco). Do you see any problem with that?

> I can think of two alternatives.
> First, you could rely on the native AAL2 UUI codepoint differentiation defined in I.366.
> Second, you could use the method described in Y.1452 for multiplexing RTP streams
> (at the price of additional overhead).
What method do you mean?(What clause Y.1452 is defined?).

Regards,

Javi
> Y(J)S
>
>
>
>
>
>
> -----Original Message-----
> From: pwe3-bounces@ietf.org [mailto:pwe3-bounces@ietf.org] On Behalf Of Javi Mu?oz
> Sent: Monday, December 12, 2011 19:28
> To: pwe3@ietf.org
> Subject: [PWE3] Different manipulation of channels in a Nx64 service
>
> I have the next situation:
>
> ISDN TE_A1<--->  [        ]       [        ]<--->  ISDN TE_A2
> ISDN TE_B1<--->  [        ]       [        ]<--->  ISDN TE_B2
> ISDN TE_C1<--->  [AGW(PE1)]<--->  [AGW(PE2)]<--->  ISDN TE_C2
> ...              [        ]       [        ]
> ISDN TE_D1<--->  [        ]       [        ]<--->  ISDN TE_D2
>
>
> Each AGW finishes several ISDN interfaces (then, several TDM circuits).
>
> * ISDN_TE_A1 has stablished a 64kbps call with ISDN_TE_A2 using the RTP
> codec CLEARMODE.
> * ISDN_TE_B1 has stablished a 64kbps call with ISDN_TE_B2 using the RTP
> codec G.711-u without VAD
> * ISDN_TE_C1 has stablished a 64kbps call with ISDN_TE_C2 using the RTP
> codec G.711-u with VAD
> ...
> * ISDN_TE_D1 has stablished a 64kbps call with ISDN_TE_D2 using the RTP
> codec G.711-u without VAD
>
> (the codec to use for each call would be indicated by an external
> signalling to the TDMPWs, such as Megaco)
>
> Is it possible to use a single TDMoPW TDMoIP AAL2 to emulate all these
> calls?
>
> If this is not possible to use different codec, at least, would it be
> possible to use a single TDMoPW TDMoIP AAL2 to emulate all calls with
> the same type of codec and media manipulation (i.e. calls "ISDN_TE_B1 -
> ISDN_TE_B2" and "ISDN_TE_D1 - ISDN_TE_D2").
>
> NOTE: I propose directly AAL2, and not CESoPSN or TDMoIP AAL2, due to
> they are different calls, so that it is necessary to dynamically modify
> the number of channels, which is only supported by AAL2.
>
>
> Regards,
>
> Javi
>
>
>
>
>
> _______________________________________________
> pwe3 mailing list
> pwe3@ietf.org
> https://www.ietf.org/mailman/listinfo/pwe3
>


From javi@trajano.us.es  Tue Dec 13 04:15:58 2011
Return-Path: <javi@trajano.us.es>
X-Original-To: pwe3@ietfa.amsl.com
Delivered-To: pwe3@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EDFC221F8ABD for <pwe3@ietfa.amsl.com>; Tue, 13 Dec 2011 04:15:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.165
X-Spam-Level: 
X-Spam-Status: No, score=-6.165 tagged_above=-999 required=5 tests=[AWL=0.133,  BAYES_00=-2.599, HTML_MESSAGE=0.001, 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 reI0x8IgSkRw for <pwe3@ietfa.amsl.com>; Tue, 13 Dec 2011 04:15:58 -0800 (PST)
Received: from mail.us.es (mail.us.es [193.147.175.20]) by ietfa.amsl.com (Postfix) with ESMTP id A4CC021F8ACC for <pwe3@ietf.org>; Tue, 13 Dec 2011 04:15:57 -0800 (PST)
Received: (qmail 2865 invoked from network); 13 Dec 2011 13:15:56 +0100
Received: from unknown (HELO us.es) (192.168.2.11) by us.es with SMTP; 13 Dec 2011 13:15:56 +0100
Received: (qmail 20551 invoked by uid 507); 13 Dec 2011 12:15:52 -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/14121.   Clear:RC:1(127.0.0.1):.  Processed in 0.049043 secs); 13 Dec 2011 12:15:52 -0000
Received: from unknown (HELO antivirus1) (127.0.0.1) by us.es with SMTP; 13 Dec 2011 12:15:52 -0000
Received: from 192.168.1.13 (192.168.1.13) by antivirus1 (F-Secure/fsigk_smtp/406/antivirus1); Tue, 13 Dec 2011 13:15:52 +0100 (CET)
X-Virus-Status: clean(F-Secure/fsigk_smtp/406/antivirus1)
Received: (qmail 13832 invoked from network); 13 Dec 2011 13:15:52 +0100
Received: from trajano.us.es (193.147.162.130) by us.es with AES256-SHA encrypted SMTP; 13 Dec 2011 13:15:52 +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 pBDCFpWv003490 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NOT) for <pwe3@ietf.org>; Tue, 13 Dec 2011 13:15:51 +0100
Message-ID: <4EE741F7.2080706@trajano.us.es>
Date: Tue, 13 Dec 2011 13:15:51 +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: "pwe3@ietf.org" <pwe3@ietf.org>
Content-Type: multipart/alternative; boundary="------------020309030703090009040305"
Subject: [PWE3] Set up of TDMPWs after the establishment of a call
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pwe3>, <mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pwe3>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 13 Dec 2011 12:15:59 -0000

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

Recommendations [ITU-T Y.2262; Y.2012] proposes to support multichannel 
ISDN calls using TDMoIP (UDP/IP TDMPWs). However, they do not indicate 
what kind of TDMPW, or when it must be set up.

The scenario is:

|ISDN TE| [1xD channel ] --> |AGW|<-->  MGC (Q.931/SIP)<--> |AGW|<-- 
[1xD channel ] |ISDN TE|
|_______| [NxB channels] --> |___|<--------[TDMPW]--------> |___|<-- 
[NxB channels] |_______|

* AGW (Access Gateway) would also be the PE (Provider Edge) of the TDMPW.


I understand that:

* Static TDMPWs (SAToP, CESoPSN, TDMoIP AAL1) must be set up before 
calls: so, they are not a good choice in this case for reasons of 
scalability (It will require the establishment of a PW with every 
potential destination AGW, which may be in the numbers of tens of 
thousands for a single PNO).

* TDMPW TDMoIP AAL2: I think it is possible to set up the TDMPW between 
two AGWs when the first call occurs between them. For second and 
subsequent calls, it would expand the number of CIDs of the TDMPW. The 
TDMPW would be deleted when all calls between the two AGWs are released.


Two questions:

(a) Is it valid this proposed use of TDMPWs?

(b) Each AGW/PE could belong to a different PNO. Is it possible to 
establish a TDMPW between two PEs that belong to different PNO?

Regards,

Javi

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

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

    <meta http-equiv="content-type" content="text/html; charset=ISO-8859-1">
  </head>
  <body bgcolor="#ffffff" text="#000000">
    Recommendations [ITU-T Y.2262; Y.2012] <span id="result_box"
      class="" lang="en"><span class="hps">proposes</span> to <span
        class="hps">support</span> <span class="hps">multichannel</span>
      <span class="hps">ISDN calls</span> <span class="hps">using</span>
      <span class="hps">TDMoIP (UDP/IP TDMPWs)</span></span>. However,
    they do not indicate <span id="result_box" class="" lang="en"><span
        class="hps">what kind of</span> <span class="hps">TDMPW</span><span
        class="">, or</span> <span class="hps">when it must be</span> <span
        class="hps">set up.<br>
        <br>
      </span></span><span id="result_box" class="short_text" lang="en"><span
        class="hps">The scenario</span> <span class="hps">is:</span></span><br>
    <br>
    <tt><code class="moz-txt-verticalline"><span class="moz-txt-tag">|</span>ISDN
        TE<span class="moz-txt-tag">|</span></code> [1xD channel ]
      --&gt; <code class="moz-txt-verticalline"><span
          class="moz-txt-tag">|</span>AGW<span class="moz-txt-tag">|</span></code>&lt;--&gt;&nbsp;
      MGC (Q.931/SIP)&lt;--&gt; <code class="moz-txt-verticalline"><span
          class="moz-txt-tag">|</span>AGW<span class="moz-txt-tag">|</span></code>&lt;--
      [1xD channel ] <code class="moz-txt-verticalline"><span
          class="moz-txt-tag">|</span>ISDN TE<span class="moz-txt-tag">|</span></code></tt>
    <tt><br>
      |_______| [NxB channels] --&gt;
      |___|&lt;--------[TDMPW]--------&gt; |___|&lt;-- [NxB channels]
      |_______|</tt><br>
    <br>
    * AGW (Access Gateway) would also be the PE (Provider Edge) of the
    TDMPW.<br>
    <br>
    <br>
    I understand that:<br>
    <br>
    * Static TDMPWs (SAToP, CESoPSN, TDMoIP AAL1) must be set up before
    calls: so, they are not <span id="result_box" class="" lang="en"><span
        class="hps">a good</span> choice <span class="hps">in this case</span>
      <span class="hps">for reasons of</span> <span class="hps">scalability
        (</span></span>It will require the establishment of a PW with
    every potential destination AGW, which may be in the numbers of tens
    of thousands for a single PNO).<br>
    <br>
    * TDMPW TDMoIP AAL2: I think it is possible to set up the TDMPW <span
      id="result_box" class="" lang="en"><span class="hps">between two</span>
      AGWs <span class="hps">when</span> <span class="hps">the first
        call</span> <span class="hps">occurs</span> <span class="hps">between
        them. </span></span><span id="result_box" class="" lang="en"><span
        class="hps">For second and</span> <span class="hps">subsequent
        calls</span><span>, it</span> <span class="hps">would</span> <span
        class="hps">expand</span> <span class="hps">the number of</span>
      <span class="hps">CIDs of the TDMPW. </span></span><span
      id="result_box" class="" lang="en"><span class="hps">The</span> <span
        class="hps">TDMPW</span> <span class="hps">would be</span> <span
        class="hps">deleted when</span> <span class="hps">all calls</span>
      <span class="hps">between the two</span> <span class="hps">AGWs</span>
      <span class="hps">are released.<br>
        <br>
        <br>
        Two questions:<br>
        <br>
        (a) Is it valid this proposed use of TDMPWs?<br>
        <br>
        (b) </span></span><span id="result_box" class="short_text"
      lang="en"><span class="hps">Each AGW</span>/PE <span class="hps">could
        belong to</span> <span class="hps">a different PNO. </span></span><span
      id="result_box" class="" lang="en"><span class="hps">Is it
        possible to</span> <span class="hps">establish a</span> <span
        class="hps">TDMPW</span> <span class="hps">between two PEs </span><span
        class="hps">that belong to</span> <span class="hps">different</span>
      PNO<span class="hps">?<br>
        <br>
        Regards,<br>
        <br>
        Javi<br>
      </span></span>
  </body>
</html>

--------------020309030703090009040305--

From yaakov_s@rad.com  Tue Dec 13 10:21:40 2011
Return-Path: <yaakov_s@rad.com>
X-Original-To: pwe3@ietfa.amsl.com
Delivered-To: pwe3@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8A40521F8AF1 for <pwe3@ietfa.amsl.com>; Tue, 13 Dec 2011 10:21:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.676
X-Spam-Level: 
X-Spam-Status: No, score=-101.676 tagged_above=-999 required=5 tests=[AWL=-0.578, BAYES_00=-2.599, J_CHICKENPOX_22=0.6, J_CHICKENPOX_63=0.6, MIME_8BIT_HEADER=0.3, UNPARSEABLE_RELAY=0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xDJueZHNJ03H for <pwe3@ietfa.amsl.com>; Tue, 13 Dec 2011 10:21:40 -0800 (PST)
Received: from rad.co.il (mailrelay01.rad.co.il [62.0.23.252]) by ietfa.amsl.com (Postfix) with ESMTP id DE76B21F8ADC for <pwe3@ietf.org>; Tue, 13 Dec 2011 10:21:36 -0800 (PST)
Received: from Internal Mail-Server by MailRelay01 (envelope-from yaakov?s@rad.com) with AES128-SHA encrypted SMTP; 13 Dec 2011 20:13:41 +0200
Received: from EXRAD5.ad.rad.co.il ([192.114.24.28]) by EXRAD5.ad.rad.co.il ([192.114.24.28]) with mapi id 14.01.0323.003; Tue, 13 Dec 2011 20:21:32 +0200
From: Yaakov Stein <yaakov_s@rad.com>
To: =?Windows-1252?Q?Javi_Mu=F1oz?= <javi@trajano.us.es>, "pwe3@ietf.org" <pwe3@ietf.org>
Thread-Topic: [PWE3] Different manipulation of channels in a Nx64 service
Thread-Index: AQHMuPNTu2lISxaldki9+sQRHKsxRZXZaO7QgAAXcICAAJTRoA==
Date: Tue, 13 Dec 2011 18:21:31 +0000
Message-ID: <07F7D7DED63154409F13298786A2ADC9042831D9@EXRAD5.ad.rad.co.il>
References: <4EE63982.7020403@trajano.us.es> <07F7D7DED63154409F13298786A2ADC90427FBB4@EXRAD5.ad.rad.co.il> <4EE73621.1090802@trajano.us.es>
In-Reply-To: <4EE73621.1090802@trajano.us.es>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.115.243.62]
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [PWE3] Different manipulation of channels in a Nx64 service
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pwe3>, <mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pwe3>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 13 Dec 2011 18:21:40 -0000

Javi

If you use Megaco to set up the channels then everything should be fine.

I was thinking about extending the AAL2 TLV to have sub-TLVs per CID
rather than a single encoding field for all CIDs simultaneously.

Although I was editor of Y.1452 I don't remember the clause number
(and I am not on my PC right now).
I think it is the last clause - it talks about muxing RTP flows.
There you can have a RTP header for each CID, and so identify encoding
with higher granularity.

Y(J)S

-----Original Message-----
From: Javi Mu=F1oz [mailto:javi@trajano.us.es]=20
Sent: Tuesday, December 13, 2011 13:25
To: pwe3@ietf.org
Cc: Yaakov Stein
Subject: Re: [PWE3] Different manipulation of channels in a Nx64 service

Yaakov,
> Javi
>
> If I understand you question, you are asking whether an AAL2 TDMoIP PW ca=
n mix channels that
> 1) originated from different TDM trunks,  and
I assumed that this part was possible (we had already discussed in=20
previous post).
> 2) that are encoded with different coding systems (A-law, u-law, VAD, etc=
. etc.)
This was my question.
> Please note, however, that the precise mapping of channels to trunks+time=
slots
> would need to be configured by a management system as the TDM control pro=
tocol extensions
> in RFC 5287 define an optional "mapping base" which only supports the sin=
gle-trunk case.
As we have already spoken on other occasions, my intention is to use=20
Megaco for this mapping of channels to trunks+timeslots.

> Since the channels are completely independent, they can carry anything yo=
u want.
>
> However, the AAL2 control protocol extensions are woefully insufficient t=
o describe
> what is needed here. They indeed contain a VAD indicator and encoding fie=
ld,
> but only for the entire PW, not for individual CIDs.
What extensiones do you mean exactly?

> It would be a trivial exercise to extend the TLV, but it would become ver=
y bulky.
>
> If you absolutely can not configure and need to recognize the channel typ=
e automatically,
My intention was also to use MeGaCo(The node that finishes Q.931/SIP=20
signaling know the type of each channel, so it can indicate to the AGW /=20
PE using Megaco). Do you see any problem with that?

> I can think of two alternatives.
> First, you could rely on the native AAL2 UUI codepoint differentiation de=
fined in I.366.
> Second, you could use the method described in Y.1452 for multiplexing RTP=
 streams
> (at the price of additional overhead).
What method do you mean?(What clause Y.1452 is defined?).

Regards,

Javi
> Y(J)S
>
>
>
>
>
>
> -----Original Message-----
> From: pwe3-bounces@ietf.org [mailto:pwe3-bounces@ietf.org] On Behalf Of J=
avi Mu?oz
> Sent: Monday, December 12, 2011 19:28
> To: pwe3@ietf.org
> Subject: [PWE3] Different manipulation of channels in a Nx64 service
>
> I have the next situation:
>
> ISDN TE_A1<--->  [        ]       [        ]<--->  ISDN TE_A2
> ISDN TE_B1<--->  [        ]       [        ]<--->  ISDN TE_B2
> ISDN TE_C1<--->  [AGW(PE1)]<--->  [AGW(PE2)]<--->  ISDN TE_C2
> ...              [        ]       [        ]
> ISDN TE_D1<--->  [        ]       [        ]<--->  ISDN TE_D2
>
>
> Each AGW finishes several ISDN interfaces (then, several TDM circuits).
>
> * ISDN_TE_A1 has stablished a 64kbps call with ISDN_TE_A2 using the RTP
> codec CLEARMODE.
> * ISDN_TE_B1 has stablished a 64kbps call with ISDN_TE_B2 using the RTP
> codec G.711-u without VAD
> * ISDN_TE_C1 has stablished a 64kbps call with ISDN_TE_C2 using the RTP
> codec G.711-u with VAD
> ...
> * ISDN_TE_D1 has stablished a 64kbps call with ISDN_TE_D2 using the RTP
> codec G.711-u without VAD
>
> (the codec to use for each call would be indicated by an external
> signalling to the TDMPWs, such as Megaco)
>
> Is it possible to use a single TDMoPW TDMoIP AAL2 to emulate all these
> calls?
>
> If this is not possible to use different codec, at least, would it be
> possible to use a single TDMoPW TDMoIP AAL2 to emulate all calls with
> the same type of codec and media manipulation (i.e. calls "ISDN_TE_B1 -
> ISDN_TE_B2" and "ISDN_TE_D1 - ISDN_TE_D2").
>
> NOTE: I propose directly AAL2, and not CESoPSN or TDMoIP AAL2, due to
> they are different calls, so that it is necessary to dynamically modify
> the number of channels, which is only supported by AAL2.
>
>
> Regards,
>
> Javi
>
>
>
>
>
> _______________________________________________
> pwe3 mailing list
> pwe3@ietf.org
> https://www.ietf.org/mailman/listinfo/pwe3
>


From javi@trajano.us.es  Tue Dec 13 11:26:39 2011
Return-Path: <javi@trajano.us.es>
X-Original-To: pwe3@ietfa.amsl.com
Delivered-To: pwe3@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0D56821F8A7E for <pwe3@ietfa.amsl.com>; Tue, 13 Dec 2011 11:26:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.57
X-Spam-Level: 
X-Spam-Status: No, score=-5.57 tagged_above=-999 required=5 tests=[AWL=-0.471,  BAYES_00=-2.599, J_CHICKENPOX_22=0.6, J_CHICKENPOX_63=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 3gpbR2a6etYz for <pwe3@ietfa.amsl.com>; Tue, 13 Dec 2011 11:26:38 -0800 (PST)
Received: from mail.us.es (mail.us.es [193.147.175.20]) by ietfa.amsl.com (Postfix) with ESMTP id 507F321F8A6F for <pwe3@ietf.org>; Tue, 13 Dec 2011 11:26:36 -0800 (PST)
Received: (qmail 17835 invoked from network); 13 Dec 2011 20:26:35 +0100
Received: from unknown (HELO us.es) (192.168.2.11) by us.es with SMTP; 13 Dec 2011 20:26:35 +0100
Received: (qmail 988 invoked by uid 507); 13 Dec 2011 19:26:34 -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/14122.   Clear:RC:1(127.0.0.1):.  Processed in 0.054706 secs); 13 Dec 2011 19:26:34 -0000
Received: from unknown (HELO antivirus1) (127.0.0.1) by us.es with SMTP; 13 Dec 2011 19:26:34 -0000
Received: from 192.168.1.13 (192.168.1.13) by antivirus1 (F-Secure/fsigk_smtp/406/antivirus1); Tue, 13 Dec 2011 20:26:34 +0100 (CET)
X-Virus-Status: clean(F-Secure/fsigk_smtp/406/antivirus1)
Received: (qmail 24865 invoked from network); 13 Dec 2011 20:26:34 +0100
Received: from trajano.us.es (193.147.162.130) by us.es with AES256-SHA encrypted SMTP; 13 Dec 2011 20:26:34 +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 pBDJQYYA009773 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NOT); Tue, 13 Dec 2011 20:26:34 +0100
Message-ID: <4EE7A6EB.8030401@trajano.us.es>
Date: Tue, 13 Dec 2011 20:26:35 +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: "pwe3@ietf.org" <pwe3@ietf.org>
References: <4EE63982.7020403@trajano.us.es>	<07F7D7DED63154409F13298786A2ADC90427FBB4@EXRAD5.ad.rad.co.il> <4EE73621.1090802@trajano.us.es> <07F7D7DED63154409F13298786A2ADC9042831D9@EXRAD5.ad.rad.co.il>
In-Reply-To: <07F7D7DED63154409F13298786A2ADC9042831D9@EXRAD5.ad.rad.co.il>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
Cc: Yaakov Stein <yaakov_s@rad.com>
Subject: Re: [PWE3] Different manipulation of channels in a Nx64 service
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pwe3>, <mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pwe3>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 13 Dec 2011 19:26:39 -0000

Yaakov
> Although I was editor of Y.1452 I don't remember the clause number
> (and I am not on my PC right now).
It is clause 11. It proposes to carry the RTP header in each CID. This 
allows to indicate de Payload Type. But, how may it indicate if using 
G.711 with or without VAD, for instance?
> you could rely on the native AAL2 UUI codepoint differentiation defined in I.366.
>
Regards

Javi
>
> Y(J)S
>
> -----Original Message-----
> From: Javi Muñoz [mailto:javi@trajano.us.es]
> Sent: Tuesday, December 13, 2011 13:25
> To: pwe3@ietf.org
> Cc: Yaakov Stein
> Subject: Re: [PWE3] Different manipulation of channels in a Nx64 service
>
> Yaakov,
>> Javi
>>
>> If I understand you question, you are asking whether an AAL2 TDMoIP PW can mix channels that
>> 1) originated from different TDM trunks,  and
> I assumed that this part was possible (we had already discussed in
> previous post).
>> 2) that are encoded with different coding systems (A-law, u-law, VAD, etc. etc.)
> This was my question.
>> Please note, however, that the precise mapping of channels to trunks+timeslots
>> would need to be configured by a management system as the TDM control protocol extensions
>> in RFC 5287 define an optional "mapping base" which only supports the single-trunk case.
> As we have already spoken on other occasions, my intention is to use
> Megaco for this mapping of channels to trunks+timeslots.
>
>> Since the channels are completely independent, they can carry anything you want.
>>
>> However, the AAL2 control protocol extensions are woefully insufficient to describe
>> what is needed here. They indeed contain a VAD indicator and encoding field,
>> but only for the entire PW, not for individual CIDs.
> What extensiones do you mean exactly?
>
>> It would be a trivial exercise to extend the TLV, but it would become very bulky.
>>
>> If you absolutely can not configure and need to recognize the channel type automatically,
> My intention was also to use MeGaCo(The node that finishes Q.931/SIP
> signaling know the type of each channel, so it can indicate to the AGW /
> PE using Megaco). Do you see any problem with that?
>
>> I can think of two alternatives.
>> First, you could rely on the native AAL2 UUI codepoint differentiation defined in I.366.
>> Second, you could use the method described in Y.1452 for multiplexing RTP streams
>> (at the price of additional overhead).
> What method do you mean?(What clause Y.1452 is defined?).
>
> Regards,
>
> Javi
>> Y(J)S
>>
>>
>>
>>
>>
>>
>> -----Original Message-----
>> From: pwe3-bounces@ietf.org [mailto:pwe3-bounces@ietf.org] On Behalf Of Javi Mu?oz
>> Sent: Monday, December 12, 2011 19:28
>> To: pwe3@ietf.org
>> Subject: [PWE3] Different manipulation of channels in a Nx64 service
>>
>> I have the next situation:
>>
>> ISDN TE_A1<--->   [        ]       [        ]<--->   ISDN TE_A2
>> ISDN TE_B1<--->   [        ]       [        ]<--->   ISDN TE_B2
>> ISDN TE_C1<--->   [AGW(PE1)]<--->   [AGW(PE2)]<--->   ISDN TE_C2
>> ...              [        ]       [        ]
>> ISDN TE_D1<--->   [        ]       [        ]<--->   ISDN TE_D2
>>
>>
>> Each AGW finishes several ISDN interfaces (then, several TDM circuits).
>>
>> * ISDN_TE_A1 has stablished a 64kbps call with ISDN_TE_A2 using the RTP
>> codec CLEARMODE.
>> * ISDN_TE_B1 has stablished a 64kbps call with ISDN_TE_B2 using the RTP
>> codec G.711-u without VAD
>> * ISDN_TE_C1 has stablished a 64kbps call with ISDN_TE_C2 using the RTP
>> codec G.711-u with VAD
>> ...
>> * ISDN_TE_D1 has stablished a 64kbps call with ISDN_TE_D2 using the RTP
>> codec G.711-u without VAD
>>
>> (the codec to use for each call would be indicated by an external
>> signalling to the TDMPWs, such as Megaco)
>>
>> Is it possible to use a single TDMoPW TDMoIP AAL2 to emulate all these
>> calls?
>>
>> If this is not possible to use different codec, at least, would it be
>> possible to use a single TDMoPW TDMoIP AAL2 to emulate all calls with
>> the same type of codec and media manipulation (i.e. calls "ISDN_TE_B1 -
>> ISDN_TE_B2" and "ISDN_TE_D1 - ISDN_TE_D2").
>>
>> NOTE: I propose directly AAL2, and not CESoPSN or TDMoIP AAL2, due to
>> they are different calls, so that it is necessary to dynamically modify
>> the number of channels, which is only supported by AAL2.
>>
>>
>> Regards,
>>
>> Javi
>>
>>
>>
>>
>>
>> _______________________________________________
>> pwe3 mailing list
>> pwe3@ietf.org
>> https://www.ietf.org/mailman/listinfo/pwe3
>>
>


From javi@trajano.us.es  Wed Dec 14 02:52:36 2011
Return-Path: <javi@trajano.us.es>
X-Original-To: pwe3@ietfa.amsl.com
Delivered-To: pwe3@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E5CB021F8B62 for <pwe3@ietfa.amsl.com>; Wed, 14 Dec 2011 02:52:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.954
X-Spam-Level: 
X-Spam-Status: No, score=-4.954 tagged_above=-999 required=5 tests=[AWL=-1.055, BAYES_00=-2.599, J_CHICKENPOX_22=0.6, J_CHICKENPOX_43=0.6, J_CHICKENPOX_54=0.6, J_CHICKENPOX_63=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 D-QYlMDU5+x8 for <pwe3@ietfa.amsl.com>; Wed, 14 Dec 2011 02:52:35 -0800 (PST)
Received: from mail.us.es (mail.us.es [193.147.175.20]) by ietfa.amsl.com (Postfix) with ESMTP id C221921F8B68 for <pwe3@ietf.org>; Wed, 14 Dec 2011 02:52:34 -0800 (PST)
Received: (qmail 23878 invoked from network); 14 Dec 2011 11:52:33 +0100
Received: from unknown (HELO us.es) (192.168.2.11) by us.es with SMTP; 14 Dec 2011 11:52:33 +0100
Received: (qmail 6680 invoked by uid 507); 14 Dec 2011 10:52:31 -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/14123.   Clear:RC:1(127.0.0.1):.  Processed in 0.058446 secs); 14 Dec 2011 10:52:31 -0000
Received: from unknown (HELO antivirus1) (127.0.0.1) by us.es with SMTP; 14 Dec 2011 10:52:31 -0000
Received: from 192.168.1.13 (192.168.1.13) by antivirus1 (F-Secure/fsigk_smtp/406/antivirus1); Wed, 14 Dec 2011 11:52:31 +0100 (CET)
X-Virus-Status: clean(F-Secure/fsigk_smtp/406/antivirus1)
Received: (qmail 23474 invoked from network); 14 Dec 2011 11:52:31 +0100
Received: from trajano.us.es (193.147.162.130) by us.es with AES256-SHA encrypted SMTP; 14 Dec 2011 11:52:31 +0100
Received: from [193.147.162.138] (adriano.us.es [193.147.162.138]) (authenticated bits=0) by trajano.us.es (8.13.8/8.13.8/Debian-3) with ESMTP id pBEAqVNR020890 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NOT); Wed, 14 Dec 2011 11:52:31 +0100
Message-ID: <4EE87FF4.5090704@trajano.us.es>
Date: Wed, 14 Dec 2011 11:52:36 +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: Yaakov Stein <yaakov_s@rad.com>
References: <4EE63982.7020403@trajano.us.es>	<07F7D7DED63154409F13298786A2ADC90427FBB4@EXRAD5.ad.rad.co.il> <4EE73621.1090802@trajano.us.es> <07F7D7DED63154409F13298786A2ADC9042831D9@EXRAD5.ad.rad.co.il>
In-Reply-To: <07F7D7DED63154409F13298786A2ADC9042831D9@EXRAD5.ad.rad.co.il>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
Cc: "pwe3@ietf.org" <pwe3@ietf.org>
Subject: Re: [PWE3] Different manipulation of channels in a Nx64 service
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pwe3>, <mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pwe3>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 14 Dec 2011 10:52:37 -0000

Yaakov,

A question about Y.1452. In the figure 11-1, what exactly is VoIP 
header?: "only the RTP header" or "the RTP, UDP and IP headers"?


And an opinion. If we decide to use a TDMPW for each call:

ISDN TE_A1<--->   [        ]<-TDMPW1->  [        ]<--->   ISDN TE_A2
ISDN TE_B1<--->   [        ]<-TDMPW2->  [        ]<--->   ISDN TE_B2
ISDN TE_C1<--->   [AGW(PE1)]<-TDMPW3->  [AGW(PE2)]<--->   ISDN TE_C2
...
ISDN TE_D1<--->   [        ]<-TDMPWn->  [        ]<--->   ISDN TE_D2


taking into account that:

* They are user calls(thus, they are established / released quite often).

* Each call can be of a different type (voice, VBD, CLEARMODE, ...).

* Each operator (OPN) has many AGWs(not only the two shown in Figure, 
possibily tens of thousands), so that a TE in a AGW may call to a TE in 
any other AGW.

What kind of TDMPW would you use:

* CESoPSN or TDMoIP AAL1

and / or

* TDMoIP AAL2  ?


Regards,

Javi


El 13/12/2011 19:21, Yaakov Stein escribió:
> Javi
>
> If you use Megaco to set up the channels then everything should be fine.
>
> I was thinking about extending the AAL2 TLV to have sub-TLVs per CID
> rather than a single encoding field for all CIDs simultaneously.
>
> Although I was editor of Y.1452 I don't remember the clause number
> (and I am not on my PC right now).
> I think it is the last clause - it talks about muxing RTP flows.
> There you can have a RTP header for each CID, and so identify encoding
> with higher granularity.
>
> Y(J)S
>
> -----Original Message-----
> From: Javi Muñoz [mailto:javi@trajano.us.es]
> Sent: Tuesday, December 13, 2011 13:25
> To: pwe3@ietf.org
> Cc: Yaakov Stein
> Subject: Re: [PWE3] Different manipulation of channels in a Nx64 service
>
> Yaakov,
>> Javi
>>
>> If I understand you question, you are asking whether an AAL2 TDMoIP PW can mix channels that
>> 1) originated from different TDM trunks,  and
> I assumed that this part was possible (we had already discussed in
> previous post).
>> 2) that are encoded with different coding systems (A-law, u-law, VAD, etc. etc.)
> This was my question.
>> Please note, however, that the precise mapping of channels to trunks+timeslots
>> would need to be configured by a management system as the TDM control protocol extensions
>> in RFC 5287 define an optional "mapping base" which only supports the single-trunk case.
> As we have already spoken on other occasions, my intention is to use
> Megaco for this mapping of channels to trunks+timeslots.
>
>> Since the channels are completely independent, they can carry anything you want.
>>
>> However, the AAL2 control protocol extensions are woefully insufficient to describe
>> what is needed here. They indeed contain a VAD indicator and encoding field,
>> but only for the entire PW, not for individual CIDs.
> What extensiones do you mean exactly?
>
>> It would be a trivial exercise to extend the TLV, but it would become very bulky.
>>
>> If you absolutely can not configure and need to recognize the channel type automatically,
> My intention was also to use MeGaCo(The node that finishes Q.931/SIP
> signaling know the type of each channel, so it can indicate to the AGW /
> PE using Megaco). Do you see any problem with that?
>
>> I can think of two alternatives.
>> First, you could rely on the native AAL2 UUI codepoint differentiation defined in I.366.
>> Second, you could use the method described in Y.1452 for multiplexing RTP streams
>> (at the price of additional overhead).
> What method do you mean?(What clause Y.1452 is defined?).
>
> Regards,
>
> Javi
>> Y(J)S
>>
>>
>>
>>
>>
>>
>> -----Original Message-----
>> From: pwe3-bounces@ietf.org [mailto:pwe3-bounces@ietf.org] On Behalf Of Javi Mu?oz
>> Sent: Monday, December 12, 2011 19:28
>> To: pwe3@ietf.org
>> Subject: [PWE3] Different manipulation of channels in a Nx64 service
>>
>> I have the next situation:
>>
>> ISDN TE_A1<--->   [        ]       [        ]<--->   ISDN TE_A2
>> ISDN TE_B1<--->   [        ]       [        ]<--->   ISDN TE_B2
>> ISDN TE_C1<--->   [AGW(PE1)]<--->   [AGW(PE2)]<--->   ISDN TE_C2
>> ...              [        ]       [        ]
>> ISDN TE_D1<--->   [        ]       [        ]<--->   ISDN TE_D2
>>
>>
>> Each AGW finishes several ISDN interfaces (then, several TDM circuits).
>>
>> * ISDN_TE_A1 has stablished a 64kbps call with ISDN_TE_A2 using the RTP
>> codec CLEARMODE.
>> * ISDN_TE_B1 has stablished a 64kbps call with ISDN_TE_B2 using the RTP
>> codec G.711-u without VAD
>> * ISDN_TE_C1 has stablished a 64kbps call with ISDN_TE_C2 using the RTP
>> codec G.711-u with VAD
>> ...
>> * ISDN_TE_D1 has stablished a 64kbps call with ISDN_TE_D2 using the RTP
>> codec G.711-u without VAD
>>
>> (the codec to use for each call would be indicated by an external
>> signalling to the TDMPWs, such as Megaco)
>>
>> Is it possible to use a single TDMoPW TDMoIP AAL2 to emulate all these
>> calls?
>>
>> If this is not possible to use different codec, at least, would it be
>> possible to use a single TDMoPW TDMoIP AAL2 to emulate all calls with
>> the same type of codec and media manipulation (i.e. calls "ISDN_TE_B1 -
>> ISDN_TE_B2" and "ISDN_TE_D1 - ISDN_TE_D2").
>>
>> NOTE: I propose directly AAL2, and not CESoPSN or TDMoIP AAL2, due to
>> they are different calls, so that it is necessary to dynamically modify
>> the number of channels, which is only supported by AAL2.
>>
>>
>> Regards,
>>
>> Javi
>>
>>
>>
>>
>>
>> _______________________________________________
>> pwe3 mailing list
>> pwe3@ietf.org
>> https://www.ietf.org/mailman/listinfo/pwe3
>>
>


From javi@trajano.us.es  Thu Dec 15 09:52:28 2011
Return-Path: <javi@trajano.us.es>
X-Original-To: pwe3@ietfa.amsl.com
Delivered-To: pwe3@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9D5D921F8669 for <pwe3@ietfa.amsl.com>; Thu, 15 Dec 2011 09:52:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.919
X-Spam-Level: 
X-Spam-Status: No, score=-4.919 tagged_above=-999 required=5 tests=[AWL=-1.020, BAYES_00=-2.599, J_CHICKENPOX_22=0.6, J_CHICKENPOX_43=0.6, J_CHICKENPOX_54=0.6, J_CHICKENPOX_63=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 FgTsU-xg-02p for <pwe3@ietfa.amsl.com>; Thu, 15 Dec 2011 09:52:25 -0800 (PST)
Received: from mail.us.es (mail.us.es [193.147.175.20]) by ietfa.amsl.com (Postfix) with ESMTP id 17A3321F85FF for <pwe3@ietf.org>; Thu, 15 Dec 2011 09:52:23 -0800 (PST)
Received: (qmail 8486 invoked from network); 15 Dec 2011 18:52:20 +0100
Received: from unknown (HELO us.es) (192.168.2.13) by us.es with SMTP; 15 Dec 2011 18:52:20 +0100
Received: (qmail 18422 invoked by uid 507); 15 Dec 2011 17:52: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/14124.   Clear:RC:1(127.0.0.1):.  Processed in 0.055942 secs); 15 Dec 2011 17:52:17 -0000
Received: from unknown (HELO antivirus3) (127.0.0.1) by us.es with SMTP; 15 Dec 2011 17:52:17 -0000
Received: from 192.168.1.13 (192.168.1.13) by antivirus3 (F-Secure/fsigk_smtp/406/antivirus3); Thu, 15 Dec 2011 18:52:17 +0100 (CET)
X-Virus-Status: clean(F-Secure/fsigk_smtp/406/antivirus3)
Received: (qmail 12815 invoked from network); 15 Dec 2011 18:52:17 +0100
Received: from trajano.us.es (193.147.162.130) by us.es with AES256-SHA encrypted SMTP; 15 Dec 2011 18:52: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 pBFHqFEo014849 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NOT); Thu, 15 Dec 2011 18:52:16 +0100
Message-ID: <4EEA33DA.5070709@trajano.us.es>
Date: Thu, 15 Dec 2011 18:52:26 +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: "pwe3@ietf.org" <pwe3@ietf.org>
References: <4EE63982.7020403@trajano.us.es>	<07F7D7DED63154409F13298786A2ADC90427FBB4@EXRAD5.ad.rad.co.il>	<4EE73621.1090802@trajano.us.es>	<07F7D7DED63154409F13298786A2ADC9042831D9@EXRAD5.ad.rad.co.il> <4EE87FF4.5090704@trajano.us.es>
In-Reply-To: <4EE87FF4.5090704@trajano.us.es>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
Cc: Yaakov Stein <yaakov_s@rad.com>
Subject: Re: [PWE3] Different manipulation of channels in a Nx64 service
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pwe3>, <mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pwe3>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Dec 2011 17:52:30 -0000

For the opinion about using CESoPSN/TDMoIP AAL1 and/or TDMoIP AAL2, I 
would add that:

* Some calls may be switched (SVCs) and others permanent (PVCs).


Also, I'd like to know your opinion whether you think is better a TDMPW 
per call, or use a TDMPW for multiple calls (muxing).

Regards,

Javi


El 14/12/2011 11:52, Javi Muñoz escribió:
> Yaakov,
>
> A question about Y.1452. In the figure 11-1, what exactly is VoIP 
> header?: "only the RTP header" or "the RTP, UDP and IP headers"?
>
>
> And an opinion. If we decide to use a TDMPW for each call:
>
> ISDN TE_A1<--->   [        ]<-TDMPW1->  [        ]<--->   ISDN TE_A2
> ISDN TE_B1<--->   [        ]<-TDMPW2->  [        ]<--->   ISDN TE_B2
> ISDN TE_C1<--->   [AGW(PE1)]<-TDMPW3->  [AGW(PE2)]<--->   ISDN TE_C2
> ...
> ISDN TE_D1<--->   [        ]<-TDMPWn->  [        ]<--->   ISDN TE_D2
>
>
> taking into account that:
>
> * They are user calls(thus, they are established / released quite often).
>
> * Each call can be of a different type (voice, VBD, CLEARMODE, ...).
>
> * Each operator (OPN) has many AGWs(not only the two shown in Figure, 
> possibily tens of thousands), so that a TE in a AGW may call to a TE 
> in any other AGW.
>
> What kind of TDMPW would you use:
>
> * CESoPSN or TDMoIP AAL1
>
> and / or
>
> * TDMoIP AAL2  ?
>
>
> Regards,
>
> Javi
>
>
> El 13/12/2011 19:21, Yaakov Stein escribió:
>> Javi
>>
>> If you use Megaco to set up the channels then everything should be fine.
>>
>> I was thinking about extending the AAL2 TLV to have sub-TLVs per CID
>> rather than a single encoding field for all CIDs simultaneously.
>>
>> Although I was editor of Y.1452 I don't remember the clause number
>> (and I am not on my PC right now).
>> I think it is the last clause - it talks about muxing RTP flows.
>> There you can have a RTP header for each CID, and so identify encoding
>> with higher granularity.
>>
>> Y(J)S
>>
>> -----Original Message-----
>> From: Javi Muñoz [mailto:javi@trajano.us.es]
>> Sent: Tuesday, December 13, 2011 13:25
>> To: pwe3@ietf.org
>> Cc: Yaakov Stein
>> Subject: Re: [PWE3] Different manipulation of channels in a Nx64 service
>>
>> Yaakov,
>>> Javi
>>>
>>> If I understand you question, you are asking whether an AAL2 TDMoIP 
>>> PW can mix channels that
>>> 1) originated from different TDM trunks,  and
>> I assumed that this part was possible (we had already discussed in
>> previous post).
>>> 2) that are encoded with different coding systems (A-law, u-law, 
>>> VAD, etc. etc.)
>> This was my question.
>>> Please note, however, that the precise mapping of channels to 
>>> trunks+timeslots
>>> would need to be configured by a management system as the TDM 
>>> control protocol extensions
>>> in RFC 5287 define an optional "mapping base" which only supports 
>>> the single-trunk case.
>> As we have already spoken on other occasions, my intention is to use
>> Megaco for this mapping of channels to trunks+timeslots.
>>
>>> Since the channels are completely independent, they can carry 
>>> anything you want.
>>>
>>> However, the AAL2 control protocol extensions are woefully 
>>> insufficient to describe
>>> what is needed here. They indeed contain a VAD indicator and 
>>> encoding field,
>>> but only for the entire PW, not for individual CIDs.
>> What extensiones do you mean exactly?
>>
>>> It would be a trivial exercise to extend the TLV, but it would 
>>> become very bulky.
>>>
>>> If you absolutely can not configure and need to recognize the 
>>> channel type automatically,
>> My intention was also to use MeGaCo(The node that finishes Q.931/SIP
>> signaling know the type of each channel, so it can indicate to the AGW /
>> PE using Megaco). Do you see any problem with that?
>>
>>> I can think of two alternatives.
>>> First, you could rely on the native AAL2 UUI codepoint 
>>> differentiation defined in I.366.
>>> Second, you could use the method described in Y.1452 for 
>>> multiplexing RTP streams
>>> (at the price of additional overhead).
>> What method do you mean?(What clause Y.1452 is defined?).
>>
>> Regards,
>>
>> Javi
>>> Y(J)S
>>>
>>>
>>>
>>>
>>>
>>>
>>> -----Original Message-----
>>> From: pwe3-bounces@ietf.org [mailto:pwe3-bounces@ietf.org] On Behalf 
>>> Of Javi Mu?oz
>>> Sent: Monday, December 12, 2011 19:28
>>> To: pwe3@ietf.org
>>> Subject: [PWE3] Different manipulation of channels in a Nx64 service
>>>
>>> I have the next situation:
>>>
>>> ISDN TE_A1<--->   [        ]       [        ]<--->   ISDN TE_A2
>>> ISDN TE_B1<--->   [        ]       [        ]<--->   ISDN TE_B2
>>> ISDN TE_C1<--->   [AGW(PE1)]<--->   [AGW(PE2)]<--->   ISDN TE_C2
>>> ...              [        ]       [        ]
>>> ISDN TE_D1<--->   [        ]       [        ]<--->   ISDN TE_D2
>>>
>>>
>>> Each AGW finishes several ISDN interfaces (then, several TDM circuits).
>>>
>>> * ISDN_TE_A1 has stablished a 64kbps call with ISDN_TE_A2 using the RTP
>>> codec CLEARMODE.
>>> * ISDN_TE_B1 has stablished a 64kbps call with ISDN_TE_B2 using the RTP
>>> codec G.711-u without VAD
>>> * ISDN_TE_C1 has stablished a 64kbps call with ISDN_TE_C2 using the RTP
>>> codec G.711-u with VAD
>>> ...
>>> * ISDN_TE_D1 has stablished a 64kbps call with ISDN_TE_D2 using the RTP
>>> codec G.711-u without VAD
>>>
>>> (the codec to use for each call would be indicated by an external
>>> signalling to the TDMPWs, such as Megaco)
>>>
>>> Is it possible to use a single TDMoPW TDMoIP AAL2 to emulate all these
>>> calls?
>>>
>>> If this is not possible to use different codec, at least, would it be
>>> possible to use a single TDMoPW TDMoIP AAL2 to emulate all calls with
>>> the same type of codec and media manipulation (i.e. calls "ISDN_TE_B1 -
>>> ISDN_TE_B2" and "ISDN_TE_D1 - ISDN_TE_D2").
>>>
>>> NOTE: I propose directly AAL2, and not CESoPSN or TDMoIP AAL2, due to
>>> they are different calls, so that it is necessary to dynamically modify
>>> the number of channels, which is only supported by AAL2.
>>>
>>>
>>> Regards,
>>>
>>> Javi
>>>
>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> pwe3 mailing list
>>> pwe3@ietf.org
>>> https://www.ietf.org/mailman/listinfo/pwe3
>>>
>>
>
> _______________________________________________
> pwe3 mailing list
> pwe3@ietf.org
> https://www.ietf.org/mailman/listinfo/pwe3
>


From javi@trajano.us.es  Fri Dec 16 03:20:19 2011
Return-Path: <javi@trajano.us.es>
X-Original-To: pwe3@ietfa.amsl.com
Delivered-To: pwe3@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E3F0F21F8B30 for <pwe3@ietfa.amsl.com>; Fri, 16 Dec 2011 03:20:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.586
X-Spam-Level: 
X-Spam-Status: No, score=-4.586 tagged_above=-999 required=5 tests=[AWL=-1.287, BAYES_00=-2.599, J_CHICKENPOX_22=0.6, J_CHICKENPOX_43=0.6, J_CHICKENPOX_44=0.6, J_CHICKENPOX_54=0.6, J_CHICKENPOX_63=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 nfqvUgR5QQ4c for <pwe3@ietfa.amsl.com>; Fri, 16 Dec 2011 03:20:19 -0800 (PST)
Received: from mail.us.es (mail.us.es [193.147.175.20]) by ietfa.amsl.com (Postfix) with ESMTP id 5ADBE21F8B31 for <pwe3@ietf.org>; Fri, 16 Dec 2011 03:20:18 -0800 (PST)
Received: (qmail 2508 invoked from network); 16 Dec 2011 12:20:14 +0100
Received: from unknown (HELO us.es) (192.168.2.12) by us.es with SMTP; 16 Dec 2011 12:20:14 +0100
Received: (qmail 7593 invoked by uid 507); 16 Dec 2011 11:20:10 -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/14125.   Clear:RC:1(127.0.0.1):.  Processed in 0.058549 secs); 16 Dec 2011 11:20:10 -0000
Received: from unknown (HELO antivirus2) (127.0.0.1) by us.es with SMTP; 16 Dec 2011 11:20:10 -0000
Received: from 192.168.1.13 (192.168.1.13) by antivirus2 (F-Secure/fsigk_smtp/406/antivirus2); Fri, 16 Dec 2011 12:20:10 +0100 (CET)
X-Virus-Status: clean(F-Secure/fsigk_smtp/406/antivirus2)
Received: (qmail 4558 invoked from network); 16 Dec 2011 12:20:10 +0100
Received: from trajano.us.es (193.147.162.130) by us.es with AES256-SHA encrypted SMTP; 16 Dec 2011 12:20:10 +0100
Received: from [193.147.162.138] (adriano.us.es [193.147.162.138]) (authenticated bits=0) by trajano.us.es (8.13.8/8.13.8/Debian-3) with ESMTP id pBGBK8VM027941 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NOT); Fri, 16 Dec 2011 12:20:09 +0100
Message-ID: <4EEB2976.90707@trajano.us.es>
Date: Fri, 16 Dec 2011 12:20:22 +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: pwe3@ietf.org
References: <4EE63982.7020403@trajano.us.es>	<07F7D7DED63154409F13298786A2ADC90427FBB4@EXRAD5.ad.rad.co.il>	<4EE73621.1090802@trajano.us.es>	<07F7D7DED63154409F13298786A2ADC9042831D9@EXRAD5.ad.rad.co.il>	<4EE87FF4.5090704@trajano.us.es> <4EEA33DA.5070709@trajano.us.es>
In-Reply-To: <4EEA33DA.5070709@trajano.us.es>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
Cc: Yaakov Stein <yaakov_s@rad.com>
Subject: Re: [PWE3] Different manipulation of channels in a Nx64 service
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pwe3>, <mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pwe3>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 16 Dec 2011 11:20:20 -0000

Yaakov,

And an additional question.

When using a TDMPW TDMoIP AAL2 per call(mono or multichannel), I think 
it might be better to simply use RTP. In a ISDN multichannel call, the 
"N" 1x64 kbps-channels may be modeled as a virtual single channel of 
rate Nx64 kbps, then as a single stream of media:

Media of "stream Nx64"
         RTP
         UDP
         IP


TDMoIP AAL2 would keep the identification of the channel to which each 
sample belongs (but it is not necessary to be a single stream carrried 
over "N" channels).

If this is correct, then the RTP solution here would be better to have 
less overhead.

Regards,

Javi


El 15/12/2011 18:52, Javi Muñoz escribió:
> For the opinion about using CESoPSN/TDMoIP AAL1 and/or TDMoIP AAL2, I 
> would add that:
>
> * Some calls may be switched (SVCs) and others permanent (PVCs).
>
>
> Also, I'd like to know your opinion whether you think is better a 
> TDMPW per call, or use a TDMPW for multiple calls (muxing).
>
> Regards,
>
> Javi
>
>
> El 14/12/2011 11:52, Javi Muñoz escribió:
>> Yaakov,
>>
>> A question about Y.1452. In the figure 11-1, what exactly is VoIP 
>> header?: "only the RTP header" or "the RTP, UDP and IP headers"?
>>
>>
>> And an opinion. If we decide to use a TDMPW for each call:
>>
>> ISDN TE_A1<--->   [        ]<-TDMPW1->  [        ]<--->   ISDN TE_A2
>> ISDN TE_B1<--->   [        ]<-TDMPW2->  [        ]<--->   ISDN TE_B2
>> ISDN TE_C1<--->   [AGW(PE1)]<-TDMPW3->  [AGW(PE2)]<--->   ISDN TE_C2
>> ...
>> ISDN TE_D1<--->   [        ]<-TDMPWn->  [        ]<--->   ISDN TE_D2
>>
>>
>> taking into account that:
>>
>> * They are user calls(thus, they are established / released quite 
>> often).
>>
>> * Each call can be of a different type (voice, VBD, CLEARMODE, ...).
>>
>> * Each operator (OPN) has many AGWs(not only the two shown in Figure, 
>> possibily tens of thousands), so that a TE in a AGW may call to a TE 
>> in any other AGW.
>>
>> What kind of TDMPW would you use:
>>
>> * CESoPSN or TDMoIP AAL1
>>
>> and / or
>>
>> * TDMoIP AAL2  ?
>>
>>
>> Regards,
>>
>> Javi
>>
>>
>> El 13/12/2011 19:21, Yaakov Stein escribió:
>>> Javi
>>>
>>> If you use Megaco to set up the channels then everything should be 
>>> fine.
>>>
>>> I was thinking about extending the AAL2 TLV to have sub-TLVs per CID
>>> rather than a single encoding field for all CIDs simultaneously.
>>>
>>> Although I was editor of Y.1452 I don't remember the clause number
>>> (and I am not on my PC right now).
>>> I think it is the last clause - it talks about muxing RTP flows.
>>> There you can have a RTP header for each CID, and so identify encoding
>>> with higher granularity.
>>>
>>> Y(J)S
>>>
>>> -----Original Message-----
>>> From: Javi Muñoz [mailto:javi@trajano.us.es]
>>> Sent: Tuesday, December 13, 2011 13:25
>>> To: pwe3@ietf.org
>>> Cc: Yaakov Stein
>>> Subject: Re: [PWE3] Different manipulation of channels in a Nx64 
>>> service
>>>
>>> Yaakov,
>>>> Javi
>>>>
>>>> If I understand you question, you are asking whether an AAL2 TDMoIP 
>>>> PW can mix channels that
>>>> 1) originated from different TDM trunks,  and
>>> I assumed that this part was possible (we had already discussed in
>>> previous post).
>>>> 2) that are encoded with different coding systems (A-law, u-law, 
>>>> VAD, etc. etc.)
>>> This was my question.
>>>> Please note, however, that the precise mapping of channels to 
>>>> trunks+timeslots
>>>> would need to be configured by a management system as the TDM 
>>>> control protocol extensions
>>>> in RFC 5287 define an optional "mapping base" which only supports 
>>>> the single-trunk case.
>>> As we have already spoken on other occasions, my intention is to use
>>> Megaco for this mapping of channels to trunks+timeslots.
>>>
>>>> Since the channels are completely independent, they can carry 
>>>> anything you want.
>>>>
>>>> However, the AAL2 control protocol extensions are woefully 
>>>> insufficient to describe
>>>> what is needed here. They indeed contain a VAD indicator and 
>>>> encoding field,
>>>> but only for the entire PW, not for individual CIDs.
>>> What extensiones do you mean exactly?
>>>
>>>> It would be a trivial exercise to extend the TLV, but it would 
>>>> become very bulky.
>>>>
>>>> If you absolutely can not configure and need to recognize the 
>>>> channel type automatically,
>>> My intention was also to use MeGaCo(The node that finishes Q.931/SIP
>>> signaling know the type of each channel, so it can indicate to the 
>>> AGW /
>>> PE using Megaco). Do you see any problem with that?
>>>
>>>> I can think of two alternatives.
>>>> First, you could rely on the native AAL2 UUI codepoint 
>>>> differentiation defined in I.366.
>>>> Second, you could use the method described in Y.1452 for 
>>>> multiplexing RTP streams
>>>> (at the price of additional overhead).
>>> What method do you mean?(What clause Y.1452 is defined?).
>>>
>>> Regards,
>>>
>>> Javi
>>>> Y(J)S
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> -----Original Message-----
>>>> From: pwe3-bounces@ietf.org [mailto:pwe3-bounces@ietf.org] On 
>>>> Behalf Of Javi Mu?oz
>>>> Sent: Monday, December 12, 2011 19:28
>>>> To: pwe3@ietf.org
>>>> Subject: [PWE3] Different manipulation of channels in a Nx64 service
>>>>
>>>> I have the next situation:
>>>>
>>>> ISDN TE_A1<--->   [        ]       [        ]<--->   ISDN TE_A2
>>>> ISDN TE_B1<--->   [        ]       [        ]<--->   ISDN TE_B2
>>>> ISDN TE_C1<--->   [AGW(PE1)]<--->   [AGW(PE2)]<--->   ISDN TE_C2
>>>> ...              [        ]       [        ]
>>>> ISDN TE_D1<--->   [        ]       [        ]<--->   ISDN TE_D2
>>>>
>>>>
>>>> Each AGW finishes several ISDN interfaces (then, several TDM 
>>>> circuits).
>>>>
>>>> * ISDN_TE_A1 has stablished a 64kbps call with ISDN_TE_A2 using the 
>>>> RTP
>>>> codec CLEARMODE.
>>>> * ISDN_TE_B1 has stablished a 64kbps call with ISDN_TE_B2 using the 
>>>> RTP
>>>> codec G.711-u without VAD
>>>> * ISDN_TE_C1 has stablished a 64kbps call with ISDN_TE_C2 using the 
>>>> RTP
>>>> codec G.711-u with VAD
>>>> ...
>>>> * ISDN_TE_D1 has stablished a 64kbps call with ISDN_TE_D2 using the 
>>>> RTP
>>>> codec G.711-u without VAD
>>>>
>>>> (the codec to use for each call would be indicated by an external
>>>> signalling to the TDMPWs, such as Megaco)
>>>>
>>>> Is it possible to use a single TDMoPW TDMoIP AAL2 to emulate all these
>>>> calls?
>>>>
>>>> If this is not possible to use different codec, at least, would it be
>>>> possible to use a single TDMoPW TDMoIP AAL2 to emulate all calls with
>>>> the same type of codec and media manipulation (i.e. calls 
>>>> "ISDN_TE_B1 -
>>>> ISDN_TE_B2" and "ISDN_TE_D1 - ISDN_TE_D2").
>>>>
>>>> NOTE: I propose directly AAL2, and not CESoPSN or TDMoIP AAL2, due to
>>>> they are different calls, so that it is necessary to dynamically 
>>>> modify
>>>> the number of channels, which is only supported by AAL2.
>>>>
>>>>
>>>> Regards,
>>>>
>>>> Javi
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> pwe3 mailing list
>>>> pwe3@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/pwe3
>>>>
>>>
>>
>> _______________________________________________
>> pwe3 mailing list
>> pwe3@ietf.org
>> https://www.ietf.org/mailman/listinfo/pwe3
>>
>
> _______________________________________________
> pwe3 mailing list
> pwe3@ietf.org
> https://www.ietf.org/mailman/listinfo/pwe3
>


From javi@trajano.us.es  Fri Dec 16 10:16:14 2011
Return-Path: <javi@trajano.us.es>
X-Original-To: pwe3@ietfa.amsl.com
Delivered-To: pwe3@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0907121F8A66 for <pwe3@ietfa.amsl.com>; Fri, 16 Dec 2011 10:16:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.046
X-Spam-Level: 
X-Spam-Status: No, score=-6.046 tagged_above=-999 required=5 tests=[AWL=0.253,  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 0E2IjV1ZdBg9 for <pwe3@ietfa.amsl.com>; Fri, 16 Dec 2011 10:16:13 -0800 (PST)
Received: from mail.us.es (mail.us.es [193.147.175.20]) by ietfa.amsl.com (Postfix) with ESMTP id 095B421F8A62 for <pwe3@ietf.org>; Fri, 16 Dec 2011 10:16:12 -0800 (PST)
Received: (qmail 12574 invoked from network); 16 Dec 2011 19:16:11 +0100
Received: from unknown (HELO us.es) (192.168.2.11) by us.es with SMTP; 16 Dec 2011 19:16:11 +0100
Received: (qmail 29456 invoked by uid 507); 16 Dec 2011 18:16:09 -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/14128.   Clear:RC:1(127.0.0.1):.  Processed in 0.038499 secs); 16 Dec 2011 18:16:09 -0000
Received: from unknown (HELO antivirus1) (127.0.0.1) by us.es with SMTP; 16 Dec 2011 18:16:09 -0000
Received: from 192.168.1.13 (192.168.1.13) by antivirus1 (F-Secure/fsigk_smtp/406/antivirus1); Fri, 16 Dec 2011 19:16:09 +0100 (CET)
X-Virus-Status: clean(F-Secure/fsigk_smtp/406/antivirus1)
Received: (qmail 11379 invoked from network); 16 Dec 2011 19:16:09 +0100
Received: from trajano.us.es (193.147.162.130) by us.es with AES256-SHA encrypted SMTP; 16 Dec 2011 19:16:09 +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 pBGIG89b002999 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NOT); Fri, 16 Dec 2011 19:16:08 +0100
Message-ID: <4EEB8AF7.10702@trajano.us.es>
Date: Fri, 16 Dec 2011 19:16:23 +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: Yaakov Stein <yaakov_s@rad.com>
References: <4E96D20D.9050202@trajano.us.es> <07F7D7DED63154409F13298786A2ADC9040B46BC@EXRAD5.ad.rad.co.il>
In-Reply-To: <07F7D7DED63154409F13298786A2ADC9040B46BC@EXRAD5.ad.rad.co.il>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "pwe3@ietf.org" <pwe3@ietf.org>
Subject: Re: [PWE3] TDMoIP AAL2 and TSSI structures
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pwe3>, <mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pwe3>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 16 Dec 2011 18:16:14 -0000

Yaakov,

You wrote me:

> When using TDMoIP in AAL2 mode, sample order is guaranteed
>
> [Javi] ITU-T I.140 defines:
>
> + TSSI structure (time slot sequence integrity): if a sample "bi" is
> send and, later, a second sample "bk" (for any two different channels of
> an aggregate of channels, B1 and B2), "bi" always come first.
>
>
> If we use a TDMoPW TDMoIP AAL2 to emulate the aggregate of that channels
> (B1 and B2), would TSSI structure be guaranteed?


I agreed with you. However, after thinking more slowly, I have some doubts.

TSSI requires that if we have two channels B1 and B2 in CEa (source CE 
source) and CEb (destination CE) then:

* if in CE1: a sample "b1a" is send on channel B1 and, later, a second 
sample "b2a" is send on channel B2

* then, in CE2: sample "b1a" must reach CE2 (on its channel B1) before 
"b2a" (on its channel B2)

The same for other samples "b1b", "b2b" sent later.


          b1a          b1b
     B1 ==|============|==================
CE1       \  b2a       \      b2b
     B2 ====\=|==========\======|=========
             \  \         \      \
              \   \         \      \
               \b1a  \        \b1b  \
     B1 ========|=====\========|=====\====
CE2                    \ b2a         \b2b
     B2 ==================|============|==


In TDMPW AAL2-mode, we migth have a TDMPW packet with the payload:

TDMPW Payload:        [CPS packet of B1][CPS packet of B2]

where:

[CPS packet of B1] = [CPS header, with CID=B1] [CPS payload: samples 
b1a, b1b, b1c, b1d]

[CPS packet of B2] = [CPS header, with CID=B1] [CPS payload: samples 
b2a, b2b, b2c, b2d]

So, I understand that CEs first read all the samples of "CPS packet of 
B1" (so "b1a, b1b, ...") and later, all the samples of "CPS packet of 
B2" (so "b2a, b2b, ..."), which does not coincide with the delivery 
order (b1a, b2a, b1b, b2b, b1c, ...)

Am I wrong?

Regards,

Javi



From yaakov_s@rad.com  Sun Dec 18 01:39:10 2011
Return-Path: <yaakov_s@rad.com>
X-Original-To: pwe3@ietfa.amsl.com
Delivered-To: pwe3@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5C8B021F853B for <pwe3@ietfa.amsl.com>; Sun, 18 Dec 2011 01:39:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -98.498
X-Spam-Level: 
X-Spam-Status: No, score=-98.498 tagged_above=-999 required=5 tests=[BAYES_50=0.001, J_CHICKENPOX_22=0.6, J_CHICKENPOX_63=0.6, MIME_8BIT_HEADER=0.3, UNPARSEABLE_RELAY=0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1ph8p7GgGfgW for <pwe3@ietfa.amsl.com>; Sun, 18 Dec 2011 01:39:09 -0800 (PST)
Received: from rad.co.il (mailrelay02.rad.co.il [62.0.23.237]) by ietfa.amsl.com (Postfix) with ESMTP id 05C1721F8531 for <pwe3@ietf.org>; Sun, 18 Dec 2011 01:39:06 -0800 (PST)
Received: from Internal Mail-Server by MailRelay02 (envelope-from yaakov?s@rad.com) with AES128-SHA encrypted SMTP; 18 Dec 2011 11:16:29 +0200
Received: from EXRAD5.ad.rad.co.il ([192.114.24.28]) by EXRAD5.ad.rad.co.il ([192.114.24.28]) with mapi id 14.01.0323.003; Sun, 18 Dec 2011 11:38:53 +0200
From: Yaakov Stein <yaakov_s@rad.com>
To: =?Windows-1252?Q?Javi_Mu=F1oz?= <javi@trajano.us.es>, "pwe3@ietf.org" <pwe3@ietf.org>
Thread-Topic: [PWE3] Different manipulation of channels in a Nx64 service
Thread-Index: AQHMuPNTu2lISxaldki9+sQRHKsxRZXZaO7QgAAXcICAAJTRoP//8aSAgAdY5xA=
Date: Sun, 18 Dec 2011 09:38:52 +0000
Message-ID: <07F7D7DED63154409F13298786A2ADC904299BCE@EXRAD5.ad.rad.co.il>
References: <4EE63982.7020403@trajano.us.es> <07F7D7DED63154409F13298786A2ADC90427FBB4@EXRAD5.ad.rad.co.il> <4EE73621.1090802@trajano.us.es> <07F7D7DED63154409F13298786A2ADC9042831D9@EXRAD5.ad.rad.co.il> <4EE7A6EB.8030401@trajano.us.es>
In-Reply-To: <4EE7A6EB.8030401@trajano.us.es>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [172.17.170.143]
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [PWE3] Different manipulation of channels in a Nx64 service
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pwe3>, <mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pwe3>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 18 Dec 2011 09:39:10 -0000

See RFCs 3551 and 3389.

Y(J)S

-----Original Message-----
From: Javi Mu=F1oz [mailto:javi@trajano.us.es]=20
Sent: Tuesday, December 13, 2011 21:27
To: pwe3@ietf.org
Cc: Yaakov Stein
Subject: Re: [PWE3] Different manipulation of channels in a Nx64 service

Yaakov
> Although I was editor of Y.1452 I don't remember the clause number
> (and I am not on my PC right now).
It is clause 11. It proposes to carry the RTP header in each CID. This=20
allows to indicate de Payload Type. But, how may it indicate if using=20
G.711 with or without VAD, for instance?
> you could rely on the native AAL2 UUI codepoint differentiation defined i=
n I.366.
>
Regards

Javi
>
> Y(J)S
>
> -----Original Message-----
> From: Javi Mu=F1oz [mailto:javi@trajano.us.es]
> Sent: Tuesday, December 13, 2011 13:25
> To: pwe3@ietf.org
> Cc: Yaakov Stein
> Subject: Re: [PWE3] Different manipulation of channels in a Nx64 service
>
> Yaakov,
>> Javi
>>
>> If I understand you question, you are asking whether an AAL2 TDMoIP PW c=
an mix channels that
>> 1) originated from different TDM trunks,  and
> I assumed that this part was possible (we had already discussed in
> previous post).
>> 2) that are encoded with different coding systems (A-law, u-law, VAD, et=
c. etc.)
> This was my question.
>> Please note, however, that the precise mapping of channels to trunks+tim=
eslots
>> would need to be configured by a management system as the TDM control pr=
otocol extensions
>> in RFC 5287 define an optional "mapping base" which only supports the si=
ngle-trunk case.
> As we have already spoken on other occasions, my intention is to use
> Megaco for this mapping of channels to trunks+timeslots.
>
>> Since the channels are completely independent, they can carry anything y=
ou want.
>>
>> However, the AAL2 control protocol extensions are woefully insufficient =
to describe
>> what is needed here. They indeed contain a VAD indicator and encoding fi=
eld,
>> but only for the entire PW, not for individual CIDs.
> What extensiones do you mean exactly?
>
>> It would be a trivial exercise to extend the TLV, but it would become ve=
ry bulky.
>>
>> If you absolutely can not configure and need to recognize the channel ty=
pe automatically,
> My intention was also to use MeGaCo(The node that finishes Q.931/SIP
> signaling know the type of each channel, so it can indicate to the AGW /
> PE using Megaco). Do you see any problem with that?
>
>> I can think of two alternatives.
>> First, you could rely on the native AAL2 UUI codepoint differentiation d=
efined in I.366.
>> Second, you could use the method described in Y.1452 for multiplexing RT=
P streams
>> (at the price of additional overhead).
> What method do you mean?(What clause Y.1452 is defined?).
>
> Regards,
>
> Javi
>> Y(J)S
>>
>>
>>
>>
>>
>>
>> -----Original Message-----
>> From: pwe3-bounces@ietf.org [mailto:pwe3-bounces@ietf.org] On Behalf Of =
Javi Mu?oz
>> Sent: Monday, December 12, 2011 19:28
>> To: pwe3@ietf.org
>> Subject: [PWE3] Different manipulation of channels in a Nx64 service
>>
>> I have the next situation:
>>
>> ISDN TE_A1<--->   [        ]       [        ]<--->   ISDN TE_A2
>> ISDN TE_B1<--->   [        ]       [        ]<--->   ISDN TE_B2
>> ISDN TE_C1<--->   [AGW(PE1)]<--->   [AGW(PE2)]<--->   ISDN TE_C2
>> ...              [        ]       [        ]
>> ISDN TE_D1<--->   [        ]       [        ]<--->   ISDN TE_D2
>>
>>
>> Each AGW finishes several ISDN interfaces (then, several TDM circuits).
>>
>> * ISDN_TE_A1 has stablished a 64kbps call with ISDN_TE_A2 using the RTP
>> codec CLEARMODE.
>> * ISDN_TE_B1 has stablished a 64kbps call with ISDN_TE_B2 using the RTP
>> codec G.711-u without VAD
>> * ISDN_TE_C1 has stablished a 64kbps call with ISDN_TE_C2 using the RTP
>> codec G.711-u with VAD
>> ...
>> * ISDN_TE_D1 has stablished a 64kbps call with ISDN_TE_D2 using the RTP
>> codec G.711-u without VAD
>>
>> (the codec to use for each call would be indicated by an external
>> signalling to the TDMPWs, such as Megaco)
>>
>> Is it possible to use a single TDMoPW TDMoIP AAL2 to emulate all these
>> calls?
>>
>> If this is not possible to use different codec, at least, would it be
>> possible to use a single TDMoPW TDMoIP AAL2 to emulate all calls with
>> the same type of codec and media manipulation (i.e. calls "ISDN_TE_B1 -
>> ISDN_TE_B2" and "ISDN_TE_D1 - ISDN_TE_D2").
>>
>> NOTE: I propose directly AAL2, and not CESoPSN or TDMoIP AAL2, due to
>> they are different calls, so that it is necessary to dynamically modify
>> the number of channels, which is only supported by AAL2.
>>
>>
>> Regards,
>>
>> Javi
>>
>>
>>
>>
>>
>> _______________________________________________
>> pwe3 mailing list
>> pwe3@ietf.org
>> https://www.ietf.org/mailman/listinfo/pwe3
>>
>


From yaakov_s@rad.com  Sun Dec 18 01:44:07 2011
Return-Path: <yaakov_s@rad.com>
X-Original-To: pwe3@ietfa.amsl.com
Delivered-To: pwe3@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0F1B421F8560 for <pwe3@ietfa.amsl.com>; Sun, 18 Dec 2011 01:44:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.198
X-Spam-Level: 
X-Spam-Status: No, score=-99.198 tagged_above=-999 required=5 tests=[AWL=0.700, BAYES_00=-2.599, J_CHICKENPOX_22=0.6, J_CHICKENPOX_43=0.6, J_CHICKENPOX_54=0.6, J_CHICKENPOX_63=0.6, MIME_8BIT_HEADER=0.3, UNPARSEABLE_RELAY=0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dIzeI4XDlM01 for <pwe3@ietfa.amsl.com>; Sun, 18 Dec 2011 01:44:06 -0800 (PST)
Received: from rad.co.il (mailrelay01.rad.co.il [62.0.23.252]) by ietfa.amsl.com (Postfix) with ESMTP id 48CE021F8549 for <pwe3@ietf.org>; Sun, 18 Dec 2011 01:43:57 -0800 (PST)
Received: from Internal Mail-Server by MailRelay01 (envelope-from yaakov?s@rad.com) with AES128-SHA encrypted SMTP; 18 Dec 2011 11:35:48 +0200
Received: from EXRAD5.ad.rad.co.il ([192.114.24.28]) by EXRAD5.ad.rad.co.il ([192.114.24.28]) with mapi id 14.01.0323.003; Sun, 18 Dec 2011 11:43:55 +0200
From: Yaakov Stein <yaakov_s@rad.com>
To: =?Windows-1252?Q?Javi_Mu=F1oz?= <javi@trajano.us.es>
Thread-Topic: [PWE3] Different manipulation of channels in a Nx64 service
Thread-Index: AQHMuPNTu2lISxaldki9+sQRHKsxRZXZaO7QgAAXcICAAJTRoIAA9F0AgAZWyhA=
Date: Sun, 18 Dec 2011 09:43:54 +0000
Message-ID: <07F7D7DED63154409F13298786A2ADC90429ABF6@EXRAD5.ad.rad.co.il>
References: <4EE63982.7020403@trajano.us.es> <07F7D7DED63154409F13298786A2ADC90427FBB4@EXRAD5.ad.rad.co.il> <4EE73621.1090802@trajano.us.es> <07F7D7DED63154409F13298786A2ADC9042831D9@EXRAD5.ad.rad.co.il> <4EE87FF4.5090704@trajano.us.es>
In-Reply-To: <4EE87FF4.5090704@trajano.us.es>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [172.17.170.143]
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "pwe3@ietf.org" <pwe3@ietf.org>
Subject: Re: [PWE3] Different manipulation of channels in a Nx64 service
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pwe3>, <mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pwe3>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 18 Dec 2011 09:44:07 -0000

A question about Y.1452. In the figure 11-1, what exactly is VoIP=20
header?: "only the RTP header" or "the RTP, UDP and IP headers"?

[YJS] The RTP header. There is no need for UDP/IP as the RTP is carried ove=
r MPLS.

And an opinion. If we decide to use a TDMPW for each call:

ISDN TE_A1<--->   [        ]<-TDMPW1->  [        ]<--->   ISDN TE_A2
ISDN TE_B1<--->   [        ]<-TDMPW2->  [        ]<--->   ISDN TE_B2
ISDN TE_C1<--->   [AGW(PE1)]<-TDMPW3->  [AGW(PE2)]<--->   ISDN TE_C2
...
ISDN TE_D1<--->   [        ]<-TDMPWn->  [        ]<--->   ISDN TE_D2


taking into account that:

* They are user calls(thus, they are established / released quite often).

* Each call can be of a different type (voice, VBD, CLEARMODE, ...).

* Each operator (OPN) has many AGWs(not only the two shown in Figure,=20
possibily tens of thousands), so that a TE in a AGW may call to a TE in=20
any other AGW.

What kind of TDMPW would you use:

* CESoPSN or TDMoIP AAL1

and / or

* TDMoIP AAL2  ?

[YJS] If the TDM trunks are mostly full (i.e., the timeslots are mostly act=
ive)
and/or the BW efficiency is not critical,
then use circuit emulation. It minimizes the processing delay and processin=
g power needed.

[YJS] If the trunks are mostly empty and/or the BW is limited,
then use loop emulation. However, take into account that this degrades
certain features.



Regards,

Javi


El 13/12/2011 19:21, Yaakov Stein escribi=F3:
> Javi
>
> If you use Megaco to set up the channels then everything should be fine.
>
> I was thinking about extending the AAL2 TLV to have sub-TLVs per CID
> rather than a single encoding field for all CIDs simultaneously.
>
> Although I was editor of Y.1452 I don't remember the clause number
> (and I am not on my PC right now).
> I think it is the last clause - it talks about muxing RTP flows.
> There you can have a RTP header for each CID, and so identify encoding
> with higher granularity.
>
> Y(J)S
>
> -----Original Message-----
> From: Javi Mu=F1oz [mailto:javi@trajano.us.es]
> Sent: Tuesday, December 13, 2011 13:25
> To: pwe3@ietf.org
> Cc: Yaakov Stein
> Subject: Re: [PWE3] Different manipulation of channels in a Nx64 service
>
> Yaakov,
>> Javi
>>
>> If I understand you question, you are asking whether an AAL2 TDMoIP PW c=
an mix channels that
>> 1) originated from different TDM trunks,  and
> I assumed that this part was possible (we had already discussed in
> previous post).
>> 2) that are encoded with different coding systems (A-law, u-law, VAD, et=
c. etc.)
> This was my question.
>> Please note, however, that the precise mapping of channels to trunks+tim=
eslots
>> would need to be configured by a management system as the TDM control pr=
otocol extensions
>> in RFC 5287 define an optional "mapping base" which only supports the si=
ngle-trunk case.
> As we have already spoken on other occasions, my intention is to use
> Megaco for this mapping of channels to trunks+timeslots.
>
>> Since the channels are completely independent, they can carry anything y=
ou want.
>>
>> However, the AAL2 control protocol extensions are woefully insufficient =
to describe
>> what is needed here. They indeed contain a VAD indicator and encoding fi=
eld,
>> but only for the entire PW, not for individual CIDs.
> What extensiones do you mean exactly?
>
>> It would be a trivial exercise to extend the TLV, but it would become ve=
ry bulky.
>>
>> If you absolutely can not configure and need to recognize the channel ty=
pe automatically,
> My intention was also to use MeGaCo(The node that finishes Q.931/SIP
> signaling know the type of each channel, so it can indicate to the AGW /
> PE using Megaco). Do you see any problem with that?
>
>> I can think of two alternatives.
>> First, you could rely on the native AAL2 UUI codepoint differentiation d=
efined in I.366.
>> Second, you could use the method described in Y.1452 for multiplexing RT=
P streams
>> (at the price of additional overhead).
> What method do you mean?(What clause Y.1452 is defined?).
>
> Regards,
>
> Javi
>> Y(J)S
>>
>>
>>
>>
>>
>>
>> -----Original Message-----
>> From: pwe3-bounces@ietf.org [mailto:pwe3-bounces@ietf.org] On Behalf Of =
Javi Mu?oz
>> Sent: Monday, December 12, 2011 19:28
>> To: pwe3@ietf.org
>> Subject: [PWE3] Different manipulation of channels in a Nx64 service
>>
>> I have the next situation:
>>
>> ISDN TE_A1<--->   [        ]       [        ]<--->   ISDN TE_A2
>> ISDN TE_B1<--->   [        ]       [        ]<--->   ISDN TE_B2
>> ISDN TE_C1<--->   [AGW(PE1)]<--->   [AGW(PE2)]<--->   ISDN TE_C2
>> ...              [        ]       [        ]
>> ISDN TE_D1<--->   [        ]       [        ]<--->   ISDN TE_D2
>>
>>
>> Each AGW finishes several ISDN interfaces (then, several TDM circuits).
>>
>> * ISDN_TE_A1 has stablished a 64kbps call with ISDN_TE_A2 using the RTP
>> codec CLEARMODE.
>> * ISDN_TE_B1 has stablished a 64kbps call with ISDN_TE_B2 using the RTP
>> codec G.711-u without VAD
>> * ISDN_TE_C1 has stablished a 64kbps call with ISDN_TE_C2 using the RTP
>> codec G.711-u with VAD
>> ...
>> * ISDN_TE_D1 has stablished a 64kbps call with ISDN_TE_D2 using the RTP
>> codec G.711-u without VAD
>>
>> (the codec to use for each call would be indicated by an external
>> signalling to the TDMPWs, such as Megaco)
>>
>> Is it possible to use a single TDMoPW TDMoIP AAL2 to emulate all these
>> calls?
>>
>> If this is not possible to use different codec, at least, would it be
>> possible to use a single TDMoPW TDMoIP AAL2 to emulate all calls with
>> the same type of codec and media manipulation (i.e. calls "ISDN_TE_B1 -
>> ISDN_TE_B2" and "ISDN_TE_D1 - ISDN_TE_D2").
>>
>> NOTE: I propose directly AAL2, and not CESoPSN or TDMoIP AAL2, due to
>> they are different calls, so that it is necessary to dynamically modify
>> the number of channels, which is only supported by AAL2.
>>
>>
>> Regards,
>>
>> Javi
>>
>>
>>
>>
>>
>> _______________________________________________
>> pwe3 mailing list
>> pwe3@ietf.org
>> https://www.ietf.org/mailman/listinfo/pwe3
>>
>


From yaakov_s@rad.com  Sun Dec 18 02:01:34 2011
Return-Path: <yaakov_s@rad.com>
X-Original-To: pwe3@ietfa.amsl.com
Delivered-To: pwe3@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D012421F84D7 for <pwe3@ietfa.amsl.com>; Sun, 18 Dec 2011 02:01:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.248
X-Spam-Level: 
X-Spam-Status: No, score=-99.248 tagged_above=-999 required=5 tests=[AWL=0.050, BAYES_00=-2.599, J_CHICKENPOX_22=0.6, J_CHICKENPOX_43=0.6, J_CHICKENPOX_44=0.6, J_CHICKENPOX_54=0.6, J_CHICKENPOX_63=0.6, MIME_8BIT_HEADER=0.3, UNPARSEABLE_RELAY=0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KvxpUbnrZUaT for <pwe3@ietfa.amsl.com>; Sun, 18 Dec 2011 02:01:34 -0800 (PST)
Received: from rad.co.il (mailrelay01.rad.co.il [62.0.23.252]) by ietfa.amsl.com (Postfix) with ESMTP id 6C61F21F84CD for <pwe3@ietf.org>; Sun, 18 Dec 2011 02:01:31 -0800 (PST)
Received: from Internal Mail-Server by MailRelay01 (envelope-from yaakov?s@rad.com) with AES128-SHA encrypted SMTP; 18 Dec 2011 11:53:21 +0200
Received: from EXRAD5.ad.rad.co.il ([192.114.24.28]) by EXRAD5.ad.rad.co.il ([192.114.24.28]) with mapi id 14.01.0323.003; Sun, 18 Dec 2011 12:01:28 +0200
From: Yaakov Stein <yaakov_s@rad.com>
To: =?Windows-1252?Q?Javi_Mu=F1oz?= <javi@trajano.us.es>, "pwe3@ietf.org" <pwe3@ietf.org>
Thread-Topic: [PWE3] Different manipulation of channels in a Nx64 service
Thread-Index: AQHMuPNTu2lISxaldki9+sQRHKsxRZXZaO7QgAAXcICAAJTRoIAA9F0AgAIHogCAASTKAIADL4Iw
Date: Sun, 18 Dec 2011 10:01:26 +0000
Message-ID: <07F7D7DED63154409F13298786A2ADC90429AC4D@EXRAD5.ad.rad.co.il>
References: <4EE63982.7020403@trajano.us.es> <07F7D7DED63154409F13298786A2ADC90427FBB4@EXRAD5.ad.rad.co.il> <4EE73621.1090802@trajano.us.es> <07F7D7DED63154409F13298786A2ADC9042831D9@EXRAD5.ad.rad.co.il> <4EE87FF4.5090704@trajano.us.es> <4EEA33DA.5070709@trajano.us.es> <4EEB2976.90707@trajano.us.es>
In-Reply-To: <4EEB2976.90707@trajano.us.es>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [172.17.170.143]
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [PWE3] Different manipulation of channels in a Nx64 service
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pwe3>, <mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pwe3>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 18 Dec 2011 10:01:34 -0000

Regarding the overhead, RTP over UDP over IP over MPLS
is much more wasteful than RTP directly over MPLS according to Y.1452.

Also, using PWs give you additional features (such as VCCV) that may or may=
 not be useful.

However, standard VoIP over MPLS is indeed an option.
See Y.1414 - there it is the first option.

Y(J)S

-----Original Message-----
From: pwe3-bounces@ietf.org [mailto:pwe3-bounces@ietf.org] On Behalf Of Jav=
i Mu?oz
Sent: Friday, December 16, 2011 13:20
To: pwe3@ietf.org
Cc: Yaakov Stein
Subject: Re: [PWE3] Different manipulation of channels in a Nx64 service

Yaakov,

And an additional question.

When using a TDMPW TDMoIP AAL2 per call(mono or multichannel), I think=20
it might be better to simply use RTP. In a ISDN multichannel call, the=20
"N" 1x64 kbps-channels may be modeled as a virtual single channel of=20
rate Nx64 kbps, then as a single stream of media:

Media of "stream Nx64"
         RTP
         UDP
         IP


TDMoIP AAL2 would keep the identification of the channel to which each=20
sample belongs (but it is not necessary to be a single stream carrried=20
over "N" channels).

If this is correct, then the RTP solution here would be better to have=20
less overhead.

Regards,

Javi


El 15/12/2011 18:52, Javi Mu=F1oz escribi=F3:
> For the opinion about using CESoPSN/TDMoIP AAL1 and/or TDMoIP AAL2, I=20
> would add that:
>
> * Some calls may be switched (SVCs) and others permanent (PVCs).
>
>
> Also, I'd like to know your opinion whether you think is better a=20
> TDMPW per call, or use a TDMPW for multiple calls (muxing).
>
> Regards,
>
> Javi
>
>
> El 14/12/2011 11:52, Javi Mu=F1oz escribi=F3:
>> Yaakov,
>>
>> A question about Y.1452. In the figure 11-1, what exactly is VoIP=20
>> header?: "only the RTP header" or "the RTP, UDP and IP headers"?
>>
>>
>> And an opinion. If we decide to use a TDMPW for each call:
>>
>> ISDN TE_A1<--->   [        ]<-TDMPW1->  [        ]<--->   ISDN TE_A2
>> ISDN TE_B1<--->   [        ]<-TDMPW2->  [        ]<--->   ISDN TE_B2
>> ISDN TE_C1<--->   [AGW(PE1)]<-TDMPW3->  [AGW(PE2)]<--->   ISDN TE_C2
>> ...
>> ISDN TE_D1<--->   [        ]<-TDMPWn->  [        ]<--->   ISDN TE_D2
>>
>>
>> taking into account that:
>>
>> * They are user calls(thus, they are established / released quite=20
>> often).
>>
>> * Each call can be of a different type (voice, VBD, CLEARMODE, ...).
>>
>> * Each operator (OPN) has many AGWs(not only the two shown in Figure,=20
>> possibily tens of thousands), so that a TE in a AGW may call to a TE=20
>> in any other AGW.
>>
>> What kind of TDMPW would you use:
>>
>> * CESoPSN or TDMoIP AAL1
>>
>> and / or
>>
>> * TDMoIP AAL2  ?
>>
>>
>> Regards,
>>
>> Javi
>>
>>
>> El 13/12/2011 19:21, Yaakov Stein escribi=F3:
>>> Javi
>>>
>>> If you use Megaco to set up the channels then everything should be=20
>>> fine.
>>>
>>> I was thinking about extending the AAL2 TLV to have sub-TLVs per CID
>>> rather than a single encoding field for all CIDs simultaneously.
>>>
>>> Although I was editor of Y.1452 I don't remember the clause number
>>> (and I am not on my PC right now).
>>> I think it is the last clause - it talks about muxing RTP flows.
>>> There you can have a RTP header for each CID, and so identify encoding
>>> with higher granularity.
>>>
>>> Y(J)S
>>>
>>> -----Original Message-----
>>> From: Javi Mu=F1oz [mailto:javi@trajano.us.es]
>>> Sent: Tuesday, December 13, 2011 13:25
>>> To: pwe3@ietf.org
>>> Cc: Yaakov Stein
>>> Subject: Re: [PWE3] Different manipulation of channels in a Nx64=20
>>> service
>>>
>>> Yaakov,
>>>> Javi
>>>>
>>>> If I understand you question, you are asking whether an AAL2 TDMoIP=20
>>>> PW can mix channels that
>>>> 1) originated from different TDM trunks,  and
>>> I assumed that this part was possible (we had already discussed in
>>> previous post).
>>>> 2) that are encoded with different coding systems (A-law, u-law,=20
>>>> VAD, etc. etc.)
>>> This was my question.
>>>> Please note, however, that the precise mapping of channels to=20
>>>> trunks+timeslots
>>>> would need to be configured by a management system as the TDM=20
>>>> control protocol extensions
>>>> in RFC 5287 define an optional "mapping base" which only supports=20
>>>> the single-trunk case.
>>> As we have already spoken on other occasions, my intention is to use
>>> Megaco for this mapping of channels to trunks+timeslots.
>>>
>>>> Since the channels are completely independent, they can carry=20
>>>> anything you want.
>>>>
>>>> However, the AAL2 control protocol extensions are woefully=20
>>>> insufficient to describe
>>>> what is needed here. They indeed contain a VAD indicator and=20
>>>> encoding field,
>>>> but only for the entire PW, not for individual CIDs.
>>> What extensiones do you mean exactly?
>>>
>>>> It would be a trivial exercise to extend the TLV, but it would=20
>>>> become very bulky.
>>>>
>>>> If you absolutely can not configure and need to recognize the=20
>>>> channel type automatically,
>>> My intention was also to use MeGaCo(The node that finishes Q.931/SIP
>>> signaling know the type of each channel, so it can indicate to the=20
>>> AGW /
>>> PE using Megaco). Do you see any problem with that?
>>>
>>>> I can think of two alternatives.
>>>> First, you could rely on the native AAL2 UUI codepoint=20
>>>> differentiation defined in I.366.
>>>> Second, you could use the method described in Y.1452 for=20
>>>> multiplexing RTP streams
>>>> (at the price of additional overhead).
>>> What method do you mean?(What clause Y.1452 is defined?).
>>>
>>> Regards,
>>>
>>> Javi
>>>> Y(J)S
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> -----Original Message-----
>>>> From: pwe3-bounces@ietf.org [mailto:pwe3-bounces@ietf.org] On=20
>>>> Behalf Of Javi Mu?oz
>>>> Sent: Monday, December 12, 2011 19:28
>>>> To: pwe3@ietf.org
>>>> Subject: [PWE3] Different manipulation of channels in a Nx64 service
>>>>
>>>> I have the next situation:
>>>>
>>>> ISDN TE_A1<--->   [        ]       [        ]<--->   ISDN TE_A2
>>>> ISDN TE_B1<--->   [        ]       [        ]<--->   ISDN TE_B2
>>>> ISDN TE_C1<--->   [AGW(PE1)]<--->   [AGW(PE2)]<--->   ISDN TE_C2
>>>> ...              [        ]       [        ]
>>>> ISDN TE_D1<--->   [        ]       [        ]<--->   ISDN TE_D2
>>>>
>>>>
>>>> Each AGW finishes several ISDN interfaces (then, several TDM=20
>>>> circuits).
>>>>
>>>> * ISDN_TE_A1 has stablished a 64kbps call with ISDN_TE_A2 using the=20
>>>> RTP
>>>> codec CLEARMODE.
>>>> * ISDN_TE_B1 has stablished a 64kbps call with ISDN_TE_B2 using the=20
>>>> RTP
>>>> codec G.711-u without VAD
>>>> * ISDN_TE_C1 has stablished a 64kbps call with ISDN_TE_C2 using the=20
>>>> RTP
>>>> codec G.711-u with VAD
>>>> ...
>>>> * ISDN_TE_D1 has stablished a 64kbps call with ISDN_TE_D2 using the=20
>>>> RTP
>>>> codec G.711-u without VAD
>>>>
>>>> (the codec to use for each call would be indicated by an external
>>>> signalling to the TDMPWs, such as Megaco)
>>>>
>>>> Is it possible to use a single TDMoPW TDMoIP AAL2 to emulate all these
>>>> calls?
>>>>
>>>> If this is not possible to use different codec, at least, would it be
>>>> possible to use a single TDMoPW TDMoIP AAL2 to emulate all calls with
>>>> the same type of codec and media manipulation (i.e. calls=20
>>>> "ISDN_TE_B1 -
>>>> ISDN_TE_B2" and "ISDN_TE_D1 - ISDN_TE_D2").
>>>>
>>>> NOTE: I propose directly AAL2, and not CESoPSN or TDMoIP AAL2, due to
>>>> they are different calls, so that it is necessary to dynamically=20
>>>> modify
>>>> the number of channels, which is only supported by AAL2.
>>>>
>>>>
>>>> Regards,
>>>>
>>>> Javi
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> pwe3 mailing list
>>>> pwe3@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/pwe3
>>>>
>>>
>>
>> _______________________________________________
>> pwe3 mailing list
>> pwe3@ietf.org
>> https://www.ietf.org/mailman/listinfo/pwe3
>>
>
> _______________________________________________
> pwe3 mailing list
> pwe3@ietf.org
> https://www.ietf.org/mailman/listinfo/pwe3
>

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

From javi@trajano.us.es  Sun Dec 18 09:13:49 2011
Return-Path: <javi@trajano.us.es>
X-Original-To: pwe3@ietfa.amsl.com
Delivered-To: pwe3@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 024B921F8531 for <pwe3@ietfa.amsl.com>; Sun, 18 Dec 2011 09:13:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.985
X-Spam-Level: 
X-Spam-Status: No, score=-2.985 tagged_above=-999 required=5 tests=[BAYES_40=-0.185, J_CHICKENPOX_62=0.6, J_CHICKENPOX_63=0.6, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7IVM8VbMJZvI for <pwe3@ietfa.amsl.com>; Sun, 18 Dec 2011 09:13:48 -0800 (PST)
Received: from mail.us.es (mail.us.es [193.147.175.20]) by ietfa.amsl.com (Postfix) with ESMTP id D905621F852E for <pwe3@ietf.org>; Sun, 18 Dec 2011 09:13:47 -0800 (PST)
Received: (qmail 1741 invoked from network); 18 Dec 2011 18:13:45 +0100
Received: from unknown (HELO us.es) (192.168.2.13) by us.es with SMTP; 18 Dec 2011 18:13:45 +0100
Received: (qmail 14107 invoked by uid 507); 18 Dec 2011 17:13:44 -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/14135.   Clear:RC:1(127.0.0.1):.  Processed in 0.036656 secs); 18 Dec 2011 17:13:44 -0000
Received: from unknown (HELO antivirus3) (127.0.0.1) by us.es with SMTP; 18 Dec 2011 17:13:44 -0000
Received: from 192.168.1.13 (192.168.1.13) by antivirus3 (F-Secure/fsigk_smtp/406/antivirus3); Sun, 18 Dec 2011 18:13:44 +0100 (CET)
X-Virus-Status: clean(F-Secure/fsigk_smtp/406/antivirus3)
Received: (qmail 2875 invoked from network); 18 Dec 2011 18:13:44 +0100
Received: from trajano.us.es (193.147.162.130) by us.es with AES256-SHA encrypted SMTP; 18 Dec 2011 18:13:44 +0100
Received: from [127.0.0.1] (112.pool85-56-79.dynamic.orange.es [85.56.79.112]) (authenticated bits=0) by trajano.us.es (8.13.8/8.13.8/Debian-3) with ESMTP id pBIHDg1O028668 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NOT); Sun, 18 Dec 2011 18:13:43 +0100
Message-ID: <4EEE1F41.6020403@trajano.us.es>
Date: Sun, 18 Dec 2011 18:13:37 +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: "pwe3@ietf.org" <pwe3@ietf.org>
References: <4EE63982.7020403@trajano.us.es>	<07F7D7DED63154409F13298786A2ADC90427FBB4@EXRAD5.ad.rad.co.il>	<4EE73621.1090802@trajano.us.es>	<07F7D7DED63154409F13298786A2ADC9042831D9@EXRAD5.ad.rad.co.il> <4EE87FF4.5090704@trajano.us.es> <07F7D7DED63154409F13298786A2ADC90429ABF6@EXRAD5.ad.rad.co.il>
In-Reply-To: <07F7D7DED63154409F13298786A2ADC90429ABF6@EXRAD5.ad.rad.co.il>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
Cc: Yaakov Stein <yaakov_s@rad.com>
Subject: Re: [PWE3] Different manipulation of channels in a Nx64 service
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pwe3>, <mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pwe3>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 18 Dec 2011 17:13:49 -0000

Yaakov,

El 18/12/2011 10:43, Yaakov Stein escribió:
> A question about Y.1452. In the figure 11-1, what exactly is VoIP
> header?: "only the RTP header" or "the RTP, UDP and IP headers"?
>
> [YJS] The RTP header. There is no need for UDP/IP as the RTP is carried over MPLS.

[Javi] I don't understand, Y.1452 only mentions VoIP over UDP/IP 
networks. Perhaps I did not adequately explain.
The question was: If we have several VoIP flows over a UDP/IP network:

Media1     Media2    ...    Media_n
  RTP        RTP      ...     RTP
  UDP        UDP      ...     UDP
  IP         IP       ...     IP

What protocol stack is the proposalby Y.1452/Figure 11-1?

(A)

[AAL2 Header|RTP Header|Media1] [AAL2 Header|RTP Header|Media2]... [AAL2 
Header|RTP Header|Media_n]
UDP
IP

or

(B)

[AAL2 Header|IP Header|UDP Header|RTP Header|Media1]... [AAL2 Header|IP 
Header|UDP Header|RTP Header|Media_n]
UDP
IP


If we use the option A, it would require that all VoIP flows have the 
same source and destination IP addresss and UDP ports (so, the same 
source and destination application).

Regards,

Javi

From stbryant@cisco.com  Tue Dec 20 12:07:22 2011
Return-Path: <stbryant@cisco.com>
X-Original-To: pwe3@ietfa.amsl.com
Delivered-To: pwe3@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6322221F84C9 for <pwe3@ietfa.amsl.com>; Tue, 20 Dec 2011 12:07:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.599
X-Spam-Level: 
X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dk2yuUYs5-DJ for <pwe3@ietfa.amsl.com>; Tue, 20 Dec 2011 12:07:22 -0800 (PST)
Received: from ams-iport-2.cisco.com (ams-iport-2.cisco.com [144.254.224.141]) by ietfa.amsl.com (Postfix) with ESMTP id A7D9F21F84A1 for <pwe3@ietf.org>; Tue, 20 Dec 2011 12:07:21 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=stbryant@cisco.com; l=1049; q=dns/txt; s=iport; t=1324411641; x=1325621241; h=message-id:date:from:reply-to:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=VT1ItEcqvv/8LCtDYuLpoKFnU1YqA40w8W95pl3mq+A=; b=IbN7cjALJFXRvWgA9giGZLJ/c0bhYAGe+D3HQpgWP+WYATIPZ8vJfcta 4o8Jzuyzaplp80GbuIDr9A2PAJeCN6GfYIDsVf2MslM6X9POtApr55WQk lBewojIYa5RF8RdNC/YvOkLN+nCD3X7OIXHjQBChze72bbubnwjHlExn8 c=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av8EAO/p8E6Q/khL/2dsb2JhbABDqTSCUIEFgXIBAQEEEgECAQcbQRALGAklDwJGBg0BBwEBHqBdAYMuDwGadowMBJR/kjA
X-IronPort-AV: E=Sophos;i="4.71,383,1320624000"; d="scan'208";a="61760147"
Received: from ams-core-2.cisco.com ([144.254.72.75]) by ams-iport-2.cisco.com with ESMTP; 20 Dec 2011 20:07:17 +0000
Received: from cisco.com (mrwint.cisco.com [64.103.70.36]) by ams-core-2.cisco.com (8.14.3/8.14.3) with ESMTP id pBKK7HHd017658; Tue, 20 Dec 2011 20:07:17 GMT
Received: from stbryant-mac2.lan (localhost [127.0.0.1]) by cisco.com (8.14.4+Sun/8.8.8) with ESMTP id pBKK7GDG016769; Tue, 20 Dec 2011 20:07:16 GMT
Message-ID: <4EF0EAF4.90002@cisco.com>
Date: Tue, 20 Dec 2011 20:07:16 +0000
From: Stewart Bryant <stbryant@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:8.0) Gecko/20111105 Thunderbird/8.0
MIME-Version: 1.0
To: Greg Mirsky <gregimirsky@gmail.com>
References: <AcxrtYptbmsGyvQQRH+q7vGDujpKuw==> <CA8A6129.172A4%matthew.bocci@alcatel-lucent.com> <CA+RyBmXy6n6dVHk_dex10pLqP-oeBS4CfUqZwg-Drw_piommYw@mail.gmail.com>
In-Reply-To: <CA+RyBmXy6n6dVHk_dex10pLqP-oeBS4CfUqZwg-Drw_piommYw@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: pwe3 <pwe3@ietf.org>
Subject: Re: [PWE3] WG Last Call for draft-ietf-pwe3-packet-pw-01.txt
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: stbryant@cisco.com
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pwe3>, <mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pwe3>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 20 Dec 2011 20:07:22 -0000

On 06/09/2011 20:16, Greg Mirsky wrote:
> Dear Authors and All,
> I'd like to propose to make use of PW Control word in packet PW
> mandatory, not optional. I believe that given presence of Ethernet
> header in packet PW encapsulation (Section 5) PW CW does not present
> significant overhead but makes use of VCCV ACH Type 1 consistent for
> all MPLS networks.
>
> Regards,
> Greg

Hi Greg

I have two concerns with making this change:

Firstly the issue of whether or not the control word should
continue to be used in PWs is not yet resolved in the PWE3 WG.

Second, the draft is a BCP based on the use of Ethernet PW as it
exists today, and as such should use the RFC4448 as it exists
today.

The right way forward is to resolve the CW issue and then, if
we elect to deprecate CWs, to write an RFC doing that and
updating RFCs as required.

I do not think that this draft should either be used as a vehicle
to resolve the CW issue, nor be held hostage to the issue.

Stewart
(Writing as duty editor of this draft)



From internet-drafts@ietf.org  Tue Dec 20 13:53:10 2011
Return-Path: <internet-drafts@ietf.org>
X-Original-To: pwe3@ietfa.amsl.com
Delivered-To: pwe3@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3C8DC11E8097; Tue, 20 Dec 2011 13:53:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.577
X-Spam-Level: 
X-Spam-Status: No, score=-102.577 tagged_above=-999 required=5 tests=[AWL=0.022, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gBIO+kGPrFPx; Tue, 20 Dec 2011 13:53:09 -0800 (PST)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AC86C11E807F; Tue, 20 Dec 2011 13:53:09 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 3.64p1
Message-ID: <20111220215256.3417.33490.idtracker@ietfa.amsl.com>
Date: Tue, 20 Dec 2011 13:53:09 -0800
Cc: pwe3@ietf.org
Subject: [PWE3] I-D Action: draft-ietf-pwe3-packet-pw-02.txt
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pwe3>, <mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pwe3>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 20 Dec 2011 21:53:10 -0000

A New Internet-Draft is available from the on-line Internet-Drafts director=
ies. This draft is a work item of the Pseudowire Emulation Edge to Edge Wor=
king Group of the IETF.

	Title           : Packet Pseudowire Encapsulation over an MPLS PSN
	Author(s)       : Stewart Bryant
                          Luca Martini
                          George Swallow
                          Andy Malis
	Filename        : draft-ietf-pwe3-packet-pw-02.txt
	Pages           : 14
	Date            : 2011-12-20

   This document describes a pseudowire mechanism that is used to
   transport a packet service over an MPLS PSN is the case where the
   client LSR and the server PE are co-resident in the same equipment.
   This pseudowire mechanism may be used to carry all of the required
   layer 2 and layer 3 protocols between the pair of client LSRs.



A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-pwe3-packet-pw-02.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-pwe3-packet-pw-02.txt


From stbryant@cisco.com  Tue Dec 20 13:56:58 2011
Return-Path: <stbryant@cisco.com>
X-Original-To: pwe3@ietfa.amsl.com
Delivered-To: pwe3@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 31A3911E808A for <pwe3@ietfa.amsl.com>; Tue, 20 Dec 2011 13:56:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.599
X-Spam-Level: 
X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CbIHvtUZWACN for <pwe3@ietfa.amsl.com>; Tue, 20 Dec 2011 13:56:57 -0800 (PST)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140]) by ietfa.amsl.com (Postfix) with ESMTP id 4DC3F11E807F for <pwe3@ietf.org>; Tue, 20 Dec 2011 13:56:56 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=stbryant@cisco.com; l=11773; q=dns/txt; s=iport; t=1324418216; x=1325627816; h=message-id:date:from:reply-to:mime-version:to:cc:subject: references:in-reply-to; bh=JoAZ1xoCemhb+OSgqjxpNoiRT2r/AdAH40p9FhFtJZU=; b=EpOdXTLJucX6+Sgk2pwba5vbfr+CWhzIN/AXZxaBpCxxFjq3AKkA2JjL k8XCPdInrDcY8ZaejecdEBEG/ge45ensn5/Rllt2gPgnEBVrlTMGRYXn8 yYN2ceJvXlf+fGgh5zMuNnBYabHTShGkoEcC5Ff/KU0YGrT0Ye1BqQyWM w=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgAFAG8D8U6Q/khR/2dsb2JhbABDqTWCUIEFgXIBAQEDARIBAgEHWwEFCwsOCgkWDwkDAgECAUUGDQEHAQEeh1iYfQGDLg8BmnOMDASUf5Iw
X-IronPort-AV: E=Sophos;i="4.71,384,1320624000";  d="scan'208,217";a="124301471"
Received: from ams-core-1.cisco.com ([144.254.72.81]) by ams-iport-1.cisco.com with ESMTP; 20 Dec 2011 21:56:55 +0000
Received: from cisco.com (mrwint.cisco.com [64.103.70.36]) by ams-core-1.cisco.com (8.14.3/8.14.3) with ESMTP id pBKLuqVO015571; Tue, 20 Dec 2011 21:56:55 GMT
Received: from stbryant-mac2.local (localhost [127.0.0.1]) by cisco.com (8.14.4+Sun/8.8.8) with ESMTP id pBKLueMp021413; Tue, 20 Dec 2011 21:56:40 GMT
Message-ID: <4EF10498.3000501@cisco.com>
Date: Tue, 20 Dec 2011 21:56:40 +0000
From: Stewart Bryant <stbryant@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:8.0) Gecko/20111105 Thunderbird/8.0
MIME-Version: 1.0
To: Lizhong Jin <lizho.jin@gmail.com>
References: <CAH==cJxugkx_HBHEgq_ehyvHtsqvO8fHH4Wcky-X-kjfbUzeFQ@mail.gmail.com>
In-Reply-To: <CAH==cJxugkx_HBHEgq_ehyvHtsqvO8fHH4Wcky-X-kjfbUzeFQ@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------090408040409000308050200"
Cc: pwe3@ietf.org
Subject: Re: [PWE3] WG Last Call for draft-ietf-pwe3-packet-pw-01.txt
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: stbryant@cisco.com
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pwe3>, <mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pwe3>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 20 Dec 2011 21:56:58 -0000

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

Lizhong

Thank you for your LC comments

On 07/09/2011 16:35, Lizhong Jin wrote:
> Hi authors,
> If the PE provides active&standby packet PW, then will the two PW be 
> configured with same unicast Ethernet addresses (PacketPWEthA and 
> PacketPWEthB), or different? If different, what kind of unicast 
> Ethernet addresses could be used?
My assumption is that it is the same Ethernet address. The Ethernet 
address is part of the client LSR, and thus if the PW changes you would 
expect that to no be effected by the change in the PW.

However that does beg a question of whether the client LSR is going to 
be able to cope with multiple logical Ethernet interfaces that all use 
the same Ethernet address (which is the current design). If that is a 
problem, then we need to change the design to use real Ethernet 
addresses, and then we are going to hit a number of IEEE issues with the 
number of virtual Ethernet addresses we are going to need to assign to PEs.

> And, I think section 1&4 needs to be revised since virtual ethernet 
> approach is selected, see below.
> Section 1, Introduction
>    Where the client LSR and server PE is co-located in the same
>    equipment, the data-link layer can be simplified to a simple protocol
>    identifier (PID) that is used to multiplex the various data-link
>    types onto a pseudowire.
> [Lizhong] the PID concept is for PID label approach, not virtual 
> ethernet approach.
Yes - I missed that, have changed this to:

"Where the client LSR and server PE is co-located in the same equipment, 
the data-link layer can be simplified to a point to point Ethernet used 
to multiplex the various data-link types onto a pseudowire. This is the 
method that described in this document."
>  Section 4, Forwarding Model
> This LSR determines the next hop in the client
>    layer, and pushes the label needed by the next hop in the client
>    layer.  It then passes the packet to the correct PW instance
>    indicating the packet protocol type.  If the PW is configured to
>    require a CW this is pushed.  The PW instance then examines the
>    protocol type and pushes a label that identifies the protocol type...
> [Lizhong] The procedure defined above seems to be the PID label 
> approach, not virtual ethernet approach.
>
Yes, again you are correct.

Here is the text I propose:

OLD

    This LSR determines the next hop in the client
    layer, and pushes the label needed by the next hop in the client
    layer.  It then passes the packet to the correct PW instance
    indicating the packet protocol type.  If the PW is configured to
    require a CW this is pushed.  The PW instance then examines the
    protocol type and pushes a label that identifies the protocol type to
    the egress PE.  The PW instance then proceeds as it would for a layer
    two PW, by pushing the PW label and then handing the packet to the
    server layer LSR for delivery.  At egress, the packet again arrives
    with the PW label at the top of stack which causes the packet to be
    passed to the correct PW instance.  This PW instance knows that the
    PW type is a packet PW, and hence that it needs to interpret the next
    label as a protocol type identifier.  If necessary the CW is then
    popped and processed.  The packet is then passed to the egress client
    LSR together with information that identifies the packet protocol
    type.  The egress client LSR then forwards the packet in the normal
    manner for a protocol of that type.

NEW

    The client LSR determines the next hop in the
    client layer, and pushes the label needed by the next hop in the
    client layer.  It then encapsulates the packet in an Ethernet header
    setting the Ethertype to MPLS.  The client LSR then passes the packet
    to the correct PW instance.  The PW instance then proceeds as defined
    for an Ethernet PW [RFC4448] by optionally pushing the control word,
    then pushing the PW label, and finally handing the packet to the
    server layer LSR for delivery to the egress PE in the server layer.

    At the egress PE in the server layer, the packet is first processed
    by the server LSR which uses the PW label to pass the packet to the
    correct PW instance.  This PW instance processed the packet as
    described in RFC4448.  The resultant Ethernet encapsulated client
    packet is then passed to the egress client LSR which then processes
    the packet in the normal manner.


END

We (as a WG) are going to have to take a look at the terms
"ingress" and "egress". I complained that the P2MP authors
used ingress and egress, and not the RFC3985 terms, and
I see that we (I) have used ingress and egress here. We
may have to write a note somewhere equating the formal
terms in RFC3985 with the "natural" terms ingress and
egress that most people prefer to use.

I have uploaded -02 of the draft.

- Stewart
(Writing as duty editor of the draft)


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

<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    Lizhong<br>
    <br>
    Thank you for your LC comments<br>
    <br>
    On 07/09/2011 16:35, Lizhong Jin wrote:
    <blockquote
cite="mid:CAH==cJxugkx_HBHEgq_ehyvHtsqvO8fHH4Wcky-X-kjfbUzeFQ@mail.gmail.com"
      type="cite">
      <div>Hi authors,</div>
      <div>If the PE provides active&amp;standby packet PW, then will
        the two PW be configured with same unicast Ethernet addresses
        (PacketPWEthA and PacketPWEthB), or different? If different,
        what kind of unicast Ethernet addresses could be used?</div>
    </blockquote>
    My assumption is that it is the same Ethernet address. The Ethernet
    address is part of the client LSR, and thus if the PW changes you
    would expect that to no be effected by the change in the PW. <br>
    <br>
    However that does beg a question of whether the client LSR is going
    to be able to cope with multiple logical Ethernet interfaces that
    all use the same Ethernet address (which is the current design). If
    that is a problem, then we need to change the design to use real
    Ethernet addresses, and then we are going to hit a number of IEEE
    issues with the number of virtual Ethernet addresses we are going to
    need to assign to PEs.<br>
    <br>
    <blockquote
cite="mid:CAH==cJxugkx_HBHEgq_ehyvHtsqvO8fHH4Wcky-X-kjfbUzeFQ@mail.gmail.com"
      type="cite">
      <div>&nbsp;</div>
      <div>And, I think section 1&amp;4 needs to be revised since
        virtual ethernet approach is selected, see below.</div>
      <div>Section 1, Introduction<br>
        &nbsp;&nbsp; Where the client LSR and server PE is co-located in the same<br>
        &nbsp;&nbsp; equipment, the data-link layer can be simplified to a simple
        protocol<br>
        &nbsp;&nbsp; identifier (PID) that is used to multiplex the various
        data-link<br>
        &nbsp;&nbsp; types onto a pseudowire.<br>
        [Lizhong] the PID concept is for PID label approach, not virtual
        ethernet approach.</div>
    </blockquote>
    Yes - I missed that, have changed this to:<br>
    <br>
    "Where the client LSR and server PE is co-located in the same
    equipment, the data-link layer can be simplified to a point to point
    Ethernet used to multiplex the various data-link types onto a
    pseudowire. This is the method that described in this document."<br>
    <blockquote
cite="mid:CAH==cJxugkx_HBHEgq_ehyvHtsqvO8fHH4Wcky-X-kjfbUzeFQ@mail.gmail.com"
      type="cite">
      <div>&nbsp;</div>
      <div>&nbsp;Section 4, Forwarding Model<br>
        This LSR determines the next hop in the client<br>
        &nbsp;&nbsp; layer, and pushes the label needed by the next hop in the
        client<br>
        &nbsp;&nbsp; layer.&nbsp; It then passes the packet to the correct PW instance<br>
        &nbsp;&nbsp; indicating the packet protocol type.&nbsp; If the PW is configured
        to<br>
        &nbsp;&nbsp; require a CW this is pushed.&nbsp; The PW instance then examines
        the<br>
        &nbsp;&nbsp; protocol type and pushes a label that identifies the protocol
        type...<br>
        [Lizhong] The procedure defined above seems to be the PID label
        approach, not virtual ethernet approach.</div>
      <div><br>
      </div>
    </blockquote>
    Yes, again you are correct.<br>
    <br>
    Here is the text I propose:<br>
    <br>
    OLD<br>
    <br>
    <meta http-equiv="content-type" content="text/html;
      charset=ISO-8859-1">
    <pre>   This LSR determines the next hop in the client
   layer, and pushes the label needed by the next hop in the client
   layer.  It then passes the packet to the correct PW instance
   indicating the packet protocol type.  If the PW is configured to
   require a CW this is pushed.  The PW instance then examines the
   protocol type and pushes a label that identifies the protocol type to
   the egress PE.  The PW instance then proceeds as it would for a layer
   two PW, by pushing the PW label and then handing the packet to the
   server layer LSR for delivery.  At egress, the packet again arrives
   with the PW label at the top of stack which causes the packet to be
   passed to the correct PW instance.  This PW instance knows that the
   PW type is a packet PW, and hence that it needs to interpret the next
   label as a protocol type identifier.  If necessary the CW is then
   popped and processed.  The packet is then passed to the egress client
   LSR together with information that identifies the packet protocol
   type.  The egress client LSR then forwards the packet in the normal
   manner for a protocol of that type.

NEW

<meta http-equiv="content-type" content="text/html; charset=ISO-8859-1">   The client LSR determines the next hop in the
   client layer, and pushes the label needed by the next hop in the
   client layer.  It then encapsulates the packet in an Ethernet header
   setting the Ethertype to MPLS.  The client LSR then passes the packet
   to the correct PW instance.  The PW instance then proceeds as defined
   for an Ethernet PW [RFC4448] by optionally pushing the control word,
   then pushing the PW label, and finally handing the packet to the
   server layer LSR for delivery to the egress PE in the server layer.

   At the egress PE in the server layer, the packet is first processed
   by the server LSR which uses the PW label to pass the packet to the
   correct PW instance.  This PW instance processed the packet as
   described in RFC4448.  The resultant Ethernet encapsulated client
   packet is then passed to the egress client LSR which then processes
   the packet in the normal manner.<pre></pre>
END

We (as a WG) are going to have to take a look at the terms
"ingress" and "egress". I complained that the P2MP authors
used ingress and egress, and not the RFC3985 terms, and
I see that we (I) have used ingress and egress here. We
may have to write a note somewhere equating the formal
terms in RFC3985 with the "natural" terms ingress and
egress that most people prefer to use.

I have uploaded -02 of the draft.

- Stewart
(Writing as duty editor of the draft)
</pre>
  </body>
</html>

--------------090408040409000308050200--

From javi@trajano.us.es  Wed Dec 21 03:56:57 2011
Return-Path: <javi@trajano.us.es>
X-Original-To: pwe3@ietfa.amsl.com
Delivered-To: pwe3@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 707E921F8512 for <pwe3@ietfa.amsl.com>; Wed, 21 Dec 2011 03:56:57 -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 1yxk7ypXCHU6 for <pwe3@ietfa.amsl.com>; Wed, 21 Dec 2011 03:56:56 -0800 (PST)
Received: from mail.us.es (mail.us.es [193.147.175.20]) by ietfa.amsl.com (Postfix) with ESMTP id ED75F21F84F9 for <pwe3@ietf.org>; Wed, 21 Dec 2011 03:56:55 -0800 (PST)
Received: (qmail 31180 invoked from network); 21 Dec 2011 12:56:51 +0100
Received: from unknown (HELO us.es) (192.168.2.12) by us.es with SMTP; 21 Dec 2011 12:56:51 +0100
Received: (qmail 23719 invoked by uid 507); 21 Dec 2011 11:56:41 -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/14160.   Clear:RC:1(127.0.0.1):.  Processed in 0.035417 secs); 21 Dec 2011 11:56:41 -0000
Received: from unknown (HELO antivirus2) (127.0.0.1) by us.es with SMTP; 21 Dec 2011 11:56:41 -0000
Received: from 192.168.1.13 (192.168.1.13) by antivirus2 (F-Secure/fsigk_smtp/406/antivirus2); Wed, 21 Dec 2011 12:56:41 +0100 (CET)
X-Virus-Status: clean(F-Secure/fsigk_smtp/406/antivirus2)
Received: (qmail 23082 invoked from network); 21 Dec 2011 12:56:40 +0100
Received: from trajano.us.es (193.147.162.130) by us.es with AES256-SHA encrypted SMTP; 21 Dec 2011 12:56: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 pBLBubUa007022 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NOT); Wed, 21 Dec 2011 12:56:37 +0100
Message-ID: <4EF1C999.3080303@trajano.us.es>
Date: Wed, 21 Dec 2011 12:57:13 +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: "pwe3@ietf.org" <pwe3@ietf.org>
References: <4EE63982.7020403@trajano.us.es>	<07F7D7DED63154409F13298786A2ADC90427FBB4@EXRAD5.ad.rad.co.il>	<4EE73621.1090802@trajano.us.es>	<07F7D7DED63154409F13298786A2ADC9042831D9@EXRAD5.ad.rad.co.il> <4EE7A6EB.8030401@trajano.us.es> <07F7D7DED63154409F13298786A2ADC904299BCE@EXRAD5.ad.rad.co.il>
In-Reply-To: <07F7D7DED63154409F13298786A2ADC904299BCE@EXRAD5.ad.rad.co.il>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
Cc: Yaakov Stein <yaakov_s@rad.com>
Subject: Re: [PWE3] Different manipulation of channels in a Nx64 service
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pwe3>, <mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pwe3>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Dec 2011 11:56:57 -0000

Yaakov,

RFC3389 (PT for noise confort) allows to convey CNG-related
parameters to the egress PE.

However, the problem I see is at the ingress point: how to tell the
ingress PE that it may apply VAD procedures for a given channel.
Of course, if VAD were allowed, the ingress PE would supress
silences and use RFC3389 to carry CNG parameters, as you said.

If we consider using AAL2 TDMoIP PWs to multiplex calls coming
to the ingress PE from different channels, these channels may be
encoded differently. Some would allow VAD, some others wouldn't.

AAL2-mode TDMPW control plane (sub-TLV "AAL2 options") allows to
indicate whether VAD is allowed for _all_ channels conveyed by the
TDMPW or not, but it is unable to allow VAD for some channels and
to deny VAD for the other.

Regards,

Javi



El 18/12/2011 10:38, Yaakov Stein escribió:
> See RFCs 3551 and 3389.
>
> Y(J)S
>
>
> Yaakov
>> Although I was editor of Y.1452 I don't remember the clause number
>> (and I am not on my PC right now).
> It is clause 11. It proposes to carry the RTP header in each CID. This
> allows to indicate de Payload Type. But, how may it indicate if using
> G.711 with or without VAD, for instance?
>> you could rely on the native AAL2 UUI codepoint differentiation defined in I.366.


From lizho.jin@gmail.com  Wed Dec 21 07:48:12 2011
Return-Path: <lizho.jin@gmail.com>
X-Original-To: pwe3@ietfa.amsl.com
Delivered-To: pwe3@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3B2D921F8593 for <pwe3@ietfa.amsl.com>; Wed, 21 Dec 2011 07:48:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.598
X-Spam-Level: 
X-Spam-Status: No, score=-3.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
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 VeGEmKqi3kRt for <pwe3@ietfa.amsl.com>; Wed, 21 Dec 2011 07:48:11 -0800 (PST)
Received: from mail-qy0-f172.google.com (mail-qy0-f172.google.com [209.85.216.172]) by ietfa.amsl.com (Postfix) with ESMTP id 1E34E21F8564 for <pwe3@ietf.org>; Wed, 21 Dec 2011 07:48:11 -0800 (PST)
Received: by qcsf15 with SMTP id f15so5502399qcs.31 for <pwe3@ietf.org>; Wed, 21 Dec 2011 07:48:10 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=k7BwW1V+zkGJ7/SMSrAyOh7BoxpWowy8+m2XLLwp8xw=; b=BGC27PzGR6yuP/6BuB2ykS8bxmY/5QihNEVC/oaJyrwiW6elSPMcB9cAoDfbldPE2A B1Tm24cgsSVsqIpF5dPMfdrB0ysbh7rYP4C0aqrWkJE+hwRp7Y5wTLMeakIgT3dEKIgW RfJx1rDo01hRc7cyn5LQsMOU+lK/boso1w2b0=
MIME-Version: 1.0
Received: by 10.229.77.134 with SMTP id g6mr2733490qck.125.1324482490543; Wed, 21 Dec 2011 07:48:10 -0800 (PST)
Received: by 10.224.37.82 with HTTP; Wed, 21 Dec 2011 07:48:10 -0800 (PST)
In-Reply-To: <4EF10498.3000501@cisco.com>
References: <CAH==cJxugkx_HBHEgq_ehyvHtsqvO8fHH4Wcky-X-kjfbUzeFQ@mail.gmail.com> <4EF10498.3000501@cisco.com>
Date: Wed, 21 Dec 2011 23:48:10 +0800
Message-ID: <CAH==cJySw3Y4WNogjaT03avRWjYphC0YFwoiZowTBED-gkkV4g@mail.gmail.com>
From: Lizhong Jin <lizho.jin@gmail.com>
To: stbryant@cisco.com
Content-Type: multipart/alternative; boundary=00235433297e5c304b04b49c1c76
Cc: pwe3@ietf.org
Subject: Re: [PWE3] WG Last Call for draft-ietf-pwe3-packet-pw-01.txt
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pwe3>, <mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pwe3>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Dec 2011 15:48:12 -0000

--00235433297e5c304b04b49c1c76
Content-Type: text/plain; charset=ISO-8859-1

Hi Stewart,
Thank you for the reply. I am OK with the changes. Other comments, see
inline.

Lizhong

2011/12/21 Stewart Bryant <stbryant@cisco.com>

> Lizhong
>
> Thank you for your LC comments
>
>
> On 07/09/2011 16:35, Lizhong Jin wrote:
>
> Hi authors,
> If the PE provides active&standby packet PW, then will the two PW be
> configured with same unicast Ethernet addresses (PacketPWEthA and
> PacketPWEthB), or different? If different, what kind of unicast Ethernet
> addresses could be used?
>
> My assumption is that it is the same Ethernet address. The Ethernet
> address is part of the client LSR, and thus if the PW changes you would
> expect that to no be effected by the change in the PW.
>
> However that does beg a question of whether the client LSR is going to be
> able to cope with multiple logical Ethernet interfaces that all use the
> same Ethernet address (which is the current design). If that is a problem,
> then we need to change the design to use real Ethernet addresses, and then
> we are going to hit a number of IEEE issues with the number of virtual
> Ethernet addresses we are going to need to assign to PEs.
>
[Lizhong] to my knowledge, for point-to-point Ethernet interface, it is
possible for them to share one MAC address.


>
>
>
> And, I think section 1&4 needs to be revised since virtual ethernet
> approach is selected, see below.
> Section 1, Introduction
>    Where the client LSR and server PE is co-located in the same
>    equipment, the data-link layer can be simplified to a simple protocol
>    identifier (PID) that is used to multiplex the various data-link
>    types onto a pseudowire.
> [Lizhong] the PID concept is for PID label approach, not virtual ethernet
> approach.
>
> Yes - I missed that, have changed this to:
>
> "Where the client LSR and server PE is co-located in the same equipment,
> the data-link layer can be simplified to a point to point Ethernet used to
> multiplex the various data-link types onto a pseudowire. This is the method
> that described in this document."
>
>
>  Section 4, Forwarding Model
> This LSR determines the next hop in the client
>    layer, and pushes the label needed by the next hop in the client
>    layer.  It then passes the packet to the correct PW instance
>    indicating the packet protocol type.  If the PW is configured to
>    require a CW this is pushed.  The PW instance then examines the
>    protocol type and pushes a label that identifies the protocol type...
> [Lizhong] The procedure defined above seems to be the PID label approach,
> not virtual ethernet approach.
>
> Yes, again you are correct.
>
> Here is the text I propose:
>
> OLD
>
>    This LSR determines the next hop in the client
>    layer, and pushes the label needed by the next hop in the client
>    layer.  It then passes the packet to the correct PW instance
>    indicating the packet protocol type.  If the PW is configured to
>    require a CW this is pushed.  The PW instance then examines the
>    protocol type and pushes a label that identifies the protocol type to
>    the egress PE.  The PW instance then proceeds as it would for a layer
>    two PW, by pushing the PW label and then handing the packet to the
>    server layer LSR for delivery.  At egress, the packet again arrives
>    with the PW label at the top of stack which causes the packet to be
>    passed to the correct PW instance.  This PW instance knows that the
>    PW type is a packet PW, and hence that it needs to interpret the next
>    label as a protocol type identifier.  If necessary the CW is then
>    popped and processed.  The packet is then passed to the egress client
>    LSR together with information that identifies the packet protocol
>    type.  The egress client LSR then forwards the packet in the normal
>    manner for a protocol of that type.
>
> NEW
>
>    The client LSR determines the next hop in the
>    client layer, and pushes the label needed by the next hop in the
>    client layer.  It then encapsulates the packet in an Ethernet header
>    setting the Ethertype to MPLS.  The client LSR then passes the packet
>    to the correct PW instance.  The PW instance then proceeds as defined
>    for an Ethernet PW [RFC4448] by optionally pushing the control word,
>    then pushing the PW label, and finally handing the packet to the
>    server layer LSR for delivery to the egress PE in the server layer.
>
>    At the egress PE in the server layer, the packet is first processed
>    by the server LSR which uses the PW label to pass the packet to the
>    correct PW instance.  This PW instance processed the packet as
>    described in RFC4448.  The resultant Ethernet encapsulated client
>    packet is then passed to the egress client LSR which then processes
>    the packet in the normal manner.
>
> END We (as a WG) are going to have to take a look at the terms "ingress"
> and "egress". I complained that the P2MP authors used ingress and egress,
> and not the RFC3985 terms, and I see that we (I) have used ingress and
> egress here. We may have to write a note somewhere equating the formal
> terms in RFC3985 with the "natural" terms ingress and egress that most
> people prefer to use. I have uploaded -02 of the draft. - Stewart (Writing
> as duty editor of the draft)
>
>

--00235433297e5c304b04b49c1c76
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div>Hi Stewart,</div>
<div>Thank you for the reply. I am OK with the changes. Other comments, see=
 inline.</div>
<div>=A0</div>
<div>Lizhong<br><br></div>
<div class=3D"gmail_quote">2011/12/21 Stewart Bryant <span dir=3D"ltr">&lt;=
<a href=3D"mailto:stbryant@cisco.com">stbryant@cisco.com</a>&gt;</span><br>
<blockquote style=3D"BORDER-LEFT:#ccc 1px solid;MARGIN:0px 0px 0px 0.8ex;PA=
DDING-LEFT:1ex" class=3D"gmail_quote">
<div text=3D"#000000" bgcolor=3D"#FFFFFF">Lizhong<br><br>Thank you for your=
 LC comments=20
<div class=3D"im"><br><br>On 07/09/2011 16:35, Lizhong Jin wrote:=20
<blockquote type=3D"cite">
<div>Hi authors,</div>
<div>If the PE provides active&amp;standby packet PW, then will the two PW =
be configured with same unicast Ethernet addresses (PacketPWEthA and Packet=
PWEthB), or different? If different, what kind of unicast Ethernet addresse=
s could be used?</div>
</blockquote></div>My assumption is that it is the same Ethernet address. T=
he Ethernet address is part of the client LSR, and thus if the PW changes y=
ou would expect that to no be effected by the change in the PW. <br><br>
However that does beg a question of whether the client LSR is going to be a=
ble to cope with multiple logical Ethernet interfaces that all use the same=
 Ethernet address (which is the current design). If that is a problem, then=
 we need to change the design to use real Ethernet addresses, and then we a=
re going to hit a number of IEEE issues with the number of virtual Ethernet=
 addresses we are going to need to assign to PEs. </div>
</blockquote>
<div>[Lizhong] to my knowledge, for point-to-point Ethernet interface, it i=
s possible for them to share one MAC address.</div>
<div>=A0</div>
<blockquote style=3D"BORDER-LEFT:#ccc 1px solid;MARGIN:0px 0px 0px 0.8ex;PA=
DDING-LEFT:1ex" class=3D"gmail_quote">
<div text=3D"#000000" bgcolor=3D"#FFFFFF">
<div class=3D"im"><br><br>
<blockquote type=3D"cite">
<div>=A0</div>
<div>And, I think section 1&amp;4 needs to be revised since virtual etherne=
t approach is selected, see below.</div>
<div>Section 1, Introduction<br>=A0=A0 Where the client LSR and server PE i=
s co-located in the same<br>=A0=A0 equipment, the data-link layer can be si=
mplified to a simple protocol<br>=A0=A0 identifier (PID) that is used to mu=
ltiplex the various data-link<br>
=A0=A0 types onto a pseudowire.<br>[Lizhong] the PID concept is for PID lab=
el approach, not virtual ethernet approach.</div></blockquote></div>Yes - I=
 missed that, have changed this to:<br><br>&quot;Where the client LSR and s=
erver PE is co-located in the same equipment, the data-link layer can be si=
mplified to a point to point Ethernet used to multiplex the various data-li=
nk types onto a pseudowire. This is the method that described in this docum=
ent.&quot;=20
<div class=3D"im"><br>
<blockquote type=3D"cite">
<div>=A0</div>
<div>=A0Section 4, Forwarding Model<br>This LSR determines the next hop in =
the client<br>=A0=A0 layer, and pushes the label needed by the next hop in =
the client<br>=A0=A0 layer.=A0 It then passes the packet to the correct PW =
instance<br>
=A0=A0 indicating the packet protocol type.=A0 If the PW is configured to<b=
r>=A0=A0 require a CW this is pushed.=A0 The PW instance then examines the<=
br>=A0=A0 protocol type and pushes a label that identifies the protocol typ=
e...<br>[Lizhong] The procedure defined above seems to be the PID label app=
roach, not virtual ethernet approach.</div>

<div><br></div></blockquote></div>Yes, again you are correct.<br><br>Here i=
s the text I propose:<br><br>OLD<br><br><pre>   This LSR determines the nex=
t hop in the client
   layer, and pushes the label needed by the next hop in the client
   layer.  It then passes the packet to the correct PW instance
   indicating the packet protocol type.  If the PW is configured to
   require a CW this is pushed.  The PW instance then examines the
   protocol type and pushes a label that identifies the protocol type to
   the egress PE.  The PW instance then proceeds as it would for a layer
   two PW, by pushing the PW label and then handing the packet to the
   server layer LSR for delivery.  At egress, the packet again arrives
   with the PW label at the top of stack which causes the packet to be
   passed to the correct PW instance.  This PW instance knows that the
   PW type is a packet PW, and hence that it needs to interpret the next
   label as a protocol type identifier.  If necessary the CW is then
   popped and processed.  The packet is then passed to the egress client
   LSR together with information that identifies the packet protocol
   type.  The egress client LSR then forwards the packet in the normal
   manner for a protocol of that type.

NEW

   The client LSR determines the next hop in the
   client layer, and pushes the label needed by the next hop in the
   client layer.  It then encapsulates the packet in an Ethernet header
   setting the Ethertype to MPLS.  The client LSR then passes the packet
   to the correct PW instance.  The PW instance then proceeds as defined
   for an Ethernet PW [RFC4448] by optionally pushing the control word,
   then pushing the PW label, and finally handing the packet to the
   server layer LSR for delivery to the egress PE in the server layer.

   At the egress PE in the server layer, the packet is first processed
   by the server LSR which uses the PW label to pass the packet to the
   correct PW instance.  This PW instance processed the packet as
   described in RFC4448.  The resultant Ethernet encapsulated client
   packet is then passed to the egress client LSR which then processes
   the packet in the normal manner.<pre></pre>
END

We (as a WG) are going to have to take a look at the terms
&quot;ingress&quot; and &quot;egress&quot;. I complained that the P2MP auth=
ors
used ingress and egress, and not the RFC3985 terms, and
I see that we (I) have used ingress and egress here. We
may have to write a note somewhere equating the formal
terms in RFC3985 with the &quot;natural&quot; terms ingress and
egress that most people prefer to use.

I have uploaded -02 of the draft.

- Stewart
(Writing as duty editor of the draft)
</pre></div></blockquote></div><br>

--00235433297e5c304b04b49c1c76--

From javi@trajano.us.es  Thu Dec 22 08:00:00 2011
Return-Path: <javi@trajano.us.es>
X-Original-To: pwe3@ietfa.amsl.com
Delivered-To: pwe3@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4A40821F8514 for <pwe3@ietfa.amsl.com>; Thu, 22 Dec 2011 08:00:00 -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 FblTyzE7QCNf for <pwe3@ietfa.amsl.com>; Thu, 22 Dec 2011 07:59:59 -0800 (PST)
Received: from mail.us.es (mail.us.es [193.147.175.20]) by ietfa.amsl.com (Postfix) with ESMTP id B607C21F84ED for <pwe3@ietf.org>; Thu, 22 Dec 2011 07:59:57 -0800 (PST)
Received: (qmail 23451 invoked from network); 22 Dec 2011 16:59:56 +0100
Received: from unknown (HELO us.es) (192.168.2.11) by us.es with SMTP; 22 Dec 2011 16:59:56 +0100
Received: (qmail 23087 invoked by uid 507); 22 Dec 2011 15:59:40 -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/14171.   Clear:RC:1(127.0.0.1):.  Processed in 0.035914 secs); 22 Dec 2011 15:59:40 -0000
Received: from unknown (HELO antivirus1) (127.0.0.1) by us.es with SMTP; 22 Dec 2011 15:59:40 -0000
Received: from 192.168.1.13 (192.168.1.13) by antivirus1 (F-Secure/fsigk_smtp/406/antivirus1); Thu, 22 Dec 2011 16:59:40 +0100 (CET)
X-Virus-Status: clean(F-Secure/fsigk_smtp/406/antivirus1)
Received: (qmail 30728 invoked from network); 22 Dec 2011 16:59:38 +0100
Received: from trajano.us.es (193.147.162.130) by us.es with AES256-SHA encrypted SMTP; 22 Dec 2011 16:59:38 +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 pBMFxb7T032741 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NOT); Thu, 22 Dec 2011 16:59:37 +0100
Message-ID: <4EF35412.4020201@trajano.us.es>
Date: Thu, 22 Dec 2011 17:00:18 +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: "pwe3@ietf.org" <pwe3@ietf.org>
References: <4EE63982.7020403@trajano.us.es>	<07F7D7DED63154409F13298786A2ADC90427FBB4@EXRAD5.ad.rad.co.il>	<4EE73621.1090802@trajano.us.es>	<07F7D7DED63154409F13298786A2ADC9042831D9@EXRAD5.ad.rad.co.il> <4EE87FF4.5090704@trajano.us.es> <07F7D7DED63154409F13298786A2ADC90429ABF6@EXRAD5.ad.rad.co.il>
In-Reply-To: <07F7D7DED63154409F13298786A2ADC90429ABF6@EXRAD5.ad.rad.co.il>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Yaakov Stein <yaakov_s@rad.com>
Subject: Re: [PWE3] Different manipulation of channels in a Nx64 service
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pwe3>, <mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pwe3>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 22 Dec 2011 16:00:00 -0000

Yaakov,
> [YJS] If the TDM trunks are mostly full (i.e., the timeslots are mostly active)
> and/or the BW efficiency is not critical,
> then use circuit emulation. It minimizes the processing delay and processing power needed.
>
> [YJS] If the trunks are mostly empty and/or the BW is limited,
> then use loop emulation. However, take into account that this degrades
> certain features.

What specific parameters are degraded more in AAL2-mode?

May any of them affect to ISDN calls, avoiding its NGN emulation?

Regards,

Javi

From javi@trajano.us.es  Fri Dec 23 03:53:33 2011
Return-Path: <javi@trajano.us.es>
X-Original-To: pwe3@ietfa.amsl.com
Delivered-To: pwe3@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C361E21F8B55 for <pwe3@ietfa.amsl.com>; Fri, 23 Dec 2011 03:53:33 -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=[AWL=0.000,  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 y+MvrMiSNxao for <pwe3@ietfa.amsl.com>; Fri, 23 Dec 2011 03:53:33 -0800 (PST)
Received: from mail.us.es (mail.us.es [193.147.175.20]) by ietfa.amsl.com (Postfix) with ESMTP id 74BF421F8B53 for <pwe3@ietf.org>; Fri, 23 Dec 2011 03:53:32 -0800 (PST)
Received: (qmail 1507 invoked from network); 23 Dec 2011 12:53:31 +0100
Received: from unknown (HELO us.es) (192.168.2.13) by us.es with SMTP; 23 Dec 2011 12:53:31 +0100
Received: (qmail 23347 invoked by uid 507); 23 Dec 2011 11:53:27 -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/14172.   Clear:RC:1(127.0.0.1):.  Processed in 0.037784 secs); 23 Dec 2011 11:53:27 -0000
Received: from unknown (HELO antivirus3) (127.0.0.1) by us.es with SMTP; 23 Dec 2011 11:53:27 -0000
Received: from 192.168.1.13 (192.168.1.13) by antivirus3 (F-Secure/fsigk_smtp/406/antivirus3); Fri, 23 Dec 2011 12:53:27 +0100 (CET)
X-Virus-Status: clean(F-Secure/fsigk_smtp/406/antivirus3)
Received: (qmail 1017 invoked from network); 23 Dec 2011 12:53:26 +0100
Received: from trajano.us.es (193.147.162.130) by us.es with AES256-SHA encrypted SMTP; 23 Dec 2011 12:53:26 +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 pBNBrQZX012746 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NOT); Fri, 23 Dec 2011 12:53:26 +0100
Message-ID: <4EF46BE4.6050101@trajano.us.es>
Date: Fri, 23 Dec 2011 12:54:12 +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: "pwe3@ietf.org" <pwe3@ietf.org>
References: <4EE63982.7020403@trajano.us.es>	<07F7D7DED63154409F13298786A2ADC90427FBB4@EXRAD5.ad.rad.co.il>	<4EE73621.1090802@trajano.us.es>	<07F7D7DED63154409F13298786A2ADC9042831D9@EXRAD5.ad.rad.co.il>	<4EE87FF4.5090704@trajano.us.es>	<07F7D7DED63154409F13298786A2ADC90429ABF6@EXRAD5.ad.rad.co.il> <4EEE1F41.6020403@trajano.us.es>
In-Reply-To: <4EEE1F41.6020403@trajano.us.es>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Subject: [PWE3] A TDMPW per call o a TDMPW for multiple calls
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pwe3>, <mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pwe3>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 23 Dec 2011 11:53:33 -0000

What is more efficient?

(a) a TDMPW per call

or

(b) a TDMPW for multiple calls (muxing).

A think (b) it requires less overhead and less control plane messages.

Regards,

Javi



From yaakov_s@rad.com  Sun Dec 25 08:42:22 2011
Return-Path: <yaakov_s@rad.com>
X-Original-To: pwe3@ietfa.amsl.com
Delivered-To: pwe3@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3985821F845A for <pwe3@ietfa.amsl.com>; Sun, 25 Dec 2011 08:42:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.698
X-Spam-Level: 
X-Spam-Status: No, score=-101.698 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_22=0.6, MIME_8BIT_HEADER=0.3, UNPARSEABLE_RELAY=0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VdfGKbDSicWz for <pwe3@ietfa.amsl.com>; Sun, 25 Dec 2011 08:42:21 -0800 (PST)
Received: from rad.co.il (mailrelay01.rad.co.il [62.0.23.252]) by ietfa.amsl.com (Postfix) with ESMTP id 08B6A21F8450 for <pwe3@ietf.org>; Sun, 25 Dec 2011 08:42:18 -0800 (PST)
Received: from Internal Mail-Server by MailRelay01 (envelope-from yaakov?s@rad.com) with AES128-SHA encrypted SMTP; 25 Dec 2011 18:33:42 +0200
Received: from EXRAD5.ad.rad.co.il ([192.114.24.28]) by EXRAD5.ad.rad.co.il ([192.114.24.28]) with mapi id 14.01.0323.003; Sun, 25 Dec 2011 18:42:15 +0200
From: Yaakov Stein <yaakov_s@rad.com>
To: =?Windows-1252?Q?Javi_Mu=F1oz?= <javi@trajano.us.es>, "pwe3@ietf.org" <pwe3@ietf.org>
Thread-Topic: [PWE3] A TDMPW per call o a TDMPW for multiple calls
Thread-Index: AQHMwWmHHACzFhTE6kab/i8fIHdhT5XsxQvQ
Date: Sun, 25 Dec 2011 16:42:14 +0000
Message-ID: <07F7D7DED63154409F13298786A2ADC9042A6123@EXRAD5.ad.rad.co.il>
References: <4EE63982.7020403@trajano.us.es> <07F7D7DED63154409F13298786A2ADC90427FBB4@EXRAD5.ad.rad.co.il> <4EE73621.1090802@trajano.us.es> <07F7D7DED63154409F13298786A2ADC9042831D9@EXRAD5.ad.rad.co.il> <4EE87FF4.5090704@trajano.us.es> <07F7D7DED63154409F13298786A2ADC90429ABF6@EXRAD5.ad.rad.co.il> <4EEE1F41.6020403@trajano.us.es> <4EF46BE4.6050101@trajano.us.es>
In-Reply-To: <4EF46BE4.6050101@trajano.us.es>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.115.243.62]
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [PWE3] A TDMPW per call o a TDMPW for multiple calls
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pwe3>, <mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pwe3>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 25 Dec 2011 16:42:22 -0000

Javi

As these discussions apparently do not interest most of the readers of this=
 list,
I propose that if you have further questions that we continue the discussio=
n off-list
(as we have been doing for the past week).

Y(J)S

-----Original Message-----
From: pwe3-bounces@ietf.org [mailto:pwe3-bounces@ietf.org] On Behalf Of Jav=
i Mu?oz
Sent: Friday, December 23, 2011 13:54
To: pwe3@ietf.org
Subject: [PWE3] A TDMPW per call o a TDMPW for multiple calls

What is more efficient?

(a) a TDMPW per call

or

(b) a TDMPW for multiple calls (muxing).

A think (b) it requires less overhead and less control plane messages.

Regards,

Javi


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