1 Management of Networks of Constrained Devices: Use Cases and Requirements draft-ersue-constrained-mgmt-01 draft-ersue-constrained-mgmt-01 IETF #84, Vancouver,

Slides:



Advertisements
Similar presentations
1 IETF Network Management Framework and Standards draft-ersue-opsawg-management-fw-01 draft-ersue-opsawg-management-fw-01 IETF #79, Beijing O&M Area Working.
Advertisements

IPv6 Multihoming without Network Address Translation draft-ietf-v6ops-multihoming- without-ipv6nat-00.
United Nations Statistics Division Review of the Implementation Guide to ISIC Rev.4.
Design Plans CSCI102 - Systems ITCS905 - Systems MCS Systems.
What If I Must Go Beyond a Preliminary Assessment? (the example of a USAID EA under Reg. 216) [DATE][SPEAKERS NAMES]
PN UNC AMR Topic Workgroup Meeting 19 – Meter Reading.
Draft-campbell-dime-load- considerations-01 IETF 92 DIME Working Group Meeting Dallas, Texas.
Progressing the Work on the MAS TR-0006, TR-0007 Group Name: Management Abstraction and Semantics Source: Tim Carey, ALU,
UNI Extensions for Diversity and Latency Support 13-Mar-13IETF 86 Orlando1 Don Dieter.
Draft-chown-v6ops-renumber-thinkabout-05 Things to think about when Renumbering an IPv6 network Tim Chown IETF 67, November 6th, 2006.
Prefix Delegation Protocol Selection T.J. Kniveton MEXT Working Group IETF 70 - December ’07 - Vancouver.
OMA Mobile liaison Considers the OMA Mobile Requirements as input from the mobile community in terms of requirements for mobile features.
OneM2M-REQ R03 Proposed simple guidelines for writing use cases and requirements Group Name: oneM2M WG1 / WG2 Source: Joerg Swetina (NEC), Ataru.
MPTCP – MULTIPATH TCP Interim meeting #3 20 th October 2011 audio Yoshifumi Nishida Philip Eardley.
6LoWPAN Security Analysis Soohong Daniel Park Ki-Hyung Kim Eunil Seo Samita Chakrabarti Julien Laganier.
CDN Interconnection Problem Statement draft-jenkins-cdni-problem-statement-02 Ben Niven-Jenkins Francois Le Faucheur Nabil Bitar.
Group Name: oneM2M WG1 Requirements Source: Phil Hawkes, Rapporteur “Benefits of oneM2M technology” TR,
1 COnstrained MANanagement (COMAN) Management of Networks with Constrained Devices: Use Cases and Requirements draft-ersue-constrained-mgmt-02 draft-ersue-constrained-mgmt-02.
How to write a professional paper. 1. Developing a concept of the paper 2. Preparing an outline 3. Writing the first draft 4. Topping and tailing 5. Publishing.
Access and Query Task Force Status at F2F1 Simon Miles.
OPSREA Open Meeting Area Directors: Dan Romascanu and Ron Bonica Monday, July 26, 2010 Afternoon Session 2, 15:20– 17:20, Brussels Room Discussion list.
RPL Applicability Statement for AMI IETF #81, IETF ROLL WG Québec City, Canada July 25-29, 2011 Jorjeta Jetcheva
Draft-tarapore-mbone- multicast-cdni-06 Percy S. Tarapore, AT&T Robert Sayko, AT&T Greg Shepherd, Cisco Toerless Eckert, Cisco Ram Krishnan, Brocade.
Conclusions Buenos Aires, – December 5 th, 2004 CDM Methodologies and Project Design Workshop for CDM Project Developers.
RADEXT WG IETF 91 Rechartering. Why? Current charter doesn’t allow us to take on new work that is waiting in the queue Has an anachronistic Diameter entanglement.
Group Name: oneM2M WG1 Requirements Source: Phil Hawkes, Rapporteur “Benefits of oneM2M technology” TR,
IETF #86 - NETCONF WG session 1 NETCONF WG IETF 86 - Orlando, FL, USA MONDAY, March 11, Bert Wijnen Mehmet Ersue.
IETF #84 - NETCONF WG session 1 NETCONF WG IETF 84, Vancouver, Canada MONDAY, July 30, Bert Wijnen Mehmet Ersue.
10 Informal Reports.
A Framework for Session Initiation Protocol User Agent Profile Delivery (draft-ietf-sipping-config-framework-11) SIPPING – IETF 68 Mar 19, 2007 Sumanth.
GEONET Brainstorming Document. Content Purpose of the document Brainstorming process / plan Proposed charter Assumptions Use cases Problem description.
Report writing. What is a report?? Record of a particular event. The literal meaning of the word report is a collection of formal or official statements,
Problem Statement: IP Address Configuration for IPDVB draft-stiemerling-ipdvb-config-02.txt M. Stiemerling (Ed.), G. Gardikis, H. Asgari, D. Negru, T.
Draft-melia-mipshop-mobility-services-ps-01.txt. From IETF #66 Discuss MIH PS (as expressed by the WG chair) Need a single PS at WG level (several drafts.
LMAP WG IETF 92, Dallas, TX Dan Romascanu Jason Weil.
Minutes of the Meeting IoT WG GISFI#6 Neemrana, Rajasthan 1 IoT_MoM_Sept_2011GISFI # 06, Sept , 2011.
Group Name: oneM2M WG1 Requirements Source: Phil Hawkes, Rapporteur “Benefits of oneM2M technology” TR,
GEONET Brainstorming Document. Content Purpose of the document Brainstorming process / plan Proposed charter Assumptions Use cases Problem description.
IETF #82 - NETCONF WG session 1 NETCONF WG IETF 82, Taipei, Taiwan TUESDAY, November 15, Afternoon Session III Bert Wijnen Mehmet Ersue.
Interdomain Multicast BCP Draft IETF 84 Vancouver, BC Robert Sayko
IPFIX Requirements: Document Changes and New Issues Raised Jürgen Quittek, NEC Benoit Claise, Cisco Tanja Zseby, Sebstian Zander, FhG FOKUS.
68th IETF, Prague, March 2007 Requirements for Manageability Sections in PCE Working Group Drafts draft-ietf-pce-manageability-requirements-01.txt Adrian.
YANG Data Model for IPv4-in-IPv6 Softwire draft-sun-softwire-yang November 2014 Q. Sun, H. Wang, Y. Cui, I. Farrer (presenter), M. Boucadair.
IETF 66 – SIMPLE WG SIMPLE Problem Statement Draft-rang-simple-problem-statement-00 Tim Rang - Microsoft Avshalom Houri – IBM Edwin Aoki – AOL.
IETF #85 - NETCONF WG session 1 NETCONF WG IETF 85, Atlanta, USA WEDNESDAY, November 7, Bert Wijnen Mehmet Ersue.
Draft-ietf-v6ops-addcon-01.txt IPv6 Unicast Address Assignment Considerations Gunter Van de Velde (editor), Tim Chown, Ciprian Popoviciu, Olaf Bonness,
UEF // University of Eastern Finland How to publish scientific journal articles? 10 STEPS TO SUCCESS lllllllllllllllllllllllllllllllll lllllllllllllllllllllllllllllllll.
XCON WG IETF-64 Meeting XCON Framework Overview & Issues
IETF 67, MPLS WG, San Diego 11/08/2006
Thierry Ernst (INRIA and WIDE) Hesham Soliman (Ericsson)
OmniRAN Introduction and Way Forward
RIPE IPv6-wg and Renumbering
76th IETF meeting, November 8-13, 2009
NAT Behavioral Requirements for Unicast UDP
Recommendations from the Stage 3 Trial Review
EC GUIDANCE ON IWT AND NATURA 2000 INTRODUCTION
Requirements for IPv6 Routers draft-ietf-v6ops-ipv6rtr-reqs
Submission Title: [SGLECIM PAR & 5C comment resolution November 2010]
DG Environment, Unit D.2 Marine Environment and Water Industry
Item 6: Improving assessment of GES Draft conclusions and Way forward
IETF-100, MPTCP WG, November 2017
ภาควิชาวิทยาการคอมพิวเตอร์ คณะวิทยาศาสตร์
BUFFALO FUND: ACCELERATOR Full Proposal Presentation
IEEE MEDIA INDEPENDENT HANDOVER DCN:
doc.: IEEE <doc#>
NFV adhoc Shitao li.
Proposed Follow-up Space Climate Observatory side-session discussions
Scene setter European Commission DG Environment
Strategi Memperbaiki dan Menyiapkan Naskah (Manuscript) Hasil Review
O&M Area Working Group WG
Presentation transcript:

