Tony,
On 11/11/2013 07:10 PM, Tony Rutkowski wrote:
> On 11/11/2013 12:56 PM, Stephen Farrell wrote:
>> IETF specifications need to be designed to protect against
>> pervasive monitoring where possible. This list is intended
>> for technical discussions attempting to meet that goal.
> Where "possible," or where "appropriate."
I think either is good enough.
> Surely you are not inferring that every "specification"
> needs to be so designed? It seems context dependent.
>> Discussion is limited to specific technical proposals for
>> improvements in IETF protocols and to IETF process changes
>> aiming to increase the liklihood that implementation and
>> deployment of IETF protocols results in better mitigation
>> for pervasive monitoring.
> What if one believes that mitigation is not
> appropriate, or that it pervasive monitoring
> should be enhanced? Those apostates should
> go somewhere else?
If someone believed that, then they would be unlikely
to be a happy and constructive contributor on this list;-)
As Brian points out, refining the list to this scope is
entirely consistent with the Vancouver tech plenary
outcome. If you want to disagree with the outcome of the
Vancouver tech-plenary, then the list for that discussion
would be [email protected] and not this one.
And to be clear, yes, there is the implication that
continued off-topic posting here (especially with occasional
inflammatory content as has happened) could lead to an
RFC 3683 PR-action, as I've previously explained to you
in off list mail.
I really hope you don't take us down that road, but I
want to be clear that this refinement of the list
description does mean that your continual statements
that this work is some kind of religious quest are now
quite clearly off-topic for this list.
In contrast, calling out any actual flaws in proposals
that are made is entirely within scope and is welcome.
S.
> Guess you don't want discuss improving the
> protocols to enhance DPI or data retention. :-)
>
> cheers,
> tony
> _______________________________________________
> perpass mailing list
> [email protected]
> https://www.ietf.org/mailman/listinfo/perpass
>
_______________________________________________
perpass mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/perpass
