High Speed Network Service

Product user guide

Version Number: July 2017

1 HSNS Product User Guide | July 2017 Table of Contents 1. INTRODUCTION TO HSNS PRODUCT USER GUIDE ...... 4 1.1. WHO IS IT FOR? ...... 4 1.2. PURPOSE ...... 4 1.3. ABOUT THIS DOCUMENT ...... 4 2. OVERVIEW ...... 4 2.1. KEY BENEFITS ...... 5 2.2. KEY FEATURES ...... 6 2.3. HSNS PREMIUM AND UFB ...... 7 3. HOW HSNS WORKS ...... 7 3.1. PRODUCT DESCRIPTION ...... 7 3.1.1. Ethernet coverage areas ...... 10 3.1.2. Tail Extension ...... 11 3.1.3. End-customer access ...... 11 3.1.4. Copper access ...... 11 3.1.5. Fibre access ...... 12 3.2. EAN FEATURES – HSNS PREMIUM & LITE ...... 13 3.3. CUSTOMER AND SERVICE VLANS ...... 14 3.3.1. Customer VLANs (CE-VLANs) ...... 14 3.3.2. Service VLANs (S-VLANs) ...... 14 3.4. SUPPORTED APPLICATIONS ...... 15 3.5. SECURITY OF CUSTOMER DATA PATH ...... 15 3.6. MAC ADDRESSES ...... 15 3.7. MTU SIZE ...... 15 3.7.1. HSNS Lite (copper) ...... 16 3.7.2. HSNS Lite (fibre)...... 16 3.7.3. HSNS Premium ...... 17 3.8. LAYER 2 CONTROL PROTOCOLS ...... 17 3.9. LAYER 3 CONTROL PACKETS ...... 17 3.10. END-CUSTOMER INTERFACE ...... 17 3.11. POI INTERFACE (E-NNI) ...... 18 3.12. AGGREGATION/HANDOVER OF TRAFFIC ...... 19 3.13. REMOTE HANDOVER ...... 19 4. OPERATIONAL SUPPORT ...... 20 4.1. GEOGRAPHIC AVAILABILITY ...... 20 4.2. HSNS SERVICE REQUEST TYPES ...... 20 4.3. SPEED UPGRADES ...... 22 4.4. ACCESS INSTALLATION & TESTING ...... 22 4.4.1. Copper access installs ...... 23 4.4.2. Fibre access installs ...... 23 4.4.3. Testing to your network ...... 24 4.5. CHURN / REASSIGNMENT ...... 24 4.6. FAULTS ...... 24 4.7. BILLING ...... 26 4.8. PRICING...... 26 5. GLOSSARY ...... 27 Appendix A Layer 2 control protocol handling ...... 31 Appendix B Reference modems & end-customer equipment requirements ...... 32 B.1 System elements ...... 32 B.1.1 End-customer equipment requirements ...... 32 Appendix C Jack-point and wiring and modem options for HSNS Lite (copper) ...... 34 C.1 Jack-point and wiring purchase option ...... 34

2 HSNS Product User Guide | July 2017 C.2 Jack-point and wiring technical specification ...... 34 Appendix D HSNS termination options ...... 36 D.1 HSNS Lite (fibre) glass only option ...... 36 D.1.1 SFP specifications for end-customer site: ...... 37 D.1.2 Testing:...... 38 D.2 HSNS Premium glass only option ...... 38 D.2.1 Testing:...... 40 Appendix E Service level targets ...... 41 E.1.1 HSNS availability ...... 41 E.1.2 Agreed service hours ...... 41 E.1.3 Geographic areas ...... 41 E.1.4 Service restoration ...... 41 E.1.5 HSNS throughput ...... 42 E.1.6 HSNS Latency ...... 43 E.1.7 Jitter ...... 44 E.1.8 Data loss ...... 44 Appendix F Interface options ...... 46 F.1 Handover link delivery ...... 46 F.2 Your requirements ...... 46 Appendix G Extended fibre access...... 48 G.1 Extended fibre access delivery...... 48 G.2 Extended fibre access feasibility result ...... 49 Appendix H Diversity options ...... 51 H.1 Access diversity: ...... 51 H.1.1 Ducting ...... 52 H.2 Last mile access diversity ...... 52 H.3 Geographic access diversity ...... 53 H.4 Full diversity ...... 54 H.5 Logical diversity ...... 55 H.5.1 Handover diversity ...... 56 H.5.2 Geographic handover diversity ...... 58 APPENDIX I: HSNS POIS ...... 59

3 HSNS Product User Guide | July 2017 1. Introduction to HSNS product user guide

HSNS Premium is a highly flexible layer 2 Ethernet solution that supports business-grade applications, such as voice, Citrix and Virtual Private Networks.

1.1. Who is it for?

Ethernet services are a widely adopted strategic element in the services portfolio, offering flexibility and scalability for both consumer and business solutions. HSNS is for retail service providers, carriers, system integrators and other customers who require a high speed layer 2 access tail service upon which they can build and offer fully managed, point-to-point and multipoint, layer 2 Ethernet and layer 3 services to your end- customers.

1.2. Purpose

This document has been developed to meet the following requirements:

 Provide details of HSNS and its components

 Provide you with product, technical, and service related information, business rules and prerequisites

 Provide possible options for use of HSNS

 Provide information on how HSNS can be used in conjunction with our other input component services.

1.3. About this document

This documentation has been developed by Chorus as a guide line for Service Providers who wish to purchase HSNS in conjunction with other Chorus services. Chorus endeavours to make this document as comprehensive and technically accurate as possible. However it may need to be updated from time to time to include clarifications, errata or additional content. Feedback on the content, technical accuracy or clarity is welcome and should be forwarded through your account manager. Commercial terms and conditions are recorded in the Chorus Ultra-Fast Broadband (UFB) Services Agreement and Wholesale Service Agreement between you and Chorus. Where there is an apparent conflict with contractual documents, the contractual documents apply. This document does not constitute an offer by Chorus to provide HSNS or Ethernet Handover Connections. 2. Overview

HSNS provides a high speed Ethernet access solution that allows you to realise a new level of speed and flexibility in deployment of revenue generating Ethernet-based services. Delivered over our Ethernet platform, HSNS provides an intermediate input service that provides the layer 2 ‘access tail’ component which you can combine with your own network or other services to provide business-grade network services to end-customers. HSNS is available nationally where we’ve deployed Ethernet access based technology. Details of availability criteria and geographic availability are set out in Section 4.1, Geographic availability. HSNS can be combined with our Ethernet handover links and other input services, such as HSNS Tail Extension or Colocation services, to enable you to provide a range of end to end

4 HSNS Product User Guide | July 2017 solutions to your customers. The flexibility of HSNS allows you to customise your customer’s end-to-end solution as desired.

UNI POI

Ethernet Direct Fibre Access Premises HSNS Lite Tail Extension Handover Networking Access-EPL Connection

Co-location HSNS Premium Access-EPL

ICABS/CRT

Third Party Backhaul

Handover links and Commercial Colocation have their own product user guides and are covered by separate agreements. For more detail on each of these additional services please refer to our website or contact your account manager.

2.1. Key benefits

The benefits of HSNS for you are:

 Ability to extend the reach of your networks and services to end-customers using HSNS without having to invest in additional costly access network infrastructure

 A choice of access speeds (1Mbps, 2Mbps, 3Mbps, 5Mbps, 7Mbps, 10Mbps, 100Mbps and 1Gbps) to suit your customer’s requirements and budget.

 Support the delivery of multiple services to your customers.

 The ability to run bandwidth-hungry corporate applications such as enterprise resource planning (ERP), customer relationship management (CRM), host back-up, disaster recovery multi-media and VoIP by offering scalable service bandwidths (from 128kbps to 1Gbps).

 The transmission support of real-time or delay-sensitive applications such as voice or real-time video using dedicated, symmetrical access bandwidth.

 802.1p and 802.1Q transparency enables a more transparent type access capability, which allows you to establish a total service relationship with your customer.

 HSNS provides a standards based layer 2 Ethernet access building block capability that provides the flexibility required by you to build and/or extend your own layer 2 VPN service.

 The Tail Extension feature enables more cost effective backhaul and aggregation of access tails enabling a you full national coverage with a reduced number of handover points.

5 HSNS Product User Guide | July 2017 End User Premises

Internet Service Service Platform Service Provider supplied Provider Customer Edge device Network (CE device) HSNS Data VPN Service Platform

Phone

CE Device Voice Management Service Platform Data / VPN Single Access – Multiple VLANs

VLAN VLAN

VLAN VLAN HSNS Email & Web Access VLAN VLAN

 Being an Ethernet access service, HSNS supports a variety of higher level connectivity protocols. You’re able to connect your own intelligent network devices to a HSNS access tail circuit to create your own layer 3 service (e.g. IP, MPLS, IPX, Decnet or other layer 3 legacy protocols), which they can further enhance by adding service management functionality to create an end-to-end managed layer 3 type solution.

 You can build up a local/regional/national presence to meet your business requirements utilising HSNS where it is available.

 Chorus allocated 802.1ad VLAN labelling at the handover interface to enable easier identification of individual end-customer accesses (i.e. one S-VID is allocated per HSNS access).

 No traffic volumes apply to HSNS billing. HSNS connections are billed on a recurring access speed and service bandwidth charge basis.

2.2. Key features

HSNS feature set

Feature/ HSNS Premium HSNS Lite (fibre) HSNS Lite (copper) capability

Access type Fibre Fibre Copper Access speed 10Mbps – 1Gbps 10Mbps & 100Mbps 1Mbps – 10Mbps options Service bandwidth 128kbps – 1Gbps 128kbps – 100Mbps 128kbps – 10Mbps options Layer 2 control Limited No No protocol support MAC address limit No current limit 20 per access tail 20 per access tail MTU frame size Access end MTU 9096 bytes 1522 bytes 1576 bytes (UNI)

6 HSNS Product User Guide | July 2017 Handover link MTU (ENNI) 9100 bytes 1526 bytes 1580 bytes End-customer Default - media Default - media Default – wires only access termination converter converter Option – jack-point & device Option - glass only Option - glass only wiring (100Mbps and above (100 Mbps only) only) Tail Extension Yes Yes Yes backhaul availability Extended fibre Yes No No availability Symmetrical Yes Yes Yes bandwidth profile High traffic class Yes Yes Yes Low traffic class No No No 802.1p & 802.1Q Yes Yes Yes transparency

2.3. HSNS Premium and UFB

HSNS Premium supports the Bitstream 4 Service Description which is based on the Business Premium service specified in the TCF Ethernet Access Service Description v24, 19 January 2011. HSNS Premium is only considered a UFB service when:

 The Broadband Customer site is located in a Chorus UFB Coverage Area;

 The E-NNI is located at a valid POI for that Chorus UFB Coverage Area;

 The service does not contain non-UFB features including Tail Extension and Logical Diversity

3. How HSNS works

3.1. Product description

HSNS is a layer 2 access tail product that provides an Ethernet-Line (E-Line) service type, with each Operator Virtual Circuit (OVC) being identified by a VLAN ID. Delivered over either copper or fibre access, HSNS provides a transparent 802.1Q and 802.1p Ethernet service between your customer’s site and a defined handover point. Each access tail is defined a single traffic profile. Your interface on the handover link is an 802.1ad interface that supports multiple HSNS service instances, each delivered on a separate S-VLAN with a defined S-VID. Your C-VIDS map directly to the 802.1Q CE-VLAN Id values on the access tail. Where multiple distributed end-customers exist within the same coverage area, HSNS provides the aggregation function and delivers the combined traffic stream over a GbE optical interface to you. HSNS supports the transport of multiple CE-VLANs (with customer defined CE-VIDs) within a single HSNS access. HSNS utilises VLAN stacking technology to enable you to uniquely identify individual end-customer VLANs (associated with each end-customer access) at the handover point.

7 HSNS Product User Guide | July 2017 Designed as an input access product, you can use HSNS as the access component to create and provide high speed network services. Individual HSNS access tails can be stitched together via your network to create point-to-point connections or multipoint networks for your customers, as illustrated in the diagram below.

 HSNS offers six copper access speed options (1Mbps, 2Mbps, 3Mbps 5Mbps, 7Mbps and 10Mbps) as well as three fibre based access speed options (10Mbps, 100Mbps and 1Gbps).

