1055 results found. results are sorted by relevance
  276-300
https://grouper.ieee.org/groups/802/15/pub/2004/15-04-0011-00-0000-ieee-802-15-wg-minutes-from-vancouver-jan17.doc
March, 1994 DOC: IEEE P802.11-94/xxx January, 2004 IEEE P802.15-<15-04-0011-00-0000> IEEE P802.15 Wireless Personal Area Networks Project IEEE P802.15 Working Group for Wireless Personal Area Networks (WPANs) Title Date Submitted [16 January, 2004] Source [Pat Kinney] [] [address] Voice: [ ] Fax: [ ] E-mail: [ pat.kinney@ieee.org ] Re: [802.15 Interim Meeting in Vancouver] Abstract [IEEE 802.15 Working Group Minutes] Purpose [Official minutes of the Working Group Session] Notice This document has been prepared to assist the IEEE P802.15.
https://grouper.ieee.org/groups/802/3/re_study/public/200407/cfi_0704_1.pdf
– Several companies have home A/V equipment with Ethernet ports now, more to follow – Digital media is the norm for home and professional A/V • DVD for videos • CD, SACD, DVD-Audio for audio • Digital cable, digital satellite, High Definition TV – Convergence: • It’s not just a buzzword, it’s really happening • Computers are used to play videos and music • “Consumer media servers” with hard drive recorders – Increased penetration residential broad band access IEEE 802.3 CFI Portland July 2004 10July 2004 Home Physical Infrastructure Home Physical Infrastructure • New homes are now being wired with UTP cable • According to the Consumer Electronics Association, 52% of new homes in the U.S. are constructed with structured wiring plants • ISO/IEC has just approved the standard for residential structured wiring plants (SC25/WG3) IEEE 802.3 CFI Portland July 2004 11July 2004 It’s already happeningIt’s already happening Digital Living Network Alliance (DLNA, was DHWG) is already developing higher-level protocols that use Ethernet as the physical layer – Professional audio has used several proprietary solutions for almost a decade • It’s very popular, but the solutions are proprietary (non- standard) – Professional video is looking for similar solutions – Using Ethernet will standardize the interface across computers and A/V equipment IEEE 802.3 CFI Portland July 2004 12July 2004 In SummaryIn Summary – The home networking market has already chosen Ethernet for data • The “home” part of SOHO is growing rapidly each year • There are already products on the market from several manufacturers- --and there are more to come – The home audio/video industry is now deliberating about whether to choose Ethernet – The expansion of Ethernet into audio/video will potentially create a new market segment • Tens of millions of new Ethernet ports per year – With increased broad band penetration and the completion of EFM, the home is the next Ethernet challenge for A/V apps IEEE 802.3 CFI Portland July 2004 13July 2004 A/V Home Entertainment A/V Home Entertainment RequirementsRequirements John Gildred Pioneer Alexei Beliaev Gibson Labs IEEE 802.3 CFI Portland July 2004 14July 2004 A/V Has Time Sensitive ApplicationsA/V Has Time Sensitive Applications • Multi-Room Synchronization – Audio playback synchronized across multiple rooms – Video playback synchronized across multiple rooms and maintaining lip-sync • Network Trickplay – Multiple HDTVs accessing recorded shows on a Digital Video Recorder – Each TV attempts slow/fast playback at same time • Jam Session – Multiple instruments with live effects and mixing – Turn on instruments and immediately begin playing – 500uSec max latency, zero long term jitter • Gibson Guitar experience at 100Mbps IEEE 802.3 CFI Portland July 2004 15July 2004 A/V Application Example Requirements A/V Application Example Requirements Asym. 0<100mSec*RequiredA/V Conferencing N/A<100mSec*RequiredNetwork VideoTrickplay Asym. 0500 usecRequired Jam session (live performance) Asym. 0500 usecRequired Multi-room synchronous audio playback Long term jitter Maximum latency Data/time guaranteeApplication *Round trip including application layer IEEE 802.3 CFI Portland July 2004 16July 2004 Home Network Use Case I:Home Network Use Case I: Different Audio Tracks in Each RoomDifferent Audio Tracks in Each Room Living Room Study Bedroom Dining Room Kitchen Basement Network Attached Storage or Home Media Server Digital Audio Player Digital Audio Player Speakers Speakers Speakers Digital Audio Player IEEE 802.3 CFI Portland July 2004 17July 2004 Home Audio Use Case IHome Audio Use Case I • User stores all his music files on a Network Attached Storage (Media Server) box connected via an Ethernet switch • Each room has a digital audio receiver, connected to Ethernet, which can access and play any song from the Media Server – Digital audio receivers drive local speakers over ordinary speaker wire IEEE 802.3 CFI Portland July 2004 18July 2004 Living Room Study Bedroom Dining Room Kitchen Basement Network Attached Storage Or Home Media Server Digital Audio Player Digital Audio Player Speakers Speakers Speakers Digital Audio Player Same Track in Multiple RoomsSame Track in Multiple Rooms Home Network Use Case II:Home Network Use Case II: IEEE 802.3 CFI Portland July 2004 19July 2004 Home Audio Use Case IIHome Audio Use Case II • Sometimes, the user wants one digital audio receiver to be the “master” and control what songs are played in other rooms through “slave” receivers – A single song in the whole house – A single song in selected rooms; e.g. living room, dining room, and study, but not bedroom • Simultaneous audio playing in multiple rooms requires synchronization and phase control of audio within the limits of human hearing to prevent “reverberation” throughout the house IEEE 802.3 CFI Portland July 2004 20July 2004 Time Sensitive RequirementsTime Sensitive Requirements • Precise End-Point Synchronization – Data/time synchronization must be sufficiently precise at little or no cost – Ethernet today does not provide data/time synchronization • Bounded Jitter and Latency – Bounded jitter and latency per A/V application is required • Bandwidth Allocation Guarantee – Guaranteed protection from interfering streams is required • Plus All the Existing Benefits of Ethernet – e.g. minimum packet loss IEEE 802.3 CFI Portland July 2004 21July 2004 Next Generation AV ConnectorNext Generation AV Connector Plug and Play IEEE 802.3 CFI Portland July 2004 22July 2004 Next Generation AV ConnectorNext Generation AV Connector Clean and Simple IEEE 802.3 CFI Portland July 2004 23July 2004 The Next Evolutionary StepThe Next Evolutionary Step (Missing Link with (Missing Link with PoEPoE Option)Option) 802.11e Ethernet 802.11e 1394 1394 Room #1 Room #2 Ethernet IEEE 802.3 CFI Portland July 2004 24July 2004 Ethernet is EverywhereEthernet is Everywhere Ubiquitous, except in the homeUbiquitous, except in the home • Fast • Robust • Very familiar • Affordable right now • Very wide product selection • Growing momentum in CE industry IEEE 802.3 CFI Portland July 2004 25July 2004 Next Generation AV ConnectorNext Generation AV Connector Universal Linkage IEEE 802.3 CFI Portland July 2004 26July 2004 Consumer Electronics is Consumer Electronics is Ready for EthernetReady for Ethernet IEEE 802.3 CFI Portland July 2004 27July 2004 Home Network Potential MarketHome Network Potential Market Seyoun Lim Samsung proyoun.lim@samsung.com IEEE 802.3 CFI Portland July 2004 28July 2004 The home network is at the heart of The home network is at the heart of the digital homethe digital home • Enabling home entertainment networks is key to opening up several large potential markets.
https://grouper.ieee.org/groups/802/15/pub/802.15%20Archives/802.15%20Archive%20pre-802WWW/2002/Mar02/02078r1P802-15_TG3-Minutes-Dallas-to_Schaumburg.doc
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.
https://grouper.ieee.org/groups/802/15/pub/04/15-04-0011-00-0000-ieee-802-15-wg-minutes-from-vancouver-jan17.doc
March, 1994 DOC: IEEE P802.11-94/xxx January, 2004 IEEE P802.15-<15-04-0011-00-0000> IEEE P802.15 Wireless Personal Area Networks Project IEEE P802.15 Working Group for Wireless Personal Area Networks (WPANs) Title Date Submitted [16 January, 2004] Source [Pat Kinney] [] [address] Voice: [ ] Fax: [ ] E-mail: [ pat.kinney@ieee.org ] Re: [802.15 Interim Meeting in Vancouver] Abstract [IEEE 802.15 Working Group Minutes] Purpose [Official minutes of the Working Group Session] Notice This document has been prepared to assist the IEEE P802.15.
https://grouper.ieee.org/rac/private/email/msg00025.html
Will the RAC make the request that IEEE Standard 1394 be modified to use EUI-48?
https://grouper.ieee.org/rac/private/email/msg00009.html
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."
https://grouper.ieee.org/rac/private/email/msg00065.html
. > This would be similar to the case of > IEEE 1394 vendor dependent command where the Company_id of the RAC is > utilized.
https://grouper.ieee.org/groups/1450/dot4/meeting_minutes/mtg2016_05_24.txt
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).
https://grouper.ieee.org/groups/802/11/email/stds-802-11-tgbf/msg02200.html
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.
https://grouper.ieee.org/rac/private/email/msg01180.html
For example, see IEEE Std 1394-1995.
https://grouper.ieee.org/rac/private/email/msg01481.html
. > >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.
https://grouper.ieee.org/rac/private/email/msg01480.html
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.
https://grouper.ieee.org/groups/802/11/email/stds-802-11-tgbf/msg02373.html
[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.
https://grouper.ieee.org/groups/802/11/email/stds-802-11-cac/msg05433.html
[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?”  
https://grouper.ieee.org/groups/802/17/documents/presentations/mar2001/dvj_rpr_03.pdf
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?)
https://grouper.ieee.org/groups/802/16/meetings/mtg32/schedule.html
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
https://grouper.ieee.org/groups/802/3/re_study/email/msg00410.html
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.
https://grouper.ieee.org/groups/802/3/re_study/email/msg00413.html
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.
https://grouper.ieee.org/groups/802/3/re_study/public/200507/johasteener_2_050720.pdf
. • Bridging to non-802 nets – 1394/USB/MoCA Specifications must be met to use Trademark 720 July 2005 ResE Study Group Thank you!
https://grouper.ieee.org/groups/802/3/re_study/email/msg00088.html
. >> 3/ FireWire is not Ethernet >> >> Items 1 and 2 have been addressed by enhancements to the IEEE-1394 >> specification (FireWore over CAT5 and bridging).
https://grouper.ieee.org/groups/802/3/bt/public/may15/diminico_01_0515.pdf
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.
https://grouper.ieee.org/groups/802/17/email/msg00746.html
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.
https://grouper.ieee.org/groups/802/3/re_study/email/msg00213.html
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.
https://grouper.ieee.org/groups/802/11/email/stds-802-11-tgm/msg00120.html
[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.
https://grouper.ieee.org/groups/802/3/re_study/email/msg00520.html
The "gating" approach is _a_ solution that can is well tested on IEEE 1394 and can easily be shown to suffice.