Re: [Idr] draft-chen-idr-ctr-availability-00.txt

Huaimo Chen <huaimo.chen@futurewei.com> Thu, 19 March 2020 15:59 UTC

Return-Path: <huaimo.chen@futurewei.com>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 764123A081B for <idr@ietfa.amsl.com>; Thu, 19 Mar 2020 08:59:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, HTTPS_HTTP_MISMATCH=0.1, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=futurewei.com
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 0-JCUstuqvE0 for <idr@ietfa.amsl.com>; Thu, 19 Mar 2020 08:59:32 -0700 (PDT)
Received: from NAM11-BN8-obe.outbound.protection.outlook.com (mail-bn8nam11on2095.outbound.protection.outlook.com [40.107.236.95]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E94733A081A for <idr@ietf.org>; Thu, 19 Mar 2020 08:59:31 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=gWCohPBafby3tnarYK3u5rSW4KiE3TPduqQs+K1HO4BmRz2CUAL21L58NqGYr2F3WvvUTSC7zKzkpF+iVGZV+xLKNbCvfbALVGF+YU/5CSv2Szf42h3A36EHl6qPGGAIslBAJhqjcjo0x3TLgZffBhpvILUzNXx64SmoXFoRdPwvOZ3gvUWhjxu/GYKIv2Wvu6fKL6gQkYXtM55Qlln/WyXPEfzlNRnU5ubx565j3xtZstzWM+Pi8ECniVWHutSWXon511xuiK0q2ieNPvF1RWtoBMWDAI0xHs+rxc1PdywpJW5Exjx+5xOsEGMcAmrG0XW2307Ge8cPGYlY6UgHiw==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck;bh=71dGWfJjTYeJNU3ES1UPx1JdDptGwfX7+6eIgtAUD3g=; b=JECi/O3NasBQLWXclOr3fCxZM7w2XsSwY0+bOT2h6jQAKlCOryhacQxh/QNfn6DgyYEAP0aRx0S8EyYEutELE8gcgIXS0xhRMzYk+A2ipZkux/gL1+21qRsqJC0d7UAFi6tMgYdK26WpHM7KoLdv3L2PF430SMX8Ys05lIzDEtCn7yzehgLkTN9OofGATc7jAbyKsMVRH8ZAhKTGwKtgqIBwFAbhaqD8s79ALijtMZFKvmLmHXflwwzaf2kh4lRzlV1iQ94/QKSAmrGymL0dP+Mm0NwHSkeWKXNs6H/ENKGHOgD0dO4xG/FiJh6rscTSiRIff3TUO6MSS6+rkw04yA==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=futurewei.com; dmarc=pass action=none header.from=futurewei.com; dkim=pass header.d=futurewei.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=Futurewei.com; s=selector2; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck;bh=71dGWfJjTYeJNU3ES1UPx1JdDptGwfX7+6eIgtAUD3g=; b=J0JuTmYasq319+IhkZjB/yQMwtBLCrnKucUQJLkuo31pGCCtvpNgLD99y2LqttwfVs+VTJhX/Y3WolosI4MpA8QS+TWOsz/+/9rIho19ajAHC9vQSoZWhfPySFjc5cgAbA0U8uXHwxTgtZB1RFHgedHeq4OnkNSGVmimM5ZmUgk=
Received: from BY5PR13MB3651.namprd13.prod.outlook.com (2603:10b6:a03:22e::19) by BY5PR13MB2933.namprd13.prod.outlook.com (2603:10b6:a03:18e::32) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2835.6; Thu, 19 Mar 2020 15:59:30 +0000
Received: from BY5PR13MB3651.namprd13.prod.outlook.com ([fe80::b87d:8a82:886f:f088]) by BY5PR13MB3651.namprd13.prod.outlook.com ([fe80::b87d:8a82:886f:f088%9]) with mapi id 15.20.2835.017; Thu, 19 Mar 2020 15:59:29 +0000
From: Huaimo Chen <huaimo.chen@futurewei.com>
To: Robert Raszuk <robert@raszuk.net>, "idr@ietf. org" <idr@ietf.org>
Thread-Topic: [Idr] draft-chen-idr-ctr-availability-00.txt
Thread-Index: AQHV9fcj2nmDGRdd/EWqsviKCTRPUahQFbyA
Date: Thu, 19 Mar 2020 15:59:29 +0000
Message-ID: <BY5PR13MB3651E3C79E9E7A8AD8331EF2F2F40@BY5PR13MB3651.namprd13.prod.outlook.com>
References: <158371607510.6713.4634073389865271789@ietfa.amsl.com>, <CAOj+MMGuEwUB_xMU+rhS-wLsn02cRo6qiantuvy7Z3vUXHtT=w@mail.gmail.com>
In-Reply-To: <CAOj+MMGuEwUB_xMU+rhS-wLsn02cRo6qiantuvy7Z3vUXHtT=w@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=huaimo.chen@futurewei.com;
x-originating-ip: [2601:199:4300:8e5a:1892:e8dc:1d57:128c]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 1ad1b9f7-d2e3-44ed-6a63-08d7cc1e8217
x-ms-traffictypediagnostic: BY5PR13MB2933:
x-microsoft-antispam-prvs: <BY5PR13MB29333E69A869CF168ACA1964F2F40@BY5PR13MB2933.namprd13.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:6108;
x-forefront-prvs: 0347410860
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(4636009)(39850400004)(376002)(136003)(366004)(396003)(346002)(199004)(7696005)(76116006)(33656002)(64756008)(66574012)(55016002)(53546011)(8936002)(478600001)(9686003)(66446008)(966005)(66946007)(6506007)(5660300002)(52536014)(66556008)(66476007)(19627405001)(186003)(86362001)(44832011)(81156014)(316002)(8676002)(71200400001)(110136005)(81166006)(2906002); DIR:OUT; SFP:1102; SCL:1; SRVR:BY5PR13MB2933; H:BY5PR13MB3651.namprd13.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1;
received-spf: None (protection.outlook.com: futurewei.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: kznYvwA9mL98wVH2OeeDFbIiP06DMmHNrbNBmtlRWsRhhIBMDVTsOAQWXWCib8/ycl/9ZUSxVkTHzthBd/tc39CJa0c1Z75IwQaP/CrSSTqlXLrOqaAq5i4qUFZYtHHBfe8FvlKpGhvtcXj0YXA6kg14Yh6Cc4dw8pjwtOLRRY5WuAfR5a3+Bj5LjJLMgpDMb4NtyW3mog4PWPXB58mOBWUhXKTVsN2zCt36hsYh2qweXTkZT48SybmZhpPk34Bg+7LklOnJjZz0fcnrDWsMQmn6qDBRu9nzFMsKqkJ8PgNClBRwZk8EOlpkX2r79BsGA9Y+w6GViwMgcAbZb3xWIzhVguPNIrNB5GXtykYhM+zDavNNBsB4m2qx1HCdvmW/b/dm0s6Ul7aEaBrHhdIh67ATjm2+CskhjY8mPebq8B5DfpC9Ms66xC9NVVattMd82OtF3qgF9QBYdJMLQwAA5W+agF8cgCfgNoJX46TIUb/Y5sPJOYZyI4ptAHzoty6w33ujNg8KxT/mvfuWy3la2g==
x-ms-exchange-antispam-messagedata: joT0rePsKrc/XtNN/tyroy3cxAoR1A1YzRmZ8P8FS53RHeUVwi2z7fpElYiWw2MwV7Q6kSOk/Tp1YLST2x9E2X+0Nacyt5RIIk66szbU+riUTD6G2WmpEineHhDKZmPNwD6feB9HlTids0JLpAuyFelJiv/9Vnm1XRXB+L3mpB9HK4D2syj9c5RZdYJ+KtaCmvwfL/W3VuNFvnVg7YelRQ==
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_BY5PR13MB3651E3C79E9E7A8AD8331EF2F2F40BY5PR13MB3651namp_"
MIME-Version: 1.0
X-OriginatorOrg: Futurewei.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 1ad1b9f7-d2e3-44ed-6a63-08d7cc1e8217
X-MS-Exchange-CrossTenant-originalarrivaltime: 19 Mar 2020 15:59:29.8498 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 0fee8ff2-a3b2-4018-9c75-3a1d5591fedc
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: yIhLwOxLcUgVbXgXof5XRvVWhS3TOJfz2c4J2VZh/hNyRRqdKudSNEbG5tcjF6Dck6DJI/79/7GASwduFoKwIQ==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BY5PR13MB2933
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/HFSVlh0tKbU_4IqphFddNGdpyHE>
Subject: Re: [Idr] draft-chen-idr-ctr-availability-00.txt
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/idr/>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 19 Mar 2020 15:59:36 -0000

Hi Robert,

    Thank you very much for your comments and suggestions.
    My answers/explanations are inline below with prefix [HC].

Best Regards,
Huaimo
________________________________
From: Idr <idr-bounces@ietf.org> on behalf of Robert Raszuk <robert@raszuk.net>
Sent: Monday, March 9, 2020 5:42 AM
To: idr@ietf. org <idr@ietf.org>
Subject: [Idr] draft-chen-idr-ctr-availability-00.txt

Dear Authors,

I read your draft and sorry to say do not have good news.

1)

First you break IBGP rule from base BGP spec. It is pretty standard that controllers distribute information via IBGP and with the help of RRs. Only RRs can send information received over IBGP to other IBGP peers.

In your case it is hard to assume that all NEs are RRs. It is also hard to assume that always multiple controllers from the same controller cluster will be connecting to the same RRs.

[HC]: It is not necessary to assume that all NEs are RRs. In general, it seems enough to assume that every edge NE is connected to the controller cluster, and one or two edges of the network are connected to multiple controllers in the cluster.

2)

