Re: [ietf-smtp] Proposed agenda for EMAILCORE BOF

Dave Crocker <dhc@dcrocker.net> Wed, 22 July 2020 12:27 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 [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8BA9E3A0AEA for <ietf-smtp@ietfa.amsl.com>; Wed, 22 Jul 2020 05:27:14 -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, NICE_REPLY_A=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 JUM5d0sbi3pF for <ietf-smtp@ietfa.amsl.com>; Wed, 22 Jul 2020 05:27:11 -0700 (PDT)
Received: from simon.songbird.com (simon.songbird.com [72.52.113.5]) (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 83FC03A0B20 for <ietf-smtp@ietf.org>; Wed, 22 Jul 2020 05:27:11 -0700 (PDT)
Received: from [192.168.1.67] (108-226-162-63.lightspeed.sntcca.sbcglobal.net [108.226.162.63]) (authenticated bits=0) by simon.songbird.com (8.14.4/8.14.4/Debian-4.1ubuntu1.1) with ESMTP id 06MCTihp019715 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Wed, 22 Jul 2020 05:29:44 -0700
Reply-To: dcrocker@bbiw.net
To: Alexey Melnikov <alexey.melnikov@isode.com>, ietf-smtp@ietf.org
Cc: Seth Blank <seth@valimail.com>
References: <579f408c-ed7e-9dbe-f626-f0dab2380d13@isode.com>
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
Message-ID: <3b8e5d41-1b61-ca9e-f257-792d3d0f0f6e@dcrocker.net>
Date: Wed, 22 Jul 2020 05:27:03 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.10.0
MIME-Version: 1.0
In-Reply-To: <579f408c-ed7e-9dbe-f626-f0dab2380d13@isode.com>
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/ax73_9AT-tE-2jpke1_-8F4dZBs>
Subject: Re: [ietf-smtp] Proposed agenda for EMAILCORE BOF
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 12:27:15 -0000

On 7/22/2020 4:49 AM, Alexey Melnikov wrote:
> Core Email Applicability Statement: - 35 mins


More time is budgeted for this than for charter discussion.

Applicability Statements have long been popular in the IETF.  They are 
an obviously good idea.

Less obvious is whether they are worth the effort.

Who uses them and what is the evidence they are worth the effort?

d/

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net