From nobody Wed Dec 23 02:40:04 2020
Return-Path: <christian@amsuess.com>
X-Original-To: core@ietfa.amsl.com
Delivered-To: core@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1])
 by ietfa.amsl.com (Postfix) with ESMTP id 0F0733A0E94;
 Wed, 23 Dec 2020 02:39:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5
 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001,
 URIBL_BLOCKED=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 dYhsVkWTHPiq; Wed, 23 Dec 2020 02:39:57 -0800 (PST)
Received: from prometheus.amsuess.com (alt.prometheus.amsuess.com
 [IPv6:2a01:4f8:190:3064::3])
 (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits))
 (No client certificate requested)
 by ietfa.amsl.com (Postfix) with ESMTPS id EDD1C3A0E8F;
 Wed, 23 Dec 2020 02:39:54 -0800 (PST)
Received: from poseidon-mailhub.amsuess.com (unknown
 [IPv6:2a02:b18:c13b:8010:a800:ff:fede:b1bd])
 by prometheus.amsuess.com (Postfix) with ESMTPS id 8289E407C1;
 Wed, 23 Dec 2020 11:39:49 +0100 (CET)
Received: from poseidon-mailbox.amsuess.com (hermes.amsuess.com [10.13.13.254])
 by poseidon-mailhub.amsuess.com (Postfix) with ESMTP id 823F7AB;
 Wed, 23 Dec 2020 11:39:27 +0100 (CET)
Received: from hephaistos.amsuess.com (unknown
 [IPv6:2a02:b18:c13b:8010:bd73:2e62:80f9:8152])
 by poseidon-mailbox.amsuess.com (Postfix) with ESMTPSA id DFD9E63;
 Wed, 23 Dec 2020 11:39:26 +0100 (CET)
Received: (nullmailer pid 2826684 invoked by uid 1000);
 Wed, 23 Dec 2020 10:39:25 -0000
Date: Wed, 23 Dec 2020 11:39:25 +0100
From: Christian =?iso-8859-1?Q?Ams=FCss?= <christian@amsuess.com>
To: mohamed.boucadair@orange.com
Cc: "draft-ietf-core-new-block@ietf.org" <draft-ietf-core-new-block@ietf.org>, 
 "core@ietf.org WG (core@ietf.org)" <core@ietf.org>,
 "dots@ietf.org" <dots@ietf.org>
Message-ID: <X+MeXXJfyXCuqyA0@hephaistos.amsuess.com>
References: <31613_1608714849_5FE30A61_31613_100_2_787AE7BB302AE849A7480A190F8B9330315A17B3@OPEXCAUBMA2.corporate.adroot.infra.ftgroup>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256;
 protocol="application/pgp-signature"; boundary="xZSAZ4uOpIvUYSpF"
Content-Disposition: inline
In-Reply-To: <31613_1608714849_5FE30A61_31613_100_2_787AE7BB302AE849A7480A190F8B9330315A17B3@OPEXCAUBMA2.corporate.adroot.infra.ftgroup>
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/2dURQ8IRlaoM4otmNgGvyfhCGP4>
Subject: Re: [core] WG Last Call on draft-ietf-core-new-block (Congestion
 Control)
X-BeenThere: core@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list"
 <core.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/core>,
 <mailto:core-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/core/>
List-Post: <mailto:core@ietf.org>
List-Help: <mailto:core-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/core>,
 <mailto:core-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 23 Dec 2020 10:39:59 -0000


--xZSAZ4uOpIvUYSpF
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Hello,

On Wed, Dec 23, 2020 at 09:14:09AM +0000, mohamed.boucadair@orange.com wrot=
e:
> You are completely right that the default probing-rate is to be
> increased for the DOTS case. FYI, this is why we went with the
> following in RFC8782:
>
> We avoided to include a pointer to these details as these are
> application-specific and that, even if the draft is motivated by the
> DOTS use case, other applications can make use of the new block
> functionality.=20

At least a one-line reference into there would be helpful when reading
the congestion control section. It can be phrased as an example ("For
the particular use case of DOTS, these parameters are negotiated; even
when not negotiated, that application uses altered defaults as in
[ref-into-dots]") to avoid the impression of general applicability, but
some example *should* be given, for without changed parameters the
Q-Block mechanism is useless (3 hour wait if all 10 initial messages are
lost).

> For NSTART, we already have the following:=20
>=20
>   "NSTART will also need to be increased from the default
>    (1) to get faster transmission rates."

It would enhance readability if that were mentioned in the congestion
control section.

It may help to draw the parallel to the MAX_PAYLOADS of the
non-confirmable case, or to talk more about the hybrid transmission
(CON only after some blocks; does that have a name? see also comment
around "seems to imply that the full exchange").

Does DOTS have an altered default here? Without having *anything* about
non-1 NSTART, the all-CON case may not even be worth having in an
example, as there's nothing even referenced where it could make sense.

Best regards
Christian

--=20
To use raw power is to make yourself infinitely vulnerable to greater power=
s.
  -- Bene Gesserit axiom

--xZSAZ4uOpIvUYSpF
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEECM1tElX6OodcH7CWOY0REtOkveEFAl/jHlkACgkQOY0REtOk
veE+7A//aM8shJ7iAezFVfp0L/pW1JVez4Q5BGOR/PXNWo7R11kyySJLvCa5a2Dy
G5tod1oEmda+6YevdY8eCH13IBu75vtrXIKohMWUVBV2AbKZNDv7pGSUTpCMMZxl
HkCvDDpdPrhcVStvBruPnC9Zu+2J+H9Q+u0WwpIeOWNWZFsMybw97f08PQF9xxDb
vyIwMtrsWSbcD916Egz0bADekkVbIJ1OCfR3OOT9xvpq1kIOMX/FsylnJzCW32Po
iW4bffFUeYeHXRpBQNFUHwntkzWtUGG4GiafvausK36UX7n+KV1kBYdF1i8N/61z
JlRURtD+5GMMHmGqoNRJUgbdLO6hZt8JU9d2Z4xsVAwwCUEIczz5W90OpJXQ9/wZ
5pCNQtmkMeFWPSXkVYY+DK1FPgrkRLDM1bhlY/M5cKRR5Swgw4mwgrAcLNXfG3MG
bghXEXToSPHr644h0orJlgs5O5CnE3aTXeyw+x7/3rAaR8gh1RbmVi45lPpFfcQM
kMttcwiD6ZmHXhVWzH+aJ7UFfFDAYr3E7WJ7oPJ28U5tVOpQ25iOOqeTmrT/Loru
i59quElttXJFrUVBFtr7r7eSjbxA58kh5W1A2qwwAoHVk4Iw8cpEVp0mK5fM7rST
dbFfJIt8P491yldp3OtpUzRub39tqih3HmGdf+tEE8g1CvCDlIc=
=0zVB
-----END PGP SIGNATURE-----

--xZSAZ4uOpIvUYSpF--

