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

Re: [10GMMF] Notes from 1st TP2 working group call, 7/30/04

I was on vacation at the time of the call but I’m confirming my interest in contributing to this TP2 effort.  


Thanks for the detailed notes – they were helpful in getting updated. Please avoid scheduling meetings on Fridays.





From: [] On Behalf Of Tom Lindsay
Sent: 31. juli 2004 19:45
Subject: [10GMMF] Notes from 1st TP2 working group call, 7/30/04



Petar Pepeljugoski; IBM

John Ewen; JDSU

Tom Lindsay, Norm Swenson, Bharath Jagannathan; ClariPhy

Jens Fiedler; Infineon

Mike Fukatsu; OCP

Brent Whitlock; RSoft

Nick Weiner, Ben Wilcox; PhyWorks

Sudeep Bhoja, John Jaeger, Jonathan King; Big Bear

Ryan Latchman; Gennum

Matt Traverso; Opnext

Lars Thon; Aeluros

Pete Hallemeier; Optium

Yi Sun; OFS

Badri Gomatam; Vitesse




Discussions were based on Tom's emails of 7/29 (agenda for call) and 7/25 (project outline), as well as lindsay_01_0704. The agenda from the 7/29 email was approved.


Purpose and objectives

  • A succinct statement is required. Action to Tom to draft. Cost is a motivation. Per 7/25 email, purpose is to gather and study cost, test methods, and penalty information and make a proposal to the LRM task force in September. I expect refinement will continue beyond that time. Any work from this group may be traded against work from the channel modeling group or the new TP3 group.
  • Work and proposal must include test methods. An important goal is that test methods should be simple and practical to keep test cost low.
  • This group's charter does not include launch geometries. That work is being done as part of the channel modeling. This group's work is focused on the time and frequency domain aspects of signals (masks, edge rates, etc.).
  • The main LRM reflector is to be used.

The high-level task list (per 7/29 email) was approved. Task order was discussed. Cost information must be shared early so that experimental and simulation work know where to focus. Test metrics must be proposed early to also support experimental and simulation work.

  • Propose/develop TP2 test metrics - probably required anyway; see slide 14 of lindsay_01_0704 for initial ideas
  • Simulations - penalty and test metric results vs. signal specs/characteristics
  • Experimental work - penalty and test metric results vs. signal specs/characteristics
  • Develop cost models - relative costs vs. signal specs/characteristics
  • Present tradeoff data and recommendations

The scope of study must include anything that both affects cost and TP2 signaling properties. This includes laser drivers, driver to laser coupling and packaging, laser chips, and optical power coupling efficiency (and electrical drive).


Task details need development by the volunteers doing the work, although some thoughts may be available in lindsay_01_0704. Some tasks require inputs from other tasks, such as

  • Experimental work must be guided by where cost benefits may lie.
  • Simulation work must also be guided by where cost benefits may lie but also by the practical range of parameter values determined by limits or availability of actual hardware.
  • Both experimental and simulation work require test metrics/methods to compare their tracking with penalty results.

In general, as folks develop details for progressing their task(s), please determine what information you need from other parts of this group or to share within the same task. This is critical to bound and focus the work.



  • Cost
    • Matt Traverso
    • John Ewen
  • TP2 test methods
    • Tom Lindsay
    • Jens Fiedler
    • Matt Traverso
  • Simulations
    • Tom Lindsay
    • Norm Swenson
    • Jens Fiedler
    • Intel (not on the call, but I know they are working on this)
  • Experiments
    • John Ewen
    • Badri Gomatam
    • Intel (not on the call, but I know they are working on this)

More volunteers are requested! Please let me know what you are interested in supporting. There were several folks that indicated interested in this work that were not able to make this call.



  • Since we are trying to support the September interim, we need to know its dates as soon as possible.
  • Calls will be held ~weekly.
  • Next call will be Friday 8/6 at 9 AM PDT.  Same numbers.



Tom Lindsay
ClariPhy Communications
phone: (425) 775-7013
cell: (206) 790-3240