HSNS access speed options

Access 1Mbps 2Mbps 3Mbps 5Mbps 7Mbps 10Mbps 100Mbps 1Gbps type Copper • • • • • • access Fibre • • • access

HSNS uses OVCs through the local aggregation network. Each OVC effectively provides a point-to-point connection between an end-customer site and the handover point. Each OVC is configured with a specified single bandwidth profile (referred to as service bandwidth). Service bandwidth is available in a range of values as detailed in the table below.

128 256 512 1 2 3 5 7 10 15 20 kbps kbps kbps Mbps Mbps Mbps Mbps Mbps Mbps Mbps Mbps 30 50 70 100 150 200 300 500 700 1 Gbps Mbps Mbps Mbps Mbps Mbps Mbps Mbps Mbps Mbps

HSNS supports the transport of multiple customer edge-defined VLANs (CE-VLANs) across any single HSNS access. You only need to nominate a single value of service bandwidth, sufficient to accommodate the total bandwidth profile requirements of the combined customer VLANs, so long as the value of service bandwidth requested is not larger than the value of access speed (refer to the illustration below).

8 HSNS Product User Guide | July 2017 Single Access – Multiple VLANs

VLAN VLAN

VLAN VLAN HSNS Access VLAN VLAN

Note: Service bandwidth is specified in terms of the Ethernet layer and includes Ethernet overheads, headers etc. For more technical detail regarding this aspect please refer to the HSNS throughput section in Appendix E. HSNS consists of four key components:

 Access from your customer’s premises to the local exchange. The access can be either copper or fibre. Where a fibre access is used, the default service is delivered with a Chorus-supplied media converter (MC) device to terminate the fibre line at the end- customer site. Where a copper access is required the default service is delivered as ‘wires only’ access to the external termination point (ETP) or building demarcation frame at your customer’s premisess3.

 Ethernet access node (EAN) can be either an Alcatel-Lucent 7302 (ISAM) or a 7450 Ethernet device (7450). The larger 7450 configured EAN is a fibre access only access node and typically installed in the more densely populated metro areas. It’s capable of higher access speeds (10Mbps, 100Mbps and 1Gbps). The smaller ISAM based EAN is capable of delivering lower access speeds over copper (1Mbps, 2Mbps, 3Mbps, 5Mbps, 7Mbps, 10Mbps) and those fitted with an FX card are able to offer fibre access of 10Mbps and 100Mbps.

 Ethernet aggregation switch (EAS) that provides the logical aggregation function by effectively combining multiple HSNS access tails (i.e. multiple OVCs) from downstream EAN exchanges and presenting them to you as a single data feed.

 Handover point is the point at which HSNS ends. The handover point facilitates the connection point within a defined geographic coverage area for ‘handover’ of HSNS traffic to you. HSNS requires the use of a Ethernet handover connection (connected to a handover point) to facilitate handing over of local HSNS access tail traffic to you. The diagram below illustrates the network relationship between each of these services and network components.

9 HSNS Product User Guide | July 2017 End User Premise HSNS Lite

ETP 1,2,3,5,7,10M CPE Copper Access Media Converter Fibre Access OFDF EAN 10M, 100M CPE

Fibre Access 100M Glass Only Alcatel Lucent Service Provider OFDF Alcatel Lucent 7450 7302 CPE ISAM

EAN OFDF OFDF

End User Premise

Media Handover Network Node CPE Converter Alcatel Lucent Point 7450 OFDF Fibre Access 10,100,1000M EAN CPE Glass Only Fibre Access OFDF 100,1000M

HSNS Premium

The HSNS boundary extends from the defined service demarcation point at your customer’s site to the optical Ethernet port (facing you) on the designated EAS handover point for the defined Ethernet coverage area. The diagram below illustrates how you and your customer’s network equipment could connect to a HSNS access tail.

Service Provider Ethernet Coverage Area Handover supplied Customer Point Edge (CE) device Access Service Provider CE EAN EAS Network POP

HSNS Handover End Link User Service Demarcation

Service Provider HSNS Service Boundary Network

3.1.1. Ethernet coverage areas HSNS is a national service and defines 44 x Ethernet coverage areas distributed geographically across the country. Each coverage area may vary in size with smaller coverage areas being associated with the more densely populated metro areas and the large coverage areas being associated with less densely populated regional/rural areas. Within each coverage area there are multiple EAN exchanges that are directly connected to end-customer premises that are located within the geographic boundary of the coverage area. HSNS access tail traffic from EANs within the coverage area is aggregated at the one or more Point of Interconnects (POIs) designated for that coverage area and presented for handover to you on an EAS at the handover point. The handover link is presented as a 10GbE or 1GbE optical interface on the EAS.

10 HSNS Product User Guide | July 2017 End EAN Handover Point User within each Coverage Area

EAN

End EAS User EAN

Coverage End EAN EAN User Area #1 EAN

End User EAS

EAN Individual HSNS Coverage EAN access tail circuits Area #2

The geographic spread of POIs and your associated handover points allow you to pick up your HSNS access tail traffic closer to your end-customer location, if required. Appendix I lists the 44 Coverage Areas. For more detail on HSNS coverage areas and associated POIs, please refer to HSNS price calculator on the HSNS page of our website.

3.1.2. Tail Extension Tail extension allows an HSNS OVC to terminate on a Ethernet Handover Connection on a remote POI rather than a local POI. This allows you to provide national HSNS services from a single Ethernet Handover Connection. A single OVC is built from UNI to Ethernet Handover Connection, irrespective of whether the Ethernet Handover Connection is at the local POI or the remote POI. That is, there is no termination of the OVC at the local POI. Tail Extension is not a selected attribute, but inferred based on whether the Handover Mapping is to a local or a remote POI.

3.1.3. End-customer access HSNS offers a choice of copper or fibre access options depending on the service bandwidth requirements of the end-customer.

3.1.4. Copper access The copper access variant of HSNS is delivered via the Alcatel-Lucent 7302 EAN (ISAM) and can support access speeds up to 10Mbps. HSNS utilises the G.SHDSL.bis line protocol standard configured as Ethernet in the first mile (EFM) to deliver individual values of access speed of 1Mbps, 2Mbps, 3Mbps, 5Mbps, 7Mbps and 10Mbps. Depending on the access speed required and the length of the copper access from the EAN to the end-customer premises, the HSNS copper line will be delivered as either 2-wire or 4-wire to the external termination point (ETP) or the building demarcation frame of the end- customer premises. You’re responsible for providing a 2wire/4wire capable G.SHDSL.bis modem to terminate the HSNS copper access.

11 HSNS Product User Guide | July 2017 Service Provider supplied Local G.SHDSL.bis Handover Point modem Building cabling Building Ethernet Ethernet cabling Access Aggregation demarcation Node Node Frame Copper Access Modem ETP EAN EAS GigE End User 2/4 wire

End User Premise

HSNS (over copper) Service Boundary

G.SHDSL.bis is sometimes referred to as enhanced symmetrical high-speed DSL (ESHDSL) standard of ITU.991.2 (also known as G.991.2.bis or E-SHDSL). Being a symmetrical xDSL standard, the access speed is dependent on the line loss (i.e. distance from the Chorus EAN to the end-customer premises). Distance is also limited in order to comply with the New Zealand Copper Local Loop Interference Management Plan (Nov 2007), parts 1, 2 and 3. The table below illustrates the possible access speed versus distance and attenuation loss values.

HSNS access speed Number of copper Attenuation max Maximum reach option wires loss from EAN

1Mbps 2-wire 31db Up to 3.1km 2Mbps 2-wire 19db Up to 2.1km 2Mbps 4-wire 31db Up to 3.3km 3Mbps 4-wire 24db Up to 2.5km 5Mbps 4-wire 15db Up to 1.6km 7Mbps 4-wire 9db Up to 0.9km 10Mbps 4-wire 5db Up to 0.6km

Note: Where the physical location of the end-customer site is within a large multi-level building or a large campus environment, a significant length of building cable could be required. You’re expected to specify the additional distance from the ETP to the end-customer in the OO&T order form.

The default option for HSNS Lite (copper) is access provided without a modem or jackpoint (i.e. ‘wires only’). A reference modem list is provided in Appendix B that identifies a number of G.SHDSL.bis modems that have been tested with a HSNS copper access.

3.1.5. Fibre access HSNS can be delivered over a fibre access for those end-customers who have higher bandwidth requirements, or whose premises is beyond the reach of a suitable copper access delivery for the specific value of access speed required. The HSNS product offers two variants of fibre access: HSNS Premium and HSNS Lite (fibre). HSNS Premium: 10Mbps, 100Mbps and a 1Gbps access speed option and HSNS Lite (fibre): access speeds of either 10Mbps or 100Mbps.

12 HSNS Product User Guide | July 2017 Where a fibre access is used to deliver HSNS, we’ll terminate the fibre access with a Chorus- supplied media converter device that presents the end-customer with an electrical (RJ45) Ethernet interface.

Endend userUser premisessPremise Chorus-supplied fibre demarcation Local splice box handover pointpoint Service ProviderProvider Chorus-supplied SupplieSuppliedd media converter Ethernet Ethernet Network Device device Access Aggregation Node Node Fibre AccessAccess CLNE MC MOFDF CLNE MC MOFDF EAN EAS GbE

End User Single Mode CustomerCustomer fibre cabling

Either you or your customer is responsible for providing a secure environment to house this media converter, as well as the AC power supply to the device.

3.2. EAN Features – HSNS Premium & Lite

HSNS is currently delivered off two different types of EAN1 with each EAN network device having its own characteristics;I larger Alcatel-Lucent 7450 network device (which supports only fibre based, higher access and bandwidth options) is more feature-rich than the smaller 7302 ISAM network device (which supports both copper and fibre delivered access options). This difference in EAN and access type feature capability effectively creates two streams of HSNS: a ‘Premium’ and ‘Lite’ variant of the HSNS product. The relationship is illustrated in the diagram below.

High Speed Network Service (HSNS)

HSNS Lite HSNS Premium Reduced Feature Set Expanded Feature Set

Copper Access Fibre Access Fibre Access

1M, 2M, 3M, 5M, 7M & 10M 10M & 100M 10M, 100M & 1000M Access Speed Options Access Speed Options Access Speed Options

HSNS Lite (copper) has an extensive national coverage available in the majority of exchanges and cabinets across the country (service coverage aligns with the Chorus Ethernet access network rollout). HSNS Lite (fibre) is available in a number of main metro exchanges across

1 As the Chorus Ethernet access network and HSNS service evolve over time the number and type of EAN devices may expand or change.

13 HSNS Product User Guide | July 2017 New Zealand2. HSNS Premium will only be available in the main metro centres where the larger and more feature-rich 7450 equipped EAN exchanges are currently located.

3.3. Customer and Service VLANs

HSNS is designed as a VLAN-based Ethernet line service. Each OVC (i.e. access tail connection) is identified by a service-VLAN-ID, and each OVC can support multiple customer edge VLANs.

3.3.1. Customer VLANs (CE-VLANs) HSNS will support the transport of the following frame types:

 Tagged Ethernet frames

 Priority tagged Ethernet frames (CVID=0)

 Untagged, native Ethernet frames. HSNS provides 802.1Q and 802.1p transparency. You or your customer can configure multiple customer VLANs with your own defined customer VLAN ID numbers (C-VIDs/CE- VIDs) over a single HSNS access. Supported VLAN values are 2 to 4094 inclusive. HSNS does not limit or control VLAN tags used by you or your customer. Either you or your customer can configure as many VLANs as you wish so long as the total of individual VLAN bandwidth requirements is within the value of service bandwidth requested.

