Re: [Idr] WG adoption call for draft-merciaz-idr-bgp-bfd-strict-mode-02.txt (9/2 to 9/17/2019)

"Mercia Zheng (merciaz)" <merciaz@cisco.com> Mon, 09 September 2019 21:32 UTC

Return-Path: <merciaz@cisco.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 92BAE12008D for <idr@ietfa.amsl.com>; Mon, 9 Sep 2019 14:32:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.499
X-Spam-Level:
X-Spam-Status: No, score=-14.499 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com header.b=JBz4xXih; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=qRl7eCzc
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 q_Vh1DuEtQIH for <idr@ietfa.amsl.com>; Mon, 9 Sep 2019 14:32:01 -0700 (PDT)
Received: from alln-iport-4.cisco.com (alln-iport-4.cisco.com [173.37.142.91]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0469A12001A for <idr@ietf.org>; Mon, 9 Sep 2019 14:32:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=17895; q=dns/txt; s=iport; t=1568064721; x=1569274321; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=oVLwjl5TC3ULi3KD2PDP17UZf7YIFu4VZQOeBoWmtXs=; b=JBz4xXih144Hg0BFrxb7A/sEI9XasXvx87S33xVAPaqXAZ+N74Wzyhw4 XVTqYHKrKxYVa/pVE/MqwRCBPjAs0urx25igmotRHlYYyAi8pYQW04uEW A2yaPXFx1r5M9/ywCBzCzcmehwBS4oMWZVZrHyhHLFZDCpybHqU83AWmr I=;
IronPort-PHdr: =?us-ascii?q?9a23=3AoDwhLRYuMLBaBTaYgqPOd8X/LSx94ef9IxIV55?= =?us-ascii?q?w7irlHbqWk+dH4MVfC4el20gebRp3VvvRDjeee87vtX2AN+96giDgDa9QNMn?= =?us-ascii?q?1NksAKh0olCc+BB1f8KavvYjYxHc1QfFRk5Hq8d0NSHZW2ag=3D=3D?=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0DnAABPxHZd/5pdJa1lGgEBAQEBAgE?= =?us-ascii?q?BAQEHAgEBAQGBZ4EWLyQsA21WIAQLKoQhg0cDiniCNyV+khaEXIJSA1QJAQE?= =?us-ascii?q?BDAEBGAEKCgIBAYQ/AheCISM4EwIDCQEBBAEBAQIBBgRthS4MhUoBAQEBAwE?= =?us-ascii?q?BEAsGHQEBLAsBDwIBCBEDAQIoAwICAiULFAkIAQEEAQ0FIoMAAYEdTQMdAQI?= =?us-ascii?q?Mmn4CgTiIYXOBMoJ9AQEFgUZBgwwYghYDBoE0i3gYgUA/gREnDBOCFzU+gQS?= =?us-ascii?q?BXQEBAwGBfQ0JglUygiaPPYUhiReOTwqCIYZ/jXUbgjSHPIQhinGNfogCkGk?= =?us-ascii?q?CBAIEBQIOAQEFgWkhgVhwFTsqAYJBgkIYIIM6hRSFPgFzgSmPdQEB?=
X-IronPort-AV: E=Sophos;i="5.64,487,1559520000"; d="scan'208,217";a="323137657"
Received: from rcdn-core-3.cisco.com ([173.37.93.154]) by alln-iport-4.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 09 Sep 2019 21:32:00 +0000
Received: from XCH-RCD-015.cisco.com (xch-rcd-015.cisco.com [173.37.102.25]) by rcdn-core-3.cisco.com (8.15.2/8.15.2) with ESMTPS id x89LVxLI023770 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Mon, 9 Sep 2019 21:32:00 GMT
Received: from xhs-aln-002.cisco.com (173.37.135.119) by XCH-RCD-015.cisco.com (173.37.102.25) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Mon, 9 Sep 2019 16:31:59 -0500
Received: from xhs-aln-003.cisco.com (173.37.135.120) by xhs-aln-002.cisco.com (173.37.135.119) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Mon, 9 Sep 2019 16:31:58 -0500
Received: from NAM04-CO1-obe.outbound.protection.outlook.com (173.37.151.57) by xhs-aln-003.cisco.com (173.37.135.120) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend Transport; Mon, 9 Sep 2019 16:31:58 -0500
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=oNWlVHJx/hj81avJP6jLOesi0RTGjGo2rXd2lIGJ2CBIe7nTPpFtLS0Zrkt0R+AdK4PFRh+SIZLnfau9yAif4P+K5NMy8wjrDfdjPFX/piPIiMbieruPtEtqTOlomddrkcssUJ4vNKGeZscK9tpS2uHpQOyTwxEhpwONr4tN1TH2K920fajd8WQFdcTWYkLGirreCVGx3ZNxPdHbhQoy8+BbtrIB6U08o0CNS4gGn8u4qw4vGmiEBDt/ZCtXyFd6e1CEDiF36WOePgwAOLVWjThN2J06kA5l1r3jnA+4clsinaxTD/vw3eEAzn6CfpFtv5HMkGzm+VSbIFQ9h5ZUeQ==
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=oVLwjl5TC3ULi3KD2PDP17UZf7YIFu4VZQOeBoWmtXs=; b=fJ4KaYrg3tqjOjneYzfWhxCzqTisCOlGvlFQj24OiE74P6UtIJkARgXbXGqSfq95LpB+i9nElFQKMoqp4gGw2l+77eUxav6NmF/M+iN0g1QZbs3a62yf6SqdFnyV1zMCeSoCXhvGxgnvrnJG7pptPBbrlxsPF7jgbCkD6xVJ2L8hOATEtdTb2mp0rg+2Nnl+zfYUGDwgCdps6V4qO9+Y2FOk3hjVrQEwHvSEgILGbssThI8TL4HfS2wNP0y6RYHC7NKu4siefxhTVUMwWYkvRw3bJ/lKD0TSeGKUUpxD11mYZ+80SC8x92PKSLcnh/LP0f9zf2wakZwLC77YFQEqhA==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=cisco.com; dmarc=pass action=none header.from=cisco.com; dkim=pass header.d=cisco.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cisco.onmicrosoft.com; s=selector2-cisco-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=oVLwjl5TC3ULi3KD2PDP17UZf7YIFu4VZQOeBoWmtXs=; b=qRl7eCzc6c1LJ6DSglYDN6di+fjvWPY6ajuHSs+P/kuyFfimr13+GRZb/+diKAYiVoyyacPB8IUI/87cKAUjjvN+BlydKNSKt6z6xWQoAxrbar32NBeS3rKS4hL6Rm0fdakZ6C5+0HmBBT80R4CYy8QXDNPjdODGRrZC1S6JefA=
Received: from BYAPR11MB3174.namprd11.prod.outlook.com (20.177.127.27) by BYAPR11MB2983.namprd11.prod.outlook.com (20.177.224.139) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2241.20; Mon, 9 Sep 2019 21:31:57 +0000
Received: from BYAPR11MB3174.namprd11.prod.outlook.com ([fe80::5889:8ac8:4ca2:be64]) by BYAPR11MB3174.namprd11.prod.outlook.com ([fe80::5889:8ac8:4ca2:be64%5]) with mapi id 15.20.2241.018; Mon, 9 Sep 2019 21:31:57 +0000
From: "Mercia Zheng (merciaz)" <merciaz@cisco.com>
To: Robert Raszuk <robert@raszuk.net>, "Acee Lindem (acee)" <acee@cisco.com>
CC: "idr@ietf.org" <idr@ietf.org>, Susan Hares <shares@ndzh.com>
Thread-Topic: [Idr] WG adoption call for draft-merciaz-idr-bgp-bfd-strict-mode-02.txt (9/2 to 9/17/2019)
Thread-Index: AdVht8Hop/hDHJozRuOf1u/upDEYlwDE/9MAAHBrD4AAI3nQAA==
Date: Mon, 9 Sep 2019 21:31:57 +0000
Message-ID: <20A92BAE-9B85-4876-B26C-98E1BDDACA03@cisco.com>
References: <003701d561b8$84171680$8c454380$@ndzh.com> <970E5C9A-7251-458B-8F9F-B452BDF58AE6@cisco.com> <CAOj+MMHEGwZ8YuaVvG0-mdKYb1gWbb6+8rM3Onf3X=CQGsbZQA@mail.gmail.com>
In-Reply-To: <CAOj+MMHEGwZ8YuaVvG0-mdKYb1gWbb6+8rM3Onf3X=CQGsbZQA@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/10.10.d.190811
authentication-results: spf=none (sender IP is ) smtp.mailfrom=merciaz@cisco.com;
x-originating-ip: [2001:420:c0c4:1002::25]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: b96a867e-6b77-458c-f73e-08d7356d2485
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600166)(711020)(4605104)(1401327)(2017052603328)(7193020); SRVR:BYAPR11MB2983;
x-ms-traffictypediagnostic: BYAPR11MB2983:
x-ms-exchange-purlcount: 4
x-ms-exchange-transport-forked: True
x-microsoft-antispam-prvs: <BYAPR11MB298362D175D3216CDAAE7828ABB70@BYAPR11MB2983.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-forefront-prvs: 01559F388D
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(4636009)(366004)(346002)(376002)(136003)(39860400002)(396003)(199004)(189003)(51914003)(43544003)(52314003)(25786009)(99286004)(256004)(14444005)(53936002)(316002)(11346002)(476003)(446003)(71200400001)(5660300002)(14454004)(2616005)(91956017)(54906003)(110136005)(71190400001)(76176011)(58126008)(66946007)(478600001)(66556008)(76116006)(66476007)(486006)(66446008)(64756008)(2906002)(9326002)(8936002)(46003)(6486002)(6436002)(966005)(86362001)(606006)(7736002)(36756003)(186003)(81156014)(81166006)(102836004)(6246003)(53546011)(6506007)(6116002)(33656002)(236005)(54896002)(6512007)(6306002)(6636002)(4326008)(229853002)(8676002); DIR:OUT; SFP:1101; SCL:1; SRVR:BYAPR11MB2983; H:BYAPR11MB3174.namprd11.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1;
received-spf: None (protection.outlook.com: cisco.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: i0UMCHMeSehQ3bHZ4R5Fq81a6/Mb3m5vzlA7IlsMlkJNRMR4Q+TCZP8mGoTKlu5zWL6945sjjjbWe6Bt+6jfM9bodoV1GW246klMYgQkVKyVK9hKe0HAtm3if8Yr3Vw+7mVs3G2vtapaT8OTToxFFTa6W87pVehL1qLO+dsenO5nba9E2fnVV9fx/hA58q9P4thqGegsUD/KnQYPHDzkykapA1P27xJkVE/HGH8lMAZdS1GwMWX1T9hh0jAe208OXfUen+bwdhFqykkD2f3GWbDXBa6uqV4t5m44vnph3FxqL9mU6ZNjaLZXs2+xFbBpeH6ZLVDIEGykHn1jnwxVWB+n0mNIfawkAZKv7Yrzqxg70uFYp0ujaw9XjLf0Cj/mqU4aK+xSkwWAxlouOh+7uWUM3wtKcUwZpYROS+shVvc=
Content-Type: multipart/alternative; boundary="_000_20A92BAE9B854876B26C98E1BDDACA03ciscocom_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: b96a867e-6b77-458c-f73e-08d7356d2485
X-MS-Exchange-CrossTenant-originalarrivaltime: 09 Sep 2019 21:31:57.5232 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 5ae1af62-9505-4097-a69a-c1553ef7840e
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: Fbv6hCKYNBpkoq6bMsny9Lc/p0+JyKpYxhC3Ur6XSN+t8QCVx/AHtsYAN0b2s2osbht4FFNuoCCV4H6+Mb1gxw==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BYAPR11MB2983
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.37.102.25, xch-rcd-015.cisco.com
X-Outbound-Node: rcdn-core-3.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/SsVkYQzfkRgJa1ffAbluB5l8WHk>
Subject: Re: [Idr] WG adoption call for draft-merciaz-idr-bgp-bfd-strict-mode-02.txt (9/2 to 9/17/2019)
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: Mon, 09 Sep 2019 21:32:03 -0000

Hi Robert,

Thanks for the review comments.
The similar question has been asked early on whether  or not this draft should be only for eBGP.
BGP BFD is enabled mostly for eBGP. RFC5882 section 10.2 specifies  “it is generally
unwise for IBGP sessions to interact with BFD if the underlying IGP
is already doing so.”.

There could still be cases where users only want to run iBGP BFD since no IGP is enabled
(e.g. fully mesh case).

Anyway, we’ll take care of this comment in the next revision.

Thanks,
Mercia

From: Idr <idr-bounces@ietf.org> on behalf of Robert Raszuk <robert@raszuk.net>
Date: Sunday, September 8, 2019 at 2:37 PM
To: "Acee Lindem (acee)" <acee@cisco.com>
Cc: "idr@ietf.org" <idr@ietf.org>rg>, Susan Hares <shares@ndzh.com>
Subject: Re: [Idr] WG adoption call for draft-merciaz-idr-bgp-bfd-strict-mode-02.txt (9/2 to 9/17/2019)

Hi Acee,

I have read the draft. Have one key question in fact triggered by colleagues comment below :)

In the draft you are not making any distinction between iBGP and eBGP sessions. Is this intentional ?

Procedures to establish and maintain eBGP vs iBGP sessions are vastly different hence an obvious question if you intentionally made no distinction or perhaps you had in mind all along that the draft applies only to eBGP ?

I think for eBGP it is useful, for iBGP I already see real cases where it may not give you what you expect.

In any case I support the adoption.

Thx,
Robert.


On Fri, Sep 6, 2019 at 9:57 PM Acee Lindem (acee) <acee@cisco.com<mailto:acee@cisco.com>> wrote:
Speaking as a co-author, I support WG adoption.
Thanks,
Acee

From: Idr <idr-bounces@ietf.org<mailto:idr-bounces@ietf.org>> on behalf of Susan Hares <shares@ndzh.com<mailto:shares@ndzh.com>>
Date: Monday, September 2, 2019 at 2:02 PM
To: IDR List <idr@ietf.org<mailto:idr@ietf.org>>
Subject: [Idr] WG adoption call for draft-merciaz-idr-bgp-bfd-strict-mode-02.txt (9/2 to 9/17/2019)

This begins a 2 week WG adoption call for draft-merciaz-idr-bgp-bfd-strict-mode-02.txt which you can access at:

https://datatracker.ietf.org/doc/draft-merciaz-idr-bgp-bfd-strict-mode/

For those who have indicated support for this draft during the lengthy IPR call, you are welcome to comment again
or to trust that the IDR chairs read your comments during the lengthy IPR call.

Please indicate if you think this draft is a good start for using the BFD technology
as a check that prevents BGP connectivity until BFD session is established
(indicating link connectivity).

Cheerily, Susan Hares

_______________________________________________
Idr mailing list
Idr@ietf.org<mailto:Idr@ietf.org>
https://www.ietf.org/mailman/listinfo/idr