IETF Logo Mail Archive

Re: [Last-Call] Last Call: <draft-halpern-gendispatch-consensusinformational-02.txt> (IETF Stream Documents Require IETF Rough Consensus) to Best Current Practice

Brian E Carpenter <brian.e.carpenter@gmail.com> Fri, 24 January 2020 21:53 UTC

Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: last-call@ietfa.amsl.com
Delivered-To: last-call@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5BE56120A01; Fri, 24 Jan 2020 13:53:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-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 n1cHMka-dXNM; Fri, 24 Jan 2020 13:53:28 -0800 (PST)
Received: from mail-pf1-x429.google.com (mail-pf1-x429.google.com [IPv6:2607:f8b0:4864:20::429]) (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 9FC911209FD; Fri, 24 Jan 2020 13:53:28 -0800 (PST)
Received: by mail-pf1-x429.google.com with SMTP id 4so1738331pfz.9; Fri, 24 Jan 2020 13:53:28 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=pAtgabtS3niAWrSlYJzMWtUKr1R/CBAknebnrXN6GYQ=; b=lSzjsrIrDd5cPjC2tMu8jHwUjqgjO9rldwbOkS7FX3Nmz3/MuzBkmPsm0chkgP93ev nNEMCSelEi7EpLdmFahp/+GrSmh9CaGxfR/RWViROB6bRyziO4apP3R84fLxXM+s/Y4a gOcvrLlMdk46A61pe+jPhK5GIHpDfKnAMfuyoyCKzxDL2dBYZFfPre7sdvjbVyWk32sz QQ0lRAhV9cR9/E/aCyPJaAaUPfklPeyAHvCDob8BLmQxtSLHzXgNpxhDS4cSYPV/GC4I Vr04Ym7qZFbBYwsGFbfhMrK+E0G4eh0rWLktMjzbmmD55ysOy5UrugjMl1aEmQPMJFTb kBcw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=pAtgabtS3niAWrSlYJzMWtUKr1R/CBAknebnrXN6GYQ=; b=e0oxMF3/xckseey2IR2yp39Nt8Dz6c4cqegLxSp54iv91y9J0sqYaueX77C3y+aG87 YHbiAyueNRgKSaRnQhsO3EFpt84w7qU+E9H1wz2QZsf1/gCJ8K7LwoXXzcAok9A8kn9Y J7UQ7jw5VkSQzd8nKo6b6B+yIc41XkXE8hMVYqGlDUP6Qw6b2vTx29kRWK+pM6x18tKs RBBKnU4TssvnawfqFb842vAAsOaFZBeXM1ekDfOJx5LE9ygA2Z0qc/6LJlDR0Cysnp72 MTCxyraHUaiSyWPsOU+CBsv2HO/j0+bv635JhBewXqnY+Z5+adTu5stelQf/KrX4D0RN f57g==
X-Gm-Message-State: APjAAAVhehw6LJtJTt1wK/9qf9bPjXzbEVB1G36k6jC91Xjyk2eIssvZ Tt02EWLN+/1ZcRtNmJIrnepW4Z29
X-Google-Smtp-Source: APXvYqxytegRAwoKXeDFz9L9zD1NjBNXnDTU9JVhhsXtqF74n0z4kVRIfNBlk2/lqYdwXSU3qgHLSg==
X-Received: by 2002:a62:8249:: with SMTP id w70mr4927935pfd.253.1579902807679; Fri, 24 Jan 2020 13:53:27 -0800 (PST)
Received: from [192.168.178.30] (88.161.69.111.dynamic.snap.net.nz. [111.69.161.88]) by smtp.gmail.com with ESMTPSA id i4sm7541521pgc.51.2020.01.24.13.53.25 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 24 Jan 2020 13:53:27 -0800 (PST)
To: last-call@ietf.org
Cc: draft-halpern-gendispatch-consensusinformational@ietf.org
References: <157988932717.22102.17207308469919846350.idtracker@ietfa.amsl.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <93d22cac-a01c-e463-c760-4ea1c3135643@gmail.com>
Date: Sat, 25 Jan 2020 10:11:51 +1300
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.9.1
MIME-Version: 1.0
In-Reply-To: <157988932717.22102.17207308469919846350.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset="utf-8"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/last-call/QSu6Rt9ga_MwCzrXayw2_ZF7Iv4>
Subject: Re: [Last-Call] Last Call: <draft-halpern-gendispatch-consensusinformational-02.txt> (IETF Stream Documents Require IETF Rough Consensus) to Best Current Practice
X-BeenThere: last-call@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF Last Calls <last-call.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/last-call>, <mailto:last-call-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/last-call/>
List-Post: <mailto:last-call@ietf.org>
List-Help: <mailto:last-call-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/last-call>, <mailto:last-call-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Jan 2020 21:53:30 -0000

Friendly amendment:

> This document introduces no new security considerations. It is a process document about changes to the rules for certain corner cases in publishing IETF stream RFCs.

It seems to me that this document will potentially improve security. You could add:

However, it will prevent publication of IETF stream documents that have not reached rough consensus about their security aspects.

Nit:

Please be consistent about "stream" vs "Stream". For example,

>  ...namely the Independent Stream. Or, for research documents, the IRTF stream

is inconsistent.

Regards
   Brian Carpenter

On 25-Jan-20 07:08, The IESG wrote:
> 
> The IESG has received a request from an individual submitter to consider the
> following document: - 'IETF Stream Documents Require IETF Rough Consensus'
>   <draft-halpern-gendispatch-consensusinformational-02.txt> as Best Current
>   Practice
> 
> The IESG plans to make a decision in the next few weeks, and solicits final
> comments on this action. Please send substantive comments to the
> last-call@ietf.org mailing lists by 2020-02-21. Exceptionally, comments may
> be sent to iesg@ietf.org instead. In either case, please retain the beginning
> of the Subject line to allow automated sorting.
> 
> Abstract
> 
> 
>    This document proposes that the IETF never publish any IETF stream
>    RFCs without IETF rough consensus.  This updates RFC 2026.
> 
> 
> 
> 
> The file can be obtained via
> https://datatracker.ietf.org/doc/draft-halpern-gendispatch-consensusinformational/
> 
> IESG discussion can be tracked via
> https://datatracker.ietf.org/doc/draft-halpern-gendispatch-consensusinformational/ballot/
> 
> 
> No IPR declarations have been submitted directly on this I-D.
> 
> 
> 
> 
> _______________________________________________
> IETF-Announce mailing list
> IETF-Announce@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf-announce
>

v2.23.0 | Report a Bug | By Email