IETF Logo Mail Archive

Re: [core] Feedback on DNS over CoAP - draft-lenders-dns-over-coap

Carsten Bormann <cabo@tzi.org> Wed, 01 September 2021 13:20 UTC

Return-Path: <cabo@tzi.org>
X-Original-To: core@ietfa.amsl.com
Delivered-To: core@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C13063A1162 for <core@ietfa.amsl.com>; Wed, 1 Sep 2021 06:20:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 C9kynGBmvdh9 for <core@ietfa.amsl.com>; Wed, 1 Sep 2021 06:20:05 -0700 (PDT)
Received: from gabriel-smtp.zfn.uni-bremen.de (gabriel-smtp.zfn.uni-bremen.de [IPv6:2001:638:708:32::15]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 007133A115E for <core@ietf.org>; Wed, 1 Sep 2021 06:20:04 -0700 (PDT)
Received: from smtpclient.apple (dynamic-218-v.informatik.uni-bremen.de [134.102.218.221]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-smtp.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4H04RK4xPcz2xYT; Wed, 1 Sep 2021 15:19:57 +0200 (CEST)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.120.0.1.13\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <23deb329-d20f-21ff-8178-7df494763167@fu-berlin.de>
Date: Wed, 01 Sep 2021 15:19:57 +0200
Cc: "core@ietf.org" <core@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <DD9BA64D-E265-47C7-A799-AB304A98F6C3@tzi.org>
References: <23deb329-d20f-21ff-8178-7df494763167@fu-berlin.de>
To: Martine Sophie Lenders <m.lenders@fu-berlin.de>
X-Mailer: Apple Mail (2.3654.120.0.1.13)
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/hjR9VmLA81q7u_g7URik8M5wlVc>
Subject: Re: [core] Feedback on DNS over CoAP - draft-lenders-dns-over-coap
X-BeenThere: core@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
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: Wed, 01 Sep 2021 13:20:30 -0000

Hi Martine,

I’ll look at more details later, but have an immediate opinion on this one:

> On 1. Sep 2021, at 13:52, Martine Sophie Lenders <m.lenders@fu-berlin.de> wrote:
> 
>  (c) There is one concern regarding FETCH. Various CoAP implementations
> do not support FETCH [4] (maybe because FETCH was added later to CoAP).
> This could hinder deployment of DoC or could lead DoC implementations
> that are not spec-compliant, because implementers just use GET or POST
> when FETCH is not available.

CoAP implementations that do not support FETCH need to be fixed.
If applications were to wait until everyone has implemented FETCH, there never would be an application that uses FETCH, so there would be no need to implement it.

Since implementing FETCH is near trivial if you already have implemented POST, maybe getting a list of CoAP implementations that still don’t do FETCH and generating fixes for them would be a good parallel activity to standardising DoC.

Grüße, Carsten

v2.23.0 | Report a Bug | By Email