Re: [mpls] PSC: draft-rhd-mpls-tp-psc-sd-00
"Eric Osborne (eosborne)" <eosborne@cisco.com> Mon, 22 April 2013 17:45 UTC
Return-Path: <eosborne@cisco.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 6EBEB21F912C for <mpls@ietfa.amsl.com>; Mon, 22 Apr 2013 10:45:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level:
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 b7gEneQnUbQe for <mpls@ietfa.amsl.com>; Mon, 22 Apr 2013 10:45:20 -0700 (PDT)
Received: from rcdn-iport-8.cisco.com (rcdn-iport-8.cisco.com [173.37.86.79]) by ietfa.amsl.com (Postfix) with ESMTP id 5F8B021F8E99 for <mpls@ietf.org>; Mon, 22 Apr 2013 10:45:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3398; q=dns/txt; s=iport; t=1366652720; x=1367862320; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=4kBAWN1uyZusmDw5N60QLjPrUujeaRcvvCywHvdymxU=; b=eLh1K7AhQhwSQbwdZnBHweS64NSZuK0BC3wEOBV5+NULbF8p+HJousRC 1QvBhwPsCb1c9wRlaEubQ2f8CguvLYtgQ28SowKgrbH9OmnwZ25EmyY9Z YWwj4XFd0mwkpfnkaqny6RLbBvR80hOEAAuXm4eiyw+H10nRNQ3A9pIQU g=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhgFAN12dVGtJXG//2dsb2JhbABPgwY2wQGBBhZ0gh8BAQEEAQEBNzQLDAQCAQgRBAEBCxQJBycLFAkIAQEEDgUIiAwMu00Ejg2BATEHBoJgYQOoL4MMgXM1
X-IronPort-AV: E=Sophos;i="4.87,528,1363132800"; d="scan'208";a="201602278"
Received: from rcdn-core2-4.cisco.com ([173.37.113.191]) by rcdn-iport-8.cisco.com with ESMTP; 22 Apr 2013 17:45:08 +0000
Received: from xhc-rcd-x01.cisco.com (xhc-rcd-x01.cisco.com [173.37.183.75]) by rcdn-core2-4.cisco.com (8.14.5/8.14.5) with ESMTP id r3MHj8JQ007013 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 22 Apr 2013 17:45:08 GMT
Received: from xmb-rcd-x09.cisco.com ([169.254.9.83]) by xhc-rcd-x01.cisco.com ([173.37.183.75]) with mapi id 14.02.0318.004; Mon, 22 Apr 2013 12:45:07 -0500
From: "Eric Osborne (eosborne)" <eosborne@cisco.com>
To: Alexander Vainshtein <Alexander.Vainshtein@ecitele.com>
Thread-Topic: PSC: draft-rhd-mpls-tp-psc-sd-00
Thread-Index: Ac47ZjCR0vbHo3uJROyqNlG6qZXPnwDP/26gADajjMA=
Date: Mon, 22 Apr 2013 17:45:06 +0000
Message-ID: <20ECF67871905846A80F77F8F4A275721015649D@xmb-rcd-x09.cisco.com>
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: [10.98.66.68]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "mpls@ietf.org" <mpls@ietf.org>, Shell Nakash <Shell.Nakash@ecitele.com>, Gideon Agmon <Gideon.Agmon@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:45:21 -0000
Hi Sasha- I tend to agree. I fully admit that PSC is a little inconsistent in these matters, in that it provides a place for SD in the alarm hierarchy but not in the state machine. However, I see little point in adding all the SD state machinery before we have some sort of SD mechanism. It may be that we come up with an SD mechanism that is more powerful than its analog in the transport world, and it might provide operators with significant flexibility that wouldn't be possible with the current proposal. Why come up with highway legislation that describes the rules of the road for flying hovercars prior to inventing the flying hovercar? eric > -----Original Message----- > From: Alexander Vainshtein [mailto:Alexander.Vainshtein@ecitele.com] > Sent: Sunday, April 21, 2013 11:45 AM > To: Eric Osborne (eosborne) > Cc: mpls@ietf.org; Rotem Cohen; Gideon Agmon; Yechiel Rosengarten; Shell > Nakash > Subject: RE: 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] PSC: draft-rhd-mpls-tp-psc-sd-00 Eric Osborne (eosborne)
- Re: [mpls] PSC: draft-rhd-mpls-tp-psc-sd-00 Alexander Vainshtein
- Re: [mpls] PSC: draft-rhd-mpls-tp-psc-sd-00 Eric Osborne (eosborne)
- Re: [mpls] PSC: draft-rhd-mpls-tp-psc-sd-00 Gregory Mirsky