Issue in MEF 7.3 and MEF-LSO-Sonata-SDK alignment

[priyatg]

1. MEF 7.3 defines the Object Type Model (find attached) for UNI/Operator UNI/Service Provide UNI Object (most important thing highlighted as red)

2. As you can see, Relation and Multiplicity between UNI and Operator UNI defined as 1:*. Also this is confirmed in MEF 7.3 requirement: - “This attribute represents the relationship between the UNI and an OperatorUni. A UNI has to be associated to at least one of the ServiceProviderUni or OperatorUni(s). It is possible to be associated to both.”

3. In other hand in MEF26.2 we can find following description: “Section 7 of MEF 10.3 [12] restricts the UNI to the use of a single Service Provider. This document aligns with this constraint. To this end, a UNI can only be associated with a single Operator that is not a Super Operator, and may be associated with multiple Super Operators only if they have a hierarchical contractual relationship between them relating to the UNI in question. In particular, if an Operator (including Super Operators) provides an OVC to a UNI to a given SP/SO, then all other OVCs provided by the Operator to the same UNI have to be provided to the same SP/SO. In other words, an Operator (including a Super Operator) cannot provide OVCs to the same UNI to multiple SP/SOs.”
   Looks like in following cases – Operator A share UNI Interface between Operator B and Operator C, but Operator A UNI Interface is used only by Service Operator A (find attached Image1.png)

4. But most important things defined in https://github.com/MEF-GIT/MEF-LSO-Sonata-SDK/ [github.com] for Operator UNI.

As you can see from Image2.png – Operator UNI inherited from CarrierEthernetExternal Interface Object Type directly – w/o UNI ObjectType. All parameters defined on UNI Object Type in MEF7.3 were moved to OperatorUNI Object Type in MEF-LSO-Sonata-SDK. And “operatorUniList (reference)” attribute was removed at all in MEF-LSO-Sonata-SDK, but still present in MEF 7.3.

Kindly confirm if this is a bug in MEF-LSO-Sonata-SDK or MEF 7.3 .

Thanks,
Priya TG

[MichalLaczynskiAmartus]

Hi @priyatg,

Unfortunately, we cannot see the images you are talking about.
Can you please attach them to the issue?
Simply by dragging into the response window.

Michał

[priyatg]

[priyatg]

Hi Mike, I attached the images as you suggested. Hope it is clear now.

Regards,
Priya

[priyatg]

Hello,

Any findings on this issue? Appreciate if someone can confirm this.

[MichalLaczynskiAmartus]

Hello,

There is an updated version: MEF 7.4 that is currently entering a Letter Ballot.
You can find it in the link below:
https://wiki.mef.net/download/attachments/118005694/L75017_001_Carrier_Ethernet_W7_4_LB_Pugaczewski.pdf?version=1&modificationDate=1601306302000&api=v2

The model there has changed.
Please go through it. I hope it can answer your question. If not, please ask in the context of what is in 7.4.

Michał

[priyatg]

Hi Michal,

Thank you for the response. Will go through MEF 7.4.
I have another question - Is there any standard defined for converting Information model to API data model?
Please let me know.

Regards,
Priya

[jtpugac]

