IEEE 802 JTC1 Standing Committee formalization proposal July 2010 doc.: IEEE 802.11-10/0xxxr0 IEEE 802 JTC1 Standing Committee formalization proposal 13 Mar 2014 Authors: Name Company Phone email Andrew Myles Cisco +61 2 84461010 +61 418 656587 amyles@cisco.com Andrew Myles, Cisco Andrew Myles, Cisco

It is proposed that the status of the IEEE 802 JTC1 Standing Committee be formalised … The IEEE 802.11 JTC1 ad hoc was created many years ago to deal with liaison issues between the IEEE 802.11 WG and ISO/IEC JTC1/SC6 In about November 2010, as the result of ad hoc discussion by the IEEE 802 ExCom, it expanded its scope to all IEEE 802 matters At about that time the ad hoc changed its name to IEEE 802 JTC1 Standing Committee at the direction of the IEEE 802 EC Chair It is unclear whether this status and name change were ever formalised by the IEEE 802 EC, although both changes were accepted by default It is proposed that the status of the Standing Committee now (March 2014) be formalised by a motion by the IEEE 802 EC It is proposed that the scope of the Standing Committee remain the same as that decided by the IEEE 802 EC ad hoc in November 2010 Andrew Myles, Cisco

… with a scope that is the same as that used since November 2010 July 2010 doc.: IEEE 802.11-10/0xxxr0 … with a scope that is the same as that used since November 2010 Agreed goals from November 2010 Provides a forum for 802 members to discuss issues relevant to both: IEEE 802 ISO/IEC JTC1/SC6 Recommends positions to ExCom on ISO/IEC JTC1/SC6 actions affecting IEEE 802 Note that IEEE 802 LMSC holds the liaison to SC6, not the IEEE 802.11 WG Participates in dialog with IEEE staff and 802 ExCom on issues concerning IEEE’s relationship with ISO/IEC Organises IEEE 802 members to contribute to liaisons and other documents relevant to the ISO/IEC JTC1/SC6 members Andrew Myles, Cisco Andrew Myles, Cisco

The SC document reflector will continue to be hosted by IEEE 802.11 WG The SC document reflector has been hosted by the IEEE 802.11 WG on Mentor for many years It is proposed the hosting not change, to maintain continuity Andrew Myles, Cisco