[hiaps] BOF scheduling Call update.

joel jaeggli <joelja@bogus.com> Thu, 23 January 2014 02:03 UTC

Return-Path: <joelja@bogus.com>
X-Original-To: hiaps@ietfa.amsl.com
Delivered-To: hiaps@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1FD081A0213 for <hiaps@ietfa.amsl.com>; Wed, 22 Jan 2014 18:03:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.435
X-Spam-Level:
X-Spam-Status: No, score=-2.435 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.535] autolearn=ham
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 fj7YaIYyuiAf for <hiaps@ietfa.amsl.com>; Wed, 22 Jan 2014 18:03:50 -0800 (PST)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id B1EC11A0220 for <hiaps@ietf.org>; Wed, 22 Jan 2014 18:03:50 -0800 (PST)
Received: from mb-aye.local (c-50-174-18-221.hsd1.ca.comcast.net [50.174.18.221]) (authenticated bits=0) by nagasaki.bogus.com (8.14.7/8.14.7) with ESMTP id s0N23kkM091384 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Thu, 23 Jan 2014 02:03:48 GMT (envelope-from joelja@bogus.com)
Message-ID: <52E0787C.1050605@bogus.com>
Date: Wed, 22 Jan 2014 18:03:40 -0800
From: joel jaeggli <joelja@bogus.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:27.0) Gecko/20100101 Thunderbird/27.0
MIME-Version: 1.0
To: "hiaps@ietf.org" <hiaps@ietf.org>
X-Enigmail-Version: 1.6
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="Ht8pqmRRCFonSOVSMIgG7bdu3NXOTb0Vj"
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.4.3 (nagasaki.bogus.com [147.28.0.81]); Thu, 23 Jan 2014 02:03:50 +0000 (UTC)
Cc: Richard Barnes <rlb@ipv.sx>, Brian Haberman <brian@innovationslab.net>
Subject: [hiaps] BOF scheduling Call update.
X-BeenThere: hiaps@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Host Identification, Address and Prefix Sharing in Wi-Fi Access \(hiaps\)" <hiaps.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/hiaps>, <mailto:hiaps-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/hiaps/>
List-Post: <mailto:hiaps@ietf.org>
List-Help: <mailto:hiaps-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/hiaps>, <mailto:hiaps-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Jan 2014 02:03:52 -0000

Hi,

The BOF scheduling call was held this morning.

The feedback received was fairly unfavorable with respect to our
prospects, It has been decided not to include it in the schedule for
IETF 89 on that basis.

Some observations.

* With respect to emergency services use case Richard Barnes has
expressed an interest in socializing that with ecrit. There may also be
overlap with geopriv where useful work can be done.

* There is very active disinterest with respect to exposing additional
identifiers in a fashion that is visible to on-path observers. Evolving
sentiments regarding exposure to pervasive monitoring play into this. In
this respect the historical effort in this space e.g. RFC 6967  RFC 6269
is helpful insofar as it highlights the problems with some of the
potential approaches.

* Consent is another question when it comes to notionally signaling on
behalf of users. either for all packets/flows, some of them, or on the
basis of DPI, e.g. application awareness through inspection, there is
some assumption that applications should be resistant to the later for a
variety of reasons.

* The existing documents don't point in the direction that I feel can
get support from the current IESG and IAB, myself included.

* There does not at this time appear to be a critical-mass associated
with the proposed working-group and working group items.

Thank you for your forbearance.

joel