Re: is there a specific proposal for living ops docs?

Job Snijders <job@instituut.net> Fri, 19 July 2019 23:20 UTC

Return-Path: <job@instituut.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 BCF131200A1 for <ietf@ietfa.amsl.com>; Fri, 19 Jul 2019 16:20:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=instituut-net.20150623.gappssmtp.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 9IXS7oAxc7MN for <ietf@ietfa.amsl.com>; Fri, 19 Jul 2019 16:20:07 -0700 (PDT)
Received: from mail-ot1-x32b.google.com (mail-ot1-x32b.google.com [IPv6:2607:f8b0:4864:20::32b]) (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 058CD120033 for <ietf@ietf.org>; Fri, 19 Jul 2019 16:20:06 -0700 (PDT)
Received: by mail-ot1-x32b.google.com with SMTP id l15so34428824otn.9 for <ietf@ietf.org>; Fri, 19 Jul 2019 16:20:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=instituut-net.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=aneJrd9GDXstFPtdN0SMYpsiLbVeAJ0xJm4MPVtWDqA=; b=gyJ+ISugY9pHXpcuGvm3twgCtIXzpS+qGRvwSzu0tHX+VVYcsFiZ+jT0uKpvrseXpu TBDJytJajdegmc8IXCTMQLvahCzKFSIrrQ2X/R0g+k/4G9HP/jxAV0E8q4LIho6nKYFi cLcZ/a+wB87PvtHDZZy134MljANCuok0cZdheA/238vE0xyFX2/RAENQcBMcqx2z5dRl tXl/h9Hlud10Kvpx78CeNlywsDh78RP8f8Qo0DCboNow1Zl2nw4ejfJM+CbJWb/lCSXF VN8XUojbIXkvvZMMLhk4pRLLduyEqNOX4RYnDlGjpQpABXRqsBqBTav/4ry74Yg8ojkU SLjg==
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=aneJrd9GDXstFPtdN0SMYpsiLbVeAJ0xJm4MPVtWDqA=; b=QH8vWGyPppjiTpAahPTODjyDKWY8egJUvW9p4vyilZefg9XzfKGQFGKym1pHoFFvKL d6btoTBz78Tc/9ZVpbmJ1ookZEMStj5KW/D7w3g3czyqjblQgtOZZjrPoqvtpve4C8Q/ mxBCAgflwnX6Sm7hU8ZxA/mIOwrWpKoZt4DG9I06qxxExZcuX7nItU9XQvtRh3AiyjED UBB5NtvTKmmTmeJ+7c9sas6bcapaiZsNenp/KDDYXwDahg7PXErBRbAWKLFjs/hm679o vc+bHSF/7spRRieGKuy9kRFPOWSM9Um1nQZrfqKWRCwL485Umu16RWjDLNoExLeKOtoh B4FQ==
X-Gm-Message-State: APjAAAU6Le/EAdotz9u7RXHUPK1tcueuL8PCdSEYoV5s7DiXEa8FEbNZ b7y5dSTXZVxM1cfRpnncame+uVjVicDYVpSJbrY=
X-Google-Smtp-Source: APXvYqz59psBMRHn592+KiUnoSRvE7nd6qvHa8RB+HeBlkfawYviSsAawmxWgCiueoebL6euOdVkVwZyGqx1FaT1F68=
X-Received: by 2002:a9d:7d90:: with SMTP id j16mr38137027otn.95.1563578406059; Fri, 19 Jul 2019 16:20:06 -0700 (PDT)
MIME-Version: 1.0
References: <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> <C3D53639-C2C0-42CE-9708-99294091E012@puck.nether.net> <a17a8648-14c8-1889-4ee3-86996ff6281e@gmail.com> <3B0C189A-D56B-430F-82FF-19DE0DC788DE@puck.nether.net> <BA80E73F53C26B9191294131@JcK-HP5.jck.com> <20190719190534.GG38674@shrubbery.net> <4f43fac6-ed7f-08ca-d5da-1e84b0a7b12b@network-heretics.com> <3a678b4a-1c9e-8a2a-ea02-ac32a07f3711@gmail.com>
In-Reply-To: <3a678b4a-1c9e-8a2a-ea02-ac32a07f3711@gmail.com>
From: Job Snijders <job@instituut.net>
Date: Fri, 19 Jul 2019 19:19:54 -0400
Message-ID: <CACWOCC8g_YXT9OU6NxuhFGkxuejxux_ykoKfA7i8cmZ73nWjeg@mail.gmail.com>
Subject: Re: is there a specific proposal for living ops docs?
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Cc: Keith Moore <moore@network-heretics.com>, ietf@ietf.org
Content-Type: multipart/alternative; boundary="00000000000078cbb0058e10f742"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/YrqsUfDRkq3fKY5ih59-zgLeprI>
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 23:20:09 -0000

On Fri, Jul 19, 2019 at 19:17 Brian E Carpenter <brian.e.carpenter@gmail.com>
wrote:

> That's exactly why I asked about RIPE's solution. Before proposing
> a solution, don't we want to study one that apparently works?


Works by what metric?

IETF has take some responsibility for after-care here.

Kind regards,

Job