IETF Logo Mail Archive

Re: [Mpls-interop] Who will be in Geneva?

"Sprecher, Nurit (NSN - IL/Hod HaSharon)" <nurit.sprecher@nsn.com> Tue, 02 December 2008 11:38 UTC

Return-Path: <mpls-interop-bounces@ietf.org>
X-Original-To: mpls-interop-archive@ietf.org
Delivered-To: ietfarch-mpls-interop-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 029C83A67D7; Tue, 2 Dec 2008 03:38:15 -0800 (PST)
X-Original-To: mpls-interop@core3.amsl.com
Delivered-To: mpls-interop@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 622D43A68FC for <mpls-interop@core3.amsl.com>; Tue, 2 Dec 2008 03:38:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.932
X-Spam-Level:
X-Spam-Status: No, score=-5.932 tagged_above=-999 required=5 tests=[AWL=0.667, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 WO2TgPYodmKq for <mpls-interop@core3.amsl.com>; Tue, 2 Dec 2008 03:38:12 -0800 (PST)
Received: from demumfd001.nsn-inter.net (demumfd001.nsn-inter.net [217.115.75.233]) by core3.amsl.com (Postfix) with ESMTP id 3A7543A67D7 for <mpls-interop@ietf.org>; Tue, 2 Dec 2008 03:38:12 -0800 (PST)
Received: from demuprx016.emea.nsn-intra.net ([10.150.129.55]) by demumfd001.nsn-inter.net (8.12.11.20060308/8.12.11) with ESMTP id mB2Bc4in023301 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Tue, 2 Dec 2008 12:38:04 +0100
Received: from demuexc024.nsn-intra.net (demuexc024.nsn-intra.net [10.159.32.11]) by demuprx016.emea.nsn-intra.net (8.12.11.20060308/8.12.11) with ESMTP id mB2Bc2Z0021239; Tue, 2 Dec 2008 12:38:04 +0100
Received: from DEMUEXC030.nsn-intra.net ([10.150.128.57]) by demuexc024.nsn-intra.net with Microsoft SMTPSVC(6.0.3790.3959); Tue, 2 Dec 2008 12:38:03 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Tue, 2 Dec 2008 12:37:59 +0100
Message-ID: <43284B5A95E36B4AB4A91EBA4E0FC31EFE0C84@DEMUEXC030.nsn-intra.net>
In-Reply-To: <2095F13194CC41BDB8FE61BC7A8187AB@your029b8cecfe>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [Mpls-interop] Who will be in Geneva?
Thread-Index: AclUcUxh976NhLIzRSaCPszRWDCReAAAPwfw
References: <A79C9B7D57B940FF802C8395F15E232E@your029b8cecfe> <C55A12D2.EB1D%benjamin.niven-jenkins@bt.com> <43284B5A95E36B4AB4A91EBA4E0FC31EFE09F2@DEMUEXC030.nsn-intra.net> <43284B5A95E36B4AB4A91EBA4E0FC31EFE09F3@DEMUEXC030.nsn-intra.net> <49350F0B.8060605@alcatel-lucent.com> <43284B5A95E36B4AB4A91EBA4E0FC31EFE0C10@DEMUEXC030.nsn-intra.net> <493512FC.70700@alcatel-lucent.com> <43284B5A95E36B4AB4A91EBA4E0FC31EFE0C35@DEMUEXC030.nsn-intra.net> <2095F13194CC41BDB8FE61BC7A8187AB@your029b8cecfe>
From: "Sprecher, Nurit (NSN - IL/Hod HaSharon)" <nurit.sprecher@nsn.com>
To: "Adrian Farrel" <adrian@olddog.co.uk>, "ext Martin Vigoureux" <martin.vigoureux@alcatel-lucent.com>
X-OriginalArrivalTime: 02 Dec 2008 11:38:03.0515 (UTC) FILETIME=[6FC7F4B0:01C95472]
Cc: mpls-interop@ietf.org
Subject: Re: [Mpls-interop] Who will be in Geneva?
X-BeenThere: mpls-interop@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF MPLS Interoperability Design Team <mpls-interop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls-interop>, <mailto:mpls-interop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/mpls-interop>
List-Post: <mailto:mpls-interop@ietf.org>
List-Help: <mailto:mpls-interop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls-interop>, <mailto:mpls-interop-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mpls-interop-bounces@ietf.org
Errors-To: mpls-interop-bounces@ietf.org

The main issue with "LSP Hierarchy" is that it is strange to use it for
a part of MS-PW (one or more segments of a PW). 

-----Original Message-----
From: ext Adrian Farrel [mailto:adrian@olddog.co.uk] 
Sent: Tuesday, December 02, 2008 13:30
To: Sprecher, Nurit (NSN - IL/Hod HaSharon); ext Martin Vigoureux
Cc: ext Ben Niven-Jenkins; mpls-interop@ietf.org
Subject: Re: [Mpls-interop] Who will be in Geneva?

> First, protection switching in MPLS-TP is independent of the control
> plane...we can have protection switching even in the absence of a CP.

Yes

> Second, GMPLS segment protection really uses LSP hierarchy for
> protecting a segment......

No!

There are many solutions.
I have warned about using the term "segment protection".
I will warn again.

GMPLS "Segment protection" (RFC 4873) does NOT (that is, not, not, not)
use 
hierarchy.
(Did I say "not"?)

> TC (or what ever name you select) provides you a clean architectural
> way to initiate and terminate messages for a part of a path (segment).
> This can be used for OAM, protection and maybe other purposes in
> the future as well.

I also wish you would stop using the term TC because it is just
confusing 
things.

If what you want to say is that hierarchcial agregation is useful, then
we 
will agree.
It can be used to provide OAM for a part of an LSP path.
It can be used to aggregate OAM for a set of LSPs that are parallel for
part 
of their paths.
It can be used to aggregate protection for a set of LSPs that are
parallel 
for part of their paths.

This is LSP hierarchy. No need for other terms.

Adrian


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

v2.8.7 | Report a Bug | By Email