Re: New Version Notification for draft-ietf-bfd-stability-06.txt

Santosh P K <santosh.pallagatti@gmail.com> Fri, 24 July 2020 14:31 UTC

Return-Path: <santosh.pallagatti@gmail.com>
X-Original-To: rtg-bfd@ietfa.amsl.com
Delivered-To: rtg-bfd@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1157F3A09F1 for <rtg-bfd@ietfa.amsl.com>; Fri, 24 Jul 2020 07:31:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 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, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 h8QZZmKhPtJP for <rtg-bfd@ietfa.amsl.com>; Fri, 24 Jul 2020 07:31:22 -0700 (PDT)
Received: from mail-il1-x130.google.com (mail-il1-x130.google.com [IPv6:2607:f8b0: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 2D09F3A09ED for <rtg-bfd@ietf.org>; Fri, 24 Jul 2020 07:31:22 -0700 (PDT)
Received: by mail-il1-x130.google.com with SMTP id i138so1466818ild.9 for <rtg-bfd@ietf.org>; Fri, 24 Jul 2020 07:31:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=na9bCJP8D6pGaj/BJr1BS789wYZBnTH0vwP8q1geT/o=; b=EQbwcaY6FTrl93msatHgvmwKSYR5w3b8iJAm2MVgcPKETccGerB7hV110M7BJmOkVR lH1kpEvkVjo/X7xu3XpsIxi+TmE0ym3sL4Lsdp4Z3oBSnaa3ymoICa9rgxzxhX6QlgXe 1TPBuZ85XeUFg/3YBFGniDX+61JNiX781smnMRPNP4P3Nd+hgNU3SJYQqRNwgVwQ00Y0 wsSqlQYWJe9MJerODu7amhtOpeJVHnxJ1wb/oN/6iHw2biWsw5mj1yJvbG5kmUvDnsTc 3dF+NgxGvH5K5zt6WOOl/H1+IhtBEHfMna5GraNPSQUmGJerts+UlfEE1zh5nHd93d5g LzYA==
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=na9bCJP8D6pGaj/BJr1BS789wYZBnTH0vwP8q1geT/o=; b=JKp04LFsizsBmPqnO3yI08eHCOhw20alre6FFie5wuN5V5/V3/fLX9nXgRPmP7v8Nl /h5qvKTR17TwvLPrajgXiImA5dy3+F3DwyKMOXzGG4vi4GajyOzOrgb5LrzYBKojbKnS gC4umnR4kvo8gJHQMeWsAecTfsNxvTaGrloIEuaurAK8g8Y79zhOvmknYp4I3pgFyN4P 0dPqKfDxpe/E0avNdt9oYiaoRAdzZfv0Ok5cATK66YFuAvBpGRCKbj40jAZDEMRfY1Ey V+8DHd4Uxuduz68wKVgLRagU8L0rRjNptvsfSNxjbdClEy+sLio82oiP0g3zbP050kO7 Y2fw==
X-Gm-Message-State: AOAM533Ts2Uu/yvLw+9sTi7gZmB3BG/1SsE1J9vHGf5VB7rkpbm1jGWM gOAQUpJPtb5+5xihs45cSfsRKBZkmVm8nPvTwivkNcLD
X-Google-Smtp-Source: ABdhPJyftdhnN8RICMKqo3kohDi6CS/In1c4Iswo49LYHghUymNqNJTVINIRuaOojElfH3yYNyN5ojbZNXAKXmj08qY=
X-Received: by 2002:a92:50f:: with SMTP id q15mr10846427ile.38.1595601080097; Fri, 24 Jul 2020 07:31:20 -0700 (PDT)
MIME-Version: 1.0
References: <159463868413.22444.9991690475315066846@ietfa.amsl.com> <CACi9rdsvv=cm1xnYa4Hp6mJukogJgkrRuBrCKByOVfmD38Gi+A@mail.gmail.com> <1B318C9F-DF6A-4762-9AAF-A2AD8A025E24@cisco.com>
In-Reply-To: <1B318C9F-DF6A-4762-9AAF-A2AD8A025E24@cisco.com>
From: Santosh P K <santosh.pallagatti@gmail.com>
Date: Fri, 24 Jul 2020 20:01:09 +0530
Message-ID: <CACi9rdsR27gYUdRHTSZzW07RRVu4tgsg_e1pq5RA1VWFRcyr_A@mail.gmail.com>
Subject: Re: New Version Notification for draft-ietf-bfd-stability-06.txt
To: "Reshad Rahman (rrahman)" <rrahman@cisco.com>
Cc: rtg-bfd WG <rtg-bfd@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000095208205ab30d3b6"
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtg-bfd/NmjeLGl10uW3Q0aiovatTtrUjgk>
X-BeenThere: rtg-bfd@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "RTG Area: Bidirectional Forwarding Detection DT" <rtg-bfd.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtg-bfd>, <mailto:rtg-bfd-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rtg-bfd/>
List-Post: <mailto:rtg-bfd@ietf.org>
List-Help: <mailto:rtg-bfd-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtg-bfd>, <mailto:rtg-bfd-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Jul 2020 14:31:24 -0000

Reshad,
  Thanks again. I will address these comments.

Thanks
Santosh P K

On Fri, Jul 24, 2020 at 8:13 AM Reshad Rahman (rrahman) <rrahman@cisco.com>
wrote:

> Hi Santosh,
>
>
>
> Thanks for addressing the comments.
>
>
>
> General: NULL authentication TLV is still used, should be replaced with
> NULL authentication type or section as appropriate.
>
> Be consistent for Null v/s NULL (NULL Auth is used in
> bfd-optimizing-authentication)
>
>
>
> Introduction
>
> s/detect lost packet/detect lost packets/
>
>
>
> Section 3 Use Cases:
>
> s/any BFD packet loss if loss/any BFD packet loss if the loss/
>
> s/BFD implementation/BFD implementations/
>
> Where the text says “failure of a link”, might be better to say “failure
> of a datapath”?
>
> Informative references to CFM and TWAMP would be useful
>
>
>
> Section 4
>
> “by appending the Null-Authentication type “. Suggest “by appending an authentication section with the NULL Authentication type “
>
>
>
> Section 5
>
> “BFD uses authentication TLV”, suggest change to “BFD uses an
> authentication section”.
>
>
>
> “BFD packets MUST include NULL-Auth TLV”. Change to “BFD control packets
> MUST include an authentication section with the NULL Authentication type”
>
>
>
> Section 5.1
>
>
>
> “The first BFD NULL-Auth type processed by the receiver…”.  Change to  “The first BFD authentication section with the NULL Authentication type, in a valid BFD control packet, processed by the receiver” .
>
> Also, does it have to be NULL Auth, I believe it can be any auth with sequence number? If that’s the case change to  “The first BFD authentication section with a non-zero sequence number, in a valid BFD control packet, processed by the receiver is used for….”.
>
>
>
> Regards,
>
> Reshad.
>
>
>
> *From: *Rtg-bfd <rtg-bfd-bounces@ietf.org> on behalf of Santosh P K <
> santosh.pallagatti@gmail.com>
> *Date: *Sunday, July 19, 2020 at 4:06 PM
> *To: *"rtg-bfd@ietf.org" <rtg-bfd@ietf.org>
> *Subject: *Fwd: New Version Notification for
> draft-ietf-bfd-stability-06.txt
>
>
>
> Hello All,
>
>     A new version of draft for BFD-stablity is here for review. Changes
> include addressing shepherd comments as provided here.
> https://datatracker.ietf.org/doc/draft-ietf-bfd-stability/shepherdwriteup/.
> Please also see attached diff.
>
>
>
> Thanks
>
> Santosh P K
>
> ---------- Forwarded message ---------
> From: <internet-drafts@ietf.org>
> Date: Mon, Jul 13, 2020 at 4:41 PM
> Subject: New Version Notification for draft-ietf-bfd-stability-06.txt
> To: Mach Chen <mach.chen@huawei.com>om>, Ankur Saxena <ankurpsaxena@gmail.com>om>,
> Peng Fan <fanp08@gmail.com>om>, Mahesh Jethanandani <mjethanandani@gmail.com>om>,
> Ashesh Mishra <mishra.ashesh@gmail.com>om>, Santosh Pallagatti <
> santosh.pallagatti@gmail.com>
>
>
>
>
> A new version of I-D, draft-ietf-bfd-stability-06.txt
> has been successfully submitted by Santosh Pallagatti and posted to the
> IETF repository.
>
> Name:           draft-ietf-bfd-stability
> Revision:       06
> Title:          BFD Stability
> Document date:  2020-07-13
> Group:          bfd
> Pages:          6
> URL:
> https://www.ietf.org/internet-drafts/draft-ietf-bfd-stability-06.txt
> Status:         https://datatracker.ietf.org/doc/draft-ietf-bfd-stability/
> Htmlized:       https://tools.ietf.org/html/draft-ietf-bfd-stability-06
> Htmlized:
> https://datatracker.ietf.org/doc/html/draft-ietf-bfd-stability
> Diff:
> https://www.ietf.org/rfcdiff?url2=draft-ietf-bfd-stability-06
>
> Abstract:
>    This document describes extensions to the Bidirectional Forwarding
>    Detection (BFD) protocol to measure BFD stability.  Specifically, it
>    describes a mechanism for detection of BFD packet loss.
>
>
>
>
> Please note that it may take a couple of minutes from the time of
> submission
> until the htmlized version and diff are available at tools.ietf.org.
>
> The IETF Secretariat
>
>