![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
John C Klensin wrote:
Sadly, I have to agree with Keith. While these lists are a fact of life today, and I would favor an informational document or document that simply describes how they work and the issues they raise, standardizing them and formally recommending their use is not desirable at least without some major changes in our email model and standards for what gets addresses onto --and, more important, off of-- those lists.
John, What are the technical deficiencies of this specification?What are the specific problems the mechanism it defines pose to "our email model and standards"?
What are the specific, "major changes" that would be required to the model and standards, to make the current specification acceptable?
This type of mechanism has massive adoption throughput the Internet. It's perceived efficacy also is massive. The current specification merely seeks to provide a stable technical basis for that mechanism.
In the face of overwhelming community consensus for this mechanism, you offer a simple, flat, fundamental rejection, yet provide no substantiation.
Really, John, it would help for a posting to do more than say that you don't like the idea of the mechanism.
d/ -- Dave Crocker Brandenburg InternetWorking bbiw.net _______________________________________________ Ietf mailing list Ietf at ietf.org https://www.ietf.org/mailman/listinfo/ietf
Note Well: Messages sent to this mailing list are the opinions of the senders and do not imply endorsement by the IETF.