Dear 802.11 members,
For your information… please see below.
If you have an opinion/comments on this PAR, please provide it to any member of NesCom.
Best Regards,
Adrian P STEPHENS
Tel: +44 (1793) 404825 (office)
Tel: +44 (7920) 084 900 (mobile, UK)
Tel: +1 (408) 2397485 (mobile, USA)
----------------------------------------------
Intel Corporation (UK) Limited
Registered No. 1134945 (England)
Registered Office: Pipers Way, Swindon SN3 1RJ
VAT No: 860 2173 47
From: ***** IEEE 802 Executive Committee List ***** [mailto:STDS-802-SEC@xxxxxxxx]
On Behalf Of Paul Nikolich
Sent: 05 September 2014 15:41
To: STDS-802-SEC@xxxxxxxxxxxxxxxxx
Subject: [802SEC] proposed project your group may have an interest in--P1912 Geo-proximity IP/RFID/Wireless Enabled Device Architecture
In reviewing the agenda for the upcoming 09OCT IEEE SA NesCom meeting, I noticed a project that your group may have an interest in, the Communications Society draft PAR, P1912 Geo-proximity
IP/RFID/Wireless Enabled Device Architecture. I've copied the details below.
Please share this with your WG as appropriate and provide comments to NesCom. I believe Jon Rosdahl is the sole 802 representative on NesCom this year and Lisa Weisser is the administrator
l.weisser@xxxxxxxx.
Submitter Email: mail@xxxxxxxxxxxxxxx
Type of Project: New IEEE Standard
PAR Request Date: 25-Aug-2014
PAR Approval Date:
PAR Expiration Date:
Status: Unapproved PAR, PAR for a New IEEE Standard
1.1 Project Number: P1912
1.2 Type of Document: Standard
1.3 Life Cycle: Full Use2.1 Title: Common
Architectural Standard for Geo-proximity IP/RFID/Wireless Enabled Devices for Privacy, Authentication, Non-Repudiation, and Information Assurance
3.1 Working
Group: Requested: COM/SBA/1912_Architectural Standard for Secure and Private Multi-directional Recognition
and Communication Among Disparate End User IP/RFID//Wireless or Other Remote Communication Technology Within Limited Parameters Set by Users for personal and in Home or Office Settings (COM/SDB/P1912)
3.2 Sponsoring
Society and Committee: IEEE Communications Society/Standards Development Board (COM/SDB)
Contact Information for Sponsor Chair
Name: Mehmet Ulema
Email Address: m.ulema@xxxxxxxx
Phone: +1 732 957-0924
Contact Information for Standards Representative
Name: Mehmet Ulema
Email Address: m.ulema@xxxxxxxx
Phone: +1 732 957-0924
4.1 Type of Ballot: Individual
4.2 Expected Date of submission of draft to the IEEE-SA for Initial Sponsor Ballot: 09/2014
4.3 Projected Completion Date for Submittal to RevCom: 08/2017
5.1 Approximate number of people expected to be actively involved in the development of this project: 100
5.1 Approximate number of people expected to be actively involved in the development of this project: 100
5.2 Scope: This standard lays the technical foundation for an architectural standard for a common communication protocol for enabling assignable
relationships among disparate digital wireless technologies using unique identifiers that are inherent in the technology or can be assigned by users, through subnets or private geo/location-proximity fencing protocols that relies on user assignable physical
location and digital relationships among owner/user devices. The resulting architecture will permit end users/consumers' establishment of an array of subnets among two or more devices to support the equivalent of private GPS systems within a radius defined
by radial points or bounded interior spaces or geo-locations by use of enduser wireless technology sharing a common architecture. This architectural standard does not prescribe the data security within devices. This architectural standard does not prescribe
network applications, communication protocols nor the facilitation of information/data exchange in a networked environment. This architectural standard does not define an approach for deployment of the technology that may incorporate this standard. The architectural
standard defines communication, security, and privacy protocols to support end user private use of the wireless communication capacity of wireless enabled technology within discrete boundaries. The architecture will address the parameters to enable disparate
wireless devices to act in concert to designate micro-fences within the larger geo-locations such as one bounded by a structure or created by devices associated with a user. The architecture will support users election to delineate prohibited and approved
zones for access or use based on user designations.
5.3 Is the completion of this standard dependent upon the completion of another standard: No
5.4 Purpose: The proliferation of wireless digital devices and their potential for creating new opportunities for consumers to better manage
personal digital devices, user content, or wireless technology as well as for making life less complex, can be addressed by a common underlying architecture that supports communication among disparate wireless technology. A common architecture will allow applications,
devices and services that support users' ability to establish uses not inherent to a particular wireless products' design or concept will make possible new markets for components of wireless communication technology, as well as increased consumption of wireless
enabled devices and technology. Establishing a common architecture will support end user ease of use of security and privacy options. The common architecture can support unique device recognition among wireless digital devices and technology. "Establishing
a common architecture will allow standards development based on this standard for a range of applications and digital technologies. Ultimately, the standard can aid in preventing theft, abuse or misuse of digital devices and information and in increasing privacy,
while at the same time reducing reliance upon passwords or PINs to establish that the possessor of a device is legitimate. Social and cultural adoption of technology requires greater security and ease of securing IP enabled digital devices. This foundational
architectural protocol will support a level of flexibility in the methods that may be employed by users to exert control over or access to owner or user content of wireless digital devices. Data access gateways that do not rely solely on passwords for security
and privacy would free up time and resources devoted to password retrieval, assignment, reassignment and layering of security features for consumer end user technology. This architecture can also address macro-security and safety issues in the interior or
immediate exterior of private homes and commercial spaces, with the potential of making these environments safer. Establishment of this protocol provides an opportunity to voluntarily achieve greater consumer and user control over physical devices and technology
that fit the unique needs of individual users. Adoption of the standard will extend greater control to owners or legitimate users through a common architecture, while supporting innovation and broad adoption of IP/RFID/Wireless or other remote communication
enabled devices and technology.
5.5 Need for the Project: A common architecture will allow applications, devices and services that support users' ability to establish uses
not inherent to a particular wireless products' design or concept will make possible new markets for components of wireless communication technology, as well as increased consumption of wireless enabled devices and technology. Establishing a common architecture
will support end user ease of use of security and privacy options.
5.6 Stakeholders for the Standard: Stakeholders for this architectural standard include remote communication technology manufactures, component
wireless and remote communication technology providers, device and technology end-users, OEM, After market suppliers, wholesalers, retailers, medical device users, NFC users, developers and suppliers, and IoT manufacturers, service providers and end-users.
---------- This email is sent from the 802 Executive Committee email reflector. This list is maintained by Listserv.
_______________________________________________________________________________
If you wish to be removed from this reflector, do not send your request to this reflector - it will have no effect.