Dear colleagues,
I started working on Action Item #13 and went through the cleanup of Clause 12 and Clause 13, resulting in the two following comments and attached contributions.
Technical | Yes | 229 | 12 | 1 | Action Item #13 requires updates to Clause 12 content as follows:
- remove "12.2.1 DPoE eOAM management" (no more profiles) and promote all subclauses by one level
- remove "12.3.1 Software upgrade using DPoE eOAM management" (no more profiles) and promote all subclauses by one level, merge text from under 12.3.1 into 12.3
- replace all references to 1G/10G-EPON MPCP with 802.3ca, 144.3.7
- fix cross references to all figures and subclauses in Clause 12 itself
- replace references to 13.4 and 14.4 (no more profiles) with Clause 13 and Clause 14, respectively
- update all references to subclauses and tables in Clause 13 and Clause 14 with proper references
- replace "The eOAM version negotiation phase, such as the one described in 12.2.1, is not used in this profile, and tThe OLT is expected to support all the versions of the eOAM management suite that are supported by the fielded ONUs connected to its ports. " with "The OLT is expected to support all the versions of the eOAM management suite that are supported by the fielded ONUs connected to its ports. " since there are no more profiles.
- strike 4 instances of "complying with the requirements of this profile" - there are no more profiles
- strike "for this profile " - there are no more profiles | See tf4_2110_hajduczenia_01.pdf for all the tracked changes to Clause 12.
Update PICS (not covered in this contribution) |
Technical | Yes | 246 | 13 | 1 | Action Item #13 requires updates to Clause 13 content as follows:
- remove all references to profile by striking the following statements: "specified in this profile" (3x), ", and defined by this profile" (3x), " used by this profile", "specified for this profile" (3x), "for this profile" (3x), and "required for compliance with this profile " - we do not have profiles anymore
- revise Table 13-5, Version field, to use only value 0x30 to signal compliance with IEEE Std 1904.4. All other values are reserved for backward compatibility | See tf4_2110_hajduczenia_02.pdf for all the tracked changes to Clause 13.
Update PICS (not covered in this contribution) |
Apart from editorial and small technical changes (e.g., remove any references to profile, since we do not do profiles anymore in 1904.4), the largest change I wanted to signal was in Table 13-5 (Information TLV), which contains the eOAM version information. I suggest we use 0x30, which is backward compatible with 1904.1 versions used for Package A, and signals a new version block. I do not expect a lot of revisions to 1904.1, but we still have more than 10 possible minor revisions available. I believe it is plenty.
Now, Action Item #13 calls also for new ONU capability discovery
13 | Device and capability discovery | New 802.3ca behavior | New capabilities (fragmentation, multiple channels, etc.) |
covering fragmentation, multiple channels, etc. Rather than cram them into the Information TLV, I suggest we create a new capability TLV under 0xDB branch, and create entries for following capabilities:
- Support for downstream fragmentation (Boolean)
- Support for upstream fragmentation (Boolean)
- Number of downstream channels supported (int, 1 byte)
- Number of upstream channels supported (int, 1 byte)
These 4 entries exhaust the capabilities I can think of and that are not otherwise covered elsewhere. To follow up, we might want to allow for fragmentation to be disabled (R/W) in downstream and upstream directions, but I am struggling to find a reason to change the number of channels supported.
Are there any other capabilities we should be reporting for the ONU that are specific to 803.3ca systems?
Thank you
Marek
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