Thread Links Date Links
Thread Prev Thread Next Thread Index Date Prev Date Next Date Index

[802.3_NGECDC] Re Nendica "Header Compression" Workshop,



Folks,

 

For those on the Nendica "Header Compression" Workshop call this morning.

 

Having done some more homework (802-2024, 802.1AC-2016, 802.3-2022), I acknowledge that 802/802.1/802.3, including the IEE and EISS definitions, do not require changes to “support” the UEC UFH header.

 

For those who are interested in a longer read, here’s my assessment:

 

Apart from the U/L and I/G bits (and maybe the Y and Z bits) we can consider destination_address & source_address as opaque octet strings. 802.3 doesn’t care what’s in the SA/DA pair when it’s operating in promiscuous receive mode. The MAC Service (802.1AC-2016 clause 14) used for a host is a subset of the ISS (802.1AC-2016 clause 11). The Ethernet convergence function (802.1AC-2016 clause 13.1) passes the destination_address and source_address parameters unaltered.

 

802 “8.4 Local MAC addresses” states:

·         Except for U/L and I/G all bits of the address are locally administered.

·         The locally administered bits of local MAC addresses are arbitrarily assignable under the condition that local MAC addresses are unique within a LAN

 

802 “8.4.3 Structured Local Address Plan (SLAP)” provides a little more structure for address management  for a little more control by assigning the least significant 4 bits of the initial octet on an address as SAI bits(M,X,Y,Z) which are used to assign 4 SLAP quadrants (Extended Local, Standard Assigned, Administratively Assigned, Reserved). This also allows other 802 standards to assign additional SLAP bits. The non-reserved quadrants are

·         Extended Local includes a 24 bit Company ID (CID aka OID), so I don’t think that fits the UFH scheme.

·         Standard Assigned requires an 802 standard to define the address format

·         Administratively Assigned allows for arbitrary assignment having consumed 4 bits of the address

 

SLAP allows for multiple different local address allocation schemes operating on the same LAN.   

 

UEC_liaison_2026-04-UFH_Presentation_to_IEEE.pdf depicts using SLAP Administratively Assigned addresses with the extra two bits (Y,Z) set to 00. Unless it’s a goal to run multiple local address assignment schemes on the target networks, the UFH could not use SLAP and reclaim an extra two bits.

 

Regards,

Peter

_______________________________________________________________

Peter Jones               Distinguished Engineer,

                          Cisco Networking Hardware

                          Chair, Ethernet Alliance

                          Chair, IEEE 802.3 YANG Ad Hoc

Mobile:                   +1 408 315 8024

Email:                    petejone@xxxxxxxxx

Web:                      https://about.me/petergjones

Webex:                    https://cisco.webex.com/meet/petejone

Book a call:              Book time with Peter

_______________________________________________________________

 


To unsubscribe from the STDS-802-3-NGECDC list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-3-NGECDC&A=1