Re: [Dots] draft-ietf-core-new-block for draft-ietf-dots-telemetry

mohamed.boucadair@orange.com Wed, 26 May 2021 13:07 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 C90293A2E93 for <dots@ietfa.amsl.com>; Wed, 26 May 2021 06:07:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.095
X-Spam-Level:
X-Spam-Status: No, score=-2.095 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, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, 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 lcecjWju6H8m for <dots@ietfa.amsl.com>; Wed, 26 May 2021 06:07:32 -0700 (PDT)
Received: from relais-inet.orange.com (relais-inet.orange.com [80.12.66.40]) (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 35BD23A117E for <dots@ietf.org>; Wed, 26 May 2021 06:07:26 -0700 (PDT)
Received: from opfedar02.francetelecom.fr (unknown [xx.xx.xx.4]) by opfedar27.francetelecom.fr (ESMTP service) with ESMTP id 4Fqrp41lz8z31JZ; Wed, 26 May 2021 15:07:24 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=orange.com; s=ORANGE001; t=1622034444; bh=HBlU6KfRylJhoD3nfgTIzpRCtS8mGKyQcN9pwQnKQQE=; h=From:To:Subject:Date:Message-ID:Content-Type:MIME-Version; b=aiOOFlDPmk8c2a2vK2iCIAYqCam5ubRK0j66U3cHx8H79TMnJotXXCBMjTrPANxvG 9Rll8A7KN1m+JoEKsh/AjyvZYB6bCad9uJN0o7WewT/4ygyrEKS+ng2+JWCLFIcAZW adqg20gp42x0qMQ063Fsf9AEuxNS+wxn8HvJs+GfV49dFV8ZJPUZ5h5KIuVDO+1TZj vvULisFFUKfmLPuOUbxT898blA4NWoz98OKA5svCRu/Yw70eMgCOOAyhnYLWx7le4C h8O1IunU2/9umkLtI4ZVuLCYqnUgo1yhfNrZo4+tZyAoyfERWp2l/aUAFgjRo9FarD jmE14o+1Lb0mg==
Received: from Exchangemail-eme6.itn.ftgroup (unknown [xx.xx.13.82]) by opfedar02.francetelecom.fr (ESMTP service) with ESMTP id 4Fqrp40t94zCqkV; Wed, 26 May 2021 15:07:24 +0200 (CEST)
From: mohamed.boucadair@orange.com
To: "dots@ietf.org" <dots@ietf.org>
CC: Jon Shallow <supjps-ietf@jpshallow.com>
Thread-Topic: [Dots] draft-ietf-core-new-block for draft-ietf-dots-telemetry
Thread-Index: AdcXQzssePT/XT7jQo6Gsf+7fCfXOg640+Xg
Date: Wed, 26 May 2021 13:07:23 +0000
Message-ID: <24345_1622034444_60AE480C_24345_185_5_787AE7BB302AE849A7480A190F8B93303538F49A@OPEXCAUBMA2.corporate.adroot.infra.ftgroup>
References: <06b801d71743$3ea976a0$bbfc63e0$@jpshallow.com>
In-Reply-To: <06b801d71743$3ea976a0$bbfc63e0$@jpshallow.com>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.114.13.245]
Content-Type: multipart/alternative; boundary="_000_787AE7BB302AE849A7480A190F8B93303538F49AOPEXCAUBMA2corp_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/dots/thdenufk5pDlbGghYdKTIpi4Viw>
Subject: Re: [Dots] draft-ietf-core-new-block for draft-ietf-dots-telemetry
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: Wed, 26 May 2021 13:07:43 -0000

Hi all,

Now that draft-ietf-core-new-block is almost ready to be sent to the RFC editor, it would be good if we can consider adopting draft-bosh-dots-quick-blocks so that DOTS agents can negotiate Q-Block functionality and make use of it instead of Block1/2.

Cheers,
Med

De : Dots [mailto:dots-bounces@ietf.org] De la part de Jon Shallow
Envoyé : vendredi 12 mars 2021 14:26
À : dots@ietf.org
Objet : [Dots] draft-ietf-core-new-block for draft-ietf-dots-telemetry

Hi All,

Following the Core meeting at IETF 110 today, https://datatracker.ietf.org/doc/draft-ietf-core-new-block/ which handles sending a CoAP non-confirmable body split over multiple payloads, has passed WGLC, and is waiting for the write-up to progress the document to the IESG.

This draft refers to https://datatracker.ietf.org/doc/html/draft-bosh-dots-quick-blocks-01 for an example mechanism to negotiate the additional congestion control parameters  using the DOTS signal channel configuration mechanism, defining some new YANG/CBOR mapping entries.

This draft has been implemented, available using libcoap and the specific code (not merged) can be found at https://github.com/obgm/libcoap/pull/611  and has been tested in lossy and DOTS environments.

This draft is of significance for the DOTS telemetry draft ( https://datatracker.ietf.org/doc/html/draft-ietf-dots-telemetry-15#section-4.3 ), which needs to be able to continue to send (large) telemetry information under network attack situations.

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.