IETF Logo Mail Archive

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

S Moonesamy <sm+ietf@elandsys.com> Wed, 20 June 2018 14:18 UTC

Return-Path: <sm@elandsys.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 E01A61292AD; Wed, 20 Jun 2018 07:18:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.79
X-Spam-Level:
X-Spam-Status: No, score=-1.79 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, RCVD_IN_DNSWL_NONE=-0.0001, T_DKIM_INVALID=0.01] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=opendkim.org header.b=tBY0FcnN; dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=elandsys.com header.b=sbko06Ci
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 UrdhANQDxrqs; Wed, 20 Jun 2018 07:18:12 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id EAC9A126CB6; Wed, 20 Jun 2018 07:18:11 -0700 (PDT)
Received: from DESKTOP-K6V9C2L.elandsys.com ([197.224.107.184]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id w5KEHvFa008693 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 20 Jun 2018 07:18:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1529504291; x=1529590691; bh=Ma5EHefPkGXUDTpIms8IboezOgDhGi2Eye+SmCsYFhM=; h=Date:To:From:Subject:In-Reply-To:References; b=tBY0FcnN2VeA2ZS4hWLXeGSTAhuG1Cz98OjuJpFzIe8+6zNXJJGwlVwFtO3Bu3N2+ cLSZMxLojkcOL/0vxU8jDzeyWyPxxZYDnZIwGkmuZ8EQJTVTFxHhKpBUtiKs10XVM4 a/Kup0nqj/NA1h2JmAwwdFeB0a2rU4SwDDTCKilw=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1529504291; x=1529590691; i=@elandsys.com; bh=Ma5EHefPkGXUDTpIms8IboezOgDhGi2Eye+SmCsYFhM=; h=Date:To:From:Subject:In-Reply-To:References; b=sbko06CiIKS4cqpzQHPAbyiMuFOypXDAbC33PTlAHjIx2iu3WrKlgo5ObZHsu/lg7 mjK4LqcW7Utfu4qtKKBgMr+a+dt4oMxRcGCyazeojmbj0XqfcBR9h46VfxgCJ0cBZ0 K5+NvhRE8MDZteFLfy8t/BmEwtiV43rcBGk/zk/0=
Message-Id: <6.2.5.6.2.20180620071010.0be97288@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Wed, 20 Jun 2018 07:17:02 -0700
To: Alexey Melnikov <alexey.melnikov@isode.com>, iesg@ietf.org, ietf@ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: Last Call: Moving RFC 4405, RFC 4406, RFC 4407 (Sender-ID) to Historic
In-Reply-To: <404d054e-d963-dd70-c9ae-f6ae4666797b@isode.com>
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> <404d054e-d963-dd70-c9ae-f6ae4666797b@isode.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Via50rroe7aRBUVzM5ttrve_OlE>
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:18:13 -0000

Hi Alexey,
At 06:59 AM 20-06-2018, Alexey Melnikov wrote:
>Adding a note about the extension being moved to Historic is 
>reasonable. Removing the entry is not.

Adding a note sounds fine.  I'll leave the process details to you.

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

My guess is that the editor might read the ietf@ mailing list. :-)

Regards,
S. Moonesamy

v2.23.0 | Report a Bug | By Email