Here is a list of some of my relevant qualifications: Performance modeling activities: Founded and run AmerNet which specializes in architecture analysis and performance modeling for networking and communication products and have many clients in various committees of the IEEE 802 and elsewhere Recognized expert in the field of network/communication performance analysis and modeling and author of many publications, articles and papers on various aspects of LAN/Networking performance analysis Worked in the LAN performance analysis group at IBM since 1988 Activities in RPR: Have been participating in the RPRSG since the first meeting in May 2000 Volunteered to chair the adhoc committee on performance modeling for the RPRSG Successfully led the performance adhoc committee to reach agreement on a lot of open issues related to the performance modeling efforts Drafted and posted a draft charter for the RPR performance committee as well as the list of its accomplishments  Activities in the IEEE 802 standards and other standard bodies: An active participant in the IEEE 802 since 1992 Have been a voting member of 802.3, 802.5, 802.15 and 802.17 Represented IBM's position in various IEEE 802 committees Provided a tutorial on QoS and priorities in Token Ring LANs based on extensive simulations and performance analysis The main IEEE 802 representative for Rockwell Semiconductor Systems Chaired the QoS study group from July 1998 till March 1999 An active participant in the IETF, NP Forum and IEEE 1394 Educational background: MS degree in Electrical Engineering (Caltech - 1986) Professional background: Specialized in the area of LAN performance analysis for my entire career Responsible for the performance analysis of many system architectures and networking chips at IBM Responsible for joint research work between IBM and NC-State University in the area of multimedia performance in LAN environments Founded AmerNet in May 1998 which specializes in performance modeling and architectural analysis In response to a request from our chair to clarify why I am active in IEEE 802.17:   AmerNet provides services related to IEEE activities.

Most noteable are IEEE 754 Floating Point > and IEEE 1394, and other microprocessor standards.

From IEEE Std 1394 Serial Bus experiences, as well as the telecom industry as a whole, the value of synchronous transfers is greatly increased if time-of-day clocks can also be synchronized.

Probably useful to the customers, although accurate network timing and good QOS are likely to be perceived as threats by IEEE 1394 zealots.

This is one place where the SG received conflicting >> information, so the more restrictive number was used ... since existence >> proofs (IEEE 1588 and IEEE 1394) shows that this kind of >> synchronization can >> easily be done with very low complexity. >> >> The numbers I quote here are open for discussion.

Most noteable are IEEE 754 Floating Point >> > and IEEE 1394, and other microprocessor standards.

. > > From IEEE Std 1394 Serial Bus experiences, as well as > the telecom industry as a whole, the value of synchronous > transfers is greatly increased if time-of-day clocks > can also be synchronized. > > DVJ > > > David V.

. 802.3af, 802.3at TIA-862 building automation and security devices Remote cameras IP telephone Multimedia devices supported by IEEE Std 1394-2008.

IEEE 1394 and 1588. • The reliability of Ethernet components and systems can be extrapolated in the target environments with a high degree of confidence. 15 November 2005 IEEE 802.1./802.3 Residential Ethernet 6 Economic Feasibility Cost factors known, reliable data Reasonable cost for performance expected Total installation costs considered • The cost factors for Ethernet components and systems are well known.

I have updated the GEN Comment Spreadsheet: https://mentor.ieee.org/802.11/dcn/12/11-12-1394-01-000m-gen-adhoc-preballot-comment-collection-resolutions.xlsx   The Tab for Vinko's set of comments is now labeled GEN-1297 Dorothy will have a motion prepared for this morning that accepts the resolution for GEN Motion A (Comments from Sept), and GEN-1297 (Vinko's Comments).  

From IEEE Std 1394 Serial Bus experiences, as well as the telecom industry as a whole, the value of synchronous transfers is greatly increased if time-of-day clocks can also be synchronized.

I’ve uploaded the received comments to mentor:  https://mentor.ieee.org/802.11/dcn/23/11-23-1394-00-00bf-lb276-comments-and-approved-resolutions.xlsx A few action items: PoCs : Please review the comments that I have tentatively assigned to your area, and let me know if you any changes are needed.

I’ve uploaded the received comments to mentor:  https://mentor.ieee.org/802.11/dcn/23/11-23-1394-00-00bf-lb276-comments-and-approved-resolutions.xlsx A few action items: PoCs : Please review the comments that I have tentatively assigned to your area, and let me know if you any changes are needed.

IEEE 1394. • The reliability of Ethernet components and systems can be extrapolated in the target environments with a high degree of confidence.

(ADSL2+, 1394, …) • Any other outreach (companies, countries) of importance to inform or engage?

>Although I have chaired four different IEEE WGs, and two SGs (1196 Nubus 2, >1394, 1394b, and 1394c), those were all MSC-sponsored, and I was certainly >inexperienced with 802 procedures, much less 802.3 procedures.

From IEEE Std 1394 Serial Bus experiences, as well as the telecom industry as a whole, the value of synchronous transfers is greatly increased if time-of-day clocks can also be synchronized.

From IEEE Std 1394 Serial Bus experiences, as well as the telecom industry as a whole, the value of synchronous transfers is greatly increased if time-of-day clocks can also be synchronized.

. > > From IEEE Std 1394 Serial Bus experiences, as well as > the telecom industry as a whole, the value of synchronous > transfers is greatly increased if time-of-day clocks > can also be synchronized. > > DVJ > > > David V.

Most noteable are IEEE 754 Floating Point >> > and IEEE 1394, and other microprocessor standards.

.: IEEE 802.11-98/217 Submission System Architecture Overview P r i n t e r C a m e r a G a m e P a d U S B Lamp Smoke Detector Thermostat Security System Power Line 78 Stereo Camcorder VCR TV 1394 Phone Cable Grandma’s Brownies 3 cups flour 1 cup grated chocolate 1 cup sugar 1 stick butter Control Point May 1998 Stuart K.

From IEEE Std 1394 Serial Bus experiences, as well as the telecom industry as a whole, the value of synchronous transfers is greatly increased if time-of-day clocks can also be synchronized.

The following presentations were made: #1 Geoff Thompson, Nortel – Spyder-LAN (see Spider-LAN.ppt) Discussion: 1394 compatibility 100Mbps compatibility Can spyder mode be originated and best-effort data be later sent from the same DTE Can spider elements be cascaded?

Firewire UTP – IEEE 1394 over UTP.

Cell: +1 (819) 609-1394 E-Mail: francois.menard@xxxxxxxxxxx Follow-Ups : Re: [802.3_NGEPON] ONU ASIC and wavelength plans From: Glen Kramer Re: [802.3_NGEPON] ONU ASIC and wavelength plans From: Duane Remein Re: [802.3_NGEPON] ONU ASIC and wavelength plans From: Marek Hajduczenia References : Re: [802.3_NGEPON] ONU ASIC and wavelength plans From: Shawn Esser Re: [802.3_NGEPON] ONU ASIC and wavelength plans From: Marek Hajduczenia Re: [802.3_NGEPON] ONU ASIC and wavelength plans From: Barry Colella Re: [802.3_NGEPON] ONU ASIC and wavelength plans From: Marek Hajduczenia Re: [802.3_NGEPON] ONU ASIC and wavelength plans From: Barry Colella Prev by Date: Re: [802.3_NGEPON] ONU ASIC and wavelength plans Next by Date: Re: [802.3_NGEPON] ONU ASIC and wavelength plans Previous by thread: Re: [802.3_NGEPON] ONU ASIC and wavelength plans Next by thread: Re: [802.3_NGEPON] ONU ASIC and wavelength plans Index(es): Date Thread