Re: [Dots] [core] WG Last Call on draft-ietf-core-new-block

mohamed.boucadair@orange.com Tue, 12 January 2021 07: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 4829A3A118E; Mon, 11 Jan 2021 23:21:47 -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_H3=-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 XBd6s8-k3_Sk; Mon, 11 Jan 2021 23:21:46 -0800 (PST)
Received: from relais-inet.orange.com (relais-inet.orange.com [80.12.66.40]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C415E3A0EF0; Mon, 11 Jan 2021 23:21:45 -0800 (PST)
Received: from opfedar05.francetelecom.fr (unknown [xx.xx.xx.7]) by opfedar21.francetelecom.fr (ESMTP service) with ESMTP id 4DFMT32M6Sz7tHK; Tue, 12 Jan 2021 08:21:43 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=orange.com; s=ORANGE001; t=1610436103; bh=dCJGAGcA9stvRc1OmBmMzVWkvwpgGHeac9+psHA00Mo=; h=From:To:Subject:Date:Message-ID:Content-Type: Content-Transfer-Encoding:MIME-Version; b=YpY0pq8InpV+dJFUt6t01395z9c5N4ZeO6b8zGvRos2a3bbgz1IwIzjT5xT1nBOL8 yHJQ/tR2g710afkYdfwAIk7OYqeEdH3FVHtoLOVNsAvjxHopsnGP/UpQB/MKusRQS7 YkbhjskeZdmej+O5AOTl+umguEQ7D6u2DLvX/RybGpaVJ5vjByncBbSMm42+jeI2WF /c1EqAgyH+BYEuo0vx8xxaI5aRQs3O9eUgNPUHNK0VwK53fRpdsH51m3i8Fp8jQq/t xSGlBXEks0QAcyvu5qW+/e9TiMB0Ngy076+PXhBZNYuyIyETMFCUj+FJTOjKYiYCMN zEF4KXC0LaXWQ==
Received: from Exchangemail-eme6.itn.ftgroup (unknown [xx.xx.13.54]) by opfedar05.francetelecom.fr (ESMTP service) with ESMTP id 4DFMT30kLjz2xCZ; Tue, 12 Jan 2021 08:21:43 +0100 (CET)
From: <mohamed.boucadair@orange.com>
To: Marco Tiloca <marco.tiloca@ri.se>, "supjps-ietf@jpshallow.com" <supjps-ietf@jpshallow.com>, "jon@jpshallow.com" <jon@jpshallow.com>, "christian@amsuess.com" <christian@amsuess.com>, "draft-ietf-core-new-block@ietf.org" <draft-ietf-core-new-block@ietf.org>
CC: "dots@ietf.org" <dots@ietf.org>, "core@ietf.org" <core@ietf.org>
Thread-Topic: [Dots] [core] WG Last Call on draft-ietf-core-new-block
Thread-Index: AQHW6E9Bzk5nyR9aqEaF1vgDuALPQKojhhSA
Date: Tue, 12 Jan 2021 07:21:42 +0000
Message-ID: <25360_1610436103_5FFD4E07_25360_250_11_787AE7BB302AE849A7480A190F8B9330315B7B02@OPEXCAUBMA2.corporate.adroot.infra.ftgroup>
References: <022401d6e440$06763ba0$1362b2e0$@jpshallow.com> <fa7956ae-31a3-7724-3af4-4e755a719045@ri.se> <041101d6e5c2$e17fbef0$a47f3cd0$@jpshallow.com> <a549b34f-3f72-a6df-b2c3-ae9d3759b701@ri.se> <047b01d6e5e2$2115ba50$63412ef0$@jpshallow.com> <f8774b5c-9736-1cff-266f-f9b66653a86c@ri.se> <065301d6e805$286163c0$79242b40$@jpshallow.com> <df2ee5a1-0d36-7f28-534d-42f2eb063040@ri.se> <06e801d6e838$4be6ae30$e3b40a90$@jpshallow.com> <82c69828-fcc7-b039-925b-00d5a3fdce8a@ri.se>
In-Reply-To: <82c69828-fcc7-b039-925b-00d5a3fdce8a@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/k07h-V_XpIGniHBTJDDf9cIh2Mk>
Subject: Re: [Dots] [core] WG Last Call on draft-ietf-core-new-block
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, 12 Jan 2021 07:21:47 -0000

Hi Marco, all, 

With regards to 2.02, RFC7959 says the following: 

   Hence, for the methods defined in [RFC7252], Block1 is useful with
   the payload-bearing POST and PUT requests and their responses.
   Block2 is useful with GET, POST, and PUT requests and their payload-
   ^^^^^^                                                     ^^^^^^^^
   bearing responses (2.01, 2.02, 2.04, and 2.05 -- see Section 5.5 of
   ^^^^^^^^                 ^^^^
   [RFC7252]).

Which we think is broken. 

We don't echo that part in the new-block. 

Should we fill an errata against this?

Cheers,
Med

> -----Message d'origine-----
> De : Dots [mailto:dots-bounces@ietf.org] De la part de Marco Tiloca
> Envoyé : lundi 11 janvier 2021 20:23
> À : supjps-ietf@jpshallow.com; jon@jpshallow.com;
> christian@amsuess.com; draft-ietf-core-new-block@ietf.org
> Cc : dots@ietf.org; core@ietf.org
> Objet : Re: [Dots] [core] WG Last Call on draft-ietf-core-new-block
> 
> Hi Jon,
> 
> Thanks for the fast reaction. Please, see inline.
> 
> Best,
> /Marco
> 
> On 2021-01-11 17:39, supjps-ietf@jpshallow.com wrote:
> > Hi Marco,
> >
> >> response code beside it).
> > [Jon] Thanks - added.  Also added in 2.02 and 2.05 as being
> expected response codes in 3.3.
> 
> ==>MT
> Looks good.
> <==
> 

_________________________________________________________________________________________________________________________

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.