Re: [mpls] PSC: draft-rhd-mpls-tp-psc-sd-00

Gregory Mirsky <gregory.mirsky@ericsson.com> Mon, 22 April 2013 17:57 UTC

Return-Path: <gregory.mirsky@ericsson.com>
X-Original-To: mpls@ietfa.amsl.com
Delivered-To: mpls@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E407C21F93CC for <mpls@ietfa.amsl.com>; Mon, 22 Apr 2013 10:57:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pCbtkN8EYoHN for <mpls@ietfa.amsl.com>; Mon, 22 Apr 2013 10:57:39 -0700 (PDT)
Received: from usevmg20.ericsson.net (usevmg20.ericsson.net [198.24.6.45]) by ietfa.amsl.com (Postfix) with ESMTP id 2877F21F93BE for <mpls@ietf.org>; Mon, 22 Apr 2013 10:57:39 -0700 (PDT)
X-AuditID: c618062d-b7f0d6d00000097e-13-51757a12ceef
Received: from EUSAAHC004.ericsson.se (Unknown_Domain [147.117.188.84]) by usevmg20.ericsson.net (Symantec Mail Security) with SMTP id 11.2C.02430.21A75715; Mon, 22 Apr 2013 19:57:38 +0200 (CEST)
Received: from EUSAAMB106.ericsson.se ([147.117.188.123]) by EUSAAHC004.ericsson.se ([147.117.188.84]) with mapi id 14.02.0318.004; Mon, 22 Apr 2013 13:57:38 -0400
From: Gregory Mirsky <gregory.mirsky@ericsson.com>
To: Alexander Vainshtein <Alexander.Vainshtein@ecitele.com>, "Eric Osborne (eosborne)" <eosborne@cisco.com>
Thread-Topic: PSC: draft-rhd-mpls-tp-psc-sd-00
Thread-Index: Ac47ZjCR0vbHo3uJROyqNlG6qZXPnwDP/26gADbl9CA=
Date: Mon, 22 Apr 2013 17:57:36 +0000
Message-ID: <7347100B5761DC41A166AC17F22DF1121B48605B@eusaamb106.ericsson.se>
References: <20ECF67871905846A80F77F8F4A27572101502B9@xmb-rcd-x09.cisco.com> <F9336571731ADE42A5397FC831CEAA0212303FA6@ILPTWPVEXMB02.ecitele.com>
In-Reply-To: <F9336571731ADE42A5397FC831CEAA0212303FA6@ILPTWPVEXMB02.ecitele.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [147.117.188.134]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrILMWRmVeSWpSXmKPExsUyuXRPiK5QVWmgwarZuhZTt35gtmias5nR om3xIjaLW0tXslq8ezOLyYHVY8rvjawem/4dZ/RYsuQnUwBzFJdNSmpOZllqkb5dAlfG64mn 2Ap+iVdcWP2VpYFxm3AXIyeHhICJRNfudUwQtpjEhXvr2UBsIYGjjBIHN5h1MXIB2csZJT7/ OccMkmATMJJ4sbGHHcQWEciVeLJ6J1ADBwezQLnEv2mCIGFhAT2JXZMfs0CU6EvcWXGWEcK2 kjh4YBYriM0ioCpx4vt9sJG8Ar4SR37tY4HYNZlR4uPMnWANnAKBEntausBsRqDjvp9aA3Yo s4C4xK0n86GOFpBYsuc8M4QtKvHy8T9WCFtZYsmT/SwQ9ToSC3Z/YoOwtSWWLXwNtVhQ4uTM JywTGMVmIRk7C0nLLCQts5C0LGBkWcXIUVqcWpabbmSwiREYTcck2HR3MO55aXmIUZqDRUmc N8j1QoCQQHpiSWp2ampBalF8UWlOavEhRiYOTqkGxuoXpTpXTS6mS04zuC+XwKy2ekJf0u9g hwkMYbOUJr6JebrhA6OUxIKmqsaeHmk+4+ScEpk1RaWpWz5s+PqTJzxHSaqvJjPsscSOG2F7 q42t3ZLlt/fUWfK/+hYj0fD4vN3dFJbfl3ce/l75Wi2e4eeek0YOqyPYZOLDeIO429Y/aFOu 3fNBiaU4I9FQi7moOBEAYYNDMnQCAAA=
Cc: "mpls@ietf.org" <mpls@ietf.org>, Gideon Agmon <Gideon.Agmon@ecitele.com>, Shell Nakash <Shell.Nakash@ecitele.com>
Subject: Re: [mpls] PSC: draft-rhd-mpls-tp-psc-sd-00
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Apr 2013 17:57:40 -0000

Dear Sasha, Eric, et al.,
I too share Sasha's concern in regard to SD in packet transport networks. I think that before we as WG discuss SD handling by PSC, the SD in Packet Transport Network must be clearly defined. Otherwise it looks as we've been asked to discuss Something Happens and You Must React.

	Regards,
		Greg

-----Original Message-----
From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf Of Alexander Vainshtein
Sent: Sunday, April 21, 2013 8:45 AM
To: Eric Osborne (eosborne)
Cc: mpls@ietf.org; Shell Nakash; Gideon Agmon
Subject: Re: [mpls] PSC: draft-rhd-mpls-tp-psc-sd-00

Eric, and all,
The issue has been discussed actively in the past.

I can only re-state my position during these discussions, namely that there is no way to define a reasonable analog of Signal Degrade (SD) in MPLS and, by implication, in the MPLS-TP data plane. By "reasonable" here I mean a method that does not depend on the actual traffic going thru the LSP.

The fact that we could not reach any consensus for such a definition in the past is not, of course, a mathematical proof of non-existence of SD.
But it is a good indication of a fundamental problem IMO.

As a consequence, IMHO and FWIW, there is no need in defining SD-related state transitions, behavior etc.

My 2c,
     Sasha

> -----Original Message-----
> From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf 
> Of Eric Osborne (eosborne)
> Sent: Wednesday, April 17, 2013 3:26 PM
> To: mpls@ietf.org
> Subject: [mpls] PSC: draft-rhd-mpls-tp-psc-sd-00
> 
> This thread is for discussing draft-rhd-mpls-tp-psc-sd-00.  The draft 
> provided extensions to the PSC state machine to handle Signal Degrade 
> (SD).  It does not define SD or provide scope around where or how SD 
> may be used.  There are some expired drafts that touch on the definition and use of SD, including:
> 
> draft-zhl-mpls-tp-sd-03
> draft-rkhd-mpls-tp-sd-03
> 
> (this is not an exhaustive list.  It's the top two google hits.)
> 
> 
> The questions I think are relevant are:
> 
> - do we need an SD mechanism in MPLS-TP?
> - if so, is it reasonable to define state transitions for it before we 
> have defined SD itself?
> - if yes to both of the above, does this draft provide the right 
> behavior?  Are there alternative approaches?
> 
> but of course any and all discussion is welcome.
> 
> 
> 
> eric
> 
> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls


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.

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