CAnet II ARDNOC Meeting

1
CAnet II ARDNOC Meeting

• Nov 7th Ottawa

2
Agenda

• 800 Coffee and Muffins
• 830 Welcome to ARDNOC - Steve and Bill
• 835 ARDNOC tour - Steve
• 930 Technical Update - John Coulter and Steve
• 1030 Coffee
• 1045 Class C address space for C2
• 1115 Blackholing problems
• 1145 Distributed ARDNOC funding review - Bill
• 1215 Lunch
• ARDNOC arrangements for (who, how, when)
• 100 Route Server
• 130 Multitasking
• 200 Caching
• 230 Telephony
• 300 Coffee
• 315 Performance Measurement
• 345 IPv6
• 415 QoS, Others??

3
CAnet II Governance
4
From last meeting - Sept 15th

• The NTN will be decomissioned by Sept 30. Those
  regions that do not have an SVC capable switch by
  that time will not have access to a network, but
  routers will be able to connect
• Steve will coordinate with regions on gradual
  decommissioning of NTN
• By Sept 30 Mbone users will have to get their
  Mbone feed from their local GigaPOP
• Non QoS IP traffic will use UBR path. As a result
  close coordination or merging with TNOC required
  to make sure ATM projects do not impact
  production C2 traffic.
• VBR will be reserved for QoS traffic
• TNOC tentatively approves projects subject to
  review by ARDNOC that project will not impact
  production traffic.

5

• C2 technical committee recommends to the C2
  policy committee that C2 be the Mbone core for
  all Canada and that GigaPOPs be allowed to
  redistribute mbone to commercial ISPs as an
  experimental service only with no guarantees.
  This will allow smaller ISPs and SMEs to
  experiment and participate in advanced networking
  activities.
• C2 technical committee also discussed doing the
  same with hierarchical global caching. But no
  recommendation or resolution at this time.
• C2 technical committee to recommend to Steve
  Ladouceur what equipment to buy for 6 bone
• Bill St Arnaud to get clarification on approval
  for a Tier B with multiple connections through
  different RANs e.g. TRlabs

6
ARDNOC Process

• Bell to provide 1st and 2nd line support under
  ARDNOC
• 1st line is after hours 1-800-??
• 2nd line is after hours network engineer to do
  router resets, etc or will call 3rd line support
  in regions
• 3rd line support is ARDNOC engineering and other
  designated leads in regions
• First and Second Line are the primary interface
  outside of 9-5, when a trouble ticket resolution
  process escalates. Their role is to analyse the
  trouble from an engineering standpoint, when
  normal operational procedures did not work. Not
  required to perform major engineering work during
  off-hours, but simply to look for the obvious and
  try to fix-it.. The only people they talk to are
  ARDNOC and RAN engineering

7
Third Line Support

• Chief engineer this role to be assumed by Bell
  e.g. Steve Ladouceur.
• Overall contractual responsibility and authority
• Can make call to move or re-assign 3rd line prime
  and secondary engineering between RANs and ARDNOC
  (in consultation with C2 technical committee)
• Third Line Prime Engineer- They are primarily
  responsible for the trade-off studies,
  experimentation, and break-in of the service.
  Third Line-engineer is responsible to assist the
  Operations liaison in debugging serious problems
  which have escalated to this level (9-5)
  operation
• can be located in RAN/GigaPOPs or ARDNOC
• only RAN/GigaPOP engineering can participate in
  distributed ARDNOC i.e. not attached universities
  or colleges or individuals not directly part of
  RAN engineering team
• Third Line Secondary Engineer backs up prime as
  above
• if prime in RAN then secondary in ARDNOC and vice
  versa

8
Possible roles for RAN as part of ARDNOC

• Trade-off studies and Experimentation
• research, aimed at identifying a
  technology/protocol track for the service and
  production of specifications
• installing, testing and verifying the operability
  of the service and technology in a lab, prior to
  its deployment on the backbone.
• Technology Break In
• initial installation on the backbone with limited
  experimental access to one or two RAN's.
  Technology is integrated with the rest of
  backbone services, as well as within specific
  RANs, in order to assure compatibility and
  inter-operability with the existing
  infrastructure.
• Operations
• the service is deployed and accessed by all RANs.
  In this phase, the responsible RAN NOC is the
  principal entry point for trouble tickets into
  the ARDNOC. Also provides Prime Third Line
  Engineering support to other NOCs

9
Funding to RANs to be part of virtual ARDNOC

• Can define a project encompassing any phase from
  experimentation to operations
• RANs that made ARDNOC submissions get first crack
• Proposing a program to CAnet II policy committee
  for funding for virtual ARDNOC projects, National
  Connectedness trials, etc
• Criteria to be defined but 3 key conditions
• Encourage for profit private sector partner
• must have a RAN agreement in place with CANARIE

10
Preliminary Assignments

• All assignements of prime and secondary to be
  coordinated with Steve Ladouceur
• Mbone -
• Route Server -
• Caching -
• Statistics -
• OC3mon -
• Telephony -