RE: Regarding focus of draft-nottingham-for-the-users

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



+1 Eliot (especially first mail), Jari, Kathleen, Stewart (and of course, others, e.g. Stephen, on the uncertainty of the scope vs. rest of the document).

 

I think it is misleading/oversimplified to identify specific “groups” as threats. It doesn’t help any constructive discussion to say “us vs. them” especially when “them” is probably the majority of us.

 

I’d suggest if continuing with this draft to generalize, e.g.:

the IETF tends to protect their interests over those of parties such as network operators or equipment vendors/s/the IETF tends to protect their interests over other interests which may harm the user.

 

And this sentence:

While networks need to be managed, employers and equipment vendors need to meet business goals, and so on, the IETF's mission is to "build a better human society"/s/ The IETF's mission is to "build a better human society”.

 

This document, especially the above sentence, does not accurately reflect RFC3935. There is no sentence in RFC3935 implying some IETF participants “need to meet business goals”. RFC3935’s mission statement is inclusive. This document as currently is divisive. I prefer RFC3935.

 

Deborah

(no hats)

 

From: ietf <ietf-bounces@xxxxxxxx> On Behalf Of Eliot Lear
Sent: Thursday, March 21, 2019 5:14 AM
To: Martin Thomson <mt@xxxxxxxxxxxxxx>
Cc: ietf@xxxxxxxx
Subject: Re: Regarding focus of draft-nottingham-for-the-users

 

Martin:



On 21 Mar 2019, at 02:01, Martin Thomson <mt@xxxxxxxxxxxxxx> wrote:

 

On Wed, Mar 20, 2019, at 22:50, Keith Moore wrote:

We can either stick our heads in the sand, or try to have some
foresight.  Our foresight will certainly be imperfect, but it's probably
better than willful blindness.


I agree with Keith's points here, but I don't think that the draft is demanding any more than what we can (and mostly already) do.  Just a recognition that what we do isn't free of consequence and that we have a responsibility to engage with those consequences.

 

One cannot but agree with the abstracted point you have made.   Unfortunately, that is not what the draft actually states (see my first email in this thread).



I don't think that we've had a problem of willful ignorance or blindness.. I'd suggest that it's more a case of denial.  Denial of the fact that there are wider consequences to our choices.  More seriously, denial of the fact that ignoring them is a very particular way of engaging with those consequences.

 

 

A claim that others are in denial is either true or a discounting of considered experience and conclusions of people with different perspectives.  Can you elaborate on why you believe it to be the former and not the latter?

 



Yes, we are better at making decisions when we can concentrate on technical matters, but any decisions we make will be more relevant when their greater context is considered in that process.  My view is that anything less would be irresponsible.

 

 

That's not only because just because we as a community are primarily techies, but also because people have different priorities and concerns.  It is hard to find consensus on our works when conflicting values have technical implications; and in those cases it should be hard.

 

As you implied above, this tussle is already necessarily playing out.  A new normative document could, by design, place a finger on the scale, as I previously wrote, in such a way as to short circuit consideration of consequences, leading to the very irresponsible outcome you wish to avoid.

 

Eliot


[Index of Archives]     [IETF Annoucements]     [IETF]     [IP Storage]     [Yosemite News]     [Linux SCTP]     [Linux Newbies]     [Mhonarc]     [Fedora Users]

  Powered by Linux