Re: Last Call: Moving RFC 4405, RFC 4406, RFC 4407 (Sender-ID) to Historic
S Moonesamy <sm+ietf@elandsys.com> Wed, 20 June 2018 13:52 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 87297130EA2;
Wed, 20 Jun 2018 06:52:50 -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=gscBX3Z7; dkim=fail (1024-bit key)
reason="fail (message has been altered)" header.d=elandsys.com
header.b=sPSycS7J
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 vhQuoqRJ6mkq; Wed, 20 Jun 2018 06:52:50 -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 DD2B3130E96;
Wed, 20 Jun 2018 06:52:49 -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 w5KDqbAH023237
(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
Wed, 20 Jun 2018 06:52:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org;
s=mail2010; t=1529502769; x=1529589169;
bh=fBmRUJwdb6dKevUQP+BbCzvyJsD4A3XgTB3FJOVdEkw=;
h=Date:To:From:Subject:In-Reply-To:References;
b=gscBX3Z7FEgjnVdP+kJkFipSJ47iAv/kA2wMWTi96WhGvE8MU0svh6qE+MQlj8hOj
ESz8miYKE0WQB7YfTpGLU5ZtCg2yPKn/ixEsdqfUN0FqY0MocMhd+E4Qx44GYX9Y4j
mB0NrkSt8Az3qK5iox5QyfLoFdDY1A6T9dssUAxE=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail;
t=1529502769; x=1529589169; i=@elandsys.com;
bh=fBmRUJwdb6dKevUQP+BbCzvyJsD4A3XgTB3FJOVdEkw=;
h=Date:To:From:Subject:In-Reply-To:References;
b=sPSycS7JHnRmDSrSxC1J4O1Rzv3xk0y9PjEkiqUp3/SkdGO7YVuvJfQfvbrlN9/3k
XuOet1En4lYCEp5wzkB8WTtbqa8ur8nZlLAi3IRkmf8TaAhov/UuXelMYmR328tU7L
d58QjI98oGcrf8FfKJc+S81LHCpGRb4NFKTDFGzg=
Message-Id: <6.2.5.6.2.20180620062609.08678c98@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Wed, 20 Jun 2018 06:40:08 -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: <3679f35a-f6a8-47e9-9c0a-84b99a388855@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>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/ufovadbA4jLapSMaOjOK1tKESYs>
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 13:52:51 -0000
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. I suggest considering Section 2.2 of RFC 5321. Regards, S. Moonesamy
- Re: Last Call: Moving RFC 4405, RFC 4406, RFC 440… Hector Santos
- Re: Last Call: Moving RFC 4405, RFC 4406, RFC 440… S Moonesamy
- Re: Last Call: Moving RFC 4405, RFC 4406, RFC 440… John C Klensin
- Re: Last Call: Moving RFC 4405, RFC 4406, RFC 440… S Moonesamy
- Re: Last Call: Moving RFC 4405, RFC 4406, RFC 440… Alexey Melnikov
- Re: Last Call: Moving RFC 4405, RFC 4406, RFC 440… S Moonesamy
- Re: Last Call: Moving RFC 4405, RFC 4406, RFC 440… Scott Kitterman
- Re: Last Call: Moving RFC 4405, RFC 4406, RFC 440… Alexey Melnikov
- Re: Last Call: Moving RFC 4405, RFC 4406, RFC 440… S Moonesamy
- Re: Last Call: Moving RFC 4405, RFC 4406, RFC 440… Barry Leiba
- Re: Last Call: Moving RFC 4405, RFC 4406, RFC 440… ned+ietf
- Re: Last Call: Moving RFC 4405, RFC 4406, RFC 440… Kurt Andersen
- Re: Last Call: Moving RFC 4405, RFC 4406, RFC 440… Scott O. Bradner
- Re: Last Call: Moving RFC 4405, RFC 4406, RFC 440… John Levine
- Re: Last Call: Moving RFC 4405, RFC 4406, RFC 440… Kurt Andersen
- Re: Last Call: Moving RFC 4405, RFC 4406, RFC 440… John C Klensin
- Re: Last Call: Moving RFC 4405, RFC 4406, RFC 440… John R Levine
- Re: Last Call: Moving RFC 4405, RFC 4406, RFC 440… John Levine
- Re: Last Call: Moving RFC 4405, RFC 4406, RFC 440… Barry Leiba
- Re: Last Call: Moving RFC 4405, RFC 4406, RFC 440… John C Klensin
- Re: Last Call: Moving RFC 4405, RFC 4406, RFC 440… Barry Leiba
- Re: Last Call: Moving RFC 4405, RFC 4406, RFC 440… John R Levine