Re: [PWE3] draft-manhoudt-pwe3-tsop-00.txt and IP

Yaakov Stein <yaakov_s@rad.com> Wed, 18 July 2012 09:25 UTC

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 AC65F21F861E for <pwe3@ietfa.amsl.com>; Wed, 18 Jul 2012 02:25:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.489
X-Spam-Level:
X-Spam-Status: No, score=-102.489 tagged_above=-999 required=5 tests=[AWL=0.109, BAYES_00=-2.599, 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 tMIk05KoteCK for <pwe3@ietfa.amsl.com>; Wed, 18 Jul 2012 02:25:06 -0700 (PDT)
Received: from rad.co.il (mailrelay02.rad.co.il [62.0.23.237]) by ietfa.amsl.com (Postfix) with ESMTP id C0C3021F8620 for <pwe3@ietf.org>; Wed, 18 Jul 2012 02:25:03 -0700 (PDT)
Received: from Internal Mail-Server by MailRelay02 (envelope-from yaakov?s@rad.com) with AES128-SHA encrypted SMTP; 18 Jul 2012 11:49:38 +0300
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.02.0298.004; Wed, 18 Jul 2012 12:25:51 +0300
From: Yaakov Stein <yaakov_s@rad.com>
To: "gmanhoudt@aimvalley.nl" <gmanhoudt@aimvalley.nl>, Alexander Vainshtein <Alexander.Vainshtein@ecitele.com>, "stbryant@cisco.com" <stbryant@cisco.com>
Thread-Topic: [PWE3] draft-manhoudt-pwe3-tsop-00.txt and IP
Thread-Index: AQHNXnGiS690goHnm0iu3kV86wpwkZciBfkAgAyK2wCAADQsEIAACYAA
Date: Wed, 18 Jul 2012 09:25:50 +0000
Message-ID: <07F7D7DED63154409F13298786A2ADC9044E9468@EXRAD5.ad.rad.co.il>
References: <20120709230133.15922.55905.idtracker@ietfa.amsl.com> <4FFBE04A.5010203@cisco.com> <F9336571731ADE42A5397FC831CEAA020997FF@FRIDWPPMB001.ecitele.com> <500674D8.1040601@aimvalley.nl>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [172.17.141.36]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Commtouch-Refid: str=0001.0A090203.50068120.0056,ss=1,fgs=0
Cc: "peter.roberts@alcatel-lucent.com" <peter.roberts@alcatel-lucent.com>, pwe3 <pwe3@ietf.org>, "stephan.roullot@alcatel-lucent.com" <stephan.roullot@alcatel-lucent.com>
Subject: Re: [PWE3] draft-manhoudt-pwe3-tsop-00.txt and IP
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, 18 Jul 2012 09:25:07 -0000

Gert and all, 

I would like to partially retract what I previously said about the S1 byte and traceability.
I hit the send too quickly, and should have thought over the issue first.

It is true that the SSM message relates information about traceability,
i.e., that after N SDH network elements a certain amount of phase noise has accumulated,
so that the bit stream does not obey the G.81x masks.
However, this is not applicable here.
Here the physical layer traceability is truly broken,
and you are relying on unexplained magic to restore it.

All that your statement about not dropping or adding bits guarantees is
lim_tau->infinity  MTIE(tau) / tau = 0, which is not enough.
The MTIE slope has to obey the constraint at some finite time.

Put in another way, stating that you don't drop or add bits is equivalent
to stating that you are somehow traceable to the original clock,
but since you broke the physical layer, and do not describe any mechanism
for recovery of that physical layer clock, in fact you WILL be forced
to have bit slips at the egress IWF.

So, simply saying that the SSM is correct by definition,
and relying on magic to restore the proper clock,
is not meaningful.

Sorry for my previous incorrect statements.

Y(J)S