Re: [bmwg] [RTG-DIR] bmwg Digest, Vol 200, Issue 6

[Sudhin <[e-mail]>]

Hi Joel,

Sure, I will put a note.

Regards,
Sudhin

From: "Joel M. Halpern" <[e-mail]>
Sent: Thu, 17 Jun 2021 19:23:29
To: "[e-mail]" <[e-mail]>
Cc: [e-mail]
Subject: Re: [RTG-DIR] bmwg Digest, Vol 200, Issue 6
 iWe couldn't verify the sender of this email.Thank you Sudhin.  If the observations have to be generic, then could
you at least say that this will be measured by observing the network
management counters that the implementations has chosen to expose?  And
maybe even note that this will likely need to be specific to the
implementation as said coutners are not currently standardized?

Yours,
Joel

On 6/17/2021 6:22 AM, Sudhin wrote:
> Hi Joel,
>
> Thank you for the comments. Appreciate it. Kindly find the answers
> inline and the modification will be done shortly, I will update the new
> version in a couple of days.
>
> Regards,
> Sudhin
>
> From: [e-mail]
> Sent: Thu, 17 Jun 2021 00:31:11
> To: [e-mail]
> Subject: bmwg Digest, Vol 200, Issue 6
>
> Send bmwg mailing list submissions to
>        [e-mail]
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://www.ietf.org/mailman/listinfo/bmwg
> <https://www.ietf.org/mailman/listinfo/bmwg==>
> or, via email, send a message with subject or body 'help' to
>        [e-mail]
>
> You can reach the person managing the list at
>        [e-mail]
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of bmwg digest..."
>
>
> Today's Topics:
>
>     1. Rtgdir last call review of draft-ietf-bmwg-evpntest-08
>          (Joel Halpern via Datatracker)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Wed, 16 Jun 2021 11:59:12 -0700
> From: Joel Halpern via Datatracker <[e-mail]>
> To: <[e-mail]>
> Cc: [e-mail], [e-mail],
>        [e-mail]
> Subject: [bmwg] Rtgdir last call review of draft-ietf-bmwg-evpntest-08
> Message-ID: <[e-mail]>
> Content-Type: text/plain; charset="utf-8"
>
> Reviewer: Joel Halpern
> Review result: Has Issues
>
> I have been selected as the Routing Directorate reviewer for this draft. The
> Routing Directorate seeks to review all routing or routing-related drafts as
> they pass through IETF last call and IESG review, and sometimes on special
> request. The purpose of the review is to provide assistance to the
> Routing ADs.
> For more information about the Routing Directorate, please see
> ?http://trac.tools.ietf.org/area/rtg/trac/wiki/RtgDir
> <http://trac.tools.ietf.org/area/rtg/trac/wiki/RtgDir==>
>
> Although these comments are primarily for the use of the Routing ADs, it
> would
> be helpful if you could consider them along with any other IETF Last Call
> comments that you receive, and strive to resolve them through discussion
> or by
> updating the draft.
>
> Document: draft-name-version.txt
> Reviewer: your-name
> Review Date: date
> IETF LC End Date: date-if-known
> Intended Status: copy-from-I-D
>
> Summary:
> I have some minor concerns about this document that I think should be
> resolved
> before publication.
>
> Major Comments: N/A
>
> Minor Comments:
>       Reading section 3.1 on the rate for learning addresses, I am left
> guessing
>       how the procedure is to be performed.   The text references RFC 2889
> section
>       5.8, but only for the meaning for the terms.   The test procedure is
> clearly
>       different since that test relies on observing flooding.   As best I can
>       guess, the test assumes that there is an observable (Netconf ? YANG ?)
>       variable that reports how many local MAC addresses the device under test
>       has learned.   It would be good to be more explicit about that, if
> possible
>       pointing to the YANG module that defines the parameter to be observed.
>    A similar clarification would be helpful on section 3.2 (on control
> plane MAC
>    learning). It probably would be helpful if sections 3.3 and 3.4 then
>    referenced sections 3.1 and 3.2 respectively for what is being
> observed. This
>    probably applies to section 4 as well.   If the same variables are to
> be used,
>    then a simple reference to the earlier description would seem to suffice.
>
> Sudhin>>>> it must be generic because not all the evpn features are
> supported in Yang models and it is up to the user choice that is reason
> any specific ways to capture the data is omitted.
>
>    I believe that section 3.8 on high availability is intended to cause a
> switch
>    of traffic path from DUT to MHPE2.    However, the text in that section
> never
>    refers to MHPE 2.   It refers to switch of routing processor.   It is
> possible
>    that this is intended to be a redundancy test within DUT.   If so, it would
>    help to be more explicit, since as far as I know we do not standardize
> that
>    behavior.
>
> I am left puzzled as to the need for MHPE2 in these tests.   I assume
> there is
> some obvious and simple reason for including it that I missed.   Could
> you add
> an explanation?
>
> Sudhin>>> MHPE2 is very much needed in multi homing scenario, it plays
> as a standby role in testing, sure will add an explnation in the section
>
>   "Test Setup Configuration".
>
>
> Nits:
>       At the end of section 2, the text reads "The X is used as variable..."
>       Could you change that to "The X below is used as a variable ..."?   I
> spent
>       some time looking backwards for the X.
>
> Sudhin >>>> Sure
>
>    The equation at the end of section 3.9 (ARD / ND scaling) is somewhat
>    misleading.   It uses the same v1, v2, ..vn in successive lines to
> implicitly
>    refer to the IPv4 measurements and the IPv6 measurements.   It would be
> good
>    to name these separately, as obviously the same calculation can not
> produce
>    two different results.
>
> Sudhin>>> sure will change.
>
>
>
>
> ------------------------------
>
> Subject: Digest Footer
>
> _______________________________________________
> bmwg mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/bmwg
> <https://www.ietf.org/mailman/listinfo/bmwg==>
>
>
> ------------------------------
>
> End of bmwg Digest, Vol 200, Issue 6
> ************************************