IETF Logo Mail Archive

Re: [Lsr] Working Group Last Call for "OSPF Strict-Mode for BFD" - draft-ietf-lsr-ospf-bfd-strict-mode-04

Ketan Talaulikar <ketant.ietf@gmail.com> Thu, 03 February 2022 15:30 UTC

Return-Path: <ketant.ietf@gmail.com>
X-Original-To: lsr@ietfa.amsl.com
Delivered-To: lsr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6C68D3A08E3; Thu, 3 Feb 2022 07:30:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.096
X-Spam-Level:
X-Spam-Status: No, score=-2.096 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_DNSWL_BLOCKED=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=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 aywnGH5b01Xx; Thu, 3 Feb 2022 07:30:52 -0800 (PST)
Received: from mail-vk1-xa2a.google.com (mail-vk1-xa2a.google.com [IPv6:2607:f8b0:4864:20::a2a]) (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 B94423A08DC; Thu, 3 Feb 2022 07:30:52 -0800 (PST)
Received: by mail-vk1-xa2a.google.com with SMTP id m131so1932674vkm.7; Thu, 03 Feb 2022 07:30:52 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=nGUoVDbLdKRAiaQFR5N665vb+zZZure52QPqKv4H7fY=; b=ecC1SfD38Xb8wNqrrI63Er5sAbzBAPwoJxlOXw0456BOle7uONChlc4ExE5w8ERRrh I6zvBIICbCVxlGec7jLzY+wGJlBepZwZweuR3IRbbLUUqnvscr4q1/wC4C/QPU5pFLXL dopOhQelv/j7QmMZpnNr4oHv7N6MPrWS5mjBPhEgX0HzjkrgAjoFOIXvkwTZuxJumIEy KfFgyFV+1DtTudaJmenfaUh+FHGUc5I+JH0pp1EXshSeHvbv4kjWn2bw3wKZFTdOcoZ3 Z0GxGox+AfjkTuv1NJTuqEv6puyQBZohBGOw10Mjl4j6NNIW/d11FanP3a1yqdVtwj1u dgYQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=nGUoVDbLdKRAiaQFR5N665vb+zZZure52QPqKv4H7fY=; b=NaNkRQ3kzz3sNAZLbHcdxrj0KgQVSkz9kt2EmL/MdLtNqv0DZLuKCRZsghdm7zGVnd QdMOC3ZlQlpHBdlj7O5Bfb0M46AdMcCWzfNZkkDSGD22F4sk6qZGFaQ3GI/AmV+c4CzK QaiS3YOyS3EkJIlKi74ck0q0kmensbrLFmyKQzZha899BZdCEB/QUt/9zztkGRKs2I8q Q5m4w2HFCXo/I/7PjGhfiUtkjtF3uGNvZd89USo+XxIWwOwsJuwf5QlaIZ5E9SzPYX9v wrrLN+b39e7jA6jg+rhVD70gwMYQmdW9+VTCl69UonfgBsbx3qIMzlntCBnlgvtg+89v z+Cw==
X-Gm-Message-State: AOAM531GhrZR57WNURDmvFfRqxGsVZwXNYr6h1uP/uofIzLl/slrW9Ca hMGpTPuGdAuC1qDQSwQ0vgTw2wX88/K/861w4N6+NTaIUEk=
X-Google-Smtp-Source: ABdhPJxvhfMtlEM2+ysjuuoiDezK76c81Ul67kSRpixfqoy3Ofo0ViDkZmk+IwUTiBYYXGtOv4yFQYVhtp0mIBqRt7I=
X-Received: by 2002:a1f:4e03:: with SMTP id c3mr14641197vkb.7.1643902250902; Thu, 03 Feb 2022 07:30:50 -0800 (PST)
MIME-Version: 1.0
References: <EBCD00A9-97D1-4D5E-A1F3-7BA1D6351E12@cisco.com> <71EDA220-3760-455C-856F-B76EC142068C@cisco.com>
In-Reply-To: <71EDA220-3760-455C-856F-B76EC142068C@cisco.com>
From: Ketan Talaulikar <ketant.ietf@gmail.com>
Date: Thu, 03 Feb 2022 21:00:38 +0530
Message-ID: <CAH6gdPyY2YwNzoGwNhx9cP2Z+RRv9Hgvrv=kSfd8kPGniyirPg@mail.gmail.com>
To: "Acee Lindem (acee)" <acee@cisco.com>
Cc: "Acee Lindem (acee)" <acee=40cisco.com@dmarc.ietf.org>, "lsr@ietf.org" <lsr@ietf.org>, "draft-ietf-lsr-ospf-bfd-strict-mode@ietf.org" <draft-ietf-lsr-ospf-bfd-strict-mode@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000b5e81005d71ed1e3"
Archived-At: <https://mailarchive.ietf.org/arch/msg/lsr/lnrYvEoBqLJrbiIApNxzqeJ-YbM>
Subject: Re: [Lsr] Working Group Last Call for "OSPF Strict-Mode for BFD" - draft-ietf-lsr-ospf-bfd-strict-mode-04
X-BeenThere: lsr@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Link State Routing Working Group <lsr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/lsr>, <mailto:lsr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/lsr/>
List-Post: <mailto:lsr@ietf.org>
List-Help: <mailto:lsr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/lsr>, <mailto:lsr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Feb 2022 15:30:55 -0000

Hi Acee,

The authors had picked the term "OSPF BFD Strict-Mode" originally - please
refer to
https://datatracker.ietf.org/doc/html/draft-ketant-lsr-ospf-bfd-strict-mode-01.
However, post IETF presentation, we got feedback from WG members that the
term was misleading and gave an impression that the proposal was
introducing a "strict-mode" in BFD. What we are doing is introducing a
"strict-mode" of operation in OSPF for BFD usage.

We are open to any suggestions for change/clarity.

Thanks,
Ketan


On Thu, Feb 3, 2022 at 2:07 AM Acee Lindem (acee) <acee@cisco.com> wrote:

> Speaking as Document Shepherd:
>
>
>
> I have some editorial comments that I will pass on to the authors offline.
> One change I didn’t suggest since it was a big change was from “Strict-Mode
> for BFD” to simply “BFD Strict-Mode”. What are your thoughts on this?
>
>
>
> We’ve had some good discussion and an updated version is coming with some
> updates based on that discussion. Remember that we don’t necessarily have
> to incorporate every suggested change but simply need to conclude the
> discussion.
>
>
>
> Thanks,
>
> Acee
>
>
>
> *From: *"Acee Lindem (acee)" <acee=40cisco.com@dmarc.ietf.org>
> *Date: *Friday, January 28, 2022 at 7:24 AM
> *To: *Acee Lindem <acee@cisco.com>, "lsr@ietf.org" <lsr@ietf.org>
> *Cc: *"draft-ietf-lsr-ospf-bfd-strict-mode@ietf.org" <
> draft-ietf-lsr-ospf-bfd-strict-mode@ietf.org>
> *Subject: *Re: [Lsr] Working Group Last Call for "OSPF Strict-Mode for
> BFD" - draft-ietf-lsr-ospf-bfd-strict-mode-04
>
>
>
> Speaking as WG member:
>
>
>
> I support publication of the document. As indicated by the Albert Fu, it
> has been implemented by two vendors. I will provide WG Last Call comments
> when I prepare the Shepherd’s report.
>
>
>
> Thanks,
>
> Acee
>
>
>
> *From: *Lsr <lsr-bounces@ietf.org> on behalf of "Acee Lindem (acee)"
> <acee=40cisco.com@dmarc.ietf.org>
> *Date: *Thursday, January 27, 2022 at 12:09 PM
> *To: *"lsr@ietf.org" <lsr@ietf.org>
> *Cc: *"draft-ietf-lsr-ospf-bfd-strict-mode@ietf.org" <
> draft-ietf-lsr-ospf-bfd-strict-mode@ietf.org>
> *Subject: *[Lsr] Working Group Last Call for "OSPF Strict-Mode for BFD" -
> draft-ietf-lsr-ospf-bfd-strict-mode-04
>
>
>
> LSR WG,
>
>
>
> This begins a two week last call for the subject draft. Please indicate
> your support or objection on this list prior to 12:00 AM UTC on February 11
> th, 20222. Also, review comments are certainly welcome.
>
> Thanks,
> Acee
>
>
>

v2.23.0 | Report a Bug | By Email