[802.3_ITSA] IEEE P802.3cx Task Force status
- To: STDS-802-3-ITSA@xxxxxxxxxxxxxxxxx
- Subject: [802.3_ITSA] IEEE P802.3cx Task Force status
- From: "Law, David" <dlaw@xxxxxxx>
- Date: Wed, 1 Jun 2022 19:42:23 +0000
- Accept-language: en-GB, en-US
- Arc-authentication-results: i=2; mx.google.com; dkim=pass header.i=@hpe.com header.s=pps0720 header.b=MDuj8taU; arc=pass (i=1 spf=pass spfdomain=hpe.com dkim=pass dkdomain=hpe.com dmarc=pass fromdomain=hpe.com); spf=pass (google.com: domain of prvs=01514ebef6=dlaw@xxxxxxx designates 148.163.143.35 as permitted sender) smtp.mailfrom="prvs=01514ebef6=dlaw@xxxxxxx"
- Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=hpe.com; dmarc=pass action=none header.from=hpe.com; dkim=pass header.d=hpe.com; arc=none
- Arc-message-signature: i=2; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=mime-version:content-transfer-encoding:content-language :accept-language:message-id:date:thread-index:thread-topic:subject :to:from:dkim-signature; bh=Q8jMI9iAI/1CMVIqZgwy4izXQk3MPetf8UBFPcHyhQs=; b=uzM/dv2OfY3AzKTyhCk2UpH/2bK1DU/HFlR4VFQICZdyqPDof5uaQHkcZpU7tyAs0B Am0L8gEbDjqgLuGABFBrmV8PlAwZrjQIB8zsY6NOcsWpCKkpI2mcy6wyWT9ubo2PDpdl LLwblV6GpKB2NXB6wH0vohF2THKN3v6rrBkMyZwLAdA903GRERDCMsz3paYxLE4sTG/D JlJRTOcEHQp96b18JlYl7+/5ae0rjK/CSd7+uUrUzw3ug2cnaDLB+vlqbhQVL6u92BvM 5EmIvTH8CqSdsRYgJfAMPc6ZfMWHO2YPLQqNL1PJ7xKvNxKOpzEoH0MIRzJfWsdTQ7hL rDag==
- Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=Q8jMI9iAI/1CMVIqZgwy4izXQk3MPetf8UBFPcHyhQs=; b=bSauDD3WjT8JBQomFLt6DbaVoWVFuczgf8IndPovbJnKGZXaUsAnll1fTCWWh9wmMfbVEXJ2Z07qsqxHvUvkO27MzhTpHq2nYiM70fTFgUJrO/0ayRkPNXaa741YX9A4GFxaSDfqgI62epd9HfZZJobYVqPFrVxiNcZzf+/1l8WcIqUsR8K7B07cjhKEAc05K5WDmvR5lkGnUPz89cUJ8wH5mRSSDGpyIKvJPbnZk5dkvdztbGW/8rglClmeWMO2/G1bZXFcbyK/0XUeVLqb9uu3aNaKZU+mUdQECBVieV+BKDp9xYadK160/mlJei6aQc18CB4SpPOhECX6sAB2+w==
- Arc-seal: i=2; a=rsa-sha256; t=1654112559; cv=pass; d=google.com; s=arc-20160816; b=Zd5Z+z6dI5Fqkzak9bAW4SX4vPYZ0PFVJHpoUR0/ZCng8BYTxKL9tV+Pcq7m4lSK4v vKDaF+hfTP1E3kgFT/7M8xb01Kd8s2euEkC3hSsw6AKHESfHOmxpe3aSbngYjBQCUK1p exS0il1BfFq3+uKAhS0y1/GBPa/ukl4nfE5CXUDNmuX1nb0HepXV63Jjxq69pssxI/4p YVdGsrpFmPvFllmxhCp/ui/SpkCai0cI8gTlh6fdUocyT3oG9R9GxGXYYQGVPvJFZsY6 mgf/YNhw65vCVj78tyP5qWINi+EM4yHVXqPNnKRFpzMlxgGABZ3mcgfhE5St3RM81y9y geeQ==
- Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=fg4UVvfQgBe7dFr1MLjYNc6gzHI9vKK2m740QW7P754AJCrzqlkz4zbgmfz3FDkz/eKAGSrw66nspqY1oip8JEfp/yLhzmi9HPZURxGaL8LRheVsvUHt4hbZmoEaTcdhDDms3J99Mo0nFrXdmuTqtxU+RxN6qIDGduCepYrOgsmm6KAK6rEJkX0dm7gyCvNS+Z37Ub1pKF4gYN+CCPJfCcf03cKY6QBTAC2T9VuPetH5lF00fBLFyQqKmho9poQ4ItMv2Z7yA2dvzy8UprS2QqbCfLJyCrAJYGhz6E4hyRgVUEJDSFvChhjTC0fCzoADnTgEiI3isTBJUIh/DNBwtA==
- Delivered-to: mhonarc@xxxxxxxxxxxxxxxx
- Delivered-to: stds-802-3-ITSA@xxxxxxxxxxxxxxxxx
- List-help: <https://listserv.ieee.org/cgi-bin/wa?LIST=STDS-802-3-ITSA>, <mailto:LISTSERV@LISTSERV.IEEE.ORG?body=INFO%20STDS-802-3-ITSA>
- List-owner: <mailto:STDS-802-3-ITSA-request@LISTSERV.IEEE.ORG>
- List-subscribe: <mailto:STDS-802-3-ITSA-subscribe-request@LISTSERV.IEEE.ORG>
- List-unsubscribe: <mailto:STDS-802-3-ITSA-unsubscribe-request@LISTSERV.IEEE.ORG>
- Reply-to: "Law, David" <dlaw@xxxxxxx>
- Thread-index: Adh1kuOPsilmOjinTK6GfAm3XEVTrA==
- Thread-topic: IEEE P802.3cx Task Force status
Dear IEEE P802.3cx Task Force,
At the March 2022 IEEE 802 Plenary session IEEE P802.3cx received conditional approval to proceed to Standards Association ballot. One of the conditions to be met before proceeding to Standards Association ballot is item (c), 'No technical changes, as determined by the Working Group Chair, were made as a result of the recirculation ballot.' <https://mentor.ieee.org/802-ec/dcn/17/ec-17-0090-25-0PNP-ieee-802-lmsc-operations-manual.pdf#page=23>.
Upon my review of the changes that will result from the comment responses <https://ieee802.org/3/cx/comments/802d3cx_D2_4_approved.pdf>, and the changes in the compare draft <https://ieee802.org/3/cx/private/Files/802.3cx_D2p5_CMP.pdf>, I was unable to make that determination. For example, I see several register number changes on page 4, I see the addition of 'in ns' and 'with ns resolution' to two entries to Table 45-139 on pages 6, 7 and 8, and similar text is added to subclause headings on page 9, and the deletion of the text 'Writes to this bit are ignored if they attempt to set the bit to a value for which the corresponding capability bits in register (3.1800) indicate is not supported' and addition of the text 'This bit has an effect only if both data delay measurement point ability bits are set to 1 in the TimeSync PCS capability register (see 45.2.3.67).' to subclause 45.2.3.69a.1 on page 10'.
While Motion #3 of the IEEE P802.3cx Task Force meeting held on 16 May 2022 authorised the editor to produce D3.0 on the basis of D2.4 closed comments and proceed to IEEE SA ballot, based on the above, this will not be possible. The IEEE P802.3cx Task Force Chair will send an email to propose an alternative path forward.
One additional item I wanted to inform you was that I have asked that the IEEE P802.3cx amendment number be updated to amendment 6. This is because I believe that IEEE P802.3de will be ready for unconditional submittal to the September RevCom agenda at the July plenary, however, IEEE P802.3cx will only be requesting unconditional approval to proceed to Standards Association ballot.
Best regards,
David Law
IEEE 802.3 Ethernet Working Group Chair
________________________________________________________________________
To unsubscribe from the STDS-802-3-ITSA list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-3-ITSA&A=1