3.3.2. Service VLANs (S-VLANs) Traffic from each HSNS access tail is treated as a single logical connection. This logical connection is bound by a single bandwidth profile. HSNS utilises 802.1ad technology to encapsulate the end-customers’ or your defined and configured CE-VIDs within each HSNS access tail, with a second tag layer called the service-VLAN ID (S-VID), thereby enabling easier identification of individual HSNS access tail circuits at the designated handover point. The CE-VID is delivered as a C-VID at the handover. This also prevents CE-VID values from clashing with those from different accesses delivered over the same handover link interface. All data within the S-VID is carried via an MPLS virtual leased line (VLL). We’ll allocate S-VIDs in the range S-VID 2 to 4094. One S-VID is allocated per HSNS access (i.e. per VLL). S-VIDs will be unique per handover link (i.e. per port on a 7450 EAS) within a coverage area. The relationship between the customer VLANs (CE-VLAN) and the service VLANs (S-VLAN) is illustrated in the diagram below.

C-VLAN Handover UNI Transparency Point Customer End User Connection Premise A S-VLANs 1501 X 1501 Y Handover Link HSNS Service Provider POP Site ACCESS

Service End User C-VLAN EAN Bandwidth S-VLAN 1501 X Handover Y C-VLAN Connection X Y Service Provider C-VLAN Network Transparency UNI Customer End User Connection Service Bandwidth Premise B S-VLAN 1502 HSNS EAS ACCESS

S-VLANs End User 1502 A C-VLAN EAN 1502 B A 1502 C B C-VLAN 1502 D C A End User Premise ‘A’ = S-VLAN 1501 D B End User Premise ‘B’ = S-VLAN 1502 C D

2We’ll review the HSNS Lite (fibre) coverage areas regularly to deliver service according to customer demand and capex capability.

14 HSNS Product User Guide | July 2017 3.4. Supported applications

HSNS access service is delivered using uncontended symmetrical bandwidth. Examples of services that could be supported over HSNS are:

 web browsing

 audio streaming

 file transfer

 video streaming

 email

 voice over IP

 video conferencing

 low latency / real-time applications. The service performance is, in part, dependent on the configuration of your equipment, network and backhaul arrangements. Therefore, we don’t warrant that the resulting end-to- end service is suitable for such applications. We do not impose or control QoS on a HSNS local access circuit. However, HSNS will be policed so that the traffic conforms to the subscribed values of access speed and service bandwidth for the service. HSNS will preserve Layer 2 priority values (802.1p) parameters that are applied by you and/or your customer. 802.1p values will be carried transparently across a HSNS access. Traffic not containing the correct service attributes e.g. rate, ethertype, will be discarded.

3.5. Security of customer data path

All Ethernet customer traffic is logically separated using VLANs and MPLS VLLs within our Ethernet access network thereby providing secure logical separation your customer’s traffic within our network. Individual end-customer HSNS traffic connections have no visibility of adjacent end-customer traffic streams.

3.6. MAC addresses

MAC address learning is determined by the capability of the specific network device used at the EAN exchange.

 HSNS Lite: For HSNS delivered off an ISAM i.e. HSNS Lite (copper & fibre), there is a MAC address learning limit of 20.

 HSNS Premium: For HSNS delivered off a 7450 EAN there is no MAC address limit.

3.7. MTU size

Access type Access end MTU (UNI) Handover link MTU (ENNI)

HSNS Premium 9096 9100 HSNS Lite (fibre) 1522 1526 HSNS Lite (copper) 1576 1580

15 HSNS Product User Guide | July 2017 The frame size presented at the handover point interface will contain an additional 4 octets for the additional S-VID tag. It’s your responsibility to check with the modem/router vendor(s) that the chosen CPE conforms to this specification.

3.7.1. HSNS Lite (copper)

Tagged (C-VLAN) Ethernet frame presented to EAN from end user = 1576 bytes

Type Type/ Destination Mac Source Mac TCI Payload CRC x8100 length 2 octs 6 octets 6 octets 2 octs 2 octs 4646 -89781554 octets octets 4 octets

HSNS Lite (Copper)

Tagged (C-VLAN + S-VLAN) Ethernet frame presented at EAS (Handover Point) = 1580 bytes

Type Type Type/ Destination Mac Source Mac TCI TCI Payload CRC x88a8 x8100 length 2 octs 2 octs 6 octets 6 octets 2 octs 2 octs 2 octs 46 --89781554 octets octets 4 octets

PCP CFI VID 110 0 S-VID – unique per tail

3.7.2. HSNS Lite (fibre)

Tagged (C-VLAN) Ethernet frame presented to EAN from end user = 1522 bytes

Type Type/ Destination Mac Source Mac TCI Payload CRC x8100 length 2 octs 6 octets 6 octets 2 octs 2 octs 4646 -89781500 octets octets 4 octets

HSNS Lite (Fibre)

Tagged (C-VLAN + S-VLAN) Ethernet frame presented at EAS (Handover Point) = 1526 bytes

Type Type Type/ Destination Mac Source Mac TCI TCI Payload CRC x88a8 x8100 length 2 octs 2 octs 6 octets 6 octets 2 octs 2 octs 2 octs 46 --89781500 octets octets 4 octets

PCP CFI VID 110 0 S-VID – unique per tail

16 HSNS Product User Guide | July 2017 3.7.3. HSNS Premium

Tagged (C-VLAN) Ethernet frame presented to EAN from end user = 9000 bytes

Type Type/ Destination Mac Source Mac TCI Payload CRC x8100 length 2 octs 6 octets 6 octets 2 octs 2 octs 4646 -89788978 octets octets 4 octets

HSNS Premium

Tagged (C-VLAN + S-VLAN) Ethernet frame presented at EAS (Handover Point) = 9004 bytes

Type Type Type/ Destination Mac Source Mac TCI TCI Payload CRC x88a8 x8100 length 2 octs 2 octs 6 octets 6 octets 2 octs 2 octs 2 octs 46 --89788978 octets octets 4 octets

PCP CFI VID 110 0 S-VID – unique per tail

3.8. Layer 2 control protocols

The manner in which layer 2 control protocols are handled by HSNS is determined by the capability of the specific Ethernet network device installed within the EAN exchange.

 HSNS Lite will discard all layer 2 control protocols.

 HSNS Premium will handle individual layer 2 control protocols in one of a number of ways, depending on the individual protocol being presented.

3.9. Layer 3 control packets

The manner in which layer 3 packets are handled by HSNS is determined by the capability of the specific Ethernet network device installed within the EAN exchange and the type of access medium used to deliver the service.

 HSNS Lite: Layer 3 control packets are rate limited on HSNS Lite (copper and fibre) to 60 packets per second and tested using DHCP traffic. All control packets are separated from data packets and then rate limited on a per access basis. The control packet protocol type depends on the applied forwarding model and can be 802.1x, ARP, RIP, DHCP, IGMP, PPPoE Discovery, PPP LCP, PPP control, and PPP LCP termination acknowledgement.

 HSNS Premium: HSNS fibre accesses are transparent to layer 3 control packets.

3.10. End-customer Interface

The end-customer interface will differ depending on whether a copper or fibre access has been provisioned as part of the HSNS access. Fibre access interface: HSNS fibre access tails are delivered over our Ethernet access network to a Chorus-supplied media converter device sited at the end-customer’s premises as a default. The media converter presents your customer with an electrical Ethernet interface in the form of a RJ45 female jack. The access interface can be 10Mbps, 100Mbps or 1Gbps.

17 HSNS Product User Guide | July 2017 Physical access type Interface standard presented to end-customer

10Mbps fibre RJ45 10BaseT 100Mbps fibre RJ45 100BaseTX 1Gbps fibre RJ45 1000BaseT

The service demarcation between the HSNS fibre access and the end-customer is a single 10/100bT or 1000bT 802.3 and 802.1Q Ethernet port (i.e. the port on the media converter).The ethertype is 8100. The media converter device also allows our assure processes to check the status of the fibre access component of the HSNS circuit (facing the end-customer premises) to verify if it is live in the network, and allows for the transparent pass through of certain you generated diagnostic packets (i.e. ping). The media converter device is physically set to connect at a prescribed access rate (10Mbps, 100Mbps or 1 Gbps) to a port on the EAN designated for HSNS data. For specifications on the media converter for HSNS, see Appendix B for additional interface specifications3. Copper access interface: The wires only copper access is delivered as either 2-wire or 4- wire depending on the access speed requested and the distance from the end-customer premises to the EAN. The service demarcation is at the ETP or the building cabling frame.

Physical access type Interface standard presented to end- customer

Wires only - 2-wire copper G.SHDSL.bis (EFM mode – 2Base-TL) Wires only - 4-wire copper G.SHDSL.bis (EFM mode – 2Base-TL)

As HSNS does not include a modem device with the copper access option, you’re responsible for providing a modem device that is G.SHDSL.bis 2/4wire compatible. For guidance on tested modems please refer to Appendix B, reference modems.

3.11. POI Interface (E-NNI)

HSNS is handed over to you as an Ethernet circuit on an Ethernet Handover Connection located at a local or, if Tail Extension is used, a remote POI. The Ethernet Handover Connection, which forms the External Network to Network (E-NNI) function for the HSNS OVC, comprises a fibre optic physical interface at 1Gbps (GbE) or 10Gbps (GbE). At least one valid local or remote Ethernet Handover Connection is needed before HSNS can be consumed for an HSNS coverage area. The Tail Extension feature allows the entire country to be served from a single Ethernet Handover Connection, subject to bandwidth. The demarcation point between the HSNS circuit and your network is the Ethernet Handover Connection handover point designated for the coverage area. The handover link is presented as a GbE 802.3 E-NNI service provider interface The physical interface will be a single mode optical interface, delivered to your main optical fibre distribution frame (MOFDF). For more information refer to Appendix F, interface options.

3You customer is responsible for supplying AC power to the Chorus-supplied media converter

18 HSNS Product User Guide | July 2017 3.12. Aggregation/handover of traffic

HSNS access extends from the service demarcation point at the end-customer’s premises through our Ethernet access network to a nominated handover point within any given coverage area. Each handover point is a logical demarcation point for a specific coverage area to which HSNS access can be built and then handed over to you via an Ethernet handover link. To facilitate transfer of HSNS traffic at a handover point, you must first have ordered a handover link to the required handover point. A handover link provides connectivity between our network and your network for the purpose of delivering traffic between those networks. An Ethernet handover link can be supplied by us to your POP within the same coverage area as illustrated in the diagram below.

Ethernet HSNS with Copper Access Access Handover Point Node Copper Access Modem ETP EAN Ethernet Service Provider Aggregation POP Node Single Mode End User OFDF Fibre Access OFDF End User Premise Service Provider EAS Network Ethernet Equipment HSNS with Fibre Access Access Node Telecom Exchange

CLNE MC OFDF EAN

End User End User Premise Fibre Access Handover Handover Connection Fibre

HSNS Access Tail Handover Link

Alternatively, you may wish to establish a handover link from your POP site to the handover point utilising your own fibre infrastructure or that of a 3rd party fibre access provider. In this example the handover fibre component (refer to diagram above) is supplied by you (or a 3rd party fibre supplier). Please refer to the handover link product user guide for additional detail on this service.

3.13. Remote handover

If you don’t wish to (or are unable to) collect HSNS traffic from the designated handover point in the local coverage area and would like to transport the HSNS traffic to another handover point in another coverage area (where they have already established a handover link) you may do so in one of the following ways:

 Use the HSNS Tail Extension feature, or

 Provide your own transport, or

 Use 3rd party transport. Where you wishes to extend an HSNS access tail beyond its local handover point to any remote handover point (tier 2 or tier 3 EAS), you can choose to do so by utilising the Tail Extension feature of HSNS.

19 HSNS Product User Guide | July 2017 The HSNS Tail Extension feature can be ordered on a per tail basis. The Tail Extension VLL can terminate at any EAS and will be configured to match the service attributes of the HSNS tail e.g. bandwidth. The Tail Extension feature incurs a service bandwidth charge based on step distance bands B- H.

4. Operational Support

4.1. Geographic availability

HSNS is available where we’ve deployed appropriate Ethernet-based technology that supports HSNS on the terms and conditions of this technical user guide. As HSNS is delivered over our Ethernet access platform, service and coverage will follow the Ethernet platform rollout. For service coverage, please refer to HSNS price calculator on our website customer.chorus.co.nz/hsns-premium or data coverage maps ccm.wialus.co.nz/login, which identifies currently available Ethernet access nodes as well as your associated supported access speed options. Alternatively, contact your account manager for the most up–to-date list of HSNS capable EANs (to facilitate end-customer connection) and associated EAS nodes (to facilitate handover to you).

