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

<benjamin.niven-jenkins@bt.com> Fri, 02 April 2010 11:40 UTC

Return-Path: <benjamin.niven-jenkins@bt.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 6BB923A677E; Fri, 2 Apr 2010 04:40:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.916
X-Spam-Level:
X-Spam-Status: No, score=-0.916 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, DNS_FROM_OPENWHOIS=1.13, HELO_MISMATCH_COM=0.553]
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 QepXBhwLBJSx; Fri, 2 Apr 2010 04:40:39 -0700 (PDT)
Received: from smtpe1.intersmtp.com (smtp61.intersmtp.COM [62.239.224.234]) by core3.amsl.com (Postfix) with ESMTP id 6C39B3A6900; Fri, 2 Apr 2010 04:38:59 -0700 (PDT)
Received: from EVMHT66-UKRD.domain1.systemhost.net (10.36.3.103) by RDW083A005ED61.smtp-e1.hygiene.service (10.187.98.10) with Microsoft SMTP Server (TLS) id 8.1.393.1; Fri, 2 Apr 2010 12:39:15 +0100
Received: from EMV65-UKRD.domain1.systemhost.net ([169.254.1.222]) by EVMHT66-UKRD.domain1.systemhost.net ([10.36.3.103]) with mapi; Fri, 2 Apr 2010 12:39:32 +0100
From: benjamin.niven-jenkins@bt.com
To: Alexander.Vainshtein@ecitele.com, adrian@olddog.co.uk
Date: Fri, 02 Apr 2010 12:39:28 +0100
Thread-Topic: [CCAMP] [mpls] Term "PSC"indraft-ietf-mpls-tp-linear-protection-01
Thread-Index: AcrL8UXTy/5QKB/HSvmNL816886NAAABtBiAAZhELCQ=
Message-ID: <C7DB9600.1405D%benjamin.niven-jenkins@bt.com>
In-Reply-To: <A3C5DF08D38B6049839A6F553B331C76C10809F659@ILPTMAIL02.ecitele.com>
Accept-Language: en-US, en-GB
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-Entourage/13.3.0.091002
acceptlanguage: en-US, en-GB
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: mpls@ietf.org, CCAMP@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: Fri, 02 Apr 2010 11:40:40 -0000

LOL, if only I had got around to reading this e-mail yesterday :-) Ben


On 25/03/2010 08:52, "Alexander Vainshtein"
<Alexander.Vainshtein@ecitele.com> wrote:

> 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
>> 
> 
> _______________________________________________
> CCAMP mailing list
> CCAMP@ietf.org
> https://www.ietf.org/mailman/listinfo/ccamp