[1904.2 TF] comment on VLC peer address

[Glen Kramer <000006d1020766de-dmarc-request@xxxxxxxxxxxxxxxxx>]

All,

 

In our 1904.2 current architecture, a station is able to receive and process VPCPDUs carrying OAM, OMCI, or VLC_CONFIG without any rules. But to transmit a VLCPDU carrying any of these payloads, a rule is necessary to provision the destination address. This leads to the following dependency:

1.       In order to provision a destination address for OAM or OMCI tunnels, an egress rule is needed.

2.       To provision this egress rule, the VLC_CONFIG request message is issued.

3.       A VLC_CONFIG request requires a VLC_CONFIG response.

4.       Before a station can issue a VLC_CONFIG response, an egress rule is required to provision VLC tunnel destination address

 

Altogether, that implies that the very first rule should ALWAYS be the egress rule that provisions the VLC destination address.

But maybe we donâ??t need to have that implied requirement.

 

A station can automatically determine the VLC peer MAC address from the received VLC_CONFIG request. No explicit rule is necessary.

To do this, we need to make changes to both receive and transmit state diagrams, but this changes are very small, as shown below.

If we do this, then we donâ??t need to have that initial rule to provision VLC peer address.

 

Of course, we still may want to have such rule in a hypothetical use case when the destination of VLC response is not the same as the source of the VLC request. (I cannot think of an actual use case for this, but the capability to handle this is still preserved.) Below are the changes needed to the state diagrams.

 

VLC Receive SD:

 

VLC Transmit SD:

 

 

We can potentially expand this behavior to OMCI payloads by adding another variable OmciPeerAddr.

I am thinking of submitting a comment to make this change, but would like to know if anyone sees any issues with this approach.

 

Thank you,

-Glen

 

This electronic communication and the information and any files transmitted with it, or attached to it, are confidential and are intended solely for the use of the individual or entity to whom it is addressed and may contain information that is confidential, legally privileged, protected by privacy laws, or otherwise restricted from disclosure to anyone else. If you are not the intended recipient or the person responsible for delivering the e-mail to the intended recipient, you are hereby notified that any use, copying, distributing, dissemination, forwarding, printing, or copying of this e-mail is strictly prohibited. If you received this e-mail in error, please return the e-mail to the sender, delete it from your computer, and destroy any printed copy of it.

---

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

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature