[manet] [Errata Held for Document Update] RFC6130 (4866)

RFC Errata System <rfc-editor@rfc-editor.org> Wed, 25 January 2017 16:34 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: manet@ietfa.amsl.com
Delivered-To: manet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 730A2129A32; Wed, 25 Jan 2017 08:34:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.401
X-Spam-Level:
X-Spam-Status: No, score=-7.401 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-3.199, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 5zTMD-U4M4jA; Wed, 25 Jan 2017 08:34:21 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7FF43129A2C; Wed, 25 Jan 2017 08:34:21 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 64743B81C21; Wed, 25 Jan 2017 08:34:21 -0800 (PST)
To: nmalykh@gmail.com, T.Clausen@computer.org, chris.dearlove@baesystems.com, jdean@itd.nrl.navy.mil
X-PHP-Originating-Script: 30:errata_mail_lib.php
From: RFC Errata System <rfc-editor@rfc-editor.org>
Message-Id: <20170125163421.64743B81C21@rfc-editor.org>
Date: Wed, 25 Jan 2017 08:34:21 -0800 (PST)
Archived-At: <https://mailarchive.ietf.org/arch/msg/manet/zwoxwDvglT08Y_NiVIdTXh2t5is>
Cc: manet@ietf.org, iesg@ietf.org, rfc-editor@rfc-editor.org
Subject: [manet] [Errata Held for Document Update] RFC6130 (4866)
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Mobile Ad-hoc Networks <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/manet/>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 25 Jan 2017 16:34:23 -0000

The following errata report has been held for document update 
for RFC6130, "Mobile Ad Hoc Network (MANET) Neighborhood Discovery Protocol (NHDP)". 

--------------------------------------
You may review the report below and at:
http://www.rfc-editor.org/errata_search.php?rfc=6130&eid=4866

--------------------------------------
Status: Held for Document Update
Type: Editorial

Reported by: Nikolai Malykh <nmalykh@gmail.com>
Date Reported: 2016-11-15
Held by: Alvaro Retana (IESG)

Section: 4.3.2

Original Text
-------------
   o  For each MANET interface, within every time interval equal to the
      corresponding REFRESH_INTERVAL, sent HELLO messages MUST
      collectively include all of the relevant information in the
      corresponding Link Set and the Neighbor Information Base.  Note
      that when determining whether to include information in a HELLO
      message, the sender MUST consider all times up to the latest time
      when it may send its next HELLO message on this MANET interface.

   o  For each MANET interface, within every time interval equal to the
      corresponding REFRESH_INTERVAL, sent HELLO messages MUST
      collectively include all of the relevant information in the
      corresponding Link Set and the Neighbor Information Base.


Corrected Text
--------------
   o  For each MANET interface, within every time interval equal to the
      corresponding REFRESH_INTERVAL, sent HELLO messages MUST
      collectively include all of the relevant information in the
      corresponding Link Set and the Neighbor Information Base.  Note
      that when determining whether to include information in a HELLO
      message, the sender MUST consider all times up to the latest time
      when it may send its next HELLO message on this MANET interface.



Notes
-----
The second statement is already contained in the first one.

=====
>From Christopher Dearlove (author):

it is the other paragraph that should be deleted. Because the paragraph following the two quoted paragraphs, which I copy here:

   o  When determining whether to include a given piece of neighbor
      information in a HELLO message, it is not sufficient to consider
      whether that information has been sent in the interval of length
      REFRESH_INTERVAL up to the current time.  Instead, the router MUST
      consider the interval of length REFRESH_INTERVAL that will end at
      the latest possible time at which the next HELLO message will be
      sent on this MANET interface.  (Normally, this will be
      HELLO_INTERVAL past the current time, but MAY be earlier if this
      router elects to divide its neighbor information among more than
      one HELLO message in order to reduce the size of its HELLO
      messages.)  All neighbor information MUST be sent in this
      interval, i.e., the router MUST ensure that this HELLO message
      includes all neighbor information that has not already been
      included in any HELLO messages sent since the start of this
      interval (normally, the current time - (REFRESH_INTERVAL -
      HELLO_INTERVAL)).

contains the additional information in the longer paragraph, expanded to explain what it means.

Thus the resolution is to delete the first paragraph:

OLD:

   o  For each MANET interface, within every time interval equal to the
      corresponding REFRESH_INTERVAL, sent HELLO messages MUST
      collectively include all of the relevant information in the
      corresponding Link Set and the Neighbor Information Base.  Note
      that when determining whether to include information in a HELLO
      message, the sender MUST consider all times up to the latest time
      when it may send its next HELLO message on this MANET interface.

NEW:


--------------------------------------
RFC6130 (draft-ietf-manet-nhdp-15)
--------------------------------------
Title               : Mobile Ad Hoc Network (MANET) Neighborhood Discovery Protocol (NHDP)
Publication Date    : April 2011
Author(s)           : T. Clausen, C. Dearlove, J. Dean
Category            : PROPOSED STANDARD
Source              : Mobile Ad-hoc Networks
Area                : Routing
Stream              : IETF
Verifying Party     : IESG