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

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.

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

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 "gating" approach is _a_ solution that can is well tested on IEEE 1394 and can easily be shown to suffice.

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.

IEEE 1394.

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?)

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

For instance, a 1394 FCSL cannot correctly process a frame from an 802.2 FCSL.

Zhang gave a presentation titled ‘Wireless 1394 from microwave to millimeter-wave in MMAC’ (04/351r0).

The relevant standards include: CSMA/CD (IEEE 802.3, ISO 8802-3) Token Bus (IEEE 802.4, ISO 8802-4) Token Ring (IEEE 802.5, ISO/IEC 8802-5) IEEE 802.6 (ISO/IEC DIS 8802-6) FDDI (ISO 9314-2) WLAN (IEEE 802.11, ISO/IEC 8802-11) B) The 'company_id' relevant standards include: defined in IEEE Std 1212-1991 Control and Status Register (CSR) Architecture referenced by IEEE Std 896.2-1991 Futurebus+Physical Layers and Profiles IEEE Std 1596-1992 Scalable Coherent Interface IEEE Std 1394-1995 Serial Bus document.

For instance, a 1394 FCSL cannot correctly process a frame from an 802.2 FCSL.

IEEE 802.3 Residential Ethernet email archive IEEE 802.3 Residential Ethernet email archive Date Index (Page 14 of 15) Thread Index Search Tool First Page Prev Page Next Page Last Page Re: [RE] CE applications (was: RE: [RE] Focus of discussions) From : Alexei Beliaev Date: Thu, 2 Sep 2004 13:04:31 -0400 (EDT) Re: [RE] CE applications (was: RE: [RE] Focus of discussions) From : Gross, Kevin Date: Thu, 2 Sep 2004 11:28:43 -0400 (EDT) Re: [RE] Resume (was: Network topology requirements (was: [RE] CE app lications )) From : Gross, Kevin Date: Thu, 2 Sep 2004 10:44:15 -0400 (EDT) Re: [RE] Network topology requirements (was: [RE] CE applications ) From : Richard Brand Date: Thu, 2 Sep 2004 02:19:43 -0400 (EDT) Re: [RE] CE applications (was: RE: [RE] Focus of discussions) From : David V James Date: Wed, 1 Sep 2004 19:18:52 -0400 (EDT) Re: [RE] CE applications (was: RE: [RE] Focus of discussions) From : David V James Date: Wed, 1 Sep 2004 19:06:12 -0400 (EDT) Re: [RE] CE applications (was: RE: [RE] Focus of discussions) From : Henry Sariowan Date: Wed, 1 Sep 2004 18:29:57 -0400 (EDT) Re: [RE] CE applications (was: RE: [RE] Focus of discussions) From : Wadekar, Manoj K Date: Wed, 1 Sep 2004 18:12:07 -0400 (EDT) Re: [RE] Network topology requirements (was: [RE] CE applications ) From : Gross, Kevin Date: Wed, 1 Sep 2004 17:58:23 -0400 (EDT) Re: [RE] Overprovisioning (was Re: [RE] CE applications) From : Gross, Kevin Date: Wed, 1 Sep 2004 16:55:02 -0400 (EDT) Re: [RE] Requirement: Bridging to 1394 From : Gross, Kevin Date: Wed, 1 Sep 2004 16:52:39 -0400 (EDT) [RE] Requirement: Bridging to 1394 From : Michael D.

GND Pair 2 Thomas Müller 4 IEEE RTPGETwisted Quad Fundamentals Typical insertion loss 1 dB/m @ 1 GHz Low crosstalk Bidirektional communication up to 3 GBit/s over 10 m LVDS possible Sdd21 [Pair 1] f [MHz] In se rt io n lo ss [ dB /m ] 0.1 1 10 100 1000 0.001 0.01 0.1 1 10 NEXT [Pair 1 to Pair 2] f [MHz] S dd 21 ( ne ar -e nd ) [d B ] 0.1 1 10 100 1000 -100 -90 -80 -70 -60 -50 -40 -30 -20 -10 0 Orange: Cat 6a Black: Cat 5 Thomas Müller 5 IEEE RTPGE Open interface (connectors are available from different vendors) Interface as described in automotive IEEE 1394 Copper Automotive Standard (Supplement to IDB-1394) Project TS2008001 Designed to meet automotive requirements Electrical (e.g.

Zhang gave a presentation titled ‘Wireless 1394 from microwave to millimeter-wave in MMAC’ (04/351r0).

(see 802.1AS assumptions from AVB document)). • 61883 format over AVBTP will support presentation time using AVBTP timestamp field instead of current 61883 SYT field – 1394/61883 to 1722/61883 gateways will have to take care of all SYT to AVBTP timestamp conversions, synchronization, cross timestamps, etc. – Editor’s note: Need to work out SYT field for SPH = 1 packets as timestamps are on a per source packet basis (MPEG packet) instead of in the CIP header. • AVBTP 61883 presentation time shall be relative to the 802.1AS clock • Adapt 1394 AV/C Function Control Protocol (FCP) for use in 61883 over AVBTP. • Proprietary encapsulations allowed via reserved subtype (7F16) • Allow for other future expansions via different subtypes.

(see 802.1AS assumptions from AVB document)). • 61883 format over AVBTP will support presentation time using AVBTP timestamp field instead of current 61883 SYT field – 1394/61883 to 1722/61883 gateways will have to take care of all SYT to AVBTP timestamp conversions, synchronization, cross timestamps, etc. – Editor’s note: Need to work out SYT field for SPH = 1 packets as timestamps are on a per source packet basis (MPEG packet) instead of in the CIP header. • AVBTP 61883 presentation time shall be relative to the 802.1AS clock • Adapt 1394 AV/C Function Control Protocol (FCP) for use in 61883 over AVBTP. • Proprietary encapsulations allowed via reserved subtype (7F16) • Allow for other future expansions via different subtypes.

(see 802.1AS assumptions from AVB document)). • 61883 format over AVBTP will support presentation time using AVBTP timestamp field instead of current 61883 SYT field – 1394/61883 to 1722/61883 gateways will have to take care of all SYT to AVBTP timestamp conversions, synchronization, cross timestamps, etc. – Editor’s note: Need to work out SYT field for SPH = 1 packets as timestamps are on a per source packet basis (MPEG packet) instead of in the CIP header. • AVBTP 61883 presentation time shall be relative to the 802.1AS clock • Adapt 1394 AV/C Function Control Protocol (FCP) for use in 61883 over AVBTP. • Proprietary encapsulations allowed via reserved subtype (7F16) • Allow for other future expansions via different subtypes.

802.17 Terms And Definitions 802.17 Terms And Definitions TA Document Not AcceptedIEEE802.17-11Jul2001 IF ="Approved" "" "/ SUBJECT \* MERGEFORMAT :5" \* MERGEFORMAT / SUBJECT \* MERGEFORMAT :5 , July 11, 2000 TA Document Not AcceptedIEEE802.17-11Jul2001 IF ="Approved" "" "/ SUBJECT \* MERGEFORMAT :5" \* MERGEFORMAT / SUBJECT \* MERGEFORMAT :5 , July 11, 2000 802.17 Terms And Definitions 1.

(802.1d, RFC-1394, IP, USB, PCI?)

(802.1d, RFC-1394, IP, USB, PCI?)

(802.1d, RFC-1394, IP, USB, PCI?)

(802.1d, RFC-1394, IP, USB, PCI?)

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.