Re: Fwd: Things that used to be clear (was Re: Evolving Documents (nee "Living Documents") side meeting at IETF105.)

Randy Bush <randy@psg.com> Fri, 05 July 2019 06:04 UTC

Return-Path: <randy@psg.com>
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 68F8E12016E for <ietf@ietfa.amsl.com>; Thu, 4 Jul 2019 23:04:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.9
X-Spam-Level:
X-Spam-Status: No, score=-6.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_HELO_NONE=0.001, 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 u2j8eyUAaqS0 for <ietf@ietfa.amsl.com>; Thu, 4 Jul 2019 23:04:08 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:8006::18]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id ABEF81200F6 for <ietf@ietf.org>; Thu, 4 Jul 2019 23:04:08 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=ryuu.rg.net) by ran.psg.com with esmtp (Exim 4.90_1) (envelope-from <randy@psg.com>) id 1hjHKI-0004Q1-7U; Fri, 05 Jul 2019 06:04:06 +0000
Date: Thu, 04 Jul 2019 23:04:05 -0700
Message-ID: <m2bly9vwyy.wl-randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Keith Moore <moore@network-heretics.com>
Cc: IETF Rinse Repeat <ietf@ietf.org>
Subject: Re: Fwd: Things that used to be clear (was Re: Evolving Documents (nee "Living Documents") side meeting at IETF105.)
In-Reply-To: <E07091D0-7E41-464E-9FC4-223F5214F479@network-heretics.com>
References: <BA582074-55F0-4808-B6D6-00B58C040DE0@network-heretics.com> <E07091D0-7E41-464E-9FC4-223F5214F479@network-heretics.com>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/26.2 Mule/6.0 (HANACHIRUSATO)
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset="US-ASCII"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/T8tFxO2SvxgTjuKoPq-tC1-Pyeo>
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, 05 Jul 2019 06:04:11 -0000

>>> I want us to go be able to produce operational guidance how to
>>> operate BGP-4 networks at a faster rate than the IETF can review and
>>> publish at this point in time.

the ops communities have such mechanisms.  the ietf is not the ideal
place to seek operational guidance for bgp networks.

does the ops community want the ietf's imprimatur on an under-reviewed
documents?

randy