Scope of Changes 2024

SEBA RD Update 2024

Background and Problem Statement

Broadband Forum and LF BB have joined forces (Tiger Team, “TT”) to collaborate in the analysis and identifiable actions to align the assets of the two organisations with the objectives of accelerating adoption of standards, reference designs and opensource-based solutions in the disaggregated whitebox access node domain.

Based on findings, assets of both organisations may need updating and in this initial phase, it has been proposed, and agreed, that the SEBA RD requires an update:

Review the SEBA RD as a whole and ensure that the document includes up-to-date information, deprecating out of date items.
In addition, consider the recommendations from the joint TT [1] as input to the uplift of the document. To date, the TRs 413 (SBI), 451 (OMCI) and 477 (Disaggregated Access Node) have been analysed and they key recommendation is to include [Recommendation 1] NC/YANG as an implementation option in SEBA-based solutions and, where implemented, this should follow the appropriate BBF TRs and Common YANG models.

Scope of (known) changes

Initial analysis of SEBA RD indicates that very few changes are expected in the SEBA RD to align with [Recommendation 1]. This includes the items below although this is not an exclusive list:

· Updating existing references to BBF TRs (e.g. 383, 385, new ones) where needed for Common YANG models adopted by SEBA-based solutions (primarily VOLTHA components);

· Changes to architectural diagrams, where these include annotated texts for protocol and YANG options – where such diagrams do not include such details already, this may be optionally decided upon by authors/contributors;

· Add new sections for the specific items already analysed, e.g. how vOMCI and OpenOMCI can co-exist and align, specific references to VOLTHA additions to the BBF Common YANG models[2] updating /uplifting existing text and potentially a short new section (s) on relevant topic(s) in the scope

· Review the accuracy of and completeness of the document as a whole for general consistency and accuracy of information which may have arisen since the last publication

Clarify the scope of the RD itself regarding “Design Document” based on implementations or a blueprint cross-referencing work ongoing elsewhere.

Contributors List:

Francisco DeCarvalho francisco.decarvalho@radisys.com;

Serkant Uluderya serkant.uluderya@netsia.com

[1] https://wiki.broadband-forum.org/display/BBF/BBF+and+LF+Alignment+Tiger+Team+-+Disaggregated+Access+Nodes%2C+SBI+and+NBI

[2] These have already been ratified by the BBF in Common YANG TRs (e.g. 383/385)