Re: [Rfced-future] CONCERN positions after RSWG discussion (draft-iab-rfcefdp-rfced-model)

Alvaro Retana <aretana.ietf@gmail.com> Wed, 09 March 2022 22:58 UTC

Return-Path: <aretana.ietf@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 42E093A1169; Wed, 9 Mar 2022 14:58:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.107
X-Spam-Level:
X-Spam-Status: No, score=-1.107 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, FREEMAIL_REPLY=1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, UNPARSEABLE_RELAY=0.001] autolearn=no 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 Ps21R29eJnY4; Wed, 9 Mar 2022 14:58:22 -0800 (PST)
Received: from mail-ej1-x632.google.com (mail-ej1-x632.google.com [IPv6:2a00:1450:4864:20::632]) (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 D369F3A1130; Wed, 9 Mar 2022 14:58:21 -0800 (PST)
Received: by mail-ej1-x632.google.com with SMTP id d10so8278487eje.10; Wed, 09 Mar 2022 14:58:21 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=from:in-reply-to:references:mime-version:date:message-id:subject:to :cc; bh=deuc8jjmnzMwb3o2wuoGZfPUTtsX3EW+wyMt5eBwG/s=; b=gOib9Z6QBedSGjqMXgsOXSbCBaajTEv+bHm2mDq8iHDKdrfwf2f4wTGNj9c/Y9q4zg yZOAMmzSG08W5pFhD2gWjIbR/qxSlIMDUublssbJExgIHED3ZLI6yQhU7O2qJWeKBX08 daEW3EPMUOH3z0PKm1HqOT7Mvp13s4uzpubq8hyIAwUPXIsCbHqr2zHJKr2wKd1uJv3P JwLZOk1nh4opJC88++21ZpK2jWoeiW8SOExn3sGfy8DPpugLLIUL+ZmhVLJJHurjIFvG 78tPzcv3k9nfrdpN4eA3PxA6m/DzxQ2lRzYhQO0IqAuTXNGSFgR69WA5TFdSxe9EreB+ pUuw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:from:in-reply-to:references:mime-version:date :message-id:subject:to:cc; bh=deuc8jjmnzMwb3o2wuoGZfPUTtsX3EW+wyMt5eBwG/s=; b=hBQDRCzgbnU76pCTTd8OiopKZToq0RLEYwOnXn1DCWgfMjM/thSoWnWV+XnK2sejUZ 5nxh0KQVCAdmg9QDZUWJJDaTeAkq+34lSv+aUD5NKv6kkwuLXSAZElYGY/byewM3+UmM Y9kKb1Na5OZ3Pia3ewyQnSfooL9I3clwaOAHpRWedTG/NjRU54eYiWnOc0IupiMdwpTR 6S59xTlkiTfCgdpLbGhIdNUWUEwH2WbMVOf9PbvyOOJHdGq5PSuP5bnmzgkMCMxUyNfL Ywa0Cg93Ocr80jAEuXi212pmsq+WRP02GB0aiPKbQR5xj9VgeeA8FJXfwlH5f5n2oe8X 1cPA==
X-Gm-Message-State: AOAM533cCX3slzA1pYqql4AVh3HaycBgE75JR4lUxQL1al55AnJLVL43 IP1q3gfLMqXL2/ZlsnOADDB3/V4nYVddWhwPZNFJxRLu
X-Google-Smtp-Source: ABdhPJyjv6ykkC6p9pfMLh3RBPgsNlyBKDUNrfN7CgQFfCDnNNwq0sbcEu0y3YIQbzw+JDHjL8Sv9qy+H/0VqhZhp5Y=
X-Received: by 2002:a17:907:7e96:b0:6da:f7ee:4a25 with SMTP id qb22-20020a1709077e9600b006daf7ee4a25mr1849233ejc.436.1646866699959; Wed, 09 Mar 2022 14:58:19 -0800 (PST)
Received: from 1058052472880 named unknown by gmailapi.google.com with HTTPREST; Wed, 9 Mar 2022 14:58:19 -0800
From: Alvaro Retana <aretana.ietf@gmail.com>
In-Reply-To: <197f0d67-28a5-c800-65bf-9d8c039b5978@gmail.com>
References: <CAMMESsyaoHCgz8SqWa6NH1A49dGNLkJ_CwqoKedxL8cBGpv99w@mail.gmail.com> <CABcZeBNBf46i6SS2wgk1kdUD5WVrhe3BdTz_Zs2eFig4nODikg@mail.gmail.com> <CAMMESsyBYWXgJwUSqUofh9q7r3FnyBGJFjHOoEtZXjkBmfUsLw@mail.gmail.com> <1f7f1977-3106-77f2-1be5-df514181c7be@joelhalpern.com> <197f0d67-28a5-c800-65bf-9d8c039b5978@gmail.com>
MIME-Version: 1.0
Date: Wed, 09 Mar 2022 14:58:19 -0800
Message-ID: <CAMMESsxfKXUQryWO1UxGmWp2UqD3MKK3YEBZp3bFKL5g-gQq3A@mail.gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, "Joel M. Halpern" <jmh@joelhalpern.com>
Cc: The IAB <iab@iab.org>, The IESG <iesg@ietf.org>, rfced-future@iab.org
Content-Type: multipart/alternative; boundary="000000000000a4c0be05d9d108d4"
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfced-future/mi0iGSqwlXX2T-pO3XoKcffmJko>
Subject: Re: [Rfced-future] CONCERN positions after RSWG discussion (draft-iab-rfcefdp-rfced-model)
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: Wed, 09 Mar 2022 22:58:28 -0000

Thanks Brian -- you explained it better than I did. :-)

Yes, I was trying to avoid a possible deadlock from raising an issue to the
RSWG, not liking the result of the discussion, and bringing it up again as
a CONCERN.

It seems that everyone considers this case already covered.

Thanks for the discussion.

Alvaro.

On March 9, 2022 at 4:38:11 PM, Brian E Carpenter (
brian.e.carpenter@gmail.com) wrote:

I think there's an analogy here with the history of DISCUSS.

Once, there was no such thing as the IESG "DISCUSS criteria" document,
and occasionally ADs would use a DISCUSS to attempt to override
WG consensus because they personally disagreed. This could lead to a
deadlock and was viewed as an abuse of process. Hence, we got the
DISCUSS criteria.

I may be wrong, but I think Alvaro is trying to avoid the same
thing here. But I also think that the CONCERN rules in the draft
already provide criteria ("three reasons why an RSAB member may
file a position of CONCERN") and an override ("If at least three
voting members vote YES, the proposal is approved"). So for me,
we've already covered this.

Regards
Brian Carpenter