Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: middle of ATA wiki surgery... not done yet.





Note: The  For work and wiki pages predating the January 2019 formation of the Access and Transport Architecture Work Area, see the retired Architecture and Migration Work Area was merged with and the Routing and Transport Work Area in January 2019 forming the Access and Transport Architecture Work Area. See announcement from the 2018 Q4 meeting report in Glasgow, UK.

Excerpt

Work Area Directors: David Sinicrope

Mission:

wiki pages.  

Image Added

ATA Project Streams and Deliverables 

Projects Not Assigned to a Project Stream

Multiexcerpt
MultiExcerptNameATANonPS

Project Stream Page: ATA Non-PS Assigned Projects

Work Area Director: David Sinicrope (GM) , Ericsson

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. 

Multiexcerpt
MultiExcerptNameATANonPSProjects


Project Name and Page LinkProject Overview

Disaggregated BNG

Multiexcerpt include
SpaceWithExcerptBBF
MultiExcerptNameATADBNGOverview
PageWithExcerptDisaggregated BNG

Hybrid Access – Assisting Targeted FTTP Deployment

Multiexcerpt include
SpaceWithExcerptBBF
MultiExcerptNameATAHybridAccessOverview
PageWithExcerptHybrid Access – Assisting Targeted FTTP Deployment



 


Performance, Experience, and Application Testing (PEAT) Project Stream

Multiexcerpt
MultiExcerptNameATANonPS

Project Stream Page: Performance, Experience, and Application Testing (PEAT) Project Stream

Project Stream Leads: Ken Ko , ADTRAN; Gregory Mirsky , ZTE

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. 

Multiexcerpt
MultiExcerptNameATAPEATPSProjects


Project Name and Page LinkProject Overview

Application Layer Testing Project

Multiexcerpt include
SpaceWithExcerptBBF
MultiExcerptNameATAPEATPSALTOverview
PageWithExcerptApplication Layer Testing Project

Hybrid Access – Assisting Targeted FTTP Deployment

Multiexcerpt include
SpaceWithExcerptBBF
MultiExcerptNameATAHybridAccessOverview
PageWithExcerptHybrid Access – Assisting Targeted FTTP Deployment



 

Multiexcerpt
MultiExcerptNameATAPEATPS


Multiexcerpt
MultiExcerptNameATAApplicationLayerTestingPS


Project Stream

Description

PS Leaders

Application Layer Testing


Ken Ko, ADTRAN








Work Area Overview

Mission Statement:
Multiexcerpt
MultiExcerptNameATAMissionStmt

The Access and Transport Architecture (ATA) Work Area (WA) defines and specifies the architecture and 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, residential broadband Internet access, etc.  as well as specifications for testing these networks and there application.  (E.g., Performance monitoring and testing, Application Level Testing and testing quality of experience.).  This work is typically in the form of architecture, equipment requirements, test guidance, implementation guidance, and education materials.

Work Area Directors:

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 infrastructure, value-added services and application delivery for fixed and mobile access networks, and allows deployment at the pace of each relevant 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 leveraging new networking technology for 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 todrive product development and service deployment.

Access and Transport Architecture Work Area

Email List:

ATA Work Area (WA): ata@broadband-forum.org

: ATA

  • used for ATA meeting notification, agendas, discussion, etc.

Join or Leave BBF Groups and Email Lists

See Also:

Children Display

ATA Project Streams and Deliverables 

Multiexcerpt
MultiExcerptNameA&MNonPS

Project Stream

Description

PS Leaders

Non-PS Assigned

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

 

Multiexcerpt
MultiExcerptNameATANonProjects

WT/MD/SD#

(JIRA Link)

Non-PS Assigned  Projects

Related Contributions

Editor(s)

SD-452Broadband Quality Experience Delivered (Broadband QED)click hereMD-455Multi Access Broadband - Performance Networking On DemandWT-459Control and User Plane Separation for a Disaggregated BNGKenneth Wan Multiexcerpt
MultiExcerptNameATAApplicationLayerTestingPS


ATA Calls, Minutes, Agendas

Each Project keeps i

See Also:

Children Display

Project Stream

Description

PS Leaders

Application Layer Testing

To define how test traffic is specified and generated at the application layer. It supports specification of test traffic that exhibits the complexity resulting from multiple types of applications and subscribers aggregated in a common network.

Ken Ko, ADTRAN

Multiexcerpt
MultiExcerptNameATAApplicationLayerTestingProjects

WT/MD/SD#

Application-Layer Testing Projects

Related Contributions

Editor(s)

Application-Layer Test Traffic Architecture and Requirements

Click Here

Ken Ko, ADTRAN

Daniel Moss, UNH IOL

WT-422

Application-Layer Testing Implementer's Guide

Click Here

WT-424Data Models for Application-Layer Test TrafficClick Here

Martin Casey, Calix

Jason Walls, QA Cafe