[Dots] DOTS Information and Data Model

Flemming Andreasen <fandreas@cisco.com> Mon, 26 September 2016 20:43 UTC

From: Flemming Andreasen <fandreas@cisco.com>
To: dots <dots@ietf.org>
Message-ID: <c26be621-9826-5122-4162-315a60dd65d4@cisco.com>
Date: Mon, 26 Sep 2016 16:43:28 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.3.0
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dots/0XMw-ffywy9eV5nAGaNfm17TvJo>
Cc: dots-chairs@ietf.org, "'Tirumaleswar Reddy (tireddy)'" <tireddy@cisco.com>
Subject: [Dots] DOTS Information and Data Model
Precedence: list

Greetings

As promised during the Berlin meeting, Tiru and I just submitted a -00 
(and very much work in progress) document for the DOTS Information and 
Data Model - we will use this as the basis for the discussion in the 
virtual interim meeting Tuesday:

https://datatracker.ietf.org/doc/draft-andreasen-dots-info-data-model/

The focus in this version has been on identifying a (high-level) set of 
logical messages and information elements that seem to be needed based 
on the DOTS requirements, DOTS use cases (WG adopted use case doc only 
for now), and DOTS architecture. For now, we have purposely not said 
anything about the particular protocol to be used or anything else 
related to "wire formats".

Expected next steps will be to drill down further on the details of both 
the messages and information elements and of course to get feedback on 
what is currently suggested in here.

Thanks

     -- Flemming

[Dots] DOTS Information and Data Model Flemming Andreasen