RE: [802.3ae_Serial] Updated issue list; phone conference tomorro w as usual
Juergen,
By "Technical feasibility" I meant that the "PMD Technical Feasibility
Demonstration" activity would be not be organised by this agenda but by the
plan and coordinators set up by Vipul Bhatt. I meant no particular
connection with the two lines above that one.
Piers
> -----Original Message-----
> From: Rahn, Juergen (Juergen) [mailto:krahn@xxxxxxxxxx]
> Sent: 24 July 2001 10:25
> To: '802.3ae Serial'; 'DAWE,PIERS (A-England,ex1)'
> Subject: AW: [802.3ae_Serial] Updated issue list; phone conference
> tomorrow as usual
>
>
> Hi,
> Concerning the letter from ITU there is stated :
> issues concerning link verification and link engineering (In
> particular in
> light of the attenuator management in 1550nm range). This may
> be covered by this agenda item,
> And it stated that there is something to be covered by other groups.
> I suspect this is the triple tradeoff and the description
> and use of the
> RMS width for SLM . As this is not on the agenda I am a bit
> curios who is the group to deal with this?
> Regards Juergen
>
> > ----------
> > Von: DAWE,PIERS (A-England,ex1)[SMTP:piers_dawe@xxxxxxxxxxx]
> > Gesendet: Montag, 23. Juli 2001 20:29
> > An: '802.3ae Serial'
> > Betreff: [802.3ae_Serial] Updated issue list; phone conference
> > tomorrow as usual
> >
> >
> > Here are the list of actions from the database with some other known
to-do
> > items. You will see that the comment database is pretty repetitive:
> > basically, check all the dB numbers in all the tables. By eliminating
> > unallocated margin and making the link attenuation normative, we should
> > end
> > up with simpler, more understandable tables. I am working on a
> > spreadsheet
> > update to support this.
> >
> > Serial PMD ad hoc issues list
> > -----------------------------
> > # numbers are from comment database
> >
> > General
> > -------
> > Liaison letter from ITU-T SG15
> > Optical power measurement in network maintenance
> > (Technical feasibility - covered by other groups)
> >
> > All wavelengths
> > ---------------
> > # 317 combine Rx jitter tolerance and Rx sensitivity tests
> > further work (add calibration sequence, etc.).
> >
> > Road-test jitter and stressed sensitivity measurements
> > Jitter spec values
> >
> > Road-test the test patterns (LAN and WAN?)
> >
> > SR/SW
> > -----
> > # 77
> > Check SR/ SW Rx sensitivity value. May need to allow for
> jitter penalty.
> > # 78
> > Check SR/ SW stressed Rx sensitivity value. May need to
> allow for jitter
> > penalty.
> > # 79
> > Check SR/ SW vertical eye closure penalty value.
> > # 81
> > Check SR/ SW link power penalties.
> >
> > LR/LW
> > -----
> > Obtaining test fibers or equivalent for 1310 dispersion penalty
> > measurement
> > # 364
> > power budget, 1310 nm Tables 52- 12, table 52- 14 and
> tables 52- 15 are
> > not
> > clear understandable and probably inconsistent.
> > Send to Serial PMD ad hoc.
> > # 367,368,130
> > maximum average transmitter power and receiver overload
> changed to 0.5 dBm
> > by #130 and sent to Serial PMD ad hoc for final resolution.
> > # 89
> > Check LR/ LW Tx triple trade off table.
> > # 86
> > Check LR/ LW Rx sensitivity value. May need to allow for
> jitter penalty.
> > # 87
> > Check LR/ LW stressed Rx sensitivity value: thought very
> demanding by
> > some.
> > May need to
> > allow for jitter penalty.
> > # 88
> > Check LR/ LW vertical eye closure penalty value.
> > # 90
> > Check LR/ LW link power penalties. Need to allow for
> reflection noise and,
> > to be decided,
> > jitter penalty.
> >
> > ER/EW
> > -----
> > # 363
> > power budget, 1550 nm Tables 52- 17, table 52- 18 and
> tables 52- 19 are
> > not
> > clear understandable and probably inconsistent.
> > Send to Serial PMD ad hoc.
> > # 96
> > Check ER/ EW link power penalties. May need to allow for
> jitter penalty,
> > to
> > be decided.
> >
> > Tomorrow's phone conference
> > ---------------------------
> > Usual coordinates:
> > 15:15 GMT = 4:15 pm BST = 17:15 CET = 11:15 am EDT =
> 8:15 am PDT,
> > Tuesday
> > +1(816)650-0631 Access code 39209
> >
> > Piers
> >
>