| Thread Links | Date Links | ||||
|---|---|---|---|---|---|
| Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
From a previous email: > Unless we have a strong reason to mess with the software download, Iâ??d leave it alone. (But there might be such a reason. I will clarify in a separate email.)  The software download in 1904.4 is the same as 1904.1 package A. It was based on a very high-level description in DPOE (2.5 pages) and expanded into a formal specification with message formats and state diagrams (bringing its size to a total of 15 pages). As a one-sentence description, the ONU verifies the check sequence in the received image and if it is a match, it unconditionally commits this image to activate after the next ONU restart. There is no mention of preserving the old image and rolling back if the new image causes issues for the ONU.  In contrast, the software update in Package C formally specifies the following separate steps: 1)     Image download and verification (almost like a generic file transfer) 2)     Image activation is a process where ONU restarts with the new image, but the old image is still marked as the default. If ONU booting with new image succeeds and internal diagnostic passes, the ONU resets a reboot timer and informs the OLT. If ONU booting failed, the reboot timer expires and ONU restarts again, this time with the default/old image. This step is optional. 3)     Committing new image is marking the new image as default (committed) and the old image as backup. This is done on request from the OLT after a successful activation test.  Also, this package specifies a Boot Loader state diagram, which decides which image to load based on various flags and checks.  So, my question is whether we are ok with the current specification that does not provide a roll-back to previous image in case of any issues with the software image? Or would we rather switch to package C approach? This one is 25 pages long.  Thank you, 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 |
Attachment:
smime.p7s
Description: S/MIME Cryptographic Signature