BBF Wiki Home Page | BBF Website | Work in Progress

Note: Use Common WA & PS Agenda and Minutes Template for A&M Work Area


<need to clean up this page...>


Architectural aspects of Broadband assured services as called out in SD-377. These include

  1. WT-387 Broadband Assured Services Architecture
  2. WT-388 Broadband Assured Services Specification
  3. SD397 Broadband Platform Environment Source Document (related document)
 


Current Projects

  1. WT-387 Broadband Assured Services Architecture
  2. WT-388 Broadband Assured Services Specification

Source Document

  • SD-377 BAS Source Document (Innovation Group)

Related Work

  • SD397 (posted on ARO)  Broadband Platform Environment Source Document 
  • SD-389 Use Cases (Innovation Group)

  • Q1 2017

    ItemDescriptionAction/Status/Comments
    Agenda

    2017.174

    Attendance: ~20

    SD-389 

    Contribution 2017.174

    AR? Augmented reality

    Discussion around the KPIs for 4K video.

    Proposes studying service and network KPI requirements for AR/VR and video as part of SD-389.

    We have use cases, now collecting KPIs, how do we actually build the network to do this?

    Innovation white paper on traffic management.  Need the what before the how!

    How much is missing in the service definitions?

    Ordering an IP service in 200 different countries cited as an example. Big delta between a generic IP service, and p2p application delivery KPIs. MEF work is more akin to the latter. and addressing the enterprise space.

    Call for contributions on the service definitions.

    Would be good to know what the MEF was doing. Dave S. to draft a liaison response to the MEF. We will vet it on the mailing list prior to closing plenary.





Call agendas and minutes


TopicDescriptionDescription/DetailsAction/Status, Who/When, Comments
Agenda for call Oct 5 2016
  1. Approval of minutes
  2. Follow up on Action points from Friday Sept 23 meeting
  3. Review SD-397 (bbf2016.1018.02)
  4. Review new draft SD-377 v19 (bbf2016.370.04)
  5. Plan for Kansas city
  6. A.O.B.
  7. Action summary

Lead by: David Allan

Minutes by : Mauro Tilocca

Attendees: David Allan, Mauro Tilocca, Andrew Malis, George Dobrowski, Ken Ko, Charles Cook, Michael Bugenhagen, Michael Fargano, Yuanlong Jiang

Apologies: Georgios Karagiannis, Mark Fishburn



Webex Info

Oct 5, 2016, 6:00am PT / 9:00am ET /  2:00pm BST / 3:00 CET.

 https://broadbandforum.webex.com/broadbandforum/j.php?MTID=m3286dac761ebecf7a4fabcdada9a8a36

Audio Details:

  • Audio Access Code: 801 395 212
  • Toll (International): +1-415-655-0002

2. Enter your name and email address.

3. Enter the session password: am2016

Meeting Number: 801 395 212

Host Key: 901336

Audio Details:

Audio Access Code: 801 395 212

Toll (International): +1-415-655-0002

International local access numbers: https://broadbandforum.webex.com/cmp3100/webcomponents/widget/globalcallin/globalcallin.do?siteurl=broadbandforum&serviceType=MC&eventID=499447377&tollFree=0
Previous minutes and actions

See minutes of 9/23 call

bbf2016.1020.00.docx

 

 

All Action points

  • AP1: Mike Bugenhagen will draft a separate document – “principles document”.  This document will include the content provided on the VNG Manager and will form the basis for the new BBF framework/platform. The target draft to be distributed by September 30.  Draft to include a figure/illustration where projects map into figure. In addition to this the draft should relate to WT-359.
  • AP2: George Dobrowski will get an SD number allocated for the draft.
  • AP3: George Dobrowski with Ken Ko, Dave Allan and Dave Thorne make recommendation to the Steering Committee where this work fits in BBF and other related and/or durative work.
  • AP4: George Dobrowski: To provide last version of WT-359 to Mike Bugenhagen,
  • AP5: Mark Fishburn to provide the source of the figure used in Section 7.1.2 used in WT-387 to Mike Bugenhagen, see below

  • AP6: Mike Bugenhagen provides a hint on how the relation between the BBF framework/platform and Section 7.1.2 of WT-387 should be
  • AP7: Michael Bugenhagen expands service template using standard method sections 7.3 into catalog entries
  • AP8: Mark Fishburn : Include the below information in Section 5.1 of SD-377

