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

(ADSL2+, 1394, …) • Any other outreach (companies, countries) of importance to inform or engage?

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.

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.

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.

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

IEEE 1394. • The reliability of Ethernet components and systems can be extrapolated in the target environments with a high degree of confidence.

Kind regards Stephen On Thu, 16 Nov 2023 at 14:47, Hanxiao (Tony, WT Lab) < 0000177ab8f731c4-dmarc-request@xxxxxxxxxxxxxxxxx > wrote: --- 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?”  

Cell: +1 (819) 609-1394 E-Mail: francois.menard@xxxxxxxxxxx Follow-Ups : Re: [802.3_NGEPON] ONU ASIC and wavelength plans From: Glen Kramer Re: [802.3_NGEPON] ONU ASIC and wavelength plans From: Duane Remein Re: [802.3_NGEPON] ONU ASIC and wavelength plans From: Marek Hajduczenia References : Re: [802.3_NGEPON] ONU ASIC and wavelength plans From: Shawn Esser Re: [802.3_NGEPON] ONU ASIC and wavelength plans From: Marek Hajduczenia Re: [802.3_NGEPON] ONU ASIC and wavelength plans From: Barry Colella Re: [802.3_NGEPON] ONU ASIC and wavelength plans From: Marek Hajduczenia Re: [802.3_NGEPON] ONU ASIC and wavelength plans From: Barry Colella Prev by Date: Re: [802.3_NGEPON] ONU ASIC and wavelength plans Next by Date: Re: [802.3_NGEPON] ONU ASIC and wavelength plans Previous by thread: Re: [802.3_NGEPON] ONU ASIC and wavelength plans Next by thread: Re: [802.3_NGEPON] ONU ASIC and wavelength plans Index(es): Date Thread

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.

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.

IEEE 802.3 Open Revision Requests
Order by Request Number IEEE 802.3 Open Revision Requests Order by Request Number Req# Status Standard Clause Date Subject 1380 B 802.3.2-2019 Various, see details 08-Sep-20 MAC address format 1383 B 802.3.1-2013 Various, see details 19-Nov-20 References to IEEE Std 802.1D 1394 B 802.3-2022 98.2.1 18-Feb-22 Clause 98 HSM support 1395 B 802.3-2022 147.8 22-Mar-22 Mixing segment specifications 1396 B 802.3-2022 147.8 22-Mar-22 Mixing segment specifications 1397 B 802.3-2022 1.4.473 01-Apr-22 Definition of "PoDL PSE" 1398 B 802.3-2022 Various, see details 23-May-22 Primitive name 1399 B 802.3-2022 56.1.3 06-Jun-22 Split Table 56-1 by media type 1400 B 802.3-2022 4.1.2.2 13-Jul-22 Description of collision 1401 B 802.3-2022 144.3.5 09-Sep-22 Remove GLID from list 1402 B 802.3-2022 135F.1 01-Dec-22 Typo 1403 B 802.3-2022 Table 119-5 09-May-23 Typo 1404 B 802.3-2022 Annex 55A 12-May-23 Machine-readable extracts 1405 B 802.3-2022 Various, see details 26-May-23 Formatting error 1406 B 802.3-2022 Various, see details 26-May-23 Incorrect cross-reference 1407 B 802.3-2022 Various, see details 02-Jun-23 Update interface list 1408 B 802.3-2022 30.12.3.1.59 07-Jul-23 "PD" not "PSE" 1409 B 802.3-2022 30.12.3.1 10-Jul-23 Duplicate subclause numbers 1410 B 802.3-2022 Various, see details 06-Aug-23 Typo 1411 B 802.3-2022 99.3.6 06-Aug-23 mCRC value mapping 1412 B 802.3-2022 99.4.7.1 06-Aug-23 State diagram conventions 1413 B 802.3-2022 99.4.7.7 18-Aug-23 SMDS_ENCODE() definition 1414 B 802.3-2022 99.4.7.7 18-Aug-23 Typo 1415 B 802.3-2022 149.8.2.1 07-Sep-23 Error in return loss limit 1416 B 802.3cy-2023 165.8.2.1 07-Sep-23 Error in return loss limit 1417 B 802.3ck-2022 161.5.3.8 20-Sep-23 am_rxpayloads derivation 1418 B 802.3-2022 Figure 36-3 20-Sep-23 Incorrect title 1419 B 802.3-2022 Figure 99-6 22-Sep-23 Missing action 1420 B 802.3ck-2022 116.4 29-Sep-23 Incorrect delay constraints 1421 I 802.3-2022 97.4.2.4 11-Oct-23 infofield_complete behavior 1422 B 802.3-2022 97.4.2.4.10 11-Oct-23 Requirement conditional on EEE 1423 B 802.3ck-2022 Various, see details 08-Nov-23 AC-coupling to test points 1424 B 802.3ck-2022 Various, see details 08-Nov-23 Add measurement frequency 1425 B 802.3-2022 Figure 119-11 13-Dec-23 Typo 1426 B 802.3-2022 149.1.3 18-Jan-24 Extraneous signal 1427 B 802.3-2022 120G.3.3.5.2 25-Jan-24 Incorrect reference point 1428 R 802.3-2022 132.1.6 07-Feb-24 Incorrect cross reference 1429 R 802.3-2022 46.3.4.3 02-Apr-24 State diagram transition 1430 R 802.3-2022 Table 141-20 03-Apr-24 Incorrect column headings 1431 R 802.3-2022 Various, see details 29-Apr-24 Update reference Return to 802.3 Maintenance Requests Page Last Update: 08 May 2024

