Re: [Bier] Robert Wilton's Discuss on draft-ietf-bier-te-arch-10: (with DISCUSS and COMMENT)
Alvaro Retana <aretana.ietf@gmail.com> Wed, 25 August 2021 15:43 UTC
Return-Path: <aretana.ietf@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 647653A0966; Wed, 25 Aug 2021 08:43:46 -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, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=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 4GuytWWZBa7H; Wed, 25 Aug 2021 08:43:40 -0700 (PDT)
Received: from mail-ej1-x631.google.com (mail-ej1-x631.google.com [IPv6:2a00:1450:4864:20::631]) (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 4E7723A096B; Wed, 25 Aug 2021 08:43:40 -0700 (PDT)
Received: by mail-ej1-x631.google.com with SMTP id u3so52540088ejz.1; Wed, 25 Aug 2021 08:43:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:in-reply-to:references:mime-version:date:message-id:subject:to :cc:content-transfer-encoding; bh=STy/qwHK8KXcoMgUe2HAjuJcoDocK8MGohzZ3Pu8Rzo=; b=mLtw0n1ThRdSinFcCYJCBRJX92ewgO61rdTQ4W83pwbmNKasZ2OM7ymwO1c1acSm2f WDOsfBLPh+Let0dvg2IZA+jLXWI3hqlfvigG8+Jjltq2tY0/1cTKIwOi60vcXlilRslz 9zTTr5OpsOaDqCps0+ST+uCqnHhxwuC5FMfZunWQUAB/6VEqgfjWTGftHO+bn43oJDgc nB11us9kAHpoC6ctPEqVosHv1cctaIMAkkuXUJ7x1GbhzZkqSYaKBb9Ew50ETm9adeAR u/nNQR60TLBqwWvi4AKGaZcE8YFVPVST4sEu/KMEGdlRsyUFtOh+k3MB0YrDGPrJocxq 9Wug==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:in-reply-to:references:mime-version:date :message-id:subject:to:cc:content-transfer-encoding; bh=STy/qwHK8KXcoMgUe2HAjuJcoDocK8MGohzZ3Pu8Rzo=; b=tszuAfnmqN0ksbr5ytOseAqf6/GlQOisl1he9l11DCycCueGzG4n1sRnlUfI8QhSMX JQ5y3EiG9ZlF57Zd38qfieSJBjq4l5zVIz2fEhZZ5GT/5uGtop7C3DI5ME/ffHuSJ+Nd NLFcPINOB96dyuhbS5wApWiiCV6ewMcLyj0SpuXGFae10suWjg4BJNK/ZQY3pPC5sj6B kpZyRZ4ry/O9Qfk/mVQ6fHzqxOqEP1W5sv6qvidWmSQ8BaPi8Yxt81K3sWt/sCkn39KM 211BC/q2sY8WvsYNYlR2feqtL7DQ62H44+FSjw9HW5/QM5PZPCPA4JWgBIZZfoWmm1yj u6OA==
X-Gm-Message-State: AOAM5305KxGUeZJ0YTs9BaRQHm+6vLTaCfoIojmGfNQ2lY4qWJvwIWCi O+UsuuRn+XTJKgbFAyllrrLewZvXFM6sLNAWDaARjVyd
X-Google-Smtp-Source: ABdhPJxgYpslbx5sFNiT43YDLQFh6wa3KAfEuSC34CM6Pd/NkoI7U4rcNhbP11bf1uHtshdzkt6uwmToamsYBofY+Mc=
X-Received: by 2002:a17:907:384:: with SMTP id ss4mr23268059ejb.478.1629906217666; Wed, 25 Aug 2021 08:43:37 -0700 (PDT)
Received: from 1058052472880 named unknown by gmailapi.google.com with HTTPREST; Wed, 25 Aug 2021 08:43:37 -0700
From: Alvaro Retana <aretana.ietf@gmail.com>
In-Reply-To: <162989945476.29713.12937356180696657837@ietfa.amsl.com>
References: <162989945476.29713.12937356180696657837@ietfa.amsl.com>
MIME-Version: 1.0
Date: Wed, 25 Aug 2021 08:43:37 -0700
Message-ID: <CAMMESsxiRE_YijFK6pKfk74O=xzAoRCmvBDDkeTcMLom5pexdA@mail.gmail.com>
To: Robert Wilton via Datatracker <noreply@ietf.org>, The IESG <iesg@ietf.org>, Robert Wilton <rwilton@cisco.com>
Cc: draft-ietf-bier-te-arch@ietf.org, Xuesong Geng <gengxuesong@huawei.com>, bier@ietf.org, bier-chairs@ietf.org
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/bier/UL4w7LdVFpz1NQopX0BkRaLDWwQ>
Subject: Re: [Bier] Robert Wilton's Discuss on draft-ietf-bier-te-arch-10: (with DISCUSS and COMMENT)
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: Wed, 25 Aug 2021 15:43:47 -0000
On August 25, 2021 at 9:50:55 AM, Robert Wilton wrote: Rob: Hi! Both RFC8279 and RFC8296 are in fact Standard Track documents. The bier WG was originally chartered to produce experimental work, right as those documents were published (as Experimental), the WG was rechartered and the status of the documents was changed to Standards Track: https://datatracker.ietf.org/doc/status-change-bier-core-to-proposed-standard/ FWIW, the datatracker shows the correct status even if the document doesn't. Yes, that is confusing. :-( Thanks! Alvaro. > ---------------------------------------------------------------------- > DISCUSS: > ---------------------------------------------------------------------- > > Hi, > > I would like to please double check with the authors, responsible AD, and IESG > that publishing this as standards track is the right choice (as opposed to > experimental). > > From the first line of the introduction: > "BIER-TE is based on architecture, terminology and packet formats with > BIER as described in [RFC8279] and [RFC8296]. > > Both RFC 8279 and RFC 8296 are experimental RFCs, hence (1) I wanted to check > that by publishing this draft as Std Track, that this draft isn't being built > on an unstable footing. > > This draft has a normative reference to RFC 8279, but only an informative > reference to RFC 8296. > > Hence, I further wanted to check: > (2) Should RFC 8296 really be a normative reference? > (3) The IETF LC announcement didn't seem to flag the downref to RFC 8279. RFC > 8067 says that is not strictly required, but in this case I think that would > have been useful. > > I can see from the document history that the WG has flip-flopped on whether > this document should be experimental or stds track, but I couldn't quickly > find this discussion, and it wasn't covered in shepherds writeup. If it is > possible for someone to provide a quick summary as to why it is okay and > right to publish this as standards track that would be appreciated.
- [Bier] Robert Wilton's Discuss on draft-ietf-bier… Robert Wilton via Datatracker
- Re: [Bier] Robert Wilton's Discuss on draft-ietf-… Alvaro Retana
- Re: [Bier] Robert Wilton's Discuss on draft-ietf-… Rob Wilton (rwilton)
- Re: [Bier] Robert Wilton's Discuss on draft-ietf-… Alvaro Retana
- Re: [Bier] Robert Wilton's Discuss on draft-ietf-… Warren Kumari
- Re: [Bier] Robert Wilton's Discuss on draft-ietf-… Murray S. Kucherawy
- [Bier] RFC status change (was: Re: Robert Wilton'… Toerless Eckert
- Re: [Bier] Robert Wilton's Discuss on draft-ietf-… Toerless Eckert