1055 results found. results are sorted by relevance
  251-275
https://grouper.ieee.org/groups/802/11/email/stds-802-11-tgm/msg00141.html
From : Jon Rosdahl < jrosdahl@xxxxxxxx > Date : Tue, 15 Jan 2013 01:02:41 -0700 --- This message came from the IEEE 802.11 Task Group M Technical Reflector --- Hello, I have uploaded the GEN AdHoc file that shows all the comments in the Gen AdHoc: https://mentor.ieee.org/802.11/dcn/12/11-12-1394-04-000m-gen-adhoc-preballot-comment-collection-resolutions.xlsx   There are several comments that are still open, as we try to complete prep for closing comments this week, we could use your help.
https://grouper.ieee.org/groups/802/11/email/stds-802-11-tgm/msg00156.html
[STDS-802-11-TGM] Update to Gen AdHoc comments posted -- 11-12/1394r8 Thread Links Date Links Thread Prev Thread Next Thread Index Date Prev Date Next Date Index [STDS-802-11-TGM] Update to Gen AdHoc comments posted -- 11-12/1394r8 To : STDS-802-11-TGM@xxxxxxxxxxxxxxxxx Subject : [STDS-802-11-TGM] Update to Gen AdHoc comments posted -- 11-12/1394r8 From : Jon Rosdahl < jrosdahl@xxxxxxxx > Date : Thu, 17 Jan 2013 16:42:19 -0700 --- This message came from the IEEE 802.11 Task Group M Technical Reflector --- https://mentor.ieee.org/802.11/dcn/12/11-12-1394-08-000m-gen-adhoc-preballot-comment-collection-resolutions.xlsx Covers comment resolutions added through PM1 Thursday Jan 17th.  
https://grouper.ieee.org/groups/802/11/email/stds-802-11-tgm/msg00158.html
From : Jon Rosdahl < jrosdahl@xxxxxxxx > Date : Thu, 17 Jan 2013 19:30:53 -0700 --- This message came from the IEEE 802.11 Task Group M Technical Reflector --- https://mentor.ieee.org/802.11/dcn/12/11-12-1394-09-000m-gen-adhoc-preballot-comment-collection-resolutions.xlsx   That is the last update planned for the week.
https://grouper.ieee.org/groups/802/11/email/stds-802-11/msg00201.html
From : Jon Rosdahl < jrosdahl@xxxxxxxx > Date : Tue, 15 Jan 2013 01:02:41 -0700 --- This message came from the IEEE 802.11 Working Group Reflector --- Hello, I have uploaded the GEN AdHoc file that shows all the comments in the Gen AdHoc: https://mentor.ieee.org/802.11/dcn/12/11-12-1394-04-000m-gen-adhoc-preballot-comment-collection-resolutions.xlsx   There are several comments that are still open, as we try to complete prep for closing comments this week, we could use your help.
https://grouper.ieee.org/groups/1722/1/contributions/2010/1722.1-turner-p1722_formats_2010-05-10-v1.pdf
High-precision multi-bit linear audio 25 to 196 bit PCM MIDI conformant SMPTE time code conformant Sample count Ancillary data 32bit floating point 24 bit * 4 pack 32bit generic 61883-7 (BO.1294) Transport Stream DirecTV DSS MPEG-2 transport stream. 130byte TS packet length 61883-8 (BT.601) Video Compressed and uncompressed video: 176x120 to 1920x1080, 15 to 60fps IIDC (1394 Digital Camera) Video Uncompressed video 160x120 to 1600x1200 RGB/YUV/B&W, 1.875 to 240fps MMA ?
https://grouper.ieee.org/groups/802/secmail/msg10441.html
. > - 802.15 representative to 802 Architecture committee > - 802 EC Attendance software point of contact, July 2006-present > - Sponsor ballot participant in a variety of groups (802.1, 802.16, > 802.11, 802.15, 802.20, 287, 1394, 260.3) > > James Gilb > ---------- This email is sent from the 802 Executive Committee email reflector.
https://grouper.ieee.org/groups/802/11/email/stds-802-11-tgm/msg00142.html
[STDS-802-11-TGM] update to Gen AdHoc Spreadsheet posted -- 11-12/1394r5 Thread Links Date Links Thread Prev Thread Next Thread Index Date Prev Date Next Date Index [STDS-802-11-TGM] update to Gen AdHoc Spreadsheet posted -- 11-12/1394r5 To : STDS-802-11-TGM@xxxxxxxxxxxxxxxxx Subject : [STDS-802-11-TGM] update to Gen AdHoc Spreadsheet posted -- 11-12/1394r5 From : Jon Rosdahl < jrosdahl@xxxxxxxx > Date : Tue, 15 Jan 2013 10:46:03 -0700 --- This message came from the IEEE 802.11 Task Group M Technical Reflector --- After reviewing the file, there were some minor errors that have been corrected here: https://mentor.ieee.org/802.11/dcn/12/11-12-1394-05-000m-gen-adhoc-preballot-comment-collection-resolutions.xlsx   note that Eldad's 5 Comments all now show up on Tab GEN 1431 correctly.
https://grouper.ieee.org/groups/802/11/email/stds-802-11-tgm/msg00146.html
https://mentor.ieee.org/802.11/dcn/12/11-12-1394-06-000m-gen-adhoc-preballot-comment-collection-resolutions.xlsx   Please let me know if you can take one or more comments.
https://grouper.ieee.org/groups/802/11/email/stds-802-11-tgm/msg00148.html
There are 10 CIDs that are ready now for a motion   https://mentor.ieee.org/802.11/dcn/12/11-12-1394-07-000m-gen-adhoc-preballot-comment-collection-resolutions.xlsx   28 CIDs have an owner -- 27 still open for help.   
https://grouper.ieee.org/groups/802/secmail/msg02607.html
. > 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" ;.
https://grouper.ieee.org/groups/802/3/maint/requests/maint_1394.pdf
When it 24 did this it listed the existing PHY speeds, thinking new PHYs would be 25 added as they came available. 802.3ch-2020 already failed to add itself. 26 Making this general change will fix the problem that clause 149 27 (2.5G/5G/10GBASE-T1) are not included, as well as smooth the path for 28 IEEE P802.3cy, without impacting existing networks, or closing 29 possibilities for 100BASE-T1L and any possible future 1000BASE-T1L. 30 Additionally, contributions in the Greater than 10 Mb/s long-reach SPE 31 study group have shown that long-reach 1 Gb/s is challenging, leaving 32 greater than 1 Gb/s unlikely - hence 1 Gb/s is a good threshold to pass 33 autonegotiation off to the shorter-reach HSM. 34 35 IMPACT ON EXISTING NETWORKS: None. 36 37 38 +----------------------------------------------------------------------+ 39 |Please attach supporting material, if any | 40 |Submit to:- David Law, Chair IEEE 802.3 | 41 |and copy:- Adam Healey, Vice-Chair IEEE 802.3 | 42 | | 43 |At:- E-Mail: stds-802-3-maint-req@ieee.org | 44 | | 45 | +------- For official 802.3 use -----------+ | 46 | | REV REQ NUMBER: 1394 | | 47 | | DATE RECEIVED: 18 February, 2022 | | 48 | | EDITORIAL/TECHNICAL | | 49 | | ACCEPTED/DENIED | | 50 | | BALLOT REQ'D YES/NO | | 51 | | COMMENTS: | | 52 +-------------+------------------------------------------+-------------+ 53 | For information about this Revision Request see - | 54 |http://www.ieee802.org/3/maint/requests/revision_history.html#REQ1394 | 55 +----------------------------------------------------------------------+ 56
https://grouper.ieee.org/rac/private/email/msg00969.html
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.
https://grouper.ieee.org/rac/private/email/msg00435.html
If Peter's concerns are properly paraphrased in the previous paragraph, then I note that: 1) Peter is an authority on 1212 & 1394. 2) Peter has valid points of concern.
https://grouper.ieee.org/rac/private/email/msg00968.html
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.
https://grouper.ieee.org/groups/802/3/re_study/email/msg00061.html
The DTV/audio "clusters" will likely be connected together with 1394, but the bridges between 1394 and 802.3+ will have queues as well, so that doesn't reduce the need for queue management.
https://grouper.ieee.org/groups/802/3/re_study/email/msg00067.html
The DTV/audio "clusters" will likely be connected together with 1394, but the bridges between 1394 and 802.3+ will have queues as well, so that doesn't reduce the need for queue management.
https://grouper.ieee.org/groups/802/3/re_study/email/msg00069.html
But first, this group needs to ask, among other potential use cases, should "1394 carriage over IP" be included as the legitimate use case for Residential Ethernet?
https://grouper.ieee.org/groups/802/17/email/msg00756.html
I'm more familiar with IEEE Std 1394, which distributes&synchronizes timers so that the microphone data can be presented to the amplifier without dropping/inserting samples.
https://grouper.ieee.org/groups/802/3/cm_study/public/november04/james_1_1104.pdf
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.
https://grouper.ieee.org/groups/1722/contributions/2007/avbtp-bartky-encapsulation-v0-05-2007-08-09.pdf
(see 802.1AS assumptions from AVB document)). • 61883 format over AVBTP will support presentation time in the same manner as 1394/61883 using the SYT field and in 24.576 MHz cycle time based on 802.1AS clock. – 61883-4 & 61883-7: Source Packet Header format with 0-127 seconds, 0-7999 8 kHz cycles, 0-3072 24.576 MHz sub-cycles.
https://grouper.ieee.org/groups/1722/contributions/2007/AVB-TP-Sync-mmora-070620.pdf
One of the warts on IEC61883 is the lack of layering (one can't tell where 61883 stops and 1394 starts).
https://grouper.ieee.org/groups/802/3/re_study/material/DVJ%20whitepapers/dvjReBars2005Aug10.pdf
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.
https://grouper.ieee.org/groups/802/3/re_study/material/DVJ%20whitepapers/dvjReNext2005Aug10.pdf
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.
https://grouper.ieee.org/groups/802/15/pub/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/1722/contributions/2007/avbtp-bartky-encapsulation-v0-08-2007-11-04.pdf
(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.