John Scudder's No Objection on draft-ietf-6man-grand-05: (with COMMENT)

John Scudder via Datatracker <noreply@ietf.org> Thu, 01 July 2021 01:32 UTC

Return-Path: <noreply@ietf.org>
X-Original-To: ipv6@ietf.org
Delivered-To: ipv6@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id E15253A101B; Wed, 30 Jun 2021 18:32:39 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: John Scudder via Datatracker <noreply@ietf.org>
To: The IESG <iesg@ietf.org>
Cc: draft-ietf-6man-grand@ietf.org, 6man-chairs@ietf.org, ipv6@ietf.org, Bob Hinden <bob.hinden@gmail.com>, bob.hinden@gmail.com
Subject: John Scudder's No Objection on draft-ietf-6man-grand-05: (with COMMENT)
X-Test-IDTracker: no
X-IETF-IDTracker: 7.33.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: John Scudder <jgs@juniper.net>
Message-ID: <162510315925.6473.16343810620669363979@ietfa.amsl.com>
Date: Wed, 30 Jun 2021 18:32:39 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/PGoSFF0gWg0ftw1MC5CIyfFkZe4>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.29
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 01 Jul 2021 01:32:45 -0000

John Scudder has entered the following ballot position for
draft-ietf-6man-grand-05: 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/iesg/statement/discuss-criteria.html
for more information about DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-6man-grand/



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

Thanks for a clear, readable, well-organized, and well-motivated document. I
have just a few questions and comments below.

1. Section 5.2

              The
   only potential impact would be for packets arriving to the router
   after the unsolicited NA from the host but before the rightful owner
   responded with the solicited NA.  Those packets would be sent to the
   host with the optimistic address instead of its rightful owner.
   However most likely those packets would have been dropped anyway:
   creating the INCOMPLETE entry is usually triggered by traffic, so the
   router probably has some packets in the buffer already, dropping
   subsequent packets received before the address resolution is
   completed.

Wouldn’t the buffered packets (received before the unsolicited NA) be
misdelivered to the optimistic host? The quoted paragraph restricts itself to
packets arriving after the unsolicited NA.

2. Section 5.3.1

Couldn’t step 4 (host detects duplication) complete sometime after step 7
(router sends NS to host)? (This might also apply to 5.3.2.) If that's possible
the analysis would be a little less rosy, right?

3. Section 5.3.1

        However the same
   behaviour would be observed if changes proposed in this document are
   implemented

Do you mean “are *not* implemented”?

4. Section 8.4

Please add SLLAO to terminology section or expand on first use.