Re: Status of this memo

Martin Vigoureux <martin.vigoureux@nokia.com> Tue, 27 April 2021 20:08 UTC

Return-Path: <martin.vigoureux@nokia.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 0DD1C3A1E8A for <ietf@ietfa.amsl.com>; Tue, 27 Apr 2021 13:08:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, MSGID_FROM_MTA_HEADER=0.001, NICE_REPLY_A=-0.001, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nokia.onmicrosoft.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 lnvsGA_2gu2D for <ietf@ietfa.amsl.com>; Tue, 27 Apr 2021 13:08:45 -0700 (PDT)
Received: from EUR05-VI1-obe.outbound.protection.outlook.com (mail-vi1eur05on2090.outbound.protection.outlook.com [40.107.21.90]) (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 F171F3A1E85 for <ietf@ietf.org>; Tue, 27 Apr 2021 13:08:44 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=AQhg7OlIvy4RzRLx4FpSVsI9VDDbLCRGwU2HMHqyJDUHJc+NTekoW5FsRJ+GlVsdmuj08GZVRNV9k1foCKy11s37VSR8Da7lpxffOOvBKD9bo+QXiOI8LOUZj15UxJTL2tdcyz+Fd6t6to3OtD769ilwgJ8Z2/O4fpCcYgJ4OrtbxCGM5cZ/op00jj1Ql4PdeFYjAgdaLjpwmNbfw2HJ0jW1qcV7t8vV8rFROb4lMb3NDtCiw9ndUfGfHgzkp4ndEk2rEqyW7jdYqXeic/HncUPlBdoZaX5ICEKYGgSGOoKTPB3zB2i00k9/VvPaZ7WxU42kF1QCJIEafJ1D8mAJdw==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=stMrTviUXC6Hbe70jPajLRCTZQv1EZ4sEXms3zgnKdM=; b=MR3JUghof2j9InXyoCksJoszJpMN8ZjQg4gKH+Ce5tmnYIh6IQ3dtBQLZblfgESmEbtu4r55QcDHGvlQsae1uBEPudxGZSUTZvh/cGUWL4dgJIlhSv78cgSk15dROsWk4X9F3wloUOtAQ89+PkVQ0GZCRBj5OjXLUltZa/oytvXthwjpVsjBmw/UlWrwl2TYm6Xzcu+CZyzEl8T2ldDL6ddZwjzlQmVH+7YlbDaSwruHYMw38Eb7Qwpt1zF6pkaff+NxcLqRSQxEZPto0YEsAItfX39t5HVFZ61kGbkgehmjnNB2nUEjZKDS9rPaDRK71hxSYhnmQ2SB0wbKeCruqA==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=nokia.com; dmarc=pass action=none header.from=nokia.com; dkim=pass header.d=nokia.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nokia.onmicrosoft.com; s=selector1-nokia-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=stMrTviUXC6Hbe70jPajLRCTZQv1EZ4sEXms3zgnKdM=; b=SFvzqzWbDQk9bhXAiQ4QNLkW3ZxPD2QR+SS2Lk1wuY8VPgj2DBSLjmoDVS6/sjslRwtsNttBFiH8EIIpM8Gck/73C49+ce4Q5T7GuYWkd7mHqV/mXMiJVTnrfD53/WTmKLXerbMFvccsgiGXUKzW9KWNr8ednnzLPbdaQY67ZCk=
Authentication-Results: ietf.org; dkim=none (message not signed) header.d=none;ietf.org; dmarc=none action=none header.from=nokia.com;
Received: from AM6PR07MB5560.eurprd07.prod.outlook.com (2603:10a6:20b:6f::22) by AM7PR07MB6931.eurprd07.prod.outlook.com (2603:10a6:20b:1b1::14) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.4087.17; Tue, 27 Apr 2021 20:08:42 +0000
Received: from AM6PR07MB5560.eurprd07.prod.outlook.com ([fe80::6d57:7a33:dd25:1fc1]) by AM6PR07MB5560.eurprd07.prod.outlook.com ([fe80::6d57:7a33:dd25:1fc1%7]) with mapi id 15.20.4087.025; Tue, 27 Apr 2021 20:08:42 +0000
Subject: Re: Status of this memo
To: "Andrew G. Malis" <agmalis@gmail.com>
Cc: IETF Discussion <ietf@ietf.org>
References: <376f83f0-89a3-cd0e-1792-c8434bd8a5d2@gmail.com> <9ACE59FA-30B6-475A-AF6B-4B874E4A2788@eggert.org> <1804294246.5904.1619512137931@appsuite-gw2.open-xchange.com> <D653D3B2-7666-409A-B856-2A4B1BA958CA@eggert.org> <3DBB64B1-40B8-4BC3-B66C-7F9B7F395874@akamai.com> <b5210c71-9500-3dba-05d2-4ae1c6ad16e9@network-heretics.com> <CAA=duU1VJs2vCE=uCF=fXO7FNedn9yPAaZWTgcaAiHTexA8uWA@mail.gmail.com> <2c48c55c-fd37-6ced-e025-707eb145a27b@nokia.com> <CAA=duU1zuZ0ae_fK9vQkkRxFffgitLpATxwNcpfeftepBpY4=w@mail.gmail.com>
From: Martin Vigoureux <martin.vigoureux@nokia.com>
Message-ID: <5e86ed45-e689-4474-a0aa-fa80118ea172@nokia.com>
Date: Tue, 27 Apr 2021 22:07:30 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.5.0
In-Reply-To: <CAA=duU1zuZ0ae_fK9vQkkRxFffgitLpATxwNcpfeftepBpY4=w@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-GB
Content-Transfer-Encoding: 8bit
X-Originating-IP: [131.228.2.21]
X-ClientProxiedBy: CH2PR18CA0056.namprd18.prod.outlook.com (2603:10b6:610:55::36) To AM6PR07MB5560.eurprd07.prod.outlook.com (2603:10a6:20b:6f::22)
MIME-Version: 1.0
X-MS-Exchange-MessageSentRepresentingType: 1
Received: from [172.30.2.231] (131.228.2.21) by CH2PR18CA0056.namprd18.prod.outlook.com (2603:10b6:610:55::36) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.4087.25 via Frontend Transport; Tue, 27 Apr 2021 20:08:40 +0000
X-MS-PublicTrafficType: Email
X-MS-Office365-Filtering-Correlation-Id: bf795235-88d0-4acb-8351-08d909b84165
X-MS-TrafficTypeDiagnostic: AM7PR07MB6931:
X-Microsoft-Antispam-PRVS: <AM7PR07MB693188339BB364C4B999F29E8C419@AM7PR07MB6931.eurprd07.prod.outlook.com>
X-MS-Oob-TLC-OOBClassifiers: OLM:10000;
X-MS-Exchange-SenderADCheck: 1
X-Microsoft-Antispam: BCL:0;
X-Microsoft-Antispam-Message-Info: kTFzL1iBEvi/ETjeJ286tX5ArSvYqOCQ78BaFICXJ7S40UsuqGc9tx15uWKrAhjGer+nVWbJxEzSUwCwWzAtVb/xzqwhk8VoTG/fAxoZ0oUS6YP06PfhUUuuZdy4GR6Ol1ZvuEEZpqJM31s1mS7Jw6grFcYnn8K3iSBkiUaV9BM64dLW+4beQW/fO+vu4HwjtgWZr2/ZbAn6jYAR+82hEVDXkX5ovNyis4RN1FWmpgH9yC8sONffU53EjzZX+BmPI8Ykh82mQcPsZfYlsuoPutqHINwKjwD/Owmwog3mxhDGVXaaP8TpKEx4/IV7+qPKU9AAHY2oFqpcaDMYa7n4FpnGtZa3M82d+QuGRo4jM6u0cVJXWGwVdf1HxzrxAqx6EkmPJciqKoReLjdKeSVIt9iVcfgNfj/CR/wUpHUhcmxldNwnLfnSzEFURU+1NH0AARMTs2pAxCZmqn0MAnzxtCiJSLSF+9vLv7MVZYEOXGexdTK07603bN5VsZ6w/+MC1xUtR9QMvXRmhjTzax21FPjGZCQw13lgTgW8FR4S0LxdLTsGceenbyMH373tQJMKv7L84mOysqF8oWwZzCU0OigRUkrCX/S+KwaREsRFyKbh14vgi8HfKeD4kOX82MnWF+wPfBuJrcZt98v7my+kgD7ds53LgkhzYDzvngRfffz+j05tMfu4FJrcYP93p7yQzKAy5T6T+ylyzni98d/CLFSQ7HYpt6P/orTync4Xjx4=
X-Forefront-Antispam-Report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:AM6PR07MB5560.eurprd07.prod.outlook.com; PTR:; CAT:NONE; SFS:(4636009)(136003)(376002)(366004)(39860400002)(396003)(346002)(16526019)(26005)(186003)(38350700002)(4326008)(66946007)(3480700007)(38100700002)(5660300002)(956004)(66476007)(66556008)(6666004)(31696002)(36756003)(2906002)(83380400001)(66574015)(31686004)(8676002)(2616005)(6916009)(316002)(44832011)(8936002)(16576012)(52116002)(86362001)(6486002)(478600001)(53546011)(45980500001)(43740500002); DIR:OUT; SFP:1102;
X-MS-Exchange-AntiSpam-MessageData: gBlLN/nzyXCsxKsUz6NsA/tHCvUjLqEcya+IQmHd3Cma9TTHyo5xlya45wVgjjoKv9W3a+TMwxM+ZSeiMwPdrQXu/h5uMjKhgYdmUN8UP0qalGpeIPdwa7NN33E2bwXhWhzid4FJ6GfTSNnmZLyXG4+EjBnAXo1kufsCpUycUqbCC5RbubuQMTOY+jpy+fQIrSQbieSldITFQ0pqqx2R5JHhgLHfS5aAcKJEVNKk8rjC3GSDI0LWpnmTJ8vkIK7qbWBCgArMcXzdjMwkpGKnOTdkcoqQvdqhoAN3wV1K7i8YUhEWd5i0jpIlcH/RHLWnz+ZI4XsBWmkRQI1KWYk+2edGFZFBOq9qMqRiRBH4a7G91dP1WqLk4y4za9iZelyXm7q9HmTGMfBiYWPK6QocstwPm6yh6Du1hmBm1f9GTGskruegA/5szHOlGRnFDpsaLKn1IMOZBYZKU/lJAlLiEdXaJfVCqHu5s2jMOjnZFZQAznFY5Jk2KHFcHn2KlSCKP+WTmhU2kgr04av+1gkOK7Sg53x5SYiQkWLgTm5sqhaWHQje6Q2A2AKWXsPwDmQNyZ9BykI0rlYLAFi3fEa+B7eMQn14VM3+T7YHcGSkW+KDQP79bqEnjiPXSSS6hLPzKfNn1+0hHxRQAt3t48eVaoBfxH36O3U8cKov8ZJvCi8nBM+KucyPm28lwq50PmDNYaggjlfUNIyaSt0IHlC7WOQb48x0KPvrr8x9hMbX3/H+Ysu5+MMuETmZXI9+iNuy7OSVX2YihuQgMGRojUxFmKLyl7F1d1MbQEL1Galqna+ReWEBPWkrGBOLyZUq2xOTrlELr9yc1nQVHC2kWDl90pyPQrExKBNnbUvA49Q7GM8mHx3YHMbuC7aw9ADWGrZLX45tYxYzVmpmcnBRg/+EsyNsNq8sRN+JACbxBz0oXIe7Pk4NRy/A51i4h844aZqo7Pub9NaMFQ1cp/u0GyLRuQ5UePW1BH/J/ZxdHWQ+1duNcWTgtRIOXNwYBFiuOnrz6pslS1A+RO7LvJd52mEj0JtgWnZTFhNBcuqKH6iSFvhrfWN7+1T5hrzdhvO9gZ5/zOv0URIC8u2jlIRmOqJdiVK3hImZW2w7bmd2+4xfwxR2PYhxWXDgQ4DX6Q/Y+ibwqM8EiFtRy94LuvtVyY9FMImzOK6TFy5ncDTAzdCN52aNzZtsthhpgVJ6EMowF4+GoGFbl4fcG+3FlISlOlS9CGH60JKTchxClCxdV1xVayfXKbEl4By1oUIHF4Oo/mfrzJ74zbQJYovARsbIunzdMC6nF4SPl2jmkgT7Kys+1VpozDkZLPtMTnhgfPo72Toa
X-OriginatorOrg: nokia.com
X-MS-Exchange-CrossTenant-Network-Message-Id: bf795235-88d0-4acb-8351-08d909b84165
X-MS-Exchange-CrossTenant-AuthSource: AM6PR07MB5560.eurprd07.prod.outlook.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 27 Apr 2021 20:08:42.6779 (UTC)
X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted
X-MS-Exchange-CrossTenant-Id: 5d471751-9675-428d-917b-70f44f9630b0
X-MS-Exchange-CrossTenant-MailboxType: HOSTED
X-MS-Exchange-CrossTenant-UserPrincipalName: 2S4VO7Zc0XCJS3EJRZ3WdvGNmaqk2Y7e1Z6uixj01oRm3FKNLZnav848YGy9bZ2faGYt0fB8VoaJpYcBdEG/bSL1Pl2VwZfzZ0CrNN4vL/Y=
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM7PR07MB6931
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/wUC6ivdjWpZREKH0PDlUY-3lS0w>
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: Tue, 27 Apr 2021 20:08:51 -0000

Thank you Andy

The point I'm trying to get at is:
since "adoption polls" are not an official part of our processes, I 
guess it means WG chairs can adopt a document without running such 
adoption poll, and I sort of remember having seen that at least once.
If that is effectively possible, what are the elements allowing to claim 
that there is WG consensus the day that document becomes 
draft-ietf-<wg>-...?

If I had had to pick a precise moment I would have in fact said 
"Publication Requested" time.

-m

Le 2021-04-27 à 20:08, Andrew G. Malis a écrit :
> Martin,
> 
> A draft reflects WG consensus when it has the name draft-ietf-wg-.... 
> (that's the definition of that name). Before then, it's just a proposal 
> from one or more individuals.
> 
> It's the document editor and WG chair's jobs to make sure that WG drafts 
> do in fact reflect WG status. If a WG participant disagrees with the 
> editor and the chair that the draft reflects WG consensus, they can 
> appeal to an AD or the IESG as a whole.
> 
> This is from RFC 2418:
> 
> 6.3. Document Editor
> 
>     Most IETF working groups focus their efforts on a document, or set of
>     documents, that capture the results of the group's work.  A working
>     group generally designates a person or persons to serve as the Editor
>     for a particular document.  The Document Editor is responsible for
>     ensuring that the contents of the document accurately reflect the
>     decisions that have been made by the working group.
> 
>     As a general practice, the Working Group Chair and Document Editor
>     positions are filled by different individuals to help ensure that the
>     resulting documents accurately reflect the consensus of the working
>     group and that all processes are followed.
> 
> Cheers,
> Andy
> 
> 
> On Tue, Apr 27, 2021 at 12:07 PM Martin Vigoureux 
> <martin.vigoureux@nokia.com <mailto:martin.vigoureux@nokia.com>> wrote:
> 
>     Andy,
> 
>     quick question, if I may:
> 
>     Le 2021-04-27 à 17:06, Andrew G. Malis a écrit :
>      > Keith,
>      >
>      > I disagree. WGs have charters, which result in RFCs. During that
>      > process, they have consensus-based working drafts that are
>     refined to
>      > meet their charter goals. That's an "adopted" draft. But it
>     doesn't have
>      > to be based on a single individual draft, a working draft can be the
>      > result of merging earlier individual drafts, or can even
>     originate as a
>      > WG draft without a preceding individual draft or drafts. But yes,
>      > working drafts do reflect WG consensus, and they have formal
>     standing as
>      > such.
>     At which point in time to do they reflect WG consensus, according to
>     you?
>     As examples to illustrate my ask: From day 1 or only at "Publication
>     Requested" time, or some other time, if any specific one?
> 
>     -m
> 
> 
>      >
>      > Cheers,
>      > Andy
>      >
>      >
>      > On Tue, Apr 27, 2021 at 10:27 AM Keith Moore
>     <moore@network-heretics.com <mailto:moore@network-heretics.com>
>      > <mailto:moore@network-heretics.com
>     <mailto:moore@network-heretics.com>>> wrote:
>      >
>      >     On 4/27/21 10:17 AM, Salz, Rich wrote:
>      >
>      >>>         There was also a suggestion to add something to the
>     boilerplate text of individual I-Ds along the lines of "anyone can
>     submit an I-D; they have no formal standing until they are adopted
>     by a group in the IETF or IRTF". Would that provide additional
>     clarification?
>      >>     Oh yes, PLEASE!
>      >
>      >     concur.   Except get rid of the "adopted" bit, because even
>     assuming
>      >     that "adoption" of a draft by a WG is useful, it doesn't
>     imply any
>      >     kind of broad support from the organization.   Just say that the
>      >     existence of a draft does not mean it has any formal standing
>     with
>      >     IETF or any other organization.   Documents with formal
>     standing in
>      >     IETF are published as RFCs.
>      >
>      >     Keith
>      >
>      >
>