[Gendispatch] url/web-trackers and IETF mailing lists

[Michael Richardson <[e-mail]>]

Hi, Gendispatch is not (as far as I know) scheduled to meet at IETF123.
I would like consideration of how to dispatch this document.

I had originally asked the IESG if they would introduce a policy based upon
their perogative, and they asked that I write an I-D.

There has been some discussion on [e-mail], and a few private threads.

There are some dissension as to whether or not any policy could be
practically implemented.  Or whether it would be effective.  Some suggest
that we not bother to have a policy that they think can't be implemented, or
won't be 100% effective.  I understand that view, but for the moment, I'd
prefer if people could put that view in their back pocket.

I'd like to suggest seperate discussion of whether or not this is a good
idea (a good policy in the abstract) from the whether or not a particular
implementation of the policy would be effective.

What I suggest is that, if once we agree on what kinds of actions would be
tolerable, that we come back to whether or not the policy is worthwhile.
(It might be that we do not come to any such agreement)

https://datatracker.ietf.org/doc/draft-richardson-no-trackers-in-archives/
https://github.com/mcr/no-trackers

1.  Introduction

   The IETF does most of it's work via email lists.

   Indeed unlike many organizations, face to face meetings are not
   considered final, and process documents [RFC2026] emphasis that it is
   on mailing lists that rough consensus is sought: [RFC7282].

   To that end, an accurate, searchable, safe and public archive is
   maintained by the IETF.  Viewing the archives should not subject
   participants to monitoring by third parties.

   An increasing occurance is (enterprise) email systems that attempt to
   make all links "safe" for their employees, screening their employees
   from the phising attack of the day.  This is often accomplishing by
   filtering all email for HTTP links that appear in email, and then
   rewriting them to go through a filtering service.



--
Michael Richardson <[e-mail]>   . o O ( IPv6 IøT consulting )
           Sandelman Software Works Inc, Ottawa and Worldwide