Re: [mpls] MPLS-RT review of draft-bonica-mpls-self-ping

Ronald Bonica <rbonica@juniper.net> Thu, 19 March 2015 15:30 UTC

Return-Path: <rbonica@juniper.net>
X-Original-To: mpls@ietfa.amsl.com
Delivered-To: mpls@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E4D2A1A0A85 for <mpls@ietfa.amsl.com>; Thu, 19 Mar 2015 08:30:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.902
X-Spam-Level:
X-Spam-Status: No, score=-101.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] 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 M2TwRWPR8iIk for <mpls@ietfa.amsl.com>; Thu, 19 Mar 2015 08:30:39 -0700 (PDT)
Received: from na01-bl2-obe.outbound.protection.outlook.com (mail-bl2on0128.outbound.protection.outlook.com [65.55.169.128]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E2F851A0E10 for <mpls@ietf.org>; Thu, 19 Mar 2015 08:30:38 -0700 (PDT)
Received: from CO1PR05MB442.namprd05.prod.outlook.com (10.141.73.146) by CO1PR05MB441.namprd05.prod.outlook.com (10.141.73.147) with Microsoft SMTP Server (TLS) id 15.1.118.21; Thu, 19 Mar 2015 15:30:36 +0000
Received: from CO1PR05MB442.namprd05.prod.outlook.com ([169.254.13.69]) by CO1PR05MB442.namprd05.prod.outlook.com ([169.254.13.69]) with mapi id 15.01.0118.021; Thu, 19 Mar 2015 15:30:36 +0000
From: Ronald Bonica <rbonica@juniper.net>
To: Mach Chen <mach.chen@huawei.com>, "mpls-chairs@tools.ietf.org" <mpls-chairs@tools.ietf.org>, "draft-bonica-mpls-self-ping@tools.ietf.org" <draft-bonica-mpls-self-ping@tools.ietf.org>
Thread-Topic: MPLS-RT review of draft-bonica-mpls-self-ping
Thread-Index: AQHQVvDgK8HGVN8p4k2ca0R6IkmelJ0Ue/JggACc1ACAAAAxgIAO64CA
Date: Thu, 19 Mar 2015 15:30:35 +0000
Message-ID: <CO1PR05MB442E04BDF2D21601E396991AE010@CO1PR05MB442.namprd05.prod.outlook.com>
References: <F73A3CB31E8BE34FA1BBE3C8F0CB2AE28B3A416A@SZXEMA510-MBX.china.huawei.com> <F73A3CB31E8BE34FA1BBE3C8F0CB2AE28B3A4321@SZXEMA510-MBX.china.huawei.com>
In-Reply-To: <F73A3CB31E8BE34FA1BBE3C8F0CB2AE28B3A4321@SZXEMA510-MBX.china.huawei.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [66.129.241.14]
authentication-results: huawei.com; dkim=none (message not signed) header.d=none;
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:CO1PR05MB441;
x-microsoft-antispam-prvs: <CO1PR05MB441A273BB4A7DADB82E28C7AE010@CO1PR05MB441.namprd05.prod.outlook.com>
x-forefront-antispam-report: BMV:1; SFV:NSPM; SFS:(10019020)(6009001)(37854004)(66066001)(230783001)(86362001)(2501003)(106116001)(99286002)(2656002)(33656002)(87936001)(62966003)(77156002)(46102003)(122556002)(40100003)(74316001)(50986999)(54356999)(76176999)(2201001)(102836002)(2950100001)(92566002)(2900100001)(76576001); DIR:OUT; SFP:1102; SCL:1; SRVR:CO1PR05MB441; H:CO1PR05MB442.namprd05.prod.outlook.com; FPR:; SPF:None; MLV:sfv; LANG:en;
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(601004)(5005006)(5002010); SRVR:CO1PR05MB441; BCL:0; PCL:0; RULEID:; SRVR:CO1PR05MB441;
x-forefront-prvs: 052017CAF1
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
X-MS-Exchange-CrossTenant-originalarrivaltime: 19 Mar 2015 15:30:35.9632 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: bea78b3c-4cdb-4130-854a-1d193232e5f4
X-MS-Exchange-Transport-CrossTenantHeadersStamped: CO1PR05MB441
Archived-At: <http://mailarchive.ietf.org/arch/msg/mpls/9WgNguPkKK31JYyZ1G9nY0XZ34E>
Cc: "mpls@ietf.org" <mpls@ietf.org>, "mpls-ads@tools.ietf.org" <mpls-ads@tools.ietf.org>
Subject: Re: [mpls] MPLS-RT review of draft-bonica-mpls-self-ping
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 19 Mar 2015 15:30:46 -0000

Mach,

In a previous email, you said:

> 4. LSP Ping and BFD (especially S-BFD) are alternative tools for LSP readiness
> detection. If the scalability of control plane is the concern, there should be an
> analyses whether S-BFD cannot satisfy the requirement.

The following text addresses that issue.

                                         Ron


Text
====================================
Consider the following use case: 

- A network contains 100's of iLSRs
- Each iLSR is also an eLSR
- The network contains a full-mesh of RSVP-signaled LSPs (tens of thousands of LSPs)
- A network event occurs, causing half of those LSPs to re-signal
- RSVP churns, CPU's boil.....

Now, each iLSR needs to verify the readiness of its LSPs before attempting to forward traffic through them. The following are requirements of the mechanism used to verify readiness:

- it must return results quickly. (There is no time to set up session state or visit the control plane on the egress).
- it can consume only minimal control plane resources at the ingress
- it cannot consume any control plane resources whatsoever on the egress

The last requirement is very important. If the verification mechanism burns control plane resource on the egress, where CPUs are already saturated, network convergence time will suffer.

Only LSP Self ping fulfills the final requirement. Beyond that, LSP Self ping terminates as soon as it has verified LSP readiness.