Version 1.0 Draft Effective date: 2026-04-01 Last updated: 2026-03-19

RegPEX Acceptable Use Policy

This document defines the permitted and prohibited uses of the RegPEX peering fabric and associated services. All Members must comply with this policy as a condition of participation.

1. Permitted Use

The following uses of the RegPEX infrastructure are expressly permitted:

Category Details
IPv4/IPv6 Unicast Exchange of unicast IPv4 and IPv6 traffic between peering parties
BGP BGP-4 and MP-BGP for routing table exchange
ICMP Internet Control Message Protocol for connectivity testing
BFD Bidirectional Forwarding Detection for fast failure detection

2. Prohibited Use — Traffic

The following traffic and behavior are prohibited on the RegPEX fabric:

Prohibition Description
Transit No transit services; traffic must originate from or be destined to a RegPEX Member
Default Route No advertisement of default (0.0.0.0/0 or ::/0) routes
Proxy ARP/NDP No proxy ARP or Neighbor Discovery Proxy
DHCP No DHCP server or relay services
STP No Spanning Tree Protocol or similar layer-2 loop-prevention protocols
Broadcast Storm No excessive broadcast, multicast, or unknown-unicast flooding
MAC Flooding No MAC address table exhaustion attacks

3. Prohibited Use — Security

The following security-related activities are strictly prohibited:

Prohibition Description
IP Spoofing No transmission of traffic with forged source IP addresses
ARP Spoofing No ARP cache poisoning or spoofed ARP/NDP advertisements
DDoS No participation in or origination of distributed denial-of-service attacks
Port Scanning No unauthorized port scanning or reconnaissance against other Members
Unauthorized Access No attempts to gain unauthorized access to systems or networks
BGP Hijacking No advertisement of routes for address space not legitimately assigned to the advertiser

All Members must comply with applicable laws, including:

  • Turkish Law — Full compliance with Turkish legislation governing telecommunications and data communications
  • Copyright — No transmission of infringing or pirated content
  • Spam — No unsolicited bulk messaging; compliance with anti-spam regulations

5. Ethernet Frame Requirements

Frame Size

Type Size
Standard 64–1500 bytes
Jumbo Up to 9000 bytes (where explicitly supported)

Allowed EtherTypes

EtherType Protocol
0x0800 IPv4
0x86DD IPv6
0x0806 ARP

VLAN Restrictions

  • 802.1Q — No 802.1Q tagged frames on access ports; untagged/access mode only unless otherwise agreed

6. BGP Security Requirements

Members must implement the following BGP security measures:

Requirement Description
MD5 / TCP-AO Session authentication using MD5 or TCP-AO
GTSM Generalized TTL Security Mechanism (recommended)
max-prefix Prefix limit configured as per RegPEX guidelines
Graceful Restart Graceful restart capability recommended

7. Monitoring

RegPEX monitors the peering fabric for operational and security purposes:

Aspect Policy
sFlow / NetFlow Traffic sampling may be used for aggregate statistics
Aggregate Only Data is used only in aggregate form; no per-flow or per-Member deep inspection
No Content Inspection RegPEX does not inspect payload content beyond required header analysis

8. Violation Procedure

Process

  1. Detect — RegPEX or another Member identifies a violation
  2. Notify — RegPEX notifies the violating Member via registered contact
  3. Remediation — Member has 1–24 hours to fix the issue (depending on severity)
  4. Disable — If not remediated, RegPEX may disable the affected port or sessions
  5. Escalate — Persistent or serious violations may lead to suspension or termination

Emergency Rights

RegPEX reserves the right to immediately disable any port or BGP session that poses a critical threat to the fabric or other Members, with notification to follow.

Abuse Reporting

Report suspected policy violations to: abuse@regpex.net


This policy is subject to change. Members will be notified of material updates in advance.