John S. wants to make sure that we provide what is necessary to support requirements for 1394.

All rights reserved 51 This is an unapproved IEEE Standards Draft, subject to change 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 6.6.2 61883-2 timing and synchronization 61883-2 formatted frames shall follow the same timing and synchronization rules as defined in IEC 61883-2 section 6, but using IEEE 802.1AS time in the avbtp_timestamp frame field instead of IEEE 1394 based cycle time in the SYT field.

. >> > >> >As an MSC representative, I would have provided >> >such a follow-up on the addresses used within >> >MSC sponsored projects (754, 1394, etc.), as >> >a duty to my position. >> > >> >I prefer to see the evidence before jumping into >> >denial or conclusions, since (through out my career) >> >I have seen suboptimal decisions made when this >> >ordering is reversed. >> > >> > >> >If you feel strongly about this, >> >Yes, I feel strongly about conservation of OUI space. >> >I naively thoutht that to be the premise of our charter. >> >Times change, I suppose... >> > >> >Cheers, >> >DVJ >> > >> > >> -----Original Message----- >> > >> From: Geoff Thompson [ mailto:gthompso@nortel.com ] >> > >> Sent: Wednesday, August 08, 2007 3:07 PM >> > >> To: Floyd Backes >> > >> Cc: dvj@alum.mit.edu; Geoff Thompson; a.n.weaver@IEEE.ORG; >> > >> stds-rac@IEEE.ORG >> > >> Subject: RE: Request for multiple OUI assignments >> > >> >> > >> >> > >> At 11:48 AM 8/8/2007 , Floyd Backes wrote: >> > >> >If you feel strongly about this, you could review the >> latest version of >> > >> >802.1 MAC Bridging, figure out how it can be made to work >> using the same >> > >> >MAC address on every port, get a PAR to update the >> standard, and then >> > >> >slug it out with Mick over the ensuing 2 years to produce a revised >> > >> >standard.

Otherwise, large companies (with many divisions) have to purchase several OUIs (as happended in 1394), because divergent interests conflict with the first user's definitions.

. > >> > > >> >As an MSC representative, I would have provided > >> >such a follow-up on the addresses used within > >> >MSC sponsored projects (754, 1394, etc.), as > >> >a duty to my position. > >> > > >> >I prefer to see the evidence before jumping into > >> >denial or conclusions, since (through out my career) > >> >I have seen suboptimal decisions made when this > >> >ordering is reversed. > >> > > >> > >> >If you feel strongly about this, > >> >Yes, I feel strongly about conservation of OUI space. > >> >I naively thoutht that to be the premise of our charter. > >> >Times change, I suppose... > >> > > >> >Cheers, > >> >DVJ > >> > > >> > >> -----Original Message----- > >> > >> From: Geoff Thompson [ mailto:gthompso@nortel.com ] > >> > >> Sent: Wednesday, August 08, 2007 3:07 PM > >> > >> To: Floyd Backes > >> > >> Cc: dvj@alum.mit.edu; Geoff Thompson; a.n.weaver@IEEE.ORG; > >> > >> stds-rac@IEEE.ORG > >> > >> Subject: RE: Request for multiple OUI assignments > >> > >> > >> > >> > >> > >> At 11:48 AM 8/8/2007 , Floyd Backes wrote: > >> > >> >If you feel strongly about this, you could review the > >> latest version of > >> > >> >802.1 MAC Bridging, figure out how it can be made to work > >> using the same > >> > >> >MAC address on every port, get a PAR to update the > >> standard, and then > >> > >> >slug it out with Mick over the ensuing 2 years to produce a revised > >> > >> >standard.

. > >As an MSC representative, I would have provided >such a follow-up on the addresses used within >MSC sponsored projects (754, 1394, etc.), as >a duty to my position. > >I prefer to see the evidence before jumping into >denial or conclusions, since (through out my career) >I have seen suboptimal decisions made when this >ordering is reversed. > > >> >If you feel strongly about this, >Yes, I feel strongly about conservation of OUI space.

While most of the current implementations are MAC addresses, and some Firewire (1394) addresses, it is expanding to all elements within the addressable environment with EUI requirements for disk drives to clusters to PCIExpress devices on the mother board and beyond.

