Child pages
  • Contributions
onf2017.154IMP Work Items for future release V1.4: 7/2018V1.5: 4Q2018
Participation - L = Lead, P = actively Participate
ItemShort NameTR-512 sub docReleaseChris HNigel DKam LBernd ZMalcolm BRod LQilei WXiang YYuji TItalo BXing ZKarthik SSteve SAndrea MScott MSibylle SAugie JRick JingPriorityStart Date1st Draft date1st reviewupdatefinal reviewTarget publica.Brigade Process ?Nov. Meeting DeliverableLong Description
1Controller81.4LPPPP?P8-Jun18/6-22/625/6-6/79/7-20/723/7-27/7Controller model and NE deconstruction (at least some more examples)
3Specification71.4LPPP 25-Sep8-Jun18/6-22/625/6-6/79/7-20/723/7-27/7Spec model (with Tapi) * Especially scheme spec related to the photonic model
4Software121.4LPP8-Jun18/6-22/625/6-6/79/7-20/723/7-27/7Modelling of software, Good material from TMF TR-225 * And relating it to hardware and emergent function
Software exampleA.13L8-Jun18/6-22/625/6-6/79/7-20/723/7-27/7
5OAM91.5PPPPPPPL P25-SepNoOAM (called for by Tapi); For November delivery generalize whatever in the current TAPI OAM
6Resilience51.5PP?LNoResilience examples (as called for by TAPI)
8Equipment enhancements61.4L 8-Jun18/6-22/625/6-6/79/7-20/723/7-27/7Equipment (as called for by TAPI). Chris: mix a lot of core framework with other stuff, Nigel: May need a strong story for v1.3.1 * Spec of capability; * Defining the properties of the equipment; * Equip - function (in the PC) Move the spec to 1.5
10Operation Patterns101.4LPPPP8-Jun18/6-22/625/6-6/79/7-20/723/7-27/7Model patterns to support operations patterns including intent, TOSCA and policy (with Boulder), query More than just intent Join the operation pattern into the control
12Entity lifecycle31.5PPLPPP2-OctLifecycle of entities (including split and join) * Dynamic view/abstraction/virtualization
15RationaleA.31.4L 2-Oct8-Jun18/6-22/625/6-6/79/7-20/723/7-27/7 1.3 overhang: Modelling rationale, ...
16P&R MethodologyLPPPrune &Refactoring methodology and tooling
17UML GuideTR-5141.3PLPDone18/6-22/625/6-6/79/7-20/723/7-27/7UML Modeling Guidelines
18Papyrus GuideTR-5151.3PLPDone18/6-22/625/6-6/79/7-20/723/7-27/7Papyrus Guidelines
19UML-YANG GuideTR-5312PLPPDone18/6-22/625/6-6/79/7-20/723/7-27/7Mapping Guidelines
20UML-OAPI GuideTR-543?Mapping Guideines
22UML-Yang GenUML-Yang Generator
23UML-OAPI GenUML-OAPI Generator
25P&R ToolingPL
27UML-Protobuf GuideTR-544LP?Done
31Layer Examples (packet)A.61.4PPPL P?25-SepMarch18/6-22/625/6-6/79/7-20/723/7-27/7NoMore examples of layers (as called for by TAPI etc) * Defer L0 (media (photonic and wireless)) Analogue; * Focus on L1/2 Circuit; * L2/3 (inc LAG) Packet; * Multilayer etc
2Processing Construct111.4LPPP?PDone18/6-22/625/6-6/79/7-20/723/7-27/7NoSlide pack for TOSCAPC/Component/VNF/TOSCA * Should we continue to have ControlComponent as a specialized class of PC/Component
13Model StructureA.21.5LPNoModel structure & model patterns, Chris: cycle of model, need architecture of the model, Nigel: need cleaning
14Topology4 1.5LPP?P25-SepTopology stuff outstanding (IETF TEAS comparison). Fix ForwardingEntity _PAC model (should be decoration/spec); Per TAPI request, need to develop examples of usage of the topology Pacs. Consider pull this for 1.4 for TAPI needs.
21UML-TOSCA Guide1.5PPLHMapping Guideines
24UML-TOSCA Gen1.5LUML-TOSCA Generator
26Intent1.5LPP?P?P?28-SepBrigade (joint with ONOS)Could lead to use the operation patterns; could be merged into operation patterns
28UML-Protobuf Gen1.5PL?
29Party model1.5LP
30Location model1.5LP
7Layer Examples (circuit)A.51.4L March18/6-22/625/6-6/79/7-20/723/7-27/7
9IP1.5?PPIP driven by requirements from ECC/DCN ensuring we have core support (IMP, OT, TAPI brigade * Extending over time to “full” IP via appropriate collaboration and federation
11Views1.5?L?PView abstractions and virtualisation
32Photonic model examplesA.41.4L8-Jun18/6-22/625/6-6/79/7-20/723/7-27/7
11/6 – 15/6 (in Ottawa)
18/6 -22/6 review
25/6 -6/7 2 weeks update
9/7 – 20/7 2 weeks final review
23/7 – 27/7 update and publish