Search

Help

Page 4 of 7. Showing 68 results (0.033 seconds)

  1. BBF_Q4_2017_Newsletter.pdf

    discussion around the related working text and the addition of some use cases was agreed. The Work Area also continued its activities on its other deliverables … will be available soon The BUS Work Area is working in conjunction with the Physical Layer Transmission Work Area to push forward the development of real
  2. SDN and NFV

    and in turn the automation and Orchestration of PNFs and VNFs in a Cloud CO type of architecture. The development of this Working Text shall also shape
    BBF WikiMar 21, 2024
  3. BBF Q3 2023 Newsletter_FINAL.pdf

    a Working Text on the architecture of this project, and there is a call for volunteers for editors. The document will address scenarios and gaps identified during … opportunity to do such, as well as generally foster a productive team working environment. While we will continue to allow remote participation, we strongly
  4. BBF Q1 2019 Newsletter.pdf

    traffic with very different characteristics. This Working Text (WT) defines an architecture and requirements for the specification of test traffic generated … Abrahamsson. “As we continue this work, we are working towards having standardized modules as much as possible and with open source development and cooperation
  5. Assigned Names and Numbers

    number, Issue, Amendment and Corrigendum respectively (-c is optional) Note: wt is used instead of tr to reference a BBF Working Text (never in a published standard
    BBF WikiFeb 21, 2024
  6. BBF 2021 Q3 Newsletter.pdf

    Power Feed Testing Issue 3' (WT-338i3) was created. The Working Texts for 'Architecture and Requirements for Home Distribution Networks' (WT-488), 'Fiber … - Participants in PEAT PS working on QED will make individual submissions to the upcoming IAB Workshop on "Measuring Network Quality for End-Users, 2021
  7. BBF OB Project Participation Agreement Template OB-STAMP.pdf

    ) The following text shall replace Section 3.1 of the BBF IPR Policy with respect to the Submissions of Artifacts and Contribution of Programs: 3.1 License Obligations (i … the BBF IPR Policy. (e) The following text shall replace Section 3.2 of the BBF IPR Policy with respect to the Program(s) only: (for Artifacts, Section 3.2 is used
  8. BBF OB Project Participation Agreement OB-CAS.pdf

    , and each “Program” in this Project shall constitute a “Work” under the Apache 2.0 license. (d) The following text shall replace Section 3.1 of the BBF IPR Policy … approval will be recommended, assented and minuted at a regular meeting of the Project, with final approval by the Board. G. Working with external groups
  9. OB-UDPST_PA.pdf

    license and defined terms applicable to the Artifacts shall have the meanings set forth in the BBF IPR Policy. (d) The following text shall replace Section 3.1 … ) The following text shall replace Section 3.2 of the BBF IPR Policy with respect to the Program(s) only: (for Artifacts, Section 3.2 is used as is.) 3.2
  10. OB-USP-Agent_PA.pdf

    license and defined terms applicable to the Artifacts shall have the meanings set forth in the BBF IPR Policy. (d) The following text shall replace Section … . (e) The following text shall replace Section 3.2 of the BBF IPR Policy with respect to the Program(s) only: (for Artifacts, Section 3.2 is used