Re: [secdir] Secdir last call review of draft-ietf-bess-mvpn-fast-failover-11
Daniel Migault <daniel.migault@ericsson.com> Wed, 11 November 2020 16:48 UTC
Return-Path: <daniel.migault@ericsson.com>
X-Original-To: secdir@ietfa.amsl.com
Delivered-To: secdir@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6EFC33A11F7; Wed, 11 Nov 2020 08:48:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.101
X-Spam-Level:
X-Spam-Status: No, score=-2.101 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-0.001, 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=ericsson.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 iZav8pfwRdwS; Wed, 11 Nov 2020 08:48:19 -0800 (PST)
Received: from NAM12-MW2-obe.outbound.protection.outlook.com (mail-mw2nam12on2046.outbound.protection.outlook.com [40.107.244.46]) (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 39EEE3A1158; Wed, 11 Nov 2020 08:48:18 -0800 (PST)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=F2KqBTZJ8eLmGlC+WCsnJIsjWNzjncXII8+SJaUR9nxhcYFctmC2NFZVpsu8PeIwV6tOqF3BWTZjncMgPxF0dOa2/P3pYAwlbMWXbFcHnfDj4NoQKrB++QEErLbk5fUqdtxcih6opBXhvx/BysEHLcA/JwhhU0uQcvVZiGho5KpFbpB9a2lkTwIW4bgyteooYHdmYuiz1SAMBcv/xLmQ6b/5gQNxqSYXagHFsrDhWiDO8gy1CtWo6sRDZCD7KWfboNhfQbkRtyKPeC76P14gjSh8i4zzwFMzbSDHCWt5ktvCiCJzg0ncEZPOx9KA77KgxObCMGv9sf5DyOfZQs5+Jw==
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=DCN2lDS8qB2lh3VNbj30+tVFuHiZo+Ewf7i0U8ZjCSg=; b=jrjHOqeH9+ByGkH6xDLXQ2jKAPovYKL6aOuRX8pDfrcpGHAQG+l0BAXBzXE87cyeSI702EiYPn5LkGB3W6/t/TAQyrFSbltV/0Gwyx0utDNCVyoECdysZ4/rxprgGe1x/3c3AeH8ZFVPMVvDUKIXcV5G1AsrB/89E4vUazGaG54WupeyW5axLigQN4I2Oz4i0wF27f/DfhF1ljE+NuUjJ7r5XXiwhqzSDlKBoyqw8regKwhZ/B2uN38eWBOy6UHZcTr3qi7okOvbITTTvr6npltA85YAr+boI5N0K99ym0qXuvO/eGFjnGaspjddFxBlVgfTikmnLGF9Z242K/D5aA==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=ericsson.com; dmarc=pass action=none header.from=ericsson.com; dkim=pass header.d=ericsson.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ericsson.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=DCN2lDS8qB2lh3VNbj30+tVFuHiZo+Ewf7i0U8ZjCSg=; b=nlWgTQqH8UTiVCYfsGiWVvdIYVUvW+lFVSG3wc2J6eVClIUKIfydtZQa21g84QBagZPHTFpVRBXbN4D9vyVmIBfmnal+glTOwJ935rezz4Gq6WdgUMFKNwvOxCGP7xiN+Co5UcJVyTRVmBJo3MSxMa77tW8bN2cIVnnndk/58sg=
Received: from DM6PR15MB2379.namprd15.prod.outlook.com (2603:10b6:5:8a::16) by DM6PR15MB2827.namprd15.prod.outlook.com (2603:10b6:5:1ac::16) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3541.23; Wed, 11 Nov 2020 16:48:15 +0000
Received: from DM6PR15MB2379.namprd15.prod.outlook.com ([fe80::28b4:8429:419b:15b0]) by DM6PR15MB2379.namprd15.prod.outlook.com ([fe80::28b4:8429:419b:15b0%3]) with mapi id 15.20.3541.025; Wed, 11 Nov 2020 16:48:15 +0000
From: Daniel Migault <daniel.migault@ericsson.com>
To: Greg Mirsky <gregimirsky@gmail.com>
CC: "secdir@ietf.org" <secdir@ietf.org>, BESS <bess@ietf.org>, "last-call@ietf.org" <last-call@ietf.org>, "draft-ietf-bess-mvpn-fast-failover.all@ietf.org" <draft-ietf-bess-mvpn-fast-failover.all@ietf.org>
Thread-Topic: Secdir last call review of draft-ietf-bess-mvpn-fast-failover-11
Thread-Index: AQHWt9C5emGUONFgKUKxrX3Gy2SfzqnDA2lu
Date: Wed, 11 Nov 2020 16:48:15 +0000
Message-ID: <DM6PR15MB237965003540C4F0679A45DEE3E80@DM6PR15MB2379.namprd15.prod.outlook.com>
References: <160345656094.22100.7057001737682109381@ietfa.amsl.com>, <CA+RyBmVXOrQu2Efs9nojMTOWyy09Cd4XEYS8a5HF+18C+_X1Nw@mail.gmail.com>
In-Reply-To: <CA+RyBmVXOrQu2Efs9nojMTOWyy09Cd4XEYS8a5HF+18C+_X1Nw@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: gmail.com; dkim=none (message not signed) header.d=none;gmail.com; dmarc=none action=none header.from=ericsson.com;
x-originating-ip: [96.22.11.129]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 5ff40e05-20aa-4775-d3a7-08d8866195e8
x-ms-traffictypediagnostic: DM6PR15MB2827:
x-microsoft-antispam-prvs: <DM6PR15MB28270CD36FD3020960E83450E3E80@DM6PR15MB2827.namprd15.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:9508;
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: oos6S0BeYtPSzZjzUi10NxPAcmqjcb20Krk4QKHDGIYAfPE4Tr7VxEfdLox1cbH34pascEbTKtq+KsJBISvdYZmnttIeN7XDkwDReAZ3rp1nSt/MHEhnumTKPaXZ+M5GVM3vTr7scT+4lrYwTCqlwCmSvb7Lhi3MUcINdHdZs7LPzPlB4F4XuA3oGb4YXF52lQFSJgqvTkP5jLA9mDF7seppuuMtRpW7zYVW8VbF12B5H9WLpXd6ruIALoRnNSROYhb4wWUmDi/srpDW/NoL4VIstPO5ouL3eakXVHn29NB6G6hBGi4OmxLNaLAaQ1vLmalaYQWKb4GdliRw1/PCOh8by74eRsK7DdVBG7O/FI9YUB5FZxlrvkNIVhu5/TK1
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:DM6PR15MB2379.namprd15.prod.outlook.com; PTR:; CAT:NONE; SFS:(4636009)(366004)(346002)(376002)(39860400002)(136003)(396003)(83380400001)(316002)(9686003)(33656002)(6916009)(66574015)(6506007)(53546011)(54906003)(44832011)(4326008)(55016002)(52536014)(71200400001)(7696005)(5660300002)(26005)(86362001)(186003)(91956017)(30864003)(76116006)(19627405001)(66446008)(8676002)(478600001)(2906002)(8936002)(64756008)(66476007)(66946007)(66556008)(21314003); DIR:OUT; SFP:1101;
x-ms-exchange-antispam-messagedata: PHJnaGda/yJjBWW8Cd1VfgIMtV4mPCEfpRlV2Xw6WzjS80igwEe+uF8Tg2npsRSgzzAkIkhwttlLXhNaAZMKoOTbAf+MilgwXlDzFGhN3SvJHQ6BocqIchReZYNn7gymh+maIZxf9nkfqq4L12cZ2y1k2uiPQCSNpW3wGv6RANCT/sZvY4aRwLqE/5SyrhQ94Os3Cn8UMal1b5bSsjthlN9Oc9wlmGKstzUwe+NOrlbDp0JoDcrAXRkJCgii8i1mlvX6p7dqd9XSQvZeTK/2/IAb4CVNeMgB+nf3UzkluPlDG4CH3DWVdIflT8TCGqqPSFz0ULrc2CqOgZAYU+7ipRVaR82+DzmUhr247oYrTWGvctfsScyiis4rAjp0s64InjuYIjktZlP5nurviCHXC2tTEvTAqIoIYnhC73vsmycvjlhaiYYYA6Vcm19MGMBVJ3An8+AMYTelw9otzfmJ3QqUb1ttmbR4wfKPn5D0wc/cxMcBkHZhvFCoeLaqjC2ixjFyBBMIBVoWjCKy+Kk1FvTXgCVeBwu7tiHxGEXsC48jYjFvrpwU48ySsIhKsPvr7CY9EFZZ1YVpWmFIzZghmNTZl2ofcol4aeGKE2kTTzns0bO//eONNsyr2k1WKoKSm5k3Ozb75WLbOfEfOcw9Rw==
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_DM6PR15MB237965003540C4F0679A45DEE3E80DM6PR15MB2379namp_"
MIME-Version: 1.0
X-OriginatorOrg: ericsson.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: DM6PR15MB2379.namprd15.prod.outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 5ff40e05-20aa-4775-d3a7-08d8866195e8
X-MS-Exchange-CrossTenant-originalarrivaltime: 11 Nov 2020 16:48:15.6979 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 92e84ceb-fbfd-47ab-be52-080c6b87953f
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: I4p28V7rHkr/LrnqlL/j1qRUVoUvswvFNs7Z8hfik1w+tJehoDccx0l1WyXEEZMNoz3jseGX4E3gee3BzqJSOBYqH4Bnp30QF4KLfvfi/04=
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM6PR15MB2827
Archived-At: <https://mailarchive.ietf.org/arch/msg/secdir/Msl0uothHW9Ep8b4CJnkPmYeJvY>
Subject: Re: [secdir] Secdir last call review of draft-ietf-bess-mvpn-fast-failover-11
X-BeenThere: secdir@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Security Area Directorate <secdir.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/secdir>, <mailto:secdir-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/secdir/>
List-Post: <mailto:secdir@ietf.org>
List-Help: <mailto:secdir-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/secdir>, <mailto:secdir-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 11 Nov 2020 16:48:27 -0000
Hi Greg, Thanks for the response and clarifications. Most of my comments have been addressed/answered. However, it seems to me that some additional text might be added to the security consideration section document the impact on the network of a fast-failover operation. The knowledge of these impact might be useful for an operator to determine when the trigger can be done. Please see more comments inline. Yours, Daniel ________________________________ From: Greg Mirsky <gregimirsky@gmail.com> Sent: Tuesday, November 10, 2020 9:13 PM To: Daniel Migault <daniel.migault@ericsson.com> Cc: secdir@ietf.org <secdir@ietf.org>; BESS <bess@ietf.org>; last-call@ietf.org <last-call@ietf.org>; draft-ietf-bess-mvpn-fast-failover.all@ietf.org <draft-ietf-bess-mvpn-fast-failover.all@ietf.org> Subject: Re: Secdir last call review of draft-ietf-bess-mvpn-fast-failover-11 Hi Daniel, many thanks for the review, thoughtful comments, and questions, all are much appreciated. Also, my apologies for the long delay to respond to your comments. Please find my answers and notes in-line below tagged by GIM>>. Attached are the new working version and the diff to -12. Regards, Greg On Fri, Oct 23, 2020 at 5:36 AM Daniel Migault via Datatracker <noreply@ietf.org<mailto:noreply@ietf.org>> wrote: Reviewer: Daniel Migault Review result: Has Nits Hi, I reviewed this document as part of the Security Directorate's ongoing effort to review all IETF documents being processed by the IESG. These comments were written primarily for the benefit of the Security Area Directors. Document authors, document editors, and WG chairs should treat these comments just like any other IETF Last Call comments. Please note also that my expertise in BGP is limited, so feel free to take these comments with a pitch of salt. Review Results: Has Nits Please find my comments below. Yours, Daniel Multicast VPN Fast Upstream Failover draft-ietf-bess-mvpn-fast-failover-11 Abstract This document defines multicast VPN extensions and procedures that allow fast failover for upstream failures, by allowing downstream PEs to take into account the status of Provider-Tunnels (P-tunnels) when selecting the Upstream PE for a VPN multicast flow, and extending BGP MVPN routing so that a C-multicast route can be advertised toward a Standby Upstream PE. <mglt> Though it might be just a nit, if MVPN designates multicast VPN, it might be clarifying to specify the acronym in the first sentence. This would later make the correlation with BGP MVPN clearer. </mglt> GIM>> I've updated s/BGP MVPN/BGP multicast VPN/. Also, s/mVPN/MVPN/ throughout the document. 1. Introduction In the context of multicast in BGP/MPLS VPNs, it is desirable to provide mechanisms allowing fast recovery of connectivity on different types of failures. This document addresses failures of elements in the provider network that are upstream of PEs connected to VPN sites with receivers. <mglt> Well I am not familiar with neither BGP nor MPLS. It seems that BGP/MLPS IP VPNS and MPLS/BGP IP VPNs are both used. I am wondering if there is a distinction between the two and a preferred way to designate these VPNs. My understanding is that the VPN-IPv4 characterizes the VPN while MPLS is used by the backbone for the transport. Since the PE are connected to the backbone the VPN-IPv4 needs to be labeled. </mglt> GIM>> I understand that this document often sends the reader to check RFC 6513 and/or RFC 6514. BGP/MPLS MVPN identifies the case of providing a multicast service over an IP VPN that is overlayed on the MPLS data plane using the BGP control plane. Section 3 describes local procedures allowing an egress PE (a PE connected to a receiver site) to take into account the status of P-tunnels to determine the Upstream Multicast Hop (UMH) for a given (C-S, C-G). This method does not provide a "fast failover" solution <mglt> I understand the limitation is due to BGP convergence. </mglt> GIM>> Yes, a dynamic routing protocol, BGP in this case, provides the service restoration functionality but the restoration time is significant and affects the experience of a client. when used alone, but can be used together with the mechanism described in Section 4 for a "fast failover" solution. Section 4 describes protocol extensions that can speed up failover by not requiring any multicast VPN routing message exchange at recovery time. Moreover, section 5 describes a "hot leaf standby" mechanism, that uses a combination of these two mechanisms. This approach has similarities with the solution described in [RFC7431] to improve failover times when PIM routing is used in a network given some topology and metric constraints. [...] 3.1.1. mVPN Tunnel Root Tracking A condition to consider that the status of a P-tunnel is up is that the root of the tunnel, as determined in the x-PMSI Tunnel attribute, is reachable through unicast routing tables. In this case, the downstream PE can immediately update its UMH when the reachability condition changes. That is similar to BGP next-hop tracking for VPN routes, except that the address considered is not the BGP next-hop address, but the root address in the x-PMSI Tunnel attribute. If BGP next-hop tracking is done for VPN routes and the root address of a given tunnel happens to be the same as the next-hop address in the BGP A-D Route advertising the tunnel, then checking, in unicast routing tables, whether the tunnel root is reachable, will be unnecessary duplication and thus will not bring any specific benefit. <mglt> It seems to me that x-PMSI address designates a different interface than the one used by the Tunnel itself. If that is correct, such mechanisms seems to assume that one equipment up on one interface will be up on the other interfaces. I have the impression that a configuration change in a PE may end up in the P-tunnel being down, while the PE still being reachable though the x-PMSI Tunnel attribute. If that is a possible scenario, the current mechanisms may not provide more efficient mechanism than then those of the standard BGP. GIM>> That is a very interesting angle, thank you. Yes, in OAM, and in the Fault Management (FM) OAM in particular, we have to make some assumptions about the state of the remote system based on a single event or change of state. Usually, AFAIK, operators use not a physical interface but a loopback to associate with a tunnel. With a fast IGP convergence, a loopback interface is reachable as long as there's a path through the network between two nodes. <mglt> Thanks for the clarification </mglt> Similarly, it is assumed the tunnel is either up or down and the determination of not being up if being down. I am not convinced that the two only states. Typically services under DDoS may be down for a small amount of time. While this affects the network, there is not always a clear cut between the PE being up or down. </mglt> GIM>> In defect detection a system often has some hysteresis, i.e., time that the system has to wait to change its state. For example, BFD changes state from Up to Down after the system does not receive N consecutive packets (usually 3). As a result, in some cases, the system can be tuned to detect relatively short outages while in others be slower and miss short-lived outages. [...] 3.1.6. BFD Discriminator Attribute P-tunnel status may be derived from the status of a multipoint BFD session [RFC8562] whose discriminator is advertised along with an x-PMSI A-D Route. This document defines the format and ways of using a new BGP attribute called the "BFD Discriminator". It is an optional transitive BGP attribute. In Section 7.2, IANA is requested to allocate the codepoint value (TBA2). The format of this attribute is shown in Figure 1. <mglt> I feel that the sentence "In Section ... TBA2)." should be removed. </mglt> GIM>> We use this to mark where to note the allocated value. Usually, this text is replaced by the RFC Editor to read In Section 7.2 IANA allocated codepoint XXX. 0 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | BFD Mode | Reserved | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | BFD Discriminator | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ ~ Optional TLVs ~ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Figure 1: Format of the BFD Discriminator Attribute Where: BFD Mode field is the one octet long. This specification defines the P2MP BFD Session as value 1 Section 7.2. Reserved field is three octets long, and the value MUST be zeroed on transmission and ignored on receipt. BFD Discriminator field is four octets long. Morin, et al. Expires April 5, 2021 [Page 7] Internet-Draft mVPN Fast Upstream Failover October 2020 Optional TLVs is the optional variable-length field that MAY be used in the BFD Discriminator attribute for future extensions. TLVs MAY be included in a sequential or nested manner. To allow for TLV nesting, it is advised to define a new TLV as a variable- length object. Figure 2 presents the Optional TLV format TLV that consists of: * one octet-long field of TLV 's Type value (Section 7.3) * one octet-long field of the length of the Value field in octets * variable length Value field. The length of a TLV MUST be multiple of four octets. <mglt> I am wondering why the constraint on the length is not mentioned in the paragraph associated to the field - as opposed to a separate paragraph. </mglt> GIM>> There might be a slight confusion due to the use of Length and length. Capitalized - the name of the field which value is the length of the Value field. The last sentence refers to the overall length of a TLV, including lengths of Type, Length and Value fields. <mglt> you are correct that might have confused me. </mglt> [..] 8. Security Considerations This document describes procedures based on [RFC6513] and [RFC6514] and hence shares the security considerations respectively represented in these specifications. This document uses p2mp BFD, as defined in [RFC8562], which, in turn, is based on [RFC5880]. Security considerations relevant to each protocol are discussed in the respective protocol specifications. An implementation that supports this specification MUST use a mechanism to control the maximum number of p2mp BFD sessions that can be active at the same time. <mglt> At a high level view - or at least my interpretation of it - the document proposes a mechanism based on BFD to detect fault in the path. Upon a fault detection a fail-over operation is instructed using BGP. This rocedure is expected to perform a faster fail-over than traditional BGP convergence on maintaining routing tables. Once the fail over has been performed, BFD is confirms the new path is "legitimate" and works. It seems correct to me that the current protocol relies on BGP / BFD security. That said, having BFD authentication based on MD5 or SHA1 may suggest that stronger primitives be recommended. While this does not concerns the current document, it seems to me that the information might be relayed to routing ADs. What remains unclear to me - and I assume this might be due to my lake or expertise in routing area - is the impact associated to performing a fail-over both on 1) the data plane and 2) the standard BGP way to establish routing tables. Regarding the data plane, I am wondering if fail-over results in a lost of packets for example - I suppose for example that at least the packets in the process of being forwarded might be lost. I believe that providing details on this may be good. GIM>> You bring up a very topic for the discussion, thank you. With network failure detection in place, the fail-over can be viewed as the reaction to a network failure. If that is the case, then packet loss experienced by service due to the fail-over is the result of the network failure. Would you agree with that view? A shorter failure detection interval and faster fail-over should minimize the packet loss and, as a result, the negative impact on the service itself. <mglt> sure. If you know the network is down, then fast fail-over is definitively a plus. What I think could be useful is to evaluate the cost associated to a fast-fail-over without any network failure. This would be useful for an operator to evaluate whether it should spend more time in diagnosing a network failure versus performing a fast-fail-over. Typically, if a fast failover comes a no cost at all, one operator would maybe use one exchange to test the liveness of a node rather than 3. At that point, it seems to me that additional text coudl be added to characterize the impact. These could be high level and indicative, but it seems to me that knowing these impacts presents some value to the operators. </mglt> If there are any impacts I would like to understand also in which cases the decision to perform a failover operation may result in more harm than the event that has been over-interpreted. An hypothetical scenario could be that the non reception of a BFD packet is interpreted as a PE being down while it may not be correct and the PE might have been simply under stress. A "too fast" fail-over may over interpreted it and perform a fail-over. If such things could happen, an attacker could leverage a micro event to perform network operation that are not negligible. Another way to see that is that an attacker might not have direct access to the control plan, but could use the data plan to generate a stress and sort of control the fail over. It seems to me that some text might be welcome to prevent such cases to happen. This could be guidance for declaring a tunnel down for example. GIM>> I agree with your scenario. Over-short detection interval may produce a false-negative transition to the Down state in BFD and thus triggering the fail-over. I think that that is more an operational issue, something that an operator will consider when deploying the mechanism specified in this draft. Resulting from addressing RtgDir review the draft was updated to provide more guidance: In many cases, it is not practical to use both protection methods at the same time because uncorrelated timers might cause unnecessary switchovers and destabilize the network. <mglt> Thanks for the feed back, It seems to me important to mention it is not recommended these two mechanism co-exist. How to avoid false negative transition might be out of scope of the draft I agree, but it seems to me worth being mentioned especially in relation to the impacts associated to a fail-over. In case the fast-failover comes with no impact this becomes less of a problem for operator deploying it. </mglt> Though the text above might not be general, I think that it also applies to the scenario you've presented. Similarly, it would be good to add some text regarding the interferences with the non-fast forwarding fail over when performed by the standard BGP. Typically, my impression is that the fast fail-over mechanism is a local decision versus the BGP convergence that is more global. As a result, even with more time this two mechanisms may come with different outcomes. One such example to illustrate my purpose could be the following. Note that this is only illustrative of my purpose, and I let you find and pick on ethat is more appropriated. I am thinking of a case where a standby PE is be shared among multiple PEs - supposing this situation could occur. Typically, if PE_1, PE_2 are shared by PE_a, ..., PE_z. In case PE_a and PE_b are down, we expect PE_a to switch to PE_1 and PE_b to switch to PE_2. It seems to me that BGP would end up in such situation while a local decision may end up in PE_a and PE_a to switch to PE_1. </mglt> GIM>> Thank you for the scenario that is very common in deploying protection based on the shared redundant resources. Such schemes, referred to as M:N protection, in addition to using mechanism detecting a network failure, e.g., BFD, require a protocol to coordinate the switchover. This specification applies to a more special deployment scenario where one working PE is protected by one or more standby PEs, i.e., 1:N protection. <mglt> I understand the document is addressing a 1:N scenario. That said, if M:N scenario leverage from 1:N protection it seems to me worth raising the issue. </mglt>
- [secdir] Secdir last call review of draft-ietf-be… Daniel Migault via Datatracker
- Re: [secdir] Secdir last call review of draft-iet… Greg Mirsky
- Re: [secdir] Secdir last call review of draft-iet… Greg Mirsky
- Re: [secdir] Secdir last call review of draft-iet… Daniel Migault
- Re: [secdir] Secdir last call review of draft-iet… Greg Mirsky
- Re: [secdir] Secdir last call review of draft-iet… Daniel Migault
- Re: [secdir] Secdir last call review of draft-iet… Greg Mirsky
- Re: [secdir] Secdir last call review of draft-iet… Daniel Migault
- Re: [secdir] Secdir last call review of draft-iet… Greg Mirsky