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.

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

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.

RBR includes features appropriate for the > low-latency > backplane environment: destination-based flow control, low-power > short-haul > PHY, backplane-to-backplane links, transport of IEEE-1394 > isochronous > data, > and support of IEEE-1596 memory-update operations." > > Background material includes: > http://grouper.ieee.org/groups/msc/MSC200404/RbrSlides2004Mar31.pdf > http://grouper.ieee.org/groups/msc/MSC200401/RprBackplane.pdf > > Items on the agenda include: > 1) Formulation of email reflector lists. > 2) Review of approved PAR. > 3) Sollicitation of technical inputs and strawman proposals. > 4) Discussion of related activities. > 5) Future meeting schedule. > 6) Other items as requested. > > In particular, this is an opportunity to suggest directions, revisions > of the slides and objectives, and/or strawman proposals.

Regards, Edward ---------- Forwarded message --------- Hello Edward,   You allocations: TransactionID Type Status User Group Resource Ref Doc Ref Subclause Ref Location Name Req Value Description Allocated Value 1390 Allocate Pending Edward Au TGbe StatusCodes IEEE Std 802.11-2020 9.4.1.9 Table 9-50 DENIED_LINK_ON_WHICH_THE_(RE)ASSOCIATION FRAME_IS_ TRANSMITTED_NOT_ACCEPTED Link not accepted because the link on which the (Re)Association Request frame is transmitted is not accepted. 139 1391 Allocate Pending Edward Au TGbe StatusCodes IEEE Std 802.11-2020 9.4.1.9 Table 9-50 EPCS_DENIED_VERIFICATION_FAILURE EPCS priority access is temporarily denied because the receiving AP MLD is unable to verify that the non-AP MLD is authorized for an unspecified reason. 140 1392 Allocate Pending Edward Au TGbe StatusCodes IEEE Std 802.11-2020 9.4.1.9 Table 9-50 DENIED_OPERATION_PARAMETER_UPDATE Operation parameter update denied because the requested operation parameters or capabilities are not acceptable. 141 1393 Allocate Pending Edward Au TGbe Element ID Extension 1 IEEE Std 802.11-2020 9.4.2.1 Table 9-92 MLO Link Information 133 1394 Allocate Pending Edward Au TGbe Element ID Extension 1 IEEE Std 802.11-2020 9.4.2.1 Table 9-92 AID Bitmap 134 1395 Allocate Pending Edward Au TGbe Element ID Extension 1 IEEE Std 802.11-2020 9.4.2.1 Table 9-92 Bandwidth Indication 135   So you don’t need to ask twice 😊   -Robert     From: Edward Au < edward.ks.au@xxxxxxxxx > Sent: Thursday, January 26, 2023 8:22 AM To: Stacey, Robert < robert.stacey@xxxxxxxxx > Subject: 11be ANA request   Dear Robert,   I would like to request allocation of the following 6 items for TGbe:   Type of Request Resource Name Item Name Item Description Requested Value (if any) Requested by Task Group Requested by Name Allocate StatusCodes DENIED_LINK_ON_WHICH_THE_(RE)ASSOCIATION FRAME_IS_ TRANSMITTED_NOT_ACCEPTED Link not accepted because the link on which the (Re)Association Request frame is transmitted is not accepted.  

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

- Speeds - Connectivity Study Item 3: Investigating existing mechanismsInvestigating existing mechanisms - 802.3 Clause 64, Clause 65 - 1394 isochronous - Gibson MaGIC Study Item 4: Interactions with 802.1Interactions with 802.1 - Ex: 802.1d, 802.1p, 802.1q, etc… IEEE 802.3 CFI Portland July 2004 7July 2004 Call for InterestCall for Interest Request 802.3 at the Closing Plenary to form a Residential Ethernet Study Group to develop a standards project proposal (PAR and 5 Criteria) for Residential Ethernet.

. – Identified points of agreement on autonegotiation – Agreed to specify 10 GbE serial, GbE serial and 10 GbE four lane (change of Five Criteria approved to be consistent with these interface objectives) – Adopted definition of “improved FR4” – Signaling ad-hoc to be formed 16 July 2004 IEEE 802.3 Report 7 802.3aq 10GBASE-LRM • Extends Ethernet capabilities at 10 Gb/s – Operation over installed multimode fiber – New physical layer to run under 802.3ae specified XGMII • Working toward first draft 16 July 2004 IEEE 802.3 Report 8 Congestion Management SG • Adopted narrowed problem statement: 802.3 MAC client needs to be able to limit traffic being received from its peer to avoid congestion due to oversubscription • Agreed on a partial set of objectives for a possible project • Study Group extended through November plenary meeting 16 July 2004 IEEE 802.3 Report 9 Frame Expansion SG • Address request from 802.1 to expand 802.3 maximum frame size to allow addition of protocol header and trailer fields – IEEE 802.3 Ad Hoc/CFI held – Also subject of joint technical plenary with 802.1 – Half duplex repeater limits and other PHY layer limitation were discussed, additional study required for PHY layers that support retiming in the data path • Study Group approved by 802.3 and Executive Committee 16 July 2004 IEEE 802.3 Report 10 Residential Ethernet SG • Successful call for interest held on Residential Ethernet – Focus is requirements of consumer electronics within the home – Issues include latency, latency jitter, and timing synchronization for consumer media distribution/playback • Study Group approved by 802.3 and Executive Committee 16 July 2004 IEEE 802.3 Report 11 Other Activities • IEEE 1394 tutorial sponsored • New maintenance requests approved, interpretations response approved • Autumn interim meeting – Details are TBD – Target week: 27 September 2004 – Target location: North America

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.

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.

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

Some overall news: * The IEEE SA Standards board approved the 1394 revision PAR.

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.

Firewire UTP – IEEE 1394 over UTP.

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.