Re: [ietf-smtp] Adding a new value to the WITH protocol type subregistry

Alexey Melnikov <alexey.melnikov@isode.com> Thu, 12 July 2018 16:48 UTC

Return-Path: <alexey.melnikov@isode.com>
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 7C619130EA6 for <ietf-smtp@ietfa.amsl.com>; Thu, 12 Jul 2018 09:48:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=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 fkUuBH8A3thU for <ietf-smtp@ietfa.amsl.com>; Thu, 12 Jul 2018 09:48:19 -0700 (PDT)
Received: from statler.isode.com (Statler.isode.com [62.232.206.189]) by ietfa.amsl.com (Postfix) with ESMTP id 169DE130E89 for <ietf-smtp@ietf.org>; Thu, 12 Jul 2018 09:48:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1531414098; d=isode.com; s=june2016; i=@isode.com; bh=NyI/3+TDa8DjJj+uIlDpYPz/4Bam8beAn4t/1s3Ja2o=; 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=tqoMuBO4gGwSEMChOErscfUOpdXCffB8wzM+5Xj5qkhszIJPTVVo1Cv9tJAQRgN/8ILt+c rzCOMopt4msZKGcC8nTC3zhqW7OgHjEK7o/XijQXQGp8TPLUZeb7G9yKvmahrsWPUoopuF ppGoDOv0EyrsElI1zItu4SX8XfhFvow=;
Received: from [192.168.0.5] (cpc121086-nmal24-2-0-cust54.19-2.cable.virginm.net [77.97.145.55]) by statler.isode.com (submission channel) via TCP with ESMTPSA id <W0eGUgBcJhxf@statler.isode.com>; Thu, 12 Jul 2018 17:48:18 +0100
To: valdis.kletnieks@vt.edu
Cc: ietf-smtp <ietf-smtp@ietf.org>
References: <2017854d-2cc2-3058-3d1b-0da927491491@isode.com> <15701.1531413498@turing-police.cc.vt.edu>
From: Alexey Melnikov <alexey.melnikov@isode.com>
Openpgp: preference=signencrypt
Message-ID: <2cf38389-2c36-3d41-bad0-e94fbde291b1@isode.com>
Date: Thu, 12 Jul 2018 17:48:17 +0100
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.8.0
In-Reply-To: <15701.1531413498@turing-police.cc.vt.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset="windows-1252"
Content-Language: en-US
Content-transfer-encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-smtp/T9aEe2HDDpexmoGKtNKKNXew7VY>
Subject: Re: [ietf-smtp] Adding a new value to the WITH protocol type subregistry
X-BeenThere: ietf-smtp@ietf.org
X-Mailman-Version: 2.1.27
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: Thu, 12 Jul 2018 16:48:21 -0000

Hi,

On 12/07/2018 17:38, valdis.kletnieks@vt.edu wrote:
> On Thu, 12 Jul 2018 16:58:22 +0100, Alexey Melnikov said:
>> I would like to add a new value to the "WITH protocol types" subregistry
> 
> What would this value correspond to?  In other words, what's the protocol
> you're trying to add, and how is it different from the already extant values?

It is an alternative to SMTP for some HF environments. It can be
gatewayed to and from SMTP though, so it would be good to be able to
have a token in the Received line to signal that a particular message
was not transported over SMTP at some point. See
draft-melnikov-email-over-pmul-05.txt


>> required" choice, so that registrations can be added by, say,
>> Independent Stream RFCs?
> 
> I think this is a non-starter.  You're going to need a standards-track RFC
> similar to what RFC4356 does for Internet<->MMS gatewaying to get
> any real traction.
> 
> Plus, having the draft go through the standards process has a high likelyhood
> of people pointing out problems and potential improvements in your protocol :)

For this there must be enough interest in discussing it. The protocol is
rather specialized and I don't think there would be enough interest. So
it is a perfectly reasonable to publish it as an Independent Stream RFC.

Best Regards,
Alexey