Re: [Dots] [core] I-D Action: draft-ietf-core-new-block-05.txt

mohamed.boucadair@orange.com Tue, 19 January 2021 15:21 UTC

Return-Path: <mohamed.boucadair@orange.com>
X-Original-To: dots@ietfa.amsl.com
Delivered-To: dots@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 261243A159C; Tue, 19 Jan 2021 07:21:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.118
X-Spam-Level:
X-Spam-Status: No, score=-2.118 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, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=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=orange.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 mdI9BRFTLhim; Tue, 19 Jan 2021 07:21:05 -0800 (PST)
Received: from relais-inet.orange.com (relais-inet.orange.com [80.12.70.34]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 60E153A159E; Tue, 19 Jan 2021 07:21:05 -0800 (PST)
Received: from opfednr02.francetelecom.fr (unknown [xx.xx.xx.66]) by opfednr25.francetelecom.fr (ESMTP service) with ESMTP id 4DKsmw0rwCzCrKv; Tue, 19 Jan 2021 16:21:04 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=orange.com; s=ORANGE001; t=1611069664; bh=J+XLJtYvfQpZGTGjjEwmDePktNGMWhuwcFIqlgGYi5A=; h=From:To:Subject:Date:Message-ID:Content-Type: Content-Transfer-Encoding:MIME-Version; b=ervHUfef+/pF3mB4XbmnalB+bvYUzG+xBCG26WKzA+76QacjnLq9Kue+axlajXEsN 4G00C08eNuuB7EyVTshiCXa4c/XW8Egls6B0tTtSTSPPzA3siK6YBuLWo0mwU8f9/g lDxbLwxbVSmbQgkD/Atg87nG74EZdHaNco5VNbSkbi1VHWybjbfySmQ/LEZrUk+sZD rIcaQyj326D/urcoyQ/EHz3kbnW3dLC42QvuSEeVeA8MXs8QjqrerdZufaFBgFHVA+ oCUISwVaTThIb2Ixqh5hLtV1kwXruBw8eh/v1AXsnD3sqbF5pouiTgpwcTjq+GMwZd hj4WuYewzM0Hg==
Received: from Exchangemail-eme6.itn.ftgroup (unknown [xx.xx.13.98]) by opfednr02.francetelecom.fr (ESMTP service) with ESMTP id 4DKsmw04jjz8sZq; Tue, 19 Jan 2021 16:21:04 +0100 (CET)
From: <mohamed.boucadair@orange.com>
To: Marco Tiloca <marco.tiloca@ri.se>, "supjps-ietf@jpshallow.com" <supjps-ietf@jpshallow.com>, "core@ietf.org" <core@ietf.org>
CC: "draft-ietf-core-new-block@ietf.org" <draft-ietf-core-new-block@ietf.org>, "dots@ietf.org" <dots@ietf.org>
Thread-Topic: [core] I-D Action: draft-ietf-core-new-block-05.txt
Thread-Index: AQHW7mzEKkNbbrzxCk+23dClOwj886ovEB+A
Date: Tue, 19 Jan 2021 15:21:03 +0000
Message-ID: <11344_1611069664_6006F8E0_11344_455_1_787AE7BB302AE849A7480A190F8B9330315BD0BE@OPEXCAUBMA2.corporate.adroot.infra.ftgroup>
References: <161056117925.23400.10291073677288718681@ietfa.amsl.com> <24069_1610561621_5FFF3855_24069_12_1_787AE7BB302AE849A7480A190F8B9330315B92B9@OPEXCAUBMA2.corporate.adroot.infra.ftgroup> <15aa1f32-db32-6c9a-70dc-b30ed6f33466@ri.se> <00d701d6eb31$05fe11f0$11fa35d0$@jpshallow.com> <4feb5743-4193-97f1-5231-038b1838b934@ri.se> <033b01d6eda4$8013a980$803afc80$@jpshallow.com> <5fc34721-6a91-39b9-5f8d-b58e6ec905f6@ri.se> <3017_1611059042_6006CF62_3017_76_1_787AE7BB302AE849A7480A190F8B9330315BCBD4@OPEXCAUBMA2.corporate.adroot.infra.ftgroup> <caab5ba1-7f93-e6c4-e58c-6d838d2b17f1@ri.se>
In-Reply-To: <caab5ba1-7f93-e6c4-e58c-6d838d2b17f1@ri.se>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.114.13.247]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/dots/hiC2JHXEErD2H0ytf4P5ehvepQ8>
Subject: Re: [Dots] [core] I-D Action: draft-ietf-core-new-block-05.txt
X-BeenThere: dots@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "List for discussion of DDoS Open Threat Signaling \(DOTS\) technology and directions." <dots.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dots>, <mailto:dots-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dots/>
List-Post: <mailto:dots@ietf.org>
List-Help: <mailto:dots-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dots>, <mailto:dots-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 19 Jan 2021 15:21:07 -0000

