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.

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.

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.

(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.1d, RFC-1394, IP, USB, PCI?)

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

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

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

.: IEEE 802.11-98/217 Submission System Architecture Overview P r i n t e r C a m e r a G a m e P a d U S B Lamp Smoke Detector Thermostat Security System Power Line 78 Stereo Camcorder VCR TV 1394 Phone Cable Grandma’s Brownies 3 cups flour 1 cup grated chocolate 1 cup sugar 1 stick butter Control Point May 1998 Stuart K.

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

. > > 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. > > DVJ > > > David V.

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

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.

References: https://mentor.ieee.org/802.11/dcn/12/11-12-1189-09-000m-mac-adhoc-pre-ballot-comment-collection-resolutions.xls , https://mentor.ieee.org/802.11/dcn/12/11-12-1082-12-0000-revmc-pre-ballot-comments.xls and https://mentor.ieee.org/802.11/dcn/12/11-12-1394-03-000m-gen-adhoc-preballot-comment-collection-resolutions.xlsx .

[STDS-802-11-EDITORS] 11be ANA request Thread Links Date Links Thread Prev Thread Next Thread Index Date Prev Date Next Date Index [STDS-802-11-EDITORS] 11be ANA request To : STDS-802-11-EDITORS@xxxxxxxxxxxxxxxxx Subject : [STDS-802-11-EDITORS] 11be ANA request From : "Stacey, Robert" < robert.stacey@xxxxxxxxx > Date : Thu, 26 Jan 2023 17:04:22 +0000 --- This message came from the IEEE 802.11 Editors' Reflector --- Hello Edward,   You allocations: TransactionID Type Status User Group Resource Ref Doc Ref Subclause Ref Location Name Req Value Description Allocated Value 1390 Allocate Pending Edward Au TGbe StatusCodes IEEE Std 802.11-2020 9.4.1.9 Table 9-50 DENIED_LINK_ON_WHICH_THE_(RE)ASSOCIATION FRAME_IS_ TRANSMITTED_NOT_ACCEPTED Link not accepted because the link on which the (Re)Association Request frame is transmitted is not accepted. 139 1391 Allocate Pending Edward Au TGbe StatusCodes IEEE Std 802.11-2020 9.4.1.9 Table 9-50 EPCS_DENIED_VERIFICATION_FAILURE EPCS priority access is temporarily denied because the receiving AP MLD is unable to verify that the non-AP MLD is authorized for an unspecified reason. 140 1392 Allocate Pending Edward Au TGbe StatusCodes IEEE Std 802.11-2020 9.4.1.9 Table 9-50 DENIED_OPERATION_PARAMETER_UPDATE Operation parameter update denied because the requested operation parameters or capabilities are not acceptable. 141 1393 Allocate Pending Edward Au TGbe Element ID Extension 1 IEEE Std 802.11-2020 9.4.2.1 Table 9-92 MLO Link Information 133 1394 Allocate Pending Edward Au TGbe Element ID Extension 1 IEEE Std 802.11-2020 9.4.2.1 Table 9-92 AID Bitmap 134 1395 Allocate Pending Edward Au TGbe Element ID Extension 1 IEEE Std 802.11-2020 9.4.2.1 Table 9-92 Bandwidth Indication 135   So you don’t need to ask twice 😊   -Robert     From: Edward Au Sent: Thursday, January 26, 2023 8:22 AM To: Stacey, Robert Subject: 11be ANA request   Dear Robert,   I would like to request allocation of the following 6 items for TGbe:   Type of Request Resource Name Item Name Item Description Requested Value (if any) Requested by Task Group Requested by Name Allocate StatusCodes DENIED_LINK_ON_WHICH_THE_(RE)ASSOCIATION FRAME_IS_ TRANSMITTED_NOT_ACCEPTED Link not accepted because the link on which the (Re)Association Request frame is transmitted is not accepted.  

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

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