Versions Compared
Key
- This line was added.
- This line was removed.
- Formatting was changed.
Note: The Architecture and Migration Work Area was merged with the Routing and Transport Work Area in January 2019 forming For work and wiki pages predating the January 2019 formation of the Access and Transport Architecture Work Area. See announcement from the 2018 Q4 meeting report in Glasgow, UK., see the retired Architecture and Migration Work Area and the Routing and Transport Work Area wiki pages.
Table of Contents | ||
---|---|---|
|
Image Added
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.
ATA New Project Initiation Forms (NPIFs)
Multiexcerpt | ||
---|---|---|
| ||
Project Page: ATA New Project Initiation Forms (NPIFs) Work Area Director:Jonathan Newton , Vodafone. Description: Proposed new projects for ATA or combination of Work Areas including ATA. |
ATA Non-PS Assigned Projects
Multiexcerpt | ||
---|---|---|
| ||
Project Stream Page: ATA Non-PS Assigned Projects Work Area Director: Jonathan Newton , Vodafone. 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. |
Access Architecture (AA) Project Stream
Multiexcerpt | ||
---|---|---|
| ||
Project Stream Page: Access Architecture (AA) Project Stream Project Stream Leads: Jonathan Newton, Vodafone Mission: 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. |
Mission Statement:
Excerpt |
---|
TBA Work Area Directors: David Sinicrope |
Show If | ||
---|---|---|
| ||
David Sinicrope any chance you can look at this and give an OK or edit today? I am providing to Robin for inclusion in a priority document related to the license application. Proposed text: Mission: The Access and Transport Architecture (ATA) Work Area (WA) defines the architecture of Broadband Forum's work and specifies the integration of routing and transport network infrastructure. ATA produces industry-agreed specifications for applications such as mobile backhaul/transport infrastructure, data center interconnect, video distribution, etc. This work is typically in the form of architecture, equipment requirements, interoperability and conformance test plans, implementation guidance, and education materials. Business Impact: 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 effectively be a stable hybrid network. This enables seamless migration based on market acceptance of on new technologies, protection of existing infrastructure investment , and normal spread of deployment in different territories.The project stream will focus on:
Business Impact: The work creates the necessary foundation for all of the broadband network. It underpins . ATA specifications underpin all the new value-added services and application delivery for fixed and mobile 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 hybrid 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. Scope: Specifically the project stream covers the following areas: ATA maintains the primary architectural models for the work of Broadband Forum. The models reflect the control, management, and data plane aspects of Broadband Forum-defined architectures. The models are augmented to subsume new industry directions, such as SDN and NFV, while carrying forward key aspects of broadband as currently deployed. The products of the work area provide Broadband Forum with a collective and consistent language and algebra to help drive overall consistency of product. |
ATA Project Streams and Deliverables
MultiExcerptName | A&MNonPS |
---|
Project Stream
Description
PS Leaders
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.
David Sinicrope, Ericsson
MultiExcerptName | ATANonProjects |
---|
WT/MD/SD#
(JIRA Link)
Non-PS Assigned Projects
Related Contributions
Editor(s)
MultiExcerptName | ATAApplicationLayerTestingPS |
---|
Project Stream
Description
PS Leaders
Ken Ko, ADTRAN
MultiExcerptName | ATAApplicationLayerTestingProjects |
---|
WT/MD/SD#
Application-Layer Testing Projects
Related Contributions
Editor(s)
Application-Layer Test Traffic Architecture and Requirements
Ken Ko, ADTRAN
Daniel Moss, UNH IOL
Application-Layer Testing Implementer's Guide
Martin Casey, Calix
Jason Walls, QA Cafe
|
Multiexcerpt | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Projects
|
Performance, Experience, and Application Testing (PEAT) Project Stream
Multiexcerpt | ||
---|---|---|
| ||
Project Stream Page: Performance, Experience, and Application Testing (PEAT) Project Stream Project Stream Leads: Fabio Giudici Mission: 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. Business Impact: 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. Scope: Specifically the project stream covers the following areas of connectivity quality testing:
|
Multiexcerpt | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Work Area Overview
Mission Statement:
Multiexcerpt | ||
---|---|---|
| ||
The Access and Transport Architecture (ATA) Work Area (WA) defines and specifies the architecture and equipment requirements for access and transport network infrastructure. ATA produces industry-agreed specifications for applications such as broadband Internet access 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 Director:
|
Business Impact:
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 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.
Scope:
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.
Email List:
ATA Work Area (WA): ata@broadband-forum.org
- used for
Access and Transport Architecture Work Area Email List:
ata@broadband-forum.org:- ATA meeting notification, agendas, discussion, etc.
Join or Leave BBF Groups and Email Lists
- Go to your JIRA profile page to 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.
See Also:
Children Display |
---|
...