IETF Logo Mail Archive

Re: [PWE3] [mpls] WG Last Call for draft-ietf-pwe3-endpoint-fast-protection-01 - RFC4447

Yimin Shen <yshen@juniper.net> Fri, 08 August 2014 14:00 UTC

Return-Path: <yshen@juniper.net>
X-Original-To: pwe3@ietfa.amsl.com
Delivered-To: pwe3@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E61791B2A31; Fri, 8 Aug 2014 07:00:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.602
X-Spam-Level:
X-Spam-Status: No, score=-2.602 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dZtueEZFWAf6; Fri, 8 Aug 2014 07:00:39 -0700 (PDT)
Received: from na01-bl2-obe.outbound.protection.outlook.com (mail-bl2lp0211.outbound.protection.outlook.com [207.46.163.211]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CEBC71B29CD; Fri, 8 Aug 2014 07:00:38 -0700 (PDT)
Received: from BY2PR05MB728.namprd05.prod.outlook.com (10.141.223.25) by BY2PR05MB728.namprd05.prod.outlook.com (10.141.223.25) with Microsoft SMTP Server (TLS) id 15.0.995.14; Fri, 8 Aug 2014 14:00:29 +0000
Received: from BY2PR05MB728.namprd05.prod.outlook.com ([10.141.223.25]) by BY2PR05MB728.namprd05.prod.outlook.com ([10.141.223.25]) with mapi id 15.00.0995.014; Fri, 8 Aug 2014 14:00:29 +0000
From: Yimin Shen <yshen@juniper.net>
To: Loa Andersson <loa@pi.nu>, Mingui Zhang <zhangmingui@huawei.com>, "Stewart Bryant (stbryant)" <stbryant@cisco.com>
Thread-Topic: [PWE3] [mpls] WG Last Call for draft-ietf-pwe3-endpoint-fast-protection-01 - RFC4447
Thread-Index: AQHPsut9xMpTT3UKUUu7y8CePcLxcpvGtyQQ
Date: Fri, 08 Aug 2014 14:00:28 +0000
Message-ID: <496a2c137775477c8c78c7e8d5463c6e@BY2PR05MB728.namprd05.prod.outlook.com>
References: Your message of Tue, 05 Aug 2014 13:59:49 -0000. <9696d0db139d46ffaad7be11340215e8@AM3PR03MB612.eurprd03.prod.outlook.com> <16167.1407340459@erosen-lnx>, <4552F0907735844E9204A62BBDD325E76AAAA7F4@nkgeml512-mbx.china.huawei.com> <22D4AECA-2D36-4F79-98CB-96E4B9BDC126@cisco.com> <4552F0907735844E9204A62BBDD325E76AAAB6F9@nkgeml512-mbx.china.huawei.com> <53E498D4.6000107@pi.nu>
In-Reply-To: <53E498D4.6000107@pi.nu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [66.129.241.10]
x-microsoft-antispam: BCL:0;PCL:0;RULEID:
x-forefront-prvs: 02973C87BC
x-forefront-antispam-report: SFV:NSPM; SFS:(6009001)(377424004)(252514010)(164054003)(51704005)(13464003)(189002)(199002)(24454002)(377454003)(76576001)(50986999)(99396002)(74662001)(81342001)(106356001)(106116001)(76176999)(54356999)(33646002)(93886004)(74316001)(80022001)(85306004)(79102001)(66066001)(105586002)(81542001)(99286002)(95666004)(64706001)(20776003)(4396001)(83322001)(76482001)(19580405001)(15975445006)(74502001)(86362001)(2656002)(46102001)(107046002)(21056001)(19580395003)(85852003)(87936001)(77982001)(101416001)(83072002)(24736002)(108616003); DIR:OUT; SFP:; SCL:1; SRVR:BY2PR05MB728; H:BY2PR05MB728.namprd05.prod.outlook.com; FPR:; MLV:sfv; PTR:InfoNoRecords; MX:1; LANG:en;
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
Archived-At: http://mailarchive.ietf.org/arch/msg/pwe3/8YEHJp7ftHEKkBzM2lSlwTJqyKg
Cc: "mpls@ietf.org" <mpls@ietf.org>, "Eric Rosen (erosen)" <erosen@cisco.com>, pwe3 <pwe3@ietf.org>, "pwe3-chairs@tools.ietf.org" <pwe3-chairs@tools.ietf.org>
Subject: Re: [PWE3] [mpls] WG Last Call for draft-ietf-pwe3-endpoint-fast-protection-01 - RFC4447
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Pseudowire Emulation Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pwe3>, <mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pwe3/>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 08 Aug 2014 14:00:42 -0000

Hi Loa,

This draft assumes decoupled control plane and dataplane architecture of routers, and it requires that the backup path (or backup forwarding state) be pre-programmed in the dataplane on PLR. Hence when the dataplane (of PLR) detects a failure, it is able to restore traffic locally and independently by redirecting traffic over the preprogrammed backup path. This is generally assumed to be faster that mechanisms that involve control plane protocols, or end-to-end messaging or OAM, because there is no event propagation delay. I believe this is a common assumption for all IP/MPLS FRR mechanisms.

It will not be a problem if this mechanism and an e2e mechanism are both implemented in a network. As described in the draft, this mechanism provides local repair, and it is viewed as a temporary repair. The draft strongly recommend this mechanism to be used in tandem with an e2e or global repair mechanism, so that the later can eventually move traffic from the locally repaired PW over to a fully functional PW, as a permanent repair.


Thanks,

/Yimin


-----Original Message-----
From: pwe3 [mailto:pwe3-bounces@ietf.org] On Behalf Of Loa Andersson
Sent: Friday, August 08, 2014 5:31 AM
To: Mingui Zhang; Stewart Bryant (stbryant)
Cc: mpls@ietf.org; Eric Rosen (erosen); pwe3; pwe3-chairs@tools.ietf.org
Subject: Re: [PWE3] [mpls] WG Last Call for draft-ietf-pwe3-endpoint-fast-protection-01 - RFC4447

Authors, Mingui, Stewart

On 2014-08-08 04:46, Mingui Zhang wrote:
> Hi Stewart,
>
> I think authors would say the S-PE stitching method involves the control plane processing during the repair procedure. They emphasized their method uses data plane & local repair, which can be faster.
> Here, I want to raise one issue:

It seems that we take it for granted that the method proposed on this draft is faster than e.g. the e2e protection a la mpls-tp. Why is that?
If we have implementations of both, do we have any real measurements?

/Loa

-- 


Loa Andersson                        email: loa@mail01.huawei.com
Senior MPLS Expert                          loa@pi.nu
Huawei Technologies (consultant)     phone: +46 739 81 21 64

_______________________________________________
pwe3 mailing list
pwe3@ietf.org
https://www.ietf.org/mailman/listinfo/pwe3

v2.23.0 | Report a Bug | By Email