| Thread Links | Date Links | ||||
|---|---|---|---|---|---|
| Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
JC,
As Glen mentioned on the call, there are cases where the registration parameters of the ONU might need to be changed. There is no need for the ONU to go through a full blown registration, since the ONU is already known (distance, MAC address, etc.) so we can push the device to go into an accelerated re-registration process saving on time and bandwidth.
Marek
From: stds-1904-4-tf@xxxxxxxx <stds-1904-4-tf@xxxxxxxx> On Behalf Of Jean-Christophe Marion
Sent: Thursday, August 26, 2021 7:12 PM
To: Glen Kramer <000006d1020766de-dmarc-request@xxxxxxxx>
Cc: STDS-1904-4-TF@xxxxxxxxxxxxxxxxx
Subject: Re: comment against 802.3ca to fix the ONU re-registration issue
Hi Ed,
Yes, I would like to discuss it further. I was a little confused yesterday and still today about the use case. I thought that the re-register use case is to support the directed discovery. But it seems that we just want to re-register a link that was already registered. And I am confused about why we would do that.
Thanks,
Jc
On Aug 26, 2021, at 5:35 PM, Glen Kramer <000006d1020766de-dmarc-request@xxxxxxxx> wrote:
Dear colleagues,
The 802.3 maintenance TF chair just announced a series of calls to resolve comments against 802.3 D2.0. They already have a large number of comments, including 10 post-deadline comments. I would like to submit our comment fairly soon, as they consider the post-deadline comments in FIFO order.
Please take another look at the following presentation that we discussed yesterday and let me know whether you (a) agree and support this solution, or (b) can offer an improved solution.
I would like to attach this presentation as a comment supplement to better illustrate to 802.3 maintenance TF the problem and the solution. And to emphasize that this material was reviewed and vetted by many people, I would like to include all names as co-authors of this presentation. Please, let me know if it is ok to include your name on the first slide. If you don’t feel like you understand this material enough or feel uncomfortable with being listed for any reason whatsoever, it is no problem, but please let me know either way, so I don’t continue waiting. I would like to submit the comment the first half of next week.
If anyone would like to discuss this more, let me know and I will be happy to schedule a webex call.
Thank you,
Glen
From: Adam Healey <0000074ad040f574-dmarc-request@xxxxxxxx>
Sent: Thursday, August 26, 2021 4:32 PM
To: STDS-802-3-MAINT@xxxxxxxxxxxxxxxxx
Subject: [STDS-802-3-MAINT] IEEE P802.3 (IEEE 802.3dc) revision D2.0 comment resolution meeting series
Colleagues,
I am announcing a series of teleconference meetings for the resolution of comments received against the IEEE P802.3 (IEEE 802.3dc) initial Working Group ballot.
- Tuesday 7 September 2021 from 10 am to 1 pm EDT (14:00-17:00 UTC)
- Monday 20 September 2021 from 10 am to 1 pm EDT (14:00-17:00 UTC)
- Thursday 23 September 2021 from 10 am to 1 pm EDT (14:00-17:00 UTC)
- Monday 27 September 2021 from 10 am to 1 pm EDT (14:00-17:00 UTC)
The teleconference coordinates may be found on the IEEE 802.3 Call and Meeting Calendar. Note that motions may be considered at these meetings.
Please review the IEEE-SA patent, copyright, and participation policies <http://ieee802.org/3/policies.html> prior to the meeting.
Meetings have been provisioned based on a rough guess of the time needed to complete comment resolution. Meetings will be cancelled if they are not needed. However, there is not enough time to add more meetings while keeping to the target project schedule. As a result, I will allow the 27 September meeting to run as long as needed to complete comment resolution.
Comment reports will be posted following the announcement of the ballot results. I will provide more information about the comment resolution process and the expected order of consideration as we approach the 7 September meeting.
Thanks,
--Adam
To unsubscribe from the STDS-802-3-MAINT list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-3-MAINT&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
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