Skip to end of banner
Go to start of banner

5G SBP Use Case - Nephio Upstreaming

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Version History

Version 1 Next »

Use Case Name:

Nephio Upstreaming

Use Case Description:

Match existing and upcoming 5G SBP capabilities to upstream to Nephio. As starting points;

  • Look at security goals discussed with the LFN TAC (from SECOM)

    • TAC security hardening efforts

    • Bring in Amy for feedback

    • Nephio road show (what is the pitch?, What are the alignment points?). Can 5G SBP efforts be included in Nephio on a permanent basis? What permanent features can be included in Nephio?

      • Next Steps:

        • Action Items:

          • LJ Illuzzi Create a 5G SBP Use Case Page

            • This page created

          • Develop a pitch/discussion points. Reference: Library and existing Use Cases in flight.

          • LJ Illuzzi get on a Nephio TSC agenda

  • Nephio SIG looking at ambient MESH, and and also to see if they can incorpate spiffe workload identity.

-Epic

-Problem Statement


Blueprint Owner

enter name

Users Stories


  • a.

  • b.

  • c.

Interaction with other open source projects and components

  • a.

  • b.

  • c.

Resources -people


Resources (people) to execute on the blueprint:

  • enter name 1

  • enter name 2

  • ...


Steps to Realization

  • What is the very 1st step to realization?

  • 2nd step?

  • 3rd step?

High-level architecture diagram



High level lab topology diagram



Dependencies - list of any dependencies that rely of future releases of a specfic component.


  • Yes

    • Enter details:

or

  • No

High-level timeline


  • Month that build can begin: enter month/year

  • Approximate duration of build: enter number of weeks or months

  • Approximate completion of outputs: enter month/year

Upstreaming Opportunities


  • enter project(s) and details

Blueprint Outputs 

(Suggested. Not all may apply)

check all that apply:

  • Code repository
  • Configuration files (e.g. Helm charts, etc.)
  • Upstreaming to relevant projects 
  • Continuous Integration
  • Test requirements and test results (if applicable)
  • Documentation:
    • Overview and Theory of Operation (i.e., what does it do?)
    • Deployment and setup
  • Videos
    • demo
    • lab setup/behind the scenes
    • other

Links to existing documentation (Build Guide, Slideware, etc), if available.


Links to existing demo/video, if available.


Links to existing code/repos, if available.


  • No labels