All, Here is MEF W7.4 version that has recently gone to Letter Ballot. Regarding the question of converting an information model to API below is a figure I put together that describes the process. I believe this is an area that could use additional work in tooling. There are some promising tools that are not complete and we could discuss on a conference call. Thanks, Jack [cid:[email protected]] From: priyatg <[email protected]> Reply-To: MEF-GIT/MEF-LSO-Sonata-SDK <[email protected]> Date: Wednesday, October 14, 2020 at 6:14 AM To: MEF-GIT/MEF-LSO-Sonata-SDK <[email protected]> Cc: Subscribed <[email protected]> Subject: Re: [MEF-GIT/MEF-LSO-Sonata-SDK] Issue in MEF 7.3 and MEF-LSO-Sonata-SDK alignment (#164) CAUTION: This email originated outside of Lumen Technologies. Do not click links or open attachments unless you recognize the sender and know the content is safe. Hi Michal, Thank you for the response. Will go through MEF 7.4. I have another question - Is there any standard defined for converting Information model to API data model? Please let me know. Regards, Priya — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub<https://imss91-ctp.trendmicro.com:443/wis/clicktime/v1/query?url=https%3a%2f%2fgithub.com%2fMEF%2dGIT%2fMEF%2dLSO%2dSonata%2dSDK%2fissues%2f164%23issuecomment%2d708334047&umid=6236B369-B19F-A005-BD85-B633B70AA3C7&auth=19120be9529b25014b618505cb01789c5433dae7-cd5ab9d9916dfeac33d05ee234f194bd9b817cc3>, or unsubscribe<https://imss91-ctp.trendmicro.com:443/wis/clicktime/v1/query?url=https%3a%2f%2fgithub.com%2fnotifications%2funsubscribe%2dauth%2fACR4QO2NEFF5ZM54M6ODNH3SKWBVLANCNFSM4REPUTYA&umid=6236B369-B19F-A005-BD85-B633B70AA3C7&auth=19120be9529b25014b618505cb01789c5433dae7-356fbf7a7af19dc4a326325e3ef223444ab80f74>. This communication is the property of Lumen Technologies and may contain confidential or privileged information. Unauthorized use of this communication is strictly prohibited and may be unlawful. If you have received this communication in error, please immediately notify the sender by reply e-mail and destroy all copies of the communication and any attachments.

[priyatg]

Hi Jack,

Thank you for the prompt response. I am unable to view the figure, can you share it again?

Regards,
Priya

[jtpugac]

Priya, I am attached the Powerpoint with figure and notes. Please let me know if this works. Thanks, Jack From: priyatg <[email protected]> Reply-To: MEF-GIT/MEF-LSO-Sonata-SDK <[email protected]> Date: Wednesday, October 14, 2020 at 7:34 AM To: MEF-GIT/MEF-LSO-Sonata-SDK <[email protected]> Cc: "Pugaczewski, Jack" <[email protected]>, Comment <[email protected]> Subject: Re: [MEF-GIT/MEF-LSO-Sonata-SDK] Issue in MEF 7.3 and MEF-LSO-Sonata-SDK alignment (#164) CAUTION: This email originated outside of Lumen Technologies. Do not click links or open attachments unless you recognize the sender and know the content is safe. Hi Jack, Thank you for the prompt response. I am unable to view the figure, can you share it again? Regards, Priya — You are receiving this because you commented. Reply to this email directly, view it on GitHub<https://imss91-ctp.trendmicro.com:443/wis/clicktime/v1/query?url=https%3a%2f%2fgithub.com%2fMEF%2dGIT%2fMEF%2dLSO%2dSonata%2dSDK%2fissues%2f164%23issuecomment%2d708370735&umid=10B843E8-B1A0-BE05-85A2-5B6D8742CE89&auth=19120be9529b25014b618505cb01789c5433dae7-7957b11490f828bcb29a2baed4191ac28d4bf97b>, or unsubscribe<https://imss91-ctp.trendmicro.com:443/wis/clicktime/v1/query?url=https%3a%2f%2fgithub.com%2fnotifications%2funsubscribe%2dauth%2fACR4QO4LSEMPUHWDPIZQS2DSKWLBDANCNFSM4REPUTYA&umid=10B843E8-B1A0-BE05-85A2-5B6D8742CE89&auth=19120be9529b25014b618505cb01789c5433dae7-496d022fd765edece2da02145b338c1f3a5b24db>. This communication is the property of Lumen Technologies and may contain confidential or privileged information. Unauthorized use of this communication is strictly prohibited and may be unlawful. If you have received this communication in error, please immediately notify the sender by reply e-mail and destroy all copies of the communication and any attachments.

[priyatg]

Hi Jack,

The problem still remains :-) I am reaching out to you through email to get the power point slide. Hope this is OK.

Regards,
Priya