4.2. HSNS service request types

There are three request types:

 New connection

 Moves, adds and changes

 Relinquish. As a prerequisite, you must have established a handover link to at least one handover point for the handover of HSNS traffic. There are three types of MACs supported

20 HSNS Product User Guide | July 2017

Technical attribute Attribute definition

Simple No truck roll required (i.e. work activity does not require a technician to be despatched to your customer’s site or our exchange). Work requires simple ‘logical’ changes only to circuit configuration and/or circuit records. Standard Truck roll / on-site implementation required No network build activity required Complex A truck roll MAC that is technically difficult or can’t be completed within standard timescales Network build required. We’re agreeing on a completion date that includes multiple requests submitted at the same time, or bulk requests involving project type work.

Note: Bulk requests shall be actioned as a project activity and managed using our managed provisioning service. This would be treated as a complex MAC request. A bulk request is defined as more than 5 MAC requests. Examples of typical MAC types and associated price structures are detailed in the table below:

MAC Description MAC Variations MAC Type

Access speed You request an upgrade or No equipment changes Simple change downgrade of the access speed, or No truck roll required access speed change is required as part of a service bandwidth change Access mechanism Standard request changes

Network changes N/A (RQ/NC) required to achieve new access speed

Service You request a service bandwidth No equipment changes Simple bandwidth upgrade or downgrade within the No truck roll required change existing same access speed Access mechanism Standard changes

Move - You request a relocation of a HSNS No speed change or Simple internal access tail service demarcation cabling required point within the same end-customer site Work includes an Standard Access Speed or Service Bandwidth change

Building cabling or Complex associated network changes required

Handover You request an existing HSNS No speed change or Simple point access tail to be remapped to a cabling required

21 HSNS Product User Guide | July 2017 remapping different local or remote handover Work includes an Standard point access speed or service

bandwidth change

Example #1:

Any access speed change (upgrade or downgrade) that requires installation of additional copper or fibre access lines will be treated as relinquishment and new connect. It will attract charges comparable to the appropriate installation rate. This also applies to changes in service bandwidth that necessitate a change to the associated access speed. A couple of possible examples to illustrate this are described below:

 You request an access speed upgrade of your copper access from 2Mbps to 5Mbps. This request will require a new connect 4-wire HSNS copper access to be installed in parallel to the existing 2-wire HSNS access circuit pair (to reduce service interruption to your customer). Once the new 4-wire HSNS access line has been installed and tested you liaise with your customer to co-ordinate the cut-over of your service to the new HSNS access and subsequently submit an RQ request for the 2-wire circuit.

 You request an increase of your service bandwidth from 50Mbps to 150Mbps. This change in bandwidth will necessitate an upgrade of the fibre based access speed from the existing single-fibre 100Mbps access to a dual fibre 1Gbp fibre access. The new 1Gbps dual fibre access line and associated dual fibre media converter will be installed in parallel to the existing single fibre 100Mbps HSNS access circuit and single-fibre media converter (to help reduce service interruption for your customer). Once the new dual-fibre HSNS access line and media converter have been installed and tested you liaise with your customer to co-ordinate the cut-over of your service to the new HSNS access and associated service bandwidth and subsequently submit an RQ request for the single fibre access. The examples described above will also apply to a speed downgrade (i.e. 4-wire to 2-wire copper or a dual fibre to single fibre access line change).

Example #2:

Any external removal from one physical premises to another premises (i.e. different building) will be treated as a relinquishment of the existing HSNS access tail and a new connection to the other end-customer premises. The new HSNS access will be provisioned as per current HSNS new connection process and charged at the appropriate new connection installation rate. Once the new HSNS access has been installed and tested, you will liaise with your customer and co-ordinate the cut-over of the service to the new HSNS access and associated service bandwidth and subsequently submit an RQ request for the old HSNS access.

4.3. Speed upgrades

Speed upgrades or downgrades can be ordered as a MAC request. Where a speed upgrade request necessitates an upgrade of the access, this will be classed as a relinquishment (RQ)/ New Connect (NC). Speed upgrades that do not require an additional access build will be treated as a simple MAC and charged at the simple MAC rate.

4.4. Access installation & testing

22 HSNS Product User Guide | July 2017 4.4.1. Copper access installs External termination po–nt - The ETP is the external termination point for copper based HSNS services to your customer’s premises. Where there is no termination point external to the premises, it is either the first data jack on the premises wiring or the building distribution frame. Where HSNS is delivered over copper, the access is presented as ‘wires only’ to the ETP as default. This effectively becomes the HSNS demarcation point. Any internal building cabling used to extend HSNS beyond the HSNS demarcation point to another location, within the same premises, is the responsibility of you or your customer. Ownership and ongoing maintenance of internal building cabling is the responsibility of you or your customer.

End User Premises

Service Provider supplied Internal Customer edge (CE) device Building (G.SHDSL.bis modem) Cabling ETP HSNS Copper Access EAN

HSNS Service End User Demarcation

HSNS Service Boundary HSNS over Copper

We’ll test the HSNS copper access (using a test modem) from the HSNS demarcation point back into our network. Once the access commissioning test has been completed the test modem is removed and you’re advised of the test completion via OO&T.

4.4.2. Fibre access installs Where HSNS is delivered over a fibre access, we’ll deliver fibre to your customer’s building and terminate the cable on a Chorus-supplied MOFDF (fibre splice box) within a suitable location within the building. The Chorus MOFDF acts as a Chorus fibre demarcation point. The HSNS fibre access is terminated with a Chorus-supplied media converter which in turn will be connected to the Chorus MOFDF as illustrated in the diagram below. Once the fibre cabling is completed one of our technicians will initiate a test of the fibre access from the media converter back into our network. 4

4 A glass only option is also available; please refer to Appendix D for more information.

23 HSNS Product User Guide | July 2017

4.4.3. Testing to your network

HSNS variant Service test performed

Lite (copper) Traffic flood test Lite (fibre) Layer 1 test of optical fibre and connectivity testing of layer 2 to EAN port Premium Layer 1 test of optical fibre and connectivity testing of layer 2 to EAN port

4.5. Churn / reassignment

It is not possible for you to transfer/ churn to HSNS from any other service – retail or unbundled. Existing circuit connections must be relinquished and an HSNS access requested.

4.6. Faults

You must conduct an initial fault diagnosis to establish that the fault is not within your responsibility prior to reporting the fault to us. You’re responsible for repair of any fault within your network. HSNS faults must be reported to us via Online Fault Management (OFM) system. We’ll diagnose and repair any faults in our network. Once a fault has been resolved by our faults team, the OFM fault ticket details will be updated and the fault closed. You can view the status of the fault at any time through OFM. Below is a diagram illustrating types of faults that customers may experience on a HSNS tail, and identifying you responsibilities.

24 HSNS Product User Guide | July 2017 HSNS Fault (service provider testing pre-requisites)

Circuit down? Circuit intermittent? Circuit is slow?

If Layer 1 down: If Intermittent: If slow circuit:

1. Is the CPE using a 1. Check the CPE 1. Check the CPE port g.SHDSL.bis cables and reset the is configured to the interface? power to the CPE contracted value of 2. If CPE is configured 2. Check that the CPE is service bandwidth correctly then try a configured correctly (i.e. ensure rate power reset and if okay then try shaping is set up a power reset. correctly on port) 3. Log an OFM ticket 2. Reset power to CPE and include precise 3. Log an OFM ticket If Layer 2 down: information about and include precise the fault information about 1. Check and validate the fault including CPE configuration value of latency is correct being experienced 2. Is the sub-interface configured on the network handover? 3. Log an OFM ticket and include precise information about the fault

Support level Accountability Support provided

Tier 1 You Provide initial diagnostics and only refer the fault to tier 2 when fault is proven to be within the our network. Tier 2 Chorus service BAU first response to you for network faults, and support dispatch of field service company. Tier 3 Chorus network BAU second response options for escalated single or vendor multiple you/end-customer faults indicating a (Alcatel-Lucent) potential common network infrastructure issues. Tier 3 Chorus service BAU support for physical equipment restoration. (on-site) companies

Charges may be applied for unnecessary site visits or cancellations. An example would be where one of our service technicians makes a site visit (end-customer, your site or Chorus exchange), to attend a fault, and there is no fault in our network. In this instance you may be charged a ‘diagnosis –eg - no fault found’ charge. Should a you log a fault relating to dropped packets and we determine the discarded traffic is a result of you sending traffic in excess of the value of the service bandwidth rate associated

25 HSNS Product User Guide | July 2017 with the HSNS access tail purchased, then a one-off ‘diagnosis fee - no fault found’ charge may be levied against your account. HSNS is offered as a non-managed layer 2 access tail service. It’s not an end-to-end managed service and doesn’t provide real-time monitoring of individual HSNS access tail connections.

4.7. Billing

Where the provision for electronic billing (ebill) exists for you, the billing details for HSNS will be presented on your ebill. Each HSNS access tail connection will be identified on the invoice by its unique service identifier number (IDA number). Each charge line is comprised of:

 Service Identifier

 Physical address of end-customer premises

 Chorus order/fault reference

 Charge description

 Date actioned and period covered

 Charge amount. The recurring service charges associated with each HSNS access tail connection will identify the value of access speed (including the access zone) and the associated service bandwidth requested. Handover link, Tail Extension and other services will be listed separately and billed as separate services. Any billing enquires should be advised to your billing representative or your account manager.

4.8. Pricing

The HSNS access service price components are:

 Access speed

 Service bandwidth

 Installation fee

 Moves, adds and changes fees. HSNS access speed will be charged as a recurring monthly access fee, to be paid in advance. The HSNS access speed component utilises de-averaged pricing with each access speed option being broken down further into six associated access zone classification steps (CBD, metro, urban, C, D & E).

Access speed Access type Zone 1 Mbps Copper CBD Metro Urban C D E 2 Mbps Copper CBD Metro Urban C D E 3 Mbps Copper CBD Metro Urban C D E 5 Mbps Copper CBD Metro Urban C D E 7 Mbps Copper CBD Metro Urban C D E 10 Mbps Copper CBD Metro Urban C D E 10 Mbps Fibre CBD Metro Urban C D E

26 HSNS Product User Guide | July 2017 100 Mbps Fibre CBD Metro Urban C D E 1 Gbps Fibre CBD Metro Urban C D E

Installation charges will be applied as a one-off fee. MAC fees will be applied as a one-off fee. A HSNS pricing calculator is available for you to download and is available on our website. 5. Glossary

Term Description

Access tail The logical point-to-point connection between the MC device at the end-customer site and your facing port on the EAS node. Access zone Access pricing is de-averaged into six groups (CBD, metro, urban, classification C, D, E); each EAN is assigned an access zone - CBD, Metro, Urban, C, D, E. The classification system works so that the lowest cost EANs are classified CBD and the highest cost Group E. Coverage A geographic region defined by network design which groups area together a number of EAN exchanges which are served by a single EAS. A coverage area is also defined as a defined Ethernet catchment area within which a HSNS access tail circuit can be deployed. CE Customer edge Customer edge device (typically a router supplied by you) sited at the edge of the customer network at the end-customer premises. C-VID Customer associated VLAN ID number is the VLAN ID (inner-tag) number associated with the end-customer site access. CE-VID Customer end VLAN ID, 0 to 4095. VLAN identifier stored in the 802.1q tag at the UNI. EAN Ethernet access node An Ethernet capable exchange site to which an end-customer fibre access (HSNS access tail) connects directly. EAS Ethernet aggregation switch An Ethernet node which has been configured as an aggregation device. The EAS aggregates traffic from multiple HSNS access tail circuits within a common coverage area. An EAS site is associated with each coverage area. Egress The point where traffic is delivered to the end-customer from the Chorus-supplied media converter, as well as traffic delivered to you from the port on the EAS End-customer A customer of a you who uses services, which have been provided to them by you. This entity is billed by you Handover link A fibre connection between the handover point and your POP for the purpose of handing over traffic for unbundled services. Handover The location where aggregated HSNS access tail circuits in a point coverage area are presented for transport to you via a handover link. HSNS High Speed Network Service