Here is a list of some of my relevant qualifications: Performance modeling activities: Founded and run AmerNet which specializes in architecture analysis and performance modeling for networking and communication products and have many clients in various committees of the IEEE 802 and elsewhere Recognized expert in the field of network/communication performance analysis and modeling and author of many publications, articles and papers on various aspects of LAN/Networking performance analysis Worked in the LAN performance analysis group at IBM since 1988 Activities in RPR: Have been participating in the RPRSG since the first meeting in May 2000 Volunteered to chair the adhoc committee on performance modeling for the RPRSG Successfully led the performance adhoc committee to reach agreement on a lot of open issues related to the performance modeling efforts Drafted and posted a draft charter for the RPR performance committee as well as the list of its accomplishments  Activities in the IEEE 802 standards and other standard bodies: An active participant in the IEEE 802 since 1992 Have been a voting member of 802.3, 802.5, 802.15 and 802.17 Represented IBM's position in various IEEE 802 committees Provided a tutorial on QoS and priorities in Token Ring LANs based on extensive simulations and performance analysis The main IEEE 802 representative for Rockwell Semiconductor Systems Chaired the QoS study group from July 1998 till March 1999 An active participant in the IETF, NP Forum and IEEE 1394 Educational background: MS degree in Electrical Engineering (Caltech - 1986) Professional background: Specialized in the area of LAN performance analysis for my entire career Responsible for the performance analysis of many system architectures and networking chips at IBM Responsible for joint research work between IBM and NC-State University in the area of multimedia performance in LAN environments Founded AmerNet in May 1998 which specializes in performance modeling and architectural analysis In response to a request from our chair to clarify why I am active in IEEE 802.17:   AmerNet provides services related to IEEE activities.

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

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 .

. • ~20 individuals from ~8 organizations • Goals for the Week – Create a set of non-binding SG Objectives – Presentations • Created ad hocs on plug and play, synchronous issues, and PoE • Set goals for November Plenary IEEE 802.3 RESG San Antonio November 2004 3November 2004 PresentationsPresentations • “Application Objectives,” Dennis Lou, Pioneer • “MaGIC experience,” Alexei Beliaev, Gibson Labs • “Bridging 1394: a requirement for Residential Ethernet, “ Michael Johas Teener, Plumblinks • “Technical and economic feasibility for millisecond deterministic delay in Residential Ethernet,” Michael Johas Teener, Plumblinks • “Residential Ethernet: 2 Criteria,” Mike McCormack, 3Com • “Some Issues and Considerations for RE,” Jae Hun Cho, Chong Ho Yoon, Samsung Electronics IEEE 802.3 RESG San Antonio November 2004 4November 2004 Draft Objectives 9/30/2004Draft Objectives 9/30/2004 • Plug and Play – No user setup required (i.e.

The following presentations were made: #1 Geoff Thompson, Nortel – Spyder-LAN (see Spider-LAN.ppt) Discussion: 1394 compatibility 100Mbps compatibility Can spyder mode be originated and best-effort data be later sent from the same DTE Can spider elements be cascaded?

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

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

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.