rfc2821bis-04
John C Klensin <john+smtp@jck.com> Mon, 14 May 2007 17:46 UTC
Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l4EHk070069568 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 14 May 2007 10:46:00 -0700 (MST) (envelope-from owner-ietf-smtp@mail.imc.org)
Received: (from majordom@localhost) by balder-227.proper.com (8.13.5/8.13.5/Submit) id l4EHk0Ys069566; Mon, 14 May 2007 10:46:00 -0700 (MST) (envelope-from owner-ietf-smtp@mail.imc.org)
X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-smtp@mail.imc.org using -f
Received: from bs.jck.com (ns.jck.com [209.187.148.211]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l4EHjujC069548 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for <ietf-smtp@imc.org>; Mon, 14 May 2007 10:45:58 -0700 (MST) (envelope-from john+smtp@jck.com)
Received: from [127.0.0.1] (helo=p3.JCK.COM) by bs.jck.com with esmtp (Exim 4.34) id 1HnecN-000AHQ-La for ietf-smtp@imc.org; Mon, 14 May 2007 13:45:56 -0400
Date: Mon, 14 May 2007 13:45:54 -0400
From: John C Klensin <john+smtp@jck.com>
To: ietf-smtp@imc.org
Subject: rfc2821bis-04
Message-ID: <F41E7445A8E7174CE7A279A1@p3.JCK.COM>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="==========F42CBF6063BBC9423AC8=========="
Sender: owner-ietf-smtp@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-smtp/mail-archive/>
List-ID: <ietf-smtp.imc.org>
List-Unsubscribe: <mailto:ietf-smtp-request@imc.org?body=unsubscribe>
Hi.
rfc2821bis-04 is in the posting queue. I assume that it will
show up in the directories sometime today or tomorrow and that
Tony will post an issues status list and further instructions
shortly thereafter.
This is beginning to feel to me as if we are getting into the
home stretch, aka the point of diminishing returns, but
decisions about that are up to Tony.
I have just added Issue 36 to reflect the general topic of
revising the IANA Considerations Section to include pointers to
sundry registry-creation documents. Note that, if we do this,
we are likely to need downrefs to some existing documents (per
draft-klensin-norm-ref-04, to be RFC 4897 sometime soon) and/or
to move them to Draft along with this one and, if we need a
reference to draft-hansen-4468upd-mailesc-registry, to move that
along and into Last Call and the RFC Editor queue really soon
now so it can _even_ be a downref.
Current issues list attached.
john
- Re: rfc2821bis-04 Tony Hansen
- rfc2821bis-04 John C Klensin