Tony Hansen | 3 Jan 00:54
Picon
Favicon

[Fwd: Last Call: draft-ietf-opes-smtp-security (Integrity, privacy and security in OPES for SMTP) to Informational RFC]

fyi, this seems relevant to these two lists.

	Tony
Picon Favicon
From: The IESG <iesg-secretary <at> ietf.org>
Subject: Last Call: draft-ietf-opes-smtp-security (Integrity, privacy and security in OPES for SMTP) to Informational RFC
Date: 2007-01-02 14:44:23 GMT
The IESG has received a request from the Open Pluggable Edge Services WG
(opes) to consider the following document:

- 'Integrity, privacy and security in OPES for SMTP '
   <draft-ietf-opes-smtp-security-02.txt> as an Informational RFC

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action.  Please send substantive comments to the
ietf <at> ietf.org mailing lists by 2007-01-17. Exceptionally, 
comments may be sent to iesg <at> ietf.org instead. In either case, please 
retain the beginning of the Subject line to allow automated sorting.

The file can be obtained via
http://www.ietf.org/internet-drafts/draft-ietf-opes-smtp-security-02.txt

IESG discussion can be tracked via
(Continue reading)

Tony Hansen | 22 Jan 21:31
Picon
Favicon

[Fwd: Advancing RFC2821 to Draft Standard -- outline of work]

This is an FYI of work that's starting up on the ietf-smtp <at> imc.org
mailing list.

	Tony Hansen
	tony <at> att.com
Favicon
From: Lisa Dusseault <ldusseault <at> commerce.net>
Subject: Advancing RFC2821 to Draft Standard -- outline of work
Date: 2007-01-22 19:40:08 GMT

I've been discussing the advancement of RFC2821 along the standards  
track with a few people, and we'd like to proceed publicly.  This  
email can be considered an informal charter and plan for initial  
work, with consensus goals for the effort, which may not need a  
formal WG.  Charter-bashing should be done *early* if you disagree.  
I'd rather avoid late-cycle suggestions to change the goals. This  
list seems like a fine place to have discussions about the goals, as  
well as to do the actual work, and I'll post pointers to a couple  
other lists to direct people here who aren't already subscribed.

1.  We want to advance RFC2821/SMTP to Draft Standard.  Thus, we  
don't want to design anything "new" or "better" for SMTP as part of  
this particular effort, which would require recycling at Proposed  
Standard -- in fact, we want to be conservative in minimizing  
(Continue reading)


Gmane