Thread Links | Date Links | ||||
---|---|---|---|---|---|
Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
Hi All, I’ll jump in shortly…. From: stds-1904-4-tf@xxxxxxxxxxxxxxxxx <stds-1904-4-tf@xxxxxxxxxxxxxxxxx>
On Behalf Of Tucker, Ryan R Yes, to be fair it’s only used as part of traffic classification and not a way for the OLT to signal a particular port. Ryan From:
stds-1904-4-tf@xxxxxxxxxxxxxxxxx <stds-1904-4-tf@xxxxxxxxxxxxxxxxx>
On Behalf Of Curtis Knittle CAUTION: The e-mail below is from an external source.
Please exercise caution before opening attachments, clicking links, or following guidance.
I think the CMIM was really a bit-map in DOCSIS/DPoE, not a port type, wasn’t it? CMCI, now that might be different, which is what’s in the table.
I think configuration of ports on the other side of a switch or router would be out of scope, and I think there are other methods for provisioning these ports. Steve Burroughs may have more info here. I think this would be considered more
of a gateway, rather than the entire device being the ONU. Curtis From:
stds-1904-4-tf@xxxxxxxxxxxxxxxxx <stds-1904-4-tf@xxxxxxxxxxxxxxxxx>
On Behalf Of Marek Hajduczenia Ryan, CMIM is not really mapped into anything in 1904.1/4 right now, but yes, the concept would be pretty much the same – there should be, likely, a way to address UNI ports that are connected to a single service port across an embedded Ethernet
switch. marek From: Tucker, Ryan R <Ryan.Tucker@xxxxxxxxxxx>
Glen Q1: Here is a list from the latest copy of DPoE-OAMv2.0. It appears that 0x9-0xD are not included in the current version of SIEPON, unless I’ve missed a reference somewhere. Q2: Currently I have not seen the use case to have multiple eSAFE elements embedded in an ONU device. I am not saying there couldn’t be, just hasn’t been discussed with me. Marek, when you mention embedded switch, are you referring to some sort of eSAFE construct, or any simple switch which may exist in the ONU device? If it’s the later, I think, at least in DPoE, a Cable Modem
Interface Mask (CMIM) can be utilized to address up to 16 UNI ports on an ONU device. Ryan From:
stds-1904-4-tf@xxxxxxxxxxxxxxxxx <stds-1904-4-tf@xxxxxxxxxxxxxxxxx>
On Behalf Of Marek Hajduczenia CAUTION: The e-mail below is from an external source.
Please exercise caution before opening attachments, clicking links, or following guidance.
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 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 The contents of this e-mail message and 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 The contents of this e-mail message and 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 |