Request for Stand-Alone Project
This page forms the basis for a Board of Directors (BoD) agreement for new stand-alone projects. The Board of Directors will review the Request Form, with any accompanying documents. Upon agreement to proceed, BBF staff, on behalf of the Board of Directors, will oversee the processing of the necessary legal agreements, procedures, membership rules, setup of software tools, etc.
If you are interested in proposing a new project, please reach out to BBF via info@broadband-forum.org.
Notice: This Form has been prepared to assist the Broadband Forum. It is offered to the BoD as a basis for discussion and is not a binding proposal on the author(s), parent companies or any other company. The information is provided "as is" with no warrantees of any kind. Information presented in this document is subject to change after further study. The author reserves the right to add, amend or withdraw any and all statements made herein. |
Directions:
To submit a request for a new stand-alone project, copy this page by clicking the "..." menu button at the top right, then "Copy". Publish your new page with a title of the format: "Request for Stand-Alone Project: [Title and Acronym]".
Item | Details and description | |||
Title | Open Broadband STAMP (OB-STAMP) | |||
| Type of project |
| |||
| Project description | Introduction: OB-STAMP (Open Broadband - Simple Two-Way Active Measurement Protocol) aims to create an open-source implementation of a STAMP Sender and Reflector, fully compatible with RFC 8762 and its associated extensions, to be installed on a Customer Premises Equipment (CPE). The application must run as a containerized application within the CPE following the User Services Platforms (USP) paradigms. The (soon-to-be) TR-390.2 Amendment 1 document also describes the feasibility of using the STAMP protocol to take the performance measurements in the subscriber home network. Existing work (if any): Project prerequisites: Project roles: | |||
Project scope/phases | Initial release: STAMP Reflector (TR-390.2) integrated with the TR-181 management. Subsequent releases to implement additional features:
| |||
| Business need(s) and opportunities | By utilizing the measurements conducted within the IP Edge - CPE segment, there is potential to harness the opportunities outlined in the MR-452.x and TR-452.x documents, thereby enhancing the quality of service provided to subscribers. | |||
| Business impact(s) (check as many as applicable) |
| |||
| Savings (if applicable) |
| |||
| Audience (check as many as applicable) | Industry:
Role:
| |||
| Deliverable type(s) (check as many as applicable) | National/International institutions:
Media:
Type:
| |||
| Relationship to BBF strategy (e.g., Ultra-fast, Agile, Valuable) | Quantify and verify "ultra-fast" | |||
Related BBF documents/projects |
| |||
Related project dependencies from and proposed interactions with other SDOs/industry forums. Do any of these organizations (or members of ) need to be direct contributors inside the project? | There are no dependencies at this time. Work in IETF may lead to future enhancements of the code. | |||
Other special considerations: for non-members, IPP, timing, etc. | None at this time. | |||
Target project completion date | Initial release delivered by Q2 2024 | |||
Supporting companies (please indicate if they are not BBF Members): | OutSys | fgiudici@outsys.com; | Supporter, Contributor, Project Leader | |
| Domos | bjorn@domos.no | Supporter, Contributor | ||
| Vodafone | Supporter | |||
| Deutsche Telekom | Supporter | |||
| Radisys | Supporter | |||
Approval:
Project name:
Initiation date:
Leadership:
IPP:
Scope of Work:
Project deliverables:
Non-BBF members: