RE: How CIR behaviour in contention works for bit stream 2 and 3 Bit streams 2 and 3 define a CIR component which is incremented in 2.5 meg chunks. The default value is 2.5 meg CIR. In order to use this high priority queue the RSP must tag their layer 2 frames with P-bit 4. All other p-bits are remarked to 0--as per the TCF requirement. If a services exceeds the allocated CIR, those frames delivered outside of the policy will be discarded. That is anything over the CIR is dumped. From a end-user perspective, if all traffic was tagged high priority, then any excess over 2.5 would be randomly dropped and the customer would never experience the advertised 10m up / 30m down (low priority). Bit stream 3a is being designed to allow some excess to be used where frames out of policy will be tagged discard eligible, but not immediately discarded. Remember that Chorus has created labs in Auckland and Wellington which are open to Retail Service Providers so that services parameters appropriate to the applications that RSPs want to sell can be developed. The feedback from these labs needs to get to the TCF and CFH so any new products can be ratified by the industry. Curtis Owings Principal Solution Architect T +64 4 498 9355 (extn 49355) M +64 27 655 5335 E Curtis.Owings(a)chorus.co.nz Level 3, Deloitte House, 10 Brandon Street P O Box 632, Wellington www.chorus.co.nz P Please consider the environment before printing this e-mail ________________________________ This communication, including any attachments, is confidential. If you are not the intended recipient, you should not read it - please contact me immediately, destroy it, and do not copy or use any part of this communication or disclose anything about it. Thank you. Please note that this communication does not designate an information system for the purposes of the Electronic Transactions Act 2002.