IETF Logo Mail Archive

Re: [Drip] WGLC for draft-ietf-drip-arch

Daniel Migault <mglt.ietf@gmail.com> Tue, 02 March 2021 22:23 UTC

Return-Path: <mglt.ietf@gmail.com>
X-Original-To: tm-rid@ietfa.amsl.com
Delivered-To: tm-rid@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5ECB63A1323 for <tm-rid@ietfa.amsl.com>; Tue, 2 Mar 2021 14:23:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.096
X-Spam-Level:
X-Spam-Status: No, score=-2.096 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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-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=gmail.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 x6KQ_xCxa1do for <tm-rid@ietfa.amsl.com>; Tue, 2 Mar 2021 14:22:58 -0800 (PST)
Received: from mail-ua1-x929.google.com (mail-ua1-x929.google.com [IPv6:2607:f8b0:4864:20::929]) (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 846803A1322 for <tm-rid@ietf.org>; Tue, 2 Mar 2021 14:22:58 -0800 (PST)
Received: by mail-ua1-x929.google.com with SMTP id y35so7312226uad.5 for <tm-rid@ietf.org>; Tue, 02 Mar 2021 14:22:58 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=tdHfvswEuPbvIPwco2FCZodNCeUl55aNluENnN6uNGc=; b=e90EeK5hIH5FKvpZr43R19wZjxAOBSc1jtfWUrtYcqO8VRk1qzaRXXXG2w9znmrd7b 6ThWjj7Zokbm8rnc+kvFhkWEUS2wgq3yC76VOCp/jNNRUpuYYeHL8jfU+qAlEu4S9ka/ ef7PYzqY2C6V6aRnI6cGzeUSrMnsFs3s56oA2EcFaHGlrwfrUCavr7tJVuYSk0809iBH 9SI14EB5R9vOC35g47fNiYgroqItwiO8KEPucPajUwkwXK0PDRH3Copg92zDoIQOJpJW vCcg5Qr7gOk+WW0TZWdEh5h3tDsYWE5liAXLAfSJn4MHkiQp/TXdKQTbAI7P4aY1lB0Z zLQg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=tdHfvswEuPbvIPwco2FCZodNCeUl55aNluENnN6uNGc=; b=rR0+H8jRNBDmeTt0YTWbUku+AesYmNXAuWxSpCMncPa/1yz6UWA9vVpwwuQxVz5qc+ YPbjmP7GeMpogsqF/bD47CxgFYpUkuBh6RanmVRykZdEd7jmTwak5whRSQFySQNCZIct xhRPJ9lC8H5fn5u4gRaYp4UCCn4CI5un7e8YR9bD0ucGp8KgWK4PutejY7wGRFcL+i9F 4y4thdqJQLf+vP67+KlQP25pZ4X8F00wMB9ltfcn3fSTVCxS3amar6wJLUx7TBIySd/B LVs5MhMpFm44zzX8WMDzblP2RguxWzxsDWysBmlaSf2hwm4giqpfNYEZb1CHTm+99reX O4aA==
X-Gm-Message-State: AOAM533ZxJXhtwovPLiY4Ur8qrLuLZNEFdZwK74fELPjk2ofJXkQ3NYl 5aG2xe33ubivvLHR9zsM78yksROznQLWGmBA227EyZieavY=
X-Google-Smtp-Source: ABdhPJyBnxsQRcRPKZiP3l9JRKcZTDHSaRNDv1bKvYUKHqkm/QIF7bL81ixLDi+vZgQUUDrveHYbkwJXm/7C04cIww4=
X-Received: by 2002:ab0:42c:: with SMTP id 41mr13852476uav.80.1614723776694; Tue, 02 Mar 2021 14:22:56 -0800 (PST)
MIME-Version: 1.0
References: <CADZyTkkfO6AcFhshN3TvO5tUzRp=FDi17_j0DhcXjyn7zC5oSw@mail.gmail.com> <20210227104656.GA24369@sources.org>
In-Reply-To: <20210227104656.GA24369@sources.org>
From: Daniel Migault <mglt.ietf@gmail.com>
Date: Tue, 02 Mar 2021 17:22:45 -0500
Message-ID: <CADZyTkm7fiABokZPBR0RSdGyN-F00YCqw0FWN6x2q2iEQ6kGLw@mail.gmail.com>
To: Stephane Bortzmeyer <bortzmeyer@nic.fr>
Cc: tm-rid@ietf.org
Content-Type: multipart/alternative; boundary="0000000000001ecafe05bc952dd3"
Archived-At: <https://mailarchive.ietf.org/arch/msg/tm-rid/4wFbHi5pPI_A6XO-vR6H2_Ils7s>
Subject: Re: [Drip] WGLC for draft-ietf-drip-arch
X-BeenThere: tm-rid@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Drone Remote Identification Protocol <tm-rid.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tm-rid>, <mailto:tm-rid-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tm-rid/>
List-Post: <mailto:tm-rid@ietf.org>
List-Help: <mailto:tm-rid-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tm-rid>, <mailto:tm-rid-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Mar 2021 22:23:00 -0000

Hi,

I have provided my comments in a PR [1]. I thought it might be useful to
use the git interface to follow up the comments. In some cases there is
only a comment, in other cases I added a space to the text I raised
concerned so it appeared in the PR and hopefully can be updated, in other
case I did the update directly.

If this happens to be not useful at all, feel free to let me know.

Yours,
Daniel

[1] https://github.com/ietf-wg-drip/draft-ietf-drip-arch/pull/2/files

On Sat, Feb 27, 2021 at 5:48 AM Stephane Bortzmeyer <bortzmeyer@nic.fr>
wrote:

> On Tue, Feb 23, 2021 at 09:57:22AM -0500,
>  Daniel Migault <mglt.ietf@gmail.com> wrote
>  a message of 54 lines which said:
>
> > This email starts a WGLC for  draft-ietf-drip-arch available here:
> >  https://datatracker.ietf.org/doc/html/draft-ietf-drip-arch-10
> >
> > Please review the document and provide your feed back / comments by March
> > 9.
>
> I've read -11. Drones are clearly not my area of expertise. The draft
> is hard to follow, with a number of acronyms I'm not familiar
> with. Some are in section "3.2.  Abbreviations", some are defined at
> first use. There is certainly a reason for this difference but it does
> not help the reader.
>
> Also, I have the feeling that the draft is quite vague on many
> aspects, and it mixes architectural issues with details which are very
> interesting (such as the discussion about sizes of cryptographic keys
> and signatures) but may be not for an "architecture" document. Also,
> I'm glad there are rationales for some decisions (why HHIT and not HIT
> or CGA) but they should be more separated from the specification of
> the choosen architecture.
>
> Regarding the claim of vagueness, let's take the DNS part as an
> example. "These public information registries can use secure DNS
> transport (e.g.  DNS over TLS)" Is it to become a MAY in the future
> protocol? There is no today an IETF standard about DNS-over-TLS for
> authoritative name servers. Today, it looks like Hand-waving. And why
> DNSSEC disappeared? (It was in -08.)
>


-- 
Daniel Migault
Ericsson

v2.23.0 | Report a Bug | By Email