[ietf-smtp] Template for Additional Work Items

Dave Crocker <dhc@dcrocker.net> Wed, 22 July 2020 19:04 UTC

Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf-smtp@ietfa.amsl.com
Delivered-To: ietf-smtp@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id ECA623A03EA for <ietf-smtp@ietfa.amsl.com>; Wed, 22 Jul 2020 12:04:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id nGZ7lmnAcb85 for <ietf-smtp@ietfa.amsl.com>; Wed, 22 Jul 2020 12:04:45 -0700 (PDT)
Received: from simon.songbird.com (simon.songbird.com []) (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 E8ED03A003C for <ietf-smtp@ietf.org>; Wed, 22 Jul 2020 12:04:45 -0700 (PDT)
Received: from [] (108-226-162-63.lightspeed.sntcca.sbcglobal.net []) (authenticated bits=0) by simon.songbird.com (8.14.4/8.14.4/Debian-4.1ubuntu1.1) with ESMTP id 06MJ7IAH027449 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT) for <ietf-smtp@ietf.org>; Wed, 22 Jul 2020 12:07:19 -0700
Reply-To: dcrocker@bbiw.net
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
To: ietf-smtp <ietf-smtp@ietf.org>
Message-ID: <0c1d7b5e-202a-7451-95fb-ebdf6c0a7d40@dcrocker.net>
Date: Wed, 22 Jul 2020 12:04:40 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.10.0
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-smtp/RuQTq9V-ck112W0NzYsqiLnfrTk>
Subject: [ietf-smtp] Template for Additional Work Items
X-BeenThere: ietf-smtp@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Discussion of issues related to Simple Mail Transfer Protocol \(SMTP\) \[RFC 821, RFC 2821, RFC 5321\]" <ietf-smtp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-smtp>, <mailto:ietf-smtp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-smtp/>
List-Post: <mailto:ietf-smtp@ietf.org>
List-Help: <mailto:ietf-smtp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-smtp>, <mailto:ietf-smtp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Jul 2020 19:04:49 -0000

By way of trying to focus and facilitate emailcore efforts, perhaps we 
could use a simple template, when suggesting addition of an item to the 
topics/tasks list.

Anything in the regular errata database is an 'existing' item.  The 
issue is for items introduced on the mailing list.

I suggest...

Item:        { Reference-name }

Issue:       { Concise description of problem, concern, or the like }

Effect:      { What significant effect(s) is this issue producing? }

Validation:  { Document the basis for the claimed effect }

Dave Crocker
Brandenburg InternetWorking