Re: [core] Martin Duke's Discuss on draft-ietf-core-new-block-11: (with DISCUSS and COMMENT)

Martin Duke <martin.h.duke@gmail.com> Tue, 04 May 2021 15:28 UTC

Return-Path: <martin.h.duke@gmail.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 8B9E23A0B56; Tue, 4 May 2021 08:28:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.096
X-Spam-Level:
X-Spam-Status: No, score=-2.096 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 ed4l0-VrvZ3r; Tue, 4 May 2021 08:28:35 -0700 (PDT)
Received: from mail-il1-x131.google.com (mail-il1-x131.google.com [IPv6:2607:f8b0:4864:20::131]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A8CF23A0B9E; Tue, 4 May 2021 08:28:34 -0700 (PDT)
Received: by mail-il1-x131.google.com with SMTP id c3so6687318ils.5; Tue, 04 May 2021 08:28:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=l4MTkMHmLcoTNvVaNI4Jzb8ZGKws9idIJ4AL2IlGYHw=; b=V7izwVoqorqOYU1FwG2sss0vvqMW5vuq0Y10Tc79KJcq4Us4lBLWisoXT3MUuo5nxV LmmdjT6hR0knu0GoCUq+IoSOUhx5j78QbRcHirvp56LimLcVIaWb9gt5c5vs8gXW9IYu UP23hHPh7n7ecHqdJWe0o16nZSYz/6OJS4txh/rBvwPWfWC3+5xM9PzleWqU7BrHQqFD cec2L1VzhdVaE5njEgjJvjlrtdJ6ajM+5BvkMVicehDlyKecb1+rxDdqhpRFxntGBxWX Kzxk5Nc6mYE8dTzMwHjLLp1Uw2Q0BBHII9iaDg1WLJ3s/+JuDiRPkwHJns6GxZU9xaes +obQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=l4MTkMHmLcoTNvVaNI4Jzb8ZGKws9idIJ4AL2IlGYHw=; b=tkmZtxju+sZOFK3Ydk+RYBTVxrNxabpyfnVpLyL54R9Sl+ChwBHLNnskm0CCUeeHo8 U8lmbQQwaS72JDs0GcY2FLlG9+kyd6Ovgca69oAvxDhYeMYwUDTMGDsrn6Cx/RD+Shsq bLPQeTRXl2xZPOE19dtBc7TO9i/ie3Dv1mfEHuLcl8YtRNzrtQCpZvmoGrMcSpz5gBNy VHgRBDAGeY2LqN5xq6cgyNlziOi2ULwg0c5AJAMlQKxsgEsnZgSzvjMs86daEvWLsQYN t2Ra63xcorjOFpECvkIQnF3eGnM+dx89Z6Qxxz1y06PhoWvZA0U1JOOor+xLw5xqL0mP WE/A==
X-Gm-Message-State: AOAM531JT4h5WcRazB4/bkpwMxbz9DRiUl+jMPkmHJA3++yf8bRYpiNd ATm5iJKIRTFort5TpdABX+pjOp5lXhpBKnSGvUs=
X-Google-Smtp-Source: ABdhPJzdHMezXnZSWa7+Ex+pRKS0hFt0F37KF2gUDzMuKXs8z7eo1uaeCc+C6w87uu9or19WyIVVTvUWac36jWscS8g=
X-Received: by 2002:a05:6e02:2162:: with SMTP id s2mr21158617ilv.237.1620142112561; Tue, 04 May 2021 08:28:32 -0700 (PDT)
MIME-Version: 1.0
References: <161973861706.19975.3092798532288165336@ietfa.amsl.com> <9640_1619783334_608BEEA5_9640_342_16_787AE7BB302AE849A7480A190F8B9330353751A9@OPEXCAUBMA2.corporate.adroot.infra.ftgroup> <CAM4esxS7E54VF8PQ=MAPeLJbRi_NY1jZoK15ZWyJhWyE9VVn+Q@mail.gmail.com> <21895_1620118865_60910D51_21895_367_1_787AE7BB302AE849A7480A190F8B9330353764A2@OPEXCAUBMA2.corporate.adroot.infra.ftgroup>
In-Reply-To: <21895_1620118865_60910D51_21895_367_1_787AE7BB302AE849A7480A190F8B9330353764A2@OPEXCAUBMA2.corporate.adroot.infra.ftgroup>
From: Martin Duke <martin.h.duke@gmail.com>
Date: Tue, 4 May 2021 08:28:23 -0700
Message-ID: <CAM4esxS=q-NRUp4ph8oPjwWhY1uznDqH1p5YQ1WfWTy+TAVERg@mail.gmail.com>
To: mohamed.boucadair@orange.com
Cc: The IESG <iesg@ietf.org>, "draft-ietf-core-new-block@ietf.org" <draft-ietf-core-new-block@ietf.org>, "core-chairs@ietf.org" <core-chairs@ietf.org>, "core@ietf.org" <core@ietf.org>, "marco.tiloca@ri.se" <marco.tiloca@ri.se>
Content-Type: multipart/alternative; boundary="0000000000001adef205c182bb09"
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/0YTr1SdjVTHnz6Q70DH8IuOKKro>
Subject: Re: [core] Martin Duke's Discuss on draft-ietf-core-new-block-11: (with DISCUSS and COMMENT)
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: Tue, 04 May 2021 15:28:41 -0000

OK, we've reached understanding on the NON_PROBING_WAIT/NON_PARTIAL_TIMEOUT
issue. Thank you for the edit.

I also now understand that essentially every connection will have a Q-block
exchange using CON. As this is an integral part of the protocol, I don't
believe it's sufficient for Sec 7.1 to declare congestion control
parameters out of scope, unless there's a normative reference to some other
draft that explains how to do it.

Thanks
Martin

On Tue, May 4, 2021 at 2:01 AM <mohamed.boucadair@orange.com> wrote:

> Hi Martin,
>
>
>
> Please see inline.
>
>
>
> Cheers,
>
> Med
>
>
>
> *De :* Martin Duke [mailto:martin.h.duke@gmail.com]
> *Envoyé :* lundi 3 mai 2021 20:57
> *À :* BOUCADAIR Mohamed TGI/OLN <mohamed.boucadair@orange.com>
> *Cc :* The IESG <iesg@ietf.org>rg>; draft-ietf-core-new-block@ietf.org;
> core-chairs@ietf.org; core@ietf.org; marco.tiloca@ri.se
> *Objet :* Re: Martin Duke's Discuss on draft-ietf-core-new-block-11:
> (with DISCUSS and COMMENT)
>
>
>
>
>
>
>
> On Fri, Apr 30, 2021 at 4:48 AM <mohamed.boucadair@orange.com> wrote:
>
> >
> > I can't reconcile (4.1) with the last sentence in (7.2).
>
> [Med] Why? 4.1 can be done with default CoAP setting. The purpose of this
> CON request is to determine support of the functionality. We made this
> change:
>
> OLD:
>    Congestion control for CON requests and responses is specified in
>    Section 4.7 of [RFC7252].  In order to benefit from faster
>    transmission rates, NSTART will need to be increased from 1.
>    However, the other CON congestion control parameters will need to be
>    tuned to cover this change.  This tuning is not specified in this
>    document given that the applicability scope of the current
>    specification assumes that all requests and responses using Q-Block1
>    and Q-Block2 will be Non-confirmable (Section 3.2).
>
> NEW:
>    Congestion control for CON requests and responses is specified in
>    Section 4.7 of [RFC7252].  In order to benefit from faster
>    transmission rates, NSTART will need to be increased from 1.
>    However, the other CON congestion control parameters will need to be
>    tuned to cover this change.  This tuning is not specified in this
>    document given that the applicability scope of the current
>    specification assumes that all requests and responses using Q-Block1
>    and Q-Block2 will be Non-confirmable (Section 3.2) apart from the
>                                                       ^^^^^^^^^^^^^^
>    initial Q-Block functionality negotiation.
>    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>
>
>
> Does the functionality negotiation in (4.1) involve something other than
> sending Q-Block options?
>
> *[Med] No. All what is needed is to send the options in a CON message as
> per:  *
>
>
>
>    To indicate support for Q-Block2 responses, the CoAP client MUST
>
>    include the Q-Block2 Option in a GET or similar request (FETCH, for
>
>    example), the Q-Block2 Option in a PUT or similar request (POST, for
>
>    example), or the Q-Block1 Option in a PUT or similar request so that
>
>    the server knows that the client supports this Q-Block functionality
>
>    should it need to send back a body that spans multiple payloads.
>
>    Otherwise, the server would use the Block2 Option (if supported) to
>
>    send back a message body that is too large to fit into a single IP
>
>    packet [RFC7959].
>
>
>
> If so, then (4.1) ought to clarify that it's what you mean. If it's just a
> GET or whatever, then the text here is fine, but there needs to be more on
> congestion control for confirmable messages.
>
>
>
>
>  Moreover, if
> > my reading of (4.1) is correct, it's not sufficient to declare
> > congestion control guidance out of scope when it's a mandated part of
> > the protocol.
> >
>
> >
> > - (7.2) If NON_PROBING_WAIT and NON_PARTIAL_TIMEOUT both "have the
> > same value as computed for EXCHANGE_LIFETIME", why are they different
> > variables?
>
> [Med] Because they refer to distinct aspects that may be tweaked
> separately: the timeout induced by PROBING_RATE and the one to observe for
> expired partial bodies.
>
>  Or is that they SHOULD have the same value but might not?
> > A normative word would be helpful here.
>
> [Med] Not sure a change is needed here given the definition of the two
> parameters.
>
>
>
> But they can't be tweaked separately! The spec states that they are both
> computed as EXCHANGE_LIFETIME. It does not allow for them to be set
> separately.
>
> *[Med] Ah, I see what confuses you. We made this change:*
>
>
>
> *OLD:*
>
>    NON_PROBING_WAIT is used to limit the potential wait needed
>
>    calculated when using PROBING_RATE.  NON_PROBING_WAIT has the same
>
>    value as computed for EXCHANGE_LIFETIME (Section 4.8.2 of [RFC7252]).
>
>
>
>    NON_PARTIAL_TIMEOUT is used for expiring partially received bodies.
>
>    NON_PARTIAL_TIMEOUT has the same value as computed for
>
>    EXCHANGE_LIFETIME (Section 4.8.2 of [RFC7252]).
>
>
>
> *NEW:*
>
>    NON_PROBING_WAIT is used to limit the potential wait needed
>
>    calculated when using PROBING_RATE.  By default, NON_PROBING_WAIT has
>
>    the same value as EXCHANGE_LIFETIME (Section 4.8.2 of [RFC7252]).
>
>
>
>    NON_PARTIAL_TIMEOUT is used for expiring partially received bodies.
>
>    By default, NON_PARTIAL_TIMEOUT has the same value as
>
>    EXCHANGE_LIFETIME (Section 4.8.2 of [RFC7252]).
>
>
>
> _________________________________________________________________________________________________________________________
>
> Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
> pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
> a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
> Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.
>
> This message and its attachments may contain confidential or privileged information that may be protected by law;
> they should not be distributed, used or copied without authorisation.
> If you have received this email in error, please notify the sender and delete this message and its attachments.
> As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
> Thank you.
>
>