In the table shown in Section 5.1 please include a sentence that emphasizes that there is a virtualized service assurance engine that is incorporated in the VNF Manager or NFVO. Then in the text include text that mentions “Assured engine monitors the items in table of Section 5.1 by applying policies and actions.”

  • AP9: ALL: How to use TR-304 in the context of BAS?
  • AP 10 Mark Fishburn (not in minutes) rework of SD-377 (content moved to SD-397)

 

  • IPR declarations: none

  • Minutes approval: minutes of the September 23 call approved

  • Action update
  • AP1: done. That's SD-397 (2016.1018)
  • AP2: completed. That's SD-397
  • AP3: open, not strictly necessary to make a recommendation to the SC if WA directors come to an agreement.
  • AP4: completed
  • AP5: complete: This was first posted on slide 17 of bbf2016.508 and is also posted in the Broadband Forum sample diagrams the wiki (see the bottom of the wiki home page or download directly)
  • AP6: under discussion, somewhat related to the due diligence in AP3
  • AP7: open
  • AP8: complete/superseded by SD-397
  • AP9: open
  • AP 10 completed and uploaded 377v19 as bbf2016.370.04
  • AP11 (new) Michael Bugenhagen to put SD-397 on the Wiki.

 

Review SD-397 (bbf2016.1018.02) 

This document will include the content provided on the VNG Manager and will form the basis for the new BBF framework/platform.

Draft to include a figure/illustration where projects map into figure.

In addition to this the draft should relate to WT-359.

Michael Bugenhagen referred that ETSI NFV NOC (Netw Operators Council) is very interested to the work in SD-397 and would like to publish a White Paper about it once mature/finalized.

Michael Bugenhagen presented SD-397 Rev-01, describing a model driven platform. This is supposed to serve "any" service and there is no point in focusing on a specific Use Case. Actually this is a wider scope than BAS.

Q. Ken: what's the status of this work.

A. Mike: just started on the basis of the originating NPIF (2016.985) plus SD-397 which refer to some more next steps some not yet covered. Some presentations already available, e.g. those that will be presented at the 4Q BoF on Operator Migration.

 

Discussion about the relationship between SD-397 and SD-377 (and then WT-387 and 388).

Mauro Tilocca: it looks like SD-397 and further technical dleiverables aim to define a generic platform that enables BAS type of service and more. So in a sense it looks like this is something that would take priority before being able to define a technical solution for BAS.

David Allan: I see SD-397 and BAS (SD-377) as orthogonal.

There is genreal agreement that the Sd-397 work/scope goes well beyond BAS and is applicable to other BBf initiatives like the Cloud CO project and OBI.

This is part of the due diligence in AP3.

Review new draft SD-377 v19 (bbf2016.370.04) 

Rework of 377 removing Mike’s contribution – separating the user services from the underlying NFV enabled network services platform that span a number of projects - all moving to 397

Explore the word “assured” in the document and look for some alternative titles for discussion

This item was not addressed due to lack of time.
A.O.B   
Summary

Action summary

  
Wrap upNext Call  

 


Minutes from previous calls

TopicsDescription

Action/Status, Who/When, Comments

Agendas for call 9/23/16
  • Minutes of 9/13 call
  • Review additional elements of SD-377
  • Discussion of SD-387 work
  • Implication of the innovation track work  (SD-389)
  • Q4 meeting
  • next call

Call details:

Call lead by:

attendees:

Approval of minutes of 9/13See below 
Additions to SD-377

For discussion:The location of platform discussion within the service delivery source document and it's content

Status of SD-387

Discuss. Should the additional contribution by Michael Bugenhagen to SD-377 generate a new WT?

 
SD-389Status of development of use cases within the Innovation track and relationship to A&M work 
 Q4 meetingPreparation for Kansas city sessions within A&M 
Next call  
TopicsDescription

Action/Status, Who/When, Comments

Agendas and Minutes for Call 9/13/16

Agenda of BAS teleconference on 13 September at 16:00 CEST

 Minutes fro 8/30 call

Agenda topic 0: Minutes from 8/30 call

Agenda topic 1: SD-377 update

  • expand service template using standard method sections 7.3 into catalog entries Michael Bugenhagen
  • Add VNF management framework for assurance Michael Bugenhagen
  • Relate BAS to TR-304
  • Repost small SD-377 modifications as v.17 (done):
  1. https://www.broadband-forum.org/bin/c5i?mid=4&rid=7&gid=0&k1=46725&k2=3&k3=9&tid=1473754078

