IETF Logo Mail Archive

Re: [Last-Call] Last Call: <draft-billon-expires-06.txt> (Updated Use of the Expires Message Header Field) to Proposed Standard

Alexey Melnikov <alexey.melnikov@isode.com> Tue, 29 November 2022 18:03 UTC

Return-Path: <alexey.melnikov@isode.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 3BE52C14CEFC; Tue, 29 Nov 2022 10:03:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, NICE_REPLY_A=-0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=isode.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RsjeaoYfaBlB; Tue, 29 Nov 2022 10:03:43 -0800 (PST)
Received: from statler.isode.com (Statler.isode.com [62.232.206.189]) by ietfa.amsl.com (Postfix) with ESMTP id 1765FC14F73D; Tue, 29 Nov 2022 10:03:43 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1669745021; d=isode.com; s=june2016; i=@isode.com; bh=mETBI4lZzfiXfrWhFEoHSik7jVdbWbPtmCeakDMP48g=; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:Cc:MIME-Version: In-Reply-To:References:Content-Type:Content-Transfer-Encoding: Content-ID:Content-Description; b=Dc6QsCN/1B8hnoNbCc9YIBgkqE5MMttanmHrnvRZPOO6XtcMiCOUw7ePb0cYeam7cjl3G+ 05zDFjhE11/+6XSlhgAK+0t8Ej3mIRGnjnsH+ev6/hSqwcMMD1OTsebtZodNqESfH4CgIy +nZl8t8v9AtdgMOI6z50eCd/9jFRrGE=;
Received: from [192.168.1.222] (host31-49-219-106.range31-49.btcentralplus.com [31.49.219.106]) by statler.isode.com (submission channel) via TCP with ESMTPSA id <Y4ZJegAPgZpq@statler.isode.com>; Tue, 29 Nov 2022 18:03:40 +0000
Message-ID: <ed15418b-e97a-49c1-0e52-81529c574b35@isode.com>
Date: Tue, 29 Nov 2022 18:03:36 +0000
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101 Thunderbird/102.3.2
To: Barry Leiba <barryleiba@computer.org>
Cc: last-call@ietf.org, draft-billon-expires@ietf.org
References: <166973210946.22951.15613495979123865103@ietfa.amsl.com> <fff569c8-f2ac-1ddb-ba71-16709b4c723c@isode.com> <CALaySJL2qFdvJkiq+79aatE4pAQ_W5Z887Dychg=qfD5M9=1Fg@mail.gmail.com>
From: Alexey Melnikov <alexey.melnikov@isode.com>
In-Reply-To: <CALaySJL2qFdvJkiq+79aatE4pAQ_W5Z887Dychg=qfD5M9=1Fg@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/last-call/bQ9T-VpbjjcGqou5P88ZxJr6kes>
Subject: Re: [Last-Call] Last Call: <draft-billon-expires-06.txt> (Updated Use of the Expires Message Header Field) to Proposed Standard
X-BeenThere: last-call@ietf.org
X-Mailman-Version: 2.1.39
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: Tue, 29 Nov 2022 18:03:47 -0000

Hi Barry,

On 29/11/2022 17:58, Barry Leiba wrote:
> Thanks, Alexey.
>
> I'm really glad to head that you implemented it; that's good input.
> I'm curious: What does your client do when it encounters an expired
> message?

My webmail client shows time left to action certain messages or that a 
message is past its expiration date. It doesn't auto-delete/auto-hide 
expired messages.

Best Regards,

Alexey

> Barry
>
> On Tue, Nov 29, 2022 at 12:36 PM Alexey Melnikov
> <alexey.melnikov@isode.com> wrote:
>> On 29/11/2022 14:28, The IESG wrote:
>>
>>> The IESG has received a request from an individual submitter to consider the
>>> following document: - 'Updated Use of the Expires Message Header Field'
>>>     <draft-billon-expires-06.txt> as Proposed Standard
>>>
>>> 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 2022-12-27. 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 allows broader use of the Expires message header field
>>>      for mail messages.  Message creators can then indicate when a message
>>>      sent becomes valueless and can safely be deleted, while recipients
>>>      would use the information to delete or ignore these valueless
>>>      messages.
>>>
>>>
>>>
>>>
>>> The file can be obtained via
>>> https://datatracker.ietf.org/doc/draft-billon-expires/
>> I read the draft and I support its publication as an RFC. I implemented
>> the draft in a webmail client.
>>
>> I agree with Barry Leiba's review suggesting a better Introduction section.
>>
>> I only have a small nit:
>>
>> RFC 5322 defines syntax for the Date header field:
>>
>>      orig-date = "Date:" date-time CRLF
>>
>> Note the terminating CRLF.
>>
>> I suggest this document add CRLF to the end of
>>
>>      expires = "Expires" ":" date-time
>>
>> to match.
>>
>> Best Regards,
>> Alexey

v2.23.0 | Report a Bug | By Email