Thread Links | Date Links | ||||
---|---|---|---|---|---|
Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
Arkin, that is precisely why I would recommend not showing OMCI explicitly – this will only generate a lot of OMCI-related discussions on how and why, and at the end of the day UMCI is supposed to just encapsulate and carry OMCI (and other) datagrams without knowing what the upper layer protocol really does Marek From: stds-1904-2-tf@xxxxxxxx <stds-1904-2-tf@xxxxxxxx> On Behalf Of Aydin, Arkin (Nokia - US/Raleigh) To be honest, I am a bit confused about the purpose of the UMT (may be this is due to lack of background on my side due to missing the earlier meetings). Are we mentioning the GPON as a specific use-case example of "Other non-OAM clients" or is that the only client that can directly interact with UMT? If it is the only one, I am more confused about the activity because it seems that the UMT is now required to deal with "OMCI_requests" (per the picture) which is a very specific functional extension designed for GPON in the 1904. If not, then I am also curious to learn the other examples that will use both the OAM client and/or directly interact with UMT sublayer. In those cases which messages will be used to directly interact with UMT since the picture refers to such direct messages as "OMCI_requests" and "OMCI_indication". Best Regards Arkin On 6/10/2019 8:42 AM, Marek Hajduczenia wrote:
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 |