Re: [hrpc] re how 8280 is being used for HR considerations sections

farzaneh badii <farzaneh.badii@gmail.com> Tue, 04 May 2021 17:34 UTC

Return-Path: <farzaneh.badii@gmail.com>
X-Original-To: hrpc@ietfa.amsl.com
Delivered-To: hrpc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A7A0B3A143C for <hrpc@ietfa.amsl.com>; Tue, 4 May 2021 10:34:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.997
X-Spam-Level:
X-Spam-Status: No, score=-1.997 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, HTTPS_HTTP_MISMATCH=0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Xbs2PyYxGafe for <hrpc@ietfa.amsl.com>; Tue, 4 May 2021 10:33:56 -0700 (PDT)
Received: from mail-lj1-x233.google.com (mail-lj1-x233.google.com [IPv6:2a00:1450:4864:20::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 853923A144F for <hrpc@irtf.org>; Tue, 4 May 2021 10:33:56 -0700 (PDT)
Received: by mail-lj1-x233.google.com with SMTP id o16so12216905ljp.3 for <hrpc@irtf.org>; Tue, 04 May 2021 10:33:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=tLDREA8nx37CEE6ac4E0zCPD/x3jGlqLHOFdyp8trYw=; b=pG8LwF45UJf5pPLbJ4Zz1lq67y5TKW4kS8QeFcsgcIwUwwbY06Lnocv3iRzGF6YIVh 67JQ39/iWjOjdezfS94fCIEF1hvOelNWDA5kvcMBr3i5+Em1whZ1gkWov+FLGBRnvSyu dAeYTGUPPc1c2YlKxHrzla3NqDauZlCDmHZ5fV6+6J95T8xt/xDW4eiESFh73jHvNusJ b9mMia0BsXj0lYZDk369BzYCbO1S3YGqd6JZLKUuW58E3+/fnBtSxE+CxnuzWr9uxp8z QeQy7fj2Ht46ZdavtMUZr9td6fn9lYqKOhkXSe8TfxovhuQ6sc2VCiCsZNNcr/waCCI0 q7pA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=tLDREA8nx37CEE6ac4E0zCPD/x3jGlqLHOFdyp8trYw=; b=dHFIKZZGxKn3DMHcArlTGy4eYj/5NeLQuWvkKSj21turlyWiyrYPOgeK0XjjESFP8Z vB66mmejTC8w6O2Kbd02cxbLs6kPYWWZSpYKhPMw6s4QopEVrD1q/RxkPS1sqZujKGqe OxI1ZuJHXASDBoVm+wjverJ8wE7woBZXC0mZvFOWIbDxfbG0VqZWo0fRrLHhJVKNt5iU O/5uTdm5GVsJozgpVtto9JeBs5m0tc9seND/U8E8BwWmIIDuEYm0m2VEViQ6g1nXZ+tT qEStQzToM/5v5LAn1V3jGYcB/oUsdOSPgHC11BLEo/eGErfe6PhPMLUxehsO9R9Go1+f KWhQ==
X-Gm-Message-State: AOAM531VGzkiK7vt3mWy8c8LO7ElWNnonpE6JndlnTMob1mYTGhhvScb HpURxvQ8whQWRUPdsn49xP3dbP+k7jdJA/d1siY=
X-Google-Smtp-Source: ABdhPJyfGnqVeKrVygYHpIqjaR077urLFPFqP/NPFKvF+yq5miH6CSy4aAGGNEjTyBur1pZ1EbBpVzguiudzjtMy+Co=
X-Received: by 2002:a2e:9802:: with SMTP id a2mr17588847ljj.104.1620149633009; Tue, 04 May 2021 10:33:53 -0700 (PDT)
MIME-Version: 1.0
References: <mailman.2371.1620057586.7119.hrpc@irtf.org> <CAB2unbPMAibLYLtHVe+jJcsMa65Y5Ak4gYCGsw8QUON03BTatQ@mail.gmail.com> <375c76f5-cbfb-cab1-e4c6-a435623ff497@cdt.org> <CAB2unbOyLPK4GgBYu-c8VZ9YmgGwzm+o_0+LB9MNH4r-Ccu2rw@mail.gmail.com> <58c97cfc-6f73-a26b-cc5c-84df34e4bcff@cdt.org>
In-Reply-To: <58c97cfc-6f73-a26b-cc5c-84df34e4bcff@cdt.org>
From: farzaneh badii <farzaneh.badii@gmail.com>
Date: Tue, 04 May 2021 13:33:26 -0400
Message-ID: <CAN1qJvAz25QyW9G5+tmL8xMd+zXRDf32+DGNrHNQCjjBTHz2Dw@mail.gmail.com>
To: Mallory Knodel <mknodel@cdt.org>
Cc: Sandra Braman <braman@tamu.edu>, Hrpc <hrpc@irtf.org>
Content-Type: multipart/alternative; boundary="0000000000005bcba505c1847b6a"
Archived-At: <https://mailarchive.ietf.org/arch/msg/hrpc/2KZDr_SMPziP6l-6D4Qati7bULQ>
Subject: Re: [hrpc] re how 8280 is being used for HR considerations sections
X-BeenThere: hrpc@irtf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: hrpc discussion list <hrpc.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/hrpc>, <mailto:hrpc-request@irtf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/hrpc/>
List-Post: <mailto:hrpc@irtf.org>
List-Help: <mailto:hrpc-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/hrpc>, <mailto:hrpc-request@irtf.org?subject=subscribe>
X-List-Received-Date: Tue, 04 May 2021 17:34:02 -0000

I think Professor Braman is making a very valid argument. I don't know why
it doesn't need this additional analysis. I also don't think she is arguing
that HRPC lacks vigour. The argument is that before adding anything to the
I-D we should do enough research. We can also have a chain of I-Ds that can
include our changes over time. (I think like a living document, if that's
possible) I personally don't think the number of I-Ds that this group
publishes matter. It can be one I-D that can be tested and researched over
time. For example, like Fidler and I argued in the past and we saw this
argument on this mailing list as well, implementation is very important. We
can observe the implementation of the protocols and add to the documents
from what we have learned and test the theories.


Farzaneh


On Tue, May 4, 2021 at 1:07 PM Mallory Knodel <mknodel@cdt.org> wrote:

> Hi Sandra,
>
> I believe draft-guidelines has achieved it's aim and doesn't need this
> additional analysis, as interesting as it might be. As Niels said, there
> has already been sufficient work done in this regard for draft-guidelines
> that shouldn't be overlooked.
>
> I suggest it being additional, and ongoing work, that builds on
> draft-guidelines.
>
> One of the challenges that I'm noticing in these exchanges about HRPC work
> is how people view it, and are inspired by the potential, but rather than
> saying "yes, AND" or "this has given me an idea", the tendency is to assume
> the existing work is somehow lacking because it hasn't already incorporated
> that new idea.
>
> HRPC isn't suffering from rigour in its ideas an execution on those.
> Indeed we rather need to establish the foundational research so that these
> new ideas-- like the analysis framework-- can build on top, hopefully as
> new drafts.
>
> -Mallory
> On 5/4/21 12:54 PM, Sandra Braman wrote:
>
> Appreciate the thought, Mallory. However, whether or not the analysis will
> yield anything that should be incorporated into the draft guidelines text
> can only be determined once the research has been done.
>
>
> On Tue, May 4, 2021 at 11:16 AM Mallory Knodel <mknodel@cdt.org> wrote:
>
>> Thanks for volunteering to work on this, Sandra!
>>
>> I would suggest that the analysis go further in depth and also stay open,
>> as things change and progress, so adding them to existing drafts wouldn't
>> be the best strategy.
>>
>> -Mallory
>> On 5/4/21 4:21 AM, Sandra Braman wrote:
>>
>> Given the process, there is no need or reason to say analysis of this
>> subject "can't be included" in the draft guidelines document currently
>> being discussed. An alternative formulation would be to say that the
>> document should not be considered complete until uses people are making of
>> the existing document for which the draft is trying to provide guidelines
>> have been examined and insights they provide have been incorporated into
>> the text. This is not only within existing scope but a basic step, for
>> would be for many the first step, for either a researcher looking at this
>> problem or for someone who is writing a guide in a technical writing sense.
>>
>> I'll do the analysis of discussions of the human rights considerations
>> section in the 7 drafts that include these sections and report back as soon
>> as I can. This should be a couple of weeks, and by then I'll have other
>> thoughts on what is the current draft of the text at that point as well
>> (with all thumbs up the option I, as so many, am hoping for). It will also
>> be interesting to see the genetic drift from RFC 3552 to RFC 6973 (which
>> opens by saying it is modeled on 3552) to RFC 8280; the 3552 I asked about
>> a few days ago is the grandparent. Thanks again to Gurshabad for pointers
>> as I am still learning my way around the document system.
>>
>> ---------- Forwarded message ----------
>>> From: Mallory Knodel <mknodel@cdt.org>
>>> To: Sandra Braman <braman@tamu.edu>
>>> Cc: hrpc@irtf.org
>>> Bcc:
>>> Date: Mon, 3 May 2021 11:23:53 -0400
>>> Subject: Re: [hrpc] re history lessons
>>> On 5/3/21 11:15 AM, Sandra Braman wrote:
>>>
>>> > and what the reasons were for not ultimately including that section in
>>> > documents ultimately published
>>>
>>> No one has yet done this research so it can't be included or cited.
>>>
>>> We do not have any current work items on it either but would openly
>>> encourage and welcome them,
>>>
>>
>>
>>>
>>> -M
>>>
>>> --
>>> Mallory Knodel
>>> CTO, Center for Democracy and Technology
>>> gpg fingerprint :: E3EB 63E0 65A3 B240 BCD9 B071 0C32 A271 BD3C C780
>>>
>>>
>> _______________________________________________
>> hrpc mailing listhrpc@irtf.orghttps://www.irtf.org/mailman/listinfo/hrpc <https://urldefense.com/v3/__https://www.irtf.org/mailman/listinfo/hrpc__;!!KwNVnqRv!Q3RHG3ea9r2vSSpq_EJKDDzP-dY5e94Qq5jfyzZrEBH0WNUfUVjItIPgDwEByg$>
>>
>> --
>> Mallory Knodel
>> CTO, Center for Democracy and Technology
>> gpg fingerprint :: E3EB 63E0 65A3 B240 BCD9 B071 0C32 A271 BD3C C780
>>
>> --
> Mallory Knodel
> CTO, Center for Democracy and Technology
> gpg fingerprint :: E3EB 63E0 65A3 B240 BCD9 B071 0C32 A271 BD3C C780
>
> _______________________________________________
> hrpc mailing list
> hrpc@irtf.org
> https://www.irtf.org/mailman/listinfo/hrpc
>