Re: [mpls] Opsdir last call review of draft-ietf-mpls-bfd-directed-27

Greg Mirsky <gregimirsky@gmail.com> Tue, 16 April 2024 10:00 UTC

Return-Path: <gregimirsky@gmail.com>
X-Original-To: mpls@ietfa.amsl.com
Delivered-To: mpls@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EF3B2C14F694; Tue, 16 Apr 2024 03:00:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.095
X-Spam-Level:
X-Spam-Status: No, score=-2.095 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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=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 ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gOhUDunyOR4n; Tue, 16 Apr 2024 03:00:43 -0700 (PDT)
Received: from mail-yw1-x112f.google.com (mail-yw1-x112f.google.com [IPv6:2607:f8b0:4864:20::112f]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 71AA5C14F5E0; Tue, 16 Apr 2024 03:00:43 -0700 (PDT)
Received: by mail-yw1-x112f.google.com with SMTP id 00721157ae682-61500da846fso30160127b3.1; Tue, 16 Apr 2024 03:00:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1713261642; x=1713866442; darn=ietf.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=8V4CxHkxoFaif1yrtcAbEHUf4Q7f/1Fy5UhvkmPqQ60=; b=PLfXTdLEhVHVeqoZekrboJ/aI7Xy622nyZAJyrRP6UWCTeA0KvEPxTOuF8XcWRRaE3 foA6oB1Fvkp2oWANuNYky+Osn89DY2c8PFcd3OM4IWV1Hjy9pCNSuF4unij1v8lQeg6L IkeON0R7Yiq+TwiCxczj/zYrhi5ylbdpW8B8oQEglY87dgJP3yWD+Smd90KJrgVg7Wgj q4W4g5jrmcPnS7pJCLgsasyCPYHUy8lq37V/AqKHcfbJGmjq7XJ9srw6K+RHku1ZnaH+ RWsDrPJlhcXOtrbuVHHq8NgfuTFJhMFOa63g5XVQV7VfRYxA7vn1JpEAPJNRyP8X04PA lUZA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1713261642; x=1713866442; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=8V4CxHkxoFaif1yrtcAbEHUf4Q7f/1Fy5UhvkmPqQ60=; b=uTidmj5TVZn7AWWHXgpyS/0yRhq4zOmzd2gmwaHhkKrRtAUAnRxtl7iO+JYXi2oF73 /N8GuoWlp5A4iHo58yFQ6tWf5k9jUHl/o2U/S9iy/5L+lFwo6bU1yigcZEu4RqIzQJN9 nypu+4xIViSwcDF8lYpsDLeOv1cft6/IA1NlE3Mrxl0NXHLbTyDr52TpucaJb4PIBgCm LvSr4xPhcE3lOqCtma2cbVyWa7v7Ty9rPeXAbsFiVTGxkMGVxa12ggWgvcI6NRAKpy6e Jar0R7aBybl/x5axR6u0M/SZT6cpQm4ywB5da3RFCE25PxnIqUiV3I7v/oX55GjkvD+M FMgQ==
X-Forwarded-Encrypted: i=1; AJvYcCVK7SACfclyfRUDPQk3u4tFI0/0wC9LCfwuQPU+TQ21sELT2V+Vh7CGk5SHsQi0Rr+d8+sLnNzSqN5xdRVgMPGyIrAtv4elYsZVZDNjGjS0yfMONNAQ3PN/yqbrreovjbWNwKJ625atbNXe8sF/QmL0NmBTxI251aFnaPyO
X-Gm-Message-State: AOJu0YzIFBzxXUDwNFcoOYwpXLntGuqBzz83hSGV5gvcslOqs34x2d+c ranMtIi6jjPjUFjJ1YuiJtzapPLnIg5y8lTm5yqgOS+JjKlRHpT9gi6SOz65DlQYc2Mw7ydZp2w NRR51BpZxWEmijZJ3eicWPCYZvw3jp7wX/Z0=
X-Google-Smtp-Source: AGHT+IGJ8/lvRY2J5OuJwcPOPhcde9XqaEy+hzoVzTP02+zKZdqZ0PBHWawyAtP0yCjddVun+zU3Aq910b4Vg4RDzZU=
X-Received: by 2002:a0d:cb8f:0:b0:61a:d2a0:5497 with SMTP id n137-20020a0dcb8f000000b0061ad2a05497mr4839360ywd.8.1713261642524; Tue, 16 Apr 2024 03:00:42 -0700 (PDT)
MIME-Version: 1.0
References: <171294228645.36819.2486980913632249384@ietfa.amsl.com> <CA+RyBmVr96atALM3p5jAPxux-r-4-Q-OnULuUcQ_dwAAP1=HMg@mail.gmail.com> <BN9PR11MB537127AF72A2B747F2831437B8092@BN9PR11MB5371.namprd11.prod.outlook.com> <CA+RyBmW+v-nYzHdy5quuqR4qMittnPjQU6hHqgzFmamr04PpcQ@mail.gmail.com>
In-Reply-To: <CA+RyBmW+v-nYzHdy5quuqR4qMittnPjQU6hHqgzFmamr04PpcQ@mail.gmail.com>
From: Greg Mirsky <gregimirsky@gmail.com>
Date: Tue, 16 Apr 2024 12:00:32 +0200
Message-ID: <CA+RyBmWRpZCOz9RgVU4qVT0FPrBoGsL4ZqC2p4sDtfG6zzfJ8w@mail.gmail.com>
To: "Joe Clarke (jclarke)" <jclarke@cisco.com>
Cc: "ops-dir@ietf.org" <ops-dir@ietf.org>, "draft-ietf-mpls-bfd-directed.all@ietf.org" <draft-ietf-mpls-bfd-directed.all@ietf.org>, "last-call@ietf.org" <last-call@ietf.org>, "mpls@ietf.org" <mpls@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000009c2dd9061633cf50"
Archived-At: <https://mailarchive.ietf.org/arch/msg/mpls/HlrbeAdtV0p4_6GJRkb1Zn96gf8>
Subject: Re: [mpls] Opsdir last call review of draft-ietf-mpls-bfd-directed-27
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mpls/>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 16 Apr 2024 10:00:48 -0000

Hi Joe,
I've uploaded the new version that includes updates resulting from our
discussion.
Name:     draft-ietf-mpls-bfd-directed
Revision: 28
Title:    Bidirectional Forwarding Detection (BFD) Directed Return Path for
MPLS Label Switched Paths (LSPs)
Date:     2024-04-16
Group:    mpls
Pages:    11
URL:
https://www.ietf.org/archive/id/draft-ietf-mpls-bfd-directed-28.txt
Status:   https://datatracker.ietf.org/doc/draft-ietf-mpls-bfd-directed/
HTML:
https://www.ietf.org/archive/id/draft-ietf-mpls-bfd-directed-28.html
HTMLized: https://datatracker.ietf.org/doc/html/draft-ietf-mpls-bfd-directed
Diff:
https://author-tools.ietf.org/iddiff?url2=draft-ietf-mpls-bfd-directed-28

Thank you for your help in improving the draft.

Regards,
Greg

On Mon, Apr 15, 2024 at 4:02 PM Greg Mirsky <gregimirsky@gmail.com> wrote:

> Thank you, Joe, for your quick response. I'll upload the updated version
> with the updates addressing the TSVART review.
>
> Regards,
> Greg
>
> On Mon, Apr 15, 2024 at 3:48 PM Joe Clarke (jclarke) <jclarke@cisco.com>
> wrote:
>
>> Thanks for the modifications.  They read well to me.  As to the question…
>>
>>
>>
>> Finally, my question.  In the Operational Consideration, what would (or
>> should)
>> happen to the underlying service while the LSP ping is processed in the
>> case of
>> reverse-path FEC failure?  Is there guidance to provide to maintain
>> service
>> while this new session might be established?
>>
>> GIM>> That, in my opinion, is the formative question; thank you for that.
>> It is assumed that the operator controls the network to which the Reverse
>> PAth Control TLV is applied. If theat is the case, the failure of the
>> installed reverse path is a case of the network failure. The operator, I
>> assume that from the ingress BFD peer, is notified, and then can switch the
>> reverse path of the BFD session. I imagine, that there could be other
>> switchover policies, but I believe that it is essential that the ingress
>> BFD peer detects the network failure if the reverse path of the BFD session
>> fails. WDYT?
>>
>>
>>
>> JMC: I read this differently the first time.  Thinking on your figure, I
>> agree with you.  If the tunnel A-B-C-D-G-H is good, but the reverse
>> H-G-D-C-B-A is not (and this is the reverse path requested), then we can
>> assume there isn’t bidirectional forwarding and the ingress peer should be
>> informed.  That likely should warrant a service interruption unless there
>> is another viable failover path.
>>
>>
>>
>> Joe
>>
>