27 HSNS Product User Guide | July 2017 A Chorus service product which offers a high speed, layer 2 Ethernet access tail circuit. Layer 2 Layer 2 is the data level in open systems interconnection (OSI) 7- layer model. In very basic terms: layer 1 is the physical cable connection; layer 2 adds transmission error detection, while layer 3 adds packet routing/error correction/congestion control. Layer 3 The network Layer is the third layer of the OSI model. Layer 3 is responsible for end-to-end (source to destination) packet delivery, whereas layer 2 is responsible for node to node delivery. Layer 3 is typically associated with routing. Layer 3 services are often referred to as ‘managed services’. L2 MPLS VPN A layer 2 MPLS VPN also known as a L2VPN is a point-to-point pseudo-wire service which defines methods to transport layer 2 packets across MPLS networks. It can be used to replace existing physical links. MACs Moves, adds and changes to a end-customer/your existing installation. These are also referred to as change requests. MEF Metro Ethernet Forum. An international standards body that defines technical specifications and Ethernet service attributes for Ethernet based services MC Media converter Copper-to-optical converters provide a transparent Ethernet link between copper medium and fibre-optic medium. These devices convert and forward Ethernet frames from electrical signals to fibre signals and vice versa. MPLS Multiprotocol label switching MPLS is a data carrying mechanism that belongs to the family of packet-switched networks. MPLS operates at an OSI layer model layer that is generally considered to lie between traditional definitions of layer 2 (data link layer) and layer 3 (network layer), and therefore is often referred to as a layer 2.5 protocol. MPLS can be used to carry many different types of traffic, including IP packets, as well as native ATM, SONET and Ethernet frames. MPLS can be used to create L2VPN and L3VPN solutions. A layer 2 MPLS VPN also known as a L2VPN is a point-to-point pseudo-wire service which defines methods to transport layer 2 packets across MPLS networks. It can be used to replace existing physical links. OFM Online fault management OFM is an online system for the logging and tracking of faults. OO&T Online ordering & tracking OO&T is an online system for logging service requests and tracking your progress. OVC Operator virtual connection. A metro Ethernet forum defined Ethernet private line that associates an UNI to an ENNI with appropriate QoS characteristics. PE Provider edge Provider edge router at the edge of you network. POP Point of presence Physical location of your network equipment.

28 HSNS Product User Guide | July 2017 QinQ Queue in queue A methodology of encapsulating IEEE8021.Q VLAN tags within 802.1Q. QinQ allows a you to expand the VLAN space by tagging the tagged packets thus producing a double tagged frame. Uses C- VLAN and S-VLAN ID tags. QoS Quality of service QoS is the ability of a network to deliver a predetermined level of performance to an application or a class or group of applications. SLA Service level agreement A contract between you and a customer that specifies, usually in measurable terms, what services the network you will furnish. SDR Sustained data rate (throughput) The maximum average data rate (in kilobits per sec) for a given packet size that can be sustained across an access circuit. S-VID You VLAN-ID number The VLAN ID (outer-tag) number that is associated with you. S-VID is used with QinQ. Tail Extension An optional HSNS service feature that extends the HSNS handover point from the local coverage area to any other EAS equipped exchange on a per tail basis. Truck roll Refers to an engineer or field service representative making a physical visit to a site to make alterations to the network or service. VLAN Virtual local area network A logical group of network devices that appear to be in the same LAN, regardless of your physical location. With regard to HSNS; a VLAN will allow a certain portion of traffic to be isolated from the rest of the traffic in the access tail or in other VLANs within the same access tail. VLAN ID A 12 bit field specifying the VLAN to which a frame belongs. (VID) VLL Virtual leased line VLL is a way to provide Ethernet-based point-to-point communication over MPLS/IP networks. In the industry, the technology is also referred to as virtual private wire service (VPWS) or EoMPLS (Ethernet over MPLS). VLL uses the pseudo-wire encapsulation for transporting Ethernet traffic over an MPLS tunnel across an IP/MPLS network. VoIP Voice over internet protocol This is the routing of voice conversations over the Internet or through any other IP-based network. VPN Virtual private network A VPN is a communications network tunnelled through another network, and typically dedicated for a specific network. Generally, a VPN has a topology more complex that a point-to-point connection. 802.3 Is a collection of IEEE standards defining the physical layer and the media access control (MAC) sub layer of the data link layer of wired Ethernet. This is generally a LAN technology with same WAN applications. Physical connections are made between nodes and/or infrastructure devices (hubs, switches, routers) by various type of

29 HSNS Product User Guide | July 2017 copper or fibre cable. 802.3 is a technology that can support the IEEE 802.1 network architecture. 802.1Q Refers to 802.1Q-2005 - an IEEE 802 standard that defines the mechanism that allows multiple bridged networks to transparently share the same physical network link without leakage of information between networks. It is also defines the meaning of the term virtual LAN (VLAN) which is an encapsulation protocol for VLAN tagging. Associated with Ether type value in the SNAP header which is set to hex 8100. 802.1ad A form of double tagging or nested VLAN tagging similar to Q in Q. It is used by you because it allows you to use VLANs internally while mixing traffic from your clients that are already VLAN-tagged. This standard defines Ether type 88a8 for your ‘outer-tags’.

30 HSNS Product User Guide | July 2017 Appendix A Layer 2 control protocol handling

Premium and Lite service variants of HSNS will treat layer 2 control protocols in the manner as detailed in the following table. The HSNS Lite service variant (7302 EAN) will discard Ethernet control frames identified by the following MAC destination address.

 01-80-C2-00-00-0X

 01-80-C2-00-00-10

 01-80-C2-00-00-2X This includes the following protocols:

Layer 2 control protocol MAC DA HSNS Lite HSNS Premium (7302 EAN) (7450 EAN)

STP/RSTP IEEE 802.1D-2004, ‘Part 3: 01-80-C2- Discard Transparently media access control (MAC) bridges’ 00-000-00 forwarded MSTP IEEE 802.1Q-2005, ‘virtual bridged local area networks’ PAUSE IEEE 802.3-2005, ‘Part 3: 01-80-C2- Discard Tunnel if tagged Carrier sense multiple access with 00-000-01 collision detection (CSMA/CD) access method and physical layer specifications’ LACP/LAMP IEEE 802.3-2005, ‘Part 3: 01-80-C2- Discard Tunnel if tagged Carrier sense multiple access with 00-000-02 collision detection (CSMA/CD) access method and physical layer specifications’ Link OAM IEEE 802.1X-2005, ‘Part 3: 01-80-C2- Discard Tunnel if tagged Carrier sense multiple access with 00-000-02 collision detection (CSMA/CD) access method and physical layer specifications’ Port Authentication IEEE 802.1X-2004, 01-80-C2- Discard Tunnel if tagged ‘Port-Based Network Access Control’ 00-000-03 E-LMI MEF Technical Specification MEF 01-80-C2- Discard Discard 16, ‘ Ethernet Local Management 00-000-07 Interface’’ January 2006 LLDP IEEE 802.1AB-2005, ‘Station and 01-80-C2- Discard Discard Media Access Control, Connectivity 00-000-0E Discovery’ GARP IEEE 802.1Q-2004, ‘Virtual 01-80-C2- Discard Tunnel Bridged Local area Networks’ 00-000-20 MRP Block IEEE 802.1ak-2007, ‘Virtual through Bridged Local Area Networks, 01-80-C2- Amendment 07: Multiple Registration 00-00-2F Protocol’

CFM frame identified by an ethertype of 0x8902 will be discarded by HSNS Lite.

31 HSNS Product User Guide | July 2017 Appendix B Reference modems & end-customer equipment requirements

B.1 System elements The copper access variant of HSNS utilises a G.SHDSL.bis line protocol to deliver up to 10Mbps of symmetrical bandwidth over a 2-wire or 4-wire copper line. HSNS does not include a modem with the copper access option and, instead, offers you the flexibility to choose your own 2/4 wire capable G.SHDSL.bis modem to suit the requirements of the service you’re delivering to your end-customer. As the G.SHDSL.bis is a relatively new symmetrical xDSL standard, we created a reference list of 2/4 wire capable G.SHDSL.bis modems (with associated specific hardware revision and software/firmware version) that we’ve tested on a HSNS copper access. We will not test every G.SHDSL.bis capable modem available on the market, however we’ve tested a limited number of modems to confirm that they will work with a HSNS copper access. The table below identifies the modems that have been tested with HSNS Lite (copper) accesses.

Modem Model Firmware/Software Revision

Thomson ST620s R8.2.1.4 Thomson GT605s R8.2.3.A Nokia-Siemens FlexiNT22 Software: P80100.01_00_PRE FPGA Ver: 9A, Hardware: E80001.01-05 RAD LA-210 Rev 1.53 Cisco 888E IOS Software: 15.1(1)T minimum. You’re free to choose other G.SHDSL.bis modems (not included in the HSNS reference modem list) to terminate a HSNS copper access. Any G.SHDSL.bis modem device connected to our access network must be Telepermit certified. Please check with your G.SHDSL.bis modem vendor.

B.1.1 End-customer equipment requirements

Yous must make your own arrangements with end-customers for the purchase and installation of all required CPE and wiring to use HSNS. You or your end-customer must ensure that all equipment directly connected to a HSNS access tail (fibre or copper) adheres to Telepermit requirements. A list of Telepermitted equipment is available at www.telepermit.co.nz. Where HSNS access is delivered via a fibre access either you or your customer is responsible for supplying AC power to the Chorus-supplied media converter. You or your customer are also responsible for providing a secure environment to house the media converter. The technical specifications for the Chorus-supplied media converter are detailed below:

32 HSNS Product User Guide | July 2017

Power Characteristics:

 Power pack: Input voltage: 100-240 VAC, 50-60 Hz

 Power pack: Output power rating 12 watts12VDC @ 1.5A

 Media converter max power consumption: 12Watts. Physical:

 Dimensions: 98mm (W) x 25mm (H) x 140 (D)

 Weight: 370gm. Environmental:

 Operating Temp: 0°C to 50°C

 Storage Temp: -20°C to 85°C

 Operating relative humidity: 10 to 90% non-condensing. Reliability:

 MTBF: 133 000 hrs. Hardware Features:

 1 x electrical Ethernet RJ45 port (10/100bT or GbE)

 1 x single mode optical (10/100bT or GbE).

33 HSNS Product User Guide | July 2017 Appendix C Jack-point and wiring and modem options for HSNS Lite (copper)

C.1 Jack-point and wiring purchase option The default access installation for HSNS Lite (copper) is ‘wires only’, however you can request a jack-point to be installed at your customer’s site by requesting the ‘wiring and jack-point’ option on the customer order in OO&T. An RJ-45 jack-point will be installed where Cat5/3 cabling exists,  The HSNS Lite (copper) service demarcation will not change where a wiring and jack-point installation service is installed;  Responsibility for maintenance of HSNS Lite (copper) within the end-customer’s premises will remain with you; If our technician deems the cable onsite as being unsuitable for carrying out the jack-point installation, we will let you know and there will be no additional charge.

C.2 Jack-point and wiring technical specification All wiring and jack-point installed in conjunction with a HSNS Lite (copper) installation will be installed as per the T-568A specification.

It is recommended that you liaise with your CPE vendor to ensure that the cable supplied with your CPE is configured to match the T-568A standard. If your selected CPE requires a different pin-out (i.e. RJ11) to that specified under T568A, an easy solution is to procure a cross over cable.

34 HSNS Product User Guide | July 2017

35 HSNS Product User Guide | July 2017 Appendix D HSNS termination options

D.1 HSNS Lite (fibre) glass only option HSNS Lite (fibre) access has the option for the end-customer interface to be presented without the default Chorus-supplied media converter and instead be presented as a single fibre ‘glass only’ interface. This is illustrated in the diagram below.

HSNS Lite …(fibre) – -Glass Only option Only Interface Presentation

End User premisess Chorus Exchange

AlcatAlcatelel - Lucent Seservicervice providerProvider Chorus 7302 ISAM Suppliedsupplied Fibre 100 Mbps CE DeviceDevice & SFPSFP Splice Box FibreFibre AccessAccess

