Re: Last Call: Moving RFC 4405, RFC 4406, RFC 4407 (Sender-ID) to Historic

Alexey Melnikov <alexey.melnikov@isode.com> Wed, 20 June 2018 14:00 UTC

Return-Path: <alexey.melnikov@isode.com>
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 7F928130EAF; Wed, 20 Jun 2018 07:00:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level:
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-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 ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OT4YdaKcpRwM; Wed, 20 Jun 2018 07:00:03 -0700 (PDT)
Received: from waldorf.isode.com (waldorf.isode.com [62.232.206.188]) by ietfa.amsl.com (Postfix) with ESMTP id EB9EC130EA5; Wed, 20 Jun 2018 07:00:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1529503202; d=isode.com; s=june2016; i=@isode.com; bh=yIYo7yCrsjRWopw5whT8Z2BXXiwkjIENLGbPtKfGC5o=; 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=Q+4ZT2G6uAh4ZrSyeVxos+n9BC2J3x/sE9rITfA/plTZmqfXT1Ar2zoY2XzA7M/XR4/Z9i wKGfs3z8gAk4eA2F3lzt92bsQgjePh5a0Ac35Ayqu9WsL7eduYVrEszxn9/NIG+j+sSOFb sD98yeXIxwZfS2ehBTj1Dsbwl4+rfs4=;
Received: from [172.20.1.215] (dhcp-215.isode.net [172.20.1.215]) by waldorf.isode.com (submission channel) via TCP with ESMTPSA id <Wypd4gAE9Q24@waldorf.isode.com>; Wed, 20 Jun 2018 15:00:02 +0100
Subject: Re: Last Call: Moving RFC 4405, RFC 4406, RFC 4407 (Sender-ID) to Historic
To: S Moonesamy <sm+ietf@elandsys.com>, iesg@ietf.org, ietf@ietf.org
References: <152588285893.3989.7909763661642193132.idtracker@ietfa.amsl.com> <6.2.5.6.2.20180619151759.0bf2c2b0@elandnews.com> <3679f35a-f6a8-47e9-9c0a-84b99a388855@isode.com> <6.2.5.6.2.20180620062609.08678c98@elandnews.com>
From: Alexey Melnikov <alexey.melnikov@isode.com>
Message-ID: <404d054e-d963-dd70-c9ae-f6ae4666797b@isode.com>
Date: Wed, 20 Jun 2018 14:59:47 +0100
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0
In-Reply-To: <6.2.5.6.2.20180620062609.08678c98@elandnews.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-GB
Content-transfer-encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/mv6GMTuUVMzXxPtTRrItTPl3pDA>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.26
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, 20 Jun 2018 14:00:05 -0000

Hi SM,

On 20/06/2018 14:40, S Moonesamy wrote:
> Hi Alexey,
> At 03:44 AM 20-06-2018, Alexey Melnikov wrote:
>> I can't think of any actions needed for the SMTP Service Extensions 
>> registry. SUBMITTER is not going to be removed from it. Did you think 
>> of something else?
>
> Not taking any action to update the registry defeats the purpose of 
> having the registry.
Adding a note about the extension being moved to Historic is reasonable. 
Removing the entry is not.

>   I suggest considering Section 2.2 of RFC 5321.

I am happy to be proven wrong, but I don't think it covers the case of 
an SMTP extension being made historic.

Best Regards,
Alexey