[hrpc] Draft-HRPC-guidelines

Avri <avri@apc.org> Thu, 28 March 2019 10:03 UTC

Return-Path: <avri@apc.org>
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 2F2E11202E6 for <hrpc@ietfa.amsl.com>; Thu, 28 Mar 2019 03:03:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level:
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3] autolearn=ham autolearn_force=no
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 3oMFPP6WI5Gq for <hrpc@ietfa.amsl.com>; Thu, 28 Mar 2019 03:03:54 -0700 (PDT)
Received: from mail.gn.apc.org (mail.gn.apc.org [37.220.108.136]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6D9CF12044C for <hrpc@irtf.org>; Thu, 28 Mar 2019 03:03:54 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mail.gn.apc.org (Postfix) with ESMTP id 945432038D9A for <hrpc@irtf.org>; Thu, 28 Mar 2019 10:03:52 +0000 (GMT)
X-Virus-Scanned: by amavisd-new at mail.gn.apc.org
Received: from mail.gn.apc.org ([127.0.0.1]) by localhost (mail.gn.apc.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GKjwddwNjSRr for <hrpc@irtf.org>; Thu, 28 Mar 2019 10:03:47 +0000 (GMT)
Received: from anonymous ([10.254.254.3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: avri) by mail.gn.apc.org (Postfix) with ESMTPSA id 1CE672038D9E for <hrpc@irtf.org>; Thu, 28 Mar 2019 10:03:46 +0000 (GMT)
Date: Thu, 28 Mar 2019 11:03:44 +0100
From: Avri <avri@apc.org>
To: Hrpc <hrpc@irtf.org>
Message-ID: <5953ec1b-990a-457f-bc12-1c3fe159304a@avris-iPad>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="5c9c9c00_7fdcc233_5088"
Archived-At: <https://mailarchive.ietf.org/arch/msg/hrpc/CMZNwYxubKupeCKsNy6wO_AAlqA>
Subject: [hrpc] Draft-HRPC-guidelines
X-BeenThere: hrpc@irtf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "mail@nielstenoever.net" <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: Thu, 28 Mar 2019 10:04:08 -0000

     
 

 Hi,
 

 
Apologies for last minute comments, but I was not sure about being able to continue with the research group until just recently.
 

 
I think this document is coming along nicely. I especially like the way it is attempting to gather consideration that relate to the various rights as opposed to just concentrating on one or two of the rights.
 

 
Some specific comments:  
 

 
- I think that perhaps in the abstract or the intro, it should mention that these are considerations are still under test.    You indicate that they are being still being developed but not that they still need test for usefulness and validity. This is an activity I think we still need to develop a methodology for - some rigorous manner of testing and documenting the testing.
 

 
- in 3.2.1  &  3.2.2 It seems to indicate that the considerations are not useful for doing an impact analaysis.    I think that when done in a last call review, they do contribute to doing an impact analysis. I think that might be a use we need to verify and test for, but I think it might be worth mentioning.    Though one distinction probably worth making is that use of the considerations while the protocol is in development is a process best done by those involved in the protocol development itself, while an impact analysis done as part of a last call is probably best done by an external observer.    So while I think it should be possible to use the same considerations in both processes, the way it is done and by whom probably varies. 

 
 

 
- in 3.3 you mention that we do not discuss the issue of whether a HR considerations section should be added.    I do not think that is an IRTF task. We should be be developing the considerations and testing them for their use and reasonableness.    Any proposal to make them part of an IETF process should probably be left to some future IETF process.    One of the things we have had an issue with, and some pointed comments on, is crossing into the actual IETF engineering process.
 

 
- in 3.3.x, I think it would be good to point to where the HR that are impacted by by the consideration are discussed and explained.    I know this may creates cross references to work that is not yet done, but it seems to just be left unexplained in the current draft.    I think that if the doc says a consideration is useful for, e.g., for the right of political participation or for participation in cultural life ... we should explain why somewhere - not in this doc but in a doc specifically related to the right and considerations pertinent to that right. Also might be worth listing the UDHR    and para reference for each so that they can be looked up by readers.
 

 
All in all, I think it is coming out well. thanks for the effort.
 

 
Avri