EAN MOFDF Endend userUser

Given that there is no IEEE standard for 10Mbps optical the HSNS ‘glass only’ option is only available with a 100Mbps access for HSNS Lite (fibre).

HSNS Lite (fibre) glass only options

Fibre connector types Single optical connector LC or SC Physical options 100BASE-BX10 (single fibre)

IMPORTANT TECHNICAL NOTE: As the 100BASE-BX10 is a single fibre IEEE standard the transmit (TX) and receive (RX) optical wavelengths will transit the same physical fibre strand meaning that TX and RX wavelength values will be transposed at either end of the fibre link thus the optical port at each end must be terminated with the correct type of bidirectional optical SFP device as illustrated in the diagram below.

36 HSNS Product User Guide | July 2017 100BASE-BX SFP type required for glass-only option:

D.1.1 SFP specifications for end-customer site:

Our EAN optical port will be fitted with a BX-D type SFP and the CE device you’ve supplied at your customer’s end of the HSNS Lite (fibre) access must use a BX-U type SFP as illustrated in the diagram above. You’re responsible for sourcing and supplying your own 100BASE BX-U type SFP device.

As with all fibre access requests, a manual fibre feasibility will be required and we will identify the estimated optical line loss to aid you in sourcing the correct type of 100BASE-BX type SFP.

When configuring a glass only connection for HSNS Lite (fibre), you’re required to ensure that the optical equipment has a transmit power range (minimum TX power to maximum TX power) and receive sensitivity range (minimum RX power to maximum RX power) that fits within the following parameters.

HSNS Lite (fibre) glass only SFP specification parameters for end-customer site

Loss SFP Type Min TX Max TX Min RX Max RX Chorus range pwr part pwr (dBm) pwr pwr (dBm) (dBm) (dBm) (dBm) number

0-11 100Base-BX -14 -8 -28 -8 3FE29195AA single mode, 1310TX, 1550RX, 10km

Note * the value quoted for the loss range includes a 3dB margin. We have listed the Alcatel SFP part number that is complementary to the one we’ll be using within our network.

37 HSNS Product User Guide | July 2017

D.1.2 Testing:

Once installation is completed, technicians will perform a traffic test to confirm that the circuit is working. Please note this test does not test from your CPE.

D.2 HSNS Premium glass only option HSNS Premium access has the option for the end-customer interface be presented without the default Chorus-supplied media converter and instead be presented as a dual fibre ‘glass only’ interface.

HSNS Premium … Glass-Only Interface Presentation

Telecom Exchange End User Premise

Alcatel-Lucent Service Provider Telecom 7450 Supplied Fibre 100 or 1000Mbps CE Device & SFP Splice Box Fibre Access

EAN OFDF End User

Given that there is no IEEE standard for 10M optical the HSNS ‘glass only’ option is only available with 100Mbps and 1000Mbps accesses for HSNS Premium.

HSNS Premium Glass Only Options Fibre connector types Single optical connectors with LC or SC

Physical options 1000Base-BX (1GbE single fibre)

The end-customer demarcation will be dual optical connectors with LC or SC as connector options.

As with all fibre access requests, a manual prequalification will be required and we’ll identify the estimated optical line loss to aid you in sourcing the correct SFP type. When configuring a glass only connection for HSNS Premium, you are required to ensure that the optical equipment has a transmit power range (minimum TX power to maximum TX power) and receive sensitivity range (minimum RX power to maximum RX power) that fits within the following parameters.

38 HSNS Product User Guide | July 2017

HSNS Premium Glass Only 1000BX SFP Specification parameters for end- customer site

Loss SFP type Min TX Max TX Min RX Max RX Chorus range pwr part pwr (dBm) pwr pwr (dBm) (dBm) (dBm) (dBm) number

0 -6.7 1000Base- -9 -3 -18.7 -3 3HE0086 BX10-U 8CA single mode, TX 1310nm, RX 1490nm, 10km 0-4.5 1000BASE- -11.5 -3 -19 -3 3HE0002 LX* 8 Single Mode, AA 1310nm, 10km 3 – 16 1000Base- -5 0 -24 -3 3HE0432 BX40-U 4AA single mode, TX 1310nm, RX 1490nm, 40km * 1000BASE-LX is for dual fibre installs, which are normally limited to same-building installations. The value quoted for the loss range includes a 3dB margin. We have listed the Alcatel SFP part number that we’ll be using within our network. As with all fibre access requests, a manual fibre prequalification will be required and we’ll identify the estimated optical line loss to aid you in sourcing the correct type of SFP.

HSNS Premium glass only 100FX SFP specification parameters for end-customer site

Loss SFP type Min TX Max TX Min RX Max RX Chorus range pwr part pwr (dBm) pwr pwr (dBm) (dBm) (dBm) (dBm) number 0-13 100Base-FX -15 -8 -31 -8 CFETF1014- 205 Rev G single mode,

1310, 20km

13-23 100Base-FX -8 -2 -34 -7 CFETF1015- 205 Rev G single mode,

39 HSNS Product User Guide | July 2017 1310, 40km

Note * the value quoted for the ‘Loss Range’ includes a 3dB Margin.

We have listed the Transition Networks media convertor part number that we’ll be using within our network. As with all fibre access requests, manual fibre prequalification will be required and we’ll identify the estimated optical line loss to aid you in sourcing the correct type of SFP. D.2.1 Testing:

Once installation is completed, technicians will perform a traffic test to confirm that the circuit is working. Please note this test does not test from your CPE.

40 HSNS Product User Guide | July 2017 Appendix E Service level targets

Service level targets for faults and provisioning are detailed in the Service Level Agreement and Operations Manual. These service specifications are design targets only and should be used by you when developing end-to-end solutions. HSNS however will likely only form a small part of any such end-to-end solution. Actual performance is not guaranteed as it is subject to external influence. Service levels set out in this appendix are targets only. Technical attributes of HSNS are characterised by the key components shown below. E.1.1 HSNS availability

Definition: HSNS is available for use by end-customers and functioning in accordance with the service description.

An HSNS access tail circuit is deemed unavailable when no data can pass to or from the end- customer site during agreed service hours, unless the outage was a planned outage, a force majeure event, or a failure arising on the end-customer side of the HSNS access demarcation point or on your side of the handover point.

HSNS availability service target

Metro 99.7%

Rural 99.5% Note: Availability figure based on 7x7x7 service hours over a year (7am -7pm per day over 365 days).

E.1.2 Agreed service hours

For HSNS the default service hours are 7am – 7pm x 7 days a week E.1.3 Geographic areas

For HSNS these are defined as follows:

Geographic areas New Zealand locations

Metro Within 30 kilometres of the centre of Auckland, Hamilton, Rotorua, Tauranga, New Plymouth, Napier, Wellington, Palmerston North, Nelson, Christchurch and Dunedin

Rural All other New Zealand locations

E.1.4 Service restoration

Definition: The elapsed time during agreed service hours between call reception and the customer being notified that service is restored to the defined levels as a result of a site visit.

The HSNS service restoration target is < 6 Hours.

41 HSNS Product User Guide | July 2017 E.1.5 HSNS throughput

Technical attribute Attribute definition Performance target

Throughput rates The maximum sustained data rate (SDR) 128kbps to 1Gbps achievable through a HSNS access tail (applicable for HSNS, service connection between the service demarcation bandwidth configuration) point at the end-customer premises (ETP for copper access or the electrical Ethernet port on the media converter facing the end- customer) to the handover point (facing you), and includes all transmission overheads and headers as well as end-customer/you data.

HSNS throughput is limited by two factors: service bandwidth and access speed. The maximum throughput achievable through an HSNS access is dependent on the access speed and the Ethernet frame size. Access speeds are defined in terms of layer 1 (physical interface). When Ethernet frames are transmitted over a physical interface, additional overheads are added by the interface. Ethernet devices must also allow a minimum idle period between transmissions of Ethernet frames, known as inter frame gap (IFG). This provides a minimum recovery time between frames to allow Ethernet devices to prepare for reception of the following frame. The minimum IFG gap is 96 bits (12Bytes) which equates to 960 nanoseconds for fast Ethernet (i.e. 100Mbps). Furthermore, before sending an Ethernet frame, the preamble and start frame delimiter (SFD) must be sent for clock synchronization and to inform a reception device that a frame is about to be transmitted. The preamble and SFD payload sizes are 7Bytes and 1Byte, which consist of fixed patterns, 0x55 and 0xD5 respectively. Therefore, total Ethernet overhead for a single MAC frame is 20Bytes and is made up of the following:

 7Bytes of preamble

 1Byte of SFD

 12Bytes of IFG This implies that each single Ethernet frame has 20Bytes of overhead. This overhead is more significant for small Ethernet frame sizes (minimum Ethernet frame size is 64Bytes) as can be seen in the graph at the bottom of the page. As a frame size increases the overhead factor becomes less significant. When small Ethernet frames are transmitted from the end-customer/you, this overhead is significant. A 64Bytes Ethernet Frame is equal to 64+20=84Bytes on the wire, which leads to a 31.25% overhead. For larger Ethernet frames, the impact is minimal. A 1518Byte Ethernet frame is equal to 1518+20=1538Bytes on wire which leads to a 1.3% overhead. This means that the Ethernet frame size as transmitted by either the end-customer/you has a direct influence on the throughput efficiency. Example: For a fast Ethernet interface, the physical line rate is 100Mb/s, and if the Ethernet frame size of the traffic is 64 bytes, then the maximum achievable throughput will be 76Mb/s. You need to take this into account when selecting access speeds and service bandwidths. Any layer 3 payload is further encapsulated by an Ethernet MAC layer, and depending on the Ethernet encapsulation used, additional overhead for layer 3 data may also slightly change.

42 HSNS Product User Guide | July 2017 Standard ethernet overhead for an IP packet is 18Bytes (4Bytes DMAC, 4Bytes SMAC, 2Bytes type, and 4Bytes FCS, exclusive of Preamble, SFD and IFG). When 802.1Q S-VID tagging is used, overhead increases to 22Bytes. The graph illustrated below gives a high level appreciation of L2/3 efficiencies based around the requirement to allow for preamble, IFG, SFD etc.

100% 90% 80% General Ethernet Efficiency 70% 60% Layer 3 Throughput - 50% Untagged Traffic 40% L3 Throughput - Single 30% Tagged Traffic 20% 10% 0%

64 256 448 640 832 1024 1216 1408 1526

HSNS will limit traffic (i.e. discard excess traffic) at both the aggregate level and at the end- customer to the stated service bandwidth. Yous need to pace (i.e. rate shape) traffic on a per service bandwidth basis. When such traffic is discarded, functional throughput performance targets will not be met until the data rate once again falls below the specified service bandwidth value. We strongly recommend that you or your customers limit the amount of traffic presented to the ingress EAN and handover point to a level that does not exceed the service bandwidth in order to ensure that HSNS can meet your application performance requirements. Note: The available values of service bandwidth may evolve over time.

E.1.6 HSNS Latency

HSNS latency (on a per service bandwidth profile basis) is a measure of the overall one-way fixed delay of Ethernet packets across a HSNS access tail circuit.

Technical attribute Attribute definition Performance target

Latency The absolute time (in milliseconds) from the Fibre access (one-way) time the first bit of an Ethernet frame enters the 10mS end-customer facing side of the HSNS demarcation point (at their premises) to the time the first bit of the same Ethernet frame exits the egress port on the handover point Copper access (within the same coverage area) facing you (or 15mS vice versa).

The latency figure is also dependent on the frame size and type of access medium used to deliver HSNS. A fibre optic delivery will have a lower latency figure over a copper access delivery. Target figure is based on a 1500 byte MAC payload.

43 HSNS Product User Guide | July 2017

HSNS One way Latency = 15mS

Service Provider supplied Customer Handover Edge (CE) device Point

Access Provider Service CE EAN EAS Edge Provider (PE) device Network End HSNS User Demarcation

End User Premise

As HSNS does not include active electronics at your customer’s end of the access, the real- time monitoring or measurement of line performance parameters (such as latency) is not possible. While offered as a non-managed layer 2 service, the access component is engineered to theoretical maximum limits, and offers a target value for one-way latency of 15 milliseconds for copper and 10mS for a fibre access.