Agenda topic 2: WT-387 Architecture - what is supported? Michael Bugenhagen

 
 

Agenda topic 2: WT-387 Architecture - what is supported? Michael Bugenhagen

Agenda topic 3: Discuss Additional NPIF Top Down NFV End-to-End Access model bbf2016.914, see:

https://www.broadband-forum.org/bin/c5i?mid=4&rid=7&gid=0&k1=47603&k3=9&tid=1473754234		 
   
TopicsDescription

Action/Status, Who/When, Comments

Agenda

8/30/16

  • Contribution from Mike Bugenhagen on Step 1 (part of SD-377: Broadband Assured IP Services Source Document)
  • Agenda topic_: Next Steps and Action Point
  • AOB

Lead by David Allan

Minutes by: Georgios Karagiannis

On the call: Michael Fargano, Michael Bugenhagen, Charles Cook, David Thorne, George Dobrowski, Mauro Tilocca, Yuanlong Jiang, Mark Fishburn, Robin Mersh

Agenda and Minutes were agreed

SD-377 update

SD-377 update: bbf2016.370.02

Discussion of the

  • Provider “resource deployment locations"
  • Model Driven “resource” hierarchy
  • Categorized abstract use cases for enabling services

To provide a generic Cloud Service Delivery capability not limited to BAS

 Architecture discussion
WT-387 Architecture - what is supported? Michael Bugenhagen
 

Additional NPIF

Top Down NFV End-to-End Access model bbf2016.914

action: all read  and comment
Agenda topic_4: Next Steps and Action Points

Deferred to future call:

  • Step 2:
    • Description of network deployments
      • Action Point: ALL
      • Validation of the network deployments with operators/providers
  • Step 3:
    • Define architecture, technical specification and use cases based on the previous 2 steps, using the model driven approach.
      • Using data models can be a starting point.

 

Action Point: SPAC?

 

 

 

Action Point: all

AOBnone 
 Next Call

Next Call:

Discuss Mike's NPIF and updated contributions above

Sep 13 7am PDT, 9EDT, 4pm CEST

Agendas and Minutes for 8/16 call

TopicsDescriptionAction/Status/Comments

Agenda

8/16 call

Discuss use cases and the steps to the definition of the architecture and and services (TW-387, WT-388, etc.) and data models

Hoste: David Allan
Minutes: Georgios Karagiannis

Attendees:

  • Michael Bugenhagen, Ken Kerpez,, Charles Cook, George Dobrowski, Robin Mersh, Yuanlong Jiang, Mark Fishburn
  • Duane Remein, Kenneth Wan, Shailesh Suman
Step 1

Categories of use cases:

  • Legacy based systems and platform?? (domain) resources
  • IP or Ethernet access
  • Smart Cell,
  • IoT
  • Data center – Data center Inter-connect,
  • CDN, VR/AR
  • Public safety (safety critical services, emergency alerting),
  • Home medical and security

Platform that can support these categories:

  • Legacy
  • Legacy + SDN/NFV enabled

Features that are incorporated into the platform;

  • WT-304 includes service attributes that have been agreed by providers.
  • Start top down first. Metadata/Metaclasses  can be used to support several service attributes, e.wg different QoS.
  • Good to create data models/service definitions. This could be part of Step 3.

Action Point: Mike Bugenhagen works on this step and provides first draft,
which will be incorporated in SD-377, in one week from now, MB

 

Step 2:

Description of network deployments

Validation of the network deployments with operators/providers

Action Point: ALL

Action Point: SPAC?

Step 3:

Define architecture, technical specification and use cases based on the previous 2 steps, using the model driven approach.

Using data models can be a starting point.

Action Point: All
Additional comments

Probably the BAS work could be overlapping with other BBF work (SD-373, etc.);

Discussion on overlapping topics between BAS and other BBF activities could be incorporated in the migration discussion during BBF Q4 2016.

Important to base the BAS work on existing BBF work (and/or elsewhere) and enhance it in order to support the BAS advanced services.

 
Next CallAug 30 7am PDT, 9EDT, 4pm CEST 

.

BBF Wiki Home Page | Privacy Policy | Terms of Use