RegPEX Connection Models Policy

1. Overview

RegPEX, as a carrier-neutral IX, offers members three connection models. Each model addresses different technical and commercial requirements. Members may switch between models or use multiple models simultaneously.

2. Model 1 — Direct Cross-Connect

2.1 Definition

A physical fibre connection (cross-connect) between the member's own equipment (router or switch) and RegPEX's peering switch, installed within the data centre. This is RegPEX's most robust and permanent connection model.

2.2 Suitable Use Cases

• Members with colocation or rack space at one of the RegPEX POP locations
• Members requiring high traffic capacity or low latency
• Members seeking long-term, guaranteed connectivity

2.3 Technical Specifications

2.4 Provisioning Process

1. Membership application is completed
2. RegPEX assigns port and peering IP
3. Member orders cross-connect from the data centre operator (LoA provided by RegPEX)
4. BGP configuration is completed once the physical link is in place
5. Connectivity test and go-live

2.5 Member Obligations

• Pays cross-connect installation and monthly recurring charges directly to the data centre operator
• Ensures equipment is physically present at the POP
• Notifies RegPEX NOC of planned maintenance at least 72 hours in advance

2.6 RegPEX Obligations

• Maintains the peering switch port in active, monitored state
• Guarantees 99.95% uptime SLA
• Applies standard SLA credit policy in case of outage

3. Model 2 — Carrier VLAN (L2 Extension)

3.1 Definition

A model in which the member is not physically present at a RegPEX POP but connects to the RegPEX peering VLAN at Layer 2 via a third-party carrier (ISP, metro Ethernet operator, MPLS provider, etc.) that has access to that location.

3.2 Suitable Use Cases

• Members near a RegPEX POP but not in the same building
• Members wishing to extend fibre or metro Ethernet from their own colocation to a RegPEX POP
• Members purchasing a ready-made "IX handoff" service from a carrier

3.3 Carrier Requirements

• The carrier must be able to extend the RegPEX peering VLAN (VLAN 100) to the member's location (L2 extension)
• Delivery must be untagged or single VLAN-tagged (for QinQ-capable carriers, inner tag must be untagged)
• Carrier link MTU must be at least 1504 bytes (VLAN tag + Ethernet overhead + payload)
• The carrier is not required to be on an approved RegPEX partner list, but must meet technical requirements

3.4 Technical Specifications

3.5 Liability Boundaries

• RegPEX guarantees only the peering fabric and its own switch port.
• RegPEX bears no responsibility for outages, latency, or packet loss on the carrier link.
• In the event of a fault, the member must first contact their carrier, then notify RegPEX NOC.

3.6 Provisioning Process

1. Member selects "Carrier VLAN" model in the membership application and provides carrier details
2. RegPEX coordinates with the carrier for technical acceptance
3. VLAN configuration and end-to-end testing are completed
4. BGP configuration and go-live

3.7 Carrier Change

If a member wishes to change carrier, RegPEX NOC must be notified at least 5 business days in advance. Where possible, both carriers should be active simultaneously to minimise disruption.

4. Model 3 — Remote Peering (GRE Tunnel)

4.1 Definition

A model in which the member has no physical presence at any RegPEX POP and connects to the RegPEX peering fabric via a GRE tunnel over their own internet connection to the RegPEX Remote Peering Gateway (RPG).

4.2 Purpose and Scope

Remote Peering is designed for the following scenarios:

• Network operators wishing to quickly start or test connectivity with RegPEX
• Small to medium-sized networks where traffic volume does not yet justify a physical connection
• Transitional use before migrating to a permanent physical connection

Important: Remote Peering is not designed as a permanent connection model. As traffic grows, or after a maximum of 6 months, members are expected to migrate to Model 1 or Model 2.

4.3 Free Trial Period

RegPEX offers approved Remote Peering members a 1-month free trial upon activation.

• The trial period begins on the date the tunnel is activated.
• The trial period counts towards the 6-month maximum.
• All technical requirements and usage rules apply in full during the trial.
• At the end of the trial, the member may proceed to a paid subscription or terminate the connection. If no notification is given, the connection is automatically terminated.

4.4 Technical Specifications

4.5 Tunnel Requirements

Member side:

• GRE-capable router (Cisco IOS/XE, Juniper Junos, MikroTik, Linux iproute2, FRRouting, etc.)
• Fixed, publicly routable IPv4 address (GRE endpoint)
• Tunnel MTU must be configured at 1476 bytes or lower
• Transport connection: minimum 100 Mbps (reliable, low-loss connection recommended)

Prohibited uses:

• Reselling or sub-leasing the GRE tunnel to third parties
• Carrying transit traffic over the tunnel
• Changing the tunnel endpoint IP address without notifying RegPEX
• Using more than one MAC address (without approval)

4.6 SLA and Liability

4.7 Duration Limit and Migration Obligation

• Remote Peering may be used for a maximum of 6 months (including the free trial period).
• At the end of month 6, the member must choose one of the following:
  • Continue with Model 1 (Cross-Connect) or Model 2 (Carrier VLAN)
  • Withdraw from membership
• RegPEX will send a written migration notice at month 4.
• In exceptional circumstances (natural disaster, POP access restrictions, etc.), RegPEX may grant an extension of up to 3 months.

4.8 Application and Provisioning Process

1. Member selects "Remote Peering (GRE)" in the membership application
2. Member's GRE endpoint public IP address and preferred POP are provided
3. RegPEX reviews and approves the application
4. Upon approval, RegPEX provides RPG parameters (RPG IP, tunnel key, peering IP)
5. Member configures the GRE tunnel on their router
6. Connectivity test (ping, MTU check) is performed
7. BGP configuration and go-live — 1-month free trial begins

5. Model Comparison

6. Model Migration

• Migration from Remote Peering to Cross-Connect or Carrier VLAN is carried out with minimal disruption.
• Migration planning must be coordinated with RegPEX NOC at least 10 business days in advance.
• Both connections may remain active simultaneously during migration (additional charges may apply).

7. Contact

• Applications and technical enquiries: peering@regpex.tr
• NOC: noc@regpex.tr / +90 (312) 486 01 86
• General enquiries: Contact Form