02078r0P802.15_TG3-Minutes Dallas Interim March, 1994 DOC: IEEE P802.11-94/xxx February 2002 IEEE P802.15.3 doc:. 02/078r0 IEEE 802.15 Wireless Personal Area Networks ( Project IEEE 802.15 Working Group for WPANs( Title IEEE 802.15 TG3 Minutes from Dallas to Schaumburg Date Submitted [29 January 2002] Sources Jim Allen Appairent Technologies, Inc. 150 Lucius Gordon Dr.

IEEE Draft P802.17/D0.3 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 Residential Ethernet (RE) (a working paper) The following paper represents an initial attempt to codify the content of multiple IEEE 802.3 Residential Ethernet (RE) Study Group slide presenta- tions.

IEEE Draft P802.17/D0.3 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 Residential Ethernet (RE) (a working paper) The following paper represents an initial attempt to codify the content of multiple IEEE 802.3 Residential Ethernet (RE) Study Group slide presenta- tions.

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

Inouye, The IEEE RAC has assigned an Individual Address to the Bluetooth SIG for use as a Bluetooth-specific extension to the 1394 Trade Association's "AV/C Digital Interface Command set General Specification."

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

Turn 1385-1402 black after following changes Delete Footnotes: 7 & 8 Change 1385-1387: buf_attributes: the purpose of buffer-type attributes is to provide values that on a per pad basis, override corresponding values expected to be found in a buffer type description library. 1387-1394: Delete : Buffer-type with device specifications. 1407-1408: Turn black. 1409-1410: Change to: 39.1).

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.

For example, see IEEE Std 1394-1995.

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

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

[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?”  

IEEE 1596-1992 SCI IEEE 1394-1994 Written&posted pseudo-draft Special interests Deterministic scheduling in the home Simple/sufficient QOS on the first mile Lessons of the past… Flow control mandates 2-out-of-3 Low latency transmissions Fair bandwidth allocation High bandwidth utilization Feedback control systems Low latency signaling Control passes asynchronous packets Separate synchronous queues Other observations Local control => global perversions Fairness is inherently “approximate” Strange beating sequences DO OCCUR data[n]fair asynchronous data[n]unfair asynchronous Arbitration classes • Low latency & guaranteed BW • Bounded latency & guaranteed BW • Fairness on residual bandwidth (unused as well as nonprovisioned) data[n]synchronous Fs Fu 1-(Fa’-Fu’) (Fs+Fu)<1 Fa’ asyncFifo filling • Throttle asynchronous insertions synchFifo P5 asyncSend asyncPolice fifoPoliceasyncFifo syncPolice Fairness policing • Consumed asyncSend => inform others (asyncSend is higher level queue) synchFifo PF asyncSend asyncPolice fifoPoliceasyncFifo syncPolice Fairness assistance • Fair assistance => asyncSend filling • Throttle nonprovisioned insertions synchFifo PF nodeA Token based fairness • Receive the grant wavefront • Hold the wavefront while sending • Fairness weighting is higher-level issue nodeB nodeC grant-B grant-A nodeA Opposing arbitration • Data packets flow in one direction • Arbitration control flows in the other* nodeB nodeC packet control Arbitration notes Dual levels Synchronous, pre-emptive low latency Asynchronous, negotiated and residual Jumbo frames Affect asynchronous latencies NO IMPACT on synchronous latency Idle symbols Lowest latency for control No catch-22 (arbitrate for arbitration control) For the future Heterogeneous bandwidths Incremental growth useful (inevitable?)

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

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

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

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

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

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.

I could imagine one that is used to tag all IEC 61883-type packets (the normal tagging and formatting system for consumer-electronics type streams in 1394). -- --------------------------------------------------------------- Michael D.

IEEE 1394.

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.