E.1.7 Jitter

Technical attribute Attribute definition Performance target

Jitter The overall packet delay variation of an ≤ 8mS Ethernet packet between the HSNS (milliseconds) demarcation point at the end-customer and the interface at the local handover point (excluding serialisation delay)

One way packet delay variations exclude serialisation delay, which is the amount of time needed to transmit an Ethernet frame over the line rate. This serialisation delay is dependent on the size of the Ethernet frame, plus the size of the outstanding frames already being forwarded and is proportional to the actual line speed. HSNS is not offered as a managed service and does not include real-time monitoring or measurement of line performance parameters. It is, however, engineered to theoretical maximum limits and offers a target performance value for jitter of ≤8 milliseconds. Target figure is based on a 1500 byte MAC payload.

E.1.8 Data loss

Data loss (on a per service bandwidth connection basis) is a measure of the overall percentage of all data packets lost across a HSNS access circuit.

44 HSNS Product User Guide | July 2017

Technical Attribute definition Performance target attribute

Data Loss Overall percentage of all data frames lost across a ≤ 0.1% HSNS access between the service demarcation point facing the end-customer and the local handover point facing you (Excludes frames dropped due to sending invalid traffic or traffic that exceeds the service bandwidth)

HSNS is not offered as an end-to-end managed service and does not include real-time monitoring or measurement of line performance parameters. However, HSNS is engineered to theoretical maximum limits and offers a target performance value for data loss ≤1%.

45 HSNS Product User Guide | July 2017 Appendix F Interface options

(This section should be read in conjunction with the handover link product user guide.)

F.1 Handover link delivery The handover link is presented as a 1GbE or 10GbE 802.3 E-NNI retail 0service provider interface via an optical fibre interface on our MOFDF. The ether type at the handover point facing you is 88a8 (802.1ad). You’re responsible for rate-shaping traffic entering the handover point. We’ll discard any traffic exceeding the allocated service bandwidth at the handover point. The optical handover point is delivered over single mode fibre. The interface connectors are specified as follows: FC-PC, SC-APC, SC, LC Traffic not containing valid service attributes e.g. encapsulation ID, rate, Ethertype will be discarded.

F.2 Your requirements  A Gig or 10Gig Ethernet optical interface to support the Handover port carrying HSNS traffic.

 Your egress traffic should be paced below the SDR of the aggregated traffic to prevent traffic discard. We’ll specify the SDR (refer to HSNS service bandwidth values).

 802.1ad and 802.3 will be used for the interconnection at the handover link. Note: Each HSNS instance related to an end-customer access connection is delivered to you as a unique (per handover link) S-VLAN. Layer 3 aspects, such as IP addressing, are solely within your control.

 A connection to a handover point in each coverage area where HSNS access is required (unless Tail Extension is purchased).

46 HSNS Product User Guide | July 2017 Parameter Specification

Connector type Choice of: FC-PC, SC-APC, SC, LC Fibre type Single-mode fibre Standard IEEE 802.3z Interface protocol Gigabit Ethernet MTU Defined by downstream access speed option Bandwidth GbE: A payload capacity of 1024 Mbps for IP transmission

Optical parameters: -18.8dBm (minimum) Average receive power +0.7dBm (maximum) Centre wavelength 1310nm 1000BASE-LX Coupled transmit power -8.2dBm (minimum) -3.7dBm (maximum) VLAN ID numbering SVID (Chorus allocated)

47 HSNS Product User Guide | July 2017 Appendix G Extended fibre access

HSNS access tails can be delivered off either an Alcatel-Lucent 7302 ISAM or a 7450 configured EAN. The ISAM 7302, delivering HSNS Lite, will be fitted into nearly every Chorus exchange over time. The larger and more expensive 7450 EAN node (delivering the more feature rich HSNS Premium service) will only be installed into a smaller number of exchanges, predominantly in the metro areas of the main cities and larger regional centres.

The smaller HSNS Premium footprint can therefore, in some instances, create challenges when delivering fibre based access options out to end-customer premisess located beyond the local coverage of the nearest 7450 EAN equipped exchange. In these situations the ‘last mile’ fibre access between your customer’s premises and the associated local fibre servicing exchange can be extended (where sufficient dedicated fibre capacity is available) through one or more exchange geographic boundaries typical HSNS Premium access where the local fibre servicing exchange is also a 7450 EAN equipped exchange. In this scenario there is no requirement to extend the last mile access beyond the local fibre servicing exchange to connect to a 7450 EAN.

‘Local’ Fibre Servicing Exchange

The end-user premise is directly connected A to an EAN equipped exchange via EAN dedicated fibre(s) OFDF

End User Premise ‘Last Mile’ fibre access

‘Typical’ HSNS Premium connection … NO ‘Extended Fibre Access’ is required

A ‘typical’ HSNS Premium fibre access path to an EAN equipped local exchange

G.1 Extended fibre access delivery The following diagram illustrates an example of a HSNS Premium connection where the local fibre servicing exchange that the end-customer is directly connected to is not equipped with a 7450 EAN. The last mile fibre access must then be ‘extended’ through additional exchange boundaries in order to connect to the nearest 7450 EAN equipped exchange. The fibre access path traverses through two exchanges in order to connect to the nearest 7450 EAN equipped exchange. Where an extended fibre access is required an additional recurring charge is levied. Extended Fibre Access charges are $POA and identified via a fibre feasibility Note: Extended fibre access is only offered with HSNS Premium and is not available with HSNS Lite (fibre).

48 HSNS Product User Guide | July 2017

‘Local’ Fibre 7450 EAN

Servicing Exchange Exchange Exchange

A C B EAN

OFDF OFDF OFDF

End User Premise

‘Last Mile Extended Fibre Access fibre access HSNS Premium connection with additional ‘Extended Fibre Access’ component

A HSNS Premium connection that requires an extended fibre access to connect to an EAN exchange

G.2 Extended fibre access feasibility result HSNS Premium solutions that require an extended fibre access component will be identified in the initial fibre feasibility along with the associated Extended Fibre Access surcharge. The extended fibre access surcharge is expressed as a recurring monthly charge and is additional to the other typical recurring HSNS charges such as access, service bandwidth and Tail Extension (where applicable). Note: From a billing point of view the access group zone classification associated with the access speed charge is based on the exchange in which the 7450 EAN node is housed in (e.g. exchange A in the example above) rather than the local exchange to which the end-customer premises is directly connected to (e.g. exchange C in the example above).

The fibre feasibility result will also identify the exchange name code of the local fibre servicing exchange, the 7450 EAN equipped exchange and the associated local EAS exchange. An extended fibre access solution is easily identified by the fact that the exchange name code for the local and 7450 EAN exchange will differ. The fibre feasibility result will include:

 Fibre installation cost (one-off charge)

 Install time frame and classification of install build work required

 Access group charge zone classification of the associated 7450 EAN exchange

 Extended fibre access surcharge (recurring charge)

49 HSNS Product User Guide | July 2017 A sample OOT fibre feasibility result for a HSNS Premium solution that includes an extended fibre access component is illustrated below.

Sample OO&T fibre feasibility result that identifies an extended fibre access component

Once the HSNS access tail has been provisioned the customer will be billed with the following typical HSNS charges as listed below:

 Fibre install (standard or non-standard) One-Off charge

 Access speed Recurring monthly charge

 Service bandwidth Recurring monthly charge

 Extended fibre access (where applicable) Recurring monthly surcharge

 Tail Extension (where applicable) Recurring monthly charge Note: In some instances where your customer’s premises are located in a geographically remote region the feasibility result may return a ‘service not available’ result. This indicates that there is no fibre network (or insufficient fibre capacity) available in that region or exchange area to provision a HSNS Premium service to that specific premises.

50 HSNS Product User Guide | July 2017 Appendix H Diversity options

HSNS offers a range of diversity options that you can incorporate into your own network design to help improve the resiliency of your service for your customers. These diversity options can be broken down into two categories:  Access diversity . Last mile . Geographic access diversity . Full diversity  Logical diversity . Handover diversity . Geographic handover diversity

The following information gives details on each of these diversity variants. The HSNS diversity service preview paper provides additional information and background on diversity and is recommended to be read in conjunction with this product user guide.

H.1 Access diversity: Access diversity allows the customer to select a combination of access tails and speeds from the following product variants:

 HSNS Premium

 HSNS Lite (fibre)

 HSNS Lite (copper) You can select any combination of these HSNS variants to create a solution that fits your customer’s requirements. The following table illustrates the access variants that can be used for the standard and diverse components of a solution.

HSNS service variants Diversity – available options

Standard access Diverse access

HSNS Premium √ √

HSNS Lite (fibre) √ √

HSNS Lite (copper) √  Our design rules dictate that a copper access tail cannot be used to deliver the diverse access tail. The reason being that the length of the diverse access cable route (between the end- customer premises and the Chorus access node) will be considerably longer that the length of the normal cable duct route that would typically be allocated to provision a standard access. While the performance and bandwidth capability of a fibre access is not affected as much by the extended length of the diverse fibre route, the same cannot be said for copper. It’s relatively simple to extend existing fibre paths by splicing on additional sections of diverse fibre cable and still deliver the same value of bandwidth as the standard/primary access, the

51 HSNS Product User Guide | July 2017 same is not possible with copper, whose bandwidth capacity reduces dramatically with increased distance. At the same time the design of our underground copper cable access network does not lend to easy splicing of additional sections of copper cable via extended diverse routes. Furthermore, while some fibre ducting is installed in physical ring type duct designs the same design approach is not used with copper based access networks and therefore it’s not easy to provisioning diverse access routes.

Once each access tail is built, there are no additional ongoing costs for the service apart from the monthly rental for each access tail. *All diversity solutions will require a manual prequalification (PQ) to ensure that the required level of resiliency can be delivered as outlined in this product user guide. H.1.1 Ducting

To ensure that the customer receives the maximum level of access diversity we’ll always quote the cost to install an additional cable entry point (dual duct) if not currently present into the building premises. At the time of installation you can opt not to proceed with the diverse duct option. This is not the preferred delivery method as it reduces the resiliency of the service.

H.2 Last mile access diversity With last mile access diversity you’re looking to provide high availability against failure of the Chorus last mile fibre access (i.e. a fibre cut) or failure of the access port or line card on the Ethernet Access Node (EAN) that directly connects to the cable access to your customer’s site. This diversity option is provisioned using two Ethernet Virtual Connections across our network. Each Ethernet attachment circuit is allocated its own separate physical port on the same EAN but mapped to the same physical EAS port at the handover point facing you. Each EAN port is connected to the end-customer premises via physically diverse access cable routes. The logical configuration is illustrated in the diagram below.

Chorus Network

Logical configuration for last mile access diversity

52 HSNS Product User Guide | July 2017

As each HSNS OVC is a HSNS access tail connection in its own right, it’s presented to you at the handover point with its own individual S-VID. Note: When ‘last mile access diversity’ involves two fibre-based Ethernet attachment circuits, separation of the two can normally be built, notwithstanding any environmental and/or geographical restrictions. As part of improvements to our inventory systems, we will ensure access diversity options are maintained for the life of the service. Pending improvements to our inventory systems, we have a manual process in place to maintain last mile access diversity. When it involves one copper-based Ethernet attachment circuit and one fibre-based Ethernet attachment circuit, separation of the two can normally be built, notwithstanding any environmental and/or geographic restrictions, but ongoing maintenance of separation of the two cannot be guaranteed for the life of the service. This is due to a different inventory system being used for fibre records versus copper records.

Where you have multiple handovers in the one physical exchange building, we can map each diverse access to a different handover port. Where possible we’ll work with you to identify potential resiliency at this level when ordering handover links. Last mile access diversity cannot support Tail Extension.

