Re: [Bier] status of draft-ietf-bier-oam-requirements

Greg Mirsky <gregimirsky@gmail.com> Thu, 16 April 2020 19:17 UTC

Return-Path: <gregimirsky@gmail.com>
X-Original-To: bier@ietfa.amsl.com
Delivered-To: bier@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 575343A0ECF for <bier@ietfa.amsl.com>; Thu, 16 Apr 2020 12:17:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 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, 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 bYM1ROk6xU1R for <bier@ietfa.amsl.com>; Thu, 16 Apr 2020 12:17:30 -0700 (PDT)
Received: from mail-lf1-x130.google.com (mail-lf1-x130.google.com [IPv6:2a00:1450:4864:20::130]) (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 0B3FD3A0ECE for <bier@ietf.org>; Thu, 16 Apr 2020 12:17:29 -0700 (PDT)
Received: by mail-lf1-x130.google.com with SMTP id x23so6488533lfq.1 for <bier@ietf.org>; Thu, 16 Apr 2020 12:17:29 -0700 (PDT)
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=2bIEPQUbR41RN2xJoOoMgzQlhxROn+uxFRleBcsrQSM=; b=fIzFXt5AdQAW4rj313AO2kTVyfANtiUq1ZdoyDmisEvzJnyPm7TnUTac4ItlahgzVM st44aQafs+0nCLj5ZI7RVCzahIsdu8MDEMZWb1xd/gVxTk7h1V5cWNsuMAFfNmtHPSb0 3wpdNkpc0aI80SRA6XSjlhiTTVPNF91WnUPhSh/AVpMQ9O9/QXJQ6avx70EdfWtvSdlp 6FLs1X39QBbSAtYz7F7DlJma6HBhgoH/zl8sisxhizNgkh+o6OxehIvc9bDDNIt4jm5T ez+awwTxggtcSDRLpSlnNiOcN/bJRHSnkeNpVLVWNxhqqgeJr0+s0syguKjjXaCgik1g qIvA==
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=2bIEPQUbR41RN2xJoOoMgzQlhxROn+uxFRleBcsrQSM=; b=JCJpfuaV/70nPvFNm00y9aqwG4M5DfNtA6BcQYEFjiGahJ5pCnhUyaDziwyiz5KFZ8 J33jM60xumIrTd6Kv5ULvV+7SKLf5VPeVYDFAS/jSBWmZAVCkiX9tJvfDXHXcsgMxmSQ numNUEwS9ybZqLNtPao0uDg1cDSxYapP4PEE1D7rYawK2IsXZatBeiBgTcwYbH3eygRs 52FMB0Z1rQpfUKob8pFgYwUFAIBiyF460rDJeEAA43psNnBGVNYyp/rItxxsLwEibq8L SuUWEJg7ju7LxYH6HciLWQ0TZ1xtK9RKqdiYVssRilvVCaK6R1VeXjJSAEjva2KzWToQ pmZg==
X-Gm-Message-State: AGi0PuZXg/oiraVzmALOjOLg6Eh5/AC71qGz36+0rXdpmwt6cDLJ1RQP WtVdsbw2L7UxnG5IHWCrkNQY1YAcT1CudHSKZ9s=
X-Google-Smtp-Source: APiQypJ/yJX4tvLMEGR5qKJ11VHdC2lqvHthdJ50gX5ctgwqOaa3Ia4BpYBTOz4YDZjFIPVQ+L5G8YbZrQ+0BbwWAqo=
X-Received: by 2002:a19:c895:: with SMTP id y143mr6482758lff.123.1587064647932; Thu, 16 Apr 2020 12:17:27 -0700 (PDT)
MIME-Version: 1.0
References: <CA+wi2hPRtCz2kumEHGzxuFqvyhWexQzHSaiT21JFaHuYO9wTAA@mail.gmail.com>
In-Reply-To: <CA+wi2hPRtCz2kumEHGzxuFqvyhWexQzHSaiT21JFaHuYO9wTAA@mail.gmail.com>
From: Greg Mirsky <gregimirsky@gmail.com>
Date: Thu, 16 Apr 2020 12:17:17 -0700
Message-ID: <CA+RyBmWQ5UWYZiBb1OheL_sdxK9_D8uYV8h4zHHZFfOgwqYp9g@mail.gmail.com>
To: Tony Przygienda <tonysietf@gmail.com>
Cc: BIER WG <bier@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000093601f05a36d4891"
Archived-At: <https://mailarchive.ietf.org/arch/msg/bier/C4apU5t_Ih2tb3Vg3Bf89sWdngg>
Subject: Re: [Bier] status of draft-ietf-bier-oam-requirements
X-BeenThere: bier@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "\"Bit Indexed Explicit Replication discussion list\"" <bier.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/bier>, <mailto:bier-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/bier/>
List-Post: <mailto:bier@ietf.org>
List-Help: <mailto:bier-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/bier>, <mailto:bier-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Apr 2020 19:17:33 -0000

Hi Tony, Greg, et al.,
thank you for the most detailed explanation of the state of this document
and where it can go from here. I believe that the document is an important
part of the overall work on the OAM toolset in BIER. As that work is not
yet complete the publication of the draft-ietf-bier-oam-requirements would
help those interested in further developing BIER OAM. On the other hand, to
the best of my understanding and please correct me if I'm wrong here, the
headstone saying "Dead WG Document" would not remove it from the list of
documents on BIER WG page and it can be easily accessed by anyone
interested to read. Also, would marking it as "Dead WG Document" affect the
progress of solution-proposing drafts that use
draft-ietf-bier-oam-requirements as an informational reference? If there
will be no negative impact, then I'd conclude with "it would be nice to
publish but the other way is okay too". I hope I didn't confuse you all.

Regards,
Greg

On Wed, Apr 15, 2020 at 8:42 AM Tony Przygienda <tonysietf@gmail.com> wrote:

> Dear BIER WG participants, situation of
> https://datatracker.ietf.org/doc/draft-ietf-bier-oam-requirements/ is
> unsatisfactory at this point in time.
>
> The draft was adopted around 2015 but did not elicit any comments or
> significant technical changes for the 5 years following or during the WGLC
> (which was bundled with 2 other drafts on top). Only activity were some
> private discussions among the authors as to the content of the authors
> list. A shepherd was assigned quite a while ago, no write-down was provided
> and no activity was seen. Given that the response to authors as to their
> participation and call for two volunteers to act as editors met with, ehem,
> underwhelming response, it looks like we may be flogging a dead horse
> forward here towards publication.
>
> Hence, I would suggest that we call a WG LC consensus again to gauge the
> interest on this draft. We will need multiple people across multiple
> organizations explaining support with more than just "+1" mail and
> obviously having read the draft and ideally commenting why they think this
> draft is WGLC ready & should be published. On top I suggest that we need
> the shepherd to read/comment on the draft. If we get that together then the
> document should be forwarded towards IESG (with diminished authors' list
> per latest feedbacks given) or otherwise we move it to "Dead WG Document"
> status and we may warm it up in the future should the interest perk up.
>
> Opinions? Otherwise the according calls will go to the list in next couple
> days ...
>
> thanks
>
> --- tony
> _______________________________________________
> BIER mailing list
> BIER@ietf.org
> https://www.ietf.org/mailman/listinfo/bier
>