The best solution to your problem is to have two independent controller clusters. When fatal intra-cluster failures occur all cluster members should drop BGP sessions to the network.

[HC]: Using two or more independent controller clusters for network or controller reliability/availability is another solution, which we will consider.

3)

Asking all network elements to participate in exchanging information between controllers is really not a good idea. Not to mention that your current encoding does not even have a notion of cluster id.

[HC]: In general, only one or two edges of the network will participate in exchanging information about controllers between controllers. We will consider cluster ID notion and encoding.

Many thx,
R.

---------- Forwarded message ---------
From: <internet-drafts@ietf.org<mailto:internet-drafts@ietf.org>>
Date: Mon, Mar 9, 2020 at 2:08 AM
Subject: I-D Action: draft-chen-idr-ctr-availability-00.txt
To: <i-d-announce@ietf.org<mailto:i-d-announce@ietf.org>>



A New Internet-Draft is available from the on-line Internet-Drafts directories.


        Title           : BGP for Network High Availability
        Authors         : Huaimo Chen
                          Yanhe Fan
                          Aijun Wang
                          Lei Liu
                          Xufeng Liu
        Filename        : draft-chen-idr-ctr-availability-00.txt
        Pages           : 12
        Date            : 2020-03-08

Abstract:
   This document describes protocol extensions to BGP for improving the
   reliability or availability of a network controlled by a controller
   cluster.



