John:
Let me propose something different. There are 2 priorities: 1) Priority 1 – something that fits the market, and provides easy reading by users 2) Priority 2 – something that is architecturally clean I understand you feel your base model is architecturally perfect. Feedback from product groups are that your model are difficult to understand. The models from the teams that have worked on the hackathon have been understood and worked on by the teams. We should work toward both. An attitude that says “my model’s perfect” does not align with the yang model’s readably . Just my 2 cents. Sue Hares From: I2nsf [mailto:i2nsf-boun...@ietf.org] On Behalf Of John Strassner Sent: Sunday, July 16, 2017 1:36 PM To: Linda Dunbar; John Strassner Cc: i2nsf@ietf.org Subject: Re: [I2nsf] need some work to improve the consistency of I2NSF Information and data model: maybe a design team? I cannot attend Prague due to family health issues. That being said, I agree with Linda. I see three major problems: 1) There should be one, and only one, information model. a) It is great to have multiple contributions, but those contributions MUST be written to enhance the existing model, not propose a new one 2) In general, some of the info models are not really **models** per se, but rather, requirements for models. 3) In general, I cannot trace data model work back to the info model work. a) This is especially true for drafts that are trying to use or define policies I propose that draft-xibassnez is used for our info model. This means that the other info model drafts SHOULD be restructured to add to that draft. I propose that we wait on further data model draft definition until some people (I will help) on the design team can formulate guidelines and perhaps examples to properly derive data models from our info model. regards, John On Fri, Jul 14, 2017 at 9:27 AM, Linda Dunbar <linda.dun...@huawei.com> wrote: Thanks to many people contributions. We now have many drafts on the information model and data model for I2NSF: Information model: draft-xibassnez-i2nsf-capability-02 draft-zhang-i2nsf-info-model-monitoring-04 draft-hyun-i2nsf-registration-interface-im-02 draft-kumar-i2nsf-client-facing-interface-im-03 draft-xia-i2nsf-security-policy-object-01 Data Model: draft-hares-i2nsf-capability-data-model-03 draft-jeong-i2nsf-consumer-facing-interface-dm-02 draft-kim-i2nsf-nsf-facing-interface-data-model-02 draft-hyun-i2nsf-registration-interface-dm-01 But the problem is that they are not all consistent. Extra work is needed to improve the consistency for I2NSF information and data models for both Client/Consumer facing and NSF facing interfaces. So we are going to form a design team to work on it. If you are interested in participate, please click on this doodle poll: https://doodle.com/poll/4ryrcw3993fbf7ca For people not in Prague, we can set up a Webex for you to call in. Thank you very much for the contribution. Linda & Adrian _______________________________________________ I2nsf mailing list I2nsf@ietf.org https://www.ietf.org/mailman/listinfo/i2nsf -- regards, John
_______________________________________________ I2nsf mailing list I2nsf@ietf.org https://www.ietf.org/mailman/listinfo/i2nsf