Re: [Add] The ADD WG has placed draft-boucadair-add-deployment-considerations in state "Call For Adoption By WG Issued"

Michael Richardson <mcr+ietf@sandelman.ca> Sat, 16 October 2021 22:12 UTC

Return-Path: <mcr+ietf@sandelman.ca>
X-Original-To: add@ietfa.amsl.com
Delivered-To: add@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E679A3A0791 for <add@ietfa.amsl.com>; Sat, 16 Oct 2021 15:12:44 -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 LeZNN2DIbhtT for <add@ietfa.amsl.com>; Sat, 16 Oct 2021 15:12:40 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 61A143A077A for <add@ietf.org>; Sat, 16 Oct 2021 15:12:39 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id 58F6418290 for <add@ietf.org>; Sat, 16 Oct 2021 18:13:04 -0400 (EDT)
Received: from tuna.sandelman.ca ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavisd-new, port 10024) with LMTP id zwl1kjGG9eXO for <add@ietf.org>; Sat, 16 Oct 2021 18:13:03 -0400 (EDT)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 9D8ED1808D for <add@ietf.org>; Sat, 16 Oct 2021 18:13:03 -0400 (EDT)
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 28BDFAC for <add@ietf.org>; Sat, 16 Oct 2021 18:12:37 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: add@ietf.org
In-Reply-To: <CABcZeBOWQ3-gF1zeyHhxM4YSFqnB+voRHZRPe6UfJOhyOUz2qQ@mail.gmail.com>
References: <163405362776.24337.4864570719046284586@ietfa.amsl.com> <CABcZeBOWQ3-gF1zeyHhxM4YSFqnB+voRHZRPe6UfJOhyOUz2qQ@mail.gmail.com>
X-Mailer: MH-E 8.6+git; nmh 1.7+dev; GNU Emacs 26.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha512"; protocol="application/pgp-signature"
Date: Sat, 16 Oct 2021 18:12:37 -0400
Message-ID: <11572.1634422357@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/add/71PrnSJ-QEmT_r5WA1bB7vJ_JvI>
Subject: Re: [Add] The ADD WG has placed draft-boucadair-add-deployment-considerations in state "Call For Adoption By WG Issued"
X-BeenThere: add@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Applications Doing DNS <add.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/add>, <mailto:add-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/add/>
List-Post: <mailto:add@ietf.org>
List-Help: <mailto:add-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/add>, <mailto:add-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 16 Oct 2021 22:12:45 -0000

I have a problem with the implied view here is that WGs can only adopt
documents they intend to publish.
That suggests, against our process, that documents that a WG adopts will all
be published.   When that's really a second decision.

The WG can adopt the document and not publish it.
WGs have done this with use cases and requirements regularly.
It can merge the contents into a protocol document (or documents).
It can remain as a reference of some kind to retain a history of WG
conclusions.   Adopting it costs nothing, but allows discussion of the
document to get priority over non-adopted documents.

The list of documents the WG has adopted is a list of things that a person who
wishes to participate in the WG needs to know about. (i.e.: Needs to read)

I agree with you: I don't know if the document will be useful as an operational RFC.
I think that many enterprise and ISP operators might appreciate the content.
That remains to be seen, I think.

But, since you say it's useful as background material, that implies that all participants
in the WG should be familiar with it.  So, by that argument, it should be adopted.

Eric Rescorla <ekr@rtfm.com> wrote:
    > I do not support adoption of this draft. It's largely background material
    > and I do not believe that the WG needs to work on it or publish it as an
    > RFC. It can serve its purpose just fine as an individual draft.




    > On Tue, Oct 12, 2021 at 8:47 AM IETF Secretariat <
    > ietf-secretariat-reply@ietf.org> wrote:

    >>
    >> The ADD WG has placed draft-boucadair-add-deployment-considerations in
    >> state
    >> Call For Adoption By WG Issued (entered by Glenn Deen)
    >>
    >> The document is available at
    >>
    >> https://datatracker.ietf.org/doc/draft-boucadair-add-deployment-considerations/
    >>
    >> Comment:
    >> This document is a -00 draft however the material is not new and has been
    >> moved from other WG documents into this draft as suggested during WG
    >> discussions in past meetings.
    >>
    >> This WG Adoption call will run for 2 weeks until Oct 27, 2021.
    >>
    >> thanks,
    >> ADD Co-chairs,
    >> Glenn Deen,  David Lawrence
    >>
    >> --
    >> Add mailing list
    >> Add@ietf.org
    >> https://www.ietf.org/mailman/listinfo/add
    >>

    > ----------------------------------------------------
    > Alternatives:

    > ----------------------------------------------------
    > --
    > Add mailing list
    > Add@ietf.org
    > https://www.ietf.org/mailman/listinfo/add

--
Michael Richardson <mcr+IETF@sandelman.ca>   . o O ( IPv6 IøT consulting )
           Sandelman Software Works Inc, Ottawa and Worldwide