Re-,

Great. Thanks. 

A version with the agreed changes is now public: 

URL:            https://www.ietf.org/archive/id/draft-ietf-core-new-block-06.txt 
Status:         https://datatracker.ietf.org/doc/draft-ietf-core-new-block/ 
Htmlized:       https://datatracker.ietf.org/doc/html/draft-ietf-core-new-block 
Htmlized:       https://tools.ietf.org/html/draft-ietf-core-new-block-06 
Diff:           https://www.ietf.org/rfcdiff?url2=draft-ietf-core-new-block-06

Cheers,
Med

> -----Message d'origine-----
> De : Marco Tiloca [mailto:marco.tiloca@ri.se]
> Envoyé : mardi 19 janvier 2021 15:10
> À : BOUCADAIR Mohamed TGI/OLN <mohamed.boucadair@orange.com>om>;
> supjps-ietf@jpshallow.com; core@ietf.org
> Cc : draft-ietf-core-new-block@ietf.org; dots@ietf.org
> Objet : Re: [core] I-D Action: draft-ietf-core-new-block-05.txt
> 
> Got it, thanks.
> 
> Best,
> /Marco
> 
> On 2021-01-19 13:24, mohamed.boucadair@orange.com wrote:
> > Hi Marco,
> >
> > The proposed edits look good to me. Will be fixed in the github.
> >
> > 2.31 is not mentioned in in the excerpt you quoted from Section
> 3.3 because 2.31 is not **required**. A server may decide to not
> reply with 2.31 as a function of its overall load and prefer to
> observe a pause before handling the next block. That’s is why we do
> have SHOULD, not a MUST.
> >
> > Cheers,
> > Med
> >
> >> -----Message d'origine-----
> >> De : Marco Tiloca [mailto:marco.tiloca@ri.se] Envoyé : mardi 19
> >> janvier 2021 12:50 À : supjps-ietf@jpshallow.com; BOUCADAIR
> Mohamed
> >> TGI/OLN <mohamed.boucadair@orange.com>om>; core@ietf.org Cc :
> >> draft-ietf-core-new-block@ietf.org; dots@ietf.org Objet : Re:
> [core]
> >> I-D Action: draft-ietf-core-new-block-05.txt
> >>
> >> Hi Jon,
> >>
> >> Thanks, please see below some minor points, otherwise it looks
> good
> >> to me.
> >>
> >> Best,
> >> /Marco
> >>
> >> * Section 3.1 - In the paragraph right above Table 2, s/with CoAP
> >> over TCP/with CoAP over reliable transports.
> >>
> >> * Section 3.1 - I think that the new final paragraph "Note that
> if
> >> Q-Block1 (or Q-Block2) ... MUST NOT be included." fits better
> before
> >> the paragraph discussing the use of OSCORE, i.e. "The Q-Block1
> and
> >> ...
> >> fragmentation of requests."
> >>
> >> * Section 3.3 - "For Non-confirmable transmission, no response is
> >> required until the successful receipt of the body by the server
> or
> >> some of the payloads have not arrived after a timeout and a
> >> retransmit missing payloads response is needed."
> >>
> >>    Shouldn't this also mention the case where the server sends a
> >> 2.31 response to have the client continue sending the next
> >> MAX_PAYLOADS payloads?
> >>
> >> * Section 3.3 - Proposed clarification for the 4.02 response
> code:
> >>
> >>     "Either this Response Code (in case of Confirmable request)
> or a
> >> reset message (in case of Non-confirmable request) MUST be
> returned
> >> if the server does not support the Q-Block1 Option."
> >>
> >>
> >> On 2021-01-18 15:16, supjps-ietf@jpshallow.com wrote:
> >>> Hi Marco,
> >>>
> >>> We have updated github [1] to take account of your latest
> comments
> >> for your review.
> >>> Regards
> >>>
> >>> Jon
> >>> 


_________________________________________________________________________________________________________________________

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.