H.3 Geographic access diversity Geographic access diversity introduces even greater levels of physical separation by routing each last mile access path via a different EAN device located in geographically diverse exchange buildings. With this diversity option you is protecting your service from failure of the last mile access cable, access port and/or the Ethernet access node itself. This diversity option, by default, also protects from a failure at either of the Chorus buildings that house the Ethernet access nodes. This diversity option is provisioned using two Ethernet virtual connections across our network. Each Ethernet attachment circuit is allocated its own port on separate EAN, housed in different exchange buildings, thereby providing physically diverse access cable routes. Both HSNS OVCs are mapped to the same physical EAS port at the handover point facing you. Each HSNS OVC is presented to you at the handover point with its own individual S-VID. Note: When ‘geographic access diversity’ involves two fibre-based Ethernet attachment circuits, separation of the two can normally be built, notwithstanding any environmental and/or geographical restrictions. As part of improvements to our inventory systems, we’ll ensure access diversity options are maintained for the life of the service. Pending improvements to our inventory systems, we have a manual process in place to maintain geographic access diversity. When geographic access diversity involves one copper-based Ethernet attachment circuit and one fibre-based Ethernet attachment circuit, separation of the two can normally be built, notwithstanding any environmental and/or geographic restrictions, but ongoing maintenance of separation of the two cannot be guaranteed for the life of the service. This is due to a different inventory system being used for fibre records versus copper records. Where you has multiple handovers in one exchange building, we can map each diverse access to a different handover port. Where possible, we’ll work with you to identify potential resiliency at this level when ordering handover links. Last mile access diversity cannot support Tail Extension.

53 HSNS Product User Guide | July 2017

Logical configuration for geographic access diversity

H.4 Full diversity Full diversity potentially provides the highest level of service availability on our network. Full diversity effectively provides diversity at both ends of a service connection by building resiliency into the Ethernet attachment circuits facing both the end-customer and you (i.e. handover link), protecting against last mile access cable cuts, access port/line card, handover port/line card, and/or node failures, where possible. The highest degree of Full Diversity relies on the ability to configure the end points of each OVC on separate EAN and EAS devices, and when coupled with the inherent resiliency of our MPLS network, will enable you to deliver a higher availability solution to your customers. The logical configuration of full diversity is illustrated in the diagram below.

54 HSNS Product User Guide | July 2017

Logical configuration for Full Diversity

Each HSNS OVC is presented to you at the handover point with its own S-VID. Full diversity can be used to protect the service to your customer is being impacted by a failure within our network and/or by a failure within your network. Consideration should therefore be given by you to the resilience of your infrastructure on the ends of a full diversity service, i.e. going to the expense of providing full diversity, only to connect both Ethernet attachment circuits into the same CPE, might be questionable. Note: When full diversity involves two fibre-based Ethernet attachment circuits, separation of the two can normally be built, notwithstanding any environmental and/or geographical restrictions. As part of improvements to our inventory systems, we will ensure access diversity options are maintained for the life of the service. Pending improvements to our inventory systems, Chorus has a manual process in place to maintain full diversity When full diversity involves one copper-based Ethernet attachment circuit and one fibre- based Ethernet attachment circuit, separation of the two can normally be built, notwithstanding any environmental and/or geographic restrictions, but ongoing maintenance of separation of the two cannot be guaranteed for the life of the service. This is due to a different inventory system being used for fibre records versus copper records. Note: The handover fibres for each of the two handover points can be provided by us or a third party.

You have the option of incorporating Tail Extension and extended fibre into the access tails to provide the full diversity solution to your customers. You’ll be limited to only one Tail Extension per fully diverse configuration.

H.5 Logical diversity Logical diversity will provide service protection for individual access tail connections depending on the variant selected at the following points in the network: failure of EAN node, handover ports or failure (cut) of a handover fibre access.

55 HSNS Product User Guide | July 2017 While this solution is not a replacement for access diversity, in some instances it will provide adequate cover for your customers. This level of resiliency will not require the potential high cost associated with the initial build cost and multiple monthly rentals that access diversity will incur. Logical diversity can be provisioned across the following HSNS variants:  HSNS Premium

 HSNS Lite (fibre)

 HSNS Lite (copper)

H.5.1 Handover diversity

With handover diversity the customer is looking to protect a service connection from disruption caused by a fault at the Handover end of the connection path. Handover diversity delivers two separate Ethernet attachment circuits at the handover, both of which connect back to the same EAN access port (facing the end-customer) via two OVCs. Both the primary and secondary handover ports are delivered off the same EAS node, with each port being provisioned off different line cards. Where possible we’ll work with you to identify potential resiliency at this level when ordering handover links. This diversity option effectively provides service protection to individual HSNS access tail connections against failure of either of the EAS handover ports; failure of either handover fibre access (i.e. a fibre cut); and failure of your ports. The logical configuration is illustrated in the diagram below.

SVID 500

SVID 400

Logical configuration for handover diversity

Note: We can supply both of the fibre based Ethernet attachment circuits at the handover point (i.e. handover fibres) or they can be supplied by a third party or by you. You could also use a mixture of us and third party/you supplied fibre. Where we have supplied both handover fibres you can opt to have them delivered to your network site via diverse fibre duct paths.

56 HSNS Product User Guide | July 2017 With handover diversity you must identify those individual HSNS access tail connections (which may already be mapped to an existing handover point) that must also be mapped to the diverse handover. This means that handover diversity does not, by default, provide diversity to every HSNS access tail connection associated with the primary handover point and, instead, you must identify only those individual HSNS access tail connections that appear on the primary handover point that require handover diversity with a selected secondary handover point. Handover diversity is therefore provided on an individual HSNS access tail connection basis. To deliver this capability two HSNS OVCs are configured from the same EAN port to different diverse EAS handover ports. At the end-customer premises end of the service both OVCs will use the same Ethernet attachment circuit (i.e. physical last mile access cable).

To help more clearly explain how handover diversity works, take the example of a handover point that has 100 x HSNS access tails already connected to it, however only three of these existing HSNS access tails required handover diversity. Should a fault develop on the primary handover link then all but the three selected HSNS access tails will experience a service outage. The 3 x HSNS access tails that have a diverse OVC mapped to the secondary handover point will continue to work. Note: Each of the three HSNS access tail connections used in this example could be of a different type i.e. 1 x HSNS Premium, 1 x HSNS Lite fibre and 1 x HSNS Lite copper access tail connection. The network configuration for handover diversity will be slightly different to the other access type diversity options presented in this service preview document. There are additional requirements on the end-customer CPE equipment that you must be aware of. With the last mile access, geographic access and full diversity type options each of the dual HSNS access tail connections only have a single S-VID value allocated per OVC, with the S- VID being pushed and popped at the EAS/handover end of the OVC. However, with handover diversity 2 x Chorus allocated S-VID values are allocated per individual HSNS OVC: one at the EAS/handover and one at the EAN/access end of each HSNS OVC. This is illustrated in the figure 24 diagram. Handover diversity therefore requires your CPE on the end-customer’s premises to be an 802.1ad provider bridge (capable of VLAN stacking). Each of the two diverse HSNS access tail connections will be allocated an S-VID for each end of the OVC. Chorus will push/pop an SVID at the end-customer end for each of the standard/primary OVC and the diverse/secondary OVC (depending which one is being used). Your customer’s CPE must also push/pop SVID’s to mark service frames for each of the standard/primary or diverse/secondary OVCs. Each handover link is still required to be an 802.1ad provider bridge (capable of VLAN stacking) so that Chorus allocated SVID’s can be pushed/popped in the same manner as with the current default standard HSNS service. It is important to note that the SVID at the end-customer end will not be aligned with the SVID at the handover point. The reason being that SVIDs values are independently allocated at each end of a HSNS OVC. If the end-to end service wishes to use the primary path connection, then the end-customer CPE must ‘push’ the appropriate S-VID value allocated by us for the ‘A’ end primary OVC onto egress traffic service frames. As the Ethernet service frames enter the Chorus EAN port it will inspect the value of the outer tag (i.e. the S-VID value) after which it will pop the outer S- VID tag and send the service frame down the associated HSNS OVC path to the remote primary handover point. At the primary handover point the EAS port will push the allocated Chorus S-VID tag value associated with the primary handover point (Z-end) of the primary OVC.

57 HSNS Product User Guide | July 2017 If the traffic is to be now delivered from the end-customer CPE (A-End) to the secondary handover via the secondary OVC connection then the end-customer CPE must tag all egress Ethernet service frames with the Chorus allocated A-End S-VID tag number (i.e. push) associated with the secondary HSNS OVC . On entry to the Chorus EAN access port the outer S-VID tag will be popped off and the traffic sent down the diverse HSNS OVC associated with the secondary handover point, where it will be presented to you with the associated Z-End S- VID value associated with the secondary OVC handover.

H.5.2 Geographic handover diversity

This option delivers two handover ports delivered off different EAS nodes. Each of the diverse EAS nodes can be located within the same physical Chorus building or in geographically diverse buildings. This diversity option effectively provides service protection for individually selected HSNS access tail connections against failure of either of the EAS node, handover ports or failure of either handover fibre access (i.e. a fibre cut).

SVID 500

SVID 400 1 0 M ,

1 Logical configuration for Geographic Handover Diversity 0

0 HSN M Geographic handover diversity will require the CPE on the end-customer’s premises to be an S 802.1ad provider bridge (capable of VLAN stacking). We’ll allocate a S-VID for your & customer’s end and the handover end of each of the two diverse HSNS OVCs (in exactly the Pre same manner as handover diversity). 1 miu 0 0 m 0 Expande M d Feature Set A c c 58 HSNS Product User Guide | July 2017 e s

Appendix I: HSNS POIs

This appendix lists the POIs for HSNS, where:  UFB Coverage Areas match the NGA UFB Coverage Areas, including RBI;  HSNS Coverage Areas are ‘legacy’ alternate coverage areas. These may overlap some UFB Coverage Areas For a full list of Chorus Exchanges to POI mapping, see the Chorus Customer website.

Coverage Area Code Type POI(s) ASHBURTON AR UFB ASHBURTON AUCKLAND GLF/MDR UFB GLENFIELD / MAYORAL DRIVE HENDERSON HSN HSNS HENDERSON HOWICK HCK HSNS HOWICK MOUNT ALBERT MAB HSNS MOUNT ALBERT PAPAKURA PAK HSNS PAPAKURA PAPATOETOE POP HSNS PAPATOETOE REMUERA RUE HSNS REMUERA TORBAY TBY HSNS TORBAY BLENHEIM BM UFB BLENHEIM CHRISTCHURCH CH UFB CHRISTCHURCH RICCARTON RIC HSNS RICCARTON DUNEDIN DN/SOD UFB DUNEDIN / SOUTH DUNEDIN FIELDING PM UFB PALMERSTON NORTH GISBORNE GS UFB GISBORNE GREYMOUTH GM UFB GREYMOUTH HAMILTON HN UFB HAMILTON HAWERA NU UFB NEW PLYMOUTH INVERCARGILL IN UFB INVERCARGILL KAPITI PRM UFB PARAPARAUMU LEVIN LVN UFB LEVIN MASTERTON MS UFB MASTERTON NAPIER / HASTINGS NA/HBN UFB NAPIER / HASTINGS NELSON NN UFB NELSON NEW PLYMOUTH NU UFB NEW PLYMOUTH OAMARU OU UFB OAMARU PALMERSTON NORTH PM UFB PALMERSTON NORTH PUKEKOHE PUK UFB GLENFIELD / MAYORAL DRIVE QUEENSTOWN QST UFB QUEENSTOWN

59 HSNS Product User Guide | July 2017 CROMWELL CMW HSNS CROMWELL RANGIORA CH UFB CHRISTCHURCH ROTORUA RO UFB ROTORUA TAUPO TPO UFB TAUPO TAURANGA TG UFB TAURANGA TIMARU TU UFB TIMARU TOKOROA HN UFB HAMILTON WAIHEKE ISLAND WH UFB GLENFIELD / MAYORAL DRIVE WAIUKU WKU UFB GLENFIELD / MAYORAL DRIVE WANGANUI WG UFB WANGANUI WELLINGTON / PORIRUA WN/PRO UFB WELLINGTON / PORIRUA NAENAE NAE HSNS NAENAE WHAKATANE WHK UFB WHAKATANE WHANGAREI WR UFB WHANGAREI KERIKERI KC HSNS KERIKERI

60 HSNS Product User Guide | July 2017