Re: [mpls-tp] Linear Ether APS-g8031

Saravanan P <PSaravanan@ixiacom.com> Mon, 27 December 2010 09:30 UTC

Return-Path: <PSaravanan@ixiacom.com>
X-Original-To: mpls-tp@core3.amsl.com
Delivered-To: mpls-tp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id DA5B53A6801 for <mpls-tp@core3.amsl.com>; Mon, 27 Dec 2010 01:30:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.691
X-Spam-Level:
X-Spam-Status: No, score=-0.691 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, RCVD_ILLEGAL_IP=1.908]
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 7hK9bgafanGq for <mpls-tp@core3.amsl.com>; Mon, 27 Dec 2010 01:30:12 -0800 (PST)
Received: from ixqw-mail-out.ixiacom.com (ixqw-mail-out.ixiacom.com [66.77.12.12]) by core3.amsl.com (Postfix) with ESMTP id 96BE63A67A1 for <mpls-tp@ietf.org>; Mon, 27 Dec 2010 01:30:03 -0800 (PST)
Received: from ixcaexch07.ixiacom.com ([fe80:0000:0000:0000:e021:fcf5:238.143.231.20]) by IXCA-HC2.ixiacom.com ([10.200.2.51]) with mapi; Mon, 27 Dec 2010 01:31:58 -0800
From: Saravanan P <PSaravanan@ixiacom.com>
To: 'Huub van Helvoort' <huubatwork@gmail.com>
Date: Mon, 27 Dec 2010 01:32:07 -0800
Thread-Topic: [mpls-tp] Linear Ether APS-g8031
Thread-Index: AculpWouJVzLrbxFRkeT4z8cOmC1rQAAYa+w
Message-ID: <CFAB86E936BD6440B59B8FA25A792C060DF928DBA0@IXCAEXCH07.ixiacom.com>
References: <CFAB86E936BD6440B59B8FA25A792C060DF928DB9F@IXCAEXCH07.ixiacom.com> <4D18572B.3080609@gmail.com>
In-Reply-To: <4D18572B.3080609@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Cc: "mpls-tp@ietf.org" <mpls-tp@ietf.org>
Subject: Re: [mpls-tp] Linear Ether APS-g8031
X-BeenThere: mpls-tp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: MPLS-TP Mailing list <mpls-tp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls-tp>
List-Post: <mailto:mpls-tp@ietf.org>
List-Help: <mailto:mpls-tp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Dec 2010 09:30:24 -0000

Hello Huub,

Thanks for this clarification.
Can I consider flowing two drafts are different option for implementing APS in MPL-TP?

1) Linear Protection Switching in MPLS-TP  draft-zulr-mpls-tp-linear-protection-switching-01.txt

2) MPLS-TP Linear Protection  draft-ietf-mpls-tp-linear-protection-03.txt

Regards,
Saravanan.


-----Original Message-----
From: Huub van Helvoort [mailto:huubatwork@gmail.com]
Sent: Monday, December 27, 2010 2:37 PM
To: Saravanan P
Cc: mpls-tp@ietf.org
Subject: Re: [mpls-tp] Linear Ether APS-g8031

Hello Saravanan,

You wrote:

> I am implementing Ether APS channel functionality over pseudo wire/LSP
> and using BFD for CCM . As per my understanding Liner protection
> switching functionality shall be implemented by two standard
> IETF(draft-ietf-mpls-tp-linear-protection) and another one is I-TUT (g8031).

FYI: G.8031 is the linear protection for Ethernet.
G.8131 is linear protection for MPLS-TP, see also http://tools.ietf.org/html/draft-zulr-mpls-tp-linear-protection-switching
which is based on G.8131.

> CCM functionality would be either y.1731 or BFD but EtherAps should be
> g8031 or IETF.

The linear protection uses the SF (signal/service fail) as trigger.
SF detection can be based on MT-CCM defined in
http://tools.ietf.org/html/draft-bhh-mpls-tp-oam-y1731
or on extended BFD.

> Is this combination work in field and any one foresee interoperability
> issue?

The MT-CCM and G.8131 combination has been tested several times by EANTC and is deployed in China by major operators in many nodes.

> I don’t see anywhere in requirement document for g8031 as an APS
> option on LSP/PW.

As I mentioned above look for G.8131, but you will not find that in any requirement document as this is considered a solution of the generic "linear protection requirement".

Best regards, Huub.


--
*****************************************************************
                          我爱外点一七三一