[nvo3] Zaheduzzaman Sarker's No Objection on draft-ietf-nvo3-bfd-geneve-12: (with COMMENT)

Zaheduzzaman Sarker via Datatracker <noreply@ietf.org> Mon, 07 August 2023 13:39 UTC

Return-Path: <noreply@ietf.org>
X-Original-To: nvo3@ietf.org
Delivered-To: nvo3@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 9A618C1519BD; Mon, 7 Aug 2023 06:39:01 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Zaheduzzaman Sarker via Datatracker <noreply@ietf.org>
To: The IESG <iesg@ietf.org>
Cc: draft-ietf-nvo3-bfd-geneve@ietf.org, nvo3-chairs@ietf.org, nvo3@ietf.org, matthew.bocci@nokia.com, matthew.bocci@nokia.com
X-Test-IDTracker: no
X-IETF-IDTracker: 11.5.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Zaheduzzaman Sarker <zahed.sarker.ietf@gmail.com>
Message-ID: <169141554162.7606.6879172772467364239@ietfa.amsl.com>
Date: Mon, 07 Aug 2023 06:39:01 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/nvo3/63x_X0efUHIVZKbUiWHgZdaAXVs>
Subject: [nvo3] Zaheduzzaman Sarker's No Objection on draft-ietf-nvo3-bfd-geneve-12: (with COMMENT)
X-BeenThere: nvo3@ietf.org
X-Mailman-Version: 2.1.39
List-Id: "Network Virtualization Overlays \(NVO3\) Working Group" <nvo3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/nvo3>, <mailto:nvo3-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/nvo3/>
List-Post: <mailto:nvo3@ietf.org>
List-Help: <mailto:nvo3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/nvo3>, <mailto:nvo3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 07 Aug 2023 13:39:01 -0000

Zaheduzzaman Sarker has entered the following ballot position for
draft-ietf-nvo3-bfd-geneve-12: No Objection

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to https://www.ietf.org/about/groups/iesg/statements/handling-ballot-positions/ 
for more information about how to handle DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-nvo3-bfd-geneve/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

Thanks for working on this specification. Special thanks to Magnus Westerlund
for identifying an important aspect in his TSVART review and I am happy to see
the resolution in the -11 version of this doc.

I have stumbled upon similar clarification issues that John has brought up in
his discuss. It not clear to me how this validation need to be done as written
in Section 5.1

     Then the UDP destination port and the TTL or Hop Limit of the inner IP
     packet MUST be validated to determine whether the received packet can be
     processed by BFD.

I was expecting pointers for those validation mechanism special to BFD. Can we
be more clear on this?