| Thread Links | Date Links | ||||
|---|---|---|---|---|---|
| Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
|
Hmm…. Now that I re-read that statement, it is confusing. The intent of the statement is to convey that the OAM-based ONU management functionality that would traditionally be in the OLT is being moved to an external entity (a general purpose server, probably). The specifics of where the client resides or how it is split is what I am trying to figure out in the context of D0.6. I think there must be some lightweight version of the OAM client in the OLT, but if it’s there, then how does the OAMPDU get to it from the UMT SL? I don’t think the OLT’s OAM sublayer (on the PON side) can
be removed or else the OLT loses key functions (loopback) that should not be moved to an external location. I also wonder if the OAM sublayer needs to exist in the “Manager” side. For the purposes of OAM over UMT to manage the ONUs, I don’t think it needs to be there. Lastly, is my depiction of the tunnel correct (terminating at the UMT sublayer on the PON side of the OLT)? --kan-- -- Kevin A. Noll Sr. Director, Systems Architecture Tibit Communications kevin.noll@xxxxxxxxxxxx From: Glen Kramer <glen.kramer@xxxxxxxxxxxx> Kevin, I can try later today or tomorrow. Can you describe what this sentence means: “OLT’s OAM Client is disaggregated and moved to the ONU Manager”? Does it mean the client is split in several pieces, or that it is separated from OAM sublayer, or that the client and OAM sublayer are simply moved together to the ONU Manager? -Glen From: Kevin Noll [mailto:kevin.noll@xxxxxxxxxxxx]
Glen, Please refer to the attached PPT. Could you answer the questions contained in the slides and adjust the diagrams to help us understand how this should work? --kan-- -- Kevin A. Noll Sr. Director, Systems Architecture Tibit Communications 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 |