- This line was added.
- This line was removed.
- Formatting was changed.
ATA Work Area Project Streams and Projects
Project Deliverable and Document Numbering Note
Most projects use deliverable (e.g., tutorial slide deck) and document numbers assigned independent of inter-relation or project association. (e.g., TR-421, MR-433, MR-238, TR-224, TR-350, MR-367)
However, some deliverables or documents are numbered in a series associating them together as related or part of the same project using a suffix notation (e.g., TR-452.1, TR-452.2, TR-452.3, etc;. MR-452.1, MR-452.2, MR-452.3, etc.; TR-319 Base, TR-319 Part A, TR-319 Part B, etc.) The suffix, when used, is treated as an integral part of the document number for purposes of revision (e.g., TR.459.2 Issue 2), amendment (e.g. WT-390.2 Amendment 1), or correction (e.g., MD-521.2 Corrigendum 1). Note that the first deliverable in a series may or may not use the .1 suffix. (e.g., TR-459, TR-459.2, TR-459.3 vs. TR-452.1, TR-452.2, TR-452.3, etc., MR-521.1, MR-521.2, etc.).
Questions on ATA document numbering should be directed to the Work Area Directors.
Project Page: ATA New Project Initiation Forms (NPIFs)
Description: Proposed new projects for ATA or combination of Work Areas including ATA.
Project Stream Page: ATA Non-PS Assigned Projects
Description: Projects that don’t fit under the scope of an existing Project Stream or if they fit under the scope of more than one Project Stream, are developed under the Non-PS Assigned category.
Project Stream Page: Access Architecture (AA) Project Stream
Project Stream Leads: Jonathan Newton, Vodafone
The project stream mission is to advance access broadband network architecture in traditional and new areas to ensure quality connectivity leading to quality user experience. Identify and document the key functionalities and relationships between entities to facilitate the transition of networks to encompass new practices such as virtualization while documenting the key functionalities that need to be brought forward to enable a seamless evolution path.A critical element of the work is the long term support of existing and new physical and statically management network elements alongside agile and virtualized functions in what effectively will be a stable hybrid network. This enables seamless migration based on market acceptance on new technologies, protection of existing infrastructure investment and normal spread of deployment in different territories.The project stream will focus on:
The work creates the necessary foundation for all of the broadband network. It underpins new value-added services and application delivery for fixed access networks, for home and business that can now be deployed at the pace of each market. Co-existence of physical and virtualized solutions and from static and dynamic services will create a broadband network mitigating the risks to existing revenue and enabling market-paced migration. Drive evolution of the network to improve scale, resiliency, reliability and security.
Specifically the project stream covers the following areas:
Project Stream Page: Mobile Transport and Routing (MT&R) Project Stream
Project Stream Leads: David Sinicrope (GM), Ericsson
To produce industry agreed specifications of the routing and transport network infrastructure and solutions for the transport of traffic in mobile networks, including 2G, 3G, LTE and 5G mobile networks. This work typically being in the form of architecture, equipment requirements, interoperability and conformance test plans, implementation guidance and education materials.
This work accelerates industry adoption of new routing and transport technology and deployment of new services and infrastructure in mobile networks. The work includes the introduction of and migration to SDN and virtualization of the mobile transport network infrastructure where commercially viable.
Control, management and data plane for the IP layer down to the physical layers, including time and synchronization, OAM, routing, resiliency, scalability, security, virtualization of the mobile transport infrastructure, and enablement of software driven networking.
Project Stream Page: Performance, Experience, and Application Testing (PEAT) Project Stream
Project Stream Leads: Gregory Mirsky , Ericsson
The project stream mission is to advance testing in traditional and new areas to ensure quality connectivity leading to quality user experience.
The project stream will focus mainly in two areas:
Both are needed to provide insight into quality of experience and application outcomes such that the network, while essential, becomes an invisible part of the customer experience.
Provide the information needed to analyze a network’s detailed performance allowing service providers to offer not only higher capacity connectivity services, but also higher quality connectivity services.
This in turn enables and accelerates industry adoption and deployment of new services and infrastructure.
Specifically the project stream covers the following areas of connectivity quality testing:
Project Stream Page: Cloud Interconnect (CI) Project Stream
Project Stream Leads: David Sinicrope (GM), Ericsson
This project addresses architectures, requirements and use cases for providing interconnection between Cloud data centers.
Carrier Ethernet provides extensions to Ethernet enabling telecommunications network providers to provide Ethernet services to customers for multi service use, including cloud data center interconnection. Service providers are deploying Carrier Ethernet services around the globe, in large part, because Carrier Ethernet has compelling capabilities such as standardized service definitions as well as improved scalability, reliability, QoS, and manageability.
Carrier Ethernet services are being used in Broadband access networks, enterprise networks and backhaul networks. This deliverables for this project provides technical architecture and equipment requirements implementing the specified Ethernet services using various technologies, e.g., with an MPLS EVPN network. By specifying a common technical architecture, common equipment requirements and common set of feature options, this project promotes multi-vendor interoperability of cloud interconnect services, networks and equipment. e.g,. EVPN for support of MEF Carrier Ethernet services.
Currently the project focuses on data center interconnect via Ethernet and Ethernet Services and their implementation using BGP MPLS based Ethernet VPNs (EVPN) in IP/MPLS network. While at the current time this involves networks providing Carrier Ethernet connectivity, other interconnection technologies are not excluded.
WT-224 and WT-178 provide architecture and nodal requirements to support broadband multi-service networks and MEF carrier Ethernet services. They use VPWS and VPLS in IP/MPLS networks and provides how service parameters are supported in MPLS network.
New Ethernet service applications require capabilities such as: multi-homing with all-active forwarding; load balancing; policy based control, and control plane MAC learning. WT-224 and WT-178 based solutions do not provide these features; solutions based on BGP MPLS EVPNs do.
This project also considers, the work underway in the IETF, specify how Ethernet Provider Backbone Bridging [802.1ah] can be combined with EVPN.
Through its deliverables, (i.e., TRs, MRs, Tutorials), this project will specify how to implement the Ethernet service layer to provide cloud interconnect connectivity. It will not specify the service layer itself. Ethernet Control and OAM protocols will be transparently transported, except for cases where Layer 2 control protocol processing is required by the service definition.
In order to support Carrier Ethernet services for cloud interconnect across multiple networks the project will addresses multiple autonomous systems and the preservation of end-to-end capabilities (e.g., OAM, QoS and protection etc).
Project Page: Packet Optical Evolution (POE) Project Stream
Project Stream Leads: David Sinicrope (GM), Ericsson u
Mission:To produce industry agreed specifications of the routing and transport network infrastructure and solutions for the integration of packet and optical technologies, including DWDM, Ethernet, MPLS and IP. This work typically being in the form of architecture, equipment requirements, interoperability and conformance test plans, implementation guidance and education materials.
Business Impact:This work accelerates industry adoption of new routing and transport technology and deployment of new services and infrastructure in optical and packet infrastructure networks. The work includes the introduction of and migration to SDN and virtualization of the packet optical transport network infrastructure where commercially viable.
This work leverages the optical and packet technologies defined in other organizations such as ITU-T SG15, OIF, IETF, IEEE and brings them together for integrated packet optical solutions, architecture and equipment requirements.
Work Area Overview
The Access and Transport Architecture (ATA) Work Area (WA) defines and specifies the architecture and equipment requirements for access, routing and transport network infrastructure. ATA produces industry-agreed specifications for applications such as mobile transport infrastructure (fronthaul and backhaul), data center interconnect, broadband Internet access, etc. as well as specifications for managing, testing, and maintaining these networks and their applications. This work typically takes the form of architecture, equipment requirements, test & implementation guidance, and education materials.
Work Area Directors:
A critical element of the work is the long term support of existing network elements alongside virtualized software based network functions, resulting in a stable network that may be evolved over time. This enables seamless migration of new networking technologies based on their market acceptance, at the same time protecting existing infrastructure investment, and deployment into new different territories. ATA specifications underpin the network infrastructure, value-added services and application delivery for fixed and mobile access networks, and allow deployment at the pace of each relevant market. Co-existence of physical and virtualized solutions for static and dynamic services create a network infrastructure mitigating the risks to existing revenue at the same time it leverages new networking technology according to market demand.
ATA maintains the primary architectures for the work of Broadband Forum. The architectures, requirements and other deliverables reflect the control, management, and data plane aspects of the access, transport and routed networks used to provide operator, enterprise and “over-the-top” Internet based connectivity services. The deliverables of the work area are designed to leverage and integrate new industry technologies while protecting investment of current deployments. These deliverables provide the industry with a collective and consistent methodology to drive product development and service deployment.
ATA Work Area (WA): firstname.lastname@example.org
- used for ATA meeting notification, agendas, discussion, etc.
- Go to your JIRA profile page to see all of your current BBF group memberships.
ATA Calls, Minutes, Agendas
Each Project has its own agenda and set of minutes.
See the ATA Calendar and Deadlines for details on conference calls and meetings.