Re: [perpass] perpass: what next?
Michael Richardson <mcr+ietf@sandelman.ca> Fri, 17 April 2015 14:02 UTC
Return-Path: <mcr@sandelman.ca>
X-Original-To: perpass@ietfa.amsl.com
Delivered-To: perpass@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2FF8F1B2D08 for <perpass@ietfa.amsl.com>; Fri, 17 Apr 2015 07:02:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.311
X-Spam-Level:
X-Spam-Status: No, score=-1.311 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, J_CHICKENPOX_32=0.6, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=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 isIcEz1QC_A9 for <perpass@ietfa.amsl.com>; Fri, 17 Apr 2015 07:02:47 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 153231B2D10 for <perpass@ietf.org>; Fri, 17 Apr 2015 07:02:35 -0700 (PDT)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 24BC1E033 for <perpass@ietf.org>; Fri, 17 Apr 2015 10:13:48 -0400 (EDT)
Received: by sandelman.ca (Postfix, from userid 179) id E178563B76; Fri, 17 Apr 2015 10:02:32 -0400 (EDT)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id CC9F9636B6 for <perpass@ietf.org>; Fri, 17 Apr 2015 10:02:32 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: perpass <perpass@ietf.org>
In-Reply-To: <5530EEAB.5050601@cs.tcd.ie>
References: <5530EEAB.5050601@cs.tcd.ie>
X-Mailer: MH-E 8.6; nmh 1.3-dev; GNU Emacs 24.4.2
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha1"; protocol="application/pgp-signature"
Date: Fri, 17 Apr 2015 10:02:32 -0400
Message-ID: <25042.1429279352@sandelman.ca>
Sender: mcr@sandelman.ca
Archived-At: <http://mailarchive.ietf.org/arch/msg/perpass/XgwTBzir5HooH6oWipZPGr7C2R0>
Subject: Re: [perpass] perpass: what next?
X-BeenThere: perpass@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "The perpass list is for IETF discussion of pervasive monitoring. " <perpass.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/perpass>, <mailto:perpass-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/perpass/>
List-Post: <mailto:perpass@ietf.org>
List-Help: <mailto:perpass-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/perpass>, <mailto:perpass-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 17 Apr 2015 14:02:50 -0000
Stephen Farrell <stephen.farrell@cs.tcd.ie> wrote: > While I do have some ideas, I'd rather not skew the discussion by > throwing those out right now. I will also report back here after > the IESG discussion. > And just as a reminder, we've used this list mostly for very > initial discussions and seen all chunky items of work handled > elsewhere, be that in current WGs or by forming new WGs or > whatever. I think that's been a good mode of operation so far, > so we're not really asking here about how to change that, but > rather for discussion of which topics we can usefully try handle > in that same way over the coming year or two. I think that the items have been correctly chunked off, and I think that waiting is not yet complete, so we can not yet grok what the next step is. I think that the ACME work is very significant, and once it is further along, I think that extending it into non-web-server realms is important. The biggest issue that I see in the perpass space has been persistent market failures of some of our key technologies. Not entirely our problem, but each time I see an industry "consortia" write a specification behind closed doors that is more than a list of RFCs, I think we have failed. Among groups that I have observed the Broadband Forum has done the best job in my opinion. This is very much a case where there has been a significant gap between what we specify, and what there are resources to actually implement *AND* deploy. I wish that the consortia could be involved in funding and coordinating open source reference implementations. The Eclipse and Apache foundations are sometimes really good at this, but they also seem to go and invent new specifications at times for reasons I think has more to do who is funding them than what is needed. So my message to the IESG for your retreat is: how can the IETF better leverage ISOC's contacts and marketing efforts... How can we make IETF work (including "running code") more relevant to things like Tenure Track committees... can we "infiltrate" NSF-like entities in various places. Many ccTLD entities seem to have money to spend on infrastructure initiatives (CIRA, nic.cz, nic.nl, nic.mx are the ones I know about)... maybe there could be some overt coordination here. -- ] Never tell me the odds! | ipv6 mesh networks [ ] Michael Richardson, Sandelman Software Works | network architect [ ] mcr@sandelman.ca http://www.sandelman.ca/ | ruby on rails [
- Re: [perpass] perpass: what next? John Levine
- [perpass] perpass: what next? Stephen Farrell
- Re: [perpass] perpass: what next? Michael Richardson
- Re: [perpass] perpass: what next? Mike Liebhold
- Re: [perpass] perpass: what next? Watson Ladd
- Re: [perpass] perpass: what next? Stephen Farrell
- Re: [perpass] perpass: what next? Tim Bray
- Re: [perpass] perpass: what next? Adam Caudill
- Re: [perpass] perpass: what next? Paul Wouters
- Re: [perpass] perpass: what next? carlo von lynX
- Re: [perpass] perpass: what next? Mike Liebhold
- Re: [perpass] perpass: what next? Watson Ladd
- Re: [perpass] perpass: what next? carlo von lynX
- Re: [perpass] perpass: what next? Joseph Lorenzo Hall
- Re: [perpass] perpass: what next? Christian Huitema
- Re: [perpass] perpass: what next? Stefan Winter
- Re: [perpass] perpass: what next? Michael Richardson
- Re: [perpass] perpass: what next? Ted Lemon
- Re: [perpass] perpass: what next? Mike Liebhold
- Re: [perpass] perpass: what next? Stefan Winter
- Re: [perpass] perpass: what next? Stefan Winter
- Re: [perpass] perpass: what next? Stephen Farrell
- Re: [perpass] perpass: what next? Kathleen Moriarty