IETF Logo Mail Archive

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

Hans Petter Holen <hph@oslo.net> Sat, 20 July 2019 20:13 UTC

Return-Path: <hph@oslo.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 1E1D0120048 for <ietf@ietfa.amsl.com>; Sat, 20 Jul 2019 13:13:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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=oslo.net
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 vsN6twfGNrxz for <ietf@ietfa.amsl.com>; Sat, 20 Jul 2019 13:13:17 -0700 (PDT)
Received: from mail-wr1-x42c.google.com (mail-wr1-x42c.google.com [IPv6:2a00:1450:4864:20::42c]) (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 EAA12120045 for <ietf@ietf.org>; Sat, 20 Jul 2019 13:13:16 -0700 (PDT)
Received: by mail-wr1-x42c.google.com with SMTP id n9so10363550wrr.4 for <ietf@ietf.org>; Sat, 20 Jul 2019 13:13:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=oslo.net; s=google; h=mime-version:references:in-reply-to:reply-to:from:date:message-id :subject:to:cc; bh=hdwGo+u1QnB1JZJO4TjHSE0LcM0tzRyHZlFynqqhaxY=; b=FxOC3ecCzO4KfISUJkdjDTWhvKeU9QYxiRLAOgCmxV9gUDihm1rYCcaI0ZSs/rZzvR HTfm7e8+bhoyjY7u6rZyoBwYhwF8KAIs80Ty9jGrq+IgBxAKMHRGFCv8ib8rJp9VIvSo wFwOlaKdg1590UEc3cswmruUoaB5YNo4eVNzLRVjDwVN8IMo5X0vJhBGp7QEUs8MwvkG QNGjYsJVcMUfTv6Q9uixsk2Qu1uaQXBzNsSTEbocIzOtlxGEguobY1QZFSeQ+dUAPCmq LuPFAjopq8MiM1/QoIsMgGY4CNzZvwdSTqtlUxys6NspCa1FzsLv91GQb7nfm9XNzKVi EcwQ==
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:reply-to :from:date:message-id:subject:to:cc; bh=hdwGo+u1QnB1JZJO4TjHSE0LcM0tzRyHZlFynqqhaxY=; b=NsLxzDjHXARvAWMHeH7U67Zb040++N7XyyThGylbxRqAx86M/urB7m5hVzb0V23Hcr EJtPXmZDE1mKfhRHNWIZ4vbIus0LvnKNbu60isHr4W9U9GwWpEKYp4ET/dUYUyavvENN sDjAp3UuYzCba9glLlN1jd4KnARn5PUbneCncyYHLNOaPd+21yU5ZUI/mCHZVgOq7jy6 pH+gdD0BOHWwT7MGjbcbo9PyQT4gn49wPGWOWv8nmRsMeNakwUtwcSVoh4yg4XvoNytA vecb7TELqW11wblRG4Hyg84rUtNB6Gcb6k6n3cXbvSwLaC81cz5ogkqPHp7hDbIzGn+H +hJQ==
X-Gm-Message-State: APjAAAUTyx/buP5C1NMnCQPzp1kEklvf8XyV41q6LnCXh2Piouu/Lurw mfS4xwKKGyVYWYdGz3CB4mTetO4IHYDhq7gu3/ZJXg==
X-Google-Smtp-Source: APXvYqwz1DxW494mFRntUTruam+K2q/xZFLhg1+VUINtRx1qOPrv8zxzMdDZ7yylM+TfhS46mvX35VfWptFVyS1H0+E=
X-Received: by 2002:adf:eb0f:: with SMTP id s15mr3914747wrn.324.1563653595022; Sat, 20 Jul 2019 13:13:15 -0700 (PDT)
MIME-Version: 1.0
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> <C3D53639-C2C0-42CE-9708-99294091E012@puck.nether.net> <a17a8648-14c8-1889-4ee3-86996ff6281e@gmail.com>
In-Reply-To: <a17a8648-14c8-1889-4ee3-86996ff6281e@gmail.com>
Reply-To: hph@oslo.net
From: Hans Petter Holen <hph@oslo.net>
Date: Sat, 20 Jul 2019 16:13:04 -0400
Message-ID: <CAJPAtr3MFzRO0FuCmGO3Wwhq2CwAr1tdikiKJXv1G-eUdnYCig@mail.gmail.com>
Subject: Re: Evolving Documents (nee "Living Documents") side meeting at IETF105.)
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Cc: Jared Mauch <jared@puck.nether.net>, ietf@ietf.org
Content-Type: multipart/alternative; boundary="000000000000155d4a058e227911"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/2hkRhIwY3wiObmS6NW_hL5lwkM8>
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: Sat, 20 Jul 2019 20:13:20 -0000

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

> Yes but I want a standard for comparison: how long does RIPE take? I have
> never been involved in that side of RIPE, so I have no idea whether they
> manage it in weeks, months or years. What is a realistic target?


For _policy proposals_ there is a well defined process described in RIPE 710
https://www.ripe.net/publications/docs/ripe-710

Which would take you a minmimum of 20ish weeks.

BCPs are not bound by this process, so it is hard to give an accurate
answer.

We just had a discussion last week that we really should write down the
process for developing and publising RIPE documents in general.

Hans Petter Holen
RIPE Chair

>
-- 
-- Hans Petter Holen Mobile +47 45 06 60 54 | hph@oslo.net |
http://hph.oslo.net

v2.23.0 | Report a Bug | By Email