there is no reason why it cannot be a generic e-mail replacement
Implementation is relativally simple
Deployment is not. Do you have the support of any of the major providers of
email infrastructure?
The mistake many people make about the IETF is believing that the way
standards get deployed is you propose something in the IETF and the industry
then eagerly deploys it.
In practice the industry takes little to no notice of IETF activities. The
only way a protocol is going to get deployed is if you have a propagation
strategy to drive deployment. There are 3000++ RFCs and of those maybe
thirty have ever been implemented and deployed on a network wide scale.
RSS is the emergent protocol, it supports richer content
than NNTP, is
considerably simpler and has a significant user base even
though there are
practically no clients (!)
not relevant
If you want people to take notice of you you need to explain why your
proposal is better than an infrastructure that has five years of deployment
experience at this point and is widely implemented.
I suggest that if you want to take this further you submit a draft and see
if you can persuade people to read it.
Phill
_______________________________________________
Asrg mailing list
Asrg(_at_)ietf(_dot_)org
https://www1.ietf.org/mailman/listinfo/asrg