IEEE staff have noted that the public listing of Standard Group MAC Addresses found here: https://standards.ieee.org/products-services/regauth/grpmac/public.html has become out of date. The 802.1 Maintenance Task Group discussed this in the September 2018 interim meeting, and I took on the job of updating the tables for the above web page. A proposed revision of the tables for review is now at: http://www.ieee802.org/1/files/public/docs2018/maint-seaman-public-group-addresses-0918-v01.html a pdf version is at: http://www.ieee802.org/1/files/public/docs2018/maint-seaman-public-group-addresses-0918-v01.pdf [Assumptions about page size were made by the browser's "Export to PDF .." function when the pdf when created so the appearance of the page differs from, and is less satisfactory than html in a browser (at least when using Safari on my desktop machine)]. This note details the differences between the proposed update and the current public page tables. The visible content is described first. Notes on the details of the html follow. 1. Where the address assignment information is in IEEE Std 802.1Q, the table no longer makes reference to IEEE Std 802.1D under "Standards using the value": 802.1D has been withdrawn and the technical content transferred to IEEE Std 802.1Q. One reference to 802.1D has been retained: 01-80-C2-00-00-10 is the "All LANs Bridge Management Group Address" (now deprecated). Similarly references to other withdrawn standards (e.g. IEEE Std 802.5) have been retained where the assignment is not normatively recorded in a current standard. 2. References to IEEE 802.1 standards are to the base standard, not to any amendment in which they might first appear. The current text of any standard is the base standard plus approved amendments, so it is not necessary for these address assignment listings to refer to amendments. Referring to the base standard has the advantage of not requiring a change to the listing when the amendment is rolled up into the next revision of the base standard. Amendments previously referenced have been rolled up. 3. The current public page tables omit usage of the 802.1Q Reserved Addresses by other 802.1 standards. Recording our other uses is important, as a guard against changes to the use of the address or its renaming (which might cause confusion) without addressing all the dependencies on the address.I have checked (I believe) all the current 802.1 base standards and included them, where appropriate, under "Standards using the value". I note that 802.1BR identified the "Nearest non-TPMR Bridge group address" only by name, not by value. 4. The name(s) given to the 802.1Q Reserved Addresses in the "Notes" column have been updated to match (including case stropping) their names as given in IEEE Std 802.1Q-2018 Table 8-1. Where other referenced standards use (or historically have used) other names for the same assignment these are also given. 5. The group MAC addresses used in ISO 9542 ES-IS protocol have been moved to the Standard Group MAC Addresses table. The initial reason for their separation cannot be ascertained from reading this web page, and should not concern the reader. The 9542 values are just as 'standard' as the others. [The OUI 01-80-C2 was assigned to IEEE 802.1 and the WG has the responsibility of making further assignments to others who met the necessary criteria for an assignment. That registration activity is now undertaken by the RAC. The 9542 ES-IS assignment predated that arrangement. This history has no bearing on the use of the addresses.] 6. The headings "Standard using the value" have been changed to "Standards using the value" since some values are used and normatively referenced by more than one standard (in the original table, as well as the proposed revision). 7. "Reserved for future standardization" has been italicized in "Notes" just as "unassigned" is italicized. The italics helps the "Reserved .." state standout, just as it does for "unassigned". 6. The reference to IEEE Std 802.11aa has not been changed to IEEE Std 802.11. That change should probably be made (as for point 2 above) but should be checked with someone familiar with 802.11 to check that the amendment has been approved and will be rolled up. 7. The "Standard using the value" for the range 01-80-C2-00-00-40 to 01-80-C2-00-00-4F is recorded as "TRILL". This is not a satisfactory reference: "TRILL" is not a document. 8. The final "Note" has been upadterd to refere to the table of 802.5 Functional Address instaed of to "this table" as the letter is open to misinterpretation. HTML details: The html file for the tables referenced above is based on extracting the table from the much larger web page. It begins with: (line 3454 in the original web page text) and ends with: (line 3928 in the original web page text) So it may well be possible to update the original html simply by replacing those lines with the content of the reference html file. I have tried to be conservative with changes to the layout, though for reasons I don't understand the original cut out html had some text spacing problems (which I fixed) and used an em dash character that doesn't always render properly. I have replaced the em dashes with the html "—" which should always work. On the other hand the original was probably generated using a powerful editing/layout tool that I don't have access to, and maintenance of the web page might require continued use of that tool. In that case some one who does is stuck with the task of transcribing the updates from our revised tables. Mick Seaman 6th October 2018