Return-Path: X-Original-To: pwe3@core3.amsl.com Delivered-To: pwe3@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B5DE13A6887 for ; Mon, 14 Dec 2009 13:42:36 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.312 X-Spam-Level: X-Spam-Status: No, score=-6.312 tagged_above=-999 required=5 tests=[AWL=0.286, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RfVsrqFuNx-e for ; Mon, 14 Dec 2009 13:42:36 -0800 (PST) Received: from mail.us.es (mail.us.es [193.147.175.20]) by core3.amsl.com (Postfix) with ESMTP id 64F123A6849 for ; Mon, 14 Dec 2009 13:42:35 -0800 (PST) Received: (qmail 30469 invoked from network); 14 Dec 2009 22:42:17 +0100 Received: from unknown (HELO us.es) (192.168.2.11) by us.es with SMTP; 14 Dec 2009 22:42:17 +0100 Received: (qmail 9724 invoked by uid 507); 14 Dec 2009 21:42:18 -0000 Received: from 127.0.0.1 by antivirus1 (envelope-from , uid 501) with qmail-scanner-2.06 (clamdscan: 0.95.3/10169. Clear:RC:1(127.0.0.1):. Processed in 0.037904 secs); 14 Dec 2009 21:42:18 -0000 Received: from unknown (HELO us.es) (127.0.0.1) by us.es with SMTP; 14 Dec 2009 21:42:18 -0000 Received: (qmail 9606 invoked from network); 14 Dec 2009 22:42:14 +0100 Received: from unknown (HELO trajano.us.es) (193.147.162.130) by us.es with (DHE-RSA-AES256-SHA encrypted) SMTP; 14 Dec 2009 22:42:14 +0100 Received: from [192.168.1.40] (trajano.us.es [193.147.162.130]) (authenticated bits=0) by trajano.us.es (8.13.8/8.13.8/Debian-3) with ESMTP id nBELgHh7029192; Mon, 14 Dec 2009 22:42:18 +0100 Message-ID: <4B26B136.5000907@trajano.us.es> Date: Mon, 14 Dec 2009 22:42:14 +0100 From: Javi User-Agent: Thunderbird 2.0.0.23 (Windows/20090812) MIME-Version: 1.0 To: "pwe3@ietf.org" References: <4763642.1259522511830.JavaMail.root@viefep14> <4B12E258.5070708@trajano.us.es> <48E7911F78327A449A9FB956376672863360CD06@exrad4.ad.rad.co.il> <4B1582BA.8040803@trajano.us.es> <48E7911F78327A449A9FB956376672863413B9AA@exrad4.ad.rad.co.il> <4B1822D5.40904@trajano.us.es> <4B22E4E5.9080107@trajano.us.es> <48E7911F78327A449A9FB956376672863462A347@exrad4.ad.rad.co.il> <4B267EB2.8040301@trajano.us.es> In-Reply-To: <4B267EB2.8040301@trajano.us.es> Content-Type: multipart/alternative; boundary="------------030709040509000404040206" Cc: Yaakov Stein Subject: Re: [PWE3] TDM Channels and TDMPW Payload X-BeenThere: pwe3@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Pseudo Wires Edge to Edge List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Dec 2009 21:42:36 -0000 This is a multi-part message in MIME format. --------------030709040509000404040206 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Thanks. Any about this? [YJS] Yes, trunk defects can be so indicated. If the AAL2 channels come from a single E1 or T1 you can use the L, R and M. [Javi-New] ITU-T Recommendation Y.1452 (clause 8.3.1), describing TDMoIP AAL.2, indicates bits R, M of the CW are reserved (value always 0). The, if a TDMPW AAL.2 can emulate a full trunk, where does it carry circuit level defects? Regards, Javi --------------030709040509000404040206 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit

Thanks. Any about this?

[YJS] Yes, trunk defects can be so indicated. If the AAL2 channels come from a single E1 or T1 you can use the L, R and M.

[Javi-New] ITU-T Recommendation Y.1452 (clause 8.3.1),  describing TDMoIP AAL.2, indicates bits R, M of the CW are reserved (value always 0). The, if a TDMPW AAL.2 can emulate a full trunk, where does it carry circuit level defects?

Regards,

Javi
--------------030709040509000404040206--