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.

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.

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.

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

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.

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. >> >> The numbers I quote here are open for discussion.

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.

[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 : Thu, 28 Sep 2023 00:07:36 +0000 All,   I have uploaded updated versions of the following documents: LB276 comments and approved resolutions ( https://mentor.ieee.org/802.11/dcn/23/11-23-1394-07-00bf-lb276-comments-and-approved-resolutions.xlsx ) LB276 SPs and motions ( https://mentor.ieee.org/802.11/dcn/23/11-23-1494-03-00bf-lb276-sps-and-motions.xlsx ) Best,   Claudio   Assigned Ready for Motion Approved RfM+A Alecs 18 0 16 16 Ali 33 0 33 33 Assaf 26 0 0 0 Atsushi 47 21 0 21 Benedikt 6 0 0 0 Chaoming 2 0 1 1 Cheng 46 0 34 34 Chris 15 0 0 0 Claudio (E) 66 53 0 53 Claudio (T) 29 27 0 27 Dibakar 25 0 0 0 Dongguk 8 0 3 3 Dong 32 11 0 11 Mahmoud 17 10 0 10 Mengshi 20 20 0 20 Mike M. 1 0 1 1 Naren 34 0 4 4 Ning 1 0 0 0 Pei 11 7 4 11 Rojan 4 0 0 0 Rui Du 27 6 0 6 Rui Yang 8 0 8 8 Shuling (Julia) 4 0 0 0 Stephen S. 24 0 9 9 Xiandong 13 0 13 13 Yan 10 0 4 4 Yanjun 1 0 0 0 Zhanjing 8 8 0 8 Zhuqing 9 0 0 0 All 545 163 130 293 0.299082569 0.2385321 0.5376147   To unsubscribe from the STDS-802-11-TGBF list, click the following link: https://listserv.ieee.org/cgi-bin/wa?

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

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." > > Background material includes: > http://grouper.ieee.org/groups/msc/MSC200404/RbrSlides2004Mar31.pdf > http://grouper.ieee.org/groups/msc/MSC200401/RprBackplane.pdf > > Items on the agenda include: > 1) Formulation of email reflector lists. > 2) Review of approved PAR. > 3) Sollicitation of technical inputs and strawman proposals. > 4) Discussion of related activities. > 5) Future meeting schedule. > 6) Other items as requested. > > In particular, this is an opportunity to suggest directions, revisions > of the slides and objectives, and/or strawman proposals.

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.

. – Identified points of agreement on autonegotiation – Agreed to specify 10 GbE serial, GbE serial and 10 GbE four lane (change of Five Criteria approved to be consistent with these interface objectives) – Adopted definition of “improved FR4” – Signaling ad-hoc to be formed 16 July 2004 IEEE 802.3 Report 7 802.3aq 10GBASE-LRM • Extends Ethernet capabilities at 10 Gb/s – Operation over installed multimode fiber – New physical layer to run under 802.3ae specified XGMII • Working toward first draft 16 July 2004 IEEE 802.3 Report 8 Congestion Management SG • Adopted narrowed problem statement: 802.3 MAC client needs to be able to limit traffic being received from its peer to avoid congestion due to oversubscription • Agreed on a partial set of objectives for a possible project • Study Group extended through November plenary meeting 16 July 2004 IEEE 802.3 Report 9 Frame Expansion SG • Address request from 802.1 to expand 802.3 maximum frame size to allow addition of protocol header and trailer fields – IEEE 802.3 Ad Hoc/CFI held – Also subject of joint technical plenary with 802.1 – Half duplex repeater limits and other PHY layer limitation were discussed, additional study required for PHY layers that support retiming in the data path • Study Group approved by 802.3 and Executive Committee 16 July 2004 IEEE 802.3 Report 10 Residential Ethernet SG • Successful call for interest held on Residential Ethernet – Focus is requirements of consumer electronics within the home – Issues include latency, latency jitter, and timing synchronization for consumer media distribution/playback • Study Group approved by 802.3 and Executive Committee 16 July 2004 IEEE 802.3 Report 11 Other Activities • IEEE 1394 tutorial sponsored • New maintenance requests approved, interpretations response approved • Autumn interim meeting – Details are TBD – Target week: 27 September 2004 – Target location: North America

- Speeds - Connectivity Study Item 3: Investigating existing mechanismsInvestigating existing mechanisms - 802.3 Clause 64, Clause 65 - 1394 isochronous - Gibson MaGIC Study Item 4: Interactions with 802.1Interactions with 802.1 - Ex: 802.1d, 802.1p, 802.1q, etc… IEEE 802.3 CFI Portland July 2004 7July 2004 Call for InterestCall for Interest Request 802.3 at the Closing Plenary to form a Residential Ethernet Study Group to develop a standards project proposal (PAR and 5 Criteria) for Residential Ethernet.

I have updated the GEN Comment Spreadsheet: https://mentor.ieee.org/802.11/dcn/12/11-12-1394-01-000m-gen-adhoc-preballot-comment-collection-resolutions.xlsx   The Tab for Vinko's set of comments is now labeled GEN-1297 Dorothy will have a motion prepared for this morning that accepts the resolution for GEN Motion A (Comments from Sept), and GEN-1297 (Vinko's Comments).  

Re: [STDS-802-11-TGAZ] TGaz Sep. 9th Telecon Agenda and Call for Submiss Thread Links Date Links Thread Prev Thread Next Thread Index Date Prev Date Next Date Index Re: [STDS-802-11-TGAZ] TGaz Sep. 9th Telecon Agenda and Call for Submissions To : STDS-802-11-TGAZ@xxxxxxxxxxxxxxxxx Subject : Re: [STDS-802-11-TGAZ] TGaz Sep. 9th Telecon Agenda and Call for Submissions From : "Das, Dibakar" < dibakar.das@xxxxxxxxx > Date : Thu, 10 Sep 2020 17:52:45 +0000 Hi Jonathan,   Can you please add the following CR submissions to the queue: 11-20-1392- CR for 11.22.6.3.3 (Dibakar Das) 11-20-1393- Misc CR for Clause 9 (Dibakar Das) 11-20-1394- Misc CR for Clause 11 (Dibakar Das) ?  

Jonathan   From: Das, Dibakar Sent: Thursday, September 10, 2020 10:53 To: Segev, Jonathan ; STDS-802-11-TGAZ@xxxxxxxxxxxxxxxxx Subject: RE: TGaz Sep. 9th Telecon Agenda and Call for Submissions   Hi Jonathan,   Can you please add the following CR submissions to the queue: 11-20-1392- CR for 11.22.6.3.3 (Dibakar Das) 11-20-1393- Misc CR for Clause 9 (Dibakar Das) 11-20-1394- Misc CR for Clause 11 (Dibakar Das) ?  

. > >> > > >> >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. > >> >I naively thoutht that to be the premise of our charter. > >> >Times change, I suppose... > >> > > >> >Cheers, > >> >DVJ > >> > > >> > >> -----Original Message----- > >> > >> From: Geoff Thompson [ mailto:gthompso@nortel.com ] > >> > >> Sent: Wednesday, August 08, 2007 3:07 PM > >> > >> To: Floyd Backes > >> > >> Cc: dvj@alum.mit.edu; Geoff Thompson; a.n.weaver@IEEE.ORG; > >> > >> stds-rac@IEEE.ORG > >> > >> Subject: RE: Request for multiple OUI assignments > >> > >> > >> > >> > >> > >> At 11:48 AM 8/8/2007 , Floyd Backes wrote: > >> > >> >If you feel strongly about this, you could review the > >> latest version of > >> > >> >802.1 MAC Bridging, figure out how it can be made to work > >> using the same > >> > >> >MAC address on every port, get a PAR to update the > >> standard, and then > >> > >> >slug it out with Mick over the ensuing 2 years to produce a revised > >> > >> >standard.

[STDS-802-11-TGBF] Updated group documents (LB276) Thread Links Date Links Thread Prev Thread Next Thread Index Date Prev Date Next Date Index [STDS-802-11-TGBF] Updated group documents (LB276) To : STDS-802-11-TGBF@xxxxxxxxxxxxxxxxx Subject : [STDS-802-11-TGBF] Updated group documents (LB276) From : Claudio da Silva < 00001ce441172b4c-dmarc-request@xxxxxxxxxxxxxxxxx > Date : Thu, 14 Sep 2023 14:42:50 +0000 All,   I have uploaded updated versions of the following documents: LB276 comments and approved resolutions ( https://mentor.ieee.org/802.11/dcn/23/11-23-1394-05-00bf-lb276-comments-and-approved-resolutions.xlsx ) LB276 SPs and motions ( https://mentor.ieee.org/802.11/dcn/23/11-23-1494-01-00bf-lb276-sps-and-motions.xlsx ) Best,   Claudio   Assigned Ready for Motion Approved RfM+A Alecs 18 0 16 16 Ali 33 0 33 33 Assaf 26 0 0 0 Atsushi 47 0 0 0 Benedikt 6 0 0 0 Chaoming 2 0 1 1 Cheng 46 0 34 34 Chris 15 0 0 0 Claudio (E) 66 0 0 0 Claudio (T) 29 0 0 0 Dibakar 25 0 0 0 Dongguk 8 0 3 3 Dong 32 0 0 0 Mahmoud 17 0 0 0 Mengshi 20 0 0 0 Mike M. 1 0 1 1 Naren 34 0 4 4 Ning 1 0 0 0 Pei 11 0 4 4 Rojan 4 0 0 0 Rui Du 27 0 0 0 Rui Yang 8 0 8 8 Shuling (Julia) 4 0 0 0 Stephen S. 24 0 9 9 Xiandong 13 0 13 13 Yan 10 0 4 4 Yanjun 1 0 0 0 Zhanjing 8 0 0 0 Zhuqing 9 0 0 0 All 545 0 130 130 0 0.2385321 0.2385321   Submitted Ready for Motion Approved RfM+A PoC Annexes 29 0 0 Claudio DMG 84 0 23 23 Alecs Editorial 67 0 1 1 Claudio Exchange 98 0 53 53 Cheng Misc 26 0 20 20 Zinan OST 147 0 15 15 Chaoming Reporting 60 0 3 3 Chris SBP 34 0 15 15 Cheng All 545 0 130 130 0 0.2385321 0.238532     To unsubscribe from the STDS-802-11-TGBF list, click the following link: https://listserv.ieee.org/cgi-bin/wa?

Firewire UTP – IEEE 1394 over UTP.

Best Regards,   Adrian P STEPHENS Tel: +44 (1793) 404 825 Tel: +44 (7920) 084 900 Tel: +1 (408) 239 7485   ---------------------------------------------- Intel Corporation (UK) Limited Registered No. 1134945 (England) Registered Office: Pipers Way, Swindon SN3 1RJ VAT No: 860 2173 47   From: ***** IEEE stds-802-11-tgm List ***** [mailto:STDS-802-11-TGM@xxxxxxxx] On Behalf Of Jon Rosdahl Sent: Tuesday, December 11, 2012 2:25 PM To: STDS-802-11-TGM@xxxxxxxxxxxxxxxxx Subject: [STDS-802-11-TGM] [Gen AdHoc] Update to comment spreadsheet through Dec 7th Telecon   --- 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.