RE: i18n name badges

Actually, I think RFID is much more expensive than bar codes, and
it's even more expensive the more you use it.

With barcode, you pay once for the readers.  Printing barcodes on badges
doesn't cost anything.  RFID tags cost money every time you make a badge,
plus the readers are what, 10X the cost of a barcode reader now?
RFID tags with storage are currently pretty expensive, and unnecessary, IMO.
Just a unique serial number and the registration database is sufficient.

I think we can make both optional.  Barcode is easily optional, just
don't swipe in.   I think you can easily lower the range of RFID so that
accidental swiping isn't likely.  You can also just decline to get the
barcode or RFID tag.

Brian  

> -----Original Message-----
> From: JORDI PALET MARTINEZ 
> [mailto:jordi(_dot_)palet(_at_)consulintel(_dot_)es]
> Sent: Wednesday, November 19, 2003 4:28 PM
> To: ietf(_at_)ietf(_dot_)org
> Subject: Re: i18n name badges
>
>
> It should be RFID, cheaper, and easier, not only for the blue sheets.
>
> The badge could be pre-configured with the data from our own 
> IETF registration.
>
> The badge will store the names of the people who we have been 
> talking during the week, and data like when, how much time, 
> .... We can then use an inexpensive reader to get a small 
> database out of it.
>
> Someone can complain about privacy issues, but I feel that is 
> the same now when the blue sheet is circulated, or the 
> attendance list is in the web site, right ?
>
> It will save a lot of time (money) to all of us, including 
> the IETF secretariat.
>
> Regards,
> Jordi
>
> ----- Original Message ----- 
> From: "Rosen, Brian" <Brian(_dot_)Rosen(_at_)marconi(_dot_)com>
> To: "'JORDI PALET MARTINEZ'" <jordi(_dot_)palet(_at_)consulintel(_dot_)es>; 
> <ietf(_at_)ietf(_dot_)org>
> Sent: Wednesday, November 19, 2003 10:14 PM
> Subject: RE: i18n name badges
>
>
> > Let's keep going.
> >
> > I'd contribute, say, $25, plus write some code towards 
> getting a barcode 
> > reader (or, maybe RFID??) for each meeting room that would 
> be used to 
> > "swipe in" and automate the "blue sheets".
> >
> > Brian
> >
> > > -----Original Message-----
> > > From: JORDI PALET MARTINEZ 
> > > [mailto:jordi(_dot_)palet(_at_)consulintel(_dot_)es]
> > > Sent: Wednesday, November 19, 2003 3:08 PM
> > > To: ietf(_at_)ietf(_dot_)org
> > > Subject: Re: i18n name badges
> > >
> > >
> > > Keith,
> > >
> > > I'm not sure if you are joking, but I think is an 
> excellent idea ...
> > > A badge communication protocol ... if you start with the 
> > > draft, I will be happy to contribute !
> > >
> > > Regards,
> > > Jordi
> > >
> > > ----- Original Message ----- 
> > > From: "Keith Moore" <moore(_at_)cs(_dot_)utk(_dot_)edu>
> > > To: "Peter Saint-Andre" <stpeter(_at_)jabber(_dot_)org>
> > > Cc: <moore(_at_)cs(_dot_)utk(_dot_)edu>; <ietf(_at_)ietf(_dot_)org>
> > > Sent: Wednesday, November 19, 2003 8:12 PM
> > > Subject: Re: i18n name badges
> > >
> > >
> > > > > Proposals for making email addresses fully 
> > > internationalized were a
> > > > > hot topic in Minneapolis. I'd like to suggest a more 
> > > modest reform:
> > > > > fully internationalized IETF name badges. IETF 59 
> might be a fine
> > > > > venue for rolling those out...
> > > > I'd love to see an Internet-Draft on the topic.  For 
> > > instance, should
> > > > the badges be able to list multiple versions of a 
> person's name and
> > > > affiliation?  How many versions?
> > > >
> > > > That, and it seems appropriate to demonstrate running code.
> > > > Set up a web form where an attendee can type in his own 
> names and
> > > > affiliations and have the backend generate a file to be 
> printed out.
> > > >
> > > **********************************
> > > Madrid 2003 Global IPv6 Summit
> > > Presentations and videos on line at:
> > > http://www.ipv6-es.com
> > >
> > > This electronic message contains information which may be 
> > > privileged or confidential. The information is intended to be 
> > > for the use of the individual(s) named above. If you are not 
> > > the intended recipient be aware that any disclosure, copying, 
> > > distribution or use of the contents of this information, 
> > > including attached files, is prohibited.
> > >
> > >
> > >
> > >
> > > _______________________________________________
> > > This message was passed through 
> > > ietf_censored(_at_)carmen(_dot_)ipv6(_dot_)cselt(_dot_)it, which is a 
> > > sublist of 
> > > ietf(_at_)ietf(_dot_)org(_dot_) Not all messages are passed. Decisions on 
> > > what 
> > > to pass are made solely by IETF_CENSORED ML Administrator 
> > > (ietf_admin(_at_)ngnet(_dot_)it).
> **********************************
> Madrid 2003 Global IPv6 Summit
> Presentations and videos on line at:
> http://www.ipv6-es.com
>
> This electronic message contains information which may be 
> privileged or confidential. The information is intended to be 
> for the use of the individual(s) named above. If you are not 
> the intended recipient be aware that any disclosure, copying, 
> distribution or use of the contents of this information, 
> including attached files, is prohibited.
>
>
>
>
> _______________________________________________
> This message was passed through 
> ietf_censored(_at_)carmen(_dot_)ipv6(_dot_)cselt(_dot_)it, which is a sublist 
> of 
> ietf(_at_)ietf(_dot_)org(_dot_) Not all messages are passed. Decisions on 
> what 
> to pass are made solely by IETF_CENSORED ML Administrator 
> (ietf_admin(_at_)ngnet(_dot_)it).