||Mar 2012 Plenary
||How the connection_identifier value is used to obtain the B-MAC address is really implementation specific. There was a specific comment during the development of this to make sure the connection_identifier was an indirect reference to the actual MAC address and not explicit. This also allows the connection_identifier to contain other values for other port types (e.g. Port Extension). There was and is a strong desire to NOT have a learning/ageing function for this capability, so no additional table is required. Given this, we really don’t have a problem here, but a clarification could be helpful and two proposals are on the table; Make the connection_identifier explicitly a MAC address for CBPs or insert a note that indicates this is implementation specific and in the case of a 1:1 mapping does not require any learning/ageing and can be stored in the existing FDB. Add the following note just before the beginning of 6.10.1:
Note -- There is a 1:1 relationship between a given value of the connection_identifier and a backbone MAC address. This level of indirection is provided to allow the use of the connection_identifier parameter for other purposes by other types of Bridge Ports. The relationship between a given connection_identifier value and a backbone MAC address is maintained as long any FDB entry contains this value for the connection_identifier. No ageing mechanism other than that specified for Dynamic FDB entries is implied.
||Ready for Ballot