The only thing that comes to mind (and I hate to throw it in) is the case of a service port connecting to an embedded Ethernet switch. In this case, a single service port would be “split” into multiple UNI ports. The question on how to address individual UNIs is a separate challenge, since from the ONU perspective, they all look like a single service port. However, this is precisely what drove the addition of aPhyType attribute to address the case of a single service port terminating on a 1:2 Ethernet switch, where one UNI port is implemented as a pluggable cage and another UNI port as a standard RJ45 jack.
If we want to support such a scenario, we also need to consider if we want to be able to address individual UNI ports behind such an embedded Ethernet switch or not. It seems like a bit of a stretch for our scope of work, but on the other hand it is still part of an ONU 😊
Marek
From: stds-1904-4-tf@xxxxxxxxxxxxxxxxx <stds-1904-4-tf@xxxxxxxxxxxxxxxxx> On Behalf Of Glen Kramer
Sent: Wednesday, June 30, 2021 5:51 PM
To: stds-1904-4-TF@xxxxxxxxxxxxxxxxx
Subject: Service port types
Picking up the discussion from the last meeting on service port types.
These are the types currently defined in DPoE and SIEPON:
Q1: We decided to add another type for UNI_port. Also Ryan mentioned we need to add another type. What was this type?
Q2: Besides UNI ports, are there any service port types (i.e., eSAFE entities) that may exist as multiple instances in an ONU?
For example, can there be more than one eMTA or eDVA per ONU/CM?
Thanks,
Glen
To unsubscribe from the STDS-1904-4-TF list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-1904-4-TF&A=1
To unsubscribe from the STDS-1904-4-TF list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-1904-4-TF&A=1