Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. Permission to record /Roll call   ~4 minutes
  2. Open meeting: No IPR protection                  ~1 minute
  3. Review Agenda   ~5 minutes
  4. Review of output from Workshop #1  ~10 minutes
  5. Establish the collaboration/contribution process  (30 minutes)
    1. Reconfirmation of agreed objectives in Workshop #1
    2. List of discussion topics
    3. Agree  Schedule Dates
    4. Contribution process
    5. Have some strawman straw man contributions ahead of meeting time
  6. Identify concepts and definition (Time permitting) 
    1. Autonomous Networks,  
    2. Autonomous Network Levels,  
    3. Intent driven interactions
    4. Control loops
    5. Autonomous Domain
  7. Agree schedule for future meetings   ~10 minutes
  8. AOB

...

  1. Kevin proposed a simple matrix of topic/SDO to establish the full list of topics and then to  establish which SDOs and individuals were prepared to contribute to those topics. The topic list was seeded by the 5 topics listed in the agenda.
  2. Discussion followed focused on making clear the precise objectives of the group are and some suggestions were given on how to organise organize this worksheet to create a more high-level landscape and then roadmap view of collaboration.
  3. As such, it was not possible to fully complete this matrix analysis during the meeting as clarification on the high-level objectives was needed from many participants. 
  4. The matrix of topic/SDO will be further elaborated offline by participants and analyzed in future meetings. Matrix is in spreadsheet above: Multi-SDO Autonomous Networks Meeting 2 MoM 22-FEB-2021.xlsx

...

  • Need to establish a common view of the objectives and benefits of such coordination.
  • Query about objectives of the worksheet:
    • Confirm the topics identified from Workshop #1.
    • Who is interested in what topics? Frameworks specific meaning of definitions / terms
    • Who might be planning to contribute?
    • Alignment by sharing of work
    • Possibly jointly developed document.
    • Approach is to establish which groups have interest in which  areas.
  • Noted that topics are similar and different groups may be working on similar concepts but at different levels of the network.
  • General consensus to work out what to do together in concrete form

Concerns-

...

Operational/

...

organizational

  • Concern if the work addresses standardization as that will take much time.
  • Joint specification would require discussions on rules and procedures.
    And is the purpose of the parallel Inter SDO meeting for later in March 2021.
  • Over arching document might be feasible.  E.g. White paper
    • Could be definitions and or frameworks
    • Use case
    • Test and verification
  • Different group will have more or less engagement and some topics might be of higher or lower priority.
  • Autonomous levels - are these separate from maturity levels? Consensus was yes.
  • Conceptually alignment whilst necessary might still not create aligned outputs for example APIs models split between common /non domain specific and domain specific.
  • Intent APIs are one example where divergence across SDO would be unhelpful.
  • Concerns about possibility of establishing a 'mega-organization' to create common framework
  • Multiple things done in organization trying to create consistency work in collaboration using Liaison offices and liaisons
  • Need to avoid creating obstacles and impeding SDO progressing their existing works
  • Idea of Joint PoCs looks good and was supported by multiple participant
  • Concerns about setting a scope of work that is too large to be done within reasonable timeframe time frame and effort.
  • Starting point should be the existing SDO material and consider motivation and issues they plan to solve. E.g. whether Autonomous Network means the same in all organizations. Should try to find the commonalities  and how complementary work.

...

  • Common information models:
    • Federation / merge of information models was successful for Network models as developed between 3GPP and TM Forum and common models lead by Cablelabs.
    • Concern about creating new over arching model as that creates N+1 standards.
    • Should try to establish what was done in the past that worked well.
  • PROPOSAL: Review proposal developed by IEEE at FUture Future networking conference "Overarching Blueprint of Common Operational Principles of Autonomic/Autonomous Networks," which involves Mappings for Federated Models as well
  • Concern that even aligning principles guidelines across SDOs could be a challenge as implies changes to existing SDO specifications.
  • Formal contributions might be best done by company contributions as easier to handle in the SDO Working Groups.
  • Outcomes could be:
    • Sharing of information.
    • Sharing of definition, then figure out if there a was mutual interest to create shared understanding which could then become the Landscape/ Roadmap.

...

We will ask attendees to complete the spreadsheet analysis online.

Action List

  •  We will ask attendees to complete the spreadsheet analysis online.

Next Meeting details

Scheduled Date:        

...