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.

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

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

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.

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. 

Regards, Edward ---------- Forwarded message --------- 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 < edward.ks.au@xxxxxxxxx > Sent: Thursday, January 26, 2023 8:22 AM To: Stacey, Robert < robert.stacey@xxxxxxxxx > 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.  

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.

John S. wants to make sure that we provide what is necessary to support requirements for 1394.

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

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.

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

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

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.

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.

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.

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.

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

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

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