The IEEE 802.21 Working Group on Media access Independent Services (MIS) developed standards that enabled optimization of higher layer services including IoT and handover services when performed between heterogeneous IEEE 802 networks. The MIS framework is also applicable when networking between IEEE 802 networks and Cellular networks.
The IEEE P1900 Standards Committee, DySPAN-SC's predecessor, was established in the first quarter 2005 jointly by the IEEE Communications Society (ComSoc) and the IEEE Electromagnetic Compatibility (EMC) Society. The objective of the effort was to develop supporting standards dealing with new technologies and techniques being developed for next generation radio and advanced spectrum management. On 22 March 2007, the IEEE Standards Association Standards Board approved the reorganization of the IEEE 1900 effort as Standards Coordinating Committee 41 (SCC41), "Dynamic Spectrum Access Networks (DySPAN)". The IEEE Communications Society and EMC Society were supporting societies for this effort, as they were for the IEEE 1900 effort.
IEEE SCC41 was approached by the IEEE ComSoc Standards Board (CSSB) in late 2010, as ComSoc Standards Board was extremely interested in SCC41 being brought back directly under its wing. SCC41 voted to be directly answerable to ComSoc in December 2010, and was thereby renamed as IEEE DySPAN-SC. At its December 2010 Meeting, the IEEE Standards Association Standards Board (SASB) approved the transfer of projects from SCC41 to CSSB.
A framework of Internet Protocol (IP)-based service overlay networks is described and context-aware [e.g., such as required Quality of Service (QoS) level; type of service such as real time versus data; nature of data stream such as I-frame versus B-frame; and type of terminal such as TV monitor versus personal digital assistant], dynamically adaptive (e.g., using locally derived information to discover, organize, and maintain traffic flows in the network within a local area network), and self-organizing networking capabilities (e.g., developing network structures based on the needs of the customers and the capabilities of existing network structures), including advanced routing and forwarding schemes, that are independent of underlying networks, are specified in this Next Generation Service Overlay Network (NGSON) standard. The NGSON architecture provides advanced service- and transport-related functions to support context-aware, dynamically adaptive, and self-organizing networks. This standard specifies a functional architecture for NGSON. The functional architecture consists of a set of functional entities (FEs), their functions, reference points, and information flows to illustrate service interaction and media delivery among FEs and external components. NGSON may operate with different underlying networks such as IP Multimedia Subsystem (IMS), next generation network (NGN), peer-to-peer (P2P) overlay, or Web to transmit NGSON signaling messages and/or media among its users and services.
The IEEE 802 LAN/MAN Standards Committee develops and maintains networking standards and recommended practices for local, metropolitan, and other area networks, using an open and accredited process, and advocates them on a global basis. The most widely used standards are for Ethernet, Bridging and Virtual Bridged LANs Wireless LAN, Wireless PAN, Wireless MAN, Wireless Coexistence, Media Independent Handover Services, and Wireless RAN. An individual Working Group provides the focus for each area.
Standardization of information, communication and control systems in the field of urban and rural surface transportation, including intermodal and multimodal aspects thereof, traveller information, traffic management, public transport, commercial transport, emergency services and commercial services in the intelligent transport systems (ITS) field.
Given the longstanding and fervent belief in the value for incident sharing, new advancements in enabling technology, and the promising shifts in the legal landscape, the Cloud Security Alliance believes now is the time to act. For this reason we introduce the Cloud Cyber Incident Sharing Center or Cloud-CISC.
From a user perspective, Cloud is a service. However, for Cloud Service Providers, integrators and channel partners who construct or build the Cloud, the Cloud architecture is comprised of many Cloud computing components. Examples of these components are hypervisors, Cloud operating systems components such as “Swift”, “Glance” for OpenStack, virtual desktop infrastructure platforms, cloud dedicated firewalls and so on. How can we evaluate the security of these Cloud components? Currently, most of the security standards related to Cloud Computing focus on the information security management system. However, these standards are insufficient to evaluate cloud component security because they focus on management security rather than the technical security requirements of the components. In order to address this gap, the Cloud Component Specifications working group proposes to develop internationally recognized technical security specifications for cloud components.
The Cloud Key Management Working Group aims to facilitate the standards for seamless integration between CSPs and key broker services. Standardization will take place across key management lifecycle operations and a common set of APIs, enabling consistent implementation of enterprise key policies. Customer-centric in principle, the goal will be for data stored or traversing the cloud and requiring encryption the corresponding encryption keys will be protected and their lifecycle managed by the customer. The purpose of the Cloud Key Management Working Group is to align cloud key management interoperability standards across service providers, maintain and develop API and key interoperability specifications, develop business model templates and specifications for standardized key interoperability, promote the adoption of key management standards and key brokering interoperability, and provide well documented guidelines and a standard approach to vendors to ensure seamless interoperability and compliance to those guidelines/standards.
The Enterprise Resource Planning (ERP) WG seeks to develop best practices to enable organizations that run their business on large ERP implementations, such as SAP or Oracle applications, to securely migrate to and operate in cloud environments. Every ERP deployment is something that is unique to each organization. In most cases organizations spend months if not years customizing their SAP or Oracle implementations and also spend a significant amount of money with third party contractors to get the implementations done. This makes standard security measures more difficult to implement due to the differences of each deployment. With the complexity of these large implementations, combined with the criticality of data and processes housed in these applications, it is imperative that industry best practices be established to provide companies with security guidelines when migrating to the cloud in order to protect the organization’s critical infrastructure.
The Financial Services Stakeholders Platform main objective is to identify and share the challenges, risks and best practices for the development, deployment and management of secure cloud services in the financial services industry.
The Health Information Management Working Group aims to provide direct influence on how health information service providers deliver secure cloud solutions (services, transport, applications and storage) to their clients, and foster cloud awareness within all aspects of healthcare and related industries.
