IETF Logo Mail Archive

Re: [hrpc] [Pearg] descriptive censorship work: draft-hall-censorship-tech: move to hrpc?

stephen.farrell@cs.tcd.ie Sat, 18 May 2019 07:37 UTC

Return-Path: <stephen.farrell@cs.tcd.ie>
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 520C81202B1 for <hrpc@ietfa.amsl.com>; Sat, 18 May 2019 00:37:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.301
X-Spam-Level:
X-Spam-Status: No, score=-4.301 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cs.tcd.ie
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 VvD17-hQDFIX for <hrpc@ietfa.amsl.com>; Sat, 18 May 2019 00:37:22 -0700 (PDT)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 077EA1200B6 for <hrpc@irtf.org>; Sat, 18 May 2019 00:37:21 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id D59DDBE51; Sat, 18 May 2019 08:37:18 +0100 (IST)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TB3d2hPQW3p3; Sat, 18 May 2019 08:37:17 +0100 (IST)
Received: from [100.64.5.61] (unknown [212.129.73.91]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 41103BE50; Sat, 18 May 2019 08:37:17 +0100 (IST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; s=mail; t=1558165037; bh=yOYUMJ9y4SvDlGlxc7gBo4PjVscFeJsto08z6agFeKs=; h=To:Cc:From:Subject:In-Reply-To:References:Date:From; b=fvn1VQhGg5k8XeaSawpmIicnibUEMYZ1qW3MjCDX1jnEyYjCgPqcuIGAzgc+3l+7o nGzdOmkeJNJf8AwBgF86eb8xQ7k82xRnqLzaAs0lsCVWIony9se2v1btkzQIIiSD/v RGliidQCXGqSo4Ff2vo6owqntsQjEdTynes4V3BU=
X-Priority: 3
To: melinda.shore@nomountain.net
Cc: hrpc@irtf.org
From: stephen.farrell@cs.tcd.ie
In-Reply-To: <a148823f-3501-b9a6-f460-eb85105c1e49@nomountain.net>
References: <CABtrr-Ubq5z_Nx4-VA7gLgGMaxOBvfpSpXKJfeO9Q9C9eCA8Fg@mail.gmail.com> <CAJm22JazQHLN=zZ_RpAwYX5AcUuws6nan-4jShzLwSbz2ysHsQ@mail.gmail.com> <e88b630d-b979-185b-e744-977ab080baad@cs.tcd.ie> <CAJm22JbitJsoDDb=k7U7ocgCtMCNbGWoXpLZNDt0zvXz81YT0g@mail.gmail.com> <d9a145c9-8f18-4922-eade-2fa5361af7a6@cis-india.org> <a148823f-3501-b9a6-f460-eb85105c1e49@nomountain.net>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
Date: Sat, 18 May 2019 07:37:15 +0000
Message-ID: <5ziz8e.provu5.rtdbnh-qmf@mercury.scss.tcd.ie>
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/hrpc/FXO88aCM7_F6rq-Fk6-uEnfhIsg>
Subject: Re: [hrpc] [Pearg] descriptive censorship work: draft-hall-censorship-tech: move to hrpc?
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: Sat, 18 May 2019 07:37:25 -0000


On Saturday, 18 May 2019, Melinda Shore wrote:
> On 5/17/19 10:13 PM, Gurshabad Grover wrote:
> > If that is not happening (hope I'm not missing some more context), I
> > think this draft is more suitable for the hrpc rg.
> 
> Wearing no hats ...  I just reread the draft and I think it's
> an excellent piece of work that ought to be published, but I
> do not think it is particularly suitable as a research group
> product (either pearg or hrpc).  Let's find out why it hasn't
> moved forward so far and do what we can to remedy that, rather
> than using the IRTF to route around IETF roadblocks.
>

I don't  recall IETF roadblocks. When I was AD I was willing to sponsor but the draft didn't get done and IIUC it's just recently the authors got enough cycles to complete it. 

I still think pearg is the best current fit, as follow up work here would seem more likely, but if various RG chairs went into a huddle and got it moving that'd be fine, 

S. 

S

 
> Melinda
> 
> 
> 
> -- 
> Software longa, hardware brevis
> 
> PGP key fingerprint  4F68 2D93 2A17 96F8 20F2
>                      34C0 DFB8 9172 9A76 DB8F
> 
>

v2.23.0 | Report a Bug | By Email