Re: [manet] Alissa Cooper's Discuss on draft-ietf-manet-dlep-pause-extension-06: (with DISCUSS and COMMENT)

Alvaro Retana <> Thu, 11 April 2019 13:49 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id D76FD120306; Thu, 11 Apr 2019 06:49:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.997
X-Spam-Status: No, score=-1.997 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id T3u-suw5nb_H; Thu, 11 Apr 2019 06:49:40 -0700 (PDT)
Received: from ( [IPv6:2607:f8b0:4864:20::331]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id C495B1202E2; Thu, 11 Apr 2019 06:49:40 -0700 (PDT)
Received: by with SMTP id e80so5270451ote.5; Thu, 11 Apr 2019 06:49:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=from:in-reply-to:references:mime-version:date:message-id:subject:to :cc; bh=WQfdkj5uF7o7gLCLAxAapP4dXbW+sLreGEvfy2frTQ4=; b=o4mzBKFHRrNaXQW/mvd0Mxlz7gfO3MhLlF+LRacwL+1c/3EGfhYbeAn+ulaISPZXj3 J3kZ34XPojdKII7VxPLFavTxDZh58mJdAso1Se1NVWVwr3+P/Sl0mIrR6sfVU9uLRIq4 IIbSMwDI2FHCkpU0gvRdLlYHdeeUxwBu0uuqrxSucQULlty8Sno7vXbMf5fkec4q0DWm qC+ajdwap+EJY+pjSfuzJdxAzUhcdhclndooECgkvURPJZfxWWVmNx/0cfDMLzyB6dBe CG/nvFgv277uJDDk0/HRBeiI9Bj62HYi4QCLYkrMM4Qn4hOiX6x9jscYcYF3f2pMTpsx DQPw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=x-gm-message-state:from:in-reply-to:references:mime-version:date :message-id:subject:to:cc; bh=WQfdkj5uF7o7gLCLAxAapP4dXbW+sLreGEvfy2frTQ4=; b=p7TuW2+TU2W1Fb1RSaYgWzt+ir+kb8ooYGW0C6u857lIKix8AMpfVW0ix8jlDru2eq 02OWymLFbUNpZYOaqfLE0i9faBLGu9L11GfoEhcU32IZCGAW+8NHzda2NVgZkQGH7HjB UEz6xrVyWOjIhSHj4NSgdeFyRog5J4sQrvHLy30M9JrO1O1SKOLKWv5FmWFqhnbsohX4 ip9cVQvgyCPwaIu6U+Cy3kfnKma5BvRnshEEm9OpoVZUUCQWV/ZEFyTssSZJuNPXBKxW PcgXixQNdHbs7qWZ5HtA4yYiGwE4+ZPtIb0xYk+8INpPpwFmEM+RgHV/Tw00deRVaWe+ GyxQ==
X-Gm-Message-State: APjAAAVT1JilC+YZvy4fNrPg5+8vDjj+Uh+NdteangJkAYQMw3zYYJZn V6jUoR4DxtYAg2AiRN2X2kPdqd+UHnb+JuqCj00=
X-Google-Smtp-Source: APXvYqxnUME7Oe3ge2QhGV9GlnNs3I2S6UsnzcxAJQmb6UyV2NFMJAVbqWLdxLB0/I8Cy9tC2p1g5clh7G47DA8RM9g=
X-Received: by 2002:a05:6830:1103:: with SMTP id w3mr33583513otq.28.1554990580012; Thu, 11 Apr 2019 06:49:40 -0700 (PDT)
Received: from 1058052472880 named unknown by with HTTPREST; Thu, 11 Apr 2019 06:49:39 -0700
From: Alvaro Retana <>
In-Reply-To: <>
References: <> <> <>
MIME-Version: 1.0
Date: Thu, 11 Apr 2019 06:49:39 -0700
Message-ID: <>
To: Alissa Cooper <>
Cc: Stan Ratliff <>,, IESG <>,,
Content-Type: multipart/alternative; boundary="000000000000269aa105864175cb"
Archived-At: <>
Subject: Re: [manet] Alissa Cooper's Discuss on draft-ietf-manet-dlep-pause-extension-06: (with DISCUSS and COMMENT)
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Mobile Ad-hoc Networks <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 11 Apr 2019 13:49:43 -0000

On April 11, 2019 at 9:06:50 AM, Alissa Cooper ( wrote:

Is there any scope limitation to the functionality that could potentially
be characterized as further "development of DLEP"? I ask because from a
quick read of the base specification, it doesn’t look like pause/resume was
contemplated, and as you note this was not explicitly called out in the
charter whereas credit windowing was. I’m wondering what the boundary is
around the functionality DLEP is expected to provide as a protocol.

In short, I believe the boundary is simply “whatever the users need”.

When we re-chartered (a couple of years ago), the WG thought that credit
windowing would be the focus (there was a document in progress, etc.), but
that has changed to include this extension, and others.  The community
working on DLEP is a very close-knit group with related (it not
significantly overlapping) users — the focus of the work then follows what
their users require.

At some point we should think about generalizing the charter.