Tony Finch wrote:
If the current document is intended as a case analysis for a particular
application -- namely email -- to serve as *input* to the design of the OPES
architecture and protocols, then I do not see how the current document
achieves that.
I believe it's intended to fit the existing OPES architecture to SMTP.
The original charter of OPES focused on services operating on HTTP
messages. OPES was then re-chartered to add support for services
operating on SMTP.
In a first step, the WG discussed how the SMTP work would have to
address the IAB considerations for OPES [RFC 3238]. The draft
(draft-ietf-opes-smtp-security) summarizes the results of these discussions.
Since there's a lack of interest (i.e. not a sufficient number of active
contributors) we decided *not* to move forward with the SMTP work and to
dissolve the WG.
The intend of publishing this document before dissolving the WG is to
have the discussion on how the IAB considerations apply to OPES/SMTP
written down, in case individual contributors might pick-up the
OPES/SMTP work later on (although we don't have indication this might
happen).
Thanks,
Markus
_______________________________________________
Ietf mailing list
Ietf(_at_)ietf(_dot_)org
https://www1.ietf.org/mailman/listinfo/ietf