From 5cbae56e0c98565568e72965b179055a7f8f45d1 Mon Sep 17 00:00:00 2001 From: ankraft <an.kraft@gmail.com> Date: Sat, 19 Oct 2024 20:03:14 +0200 Subject: [PATCH] Improved list formatting. Corrected wrong clause numbering (7.2 -> 6.2) --- ...d_Device_Management_with_FlexContainers.md | 27 +++++++++---------- 1 file changed, 13 insertions(+), 14 deletions(-) diff --git a/WI-0109-IPE-based_Device_Management_with_FlexContainers.md b/WI-0109-IPE-based_Device_Management_with_FlexContainers.md index 8def34d..eb99b52 100644 --- a/WI-0109-IPE-based_Device_Management_with_FlexContainers.md +++ b/WI-0109-IPE-based_Device_Management_with_FlexContainers.md @@ -30,27 +30,26 @@ Device Magangement using flexContainers (IPE-based) with SDT provides a unique a The IPE-based Device Management with FlexContainers (IPE-DM) offers: - - A simplified architecture: one IPE per interworked technology, not a global CSF for the CSE to handle all external technologies. - - A simplified data model: no need to describe in each managed entity the full information on its origin. - - A simplified design: only <flexContainers>, not <mgmtObj> + <mgmtCmd>. FCs (flexContainers) are more flexible than MOs (FCs can have FC children). - - A simplified usage: unified Service & Device Management. - - An historization of DM events through flexContainerInstances. +- A simplified architecture: one IPE per interworked technology, not a global CSF for the CSE to handle all external technologies. +- A simplified data model: no need to describe in each managed entity the full information on its origin. +- A simplified design: only <flexContainers>, not <mgmtObj> + <mgmtCmd>. FCs (flexContainers) are more flexible than MOs (FCs can have FC children). +- A simplified usage: unified Service & Device Management. +- An historization of DM events through flexContainerInstances. While the current DMG CSF: - - Was designed before the creation of the <flexContainer> resource (release 2). - - Is not documented to the level required for the test purposes. - - Is designed in a way that it is the CSE that manages MOs, hence it has to 'know' the underlying DM protocols: not suited for the explosion of IoT protocols (in the proposed IPE-based DM, the 'intelligence' is in the IPEs, not in the CSE). - - - Is designed for 'real' DM protocols (BBF TR-069, OMA DM & LwM2M), not for interworking with IoT networks that have few 'pure DM' features. +- Was designed before the creation of the <flexContainer> resource (release 2). +- Is not documented to the level required for the test purposes. +- Is designed in a way that it is the CSE that manages MOs, hence it has to 'know' the underlying DM protocols: not suited for the explosion of IoT protocols (in the proposed IPE-based DM, the 'intelligence' is in the IPEs, not in the CSE). +- Is designed for 'real' DM protocols (BBF TR-069, OMA DM & LwM2M), not for interworking with IoT networks that have few 'pure DM' features. This Release 5 Work Item proposes to define an IPE-based Device Management with FlexContainers that will be more future-proof and applicable to any kind of existing or future IoT networks. This work item will specify the IPE-based Device Management with FlexContainers to cover at least the existing functional scope of device management features that are: - - the basic management features (including BBF TR-069, OMA DM & LwM2M), - - the CMDH (Communication Management and Delivery Handling) and - - the Field Device Configuration. +- the basic management features (including BBF TR-069, OMA DM & LwM2M), +- the CMDH (Communication Management and Delivery Handling) and +- the Field Device Configuration. # 3 Intended Output @@ -87,7 +86,7 @@ Provide the schedule of tasks to be performed; \* The first versions will be assigned by the secretariat (WPM Secretary) -## 7.2 CRs to existing specifications (if any) +## 6.2 CRs to existing specifications (if any) | Impacted<br />TS/TR | CR number (when known) | Subject of the CR | Approved at plenary# | Impacted WGs | Comments | |-|-|-|-|-|-| -- GitLab