Re: Proposed IESG Statement on the use of the “Updates” header

Julian Reschke <julian.reschke@gmx.de> Wed, 12 September 2018 15:23 UTC

Return-Path: <julian.reschke@gmx.de>
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 64953130F99; Wed, 12 Sep 2018 08:23:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 v3mELV8uWJVn; Wed, 12 Sep 2018 08:23:20 -0700 (PDT)
Received: from mout.gmx.net (mout.gmx.net [212.227.15.18]) (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 C9C99130F03; Wed, 12 Sep 2018 08:23:19 -0700 (PDT)
Received: from [192.168.178.20] ([84.171.150.162]) by mail.gmx.com (mrgmx003 [212.227.17.190]) with ESMTPSA (Nemesis) id 0MZkNy-1gHDKd0lZO-00LWT1; Wed, 12 Sep 2018 17:23:17 +0200
Subject: =?UTF-8?Q?Re=3a_Proposed_IESG_Statement_on_the_use_of_the_=e2=80=9c?= =?UTF-8?Q?Updates=e2=80=9d_header?=
To: Paul Hoffman <paul.hoffman@vpnc.org>, ietf@ietf.org, The IESG <iesg@ietf.org>
References: <59F6DED7-8D39-4206-8268-22AB6A99A876@nostrum.com> <8DA3AA49-BB06-4DA6-A028-F487FC9822EB@sn3rd.com> <AFE1600A-7883-4CD6-BD6A-232E12514123@vpnc.org>
From: Julian Reschke <julian.reschke@gmx.de>
Message-ID: <3d9d56cf-a445-c1b8-6944-7502a497942d@gmx.de>
Date: Wed, 12 Sep 2018 17:23:15 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.0
MIME-Version: 1.0
In-Reply-To: <AFE1600A-7883-4CD6-BD6A-232E12514123@vpnc.org>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
X-Provags-ID: V03:K1:Mml6QfN2QvBMFSQ8RksJTPV9CIO/vzqG2gpEoCPgV9yM7NO+iVl YL87VVwpSrJDSTn1tM/obdwb8wNFPYM0SvsmhLy7RJAdk83JQom600ghEk7VOCGd41IR+qK M0A7veB5hyr9Htj6E4kcUNqEpgNR9kxqBLBc+8kT3c3tKyJdmNqDi12vb+TXtV/9zZ9kiU6 5rDmXel4U46o3maa1aHcg==
X-UI-Out-Filterresults: notjunk:1;V01:K0:kiScHHvEwk0=:56o0IPfejlQvpKz3hiL6MD iCJS+sgei5UqMCbSiazYqTXSN2L5mTis6Eq+6opmah95V3rGieKEhj9C2RMS+d6Jqk41zjK0u AiIRTGpddcXJhGFKIuL8EMl3phWt/NdWRkTClrKUSbZzAok40wB9A+xby8edutkcM8yYqBUIQ X1cEbTqA0u97RFKhuA+8qDxM+JSAkszCeyFdV4ID3kXdplD/ArxfwreNk8AVhXg9G/KnpMJ/o iveYsQAaQh+S2Pe0JxfMETc9OoahS9/Z56wgDvg3uTw7c+B0ndlKR3/XlmdL44L8mjspE8I81 lc5sNmvfDe2A1WVmFRLyWOtib//ZW7gsraRF2XlG+cYJhUrQS6Fn0dvcDRbJwuSmnxen/lhSC EbVHo7BImb3RKCZafatG3vAcaIMh0t5wWNYgXnNyYJcZqqMapW0eH5/tcihHdUlyRdJKACosz qZCC7a2pwC4WzP5FuZm3KVZ5dCi7HEdbIYs+33dXg4H/ySyAsqjDoe62pkdSwv8GQ5XpGEq0P 1S6YbQ3n0cmmYNXuRKQYnyNWtuNf/prPfvFzuo9KHMIUvAEZ5KeOYtMnDBnVdg7MTyUOFEds+ SIPkiuLKkvhhnsNL3Mxx8D0BXBL96btjInzBUl8k4oN3hCgdt7++D/ZRf81253Sn5d8vG0iPK B/Fz87itzOYRe3q0PsW5/r3xepeKLbWCLWU5HAwmsv2jkZ6t2IsRHr+CQRvkLoNvEoHRnwxRQ MH8iaPGFkKs9GgK6zQMwIpGgWg2OdN8id/RYK/XhOLlXvGK28TPhhXnqNshca2g0a6UPNpFnR kUOJhODBKMIAgXCeJQWYl20Ez8bQ0v9z6NIHkA1k1oO71TbX/I=
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/MINx87OVXZ9fM4Idh81b7q_Qt7g>
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: Wed, 12 Sep 2018 15:23:26 -0000

On 9/12/2018 4:45 PM, Paul Hoffman wrote:
> ...
> The specific reasons that a given RFC updates another should be 
> described near the top of the Introduction section of the new RFC, 
> possibly in its own sub-section. This text should contain enough detail 
> to help readers who are familiar with the specification that is being 
> updated to decide if they need to read the rest of this newer RFC. This 
> text must contain enough detail for readers to fully understand the 
> nature of the update.
> ...

Yes.

...or maybe move that information into a later section/appendix, and 
refer to that from the introduction.

Best regards, Julian