Re: [spring] Draft for Node protection of intermediate nodes in SR Paths

Robert Raszuk <robert@raszuk.net> Fri, 22 November 2019 09:22 UTC

Return-Path: <robert@raszuk.net>
X-Original-To: spring@ietfa.amsl.com
Delivered-To: spring@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1B585120815 for <spring@ietfa.amsl.com>; Fri, 22 Nov 2019 01:22:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 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, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=raszuk.net
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 NDe9cgCXzRF9 for <spring@ietfa.amsl.com>; Fri, 22 Nov 2019 01:22:43 -0800 (PST)
Received: from mail-qv1-xf2d.google.com (mail-qv1-xf2d.google.com [IPv6:2607:f8b0:4864:20::f2d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D53AE120807 for <spring@ietf.org>; Fri, 22 Nov 2019 01:22:42 -0800 (PST)
Received: by mail-qv1-xf2d.google.com with SMTP id n12so2606179qvt.1 for <spring@ietf.org>; Fri, 22 Nov 2019 01:22:42 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=raszuk.net; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=fLXlglDkP+6wwdfjUpKwNeMRUP2JAkF0mwtf+lqMFP0=; b=OOQoqtlQq+gVbiln7YaVTVmKN3I/iiiJbm4cSumsTTdssW3kQJ1ClQbvTaIoTpfH5E sipiZHeQBKKd2R+/2iv9jaCgszzDHS8W5BI7cbfvZyeXn7H90z04X6LFrvlyBzer/d9x ho8DHnTJByS34a5KYl7OsDx7s23o9tgNxrQXaQbZXAPOM7T3yO8Kk185tHBImzEMB4Qr 9Yu9W5OQN7lMmRVdDWLBgBVnY/Ki2NDWPgY4p9XZNAZmhfIAnxBxwEqO0JISJro2rNtT BYkytRDtZBeg4qorMrtLfuw+voenf3VBNs9vx9FqRXklXYpj7G10TRzsLDK6F0kq7gr6 cwFw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=fLXlglDkP+6wwdfjUpKwNeMRUP2JAkF0mwtf+lqMFP0=; b=nhZHbokl0gY2LvAXfGTnAcG3PNPnxS7gdG7UFGAnQbO3Z/1CkQ5FMAXOe4C4pQ8M5r 5yZUboWFxuQadvASm0m1Jw/3zpX3NM9dNz5urYh4zA7DlaS0gDIxSEelrBwTj5eHWqbG Xu+1YF0GLkkh/1dDIcn+hM0DaWtBwxuNrZh6H5c1wCwwhL6og+MW70j9YhaOfikXLmSZ qheUWgorLBkmaPpWkwSvcT0ebA9FbVOufJ7xUab3p01HCtJpezmjhvmDCevCJozHmPDU ox5Xp61DwykqK2Wi/qpBTWl4SEjiIdg2/olHD1f37tm6ihsCuwxSIOw6EWrSBqVyu9xx sQnQ==
X-Gm-Message-State: APjAAAVBgrlhFXiGl1XLqZXSRTgfhY0QiDfdkZVnow2WP16+Imzi5V6F I/stmvIpr/c9ouWe/MJ2g2ufuxu1VfyrkgtIAF6H8/dLbzY=
X-Google-Smtp-Source: APXvYqzdqV+81lFeMC5GiqC3pnQB6RAh1gGSyQb+PHLVf8RSe3t213PUPx78H2+T16R219D63Xz+X7xz1AMpQQacjqI=
X-Received: by 2002:a0c:f241:: with SMTP id z1mr3245250qvl.53.1574414561724; Fri, 22 Nov 2019 01:22:41 -0800 (PST)
MIME-Version: 1.0
References: <BYAPR05MB394365C9E4719913BEC0809CD5490@BYAPR05MB3943.namprd05.prod.outlook.com>
In-Reply-To: <BYAPR05MB394365C9E4719913BEC0809CD5490@BYAPR05MB3943.namprd05.prod.outlook.com>
From: Robert Raszuk <robert@raszuk.net>
Date: Fri, 22 Nov 2019 10:22:34 +0100
Message-ID: <CAOj+MMFOueodpR-06AN47aND6_9WJAwPaXMTaP-0nzd0HCVzKA@mail.gmail.com>
To: Shraddha Hegde <shraddha=40juniper.net@dmarc.ietf.org>
Cc: "rtgwg@ietf.org" <rtgwg@ietf.org>, "spring@ietf.org" <spring@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000ae5fe50597ebf4ce"
Archived-At: <https://mailarchive.ietf.org/arch/msg/spring/4LbnpR6WFHCcu7YaJj9R0g2zSoo>
Subject: Re: [spring] Draft for Node protection of intermediate nodes in SR Paths
X-BeenThere: spring@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Source Packet Routing in NetworkinG \(SPRING\)" <spring.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spring>, <mailto:spring-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spring/>
List-Post: <mailto:spring@ietf.org>
List-Help: <mailto:spring-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spring>, <mailto:spring-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Nov 2019 09:22:45 -0000

Hi Shraddha,

I have one question to the document.

As you know the critical element for the effective protection of any scheme
is the failure detection. On that your draft seems to have just one little
paragraph:

   Note that R7 activates the node-protecting backup path when it
   detects that the link to R8 has failed.  R7 does not know that node
   R8 has actually failed.  However, the node-protecting backup path is
   computed assuming that the failure of the link to R8 implies that R8
   has failed.


Well IMO this is not enough. Specifically there can be a lot of types of
node failure when link is still up. Moreover there can be even running BFD
across the link just fine when say fabric failure occurs at R8.

While this is not solely issue with this draft, it is our common IETF
failure to provide correct means of detecting end to end path or fragments
of path failures (I am specifically not calling them segment here :).

For example I propose that to effectively detect R8 failure as node failure
which is the topic of your proposal a mechanism is clearly defined and
includes bi-dir data plane probes send between R7-R9, R3-R7, R4-R7, R4-R9,
R3-R9

Many thx,
Robert.


On Fri, Nov 22, 2019 at 4:38 AM Shraddha Hegde <shraddha=
40juniper.net@dmarc.ietf.org> wrote:

> WG,
>
> This is the draft I pointed out that talks about solutions for providing
> node-protection.
> It covers Anycast case as well as keeping forwarding plane longer.
>
> *https://tools.ietf.org/html/draft-hegde-spring-node-protection-for-sr-te-paths-05*
> <https://tools.ietf.org/html/draft-hegde-spring-node-protection-for-sr-te-paths-05>
>
> Review and comments solicited.
>
> Rgds
> Shraddha
>
> _______________________________________________
> rtgwg mailing list
> rtgwg@ietf.org
> https://www.ietf.org/mailman/listinfo/rtgwg
>