| Thread Links | Date Links | ||||
|---|---|---|---|---|---|
| Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
|
CommentID: (Leave Blank) CommenterName: Peter Stassar CommenterEmail: peter.stassar@xxxxxxxxxx CommenterPhone: CommenterCellPhone: CommenterCompany: Huawei Technologies NL BV Clause: 115 Subclause: Page: Line: CommentType: TR Comment: In Clause 115 no required BER has been specified, so the required performance for the optics is not specified. CommentEnd: SuggestedRemedy: specify required BER performance RemedyEnd: CommentID: (Leave Blank) CommenterName: Peter Stassar CommenterEmail: peter.stassar@xxxxxxxxxx CommenterPhone: CommenterCellPhone: CommenterCompany: Huawei Technologies NL BV Clause: 115 Subclause: 115.4 Page: Line: CommentType: TR Comment: Only a single PMD 1000BASE-RH is given, but there are in fact 6 subtypes. It is general practice to make different PMD types for different power budgets. See for instance 100GBASE-LR4 and 100GBASE-ER4, which are specified in a
single clause in the same tables, with different columns. CommentEnd: SuggestedRemedy: create 6 PMDs RemedyEnd: CommentID: (Leave Blank) CommenterName: Peter Stassar CommenterEmail: peter.stassar@xxxxxxxxxx CommenterPhone: CommenterCellPhone: CommenterCompany: Huawei Technologies NL BV Clause: 115 Subclause: 115.2 Page: Line: CommentType: TR Comment: A definition of tx_signal is not provided. CommentEnd: SuggestedRemedy: create definition RemedyEnd: CommentID: (Leave Blank) CommenterName: Peter Stassar CommenterEmail: peter.stassar@xxxxxxxxxx CommenterPhone: CommenterCellPhone: CommenterCompany: Huawei Technologies NL BV Clause: 115 Subclause: 115.3 Page: Line: CommentType: ER Comment: Values for tx_signal in 115.3.3 are not clear because of the following provided relation: a ≤ tx_signal < a CommentEnd: SuggestedRemedy: add a “minus” sign to the “left-hand” “a” RemedyEnd: CommentID: (Leave Blank) CommenterName: Peter Stassar CommenterEmail: peter.stassar@xxxxxxxxxx CommenterPhone: CommenterCellPhone: CommenterCompany: Huawei Technologies NL BV Clause: 115 Subclause: 115.2 Page: Line: CommentType: TR Comment: In 115.2.1 tx_signal is stated to be analog but it is also defined to be one of 512 discrete values in Clause 114. CommentEnd: SuggestedRemedy: fix ambiguity RemedyEnd: CommentID: (Leave Blank) CommenterName: Peter Stassar CommenterEmail: peter.stassar@xxxxxxxxxx CommenterPhone: CommenterCellPhone: CommenterCompany: Huawei Technologies NL BV Clause: 115 Subclause: Page: Line: CommentType: TR Comment: How many optical levels are there? In some places there seem to be 512 (-256 through 255) and others 513 (-256 through +256)? CommentEnd: SuggestedRemedy: resolve ambiguity by appropriate definitions and specifications RemedyEnd: CommentID: (Leave Blank) CommenterName: Peter Stassar CommenterEmail: peter.stassar@xxxxxxxxxx CommenterPhone: CommenterCellPhone: CommenterCompany: Huawei Technologies NL BV Clause: 115 Subclause: 115.4 Page: Line: CommentType: TR Comment: In the transmitter spec in Table 115-3 the required signaling rate is not specified. CommentEnd: SuggestedRemedy: add signaling rate to Table 115-3 RemedyEnd: CommentID: (Leave Blank) CommenterName: Peter Stassar CommenterEmail: peter.stassar@xxxxxxxxxx CommenterPhone: CommenterCellPhone: CommenterCompany: Huawei Technologies NL BV Clause: 115 Subclause: 115.4 Page: Line: CommentType: TR Comment: The transmitter spec in Table 115-3 does not provide “conventional” transmitter quality parameters, like TDP, which are normally used to ensure that the required distance can be bridged with acceptable penalties, and eye mask
(or similar) spec that guarantees sufficient eye opening of the 16-level PAM16 signal under worst case (reflection) conditions. The commenter has been unable to find results of testing to check if the currently used parameters “amplitude”, “linearity” and
“spectral width” are sufficient to support multi-vendor interoperability. CommentEnd: SuggestedRemedy: generate appropriate specification for multi-vendor compatibility RemedyEnd: CommentID: (Leave Blank) CommenterName: Peter Stassar CommenterEmail: peter.stassar@xxxxxxxxxx CommenterPhone: CommenterCellPhone: CommenterCompany: Huawei Technologies NL BV Clause: 115 Subclause: 115.4 Page: Line: CommentType: TR Comment: The transmitter spec in Table 115-3 does not contain a parameter “Optical return loss tolerance (max)” and “Transmitter reflectance (max)”. CommentEnd: SuggestedRemedy: add additional parameters RemedyEnd: CommentID: (Leave Blank) CommenterName: Peter Stassar CommenterEmail: peter.stassar@xxxxxxxxxx CommenterPhone: CommenterCellPhone: CommenterCompany: Huawei Technologies NL BV Clause: 115 Subclause: 115.4 Page: Line: CommentType: TR Comment: The receiver spec in Table 115-4 is only specified for different power levels, not associated with any performance requirement Even a mobile phone will comply to it. CommentEnd: SuggestedRemedy: generate specification for multi-vendor compatibility RemedyEnd: CommentID: (Leave Blank) CommenterName: Peter Stassar CommenterEmail: peter.stassar@xxxxxxxxxx CommenterPhone: CommenterCellPhone: CommenterCompany: Huawei Technologies NL BV Clause: 115 Subclause: 115.4 Page: Line: CommentType: TR Comment: The receiver spec in Table 115-4 does not contain any reflectance requirement. CommentEnd: SuggestedRemedy: add reflectance to Table 115-4 RemedyEnd: CommentID: (Leave Blank) CommenterName: Peter Stassar CommenterEmail: peter.stassar@xxxxxxxxxx CommenterPhone: CommenterCellPhone: CommenterCompany: Huawei Technologies NL BV Clause: 115 Subclause: 115.4 Page: Line: CommentType: TR Comment: The receiver spec in Table 115-4 does not contain a wavelength spec. CommentEnd: SuggestedRemedy: add wavelength range to Table 115-4 RemedyEnd: CommentID: (Leave Blank) CommenterName: Peter Stassar CommenterEmail: peter.stassar@xxxxxxxxxx CommenterPhone: CommenterCellPhone: CommenterCompany: Huawei Technologies NL BV Clause: 115 Subclause: 115.4 Page: Line: CommentType: TR Comment: The receiver spec in Table 115-4 does not contain a maximum input power specification CommentEnd: SuggestedRemedy: add maximum input power to Table 115-4 RemedyEnd: CommentID: (Leave Blank) CommenterName: Peter Stassar CommenterEmail: peter.stassar@xxxxxxxxxx CommenterPhone: CommenterCellPhone: CommenterCompany: Huawei Technologies NL BV Clause: 115 Subclause: 115.4 Page: Line: CommentType: TR Comment: The receiver spec in Table 115-4 does not contain a damage threshold specification CommentEnd: SuggestedRemedy: add damage threshold to Table 115-4 RemedyEnd: CommentID: (Leave Blank) CommenterName: Peter Stassar CommenterEmail: peter.stassar@xxxxxxxxxx CommenterPhone: CommenterCellPhone: CommenterCompany: Huawei Technologies NL BV Clause: 115 Subclause: 115.4 Page: Line: CommentType: TR Comment: The receiver spec in Table 115-4 does not contain a spec for stressed receiver sensitivity with associated conditions. CommentEnd: SuggestedRemedy: add spec for stress receiver sensitivity with appropriate testing conditions to Table 115-4 RemedyEnd: CommentID: (Leave Blank) CommenterName: Peter Stassar CommenterEmail: peter.stassar@xxxxxxxxxx CommenterPhone: CommenterCellPhone: CommenterCompany: Huawei Technologies NL BV Clause: 115 Subclause: 115.4 Page: Line: CommentType: TR Comment: The link spec in Table 115-5 does not contain any maximum penalty, nor a maximum discrete reflectance. CommentEnd: SuggestedRemedy: add maximum penalty and maximum discrete reflectance to Table 115-5 RemedyEnd: CommentID: (Leave Blank) CommenterName: Peter Stassar CommenterEmail: peter.stassar@xxxxxxxxxx CommenterPhone: CommenterCellPhone: CommenterCompany: Huawei Technologies NL BV Clause: 115 Subclause: 115.5 Page: Line: CommentType: TR Comment: The optical measurements clause 115.5 does not contain any performance related testing, like TDP, with associated reference transmitters and receivers. CommentEnd: SuggestedRemedy: add performance related testing to Clause 115.5 RemedyEnd: CommentID: (Leave Blank) CommenterName: Peter Stassar CommenterEmail: peter.stassar@xxxxxxxxxx CommenterPhone: CommenterCellPhone: CommenterCompany: Huawei Technologies NL BV Clause: 115 Subclause: 115.5 Page: Line: CommentType: TR Comment: The optical measurements clause 115.5 does not contain a worst case channel spec (115.4.3 is informative). CommentEnd: SuggestedRemedy: add worst case channel spec to clause 115.5 RemedyEnd: CommentID: (Leave Blank) CommenterName: Peter Stassar CommenterEmail: peter.stassar@xxxxxxxxxx CommenterPhone: CommenterCellPhone: CommenterCompany: Huawei Technologies NL BV Clause: 115 Subclause: Page: Line: CommentType: TR Comment: It’s totally unclear if this optical configuration is not sensitive to reflections from the POF link or whether it’s very sensitive to reflections (as one would expect from the kind of multi-level signals used) and then how to
limit penalties by appropriate specifications of maximum discrete reflectance and receiver reflectance. CommentEnd: SuggestedRemedy: resolve sensitivity to reflections or state that it is not relevant, supported by appropriate testing RemedyEnd: CommentID: (Leave Blank) CommenterName: Peter Stassar CommenterEmail: peter.stassar@xxxxxxxxxx CommenterPhone: CommenterCellPhone: CommenterCompany: Huawei Technologies NL BV Clause: 115 Subclause: Page: Line: CommentType: TR Comment: Kind of conclusion on the assessment of Clause 115: The general state of Clause 115 for the optical spec appears underspecified to enable the development of multi-vendor interoperable devices. It probably will require a significant
rewrite to bring it to a significantly more complete level comparable to the 1G bi-directional specs in Clause 59. CommentEnd: SuggestedRemedy: rewrite Clause 115 to make it appropriate to support multi-vendor compatibility, similar to Clause 59. Furthermore show test results that specification methodology is sufficient to support multi-vendor compatibility. RemedyEnd: |