IETF Logo Mail Archive

Re: [Rfced-future] Consensus check: Issue 22 – new stream for RFC Editor

Bob Hinden <bob.hinden@gmail.com> Fri, 25 June 2021 17:37 UTC

Return-Path: <bob.hinden@gmail.com>
X-Original-To: rfced-future@ietfa.amsl.com
Delivered-To: rfced-future@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ACA693A0D03 for <rfced-future@ietfa.amsl.com>; Fri, 25 Jun 2021 10:37:40 -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, RCVD_IN_DNSWL_BLOCKED=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 pL9-sETR4xRp for <rfced-future@ietfa.amsl.com>; Fri, 25 Jun 2021 10:37:36 -0700 (PDT)
Received: from mail-wm1-x32a.google.com (mail-wm1-x32a.google.com [IPv6:2a00:1450:4864:20::32a]) (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 005EB3A0D01 for <rfced-future@iab.org>; Fri, 25 Jun 2021 10:37:35 -0700 (PDT)
Received: by mail-wm1-x32a.google.com with SMTP id u5-20020a7bc0450000b02901480e40338bso6780299wmc.1 for <rfced-future@iab.org>; Fri, 25 Jun 2021 10:37:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=JzarHP8BMBrg1+ZfuSIWDyVfq5zrlb9nJrFfOYWkRVU=; b=ogaAE9ywD99XQobw4Avwwaye6rQFyPgrO38HZTtQhxnvGO9/tOO9uWYyNzklCUp4q6 sVuQeRAJu56MmnXi8UYFhXjuOeL0kcPULXCdzevEY3L3/Qli9ZpGfJrujanj2A/qpkg6 iRTm1ovLZX278YcGCi53FXlbn9R0s3n9wi8l6fkYPAdWVzqoPlZdkwpHIlhbXA+vlRC7 gWMlRgNKskCmWIXNlBVu964AjFjqMCzZigH9JUthgf4caeRJT9hNNX6hAqot+URYL0VL KsoUNpula7aHU//SUe8E+2b9hTHMCtkrIfiAaW+bm4q5hP1yXDJdmVV0BrYiK9eXQb97 tv4w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=JzarHP8BMBrg1+ZfuSIWDyVfq5zrlb9nJrFfOYWkRVU=; b=ETlUPlyN1d9tKaw9WP3i+sQiWCsfWlcIQ9qWz4GfBHxmrOm68CCA5Dip7o7Inahp1K ifpG1nUa1Tq3g4DjdSRXbjaEWkBpxY/EHcDvMAqhqN52mRJpKWbv62782oL3XoThxCaL KsEMGunwpdHMuXCyocTRGyfRH4493aqf61tAqYQVH2GSHdCr4v8LPyQuzi9sJE1DolMI o8B0MzjicB/u2Bdyy00rRM7PTLHinCCWrtl76q6ijOMegh4x9odjH7ylM3GkkRv+inZz H42Pkrc6+Jk1ZL8ObgvaBCiWN/NL24zicE7+rSnDmWuKU4SIwGRljD73lGNm10svUhDj Mh5w==
X-Gm-Message-State: AOAM5312ShEA5/52ydtS01sKq4o3r+9bybTrxMGKM+Y+V/WgKAhk9qNE S4qxMFDt4y2o/Q74ZTYui7M=
X-Google-Smtp-Source: ABdhPJyE0b/N1//AwzGfUpUVDwXudw9a2AM/0adSLN91NGVnpV3pFnXDpdlbpIGQLPX+vCR3wvSgMg==
X-Received: by 2002:a05:600c:608:: with SMTP id o8mr11914445wmm.98.1624642652795; Fri, 25 Jun 2021 10:37:32 -0700 (PDT)
Received: from [10.0.0.199] (c-24-5-53-184.hsd1.ca.comcast.net. [24.5.53.184]) by smtp.gmail.com with ESMTPSA id h15sm6570989wrq.88.2021.06.25.10.37.31 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Fri, 25 Jun 2021 10:37:32 -0700 (PDT)
From: Bob Hinden <bob.hinden@gmail.com>
Message-Id: <A9E7C98E-F47C-4C28-BDC9-23941203516F@gmail.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_1869BFA5-4381-41F7-8A4A-CE18928C3151"; protocol="application/pgp-signature"; micalg="pgp-sha512"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.21\))
Date: Fri, 25 Jun 2021 10:37:29 -0700
In-Reply-To: <476493c2-e434-0451-beaf-29a59be15aa3@joelhalpern.com>
Cc: Bob Hinden <bob.hinden@gmail.com>, rfced-future@iab.org
To: "Joel M. Halpern" <jmh@joelhalpern.com>
References: <3f4c264e-4639-4d6b-cf22-0a2be503decc@joelhalpern.com> <3D3EC062-7B1A-43C4-99D5-A204A4565ECE@ietf.org> <cf2921d8-fd1f-d9c9-da72-ff760eda347c@lear.ch> <3b4b6d91-64e3-d0d7-bcbc-284f29a46fb7@joelhalpern.com> <9fdeb823-9470-00a8-b1b1-91630b996c8c@gmail.com> <351774DB-C6DC-439F-9B5C-FB427EC9F6FE@ietf.org> <ac1aea74-da8e-405d-2a73-fbc6fc97ce24@gmail.com> <D1D7247E-6F03-475A-88F4-50E45A8B6F0E@eggert.org> <ec86e68e-961a-2c1a-fb9a-0ba8be20c524@huitema.net> <476493c2-e434-0451-beaf-29a59be15aa3@joelhalpern.com>
X-Mailer: Apple Mail (2.3445.104.21)
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfced-future/oUrAU_1eQ02aYuN9kHjQyQk_1kQ>
Subject: Re: [Rfced-future] Consensus check: Issue 22 – new stream for RFC Editor
X-BeenThere: rfced-future@iab.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: RFC Editor Future Development Program <rfced-future.iab.org>
List-Unsubscribe: <https://www.iab.org/mailman/options/rfced-future>, <mailto:rfced-future-request@iab.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rfced-future/>
List-Post: <mailto:rfced-future@iab.org>
List-Help: <mailto:rfced-future-request@iab.org?subject=help>
List-Subscribe: <https://www.iab.org/mailman/listinfo/rfced-future>, <mailto:rfced-future-request@iab.org?subject=subscribe>
X-List-Received-Date: Fri, 25 Jun 2021 17:37:41 -0000


> On Jun 25, 2021, at 10:19 AM, Joel M. Halpern <jmh@joelhalpern.com> wrote:
> 
> If the IAB retains the right to rewrite or refuse the documents from this process, then I do not see what we have accomplished with this entire circus ???

+1

Bob


> 
> Yours,
> Joel
> 
> On 6/25/2021 1:16 PM, Christian Huitema wrote:
>> On 6/24/2021 1:46 AM, Lars Eggert wrote:
>>> Hi,
>>> 
>>> On 2021-6-24, at 7:57, Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:
>>>> As somebody else said, this stream by its very nature is going to be special and even self-referential. The notion we have of a stream being a client of the RFC Series just doesn't apply, so the normal notion of a stream manager doesn't apply**. But surely we need someone to act as progress chaser and nit resolver when a document has left the RSAB and is inside the RPC? And who will that be if it's not the RSEA?
>>> I still remain unconvinced that we even need a new stream. I may be in the rough, but I would be OK with using the IAB stream and leaving the IAB a role here.
>> +1. That seems a much simpler solution than creating yet another rarely used structure.
>> -- Christian Huitema
> 
> --
> Rfced-future mailing list
> Rfced-future@iab.org
> https://www.iab.org/mailman/listinfo/rfced-future

v2.23.0 | Report a Bug | By Email