Our (TCL's) view is as follows: 1. We don't care what the incoming 802.1p bits are. By the time they reach us, it's already too late to do anything. 2. The IX is a layer three interconnect. So, we don't care about the enclosing Ethernet frame, only the crunchy goodness of the IP pocket within. 3. We do not know, nor we we care to know, about the nature of the IX network beyond the NNI itself. What happens within is entirely up to the IX operator.
Because of that: 1. We completely ignore the 802.1p bits on incoming frames. 2. We set the 802.1p bits on all outgoing frames to zero.
Where we do QoS, we base it entirely on the Diffserv bits in the IP header. We would assume that the IX operator, if it cares about 802.1p, will likewise set the bits based on Diffserv.
I suppose we might contemplate setting the outgoing bits for the benefit of the IX, but that would of course require some agreement on the mapping.
-- Michael Newbery IP Architect TelstraClear Limited
Oh Michael, I'm really sorry about this, but someone has to say it :-) - TCL doesn't peer at the IX's so its all rather moot what TCL's view would be !, I'm sure all the IX peers would welcome you back with open arms QOS or not however ;-)