[Lsr] Doubt regarding A bit set/unset

Gurusiddesh Nidasesi <gurusiddesh.nidasesi@ipinfusion.com> Mon, 19 April 2021 10:12 UTC

MIME-Version: 1.0
From: Gurusiddesh Nidasesi <gurusiddesh.nidasesi@ipinfusion.com>
Date: Mon, 19 Apr 2021 15:42:35 +0530
Message-ID: <CAHhGMfEyyBNRCY6qbc-K8Yq1PoSwB3qVLitP4NVKn80fY85FbA@mail.gmail.com>
To: lsr@ietf.org
Cc: Vikram Agrawal <vikram.agrawal@ipinfusion.com>, Mahalakshmi Kumar <mahalakshmi.udhaya@ipinfusion.com>, Dona Maria John <dona.john@ipinfusion.com>, ginsberg@cisco.com, stefano@previdi.net, spencer.giacalone@gmail.com
Content-Type: multipart/alternative; boundary="00000000000049e86805c0509230"
Archived-At: <https://mailarchive.ietf.org/arch/msg/lsr/uN_U5wCXSrGgTO6Lsrpwxu6VaC8>
Subject: [Lsr] Doubt regarding A bit set/unset
Precedence: list

Hi All,

I had a query regarding setting/unsetting A bit.

https://tools.ietf.org/html/rfc8570#section-4.1 states that

A bit:  This field represents the Anomalous (A) bit.  The A bit is
      set when the measured value of this parameter exceeds its
      configured maximum threshold.  The A bit is cleared when the
      measured value falls below its configured reuse threshold.  If the
      A bit is cleared, the sub-TLV represents steady-state link
      performance.


So does it mean we have to have two configurations one for reuse and
another for maximum threshold?

Will below example follow the RFC?

reuse threshold : 50 usec

maximum threshold : 100 usec

1st measured value : 110 usec

conclusion: Set A bit.


2nd measured value : 75 usec

conclusion : Do nothing (Maintain pervious state of A bit as the value
is less than reuse or greater than threshold)


3rd measurement value : 30 usec

conclusion: Unset A bit.


 If we have to have two configuration for threshold to set/unset A
bit, will they be different from the threshold that we use for
advertisements?



Regards,
Gurusiddesh V N

-- 
.

[Lsr] Doubt regarding A bit set/unset Gurusiddesh Nidasesi