At 04:12 AM 8/2/2011, Alessandro Vesely wrote:
+1, I obviously agree! Unfortunately, this option seems to be out of
reach right now. Any chance we can pursue it before shutting down?
Would the WG resolve to considerately complete 5321bis and only it?
I'll summarize the discussion about shutting the YAM WG. There was a
solid consensus on the question of shutting down [1]. J.D. Falk and
Dave Corcker did not object to it [2] [3]. I read the messages from
Alessandro Vesely as an objection.
Barry Leiba explained the status of 5321bis-smtp-pre-evaluation. I
gather that it is clear that the document cannot be published as a
RFC as it was discussed by the IESG as a management item.
The question on the table is whether there is an chance for the WG to
pursue work on 5321bis before it is shut down. Barry mentioned that
it's a pity to waste the work that was done and that he would really
like to see the current version of SMTP back at full Standard level
[4]. He also volunteered to edit 5321bis document, incorporating the
changes from the pre-evaluation document.
Does the working group think that it is reasonable to give it a go?
I haven't seen any objection to the changes mentioned in the
pre-evaluation document. John Klensin commented [5] on
the description of the extension model in 5321. That is the kind of
change which Barry described as "new discoveries that are so bad that
they absolutely have to be incorporated".
I am open to having the work done. That presumes that the working
group is agreeable to deferring the question of shutting down. If
there is interest in putting two months in this work, the working
group could do the following:
(a) Each WG participant posts a list of proposed changes together with the
rationale for the change. The WG avoids any discussion of the proposed
changes at this stage.
(b) I'll list each proposed change in the issue tracker. If there are two or
more changes that are similar, I'll track them as one if people agree.
(c) Once the WG has a list of issues, it can estimate the time required to
get the work done and how to deal with the issues.
The above work can be done under the current charter.
Regards,
S. Moonesamy
YAM WG co-chair
1. http://www.ietf.org/proceedings/81/minutes/yam.txt
2. http://www.ietf.org/mail-archive/web/yam/current/msg00706.html
3. http://www.ietf.org/mail-archive/web/yam/current/msg00707.html
4. http://www.ietf.org/mail-archive/web/yam/current/msg00721.html
5. http://www.ietf.org/mail-archive/web/yam/current/msg00722.html
_______________________________________________
yam mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/yam
