Re: [76attendees] RFID

"George, Wes E [NTK]" <Wesley.E.George@sprint.com> Tue, 10 November 2009 01:48 UTC

Return-Path: <Wesley.E.George@sprint.com>
X-Original-To: 76attendees@core3.amsl.com
Delivered-To: 76attendees@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 13B563A68E0 for <76attendees@core3.amsl.com>; Mon, 9 Nov 2009 17:48:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.499
X-Spam-Level:
X-Spam-Status: No, score=-3.499 tagged_above=-999 required=5 tests=[AWL=0.100, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8RdxpadVMBA8 for <76attendees@core3.amsl.com>; Mon, 9 Nov 2009 17:48:46 -0800 (PST)
Received: from VA3EHSOBE002.bigfish.com (va3ehsobe002.messaging.microsoft.com [216.32.180.12]) by core3.amsl.com (Postfix) with ESMTP id 302903A67AF for <76attendees@ietf.org>; Mon, 9 Nov 2009 17:48:46 -0800 (PST)
Received: from mail180-va3-R.bigfish.com (10.7.14.253) by VA3EHSOBE002.bigfish.com (10.7.40.22) with Microsoft SMTP Server id 8.1.240.5; Tue, 10 Nov 2009 01:49:12 +0000
Received: from mail180-va3 (localhost.localdomain [127.0.0.1]) by mail180-va3-R.bigfish.com (Postfix) with ESMTP id 368CB16581F6; Tue, 10 Nov 2009 01:49:12 +0000 (UTC)
X-SpamScore: -42
X-BigFish: VS-42(zz542N98dN4015L9371Pzz1202hzz1033ILz2fh6bh87h43j61h)
X-Spam-TCS-SCL: 0:0
X-FB-DOMAIN-IP-MATCH: fail
Received: from mail180-va3 (localhost.localdomain [127.0.0.1]) by mail180-va3 (MessageSwitch) id 1257817751764110_26519; Tue, 10 Nov 2009 01:49:11 +0000 (UTC)
Received: from VA3EHSMHS029.bigfish.com (unknown [10.7.14.246]) by mail180-va3.bigfish.com (Postfix) with ESMTP id AC75775004C; Tue, 10 Nov 2009 01:49:11 +0000 (UTC)
Received: from pdas1403.corp.sprint.com (144.229.32.12) by VA3EHSMHS029.bigfish.com (10.7.99.39) with Microsoft SMTP Server (TLS) id 14.0.482.32; Tue, 10 Nov 2009 01:49:11 +0000
Received: from PLSWH02A.ad.sprint.com (PLSWH02A.corp.sprint.com [144.226.242.131]) by pdas1403.corp.sprint.com (Switch-3.3.2/Switch-3.3.2) with ESMTP id nAA1jaLX004482 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 9 Nov 2009 19:45:36 -0600 (CST)
Received: from PLSWM01C.ad.sprint.com ([144.226.242.77]) by PLSWH02A.ad.sprint.com ([2002:90e2:f283::90e2:f283]) with mapi; Mon, 9 Nov 2009 19:49:10 -0600
From: "George, Wes E [NTK]" <Wesley.E.George@sprint.com>
To: "John G. Scudder" <jgs@juniper.net>, Fred Baker <fred@cisco.com>
Date: Mon, 9 Nov 2009 19:49:06 -0600
Thread-Topic: [76attendees] RFID
Thread-Index: AcphoxvBFDidkRodS4qY94GkvjTjwgAAdWSA
Message-ID: <F7EB0A7C707E39409A73CD0353242551A8873B2F02@PLSWM01C.ad.sprint.com>
References: <7BAB4E87-5B63-4FC9-A6CF-576EB180A6C0@cisco.com> <F7584C95-7C4F-4741-AB44-CB68B36D8937@juniper.net>
In-Reply-To: <F7584C95-7C4F-4741-AB44-CB68B36D8937@juniper.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Reverse-DNS: unknown
Cc: "76attendees@ietf.org" <76attendees@ietf.org>
Subject: Re: [76attendees] RFID
X-BeenThere: 76attendees@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <76attendees.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/76attendees>, <mailto:76attendees-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/76attendees>
List-Post: <mailto:76attendees@ietf.org>
List-Help: <mailto:76attendees-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/76attendees>, <mailto:76attendees-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 10 Nov 2009 01:48:47 -0000

I like the concept. I do not have privacy concerns, given that even if you could determine the link between the RFID and my account, for your trouble you are the proud owner of mostly useless information, a lot of which you probably already know. It's not like the system asks for any sort of personal info that could be used maliciously (nor should it).
I would argue that if you are actually that interested in me (or any other attendee) that there are much easier ways to get more useful information about me than to try to compromise a benign RFID system.

I echo John's comments - too many instances of reader issues, site login problems, incorrect room/reader associations leading to incorrect records for this to be quite ready for primetime as a replacement for the bluesheets, but a great idea, and one we should continue to refine.

I would recommend that if the folks undertaking this experiment are willing, we continue with the experiment for the next few meetings in order to work the kinks out and enhance the system (such as populating on Jabber/audio), perhaps with a dedicated mailing list for RFID issues/suggestions.

Thanks,
Wes

-----Original Message-----
From: 76attendees-bounces@ietf.org [mailto:76attendees-bounces@ietf.org] On Behalf Of John G. Scudder
Sent: Monday, November 09, 2009 8:12 PM
To: Fred Baker
Cc: 76attendees@ietf.org
Subject: Re: [76attendees] RFID

On Nov 10, 2009, at 9:59 AM, Fred Baker wrote:
> What do people think of it? Is it useful/interesting? If we were to

I'll go with "interesting".  As for "useful", so far IMO the rough
edges make this particular implementation a net negative -- in several
meetings I've been in, various RFID reader related gremlins have
interrupted the flow of the meeting.  To get to "useful" the
probability of needing to interrupt your train of thought and futz
with the tech would have to be at least an order of magnitude less.  I
don't mind, that's why it's an experiment.

--John
_______________________________________________
76attendees mailing list
76attendees@ietf.org
https://www.ietf.org/mailman/listinfo/76attendees


This e-mail may contain Sprint Nextel Company proprietary information intended for the sole use of the recipient(s). Any use by others is prohibited. If you are not the intended recipient, please contact the sender and delete all copies of the message.