Re: [manet] DLEP required metrics

Henning Rogge <> Fri, 04 May 2018 04:28 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id E5B2712702E for <>; Thu, 3 May 2018 21:28:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Status: No, score=-2 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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-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 ffzc46P4KVji for <>; Thu, 3 May 2018 21:28:05 -0700 (PDT)
Received: from ( [IPv6:2607:f8b0:400d:c0d::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 479A7126C0F for <>; Thu, 3 May 2018 21:28:05 -0700 (PDT)
Received: by with SMTP id q6-v6so25843430qtn.3 for <>; Thu, 03 May 2018 21:28:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=s1OUIE5NYerQHb8xMVu1cV1cYT4a8eQR0Spq/Y71gX4=; b=oEWoaFYOh/km8RgYlQ9arp1w7AYhgv6EaPLULbuNJzo/YPLLEKw1W762OaFuw1Jdq4 bbvQmY3OZz7PT3ENIa0j1tEpk6qV9VmRoiDT8WNxDYq48ONb+apniwIL70WzE4aF8YF5 J6J8g5Vr/Q0e3AOWHaqg2VKkffuUAJ9QvGOCoH0zh1dVXItNY9j0jst+IOfiFpkE/PoM FxHnP6XbrRByr2RyKWpnqptCP1mYUjkSXN23jyG1EBpsMSdH2I3wGM9uNHiRuX2qL0pH AjgQ0SCsN8bSzfVULvvupM74oNf2RaniVSh0emoGMqC2fTehUCqsZ+VmRqocOKYO+gXq NZqw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=s1OUIE5NYerQHb8xMVu1cV1cYT4a8eQR0Spq/Y71gX4=; b=GqX6WO+ZHLKvPHlzt6+NhOph5oNueCEusaaUjProLPk/tbn4RF/3nVtpgZwv0zB3MH +OPlYL9vLF4Treq+e1U90CZoWSgShAaw2fujHHCbYI6NaxfJe3GQepgEcpjlUVH8DUz3 P+JCz9dItxrpPZH1gvXmsZ8ay34Pvd2gwm0pHCPypQTc2vfaOxq0NkMAZQTvD70fY/f9 z8z4inxyA4faUGS6zglUF23ideFK06/+vLYHgpxiUjPEjRGlfEcb3U6cd5G504rBogax 7P3cCnFCXHsISfu9Ta7FAfId3p32wsfRKyjDU+9iLjTdEk7xWB6TIn9TJuWhnwaPoKZP rnog==
X-Gm-Message-State: ALQs6tD/saOmWrotoJRqWYHaNj2OJ3BJd4vnNse7qf+MEfEuPaeonUmV F0BccLA3vRQlOND8RN/JtEVnLDFnJa/L+HvbT2o=
X-Google-Smtp-Source: AB8JxZocF8QK47bX70LdpJwwQh8BQVMKTul7JoBNgz9MtSok/yU9XxbB2tId8iS2Kr6fMmhYiUmAdwos/myuGpcdXds=
X-Received: by 2002:a0c:bc90:: with SMTP id l16-v6mr21487273qvg.178.1525408083957; Thu, 03 May 2018 21:28:03 -0700 (PDT)
MIME-Version: 1.0
References: <>
In-Reply-To: <>
From: Henning Rogge <>
Date: Fri, 04 May 2018 04:27:38 +0000
Message-ID: <>
To: "Wiggins, David - 0665 - MITLL" <>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <>
Subject: Re: [manet] DLEP required metrics
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Mobile Ad-hoc Networks <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Fri, 04 May 2018 04:28:07 -0000

On Thu, May 3, 2018 at 11:34 PM Wiggins, David - 0665 - MITLL <> wrote:

> In RFC 8175, the following metrics are required in a Session
Initialization Response:

> Maximum Data Rate (Receive)
> Maximum Data Rate (Transmit)
> Current Data Rate (Receive)
> Current Data Rate (Transmit)

I think these four should be no trouble... if you don't know the exact
"current" bitrate, just report a fixed one... if you only support one
bitrate at all, just report them both as maximum and current.

> Latency

This one is more tricky... just give it a guess... most modern "civil"
technologies could easily report "1 millisecond"... only low bandwidth
radios or satcom links should report something higher (if you don't know
the "correct" value).

> If a modem doesn’t have a value for one or more of these metrics, what
value should it use?  Ideally it would just omit the metric, but with the
current RFC, that isn’t an option.   Note that these same metrics are
optional in Destination Up and Update.

They are optional in Dest Up/Down because you are allowed to report a
default value for all neighbors in the Session Initialization and it will
just be valid for all neighbors.

Henning Rogge