The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-chen-idr-ctr-availability/<https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fdraft-chen-idr-ctr-availability%2F&data=02%7C01%7Chuaimo.chen%40futurewei.com%7C4afaa98d844947f1b03608d7c40e4481%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C637193437868987310&sdata=lOGxdK%2BGukAtjt3W3AoBq3hxmt8vNBC1fAvpMv5ROyI%3D&reserved=0>

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-chen-idr-ctr-availability-00<https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Ftools.ietf.org%2Fhtml%2Fdraft-chen-idr-ctr-availability-00&data=02%7C01%7Chuaimo.chen%40futurewei.com%7C4afaa98d844947f1b03608d7c40e4481%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C637193437868987310&sdata=uJMQBTm5YVYgAL8JDmFJI2Z%2B2KFUst5SJdhPJPuamv8%3D&reserved=0>
https://datatracker.ietf.org/doc/html/draft-chen-idr-ctr-availability-00<https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fhtml%2Fdraft-chen-idr-ctr-availability-00&data=02%7C01%7Chuaimo.chen%40futurewei.com%7C4afaa98d844947f1b03608d7c40e4481%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C637193437868997301&sdata=g4S6FkscMfxOvKu0ar0N%2F5h6YKjBQ%2F3OQAlmIdo%2FGL4%3D&reserved=0>


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org<https://nam11.safelinks.protection.outlook.com/?url=http%3A%2F%2Ftools.ietf.org%2F&data=02%7C01%7Chuaimo.chen%40futurewei.com%7C4afaa98d844947f1b03608d7c40e4481%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C637193437868997301&sdata=iB23OQijsbiuH6eVMu782lSxe9VJsCH7s3Yc4c3DAJw%3D&reserved=0>.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


_______________________________________________
I-D-Announce mailing list
I-D-Announce@ietf.org<mailto:I-D-Announce@ietf.org>
https://www.ietf.org/mailman/listinfo/i-d-announce<https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ietf.org%2Fmailman%2Flistinfo%2Fi-d-announce&data=02%7C01%7Chuaimo.chen%40futurewei.com%7C4afaa98d844947f1b03608d7c40e4481%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C637193437868997301&sdata=q%2F66OyDbdk9E9z0HnmUIxtadQVdWfw6KWqYa%2BF6jvLM%3D&reserved=0>
Internet-Draft directories: http://www.ietf.org/shadow.html<https://nam11.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.ietf.org%2Fshadow.html&data=02%7C01%7Chuaimo.chen%40futurewei.com%7C4afaa98d844947f1b03608d7c40e4481%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C637193437869007292&sdata=rtB%2BW0A3z%2F5ob%2BSZi4Ghz8UBWhtORfCQsgUOl%2B9I6Zo%3D&reserved=0>
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt