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.
Dear Colleague,
This is to notify you that one or more objects in which you are
designated for notification have been modified in the NZRR routing
registry database.
These objects are used to configure the various NZIX route servers
(http://nzix.net/) so you can expect the relevant servers to be reloaded
in the near future. The reloading of the servers is staggered over a
period of time so that if you are peering with both servers at an
exchange, you can maintain at least one BGP session at all times and
consequently a full set of routes.
Diagnostic output:
------------------------------------------------------------
---
PREVIOUS OBJECT:
route-set: AS9439:RS-ROUTES:AS2687
descr: advertised to AS9439 by at&t - AS2687
members: 103.5.80.0/22^22-29,
202.36.192.0/22^22-29,
32.114.24.0/23^23-29,
122.248.172.0/23^23-29,
202.14.252.0/23^23-29,
202.36.68.0/23^23-29,
203.99.128.0/23^23-29,
203.163.70.0/23^23-29,
203.176.122.0/23^23-29,
32.234.81.0/24^24-29,
202.12.105.0/24^24-29,
202.14.254.0/24^24-29,
202.27.160.0/24^24-29,
202.36.80.0/24^24-29,
202.37.254.0/24^24-29,
202.135.38.0/24^24-29,
202.135.49.0/24^24-29,
202.135.64.0/24^24-29,
202.135.107.0/24^24-29,
202.135.111.0/24^24-29,
202.135.112.0/24^24-29,
202.135.116.0/24^24-29,
202.135.142.0/24^24-29,
202.135.146.0/24^24-29,
202.135.190.0/24^24-29,
202.135.192.0/24^24-29,
202.135.231.0/24^24-29,
203.163.68.0/24^24-29,
203.163.94.0/24^24-29,
203.163.98.0/24^24-29,
203.196.101.0/24^24-29,
203.196.119.0/24^24-29,
203.196.121.0/24^24-29
admin-c: RPA1-NZRR
tech-c: RPA1-NZRR
notify: rpsl-admin(a)nzix.net
notify: nznog(a)list.waikato.ac.nz
notify: dl-globalwork(a)att.com
mnt-by: MAINT-NZRR-NZ
changed: rpsl-admin(a)nzix.net 20120531
source: NZRR
REPLACED BY:
route-set: AS9439:RS-ROUTES:AS2687
descr: advertised to AS9439 by AT&T - AS2687
members: 103.5.80.0/22^22-29,
202.36.192.0/22^22-29,
32.114.24.0/23^23-29,
122.248.172.0/23^23-29,
202.14.252.0/23^23-29,
202.36.68.0/23^23-29,
203.99.128.0/23^23-29,
203.163.70.0/23^23-29,
203.176.122.0/23^23-29,
32.234.81.0/24^24-29,
202.12.105.0/24^24-29,
202.14.254.0/24^24-29,
202.36.80.0/24^24-29,
202.37.254.0/24^24-29,
202.135.38.0/24^24-29,
202.135.49.0/24^24-29,
202.135.64.0/24^24-29,
202.135.107.0/24^24-29,
202.135.111.0/24^24-29,
202.135.112.0/24^24-29,
202.135.116.0/24^24-29,
202.135.142.0/24^24-29,
202.135.146.0/24^24-29,
202.135.190.0/24^24-29,
202.135.192.0/24^24-29,
202.135.231.0/24^24-29,
203.163.68.0/24^24-29,
203.163.94.0/24^24-29,
203.163.98.0/24^24-29,
203.196.101.0/24^24-29,
203.196.119.0/24^24-29,
203.196.121.0/24^24-29
admin-c: RPA1-NZRR
tech-c: RPA1-NZRR
notify: rpsl-admin(a)nzix.net
notify: nznog(a)list.waikato.ac.nz
notify: tim(a)citylink.co.nz
mnt-by: MAINT-NZRR-NZ
changed: rpsl-admin(a)nzix.net 20120605
source: NZRR
------------------------------------------------------------
Dear Technical Community,
The next step towards completing the DNSSEC deployment for .nz is to
sign the second level domains, thus allowing registrants to enable
DNSSEC for their domains. We have prepared a staggered deployment
schedule for the unmoderated second level domains, which is available in
full at http://nzrs.net.nz/dns/dnssec
As a summary, geek.nz will be the first DNSSEC signed second level
domain, closely followed by ac.nz, gen.nz, maori.nz and school.nz, all
during June. In July, net.nz and org.nz will be signed, ending with
co.nz during early August.
As a reminder, the SRS has been able to receive DS records for domains
under .nz since last year, and those records will be included in their
respective zone when DNSSEC is fully enable for the second level domain.
We advise against using any of the Second Level Domains DS records as a
trust anchors.
If you have any questions around this process, don't hesitate to contact
us at support(a)nzrs.net.nz
Kind Regards,
--
Sebastian Castro
DNS Specialist
.nz Registry Services (New Zealand Domain Name Registry Limited)
desk: +64 4 495 2337
mobile: +64 21 400535
