IETF Logo Mail Archive

Re: [ietf-smtp] Mail Transfer Protocol over ACP 142

S Moonesamy <sm+ietf@elandsys.com> Fri, 11 August 2017 19:02 UTC

Return-Path: <sm@elandsys.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 7623E1323BF for <ietf-smtp@ietfa.amsl.com>; Fri, 11 Aug 2017 12:02:11 -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, 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=lV0j9dG5; dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=elandsys.com header.b=wytMIjY1
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 WukF-KbQjozd for <ietf-smtp@ietfa.amsl.com>; Fri, 11 Aug 2017 12:02:10 -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 2FDDA124234 for <ietf-smtp@ietf.org>; Fri, 11 Aug 2017 12:02:10 -0700 (PDT)
Received: from SUBMAN.elandsys.com ([197.227.83.78]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id v7BJ1vU1013294 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 11 Aug 2017 12:02:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1502478128; x=1502564528; bh=uQqlysmZfFjL0IqfzfYVYnrve0Xk8ifBu8R4G+AorXQ=; h=Date:To:From:Subject:In-Reply-To:References; b=lV0j9dG5e8eaSEphg5F6Te70cXJI9n9vaWXHS+HVpTt+sYsmBh5CiRZ2KnsM45INn 0ATxUHF9zIK/5TNFpnA6aZHIgmUE7NmL3uRgQkSJny8kGdYNPPrq2DBXmYo3HcRynu UTs65vnL7JWkYbsOxnyATxikyq54mkWNyum5E75w=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1502478128; x=1502564528; i=@elandsys.com; bh=uQqlysmZfFjL0IqfzfYVYnrve0Xk8ifBu8R4G+AorXQ=; h=Date:To:From:Subject:In-Reply-To:References; b=wytMIjY1vauIE26+hB9+H34HbcnEOv2yOzmliyH1O//W5wrF+Xcwfh3Giy6+sQfRb n8MWQOlbvnwxg4i9zPyVs0coK4nEcnQWAEaGGSTSUxI8BQwBIiwzSvAh0MbCtG2RA4 TrQtjqgdOG2InRPPj94WqcGb+79K5Nihwhz8z8Z0=
Message-Id: <6.2.5.6.2.20170811114643.0cb87718@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Fri, 11 Aug 2017 12:01:44 -0700
To: Alexey Melnikov <alexey.melnikov@isode.com>, ietf-smtp@ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
In-Reply-To: <fd285cfd-7dc2-6de4-6226-b2e32da2755e@isode.com>
References: <fd285cfd-7dc2-6de4-6226-b2e32da2755e@isode.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-smtp/6M5OgBu2PrLkBS2o1kqb60IlpPk>
Subject: Re: [ietf-smtp] Mail Transfer Protocol over ACP 142
X-BeenThere: ietf-smtp@ietf.org
X-Mailman-Version: 2.1.22
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: Fri, 11 Aug 2017 19:02:11 -0000

Hi Alexey,
At 09:30 11-08-2017, Alexey Melnikov wrote:
>Based on some work that Isode is doing with gatewaying Internet 
>email to ACP 142 (*) environments, I wrote a draft 
><https://datatracker.ietf.org/doc/draft-melnikov-email-over-pmul/?include_text=1>. 
>If people can review and provide feedback, that would be much appreciated.

[snip]

>(*) - ACP 142 defines a transport protocol for reliable multicast in 
>bandwidth constrained and delayed acknowledgement environments

I could not find the ACP 142 specification.  From what I read, it is 
used in military messaging handling systems.

Regards,
S. Moonesamy

v2.23.0 | Report a Bug | By Email