Thread Links Date Links
Thread Prev Thread Next Thread Index Date Prev Date Next Date Index

Re: [10GMMF] Comment discussions on TP2 call 1/13/05

Proposed status on assigned comments.
Topic for today's TP2 call.
----- Original Message -----
Sent: Friday, January 14, 2005 5:03 PM
Subject: [10GMMF] Comment discussions on TP2 call 1/13/05

Per the 1/13 TP2 meeting minutes, we discussed related D1.0 comments.
  • Nick asked if we could pre-resolve some comments relating to TP2.
  • The comment list is in the agenda. All comments were discussed.
  • A separate email will attempt to capture progress.
Discussions: (note - there are some of the secretary's subsequent opinions added below, preceded with "TL -").
  • Comment 49 & 50
    • No disagreement that overshoot masks should be relaxed. Lew was not on call to present his view that overshoot masks should be eliminated, so final value decision was deferred. Plan to discuss next week.
    • Agree on value? 0.75? Remove?
    • Re-raised concern that absolute overshoot power may need to be limited for Rx linearity. No specific proposals were given, and no specific comment was submitted, so this is a potential future item.
  • Comment 81 & 83
    • Recalled that prbs pattern is for component level testing. Normative test will use a subpattern from AnAi or BnBi.
    • Agreed that final prbs pattern must be better defined, preferably referencable through another standard.
    • Agreed that final prbs pattern should be convenient, preferable built-into pattern generators.
    • It is understood that prbs7 is probably not adequate, but more work is required to determine the best option. Work is planned (see TP2 notes).
    • Discussion about insertion of extra zero to balance prbs pattern not conclusive.
      • Agilent has reported that "zero-insertion" is standard on new equipment.
    • Idea was raised to insert long(er) runs of 1's and 0's into pattern to stress lower frequency impairments. Not concluded.
    • Plan to discuss again next week.
    • Propose x^9+x^5+1, non inverting. Lew - what is ITU reference? Use this for instances for a call-out of the prbs pattern (comment 111, etc.).
  • Comment 104
    • Okay.
    • Propose accept
  • Comment 105
    • Okay, but final pattern is TBD. Experimental work is planned to evaluate samples per UI, but 7 appears adequate at this time.
    • Propose accept
  • Comment 106
    • Okay.
    • Propose accept
  • Comment 109
    • Okay. Waiting to discuss MATLAB code 1/20 on TP2 call. Editorial format for the code, including scope of comments, should follow precedence of other standards (clause 40). TL - clause 40 appears to have minimal comments.
    • Review on TP2 call 1/20. TAL has submitted presentation for background, hope for support of TP2 group.
  • Comment 111
    • Okay, but final pattern is TBD.
    • Propose accept
  • Comment 107
    • Spirit of comment is good.
    • Need noise <<N0 of simulated Rx white noise density.
    • Jan Peeters Weem to test effect of noise in lab and run through MATLAB code, report on 1/20 call.
    • TL - some follow-on discussion are occurring with good progress. Expect to conclude next week. A recommended # of averages value may be given, leaving an actual number of averages up to the tester.
    • Propose "Averaging should be used to avoid a pessimistic estimate of TWDP."
  • Comment 108
    • Okay. Crosstalk from asynchronous Rx should be removed by averaging, so requirement for simultaneous operation should not be not necessary.
    • Propose accept, but propose duplex operation should occur during RIN test.
    • TL - so does crosstalk get measured in RIN test?
  • Comment 110
    • Okay. Location and format of the informative section not clear. Editor's preference, but should follow precedence of other standards, perhaps clause 40. Comment suggest appendix, since body of standard should focus on normative material.
    • Propose accept, but does editor need more guidance?
Please respond if I errored in recording these comment discussions.
Tom Lindsay
ClariPhy Communications
phone: (425) 608-0209, or (949) 480-9210
cell: (206) 790-3240