[Dots] draft-ietf-core-new-block for draft-ietf-dots-telemetry
Jon Shallow <supjps-ietf@jpshallow.com> Fri, 12 March 2021 13:26 UTC
Return-Path: <supjps-ietf@jpshallow.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 4A4B83A0E10 for <dots@ietfa.amsl.com>; Fri, 12 Mar 2021 05:26:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, 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 VI2ZVFdaSBn4 for <dots@ietfa.amsl.com>; Fri, 12 Mar 2021 05:26:05 -0800 (PST)
Received: from mail.jpshallow.com (mail.jpshallow.com [217.40.240.153]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6B7953A0DAC for <dots@ietf.org>; Fri, 12 Mar 2021 05:26:05 -0800 (PST)
Received: from mail2.jpshallow.com ([192.168.0.3] helo=N01332) by mail.jpshallow.com with esmtp (Exim 4.92.3) (envelope-from <jon.shallow@jpshallow.com>) id 1lKhnl-0001iA-KL for ietf-supjps-dots@ietf.org; Fri, 12 Mar 2021 13:26:01 +0000
From: Jon Shallow <supjps-ietf@jpshallow.com>
To: dots@ietf.org
Date: Fri, 12 Mar 2021 13:26:01 -0000
Message-ID: <06b801d71743$3ea976a0$bbfc63e0$@jpshallow.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_06B9_01D71743.3EA976A0"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AdcXQzssePT/XT7jQo6Gsf+7fCfXOg==
Content-Language: en-gb
Archived-At: <https://mailarchive.ietf.org/arch/msg/dots/cZLtCFkdBHdbsM3U64yd0o2fg64>
Subject: [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: Fri, 12 Mar 2021 13:26:16 -0000
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
- [Dots] draft-ietf-core-new-block for draft-ietf-d… Jon Shallow
- Re: [Dots] draft-ietf-core-new-block for draft-ie… mohamed.boucadair