1 Management of Networks of Constrained Devices: Use Cases and Requirements draft-ersue-constrained-mgmt-01 draft-ersue-constrained-mgmt-01 IETF #84, Vancouver, Canada OPS Area Open Session Mehmet Ersue Dan Romascanu Juergen Schoenwaelder

The Aim Provide a problem statement on the issue of the management of constrained networks as well as networks with constrained devices. Explain the classes for constrained device categories. Describe different topology options for the networking and management of constrained devices. Raise the questions on and understand the use cases, requirements and the required solution space for the management of constrained networks as well as networks comprised by constrained devices. Describe use cases and scenarios from the network as well as from the application point of view. Avoid recommending any particular solutions. 2

The Issues and the conclusion after the adhoc discussion on Wed morning Scope: networks with constrained devices only or also management of constrained networks? –Agreed to describe the use case for constrained networks but exclude for the detailed requirements discussion, which can be given in the annex. Classifying devices based on features –provide a list of management features and level of features to be matched to device classes and use cases (including FCAPS). –different devices in a device class might use different subsets Matching use cases to device classes –agreed to list the device categories and the assumed network size in a use case Giving specific requirements per use case and device class –planned to address in section 4. Reference available work on constrained networks/devices –e.g. FP7 EU project Butler-SmartLife 3

Some further suggestions from the adhoc discussion on Wed morning Look what other bodies are doing, e.g. ETSI device model, OMA device management, or OBIX from OASIS Include cellular and M2M use cases. Compared to the top-down view in the current document look also from the bottom-up view considering the needs of very constrained devices. –understand the requirements on simplifying the management technologies to use in very constrained devices –look at the necessary models from two angles, i.e. the minimalistic approach as well as reducing existing models. A conclusion section should summarize the gaps and highlight potential need for new work. 4

The Plan An initial draft describing the problem space and use cases from the application point of view available. Clarify and address issues discussed. Disscus on Coman maillist. Submit next draft as "draft-ersue-coman-constrained-mgmt-00" to enable simple access Get feedback of and involve constrained device experts especially in the Core WG. 5