[manet] Mirja Kühlewind's No Objection on draft-ietf-manet-dlep-multi-hop-extension-06: (with COMMENT)

Mirja Kühlewind via Datatracker <noreply@ietf.org> Mon, 29 April 2019 13:38 UTC

Return-Path: <noreply@ietf.org>
X-Original-To: manet@ietf.org
Delivered-To: manet@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 1057A1202FF; Mon, 29 Apr 2019 06:38:43 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: Mirja Kühlewind via Datatracker <noreply@ietf.org>
To: The IESG <iesg@ietf.org>
Cc: draft-ietf-manet-dlep-multi-hop-extension@ietf.org, Stan Ratliff <sratliff@idirect.net>, aretana.ietf@gmail.com, manet-chairs@ietf.org, sratliff@idirect.net, manet@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.95.1
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Mirja Kühlewind <ietf@kuehlewind.net>
Message-ID: <155654512305.15899.6671265788242474328.idtracker@ietfa.amsl.com>
Date: Mon, 29 Apr 2019 06:38:43 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/manet/X8hRIGvaTYs3sG61yx5sQbapxgM>
Subject: [manet] Mirja Kühlewind's No Objection on draft-ietf-manet-dlep-multi-hop-extension-06: (with COMMENT)
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.29
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: Mon, 29 Apr 2019 13:38:43 -0000

Mirja Kühlewind has entered the following ballot position for
draft-ietf-manet-dlep-multi-hop-extension-06: 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 IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-manet-dlep-multi-hop-extension/



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

 1) Maybe this is a bit of a blunt question because I might not know enough
 about DLEP but how does a modem know the number of hops? Is there any need to
 say something more about how to gather this information in the document?

 2) Should the security consideration section maybe also say something about
 the frequency of re-configurations? Maybe that should be limited, also in
 order to not generate a large amount of signalling messages that could congest
 the link. Maybe you want to at least limit the rate of messages sent such that
 multiple re-configuration could be covered by one message in case there is a
 high rate of re-configurations. Or is there already such a limit in DLEP? If
 yes, it would be good to state that explicitly in this document as well.

 nits:
 - There seems to be a text fragment (“example using .”) in the intro text:
 “This document refers to
   forwarding by intermediate modems as 'multi-hop forwarding'.  example
   using . DLEP Destination messages can be used to …”
 - Sec 3.1: s/to indicate the number of modem/to indicate the number of modems/
 -> plural: modemS