Alex Rousskov wrote:
If several milestones are highly desirable, we can split SMTP work
into "generic MIME" and "SMTP-specific" sections of the same draft and
then base milestones on those sections.
Given the already narrowed focus, I'd suggest to have a single
document that fuly describes the SMTP solution, rather than defining a
generic MIME solution and a seperate document with SMTP specific
pieces. Let's see what the feedback will be.
Moreover, we can add "SMTP command adaptation" section/milestone (as
opposed to SMTP MIME message adaptation), if that is in scope. BTW, is
I would consider this part of the SMTP solution. Explicit SMTP use
cases would help clarifying the scope issue...