Re: [Last-Call] Tsvart last call review of draft-ietf-drip-arch-22

Kyle Rose <krose@krose.org> Mon, 11 April 2022 14:53 UTC

Return-Path: <krose@krose.org>
X-Original-To: last-call@ietfa.amsl.com
Delivered-To: last-call@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 88DB03A0A4A for <last-call@ietfa.amsl.com>; Mon, 11 Apr 2022 07:53:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.108
X-Spam-Level:
X-Spam-Status: No, score=-2.108 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, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=krose.org
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 LH_qKYdhEaWl for <last-call@ietfa.amsl.com>; Mon, 11 Apr 2022 07:52:59 -0700 (PDT)
Received: from mail-wr1-x434.google.com (mail-wr1-x434.google.com [IPv6:2a00:1450:4864:20::434]) (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 5C04C3A099D for <last-call@ietf.org>; Mon, 11 Apr 2022 07:52:59 -0700 (PDT)
Received: by mail-wr1-x434.google.com with SMTP id b19so23375068wrh.11 for <last-call@ietf.org>; Mon, 11 Apr 2022 07:52:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=krose.org; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=/g3AXeuf/W5+oa2lp9nLUsxvJQYrpKNBBwrR6tTHDQg=; b=llDHsW2Lxg8sMgyWdzpBtrUt9Eyrc0IhEXV8BZsK/ocn+8fw00OcQ0lk3aj6+howdd tth/exsUXlnUj48RUzkhaoC8angwkXJp4kueXjbCCIyPXsBLAuj18zOBz5IsHQtjP2Tf jb6iIsPs6dHTYAhBu1euB29WocNHwR5JMhyO0=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=/g3AXeuf/W5+oa2lp9nLUsxvJQYrpKNBBwrR6tTHDQg=; b=e3UKnKcGpsHfKroFNsTIiQgMA8uKBxP8NcwFk8nh156ruy/v34Z6A+Ty8t6zMGpuwN 4waBHHnVOVZeaGuKcP4HJGxYVxupmr9U95huWzA2OwC5x3QsYnfqvt44JRNbA4hrSR3s jxV0Y3darZ/2cFcSpRb1vmUhXLQBnqadqAAFu2j+1JEvKShdQTqnP89q40wFaBfnBKmu DSwTWHPTcZHsNUVpRC0l5jkv1TgXewWRpsEU8hHuse+eBd5NrEKaC2LIpFeyl67r8Op9 hBYesPvSSGKAQwZ6LNfZ5wbCOzshPC3xJ9jwjoAHBTM/CVXvzE6yCFYd/1KUw+heOSwM XOrA==
X-Gm-Message-State: AOAM531WQSsXLy18vMF5tKXX3rw9WJiR/DCLBmOgJbIsh/wy7MeOfcIN N2FlkI9KadWhBQ2meczbCcIDyc448YNflsn9KoO+0g==
X-Google-Smtp-Source: ABdhPJy7sBahHcEYfdkslIBJSjdqVDTgsk2ZU33puPTmsQ+eEllQyUsJjO0DLUjXYDM0eKAbp9Gze0GVBgq1PJam23A=
X-Received: by 2002:adf:f746:0:b0:207:9bc7:68ba with SMTP id z6-20020adff746000000b002079bc768bamr10428885wrp.600.1649688777080; Mon, 11 Apr 2022 07:52:57 -0700 (PDT)
MIME-Version: 1.0
References: <164917011975.19763.17148975510019277045@ietfa.amsl.com> <FD42868B-9AE0-429C-90F7-65E6889BC2FB@cisco.com>
In-Reply-To: <FD42868B-9AE0-429C-90F7-65E6889BC2FB@cisco.com>
From: Kyle Rose <krose@krose.org>
Date: Mon, 11 Apr 2022 10:52:46 -0400
Message-ID: <CAJU8_nUnzNeGUft3kmsaVvt0FL4zj-V1EDrOrWUPYFS+7o4Bxg@mail.gmail.com>
To: "Eric Vyncke (evyncke)" <evyncke@cisco.com>
Cc: "tsv-art@ietf.org" <tsv-art@ietf.org>, "draft-ietf-drip-arch.all@ietf.org" <draft-ietf-drip-arch.all@ietf.org>, "last-call@ietf.org" <last-call@ietf.org>, "tm-rid@ietf.org" <tm-rid@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000008c568a05dc6219bf"
Archived-At: <https://mailarchive.ietf.org/arch/msg/last-call/YLTGcg-yUMqT2NzCM1c15Bg_tSM>
Subject: Re: [Last-Call] Tsvart last call review of draft-ietf-drip-arch-22
X-BeenThere: last-call@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF Last Calls <last-call.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/last-call>, <mailto:last-call-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/last-call/>
List-Post: <mailto:last-call@ietf.org>
List-Help: <mailto:last-call-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/last-call>, <mailto:last-call-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 11 Apr 2022 14:53:05 -0000

On Wed, Apr 6, 2022 at 12:03 PM Eric Vyncke (evyncke) <evyncke@cisco.com>
wrote:

> First, thank you for your technical review on this document. The more eyes
> on a document, the better the result.
>

And thank you for the reply!


> Allow me to reply, as the responsible AD for DRIP, about your last point:
> whether this work should happen at the IETF.
>
> As an IESG member, my view is that the IETF should welcome new pieces of
> work related to IP technologies. After two BoF, and a community consensus,
> the DRIP WG was officially formed (i.e., with the IETF community support).
> While the DRIP meetings do not attract hundreds of people, there are enough
> IETF engineers to make progress. So, in my opinion, this work can be done
> at the IETF (albeit other fora could have hosted it as the work is at the
> border of other fora -- like ICAO). The charter is also explicitly
> requesting the re-use of existing protocols as much as possible.
>

Understood and stipulated. I'm explicitly second-guessing IETF consensus on
this one from the vantage point of hypotheticals such as "If I were looking
for standards in this area, where would I first look?", mostly because I
have had the discussion of scope creep in the past with fellow IETFers and
wanted a concrete example of what I mean by that documented somewhere.

Anyway, I expected to be in the rough on this one, so I won't belabor it
further.
Thanks,
Kyle