IETF Logo Mail Archive

Re: Evolving Documents (nee "Living Documents") side meeting at IETF105.)

Jared Mauch <jared@puck.nether.net> Fri, 19 July 2019 05:27 UTC

Return-Path: <jared@puck.nether.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8A88E1200FB for <ietf@ietfa.amsl.com>; Thu, 18 Jul 2019 22:27:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-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 CnnFNThyzjly for <ietf@ietfa.amsl.com>; Thu, 18 Jul 2019 22:27:19 -0700 (PDT)
Received: from puck.nether.net (puck.nether.net [204.42.254.5]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 491BC1200D7 for <ietf@ietf.org>; Thu, 18 Jul 2019 22:27:19 -0700 (PDT)
Received: from [IPv6:2603:3015:3606:cbe1:44f5:e75b:d66d:b3fa] (unknown [IPv6:2603:3015:3606:cbe1:44f5:e75b:d66d:b3fa]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by puck.nether.net (Postfix) with ESMTPSA id 4AD81540134; Fri, 19 Jul 2019 01:27:17 -0400 (EDT)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
Subject: Re: Evolving Documents (nee "Living Documents") side meeting at IETF105.)
From: Jared Mauch <jared@puck.nether.net>
In-Reply-To: <a1561aa7-5f41-0e2a-1892-cfb587196ac0@gmail.com>
Date: Fri, 19 Jul 2019 01:27:16 -0400
Cc: "Joel M. Halpern" <jmh@joelhalpern.com>, Job Snijders <job@ntt.net>, ietf@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <C3D53639-C2C0-42CE-9708-99294091E012@puck.nether.net>
References: <00618698-deec-64cf-b478-b85e46647602@network-heretics.com> <20190718231911.GA75391@shrubbery.net> <ed9d3b5b-7442-fdee-8f0f-c614ca4b59e4@network-heretics.com> <CACWOCC-T13zD1DVKA1H3UTNG9iKdNz5TDzObYPk_A6sjfPKFug@mail.gmail.com> <8F980759-324F-49C5-925A-DF0EEABBBD21@network-heretics.com> <d08dbee2-7844-d813-0b93-5db503501c7e@gmail.com> <50E6B4DF-83FC-46A5-94E9-1FF08F597CCF@network-heretics.com> <F2D5DCCF-4051-444B-9522-9E11F9F93005@fugue.com> <869599E9-7571-4677-AB9A-961027549C54@network-heretics.com> <144ff436-a7a2-22f7-7b06-4d0b3bcfefac@joelhalpern.com> <20190719041456.GL33367@vurt.meerval.net> <254fc5f6-3576-a62f-b84f-a7c5d29b0055@joelhalpern.com> <a1561aa7-5f41-0e2a-1892-cfb587196ac0@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
X-Mailer: Apple Mail (2.3445.104.11)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/umRtbzXSEANqupsjj3ClgEK5LLk>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 19 Jul 2019 05:27:21 -0000


> On Jul 19, 2019, at 1:20 AM, Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:
> 
> 
> How long does RIPE take to produce a BCOP?
> See https://www.ripe.net/publications/docs/ripe-690#2--what-is-a-bcop-

Some IETF WGs may take several years to produce a BCP.

Sometimes advice needs to change quickly as new things are learned, the IETF process may not reflect that.  Iterative drafts reflect the best collective knowledge at that point in time.  Capturing that historical view may not feel interesting today, but over time understanding the iterations and why things that changed quickly (eg: ip directed-broadcast) is useful.  Those recommendations often shift faster than the IETF could move even in the best of scenarios.

- Jared

v2.23.0 | Report a Bug | By Email