. • Technologies such as IEEE 1394, Bluetooth and USB exist today but each has their own encapsulation, protocols, timing control, etc. such that building interworking functions is difficult.

. > >As an MSC representative, I would have provided >such a follow-up on the addresses used within >MSC sponsored projects (754, 1394, etc.), as >a duty to my position. > >I prefer to see the evidence before jumping into >denial or conclusions, since (through out my career) >I have seen suboptimal decisions made when this >ordering is reversed. > > >> >If you feel strongly about this, >Yes, I feel strongly about conservation of OUI space.

. >> >>As an MSC representative, I would have provided >>such a follow-up on the addresses used within >>MSC sponsored projects (754, 1394, etc.), as >>a duty to my position. >> >>I prefer to see the evidence before jumping into >>denial or conclusions, since (through out my career) >>I have seen suboptimal decisions made when this >>ordering is reversed. >> >> >>>>>If you feel strongly about this, >> >>Yes, I feel strongly about conservation of OUI space.

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. -           PoCs : Once you’ve reviewed the comments assigned to your area, please send a request for volunteers to your TTT. 

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

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.

. > > 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.

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.

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

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.

Firewire UTP – IEEE 1394 over UTP.

Best Regards,   Adrian P STEPHENS Tel: +44 (1793) 404 825 Tel: +44 (7920) 084 900 Tel: +1 (408) 239 7485   ---------------------------------------------- Intel Corporation (UK) Limited Registered No. 1134945 (England) Registered Office: Pipers Way, Swindon SN3 1RJ VAT No: 860 2173 47   From: ***** IEEE stds-802-11-tgm List ***** [mailto:STDS-802-11-TGM@xxxxxxxx] On Behalf Of Jon Rosdahl Sent: Tuesday, December 11, 2012 2:25 PM To: STDS-802-11-TGM@xxxxxxxxxxxxxxxxx Subject: [STDS-802-11-TGM] [Gen AdHoc] Update to comment spreadsheet through Dec 7th Telecon   --- This message came from the IEEE 802.11 Task Group M Technical Reflector --- I have uploaded doc 11-12/1394r3 which contains the updated status for the Gen AdHoc Comments through the Dec 7th Telecon. https://mentor.ieee.org/802.11/dcn/12/11-12-1394-03-000m-gen-adhoc-preballot-comment-collection-resolutions.xlsx   Note that there are still a lot of comments that could use some assistance in resolving.

Best Regards,   Adrian P STEPHENS Tel: +44 (1793) 404 825 Tel: +44 (7920) 084 900 Tel: +1 (408) 239 7485   ---------------------------------------------- Intel Corporation (UK) Limited Registered No. 1134945 (England) Registered Office: Pipers Way, Swindon SN3 1RJ VAT No: 860 2173 47   From: ***** IEEE stds-802-11-tgm List ***** [mailto:STDS-802-11-TGM@xxxxxxxx] On Behalf Of Jon Rosdahl Sent: Tuesday, December 11, 2012 2:25 PM To: STDS-802-11-TGM@xxxxxxxxxxxxxxxxx Subject: [STDS-802-11-TGM] [Gen AdHoc] Update to comment spreadsheet through Dec 7th Telecon   --- This message came from the IEEE 802.11 Task Group M Technical Reflector --- I have uploaded doc 11-12/1394r3 which contains the updated status for the Gen AdHoc Comments through the Dec 7th Telecon. https://mentor.ieee.org/802.11/dcn/12/11-12-1394-03-000m-gen-adhoc-preballot-comment-collection-resolutions.xlsx   Note that there are still a lot of comments that could use some assistance in resolving.

References: https://mentor.ieee.org/802.11/dcn/12/11-12-1189-09-000m-mac-adhoc-pre-ballot-comment-collection-resolutions.xls , https://mentor.ieee.org/802.11/dcn/12/11-12-1082-12-0000-revmc-pre-ballot-comments.xls and https://mentor.ieee.org/802.11/dcn/12/11-12-1394-03-000m-gen-adhoc-preballot-comment-collection-resolutions.xlsx .

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.