From nobody Mon Jun 21 07:10:05 2021 Return-Path: X-Original-To: ipv6@ietfa.amsl.com Delivered-To: ipv6@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CFCF63A10CE; Mon, 21 Jun 2021 07:09:59 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.198 X-Spam-Level: X-Spam-Status: No, score=-0.198 tagged_above=-999 required=5 tests=[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] 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 3Tna0tgTFT6q; Mon, 21 Jun 2021 07:09:58 -0700 (PDT) Received: from mail-io1-xd36.google.com (mail-io1-xd36.google.com [IPv6:2607:f8b0:4864:20::d36]) (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 BC4A93A10CD; Mon, 21 Jun 2021 07:09:57 -0700 (PDT) Received: by mail-io1-xd36.google.com with SMTP id g22so2177139iom.1; Mon, 21 Jun 2021 07:09:57 -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=qyoiqjQ52UI7XahIV3FyKUwhyYqHF5SJ9VYx08xErU8=; b=t5OilJXMg4WVMcBB6yLrbqMjwTmRivlKjLWz8CaWyzWkDPG+S7vuEKL/nPzLxV/Rgf or3mahRKPbFW9fuzjrCYQjFXUL6ZH/CqkwL8/ZUKsvkpJ2bovV0fYHcpTKpPqzY4dn8R PTToOpUnadyhHK11F3xTn0DwoZvBLtO7stre/RICMxS6OedlIP45z6P5UOr4a3SqZJFq qcYAsUdlbqxtr1DXXBRCPFRAou6SsXi5XazdvhpdWqfjISolQxx9Q0CFEvWFA8wO0rkn V5FIR3q4jhaZ9CWU8gSPEHBPBVuUvwwGTTMXxCg83oqj4bebKqaXT1ZRPlUGl2bC6Xhj LIwA== 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=qyoiqjQ52UI7XahIV3FyKUwhyYqHF5SJ9VYx08xErU8=; b=Y/jagSKk9ib+tKQ7yWjHU3MED63eFTVrrOACCgyGA88JzDnpsN9VZ0JcbyGh5JcS4o 9nqK/mUJXyBS7KnxtPUXmtX3y3WP8drsmF2PWjrL5PhPePNPbUxQag4wQGkUkzR+srKE DSq2najJ7knGpZ2jKw2PHpv3kFZmpzG0o+Jw0VwKc07EznNA0dNh76oCWql+cr6Clern wM+YF+k6zZ8ziqwpZ9S+aMS7RO35y1/er0pkWrd66qYsh/3pKL4loVNFa0K5vTy87wxq L7Uw1D1Lo+hrYzpo9k1gNSfEckPXl4txU+k2bjMQisFiRgDo/0Y/tvbr/ok+Thllr1Y1 7Keg== X-Gm-Message-State: AOAM531q8Vu2zt34pBvr9msNSytgcWJy5sJTlbk+ov/H08VyIQzWEH5q QTJt27amxYxGw6yCZpN+mBx3eMEz4UlaE2G2fsQ= X-Google-Smtp-Source: ABdhPJzQC5b/H5zZlOisxzxAmxWnZ9SHxFYmCHpvIlqcHDFfO7pRYVfXLHDZLd4WhZuCmbjM0XVVAKtSYLqbhIr5wlc= X-Received: by 2002:a05:6638:12c1:: with SMTP id v1mr17287894jas.97.1624284595305; Mon, 21 Jun 2021 07:09:55 -0700 (PDT) MIME-Version: 1.0 References: <162395278040.16283.13895377798525598080@ietfa.amsl.com> In-Reply-To: From: Dan Romascanu Date: Mon, 21 Jun 2021 17:09:43 +0300 Message-ID: Subject: Re: [Last-Call] Genart last call review of draft-ietf-6man-grand-04 To: Jen Linkova Cc: gen-art , Last Call , draft-ietf-6man-grand.all@ietf.org, 6man Content-Type: multipart/alternative; boundary="00000000000051421105c5473a71" Archived-At: X-BeenThere: ipv6@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "IPv6 Maintenance Working Group \(6man\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Jun 2021 14:10:00 -0000 --00000000000051421105c5473a71 Content-Type: text/plain; charset="UTF-8" Looks good. Thanks for addressing this as well. Regards, Dan On Mon, Jun 21, 2021 at 3:06 PM Jen Linkova wrote: > On Mon, Jun 21, 2021 at 8:16 PM Dan Romascanu wrote: > > Yes, a paragraph in the Introduction explaining the structure of the > document and especially the place(s) where normative text can be found > would be useful. If you add these you may consider deleting other such > references spread in the text. > > I'll add the following to the very end of the Introduction: > > "This document updates the Neighbor Discovery protocol to avoid packet > loss in the scenario described above. Section 4 discusses the > changes and analyses the potential impact, while normative changes to > [RFC4861] are specified in Section 6. > > -- > SY, Jen Linkova aka Furry > --00000000000051421105c5473a71 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Looks good. Thanks for addressing this as well.=C2=A0
=
Regards,

Dan


On= Mon, Jun 21, 2021 at 3:06 PM Jen Linkova <furry13@gmail.com> wrote:
On Mon, Jun 21, 2021 at 8:16 PM Dan Romascanu <= dromasca@gmail.com<= /a>> wrote:
> Yes, a paragraph in the Introduction explaining the structure of the d= ocument and especially the place(s) where normative text can be found would= be useful. If you add these you may consider deleting other such reference= s spread in the text.

I'll add the following to the very end of the Introduction:

"This document updates the Neighbor Discovery protocol to avoid packet=
loss in the scenario described above.=C2=A0 Section 4 discusses the
changes and analyses the potential impact, while normative changes to
[RFC4861] are specified in Section 6.

--
SY, Jen Linkova aka Furry
--00000000000051421105c5473a71--