From nobody Thu Aug 26 00:21:16 2021 Return-Path: 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 629C43A1198; Thu, 26 Aug 2021 00:21:10 -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 55BRVqeNW_qo; Thu, 26 Aug 2021 00:21:04 -0700 (PDT) Received: from mail-vk1-xa32.google.com (mail-vk1-xa32.google.com [IPv6:2607:f8b0:4864:20::a32]) (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 4E5993A1187; Thu, 26 Aug 2021 00:21:04 -0700 (PDT) Received: by mail-vk1-xa32.google.com with SMTP id 1so580324vkk.1; Thu, 26 Aug 2021 00:21:04 -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=emCL33DJCCTXYwhoMZCz9g0Vam1hEORGXQHzpT5AMiw=; b=MHmejgtK3B4vTbasEGH1kdBkMh/JA+audBXc5Btc+7wiWsiJKIo0Q5M2Oeswc0iR5U oJlOixqfvH4XREZQuExfx5VhxKQfe90IDBSK456Or+TrB4lC65ZzZe9jo9szsRlp3LaT YqNHgJYclDG7rgQuwL/NTM8jUz3iY9tpB46YJHdlbHE3zmL/BfWX26fFLFZ4UqBL+6dX QAARKkWzPg9WuxyTMbM2vyoHR4ZUCtHLCEkz/+p8YW7XrrjZmUyeGD6CDjlPvSP4tBbV kjZq0uRJ5mc1SITqDTUzoZoNADDripIIy73kZP5OXOjz/IpU03Ul1CPQZyzFLFYMj3/B 0sMQ== 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=emCL33DJCCTXYwhoMZCz9g0Vam1hEORGXQHzpT5AMiw=; b=GrkNFQ4ZPzu3Zhjy+raCp5cLVgcr1W7d5W4MYjXzeYp6QoRvLl5jmzmJwzYVzuy9Sz 0hv6hA1YEHGNGPukqGIlItP0Ehq4mL0Xi3Gc4Swd5si00uDAAcYtgXd1XOhHsi0uiH7N wd40O2BYmOcJAai0xZ6tdZiukdX1Jaj8GVe3/VK46B+3p1S95PF9PeORxF+yRvLPu7yU blv7Lu5RaO7LpfaMgo39+pJuzb9hM3iI5IuHnfJUeBE4X58xP1wSgDaClb/6trQKR8zj cQGpYCsK9E0g//mGkdm4BRiBR1ZllzBWYr/0UkyACvkLMjsobWKSqtCm5iCXDBkiaXlI 6uqA== X-Gm-Message-State: AOAM533VSv3Ur/phHvei3qsbWvr9ND8AbsQQnLPm59iZ3VTYFsFU+a5T Y7A54fsYOAhBxqG1LJcM7EEijHHoZAI00Vx4EzI= X-Google-Smtp-Source: ABdhPJy7M9Vsuz3Lj3gEolS3nXPN7mCj79OUkkd2cpQbfvWTnXJHSokZQZBQVR390Pd7gI3eG2PKsL55VSkuFTuluAg= X-Received: by 2002:a1f:3215:: with SMTP id y21mr1321777vky.13.1629962462276; Thu, 26 Aug 2021 00:21:02 -0700 (PDT) MIME-Version: 1.0 References: <162989945476.29713.12937356180696657837@ietfa.amsl.com> In-Reply-To: From: "Murray S. Kucherawy" Date: Thu, 26 Aug 2021 00:20:51 -0700 Message-ID: To: Warren Kumari Cc: Alvaro Retana , "bier@ietf.org" , "Rob Wilton (rwilton)" , "draft-ietf-bier-te-arch@ietf.org" , The IESG , Xuesong Geng , "bier-chairs@ietf.org" Content-Type: multipart/alternative; boundary="0000000000008fb1cb05ca713557" Archived-At: 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\"" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 26 Aug 2021 07:21:11 -0000 --0000000000008fb1cb05ca713557 Content-Type: text/plain; charset="UTF-8" Since I almost DISCUSSed the same thing: On Wed, Aug 25, 2021 at 12:16 PM Warren Kumari wrote: > > > When I pulled up these docs, and both in tools and datatracker the >> document >> > boilerplate has them as experimental. Do you know if this is a generic >> issue, >> > or specific to these docs for some reason? I would say that having >> different >> > status in different places is highly confusing. >> >> Yes, it is confusing. The problem is that the boilerplate is part of > > the RFC, so it's immutable. >> > > Can someone ELI5 why we don't just republish documents when the status > changes? > > It seems like it would be trivial to take RFC8296, and run `sed /Category: > Experimental/Category: Proposed Standard/`, add "Obsoletes: RFC8296", and > slap a new number on it... > > It is already clear that we will soon need 5 digit RFC numbers, so it's > not like these are a limited resource... > I'd settle for a notation at the top in some attention-getting color, akin to "Errata Exist", something like "Status Change Exists" and a link to the status change action, or the new status, or something. -MSK --0000000000008fb1cb05ca713557 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Since I almost DISCUSSed the same thing:<= /div>

On Wed, Aug 25, 2021 at 12= :16 PM Warren Kumari <warren@kumari= .net> wrote:

> When I pulled up these docs, and both in tools and datatracker the doc= ument
> boilerplate has them as experimental. Do you know if this is a generic= issue,
> or specific to these docs for some reason? I would say that having dif= ferent
> status in different places is highly confusing.

Yes, it is confusing.=C2=A0 The problem is that the boilerplate is part of<= /blockquote>
the RFC, so it's immutable.

Can som= eone ELI5 why we don't just=C2=A0republish documents when the status ch= anges?=C2=A0

It seems like it would be trivial to = take RFC8296, and run `sed /Category: Experimental/Category: Proposed Stand= ard/`, add "Obsoletes: RFC8296", and slap a new number on it...

It is already=C2=A0clear that we will soon need 5 d= igit RFC numbers, so it's not like these are a limited resource...

I'd settle for a notation= at the top in some attention-getting color, akin to "Errata Exist&quo= t;, something like "Status Change Exists" and a link to the statu= s change action, or the new status, or something.

= -MSK
--0000000000008fb1cb05ca713557--