Johas Teener - Mike@Teener.com PGP ID 0x3179D202 23 Acacia Way, Santa Cruz, CA 95062-1313 +1-831-247-9666, fax +1-831-480-5845 ------------------- www.teener.com ------------------------ Prev by Date: Re: [RE] Overprovisioning (was Re: [RE] CE applications) Next by Date: Re: [RE] CE applications (was: RE: [RE] Focus of discussions) Prev by thread: Re: [RE] Requirement: Bridging to 1394 Next by thread: Re: [RE] Overprovisioning (was Re: [RE] CE applications) Index(es): Date Thread

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

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

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

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

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

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. -           PoCs : Once you’ve reviewed the comments assigned to your area, please send a request for volunteers to your TTT. 

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.

Firewire UTP – IEEE 1394 over UTP.

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

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

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.

Probably useful to the customers, although accurate network timing and good QOS are likely to be perceived as threats by IEEE 1394 zealots.

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.

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.

Most noteable are IEEE 754 Floating Point >> > and IEEE 1394, and other microprocessor standards.

Most noteable are IEEE 754 Floating Point >> > and IEEE 1394, and other microprocessor standards.

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

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.

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.

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

Some overall news: * The IEEE SA Standards board approved the 1394 revision PAR.

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?

IEEE 1394 and 1588. • The reliability of Ethernet components and systems can be extrapolated in the target environments with a high degree of confidence. 15 November 2005 IEEE 802.1./802.3 Residential Ethernet 6 Economic Feasibility Cost factors known, reliable data Reasonable cost for performance expected Total installation costs considered • The cost factors for Ethernet components and systems are well known.