[core] I-D Action: draft-ietf-core-echo-request-tag-10.txt
internet-drafts@ietf.org Mon, 13 July 2020 19:42 UTC
Return-Path: <internet-drafts@ietf.org>
X-Original-To: core@ietf.org
Delivered-To: core@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 0D0C83A05A0; Mon, 13 Jul 2020 12:42:07 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
Cc: core@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 7.8.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: core@ietf.org
Message-ID: <159466932700.14803.16449149770794423255@ietfa.amsl.com>
Date: Mon, 13 Jul 2020 12:42:07 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/kd4ZF7Gk3XfT71sS1yaH0AHT8bk>
Subject: [core] I-D Action: draft-ietf-core-echo-request-tag-10.txt
X-BeenThere: core@ietf.org
X-Mailman-Version: 2.1.29
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: Mon, 13 Jul 2020 19:42:07 -0000
A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Constrained RESTful Environments WG of the IETF.
Title : CoAP: Echo, Request-Tag, and Token Processing
Authors : Christian Amsüss
John Preuß Mattsson
Göran Selander
Filename : draft-ietf-core-echo-request-tag-10.txt
Pages : 31
Date : 2020-07-13
Abstract:
This document specifies enhancements to the Constrained Application
Protocol (CoAP) that mitigate security issues in particular use
cases. The Echo option enables a CoAP server to verify the freshness
of a request or to force a client to demonstrate reachability at its
claimed network address. The Request-Tag option allows the CoAP
server to match block-wise message fragments belonging to the same
request. This document updates RFC7252 with respect to the client
Token processing requirements, forbidding non-secure reuse of Tokens
to ensure binding of response to request when CoAP is used with
security, and with respect to amplification mitigation, where the use
of Echo is now recommended.
The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-core-echo-request-tag/
There are also htmlized versions available at:
https://tools.ietf.org/html/draft-ietf-core-echo-request-tag-10
https://datatracker.ietf.org/doc/html/draft-ietf-core-echo-request-tag-10
A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-core-echo-request-tag-10
Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.
Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/
- [core] I-D Action: draft-ietf-core-echo-request-t… internet-drafts