Protocol Action: 'ESMTP and LMTP Transmission Types Registration' to Draft Standard

The IESG <iesg-secretary@ietf.org> Mon, 25 January 2010 20:31 UTC

Return-Path: <wwwrun@core3.amsl.com>
X-Original-To: ietf-announce@ietf.org
Delivered-To: ietf-announce@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 30) id 582BC3A68FA; Mon, 25 Jan 2010 12:31:15 -0800 (PST)
X-idtracker: yes
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Subject: Protocol Action: 'ESMTP and LMTP Transmission Types Registration' to Draft Standard
Message-Id: <20100125203115.582BC3A68FA@core3.amsl.com>
Date: Mon, 25 Jan 2010 12:31:15 -0800 (PST)
Cc: Internet Architecture Board <iab@iab.org>, RFC Editor <rfc-editor@rfc-editor.org>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-announce>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 25 Jan 2010 20:31:15 -0000

The IESG has approved the following document:

- 'ESMTP and LMTP Transmission Types Registration '
  RFC 3848 as a Draft Standard

This document has been reviewed in the IETF but is not the product of an
IETF Working Group. 

The IESG contact person is Alexey Melnikov.

A URL of this RFC is:
http://www.ietf.org/rfc/rfc3848.txt

Technical Summary

   This document registers seven new mail transmission types (ESMTPA,
   ESMTPS, ESMTPSA, LMTP, LMTPA, LMTPS, LMTPSA) for use in the "with"
   clause of a Received header in an Internet message.

Working Group Summary

   This is not a working group document.
   Publication of the RFC 3848 was non controversial.

Document Quality

   There are multiple implementations (both parsers and generators)
   of the protocol, please see the implementation report.

Personnel

   Alexey Melnikov is the responsible Area Director. This document
   has no shepherd.