Peering Policy for AS3257

Requirements for Settlement-Free IPv4/IPv6 Interconnection

• Applicant must operate a 24x7 fully staffed Network Operation Center and must respond to all operational issues within 24 hours
• Applicant must operate a global IP backbone consisting of mainly 10Gbps/OC192 or faster links
• Applicant must use the peering connection for all traffic destined towards the Tinet network
• Tinet does not accept routes containing a peers AS number from any other peer network
• Applicant must sell (native) Internet connectivity to third parties and/or end users
• Applicant must meet and maintain a traffic ratio of 1:2 or better
• Applicant and Tinet agree on routing practices and locations such that each party bears a reasonably equal share of network cost
• Unless otherwise agreed, Applicants announcements must be consistent, i.e. Applicant must advertise the same set of customer routes with the same policies on all peering sessions
• There will be only one peering relationship per corporation/company
• Applicant or Applicants's entities must not have any transit or peering relationship with Tinet or any other Tinet entity or have had such a relationship in the 6 months prior to application.
• Peers on public exchanges must not sell or provide next-hop information to any 3rd party, e.g. peer must not re-advertise Tinet routes to any peer
• Applicant must filter received customer routes using prefix-list filters on all customer links
• Applicant agrees to peer in all markets where Peer and Tinet share a presence
• Tinet reserves the right to terminate the peering at any time with 30 days notice
• Applicant agrees in writing to Tinet's peering policy
• Tinet may honor legacy peers not entirely matching requirements outlined in here at it's sole discretion
• This policy is a guideline. Meeting all the requirements stated in here does not guarantee that Tinet will enter into a settlement-free relationship with the applicant. Tinet reserves the right not to grant settlement-free peering to an applicant based on business reasons
• Any exceptions to this policy will be granted at the sole discretion of Tinet

Technical Requirements

• All new peerings must be over private links of minimum 10G capacity. A minimum of three links interconnecting independent node-sets is required for each continent. Substantial domestic traffic is expected to justify each of these links.
• Applicants traffic received from the Tinet network must amount to at least 5 Gbit/s judged on average traffic over 1 (one) month
• Applicant advertises a minimum of 2,000 fully aggregated routes or equivalent of 75,000 Class-C networks
• Applicant provides paid transit services to at least 500 distinct directly connected AS numbers
• Applicants network must share a presence with Tinet in at least six regions in Europe and six markets in North America out of the reguions below. These regions must be linked with redundant dedicated IP backbone capacity of OC192 or higher. Applicants are expected to have a significant customer base in any of the regions and thus carry siginficant local traffic in these regions to match this requirement
• All peering connections must be dual-stack IPv4 and IPv6

European regions

• Belgium, Netherlands, Luxemburg
• Germany, Austria, Switzerland
• France
• UK (including Ireland)
• Italy, Greece
• Spain
• Sweden, Norway, Denmark
• Czech Republic, Poland, Romania, Bulgaria, Slovakia

US regions

• Boston, Montreal, Toronto
• New York, New Jersey
• Washington DC, Ashburn
• Miami
• Dallas
• Denver
• Bay Area (San Jose)
• Seattle
• Los Angeles
• Chicago
• Atlanta

Asian regions

• Hong Kong
• Singapore