[spring] Where a trigger for the protection switchover in SR-MPLS will come from?

Greg Mirsky <gregimirsky@gmail.com> Sun, 02 August 2020 23:56 UTC

Return-Path: <gregimirsky@gmail.com>
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 591D13A0DDD; Sun, 2 Aug 2020 16:56:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.198
X-Spam-Level:
X-Spam-Status: No, score=-0.198 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 U1w3n006X0ok; Sun, 2 Aug 2020 16:56:32 -0700 (PDT)
Received: from mail-lf1-x130.google.com (mail-lf1-x130.google.com [IPv6:2a00:1450:4864:20::130]) (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 E19F03A0DDC; Sun, 2 Aug 2020 16:56:31 -0700 (PDT)
Received: by mail-lf1-x130.google.com with SMTP id i19so19532327lfj.8; Sun, 02 Aug 2020 16:56:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=gwgwK3Aa7mK+y7VidIhNSHgx+qEt+kaYnSpI9hlF5hE=; b=FywlSW8tXMrURaw0VubM5/SZggN+tmDmjnqTP1bmAMxX3Zq7x2iU8FKKCeBp6K+MYv cyZouyu/5GDlecetMFc8K6Npjl7dPYenqvmNmpWBb67mybdSxJACJtkxSWIvFr+aJdhI NfZS3kDSXljKpX86+RoRlYrdimFXpm3EfDCouAdh6ZuTK3zJSDgGwFRQdfvuZB6xjB8f xWxWqHXKNi29ou7AuXFwsUbAflGpBkvxmG3kAZwF0gDihYb2ZnIzK7EbeFRAgOmUhzav kWDP5VvBXnuedOXwWZ2+eUtNvPCXFXMQIBiX8/9XcMKQBLoXc23Tc/F4Cxd4dqE4Cotb Zc7g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=gwgwK3Aa7mK+y7VidIhNSHgx+qEt+kaYnSpI9hlF5hE=; b=aIx921NiPmoeUAe/B5kySWfG+5Wim1PgmRN0DRZIhemPqCGDO+2x+eRIwsNJnh66XD pJw73qloIEmVZ7VDGUKURtdjiHyKheht3hbjauhm32OSlMOIz3hAriJvU9yVsORL9ZLi p5H7Fyr1mqdoFXtF5krBmntmHaybpJhWfAmrCchb4gbQO8itwCjg6vKhdl4m88lZw+PP s46RIpzCg7nhS2lkfSOFUhHsZcvJ0RGRYaCMtMhrGvEg0a/MgMlSjbvCyx1Xt3QjWwE9 FGGzWfL21UN1ohxNwPNFqWjZBFlPlE1UYxkX1VJgFUNAYRzCskR9+D38LIpTBdkgoZHZ lzLQ==
X-Gm-Message-State: AOAM532h/sKkn9oBWTmPOi20f635n66AEteyx9PUd2McjkVlhZSYd6oA Cc4mMLxdEwoTTFjE0ekLjZzmkqZGk8GiC2rZe8bO/g==
X-Google-Smtp-Source: ABdhPJxE5Gef6C/oFPMgRtvPeysav44OGD7HEOgQZvBYNeZTujuOyCzSNBtt3Nky2tOPH3ajAVEdYZ1sPVz4RuDJPac=
X-Received: by 2002:a19:be53:: with SMTP id o80mr7089166lff.33.1596412589727; Sun, 02 Aug 2020 16:56:29 -0700 (PDT)
MIME-Version: 1.0
From: Greg Mirsky <gregimirsky@gmail.com>
Date: Sun, 2 Aug 2020 16:56:18 -0700
Message-ID: <CA+RyBmULA2dbkp1ZEWRzH-W=Jr-DH7H6RorK77MVSxBkDjMBZg@mail.gmail.com>
To: spring <spring@ietf.org>, spring-chairs@ietf.org
Content-Type: multipart/alternative; boundary="0000000000005362d405abedc535"
Archived-At: <https://mailarchive.ietf.org/arch/msg/spring/Gi9cYzAqplfXQQsreSQld8EPGno>
Subject: [spring] Where a trigger for the protection switchover in SR-MPLS will come from?
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: Sun, 02 Aug 2020 23:56:33 -0000

Dear All,
after reviewing draft-hegde-spring-node-protection-for-sr-te-paths I've got
a question to ask Where a trigger for the protection switchover in SR-MPLS
will come from?
The draft discusses methods to provide local link and node protection.
Obviously, the protection is triggered by the detection of the failure. The
document refers to Section 5.2 RFC 8679 in which relationships between the
defect detection mechanism used and the scope of protection (link or node)
are discussed. RFC 8679 is MPLS-centric and, though not explicitly
referenced, BFD over MPLS LSP (RFC 5884) can be used as the defect
detection mechanism. To the best of my knowledge, SPRING WG doesn't have a
WG document describing defect detection mechanism in an SR-MPLS network.
Hence my question in the subject line. Of course, not having a solution
does not affect the value
of draft-hegde-spring-node-protection-for-sr-te-paths but it probably would
stand out as the more comprehensive solution if the specification of the
defect detection in SR-MPLS was produced by the SPRING WG soon after.

Regards,
Greg