Networking

Available (317)

Showing 277 - 288 per page



Access Networks Working Group

The IEEE 1904 Access Networks Working Group (ANWG) uses an open and accredited process to develop standards for access networks. The Working Group technical expertise covers various optical access architectures based on Ethernet Passive Optical Networks (EPON), such as fiber-to-the-home, fiber-to-the-business, and cellular backhaul.

IEEE 1904

DySPAN-SC (IEEE P1900)

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.

TOSCA Simple Profile in YAML Version 1.2

The TOSCA Simple Profile in YAML specifies a rendering of TOSCA which aims to provide a more accessible syntax aswell as a more concise and incremental expressiveness of the TOSCA DSL in order to minimize the learning curve and speed the adoption of the use of TOSCA to portably describe cloud applications. This proposal describes a YAML rendering for TOSCA. YAML is a human friendly data serialization standard (http://yaml.org/) with a syntax much easier to read and edit than XML. As there are a number of DSLs encoded in YAML, a YAML encoding of the TOSCA DSL makes TOSCA more accessible by these communities.This proposal prescribes an isomorphic rendering in YAML of a subset of the TOSCA v1.0 XML specification ensuring that TOSCA semantics are preserved and can be transformed from XML to YAML or from YAML to XML. Additionally, in order to streamline the expression of TOSCA semantics, the YAML rendering is sought to be more concise and compact through the use of the YAML syntax.

Cloud computing - Functional requirements of Network as a Service

Recommendation ITU-T Y.3512 describes the concept of Network as a Service (NaaS) and its functional requirements. It provides typical use cases of NaaS and specifies the functional requirements of three aspects, ranging from NaaS application, NaaS platform and NaaS connectivity which are based on the corresponding uses cases and cloud capabilities types.
ITU-T Y.3512

Cloud computing – Functional architecture of Network as a Service

Recommendation ITU-T Y.3515 provides Network as a Service (NaaS) functional architecture by specifying functionalities and functional components as well as reference points for the operation support system (OSS). This Recommendation also describes the mapping between functionalities and functional requirements of NaaS, relationship between the NaaS functional architecture and software-defined networking (SDN), and illustrated usage of SDN and network functions virtualisation (NFV) in support of the NaaS functional architecture.
ITU-T Y.3515

Future networks: Objectives and design goals

Recommendation ITU-T Y.3001 describes objectives and design goals for future networks (FNs). In order to differentiate FNs from existing networks, four objectives have been identified: service awareness, data awareness, environmental awareness, and social and economic awareness. In order to realize these objectives, twelve design goals have been identified: service diversity, functional flexibility, virtualization of resources, data access, energy consumption, service universalization, economic incentives, network management, mobility, optimization, identification, reliability and security. This Recommendation assumes that the target timeframe for FNs falls approximately between 2015 and 2020. Appendix I describes technologies elaborated in recent research efforts that are likely to be used as an enabling technology for each design goal.
ITU-T Y.3001

CLOUD;
Test Descriptions for Cloud Interoperability

The present document specifies Interoperability Test Descriptions (TDs) for OCCI and CDMI standards. The Test Descriptions cover the OCCI and CDMI protocol specifications where relevant and more specifically:

  • OCCI interoperability testing, to prove that end-to-end functionality is as required by the standard.
  • CDMI interoperability testing, to prove that end-to-end functionality is as required by the standard.
  • OCCI + CDMI interworking testing, to prove that end-to-end functionality is as required by the standards.

 

TS 103 142 V1.1.1

Network Functions Virtualisation (NFV); Use Cases

The scope of the present document is to describe use cases of interest for Network Functions Virtualisation (NFV). It updates and extends ETSI GS NFV 001 V1.1.1

The present document provides a review of previous use cases and adds some new use cases in the context of virtualisation that are related to emerging 5G features such as the Network Slicing concept, enhanced Security, IOT virtualisation.

  • Use Case #1: Network Function Virtualisation Infrastructure as a Service (NFVIaaS)
  • Use Case #2: VNF Forwarding Graphs
  • Use Case #3: Virtualisation of Mobile Core Network and IMS
  • Use Case #4: Virtualisation of Mobile base station
  • Use Case #5: Virtualisation of the Home Environment
  • Use Case #6: Virtual Content Delivery Network (vCDN) - Fulfilment
  • Use Case #7: Fixed Access Network Functions Virtualisation
  • Use Case #8: Crypto as a Service (CaaS)
  • Use Case #9: Network Slicing
  • Use Case #10: Virtualisation of Internet of Things (IoT)
  • Use Case #11: Rapid Service Deployment
  • Use Case #12: Devops/CI/CD
  • Use Case #13: A/B testing
  • Use Case #14: VNF composition across multiple administrative domains
  • Use Case #15: Security as a Service (SecaaS)

The order of use cases is not intended to give any priority amongst use cases.

These service models and use cases are intended to clarify the roles and interactions of the various types of commercial entities acting in a marketplace for services delivered via these VNFs. These actors include commercial entities/roles such as Service Providers, Enterprises, Consumers, etc. The fields of application provide high level descriptions of areas where the industry believes NFV technologies can be applied and which are representative of the business and technical challenges to be overcome.

The service models and use cases described in the present document are intended to provide a commercial and technical context that is expected to be useful for discussions to be handled s in further specifications to be developed by the NFV ISG. Other Industry forums may also find these service models and use cases helpful as they consider implementation options for virtualisation of the network functions they have previously standardized. The present document is not intended to provide detailed behavioural modelling of components of the NFV framework. Future documents describing additional components of the NFV framework may develop additional use cases to illustrate the behaviour of those NFV framework components; those components of the NFV framework, however, should be validated against the service models and fields of application described in the present document for consistency

GR NFV 001 V1.2.1

Network Functions Virtualisation (NFV); Architectural Framework

The present document describes the high-level functional architectural framework and design philosophy of virtualised network functions and of the supporting infrastructure. The document also defines the scope of the NFV Industry Specification Group (ISG) activities to realize this framework.
 
The purpose of the present document is to abstract the overall problem space in such a way that the requirements and aspects unique to NFV (ETSI GS NFV 004: "Network Functions Virtualisation (NFV); Virtualisation Requirements") are clearly identified so that the work can be scoped and organized. The resulting network architectural framework aims at positioning NFV among relevant telecommunications and IT industry stakeholders, including network operators, solution vendors, service integrators and providers, as well as serving as a reference to NFV ISG working groups.
 
Another purpose of the present document is to provide guidance to the industry Standards Development Organizations (SDOs) to align existing network related specifications with the NFV architectural framework outlined in the present document. Any further standardization of network functions, architecture and interfaces that are required to properly operate in a virtualised environment will be carried out in relevant SDOs. The resulting standards are expected to support the NFV high-level architectural requirements for both intra- and inter-provider domains.

GS NFV 002 V1.2.1

Network Functions Virtualisation (NFV); Terminology for Main Concepts in NFV

The present document provides terms and definitions for conceptual entities within the scope of the ISG NFV, in order to achieve a "common language" across all the ISG NFV working groups.

GS NFV 003 V1.4.1

Network Functions Virtualisation (NFV); Virtualisation Requirements

The present document specifies the requirements that Telecommunications operations put on Network Functions Virtualisation in order to consolidate network equipment, belonging to fixed and mobile networks, onto industry standard high volume servers, switches and storage, which could be located in N-PoPs, Network Nodes and in end user premises.
 
The present document addresses the requirements in the following areas:

  • Portability/Interoperability
  • Performance
  • Management and Orchestration
  • Elasticity
  • Security
  • Resiliency
  • Network Stability
  • Service Continuity
  • Operations
  • Energy Efficiency
  • Migration and co-existence with existing platforms

The present document addresses the requirements to facilitate the assignment of infrastructure resources to virtual network functions. Specific NFV requirements will focus primarily on the differences introduced by the Network Functions Virtualisation (NFV) process, and not on aspects of the Network Functions (NF) interfaces, protocols and management that are identical whether the implementation is physical or virtual.

GS NFV 004 V1.1.1

LAN/MAN Standards Committee


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.

IEEE 802