The one question I do have – why do we even have to show OMCI? There are many other clients which may (or may not) be supported. Do we have now to show all of them?
Rather than show OMCI, I’d recommend showing just “Other non-OAM clients” instead to cover them all with a single drawing
Marek
From: stds-1904-2-tf@xxxxxxxx <stds-1904-2-tf@xxxxxxxx> On Behalf Of Glen Kramer
Sent: Wednesday, June 5, 2019 12:07 PM
To: STDS-1904-2-TF@xxxxxxxxxxxxxxxxx
Subject: The latest layering diagram
All,
In Salt Lake City, Kevin and I discussed the UMT layering diagram some more. The focus was on how to support the C57 loopback, while a device may be receiving both native OAMPDUs and OAM over UMTPDUs.
Another challenge was the desire to support OMCI, which also can be in two forms: OMCI over OAMPDUs (per ITU-T G.988) or OMCI directly over UMTPDUs.
Kevin and I believe the following layering diagram solves all these issues.
These diagram is somewhat similar to what I presented on the last conference call, but it has the UMT layer extended to allow native OMCI interface to OMCI client.
You may want to look again at the presentation from the call, which explains how UMT layer operates.
http://www.ieee1904.org/2/meeting_archive/2019/04/tf2_1904_kramer_layering_3.pdf
-Glen
To unsubscribe from the STDS-1904-2-TF list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-1904-2-TF&A=1
To unsubscribe from the STDS-1904-2-TF list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-1904-2-TF&A=1