Versions Compared
Key
- This line was added.
- This line was removed.
- Formatting was changed.
Note: 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 and the Routing and Transport Work Work Area wiki pages.
Table of Contents | ||
---|---|---|
|
ATA Work Area Project Streams and Projects
ATA New Project Initiation Forms (NPIFs)
Multiexcerpt | ||
---|---|---|
| ||
Project Page: ATA New Project Initiation Forms (NPIFs) Work Area Director: David Sinicrope (GM), Ericsson 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: 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. |
Access Architecture (AA) Project Stream
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.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:
Business Impact: 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. Scope: Specifically the project stream covers the following areas:
|
Multiexcerpt | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Projects
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Multiexcerpt | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Multiexcerpt | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Projects
Multiexcerpt |
Project Deliverables Title Number Description Resources Editors WT-459.2 (In Final Ballot) This Working Text defines the architecture and requirements to support CG-NAT for a MS-DBNG defined in TR-459. Baseline Working Text (WT) draft CONTRIB-21341 Multi-Service Disaggregated BNG with CUPS.Reference Architecture, Deployment Models, interface, and Protocol Specifications WT-459 issue 2 This is an issue 2 of TR-459, renamed to "Multi-Service Disaggregated BNG with CUPS.Reference Architecture, Deployment Models, interface, and Protocol Specifications". This is to further differentiate from WT-487. This Working Text further clarify call flows, requirements, and PFCP IEs updates for TR-459. Baseline Working Text (WT) draft CONTRIB-22737. IPTV Multicast for the Disaggregated BNG TR-459.3 This Working Text defines the architecture and requirements to support IP Multicast for a disaggregated BNG defined in TR-459. Control and User Plane Separation for a Disaggregated BNG TR-459 TR-459 defines the architecture, the requirements, and the protocol for a control and user plane separation of a disaggregated BNG.
Multiexcerpt |
Project Deliverables Title Number Description Resources Editors --- | --- | --- | --- | --- Multiexcerpt | MultiExcerptName |
Subscriber Session Steering WT-474 Baseline Working Text (WT) draft CONTRIB-22389. | | ATADBNGWAOverview
| projects focuses on control/user plane separation of BNG in the case of wired access (e.g. PON, xDSL, etc). It will start with use case details, including deployment scenarios and operational aspects, then move to architectural framework and finally move to protocol considerationsThis project profiles DBNG aspects specific to MS-BNG aggregating subscribers over wired access networks, including fixed access(e.g. PPPoE, IPoE, L2TP, etc.), CGN, multicast, resilience, etc.It will define use case, architecture, requirements and CUPS protocol for wired access.
Motivation: Continue to promote BNG enhancements that allow more flexibility in terms of deployment models and multi-vendor interoperability between disaggregated components.Key business impact: benefits of network disaggregation applied to fixed subscriber management; additional deployment models to adapt to wide areas of operators requirementsScope:This project profiles DBNG aspects specific to MS-BNG aggregating subscribers over wireline access networks. The scope of this new project addresses a subset of the fixed access use cases found in TR-459 and potential additional fixed use cases.This project excludes any use cases that includes wireless access (4G/5G, Wi-Fi,…), hybrid access and wireless-wireline convergence. Such use cases are addressed by TR-459 cases in addition to the wireline baseline.The project is phased with checkpoints in-between phases, to ensure clear transitions between stage 1/ 2/ 3 aspects. Phase 1: Scope and DBNG for wired access Use Cases
-----------Phase 2: Architectural Aspects for DBNG in fixed access & Requirements for nodes and interfaces/protocols between CP and UP
-----------Phase 3: Protocol specific aspects
Between each phase, consensus is required to agree to progress to the next phase. The goal is to proceed in a top-down fashion, encouraging the group to focus contributions relevant for the active phase, getting to a stable content before moving to the next level of detail.This project is expected to leverage the protocol-independent areas of TR-459 (e.g. architecture, functional decomposition,…) for what is relevant for fixed only. As much as possible, consistency with protocol independent aspects of TR-459 should prevail.It is understood that following issues/revisions of TR-459 will continue in parallel to this new project (eg. CGNAT and multicast support). This does not preclude this new project to cover these use cases.Upon completion of this working text, some Marketing Document can be generated to advertise BBF recommendations Multiexcerpt |
Project Deliverables Title Number Description Resources Editors DBNG for Wired Access WT-487 This project profiles DBNG aspects specific to MS-BNG aggregating subscribers over wired access networks, including fixed access(e.g. PPPoE, IPoE, L2TP, etc.), CGN, multicast, resilience, etc.This project will include use case, reference architecture, requirements, interfaces, and protocol specifications for Wired Access DBNG. Baseline Working Text (WT) draft |
Mobile Transport and Routing (MT&R) Project Stream
Multiexcerpt | ||
---|---|---|
| ||
Project Stream Page: Mobile Transport and Routing (MT&R) Project Stream Project Stream Leads: David Sinicrope (GM), Ericsson Mission: 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. Business Impact: 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. Scope: 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. |
|
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 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Multiexcerpt | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Multiexcerpt |
Project Deliverables Title | Number | Description | Resources | Editor(s) | 5G Transport Architecture and Requirements | WT-521 | Jira | server | BBF Jira | columnIds | issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution | columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution | 20551
| Ron Insler
RAD | 5G Transport Tutorial | | MD-521.2
columnIds | issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution | columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution | 21956
David Sinicrope , Ericsson
5G Transport Whitepaper | MR-521.1
columnIds | issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution |
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution | 21980
Joel Halpern , Ericsson MPLS in Mobile Backahul | TR-221 |
columnIds | issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution |
columns | key
MSTRFILES-49 | MPLS in Mobile Backhaul Amendment 1 - adds support for enhanced services and small cells | TR-221 Amd 1 | Jira | server | BBF Jira | columnIds | issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution | columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
| 11531
Balazs Varga, Ericsson | 2nd amendment to TR-221 MPLS in Mobile Backhaul Networks - adds architecture and requirements for |
| TR-221 Amd 2
columnIds | issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution |
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution | 15842
| Yuanlong Jiang
Huawei | MMBI LTE Tutorial | MR-234 |
David Sinicrope , Ericsson | MMBI White Paper on Use of MPLS in LTE | MR-238 |
| Energy Efficient Mobile Backhaul | TR-293 |
Konstantinos Samdanis | Mobile – Transport Network Slice instance Management Interfaces (MTNSi)
Multiexcerpt |
Project Deliverables Title Number | Description | Resources Editor(s) MTNSI Architecture and Requirements | WT-522 | MTNSI Architecture and Requirements |
Xueyan Song , ZTE Reza Rokui , Nokia |
Performance, Experience, and Application Testing (PEAT) Project Stream
MultiExcerptName | ATAMPEATPSOverview |
---|
Project Stream Page: Performance, Experience, and Application Testing (PEAT) Project Stream
Project Stream Leads: Gregory Mirsky , Ericsson
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:
Enhanced packet layer performance testing e.g.,bandwidth/capacity, min/average/max latency measurements and jitter, loss, etc and Testing that goes beyond traditional packet layer performance to test and analyze the application and service layer qualityBoth 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:
Application Layer Testing supports specification of test traffic, and associated measurements, that exhibits the complexity resulting from multiple types of applications and subscribers aggregated in a common network.
CE to IP Edge testing extends Broadband Forum’s OAM framework with architectural and nodal requirements to enable Customer Equipment to IP Edge service assurance of broadband subscribers, both for business and residential connections.
IP Layer Capacity Metrics and Measurements harmonizes the Industry around a specific set of Capacity metrics and measurement method with clear benefits of multi-dimensional performance assessment at existing and new Gigabit-rate access speeds.
Quality Experience Delivered is a method of systems performance analysis that decomposes a round trip time into constituent components enabling the networks performance to be analyzed and traced to sources causing performance degradation (packet loss/delay), be they structural (architecture/design), network dimensioning (link speeds etc.) or network load/scheduling related.
MultiExcerptName | ATAPEATPSProjects |
---|
Project Name and Page Link
Project Overview
Multiexcerpt | ||
---|---|---|
| ||
Project Overview To define how test traffic is specified and generated at the application layer. It supports specification of test traffic, as well as associated metrics and measurement methods, that reflects the complexity resulting from multiple types of applications and subscribers aggregated in a common network. |
MultiExcerptName | ATAPEATPSALTDeliverables |
---|
Project Deliverables
Title
Resources
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
Ken Ko, ADTRAN
Multiexcerpt | ||
---|---|---|
| ||
Project Overview This project will extend Broadband Forum’s OAM framework with architectural and nodal requirements to enable Customer Equipment to IP Edge service assurance of broadband subscribers, both for business and residential connections. The main business drivers for this work are:
The BBF is in a unique position to give service providers the tools they need in this subject matter, defining a solution that allows measurement and exposure of RG/CPE to BNG/PE network performance and addresses the current gap. |
MultiExcerptName | ATAPEATPSPerfTstDeliverables |
---|
Project Deliverables
Title
Resources
Editor(s)
Performance Measurement from Customer Equipment to IP Edge
|
Guiu Fabregas , Nokia
Gregory Mirsky , ZTE
Multiexcerpt | ||
---|---|---|
| ||
Project Overview This project will deliver documentation that gives a comprehensive overview of Quality Attenuation and its applicability to broadband networks. It will cover the theory, measurement technique, use-cases and benefits of the approach. |
MultiExcerptName | ATAPEATPSQEDDeliverables |
---|
Project Deliverables
Title
Resources
Editor(s)
Broadband Quality Experience Delivered (Broadband QED)
Jira | ||||||
---|---|---|---|---|---|---|
|
Peter Thompson , PNSol
Bruno Cornaglia, Vodafone
Jira | ||||||
---|---|---|---|---|---|---|
|
Jonathan Newton , Vodafone
Jira | ||||||
---|---|---|---|---|---|---|
|
Jira | ||||||||
---|---|---|---|---|---|---|---|---|
|
Jira | ||||||
---|---|---|---|---|---|---|
|
Peter Thompson , PNSol
Rudy Hernandez , Spirent
Jira | ||||||
---|---|---|---|---|---|---|
|
Jira | ||||||
---|---|---|---|---|---|---|
|
Jira | ||||||
---|---|---|---|---|---|---|
|
Peter Thompson , PNSol
Jira | ||||||
---|---|---|---|---|---|---|
|
Peter Thompson , PNSol
Jira | ||||||
---|---|---|---|---|---|---|
|
Jira | ||||||
---|---|---|---|---|---|---|
|
Jira | ||||||
---|---|---|---|---|---|---|
|
Jonathan Newton , Vodafone
Jira | ||||||||
---|---|---|---|---|---|---|---|---|
|
Peter Thompson PNSol
Jira | ||||||
---|---|---|---|---|---|---|
|
Gavin Young , Vodafone Peter Thompson , PNSol
Multiexcerpt | ||
---|---|---|
| ||
Project Overview Standardize the IP-Layer Capacity Metric and Measurements with the benefit of BBF membership's unique expertise and perspectives. Ideally, to harmonize the Industry around a specific Capacity metric and method with clear benefits of multi-dimensional performance assessment at existing and new Gigabit-rate access speeds. |
MultiExcerptName | ATAPEATPSIPCapDeliverables |
---|
Project Deliverables
Title
Resources
Editor(s)
Maximum IP-Layer Capacity Metric, Related Metrics, and Measurements
Al Morton, AT&T
Al Morton, AT&T
Cloud Interconnect (CI) Project Stream
MultiExcerptName | ATACIPSOverview |
---|
Project Stream Page: Cloud Interconnect (CI) Project Stream
Project Stream Leads: David Sinicrope (GM), Ericsson (acting)
Mission:
This project addresses architectures, requirements and use cases for providing interconnection between Cloud data centers.
Business Impact:
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.
Scope:
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.
For example:
- Support for attachment circuits providing user-to-network interface complying with Metro Ethernet Forum (MEF UNI).
- Support for Ethernet attachment circuits for multi-service broadband access and aggregation (i.e., TR-101/WT-178).
- Support for service level OAM and performance monitoring
- Frame Relay and ATM are out of scope
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).
MultiExcerptName | ATACIPSProjects |
---|
Project Name and Page Link
Project Overview
Multiexcerpt | ||
---|---|---|
| ||
Project Overview The project covers the support of following Ethernet services:
It is intended to apply the same understanding as has been used for WT-224 and WT-178 and to profile IETF and MEF standards. This project specifically addresses the support of Ethernet services using BGP MPLS Based Ethernet VPNs (EVPN). For more information, please see the New Project Information Form (NPIF) for the EVPN project. |
MultiExcerptName | ATACIPSEVPNDeliverables |
---|
Project Deliverables
Title
Resources
Editor(s)
Eric Gray , Ericsson
Multiexcerpt | ||
---|---|---|
| ||
Project Overview Provide architecture and nodal requirements to support broadband multi-service networks and MEF carrier Ethernet services. Use VPWS and VPLS in IP/MPLS networks and provides how service parameters are supported in MPLS network. The project covers the support of following Ethernet services:
It is intended to apply the same understanding as has been used for WT-224 and WT-178 and to profile IETF and MEF standards. This project specifically addresses the support of MPLS in Carrier Ethernet Networks. |
MultiExcerptName | ATACIPSVPLSDeliverables |
---|
Project Deliverables
Title
Resources
Editor(s)
Rao Cherukuri, Distinguished Fellow, Juniper
Seamless MPLS for efficient broadband services delivery - Tutorial
Packet Optical Evolution (POE) Project Stream
Multiexcerpt | ||
---|---|---|
| ||
Project Page: Packet Optical Evolution (POE) Project Stream Project Stream Leads: David Sinicrope (GM), Ericsson (acting) 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.Scope 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. |
Multiexcerpt | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Multiexcerpt |
Project Deliverables Title Number | Description | Resources Editor(s) FlexE in IP/MPLS networks Study | OD-462 (was SD-FlexEMPLS45G)
Dean Cheng , Huawei Achieving Packet Network Optimization using DWDM Interfaces |
Multiexcerpt |
Project Deliverables Title Number | Description | Resources Editor(s) Achieving Packet Network Optimization using DWDM Interfaces | TR-319 Base | Achieving Packet Network Optimization using DWDM Interfaces – Physically Integrated Model | TR-319 Part A | Achieving Packet Network Optimization using DWDM Interfaces – Physically Separated Model | TR-319 Part B |
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 , routing and transport network infrastructure. ATA ATA produces industry-agreed specifications for applications such as mobile transport infrastructure (fronthaul and backhaul), data center interconnect, broadband Internet access , etc. as 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 DirectorsDirector:
|
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 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.
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 ATA meeting notification, agendas, discussion, etc.
Join or Leave BBF Groups and Email Lists
- 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.
See Also:
Children Display |
---|
...