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

[STDS-802-11-TGBF] Updated group documents Thread Links Date Links Thread Prev Thread Next Thread Index Date Prev Date Next Date Index [STDS-802-11-TGBF] Updated group documents To : STDS-802-11-TGBF@xxxxxxxxxxxxxxxxx Subject : [STDS-802-11-TGBF] Updated group documents From : Claudio da Silva < 00001ce441172b4c-dmarc-request@xxxxxxxxxxxxxxxxx > Date : Fri, 3 Nov 2023 17:59:45 +0000 All,   I have uploaded updated versions of our comment resolution documents: LB276 comments and approved resolutions ( https://mentor.ieee.org/802.11/dcn/23/11-23-1394-09-00bf-lb276-comments-and-approved-resolutions.xlsx ) LB276 SPs and motions ( https://mentor.ieee.org/802.11/dcn/23/11-23-1494-05-00bf-lb276-sps-and-motions.xlsx ) Please review and let me know if you find problems.

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.

. > This would be similar to the case of > IEEE 1394 vendor dependent command where the Company_id of the RAC is > utilized.

[STDS-802-11-TGM] [Gen AdHoc] Update to comment spreadsheet through Dec Thread Links Date Links Thread Prev Thread Next Thread Index Date Prev Date Next Date Index [STDS-802-11-TGM] [Gen AdHoc] Update to comment spreadsheet through Dec 7th Telecon To : STDS-802-11-TGM@xxxxxxxxxxxxxxxxx Subject : [STDS-802-11-TGM] [Gen AdHoc] Update to comment spreadsheet through Dec 7th Telecon From : Jon Rosdahl < jrosdahl@xxxxxxxx > Date : Tue, 11 Dec 2012 07:25:09 -0700 --- 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.

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.

Examples of such applications include LAN devices, wireless access points, ANSI/TIA-862-B building automation and security devices like remote cameras, IP telephone and multimedia devices, all of which may be supported by standards such as IEEE Std 802.3™-2012 Clause 33 DTE Power via MDI or IEEE Std. 1394-2008.

. >> 3/ FireWire is not Ethernet >> >> Items 1 and 2 have been addressed by enhancements to the IEEE-1394 >> specification (FireWore over CAT5 and bridging).

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

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.

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.

. • Bridging to non-802 nets – 1394/USB/MoCA Specifications must be met to use Trademark 720 July 2005 ResE Study Group Thank you!

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.

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

[STDS-802-11-CAC] 答复: [STDS-802-11-CAC] Motions, timelines and web pages Thread Links Date Links Thread Prev Thread Next Thread Index Date Prev Date Next Date Index [STDS-802-11-CAC] 答复: [STDS-802-11-CAC] Motions, timelines and web pages To : STDS-802-11-CAC@xxxxxxxxxxxxxxxxx Subject : [STDS-802-11-CAC] 答复: [STDS-802-11-CAC] Motions, timelines and web pages From : "Hanxiao (Tony, WT Lab)" < 0000177ab8f731c4-dmarc-request@xxxxxxxxxxxxxxxxx > Date : Fri, 17 Nov 2023 00:47:48 +0000 --- This message came from the IEEE 802.11 Chairs' Advisory Committee Reflector --- Hi Stephen,          TGbf would like to request one more motion (Now totally 3 motions):     Having approved comment resolutions for all of the comments received from LB276 on P802.11bf D2.0 as contained in document 11-23/1394r12, https://mentor.ieee.org/802.11/dcn/23/11-23-1394-12-00bf-lb276-comments-and-approved-resolutions.xlsx Instruct the editor to prepare P802.11bf D3.0 incorporating these resolutions and, Approve a 30 day Working Group Recirculation Ballot asking the question “Should P802.11bf D3.0 be forwarded to SA Ballot?”  

. > Examples: > IEEE Std 802(R)-2002 or IEEE 802(R)-2002 > IEEE 802(R) Working Group > IEEE Std 802.11b(TM)-1999 > IEEE 1394(TM) > IEEE P1232(TM) >If you have any questions, CONTACT Claudio Stanziola - IEEE Standards >Activities - telephone +1 732 562 3804; " MailTo:c.stanziola@ieee.org" ;.

Will the RAC make the request that IEEE Standard 1394 be modified to use EUI-48?

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.

For example, see IEEE Std 1394-1995.

The "gating" approach is _a_ solution that can is well tested on IEEE 1394 and can easily be shown to suffice.

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

. > > Examples: > > IEEE Std 802(R)-2002 or IEEE 802(R)-2002 > > IEEE 802(R) Working Group > > IEEE Std 802.11b(TM)-1999 > > IEEE 1394(TM) > > IEEE P1232(TM) > >If you have any questions, CONTACT Claudio Stanziola - IEEE Standards > >Activities - telephone +1 732 562 3804; " MailTo:c.stanziola@ieee.org" ;.

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.

Morning Afternoon Evening Daily IEEE 802 Registration Desk: Plaza Foyer Sun 5-8 pm, Mon-Thu: 7:30 am-5 pm IEEE 802 Office: Broadway 1 Sun 5-8 pm, Mon-Fri: 7:30 am-5 pm Sun 802 Architecture Group 2-5 pm Parlor C Mon IEEE 802 EC Meeting 8-10:30 am Pavilion IEEE 802 Opening Plenary 11 - 12 am Grand Ballroom  IEEE 802.16 Opening Plenary 1:00-3:30 pm  TGe 4-9 pm  IEEE 802 Tutorial #1 (802.1): Connectivity Fault Mgmt 6:30-8:00 pm Queen Marie - Embassy Suites Education, Mentoring & Support : PARs, Balloting, and Draft Approval 8:00-9:30 pm Grand Ballroom II Tue TGe 8am-10 pm IEEE 802 Tutorial #3 (802.19): Coexistence in Unlicensed Bands: Challenges and Solutions 6:30-8:00 pm Grand Ballroom II IEEE 802 Tutorial #4 (802.3): 1394 and 802 8:00-9:30 pm Grand Ballroom II Education, Mentoring & Support : Advanced Framemaker Training   8:00-9:30 pm Forum Suite TGC 8am-5 pm 802.16 Ad Hoc Committee: Licensed-Exempt Coexistence 8-10 pm Wed TGe 8 am-6 pm IEEE 802 Social Reception Crystall Ballroom, 6:30-9 pm 802.16 NetMan Study Group 8am-6 pm Thu TGe 8 am-5 pm IEEE 802.16 Closing Plenary 7-10 pm   Maintenance of IEEE Std 802.26-2004 8am-12 am TGC or Maintenance 1-5 pm Fri IEEE 802 SEC Meeting 1-6 pm Salon I-III  Roger Marks ( r.b.marks@ieee.org ) Chair, IEEE 802.16 Working Group on Broadband Wireless Access Standards r.b.marks@ieee.org Return to IEEE 802.16 Session #32 Page

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.