IETF Logo Mail Archive

Re: [mpls] [CCAMP] Term "PSC" indraft-ietf-mpls-tp-linear-protection-01

Alexander Vainshtein <Alexander.Vainshtein@ecitele.com> Thu, 25 March 2010 08:52 UTC

Return-Path: <Alexander.Vainshtein@ecitele.com>
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 25EF23A6AF2; Thu, 25 Mar 2010 01:52:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.819
X-Spam-Level:
X-Spam-Status: No, score=-0.819 tagged_above=-999 required=5 tests=[AWL=0.650, BAYES_00=-2.599, DNS_FROM_OPENWHOIS=1.13]
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 d5n3GnBcPCjs; Thu, 25 Mar 2010 01:52:09 -0700 (PDT)
Received: from ilptbmg01.ecitele.com (ilptbmg01-out.ecitele.com [147.234.242.234]) by core3.amsl.com (Postfix) with ESMTP id AD9B83A6909; Thu, 25 Mar 2010 01:52:06 -0700 (PDT)
X-AuditID: 93eaf2e7-b7b62ae000003814-d3-4bab221a08dc
Received: from ILPTEXCH02.ecitele.com ( [147.234.245.181]) by ilptbmg01.ecitele.com (Symantec Brightmail Gateway) with SMTP id D8.32.14356.A122BAB4; Thu, 25 Mar 2010 10:43:07 +0200 (IST)
Received: from ILPTMAIL02.ecitele.com ([147.234.244.212]) by ILPTEXCH02.ecitele.com ([147.234.245.181]) with mapi; Thu, 25 Mar 2010 10:52:26 +0200
From: Alexander Vainshtein <Alexander.Vainshtein@ecitele.com>
To: Adrian Farrel <adrian@olddog.co.uk>
Date: Thu, 25 Mar 2010 10:52:25 +0200
Thread-Topic: [CCAMP] [mpls] Term "PSC" indraft-ietf-mpls-tp-linear-protection-01
Thread-Index: AcrL8UXTy/5QKB/HSvmNL816886NAAABtBiA
Message-ID: <A3C5DF08D38B6049839A6F553B331C76C10809F659@ILPTMAIL02.ecitele.com>
References: <8bf39341003231036w3ceaac70l18ee403c034da761@mail.gmail.com><8bf39341003240120r554b72j3f6b924475a11d3c@mail.gmail.com> <A3C5DF08D38B6049839A6F553B331C76C1078FB66E@ILPTMAIL02.ecitele.com> <239F5ECAA0574FB4A0003E9EC88F5D30@your029b8cecfe>
In-Reply-To: <239F5ECAA0574FB4A0003E9EC88F5D30@your029b8cecfe>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: AAAAAA==
Cc: "mpls@ietf.org" <mpls@ietf.org>, "CCAMP@ietf.org" <CCAMP@ietf.org>, "mpls-tp@ietf.org" <mpls-tp@ietf.org>
Subject: Re: [mpls] [CCAMP] Term "PSC" indraft-ietf-mpls-tp-linear-protection-01
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Thu, 25 Mar 2010 08:52:10 -0000

Adrian,
Lots of thanks for pointing to 5513, I've missed its publication.
IMHO and FWIW (which are not covered by 5513) it is extremely relevant for the MPLS-TP project.
Do you consider 5513bis to cover MPLS-TP?

Regards,
     Sasha

-----Original Message-----
From: Adrian Farrel [mailto:adrian@olddog.co.uk] 
Sent: Thursday, March 25, 2010 9:56 AM
To: Alexander Vainshtein; Vivien Sterling
Cc: mpls@ietf.org; CCAMP@ietf.org; mpls-tp@ietf.org
Subject: Re: [CCAMP] [mpls] Term "PSC" indraft-ietf-mpls-tp-linear-protection-01

For issues related to clashes of acronyms please see RFC 5513.


----- Original Message ----- 
From: "Alexander Vainshtein" <Alexander.Vainshtein@ecitele.com>
To: "Vivien Sterling" <vivien.sterling@gmail.com>
Cc: <mpls@ietf.org>; <CCAMP@ietf.org>; <mpls-tp@ietf.org>
Sent: Wednesday, March 24, 2010 8:30 AM
Subject: Re: [CCAMP] [mpls] Term "PSC" 
indraft-ietf-mpls-tp-linear-protection-01


Vivien and all,
AFAIK, PSC stands for "Protection State Coordination" in the MPLS-TP 
parlance (see MPLS-TP Survivability 
Framework<http://datatracker.ietf.org/doc/draft-ietf-mpls-tp-survive-fwk/>)  
- a new fancy name for what has been known as "APS Protocol" in SONET/SDH.

As you've noted, it has a completely different meaning in GMPLS.

Since GMPLS is going to be used with MPLS-TP, double usage of this acronym 
looks highly problematic.

Regards,
     Sasha

From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf Of 
Vivien Sterling
Sent: Wednesday, March 24, 2010 10:21 AM
To: CCAMP@ietf.org; mpls@ietf.org; mpls-tp@ietf.org
Subject: [mpls] Term "PSC" in draft-ietf-mpls-tp-linear-protection-01

Dear Experts,

I'm surprised to find the term "PSC" used in this draft. I suppose the 
authors are talking about data plane not control plane, right? Isn't PSC in 
GMPLS elaborated as "Packet Switch Capable" ? It's confusing :-(

--
Cheers,
Vivien



--------------------------------------------------------------------------------


> _______________________________________________
> CCAMP mailing list
> CCAMP@ietf.org
> https://www.ietf.org/mailman/listinfo/ccamp
>

v2.23.0 | Report a Bug | By Email